RE: [PWOT] mpls-in-ip
"tom worster" <tom@ennovatenetworks.com> Wed, 28 February 2001 16:45 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 LAA12533 for <pwot-archive@odin.ietf.org>; Wed, 28 Feb 2001 11:45:07 -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 LAA25487; Wed, 28 Feb 2001 11:40:33 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA25451 for <pwot@ns.ietf.org>; Wed, 28 Feb 2001 11:40:31 -0500 (EST)
Received: from ennovatenetworks.com ([63.102.148.71]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA12255 for <pwot@ietf.org>; Wed, 28 Feb 2001 11:40:31 -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 LAA23364; Wed, 28 Feb 2001 11:40:27 -0500 (EST) (envelope-from tom@ennovatenetworks.com)
From: tom worster <tom@ennovatenetworks.com>
To: 'Sasha Vainshtein' <Sasha@AXERRA.com>, "'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:40:36 -0500
Message-ID: <007301c0a1a5$2da3a8f0$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: <AF5018AC03D1D411ABB70002A5091326039C43@TLV1>
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: Sasha Vainshtein [mailto:Sasha@AXERRA.com] > > I have doubts regarding your presumtions: > 1) An MPLS LSP may be multipoint-to-point as > opposed to all the > rest of of the pseudo-wire examples in your message in mpls-in-ip no label switching occurs between encapsulator and decapsulator. so i don't see that p2mp and mp2p lsr requirements affect the encapsulation. > 2) IP per se is can be hardly considered as > transport since it > does not allow for demuxing between an > indefinitely large number of logical > application instances > within the downstream host. BTW, this is why - IMHO > - in order to > treat MPLS as transport you usually require a stack of two > labels while ATM > provides transport capabilities inherently by using VPI/VCI if such multiplexing is, in the opinion of the wg, a necessary characteristic of "transport" then i would argue that mpls-in-ip is a good example of signalled multi-protocol transport tunnels for ip core networks. 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