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

Re: RADEXT WG Last Call: "RADIUS attributes for IPv6 Access Networks" (2nd round)

To: "Sanchez, Mauricio (HP Networking)" <mauricio.sanchez@hp.com>
Subject: Re: RADEXT WG Last Call: "RADIUS attributes for IPv6 Access Networks" (2nd round)
From: Peter Deacon <peterd@iea-software.com>
Date: Thu, 13 Jan 2011 10:13:12 -0800 (Pacific Standard Time)
Cc: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
In-reply-to: <9BC2F7926B33FE4AB10D69891D58FC1C5B4F9B8194@GVW0671EXC.americas.hpqcorp.net>
References: <9BC2F7926B33FE4AB10D69891D58FC1C5B4F9B8194@GVW0671EXC.americas.hpqcorp.net>
User-agent: Alpine 2.00 (WNT 1167 2008-08-23)

On Thu, 13 Jan 2011, Sanchez, Mauricio (HP Networking) wrote:

This is an announcement of RADEXT WG second last call on "RADIUS attributes for
IPv6 Access Networks", prior to sending the document to the IESG for publication
as a proposed standard RFC.   The first last call did not garner any comments,
whether positive or negative.  If you read the draft and have no issues, please
state this as so on the mailing list.


Looks good, noticed one minor problem.

In 3.3 description the reserved field is missing.

Recommend adding (RFC3162 text)

Reserved
This field, which is reserved and MUST be present, is always set to zero

regards,
Peter

References:
- RADEXT WG Last Call: "RADIUS attributes for IPv6 Access Networks" (2nd round)
  - From: "Sanchez, Mauricio (HP Networking)" <mauricio.sanchez@hp.com>

Prev by Date: Re: RADEXT WG Last Call: "RADIUS attributes for IPv6 Access Networks" (2nd round)
Next by Date: FW: Informational RFC to be: <draft-zorn-radius-keywrap-18.txt>
Previous by thread: Re: RADEXT WG Last Call: "RADIUS attributes for IPv6 Access Networks" (2nd round)
Next by thread: [radext] ipv6-access #61 (new): DNS attribute for IPv4?
Index(es):
- Date
- Thread