Issue 116: Technical Comments

["Sanchez, Mauricio (PNB Roseville)" <mauricio.sanchez@hp.com>]

Dave commented...

> Issue 116: Technical Comments
> Submitter name: David Nelson
> Submitter email address: dnelson@enterasys.com Date first 
> submitted: August 11, 2005
> Reference: http://ops.ietf.org/lists/radiusext/2005/msg00643.html
> Section 2.2
> Text appears to create retroactive normative requirements on 
> existing implementations.
> 
> Requested changes:
> 
> Change:
> 
>       Similarly, if a NAS conforming to this specification receives a 
>       CoA message that contains an attribute from this 
> document that it 
>       does not recognize or cannot apply, it MUST NOT terminate the 
>       session and MUST generate a CoA-NAK packet with 
> ERROR-CAUSE(101) 
>       set to "Unsupported Attribute"(401).  
> 
> To:
> 
>       Similarly, if a NAS conforming to this specification and also
>       conforming to RFC 3576 [RFC3576] receives a CoA message that 
>       contains an attribute from this document that it does not 
>       recognize or cannot apply, it MUST NOT terminate the session and
>       MUST generate a CoA-NAK packet with Error-Cause (101) set to
>       "Unsupported Attribute"(401).  

[ms] Agree.  Document to be changed. 

< Second issue relating to data types has already been closed. >

Cheers,
MS

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