[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Issue 226: RFC 3576bis and Renumbering
> I think we'd be better off just making Acct-Session-Id a MUST, and
> ignoring the other attributes.
Making Acct-Session-Id a MUST would ensure Diameter compatibility.
User-Name probably needs to be at least a MAY for the same reason.
I would agree that the other attributes are of dubious utility.
For example, where the IP address isn't assigned by the NAS
(e.g. L2 access device) neither the RADIUS server nor the NAS
may know the IP address associated with the session. In this case
it doesn't make sense to send a CoA-Request with IP address session
identification attributes.
Even if the NAS does assign the IP address (e.g. PPP), PPP peers typically
cannot renegotiate IPCP in mid-stream, so that a request to change the
IP address in mid-session cannot be carried out. About the only address
change attribute that makes sense is Framed-IPv6-Prefix, since a changed
Framed-IPv6-Prefix can result in a changed RA.
However, in -04 this has to be done in two steps since Framed-IPv6-Prefix
and Framed-Interface-Id are reserved for session identification.
So it makes sense to remove the IP address session identification attributes
and allowing Framed-IPv6-Prefix to be included in a CoA-Request.
Similarly, I struggle to understand the use of Called/Calling-Station-Id as
session identification attributes. As you note, a RADIUS server would
have the mapping between Called/Calling-Station-Id and Acct-Session-Id,
so there is no need to ask the NAS to do the work itself.
So my inclination would be to cull the list to the following:
Attribute # Reference Description
--------- --- --------- -----------
User-Name 1 [RFC2865] The name of the user
associated with the session.
Acct-Session-Id 44 [RFC2866] The identifier uniquely
identifying the session
on the NAS.