From idr-bounces@ietf.org Tue May 16 14:19:43 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fg44h-0003n6-9F; Tue, 16 May 2006 14:15:15 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fg44g-0003mQ-8E for idr@ietf.org; Tue, 16 May 2006 14:15:14 -0400 Received: from mail-red.research.att.com ([192.20.225.110]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fg44f-0004o7-1d for idr@ietf.org; Tue, 16 May 2006 14:15:14 -0400 Received: from bright.research.att.com (bright.research.att.com [135.207.20.189]) by mail-green.research.att.com (Postfix) with ESMTP id C8CD28147; Tue, 16 May 2006 14:15:12 -0400 (EDT) Received: (from fenner@localhost) by bright.research.att.com (8.12.11.20060308/8.12.10/Submit) id k4GIFCq0004449; Tue, 16 May 2006 11:15:12 -0700 From: Bill Fenner Message-Id: <200605161815.k4GIFCq0004449@bright.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: "John G. Scudder" References: <200508121513.j7CFDnq2012021@bright.research.att.com> Date: Tue, 16 May 2006 11:15:12 -0700 Versions: dmail (linux) 2.7/makemail 2.14 X-Spam-Score: 0.0 (/) X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352 Cc: Rex Fernando , Yakov Rekhter , idr@ietf.org Subject: [Idr] Re: AD Review comments on draft-ietf-idr-restart X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: idr-bounces@ietf.org >So, I'd say the draft is correct in spirit, but >in reviewing it I see that the words are kind of >broken (in part because the base spec changed >since we wrote the draft, and in part because as >you point out TcpConnectionFails has more baggage >than we wanted). I expected that was part of it - the target FSM wasn't the one that finally got published. >Here's a proposal for wording that matches the >FSM of RFC 4271. Seems reasonable. My only suggestion is to change the order of the following: > If the local system receives a NOTIFICATION message (Event 24 or > Event 25) or if the Graceful Restart capability with one or more > AFI/SAFI has not been received for the session and the local > system receives a TcpConnectionFails (Event 18) from the > underlying TCP, the local system: to "..or if the system receives ... and the Graceful Restart capability .. has not been received ..." -- since the trigger is "receives a TcpConnectionFails" and then the condition of whether it picks this rule or the next one is the capability. I'd suggest rephrasing the other conditional similarly: > However, if the Graceful Restart capability with one or more > AFI/SAFI has been received for the session and the local system > receives a TcpConnectionFails (Event 18) from the underlying TCP, > the local system: Otherwise, it makes sense. I agree that there's no need to add a zero-time state to make this decision, and conditions in order to decide the proper transition are OK. When you update the draft with these changes, would you please consider my other comments (on an IANA considerations section and guidance on setting the timer) at the same time? Thanks, Bill _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr From idr-bounces@ietf.org Tue May 16 15:52:27 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fg5YS-0007p3-21; Tue, 16 May 2006 15:50:04 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fg5YQ-0007oK-67; Tue, 16 May 2006 15:50:02 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=cypress.neustar.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fg5YP-0002R5-Pn; Tue, 16 May 2006 15:50:02 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by cypress.neustar.com (8.12.8/8.12.8) with ESMTP id k4GJo167010825 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 16 May 2006 19:50:01 GMT Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1Fg5YP-0007jr-Cz; Tue, 16 May 2006 15: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: Date: Tue, 16 May 2006 15:50:01 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: 73734d43604d52d23b3eba644a169745 Cc: idr@ietf.org Subject: [Idr] I-D ACTION:draft-ietf-idr-bgp-identifier-07.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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 : AS-wide Unique BGP Identifier for BGP-4 Author(s) : E. Chen, J. Yuan Filename : draft-ietf-idr-bgp-identifier-07.txt Pages : 5 Date : 2006-5-16 To accommodate situations where the current requirements for the BGP Identifier are not met, this document relaxes the definition of the BGP Identifier to be a 4-octet unsigned, non-zero integer, and relaxes the "uniqueness" requirement so that only AS-wide uniqueness of the BGP Identifiers is required. These revisions to the base BGP specification do not introduce any backward compatibility issue. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-idr-bgp-identifier-07.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-idr-bgp-identifier-07.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-idr-bgp-identifier-07.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2006-5-16130422.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-idr-bgp-identifier-07.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-idr-bgp-identifier-07.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-5-16130422.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-- From idr-bounces@ietf.org Tue May 16 15:52:27 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fg5YZ-0007vr-AF; Tue, 16 May 2006 15:50:11 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fg5YQ-0007oi-F0; Tue, 16 May 2006 15:50:02 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=pine.neustar.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fg5YP-0002R8-RR; Tue, 16 May 2006 15:50:02 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by pine.neustar.com (8.12.8/8.12.8) with ESMTP id k4GJo1XO032588 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 16 May 2006 19:50:01 GMT Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1Fg5YP-0007jw-Di; Tue, 16 May 2006 15: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: Date: Tue, 16 May 2006 15:50:01 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: 73734d43604d52d23b3eba644a169745 Cc: idr@ietf.org Subject: [Idr] I-D ACTION:draft-ietf-idr-bgp-prefix-orf-03.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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 : Address Prefix Based Outbound Route Filter for BGP-4 Author(s) : E. Chen, S. Sangli Filename : draft-ietf-idr-bgp-prefix-orf-03.txt Pages : 6 Date : 2006-5-16 This document defines a new Outbound Router Filter type for BGP, termed "Address Prefix Outbound Route Filter", that can be used to perform address prefix based route filtering. This ORF-type supports prefix length or range based matching, wild-card based address prefix matching, as well as the exact address prefix matching for address families. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-idr-bgp-prefix-orf-03.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-idr-bgp-prefix-orf-03.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-idr-bgp-prefix-orf-03.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2006-5-16130702.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-idr-bgp-prefix-orf-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-idr-bgp-prefix-orf-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-5-16130702.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-- From idr-bounces@ietf.org Fri May 19 15:36:09 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FhAgF-0005LZ-Te; Fri, 19 May 2006 15:30:35 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FhAgD-0005BM-K3 for idr@ietf.org; Fri, 19 May 2006 15:30:33 -0400 Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FhAgB-00066f-AT for idr@ietf.org; Fri, 19 May 2006 15:30:33 -0400 Received: from sj-dkim-7.cisco.com ([171.68.10.88]) by sj-iport-4.cisco.com with ESMTP; 19 May 2006 12:30:31 -0700 X-IronPort-AV: i="4.05,147,1146466800"; d="txt'?scan'208"; a="1809432792:sNHT36516214" Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138]) by sj-dkim-7.cisco.com (8.12.11/8.12.11) with ESMTP id k4JJUUVM016616; Fri, 19 May 2006 12:30:30 -0700 Received: from [128.107.134.9] (enke-linux.cisco.com [128.107.134.9]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id k4JJUUsF018286; Fri, 19 May 2006 12:30:30 -0700 (PDT) Message-ID: <446E1CD6.6060903@cisco.com> Date: Fri, 19 May 2006 12:30:30 -0700 From: Enke Chen User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: idr@ietf.org Content-Type: multipart/mixed; boundary="------------060908090108060905000002" DKIM-Signature: a=rsa-sha1; q=dns; l=2361; t=1148067030; x=1148931030; c=relaxed/simple; s=sjdkim7001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=enkechen@cisco.com; z=From:Enke=20Chen=20 |Subject:Implementation=20survey=20for=20draft-ietf-idr-route-filter-13.txt=20and =0A=20draft-ietf-idr-bgp-prefix-orf-03.txt; X=v=3Dcisco.com=3B=20h=3DuUI/iEUb96vs37kGxjZQi1Da7jY=3D; b=gd6tzF+PZ9ZLHC/DCx9eBWfT6kRYfrpLhExLEZCDEIbDet2yu/NTwd0NOs1DnjDmCAjhFUcG cGZRaG5CSP6YmUCAfK0HshEGZtuaXTSFFytxSFv82Bt5qvo1Krw/T1Wk; Authentication-Results: sj-dkim-7.cisco.com; header.From=enkechen@cisco.com; dkim=pass ( 42 extraneous bytes; sig from cisco.com verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 73734d43604d52d23b3eba644a169745 Cc: Susan Hares , Yakov Rekhter Subject: [Idr] Implementation survey for draft-ietf-idr-route-filter-13.txt and draft-ietf-idr-bgp-prefix-orf-03.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: idr-bounces@ietf.org This is a multi-part message in MIME format. --------------060908090108060905000002 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi, folks: I am working on an implementation report for draft-ietf-idr-route-filter-13.txt and draft-ietf-idr-bgp-prefix-orf-03.txt. It will be greatly appreciated if folks can fill out the attached survey form, and send to me by June 5, 2006. -- Enke --------------060908090108060905000002 Content-Type: text/plain; name="form.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="form.txt" Implementation Survey for BGP ORF and Prefix-ORF ------------------------------------------------ Organization: Person filling out this form: Implementation (software version): List the ORF types that are implemented in your implementation: a) communities ORF: Yes/No b) extended communities ORF: Yes/No c) prefix ORF: Yes/No Does your implementation follow the normal procedures for handling a ROUTE-REFRESH request that does not carry ORF entries? Does your implementation defer route advertisements as specified in the specification after receiving ORF entries with "when-to-refresh" set to DEFER? How does your implementation handle route advertisements after receiving ORF entries with "when-to-refresh" set to IMMEDIATE? a) re-advertise all routes in the Adj-RIB-OUT for the AFI/SAFI (i.e., follow the normal ROUTE-REFRESH procedure), but take the ORF entries into account. Yes/No b) maintain extra state and do not re-advertise the routes that have not been effected by the ORF entries, as suggested by the specification. Yes/No Does your implementation follow all other procedures specified in the Operation Section of the specification? Has there been any interoperability testing? List the ORF types tested. Are there parts of the specification that are unclear where the implementor had to exercise some judgment that may impact the implementation and/or interoperability? a) ORF base spec: b) Prefix-ORF spec: ----------------------------------------------------------------------- --------------060908090108060905000002 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 --------------060908090108060905000002-- From idr-bounces@ietf.org Sat May 20 16:00:49 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FhXZ4-0006l5-OT; Sat, 20 May 2006 15:56:42 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FhXZ4-0006l0-37 for idr@ietf.org; Sat, 20 May 2006 15:56:42 -0400 Received: from sccrmhc14.comcast.net ([63.240.77.84]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FhXZ1-0005SG-Su for idr@ietf.org; Sat, 20 May 2006 15:56:42 -0400 Received: from waltxp (c-69-255-22-217.hsd1.va.comcast.net[69.255.22.217]) by comcast.net (sccrmhc14) with SMTP id <2006052019563901400knsole>; Sat, 20 May 2006 19:56:39 +0000 From: "Walt Lazear" To: Date: Sat, 20 May 2006 15:56:33 -0400 Message-ID: <013901c67c47$82be7540$5100a8c0@WaltXP> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Spam-Score: 0.0 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Cc: 'Walt Lazear' Subject: [Idr] BGP in an IPv6-only environment X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: idr-bounces@ietf.org I was looking at RFC 2283 (Multiprotocol Extensions for BGP-4) and in the overview, it mentions that any BGP speaker has to have an IPv4 address (to create the BGP Identifier attribute). This does not bode well for the future of IPv6, to which I am sensitized by some ongoing Government work. Talking to some who have created IPv6-only environments, it seems that they are only dealing with single subnets or very simple topologies, so BGP has not been an issue. I also looked back in the IDR archives for a rationale, but could not find such a discussion recently. So, what is someone to do who wants to create an IPv6-only environment? Is it up to those defining (the future) version BGP-5 to create BGP identifiers longer than 32 bits or AS numbers longer than 16 bits (while we're at it), to accommodate the incredibly larger world of IPv6 (with 128-bit addresses)? Or was it a compromise in RFC 2283 to ignore the IPv6-only world (assuming it won't really happen on operational networks for decades) and therefore retain backward compatibility? That's valuable in the short term, but not forever. Thanks in advance for any thoughts. Walt Lazear _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr From idr-bounces@ietf.org Sat May 20 16:30:10 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FhY4N-0002tn-1R; Sat, 20 May 2006 16:29:03 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FhY4L-0002ti-Rf for idr@ietf.org; Sat, 20 May 2006 16:29:01 -0400 Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FhY4J-0006u4-HG for idr@ietf.org; Sat, 20 May 2006 16:29:01 -0400 Received: from sj-dkim-5.cisco.com ([171.68.10.79]) by sj-iport-4.cisco.com with ESMTP; 20 May 2006 13:28:59 -0700 X-IronPort-AV: i="4.05,150,1146466800"; d="scan'208"; a="1809922966:sNHT52500894" Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138]) by sj-dkim-5.cisco.com (8.12.11/8.12.11) with ESMTP id k4KKSwk2002426; Sat, 20 May 2006 13:28:58 -0700 Received: from [10.21.97.189] (sjc-vpn1-445.cisco.com [10.21.97.189]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id k4KKSwsF028870; Sat, 20 May 2006 13:28:58 -0700 (PDT) Message-ID: <446F7C0A.9050602@cisco.com> Date: Sat, 20 May 2006 13:28:58 -0700 From: Enke Chen User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Walt Lazear Subject: Re: [Idr] BGP in an IPv6-only environment References: <013901c67c47$82be7540$5100a8c0@WaltXP> In-Reply-To: <013901c67c47$82be7540$5100a8c0@WaltXP> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit DKIM-Signature: a=rsa-sha1; q=dns; l=1522; t=1148156938; x=1149020938; c=relaxed/simple; s=sjdkim5001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=enkechen@cisco.com; z=From:Enke=20Chen=20 |Subject:Re=3A=20[Idr]=20BGP=20in=20an=20IPv6-only=20environment; X=v=3Dcisco.com=3B=20h=3DhCdUmf6+e5Tn8EDauvri39G5Y6E=3D; b=cWULM1HgrVOVLFbQKfUwhE9S6FqOzCpaXmpM4NVPIovaDQ1yG7PsIi5uRAwbESwsiC2Fpdxt jmdGIZbJKw9bmW9yi4VqFkvow0szsO185yyKHw90n3W3y0GOj4H66g55; Authentication-Results: sj-dkim-5.cisco.com; header.From=enkechen@cisco.com; dkim=pass ( sig from cisco.com verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69 Cc: idr@ietf.org X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: idr-bounces@ietf.org Hi, Walt: Please take a look at these documents: draft-ietf-idr-bgp-identifier-07.txt draft-ietf-idr-as4bytes-12.txt -- Enke Walt Lazear wrote: >I was looking at RFC 2283 (Multiprotocol Extensions for BGP-4) and in >the overview, it mentions that any BGP speaker has to have an IPv4 >address (to create the BGP Identifier attribute). This does not bode >well for the future of IPv6, to which I am sensitized by some ongoing >Government work. > >Talking to some who have created IPv6-only environments, it seems that >they are only dealing with single subnets or very simple topologies, so >BGP has not been an issue. I also looked back in the IDR archives for a >rationale, but could not find such a discussion recently. > >So, what is someone to do who wants to create an IPv6-only environment? >Is it up to those defining (the future) version BGP-5 to create BGP >identifiers longer than 32 bits or AS numbers longer than 16 bits (while >we're at it), to accommodate the incredibly larger world of IPv6 (with >128-bit addresses)? Or was it a compromise in RFC 2283 to ignore the >IPv6-only world (assuming it won't really happen on operational networks >for decades) and therefore retain backward compatibility? That's >valuable in the short term, but not forever. > >Thanks in advance for any thoughts. > >Walt Lazear > > > >_______________________________________________ >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 From idr-bounces@ietf.org Sat May 20 18:32:02 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FhZwI-0007xg-42; Sat, 20 May 2006 18:28:50 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FhZwH-0007xb-Et for idr@ietf.org; Sat, 20 May 2006 18:28:49 -0400 Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FhZwF-0003tF-3x for idr@ietf.org; Sat, 20 May 2006 18:28:49 -0400 Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-4.cisco.com with ESMTP; 20 May 2006 15:28:47 -0700 X-IronPort-AV: i="4.05,151,1146466800"; d="scan'208"; a="1809945056:sNHT30666584" Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id k4KMSk3D011769; Sat, 20 May 2006 15:28:46 -0700 Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k4KMSkB7016383; Sat, 20 May 2006 15:28:46 -0700 (PDT) Received: from [10.32.244.220] (stealth-10-32-244-220.cisco.com [10.32.244.220]) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id k4KMQ4Ux025126; Sat, 20 May 2006 15:26:04 -0700 In-Reply-To: <013901c67c47$82be7540$5100a8c0@WaltXP> References: <013901c67c47$82be7540$5100a8c0@WaltXP> Mime-Version: 1.0 (Apple Message framework v750) X-Priority: 3 (Normal) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Fred Baker Subject: Re: [Idr] BGP in an IPv6-only environment Date: Sat, 20 May 2006 15:28:44 -0700 To: Walt Lazear X-Mailer: Apple Mail (2.750) Authentication-Results: sj-dkim-3.cisco.com; header.From=fred@cisco.com; dkim=pass ( sig from cisco.com verified; ); DKIM-Signature: a=rsa-sha1; q=dns; l=2330; t=1148164126; x=1149028126; c=relaxed/simple; s=sjdkim3001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fred@cisco.com; z=From:Fred=20Baker=20 |Subject:Re=3A=20[Idr]=20BGP=20in=20an=20IPv6-only=20environment; X=v=3Dcisco.com=3B=20h=3DK1Z7UN4uUV+poGh8Xc+F9dlIvk4=3D; b=CaJfxI74J9Gc4HfDkKT26WXaDUkie9tFhmrH295enBxbBlJ1he+cKjEq9XwP/JFmCjH30eFE ut0Kxc4zal0ACyb1EBUvzpjQGHmZmCcihQHLuVo9UnPxvyk9uGI5Bfhj; X-Spam-Score: 0.0 (/) X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca Cc: idr@ietf.org X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: idr-bounces@ietf.org I believe that the authors of RFC 2283 were taking the IETF recommendation wrt IPv6 deployment seriously: initially, don't deploy IPv6-only, but rather deploy dual stack. The network of which you speak will have to figure out how to support IPv4 equipment, if for no other reason because not all equipment will be upgraded simultaneously. It is in that network's best interest, I believe, to go dual stack initially and only switch to IPv6-only when the equipment is supports has all been upgraded to also support IPv6. That said, your point that BGP needs to be able to operate in an IPv6- only environment is valid. I believe that a solution may be to have it associate router IDs with addresses, and use router ids in these three places. Not that I wouldn't like to replace BGP with something new, but I don't see that happening in the near term. On May 20, 2006, at 12:56 PM, Walt Lazear wrote: > I was looking at RFC 2283 (Multiprotocol Extensions for BGP-4) and in > the overview, it mentions that any BGP speaker has to have an IPv4 > address (to create the BGP Identifier attribute). This does not bode > well for the future of IPv6, to which I am sensitized by some ongoing > Government work. > > Talking to some who have created IPv6-only environments, it seems that > they are only dealing with single subnets or very simple > topologies, so > BGP has not been an issue. I also looked back in the IDR archives > for a > rationale, but could not find such a discussion recently. > > So, what is someone to do who wants to create an IPv6-only > environment? > Is it up to those defining (the future) version BGP-5 to create BGP > identifiers longer than 32 bits or AS numbers longer than 16 bits > (while > we're at it), to accommodate the incredibly larger world of IPv6 (with > 128-bit addresses)? Or was it a compromise in RFC 2283 to ignore the > IPv6-only world (assuming it won't really happen on operational > networks > for decades) and therefore retain backward compatibility? That's > valuable in the short term, but not forever. > > Thanks in advance for any thoughts. > > Walt Lazear > > > > _______________________________________________ > 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 From idr-bounces@ietf.org Sun May 21 14:21:57 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FhsWE-00088t-NA; Sun, 21 May 2006 14:19:10 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FhsTt-0007wW-St for idr@ietf.org; Sun, 21 May 2006 14:16:45 -0400 Received: from sccrmhc12.comcast.net ([204.127.200.82]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FhsQ3-0002FH-16 for idr@ietf.org; Sun, 21 May 2006 14:12:50 -0400 Received: from waltxp (c-69-255-22-217.hsd1.va.comcast.net[69.255.22.217]) by comcast.net (sccrmhc12) with SMTP id <20060521181246012005d4qie>; Sun, 21 May 2006 18:12:46 +0000 From: "Walt Lazear" To: Date: Sun, 21 May 2006 14:12:44 -0400 Message-ID: <014101c67d02$2c4a6f00$5100a8c0@WaltXP> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 In-Reply-To: X-Spam-Score: 0.0 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 Subject: [Idr] Re: BGP in an IPv6-only environment X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: idr-bounces@ietf.org Thanks to those who pointed out the documents I had missed, that defined BGP Identifier as something other than an IPv4 address and enlarged the AS number space. While it was disappointing not to have an algorithm to help derive the BGP ID (like using parts of a MAC address or an IPv6 address), the definition is at least protocol independent and can be manually configured. Sorry I had missed the document and discussion, but I recently joined the mailing list. In my note, I was referring not to a transitioning network (for which I heartily agree that dual stack is the right transition mechanism), but to someone who wanted to build an IPv6-only network from scratch. This could be done in a detached testbed or network, with no connectivity to the public Internet. The new documents help make that possible. Thanks again. Walt _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr From idr-bounces@ietf.org Thu May 25 15:52:50 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FjLrO-0006HB-Qk; Thu, 25 May 2006 15:51:06 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FjLrL-0006F7-D0; Thu, 25 May 2006 15:51:03 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FjLrL-0008FP-AU; Thu, 25 May 2006 15:51:03 -0400 Received: from cypress.neustar.com ([209.173.57.84]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FjLrJ-0004DY-SW; Thu, 25 May 2006 15:51:03 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by cypress.neustar.com (8.12.8/8.12.8) with ESMTP id k4PJo167010043 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 25 May 2006 19:50:01 GMT Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1FjLqL-0002MN-FR; Thu, 25 May 2006 15: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: Date: Thu, 25 May 2006 15:50:01 -0400 X-Spam-Score: -2.6 (--) X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86 Cc: idr@ietf.org Subject: [Idr] I-D ACTION:draft-ietf-idr-restart-11.txt X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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 : Graceful Restart Mechanism for BGP Author(s) : S. Sangli, et al. Filename : draft-ietf-idr-restart-11.txt Pages : 11 Date : 2006-5-25 This document proposes a mechanism for BGP that would help minimize the negative effects on routing caused by BGP restart. An End-of-RIB marker is specified and can be used to convey routing convergence information. A new BGP capability, termed "Graceful Restart Capability", is defined which would allow a BGP speaker to express its ability to preserve forwarding state during BGP restart. Finally, procedures are outlined for temporarily retaining routing information across a TCP transport reset. The mechanisms described in this document are applicable to all routers, both those with the ability to preserve forwarding state during BGP restart and those without (although the latter need to implement only a subset of the mechanisms described in this document). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-idr-restart-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-restart-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-restart-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: <2006-5-25130442.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-idr-restart-11.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-idr-restart-11.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-5-25130442.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-- From idr-bounces@ietf.org Sun May 28 12:13:49 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FkNrk-0000j1-GJ; Sun, 28 May 2006 12:11:44 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FkNri-0000iv-Hu for idr@ietf.org; Sun, 28 May 2006 12:11:42 -0400 Received: from colo-dns-ext2.juniper.net ([207.17.137.64]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FkNrh-0003A4-6B for idr@ietf.org; Sun, 28 May 2006 12:11:42 -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 k4SGBe1Z055125 for ; Sun, 28 May 2006 09:11:40 -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 k4SGBe534116 for ; Sun, 28 May 2006 09:11:40 -0700 (PDT) (envelope-from yakov@juniper.net) Message-Id: <200605281611.k4SGBe534116@merlot.juniper.net> To: idr@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <9829.1148832700.1@juniper.net> Date: Sun, 28 May 2006 09:11:40 -0700 From: Yakov Rekhter X-Spam-Score: 0.0 (/) X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793 Subject: [Idr] Internet Draft cutoff dates X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: idr-bounces@ietf.org fyi. ----------------------------------------------------------------- From: ietf-secretariat@ietf.org [mailto:ietf-secretariat@ietf.org] Sent: Friday, May 26, 2006 12:00 AM To: ietf-announce@ietf.org Subject: Internet-Drafts Submission Cutoff Dates for the 66th IETF Meetingin Montreal, Quebec, Canada There are two (2) Internet-Draft cutoff dates for the 66th IETF Meeting in Montreal, Quebec, Canada: June 19th: Cutoff Date for Initial (i.e., version -00) Internet-Draft Submissions All initial Internet-Drafts (version -00) must be submitted by Monday, June 19th at 9:00 AM ET. As always, all initial submissions with a filename beginning with "draft-ietf" must be approved by the appropriate WG Chair before they can be processed or announced. The Secretariat would appreciate receiving WG Chair approval by Monday, June 12th at 9:00 AM ET. June 26th: Cutoff Date for Revised (i.e., version -01 and higher) Internet-Draft Submissions All revised Internet-Drafts (version -01 and higher) must be submitted by Monday, June 26th at 9:00 AM ET. Initial and revised Internet-Drafts received after their respective cutoff dates will not be made available in the Internet-Drafts directory or announced until on or after Monday, July 10th at 9:00 AM ET, when Internet-Draft posting resumes. Please do not wait until the last minute to submit. Thank you for your understanding and cooperation. If you have any questions or concerns, then please send a message to internet-drafts@ietf.org. The IETF Secretariat FYI: The Internet-Draft cutoff dates as well as other significant dates for the 66th IETF Meeting can be found at http://www.ietf.org/meetings/cutoff_dates_66.html. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr From idr-bounces@ietf.org Sun May 28 12:17:10 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FkNwt-0003hf-39; Sun, 28 May 2006 12:17:03 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FkNws-0003ha-0m for idr@ietf.org; Sun, 28 May 2006 12:17:02 -0400 Received: from colo-dns-ext1.juniper.net ([207.17.137.57]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FkNwq-0003Fn-Lz for idr@ietf.org; Sun, 28 May 2006 12:17:02 -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 k4SGGxX52242 for ; Sun, 28 May 2006 09:17:00 -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 k4SGGs534550 for ; Sun, 28 May 2006 09:16:54 -0700 (PDT) (envelope-from yakov@juniper.net) Message-Id: <200605281616.k4SGGs534550@merlot.juniper.net> To: idr@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <9964.1148833014.1@juniper.net> Date: Sun, 28 May 2006 09:16:54 -0700 From: Yakov Rekhter X-Spam-Score: 0.0 (/) X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de Subject: [Idr] IDR WG meeting at IETF 66 X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: idr-bounces@ietf.org Folks, Its about time to start thinking about agenda items for the next IETF. Please forward any IDR agenda items you might have to Sue and myself. The deadline is June 30. If you plan to make a presentation, please also keep in mind the rule "no Internet Draft - no time slot". Sue & Yakov. _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr From idr-bounces@ietf.org Tue May 30 17:37:34 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FlBrv-0007ax-D8; Tue, 30 May 2006 17:35:15 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FlBrt-0007ap-TO; Tue, 30 May 2006 17:35:13 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FlBrt-0006EB-Rs; Tue, 30 May 2006 17:35:13 -0400 Received: from cypress.neustar.com ([209.173.57.84]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FlBiZ-0002Y6-CS; Tue, 30 May 2006 17:25:38 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by cypress.neustar.com (8.12.8/8.12.8) with ESMTP id k4ULOZmU006314 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 30 May 2006 21:24:35 GMT Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1FlBha-0006SS-Uy; Tue, 30 May 2006 17:24:34 -0400 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Tue, 30 May 2006 17:24:34 -0400 X-Spam-Score: -2.6 (--) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Cc: idr@ietf.org Subject: [Idr] Last Call: 'Graceful Restart Mechanism for BGP' to Proposed Standard (draft-ietf-idr-restart) X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: iesg@ietf.org List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: idr-bounces@ietf.org The IESG has received a request from the Inter-Domain Routing WG to consider the following document: - 'Graceful Restart Mechanism for BGP ' as a Proposed 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 2006-06-13. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-idr-restart-11.txt _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr From idr-bounces@ietf.org Wed May 31 17:20:56 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FlY7V-0008Kt-Jh; Wed, 31 May 2006 17:20:49 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FlY7U-0008Ko-Mc for idr@ietf.org; Wed, 31 May 2006 17:20:48 -0400 Received: from colo-dns-ext2.juniper.net ([207.17.137.64]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FlY7U-0002AC-9q for idr@ietf.org; Wed, 31 May 2006 17:20: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 k4VLKl1Z099322 for ; Wed, 31 May 2006 14:20:47 -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 k4VLKl501440 for ; Wed, 31 May 2006 14:20:47 -0700 (PDT) (envelope-from yakov@juniper.net) Message-Id: <200605312120.k4VLKl501440@merlot.juniper.net> To: idr@ietf.org Subject: [Idr] I-D ACTION:draft-ietf-idr-restart-11.txt MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <7600.1149110447.1@juniper.net> Date: Wed, 31 May 2006 14:20:47 -0700 From: Yakov Rekhter X-Spam-Score: 0.0 (/) X-Scan-Signature: 5d7a7e767f20255fce80fa0b77fb2433 X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: idr-bounces@ietf.org Folks, This version of the draft reflects the comments received from the Routing Area Directors. Yakov. ------- Forwarded Message Date: Thu, 25 May 2006 15:50:01 -0400 From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org cc: idr@ietf.org Subject: [Idr] I-D ACTION:draft-ietf-idr-restart-11.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 : Graceful Restart Mechanism for BGP Author(s) : S. Sangli, et al. Filename : draft-ietf-idr-restart-11.txt Pages : 11 Date : 2006-5-25 This document proposes a mechanism for BGP that would help minimize the negative effects on routing caused by BGP restart. An End-of-RIB marker is specified and can be used to convey routing convergence information. A new BGP capability, termed "Graceful Restart Capability", is defined which would allow a BGP speaker to express its ability to preserve forwarding state during BGP restart. Finally, procedures are outlined for temporarily retaining routing information across a TCP transport reset. The mechanisms described in this document are applicable to all routers, both those with the ability to preserve forwarding state during BGP restart and those without (although the latter need to implement only a subset of the mechanisms described in this document). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-idr-restart-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 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-restart-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-restart-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: <2006-5-25130442.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-idr-restart-11.txt - --OtherAccess Content-Type: Message/External-body; name="draft-ietf-idr-restart-11.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-5-25130442.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