1
Scope
1.1
Purpose
of this Recommendation
1.2
Scope
of this Recommendation
2
References
2.1
Normative
references
2.2 Informative References
2.3 Reference acquisition
3
Terms
and definitions
4
Abbreviations,
acronyms and conventions
4.1
Abbreviations
and acronyms
4.2
Conventions
5
Background
5.1
Service
goals
5.2
IPCablecom
reference architecture
5.3
Components
and interfaces
5.4
Components
5.5 Interface descriptions
6
Assumptions
7
Subscriber
provisioning
7.1
Customer
records (billing)
7.2
Equipment
set-up and configuration
7.3
Static
versus Dynamic Subscriber Provisioning Data
8
Requirements
8.1
General
requirements
8.2
Transport
requirements
9
Data
model
9.1
Overview
9.2
Relations
are encoded using the PcspRelation entity.XML encoding
10 Messaging
10.1
Overview
10.2
CMS
and PS messaging role requirements
10.3
WSDL
specification
11 Security
Annex A –
PCSP XML schema
Appendix I – Sample entity encodings
I.1 PcspService object example
I.2 PcspEndpoint object example
I.3 PcspMta object example
I.4 PcspCms object example
I.5 PcspRelation example
Appendix II – Sample object extension
II.1 Extended PcspService object example
II.2 The extension schema
Appendix
III – Data encoding evaluation
III.1
XML
III.2
ASN.1/BER
III.3
Proprietary
ASCII
III.4 SDP (Session Description Protocol)
III.5
RADIUS
III.6
SQL
III.7
Options summary
III.8
Recommendation:
XML
Appendix IV
– Transport protocol evaluation
IV.1
TFTP
with IPSec
IV.2
Batched
RADIUS – Multiple records in single request via event messages
IV.3
Diameter
IV.4
Distributed
object systems
IV.5
HTTP
IV.6 Options summary
IV.7 Recommendation: HTTP 1.1
BIBLIOGRAPHY