Issue 63: Request-ID Supplementation

[Bernard Aboba <aboba@internaut.com>]

Issue 63: Request-ID Supplementation
Submitter name: David Nelson
Submitter email address: dnelson@enterasys.com
Date first submitted: August 5, 2004
Reference:
http://www.ietf.org/proceedings/04aug/slides/radextt-1/index.html
Document: Issues and Fixes
Comment type: T
Priority: S
Section: Various
Rationale/Explanation of issue:

In RFC 3579, the recommended practices to supplement the Request-ID are
described:

"In EAP, each session has its own unique Identifier space. RADIUS server
implementations  MUST be able to distinguish between EAP packets with the
same Identifier existing within distinct sessions, originating on the
same NAS. For this purpose, sessions can be distinguished based  on NAS
and session identification attributes. NAS identification
attributes include NAS-Identifier, NAS-IPv6-Address and NAS-IPv4-Address.
Session identification attributes include User-Name, NAS-Port,
NAS-Port-Type, NAS-Port-Id,  Called-Station-Id, Calling-Station-Id and
Originating-Line-Info."

This practice applies to other types of RADIUS requests, other than those
involving EAP.

It is commonly a problem on high port density devices.
Is this practice clearly defined?
Is it commonly implemented?
Is it sufficient to address the Request-ID number space "wrap-around"
issue?

[BA] Also see Issue 242 (related issues)

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>