draft-ietf-ccamp-swcaps-update-01.txt		draft-ietf-ccamp-swcaps-update-02.txt
	Internet Draft Lou Berger		Internet Draft Lou Berger
	Updates: 3471, 4202, 4203, 5307 (LabN)		Updates: 3471, 4202, 4203, 5307 (LabN)
	Category: Standards Track Julien Meuric		Category: Standards Track Julien Meuric
	Expiration Date: October 17, 2013 (France Telecom Orange)		Expiration Date: February 22, 2014 (France Telecom Orange)
	April 17, 2013		August 22, 2013
	Revised Definition of The GMPLS Switching Capability and Type Fields		Revised Definition of The GMPLS Switching Capability and Type Fields
	draft-ietf-ccamp-swcaps-update-01.txt		draft-ietf-ccamp-swcaps-update-02.txt
	Abstract		Abstract
	GMPLS provides control for multiple switching technologies, and		GMPLS provides control for multiple switching technologies, and
	hierarchical switching within a technology. GMPLS routing and		hierarchical switching within a technology. GMPLS routing and
	signaling use common values to indicate switching technology type.		signaling use common values to indicate switching technology type.
	These values are carried in routing in the Switching Capability		These values are carried in routing in the Switching Capability
	field, and in signaling in the Switching Type field. While the		field, and in signaling in the Switching Type field. While the
	values used in these fields are the primary indicators of the		values used in these fields are the primary indicators of the
	technology and hierarchy level being controlled, the values are		technology and hierarchy level being controlled, the values are
	skipping to change at page 1, line 51		skipping to change at page 1, line 51
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/1id-abstracts.html		http://www.ietf.org/1id-abstracts.html
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html		http://www.ietf.org/shadow.html
	This Internet-Draft will expire on October 17, 2013		This Internet-Draft will expire on February 22, 2014
	Copyright and License Notice		Copyright and License Notice
	Copyright (c) 2013 IETF Trust and the persons identified as the		Copyright (c) 2013 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 6, line 5		skipping to change at page 6, line 5
	2.3. Assigned Switching Types		2.3. Assigned Switching Types
	This document deprecates the following Switching Types:		This document deprecates the following Switching Types:
	Value Name		Value Name
	2 Packet-Switch Capable-2 (PSC-2)		2 Packet-Switch Capable-2 (PSC-2)
	3 Packet-Switch Capable-3 (PSC-3)		3 Packet-Switch Capable-3 (PSC-3)
	4 Packet-Switch Capable-4 (PSC-4)		4 Packet-Switch Capable-4 (PSC-4)
	These values SHOULD NOT be treated as reserved values, i.e.,		These values SHOULD be treated as unsupported types and, in the
	SHOULD NOT be generated and SHOULD be ignored upon receipt.		case of signaling, processed according to Section 2.1.1 of
			[RFC3473].
	3. Compatibility		3. Compatibility
	For existing implementations, the primary impact of this document is		For existing implementations, the primary impact of this document is
	deprecating the use of PSC-2, 3 and 4. At the time of publication,		deprecating the use of PSC-2, 3 and 4. At the time of publication,
	there are no known deployments (or even implementations) that make		there are no known deployments (or even implementations) that make
	use of these values so there is no compatibility issues for current		use of these values so there is no compatibility issues for current
	routing and signaling implementations.		routing and signaling implementations.
	4. Security Considerations		4. Security Considerations
	skipping to change at page 6, line 28		skipping to change at page 6, line 29
	This document impacts the values carried in a single field in		This document impacts the values carried in a single field in
	signaling and routing. As no new protocol formats or mechanisms are		signaling and routing. As no new protocol formats or mechanisms are
	defined, there are no particular security implications raised by this		defined, there are no particular security implications raised by this
	document.		document.
	For a general discussion on MPLS and GMPLS related security issues,		For a general discussion on MPLS and GMPLS related security issues,
	see the MPLS/GMPLS security framework [RFC5920].		see the MPLS/GMPLS security framework [RFC5920].
	5. IANA Considerations		5. IANA Considerations
	IANA needs to deprecate and redefine the registry. In particular the		IANA needs to deprecate and redefine the related registry. In
	Switching Types portion of the Generalized Multi-Protocol Label		particular the Switching Types portion of the Generalized Multi-
	Switching (GMPLS) Signaling Parameters should be revised to read:		Protocol Label Switching (GMPLS) Signaling Parameters should be
			revised to read:
	Switching Types		Switching Types
	Registration Procedures		Registration Procedures
	Standards Action		Standards Action
	Reference		Reference
	[RFC3471][RFC4328][This.draft]		[RFC3471][RFC4328][This.draft]
	skipping to change at page 7, line 15		skipping to change at page 7, line 17
	52-99 Unassigned		52-99 Unassigned
	100 Time-Division-Multiplex Capable (TDM) [RFC3471]		100 Time-Division-Multiplex Capable (TDM) [RFC3471]
	101-124 Unassigned		101-124 Unassigned
	125 Data Channel Switching Capable (DCSC) [RFC6002]		125 Data Channel Switching Capable (DCSC) [RFC6002]
	126-149 Unassigned		126-149 Unassigned
	150 Lambda-Switch Capable (LSC) [RFC3471]		150 Lambda-Switch Capable (LSC) [RFC3471]
	151-199 Unassigned		151-199 Unassigned
	200 Fiber-Switch Capable (FSC) [RFC3471]		200 Fiber-Switch Capable (FSC) [RFC3471]
	201-255 Unassigned		201-255 Unassigned
			A parallel change to IANA-GMPLS-TC-MIB is also required. In
			particular, under IANAGmplsSwitchingTypeTC a reference to this
			document should be added as item 3. Also the following changes should
			be made to the related values:
			deprecated(2), -- Deprecated
			deprecated(3), -- Deprecated
			deprecated(4), -- Deprecated
	6. Acknowledgments		6. Acknowledgments
	We thank John Drake for highlighting the current inconsistent		We thank John Drake for highlighting the current inconsistent
	definitions associated with the Switching Capability and Type Fields.		definitions associated with the Switching Capability and Type Fields.
	Daniele Ceccarelli provided valuable feedback on this document.		Daniele Ceccarelli and Adrian Farrel provided valuable feedback on
			this document.
	7. References		7. References
	7.1. Normative References		7.1. Normative References
	[RFC2119] Bradner, S., "RFC Key Words Key words for use in RFCs to		[RFC2119] Bradner, S., "RFC Key Words Key words for use in RFCs to
	Indicate Requirement Levels", RFC 2119, March 1997.		Indicate Requirement Levels", RFC 2119, March 1997.
	[RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching		[RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching
	(GMPLS) Signaling Functional Description", RFC 3471,		(GMPLS) Signaling Functional Description", RFC 3471,
	skipping to change at line 398		skipping to change at line 411
	Email: lberger@labn.net		Email: lberger@labn.net
	Julien Meuric		Julien Meuric
	France Telecom Orange		France Telecom Orange
	Research & Development		Research & Development
	2, Avenue Pierre Marzin		2, Avenue Pierre Marzin
	22307 Lannion Cedex - France		22307 Lannion Cedex - France
	Phone: +33 2 96 05 28 28		Phone: +33 2 96 05 28 28
	Email: julien.meuric@orange.com		Email: julien.meuric@orange.com
	Generated on: Wed, Apr 17, 2013 5:20:51 PM		Generated on: Thu, Aug 22, 2013 9:07:38 AM
End of changes. 9 change blocks.
	10 lines changed or deleted		22 lines changed or added
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/