draft-ietf-idr-fsm-subcode-01.txt		draft-ietf-idr-fsm-subcode-02.txt
	Network working group J. Dong
	Internet Draft M. Chen
	Intended status: Standards Track Huawei Technologies
	Expires: September 2011 A. Suryanarayana
	Juniper Networks
	March 14, 2011
	Subcodes for BGP Finite State Machine Error		Network Working Group J. Dong
			Internet-Draft M. Chen
			Intended status: Standards Track Huawei Technologies
			Expires: February 12, 2012 A. Suryanarayana
			Cisco Systems
			August 11, 2011
	draft-ietf-idr-fsm-subcode-01.txt		Subcodes for BGP Finite State Machine Error
			draft-ietf-idr-fsm-subcode-02
	Abstract		Abstract
	This document defines several subcodes for BGP Finite State Machine		This document defines several subcodes for BGP Finite State Machine
	Error that could provide more information to help network operators		(FSM) Error that could provide more information to help network
	in diagnosing BGP FSM issues and correlating network events.		operators in diagnosing BGP FSM issues and correlating network
			events.
			Requirements Language
			The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
			"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
			document are to be interpreted as described in RFC 2119 [RFC2119].
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted to IETF in full conformance with		This Internet-Draft is submitted in full conformance with the
	the provisions of BCP 78 and BCP 79.		provisions of BCP 78 and 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). Note that other groups may also distribute
	other groups may also distribute working documents as Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six		Internet-Drafts are draft documents valid for a maximum of six months
	months and may be updated, replaced, or obsoleted by other documents		and may be updated, replaced, or obsoleted by other documents at any
	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		This Internet-Draft will expire on February 12, 2012.
	http://www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.
	This Internet-Draft will expire on September 14, 2011.
	Copyright Notice		Copyright Notice
	Copyright (c) 2011 IETF Trust and the persons identified as the		Copyright (c) 2011 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
	carefully, as they describe your rights and restrictions with		carefully, as they describe your rights and restrictions with respect
	respect to this document. Code Components extracted from this		to this document. Code Components extracted from this document must
	document must include Simplified BSD License text as described in		include Simplified BSD License text as described in Section 4.e of
	Section 4.e of the Trust Legal Provisions and are provided without		the Trust Legal Provisions and are provided without warranty as
	warranty as described in the Simplified BSD License.		described in the Simplified BSD License.
	Conventions used in this document
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in RFC-2119 [RFC2119].
	Table of Contents		Table of Contents
	1. Introduction ................................................ 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. Definition of Finite State Machine Error Subcodes ........... 2		2. Definition of Finite State Machine Error Subcodes . . . . . . . 3
	3. Usage of FSM Error Subcodes ................................. 3		3. Usage of FSM Error Subcodes . . . . . . . . . . . . . . . . . . 3
	4. Security Considerations ..................................... 3		4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4
	5. IANA Considerations ......................................... 3		5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
	6. Contributors ................................................ 4		6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 4
	7. Acknowledgments ............................................. 4		7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4
	8. References .................................................. 4		8. Normative References . . . . . . . . . . . . . . . . . . . . . 4
	8.1. Normative References ................................... 4		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 4
	8.2. Informative References ................................. 4
	Authors' Addresses ............................................. 5
	1. Introduction		1. Introduction
	This document defines several subcodes for BGP [RFC4271] Finite		This document defines several subcodes for BGP [RFC4271] Finite State
	State Machine Error that could provide more information to help		Machine Error that could provide more information to help network
	network operators in diagnosing BGP FSM issues and correlating		operators in diagnosing BGP FSM issues and correlating network
	network events. This information is also helpful to developers in		events. This information is also helpful to developers in lab
	lab situations.		situations.
	2. Definition of Finite State Machine Error Subcodes		2. Definition of Finite State Machine Error Subcodes
	This document defines following subcodes for BGP Finite State		This document defines following subcodes for BGP Finite State Machine
	Machine Error:		Error:
	0 - Unspecific Error		0 - Unspecific Error
	1 - Receive Unexpected Message in OpenSent State
	2 - Receive Unexpected Message in OpenConfirm State		1 - Receive Unexpected Message in OpenSent State
	3 - Receive Unexpected Message in Established State		2 - Receive Unexpected Message in OpenConfirm State
	3. Usage of FSM Error Subcodes		3 - Receive Unexpected Message in Established State
	If a BGP speaker receives an unexpected message		3. Usage of FSM Error Subcodes
	(KEEPALIVE/UPDATE/ROUTE-REFRESH message) on a session in OpenSent
	state, it MUST send to the neighbor a Notification message with the
	Error Code Finite State Machine Error and the Error Subcode "Receive
	Unexpected Message in OpenSent State". The Data field is a 1-octet
	unsigned integer which indicates type of the unexpected message.
	If a BGP speaker receives an unexpected message (OPEN/UPDATE/ROUTE-		If a BGP speaker receives an unexpected message (e.g. KEEPALIVE/
	REFRESH message) on a session in OpenConfirm state, it MUST send to		UPDATE/ROUTE-REFRESH message) on a session in OpenSent state, it MUST
	the neighbor a Notification message with the Error Code Finite State		send to the neighbor a NOTIFICATION message with the Error Code
	Machine Error and the Error Subcode "Receive Unexpected Message in		Finite State Machine Error and the Error Subcode "Receive Unexpected
	OpenConfirm State". The Data field is a 1-octet unsigned integer		Message in OpenSent State". The Data field is a 1-octet unsigned
	which indicates type of the unexpected message.		integer which indicates type of the unexpected message.
	If a BGP speaker receives an unexpected message (OPEN message) on a		If a BGP speaker receives an unexpected message (e.g. OPEN/UPDATE/
	session in Established state, it MUST send to the neighbor a		ROUTE-REFRESH message) on a session in OpenConfirm state, it MUST
	Notification message with the Error Code Finite State Machine Error		send to the neighbor a NOTIFICATION message with the Error Code
			Finite State Machine Error and the Error Subcode "Receive Unexpected
			Message in OpenConfirm State". The Data field is a 1-octet unsigned
			integer which indicates type of the unexpected message.
			If a BGP speaker receives an unexpected message (e.g. OPEN message)
			on a session in Established state, it MUST send to the neighbor a
			NOTIFICATION message with the Error Code Finite State Machine Error
	and the Error Subcode "Receive Unexpected Message in Established		and the Error Subcode "Receive Unexpected Message in Established
	State". The Data field is a 1-octet unsigned integer which indicates		State". The Data field is a 1-octet unsigned integer which indicates
	type of the unexpected message.		type of the unexpected message.
	4. Security Considerations		4. Security Considerations
	This document does not change the security properties of BGP.		This document does not change the security properties of BGP.
	5. IANA Considerations		5. IANA Considerations
	IANA is requested to make the following allocations from registries
	under its control.
	This document defines Error Subcodes 0 - 3 for BGP Finite State
	Machine Error.
	0 - Unspecific Error		IANA is requested to create the registry "BGP Finite State Machine
			Error Subcodes", within the "BGP Error Subcodes" registry, with
			Registration Procedures "Standards Action process or the Early IANA
			Allocation process".
	1 - Receive Unexpected Message in OpenSent State		The registry should be populated with the following values:
	2 - Receive Unexpected Message in OpenConfirm State		Value Name
	3 - Receive Unexpected Message in Established State		0 Unspecified Error
			1 Receive Unexpected Message in OpenSent State
			2 Receive Unexpected Message in OpenConfirm State
			3 Receive Unexpected Message in Established State
	6. Contributors		6. Contributors
	The following individuals contributed to this document:		The following individuals contributed to this document:
	Xiaoming Gu		Xiaoming Gu EMail: guxiaoming@huawei.com
	EMail: guxiaoming@huawei.com
	Chong Wang
	EMail: chongwang@huawei.com		Chong Wang EMail: chongwang@huawei.com
	7. Acknowledgments		7. Acknowledgements
	The authors would like to thank John Scudder, Jeffrey Haas, Susan		The authors would like to thank John Scudder, Jeffrey Haas, Susan
	Hares, Keyur Patel, Enke Chen and Ruediger Volk for their valuable		Hares, Keyur Patel, Enke Chen and Ruediger Volk for their valuable
	suggestions and comments to this document.		suggestions and comments to this document.
	8. References		8. Normative References
	8.1. Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.
	[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
	IANA Considerations Section in RFCs", BCP 26, RFC 5226,
	May 2008.
	[RFC4271] Rekhter, Y., Li, T. and Hares, S., "A Border Gateway
	Protocol 4 (BGP-4)", RFC 4271, January 2006.
	8.2. Informative References		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
			Requirement Levels", BCP 14, RFC 2119, March 1997.
	[RFC4486] Chen, E. and Gillet, V., "Subcodes for BGP Cease		[RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway
	Notification Message", RFC 4486, April 2006.		Protocol 4 (BGP-4)", RFC 4271, January 2006.
	Authors' Addresses		Authors' Addresses
	Jie Dong		Jie Dong
	Huawei Technologies Co.,Ltd.		Huawei Technologies
	Huawei Building, No.3 Xinxi Rd.,		Huawei Building, No.3 Xinxi Rd
	Hai-Dian District		Beijing 100085
	Beijing, 100085		China
	P.R. China
	EMail: jie.dong@huawei.com		Email: jie.dong@huawei.com
	Mach(Guoyi) Chen		Mach Chen
	Huawei Technologies Co.,Ltd.		Huawei Technologies
	Huawei Building, No.3 Xinxi Rd.,		Huawei Building, No.3 Xinxi Rd
	Hai-Dian District		Beijing 100085
	Beijing, 100085		China
	P.R. China
	EMail: mach.chen@huawei.com		Email: mach.chen@huawei.com
	Anantharamu Suryanarayana		Anantharamu Suryanarayana
	Juniper Networks		Cisco Systems
			USA
	EMail: anantha@juniper.net		Email: asuryana@cisco.com
End of changes. 41 change blocks.
	130 lines changed or deleted		107 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/