draft-ietf-ccamp-ospf-gmpls-extensions-03.txt		draft-ietf-ccamp-ospf-gmpls-extensions-04.txt
	CCAMP Working Group K. Kompella (Juniper Networks)		CCAMP Working Group K. Kompella (Juniper Networks)
	Internet Draft Y. Rekhter (Juniper Networks)		Internet Draft Y. Rekhter (Juniper Networks)
	Expiration Date: July 2002 A. Banerjee (Calient Networks)		Expiration Date: August 2002 A. Banerjee (Calient Networks)
	J. Drake (Calient Networks)		J. Drake (Calient Networks)
	G. Bernstein (Ciena)		G. Bernstein (Ciena)
	D. Fedyk (Nortel Networks)		D. Fedyk (Nortel Networks)
	E. Mannie (GTS Network)		E. Mannie (GTS Network)
	D. Saha (Tellium)		D. Saha (Tellium)
	V. Sharma (Metanoia, Inc.)		V. Sharma (Metanoia, Inc.)
	OSPF Extensions in Support of Generalized MPLS		OSPF Extensions in Support of Generalized MPLS
	draft-ietf-ccamp-ospf-gmpls-extensions-03.txt		draft-ietf-ccamp-ospf-gmpls-extensions-04.txt
	1. Status of this Memo		1. Status of this Memo
	This document is an Internet-Draft and is in full conformance with		This document is an Internet-Draft and is in full conformance with
	all provisions of Section 10 of RFC2026.		all provisions of Section 10 of RFC2026.
	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
	other groups may also distribute working documents as Internet-		other groups may also distribute working documents as Internet-
	Drafts.		Drafts.
	skipping to change at page 3, line 23		skipping to change at page 3, line 23
	In this section we define the enhancements to the TE properties of		In this section we define the enhancements to the TE properties of
	GMPLS TE links that can be announced in OSPF TE LSAs. The Traffic		GMPLS TE links that can be announced in OSPF TE LSAs. The Traffic
	Engineering (TE) LSA, which is an opaque LSA with area flooding scope		Engineering (TE) LSA, which is an opaque LSA with area flooding scope
	[3], has only one top-level Type/Length/Value (TLV) triplet and has		[3], has only one top-level Type/Length/Value (TLV) triplet and has
	one or more nested TLVs for extensibility. The top-level TLV can		one or more nested TLVs for extensibility. The top-level TLV can
	take one of two values (1) Router Address or (2) Link. In this		take one of two values (1) Router Address or (2) Link. In this
	document, we enhance the sub-TLVs for the Link TLV in support of		document, we enhance the sub-TLVs for the Link TLV in support of
	GMPLS. Specifically, we add the following sub-TLVs:		GMPLS. Specifically, we add the following sub-TLVs:
	1. Outgoing Interface Identifier,		1. Link Local Identifier,
	2. Incoming Interface Identifier,		2. Link Remote Identifier,
	3. Link Protection Type,		3. Link Protection Type,
	4. Shared Risk Link Group, and		4. Shared Risk Link Group, and
	5. Interface Switching Capability Descriptor.		5. Interface Switching Capability Descriptor.
	This brings the list of sub-TLVs of the TE Link TLV to:		This brings the list of sub-TLVs of the TE Link TLV to:
	Sub-TLV Type Length Name		Sub-TLV Type Length Name
	1 1 Link type		1 1 Link type
	2 4 Link ID		2 4 Link ID
	3 variable Local interface IP address		3 variable Local interface IP address
	skipping to change at page 4, line 7		skipping to change at page 4, line 7
	9 4 Resource class/color		9 4 Resource class/color
	11 4 Link Local Identifier		11 4 Link Local Identifier
	12 4 Link Remote Identifier		12 4 Link Remote Identifier
	14 4 Link Protection Type		14 4 Link Protection Type
	15 variable Interface Switching Capability Descriptor		15 variable Interface Switching Capability Descriptor
	16 variable Shared Risk Link Group		16 variable Shared Risk Link Group
	32768-32772 - Reserved for Cisco-specific extensions		32768-32772 - Reserved for Cisco-specific extensions
	5.1. Link Local Identifier		5.1. Link Local Identifier
	An Outgoing Interface Identifier is a sub-TLV of the Link TLV with		A Link Local Identifier is a sub-TLV of the Link TLV with type 11,
	type 11, and length 4.		and length 4.
	5.2. Link Remote Identifier		5.2. Link Remote Identifier
	An Incoming Interface Identifier is a sub-TLV of the Link TLV with		A Link Remote Identifier is a sub-TLV of the Link TLV with type 12,
	type 12, and length 4.		and length 4.
	5.3. Link Protection Type		5.3. Link Protection Type
	The Link Protection Type is a sub-TLV of the Link TLV, with type 14,		The Link Protection Type is a sub-TLV of the Link TLV, with type 14,
	and length of four octets, the first of which is a bit vector		and length of four octets, the first of which is a bit vector
	describing the protection capabilities of the link. They are:		describing the protection capabilities of the link. They are:
	0x01 Extra Traffic		0x01 Extra Traffic
	0x02 Unprotected		0x02 Unprotected
	skipping to change at page 6, line 25		skipping to change at page 6, line 25
	3.1.1 of [GMPLS-SIG].		3.1.1 of [GMPLS-SIG].
	Maximum LSP Bandwidth is encoded as a list of eight 4 octet fields in		Maximum LSP Bandwidth is encoded as a list of eight 4 octet fields in
	the IEEE floating point format, with priority 0 first and priority 7		the IEEE floating point format, with priority 0 first and priority 7
	last. The units are bytes (not bits!) per second.		last. The units are bytes (not bits!) per second.
	The content of the Switching Capability specific information field		The content of the Switching Capability specific information field
	depends on the value of the Switching Capability field.		depends on the value of the Switching Capability field.
	When the Switching Capability field is PSC-1, PSC-2, PSC-3, or PSC-4,		When the Switching Capability field is PSC-1, PSC-2, PSC-3, or PSC-4,
	the specific information includes Interface MTU and Minimum LSP		the specific information includes Interface MTU, Minimum LSP
	Bandwidth. The Interface MTU is encoded as a two octets integer. The		Bandwidth, and padding. The Interface MTU is encoded as a 2 octets
	Minimum LSP Bandwidth is is encoded in a 4 octets field in the IEEE		integer. The Minimum LSP Bandwidth is is encoded in a 4 octets field
	floating point format. The units are bytes (not bits!) per second.		in the IEEE floating point format. The units are bytes (not bits!)
			per second. The padding is 2 octets, and is used to make the
			Interface Switching Capability Descriptor sub-TLV 32-bits aligned.
	When the Switching Capability field is L2SC, there is no specific		When the Switching Capability field is L2SC, there is no specific
	information.		information.
	When the Switching Capability field is TDM, the specific information		When the Switching Capability field is TDM, the specific information
	includes Minimum LSP Bandwidth, and an indication whether the		includes Minimum LSP Bandwidth, an indication whether the interface
	interface supports Standard or Arbitrary SONET/SDH. The Minimum LSP		supports Standard or Arbitrary SONET/SDH, and padding. The Minimum
	Bandwidth is encoded in a 4 octets field in the IEEE floating point		LSP Bandwidth is encoded in a 4 octets field in the IEEE floating
	format. The units are bytes (not bits!) per second. The indication		point format. The units are bytes (not bits!) per second. The
	whether the interface supports Standard or Arbitrary SONET/SDH is		indication whether the interface supports Standard or Arbitrary
	encoded as 1 octet. The value of this octet is 0 if the interface		SONET/SDH is encoded as 1 octet. The value of this octet is 0 if the
	supports Standard SONET/SDH, and 1 if the interface supports		interface supports Standard SONET/SDH, and 1 if the interface
	Arbitrary SONET/SDH.		supports Arbitrary SONET/SDH. The padding is 3 octets, and is used
			to make the Interface Switching Capability Descriptor sub-TLV 32-bits
			aligned.
	When the Switching Capability field is LSC, there is no specific		When the Switching Capability field is LSC, there is no specific
	information.		information.
	The Interface Switching Capability Descriptor sub-TLV may occur more		The Interface Switching Capability Descriptor sub-TLV may occur more
	than once within the Link TLV (this is needed to handle interfaces		than once within the Link TLV (this is needed to handle interfaces
	that support multiple switching capabilities).		that support multiple switching capabilities).
	6. Security Considerations		6. Implications on Graceful Restart
			The restarting node should follow the OSPF restart procedures [OSPF-
			RESTART], and the RSVP-TE restart procedures [GMPLS-RSVP].
			Once the restarting node re-establishes at least one OSPF adjacency,
			the node should originate its TE LSAs. These LSAs should be
			originated with 0 unreserved bandwidth until the node is able to
			determine the amount of unreserved resources taking into account the
			resources reserved by the already established LSPs that have been
			preserved across the restart. Once the restarting node determines the
			amount of unreserved resources, taking into account the resources
			reserved by the already established LSPs that have been preserved
			across the restart, the node should advertise these resources in its
			TE LSAs.
			Neighbors of the restarting node should continue advertise the actual
			unreserved bandwidth on the TE links from the neighbors to that node.
			Regular graceful restart should not be aborted if a TE LSA or TE
			topology changes. TE graceful restart need not be aborted if a TE LSA
			or TE topology changes.
			7. Security Considerations
	The sub-TLVs proposed in this document does not raise any new		The sub-TLVs proposed in this document does not raise any new
	security concerns.		security concerns.
	7. Acknowledgements		8. Acknowledgements
	The authors would like to thank Suresh Katukam, Jonathan Lang and		The authors would like to thank Suresh Katukam, Jonathan Lang and
	Quaizar Vohra for their comments on the draft.		Quaizar Vohra for their comments on the draft.
	8. References		9. References
	[OSPF-TE] Katz, D., Yeung, D., "Traffic Engineering Extensions to		[OSPF-TE] Katz, D., Yeung, D., "Traffic Engineering Extensions to
	OSPF",		OSPF",
	draft-katz-yeung-ospf-traffic-04.txt (work in progress)		draft-katz-yeung-ospf-traffic-04.txt (work in progress)
	[GMPLS-SIG] "Generalized MPLS - Signaling Functional		[GMPLS-SIG] "Generalized MPLS - Signaling Functional
	Description", draft-ietf-mpls-generalized-signaling-04.txt (work		Description", draft-ietf-mpls-generalized-signaling-04.txt (work
	in progress)		in progress)
			[GMPLS-RSVP] "Generalized MPLS Signaling - RSVP-TE Extensions",
			draft-ietf-mpls-generalized-rsvp-te-06.txt (work in progress)
	[GMPLS-ROUTING] "Routing Extensions in Support of Generalized MPLS",		[GMPLS-ROUTING] "Routing Extensions in Support of Generalized MPLS",
	draft-ietf-ccamp-gmpls-routing-00.txt		draft-ietf-ccamp-gmpls-routing-01.txt (work in progress)
	9. Authors' Information		[OSPF-RESTART] "Hitless OSPF Restart", draft-ietf-ospf-hitless-
			restart-02.txt
			(work in progress)
			10. Authors' Information
	Kireeti Kompella		Kireeti Kompella
	Juniper Networks, Inc.		Juniper Networks, Inc.
	1194 N. Mathilda Ave		1194 N. Mathilda Ave
	Sunnyvale, CA 94089		Sunnyvale, CA 94089
	Email: kireeti@juniper.net		Email: kireeti@juniper.net
	Yakov Rekhter		Yakov Rekhter
	Juniper Networks, Inc.		Juniper Networks, Inc.
	1194 N. Mathilda Ave		1194 N. Mathilda Ave
End of changes.
This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/