RE: REMINDER: RADEXT WG review of draft-nelson-radius-management-authorization

"Avi Lior" <avi@bridgewatersystems.com> Sat, 18 August 2007 13:17 UTC

Envelope-to: radiusext-data@psg.com
Delivery-date: Sat, 18 Aug 2007 13:18:02 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: REMINDER: RADEXT WG review of draft-nelson-radius-management-authorization
Date: Sat, 18 Aug 2007 09:17:03 -0400
Message-ID: <E7CCE8A83907104ABEE91AC3AE3709A00F09504B@exchange.bridgewatersys.com>
From: Avi Lior <avi@bridgewatersystems.com>
To: Bernard Aboba <bernard_aboba@hotmail.com>, radiusext@ops.ietf.org

I have read through the document and I support it becoming a WG item.

Thanx. 

-----Original Message-----
From: owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org]
On Behalf Of Bernard Aboba
Sent: Tuesday, August 14, 2007 10:32 AM
To: radiusext@ops.ietf.org
Subject: REMINDER: RADEXT WG review of
draft-nelson-radius-management-authorization

The WG review request ends on August 16, 2007.  So far we have had only
person express interest - not enough to adopt this document as a WG work
item.  Please post to the list if you support taking this on as a WG
work item (even if you have no comments to post).


>From: "Wijnen, Bert (Bert)" <bwijnen@alcatel-lucent.com>
>To: <dnelson@enterasys.com>, <gdweber@cisco.com>
>CC: <j.schoenwaelder@jacobs-university.de>,        "Bernard Aboba" 
><bernard_aboba@hotmail.com>
>Subject: RE: [Isms] [bernard_aboba@hotmail.com: Review o 
>fdraft-nelson-radius-management-authorization-05.txt]
>Date: Tue, 14 Aug 2007 11:35:43 +0200
>
>Some nits:
>
>Sect 4
>
>    The local application of the Management-Policy-Id within the
managed
>    entity may take the form of (a) one of an enumeration of command
>    privilege levels, (b) a mapping into an SNMP View Based Access
>    Control Method (VACM) table [RFC3415], or (c) some other set of
>
>Did you intend to writhe "Method", or do you mean "Model"?
>VACM stands for View Based Access Control Model in the SNMP context.
>
>Sect 7.3
>    The Text field is one or more octets, and its contents are
>    implementation dependent.  It is intended to be human readable and
>    MUST NOT affect operation of the protocol.  It is recommended that
>    the message contain UTF-8 encoded 10646 [RFC2279] characters.
>
>The latest RFC for UTF-8 is RFC3629.
>I guess it is better reference that one.
>
>I can support this work item as a topic for the RADEXT WG.
>Not sure how much I can contribute though, but I will try to review 
>revisions of the document
>
>Bert Wijnen



--

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

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