Re: [RAM] First cut at routing & addressing problem statement

"Ricardo V. Oliveira" <rveloso@cs.ucla.edu> Fri, 27 July 2007 14:28 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 1IEQoE-0004gW-QS; Fri, 27 Jul 2007 10:28:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IEQoD-0004gL-3w for ram@iab.org; Fri, 27 Jul 2007 10:28:49 -0400
Received: from mail-red.research.att.com ([192.20.225.110]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEQoC-0005SK-Gt for ram@iab.org; Fri, 27 Jul 2007 10:28:49 -0400
Received: from [135.207.28.60] (fpdhcp060.research.att.com [135.207.28.60]) by bigmail.research.att.com (8.13.7+Sun/8.11.6) with ESMTP id l6RESmgN011183 for <ram@iab.org>; Fri, 27 Jul 2007 10:28:48 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v752.2)
In-Reply-To: <200707270020.l6R0KbZs014836@cichlid.raleigh.ibm.com>
References: <200707270020.l6R0KbZs014836@cichlid.raleigh.ibm.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <FA9B89E9-F38E-459B-8B09-C22E80E726C7@cs.ucla.edu>
Content-Transfer-Encoding: 7bit
From: "Ricardo V. Oliveira" <rveloso@cs.ucla.edu>
Subject: Re: [RAM] First cut at routing & addressing problem statement
Date: Fri, 27 Jul 2007 10:32:19 -0400
To: ram@iab.org
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
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

Hi Thomas,

Some minor comments on the draft:
Sec 4.7:
"For a large ISP, the internal IPv4 table can be between 50,000 and  
150,000 routes."
What do you mean by internal IPv4 table? In large IS, the number of  
routable prefixes in a router can easily reach 250k.

   The degree of interconnectedness between ASes has increased in recent
    years.  That is, the Internet as whole is becoming "flatter" with an
    increasing number of possible paths interconnecting sites [ref?]
http://www.cs.ucla.edu/~rveloso/papers/fp163_oliveira.pdf has some  
numbers for this in section 4.3.

Thanks,

--Ricardo


On Jul 26, 2007, at 8:20 PM, Thomas Narten wrote:

> 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


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