From: Howard C. Berkowitz (hcb@gettcomm.com)
Date: Mon Jun 06 2005 - 23:00:08 GMT-3
>To: ietf-announce@ietf.org
>From: rfc-editor@rfc-editor.org
>Date: Mon, 06 Jun 2005 16:49:06 -0700
>Cc: bmwg@ietf.org, rfc-editor@rfc-editor.org
>Subject: RFC 4098 on Terminology for Benchmarking BGP Device Convergence in
> the Control Plane
>
>
>
>
>A new Request for Comments is now available in online RFC libraries.
>
>
> RFC 4098
>
> Title: Terminology for Benchmarking BGP Device
> Convergence in the Control Plane
> Author(s): H. Berkowitz, E. Davies, Ed., S. Hares,
> P. Krishnaswamy, M. Lepp
> Status: Informational
> Date: June 2005
> Mailbox: hcb@gettcomm.com, elwynd@dial.pipex.com,
> skh@nexthop.com, padma.krishnaswamy@saic.com,
> mlepp@lepp.com
> Pages: 36
> Characters: 66845
> Updates/Obsoletes/SeeAlso: None
>
> I-D Tag: draft-ietf-bmwg-conterm-06.txt
>
> URL: ftp://ftp.rfc-editor.org/in-notes/rfc4098.txt
>
>
>This document establishes terminology to standardize the
>description of benchmarking methodology for measuring eBGP convergence
>in the control plane of a single BGP device. Future documents will
>address iBGP convergence, the initiation of forwarding based on
>converged control plane information and multiple interacting BGP
>devices. This terminology is applicable to both IPv4 and IPv6.
>Illustrative examples of each version are included where relevant.
>
>This document is a product of the Benchmarking Methodology Working
>Group of the IETF.
>
>This memo provides information for the Internet community. It does
>not specify an Internet standard of any kind. 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.
>
>
>Joyce K. Reynolds and Sandy Ginoza
>USC/Information Sciences Institute
>
>...
>
>Below is the data which will enable a MIME compliant Mail Reader
>implementation to automatically retrieve the ASCII version
>of the RFCs.
>
>
>[The following attachment must be fetched by mail. Command-click the
>URL below and send the resulting message to get the attachment.]
><mailto:RFC-INFO@RFC-EDITOR.ORG?body=RETRIEVE:%20rfc%0D%0ADOC-ID:%20rfc4098>
>[The following attachment must be fetched by ftp. Command-click the
>URL below to ask your ftp client to fetch it.]
><ftp://ftp.isi.edu/in-notes/rfc4098.txt>
>_______________________________________________
>IETF-Announce mailing list
>IETF-Announce@ietf.org
>https://www1.ietf.org/mailman/listinfo/ietf-announce
This archive was generated by hypermail 2.1.4 : Wed Jul 06 2005 - 14:43:41 GMT-3