RFC Errata
Found 2 records.
Status: Verified (2)
RFC 2868, "RADIUS Attributes for Tunnel Protocol Support", June 2000
Source of RFC: radius (ops)
Errata ID: 2714
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Wang Haojian
Date Reported: 2011-02-12
Verifier Name: Dan Romascanu
Date Verified: 2011-02-28
Section 3.10 says:
3.10. Tunnel-Server-Auth-ID Description This Attribute specifies the name used by the tunnel terminator during the authentication phase of tunnel establishment. The Tunnel-Client-Auth-ID Attribute MAY be included (as a hint to the ^^^^^^^^^^^^^^^^^^^^^
It should say:
3.10. Tunnel-Server-Auth-ID Description This Attribute specifies the name used by the tunnel terminator during the authentication phase of tunnel establishment. The Tunnel-Server-Auth-ID Attribute MAY be included (as a hint to the
Notes:
Maybe here should be the "Tunnel-Server-Auth-ID"
Errata ID: 2716
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Wang Haojian
Date Reported: 2011-02-12
Verifier Name: Dan Romascanu
Date Verified: 2011-02-13
Section 6 says:
6.1. Tunnel-Type Attribute Values Values 1-12 of the Tunnel-Type Attribute are defined in Section 5.1; the remaining values are available for assignment by the IANA with IETF Consensus [16]. 6.2. Tunnel-Medium-Type Attribute Values Values 1-15 of the Tunnel-Medium-Type Attribute are defined in Section 5.2; the remaining values are available for assignment by the IANA with IETF Consensus [16].
It should say:
6.1. Tunnel-Type Attribute Values Values 1-12 of the Tunnel-Type Attribute are defined in Section 3.1; the remaining values are available for assignment by the IANA with IETF Consensus [16]. 6.2. Tunnel-Medium-Type Attribute Values Values 1-15 of the Tunnel-Medium-Type Attribute are defined in Section 3.2; the remaining values are available for assignment by the IANA with IETF Consensus [16].
Notes:
Should be "Section 3.1" and "Section 3.2"