|
|
|
|
Found 6 records.
Errata ID: 3156
Status: Verified
Type: Editorial
Reported By: Nikolai Malykh
Date Reported: 2012-03-15
Verifier Name: Adrian Farrel
Date Verified: 2012-03-17
Section 3.5.8 says:
Path Vector
Specifies the LSRs along the LSR being set up by the Label Request
message. Section "Path Vector Procedures" describes how to handle
this TLV.
It should say:
Path Vector
Specifies the LSRs along the LSP being set up by the Label Request
message. Section "Path Vector Procedures" describes how to handle
this TLV.
Notes:
Erroneously typed LSR instead of the LSP.
Errata ID: 2133
Status: Held for Document Update
Type: Editorial
Reported By: Nikolai Malykh
Date Reported: 2010-04-07
Held for Document Update by: Adrian Farrel
Section 2.5.4 says:
NON EXISTENT Session TCP connection established INITIALIZED
established
It should say:
NON EXISTENT Session TCP connection established INITIALIZED
Errata ID: 3155
Status: Held for Document Update
Type: Editorial
Reported By: Nikolai Malykh
Date Reported: 2012-03-12
Held for Document Update by: Adrian Farrel
Section 3.5.1.2.1 says:
- The LDP protocol version is not supported by the receiver, d or
it is supported but is not the version negotiated for the
session during session establishment. This is a fatal error
signaled by the Bad Protocol Version Status Code.
It should say:
- The LDP protocol version is not supported by the receiver, or
it is supported but is not the version negotiated for the
session during session establishment. This is a fatal error
signaled by the Bad Protocol Version Status Code.
Errata ID: 3415
Status: Held for Document Update
Type: Editorial
Reported By: Jeff Wheeler
Date Reported: 2012-11-26
Held for Document Update by: Adrian Farrel
Date Held: 2012-11-26
Section 3.1 says:
Prior to completion of the negotiation, the maximum allowable length is 4096 bytes.
It should say:
Prior to completion of the negotiation, the maximum allowable length is 4096 octets.
Notes:
"octets" instead of "bytes"
Although "octet" is technically correct, there will be little confusion caused by the use of "byte"
Errata ID: 3425
Status: Held for Document Update
Type: Editorial
Reported By: Jeff Wheeler
Date Reported: 2012-12-08
Held for Document Update by: Adrian Farrel
Section 3.5 says:
The specification assigns type values for related messages, such as the Label messages, from of a contiguous block in the 16-bit message type number space.
It should say:
The specification assigns type values for related messages, such as the Label messages, from a contiguous block in the 16-bit message type number space.
Notes:
"from of a contiguous block" changed to "from a contiguous block"
Errata ID: 3416
Status: Rejected
Type: Technical
Reported By: Jeff Wheeler
Date Reported: 2012-11-26
Rejected by: Adrian Farrel
Date Rejected: 2012-11-26
Section 3.1 says:
For a platform-wide label space, these SHOULD both be zero.
It should say:
For a platform-wide label space, these MUST both be zero.
Notes:
See Section 2.2.2 text, "The last two octets of LDP Identifiers for platform-wide label spaces are always both zero."
--VERIFIER NOTES--
The text in 2.2.2 is descriptive of the LDP identifiers, but not a requirement. The text in 3.1 describes how the LDP identifier is constructed.
The purpose of the "SHOULD" is to direct normal behavior, but not to absolutely require the use of zero in these two octets if a good reason can be found.
Furthermore, there is nothing that would actually prohibit the use of non-zero values. The identifier of a label space is a local matter and another node, seeing a label space identifier, should not make any assumptions about the label space (e.g., it being a global label space or not), nor should it really matter.