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

RE: IPv6 Address Option

To: "'Alan DeKok'" <aland@deployingradius.com>
Subject: RE: IPv6 Address Option
From: "Glen Zorn" <glenzorn@comcast.net>
Date: Sat, 26 Sep 2009 20:09:11 +0700
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: <4ABDF224.9070307@deployingradius.com>
References: <986DCE2E44129444B6435ABE8C9E424D02DC1328@SGSINSMBS02.ad4.ad.alcatel.com> <4ABDBFE5.4050406@deployingradius.com> <000301ca3e8f$46331a00$d2994e00$@net> <000401ca3e91$6b916070$42b42150$@net> <4ABDF224.9070307@deployingradius.com>

Alan DeKok [mailto:aland@deployingradius.com] writes:

> Glen Zorn wrote:
> > Even more interestingly, your latest missive seems to strongly imply
> that
> > adopting the RADIUS Design (Mis-)Guidelines will be a "significant
> barrier
> > to adoption" of new attributes designed following them...
> 
>   Perhaps there's an IETF process to obtain WG consensus and update
> published documents?

What do you mean?



--
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: Alan DeKok <aland@deployingradius.com>

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>
- RE: IPv6 Address Option
  - From: "Glen Zorn" <glenzorn@comcast.net>
- Re: IPv6 Address Option
  - From: Alan DeKok <aland@deployingradius.com>

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