--- 1/draft-ietf-idr-error-handling-00.txt	2011-12-16 01:13:57.223004095 +0100
+++ 2/draft-ietf-idr-error-handling-01.txt	2011-12-16 01:13:57.243005587 +0100
@@ -1,21 +1,21 @@
 
 Internet Engineering Task Force (IETF)                        J. Scudder
 Internet Draft                                          Juniper Networks
 Update: 1997, 4271, 4360 (if approved)                           E. Chen
 Intended Status: Standards Track                            P. Mohapatra
-Expires: May 17, 2012                                           K. Patel
+Expires: June 16, 2012                                          K. Patel
                                                            Cisco Systems
-                                                       November 16, 2011
+                                                       December 15, 2011
 
              Revised Error Handling for BGP UPDATE Messages
-                  draft-ietf-idr-error-handling-00.txt
+                  draft-ietf-idr-error-handling-01.txt
 
 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 as 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
@@ -36,21 +36,21 @@
    and may be updated, replaced, or obsoleted by other documents at any
    time.  It is inappropriate to use Internet-Drafts as reference
    material or to cite them other than as "work in progress."
 
    The list of current Internet-Drafts can be accessed at
    http://www.ietf.org/1id-abstracts.html
 
    The list of Internet-Draft Shadow Directories can be accessed at
    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 (c) 2011 IETF Trust and the persons identified as the
    document authors. All rights reserved.
 
    This document is subject to BCP 78 and the IETF Trust's Legal
    Provisions Relating to IETF Documents
    (http://trustee.ietf.org/license-info) in effect on the date of
    publication of this document. Please review these documents
@@ -157,20 +157,24 @@
    The approach of "treat-as-withdraw" MUST be used for the error
    handling of the cases described in Section 6.3 of [RFC4271] that
    specify a session reset and involve any of the following attributes:
    ORIGIN, AS_PATH, NEXT_HOP, MULTI_EXIT_DISC, and LOCAL_PREF.
 
    The approach of "attribute discard" MUST be used for the error
    handling of the cases described in Section 6.3 of [RFC4271] that
    specify a session reset and involve any of the following attributes:
    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
    same approach (either "treat-as-withdraw" or "attribute discard") is
    specified for the handling of these malformed attributes, then the
    specified approach MUST be used. Otherwise "treat-as-withdraw" MUST
    be used.
 
    A document which specifies a new attribute MUST provide specifics
    regarding what constitutes an error for that attribute and how that
    error is to be handled.