IETF Logo Mail Archive

Re: [Idr] AD Review of draft-ietf-idr-bgp-extended-messages-20

Jeffrey Haas <jhaas@pfrc.org> Wed, 08 March 2017 21:36 UTC

Return-Path: <jhaas@pfrc.org>
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 77C361294D7; Wed, 8 Mar 2017 13:36:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 3GQXAtQjP8Li; Wed, 8 Mar 2017 13:36:47 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 70DBA129462; Wed, 8 Mar 2017 13:36:47 -0800 (PST)
Received: from [172.29.109.148] (unknown [66.129.239.12]) by slice.pfrc.org (Postfix) with ESMTPSA id AD4861E32D; Wed, 8 Mar 2017 16:42:47 -0500 (EST)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Content-Type: multipart/alternative; boundary="Apple-Mail=_A6C2B194-3FC1-4C05-8F22-EC58757D883C"
From: Jeffrey Haas <jhaas@pfrc.org>
In-Reply-To: <EFB3835C-AEEA-46ED-9D6A-91889B005D1C@cisco.com>
Date: Wed, 08 Mar 2017 13:36:47 -0800
Message-Id: <D2EA6CE7-26F7-4C09-B015-78B72D63B2BC@pfrc.org>
References: <DAEE98CC-8483-499E-B71C-FE4C6FC15A4A@cisco.com> <20170228210627.GB17448@pfrc.org> <EFB3835C-AEEA-46ED-9D6A-91889B005D1C@cisco.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/rnJfuo04rI1Pqjwm1rw3llsOEko>
Cc: "idr-chairs@ietf.org" <idr-chairs@ietf.org>, "draft-ietf-idr-bgp-extended-messages@ietf.org" <draft-ietf-idr-bgp-extended-messages@ietf.org>, Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Subject: Re: [Idr] AD Review of draft-ietf-idr-bgp-extended-messages-20
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: Wed, 08 Mar 2017 21:36:48 -0000

> On Mar 7, 2017, at 2:07 PM, Alvaro Retana (aretana) <aretana@cisco.com> wrote:
> 
>> I'm not sure such guidance belongs in this document.  We already have
>> scenarios wherein normal protocol machinery can result in messages that are
>> too large.  The expected behavior is "treat as withdraw" to the next
>> downstream, similar to the BGP Error handling RFC.
>> 
>> Examples of this include AS_PATH or CLUSTER_LIST attributes needing to add a
>> new entry on a full PDU.
> 
> Ok…but is that documented anywhere?  I may be missing it, but I couldn’t find anything like that in rfc4271 or rfc7606.


At best, this is "reading between the lines".

If you can't form a valid PDU to encode in your Adj-rib-out, you withdraw your entry from the adj-rib-out.  This means you send an explicit withdraw.

I think it'd be gross to take this specific document and try to force it to be a normative clarification to this point.



-- Jeff

v2.23.0 | Report a Bug | By Email