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

jim deleskie <deleskie@gmail.com> Sun, 17 May 2015 00:42 UTC

Return-Path: <deleskie@gmail.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 878601A8886; Sat, 16 May 2015 17:42:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, SPF_PASS=-0.001] 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 b8nn7XZT8eCt; Sat, 16 May 2015 17:42:30 -0700 (PDT)
Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) (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 212D41A8876; Sat, 16 May 2015 17:42:30 -0700 (PDT)
Received: by wicnf17 with SMTP id nf17so31960242wic.1; Sat, 16 May 2015 17:42:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=f0J7L5/tzyOwndJY74IBYODiZ66XKoidUP2cBJXoSgA=; b=XfrpfwG0bSWP4YudP9i3edneFHVLXkllOws0vgaeF5Meg8FkQx7xvQHcfaN/DvC5qj 6oPhCAzwwjSHRcksI4j4tz/yqLP4s5cCMceiGf6vfVWjSkHahlFn3ajmVnVr7/esUw08 vBqoVdiN4qyQDKVOIxGoBRPjrqTjezjOEeSG5vJ8RLwjawrUprM49Vdw7ljDRVOe6TS9 yRo8vFIj1YZSeGDef4SnYNPrn1hqI5YMWxYZ8ECcfRSg6pynACL5G21hClNhxeWpZ5BB 8XCojPZNkh47d2QugopuwjjL7Ou4BJoZStKGRkHg9rCtytfAn8UpSvA5ZCrWOiL95sE4 FhEQ==
MIME-Version: 1.0
X-Received: by 10.194.5.103 with SMTP id r7mr30464492wjr.47.1431823348834; Sat, 16 May 2015 17:42:28 -0700 (PDT)
Received: by 10.28.62.79 with HTTP; Sat, 16 May 2015 17:42:28 -0700 (PDT)
In-Reply-To: <201505162350.t4GNohsL040700@maildrop31.somerville.occnc.com>
References: <CABg5FUVTSJNF2NOeN1m9ESUzQo3HVNu-fut5PTuHZ+LTigD4eQ@mail.gmail.com> <201505162350.t4GNohsL040700@maildrop31.somerville.occnc.com>
Date: Sat, 16 May 2015 21:42:28 -0300
Message-ID: <CAJL_ZMNAQXTbGJSG5WENYL5KwSC7uF2mPDSr78ZyxhRKvtDnVA@mail.gmail.com>
From: jim deleskie <deleskie@gmail.com>
To: curtis@ipv6.occnc.com
Content-Type: multipart/alternative; boundary="047d7b4512f216a96005163c5ad1"
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/apRKMTKVGzGnT5e1ymRKmalg93Y>
Cc: John Heasley <heas@shrubbery.net>, idr wg <idr@ietf.org>, "idr-bounces@ietf.org" <idr-bounces@ietf.org>, Robert Raszuk <robert@raszuk.net>
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: Sun, 17 May 2015 00:42:32 -0000

Curtis,

 But what would you know... :)  Good to see you, its been a while, hope all
is well.

-jim

On Sat, May 16, 2015 at 8:50 PM, Curtis Villamizar <curtis@ipv6.occnc.com>
wrote:

> In message <
> CABg5FUVTSJNF2NOeN1m9ESUzQo3HVNu-fut5PTuHZ+LTigD4eQ@mail.gmail.com>
> Dinesh Dutt writes:
>
> > Hi John,
> >
> > On Sat, May 16, 2015 at 9:37 AM, John Heasley <heas@shrubbery.net>
> wrote:
> >
> > > Am 16.05.2015 um 11:59 schrieb Thomas Mangin <
> > > thomas.mangin@exa-networks.co.uk>:
> > > >
> > > > I would rather see this totally harmless draft (as vendors can
> decide to
> > > ignore it without consequences) progress than seeing Cumulus assigning
> a
> > > capability number for it and later find that we have like multisession
> two
> > > different code for the same feature :p
> > >
> > > Or just keep track of your peering info in a database ... With contact
> > > info, business relationship, etc.  this is not a bgp problem, IMO.
> Its a
> > > CRM and NMS problem.
> > >
> >
> > In the data center, you've met the other side, and its you. I don't
> think I
> > said that carrying the hostname was a BGP problem. We see it as a way to
> > simplify operations in the DC, by supplementing numbers with names,
> >
> > Dinesh
>
>
> Pardon my ignorance of BGP, but wouldn't a check of the router-id
> resolve that issue.  You know that non-routable 4 bit thing that is
> unique and isn't an address (but somehow manages to fall within an
> assigned IPv4 prefix) that has been in BGP for a while.
>
> Look up the router-id maybe?  And yes peering info in a database has
> been successfully tried before.  If you need peering info, why is FQDN
> any easier to use to look it up than router-id?
>
> Isn't there something in DNS to map an address to FQDN?  Maybe you
> could use that.  I think some people have successfully used that too.
>
> Never ran a DC but I always thought that if you brought up a peering
> and "it was you" your network was in rather bad shape to start with.
>
> :-)
>
> Curtis
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>