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

"Thomas Mangin" <thomas.mangin@exa-networks.co.uk> Sun, 17 May 2015 10:00 UTC

Return-Path: <thomas.mangin@exa-networks.co.uk>
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 BEA4B1A9025 for <idr@ietfa.amsl.com>; Sun, 17 May 2015 03:00:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 mYVX_dGaHnoD for <idr@ietfa.amsl.com>; Sun, 17 May 2015 03:00:28 -0700 (PDT)
Received: from out-1.mail.exa.net.uk (out-1.mail.exa.net.uk [82.219.4.129]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 951171A901C for <idr@ietf.org>; Sun, 17 May 2015 03:00:28 -0700 (PDT)
Received: from smtp-5.exa.net.uk (unknown [82.219.5.5]) by out-1.mail.exa.net.uk (ExaSMTPD) with ESMTP id C26241C0058; Sun, 17 May 2015 11:00:25 +0100 (BST)
Received: from smtp-5.exa.net.uk (localhost [127.0.0.1]) by smtp-5.exa.net.uk (ExaSMTPD) with ESMTP id B13FB40CFF; Sun, 17 May 2015 11:00:25 +0100 (BST)
Received: from [10.37.129.2] (ptr-34.212.219.82.rev.exa.net.uk [82.219.212.34]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: thomas@mangin.com) by smtp-5.exa.net.uk (ExaSMTPD) with ESMTPSA; Sun, 17 May 2015 11:00:25 +0100 (BST)
From: Thomas Mangin <thomas.mangin@exa-networks.co.uk>
To: Randy Bush <randy@psg.com>
Date: Sun, 17 May 2015 11:00:13 +0100
Message-ID: <F59C5345-A2EF-4BC7-AA5B-56F2D5C94562@exa-networks.co.uk>
In-Reply-To: <m2fv6vv9nm.wl%randy@psg.com>
References: <20150516015819.5849234.74476.67011@gmail.com> <CANL=f0gAfs9f-Jt7r3bxMfB7f3Ta+funv8nvmkiCmFsQfGHTcg@mail.gmail.com> <CA+b+ERmY46GHLJUhi5PzwyVJ4Wcns_R11QXC=oLMzAXrYi-v2g@mail.gmail.com> <CABg5FUV5Z+S_m6V7=dB_cuOZpDV-MS_cV+mhwERtjaNCiNfT2w@mail.gmail.com> <CA+b+ERmCpjbBmNAeFyNm6_KTWtOB41Zge559O4jbtEjwKG+yXg@mail.gmail.com> <CABg5FUVSq4Xunivo3tBNh0=x+W=ZOD9pUYGWs18EcuXiFG-4MQ@mail.gmail.com> <CA+b+ER=m_LttyMumi+JLd1cfTLqk16RAQgfbX4qmxGAh1k5Wxw@mail.gmail.com> <CANL=f0iPLinA6Qr8-r6mev4474UZT9g5Bjng_6+f7xPZ2zdfVg@mail.gmail.com> <FC7F6336-4846-4C4C-B002-4DE255F10B2A@exa-networks.co.uk> <89600117-8199-45E0-BB06-C69E94091C17@shrubbery.net> <20150516192556.GB73434@Vurt.local> <m2pp60ur4m.wl%randy@psg.com> <9D75C21F-B76D-451C-B367-2543C94EBEB7@exa-networks.co.uk> <m2fv6vv9nm.wl%randy@psg.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
X-Mailer: MailMate (1.9.1r5084)
X-Virus-Scanned: ClamAV using ClamSMTP
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/UripF9J-yBENHpM5DHQMn3Cz36o>
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: Sun, 17 May 2015 10:00:30 -0000


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.

Thomas