IETF Logo Mail Archive

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

"Alvaro Retana (aretana)" <aretana@cisco.com> Tue, 07 March 2017 22:15 UTC

Return-Path: <aretana@cisco.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 6A43D129519; Tue, 7 Mar 2017 14:15:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 jYGoltql_tJS; Tue, 7 Mar 2017 14:15:54 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C6A21294EC; Tue, 7 Mar 2017 14:15:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1368; q=dns/txt; s=iport; t=1488924954; x=1490134554; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=/pOTx4aOy1XXR5R4hmEySqivkWbIEVcFyUsmROMCW64=; b=ZaUOjSfCUAlvPhjM9FEHgo3ZHrfpvFusAuW4HiiT1eWAY26Q04CE7mEM oUxI4JHgYeTCTzg3DPVsvc7gFr9EMR1/6KSSDJm6emxV5eH4OqMlVm52j 7Ml98mmyFp9j+j4Mh2/Ff4LQqdgfdmDR41pDukau+aTqZkF8TRhTGP6wb A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AvAgBJML9Y/5RdJa1dGgEBAQECAQEBAQgBAQEBg1GBaweDWIoMkSyVVoINhiICGoIRPxgBAgEBAQEBAQFrHQuFFgYjEUUQAgEIGgImAgICMBUQAgQOBYl/sGGCJop8AQEBAQEBAQEBAQEBAQEBAQEBAQEBHYELhUOCBQiCYoUOgkwugjEBBJV3hjkBih2IGYF7jySIQ4p3AR84gQNWFVABhkJ1iQaBDQEBAQ
X-IronPort-AV: E=Sophos;i="5.36,260,1486425600"; d="scan'208";a="394077425"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Mar 2017 22:15:53 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id v27MFrpF029358 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 7 Mar 2017 22:15:53 GMT
Received: from xch-aln-002.cisco.com (173.36.7.12) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 7 Mar 2017 16:15:53 -0600
Received: from xch-aln-002.cisco.com ([173.36.7.12]) by XCH-ALN-002.cisco.com ([173.36.7.12]) with mapi id 15.00.1210.000; Tue, 7 Mar 2017 16:15:53 -0600
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: "idr-chairs@ietf.org" <idr-chairs@ietf.org>
Thread-Topic: [Idr] AD Review of draft-ietf-idr-bgp-extended-messages-20
Thread-Index: AQHSjglrFbHoeYS2WUyxb/MV1DegzqF/VY+AgAlhrgCAAEiTgIABFaOA
Date: Tue, 07 Mar 2017 22:15:52 +0000
Message-ID: <8F538ECE-0317-41CE-95BC-9F64E7385B4D@cisco.com>
References: <DAEE98CC-8483-499E-B71C-FE4C6FC15A4A@cisco.com> <20170228210627.GB17448@pfrc.org> <3eb4d853-1d44-6250-c70a-26f60eac39e6@cisco.com> <006e01d296db$a7c4c320$f74e4960$@ndzh.com>
In-Reply-To: <006e01d296db$a7c4c320$f74e4960$@ndzh.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.1f.0.170216
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.117.15.6]
Content-Type: text/plain; charset="utf-8"
Content-ID: <BDE52EB17E556F44B012C0E607C59E04@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/nIjRWbxtCvQPcf3j50s086W45EM>
Cc: "idr@ietf.org" <idr@ietf.org>, "draft-ietf-idr-bgp-extended-messages@ietf.org" <draft-ietf-idr-bgp-extended-messages@ietf.org>, Susan Hares <shares@ndzh.com>
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: Tue, 07 Mar 2017 22:15:58 -0000

Hi!

After reading the messages in this thread, I’m returning the document to the WG to finish the discussion there.

Based on the discussion, I think there are some open items that I would like the WG to close on (in no particular order):

- Should this document address all messages or just UPDATES?  [The Chairs asked for feedback from grow.]

- Are any updates needed to the FSM?

- Is it ok to send/accept Extended Messages without having received/advertised the Capability?  This is a significant change in the way BGP operates – and would set an important precedent.

- What about incremental deployment?  Should there be operational guidance?  If so, what should that guidance be?


Thanks!

Alvaro.


On 3/6/17, 7:42 PM, "Susan Hares" <shares@ndzh.com> wrote:

> <WG chair hat on> 
> If there is enough concern about the extended messages covering all messages versus 
> UPDATE messages,  I will need to do  1 week call on this topic.  
> <WG Chair hat off>

v2.23.0 | Report a Bug | By Email