draft-ietf-idr-error-handling-00.txt		draft-ietf-idr-error-handling-01.txt
	Internet Engineering Task Force (IETF) J. Scudder		Internet Engineering Task Force (IETF) J. Scudder
	Internet Draft Juniper Networks		Internet Draft Juniper Networks
	Update: 1997, 4271, 4360 (if approved) E. Chen		Update: 1997, 4271, 4360 (if approved) E. Chen
	Intended Status: Standards Track P. Mohapatra		Intended Status: Standards Track P. Mohapatra
	Expires: May 17, 2012 K. Patel		Expires: June 16, 2012 K. Patel
	Cisco Systems		Cisco Systems
	November 16, 2011		December 15, 2011
	Revised Error Handling for BGP UPDATE Messages		Revised Error Handling for BGP UPDATE Messages
	draft-ietf-idr-error-handling-00.txt		draft-ietf-idr-error-handling-01.txt
	Abstract		Abstract
	According to the base BGP specification, a BGP speaker that receives		According to the base BGP specification, a BGP speaker that receives
	an UPDATE message containing a malformed attribute is required to		an UPDATE message containing a malformed attribute is required to
	reset the session over which the offending attribute was received.		reset the session over which the offending attribute was received.
	This behavior is undesirable as a session reset would impact not only		This behavior is undesirable as a session reset would impact not only
	routes with the offending attribute, but also other valid routes		routes with the offending attribute, but also other valid routes
	exchanged over the session. This document partially revises the		exchanged over the session. This document partially revises the
	error handling for UPDATE messages, and provides guidelines for the		error handling for UPDATE messages, and provides guidelines for the
	skipping to change at page 1, line 47		skipping to change at page 1, line 47
	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 May 17, 2012.		This Internet-Draft will expire on June 16, 2012.
	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
	skipping to change at page 4, line 31		skipping to change at page 4, line 31
	The approach of "treat-as-withdraw" MUST be used for the error		The approach of "treat-as-withdraw" MUST be used for the error
	handling of the cases described in Section 6.3 of [RFC4271] that		handling of the cases described in Section 6.3 of [RFC4271] that
	specify a session reset and involve any of the following attributes:		specify a session reset and involve any of the following attributes:
	ORIGIN, AS_PATH, NEXT_HOP, MULTI_EXIT_DISC, and LOCAL_PREF.		ORIGIN, AS_PATH, NEXT_HOP, MULTI_EXIT_DISC, and LOCAL_PREF.
	The approach of "attribute discard" MUST be used for the error		The approach of "attribute discard" MUST be used for the error
	handling of the cases described in Section 6.3 of [RFC4271] that		handling of the cases described in Section 6.3 of [RFC4271] that
	specify a session reset and involve any of the following attributes:		specify a session reset and involve any of the following attributes:
	ATOMIC_AGGREGATE and AGGREGATOR.		ATOMIC_AGGREGATE and AGGREGATOR.
			If an attribute appears more than once in an UPDATE message, then all
			the occurrences of the attribute other than the first one SHALL be
			discarded and the UPDATE message continue to be processed.
	When multiple malformed attributes exist in an UPDATE message, if the		When multiple malformed attributes exist in an UPDATE message, if the
	same approach (either "treat-as-withdraw" or "attribute discard") is		same approach (either "treat-as-withdraw" or "attribute discard") is
	specified for the handling of these malformed attributes, then the		specified for the handling of these malformed attributes, then the
	specified approach MUST be used. Otherwise "treat-as-withdraw" MUST		specified approach MUST be used. Otherwise "treat-as-withdraw" MUST
	be used.		be used.
	A document which specifies a new attribute MUST provide specifics		A document which specifies a new attribute MUST provide specifics
	regarding what constitutes an error for that attribute and how that		regarding what constitutes an error for that attribute and how that
	error is to be handled.		error is to be handled.
End of changes. 5 change blocks.
	4 lines changed or deleted		8 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/