Re: [trill] draft-ietf-trill-centralized-replication - 2 Week WG LC (5/24 to 6/7)

Linda Dunbar <linda.dunbar@huawei.com> Wed, 01 June 2016 15:05 UTC

Return-Path: <linda.dunbar@huawei.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B68B612D549; Wed, 1 Jun 2016 08:05:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.646
X-Spam-Level:
X-Spam-Status: No, score=-5.646 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 ZIcfy1-Oar-u; Wed, 1 Jun 2016 08:05:21 -0700 (PDT)
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 8731412D5AA; Wed, 1 Jun 2016 08:05:20 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml706-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CQB47241; Wed, 01 Jun 2016 15:05:18 +0000 (GMT)
Received: from DFWEML702-CAH.china.huawei.com (10.193.5.176) by lhreml706-cah.china.huawei.com (10.201.5.182) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 1 Jun 2016 16:05:17 +0100
Received: from DFWEML501-MBB.china.huawei.com ([10.193.5.179]) by dfweml702-cah.china.huawei.com ([10.193.5.176]) with mapi id 14.03.0235.001; Wed, 1 Jun 2016 08:05:15 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: Susan Hares <shares@ndzh.com>
Thread-Topic: [trill] draft-ietf-trill-centralized-replication - 2 Week WG LC (5/24 to 6/7)
Thread-Index: AQHRvAxXRuM8AZ3qFkGYepDnEBnJ+5/UtbZw
Date: Wed, 1 Jun 2016 15:05:14 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F657EAD454@dfweml501-mbb>
References: <021701d1b5cd$32cd8d30$9868a790$@ndzh.com> <CAFFrbz8scnJmfj5p46JKzQk-N3Zd_S3Y9pXBVPsEOmoF2-dQ5w@mail.gmail.com>
In-Reply-To: <CAFFrbz8scnJmfj5p46JKzQk-N3Zd_S3Y9pXBVPsEOmoF2-dQ5w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.192.11.71]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F657EAD454dfweml501mbb_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020201.574EF9AF.009C, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 43574169086ecf7c67ecc563096c2558
Archived-At: <http://mailarchive.ietf.org/arch/msg/trill/zjGXHIn-6FOkjLy43auX9i24rYg>
Cc: Donald Eastlake <d3e3e3@gmail.com>, "trill-chairs@ietf.org" <trill-chairs@ietf.org>, "draft-ietf-trill-centralized-replication@ietf.org" <draft-ietf-trill-centralized-replication@ietf.org>, "trill@ietf.org" <trill@ietf.org>
Subject: Re: [trill] draft-ietf-trill-centralized-replication - 2 Week WG LC (5/24 to 6/7)
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 01 Jun 2016 15:05:23 -0000


Support,

Linda Dunbar


On Tue, May 24, 2016 at 8:01 AM, Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>> wrote:
This begins a 2 week WG LC for draft-ietf-trill-centralized-repllication-05 (5/24 to 6/7)

https://datatracker.ietf.org/doc/draft-ietf-trill-centralized-replication/


In your comments please include answers to the following questions:


1)      Does this solve the resolve this RPF check failure issue through centralized replication?

2)      Is this draft ready for publications?  Do you have any concerns regarding this technology?

3)      Do you know of any implementations?

Sue Hares  and Jon Hudson





.