Re: [sidr] BGPsec without Extended Messages (draft-ietf-sidr-bgpsec-protocol)

"Susan Hares" <shares@ndzh.com> Wed, 05 April 2017 15:06 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16CC1129447; Wed, 5 Apr 2017 08:06:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.945
X-Spam-Level:
X-Spam-Status: No, score=0.945 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845] autolearn=no 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 xh6uOxs6D4_s; Wed, 5 Apr 2017 08:06:25 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD881129400; Wed, 5 Apr 2017 08:06:24 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=50.36.81.153;
From: "Susan Hares" <shares@ndzh.com>
To: "'Sean Turner'" <sean@sn3rd.com>, "'Alvaro Retana \(aretana\)'" <aretana@cisco.com>
Cc: <idr@ietf.org>, <draft-ietf-sidr-bgpsec-protocol@ietf.org>, <sidrops@ietf.org>, "'Matthew Lepinski'" <mlepinski@ncf.edu>, <sidr-chairs@ietf.org>, <sidr@ietf.org>
References: <65677770-43DB-4CE0-8E81-B35B9A82DF6F@cisco.com> <CA++NScEB1=TswjnszJm8_kghE2n8MX9gyDPePRsqqNALKyA6=g@mail.gmail.com> <36894BDC-01FC-41A5-B7B8-BC91204AE1D2@cisco.com> <EE8D4558-4EF4-43B3-AA65-B22FFCAF72E3@sn3rd.com>
In-Reply-To: <EE8D4558-4EF4-43B3-AA65-B22FFCAF72E3@sn3rd.com>
Date: Wed, 5 Apr 2017 11:01:18 -0400
Message-ID: <010301d2ae1d$7da5ace0$78f106a0$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQLdsGeZpjPoefLB4jQRysFxTsKF4wJc5AG5Anj93pIBwuVnDp9sE14w
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/BJ4PewfEQiDfoLMjDbiUaGnLUa8>
Subject: Re: [sidr] BGPsec without Extended Messages (draft-ietf-sidr-bgpsec-protocol)
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidr/>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 15:06:27 -0000

<individual contributor, RFC4271 co-author> 
Seems reasonable to me. 

Sue Hares 

-----Original Message-----
From: sidr [mailto:sidr-bounces@ietf.org] On Behalf Of Sean Turner
Sent: Wednesday, April 5, 2017 10:49 AM
To: Alvaro Retana (aretana)
Cc: idr@ietf.org; draft-ietf-sidr-bgpsec-protocol@ietf.org;
sidrops@ietf.org; Matthew Lepinski; sidr-chairs@ietf.org; sidr@ietf.org
Subject: Re: [sidr] BGPsec without Extended Messages
(draft-ietf-sidr-bgpsec-protocol)


> On Apr 4, 2017, at 13:18, Alvaro Retana (aretana) <aretana@cisco.com>
wrote:
> 
> To me, the main purpose of changing the BGPsec spec is to depend on
whatever BGP does, and not on a future extension that may or may not be in
the form it is today.  However, if we keep the reference to the known
standard (rfc4271), then we should not have to update this document because
we would just inherit whatever BGP does.

This sound reasonable to me.

spt
_______________________________________________
sidr mailing list
sidr@ietf.org
https://www.ietf.org/mailman/listinfo/sidr