From l2vpn-bounces@ietf.org Sun Nov 04 21:49:44 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ios1y-0003BV-M9; Sun, 04 Nov 2007 21:49:38 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ios1x-0003A5-6I for l2vpn@ietf.org; Sun, 04 Nov 2007 21:49:37 -0500 Received: from dog.tcb.net ([64.78.150.133]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Ios1w-0000Jo-Au for l2vpn@ietf.org; Sun, 04 Nov 2007 21:49:37 -0500 Received: by dog.tcb.net (Postfix, from userid 0) id EC1F62680A5; Sun, 4 Nov 2007 19:49:19 -0700 (MST) Received: from pmac.castlepoint.net (71-215-94-199.hlrn.qwest.net [71.215.94.199]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; Sun, 04 Nov 2007 19:49:19 -0700 (MST) (envelope-from shane@castlepoint.net) X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=71.215.94.199; client-port=4477; syn-fingerprint=65535:55:1:64:M1460,N,W3,N,N,T,S MacOS 10.4.8; data-bytes=0 Message-Id: From: Shane Amante To: "Shah, Himanshu" In-Reply-To: <3C13767EA2F93441AFB13A630204F1B29FBA21@mamxm02.ciena.com> Content-Type: multipart/mixed; boundary=Apple-Mail-20--972104717 Mime-Version: 1.0 (Apple Message framework v912) Date: Sun, 4 Nov 2007 19:49:03 -0700 References: <3C13767EA2F93441AFB13A630204F1B29FBA21@mamxm02.ciena.com> X-Mailer: Apple Mail (2.912) X-Spam-Score: 0.0 (/) X-Scan-Signature: e367d58950869b6582535ddf5a673488 Cc: l2vpn@ietf.org Subject: Re: IETF 70: Call for slots for Vancouver X-BeenThere: l2vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: l2vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: l2vpn-bounces@ietf.org --Apple-Mail-20--972104717 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Himanshu, The primary goal is to update the existing milestones -- complete ones that are behind us and assign new dates to those that remain incomplete, (e.g.: MIB's, OAM). Second, since we've already taken on multicast, we should add that, with appropriate deliverables, to the charter, as well. Given that we have a fair bit of uncompleted work from the original charter, (MIB's, OAM), plus "new" work (multicast) on our plate, I don't think we're in a good position to ask the IESG to consider taking on more new work, until we finish what we've got, (particularly around the OAM & MIB's). 'New' work items that may fall into this category are: - Optimizations to improve 'scalability'[1] of VPLS, e.g.: 802.1ah or similar 'MPLS-only' methods - Inter-domain VPLS -- I'm not sure if there is interest here, but it has been brought up in the past So, I see two choices for the path forward: 1) Finish up what we've got (MIB's, OAM + multicast) and shutdown. 2) First and foremost, finish up what we've got (MIB's, OAM + multicast). Then, work on addt'l work items defined above in the 'new' work items category, (plus perhaps items that I haven't listed that others may bring forward). Finally, evaluate shutting down. Thoughts? -shane [1] Relative to this point, we seem to have briefly delved into this area without asking the question of what problem(s) do we *really* need to solve? For example: optimizing MAC flushing, reducing the size of MAC tables, other? We collectively need to agree what, if any, problems we need to solve before we take on any formal work in this area. See attached for the new, proposed charter and milestones. If you have opinions on the deliverables, dates or text, please speak up. --Apple-Mail-20--972104717 Content-Disposition: attachment; filename=l2vpn-milestones.txt Content-Type: text/plain; x-unix-mode=0644; name="l2vpn-milestones.txt" Content-Transfer-Encoding: quoted-printable The L2VPN working group is responsible for defining and specifying a = limited =0D number of solutions for supporting provider-provisioned Layer-2 Virtual =0D= Private Networks (L2VPNs). Layer-2 VPN's comprise the following:=0D =0D 1. Virtual Private LAN Service (VPLS) -- Layer-2 service that emulates = LAN's=0D across an IP and an MPLS-enabled IP network, allowing standard = Ethernet=0D devices communicate with each other as if they were connected to a = common=0D LAN segment.=0D =0D 2. Virtual Private Wire Service (VPWS) -- Layer-2 service that provides=0D= Layer-2 point-to-point connectivity, (e.g. Frame Relay DLCI, ATM = VPI/VCI,=0D point-to-point Ethernet), across an IP and an MPLS-enabled IP = network.=0D =0D 3. IP-only VPNs -- A Layer-2 service over an IP and MPLS-enabled = network,=0D allowing standard IP devices to communicate with each other as if = they were=0D connected to a common LAN or with some mesh of point-to-point = circuits,=0D (not necessarily fully meshed). The WG will address two cases of = IP-only=0D VPN's: a) where the customer attachment circuits use the same Layer-2=0D= protocol at all attachment points in the same L2VPN; and, b) where = the=0D customer attachment circuits use different Layer-2 protocols on the=0D= attachment points in the same L2VPN. Note, the latter is a = restricted=0D form of inter-working that is limited to providing the facilities=0D necessary to carry IP over the L2VPN; general Layer-2 inter-working = is=0D not in scope.=0D =0D As a general rule, the L2VPN WG will not create new protocols, but will=0D= provide functional requirements for extensions of existing protocols = that will=0D be discussed in the protocol-specific WGs. As a specific example, this = WG=0D will not define new encapsulation mechanism, but will use those defined = in the=0D PWE3 WG. Finally, the WG will review proposed protocol extensions for = L2VPNs=0D before they are recommended to appropriate protocol-specific WGs.=0D =0D The L2VPN WG scope includes the following:=0D =0D 1. Discovery of PE's participating in a Layer-2 VPN and the associated=0D= topology required for connectivity of the L2VPN service.=0D =0D 2. Signaling of L2VPN related information for the purpose of setup and=0D= maintenance of L2VPN circuits. As much as possible, PWE3 signaling=0D= procedures should be used.=0D =0D 3. MIB's for Layer-2 VPN solutions.=0D =0D 4. L2VPN-specific OAM extensions -- extensions to existing OAM solutions=0D= for VPLS, VPWS, and IP-only L2VPNs. As much as possible, PWE3 OAM=0D signaling procedures should be used.=0D =0D The L2VPN WG currently works on the following tasks:=0D =0D - Define MIB's appropriate for each type of Layer-2 VPN.=0D =0D - Specification of Operations Administration and Management (OAM) = mechanisms=0D for VPLS, VPWS and IP-only VPN's.=0D =0D - Specification of procedures to permit optimization of L2VPN multicast = data=0D traffic within a IP or MPLS Backbone network.=0D =0D The WG will address Intra-AS scenarios only at this point, (other = scenarios=0D will be considered for inclusion in the updated charter when the current = one=0D is completed.)=0D =0D Where necessary, the WG will coordinate its activities with IEEE 802.1.=0D= =0D Goals and Milestones:=0D =0D Done Submit L2 requirements to IESG for publication as Informational = RFC=0D Done Identify VPLS and VPWS solutions for the WG=0D Done Submit L2 framework to IESG for publication as Informational RFC=0D= Done Submit VPLS solution documents to IESG=0D Done Submit VPWS solution documents to IESG=0D Done Submit an I-D on OAM requirements for VPLS=0D Done Submit an I-D on OAM requirements for VPWS=0D Done Submit an I-D describing MIB for VPLS=0D Done Submit an I-D describing MIB for VPWS=0D =0D Dec 2007 Submit IP-only L2VPN solution documents to IESG=0D Mar 2008 Submit MIB for VPLS to IESG=0D Mar 2008 Submit MIB for VPWS to IESG=0D Mar 2008 Submit MIB for IP-only L2VPN to IESG=0D =0D Aug 2008 Submit OAM solution for VPWS to IESG=0D Aug 2008 Submit OAM solution for VPLS to IESG=0D Aug 2008 Submit OAM solution for IP-only L2VPN to IESG=0D =0D Nov 2008 Submit Multicast Optimization Solutions for VPLS to IESG=0D Nov 2008 Submit Multicast Optimization Solutions for VPWS to IESG=0D Nov 2008 Submit Multicast Optimization Solutions for IP-only L2VPN to = IESG= --Apple-Mail-20--972104717 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit On Oct 30, 2007, at 6:28 AM, Shah, Himanshu wrote: > Hi Shane, > > what is on the deck for charter update? > > /himanshu > >> -----Original Message----- >> From: Shane Amante [mailto:shane@castlepoint.net] >> Sent: Monday, October 29, 2007 11:19 PM >> To: l2vpn@ietf.org >> Subject: IETF 70: Call for slots for Vancouver >> >> >> Hi, >> >> We have been tentatively granted a 1 hour meeting slot on: >> TUESDAY, December 4, 2007 >> 1740-1840 Afternoon Session III >> Salon 3 INT l2vpn Layer 2 Virtual Private >> Networks WG >> >> One thing we are going to cover is a charter update. If there are >> other items you wish to discuss, please mail Vach or I. >> >> Thanks! >> >> -shane >> --Apple-Mail-20--972104717-- From l2vpn-bounces@ietf.org Sat Nov 17 23:51:09 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Itc7A-0004RR-SZ; Sat, 17 Nov 2007 23:50:36 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Itc76-0004L1-RE; Sat, 17 Nov 2007 23:50:33 -0500 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Itc76-0003Tp-Dz; Sat, 17 Nov 2007 23:50:32 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 4399D2AC7F; Sun, 18 Nov 2007 04:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1Itc6c-0008NC-1E; Sat, 17 Nov 2007 23:50:02 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Sat, 17 Nov 2007 23:50:02 -0500 X-Spam-Score: 0.0 (/) X-Scan-Signature: 73734d43604d52d23b3eba644a169745 Cc: l2vpn@ietf.org Subject: I-D Action:draft-ietf-l2vpn-vpls-mcast-03.txt X-BeenThere: l2vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: l2vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: l2vpn-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Layer 2 Virtual Private Networks Working Group of the IETF. Title : Multicast in VPLS Author(s) : R. Aggarwal, et al. Filename : draft-ietf-l2vpn-vpls-mcast-03.txt Pages : 41 Date : 2007-11-17 This document describes a solution for overcoming a subset of the limitations of existing VPLS multicast solutions. It describes procedures for VPLS multicast that utilize multicast trees in the sevice provider (SP) network. One such multicast tree can be shared between multiple VPLS instances. Procedures by which a single multicast tree in the backbone can be used to carry traffic belonging only to a specified set of one or more IP multicast streams from one or more VPLSs are also described. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-vpls-mcast-03.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-l2vpn-vpls-mcast-03.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-l2vpn-vpls-mcast-03.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-11-17234945.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-l2vpn-vpls-mcast-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-l2vpn-vpls-mcast-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-11-17234945.I-D\@ietf.org> --OtherAccess-- --NextPart-- From l2vpn-bounces@ietf.org Tue Nov 20 11:42:21 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuWAn-0002XG-Kd; Tue, 20 Nov 2007 11:42:05 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuWAm-0002VV-9y for l2vpn@ietf.org; Tue, 20 Nov 2007 11:42:04 -0500 Received: from mail3.extremenetworks.com ([207.179.9.4]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IuWAl-0008VQ-Th for l2vpn@ietf.org; Tue, 20 Nov 2007 11:42:04 -0500 Received: by mail3.extremenetworks.com with Internet Mail Service (5.5.2655.55) id ; Tue, 20 Nov 2007 08:31:31 -0800 Message-ID: <3DC3910A44FBD94B8513C8E2A3F220E10269900A@sc-msexch-16.extremenetworks.com> From: Olen Stokes To: "'l2vpn@ietf.org'" Date: Tue, 20 Nov 2007 08:41:58 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2655.55) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Score: 0.0 (/) X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002 Subject: Notification for draft-stokes-l2vpn-cfm-vccv-oam-00.txt X-BeenThere: l2vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: l2vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: l2vpn-bounces@ietf.org The subject draft is available from the on-line Internet-Drafts directories. It has been submitted to the Layer 2 Virtual Private Networks Working Group. Title : OAM for L2 VPN Networks Using CFM and VCCV Author(s): O. Stokes, S. Amamte, P. Dutta, Y. Serbest Filename : draft-stokes-l2vpn-cfm-vccv-oam-00.txt Pages : 26 Date : 2007-11-05 Abstract The IEEE has defined P802.1ag Connectivity Fault Management (CFM) for managing bridged LAN networks. The IETF has defined L2 Virtual Private Networks (VPNs) that provide an emulated LAN service for such bridged networks. These L2 VPNs are created using a collection of one or more point-to-point pseudo wires (PWs). The IETF has also defined Virtual Circuit Connectivity Verification (VCCV) for managing these PWs. This memo discusses the ability of a combination of CFM and VCCV to meet the OAM requirements of a L2 VPN. The draft describes possible deployment scenarios for CFM and VCCV in a L2 VPN environment. It also discusses areas of concern where additional functionality may be of benefit to network operators. The difficulties in addressing the OAM aspects of the VPLS Forwarders described in RFC 4664 are specifically discussed. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-stokes-l2vpn-cfm-vccv-oam-00.txt Comments and discussions are requested on the mailing list. A presentation is planned at the Vancouver IETF if there is sufficient interest. Cheers, Olen From l2vpn-bounces@ietf.org Tue Nov 20 12:47:28 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuXBn-0007n0-9o; Tue, 20 Nov 2007 12:47:11 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuXBl-0007mv-Ea for l2vpn@ietf.org; Tue, 20 Nov 2007 12:47:09 -0500 Received: from ihemail4.lucent.com ([135.245.0.39]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IuXBh-0001Xy-Nn for l2vpn@ietf.org; Tue, 20 Nov 2007 12:47:09 -0500 Received: from ilexp02.ndc.lucent.com (h135-3-39-2.lucent.com [135.3.39.2]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id lAKHjsYe010670 for ; Tue, 20 Nov 2007 11:46:57 -0600 (CST) Received: from inexp02.in.lucent.com ([135.254.223.66]) by ilexp02.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 20 Nov 2007 11:46:52 -0600 Received: from INEXC1U01.in.lucent.com ([135.254.223.26]) by inexp02.in.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 20 Nov 2007 23:16:47 +0530 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C82B9D.520B65F6" Date: Tue, 20 Nov 2007 23:16:39 +0530 Message-ID: <6D26D1FE43A66F439F8109CDD4241965F74D83@INEXC1U01.in.lucent.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Notification for draft-stokes-vkompella-l2vpn-vpls-oam-01.txt Thread-Index: AcgrnU4N4+TL7Hy1RcmuhXWYxJBBBA== From: "Dutta, Pranjal \(Pranjal\)" To: X-OriginalArrivalTime: 20 Nov 2007 17:46:47.0010 (UTC) FILETIME=[5243E420:01C82B9D] X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39 X-Spam-Score: 0.1 (/) X-Scan-Signature: 681e62a2ce9b0804b459fe780d892beb Subject: Notification for draft-stokes-vkompella-l2vpn-vpls-oam-01.txt X-BeenThere: l2vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: l2vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: l2vpn-bounces@ietf.org This is a multi-part message in MIME format. ------_=_NextPart_001_01C82B9D.520B65F6 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable The subject draft is available from the on-line Internet-Drafts=20 directories. It has been submitted to the Layer 2 Virtual Private Networks Working Group. =20 =20 Title : OAM for Virtual Private LAN Service (VPLS) Author(s) : O. Stokes, et al. Filename : draft-stokes-vkompella-l2vpn-vpls-oam-01.txt Pages : 46 Date : 2007-11-19 =20 Abstract =20 This document describes a methodology and a set of mechanisms for=20 Operation, Administration and Maintenance (OAM) of a general VPN=20 (Virtual Private Network) service that is applied to a Virtual=20 Private LAN Service [RFC4761][RFC4762].=20 draft-stokes-l2vpn-cfm-vccv-oam-00.txt describes the capabilities of CFM=20 802.1ag and VCCV for OAM operations among the bridge module=20 components in the VPLS. The OAM functions described in this document=20 builds the additional capabilities into 802.1ag + VCCV to detect, verify=20 and isolate connectivity faults among the VPLS forwarder components. The=20 methodology adopted extends LSP Ping concepts described in RFC4379 and=20 VCCV capabilities. =20 A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-stokes-vkompella-l2vpn-vpls-oa m-01.txt =20 Comments and discussions are requested on the mailing list. A presentation is planned at the Vancouver IETF if there is sufficient interest. =20 =20 Cheers, Pranjal =20 ------_=_NextPart_001_01C82B9D.520B65F6 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

