IETF Logo Mail Archive

Re: [Idr] I-D Action: draft-ietf-idr-bgp-extended-messages-12.txt

Randy Bush <randy@psg.com> Sat, 21 May 2016 12:36 UTC

Return-Path: <randy@psg.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FC6712D0A2 for <idr@ietfa.amsl.com>; Sat, 21 May 2016 05:36:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.326
X-Spam-Level:
X-Spam-Status: No, score=-8.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426] autolearn=ham autolearn_force=no
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 XlOIivRjC-ft for <idr@ietfa.amsl.com>; Sat, 21 May 2016 05:36:50 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A81312B053 for <idr@ietf.org>; Sat, 21 May 2016 05:36:50 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.82) (envelope-from <randy@psg.com>) id 1b469A-0006Wr-K3 for idr@ietf.org; Sat, 21 May 2016 12:36:48 +0000
Date: Sat, 21 May 2016 14:36:47 +0200
Message-ID: <m2lh33zixs.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: idr wg list <idr@ietf.org>
In-Reply-To: <20160521104812.18611.97398.idtracker@ietfa.amsl.com>
References: <20160521104812.18611.97398.idtracker@ietfa.amsl.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/TFaqIPVj9daQ0dGSiViWgqFZaQE>
Subject: Re: [Idr] I-D Action: draft-ietf-idr-bgp-extended-messages-12.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 May 2016 12:36:51 -0000

the change was to error handling.  jgs did the heavy lifting, tyvm.

OLD

5.  Error Handling

   A BGP speaker that has the ability to use extended messages but has
   not advertised the BGP Extended Messages capability, presumably due
   to configuration, SHOULD NOT accept such a message.

   However, a BGP speaker that does not advertise the BGP Extended
   Messages capability might also genuinely not support extended
   messages.  Such a speaker would be expected to follow the error
   handling procedures of [RFC4221], Section 6.1, and reset the session
   with a Bad Message Length NOTIFICATION if it receives an extended
   message.  A speaker that treats an improper extended message as a
   fatal error should do likewise.

NEW

5.  Error Handling

   A BGP speaker that has the ability to use extended messages but has
   not advertised the BGP Extended Messages capability, presumably due
   to configuration, SHOULD NOT accept an extended message.  A speaker
   MAY implement a more liberal policy and accept extended messages even
   from a peer that has not advertised the capability.

   However, a BGP speaker that does not advertise the BGP Extended
   Messages capability might also genuinely not support extended
   messages.  Such a speaker would be expected to follow the error
   handling procedures of [RFC4221], Section 6.1, and reset the session
   with a Bad Message Length NOTIFICATION if it receives an extended
   message.  A speaker that treats an improper extended message as a
   fatal error, as described in the preceding paragraph, MUST do
   likewise.

randy

v2.23.0 | Report a Bug | By Email