Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

RE: stds-80220-requirements: Quality of Service and the MAC (4.4.1)

We agree with this change as it is in the spirit of the original requirement specified (i.e.it merely replaces RFC2598 with RFC3246 as within the Internet standards track RFC 3246 obsoletes RFC 2598 that defines the DiffServ Expedited Forwarding behavior).
 
Branislav
-----Original Message-----
From: owner-stds-80220-requirements@majordomo.ieee.org [mailto:owner-stds-80220-requirements@majordomo.ieee.org]On Behalf Of huhao
Sent: Monday, December 01, 2003 1:11 AM
To: stds-80220-requirements@ieee.org
Subject: stds-80220-requirements: Quality of Service and the MAC (4.4.1)

All,
 

This contribution is proposed to calibrate some inconsistency between the current SRD v9 in 4.4.1 “Quality of Service and MAC” and RFC. Please note the red part of the following section.

Current text:

“…….

The 802.20 air interface shall support the IETF Differentiated Services (DS) Architecture to be compatible with other IP network standards including IP mobile standards. To this end, 802.20 shall support the standard DiffServ QoS model. Some of the forwarding behaviors that should be supported by 802.20 include: Expedited Forwarding (EF), Assured Forwarding (AF), and Best Effort (BE) DS per Hop Behaviors (PHBs) as defined by the RFC 2597 and RFC 2598. 802.20 shall also support configuration of the PHBs by a DS API that shall be based on a subset of the information model defined in RFC 3289.

……”

Proposed Text

“…….

The 802.20 air interface shall support the IETF Differentiated Services (DS) Architecture to be compatible with other IP network standards including IP mobile standards. To this end, 802.20 shall support the standard DiffServ QoS model. Some of the forwarding behaviors that should be supported by 802.20 include: Expedited Forwarding (EF), Assured Forwarding (AF), and Best Effort (BE) DS per Hop Behaviors (PHBs) as defined by the RFC 2597 and RFC 3246. 802.20 shall also support configuration of the PHBs by a DS API that shall be based on a subset of the information model defined in RFC 3289.

……”

Rationale:

The RFC 2598 is obsolete and replaced by RFC 3246 in IETF. The new RFC 3246 adds mathematical formalism to give a more rigorous definition of the behavior described.
 
Best Regards,
 
Hao