Skip to content

Commit

Permalink
Specify MAC address format like this example 00-00-5E-00-53-23
Browse files Browse the repository at this point in the history
Reasons for choosing this format:

* IEEE 802 uses this format: https://en.wikipedia.org/wiki/MAC_address#Notational_conventions
* IETF uses this format: https://tools.ietf.org/html/rfc7042

It is not yet clear if we should prefer upper or lowercase. I just went
with uppercase for now because that is what the references above use.

Reason for choosing 00-00-5E-00-53-23:

It is in the range of unicast MAC addresses reserved for documentation
as specified by: https://tools.ietf.org/html/rfc7042#section-2.1.2
  • Loading branch information
ypid-geberit committed Feb 11, 2021
1 parent 9e30a88 commit 0d4a296
Show file tree
Hide file tree
Showing 6 changed files with 42 additions and 3 deletions.
12 changes: 10 additions & 2 deletions schemas/client.yml
Original file line number Diff line number Diff line change
Expand Up @@ -48,19 +48,27 @@
- name: mac
level: core
type: keyword
example: 00-00-5E-00-53-23
description: >
MAC address of the client.
The format from RFC 7042 should be used: Each octet (that is, 8-bit
byte) is represented by two [uppercase] hexadecimal digits giving the
value of the octet as an unsigned integer. Successive octets are
separated by a hyphen.
- name: domain
level: core
type: keyword
type: wildcard
beta: Note the usage of `wildcard` type is considered beta. This field used to be type `keyword`.
description: >
Client domain.
- name: registered_domain
level: extended
type: keyword
type: wildcard
short: The highest registered client domain, stripped of the subdomain.
beta: Note the usage of `wildcard` type is considered beta. This field used to be type `keyword`.
description: >
The highest registered client domain, stripped of the subdomain.
Expand Down
6 changes: 6 additions & 0 deletions schemas/destination.yml
Original file line number Diff line number Diff line change
Expand Up @@ -43,9 +43,15 @@
- name: mac
level: core
type: keyword
example: 00-00-5E-00-53-23
description: >
MAC address of the destination.
The format from RFC 7042 should be used: Each octet (that is, 8-bit byte) is
represented by two [uppercase] hexadecimal digits giving the value of
the octet as an unsigned integer. Successive octets are separated by a
hyphen.
- name: domain
level: core
type: keyword
Expand Down
7 changes: 7 additions & 0 deletions schemas/host.yml
Original file line number Diff line number Diff line change
Expand Up @@ -55,11 +55,18 @@
- name: mac
level: core
type: keyword
example: 00-00-5E-00-53-23
description: >
Host mac addresses.
The format from RFC 7042 should be used: Each octet (that is, 8-bit byte) is
represented by two [uppercase] hexadecimal digits giving the value of
the octet as an unsigned integer. Successive octets are separated by a
hyphen.
normalize:
- array


- name: type
level: core
type: keyword
Expand Down
8 changes: 7 additions & 1 deletion schemas/observer.yml
Original file line number Diff line number Diff line change
Expand Up @@ -20,8 +20,14 @@
- name: mac
level: core
type: keyword
example: 00-00-5E-00-53-23
description: >
MAC addresses of the observer
MAC addresses of the observer.
The format from RFC 7042 should be used: Each octet (that is, 8-bit byte) is
represented by two [uppercase] hexadecimal digits giving the value of
the octet as an unsigned integer. Successive octets are separated by a
hyphen.
normalize:
- array

Expand Down
6 changes: 6 additions & 0 deletions schemas/server.yml
Original file line number Diff line number Diff line change
Expand Up @@ -48,9 +48,15 @@
- name: mac
level: core
type: keyword
example: 00-00-5E-00-53-23
description: >
MAC address of the server.
The format from RFC 7042 should be used: Each octet (that is, 8-bit byte) is
represented by two [uppercase] hexadecimal digits giving the value of
the octet as an unsigned integer. Successive octets are separated by a
hyphen.
- name: domain
level: core
type: keyword
Expand Down
6 changes: 6 additions & 0 deletions schemas/source.yml
Original file line number Diff line number Diff line change
Expand Up @@ -43,9 +43,15 @@
- name: mac
level: core
type: keyword
example: 00-00-5E-00-53-23
description: >
MAC address of the source.
The format from RFC 7042 should be used: Each octet (that is, 8-bit byte) is
represented by two [uppercase] hexadecimal digits giving the value of
the octet as an unsigned integer. Successive octets are separated by a
hyphen.
- name: domain
level: core
type: keyword
Expand Down

0 comments on commit 0d4a296

Please sign in to comment.