Re: [trill] New Version Notification for draft-hao-trill-irb-05.txt

Muhammad Durrani <mdurrani@Brocade.com> Fri, 17 October 2014 08:32 UTC

Return-Path: <mdurrani@Brocade.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 578681A895C; Fri, 17 Oct 2014 01:32:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 CbZOOHb2NcsX; Fri, 17 Oct 2014 01:32:28 -0700 (PDT)
Received: from mx0a-000f0801.pphosted.com (mx0a-000f0801.pphosted.com [IPv6:2620:100:9001:7a::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4AEFB1A002C; Fri, 17 Oct 2014 01:32:28 -0700 (PDT)
Received: from pps.filterd (m0048193 [127.0.0.1]) by mx0a-000f0801.pphosted.com (8.14.5/8.14.5) with SMTP id s9H80BI7032374; Fri, 17 Oct 2014 01:31:52 -0700
Received: from hq1wp-exchub01.corp.brocade.com ([144.49.131.13]) by mx0a-000f0801.pphosted.com with ESMTP id 1q2c9cjsj0-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 17 Oct 2014 01:31:52 -0700
Received: from HQ1WP-EXHUB01.corp.brocade.com (10.70.36.14) by HQ1WP-EXCHUB01.corp.brocade.com (10.70.36.99) with Microsoft SMTP Server (TLS) id 14.3.123.3; Fri, 17 Oct 2014 01:31:51 -0700
Received: from HQ1-EXCH02.corp.brocade.com ([fe80::2d68:8453:a561:e26c]) by HQ1WP-EXHUB01.corp.brocade.com ([fe80::55ee:533:4b9d:a097%12]) with mapi; Fri, 17 Oct 2014 01:31:51 -0700
From: Muhammad Durrani <mdurrani@Brocade.com>
To: "Xiaorong (Andrew) Qu" <laodulaodu@gmail.com>, "internet-drafts@ietf.org" <internet-drafts@ietf.org>, "trill@ietf.org" <trill@ietf.org>
Date: Fri, 17 Oct 2014 01:31:50 -0700
Thread-Topic: New Version Notification for draft-hao-trill-irb-05.txt
Thread-Index: Ac/p3gEQK/+XRjPVSBeggChobvvVYAABhj2Q
Message-ID: <06FF377397785A4781BD13272EBF3D586655900DF9@HQ1-EXCH02.corp.brocade.com>
References: <20141015031004.12305.58169.idtracker@ietfa.amsl.com> <CAJ_UP_djWR=6SnpsxDzrd=JEJoweGiJG06Trfrk4sqywGf3o+g@mail.gmail.com>
In-Reply-To: <CAJ_UP_djWR=6SnpsxDzrd=JEJoweGiJG06Trfrk4sqywGf3o+g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_06FF377397785A4781BD13272EBF3D586655900DF9HQ1EXCH02corp_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.12.52, 1.0.28, 0.0.0000 definitions=2014-10-17_02:2014-10-16,2014-10-17,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1410170082
Archived-At: http://mailarchive.ietf.org/arch/msg/trill/4zgiyGAWllPx4x2Bfi2TqbN2kwA
Cc: "Donald E. Eastlake 3rd" <d3e3e3@gmail.com>, Liang Xia <frank.xialiang@huawei.com>, Weiguo Hao <haoweiguo@huawei.com>, Li Yizhou <liyizhou@huawei.com>
Subject: Re: [trill] New Version Notification for draft-hao-trill-irb-05.txt
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: Fri, 17 Oct 2014 08:32:30 -0000

I agree with Andrew – suggested distributed model will solve scale issues as seen with centralized model for ARP/VRRP etc. This is essential for large deployments with massive hosts targeted for scale out fabric.
The proposed draft will help product implementing TRILL based fabric for hyper scale data center.

Regards,
Muhammad

From: Xiaorong (Andrew) Qu [mailto:laodulaodu@gmail.com]
Sent: Friday, October 17, 2014 12:43 AM
To: internet-drafts@ietf.org; trill@ietf.org
Cc: Li Yizhou; Liang Xia; Weiguo Hao; Muhammad Durrani; Donald E. Eastlake 3rd
Subject: Re: New Version Notification for draft-hao-trill-irb-05.txt

Hi Weiguo,

Thanks a lot.

This distributed gateway proposal helps resolve ARP storm kind of issues, architect is more clean than centralized
model.  solving VRRP scalability issue when centralized model is utilized for large number L2 segments.

Specially when TRILL is used to form network fabric that is more than large L2 network,  distributed gateway
works seemlessly like one system with each interface configured as L3 interface.  To servers,  each L3 interface is
a nature default gateway that is distributed manner.

Andrew

On Tue, Oct 14, 2014 at 8:10 PM, <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>> wrote:

A new version of I-D, draft-hao-trill-irb-05.txt
has been successfully submitted by Weiguo Hao and posted to the
IETF repository.

Name:           draft-hao-trill-irb
Revision:       05
Title:          TRILL Distributed Layer 3 Gateway
Document date:  2014-10-15
Group:          Individual Submission
Pages:          20
URL:            http://www.ietf.org/internet-drafts/draft-hao-trill-irb-05.txt
Status:         https://datatracker.ietf.org/doc/draft-hao-trill-irb/
Htmlized:       http://tools.ietf.org/html/draft-hao-trill-irb-05
Diff:           http://www.ietf.org/rfcdiff?url2=draft-hao-trill-irb-05

Abstract:
   Currently TRILL protocol provides optimal pair-wise data frame forwarding
for    layer 2 intra-subnet traffic but not for layer 3 inter-subnet traffic.
A    centralized gateway solution is typically used for layer 3 inter-subnet
traffic    forwarding but has following issues:




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org<http://tools.ietf.org>.

The IETF Secretariat