IETF Logo Mail Archive

Re: [Idr] Early Allocation call #1 - draft-ietf-idr-flowspec-path-redirect

Zhuangshunwan <zhuangshunwan@huawei.com> Mon, 15 January 2018 03:20 UTC

Return-Path: <zhuangshunwan@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 46C9B126D46 for <idr@ietfa.amsl.com>; Sun, 14 Jan 2018 19:20:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.229
X-Spam-Level:
X-Spam-Status: No, score=-4.229 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 lTEmedGB84xl for <idr@ietfa.amsl.com>; Sun, 14 Jan 2018 19:20:52 -0800 (PST)
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 60099129966 for <idr@ietf.org>; Sun, 14 Jan 2018 19:20:52 -0800 (PST)
Received: from LHREML710-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 661C29AC1A5FA for <idr@ietf.org>; Mon, 15 Jan 2018 03:20:49 +0000 (GMT)
Received: from NKGEML413-HUB.china.huawei.com (10.98.56.74) by LHREML710-CAH.china.huawei.com (10.201.108.33) with Microsoft SMTP Server (TLS) id 14.3.361.1; Mon, 15 Jan 2018 03:20:49 +0000
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by NKGEML413-HUB.china.huawei.com ([10.98.56.74]) with mapi id 14.03.0361.001; Mon, 15 Jan 2018 11:20:42 +0800
From: Zhuangshunwan <zhuangshunwan@huawei.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
CC: "'John G. Scudder'" <jgs@bgp.nu>
Thread-Topic: [Idr] Early Allocation call #1 - draft-ietf-idr-flowspec-path-redirect
Thread-Index: AdONr9GM83SjUQeHT3W3RHXqLsh0AQ==
Date: Mon, 15 Jan 2018 03:20:42 +0000
Message-ID: <19AB2A007F56DB4E8257F949A2FB9858CDA6E060@NKGEML515-MBX.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.130.202.166]
Content-Type: multipart/alternative; boundary="_000_19AB2A007F56DB4E8257F949A2FB9858CDA6E060NKGEML515MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/OPLWdGutR--Wwp1W5IfdxNOky7Y>
Subject: Re: [Idr] Early Allocation call #1 - draft-ietf-idr-flowspec-path-redirect
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: Mon, 15 Jan 2018 03:20:54 -0000

Support

Cheers,
SHunwan


·¢¼þÈË: Idr [mailto:idr-bounces@ietf.org] ´ú±í Susan Hares
·¢ËÍʱ¼ä: 2018Äê1ÔÂ13ÈÕ 0:43
ÊÕ¼þÈË: idr@ietf.org
³­ËÍ: 'John G. Scudder' <jgs@bgp.nu>
Ö÷Ìâ: [Idr] Early Allocation call #1 - draft-ietf-idr-flowspec-path-redirect

This begins a 1 week WG call to approve the early allocation of code points for draft-ietf-idr-flowspec-path-redirect.  You can obtain a copy of the specification at:

https://datatracker.ietf.org/doc/draft-ietf-idr-flowspec-path-redirect/

There are two groups implementing and testing code based on the -03.txt version.  The authors consider the specification stable.

In your comments on this call, please indicate if you:

1)      Feel the allocation is in the best interest of Internet (aka ¨C assign code points early),

2)      If you feel there any problem with providing an early allocation.

If we have enough responses after the  1 week, the chairs will forward the request to the AD.  We are going with a 1 week call because many of you have indicated you wish to reduce the time and effort to get these early allocations.

If there are not enough responses after 1 week, we will extend this call to a second week.


Sue Hares

v2.23.0 | Report a Bug | By Email