Table of Contents
1Scope
2References
2.1Normativereferences
2.2Informativereferences
2.3Referenceacquisition
3Termsanddefinitions
4Abbreviations,acronymsandconventions
4.1Abbreviationsandacronyms
4.2Conventions
5Technicaloverview
5.1Systemarchitecture
5.2Bondingservicesmodel
5.3Multipleservicesmodel
6DEPIarchitecture
6.1DEPIDataPath
6.2Networkingconsiderations
6.3Systemtimingconsiderations
7DEPIcontrolplane
7.1Topology
7.2Addressing
7.3Controlmessageformat
7.4Signalling
7.5AVPdefinitions
8DEPIforwardingplane
8.1L2TPv3transportpacketformat
8.2DOCSISMPTmode
8.3PSPmode
8.4DEPIlatencymeasurement(DLM)sublayerheader
8.5M-CMTScoreoutputrate
AnnexA-DEPIMTU
A.1L2TPv3lowerlayerpayloadsize
A.2MaximumframesizeforDEPI
A.3PathMTUdiscovery
AnnexB-Parametersandconstants
AppendixI-DEPIandDOCSISsystemperformance
I.1Introduction
I.2Round-triptimeandperformance
I.3Elementsofround-triptime
I.4CINcharacteristics
I.5Queueingdelaysinnetworkelements
I.6Trafficprioritizationandnetworkdelays
I.7QueuepersistenceinaDEPIflow
I.8PSPmode
AppendixII-EarlyadoptionandevolvinguseofEQAMdevices
II.1EQAMdevelopment:CategoryA(noDTI)
II.2EQAMdevelopment:CategoryB(withDTI)
II.3PossibleM-CMTSfeaturephasing
II.4OptionalUDPlayer Abstract
Describes an interface known as the Downstream External PHY Interface (DEPI) and associated protocol requirements for the transport of downstream user data between the "M-CMTS Core" and the EQAM.
