Re: [Idr] WG adoption call for draft-ymbk-idr-bgp-open-policy (5/20 to 6/3/2017).
Jeffrey Haas <jhaas@pfrc.org> Wed, 05 July 2017 17:53 UTC
Return-Path: <jhaas@slice.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 40271131552 for <idr@ietfa.amsl.com>; Wed, 5 Jul 2017 10:53:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level:
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 NfVtpTIP41Md for <idr@ietfa.amsl.com>; Wed, 5 Jul 2017 10:53:02 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 16841131555 for <idr@ietf.org>; Wed, 5 Jul 2017 10:53:02 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 592CC1E34A; Wed, 5 Jul 2017 14:02:12 -0400 (EDT)
Date: Wed, 05 Jul 2017 14:02:12 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: idr@ietf.org
Message-ID: <20170705180212.GA15632@pfrc.org>
References: <001e01d2d14c$32ed2e10$98c78a30$@ndzh.com> <19180.1496426777@x59.NIC.DTAG.DE> <CACWOCC9Ar8aJdGEOYPTnQ_h6q6FqKizM2qqw6QLuo+7ywaCVCw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CACWOCC9Ar8aJdGEOYPTnQ_h6q6FqKizM2qqw6QLuo+7ywaCVCw@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/-AcH9EJYXcLOVwMrvGsV_NI2Nvg>
Subject: Re: [Idr] WG adoption call for draft-ymbk-idr-bgp-open-policy (5/20 to 6/3/2017).
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.22
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, 05 Jul 2017 17:53:03 -0000
Job, On Sun, Jun 04, 2017 at 11:59:47AM +0000, Job Snijders wrote: > Unfortunately, as it's currently specified, I still cannot see my > affiliation deploying this technology in a meaningful way. > > The word "peer" is extremely overloaded: it is a homonym which conflates > all kinds of concepts. The term appears in too many training courses to be > redefined to one specific meaning. On top of that, I all too often see that > provisioning- or customer engineers don't have clear insight as to who is > customer and who the supplier is. Even worse: a customer may assume the > supplier role as part of a larger deal. While in the hallways we easily > talk about simplified models on how the internet works, actually enforcing > that simplification in the context of EBGP to me is undesirable. I have some opinions here that probably overlap your own. While I haven't paid good attention to operator forums like NANOG for a while, I remember that definitions of 'peer' tended to make for a heated topic. I also don't remember any particular convergence on a formal definition that would hold up in a BGP AS-graph sort of way. It might be helpful if you or other operators rally for what the current definition of that term is perceived to be. (And yes, I realize that simply asking the question may be tantamount to starting a flame war...) [...] > > Perhaps if the draft would focus on merely two classifications: "stub" and > "transit" networks, where the former would be an affirmation that neither > party expects the "stub" network to transit prefixes for any other ASN, and > transit networks would enjoy the same behavior as any ASN today, that would > give a different twist to this idea. Downside is that one needs to bounce > the session to become a transit provider. The real issue here is the simple matter of AS-graph definition. A stub network is always clear. Traditional papers for valley free routing tend to focus on the remaining up/down/lateral relationships. I believe these are the properties we're looking for, and that stub/transit is probably not a sufficient relationship. -- Jeff
- [Idr] WG adoption call for draft-ymbk-idr-bgp-ope… Susan Hares
- Re: [Idr] WG adoption call for draft-ymbk-idr-bgp… Randy Bush
- Re: [Idr] WG adoption call for draft-ymbk-idr-bgp… Alexander Azimov
- Re: [Idr] WG adoption call for draft-ymbk-idr-bgp… Matthias Waehlisch
- Re: [Idr] WG adoption call for draft-ymbk-idr-bgp… Daniel Ginsburg
- Re: [Idr] WG adoption call for draft-ymbk-idr-bgp… Brian Dickson
- Re: [Idr] WG adoption call for draft-ymbk-idr-bgp… Carlos M. Martinez
- Re: [Idr] WG adoption call for draft-ymbk-idr-bgp… bruno.decraene
- Re: [Idr] WG adoption call for draft-ymbk-idr-bgp… Alexander Azimov
- Re: [Idr] WG adoption call for draft-ymbk-idr-bgp… Ruediger Volk, Deutsche Telekom Technik - FMED-41..
- Re: [Idr] WG adoption call for draft-ymbk-idr-bgp… Smith, Donald
- Re: [Idr] WG adoption call for draft-ymbk-idr-bgp… Job Snijders
- Re: [Idr] WG adoption call for draft-ymbk-idr-bgp… David Monosov
- Re: [Idr] WG adoption call for draft-ymbk-idr-bgp… Pushpasis Sarkar
- Re: [Idr] WG adoption call for draft-ymbk-idr-bgp… Gaurav Dawra (gdawra)
- Re: [Idr] WG adoption call for draft-ymbk-idr-bgp… Alexander Azimov
- Re: [Idr] WG adoption call for draft-ymbk-idr-bgp… Jeffrey Haas
- Re: [Idr] WG adoption call for draft-ymbk-idr-bgp… Nick Hilliard
- Re: [Idr] WG adoption call for draft-ymbk-idr-bgp… Job Snijders
- Re: [Idr] WG adoption call for draft-ymbk-idr-bgp… Sriram, Kotikalapudi (Fed)
- Re: [Idr] WG adoption call for draft-ymbk-idr-bgp… Randy Bush