Re: [Idr] Re:Commentsondraft-zhang-idr-bgp-entire-routes-reflect-00.txt
"Manav Bhatia" <manav@riverstonenet.com> Sat, 30 July 2005 02:32 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dyh90-0002DY-F6; Fri, 29 Jul 2005 22:32:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dyh8w-0002DT-6s for idr@megatron.ietf.org; Fri, 29 Jul 2005 22:32:08 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24883 for <idr@ietf.org>; Fri, 29 Jul 2005 22:31:59 -0400 (EDT)
Received: from mail.riverstonenet.com ([63.113.148.10] helo=riverstonenet.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Dyhec-0007JW-FT for idr@ietf.org; Fri, 29 Jul 2005 23:04:52 -0400
Received: from legolas.rs.riverstonenet.com by riverstonenet.com (8.9.3+Sun/SMI-SVR4-Yago) id TAA25157; Fri, 29 Jul 2005 19:31:29 -0700 (PDT)
Received: from manav ([10.128.16.128]) by legolas.rs.riverstonenet.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 29 Jul 2005 19:31:28 -0700
Message-ID: <012101c594af$16b140b0$6401a8c0@manav>
From: Manav Bhatia <manav@riverstonenet.com>
To: Zhang Renhai <zhangrenhai@huawei.com>
References: <20050719171206.70331.qmail@web60718.mail.yahoo.com><Pine.GSO.4.58.0507271411200.2495@aretana-u10.cisco.com> <000901c59404$f4baf3c0$69646e0a@huawei.com>
Subject: Re: [Idr] Re:Commentsondraft-zhang-idr-bgp-entire-routes-reflect-00.txt
Date: Sat, 30 Jul 2005 08:03:33 +0530
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-OriginalArrivalTime: 30 Jul 2005 02:31:28.0617 (UTC) FILETIME=[CA1EE590:01C594AE]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Content-Transfer-Encoding: 7bit
Cc: idr@ietf.org
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org
Hi Zhang, Besides proposing a way to advertise multiple paths, draft-bhatia-ecmp-routes-in-bgp-01.txt also discusses how an implementation should construct its AS_PATH wherein the path length is preserved and sufficient information is provided to avoid loops, if its using equal cost BGP paths for its forwarding. Thanks, Manav ----- Original Message ----- From: "Zhang Renhai" <zhangrenhai@huawei.com> To: "Alvaro Retana" <aretana@cisco.com>; "Tulip Rasputin" <tulip_rasputin@yahoo.ca> Cc: <raszuk@cisco.com>; <idr@ietf.org> Sent: Friday, July 29, 2005 11:45 AM Subject: Re: [Idr] Re:Commentsondraft-zhang-idr-bgp-entire-routes-reflect-00.txt > Hi, Alvaro > > I think this is an interesting topic because there are now three drafts addressing it > I recently looked through other two drafts, one is yours and other is > draft-bhatia-ecmp-routes-in-bgp-01.txt, and I think the goal is basically same but the > mechanism to achieve it is very different. If you will, I'd like to discuss with you next > week at Paris if the meeting time is not enough to talk. > > Cheers, > Zhang > > ----- Original Message ----- > From: "Alvaro Retana" <aretana@cisco.com> > To: "Tulip Rasputin" <tulip_rasputin@yahoo.ca> > Cc: <raszuk@cisco.com>; <idr@ietf.org> > Sent: Thursday, July 28, 2005 5:16 AM > Subject: Re: [Idr] Re: Commentsondraft-zhang-idr-bgp-entire-routes-reflect-00.txt > > > > On Tue, 19 Jul 2005, Tulip Rasputin wrote: > > > > Tulip: > > > > -> !> Would you be so kind to comment what proposed in your draft has not > > -> !> already been addressed in our ADD_PATHs proposal RR !> functionality > > -> wise ? > > -> > > -> I see absolutely nothing wrong in this! > > -> > > -> There isnt any rule in the IETF that forbids multiple submissions to > > -> achieve the same objective. Its left on the community to decide which > > -> proposal they are most comfortable with. If it happens to be the draft > > -> thats been submitted later, then so be it! > > -> > > -> IETF is an open standards body, in case you forgot that, and nothing, > > -> is patented here. If you dont want others to address the same issues > > -> that you've been trying to solve, then IETF isnt really the right place > > -> for you to start with! > > -> > > -> YOu should be patenting your ideas, but then, nobody else is going to > > -> implement them. > > > > I think Robert was only asking Zhang to compare...nothing else. > > > > In any case, I think we can all agree about the openness of the IETF, > > multiple solutions, community, etc.. > > > > Just to clarify, we have no IPR claims over any part of the ADD_PATH work. > > Also, We have posted an update to the draft and plan to talk about it next > > week. > > > > Thanks! > > > > Alvaro. > > > > -> !> Ref: draft-walton-bgp-add-paths-03.txt > > > > _______________________________________________ > > Idr mailing list > > Idr@ietf.org > > https://www1.ietf.org/mailman/listinfo/idr > > > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://www1.ietf.org/mailman/listinfo/idr _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id WAA21495 for <idr-archive@nic.merit.edu>; Fri, 29 Jul 2005 22:34:00 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dyh90-0002DY-CY; Fri, 29 Jul 2005 22:32:10 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dyh8w-0002DT-6s for idr@megatron.ietf.org; Fri, 29 Jul 2005 22:32:08 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24883 for <idr@ietf.org>; Fri, 29 Jul 2005 22:31:59 -0400 (EDT) Received: from mail.riverstonenet.com ([63.113.148.10] helo=riverstonenet.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Dyhec-0007JW-FT for idr@ietf.org; Fri, 29 Jul 2005 23:04:52 -0400 Received: from legolas.rs.riverstonenet.com by riverstonenet.com (8.9.3+Sun/SMI-SVR4-Yago) id TAA25157; Fri, 29 Jul 2005 19:31:29 -0700 (PDT) Received: from manav ([10.128.16.128]) by legolas.rs.riverstonenet.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 29 Jul 2005 19:31:28 -0700 Message-ID: <012101c594af$16b140b0$6401a8c0@manav> From: "Manav Bhatia" <manav@riverstonenet.com> To: "Zhang Renhai" <zhangrenhai@huawei.com> References: <20050719171206.70331.qmail@web60718.mail.yahoo.com><Pine.GSO.4.58.0507271411200.2495@aretana-u10.cisco.com> <000901c59404$f4baf3c0$69646e0a@huawei.com> Subject: Re: [Idr] Re:Commentsondraft-zhang-idr-bgp-entire-routes-reflect-00.txt Date: Sat, 30 Jul 2005 08:03:33 +0530 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1478 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478 X-OriginalArrivalTime: 30 Jul 2005 02:31:28.0617 (UTC) FILETIME=[CA1EE590:01C594AE] X-Spam-Score: 0.0 (/) X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87 Content-Transfer-Encoding: 7bit Cc: idr@ietf.org X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing <idr.ietf.org> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe> List-Archive: <http://www1.ietf.org/pipermail/idr> List-Post: <mailto:idr@ietf.org> List-Help: <mailto:idr-request@ietf.org?subject=help> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe> Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org Hi Zhang, Besides proposing a way to advertise multiple paths, draft-bhatia-ecmp-routes-in-bgp-01.txt also discusses how an implementation should construct its AS_PATH wherein the path length is preserved and sufficient information is provided to avoid loops, if its using equal cost BGP paths for its forwarding. Thanks, Manav ----- Original Message ----- From: "Zhang Renhai" <zhangrenhai@huawei.com> To: "Alvaro Retana" <aretana@cisco.com>; "Tulip Rasputin" <tulip_rasputin@yahoo.ca> Cc: <raszuk@cisco.com>; <idr@ietf.org> Sent: Friday, July 29, 2005 11:45 AM Subject: Re: [Idr] Re:Commentsondraft-zhang-idr-bgp-entire-routes-reflect-00.txt > Hi, Alvaro > > I think this is an interesting topic because there are now three drafts addressing it > I recently looked through other two drafts, one is yours and other is > draft-bhatia-ecmp-routes-in-bgp-01.txt, and I think the goal is basically same but the > mechanism to achieve it is very different. If you will, I'd like to discuss with you next > week at Paris if the meeting time is not enough to talk. > > Cheers, > Zhang > > ----- Original Message ----- > From: "Alvaro Retana" <aretana@cisco.com> > To: "Tulip Rasputin" <tulip_rasputin@yahoo.ca> > Cc: <raszuk@cisco.com>; <idr@ietf.org> > Sent: Thursday, July 28, 2005 5:16 AM > Subject: Re: [Idr] Re: Commentsondraft-zhang-idr-bgp-entire-routes-reflect-00.txt > > > > On Tue, 19 Jul 2005, Tulip Rasputin wrote: > > > > Tulip: > > > > -> !> Would you be so kind to comment what proposed in your draft has not > > -> !> already been addressed in our ADD_PATHs proposal RR !> functionality > > -> wise ? > > -> > > -> I see absolutely nothing wrong in this! > > -> > > -> There isnt any rule in the IETF that forbids multiple submissions to > > -> achieve the same objective. Its left on the community to decide which > > -> proposal they are most comfortable with. If it happens to be the draft > > -> thats been submitted later, then so be it! > > -> > > -> IETF is an open standards body, in case you forgot that, and nothing, > > -> is patented here. If you dont want others to address the same issues > > -> that you've been trying to solve, then IETF isnt really the right place > > -> for you to start with! > > -> > > -> YOu should be patenting your ideas, but then, nobody else is going to > > -> implement them. > > > > I think Robert was only asking Zhang to compare...nothing else. > > > > In any case, I think we can all agree about the openness of the IETF, > > multiple solutions, community, etc.. > > > > Just to clarify, we have no IPR claims over any part of the ADD_PATH work. > > Also, We have posted an update to the draft and plan to talk about it next > > week. > > > > Thanks! > > > > Alvaro. > > > > -> !> Ref: draft-walton-bgp-add-paths-03.txt > > > > _______________________________________________ > > Idr mailing list > > Idr@ietf.org > > https://www1.ietf.org/mailman/listinfo/idr > > > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://www1.ietf.org/mailman/listinfo/idr _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id CAA24297 for <idr-archive@nic.merit.edu>; Fri, 29 Jul 2005 02:41:01 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DyOXL-0007bq-It; Fri, 29 Jul 2005 02:40:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DyOXK-0007Xv-3a for idr@megatron.ietf.org; Fri, 29 Jul 2005 02:40:02 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA16027 for <idr@ietf.org>; Fri, 29 Jul 2005 02:39:52 -0400 (EDT) Received: from szxga01-in.huawei.com ([61.144.161.53] helo=huawei.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DyP2n-00066Q-Dj for idr@ietf.org; Fri, 29 Jul 2005 03:12:35 -0400 Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IKD00IRWMQG34@szxga01-in.huawei.com> for idr@ietf.org; Fri, 29 Jul 2005 14:44:40 +0800 (CST) Received: from szxml02-in ([172.24.1.6]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IKD009JOMQGZ1@szxga01-in.huawei.com> for idr@ietf.org; Fri, 29 Jul 2005 14:44:40 +0800 (CST) Received: from z18605 ([10.110.100.105]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0IKD005ZCMSL5Q@szxml02-in.huawei.com>; Fri, 29 Jul 2005 14:45:57 +0800 (CST) Date: Fri, 29 Jul 2005 14:15:44 +0800 From: Zhang Renhai <zhangrenhai@huawei.com> Subject: Re: [Idr] Re: Commentsondraft-zhang-idr-bgp-entire-routes-reflect-00.txt To: Alvaro Retana <aretana@cisco.com>, Tulip Rasputin <tulip_rasputin@yahoo.ca> Message-id: <000901c59404$f4baf3c0$69646e0a@huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Mailer: Microsoft Outlook Express 5.50.4807.1700 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <20050719171206.70331.qmail@web60718.mail.yahoo.com> <Pine.GSO.4.58.0507271411200.2495@aretana-u10.cisco.com> X-Spam-Score: 0.0 (/) X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15 Content-Transfer-Encoding: 7BIT Cc: raszuk@cisco.com, idr@ietf.org X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing <idr.ietf.org> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe> List-Archive: <http://www1.ietf.org/pipermail/idr> List-Post: <mailto:idr@ietf.org> List-Help: <mailto:idr-request@ietf.org?subject=help> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe> Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org Hi, Alvaro I think this is an interesting topic because there are now three drafts addressing it I recently looked through other two drafts, one is yours and other is draft-bhatia-ecmp-routes-in-bgp-01.txt, and I think the goal is basically same but the mechanism to achieve it is very different. If you will, I'd like to discuss with you next week at Paris if the meeting time is not enough to talk. Cheers, Zhang ----- Original Message ----- From: "Alvaro Retana" <aretana@cisco.com> To: "Tulip Rasputin" <tulip_rasputin@yahoo.ca> Cc: <raszuk@cisco.com>; <idr@ietf.org> Sent: Thursday, July 28, 2005 5:16 AM Subject: Re: [Idr] Re: Commentsondraft-zhang-idr-bgp-entire-routes-reflect-00.txt > On Tue, 19 Jul 2005, Tulip Rasputin wrote: > > Tulip: > > -> !> Would you be so kind to comment what proposed in your draft has not > -> !> already been addressed in our ADD_PATHs proposal RR !> functionality > -> wise ? > -> > -> I see absolutely nothing wrong in this! > -> > -> There isnt any rule in the IETF that forbids multiple submissions to > -> achieve the same objective. Its left on the community to decide which > -> proposal they are most comfortable with. If it happens to be the draft > -> thats been submitted later, then so be it! > -> > -> IETF is an open standards body, in case you forgot that, and nothing, > -> is patented here. If you dont want others to address the same issues > -> that you've been trying to solve, then IETF isnt really the right place > -> for you to start with! > -> > -> YOu should be patenting your ideas, but then, nobody else is going to > -> implement them. > > I think Robert was only asking Zhang to compare...nothing else. > > In any case, I think we can all agree about the openness of the IETF, > multiple solutions, community, etc.. > > Just to clarify, we have no IPR claims over any part of the ADD_PATH work. > Also, We have posted an update to the draft and plan to talk about it next > week. > > Thanks! > > Alvaro. > > -> !> Ref: draft-walton-bgp-add-paths-03.txt > > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://www1.ietf.org/mailman/listinfo/idr _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id RAA24489 for <idr-archive@nic.merit.edu>; Wed, 27 Jul 2005 17:17:50 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DxtH3-0005MO-5Z; Wed, 27 Jul 2005 17:17:09 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DxtH1-0005MJ-Ti for idr@megatron.ietf.org; Wed, 27 Jul 2005 17:17:07 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03812 for <idr@ietf.org>; Wed, 27 Jul 2005 17:17:05 -0400 (EDT) Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DxtmL-0003fx-NO for idr@ietf.org; Wed, 27 Jul 2005 17:49:31 -0400 Received: from rtp-core-2.cisco.com (64.102.124.13) by rtp-iport-2.cisco.com with ESMTP; 27 Jul 2005 17:16:58 -0400 X-IronPort-AV: i="3.95,146,1120449600"; d="scan'208"; a="64209454:sNHT29424112" Received: from cisco.com (shako.cisco.com [64.102.17.78]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j6RLGvVu001530; Wed, 27 Jul 2005 17:16:57 -0400 (EDT) Received: from aretana-u10.cisco.com (aretana-u10.cisco.com [64.102.48.77]) by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id RAA12871; Wed, 27 Jul 2005 17:16:57 -0400 (EDT) Date: Wed, 27 Jul 2005 14:16:57 -0700 (PDT) From: Alvaro Retana <aretana@cisco.com> To: Tulip Rasputin <tulip_rasputin@yahoo.ca> Subject: Re: [Idr] Re: Commentson draft-zhang-idr-bgp-entire-routes-reflect-00.txt In-Reply-To: <20050719171206.70331.qmail@web60718.mail.yahoo.com> Message-ID: <Pine.GSO.4.58.0507271411200.2495@aretana-u10.cisco.com> References: <20050719171206.70331.qmail@web60718.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Cc: raszuk@cisco.com, idr@ietf.org X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing <idr.ietf.org> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe> List-Archive: <http://www1.ietf.org/pipermail/idr> List-Post: <mailto:idr@ietf.org> List-Help: <mailto:idr-request@ietf.org?subject=help> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe> Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org On Tue, 19 Jul 2005, Tulip Rasputin wrote: Tulip: -> !> Would you be so kind to comment what proposed in your draft has not -> !> already been addressed in our ADD_PATHs proposal RR !> functionality -> wise ? -> -> I see absolutely nothing wrong in this! -> -> There isnt any rule in the IETF that forbids multiple submissions to -> achieve the same objective. Its left on the community to decide which -> proposal they are most comfortable with. If it happens to be the draft -> thats been submitted later, then so be it! -> -> IETF is an open standards body, in case you forgot that, and nothing, -> is patented here. If you dont want others to address the same issues -> that you've been trying to solve, then IETF isnt really the right place -> for you to start with! -> -> YOu should be patenting your ideas, but then, nobody else is going to -> implement them. I think Robert was only asking Zhang to compare...nothing else. In any case, I think we can all agree about the openness of the IETF, multiple solutions, community, etc.. Just to clarify, we have no IPR claims over any part of the ADD_PATH work. Also, We have posted an update to the draft and plan to talk about it next week. Thanks! Alvaro. -> !> Ref: draft-walton-bgp-add-paths-03.txt _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id NAA05515 for <idr-archive@nic.merit.edu>; Wed, 27 Jul 2005 13:14:33 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DxpQX-00032c-8U; Wed, 27 Jul 2005 13:10:41 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DxpQV-00032V-Fc for idr@megatron.ietf.org; Wed, 27 Jul 2005 13:10:39 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14646 for <idr@ietf.org>; Wed, 27 Jul 2005 13:10:36 -0400 (EDT) Received: from colo-dns-ext1.juniper.net ([207.17.137.57]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Dxpvl-00043f-2F for idr@ietf.org; Wed, 27 Jul 2005 13:43:00 -0400 Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext1.juniper.net (8.11.3/8.9.3) with ESMTP id j6RHAM965954; Wed, 27 Jul 2005 10:10:22 -0700 (PDT) (envelope-from yakov@juniper.net) Received: from juniper.net (sapphire.juniper.net [172.17.28.108]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id j6RHACG34118; Wed, 27 Jul 2005 10:10:12 -0700 (PDT) (envelope-from yakov@juniper.net) Message-Id: <200507271710.j6RHACG34118@merlot.juniper.net> To: idr@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <16228.1122484212.1@juniper.net> Date: Wed, 27 Jul 2005 10:10:12 -0700 From: Yakov Rekhter <yakov@juniper.net> X-Spam-Score: 0.0 (/) X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed Cc: skh@nexthop.com Subject: [Idr] presentations X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing <idr.ietf.org> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe> List-Archive: <http://www1.ietf.org/pipermail/idr> List-Post: <mailto:idr@ietf.org> List-Help: <mailto:idr-request@ietf.org?subject=help> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe> Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org Folks, Those who will be presenting at the IETF please send your presentations (if you did not do this already) as soon as possible to Sue and myself. Yakov. _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr Received: from CBL217-132-147-125.bb.netvision.net.il (CBL217-132-147-125.bb.netvision.net.il [217.132.147.125]) by nic.merit.edu (8.9.3/8.9.1) with SMTP id GAA12214 for <idr-archive@nic.merit.edu>; Tue, 26 Jul 2005 06:40:02 -0400 (EDT) Received: from bigfoot.com (mail-kr.bigfoot.com [211.115.216.228]) by CBL217-132-147-125.bb.netvision.net.il (Postfix) with ESMTP id F2F269AA8D for <idr-archive@nic.merit.edu>; Mon, 25 Jul 2005 15:43:06 -0500 From: "Dressage T. Controvert" <hpenner@bigfoot.com> To: Idr <idr-archive@nic.merit.edu> Subject: Borland Software and more. The best price. Date: Mon, 25 Jul 2005 15:43:06 -0500 Message-ID: <110001c59159$f31c581e$43790c42@bigfoot.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0019_534618A8.2A56CD16" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2605 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2479.0006 X-AntiVirus: checked by AntiVir MailGate (version: 2.0.1.5; AVE: 6.17.0.2; VDF: 6.17.0.5; host: CBL217-132-147-125.bb.netvision.net.il) This is a multi-part message in MIME format. ------=_NextPart_000_0019_534618A8.2A56CD16 Content-Type: text/plain Content-Transfer-Encoding: 7bit http://aiz.unearnedkh.info/?dsfifudXqOQXZ1J Borland Software and more. The best price. Examine our price-list. Windows 2000 Adv. Server - $69.95 Fireworks MX 2004 - $60 Win 2k Advanced Server - $69.95 Windows 2000 Professional - $50 MS Office 2003 Pro (1 CD Edition) - $89.95 Fireworks MX 2004 - $60 Photoshop CS with ImageReady CS - $90 Windows NT 4.0 Server - $40 Win 2k Advanced Server - $69.95 Microsoft Office 2003 Professional (1 CD Edition) - $89.95 Win XP Pro - $69.95 Microsoft FileMaker 7.0 Pro - $69.95 Quark Xpress 6 Passport Multilanguage - $60 Office XP Professional - $70 Windows 95 - $49.95 Try to click http://qtsjnzq.jansenisten.info/?CR8bET6QPbJkSWC ------=_NextPart_000_0019_534618A8.2A56CD16 Content-Type: text/html Content-Transfer-Encoding: quoted-printable <html> <body> <table align=3dcenter> <tr><td align=3dcenter> <strong align=3dcenter><a href=3d"http://garyebq=2enightcapif=2einfo/?O1k= nkzi0_nVw26i"> <font size=3d4 color=3d#1213a7> Just click to buy OEM software! </a></strong> </td></tr> <tr><td align=3dcenter><font size=3d4>Check out our prices=2e</td></tr> </table> <table align=3dcenter border=3d0> <tr><td align=3dcenter colspan=3d2>Special Offers:</td></tr> <tr><td>Bundle Special:Win XP Professional With SP2 Full Version + Office= 2003 Professional (1 CD Edition)</td><td>$99=2e95</td></tr><tr><td>Bundl= e Special:Macromedia Dreamwaver MX 2004 + Macromedia Flash MX 2004</td><t= d>$109=2e95</td></tr><tr><td>Special Offer:MS Win XP Professional + MS Of= fice XP Professional</td><td>$89=2e95</td></tr><tr><td>Bundle Special:Pho= toshop + Premiere + Illustrator </td><td>$129=2e95</td></tr> <tr><td> </td></tr> <tr><td align=3dcenter colspan=3d2>Microsoft|c| Windows </td></tr> <tr><td>Win NT 4=2e0 Server </td><td>$49=2e95</td></tr><tr><td>Win XP Pro= With SP2 Full Version</td><td>$79=2e95</td></tr><tr><td>Win Millenium </= td><td>$59=2e95</td></tr><tr><td>Win XP Pro</td><td>$69=2e95</td></tr><tr= ><td>Win 2000 Advanced Server </td><td>$69=2e95</td></tr><tr><td>Win 98 S= econd Edition </td><td>$49=2e95</td></tr><tr><td>Win 95</td><td>$49=2e95<= /td></tr><tr><td>Win 2000 Pro</td><td>$59=2e95</td></tr> <tr><td> </td></tr> <tr><td align=3dcenter colspan=3d2>Microsoft Office|R|:</td></tr> <tr><td>Office 2000 Premium Edition (2 CD Edition)</td><td>$59=2e95</td><= /tr><tr><td>Office XP Pro</td><td>$79=2e95</td></tr><tr><td>Office 97 SR2= </td><td>$49=2e95</td></tr><tr><td>Office 2003 Pro (1 CD Edition)</td><td= >$89=2e95</td></tr> <tr><td> </td></tr> <tr><td align=3dcenter colspan=3d2>Other Microsoft Software:</td></tr> <tr><td>MS Money 2004</td><td>$69=2e95</tr></td><tr><td>MS Exchange 2003 = Enterprise Server</td><td>$69=2e95</tr></td><tr><td>MS Picture It Premium= 9</td><td>$59=2e95</tr></td><tr><td>MS Project 2003 Pro</td><td>$69=2e95= </tr></td><tr><td>MS Plus! XP</td><td>$59=2e95</tr></td><tr><td>MS Works = 7</td><td>$69=2e95</tr></td><tr><td>MS Encarta Encyclopedia Delux 2004 (3= CD)</td><td>$89=2e95</tr></td><tr><td>MS Visual Studio =2eNET Architect = Edition (8CD)</td><td>$139=2e95</tr></td><tr><td>MS SQL Server 2k Enterpr= ise Edition</td><td>$69=2e95</tr></td><tr><td>MS Streets and Trips 2004 N= orth America (2 CD Edition)</td><td>$69=2e95</tr></td> <tr><td> </td></tr> <tr><td align=3dcenter colspan=3d2>Adobe Software for PC:</td></tr> <tr><td>Adobe Creative Suite Standard (3 CD) </td><td>$129=2e95</td></tr>= <tr><td>Adobe Photoshop CS with ImageReady CS </td><td>$99=2e95</td></tr>= <tr><td>Adobe Acrobat 6 Professional </td><td>$79=2e95</td></tr><tr><td>A= dobe PageMaker 7 (2 CD) </td><td>$69=2e95</td></tr><tr><td>Adobe Creative= Suite Premium (5 CD) </td><td>$149=2e95</td></tr><tr><td>Adobe Illustrat= or 10 </td><td>$69=2e95</td></tr><tr><td>Adobe Premiere 7 </td><td>$69=2e= 95</td></tr><tr><td>Adobe InDesign CS PageMaker Edition (2 CD) </td><td>$= 69=2e95</td></tr><tr><td>Adobe Photoshop 7 </td><td>$69=2e95</td></tr> <tr><td> </td></tr> <tr><td align=3dcenter colspan=3d2>Adobe Software for Mac:</td></tr> <tr><td>Adobe Premiere 6=2e5 (Apple Macintosh)</td><td>$89=2e95</td></tr>= <tr><td>Adobe InDesign CS (Apple Macintosh)</td><td>$69=2e95</td></tr><tr= ><td>Adobe Illustrator CS CE (Apple Macintosh)</td><td>$69=2e95</td></tr>= <tr><td>Adobe Actobat 6=2e0 Professional (Apple Macintosh)</td><td>$79=2e= 95</td></tr><tr><td>Adobe After Effects 6=2e0 (Apple Macintosh)</td><td>$= 69=2e95</td></tr><tr><td>Adobe LiveMotion 2=2e0 (Apple Macintosh)</td><td= >$69=2e95</td></tr><tr><td>Adobe Photoshop CS (Apple Macintosh)</td><td>$= 99=2e95</td></tr> <tr><td> </td></tr> <tr><td align=3dcenter colspan=3d2>Macromedia Software for PC:</td></tr> = <tr><td>Macromedia Dreamwaver MX 2004</td><td>$69=2e95</tr></td><tr><td>M= acromedia Flash MX 2004</td><td>$69=2e95</tr></td><tr><td>Macromedia Fire= works MX 2004</td><td>$69=2e95</tr></td><tr><td>Macromedia Freehand MX 11= </td><td>$69=2e95</tr></td> <tr><td> </td></tr> <tr><td align=3dcenter colspan=3d2>Macromedia Software for Mac:</td></tr>= <tr><td>Macromedia Flash MX 2004 (Mac)</td><td>$69=2e95</td></tr><tr><td>= Macromedia Fireworks MX 2004 (Mac)</td><td>$69=2e95</td></tr><tr><td>Macr= omedia Studio MX 2004 with Director MX 2004 (Mac)</td><td>$139=2e95</td><= /tr><tr><td>Macromedia Dreamweaver MX 2004 (Mac)</td><td>$69=2e95</td></t= r><tr><td>Macromedia Director MX 2004 (Mac)</td><td>$69=2e95</td></tr><tr= ><td>Macromedia FreeHand MX (Mac)</td><td>$69=2e95</td></tr> <tr><td> </td></tr> <tr><td align=3dcenter colspan=3d2>Corel Software:</td></tr> <tr><td>Corel Draw Graphics Suite 11</td><td>$59=2e95</td></tr><tr><td>Co= rel Photo Painter 8=2e0</td><td>$59=2e95</td></tr><tr><td>Corel Draw Grap= hics Suite 11 (Apple Macintosh)</td><td>$59=2e95</td></tr><tr><td>Corel P= hoto Painter 8=2e0 (Apple Macintosh)</td><td>$59=2e95</td></tr><tr><td>Co= rel WordPerfect Office </td><td>$69=2e95</td></tr> <tr><td> </td></tr> </table> <table align=3dcenter> <tr><td align=3dcenter> <a href=3d"http://xbgf=2eprimaryfe=2einfo/?ratwtIrFE0yFHfr"><h3><font siz= e=3d3 color=3d#212346>Check it</font></h3></a> </td></tr> </table> </body> </html> ------=_NextPart_000_0019_534618A8.2A56CD16-- Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id FAA15020 for <idr-archive@nic.merit.edu>; Mon, 25 Jul 2005 05:36:42 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DwzMU-00027d-BZ; Mon, 25 Jul 2005 05:35:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DwzMS-00027K-5Z for idr@megatron.ietf.org; Mon, 25 Jul 2005 05:35:00 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01131 for <idr@ietf.org>; Mon, 25 Jul 2005 05:34:58 -0400 (EDT) Received: from ams-iport-1.cisco.com ([144.254.224.140]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DwzrH-0002NA-Fq for idr@ietf.org; Mon, 25 Jul 2005 06:06:51 -0400 Received: from ams-core-1.cisco.com (144.254.224.150) by ams-iport-1.cisco.com with ESMTP; 25 Jul 2005 11:34:50 +0200 Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com [144.254.231.87]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j6P9YVDq018427; Mon, 25 Jul 2005 11:34:47 +0200 (MEST) Received: from xmb-ams-333.cisco.com ([144.254.231.78]) by xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.0); Mon, 25 Jul 2005 11:34:41 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Subject: RE: [Idr] Re: draft-ooms-v6ops-bgp-tunnel-05.txt Date: Mon, 25 Jul 2005 11:34:35 +0200 Message-ID: <A05118C6DF9320488C77F3D5459B17B7013B1D5E@xmb-ams-333.emea.cisco.com> Thread-Topic: [Idr] Re: draft-ooms-v6ops-bgp-tunnel-05.txt Thread-Index: AcWO6HQg96fL+6qxSUaLkTKfmmxcJQCEKtEQ From: "Francois Le Faucheur \(flefauch\)" <flefauch@cisco.com> To: "Yakov Rekhter" <yakov@juniper.net>, "Pekka Savola" <pekkas@netcore.fi> X-OriginalArrivalTime: 25 Jul 2005 09:34:41.0194 (UTC) FILETIME=[1535E8A0:01C590FC] X-Spam-Score: 0.0 (/) X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe Cc: skh@nexthop.com, idr@ietf.org, "Francois Le Faucheur \(flefauch\)" <flefauch@cisco.com> X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing <idr.ietf.org> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe> List-Archive: <http://www1.ietf.org/pipermail/idr> List-Post: <mailto:idr@ietf.org> List-Help: <mailto:idr-request@ietf.org?subject=help> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe> Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by nic.merit.edu id FAA15020 Yakov, Pekka, >> -----Original Message----- >> From: idr-bounces@ietf.org [mailto:idr-bounces@ietf.org] On >> Behalf Of Yakov Rekhter >> Sent: vendredi 22 juillet 2005 20:05 >> To: Pekka Savola >> Cc: skh@nexthop.com; Yakov Rekhter; idr@ietf.org >> Subject: [Idr] Re: draft-ooms-v6ops-bgp-tunnel-05.txt >> >> Pekka, >> >> > Hi, >> > >> > Just curious as it isn't on the agenda: what's the status of >> > draft-ooms-v6ops-bgp-tunnel-05.txt? >> > >> > The last I heard was a call for implementation report(s) [and one >> > report] on February 9. Although multiple implementations do exist (including at least two commercially available), at this stage, there is still a single response to the "implementation survey". >> >> We are awaiting the implementation report from Francois. I am under the assumption that an implementation report should be based on details about more than one implementation. When (at least) one other implementor provides an additional response to the "implementation survey", I will draft/submit an implementation report. If no other response is provided to the "implementation survey" in the short future, I would suggest we consider publishing the v6ops-bgp-tunnel document as Informational (instead of Standards), so it can actually get published without the procedure hurdle of an implementation report. I welcome further guidance on how to progress this document. Francois >> >> Yakov. >> >> > On Fri, 22 Jul 2005, Yakov Rekhter wrote: >> > > Here is the final agenda for the IDR WG meeting. >> > > >> > > 1. IDR Documents status update 5 mins >> > >> > -- >> > Pekka Savola "You each name yourselves >> king, yet the >> > Netcore Oy kingdom bleeds." >> > Systems. Networks. Security. -- George R.R. Martin: A >> Clash of Kings >> >> _______________________________________________ >> Idr mailing list >> Idr@ietf.org >> https://www1.ietf.org/mailman/listinfo/idr >> _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id OAA20299 for <idr-archive@nic.merit.edu>; Fri, 22 Jul 2005 14:07:08 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dw1to-0001Rv-FN; Fri, 22 Jul 2005 14:05:28 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dw1tn-0001Rq-EJ for idr@megatron.ietf.org; Fri, 22 Jul 2005 14:05:27 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06629 for <idr@ietf.org>; Fri, 22 Jul 2005 14:05:25 -0400 (EDT) Received: from colo-dns-ext1.juniper.net ([207.17.137.57]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Dw2O4-0007sW-Ay for idr@ietf.org; Fri, 22 Jul 2005 14:36:45 -0400 Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext1.juniper.net (8.11.3/8.9.3) with ESMTP id j6MI5D907848; Fri, 22 Jul 2005 11:05:14 -0700 (PDT) (envelope-from yakov@juniper.net) Received: from juniper.net (sapphire.juniper.net [172.17.28.108]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id j6MI52G46465; Fri, 22 Jul 2005 11:05:02 -0700 (PDT) (envelope-from yakov@juniper.net) Message-Id: <200507221805.j6MI52G46465@merlot.juniper.net> To: Pekka Savola <pekkas@netcore.fi> In-Reply-To: Your message of "Fri, 22 Jul 2005 20:49:22 +0300." <Pine.LNX.4.61.0507222048030.13132@netcore.fi> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <92026.1122055502.1@juniper.net> Date: Fri, 22 Jul 2005 11:05:02 -0700 From: Yakov Rekhter <yakov@juniper.net> X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Cc: skh@nexthop.com, Yakov Rekhter <yakov@juniper.net>, idr@ietf.org Subject: [Idr] Re: draft-ooms-v6ops-bgp-tunnel-05.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing <idr.ietf.org> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe> List-Archive: <http://www1.ietf.org/pipermail/idr> List-Post: <mailto:idr@ietf.org> List-Help: <mailto:idr-request@ietf.org?subject=help> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe> Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org Pekka, > Hi, > > Just curious as it isn't on the agenda: what's the status of > draft-ooms-v6ops-bgp-tunnel-05.txt? > > The last I heard was a call for implementation report(s) [and one > report] on February 9. We are awaiting the implementation report from Francois. Yakov. > On Fri, 22 Jul 2005, Yakov Rekhter wrote: > > Here is the final agenda for the IDR WG meeting. > > > > 1. IDR Documents status update 5 mins > > -- > Pekka Savola "You each name yourselves king, yet the > Netcore Oy kingdom bleeds." > Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id NAA19089 for <idr-archive@nic.merit.edu>; Fri, 22 Jul 2005 13:51:46 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dw1eZ-00044A-8P; Fri, 22 Jul 2005 13:49:43 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dw1eX-00042a-A5 for idr@megatron.ietf.org; Fri, 22 Jul 2005 13:49:41 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05826 for <idr@ietf.org>; Fri, 22 Jul 2005 13:49:39 -0400 (EDT) Received: from netcore.fi ([193.94.160.1]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Dw28m-0007Ld-RI for idr@ietf.org; Fri, 22 Jul 2005 14:20:59 -0400 Received: from localhost (pekkas@localhost) by netcore.fi (8.11.6/8.11.6) with ESMTP id j6MHnMe13389; Fri, 22 Jul 2005 20:49:22 +0300 Date: Fri, 22 Jul 2005 20:49:22 +0300 (EEST) From: Pekka Savola <pekkas@netcore.fi> To: Yakov Rekhter <yakov@juniper.net> In-Reply-To: <200507221551.j6MFpQG18862@merlot.juniper.net> Message-ID: <Pine.LNX.4.61.0507222048030.13132@netcore.fi> References: <200507221551.j6MFpQG18862@merlot.juniper.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Cc: skh@nexthop.com, idr@ietf.org Subject: [Idr] draft-ooms-v6ops-bgp-tunnel-05.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing <idr.ietf.org> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe> List-Archive: <http://www1.ietf.org/pipermail/idr> List-Post: <mailto:idr@ietf.org> List-Help: <mailto:idr-request@ietf.org?subject=help> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe> Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org Hi, Just curious as it isn't on the agenda: what's the status of draft-ooms-v6ops-bgp-tunnel-05.txt? The last I heard was a call for implementation report(s) [and one report] on February 9. On Fri, 22 Jul 2005, Yakov Rekhter wrote: > Here is the final agenda for the IDR WG meeting. > > 1. IDR Documents status update 5 mins -- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id LAA08826 for <idr-archive@nic.merit.edu>; Fri, 22 Jul 2005 11:53:14 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DvzoK-0003qE-Ed; Fri, 22 Jul 2005 11:51:40 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DvzoI-0003pH-UK for idr@megatron.ietf.org; Fri, 22 Jul 2005 11:51:39 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27405 for <idr@ietf.org>; Fri, 22 Jul 2005 11:51:36 -0400 (EDT) Received: from colo-dns-ext2.juniper.net ([207.17.137.64]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Dw0IY-0002iz-HI for idr@ietf.org; Fri, 22 Jul 2005 12:22:55 -0400 Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext2.juniper.net (8.12.3/8.12.3) with ESMTP id j6MFpQBm098790; Fri, 22 Jul 2005 08:51:26 -0700 (PDT) (envelope-from yakov@juniper.net) Received: from juniper.net (sapphire.juniper.net [172.17.28.108]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id j6MFpQG18862; Fri, 22 Jul 2005 08:51:26 -0700 (PDT) (envelope-from yakov@juniper.net) Message-Id: <200507221551.j6MFpQG18862@merlot.juniper.net> To: idr@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <72809.1122047486.1@juniper.net> Date: Fri, 22 Jul 2005 08:51:26 -0700 From: Yakov Rekhter <yakov@juniper.net> X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Cc: skh@nexthop.com Subject: [Idr] final agenda X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing <idr.ietf.org> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe> List-Archive: <http://www1.ietf.org/pipermail/idr> List-Post: <mailto:idr@ietf.org> List-Help: <mailto:idr-request@ietf.org?subject=help> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe> Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org Folks, Here is the final agenda for the IDR WG meeting. 1. IDR Documents status update 5 mins 2. draft-li-as-hopcount-01.txt 30 mins 3. draft-zhang-idr-bgp-entire-routes-reflect-01.txt 15 mins 4. draft-walton-bgp-add-paths-03.txt draft-walton-bgp-route-oscillation-stop-01.txt 20 mins 5. draft-dubois-bgp-pm-reqs-01.txt 15 mins 6. draft-hares-bose-dynamic_as-01.txt 10 mins 7. draft-ietf-idr-bgp-multisession-01.txt 10 mins 8. draft-kapoor-nalawade-idr-bgp-ssa-02.txt draft-nalawade-kapoor-tunnel-safi-03.txt. 15 mins Sue & Yakov. _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id NAA15950 for <idr-archive@nic.merit.edu>; Tue, 19 Jul 2005 13:14:31 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Duvdl-0004EQ-VW; Tue, 19 Jul 2005 13:12:22 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Duvdk-0004Dt-Ek for idr@megatron.ietf.org; Tue, 19 Jul 2005 13:12:20 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15135 for <idr@ietf.org>; Tue, 19 Jul 2005 13:12:17 -0400 (EDT) Received: from web60718.mail.yahoo.com ([209.73.178.206]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Duw7K-00040V-VO for idr@ietf.org; Tue, 19 Jul 2005 13:43:00 -0400 Received: (qmail 70333 invoked by uid 60001); 19 Jul 2005 17:12:06 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.ca; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=xHO9APlMOuZ6JK+daztchxnKsa31gmxJdklvR7y0ZcUaXHXizBpQTTSBYmE1+Ggyg2YbxxKu262CNAEDLYkTPrpYOeLyxH5Q0fqNyff79kML22MjoABUSstLRDF6hk/YceuYhZS+NjWowt/dRftVihrlzi0Uhjc1ain5b4cvT8k= ; Message-ID: <20050719171206.70331.qmail@web60718.mail.yahoo.com> Received: from [66.17.149.13] by web60718.mail.yahoo.com via HTTP; Tue, 19 Jul 2005 13:12:06 EDT Date: Tue, 19 Jul 2005 13:12:06 -0400 (EDT) From: Tulip Rasputin <tulip_rasputin@yahoo.ca> Subject: Re: [Idr] Re: Commentson draft-zhang-idr-bgp-entire-routes-reflect-00.txt To: raszuk@cisco.com, idr@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Score: 2.9 (++) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 Content-Transfer-Encoding: 8bit Cc: X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing <idr.ietf.org> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe> List-Archive: <http://www1.ietf.org/pipermail/idr> List-Post: <mailto:idr@ietf.org> List-Help: <mailto:idr-request@ietf.org?subject=help> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe> Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org Robert, !> !> Would you be so kind to comment what proposed in your draft has not !> already been addressed in our ADD_PATHs proposal RR !> functionality wise ? I see absolutely nothing wrong in this! There isnt any rule in the IETF that forbids multiple submissions to achieve the same objective. Its left on the community to decide which proposal they are most comfortable with. If it happens to be the draft thats been submitted later, then so be it! IETF is an open standards body, in case you forgot that, and nothing, is patented here. If you dont want others to address the same issues that you've been trying to solve, then IETF isnt really the right place for you to start with! YOu should be patenting your ideas, but then, nobody else is going to implement them. Hard Luck! Tulip !> !> Ref: draft-walton-bgp-add-paths-03.txt !> !> Thx, !> R. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id IAA21067 for <idr-archive@nic.merit.edu>; Tue, 19 Jul 2005 08:31:02 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DurDJ-0007Kw-RS; Tue, 19 Jul 2005 08:28:45 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DurDF-0007Ko-TG for idr@megatron.ietf.org; Tue, 19 Jul 2005 08:28:44 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08758 for <idr@ietf.org>; Tue, 19 Jul 2005 08:28:40 -0400 (EDT) Received: from szxga02-in.huawei.com ([61.144.161.54] helo=huawei.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Durgr-0004eJ-IN for idr@ietf.org; Tue, 19 Jul 2005 08:59:19 -0400 Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IJV00H9CK9Z4M@szxga02-in.huawei.com> for idr@ietf.org; Tue, 19 Jul 2005 20:34:47 +0800 (CST) Received: from szxml01-in ([172.24.1.3]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IJV003ZDK9Y1U@szxga02-in.huawei.com> for idr@ietf.org; Tue, 19 Jul 2005 20:34:47 +0800 (CST) Received: from z18605 ([10.110.100.105]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0IJV00DSJKEZGY@szxml01-in.huawei.com>; Tue, 19 Jul 2005 20:37:47 +0800 (CST) Date: Tue, 19 Jul 2005 20:04:55 +0800 From: Zhang Renhai <zhangrenhai@huawei.com> To: Manav Bhatia <manav@riverstonenet.com> Message-id: <003701c58c5a$13fb2aa0$69646e0a@huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Mailer: Microsoft Outlook Express 5.50.4807.1700 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <GONDORvnbEG10Gai4om00000102@gondor.rs.riverstonenet.com> X-Spam-Score: 0.0 (/) X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3 Content-Transfer-Encoding: 7BIT Cc: idr@ietf.org Subject: [Idr] Re: Comments on draft-zhang-idr-bgp-entire-routes-reflect-00.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing <idr.ietf.org> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe> List-Archive: <http://www1.ietf.org/pipermail/idr> List-Post: <mailto:idr@ietf.org> List-Help: <mailto:idr-request@ietf.org?subject=help> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe> Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org Hi, Manav I can't find the draft you mentioned below, are you sure the name is correct? Thanks Zhang ----- Original Message ----- From: "Manav Bhatia" <manav@riverstonenet.com> To: <zhangrenhai@huawei.com> Cc: <idr@ietf.org> Sent: Tuesday, July 19, 2005 12:13 PM Subject: Comments on draft-zhang-idr-bgp-entire-routes-reflect-00.txt > > Hi Zhang, > > There are some things that are not clear to me as I went through your draft. > > [1] The Entire RR capability that you talk of enables a client to inform the > RR that it can "handle withdrawn routes segment that contains a NEXT_HOP". > But how does this help? Say the RR has multiple ways to reach a destination. > If it tries to announce this reachability information multiple times, then > the subsequent UPDATEs will be considered as implicit withdrawals for the > previous announcements. Thus, you need a way to tell your remote BGP peer > that the UPDATE that is being sent now is not an implicit withdrawal, but a > regular UPDATE that it needs to append and not replace. > > I don't see this discussed anywhere in the document. > > [2] If you ever want BGP to load balance or advertise multiple paths then > you need to consider the AS_PATHs. Would the RR in your case advertise > multiple paths only if *all* the path attributes are same or would it also > do this given different, but equivalent, path attributes? An example of the > latter case would be two paths with AS_PATHs {X Y Z} and {X A Z} > respectively. It's the latter case that's more realistic and hence more > interesting. > > We presented a similar idea (draft-bhatia-ecmp-routes-in-bgp-01.txt) in the > IDR WG that does this and takes care of all the scenarios that I just > mentioned. You can look at the slides at > http://www1.ietf.org/proceedings_new/04nov/slides/idr-1/sld1.htm > > We are working on updating our original document and should be posting it > soon. > > Thanks, > Manav > > -- > Manav Bhatia > Member of Technical Staff > Riverstone Networks, Inc. > http://www.riverstonenet.com > _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id IAA20207 for <idr-archive@nic.merit.edu>; Tue, 19 Jul 2005 08:18:35 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dur2I-0004Dk-2f; Tue, 19 Jul 2005 08:17:22 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dur2G-0004CF-CC for idr@megatron.ietf.org; Tue, 19 Jul 2005 08:17:20 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07980 for <idr@ietf.org>; Tue, 19 Jul 2005 08:17:19 -0400 (EDT) Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DurVs-0004Bm-Ct for idr@ietf.org; Tue, 19 Jul 2005 08:47:57 -0400 Received: from sj-core-5.cisco.com (171.71.177.238) by sj-iport-4.cisco.com with ESMTP; 19 Jul 2005 05:17:11 -0700 Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j6JCGeVr004355; Tue, 19 Jul 2005 05:17:07 -0700 (PDT) Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 19 Jul 2005 05:17:07 -0700 Received: from [10.21.120.147] ([10.21.120.147]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 19 Jul 2005 05:17:02 -0700 Message-ID: <42DCEF34.9020406@cisco.com> Date: Tue, 19 Jul 2005 05:16:52 -0700 From: Robert Raszuk <raszuk@cisco.com> Organization: Signature: http://www.employees.org/~raszuk/sig/ User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Zhang Renhai <zhangrenhai@huawei.com> Subject: Re: [Idr] Re: Comments on draft-zhang-idr-bgp-entire-routes-reflect-00.txt References: <GONDORvnbEG10Gai4om00000102@gondor.rs.riverstonenet.com> <001101c58c35$4ff5eec0$69646e0a@huawei.com> In-Reply-To: <001101c58c35$4ff5eec0$69646e0a@huawei.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 19 Jul 2005 12:17:03.0304 (UTC) FILETIME=[C57B6C80:01C58C5B] X-Spam-Score: 0.0 (/) X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014 Content-Transfer-Encoding: 7bit Cc: idr@ietf.org X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: raszuk@cisco.com List-Id: Inter-Domain Routing <idr.ietf.org> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe> List-Archive: <http://www1.ietf.org/pipermail/idr> List-Post: <mailto:idr@ietf.org> List-Help: <mailto:idr-request@ietf.org?subject=help> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe> Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org Zhang, Would you be so kind to comment what proposed in your draft has not already been addressed in our ADD_PATHs proposal RR functionality wise ? Ref: draft-walton-bgp-add-paths-03.txt Thx, R. _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id FAA09665 for <idr-archive@nic.merit.edu>; Tue, 19 Jul 2005 05:16:53 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DuoDI-00031f-VA; Tue, 19 Jul 2005 05:16:33 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DuoDH-00031Y-DA for idr@megatron.ietf.org; Tue, 19 Jul 2005 05:16:31 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23391 for <idr@ietf.org>; Tue, 19 Jul 2005 05:16:29 -0400 (EDT) Received: from szxga01-in.huawei.com ([61.144.161.53] helo=huawei.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Duogf-0004L8-P3 for idr@ietf.org; Tue, 19 Jul 2005 05:47:07 -0400 Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IJV00LSKAX6I5@szxga01-in.huawei.com> for idr@ietf.org; Tue, 19 Jul 2005 17:12:42 +0800 (CST) Received: from szxml02-in ([172.24.1.6]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IJV00M8QAX55L@szxga01-in.huawei.com> for idr@ietf.org; Tue, 19 Jul 2005 17:12:42 +0800 (CST) Received: from z18605 ([10.110.100.105]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0IJV00A0AAZ8CZ@szxml02-in.huawei.com>; Tue, 19 Jul 2005 17:13:56 +0800 (CST) Date: Tue, 19 Jul 2005 16:44:11 +0800 From: Zhang Renhai <zhangrenhai@huawei.com> Subject: Re: complementarity[Idr] Re: Comments ondraft-zhang-idr-bgp-entire-routes-reflect-00.txt To: Manav Bhatia <manav@riverstonenet.com> Message-id: <002301c58c3e$08edf280$69646e0a@huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Mailer: Microsoft Outlook Express 5.50.4807.1700 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <GONDORdKO8FNpyLAPDV0000010d@gondor.rs.riverstonenet.com> X-Spam-Score: 0.0 (/) X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976 Content-Transfer-Encoding: 7BIT Cc: idr@ietf.org X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing <idr.ietf.org> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe> List-Archive: <http://www1.ietf.org/pipermail/idr> List-Post: <mailto:idr@ietf.org> List-Help: <mailto:idr-request@ietf.org?subject=help> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe> Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org complementarity: ----- Original Message ----- From: "Manav Bhatia" <manav@riverstonenet.com> To: "'Zhang Renhai'" <zhangrenhai@huawei.com> Cc: <idr@ietf.org> Sent: Tuesday, July 19, 2005 4:25 PM Subject: RE: [Idr] Re: Comments ondraft-zhang-idr-bgp-entire-routes-reflect-00.txt > > Hi Zhang, > > !> The AS_PATH attribute is not related to the capability, in > !> fact, the Next Hop > !> attribute is the key factor, the client can make the load > !> balancing only among the > !> different next hop, multiple paths with the same next hop > !> have no meaning to > > I am talking about multiple paths with different NEXT_HOPs. > > For example, two routes with the following attributes: > > AS_PATH {X, Y, Z} NEXT_HOP N1 > and > AS_PATH {A, B, Z} NEXT_HOP N2 > > You need a way to advertise this information. [complementarity] Using the different UPDATE packets. > > !> loading balancing and only one route is reflected to the > !> client, otherwise, all routes > !> will be advertised to the client, wrt which routes are used > !> to performing load balancing, > !> it's the local dicision of the client. > > If a BGP peer is receiving the above two paths and is splitting the load or > is doing multipath using N1 and N2, then it MUST inform its downstream peers > about the AS_PATHs that will be used when forwarding the data. You have to > do that to avoid AS Path loops. > > Manav > > !> > !> > > !> > We presented a similar idea > !> (draft-bhatia-ecmp-routes-in-bgp-01.txt) in the > !> > IDR WG that does this and takes care of all the scenarios > !> that I just > !> > mentioned. You can look at the slides at > !> > http://www1.ietf.org/proceedings_new/04nov/slides/idr-1/sld1.htm > !> > > !> I will study your draft, thanks. > !> > !> Regards, > !> Zhang > !> > !> > We are working on updating our original document and > !> should be posting it > !> > soon. > !> > > !> > Thanks, > !> > Manav > !> > > !> > -- > !> > Manav Bhatia > !> > Member of Technical Staff > !> > Riverstone Networks, Inc. > !> > http://www.riverstonenet.com > !> > > !> > !> > !> > !> _______________________________________________ > !> Idr mailing list > !> Idr@ietf.org > !> https://www1.ietf.org/mailman/listinfo/idr > _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id FAA08956 for <idr-archive@nic.merit.edu>; Tue, 19 Jul 2005 05:04:53 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Duo0V-0006q0-Jv; Tue, 19 Jul 2005 05:03:19 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Duo0T-0006ps-MO for idr@megatron.ietf.org; Tue, 19 Jul 2005 05:03:18 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22120 for <idr@ietf.org>; Tue, 19 Jul 2005 05:03:15 -0400 (EDT) Received: from szxga02-in.huawei.com ([61.144.161.54] helo=huawei.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DuoTz-0003ed-SO for idr@ietf.org; Tue, 19 Jul 2005 05:33:53 -0400 Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IJV00FD2ARFY3@szxga02-in.huawei.com> for idr@ietf.org; Tue, 19 Jul 2005 17:09:16 +0800 (CST) Received: from szxml01-in ([172.24.1.3]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IJV00J48ARF5K@szxga02-in.huawei.com> for idr@ietf.org; Tue, 19 Jul 2005 17:09:15 +0800 (CST) Received: from z18605 ([10.110.100.105]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0IJV00BQHAWFLJ@szxml01-in.huawei.com>; Tue, 19 Jul 2005 17:12:16 +0800 (CST) Date: Tue, 19 Jul 2005 16:39:23 +0800 From: Zhang Renhai <zhangrenhai@huawei.com> Subject: Re: [Idr] Re: Comments ondraft-zhang-idr-bgp-entire-routes-reflect-00.txt To: Manav Bhatia <manav@riverstonenet.com> Message-id: <001201c58c3d$5dd71e80$69646e0a@huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Mailer: Microsoft Outlook Express 5.50.4807.1700 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <GONDORdKO8FNpyLAPDV0000010d@gondor.rs.riverstonenet.com> X-Spam-Score: 0.0 (/) X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43 Content-Transfer-Encoding: 7BIT Cc: idr@ietf.org X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing <idr.ietf.org> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe> List-Archive: <http://www1.ietf.org/pipermail/idr> List-Post: <mailto:idr@ietf.org> List-Help: <mailto:idr-request@ietf.org?subject=help> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe> Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org Hi, Manav ----- Original Message ----- From: "Manav Bhatia" <manav@riverstonenet.com> To: "'Zhang Renhai'" <zhangrenhai@huawei.com> Cc: <idr@ietf.org> Sent: Tuesday, July 19, 2005 4:25 PM Subject: RE: [Idr] Re: Comments ondraft-zhang-idr-bgp-entire-routes-reflect-00.txt > > Hi Zhang, > > !> The AS_PATH attribute is not related to the capability, in > !> fact, the Next Hop > !> attribute is the key factor, the client can make the load > !> balancing only among the > !> different next hop, multiple paths with the same next hop > !> have no meaning to > > I am talking about multiple paths with different NEXT_HOPs. > > For example, two routes with the following attributes: > > AS_PATH {X, Y, Z} NEXT_HOP N1 > and > AS_PATH {A, B, Z} NEXT_HOP N2 > > You need a way to advertise this information. According the rule I mentioned in the last mail, the RR will reflect the two routes, the key change on the RR about this capability is that the RR doesn't make the routes selection between the routes with different next hop.So I think there is no contradiction with your point on this aspect. > > !> loading balancing and only one route is reflected to the > !> client, otherwise, all routes > !> will be advertised to the client, wrt which routes are used > !> to performing load balancing, > !> it's the local dicision of the client. > > If a BGP peer is receiving the above two paths and is splitting the load or > is doing multipath using N1 and N2, then it MUST inform its downstream peers > about the AS_PATHs that will be used when forwarding the data. You have to > do that to avoid AS Path loops. Sure, I guess your concern is that when forwording the routes performing the load balancing as one route, the AS_PATH attribute must be changed consequently, e.g., changing some AS from sequence to set, correct? Indeed, the AS_PATH should be considered carefully. If this is nacessary in the draft, I will cover it in the future version. Thanks, Zhang > > Manav > > !> > !> > > !> > We presented a similar idea > !> (draft-bhatia-ecmp-routes-in-bgp-01.txt) in the > !> > IDR WG that does this and takes care of all the scenarios > !> that I just > !> > mentioned. You can look at the slides at > !> > http://www1.ietf.org/proceedings_new/04nov/slides/idr-1/sld1.htm > !> > > !> I will study your draft, thanks. > !> > !> Regards, > !> Zhang > !> > !> > We are working on updating our original document and > !> should be posting it > !> > soon. > !> > > !> > Thanks, > !> > Manav > !> > > !> > -- > !> > Manav Bhatia > !> > Member of Technical Staff > !> > Riverstone Networks, Inc. > !> > http://www.riverstonenet.com > !> > > !> > !> > !> > !> _______________________________________________ > !> Idr mailing list > !> Idr@ietf.org > !> https://www1.ietf.org/mailman/listinfo/idr > _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id EAA07010 for <idr-archive@nic.merit.edu>; Tue, 19 Jul 2005 04:28:03 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DunQW-0004uR-1C; Tue, 19 Jul 2005 04:26:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DunQU-0004u3-Eh for idr@megatron.ietf.org; Tue, 19 Jul 2005 04:26:06 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19771 for <idr@ietf.org>; Tue, 19 Jul 2005 04:26:04 -0400 (EDT) Received: from mail.riverstonenet.com ([63.113.148.10] helo=riverstonenet.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Dunu3-0002BY-Vm for idr@ietf.org; Tue, 19 Jul 2005 04:56:41 -0400 Received: from gondor.rs.riverstonenet.com by riverstonenet.com (8.9.3+Sun/SMI-SVR4-Yago) id BAA21890; Tue, 19 Jul 2005 01:25:50 -0700 (PDT) Received: from pfloyd ([172.24.2.31]) by gondor.rs.riverstonenet.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 19 Jul 2005 13:55:48 +0530 From: "Manav Bhatia" <manav@riverstonenet.com> To: "'Zhang Renhai'" <zhangrenhai@huawei.com> Subject: RE: [Idr] Re: Comments ondraft-zhang-idr-bgp-entire-routes-reflect-00.txt Date: Tue, 19 Jul 2005 13:55:48 +0530 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AcWMOgf93ye/IE4fQs+GbUzy1dMzWAAACYrw X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 In-Reply-To: <001101c58c35$4ff5eec0$69646e0a@huawei.com> Message-ID: <GONDORdKO8FNpyLAPDV0000010d@gondor.rs.riverstonenet.com> X-OriginalArrivalTime: 19 Jul 2005 08:25:48.0570 (UTC) FILETIME=[777F07A0:01C58C3B] X-Spam-Score: 0.0 (/) X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135 Content-Transfer-Encoding: 7bit Cc: idr@ietf.org X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing <idr.ietf.org> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe> List-Archive: <http://www1.ietf.org/pipermail/idr> List-Post: <mailto:idr@ietf.org> List-Help: <mailto:idr-request@ietf.org?subject=help> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe> Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org Hi Zhang, !> The AS_PATH attribute is not related to the capability, in !> fact, the Next Hop !> attribute is the key factor, the client can make the load !> balancing only among the !> different next hop, multiple paths with the same next hop !> have no meaning to I am talking about multiple paths with different NEXT_HOPs. For example, two routes with the following attributes: AS_PATH {X, Y, Z} NEXT_HOP N1 and AS_PATH {A, B, Z} NEXT_HOP N2 You need a way to advertise this information. !> loading balancing and only one route is reflected to the !> client, otherwise, all routes !> will be advertised to the client, wrt which routes are used !> to performing load balancing, !> it's the local dicision of the client. If a BGP peer is receiving the above two paths and is splitting the load or is doing multipath using N1 and N2, then it MUST inform its downstream peers about the AS_PATHs that will be used when forwarding the data. You have to do that to avoid AS Path loops. Manav !> !> > !> > We presented a similar idea !> (draft-bhatia-ecmp-routes-in-bgp-01.txt) in the !> > IDR WG that does this and takes care of all the scenarios !> that I just !> > mentioned. You can look at the slides at !> > http://www1.ietf.org/proceedings_new/04nov/slides/idr-1/sld1.htm !> > !> I will study your draft, thanks. !> !> Regards, !> Zhang !> !> > We are working on updating our original document and !> should be posting it !> > soon. !> > !> > Thanks, !> > Manav !> > !> > -- !> > Manav Bhatia !> > Member of Technical Staff !> > Riverstone Networks, Inc. !> > http://www.riverstonenet.com !> > !> !> !> !> _______________________________________________ !> Idr mailing list !> Idr@ietf.org !> https://www1.ietf.org/mailman/listinfo/idr _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id EAA06372 for <idr-archive@nic.merit.edu>; Tue, 19 Jul 2005 04:16:00 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DunFn-0000tQ-9s; Tue, 19 Jul 2005 04:15:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DunFj-0000sk-E5 for idr@megatron.ietf.org; Tue, 19 Jul 2005 04:15:00 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19120 for <idr@ietf.org>; Tue, 19 Jul 2005 04:14:57 -0400 (EDT) Received: from szxga01-in.huawei.com ([61.144.161.53] helo=huawei.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DunjE-0001kg-QJ for idr@ietf.org; Tue, 19 Jul 2005 04:45:34 -0400 Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IJV00B9J8138B@szxga01-in.huawei.com> for idr@ietf.org; Tue, 19 Jul 2005 16:10:15 +0800 (CST) Received: from szxml02-in ([172.24.1.6]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IJV009S3812HR@szxga01-in.huawei.com> for idr@ietf.org; Tue, 19 Jul 2005 16:10:15 +0800 (CST) Received: from z18605 ([10.110.100.105]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0IJV0055B835HA@szxml02-in.huawei.com>; Tue, 19 Jul 2005 16:11:29 +0800 (CST) Date: Tue, 19 Jul 2005 15:41:44 +0800 From: Zhang Renhai <zhangrenhai@huawei.com> To: Manav Bhatia <manav@riverstonenet.com> Message-id: <001101c58c35$4ff5eec0$69646e0a@huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Mailer: Microsoft Outlook Express 5.50.4807.1700 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <GONDORvnbEG10Gai4om00000102@gondor.rs.riverstonenet.com> X-Spam-Score: 0.0 (/) X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac Content-Transfer-Encoding: 7BIT Cc: idr@ietf.org Subject: [Idr] Re: Comments on draft-zhang-idr-bgp-entire-routes-reflect-00.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing <idr.ietf.org> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe> List-Archive: <http://www1.ietf.org/pipermail/idr> List-Post: <mailto:idr@ietf.org> List-Help: <mailto:idr-request@ietf.org?subject=help> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe> Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org Hi, Manav Please see inline. ----- Original Message ----- From: "Manav Bhatia" <manav@riverstonenet.com> To: <zhangrenhai@huawei.com> Cc: <idr@ietf.org> Sent: Tuesday, July 19, 2005 12:13 PM Subject: Comments on draft-zhang-idr-bgp-entire-routes-reflect-00.txt > > Hi Zhang, > > There are some things that are not clear to me as I went through your draft. > > [1] The Entire RR capability that you talk of enables a client to inform the > RR that it can "handle withdrawn routes segment that contains a NEXT_HOP". > But how does this help? Say the RR has multiple ways to reach a destination. > If it tries to announce this reachability information multiple times, then > the subsequent UPDATEs will be considered as implicit withdrawals for the > previous announcements. Thus, you need a way to tell your remote BGP peer > that the UPDATE that is being sent now is not an implicit withdrawal, but a > regular UPDATE that it needs to append and not replace. Yes, here a method is need to make the subsequent UPDATEs not an implicit withdrawl, prevously I thought of a method, that is , for the client with which RR has negotiated the capability, there will be no the implicit withdrawals any more, instead, when updating the routes , RR should first advertises the withdraw explicitly, I don't think it a good method lately. So, as you say, a indication can be included in the subsequent UPDATEs when reflecting more than one routes to a destination, and this should be coverd in the future version, but the mechanism is still not clear now, anyone is encouraged to contribute this. > > I don't see this discussed anywhere in the document. > > [2] If you ever want BGP to load balance or advertise multiple paths then > you need to consider the AS_PATHs. Would the RR in your case advertise > multiple paths only if *all* the path attributes are same or would it also > do this given different, but equivalent, path attributes? An example of the > latter case would be two paths with AS_PATHs {X Y Z} and {X A Z} > respectively. It's the latter case that's more realistic and hence more > interesting. The AS_PATH attribute is not related to the capability, in fact, the Next Hop attribute is the key factor, the client can make the load balancing only among the different next hop, multiple paths with the same next hop have no meaning to loading balancing and only one route is reflected to the client, otherwise, all routes will be advertised to the client, wrt which routes are used to performing load balancing, it's the local dicision of the client. > > We presented a similar idea (draft-bhatia-ecmp-routes-in-bgp-01.txt) in the > IDR WG that does this and takes care of all the scenarios that I just > mentioned. You can look at the slides at > http://www1.ietf.org/proceedings_new/04nov/slides/idr-1/sld1.htm > I will study your draft, thanks. Regards, Zhang > We are working on updating our original document and should be posting it > soon. > > Thanks, > Manav > > -- > Manav Bhatia > Member of Technical Staff > Riverstone Networks, Inc. > http://www.riverstonenet.com > _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id AAA21061 for <idr-archive@nic.merit.edu>; Tue, 19 Jul 2005 00:13:48 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DujTx-0006K4-8k; Tue, 19 Jul 2005 00:13:25 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DujTv-0006Jz-Vu for idr@megatron.ietf.org; Tue, 19 Jul 2005 00:13:24 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA15308 for <idr@ietf.org>; Tue, 19 Jul 2005 00:13:21 -0400 (EDT) Received: from mail.riverstonenet.com ([63.113.148.10] helo=riverstonenet.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DujxT-000221-Cp for idr@ietf.org; Tue, 19 Jul 2005 00:43:56 -0400 Received: from gondor.rs.riverstonenet.com by riverstonenet.com (8.9.3+Sun/SMI-SVR4-Yago) id VAA27024; Mon, 18 Jul 2005 21:13:01 -0700 (PDT) Received: from pfloyd ([172.24.2.31]) by gondor.rs.riverstonenet.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 19 Jul 2005 09:43:00 +0530 From: "Manav Bhatia" <manav@riverstonenet.com> To: <zhangrenhai@huawei.com> Date: Tue, 19 Jul 2005 09:43:00 +0530 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AcWMGCZgxzQ0SFSMRvGBorwwiZgYuQ== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Message-ID: <GONDORvnbEG10Gai4om00000102@gondor.rs.riverstonenet.com> X-OriginalArrivalTime: 19 Jul 2005 04:13:00.0132 (UTC) FILETIME=[26671240:01C58C18] X-Spam-Score: 0.0 (/) X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb Content-Transfer-Encoding: 7bit Cc: idr@ietf.org Subject: [Idr] Comments on draft-zhang-idr-bgp-entire-routes-reflect-00.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing <idr.ietf.org> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe> List-Archive: <http://www1.ietf.org/pipermail/idr> List-Post: <mailto:idr@ietf.org> List-Help: <mailto:idr-request@ietf.org?subject=help> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe> Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org Hi Zhang, There are some things that are not clear to me as I went through your draft. [1] The Entire RR capability that you talk of enables a client to inform the RR that it can "handle withdrawn routes segment that contains a NEXT_HOP". But how does this help? Say the RR has multiple ways to reach a destination. If it tries to announce this reachability information multiple times, then the subsequent UPDATEs will be considered as implicit withdrawals for the previous announcements. Thus, you need a way to tell your remote BGP peer that the UPDATE that is being sent now is not an implicit withdrawal, but a regular UPDATE that it needs to append and not replace. I don't see this discussed anywhere in the document. [2] If you ever want BGP to load balance or advertise multiple paths then you need to consider the AS_PATHs. Would the RR in your case advertise multiple paths only if *all* the path attributes are same or would it also do this given different, but equivalent, path attributes? An example of the latter case would be two paths with AS_PATHs {X Y Z} and {X A Z} respectively. It's the latter case that's more realistic and hence more interesting. We presented a similar idea (draft-bhatia-ecmp-routes-in-bgp-01.txt) in the IDR WG that does this and takes care of all the scenarios that I just mentioned. You can look at the slides at http://www1.ietf.org/proceedings_new/04nov/slides/idr-1/sld1.htm We are working on updating our original document and should be posting it soon. Thanks, Manav -- Manav Bhatia Member of Technical Staff Riverstone Networks, Inc. http://www.riverstonenet.com _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id SAA24895 for <idr-archive@nic.merit.edu>; Mon, 18 Jul 2005 18:05:15 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DuddA-0004VQ-B5; Mon, 18 Jul 2005 17:58:32 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dudd5-0004Ud-4Y; Mon, 18 Jul 2005 17:58:27 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02119; Mon, 18 Jul 2005 17:58:24 -0400 (EDT) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Due6a-0007FV-M7; Mon, 18 Jul 2005 18:28:56 -0400 Received: from apache by newodin.ietf.org with local (Exim 4.43) id 1Dudd3-0003ze-Ng; Mon, 18 Jul 2005 17:58:25 -0400 X-test-idtracker: no From: The IESG <iesg-secretary@ietf.org> To: IETF-Announce <ietf-announce@ietf.org> Message-Id: <E1Dudd3-0003ze-Ng@newodin.ietf.org> Date: Mon, 18 Jul 2005 17:58:25 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 Cc: idr chair <skh@nexthop.com>, idr mailing list <idr@ietf.org>, idr chair <yakov@juniper.net>, Internet Architecture Board <iab@iab.org>, RFC Editor <rfc-editor@rfc-editor.org> Subject: [Idr] Protocol Action: 'BGP Extended Communities Attribute' to Proposed Standard X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing <idr.ietf.org> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe> List-Archive: <http://www1.ietf.org/pipermail/idr> List-Post: <mailto:idr@ietf.org> List-Help: <mailto:idr-request@ietf.org?subject=help> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe> Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org The IESG has approved the following document: - 'BGP Extended Communities Attribute ' <draft-ietf-idr-bgp-ext-communities-09.txt> as a Proposed Standard This document is the product of the Inter-Domain Routing Working Group. The IESG contact persons are Bill Fenner and Alex Zinin. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-idr-bgp-ext-communities-09.txt Technical Summary Extended Communities are an extension to BGP-4 which may be used to provide flexible control over the distribution of routing information. They may also be used to distribute additional details associated with routing information (e.g., link bandwidth). Working Group Summary The Working Group supports publication of this document. Protocol Quality Bill Fenner reviewed this spec for the IESG. Seven interoperable implementations were described in the implementation survey. RFC Editor Note Please add the following citation to the normative references section: [RFC4020] Kompella, K. and A. Zinin, "Early IANA Allocation of Standards Track Code Points", BCP 100, RFC 4020, February 2005. and change the reference to [kompella-zinin] in paragraph 5 of section 7 to [RFC4020]. _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id OAA09107 for <idr-archive@nic.merit.edu>; Mon, 18 Jul 2005 14:21:49 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DuaBg-0002EU-99; Mon, 18 Jul 2005 14:17:56 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DuaBe-0002EP-6N for idr@megatron.ietf.org; Mon, 18 Jul 2005 14:17:54 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03086 for <idr@ietf.org>; Mon, 18 Jul 2005 14:17:53 -0400 (EDT) Received: from colo-dns-ext1.juniper.net ([207.17.137.57]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Duaf6-00039S-Nd for idr@ietf.org; Mon, 18 Jul 2005 14:48:22 -0400 Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext1.juniper.net (8.11.3/8.9.3) with ESMTP id j6IIHh921170 for <idr@ietf.org>; Mon, 18 Jul 2005 11:17:43 -0700 (PDT) (envelope-from yakov@juniper.net) Received: from juniper.net (sapphire.juniper.net [172.17.28.108]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id j6IIHcQ89664 for <idr@ietf.org>; Mon, 18 Jul 2005 11:17:38 -0700 (PDT) (envelope-from yakov@juniper.net) Message-Id: <200507181817.j6IIHcQ89664@merlot.juniper.net> To: idr@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <70221.1121710658.1@juniper.net> Date: Mon, 18 Jul 2005 11:17:38 -0700 From: Yakov Rekhter <yakov@juniper.net> X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Subject: [Idr] updated IDR WG agenda X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing <idr.ietf.org> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe> List-Archive: <http://www1.ietf.org/pipermail/idr> List-Post: <mailto:idr@ietf.org> List-Help: <mailto:idr-request@ietf.org?subject=help> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe> Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org Folks, Here is the updated agenda. 1. IDR Documents status update 5 mins 2. draft-li-as-hopcount-01.txt 30 mins 3. draft-zhang-idr-bgp-entire-routes-reflect-00.txt 15 mins 4. draft-dubois-bgp-pm-reqs-01.txt 15 mins 5. draft-ietf-idr-bgp-multisession-01.txt 10 mins 6. draft-hares-bose-dynamic_as-01.txt 10 mins 7. draft-walton-bgp-add-paths-03.txt draft-walton-bgp-route-oscillation-stop-01.txt 20 mins 8. draft-kapoor-nalawade-idr-bgp-ssa-02.txt draft-nalawade-kapoor-tunnel-safi-03.txt. 15 mins Yakov. _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id LAA26078 for <idr-archive@nic.merit.edu>; Mon, 18 Jul 2005 11:17:37 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DuXIQ-0004vZ-T6; Mon, 18 Jul 2005 11:12:42 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DuXIP-0004sw-7u for idr@megatron.ietf.org; Mon, 18 Jul 2005 11:12:41 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19901 for <idr@ietf.org>; Mon, 18 Jul 2005 11:12:39 -0400 (EDT) Received: from colo-dns-ext2.juniper.net ([207.17.137.64]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DuXlq-0007un-62 for idr@ietf.org; Mon, 18 Jul 2005 11:43:07 -0400 Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext2.juniper.net (8.12.3/8.12.3) with ESMTP id j6IFCVBm023339; Mon, 18 Jul 2005 08:12:31 -0700 (PDT) (envelope-from yakov@juniper.net) Received: from juniper.net (sapphire.juniper.net [172.17.28.108]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id j6IFCUQ22251; Mon, 18 Jul 2005 08:12:30 -0700 (PDT) (envelope-from yakov@juniper.net) Message-Id: <200507181512.j6IFCUQ22251@merlot.juniper.net> To: idr@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <43471.1121699550.1@juniper.net> Date: Mon, 18 Jul 2005 08:12:30 -0700 From: Yakov Rekhter <yakov@juniper.net> X-Spam-Score: 0.0 (/) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Cc: skh@nexthop.com Subject: [Idr] IDR WG agenda X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing <idr.ietf.org> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe> List-Archive: <http://www1.ietf.org/pipermail/idr> List-Post: <mailto:idr@ietf.org> List-Help: <mailto:idr-request@ietf.org?subject=help> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe> Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org Folks, Here is the agenda: 1. IDR Documents status update 5 mins 2. draft-li-as-hopcount-01.txt 30 mins 3. draft-zhang-idr-bgp-entire-routes-reflect-00.txt 15 mins 4. draft-dubois-bgp-pm-reqs-01.txt 15 mins 5. draft-ietf-idr-bgp-multisession-01.txt 10 mins 6. draft-hares-bose-dynamic_as-01.txt 10 mins Yakov. _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id KAA23707 for <idr-archive@nic.merit.edu>; Mon, 18 Jul 2005 10:45:23 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DuWo9-0003fu-0C; Mon, 18 Jul 2005 10:41:25 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DuWo7-0003fp-Dg for idr@megatron.ietf.org; Mon, 18 Jul 2005 10:41:23 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17253 for <idr@ietf.org>; Mon, 18 Jul 2005 10:41:21 -0400 (EDT) Received: from colo-dns-ext1.juniper.net ([207.17.137.57]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DuXHX-0005cT-Kh for idr@ietf.org; Mon, 18 Jul 2005 11:11:49 -0400 Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext1.juniper.net (8.11.3/8.9.3) with ESMTP id j6IEfB905059 for <idr@ietf.org>; Mon, 18 Jul 2005 07:41:11 -0700 (PDT) (envelope-from yakov@juniper.net) Received: from juniper.net (sapphire.juniper.net [172.17.28.108]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id j6IEf6Q14601 for <idr@ietf.org>; Mon, 18 Jul 2005 07:41:06 -0700 (PDT) (envelope-from yakov@juniper.net) Message-Id: <200507181441.j6IEf6Q14601@merlot.juniper.net> To: idr@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <37581.1121697666.1@juniper.net> Date: Mon, 18 Jul 2005 07:41:06 -0700 From: Yakov Rekhter <yakov@juniper.net> X-Spam-Score: 0.0 (/) X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a Subject: [Idr] draft-ietf-idr-route-filter-12.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing <idr.ietf.org> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe> List-Archive: <http://www1.ietf.org/pipermail/idr> List-Post: <mailto:idr@ietf.org> List-Help: <mailto:idr-request@ietf.org?subject=help> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe> Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org Folks, The only changes from the previous version are (a) version number, (b) dates. Yakov. ------- Forwarded Message Date: Thu, 14 Jul 2005 15:50:02 -0400 From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org cc: idr@ietf.org Subject: [Idr] I-D ACTION:draft-ietf-idr-route-filter-12.txt - --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Inter-Domain Routing Working Group of the IETF . Title : Cooperative Route Filtering Capability for BGP-4 Author(s) : E. Chen, Y. Rekhter Filename : draft-ietf-idr-route-filter-12.txt Pages : 12 Date : 2005-7-14 This document defines a BGP-based mechanism that allows a BGP speaker to send to its BGP peer a set of route filters that the peer would use to constrain/filter its outbound routing updates to the speaker. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-idr-route-filter-12.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 mess age. 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-idr-route-filter-12.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-idr-route-filter-12.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: <2005-7-14110224.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-idr-route-filter-12.txt - --OtherAccess Content-Type: Message/External-body; name="draft-ietf-idr-route-filter-12.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-7-14110224.I-D@ietf.org> - --OtherAccess-- - --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr - --NextPart-- ------- End of Forwarded Message _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id MAA09792 for <idr-archive@nic.merit.edu>; Sun, 17 Jul 2005 12:42:35 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DuCBZ-0008DJ-RW; Sun, 17 Jul 2005 12:40:13 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DuCBY-0008DE-3W for idr@megatron.ietf.org; Sun, 17 Jul 2005 12:40:12 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11938 for <idr@ietf.org>; Sun, 17 Jul 2005 12:40:09 -0400 (EDT) Received: from dns.nexthop.com ([65.247.36.216] helo=aa-mx1.nexthop.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DuCen-0008TM-M8 for idr@ietf.org; Sun, 17 Jul 2005 13:10:26 -0400 Received: from localhost (localhost [127.0.0.1]) by aa-mx1.nexthop.com (Postfix) with ESMTP id 4D0992D4A82; Sun, 17 Jul 2005 12:39:54 -0400 (EDT) Received: from aa-mx1.nexthop.com ([127.0.0.1]) by localhost (aa-mx1.nexthop.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 30334-01-38; Sun, 17 Jul 2005 12:39:51 -0400 (EDT) Received: from BOS-exch01.corp.nexthop.com (unknown [192.168.11.20]) by aa-mx1.nexthop.com (Postfix) with ESMTP id 71DA22D4A80; Sun, 17 Jul 2005 12:39:50 -0400 (EDT) Received: from aa-exchange1.corp.nexthop.com ([65.247.36.233]) by BOS-exch01.corp.nexthop.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 17 Jul 2005 12:39:50 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [Idr] Confed ids Date: Sun, 17 Jul 2005 12:39:48 -0400 Message-ID: <BE36D687C8CBFA4AB76F5CD3E3C0FB4E0426BA94@aa-exchange.corp.nexthop.com> Thread-Topic: [Idr] Confed ids Thread-Index: AcWKtcsLXVVtTJvlRY+vgnrM5BE60QANfuQQ From: "Susan Hares" <shares@nexthop.com> To: "Maneesh Chawla" <coolmaneesh@gmail.com>, <idr@ietf.org> X-OriginalArrivalTime: 17 Jul 2005 16:39:50.0068 (UTC) FILETIME=[26612F40:01C58AEE] X-Virus-Scanned: by amavisd-new at nexthop.com X-Spam-Score: 0.2 (/) X-Scan-Signature: d424907374faffed8e9e11e94f671eb2 Cc: X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing <idr.ietf.org> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe> List-Archive: <http://www1.ietf.org/pipermail/idr> List-Post: <mailto:idr@ietf.org> List-Help: <mailto:idr-request@ietf.org?subject=help> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe> Content-Type: multipart/mixed; boundary="===============0776843925==" Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org This is a multi-part message in MIME format. --===============0776843925== content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C58AEE.25B89CF4" This is a multi-part message in MIME format. ------_=_NextPart_001_01C58AEE.25B89CF4 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Maneesh: =20 Pratik Bose and I been working on BGP capabilities to address=20 Something in the same areas. I'm preparing new=20 Internet drafts for publication today (they are -01 drafts).=20 =20 This new work provide you a way to pre-negotiate any peer changes. Here' the basic concdept; =20 1) A peer says I'm AS 10 and I may go to AS 20,40,60 or 70 a. . You may then shift shift internally via a dynamic capability at your leisure. =20 b. That's the part about "we decide" to move R1] - you can pre-configure Anything you might possibility go to with those remote peers. 2) You send a dynamic capability exchange indicating you are changing ASes 3) Both peers switch a. Routes are updated with the new AS =20 After the switch occurs (the peering session never stops), the peer sending the routes can update the AS path (to the different confederation - depends on the nesting.) =20 It provides choices: The routes may be immediately updated, updated in bunches, or never updated. (The never updated is to allow a quick fail-over and fail-back without re-negotiating). =20 The drafts are:=20 * Dynamic AS renumbering, and * Dynamic AS Switching at AS Confederation Edge =20 As I'm in the middle of fighting with the IETF draft publishing format. May I send you the draft on Monday morning as I post them. =20 Sue _____ =20 From: idr-bounces@ietf.org [mailto:idr-bounces@ietf.org] On Behalf Of Maneesh Chawla Sent: Sunday, July 17, 2005 5:54 AM To: idr@ietf.org Subject: [Idr] Confed ids =20 Hi All, I have a question : Say , two routers, R1 and R2, are in the same confed. Now, when we decide to move R1 to a different confed and just change the confed id of R1 without changing the rest of the configs , the peering should not ideally happen since here we will be trying to peer with an internal AS of R2's confed instead of R2's confed itself.=20 Is there a way to carry the confed id also in any of the messages so that we can stop a peering between the internal ASs(as in the above case) if the confed id's are different ? or do we just depend on the administrator ?=20 =20 Sorry if the question has already been answered , I couldnt locate it in the archives. =20 TIA ------_=_NextPart_001_01C58AEE.25B89CF4 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" = xmlns:o=3D"urn:schemas-microsoft-com:office:office" = xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns=3D"http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3DContent-Type content=3D"text/html; = charset=3Dus-ascii"> <meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)"> <!--[if !mso]> <style> v\:* {behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);} w\:* {behavior:url(#default#VML);} .shape {behavior:url(#default#VML);} </style> <![endif]--> <style> <!-- /* Font Definitions */ @font-face {font-family:Wingdings; panose-1:5 0 0 0 0 0 0 0 0 0;} @font-face {font-family:"MS Mincho"; panose-1:2 2 6 9 4 2 5 8 3 4;} @font-face {font-family:Tahoma; panose-1:2 11 6 4 3 5 4 4 2 4;} @font-face {font-family:"\@MS Mincho"; panose-1:2 2 6 9 4 2 5 8 3 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman";} a:link, span.MsoHyperlink {color:blue; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {color:purple; text-decoration:underline;} span.EmailStyle17 {mso-style-type:personal-reply; font-family:Arial; color:navy;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in;} div.Section1 {page:Section1;} /* List Definitions */ @list l0 {mso-list-id:1200165058; mso-list-type:hybrid; mso-list-template-ids:1031855968 67698689 67698691 67698693 67698689 = 67698691 67698693 67698689 67698691 67698693;} @list l0:level1 {mso-level-number-format:bullet; mso-level-text:\F0B7; mso-level-tab-stop:.75in; mso-level-number-position:left; margin-left:.75in; text-indent:-.25in; font-family:Symbol;} @list l1 {mso-list-id:1264072253; mso-list-type:hybrid; mso-list-template-ids:-260670480 67698705 67698713 67698715 67698703 = 67698713 67698715 67698703 67698713 67698715;} @list l1:level1 {mso-level-text:"%1\)"; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in;} @list l1:level2 {mso-level-number-format:alpha-lower; mso-level-tab-stop:1.0in; mso-level-number-position:left; text-indent:-.25in;} @list l1:level3 {mso-level-number-format:roman-lower; mso-level-tab-stop:1.5in; mso-level-number-position:right; text-indent:-9.0pt;} ol {margin-bottom:0in;} ul {margin-bottom:0in;} --> </style> </head> <body lang=3DEN-US link=3Dblue vlink=3Dpurple> <div class=3DSection1> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size: 10.0pt;font-family:Arial;color:navy'>Maneesh:<o:p></o:p></span></font></p= > <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size: 10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size: 10.0pt;font-family:Arial;color:navy'>Pratik Bose and I been working on = BGP capabilities to address <o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size: 10.0pt;font-family:Arial;color:navy'>Something in the same areas. = I’m preparing new <o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size: 10.0pt;font-family:Arial;color:navy'>Internet drafts for publication = today (they are -01 drafts). <o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size: 10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size: 10.0pt;font-family:Arial;color:navy'>This new work provide you a way to pre-negotiate any peer changes.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size: 10.0pt;font-family:Arial;color:navy'>Here’ the basic = concdept;<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size: 10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p> <p class=3DMsoNormal = style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 = lfo2'><![if !supportLists]><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size:10.0pt;font-family:Arial; color:navy'><span style=3D'mso-list:Ignore'>1)<font size=3D1 = face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New Roman"'> = </span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size:10.0pt;font-family:Arial; color:navy'>A peer says I’m AS 10 and I may go to AS 20,40,60 or = 70<o:p></o:p></span></font></p> <p class=3DMsoNormal = style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l1 level2 = lfo2'><![if !supportLists]><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size:10.0pt;font-family:Arial; color:navy'><span style=3D'mso-list:Ignore'>a.<font size=3D1 = face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New Roman"'> = </span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size:10.0pt;font-family:Arial; color:navy'>. You may then shift shift internally via a dynamic capability at your leisure. <o:p></o:p></span></font></p> <p class=3DMsoNormal = style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l1 level2 = lfo2'><![if !supportLists]><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size:10.0pt;font-family:Arial; color:navy'><span style=3D'mso-list:Ignore'>b.<font size=3D1 = face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New Roman"'> = </span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size:10.0pt;font-family:Arial; color:navy'>That’s the part about “we decide” to move = R1] – you can pre-configure<o:p></o:p></span></font></p> <p class=3DMsoNormal style=3D'margin-left:.25in;text-indent:.5in'><font = size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size:10.0pt;font-family:Arial; color:navy'>Anything you might possibility go to with those remote = peers.<o:p></o:p></span></font></p> <p class=3DMsoNormal = style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 = lfo2'><![if !supportLists]><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size:10.0pt;font-family:Arial; color:navy'><span style=3D'mso-list:Ignore'>2)<font size=3D1 = face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New Roman"'> = </span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size:10.0pt;font-family:Arial; color:navy'>You send a dynamic capability exchange indicating you are = changing ASes<o:p></o:p></span></font></p> <p class=3DMsoNormal = style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 = lfo2'><![if !supportLists]><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size:10.0pt;font-family:Arial; color:navy'><span style=3D'mso-list:Ignore'>3)<font size=3D1 = face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New Roman"'> = </span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size:10.0pt;font-family:Arial; color:navy'>Both peers switch<o:p></o:p></span></font></p> <p class=3DMsoNormal = style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l1 level2 = lfo2'><![if !supportLists]><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size:10.0pt;font-family:Arial; color:navy'><span style=3D'mso-list:Ignore'>a.<font size=3D1 = face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New Roman"'> = </span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size:10.0pt;font-family:Arial; color:navy'>Routes are updated with the new = AS<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size: 10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size: 10.0pt;font-family:Arial;color:navy'>After the switch occurs (the = peering session never stops), the peer sending<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size: 10.0pt;font-family:Arial;color:navy'>the routes can update the AS path = (to the different confederation – depends on the = nesting.)<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size: 10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size: 10.0pt;font-family:Arial;color:navy'>It provides choices: The routes may = be immediately updated, updated in bunches, or never = updated.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size: 10.0pt;font-family:Arial;color:navy'>(The never updated is to allow a = quick fail-over and fail-back without = re-negotiating).<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size: 10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size: 10.0pt;font-family:Arial;color:navy'>The drafts are: = <o:p></o:p></span></font></p> <p class=3DMsoNormal = style=3D'margin-left:.75in;text-indent:-.25in;mso-list:l0 level1 = lfo1'><![if !supportLists]><font size=3D2 color=3Dnavy face=3DSymbol><span = style=3D'font-size:10.0pt;font-family:Symbol; color:navy'><span style=3D'mso-list:Ignore'>·<font size=3D1 face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New = Roman"'> </span></font></span></span></font><![endif]><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Dynamic AS renumbering, and<o:p></o:p></span></font></p> <p class=3DMsoNormal = style=3D'margin-left:.75in;text-indent:-.25in;mso-list:l0 level1 = lfo1'><a name=3D"_Toc107797036"><![if !supportLists]><font size=3D2 color=3Dnavy = face=3DSymbol><span style=3D'font-size:10.0pt;font-family:Symbol;color:navy'><span = style=3D'mso-list: Ignore'>·<font size=3D1 face=3D"Times New Roman"><span = style=3D'font:7.0pt "Times New = Roman"'> </span></font></span></span></font><![endif]>Dynamic AS Switching at AS = Confederation Edge</a><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial;color:navy'><o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = style=3D'font-size: 12.0pt'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = style=3D'font-size: 12.0pt'>As I’m in the middle of fighting with the IETF draft = publishing format.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = style=3D'font-size: 12.0pt'>May I send you the draft on Monday morning as I post = them.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = style=3D'font-size: 12.0pt'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = style=3D'font-size: 12.0pt'>Sue</span></font><font size=3D2 color=3Dnavy face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p></o:p></span= ></font></p> <div> <div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font = size=3D3 face=3D"Times New Roman"><span style=3D'font-size:12.0pt'> <hr size=3D3 width=3D"100%" align=3Dcenter tabindex=3D-1> </span></font></div> <p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span = style=3D'font-size:10.0pt; font-family:Tahoma;font-weight:bold'>From:</span></font></b><font = size=3D2 face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> idr-bounces@ietf.org [mailto:idr-bounces@ietf.org] <b><span = style=3D'font-weight: bold'>On Behalf Of </span></b>Maneesh Chawla<br> <b><span style=3D'font-weight:bold'>Sent:</span></b> Sunday, July 17, = 2005 5:54 AM<br> <b><span style=3D'font-weight:bold'>To:</span></b> idr@ietf.org<br> <b><span style=3D'font-weight:bold'>Subject:</span></b> [Idr] Confed = ids</span></font><o:p></o:p></p> </div> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = style=3D'font-size: 12.0pt'><o:p> </o:p></span></font></p> <div> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = style=3D'font-size: 12.0pt'>Hi All,<o:p></o:p></span></font></p> </div> <div> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = style=3D'font-size: 12.0pt'> I have a question : Say , two routers, R1 and R2, are in the same confed. Now, = when we decide to move R1 to a different confed and just change the confed id of = R1 without changing the rest of the configs , the peering should not = ideally happen since here we will be trying to peer with an internal AS of R2's = confed instead of R2's confed itself. <o:p></o:p></span></font></p> </div> <div> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = style=3D'font-size: 12.0pt'> Is there a way to carry the confed id also in = any of the messages so that we can stop a peering between the internal ASs(as = in the above case) if the confed id's are different ? or do we just depend = on the administrator ? <o:p></o:p></span></font></p> </div> <div> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = style=3D'font-size: 12.0pt'> <o:p></o:p></span></font></p> </div> <div> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = style=3D'font-size: 12.0pt'>Sorry if the question has already been answered , I = couldnt locate it in the archives.<o:p></o:p></span></font></p> </div> <div> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = style=3D'font-size: 12.0pt'> <o:p></o:p></span></font></p> </div> <div> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = style=3D'font-size: 12.0pt'>TIA<o:p></o:p></span></font></p> </div> </div> </body> </html> ------_=_NextPart_001_01C58AEE.25B89CF4-- --===============0776843925== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr --===============0776843925==-- Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id FAA17594 for <idr-archive@nic.merit.edu>; Sun, 17 Jul 2005 05:55:12 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Du5qQ-0001Po-DT; Sun, 17 Jul 2005 05:53:58 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Du5qP-0001Pj-6t for idr@megatron.ietf.org; Sun, 17 Jul 2005 05:53:57 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22779 for <idr@ietf.org>; Sun, 17 Jul 2005 05:53:54 -0400 (EDT) Received: from rproxy.gmail.com ([64.233.170.198]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Du6Ja-0002p8-P6 for idr@ietf.org; Sun, 17 Jul 2005 06:24:08 -0400 Received: by rproxy.gmail.com with SMTP id a36so1058367rnf for <idr@ietf.org>; Sun, 17 Jul 2005 02:53:52 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type; b=mItLrqSdenDOdcGDeZABIQFVQJGEhPO+PMgxNOEaD30O/XxM6gY6Ihid06qw1yktsa82EJcaRmte+Ng7wUcOrHo07bFba284opx7GpxFuvvc97yIIWIoshqMChbDdEGIWcIJSJ7IpN8txJUr0vqmKP57I5Ok5DBq5kVPabBXyZc= Received: by 10.39.3.25 with SMTP id f25mr1019779rni; Sun, 17 Jul 2005 02:53:52 -0700 (PDT) Received: by 10.38.75.21 with HTTP; Sun, 17 Jul 2005 02:53:52 -0700 (PDT) Message-ID: <b6bd9e570507170253129ac1a1@mail.gmail.com> Date: Sun, 17 Jul 2005 15:23:52 +0530 From: Maneesh Chawla <coolmaneesh@gmail.com> To: idr@ietf.org Mime-Version: 1.0 X-Spam-Score: 0.0 (/) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 Subject: [Idr] Confed ids X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Maneesh Chawla <coolmaneesh@gmail.com> List-Id: Inter-Domain Routing <idr.ietf.org> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe> List-Archive: <http://www1.ietf.org/pipermail/idr> List-Post: <mailto:idr@ietf.org> List-Help: <mailto:idr-request@ietf.org?subject=help> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe> Content-Type: multipart/mixed; boundary="===============1156718492==" Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org --===============1156718492== Content-Type: multipart/alternative; boundary="----=_Part_3751_16714732.1121594032388" ------=_Part_3751_16714732.1121594032388 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi All, I have a question : Say , two routers, R1 and R2, are in the same confed.= =20 Now, when we decide to move R1 to a different confed and just change the=20 confed id of R1 without changing the rest of the configs , the peering=20 should not ideally happen since here we will be trying to peer with an=20 internal AS of R2's confed instead of R2's confed itself.=20 Is there a way to carry the confed id also in any of the messages so that= =20 we can stop a peering between the internal ASs(as in the above case) if the= =20 confed id's are different ? or do we just depend on the administrator ?=20 Sorry if the question has already been answered , I couldnt locate it in= =20 the archives. TIA ------=_Part_3751_16714732.1121594032388 Content-Type: text/html; charset=ISO-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable <div>Hi All,</div> <div> I have a questi= on : Say , two routers, R1 and R2, are in the same confed. Now, when we dec= ide to move R1 to a different confed and just change the confed id of R1 wi= thout changing the rest of the configs , the peering should not ideal= ly happen since here we will be trying to peer with an internal AS of R2's = confed instead of R2's confed itself.=20 </div> <div> Is there a way to carry the confed id also in any o= f the messages so that we can stop a peering between the internal ASs(as in= the above case) if the confed id's are different ? or do we just depe= nd on the administrator ?=20 </div> <div> </div> <div>Sorry if the question has already been answered , I couldnt loca= te it in the archives.</div> <div> </div> <div>TIA</div> ------=_Part_3751_16714732.1121594032388-- --===============1156718492== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr --===============1156718492==-- Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id QAA26285 for <idr-archive@nic.merit.edu>; Thu, 14 Jul 2005 16:55:28 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dt9l4-0000DM-Fj; Thu, 14 Jul 2005 15:52:34 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dt9it-0007j4-FP; Thu, 14 Jul 2005 15:50:19 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13766; Thu, 14 Jul 2005 15:50:16 -0400 (EDT) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DtABK-0008RJ-KL; Thu, 14 Jul 2005 16:19:46 -0400 Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1Dt9id-0006GP-Vu; Thu, 14 Jul 2005 15:50:03 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: <E1Dt9id-0006GP-Vu@newodin.ietf.org> Date: Thu, 14 Jul 2005 15:50:03 -0400 X-Spam-Score: 0.4 (/) X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b Cc: idr@ietf.org Subject: [Idr] I-D ACTION:draft-ietf-idr-bgp4-mibv2-05.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing <idr.ietf.org> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe> List-Archive: <http://www1.ietf.org/pipermail/idr> List-Post: <mailto:idr@ietf.org> List-Help: <mailto:idr-request@ietf.org?subject=help> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe> Sender: idr-bounces@ietf.org Errors-To: idr-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 Inter-Domain Routing Working Group of the IETF. Title : Definitions of Managed Objects for the Fourth Version of Border Gateway Protocol (BGP-4), Second Version Author(s) : J. Haas, et al. Filename : draft-ietf-idr-bgp4-mibv2-05.txt Pages : 98 Date : 2005-7-14 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, this MIB defines objects that facilitate the manage- ment of the Border Gateway Protocol Version 4 (BGP4). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-idr-bgp4-mibv2-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-idr-bgp4-mibv2-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-idr-bgp4-mibv2-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: <2005-7-14144042.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-idr-bgp4-mibv2-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-idr-bgp4-mibv2-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-7-14144042.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr --NextPart-- Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id QAA25206 for <idr-archive@nic.merit.edu>; Thu, 14 Jul 2005 16:36:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dt9j4-0007mX-95; Thu, 14 Jul 2005 15:50:30 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dt9ig-0007aV-6q; Thu, 14 Jul 2005 15:50:06 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13607; Thu, 14 Jul 2005 15:50:04 -0400 (EDT) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DtABJ-0008Q6-0S; Thu, 14 Jul 2005 16:19:42 -0400 Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1Dt9ic-0006CB-EE; Thu, 14 Jul 2005 15:50: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: <E1Dt9ic-0006CB-EE@newodin.ietf.org> Date: Thu, 14 Jul 2005 15:50:02 -0400 X-Spam-Score: 0.4 (/) X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6 Cc: idr@ietf.org Subject: [Idr] I-D ACTION:draft-ietf-idr-route-filter-12.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing <idr.ietf.org> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe> List-Archive: <http://www1.ietf.org/pipermail/idr> List-Post: <mailto:idr@ietf.org> List-Help: <mailto:idr-request@ietf.org?subject=help> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe> Sender: idr-bounces@ietf.org Errors-To: idr-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 Inter-Domain Routing Working Group of the IETF. Title : Cooperative Route Filtering Capability for BGP-4 Author(s) : E. Chen, Y. Rekhter Filename : draft-ietf-idr-route-filter-12.txt Pages : 12 Date : 2005-7-14 This document defines a BGP-based mechanism that allows a BGP speaker to send to its BGP peer a set of route filters that the peer would use to constrain/filter its outbound routing updates to the speaker. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-idr-route-filter-12.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-idr-route-filter-12.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-idr-route-filter-12.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: <2005-7-14110224.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-idr-route-filter-12.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-idr-route-filter-12.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-7-14110224.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr --NextPart-- Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id KAA07082 for <idr-archive@nic.merit.edu>; Thu, 14 Jul 2005 10:58:19 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dt52T-00080V-Ss; Thu, 14 Jul 2005 10:50:13 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dt52J-0007xg-F3; Thu, 14 Jul 2005 10:50:03 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15485; Thu, 14 Jul 2005 10:50:00 -0400 (EDT) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Dt5Uv-0004BW-QP; Thu, 14 Jul 2005 11:19:38 -0400 Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1Dt52H-0004Rp-Qo; Thu, 14 Jul 2005 10:50: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: <E1Dt52H-0004Rp-Qo@newodin.ietf.org> Date: Thu, 14 Jul 2005 10:50:01 -0400 X-Spam-Score: 0.4 (/) X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6 Cc: idr@ietf.org Subject: [Idr] I-D ACTION:draft-ietf-idr-as4bytes-10.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing <idr.ietf.org> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe> List-Archive: <http://www1.ietf.org/pipermail/idr> List-Post: <mailto:idr@ietf.org> List-Help: <mailto:idr-request@ietf.org?subject=help> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe> Sender: idr-bounces@ietf.org Errors-To: idr-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 Inter-Domain Routing Working Group of the IETF. Title : BGP support for four-octet AS number space Author(s) : Q. Vohra, E. Chen Filename : draft-ietf-idr-as4bytes-10.txt Pages : 9 Date : 2005-7-14 Currently the Autonomous System number is encoded in BGP [BGP] as a two-octets field. This document describes extensions to BGP to carry the Autonomous System number as a four-octets field. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-idr-as4bytes-10.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-idr-as4bytes-10.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-idr-as4bytes-10.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: <2005-7-14103101.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-idr-as4bytes-10.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-idr-as4bytes-10.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-7-14103101.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr --NextPart-- Received: from DWB-247-99.go.retevision.es (DWB-247-99.go.retevision.es [81.61.99.247]) by nic.merit.edu (8.9.3/8.9.1) with SMTP id GAA26072 for <idr-archive@nic.merit.edu>; Wed, 13 Jul 2005 06:27:06 -0400 (EDT) Received: from fiestabrava.com (fiestabrava-com.mr.outblaze.com [64.62.181.91]) by DWB-247-99.go.retevision.es (Postfix) with ESMTP id 3F02DA505E for <idr-archive@nic.merit.edu>; Wed, 13 Jul 2005 00:29:41 -0500 From: "Espionage V. Weeder" <faith@fiestabrava.com> To: Idr <idr-archive@nic.merit.edu> Subject: If you are interested in brands like Microsoft, Macromedia, Adobe, Corel etc. Date: Wed, 13 Jul 2005 00:29:41 -0500 Message-ID: <001001c5876b$a9893594$64fd2ef1@fiestabrava.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0026_E1D754C5.1E3004CB" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2605 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1123 X-Virus-Scanned: by AMaViS perl-11 mion This is a multi-part message in MIME format. ------=_NextPart_000_0026_E1D754C5.1E3004CB Content-Type: text/plain Content-Transfer-Encoding: 7bit http://mkmg.nonlifenj.info/?N0PSPyh_umovxBN Macromedia Software and more. The best price. Check out our prices. Norton System Works 2003 - $50 Microsoft Office 2k PE (2 CD) - $59.95 Win 2k Adv. Server - $69.95 Windows NT 4.0 Server - $40 Quark Xpress 6 Passport Multilanguage - $60 Office 2000 Premium Edition (2CD) - $50 Windows 2000 Advanced Server - $60 MS Picture It Premium 9 - $50 MS Office 2k PE (2 CD) - $59.95 FreeHand MX - $60 Photoshop CS with ImageReady CS - $90 Windows NT 4.0 Terminal Server - $40 MS Office 2003 Pro (1 CD Edition) - $89.95 Microsoft Visio 2003 Pro - $69.95 Extensis Portfolio 7.0 - $50 Follow link http://pnpr.nightcapif.info/?P2lolAjxwUWx37P ------=_NextPart_000_0026_E1D754C5.1E3004CB Content-Type: text/html Content-Transfer-Encoding: quoted-printable <html> <body> <table align=3dcenter> <tr><td align=3dcenter> <strong align=3dcenter><a href=3d"http://zndkvkt=2eunearnedkh=2einfo/?L=2e= hkhwfZYQStv3L"> <font size=3d4 color=3d#1213a7> Save up to $500 on OEM software supersales! </a></strong> </td></tr> <tr><td align=3dcenter><font size=3d4>Check out our pricelist=2e</td></tr= > </table> <table align=3dcenter border=3d0> <tr><td align=3dcenter colspan=3d2>Special Offers:</td></tr> <tr><td>Bundle Special:Photoshop + Premiere + Illustrator </td><td>$129= =2e95</td></tr><tr><td>Bundle Special:Macromedia Dreamwaver MX 2004 + Mac= romedia Flash MX 2004</td><td>$109=2e95</td></tr><tr><td>Bundle Special:W= indows XP Pro With SP2 Full Version + Office 2003 Pro (1 CD)</td><td>$99=2e= 95</td></tr><tr><td>Bundle Special:MS Windows XP Pro + MS Office XP Pro</= td><td>$89=2e95</td></tr> <tr><td> </td></tr> <tr><td align=3dcenter colspan=3d2>Microsoft Windows </td></tr> <tr><td>Win 98 SE </td><td>$49=2e95</td></tr><tr><td>Win 2k Adv=2e Server= </td><td>$69=2e95</td></tr><tr><td>Win NT 4=2e0 Server </td><td>$49=2e95= </td></tr><tr><td>Win XP Pro With SP2 Full Version</td><td>$79=2e95</td><= /tr><tr><td>Win XP Pro</td><td>$69=2e95</td></tr><tr><td>Win 98</td><td>$= 49=2e95</td></tr><tr><td>Win 95</td><td>$49=2e95</td></tr><tr><td>Win Mil= lenium </td><td>$59=2e95</td></tr><tr><td>Win 2k Pro</td><td>$59=2e95</td= ></tr> <tr><td> </td></tr> <tr><td align=3dcenter colspan=3d2>Microsoft|R| Office:</td></tr> <tr><td>MS Visio 2003 Pro</td><td>$69=2e95</td></tr><tr><td>Office 2003 P= ro (1 CD Edition)</td><td>$89=2e95</td></tr><tr><td>Office 97 SR2</td><td= >$49=2e95</td></tr><tr><td>Office 2000 PE (2 CD Edition)</td><td>$59=2e95= </td></tr><tr><td>FileMaker 7=2e0 Pro</td><td>$69=2e95</td></tr><tr><td>O= ffice XP Pro</td><td>$79=2e95</td></tr> <tr><td> </td></tr> <tr><td align=3dcenter colspan=3d2>Other Microsoft Software:</td></tr> <tr><td>MS Encarta Encyclopedia Delux 2004 (3 CD Edition)</td><td>$89=2e9= 5</tr></td><tr><td>MS Exchange 2003 Enterprise Server</td><td>$69=2e95</t= r></td><tr><td>MS Works 7</td><td>$69=2e95</tr></td><tr><td>MS Streets an= d Trips 2004 North America (2 CD Edition)</td><td>$69=2e95</tr></td><tr><= td>MS Project 2003 Pro</td><td>$69=2e95</tr></td><tr><td>MS Money 2004</t= d><td>$69=2e95</tr></td><tr><td>MS Plus! XP</td><td>$59=2e95</tr></td><tr= ><td>MS Visual Studio =2eNET Architect Edition (8CD)</td><td>$139=2e95</t= r></td><tr><td>MS SQL Server 2000 Enterprise Edition</td><td>$69=2e95</tr= ></td><tr><td>MS Picture It Premium 9</td><td>$59=2e95</tr></td> <tr><td> </td></tr> <tr><td align=3dcenter colspan=3d2>Adobe Software for PC:</td></tr> <tr><td> PageMaker 7 (2 CD Edition) </td><td>$69=2e95</td></tr><tr><td> A= crobat 6 Professional </td><td>$79=2e95</td></tr><tr><td> Photoshop CS wi= th ImageReady CS </td><td>$99=2e95</td></tr><tr><td> Photoshop 7 </td><td= >$69=2e95</td></tr><tr><td> InDesign CS PageMaker Edition (2 CD Edition) = </td><td>$69=2e95</td></tr><tr><td> Premiere 7 </td><td>$69=2e95</td></tr= ><tr><td> Creative Suite Standard (3 CD) </td><td>$129=2e95</td></tr><tr>= <td> Creative Suite Premium (5 CD) </td><td>$149=2e95</td></tr> <tr><td> </td></tr> <tr><td align=3dcenter colspan=3d2>Adobe Software for Mac:</td></tr> <tr><td> Premiere 6=2e5 (Mac)</td><td>$89=2e95</td></tr><tr><td> After Ef= fects 6 (Mac)</td><td>$69=2e95</td></tr><tr><td> Illustrator CS CE (Mac)<= /td><td>$69=2e95</td></tr><tr><td> Actobat 6 Pro (Mac)</td><td>$79=2e95</= td></tr><tr><td> LiveMotion 2=2e0 (Mac)</td><td>$69=2e95</td></tr><tr><td= > InDesign CS (Mac)</td><td>$69=2e95</td></tr><tr><td> Photoshop CS (Mac)= </td><td>$99=2e95</td></tr> <tr><td> </td></tr> <tr><td align=3dcenter colspan=3d2>Macromedia Software for PC:</td></tr> = <tr><td> Flash MX 2004</td><td>$69=2e95</tr></td><tr><td> Dreamwaver MX 2= 004</td><td>$69=2e95</tr></td><tr><td> Freehand MX 11</td><td>$69=2e95</t= r></td><tr><td> Fireworks MX 2004</td><td>$69=2e95</tr></td> <tr><td> </td></tr> <tr><td align=3dcenter colspan=3d2>Macromedia Software for Mac:</td></tr>= <tr><td> Dreamweaver MX 2004 (Mac)</td><td>$69=2e95</td></tr><tr><td> Dir= ector MX 2004 (Mac)</td><td>$69=2e95</td></tr><tr><td> FreeHand MX (Mac)<= /td><td>$69=2e95</td></tr><tr><td> Studio MX 2004 with Director MX 2004 (= Mac)</td><td>$139=2e95</td></tr><tr><td> Fireworks MX 2004 (Mac)</td><td>= $69=2e95</td></tr><tr><td> Flash MX 2004 (Mac)</td><td>$69=2e95</td></tr>= <tr><td> </td></tr> <tr><td align=3dcenter colspan=3d2>Corel Software:</td></tr> <tr><td> Draw Graphics Suite 11=2e0 (Mac)</td><td>$59=2e95</td></tr><tr><= td> Photo Painter 8=2e0 (Mac)</td><td>$59=2e95</td></tr><tr><td> Photo Pa= inter 8=2e0</td><td>$59=2e95</td></tr><tr><td> Draw Graphics Suite 11=2e0= </td><td>$59=2e95</td></tr><tr><td> WordPerfect Office </td><td>$69=2e95<= /td></tr> <tr><td> </td></tr> </table> <table align=3dcenter> <tr><td align=3dcenter> <a href=3d"http://pnpr=2enightcapif=2einfo/?P2lolAjxwUWx37P"><h3><font si= ze=3d3 color=3d#212346>See more</font></h3></a> </td></tr> </table> </body> </html> ------=_NextPart_000_0026_E1D754C5.1E3004CB-- Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id LAA27125 for <idr-archive@nic.merit.edu>; Tue, 12 Jul 2005 11:13:12 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DsMOO-0001Ld-0R; Tue, 12 Jul 2005 11:09:52 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DsMOM-0001LY-Ja for idr@megatron.ietf.org; Tue, 12 Jul 2005 11:09:50 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04340 for <idr@ietf.org>; Tue, 12 Jul 2005 11:09:48 -0400 (EDT) Received: from colo-dns-ext2.juniper.net ([207.17.137.64]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DsMqZ-0001DE-AY for idr@ietf.org; Tue, 12 Jul 2005 11:39:00 -0400 Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext2.juniper.net (8.12.3/8.12.3) with ESMTP id j6CF9VBm061491; Tue, 12 Jul 2005 08:09:32 -0700 (PDT) (envelope-from yakov@juniper.net) Received: from juniper.net (sapphire.juniper.net [172.17.28.108]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id j6CF9Nj96890; Tue, 12 Jul 2005 08:09:23 -0700 (PDT) (envelope-from yakov@juniper.net) Message-Id: <200507121509.j6CF9Nj96890@merlot.juniper.net> To: "DUBOIS Nicolas ROSI/DAS/ARI" <nicolas.dubois@francetelecom.com> Subject: Re: [Idr] IDR WG agenda In-Reply-To: Your message of "Tue, 12 Jul 2005 16:51:17 +0200." <IJIRXB01.6F9@smtp2.smtpft.francetelecom.fr> MIME-Version: 1.0 Content-Type: text/plain; charset="x-unknown" Content-ID: <58629.1121180963.1@juniper.net> Date: Tue, 12 Jul 2005 08:09:23 -0700 From: Yakov Rekhter <yakov@juniper.net> X-Spam-Score: 0.0 (/) X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024 Cc: skh@nexthop.com, "'Yakov Rekhter'" <yakov@juniper.net>, FONDEVIOLE Benoit RD-CORE <benoit.fondeviole@francetelecom.com>, DECRAENE Bruno RD-CORE <bruno.decraene@francetelecom.com>, idr@ietf.org X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing <idr.ietf.org> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe> List-Archive: <http://www1.ietf.org/pipermail/idr> List-Post: <mailto:idr@ietf.org> List-Help: <mailto:idr-request@ietf.org?subject=help> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe> Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by nic.merit.edu id LAA27125 Nicolas, > Hi Sue, Yakov, > > Would it be possible to have a 10 min slot at the next IETF GROw meeting in > order to present an updated version (to be posted soon) of the following > draft: > > http://www.ietf.org/internet-drafts/draft-dubois-bgp-pm-reqs-01.txt You have 15 mins (10 mins for the presentation and 5 mins for questions and answers). > We also requested a slot in the GROw working group. We do not know if it is > better to present the draft in grow, in IDR or in both ? You should certainly present it in IDR. With respect to presenting it in GROW, I do not have an opinion on this. Yakov. > > Best regards, > > Nicolas, Bruno and Benoît > > Nicolas Dubois > Tel : 0144442817 > > > > > -----Message d'origine----- > > De : idr-bounces@ietf.org [mailto:idr-bounces@ietf.org] De la > > part de Yakov Rekhter > > Envoyé : lundi 20 juin 2005 15:41 > > À : idr@ietf.org > > Cc : skh@nexthop.com; yakov@juniper.net > > Objet : [Idr] IDR WG agenda > > > > Folks, > > > > Its about time to start thinking about agenda items for the > > next IETF. Please forward any IDR agenda items you might have > > to me and Sue. > > > > And if you plan to make a presentation, please also keep in > > mind the rule "no document - no time slot". > > > > Sue & Yakov. > > > > _______________________________________________ > > Idr mailing list > > Idr@ietf.org > > https://www1.ietf.org/mailman/listinfo/idr > _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id LAA26675 for <idr-archive@nic.merit.edu>; Tue, 12 Jul 2005 11:08:23 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DsM6e-0003Ov-Uu; Tue, 12 Jul 2005 10:51:32 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DsM6d-0003Oq-RQ for idr@megatron.ietf.org; Tue, 12 Jul 2005 10:51:32 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29821 for <idr@ietf.org>; Tue, 12 Jul 2005 10:51:29 -0400 (EDT) Received: from relais-inet.francetelecom.com ([212.234.67.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DsMYo-0007sI-Pq for idr@ietf.org; Tue, 12 Jul 2005 11:20:42 -0400 Received: from prive-Rline3.com ([192.168.1.32] [192.168.1.32]) by Rline3.francetelecom.com with ESMTP for idr@ietf.org; Tue, 12 Jul 2005 16:51:11 +0200 Received: from smtp2.smtpft.francetelecom.fr ([193.249.133.11] [193.249.133.11]) by Rline3.francetelecom.com with ESMTP for idr@ietf.org; Tue, 12 Jul 2005 16:51:11 +0200 Received: from FTBIEZ3ZCWRQWV ([10.158.49.235]) by smtp2.smtpft.francetelecom.fr (Netscape Messaging Server 4.15) with ESMTP id IJIRXB01.6F9; Tue, 12 Jul 2005 16:51:11 +0200 From: "DUBOIS Nicolas ROSI/DAS/ARI" <nicolas.dubois@francetelecom.com> To: "'Yakov Rekhter'" <yakov@juniper.net>, <idr@ietf.org> Subject: RE: [Idr] IDR WG agenda Date: Tue, 12 Jul 2005 16:51:17 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Mailer: Microsoft Office Outlook, Build 11.0.6353 Thread-Index: AcV1nf8XeESVbiCaSeGNV7dE55sGGgRUcpEQ X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 In-Reply-To: <200506201340.j5KDeqj73105@merlot.juniper.net> Message-Id: <IJIRXB01.6F9@smtp2.smtpft.francetelecom.fr> X-Spam-Score: 0.0 (/) X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa Cc: skh@nexthop.com, DECRAENE Bruno RD-CORE <bruno.decraene@francetelecom.com>, FONDEVIOLE Benoit RD-CORE <benoit.fondeviole@francetelecom.com> X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing <idr.ietf.org> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe> List-Archive: <http://www1.ietf.org/pipermail/idr> List-Post: <mailto:idr@ietf.org> List-Help: <mailto:idr-request@ietf.org?subject=help> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe> Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by nic.merit.edu id LAA26675 Hi Sue, Yakov, Would it be possible to have a 10 min slot at the next IETF GROw meeting in order to present an updated version (to be posted soon) of the following draft: http://www.ietf.org/internet-drafts/draft-dubois-bgp-pm-reqs-01.txt We also requested a slot in the GROw working group. We do not know if it is better to present the draft in grow, in IDR or in both ? Best regards, Nicolas, Bruno and Benoît Nicolas Dubois Tel : 0144442817 > -----Message d'origine----- > De : idr-bounces@ietf.org [mailto:idr-bounces@ietf.org] De la > part de Yakov Rekhter > Envoyé : lundi 20 juin 2005 15:41 > À : idr@ietf.org > Cc : skh@nexthop.com; yakov@juniper.net > Objet : [Idr] IDR WG agenda > > Folks, > > Its about time to start thinking about agenda items for the > next IETF. Please forward any IDR agenda items you might have > to me and Sue. > > And if you plan to make a presentation, please also keep in > mind the rule "no document - no time slot". > > Sue & Yakov. > > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://www1.ietf.org/mailman/listinfo/idr _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id LAA02247 for <idr-archive@nic.merit.edu>; Mon, 11 Jul 2005 11:00:48 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DrzhJ-0006jv-Ci; Mon, 11 Jul 2005 10:55:53 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DrzhH-0006jl-3h for idr@megatron.ietf.org; Mon, 11 Jul 2005 10:55:51 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17900 for <idr@ietf.org>; Mon, 11 Jul 2005 10:55:48 -0400 (EDT) Received: from colo-dns-ext2.juniper.net ([207.17.137.64]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ds09H-0002Tr-Dy for idr@ietf.org; Mon, 11 Jul 2005 11:24:48 -0400 Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext2.juniper.net (8.12.3/8.12.3) with ESMTP id j6BEtcBm051044 for <idr@ietf.org>; Mon, 11 Jul 2005 07:55:38 -0700 (PDT) (envelope-from yakov@juniper.net) Received: from juniper.net (sapphire.juniper.net [172.17.28.108]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id j6BEtcj52219 for <idr@ietf.org>; Mon, 11 Jul 2005 07:55:38 -0700 (PDT) (envelope-from yakov@juniper.net) Message-Id: <200507111455.j6BEtcj52219@merlot.juniper.net> To: idr@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <11857.1121093738.1@juniper.net> Date: Mon, 11 Jul 2005 07:55:38 -0700 From: Yakov Rekhter <yakov@juniper.net> X-Spam-Score: 0.0 (/) X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027 Subject: [Idr] revised draft draft-ietf-idr-bgp-ext-communities-09.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing <idr.ietf.org> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe> List-Archive: <http://www1.ietf.org/pipermail/idr> List-Post: <mailto:idr@ietf.org> List-Help: <mailto:idr-request@ietf.org?subject=help> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe> Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org Folks, The revised draft reflects the comments received from the IESG as well as the information from the implementation report. Yakov. ------- Forwarded Message Date: Wed, 06 Jul 2005 15:50:02 -0400 From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org cc: idr@ietf.org Subject: [Idr] I-D ACTION:draft-ietf-idr-bgp-ext-communities-09.txt - --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Inter-Domain Routing Working Group of the IETF . Title : BGP Extended Communities Attribute Author(s) : Y. Rekhter, et al. Filename : draft-ietf-idr-bgp-ext-communities-09.txt Pages : 12 Date : 2005-7-6 This document describes the "extended community" BGP-4 attribute. This attribute provides a mechanism for labeling information carried in BGP-4. These labels can be used to control the distribution of this information, or for other applications. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-idr-bgp-ext-communities-09.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 mess age. 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-idr-bgp-ext-communities-09.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-idr-bgp-ext-communities-09.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: <2005-7-6144618.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-idr-bgp-ext-communities-09.txt - --OtherAccess Content-Type: Message/External-body; name="draft-ietf-idr-bgp-ext-communities-09.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-7-6144618.I-D@ietf.org> - --OtherAccess-- - --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr - --NextPart-- ------- End of Forwarded Message _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id PAA19876 for <idr-archive@nic.merit.edu>; Wed, 6 Jul 2005 15:55:23 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DqFv9-0000A0-E1; Wed, 06 Jul 2005 15:50:59 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DqFuI-00080N-35; Wed, 06 Jul 2005 15:50:06 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10087; Wed, 6 Jul 2005 15:50:04 -0400 (EDT) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DqGLI-00086G-0d; Wed, 06 Jul 2005 16:18:01 -0400 Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1DqFuE-00088w-EL; Wed, 06 Jul 2005 15:50: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: <E1DqFuE-00088w-EL@newodin.ietf.org> Date: Wed, 06 Jul 2005 15:50:02 -0400 X-Spam-Score: 0.4 (/) X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6 Cc: idr@ietf.org Subject: [Idr] I-D ACTION:draft-ietf-idr-bgp-ext-communities-09.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing <idr.ietf.org> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe> List-Archive: <http://www1.ietf.org/pipermail/idr> List-Post: <mailto:idr@ietf.org> List-Help: <mailto:idr-request@ietf.org?subject=help> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe> Sender: idr-bounces@ietf.org Errors-To: idr-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 Inter-Domain Routing Working Group of the IETF. Title : BGP Extended Communities Attribute Author(s) : Y. Rekhter, et al. Filename : draft-ietf-idr-bgp-ext-communities-09.txt Pages : 12 Date : 2005-7-6 This document describes the "extended community" BGP-4 attribute. This attribute provides a mechanism for labeling information carried in BGP-4. These labels can be used to control the distribution of this information, or for other applications. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-idr-bgp-ext-communities-09.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-idr-bgp-ext-communities-09.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-idr-bgp-ext-communities-09.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: <2005-7-6144618.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-idr-bgp-ext-communities-09.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-idr-bgp-ext-communities-09.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-7-6144618.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr --NextPart-- Received: from crewstart.com ([61.80.195.109]) by nic.merit.edu (8.9.3/8.9.1) with SMTP id DAA00160 for <idr-archive@nic.merit.edu>; Mon, 4 Jul 2005 03:18:41 -0400 (EDT) Received: from smapxsmap.net (smap-net-bk.mr.outblaze.com [205.158.62.177]) by crewstart.com (Postfix) with ESMTP id 4E2C5D4930 for <idr-archive@nic.merit.edu>; Sun, 03 Jul 2005 21:20:17 -0500 From: "Whizzes H. Sighted" <opt@smapxsmap.net> To: Idr <idr-archive@nic.merit.edu> Subject: Cheapest and best OEM software here! Date: Sun, 03 Jul 2005 21:20:17 -0500 Message-ID: <110001c5803e$6c7a77c3$a24ee2b4@smapxsmap.net> MIME-Version: 1.0 Content-Type: text/html Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Virus-Scanned: Symantec AntiVirus Scan Engine <html> <body> Hello!<br> <strong><a href=3d"http://jezfks=2eprimaryfe=2einfo/?OxkTkzOwvTpu2CO">Mos= t popular software for you! Up to 70% discount on our site=2e<br> </a></strong> <p><strong>New software:</strong> <br> Corel Draw Graphics Suite 11 - $50 <br> MS Picture It Premium 9 - $50 <br> Premiere 6=2e5 - $80 <br> MS Money 2004 - $60 <br> LiveMotion 2=2e0 - $60 <br> MS Streets and Trips 2004 - $60 <br> Photoshop 7 - $60 <br> Windows 2000 Professional - $50 <br> Photoshop CS with ImageReady CS - $90 <br> Dreamweaver MX 2004 - $60 <br> MS Plus! XP - $50 <br> Windows 2000 Professional - $50 <br> Borland Delphi 7 Enterprise Edition (2CD) - $60 <br> MS SQL Server 2000 Enterprise Edition - $60 <br> Flash MX 2004 - $60 <br> GoLive CS - $60 <br> </p> <p><a href=3d"http://vfcd=2enightcapif=2einfo/?GpcLIXGonfhSquG"><strong>V= isit now!</strong></a></p> </body> </html>
- Re: [Idr] Re: Commentson draft-zhang-idr-bgp-enti… Tulip Rasputin
- Re: [Idr] Re: Commentson draft-zhang-idr-bgp-enti… Alvaro Retana
- Re: [Idr] Re: Commentsondraft-zhang-idr-bgp-entir… Zhang Renhai
- Re: [Idr] Re:Commentsondraft-zhang-idr-bgp-entire… Manav Bhatia