[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: stds-802-16: 802.16, not 802, will deal with "ATM vs. IP"
- To: "'email@example.com'" <firstname.lastname@example.org>
- Subject: RE: stds-802-16: 802.16, not 802, will deal with "ATM vs. IP"
- From: Jack_Fijolek@3com.com
- Date: Tue, 20 Apr 1999 17:58:14 -0500
- Sender: email@example.com
[Notice: It is the policy of 802.16 to treat messages posted here as non-confidential.]
Comments in this thread do not seem to come from those that have read the 802.14
ATM based MAC or the DOCSIS v1.1 SP-RFI document. Yes, 802.14 spent years
bickering over ATM vs. IP using the same exact arguments dredged up in these
threads. 802.14 ended up discarding their 2 years of ATM MAC work as irrelevant
because DOCSIS proved to be evolving into something more than a simple
residential internet service.
The first version of the DOCSIS standard (version 1.0) concentrated on defining
the MAC and IP layer components required for a Cable Modem to initialize with
its Cable Modem Termination System and focuses mostly on best effort services
and class of service (CoS) differentiation. Version 1.1 of the standard adds
support for Quality of Service (QoS) at the MAC layer between the CM and the
CMTS. Using this specification DOCSIS v1.1 can deliver QoS guaranteed services
more efficiently than cell based CBR. DOCSIS v1.1 can meet most jitter and delay
requirements with minimal header overhead using an unsolicited grant service,
link layer fragmentation and packet header suppression.
3Com Cable Access