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

Hi Donald,

Few questions inline.

Sam

Sent from my iPad

On May 14, 2012, at 12:26 PM, Donald Eastlake <d3e3e3@gmail.com> wrote:

> 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:
%sam- does this mean, the poll being undertaken is a moot point? If so, why to ask the WG for adoption?
> 
> 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.
%sam - are you saying, because it uses ip, it is superior technology than L2 technologies like PW? Ip has to use L2 anyway, so, the logic you are using doesn't make sense to me.
> 
>> 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.
That is not true. Vpls is a multi point technology and is widely used in many network types. Which aspects of the technology makes ip better here?
> 
> 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.
It is not entirely correct. The existing draft does encap trill frames with labels to be transferred over pw's. Whether it connects islands or something else is a matter of how you deploy the technology.

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