[Issue] Editorial cmts on CUI-04

[Greg Weber <gdweber@cisco.com>]

Editorial comments on CUI-04
Submitter name: Greg Weber
Submitter email address: gdweber@cisco.com
Date first submitted: April 12, 2005
Reference: n/a
Document: draft-ietf-radext-chargeable-user-id-04.txt
Comment type: E
Priority: 1
Section: various
Rationale/Explanation of issue:

Some editorial nits by section
(S=Section, P=Paragraph)

S1P5: "subscriber" and "user" seem to be used interchangably.  Unless you
      mean something different by "subscriber", I suggest there would be
      less potential for confusion is you use "user" consistently. Otherwise,
      please explain the difference in meaning.
S1.1P3: "Therfore" -> "Therefore"
S2P1: There aren't really any references to or dependencies on RFC3576.
      Why not just remove this reference?
S2.1P2: "may not choose to send" -> "may choose not to send"
S2.2: In the ASCII art, the bit position numbers are not lined up
      with the diagram (off by one column).
S4:   The Diameter Considerations sections seems to place requirements on
      other documents.  Isn't CUI available to Diameter applications as
      a RADIUS attribute?  Why does another attribute need to be defined?
      Maybe the text of this section can be removed & just say that there
      are no particular Diameter considerations.
S6P2: "clients)outside" -> "clients) outside"

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