Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-overview ENDING: 10/21/2015)

Sandra Murphy <sandy@tislabs.com> Thu, 15 October 2015 11:03 UTC

Return-Path: <sandy@tislabs.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 774231B2AB6 for <sidr@ietfa.amsl.com>; Thu, 15 Oct 2015 04:03:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 HUGFUUhYzXE4 for <sidr@ietfa.amsl.com>; Thu, 15 Oct 2015 04:03:10 -0700 (PDT)
Received: from walnut.tislabs.com (walnut.tislabs.com [192.94.214.200]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 50D991B2AB5 for <sidr@ietf.org>; Thu, 15 Oct 2015 04:03:10 -0700 (PDT)
Received: from nova.tislabs.com (unknown [10.66.1.77]) by walnut.tislabs.com (Postfix) with ESMTP id A6B3F28B0046; Thu, 15 Oct 2015 07:03:09 -0400 (EDT)
Received: from [IPv6:::1] (localhost.localdomain [127.0.0.1]) by nova.tislabs.com (Postfix) with ESMTP id 6F3DC1F8035; Thu, 15 Oct 2015 07:03:09 -0400 (EDT)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_D0DCB0C8-06C8-4503-A636-EA25ECD9ACC3"; protocol="application/pgp-signature"; micalg="pgp-sha512"
X-Pgp-Agent: GPGMail 2.5.1
From: Sandra Murphy <sandy@tislabs.com>
In-Reply-To: <D2442A8C.6CE45%wesley.george@twcable.com>
Date: Thu, 15 Oct 2015 07:02:22 -0400
Message-Id: <CABE5B0C-6C9E-4EE7-A6F4-364745BBB1E9@tislabs.com>
References: <yj9osi5mae4p.wl%morrowc@ops-netman.net> <D2442A8C.6CE45%wesley.george@twcable.com>
To: Wesley George <wesley.george@twcable.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/sidr/vh5AZEInHe5g3tS4C5wTlJpsTNY>
Cc: "sidr@ietf.org" <sidr@ietf.org>, Sandra Murphy <sandy@tislabs.com>
Subject: Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-overview ENDING: 10/21/2015)
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 15 Oct 2015 11:03:11 -0000

On Oct 14, 2015, at 5:25 PM, George, Wes <wesley.george@twcable.com> wrote:

> Gave this a review, and stumbled across an issue that may not necessarily
> be gating to this draft, but should probably be addressed in some other
> drafts.

…


> 
> Substantive: I had to think through this for a bit to make sure I
> understood why this is true beyond the obvious problem of AS23456 not
> being unique. I think we need some additional words explaining why, though
> I am not sure if it belongs here, in the protocol draft, or in sriram's
> design-choices doc (7.6 is very thin on explanation). I think that this is
> a specific corner case for the more generic case of incremental
> deployment, where a given path has some routers/ASNs that support BGPSec
> and some that do not, and as far as I can tell, incremental deployment
> isn't really discussed as a concept beyond the [non]negotiation of support
> between peers.
> 
> 

Do you think the bgpsec-ops draft is the right place for that discussion?

Sriram’s draft is an individual submission, not a wg draft.  Sriram can put text there if he wants.  But it’s not subject to wg consensus.

—Sandy