Re: [PWOT] mpls-in-ip

Alan Hannan <alan@routingloop.com> Tue, 27 February 2001 19:37 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 OAA25739 for <pwot-archive@odin.ietf.org>; Tue, 27 Feb 2001 14:37:05 -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 OAA00829; Tue, 27 Feb 2001 14:32:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA00789 for <pwot@ns.ietf.org>; Tue, 27 Feb 2001 14:32:11 -0500 (EST)
Received: from ulysses.routingloop.com (root@c1297948-a.snvl1.sfba.home.com [65.3.196.186]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA25493 for <pwot@ietf.org>; Tue, 27 Feb 2001 14:32:06 -0500 (EST)
Received: (from alan@localhost) by ulysses.routingloop.com (8.10.0/8.10.0) id f1RJVvd01227; Tue, 27 Feb 2001 11:31:57 -0800 (PST)
Date: Tue, 27 Feb 2001 11:31:57 -0800
From: Alan Hannan <alan@routingloop.com>
To: tom worster <tom@ennovatenetworks.com>
Cc: "PWOT Email List (E-mail)" <pwot@ietf.org>, "CEOT Email List (E-mail)" <ceot@laurelnetworks.com>
Subject: Re: [PWOT] mpls-in-ip
Message-ID: <20010227113157.I575@routingloop.com>
References: <00ba01c0a0db$95e74ea0$7203010a@ennovatenetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Mailer: Mutt 1.0.1i
In-Reply-To: <00ba01c0a0db$95e74ea0$7203010a@ennovatenetworks.com>; from tom@ennovatenetworks.com on Tue, Feb 27, 2001 at 11:37:33AM -0500
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

> 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?"

  yes

> 2) can ip be regarded as "transport?"

  yes

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

  sure

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

  general agreement from this vector.

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