RFC Errata
Found 5 records.
Status: Verified (4)
RFC 4591, "Frame Relay over Layer 2 Tunneling Protocol Version 3 (L2TPv3)", August 2006
Note: This RFC has been updated by RFC 5641
Source of RFC: l2tpext (int)
Errata ID: 735
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2006-08-11
Verifier Name: Brian Haberman
Date Verified: 2012-05-10
Section 4.3 says:
With L2TPv3 as the tunneling protocol, the packet resulted from the encapsulation is N bytes longer than Frame Relay frame without the opening and closing HDLC flags or FCS. The value of N depends on the following fields:
It should say:
With L2TPv3 as the tunneling protocol, the packet resulting from the encapsulation is N bytes longer than the Frame Relay frame without the opening and closing HDLC flags or FCS. The value of N depends on the following fields:
Errata ID: 3223
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2006-08-11
Verifier Name: Brian Haberman
Date Verified: 2012-05-10
Section 3.2 says:
General Result Codes regarding L2TP session establishment are defined
in [RFC3931]. Additional Frame Relay result codes are defined as
follows:
17: FR PVC was deleted permanently (no longer provisioned) 18: FR
PVC has been INACTIVE for an extended period of time 19:
Mismatched FR Header Length
It should say:
General Result Codes regarding L2TP session establishment are defined
in [RFC3931]. Additional Frame Relay result codes are defined as
follows:
17: FR PVC was deleted permanently (no longer provisioned)
18: FR PVC has been INACTIVE for an extended period of time
19: Mismatched FR Header Length
Errata ID: 3224
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2006-08-11
Verifier Name: Brian Haberman
Date Verified: 2012-05-10
Section 3.5 says:
The Frame Relay Header Length Type is a 2-octet unsigned integer with
the following values defined in this document:
2: Two-octet Frame Relay Header 4: Four-octet Frame Relay Header
It should say:
The Frame Relay Header Length Type is a 2-octet unsigned integer with
the following values defined in this document:
2: Two-octet Frame Relay Header
4: Four-octet Frame Relay Header
Errata ID: 3225
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2006-08-11
Verifier Name: Brian Haberman
Date Verified: 2012-05-10
Section 4.1 says:
C/R (bit 6) FR frame C/R (command/response) bit [Q922]. F - FECN (bit 12): FR FECN (Forward Explicit Congestion Notification) bit [Q922]. B - BECN (bit 13): FR BECN (Backward Explicit Congestion Notification) bit [Q922]. D - DE (bit 14) FR DE bit indicates the discard eligibility [Q922].
It should say:
C (bit 6): FR frame C/R (command/response) bit [Q922].
F (bit 12): FR FECN (Forward Explicit Congestion Notification)
bit [Q922].
B (bit 13): FR BECN (Backward Explicit Congestion Notification)
bit [Q922].
D (bit 14): FR DE bit indicates the discard eligibility [Q922].
Notes:
The "full bit names" have been removed from the left hand sides
(corresponding to the diagrams), and replaced "C/R" by "C", because
these "full bit names" do not appear in the diagrams, but already do
appear in the explanatory text on the right hand side. Thus, to the
left of the colons, there now are only -- and precisely -- the terms
from the diagrams.
Status: Rejected (1)
RFC 4591, "Frame Relay over Layer 2 Tunneling Protocol Version 3 (L2TPv3)", August 2006
Note: This RFC has been updated by RFC 5641
Source of RFC: l2tpext (int)
Errata ID: 3222
Status: Rejected
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2006-08-11
Rejected by: Brian Haberman
Date Rejected: 2012-05-10
(1) [line folding issue]
The final part of Section 3.2, on page 5 of RFC 4591, syas:
General Result Codes regarding L2TP session establishment are defined
in [RFC3931]. Additional Frame Relay result codes are defined as
follows:
17: FR PVC was deleted permanently (no longer provisioned) 18: FR
PVC has been INACTIVE for an extended period of time 19:
Mismatched FR Header Length
For clarity, the RFC sould say instead:
General Result Codes regarding L2TP session establishment are defined
in [RFC3931]. Additional Frame Relay result codes are defined as
follows:
| 17: FR PVC was deleted permanently (no longer provisioned)
| 18: FR PVC has been INACTIVE for an extended period of time
| 19: Mismatched FR Header Length
(2) [another line folding issue]
Within Section 3.5, on page 7, the RFC text just below the diagram
says:
The Frame Relay Header Length Type is a 2-octet unsigned integer with
the following values defined in this document:
2: Two-octet Frame Relay Header 4: Four-octet Frame Relay Header
For clarity, the RFC sould say instead:
The Frame Relay Header Length Type is a 2-octet unsigned integer with
the following values defined in this document:
| 2: Two-octet Frame Relay Header
| 4: Four-octet Frame Relay Header
(3) [missing colons, and formatting]
In Section 4.1, the explanations just below the FR Header diagrams
on page 8 of the RFC read:
C/R (bit 6) FR frame C/R (command/response) bit [Q922].
F - FECN (bit 12): FR FECN (Forward Explicit Congestion
Notification) bit [Q922].
B - BECN (bit 13):
|
FR BECN (Backward Explicit Congestion Notification) bit [Q922].
D - DE (bit 14) FR DE bit indicates the discard eligibility [Q922].
For clarity, it should better say:
vvvvv
| C (bit 6): FR frame C/R (command/response) bit [Q922].
| F (bit 12): FR FECN (Forward Explicit Congestion Notification)
| bit [Q922].
| B (bit 13): FR BECN (Backward Explicit Congestion Notification)
| bit [Q922].
| D (bit 14): FR DE bit indicates the discard eligibility [Q922].
^^^^
[ Additional rationale for the proposed clarifications:
The "full bit names" have been removed from the left hand sides
(corresponding to the diagrams), and replaced "C/R" by "C", because
these "full bit names" do not appear in the diagrams, but already do
appear in the explanatory text on the right hand side. Thus, to the
left of the colons, there now are only -- and precisely -- the terms
from the diagrams. ]
(4) [typo + word omission]
The first paragraph of Section 4.3, on page 9, says:
vv
With L2TPv3 as the tunneling protocol, the packet resulted from the
encapsulation is N bytes longer than Frame Relay frame without the
opening and closing HDLC flags or FCS. The value of N depends on the
following fields:
It should say:
vvv
| With L2TPv3 as the tunneling protocol, the packet resulting from the
| encapsulation is N bytes longer than the Frame Relay frame without
the opening and closing HDLC flags or FCS. The value of N depends on
the following fields:
It should say:
[see above]
Notes:
from pending
--VERIFIER NOTES--
Extraneous duplicate of errata 735