[PWOT] RE: l2vpn work split

"tom worster" <tom@ennovatenetworks.com> Wed, 28 March 2001 16:18 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 LAA03672 for <pwot-archive@odin.ietf.org>; Wed, 28 Mar 2001 11:18:57 -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 LAA21260; Wed, 28 Mar 2001 11:12:45 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA21229 for <pwot@ns.ietf.org>; Wed, 28 Mar 2001 11:12:43 -0500 (EST)
Received: from ennovatenetworks.com ([63.102.148.71]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA03264 for <pwot@ietf.org>; Wed, 28 Mar 2001 11:12:44 -0500 (EST)
Received: from tworster (vpn3.tst.ennovatenetworks.com [10.1.2.3]) by ennovatenetworks.com (8.8.7/8.8.7) with SMTP id LAA17039; Wed, 28 Mar 2001 11:11:14 -0500 (EST) (envelope-from tom@ennovatenetworks.com)
From: tom worster <tom@ennovatenetworks.com>
To: danny@ambernetworks.com
Cc: "'PWOT Email List (E-mail)'" <pwot@ietf.org>, "ppvpn list (E-mail)" <ppvpn@zephion.net>
Date: Wed, 28 Mar 2001 11:11:08 -0500
Message-ID: <000601c0b7a1$b4eb48b0$6741a8c0@thefsb.org>
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)
In-reply-to: <200103272348.QAA14798@tcb.net>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit

From: danny@sofos.tcb.net Danny McPherson
> 
> 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.  

ok. i think i can imagine that. so...

does this imply that pwe3 will defer to those 
requirements from ppvpn that apply to work 
happening in pwe3?

does it also mean that the technology aspects 
proposed by kireeti, juha and himanshu, among 
others, in ppvpn should be worked on in pwe3?

c u
fsb

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