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

Re: IPv6 Address Option

To: Glen Zorn <glenzorn@comcast.net>
Subject: Re: IPv6 Address Option
From: Alan DeKok <aland@deployingradius.com>
Date: Sat, 26 Sep 2009 12:40:17 +0200
Cc: 'MILES DAVID' <David.Miles@alcatel-lucent.com.au>, radiusext@ops.ietf.org, Bernard_Aboba@hotmail.com, d.b.nelson@comcast.net, 'Maglione Roberta' <roberta.maglione@telecomitalia.it>, townsley@cisco.com
In-reply-to: <000301ca3e8f$46331a00$d2994e00$@net>
References: <986DCE2E44129444B6435ABE8C9E424D02DC1328@SGSINSMBS02.ad4.ad.alcatel.com> <4ABDBFE5.4050406@deployingradius.com> <000301ca3e8f$46331a00$d2994e00$@net>
User-agent: Thunderbird 2.0.0.23 (Macintosh/20090812)

Glen Zorn wrote:
> ... but draft-ietf-radext-design-08, section 2.1.2 says (talking about
> the tagging mechanism defined in RFC 2868) "New attributes SHOULD NOT use
> this tagging method...".  Which is it?  

  I suggest racing against the design guidelines document.  After all,
it's only a draft.  If the IPv6 document can get published first, then
the design guidelines matter a lot less.

  Alan DeKok.

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

Follow-Ups:
- RE: IPv6 Address Option
  - From: "Glen Zorn" <glenzorn@comcast.net>

References:
- IPv6 Address Option
  - From: "MILES DAVID" <David.Miles@alcatel-lucent.com.au>
- Re: IPv6 Address Option
  - From: Alan DeKok <aland@deployingradius.com>
- RE: IPv6 Address Option
  - From: "Glen Zorn" <glenzorn@comcast.net>

Prev by Date: RE: IPv6 Address Option
Next by Date: Re: IPv6 Address Option
Previous by thread: Re: IPv6 Address Option
Next by thread: RE: IPv6 Address Option
Index(es):
- Date
- Thread