RE: [nemo] new requirement for draft-ietf-nemo-requirements

"Hesham Soliman" <Hesham@elevatemobile.com> Tue, 05 December 2006 04:42 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GrS8F-0005oo-Dx; Mon, 04 Dec 2006 23:42:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GrS8E-0005of-3B for nemo@ietf.org; Mon, 04 Dec 2006 23:42:14 -0500
Received: from omta05sl.mx.bigpond.com ([144.140.93.195]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GrS88-0003Jv-LR for nemo@ietf.org; Mon, 04 Dec 2006 23:42:14 -0500
Received: from PC20005 ([124.191.178.123]) by omta05sl.mx.bigpond.com with ESMTP id <20061205044157.GVMO14364.omta05sl.mx.bigpond.com@PC20005>; Tue, 5 Dec 2006 04:41:57 +0000
From: Hesham Soliman <Hesham@elevatemobile.com>
To: 'Jari Arkko' <jari.arkko@piuha.net>, 'IETF NEMO WG' <nemo@ietf.org>
Subject: RE: [nemo] new requirement for draft-ietf-nemo-requirements
Date: Tue, 05 Dec 2006 15:41:53 +1100
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
In-Reply-To: <45743493.3010403@piuha.net>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
Thread-Index: AccXsyDJmxGRrINiTW2i+BsEe0f0+QAdGiQw
Message-Id: <20061205044157.GVMO14364.omta05sl.mx.bigpond.com@PC20005>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: 'Ross Callon' <rcallon@juniper.net>
X-BeenThere: nemo@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: NEMO Working Group <nemo.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nemo>, <mailto:nemo-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nemo@ietf.org>
List-Help: <mailto:nemo-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nemo>, <mailto:nemo-request@ietf.org?subject=subscribe>
Errors-To: nemo-bounces@ietf.org

Jari, 

It's hard to disagree with the requirement. As you say the current solution
doesn't break this requirement so it might only be useful for future work,
but it's fine to have it. 

Hesham 

 > -----Original Message-----
 > From: Jari Arkko [mailto:jari.arkko@piuha.net] 
 > Sent: Tuesday, December 05, 2006 1:46 AM
 > To: IETF NEMO WG
 > Cc: Ross Callon
 > Subject: [nemo] new requirement for draft-ietf-nemo-requirements
 > 
 > Hi all,
 > 
 > We reviewed this draft in the IESG, and Ross raised
 > a requirement that he thinks is important but is not
 > listed in the current document. It is about the effect
 > to the Internet routing tables. Please find a suggested
 > edit below. We thought that this change is large
 > enough that the WG needs to be consulted, even
 > if the requirement is fulfilled by NEMO BSP. So,
 > if you have a problem with this change let us know
 > by the end of the week (Dec 8th).
 > 
 > NEW Section 3.12:
 > 
 > 3.12  Minimal Impact on Internet Routing
 > 
 > Any NEMO solution(s) needs have minimal negative effect on the
 > global Internet routing system. The solution must therefore 
 > limit both
 > the amount of information that must be injected into 
 > Internet routing,
 > as well as the dynamic changes in the information that is injected
 > into the global routing system.
 > 
 > As one example of why this is necessary, consider the approach of
 > advertising each mobile network's connectivity into BGP, and for
 > every movement withdrawing old routes and injecting new routes.
 > If there were tens of thousands of mobile networks each advertising
 > and withdrawing routes, for example, at the speed that an 
 > airplane can
 > move from one ground station to another, the potential effect on BGP
 > could be very unfortunate. In this example the total amount 
 > of routing
 > information advertised into BGP may be acceptable, but the dynamic
 > instability of the information (ie, the number of changes over time)
 > would be unacceptable.
 > 
 > NEW requirement to be added to the end of Section 4:
 > 
 > R17: The solution should have a minimal impact on the
 > global Internet routing system.
 > 
 > 
 >