From idr-bounces@ietf.org Fri May 18 20:32:54 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HpCsC-0000lh-Pn; Fri, 18 May 2007 20:32:40 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HpCs9-0000hM-9S; Fri, 18 May 2007 20:32:37 -0400 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HpCs8-0008Sj-TQ; Fri, 18 May 2007 20:32:37 -0400 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id l4J0WahR015255; Fri, 18 May 2007 17:32:36 -0700 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id l4J0Waxg015254; Fri, 18 May 2007 17:32:36 -0700 Date: Fri, 18 May 2007 17:32:36 -0700 Message-Id: <200705190032.l4J0Waxg015254@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.8 (--------------) X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135 Cc: idr@ietf.org, rfc-editor@rfc-editor.org Subject: [Idr] RFC 4893 on BGP Support for Four-octet AS Number Space 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 A new Request for Comments is now available in online RFC libraries. RFC 4893 Title: BGP Support for Four-octet AS Number Space Author: Q. Vohra, E. Chen Status: Standards Track Date: May 2007 Mailbox: quaizar.vohra@gmail.com, enkechen@cisco.com Pages: 10 Characters: 21520 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-idr-as4bytes-13.txt URL: http://www.rfc-editor.org/rfc/rfc4893.txt Currently the Autonomous System (AS) number is encoded as a two-octet entity in BGP. This document describes extensions to BGP to carry the Autonomous System number as a four-octet entity. [STANDARDS TRACK] This document is a product of the Inter-Domain Routing Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr From idr-bounces@ietf.org Mon May 21 11:13:36 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hq9Zb-0006NA-6Y; Mon, 21 May 2007 11:13:23 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hq9ZV-0006Is-6K for idr@ietf.org; Mon, 21 May 2007 11:13:18 -0400 Received: from borg.juniper.net ([207.17.137.119] helo=smtpb.juniper.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hq9ZT-0006YM-VL for idr@ietf.org; Mon, 21 May 2007 11:13:17 -0400 Received: from unknown (HELO merlot.juniper.net) ([172.17.27.10]) by smtpb.juniper.net with ESMTP/TLS/DES-CBC3-SHA; 21 May 2007 08:13:15 -0700 Received: from juniper.net (sapphire.juniper.net [172.17.28.108]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id l4LFDBJ97997; Mon, 21 May 2007 08:13:11 -0700 (PDT) (envelope-from yakov@juniper.net) Message-Id: <200705211513.l4LFDBJ97997@merlot.juniper.net> To: idr@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <79771.1179760391.1@juniper.net> Date: Mon, 21 May 2007 08:13:11 -0700 From: Yakov Rekhter X-Spam-Score: 0.0 (/) X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de Cc: skh@nexthop.com Subject: [Idr] IETF 69 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 July 13, 2007 And 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 29 17:45:21 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ht9V8-00087m-IF; Tue, 29 May 2007 17:45:11 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ht9V7-000855-3S for idr@ietf.org; Tue, 29 May 2007 17:45:09 -0400 Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ht9V4-0008Cq-Uf for idr@ietf.org; Tue, 29 May 2007 17:45:09 -0400 Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-3.cisco.com with ESMTP; 29 May 2007 14:45:06 -0700 X-IronPort-AV: i="4.14,590,1170662400"; d="scan'208,217"; a="489162160:sNHT276338288" Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id l4TLj6at028898 for ; Tue, 29 May 2007 14:45:06 -0700 Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l4TLiau7024418 for ; Tue, 29 May 2007 21:45:06 GMT Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 29 May 2007 14:44:55 -0700 Received: from [171.71.55.133] ([171.71.55.133]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 29 May 2007 14:44:55 -0700 Mime-Version: 1.0 (Apple Message framework v752.3) To: idr@ietf.org Message-Id: <8B284930-65AC-4B2C-A337-94B9D25DC59D@cisco.com> References: From: Tony Li Date: Tue, 29 May 2007 14:44:55 -0700 X-Mailer: Apple Mail (2.752.3) X-OriginalArrivalTime: 29 May 2007 21:44:55.0375 (UTC) FILETIME=[98811DF0:01C7A23A] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=20572; t=1180475106; x=1181339106; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=tli@cisco.com; z=From:=20Tony=20Li=20 |Subject:=20Fwd=3A=20I-D=20ACTION=3Adraft-li-bgp-stability-00.txt=20 |Sender:=20; bh=ZdFb78euulARoPJ0oRofJVur44xL/q0JkIy3bTcNNHc=; b=jRPlMRvAH3c0ipf8DhyRCvHxBXvhJ3Z73UK1yswCQC1OJ677jVxjN+zxidLp63AARDYyBoCY BXAKvPVxr5V41Obs1Pt+ykWYjMizxwa5J48RoZVzgf2eqvOgo4UHkAZV; Authentication-Results: sj-dkim-4; header.From=tli@cisco.com; dkim=pass (sig from cisco.com/sjdkim4002 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 1a2f5df4c6f30e0d5df43748fb095119 Subject: [Idr] Fwd: I-D ACTION:draft-li-bgp-stability-00.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: , Content-Type: multipart/mixed; boundary="===============1421547398==" Errors-To: idr-bounces@ietf.org --===============1421547398== Content-Type: multipart/alternative; boundary=Apple-Mail-13-304432214 --Apple-Mail-13-304432214 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed FYI This is very much a work in progress. Comments and discussion welcome, both privately or on the mailing list. Thanks, Tony Begin forwarded message: > From: Internet-Drafts@ietf.org > Date: May 29, 2007 12:50:02 PM PDT > To: i-d-announce@ietf.org > Subject: I-D ACTION:draft-li-bgp-stability-00.txt > Reply-To: internet-drafts@ietf.org > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > > Title : BGP Stability Improvements > Author(s) : T. Li > Filename : draft-li-bgp-stability-00.txt > Pages : 13 > Date : 2007-5-29 > > BGP is the routing protocol used to tie the Autonomous Systems > (ASes) > of the Internet together. The ongoing stability of BGP in the face > of arbitrary inputs, both malicious and unintentional, is of > primary > importance to the overall stability of the Internet. The overall > issue is not a new one. Previously, one aspect of stability, known > as route flap damping was originally discussed in RFC 2439. In the > intervening years, a great deal of experience with flap damping and > other stability concerns has been accumulated. Most recently, the > issue of BGP stability has been highlighted in RAWS. This document > describes the experience that has been gained concerning > stability in > the intervening years, hypotheses about remaining problems, > suggestions for experiments to be performed, and proposals for > possible alternatives. > > > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-li-bgp-stability-00.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-li-bgp-stability-00.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-li-bgp-stability-00.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. > Content-Type: text/plain > Content-ID: <2007-5-29113529.I-D@ietf.org> > > _______________________________________________ > I-D-Announce mailing list > I-D-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/i-d-announce --Apple-Mail-13-304432214 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=ISO-8859-1

