RE: RFC 3580 Errata Submisssion

["Congdon, Paul T (ProCurve)" <[e-mail]>]

802.1 is concerned with canonical format or non-canonical format because they have to 'sometimes' bridge between two LAN segments that have different representations.  As long as the NAS always uses the same format on every request it should give the desired behavior, though I agree it would eliminate more confusion if it were explicitly stated as needing to be one way or the other since the AAA server is presumably using this value as well.  I don't think collisions are likely.  Doesn't seem like a reason to fix the document.  Most people got this right, or at least checked the document before implementing something else.

Paul

From: [e-mail] [mailto:[e-mail]] On Behalf Of Glen Zorn
Sent: Friday, September 12, 2008 3:19 PM
To: 'Bernard Aboba'; [e-mail]
Subject: RE: RFC 3580 Errata Submisssion

Comments?
A couple:

Why would the "bridge or Access Point MAC address" be conveyed in the Calling-Station-Id Attribute?
The example in the corrected text is incorrect (the '.' should be outside the quotes, not inside).
This Errata seems to be editorial rather than technical to me, since AFAICT the change wouldn't modify the on-wire representation of the Attribute.


________________________________________
From: RFC Errata System [[e-mail]]
Sent: Friday, September 12, 2008 12:54 PM
To: [e-mail]; Bernard Aboba; [e-mail]; [e-mail]; [e-mail]; [e-mail]
Cc: [e-mail]
Subject: [Technical Errata Reported] RFC3580 (1503)

The following errata report has been submitted for RFC3580,
"IEEE 802.1X Remote Authentication Dial In User Service (RADIUS) Usage Guidelines".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=3580&eid=1503

--------------------------------------
Type: Technical
Reported by: Avi Lior <[e-mail]>

Section: 3.21

Original Text
-------------
For IEEE 802.1X Authenticators, this attribute is used to store the
   Supplicant MAC address in ASCII format (upper case only), with octet
   values separated by a "-".  Example: "00-10-A4-23-19-C0".

Corrected Text
--------------
For IEEE Std 802.1X-2001 authenticators, this attribute is used to store the bridge or Access Point MAC
address, represented as an ASCII character string in Canonical format (see IEEE Std 802). For example,
&#147;00-10-A4-23-19-C0.&#148;

Notes
-----
The IETF Informational RFC needed to specify that the representation of the MAC address is in Canonical Format.

This is the case in the IEEE document 802_1x-2001 which is the corrected text provided.

I would be okay if the authors wanted to use Supplicant MAC address instead of "bridge or Access Point" in the proposed corrected text.

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (RFC Editor & Editorial Board)
can log in to change the status and edit the report, if necessary.

--------------------------------------
RFC3580 ( draft-congdon-radius-8021x-29)
--------------------------------------
Title               : IEEE 802.1X Remote Authentication Dial In User Service (RADIUS) Usage Guidelines
Publication Date    : September 2003
Author(s)           : P. Congdon, B. Aboba, A. Smith, G. Zorn, J. Roese
Category            : INFORMATIONAL
Source              : INDEPENDENT
Area                : N/A
Stream              : INDEPENDENT
Verifying Party     : RFC Editor & Editorial Board