RE: RFC 3576bis Comments

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

Thank you for your comments. We'll incorporate these changes in the next
revision.  

Does the WG have any more issues reg. terminology confusion?

Thanks
Nagi.

-----Original Message-----
From: owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org]
On Behalf Of Bernard Aboba
Sent: Saturday, September 03, 2005 4:58 PM
To: radiusext@ops.ietf.org
Subject: Re: RFC 3576bis Comments

Some additional comments on references.  These documents do not include
a normative reference to RFC 4001, but probably should:

   [RFC4001]  Daniele, M., Haberman, B., Routhier, S., and J.
              Schoenwaelder, "Textual Conventions for Internet Network
              Addresses", RFC 4001, February 2005.

On Sat, 3 Sep 2005, Bernard Aboba wrote:

> Some comments on draft-ietf-radext-dynauth-client-mib-01.txt. Most of 
> these comments also apply to the dynauth-server-mib document.
> 
> The initial sections could use some re-organization.  My suggestion is

> to start the document with Section 2 - Introduction.  Section 1
> (Requirements) would become Section 1.1, and Terminology would become 
> Section 1.2.
> 
> Section 2 (Introduction) refers to RFC 2619 and 2621.  It should also 
> probably refer to the RFC 2619bis and RFC 2621bis documents.
> 
> To address some of the terminology confusion, my suggestion is that 
> the Terminology section be rewritten as follows:
> 
> "1.2  Terminology
> 
>    Dynamic Authorization Server (DAS)
> 
>    The component that resides on the NAS which processes the 
>    Disconnect and Change-of-Authorization (CoA) Request packets 
>    [RFC3576] sent by the Dynamic Authorization Client. 
> 
>    Dynamic Authorization Client (DAC)
> 
>    The component which sends Disconnect and CoA-Request packets 
>    to the Dynamic Authorization Server.  While often residing on the 
>    RADIUS server,  it is also possible for this component to
>    be located on a separate host, such as a Rating Engine.  
> 
>    Dynamic Authorization Server Port
> 
>    The UDP port on which the Dynamic Authorization server listens for
>    the Disconnect and CoA requests sent by the Dynamic Authorization
>    Client."
> 
> Section 5
> 
> Rewrite the first paragraph:
> 
> "5.  Overview
> 
>    "Dynamic Authorization Extensions to RADIUS" [RFC3576] defines
>    the operation of Disconnect-Request, Disconnect-ACK,
Disconnect-NAK,
>    CoA-Request, CoA-ACK and CoA-NAK packets.  [DYNSERV] defines the
>    Dynamic Authorization Server MIB and the relationship with other
>    MIB modules.  This MIB module for the Dynamic Authorization
>    Client contains the following:"
> 
> 
> Capitalization
> 
> The term "authenticator" is inconsistently capitalized.  
> 

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