Last Call: <draft-ietf-idr-error-handling-18.txt> (Revised Error Handling for BGP UPDATE Messages) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Thu, 26 February 2015 21:01 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E8C11A8873; Thu, 26 Feb 2015 13:01:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7ROfYvmxhfZu; Thu, 26 Feb 2015 13:01:13 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B705F1A8828; Thu, 26 Feb 2015 13:01:11 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-idr-error-handling-18.txt> (Revised Error Handling for BGP UPDATE Messages) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 5.12.0
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
Message-ID: <20150226210111.16401.67992.idtracker@ietfa.amsl.com>
Date: Thu, 26 Feb 2015 13:01:11 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/TnxRPPXe814zrTYtRlc23_CywB8>
Cc: idr@ietf.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Feb 2015 21:01:14 -0000

The IESG has received a request from the Inter-Domain Routing WG (idr) to
consider the following document:
- 'Revised Error Handling for BGP UPDATE Messages'
  <draft-ietf-idr-error-handling-18.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2015-03-12. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   According to the base BGP specification, a BGP speaker that receives
   an UPDATE message containing a malformed attribute is required to
   reset the session over which the offending attribute was received.
   This behavior is undesirable, because a session reset would impact
   not only routes with the offending attribute, but also other, valid
   routes exchanged over the session.  This document partially revises
   the error handling for UPDATE messages and provides guidelines for
   the authors of documents defining new attributes.  Finally, it
   revises the error handling procedures for a number of existing
   attributes.

   This document updates error handling for RFCs 1997, 4271, 4360, 4456,
   4760, 5543, 5701 and 6368.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-idr-error-handling/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-idr-error-handling/ballot/


No IPR declarations have been submitted directly on this I-D.