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 MTA to CMTS Quality-of-Service
Protocol (pkt‑q3)
6.1 RSVP extensions overview
6.2 RSVP Flowspecs
6.3 Definition of additional RSVP
objects
6.4 Definition of RSVP messages
6.5 Reservation operation
6.6 Definition of Commit messages
6.7 Commit operations
7 Embedded MTA
to CM QoS Protocol (pkt-q1)
7.1 Mapping Flowspecs into J.112 QoS parameters
7.2 J.112 support for resource
reservation
7.3 Use of J.112 MAC control service
interface
8 Authorization interface
description (pkt‑q6)
8.1 Gates: the Framework for QoS
control
8.2 COPS profile
for IPCablecom
8.3 Gate Control
protocol message formats
8.4 Gate control protocol operation
8.5 CMS use of gate protocol
8.6 Gate-Coordination
Annex A – Timer
definitions and values
Appendix I
Appendix II – Sample
protocol message exchanges for basic DCS on-net to on-net call for stand-alone MTA
Appendix III – Sample
protocol message exchanges for basic NCS
on‑net to on‑net call for stand-alone MTA
Appendix
IV – Sample protocol
message exchanges for mid‑call codec change
Appendix V – Sample
protocol message exchanges for Call Hold
V.1 Example call flow
Appendix VI – Sample
protocol message exchanges for Call Waiting
VI.1 Example call flow
Appendix VII – Sample
protocol message exchanges for basic DCS on-net to on-net call of an embedded
MTA
Appendix VIII –
Sample protocol message exchanges for basic NCS call for embedded MTA
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 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
Appendix XIII –
Incompatible gate parameter change for NCS call for embedded MTA
Appendix XIV –
Incompatible gate parameter change for NCS call for embedded MTA
Appendix
XV – Sample protocol
message exchanges for Call Waiting using NCS