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

[Curtis Villamizar <[e-mail]>]

In message <[e-mail]>
Dinesh Dutt writes:
 
> On Sun, May 17, 2015 at 3:00 AM, Thomas Mangin <
> [e-mail]> wrote:
>  
> >
> >
> > http://exa.net.uk/about/contact-us
> > On 17 May 2015, at 10:24, Randy Bush wrote:
> >
> > >>> and we're all waiting for the attack where the sender puts tasty
> > >>> things in the supposed dns name
> > >> If the worry is about the complexity of handling UTF-8, the draft
> > >> could be change to require ascii 'a' through 'z' (in a
> > >> case-insensitive manner), the digits '0' through '9', and the hyphen
> > >> ('-') to be put in the draft as it is what DNS allows.
> > >
> > > bzzzzt!  dns is eight bit clear.  you are thinking of some restrictions
> > > on hostnames, the leftmost chunk of the lhs at most.
> >
> > I stand corrected.
> > That said, then perhaps the way is to only pass the hostname and not the
> > fqdn.
> >
>  
> That'll be fine. We added fqdn to allow for cases outside the DC.
>  
> On a different note, OSPF has a far more involved modification to allow the
> carrying of hostnames (https://tools.ietf.org/html/rfc5642). I'm curious as
> to why that was considered OK.
>  
> Dinesh


OSPF can and often is run on unnumbered interfaces (or using link
local addresses in IPv6).  You can't use rDNS in these cases and the
router-id is not supposed to be an address so you can't be sure a rDNS
lookup of the router-id will yield anything useful.  [Realistically,
ISIS did it so OSPF felt obligated.]

AFAIK - BGP is still being run on numbered interfaces or bound to a
numbered loopback interface, which in both cases can be looked up
using rDNS to get FQDN.

If you use reuse PI space within the DC rather than routeable, or
unique allocation from 10/8, or better yet use IPv6, you create your
own mess and you are proposing changing BGP to bandaid over it.

Cluelessly yours,

Curtis