1
Scope
2 References
3 Terms and definitions
4 Abbreviations
5 Technical overview
5.1 IPCablecom QoS architecture
requirements
5.2 IP QoS Access Network Elements
5.2.1 Multimedia Terminal Adaptor (MTA)
5.2.2 Cable Modem (CM)
5.2.3 Access Node (AN)
5.2.4 Call Management Server (CMS) and Gate Controller (GC)
5.2.5 Record Keeping Server (RKS)
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.6.1 Preventing theft of service
5.6.2 Two-phase resource commitment
5.6.3 Segmented resource assignment
5.6.4 Resource changes during a session
5.6.5 Dynamic binding of resources
5.6.6 Dynamic QoS performance
5.6.7 Session class
5.6.8 Intermediate network support
5.6.9 Backbone QoS support
5.7 Theory of operation
5.7.1 Basic session set-up
5.7.2 Gate coordination
5.7.3 Changing the packet classifiers associated with a gate
5.7.4 Session resources
5.7.5 Admission control and session classes
5.7.6 Resource renegotiations
5.7.7 Dynamic binding of resources (Re-reserve)
5.7.8 Support for billing
5.7.9 Backbone resource management
5.7.10 Setting the DiffServ code point
6 MTA to AN Quality-of-Service
Protocol (pkt‑q3)
6.1 RSVP extensions overview
6.1.1 Segmented operation
6.1.2 Bidirectional reservations
6.1.3 Header compression, suppression and VAD
6.1.4 Dynamic binding of resources
6.1.5 Two-stage reserve/commit process
6.1.6 Authentication
6.2 RSVP Flowspecs
6.3 Definition of additional RSVP
objects
6.3.1 Reverse-Rspec
6.3.2 Reverse-Session
6.3.3 Reverse-Sender-Template
6.3.4 Reverse-Sender-Tspec
6.3.5 Forward-Rspec
6.3.6 Component-Tspec
6.3.7 Resource-ID
6.3.8 Gate-ID
6.3.9 Commit-Entity
6.3.10 DClass
6.4 Definition of RSVP messages
6.4.1 Message Objects for Upstream
Reservation
6.4.2 Message objects for downstream reservation
6.4.3 Message objects for support of multiple Flowspecs
6.5 Reservation Operation
6.5.1 Reservation establishment
6.5.2 Reservation change
6.5.3 Reservation deletion
6.5.4 Reservation maintenance
6.6 Definition of Commit messages
6.7 Commit operations
7 Authorization interface
description (pkt‑Q6)
7.1 Gates: the Framework for QoS
Control
7.1.1 Classifier
7.1.2 Gate
7.1.3 Gate identification
7.1.4 Gate transition diagram
7.1.5 Gate coordination
7.2 COPS profile
for IPCablecom
7.3 Gate Control
protocol message formats
7.3.1 COPS common message format
7.3.2 Additional COPS Objects
for Gate Control
7.3.3 Definition of Gate Control Messages
7.4 Gate control protocol operation
7.4.1 Initialization sequence
7.4.2 Operation sequence
7.4.3 Procedures for allocating a new gate
7.4.4 Procedures for authorizing resources through a gate
7.4.5 Procedures for Querying a Gate
7.4.6 Procedures for Deleting a Gate
7.4.7 Termination Sequence
8 Gate‑to‑gate
coordination interface (pkt‑q8)
8.1 Gate‑to‑gate
protocol messages
8.1.1 GATE‑OPEN
8.1.2 GATE‑OPEN‑ACK
8.1.3 GATE‑OPEN‑ERR
8.1.4 GATE‑CLOSE
8.1.5 GATE‑CLOSE‑ACK
8.1.6 GATE‑CLOSE‑ERR
8.2 Gate
coordination procedures
8.2.1 Example procedures for end‑to‑end
gate coordination
8.2.2 Example procedures for proxied gate coordination
Annex A -
Additional requirements for J.112 Annex A implementations
A.1 Terminology
A.2 Mapping of Flowspecs into J.112
QoS parameters
A.3 Use of J.112 MAC Primitives
A.3.1 Reserving resources
A.3.2 Committing resources
A.3.3 Releasing resources
A.4 Support of two-phase resource
allocation
A.5 Reservation
maintenance
Annex B -
Additional requirements for J.112 Annex B and Annex C implementations
B.1 Mapping Flowspecs into J.112 QoS
parameters
B.2 J.112 support for resource
reservation
B.2.1 Two-phase QoS Reservation/Commit
B.2.2 Reservation with multiple service flow specifications
B.2.3 Reservation maintenance
B.2.4 Support for dynamic binding of resources
B.2.5 QoS parameter mapping for authorization
B.2.6 Automatically-committed resources
B.3 Use of J.112 MAC control service
interface
B.3.1 Reservation establishment
B.3.2 Reservation change
B.3.3 Reservation deletion
B.3.4 Mapping RSVP Flowspecs into J.112 QoS parameters
Annex C - Timer
definitions and values
Appendix I - Sample
mapping of SDP descriptions into RSVP flowspecs
Appendix II - Sample
protocol message exchanges for basic DCS on-net to on-net call for standalone MTA
II.1 Example Call Flow with J.112 Annex
A messages
II.2 Example call flow with J.112 Annex
B/Annex C messages
Appendix III -Sample protocol
message exchanges for basic NCS on‑net
to on‑net call for standalone MTA
III.1 Example call flow with J.112 Annex
A messages
III.2 Example Call Flow with J.112 Annex
B/Annex C messages
Appendix IV -Sample protocol
message exchanges for mid‑call codec change
IV.1 Example call flow with J.112 Annex
A messages
IV.2 Example call flow with J.112 Annex
B/Annex C messages
Appendix V - Sample
protocol message exchanges for Call Hold
V.1 Example call flow with J.112 Annex
A messages
V.2 Example call flow with J.112 Annex
B/Annex C messages
Appendix VI - Sample
protocol message exchanges for Call Waiting
VI.1 Example call flow with J.112 Annex
A messages
VI.2 Example call flow with J.112 Annex
B/Annex C messages
Appendix VII - Sample
protocol message exchanges for basic DCS on-net to on-net call of an embedded
MTA
VII.1 Example call flow with J.112 Annex
A messages
VII.2 Example call flow with J.112 Annex
B/Annex C messages
Appendix VIII - Sample
protocol message exchanges for basic NCS call for embedded MTA
VIII.1 Example call flow with J.112 Annex
A messages
VIII.2 Example Call Flow with J.112 Annex
B/Annex C messages
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 non-cooperation
for billing
IX.4 Scenario No. 4: MTA altering the
destination address in voice packets
IX.5 Scenario No. 5: Use of
half-connections
IX.6 Scenario No. 6: Early termination
leaving a half-connection
IX.7 Scenario No. 7: Forged Gate Coordination messages
IX.8 Scenario No. 8: 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 XI - RSVP
(Resource Reservation Protocol)
XI.1 RSVP procedures and principles
XI.2 RSVP flowspec
Appendix XII - TCP
considerations
XII.1 Requirements
XII.2 Recommended changes
XII.3 TCP connection establishment impacting post-dial delay
XII.4 Need low
latency for packets between the GC and AN, 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