RE: [PWOT] mpls-in-ip
"tom worster" <tom@ennovatenetworks.com> Wed, 28 February 2001 16:33 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA11812 for <pwot-archive@odin.ietf.org>; Wed, 28 Feb 2001 11:33:00 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA25120; Wed, 28 Feb 2001 11:28:38 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA25090 for <pwot@ns.ietf.org>; Wed, 28 Feb 2001 11:28:37 -0500 (EST)
Received: from ennovatenetworks.com ([63.102.148.71]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA11635 for <pwot@ietf.org>; Wed, 28 Feb 2001 11:28:35 -0500 (EST)
Received: from tworster (dhcp114.tst.ennovatenetworks.com [10.1.3.114]) by ennovatenetworks.com (8.8.7/8.8.7) with SMTP id LAA22179; Wed, 28 Feb 2001 11:28:32 -0500 (EST) (envelope-from tom@ennovatenetworks.com)
From: tom worster <tom@ennovatenetworks.com>
To: erosen@cisco.com
Cc: "'PWOT Email List (E-mail)'" <pwot@ietf.org>, "'CEOT Email List (E-mail)'" <ceot@laurelnetworks.com>
Subject: RE: [PWOT] mpls-in-ip
Date: Wed, 28 Feb 2001 11:28:40 -0500
Message-ID: <006e01c0a1a3$83439740$7203010a@ennovatenetworks.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Importance: Normal
In-Reply-To: <200102281425.JAA27807@erosen-sun.cisco.com>
Content-Transfer-Encoding: 7bit
Sender: pwot-admin@ietf.org
Errors-To: pwot-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <pwot.ietf.org>
X-BeenThere: pwot@ietf.org
Content-Transfer-Encoding: 7bit
From: Eric Rosen [mailto:erosen@cisco.com] > > > 1) is an mpls lsp an example of a "pseudo-wire?" > > > 2) can ip be regarded as "transport?" > > I'm not sure this is the right approach. If we follow > this out, those > brainiacs in the IESG are likely to tell us that the MPLS > LSP has to be > carried as a VC in something like > draft-martini-l2circuit-encap-mpls-01. i'm not comfortable with the reasoning that a proposal is not right because the superintendents of the wg might interpret it the wrong way and come up with some funny ideas. i think it would be more customary for the wg to decide what it would like to do (within the context of its charter) while assuming that the wg superintendents are reasonable. it seems that the potential problem you mention is perhaps more a communication issue than a technical one. c u fsb _______________________________________________ pwot mailing list pwot@ietf.org http://www.ietf.org/mailman/listinfo/pwot
- [PWOT] mpls-in-ip tom worster
- Re: [PWOT] mpls-in-ip Dan Tappan
- Re: [PWOT] mpls-in-ip Kireeti Kompella
- Re: [PWOT] mpls-in-ip Alan Hannan
- RE: [PWOT] mpls-in-ip tom worster
- Re: [PWOT] mpls-in-ip Alan Hannan
- RE: [PWOT] mpls-in-ip tom worster
- RE: [PWOT] mpls-in-ip tom k. johnson
- Re: [PWOT] mpls-in-ip Eric Rosen
- RE: [PWOT] mpls-in-ip Sasha Vainshtein
- RE: [PWOT] mpls-in-ip tom worster
- RE: [PWOT] mpls-in-ip tom worster