[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Issue: Editorial comments on draft-ietf-radext-ieee802-00.txt



Submitter name: David Nelson

Submitter email address: dnelson@enterasys.com Date first submitted: August 10, 2005

Reference: (missing from the RADEXT archive ???)

Document: VLAN, Priority and Filtering Attributes Comment type: 'E' Editorial

Priority: '1' Should fix

Section: 2

Rationale/Explanation of issue:

 

Better phrasing.

 

Requested changes:

 

(1)

 

The first paragraph is awkwardly worded.  Perhaps the following would be an improvement.

 

      In this section we provide an elaboration of the requirements

      briefly described in the Introduction.

 

(2)

 

      For example, the user maybe on

      a prepaid plan and all the resources have been used up.

 

Change "maybe" to "may be" and "resources have" to "credit balance has".

 

(3)

 

      For example, the ability to block and

      redirect traffic is required for TCP users, cell phone users,

      WiFi users.

 

Change "TCP users" to "IP users".

 

(4)

 

Change:

 

      As pointed out by [NASREQ] the use Filter-Id is not roaming

      friendly and it is recommended that instead one should use NAS-

      Filter-Rule(TBD) AVP.  For this reason, this document introduces

      NAS-Filter-Rule(TBD) to RADIUS.

 

To:

 

      As pointed out by [NASREQ] the use Filter-Id is not roaming

      friendly and it is recommended that instead one should adapt

      the Diameter NAS-Filter-Rule AVP as a RADIUS NAS-Filter-Rule(TBD)

      attribute.