Re: [Idr] I-D Action: draft-ietf-idr-bgp-ipv6-rt-constrain-12.txt
"Dongjie (Jimmy)" <jie.dong@huawei.com> Thu, 26 April 2018 12:11 UTC
Return-Path: <jie.dong@huawei.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EA271200C1; Thu, 26 Apr 2018 05:11:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 dao4LZMqhQiU; Thu, 26 Apr 2018 05:11:47 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 915A11201F2; Thu, 26 Apr 2018 05:11:47 -0700 (PDT)
Received: from lhreml702-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 00FD16BAF56AF; Thu, 26 Apr 2018 13:11:42 +0100 (IST)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml702-cah.china.huawei.com (10.201.108.43) with Microsoft SMTP Server (TLS) id 14.3.382.0; Thu, 26 Apr 2018 13:11:40 +0100
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0361.001; Thu, 26 Apr 2018 20:11:33 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: "idr@ietf.org" <idr@ietf.org>
CC: "idr-chairs@ietf.org" <idr-chairs@ietf.org>
Thread-Topic: [Idr] I-D Action: draft-ietf-idr-bgp-ipv6-rt-constrain-12.txt
Thread-Index: AQHT3VcWkxDMwLaee0ajSLAYsuD4maQS89hQ
Date: Thu, 26 Apr 2018 12:11:32 +0000
Message-ID: <76CD132C3ADEF848BD84D028D243C927984099A9@NKGEML515-MBX.china.huawei.com>
References: <152474439500.22908.1104216463799940715@ietfa.amsl.com>
In-Reply-To: <152474439500.22908.1104216463799940715@ietfa.amsl.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.130.151.75]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/ut9XH3a-7UPSeijoxNa0vgx4bzs>
Subject: Re: [Idr] I-D Action: draft-ietf-idr-bgp-ipv6-rt-constrain-12.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 26 Apr 2018 12:11:50 -0000
Hi all, This new version updates the IANA Considerations section following the guidance of the chairs. Best regards, Jie > -----Original Message----- > From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org > Sent: Thursday, April 26, 2018 8:07 PM > To: i-d-announce@ietf.org > Cc: idr@ietf.org > Subject: [Idr] I-D Action: draft-ietf-idr-bgp-ipv6-rt-constrain-12.txt > > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Inter-Domain Routing WG of the IETF. > > Title : IPv6 Extensions for Route Target Distribution > Authors : Keyur Patel > Robert Raszuk > Martin Djernaes > Jie Dong > Mach(Guoyi) Chen > Filename : draft-ietf-idr-bgp-ipv6-rt-constrain-12.txt > Pages : 6 > Date : 2018-04-26 > > Abstract: > The current route target distribution specification as described in > [RFC 4684] defines Route Target NLRIs of maximum length of 12 bytes. > The IPv6 specific Route Target extended community is defined in [RFC > 5701] as length of 20 bytes. Since the current specification only > supports prefixes of maximum length of 12 bytes, the lack of an IPv6 > specific Route Target reachability information may be a problem when > an operator wants to use this application in a pure IPv6 environment. > This document defines an extension that allows BGP to exchange longer > length IPv6 Route Target prefixes. > > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-ipv6-rt-constrain/ > > There are also htmlized versions available at: > https://tools.ietf.org/html/draft-ietf-idr-bgp-ipv6-rt-constrain-12 > https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgp-ipv6-rt-constrain-12 > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-bgp-ipv6-rt-constrain-12 > > > Please note that it may take a couple of minutes from the time of submission > until the htmlized version and diff are available at tools.ietf.org. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://www.ietf.org/mailman/listinfo/idr
- [Idr] I-D Action: draft-ietf-idr-bgp-ipv6-rt-cons… internet-drafts
- Re: [Idr] I-D Action: draft-ietf-idr-bgp-ipv6-rt-… Dongjie (Jimmy)