[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:                           
---------------------------------------+------------------------------------
 Section 3.1

       * Provisioning of services is not possible within an
         Access-Reject;

 [BA] This should say "Access-Reject or Disconnect-Request;"

    As noted in [RFC5080] Section 2.6, the intent of an Access-Reject is
    to deny access to the requested service.  As a result, RADIUS does
    not allow the provisioning of services within an Access-Reject.
    Documents which include provisioning of services within an Access-
    Reject are inherently incompatible with RADIUS, and SHOULD be
    redesigned.

 [BA] Recommend adding a paragraph on Disconnect-Request after this one:

    As noted in [RFC5176] Section 3:

    A Disconnect-Request MUST contain only NAS and session identification
    attributes.  If other attributes are included in a Disconnect-
    Request, implementations MUST send a Disconnect-NAK; an Error-Cause
    Attribute with value "Unsupported Attribute" MAY be included.

    As a result, documents which include provisioning of services
    within a Disconnect-Request are inherently incompatible with RADIUS,
    and SHOULD be redesigned.

-- 
Ticket URL: <https://wiki.tools.ietf.org/wg/radext/trac/ticket/55>
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/>