Re: CUI - issues addressed in version 3

[Greg Weber <gdweber@cisco.com>]

> 
> Hi David, Bernard, Greg, Barney:
> 
> First, thanks again for reviewing the draft and submitting issues
> against versions 1 and 2. It would be great if you can let us know
> whether or not version 03 addresses the issues.    
> 
> Issues addressed in Version 3
> =============================
> Issue 13 (Owner: David Mariblanca)
> Issue 14 (Owner: Bernard Aboba)
> Issue 18 (Owner: Greg Weber)

Hi Farid,
The current version of the draft addresses most of the editorial
issues I mentioned for version -01.  Here are some exceptions:

Section 2.1
  "Access Accept message" -> "Access-Accept message"
  "Accounting Requests" -> "Accounting-Request"
  "User-Name (1)" -> "User-Name(1)" (two places)
Section 5
  "Event-Timestamp" -> "Event-Timestamp(55)"

A couple other nits I see:

Abstract
  "identity a user" -> "identify a user"
Section 2.1
  "CUI attribute the CUI attribute" -> "CUI attribute, the CUI attribute"
  Several occurances of multiple spaces between words, e.g.
    "the  second  part  is  the"  
Normative References
  Each non-IETF reference seems to be missing something, e.g.
    '...Plan", , May 1997'
  
Greg

> Issue 21 (Owner: Barney Wolff)
> Issue 22 (Owner: Barney Wolff) 
> 
> The description of these issues can be found in in
> http://www.drizzle.com/~aboba/RADEXT/#Issue%2014.
> 
> Thanks for your help.
> 
> BR,
> Farid
> 
> --
> 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/>