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
Appendices
I to VIII, and XI
Appendix IX
– Theft of service scenarios
IX.1
Scenario
No. 1: Customers establishing high QoS connections themselves
IX.2
Scenario
No. 2: Customers using provisioned QoS for non-voice applications
IX.3
Scenario
No. 3: MTA altering the destination address in voice packets
IX.4
Scenario
No. 4: Use of half-connections
IX.5
Scenario
No. 6: Early termination leaving a half-connection
IX.6
Scenario
No. 6: Forged gate coordination messages
IX.7
Scenario
No. 7: Fraud directed against unwanted callers
Appendix X
– COPS (Common Open Policy Service)
X.1
COPS
procedures and principles
X.2
Comparison
of COPS and LDAP for policy
Appendix
XII – TCP considerations
XII.1
Requirements
XII.2
Recommended
changes
XII.3
TCP
connection establishment impacting post-dial delay
XII.4 Need for low latency for packets
between the GC and CMTS, even under loss
XII.5
Head
of line blocking
XII.6
TCP
slow start
XII.7
Delaying
of packets: Nagle's algorithm
XII.8
Non-blocking
interface