IETF Logo Mail Archive

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

"Dongjie (Jimmy)" <jie.dong@huawei.com> Thu, 21 May 2015 02:39 UTC

Return-Path: <jie.dong@huawei.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 CB7501ACE87 for <idr@ietfa.amsl.com>; Wed, 20 May 2015 19:39:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 1ktMp1DxbFb3 for <idr@ietfa.amsl.com>; Wed, 20 May 2015 19:39:50 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0299F1ACE76 for <idr@ietf.org>; Wed, 20 May 2015 19:39:49 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BSU08053; Thu, 21 May 2015 02:39:48 +0000 (GMT)
Received: from NKGEML408-HUB.china.huawei.com (10.98.56.39) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 21 May 2015 03:39:47 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.152]) by nkgeml408-hub.china.huawei.com ([10.98.56.39]) with mapi id 14.03.0158.001; Thu, 21 May 2015 10:39:43 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: Nick Hilliard <nick@foobar.org>, Daniel Walton <dwalton@cumulusnetworks.com>, idr wg <idr@ietf.org>, Dinesh Dutt <ddutt@cumulusnetworks.com>
Thread-Topic: [Idr] draft-walton-bgp-hostname-capability-00
Thread-Index: AQHQj3dWocpdGUzGQES+WjyW1HSQCp2CrgCAgAMOwCA=
Date: Thu, 21 May 2015 02:39:42 +0000
Message-ID: <76CD132C3ADEF848BD84D028D243C92757D4CCA4@nkgeml512-mbx.china.huawei.com>
References: <CANL=f0h9ZV+SPr+2vcx2dEk4O9MxBAZJEU7xgHZDC=ep2g2r-g@mail.gmail.com> <555B22B7.4000207@foobar.org>
In-Reply-To: <555B22B7.4000207@foobar.org>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.97.131]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/vrbUH26MnlDYgiUbYtpuEk7ygIc>
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: Thu, 21 May 2015 02:39:51 -0000

Hi Nick, 

> -----Original Message-----
> From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Nick Hilliard
> Sent: Tuesday, May 19, 2015 7:47 PM
> To: Daniel Walton; idr wg; Dinesh Dutt
> Subject: Re: [Idr] draft-walton-bgp-hostname-capability-00
> 
> On 16/05/2015 02:26, 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.
> 
> I like this idea because it makes my life as an operator easier.
> 
> There is a similar option in ISIS for transmitting hostnames in ISIS.  This is
> operationally useful for a wide variety of purposes.
> 
> I would suggest that it would be more appropriate to define a generic text bgp
> capability along the lines of draft-ietf-idr-advisory, and define the BGP
> hostname as a subtype rather than using a dedicated bgp hostname capability.

Totally agree with this, and actually the "BGP Session Information Capability" as defined in draft-dong-idr-fsm-subcode-00 (only in the -00 version) can meet your requirement, in which the "peer description" is just one of the subtypes. This part was splitted out from later versions of draft-fsm-subcode, but this mechanism can be used if such information needs to be exchanged.

Best regards,
Jie

> 
> Nick
> 
> 
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr

v2.23.0 | Report a Bug | By Email