RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Verified (1)

RFC 4852, "IPv6 Enterprise Network Analysis - IP Layer 3 Focus", April 2007

Source of RFC: v6ops (ops)

Errata ID: 1044

Status: Verified
Type: Editorial

Reported By: Alfred Hoenes
Date Reported: 2007-05-08

Section 10.2 says:

   [TSPB]   Blanchet, M., and F. Parent, "IPv6 Tunnel Broker with the
|           Tunnel Setup Protocol (TSP", Work in Progress, August 2005.

It should say:

   [TSPB]   Blanchet, M., and F. Parent, "IPv6 Tunnel Broker with the
|           Tunnel Setup Protocol (TSP)", Work in Progress, August 2005.

Notes:

Matching parenthesis missing.

Status: Held for Document Update (1)

RFC 4852, "IPv6 Enterprise Network Analysis - IP Layer 3 Focus", April 2007

Source of RFC: v6ops (ops)

Errata ID: 1043

Status: Held for Document Update
Type: Editorial

Reported By: Alfred Hoenes
Date Reported: 2007-05-08
Held for Document Update by: Ron Bonica

Section 10.1 says:

  [IPSEC]  Eastlake 3rd, D., "Cryptographic Algorithm Implementation
           Requirements for Encapsulating Security Payload (ESP) and
           Authentication Header (AH)", RFC 4305, December 2005.

It should say:

  [IPSEC]  Kent, S. and K. Seo, "Security Architecture for the
           Internet Protocol", RFC 4301, December 2005.

Notes:

a) RFC 4305 has been obsoleted by RFC 4835, published two weeks
before RFC 4852.

b) The single use of "[IPSEC]" in the text is totally unrelated to
specific cryptographic algorithms and their support in IPsec;
it refers to IPsec in general, as a framework to secure IPv6 ND.

c) The primary reference for IPsec alway should be the latest IPsec
Architecture document, currently RFC 4301, and not a subordinate
document with recommendations for cryptographic algorithm support
like RFC 4305/4835, subject to relatively frequent updates.

Report New Errata



Search RFCs
Advanced Search
×