RE: Last Look at RFC 2618bis, 2619bis

"Nelson, David" <dnelson@enterasys.com> Mon, 23 January 2006 15:55 UTC

Envelope-to: radiusext-data@psg.com
Delivery-date: Mon, 23 Jan 2006 15:56:23 +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: Last Look at RFC 2618bis, 2619bis
Date: Mon, 23 Jan 2006 10:55:49 -0500
Message-ID: <3CFB564E055A594B82C4FE89D215656006B7CE@MABOSEVS2.ets.enterasys.com>
Thread-Topic: Last Look at RFC 2618bis, 2619bis
Thread-Index: AcYflKhLA6ztI2rWQ4SjAlJP/fvi6gAoGHuw
From: "Nelson, David" <dnelson@enterasys.com>
To: radiusext@ops.ietf.org

> New versions of RFC 2618bis and 26819bis have been posted to the
archive:
> 
>
http://www.ietf.org/internet-drafts/draft-ietf-radext-rfc2618bis-02.txt
>
http://www.ietf.org/internet-drafts/draft-ietf-radext-rfc2619bis-02.txt
> 
> Please review these documents for resolution of the RADEXT WG last
call
> issues and post comments to the RADEXT WG mailing list by Monday,
January
> 30, 2006.

Please note that Issue 146 (incorrect counter arithmetic) has not been
addressed.  The WG discussion of this issue did not yield a consensus
that I could detect.  Additionally, since this issue exists in widely
deployed MIBs, it may be better to deal this Issue 146 in the RADIUS
Issues and Fixes Draft.


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