1
Scope
2
References
2.1
Normative
references
2.2
Informative
references
3
Terms
and definitions
4
Abbreviations
and conventions
4.1
Abbreviations
4.2
Conventions
5
Technical overview
5.1
IPCablecom
QoS architecture requirements
5.2
IP
QoS access network elements
5.3
IPCablecom
dynamic QoS architecture
5.4
QoS
interfaces
5.5
Framework
for IPCablecom QoS
5.6
Requirements
of access network resource management
5.7
Theory
of operation
6
Embedded
MTA to CM QoS Protocol (pkt-q1)
6.1
RSVP
flowspecs
6.2
DOCSIS
support for resource reservation
6.3
Use
of DOCSIS MAC control service interface
7
Authorization
interface description (pkt‑q6)
7.1
Gates:
The framework for QoS control
7.2 COPS profile for IPCablecom
7.3 Gate control protocol message formats
7.4
Gate
control protocol operation
7.5
CMS
use of gate protocol
7.6
Gate-coordination
Annex A
–Timer definitions and values
Appendix I
– Theft of service scenarios
I.1
Scenario No. 1: Customers
establishing high QoS connections themselves
I.2
Scenario No. 2:
Customers using provisioned QoS for non-voice applications
I.3
Scenario No. 3: MTA altering the
destination address in voice packets
I.4
Scenario No. 4: Use of
half-connections
I.5
Scenario No. 6: Early termination
leaving a half-connection
I.6
Scenario No. 6: Forged
gate coordination messages
I.7
Scenario No. 7: Fraud
directed against unwanted callers
Appendix II
– COPS (common open policy service)
II.1
COPS
procedures and principles
II.2
Comparison
of COPS and LDAP for policy
Appendix
III – TCP considerations
III.1
Requirements
III.2
Recommended
changes
III.3
TCP
connection establishment impacting post-dial delay
III.4 Need for low latency for packets
between the GC and CMTS, even under loss
III.5
Head-of-line
blocking
III.6
TCP
slow start
III.7
Delaying
of packets: Nagle's algorithm
III.8
Non-blocking
interface