From l3vpn-bounces@ietf.org Tue Jan 02 17:19:12 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H1ry1-0001xX-CS; Tue, 02 Jan 2007 17:18:45 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H1rxy-0001vL-7L; Tue, 02 Jan 2007 17:18:42 -0500 Received: from out001.atlarge.net ([129.41.63.69]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H1rxt-0004oX-W9; Tue, 02 Jan 2007 17:18:42 -0500 Received: from nemertes-01-ex.atlarge.net ([10.100.50.167]) by out001.atlarge.net with Microsoft SMTPSVC(6.0.3790.1830); Tue, 2 Jan 2007 16:16:51 -0600 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Tue, 2 Jan 2007 16:18:53 -0600 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: FutureNet 2007 Call For Presentations Thread-Index: AccukSytZr2ld2u9RvuHPF7uXbxFTwAA4FRQAAkWooAAAF48cA== From: "Irwin Lazar" To: , , , , X-OriginalArrivalTime: 02 Jan 2007 22:16:51.0794 (UTC) FILETIME=[B40E3320:01C72EBB] X-Spam-Score: 0.0 (/) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 Cc: mpls-ops@mplsrc.com Subject: FutureNet 2007 Call For Presentations X-BeenThere: l3vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: l3vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: l3vpn-bounces@ietf.org Greetings, The "Call for Presentations" for "FutureNet 2007: MPLS, VPLS and Beyond" is now available at http://www.futurenetexpo.com/speaker/submit_pres.html FutureNet will be held at the Grand Hyatt Hotel on April 30 - May 3, 2007 in New York City. FutureNet represents the evolution of MPLScon, which for the last six years has been the premier industry conference focusing on MPLS, VPN and WAN technologies from both enterprise and service provider perspectives. =20 With this year's event we'll expand our focus to cover next generation network technologies including emerging Ethernet services, fixed/mobile convergence, rich-media service delivery, optical networking and more. As has been the tradition from past events, FutureNet will focus on end-user case studies from both enterprises and service providers providing real-world insight into challenges and lessons learned. =20 We invite you to review the Call For Presentations and submit an abstract. Please note that abstracts are due by February 2nd, 2007. Please feel free to contact me with any questions. My contact information is below. =20 Sincerely, Irwin Lazar Conference Director, FutureNet: MPLS, VPLS, and Beyond (Formerly MPLScon) http://www.futurenetexpo.com/ irwin.lazar@nemertes.com 703-468-4361 AIM/Google/Yahoo/Skype: imlazar =20 From l3vpn-bounces@ietf.org Mon Jan 15 12:52:46 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6Vzw-0005AM-0F; Mon, 15 Jan 2007 12:51:56 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6Vzr-00058t-Bu for l3vpn@ietf.org; Mon, 15 Jan 2007 12:51:51 -0500 Received: from kremlin.juniper.net ([207.17.137.120]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H6Vxv-0001SC-La for l3vpn@ietf.org; Mon, 15 Jan 2007 12:49:52 -0500 Received: from unknown (HELO proton.jnpr.net) ([10.10.2.37]) by kremlin.juniper.net with ESMTP; 15 Jan 2007 09:46:01 -0800 X-IronPort-AV: i="4.13,191,1167638400"; d="scan'208"; a="640383921:sNHT31502588" Received: from [172.25.51.57] ([172.25.51.57] RDNS failed) by proton.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Mon, 15 Jan 2007 12:49:50 -0500 Message-ID: <45ABBEBB.1070702@juniper.net> Date: Mon, 15 Jan 2007 12:49:47 -0500 From: Ron Bonica User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: l3vpn@ietf.org X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 15 Jan 2007 17:49:50.0439 (UTC) FILETIME=[8DF42F70:01C738CD] X-Spam-Score: 0.0 (/) X-Scan-Signature: 08e48e05374109708c00c6208b534009 Subject: IETF 68 X-BeenThere: l3vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: l3vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: l3vpn-bounces@ietf.org Folks, Does anyone have anything that they want to present at IETF 68? If I don't hear anything by Wednesday, I will request a short (1 hour) block in which we can meet. Ron From l3vpn-bounces@ietf.org Tue Jan 16 10:31:16 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6qGd-0006Ol-80; Tue, 16 Jan 2007 10:30:31 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6qGY-0006Bg-Et; Tue, 16 Jan 2007 10:30:26 -0500 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1H6qGY-0003x1-5W; Tue, 16 Jan 2007 10:30:26 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id D741017665; Tue, 16 Jan 2007 15:29:55 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1H6qG3-0000ru-FG; Tue, 16 Jan 2007 10:29:55 -0500 X-test-idtracker: no From: The IESG To: IETF-Announce Message-Id: Date: Tue, 16 Jan 2007 10:29:55 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa Cc: l3vpn chair , Internet Architecture Board , l3vpn mailing list , RFC Editor Subject: Document Action: 'Requirements for Multicast in L3 Provider-Provisioned VPNs' to Informational RFC X-BeenThere: l3vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: l3vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: l3vpn-bounces@ietf.org The IESG has approved the following document: - 'Requirements for Multicast in L3 Provider-Provisioned VPNs ' as an Informational RFC This document is the product of the Layer 3 Virtual Private Networks Working Group. The IESG contact persons are Mark Townsley and Jari Arkko. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-l3vpn-ppvpn-mcast-reqts-10.txt Technical Summary This document presents a set of functional requirements for network solutions that allow the deployment of IP multicast within L3 Provider Provisioned virtual private networks (PPVPNs). It specifies requirements both from the end user and service provider standpoints. It is intended that potential solutions specifying the support of IP multicast within such VPNs will use these requirements as guidelines. Working Group Summary There was strong consensus to publish. Protocol Quality This document was reviewed for the IESG by Mark Townsley. Note to RFC Editor OLD In Section 5.2.10 ' ... SNMP [RFC3411] MIBs (Management Information Bases) ...' New: '... SMIv2 [RFC2578] Management Information Base (MIB) modules to be used with SNMP [RFC3411] ... Please and add an Informational reference to [RFC2578] ftp://ftp.rfc-editor.org/in-notes/rfc2578.txt. From l3vpn-bounces@ietf.org Wed Jan 24 21:20:56 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H9uDL-0007b5-IQ; Wed, 24 Jan 2007 21:19:47 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H9uDH-0007ac-Uv; Wed, 24 Jan 2007 21:19:43 -0500 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H9uDG-0005rR-Ho; Wed, 24 Jan 2007 21:19:43 -0500 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id l0P2Jd5Q014438; Wed, 24 Jan 2007 18:19:39 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id l0P2JdS2014437; Wed, 24 Jan 2007 18:19:39 -0800 Date: Wed, 24 Jan 2007 18:19:39 -0800 Message-Id: <200701250219.l0P2JdS2014437@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.8 (--------------) X-Scan-Signature: 25620135586de10c627e3628c432b04a Cc: l3vpn@ietf.org, rfc-editor@rfc-editor.org Subject: RFC 4797 on Use of Provider Edge to Provider Edge (PE-PE) Generic Routing Encapsulation (GRE) or IP in BGP/MPLS IP Virtual Private Networks X-BeenThere: l3vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: l3vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: l3vpn-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4797 Title: Use of Provider Edge to Provider Edge (PE-PE) Generic Routing Encapsulation (GRE) or IP in BGP/MPLS IP Virtual Private Networks Author: Y. Rekhter, R. Bonica, E. Rosen Status: Informational Date: January 2007 Mailbox: yakov@juniper.net, rbonica@juniper.net, erosen@cisco.com Pages: 10 Characters: 18985 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-l3vpn-gre-ip-2547-05.txt URL: http://www.rfc-editor.org/rfc/rfc4797.txt This document describes an implementation strategy for BGP/MPLS IP Virtual Private Networks (VPNs) in which the outermost MPLS label (i.e., the tunnel label) is replaced with either an IP header or an IP header with Generic Routing Encapsulation (GRE). The implementation strategy described herein enables the deployment of BGP/MPLS IP VPN technology in networks whose edge devices are MPLS and VPN aware, but whose interior devices are not. This memo provides information for the Internet community. This document is a product of the Layer 3 Virtual Private Networks Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... From l3vpn-bounces@ietf.org Mon Jan 29 10:59:35 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBYts-0001th-Ge; Mon, 29 Jan 2007 10:58:32 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HBYtr-0001tb-Lg for l3vpn@ietf.org; Mon, 29 Jan 2007 10:58:31 -0500 Received: from borg.juniper.net ([207.17.137.119]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBYtq-0006Kh-DD for l3vpn@ietf.org; Mon, 29 Jan 2007 10:58:31 -0500 Received: from unknown (HELO proton.jnpr.net) ([10.10.2.37]) by borg.juniper.net with ESMTP; 29 Jan 2007 07:58:30 -0800 X-IronPort-AV: i="4.13,253,1167638400"; d="scan'208"; a="665395149:sNHT31368460" Received: from [172.25.51.58] ([172.25.51.58] RDNS failed) by proton.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Mon, 29 Jan 2007 10:58:29 -0500 Message-ID: <45BE19A2.1070903@juniper.net> Date: Mon, 29 Jan 2007 10:58:26 -0500 From: Ron Bonica User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: l3vpn@ietf.org X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 29 Jan 2007 15:58:29.0355 (UTC) FILETIME=[51802BB0:01C743BE] X-Spam-Score: 0.0 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Subject: Revised ID Needed X-BeenThere: l3vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: l3vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: l3vpn-bounces@ietf.org Folks, The following drafts have been submitted to the IESG and have been in the REVISED ID NEEDED state for several months: - draft-ietf-l3vpn-ce-based - draft-ietf-l3vpn-vpn-vr - draft-ietf-l3vpn-vr-mib - draft-declercq-l3vpn-ce-based-as - draft-ietf-l3vpn-as-vr - draft-ietf-l3vpn-bgpvpn-auto The WG chairs are requesting that these drafts be updated by IETF 68. Failure to update these drafts will result in their being dropped as WG items. Also, draft-ietf-l3vpn-ipsec-2547 was placed in the REVISED ID NEEDED state today. Could one of the authors please contact me with an estimated date for a new draft version? Ron