|
|
|
Found 4 records.
Errata ID: 1627
Status: Held for Document Update
Type: Editorial
Reported By: Yelland Mr Michael
Date Reported: 2007-03-02
Held for Document Update by: RFC Editor
Date Held: 2008-12-03
Section 2.7 says:
Routers must not forward any multicast packets beyond of the scope indicated by the scop field in the destination multicast address.
It should say:
Routers must not forward any multicast packets beyond the scope indicated by the scop field in the destination multicast address.
Notes:
extraneous "of"
Errata ID: 863
Status: Rejected
Type: Editorial
Reported By: Yelland Mr Michael
Date Reported: 2007-03-02
Rejected by: RFC Editor
Date Rejected: 2008-12-03
Section 2.7 says:
Nodes must not originate a packet to a multicast address whose scop field contains the reserved value 0; if such a packet is received, it must be silently dropped. Nodes should not originate a packet to a multicast address whose scop field contains the reserved value F; ...
It should say:
Nodes must not originate a packet to a multicast address whose scope field contains the reserved value 0; if such a packet is received, it must be silently dropped. Nodes should not originate a packet to a multicast address whose scope field contains the reserved value F; ...
Notes:
Typo: scop --> scope (2 times)
-- RATIONALE FOR REJECTION --
This isn't a typo. The field is named "scop". See Section 2.7:
scop is a 4-bit multicast scope value used to limit the scope of
the multicast group.
Thanks to Bob Hinden for pointing this out.
This report was incorrectly marked "Verified" from 2007-11-01 to 2008-12-03.
Errata ID: 864
Status: Rejected
Type: Editorial
Reported By: Yelland Mr Michael
Date Reported: 2007-03-02
Rejected by: RFC Editor
Date Rejected: 2008-12-03
Section 2.7 says:
Routers must not forward any multicast packets beyond of the scope indicated by the scop field in the destination multicast address.
It should say:
Routers must not forward any multicast packets beyond the scope indicated by the scope field in the destination multicast address.
Notes:
Typo: scop --> scope; extraneous "of"
-- RATIONALE FOR REJECTION --
This isn't a typo. The field is named "scop". See Section 2.7:
scop is a 4-bit multicast scope value used to limit the scope of
the multicast group.
Thanks to Bob Hinden for pointing this out.
This report was incorrectly marked "Verified" from 2007-11-01 to 2008-12-03.
[There is an extraneous "of", which has been listed in a separate report: Errata ID 1627.]
Errata ID: 865
Status: Rejected
Type: Editorial
Reported By: Yelland Mr Michael
Date Reported: 2007-03-02
Rejected by: RFC Editor
Date Rejected: 2007-12-03
Section 2.7 says:
Nodes must not originate a packet to a multicast address whose scop field contains the reserved value 0; if such a packet is received, it must be silently dropped. Nodes should not originate a packet to a multicast address whose scop field contains the reserved value F; ...
It should say:
Nodes must not originate a packet to a multicast address whose scope field contains the reserved value 0; if such a packet is received, it must be silently dropped. Nodes should not originate a packet to a multicast address whose scope field contains the reserved value F; ...
Notes:
Typo: scop --> scope (2 times)
-- RATIONALE FOR REJECTION --
This isn't a typo. The field is named "scop". See Section 2.7:
scop is a 4-bit multicast scope value used to limit the scope of
the multicast group.
Thanks to Bob Hinden for pointing this out.
This report was incorrectly marked "Verified" from 2007-11-01 to 2008-12-03.