175
devices. Example product categories expected to adhere to this class include (but are not
limited to) end user communication appliances, such as IP Phones, PC-based softphones, or
other communication appliances that directly support the end user. Discovery services defined
in this class include provision of location identifier (including ECS / E911 information),
embedded L2 switch support, and inventory management.
LLDP-MED Capabilities describes the neighborhood unit's LLDP-MED capabilities. The
possible capabilities are: LLDP-MED capabilities, Network Policy, Location Identification,
Extended Power via MDI-PSE, and Extended Power via MDI – PD, Inventory, and Reserved.
Application Type indicating the primary function of the application(s) defined for this network
policy, advertised by an Endpoint or Network Connectivity Device. The possible application
types are shown below.
Voice – for use by dedicated IP Telephony handsets and other similar appliances
supporting interactive voice services. These devices are typically deployed on a
separate VLAN for ease of deployment and enhanced security by isolation from data
applications.
Voice Signaling - for use in network topologies that require a different policy for the
voice signaling than for the voice media.
Guest Voice - to support a separate limited feature-set voice service for guest users
and visitors with their own IP Telephony handsets and other similar appliances
supporting interactive voice services.
Guest Voice Signaling - for use in network topologies that require a different policy for
the guest voice signaling than for the guest voice media.
Softphone Voice - for use by softphone applications on typical data centric devices,
such as PCs or laptops.
Video Conferencing – for use by dedicated Video Conferencing equipment and other
similar appliances supporting real-time interactive video/audio services.
Steaming Video - for use by broadcast or multicast based video content distribution
and other similar applications supporting streaming video services that require
specific network policy treatment. Video applications relying on TCP with buffering
would not be an intended use of this application type.
Video Signaling - for use in network topologies that require a separate policy for
the video signaling than for the video media.
Policy indicates that an Endpoint Device wants to explicitly advertise that the policy is required
by the device. Can be either Defined or Unknown. Unknown: The network policy for the specified
application type is currently unknown.
Defined: The network policy is defined
TAG is indicative of whether the specified application type is using a tagged or an untagged
VLAN. Can be Tagged or Untagged.
Untagged: The device is using an untagged frame format and as such does not include a tag
header as defined by IEEE 802.1Q-2003.
Tagged: The device is using the IEEE 802.1Q tagged frame format.
VLAN ID is the VLAN identifier (VID) for the port as defined in IEEE 802.1Q-2003. A value of 1
through 4094 is used to define a valid VLAN ID. A value of 0 (Priority Tagged) is used if the device
is using priority tagged frames as defined by IEEE 802.1Q-2003, meaning that only the IEEE
802.1D priority level is significant and the default PVID of the ingress port is used instead.
Priority is the Layer 2 priority to be used for the specified application type. One of the eight
priority levels (0 through 7).
DSCP is the DSCP value to be used to provide Diffserv node behavior for the specified
application type as defined in IETF RFC 2474. Contain one of 6r code point values (0 through 63)
Identifies if MAC/PHY auto-negotiation is supported by the link partner.
Identifies if auto-negotiation is currently enabled at the link partner. If Auto-negotiation is
supported and Auto-negotiation status is disabled, the 802.3 PMD operating mode will be
determined the operational MAU type field value rather than by auto-negotiation.
Auto-negotiation
Capabilities
Displays the link partners MAC/PHY capabilities.
To Next Page