IETF Logo Mail Archive

RE: Review of draft-ietf-radext-vlan-02.txt

"Nelson, David" <dnelson@enterasys.com> Wed, 19 April 2006 17:09 UTC

Envelope-to: radiusext-data@psg.com
Delivery-date: Wed, 19 Apr 2006 17:09:52 +0000
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Review of draft-ietf-radext-vlan-02.txt
Date: Wed, 19 Apr 2006 13:09:24 -0400
Message-ID: <3CFB564E055A594B82C4FE89D21565602191EE@MABOSEVS2.ets.enterasys.com>
Thread-Topic: Review of draft-ietf-radext-vlan-02.txt
Thread-Index: AcZj0DMm0X1QaY70RJepgxB8r8M7CQAA2Ynw
From: "Nelson, David" <dnelson@enterasys.com>
To: radiusext@ops.ietf.org

Bernard Aboba writes...

> >as listed in the references section, do not
> 
> I think we are only talking about IEEE 802.1Q, right?  IEEE 802 and
IEEE
> 802.1D do not deal with this issue.

IEEE 802.1X also.

> If it is only one or two standards, I'd
> prefer to refer to them explicitly.

Sure.  My intent was to replace the "currently", which would not fly in
an RFC, with references to specific versions of the standards.


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

v2.23.0 | Report a Bug | By Email