New Editorial Issue (on draft-ietf-geopriv-radius-lo-05.txt)

["Nelson, David" <dnelson@enterasys.com>]

Description of issue
Submitter name: David Nelson
Submitter email address: dnelson@enterasys.com
Date first submitted: February 15, 2006
Reference:
Document: RADIUS-GEOPRIV-05
Comment type: 'E'ditorial
Priority: '1' Should fix
Section: 3.2
Rationale/Explanation of issue:

   Improper use of terminology.

Requested change:

   Upon receiving the Authorize-Only message from the access network,
   the RADIUS server MUST respond with either an Access-Accept or an
   Access-Reject message.

s/Authorize-Only message from the access network/Access-Request message
containing the Service-Type hint attribute with a value of
Authorize-Only
from the NAS/

Section: 5
Rationale/Explanation of issue:

   Improper use of terminology.

Requested change:

   Furthermore, the Basic-Policy-Rules and the Extended-
   Policy-Rules attributes are attached to the Location-Information
   attribute turning location information into a Location Object as
   defined in [12].

The term "attached" apparently has a well understood meaning in terms of
GEOPRIV data objects, but its use in connection with RADIUS attributes
is potentially confusing, and my lead the implementer to believe that
RADIUS application-layer reassembly (i.e. concatenation of two
attributes) is being performed.  If this is the intended outcome
(concatenation within the RADIUS client) then this wording may be OK.
Otherwise, if the RADIUS client is supposed to deliver the individual
attributes to GEOPRIV subsequent processing, rewording to that effect
may be required.

Section:  15.2
Rationale/Explanation of issue:

Cut and paste error.  Redundant words.

Requested change:

   Following the policies outline in [10] new Operator-Namespaces will
   be assigned after Expert Review by the RADEXT working group or its
   designated successor.  Updates can be provided based on expert
   approval only.  A designated expert will be appointed by the O&M Area
   Directors.  No mechanism to mark entries entries as "deprecated is
   envisioned.  Based on expert approval it is possible to delete
   entries from the registry.

s/Operator-Namespace/Requested-Info/

s/entries entries/entries/


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