Re: [PWOT] mpls-in-ip

Dan Tappan <tappan@cisco.com> Tue, 27 February 2001 17:10 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 MAA18406 for <pwot-archive@odin.ietf.org>; Tue, 27 Feb 2001 12:10:22 -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 MAA27538; Tue, 27 Feb 2001 12:01:50 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA27504 for <pwot@ns.ietf.org>; Tue, 27 Feb 2001 12:01:48 -0500 (EST)
Received: from pilgrim.cisco.com (pilgrim.cisco.com [171.69.204.12]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA17902 for <pwot@ietf.org>; Tue, 27 Feb 2001 12:01:45 -0500 (EST)
Received: from tappan-w2k.cisco.com (tappan-frame1.cisco.com [10.83.99.42]) by pilgrim.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id MAA08457; Tue, 27 Feb 2001 12:00:43 -0500 (EST)
Message-Id: <4.3.2.7.2.20010227115409.03bde708@pilgrim.cisco.com>
X-Sender: tappan@pilgrim.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 27 Feb 2001 12:00:11 -0500
To: tom worster <tom@ennovatenetworks.com>
From: Dan Tappan <tappan@cisco.com>
Subject: Re: [PWOT] mpls-in-ip
Cc: "PWOT Email List (E-mail)" <pwot@ietf.org>, "CEOT Email List (E-mail)" <ceot@laurelnetworks.com>
In-Reply-To: <00ba01c0a0db$95e74ea0$7203010a@ennovatenetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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

>
>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.

Well, my first reaction was that it's a stretch.

On the other hand I'd agree that defining a standard for MPLSinIP and/or 
documenting MPLSinGRE is a "good thing". And if there isn't another working 
group where it fits, Tom's reasoning below isn't totally outrageous.

Certainly this group seems to be intended to cover both
- tunneling X in MPLS
and
- tunneling X in IP
so
- Tunneling X in MPLS in IP
might be a natural leap.

At 11:37 AM 2/27/2001 -0500, tom worster wrote:
>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


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