[RAM] First cut at routing & addressing problem statement

Thomas Narten <narten@us.ibm.com> Fri, 27 July 2007 00:20 UTC

Return-path: <ram-bounces@iab.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IEDZe-0008Ta-TX; Thu, 26 Jul 2007 20:20:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IEDZd-0008TV-6O for ram@iab.org; Thu, 26 Jul 2007 20:20:53 -0400
Received: from e33.co.us.ibm.com ([32.97.110.151]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEDZc-0004LZ-Ii for ram@iab.org; Thu, 26 Jul 2007 20:20:53 -0400
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by e33.co.us.ibm.com (8.13.8/8.13.8) with ESMTP id l6R0Ko3f006069 for <ram@iab.org>; Thu, 26 Jul 2007 20:20:50 -0400
Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v8.4) with ESMTP id l6R0Knjc163296 for <ram@iab.org>; Thu, 26 Jul 2007 18:20:49 -0600
Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id l6R0Kne2003682 for <ram@iab.org>; Thu, 26 Jul 2007 18:20:49 -0600
Received: from cichlid.raleigh.ibm.com (wecm-9-67-192-212.wecm.ibm.com [9.67.192.212]) by d03av02.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id l6R0KmuS003645 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ram@iab.org>; Thu, 26 Jul 2007 18:20:49 -0600
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by cichlid.raleigh.ibm.com (8.13.8/8.12.5) with ESMTP id l6R0KbZs014836 for <ram@iab.org>; Thu, 26 Jul 2007 19:20:47 -0500
Message-Id: <200707270020.l6R0KbZs014836@cichlid.raleigh.ibm.com>
To: ram@iab.org
Date: Thu, 26 Jul 2007 19:20:37 -0500
From: Thomas Narten <narten@us.ibm.com>
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Subject: [RAM] First cut at routing & addressing problem statement
X-BeenThere: ram@iab.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing and Addressing Mailing List <ram.iab.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ram>
List-Post: <mailto:ram@iab.org>
List-Help: <mailto:ram-request@iab.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=subscribe>
Errors-To: ram-bounces@iab.org

The Routing & Addressing directorate has been working on a strawman
problem statement since Prague. I just submitted our first cut as an
Internet Draft and it's available at:

http://www.cs.duke.edu/~narten/ietf/draft-narten-radir-problem-statement-00.txt

We would welcome comments on the document. In particular:

 - Do folk agree with the problem statement as written, or are we
   missing something fairly fundamental?

 - Are there other pressures on the routing system that we have not
   listed or described completely?

 - We intentionally did not include improving mobility as a core
   "problem", as explained in the document. (That doesn't mean we
   don't recognize that some of the solutions under discussion may
   also be applicable to mobility scenarios. Rather, we tend to see
   improved mobility as a possible benefit of certain classes of
   solutions.)

 - Are there other views of what folk perceive the core routing and
   addressing problem to be?

Thomas

_______________________________________________
RAM mailing list
RAM@iab.org
https://www1.ietf.org/mailman/listinfo/ram