RFC Errata
Found 4 records.
Status: Verified (4)
RFC 4877, "Mobile IPv6 Operation with IKEv2 and the Revised IPsec Architecture", April 2007
Source of RFC: mip6 (int)
Errata ID: 910
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2007-04-16
Verifier Name: RFC Editor
Date Verified: 2007-11-02
Section 3 says:
The packet formats for tunneled mobile prefix discovery messages are very similar to the tunneled Binding Update and Binding Acknowledgment with the with the home address as the source address in the inner IP header.
It should say:
The packet formats for tunneled mobile prefix discovery messages are very similar to the tunneled Binding Update and Binding Acknowledgment with the home address as the source address in the inner IP header.
Notes:
from pending
Errata ID: 911
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2007-04-16
Verifier Name: RFC Editor
Date Verified: 2007-11-02
Section 4.2 says:
o The home agent MUST use the Type 2 Routing header in Binding Acknowledgements and Mobile Prefix Advertisements sent to the mobile node when transport mode IPsec protection is used, again due to the need to have the home address visible when the policy checks are made.
It should say:
o The home agent MUST use the Type 2 Routing header in Binding Acknowledgements and Mobile Prefix Advertisements sent to the mobile node when transport mode IPsec protection is used, again due to the need to have the home address be visible when the policy checks are made.
Notes:
omission of verb
from pending
Errata ID: 912
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2007-04-16
Verifier Name: RFC Editor
Date Verified: 2007-11-02
Section 4.3 says:
[...]. The use of sequence number in the ESP header to provide anti-replay protection is optional because the sequence numbers in the Binding Updates provide anti-replay protection.
It should say:
[...]. The use of the sequence number in the ESP header to provide anti-replay protection is optional because the sequence numbers in the Binding Updates provide anti-replay protection.
Notes:
missing article
from pending
Errata ID: 913
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2007-04-16
Verifier Name: RFC Editor
Date Verified: 2007-11-02
Section 5 says:
[...]. This case uses IPsec tunnel mode SA with the protocol selector set to 'any'.
It should say:
[...]. This case uses IPsec tunnel mode SAs with the protocol selector set to 'any'.
Notes:
SA --> SAs
from pending