RE: REMINDER: Review comments on RFC 3576 MIBs (fwd)

["Nagi Reddy Jonnala \(njonnala\)" <njonnala@cisco.com>]

Hi Inderpreet,

Thank you for your comments.

DAC and DAS terminology would still be there but in Bernard suggested
format. Please see the below e-mail thread "RFC 3576bis Comments" for
more comments.

https://psg.com/lists/radiusext/2005/msg00756.html

We'll take care of the typo in the next revision.

Thanks
Nagi.

-----Original Message----- 
From: owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org]
On Behalf Of Bernard Aboba
Sent: Tuesday, September 13, 2005 3:00 AM
To: radiusext@ops.ietf.org
Subject: RE: REMINDER: Review comments on RFC 3576 MIBs (fwd)



---------- Forwarded message ----------
Date: Mon, 12 Sep 2005 11:25:03 -0400
From: Inderpreet Singh <inderpreet.singh@siemens.com>
To: Bernard Aboba <aboba@internaut.com>, radiusext@ops.ietf.org
Subject: RE: REMINDER:  Review comments on RFC 3576 MIBs

I have read the documents and am ok with the contents.

1. Wanted to confirm that the discussion on the terminology DAS and DAC
stands and that there are no changes planned to either the base RFC 3576
or this MIB draft.

2. Page 6 - Section Terminology, para 2 there is a small typo.  On line
3 of para 2, change "itand" to "it and"

Thanks

---
Inderpreet Singh
Chief Architect
Chantry Networks Inc., A Siemens Company inderpreet.singh@siemens.com

-----Original Message-----
From: owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org]
On Behalf Of Bernard Aboba
Sent: Sunday, September 11, 2005 1:32 AM
To: radiusext@ops.ietf.org
Subject: REMINDER: Review comments on RFC 3576 MIBs

So far, the RFC 3576 MIBs have received only 3 comments, from two 
individuals.   This either means that the document is in very good
shape, 
or that hardly anyone has read it.  

In order to advance this document, we need to distinguish these two
outcomes. 

If you have read the documents and believe they are ok, please post this
indication to the RADEXT WG list. 

If you have read the documents and have an issue with them, please post
the issue to the RADEXT WG list in the format described on the RADEXT WG
web page:
http://www.drizzle.com/~aboba/RADEXT/

If you have not read the documents, please do so NOW:
http://www.ietf.org/internet-drafts/draft-ietf-radext-dynauth-client-mib
-01.
txt
http://www.ietf.org/internet-drafts/draft-ietf-radext-dynauth-server-mib
-01.
txt

If we do not hear from anyone, we will assume that there is little or no
interest in implementing this document. 

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

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