{"id":690529,"date":"2024-11-06T05:22:25","date_gmt":"2024-11-06T05:22:25","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/tia-10572006-r2011\/"},"modified":"2024-11-06T05:22:25","modified_gmt":"2024-11-06T05:22:25","slug":"tia-10572006-r2011","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/tia\/tia-10572006-r2011\/","title":{"rendered":"TIA-1057:2006 (R2011)"},"content":{"rendered":"
This Standard defines a set of organizationally-specific IEEE
\n802.1AB TLV extensions and a related MIB module, for the purpose of
\nimproved deployment properties and multi-vendor interoperability
\nbetween VoIP endpoint devices and IEEE 802 networking
\ninfrastructure elements. Where required for correct multi-vendor
\ninteroperation, specific constraints on IEEE 802.1AB protocol
\nbehavior, application-level interaction with the protocol elements,
\nas well as constraints on existing IEEE 802.1AB TLVs and related
\nMIB module, are also defined.<\/p>\n
This Standard is applicable to all VoIP network edge devices
\nsuch as (but not limited to) IP Phones, Voice \/ Media Gateways,
\nMedia Servers, IP Communications Controllers or other VoIP devices
\nor servers, as well as to network access elements such as (but not
\nlimited to) IEEE 802 LAN Bridges or Wireless Access Points, and L2
\nor L3 switches or routers which are connected within IEEE 802
\nLANs.<\/p>\n
This Standard specifically addresses usage of LLDP and the
\nextensions defined herein within IEEE 802 LAN environments. This
\nStandard may also be applicable to IEEE 802 MAN environments (IEEE
\n802.1AB is not specific to this, however there are no defined
\nlimits).<\/p>\n
This Standard is specifically defined for use between VoIP
\nendpoints and LAN network access elements, and as such is not
\nintended for use on links between LAN infrastructure elements.<\/p>\n
This Standard is international in scope.<\/p>\n
This Standard conforms to and harmonizes with other existing,
\nreferenced TIA, ANSI, ISO, IEEE, IETF, ETSI, ITU-T and other
\nstandards. Specifically, this Standard conforms to IEEE 802.1AB [1]
\nand use of the extension mechanisms defined as part of that
\nStandard, as well as to applicable IEEEdefined pre-existing
\nextensions to IEEE 802.1AB as published in Annexes F (802.1
\nextensions) and Annex G (802.3 extensions) of that Standard.<\/p>\n
This Standard does not address interactions between IEEE 802.1AB
\nand other link level protocols such as IEEE 802.1X or IEEE
\n802.3af.<\/p>\n
This Standard is not specific to any particular VoIP control
\narchitecture, signaling or other higher-level protocol (e.g. SIP,
\nMegaco \/ H.248, H.323, etc).<\/p>\n
This Standard is not specific to any particular system
\nmanagement architecture, and does not mandate use of SNMP or other
\nparticular management protocol.<\/p>\n
This Standard does not place any application-level requirements
\non interaction between system components such as control signaling,
\nsetting of policies, gathering of management information, or usage
\nof the information provided.<\/p>\n
Scope of Current Standard Release<\/strong><\/p>\n In this release of this Standard, the following capabilities are \u2022 LAN speed and duplex in use, 2-way advertisement (see section \u2022 Network policy discovery, including VLAN id, 802.1p priority \u2022 Device location and topology discovery based on LAN-level \u2022 IP Phone location identification, including emergency call \u2022 Endpoint Location Identification Discovery). Endpoint move \u2022 Extended Power over Ethernet (PoE) discovery for fine-grained \u2022 Extended device identification for inventory management, 1-way \u2022 Identification of endpoint-embedded network connectivity \u2022 Application level interactions with the LLDP protocol elements \u2022 Applicability of LLDP-MED to Wireless LAN environments Note that some of these capabilities are based on newly defined It is considered that future iterations of this Standard can Future Considerations<\/strong><\/p>\n The following were considered for inclusion in this release of \u2022 IP Phone advertisement of its dialable phone number, URI or \u2022 Extended device class definitions such as basic IP phone, \u2022 Media type(s) supported (voice, video, text conversation, \u2022 Media bandwidth requirement(s) advertise by endpoint.<\/p>\n \u2022 Device operational status.<\/p>\n \u2022 Device mobility.<\/p>\n \u2022 IP Phone advertisement of ECS calls in progress.<\/p>\n \u2022 Specific extensions for usage of LLDP-MED in Wireless LAN Purpose<\/strong><\/p>\n This Standard fills a recognized need in the Voice Over IP To fulfill these needs, this Standard provides extensions to LLDP extensions and behavior requirements are described Telecommunications – IP Telephony Infrastructure – Link Layer Discovery Protocol for Media Endpoint Devices<\/b><\/p>\n
\nfully specified. More detailed functional descriptions of these
\ncapabilities, as well as specific references to implementation
\nsections, are given in section 7, Media Endpoint Discovery
\nFunctional Description.<\/p>\n
\n7.2, LAN Speed and Duplex Discovery).<\/p>\n
\nand Diffserv code point (DSCP), 2-way advertisement (see section
\n7.3, Network Policy Discovery).<\/p>\n
\nMAC\/port information, 2-way advertisement (see section 7.4, LAN
\nLevel Endpoint Location Discovery).<\/p>\n
\nservice location, based on IETF and NENA-defined location objects,
\n1-way advertisement from LAN infrastructure element to endpoint
\n(see section 7.5,<\/p>\n
\ndetection notification from network connectivity device to their
\nassociated VoIP management application(s), using SNMP or similar
\n(see section 7.6, Endpoint Move Detection Notification).<\/p>\n
\npower management, 2-way advertisement (see section 7.7, Extended
\nPower Via MDI Discovery).<\/p>\n
\nadvertisement from endpoint to LAN infrastructure element (see
\nsection 7.8, Inventory Management Discovery).<\/p>\n
\ncapabilities (e.g. multi-port IP Phone with embedded L2 switch or
\nbridge capability), 1-way advertisement from endpoint to LAN
\ninfrastructure element (see section 7.9, Embedded Network
\nConnectivity Discovery).<\/p>\n
\nto provide timely startup of LLDP to support rapid availability of
\nEmergency Call Service (see section 7.10, LLDP-MED Fast Start
\nProtocol Behavior).<\/p>\n
\n(Informative, see ANNEX B: LLDPMED Support for Voice over Wireless
\nLAN).<\/p>\n
\nTLVs and the related MIB module defined herein, while others of
\nthese capabilities are based on previously defined TLVs and related
\nMIB modules from the IEEE 802.1AB base specification [1].<\/p>\n
\npotentially add expanded support in the above or related areas, and
\nalso for other types of media endpoints, such as video devices.
\nRefer to section 2.2 Future Considerations for a listing of future
\nitems considered, but not specified in this release of this
\nStandard.<\/p>\n
\nthis Standard, but are now considered candidates for future
\nreleases, and every effort is made to provide for extensibility to
\nthese and other capabilities:<\/p>\n
\nother callable address.<\/p>\n
\nvideo phone, web phone, etc.<\/p>\n
\netc).<\/p>\n
\nenvironments.<\/p>\n
\n(VoIP) industry, brought about by the use of equipment supplied by
\nmany different manufacturers, along with the need for
\ncost-effective, readily deployable, and easily managed solutions.
\nIn particular, the needs for deployment of VoIP equipment into IEEE
\n802 – based LAN environments are addressed. It will be useful to
\nanyone engaged in the manufacture of VoIP equipment and related
\nproducts, as well as to those purchasing, operating or using such
\nproducts. It is internationally applicable.<\/p>\n
\nIEEE 802.1AB that are specific to the requirements of Media
\nEndpoint Devices in an IEEE 802 LAN environment. Specific usage of
\nthe IEEE 802.1AB LLDP base specification is also defined.
\nInteraction behavior between the Media Endpoint Devices and the LAN
\ninfrastructure elements are also described where they are relevant
\nto correct operation or multi-vendor interoperability.<\/p>\n
\nspecifically in the areas of network configuration and policy,
\ndevice location (including for Emergency Call Service \/ E911),
\nPower over Ethernet management, and inventory management.
\nExtensibility mechanisms to allow for future work in this area are
\nalso provided where possible.<\/p>\n","protected":false},"excerpt":{"rendered":"\n\n
\n Published By<\/td>\n Publication Date<\/td>\n Number of Pages<\/td>\n<\/tr>\n \n TIA<\/b><\/a><\/td>\n 2006<\/td>\n 134<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"featured_media":690537,"template":"","meta":{"rank_math_lock_modified_date":false,"ep_exclude_from_search":false},"product_cat":[2646],"product_tag":[],"class_list":{"0":"post-690529","1":"product","2":"type-product","3":"status-publish","4":"has-post-thumbnail","6":"product_cat-tia","8":"first","9":"instock","10":"sold-individually","11":"shipping-taxable","12":"purchasable","13":"product-type-simple"},"_links":{"self":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product\/690529","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product"}],"about":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/types\/product"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media\/690537"}],"wp:attachment":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media?parent=690529"}],"wp:term":[{"taxonomy":"product_cat","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_cat?post=690529"},{"taxonomy":"product_tag","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_tag?post=690529"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}