Re: [radext] #55: Disconnect-Request

["radext issue tracker" <trac@tools.ietf.org>]

#55: Disconnect-Request
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@â            |       Owner:  aland@â                  
     Type:  enhancement                |      Status:  new                      
 Priority:  major                      |   Milestone:  milestone1               
Component:  design                     |     Version:  1.0                      
 Severity:  Submitted WG Document      |    Keywords:                           
---------------------------------------+------------------------------------

Comment(by bernard_aboba@â):

 Recommendation is to change the text as follows:

 Change:
     Documents which include provisioning of services within an Access-
     Reject are inherently incompatible with RADIUS, and SHOULD be
     redesigned.

 To:

     Documents which include provisioning of services within an Access-
     Reject or Disconnect-Request are inherently incompatible with RADIUS
     and need to be redesigned.

 for A.4, proposed text is:

     * Provisioning of service in an Access-Reject. Such provisioning is
 not permitted by RFC 2865. If limited access needs to be provided, then an
 Access-Accept with appropriate authorizations can be used instead.

     * Provisioning of service in a Disconnect-Request. Such provisioning
 is not permitted, by RFC 5176. If limited access needs to be provided,
 then a CoA-Request with appropriate authorizations can be used instead.

-- 
Ticket URL: <https://wiki.tools.ietf.org/wg/radext/trac/ticket/55#comment:3>
radext <http://tools.ietf.org/radext/>


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