[radext] #39: Section 4

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

#39: Section 4
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@â            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  minor                      |   Milestone:  milestone1
Component:  design                     |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------
 4. IANA Considerations

    This document does not require that the IANA update any existing
    registry or create any new registry, but includes information that
    affects the IANA, which:

       * includes specific guidelines for Expert Reviewers appointed
         under the IANA considerations of [RFC3575]

       * includes guidelines that recommend against self allocation from
         the RADIUS standard attribute space in other SDO RADIUS
         Attribute specifications.

       * recommends that SDOs request a Private Enterprise Code (PEC)
         from the IANA, for use as a Vendor-Id within a Vendor-Specific
         attribute.

 [BA] BCPs cannot update standards track documents such as RFC 2865 or
 3575. This should be made more clear.  Recommended change:

 4. IANA Considerations

    This document has no action items for IANA.  However, it does provide
 guidelines for Expert Reviewers appointed as described in [RFC3575].

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