Re: [Idr] Mirja Kühlewind's No Objection on draft-ietf-idr-ix-bgp-route-server-11: (with COMMENT)

Randy Bush <randy@psg.com> Tue, 14 June 2016 03:14 UTC

Return-Path: <randy@psg.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 0137512D5AA for <idr@ietfa.amsl.com>; Mon, 13 Jun 2016 20:14:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.326
X-Spam-Level:
X-Spam-Status: No, score=-8.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426] 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 KJNNwMbWmO3t for <idr@ietfa.amsl.com>; Mon, 13 Jun 2016 20:14:55 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C13FF12D586 for <idr@ietf.org>; Mon, 13 Jun 2016 20:14:55 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.82) (envelope-from <randy@psg.com>) id 1bCeoW-0000Hz-Rt; Tue, 14 Jun 2016 03:14:53 +0000
Date: Tue, 14 Jun 2016 12:14:50 +0900
Message-ID: <m2shwgmpg5.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Christopher Morrow <morrowc.lists@gmail.com>
In-Reply-To: <CAL9jLabgF=h9wSg4GoDoJiT76HcKK2DhpJv=ZxLws7LSs8RN3g@mail.gmail.com>
References: <20160613132809.12486.44511.idtracker@ietfa.amsl.com> <575EB839.3050303@foobar.org> <0DE7AB8E-4CFD-44C5-898F-47F48B542599@kuehlewind.net> <575F2704.3050509@foobar.org> <m237ogo5w1.wl%randy@psg.com> <CAL9jLaaCa9aUOw0HUfyrt05GTYL+yGZum1M=3_4r_E0nx4PqJg@mail.gmail.com> <A65A6088-433D-4200-B098-B2FFEB0A45CD@psg.com> <CAL9jLabgF=h9wSg4GoDoJiT76HcKK2DhpJv=ZxLws7LSs8RN3g@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/ZbxGKDQolgZ93OiTGF02QDjFePk>
Cc: "idr@ietf.org List" <idr@ietf.org>
Subject: Re: [Idr] =?iso-8859-1?q?Mirja_K=FChlewind=27s_No_Objection_on_draft-?= =?iso-8859-1?q?ietf-idr-ix-bgp-route-server-11=3A_=28with_COMMENT=29?=
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, 14 Jun 2016 03:14:57 -0000

>>>> i hate to be old fashioned; actually, that's a lie; but is there either
>>>> an OLD/NEW here or an internet-draft.
> err, maybe nick was thinking there might be more revisions on his text
> options?

see OLD/NEW comment above

> I'm not a native bgp speaker, but I'd question (for instance) the use of
> 'AS_PATH segment' in this part of the draft, given:
> 
>             "AS_PATH is a well-known mandatory attribute that is composed
>             of a sequence of AS path segments.  Each AS path segment is
>             represented by a triple <path segment type, path segment
>             length, path segment value>."
> 
> from: https://tools.ietf.org/html/rfc4271
> 
> I would have thought 'segment' was an individual 'asn' (the triple I
> suppose, the TLV) in the AS_PATH, not the whole 'AS_PATH' attribute. Maybe
> instead of 'AS_PATH segment' in nick's revision:
> 
>              "This differs from the behaviour specified in section
>               5.1.2 of <xref target="RFC4271" />, which requires that
>               the BGP speaker prepends its own AS number as the last
>               element of the AS_PATH.  While it is technically
>               possible to operate a route server which prepends its
>               own AS to the AS_PATH, it is not recommended to do so
>               because this may adversely affect the resulting network
>               topology between the route server clients."
> 
> ​again, I'm not a native bgp speaker, so I'm probably off base, but...
> maybe there's a revision in the revision still to be had before updating
> the actual draft archive?​

i think what might be said is "creating an undesirably longer AS_PATH"
and thus biasing receivers against using the exchange.