The subject draft is available from the on-line Internet-Drafts =

directories. It has been submitted to the Layer 2 Virtual = Private Networks Working Group.

 

 

      = Title       : OAM for Virtual Private LAN = Service (VPLS)

      Author(s)   : O. = Stokes, et al.

      Filename    : = draft-stokes-vkompella-l2vpn-vpls-oam-01.txt

      = Pages       : 46

      = Date        : = 2007-11-19

 

Abstract

     
   This document describes a methodology and a set of = mechanisms for

   Operation, Administration and Maintenance (OAM) of = a general VPN

   (Virtual Private Network) service that is applied = to a Virtual

   Private LAN Service [RFC4761][RFC4762]. =

   draft-stokes-l2vpn-cfm-vccv-oam-00.txt describes = the capabilities of CFM
   802.1ag and VCCV for OAM operations among the bridge module =
   components in the VPLS. The OAM functions described in this = document
   builds the additional capabilities into 802.1ag + VCCV to = detect, verify
   and isolate connectivity faults among the VPLS forwarder = components. The
   methodology adopted extends LSP Ping concepts described in = RFC4379 and
   VCCV capabilities.

 

A URL for this Internet-Draft is:

http://www.ietf.org/internet-drafts/draft-stokes-vkompella-l2vpn-= vpls-oam-01.txt

 

