• 1 Scope
  • 2 References
  • 3 Definitions
    • 3.1 Terms defined elsewhere
    • 3.2 Terms defined in this Recommendation
  • 4 Abbreviations and acronyms
  • 5 Home network architecture and reference models
  • 6 Profiles
  • 7 Physical layer specification
  • 8 Data link layer specification
    • 8.1 Functional model and frame formats
      • 8.1.1 Functional model of the data link layer (DLL)
      • 8.1.2 Application protocol convergence (APC)
      • 8.1.3 Logical link control (LLC)
        • 8.1.3.1 LLC frame format
          • 8.1.3.1.1 LLC frame header fields
            • 8.1.3.1.1.1 LLC frame type (LLCFT)
            • 8.1.3.1.1.2 Timestamp present indication (TSMPI)
            • 8.1.3.1.1.3 CCMP header present indication (CCMPI)
            • 8.1.3.1.1.4 LLC frame priority (LPRI)
            • 8.1.3.1.1.5 Frame length (FLEN)
            • 8.1.3.1.1.6 OriginatingNode
            • 8.1.3.1.1.7 Broadcast indicator (BRCTI)
            • 8.1.3.1.1.8 Time to live (TTL)
            • 8.1.3.1.1.9 Timestamp (TSMP)
            • 8.1.3.1.1.10 DestinationNode
            • 8.1.3.1.1.11 MCSTI
        • 8.1.3.2 Generation of LPDUs
          • 8.1.3.2.1 LPDU header format
            • 8.1.3.2.1.1 Segment sequence number (SSN)
            • 8.1.3.2.1.2 LLC frame boundary offset (LFBO)
            • 8.1.3.2.1.3 Valid segment flag (VSF)
            • 8.1.3.2.1.4 Management queue flag (MQF)
            • 8.1.3.2.1.5 Oldest pending segment flag (OPSF)
          • 8.1.3.2.2 LPDU check sequence (LPCS)
        • 8.1.3.3 Generation of LPDUs for retransmission
        • 8.1.3.4 LCDU frame format
      • 8.1.4 Medium access control (MAC)
        • 8.1.4.1 Assembling of an MPDU from LPDUs
    • 8.2 MAP controlled medium access
      • 8.2.1 The MAC cycle
      • 8.2.2 Duration of the MAC cycle
      • 8.2.3 TXOP timing
    • 8.3 Transmission opportunities (TXOPs) and time slots (TSs)
      • 8.3.1 Assignment of nodes and connections to TXOPs and TSs
        • 8.3.1.1 Persistent and non-persistent TXOPs
        • 8.3.1.2 Persistent access
      • 8.3.2 TXOP and TS attributes
      • 8.3.3 Medium access in STXOPs
        • 8.3.3.1 TS size and timing
        • 8.3.3.2 TS assignment rules
          • 8.3.3.2.1 Sequential TS assignment rule
          • 8.3.3.2.2 Line activity dependent TS assignment rule
        • 8.3.3.3 Transmission in CFTS
        • 8.3.3.4 Transmission in CBTS
          • 8.3.3.4.1 Priority resolution
          • 8.3.3.4.2 Mapping of MPDU priorities to medium access priorities
          • 8.3.3.4.3 CBTS back-off rules
          • 8.3.3.4.4 Use of RTS/CTS signalling
          • 8.3.3.4.5 Closing of CBTS
            • 8.3.3.4.5.1 STXOP containing CBTS and CFTS
              • 8.3.3.4.5.1.1 Duration-based CBTS closure
              • 8.3.3.4.5.1.2 Timeout-based from frame sequence start CBTS closure
              • 8.3.3.4.5.1.3 Timeout-based from CBTS start CBTS closure
            • 8.3.3.4.5.2 CBTXOP containing CBTS with different attributes
            • 8.3.3.4.5.3 CBTXOP containing CBTS with same attributes
          • 8.3.3.4.6 Use of CBTS with no PR signals
          • 8.3.3.4.7 Use of INUSE signal in CBTS
          • 8.3.3.4.8 Use of CBTS for node registration
          • 8.3.3.4.9 Collision inference
        • 8.3.3.5 Enhanced frame detection (EFD) STXOP
        • 8.3.3.6 TS grid synchronization loss and recovery
          • 8.3.3.6.1 TS grid synchronization loss detection
          • 8.3.3.6.2 TS grid synchronization recovery
        • 8.3.3.7 Silent TXOP or TS
      • 8.3.4 Medium access in CFTXOPs
      • 8.3.5 Transmission using PHY frame bursting
      • 8.3.6 Scheduled inactivity
        • 8.3.6.1 Scheduled inactivity over multiple MAC cycles
          • 8.3.6.1.1 Long inactivity scheduling
        • 8.3.6.2 Scheduled inactivity in a single MAC cycle
          • 8.3.6.2.1 Short inactivity scheduling
      • 8.3.7 Bidirectional transmissions
      • 8.3.8 Extended acknowledgements
      • 8.3.9 Piggybacked acknowledgements in BMSG frames
    • 8.4 Control parameters for APC, LLC, and MAC
      • 8.4.1 General parameters for management message timeout
    • 8.5 Functions of the endpoint node
      • 8.5.1 MAC cycle synchronization and synchronized transmissions
      • 8.5.2 Bandwidth reservation
      • 8.5.3 Routing of ADPs
      • 8.5.4 Broadcast of LLC frames
        • 8.5.4.1 Filtering of broadcast LLC frames
      • 8.5.5 Reporting of detected neighbouring domains
      • 8.5.6 MAP relaying
        • 8.5.6.1 MAP relaying for registration of hidden nodes
        • 8.5.6.2 MAP relaying for operation of registered hidden nodes
      • 8.5.7 Relaying messages
        • 8.5.7.1 Relaying of LCDU
        • 8.5.7.2 Relaying of APDU
      • 8.5.8 Retransmissions and acknowledgement
      • 8.5.9 Bidirectional flows
        • 8.5.9.1 Bidirectional service flows
        • 8.5.9.2 Bidirectional prioritized data connections
    • 8.6 Domain master node functional capabilities
      • 8.6.1 Network admission
        • 8.6.1.1 Network admission protocol
          • 8.6.1.1.1 Registration into the domain
          • 8.6.1.1.2 Periodic re-registrations
          • 8.6.1.1.3 Resignation from the domain
            • 8.6.1.1.3.1 Self-resignation
            • 8.6.1.1.3.2 Forced resignation
          • 8.6.1.1.4 Registration and resignation messages
            • 8.6.1.1.4.1 Registration request message (ADM_NodeRegistrRequest.req)
            • 8.6.1.1.4.2 Registration response message (ADM_DmRegistrResponse.cnf)
            • 8.6.1.1.4.3 Resignation request message (ADM_NodeResignRequest.req)
            • 8.6.1.1.4.4 Resignation confirmation message (ADM_DmResign.cnf)
            • 8.6.1.1.4.5 Forced resignation request message (ADM_DmForcedResign.req)
            • 8.6.1.1.4.6 Re-registration request message (ADM_NodeReRegistrRequest.req)
            • 8.6.1.1.4.7 Re-registration response message (ADM_DmReRegistrResponse.cnf)
            • 8.6.1.1.4.8 Re-registration initiation message (ADM_DmReRegistrInitiate.ind)
            • 8.6.1.1.4.9 New node registered indication to SC (ADM_NewNodeRegistered.ind)
        • 8.6.1.2 Admission via proxy
        • 8.6.1.3 Domain maintenance after node admission
      • 8.6.2 Bandwidth management
        • 8.6.2.1 Description of TSpec parameters
        • 8.6.2.2 Lifecycle of a data flow
          • 8.6.2.2.1 Flow establishment
          • 8.6.2.2.2 Flow establishment via relay nodes
          • 8.6.2.2.3 Flow maintenance
            • 8.6.2.2.3.1 Timing adjustment of CFTXOP
          • 8.6.2.2.4 Flow termination
            • 8.6.2.2.4.1 Message sequence chart for flow termination
          • 8.6.2.2.5 Tunnel reconstruction or termination
            • 8.6.2.2.5.1 Normal tunnel termination
            • 8.6.2.2.5.2 Tunnel reconstruction or termination due to a broken link
              • 8.6.2.2.5.2.1 MSC of tunnel reconstruction for case 1
              • 8.6.2.2.5.2.2 Tunnel reconstruction for case 2
              • 8.6.2.2.5.2.3 Tunnel reconstruction for case 3
              • 8.6.2.2.5.2.4 Tunnel reconstruction for case 4
            • 8.6.2.2.5.3 Domain master triggered tunnel termination
            • 8.6.2.2.5.4 Tunnel termination due to disconnection of the originating node
        • 8.6.2.3 Flow signalling protocol messages
          • 8.6.2.3.1 Format of CL_EstablishFlow.req
          • 8.6.2.3.2 Format of CL_EstablishFlow.cnf
          • 8.6.2.3.3 Format of CL_TerminateFlow.req
          • 8.6.2.3.4 Format of CL_TerminateFlow.cnf
          • 8.6.2.3.5 Format of CL_FlowTerminated.ind
          • 8.6.2.3.6 Format of FL_OriginateFlow.req
          • 8.6.2.3.7 Format of FL_OriginateFlow.cnf
          • 8.6.2.3.8 Format of FL_AdmitFlow.req
          • 8.6.2.3.9 Format of FL_AdmitFlow.cnf
          • 8.6.2.3.10 Format of FL_AdmitFlow.ind
          • 8.6.2.3.11 Format of FL_ModifyFlowParameters.req
          • 8.6.2.3.12 Format of FL_ModifyFlowParameters.cnf
          • 8.6.2.3.13 Format of FL_TerminateFlow.req
          • 8.6.2.3.14 Format of FL_TerminateFlow.cnf
          • 8.6.2.3.15 Format of FL_ModifyFlowParameters.ind
          • 8.6.2.3.16 Format of FL_ModifyFlowAllocations.req
          • 8.6.2.3.17 Format of FL_ModifyFlowAllocations.cnf
          • 8.6.2.3.18 Format of FL_AdmitFlow.rsp
          • 8.6.2.3.19 Format of FL_BrokenTunnel.ind
          • 8.6.2.3.20 Format of FL_BrokenTunnel.rsp
          • 8.6.2.3.21 Format of FL_ReleaseTunnel.req
          • 8.6.2.3.22 Format of FL_ReleaseTunnel.cnf
          • 8.6.2.3.23 Format of FL_DM_RenewTunnel.req
          • 8.6.2.3.24 Format of FL_DM_RenewTunnel.cnf
          • 8.6.2.3.25 Format of the FL_RenewTunnel.req message
          • 8.6.2.3.26 Format of the FL_RenewTunnel.cnf message
          • 8.6.2.3.27 Format of the FL_DeleteFlow.req message
          • 8.6.2.3.28 Format of the FL_DeleteFlow.cnf message
          • 8.6.2.3.29 Format of CL_TerminateFlow.ind
          • 8.6.2.3.30 Format of FL_TerminateTunnel.req
          • 8.6.2.3.31 Format of FL_TerminateTunnel.cnf
        • 8.6.2.4 Bandwidth update protocol for prioritized connections
          • 8.6.2.4.1 Bandwidth update protocol messages
            • 8.6.2.4.1.1 Format of BU_BWUpdate.req
            • 8.6.2.4.1.2 Format of BU_BWUpdate.cnf
      • 8.6.3 Synchronization to an external source
        • 8.6.3.1 AC line cycle synchronization
      • 8.6.4 Routing and topology management
        • 8.6.4.1 Domain master operation for routing and topology management
          • 8.6.4.1.1 Domain master operation in CRTM mode
            • 8.6.4.1.1.1 Generation of the unicast routing table
            • 8.6.4.1.1.2 Distribution of routing tables
            • 8.6.4.1.1.3 Generation of the BRT
          • 8.6.4.1.2 Domain master operation in DRTM mode
        • 8.6.4.2 Endpoint node topology maintenance
          • 8.6.4.2.1 Endpoint node topology maintenance in CRTM mode
            • 8.6.4.2.1.1 Communication of endpoint topology change in CRTM mode
          • 8.6.4.2.2 Endpoint node topology maintenance in DRTM mode
          • 8.6.4.2.3 Flooding of topology information
        • 8.6.4.3 Message formats
          • 8.6.4.3.1 Format of TM_NodeTopologyChange.ind
          • 8.6.4.3.2 Format of the TM_NodeTopologyChange.req
          • 8.6.4.3.3 Format of TM_NodeTopologyChange.cnf
          • 8.6.4.3.4 Format of TM_DMBackup.ind
          • 8.6.4.3.5 Format of TM_DomainRoutingChange.ind
          • 8.6.4.3.6 Format of TM_ReturnDomainRouting.req
          • 8.6.4.3.7 Format of TM_ReturnDomainRouting.cnf
      • 8.6.5 Backup domain master
        • 8.6.5.1 Backup domain master assignment and release
        • 8.6.5.2 Message formats for assignment and release of the backup
        • 8.6.5.3 Recovery of the domain master failure by backup
          • 8.6.5.3.1 Domain master failure detection
          • 8.6.5.3.2 Domain master recovery procedure
      • 8.6.6 Domain master selection
        • 8.6.6.1 Domain master selection
          • 8.6.6.1.1 Domain master selection at initialization
          • 8.6.6.1.2 Domain master maintenance
          • 8.6.6.1.3 Merging procedure
          • 8.6.6.1.4 Management message formats for domain master maintenance
            • 8.6.6.1.4.1 Format of ADM_NodeReportMAPD.ind
            • 8.6.6.1.4.2 Format of ADM_NodeReportMAPA.ind
        • 8.6.6.2 Domain master recovery in case of no backup ready
        • 8.6.6.3 Ranking of domain master capabilities
        • 8.6.6.4 Handing domain master's role to a more capable node
        • 8.6.6.5 Message formats to support handover
          • 8.6.6.5.1 DM_Handover.req message
          • 8.6.6.5.2 DM_Handover.cnf message
          • 8.6.6.5.3 DM_Handover.ind message
          • 8.6.6.5.4 DM_Handover.rsp message
          • 8.6.6.5.5 DM_HandoverRequest.ind message
      • 8.6.7 Selection of PHY-frame header segmentation
      • 8.6.8 Selection of the DNI and the DOD
        • 8.6.8.1 Selection and maintenance of the DOD
        • 8.6.8.2 Selection and maintenance of the DNI
          • 8.6.8.2.1 Generation of the DNI
      • 8.6.9 Per-node transmit PSD shaping
        • 8.6.9.1 Format of TP_TransmitPsdChange.req message
        • 8.6.9.2 Format of TP_TransmitPsdChange.cnf
      • 8.6.10 Selection of initialization seeds used for generating preamble, PR, INUSE, NACK and IDPS signals
    • 8.7 Addressing scheme
      • 8.7.1 Node identifier
        • 8.7.1.1 DEVICE_ID
        • 8.7.1.2 MULTICAST_ID and BROADCAST_ID
      • 8.7.2 Flow identifier (FLOW_ID)
    • 8.8 Medium access plan (MAP) frame
      • 8.8.1 MAP generation and distribution
      • 8.8.2 MAP frame transmission
      • 8.8.3 MAP header
      • 8.8.4 TXOP descriptor
        • 8.8.4.1 TXOP descriptor extension
          • 8.8.4.1.1 TXOP attributes extension data
          • 8.8.4.1.2 TXOP absolute timing extension data
          • 8.8.4.1.3 Group information extension data
          • 8.8.4.1.4 Maximum transmission limitation extension data
          • 8.8.4.1.5 CBTS nodes information Extension Data
          • 8.8.4.1.6 Additional TXOP attributes extension data
        • 8.8.4.2 Special values for the TXOP descriptor
      • 8.8.5 Auxiliary information field
        • 8.8.5.1 Reserved field
        • 8.8.5.2 Domain information sub-field
        • 8.8.5.3 Long inactivity schedule sub-field
        • 8.8.5.4 Short inactivity schedule sub-field
        • 8.8.5.5 PSD-related domain info sub-field
        • 8.8.5.6 New domain master ID sub-field
        • 8.8.5.7 Backup domain master ID sub-field
        • 8.8.5.8 Timer-related domain info sub-field
          • 8.8.5.8.1 Topology update interval sub-field
        • 8.8.5.9 Registration code sub-field
        • 8.8.5.10 DOD update sub-field
        • 8.8.5.11 NMK_DB_update sub-field
        • 8.8.5.12 Contention window (CW) information sub-field
        • 8.8.5.13 NDIM information sub-field
        • 8.8.5.14 Power saving update sub-field
        • 8.8.5.15 Additional domain information sub-field
      • 8.8.5.16 Security-related domain info sub-field
        • 8.8.5.17 MAC authorization information sub-field
        • 8.8.5.18 Neighbouring Domain List domain info sub-field
      • 8.8.6 MAP schedule persistence publication
    • 8.9 Retransmission and acknowledgement protocol
      • 8.9.1 Acknowledgment for a unicast PHY frame
        • 8.9.1.1 Immediate acknowledgment
        • 8.9.1.2 Delayed acknowledgment
      • 8.9.2 Acknowledgment for multicast PHY frames
        • 8.9.2.1 Multicast acknowledgement overview
        • 8.9.2.2 Multicast acknowledgement procedure
      • 8.9.3 Request for ACK retransmission
      • 8.9.4 Acknowledgement protocol parameters
        • 8.9.4.1 General parameters
        • 8.9.4.2 Transmitter variables and control flags
        • 8.9.4.3 Receiver variables and control flags
      • 8.9.5 Acknowledgement protocol operation
        • 8.9.5.1 SSN comparison
        • 8.9.5.2 Segment lifecycle
        • 8.9.5.3 Acknowledgement protocol state machine for unicast transmission
          • 8.9.5.3.1 Transmission window operation
          • 8.9.5.3.2 Reception window operation
        • 8.9.5.4 Acknowledgement protocol state machine for multicast transmission
          • 8.9.5.4.1 Transmission window operation
          • 8.9.5.4.2 Reset of a multicast connection with acknowledgements
          • 8.9.5.4.3 Reception window operation
    • 8.10 Management and control message format
      • 8.10.1 Management message format
        • 8.10.1.1 Management message OPCODEs
        • 8.10.1.2 Management of message sequence numbers and segmentation
      • 8.10.2 Control message format
        • 8.10.2.1 Control message OPCODEs
    • 8.11 Channel estimation protocol
      • 8.11.1 Receiver-initiated channel estimation
        • 8.11.1.1 Channel estimation initiation
        • 8.11.1.2 Channel estimation bandwidth request
        • 8.11.1.3 Channel estimation initiation confirmation
        • 8.11.1.4 Request for PROBE frame transmission
        • 8.11.1.5 PROBE frame transmission
        • 8.11.1.6 Channel estimation completion
        • 8.11.1.7 Channel estimation cancellation
        • 8.11.1.8 Channel estimation bandwidth release
      • 8.11.2 Transmitter-requested channel estimation
        • 8.11.2.1 Channel estimation request
      • 8.11.3 Shortened channel estimation processes
        • 8.11.3.1 Unsolicited CE_ParamUpdate.req
        • 8.11.3.2 Partial BAT update
          • 8.11.3.2.1 PBU request
          • 8.11.3.2.2 PBU confirmation
      • 8.11.4 Channel estimation using PROBE frames
        • 8.11.4.1 Channel estimation using PROBE frames transmitted by a node as requested by Domain Master
      • 8.11.5 BAT_ID maintenance
      • 8.11.6 ACE symbol insertion
      • 8.11.7 Management message formats for channel estimation
        • 8.11.7.1 Format of CE_ProbeSlotAssign.req
        • 8.11.7.2 Format of CE_ProbeSlotRelease.req
        • 8.11.7.3 Format of CE_ParamUpdate.req
        • 8.11.7.4 Format of CE_ParamUpdateRequest.ind
        • 8.11.7.5 Format of CE_PartialBatUpdate.req
        • 8.11.7.6 Format of CE_ACESymbols.ind
        • 8.11.7.7 Format of CE_ProbeSlotAssign.cnf
        • 8.11.7.8 Format of CE_ProbeSlotRelease.cnf
        • 8.11.7.9 Format of CE_ParamUpdate.cnf
        • 8.11.7.10 Format of CE_PartialBatUpdate.cnf
        • 8.11.7.11 Format of CE_Request.ind
        • 8.11.7.12 Format of CE_Initiation.req
        • 8.11.7.13 Format of CE_Initiation.cnf
        • 8.11.7.14 Format of CE_ProbeRequest.ind
        • 8.11.7.15 Format of CE_Cancellation.req
        • 8.11.7.16 Format of CE_BatIdMaintain.ind
        • 8.11.7.17 Format of CE_Cancellation.cnf
    • 8.12 Connection management
      • 8.12.1 Establishment of a unicast connection with acknowledgements
        • 8.12.1.1 Establishment of the management connection
        • 8.12.1.2 Establishment of a data connection
      • 8.12.2 Establishment of a unicast connection without acknowledgements
        • 8.12.2.1 Establishment of the management connection
        • 8.12.2.2 Establishment of a data connection
      • 8.12.3 Establishment of a unicast data connection for a service flow
      • 8.12.4 Flow control of connections
      • 8.12.5 Release of a unicast connection with acknowledgements
        • 8.12.5.1 Release of the management connection
        • 8.12.5.2 Release of a data connection
      • 8.12.6 Release of a unicast connection without acknowledgements
        • 8.12.6.1 Release of the management connection
        • 8.12.6.2 Release of a data connection
      • 8.12.7 Reset of a unicast connection with acknowledgements
      • 8.12.8 Broadcast connections
        • 8.12.8.1 Broadcast management connection
        • 8.12.8.2 Broadcast data connection
    • 8.13 Message flooding
    • 8.14 Operation in the presence of neighbouring domains – Distributed domain coordination (NDIM)
      • 8.14.1 General principles
        • 8.14.1.1 NDIM procedure
      • 8.14.2 NDIM cluster
      • 8.14.3 Inter-domain signalling and communication
      • 8.14.4 NDIM MAC cycle alignment procedures
        • 8.14.4.1 Full MAC cycle alignment procedure
        • 8.14.4.2 Foreshortened MAC cycle alignment procedure
        • 8.14.4.3 MAC cycle alignment procedure in presence of coexisting access system
        • 8.14.4.4 Post-alignment procedure
        • 8.14.4.5 MAC cycle alignment procedure during startup of a domain
      • 8.14.5 Routine maintenance procedure for a node to follow after MAC cycle alignment
      • 8.14.6 Communication between neighbouring domains
        • 8.14.6.1 Node to node communication through IDCC
          • 8.14.6.1.1 Transmitting a unicast IDM to a neighbouring domain
          • 8.14.6.1.2 Transmitting a broadcast IDM to a neighbouring domain
        • 8.14.6.2 Transmitting IDMs from domain master to neighbouring domain master
      • 8.14.7 Coordination of transmissions among nodes from neighbouring domains within a cluster
        • 8.14.7.1 General Principles of neighbouring domain coordination
        • 8.14.7.2 Neighbouring domain coordination procedure
          • 8.14.7.2.1 Default MAC cycle time allocation based on DOD
          • 8.14.7.2.2 Exchange of interference information between neighbouring domains
          • 8.14.7.2.3 Default MAC cycle time allocation based on interference information
          • 8.14.7.2.4 Static Exchange of time slots between neighbouring domains
        • 8.14.7.3 Impact of ITU-T G.9972 on neighbouring domain coordination
        • 8.14.7.4 Examples of allocation
          • 8.14.7.4.1 Example of simple neighbouring domain coordination between five domains
          • 8.14.7.4.2 Example of neighbouring domain coordination between five domains with conflicts
        • 8.14.7.5 Synchronization of neighbouring domain coordination
      • 8.14.8 NDIM parameters
      • 8.14.9 NDIM protocol messages
        • 8.14.9.1 NDIM Start alignment procedure request
        • 8.14.9.2 NDIM IDCC slot reserve request
        • 8.14.9.3 NDIM IDCC slot reserve confirmation
        • 8.14.9.4 NDIM_ReportAlignment.req format
        • 8.14.9.5 NDIM_ReportAlignment.cnf format
        • 8.14.9.6 NDIM Remote presence request
        • 8.14.9.7 NDIM Remote presence confirmation
        • 8.14.9.8 NDIM Transmit indication
        • 8.14.9.9 NDIM Receive indication
        • 8.14.9.10 NDIM IDCC_Release message format
        • 8.14.9.11 NDIM IDCC _Release confirmation
        • 8.14.9.12 NDIM interference report indication
      • 8.14.10 Inter-domain protocol messages
        • 8.14.10.1 IDM_ClusterAlignment.req format
        • 8.14.10.2 IDM ClusterAlignment.cnf message format
        • 8.14.10.3 IDM interfering nodes information
        • 8.14.10.4 IDM interference information response
        • 8.14.10.5 IDM coordinating domains information
        • 8.14.10.6 IDM coordination information response
        • 8.14.10.7 IDM share unallocated slot request
        • 8.14.10.8 IDM share unallocated Slot confirmation
        • 8.14.10.9 IDM share unallocated Slot indication
        • 8.14.10.10 IDM request unallocated slot request
        • 8.14.10.11 IDM request unallocated slot confirmation
        • 8.14.10.12 IDM request unallocated slot indication
        • 8.14.10.13 IDM swap allocated slot request
        • 8.14.10.14 IDM swap allocated slot confirmation
        • 8.14.10.15 IDM swap allocated slot indication
        • 8.14.10.16 IDM coordination preference indication
        • 8.14.10.17 IDM domain master change indication
        • 8.14.10.18 IDM DNI change indication
    • 8.15 Coexistence with alien power-line networks
    • 8.16 PHY multicast binding protocol
      • 8.16.1 Initialization of a PHY multicast group
      • 8.16.2 Maintenance of multicast binding information
      • 8.16.3 Termination of a multicast group
      • 8.16.4 PHY multicast binding protocol flow
        • 8.16.4.1 Message sequence – Initialization of a PHY multicast group for a new multicast stream
        • 8.16.4.2 Message sequence – Split of a multicast stream into several PHY multicast groups
        • 8.16.4.3 Message sequence – Establish a PHY multicast group with flow-control disabled
        • 8.16.4.4 Message sequence – Maintenance of multicast binding information
      • 8.16.5 PHY multicast binding protocol messages
        • 8.16.5.1 PHY multicast group information update indication
        • 8.16.5.2 Multicast binding information confirmation from receiver
        • 8.16.5.3 Format of MC_GrpRemove.req
        • 8.16.5.4 Format of MC_GrpRemove.cnf
    • 8.17 DLL multicast stream
      • 8.17.1 DLL multicast stream establishment
      • 8.17.2 DLL multicast stream establishment with bandwidth reservation
        • 8.17.2.1 Bandwidth reservation when direct link from originating node to client node
        • 8.17.2.2 Bandwidth reservation through relay
      • 8.17.3 Preventing loops and packet duplications
      • 8.17.4 Releasing client node from MSID
      • 8.17.5 Recovery from a DLL multicast broken path
      • 8.17.6 Aging DLL multicast path process
      • 8.17.7 DLL Multicast stream bandwidth maintenance
      • 8.17.8 Transmission of bandwidth managed DLL multicast stream
      • 8.17.9 DLL Multicast protocol messages
        • 8.17.9.1 DMC_Path.req message format
        • 8.17.9.2 DMC_Path.cnf message format
        • 8.17.9.3 DMC_PathReject.cnf message format
        • 8.17.9.4 DMC_EnforcePath.req message format
        • 8.17.9.5 DMC_ReleasePath.req message format
        • 8.17.9.6 DMC_ReleasePath.cnf message format
        • 8.17.9.7 DMC_PathAlive.ind message format
        • 8.17.9.8 DMC_BrokenLink.ind message format
        • 8.17.9.9 DMC_BWReserve.req message format
        • 8.17.9.10 DMC_BWReserve.cnf message format
        • 8.17.9.11 DMC_BWRelease.req message format
        • 8.17.9.12 DMC_BWRelease.cnf message format
    • 8.18 Inter-bandplan interoperability
      • 8.18.1 Bandplan-related information
      • 8.18.2 Configuring the minimum and maximum bandplan for the domain
      • 8.18.3 Conveying bandplan-related information to all nodes in the domain
      • 8.18.4 Transmissions of MAPs to guarantee inter-bandplan interoperability
      • 8.18.5 Inter-bandplan payload transmissions
    • 8.19 Node information and capabilities exchange
    • 8.20 Metrics acquisition
      • 8.20.1 Metrics acquisition protocol messages
        • 8.20.1.1 Format of MA_AcquireMetrics.req
        • 8.20.1.2 Format of MA_AcquireMetrics.cnf
    • 8.21 Operation in power saving modes
      • 8.21.1 Power saving mode transitions
      • 8.21.2 Operation in L1 power saving mode
      • 8.21.3 Operation in L2 power saving mode
      • 8.21.4 Operation in L3 power saving mode
      • 8.21.5 Operation in L4 power saving mode
      • 8.21.6 Domain master in power saving mode
    • 8.22 Layer 2 Configuration and Management Protocol (LCMP)
      • 8.22.1 LCMP behaviour description
      • 8.22.2 Transmission scheme
      • 8.22.3 LCMP messages
        • 8.22.3.1 LCMP READ request message (LCMP_Read.req)
        • 8.22.3.2 LCMP READ confirmation message (LCMP_Read.cnf)
        • 8.22.3.3 LCMP WRITE request message (LCMP_Write.req)
        • 8.22.3.4 LCMP WRITE confirmation message (LCMP_Write.cnf)
        • 8.22.3.5 LCMP_Ctrl request message (LCMP_Ctrl.req)
        • 8.22.3.6 LCMP_Ctrl confirmation message (LCMP_Ctrl.cnf)
        • 8.22.3.7 LCMP NOTIFY indication message (LCMP_Notify.ind)
        • 8.22.3.8 LCMP NOTIFY response message (LCMP_Notify.rsp)
        • 8.22.3.9 LCMP indication message (LCMP.ind)
        • 8.22.3.10 LCMP response message (LCMP.rsp)
      • 8.22.4 ITU-T LCMP messages
    • 8.23 Run-length compression of fields of management messages
    • 8.24 Payload compression in management messages
    • 8.24.1 Huffman coding of MMPL
  • 9 Security
    • 9.1 Encryption
      • 9.1.1 Description of the CCMP
        • 9.1.1.1 CCM encryption
        • 9.1.1.2 Parameters
        • 9.1.1.3 Input variables
      • 9.1.2 CCM encryption protocol (CCMP)
        • 9.1.2.1 Functional description
        • 9.1.2.2 CCMP encryption format
        • 9.1.2.3 CCMP header
    • 9.2 Authentication and key management procedures
      • 9.2.1 Overview
      • 9.2.2 Authentication to the domain
        • 9.2.2.1 Authentication
          • 9.2.2.1.1 Authentication failure
          • 9.2.2.1.2 Successful authentication
          • 9.2.2.1.3 Authentication via proxy
        • 9.2.2.2 The PAK protocol parameters
          • 9.2.2.2.1 Node identifier
          • 9.2.2.2.2 Node password
          • 9.2.2.2.3 Diffie-Hellman prime
          • 9.2.2.2.4 Diffie-Hellman generator
          • 9.2.2.2.5 Secret exponents
          • 9.2.2.2.6 Hash functions
          • 9.2.2.2.7 NSC key
      • 9.2.3 Pair-wise authentication and generation of point-to-point keys
        • 9.2.3.1 Generation of point-to-point encryption keys
      • 9.2.4 Updating and termination of encryption keys
        • 9.2.4.1 Updating of NSC using the re-authentication procedure
        • 9.2.4.2 Updating of NN keys
        • 9.2.4.3 Termination of NSC and NN keys
        • 9.2.4.4 Updating of the DB keys and NMK
      • 9.2.5 Messages supporting AKM procedures
        • 9.2.5.1 Authentication messages
          • 9.2.5.1.1 Format of AUT_NodeAuthentication.req
          • 9.2.5.1.2 Format of AUT_Promp.ind
          • 9.2.5.1.3 Format of AUT_Verification.rsp
          • 9.2.5.1.4 Format of AUT_Confirmation.cnf
          • 9.2.5.1.5 Format of AUT_NodeAuthenticated.req
          • 9.2.5.1.6 Format of AUT_NodeAuthenticated.cnf
        • 9.2.5.2 Pair-wise authentication messages
          • 9.2.5.2.1 Format of AKM_KeyRequest.req
            • 9.2.5.2.1.1 Format of AKM_AddClient.req
          • 9.2.5.2.2 Format of AKM_NewKey.req
          • 9.2.5.2.3 Format of AKM_NewKey.cnf
          • 9.2.5.2.4 Format of AKM_KeyConfirmation.req
          • 9.2.5.2.5 Format of SC_DMRes.req
          • 9.2.5.2.6 Format of SC_DMRes.cnf
          • 9.2.5.2.7 Format of AKM_NewKey.ind
        • 9.2.5.3 Key updating messages
          • 9.2.5.3.1 Format of AKM_KeyUpdate.req
          • 9.2.5.3.2 Format of AKM_DomainKeyUpdate.req message
          • 9.2.5.3.3 Format of AKM_DomainKeyUpdate.cnf message
      • 9.2.6 Re-establishment of the security controller
        • 9.2.6.1 Security controller failure detection
        • 9.2.6.2 Security controller re-establishment procedure when the SC is allowed to change autonomously
        • 9.2.6.3 Security controller re-establishment procedure when a backup SC is assigned
      • 9.2.7 Handover of SC function
  • Annex A Application protocol convergence sublayer
    • A.1 Ethernet APC (EAPC)
      • A.1.1 Frame conversion
      • A.1.2 Classification
      • A.1.3 Flow control
      • A.1.4 Management plane
    • A.2 Other types of APC
  • Annex B to Annex W
  • Annex X Test vectors
    • X.1 CCM encryption
      • X.1.1 CCM test vector 1
        • X.1.1.1 Input parameters
        • X.1.1.2 Parameters generated
    • X.2 PAK test vectors
      • X.2.1 PAK test vector 1
      • X.2.1.1 Input parameters
      • X.2.1.2 Parameters generated or exchanged
    • X.3 Huffman coding
      • X.3.1 Test vector 1
        • X.3.1.1 Input (uncompressed) management message payload (MMPL)
        • X.3.1.2 Compressed management message payload
        • X.3.1.3 Uncompressed received management message payload
        • X.3.1.4 Output (uncompressed) management message payload (MMPL)
  • Bibliography