Re: [trill] Two Week WG Adoption call for draft-zhang-trill-mtu-negotiation (2/15 to 3/1)

Haoweiguo <haoweiguo@huawei.com> Mon, 16 February 2015 06:11 UTC

Return-Path: <haoweiguo@huawei.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B33F61A874D for <trill@ietfa.amsl.com>; Sun, 15 Feb 2015 22:11:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.61
X-Spam-Level:
X-Spam-Status: No, score=-3.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_55=0.6, 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 d7caElou-6pp for <trill@ietfa.amsl.com>; Sun, 15 Feb 2015 22:11:44 -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 93B351A874B for <trill@ietf.org>; Sun, 15 Feb 2015 22:11:42 -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 BSR18400; Mon, 16 Feb 2015 06:11:41 +0000 (GMT)
Received: from NKGEML403-HUB.china.huawei.com (10.98.56.34) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 16 Feb 2015 06:11:40 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.146]) by nkgeml403-hub.china.huawei.com ([10.98.56.34]) with mapi id 14.03.0158.001; Mon, 16 Feb 2015 14:11:36 +0800
From: Haoweiguo <haoweiguo@huawei.com>
To: Susan Hares <shares@ndzh.com>, "trill@ietf.org" <trill@ietf.org>
Thread-Topic: [trill] Two Week WG Adoption call for draft-zhang-trill-mtu-negotiation (2/15 to 3/1)
Thread-Index: AQHQSVoZofbVjezb/UuuV6UzTyTUVJzyneHp
Date: Mon, 16 Feb 2015 06:11:35 +0000
Message-ID: <DD5FC8DE455C3348B94340C0AB5517334F844C52@nkgeml501-mbs.china.huawei.com>
References: <023201d04952$b10c1790$132446b0$@ndzh.com>
In-Reply-To: <023201d04952$b10c1790$132446b0$@ndzh.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.135.23.94]
Content-Type: multipart/alternative; boundary="_000_DD5FC8DE455C3348B94340C0AB5517334F844C52nkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/trill/I-Rd7qhLk6YmW2IhlHHJi2w8xuE>
Cc: 'Donald Eastlake' <d3e3e3@gmail.com>, "jon.hudson@gmail.com" <jon.hudson@gmail.com>
Subject: Re: [trill] Two Week WG Adoption call for draft-zhang-trill-mtu-negotiation (2/15 to 3/1)
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/trill/>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Feb 2015 06:11:47 -0000

Support.

Link-wide MTU and its testing method are newly introduced in this draft, because link-wide MTU is frequently larger than campus wide MTU, so link-wide MTU introduction will help to reduce packet fragments for some link local applications like CSNPs,PSNPs,and etc.

Thanks,

weiguo

________________________________
From: Susan Hares [shares@ndzh.com]
Sent: Monday, February 16, 2015 3:07
To: trill@ietf.org
Cc: 'Donald Eastlake'; jon.hudson@gmail.com
Subject: [trill] Two Week WG Adoption call for draft-zhang-trill-mtu-negotiation (2/15 to 3/1)

This begins a 2 week WG adoption call for draft-zhang-trill-mtu-negotiation-08 (2/15 to 3/1).  Please comment on the draft technical issues and discuss whether this is useful in TRILL deployments.   In your comments include an indication of “support” or “No support”.

Sue Hares and Jon Hudson