[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Proposed Resolution of Issue 234: Attribute Restriction

To: <radiusext@ops.ietf.org>
Subject: RE: Proposed Resolution of Issue 234: Attribute Restriction
From: "David B. Nelson" <dnelson@elbrysnetworks.com>
Date: Mon, 4 Jun 2007 10:58:08 -0400
In-reply-to: <BAY117-W1980EED1E001F0B29508C493210@phx.gbl>
Organization: Elbrys Networks, Inc.
References: <BAY117-W1980EED1E001F0B29508C493210@phx.gbl>

> "This Access-Request SHOULD contain the NAS identification
> attributes from the CoA-Request, as well as the session identification
> attributes from the CoA-Request permitted in an Access-Request; it also
> MAY contain other attributes permitted in an Access-Request."

Looks good.


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

References:
- Proposed Resolution of Issue 234: Attribute Restriction
  - From: Bernard Aboba <bernard_aboba@hotmail.com>

Prev by Date: RE: RFC3576bis and Session State
Next by Date: RE: Issue 238: Identification of multiple sessions
Previous by thread: Proposed Resolution of Issue 234: Attribute Restriction
Next by thread: Determining WG consensus on Issue 226: RFC 3576bis and Renumbering
Index(es):
- Date
- Thread