RFC 4984 on Report from the IAB Workshop on Routing and Addressing

rfc-editor@rfc-editor.org Thu, 27 September 2007 22:38 UTC

Return-path: <ietf-announce-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ib1zu-0005kR-Nq; Thu, 27 Sep 2007 18:38:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ib1zs-0005hY-NY for ietf-announce@ietf.org; Thu, 27 Sep 2007 18:38:16 -0400
Received: from bosco.isi.edu ([128.9.168.207]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ib1zh-0004Lq-Fa for ietf-announce@ietf.org; Thu, 27 Sep 2007 18:38:11 -0400
Received: by bosco.isi.edu (Postfix, from userid 70) id 65D26E5262; Thu, 27 Sep 2007 15:33:55 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20070927223355.65D26E5262@bosco.isi.edu>
Date: Thu, 27 Sep 2007 15:33:55 -0700 (PDT)
X-Spam-Score: -15.0 (---------------)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: iab@iab.org, rfc-editor@rfc-editor.org
Subject: RFC 4984 on Report from the IAB Workshop on Routing and Addressing
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Errors-To: ietf-announce-bounces@ietf.org

A new Request for Comments is now available in online RFC libraries.

        
        RFC 4984

        Title:      Report from the IAB Workshop 
                    on Routing and Addressing 
        Author:     D. Meyer, Ed.,
                    L. Zhang, Ed.,
                    K. Fall, Ed.
        Status:     Informational
        Date:       September 2007
        Mailbox:    dmm@1-4-5.net, 
                    lixia@cs.ucla.edu, 
                    kfall@intel.com
        Pages:      39
        Characters: 96153
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-iab-raws-report-02.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4984.txt

This document reports the outcome of the Routing and Addressing
Workshop that was held by the Internet Architecture Board (IAB) on
October 18-19, 2006, in Amsterdam, Netherlands.  The primary goal of
the workshop was to develop a shared understanding of the problems
that the large backbone operators are facing regarding the
scalability of today's Internet routing system.  The key workshop
findings include an analysis of the major factors that are driving
routing table growth, constraints in router technology, and the
limitations of today's Internet addressing architecture.  It is hoped
that these findings will serve as input to the IETF community and
help identify next steps towards effective solutions.

Note that this document is a report on the proceedings of the
workshop.  The views and positions documented in this report are
those of the workshop participants and not of the IAB.  Furthermore,
note that work on issues related to this workshop report is
continuing, and this document does not intend to reflect the
increased understanding of issues nor to discuss the range of
potential solutions that may be the outcome of this ongoing work.  This 
memo provides information for the Internet community.

This document is a product of the Internet Architecture Board.


INFORMATIONAL: 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.


The RFC Editor Team
USC/Information Sciences Institute

...



_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce