1 Scope
2
References
2.1 Normative
references
2.2 Informative
references
3
Terms and Definitions
4
Abbreviations, acronyms and conventions
4.1 Abbreviations
and acronyms
4.2 Conventions
5
Technical overview
5.1 QoS
background
5.2 Architecture
6
Authorization interface description
6.1 Gates:
The framework for QoS control
6.2 Gate
transitions
6.3 COPS
profile for IPCablecom multimedia
6.4 Gate control protocol message formats
6.5 Gate
control protocol operation
7
Event messaging interface description
7.1 Introduction
7.2 Record
keeping server requirements
7.3 General
IPCablecom multimedia network element requirements
7.4 Event
messages for IPCablecom multimedia
7.5 Event
messaging attributes for IPCablecom multimedia
7.6 RADIUS
accounting protocol
8
Security requirements
8.1 CMTS – CM QoS interface (pkt-mm-1)
8.2 Policy
server – CMTS COPS interface (pkt-mm-2)
8.3 Application manager – Policy server COPS interface (pkt-mm-3)
8.4 Policy
Server – RKS Event Message Interface (pkt-mm-4)
8.5 CMTS –
RKS Event Message Interface (pkt-mm-5)
9
Mapping a FlowSpec traffic profile to
DOCSIS
9.1 Mapping
FlowSpecs to DOCSIS scheduling types
9.2 Mapping FlowSpecs to DOCSIS traffic parameters
9.3 DOCSIS
upstream parameters
9.4 DOCSIS downstream parameters
10
Message flows
10.1 Basic
message sequence
10.2 Detailed
message sequence
11
Issues for future study
Appendix I – Background information
I.1 Introduction
I.2 IPCablecom
multimedia objectives and scope
I.3 IPCablecom
multimedia framework
I.4 Proxied
QoS with policy push (Scenario 1)
I.5 Client-requested
QoS with policy-push (Scenario 2)
I.6 Client-requested
QoS with policy-pull (Scenario 3)
I.7 Comparison
of IPCablecom-T and IPCablecom multimedia
Appendix II – Guidelines for version
number assignment