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

Donald Eastlake <d3e3e3@gmail.com> Mon, 14 May 2012 19:26 UTC

Return-Path: <d3e3e3@gmail.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 6577B21F887D for <trill@ietfa.amsl.com>; Mon, 14 May 2012 12:26:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.69
X-Spam-Level:
X-Spam-Status: No, score=-103.69 tagged_above=-999 required=5 tests=[AWL=-0.091, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 9qM0AaONACsC for <trill@ietfa.amsl.com>; Mon, 14 May 2012 12:26:50 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id CA0E121F8870 for <trill@ietf.org>; Mon, 14 May 2012 12:26:50 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so6722533pbc.31 for <trill@ietf.org>; Mon, 14 May 2012 12:26:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; bh=4rT+aOS+ogNpn6kjnp1bLAehf918rVrn3d+cWPY4f2M=; b=miAPgg3XzE+sHxkDbvD2YLuKSHRnhDEZI62Oj3kHnrKVd+80BkW9idUXHEI/MmQwMh S+tTeJUPXHJLAkozOAzCwpuXET2e7raeAk5U9qroUK1YJXvA2tqFrWvjkOGITBWv4WjA IL3uy8qPcxL/5Yz32aRU9wXx1JKHgafF/4ChNk14yVrhnnmqMGA74kjClQPDDh/kGvAY bSzo6P54Wz5LyIwWkp/Q7tJII5eAJ43XGmCwNgOgys1FtMAMILEe7rpkaj8yk0QOyB29 LD8/yr7xYO7MoHPAaOhqBk/PEJSUGklXsFa0TeLlK40Fz3rXaH78kKdGaQw5sEStJKed MzwA==
Received: by 10.50.51.226 with SMTP id n2mr3989501igo.3.1337023610440; Mon, 14 May 2012 12:26:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.59.201 with HTTP; Mon, 14 May 2012 12:26:30 -0700 (PDT)
In-Reply-To: <344037D7CFEFE84E97E9CC1F56C5F4A5011CB0E0@xmb-sjc-214.amer.cisco.com>
References: <4FADB0E8.1090000@acm.org> <CAFOuuo4rpP0-ONn-SVoOzfU_+2Z_t8HaXd7dq7HJMvTwdEgGxA@mail.gmail.com> <344037D7CFEFE84E97E9CC1F56C5F4A5011CB0E0@xmb-sjc-214.amer.cisco.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 14 May 2012 15:26:30 -0400
Message-ID: <CAF4+nEEGRi1tki9vVtnZcgzVuQrB2Zbz_TB96=XJ-=T=izbOKw@mail.gmail.com>
To: trill@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
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:26:51 -0000

None of these arguments matter as our Area Director says that we need
to re-Charter to make TRILL over IP a WG draft. However, I will
respond a bit below:

On Mon, May 14, 2012 at 3:06 PM, Tissa Senevirathne (tsenevir)
<tsenevir@cisco.com> wrote:
> 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.

You can but the result is inferior, adding more layers of fuzz between
TRILL and actual transport protocol.

> 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.

Maybe on a point-to-point link the main advantage is the savings you
mention. But on a multi-point technology like IP there are lots of
other factors in addition to saving a non-trivial number of bytes,
factors related to multi-destination traffic, security, etc.

The current L2VPN WG draft, to the extent it talks about
interconnecting TRILL islands, isn't TRILL over anything but, although
it connects the TRILL data planes, runs some new different more
loosely coupled control protocol between the islands.

> 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 ?

That's no different than asking why the obstructionism about a draft
that has been presented and discussed and in which previously raised
objections have been, as far as I can tell, resolved. Sitting on your
hands is not a way to get standards done.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

> -----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
> _______________________________________________
> trill mailing list
> trill@ietf.org
> https://www.ietf.org/mailman/listinfo/trill