[PWOT] mpls-in-ip

"tom worster" <tom@ennovatenetworks.com> Tue, 27 February 2001 16:46 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 LAA16880 for <pwot-archive@odin.ietf.org>; Tue, 27 Feb 2001 11:46:16 -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 LAA26873; Tue, 27 Feb 2001 11:37:26 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA26841 for <pwot@ns.ietf.org>; Tue, 27 Feb 2001 11:37:24 -0500 (EST)
Received: from ennovatenetworks.com ([63.102.148.71]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA16315 for <pwot@ietf.org>; Tue, 27 Feb 2001 11:37:22 -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 LAA08426; Tue, 27 Feb 2001 11:37:23 -0500 (EST) (envelope-from tom@ennovatenetworks.com)
From: tom worster <tom@ennovatenetworks.com>
To: "PWOT Email List (E-mail)" <pwot@ietf.org>, "CEOT Email List (E-mail)" <ceot@laurelnetworks.com>
Date: Tue, 27 Feb 2001 11:37:33 -0500
Message-ID: <00ba01c0a0db$95e74ea0$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
Content-Transfer-Encoding: 7bit
Subject: [PWOT] mpls-in-ip
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

i'd like to ask the to-be-working group three questions 
relating to this draft (it should show in the repository
soon, a url is given below):

1) is an mpls lsp an example of a "pseudo-wire?"

2) can ip be regarded as "transport?"

3) should mpls-in-ip be a standards track work item for
pwot?

in which the terms pseudo-wire and transport express the 
scope of the wg.

my opinions are.

1) yes. if an atm connection, frame relay connection, 
ds1 or oc3 are considered pseudo-wires then i think
an mpls lsp can reasonably be considered a pseudo-wire.

2) yes. the usage of "transport" in the pwot group seems 
to be more general than other uses. if mpls (which is a
sub-ip protocol) is a transport protocol along side tcp,
udp, rtp (which are all super-ip), etc., then i don't
see why ip can't also be regarded as providing transport.

3) if i'm right on the above two points then i think
pwot would the right place to write a standard 
encapsulation of mpls in ip, should the ietf want such 
as standard.


http://thefsb.org/draft-worster-mpls-in-ip-03.txt

c u
fsb

_______________________________________________
pwot mailing list
pwot@ietf.org
http://www.ietf.org/mailman/listinfo/pwot