IETF Logo Mail Archive

Re: [trill] WG LC for draft-ietf-trill-arp-optimzation (2/8 to 2/22/2016)

Haoweiguo <haoweiguo@huawei.com> Mon, 15 February 2016 02:20 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 0104C1ACDEF; Sun, 14 Feb 2016 18:20:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.206
X-Spam-Level:
X-Spam-Status: No, score=-4.206 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.006, 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 gAl8JJo84c_A; Sun, 14 Feb 2016 18:20:00 -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 4FFA81ACDEC; Sun, 14 Feb 2016 18:19:59 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml403-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CEI44288; Mon, 15 Feb 2016 02:19:56 +0000 (GMT)
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.235.1; Mon, 15 Feb 2016 02:19:55 +0000
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.112]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.03.0235.001; Mon, 15 Feb 2016 10:19:52 +0800
From: Haoweiguo <haoweiguo@huawei.com>
To: Susan Hares <shares@ndzh.com>, "trill@ietf.org" <trill@ietf.org>
Thread-Topic: [trill] WG LC for draft-ietf-trill-arp-optimzation (2/8 to 2/22/2016)
Thread-Index: AQHRYt/k8PgP/Zr6XkmXxd45e06imp8sYDeW
Date: Mon, 15 Feb 2016 02:19:51 +0000
Message-ID: <DD5FC8DE455C3348B94340C0AB55173350293403@nkgeml513-mbx.china.huawei.com>
References: <016201d162d3$24160760$6c421620$@ndzh.com>
In-Reply-To: <016201d162d3$24160760$6c421620$@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_DD5FC8DE455C3348B94340C0AB55173350293403nkgeml513mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020204.56C135CD.0082, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.1.112, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: c59dc6f7a5250edaea503519276677c0
Archived-At: <http://mailarchive.ietf.org/arch/msg/trill/Qk_TtNfrdXt63dUCwzL_QqdgdDk>
Cc: 'Donald Eastlake' <d3e3e3@gmail.com>, "draft-ietf-trill-arp-optimization@ietf.org" <draft-ietf-trill-arp-optimization@ietf.org>, ''Alia Atlas'' <akatlas@gmail.com>, 'Jon Hudson' <jon.hudson@gmail.com>
Subject: Re: [trill] WG LC for draft-ietf-trill-arp-optimzation (2/8 to 2/22/2016)
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: <https://mailarchive.ietf.org/arch/browse/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, 15 Feb 2016 02:20:02 -0000

Hi,

I support the WG LC.

1)      Is draft-ietf-trill-arp-optimization technically sound?  Are there any flaws?

[weiguo]:  I think the arp optimization solution in this draft is OK, it can effectively reduce ARP request flooding in TRILL Campus. I have not found any flaws.

2)      Does draft-ietf-trill-arp-optimization have a key part in the directory services for TRILL?

[weiguo]: Yes, it can be used in directory server envionment and is a key part for ARP broadcast packets mitigation.

3)      Will TRILL ARP optimization be deployed in customer situations you are familiar with?

[weiguo]: It can be deployed in data center network where huge amount of servers often causes ARP broadcast storm.

Thanks,

weiguo

________________________________
From: Susan Hares [shares@ndzh.com]
Sent: Tuesday, February 09, 2016 8:45
To: trill@ietf.org
Cc: 'Donald Eastlake'; draft-ietf-trill-arp-optimization@ietf.org; 'Jon Hudson'; shares@ndzh.com; ''Alia Atlas''
Subject: [trill] WG LC for draft-ietf-trill-arp-optimzation (2/8 to 2/22/2016)

This begins a 2 week WG LC for draft-ietf-trill-optimization (2/8 to 2/22/2016).   The authors (Yizhou, Donald, Linda, Radia and Igor) should indicate whether they know of any IPR related to this draft.

The WG group should consider:

1)      Is draft-ietf-trill-arp-optimization technically sound?  Are there any flaws?

2)      Does draft-ietf-trill-arp-optimization have a key part in the directory services for TRILL?

3)      Will TRILL ARP optimization be deployed in customer situations you are familiar with?

Sue Hares

PS -  It is Chinese New Year celebration this week so a few members of our TRILL WG may begin to respond to this after the New Year celebration.

v2.23.0 | Report a Bug | By Email