[Issue] multiple source addresses

["Greg Weber \(gdweber\)" <gdweber@cisco.com>]

Description of issue: Multiple NAS address options
Submitter name: Greg Weber
Submitter email address: gdweber@cisco.com
Date first submitted: 1/9/06
Reference: n/a
Document: draft-aboba-radext-fixes-01.txt
Comment type: T/E
Priority: 1
Section: 2.7.2
Rationale/Explanation of issue:

Regarding this text:
   There are situations in which a RADIUS client or server may have
   multiple addresses.  For example, a dual stack host can have both
   IPv4 and IPv6 addresses; a host that is a member of multiple VLANs
   could have IPv4 and/or IPv6 addresses on each VLAN; a host can have
   multiple IPv4 or IPv6 addresses on a single interface.  However,
   [RFC2865] Section 5.44 only  permits zero or one NAS-IPv4-Address
   attributes within an Access-Request and [RFC3162] Section 3 only
   permits zero or one NAS-IPv6-Address attributes within an Access-
   Request.  Where a NAS has more than one global address, it is
   RECOMMENDED that the NAS include the NAS-Identifier attribute in an
   Access-Request in order to identify itself to the RADIUS server.

More typically, this situation has been addressed by allowing the NAS 
RADIUS client implementation to specify which address should be used 
(either globally or perhaps based on additional information about the
type of request).  

Requested change:
Can we change the condition on the RECOMMENDATION to something
like 'When a NAS has more than one global address and no ability
to determine which is used for identification in a particular 
request, ...'.

Also, can you change:
  "NAS-IPv4-Address" -> "NAS-IP-Address" and
  "Account-Session-ID" -> "Acct-Session-Id" in the doc.

--
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/>