Re: [dhcwg] Adoption Call for draft-cui-dhc-dhcpv6-prefix-length-hint-issue (Ends January 8, 2016)
Sheng Jiang <jiangsheng@huawei.com> Fri, 18 December 2015 01:06 UTC
Return-Path: <jiangsheng@huawei.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A3B81B31A1 for <dhcwg@ietfa.amsl.com>; Thu, 17 Dec 2015 17:06:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 PmyG4PLrfaZQ for <dhcwg@ietfa.amsl.com>; Thu, 17 Dec 2015 17:06:33 -0800 (PST)
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 9AA011B31A0 for <dhcwg@ietf.org>; Thu, 17 Dec 2015 17:06:32 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml404-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CFP29786; Fri, 18 Dec 2015 01:06:29 +0000 (GMT)
Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.235.1; Fri, 18 Dec 2015 01:06:29 +0000
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.181]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.03.0235.001; Fri, 18 Dec 2015 09:06:23 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: "Bernie Volz (volz)" <volz@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: Adoption Call for draft-cui-dhc-dhcpv6-prefix-length-hint-issue (Ends January 8, 2016)
Thread-Index: AdE4MfuqkAEjr/PZS32nv4P+3Sj+0QA/bo3Q
Date: Fri, 18 Dec 2015 01:06:23 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B927BC22711@nkgeml512-mbx.china.huawei.com>
References: <ece35e634c91412e86004506b89477c7@XCH-ALN-003.cisco.com>
In-Reply-To: <ece35e634c91412e86004506b89477c7@XCH-ALN-003.cisco.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.99.197]
Content-Type: multipart/alternative; boundary="_000_5D36713D8A4E7348A7E10DF7437A4B927BC22711nkgeml512mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020204.56735C16.0141, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.7.181, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 43d70206fa24ecbc9c004890893e035f
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/M5FJhUm8ikhs3Keaf_ZkYow5X-E>
Subject: Re: [dhcwg] Adoption Call for draft-cui-dhc-dhcpv6-prefix-length-hint-issue (Ends January 8, 2016)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Dec 2015 01:06:35 -0000
I am support to adopt this document and publish it as soon as possible because I am thinking these issues should be solved in our ongoing 3315bis, which actually integrated RFC 3633. So, this document should be published well before 3315bis and 3315bis should solve all issues raised by this document. Then perfect ending. Job done. Regards, Sheng From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz) Sent: Thursday, December 17, 2015 2:46 AM To: dhcwg@ietf.org Subject: [dhcwg] Adoption Call for draft-cui-dhc-dhcpv6-prefix-length-hint-issue (Ends January 8, 2016) Hello: This email initiates a WG call for adoption of the draft-cui-dhc-dhcpv6-prefix-length-hint-issue-03 (http://tools.ietf.org/html/draft-cui-dhc-dhcpv6-prefix-length-hint-issue-03) document as a DHC WG work item. Please indicate whether you support the adoption or not, and if not, why not. See https://tools.ietf.org/html/rfc7221#section-2.2 if you have questions about the criteria for adoption. This document falls within the WG Charter (https://datatracker.ietf.org/wg/dhc/charter/) under items #2, #3, and #4. There are currently NO IPR claims against this draft (please see http://datatracker.ietf.org/wg/dhc/documents/ as this could change at any time). The co-chairs will determine the consensus after January 8, 2016. (This is a longer period than usual because of the year end Holidays.) Happy Holidays & New Year! - Tomek & Bernie
- [dhcwg] Adoption Call for draft-cui-dhc-dhcpv6-pr… Bernie Volz (volz)
- Re: [dhcwg] Adoption Call for draft-cui-dhc-dhcpv… tianxiang li
- Re: [dhcwg] Adoption Call for draft-cui-dhc-dhcpv… Marcin Siodelski
- Re: [dhcwg] Adoption Call for draft-cui-dhc-dhcpv… Linhui Sun
- Re: [dhcwg] Adoption Call for draft-cui-dhc-dhcpv… Tomek Mrugalski
- Re: [dhcwg] Adoption Call for draft-cui-dhc-dhcpv… Sheng Jiang
- Re: [dhcwg] Adoption Call for draft-cui-dhc-dhcpv… Bernie Volz (volz)
- Re: [dhcwg] Adoption Call for draft-cui-dhc-dhcpv… Bernie Volz (volz)
- Re: [dhcwg] Adoption Call for draft-cui-dhc-dhcpv… Timothy Winters
- [dhcwg] Results of Adoption Call for draft-cui-dh… Bernie Volz (volz)