![]() The existing IS reachability (TLV type 2, defined in ISO 10589 The extended IS reachability TLV is TLV type 22. ![]() The IS-IS working group has disbanded, the review shall be performedīy a Designated Expert assigned by the responsible Area Director. This will normally require publication of additionalĭocumentation describing how the new type is used. New type values are allocated following review on the IETF IS-IS The Sub-TLV type space is managed by the IETF IS-IS WG. Sub-TLV can be computed from the length of the whole sub-TLV, when The Lengthįield indicates the length of the Value field in octets. The Typeįield indicates the type of items in the Value field. Each sub-TLV consists of three fields, a one-octet Type field,Ī one-octet Length field, and zero or more octets of Value. Sub-TLVs are used to add extra information to particular TLVs are used to add extra information to IS-IS Theĭifference is that TLVs exist inside IS-IS packets, while sub-TLVsĮxist inside TLVs. They use the same concepts as regular TLVs. This document introduces a new way to encode routing information in "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in thisĭocument are to be interpreted as described in RFC 2119. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", Mechanisms and procedures to migrate to the new TLVs are notĪ prior version of this document was published as with The router ID is useful for traffic engineering purposes because itĭescribes a single address that can always be used to reference a Increasing the dynamic range of the IS-IS metric and improving the The characteristics described in this document are neededįor traffic engineering. Information about the characteristics of a particular link to an IS. IS Neighbor TLV and IP Reachability TLV, and to include additional This document contains the design of new TLVs to replace the existing TLVs, and are a good way of encoding information in a flexible and Is composed of a fixed header and a number of tuples, each consisting State Protocol Data Units (LSPs) with routing information. Intermediate System (IS) (router) advertises one or more IS-IS Link The IS-IS protocol is specified in ISO 10589, withĮxtensions for supporting IPv4 specified in. Sub-TLVs for the Extended IP Reachability TLV. Sub-TLVs for the Extended IS Reachability TLV. Expandability of the Extended IP Reachability TLV Sub-TLV 18: Traffic Engineering Default Metric. Sub-TLV 10: Maximum Reservable Link Bandwidth. Sub-TLV 3: Administrative Group (color, resource class). RFC 5305 IS-IS Extensions for Traffic Engineering October 2008ġ. This information describesĪdditional details regarding the state of the network that are useful Information that an Intermediate System (router) can place in Link This document extends the IS-IS protocol by specifying new Intermediate System (IS-IS) protocol to support Traffic Engineering This document describes extensions to the Intermediate System to Official Protocol Standards" (STD 1) for the standardization stateĪnd status of this protocol. Please refer to the current edition of the "Internet Internet community, and requests discussion and suggestions for This document specifies an Internet standards track protocol for the Request for Comments: 5305 Redback Networks, Inc. ![]() Updated by: 5307, 8918 Network Working Group T. RFC 5305: IS-IS Extensions for Traffic Engineering
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |