draft-ietf-mpls-number-0-bw-te-lsps-10.txt   draft-ietf-mpls-number-0-bw-te-lsps-11.txt 
skipping to change at page 1, line 14 skipping to change at page 1, line 14
Intended status: Standards Track Matthew. R. Meyer Intended status: Standards Track Matthew. R. Meyer
Expires: February 19, 2009 Global Crossing Expires: February 19, 2009 Global Crossing
K. Kumaki K. Kumaki
KDDI Corporation KDDI Corporation
Alberto. Tempia Bonda Alberto. Tempia Bonda
Telecom Italia Telecom Italia
August 18, 2008 August 18, 2008
A Link-Type sub-TLV to convey the number of Traffic Engineering Label A Link-Type sub-TLV to convey the number of Traffic Engineering Label
Switched Paths signalled with zero reserved bandwidth across a link Switched Paths signalled with zero reserved bandwidth across a link
draft-ietf-mpls-number-0-bw-te-lsps-10 draft-ietf-mpls-number-0-bw-te-lsps-11
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 5, line 38 skipping to change at page 5, line 38
Value (4 octets): number of unconstrained TE LSP(s) signalled across Value (4 octets): number of unconstrained TE LSP(s) signalled across
the link. the link.
4. Elements of procedure 4. Elements of procedure
The absence of the Unconstrained TE LSP Count (sub-)TLV should be The absence of the Unconstrained TE LSP Count (sub-)TLV should be
interpreted as an absence of information about the link. interpreted as an absence of information about the link.
Similarly to other MPLS Traffic Engineering link characteristics, Similarly to other MPLS Traffic Engineering link characteristics,
LSA/LSP origination trigger mechanisms are outside the scope of this LSA/LSP origination trigger mechanisms are outside the scope of this
document. document. Care must be given to not trigger the systematic flooding
of a new IS-IS LSP or OSPF LSA with a too high granularity in case of
change of the number of unconstrained TE LSPs.
5. IANA Considerations 5. IANA Considerations
IANA has defined a sub-registry for the sub-TLVs carried in the IS-IS IANA has defined a sub-registry for the sub-TLVs carried in the IS-IS
TLV 22. IANA is requested to assign a new TLV code-point for the TLV 22. IANA is requested to assign a new TLV code-point for the
Unconstrained TE LSP Count sub-TLV carried within the TLV 22. Unconstrained TE LSP Count sub-TLV carried within the TLV 22.
Suggested Value TLV Name Reference Suggested Value TLV Name Reference
23 Unconstrained TE LSP Count (sub-)TLV This document 23 Unconstrained TE LSP Count (sub-)TLV This document
 End of changes. 2 change blocks. 
2 lines changed or deleted 4 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/