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

RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"

To: "'Alan DeKok'" <aland@deployingradius.com>
Subject: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
From: "David B. Nelson" <dnelson@elbrysnetworks.com>
Date: Thu, 14 Aug 2008 15:47:23 -0400
Cc: <radiusext@ops.ietf.org>
In-reply-to: <48A48634.9030002@deployingradius.com>
Organization: Elbrys Networks, Inc.
References: <Pine.LNX.4.64.0808131905510.24114@internaut.com> <48A3FAA1.1020109@deployingradius.com> <6197C7C240C44878809C5BFD51E7C942@xpsuperdvd2> <48A48634.9030002@deployingradius.com>

> > Yes, we do.  I can cite numerous examples.
> 
>   Where?

Section 7.1 of RFC 2865.  Section 2.1 of RFC 3580.  Section 2.2 of RFC 5176.
Section 2.1.1 of RFC 5080.  Section 6 of RFC 5090.

This is not an exhaustive list, but rather a sampling.



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

References:
- REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
  - From: Bernard Aboba <aboba@internaut.com>
- Re: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
  - From: Alan DeKok <aland@deployingradius.com>
- RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
  - From: "David B. Nelson" <dnelson@elbrysnetworks.com>
- Re: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
  - From: Alan DeKok <aland@deployingradius.com>

Prev by Date: Re: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Next by Date: RE: REMINDER: RADEXT WG Last Call on "Crypto-Agility Requirements for RADIUS"
Previous by thread: Re: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Next by thread: RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"
Index(es):
- Date
- Thread