Issue 204: Review of draft-ietf-radext-delegated-prefix-02

["Bernard Aboba" <[e-mail]>]

Issue 204: Review of draft-ietf-radext-delegated-prefix-02
Submitter name: Bernard Aboba
Submitter email address: [e-mail]
Date first submitted: August 27, 2006
Reference:
Document: draft-ietf-radext-delegated-prefix-02
Comment type: E
Priority: S
Section: Various
Rationale/Explanation of issue:

Section 1

   The Delegated-IPv6-Prefix is a RADIUS attribute [1] that carries an
   IPv6 prefix to be delegated to the user, for use in the user's
   network.  For example, the prefix in a Delegated-IPv6-Prefix
   attribute can be delegated to another node through DHCP Prefix
   Delegation [2].

[BA] Is there another potential use of the Delegated-IPv6-Prefix attribute?
Suggest this be changed to:

   "The Delegated-IPv6-Prefix is a RADIUS attribute [1] that carries an
   IPv6 prefix to be delegated to the user, for use in the user's
   network, via DHCP Prefix Delegation [2]."

--------
   The Framed-IPv6-Prefix attribute [4] serves a similar purpose, but
   may also be used for other purposes other than delegating a prefix
   for use in a user's network.  Definition of the Delegated-IPv6-Prefix
   allows the simultaneous use of the Framed-IPv6-Prefix for other
   purposes and the Delegated-IPv6-Prefix for prefix delegation.

[BA] The Framed-IPv6-Prefix attribute is used to indicate a prefix
that is announced via RS/RA, which is not really a "similar" purpose.
Suggest this be changed to:

   "The Framed-IPv6-Prefix attribute defined in [4] as not designed
   for use in prefix delegation, and therefore Framed-IPv6-Prefix
   and Delegated-IPv6-Prefix attributes may be included in the same
   RADIUS packet."
--------

   The definition of the Delegated-IPv6-Prefix Attribute is based on the
   Framed-IPv6-Prefix attribute [4].

While the attributes are similar in format, they are used for different
purposes.  Suggest that this sentence be deleted.
--------

Section 3

The following table describes which messages the Delegated-IPv6-
   Prefix attribute can appear in and in what quantity.

   +------------------------------------------------------+
   | Request Accept Accounting  #   Attribute             |
   |                Request                               |
   | 0+      0+     0+          TBD Delegated-IPv6-Prefix |
   +------------------------------------------------------+

   In this table 0+ means that zero or more instances of this attribute
   MAY be present in packet.  This attribute MUST NOT appear in any
   packet not listed in the table.

Please use the standard table format from RFC 3162; Attribute Tables
are typically included in a separate section.  Suggest the following:

"4.  Table of Attributes

   The following table provides a guide to which attributes may be found
   in which kinds of packets, and in what quantity.

   Request Accept Reject Challenge Accounting  #  Attribute
   0+      0+     0      0         0+         TBD  Delegated-IPv6-Prefix


   The meaning of the above table entries is as follows:

   0     This attribute MUST NOT be present.
   0+    Zero or more instances of this attribute MAY be present.
   0-1   Zero or one instance of this attribute MAY be present.
   1     Exactly one instance of this attribute MUST be present.
   1+    One or more of these attributes MUST be present."

Section 4

I think you need to include text on the AVP flag rules, along the lines of 
what is
in the Framed-IPv6-Prefix attribute:
                                    +---------------------+
                                    |    AVP Flag rules   |
                                    |----+-----+----+-----|----+
                  AVP               |    |     |SHLD| MUST|    |
  Attribute Name  Code   Value Type |MUST| MAY | NOT|  NOT|Encr|
  ----------------------------------|----+-----+----+-----|----|
  Delegated-IPv6-  97    OctetString| M  |  P  |    |  V  | Y  |
    Prefix                          |    |     |    |     |    |



--
to unsubscribe send a message to [e-mail] with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>