From routing-discussion-bounces@ietf.org  Thu Jun 16 22:03:23 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04929
	for <routing-discussion-archive@ietf.org>; Thu, 16 Jun 2005 22:03:23 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dj6Zf-0006nu-Fx
	for routing-discussion-archive@ietf.org; Thu, 16 Jun 2005 22:27:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dj69t-0007Ks-Cg; Thu, 16 Jun 2005 22:00:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dj69r-0007Kk-QX; Thu, 16 Jun 2005 22:00:35 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04709;
	Thu, 16 Jun 2005 22:00:24 -0400 (EDT)
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dj6Wl-0006cY-Ul; Thu, 16 Jun 2005 22:24:16 -0400
Received: from [147.28.0.62] (helo=usmovnazinin.alcatel.com)
	by psg.com with esmtp (Exim 4.50 (FreeBSD))
	id 1Dj69j-000DZ8-Ag; Fri, 17 Jun 2005 02:00:27 +0000
Date: Thu, 16 Jun 2005 19:00:25 -0700
From: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <349058829.20050616190025@psg.com>
To: routing-discussion@ietf.org
In-Reply-To: <200506151852.OAA14446@ietf.org>
References: <200506151852.OAA14446@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.8 (/)
X-Scan-Signature: d16ce744298aacf98517bc7c108bd198
Content-Transfer-Encoding: 7bit
Cc: rtg-dir@ietf.org, rtg-chairs@ietf.org
Subject: Fwd: WG Review: Transparent Interconnection of Lots of Links (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Alex Zinin <zinin@psg.com>
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 6ba8aaf827dcb437101951262f69b3de
Content-Transfer-Encoding: 7bit

Since the second BOF on this topic was inconclusive regarding community
support, the IESG is reevaluating the community consensus on whether a WG
should be formed or not.

If you have input on this, positive or negative, please send it to
iesg@ietf.org.

-- 
Alex
http://www.psg.com/~zinin

This is a forwarded message
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce@ietf.org
Cc: rbridge@postel.org
Date: Wednesday, June 15, 2005, 11:52:27 AM
Subject: WG Review: Transparent Interconnection of Lots of Links (trill)

===8<==============Original message text===============
A new IETF working group has been proposed in the Internet Area. The IESG has 
not made any determination as yet. The following draft charter was submitted, 
and is provided for informational purposes only. Please send your comments to 
the IESG mailing list (iesg@ietf.org) by June 22nd.

+++

Transparent Interconnection of Lots of Links (trill) 
=====================================================

Current Status: Proposed Working Group

Chair(s):
TBD

Internet Area Director(s):
Mark Townsley <townsley@cisco.com>
Margaret Wasserman <margaret@thingmagic.com>

Internet Area Advisor:
Mark Townsley <townsley@cisco.com>

Technical Advisor:
Bill Fenner <fenner@research.att.com>

Secretary(ies):
TBD

Mailing Lists:
General Discussion: rbridge@postel.org
To Subscribe: http://www.postel.org/mailman/listinfo/rbridge
Archive: http://www.postel.org/pipermail/rbridge

Description of Working Group:

The TRILL WG will design a solution for shortest-path frame routing in
multi-hop IEEE 802.1 Ethernet networks with arbitrary topologies,
using the link-state routing protocol technology.

This work will initially be based on draft-perlman-rbridge-03.txt.

The design should have the following properties:

- Minimal or no configuration required
- Load-splitting among multiple paths
- Routing loop mitigation (possibly through a TTL field)
- Support of multiple points of attachment
- Support for broadcast and multicast
- No significant service delay after attachment
- No less secure than existing bridged solutions

Any changes introduced to the Ethernet service model should be
analyzed and clearly documented. To ensure compatibility with IEEE
VLANs and the Ethernet service model, the WG will request an IEEE
liaison relationship with IEEE 802.1.

It is not an explicit requirement that the solution should be able to
run on existing IP routers or IEEE 802 switches as a software upgrade.
However, the working group should take deployment considerations into
account, to ensure that the solution can interwork with bridges in a
flexible manner (e.g., to allow incremental deployment into LANs that
currently use 802.1D bridges).

The TRILL working will work with the L2VPN WG and IEEE 802.1 to
develop interworking between TRILL and 802.1D bridges at the edge, such
that a bridged sub-cloud could be attached to TRILL devices in more than
one place for redundancy.

The solution must not interfere with the end-to-end transparency of
the Internet architecture or with end-to-end congestion control and
QOS mechanisms.

The WG will work on the following items:

(1) Develop a problem statement and architecture document that
describes the high-level TRILL architecture, discusses the
scalability of that architecture, describe the threat model
and security impacts of the TRILL solution, and describes the
expected impacts (if any) of the TRILL solution on the Ethernet
service model.

(2) Define the requirements for a TRILL-capable routing protocol, and
select one or more existing routing protocols that could meet
those requirements.

(3) Work with the appropriate Routing area working group to extend an
existing routing protocol to meet the TRILL working group
requirements.

Note: The TRILL working group is not chartered to develop a new
routing protocol or to make substantial modifications to an
existing routing protocol. If, during the requirements definition
and selection phase, the TRILL working group discovers that no
existing routing protocol will meet their needs, we will need to
re-assess the TRILL WG charter to determine how/if this work
should proceed.

(4) Produce a (set of) TRILL specification(s) for standards track
publication that defines what information must be carried in an
encapsulation header for data packets, and determine how to map
that information to various link types (only IEEE 802 links
initially)

The TRILL working group is chartered to undertake all of the above
tasks and may begin work on more than one of these tasks in parallel.
However, the problem statement and architecture document should be
completed before the details of the base protocol are finalized, while
there is still time to consider changes to the architecture without
major impacts on established specifications.

Goals and Milestones:

Aug 05 Accept Problem statement and architecture document as a WG
work item
Aug 05 Accept base protocol specification as a WG document
Oct 05 Accept routing protocol requirements as a WG work item
Dec 05 Submit problem statement and architecture document to the IESG
for publication as an Informational RFC
Mar 06 Submit routing protocol requirements to the IESG for
publication as an Informational RFC
Mar 06 Choose routing protocol(s) that can meet the requirements.
Apr 06 Start work with routing area WG(s) to undertake TRILL extensions.
Sep 06 Base protocol specification submitted to the IESG for
publication as a Proposed Standard RFC
Dec 06 Re-charter or shut down the WG


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce

===8<===========End of original message text===========


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Mon Jun 20 09:58:35 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29641
	for <routing-discussion-archive@ietf.org>; Mon, 20 Jun 2005 09:58:35 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DkNB2-00021x-3G
	for routing-discussion-archive@ietf.org; Mon, 20 Jun 2005 10:23:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DkMiw-0003Us-7N; Mon, 20 Jun 2005 09:54:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DkMiu-0003Uh-97; Mon, 20 Jun 2005 09:54:00 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29168;
	Mon, 20 Jun 2005 09:53:50 -0400 (EDT)
Received: from dns.nexthop.com ([65.247.36.216] helo=aa-mx1.nexthop.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DkN6S-0001ug-Py; Mon, 20 Jun 2005 10:18:23 -0400
Received: from localhost (localhost [127.0.0.1])
	by aa-mx1.nexthop.com (Postfix) with ESMTP
	id A9B172D4B19; Mon, 20 Jun 2005 09:53:31 -0400 (EDT)
Received: from aa-mx1.nexthop.com ([127.0.0.1])
	by localhost (aa-mx1.nexthop.com [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id 49065-01-29; Mon, 20 Jun 2005 09:53:28 -0400 (EDT)
Received: from BOS-exch01.corp.nexthop.com (unknown [192.168.11.20])
	by aa-mx1.nexthop.com (Postfix) with ESMTP
	id A62912D48B9; Mon, 20 Jun 2005 09:53:27 -0400 (EDT)
Received: from aa-exchange1.corp.nexthop.com ([65.247.36.233]) by
	BOS-exch01.corp.nexthop.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Jun 2005 09:53:27 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 20 Jun 2005 09:53:26 -0400
Message-ID: <BE36D687C8CBFA4AB76F5CD3E3C0FB4E0402AF2A@aa-exchange1.corp.nexthop.com>
Thread-Topic: WG Review: Transparent Interconnection of Lots of Links (trill)
Thread-Index: AcVy4gNEhepqi1LwQv+Qa7PbM7WaPQCvUC+A
From: "Susan Hares" <shares@nexthop.com>
To: "Alex Zinin" <zinin@psg.com>, <routing-discussion@ietf.org>
X-OriginalArrivalTime: 20 Jun 2005 13:53:27.0352 (UTC)
	FILETIME=[6F105B80:01C5759F]
X-Virus-Scanned: by amavisd-new at nexthop.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d890c9ddd0b0a61e8c597ad30c1c2176
Content-Transfer-Encoding: quoted-printable
Cc: rtg-dir@ietf.org, rtg-chairs@ietf.org
Subject: RE: WG Review: Transparent Interconnection of Lots of Links (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 33cc095b503da4365ce57c727e553cf1
Content-Transfer-Encoding: quoted-printable

Why are we doing this?  Is it IP or is it Frames?
If it is Frames, why is it not 802.1 - etc?=20

Sue Hares

-----Original Message-----
From: Alex Zinin [mailto:zinin@psg.com]=20
Sent: Thursday, June 16, 2005 10:00 PM
To: routing-discussion@ietf.org
Cc: rtg-dir@ietf.org; rtg-chairs@ietf.org
Subject: Fwd: WG Review: Transparent Interconnection of Lots of Links
(trill)

Since the second BOF on this topic was inconclusive regarding community
support, the IESG is reevaluating the community consensus on whether a
WG
should be formed or not.

If you have input on this, positive or negative, please send it to
iesg@ietf.org.

--=20
Alex
http://www.psg.com/~zinin

This is a forwarded message
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce@ietf.org
Cc: rbridge@postel.org
Date: Wednesday, June 15, 2005, 11:52:27 AM
Subject: WG Review: Transparent Interconnection of Lots of Links (trill)

=3D=3D=3D8<=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3DOriginal message =
text=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
A new IETF working group has been proposed in the Internet Area. The
IESG has=20
not made any determination as yet. The following draft charter was
submitted,=20
and is provided for informational purposes only. Please send your
comments to=20
the IESG mailing list (iesg@ietf.org) by June 22nd.

+++

Transparent Interconnection of Lots of Links (trill)=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D

Current Status: Proposed Working Group

Chair(s):
TBD

Internet Area Director(s):
Mark Townsley <townsley@cisco.com>
Margaret Wasserman <margaret@thingmagic.com>

Internet Area Advisor:
Mark Townsley <townsley@cisco.com>

Technical Advisor:
Bill Fenner <fenner@research.att.com>

Secretary(ies):
TBD

Mailing Lists:
General Discussion: rbridge@postel.org
To Subscribe: http://www.postel.org/mailman/listinfo/rbridge
Archive: http://www.postel.org/pipermail/rbridge

Description of Working Group:

The TRILL WG will design a solution for shortest-path frame routing in
multi-hop IEEE 802.1 Ethernet networks with arbitrary topologies,
using the link-state routing protocol technology.

This work will initially be based on draft-perlman-rbridge-03.txt.

The design should have the following properties:

- Minimal or no configuration required
- Load-splitting among multiple paths
- Routing loop mitigation (possibly through a TTL field)
- Support of multiple points of attachment
- Support for broadcast and multicast
- No significant service delay after attachment
- No less secure than existing bridged solutions

Any changes introduced to the Ethernet service model should be
analyzed and clearly documented. To ensure compatibility with IEEE
VLANs and the Ethernet service model, the WG will request an IEEE
liaison relationship with IEEE 802.1.

It is not an explicit requirement that the solution should be able to
run on existing IP routers or IEEE 802 switches as a software upgrade.
However, the working group should take deployment considerations into
account, to ensure that the solution can interwork with bridges in a
flexible manner (e.g., to allow incremental deployment into LANs that
currently use 802.1D bridges).

The TRILL working will work with the L2VPN WG and IEEE 802.1 to
develop interworking between TRILL and 802.1D bridges at the edge, such
that a bridged sub-cloud could be attached to TRILL devices in more than
one place for redundancy.

The solution must not interfere with the end-to-end transparency of
the Internet architecture or with end-to-end congestion control and
QOS mechanisms.

The WG will work on the following items:

(1) Develop a problem statement and architecture document that
describes the high-level TRILL architecture, discusses the
scalability of that architecture, describe the threat model
and security impacts of the TRILL solution, and describes the
expected impacts (if any) of the TRILL solution on the Ethernet
service model.

(2) Define the requirements for a TRILL-capable routing protocol, and
select one or more existing routing protocols that could meet
those requirements.

(3) Work with the appropriate Routing area working group to extend an
existing routing protocol to meet the TRILL working group
requirements.

Note: The TRILL working group is not chartered to develop a new
routing protocol or to make substantial modifications to an
existing routing protocol. If, during the requirements definition
and selection phase, the TRILL working group discovers that no
existing routing protocol will meet their needs, we will need to
re-assess the TRILL WG charter to determine how/if this work
should proceed.

(4) Produce a (set of) TRILL specification(s) for standards track
publication that defines what information must be carried in an
encapsulation header for data packets, and determine how to map
that information to various link types (only IEEE 802 links
initially)

The TRILL working group is chartered to undertake all of the above
tasks and may begin work on more than one of these tasks in parallel.
However, the problem statement and architecture document should be
completed before the details of the base protocol are finalized, while
there is still time to consider changes to the architecture without
major impacts on established specifications.

Goals and Milestones:

Aug 05 Accept Problem statement and architecture document as a WG
work item
Aug 05 Accept base protocol specification as a WG document
Oct 05 Accept routing protocol requirements as a WG work item
Dec 05 Submit problem statement and architecture document to the IESG
for publication as an Informational RFC
Mar 06 Submit routing protocol requirements to the IESG for
publication as an Informational RFC
Mar 06 Choose routing protocol(s) that can meet the requirements.
Apr 06 Start work with routing area WG(s) to undertake TRILL extensions.
Sep 06 Base protocol specification submitted to the IESG for
publication as a Proposed Standard RFC
Dec 06 Re-charter or shut down the WG


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce

=3D=3D=3D8<=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3DEnd of original message =
text=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Mon Jun 20 13:57:03 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23706
	for <routing-discussion-archive@ietf.org>; Mon, 20 Jun 2005 13:57:03 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DkQtt-00006G-O8
	for routing-discussion-archive@ietf.org; Mon, 20 Jun 2005 14:21:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DkQTc-0000pj-Gd; Mon, 20 Jun 2005 13:54:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DkQTb-0000pO-2F; Mon, 20 Jun 2005 13:54:27 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23213;
	Mon, 20 Jun 2005 13:53:05 -0400 (EDT)
Received: from imo-d01.mx.aol.com ([205.188.157.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DkQpy-0008Pk-W9; Mon, 20 Jun 2005 14:17:40 -0400
Received: from ewgray2k@netscape.net
	by imo-d01.mx.aol.com (mail_out_v38_r1.7.) id b.13a.10403438 (22683);
	Mon, 20 Jun 2005 13:52:38 -0400 (EDT)
Received: from [192.168.7.131] (c-24-61-197-198.hsd1.nh.comcast.net
	[24.61.197.198]) by air-in04.mx.aol.com (v106.2) with ESMTP id
	MAILININ44-589b42b702642f; Mon, 20 Jun 2005 13:52:37 -0400
Message-ID: <42B70260.4010801@netscape.net>
Date: Mon, 20 Jun 2005 13:52:32 -0400
From: Eric W Gray <ewgray2k@netscape.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: shares@nexthop.com
References: <BE36D687C8CBFA4AB76F5CD3E3C0FB4E0402AF2A@aa-exchange1.corp.nexthop.com>
In-Reply-To: <BE36D687C8CBFA4AB76F5CD3E3C0FB4E0402AF2A@aa-exchange1.corp.nexthop.com>
X-AOL-IP: 24.61.197.198
X-Mailer: Unknown (No Version)
X-Spam-Score: 1.3 (+)
X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab
Cc: Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org, routing-discussion@ietf.org,
        rtg-chairs@ietf.org
Subject: Re: WG Review: Transparent Interconnection of Lots of Links (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ewgray@GraIyMage.com
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0875249805=="
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 03169bfe4792634a390035a01a6c6d2f


--===============0875249805==
Content-Type: multipart/alternative;
	boundary="------------070905060101000003010107"


--------------070905060101000003010107
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Sue,

    The trouble with obvious questions is that everybody assumes they've 
been  asked already.
Now this question has been asked at least once, for sure.  :-)

    From the charter attached in Alex's previous message, the purpose is 
to "route" Ethernet
Frames. Quote:

The TRILL WG will design a solution for shortest-path frame routing in
multi-hop IEEE 802.1 Ethernet networks with arbitrary topologies,
using the link-state routing protocol technology.

Since it is clear that at least some people are not satisfied with the 
802.1 approach (perhaps
because of the relative inefficiency associated with completely unused 
high capacity links), I
assume you mean to ask "why is it not IEEE" - rather than "why is it not 
802.1".

    I believe that is a very good question.  I know of no very good 
reason why the IEEE might
not specify how to use an OSPF-like routing protocol to fulfill the role 
previously handled by
Spanning Tree Protocol. Perhaps the only reason why it is being 
discussed here is that it might
be better - for implementers - if the protocol used was more than 
"OSPF-like."

--
Eric

shares@nexthop.com wrote:

>Why are we doing this?  Is it IP or is it Frames?
>If it is Frames, why is it not 802.1 - etc? 
>
>Sue Hares
>
>-----Original Message-----
>From: Alex Zinin [mailto:zinin@psg.com] 
>Sent: Thursday, June 16, 2005 10:00 PM
>To: routing-discussion@ietf.org
>Cc: rtg-dir@ietf.org; rtg-chairs@ietf.org
>Subject: Fwd: WG Review: Transparent Interconnection of Lots of Links
>(trill)
>
>Since the second BOF on this topic was inconclusive regarding community
>support, the IESG is reevaluating the community consensus on whether a
>WG
>should be formed or not.
>
>If you have input on this, positive or negative, please send it to
>iesg@ietf.org.
>
>  
>

--------------070905060101000003010107
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Sue,<br>
<br>
&nbsp;&nbsp;&nbsp; The trouble with obvious questions is that everybody assumes
they've been&nbsp; asked already.<br>
Now this question has been asked at least once, for sure.&nbsp; :-)<br>
<br>
&nbsp;&nbsp;&nbsp; From the charter attached in Alex's previous message, the purpose
is to "route" Ethernet<br>
Frames. Quote:<br>
<pre wrap=""><font color="#6666cc" face="Centaur" size="+1">The TRILL WG will design a solution for shortest-path frame routing in
multi-hop IEEE 802.1 Ethernet networks with arbitrary topologies,
using the link-state routing protocol technology.</font></pre>
Since it is clear that at least some people are not satisfied with the
802.1 approach (perhaps <br>
because of the relative inefficiency associated with completely unused
high capacity links), I<br>
assume you mean to ask "why is it not IEEE" - rather than "why is it
not 802.1".<br>
<br>
&nbsp;&nbsp;&nbsp; I believe that is a very good question.&nbsp; I know of no very good
reason why the IEEE might<br>
not specify how to use an OSPF-like routing protocol to fulfill the
role previously handled by<br>
Spanning Tree Protocol. Perhaps the only reason why it is being
discussed here is that it might<br>
be better - for implementers - if the protocol used was more than
"OSPF-like."<br>
<br>
--<br>
Eric<br>
<br>
<a class="moz-txt-link-abbreviated" href="mailto:shares@nexthop.com">shares@nexthop.com</a> wrote:
<blockquote  cite="midBE36D687C8CBFA4AB76F5CD3E3C0FB4E0402AF2A@aa-exchange1.corp.nexthop.com"  type="cite">
  <pre wrap="">Why are we doing this?  Is it IP or is it Frames?
If it is Frames, why is it not 802.1 - etc? 

Sue Hares

-----Original Message-----
From: Alex Zinin [<a class="moz-txt-link-freetext" href="mailto:zinin@psg.com">mailto:zinin@psg.com</a>] 
Sent: Thursday, June 16, 2005 10:00 PM
To: <a class="moz-txt-link-abbreviated" href="mailto:routing-discussion@ietf.org">routing-discussion@ietf.org</a>
Cc: <a class="moz-txt-link-abbreviated" href="mailto:rtg-dir@ietf.org">rtg-dir@ietf.org</a>; <a class="moz-txt-link-abbreviated" href="mailto:rtg-chairs@ietf.org">rtg-chairs@ietf.org</a>
Subject: Fwd: WG Review: Transparent Interconnection of Lots of Links
(trill)

Since the second BOF on this topic was inconclusive regarding community
support, the IESG is reevaluating the community consensus on whether a
WG
should be formed or not.

If you have input on this, positive or negative, please send it to
<a class="moz-txt-link-abbreviated" href="mailto:iesg@ietf.org">iesg@ietf.org</a>.

  </pre>
</blockquote>
</body>
</html>

--------------070905060101000003010107--


--===============0875249805==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion

--===============0875249805==--



From routing-discussion-bounces@ietf.org  Mon Jun 20 14:27:51 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26288
	for <routing-discussion-archive@ietf.org>; Mon, 20 Jun 2005 14:27:51 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DkRNi-0000vZ-2n
	for routing-discussion-archive@ietf.org; Mon, 20 Jun 2005 14:52:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DkQx2-0004z9-OA; Mon, 20 Jun 2005 14:24:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DkQx0-0004yx-09; Mon, 20 Jun 2005 14:24:50 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26076;
	Mon, 20 Jun 2005 14:24:41 -0400 (EDT)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DkRKd-0000pp-AN; Mon, 20 Jun 2005 14:49:16 -0400
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-2.cisco.com with ESMTP; 20 Jun 2005 11:24:24 -0700
Received: from cliff.cisco.com (cliff.cisco.com [171.69.11.141])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j5KIOLqi009875;
	Mon, 20 Jun 2005 11:24:21 -0700 (PDT)
Received: from [10.21.147.148] (sjc-vpn7-916.cisco.com [10.21.147.148]) by
	cliff.cisco.com (8.6.12/8.6.5) with ESMTP id LAA08965;
	Mon, 20 Jun 2005 11:20:40 -0700
Message-ID: <42B708F7.9030707@tony.li>
Date: Mon, 20 Jun 2005 11:20:39 -0700
From: Tony Li <tony.li@tony.li>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ewgray@GraIyMage.com
References: <BE36D687C8CBFA4AB76F5CD3E3C0FB4E0402AF2A@aa-exchange1.corp.nexthop.com>
	<42B70260.4010801@netscape.net>
In-Reply-To: <42B70260.4010801@netscape.net>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Content-Transfer-Encoding: 7bit
Cc: Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org, rtg-chairs@ietf.org,
        routing-discussion@ietf.org, shares@nexthop.com
Subject: Re: WG Review: Transparent Interconnection of Lots of Links (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Content-Transfer-Encoding: 7bit



In other instances, when proposals were IEEE'ish, we were directed to
take them to the IEEE.

Tony


Eric W Gray wrote:
> Sue,
> 
>     The trouble with obvious questions is that everybody assumes they've
> been  asked already.
> Now this question has been asked at least once, for sure.  :-)
> 
>     From the charter attached in Alex's previous message, the purpose is
> to "route" Ethernet
> Frames. Quote:
> 
> The TRILL WG will design a solution for shortest-path frame routing in
> multi-hop IEEE 802.1 Ethernet networks with arbitrary topologies,
> using the link-state routing protocol technology.
> 
> Since it is clear that at least some people are not satisfied with the
> 802.1 approach (perhaps
> because of the relative inefficiency associated with completely unused
> high capacity links), I
> assume you mean to ask "why is it not IEEE" - rather than "why is it not
> 802.1".
> 
>     I believe that is a very good question.  I know of no very good
> reason why the IEEE might
> not specify how to use an OSPF-like routing protocol to fulfill the role
> previously handled by
> Spanning Tree Protocol. Perhaps the only reason why it is being
> discussed here is that it might
> be better - for implementers - if the protocol used was more than
> "OSPF-like."
> 
> --
> Eric
> 
> shares@nexthop.com wrote:
> 
>>Why are we doing this?  Is it IP or is it Frames?
>>If it is Frames, why is it not 802.1 - etc? 
>>
>>Sue Hares
>>
>>-----Original Message-----
>>From: Alex Zinin [mailto:zinin@psg.com] 
>>Sent: Thursday, June 16, 2005 10:00 PM
>>To: routing-discussion@ietf.org
>>Cc: rtg-dir@ietf.org; rtg-chairs@ietf.org
>>Subject: Fwd: WG Review: Transparent Interconnection of Lots of Links
>>(trill)
>>
>>Since the second BOF on this topic was inconclusive regarding community
>>support, the IESG is reevaluating the community consensus on whether a
>>WG
>>should be formed or not.
>>
>>If you have input on this, positive or negative, please send it to
>>iesg@ietf.org.
>>
>>  
>>
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www1.ietf.org/mailman/listinfo/routing-discussion

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Mon Jun 20 14:46:55 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27391
	for <routing-discussion-archive@ietf.org>; Mon, 20 Jun 2005 14:46:55 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DkRgA-0001LP-Jq
	for routing-discussion-archive@ietf.org; Mon, 20 Jun 2005 15:11:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DkRHg-0007XE-9I; Mon, 20 Jun 2005 14:46:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DkRHe-0007WH-AU; Mon, 20 Jun 2005 14:46:10 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27302;
	Mon, 20 Jun 2005 14:45:19 -0400 (EDT)
Received: from imo-d02.mx.aol.com ([205.188.157.34])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DkRec-0001I3-3n; Mon, 20 Jun 2005 15:09:54 -0400
Received: from ewgray2k@netscape.net
	by imo-d02.mx.aol.com (mail_out_v38_r1.7.) id i.2.11890227 (22681);
	Mon, 20 Jun 2005 14:44:58 -0400 (EDT)
Received: from [192.168.7.131] (c-24-61-197-198.hsd1.nh.comcast.net
	[24.61.197.198]) by air-in04.mx.aol.com (v106.2) with ESMTP id
	MAILININ42-589942b70ea9306; Mon, 20 Jun 2005 14:44:58 -0400
Message-ID: <42B70EA6.5050803@netscape.net>
Date: Mon, 20 Jun 2005 14:44:54 -0400
From: Eric W Gray <ewgray2k@netscape.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Tony Li <tony.li@tony.li>
References: <BE36D687C8CBFA4AB76F5CD3E3C0FB4E0402AF2A@aa-exchange1.corp.nexthop.com>
	<42B70260.4010801@netscape.net> <42B708F7.9030707@tony.li>
In-Reply-To: <42B708F7.9030707@tony.li>
X-AOL-IP: 24.61.197.198
X-Mailer: Unknown (No Version)
X-Spam-Score: 0.6 (/)
X-Scan-Signature: d9238570526f12788af3d33c67f37625
Cc: Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org, rtg-chairs@ietf.org,
        routing-discussion@ietf.org, shares@nexthop.com
Subject: Re: WG Review: Transparent Interconnection of Lots of Links (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ewgray@GraIyMage.com
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1506526590=="
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.6 (/)
X-Scan-Signature: b84f8c8fba0e1389e5eb998b64078964


--===============1506526590==
Content-Type: multipart/alternative;
	boundary="------------050707060007090001020000"


--------------050707060007090001020000
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Tony,

    No disagreement from me.  Perhaps the next obvious question is - has 
anyone taken this to the
IEEE?

--
Eric

Tony Li wrote:

>In other instances, when proposals were IEEE'ish, we were directed to
>take them to the IEEE.
>
>Tony
>
>
>Eric W Gray wrote:
>  
>
>>Sue,
>>
>>    The trouble with obvious questions is that everybody assumes they've
>>been  asked already.
>>Now this question has been asked at least once, for sure.  :-)
>>
>>    From the charter attached in Alex's previous message, the purpose is
>>to "route" Ethernet
>>Frames. Quote:
>>
>>The TRILL WG will design a solution for shortest-path frame routing in
>>multi-hop IEEE 802.1 Ethernet networks with arbitrary topologies,
>>using the link-state routing protocol technology.
>>
>>Since it is clear that at least some people are not satisfied with the
>>802.1 approach (perhaps
>>because of the relative inefficiency associated with completely unused
>>high capacity links), I
>>assume you mean to ask "why is it not IEEE" - rather than "why is it not
>>802.1".
>>
>>    I believe that is a very good question.  I know of no very good
>>reason why the IEEE might
>>not specify how to use an OSPF-like routing protocol to fulfill the role
>>previously handled by
>>Spanning Tree Protocol. Perhaps the only reason why it is being
>>discussed here is that it might
>>be better - for implementers - if the protocol used was more than
>>"OSPF-like."
>>
>>--
>>Eric
>>
>>shares@nexthop.com wrote:
>>
>>    
>>
>>>Why are we doing this?  Is it IP or is it Frames?
>>>If it is Frames, why is it not 802.1 - etc? 
>>>
>>>Sue Hares
>>>
>>>-----Original Message-----
>>>From: Alex Zinin [mailto:zinin@psg.com] 
>>>Sent: Thursday, June 16, 2005 10:00 PM
>>>To: routing-discussion@ietf.org
>>>Cc: rtg-dir@ietf.org; rtg-chairs@ietf.org
>>>Subject: Fwd: WG Review: Transparent Interconnection of Lots of Links
>>>(trill)
>>>
>>>Since the second BOF on this topic was inconclusive regarding community
>>>support, the IESG is reevaluating the community consensus on whether a
>>>WG
>>>should be formed or not.
>>>
>>>If you have input on this, positive or negative, please send it to
>>>iesg@ietf.org.
>>>
>>> 
>>>
>>>      
>>>
>>------------------------------------------------------------------------
>>
>>_______________________________________________
>>routing-discussion mailing list
>>routing-discussion@ietf.org
>>https://www1.ietf.org/mailman/listinfo/routing-discussion
>>    
>>
>
>
>
>  
>

--------------050707060007090001020000
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Tony,<br>
<br>
&nbsp;&nbsp;&nbsp; No disagreement from me.&nbsp; Perhaps the next obvious question is -
has anyone taken this to the<br>
IEEE?<br>
<br>
--<br>
Eric<br>
<br>
Tony Li wrote:<br>
<blockquote cite="mid42B708F7.9030707@tony.li" type="cite">
  <pre wrap="">
In other instances, when proposals were IEEE'ish, we were directed to
take them to the IEEE.

Tony


Eric W Gray wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">Sue,

    The trouble with obvious questions is that everybody assumes they've
been  asked already.
Now this question has been asked at least once, for sure.  :-)

    From the charter attached in Alex's previous message, the purpose is
to "route" Ethernet
Frames. Quote:

The TRILL WG will design a solution for shortest-path frame routing in
multi-hop IEEE 802.1 Ethernet networks with arbitrary topologies,
using the link-state routing protocol technology.

Since it is clear that at least some people are not satisfied with the
802.1 approach (perhaps
because of the relative inefficiency associated with completely unused
high capacity links), I
assume you mean to ask "why is it not IEEE" - rather than "why is it not
802.1".

    I believe that is a very good question.  I know of no very good
reason why the IEEE might
not specify how to use an OSPF-like routing protocol to fulfill the role
previously handled by
Spanning Tree Protocol. Perhaps the only reason why it is being
discussed here is that it might
be better - for implementers - if the protocol used was more than
"OSPF-like."

--
Eric

<a class="moz-txt-link-abbreviated" href="mailto:shares@nexthop.com">shares@nexthop.com</a> wrote:

    </pre>
    <blockquote type="cite">
      <pre wrap="">Why are we doing this?  Is it IP or is it Frames?
If it is Frames, why is it not 802.1 - etc? 

Sue Hares

-----Original Message-----
From: Alex Zinin [<a class="moz-txt-link-freetext" href="mailto:zinin@psg.com">mailto:zinin@psg.com</a>] 
Sent: Thursday, June 16, 2005 10:00 PM
To: <a class="moz-txt-link-abbreviated" href="mailto:routing-discussion@ietf.org">routing-discussion@ietf.org</a>
Cc: <a class="moz-txt-link-abbreviated" href="mailto:rtg-dir@ietf.org">rtg-dir@ietf.org</a>; <a class="moz-txt-link-abbreviated" href="mailto:rtg-chairs@ietf.org">rtg-chairs@ietf.org</a>
Subject: Fwd: WG Review: Transparent Interconnection of Lots of Links
(trill)

Since the second BOF on this topic was inconclusive regarding community
support, the IESG is reevaluating the community consensus on whether a
WG
should be formed or not.

If you have input on this, positive or negative, please send it to
<a class="moz-txt-link-abbreviated" href="mailto:iesg@ietf.org">iesg@ietf.org</a>.

 

      </pre>
    </blockquote>
    <pre wrap="">------------------------------------------------------------------------

_______________________________________________
routing-discussion mailing list
<a class="moz-txt-link-abbreviated" href="mailto:routing-discussion@ietf.org">routing-discussion@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www1.ietf.org/mailman/listinfo/routing-discussion">https://www1.ietf.org/mailman/listinfo/routing-discussion</a>
    </pre>
  </blockquote>
  <pre wrap=""><!---->


  </pre>
</blockquote>
</body>
</html>

--------------050707060007090001020000--


--===============1506526590==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion

--===============1506526590==--



From routing-discussion-bounces@ietf.org  Mon Jun 20 15:20:36 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01006
	for <routing-discussion-archive@ietf.org>; Mon, 20 Jun 2005 15:20:36 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DkSCl-0002CK-I4
	for routing-discussion-archive@ietf.org; Mon, 20 Jun 2005 15:45:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DkRof-0002x7-SU; Mon, 20 Jun 2005 15:20:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DkRod-0002wz-62; Mon, 20 Jun 2005 15:20:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00970;
	Mon, 20 Jun 2005 15:20:06 -0400 (EDT)
Received: from dns.nexthop.com ([65.247.36.216] helo=aa-mx1.nexthop.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DkSCE-0002BH-Nk; Mon, 20 Jun 2005 15:44:42 -0400
Received: from localhost (localhost [127.0.0.1])
	by aa-mx1.nexthop.com (Postfix) with ESMTP
	id 92F472D4FA4; Mon, 20 Jun 2005 15:19:50 -0400 (EDT)
Received: from aa-mx1.nexthop.com ([127.0.0.1])
	by localhost (aa-mx1.nexthop.com [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id 10566-01-51; Mon, 20 Jun 2005 15:19:46 -0400 (EDT)
Received: from BOS-exch01.corp.nexthop.com (unknown [192.168.11.20])
	by aa-mx1.nexthop.com (Postfix) with ESMTP
	id A185D2D51E5; Mon, 20 Jun 2005 15:03:24 -0400 (EDT)
Received: from aa-exchange1.corp.nexthop.com ([65.247.36.233]) by
	BOS-exch01.corp.nexthop.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Jun 2005 15:03:24 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 20 Jun 2005 15:03:22 -0400
Message-ID: <BE36D687C8CBFA4AB76F5CD3E3C0FB4E0402AF93@aa-exchange1.corp.nexthop.com>
Thread-Topic: WG Review: Transparent Interconnection of Lots of Links (trill)
Thread-Index: AcV1xRPoqmGDYHGPRc23T5HhKX6b2AAAxFLQ
From: "Susan Hares" <shares@nexthop.com>
To: <ewgray@GraIyMage.com>
X-OriginalArrivalTime: 20 Jun 2005 19:03:24.0057 (UTC)
	FILETIME=[BB905890:01C575CA]
X-Virus-Scanned: by amavisd-new at nexthop.com
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 7a3b79fd9d7bf2ef1762376a62c51ec4
Cc: Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org, routing-discussion@ietf.org,
        rtg-chairs@ietf.org
Subject: RE: WG Review: Transparent Interconnection of Lots of Links (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1617320555=="
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 64592953d6410e1f725ee21266e2f396

This is a multi-part message in MIME format.

--===============1617320555==
content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C575CA.BAE07251"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C575CA.BAE07251
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Eric:=20

=20

So I need more explanation - because your statement does not match with
my experience.=20

=20

A multiple company alliance (Wi-Mesh alliance)  I'm working with
proposed a

hybrid link-state and hybrid On-demand/DV (ADOV hybrid) for IEEE 802.11s
for wireless Mesh.

=20

I guess I don't understand your last comment.  The hybrid protocols (one
link state, one on-demand/proactive=20

(a variant of ADOV)) are passing MAC addresses and dealing with Wireless
Mesh Points.=20

=20

802.1 inter-working is defined for these protocols that will map
link-state 802.11 to bridge functions (802.3 or=20

Multiple 802.11 networks).   This inter-working can connect to the
Layer-2 spanning tree that Layer 3 may run over.=20

=20

I don't find the contributors to 802.1 to lack the ability to suggest
novel solutions or=20

Link state solutions for networks supported by 802.11 or 802.1.     I've
proposed FRAME TRILL solutions to

IEEE for a sub-group.  So, what I see is that I must submit solutions to
both IEEE and IETF over the same work area.=20

=20

Am I confused?  How are we advancing the work of running code?=20

=20

Sue

=20

=20

=20

  _____ =20

From: Eric W Gray [mailto:ewgray2k@netscape.net]=20
Sent: Monday, June 20, 2005 1:53 PM
To: Susan Hares
Cc: Alex Zinin; routing-discussion@ietf.org; rtg-dir@ietf.org;
rtg-chairs@ietf.org
Subject: Re: WG Review: Transparent Interconnection of Lots of Links
(trill)

=20

Sue,

    The trouble with obvious questions is that everybody assumes they've
been  asked already.
Now this question has been asked at least once, for sure.  :-)

    From the charter attached in Alex's previous message, the purpose is
to "route" Ethernet
Frames. Quote:



The TRILL WG will design a solution for shortest-path frame routing in
multi-hop IEEE 802.1 Ethernet networks with arbitrary topologies,
using the link-state routing protocol technology.

Since it is clear that at least some people are not satisfied with the
802.1 approach (perhaps=20
because of the relative inefficiency associated with completely unused
high capacity links), I
assume you mean to ask "why is it not IEEE" - rather than "why is it not
802.1".

    I believe that is a very good question.  I know of no very good
reason why the IEEE might
not specify how to use an OSPF-like routing protocol to fulfill the role
previously handled by
Spanning Tree Protocol. Perhaps the only reason why it is being
discussed here is that it might
be better - for implementers - if the protocol used was more than
"OSPF-like."

--
Eric

shares@nexthop.com wrote:=20

Why are we doing this?  Is it IP or is it Frames?
If it is Frames, why is it not 802.1 - etc?=20
=20
Sue Hares
=20
-----Original Message-----
From: Alex Zinin [mailto:zinin@psg.com]=20
Sent: Thursday, June 16, 2005 10:00 PM
To: routing-discussion@ietf.org
Cc: rtg-dir@ietf.org; rtg-chairs@ietf.org
Subject: Fwd: WG Review: Transparent Interconnection of Lots of Links
(trill)
=20
Since the second BOF on this topic was inconclusive regarding community
support, the IESG is reevaluating the community consensus on whether a
WG
should be formed or not.
=20
If you have input on this, positive or negative, please send it to
iesg@ietf.org.
=20
 =20

------_=_NextPart_001_01C575CA.BAE07251
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"PersonName"
 downloadurl=3D"http://www.microsoft.com"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Centaur;
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";
	color:black;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
pre
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:2052144734;
	mso-list-type:hybrid;
	mso-list-template-ids:437044800 2029000758 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:802;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:.75in;
	mso-level-number-position:left;
	margin-left:.75in;
	text-indent:-.25in;
	font-family:Arial;
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-font-family:Arial;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.25in;
	mso-level-number-position:left;
	margin-left:1.25in;
	text-indent:-.25in;
	font-family:"Courier New";}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body bgcolor=3Dwhite lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Eric: <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>So I need more explanation &#8211; =
because
your statement does not match with my experience. =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>A multiple company alliance =
(</span></font><font
size=3D2><span style=3D'font-size:10.0pt'>Wi-Mesh alliance) =
</span></font><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>&nbsp;I&#8217;m working with proposed =
a<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>hybrid link-state and hybrid =
On-demand/DV (ADOV
hybrid) for IEEE 802.11s for wireless Mesh.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I guess I don&#8217;t understand =
your last
comment. &nbsp;The hybrid protocols (one link state, one =
on-demand/proactive <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>(a variant of ADOV)) are passing =
MAC
addresses and dealing with Wireless Mesh Points. =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>802.1 inter-working is defined for =
these
protocols that will map link-state 802.11 to bridge functions (802.3 or =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Multiple 802.11 networks).&nbsp; =
&nbsp;This
inter-working can connect to the Layer-2 spanning tree that Layer 3 may =
run over.
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I don&#8217;t find the contributors =
to
802.1 to lack the ability to suggest novel solutions or =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Link state solutions for networks =
supported
by 802.11 or 802.1. &nbsp;&nbsp;&nbsp;&nbsp;I&#8217;ve proposed FRAME =
TRILL
solutions to<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>IEEE for a sub-group. &nbsp;So, =
what I see
is that I must submit solutions to both IEEE and IETF over the same work =
area. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Am I confused? &nbsp;How are we =
advancing
the work of running code? <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Sue<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:windowtext'>

<hr size=3D3 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 color=3Dblack face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;color:windowtext;font-weight=
:bold'>From:</span></font></b><font
size=3D2 color=3Dblack face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;
color:windowtext'> Eric W Gray [mailto:ewgray2k@netscape.net] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Monday, June 20, =
2005 1:53
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Susan Hares<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> <st1:PersonName =
w:st=3D"on">Alex
 Zinin</st1:PersonName>; routing-discussion@ietf.org; rtg-dir@ietf.org;
rtg-chairs@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: WG Review:
Transparent Interconnection of Lots of Links (trill)</span></font><font
color=3Dblack><span =
style=3D'color:windowtext'><o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt'>Sue,<br>
<br>
&nbsp;&nbsp;&nbsp; The trouble with obvious questions is that everybody =
assumes
they've been&nbsp; asked already.<br>
Now this question has been asked at least once, for sure.&nbsp; :-)<br>
<br>
&nbsp;&nbsp;&nbsp; From the charter attached in Alex's previous message, =
the
purpose is to &quot;route&quot; Ethernet<br>
Frames. Quote:<br>
<br>
<o:p></o:p></span></font></p>

<pre><font size=3D4 color=3D"#6666cc" face=3DCentaur><span =
style=3D'font-size:13.5pt;
font-family:Centaur;color:#6666CC'>The TRILL WG will design a solution =
for shortest-path frame routing =
in<o:p></o:p></span></font></pre><pre><font
size=3D4 color=3D"#6666cc" face=3DCentaur><span =
style=3D'font-size:13.5pt;font-family:
Centaur;color:#6666CC'>multi-hop IEEE 802.1 Ethernet networks with =
arbitrary topologies,<o:p></o:p></span></font></pre><pre><font
size=3D4 color=3D"#6666cc" face=3DCentaur><span =
style=3D'font-size:13.5pt;font-family:
Centaur;color:#6666CC'>using the link-state routing protocol =
technology.</span></font><o:p></o:p></pre>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt'>Since it is clear that at least some people =
are not
satisfied with the 802.1 approach (perhaps <br>
because of the relative inefficiency associated with completely unused =
high
capacity links), I<br>
assume you mean to ask &quot;why is it not IEEE&quot; - rather than =
&quot;why
is it not 802.1&quot;.<br>
<br>
&nbsp;&nbsp;&nbsp; I believe that is a very good question.&nbsp; I know =
of no
very good reason why the IEEE might<br>
not specify how to use an OSPF-like routing protocol to fulfill the role
previously handled by<br>
Spanning Tree Protocol. Perhaps the only reason why it is being =
discussed here
is that it might<br>
be better - for implementers - if the protocol used was more than
&quot;OSPF-like.&quot;<br>
<br>
--<br>
Eric<br>
<br>
<a href=3D"mailto:shares@nexthop.com">shares@nexthop.com</a> wrote: =
<o:p></o:p></span></font></p>

<pre wrap=3D""><font size=3D2 color=3Dblack face=3D"Courier New"><span
style=3D'font-size:10.0pt'>Why are we doing this?&nbsp; Is it IP or is =
it Frames?<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>If it is Frames, why is it not 802.1 - etc? =
<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Sue =
Hares<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>-----Original =
Message-----<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>From: <st1:PersonName
w:st=3D"on">Alex Zinin</st1:PersonName> [<a =
href=3D"mailto:zinin@psg.com">mailto:zinin@psg.com</a>] =
<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Sent: Thursday, June 16, 2005 10:00 =
PM<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>To: <a
href=3D"mailto:routing-discussion@ietf.org">routing-discussion@ietf.org</=
a><o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Cc: <a
href=3D"mailto:rtg-dir@ietf.org">rtg-dir@ietf.org</a>; <a
href=3D"mailto:rtg-chairs@ietf.org">rtg-chairs@ietf.org</a><o:p></o:p></s=
pan></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Subject: Fwd: WG Review: Transparent =
Interconnection of Lots of =
Links<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>(trill)<o:p></o:p></span></font></pre><pre><fo=
nt
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Since the second BOF on this topic was =
inconclusive regarding =
community<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>support, the IESG is reevaluating the =
community consensus on whether =
a<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>WG<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>should be formed or =
not.<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>If you have input on this, positive or =
negative, please send it to<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><a
href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a>.<o:p></o:p></span></font>=
</pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp; <o:p></o:p></span></font></pre></div>

</body>

</html>

------_=_NextPart_001_01C575CA.BAE07251--


--===============1617320555==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion

--===============1617320555==--



From routing-discussion-bounces@ietf.org  Mon Jun 20 15:29:05 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01531
	for <routing-discussion-archive@ietf.org>; Mon, 20 Jun 2005 15:29:04 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DkSKu-0002OX-4R
	for routing-discussion-archive@ietf.org; Mon, 20 Jun 2005 15:53:40 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DkRvp-00041a-Ap; Mon, 20 Jun 2005 15:27:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DkRvn-00041Q-Or; Mon, 20 Jun 2005 15:27:40 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01452;
	Mon, 20 Jun 2005 15:27:31 -0400 (EDT)
Received: from dns.nexthop.com ([65.247.36.216] helo=aa-mx1.nexthop.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DkSJQ-0002MK-Vp; Mon, 20 Jun 2005 15:52:07 -0400
Received: from localhost (localhost [127.0.0.1])
	by aa-mx1.nexthop.com (Postfix) with ESMTP
	id A70822D5282; Mon, 20 Jun 2005 15:27:16 -0400 (EDT)
Received: from aa-mx1.nexthop.com ([127.0.0.1])
	by localhost (aa-mx1.nexthop.com [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id 11813-01-66; Mon, 20 Jun 2005 15:27:11 -0400 (EDT)
Received: from BOS-exch01.corp.nexthop.com (unknown [192.168.11.20])
	by aa-mx1.nexthop.com (Postfix) with ESMTP
	id 39E572D518C; Mon, 20 Jun 2005 15:11:18 -0400 (EDT)
Received: from aa-exchange1.corp.nexthop.com ([65.247.36.233]) by
	BOS-exch01.corp.nexthop.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Jun 2005 15:11:17 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 20 Jun 2005 15:11:15 -0400
Message-ID: <BE36D687C8CBFA4AB76F5CD3E3C0FB4E0402AF97@aa-exchange1.corp.nexthop.com>
Thread-Topic: WG Review: Transparent Interconnection of Lots of Links (trill)
Thread-Index: AcV1y1yVjrxDd/4sTluE2xaehbTgNQAADfgQ
From: "Susan Hares" <shares@nexthop.com>
To: <ewgray@GraIyMage.com>, "Tony Li" <tony.li@tony.li>
X-OriginalArrivalTime: 20 Jun 2005 19:11:17.0686 (UTC)
	FILETIME=[D5DE6560:01C575CB]
X-Virus-Scanned: by amavisd-new at nexthop.com
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 1ed37b243475b9c4ffb6a3f90050819d
Cc: Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org, routing-discussion@ietf.org,
        rtg-chairs@ietf.org
Subject: RE: WG Review: Transparent Interconnection of Lots of Links (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1225869636=="
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: fc231bf912a450f71747fa7a4e3e2f5a

This is a multi-part message in MIME format.

--===============1225869636==
content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C575CB.D4AFFC72"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C575CB.D4AFFC72
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Eric and Tony:

=20

See my comments about Wireless Mesh proposal an Wi-Mesh alliance I'm a
part of submitted 6/15/05 to the 802.11s.

Radia or others may know more about 802.1 since they have more history
with IEEE.

=20

Sue

=20

=20

  _____ =20

From: Eric W Gray [mailto:ewgray2k@netscape.net]=20
Sent: Monday, June 20, 2005 2:45 PM
To: Tony Li
Cc: Susan Hares; Alex Zinin; rtg-dir@ietf.org;
routing-discussion@ietf.org; rtg-chairs@ietf.org
Subject: Re: WG Review: Transparent Interconnection of Lots of Links
(trill)

=20

Tony,

    No disagreement from me.  Perhaps the next obvious question is - has
anyone taken this to the
IEEE?

--
Eric

Tony Li wrote:



=20
In other instances, when proposals were IEEE'ish, we were directed to
take them to the IEEE.
=20
Tony
=20
=20
Eric W Gray wrote:
 =20

	Sue,
	=20
	    The trouble with obvious questions is that everybody assumes
they've
	been  asked already.
	Now this question has been asked at least once, for sure.  :-)
	=20
	    From the charter attached in Alex's previous message, the
purpose is
	to "route" Ethernet
	Frames. Quote:
	=20
	The TRILL WG will design a solution for shortest-path frame
routing in
	multi-hop IEEE 802.1 Ethernet networks with arbitrary
topologies,
	using the link-state routing protocol technology.
	=20
	Since it is clear that at least some people are not satisfied
with the
	802.1 approach (perhaps
	because of the relative inefficiency associated with completely
unused
	high capacity links), I
	assume you mean to ask "why is it not IEEE" - rather than "why
is it not
	802.1".
	=20
	    I believe that is a very good question.  I know of no very
good
	reason why the IEEE might
	not specify how to use an OSPF-like routing protocol to fulfill
the role
	previously handled by
	Spanning Tree Protocol. Perhaps the only reason why it is being
	discussed here is that it might
	be better - for implementers - if the protocol used was more
than
	"OSPF-like."
	=20
	--
	Eric
	=20
	shares@nexthop.com wrote:
	=20
	   =20

		Why are we doing this?  Is it IP or is it Frames?
		If it is Frames, why is it not 802.1 - etc?=20
		=20
		Sue Hares
		=20
		-----Original Message-----
		From: Alex Zinin [mailto:zinin@psg.com]=20
		Sent: Thursday, June 16, 2005 10:00 PM
		To: routing-discussion@ietf.org
		Cc: rtg-dir@ietf.org; rtg-chairs@ietf.org
		Subject: Fwd: WG Review: Transparent Interconnection of
Lots of Links
		(trill)
		=20
		Since the second BOF on this topic was inconclusive
regarding community
		support, the IESG is reevaluating the community
consensus on whether a
		WG
		should be formed or not.
		=20
		If you have input on this, positive or negative, please
send it to
		iesg@ietf.org.
		=20
		=20
		=20
		     =20

=09
------------------------------------------------------------------------
	=20
	_______________________________________________
	routing-discussion mailing list
	routing-discussion@ietf.org
	https://www1.ietf.org/mailman/listinfo/routing-discussion
	   =20

=20
=20
=20
 =20

------_=_NextPart_001_01C575CB.D4AFFC72
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"PersonName"
 downloadurl=3D"http://www.microsoft.com"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";
	color:black;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
pre
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body bgcolor=3Dwhite lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Eric and =
Tony:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>See my comments about Wireless Mesh
proposal an Wi-Mesh alliance I&#8217;m a part of submitted 6/15/05 to =
the
802.11s.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Radia or others may know more about =
802.1
since they have more history with IEEE.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Sue<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:windowtext'>

<hr size=3D3 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 color=3Dblack face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;color:windowtext;font-weight=
:bold'>From:</span></font></b><font
size=3D2 color=3Dblack face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;
color:windowtext'> Eric W Gray [mailto:ewgray2k@netscape.net] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Monday, June 20, =
2005 2:45
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Tony Li<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> Susan Hares; =
<st1:PersonName
w:st=3D"on">Alex Zinin</st1:PersonName>; rtg-dir@ietf.org;
routing-discussion@ietf.org; rtg-chairs@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: WG Review:
Transparent Interconnection of Lots of Links (trill)</span></font><font
color=3Dblack><span =
style=3D'color:windowtext'><o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt'>Tony,<br>
<br>
&nbsp;&nbsp;&nbsp; No disagreement from me.&nbsp; Perhaps the next =
obvious
question is - has anyone taken this to the<br>
IEEE?<br>
<br>
--<br>
Eric<br>
<br>
Tony Li wrote:<br>
<br>
<o:p></o:p></span></font></p>

<pre wrap=3D""><font size=3D2 color=3Dblack face=3D"Courier New"><span
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>In other instances, when proposals were =
IEEE'ish, we were directed to<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>take them to the =
IEEE.<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Tony<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Eric W Gray =
wrote:<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp; <o:p></o:p></span></font></pre>

<blockquote style=3D'margin-top:5.0pt;margin-bottom:5.0pt' =
type=3Dcite><pre wrap=3D""><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Sue,<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp; The trouble with obvious =
questions is that everybody assumes =
they've<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>been&nbsp; asked =
already.<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Now this question has been asked at least =
once, for sure.&nbsp; :-)<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp; From the charter attached =
in Alex's previous message, the purpose =
is<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>to &quot;route&quot; =
Ethernet<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Frames. =
Quote:<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>The TRILL WG will design a solution for =
shortest-path frame routing in<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>multi-hop IEEE 802.1 Ethernet networks with =
arbitrary topologies,<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>using the link-state routing protocol =
technology.<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Since it is clear that at least some people =
are not satisfied with the<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>802.1 approach =
(perhaps<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>because of the relative inefficiency =
associated with completely =
unused<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>high capacity links), =
I<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>assume you mean to ask &quot;why is it not =
IEEE&quot; - rather than &quot;why is it =
not<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>802.1&quot;.<o:p></o:p></span></font></pre><pr=
e><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp; I believe that is a very =
good question.&nbsp; I know of no very =
good<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>reason why the IEEE =
might<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>not specify how to use an OSPF-like routing =
protocol to fulfill the role<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>previously handled =
by<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Spanning Tree Protocol. Perhaps the only =
reason why it is being<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>discussed here is that it =
might<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>be better - for implementers - if the =
protocol used was more than<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&quot;OSPF-like.&quot;<o:p></o:p></span></font=
></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>--<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Eric<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><a
href=3D"mailto:shares@nexthop.com">shares@nexthop.com</a> =
wrote:<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></pre>

<blockquote style=3D'margin-top:5.0pt;margin-bottom:5.0pt' =
type=3Dcite><pre wrap=3D""><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Why are we doing this?&nbsp; Is it IP or is =
it Frames?<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>If it is Frames, why is it not 802.1 - etc? =
<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Sue =
Hares<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>-----Original =
Message-----<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>From: <st1:PersonName
w:st=3D"on">Alex Zinin</st1:PersonName> [<a =
href=3D"mailto:zinin@psg.com">mailto:zinin@psg.com</a>] =
<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Sent: Thursday, June 16, 2005 10:00 =
PM<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>To: <a
href=3D"mailto:routing-discussion@ietf.org">routing-discussion@ietf.org</=
a><o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Cc: <a
href=3D"mailto:rtg-dir@ietf.org">rtg-dir@ietf.org</a>; <a
href=3D"mailto:rtg-chairs@ietf.org">rtg-chairs@ietf.org</a><o:p></o:p></s=
pan></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Subject: Fwd: WG Review: Transparent =
Interconnection of Lots of =
Links<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>(trill)<o:p></o:p></span></font></pre><pre><fo=
nt
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Since the second BOF on this topic was =
inconclusive regarding =
community<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>support, the IESG is reevaluating the =
community consensus on whether =
a<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>WG<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>should be formed or =
not.<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>If you have input on this, positive or =
negative, please send it to<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><a
href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a>.<o:p></o:p></span></font>=
</pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'> <o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></pre></blockquote>

<pre wrap=3D""><font size=3D2 color=3Dblack face=3D"Courier New"><span
style=3D'font-size:10.0pt'>----------------------------------------------=
--------------------------<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>______________________________________________=
_<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>routing-discussion mailing =
list<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><a
href=3D"mailto:routing-discussion@ietf.org">routing-discussion@ietf.org</=
a><o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><a
href=3D"https://www1.ietf.org/mailman/listinfo/routing-discussion">https:=
//www1.ietf.org/mailman/listinfo/routing-discussion</a><o:p></o:p></span>=
</font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></pre></blockquote>

<pre wrap=3D""><font size=3D2 color=3Dblack face=3D"Courier New"><span
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&nbsp; <o:p></o:p></span></font></pre></div>

</body>

</html>

------_=_NextPart_001_01C575CB.D4AFFC72--


--===============1225869636==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion

--===============1225869636==--



From routing-discussion-bounces@ietf.org  Mon Jun 20 16:05:29 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05894
	for <routing-discussion-archive@ietf.org>; Mon, 20 Jun 2005 16:05:29 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DkSuD-0003za-Ls
	for routing-discussion-archive@ietf.org; Mon, 20 Jun 2005 16:30:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DkSW2-0001mG-79; Mon, 20 Jun 2005 16:05:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DkSW0-0001ls-8v; Mon, 20 Jun 2005 16:05:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05778;
	Mon, 20 Jun 2005 16:04:56 -0400 (EDT)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DkStg-0003wr-RS; Mon, 20 Jun 2005 16:29:33 -0400
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-1.cisco.com with ESMTP; 20 Jun 2005 13:04:45 -0700
X-IronPort-AV: i="3.93,215,1115017200"; 
	d="scan'208"; a="644692080:sNHT31537060"
Received: from cliff.cisco.com (cliff.cisco.com [171.69.11.141])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j5KK4clO024523;
	Mon, 20 Jun 2005 13:04:39 -0700 (PDT)
Received: from [10.21.147.148] (sjc-vpn7-916.cisco.com [10.21.147.148]) by
	cliff.cisco.com (8.6.12/8.6.5) with ESMTP id NAA00041;
	Mon, 20 Jun 2005 13:01:01 -0700
Message-ID: <42B7207C.6080804@tony.li>
Date: Mon, 20 Jun 2005 13:01:00 -0700
From: Tony Li <tony.li@tony.li>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Susan Hares <shares@nexthop.com>
References: <BE36D687C8CBFA4AB76F5CD3E3C0FB4E0402AF97@aa-exchange1.corp.nexthop.com>
In-Reply-To: <BE36D687C8CBFA4AB76F5CD3E3C0FB4E0402AF97@aa-exchange1.corp.nexthop.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=windows-1252
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bacfc6c7290e34d410f9bc22b825ce96
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id QAA05778
Cc: Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org, ewgray@GraIyMage.com,
        routing-discussion@ietf.org, rtg-chairs@ietf.org
Subject: Re: WG Review: Transparent Interconnection of Lots of Links (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b84f8c8fba0e1389e5eb998b64078964
Content-Transfer-Encoding: quoted-printable


Sue,

Please allow me to be a bit more direct...

What part of this should be in the IETF?  The IESG has made it quite
clear that they do not want a turf battle with the IEEE.

There seems like a clear separation of layers here and this is still L2
work.  As such, it would seem consistent for this should go over to
IEEE, even if it is  borrowing heavily from IETF technology.

Tony


Susan Hares wrote:
> Eric and Tony:
>=20
> =20
>=20
> See my comments about Wireless Mesh proposal an Wi-Mesh alliance I=92m =
a
> part of submitted 6/15/05 to the 802.11s.
>=20
> Radia or others may know more about 802.1 since they have more history
> with IEEE.
>=20
> =20
>=20
> Sue
>=20
> =20
>=20
> =20
>=20
> -----------------------------------------------------------------------=
-
>=20
> *From:* Eric W Gray [mailto:ewgray2k@netscape.net]
> *Sent:* Monday, June 20, 2005 2:45 PM
> *To:* Tony Li
> *Cc:* Susan Hares; Alex Zinin; rtg-dir@ietf.org;
> routing-discussion@ietf.org; rtg-chairs@ietf.org
> *Subject:* Re: WG Review: Transparent Interconnection of Lots of Links
> (trill)
>=20
> =20
>=20
> Tony,
>=20
>     No disagreement from me.  Perhaps the next obvious question is - ha=
s
> anyone taken this to the
> IEEE?
>=20
> --
> Eric
>=20
> Tony Li wrote:
>=20
> =20
>=20
> In other instances, when proposals were IEEE'ish, we were directed to
>=20
> take them to the IEEE.
>=20
> =20
>=20
> Tony
>=20
> =20
>=20
> =20
>=20
> Eric W Gray wrote:
>=20
>  =20
>=20
>>Sue,
>>
>>=20
>>
>>    The trouble with obvious questions is that everybody assumes they'v=
e
>>
>>been  asked already.
>>
>>Now this question has been asked at least once, for sure.  :-)
>>
>>=20
>>
>>    From the charter attached in Alex's previous message, the purpose i=
s
>>
>>to "route" Ethernet
>>
>>Frames. Quote:
>>
>>=20
>>
>>The TRILL WG will design a solution for shortest-path frame routing in
>>
>>multi-hop IEEE 802.1 Ethernet networks with arbitrary topologies,
>>
>>using the link-state routing protocol technology.
>>
>>=20
>>
>>Since it is clear that at least some people are not satisfied with the
>>
>>802.1 approach (perhaps
>>
>>because of the relative inefficiency associated with completely unused
>>
>>high capacity links), I
>>
>>assume you mean to ask "why is it not IEEE" - rather than "why is it no=
t
>>
>>802.1".
>>
>>=20
>>
>>    I believe that is a very good question.  I know of no very good
>>
>>reason why the IEEE might
>>
>>not specify how to use an OSPF-like routing protocol to fulfill the rol=
e
>>
>>previously handled by
>>
>>Spanning Tree Protocol. Perhaps the only reason why it is being
>>
>>discussed here is that it might
>>
>>be better - for implementers - if the protocol used was more than
>>
>>"OSPF-like."
>>
>>=20
>>
>>--
>>
>>Eric
>>
>>=20
>>
>>shares@nexthop.com <mailto:shares@nexthop.com> wrote:
>>
>>=20
>>
>>   =20
>>
>>>Why are we doing this?  Is it IP or is it Frames?
>>>
>>>If it is Frames, why is it not 802.1 - etc?=20
>>>
>>>=20
>>>
>>>Sue Hares
>>>
>>>=20
>>>
>>>-----Original Message-----
>>>
>>>From: Alex Zinin [mailto:zinin@psg.com]=20
>>>
>>>Sent: Thursday, June 16, 2005 10:00 PM
>>>
>>>To: routing-discussion@ietf.org <mailto:routing-discussion@ietf.org>
>>>
>>>Cc: rtg-dir@ietf.org <mailto:rtg-dir@ietf.org>; rtg-chairs@ietf.org <m=
ailto:rtg-chairs@ietf.org>
>>>
>>>Subject: Fwd: WG Review: Transparent Interconnection of Lots of Links
>>>
>>>(trill)
>>>
>>>=20
>>>
>>>Since the second BOF on this topic was inconclusive regarding communit=
y
>>>
>>>support, the IESG is reevaluating the community consensus on whether a
>>>
>>>WG
>>>
>>>should be formed or not.
>>>
>>>=20
>>>
>>>If you have input on this, positive or negative, please send it to
>>>
>>>iesg@ietf.org <mailto:iesg@ietf.org>.
>>>
>>>=20
>>>
>>>=20
>>>
>>>=20
>>>
>>>     =20
>>
>>-----------------------------------------------------------------------=
-
>>
>>=20
>>
>>_______________________________________________
>>
>>routing-discussion mailing list
>>
>>routing-discussion@ietf.org <mailto:routing-discussion@ietf.org>
>>
>>https://www1.ietf.org/mailman/listinfo/routing-discussion
>>
>>   =20
>=20
> =20
>=20
> =20
>=20
> =20
>=20
>  =20
>=20

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Mon Jun 20 16:33:31 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08233
	for <routing-discussion-archive@ietf.org>; Mon, 20 Jun 2005 16:33:31 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DkTLL-0004mw-Tx
	for routing-discussion-archive@ietf.org; Mon, 20 Jun 2005 16:58:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DkSvN-00074E-Kt; Mon, 20 Jun 2005 16:31:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DkSvM-00073b-43; Mon, 20 Jun 2005 16:31:16 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07819;
	Mon, 20 Jun 2005 16:28:57 -0400 (EDT)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DkTGv-0004gW-W3; Mon, 20 Jun 2005 16:53:34 -0400
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-2.cisco.com with ESMTP; 20 Jun 2005 13:28:48 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j5KKRoGU004655;
	Mon, 20 Jun 2005 13:28:45 -0700 (PDT)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Mon, 20 Jun 2005 16:28:28 -0400
Received: from cisco.com ([10.86.240.14]) by xfe-rtp-202.amer.cisco.com with
	Microsoft SMTPSVC(6.0.3790.211); Mon, 20 Jun 2005 16:28:28 -0400
Date: Mon, 20 Jun 2005 16:27:57 -0400
From: Scott W Brim <sbrim@cisco.com>
To: Tony Li <tony.li@tony.li>
Message-ID: <20050620202756.GA1888@sbrim-wxp01>
Mail-Followup-To: Scott W Brim <sbrim@cisco.com>, Tony Li <tony.li@tony.li>,
	Susan Hares <shares@nexthop.com>, Alex Zinin <zinin@psg.com>,
	rtg-dir@ietf.org, ewgray@GraIyMage.com, routing-discussion@ietf.org,
	rtg-chairs@ietf.org
References: <BE36D687C8CBFA4AB76F5CD3E3C0FB4E0402AF97@aa-exchange1.corp.nexthop.com>
	<42B7207C.6080804@tony.li>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <42B7207C.6080804@tony.li>
User-Agent: Mutt/1.4.2.1i
X-OriginalArrivalTime: 20 Jun 2005 20:28:28.0391 (UTC)
	FILETIME=[9DFBE770:01C575D6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Cc: Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org, ewgray@GraIyMage.com,
        routing-discussion@ietf.org, rtg-chairs@ietf.org,
        Susan Hares <shares@nexthop.com>
Subject: Re: WG Review: Transparent Interconnection of Lots of Links (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2

On Mon, Jun 20, 2005 01:01:00PM -0700, Tony Li allegedly wrote:
> There seems like a clear separation of layers here and this is still L2
> work.  As such, it would seem consistent for this should go over to
> IEEE, even if it is  borrowing heavily from IETF technology.

Yes.  

In fact that borrowing could be a good thing, and doesn't influence
who holds responsibility for the work area.  

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Mon Jun 20 17:45:52 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12940
	for <routing-discussion-archive@ietf.org>; Mon, 20 Jun 2005 17:45:52 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DkUTO-0006bp-L8
	for routing-discussion-archive@ietf.org; Mon, 20 Jun 2005 18:10:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DkU32-0001bE-8k; Mon, 20 Jun 2005 17:43:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DkU30-0001b5-G2
	for routing-discussion@megatron.ietf.org;
	Mon, 20 Jun 2005 17:43:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12846
	for <routing-discussion@ietf.org>; Mon, 20 Jun 2005 17:43:12 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DkUQm-0006Xd-Nk
	for routing-discussion@ietf.org; Mon, 20 Jun 2005 18:07:50 -0400
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131])
	by motgate8.mot.com (Motorola/Motgate7) with ESMTP id j5KLpaW9010859
	for <routing-discussion@ietf.org>; Mon, 20 Jun 2005 14:51:36 -0700 (MST)
Received: from ma19exm01.e6.bcs.mot.com (ma19exm01.e6.bcs.mot.com [10.14.33.5])
	by il06exr01.mot.com (8.13.1/8.13.0) with ESMTP id j5KLm3in006077
	for <routing-discussion@ietf.org>; Mon, 20 Jun 2005 16:48:04 -0500 (CDT)
Received: by ma19exm01.e6.bcs.mot.com with Internet Mail Service (5.5.2657.72)
	id <KPGZA23L>; Mon, 20 Jun 2005 17:43:00 -0400
Message-ID: <62173B970AE0A044AED8723C3BCF238109316D3B@ma19exm01.e6.bcs.mot.com>
From: Eastlake III Donald-LDE008 <Donald.Eastlake@motorola.com>
To: "'routing-discussion@ietf.org'" <routing-discussion@ietf.org>
Date: Mon, 20 Jun 2005 17:42:59 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede
Subject: Re: WG Review: Transparent Interconnection of Lots of Links (tril l)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6ffdee8af20de249c24731d8414917d3

Hi,

A few points:

This has been presented to IEEE 802 in the form of a tutorial session at the March 2005 IEEE 802 plenary meeting.

In my opinion it is extremely unlikely that 802.1 will have anything to do with routing. They are dedicated to the Spanning Tree Protocol and minor variations thereof.

It is true that the deadline for submission of proposals to 802.11 TGs (Mesh Networking) was last week. I would expect some of the 15 proposals that were received to include some forms of "routing on MAC addresses". However, the charter for 802.11 TGs is fairly narrow, mainly targeting radio meshes of 32 APs or less. Whatever form of network path selection is adopted by 802.11 TGs is likely to be specialized.

Furthermore, in my opinion IEEE 802 does not have as much routing expertise as the IETF and IEEE 802 would be unlikely to include any IP optimizations in its standards.

So it does not appear to me that any group in IEEE 802 will do what the proposed TRILL Charter covers and "having the IEEE do it" is not an available option.

Donald (Chair of 802.11 TGs but just speaking for myself)

--------------------------------------------------------------------------------
Sue,

Please allow me to be a bit more direct...

What part of this should be in the IETF?  The IESG has made it quite
clear that they do not want a turf battle with the IEEE.

There seems like a clear separation of layers here and this is still L2
work.  As such, it would seem consistent for this should go over to
IEEE, even if it is  borrowing heavily from IETF technology.

Tony

Susan Hares wrote:
> Eric and Tony:
> 
> See my comments about Wireless Mesh proposal an Wi-Mesh alliance I'm a
> part of submitted 6/15/05 to the 802.11s.
> 
> Radia or others may know more about 802.1 since they have more history
> with IEEE.
> 
> Sue
> ------------------------------------------------------------------------
> 
> *From:* Eric W Gray [mailto:ewgray2k at netscape.net]
> *Sent:* Monday, June 20, 2005 2:45 PM
> *To:* Tony Li
> *Cc:* Susan Hares; Alex Zinin; rtg-dir at ietf.org;
> routing-discussion at ietf.org; rtg-chairs at ietf.org
> *Subject:* Re: WG Review: Transparent Interconnection of Lots of Links
> (trill)
> 
> Tony,
> 
>     No disagreement from me.  Perhaps the next obvious question is - has
> anyone taken this to the
> IEEE?
> --
> Eric
> Tony Li wrote:
> 
> In other instances, when proposals were IEEE'ish, we were directed to
> take them to the IEEE.
> 
> Tony
> 
> 
> Eric W Gray wrote:
> 
>>Sue,
>>
>>    The trouble with obvious questions is that everybody assumes they've
>>been  asked already.
>>Now this question has been asked at least once, for sure.  :-)
>>
>>    From the charter attached in Alex's previous message, the purpose is
>>to "route" Ethernet
>>Frames. Quote:
>>
>>The TRILL WG will design a solution for shortest-path frame routing in
>>multi-hop IEEE 802.1 Ethernet networks with arbitrary topologies,
>>using the link-state routing protocol technology.
>>
>>Since it is clear that at least some people are not satisfied with the
>>802.1 approach (perhaps
>>because of the relative inefficiency associated with completely unused
>>high capacity links), I
>>assume you mean to ask "why is it not IEEE" - rather than "why is it not
>>802.1".
>>
>>    I believe that is a very good question.  I know of no very good
>>reason why the IEEE might
>>not specify how to use an OSPF-like routing protocol to fulfill the role
>>previously handled by
>>Spanning Tree Protocol. Perhaps the only reason why it is being
>>discussed here is that it might
>>be better - for implementers - if the protocol used was more than
>>"OSPF-like."
>>--
>>
>>Eric
>>
>>shares at nexthop.com <mailto:shares at nexthop.com> wrote:
>>    
>>>Why are we doing this?  Is it IP or is it Frames?
>>>If it is Frames, why is it not 802.1 - etc? 
>>>
>>>Sue Hares
>>>
>>>-----Original Message-----
>>>
>>>From: Alex Zinin [mailto:zinin at psg.com] 
>>>Sent: Thursday, June 16, 2005 10:00 PM
>>>To: routing-discussion at ietf.org <mailto:routing-discussion at ietf.org>
>>>Cc: rtg-dir at ietf.org <mailto:rtg-dir at ietf.org>; rtg-chairs at ietf.org <mailto:rtg-chairs at ietf.org>
>>>Subject: Fwd: WG Review: Transparent Interconnection of Lots of Links (trill)
>>>
>>>Since the second BOF on this topic was inconclusive regarding community
>>>support, the IESG is reevaluating the community consensus on whether a WG
>>>should be formed or not.
>>>
>>>If you have input on this, positive or negative, please send it to
>>>iesg at ietf.org <mailto:iesg at ietf.org>.

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Mon Jun 20 18:09:34 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14997
	for <routing-discussion-archive@ietf.org>; Mon, 20 Jun 2005 18:09:34 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DkUqJ-0007FQ-5f
	for routing-discussion-archive@ietf.org; Mon, 20 Jun 2005 18:34:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DkUSD-0005Ih-BC; Mon, 20 Jun 2005 18:09:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DkUSB-0005IZ-DB
	for routing-discussion@megatron.ietf.org;
	Mon, 20 Jun 2005 18:09:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14915
	for <routing-discussion@ietf.org>; Mon, 20 Jun 2005 18:09:12 -0400 (EDT)
Received: from stl-smtpout-01.boeing.com ([130.76.96.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DkUpv-0007DC-Q1
	for routing-discussion@ietf.org; Mon, 20 Jun 2005 18:33:51 -0400
Received: from stl-av-01.boeing.com ([192.76.190.6])
	by stl-smtpout-01.boeing.com (8.9.2.MG.10092003/8.8.5-M2) with ESMTP id
	RAA02670; Mon, 20 Jun 2005 17:08:56 -0500 (CDT)
Received: from XCH-NE-05P.ne.nos.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.11.3/8.11.3/MBS-AV-LDAP-01) with ESMTP id
	j5KM8ql16793; Mon, 20 Jun 2005 17:08:52 -0500 (CDT)
Received: from XCH-NE-02.ne.nos.boeing.com ([128.225.80.202]) by
	XCH-NE-05P.ne.nos.boeing.com with Microsoft SMTPSVC(5.0.2195.6713); 
	Mon, 20 Jun 2005 18:08:51 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 20 Jun 2005 18:08:51 -0400
Message-ID: <EF40C42ACAB7A649B2EAE70C19B6CD6E037C3A5A@xch-ne-02.ne.nos.boeing.com>
Thread-Topic: WG Review: Transparent Interconnection of Lots of Links (tril l)
Thread-Index: AcV14ZL7Shxm331ETqqEAKi+mFkmDwAAM35w
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>,
        <routing-discussion@ietf.org>
X-OriginalArrivalTime: 20 Jun 2005 22:08:51.0859 (UTC)
	FILETIME=[A4402E30:01C575E4]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: quoted-printable
Subject: RE: WG Review: Transparent Interconnection of Lots of Links (tril l)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Content-Transfer-Encoding: quoted-printable

Some of this seems like semantics to me, though. The purpose of
replacing the existing RSTP with a more OSPF-like algorithm is not to
introduce IP optimization into 802.1, but rather to make 802.1 more
efficient than it currently is with RSTP.

I see such a new protocol as a functional replacement for the L2 RSTP,
not anything more. Specifically, dense L2 mesh nets today are very fault
tolerant, but also very wasteful of installed bandwidth. I don't think
we're talking about "routing," in the sense of going beyond L2
boundaries, correct? Just replacing one "node interconnection algorithm"
with another one.

Viewed as a next iteration beyond the new RSTP, which was introduced in
IEEE 802.1D-2004, that work by all rights belongs in the IEEE, I think.
Sue Hares is right, I think. If this new work involves only MAC frames,
it belongs in the IEEE and not IETF.

Bert


> -----Original Message-----
> From: Eastlake III Donald-LDE008=20
> [mailto:Donald.Eastlake@motorola.com]=20
> Sent: Monday, June 20, 2005 4:43 PM
> To: 'routing-discussion@ietf.org'
> Subject: Re: WG Review: Transparent Interconnection of Lots=20
> of Links (tril l)
>=20
> Hi,
>=20
> A few points:
>=20
> This has been presented to IEEE 802 in the form of a tutorial=20
> session at the March 2005 IEEE 802 plenary meeting.
>=20
> In my opinion it is extremely unlikely that 802.1 will have=20
> anything to do with routing. They are dedicated to the=20
> Spanning Tree Protocol and minor variations thereof.
>=20
> It is true that the deadline for submission of proposals to=20
> 802.11 TGs (Mesh Networking) was last week. I would expect=20
> some of the 15 proposals that were received to include some=20
> forms of "routing on MAC addresses". However, the charter for=20
> 802.11 TGs is fairly narrow, mainly targeting radio meshes of=20
> 32 APs or less. Whatever form of network path selection is=20
> adopted by 802.11 TGs is likely to be specialized.
>=20
> Furthermore, in my opinion IEEE 802 does not have as much=20
> routing expertise as the IETF and IEEE 802 would be unlikely=20
> to include any IP optimizations in its standards.
>=20
> So it does not appear to me that any group in IEEE 802 will=20
> do what the proposed TRILL Charter covers and "having the=20
> IEEE do it" is not an available option.
>=20
> Donald (Chair of 802.11 TGs but just speaking for myself)


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Tue Jun 21 13:17:35 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09182
	for <routing-discussion-archive@ietf.org>; Tue, 21 Jun 2005 13:17:35 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DkmlS-00034V-IO
	for routing-discussion-archive@ietf.org; Tue, 21 Jun 2005 13:42:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DkmMn-0001bf-Rk; Tue, 21 Jun 2005 13:16:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DkmMm-0001bQ-1D; Tue, 21 Jun 2005 13:16:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09095;
	Tue, 21 Jun 2005 13:16:39 -0400 (EDT)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DkmkY-000335-Db; Tue, 21 Jun 2005 13:41:27 -0400
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-3.cisco.com with ESMTP; 21 Jun 2005 10:16:26 -0700
X-IronPort-AV: i="3.93,218,1115017200"; 
	d="scan'208"; a="281402874:sNHT29599628"
Received: from cliff.cisco.com (cliff.cisco.com [171.69.11.141])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j5LHGNqi023398;
	Tue, 21 Jun 2005 10:16:24 -0700 (PDT)
Received: from [10.32.15.81] ([10.32.15.81]) by cliff.cisco.com (8.6.12/8.6.5)
	with ESMTP id KAA21237; Tue, 21 Jun 2005 10:16:23 -0700
Message-ID: <42B84B66.3050006@tony.li>
Date: Tue, 21 Jun 2005 10:16:22 -0700
From: Tony Li <tony.li@tony.li>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Margaret Wasserman <margaret@thingmagic.com>
References: <p0620074fbeddb701e9fe@[10.0.0.171]>
In-Reply-To: <p0620074fbeddb701e9fe@[10.0.0.171]>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: 7bit
Cc: Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org, iesg@ietf.org,
        routing-discussion@ietf.org, rtg-chairs@ietf.org, shares@nexthop.com
Subject: Re: Fwd: Re: WG Review: Transparent Interconnection of Lots of Links
 (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: 7bit


Margaret,

Thanks for your response.  IESG cc'ed per your request.

> Please let me know if you have any further questions.  The IESG will be
> making a decision on this charter at our telechat this Thursday (June
> 23rd), so if you have an opinion about whether or not we should charter
> this WG in the IETF, please send your comments to the IESG at
> iesg@ietf.org.  We are interested in hearing from folks who do want this
> work charted (especially from folks who are willing to invest time to
> make this happen), as well as from folks who have objections to
> chartering the group.

While I have no objection to chartering this group, I'm left scratching
my head in wonder, trying to find the consistency between accepting this
work and the previous decision to reject the IS-IS work on jumbo frames.
 You may recall that the opinion at the time was that the work would
step on IEEE toes and therefore the work was halted.  The IEEE chooses
not to endorse jumbo frames, so in some sense there is no
'standardization' to be done.  Vendors, however, continue to ship
running code for jumbo frames.  And there is no agreement for IS-IS
operation in such situations.

IMHO, the IETF needs to re-examine its goals and operations in this
regard.  What used to be an organization that was about standardizing
de-facto standards is now engaged in politicking at the expense of
technology.  We claim to eschew kings and voting, but we seem to be
engaged in SDO diplomacy at the expense of code, users, and the
Internet.  Does that seem right to you?

Regards,
Tony Li

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Tue Jun 21 16:04:11 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27805
	for <routing-discussion-archive@ietf.org>; Tue, 21 Jun 2005 16:04:11 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DkpMe-0008UM-Aj
	for routing-discussion-archive@ietf.org; Tue, 21 Jun 2005 16:29:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DkonG-0005b0-G4; Tue, 21 Jun 2005 15:52:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DkonF-0005ai-87; Tue, 21 Jun 2005 15:52:21 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25065;
	Tue, 21 Jun 2005 15:52:13 -0400 (EDT)
Received: from dns.nexthop.com ([65.247.36.216] helo=aa-mx1.nexthop.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DkpB8-0007Wu-5g; Tue, 21 Jun 2005 16:17:02 -0400
Received: from localhost (localhost [127.0.0.1])
	by aa-mx1.nexthop.com (Postfix) with ESMTP
	id 6169A2D4DD4; Tue, 21 Jun 2005 15:44:37 -0400 (EDT)
Received: from aa-mx1.nexthop.com ([127.0.0.1])
	by localhost (aa-mx1.nexthop.com [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id 97205-01-75; Tue, 21 Jun 2005 15:44:34 -0400 (EDT)
Received: from BOS-exch01.corp.nexthop.com (unknown [192.168.11.20])
	by aa-mx1.nexthop.com (Postfix) with ESMTP
	id EC2782D506A; Tue, 21 Jun 2005 15:36:24 -0400 (EDT)
Received: from aa-exchange1.corp.nexthop.com ([65.247.36.233]) by
	BOS-exch01.corp.nexthop.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Jun 2005 15:36:24 -0400
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Date: Tue, 21 Jun 2005 15:36:23 -0400
Message-ID: <BE36D687C8CBFA4AB76F5CD3E3C0FB4E0402B129@aa-exchange.corp.nexthop.com>
Thread-Topic: Fwd: Re: WG Review: Transparent Interconnection of Lots of Links
	(trill)
thread-index: AcV2iTECxV7uf93hRByoCsi+T5xw+gACqXTQ
From: "Susan Hares" <shares@nexthop.com>
To: "Tony Li" <tony.li@tony.li>,
        "Margaret Wasserman" <margaret@thingmagic.com>
X-OriginalArrivalTime: 21 Jun 2005 19:36:24.0552 (UTC)
	FILETIME=[8271A680:01C57698]
X-Virus-Scanned: by amavisd-new at nexthop.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Content-Transfer-Encoding: quoted-printable
Cc: Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org, iesg@ietf.org,
        routing-discussion@ietf.org, rtg-chairs@ietf.org
Subject: RE: Fwd: Re: WG Review: Transparent Interconnection of Lots of
	Links (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Content-Transfer-Encoding: quoted-printable

Margaret:

The key point is we want to ship product with standardization.
(A good thing for all of us (IMHO).)

The rules used to be clear:

MAC address =3D IEEE
IP address/Label =3D IETF.

If we are changing the rules, we need to be clear that we are changing
the rules clearly.  Tony notes where the change in the rules didn't
match.

You worked hard to make sure we had IETF consistency.  It would be
helpful to make sure we have the same for IEEE/IETF consistency.

Many thanks,

Sue Hares

-----Original Message-----
From: Tony Li [mailto:tony.li@tony.li]=20
Sent: Tuesday, June 21, 2005 1:16 PM
To: Margaret Wasserman
Cc: Alex Zinin; rtg-dir@ietf.org; rtg-chairs@ietf.org;
routing-discussion@ietf.org; Susan Hares; iesg@ietf.org
Subject: Re: Fwd: Re: WG Review: Transparent Interconnection of Lots of
Links (trill)


Margaret,

Thanks for your response.  IESG cc'ed per your request.

> Please let me know if you have any further questions.  The IESG will
be
> making a decision on this charter at our telechat this Thursday (June
> 23rd), so if you have an opinion about whether or not we should
charter
> this WG in the IETF, please send your comments to the IESG at
> iesg@ietf.org.  We are interested in hearing from folks who do want
this
> work charted (especially from folks who are willing to invest time to
> make this happen), as well as from folks who have objections to
> chartering the group.

While I have no objection to chartering this group, I'm left scratching
my head in wonder, trying to find the consistency between accepting this
work and the previous decision to reject the IS-IS work on jumbo frames.
 You may recall that the opinion at the time was that the work would
step on IEEE toes and therefore the work was halted.  The IEEE chooses
not to endorse jumbo frames, so in some sense there is no
'standardization' to be done.  Vendors, however, continue to ship
running code for jumbo frames.  And there is no agreement for IS-IS
operation in such situations.

IMHO, the IETF needs to re-examine its goals and operations in this
regard.  What used to be an organization that was about standardizing
de-facto standards is now engaged in politicking at the expense of
technology.  We claim to eschew kings and voting, but we seem to be
engaged in SDO diplomacy at the expense of code, users, and the
Internet.  Does that seem right to you?

Regards,
Tony Li


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Wed Jun 22 07:52:25 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29405
	for <routing-discussion-archive@ietf.org>; Wed, 22 Jun 2005 07:52:25 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl4AU-0004iA-7t
	for routing-discussion-archive@ietf.org; Wed, 22 Jun 2005 08:17:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl3jV-00080N-Uc; Wed, 22 Jun 2005 07:49:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl3jS-000803-Nf; Wed, 22 Jun 2005 07:49:28 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29211;
	Wed, 22 Jun 2005 07:49:21 -0400 (EDT)
Received: from [204.9.221.21] (helo=thingmagic.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl47W-0004cd-JB; Wed, 22 Jun 2005 08:14:18 -0400
Received: from [66.30.121.250] (account margaret HELO [10.0.0.171])
	by thingmagic.com (CommuniGate Pro SMTP 4.1.8)
	with ESMTP-TLS id 398480; Wed, 22 Jun 2005 07:44:07 -0400
Mime-Version: 1.0
Message-Id: <p06200781bedefae66141@[10.0.0.171]>
In-Reply-To: <42B84B66.3050006@tony.li>
References: <p0620074fbeddb701e9fe@[10.0.0.171]> <42B84B66.3050006@tony.li>
Date: Wed, 22 Jun 2005 07:49:16 -0400
To: Tony Li <tony.li@tony.li>
From: Margaret Wasserman <margaret@thingmagic.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Cc: Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org, iesg@ietf.org,
        routing-discussion@ietf.org, rtg-chairs@ietf.org, shares@nexthop.com
Subject: Re: Fwd: Re: WG Review: Transparent Interconnection of Lots of
 Links  (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1


Hi Tony,

At 10:16 AM -0700 6/21/05, Tony Li wrote:
>While I have no objection to chartering this group, I'm left scratching
>my head in wonder, trying to find the consistency between accepting this
>work and the previous decision to reject the IS-IS work on jumbo frames.

I am sorry, but I am not familiar with the decision to reject work on 
IS-IS jumbo frames.  I don't follow the IS-IS WG, so if the decision 
was made in that context, I would not have been aware of it.

>  You may recall that the opinion at the time was that the work would
>step on IEEE toes and therefore the work was halted.  The IEEE chooses
>not to endorse jumbo frames, so in some sense there is no
>'standardization' to be done.  Vendors, however, continue to ship
>running code for jumbo frames.  And there is no agreement for IS-IS
>operation in such situations.

This sounds like a difficult situation.

In the particular case of TRILL, we were concerned that the work 
might conflict with IEEE work, so we talked to the IEEE 802 
leadership about it.  They did not express interest in chartering 
this work in the IEEE, and they did not object to chartering it in 
the IETF.

I am not quite sure what we would have done if the IEEE had said that 
they would not charter the work, but that they objected to the IETF 
chartering the work...  Luckily for me and the folks working on 
TRILL, we did not have to figure out what to do in that situation.

>IMHO, the IETF needs to re-examine its goals and operations in this
>regard.  What used to be an organization that was about standardizing
>de-facto standards is now engaged in politicking at the expense of
>technology.  We claim to eschew kings and voting, but we seem to be
>engaged in SDO diplomacy at the expense of code, users, and the
>Internet.  Does that seem right to you?

Personally, I agree with you on many counts...  I think that we do 
our best work when we standardize something that is already 
implemented in various forms and/or when vendors or operators decide 
that it would be useful to standardize an already-deployed 
technology, so that we can maximize interoperability and have a clear 
forum to discuss clarifications and extensions.

There are, of course, a large number of people who don't agree with 
that image of the IETF.  They believe that we should be standardizing 
ideas that come out of our research efforts, developing solutions to 
real (or perceived?) problems with the operation of the Internet, 
and/or standardizing solutions that will meet the needs of market 
niches that are not addressed by current technologies.   In fact, I 
suspect that most of us have fallen into one of those camps from 
time-to-time.

There is a widely held belief that standardizing a solution greatly 
increases the possibility that vendors and operators will implement 
and deploy the solution, and I am really not sure that this is the 
case...  Maybe this is a cultural issue -- 3GPP vendor and operators, 
for example, will implement and deploy whatever is standardized as 
"3GPP".  But, the more traditional Internet doesn't work that way -- 
we can't make someone implement something by standardizing it, and we 
can't prevent them by not standardizing it.  It might help for us to 
remember that more often.

Ultimately, though, the best way to address this problem is not by 
trying to enforce a specific view of the IETF from the top down 
(which would defeat the whole purpose), but through communicating a 
different vision of the IETF and trying to get enough people to adopt 
that vision that it becomes the prevailing culture (again?).

Margaret







I

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Wed Jun 22 08:15:44 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02099
	for <routing-discussion-archive@ietf.org>; Wed, 22 Jun 2005 08:15:44 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl4X4-0005X8-9j
	for routing-discussion-archive@ietf.org; Wed, 22 Jun 2005 08:40:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl47k-0001pz-Of; Wed, 22 Jun 2005 08:14:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl47i-0001p0-K1; Wed, 22 Jun 2005 08:14:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01788;
	Wed, 22 Jun 2005 08:12:39 -0400 (EDT)
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl4U3-0005Rl-PY; Wed, 22 Jun 2005 08:37:37 -0400
Received: from rtp-core-2.cisco.com (64.102.124.13)
	by rtp-iport-2.cisco.com with ESMTP; 22 Jun 2005 08:12:31 -0400
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j5MCCRgl019379; 
	Wed, 22 Jun 2005 08:12:27 -0400 (EDT)
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Wed, 22 Jun 2005 05:11:25 -0700
Received: from cisco.com ([171.68.225.134]) by xfe-sjc-212.amer.cisco.com with
	Microsoft SMTPSVC(6.0.3790.211); Wed, 22 Jun 2005 05:11:46 -0700
Date: Wed, 22 Jun 2005 08:11:12 -0400
From: Scott W Brim <sbrim@cisco.com>
To: Margaret Wasserman <margaret@thingmagic.com>
Message-ID: <20050622121111.GE4988@sbrim-wxp01>
Mail-Followup-To: Scott W Brim <sbrim@cisco.com>,
	Margaret Wasserman <margaret@thingmagic.com>,
	Tony Li <tony.li@tony.li>, Alex Zinin <zinin@psg.com>,
	rtg-dir@ietf.org, iesg@ietf.org, routing-discussion@ietf.org,
	rtg-chairs@ietf.org, shares@nexthop.com
References: <p0620074fbeddb701e9fe@[10.0.0.171]> <42B84B66.3050006@tony.li>
	<p06200781bedefae66141@[10.0.0.171]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <p06200781bedefae66141@[10.0.0.171]>
User-Agent: Mutt/1.4.2.1i
X-OriginalArrivalTime: 22 Jun 2005 12:11:46.0330 (UTC)
	FILETIME=[8F65C7A0:01C57723]
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org, iesg@ietf.org,
        routing-discussion@ietf.org, rtg-chairs@ietf.org, shares@nexthop.com
Subject: Re: Fwd: Re: WG Review: Transparent Interconnection of Lots of
	Links (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f

On Wed, Jun 22, 2005 07:49:16AM -0400, Margaret Wasserman allegedly wrote:
> In the particular case of TRILL, we were concerned that the work 
> might conflict with IEEE work, so we talked to the IEEE 802 
> leadership about it.  They did not express interest in chartering 
> this work in the IEEE, and they did not object to chartering it in 
> the IETF.

I am told that there is a new work item developing somewhere in IEEE
802, "shortest path bridging", which will deal with optimum paths and
fast convergence while maintaining current forwarding semantics.  I
was also told that there is talk of a tutorial BOF at the Paris IETF
about it.  I'm trying to get my source to speak up and say all this
wrt TRILL.

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Wed Jun 22 08:25:08 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02829
	for <routing-discussion-archive@ietf.org>; Wed, 22 Jun 2005 08:25:08 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl4g9-0005pN-KJ
	for routing-discussion-archive@ietf.org; Wed, 22 Jun 2005 08:50:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl4Dq-0004VF-Oo; Wed, 22 Jun 2005 08:20:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl4Do-0004Uv-EV; Wed, 22 Jun 2005 08:20:48 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02447;
	Wed, 22 Jun 2005 08:20:40 -0400 (EDT)
Received: from relay2.mail.uk.clara.net ([80.168.70.142])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl4bo-0005gy-4I; Wed, 22 Jun 2005 08:45:38 -0400
Received: from du-069-0228.access.clara.net ([217.158.132.228] helo=Puppy)
	by relay2.mail.uk.clara.net with smtp (Exim 4.50)
	id 1Dl4DX-000Ds8-8T; Wed, 22 Jun 2005 13:20:33 +0100
Message-ID: <070101c57725$1ca07420$7f849ed9@Puppy>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "Brian E Carpenter" <brc@zurich.ibm.com>
References: <BE36D687C8CBFA4AB76F5CD3E3C0FB4E0402B129@aa-exchange.corp.nexthop.com>
	<42B94484.5070806@zurich.ibm.com>
Date: Wed, 22 Jun 2005 13:22:46 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196
Content-Transfer-Encoding: 7bit
Cc: Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org, iesg@ietf.org,
        routing-discussion@ietf.org, rtg-chairs@ietf.org,
        Susan Hares <shares@nexthop.com>
Subject: Re: Fwd: Re: WG Review: Transparent Interconnection of Lots
	of	Links (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3
Content-Transfer-Encoding: 7bit

I think the skill-set to which Brian refers is link state routing. (Care
to confirm, Brian?)

If so, why is this WG targeted at the Internet Area not the Routing area?

Cheers,
Adrian (Still not opposing, just seeking clarification)
----- Original Message ----- 
From: "Brian E Carpenter" <brc@zurich.ibm.com>
To: "Susan Hares" <shares@nexthop.com>
Cc: "Tony Li" <tony.li@tony.li>; "Margaret Wasserman"
<margaret@thingmagic.com>; "Alex Zinin" <zinin@psg.com>;
<rtg-dir@ietf.org>; <iesg@ietf.org>; <routing-discussion@ietf.org>;
<rtg-chairs@ietf.org>
Sent: Wednesday, June 22, 2005 11:59 AM
Subject: Re: Fwd: Re: WG Review: Transparent Interconnection of Lots of
Links (trill)


> I can't speak to past events, but in this case there has been
> substantial discusssion with IEEE and I don't think there is any
> disturbance to the addressing "rule" that you cite. But the
> skill set for this particular work is in the IETF. Nobody
> denies that it's in the grey area where the question of scope
> can be discussed endlessly, but the intention is now to decide
> quickly, since the proponents have been more than patient.
>
>     Brian
>
> Susan Hares wrote:
> > Margaret:
> >
> > The key point is we want to ship product with standardization.
> > (A good thing for all of us (IMHO).)
> >
> > The rules used to be clear:
> >
> > MAC address = IEEE
> > IP address/Label = IETF.
> >
> > If we are changing the rules, we need to be clear that we are changing
> > the rules clearly.  Tony notes where the change in the rules didn't
> > match.
> >
> > You worked hard to make sure we had IETF consistency.  It would be
> > helpful to make sure we have the same for IEEE/IETF consistency.
> >
> > Many thanks,
> >
> > Sue Hares
> >
> > -----Original Message-----
> > From: Tony Li [mailto:tony.li@tony.li]
> > Sent: Tuesday, June 21, 2005 1:16 PM
> > To: Margaret Wasserman
> > Cc: Alex Zinin; rtg-dir@ietf.org; rtg-chairs@ietf.org;
> > routing-discussion@ietf.org; Susan Hares; iesg@ietf.org
> > Subject: Re: Fwd: Re: WG Review: Transparent Interconnection of Lots
of
> > Links (trill)
> >
> >
> > Margaret,
> >
> > Thanks for your response.  IESG cc'ed per your request.
> >
> >
> >>Please let me know if you have any further questions.  The IESG will
> >
> > be
> >
> >>making a decision on this charter at our telechat this Thursday (June
> >>23rd), so if you have an opinion about whether or not we should
> >
> > charter
> >
> >>this WG in the IETF, please send your comments to the IESG at
> >>iesg@ietf.org.  We are interested in hearing from folks who do want
> >
> > this
> >
> >>work charted (especially from folks who are willing to invest time to
> >>make this happen), as well as from folks who have objections to
> >>chartering the group.
> >
> >
> > While I have no objection to chartering this group, I'm left
scratching
> > my head in wonder, trying to find the consistency between accepting
this
> > work and the previous decision to reject the IS-IS work on jumbo
frames.
> >  You may recall that the opinion at the time was that the work would
> > step on IEEE toes and therefore the work was halted.  The IEEE chooses
> > not to endorse jumbo frames, so in some sense there is no
> > 'standardization' to be done.  Vendors, however, continue to ship
> > running code for jumbo frames.  And there is no agreement for IS-IS
> > operation in such situations.
> >
> > IMHO, the IETF needs to re-examine its goals and operations in this
> > regard.  What used to be an organization that was about standardizing
> > de-facto standards is now engaged in politicking at the expense of
> > technology.  We claim to eschew kings and voting, but we seem to be
> > engaged in SDO diplomacy at the expense of code, users, and the
> > Internet.  Does that seem right to you?
> >
> > Regards,
> > Tony Li
> >
> >
> >
>
>
>


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Wed Jun 22 08:49:05 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04908
	for <routing-discussion-archive@ietf.org>; Wed, 22 Jun 2005 08:49:04 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl53J-0006a1-So
	for routing-discussion-archive@ietf.org; Wed, 22 Jun 2005 09:14:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl4dw-0005sn-TB; Wed, 22 Jun 2005 08:47:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl4du-0005re-Dy; Wed, 22 Jun 2005 08:47:46 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04769;
	Wed, 22 Jun 2005 08:47:41 -0400 (EDT)
Received: from [204.9.221.21] (helo=thingmagic.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl51x-0006VS-AI; Wed, 22 Jun 2005 09:12:39 -0400
Received: from [66.30.121.250] (account margaret HELO [10.0.0.171])
	by thingmagic.com (CommuniGate Pro SMTP 4.1.8)
	with ESMTP-TLS id 398544; Wed, 22 Jun 2005 08:42:13 -0400
Mime-Version: 1.0
Message-Id: <p06200782bedf0d0ca238@[10.0.0.171]>
In-Reply-To: <20050622121111.GE4988@sbrim-wxp01>
References: <p0620074fbeddb701e9fe@[10.0.0.171]>
	<42B84B66.3050006@tony.li>	<p06200781bedefae66141@[10.0.0.171]>
	<20050622121111.GE4988@sbrim-wxp01>
Date: Wed, 22 Jun 2005 08:44:48 -0400
To: Scott W Brim <sbrim@cisco.com>
From: Margaret Wasserman <margaret@thingmagic.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org, iesg@ietf.org,
        routing-discussion@ietf.org, rtg-chairs@ietf.org, shares@nexthop.com
Subject: Re: Fwd: Re: WG Review: Transparent Interconnection of Lots of 
 Links (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d


Hi Scott,

We are aware of this proposed work in the IEEE, and the major 
proponents of this work (Mick Seaman and Norm Finn) were present on 
the call that we had with IEEE 802 leadership to discuss chartering 
the TRILL WG in the IETF.

The proposed IEEE effort is an (R)STP-based mechanism and will, 
therefore, have different applicability than a link-state-based 
mechanism, such as TRILL.  I am not sure how/if either will fare in 
the market, but they are not directly overlapping efforts.  In fact, 
there has been some interest in TRILL expressed by  at least one IEEE 
WG chair, as that group may have a need for a link-state Ethernet 
routing mechanism.

Margaret


At 8:11 AM -0400 6/22/05, Scott W Brim wrote:
>On Wed, Jun 22, 2005 07:49:16AM -0400, Margaret Wasserman allegedly wrote:
>>  In the particular case of TRILL, we were concerned that the work
>>  might conflict with IEEE work, so we talked to the IEEE 802
>>  leadership about it.  They did not express interest in chartering
>>  this work in the IEEE, and they did not object to chartering it in
>>  the IETF.
>
>I am told that there is a new work item developing somewhere in IEEE
>802, "shortest path bridging", which will deal with optimum paths and
>fast convergence while maintaining current forwarding semantics.  I
>was also told that there is talk of a tutorial BOF at the Paris IETF
>about it.  I'm trying to get my source to speak up and say all this
>wrt TRILL.


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Wed Jun 22 09:01:10 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05914
	for <routing-discussion-archive@ietf.org>; Wed, 22 Jun 2005 09:01:10 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl5F1-0006y6-Jk
	for routing-discussion-archive@ietf.org; Wed, 22 Jun 2005 09:26:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl4nZ-0002Cc-Vc; Wed, 22 Jun 2005 08:57:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl4nU-0002Ax-MI; Wed, 22 Jun 2005 08:57:40 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA05562;
	Wed, 22 Jun 2005 08:57:35 -0400 (EDT)
Received: from [204.9.221.21] (helo=thingmagic.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl5BX-0006oP-8b; Wed, 22 Jun 2005 09:22:33 -0400
Received: from [66.30.121.250] (account margaret HELO [10.0.0.171])
	by thingmagic.com (CommuniGate Pro SMTP 4.1.8)
	with ESMTP-TLS id 398559; Wed, 22 Jun 2005 08:52:18 -0400
Mime-Version: 1.0
Message-Id: <p06200783bedf0dc6cdad@[10.0.0.171]>
In-Reply-To: <070101c57725$1ca07420$7f849ed9@Puppy>
References: <BE36D687C8CBFA4AB76F5CD3E3C0FB4E0402B129@aa-exchange.corp.nexthop.com>
	<42B94484.5070806@zurich.ibm.com>
	<070101c57725$1ca07420$7f849ed9@Puppy>
Date: Wed, 22 Jun 2005 08:57:27 -0400
To: "Adrian Farrel" <adrian@olddog.co.uk>,
        "Brian E Carpenter" <brc@zurich.ibm.com>
From: Margaret Wasserman <margaret@thingmagic.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org, iesg@ietf.org,
        routing-discussion@ietf.org, rtg-chairs@ietf.org,
        Susan Hares <shares@nexthop.com>
Subject: Re: Fwd: Re: WG Review: Transparent Interconnection of Lots of
 Links (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8


Hi Adrian,

At 1:22 PM +0100 6/22/05, Adrian Farrel wrote:
>I think the skill-set to which Brian refers is link state routing. (Care
>to confirm, Brian?)

Yes, expertise in link-state routing is certainly one reason why this 
work could be seen as more in-scope for the IETF than for the IEEE. 
Also, frankly, there is interest in the IETF in doing this work (a 
link-state-based Ethernet routing solution), while the IEEE is 
continuing to pursue (R)STP-based approaches.

>If so, why is this WG targeted at the Internet Area not the Routing area?

This questions has been discussed in the IESG, as well, and we did 
not have 100% agreement regarding the area in which this work belongs.

Personally, I think that TRILL is a better fit for the Internet area, 
and I will explain why...

Traditionally, the division between the Internet area and the Routing 
area has been that the Routing area deals with protocols that 
distribute routing information (routes/labels) and the Internet area 
has been responsible for the forwarding behaviour and encapsulation 
mechanisms that make use of that information.

The TRILL charter maintains that split -- any work on the routing 
protocols themselves would be done in the routing area, while the 
encapsulation/forwarding mechanism would be developed in the Internet 
area.

Perhaps you have a different model of the division between the 
Routing and Internet areas that makes you think otherwise?

The IESG discussed this issue several months ago.  We agreed that 
this work is close to the line between Internet and Routing, but we 
reached an agreement that it would best be placed in the Internet 
area, with the understanding that we would appoint a technical 
advisor and a WG co-chair with routing expertise.  BIll Fenner 
volunteered to be the Technical Advisor, and Bill and Alex took an 
action item to return with a list of potential co-chairs.

Ultimately, I am not sure that it matters all that much which area 
this work is done in, since it will require expertise and involvement 
from both areas in order to succeed.

Margaret





_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Wed Jun 22 09:02:19 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06062
	for <routing-discussion-archive@ietf.org>; Wed, 22 Jun 2005 09:02:19 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl5G8-0006zz-79
	for routing-discussion-archive@ietf.org; Wed, 22 Jun 2005 09:27:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl4rG-0002qm-Qx; Wed, 22 Jun 2005 09:01:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl4rB-0002qI-Cb; Wed, 22 Jun 2005 09:01:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05893;
	Wed, 22 Jun 2005 09:00:57 -0400 (EDT)
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl5En-0006vq-KB; Wed, 22 Jun 2005 09:25:55 -0400
Received: from rtp-core-2.cisco.com (64.102.124.13)
	by rtp-iport-2.cisco.com with ESMTP; 22 Jun 2005 09:00:48 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j5MCxVh5018725; 
	Wed, 22 Jun 2005 08:59:53 -0400 (EDT)
Received: from xbh-sjc-231.amer.cisco.com ([128.107.191.100]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Wed, 22 Jun 2005 08:59:18 -0400
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Wed, 22 Jun 2005 05:59:16 -0700
Received: from cisco.com ([171.68.225.134]) by xfe-sjc-211.amer.cisco.com with
	Microsoft SMTPSVC(6.0.3790.211); Wed, 22 Jun 2005 05:58:38 -0700
Date: Wed, 22 Jun 2005 08:58:41 -0400
From: Scott W Brim <sbrim@cisco.com>
To: Margaret Wasserman <margaret@thingmagic.com>
Message-ID: <20050622125838.GF4988@sbrim-wxp01>
Mail-Followup-To: Scott W Brim <sbrim@cisco.com>,
	Margaret Wasserman <margaret@thingmagic.com>,
	Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org,
	Tony Li <tony.li@tony.li>, iesg@ietf.org,
	routing-discussion@ietf.org, rtg-chairs@ietf.org,
	shares@nexthop.com
References: <p0620074fbeddb701e9fe@[10.0.0.171]> <42B84B66.3050006@tony.li>
	<p06200781bedefae66141@[10.0.0.171]>
	<20050622121111.GE4988@sbrim-wxp01>
	<p06200782bedf0d0ca238@[10.0.0.171]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <p06200782bedf0d0ca238@[10.0.0.171]>
User-Agent: Mutt/1.4.2.1i
X-OriginalArrivalTime: 22 Jun 2005 12:58:38.0098 (UTC)
	FILETIME=[1B578720:01C5772A]
X-Spam-Score: 1.1 (+)
X-Scan-Signature: bb8eae9af85e4fcfe76f325e38493bf4
Cc: Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org, iesg@ietf.org,
        routing-discussion@ietf.org, rtg-chairs@ietf.org, shares@nexthop.com
Subject: Re: Fwd: Re: WG Review: Transparent Interconnection of Lots of
	Links (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea

OK thanks.

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Wed Jun 22 10:34:57 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16754
	for <routing-discussion-archive@ietf.org>; Wed, 22 Jun 2005 10:34:57 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl6hh-0001ok-T0
	for routing-discussion-archive@ietf.org; Wed, 22 Jun 2005 10:59:56 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl6Ik-0007tT-Sc; Wed, 22 Jun 2005 10:34:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DkSXi-0002fc-Dy; Mon, 20 Jun 2005 16:06:50 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06036;
	Mon, 20 Jun 2005 16:06:47 -0400 (EDT)
Received: from dyn50.sunlabs.com ([204.153.12.50] helo=mail-mta.sunlabs.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DkSvO-00041f-MG; Mon, 20 Jun 2005 16:31:24 -0400
Received: from mail.sunlabs.com ([152.70.2.186]) by mail-mta.sfvic.sunlabs.com
	(Sun Java System Messaging Server 6.1 HotFix 0.02 (built Aug 25
	2004))
	with ESMTP id <0IIE0023GFUO0100@mail-mta.sfvic.sunlabs.com>; Mon,
	20 Jun 2005 13:06:24 -0700 (PDT)
Received: from sun.com ([129.150.31.236])
	by mail.sunlabs.com (Sun Java System Messaging Server 6.1 HotFix 0.02
	(built
	Aug 25 2004)) with ESMTPSA id <0IIE0055AFUN1EX3@mail.sunlabs.com>; Mon,
	20 Jun 2005 13:06:24 -0700 (PDT)
Date: Mon, 20 Jun 2005 13:06:24 -0700
From: Radia Perlman <Radia.Perlman@sun.com>
In-reply-to: <BE36D687C8CBFA4AB76F5CD3E3C0FB4E0402AF97@aa-exchange1.corp.nexthop.com>
To: Susan Hares <shares@nexthop.com>
Message-id: <42B721C0.5010808@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=windows-1252; format=flowed
Content-transfer-encoding: QUOTED-PRINTABLE
X-Accept-Language: en-us, en
References: <BE36D687C8CBFA4AB76F5CD3E3C0FB4E0402AF97@aa-exchange1.corp.nexthop.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4.1)
	Gecko/20031008
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 65bc4909d78e8b10349def623cf7a1d1
Content-Transfer-Encoding: QUOTED-PRINTABLE
X-Mailman-Approved-At: Wed, 22 Jun 2005 10:34:01 -0400
Cc: Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org, ewgray@GraIyMage.com,
        routing-discussion@ietf.org, rtg-chairs@ietf.org
Subject: Re: WG Review: Transparent Interconnection of Lots of Links (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c2e58d9873012c90703822e287241385
Content-Transfer-Encoding: QUOTED-PRINTABLE

Yes. This has been discussed with IEEE. I even gave a tutorial there =
on=20
TRILL at the
last IEEE, both at a general tutorial slot and at the mesh group=20
(invited by the chair
of that group, Don Eastlake). It got a very friendly reception, by th=
e way.

There are some people in the wireless mesh group who
have since mentioned to me that they are interested
in proposing a solution like this within the mesh group.
And that would be good. But this technology is not specific to any=
=20
particular
layer 2 technology, and certainly not limited to wireless. So it shou=
ld=20
be standardized in something
that is layer 2 agnostic. It could also be used in other places, of=
=20
course, and if multiple WGs are
working on similar things, it is good if they cooperate and liase (is=
=20
that a word?) so that technology
works well together, and even better yet, if it converges towards the=
=20
same design. I believe
the intention of all concerned is that all the WGs that might be=20
interested and might
be helpful have liason relationships.

Radia



Susan Hares wrote:

> Eric and Tony:
>
> See my comments about Wireless Mesh proposal an Wi-Mesh alliance I=
=92m a=20
> part of submitted 6/15/05 to the 802.11s.
>
> Radia or others may know more about 802.1 since they have more hist=
ory=20
> with IEEE.
>
> Sue
>
> -------------------------------------------------------------------=
-----
>
> *From:* Eric W Gray [mailto:ewgray2k@netscape.net]
> *Sent:* Monday, June 20, 2005 2:45 PM
> *To:* Tony Li
> *Cc:* Susan Hares; Alex Zinin; rtg-dir@ietf.org;=20
> routing-discussion@ietf.org; rtg-chairs@ietf.org
> *Subject:* Re: WG Review: Transparent Interconnection of Lots of Li=
nks=20
> (trill)
>
> Tony,
>
> No disagreement from me. Perhaps the next obvious question is - has=
=20
> anyone taken this to the
> IEEE?
>
> --
> Eric
>
> Tony Li wrote:
>
>=20
>
>In other instances, when proposals were IEEE'ish, we were directed t=
o
>
>take them to the IEEE.
>
>=20
>
>Tony
>
>=20
>
>=20
>
>Eric W Gray wrote:
>
> =20
>
>>Sue,
>>
>>=20
>>
>>    The trouble with obvious questions is that everybody assumes th=
ey've
>>
>>been  asked already.
>>
>>Now this question has been asked at least once, for sure.  :-)
>>
>>=20
>>
>>    From the charter attached in Alex's previous message, the purpo=
se is
>>
>>to "route" Ethernet
>>
>>Frames. Quote:
>>
>>=20
>>
>>The TRILL WG will design a solution for shortest-path frame routing=
 in
>>
>>multi-hop IEEE 802.1 Ethernet networks with arbitrary topologies,
>>
>>using the link-state routing protocol technology.
>>
>>=20
>>
>>Since it is clear that at least some people are not satisfied with =
the
>>
>>802.1 approach (perhaps
>>
>>because of the relative inefficiency associated with completely unu=
sed
>>
>>high capacity links), I
>>
>>assume you mean to ask "why is it not IEEE" - rather than "why is i=
t not
>>
>>802.1".
>>
>>=20
>>
>>    I believe that is a very good question.  I know of no very good
>>
>>reason why the IEEE might
>>
>>not specify how to use an OSPF-like routing protocol to fulfill the=
 role
>>
>>previously handled by
>>
>>Spanning Tree Protocol. Perhaps the only reason why it is being
>>
>>discussed here is that it might
>>
>>be better - for implementers - if the protocol used was more than
>>
>>"OSPF-like."
>>
>>=20
>>
>>--
>>
>>Eric
>>
>>=20
>>
>>shares@nexthop.com <mailto:shares@nexthop.com> wrote:
>>
>>=20
>>
>>   =20
>>
>>>Why are we doing this?  Is it IP or is it Frames?
>>>
>>>If it is Frames, why is it not 802.1 - etc?=20
>>>
>>>=20
>>>
>>>Sue Hares
>>>
>>>=20
>>>
>>>-----Original Message-----
>>>
>>>From: Alex Zinin [mailto:zinin@psg.com]=20
>>>
>>>Sent: Thursday, June 16, 2005 10:00 PM
>>>
>>>To: routing-discussion@ietf.org <mailto:routing-discussion@ietf.or=
g>
>>>
>>>Cc: rtg-dir@ietf.org <mailto:rtg-dir@ietf.org>; rtg-chairs@ietf.or=
g <mailto:rtg-chairs@ietf.org>
>>>
>>>Subject: Fwd: WG Review: Transparent Interconnection of Lots of Li=
nks
>>>
>>>(trill)
>>>
>>>=20
>>>
>>>Since the second BOF on this topic was inconclusive regarding comm=
unity
>>>
>>>support, the IESG is reevaluating the community consensus on wheth=
er a
>>>
>>>WG
>>>
>>>should be formed or not.
>>>
>>>=20
>>>
>>>If you have input on this, positive or negative, please send it to
>>>
>>>iesg@ietf.org <mailto:iesg@ietf.org>.
>>>
>>>=20
>>>
>>>=20
>>>
>>>=20
>>>
>>>     =20
>>>
>>-------------------------------------------------------------------=
-----
>>
>>=20
>>
>>_______________________________________________
>>
>>routing-discussion mailing list
>>
>>routing-discussion@ietf.org <mailto:routing-discussion@ietf.org>
>>
>>https://www1.ietf.org/mailman/listinfo/routing-discussion
>>
>>   =20
>>
>=20
>
>=20
>
>=20
>
> =20
>



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Wed Jun 22 10:34:58 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16793
	for <routing-discussion-archive@ietf.org>; Wed, 22 Jun 2005 10:34:58 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl6hh-0001oi-JI
	for routing-discussion-archive@ietf.org; Wed, 22 Jun 2005 10:59:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl6Im-0007vX-4v; Wed, 22 Jun 2005 10:34:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DkiHe-0001WS-3r; Tue, 21 Jun 2005 08:55:18 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14612;
	Tue, 21 Jun 2005 08:55:09 -0400 (EDT)
Received: from [204.9.221.21] (helo=thingmagic.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DkifN-0003v0-4Y; Tue, 21 Jun 2005 09:19:54 -0400
Received: from [66.30.121.250] (account margaret HELO [10.0.0.171])
	by thingmagic.com (CommuniGate Pro SMTP 4.1.8)
	with ESMTP-TLS id 397058; Tue, 21 Jun 2005 08:49:41 -0400
Mime-Version: 1.0
Message-Id: <p0620074fbeddb701e9fe@[10.0.0.171]>
Date: Tue, 21 Jun 2005 08:54:45 -0400
To: Tony Li <tony.li@tony.li>, Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org,
        rtg-chairs@ietf.org, routing-discussion@ietf.org, shares@nexthop.com
From: Margaret Wasserman <margaret@thingmagic.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
X-Mailman-Approved-At: Wed, 22 Jun 2005 10:34:01 -0400
Subject: Fwd: Re: WG Review: Transparent Interconnection of Lots of Links 
 (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135


Hi All,

Erik forwarded this message to me, so that I could reply.  I used to 
be on routing-discussion (at least I thought I was), but I don't seem 
to be now, so please include me in any responses.

At 14:44:54 AM -0400 6/20/05, Eric W Gray wrote:
>Tony,
>
>     No disagreement from me.  Perhaps the next obvious question is - has
>anyone taken this to the
>IEEE?

We have talked to the IEEE about this, and they are very aware of 
this work.  There were several e-mail exchanges with IEEE 802 leaders 
in response to the first charter that was circulated for external 
review last November.  This lead to an e-mail discussion between IEEE 
leadership and the IESG/IAB.  We then had a conference call between 
the interested IESG folks, Bernard Aboba (IEEE liaison manager for 
the IETF) and the IEEE 802 leadership.  An rbridge (AKA TRILL) 
tutorial was also held at an IEEE 802 plenary.

The IEEE is developing a solution for shortest-path bridging, an 
(R)STP approach being developed in IEEE 802.1.  We were quite 
concerned about the potential for conflict between the TRILL work and 
the IEEE 802.1 work, and that was discussed via e-mail and on the 
call.  In the end, we concluded that a link-state-based approach will 
have different applicability than an (R)STP-based approach, and there 
has even some interest in a link-state-based approach from other 
parts of IEEE 802.

We also discussed where this work would best be housed -- in the 
IETF, in the iEEE or as a joint activity.  We don't have any 
mechanism for joint activities with the IEEE, and that option was 
quickly dismissed.  We understand that this is close to the line 
between the two organizations, but the conclusion of our discussions 
was that the development of a link-state-based Ethernet routing 
mechanism is better done in the IETF than in the IEEE.  The IEEE 
leadership did not object to the IETF pursuing this work.

The IEEE 802.1 technical leaders (Mick Seaman and Norm Finn) 
suggested that this work should be review by IEEE 802.1 for 
compliance with the Ethernet service model, and the charter includes 
a request for a formal liaison relationship with IEEE 802.1 for this 
purpose.  It has been pointed out that the purpose of the liaison 
relationship is not clear enough in the current charter, and we will 
be modifying the charter to add explicit IEEE 802.1 review milestones 
for both the architecture document and the specification.

Please let me know if you have any further questions.  The IESG will 
be making a decision on this charter at our telechat this Thursday 
(June 23rd), so if you have an opinion about whether or not we should 
charter this WG in the IETF, please send your comments to the IESG at 
iesg@ietf.org.  We are interested in hearing from folks who do want 
this work charted (especially from folks who are willing to invest 
time to make this happen), as well as from folks who have objections 
to chartering the group.

Thanks,
Margaret



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Wed Jun 22 10:38:52 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17512
	for <routing-discussion-archive@ietf.org>; Wed, 22 Jun 2005 10:38:52 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl6lb-00020Z-OK
	for routing-discussion-archive@ietf.org; Wed, 22 Jun 2005 11:03:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl6Im-0007vz-Nt; Wed, 22 Jun 2005 10:34:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl2yR-00077O-6s; Wed, 22 Jun 2005 07:00:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA24444;
	Wed, 22 Jun 2005 06:59:34 -0400 (EDT)
Received: from mtagate4.uk.ibm.com ([195.212.29.137])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl3LL-0002xM-2p; Wed, 22 Jun 2005 07:24:32 -0400
Received: from d06nrmr1407.portsmouth.uk.ibm.com
	(d06nrmr1407.portsmouth.uk.ibm.com [9.149.38.185])
	by mtagate4.uk.ibm.com (8.12.10/8.12.10) with ESMTP id j5MAxLe4274900; 
	Wed, 22 Jun 2005 10:59:21 GMT
Received: from d06av04.portsmouth.uk.ibm.com (d06av04.portsmouth.uk.ibm.com
	[9.149.37.216])
	by d06nrmr1407.portsmouth.uk.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id
	j5MAxLG6264646; Wed, 22 Jun 2005 11:59:21 +0100
Received: from d06av04.portsmouth.uk.ibm.com (loopback [127.0.0.1])
	by d06av04.portsmouth.uk.ibm.com (8.12.11/8.13.3) with ESMTP id
	j5MAxKwb012581; Wed, 22 Jun 2005 11:59:20 +0100
Received: from mail-gw3.hursley.ibm.com (mail-gw3.hursley.ibm.com
	[9.20.131.251])
	by d06av04.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id
	j5MAxKOc012560; Wed, 22 Jun 2005 11:59:20 +0100
Received: from [9.20.136.27] (helo=sp15en17.hursley.ibm.com)
	by mail-gw3.hursley.ibm.com with esmtp (Exim 4.50)
	id 1Dl2wx-0001We-U9; Wed, 22 Jun 2005 11:59:19 +0100
Received: from zurich.ibm.com (sig-9-145-134-171.de.ibm.com [9.145.134.171])
	by sp15en17.hursley.ibm.com (AIX5.1/8.11.6p2/8.11.0) with SMTP id
	j5MAxJo157738; Wed, 22 Jun 2005 11:59:19 +0100
Message-ID: <42B94484.5070806@zurich.ibm.com>
Date: Wed, 22 Jun 2005 12:59:16 +0200
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.6) Gecko/20040113
X-Accept-Language: en, fr, de
MIME-Version: 1.0
To: Susan Hares <shares@nexthop.com>
References: <BE36D687C8CBFA4AB76F5CD3E3C0FB4E0402B129@aa-exchange.corp.nexthop.com>
In-Reply-To: <BE36D687C8CBFA4AB76F5CD3E3C0FB4E0402B129@aa-exchange.corp.nexthop.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 22 Jun 2005 10:34:01 -0400
Cc: Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org, iesg@ietf.org,
        routing-discussion@ietf.org, rtg-chairs@ietf.org
Subject: Re: Fwd: Re: WG Review: Transparent Interconnection of Lots of	Links
 (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Content-Transfer-Encoding: 7bit

I can't speak to past events, but in this case there has been
substantial discusssion with IEEE and I don't think there is any
disturbance to the addressing "rule" that you cite. But the
skill set for this particular work is in the IETF. Nobody
denies that it's in the grey area where the question of scope
can be discussed endlessly, but the intention is now to decide
quickly, since the proponents have been more than patient.

    Brian

Susan Hares wrote:
> Margaret:
> 
> The key point is we want to ship product with standardization.
> (A good thing for all of us (IMHO).)
> 
> The rules used to be clear:
> 
> MAC address = IEEE
> IP address/Label = IETF.
> 
> If we are changing the rules, we need to be clear that we are changing
> the rules clearly.  Tony notes where the change in the rules didn't
> match.
> 
> You worked hard to make sure we had IETF consistency.  It would be
> helpful to make sure we have the same for IEEE/IETF consistency.
> 
> Many thanks,
> 
> Sue Hares
> 
> -----Original Message-----
> From: Tony Li [mailto:tony.li@tony.li] 
> Sent: Tuesday, June 21, 2005 1:16 PM
> To: Margaret Wasserman
> Cc: Alex Zinin; rtg-dir@ietf.org; rtg-chairs@ietf.org;
> routing-discussion@ietf.org; Susan Hares; iesg@ietf.org
> Subject: Re: Fwd: Re: WG Review: Transparent Interconnection of Lots of
> Links (trill)
> 
> 
> Margaret,
> 
> Thanks for your response.  IESG cc'ed per your request.
> 
> 
>>Please let me know if you have any further questions.  The IESG will
> 
> be
> 
>>making a decision on this charter at our telechat this Thursday (June
>>23rd), so if you have an opinion about whether or not we should
> 
> charter
> 
>>this WG in the IETF, please send your comments to the IESG at
>>iesg@ietf.org.  We are interested in hearing from folks who do want
> 
> this
> 
>>work charted (especially from folks who are willing to invest time to
>>make this happen), as well as from folks who have objections to
>>chartering the group.
> 
> 
> While I have no objection to chartering this group, I'm left scratching
> my head in wonder, trying to find the consistency between accepting this
> work and the previous decision to reject the IS-IS work on jumbo frames.
>  You may recall that the opinion at the time was that the work would
> step on IEEE toes and therefore the work was halted.  The IEEE chooses
> not to endorse jumbo frames, so in some sense there is no
> 'standardization' to be done.  Vendors, however, continue to ship
> running code for jumbo frames.  And there is no agreement for IS-IS
> operation in such situations.
> 
> IMHO, the IETF needs to re-examine its goals and operations in this
> regard.  What used to be an organization that was about standardizing
> de-facto standards is now engaged in politicking at the expense of
> technology.  We claim to eschew kings and voting, but we seem to be
> engaged in SDO diplomacy at the expense of code, users, and the
> Internet.  Does that seem right to you?
> 
> Regards,
> Tony Li
> 
> 
> 


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Wed Jun 22 10:42:40 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17995
	for <routing-discussion-archive@ietf.org>; Wed, 22 Jun 2005 10:42:40 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl6pH-00029I-RF
	for routing-discussion-archive@ietf.org; Wed, 22 Jun 2005 11:07:40 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl6In-0007wn-LY; Wed, 22 Jun 2005 10:34:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl5Fi-0006id-4z; Wed, 22 Jun 2005 09:26:50 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08484;
	Wed, 22 Jun 2005 09:25:10 -0400 (EDT)
Received: from auds951.usa.alcatel.com ([143.209.238.80])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl5cD-0007pp-SF; Wed, 22 Jun 2005 09:50:09 -0400
Received: from dh029172.ahqps.alcatel.fr (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.12.10/8.12.10) with ESMTP id
	j5MDOugJ003097; Wed, 22 Jun 2005 08:24:56 -0500 (CDT)
Date: Wed, 22 Jun 2005 06:24:51 -0700
From: Alex Zinin <alex.zinin@alcatel.com>
X-Priority: 3 (Normal)
Message-ID: <79728562.20050622062451@alcatel.com>
To: Margaret Wasserman <margaret@thingmagic.com>
In-Reply-To: <p06200783bedf0dc6cdad@[10\.0\.0\.171]>
References: <BE36D687C8CBFA4AB76F5CD3E3C0FB4E0402B129@aa-exchange.corp.nexthop.com>
	<42B94484.5070806@zurich.ibm.com>
	<070101c57725$1ca07420$7f849ed9@Puppy>
	<p06200783bedf0dc6cdad@[10.0.0.171]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 22 Jun 2005 10:34:01 -0400
Cc: Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org, iesg@ietf.org,
        routing-discussion@ietf.org, rtg-chairs@ietf.org,
        Adrian Farrel <adrian@olddog.co.uk>,
        Brian E Carpenter <brc@zurich.ibm.com>,
        Susan Hares <shares@nexthop.com>
Subject: Re: Fwd: Re: WG Review: Transparent Interconnection of Lots of
	Links (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Alex Zinin <alex.zinin@alcatel.com>
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Content-Transfer-Encoding: 7bit

Sorry for a dry reply--traveling, in meetings.

As Margaret said, the IESG didn't have an agreement on this.

I personally believe the expertise required for TRILL is in RTG. The
question of whether the WG should be formed has been dominating the
discussion though.

-- 
Alex

Wednesday, June 22, 2005, 5:57:27 AM, Margaret Wasserman wrote:

> Hi Adrian,

> At 1:22 PM +0100 6/22/05, Adrian Farrel wrote:
>>I think the skill-set to which Brian refers is link state routing. (Care
>>to confirm, Brian?)

> Yes, expertise in link-state routing is certainly one reason why this 
> work could be seen as more in-scope for the IETF than for the IEEE. 
> Also, frankly, there is interest in the IETF in doing this work (a 
> link-state-based Ethernet routing solution), while the IEEE is 
> continuing to pursue (R)STP-based approaches.

>>If so, why is this WG targeted at the Internet Area not the Routing area?

> This questions has been discussed in the IESG, as well, and we did 
> not have 100% agreement regarding the area in which this work belongs.

> Personally, I think that TRILL is a better fit for the Internet area, 
> and I will explain why...

> Traditionally, the division between the Internet area and the Routing 
> area has been that the Routing area deals with protocols that 
> distribute routing information (routes/labels) and the Internet area 
> has been responsible for the forwarding behaviour and encapsulation 
> mechanisms that make use of that information.

> The TRILL charter maintains that split -- any work on the routing 
> protocols themselves would be done in the routing area, while the 
> encapsulation/forwarding mechanism would be developed in the Internet 
> area.

> Perhaps you have a different model of the division between the 
> Routing and Internet areas that makes you think otherwise?

> The IESG discussed this issue several months ago.  We agreed that 
> this work is close to the line between Internet and Routing, but we 
> reached an agreement that it would best be placed in the Internet 
> area, with the understanding that we would appoint a technical 
> advisor and a WG co-chair with routing expertise.  BIll Fenner 
> volunteered to be the Technical Advisor, and Bill and Alex took an 
> action item to return with a list of potential co-chairs.

> Ultimately, I am not sure that it matters all that much which area 
> this work is done in, since it will require expertise and involvement 
> from both areas in order to succeed.

> Margaret






_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Wed Jun 22 10:43:02 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18072
	for <routing-discussion-archive@ietf.org>; Wed, 22 Jun 2005 10:43:02 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl6pd-0002Ak-Lw
	for routing-discussion-archive@ietf.org; Wed, 22 Jun 2005 11:08:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl6Io-0007xd-9J; Wed, 22 Jun 2005 10:34:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl5jM-0003Q9-6u; Wed, 22 Jun 2005 09:57:28 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12039;
	Wed, 22 Jun 2005 09:57:22 -0400 (EDT)
Received: from syd-iport-1.cisco.com ([64.104.193.196])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl67Q-0000az-3V; Wed, 22 Jun 2005 10:22:21 -0400
Received: from syd-core-1.cisco.com (64.104.193.198)
	by syd-iport-1.cisco.com with ESMTP; 23 Jun 2005 00:21:57 +1000
Received: from cisco.com (cfcentral.cisco.com [64.101.210.32])
	by syd-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j5MDuS91009751; 
	Wed, 22 Jun 2005 23:56:30 +1000 (EST)
Received: (from wardd@localhost)
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id IAA28900;
	Wed, 22 Jun 2005 08:56:59 -0500 (CDT)
Date: Wed, 22 Jun 2005 08:56:59 -0500
From: David Ward <dward@cisco.com>
To: Margaret Wasserman <margaret@thingmagic.com>
Message-ID: <20050622085659.V23594@cfcentral.cisco.com>
References: <BE36D687C8CBFA4AB76F5CD3E3C0FB4E0402B129@aa-exchange.corp.nexthop.com>
	<42B94484.5070806@zurich.ibm.com>
	<070101c57725$1ca07420$7f849ed9@Puppy>
	<p06200783bedf0dc6cdad@[10.0.0.171]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <p06200783bedf0dc6cdad@[10.0.0.171]>;
	from margaret@thingmagic.com on Wed, Jun 22, 2005 at 08:57:27AM
	-0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
X-Mailman-Approved-At: Wed, 22 Jun 2005 10:34:01 -0400
Cc: Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org, iesg@ietf.org,
        routing-discussion@ietf.org, rtg-chairs@ietf.org,
        Adrian Farrel <adrian@olddog.co.uk>,
        Brian E Carpenter <brc@zurich.ibm.com>,
        Susan Hares <shares@nexthop.com>
Subject: Re: Fwd: Re: WG Review: Transparent Interconnection of Lots of
	Links (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8

AFAIK, the only place that "routing L2" in a protocol has been 
drafted is in ISIS. We wrote to draft to show that it was possible and
to think through the protocol implications (how to reduce flooding, spf
churn, layout the packet format) of what was even feasible.  

The WG will not accept it as a WG item until all of this has been resolved.

-DWard


On Wed, Jun 22, 2005 at 08:57:27AM -0400, Margaret Wasserman wrote:
> 
> Hi Adrian,
> 
> At 1:22 PM +0100 6/22/05, Adrian Farrel wrote:
> >I think the skill-set to which Brian refers is link state routing. (Care
> >to confirm, Brian?)
> 
> Yes, expertise in link-state routing is certainly one reason why this 
> work could be seen as more in-scope for the IETF than for the IEEE. 
> Also, frankly, there is interest in the IETF in doing this work (a 
> link-state-based Ethernet routing solution), while the IEEE is 
> continuing to pursue (R)STP-based approaches.
> 
> >If so, why is this WG targeted at the Internet Area not the Routing area?
> 
> This questions has been discussed in the IESG, as well, and we did 
> not have 100% agreement regarding the area in which this work belongs.
> 
> Personally, I think that TRILL is a better fit for the Internet area, 
> and I will explain why...
> 
> Traditionally, the division between the Internet area and the Routing 
> area has been that the Routing area deals with protocols that 
> distribute routing information (routes/labels) and the Internet area 
> has been responsible for the forwarding behaviour and encapsulation 
> mechanisms that make use of that information.
> 
> The TRILL charter maintains that split -- any work on the routing 
> protocols themselves would be done in the routing area, while the 
> encapsulation/forwarding mechanism would be developed in the Internet 
> area.
> 
> Perhaps you have a different model of the division between the 
> Routing and Internet areas that makes you think otherwise?
> 
> The IESG discussed this issue several months ago.  We agreed that 
> this work is close to the line between Internet and Routing, but we 
> reached an agreement that it would best be placed in the Internet 
> area, with the understanding that we would appoint a technical 
> advisor and a WG co-chair with routing expertise.  BIll Fenner 
> volunteered to be the Technical Advisor, and Bill and Alex took an 
> action item to return with a list of potential co-chairs.
> 
> Ultimately, I am not sure that it matters all that much which area 
> this work is done in, since it will require expertise and involvement 
> from both areas in order to succeed.
> 
> Margaret

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Wed Jun 22 10:45:54 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18452
	for <routing-discussion-archive@ietf.org>; Wed, 22 Jun 2005 10:45:53 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl6sP-0002KC-HF
	for routing-discussion-archive@ietf.org; Wed, 22 Jun 2005 11:10:53 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl6PS-0000vx-2U; Wed, 22 Jun 2005 10:40:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl6PQ-0000vj-Bz; Wed, 22 Jun 2005 10:40:56 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17530;
	Wed, 22 Jun 2005 10:38:53 -0400 (EDT)
Received: from mtagate3.uk.ibm.com ([195.212.29.136])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl6lb-00020M-KO; Wed, 22 Jun 2005 11:03:53 -0400
Received: from d06nrmr1407.portsmouth.uk.ibm.com
	(d06nrmr1407.portsmouth.uk.ibm.com [9.149.38.185])
	by mtagate3.uk.ibm.com (8.12.10/8.12.10) with ESMTP id j5MEciGM390982; 
	Wed, 22 Jun 2005 14:38:44 GMT
Received: from d06av04.portsmouth.uk.ibm.com (d06av04.portsmouth.uk.ibm.com
	[9.149.37.216])
	by d06nrmr1407.portsmouth.uk.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id
	j5MEciG6229114; Wed, 22 Jun 2005 15:38:44 +0100
Received: from d06av04.portsmouth.uk.ibm.com (loopback [127.0.0.1])
	by d06av04.portsmouth.uk.ibm.com (8.12.11/8.13.3) with ESMTP id
	j5MEchGi023747; Wed, 22 Jun 2005 15:38:43 +0100
Received: from mail-gw3.hursley.ibm.com (mail-gw3.hursley.ibm.com
	[9.20.131.251])
	by d06av04.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id
	j5MEch8o023744; Wed, 22 Jun 2005 15:38:43 +0100
Received: from [9.20.136.27] (helo=sp15en17.hursley.ibm.com)
	by mail-gw3.hursley.ibm.com with esmtp (Exim 4.50)
	id 1Dl6NH-0005di-NM; Wed, 22 Jun 2005 15:38:43 +0100
Received: from zurich.ibm.com (sig-9-146-217-118.de.ibm.com [9.146.217.118])
	by sp15en17.hursley.ibm.com (AIX5.1/8.11.6p2/8.11.0) with SMTP id
	j5MEcho93782; Wed, 22 Jun 2005 15:38:43 +0100
Message-ID: <42B977EF.3060308@zurich.ibm.com>
Date: Wed, 22 Jun 2005 16:38:39 +0200
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.6) Gecko/20040113
X-Accept-Language: en, fr, de
MIME-Version: 1.0
To: Margaret Wasserman <margaret@thingmagic.com>
References: <BE36D687C8CBFA4AB76F5CD3E3C0FB4E0402B129@aa-exchange.corp.nexthop.com>
	<42B94484.5070806@zurich.ibm.com>
	<070101c57725$1ca07420$7f849ed9@Puppy>
	<p06200783bedf0dc6cdad@[10.0.0.171]>
In-Reply-To: <p06200783bedf0dc6cdad@[10.0.0.171]>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Content-Transfer-Encoding: 7bit
Cc: Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org, iesg@ietf.org,
        routing-discussion@ietf.org, rtg-chairs@ietf.org,
        Adrian Farrel <adrian@olddog.co.uk>, Susan Hares <shares@nexthop.com>
Subject: Re: Fwd: Re: WG Review: Transparent Interconnection of Lots of Links
 (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Content-Transfer-Encoding: 7bit

I concur with Margaret completely

    Brian

Margaret Wasserman wrote:
> 
> Hi Adrian,
> 
> At 1:22 PM +0100 6/22/05, Adrian Farrel wrote:
> 
>> I think the skill-set to which Brian refers is link state routing. (Care
>> to confirm, Brian?)
> 
> 
> Yes, expertise in link-state routing is certainly one reason why this 
> work could be seen as more in-scope for the IETF than for the IEEE. 
> Also, frankly, there is interest in the IETF in doing this work (a 
> link-state-based Ethernet routing solution), while the IEEE is 
> continuing to pursue (R)STP-based approaches.
> 
>> If so, why is this WG targeted at the Internet Area not the Routing area?
> 
> 
> This questions has been discussed in the IESG, as well, and we did not 
> have 100% agreement regarding the area in which this work belongs.
> 
> Personally, I think that TRILL is a better fit for the Internet area, 
> and I will explain why...
> 
> Traditionally, the division between the Internet area and the Routing 
> area has been that the Routing area deals with protocols that distribute 
> routing information (routes/labels) and the Internet area has been 
> responsible for the forwarding behaviour and encapsulation mechanisms 
> that make use of that information.
> 
> The TRILL charter maintains that split -- any work on the routing 
> protocols themselves would be done in the routing area, while the 
> encapsulation/forwarding mechanism would be developed in the Internet area.
> 
> Perhaps you have a different model of the division between the Routing 
> and Internet areas that makes you think otherwise?
> 
> The IESG discussed this issue several months ago.  We agreed that this 
> work is close to the line between Internet and Routing, but we reached 
> an agreement that it would best be placed in the Internet area, with the 
> understanding that we would appoint a technical advisor and a WG 
> co-chair with routing expertise.  BIll Fenner volunteered to be the 
> Technical Advisor, and Bill and Alex took an action item to return with 
> a list of potential co-chairs.
> 
> Ultimately, I am not sure that it matters all that much which area this 
> work is done in, since it will require expertise and involvement from 
> both areas in order to succeed.
> 
> Margaret
> 
> 
> 
> 


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Wed Jun 22 10:46:05 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18496
	for <routing-discussion-archive@ietf.org>; Wed, 22 Jun 2005 10:46:05 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl6sa-0002Lg-L2
	for routing-discussion-archive@ietf.org; Wed, 22 Jun 2005 11:11:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl6Il-0007uc-IE; Wed, 22 Jun 2005 10:34:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DkSdS-0003xk-BD; Mon, 20 Jun 2005 16:12:46 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06379;
	Mon, 20 Jun 2005 16:12:41 -0400 (EDT)
Received: from dyn50.sunlabs.com ([204.153.12.50] helo=mail-mta.sunlabs.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DkT1B-0004B7-Gf; Mon, 20 Jun 2005 16:37:17 -0400
Received: from mail.sunlabs.com ([152.70.2.186]) by mail-mta.sfvic.sunlabs.com
	(Sun Java System Messaging Server 6.1 HotFix 0.02 (built Aug 25
	2004))
	with ESMTP id <0IIE0023OG4R0100@mail-mta.sfvic.sunlabs.com>; Mon,
	20 Jun 2005 13:12:27 -0700 (PDT)
Received: from sun.com ([129.150.31.236])
	by mail.sunlabs.com (Sun Java System Messaging Server 6.1 HotFix 0.02
	(built
	Aug 25 2004)) with ESMTPSA id <0IIE00568G4Q1EX3@mail.sunlabs.com>; Mon,
	20 Jun 2005 13:12:27 -0700 (PDT)
Date: Mon, 20 Jun 2005 13:12:27 -0700
From: Radia Perlman <Radia.Perlman@sun.com>
In-reply-to: <42B721C0.5010808@sun.com>
To: Radia Perlman <Radia.Perlman@sun.com>
Message-id: <42B7232B.3010506@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=windows-1252; format=flowed
Content-transfer-encoding: QUOTED-PRINTABLE
X-Accept-Language: en-us, en
References: <BE36D687C8CBFA4AB76F5CD3E3C0FB4E0402AF97@aa-exchange1.corp.nexthop.com>
	<42B721C0.5010808@sun.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4.1)
	Gecko/20031008
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 27ec2ff0f5c3b18b49c722f4f1748838
Content-Transfer-Encoding: QUOTED-PRINTABLE
X-Mailman-Approved-At: Wed, 22 Jun 2005 10:34:01 -0400
Cc: Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org, ewgray@GraIyMage.com,
        routing-discussion@ietf.org, rtg-chairs@ietf.org,
        Susan Hares <shares@nexthop.com>
Subject: Re: WG Review: Transparent Interconnection of Lots of Links (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 249cd1efd3d5e0d09114abe826a41235
Content-Transfer-Encoding: QUOTED-PRINTABLE

Oh and one other thing...things like proxy ND and passing around (lay=
er=20
3, layer 2) pairs to
facilitate it, are something else that are not specific to any=20
particular layer 2 technology.

Radia



Radia Perlman wrote:

> Yes. This has been discussed with IEEE. I even gave a tutorial ther=
e=20
> on TRILL at the
> last IEEE, both at a general tutorial slot and at the mesh group=
=20
> (invited by the chair
> of that group, Don Eastlake). It got a very friendly reception, by =
the=20
> way.
>
> There are some people in the wireless mesh group who
> have since mentioned to me that they are interested
> in proposing a solution like this within the mesh group.
> And that would be good. But this technology is not specific to any=
=20
> particular
> layer 2 technology, and certainly not limited to wireless. So it=
=20
> should be standardized in something
> that is layer 2 agnostic. It could also be used in other places, of=
=20
> course, and if multiple WGs are
> working on similar things, it is good if they cooperate and liase (=
is=20
> that a word?) so that technology
> works well together, and even better yet, if it converges towards t=
he=20
> same design. I believe
> the intention of all concerned is that all the WGs that might be=
=20
> interested and might
> be helpful have liason relationships.
>
> Radia
>
>
>
> Susan Hares wrote:
>
>> Eric and Tony:
>>
>> See my comments about Wireless Mesh proposal an Wi-Mesh alliance I=
=92m=20
>> a part of submitted 6/15/05 to the 802.11s.
>>
>> Radia or others may know more about 802.1 since they have more=
=20
>> history with IEEE.
>>
>> Sue
>>
>> ------------------------------------------------------------------=
------
>>
>> *From:* Eric W Gray [mailto:ewgray2k@netscape.net]
>> *Sent:* Monday, June 20, 2005 2:45 PM
>> *To:* Tony Li
>> *Cc:* Susan Hares; Alex Zinin; rtg-dir@ietf.org;=20
>> routing-discussion@ietf.org; rtg-chairs@ietf.org
>> *Subject:* Re: WG Review: Transparent Interconnection of Lots of=
=20
>> Links (trill)
>>
>> Tony,
>>
>> No disagreement from me. Perhaps the next obvious question is - ha=
s=20
>> anyone taken this to the
>> IEEE?
>>
>> --=20
>> Eric
>>
>> Tony Li wrote:
>>
>>
>>
>> In other instances, when proposals were IEEE'ish, we were directed=
 to
>>
>> take them to the IEEE.
>>
>>
>>
>> Tony
>>
>>
>>
>>
>>
>> Eric W Gray wrote:
>>
>> =20
>>
>>> Sue,
>>>
>>>
>>>
>>>    The trouble with obvious questions is that everybody assumes t=
hey've
>>>
>>> been  asked already.
>>>
>>> Now this question has been asked at least once, for sure.  :-)
>>>
>>>
>>>
>>>    From the charter attached in Alex's previous message, the purp=
ose is
>>>
>>> to "route" Ethernet
>>>
>>> Frames. Quote:
>>>
>>>
>>>
>>> The TRILL WG will design a solution for shortest-path frame routi=
ng in
>>>
>>> multi-hop IEEE 802.1 Ethernet networks with arbitrary topologies,
>>>
>>> using the link-state routing protocol technology.
>>>
>>>
>>>
>>> Since it is clear that at least some people are not satisfied wit=
h the
>>>
>>> 802.1 approach (perhaps
>>>
>>> because of the relative inefficiency associated with completely u=
nused
>>>
>>> high capacity links), I
>>>
>>> assume you mean to ask "why is it not IEEE" - rather than "why is=
 it=20
>>> not
>>>
>>> 802.1".
>>>
>>>
>>>
>>>    I believe that is a very good question.  I know of no very goo=
d
>>>
>>> reason why the IEEE might
>>>
>>> not specify how to use an OSPF-like routing protocol to fulfill t=
he=20
>>> role
>>>
>>> previously handled by
>>>
>>> Spanning Tree Protocol. Perhaps the only reason why it is being
>>>
>>> discussed here is that it might
>>>
>>> be better - for implementers - if the protocol used was more than
>>>
>>> "OSPF-like."
>>>
>>>
>>>
>>> --=20
>>>
>>> Eric
>>>
>>>
>>>
>>> shares@nexthop.com <mailto:shares@nexthop.com> wrote:
>>>
>>>
>>>
>>>  =20
>>>
>>>> Why are we doing this?  Is it IP or is it Frames?
>>>>
>>>> If it is Frames, why is it not 802.1 - etc?
>>>>
>>>>
>>>> Sue Hares
>>>>
>>>>
>>>>
>>>> -----Original Message-----
>>>>
>>>> From: Alex Zinin [mailto:zinin@psg.com]
>>>> Sent: Thursday, June 16, 2005 10:00 PM
>>>>
>>>> To: routing-discussion@ietf.org <mailto:routing-discussion@ietf.=
org>
>>>>
>>>> Cc: rtg-dir@ietf.org <mailto:rtg-dir@ietf.org>; rtg-chairs@ietf.=
org=20
>>>> <mailto:rtg-chairs@ietf.org>
>>>>
>>>> Subject: Fwd: WG Review: Transparent Interconnection of Lots of =
Links
>>>>
>>>> (trill)
>>>>
>>>>
>>>>
>>>> Since the second BOF on this topic was inconclusive regarding=
=20
>>>> community
>>>>
>>>> support, the IESG is reevaluating the community consensus on whe=
ther a
>>>>
>>>> WG
>>>>
>>>> should be formed or not.
>>>>
>>>>
>>>>
>>>> If you have input on this, positive or negative, please send it =
to
>>>>
>>>> iesg@ietf.org <mailto:iesg@ietf.org>.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>    =20
>>>
>>> -----------------------------------------------------------------=
-------=20
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>>
>>> routing-discussion mailing list
>>>
>>> routing-discussion@ietf.org <mailto:routing-discussion@ietf.org>
>>>
>>> https://www1.ietf.org/mailman/listinfo/routing-discussion
>>>
>>>  =20
>>
>>
>>
>>
>>
>>
>>
>> =20
>>
>



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Wed Jun 22 12:19:28 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28241
	for <routing-discussion-archive@ietf.org>; Wed, 22 Jun 2005 12:19:28 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl8Kz-0005nT-OZ
	for routing-discussion-archive@ietf.org; Wed, 22 Jun 2005 12:44:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl7w1-00062D-Sk; Wed, 22 Jun 2005 12:18:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Dl7vz-00061w-RL
	for routing-discussion@megatron.ietf.org;
	Wed, 22 Jun 2005 12:18:39 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28213
	for <routing-discussion@ietf.org>; Wed, 22 Jun 2005 12:18:36 -0400 (EDT)
Received: from relay00.pair.com ([209.68.1.20] helo=relay.pair.com)
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1Dl8K8-0005l5-Ry
	for routing-discussion@ietf.org; Wed, 22 Jun 2005 12:43:37 -0400
Received: (qmail 46153 invoked from network); 22 Jun 2005 16:18:31 -0000
Received: from unknown (HELO workhorse.faster-light.net) (unknown)
	by unknown with SMTP; 22 Jun 2005 16:18:31 -0000
X-pair-Authenticated: 69.37.59.162
Received: from workhorse.faster-light.net (localhost.faster-light.net
	[127.0.0.1])
	by workhorse.faster-light.net (8.12.11/8.12.11) with ESMTP id
	j5MGIB2V039677; Wed, 22 Jun 2005 12:18:11 -0400 (EDT)
	(envelope-from curtis@workhorse.faster-light.net)
Message-Id: <200506221618.j5MGIB2V039677@workhorse.faster-light.net>
To: Brian E Carpenter <brc@zurich.ibm.com>
In-reply-to: Your message of "Wed, 22 Jun 2005 12:59:16 +0200."
	<42B94484.5070806@zurich.ibm.com> 
Date: Wed, 22 Jun 2005 12:18:11 -0400
From: Curtis Villamizar <curtis@faster-light.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290
Cc: Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org, iesg@ietf.org,
        routing-discussion@ietf.org, rtg-chairs@ietf.org,
        Susan Hares <shares@nexthop.com>
Subject: Re: Fwd: Re: WG Review: Transparent Interconnection of Lots of
	Links (trill) 
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: curtis@faster-light.net
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c


In message <42B94484.5070806@zurich.ibm.com>
Brian E Carpenter writes:
>  
> I can't speak to past events, but in this case there has been
> substantial discusssion with IEEE and I don't think there is any
> disturbance to the addressing "rule" that you cite. But the
> skill set for this particular work is in the IETF. Nobody
> denies that it's in the grey area where the question of scope
> can be discussed endlessly, but the intention is now to decide
> quickly, since the proponents have been more than patient.
>  
>     Brian


Brian,

[Appology in advance for the length of this.]

One of the conclusions that could potentially come out of a group that
has more expertice in this area is that the whole idea of bridging in
anything but a very small scale and trivial topology in general is a
bad idea and therefore this work and any further spanning tree work is
best not pursued anywhere.  Others have mentioned that IETF tends to
standardize those things that have proven useful rather than push
ideas upon user communities (Tony, others).  [insert mantra on running
code and all that.]

Its clear that there is no interest in providers in bridging
solutions.  There have been enough failures to keep most people from
further attempts, ranging from the bridging done in regional acedemic
networks in the late 1980s to attempts to use IP at the edges and ATM
in the middle, to the complete failure in the market of ATM approaches
such as RFC1577, NHRP, MPOA.

Bridging seems to be a preferred solution in enterprise.  A decade ago
there was a good reason to do so.  If you moved a box from one
ethernet segment to another you had to change its IP address.  This
was a pain for personal workstations (whether Sun, Linux, PC, MAC,
whatever) which are very numerous.  DHCP has changed that.  Only
machines providing a service need a fixed address and a DNS mapping to
that address.  Even though DHCP is universally available and widely
deployed in enterprise, enterprise hasn't caught on that the reliance
on bridging is no longer in their best interest (in fact the opposite
is true since diagnosing routing problems is much easier).

The remaining problem for enterprise is moving the servers.  Most
enterprise IT departments can deal with renumbering a server if they
have to do so to accomodate a physical move and the better ones
configure a whole new server and have it running and then just switch
the DNS entry (giving it a short TTL 24 hours prior to the switch,
etc, etc) in addition to making the switch off hours.

Mobility offers a new problem.  It would be nice to be able to keep
your laptop running and move about within wireless space with any
changes to addressing made transparently.  The best way to do this
involves decoupling the destination address of the box from the
interface address.  Loopback devices and interface aliases are nothing
new to routers and Linux and *ix systems.

A better solution to the problem of mobility of small devices like IP
phones and laptops might be entirely at layer 3 using the above
toolbox (microsoft can add loopbacks and aliases if they don't support
such a capability).  A limited initial solution might be as simple as
having the abiliby for the OS to bind to the loopback on outbound
connections by default rather than the interface (this is solved at
the application layer in some router code and kerberos implementations
and other things that providers have "fixed" for dual homing and
recompiled) and tracking the host route to the loopback within a
limited set of wireless access points (for example all those at a
given IETF meeting).  This can be made general by having DHCP offer a
preferred loopback address for the device to use.

Solving the problem of mobility between adjacent domains isn't much
harder.  The problem with switching the loopback device is that with
current OS all TCP connections stop working.  For short lived
protocols such as SMTP or POP and HTTP this is less of a problem than
for long lived connections such as SSH's slogin service (no one really
uses telnet, I hope).  For the short lived connections allowing the
loopback of a geographicly adjacent domain might provide a sufficient
grace period on the transition to solve the problem.  It would be best
if the OS could support a preferred address on the loopback and an
alias on the loopback to support the TCP connections still using the
old address.

Beyond that there would need to be a way to change the TCP address of
one end of a TCP connection.  This would have to be solved in TCP
itself.  There is currently no header option for "accept alternate
address" and "drop address" in TCP but having that would be
sufficient.  It would also open a new opportunity for abuse in TCP
connections with no cryptographic integrety check so the security
section of such a draft would have to be very non-empty.  It might be
that we'd have to restrict use of this option to TCP connections with
some form of cryptographic check (but I digress).

Ultimately one should be able to drive (or fly, or bicycle, or
whatever) across a continent with a laptop open and keep the same TCP
connection open the whole time.  The solution might be as simple as
some OS enhancements and enhancements to DHCP and a TCP option.
Please note that a spanning tree or link state solution isn't going to
get us there and therefore is a limited temporary solution.

There are sure to be other less used non-TCP protocols that are
affected.  Just like with NAT eventually this would be resolved.  For
example, a SIP enhancement might be needed to accomodate connection to
a phone that is moving about in the address space.

In the past the BSD folks would go to it, we'd play with it at IETF,
some providers would start to support it if that was needed, we'd
write an internet-draft which would become an RFC and 5-10 years later
deployment would be widespread.  It worked for DHCP.  It worked (for
some limited value of worked) for multicast.  The IETF often works
differently these days, but that doesn't mean that running code
wouldn't help matters.

Then again, the conclusions of this discussion might be quite
different but thats my thoughts on the topic.

Curtis

ps - Anyone seriously interested in these ideas please send private
email (anyone at ISC interested?) or at least change the subject.
This is sort of off topic or mostly a digression but I felt that if I
were saying "bad solution" in order to be constructive I needed to
outline a better solution.

pps - In the past work on "bad solutions" were referred to ITU or
other organization though I'm not sure that practice is codified in
any IESG policy.  I suspect a lot of the "send it to IEEE" might be
motivated by the "bad solutions are out of scope for IETF" sentiment.
:-)

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Wed Jun 22 12:21:33 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28408
	for <routing-discussion-archive@ietf.org>; Wed, 22 Jun 2005 12:21:33 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl8Mw-0005qL-9o
	for routing-discussion-archive@ietf.org; Wed, 22 Jun 2005 12:46:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl7vq-0005wl-5T; Wed, 22 Jun 2005 12:18:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl7vo-0005wa-R7; Wed, 22 Jun 2005 12:18:29 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28195;
	Wed, 22 Jun 2005 12:18:14 -0400 (EDT)
Received: from dns.nexthop.com ([65.247.36.216] helo=aa-mx1.nexthop.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl8Jm-0005kU-MK; Wed, 22 Jun 2005 12:43:16 -0400
Received: from localhost (localhost [127.0.0.1])
	by aa-mx1.nexthop.com (Postfix) with ESMTP
	id 0B75C2D5397; Wed, 22 Jun 2005 12:18:03 -0400 (EDT)
Received: from aa-mx1.nexthop.com ([127.0.0.1])
	by localhost (aa-mx1.nexthop.com [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id 95327-01-75; Wed, 22 Jun 2005 12:18:01 -0400 (EDT)
Received: from BOS-exch01.corp.nexthop.com (unknown [192.168.11.20])
	by aa-mx1.nexthop.com (Postfix) with ESMTP
	id 7ADF22D5050; Wed, 22 Jun 2005 11:57:54 -0400 (EDT)
Received: from aa-exchange1.corp.nexthop.com ([65.247.36.233]) by
	BOS-exch01.corp.nexthop.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Jun 2005 11:57:54 -0400
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Date: Wed, 22 Jun 2005 11:57:51 -0400
Message-ID: <BE36D687C8CBFA4AB76F5CD3E3C0FB4E0402B26D@aa-exchange.corp.nexthop.com>
Thread-Topic: Re: WG Review: Transparent Interconnection of Lots of Links
	(trill)
thread-index: AcV3OpUk/NpWbBtnRwC1Lx3LU6q7fgABy7xA
From: "Susan Hares" <shares@nexthop.com>
To: "Margaret Wasserman" <margaret@thingmagic.com>,
        "Tony Li" <tony.li@tony.li>, "Alex Zinin" <zinin@psg.com>,
        <rtg-dir@ietf.org>, <rtg-chairs@ietf.org>,
        <routing-discussion@ietf.org>
X-OriginalArrivalTime: 22 Jun 2005 15:57:54.0176 (UTC)
	FILETIME=[2676C800:01C57743]
X-Virus-Scanned: by amavisd-new at nexthop.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Content-Transfer-Encoding: quoted-printable
Subject: RE: Re: WG Review: Transparent Interconnection of Lots of Links
	(trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Content-Transfer-Encoding: quoted-printable

I believe the expertise for link-state protocols is in the routing area.

Sue Hares

-----Original Message-----
From: routing-discussion-bounces@ietf.org
[mailto:routing-discussion-bounces@ietf.org] On Behalf Of Margaret
Wasserman
Sent: Tuesday, June 21, 2005 8:55 AM
To: Tony Li; Alex Zinin; rtg-dir@ietf.org; rtg-chairs@ietf.org;
routing-discussion@ietf.org; Susan Hares
Subject: Fwd: Re: WG Review: Transparent Interconnection of Lots of
Links (trill)


Hi All,

Erik forwarded this message to me, so that I could reply.  I used to=20
be on routing-discussion (at least I thought I was), but I don't seem=20
to be now, so please include me in any responses.

At 14:44:54 AM -0400 6/20/05, Eric W Gray wrote:
>Tony,
>
>     No disagreement from me.  Perhaps the next obvious question is -
has
>anyone taken this to the
>IEEE?

We have talked to the IEEE about this, and they are very aware of=20
this work.  There were several e-mail exchanges with IEEE 802 leaders=20
in response to the first charter that was circulated for external=20
review last November.  This lead to an e-mail discussion between IEEE=20
leadership and the IESG/IAB.  We then had a conference call between=20
the interested IESG folks, Bernard Aboba (IEEE liaison manager for=20
the IETF) and the IEEE 802 leadership.  An rbridge (AKA TRILL)=20
tutorial was also held at an IEEE 802 plenary.

The IEEE is developing a solution for shortest-path bridging, an=20
(R)STP approach being developed in IEEE 802.1.  We were quite=20
concerned about the potential for conflict between the TRILL work and=20
the IEEE 802.1 work, and that was discussed via e-mail and on the=20
call.  In the end, we concluded that a link-state-based approach will=20
have different applicability than an (R)STP-based approach, and there=20
has even some interest in a link-state-based approach from other=20
parts of IEEE 802.

We also discussed where this work would best be housed -- in the=20
IETF, in the iEEE or as a joint activity.  We don't have any=20
mechanism for joint activities with the IEEE, and that option was=20
quickly dismissed.  We understand that this is close to the line=20
between the two organizations, but the conclusion of our discussions=20
was that the development of a link-state-based Ethernet routing=20
mechanism is better done in the IETF than in the IEEE.  The IEEE=20
leadership did not object to the IETF pursuing this work.

The IEEE 802.1 technical leaders (Mick Seaman and Norm Finn)=20
suggested that this work should be review by IEEE 802.1 for=20
compliance with the Ethernet service model, and the charter includes=20
a request for a formal liaison relationship with IEEE 802.1 for this=20
purpose.  It has been pointed out that the purpose of the liaison=20
relationship is not clear enough in the current charter, and we will=20
be modifying the charter to add explicit IEEE 802.1 review milestones=20
for both the architecture document and the specification.

Please let me know if you have any further questions.  The IESG will=20
be making a decision on this charter at our telechat this Thursday=20
(June 23rd), so if you have an opinion about whether or not we should=20
charter this WG in the IETF, please send your comments to the IESG at=20
iesg@ietf.org.  We are interested in hearing from folks who do want=20
this work charted (especially from folks who are willing to invest=20
time to make this happen), as well as from folks who have objections=20
to chartering the group.

Thanks,
Margaret



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Wed Jun 22 12:26:47 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28889
	for <routing-discussion-archive@ietf.org>; Wed, 22 Jun 2005 12:26:47 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl8S0-00062t-6U
	for routing-discussion-archive@ietf.org; Wed, 22 Jun 2005 12:51:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl7za-0006eH-4u; Wed, 22 Jun 2005 12:22:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl7zY-0006dV-32; Wed, 22 Jun 2005 12:22:20 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28479;
	Wed, 22 Jun 2005 12:22:16 -0400 (EDT)
Received: from dns.nexthop.com ([65.247.36.216] helo=aa-mx1.nexthop.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl8Nh-0005sh-73; Wed, 22 Jun 2005 12:47:17 -0400
Received: from localhost (localhost [127.0.0.1])
	by aa-mx1.nexthop.com (Postfix) with ESMTP
	id 3A4B92D4FD5; Wed, 22 Jun 2005 12:22:10 -0400 (EDT)
Received: from aa-mx1.nexthop.com ([127.0.0.1])
	by localhost (aa-mx1.nexthop.com [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id 96352-02-47; Wed, 22 Jun 2005 12:22:06 -0400 (EDT)
Received: from BOS-exch01.corp.nexthop.com (unknown [192.168.11.20])
	by aa-mx1.nexthop.com (Postfix) with ESMTP
	id 799CE2D4AAE; Wed, 22 Jun 2005 12:02:00 -0400 (EDT)
Received: from aa-exchange1.corp.nexthop.com ([65.247.36.233]) by
	BOS-exch01.corp.nexthop.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Jun 2005 12:01:59 -0400
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Date: Wed, 22 Jun 2005 12:01:58 -0400
Message-ID: <BE36D687C8CBFA4AB76F5CD3E3C0FB4E0402B271@aa-exchange.corp.nexthop.com>
Thread-Topic: Fwd: Re: WG Review: Transparent Interconnection of Lots of	Links
	(trill)
thread-index: AcV3OtV3QBoyRP39TDeBul7X3zxPSwACGadg
From: "Susan Hares" <shares@nexthop.com>
To: "Brian E Carpenter" <brc@zurich.ibm.com>
X-OriginalArrivalTime: 22 Jun 2005 16:01:59.0980 (UTC)
	FILETIME=[B8F97EC0:01C57743]
X-Virus-Scanned: by amavisd-new at nexthop.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
Content-Transfer-Encoding: quoted-printable
Cc: Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org, iesg@ietf.org,
        routing-discussion@ietf.org, rtg-chairs@ietf.org
Subject: RE: Fwd: Re: WG Review: Transparent Interconnection of Lots
	of	Links (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5d7a7e767f20255fce80fa0b77fb2433
Content-Transfer-Encoding: quoted-printable

Brian:

Please substitute "rule of thumb" for "rule" in my previous message.
Also - IMHO: Quick decisions =3D good.=20

Sue

-----Original Message-----
From: routing-discussion-bounces@ietf.org
[mailto:routing-discussion-bounces@ietf.org] On Behalf Of Brian E
Carpenter
Sent: Wednesday, June 22, 2005 6:59 AM
To: Susan Hares
Cc: Alex Zinin; rtg-dir@ietf.org; iesg@ietf.org;
routing-discussion@ietf.org; rtg-chairs@ietf.org
Subject: Re: Fwd: Re: WG Review: Transparent Interconnection of Lots of
Links (trill)

I can't speak to past events, but in this case there has been
substantial discusssion with IEEE and I don't think there is any
disturbance to the addressing "rule" that you cite. But the
skill set for this particular work is in the IETF. Nobody
denies that it's in the grey area where the question of scope
can be discussed endlessly, but the intention is now to decide
quickly, since the proponents have been more than patient.

    Brian

Susan Hares wrote:
> Margaret:
>=20
> The key point is we want to ship product with standardization.
> (A good thing for all of us (IMHO).)
>=20
> The rules used to be clear:
>=20
> MAC address =3D IEEE
> IP address/Label =3D IETF.
>=20
> If we are changing the rules, we need to be clear that we are changing
> the rules clearly.  Tony notes where the change in the rules didn't
> match.
>=20
> You worked hard to make sure we had IETF consistency.  It would be
> helpful to make sure we have the same for IEEE/IETF consistency.
>=20
> Many thanks,
>=20
> Sue Hares
>=20
> -----Original Message-----
> From: Tony Li [mailto:tony.li@tony.li]=20
> Sent: Tuesday, June 21, 2005 1:16 PM
> To: Margaret Wasserman
> Cc: Alex Zinin; rtg-dir@ietf.org; rtg-chairs@ietf.org;
> routing-discussion@ietf.org; Susan Hares; iesg@ietf.org
> Subject: Re: Fwd: Re: WG Review: Transparent Interconnection of Lots
of
> Links (trill)
>=20
>=20
> Margaret,
>=20
> Thanks for your response.  IESG cc'ed per your request.
>=20
>=20
>>Please let me know if you have any further questions.  The IESG will
>=20
> be
>=20
>>making a decision on this charter at our telechat this Thursday (June
>>23rd), so if you have an opinion about whether or not we should
>=20
> charter
>=20
>>this WG in the IETF, please send your comments to the IESG at
>>iesg@ietf.org.  We are interested in hearing from folks who do want
>=20
> this
>=20
>>work charted (especially from folks who are willing to invest time to
>>make this happen), as well as from folks who have objections to
>>chartering the group.
>=20
>=20
> While I have no objection to chartering this group, I'm left
scratching
> my head in wonder, trying to find the consistency between accepting
this
> work and the previous decision to reject the IS-IS work on jumbo
frames.
>  You may recall that the opinion at the time was that the work would
> step on IEEE toes and therefore the work was halted.  The IEEE chooses
> not to endorse jumbo frames, so in some sense there is no
> 'standardization' to be done.  Vendors, however, continue to ship
> running code for jumbo frames.  And there is no agreement for IS-IS
> operation in such situations.
>=20
> IMHO, the IETF needs to re-examine its goals and operations in this
> regard.  What used to be an organization that was about standardizing
> de-facto standards is now engaged in politicking at the expense of
> technology.  We claim to eschew kings and voting, but we seem to be
> engaged in SDO diplomacy at the expense of code, users, and the
> Internet.  Does that seem right to you?
>=20
> Regards,
> Tony Li
>=20
>=20
>=20


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Wed Jun 22 12:27:50 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29098
	for <routing-discussion-archive@ietf.org>; Wed, 22 Jun 2005 12:27:50 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl8T5-00066K-4w
	for routing-discussion-archive@ietf.org; Wed, 22 Jun 2005 12:52:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl81v-00076o-Fr; Wed, 22 Jun 2005 12:24:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl81t-00076A-Cf; Wed, 22 Jun 2005 12:24:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28687;
	Wed, 22 Jun 2005 12:24:39 -0400 (EDT)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl8Py-0005wq-1O; Wed, 22 Jun 2005 12:49:40 -0400
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-3.cisco.com with ESMTP; 22 Jun 2005 09:24:25 -0700
X-IronPort-AV: i="3.93,221,1115017200"; 
	d="scan'208"; a="281780601:sNHT29574364"
Received: from cliff.cisco.com (cliff.cisco.com [171.69.11.141])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j5MGOHVX018662;
	Wed, 22 Jun 2005 09:24:17 -0700 (PDT)
Received: from [10.21.122.155] (sjc-vpn6-667.cisco.com [10.21.122.155]) by
	cliff.cisco.com (8.6.12/8.6.5) with ESMTP id JAA27195;
	Wed, 22 Jun 2005 09:24:16 -0700
Message-ID: <42B990B0.1060700@tony.li>
Date: Wed, 22 Jun 2005 09:24:16 -0700
From: Tony Li <tony.li@tony.li>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Margaret Wasserman <margaret@thingmagic.com>
References: <p0620074fbeddb701e9fe@[10.0.0.171]> <42B84B66.3050006@tony.li>
	<p06200781bedefae66141@[10.0.0.171]>
In-Reply-To: <p06200781bedefae66141@[10.0.0.171]>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: 7bit
Cc: Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org, iesg@ietf.org,
        routing-discussion@ietf.org, rtg-chairs@ietf.org, shares@nexthop.com
Subject: Re: Fwd: Re: WG Review: Transparent Interconnection of Lots of Links
 (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: 7bit


Hi Margaret,

>>  You may recall that the opinion at the time was that the work would
>> step on IEEE toes and therefore the work was halted.  The IEEE chooses
>> not to endorse jumbo frames, so in some sense there is no
>> 'standardization' to be done.  Vendors, however, continue to ship
>> running code for jumbo frames.  And there is no agreement for IS-IS
>> operation in such situations.
> 
> In the particular case of TRILL, we were concerned that the work might
> conflict with IEEE work, so we talked to the IEEE 802 leadership about
> it.  They did not express interest in chartering this work in the IEEE,
> and they did not object to chartering it in the IETF.
> 
> I am not quite sure what we would have done if the IEEE had said that
> they would not charter the work, but that they objected to the IETF
> chartering the work...  Luckily for me and the folks working on TRILL,
> we did not have to figure out what to do in that situation.


Given this, I would like to propose that we re-open the work on IS-IS
over jumbo frames.  Since the IEEE has clearly said that jumbo frames
are out of scope, they can hardly object to the IETF working on it.


> Ultimately, though, the best way to address this problem is not by
> trying to enforce a specific view of the IETF from the top down (which
> would defeat the whole purpose), but through communicating a different
> vision of the IETF and trying to get enough people to adopt that vision
> that it becomes the prevailing culture (again?).


Please see above.  We were stopped previously by the IESG adopting just
such a specific view about structured standards development and imposing
it from the top down.  You seem to indicate that the situation may have
changed and that the IESG may now be more amenable to a more pragmatic
approach.

Regards,
Tony

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Wed Jun 22 12:31:35 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29395
	for <routing-discussion-archive@ietf.org>; Wed, 22 Jun 2005 12:31:35 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl8Wi-0006G8-Th
	for routing-discussion-archive@ietf.org; Wed, 22 Jun 2005 12:56:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl88N-0001s1-MI; Wed, 22 Jun 2005 12:31:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl88L-0001ro-QA; Wed, 22 Jun 2005 12:31:26 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29373;
	Wed, 22 Jun 2005 12:31:19 -0400 (EDT)
Received: from dns.nexthop.com ([65.247.36.216] helo=aa-mx1.nexthop.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl8WS-0006FF-Cw; Wed, 22 Jun 2005 12:56:20 -0400
Received: from localhost (localhost [127.0.0.1])
	by aa-mx1.nexthop.com (Postfix) with ESMTP
	id 5B24A2D50F9; Wed, 22 Jun 2005 12:31:09 -0400 (EDT)
Received: from aa-mx1.nexthop.com ([127.0.0.1])
	by localhost (aa-mx1.nexthop.com [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id 97634-01-68; Wed, 22 Jun 2005 12:31:05 -0400 (EDT)
Received: from BOS-exch01.corp.nexthop.com (unknown [192.168.11.20])
	by aa-mx1.nexthop.com (Postfix) with ESMTP
	id 85AD02D5124; Wed, 22 Jun 2005 12:11:30 -0400 (EDT)
Received: from aa-exchange1.corp.nexthop.com ([65.247.36.233]) by
	BOS-exch01.corp.nexthop.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Jun 2005 12:11:30 -0400
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Date: Wed, 22 Jun 2005 12:11:28 -0400
Message-ID: <BE36D687C8CBFA4AB76F5CD3E3C0FB4E0402B27D@aa-exchange.corp.nexthop.com>
Thread-Topic: WG Review: Transparent Interconnection of Lots of Links (trill)
thread-index: AcV3Op8WK9yGNX1PS5ihIdmLzkviWwACMqHw
From: "Susan Hares" <shares@nexthop.com>
To: "Radia Perlman" <Radia.Perlman@sun.com>
X-OriginalArrivalTime: 22 Jun 2005 16:11:30.0219 (UTC)
	FILETIME=[0CDD0FB0:01C57745]
X-Virus-Scanned: by amavisd-new at nexthop.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 453b1bfcf0292bffe4cab90ba115f503
Content-Transfer-Encoding: quoted-printable
Cc: Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org, ewgray@GraIyMage.com,
        routing-discussion@ietf.org, rtg-chairs@ietf.org
Subject: RE: WG Review: Transparent Interconnection of Lots of Links (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a4cdc653ecdd96665f2aa1c1af034c9e
Content-Transfer-Encoding: quoted-printable

Radia:

That is a very valid point. The Layer2/Layer3 linking is important and
outside of the scope of Layer-2.  Layer 3 expertise is key to that one.=20

Just like ISIS jumbo grams - with cross-over between the two.=20

Sue


-----Original Message-----
From: routing-discussion-bounces@ietf.org
[mailto:routing-discussion-bounces@ietf.org] On Behalf Of Radia Perlman
Sent: Monday, June 20, 2005 4:12 PM
To: Radia Perlman
Cc: Alex Zinin; rtg-dir@ietf.org; ewgray@GraIyMage.com;
routing-discussion@ietf.org; rtg-chairs@ietf.org; Susan Hares
Subject: Re: WG Review: Transparent Interconnection of Lots of Links
(trill)

Oh and one other thing...things like proxy ND and passing around (layer=20
3, layer 2) pairs to
facilitate it, are something else that are not specific to any=20
particular layer 2 technology.

Radia



Radia Perlman wrote:

> Yes. This has been discussed with IEEE. I even gave a tutorial there=20
> on TRILL at the
> last IEEE, both at a general tutorial slot and at the mesh group=20
> (invited by the chair
> of that group, Don Eastlake). It got a very friendly reception, by the

> way.
>
> There are some people in the wireless mesh group who
> have since mentioned to me that they are interested
> in proposing a solution like this within the mesh group.
> And that would be good. But this technology is not specific to any=20
> particular
> layer 2 technology, and certainly not limited to wireless. So it=20
> should be standardized in something
> that is layer 2 agnostic. It could also be used in other places, of=20
> course, and if multiple WGs are
> working on similar things, it is good if they cooperate and liase (is=20
> that a word?) so that technology
> works well together, and even better yet, if it converges towards the=20
> same design. I believe
> the intention of all concerned is that all the WGs that might be=20
> interested and might
> be helpful have liason relationships.
>
> Radia
>
>
>
> Susan Hares wrote:
>
>> Eric and Tony:
>>
>> See my comments about Wireless Mesh proposal an Wi-Mesh alliance I'm=20
>> a part of submitted 6/15/05 to the 802.11s.
>>
>> Radia or others may know more about 802.1 since they have more=20
>> history with IEEE.
>>
>> Sue
>>
>>
------------------------------------------------------------------------
>>
>> *From:* Eric W Gray [mailto:ewgray2k@netscape.net]
>> *Sent:* Monday, June 20, 2005 2:45 PM
>> *To:* Tony Li
>> *Cc:* Susan Hares; Alex Zinin; rtg-dir@ietf.org;=20
>> routing-discussion@ietf.org; rtg-chairs@ietf.org
>> *Subject:* Re: WG Review: Transparent Interconnection of Lots of=20
>> Links (trill)
>>
>> Tony,
>>
>> No disagreement from me. Perhaps the next obvious question is - has=20
>> anyone taken this to the
>> IEEE?
>>
>> --=20
>> Eric
>>
>> Tony Li wrote:
>>
>>
>>
>> In other instances, when proposals were IEEE'ish, we were directed to
>>
>> take them to the IEEE.
>>
>>
>>
>> Tony
>>
>>
>>
>>
>>
>> Eric W Gray wrote:
>>
>> =20
>>
>>> Sue,
>>>
>>>
>>>
>>>    The trouble with obvious questions is that everybody assumes
they've
>>>
>>> been  asked already.
>>>
>>> Now this question has been asked at least once, for sure.  :-)
>>>
>>>
>>>
>>>    From the charter attached in Alex's previous message, the purpose
is
>>>
>>> to "route" Ethernet
>>>
>>> Frames. Quote:
>>>
>>>
>>>
>>> The TRILL WG will design a solution for shortest-path frame routing
in
>>>
>>> multi-hop IEEE 802.1 Ethernet networks with arbitrary topologies,
>>>
>>> using the link-state routing protocol technology.
>>>
>>>
>>>
>>> Since it is clear that at least some people are not satisfied with
the
>>>
>>> 802.1 approach (perhaps
>>>
>>> because of the relative inefficiency associated with completely
unused
>>>
>>> high capacity links), I
>>>
>>> assume you mean to ask "why is it not IEEE" - rather than "why is it

>>> not
>>>
>>> 802.1".
>>>
>>>
>>>
>>>    I believe that is a very good question.  I know of no very good
>>>
>>> reason why the IEEE might
>>>
>>> not specify how to use an OSPF-like routing protocol to fulfill the=20
>>> role
>>>
>>> previously handled by
>>>
>>> Spanning Tree Protocol. Perhaps the only reason why it is being
>>>
>>> discussed here is that it might
>>>
>>> be better - for implementers - if the protocol used was more than
>>>
>>> "OSPF-like."
>>>
>>>
>>>
>>> --=20
>>>
>>> Eric
>>>
>>>
>>>
>>> shares@nexthop.com <mailto:shares@nexthop.com> wrote:
>>>
>>>
>>>
>>>  =20
>>>
>>>> Why are we doing this?  Is it IP or is it Frames?
>>>>
>>>> If it is Frames, why is it not 802.1 - etc?
>>>>
>>>>
>>>> Sue Hares
>>>>
>>>>
>>>>
>>>> -----Original Message-----
>>>>
>>>> From: Alex Zinin [mailto:zinin@psg.com]
>>>> Sent: Thursday, June 16, 2005 10:00 PM
>>>>
>>>> To: routing-discussion@ietf.org
<mailto:routing-discussion@ietf.org>
>>>>
>>>> Cc: rtg-dir@ietf.org <mailto:rtg-dir@ietf.org>; rtg-chairs@ietf.org

>>>> <mailto:rtg-chairs@ietf.org>
>>>>
>>>> Subject: Fwd: WG Review: Transparent Interconnection of Lots of
Links
>>>>
>>>> (trill)
>>>>
>>>>
>>>>
>>>> Since the second BOF on this topic was inconclusive regarding=20
>>>> community
>>>>
>>>> support, the IESG is reevaluating the community consensus on
whether a
>>>>
>>>> WG
>>>>
>>>> should be formed or not.
>>>>
>>>>
>>>>
>>>> If you have input on this, positive or negative, please send it to
>>>>
>>>> iesg@ietf.org <mailto:iesg@ietf.org>.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>    =20
>>>
>>>
------------------------------------------------------------------------

>>>
>>>
>>>
>>>
>>> _______________________________________________
>>>
>>> routing-discussion mailing list
>>>
>>> routing-discussion@ietf.org <mailto:routing-discussion@ietf.org>
>>>
>>> https://www1.ietf.org/mailman/listinfo/routing-discussion
>>>
>>>  =20
>>
>>
>>
>>
>>
>>
>>
>> =20
>>
>



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Wed Jun 22 12:53:52 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02137
	for <routing-discussion-archive@ietf.org>; Wed, 22 Jun 2005 12:53:52 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl8sD-00077H-Ha
	for routing-discussion-archive@ietf.org; Wed, 22 Jun 2005 13:18:53 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl8Pb-0000CU-Ob; Wed, 22 Jun 2005 12:49:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl8Pa-0000Bz-2O; Wed, 22 Jun 2005 12:49:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01374;
	Wed, 22 Jun 2005 12:49:04 -0400 (EDT)
Received: from dns.nexthop.com ([65.247.36.216] helo=aa-mx1.nexthop.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl8nd-0006tk-7R; Wed, 22 Jun 2005 13:14:06 -0400
Received: from localhost (localhost [127.0.0.1])
	by aa-mx1.nexthop.com (Postfix) with ESMTP
	id ADAA12D5064; Wed, 22 Jun 2005 12:48:53 -0400 (EDT)
Received: from aa-mx1.nexthop.com ([127.0.0.1])
	by localhost (aa-mx1.nexthop.com [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id 01518-01-24; Wed, 22 Jun 2005 12:48:50 -0400 (EDT)
Received: from BOS-exch01.corp.nexthop.com (unknown [192.168.11.20])
	by aa-mx1.nexthop.com (Postfix) with ESMTP
	id EC4CF2D5290; Wed, 22 Jun 2005 12:27:39 -0400 (EDT)
Received: from aa-exchange1.corp.nexthop.com ([65.247.36.233]) by
	BOS-exch01.corp.nexthop.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Jun 2005 12:27:39 -0400
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Date: Wed, 22 Jun 2005 12:27:37 -0400
Message-ID: <BE36D687C8CBFA4AB76F5CD3E3C0FB4E0402B28E@aa-exchange.corp.nexthop.com>
Thread-Topic: Fwd: Re: WG Review: Transparent Interconnection of Lots of Links
	(trill)
thread-index: AcV3Kfv7wSoq/cgDQTGa/OAV3u86eAAGxxiw
From: "Susan Hares" <shares@nexthop.com>
To: "Margaret Wasserman" <margaret@thingmagic.com>,
        "Adrian Farrel" <adrian@olddog.co.uk>,
        "Brian E Carpenter" <brc@zurich.ibm.com>
X-OriginalArrivalTime: 22 Jun 2005 16:27:39.0340 (UTC)
	FILETIME=[4E8130C0:01C57747]
X-Virus-Scanned: by amavisd-new at nexthop.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Content-Transfer-Encoding: quoted-printable
Cc: Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org, iesg@ietf.org,
        routing-discussion@ietf.org, rtg-chairs@ietf.org
Subject: RE: Fwd: Re: WG Review: Transparent Interconnection of Lots of
	Links (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Content-Transfer-Encoding: quoted-printable

Margaret:

I suggest that the expertise in the link state is in the Routing area of
the IETF.  If it belongs in the IETF due to expertise, it belongs in the
Routing.=20

Critical early review has been determined to be key to a quickly
deployed specification.  =20

Sue

-----Original Message-----
From: Margaret Wasserman [mailto:margaret@thingmagic.com]=20
Sent: Wednesday, June 22, 2005 8:57 AM
To: Adrian Farrel; Brian E Carpenter
Cc: Tony Li; Alex Zinin; rtg-dir@ietf.org; iesg@ietf.org;
routing-discussion@ietf.org; rtg-chairs@ietf.org; Susan Hares
Subject: Re: Fwd: Re: WG Review: Transparent Interconnection of Lots of
Links (trill)


Hi Adrian,

At 1:22 PM +0100 6/22/05, Adrian Farrel wrote:
>I think the skill-set to which Brian refers is link state routing.
(Care
>to confirm, Brian?)

Yes, expertise in link-state routing is certainly one reason why this=20
work could be seen as more in-scope for the IETF than for the IEEE.=20
Also, frankly, there is interest in the IETF in doing this work (a=20
link-state-based Ethernet routing solution), while the IEEE is=20
continuing to pursue (R)STP-based approaches.

>If so, why is this WG targeted at the Internet Area not the Routing
area?

This questions has been discussed in the IESG, as well, and we did=20
not have 100% agreement regarding the area in which this work belongs.

Personally, I think that TRILL is a better fit for the Internet area,=20
and I will explain why...

Traditionally, the division between the Internet area and the Routing=20
area has been that the Routing area deals with protocols that=20
distribute routing information (routes/labels) and the Internet area=20
has been responsible for the forwarding behaviour and encapsulation=20
mechanisms that make use of that information.

The TRILL charter maintains that split -- any work on the routing=20
protocols themselves would be done in the routing area, while the=20
encapsulation/forwarding mechanism would be developed in the Internet=20
area.

Perhaps you have a different model of the division between the=20
Routing and Internet areas that makes you think otherwise?

The IESG discussed this issue several months ago.  We agreed that=20
this work is close to the line between Internet and Routing, but we=20
reached an agreement that it would best be placed in the Internet=20
area, with the understanding that we would appoint a technical=20
advisor and a WG co-chair with routing expertise.  BIll Fenner=20
volunteered to be the Technical Advisor, and Bill and Alex took an=20
action item to return with a list of potential co-chairs.

Ultimately, I am not sure that it matters all that much which area=20
this work is done in, since it will require expertise and involvement=20
from both areas in order to succeed.

Margaret






_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Wed Jun 22 13:19:09 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04575
	for <routing-discussion-archive@ietf.org>; Wed, 22 Jun 2005 13:19:09 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl9Gk-00081i-Ug
	for routing-discussion-archive@ietf.org; Wed, 22 Jun 2005 13:44:11 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl8qM-0008QE-0X; Wed, 22 Jun 2005 13:16:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl8qK-0008Pp-JZ; Wed, 22 Jun 2005 13:16:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04021;
	Wed, 22 Jun 2005 13:16:41 -0400 (EDT)
Received: from [204.9.221.21] (helo=thingmagic.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl9EL-0007uI-Uz; Wed, 22 Jun 2005 13:41:43 -0400
Received: from [10.0.0.171] (account margaret HELO [10.0.0.171])
	by thingmagic.com (CommuniGate Pro SMTP 4.1.8)
	with ESMTP-TLS id 399041; Wed, 22 Jun 2005 13:11:18 -0400
Mime-Version: 1.0
Message-Id: <p06200790bedf4b3a789e@[10.0.0.171]>
In-Reply-To: <BE36D687C8CBFA4AB76F5CD3E3C0FB4E0402B28E@aa-exchange.corp.nexthop.com>
References: <BE36D687C8CBFA4AB76F5CD3E3C0FB4E0402B28E@aa-exchange.corp.nexthop.com>
Date: Wed, 22 Jun 2005 13:16:28 -0400
To: "Susan Hares" <shares@nexthop.com>, "Adrian Farrel" <adrian@olddog.co.uk>,
        "Brian E Carpenter" <brc@zurich.ibm.com>
From: Margaret Wasserman <margaret@thingmagic.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org, iesg@ietf.org,
        routing-discussion@ietf.org, rtg-chairs@ietf.org
Subject: RE: Fwd: Re: WG Review: Transparent Interconnection of Lots of
 Links (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86


Hi Sue,

The TRILL WG would not be chartered to develop a link-state routing 
protocol.  They would be chartered to make use of an existing 
link-state routing protocol, and any extensions or modifications to 
that protocol would be referred to the appropriate routing area WG.

The TRILL WG would  determine the mechanisms for encapsulating and 
forwarding Ethernet frames and for auto-configuring the rbridges.  I 
am not sure that in-depth expertise in link-state routing protocols 
is needed for that.  Instead, you need expertise in encapsulation, 
forwarding and configuration, which are all Internet area topics.

Margaret


At 12:27 PM -0400 6/22/05, Susan Hares wrote:
>Margaret:
>
>I suggest that the expertise in the link state is in the Routing area of
>the IETF.  If it belongs in the IETF due to expertise, it belongs in the
>Routing.
>
>Critical early review has been determined to be key to a quickly
>deployed specification.
>
>Sue
>
>-----Original Message-----
>From: Margaret Wasserman [mailto:margaret@thingmagic.com]
>Sent: Wednesday, June 22, 2005 8:57 AM
>To: Adrian Farrel; Brian E Carpenter
>Cc: Tony Li; Alex Zinin; rtg-dir@ietf.org; iesg@ietf.org;
>routing-discussion@ietf.org; rtg-chairs@ietf.org; Susan Hares
>Subject: Re: Fwd: Re: WG Review: Transparent Interconnection of Lots of
>Links (trill)
>
>
>Hi Adrian,
>
>At 1:22 PM +0100 6/22/05, Adrian Farrel wrote:
>>I think the skill-set to which Brian refers is link state routing.
>(Care
>>to confirm, Brian?)
>
>Yes, expertise in link-state routing is certainly one reason why this
>work could be seen as more in-scope for the IETF than for the IEEE.
>Also, frankly, there is interest in the IETF in doing this work (a
>link-state-based Ethernet routing solution), while the IEEE is
>continuing to pursue (R)STP-based approaches.
>
>>If so, why is this WG targeted at the Internet Area not the Routing
>area?
>
>This questions has been discussed in the IESG, as well, and we did
>not have 100% agreement regarding the area in which this work belongs.
>
>Personally, I think that TRILL is a better fit for the Internet area,
>and I will explain why...
>
>Traditionally, the division between the Internet area and the Routing
>area has been that the Routing area deals with protocols that
>distribute routing information (routes/labels) and the Internet area
>has been responsible for the forwarding behaviour and encapsulation
>mechanisms that make use of that information.
>
>The TRILL charter maintains that split -- any work on the routing
>protocols themselves would be done in the routing area, while the
>encapsulation/forwarding mechanism would be developed in the Internet
>area.
>
>Perhaps you have a different model of the division between the
>Routing and Internet areas that makes you think otherwise?
>
>The IESG discussed this issue several months ago.  We agreed that
>this work is close to the line between Internet and Routing, but we
>reached an agreement that it would best be placed in the Internet
>area, with the understanding that we would appoint a technical
>advisor and a WG co-chair with routing expertise.  BIll Fenner
>volunteered to be the Technical Advisor, and Bill and Alex took an
>action item to return with a list of potential co-chairs.
>
>Ultimately, I am not sure that it matters all that much which area
>this work is done in, since it will require expertise and involvement
>from both areas in order to succeed.
>
>Margaret


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Wed Jun 22 13:20:14 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04846
	for <routing-discussion-archive@ietf.org>; Wed, 22 Jun 2005 13:20:14 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl9Hn-00085L-K9
	for routing-discussion-archive@ietf.org; Wed, 22 Jun 2005 13:45:16 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl8rP-0000OS-IV; Wed, 22 Jun 2005 13:17:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl8rO-0000O7-8c; Wed, 22 Jun 2005 13:17:58 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04301;
	Wed, 22 Jun 2005 13:17:54 -0400 (EDT)
Received: from mail-dark.research.att.com ([192.20.225.112]
	helo=mail-yellow.research.att.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl9FX-0007wR-LJ; Wed, 22 Jun 2005 13:42:56 -0400
Received: from bright.research.att.com (bright.research.att.com
	[135.207.20.189])
	by mail-blue.research.att.com (Postfix) with ESMTP id 05ABE197397;
	Wed, 22 Jun 2005 13:12:02 -0400 (EDT)
Received: (from fenner@localhost)
	by bright.research.att.com (8.12.11/8.12.10/Submit) id j5MHHj11005533; 
	Wed, 22 Jun 2005 13:17:45 -0400
Message-Id: <200506221717.j5MHHj11005533@bright.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
To: tony.li@tony.li
References: <p0620074fbeddb701e9fe@[10.0.0.171]> <42B84B66.3050006@tony.li>
	<p06200781bedefae66141@[10.0.0.171]> <42B990B0.1060700@tony.li>
Date: Wed, 22 Jun 2005 13:17:45 -0400
From: Bill Fenner <fenner@research.att.com>
Versions: dmail (linux) 2.6d/makemail 2.10
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: rtg-dir@ietf.org, iesg@ietf.org, routing-discussion@ietf.org
Subject: Reopening jumbo frames in IS-IS
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a


Tony,

  [cc: header slightly trimmed]

>I would like to propose that we re-open the work on IS-IS
>over jumbo frames.  Since the IEEE has clearly said that jumbo frames
>are out of scope, they can hardly object to the IETF working on it.

My recollection, assisted with email archives, was that in December
2001, you, Randy and Ran agreed on a way forward: split the longer MTU
specification into a new document, and then define IS-IS over that.
Randy sent out drafts called draft-ymbk-mtu-00 in late 2001/early 2002
that I thought were for the first step, but I never saw anything beyond
that.

Since this was happening right as I was becoming an AD, perhaps I have
some of the details of the plan wrong, but I had thought that there was
a way forward that was then dropped by the participants due to lack of
cycles, not because the IESG said no.

  Bill

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Wed Jun 22 14:19:02 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12616
	for <routing-discussion-archive@ietf.org>; Wed, 22 Jun 2005 14:19:00 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlA3K-0002St-7l
	for routing-discussion-archive@ietf.org; Wed, 22 Jun 2005 14:34:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl9Yk-0005Y3-Nk; Wed, 22 Jun 2005 14:02:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl9Yi-0005Wl-NO; Wed, 22 Jun 2005 14:02:44 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07271;
	Wed, 22 Jun 2005 14:02:41 -0400 (EDT)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dl9hi-0000cr-4W; Wed, 22 Jun 2005 14:12:03 -0400
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-2.cisco.com with ESMTP; 22 Jun 2005 10:46:50 -0700
Received: from cliff.cisco.com (cliff.cisco.com [171.69.11.141])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j5MHknvM016101;
	Wed, 22 Jun 2005 10:46:49 -0700 (PDT)
Received: from [10.21.122.155] (sjc-vpn6-667.cisco.com [10.21.122.155]) by
	cliff.cisco.com (8.6.12/8.6.5) with ESMTP id KAA16198;
	Wed, 22 Jun 2005 10:43:09 -0700
Message-ID: <42B9A32D.5040302@tony.li>
Date: Wed, 22 Jun 2005 10:43:09 -0700
From: Tony Li <tony.li@tony.li>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Bill Fenner <fenner@research.att.com>
References: <p0620074fbeddb701e9fe@[10.0.0.171]> <42B84B66.3050006@tony.li>
	<p06200781bedefae66141@[10.0.0.171]> <42B990B0.1060700@tony.li>
	<200506221717.j5MHHj11005533@bright.research.att.com>
In-Reply-To: <200506221717.j5MHHj11005533@bright.research.att.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: 7bit
Cc: rtg-dir@ietf.org, iesg@ietf.org, routing-discussion@ietf.org
Subject: Re: Reopening jumbo frames in IS-IS
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: 7bit



Bill,

Sorry, but I was explicitly told to stop work.

Regardless of that, are you saying that it's possible to continue the work?

Tony


Bill Fenner wrote:
> Tony,
> 
>   [cc: header slightly trimmed]
> 
> 
>>I would like to propose that we re-open the work on IS-IS
>>over jumbo frames.  Since the IEEE has clearly said that jumbo frames
>>are out of scope, they can hardly object to the IETF working on it.
> 
> 
> My recollection, assisted with email archives, was that in December
> 2001, you, Randy and Ran agreed on a way forward: split the longer MTU
> specification into a new document, and then define IS-IS over that.
> Randy sent out drafts called draft-ymbk-mtu-00 in late 2001/early 2002
> that I thought were for the first step, but I never saw anything beyond
> that.
> 
> Since this was happening right as I was becoming an AD, perhaps I have
> some of the details of the plan wrong, but I had thought that there was
> a way forward that was then dropped by the participants due to lack of
> cycles, not because the IESG said no.
> 
>   Bill
> 

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Wed Jun 22 14:51:33 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16125
	for <routing-discussion-archive@ietf.org>; Wed, 22 Jun 2005 14:51:32 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlAaQ-0005do-2n
	for routing-discussion-archive@ietf.org; Wed, 22 Jun 2005 15:08:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlA4n-0000GC-Az; Wed, 22 Jun 2005 14:35:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlA4l-0000Et-4X; Wed, 22 Jun 2005 14:35:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14922;
	Wed, 22 Jun 2005 14:35:36 -0400 (EDT)
Received: from dns.nexthop.com ([65.247.36.216] helo=aa-mx1.nexthop.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlAJc-0004Mx-3b; Wed, 22 Jun 2005 14:51:13 -0400
Received: from localhost (localhost [127.0.0.1])
	by aa-mx1.nexthop.com (Postfix) with ESMTP
	id 0DE7D2D559A; Wed, 22 Jun 2005 14:25:59 -0400 (EDT)
Received: from aa-mx1.nexthop.com ([127.0.0.1])
	by localhost (aa-mx1.nexthop.com [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id 21370-01-12; Wed, 22 Jun 2005 14:25:54 -0400 (EDT)
Received: from BOS-exch01.corp.nexthop.com (unknown [192.168.11.20])
	by aa-mx1.nexthop.com (Postfix) with ESMTP
	id 9E55B2D51CD; Wed, 22 Jun 2005 14:01:37 -0400 (EDT)
Received: from aa-exchange1.corp.nexthop.com ([65.247.36.233]) by
	BOS-exch01.corp.nexthop.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Jun 2005 14:01:37 -0400
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Date: Wed, 22 Jun 2005 14:01:35 -0400
Message-ID: <BE36D687C8CBFA4AB76F5CD3E3C0FB4E0402B2D1@aa-exchange.corp.nexthop.com>
Thread-Topic: Fwd: Re: WG Review: Transparent Interconnection of Lots of Links
	(trill)
thread-index: AcV3Uiw6/YojNlnKSayAsFVlmJatwwAAG+Iw
From: "Susan Hares" <shares@nexthop.com>
To: "Margaret Wasserman" <margaret@thingmagic.com>,
        "Adrian Farrel" <adrian@olddog.co.uk>,
        "Brian E Carpenter" <brc@zurich.ibm.com>
X-OriginalArrivalTime: 22 Jun 2005 18:01:37.0309 (UTC)
	FILETIME=[6EFEFCD0:01C57754]
X-Virus-Scanned: by amavisd-new at nexthop.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68ba2b07ef271dba6ee42a93832cfa4c
Content-Transfer-Encoding: quoted-printable
Cc: Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org, iesg@ietf.org,
        routing-discussion@ietf.org, rtg-chairs@ietf.org
Subject: RE: Fwd: Re: WG Review: Transparent Interconnection of Lots of
	Links (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
Content-Transfer-Encoding: quoted-printable

Margaret:=20

Routing creates forwarding.  The difficulty is in the timing of the
updates and not the actual forwarding.  Creating encapsulations that
scale and can perform well has been in the routing area (MPLS is an
example).   Updating from the control plane to the forwarding plane is
also in the Routing area (FORCES) due to the timing issues.  =20

Even if you use existing protocols, you may have timing constraints or
protocol issues.  An example of this is the MANET OSPF work.  (Please
refer to the MANET page for this.)  Reduced flooding has been discussed
and experimented with in MANET.  Reduced flooding is key to reducing
overload on some IEEE substrates (wireless mesh).  Security of the
Bridge protocol should be a concern.  Again, the discussions in the
RP-SEC group have long discussed good and bad algorithms.=20

In 802.1 you are talking about inter-working between multiple LAN areas.
This most resembles ISIS/OSPF inter-areas.  Auto-configuration of
inter-area nodes has experience in routing or the operations.   My
understanding is that you are not assigning MAC address (aka DHCP like
functions) but creating forwarding state.=20

So I guess my summary comment is: "I do not agree with you".  The
critical component of this work is the link-state, routing
auto-configuration and security knobs known to the routing area.=20

If we are trying to get this protocol out quickly, let's build on the
expertise in the routing area.=20

Sue Hares


-----Original Message-----
From: Margaret Wasserman [mailto:margaret@thingmagic.com]=20
Sent: Wednesday, June 22, 2005 1:16 PM
To: Susan Hares; Adrian Farrel; Brian E Carpenter
Cc: Tony Li; Alex Zinin; rtg-dir@ietf.org; iesg@ietf.org;
routing-discussion@ietf.org; rtg-chairs@ietf.org
Subject: RE: Fwd: Re: WG Review: Transparent Interconnection of Lots of
Links (trill)


Hi Sue,

The TRILL WG would not be chartered to develop a link-state routing=20
protocol.  They would be chartered to make use of an existing=20
link-state routing protocol, and any extensions or modifications to=20
that protocol would be referred to the appropriate routing area WG.

The TRILL WG would  determine the mechanisms for encapsulating and=20
forwarding Ethernet frames and for auto-configuring the rbridges.  I=20
am not sure that in-depth expertise in link-state routing protocols=20
is needed for that.  Instead, you need expertise in encapsulation,=20
forwarding and configuration, which are all Internet area topics.


Margaret


At 12:27 PM -0400 6/22/05, Susan Hares wrote:
>Margaret:
>
>I suggest that the expertise in the link state is in the Routing area
of
>the IETF.  If it belongs in the IETF due to expertise, it belongs in
the
>Routing.
>
>Critical early review has been determined to be key to a quickly
>deployed specification.
>
>Sue
>
>-----Original Message-----
>From: Margaret Wasserman [mailto:margaret@thingmagic.com]
>Sent: Wednesday, June 22, 2005 8:57 AM
>To: Adrian Farrel; Brian E Carpenter
>Cc: Tony Li; Alex Zinin; rtg-dir@ietf.org; iesg@ietf.org;
>routing-discussion@ietf.org; rtg-chairs@ietf.org; Susan Hares
>Subject: Re: Fwd: Re: WG Review: Transparent Interconnection of Lots of
>Links (trill)
>
>
>Hi Adrian,
>
>At 1:22 PM +0100 6/22/05, Adrian Farrel wrote:
>>I think the skill-set to which Brian refers is link state routing.
>(Care
>>to confirm, Brian?)
>
>Yes, expertise in link-state routing is certainly one reason why this
>work could be seen as more in-scope for the IETF than for the IEEE.
>Also, frankly, there is interest in the IETF in doing this work (a
>link-state-based Ethernet routing solution), while the IEEE is
>continuing to pursue (R)STP-based approaches.
>
>>If so, why is this WG targeted at the Internet Area not the Routing
>area?
>
>This questions has been discussed in the IESG, as well, and we did
>not have 100% agreement regarding the area in which this work belongs.
>
>Personally, I think that TRILL is a better fit for the Internet area,
>and I will explain why...
>
>Traditionally, the division between the Internet area and the Routing
>area has been that the Routing area deals with protocols that
>distribute routing information (routes/labels) and the Internet area
>has been responsible for the forwarding behaviour and encapsulation
>mechanisms that make use of that information.
>
>The TRILL charter maintains that split -- any work on the routing
>protocols themselves would be done in the routing area, while the
>encapsulation/forwarding mechanism would be developed in the Internet
>area.
>
>Perhaps you have a different model of the division between the
>Routing and Internet areas that makes you think otherwise?
>
>The IESG discussed this issue several months ago.  We agreed that
>this work is close to the line between Internet and Routing, but we
>reached an agreement that it would best be placed in the Internet
>area, with the understanding that we would appoint a technical
>advisor and a WG co-chair with routing expertise.  BIll Fenner
>volunteered to be the Technical Advisor, and Bill and Alex took an
>action item to return with a list of potential co-chairs.
>
>Ultimately, I am not sure that it matters all that much which area
>this work is done in, since it will require expertise and involvement
>from both areas in order to succeed.
>
>Margaret



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Wed Jun 22 16:44:10 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03548
	for <routing-discussion-archive@ietf.org>; Wed, 22 Jun 2005 16:44:10 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlCTB-0001Cy-91
	for routing-discussion-archive@ietf.org; Wed, 22 Jun 2005 17:09:13 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlBzs-0006zN-6m; Wed, 22 Jun 2005 16:38:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlBzq-0006z4-CW; Wed, 22 Jun 2005 16:38:54 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02657;
	Wed, 22 Jun 2005 16:38:41 -0400 (EDT)
Received: from blv-smtpout-01.boeing.com ([130.76.32.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlC8d-0007lg-Gv; Wed, 22 Jun 2005 16:48:02 -0400
Received: from blv-av-01.boeing.com ([192.42.227.216])
	by blv-smtpout-01.boeing.com (8.9.2.MG.10092003/8.8.5-M2) with ESMTP id
	NAA11042; Wed, 22 Jun 2005 13:22:40 -0700 (PDT)
Received: from XCH-NE-05P.ne.nos.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.11.3/8.11.3/MBS-AV-LDAP-01) with ESMTP id
	j5MKMdn05196; Wed, 22 Jun 2005 13:22:39 -0700 (PDT)
Received: from XCH-NE-02.ne.nos.boeing.com ([128.225.80.202]) by
	XCH-NE-05P.ne.nos.boeing.com with Microsoft SMTPSVC(5.0.2195.6713); 
	Wed, 22 Jun 2005 16:22:38 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 22 Jun 2005 16:22:38 -0400
Message-ID: <EF40C42ACAB7A649B2EAE70C19B6CD6E037C3A65@xch-ne-02.ne.nos.boeing.com>
Thread-Topic: Fwd: Re: WG Review: Transparent Interconnection of Lots ofLinks
	(trill)
Thread-Index: AcV3U5IsQqy7w2XaTVyMB0cfld2vEQAEyW9w
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: "Margaret Wasserman" <margaret@thingmagic.com>
X-OriginalArrivalTime: 22 Jun 2005 20:22:38.0746 (UTC)
	FILETIME=[2267CFA0:01C57768]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: quoted-printable
Cc: rtg-dir@ietf.org, iesg@ietf.org, routing-discussion@ietf.org,
        rtg-chairs@ietf.org
Subject: RE: Fwd: Re: WG Review: Transparent Interconnection of Lots ofLinks
	(trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: quoted-printable

If TRILL is striving to adapt a link state protocol to a flat address
space, seems to me that within the current IETF structure, expertise
would be in the routing area.

But this seems to create confusion. Maybe I'm confused, but I don't
think TRILL is going after creating larger layer 2 nets at all, right?
Just attempting to do something more clever than a spanning tree for the
layer 2 catenet. So I don't think that lack of market success of NHRP or
MPOA, from the old ION wg, where two fair dinkum *routing* protocols
were being meshed together, applies here. Isn't the scope of TRILL far
smaller? I hope so.

We need a "bridging" area in the IETF, then, and perhaps work on things
like IGMP snooping can go in there as well. This might help alleviate
some of the concerns I've seen aired. We need a home for "this is really
supposed to be IEEE work, but they don't want to do it or they need
help."

Bert


> -----Original Message-----
> From: Margaret Wasserman [mailto:margaret@thingmagic.com]=20
> Sent: Wednesday, June 22, 2005 12:16 PM
> To: Susan Hares; Adrian Farrel; Brian E Carpenter
> Cc: Alex Zinin; rtg-dir@ietf.org; iesg@ietf.org;=20
> routing-discussion@ietf.org; rtg-chairs@ietf.org
> Subject: RE: Fwd: Re: WG Review: Transparent Interconnection=20
> of Lots ofLinks (trill)
>=20
>=20
> Hi Sue,
>=20
> The TRILL WG would not be chartered to develop a link-state routing=20
> protocol.  They would be chartered to make use of an existing=20
> link-state routing protocol, and any extensions or modifications to=20
> that protocol would be referred to the appropriate routing area WG.
>=20
> The TRILL WG would  determine the mechanisms for encapsulating and=20
> forwarding Ethernet frames and for auto-configuring the rbridges.  I=20
> am not sure that in-depth expertise in link-state routing protocols=20
> is needed for that.  Instead, you need expertise in encapsulation,=20
> forwarding and configuration, which are all Internet area topics.
>=20
> Margaret


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Wed Jun 22 17:20:20 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06414
	for <routing-discussion-archive@ietf.org>; Wed, 22 Jun 2005 17:20:20 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlD2B-0002v0-Ou
	for routing-discussion-archive@ietf.org; Wed, 22 Jun 2005 17:45:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlCbu-0007Rj-De; Wed, 22 Jun 2005 17:18:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlCbs-0007RM-1l; Wed, 22 Jun 2005 17:18:12 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06309;
	Wed, 22 Jun 2005 17:18:05 -0400 (EDT)
Received: from nwkea-mail-1.sun.com ([192.18.42.13])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlCzx-0002oi-GA; Wed, 22 Jun 2005 17:43:09 -0400
Received: from jurassic.eng.sun.com ([129.146.104.31])
	by nwkea-mail-1.sun.com (8.12.10/8.12.9) with ESMTP id j5MLI2Kg015402; 
	Wed, 22 Jun 2005 14:18:02 -0700 (PDT)
Received: from [192.9.61.11] (punchin-nordmark.SFBay.Sun.COM [192.9.61.11])
	by jurassic.eng.sun.com (8.13.4+Sun/8.13.4) with ESMTP id
	j5MLHvsZ377256
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
	Wed, 22 Jun 2005 14:17:59 -0700 (PDT)
Message-ID: <42B9D5A2.3050408@sun.com>
Date: Wed, 22 Jun 2005 14:18:26 -0700
From: Erik Nordmark <erik.nordmark@sun.com>
User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050323)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Margaret Wasserman <margaret@thingmagic.com>
References: <BE36D687C8CBFA4AB76F5CD3E3C0FB4E0402B28E@aa-exchange.corp.nexthop.com>
	<p06200790bedf4b3a789e@[10.0.0.171]>
In-Reply-To: <p06200790bedf4b3a789e@[10.0.0.171]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 7bit
Cc: Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org, iesg@ietf.org,
        routing-discussion@ietf.org, rtg-chairs@ietf.org,
        Adrian Farrel <adrian@olddog.co.uk>,
        Brian E Carpenter <brc@zurich.ibm.com>,
        Susan Hares <shares@nexthop.com>
Subject: Re: Fwd: Re: WG Review: Transparent Interconnection of Lots of Links
 (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 7bit

Margaret Wasserman wrote:

> The TRILL WG would  determine the mechanisms for encapsulating and 
> forwarding Ethernet frames and for auto-configuring the rbridges.  I am 
> not sure that in-depth expertise in link-state routing protocols is 
> needed for that.  Instead, you need expertise in encapsulation, 
> forwarding and configuration, which are all Internet area topics.

In addition to the above, there is also a need to work out the details 
how TRILL devices interact with IEEE 802.1D bridges at the edge. This is 
an issue where the L2VPN WG has some experience, and working with L2VPN 
and IEEE 802.1 is key. So being in the same area (INT) as L2VPN might be 
helpful.

    Erik

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Wed Jun 22 17:22:50 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06660
	for <routing-discussion-archive@ietf.org>; Wed, 22 Jun 2005 17:22:50 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlD4a-00037H-NP
	for routing-discussion-archive@ietf.org; Wed, 22 Jun 2005 17:47:53 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlCff-00007S-VI; Wed, 22 Jun 2005 17:22:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlCfe-000075-Fj; Wed, 22 Jun 2005 17:22:06 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06579;
	Wed, 22 Jun 2005 17:22:03 -0400 (EDT)
Received: from nwkea-mail-1.sun.com ([192.18.42.13])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlD3n-00031b-P2; Wed, 22 Jun 2005 17:47:07 -0400
Received: from jurassic.eng.sun.com ([129.146.108.38])
	by nwkea-mail-1.sun.com (8.12.10/8.12.9) with ESMTP id j5MLM1Kg018055; 
	Wed, 22 Jun 2005 14:22:01 -0700 (PDT)
Received: from [192.9.61.11] (punchin-nordmark.SFBay.Sun.COM [192.9.61.11])
	by jurassic.eng.sun.com (8.13.4+Sun/8.13.4) with ESMTP id
	j5MLLv7v378344
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
	Wed, 22 Jun 2005 14:21:59 -0700 (PDT)
Message-ID: <42B9D692.8020407@sun.com>
Date: Wed, 22 Jun 2005 14:22:26 -0700
From: Erik Nordmark <erik.nordmark@sun.com>
User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050323)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Bill Fenner <fenner@research.att.com>
References: <p0620074fbeddb701e9fe@[10.0.0.171]>
	<42B84B66.3050006@tony.li>	<p06200781bedefae66141@[10.0.0.171]>
	<42B990B0.1060700@tony.li>
	<200506221717.j5MHHj11005533@bright.research.att.com>
In-Reply-To: <200506221717.j5MHHj11005533@bright.research.att.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit
Cc: rtg-dir@ietf.org, iesg@ietf.org, routing-discussion@ietf.org
Subject: Re: Reopening jumbo frames in IS-IS
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: 7bit

Bill Fenner wrote:

> My recollection, assisted with email archives, was that in December
> 2001, you, Randy and Ran agreed on a way forward: split the longer MTU
> specification into a new document, and then define IS-IS over that.
> Randy sent out drafts called draft-ymbk-mtu-00 in late 2001/early 2002
> that I thought were for the first step, but I never saw anything beyond
> that.

My recollection is that the feedback from IEEE 802 was that we shouldn't 
touch non-standard things like jumbo-frames, and as a result nothing 
more was done in this area.

Perhaps we asked a suboptimal question back then; whether IEEE 802 liked 
the idea of us doing something for jumboframes and IS-IS. Had we instead 
asked them whether they were going to specify how jumboframes work with 
IS-IS, we would probably have received a different answer.

    Erik

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Wed Jun 22 17:25:11 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06890
	for <routing-discussion-archive@ietf.org>; Wed, 22 Jun 2005 17:25:10 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlD6s-0003C5-Gq
	for routing-discussion-archive@ietf.org; Wed, 22 Jun 2005 17:50:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlCho-0000jc-HY; Wed, 22 Jun 2005 17:24:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlChn-0000jI-Hz; Wed, 22 Jun 2005 17:24:19 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06823;
	Wed, 22 Jun 2005 17:24:13 -0400 (EDT)
Received: from nwkea-mail-1.sun.com ([192.18.42.13])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlD5s-00038t-R5; Wed, 22 Jun 2005 17:49:17 -0400
Received: from jurassic.eng.sun.com ([129.146.106.105])
	by nwkea-mail-1.sun.com (8.12.10/8.12.9) with ESMTP id j5MLO6Kg019297; 
	Wed, 22 Jun 2005 14:24:06 -0700 (PDT)
Received: from [192.9.61.11] (punchin-nordmark.SFBay.Sun.COM [192.9.61.11])
	by jurassic.eng.sun.com (8.13.4+Sun/8.13.4) with ESMTP id
	j5MLO1ZO378938
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
	Wed, 22 Jun 2005 14:24:03 -0700 (PDT)
Message-ID: <42B9D70E.5040401@sun.com>
Date: Wed, 22 Jun 2005 14:24:30 -0700
From: Erik Nordmark <erik.nordmark@sun.com>
User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050323)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: curtis@faster-light.net
References: <200506221618.j5MGIB2V039677@workhorse.faster-light.net>
In-Reply-To: <200506221618.j5MGIB2V039677@workhorse.faster-light.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Content-Transfer-Encoding: 7bit
Cc: Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org, iesg@ietf.org,
        routing-discussion@ietf.org, rtg-chairs@ietf.org,
        Brian E Carpenter <brc@zurich.ibm.com>,
        Susan Hares <shares@nexthop.com>
Subject: Re: Fwd: Re: WG Review: Transparent Interconnection of Lots of	Links
 (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit

Curtis Villamizar wrote:

> Its clear that there is no interest in providers in bridging
> solutions.  There have been enough failures to keep most people from
> further attempts, ranging from the bridging done in regional acedemic
> networks in the late 1980s to attempts to use IP at the edges and ATM
> in the middle, to the complete failure in the market of ATM approaches
> such as RFC1577, NHRP, MPOA.

I'm confused. There seems to be a lot of provider interest in L2VPN 
technology, which is providing what looks like a bridged service across 
a WAN.

    Erik

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Wed Jun 22 18:22:05 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12642
	for <routing-discussion-archive@ietf.org>; Wed, 22 Jun 2005 18:22:05 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlDzy-0005u1-5k
	for routing-discussion-archive@ietf.org; Wed, 22 Jun 2005 18:47:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlDZz-0004FR-3P; Wed, 22 Jun 2005 18:20:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DlDZx-0004Eu-35
	for routing-discussion@megatron.ietf.org;
	Wed, 22 Jun 2005 18:20:17 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12386
	for <routing-discussion@ietf.org>; Wed, 22 Jun 2005 18:20:13 -0400 (EDT)
Received: from relay02.pair.com ([209.68.5.16])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DlDy9-0005ld-9L
	for routing-discussion@ietf.org; Wed, 22 Jun 2005 18:45:17 -0400
Received: (qmail 52988 invoked from network); 22 Jun 2005 22:20:03 -0000
Received: from unknown (HELO workhorse.faster-light.net) (unknown)
	by unknown with SMTP; 22 Jun 2005 22:20:03 -0000
X-pair-Authenticated: 69.37.59.162
Received: from workhorse.faster-light.net (localhost.faster-light.net
	[127.0.0.1])
	by workhorse.faster-light.net (8.12.11/8.12.11) with ESMTP id
	j5MMJfxv044008; Wed, 22 Jun 2005 18:19:41 -0400 (EDT)
	(envelope-from curtis@workhorse.faster-light.net)
Message-Id: <200506222219.j5MMJfxv044008@workhorse.faster-light.net>
To: Erik Nordmark <erik.nordmark@sun.com>
In-reply-to: Your message of "Wed, 22 Jun 2005 14:24:30 PDT."
	<42B9D70E.5040401@sun.com> 
Date: Wed, 22 Jun 2005 18:19:41 -0400
From: Curtis Villamizar <curtis@faster-light.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org, iesg@ietf.org,
        routing-discussion@ietf.org, rtg-chairs@ietf.org,
        curtis@faster-light.net, Brian E Carpenter <brc@zurich.ibm.com>,
        Susan Hares <shares@nexthop.com>
Subject: Re: Fwd: Re: WG Review: Transparent Interconnection of Lots of
	Links (trill) 
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: curtis@faster-light.net
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69


In message <42B9D70E.5040401@sun.com>
Erik Nordmark writes:
>  
> Curtis Villamizar wrote:
>  
> > Its clear that there is no interest in providers in bridging
> > solutions.  There have been enough failures to keep most people from
> > further attempts, ranging from the bridging done in regional acedemic
> > networks in the late 1980s to attempts to use IP at the edges and ATM
> > in the middle, to the complete failure in the market of ATM approaches
> > such as RFC1577, NHRP, MPOA.
>  
> I'm confused. There seems to be a lot of provider interest in L2VPN 
> technology, which is providing what looks like a bridged service across 
> a WAN.
>  
>     Erik


For one things that's selling a service to someone else not building
one's own network on top of a bridged service.  btw- VPLS would be a
bridged service.  L2VPN is just the L2 part.

The motivation for L2VPN with carriers that I've spoken to is not that
there is a gold mine in this service.  It is quite the contrary.  The
bridged services and leased lines of any distance are a shrinking
market or very slow growth at best and no longer justify their own
network when the IP network is growing to circuit capacities in
multiples of OC192.  If these services can be efficiently carried over
the same nework that carries IP it would be a cost savings and in some
cases get these services back in the black again.

Provider backbones over anything resembling a bridged network seems to
be close to dead.  Also note that I said that past experience is
enough to keep "most" people from repeating mistakes of the past.
Another mistake of the past is radically overestimating market growth
so if anyone does indicate a gold mine in L2VPN I'd be skeptical.

Curtis

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Thu Jun 23 00:09:14 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07144
	for <routing-discussion-archive@ietf.org>; Thu, 23 Jun 2005 00:09:13 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlJPw-0003wm-Fj
	for routing-discussion-archive@ietf.org; Thu, 23 Jun 2005 00:34:21 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlJ1L-0000rh-Vz; Thu, 23 Jun 2005 00:08:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlJ1K-0000rZ-7K; Thu, 23 Jun 2005 00:08:54 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07138;
	Thu, 23 Jun 2005 00:08:50 -0400 (EDT)
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlJPY-0003wG-Su; Thu, 23 Jun 2005 00:33:58 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id j5N48BC26018;
	Thu, 23 Jun 2005 07:08:15 +0300
Date: Thu, 23 Jun 2005 07:08:11 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
In-Reply-To: <EF40C42ACAB7A649B2EAE70C19B6CD6E037C3A65@xch-ne-02.ne.nos.boeing.com>
Message-ID: <Pine.LNX.4.61.0506230703020.25658@netcore.fi>
References: <EF40C42ACAB7A649B2EAE70C19B6CD6E037C3A65@xch-ne-02.ne.nos.boeing.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: rbridge@postel.org, iesg@ietf.org, routing-discussion@ietf.org
Subject: RE: Fwd: Re: WG Review: Transparent Interconnection of Lots ofLinks
 (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464

On Wed, 22 Jun 2005, Manfredi, Albert E wrote:
> But this seems to create confusion. Maybe I'm confused, but I don't
> think TRILL is going after creating larger layer 2 nets at all, right?
> Just attempting to do something more clever than a spanning tree for the
> layer 2 catenet.

Maybe not intentionally, but I think that will be the result.  A usage 
case that has been shown has been a hospital whose network (with 
thousands of hosts) is a single broadcast domain.

I think everyone can agree that instead of making such large broadcast 
domains, the network should be split up by routing instead.

While TRILL would "fix" the usage case above so that using a single 
broadcast domain would still "work", that would still be very bad 
network design, and in the longer term, it would probably be 
counter-productive.

(In our environment, what we've seen recently is *decrease* in the 
size of broadcast domains/subnets due to the requirements to isolate 
and filter the traffic from other hosts at the site.  Using a single 
domain makes this security issue much worse.)

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Thu Jun 23 08:02:50 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01447
	for <routing-discussion-archive@ietf.org>; Thu, 23 Jun 2005 08:02:50 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlQoG-00080Y-TL
	for routing-discussion-archive@ietf.org; Thu, 23 Jun 2005 08:27:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlQLT-00025w-Cs; Thu, 23 Jun 2005 07:58:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlQLR-00025i-8x; Thu, 23 Jun 2005 07:58:10 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00871;
	Thu, 23 Jun 2005 07:58:08 -0400 (EDT)
Received: from mtagate2.uk.ibm.com ([195.212.29.135])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlQji-0007lt-P8; Thu, 23 Jun 2005 08:23:17 -0400
Received: from d06nrmr1407.portsmouth.uk.ibm.com
	(d06nrmr1407.portsmouth.uk.ibm.com [9.149.38.185])
	by mtagate2.uk.ibm.com (8.12.10/8.12.10) with ESMTP id j5NBvtLC164950; 
	Thu, 23 Jun 2005 11:57:55 GMT
Received: from d06av02.portsmouth.uk.ibm.com (d06av02.portsmouth.uk.ibm.com
	[9.149.37.228])
	by d06nrmr1407.portsmouth.uk.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id
	j5NBvtcR267040; Thu, 23 Jun 2005 12:57:55 +0100
Received: from d06av02.portsmouth.uk.ibm.com (loopback [127.0.0.1])
	by d06av02.portsmouth.uk.ibm.com (8.12.11/8.13.3) with ESMTP id
	j5NBvt81000786; Thu, 23 Jun 2005 12:57:55 +0100
Received: from mail-gw3.hursley.ibm.com (mail-gw3.hursley.ibm.com
	[9.20.131.251])
	by d06av02.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id
	j5NBvtfu000781; Thu, 23 Jun 2005 12:57:55 +0100
Received: from [9.20.136.27] (helo=sp15en17.hursley.ibm.com)
	by mail-gw3.hursley.ibm.com with esmtp (Exim 4.50)
	id 1DlQLD-0003ZA-1n; Thu, 23 Jun 2005 12:57:55 +0100
Received: from zurich.ibm.com (sig-9-145-135-83.de.ibm.com [9.145.135.83])
	by sp15en17.hursley.ibm.com (AIX5.1/8.11.6p2/8.11.0) with SMTP id
	j5NBvro118166; Thu, 23 Jun 2005 12:57:53 +0100
Message-ID: <42BAA3BE.2040007@zurich.ibm.com>
Date: Thu, 23 Jun 2005 13:57:50 +0200
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.6) Gecko/20040113
X-Accept-Language: en, fr, de
MIME-Version: 1.0
To: Pekka Savola <pekkas@netcore.fi>
References: <EF40C42ACAB7A649B2EAE70C19B6CD6E037C3A65@xch-ne-02.ne.nos.boeing.com>
	<Pine.LNX.4.61.0506230703020.25658@netcore.fi>
In-Reply-To: <Pine.LNX.4.61.0506230703020.25658@netcore.fi>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: 7bit
Cc: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>, rbridge@postel.org,
        iesg@ietf.org, routing-discussion@ietf.org
Subject: Re: Fwd: Re: WG Review: Transparent Interconnection of Lots ofLinks
 (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Content-Transfer-Encoding: 7bit

Pekka Savola wrote:
> On Wed, 22 Jun 2005, Manfredi, Albert E wrote:
> 
>> But this seems to create confusion. Maybe I'm confused, but I don't
>> think TRILL is going after creating larger layer 2 nets at all, right?
>> Just attempting to do something more clever than a spanning tree for the
>> layer 2 catenet.
> 
> 
> Maybe not intentionally, but I think that will be the result.  A usage 
> case that has been shown has been a hospital whose network (with 
> thousands of hosts) is a single broadcast domain.
> 
> I think everyone can agree that instead of making such large broadcast 
> domains, the network should be split up by routing instead.
> 
> While TRILL would "fix" the usage case above so that using a single 
> broadcast domain would still "work", that would still be very bad 
> network design, and in the longer term, it would probably be 
> counter-productive.
> 
> (In our environment, what we've seen recently is *decrease* in the size 
> of broadcast domains/subnets due to the requirements to isolate and 
> filter the traffic from other hosts at the site.  Using a single domain 
> makes this security issue much worse.)
> 

Having run one of those very large broadcast domains in my past life,
I understand Pekka and Manfred perfectly - but nevertheless there
seems to be a market for such solutions, and that means either
we do a hopefully good standard, or someone else does a possibly
less good standard. I don't think there's a 3rd choice.

    Brian


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Thu Jun 23 08:09:06 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02551
	for <routing-discussion-archive@ietf.org>; Thu, 23 Jun 2005 08:09:06 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlQuN-0008Rt-0M
	for routing-discussion-archive@ietf.org; Thu, 23 Jun 2005 08:34:16 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlQUw-0004CY-5S; Thu, 23 Jun 2005 08:07:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlQUu-0004CK-49; Thu, 23 Jun 2005 08:07:56 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02444;
	Thu, 23 Jun 2005 08:07:55 -0400 (EDT)
Received: from newdev.eecs.harvard.edu ([140.247.60.212]
	helo=newdev.harvard.edu) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlQtD-0008Ph-Bs; Thu, 23 Jun 2005 08:33:04 -0400
Received: by newdev.harvard.edu (Postfix, from userid 501)
	id B6C593E8113; Thu, 23 Jun 2005 08:07:40 -0400 (EDT)
To: iesg@ietf.org, rbridge@postel.org, routing-discussion@ietf.org
Message-Id: <20050623120740.B6C593E8113@newdev.harvard.edu>
Date: Thu, 23 Jun 2005 08:07:40 -0400 (EDT)
From: sob@harvard.edu (Scott Bradner)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Subject: Re: Fwd: Re: WG Review: Transparent Interconnection of Lots ofLinks
	(trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2


Brian sed:
> and that means either
> we do a hopefully good standard, or someone else does a possibly
> less good standard. I don't think there's a 3rd choice.

oh, I think there is a 3rd choice - someone else does a very bad standard

Scott

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Thu Jun 23 08:17:41 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03174
	for <routing-discussion-archive@ietf.org>; Thu, 23 Jun 2005 08:17:41 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlR2g-0000Qc-3H
	for routing-discussion-archive@ietf.org; Thu, 23 Jun 2005 08:42:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlQdC-0005qe-Mv; Thu, 23 Jun 2005 08:16:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlQdB-0005qO-El; Thu, 23 Jun 2005 08:16:29 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03030;
	Thu, 23 Jun 2005 08:16:28 -0400 (EDT)
Received: from newdev.eecs.harvard.edu ([140.247.60.212]
	helo=newdev.harvard.edu) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlR1U-0000OU-RG; Thu, 23 Jun 2005 08:41:38 -0400
Received: by newdev.harvard.edu (Postfix, from userid 501)
	id 4C2B53E8142; Thu, 23 Jun 2005 08:16:19 -0400 (EDT)
To: iesg@ietf.org, routing-discussion@ietf.org, rtg-dir@ietf.org
Message-Id: <20050623121619.4C2B53E8142@newdev.harvard.edu>
Date: Thu, 23 Jun 2005 08:16:19 -0400 (EDT)
From: sob@harvard.edu (Scott Bradner)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Subject: Re: Reopening jumbo frames in IS-IS
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2


Tony reported:
> Sorry, but I was explicitly told to stop work.

Tony is quite correct

Erik then opined:
> My recollection is that the feedback from IEEE 802 was that we shouldn't 
> touch non-standard things like jumbo-frames, and as a result nothing 
> more was done in this area.
> 
> Perhaps we asked a suboptimal question back then; whether IEEE 802 liked 
> the idea of us doing something for jumboframes and IS-IS. Had we instead 
> asked them whether they were going to specify how jumboframes work with 
> IS-IS, we would probably have received a different answer.

my discussions with the IEEE at that time mentioned IS-IS but that 
was not a factor in the exchange - the IEEE said flatly that 
	1/ jumbo frames for Ethernet were not gonna happen in the IEEE
	2/ they did not want the IETF to make a standard that
	   defined or assumed jumbo frames on Ethernet

re: Erik's suggested question - in effect they did answer that question
'no - they were not going to specify how jumboframes work at all
(nevermind with IS-IS) and please do not that that answer to mean that
the IETF should do so'

Scott

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Thu Jun 23 08:46:55 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA05862
	for <routing-discussion-archive@ietf.org>; Thu, 23 Jun 2005 08:46:55 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlRUx-0001tb-LQ
	for routing-discussion-archive@ietf.org; Thu, 23 Jun 2005 09:12:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlR55-0002dL-H9; Thu, 23 Jun 2005 08:45:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlR51-0002d9-6b; Thu, 23 Jun 2005 08:45:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA05227;
	Thu, 23 Jun 2005 08:41:45 -0400 (EDT)
Received: from imo-d01.mx.aol.com ([205.188.157.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlRPv-0001X5-5K; Thu, 23 Jun 2005 09:06:55 -0400
Received: from ewgray2k@netscape.net
	by imo-d01.mx.aol.com (mail_out_v38_r1.7.) id 7.c2.10b588af (22682);
	Thu, 23 Jun 2005 08:41:21 -0400 (EDT)
Received: from [192.168.7.131] (c-24-61-197-198.hsd1.nh.comcast.net
	[24.61.197.198]) by air-in04.mx.aol.com (v106.2) with ESMTP id
	MAILININ43-589a42baadf0170; Thu, 23 Jun 2005 08:41:21 -0400
Message-ID: <42BAADE8.6060802@netscape.net>
Date: Thu, 23 Jun 2005 08:41:12 -0400
From: Eric W Gray <ewgray2k@netscape.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: margaret@thingmagic.com
References: <BE36D687C8CBFA4AB76F5CD3E3C0FB4E0402B28E@aa-exchange.corp.nexthop.com>
	<p06200790bedf4b3a789e@[10.0.0.171]>
In-Reply-To: <p06200790bedf4b3a789e@[10.0.0.171]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AOL-IP: 24.61.197.198
X-Mailer: Unknown (No Version)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 48472a944c87678fcfe8db15ffecdfff
Content-Transfer-Encoding: 7bit
Cc: Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org, iesg@ietf.org,
        routing-discussion@ietf.org, rtg-chairs@ietf.org,
        Adrian Farrel <adrian@olddog.co.uk>,
        Brian E Carpenter <brc@zurich.ibm.com>,
        Susan Hares <shares@nexthop.com>
Subject: Re: Fwd: Re: WG Review: Transparent Interconnection of Lots of Links
 (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ewgray@GraIyMage.com
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ccfb4541e989aa743998098cd315d0fd
Content-Transfer-Encoding: 7bit

Margaret,

    The interesting thing here is that any changes in the encapsulation 
of Ethernet
frames would have drastic implications on all Ethernet equipment - 
including NIC
cards in Ethernet end stations. If this is not the case, then we are 
talking about an
encapsulation of a transport segment, rather than encapsulation 
end-to-end. If that
is what we are talking about, how does this "encapsulation" differ from 
Martini?

    Because of these considerations, I had assumed that what we would be 
doing
in the alleged TRILL working group is specifying how Ethernet (MAC) address
reachability would be advertised in an OSPF-like routing protocol. For 
the sake
of simplifying the discussion, let's assume that it would be OSPF 
instead of an off
the cuff spinout of a generic link state routing protocol.

    If the intent is to specify the use of the OSPF routing protocol to 
advertise MAC
reachability - as it certainly seems to be - then the same argument you 
make for this
work in the IETF applies to doing it in the Routing Area as well. That 
is where the
specific expertise lies.

    On the other hand, if the intent is to specify yet another L2 
encapsulation - which
could be used as an argument for doing this in the Internet Area - then 
the alleged
expertise (for yet another L2 encapsulation) is no more specific to the 
IETF than to
any other organization you might care to name.

    My general impression from the discussion is that we may have been 
successful
in playing word games with IEEE on this score where we have not been 
anywhere
near as successful in a similar context previously. If that is the case, 
then those who
have been successful in this should be congratulated for their ability 
to bandy words
- if not necessarily for their intentions in doing so.

    It also looks to me like some people want to do this work and - 
because they
have to go to the IETF anyway - they want to do it in the IETF. Frankly, 
I think
we might be able to make an argument for doing this work in the IETF - 
but only
if we simultaneously acknowledge that it should be doen in the Routing Area.

    One of the things that doing it this way might help to do is 
eliminate some of the
energy being poured into this effort that is apparently based - at least 
in part - on
some agenda(s) not shared with the IETF as a whole.

    Just to be crystal clear, I think it is obvious that some of the 
IETF leadership
wants to do this work. I also think it is clear that a lot of people 
want this work to
be done somewhere. And it should also be clear that not everyone in the 
IETF is
convinced that the IETF is the place to do it - irrespective of whether 
or not the
IEEE wants to play in the same sandbox too. But - if we're going to do 
it in the
IETF, let's do it in the right Area.

--
Eric

margaret@thingmagic.com wrote:

>
> Hi Sue,
>
> The TRILL WG would not be chartered to develop a link-state routing 
> protocol.  They would be chartered to make use of an existing 
> link-state routing protocol, and any extensions or modifications to 
> that protocol would be referred to the appropriate routing area WG.
>
> The TRILL WG would  determine the mechanisms for encapsulating and 
> forwarding Ethernet frames and for auto-configuring the rbridges.  I 
> am not sure that in-depth expertise in link-state routing protocols is 
> needed for that.  Instead, you need expertise in encapsulation, 
> forwarding and configuration, which are all Internet area topics.
>
> Margaret
>
>
> At 12:27 PM -0400 6/22/05, Susan Hares wrote:
>
>> Margaret:
>>
>> I suggest that the expertise in the link state is in the Routing area of
>> the IETF.  If it belongs in the IETF due to expertise, it belongs in the
>> Routing.
>>
>> Critical early review has been determined to be key to a quickly
>> deployed specification.
>>
>> Sue
>>
>> -----Original Message-----
>> From: Margaret Wasserman [mailto:margaret@thingmagic.com]
>> Sent: Wednesday, June 22, 2005 8:57 AM
>> To: Adrian Farrel; Brian E Carpenter
>> Cc: Tony Li; Alex Zinin; rtg-dir@ietf.org; iesg@ietf.org;
>> routing-discussion@ietf.org; rtg-chairs@ietf.org; Susan Hares
>> Subject: Re: Fwd: Re: WG Review: Transparent Interconnection of Lots of
>> Links (trill)
>>
>>
>> Hi Adrian,
>>
>> At 1:22 PM +0100 6/22/05, Adrian Farrel wrote:
>>
>>> I think the skill-set to which Brian refers is link state routing.
>>
>> (Care
>>
>>> to confirm, Brian?)
>>
>>
>> Yes, expertise in link-state routing is certainly one reason why this
>> work could be seen as more in-scope for the IETF than for the IEEE.
>> Also, frankly, there is interest in the IETF in doing this work (a
>> link-state-based Ethernet routing solution), while the IEEE is
>> continuing to pursue (R)STP-based approaches.
>>
>>> If so, why is this WG targeted at the Internet Area not the Routing
>>
>> area?
>>
>> This questions has been discussed in the IESG, as well, and we did
>> not have 100% agreement regarding the area in which this work belongs.
>>
>> Personally, I think that TRILL is a better fit for the Internet area,
>> and I will explain why...
>>
>> Traditionally, the division between the Internet area and the Routing
>> area has been that the Routing area deals with protocols that
>> distribute routing information (routes/labels) and the Internet area
>> has been responsible for the forwarding behaviour and encapsulation
>> mechanisms that make use of that information.
>>
>> The TRILL charter maintains that split -- any work on the routing
>> protocols themselves would be done in the routing area, while the
>> encapsulation/forwarding mechanism would be developed in the Internet
>> area.
>>
>> Perhaps you have a different model of the division between the
>> Routing and Internet areas that makes you think otherwise?
>>
>> The IESG discussed this issue several months ago.  We agreed that
>> this work is close to the line between Internet and Routing, but we
>> reached an agreement that it would best be placed in the Internet
>> area, with the understanding that we would appoint a technical
>> advisor and a WG co-chair with routing expertise.  BIll Fenner
>> volunteered to be the Technical Advisor, and Bill and Alex took an
>> action item to return with a list of potential co-chairs.
>>
>> Ultimately, I am not sure that it matters all that much which area
>> this work is done in, since it will require expertise and involvement
>> from both areas in order to succeed.
>>
>> Margaret
>
>
>
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www1.ietf.org/mailman/listinfo/routing-discussion


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Thu Jun 23 09:04:16 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07197
	for <routing-discussion-archive@ietf.org>; Thu, 23 Jun 2005 09:04:16 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlRll-0002g8-0n
	for routing-discussion-archive@ietf.org; Thu, 23 Jun 2005 09:29:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlRMn-0005oR-Lt; Thu, 23 Jun 2005 09:03:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlRMl-0005oE-VN; Thu, 23 Jun 2005 09:03:36 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07116;
	Thu, 23 Jun 2005 09:03:34 -0400 (EDT)
Received: from motgate5.mot.com ([144.189.100.105])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlRl5-0002aF-9S; Thu, 23 Jun 2005 09:28:44 -0400
Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233])
	by motgate5.mot.com (8.12.11/Motgate5) with ESMTP id j5ND98q9006682;
	Thu, 23 Jun 2005 06:09:08 -0700 (MST)
Received: from ma19exm01.e6.bcs.mot.com (ma19exm01.e6.bcs.mot.com [10.14.33.5])
	by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id j5ND7U19020119;
	Thu, 23 Jun 2005 08:07:31 -0500 (CDT)
Received: by ma19exm01.e6.bcs.mot.com with Internet Mail Service (5.5.2657.72)
	id <KPGZAXVT>; Thu, 23 Jun 2005 09:03:18 -0400
Message-ID: <62173B970AE0A044AED8723C3BCF238109316D56@ma19exm01.e6.bcs.mot.com>
From: Eastlake III Donald-LDE008 <Donald.Eastlake@motorola.com>
To: "'sob@harvard.edu'" <sob@harvard.edu>, iesg@ietf.org,
        routing-discussion@ietf.org
Date: Thu, 23 Jun 2005 09:03:15 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Subject: RE: Reopening jumbo frames in IS-IS
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081

It may not be very jumbo, but there now seems to be an effort underway in IEEE 802.3 for some expansion of Ethernet frames. See the web site for the Frame Expansion Task Force at http://grouper.ieee.org/groups/802/3/as/index.html. Their objectives are summarized at
http://grouper.ieee.org/groups/802/3/as/public/802_3as_objectives_0411.pdf.

Donald

-----Original Message-----
From: routing-discussion-bounces@ietf.org [mailto:routing-discussion-bounces@ietf.org] On Behalf Of sob@harvard.edu
Sent: Thursday, June 23, 2005 8:16 AM
To: iesg@ietf.org; routing-discussion@ietf.org; rtg-dir@ietf.org
Subject: Re: Reopening jumbo frames in IS-IS

Tony reported:
> Sorry, but I was explicitly told to stop work.

Tony is quite correct

Erik then opined:
> My recollection is that the feedback from IEEE 802 was that we shouldn't 
> touch non-standard things like jumbo-frames, and as a result nothing 
> more was done in this area.
> 
> Perhaps we asked a suboptimal question back then; whether IEEE 802 liked 
> the idea of us doing something for jumboframes and IS-IS. Had we instead 
> asked them whether they were going to specify how jumboframes work with 
> IS-IS, we would probably have received a different answer.

my discussions with the IEEE at that time mentioned IS-IS but that 
was not a factor in the exchange - the IEEE said flatly that 
	1/ jumbo frames for Ethernet were not gonna happen in the IEEE
	2/ they did not want the IETF to make a standard that
	   defined or assumed jumbo frames on Ethernet

re: Erik's suggested question - in effect they did answer that question
'no - they were not going to specify how jumboframes work at all
(nevermind with IS-IS) and please do not that that answer to mean that
the IETF should do so'

Scott

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Thu Jun 23 09:23:25 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09351
	for <routing-discussion-archive@ietf.org>; Thu, 23 Jun 2005 09:23:25 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlS4J-0003fT-MA
	for routing-discussion-archive@ietf.org; Thu, 23 Jun 2005 09:48:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlRe9-0000n1-BF; Thu, 23 Jun 2005 09:21:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlRe6-0000mc-MM; Thu, 23 Jun 2005 09:21:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09182;
	Thu, 23 Jun 2005 09:21:24 -0400 (EDT)
Received: from [204.9.221.21] (helo=thingmagic.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlS2H-0003XP-Ux; Thu, 23 Jun 2005 09:46:34 -0400
Received: from [66.30.121.250] (account margaret HELO [10.0.0.171])
	by thingmagic.com (CommuniGate Pro SMTP 4.1.8)
	with ESMTP-TLS id 400379; Thu, 23 Jun 2005 09:16:03 -0400
Mime-Version: 1.0
Message-Id: <p062007a9bee061b78c79@[10.0.0.171]>
In-Reply-To: <42BAADE8.6060802@netscape.net>
References: <BE36D687C8CBFA4AB76F5CD3E3C0FB4E0402B28E@aa-exchange.corp.nexthop.com>
	<p06200790bedf4b3a789e@[10.0.0.171]> <42BAADE8.6060802@netscape.net>
Date: Thu, 23 Jun 2005 09:20:21 -0400
To: ewgray@GraIyMage.com
From: Margaret Wasserman <margaret@thingmagic.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2086112c730e13d5955355df27e3074b
Cc: Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org, iesg@ietf.org,
        routing-discussion@ietf.org, rtg-chairs@ietf.org,
        Adrian Farrel <adrian@olddog.co.uk>,
        Brian E Carpenter <brc@zurich.ibm.com>,
        Susan Hares <shares@nexthop.com>
Subject: Re: Fwd: Re: WG Review: Transparent Interconnection of Lots of
 Links  (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243


Hi Eric,

At 8:41 AM -0400 6/23/05, Eric W Gray wrote:
>    If the intent is to specify the use of the OSPF routing protocol 
>to advertise MAC
>reachability - as it certainly seems to be - then the same argument 
>you make for this
>work in the IETF applies to doing it in the Routing Area as well. 
>That is where the
>specific expertise lies.

Determining how the Ethernet addresses would be advertised in OSPF 
(or IS-IS) would be done in the appropriate Routing area WG 
(presumably the OSPF or IS-IS WG).  I believe that we are in 
agreement about where this expertise lies.

>    On the other hand, if the intent is to specify yet another L2 
>encapsulation - which
>could be used as an argument for doing this in the Internet Area - 
>then the alleged
>expertise (for yet another L2 encapsulation) is no more specific to 
>the IETF than to
>any other organization you might care to name.

I have seen plenty of bad encapsulations.  If expertise is not 
required, then perhaps the people who wrote the bad encapsulations 
(ones that failed to consider MTU/fragmentation issues, for example) 
were just sloppy?

>    My general impression from the discussion is that we may have 
>been successful
>in playing word games with IEEE on this score where we have not been anywhere
>near as successful in a similar context previously. If that is the 
>case, then those who
>have been successful in this should be congratulated for their 
>ability to bandy words
>- if not necessarily for their intentions in doing so.

Your paragraph seems to assume that the IETF and the IEEE both wanted 
to do this work, and we somehow _won_ the right to do it through some 
negotiation.  This isn't the case at all.  There are some people in 
the IETF who wanted to do this work. The IEEE is not interested in 
doing this work, preferring to continue their work on (R)STP-based 
solutions.  We (the IESG) initiated a discussion with the IEEE 802 
leadership about this topic, and the IEEE leadership did not object 
to this work being done in the IETF.

We have been (and continue to be) a bit concerned about whether there 
are sufficient quantities of the right expertise in the IETF to do 
this work well.  However, responses to technical discussions on the 
TRILL list have been quite good, and there does seem to be a core 
group of well-qualified people committed to this work.

>    It also looks to me like some people want to do this work and - 
>because they
>have to go to the IETF anyway - they want to do it in the IETF. 
>Frankly, I think
>we might be able to make an argument for doing this work in the IETF 
>- but only
>if we simultaneously acknowledge that it should be doen in the Routing Area.
>
>    One of the things that doing it this way might help to do is 
>eliminate some of the
>energy being poured into this effort that is apparently based - at 
>least in part - on
>some agenda(s) not shared with the IETF as a whole.

It is not clear to me what motivations you are ascribing to whom.  If 
you think that there is a possibility of any type of misconduct or 
gaming of the system here, perhaps you could be more explicit?

>    Just to be crystal clear, I think it is obvious that some of the 
>IETF leadership
>wants to do this work. I also think it is clear that a lot of people 
>want this work to
>be done somewhere. And it should also be clear that not everyone in 
>the IETF is
>convinced that the IETF is the place to do it - irrespective of 
>whether or not the
>IEEE wants to play in the same sandbox too. But - if we're going to 
>do it in the
>IETF, let's do it in the right Area.

I am a bit concerned about this paragraph, because you seem to be 
indicating that "some members of the IETF leadership" are doing 
something underhanded here.  Personally, I think that the TRILL 
proposal is technically interesting and may benefit the Internet.  I 
also respect the key contributors to this effort.  I have advocated 
for this work because it was brought to me, and because I believe 
that it would be a good thing to do.  This is how most IETF efforts 
get started, and I don't think that there is anything unethical going 
on here.  Do you think otherwise?

If the IESG decides to charter this work (we are considering that on 
our telechat today), then the IESG will need to decide in which area 
to charter it.  I don't consider this choice to be as black-and-white 
as you apparently do.  However, I do think that the work itself (what 
the TRILL WG would be doing, not what the link-state routing protocol 
WG would need to do) is more closely related to other INT area 
efforts (such as L2VPN) than it is to the routing area.

Your comments about the "alleged expertise" required to design an L2 
encapsulation, and the fact that you didn't mention the configuration 
aspects of this work indicate to me that you may be underestimating 
the amount and complexity of the non-routing-protocol work involved 
in this effort.

Just so that you understand, I am not planning to be the responsible 
AD for this work, and it is not an issue to me whether the 
responsible AD is Mark, Bill or Alex (I trust all of them, and I 
believe that they all have the expertise to do a good job here).  The 
decision about where to place this work should be based, IMO, on 
where it belongs in the current structure of the IETF areas, and I 
personally see it as more appropriate for the INT area.  I understand 
that you see it differently, and some other people share your view. 
This is something that we will have to work out in the IESG if we 
decide to charter the group.

Thank you for your input, and I hope that you will consider being 
involved in the resulting WG, regardless of the area in which it is 
chartered.

Margaret

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Thu Jun 23 10:22:49 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15965
	for <routing-discussion-archive@ietf.org>; Thu, 23 Jun 2005 10:22:49 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlSzo-0006Uv-1c
	for routing-discussion-archive@ietf.org; Thu, 23 Jun 2005 10:48:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlSVp-0002r7-DD; Thu, 23 Jun 2005 10:17:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlSVo-0002qr-EN; Thu, 23 Jun 2005 10:17:00 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14891;
	Thu, 23 Jun 2005 10:16:06 -0400 (EDT)
Received: from imo-d02.mx.aol.com ([205.188.157.34])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlStF-00067y-0J; Thu, 23 Jun 2005 10:41:17 -0400
Received: from ewgray2k@netscape.net
	by imo-d02.mx.aol.com (mail_out_v38_r1.7.) id 7.e7.119e10e4 (22680);
	Thu, 23 Jun 2005 10:15:18 -0400 (EDT)
Received: from [192.168.7.131] (c-24-61-197-198.hsd1.nh.comcast.net
	[24.61.197.198]) by air-in04.mx.aol.com (v106.2) with ESMTP id
	MAILININ41-589842bac3f5c2; Thu, 23 Jun 2005 10:15:17 -0400
Message-ID: <42BAC3ED.4060305@netscape.net>
Date: Thu, 23 Jun 2005 10:15:09 -0400
From: Eric W Gray <ewgray2k@netscape.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Margaret Wasserman <margaret@thingmagic.com>
References: <BE36D687C8CBFA4AB76F5CD3E3C0FB4E0402B28E@aa-exchange.corp.nexthop.com>
	<p06200790bedf4b3a789e@[10.0.0.171]>
	<42BAADE8.6060802@netscape.net>
	<p062007a9bee061b78c79@[10.0.0.171]>
In-Reply-To: <p062007a9bee061b78c79@[10.0.0.171]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AOL-IP: 24.61.197.198
X-Mailer: Unknown (No Version)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d9238570526f12788af3d33c67f37625
Content-Transfer-Encoding: 7bit
Cc: Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org, iesg@ietf.org,
        routing-discussion@ietf.org, rtg-chairs@ietf.org,
        Adrian Farrel <adrian@olddog.co.uk>,
        Brian E Carpenter <brc@zurich.ibm.com>,
        Susan Hares <shares@nexthop.com>
Subject: Re: Fwd: Re: WG Review: Transparent Interconnection of Lots of Links
 (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ewgray@GraIyMage.com
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: bacfc6c7290e34d410f9bc22b825ce96
Content-Transfer-Encoding: 7bit

Margaret,

    What you did not answer is my initial comment about encapsulation.  
I will include
that again here:

"The interesting thing here is that any changes in the encapsulation of 
Ethernet
frames would have drastic implications on all Ethernet equipment - 
including NIC
cards in Ethernet end stations. If this is not the case, then we are 
talking about an
encapsulation of a transport segment, rather than encapsulation 
end-to-end. If that
is what we are talking about, how does this 'encapsulation' differ from 
Martini? "

    As this was my first paragraph, and it set the tone for the 
remaining comments,
omitting it may have been just a little disingenuous.

    Given that nobody has explained - as far as I know - what 
encapsulation changes
we expect to make (that are not covered by work already completed), your 
entire
argument about "encapsulation complexity" may be irrelevant.

    As for my specific references to word-smithing, this also requires 
an understanding
of the scope of intent to change Ethernet encapsulation. If we talk to 
the IEEE about
using OSPF to transport MAC address information, naturally they would be 
amenable
to specifying how that should be done in the IETF. But did we talk 
specifically about
introducing a new Ethernet encasulation when we talked to the IEEE?

    If we are not talking about a new (or changed) end-to-end Ethernet 
encapsulation,
then we are talking about tunneling encapsulation for L2 frames across 
part of the
network. If we plan to use L3/label encapsulation to do this, then we 
need to know
how this requirement differs from existing mechanisms (hence the Martini 
reference
that also is included in the text you omitted).

    If we are talking strictly about defining ways to use existing 
encapsulation in some
combination with extending routing protocols. then the work belongs in 
the Routing
Area, more than in the Internet Area.

    One other possibility is that we may be talking about single hop 
encapsulation for
OSPF-like advertisements in BPDU-like setup transactions. In this case, 
the expertise
you refer to does not exist in the IETF any more than it does elsewhere 
- since this is
not something that has been done before.

    My concern is that - if we are indeed talking about a replacement 
for Ethernet
encapsulation, then we will probably find out that the IEEE does care. 
The fact that
we intend to liase with the IEEE is good, but it will not help if it 
turns out that they do
not want us to proceed further after we have spent huge amounts of 
energy getting
to the point that everybody finally understands what it is that we 
intend to do.

--
Eric  

Margaret Wasserman wrote:

>
> Hi Eric,
>
> At 8:41 AM -0400 6/23/05, Eric W Gray wrote:
>
>>    If the intent is to specify the use of the OSPF routing protocol 
>> to advertise MAC
>> reachability - as it certainly seems to be - then the same argument 
>> you make for this
>> work in the IETF applies to doing it in the Routing Area as well. 
>> That is where the
>> specific expertise lies.
>
>
> Determining how the Ethernet addresses would be advertised in OSPF (or 
> IS-IS) would be done in the appropriate Routing area WG (presumably 
> the OSPF or IS-IS WG).  I believe that we are in agreement about where 
> this expertise lies.
>
>>    On the other hand, if the intent is to specify yet another L2 
>> encapsulation - which
>> could be used as an argument for doing this in the Internet Area - 
>> then the alleged
>> expertise (for yet another L2 encapsulation) is no more specific to 
>> the IETF than to
>> any other organization you might care to name.
>
>
> I have seen plenty of bad encapsulations.  If expertise is not 
> required, then perhaps the people who wrote the bad encapsulations 
> (ones that failed to consider MTU/fragmentation issues, for example) 
> were just sloppy?
>
>>    My general impression from the discussion is that we may have been 
>> successful
>> in playing word games with IEEE on this score where we have not been 
>> anywhere
>> near as successful in a similar context previously. If that is the 
>> case, then those who
>> have been successful in this should be congratulated for their 
>> ability to bandy words
>> - if not necessarily for their intentions in doing so.
>
>
> Your paragraph seems to assume that the IETF and the IEEE both wanted 
> to do this work, and we somehow _won_ the right to do it through some 
> negotiation.  This isn't the case at all.  There are some people in 
> the IETF who wanted to do this work. The IEEE is not interested in 
> doing this work, preferring to continue their work on (R)STP-based 
> solutions.  We (the IESG) initiated a discussion with the IEEE 802 
> leadership about this topic, and the IEEE leadership did not object to 
> this work being done in the IETF.
>
> We have been (and continue to be) a bit concerned about whether there 
> are sufficient quantities of the right expertise in the IETF to do 
> this work well.  However, responses to technical discussions on the 
> TRILL list have been quite good, and there does seem to be a core 
> group of well-qualified people committed to this work.
>
>>    It also looks to me like some people want to do this work and - 
>> because they
>> have to go to the IETF anyway - they want to do it in the IETF. 
>> Frankly, I think
>> we might be able to make an argument for doing this work in the IETF 
>> - but only
>> if we simultaneously acknowledge that it should be doen in the 
>> Routing Area.
>>
>>    One of the things that doing it this way might help to do is 
>> eliminate some of the
>> energy being poured into this effort that is apparently based - at 
>> least in part - on
>> some agenda(s) not shared with the IETF as a whole.
>
>
> It is not clear to me what motivations you are ascribing to whom.  If 
> you think that there is a possibility of any type of misconduct or 
> gaming of the system here, perhaps you could be more explicit?
>
>>    Just to be crystal clear, I think it is obvious that some of the 
>> IETF leadership
>> wants to do this work. I also think it is clear that a lot of people 
>> want this work to
>> be done somewhere. And it should also be clear that not everyone in 
>> the IETF is
>> convinced that the IETF is the place to do it - irrespective of 
>> whether or not the
>> IEEE wants to play in the same sandbox too. But - if we're going to 
>> do it in the
>> IETF, let's do it in the right Area.
>
>
> I am a bit concerned about this paragraph, because you seem to be 
> indicating that "some members of the IETF leadership" are doing 
> something underhanded here.  Personally, I think that the TRILL 
> proposal is technically interesting and may benefit the Internet.  I 
> also respect the key contributors to this effort.  I have advocated 
> for this work because it was brought to me, and because I believe that 
> it would be a good thing to do.  This is how most IETF efforts get 
> started, and I don't think that there is anything unethical going on 
> here.  Do you think otherwise?
>
> If the IESG decides to charter this work (we are considering that on 
> our telechat today), then the IESG will need to decide in which area 
> to charter it.  I don't consider this choice to be as black-and-white 
> as you apparently do.  However, I do think that the work itself (what 
> the TRILL WG would be doing, not what the link-state routing protocol 
> WG would need to do) is more closely related to other INT area efforts 
> (such as L2VPN) than it is to the routing area.
>
> Your comments about the "alleged expertise" required to design an L2 
> encapsulation, and the fact that you didn't mention the configuration 
> aspects of this work indicate to me that you may be underestimating 
> the amount and complexity of the non-routing-protocol work involved in 
> this effort.
>
> Just so that you understand, I am not planning to be the responsible 
> AD for this work, and it is not an issue to me whether the responsible 
> AD is Mark, Bill or Alex (I trust all of them, and I believe that they 
> all have the expertise to do a good job here).  The decision about 
> where to place this work should be based, IMO, on where it belongs in 
> the current structure of the IETF areas, and I personally see it as 
> more appropriate for the INT area.  I understand that you see it 
> differently, and some other people share your view. This is something 
> that we will have to work out in the IESG if we decide to charter the 
> group.
>
> Thank you for your input, and I hope that you will consider being 
> involved in the resulting WG, regardless of the area in which it is 
> chartered.
>
> Margaret
>
>
>

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Thu Jun 23 10:46:36 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18700
	for <routing-discussion-archive@ietf.org>; Thu, 23 Jun 2005 10:46:36 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlTMp-0007kA-VZ
	for routing-discussion-archive@ietf.org; Thu, 23 Jun 2005 11:11:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlSwU-0008GD-Of; Thu, 23 Jun 2005 10:44:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlSwT-0008DZ-3o; Thu, 23 Jun 2005 10:44:33 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18344;
	Thu, 23 Jun 2005 10:44:31 -0400 (EDT)
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlTKn-0007Z5-JU; Thu, 23 Jun 2005 11:09:43 -0400
Received: from rtp-core-1.cisco.com (64.102.124.12)
	by sj-iport-4.cisco.com with ESMTP; 23 Jun 2005 07:44:22 -0700
Received: from cisco.com (erosen-u10.cisco.com [161.44.70.36])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j5NEiHbd002444; 
	Thu, 23 Jun 2005 10:44:17 -0400 (EDT)
Message-Id: <200506231444.j5NEiHbd002444@rtp-core-1.cisco.com>
To: sob@harvard.edu (Scott Bradner)
In-reply-to: Your message of Thu, 23 Jun 2005 08:16:19 -0400.
	<20050623121619.4C2B53E8142@newdev.harvard.edu> 
User-Agent: EMH/1.14.1 SEMI/1.14.3 (Ushinoya) FLIM/1.14.3
	(=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.3
	(sparc-sun-solaris2.8) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Date: Thu, 23 Jun 2005 10:44:17 -0400
From: Eric Rosen <erosen@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: rtg-dir@ietf.org, iesg@ietf.org, routing-discussion@ietf.org
Subject: Re: Reopening jumbo frames in IS-IS 
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: erosen@cisco.com
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3


> they were not going to specify how jumboframes work at all
> (nevermind with IS-IS) and please do not that that answer to mean that
> the IETF should do so

Really, with regard to jumbo frames  the marketplace has spoken and the IEEE
has lost. Jumbo frames are a  defacto standard.  (Of course, just as happens
in theIETF,  the IEEE folks don't always  admit it when they've  lost out to
the marketplace.)

Given that  jumbo frames are  in use,  it seems silly  to say that  we can't
specify how to use them for IP protocols.  There is even some precedent; RFC
3032 (MPLS encaps)  mentions the possibility of using  ethernet frames which
contain 1504 or 1508 bytes.  

It's even sillier to say that (a) we're not allowed to do a carefully scoped
standard that solves a well-specified and immediate problem in the use of an
existing de  facto standard, but that (b)  it's fine to do  a standard which
tells folks to ignore IEEE entirely and do bridging in a completely new way.



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Thu Jun 23 11:24:38 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23653
	for <routing-discussion-archive@ietf.org>; Thu, 23 Jun 2005 11:24:38 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlTxe-0001Hh-CX
	for routing-discussion-archive@ietf.org; Thu, 23 Jun 2005 11:49:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlTZ2-0000wm-SF; Thu, 23 Jun 2005 11:24:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlTYy-0000wN-SP; Thu, 23 Jun 2005 11:24:23 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23609;
	Thu, 23 Jun 2005 11:24:12 -0400 (EDT)
Received: from nwkea-mail-2.sun.com ([192.18.42.14])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlTxA-0001Gl-6Y; Thu, 23 Jun 2005 11:49:24 -0400
Received: from jurassic.eng.sun.com ([129.146.58.166])
	by nwkea-mail-2.sun.com (8.12.10/8.12.9) with ESMTP id j5NFO8FF010911; 
	Thu, 23 Jun 2005 08:24:08 -0700 (PDT)
Received: from [192.9.61.11] (punchin-nordmark.SFBay.Sun.COM [192.9.61.11])
	by jurassic.eng.sun.com (8.13.4+Sun/8.13.4) with ESMTP id
	j5NFO4e3660036
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
	Thu, 23 Jun 2005 08:24:06 -0700 (PDT)
Message-ID: <42BAD431.8000403@sun.com>
Date: Thu, 23 Jun 2005 08:24:33 -0700
From: Erik Nordmark <erik.nordmark@sun.com>
User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050323)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ewgray@GraIyMage.com
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: 7bit
Cc: rtg-dir@ietf.org, iesg@ietf.org, routing-discussion@ietf.org,
        rtg-chairs@ietf.org
Subject: Re: Fwd: Re: WG Review: Transparent Interconnection of Lots of Links
 (trill)]
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit

[With reduced cc list]

Eric W Gray wrote:

>    The interesting thing here is that any changes in the encapsulation 
> of Ethernet
> frames would have drastic implications on all Ethernet equipment - 
> including NIC
> cards in Ethernet end stations. If this is not the case, then we are 
> talking about an
> encapsulation of a transport segment, rather than encapsulation 
> end-to-end. If that
> is what we are talking about, how does this "encapsulation" differ from 
> Martini?

Perhaps I can help answer this.

The encapsulation is not end-to-end; it is merely between the TRILL
devices. The draft-radia-rbridge draft shows the current thinking for
the encapsulation, with a header than in the case of carrying things
over Ethernet include
  - source rbridge MAC address (so that bridges between the rbridges
don't get confused)
  - next hop rbridge MAC address (to avoid proliferation should the
bridges flood the frame and multiple rbridges receive it)
  - ttl (to limit the damage from any temporary routing loops)
  - last hop rbridge (so that intermediate rbridges don't need to track
the location of each station)
  - Ethernet type

So this is quite different than the Martini approach.

Should TRILL later be expanded to apply to run over MPLS (something
which is not in the current charter) then I suspect we'd end up with an
encapsulation like Martini, and a link-state routing protocol carrying
the MAC addresses.

So the TRILL work is architecturally quite similar to the VPLS work in
L2VPN. The encapsulation that is safe and scalable for Ethernet is a key
difference.

    Erik

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Thu Jun 23 11:51:17 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26518
	for <routing-discussion-archive@ietf.org>; Thu, 23 Jun 2005 11:51:17 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlUNR-0002hP-64
	for routing-discussion-archive@ietf.org; Thu, 23 Jun 2005 12:16:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlTwt-0006p7-1f; Thu, 23 Jun 2005 11:49:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlTwq-0006nW-8r; Thu, 23 Jun 2005 11:49:00 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26412;
	Thu, 23 Jun 2005 11:48:57 -0400 (EDT)
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlULB-0002Xq-Tl; Thu, 23 Jun 2005 12:14:10 -0400
Received: from sj-core-3.cisco.com (171.68.223.137)
	by sj-iport-4.cisco.com with ESMTP; 23 Jun 2005 08:48:44 -0700
Received: from cliff.cisco.com (cliff.cisco.com [171.69.11.141])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id j5NFmf6p016373;
	Thu, 23 Jun 2005 08:48:42 -0700 (PDT)
Received: from [10.21.144.8] (sjc-vpn7-8.cisco.com [10.21.144.8]) by
	cliff.cisco.com (8.6.12/8.6.5) with ESMTP id IAA17342;
	Thu, 23 Jun 2005 08:48:41 -0700
Message-ID: <42BAD9D8.90903@tony.li>
Date: Thu, 23 Jun 2005 08:48:40 -0700
From: Tony Li <tony.li@tony.li>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Scott Bradner <sob@harvard.edu>
References: <20050623121619.4C2B53E8142@newdev.harvard.edu>
In-Reply-To: <20050623121619.4C2B53E8142@newdev.harvard.edu>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: 7bit
Cc: rtg-dir@ietf.org, iesg@ietf.org, routing-discussion@ietf.org
Subject: Re: Reopening jumbo frames in IS-IS
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: 7bit


Scott,

> 	2/ they did not want the IETF to make a standard that
> 	   defined or assumed jumbo frames on Ethernet

My understanding further extended that prohibition to any informational
or experimental RFC as well.  Those would have been (and still would be)
the best possible outcomes.  There was no requirement to make IS-IS over
jumbo frames into a standard.

Tony

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Thu Jun 23 11:57:13 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27061
	for <routing-discussion-archive@ietf.org>; Thu, 23 Jun 2005 11:57:12 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlUTA-000318-F9
	for routing-discussion-archive@ietf.org; Thu, 23 Jun 2005 12:22:25 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlU0x-0007NL-EU; Thu, 23 Jun 2005 11:53:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlU0v-0007Mz-Bq; Thu, 23 Jun 2005 11:53:13 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26675;
	Thu, 23 Jun 2005 11:53:11 -0400 (EDT)
Received: from newdev.eecs.harvard.edu ([140.247.60.212]
	helo=newdev.harvard.edu) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlUPH-0002pL-OD; Thu, 23 Jun 2005 12:18:23 -0400
Received: by newdev.harvard.edu (Postfix, from userid 501)
	id A21C13E8933; Thu, 23 Jun 2005 11:53:04 -0400 (EDT)
To: sob@harvard.edu, tony.li@tony.li
In-Reply-To: <42BAD9D8.90903@tony.li>
Message-Id: <20050623155304.A21C13E8933@newdev.harvard.edu>
Date: Thu, 23 Jun 2005 11:53:04 -0400 (EDT)
From: sob@harvard.edu (Scott Bradner)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Cc: rtg-dir@ietf.org, iesg@ietf.org, routing-discussion@ietf.org
Subject: Re: Reopening jumbo frames in IS-IS
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2

> My understanding further extended that prohibition to any informational
> or experimental RFC as well.

that was the case to start with, but as someone else pointed out,
a few years later the IEEE said that they would accept an info RFC
(thought they were not all that happy)

Scott


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Thu Jun 23 12:06:20 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28017
	for <routing-discussion-archive@ietf.org>; Thu, 23 Jun 2005 12:06:20 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlUc0-0003Va-CD
	for routing-discussion-archive@ietf.org; Thu, 23 Jun 2005 12:31:33 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlUCy-0001U9-9H; Thu, 23 Jun 2005 12:05:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlUCv-0001Tp-SZ; Thu, 23 Jun 2005 12:05:37 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27968;
	Thu, 23 Jun 2005 12:05:35 -0400 (EDT)
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlUbF-0003Ts-UO; Thu, 23 Jun 2005 12:30:48 -0400
Received: from sj-core-4.cisco.com (171.68.223.138)
	by sj-iport-5.cisco.com with ESMTP; 23 Jun 2005 09:05:20 -0700
X-IronPort-AV: i="3.93,224,1115017200"; 
	d="scan'208"; a="193706692:sNHT25529372"
Received: from cliff.cisco.com (cliff.cisco.com [171.69.11.141])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id j5NG5Ebp013083;
	Thu, 23 Jun 2005 09:05:15 -0700 (PDT)
Received: from [10.21.144.8] (sjc-vpn7-8.cisco.com [10.21.144.8]) by
	cliff.cisco.com (8.6.12/8.6.5) with ESMTP id JAA20712;
	Thu, 23 Jun 2005 09:05:14 -0700
Message-ID: <42BADDB9.9040406@tony.li>
Date: Thu, 23 Jun 2005 09:05:13 -0700
From: Tony Li <tony.li@tony.li>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Scott Bradner <sob@harvard.edu>
References: <20050623155304.A21C13E8933@newdev.harvard.edu>
In-Reply-To: <20050623155304.A21C13E8933@newdev.harvard.edu>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Content-Transfer-Encoding: 7bit
Cc: rtg-dir@ietf.org, iesg@ietf.org, routing-discussion@ietf.org
Subject: Re: Reopening jumbo frames in IS-IS
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit


>>My understanding further extended that prohibition to any informational
>>or experimental RFC as well.
> 
> that was the case to start with, but as someone else pointed out,
> a few years later the IEEE said that they would accept an info RFC
> (thought they were not all that happy)


First I hear of it.  In any case, I would very much like to progress the
work.  Given the non-standard status of jumbo frames, I have no problem
moving forward with informational or experimental as the goal.

Tony

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Thu Jun 23 12:29:19 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01412
	for <routing-discussion-archive@ietf.org>; Thu, 23 Jun 2005 12:29:19 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlUyG-0004ou-FE
	for routing-discussion-archive@ietf.org; Thu, 23 Jun 2005 12:54:32 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlUZC-0008IL-KH; Thu, 23 Jun 2005 12:28:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlUZ8-0008H1-SI; Thu, 23 Jun 2005 12:28:37 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01300;
	Thu, 23 Jun 2005 12:28:26 -0400 (EDT)
Received: from dns.nexthop.com ([65.247.36.216] helo=aa-mx1.nexthop.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlUxM-0004m1-Ha; Thu, 23 Jun 2005 12:53:40 -0400
Received: from localhost (localhost [127.0.0.1])
	by aa-mx1.nexthop.com (Postfix) with ESMTP
	id E42A22D5B0F; Thu, 23 Jun 2005 12:28:08 -0400 (EDT)
Received: from aa-mx1.nexthop.com ([127.0.0.1])
	by localhost (aa-mx1.nexthop.com [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id 30404-01-20; Thu, 23 Jun 2005 12:28:05 -0400 (EDT)
Received: from BOS-exch01.corp.nexthop.com (unknown [192.168.11.20])
	by aa-mx1.nexthop.com (Postfix) with ESMTP
	id C2B122D510C; Thu, 23 Jun 2005 11:47:10 -0400 (EDT)
Received: from aa-exchange1.corp.nexthop.com ([65.247.36.233]) by
	BOS-exch01.corp.nexthop.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Jun 2005 11:47:10 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 23 Jun 2005 11:47:07 -0400
Message-ID: <BE36D687C8CBFA4AB76F5CD3E3C0FB4E0402B447@aa-exchange.corp.nexthop.com>
Thread-Topic: Fwd: Re: WG Review: Transparent Interconnection of Lots of Links
	(trill)
thread-index: AcV39y3xYHVK+ghnRqWSf5EYctsVsQAEqUBg
From: "Susan Hares" <shares@nexthop.com>
To: "Margaret Wasserman" <margaret@thingmagic.com>, <ewgray@GraIyMage.com>
X-OriginalArrivalTime: 23 Jun 2005 15:47:10.0153 (UTC)
	FILETIME=[D1026B90:01C5780A]
X-Virus-Scanned: by amavisd-new at nexthop.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Content-Transfer-Encoding: quoted-printable
Cc: Alex Zinin <zinin@psg.com>, rtg-dir@ietf.org, iesg@ietf.org,
        routing-discussion@ietf.org, rtg-chairs@ietf.org,
        Adrian Farrel <adrian@olddog.co.uk>,
        Brian E Carpenter <brc@zurich.ibm.com>
Subject: RE: Fwd: Re: WG Review: Transparent Interconnection of Lots of
	Links (trill)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Content-Transfer-Encoding: quoted-printable

Margaret:=20

Does IETF have a formal relationship with IEEE?  The paragraphs from
your earlier mails have me a bit confused. =20

> Your paragraph seems to assume that the IETF and the IEEE both wanted=20
> to do this work, and we somehow _won_ the right to do it through some=20
> negotiation.  This isn't the case at all.  There are some people in=20
> the IETF who wanted to do this work. The IEEE is not interested in=20
> doing this work, preferring to continue their work on (R)STP-based=20
> solutions.  We (the IESG) initiated a discussion with the IEEE 802=20
> leadership about this topic, and the IEEE leadership did not object=20
> to this work being done in the IETF.

[....]=20

> We have been (and continue to be) a bit concerned about whether there=20
> are sufficient quantities of the right expertise in the IETF to do=20
> this work well.  However, responses to technical discussions on the=20
> TRILL list have been quite good, and there does seem to be a core=20
> group of well-qualified people committed to this work.

1st - I'm happy to contribute to this work in what ever forum it exists
in.

2nd - I would like to have this discussion end today (after IESG), but
it 	would be "way cool" and necessary to document who, what, when
and 	where in a document that you can post online about the IEEE/IETF
discussions.

3rd - It would be "way cool"/useful to summarize this discussion in a
document that is associated with the working group pages.

Shalom,=20

Sue Hares

(Still inspired by folks like you to make the IETF consistent!)



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Thu Jun 23 12:51:07 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03465
	for <routing-discussion-archive@ietf.org>; Thu, 23 Jun 2005 12:51:06 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlVJM-0005xJ-2z
	for routing-discussion-archive@ietf.org; Thu, 23 Jun 2005 13:16:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlUtm-0003qJ-Vc; Thu, 23 Jun 2005 12:49:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DlUtm-0003q5-71
	for routing-discussion@megatron.ietf.org;
	Thu, 23 Jun 2005 12:49:54 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03261
	for <routing-discussion@ietf.org>; Thu, 23 Jun 2005 12:49:51 -0400 (EDT)
Received: from relay01.pair.com ([209.68.5.15])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DlVI5-0005ts-If
	for routing-discussion@ietf.org; Thu, 23 Jun 2005 13:15:04 -0400
Received: (qmail 36220 invoked from network); 23 Jun 2005 16:49:42 -0000
Received: from unknown (HELO workhorse.faster-light.net) (unknown)
	by unknown with SMTP; 23 Jun 2005 16:49:42 -0000
X-pair-Authenticated: 69.37.59.162
Received: from workhorse.faster-light.net (localhost.faster-light.net
	[127.0.0.1])
	by workhorse.faster-light.net (8.12.11/8.12.11) with ESMTP id
	j5NGnAkW046351; Thu, 23 Jun 2005 12:49:10 -0400 (EDT)
	(envelope-from curtis@workhorse.faster-light.net)
Message-Id: <200506231649.j5NGnAkW046351@workhorse.faster-light.net>
To: erosen@cisco.com
In-reply-to: Your message of "Thu, 23 Jun 2005 10:44:17 EDT."
	<200506231444.j5NEiHbd002444@rtp-core-1.cisco.com> 
Date: Thu, 23 Jun 2005 12:49:10 -0400
From: Curtis Villamizar <curtis@faster-light.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: rtg-dir@ietf.org, Scott Bradner <sob@harvard.edu>,
        routing-discussion@ietf.org, iesg@ietf.org
Subject: Re: Reopening jumbo frames in IS-IS 
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: curtis@faster-light.net
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c


In message <200506231444.j5NEiHbd002444@rtp-core-1.cisco.com>
Eric Rosen writes:
>  
>  
> > they were not going to specify how jumboframes work at all
> > (nevermind with IS-IS) and please do not that that answer to mean that
> > the IETF should do so
>  
> Really, with regard to jumbo frames  the marketplace has spoken and the IEEE
> has lost. Jumbo frames are a  defacto standard.  (Of course, just as happens
> in theIETF,  the IEEE folks don't always  admit it when they've  lost out to
> the marketplace.)
>  
> Given that  jumbo frames are  in use,  it seems silly  to say that  we can't
> specify how to use them for IP protocols.  There is even some precedent; RFC
> 3032 (MPLS encaps)  mentions the possibility of using  ethernet frames which
> contain 1504 or 1508 bytes.  
>  
> It's even sillier to say that (a) we're not allowed to do a carefully scoped
> standard that solves a well-specified and immediate problem in the use of an
> existing de  facto standard, but that (b)  it's fine to do  a standard which
> tells folks to ignore IEEE entirely and do bridging in a completely new way.


I have to agree that it is silly that IEEE does not acknowledge jumbo
frames.  The provider market has spoken and any large router or large
ethernet switch either implements jumbo frames or doesn't play in that
market.

The reason for jumbo frames is that packet fragmentation in the core
can destroy performance.  As long as MTUs larger than 1500 are in use,
and they are, and the provider POPs where they are handling very high
throughput interfaces of higher MTU, the ethernet MTU will be large
enough or ethernet won't be used.  Its as simple as that.

Lets not use the argument that IEEE should let IETF do things with
jumbo frames because they are allowing IETF to do something else.

Perhaps IETF can specify how ISIS works with the defacto ethernet-like
link layer protocol that happens to differ only in the MTU size and
make it informational.  Its not as if lack of an RFC has stopped any
implementations or deployments so far the benefit of anyone else that
wants to play it wouldn't hurt to provide an informational document.

Curtis

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Thu Jun 23 13:01:02 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04657
	for <routing-discussion-archive@ietf.org>; Thu, 23 Jun 2005 13:01:02 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlVSx-0006Xb-Hp
	for routing-discussion-archive@ietf.org; Thu, 23 Jun 2005 13:26:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlV3R-0006qS-0Z; Thu, 23 Jun 2005 12:59:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DlV3P-0006or-0H
	for routing-discussion@megatron.ietf.org;
	Thu, 23 Jun 2005 12:59:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04487
	for <routing-discussion@ietf.org>; Thu, 23 Jun 2005 12:59:48 -0400 (EDT)
Received: from relay01.pair.com ([209.68.5.15])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DlVRl-0006Qh-HZ
	for routing-discussion@ietf.org; Thu, 23 Jun 2005 13:25:01 -0400
Received: (qmail 39141 invoked from network); 23 Jun 2005 16:59:49 -0000
Received: from unknown (HELO workhorse.faster-light.net) (unknown)
	by unknown with SMTP; 23 Jun 2005 16:59:49 -0000
X-pair-Authenticated: 69.37.59.162
Received: from workhorse.faster-light.net (localhost.faster-light.net
	[127.0.0.1])
	by workhorse.faster-light.net (8.12.11/8.12.11) with ESMTP id
	j5NGxHbG046390; Thu, 23 Jun 2005 12:59:17 -0400 (EDT)
	(envelope-from curtis@workhorse.faster-light.net)
Message-Id: <200506231659.j5NGxHbG046390@workhorse.faster-light.net>
To: Tony Li <tony.li@tony.li>
In-reply-to: Your message of "Thu, 23 Jun 2005 08:48:40 PDT."
	<42BAD9D8.90903@tony.li> 
Date: Thu, 23 Jun 2005 12:59:17 -0400
From: Curtis Villamizar <curtis@faster-light.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: rtg-dir@ietf.org, Scott Bradner <sob@harvard.edu>,
        routing-discussion@ietf.org, iesg@ietf.org
Subject: Re: Reopening jumbo frames in IS-IS 
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: curtis@faster-light.net
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464


In message <42BAD9D8.90903@tony.li>
Tony Li writes:
>  
>  
> Scott,
>  
> > 	2/ they did not want the IETF to make a standard that
> > 	   defined or assumed jumbo frames on Ethernet
>  
> My understanding further extended that prohibition to any informational
> or experimental RFC as well.  Those would have been (and still would be)
> the best possible outcomes.  There was no requirement to make IS-IS over
> jumbo frames into a standard.
>  
> Tony


I think we should have just defied that and written and informational
document.  Its kind of silly for the IETF to expect vendors to keep
implementing toward expired internet-drafts long after a defacto
standard exists as is done all too often.

Lets face it.  Jumbo ethernet frames have been around and have been
widely implemented for about 10 years now.

Curtis

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Thu Jun 23 14:45:09 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15120
	for <routing-discussion-archive@ietf.org>; Thu, 23 Jun 2005 14:45:09 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlX5i-0003OT-A8
	for routing-discussion-archive@ietf.org; Thu, 23 Jun 2005 15:10:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlWcu-00010n-8Q; Thu, 23 Jun 2005 14:40:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DlWcq-0000wK-NE
	for routing-discussion@megatron.ietf.org;
	Thu, 23 Jun 2005 14:40:33 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14569
	for <routing-discussion@ietf.org>; Thu, 23 Jun 2005 14:40:30 -0400 (EDT)
Received: from relay03.pair.com ([209.68.5.17])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DlX1C-0003Be-51
	for routing-discussion@ietf.org; Thu, 23 Jun 2005 15:05:43 -0400
Received: (qmail 70504 invoked from network); 23 Jun 2005 18:40:24 -0000
Received: from unknown (HELO workhorse.faster-light.net) (unknown)
	by unknown with SMTP; 23 Jun 2005 18:40:24 -0000
X-pair-Authenticated: 69.37.59.162
Received: from workhorse.faster-light.net (localhost.faster-light.net
	[127.0.0.1])
	by workhorse.faster-light.net (8.12.11/8.12.11) with ESMTP id
	j5NIdp41046891; Thu, 23 Jun 2005 14:39:51 -0400 (EDT)
	(envelope-from curtis@workhorse.faster-light.net)
Message-Id: <200506231839.j5NIdp41046891@workhorse.faster-light.net>
To: Pekka Savola <pekkas@netcore.fi>
In-reply-to: Your message of "Thu, 23 Jun 2005 07:08:11 +0300."
	<Pine.LNX.4.61.0506230703020.25658@netcore.fi> 
Date: Thu, 23 Jun 2005 14:39:51 -0400
From: Curtis Villamizar <curtis@faster-light.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
Cc: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>, rbridge@postel.org,
        iesg@ietf.org, routing-discussion@ietf.org
Subject: Re: Fwd: Re: WG Review: Transparent Interconnection of Lots ofLinks
	(trill) 
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: curtis@faster-light.net
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2


Pekka,

We seem to be in agreement.

In message <Pine.LNX.4.61.0506230703020.25658@netcore.fi>
Pekka Savola writes:
>  
> On Wed, 22 Jun 2005, Manfredi, Albert E wrote:
> > But this seems to create confusion. Maybe I'm confused, but I don't
> > think TRILL is going after creating larger layer 2 nets at all, right?
> > Just attempting to do something more clever than a spanning tree for the
> > layer 2 catenet.
>  
> Maybe not intentionally, but I think that will be the result.  A usage 
> case that has been shown has been a hospital whose network (with 
> thousands of hosts) is a single broadcast domain.

Or the college campus with 30,000-50,000 student an increasing number
with laptops.  Bridging has already been considered somewhat of a
failure on some of the larger campuses in the ethernet days and in
those days there were far fewer comuputers.

> I think everyone can agree that instead of making such large broadcast 
> domains, the network should be split up by routing instead.

So we should look for a solution which is based on routing.  No sense
repeating a prior failed exercise.

> While TRILL would "fix" the usage case above so that using a single 
> broadcast domain would still "work", that would still be very bad 
> network design, and in the longer term, it would probably be 
> counter-productive.
>  
> (In our environment, what we've seen recently is *decrease* in the 
> size of broadcast domains/subnets due to the requirements to isolate 
> and filter the traffic from other hosts at the site.  Using a single 
> domain makes this security issue much worse.)

Security by subnet isolation isn't the best security practice
butsecuring the hosts and running the applications the user needs
often isn't possible (particularly if the hosts are microsoft based).
Therefore this is very common.  One place where bridging has come into
play is creating virtual subnets to connect people who work together
but are dispersed around a building and in doing so supporting this
form of security.

So there still are still good reasons to do bridging but large scale
connection of wireless (or wired) is not a good application of
bridging.

If this is the sort of application that is driving the bridging work,
then it makes perfect sense to just use IP and encapsulate the
ethernet frames in IP and don't worry about what does the routing.  It
could be RIP, OSPF, ISIS, BGP, or (unlikely) something else.  What is
needed then is a means to distribute the mapping of MAC address to the
IP address of the nearest participating switch.  OSPF itself, or ISIS
doesn't work over distances unless you set up tunneled adjacencies.
It would be simpler to have a protocol that allows logical adjacencies
and supports some form of flooding but has no need for any other
routing protocol feature and will never need to do an SPF.  This
doesn't scale well since a domain wide mapping of MAC to something is
needed, but it does the job for small domains.

This would for example, allow a people in the office on the west coast
to be on the same subnet as a people on the east coast (pick a country
or continent) with a scattering of people in other locations.  This
addresses the "desire" to do security by subnetting.  It also
accommodates the handful of PC applications that for some reason use
IP broadcast to discover other users (I think Lotus Notes has been
weened of that behaviour but there are others).  The solution being
offerred only works with adjacent boxes (unless tunneled, over GRE for
example).

Sound a bit like adding a simple protocol to do MAC to IP mapping and
using "Transparent Ethernet Bridging" over GRE?

> Pekka Savola                 "You each name yourselves king, yet the
> Netcore Oy                    kingdom bleeds."
> Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

This seems to be a case of a square peg and a round hole and the
search for a better hammer to address the problem.  Maybe its just the
way many IT departments want to do things.  

In Radia's introduction in the draft (draft-perlman-rbridge-03.txt) it
states "The design allows for zero configuration" which may be the
underlying problem that needs solving.  As is there are other ways to
get very close to a fixed router and DHCP server configuration.  You
only need one router per closet or two for redundancy, and you will
still need a DHCP server even with the rbridges.

Curtis

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Fri Jun 24 18:52:16 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04158
	for <routing-discussion-archive@ietf.org>; Fri, 24 Jun 2005 18:52:16 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlxQe-0008Tj-Ee
	for routing-discussion-archive@ietf.org; Fri, 24 Jun 2005 19:17:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dlx1W-0006hh-VX; Fri, 24 Jun 2005 18:51:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dlx1V-0006f4-AI; Fri, 24 Jun 2005 18:51:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04062;
	Fri, 24 Jun 2005 18:51:42 -0400 (EDT)
Received: from mtagate1.uk.ibm.com ([195.212.29.134])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlxQ6-0008SM-LJ; Fri, 24 Jun 2005 19:17:12 -0400
Received: from d06nrmr1407.portsmouth.uk.ibm.com
	(d06nrmr1407.portsmouth.uk.ibm.com [9.149.38.185])
	by mtagate1.uk.ibm.com (8.12.10/8.12.10) with ESMTP id j5OMpXrU127722; 
	Fri, 24 Jun 2005 22:51:33 GMT
Received: from d06av04.portsmouth.uk.ibm.com (d06av04.portsmouth.uk.ibm.com
	[9.149.37.216])
	by d06nrmr1407.portsmouth.uk.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id
	j5OMpXto255000; Fri, 24 Jun 2005 23:51:33 +0100
Received: from d06av04.portsmouth.uk.ibm.com (loopback [127.0.0.1])
	by d06av04.portsmouth.uk.ibm.com (8.12.11/8.13.3) with ESMTP id
	j5OMpWt4008709; Fri, 24 Jun 2005 23:51:33 +0100
Received: from mail-gw3.hursley.ibm.com (mail-gw3.hursley.ibm.com
	[9.20.131.251])
	by d06av04.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id
	j5OMpWXl008701; Fri, 24 Jun 2005 23:51:32 +0100
Received: from [9.20.136.27] (helo=sp15en17.hursley.ibm.com)
	by mail-gw3.hursley.ibm.com with esmtp (Exim 4.50)
	id 1Dlx1I-0000rM-KJ; Fri, 24 Jun 2005 23:51:32 +0100
Received: from zurich.ibm.com (sig-9-145-132-60.de.ibm.com [9.145.132.60])
	by sp15en17.hursley.ibm.com (AIX5.1/8.11.6p2/8.11.0) with SMTP id
	j5OMpVo93706; Fri, 24 Jun 2005 23:51:31 +0100
Message-ID: <42BC6EFE.5040407@zurich.ibm.com>
Date: Fri, 24 Jun 2005 22:37:18 +0200
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.6) Gecko/20040113
X-Accept-Language: en, fr, de
MIME-Version: 1.0
To: Tony Li <tony.li@tony.li>
References: <20050623155304.A21C13E8933@newdev.harvard.edu>
	<42BADDB9.9040406@tony.li>
In-Reply-To: <42BADDB9.9040406@tony.li>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 7bit
Cc: rtg-dir@ietf.org, Scott Bradner <sob@harvard.edu>,
        routing-discussion@ietf.org, iesg@ietf.org
Subject: Re: Reopening jumbo frames in IS-IS
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Content-Transfer-Encoding: 7bit

Tony Li wrote:
>>>My understanding further extended that prohibition to any informational
>>>or experimental RFC as well.
>>
>>that was the case to start with, but as someone else pointed out,
>>a few years later the IEEE said that they would accept an info RFC
>>(thought they were not all that happy)
> 
> 
> 
> First I hear of it.  In any case, I would very much like to progress the
> work.  Given the non-standard status of jumbo frames, I have no problem
> moving forward with informational or experimental as the goal.

This sounds like information to me, not like an experiment. So I'd support
the idea of aiming at an Informational RFC.

(Peanut gallery question - any other Informationals needed for jumbo frames,
or is IS-IS the only one that needs documenting?)

    Brian



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Fri Jun 24 19:53:39 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09646
	for <routing-discussion-archive@ietf.org>; Fri, 24 Jun 2005 19:53:39 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlyO2-000201-Oc
	for routing-discussion-archive@ietf.org; Fri, 24 Jun 2005 20:19:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dlxyx-000689-40; Fri, 24 Jun 2005 19:53:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dlxyu-00067m-EO; Fri, 24 Jun 2005 19:53:08 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09628;
	Fri, 24 Jun 2005 19:53:05 -0400 (EDT)
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DlyNU-0001zK-7m; Fri, 24 Jun 2005 20:18:33 -0400
Received: from sj-core-3.cisco.com (171.68.223.137)
	by sj-iport-5.cisco.com with ESMTP; 24 Jun 2005 16:52:42 -0700
X-IronPort-AV: i="3.93,229,1115017200"; 
	d="scan'208"; a="194169663:sNHT26480122"
Received: from cliff.cisco.com (cliff.cisco.com [171.69.11.141])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id j5ONqd6p008688;
	Fri, 24 Jun 2005 16:52:39 -0700 (PDT)
Received: from [10.21.83.109] (sjc-vpn4-878.cisco.com [10.21.83.109]) by
	cliff.cisco.com (8.6.12/8.6.5) with ESMTP id QAA09365;
	Fri, 24 Jun 2005 16:52:39 -0700
Message-ID: <42BC9CC6.4000109@tony.li>
Date: Fri, 24 Jun 2005 16:52:38 -0700
From: Tony Li <tony.li@tony.li>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Brian E Carpenter <brc@zurich.ibm.com>
References: <20050623155304.A21C13E8933@newdev.harvard.edu>
	<42BADDB9.9040406@tony.li> <42BC6EFE.5040407@zurich.ibm.com>
In-Reply-To: <42BC6EFE.5040407@zurich.ibm.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Content-Transfer-Encoding: 7bit
Cc: rtg-dir@ietf.org, Scott Bradner <sob@harvard.edu>,
        routing-discussion@ietf.org, iesg@ietf.org
Subject: Re: Reopening jumbo frames in IS-IS
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit


> This sounds like information to me, not like an experiment. So I'd support
> the idea of aiming at an Informational RFC.

Thanks Brian.

> (Peanut gallery question - any other Informationals needed for jumbo
> frames,
> or is IS-IS the only one that needs documenting?)

I'm not aware of other significant protocols that are not using an
Ethertype encapsulation at this point, so no.

Tony

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Sat Jun 25 02:55:16 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00785
	for <routing-discussion-archive@ietf.org>; Sat, 25 Jun 2005 02:55:16 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dm4y8-0004Yw-7y
	for routing-discussion-archive@ietf.org; Sat, 25 Jun 2005 03:20:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dm4WQ-0005Co-KO; Sat, 25 Jun 2005 02:52:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dm4WO-0005Cb-1T; Sat, 25 Jun 2005 02:52:08 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00559;
	Sat, 25 Jun 2005 02:52:06 -0400 (EDT)
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dm4v2-0004V3-BN; Sat, 25 Jun 2005 03:17:38 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id j5P6pax25144;
	Sat, 25 Jun 2005 09:51:37 +0300
Date: Sat, 25 Jun 2005 09:51:36 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Tony Li <tony.li@tony.li>
In-Reply-To: <42BC9CC6.4000109@tony.li>
Message-ID: <Pine.LNX.4.61.0506250950030.25045@netcore.fi>
References: <20050623155304.A21C13E8933@newdev.harvard.edu>
	<42BADDB9.9040406@tony.li>
	<42BC6EFE.5040407@zurich.ibm.com> <42BC9CC6.4000109@tony.li>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: Brian E Carpenter <brc@zurich.ibm.com>, Scott Bradner <sob@harvard.edu>,
        routing-discussion@ietf.org, iesg@ietf.org
Subject: Re: Reopening jumbo frames in IS-IS
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581

On Fri, 24 Jun 2005, Tony Li wrote:
>> (Peanut gallery question - any other Informationals needed for 
>> jumbo frames, or is IS-IS the only one that needs documenting?)
>
> I'm not aware of other significant protocols that are not using an
> Ethertype encapsulation at this point, so no.

But as the actual IP encapsulation in jumbo frames hasn't been 
specified officially anywhere, would that need to be done instead/in 
addition?  This would seem like an appendix for "IPvX over Ethernet" 
-like specifications..

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Sat Jun 25 02:58:42 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01027
	for <routing-discussion-archive@ietf.org>; Sat, 25 Jun 2005 02:58:42 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dm51S-0004dq-86
	for routing-discussion-archive@ietf.org; Sat, 25 Jun 2005 03:24:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dm4bw-0006Fv-K9; Sat, 25 Jun 2005 02:57:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dm4bt-0006DT-Jt; Sat, 25 Jun 2005 02:57:49 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00966;
	Sat, 25 Jun 2005 02:57:48 -0400 (EDT)
Received: from 63-197-255-158.ded.pacbell.net ([63.197.255.158]
	helo=sinett.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dm50Z-0004cH-Io; Sat, 25 Jun 2005 03:23:20 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 24 Jun 2005 23:57:33 -0700
Message-ID: <BB6D74C75CC76A419B6D6FA7C38317B281DB13@sinett-sbs.SiNett.LAN>
Thread-Topic: Reopening jumbo frames in IS-IS
Thread-Index: AcV5UtpjMbdgTLRoSQOYAaK0hqLz6QAAfY/A
From: "Vishwas Manral" <Vishwas@sinett.com>
To: "Pekka Savola" <pekkas@netcore.fi>, "Tony Li" <tony.li@tony.li>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: quoted-printable
Cc: Brian E Carpenter <brc@zurich.ibm.com>, Scott Bradner <sob@harvard.edu>,
        routing-discussion@ietf.org, iesg@ietf.org
Subject: RE: Reopening jumbo frames in IS-IS
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: quoted-printable

Hi,=20

Another one I can think of is L2-LWAPP (non-routing stuff), though it
hasn't been standardized yet by CAPWAP WG.

Thanks,
Vishwas
-----Original Message-----
From: routing-discussion-bounces@ietf.org
[mailto:routing-discussion-bounces@ietf.org] On Behalf Of Pekka Savola
Sent: Saturday, June 25, 2005 12:22 PM
To: Tony Li
Cc: Brian E Carpenter; Scott Bradner; routing-discussion@ietf.org;
iesg@ietf.org
Subject: Re: Reopening jumbo frames in IS-IS

On Fri, 24 Jun 2005, Tony Li wrote:
>> (Peanut gallery question - any other Informationals needed for=20
>> jumbo frames, or is IS-IS the only one that needs documenting?)
>
> I'm not aware of other significant protocols that are not using an
> Ethertype encapsulation at this point, so no.

But as the actual IP encapsulation in jumbo frames hasn't been=20
specified officially anywhere, would that need to be done instead/in=20
addition?  This would seem like an appendix for "IPvX over Ethernet"=20
-like specifications..

--=20
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Sat Jun 25 04:06:04 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04355
	for <routing-discussion-archive@ietf.org>; Sat, 25 Jun 2005 04:06:04 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dm64f-0006C1-FI
	for routing-discussion-archive@ietf.org; Sat, 25 Jun 2005 04:31:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dm5eK-0004Af-MZ; Sat, 25 Jun 2005 04:04:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dm5eI-00048n-ML; Sat, 25 Jun 2005 04:04:22 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04226;
	Sat, 25 Jun 2005 04:04:19 -0400 (EDT)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dm62x-00069S-27; Sat, 25 Jun 2005 04:29:52 -0400
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-3.cisco.com with ESMTP; 25 Jun 2005 01:04:06 -0700
X-IronPort-AV: i="3.93,229,1115017200"; 
	d="scan'208"; a="282925417:sNHT27603740"
Received: from cliff.cisco.com (cliff.cisco.com [171.69.11.141])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j5P842VX008348;
	Sat, 25 Jun 2005 01:04:03 -0700 (PDT)
Received: from [10.21.83.109] (sjc-vpn4-878.cisco.com [10.21.83.109]) by
	cliff.cisco.com (8.6.12/8.6.5) with ESMTP id BAA25523;
	Sat, 25 Jun 2005 01:03:58 -0700
Message-ID: <42BD0FEC.7040905@tony.li>
Date: Sat, 25 Jun 2005 01:03:56 -0700
From: Tony Li <tony.li@tony.li>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Pekka Savola <pekkas@netcore.fi>
References: <20050623155304.A21C13E8933@newdev.harvard.edu>
	<42BADDB9.9040406@tony.li> <42BC6EFE.5040407@zurich.ibm.com>
	<42BC9CC6.4000109@tony.li>
	<Pine.LNX.4.61.0506250950030.25045@netcore.fi>
In-Reply-To: <Pine.LNX.4.61.0506250950030.25045@netcore.fi>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 7bit
Cc: Brian E Carpenter <brc@zurich.ibm.com>, Scott Bradner <sob@harvard.edu>,
        routing-discussion@ietf.org, iesg@ietf.org
Subject: Re: Reopening jumbo frames in IS-IS
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit


>> I'm not aware of other significant protocols that are not using an
>> Ethertype encapsulation at this point, so no.
> 
> 
> But as the actual IP encapsulation in jumbo frames hasn't been specified
> officially anywhere, would that need to be done instead/in addition? 
> This would seem like an appendix for "IPvX over Ethernet" -like
> specifications..

Pekka,

I think that the IEEE would see that as an end-run around their process.
 And they would be right.

The documents that describe jumbo frames already suggest that everything
just runs as it would over normal frame sizes, so no additional
agreement is really necessary to achieve de facto interoperability.

Tony

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Sun Jun 26 12:16:16 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16124
	for <routing-discussion-archive@ietf.org>; Sun, 26 Jun 2005 12:16:16 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DmaCt-000454-26
	for routing-discussion-archive@ietf.org; Sun, 26 Jun 2005 12:42:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DmZXf-0001f2-BV; Sun, 26 Jun 2005 11:59:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DmZXd-0001eO-9R
	for routing-discussion@megatron.ietf.org;
	Sun, 26 Jun 2005 11:59:29 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05982
	for <routing-discussion@ietf.org>; Sun, 26 Jun 2005 11:59:25 -0400 (EDT)
Received: from relay02.pair.com ([209.68.5.16])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DmZwa-0001ND-39
	for routing-discussion@ietf.org; Sun, 26 Jun 2005 12:25:16 -0400
Received: (qmail 18445 invoked from network); 26 Jun 2005 15:59:21 -0000
Received: from unknown (HELO workhorse.faster-light.net) (unknown)
	by unknown with SMTP; 26 Jun 2005 15:59:21 -0000
X-pair-Authenticated: 69.37.59.162
Received: from workhorse.faster-light.net (localhost.faster-light.net
	[127.0.0.1])
	by workhorse.faster-light.net (8.12.11/8.12.11) with ESMTP id
	j5QG0iXk006764; Sun, 26 Jun 2005 12:00:44 -0400 (EDT)
	(envelope-from curtis@workhorse.faster-light.net)
Message-Id: <200506261600.j5QG0iXk006764@workhorse.faster-light.net>
To: Brian E Carpenter <brc@zurich.ibm.com>
In-reply-to: Your message of "Fri, 24 Jun 2005 22:37:18 +0200."
	<42BC6EFE.5040407@zurich.ibm.com> 
Date: Sun, 26 Jun 2005 12:00:44 -0400
From: Curtis Villamizar <curtis@faster-light.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Cc: rtg-dir@ietf.org, Scott Bradner <sob@harvard.edu>,
        routing-discussion@ietf.org, iesg@ietf.org
Subject: Re: Reopening jumbo frames in IS-IS 
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: curtis@faster-light.net
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0


In message <42BC6EFE.5040407@zurich.ibm.com>
Brian E Carpenter writes:
>  
> Tony Li wrote:
> >>>My understanding further extended that prohibition to any informational
> >>>or experimental RFC as well.
> >>
> >>that was the case to start with, but as someone else pointed out,
> >>a few years later the IEEE said that they would accept an info RFC
> >>(thought they were not all that happy)
> > 
> > 
> > 
> > First I hear of it.  In any case, I would very much like to progress the
> > work.  Given the non-standard status of jumbo frames, I have no problem
> > moving forward with informational or experimental as the goal.
>  
> This sounds like information to me, not like an experiment. So I'd support
> the idea of aiming at an Informational RFC.
>  
> (Peanut gallery question - any other Informationals needed for jumbo frames,
> or is IS-IS the only one that needs documenting?)
>  
>     Brian


Brian,

It probably would not hurt to have an informational draft describing
jumbo frames, the reason for needing a them, when to use them and
importantly when not to use them.

Jumbo frames exists only to avoid the performance drop that would
otherwise potentially cripple core networks using GbE or 10GbE and
aggregating higher MTU links.  Since jumbo frames could otherwise be
harmful, it might make sense to ask that equipment be capable of
forwarding jumbo frames but originate standard MTU frames (except when
verifying MTU such as in ISIS) and that end user devices such as NIC
cards never originate jumbo frames.  It should also be clearly stated
that jumbo frames be disabled by default and any equipment supporting
them at the very least put harsh warnings in the equipment's user
documentation about the feature being non-standard and has a potential
to cause interoperability problem if just casually enabled.

The fear of the IEEE folks might be that once word gets out of jumbo
frames a lot of people who don't really need them will be asking for
them and equipment in bridged environments won't be able to deal with
them.  In bridged environments fragmenting isn't a possibility and
today most equipment doesn't support jumbo frames, mainly just the
larger routers and switches sold into the large provider market.

(Peanut gallery answer.  Now all you need is an author.)

Curtis

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Sun Jun 26 13:35:44 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25897
	for <routing-discussion-archive@ietf.org>; Sun, 26 Jun 2005 13:35:44 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DmbRn-0006dQ-K6
	for routing-discussion-archive@ietf.org; Sun, 26 Jun 2005 14:01:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dmb1x-0004Av-GX; Sun, 26 Jun 2005 13:34:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dmb1v-0004Ak-S2; Sun, 26 Jun 2005 13:34:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25793;
	Sun, 26 Jun 2005 13:34:47 -0400 (EDT)
Received: from adsl-65-67-187-82.dsl.rcsntx.swbell.net
	([65.67.187.82] helo=defiant.dfw.nostrum.com ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DmbQs-0006br-2R; Sun, 26 Jun 2005 14:00:38 -0400
Received: from stephen (IDENT:sprunk@localhost [127.0.0.1])
	by defiant.dfw.nostrum.com (8.11.3/8.11.3) with SMTP id j5QHYMS16520;
	Sun, 26 Jun 2005 12:34:22 -0500
Message-ID: <015a01c57a75$4e1e7b70$6801a8c0@stephen>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: <curtis@faster-light.net>, "Brian E Carpenter" <brc@zurich.ibm.com>
References: <200506261600.j5QG0iXk006764@workhorse.faster-light.net>
Date: Sun, 26 Jun 2005 12:10:46 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.3790.1218
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1218
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: 7bit
Cc: rtg-dir@ietf.org, Scott Bradner <sob@harvard.edu>,
        routing-discussion@ietf.org, iesg@ietf.org
Subject: Re: Reopening jumbo frames in IS-IS 
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: 7bit

Thus spake "Curtis Villamizar" <curtis@faster-light.net>
> It probably would not hurt to have an informational draft describing
> jumbo frames, the reason for needing a them, when to use them and
> importantly when not to use them.
>
> Jumbo frames exists only to avoid the performance drop that would
> otherwise potentially cripple core networks using GbE or 10GbE
> and aggregating higher MTU links.  Since jumbo frames could
> otherwise be harmful, it might make sense to ask that equipment be
> capable of forwarding jumbo frames but originate standard MTU
> frames (except when verifying MTU such as in ISIS) and that end
> user devices such as NIC cards never originate jumbo frames.

That seems excessively restrictive.  There are many environments today using
jumbo frames (8k-10k MTU) on end hosts without problems.

This also begs for a definition of what exactly a "jumbo" frame is; does an
MPLS label (or several) on the front of a 1500-byte Ethernet frame count?
Does a packet on media with a >1500 byte native MTU count?  Should a host on
FDDI or a direct HDLC/PPP link be limited to 1500 byte packets -- even
though its native MTU is 4470 -- because we fear it might need to talk to an
Ethernet-connected host?

> It should also be clearly stated that jumbo frames be disabled by
> default and any equipment supporting them at the very least put
> harsh warnings in the equipment's user documentation about the
> feature being non-standard and has a potential to cause
> interoperability problem if just casually enabled.

I certainly agree that jumbo frames should be disabled by default, and the
warning should explicitly note that severe problems will result if hosts on
the same subnet have different ideas of what the MTU is.  I personally have
never seen a problem with jumbos when every device on a subnet supports them
and is configured with the same MTU, but perhaps someone else can offer some
enlightening anecdotes.

We might consider adding a means for hosts configured with a "jumbo" MTU to
determine if all of its neighbors (and intermediate L2 devices) can indeed
handle such packets.  If such a mechansim existed, we could allow jumbos to
be on by default since hosts could detect when it was necessary to fall back
to a non-jumbo MTU.

S

Stephen Sprunk      "Those people who think they know everything
CCIE #3723         are a great annoyance to those of us who do."
K5SSS                                             --Isaac Asimov


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Sun Jun 26 14:10:00 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28872
	for <routing-discussion-archive@ietf.org>; Sun, 26 Jun 2005 14:10:00 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dmbyy-0007OY-2z
	for routing-discussion-archive@ietf.org; Sun, 26 Jun 2005 14:35:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DmbYI-0001TF-Fk; Sun, 26 Jun 2005 14:08:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DmbYG-0001Sz-6J; Sun, 26 Jun 2005 14:08:16 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28715;
	Sun, 26 Jun 2005 14:08:14 -0400 (EDT)
Received: from parsley.amaranth.net ([204.10.1.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DmbxE-0007M8-J3; Sun, 26 Jun 2005 14:34:05 -0400
Received: from ancho.senie.com (c-24-34-19-2.hsd1.ma.comcast.net [24.34.19.2])
	(authenticated bits=0)
	by parsley.amaranth.net (8.12.11/8.12.11) with ESMTP id j5QI7rY9023067
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Sun, 26 Jun 2005 14:07:54 -0400
Message-Id: <6.2.3.4.2.20050626135052.07407810@mail.amaranth.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4
Date: Sun, 26 Jun 2005 13:59:37 -0400
To: "Stephen Sprunk" <stephen@sprunk.org>, <curtis@faster-light.net>,
        "Brian E Carpenter" <brc@zurich.ibm.com>
From: Daniel Senie <dts@senie.com>
In-Reply-To: <015a01c57a75$4e1e7b70$6801a8c0@stephen>
References: <200506261600.j5QG0iXk006764@workhorse.faster-light.net>
	<015a01c57a75$4e1e7b70$6801a8c0@stephen>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Virus-Scanned: ClamAV version 0.85.1,
	clamav-milter version 0.85 on parsley.amaranth.net
X-Virus-Status: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Cc: rtg-dir@ietf.org, Scott Bradner <sob@harvard.edu>,
        routing-discussion@ietf.org, iesg@ietf.org
Subject: Re: Reopening jumbo frames in IS-IS 
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976

At 01:10 PM 6/26/2005, Stephen Sprunk wrote:
>Thus spake "Curtis Villamizar" <curtis@faster-light.net>
> > It probably would not hurt to have an informational draft describing
> > jumbo frames, the reason for needing a them, when to use them and
> > importantly when not to use them.
> >
> > Jumbo frames exists only to avoid the performance drop that would
> > otherwise potentially cripple core networks using GbE or 10GbE
> > and aggregating higher MTU links.  Since jumbo frames could
> > otherwise be harmful, it might make sense to ask that equipment be
> > capable of forwarding jumbo frames but originate standard MTU
> > frames (except when verifying MTU such as in ISIS) and that end
> > user devices such as NIC cards never originate jumbo frames.
>
>That seems excessively restrictive.  There are many environments today using
>jumbo frames (8k-10k MTU) on end hosts without problems.

Indeed, it would seem to make sense for communications between front 
end and back end servers (e.g. app server to database cases). In 
controlled environments it should help boost database transactions, 
NFS and whatnot. This was certainly one reason FDDI was used in 
places in the past, as large frame sizes were permitted on that medium.


>This also begs for a definition of what exactly a "jumbo" frame is; does an
>MPLS label (or several) on the front of a 1500-byte Ethernet frame count?
>Does a packet on media with a >1500 byte native MTU count?  Should a host on
>FDDI or a direct HDLC/PPP link be limited to 1500 byte packets -- even
>though its native MTU is 4470 -- because we fear it might need to talk to an
>Ethernet-connected host?




> > It should also be clearly stated that jumbo frames be disabled by
> > default and any equipment supporting them at the very least put
> > harsh warnings in the equipment's user documentation about the
> > feature being non-standard and has a potential to cause
> > interoperability problem if just casually enabled.
>
>I certainly agree that jumbo frames should be disabled by default, and the
>warning should explicitly note that severe problems will result if hosts on
>the same subnet have different ideas of what the MTU is.  I personally have
>never seen a problem with jumbos when every device on a subnet supports them
>and is configured with the same MTU, but perhaps someone else can offer some
>enlightening anecdotes.
>
>We might consider adding a means for hosts configured with a "jumbo" MTU to
>determine if all of its neighbors (and intermediate L2 devices) can indeed
>handle such packets.  If such a mechansim existed, we could allow jumbos to
>be on by default since hosts could detect when it was necessary to fall back
>to a non-jumbo MTU.

Indeed, OSPF has had such a mechanism for years as a result of the 
existence of LAN media types with disparate MTUs (token ring, FDDI). 
Routers are permitted to pack LSAs into packets up to MTU size, and 
if another router on the LAN had a different MTU, significant 
problems resulted (and those problems could lie dormant in a live 
network for a long time before things broke, as it turned out).

It would certainly be worthwhile to have some means for testing. The 
trick is when a transport or routing session fails, some generic 
mechanism is really needed to think to ask the remote end for its 
MTU. That could be an ICMP message asking for MTU. Keep in mind, 
however, that a station which can't receive a frame due to MTU 
mismatch (recipient had MTU 1500, sender something bigger) will not 
even hear the frame (dropped at MAC level) so it can't respond with 
an error message.

The Ethernet MTU of 1500 allowed this issue to be ignored for a long 
time. Other media had issues with it, but they were mostly ignored as 
Ethernet dominated. It'd sure be nice if this were dealt with on a 
generic basis. Probably could have been piggybacked on ARP responses 
if there'd been a range of MTUs to worry about when ARP was proposed. Oh well.



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Sun Jun 26 15:45:08 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07897
	for <routing-discussion-archive@ietf.org>; Sun, 26 Jun 2005 15:45:07 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DmdT2-0001E4-Lw
	for routing-discussion-archive@ietf.org; Sun, 26 Jun 2005 16:11:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dmd33-00015J-Na; Sun, 26 Jun 2005 15:44:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dmd32-000154-3s; Sun, 26 Jun 2005 15:44:08 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07825;
	Sun, 26 Jun 2005 15:44:05 -0400 (EDT)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DmdS1-0001BP-AY; Sun, 26 Jun 2005 16:09:58 -0400
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-2.cisco.com with ESMTP; 26 Jun 2005 12:43:51 -0700
Received: from cliff.cisco.com (cliff.cisco.com [171.69.11.141])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j5QJhlVX012711;
	Sun, 26 Jun 2005 12:43:47 -0700 (PDT)
Received: from [10.21.99.23] (sjc-vpn1-791.cisco.com [10.21.99.23]) by
	cliff.cisco.com (8.6.12/8.6.5) with ESMTP id MAA04536;
	Sun, 26 Jun 2005 12:43:43 -0700
Message-ID: <42BF0568.5090708@tony.li>
Date: Sun, 26 Jun 2005 12:43:36 -0700
From: Tony Li <tony.li@tony.li>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: curtis@faster-light.net
References: <200506261600.j5QG0iXk006764@workhorse.faster-light.net>
In-Reply-To: <200506261600.j5QG0iXk006764@workhorse.faster-light.net>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: 7bit
Cc: rtg-dir@ietf.org, Brian E Carpenter <brc@zurich.ibm.com>,
        Scott Bradner <sob@harvard.edu>, routing-discussion@ietf.org,
        iesg@ietf.org
Subject: Re: Reopening jumbo frames in IS-IS
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: 7bit


> Jumbo frames exists only to avoid the performance drop that would
> otherwise potentially cripple core networks using GbE or 10GbE and
> aggregating higher MTU links.


Another, and perhaps more common, reason for jumbo frames is to support
high speed data center and storage applications.  Many modern systems
have an 8KB primary memory page size, and can be most efficient at bulk
transfers when they can make use of the page as a transfer unit.

Tony

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-bounces@ietf.org  Wed Jun 29 08:53:46 2005
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14993
	for <routing-discussion-archive@ietf.org>; Wed, 29 Jun 2005 08:53:46 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DncU7-000595-DZ
	for routing-discussion-archive@ietf.org; Wed, 29 Jun 2005 09:20:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dnc3L-0003p9-CV; Wed, 29 Jun 2005 08:52:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Dnc3J-0003p4-B5
	for routing-discussion@megatron.ietf.org;
	Wed, 29 Jun 2005 08:52:29 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14929
	for <routing-discussion@ietf.org>; Wed, 29 Jun 2005 08:52:28 -0400 (EDT)
From: avri@psg.com
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DncSr-000550-5E
	for routing-discussion@ietf.org; Wed, 29 Jun 2005 09:18:54 -0400
Received: from psg.com ([147.28.0.62] helo=[127.0.0.1])
	by psg.com with esmtp (Exim 4.50 (FreeBSD)) id 1Dnc3G-0001UA-OC
	for routing-discussion@ietf.org; Wed, 29 Jun 2005 12:52:26 +0000
Mime-Version: 1.0 (Apple Message framework v622)
Content-Transfer-Encoding: 7bit
Message-Id: <f43589b875b3ce26e8e33dd433e8ec69@psg.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: routing-discussion@ietf.org
Date: Wed, 29 Jun 2005 14:51:55 +0200
X-Mailer: Apple Mail (2.622)
X-Spam-Score: 0.3 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit
Subject: Resurrection of IRTF Routing RG list (and hopefully group)
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>, 
	<mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/routing-discussion>,
	<mailto:routing-discussion-request@ietf.org?subject=subscribe>
Sender: routing-discussion-bounces@ietf.org
Errors-To: routing-discussion-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: 7bit

Hi,

A few months ago, the RRG mailing list blinked out of existence.  It 
had been very inactive, so probably no one noticed (unless the decrease 
in spam was a clue).

In any case I am currently trying to get the list, and the RG,  active 
again.  While 1 of the subprojects seems to still be active, and while 
I have anecdotal evidence of there still being interest in the work of 
RRg, there was real silence on the list.

Anyway there is new list, which randy bush was kind enough to host.  
Unfortunately the old list of subscribers was lost, so there is 
currently only one subscriber on the new list; me.  Anyone who is 
interested in discussing, and getting involved, in Routing research is 
invited to join the new list.

To be added to the list, simply send a message to majordomo.
There are two ways to do it:

address--    To: rrg-request@psg.com
message--    subscribe

  OR

address--    To: majordomo@psg.com
message--    subscribe rrg

a.


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