Comments and discussions are = requested on the mailing list.  A presentation is planned at the Vancouver IETF = if there is sufficient interest.

 

 

Cheers,

Pranjal

 

------_=_NextPart_001_01C82B9D.520B65F6-- From l2vpn-bounces@ietf.org Sun Nov 25 23:30:51 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IwVcJ-0000Gt-QF; Sun, 25 Nov 2007 23:30:43 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IwVcJ-0000Gn-3V for l2vpn@ietf.org; Sun, 25 Nov 2007 23:30:43 -0500 Received: from dog.tcb.net ([64.78.150.133]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IwVcI-0004Tj-MP for l2vpn@ietf.org; Sun, 25 Nov 2007 23:30:42 -0500 Received: by dog.tcb.net (Postfix, from userid 0) id 1E5022680F1; Sun, 25 Nov 2007 21:30:42 -0700 (MST) Received: from pmac.castlepoint.net (71-215-85-82.hlrn.qwest.net [71.215.85.82]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; for l2vpn@ietf.org; Sun, 25 Nov 2007 21:30:42 -0700 (MST) (envelope-from shane@castlepoint.net) X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=71.215.85.82; client-port=4496; syn-fingerprint=65535:55:1:64:M1460,N,W3,N,N,T,S MacOS 10.4.8; data-bytes=0 Message-Id: <069444F7-0715-4C84-B371-927393A72F3C@castlepoint.net> From: Shane Amante To: l2vpn@ietf.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v915) Date: Sun, 25 Nov 2007 21:30:41 -0700 X-Mailer: Apple Mail (2.915) X-Spam-Score: 0.0 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Subject: IETF 70: Draft Agenda for Vancouver X-BeenThere: l2vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: l2vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: l2vpn-bounces@ietf.org Hi All, Here is the draft agenda for the L2VPN meeting in Vancouver: http://www3.ietf.org/proceedings/07dec/agenda/l2vpn.txt We had a lot of requests for time slots at the Vancouver meeting and unfortunately were unable to accommodate everyone. We tried to request an additional (or larger) timeslot, but were unsuccessful with that request. Please let Vach or I know if there are comments or corrections related to this agenda. -shane From l2vpn-bounces@ietf.org Mon Nov 26 10:14:29 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IwffG-0001DQ-Vb; Mon, 26 Nov 2007 10:14:26 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IwffG-0001DG-8D for l2vpn@ietf.org; Mon, 26 Nov 2007 10:14:26 -0500 Received: from dog.tcb.net ([64.78.150.133]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IwffF-0002mi-Qr for l2vpn@ietf.org; Mon, 26 Nov 2007 10:14:26 -0500 Received: by dog.tcb.net (Postfix, from userid 0) id 59C372680AA; Mon, 26 Nov 2007 08:14:25 -0700 (MST) Received: from [127.0.0.1] (dog.tcb.net [64.78.150.133]) (authenticated-user smtp) (TLSv1/SSLv3 DHE-RSA-AES256-SHA 256/256) by dog.tcb.net with SMTP; for l2vpn@ietf.org; Mon, 26 Nov 2007 08:14:25 -0700 (MST) (envelope-from shane@castlepoint.net) X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=64.78.150.133; client-port=51264; data-bytes=0 Message-ID: <474AE2D0.4020101@castlepoint.net> Date: Mon, 26 Nov 2007 08:14:24 -0700 From: Shane Amante User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: l2vpn@ietf.org References: <069444F7-0715-4C84-B371-927393A72F3C@castlepoint.net> In-Reply-To: <069444F7-0715-4C84-B371-927393A72F3C@castlepoint.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Subject: Re: IETF 70: Draft Agenda for Vancouver X-BeenThere: l2vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: l2vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: l2vpn-bounces@ietf.org One minor correction to Item #5. The link the the correct (-01) draft is as follows: http://tools.ietf.org/html/draft-stokes-vkompella-l2vpn-vpls-oam-01 -shane Shane Amante wrote: > Hi All, > > Here is the draft agenda for the L2VPN meeting in Vancouver: > http://www3.ietf.org/proceedings/07dec/agenda/l2vpn.txt > > We had a lot of requests for time slots at the Vancouver meeting and > unfortunately were unable to accommodate everyone. We tried to request > an additional (or larger) timeslot, but were unsuccessful with that > request. > > Please let Vach or I know if there are comments or corrections related > to this agenda. > > -shane >