Issue 188: Delegated Prefix NITs

["Bernard Aboba" <bernard_aboba@hotmail.com>]

Issue 188: Delegated Prefix NITs
Submitter name: Bernard Aboba
Submitter email address: aboba@internaut.com
Date first submitted: April 15, 2006
Reference:
Document: draft-ietf-radext-delegated-prefix-00.txt
Comment type: 'E'ditorial
Priority: S
Section: Various
Rationale/Explanation of issue:

Abstract

"
  The Delegated-IPv6-Prefix attribute indicates an IPv6 prefix that is
  to be delegated to the user."

Might add a bit to the abstract, such as a reference to the RADIUS protocol. 
Suggestion:

"  This document proposes an additional RADIUS (Remote Authentication Dial
  In User Service) attribute for an IPv6 prefix that is to be delegated to 
the user.
  This attribute is usable within either RADIUS or Diameter."

Section 1

"  The Delegated-IPv6-Prefix MAY be used in Access-Accept packets, and
  can appear multiple times.  It MAY be used in an Access-Request
  packet as a hint by the NAS to the server that it would prefer these
  prefix(es), but the server is not required to honor the hint."

This section does not state whether this attribute can be included in
CoA-Request, Disconnect-Request, CoA-ACK, CoA-NAK, Disconnect-ACK
Disconnect-NAK packets and Accounting-Request packets.

Section 3

The attribute table does not clarify whether the attribute can be
included in CoA-Request, Disconnect-Request, CoA-ACK, CoA-NAK,
Disconnect-ACK or Disconnect-NAK packets.

Section 5

"Use of IP SEC [7]" -> "Use of IPsec [7]"

Section 6

I don't think references [4] and [6] are normative.  I'd add an Informative 
Reference
section and move these to that section.  This way you won't have a document
at PS making normative references to Informational RFCs.

I think reference [7] has been replaced by [RFC4301].

Diameter compatibility

The document lacks a "Diameter Considerations" section.  Here is a 
suggestion
(insert prior to IANA Considerations):

4.  Diameter Considerations

  Diameter needs to define an identical attribute with the same Type
  value.  The attribute should be available as part of the NASREQ
  application [RFC4005], as well as the Diameter EAP application
  [RFC4072].

Add references to [RFC4005] and [RFC4072]:

[RFC4005] Calhoun, P., Zorn, G., Spence, D. and D. Mitton, "Diameter
         Network Access Server Application", RFC 4005, August 2005.

[RFC4072] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible
         Authentication Protocol (EAP) Application", RFC 4072, August
         2005.



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