IETF Logo Mail Archive

Re: [tsvwg] Fwd: CALL FOR ADOPTION TSVWG: draft-briscoe-tsvwg-ecn-encap-guidelines - to end 4th March 2014

Weixinpeng <weixinpeng@huawei.com> Wed, 19 February 2014 01:25 UTC

Return-Path: <weixinpeng@huawei.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE92D1A01FC for <tsvwg@ietfa.amsl.com>; Tue, 18 Feb 2014 17:25:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.749
X-Spam-Level:
X-Spam-Status: No, score=-4.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.548, 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 A6kQShcfsmTh for <tsvwg@ietfa.amsl.com>; Tue, 18 Feb 2014 17:25:13 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 077B01A00F5 for <tsvwg@ietf.org>; Tue, 18 Feb 2014 17:25:12 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BDS60126; Wed, 19 Feb 2014 01:25:09 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 19 Feb 2014 01:24:59 +0000
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 19 Feb 2014 01:25:08 +0000
Received: from NKGEML507-MBX.china.huawei.com ([169.254.5.27]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.03.0158.001; Wed, 19 Feb 2014 09:25:02 +0800
From: Weixinpeng <weixinpeng@huawei.com>
To: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, tsvwg WG <tsvwg@ietf.org>
Thread-Topic: [tsvwg] Fwd: CALL FOR ADOPTION TSVWG: draft-briscoe-tsvwg-ecn-encap-guidelines - to end 4th March 2014
Thread-Index: AQHPLAo82icm/rnNnEKtB1n8XmGhfpq7yg1Q
Date: Wed, 19 Feb 2014 01:25:01 +0000
Message-ID: <C5C3BB522B1DDF478AA09545169155B46D7EB62F@nkgeml507-mbx.china.huawei.com>
References: <530232BD.4080508@erg.abdn.ac.uk> <53024E41.9090901@erg.abdn.ac.uk>
In-Reply-To: <53024E41.9090901@erg.abdn.ac.uk>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.76.176]
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/tsvwg/EorTPS2ribwHuPWDq2a7-RL5eMY
Subject: Re: [tsvwg] Fwd: CALL FOR ADOPTION TSVWG: draft-briscoe-tsvwg-ecn-encap-guidelines - to end 4th March 2014
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2014 01:25:15 -0000

Hi Gorry and all,
I support this document and I think adopting this document in TSVWG is a good idea.

Best Regards,
Xinpeng Wei

>-----Original Message-----
>From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of Gorry Fairhurst
>Sent: Tuesday, February 18, 2014 2:01 AM
>To: tsvwg WG
>Subject: [tsvwg] Fwd: CALL FOR ADOPTION TSVWG:
>draft-briscoe-tsvwg-ecn-encap-guidelines - to end 4th March 2014
>
>
>The authors of " Guidelines for Adding Congestion Notification to Protocols
>that Encapsulate IP"
>(draft-briscoe-tsvwg-ecn-encap-guidelines) request that this is adopted as
>TSVWG item.
>
>The IETF-88 meeting and following mailing list threads indicated some WG
>  support for this, so we are now ready to make a formal decision and this
>email is to allow people to confirm that they have sufficient energy to
>complete this work in TSVWG.
>
>* PLEASE send an email to this list if you think adopting this document in
>TSVWG is a good **OR** bad idea.
>
>* Please indicate if you are willing to REVIEW such a document during its
>development.
>
>
>Please send al notes of support/comments to the TSVWG list of chairs by the
>date above.
>
>Best wishes,
>
>Gorry, David and James.
>(TSVWG Co-Chairs)
>

v2.23.0 | Report a Bug | By Email