In Section 1.3:
The uses of "MUST" and "MUST NOT" in this document are limited to (a)
requirements to follow the IETF process for IETF standards, and (b)
quotes from other documents. As a result, the use of MUST and MUST
NOT in this document does not prescribe new mandatory behavior within
implementations.
Wasn't this to have gone in Section 1.2?
Section 2.1.1 states:
While the Framed-Interface-Id attribute defined in [RFC3162] Section
2.2 included a value field of 8 octets, the data type was not
explicitly indicated, and therefore there is controversy over whether
the format of this attribute was intended to be an 8 octet String or
whether a special Interface-Id type was intended.
. . .
Implementations supporting the Framed-Interface-Id
attribute may select a data type of their choosing (most likely an 8
octet String or a special Interface-Id data type).
Yet Section A.1.1 says:
* Interface-Id (8 octets in network byte order)
Should this say:
* Interface-Id (8 octet string in network byte order)
|