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

RE: Proposed Resolution to Issue 178: Allowing Hints in Request Messages



This is satisfactory and issue can be closed once document is updated.

MS 

> -----Original Message-----
> From: owner-radiusext@ops.ietf.org 
> [mailto:owner-radiusext@ops.ietf.org] On Behalf Of Bernard Aboba
> Sent: Thursday, March 16, 2006 10:06 AM
> To: radiusext@ops.ietf.org
> Subject: Proposed Resolution to Issue 178: Allowing Hints in 
> Request Messages
> 
> The text of Issue 178 is enclosed below.  The proposed 
> resolution is to accept the changes.
> 
> --------------------------------------------------------------
> ------------------------------------------------------------------
> Issue 178: Allowing Hints in Request Messages Submitter name: 
> Mauricio Sanchez Submitter email address: 
> mauricio.sanchez@hp.com Date first submitted: March 6, 2006
> Reference: http://ops.ietf.org/lists/radiusext/2006/msg00225.html
> Document: draft-ietf-radext-vlan-00.txt
> Comment type: T
> Priority: 2
> Section: Table in section 3, individual attributes 
> Rationale/Explanation of issue:
> Draft-ietf-radext-vlan-00 does not allow the new attributes 
> to be sent in ACCESS-REQUEST messages.  If allowed, 
> attributes in the REQUEST message could serve as 'hints' to 
> the RADIUS server during the decision making process.
> Requested change:  Allow attributes to be sent ACCESS-REQUEST 
> message Proposed changes to the document.
> 
> - Descriptions of individual attribute descriptions would be 
> changed to allow attributes in access request, as follows:
> Multiple <attr_name> attributes MAY be included in an 
> Access-Request, Access-Accept or CoA-Request packet; this 
> attribute MUST NOT be sent within an Access-Challenge, 
> Access-Reject, Disconnect-Request, Disconnect-ACK, 
> Disconnect-NAK, CoA-ACK, or CoA-NAK.
> 
> -Table in section 3 would be changed to:
> 
>    Access-   Access-  Access-  Access-    CoA-
>    Request   Accept   Reject   Challenge  Req     #    Attribute
>        0+      0+       0        0        0+    TBD  Egress-VLANID
>        0-1     0-1      0        0        0-1   TBD  Ingress-Filters
>        0+      0+       0        0        0+    TBD  Egress-VLAN-Name
>        0-1     0-1      0        0        0-1   TBD  
> User-Priority-Table
> 
> 
> 
> --
> 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/>
> 

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