TLV 18 and TLV 35 details | docsis.org

You are here

TLV 18 and TLV 35 details

2 posts / 0 new
Last post
chun_chu
TLV 18 and TLV 35 details

Max cpe information related are stored in docsis config file as TLV 18 and TLV 35 ..but i cannot find more info on TLVs ..., any pointers ???

wittmann
Short view into the MULPI

MULPI: http://www.cablelabs.com/specifications/CM-SP-MULPIv3.0-I20-121113.pdf
Annex C Common TLV Encodings
Table C–1 - Summary of Top-Level TLV Encodings

TLV 18: Max Number of CPEs -> C.1.1.7

C.1.1.7: Maximum Number of CPEs
The maximum number of CPEs which can be granted access through a CM during a CM epoch. The CM epoch is
the time between startup and hard reset of the modem. The maximum number of CPEs MUST be enforced by the
CM.
NOTE: This parameter should not be confused with the number of CPE addresses a CM may learn. A modem may
learn Ethernet MAC addresses up to its maximum number of CPE addresses (from Section 9.1.2.1). The
maximum number of CPEs that are granted access through the modem is governed by this configuration
setting.
Type 18
Length 1
Value x
The CM MUST interpret this value as an unsigned integer. The non-existence of this option, or the value 0, MUST
be interpreted by the CM as the default value of 1.
NOTE: This is a limit on the maximum number of CPEs a CM will grant access to. Hardware limitations of a given
modem implementation may require the modem to use a lower value.

TLV 35: Subscriber Mgmt Control -> C.1.1.19.1

C.1.1.19.1 Subscriber Management Control
This three byte field provides control information to the CMTS for the Subscriber Management requirements in
[DOCSIS OSSIv3.0]. The first two bytes represent the number of IPv4 addresses permitted behind the CM. The
third byte is used for control fields.
Type 35
Length 3
Value
byte 1,2 MaxCpeIPv4 (low-order 10 bits)
byte 3, bit 0: Active
byte 3, bit 1: Learnable
byte 3, bits #2-7: reserved, must be set to zero

The realy cool point of DOCSIS is to have a very good and open specification!

Best regards,

wittmann

Log in or register to post comments