[Idr] Recommend Book on BGP
Jing Shen <jshen_cad@yahoo.com.cn> Fri, 30 September 2005 08:57 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ELGi7-00012R-Jb; Fri, 30 Sep 2005 04:57:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ELGi6-00012J-0U for idr@megatron.ietf.org; Fri, 30 Sep 2005 04:57:42 -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 EAA29682 for <idr@ietf.org>; Fri, 30 Sep 2005 04:57:40 -0400 (EDT)
Received: from web15408.mail.cnb.yahoo.com ([202.43.216.211]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1ELGps-0007xz-Q3 for idr@ietf.org; Fri, 30 Sep 2005 05:05:48 -0400
Received: (qmail 69043 invoked by uid 60001); 30 Sep 2005 08:57:14 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.cn; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=1pRYsuAic+MdH36KFFVAyf+dg5/xknC8ovsHHp0OlS0B1VLWvRnJ762tdCO4wLqtDRUmV81qlq2oWIk4KmhpS1mkslzne5xkj3SjhDzY1AaI1DbgHvO7WPSUijLKNo/yyKNFQy5rdn5ETv78LQr6kIZ2iRVOsF7fLDk9o6R0krA= ;
Message-ID: <20050930085714.69041.qmail@web15408.mail.cnb.yahoo.com>
Received: from [202.96.103.151] by web15408.mail.cnb.yahoo.com via HTTP; Fri, 30 Sep 2005 16:57:13 CST
Date: Fri, 30 Sep 2005 16:57:13 +0800
From: Jing Shen <jshen_cad@yahoo.com.cn>
To: idr@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="gb2312"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id EAA29682
Subject: [Idr] Recommend Book on BGP
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, I'm sorry if this is off-topic. Would anybody recommend some book on BGP? Someone recommend Halabi's book, but it seems focusing on operational area. Is there any book discussing how BGP is designed and implemented? thanks Joe shen ___________________________________________________________ ÑÅ»¢Ãâ·ÑGÓÊÏä£ÖйúµÚÒ»¾øÎÞÀ¬»øÓʼþɧÈų¬´óÓÊÏä http://cn.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 FAA21596 for <idr-archive@nic.merit.edu>; Fri, 30 Sep 2005 05:01:52 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ELGi7-00012R-Fn; Fri, 30 Sep 2005 04:57:43 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ELGi6-00012J-0U for idr@megatron.ietf.org; Fri, 30 Sep 2005 04:57:42 -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 EAA29682 for <idr@ietf.org>; Fri, 30 Sep 2005 04:57:40 -0400 (EDT) Received: from web15408.mail.cnb.yahoo.com ([202.43.216.211]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1ELGps-0007xz-Q3 for idr@ietf.org; Fri, 30 Sep 2005 05:05:48 -0400 Received: (qmail 69043 invoked by uid 60001); 30 Sep 2005 08:57:14 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.cn; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=1pRYsuAic+MdH36KFFVAyf+dg5/xknC8ovsHHp0OlS0B1VLWvRnJ762tdCO4wLqtDRUmV81qlq2oWIk4KmhpS1mkslzne5xkj3SjhDzY1AaI1DbgHvO7WPSUijLKNo/yyKNFQy5rdn5ETv78LQr6kIZ2iRVOsF7fLDk9o6R0krA= ; Message-ID: <20050930085714.69041.qmail@web15408.mail.cnb.yahoo.com> Received: from [202.96.103.151] by web15408.mail.cnb.yahoo.com via HTTP; Fri, 30 Sep 2005 16:57:13 CST Date: Fri, 30 Sep 2005 16:57:13 +0800 (CST) From: Jing Shen <jshen_cad@yahoo.com.cn> To: idr@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=gb2312 X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id EAA29682 Subject: [Idr] Recommend Book on BGP 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 FAA21596 Hi, I'm sorry if this is off-topic. Would anybody recommend some book on BGP? Someone recommend Halabi's book, but it seems focusing on operational area. Is there any book discussing how BGP is designed and implemented? thanks Joe shen ___________________________________________________________ ÑÅ»¢Ãâ·ÑGÓÊÏä£ÖйúµÚÒ»¾øÎÞÀ¬»øÓʼþɧÈų¬´óÓÊÏä http://cn.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 QAA14697 for <idr-archive@nic.merit.edu>; Wed, 28 Sep 2005 16:12:30 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EKhwk-0007V9-Ga; Wed, 28 Sep 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 1EKhwL-0007OU-G8; Wed, 28 Sep 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 PAA02862; Wed, 28 Sep 2005 15:50:03 -0400 (EDT) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EKi3p-0007wI-AD; Wed, 28 Sep 2005 15:57:49 -0400 Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1EKhwI-00013Y-3p; Wed, 28 Sep 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: <E1EKhwI-00013Y-3p@newodin.ietf.org> Date: Wed, 28 Sep 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-as4bytes-11.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-11.txt Pages : 9 Date : 2005-9-28 Currently the Autonomous System number is encoded in BGP [BGP] as a two-octet field. This document describes extensions to BGP to carry the Autonomous System number as a four-octet field. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-idr-as4bytes-11.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-11.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-11.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-9-28135146.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-idr-as4bytes-11.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-idr-as4bytes-11.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-9-28135146.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 RAA19423 for <idr-archive@nic.merit.edu>; Fri, 23 Sep 2005 17:31:25 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EIv5x-0003dT-Cj; Fri, 23 Sep 2005 17:28:37 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EIv5s-0003ci-Bz; Fri, 23 Sep 2005 17:28: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 RAA14268; Fri, 23 Sep 2005 17:28:30 -0400 (EDT) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EIvCO-0003PY-Dw; Fri, 23 Sep 2005 17:35:16 -0400 Received: from apache by newodin.ietf.org with local (Exim 4.43) id 1EIv5r-0004b9-P5; Fri, 23 Sep 2005 17:28:31 -0400 X-test-idtracker: no To: IETF-Announce <ietf-announce@ietf.org> From: The IESG <iesg-secretary@ietf.org> Message-Id: <E1EIv5r-0004b9-P5@newodin.ietf.org> Date: Fri, 23 Sep 2005 17:28:31 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Cc: idr@ietf.org Subject: [Idr] Last Call: 'Multiprotocol Extensions for BGP-4' to Draft Standard X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: iesg@ietf.org 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 received a request from the Inter-Domain Routing WG to consider the following document: - 'Multiprotocol Extensions for BGP-4 ' <draft-ietf-idr-rfc2858bis-07.txt> as a Draft Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by 2005-10-07. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-idr-rfc2858bis-07.txt The Implementation Report can be accessed at http://www.ietf.org/IESG/Implementations/mp-bgp-implementation-report.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 VAA24057 for <idr-archive@nic.merit.edu>; Mon, 19 Sep 2005 21:38: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 1EHX3M-0002L6-8d; Mon, 19 Sep 2005 21:36:12 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EHX3K-0002L1-N0 for idr@megatron.ietf.org; Mon, 19 Sep 2005 21:36:10 -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 VAA13409 for <idr@ietf.org>; Mon, 19 Sep 2005 21:36:08 -0400 (EDT) Received: from kahuna.telstra.net ([203.50.0.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EHX93-0004CQ-8O for idr@ietf.org; Mon, 19 Sep 2005 21:42:06 -0400 Received: from gihm3.apnic.net (rsdhcp28.telstra.net [203.50.0.220]) by kahuna.telstra.net (8.12.3/8.11.3) with ESMTP id j8K1YvXt030834; Tue, 20 Sep 2005 11:34:57 +1000 (EST) (envelope-from gih@apnic.net) Message-Id: <6.2.0.14.2.20050920112118.02ac5eb0@kahuna.telstra.net> X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14 Date: Tue, 20 Sep 2005 11:34:44 +1000 To: "Yakov Rekhter" <yakov@juniper.net>, skh@nexthop.com From: Geoff Huston <gih@apnic.net> In-Reply-To: <200509190230.j8J2UrWU079438@workhorse.faster-light.net> References: <Your message of "Sun, 18 Sep 2005 20:49:00 -0000." <BAY17-F114CDEFC5FE330308DC3EFA6930@phx.gbl> <200509190230.j8J2UrWU079438@workhorse.faster-light.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Spam-Score: 0.0 (/) X-Scan-Signature: cd3fc8e909678b38737fc606dec187f0 Cc: idr@ietf.org, Bruno Rijsman <brijsman@juniper.net> Subject: [Idr] draft-ietf-idr--as4bytes - Implementation Report 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, At the last IDR working group meeting I took the action to complete an implementation report on the 4-byte AS draft. The attached implementation report has been submitted as an internet draft (to be published as draft-huston-idr-as4bytes-survey-00.txt) My thanks to Bruno Rijsman, Enke Chen and Albert Tian for their kind assistance in assembling this report. regards, Geoff ---------------------------------------------------------------------------- 4-Byte AS Implementation Report September 2005 Abstract This document provides a survey of BGP-4 4-Byte AS Number support implementations. 1. Survey Summary This document provides a survey of BGP-4 4-Byte AS Number Support [ID.4ByteAS] implementations. After a brief summary, each response is listed. The editor makes no claim as to the accuracy of the information provided. 2. Summary Forms 2.1. Juniper Networks Organization: Juniper Networks Person filling out this form: Bruno Rijsman <brijsman@juniper.net> Implementation: JUNOSe 4-1-0 and later Does the implementation include all parts of the specification: Yes Are there parts of the specification that are unclear where the implementor had to exercise some judgement that may impact interoperability? * It isn't clear what to do if the information in the old as-path is inconsistent with the information in the new as-path. * There some places where AS numbers are used where it wasn't clear how to deal with 4-octet as-numbers (e.g. extended communities). * It isn't spelled out that this capability cannot be dynamically negotiated. Has there been any interoperability testing? Yes; no problems were discovered. 1. NEW / OLD ineroperability testing with: Juniper ERX (older version which does not support draft) Juniper M/T/J Cisco 7500 2. NEW / NEW interoperability testing with: Juniper M/T/J Redback SmartEdge 3. Most deployed Juniper ERX routers run code which supports 4-octet AS-numbers (and the feature is enabled by default). This provides some confidence that the draft does not cause interoperability problems. Note however that the NEW_AS_PATH attribute is not generated unless the AS-path contains at least one AS-number greater than 65535 which is -as far as we know- not yet the case in the Internet today. Has there been testing of the interface between this implementation and the 2-byte BGP implementation on the NEW (4-byte) to OLD (2byte) update path? Yes Has there been testing of the OLD (2-byte) to NEW (4-byte) path? Yes Have there been any issues noted with the mechanism to reconstruct the 4-byte AS path from the NEW_AS-PATH attribute and the 2-byte AS Path on an OLD -NEW BGP update session? It isn't clear what to do if the information in the old as-path is inconsistent with the information in the new as-path. Any other comments regarding the implementation Some older versions of Cisco IOS send an unsupported capability notification (instead of ignoring the capability) when they receive a capability advertisement which they don't recognize and which has non-empty data. The 4-octet as-number capability is such a capability. Our implementation recognizes this notification and stops automatically stops advertising the 4-octet as-numbers capability (and others) until the next hard clear on the BGP session. 2.2. Redback Organization: Redback Person filling out this form: Albert Tian <tian@redback.com> Does the implementation include all parts of the specification: Yes Are there parts of the specification that are unclear where the implementor had to exercise some judgement that may impact interoperability? No. Has there been any interoperability testing? Yes Has there been testing of the interface between this implementation and the 2-byte BGP implementation on the NEW (4-byte) to OLD (2byte) update path? Yes (Cisco: 2-byte; Redback: 4 byte). Has there been testing of the OLD (2-byte) to NEW (4-byte) path? Yes. (Cisco: 2-byte; Redback: 4-byte). Have there been any issues noted with the mechanism to reconstruct the 4-byte AS path from the NEW_AS-PATH attribute and the 2-byte AS Path on an OLD -NEW BGP update session? No Have there been any issues noted with the mechanism to reconstruct the 4-byte AS path from the NEW_AS-PATH attribute and the 2-byte AS Path on an OLD -> NEW BGP update session? No. Any other comments regarding the implementation No References [ID.4ByteAS] Vohra, Q. and E. Chen, "BGP support for four-octet AS number space", Work in progress, Internet Draft: draft-ietf-idr-as4bytes-10.txt, July 2005. Author Geoff Huston Asia Pacific Network Information Centre Email: gih@apnic.net URI: http://www.apnic.net _______________________________________________ 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 WAA00767 for <idr-archive@nic.merit.edu>; Sun, 18 Sep 2005 22:33:17 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EHBQc-0001qm-6Q; Sun, 18 Sep 2005 22:30:46 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EHBQa-0001qh-OO for idr@megatron.ietf.org; Sun, 18 Sep 2005 22:30: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 WAA09758 for <idr@ietf.org>; Sun, 18 Sep 2005 22:30:42 -0400 (EDT) Received: from relay01.pair.com ([209.68.5.15]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1EHBW7-0000NL-16 for idr@ietf.org; Sun, 18 Sep 2005 22:36:28 -0400 Received: (qmail 7420 invoked from network); 19 Sep 2005 02:30:35 -0000 Received: from unknown (HELO workhorse.faster-light.net) (unknown) by unknown with SMTP; 19 Sep 2005 02:30:35 -0000 X-pair-Authenticated: 69.37.59.162 Received: from workhorse.faster-light.net (localhost.faster-light.net [127.0.0.1]) by workhorse.faster-light.net (8.12.11/8.12.11) with ESMTP id j8J2UrWU079438; Sun, 18 Sep 2005 22:30:53 -0400 (EDT) (envelope-from curtis@workhorse.faster-light.net) Message-Id: <200509190230.j8J2UrWU079438@workhorse.faster-light.net> To: "john smith" <johnsmith0302@hotmail.com> Subject: Re: [Idr] Re: 4-Byte As Number soon to come? In-reply-to: Your message of "Sun, 18 Sep 2005 20:49:00 -0000." <BAY17-F114CDEFC5FE330308DC3EFA6930@phx.gbl> Date: Sun, 18 Sep 2005 22:30:52 -0400 From: Curtis Villamizar <curtis@faster-light.net> X-Spam-Score: 0.0 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Cc: joel@stevecrocker.com, idr@ietf.org X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: curtis@faster-light.net 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 In message <BAY17-F114CDEFC5FE330308DC3EFA6930@phx.gbl> "john smith" writes: > > Yes possibly i did, > > i think it would help if someone could help clarify when exactly > local_pref came into the picture. Day one. local_pref appeared in the internet-draft that was the basis for the first versions of BGP4 from Cisco deployed in late fall of 1993 and the gated version deployed in the NSFHET in 1994. That internet-draft predated rfc1771. local_pref has always been in rfc1771 as well. > I was wondering if the authors could help clarify the motivation of > retaining path length. If what you mean by "retaining path length" means using AS path length in the decision process, this was to match widespread implementation and deployment. But I already said that a few messages back on this thread. Curtis _______________________________________________ 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 TAA27416 for <idr-archive@nic.merit.edu>; Sun, 18 Sep 2005 19:07: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 1EH8E6-0007F5-AA; Sun, 18 Sep 2005 19:05:38 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EH8E4-0007Eu-Qr for idr@megatron.ietf.org; Sun, 18 Sep 2005 19:05:37 -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 TAA01403 for <idr@ietf.org>; Sun, 18 Sep 2005 19:05:34 -0400 (EDT) Received: from [207.152.136.138] (helo=EXECDSL.COM) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EH8JZ-0004kI-Cs for idr@ietf.org; Sun, 18 Sep 2005 19:11:18 -0400 Received: from [162.83.99.86] (HELO JMHLap3.stevecrocker.com) by EXECDSL.COM (CommuniGate Pro SMTP 3.3) with ESMTP id 12518472; Sun, 18 Sep 2005 19:05:28 -0400 Message-Id: <6.2.1.2.0.20050918185734.02d78d70@localhost> X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2 Date: Sun, 18 Sep 2005 19:05:23 -0400 To: "john smith" <johnsmith0302@hotmail.com> From: "Joel M. Halpern" <joel@stevecrocker.com> Subject: Re: [Idr] Re: 4-Byte As Number soon to come? In-Reply-To: <BAY17-F114CDEFC5FE330308DC3EFA6930@phx.gbl> References: <200509101607.j8AG7oHm043388@workhorse.faster-light.net> <BAY17-F114CDEFC5FE330308DC3EFA6930@phx.gbl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 1.2 (+) X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c 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 There are a set of decision items laid out in the I-D that will be the new BGP RFC. These include, under certain circumstances, comparing the number of elements in the AS path. If we had and were using the metric that was recently proposed, this would not be an issue. Specifically, in section 9.1.2.2 if multiple routes have gotten this far then "Remove from consideration all routes which are not tied for having the smallest number of AS numbers present in the AS Path attributes. Note that when counting this number, an AS_Set counts as 1, no matter how many ASs are in the set." Given that the number of ASs (seqeunce elements or sets) can have a direct effect on the selection of routes, we don't want to break that criteria while allowing a router to use multiple routes. And when such a router speaks to a non-ECMP router, we want the number of AS (as described above) to be the same as it would have had if ECMP had not been used. Note that this text does not say to collapse adjacent AS Sets, but rather that each AS set counts as one AS for comparison purposes. Yours, Joel M. Halpern At 04:49 PM 9/18/2005, john smith wrote: >Yes possibly i did, > >i think it would help if someone could help clarify when exactly >local_pref came into the picture. > >I was wondering if the authors could help clarify the motivation of >retaining path length. > > >>From: Curtis Villamizar <curtis@faster-light.net> >>Reply-To: curtis@faster-light.net >>To: "john smith" <johnsmith0302@hotmail.com> >>CC: joel@stevecrocker.com, idr@ietf.org >>Subject: Re: [Idr] Re: 4-Byte As Number soon to come? Date: Sat, 10 Sep >>2005 12:07:50 -0400 >> >>In message <BAY17-F13F4246383EE8F1CE29A67A69B0@phx.gbl> >>"john smith" writes: >> > >> > > >> > >It was precisely to avoid such misleading effects that we introduced the >> > >series of AS Sets. >> > > >> > >> > then perhaps one of the authors would like to explain the arguments in >> this: >> > >> > http://www.merit.edu/mail.archives/idr/2004-09/msg00023.html >> > >> > :-) >> >> >>That message was about weights and local-pref. It appears to have >>nothing to do with AS Sets. Is it possible you got the URL wrong? >> >>Curtis > >_________________________________________________________________ >Don't just search. Find. Check out the new MSN Search! http://search.msn.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 MAA09039 for <idr-archive@nic.merit.edu>; Sat, 10 Sep 2005 12:07:07 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EE7rr-0005ps-92; Sat, 10 Sep 2005 12:06:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EE7rn-0005pT-Af for idr@megatron.ietf.org; Sat, 10 Sep 2005 12:06:13 -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 MAA08101 for <idr@ietf.org>; Sat, 10 Sep 2005 12:05:58 -0400 (EDT) Received: from relay00.pair.com ([209.68.1.20] helo=relay.pair.com) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1EE7vR-0001W6-0V for idr@ietf.org; Sat, 10 Sep 2005 12:09:58 -0400 Received: (qmail 49361 invoked from network); 10 Sep 2005 16:05:48 -0000 Received: from unknown (HELO workhorse.faster-light.net) (unknown) by unknown with SMTP; 10 Sep 2005 16:05:48 -0000 X-pair-Authenticated: 69.37.59.162 Received: from workhorse.faster-light.net (localhost.faster-light.net [127.0.0.1]) by workhorse.faster-light.net (8.12.11/8.12.11) with ESMTP id j8AG7oHm043388; Sat, 10 Sep 2005 12:07:50 -0400 (EDT) (envelope-from curtis@workhorse.faster-light.net) Message-Id: <200509101607.j8AG7oHm043388@workhorse.faster-light.net> To: "john smith" <johnsmith0302@hotmail.com> Subject: Re: [Idr] Re: 4-Byte As Number soon to come? In-reply-to: Your message of "Sat, 10 Sep 2005 11:09:52 -0000." <BAY17-F13F4246383EE8F1CE29A67A69B0@phx.gbl> Date: Sat, 10 Sep 2005 12:07:50 -0400 From: Curtis Villamizar <curtis@faster-light.net> X-Spam-Score: 0.0 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Cc: joel@stevecrocker.com, idr@ietf.org X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: curtis@faster-light.net 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 In message <BAY17-F13F4246383EE8F1CE29A67A69B0@phx.gbl> "john smith" writes: > > > > >It was precisely to avoid such misleading effects that we introduced the > >series of AS Sets. > > > > then perhaps one of the authors would like to explain the arguments in this: > > http://www.merit.edu/mail.archives/idr/2004-09/msg00023.html > > :-) That message was about weights and local-pref. It appears to have nothing to do with AS Sets. Is it possible you got the URL wrong? Curtis _______________________________________________ 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 HAA06563 for <idr-archive@nic.merit.edu>; Sat, 10 Sep 2005 07:13:40 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EE3FS-0001Zg-Db; Sat, 10 Sep 2005 07:10:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EE3FQ-0001ZC-SM for idr@megatron.ietf.org; Sat, 10 Sep 2005 07:10:16 -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 HAA27706 for <idr@ietf.org>; Sat, 10 Sep 2005 07:10:05 -0400 (EDT) Received: from bay17-f13.bay17.hotmail.com ([64.4.43.63] helo=hotmail.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EE3J1-0004Ez-QH for idr@ietf.org; Sat, 10 Sep 2005 07:14:03 -0400 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sat, 10 Sep 2005 04:09:52 -0700 Message-ID: <BAY17-F13F4246383EE8F1CE29A67A69B0@phx.gbl> Received: from 66.17.149.13 by by17fd.bay17.hotmail.msn.com with HTTP; Sat, 10 Sep 2005 11:09:52 GMT X-Originating-IP: [66.17.149.13] X-Originating-Email: [johnsmith0302@hotmail.com] X-Sender: johnsmith0302@hotmail.com In-Reply-To: <6.2.1.2.0.20050831230250.02ee26b0@localhost> From: "john smith" <johnsmith0302@hotmail.com> To: joel@stevecrocker.com Subject: Re: [Idr] Re: 4-Byte As Number soon to come? Date: Sat, 10 Sep 2005 11:09:52 +0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-OriginalArrivalTime: 10 Sep 2005 11:09:52.0624 (UTC) FILETIME=[2AE73700:01C5B5F8] X-Spam-Score: 4.5 (++++) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c 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 > >It was precisely to avoid such misleading effects that we introduced the >series of AS Sets. > then perhaps one of the authors would like to explain the arguments in this: http://www.merit.edu/mail.archives/idr/2004-09/msg00023.html :-) _________________________________________________________________ FREE pop-up blocking with the new MSN Toolbar - get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ _______________________________________________ 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 WAA01730 for <idr-archive@nic.merit.edu>; Fri, 9 Sep 2005 22:45: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 1EDvKK-0001Qd-Ac; Fri, 09 Sep 2005 22:42:48 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EDvKI-0001QY-SY for idr@megatron.ietf.org; Fri, 09 Sep 2005 22:42:47 -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 WAA29073 for <idr@ietf.org>; Fri, 9 Sep 2005 22:42:42 -0400 (EDT) Received: from zproxy.gmail.com ([64.233.162.203]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EDvNy-0001z1-Cb for idr@ietf.org; Fri, 09 Sep 2005 22:46:34 -0400 Received: by zproxy.gmail.com with SMTP id i1so1454156nzh for <idr@ietf.org>; Fri, 09 Sep 2005 19:42:33 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s¾ta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references; b=tJ69RKLO9/uNK7lCjLApxJ5Sk2xIc91a7y6PMVxKgqKkhAvqQyg8lNF12n4E5ODKdDsk33LHHWhaDqJtkgnStq3ZblZPt50yVryzdBQf+edQsU7CEwTvGJ0vQbCYDK247Z32HHlBEgt83Gre6R9V+r7yikeTAtj04cEBNg2lGhkReceived: by 10.36.126.3 with SMTP id y3mr951727nzc; Fri, 09 Sep 2005 19:42:33 -0700 (PDT) Received: by 10.36.119.9 with HTTP; Fri, 9 Sep 2005 19:42:33 -0700 (PDT) Message-ID: <92c95031050909194225c9cab7@mail.gmail.com> Date: Sat, 10 Sep 2005 08:12:33 +0530 From: Glen Kent <glen.kent@gmail.com> To: curtis@faster-light.net Subject: Re: [Idr] Re: 4-Byte As Number soon to come? In-Reply-To: <200509091643.j89GhuYk006254@workhorse.faster-light.net> Mime-Version: 1.0 References: <92c9503105090710251e1fc602@mail.gmail.com> <200509091643.j89GhuYk006254@workhorse.faster-light.net> X-Spam-Score: 0.0 (/) X-Scan-Signature: f66b12316365a3fe519e75911daf28a8 Cc: idr@ietf.org X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: glen.kent@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="=======85384305=" Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org --=======85384305= Content-Type: multipart/alternative; boundary="----=_Part_6676_4516227.1126320153688" ------=_Part_6676_4516227.1126320153688 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Curtis wrote: RFC 1771 does not have this tie breaking rule. The rule did not exist > at all therefore it also didn't say how to count an AS_SET. Yes. There has always been clear concensus that we add this to match > reality. > > Counting all the AS in an AS_SET rather than just counting the set has > always been considered to be "a bug" in implementations that do that. Isnt this *exactly* what *everybody* in this list is saying? Particularly the author(s) to whom you replied? I am amused as well curious now. Which email in this *entire* thread makes you think that the author thinks otherwise? Which is why, when you merge the SETs, you _can_ break what other people think from the path length. Decreasing the path length midway (by merging AS_SETs) IMO is a bad practise and nobody has any business doing this. And note, before anybody sparks a reply, I am not talking about a router thats doing aggregation, because that router is essentially originating a new prefix. I (like others) am talking of router that sits in the middle and suddenly decides to merge all the SETs to form one big SET before passing on the routes to its peer. Thanks -- Glen ------=_Part_6676_4516227.1126320153688 Content-Type: text/html; charset=ISO-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable <div>Curtis wrote:</div> <div><br> </div> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">RFC 1771 does not have this tie breaking rule. The rule did not exist<br>at all therefore it also didn't say how to count an AS_SET. </blockquote> <div> </div> <div>Yes.</div> <div><br> </div> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">There has always been clear concensus that we add this to match<br>reality.<br><br>Counting all the AS in an AS_SET rather than just counting the set has <br>always been considered to be "a bug" in implementations that do that.</blockquote> <div> </div> <div>Isnt this *exactly* what *everybody* in this list is saying? Particularly the author(s) to whom you replied?</div> <div> </div> <div>I am amused as well curious now. Which email in this *entire* thread makes you think that the author thinks otherwise?</div> <div> </div> <div>Which is why, when you merge the SETs, you _can_ break what other people think from the path length. Decreasing the path length midway (by merging AS_SETs) IMO is a bad practise and nobody has any business doing this. </div> <div> </div> <div>And note, before anybody sparks a reply, I am not talking about a router thats doing aggregation, because that router is essentially originating a new prefix. I (like others) am talking of router that sits in the middle and suddenly decides to merge all the SETs to form one big SET before passing on the routes to its peer. </div> <div> </div> <div>Thanks</div> <div> </div> <div>-- </div> <div>Glen</div> <div> </div> ------=_Part_6676_4516227.1126320153688-- --=======85384305= 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 --=======85384305=-- 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 MAA26491 for <idr-archive@nic.merit.edu>; Fri, 9 Sep 2005 12:44: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 1EDly2-00054s-Tk; Fri, 09 Sep 2005 12:43:11 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EDly1-00054O-Ax for idr@megatron.ietf.org; Fri, 09 Sep 2005 12:43:09 -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 MAA13365 for <idr@ietf.org>; Fri, 9 Sep 2005 12:43:06 -0400 (EDT) Received: from relay03.pair.com ([209.68.5.17]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1EDm1c-00075C-Cb for idr@ietf.org; Fri, 09 Sep 2005 12:46:53 -0400 Received: (qmail 10971 invoked from network); 9 Sep 2005 16:41:41 -0000 Received: from unknown (HELO workhorse.faster-light.net) (unknown) by unknown with SMTP; 9 Sep 2005 16:41:41 -0000 X-pair-Authenticated: 69.37.59.162 Received: from workhorse.faster-light.net (localhost.faster-light.net [127.0.0.1]) by workhorse.faster-light.net (8.12.11/8.12.11) with ESMTP id j89GhuYk006254; Fri, 9 Sep 2005 12:43:56 -0400 (EDT) (envelope-from curtis@workhorse.faster-light.net) Message-Id: <200509091643.j89GhuYk006254@workhorse.faster-light.net> To: glen.kent@gmail.com Subject: Re: [Idr] Re: 4-Byte As Number soon to come? In-reply-to: Your message of "Wed, 07 Sep 2005 22:55:45 +0530." <92c9503105090710251e1fc602@mail.gmail.com> Date: Fri, 09 Sep 2005 12:43:56 -0400 From: Curtis Villamizar <curtis@faster-light.net> X-Spam-Score: 0.0 (/) X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69 Cc: "Joel M. Halpern" <joel@stevecrocker.com>, idr@ietf.org X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: curtis@faster-light.net 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 In message <92c9503105090710251e1fc602@mail.gmail.com> Glen Kent writes: > > > On 9/2/05, Curtis Villamizar <curtis@faster-light.net> wrote: > > > > > Joel, > > > > If memory serves me, AS-SETs were introduced for aggregation and AS > > Path length wasn't in use yet. Cisco put AS Path length into their > > implementation after rfc1771 and it became widely implemented even > > though it differred from the spec. So we fixed the spec to match > > running code, operational experience, and widespread deployment. > > > Curtis, > What exactly was fixed in the spec to match the "running code, operational> > experience, and widespread deployment" ? > Is it, allowing the BGP speaker to collapse multiple AS_SETs, or is it > counting multiple AS_SETs as 1? I dont think there is any running code that> > does any of the above. > Are you sure we're not trying to "fix" something that aint yet broken? > Glen In "9.1.2.2 Breaking Ties (Phase 2)" the following was added. a) Remove from consideration all routes which are not tied for having the smallest number of AS numbers present in their AS_PATH attributes. Note, that when counting this number, an AS_SET counts as 1, no matter how many ASs are in the set. RFC 1771 does not have this tie breaking rule. The rule did not exist at all therefore it also didn't say how to count an AS_SET. There has always been clear concensus that we add this to match reality. Counting all the AS in an AS_SET rather than just counting the set has always been considered to be "a bug" in implementations that do that. Curtis _______________________________________________ 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 HAA10135 for <idr-archive@nic.merit.edu>; Thu, 8 Sep 2005 07:02:10 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EDK7b-0002NP-CO; Thu, 08 Sep 2005 06:59:11 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EDK7a-0002NK-43 for idr@megatron.ietf.org; Thu, 08 Sep 2005 06:59:10 -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 GAA12403 for <idr@ietf.org>; Thu, 8 Sep 2005 06:59:06 -0400 (EDT) Received: from ppp124-190.pppcal.vsnl.net.in ([203.197.124.190] helo=alumnux.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EDKAu-0008LX-7X for idr@ietf.org; Thu, 08 Sep 2005 07:02:38 -0400 Received: from 3d ([192.168.10.237]) by alumnux.com (8.9.3/8.9.3) with SMTP id QAA00942 for <idr@ietf.org>; Thu, 8 Sep 2005 16:45:23 +0530 Message-ID: <009701c5b464$1a712880$ed0aa8c0@3d> From: "Debdas Dey" <debdas@alumnux.com> To: <idr@ietf.org> Date: Thu, 8 Sep 2005 16:27:28 +0530 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4927.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200 X-Spam-Score: 3.4 (+++) X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6 Subject: [Idr] Idr] : 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="=======11235652=" Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org This is a multi-part message in MIME format. --=======11235652= Content-Type: multipart/alternative; boundary="----=_NextPart_000_0094_01C5B492.341651B0" This is a multi-part message in MIME format. ------=_NextPart_000_0094_01C5B492.341651B0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi All, I am a new member of this group. Can anybody please suggest about the software versions in Cisco (IOS) and Juniper (JUNOS) which implements following two drafts: 1. draft-ietf-idr-bgp-ext-communities-09.txt 2. draft-ietf-idr-dynamic-cap-07.txt Thanks and regards, debdas ================================== Debdas Dey Alumnus Software Ltd (www.alumnux.com) Infinity, Tower-II, 2nd Floor, Plot A3, Block GP, Sector V Salt Lake City Kolkata 700091 India Phone : +91-33-23575626, +91-33-23575627, +91-33-23575628 extn : 318 Fax : +91-33-23575268 ------=_NextPart_000_0094_01C5B492.341651B0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META content="text/html; charset=iso-8859-1" http-equiv=Content-Type> <META content="MSHTML 5.00.3700.6699" name=GENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=#ffffff> <DIV><FONT face=Arial size=2>Hi All,</FONT></DIV> <DIV> </DIV> <DIV><FONT face=Arial size=2>I am a new member of this group.</FONT></DIV> <DIV> </DIV> <DIV><FONT face=Arial size=2>Can anybody please suggest about the software versions in Cisco (IOS) and Juniper (JUNOS) which implements following two drafts:</FONT></DIV> <DIV> </DIV> <DIV><FONT face=Arial size=2> 1. draft-ietf-idr-bgp-ext-communities-09.txt</FONT></DIV> <DIV><FONT face=Arial size=2> 2. draft-ietf-idr-dynamic-cap-07.txt</FONT></DIV> <DIV> </DIV> <DIV> </DIV> <DIV><FONT face=Arial size=2>Thanks and regards,</FONT></DIV> <DIV><FONT face=Arial size=2>debdas</FONT></DIV> <DIV><FONT face=Arial size=2><BR>==================================<BR>Debdas Dey<BR>Alumnus Software Ltd (<A href="http://www.alumnux.com">www.alumnux.com</A>)<BR>Infinity, Tower-II, 2nd Floor,<BR>Plot A3, Block GP, Sector V<BR>Salt Lake City<BR>Kolkata 700091<BR>India<BR>Phone : +91-33-23575626, +91-33-23575627, +91-33-23575628<BR> extn : 318<BR>Fax : +91-33-23575268</FONT></DIV> <DIV> </DIV></BODY></HTML> ------=_NextPart_000_0094_01C5B492.341651B0-- --=======11235652= 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 --=======11235652=-- 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 NAA00340 for <idr-archive@nic.merit.edu>; Wed, 7 Sep 2005 13:28: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 1ED3gO-00082K-G5; Wed, 07 Sep 2005 13:26:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ED3gK-000825-V6 for idr@megatron.ietf.org; Wed, 07 Sep 2005 13:25:59 -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 NAA04053 for <idr@ietf.org>; Wed, 7 Sep 2005 13:25:54 -0400 (EDT) Received: from zproxy.gmail.com ([64.233.162.203]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ED3jX-0004Xz-6E for idr@ietf.org; Wed, 07 Sep 2005 13:29:16 -0400 Received: by zproxy.gmail.com with SMTP id i1so1024122nzh for <idr@ietf.org>; Wed, 07 Sep 2005 10:25:46 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s¾ta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references; b=dsyQKLD+EbSb5zc0+Q5OsBgg48vSi8c+LTXZSoQoGlC7FmmO9qSvAp0IZWrk4U4T1afKmrOho+QsBcK+Zs/BWFLPMmi+w72SwxkTtj6x72RadPdsyE0KyObBD+V4irRb3C7kuDn2AKYALdLT5uFLQdE/zC1wu4FmQ+ehuxJXdzIReceived: by 10.36.115.9 with SMTP id n9mr135519nzc; Wed, 07 Sep 2005 10:25:45 -0700 (PDT) Received: by 10.36.119.9 with HTTP; Wed, 7 Sep 2005 10:25:45 -0700 (PDT) Message-ID: <92c9503105090710251e1fc602@mail.gmail.com> Date: Wed, 7 Sep 2005 22:55:45 +0530 From: Glen Kent <glen.kent@gmail.com> To: curtis@faster-light.net Subject: Re: [Idr] Re: 4-Byte As Number soon to come? In-Reply-To: <200509011901.j81J1opP070240@workhorse.faster-light.net> Mime-Version: 1.0 References: <6.2.1.2.0.20050831230250.02ee26b0@localhost> <200509011901.j81J1opP070240@workhorse.faster-light.net> X-Spam-Score: 0.5 (/) X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab Cc: "Joel M. Halpern" <joel@stevecrocker.com>, idr@ietf.org X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: glen.kent@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="=======18498199=" Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org --=======18498199= Content-Type: multipart/alternative; boundary="----=_Part_21868_1342093.1126113945586" ------=_Part_21868_1342093.1126113945586 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 9/2/05, Curtis Villamizar <curtis@faster-light.net> wrote: > > Joel, > > If memory serves me, AS-SETs were introduced for aggregation and AS > Path length wasn't in use yet. Cisco put AS Path length into their > implementation after rfc1771 and it became widely implemented even > though it differred from the spec. So we fixed the spec to match > running code, operational experience, and widespread deployment. > Curtis, What exactly was fixed in the spec to match the "running code, operational experience, and widespread deployment" ? Is it, allowing the BGP speaker to collapse multiple AS_SETs, or is it counting multiple AS_SETs as 1? I dont think there is any running code that does any of the above. Are you sure we're not trying to "fix" something that aint yet broken? Glen ------=_Part_21868_1342093.1126113945586 Content-Type: text/html; charset=ISO-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable <br> <div><span class="gmail_quote">On 9/2/05, <b class="gmail_sendername">Curtis Villamizar</b> <<a href="mailto:curtis@faster-light.net">curtis@faster-light.net</a>> wrote:</span></div> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br>Joel,<br><br>If memory serves me, AS-SETs were introduced for aggregation and AS<br>Path length wasn't in use yet. Cisco put AS Path length into their <br>implementation after rfc1771 and it became widely implemented even<br>though it differred from the spec. So we fixed the spec to match<br>running code, operational experience, and widespread deployment.<br></blockquote> <div>Curtis,</div> <div> </div> <div>What exactly was fixed in the spec to match the "running code, operational experience, and widespread deployment" ?</div> <div>Is it, allowing the BGP speaker to collapse multiple AS_SETs, or is it counting multiple AS_SETs as 1? I dont think there is any running code that does any of the above. </div> <div> </div> <div>Are you sure we're not trying to "fix" something that aint yet broken?</div> <div> </div> <div>Glen</div> ------=_Part_21868_1342093.1126113945586-- --=======18498199= 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 --=======18498199=-- 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 GAA26815 for <idr-archive@nic.merit.edu>; Wed, 7 Sep 2005 06:53:10 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ECxXW-00088q-1r; Wed, 07 Sep 2005 06:52:26 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ECxXU-00088h-UC for idr@megatron.ietf.org; Wed, 07 Sep 2005 06:52: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 GAA09607 for <idr@ietf.org>; Wed, 7 Sep 2005 06:52:22 -0400 (EDT) Received: from gateout01.mbox.net ([165.212.64.21] helo=gwo1.mbox.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ECxad-000109-H1 for idr@ietf.org; Wed, 07 Sep 2005 06:55:41 -0400 Received: from gateout01.mbox.net (gateout01.mbox.net [165.212.64.21]) by gwo1.mbox.net (Postfix) with SMTP id 658F712D1B3; Wed, 7 Sep 2005 10:52:09 +0000 (GMT) Received: from gateout01.mbox.net [127.0.0.1] by gateout01.mbox.net via mtad (C8.MAIN.3.25R) with ESMTP id 378Jigk1H0064Mo1; Wed, 07 Sep 2005 10:52:07 GMT Received: from gateout01.mbox.net [127.0.0.1] by gateout01.mbox.net via mtad (C8.MAIN.3.25R) with ESMTP id 376Jigk1F0113Mo1; Wed, 07 Sep 2005 10:52:06 GMT X-USANET-Routed: 2 gwsout-vs R:localhost:1825 Received: from gw4.EXCHPROD.USA.NET [165.212.116.254] by gateout01.mbox.net via smtad (C8.MAIN.3.21U); Wed, 07 Sep 2005 10:52:06 GMT X-USANET-Source: 165.212.116.254 IN skh@nexthop.com gw4.EXCHPROD.USA.NET X-USANET-MsgId: XID072Jigk1g9618Xo1 Received: from VS4.EXCHPROD.USA.NET ([10.116.208.141]) by gw4.EXCHPROD.USA.NET with Microsoft SMTPSVC(6.0.3790.211); Wed, 7 Sep 2005 04:52:05 -0600 X-MimeOLE: Produced By Microsoft Exchange V6.5.7232.53 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 7 Sep 2005 04:52:04 -0600 Message-ID: <6F44D7F6B24A8F4DA0AB46C9BE924F020104299D@VS4.EXCHPROD.USA.NET> Thread-Topic: 2 week Last call on draft-ietf-l3vpn-ospf-2547-04.txt thread-index: AcWzmXWyDyXvfvAvQv6Xa5i8Ru3TDAAAKjcw From: "Susan Hares" <skh@nexthop.com> To: <idr@ietf.org> X-OriginalArrivalTime: 07 Sep 2005 10:52:05.0689 (UTC) FILETIME=[2FB89A90:01C5B39A] X-Spam-Score: 0.2 (/) X-Scan-Signature: 182294e3fdac3aef093c0503b87ed133 Cc: zinin@psg.com, yakov@juniper.net Subject: [Idr] FW: 2 week Last call on draft-ietf-l3vpn-ospf-2547-04.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> Content-Type: multipart/mixed; boundary="=======10259821=" Sender: idr-bounces@ietf.org Errors-To: idr-bounces@ietf.org This is a multi-part message in MIME format. --=======10259821= Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C5B39A.2F7E0160" This is a multi-part message in MIME format. ------_=_NextPart_001_01C5B39A.2F7E0160 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Resending to get around mailer limit on copies. ________________________________ From: Susan Hares Sent: Wednesday, September 07, 2005 6:47 AM To: 'idr@ietf.org' Cc: 'yakov@juniper.net'; 'zinin@psg.com'; 'acee@cisco.com'; 'rohit@utstar.com'; 'zinin@psg.com'; 'townsley@cisco.com'; 'rick@rhwilder.net'; 'rbonica@juniper.net'; 'rcallon@juniper.net'; 'erosen@cisco.com' Subject: 2 week Last call on draft-ietf-l3vpn-ospf-2547-04.txt This begins working group last call on draft-ietf-l3vpn-ospf-2547-04. This last call is limited to the changes that Eric has made to the document (which are outlined in Eric's email below). The last call will end in two weeks (September 21st). Please send any comments to the working group mailing list. Thank-you, Susan Hares and Yakov Rekhter (co-chairs, IDR) At 11:45 AM 8/29/2005 -0400, Eric Rosen wrote: ================================================= > As a result of AD review, significant changes have been made > to the specification draft-ietf-l3vpn-ospf-2547. These changes can be > seen in the latest version, draft -04. It is believed that the draft now > corresponds to the implementations. > > The following issues were addressed as a result of the AD review. > > The spec was written so as to allow a single VRF to correspond to multiple > OSPF domains. However, it did not make clear just which > parameters and procedures are relative to a domain, and which are relative to a VRF. > This has now been cleared up. However, doing so required extensive > textual changes. > > There are cases where BGP decides to put a route into the > VRF for a particular address prefix, and OSPF also decides to put a route into > the VRF for that same address prefix. Of course, only one of these can > actually be used for forwarding. The original spec did not make it > adequately clear just how a choice between two such routes would be made. This > has been clarified. In some cases, the results will be different than > they would have been if the VPN were really a pure OSPF network. These > differences are now explained and their potential consequences pointed out. > > The procedures for forwarding data traffic on a sham link > have been clarified. The procedures for sending OSPF control traffic on a > sham link have been clarified. The role of the optional "sham link endpoint > address has been clarified. > > The procedures for translating BGP-distributed VPN-IPv4 routes > into OSPF routes have been clarified. > > A discussion of NSSA routes has been added. Alex says it is not detailed > enough; any feedback in this area would be welcome. > > Due to the large number of changes, Alex has asked for a new last > call, and I expect the WG chairs to formally issue the last call shortly. ------_=_NextPart_001_01C5B39A.2F7E0160 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=us-ascii"> <meta name=Generator content="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]--><o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PersonName"/> <!--[if !mso]> <style> st1\:*{behavior:url(#default#ieooui) } </style> <![endif]--> <style> <!-- /* Font Definitions */ @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; font-family:Arial; color:windowtext;} span.EmailStyle18 {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;} --> </style> </head> <body lang=EN-US link=blue vlink=purple> <div class=Section1> <p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:navy'>Resending to get around mailer limit on copies. <o:p></o:p></span></font></p> <p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p> <div> <div class=MsoNormal align=center style='text-align:center'><font size=3 face="Times New Roman"><span style='font-size:12.0pt'> <hr size=3 width="100%" align=center tabindex=-1> </span></font></div> <p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt; font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> <st1:PersonName w:st="on">Susan Hares</st1:PersonName> <br> <b><span style='font-weight:bold'>Sent:</span></b> Wednesday, September 07, 2005 6:47 AM<br> <b><span style='font-weight:bold'>To:</span></b> 'idr@ietf.org'<br> <b><span style='font-weight:bold'>Cc:</span></b> '<st1:PersonName w:st="on">yakov@juniper.net</st1:PersonName>'; '<st1:PersonName w:st="on">zinin@psg.com</st1:PersonName>'; 'acee@cisco.com'; 'rohit@utstar.com'; '<st1:PersonName w:st="on">zinin@psg.com</st1:PersonName>'; 'townsley@cisco.com'; 'rick@rhwilder.net'; 'rbonica@juniper.net'; 'rcallon@juniper.net'; 'erosen@cisco.com'<br> <b><span style='font-weight:bold'>Subject:</span></b> 2 week Last call on draft-ietf-l3vpn-ospf-2547-04.txt</span></font><o:p></o:p></p> </div> <p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size: 12.0pt'><o:p> </o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>This begins working group last call on draft-ietf-l3vpn-ospf-2547-04.<o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>This last call is limited to the changes that Eric has made to the <o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>document (which are outlined in Eric's email below). The last call <o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>will end in two weeks (September 21st).<o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'><o:p> </o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>Please send any comments to the working group mailing list.<o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'><o:p> </o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>Thank-you,<o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'><o:p> </o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><st1:PersonName w:st="on"><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>Susan Hares</span></font></st1:PersonName><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'> and <st1:PersonName w:st="on">Yakov Rekhter</st1:PersonName> <o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>(co-chairs, IDR) <o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'><o:p> </o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>At 11:45 AM 8/29/2005 -0400, Eric Rosen wrote:<o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>=================================================<o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>> As a result of AD review, significant changes have been made<o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>> to the specification draft-ietf-l3vpn-ospf-2547. These changes can be <o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>> seen in the latest version, draft -04. It is believed that the draft now<o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>> corresponds to the implementations.<o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>> <o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>> The following issues were addressed as a result of the AD review.<o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>> <o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>> The spec was written so as to allow a single VRF to correspond to multiple<o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>> OSPF domains. However, it did not make clear just which<o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>> parameters and procedures are relative to a domain, and which are relative to a VRF.<o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>> This has now been cleared up. However, doing so required extensive<o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>> textual changes.<o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>> <o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>> There are cases where BGP decides to put a route into the <o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>> VRF for a particular address prefix, and OSPF also decides to put a route into<o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>> the VRF for that same address prefix. Of course, only one of these can<o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>> actually be used for forwarding. The original spec did not make it <o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>> adequately clear just how a choice between two such routes would be made. This<o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>> has been clarified. In some cases, the results will be different than <o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>> they would have been if the VPN were really a pure OSPF network. These<o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>> differences are now explained and their potential consequences pointed out.<o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>><o:p> </o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>> The procedures for forwarding data traffic on a sham link <o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>> have been clarified. The procedures for sending OSPF control traffic on a<o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>> sham link have been clarified. The role of the optional "sham link endpoint<o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>> address has been clarified.<o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>> <o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>> The procedures for translating BGP-distributed VPN-IPv4 routes<o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>> into OSPF routes have been clarified.<o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>><o:p> </o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>> A discussion of NSSA routes has been added. Alex says it is not detailed<o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>> enough; any feedback in this area would be welcome.<o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>> <o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>> Due to the large number of changes, Alex has asked for a new last<o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>> call, and I expect the WG chairs to formally issue the last call shortly.<o:p></o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'><o:p> </o:p></span></font></p> <p class=MsoNormal style='text-autospace:none'><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'><o:p> </o:p></span></font></p> <p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt; font-family:Arial'><o:p> </o:p></span></font></p> </div> </body> </html> ------_=_NextPart_001_01C5B39A.2F7E0160-- --=======10259821= 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 --=======10259821=-- 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 PAA29550 for <idr-archive@nic.merit.edu>; Thu, 1 Sep 2005 15:04:32 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EAuLB-0002N4-Rr; Thu, 01 Sep 2005 15:03:13 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EAuLA-0002My-8j for idr@megatron.ietf.org; Thu, 01 Sep 2005 15:03: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 PAA23218 for <idr@ietf.org>; Thu, 1 Sep 2005 15:03:08 -0400 (EDT) Received: from relay02.pair.com ([209.68.5.16]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1EAuN7-0001BJ-JO for idr@ietf.org; Thu, 01 Sep 2005 15:05:16 -0400 Received: (qmail 68424 invoked from network); 1 Sep 2005 19:02:57 -0000 Received: from unknown (HELO workhorse.faster-light.net) (unknown) by unknown with SMTP; 1 Sep 2005 19:02:57 -0000 X-pair-Authenticated: 69.37.59.162 Received: from workhorse.faster-light.net (localhost.faster-light.net [127.0.0.1]) by workhorse.faster-light.net (8.12.11/8.12.11) with ESMTP id j81J1opP070240; Thu, 1 Sep 2005 15:01:50 -0400 (EDT) (envelope-from curtis@workhorse.faster-light.net) Message-Id: <200509011901.j81J1opP070240@workhorse.faster-light.net> To: "Joel M. Halpern" <joel@stevecrocker.com> Subject: Re: [Idr] Re: 4-Byte As Number soon to come? In-reply-to: Your message of "Wed, 31 Aug 2005 23:05:51 EDT." <6.2.1.2.0.20050831230250.02ee26b0@localhost> Date: Thu, 01 Sep 2005 15:01:50 -0400 From: Curtis Villamizar <curtis@faster-light.net> X-Spam-Score: 0.0 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d Cc: idr@ietf.org, Jeffrey Haas <jhaas@nexthop.com>, Paul Jakma <paul@clubi.ie> X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: curtis@faster-light.net 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 In message <6.2.1.2.0.20050831230250.02ee26b0@localhost> "Joel M. Halpern" writes: > > Given that path prepending is the primary (arguably the only) way for an > advertiser to express provider preference in a way visible to information > receivers, it seems that AS Path length is still our primary knob. > > This would suggest that having routers along a path change the AS Path > length of advertisements they have (potentially shortening the length) > would be a very bad thing. > > It was precisely to avoid such misleading effects that we introduced the > series of AS Sets. > > Yours, > Joel M. Halpern Joel, If memory serves me, AS-SETs were introduced for aggregation and AS Path length wasn't in use yet. Cisco put AS Path length into their implementation after rfc1771 and it became widely implemented even though it differred from the spec. So we fixed the spec to match running code, operational experience, and widespread deployment. Curtis _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr
- [Idr] Recommend Book on BGP Jing Shen
- RE: [Idr] Recommend Book on BGP john smith
- Re: [Idr] Recommend Book on BGP john smith
- Re: [Idr] Recommend Book on BGP Curtis Villamizar
- Re: [Idr] Recommend Book on BGP john smith
- Re: [Idr] Recommend Book on BGP Curtis Villamizar
- Re: [Idr] Recommend Book on BGP Dow M. Street