Re: [RAM] First cut at routing & addressing problem statement
Peter Sherbin <pesherb@yahoo.com> Fri, 27 July 2007 17:51 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 1IETxw-0006qV-TJ; Fri, 27 Jul 2007 13:51:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43) id 1IETxv-0006mP-NI
for ram@iab.org; Fri, 27 Jul 2007 13:51:03 -0400
Received: from web58708.mail.re1.yahoo.com ([66.196.100.185])
by ietf-mx.ietf.org with smtp (Exim 4.43) id 1IETxv-00028U-5S
for ram@iab.org; Fri, 27 Jul 2007 13:51:03 -0400
Received: (qmail 32614 invoked by uid 60001); 27 Jul 2007 17:50:48 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
b=N4I39Ad2320RewDEHQ437bz2kceCnlDy/aRIT8vCxVA6o7G2NHJ3CAw3eLTax6Oen3iK8lIfVp90grNMAGEC9E1lpSs+bfopgiL/Gq2JYsBamjtW+q8CqZBBcijVQJplAvqmFfDcrOl4vdNEfg7pTBQIuc9c8Y3B2O9fWt63KOU=;
X-YMail-OSG: gtALL_QVM1mkb93w7n1.f_n55ItCsuLkpQ1svcoFB3jg7K6Lrh0xRERMqVGl0A11wkCjWsf01d22bbNGmnNW5iuq7x.GAl1f9gYjef1Lbx4ZAG.Di6Wq6BQsjTFADA--
Received: from [24.114.255.3] by web58708.mail.re1.yahoo.com via HTTP;
Fri, 27 Jul 2007 10:50:46 PDT
Date: Fri, 27 Jul 2007 10:50:46 -0700 (PDT)
From: Peter Sherbin <pesherb@yahoo.com>
Subject: Re: [RAM] First cut at routing & addressing problem statement
To: Thomas Narten <narten@us.ibm.com>, ram@iab.org
In-Reply-To: <200707270020.l6R0KbZs014836@cichlid.raleigh.ibm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Message-ID: <901157.22509.qm@web58708.mail.re1.yahoo.com>
X-Spam-Score: 3.3 (+++)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Cc:
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
Enjoined reading the statement. Re the "flatter" Internet in 5.1. since around 2000 seemingly there is a trend in changing upstream transit contracts to peering arrangements. By Q1 2007 in the observed example over 80% of traffic is routed via peers. Statement 1. Would it be beneficial to define the targeted number of individual prefixes in DFZ, specify the update rate and then architecture towards those numbers? E.g. assume 1 AS per each 10,000 sq km of Earth's surface and 9 routes per AS. It gives about 450K as the maximum number of DFZ entries providing an idea of the router required processing power. Statement 4. Make it more rigid "Allows end sites to switch providers without configuration changes to internal end site devices". Statement 5. seems redundant Thanks, Peter --- Thomas Narten <narten@us.ibm.com> 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 > ____________________________________________________________________________________ Get the free Yahoo! toolbar and rest assured with the added security of spyware protection. http://new.toolbar.yahoo.com/toolbar/features/norton/index.php _______________________________________________ RAM mailing list RAM@iab.org https://www1.ietf.org/mailman/listinfo/ram
- [RAM] First cut at routing & addressing problem s… Thomas Narten
- Re: [RAM] First cut at routing & addressing probl… Ricardo V. Oliveira
- [RAM] rrg presentation slides online? Ved Kafle
- Re: [RAM] First cut at routing & addressing probl… Peter Sherbin
- Re: [RAM] First cut at routing & addressing probl… Jason Schiller
- Re: [RAM] First cut at routing & addressing probl… Robin Whittle
- Re: [RAM] First cut at routing & addressing probl… Robin Whittle
- Re: [RAM] First cut at routing & addressing probl… John G. Scudder
- Re: [RAM] First cut at routing & addressing probl… Thomas Narten
- Re: [RAM] First cut at routing & addressing probl… JFC Morfin
- Re: [RAM] First cut at routing & addressing probl… JFC Morfin
- Re: [RAM] First cut at routing & addressing probl… Peter Sherbin
- Re: [RAM] First cut at routing & addressing probl… Robin Whittle
- Re: [RAM] First cut at routing & addressing probl… Thomas Narten
- Re: [RAM] First cut at routing & addressing probl… JFC Morfin
- Re: [RAM] First cut at routing & addressing probl… Brian E Carpenter
- Re: [RAM] First cut at routing & addressing probl… JFC Morfin
- Re: [RAM] First cut at routing & addressing probl… Eliot Lear
- [RAM] draft-sherbin-eia-00.txt Peter Sherbin