[radext] #28: Section 1.2

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

#28: Section 1.2
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@â            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  critical                   |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 We emphasize that the uses of "MUST" and "MUST NOT" in this document
    are limited to requirements to follow the IETF process for IETF
    standards, and quotes from other documents.  As a result, the uses of
    "MUST" and "MUST NOT" in this document do not prescribe new mandatory
    behavior within implementations.

 [BA] Since elements of this paragraph have been incorporated into the
 proposed text of Section 1.3, it can be deleted.  Note that RFC 2119
 Section 6 appears restricts usage of "MUST" and "MUST NOT":

    We emphasize that the uses of "MUST" and "MUST NOT" in this document
    are limited to requirements to follow the IETF process for IETF
    standards, and quotes from other documents.  As a result, the uses of
    "MUST" and "MUST NOT" in this document do not prescribe new mandatory
    behavior within implementations.

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