[PWOT] Re: l2vpn work split

Danny McPherson <danny@ambernetworks.com> Wed, 28 March 2001 00:02 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 TAA03939 for <pwot-archive@odin.ietf.org>; Tue, 27 Mar 2001 19:02:08 -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 SAA01130; Tue, 27 Mar 2001 18:50: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 SAA01097 for <pwot@ns.ietf.org>; Tue, 27 Mar 2001 18:50:31 -0500 (EST)
Received: from tcb.net (tcb.net [205.168.100.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA03598 for <pwot@ietf.org>; Tue, 27 Mar 2001 18:49:43 -0500 (EST)
Received: from sofos.tcb.net (sofos.tcb.net [127.0.0.1]) by tcb.net (8.9.3/8.9.3) with ESMTP id QAA14798; Tue, 27 Mar 2001 16:48:52 -0700
Message-Id: <200103272348.QAA14798@tcb.net>
X-Mailer: exmh version 2.0.3
To: tom worster <tom@ennovatenetworks.com>
cc: sob@harvard.edu, "ppvpn list (E-mail)" <ppvpn@zephion.net>, "PWOT Email List (E-mail)" <pwot@ietf.org>
From: Danny McPherson <danny@ambernetworks.com>
Reply-To: danny@ambernetworks.com
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Tue, 27 Mar 2001 16:48:52 -0700
Subject: [PWOT] Re: l2vpn work split
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

Tom,
I'd like to take a stab at this, I'm certain Scott 
will correct me if I'm of base.

> in the pwot bof i asked about the work split
> between ppvpn and pwot on the l2vpn question.
> i didn't really understand your answer so i
> thought i'd ask for it again here, where we 
> have more time for discussion.
> 
> in particular, i'm interested to learn why it
> is considered advantageous to try to split the
> work across two groups.

PWE3 will deal with standardization of pseduo wire (e.g., FR, 
ATM) functionality over IP|L2TP|MPLS.  PPVPNs, intuitively, 
deals with grouping of "technology sets" to document specific 
"VPN services offerings".  

Though there's certainly less obvious overlap, the basic idea
is that some of these "technology subsets" of the PPVPN work 
will be specified in PWE3.  

Likewise, simply because someone is employing a pseudo wire 
technology, this doesn't necessarily imply that the VPN 
acronym need be present.  That is, FR or ATM transport (i.e., 
the carriage bits, not "Layer 4") itself doesn't necessarily 
imply VPN.

A charter should be posted no later than Friday, hopefully,
it will help to clarify things. 

-danny


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