Approved
|
LLDP frames generated by the telephone will not be tagged (see 96x1H-IPI.5.1.220).
LLDP will be supported if IPv4-only or dual-stack operation is enabled, but not if IPv6-only operation is enabled.
|
Rationale:
|
While IEEE 802.1AB does not specify that LLDP frames not be tagged, some vendors’ switches will not process tagged LLDP frames.
|
Approved
|
The transmission of the following TLVs (Type-Length-Value elements) will be supported:
|
Category
|
TLV Name
(Type)
|
Info String Length
|
TLV Info String
(Value)
|
Notes
(references)
|
Basic Mandatory
|
Chassis ID
|
6
|
subtype 5: Network address (one octet); use IANA value for IPv4 = 1 (one octet)
and IPADD (4 octets)
|
Section 9.5.2 of [7.2-8a],
Section 9.2 of [7.7-1]
http://www.iana.org/assignments/address-family-numbers
96x1H-IPI.2.1.600
|
Basic Mandatory
|
Port ID
|
7
|
subtype 3: MAC address (one octet);
MAC address of the telephone (6 octets)
|
Section 9.5.3 of [7.2-8a]
Section 9.2 of [7.7-1]
|
Basic Mandatory
|
Time-To-Live
|
2
|
120 seconds
|
Section 9.5.4 and
Section 10.5.4.1 of [7.2-8a]
|
Basic Optional
|
System Name
|
9
|
the Host Name specified for DHCP option 12
|
Section 9.5.6 of [7.2-8a],
96x1H-IPI.5.1.604
|
Basic Optional
|
System Capabilities
|
4
|
Bit 2 (Bridge) will be set in the System Capabilities octets if the telephone has an internal Ethernet switch; it will be set in the Enabled Capabilities octets if PHY2STAT is not “0”.
Bit 5 (Telephone) will always be set in the System Capabilities octets; it will be set in the Enabled Capabilities octets if it is currently registered for service.
|
Section 9.5.8 of [7.2-8a]
|
Basic Optional
|
Management Address
|
23
|
Mgmt addr string length = 5
Mgmt address subtype = 1 (IPv4)
Mgmt address = IPADD (4 octets)
Interface number subtype = 3 (system port)
Interface number = 1
OID string length = 11
OID = SNMP MIB-II sysObjectID converted to hexadecimal per ITU X.690 [7.4-13] as shown below:
|
Section 9.5.9 of [7.2-8a],
96x1H-IPI.5.1.1100
ITU X.690
|
|
|
|
2B
|
06
|
01
|
04
|
01
|
B5 69
|
01
|
45
|
05
|
x
|
hex
|
|
|
|
1.3
|
.6
|
.1
|
.4
|
.1
|
.6889
|
.1
|
.69
|
.5
|
.x
|
OID
|
IEEE 802.3 Organization Specific
|
MAC / PHY Configuration / Status
|
9
|
802.3 OUI = 00-12-0F (hex)
802.3 subtype = 1
auto-negotiation support/status
= 3 if PHY1STAT is “1”, or
= 1 if PHY1STAT is not “1”.
PMD auto-negotiation advertised capability
= values sent during link auto-negotiation
if PHY1STAT is 1, or
= 0 if PHY1STAT is not “1”.
operational MAU type
= 10 if Ethernet line interface is operating
at 10Mbps, half-duplex,
= 11 if Ethernet line interface is operating
at 10Mbps, full-duplex,
= 15 if Ethernet line interface is operating
at 100Mbps, half-duplex,
= 16 if Ethernet line interface is operating
at 100Mbps, full-duplex,
= 29 if Ethernet line interface is operating
at 1000Mbps, half-duplex,
= 30 if Ethernet line interface is operating
at 1000Mbps, full-duplex.
|
Section G.2 of [7.2-8a]
96x1H-IPI.5.1.100
RFC 3636, pp.41-42
and see Note below
RFC 3636, p.12-14
|
Note:
|
At the IEEE 802.1 Closing Plenary meeting in November, 2007, the following interpretation was approved as to the proper bit ordering of the two PMD (Physical Media Dependent) auto-negotiation advertised capability octets in the 802.3 MAC/PHY Configuration/Status TLV: “Bit 0 of the ifMauAutoNegCapAdvertisedBits data type would properly be encoded in bit 8 (the most significant bit) of the first octet of the LLDP PMD auto-negotiation advertised capability field, and bits 0 through 7 of the bitstring are encoded in bits 8 through 1 of the capability field, respectively, with bits 8 through 15 of the bitstring being encoded in bits 8 through 1 of the second octet of the field. The above describes the bit and octet ordering in the LLDPDU that is passed across the MAC service boundary between LLDP and the underlying MAC service. Naturally, the representation of the data in this field in the MAC data frames, and the subsequent physical encoding, will follow whatever rules apply to the MAC/PHY technology that supports the operation of the protocol.”
|
TIA LLDP MED
|
LLDP-MED Capabilities
|
7
|
TIA OUI = 00-12-BB (hex)
LLDP Capabilities Subtype = 1
LLDP-MED Capabilities = 00-33
(Inventory, Power-via-MDI,
Network Policy, MED Caps)
LLDP-MED Device Type = 3 (Class III)
|
Section 10.2.2 of [7.7-1]
|
TIA LLDP MED
|
Extended
Power-Via-MDI
|
7
|
TIA OUI = 00-12-BB (hex)
Extended Power via MDI Subtype = 4
Power Type = 01 (PD Device)
Power Source = 01 if powered via PoE,
= 10 if powered locally
Power Priority = 0010 (High)
Power Value = 0 if the telephone is not
currently powered via PoE, otherwise the
maximum power usage of the telephone plus
all modules and adjuncts powered by the
telephone, in integer tenths of a watt.
|
Section 10.2.5 of [7.7-1]
See the table in the Note in
9xxxHW.2.5.100 of [7.1-2]
|
TIA LLDP MED
|
Network Policy
(Voice)
|
8
|
TIA OUI = 00-12-BB (hex)
Network Policy Subtype = 2
Application Type = 1 (Voice)
U = 0 (network policy is defined)
T = 1 if tagging, 0 if not tagging
X = 0 (reserved bit)
VLAN ID = endptL2QVLAN (in-use value)
L2 Priority = L2QAUD
DSCP value = DSCPAUD or DSCPBBE
whichever is in effect
|
Section 10.2.3 of [7.7-1]
96x1H-IPI.5.1.220
96x1H-IPI.5.1.1100
96x1H-IPI.2.1.1200
96x1H-IPI.2.1.1200,
96x1H-IPI.2.1.1400, and 96x1H-IPI.5.1.304
|
TIA LLDP MED
|
Inventory – Hardware Revision
|
12 to 14
|
TIA OUI = 00-12-BB (hex)
Hardware Revision Subtype = 5
Hardware Revision = MODEL
|
Section 10.2.6.1 of [7.7-1]
96x1H-IPI.2.1.100
|
TIA LLDP MED
|
Inventory – Firmware Revision
|
5 to 36
|
TIA OUI = 00-12-BB (hex)
Firmware Revision Subtype = 6
Firmware Revision = RFSINUSE
|
Section 10.2.6.2 of [7.7-1]
96x1H-IPI.2.1.1200
|
TIA LLDP MED
|
Inventory – Software
Revision
|
5 to 36
|
TIA OUI = 00-12-BB (hex)
Software Revision Subtype = 7
Software Revision = APPINUSE
|
Section 10.2.6.3 of [7.7-1]
96x1H-IPI.2.1.1200
|
TIA LLDP MED
|
Inventory –
Serial Number
|
16 to 22
|
TIA OUI = 00-12-BB (hex)
Serial Number Subtype = 8
Serial Number = SERIALNO
|
Section 10.2.6.4 of [7.7-1]
96x1H-IPI.2.1.1400
|
TIA LLDP MED
|
Inventory –
Manufacturer Name
|
9
|
TIA OUI = 00-12-BB (hex)
Manufacturer Name Subtype = 9
Manufacturer Name = Avaya
|
Section 10.2.6.5 of [7.7-1]
|
TIA LLDP MED
|
Inventory –
Model Name
|
8
|
TIA OUI = 00-12-BB (hex)
Model Name Subtype = 10
Model Name = MODEL with the final “Dxxx”
characters removed
|
Section 10.2.6.6 of [7.7-1]
96x1H-IPI.2.1.100,
9xxxHW.2.0.100 of [7.1-2]
|
Avaya/Extreme Proprietary
|
PoE Conservation Level Support
|
9 or 11
|
OUI = 00-40-0D (hex)
Subtype = 1
Current conservation level = 1 if and only if
power conservation is supported and active,
otherwise 0.
|
Section 7.1.1.1 of [7.1-25]
96x1COPS.5.3.200 of [7.1-4]
|
|
|
|
Typical power value = 0 if the telephone is not
currently powered via PoE, otherwise the
typical power usage of the telephone plus all
modules and adjuncts powered by the
telephone, with backlight(s) (if any) on at
default brightness, in integer tenths of a watt.
|
See the Table in the Note in
9xxxHW.2.5.100 of [7.1-2]
|
|
|
|
Max power value = 0 if the telephone is not
currently powered via PoE, otherwise the
maximum power usage of the telephone plus
all modules and adjuncts powered by the
telephone, in integer tenths of a watt.
|
See the Table in the Note in
9xxxHW.2.5.100 of [7.1-2]
|
|
|
|
Conservation level 1 = typical power usage of
the telephone plus all modules and adapters
powered by the telephone with power
conservation mode enabled, in integer tenths
of a watt. Conservation level 1 octets will be
included if and only if the telephone
supports power conservation.
|
See the Table in the Note in
9xxxHW.2.5.100 of [7.1-2]
96x1COPS.5.3.200 of [7.1-4]
|
Avaya/Extreme Proprietary
|
Call Server IP Address
|
8
|
OUI = 00-40-0D (hex)
Subtype = 3
Call Server IPv4 Address = endptGKINUSE
|
Section 7.1.2.1 of [7.1-25]
96x1H-IPI.5.1.1100, Group 6
|
Avaya/Extreme Proprietary
|
IP Phone Addresses
|
16
|
OUI = 00-40-0D (hex)
Subtype = 4
Phone IPv4 Address = IPADD
Phone Address Mask = NETMASK
Gateway IPv4 address = endptGIPINUSE
|
Section 7.1.2.2 of [7.1-25]
96x1H-IPI.2.1.600,
96x1H-IPI.2.1.600,
96x1H-IPI.5.1.1100, Group 1
|
Approved
|
The shutdown LLDPDU (see Section 10.2.1.2 of [7.2-8a]) will not be transmitted.
A received LLDP frame will be processed if and only if the received frame has the LLDP reserved group multicast address (01-80-C2-00-00-0E, see Section 8.1 of 802.1AB [7.2-8a] or Section 7.12 of 802.1D [7.2-4]) as the destination MAC address and an Ethernet Protocol Type of 88-CC. If a received frame contains a TIA LLDP-MED Capabilities TLV, other TLVs in the frame will be processed if and only if the TIA LLDP-MED Capabilities TLV contains a Device Type of 0 or 4. TLVs will be processed in the order that they are received. If the processing of a TLV causes the telephone to reset, remaining unprocessed TLVs will be discarded. After a power-up or reset but before registration with a call server, received TLVs will be buffered for processing only at specific times as specified in the flowcharts in 96x1H-IPI.3.1.100, as well as in 96x1H-IPI.5.1.604 and 96x1H-IPI.5.1.606.
If an organizationally-specific IEEE 802.1 Port VLAN ID TLV (see Section F.2 of [7.2-8a]) is received, the value of the parameter PHY2VLAN will be set to the Port VLAN identifier in the TLV.
If an organizationally-specific IEEE 802.1 VLAN Name TLV (see Section F.4 of [7.2-8a]) is received, it will be processed as specified in the following flowchart.
|
|
Approved
|
If a TIA LLDP MED Network Policy TLV (see Section 10.2.3 of [7.7-1]) is received, it will be processed as specified in the following flowchart.
|
Note:
|
L2QVLAN must also be marked as not having been set via LLDP any time it is set via some other mechanism, i.e., via NVL2QVLAN at start-up or after a reset, via a name=value pair in a DHCPACK message, via a SET command in a script file, or via H.323 signaling (in a layer2param non-standard data element).
|
|
Approved
|
If a TIA LLDP MED Extended Power-Via-MDI TLV (see Section 10.2.5 of [7.7-1]) is received,
power conservation mode will be enabled if the received binary Power Source value is 10, and
power conservation mode will be disabled if the received binary Power Source value is not 10.
|
Note:
|
While it is not expected that both TIA LLDP MED Extended Power-Via-MDI TLVs and Avaya/Extreme Proprietary PoE Conservation Level Request TLVs would be received, either could enable or disable power conservation mode.
|
Rationale:
|
Power conservation mode will be enabled even if the telephone is not powered over Ethernet because the telephone sends information about the power source that it is using in a TIA LLDP MED Extended Power-Via-MDI TLV, so it is assumed that the power management system intends to conserve local power as well.
|
Approved
|
If an Avaya/Extreme Proprietary Call Server TLV (see Section 7.1.2.1 of [7.1-25]) is received, the value of MCIPADD will be set to the IP address(es) in this TLV (converted to a comma-separated list) if and only if the value of MCIPADD is null or all zeroes when the TLV is processed.
If an Avaya/Extreme Proprietary File Server TLV (see Section 7.1.2.4 of [7.1-25]) is received, the values of TLSSRVR and HTTPSRVR will be set to the IP address(es) in this TLV (converted to a comma-separated list) if and only if the values of both are null or all zeroes when the TLV is processed.
If an Avaya/Extreme Proprietary 802.1Q Framing TLV (see Section 7.1.3.1 of [7.1-25]) is received,
if the current value of L2QVLAN was set via an IEEE 802.1 VLAN Name TLV,
or if the current value of L2QVLAN was set via a TIA LLDP MED Network Policy TLV:
the 802.1Q Framing TLV will be ignored.
Otherwise:
if the 802.1Q Framing value is 1, L2Q will be set to “1” (on),
if the 802.1Q Framing value is 2, L2Q will be set to “2” (off), and
if the 802.1Q Framing value is 3, L2Q will be set to “0” (auto),
but the state of tagging is not changed when the TLV is processed.
If an Avaya/Extreme Proprietary PoE Conservation Level Request TLV (see Section 7.1.1.2 of [7.1-25]) is received, power conservation mode will be enabled if the requested conservation level is 1 and power conservation mode will be disabled if the requested conservation level is 0 (see 96x1COPS.5.3.200 of [7.1-4]).
All other received TLVs will be ignored.
Support of the LLDP MIB (see Section 12 of [7.2-8a]) and the IEEE 802.1/LLDP Extension MIB (see Section F.7 of [7.2-8a]) is not required.
|
Note:
|
IEEE 802.1 TLV extensions are specified in Annex F of [7.2-8a].
IEEE 802.3 TLV extensions are specified in Annex G of [7.2-8a].
|
Rationale:
|
LLDP was created as a standard alternative to the proprietary CDP (Cisco Discovery Protocol).
LLDP frames are not forwarded because frames addressed to the reserved group multicast addresses are not supposed to be forwarded (see Section 7.12.6 of [7.2-4]), and because they could convey misleading information to the network access switch (e.g., a PC could respond with a speed/duplex setting that is not the same as that being used by the telephone’s Ethernet line interface).
Unicast LLDP messages are not processed because they could be spoofed to disruptively reset the phone onto a bogus VLAN.
|
