Re: [Idr] draft-walton-bgp-hostname-capability-00

Daniel Walton <dwalton@cumulusnetworks.com> Wed, 20 May 2015 17:19 UTC

Return-Path: <dwalton@cumulusnetworks.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0437D1A8996 for <idr@ietfa.amsl.com>; Wed, 20 May 2015 10:19:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level:
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 5OhhKqUTBbk5 for <idr@ietfa.amsl.com>; Wed, 20 May 2015 10:19:06 -0700 (PDT)
Received: from mail-ig0-x232.google.com (mail-ig0-x232.google.com [IPv6:2607:f8b0:4001:c05::232]) (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 73D241A898D for <idr@ietf.org>; Wed, 20 May 2015 10:19:06 -0700 (PDT)
Received: by igbpi8 with SMTP id pi8so139842691igb.0 for <idr@ietf.org>; Wed, 20 May 2015 10:19:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cumulusnetworks.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Gl7IEzNsQXUDA7tNJEvShFvDA8Ce7GUfX25dd11RfLs=; b=NFbpPILCUtzfZrTovM/9thdM7N0oNXjixhj3adWEeanf3bmwqgBl3i+o4A5ham0S8O qSiGmwX4C1MPTHMj78YvTLv4pWNsSCbx3Dn4W2S+Ws/092BJm8edpfjgu0yTDo0I4h1+ tygVmYRegGWZDQ+Ch2WjLPAf6YzvY9lPbry3w=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Gl7IEzNsQXUDA7tNJEvShFvDA8Ce7GUfX25dd11RfLs=; b=BUtXZsvWhxX78e2HTys39XIonWAJXFgaDtWR3hu8oVBUkuntAw2E+p3wbdbuoy2OyL xZQe+g3NZmDRrPqsKBYGXLmiMtRcJnLYSJotP3FYZhfPhG7KSmSax9qQpYeVJ9F++YnI rbGuZWPcG6vU4H/9t1ynClMps4WZ4cAPSbzzyBaoNwVGp73yzwItckhRg0oeLzoBV4sk L9y5xIqw61W+D3tnlQriACrWo6HcnI7tW4F4qIWw4h1j1MEf7IxmXGvxR2w3J0McAraM Q1pkxr0AWxqoR/JfDhg1JRhjUvDFTZZoQ/UWgEclnmHIicJ5w6mvFNC0KZ6/ymzH1bXm LXHg==
X-Gm-Message-State: ALoCoQkzzh/NP7PRDOLyg1xIb+trL/rSWca3NWSCeBkvDgjscO/BrNhlVn5iM3Ozt9KbtvZwk4Uz
MIME-Version: 1.0
X-Received: by 10.107.29.148 with SMTP id d142mr45688966iod.9.1432142345852; Wed, 20 May 2015 10:19:05 -0700 (PDT)
Received: by 10.107.129.92 with HTTP; Wed, 20 May 2015 10:19:05 -0700 (PDT)
In-Reply-To: <20150520144203.GA16193@pfrc.org>
References: <CANL=f0h9ZV+SPr+2vcx2dEk4O9MxBAZJEU7xgHZDC=ep2g2r-g@mail.gmail.com> <20150520144203.GA16193@pfrc.org>
Date: Wed, 20 May 2015 13:19:05 -0400
Message-ID: <CANL=f0j4-dYMjbT5HMu1RQKApnG-xw-ys15Pyb_OBETKHceCJw@mail.gmail.com>
From: Daniel Walton <dwalton@cumulusnetworks.com>
To: Jeffrey Haas <jhaas@pfrc.org>
Content-Type: multipart/alternative; boundary="001a114089c4caf1f70516869f1d"
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/iUNnJerugNtzmeJC1b2dcqV_PWU>
Cc: idr wg <idr@ietf.org>
Subject: Re: [Idr] draft-walton-bgp-hostname-capability-00
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 20 May 2015 17:19:09 -0000

Hi Jeff,
Thank you for the feedback.  Questions/comments inline...

On Wed, May 20, 2015 at 10:42 AM, Jeffrey Haas <jhaas@pfrc.org> wrote:

> On Fri, May 15, 2015 at 09:26:16PM -0400, Daniel Walton wrote:
> > https://tools.ietf.org/html/draft-walton-bgp-hostname-capability-00
> >
> > Feedback is welcome. There is a "Sectino" typo in the intro, will clean
> > that up.
>
> At John's request, here is a short list of things I find problematic about
> this draft.  Note that this isn't a statement of my opinion on the value of
> it.
>
> 1. The draft really should require the ext-opt-param feature.  It's too
> easy
> for a hostname to eat all of the capability space.
>

I think requiring ext-opt-param should be fine.  Agreed that if someone
configures a 255 character hostname and 255 character domain name that
would be problematic with the current draft.



> 2. You can't rely on the hostname in question being useful for DNS
> purposes.
> The IPv6 link local peering is just one example of why.
>

The hostnames learned should only be used for bgp UI purposes, we have no
plans to try to auto-populate DNS or anything like that.  We will add some
text to clarify this.


3. The specification should offer some guidance about what to do when you
> have multiple peering sessions with a given router.
> 4. The specification should offer some guidance about what to do when two
> distinct routers use the same name.
>
> Note that 3 and 4 can be distinguished based on BGP Identifier.
>

Ack.  We can put in a section of sample show command output with some
possible ways to handle these scenarios.  How one decides to display this
will obviously be implementation specific but some examples can't hurt.

Daniel


> As for the UTF-8 issue, it's the right thing to do and as much as it makes
> things a real mess, the draft wouldn't progress in IESG without I18N issues
> being dealt with.
>
> That said, carefully consider what you expect to do with the names returned
> by such a feature.  Just because you can print the things, does that mean
> the input portion of your UI can accept it?
>
> -- Jeff (best I can do with anything that isn't Latin-1 is cut and paste)
>