FYI

This is very much a work in = progress.=A0 Comments and discussion welcome, both privately or on the = mailing list.

Thanks,
Tony
<= DIV>

Begin forwarded message:

Date: May 29, 2007 12:50:02 PM = PDT
To: i-d-announce@ietf.org
Subject: = I-D ACTION:draft-li-bgp-stability-00.txt=A0

A New Internet-Draft is available from the on-line = Internet-Drafts=A0
directories.


Title : BGP Stability = Improvements
Author(s) : T. = Li
Filename : = draft-li-bgp-stability-00.txt
= Pages = = : 13
Date : 2007-5-29


=A0=A0 BGP is the routing = protocol used to tie the Autonomous Systems (ASes)
=A0=A0 = of the Internet together.=A0 = The ongoing stability of BGP in the face
=A0=A0 = of arbitrary inputs, both malicious and unintentional, is of = primary
=A0=A0 importance to the overall = stability of the Internet.=A0 = The overall
=A0=A0 issue is not a new = one.=A0 Previously, one = aspect of stability, known
=A0=A0 as route flap damping was = originally discussed in RFC 2439.=A0= In the
=A0=A0 intervening years, a great = deal of experience with flap damping and
=A0=A0 other stability concerns = has been accumulated.=A0 = Most recently, the
=A0=A0 issue of BGP stability has = been highlighted in RAWS.=A0 = This document
=A0=A0 describes the experience = that has been gained concerning stability in
=A0=A0 = the intervening years, hypotheses about remaining = problems,
=A0=A0 suggestions for = experiments to be performed, and proposals for
=A0=A0 = possible alternatives.



A URL = for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-li-bgp-stability-00.txt

To = remove yourself from the I-D Announcement list, send a message to=A0
i-d-announce-request@ietf.or= g with the word unsubscribe in the body of=A0
the = message.=A0
to = change your subscription settings.

Internet-Drafts are also = available by anonymous FTP. Login with the=A0
username = "anonymous" and a password of your e-mail address. After=A0
logging = in, type "cd internet-drafts" and then=A0
"get = draft-li-bgp-stability-00.txt".

A list of Internet-Drafts = directories can be found in
Internet-Drafts can also be = obtained by e-mail.
Send a message to:
In the body type:
"FILE = /internet-drafts/draft-li-bgp-stability-00.txt".


NOTE: The mail = server at ietf.org can return the document in
MIME-encoded form by using the = "mpack" utility.=A0 To use = this
feature, insert the command = "ENCODING mime" before the "FILE"
= command.=A0 To = decode the response(s), you will need "munpack" or
a MIME-compliant mail = reader.=A0 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
Content-Type: = text/plain

=

= --Apple-Mail-13-304432214-- --===============1421547398== 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 --===============1421547398==--