stds-80220-requirements: Section 4.4.1 Quality of Service and the MAC
Dave et al,
Here is the followup to my last email. The "change" text attributed
to Samir, Vince, Bill, Arif, and myself that appears in section
4.1.15 actually was meant for section 4.4.1.
Section 4.4.1 Quality of Service and the MAC
Current Text: Please see document rev 7.
Action: Delete all current text
Replace with: (Originally proposed by Arif Ansari, Samir Kapoor, Vince Park, Bill Young, Mike Youssefmir on 7/24/03)
802.20 protocols shall provide mechanisms for quality of service (QOS).
The 802.20 protocol standards shall define the interfaces and procedures
that facilitate the configuration and enforcement of QoS policies, which
operators may choose to implement.
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.
Service and QoS Mapping
The classes of service and QoS parameters of all services may be translated
into a common set of parameters defined by 802.20. A QoS based IP network
may employ the Resource Reservation Protocol (RSVP) to signal the
allocation of resources along a routed IP path.
Rationale:
Since the MBWA system is an integral element of the Internet it makes
sense to adopt a QoS model, which is used in conventional IP networks.
The IETF DiffServ model provides a standards-based, scalable mechanism
appropriate for managing the non-deterministic physical connections
characteristic of mobile radio systems. DiffServ provides a framework
for rate limiting e.g., to permit an operator to offer services tiered by
data rate precedence, latency and jitter management.
Proposal:
Sections 4.4.1.1 through 4.4.1.16 should be deleted.
Rationale:
The level of detail here is reflective of specifications as opposed to
requirements, which are expressed in higher-level terms.
Mike