[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: comments on draft-maglione-radext-ipv6-acct-extensions-01

Thanks for your comments.
Please see answers inline.
Regards,
Robert

-----Original Message-----
From: Glen Zorn [mailto:gwz@net-zen.net]
Sent: Tuesday, March 09, 2010 6:14 AM
To: Maglione Roberta; suresh.krishnan@ericsson.com; alan.kavanagh@ericsson.com; varga.balazs@telekom.hu; jkaippal@huawei.com
Cc: 'Glen Zorn'; ietf@ietf.org
Subject: comments on draft-maglione-radext-ipv6-acct-extensions-01

Not sure why this is Standards Track since both RFC 2866 & RFC 2869 are
Informational.
[RM] ok we can change to Informational.

It would be more in-line w/RADIUS tradition to name the Attributes
Acct-IPv6-* rather than IPv6-Acct-*.

[RM] ok fine.

References are pointers to objects, not the objects themselves.  Suggest
changing all instances of constructs like "[RFC2866]and [RFC2869] specify"
to "RFC 2866 [RFC2866] and RFC 2869 [RFC2869] specify" or simply rewriting
the sentences so that the use of pointers makes sense, in this case perhaps
to "Existing documents (RFC2866], [RFC2869]) specify".

[RM] ok we will re-phrase it.

TYPO: s/the IPv6 in broadband environment/IPv6 in broadband environments/ in
the Introduction.
TYPO: s/new RADIUS attribute have to be defined/new RADIUS attributes have
to be defined/ in the Introduction
[RM] ok we will correct these typos

The second paragraph of the Introduction says "This document describes
additional RADIUS attributes for collecting IPv6 specific statistics in
RADIUS Accounting messages"; suggest changing to "This document describes
additional RADIUS attributes for transporting IPv6-specific statistics in
RADIUS Accounting messages".

[RM] ok thanks for the suggestions we will re-phrase this sentence

Section 3, second paragraph says:
   Existing RADIUS attributes like Acct-Input-Octets, Acct-Output-
   Octets, Acct-Input-Packets, Acct-Output-Packets, Acct-Input-Gigawords
   and Acct-Output-Gigawords, could be used to collect statistics for
   all traffic(including IPv4, IPv6 and other protocols), while the
   availability of IPv6 specific RADIUS attributes would allow the
   collection of IPv6 statistics.
Suggest changing to:
   Existing RADIUS attributes like Acct-Input-Octets, Acct-Output-
   Octets, Acct-Input-Packets, Acct-Output-Packets, Acct-Input-Gigawords
   and Acct-Output-Gigawords, could be used to collect statistics for
   all traffic (including IPv4, IPv6 and other protocols), while the
   availability of IPv6-specific RADIUS attributes would allow the
   collection of IPv6 statistics.

[RM] ok

It's not at all clear to me why the first paragraph of section 4.1 exists.

The second paragraph of Section 4.1 says:
   If the Accounting-Request packet includes a Framed-IPv6-Prefix, that
   attribute MUST contain the IPv6 prefix allocated to the user.  In
   deployment scenarios where DHCPv6 prefix delegation is used, the
   Accounting-Request packet will contain a Delegated-IPv6-Prefix
   attribute that contains the IPv6 prefix delegated to the user.
The first sentence just repeats what RFC 3162 says about the
Framed-IPv6-Prefix Attribute.  This seems unnecessary.  The second sentence
says that "the Accounting-Request packet will contain a
Delegated-IPv6-Prefix attribute" but RFC 4818 doesn't say this.  As one may
have guessed, I would prefer that section 4 be deleted altogether, but if
the authors feel it necessary for it to be included, I suggest modifying it
to at least be accurate and to include references to RFC 3962 and RFC 4818.

[RM] I may need to re-discuss this point with the other co-authors, we will get back to you on this

In sections 5.*, a blank line should be added before "Length" in the
Attribute summaries.
[RM] ok

In Section 7, an allocation policy must be specified; suggest just adding a
reference to RFC 3575.

[RM] ok.



Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.


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