From l2vpn-bounces@ietf.org Tue Jul 03 00:19:52 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5Zrh-0008Md-7E; Tue, 03 Jul 2007 00:19:49 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5Zrg-0008MV-48 for l2vpn@ietf.org; Tue, 03 Jul 2007 00:19:48 -0400 Received: from cat.tcb.net ([64.78.150.134] helo=dog.tcb.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5Zqo-0007zc-20 for l2vpn@ietf.org; Tue, 03 Jul 2007 00:19:48 -0400 Received: from [172.16.15.25] (71-215-68-169.hlrn.qwest.net [71.215.68.169]) by dog.tcb.net (Postfix) with ESMTP id 5685F64352 for ; Mon, 2 Jul 2007 22:18:54 -0600 (MDT) Mime-Version: 1.0 (Apple Message framework v752.2) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: l2vpn@ietf.org From: Shane Amante Date: Mon, 2 Jul 2007 22:18:52 -0600 X-Mailer: Apple Mail (2.752.2) X-Spam-Score: 0.0 (/) X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de Subject: Support for draft-nadeau-l2vpn-vpls-mib-03 to be a WG I-D? 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, The VPLS MIB has been in progress for a little while now. I'd like to solicit input on adopting this draft as a WG doc. Please speak up on whether or not you support this I-D becoming a WG I-D. The call to make this a WG doc will end in 3 weeks, on Friday, July 20, 2007, at 1700 MST (UTC -6). -shane From l2vpn-bounces@ietf.org Tue Jul 03 03:22:53 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5cim-0004fB-0G; Tue, 03 Jul 2007 03:22:48 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5cik-0004f6-Lk for l2vpn@ietf.org; Tue, 03 Jul 2007 03:22:47 -0400 Received: from [80.86.78.228] (helo=smtp.testbed.se) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5cig-0008IQ-B2 for l2vpn@ietf.org; Tue, 03 Jul 2007 03:22:46 -0400 Received: from gw.imc.kth.se ([193.10.152.67] helo=[172.16.2.49]) by fw.testbed.se with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.43) id 1I5cic-0005sn-DR; Tue, 03 Jul 2007 09:22:40 +0200 Message-ID: <4689F935.70008@pi.se> Date: Tue, 03 Jul 2007 09:22:29 +0200 From: Loa Andersson Organization: Acreo AB User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: Shane Amante References: In-Reply-To: X-Enigmail-Version: 0.95.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: -1.4 (-) X-Spam-Report: -1.4 ALL_TRUSTED Passed through trusted hosts only via SMTP X-Spam-Score: 0.0 (/) X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22 Cc: l2vpn@ietf.org Subject: Re: Support for draft-nadeau-l2vpn-vpls-mib-03 to be a WG I-D? 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 support /loa Shane Amante wrote: > Hi, > > The VPLS MIB has been in progress for a little while now. I'd like to > solicit input on adopting this draft as a WG doc. Please speak up on > whether or not you support this I-D becoming a WG I-D. > > The call to make this a WG doc will end in 3 weeks, on Friday, July 20, > 2007, at 1700 MST (UTC -6). > > -shane > > > -- Loa Andersson Principal Networking Architect Acreo AB phone: +46 8 632 77 14 Isafjordsgatan 22 mobile: +46 739 81 21 64 Kista, Sweden email: loa.andersson@acreo.se loa@pi.se From l2vpn-bounces@ietf.org Tue Jul 03 12:59:26 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5lho-0006ym-HP; Tue, 03 Jul 2007 12:58:24 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5lhm-0006xK-LT for l2vpn@ietf.org; Tue, 03 Jul 2007 12:58:22 -0400 Received: from black.monoski.com ([63.227.123.238] helo=napoleon.monoski.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5lgx-0007KH-Kg for l2vpn@ietf.org; Tue, 03 Jul 2007 12:58:22 -0400 Received: from [2.2.2.22] (rasputinw [2.2.2.22]) (authenticated bits=0) by napoleon.monoski.com (8.13.8/8.13.8) with ESMTP id l63GuJL7017766 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 3 Jul 2007 10:56:58 -0600 (MDT) Message-ID: <468A7186.7010602@cisco.com> Date: Tue, 03 Jul 2007 09:55:50 -0600 From: Luca Martini User-Agent: Thunderbird 1.5.0.8 (X11/20061025) MIME-Version: 1.0 To: Shane Amante References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0a1 (napoleon.monoski.com [63.227.123.227]); Tue, 03 Jul 2007 10:56:59 -0600 (MDT) X-Scanned-By: MIMEDefang 2.57 on 63.227.123.227 X-Spam-Score: 1.4 (+) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Cc: l2vpn@ietf.org Subject: Re: Support for draft-nadeau-l2vpn-vpls-mib-03 to be a WG I-D? 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 About time. I support it. Luca Shane Amante wrote: > Hi, > > The VPLS MIB has been in progress for a little while now. I'd like to > solicit input on adopting this draft as a WG doc. Please speak up on > whether or not you support this I-D becoming a WG I-D. > > The call to make this a WG doc will end in 3 weeks, on Friday, July > 20, 2007, at 1700 MST (UTC -6). > > -shane From l2vpn-bounces@ietf.org Tue Jul 03 15:20:49 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5nvT-0006I5-N2; Tue, 03 Jul 2007 15:20:39 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5nvS-0006Hv-32 for l2vpn@ietf.org; Tue, 03 Jul 2007 15:20:38 -0400 Received: from paperclip.laurelnetworks.com ([63.94.127.69]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I5nvR-0007Cn-S9 for l2vpn@ietf.org; Tue, 03 Jul 2007 15:20:38 -0400 Received: from postit.laurelnetworks.com (postit.laurelnetworks.com [63.94.127.21]) by paperclip.laurelnetworks.com (ECI-DND/ECI-DND) with ESMTP id l63JK4r9031379; Tue, 3 Jul 2007 15:20:04 -0400 Received: from sherlock.pit.laurelnetworks.com (washer.pit.laurelnetworks.com [10.0.0.46]) by postit.laurelnetworks.com (ECI-DND/ECI-DND) with ESMTP id l63JK3Ff024395; Tue, 3 Jul 2007 15:20:04 -0400 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 3 Jul 2007 15:20:01 -0400 Message-ID: <36BE198A5480BE4FA343B87A8697D7A803A64F@SHERLOCK.pit.laurelnetworks.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Support for draft-nadeau-l2vpn-vpls-mib-03 to be a WG I-D? Thread-Index: Ace9KXIkmaOwXGqJQQGySvfAn6ibIwAfYkFw References: From: "Prashant Desai" To: "Shane Amante" , X-Spam-Score: 0.0 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 Cc: Subject: RE: Support for draft-nadeau-l2vpn-vpls-mib-03 to be a WG I-D? 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 I support the draft as a WG doc.=20 -----Original Message----- From: Shane Amante [mailto:shane@castlepoint.net]=20 Sent: Tuesday, July 03, 2007 12:19 AM To: l2vpn@ietf.org Subject: Support for draft-nadeau-l2vpn-vpls-mib-03 to be a WG I-D? Hi, The VPLS MIB has been in progress for a little while now. I'd like to solicit input on adopting this draft as a WG doc. Please speak up on whether or not you support this I-D becoming a WG I-D. The call to make this a WG doc will end in 3 weeks, on Friday, July 20, 2007, at 1700 MST (UTC -6). -shane From l2vpn-bounces@ietf.org Sun Jul 08 17:15:38 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I7e6M-0008QI-Sc; Sun, 08 Jul 2007 17:15:30 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I7e5w-0007hn-BO; Sun, 08 Jul 2007 17:15:04 -0400 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7e5u-0007Gt-1s; Sun, 08 Jul 2007 17:15:04 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 0166C328DC; Sun, 8 Jul 2007 21:15:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1I7e5t-0006x1-Sg; Sun, 08 Jul 2007 17:15:01 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Sun, 08 Jul 2007 17:15:01 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8 Cc: l2vpn@ietf.org Subject: I-D ACTION:draft-ietf-l2vpn-arp-mediation-08.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 : ARP Mediation for IP Interworking of Layer 2 VPN Author(s) : H. Shah, et al. Filename : draft-ietf-l2vpn-arp-mediation-08.txt Pages : 25 Date : 2007-7-8 The VPWS service [L2VPN-FRM] provides point-to-point connections between pairs of Customer Edge (CE) devices. It does so by binding two Attachment Circuits (each connecting a CE device with a Provider Edge, PE, device) to a pseudowire (connecting the two PEs). In general, the Attachment Circuits must be of the same technology (e.g., both Ethernet, both ATM), and the pseudowire must carry the frames of that technology. However, if it is known that the frames' payload consists solely of IP datagrams, it is possible to provide a point-to-point connection in which the pseudowire connects Attachment Circuits of different technologies. This requires the PEs to perform a function known as "ARP Mediation". ARP Mediation refers to the process of resolving Layer 2 addresses when different resolution protocols are used on either Attachment Circuit. The methods described in this document are applicable even when the CEs run a routing protocol between them, as long as the routing protocol runs over IP. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-arp-mediation-08.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-arp-mediation-08.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-arp-mediation-08.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-7-8161118.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-l2vpn-arp-mediation-08.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-l2vpn-arp-mediation-08.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-7-8161118.I-D@ietf.org> --OtherAccess-- --NextPart-- From l2vpn-bounces@ietf.org Sun Jul 08 18:15:15 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I7f26-00072m-Ti; Sun, 08 Jul 2007 18:15:10 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I7f1z-00070i-Aj; Sun, 08 Jul 2007 18:15:03 -0400 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I7f1y-00038s-Hd; Sun, 08 Jul 2007 18:15:03 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 5CE702AC76; Sun, 8 Jul 2007 22:15:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1I7f1y-000274-3v; Sun, 08 Jul 2007 18:15:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Sun, 08 Jul 2007 18:15:02 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: 386e0819b1192672467565a524848168 Cc: l2vpn@ietf.org Subject: I-D ACTION:draft-ietf-l2vpn-ipls-07.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 : IP-Only LAN Service (IPLS) Author(s) : H. Shah, et al. Filename : draft-ietf-l2vpn-ipls-07.txt Pages : 22 Date : 2007-7-8 A Virtual Private LAN Service (VPLS) [VPLS] is used to interconnect systems across a wide-area or metropolitan-area network, making it appear that they are on a private LAN. The systems which are interconnected may themselves be LAN switches. If, however, they are IP hosts or IP routers, certain simplifications to the operation of the VPLS are possible. We call this simplified type of VPLS an "IP-only LAN Service" (IPLS). In an IPLS, as in a VPLS, LAN interfaces are run in promiscuous mode, and frames are forwarded based on their destination MAC addresses. However, the maintenance of the MAC forwarding tables is done via signaling, rather than via the MAC address learning procedures specified in [IEEE 802.1D]. This draft specifies the protocol extensions and procedures for support of the IPLS service. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-ipls-07.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-ipls-07.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-ipls-07.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-7-8170619.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-l2vpn-ipls-07.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-l2vpn-ipls-07.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-7-8170619.I-D@ietf.org> --OtherAccess-- --NextPart-- From l2vpn-bounces@ietf.org Mon Jul 09 11:49:15 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I7vTu-0008Eg-4I; Mon, 09 Jul 2007 11:48:58 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I7vTs-0008ER-JZ for l2vpn@ietf.org; Mon, 09 Jul 2007 11:48:56 -0400 Received: from hicks.ciena.com ([63.118.34.22]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I7vTd-0002i0-BM for l2vpn@ietf.org; Mon, 09 Jul 2007 11:48:56 -0400 Received: from lin1-118-39-27.ciena.com (HELO mdmxm02.ciena.com) ([63.118.39.27]) by hicks.ciena.com with ESMTP; 09 Jul 2007 11:48:10 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Mon, 9 Jul 2007 11:48:07 -0400 Message-ID: <3C13767EA2F93441AFB13A630204F1B29FB7A2@mamxm02.ciena.com> In-Reply-To: <5lcvls$88nd48@ripley.ciena.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: I-D ACTION:draft-ietf-l2vpn-arp-mediation-08.txt Thread-Index: AcfCPsJcvWdZr1+wQhqGKYfUf5Dy8AAAHgeA From: "Shah, Himanshu" To: "Andrew G. Malis" X-OriginalArrivalTime: 09 Jul 2007 15:48:08.0690 (UTC) FILETIME=[8C0FF520:01C7C240] X-Spam-Score: 0.0 (/) X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c Cc: l2vpn@ietf.org Subject: RE: I-D ACTION:draft-ietf-l2vpn-arp-mediation-08.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 Hi Andy, The problem of sharing the PW for IPv4 and IPv6 is at the egress PE. When a frame is received over the PW, egress PE knows what = Ethernet/ATM/FR/PPP encapsulation to use based on the characteristic of the PW. So for IPv4 = Ethernet egress attachment circuit, DMAC, SMAC and Ethertype 0x0800 will be used = while in case of IPv6 MAC addresses are derived in the same manner (by PW = association) but Ethernetype is 0x86DD. Another aspect is the IPDA to DMAC derivation = for multicast which are slightly different for IPv4 and IPv6. In order to = make this=20 differentiation for the mixed traffic arriving on the shared PW, egress = PE will=20 have to examine the IP header. Not that this can not be done, but this = is an=20 additional processing step in the data path which has to be weighed = against=20 the control plane overhead that you benefit by reduction in number of = PWs=20 between two PEs. my thoughts... /himanshu > -----Original Message----- > From: Andrew G. Malis [mailto:amalis@gmail.com] > Sent: Monday, July 09, 2007 11:35 AM > To: Shah, Himanshu > Cc: l2vpn@ietf.org > Subject: Re: I-D ACTION:draft-ietf-l2vpn-arp-mediation-08.txt=20 >=20 >=20 > Himanshu, >=20 > I have a comment on section 6.2, which defines the use of the=20 > RFC 3036 Address List TLV to advertise exactly one IPv4 or=20 > one or more IPv6 addresses for the local CE. I would like to=20 > add a sentence to this section that explicitly allows the use=20 > of two Address List TLVs in the same Label Mapping message,=20 > where one is used for an IPv4 address and the other is used=20 > for one or more IPv6 addresses. This allows multiplexing both=20 > IPv4 and IPv6 on the same PW, which can cut down the number=20 > of PWs required when both IPv4 and IPv6 are in use between=20 > the pair of CEs. >=20 > Thanks, > Andy >=20 > At 7/8/2007 05:15 PM -0400, Internet-Drafts@ietf.org wrote: > >A New Internet-Draft is available from the on-line Internet-Drafts=20 > >directories. > >This draft is a work item of the Layer 2 Virtual Private=20 > Networks Working Group of the IETF. > > > > Title : ARP Mediation for IP Interworking=20 > of Layer 2 VPN > > Author(s) : H. Shah, et al. > > Filename : draft-ietf-l2vpn-arp-mediation-08.txt > > Pages : 25 > > Date : 2007-7-8 > > =20 >=20 From l2vpn-bounces@ietf.org Mon Jul 09 11:50:59 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I7vVo-0000nS-3o; Mon, 09 Jul 2007 11:50:56 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I7vVi-0000mi-9B for l2vpn@ietf.org; Mon, 09 Jul 2007 11:50:50 -0400 Received: from smtp102.vzn.mail.dcn.yahoo.com ([209.73.179.140]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1I7vVd-0003SD-Te for l2vpn@ietf.org; Mon, 09 Jul 2007 11:50:50 -0400 Received: (qmail 53814 invoked from network); 9 Jul 2007 15:50:45 -0000 Received: from unknown (HELO AMALIS.verizon.net) (agmalis@verizon.net@132.197.71.167 with login) by smtp102.vzn.mail.dcn.yahoo.com with SMTP; 9 Jul 2007 15:50:45 -0000 X-YMail-OSG: geloQqIVM1lV20moBi_1omGqLB2izjn1vfxTEO.A9jua9El5kJwHZmS3skhhEDIYZeFICKNDVA-- X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Mon, 09 Jul 2007 11:50:39 -0400 To: hshah@ciena.com From: "Andrew G. Malis" Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Spam-Score: 0.0 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 Cc: l2vpn@ietf.org Subject: Re: I-D ACTION:draft-ietf-l2vpn-arp-mediation-08.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 Message-Id: Himanshu, I have a comment on section 6.2, which defines the use of the RFC 3036 Address List TLV to advertise exactly one IPv4 or one or more IPv6 addresses for the local CE. I would like to add a sentence to this section that explicitly allows the use of two Address List TLVs in the same Label Mapping message, where one is used for an IPv4 address and the other is used for one or more IPv6 addresses. This allows multiplexing both IPv4 and IPv6 on the same PW, which can cut down the number of PWs required when both IPv4 and IPv6 are in use between the pair of CEs. Thanks, Andy At 7/8/2007 05:15 PM -0400, Internet-Drafts@ietf.org wrote: >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 : ARP Mediation for IP Interworking of Layer 2 VPN > Author(s) : H. Shah, et al. > Filename : draft-ietf-l2vpn-arp-mediation-08.txt > Pages : 25 > Date : 2007-7-8 > From l2vpn-bounces@ietf.org Mon Jul 09 12:04: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 1I7vis-00007K-2S; Mon, 09 Jul 2007 12:04:26 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I7vik-0008Up-BQ for l2vpn@ietf.org; Mon, 09 Jul 2007 12:04:19 -0400 Received: from wr-out-0506.google.com ([64.233.184.237]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7vif-0003pd-Ss for l2vpn@ietf.org; Mon, 09 Jul 2007 12:04:18 -0400 Received: by wr-out-0506.google.com with SMTP id i23so443459wra for ; Mon, 09 Jul 2007 09:04:13 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=GE5OZqO7e6gnFoKGT/U+CraJ1Ji8klqEO7kdIK2913GsrVazAj1GeQyxveTIduLUAV2Nz/DgyzgUTZ5D3UfYWWJSRY+H9pHsbppFTJSLDK911eQMKNQMMd3efAR+z+Yf5ru1zq1YCyPkK2pLPrSgk7OqLg1casper5hnSEKLBec= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=uSONNfzKJlQfCyOSuBy8SCSfCCVfFxqzL9RXJXQIG45nnQOajJOhkjEXpiPLl+1KD+AwgnEp2ljjJUI6tlHbsLinKSwbRXZ8E+9RFzHJ6Me83PXMsWj7sSG4ppzhMFIT1qgfhZERj1Uzaw1y+akHFnpkSCIjH0J+jZ8LrG2UOsY= Received: by 10.78.81.20 with SMTP id e20mr1650357hub.1183997052576; Mon, 09 Jul 2007 09:04:12 -0700 (PDT) Received: by 10.78.188.4 with HTTP; Mon, 9 Jul 2007 09:04:12 -0700 (PDT) Message-ID: <8c99930d0707090904x1157f524x3fb655c4f7ea78f@mail.gmail.com> Date: Mon, 9 Jul 2007 12:04:12 -0400 From: "Andrew G. Malis" To: "Shah, Himanshu" In-Reply-To: <3C13767EA2F93441AFB13A630204F1B29FB7A2@mamxm02.ciena.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_170055_9606133.1183997052554" References: <5lcvls$88nd48@ripley.ciena.com> <3C13767EA2F93441AFB13A630204F1B29FB7A2@mamxm02.ciena.com> X-Google-Sender-Auth: d3302f3b73334852 X-Spam-Score: 0.1 (/) X-Scan-Signature: 2857c5c041d6c02d7181d602c22822c8 Cc: l2vpn@ietf.org Subject: Re: I-D ACTION:draft-ietf-l2vpn-arp-mediation-08.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 ------=_Part_170055_9606133.1183997052554 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Himanshu, You're absolutely right, this would require an inspection of the IP header, but routers are already doing that when receiving IPv4 and IPv6 on unlabled interfaces - unless they're always relying on the L2 header for IPv4 vs. IPv6 identification. So I guess we need to hear from the vendors whether sharing the same PW for IPv4 and IPv6 can be easily implemented using current HW. Cheers, Andy On 7/9/07, Shah, Himanshu wrote: > > Hi Andy, > The problem of sharing the PW for IPv4 and IPv6 is at the egress PE. > When a frame is received over the PW, egress PE knows what > Ethernet/ATM/FR/PPP > encapsulation to use based on the characteristic of the PW. So for IPv4 > Ethernet > egress attachment circuit, DMAC, SMAC and Ethertype 0x0800 will be used > while > in case of IPv6 MAC addresses are derived in the same manner (by PW > association) > but Ethernetype is 0x86DD. Another aspect is the IPDA to DMAC derivation > for > multicast which are slightly different for IPv4 and IPv6. In order to make > this > differentiation for the mixed traffic arriving on the shared PW, egress PE > will > have to examine the IP header. Not that this can not be done, but this is > an > additional processing step in the data path which has to be weighed > against > the control plane overhead that you benefit by reduction in number of PWs > between two PEs. > > my thoughts... > > /himanshu > > > -----Original Message----- > > From: Andrew G. Malis [mailto:amalis@gmail.com] > > Sent: Monday, July 09, 2007 11:35 AM > > To: Shah, Himanshu > > Cc: l2vpn@ietf.org > > Subject: Re: I-D ACTION:draft-ietf-l2vpn-arp-mediation-08.txt > > > > > > Himanshu, > > > > I have a comment on section 6.2, which defines the use of the > > RFC 3036 Address List TLV to advertise exactly one IPv4 or > > one or more IPv6 addresses for the local CE. I would like to > > add a sentence to this section that explicitly allows the use > > of two Address List TLVs in the same Label Mapping message, > > where one is used for an IPv4 address and the other is used > > for one or more IPv6 addresses. This allows multiplexing both > > IPv4 and IPv6 on the same PW, which can cut down the number > > of PWs required when both IPv4 and IPv6 are in use between > > the pair of CEs. > > > > Thanks, > > Andy > > > > At 7/8/2007 05:15 PM -0400, Internet-Drafts@ietf.org wrote: > > >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 : ARP Mediation for IP Interworking > > of Layer 2 VPN > > > Author(s) : H. Shah, et al. > > > Filename : draft-ietf-l2vpn-arp-mediation-08.txt > > > Pages : 25 > > > Date : 2007-7-8 > > > > > > > ------=_Part_170055_9606133.1183997052554 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
Himanshu,
 
You're absolutely right, this would require an inspection of the IP header, but routers are already doing that when receiving IPv4 and IPv6 on unlabled interfaces - unless they're always relying on the L2 header for IPv4 vs. IPv6 identification. So I guess we need to hear from the vendors whether sharing the same PW for IPv4 and IPv6 can be easily implemented using current HW.
 
Cheers,
Andy
 
On 7/9/07, Shah, Himanshu <hshah@ciena.com> wrote:
Hi Andy,
The problem of sharing the PW for IPv4 and IPv6 is at the egress PE.
When a frame is received over the PW, egress PE knows what Ethernet/ATM/FR/PPP
encapsulation to use based on the characteristic of the PW. So for IPv4 Ethernet
egress attachment circuit, DMAC, SMAC and Ethertype 0x0800 will be used while
in case of IPv6 MAC addresses are derived in the same manner (by PW association)
but Ethernetype is 0x86DD. Another aspect is the IPDA to DMAC derivation for
multicast which are slightly different for IPv4 and IPv6. In order to make this
differentiation for the mixed traffic arriving on the shared PW, egress PE will
have to examine the IP header. Not that this can not be done, but this is an
additional processing step in the data path which has to be weighed against
the control plane overhead that you benefit by reduction in number of PWs
between two PEs.

my thoughts...

/himanshu

> -----Original Message-----
> From: Andrew G. Malis [mailto:amalis@gmail.com]
> Sent: Monday, July 09, 2007 11:35 AM
> To: Shah, Himanshu
> Cc: l2vpn@ietf.org
> Subject: Re: I-D ACTION:draft-ietf-l2vpn-arp-mediation-08.txt
>
>
> Himanshu,
>
> I have a comment on section 6.2, which defines the use of the
> RFC 3036 Address List TLV to advertise exactly one IPv4 or
> one or more IPv6 addresses for the local CE. I would like to
> add a sentence to this section that explicitly allows the use
> of two Address List TLVs in the same Label Mapping message,
> where one is used for an IPv4 address and the other is used
> for one or more IPv6 addresses. This allows multiplexing both
> IPv4 and IPv6 on the same PW, which can cut down the number
> of PWs required when both IPv4 and IPv6 are in use between
> the pair of CEs.
>
> Thanks,
> Andy
>
> At 7/8/2007 05:15 PM -0400, Internet-Drafts@ietf.org wrote:
> >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           : ARP Mediation for IP Interworking
> of Layer 2 VPN
> >        Author(s)       : H. Shah, et al.
> >        Filename        : draft-ietf-l2vpn-arp-mediation-08.txt
> >        Pages           : 25
> >        Date            : 2007-7-8
> >
>


------=_Part_170055_9606133.1183997052554-- From l2vpn-bounces@ietf.org Mon Jul 09 16:01:40 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I7zQP-0001CM-W6; Mon, 09 Jul 2007 16:01:37 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I7vHh-00032i-FQ for l2vpn@ietf.org; Mon, 09 Jul 2007 11:36:21 -0400 Received: from smtp103.vzn.mail.dcn.yahoo.com ([209.73.179.141]) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1I7vHS-0002Qk-6x for l2vpn@ietf.org; Mon, 09 Jul 2007 11:36:21 -0400 Received: (qmail 91709 invoked from network); 9 Jul 2007 15:35:01 -0000 Received: from unknown (HELO AMALIS.verizon.net) (agmalis@verizon.net@132.197.71.167 with login) by smtp103.vzn.mail.dcn.yahoo.com with SMTP; 9 Jul 2007 15:35:01 -0000 X-YMail-OSG: jZE3ZtYVM1kUtZM_XjyepB0KQxPwTraaatm2QB23pfpuf3JIdTZub30JZZF1tEfDaU9m9IK6tg-- X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Mon, 09 Jul 2007 11:34:56 -0400 To: hshah@ciena.com From: "Andrew G. Malis" In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Spam-Score: 0.0 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 X-Mailman-Approved-At: Mon, 09 Jul 2007 16:01:32 -0400 Cc: l2vpn@ietf.org Subject: Re: I-D ACTION:draft-ietf-l2vpn-arp-mediation-08.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 Message-Id: Himanshu, I have a comment on section 6.2, which defines the use of the RFC 3036 Address List TLV to advertise exactly one IPv4 or one or more IPv6 addresses for the local CE. I would like to add a sentence to this section that explicitly allows the use of two Address List TLVs in the same Label Mapping message, where one is used for an IPv4 address and the other is used for one or more IPv6 addresses. This allows multiplexing both IPv4 and IPv6 on the same PW, which can cut down the number of PWs required when both IPv4 and IPv6 are in use between the pair of CEs. Thanks, Andy At 7/8/2007 05:15 PM -0400, Internet-Drafts@ietf.org wrote: >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 : ARP Mediation for IP Interworking of Layer 2 VPN > Author(s) : H. Shah, et al. > Filename : draft-ietf-l2vpn-arp-mediation-08.txt > Pages : 25 > Date : 2007-7-8 > From l2vpn-bounces@ietf.org Fri Jul 13 16:52:30 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I9S7n-0004rk-1m; Fri, 13 Jul 2007 16:52:27 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I9S7l-0004k3-EI; Fri, 13 Jul 2007 16:52:25 -0400 Received: from [202.99.23.227] (helo=people.com.cn) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1I9S7k-0000Qv-JO; Fri, 13 Jul 2007 16:52:25 -0400 Received: from people.com.cn([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8) with SMTP id jm324697ec2b; Sat, 14 Jul 2007 05:03:49 +0800 Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC 2.9.5.8) with SMTP id jmb946936d4e; Tue, 10 Jul 2007 10:40:18 +0800 Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC 2.9.5.8) with SMTP id AISP action; Tue, 10 Jul 2007 10:40:18 +0800 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I7f24-00071d-Hg; Sun, 08 Jul 2007 18:15:08 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I7f1z-00070i-Aj; Sun, 08 Jul 2007 18:15:03 -0400 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I7f1y-00038s-Hd; Sun, 08 Jul 2007 18:15:03 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 5CE702AC76; Sun, 8 Jul 2007 22:15:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1I7f1y-000274-3v; Sun, 08 Jul 2007 18:15:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Sun, 08 Jul 2007 18:15:02 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: 386e0819b1192672467565a524848168 X-BeenThere: i-d-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Archive: X-AIMC-AUTH: (null) X-AIMC-MAILFROM: i-d-announce-bounces@ietf.org X-AIMC-AUTH: (null) X-AIMC-MAILFROM: Internet-Drafts@ietf.org X-Auto-Forward: jaglee@people.com.cn jag@kw.com.cn X-Spam-Score: 2.8 (++) X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b Cc: l2vpn@ietf.org Subject: I-D ACTION:draft-ietf-l2vpn-ipls-07.txt X-BeenThere: l2vpn@ietf.org Reply-To: internet-drafts@ietf.org 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 : IP-Only LAN Service (IPLS) Author(s) : H. Shah, et al. Filename : draft-ietf-l2vpn-ipls-07.txt Pages : 22 Date : 2007-7-8 A Virtual Private LAN Service (VPLS) [VPLS] is used to interconnect systems across a wide-area or metropolitan-area network, making it appear that they are on a private LAN. The systems which are interconnected may themselves be LAN switches. If, however, they are IP hosts or IP routers, certain simplifications to the operation of the VPLS are possible. We call this simplified type of VPLS an "IP-only LAN Service" (IPLS). In an IPLS, as in a VPLS, LAN interfaces are run in promiscuous mode, and frames are forwarded based on their destination MAC addresses. However, the maintenance of the MAC forwarding tables is done via signaling, rather than via the MAC address learning procedures specified in [IEEE 802.1D]. This draft specifies the protocol extensions and procedures for support of the IPLS service. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-ipls-07.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-ipls-07.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-ipls-07.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-7-8170619.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-l2vpn-ipls-07.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-l2vpn-ipls-07.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-7-8170619.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/i-d-announce --NextPart-- From l2vpn-bounces@ietf.org Sat Jul 14 12:30:59 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I9kWD-0001XE-5m; Sat, 14 Jul 2007 12:30:53 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I9kWA-0001Wm-3y for l2vpn@ietf.org; Sat, 14 Jul 2007 12:30:51 -0400 Received: from dog.tcb.net ([64.78.150.133]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I9kW6-0005Vc-RR for l2vpn@ietf.org; Sat, 14 Jul 2007 12:30:50 -0400 Received: by dog.tcb.net (Postfix, from userid 0) id 94932268470; Sat, 14 Jul 2007 10:30:46 -0600 (MDT) Received: from [172.16.15.25] (71-218-102-100.hlrn.qwest.net [71.218.102.100]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; for l2vpn@ietf.org; Sat, 14 Jul 2007 10:30:46 -0600 (MDT) (envelope-from shane@castlepoint.net) X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=71.218.102.100; client-port=1931; syn-fingerprint=65535:55:1:64:M1460,N,W0,N,N,T,S MacOS 10.4.8; data-bytes=0 Mime-Version: 1.0 (Apple Message framework v752.2) Content-Transfer-Encoding: 7bit Message-Id: <7BFF8B87-578E-4E45-A856-6EC611A0B320@castlepoint.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: l2vpn@ietf.org From: Shane Amante Date: Sat, 14 Jul 2007 10:30:30 -0600 X-Mailer: Apple Mail (2.752.2) X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d Subject: Draft IETF 69 (Chicago) Agenda 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 Chicago: http://www3.ietf.org/proceedings/07jul/agenda/l2vpn.html Please let me know if I missed anyone's request, or any other comments or corrections. -shane IETF 69: Layer 2 Virtual Private Network WG (l2vpn) Agenda WEDNESDAY, July 25, 2007, 0900-1130 =================================== Chairs: Vach Kompella Shane Amante WG Status Web Page: http://tools.ietf.org/wg/l2vpn/ 1) Administrivia 2) WG Status and Update 3) UPDATE: VPLS Interoperability with Provider Backbone Bridges http://tools.ietf.org/html/draft-sajassi-l2vpn-vpls-pbb-interop-01 Ali Sajassi (sajassi@cisco.com) 10 mins 4) VPLS Extensions for Provider Backbone Bridging http://tools.ietf.org/html/draft-balus-l2vpn-vpls-802.1ah-01 Florin Balus (florin.balus@alcatel-lucent.com) 10 mins 5) Meeting Closes From l2vpn-bounces@ietf.org Thu Jul 26 12:30:30 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IE627-00051r-Ns; Thu, 26 Jul 2007 12:17:47 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IE622-0004yE-FE for l2vpn@ietf.org; Thu, 26 Jul 2007 12:17:43 -0400 Received: from dog.tcb.net ([64.78.150.133]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IE61q-0002Tp-H7 for l2vpn@ietf.org; Thu, 26 Jul 2007 12:17:42 -0400 Received: by dog.tcb.net (Postfix, from userid 0) id E4C0A2680BA; Thu, 26 Jul 2007 10:17:29 -0600 (MDT) 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; Thu, 26 Jul 2007 10:17:29 -0600 (MDT) (envelope-from shane@castlepoint.net) X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=64.78.150.133; client-port=41941; data-bytes=0 Message-ID: <46A8C918.1080109@castlepoint.net> Date: Thu, 26 Jul 2007 10:17:28 -0600 From: Shane Amante User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: l2vpn@ietf.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 Subject: Re: Support for draft-nadeau-l2vpn-vpls-mib-03 to be a WG I-D? X-BeenThere: l2vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: l2vpn-chairs@tools.ietf.org List-Id: l2vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: l2vpn-bounces@ietf.org Shane Amante wrote: > Hi, > > The VPLS MIB has been in progress for a little while now. I'd like to > solicit input on adopting this draft as a WG doc. Please speak up on > whether or not you support this I-D becoming a WG I-D. > > The call to make this a WG doc will end in 3 weeks, on Friday, July 20, > 2007, at 1700 MST (UTC -6). This ends the call to make this document a WG draft. There appears to be consensus to make this document a WG draft. Would the authors please re-submit this draft with the following title to the ID Repository: draft-ietf-l2vpn-vpls-mib-00.txt Thanks! -shane & Vach