Re: [trill] Should we adopt draft-dunbar-trill-directory-assisted-edge-05.txt as a WG document?
<david.black@emc.com> Mon, 18 June 2012 17:23 UTC
Return-Path: <david.black@emc.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 BD5E021F85D1 for <trill@ietfa.amsl.com>; Mon, 18 Jun 2012 10:23:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.297
X-Spam-Level:
X-Spam-Status: No, score=-102.297 tagged_above=-999 required=5 tests=[AWL=0.302, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OaCTFe8Q+DS2 for <trill@ietfa.amsl.com>; Mon, 18 Jun 2012 10:23:53 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 241C621F859A for <trill@ietf.org>; Mon, 18 Jun 2012 10:23:52 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q5IHNpMi009138 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <trill@ietf.org>; Mon, 18 Jun 2012 13:23:51 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.145]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor) for <trill@ietf.org>; Mon, 18 Jun 2012 13:23:34 -0400
Received: from mxhub08.corp.emc.com (mxhub08.corp.emc.com [128.222.70.205]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q5IHNYsO030774 for <trill@ietf.org>; Mon, 18 Jun 2012 13:23:34 -0400
Received: from mx15a.corp.emc.com ([169.254.1.189]) by mxhub08.corp.emc.com ([128.222.70.205]) with mapi; Mon, 18 Jun 2012 13:23:33 -0400
From: david.black@emc.com
To: trill@ietf.org
Date: Mon, 18 Jun 2012 13:23:32 -0400
Thread-Topic: [trill] Should we adopt draft-dunbar-trill-directory-assisted-edge-05.txt as a WG document?
Thread-Index: Ac1KXk+Grl3TmycyRFeNiQSoaZERVADF8t1w
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71208C13FD8@MX15A.corp.emc.com>
References: <4FDA31F0.5000806@acm.org>
In-Reply-To: <4FDA31F0.5000806@acm.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: Re: [trill] Should we adopt draft-dunbar-trill-directory-assisted-edge-05.txt as a WG document?
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.12
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, 18 Jun 2012 17:23:53 -0000
As an informational framework-like draft, I support WG adoption of this draft. There are likely to be opportunities to use the same protocol(s) for directory access as nvo3 will use, with differences based on encapsulation differences (trill needs identify and address the remote RBridge at layer 2, nvo3 needs to identify and address the remote NVE at layer 3). Thanks, --David > -----Original Message----- > From: trill-bounces@ietf.org [mailto:trill-bounces@ietf.org] On Behalf Of Erik > Nordmark > Sent: Thursday, June 14, 2012 2:48 PM > To: trill@ietf.org > Subject: [trill] Should we adopt draft-dunbar-trill-directory-assisted-edge- > 05.txt as a WG document? > > > <http://http://tools.ietf.org/html/draft-dunbar-trill-directory-assisted-edge- > 05> > > We've discussed earlier versions of this document in the WG in the past, > and it seems like useful information for a technique that helps with ARP > and ND scaling. It does not include any protocol changes or extensions. > > The document is intended as an informational document (it says "Intended > status: Standard Track" but that is incorrect) explaining how > directories can fit into TRILL. > > Note that there is claimed IPR associated with the draft: > <https://datatracker.ietf.org/ipr/1788/> > > Please send comments to the TRILL list before June 27. > > Thanks, > Erik > _______________________________________________ > trill mailing list > trill@ietf.org > https://www.ietf.org/mailman/listinfo/trill
- [trill] Should we adopt draft-dunbar-trill-direct… Erik Nordmark
- Re: [trill] Should we adopt draft-dunbar-trill-di… Anoop Ghanwani
- Re: [trill] Should we adopt draft-dunbar-trill-di… Sam Aldrin
- Re: [trill] Should we adopt draft-dunbar-trill-di… Linda Dunbar
- Re: [trill] Should we adopt draft-dunbar-trill-di… Radia Perlman
- Re: [trill] Should we adopt draft-dunbar-trill-di… Yizhou Li
- Re: [trill] Should we adopt draft-dunbar-trill-di… hu.fangwei
- Re: [trill] Should we adopt draft-dunbar-trill-di… zhai.hongjun
- Re: [trill] Should we adopt draft-dunbar-trill-di… david.black
- Re: [trill] Should we adopt draft-dunbar-trill-di… Mingui Zhang
- Re: [trill] Should we adopt draft-dunbar-trill-di… Naveen Nimmu
- Re: [trill] Should we adopt draft-dunbar-trill-di… Tissa Senevirathne (tsenevir)
- Re: [trill] Should we adopt draft-dunbar-trill-di… Russ White
- Re: [trill] Should we adopt draft-dunbar-trill-di… Donald Eastlake
- [trill] draft-dunbar-trill-directory-assisted-edg… Erik Nordmark