RFC Errata
Found 2 records.
Status: Verified (2)
RFC 3964, "Security Considerations for 6to4", December 2004
Source of RFC: v6ops (ops)
Errata ID: 873
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Peter Su
Date Reported: 2007-03-26
Verifier Name: Pekka Savola
Date Verified: 2007-03-26
Section 4.1.3 says:
src_v6 = 2002:1234:1234::1 (forged address of the target 6to4 node) dst_v6 = 2002:0900:0002::1 (valid address) src_v4 = 8.0.0.1 (valid or invalid address) dst_v4 = 9.0.0.2 (valid address, matches dst_v6)
It should say:
src_v6 = 2002:1234:1234::1 (forged address of the target 6to4 node) dst_v6 = 2001:db8::1 (valid address) src_v4 = 8.0.0.1 (valid or invalid address)
Notes:
copy/paste error. Traffic is sent to the native IPv6 node, so the
destination address should be non-2002::/16. When 6to4 is not used,
dst_v4 is not applicable so it could be removed.
from pending
Errata ID: 874
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Peter Su
Date Reported: 2007-03-26
Verifier Name: Pekka Savola
Date Verified: 2007-03-26
Section 4.2.5 says:
The policy control is usually enacted by applying restrictions to where the routing information for 2002::/16 and/or 192.188.99.0/24 (if the anycast address used [3]) will spread.
It should say:
The policy control is usually enacted by applying restrictions to where the routing information for 2002::/16 and/or 192.88.99.0/24 (if the anycast address used [3]) will spread.
Notes:
typo in the anycast address.
from pending