From l3vpn-bounces@ietf.org Thu Jul 05 21:15:17 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I6cPi-0008WM-Fw; Thu, 05 Jul 2007 21:15:14 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I6cPW-0008IR-L0; Thu, 05 Jul 2007 21:15:02 -0400 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I6cPW-0005sQ-EA; Thu, 05 Jul 2007 21:15:02 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 1FE27175F1; Fri, 6 Jul 2007 01:15:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1I6cPV-0000tb-Mr; Thu, 05 Jul 2007 21: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: Thu, 05 Jul 2007 21:15:01 -0400 X-Spam-Score: 0.3 (/) X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8 Cc: l3vpn@ietf.org Subject: I-D ACTION:draft-ietf-l3vpn-2547bis-mcast-bgp-03.txt 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 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Layer 3 Virtual Private Networks Working Group of the IETF. Title : BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs Author(s) : R. Aggarwal, et al. Filename : draft-ietf-l3vpn-2547bis-mcast-bgp-03.txt Pages : 49 Date : 2007-7-5 This document describes the BGP encodings and procedures for exchanging the information elements required by Multicast in MPLS/BGP IP VPNs, as specified in [MVPN]. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-l3vpn-2547bis-mcast-bgp-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-l3vpn-2547bis-mcast-bgp-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-l3vpn-2547bis-mcast-bgp-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-7-5200417.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-l3vpn-2547bis-mcast-bgp-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-l3vpn-2547bis-mcast-bgp-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-7-5200417.I-D@ietf.org> --OtherAccess-- --NextPart-- From l3vpn-bounces@ietf.org Sun Jul 08 16:44:35 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I7dcN-0003yT-Dq; Sun, 08 Jul 2007 16:44:31 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I7dcL-0003yB-7u; Sun, 08 Jul 2007 16:44:29 -0400 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7dcL-0006UM-0Z; Sun, 08 Jul 2007 16:44:29 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id B616D328E4; Sun, 8 Jul 2007 20:15:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1I7d9q-0000te-J0; Sun, 08 Jul 2007 16: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 16:15:02 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1 Cc: l3vpn@ietf.org Subject: I-D ACTION:draft-ietf-l3vpn-2547bis-mcast-05.txt 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 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Layer 3 Virtual Private Networks Working Group of the IETF. Title : Multicast in MPLS/BGP IP VPNs Author(s) : E. Rosen, R. Aggarwal Filename : draft-ietf-l3vpn-2547bis-mcast-05.txt Pages : 84 Date : 2007-7-8 In order for IP multicast traffic within a BGP/MPLS IP VPN (Virtual Private Network) to travel from one VPN site to another, special protocols and procedures must be implemented by the VPN Service Provider. These protocols and procedures are specified in this document. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-l3vpn-2547bis-mcast-05.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-l3vpn-2547bis-mcast-05.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-l3vpn-2547bis-mcast-05.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-8154807.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-l3vpn-2547bis-mcast-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-l3vpn-2547bis-mcast-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-7-8154807.I-D@ietf.org> --OtherAccess-- --NextPart-- From l3vpn-bounces@ietf.org Thu Jul 19 11:31:01 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IBXxv-0002aw-Gk; Thu, 19 Jul 2007 11:30:55 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IBXxr-0002Y0-SF for l3vpn@ietf.org; Thu, 19 Jul 2007 11:30:51 -0400 Received: from smtpb.juniper.net ([207.17.137.119]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBXxq-0001Qd-Jh for l3vpn@ietf.org; Thu, 19 Jul 2007 11:30:51 -0400 Received: from unknown (HELO proton.jnpr.net) ([10.10.2.37]) by smtpb.juniper.net with ESMTP; 19 Jul 2007 08:30:49 -0700 Received: from [172.25.51.59] ([172.25.51.59] RDNS failed) by proton.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Thu, 19 Jul 2007 11:30:47 -0400 Message-ID: <469F83A5.5020802@juniper.net> Date: Thu, 19 Jul 2007 11:30:45 -0400 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: 19 Jul 2007 15:30:48.0012 (UTC) FILETIME=[C7E698C0:01C7CA19] X-Spam-Score: 0.0 (/) X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014 Subject: IETF 69 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, If you will be presenting at IETF 69, please send your slides to Rick and I so that we can post them. Also, do we have a volunteer to take minutes? (Volunteers will be rewarded with beer!) Ron From l3vpn-bounces@ietf.org Thu Jul 19 15:05:37 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IBbJT-0004qv-5R; Thu, 19 Jul 2007 15:05:23 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IBbJS-0004ql-0r for l3vpn@ietf.org; Thu, 19 Jul 2007 15:05:22 -0400 Received: from wa-out-1112.google.com ([209.85.146.183]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBbJR-0007WT-Ja for l3vpn@ietf.org; Thu, 19 Jul 2007 15:05:22 -0400 Received: by wa-out-1112.google.com with SMTP id k17so894867waf for ; Thu, 19 Jul 2007 12:05:20 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=ogF+wNHkPBenvBJGgv/t9Wr4JkN45ytC/95GH4Jqsw0//AHu51BQ1gEdXemndfdnUEvRqQlG8MQ58Z59ChflP018PyHrscJPRlHDFWKekSRsOSifGwIlJ9bbpqcKqPGCo7T2ty5MoaTNc4OMkBkmZEkAAWfKwzzOzDeQwWtrm/U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=j6+FxPz4CVD9YMt9VolRJNUHHtPaGghp3oqUiXrDk1qKfUBrZmNapSFMc0HqqnHDZVxFWPvqIxB0TIYs7GfkYSY3L4bKCH+iArSJPYcZtgX9C4x5pZvcECYftai9xkSAi/uCgG+ZRHUH1sVzeZ7xpWvkzErR9Xt1I0AVxlbS5tY= Received: by 10.115.75.1 with SMTP id c1mr2853698wal.1184871920617; Thu, 19 Jul 2007 12:05:20 -0700 (PDT) Received: by 10.114.161.5 with HTTP; Thu, 19 Jul 2007 12:05:20 -0700 (PDT) Message-ID: Date: Thu, 19 Jul 2007 12:05:20 -0700 From: "Dilip Kumar" To: l3vpn@ietf.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_45707_21902730.1184871920594" X-Spam-Score: 0.0 (/) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 Subject: RFC-4364: PE - CE routing exchange using BGP 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 ------=_Part_45707_21902730.1184871920594 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi All, I am implementing RFC-4364 and considering BGP for PE to CE (and vice versa) routing information exchange. Following text from Section-7.4 of the RFC indicates that there is no need to run multiple instances of BGP on PE router. "a) Unlike the IGP alternatives, this does not require the PE to run multiple routing algorithm instances in order to talk to multiple CEs." As CEs can use overlapping private addresses, it may be possible that two CEs connected to the PE may have the same IP address for BGP. This will allow only one BGP neighbor to be created at PE, unless some other key, like instance ID, is attached along with peer address at PE. I was wondering how it would be possible without running multiple instances of BGP at PE. Can anyone explain/clarify it ? Thanks, Dilip ------=_Part_45707_21902730.1184871920594 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi All,
    I am implementing RFC-4364 and considering BGP for PE to CE (and vice versa) routing information exchange. Following text from Section-7.4 of the RFC indicates that there is no need to run multiple instances of BGP on PE router.

            "a) Unlike the IGP alternatives, this does not require the PE
               to run multiple routing algorithm instances in order to
               talk to multiple CEs."

As CEs can use overlapping private addresses, it may be possible that two CEs connected to the PE may have the same IP address for BGP. This will allow only one BGP neighbor to be created at PE, unless some other key, like instance ID, is attached along with peer address at PE. I was wondering how it would be possible without running multiple instances of BGP at PE. Can anyone explain/clarify it ?

Thanks,
Dilip


------=_Part_45707_21902730.1184871920594-- From l3vpn-bounces@ietf.org Wed Jul 25 01:07:41 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IDZ5d-0008Mj-6l; Wed, 25 Jul 2007 01:07:13 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IDZ5b-0008Mb-HP for l3vpn@ietf.org; Wed, 25 Jul 2007 01:07:11 -0400 Received: from [2001:200:601:12:230:48ff:fe22:3a84] (helo=mandala.kddilabs.jp) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDZ5b-0003ja-5X for l3vpn@ietf.org; Wed, 25 Jul 2007 01:07:11 -0400 Received: from localhost (localhost [127.0.0.1]) by mandala.kddilabs.jp (Postfix) with ESMTP id F157FEC8D7 for ; Wed, 25 Jul 2007 14:07:09 +0900 (JST) Received: from mail.cn.kddilabs.jp (yellow.lan.kddilabs.jp [2001:200:601:1a00::10]) by mandala.kddilabs.jp (Postfix) with ESMTP id F2CEFECA57 for ; Wed, 25 Jul 2007 14:06:11 +0900 (JST) Received: from [127.0.0.1] (c011.vpn.kddilabs.jp [172.19.87.11]) by mail.cn.kddilabs.jp (Postfix) with ESMTP id 6E6551E0002 for ; Wed, 25 Jul 2007 14:06:11 +0900 (JST) Message-ID: <46A6DA44.5000501@kddilabs.jp> Date: Wed, 25 Jul 2007 14:06:12 +0900 From: Kenji Kumaki User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: l3vpn@ietf.org Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new X-Spam-Score: -1.4 (-) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d Subject: draft-kumaki-l3vpn-e2e-rsvp-te-reqts 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 Hi, I presented the following draft today. "draft-kumaki-l3vpn-e2e-rsvp-te-reqts-04" A few people were interested in this draft in today's meeting. Actually, some service providers have a plan to provide this type of services. Technically, we may deploy this service using L1VPN. But, from service provider's perspective, it may be difficult to deploy GMPLS based technology(including optical switches) as a production network. As you know, many carriers and service providers have already widely deployed IP-VPNs and they provide a lot of services on their networks. Also, a native RSVP based approach between PE and CE is fine. In this case, Admission control can be used. But fast protection technique can not be used in the network. Some customers, especially enterprise cutomers, in Japan are considerably sensitive about traffic disruption. Finally, we want to control and manage data and control planes at PEs. In that sense, we think this draft is practical requirements. Could you give me comments on this draft? Thanks, Kenji