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

Christopher Morrow <morrowc.lists@gmail.com> Tue, 14 June 2016 02:48 UTC

Return-Path: <christopher.morrow@gmail.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 36E2C12D586 for <idr@ietfa.amsl.com>; Mon, 13 Jun 2016 19:48:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 TAFS2LL3OxvZ for <idr@ietfa.amsl.com>; Mon, 13 Jun 2016 19:48:40 -0700 (PDT)
Received: from mail-yw0-x22e.google.com (mail-yw0-x22e.google.com [IPv6:2607:f8b0:4002:c05::22e]) (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 225FB12D127 for <idr@ietf.org>; Mon, 13 Jun 2016 19:48:40 -0700 (PDT)
Received: by mail-yw0-x22e.google.com with SMTP id v137so41492579ywa.3 for <idr@ietf.org>; Mon, 13 Jun 2016 19:48:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=5CvfRbhmz+0lR3FPALtKG0B988j1quWc/kKYHV9XoyA=; b=Qj9QsI0mju+auhYjUuWLr7GyuMksjGOMXS2XikLtOTg2Q/6r4Opua6h+Xegh7BlkHw kfiBzzAdwt0vflL+9T8MecdxdOiwj+mjxHXTI4GkwBTD1ncdmD7s1U/NGH/Xr8LIm3QT fIILSHnnHQ1n0lOjAcDZ39I3OvA4FHC5bq/7L71ZHrAsTMRLDUCwJC4ZR/xAoPHpMqFx m1nyoodkcrh6j80v6qeK0Bn1m/UvA4HYIgNhR9xdoLJMA7QX6DCKvkixvh4gzblhSJpu IaCAbyP7PsZS/+EO+/OOb3k/EKrQ+l2OJVkpNE9GhpHxEeYVeJgLZwLrs/9qCUrxN2LB +cnw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=5CvfRbhmz+0lR3FPALtKG0B988j1quWc/kKYHV9XoyA=; b=KEVlkzl9GIYkqYIhh+X7QxAwOXxR7x5sYbfS9vLhMZC/GFLlyQ1fAg2IotSJIsGrqI +s5TLkJEkuq/ROTK6VfpeDbBf5OZroFVdkNJH/U4CUvg1X5OZUIEul+XHHO3lWKcYm3x xGbu5M5nmkxNMGlhhvY086Jy5TumKmVrOJhxrT1lnws3hm1++6LvwBvJ8QwLmCYpIhXH FvX+SjwXPjzHuZvqmlfaNjpiYuViUzFaS+oWkvVFWZZFgfSFnHRHOOHKwFDWtCiK/VEc udXJoT/sCH3DVCG+fE9kGvx97h745gcqOWiVmDjwqscpWu7RV7KtfcbkFUNjk1+cFrJu d7gA==
X-Gm-Message-State: ALyK8tI2QLReQvYt0Z9mdqDy0/RYMZ5cxBE2iYm6lHoSNCCMhngpz2FYILLjgjjytpMNcw8APcGNhw6jI+SnYw==
X-Received: by 10.13.196.132 with SMTP id g126mr711628ywd.95.1465872519331; Mon, 13 Jun 2016 19:48:39 -0700 (PDT)
MIME-Version: 1.0
Sender: christopher.morrow@gmail.com
Received: by 10.129.146.130 with HTTP; Mon, 13 Jun 2016 19:48:38 -0700 (PDT)
In-Reply-To: <A65A6088-433D-4200-B098-B2FFEB0A45CD@psg.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>
From: Christopher Morrow <morrowc.lists@gmail.com>
Date: Mon, 13 Jun 2016 22:48:38 -0400
X-Google-Sender-Auth: ltw4xPd4v5NMHhzjU8A4rHYqr_E
Message-ID: <CAL9jLabgF=h9wSg4GoDoJiT76HcKK2DhpJv=ZxLws7LSs8RN3g@mail.gmail.com>
To: Randy Bush <randy@psg.com>
Content-Type: multipart/alternative; boundary=001a114d7ed4cd059c0535340ae0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/_OzxRDR2i-QskVbli2TST4CYEtE>
Cc: "idr@ietf.org List" <idr@ietf.org>
Subject: Re: [Idr] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft-ie?= =?utf-8?q?tf-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 02:48:42 -0000

On Mon, Jun 13, 2016 at 10:38 PM, Randy Bush <randy@psg.com>; wrote:

> this is now changed as follows:
>>>>
>>>>
>>> https://github.com/fooelisa/draft-jasinska-ix-bgp-route-server/commit/5fd0508
>>>
>>> i hate to be old fashioned; actually, that's a lie; but is there either
>>> an OLD/NEW here or an internet-draft.
>>>
>>
>> ​did you mean: "Where is the full draft?"
>>
>
> no.  i mean a real internet-draft, in the ietf drafts directory which i
> mirror.
>

​oh! "hey, cool code kid, got an email to the submission bot to get your
changes to where we can all see them?" (version of: ​
http://static.flickr.com/87/240803829_9212773615_o.png)

err, maybe nick was thinking there might be more revisions on his text
options?

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?​