Re: [trill] Should we make draft-mrw-trill-over-ip-01 a WG document?

"Tissa Senevirathne (tsenevir)" <tsenevir@cisco.com> Mon, 14 May 2012 19:06 UTC

Return-Path: <tsenevir@cisco.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 7860C21F8763 for <trill@ietfa.amsl.com>; Mon, 14 May 2012 12:06:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.165
X-Spam-Level:
X-Spam-Status: No, score=-9.165 tagged_above=-999 required=5 tests=[AWL=1.434, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 u06HNxEWsAGb for <trill@ietfa.amsl.com>; Mon, 14 May 2012 12:06:18 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 1031A21F88BD for <trill@ietf.org>; Mon, 14 May 2012 12:06:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=tsenevir@cisco.com; l=2044; q=dns/txt; s=iport; t=1337022377; x=1338231977; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=q5qV/n00qtgcEXNAR8GXPWbQxM0lJ/OSYcio57gpsSU=; b=BLI0TEBuLI4FHzpebracamqymxRmx3mh5hKmqEDxXLK6YzeOcPgPHnym lKJMgbU1NNsScOLB9YCf7+n9DNWPcnfn3/Anezq5MSAOjkq957aZbHSKv e4H5/QFe/IQ41RvhPb8BvFjOAOvnW9HNl2Uc7ZxdlQ4CQergsn17LUY6T I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAHVWsU+rRDoJ/2dsb2JhbABEs3SBB4IVAQEBBAEBAQ8BHT4LDAQCAQgRBAEBAQoGFwEGASYfCQgBAQQBEggTB4drDJpkn24EixqFHWMEiDA0m3CBaYMJ
X-IronPort-AV: E=Sophos;i="4.75,588,1330905600"; d="scan'208";a="42181155"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-3.cisco.com with ESMTP; 14 May 2012 19:06:15 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id q4EJ6FQN025237; Mon, 14 May 2012 19:06:15 GMT
Received: from xmb-sjc-214.amer.cisco.com ([171.70.151.145]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 14 May 2012 12:06:15 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 14 May 2012 12:06:09 -0700
Message-ID: <344037D7CFEFE84E97E9CC1F56C5F4A5011CB0E0@xmb-sjc-214.amer.cisco.com>
In-Reply-To: <CAFOuuo4rpP0-ONn-SVoOzfU_+2Z_t8HaXd7dq7HJMvTwdEgGxA@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [trill] Should we make draft-mrw-trill-over-ip-01 a WG document?
Thread-Index: Ac0x+CouBBXNAN0uR6i8ek02Z35wrwABzP2A
References: <4FADB0E8.1090000@acm.org> <CAFOuuo4rpP0-ONn-SVoOzfU_+2Z_t8HaXd7dq7HJMvTwdEgGxA@mail.gmail.com>
From: "Tissa Senevirathne (tsenevir)" <tsenevir@cisco.com>
To: Radia Perlman <radiaperlman@gmail.com>, Erik Nordmark <nordmark@acm.org>
X-OriginalArrivalTime: 14 May 2012 19:06:15.0388 (UTC) FILETIME=[A2A961C0:01CD3204]
Cc: trill@ietf.org
Subject: Re: [trill] Should we make draft-mrw-trill-over-ip-01 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, 14 May 2012 19:06:19 -0000

Hi Radia


If we are discussing about TRILL over foo then this draft is not generic. 

If we are discussing about TRILL over IP then I begin to wonder why cannot we use existing pseudo-wire techniques.

If we can use existing VPLS or L2VPN techniques to achieve required functionality, why do we need yet another solution to save 2 MAC address and a VLAN on outer Ethernet header. 

If we are discussing about TRILL over foo then WG need to have consensus on overall strategy before moving individual solutions to WG status. People may argue we should have a lower bar to enter documents to WG status, but side effect of that is we are over crowding the document set, hence taking focus away from agreed priority items.  Additionally, one may even argue TRILL over any other transport protocol should be part of L2VPN.

Lastly, what is the rush to move this document to WG status ?




-----Original Message-----
From: trill-bounces@ietf.org [mailto:trill-bounces@ietf.org] On Behalf Of Radia Perlman
Sent: Monday, May 14, 2012 10:37 AM
To: Erik Nordmark
Cc: trill@ietf.org
Subject: Re: [trill] Should we make draft-mrw-trill-over-ip-01 a WG document?

I don't understand the controversy.  TRILL over IP is useful in several cases which are actually clearly explained in this document.
And in general, the document seems well thought out and well written.

So, I think it should be a WG document.

Radia

On Fri, May 11, 2012 at 5:38 PM, Erik Nordmark <nordmark@acm.org> wrote:
>
> The document is at
> https://datatracker.ietf.org/doc/draft-mrw-trill-over-ip/
>
> We've discussed this document in WG meetings and on the list in the past.
>
> Please send comments to the list.
>
>   Erik
> _______________________________________________
> trill mailing list
> trill@ietf.org
> https://www.ietf.org/mailman/listinfo/trill
_______________________________________________
trill mailing list
trill@ietf.org
https://www.ietf.org/mailman/listinfo/trill