From rrg-bounces@irtf.org  Thu Jan  1 05:50:05 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CD6863A6981;
	Thu,  1 Jan 2009 05:50:05 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5FFB43A6947
	for <rrg@core3.amsl.com>; Thu,  1 Jan 2009 05:50:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id kD95vEvQXUJs for <rrg@core3.amsl.com>;
	Thu,  1 Jan 2009 05:50:03 -0800 (PST)
Received: from vms173007pub.verizon.net (vms173007pub.verizon.net
	[206.46.173.7]) by core3.amsl.com (Postfix) with ESMTP id A006C3A68CC
	for <rrg@irtf.org>; Thu,  1 Jan 2009 05:50:03 -0800 (PST)
Received: from [10.30.20.71] ([70.104.193.39]) by vms173007.mailsrvcs.net
	(Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
	with ESMTPA id <0KCS006A4P0FLQU3@vms173007.mailsrvcs.net> for
	rrg@irtf.org; Thu, 01 Jan 2009 07:48:20 -0600 (CST)
Date: Thu, 01 Jan 2009 08:49:33 -0500
From: RJ Atkinson <rja@extremenetworks.com>
In-reply-to: <3c3e3fca0812311715r5cad842elfba98f56596bd033@mail.gmail.com>
To: IRTF Routing RG <rrg@irtf.org>
Message-id: <B761BA80-6FD2-4D83-89C2-ACDC521E8574@extremenetworks.com>
MIME-version: 1.0 (Apple Message framework v930.3)
X-Mailer: Apple Mail (2.930.3)
References: <3c3e3fca0812310857y14a8233ag953a9441279a25b5@mail.gmail.com>
	<EC6C5330-557A-4D5F-8FF9-10A639806C6C@extremenetworks.com>
	<3c3e3fca0812311715r5cad842elfba98f56596bd033@mail.gmail.com>
Subject: Re: [rrg] solution strategies, nat?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org


On  31 Dec 2008, at 20:15, William Herrin wrote:
> I would like to hear about additional NAT-based techniques which, like
> Chris' notion, suggest a credible plan for reducing the demand for
> core routing slots compared to the status quo.

I cited "NAT66" specifically.  I also noted both where that
discussion has been happening (although some related
discussion has also happened here) and the existence of an I-D.
For example, one form of NAT66 is stateless, meaning that
sessions could be initiated from outside or inside the NAT
perimeter.  Please go read the draft.

I also specifically cited "architected NAT", where there is
a concrete specification that has particular properties.

Thirdly, I've talked in the past about how Locator rewriting
(which is a kind of NAT) could be used with ILNP.  This is a bit
similar to Six/One, but is not identical.  This is discussed
in detail in various published papers.

Either of these is rather different from your apparent view
of a single monolithic "IPv4 NAT".  In fact, a wide range of
different forms of NAT exist, most of which are not very well
documented.  Different NAT techniques/implementations have
different properties.

> I would prefer not to hear about the usefulness of vanilla NAT.

Certainly, it is your choice what you choose to read or hear.

> We have determined beyond the shadow of a doubt
> that the status quo is not, at this time, self-reducing.

The RG has *not* made a determination that all existing NAT
techniques (there are a wide range of various NAT methods
available in myriad different implementations) aren't part
of the possible solution set.

Under IRTF process rules, only the RG Chairs have the authority
to make a consensus determination.

> Vanilla NAT is indeed useful, but as
> widely deployed today it is already a part of the status quo.


Since IPv4 NAT has so many different forms, with varying
properties, I have no idea what you mean when you say
"Vanilla NAT".

Yours,

Ran
rja@extremenetworks.com

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan  1 08:37:51 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E909E3A68D6;
	Thu,  1 Jan 2009 08:37:51 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9BFFF3A68D6
	for <rrg@core3.amsl.com>; Thu,  1 Jan 2009 08:37:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.963
X-Spam-Level: 
X-Spam-Status: No, score=-1.963 tagged_above=-999 required=5 tests=[AWL=0.014, 
	BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 3TdigPDcD-D8 for <rrg@core3.amsl.com>;
	Thu,  1 Jan 2009 08:37:49 -0800 (PST)
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.183])
	by core3.amsl.com (Postfix) with ESMTP id 9128A3A68B9
	for <rrg@irtf.org>; Thu,  1 Jan 2009 08:37:49 -0800 (PST)
Received: by wa-out-1112.google.com with SMTP id j37so3377262waf.23
	for <rrg@irtf.org>; Thu, 01 Jan 2009 08:37:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:sender
	:to:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references
	:x-google-sender-auth;
	bh=OEDUVUBB3dzZpzXdU5+9HEwM/zcnZFpWokTnb6EiEIY=;
	b=OIPrC920v0EQUPkemfqlkw1rwbBO6NpxZmKNFi9jV1vlxfa8sto0XYH1LieHIfDSFC
	Op7QFVg1VrAIKhMoz/5eAcNjaRvxaTBlAtpKMhXTf+JCuO4xIl9gK6huO0pzMdLyxrHe
	rLU+kQCeR9sO8iGMJRA83MxH0L24yVh3f1jj0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references:x-google-sender-auth;
	b=WkG77lK5RPVswFCCLlsIyLUtrk3Ea1NZ1JnUIf4MRBiad+sj4tdixkXQh0iDWyEjjB
	pRokC2keK6b7nQ/I6f22fOG4e0dVHD/IALuSv3nC7B5x2IwAsaSNgJxUGWwUK4xy6sqR
	tPHXsY9WyASPuqSddrpH917NebvaV6JFfp210=
Received: by 10.115.18.3 with SMTP id v3mr11231413wai.32.1230827856888;
	Thu, 01 Jan 2009 08:37:36 -0800 (PST)
Received: by 10.115.74.12 with HTTP; Thu, 1 Jan 2009 08:37:36 -0800 (PST)
Message-ID: <3c3e3fca0901010837h34a191e9r7dacb7fc504ff15b@mail.gmail.com>
Date: Thu, 1 Jan 2009 11:37:36 -0500
From: "William Herrin" <bill@herrin.us>
To: "RJ Atkinson" <rja@extremenetworks.com>
In-Reply-To: <B761BA80-6FD2-4D83-89C2-ACDC521E8574@extremenetworks.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <3c3e3fca0812310857y14a8233ag953a9441279a25b5@mail.gmail.com>
	<EC6C5330-557A-4D5F-8FF9-10A639806C6C@extremenetworks.com>
	<3c3e3fca0812311715r5cad842elfba98f56596bd033@mail.gmail.com>
	<B761BA80-6FD2-4D83-89C2-ACDC521E8574@extremenetworks.com>
X-Google-Sender-Auth: a9436150ed323001
Cc: IRTF Routing RG <rrg@irtf.org>
Subject: Re: [rrg] solution strategies, nat?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Ran,

Please understand, I am neither for nor against the use of NAT as a
route reduction technique. I do, however, insist on me being able to
satisfactorily explain how a particular approach would reduce the need
or demand for core routing slots. Until someone, such as yourself, has
explained that to me well enough that I can explain it to someone
else, it isn't gong in the document.


On Thu, Jan 1, 2009 at 8:49 AM, RJ Atkinson <rja@extremenetworks.com> wrote:
> On  31 Dec 2008, at 20:15, William Herrin wrote:
>> I would like to hear about additional NAT-based techniques which, like
>> Chris' notion, suggest a credible plan for reducing the demand for
>> core routing slots compared to the status quo.
>
> I cited "NAT66" specifically.

It is not immediately obvious to me how any form of NAT66 reduces the
demand for core routing slots. If it's obvious to you, I'm listening.


> I also specifically cited "architected NAT", where there is
> a concrete specification that has particular properties.

Would you suggest a reference which describes "architected NAT"? The
first 20 hits on google led to offhand comments which were
unrevealing.


> Thirdly, I've talked in the past about how Locator rewriting
> (which is a kind of NAT) could be used with ILNP.  This is a bit
> similar to Six/One, but is not identical.  This is discussed
> in detail in various published papers.

Link please?



>> We have determined beyond the shadow of a doubt
>> that the status quo is not, at this time, self-reducing.
>
> Under IRTF process rules, only the RG Chairs have the authority
> to make a consensus determination.

That is an... interesting... refutation of established fact.


Regards,
Bill Herrin



-- 
William D. Herrin ................ herrin@dirtside.com  bill@herrin.us
3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
Falls Church, VA 22042-3004
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan  1 08:47:31 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E329D3A68B9;
	Thu,  1 Jan 2009 08:47:31 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3B6CB3A68B9
	for <rrg@core3.amsl.com>; Thu,  1 Jan 2009 08:47:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_45=0.6]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id pWW4N65JGhLs for <rrg@core3.amsl.com>;
	Thu,  1 Jan 2009 08:47:30 -0800 (PST)
Received: from elom.tchmachines.com (elom.tchmachines.com [208.76.80.198])
	by core3.amsl.com (Postfix) with ESMTP id 8DA7D3A65A5
	for <rrg@irtf.org>; Thu,  1 Jan 2009 08:47:30 -0800 (PST)
Received: from cpe-066-057-118-226.nc.res.rr.com ([66.57.118.226])
	by elom.tchmachines.com with esmtpa (Exim 4.69)
	(envelope-from <slblake@petri-meat.com>)
	id 1LIQhY-0002Zj-Cx; Thu, 01 Jan 2009 11:47:16 -0500
From: Steven Blake <slblake@petri-meat.com>
To: Robin Whittle <rw@firstpr.com.au>
In-Reply-To: <495C3FB6.8030808@firstpr.com.au>
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com>
	<75cb24520812311427m31d4dae0nd5c37130cc485eaf@mail.gmail.com>
	<495C3FB6.8030808@firstpr.com.au>
Date: Thu, 01 Jan 2009 11:47:17 -0500
Message-Id: <1230828437.2961.38.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.24.2 (2.24.2-2.fc10) 
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - elom.tchmachines.com
X-AntiAbuse: Original Domain - irtf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - petri-meat.com
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On Thu, 2009-01-01 at 14:59 +1100, Robin Whittle wrote:

> Short version:  Limits on using PC hardware for router FIBs.
>                 Fast SRAM is needed, not DRAM.

[snip]

One can build a 4M+ prefix, 300M LPM/sec FIB engine (v4 or v6) using
commercially available FPGA + DDR3.

Regarding RIB processing: I'll accept the argument that rate*state
growth is exceeding Moore's Law.  However, most RPs I've seen are anemic
compared to commodity server hardware (for legitimate reasons).  So
there is plenty of room for improvement here.


Regards,

// Steve

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan  1 11:43:46 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9130028C187;
	Thu,  1 Jan 2009 11:43:46 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 85EE228C187
	for <rrg@core3.amsl.com>; Thu,  1 Jan 2009 11:43:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.556
X-Spam-Level: 
X-Spam-Status: No, score=-2.556 tagged_above=-999 required=5 tests=[AWL=0.043, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id gxRyBBFBmC7l for <rrg@core3.amsl.com>;
	Thu,  1 Jan 2009 11:43:44 -0800 (PST)
Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.187])
	by core3.amsl.com (Postfix) with ESMTP id 94D9128C169
	for <rrg@irtf.org>; Thu,  1 Jan 2009 11:43:44 -0800 (PST)
Received: by ti-out-0910.google.com with SMTP id b8so5019483tic.11
	for <rrg@irtf.org>; Thu, 01 Jan 2009 11:43:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from
	:organization:user-agent:mime-version:to:cc:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=EVIpkD0bd+WoXzSaSv+Vruh+wj6zVveZKhuR4TPW4wI=;
	b=hUNKojAhUziFKwO+H1k99NUJiMGQheEIb4CRIU7BMTJb3ylSLvLU4bNEcDvEi99Gc5
	PzbzDgqbW5qVf5x3dn0ClqxlHCMZnDQ3hD4bk00bhs3ivK4WV3xyAf8RRx7ZkF4jZ8ia
	amXZnPdrIfQw2/0NISagzABKmKWNQUpWQJZFY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	b=JZQVqRe9J6FVpLWB1nfuZj+8K24leYBvHp+8IIZPTauQ2XVS3sGhTJ7nm9xKXdPADK
	GKunxFjmORI3RKFcmy/Pr4+HZUj7pPmA+/j0/WzZZr1dcJpoAnWsfRa0HfEWn2t0DpOK
	Qz4gTzD01bboI/YMUu/lUoNEjZNgbuufbvMo8=
Received: by 10.110.16.9 with SMTP id 9mr19341808tip.39.1230839011617;
	Thu, 01 Jan 2009 11:43:31 -0800 (PST)
Received: from ?10.1.1.4? (118-92-137-11.dsl.dyn.ihug.co.nz [118.92.137.11])
	by mx.google.com with ESMTPS id u8sm8448374tia.28.2009.01.01.11.43.28
	(version=SSLv3 cipher=RC4-MD5); Thu, 01 Jan 2009 11:43:30 -0800 (PST)
Message-ID: <495D1CE7.9010107@gmail.com>
Date: Fri, 02 Jan 2009 08:43:35 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: William Herrin <bill@herrin.us>
References: <3c3e3fca0812310857y14a8233ag953a9441279a25b5@mail.gmail.com>	<EC6C5330-557A-4D5F-8FF9-10A639806C6C@extremenetworks.com>	<3c3e3fca0812311715r5cad842elfba98f56596bd033@mail.gmail.com>	<B761BA80-6FD2-4D83-89C2-ACDC521E8574@extremenetworks.com>
	<3c3e3fca0901010837h34a191e9r7dacb7fc504ff15b@mail.gmail.com>
In-Reply-To: <3c3e3fca0901010837h34a191e9r7dacb7fc504ff15b@mail.gmail.com>
Cc: RJ Atkinson <rja@extremenetworks.com>, IRTF Routing RG <rrg@irtf.org>
Subject: Re: [rrg] solution strategies, nat?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On 2009-01-02 05:37, William Herrin wrote:
> Ran,
> 
> Please understand, I am neither for nor against the use of NAT as a
> route reduction technique. I do, however, insist on me being able to
> satisfactorily explain how a particular approach would reduce the need
> or demand for core routing slots. Until someone, such as yourself, has
> explained that to me well enough that I can explain it to someone
> else, it isn't gong in the document.

Slide 15 in
http://www.cs.auckland.ac.nz/~brian/RRG0708.pdf

    Brian
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan  1 13:00:20 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3A0823A698C;
	Thu,  1 Jan 2009 13:00:20 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 20EE93A698C
	for <rrg@core3.amsl.com>; Thu,  1 Jan 2009 13:00:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.516
X-Spam-Level: 
X-Spam-Status: No, score=-6.516 tagged_above=-999 required=5 tests=[AWL=0.083, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id E3whp3b4CgMc for <rrg@core3.amsl.com>;
	Thu,  1 Jan 2009 13:00:18 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 3EB513A6916
	for <rrg@irtf.org>; Thu,  1 Jan 2009 13:00:18 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.36,314,1228089600"; d="scan'208";a="32481814"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 01 Jan 2009 21:00:07 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n01L05xw002093
	for <rrg@irtf.org>; Thu, 1 Jan 2009 16:00:05 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n01L050V029323
	for <rrg@irtf.org>; Thu, 1 Jan 2009 21:00:05 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 1 Jan 2009 16:00:05 -0500
Received: from cisco.com ([64.102.8.172]) by xfe-rtp-202.amer.cisco.com with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 1 Jan 2009 16:00:05 -0500
Date: Thu, 1 Jan 2009 15:59:59 -0500
From: Scott Brim <swb@employees.org>
To: rrg@irtf.org
Message-ID: <20090101205959.GF9477@cisco.com>
Mail-Followup-To: Scott Brim <swb@employees.org>, rrg@irtf.org
References: <3c3e3fca0812310857y14a8233ag953a9441279a25b5@mail.gmail.com>
	<EC6C5330-557A-4D5F-8FF9-10A639806C6C@extremenetworks.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <EC6C5330-557A-4D5F-8FF9-10A639806C6C@extremenetworks.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-OriginalArrivalTime: 01 Jan 2009 21:00:05.0424 (UTC)
	FILETIME=[EBFF6B00:01C96C53]
Authentication-Results: rtp-dkim-2; header.From=swb@employees.org; dkim=neutral
Subject: Re: [rrg] solution strategies, nat?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Excerpts from RJ Atkinson on Wed, Dec 31, 2008 02:37:07PM -0500:
> (NAT/NAPT or LocatorRewriting or pick a another name) performed
> inside a site's border router can enable a site to multi-home
> effectively without any de-aggregation (i.e. without any impact on
> the DFZ RIB or DFZ FIB).  Existing mechanisms that enable
> distributed firewalls to share session state would clearly also work
> to share NAT session state among a set of site border routers, if
> that were desired.

Multihoming on different providers?  If an endpoint appears to have
two different addresses due to being NATted onto two different
providers, and routing changes so that packets switch from flowing
through one provider to flowing through the other one, connections
break.

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan  1 13:24:52 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8F18A3A6ABC;
	Thu,  1 Jan 2009 13:24:52 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 74B553A6AC0
	for <rrg@core3.amsl.com>; Thu,  1 Jan 2009 13:24:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id uUhvECpf7xPs for <rrg@core3.amsl.com>;
	Thu,  1 Jan 2009 13:24:50 -0800 (PST)
Received: from vms173003pub.verizon.net (vms173003pub.verizon.net
	[206.46.173.3]) by core3.amsl.com (Postfix) with ESMTP id 8CE233A6ABC
	for <rrg@irtf.org>; Thu,  1 Jan 2009 13:24:50 -0800 (PST)
Received: from [10.30.20.71] ([70.104.193.39]) by vms173003.mailsrvcs.net
	(Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
	with ESMTPA id <0KCT001NCA49RCW4@vms173003.mailsrvcs.net> for
	rrg@irtf.org; Thu, 01 Jan 2009 15:24:13 -0600 (CST)
Date: Thu, 01 Jan 2009 16:24:08 -0500
From: RJ Atkinson <rja@extremenetworks.com>
In-reply-to: <3c3e3fca0901010837h34a191e9r7dacb7fc504ff15b@mail.gmail.com>
To: IRTF Routing RG <rrg@irtf.org>
Message-id: <E5E14C90-2D4E-4F7A-BF05-9DB027B11E30@extremenetworks.com>
MIME-version: 1.0 (Apple Message framework v930.3)
X-Mailer: Apple Mail (2.930.3)
References: <3c3e3fca0812310857y14a8233ag953a9441279a25b5@mail.gmail.com>
	<EC6C5330-557A-4D5F-8FF9-10A639806C6C@extremenetworks.com>
	<3c3e3fca0812311715r5cad842elfba98f56596bd033@mail.gmail.com>
	<B761BA80-6FD2-4D83-89C2-ACDC521E8574@extremenetworks.com>
	<3c3e3fca0901010837h34a191e9r7dacb7fc504ff15b@mail.gmail.com>
Subject: Re: [rrg] solution strategies, nat?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org


On  1 Jan 2009, William Herrin wrote:
> It is not immediately obvious to me how any form of NAT66 reduces
> the demand for core routing slots. If it's obvious to you, I'm  
> listening.


draft-mrw-behave-nat66-01.txt

NAT66 is one example of an Architected NAT.  Kindly note that
NAT66 still seems to be a work in progress, and hence might change,
although it seems very well written to me at present.

One can imagine other instances of an Architected NAT that might make
different design decisions and might target either IPv4 or both
IPv4 and IPv6.  (NAT66 is an IPv6-specific approach.)  [See also
other comments later in this note.]

(Depending upon perspective, some might consider SHIM6
another example of an "Architected NAT", albeit one where
the NAT function occurs inside the end system.)

Some other RG folks have suggested that NAT is a viable approach
for the group to consider:
	<http://www.irtf.org/pipermail/rrg/2008-October/000009.html>
	<http://www.irtf.org/pipermail/rrg/2008-October/000075.html>
	<http://www.irtf.org/pipermail/rrg/2008-December/000614.html>

Of the last URL's concerns, NAT66 appears not to have the issues
mentioned with "N:1 multiplexing" or the issues of "session
survivability in the case of uplink failover", at least in some
modes of operation.  (NAT66 defines several options.)

Also, as noted earlier today by Brian Carpenter:
	http://www.cs.auckland.ac.nz/~brian/RRG0708.pdf

> Link please?

draft-rja-ilnp-intro-02.txt contains a number of references.



Separately, also today, Scott Brim commented:
% If an endpoint appears to have two different addresses due to
% being NATted onto two different providers, and routing changes
% so that packets switch from flowing through one provider to
% flowing through the other one, connections break.

In an old IPv4 NAT, particularly those in low-cost consumer
devices, the above is commonly true.

With NAT66, if both sites are using NAT66 and both are using
it in "Algorithmic Translation" (Section 5.1.1) mode, it is
not obvious that this issue [1] still exists.  The transport-layer
state can use, for example, ULA addresses (which are NOT in the
DFZ RIB/FIB) and the algorithmic mapping means no NAT session state
is required either.

I'm neither particularly advocating NAT-based approaches,
nor am I particularly opposed to NAT-based approaches.  I
would prefer that the RG examine all of the options, and
this sort of an approach seems to be a viable option.

Cheers,

Ran
rja@extremenetworks.com

[1] I.e. the issue created by using different addresses,
with different ISP-aggregatable routing prefixes, on
the wire between sites, for a single session.





_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan  1 14:47:45 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 807683A6870;
	Thu,  1 Jan 2009 14:47:45 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3BD733A691F
	for <rrg@core3.amsl.com>; Thu,  1 Jan 2009 14:47:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.557
X-Spam-Level: 
X-Spam-Status: No, score=-2.557 tagged_above=-999 required=5 tests=[AWL=0.042, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6uQbOeUdTSsm for <rrg@core3.amsl.com>;
	Thu,  1 Jan 2009 14:47:43 -0800 (PST)
Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.185])
	by core3.amsl.com (Postfix) with ESMTP id 3AE1E3A67F8
	for <rrg@irtf.org>; Thu,  1 Jan 2009 14:47:14 -0800 (PST)
Received: by ti-out-0910.google.com with SMTP id b8so5034069tic.11
	for <rrg@irtf.org>; Thu, 01 Jan 2009 14:47:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from
	:organization:user-agent:mime-version:to:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=Id56vWlSPQmSuyd5LR4UyNnY+VluXtg08iWDLH8ATUE=;
	b=QS64ZYp702i0w4ebKj902gQopOl6AxGsOACWHuY/jvQMXap0DnY6+jifaQoNv3Usl9
	URq3Hr/+JE+TIpxMBLFOyWTRXFdasy/Uoaw5LnYiyu9221WBDDE0ecNwhtM/4HjUl3yj
	dE/hg/bbFATRIyQwePoKUZ/QOkvvzsGU+kilM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	b=KWoAgL6+QHP9wEDDrwyck5r1ltaJ4odangbIPUIaSGuU+lj3Rq5SN4YK2BKWwF2KL6
	K4E8O8Gi1k19sk5CBZnfa6bUvaULc4BusJTV5ROkY2yse3DE5bnAVji86xtqHSUGTLOJ
	MXNwl/YGifmBdbkaeC10kSRnqJkOf2dO+ySoQ=
Received: by 10.110.70.17 with SMTP id s17mr5216768tia.23.1230850020852;
	Thu, 01 Jan 2009 14:47:00 -0800 (PST)
Received: from ?10.1.1.4? (118-92-137-11.dsl.dyn.ihug.co.nz [118.92.137.11])
	by mx.google.com with ESMTPS id b7sm11015315tic.23.2009.01.01.14.46.56
	(version=SSLv3 cipher=RC4-MD5); Thu, 01 Jan 2009 14:46:59 -0800 (PST)
Message-ID: <495D47E3.7040304@gmail.com>
Date: Fri, 02 Jan 2009 11:46:59 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Scott Brim <swb@employees.org>,  rrg@irtf.org
References: <3c3e3fca0812310857y14a8233ag953a9441279a25b5@mail.gmail.com>	<EC6C5330-557A-4D5F-8FF9-10A639806C6C@extremenetworks.com>
	<20090101205959.GF9477@cisco.com>
In-Reply-To: <20090101205959.GF9477@cisco.com>
Subject: Re: [rrg] solution strategies, nat?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On 2009-01-02 09:59, Scott Brim wrote:
> Excerpts from RJ Atkinson on Wed, Dec 31, 2008 02:37:07PM -0500:
>> (NAT/NAPT or LocatorRewriting or pick a another name) performed
>> inside a site's border router can enable a site to multi-home
>> effectively without any de-aggregation (i.e. without any impact on
>> the DFZ RIB or DFZ FIB).  Existing mechanisms that enable
>> distributed firewalls to share session state would clearly also work
>> to share NAT session state among a set of site border routers, if
>> that were desired.
> 
> Multihoming on different providers?  If an endpoint appears to have
> two different addresses due to being NATted onto two different
> providers, and routing changes so that packets switch from flowing
> through one provider to flowing through the other one, connections
> break.

Certainly. So if you were product manager for a highly reliable
distributed application, I'm sure you would insist that it was
coded to detect permanent transport failures and try alternative
addresses. That may not be elegant computer science but it's one
way that the Internet routes around damage.

    Brian


_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan  1 16:34:19 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9D3043A6A24;
	Thu,  1 Jan 2009 16:34:19 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BB0393A6A24
	for <rrg@core3.amsl.com>; Thu,  1 Jan 2009 16:34:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.55
X-Spam-Level: 
X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[AWL=0.049, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id xipF8CzjHLXA for <rrg@core3.amsl.com>;
	Thu,  1 Jan 2009 16:34:17 -0800 (PST)
Received: from QMTA08.emeryville.ca.mail.comcast.net
	(qmta08.emeryville.ca.mail.comcast.net [76.96.30.80])
	by core3.amsl.com (Postfix) with ESMTP id 724A53A6ABA
	for <rrg@irtf.org>; Thu,  1 Jan 2009 16:34:15 -0800 (PST)
Received: from OMTA01.emeryville.ca.mail.comcast.net ([76.96.30.11])
	by QMTA08.emeryville.ca.mail.comcast.net with comcast
	id yQBm1a00C0EPchoA8Qa43s; Fri, 02 Jan 2009 00:34:04 +0000
Received: from TONYLTM9XP ([155.53.1.254])
	by OMTA01.emeryville.ca.mail.comcast.net with comcast
	id yQZn1a00L5Up7oj8MQZqXj; Fri, 02 Jan 2009 00:34:02 +0000
From: "Tony Li" <tony.li@tony.li>
To: "'Paul Jakma'" <paul@clubi.ie>
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com>
	<75cb24520812311427m31d4dae0nd5c37130cc485eaf@mail.gmail.com>
	<3c3e3fca0812311524o36bf8ae5k6837b7d15813685e@mail.gmail.com>
	<75cb24520812311536u6930dcd7o65394ae000c7b5f6@mail.gmail.com>
	<1D471F7666CB4482A947C3D07CC04C1F@ad.redback.com>
	<alpine.LFD.2.00.0901011335130.4278@localhost.localdomain>
Date: Thu, 1 Jan 2009 16:33:00 -0800
Message-ID: <0D1281C807BE4306AE8B6021B487CD0F@ad.redback.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
In-Reply-To: <alpine.LFD.2.00.0901011335130.4278@localhost.localdomain>
Thread-Index: AclsFuL7HiwyV1hsRaS7bpAYgNGURQAWpUKQ
Cc: 'RRG' <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org


Hi Paul, 

|ICBW, but I think you're describing what's been called the "Memory 
|wall" by Wulf & McKee:
|
|  http://www.cs.virginia.edu/papers/Hitting_Memory_Wall-wulf94.pdf
|
|and see also:
|
|  http://www.csl.cornell.edu/~sam/papers/cf04.pdf


Thank you for the excellent references, I think they're exactly on point.
Routing is simply one of the applications that is going to hit the memory
wall.

Tony

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan  1 16:40:27 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ED2BD3A6A24;
	Thu,  1 Jan 2009 16:40:26 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 50BDC3A69CE
	for <rrg@core3.amsl.com>; Thu,  1 Jan 2009 16:40:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[AWL=0.048, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 5zaMFTxyKvVl for <rrg@core3.amsl.com>;
	Thu,  1 Jan 2009 16:40:25 -0800 (PST)
Received: from QMTA08.emeryville.ca.mail.comcast.net
	(qmta08.emeryville.ca.mail.comcast.net [76.96.30.80])
	by core3.amsl.com (Postfix) with ESMTP id A1D5E3A686A
	for <rrg@irtf.org>; Thu,  1 Jan 2009 16:40:25 -0800 (PST)
Received: from OMTA03.emeryville.ca.mail.comcast.net ([76.96.30.27])
	by QMTA08.emeryville.ca.mail.comcast.net with comcast
	id yPny1a01m0b6N64A8QgF8V; Fri, 02 Jan 2009 00:40:15 +0000
Received: from TONYLTM9XP ([155.53.1.254])
	by OMTA03.emeryville.ca.mail.comcast.net with comcast
	id yQg21a0015Up7oj8PQg4RG; Fri, 02 Jan 2009 00:40:13 +0000
From: "Tony Li" <tony.li@tony.li>
To: "'Brian E Carpenter'" <brian.e.carpenter@gmail.com>,
	"'Scott Brim'" <swb@employees.org>, <rrg@irtf.org>
References: <3c3e3fca0812310857y14a8233ag953a9441279a25b5@mail.gmail.com>	<EC6C5330-557A-4D5F-8FF9-10A639806C6C@extremenetworks.com><20090101205959.GF9477@cisco.com>
	<495D47E3.7040304@gmail.com>
Date: Thu, 1 Jan 2009 16:39:13 -0800
Message-ID: <A7F21AA1C42F465FB8FCE76D9730F4CF@ad.redback.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
In-Reply-To: <495D47E3.7040304@gmail.com>
Thread-Index: AclsYvwqqvUCEsUORRmmvP8XJo4KaQAD2XFg
Subject: Re: [rrg] solution strategies, nat?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

 

|Certainly. So if you were product manager for a highly reliable
|distributed application, I'm sure you would insist that it was
|coded to detect permanent transport failures and try alternative
|addresses. That may not be elegant computer science but it's one
|way that the Internet routes around damage.


And that again results in trying to fix the routing architecture at layers 7
and 8.  You'll pardon me if I don't find that a particularly satisfying
'solution'.

Tony

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan  1 17:08:13 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ADEE73A6AC5;
	Thu,  1 Jan 2009 17:08:13 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3B8C03A6A24
	for <rrg@core3.amsl.com>; Thu,  1 Jan 2009 17:08:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.553
X-Spam-Level: 
X-Spam-Status: No, score=-2.553 tagged_above=-999 required=5 tests=[AWL=0.046, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id MOXuKDDQVPpA for <rrg@core3.amsl.com>;
	Thu,  1 Jan 2009 17:08:11 -0800 (PST)
Received: from QMTA07.emeryville.ca.mail.comcast.net
	(qmta07.emeryville.ca.mail.comcast.net [76.96.30.64])
	by core3.amsl.com (Postfix) with ESMTP id 6478E3A69CE
	for <rrg@irtf.org>; Thu,  1 Jan 2009 17:08:11 -0800 (PST)
Received: from OMTA07.emeryville.ca.mail.comcast.net ([76.96.30.59])
	by QMTA07.emeryville.ca.mail.comcast.net with comcast
	id yLQT1a0081GXsucA7R807R; Fri, 02 Jan 2009 01:08:00 +0000
Received: from TONYLTM9XP ([155.53.1.254])
	by OMTA07.emeryville.ca.mail.comcast.net with comcast
	id yR7m1a00F5Up7oj8TR7oZ6; Fri, 02 Jan 2009 01:07:58 +0000
From: "Tony Li" <tony.li@tony.li>
To: "'William Herrin'" <bill@herrin.us>,
	"'RJ Atkinson'" <rja@extremenetworks.com>
References: <3c3e3fca0812310857y14a8233ag953a9441279a25b5@mail.gmail.com><EC6C5330-557A-4D5F-8FF9-10A639806C6C@extremenetworks.com><3c3e3fca0812311715r5cad842elfba98f56596bd033@mail.gmail.com><B761BA80-6FD2-4D83-89C2-ACDC521E8574@extremenetworks.com>
	<3c3e3fca0901010837h34a191e9r7dacb7fc504ff15b@mail.gmail.com>
Date: Thu, 1 Jan 2009 17:06:55 -0800
Message-ID: <EDF52BB5C1194991BA849302ADA869D5@ad.redback.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
In-Reply-To: <3c3e3fca0901010837h34a191e9r7dacb7fc504ff15b@mail.gmail.com>
Thread-Index: AclsL0hb/mPo3KTcTpSaf7cIqsW9LwAQ+6Pw
Cc: 'IRTF Routing RG' <rrg@irtf.org>
Subject: Re: [rrg] solution strategies, nat?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

 
Hi all,


|>> We have determined beyond the shadow of a doubt
|>> that the status quo is not, at this time, self-reducing.
|>
|> Under IRTF process rules, only the RG Chairs have the authority
|> to make a consensus determination.
|
|That is an... interesting... refutation of established fact.


<co-chair>

I'm unaware of what established facts those might be.  Let me set forth the
facts as I know them:

The IRTF operates under the procedures documented in RFC 2014, and under the
direction of the IRTF Chair.  Most significantly, we have been instructed by
the IRTF Chair to operate openly.  Within the bounds of those restrictions,
the RRG Chairs are free to set their own process, and we have many times
reiterated that we choose to operate under the "rough consensus" process
that the IETF normally uses.  We have selected this process specifically
because we feel that without the buy in of the majority of the stakeholders,
any architectural recommendation that we might make would be simply so much
hot air.  Note that this is a decision that is wholly local to the RRG and
other IRTF RGs may have a variety of different processes.

Per the "rough consensus" approach, as documented in RFC 2418, it is the
responsibility of the Chairs to determine if we have reached rough
consensus.  See section 3.3 of RFC 2418.

That said, please note that that does NOT mean that Bill is out-of-bounds in
conducting his own, unofficial consensus checks, nor is he out-of-bounds in
holding his own opinion of what the consensus is, nor in opining about what
that consensus is.  Those are simply unofficial opinions and do not
represent the official consensus of the RRG.  

Please also note that the RRG co-chairs reserve the right to change the
official processes of the RG in the future, as needs arise.

I hope this clarifies any process questions.

</co-chair>

Happy Gregorian New Year,
Tony



_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan  1 17:55:50 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4ACFB3A6AC5;
	Thu,  1 Jan 2009 17:55:50 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 53D833A6AC5
	for <rrg@core3.amsl.com>; Thu,  1 Jan 2009 17:55:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.606
X-Spam-Level: 
X-Spam-Status: No, score=-1.606 tagged_above=-999 required=5 tests=[AWL=0.289, 
	BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id gds2akDd9-I6 for <rrg@core3.amsl.com>;
	Thu,  1 Jan 2009 17:55:48 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123])
	by core3.amsl.com (Postfix) with ESMTP id 3CFDC3A67FD
	for <rrg@irtf.org>; Thu,  1 Jan 2009 17:55:48 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6])
	by gair.firstpr.com.au (Postfix) with ESMTP id 23C14175B53;
	Fri,  2 Jan 2009 12:55:35 +1100 (EST)
Message-ID: <495D741B.7000608@firstpr.com.au>
Date: Fri, 02 Jan 2009 12:55:39 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: rrg@irtf.org
References: <3c3e3fca0812310857y14a8233ag953a9441279a25b5@mail.gmail.com>	<EC6C5330-557A-4D5F-8FF9-10A639806C6C@extremenetworks.com>	<20090101205959.GF9477@cisco.com>
	<495D47E3.7040304@gmail.com>
In-Reply-To: <495D47E3.7040304@gmail.com>
Subject: Re: [rrg] solution strategies, nat? Herrin's Architectural Principle
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Ran Atkinson wrote:

>>> (NAT/NAPT or LocatorRewriting or pick a another name) performed
>>> inside a site's border router can enable a site to multi-home
>>> effectively without any de-aggregation (i.e. without any impact on
>>> the DFZ RIB or DFZ FIB).  Existing mechanisms that enable
>>> distributed firewalls to share session state would clearly also work
>>> to share NAT session state among a set of site border routers, if
>>> that were desired.

Scott Brim wrote:

>> Multihoming on different providers?  If an endpoint appears to have
>> two different addresses due to being NATted onto two different
>> providers, and routing changes so that packets switch from flowing
>> through one provider to flowing through the other one, connections
>> break.

Brian Carpenter wrote:

> Certainly. So if you were product manager for a highly reliable
> distributed application, I'm sure you would insist that it was
> coded to detect permanent transport failures and try alternative
> addresses. That may not be elegant computer science but it's one
> way that the Internet routes around damage.

Tony Li wrote:

> And that again results in trying to fix the routing architecture at
> layers 7 and 8.  You'll pardon me if I don't find that a
> particularly satisfying 'solution'.

I agree.  Furthermore, it would be in violation of Herrin's
Architectural Principle:

   http://www.irtf.org/pipermail/rrg/2008-December/000620.html

     Any problem can be solved at the application layer for a single
     application. Architectural solutions solve the problem at a
     lower layer so that it stays solved for *all* applications.

This is a concise statement of good design principles which have long
been known in many fields - including networking, software, building
design and urban planning.

  - Robin


_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan  1 18:13:10 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B48B73A684C;
	Thu,  1 Jan 2009 18:13:10 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7D5303A684C
	for <rrg@core3.amsl.com>; Thu,  1 Jan 2009 18:13:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.559
X-Spam-Level: 
X-Spam-Status: No, score=-2.559 tagged_above=-999 required=5 tests=[AWL=0.040, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id e-qYU0SpMGc3 for <rrg@core3.amsl.com>;
	Thu,  1 Jan 2009 18:13:08 -0800 (PST)
Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.188])
	by core3.amsl.com (Postfix) with ESMTP id CEB113A67FD
	for <rrg@irtf.org>; Thu,  1 Jan 2009 18:13:07 -0800 (PST)
Received: by ti-out-0910.google.com with SMTP id b8so5061819tic.11
	for <rrg@irtf.org>; Thu, 01 Jan 2009 18:12:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from
	:organization:user-agent:mime-version:to:cc:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=JOGwSn/7kFvuI9nPNCweBlzA8F+2NBYijeTenT0qXrU=;
	b=vvCEMFxTCUHJFcK0IVHMIDorTv7hSe9O+V031WL+nQLhoNhf5fUJ640jTTrr0efdlu
	4cE/jrlDI1aavSl1nQB2Zt1bgWX7IgbGtXe2bh3z8/H59OK/w4j+C6WpHGEDke2s3jbg
	l2/1u9ucbxrEZycnnHJfSoRpvRBq7FZ73g1hM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	b=JzTsCY3iynTdSF9FXdCefeVHiH/o+B7eJNrNjuRf5fTCOwp480dFhIk9+N3aFJ6vY8
	e2AFKNKIWohiLu9gsqpyIG8KmitQjLsG60L0115DtMUpOC0bou6jHJTjFRovGONBRlsy
	Xsn8DsyVqFRBETa2dG/Hw+0PRGWdhW8AhT5XE=
Received: by 10.110.50.19 with SMTP id x19mr294075tix.57.1230862374205;
	Thu, 01 Jan 2009 18:12:54 -0800 (PST)
Received: from ?10.1.1.4? (118-92-137-11.dsl.dyn.ihug.co.nz [118.92.137.11])
	by mx.google.com with ESMTPS id i6sm8400642tid.16.2009.01.01.18.12.50
	(version=SSLv3 cipher=RC4-MD5); Thu, 01 Jan 2009 18:12:53 -0800 (PST)
Message-ID: <495D782E.40600@gmail.com>
Date: Fri, 02 Jan 2009 15:13:02 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: tony.li@tony.li
References: <3c3e3fca0812310857y14a8233ag953a9441279a25b5@mail.gmail.com>	<EC6C5330-557A-4D5F-8FF9-10A639806C6C@extremenetworks.com><20090101205959.GF9477@cisco.com>
	<495D47E3.7040304@gmail.com>
	<A7F21AA1C42F465FB8FCE76D9730F4CF@ad.redback.com>
In-Reply-To: <A7F21AA1C42F465FB8FCE76D9730F4CF@ad.redback.com>
Cc: rrg@irtf.org
Subject: Re: [rrg] solution strategies, nat?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On 2009-01-02 13:39, Tony Li wrote:
>  
> 
> |Certainly. So if you were product manager for a highly reliable
> |distributed application, I'm sure you would insist that it was
> |coded to detect permanent transport failures and try alternative
> |addresses. That may not be elegant computer science but it's one
> |way that the Internet routes around damage.
> 
> 
> And that again results in trying to fix the routing architecture at layers 7
> and 8.  You'll pardon me if I don't find that a particularly satisfying
> 'solution'.

It isn't, which is why we're here, I think.

To be clear what I'm thinking, it seems that if nothing new comes out
of the routing world, we'll eventually hit the wall where PI-style
multihoming cannot grow. Then economics will rule it out except for
very large customers. At that point, medium or small customers who want
multihoming will either have to use standard multi-prefix PA IPv6, or
NAT66 (assuming IPv4 addresses are exhausted by then). In both cases,
non-SCTP transport sessions will break when multihoming fails over.
The applications community will resolve that either by supporting
address failover at layer 7 or by converting to SCTP (or some
other agile transport).

    Brian
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan  1 19:43:08 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D33AD28C16C;
	Thu,  1 Jan 2009 19:43:08 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DA87428C16C
	for <rrg@core3.amsl.com>; Thu,  1 Jan 2009 19:43:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 2ws5PO-i7dP8 for <rrg@core3.amsl.com>;
	Thu,  1 Jan 2009 19:43:07 -0800 (PST)
Received: from QMTA09.emeryville.ca.mail.comcast.net
	(qmta09.emeryville.ca.mail.comcast.net [76.96.30.96])
	by core3.amsl.com (Postfix) with ESMTP id 4329228C165
	for <rrg@irtf.org>; Thu,  1 Jan 2009 19:43:07 -0800 (PST)
Received: from OMTA11.emeryville.ca.mail.comcast.net ([76.96.30.36])
	by QMTA09.emeryville.ca.mail.comcast.net with comcast
	id yErW1a00E0mlR8UA9TivVn; Fri, 02 Jan 2009 03:42:55 +0000
Received: from TONYLTM9XP ([24.6.155.154])
	by OMTA11.emeryville.ca.mail.comcast.net with comcast
	id yTit1a0013L8a8Q8XTitUP; Fri, 02 Jan 2009 03:42:54 +0000
From: "Tony Li" <tony.li@tony.li>
To: "'Brian E Carpenter'" <brian.e.carpenter@gmail.com>
References: <3c3e3fca0812310857y14a8233ag953a9441279a25b5@mail.gmail.com>	<EC6C5330-557A-4D5F-8FF9-10A639806C6C@extremenetworks.com><20090101205959.GF9477@cisco.com>
	<495D47E3.7040304@gmail.com>
	<A7F21AA1C42F465FB8FCE76D9730F4CF@ad.redback.com>
	<495D782E.40600@gmail.com>
Date: Thu, 1 Jan 2009 19:42:49 -0800
Message-ID: <8742FBE8C6714C6F90CEEC5EEF938436@ad.redback.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
In-Reply-To: <495D782E.40600@gmail.com>
Thread-Index: Aclsf6McK3Hlee1RSLKF0UYo+ud8EgADCPSQ
Cc: rrg@irtf.org
Subject: Re: [rrg] solution strategies, nat?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

 

|To be clear what I'm thinking, it seems that if nothing new comes out
|of the routing world, we'll eventually hit the wall where PI-style
|multihoming cannot grow. Then economics will rule it out except for
|very large customers. 


Or, in another form, the cost per global prefix will grow (in constant
dollars).  One alternative at this point is that folks simply stop accepting
global prefixes, but given that the incentives of the carriers are clearly
slanted towards accepting everything, it's more likely that prefixes are
accepted, despite increased costs.  Given the current economic model, that
implies that the cost basis for ISPs rise and they pass along costs to all
consumers.

Tony


_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Fri Jan  2 04:08:34 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 38E1D3A688F;
	Fri,  2 Jan 2009 04:08:34 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CE2933A688F
	for <rrg@core3.amsl.com>; Fri,  2 Jan 2009 04:08:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.019
X-Spam-Level: 
X-Spam-Status: No, score=-1.019 tagged_above=-999 required=5 tests=[AWL=0.183, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Yo-CRrADInoF for <rrg@core3.amsl.com>;
	Fri,  2 Jan 2009 04:08:27 -0800 (PST)
Received: from imo-d20.mx.aol.com (imo-d20.mx.aol.com [205.188.139.136])
	by core3.amsl.com (Postfix) with ESMTP id 564413A6878
	for <rrg@irtf.org>; Fri,  2 Jan 2009 04:08:27 -0800 (PST)
Received: from HeinerHummel@aol.com
	by imo-d20.mx.aol.com  (mail_out_v39.1.) id i.bf4.418c3cd1 (30740);
	Fri, 2 Jan 2009 07:08:02 -0500 (EST)
From: HeinerHummel@aol.com
Message-ID: <bf4.418c3cd1.368f5da1@aol.com>
Date: Fri, 2 Jan 2009 07:08:01 EST
To: tony.li@tony.li, paul@clubi.ie
MIME-Version: 1.0
X-Mailer: 9.0 SE for Windows sub 5021
Cc: rrg@irtf.org
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2042985755=="
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org


--===============2042985755==
Content-Type: multipart/alternative; boundary="-----------------------------1230898081"


-------------------------------1230898081
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

=20
In einer eMail vom 02.01.2009 01:34:12 Westeurop=E4ische Normalzeit schreibt=
 =20
tony.li@tony.li:

ICBW,  but I think you're describing what's been called the "Memory=20
|wall" by  Wulf & McKee:
|
|   http://www.cs.virginia.edu/papers/Hitting_Memory_Wall-wulf94.pdf
|
|and  see also:
|
|   http://www.csl.cornell.edu/~sam/papers/cf04.pdf


Thank you for the  excellent references, I think they're exactly on point.
Routing is simply  one of the applications that is going to hit the  memory
wall.



Thanks for these very interesting documents.It tells me: after the ignoring=20=
=20
phase and now the rejection phase TARA will still get -within a decade- its=20=
=20
chance. Not because of eliminating the update churn or the table size proble=
m =20
but for eliminating the need to cache at any  transit-router.
=20
Ignoring phase:
I am still waiting for the promised detailed response by Lixia, or for =20
Bill's explanation why a link-state protocol cannot express the same policy=20=
as a =20
DV protocol, and -wrt to the above - I only got collective silence when I sa=
id =20
in spite of 300 000 stored routes DV does only enable one third of them, ie=20
that  twice the number cannot be provided.Very very rougly. Let me eloborate=
=20
more  on this factor by the following example:
=20
Imagine destination node d surrounded by a tightly meshed network such that=20=
=20
each node has 6 neighbor nodes whereby 2 are closer, 2 are equidistant and 2=
=20
are  more remote wrt to d. Now assume a source node s being 10 hops away fro=
m d=20
and  let us consider the number of different paths (differing at least by on=
e=20
 hop):
Dijkstra provides 1 path. ECMP provides 2^10 paths (at least this is what I=20=
=20
accredit to/expect from ECMP). My own algorithm provides 6^10 paths. This is=
=20
not  just twice but 3^10 times  what can ECMP (and DV ?)provide. These are s=
uch=20
 extremely big numbers that you don't want to store a single route of them,=20=
=20
instead look for a more intelligent mechanism.Keep in mind the average path=20=
=20
length is said to be 20, not 10.
=20
Heiner

-------------------------------1230898081
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3DISO-8859-1">
<META content=3D"MSHTML 6.00.6000.16788" name=3DGENERATOR></HEAD>
<BODY id=3Drole_body style=3D"FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY:=20=
Arial"=20
bottomMargin=3D7 leftMargin=3D7 topMargin=3D7 rightMargin=3D7><FONT id=3Drol=
e_document=20
face=3DArial color=3D#000000 size=3D2>
<DIV>
<DIV>In einer eMail vom 02.01.2009 01:34:12 Westeurop=E4ische Normalzeit sch=
reibt=20
tony.li@tony.li:</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid"><=
FONT=20
  style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000 size=
=3D2>ICBW,=20
  but I think you're describing what's been called the "Memory <BR>|wall" by=
=20
  Wulf &amp; McKee:<BR>|<BR>|&nbsp;=20
  http://www.cs.virginia.edu/papers/Hitting_Memory_Wall-wulf94.pdf<BR>|<BR>|=
and=20
  see also:<BR>|<BR>|&nbsp;=20
  http://www.csl.cornell.edu/~sam/papers/cf04.pdf<BR><BR><BR>Thank you for t=
he=20
  excellent references, I think they're exactly on point.<BR>Routing is simp=
ly=20
  one of the applications that is going to hit the=20
memory<BR>wall.<BR></FONT></BLOCKQUOTE></DIV>
<DIV></DIV>
<DIV>Thanks for these very interesting documents.It tells me: after the igno=
ring=20
phase and now the rejection phase TARA will still get -within a decade- its=20
chance. Not because of eliminating the update churn or the table size proble=
m=20
but for eliminating the need to cache at any&nbsp; transit-router.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Ignoring phase:</DIV>
<DIV>I am still waiting for the promised detailed response by Lixia, or for=20
Bill's explanation why a link-state protocol cannot express the same policy=20=
as a=20
DV protocol, and -wrt to the above - I only got collective silence when I sa=
id=20
in spite of 300 000 stored routes DV does only enable one third of them, ie=20=
that=20
twice the number cannot be provided.Very very rougly. Let me eloborate more=20
on&nbsp;this factor&nbsp;by the following example:</DIV>
<DIV>&nbsp;</DIV>
<DIV>Imagine destination node d surrounded by a tightly meshed network such=20=
that=20
each node has 6 neighbor nodes whereby 2 are closer, 2 are equidistant and 2=
 are=20
more remote wrt to d. Now assume a source node s being 10 hops away from d a=
nd=20
let us consider the number of different paths (differing at least by one=20
hop):</DIV>
<DIV>Dijkstra provides 1 path. ECMP provides 2^10 paths (at least this is wh=
at I=20
accredit to/expect from ECMP). My own algorithm provides 6^10 paths. This is=
 not=20
just twice but 3^10 times&nbsp; what can ECMP (and DV ?)provide. These are s=
uch=20
extremely big numbers that you don't want to store a single route of them,=20
instead look for a more intelligent mechanism.Keep in mind the average path=20
length is said to be 20, not 10.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Heiner</DIV></FONT></BODY></HTML>

-------------------------------1230898081--

--===============2042985755==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg

--===============2042985755==--


From rrg-bounces@irtf.org  Fri Jan  2 06:17:24 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B66393A6935;
	Fri,  2 Jan 2009 06:17:24 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0F56E3A6922
	for <rrg@core3.amsl.com>; Fri,  2 Jan 2009 06:17:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.266
X-Spam-Level: 
X-Spam-Status: No, score=-3.266 tagged_above=-999 required=5
	tests=[AWL=-0.667, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6yBwOVaxmUef for <rrg@core3.amsl.com>;
	Fri,  2 Jan 2009 06:17:22 -0800 (PST)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net
	[217.115.75.234])
	by core3.amsl.com (Postfix) with ESMTP id 8EBDA3A6935
	for <rrg@irtf.org>; Fri,  2 Jan 2009 06:17:21 -0800 (PST)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55])
	by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id
	n02EH7jj028758
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <rrg@irtf.org>; Fri, 2 Jan 2009 15:17:07 +0100
Received: from demuexc023.nsn-intra.net (webmail.nsn-intra.net [10.150.128.36])
	by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP
	id n02EH7IM026245 for <rrg@irtf.org>; Fri, 2 Jan 2009 15:17:07 +0100
Received: from FIESEXC014.nsn-intra.net ([10.159.0.22]) by
	demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 2 Jan 2009 15:17:07 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 2 Jan 2009 16:17:06 +0200
Message-ID: <2B5F3EA7272CFF47A66518E4FF3BE2350251BA3A@FIESEXC014.nsn-intra.net>
In-Reply-To: <3c3e3fca0812300732n31c11183n34da95f24650b9e8@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] Consensus call: Reject proposed strategy F?
Thread-Index: Aclqk/jJKXVk++DhQN2i3LmN0sUBEQCT23cg
References: <3c3e3fca0812231929s233ffdbavb24ae9cf7d6c091a@mail.gmail.com><49592F54.60600@gmail.com><3c3e3fca0812291235w4707f0c1k19e5f7af8b44be94@mail.gmail.com><49593CB8.2080101@gmail.com><3c3e3fca0812291429r33e96b46le91ea9e4630a27bc@mail.gmail.com><49595152.8090606@joelhalpern.com><3525C9833C09ED418C6FD6CD9514668C0559C120@emailwf1.jnpr.net>
	<3c3e3fca0812300732n31c11183n34da95f24650b9e8@mail.gmail.com>
From: "Flinck, Hannu (NSN - FI/Espoo)" <hannu.flinck@nsn.com>
To: <rrg@irtf.org>
X-OriginalArrivalTime: 02 Jan 2009 14:17:07.0306 (UTC)
	FILETIME=[CB2124A0:01C96CE4]
Subject: Re: [rrg] Consensus call: Reject proposed strategy F?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org


 Hello Bill 

Thank you for a good and concise summary of the various strategies for
routing scalability.

Related to your question about other BGP solutions, I am wondering how
well strategy D covers the proposals by Paul Francis and others:

- mapped BGP and
- virtual aggregation.

The former requires some extensions to BGP, in terms of announcing the
proper attributes for the maps and also its own RIBs. Rephrasing
strategy D to "Use plain old BGP with extensions" would capture the
mentioned BGP based solutions as well. (Notice that Paul's presentation
in the last meeting starts with "tries to minimize changes to BGP", is
not the same as "use the old BGP".)

Best regards
Hannu  

>-----Original Message-----
>From: rrg-bounces@irtf.org [mailto:rrg-bounces@irtf.org] On 
>Behalf Of ext William Herrin
>Sent: Tuesday, December 30, 2008 17:33
>To: Ross Callon
>Cc: RRG
>Subject: Re: [rrg] Consensus call: Reject proposed strategy F?
>
>On Tue, Dec 30, 2008 at 12:55 AM, Ross Callon 
><rcallon@juniper.net> wrote:
>>> > I say we should tell the folks in GROW that it's time to stop 
>>> > seriously entertaining the idea that vanilla BGP 
>(strategy F) will 
>>> > work out ok. What do you say?
>>>
>>> Firstly, given that there are useful things to do with BGP, 
>that will 
>>> extend its life, I don't think it would at all be 
>appropriate to tell 
>>> GROW not to put energy into engineering improvements.
>>
>> I agree with Joel that it would be seriously inappropriate to tell 
>> GROW (or IDR) to stop thinking about engineering improvements to BGP.
>
>
>Ross,
>
>Are there BGP improvements for which consideration is ripe, 
>yet which aren't described in the solutions summary? They 
>should have been mentioned in the months this document was 
>open to casual additions but for the rest of this week I'm 
>willing to cut a little slack.
>
>Strategy F is not "continue researching BGP improvements." 
>Strategy F is "BGP is good enough already."
>
>Do you accept the claim that BGP can be expected to remain 
>viable for the foreseeable future even if none of the 
>improvements we've considered pan out? If not, you should 
>reject strategy F.
>
>Regards,
>Bill Herrin
>
>
>--
>William D. Herrin ................ herrin@dirtside.com  bill@herrin.us
>3005 Crane Dr. ...................... Web: 
><http://bill.herrin.us/> Falls Church, VA 22042-3004 
>_______________________________________________
>rrg mailing list
>rrg@irtf.org
>https://www.irtf.org/mailman/listinfo/rrg
>
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Fri Jan  2 06:30:37 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2596A3A6935;
	Fri,  2 Jan 2009 06:30:37 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 506CF3A6935
	for <rrg@core3.amsl.com>; Fri,  2 Jan 2009 06:30:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.519
X-Spam-Level: 
X-Spam-Status: No, score=-6.519 tagged_above=-999 required=5 tests=[AWL=0.080, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id RboLWA70zf99 for <rrg@core3.amsl.com>;
	Fri,  2 Jan 2009 06:30:35 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id 931B13A692D
	for <rrg@irtf.org>; Fri,  2 Jan 2009 06:30:35 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.36,318,1228089600"; d="scan'208";a="126436628"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by sj-iport-3.cisco.com with ESMTP; 02 Jan 2009 14:30:23 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n02EUMCq024648
	for <rrg@irtf.org>; Fri, 2 Jan 2009 09:30:22 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n02EUMf2026649
	for <rrg@irtf.org>; Fri, 2 Jan 2009 14:30:22 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 2 Jan 2009 09:30:22 -0500
Received: from cisco.com ([64.102.8.172]) by xfe-rtp-202.amer.cisco.com with
	Microsoft SMTPSVC(6.0.3790.1830); Fri, 2 Jan 2009 09:30:21 -0500
Date: Fri, 2 Jan 2009 09:30:14 -0500
From: Scott Brim <swb@employees.org>
To: rrg@irtf.org
Message-ID: <20090102143014.GB87828@cisco.com>
Mail-Followup-To: Scott Brim <swb@employees.org>, rrg@irtf.org
References: <3c3e3fca0812231929s233ffdbavb24ae9cf7d6c091a@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <3c3e3fca0812231929s233ffdbavb24ae9cf7d6c091a@mail.gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-OriginalArrivalTime: 02 Jan 2009 14:30:22.0386 (UTC)
	FILETIME=[A508B920:01C96CE6]
Authentication-Results: rtp-dkim-2; header.From=swb@employees.org; dkim=neutral
Subject: Re: [rrg] Consensus call: Reject proposed strategy F?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Bill, I just got back from extended time away from mail.  Does "do
nothing" mean do nothing at lower layers?  Does "do nothing" include
the possibility of doing something compensatory at higher layers?

swb

Excerpts from William Herrin on Tue, Dec 23, 2008 10:29:35PM -0500:
> Hi Folks,
> =

> The Summary of Routing Architectures discussed in the RRG, posted at
> http://bill.herrin.us/network/rrgarchitectures.html includes:
> =

>   Strategy F.
> =

>   Do nothing. (RFC 1887 =A7 4.4.1)
> =

> I propose that we REJECT strategy F.
> =

> As we use it now, BGP lacks sufficient scalability to see the
> Internet into the coming decades. We constrain the growth of the BGP
> RIB by disadvantaging small, innovative organizations when they seek
> IP addresses from the regional registries. We constrain the growth
> of the BGP RIB by refusing to offer consumer level broadband
> products capable of multihoming. Then we spend some $2B per year
> getting the routes that do make it into BGP to work. [Herrin BGP
> Cost]  This damages the Internet, damages invention and ultimately
> damages us.
> =

> I ask you to post either, "I AGREE that we should reject strategy F"
> or "I DISAGREE; strategy F should continue to be considered.". I'd
> also appreciate a few words about why or why not.
> =

> If we have a strong consensus to reject strategy F, the Summary of
> Routing Architectures will be updated to reflect that we have
> considered and rejected it.
> =

> Regards, Bill Herrin
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Fri Jan  2 07:26:01 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 12A2C3A687B;
	Fri,  2 Jan 2009 07:26:01 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 353D93A687B
	for <rrg@core3.amsl.com>; Fri,  2 Jan 2009 07:26:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.963
X-Spam-Level: 
X-Spam-Status: No, score=-1.963 tagged_above=-999 required=5 tests=[AWL=0.014, 
	BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id xuDwvJTY3v41 for <rrg@core3.amsl.com>;
	Fri,  2 Jan 2009 07:25:59 -0800 (PST)
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.179])
	by core3.amsl.com (Postfix) with ESMTP id 526E43A6832
	for <rrg@irtf.org>; Fri,  2 Jan 2009 07:25:59 -0800 (PST)
Received: by wa-out-1112.google.com with SMTP id j37so3553964waf.23
	for <rrg@irtf.org>; Fri, 02 Jan 2009 07:25:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:sender
	:to:subject:cc:mime-version:content-type:content-transfer-encoding
	:content-disposition:x-google-sender-auth;
	bh=3AuzwfFaelg6dXSkkmwVRoypAajFm132n6GS+hBEuvM=;
	b=NpmgyNh7pMkksJEZy8coI9PvVIkPjQ3vRLXgopphUwkj6Y1pNbsjjNhSUynPDxrsVd
	p2UeqlNdWAgSjJz/0QMTTgHktyQWPEDIZs3GBAQBqQ38QD7wjQ+PiTSeaky3ZUeQltLD
	kZIVR6epti8sCQLp1PE/pisHtW84OdtpRZoJ0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:sender:to:subject:cc:mime-version:content-type
	:content-transfer-encoding:content-disposition:x-google-sender-auth;
	b=O8JA8prOa/bNW211flpZ4cSF+YFXgYUWmA8IOUoMUBzWeTKQq3VfyNJV9Ajl+jgJVk
	aEBlQNYLSAPHSXr2oz/S225BfZrAC2hBeU6ndy6Voa3VTmWpYCec6aamsJd7qM7p54yi
	/BZUfeEAbLfwPwWEQSQ5nm9O8GOYiXoBFo7xM=
Received: by 10.114.211.2 with SMTP id j2mr2278554wag.139.1230909946214;
	Fri, 02 Jan 2009 07:25:46 -0800 (PST)
Received: by 10.115.74.12 with HTTP; Fri, 2 Jan 2009 07:25:46 -0800 (PST)
Message-ID: <3c3e3fca0901020725i1a5b154at78f9edc7f36f6a5e@mail.gmail.com>
Date: Fri, 2 Jan 2009 10:25:46 -0500
From: "William Herrin" <bill@herrin.us>
To: "Flinck, Hannu (NSN - FI/Espoo)" <hannu.flinck@nsn.com>
MIME-Version: 1.0
Content-Disposition: inline
X-Google-Sender-Auth: 89901269a8aebf06
Cc: rrg@irtf.org
Subject: [rrg] Solution space summary: late addition?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On Fri, Jan 2, 2009 at 9:17 AM, Flinck, Hannu (NSN - FI/Espoo)
<hannu.flinck@nsn.com> wrote:
> Thank you for a good and concise summary of the various strategies for
> routing scalability.
>
> Related to your question about other BGP solutions, I am wondering how
> well strategy D covers the proposals by Paul Francis and others:
>
> - mapped BGP and
> - virtual aggregation.

Hi Hannu,

Was that the one where MPLS is modified to specify an exit instead of
an exit router and then the RIB and FIB both are split to multiple
routers, the split accomplished by applying short netmasks?

Nuts, I think that's probably a missed strategy. Parallelize RIB
processing, and that's one of at least two variants. The other is
parallel processing of the BGP RIB on a single router which then folds
into a single FIB.

Does anyone object to adding it late as strategy H?

Regards,
Bill Herrin



-- 
William D. Herrin ................ herrin@dirtside.com  bill@herrin.us
3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
Falls Church, VA 22042-3004
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Fri Jan  2 08:38:05 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3B40B3A69F2;
	Fri,  2 Jan 2009 08:38:05 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 30CBD28C0DD
	for <rrg@core3.amsl.com>; Fri,  2 Jan 2009 08:38:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.113
X-Spam-Level: 
X-Spam-Status: No, score=-6.113 tagged_above=-999 required=5
	tests=[AWL=-0.114, BAYES_00=-2.599, J_CHICKENPOX_45=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id dxmqd7q30pWA for <rrg@core3.amsl.com>;
	Fri,  2 Jan 2009 08:38:03 -0800 (PST)
Received: from exprod7og115.obsmtp.com (exprod7ob115.obsmtp.com [64.18.2.216])
	by core3.amsl.com (Postfix) with ESMTP id 458E33A69BD
	for <rrg@irtf.org>; Fri,  2 Jan 2009 08:38:03 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by
	exprod7ob115.postini.com ([64.18.6.12]) with SMTP
	ID DSNKSV5C1IcfG+y932rWX8ccljoOBhnivDMe@postini.com;
	Fri, 02 Jan 2009 08:37:51 PST
Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net
	(172.24.192.35) with Microsoft SMTP Server id 8.1.336.0;
	Fri, 2 Jan 2009 08:30:43 -0800
Received: from p-emlb02-sac.jnpr.net ([66.129.254.47]) by
	p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959);
	Fri, 2 Jan 2009 08:30:43 -0800
Received: from emailwf1.jnpr.net ([10.10.2.33]) by p-emlb02-sac.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.3959);	 Fri, 2 Jan 2009 08:30:43 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 2 Jan 2009 11:30:42 -0500
Message-ID: <3525C9833C09ED418C6FD6CD9514668C0566043E@emailwf1.jnpr.net>
In-Reply-To: <1230828437.2961.38.camel@localhost.localdomain>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] BGP scaling limit?
Thread-Index: AclsMJ8e3Ai5tWQqTqGoWFBwgq7fdwAwOlgw
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com><75cb24520812311427m31d4dae0nd5c37130cc485eaf@mail.gmail.com><495C3FB6.8030808@firstpr.com.au>
	<1230828437.2961.38.camel@localhost.localdomain>
From: Ross Callon <rcallon@juniper.net>
To: "Steven Blake" <slblake@petri-meat.com>,
	"Robin Whittle" <rw@firstpr.com.au>
X-OriginalArrivalTime: 02 Jan 2009 16:30:43.0262 (UTC)
	FILETIME=[7502F5E0:01C96CF7]
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Early on in this discussion engineers from multiple router vendors
stated publicly that that their engineers knew how to build routers that
would handle FIBs that were at least 4M entries or more (10M was
mentioned), using commodity hardware parts. It also became clear, at
least to a few of us talking on the side, that what the hardware guys
were telling one router vendor, in terms of what memory parts they will
have in a few years, is the same thing that they are telling other
router vendors. In various private conversations it also became clear to
me that the router hardware engineers working on the hardware forwarding
parts of routers were not even considering any major change to the
architecture, for the simple reason that they didn't need to.

There may be many reasons to consider making a major change to the way
that the Internet does routing and addressing, but the inability to
build equipment that can handle several million entries is NOT a valid
reason. 

Ross

-----Original Message-----
From: rrg-bounces@irtf.org [mailto:rrg-bounces@irtf.org] On Behalf Of
Steven Blake
Sent: 01 January 2009 11:47
To: Robin Whittle
Cc: RRG
Subject: Re: [rrg] BGP scaling limit?

On Thu, 2009-01-01 at 14:59 +1100, Robin Whittle wrote:

> Short version:  Limits on using PC hardware for router FIBs.
>                 Fast SRAM is needed, not DRAM.

[snip]

One can build a 4M+ prefix, 300M LPM/sec FIB engine (v4 or v6) using
commercially available FPGA + DDR3.

Regarding RIB processing: I'll accept the argument that rate*state
growth is exceeding Moore's Law.  However, most RPs I've seen are anemic
compared to commodity server hardware (for legitimate reasons).  So
there is plenty of room for improvement here.


Regards,

// Steve

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Fri Jan  2 10:11:37 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 718823A67F9;
	Fri,  2 Jan 2009 10:11:37 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DE4A83A67F9
	for <rrg@core3.amsl.com>; Fri,  2 Jan 2009 10:11:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.964
X-Spam-Level: 
X-Spam-Status: No, score=-1.964 tagged_above=-999 required=5 tests=[AWL=0.013, 
	BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id syPrazrjD5EM for <rrg@core3.amsl.com>;
	Fri,  2 Jan 2009 10:11:27 -0800 (PST)
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.178])
	by core3.amsl.com (Postfix) with ESMTP id C24883A66B4
	for <rrg@irtf.org>; Fri,  2 Jan 2009 10:11:27 -0800 (PST)
Received: by wa-out-1112.google.com with SMTP id j37so3590068waf.23
	for <rrg@irtf.org>; Fri, 02 Jan 2009 10:11:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:sender
	:to:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references
	:x-google-sender-auth;
	bh=gOBk+RS8RHVUwBXDnNijKp62daIufY98o4m4VV0xxYA=;
	b=fzQ5oRdhVutNXqGrDP8B6y0qKHVW1fP+D2Jca3UMe+rA1IItVSC//02fyOj8rKTceD
	tsxTwvE373g9XDIMJT1rYCO+9TP0y7u4FoBpZiQ+wm2C4U8Rd8a4Y2cLUrsd+W2x/mwi
	9FFe2p/S2whZD63yZQ7b9BF3hDsopnHqd9Bp4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references:x-google-sender-auth;
	b=PGfSJNY0YEyxrTAftQGHeTqE9CbiTVxi9l1gq1Y57TcoNqM/MmVIToEdISv6J7KVui
	IGv7zvWJmsBa9GzP0hgNrXprLgnz+maJvKs/qaKV0HJ7OXtZlMeeuyul3Uz9Ds97tcoz
	cs5yWo1p0VZZXKlIIJbD1psusfK+APQkMrfp0=
Received: by 10.114.148.2 with SMTP id v2mr6432118wad.169.1230919874392;
	Fri, 02 Jan 2009 10:11:14 -0800 (PST)
Received: by 10.115.74.12 with HTTP; Fri, 2 Jan 2009 10:11:14 -0800 (PST)
Message-ID: <3c3e3fca0901021011y7143a8bai4119cc32312e1c62@mail.gmail.com>
Date: Fri, 2 Jan 2009 13:11:14 -0500
From: "William Herrin" <bill@herrin.us>
To: tony.li@tony.li
In-Reply-To: <EDF52BB5C1194991BA849302ADA869D5@ad.redback.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <3c3e3fca0812310857y14a8233ag953a9441279a25b5@mail.gmail.com>
	<EC6C5330-557A-4D5F-8FF9-10A639806C6C@extremenetworks.com>
	<3c3e3fca0812311715r5cad842elfba98f56596bd033@mail.gmail.com>
	<B761BA80-6FD2-4D83-89C2-ACDC521E8574@extremenetworks.com>
	<3c3e3fca0901010837h34a191e9r7dacb7fc504ff15b@mail.gmail.com>
	<EDF52BB5C1194991BA849302ADA869D5@ad.redback.com>
X-Google-Sender-Auth: 92e86c501f099612
Cc: RJ Atkinson <rja@extremenetworks.com>, IRTF Routing RG <rrg@irtf.org>
Subject: Re: [rrg] solution strategies, nat?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On Thu, Jan 1, 2009 at 8:06 PM, Tony Li <tony.li@tony.li> wrote:
> |>> We have determined beyond the shadow of a doubt
> |>> that the status quo is not, at this time, self-reducing.
> |>
> |> Under IRTF process rules, only the RG Chairs have the authority
> |> to make a consensus determination.
> |
> |That is an... interesting... refutation of established fact.
>
> I'm unaware of what established facts those might be.  Let me set forth the
> facts as I know them:
> The IRTF operates under the procedures documented in RFC 2014, and under the

Fellas,

Reality check!

The status quo is: the number of entries in the BGP table has
consistently grown and continues to grow year over year since BGP's
inception. See: http://bgp.potaroo.net/

Regardless of pronoun choice, no consensus call is necessary to cite
this well established fact. Had I overreached from this statement, you
might have cause to throw the rulebook at me. Since I didn't, you
don't.



> |To be clear what I'm thinking, it seems that if nothing new comes out
> |of the routing world, we'll eventually hit the wall where PI-style
> |multihoming cannot grow. Then economics will rule it out except for
> |very large customers.
>
> Or, in another form, the cost per global prefix will grow (in constant
> dollars).

Five bucks says the current trend is the opposite of this. If you
collect the cost data from yesteryear and apply the formula at
http://bill.herrin.us/network/bgpcost.html I bet you find that the
cost per BGP prefix has been gradually falling for some time.

Regards,
Bill Herrin



-- 
William D. Herrin ................ herrin@dirtside.com  bill@herrin.us
3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
Falls Church, VA 22042-3004
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Fri Jan  2 10:16:53 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 37C8F3A68D2;
	Fri,  2 Jan 2009 10:16:53 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8246C3A68D2
	for <rrg@core3.amsl.com>; Fri,  2 Jan 2009 10:16:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.964
X-Spam-Level: 
X-Spam-Status: No, score=-1.964 tagged_above=-999 required=5 tests=[AWL=0.013, 
	BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id A13YeWGSyizl for <rrg@core3.amsl.com>;
	Fri,  2 Jan 2009 10:16:51 -0800 (PST)
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.183])
	by core3.amsl.com (Postfix) with ESMTP id 518493A66B4
	for <rrg@irtf.org>; Fri,  2 Jan 2009 10:16:51 -0800 (PST)
Received: by wa-out-1112.google.com with SMTP id j37so3591164waf.23
	for <rrg@irtf.org>; Fri, 02 Jan 2009 10:16:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:sender
	:to:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references
	:x-google-sender-auth;
	bh=T527Z6nwpnPWvyqYGWJPM2k6cP2s0BPIaZsCGr8414Y=;
	b=FFRbCU0skm2Wm7LXjP4vqio3Hg8WCg1xk5kItrZSTzmn++94SWavkKtf4sNqMEmviA
	uE7E4QedKSERwHPvtyk0mQuYIftAe5+Ei7pVbbytVridIbjO/bIrOXSro9q1Aoti3FOz
	uYdpFRcRtihHyAV8QFO0v/F909O18ajRgVrDk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references:x-google-sender-auth;
	b=GQT0QPtAyEoJWA/HZCZH2jGrtMof0NbTzWtG9kU3tKNF61D20P5YgOztI7DlqYe1Tx
	7qkndPNLwWsipSxTAzxpxz6F+Q571e2pWtjOiHN4Z/f1nCGEwwKK9jlOJytAmtI3QWtZ
	CqVN+EMYvxRqZ2IRydQTp2DdxeibsRkQSVofU=
Received: by 10.115.75.14 with SMTP id c14mr11929210wal.86.1230920199251;
	Fri, 02 Jan 2009 10:16:39 -0800 (PST)
Received: by 10.115.74.12 with HTTP; Fri, 2 Jan 2009 10:16:39 -0800 (PST)
Message-ID: <3c3e3fca0901021016p11f1263bj93dd724bb5e5c555@mail.gmail.com>
Date: Fri, 2 Jan 2009 13:16:39 -0500
From: "William Herrin" <bill@herrin.us>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
In-Reply-To: <495D1CE7.9010107@gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <3c3e3fca0812310857y14a8233ag953a9441279a25b5@mail.gmail.com>
	<EC6C5330-557A-4D5F-8FF9-10A639806C6C@extremenetworks.com>
	<3c3e3fca0812311715r5cad842elfba98f56596bd033@mail.gmail.com>
	<B761BA80-6FD2-4D83-89C2-ACDC521E8574@extremenetworks.com>
	<3c3e3fca0901010837h34a191e9r7dacb7fc504ff15b@mail.gmail.com>
	<495D1CE7.9010107@gmail.com>
X-Google-Sender-Auth: 3275b14a3ab65ac7
Cc: RJ Atkinson <rja@extremenetworks.com>, IRTF Routing RG <rrg@irtf.org>
Subject: Re: [rrg] solution strategies, nat?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On Thu, Jan 1, 2009 at 2:43 PM, Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:
> On 2009-01-02 05:37, William Herrin wrote:
>> I insist on me being able to
>> satisfactorily explain how a particular approach would reduce the need
>> or demand for core routing slots.
>
> Slide 15 in
> http://www.cs.auckland.ac.nz/~brian/RRG0708.pdf


Thanks Brian.

I follow how slide 15 achieves reliable multihoming given two constraints:

1. System contains client machines. If it contains servers, they are
limited to those protocols which have a thoroughly defined layer-7
multihoming process, such as SMTP.
2. Loss of session during a multihoming event deemed acceptable.

I accept the proposition that some significant fraction of the
multihoming demand could be satisfied with a system meeting criteria
#2. Given a satisfactorily low rate of multihoming events, a pizza
joint is happy as long as the SIP phones immediately re-establish and
the web users can get the page by hitting reload.

I accept that slide 15 offers qualitatively different multihoming
versus slide 16 in that slide 15 does not require hosts to deal with
routing constructs with which they are not presently familiar. When
fleshed out to provide a complete multihoming solution, slide 16
evolves into strategy B.

Question:

What's the cause to believe that systems meeting criteria #1 represent
a more-than-negligible portion of the multihoming demand that is
either unserved or served by BGP?


You may choose to dispute criteria #1. Before you do, I remind you
that the primary API for access to the DNS (gethostbyname) is
irretrievably defective, at least as it pertains to providing an
ephemeral GUID to LOC map.


> So if you were product manager for a highly reliable
> distributed application, I'm sure you would insist that it was
> coded to detect permanent transport failures and try alternative
> addresses.

Like a web browser, let's say? Think HTTP handles this? Think again.
Once the browser successfully connects to a particular IP address for
a given server name, it nails itself to that address in order to avoid
an otherwise unsolvable javascript+DNS hacking vector.

Regards,
Bill Herrin

-- 
William D. Herrin ................ herrin@dirtside.com  bill@herrin.us
3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
Falls Church, VA 22042-3004
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Fri Jan  2 11:14:04 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2FE393A6805;
	Fri,  2 Jan 2009 11:14:04 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 67F193A6805
	for <rrg@core3.amsl.com>; Fri,  2 Jan 2009 11:14:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.964
X-Spam-Level: 
X-Spam-Status: No, score=-1.964 tagged_above=-999 required=5 tests=[AWL=0.013, 
	BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id CRZF6sbU5Bkn for <rrg@core3.amsl.com>;
	Fri,  2 Jan 2009 11:14:02 -0800 (PST)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.234])
	by core3.amsl.com (Postfix) with ESMTP id 54A3B3A67A1
	for <rrg@irtf.org>; Fri,  2 Jan 2009 11:13:58 -0800 (PST)
Received: by rv-out-0506.google.com with SMTP id f6so8010014rvb.7
	for <rrg@irtf.org>; Fri, 02 Jan 2009 11:13:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:sender
	:to:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references
	:x-google-sender-auth;
	bh=6j53edW4p29L7jfeZaOTQcvqhNVzUE3eC0Kz7U6uCNI=;
	b=H4phx52bnMn1CN0sJd5B5IPIYoIruNZLXGF4AU4IrcFntXmAux6C3C3t3E14X37RlP
	GBiXlieGR0X3wlQ5jwOvs57C+7k1vOu+lM2YNs2Iv1f3/AcAdV/VQp6eCuShZchHHzn6
	xytb5dsaXyXYycBQaXTTDnHdb5tO8+74dXKZE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references:x-google-sender-auth;
	b=rGe7RONgZgfJWV1kh7QkpAoqjmaq/bUp1/epCWQor0iLq51YWIJsyoWLO2tjqP5Lze
	1ComqtVkoxLCgDn0ScUo+YHxr8y13U6dLoNQfN5YC3b61jBAF5k4TJIi9FYaLdh05wlD
	okuWBYZ+C9yQavq+CujBkVn89U4hZAFlGhVYI=
Received: by 10.114.190.18 with SMTP id n18mr1526100waf.101.1230923625216;
	Fri, 02 Jan 2009 11:13:45 -0800 (PST)
Received: by 10.115.74.12 with HTTP; Fri, 2 Jan 2009 11:13:45 -0800 (PST)
Message-ID: <3c3e3fca0901021113u1aeff764n818ad2ef65a8b1e5@mail.gmail.com>
Date: Fri, 2 Jan 2009 14:13:45 -0500
From: "William Herrin" <bill@herrin.us>
To: "Christopher Morrow" <morrowc.lists@gmail.com>
In-Reply-To: <75cb24520812311536u6930dcd7o65394ae000c7b5f6@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com>
	<75cb24520812311427m31d4dae0nd5c37130cc485eaf@mail.gmail.com>
	<3c3e3fca0812311524o36bf8ae5k6837b7d15813685e@mail.gmail.com>
	<75cb24520812311536u6930dcd7o65394ae000c7b5f6@mail.gmail.com>
X-Google-Sender-Auth: bea947e62ade480d
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On Wed, Dec 31, 2008 at 6:36 PM, Christopher Morrow
<morrowc.lists@gmail.com> wrote:
>> Sure I can. My $2k COTS PC can route 500mbps easily. Packet switching
>
> sorry, of course you can make the assumption, I just don't think it
> follows as closely to reality as you'd want. that 500mbps isn't doing
> anything tough, with a small table, few interfaces, no services, no
> acls/filtering/qos ... consumer PC's just aren't a good correlary for
> backbone devices.

Hi Chris,

My hypothetical $2k PC is grounded in the recent NANOG discussion
entitled "gigabit Linux routers." The original poster in that
discussion specifically wanted to do BGP, filtering and shaping under
Linux. The NANOG discussion concluded that such a construct would
reasonably route between 700mbps and 1gbs on current hardware. It was
criticized as being less user-friendly and still buggier than a
purpose-built router.

So, according to the Ops, my $2k PC is validly comparable to a modern
core router at the 500mbps level, with plenty of headroom.


>> If you can move packets across an interface at the given data rate
>> then you can blindly multiplex and demultiplex packets from and to
>> lower speed interfaces. This reduces the problem to one previously
>> solved. There's doubtless a better solution but for conceptual
>> purposes, that eliminates the data rate boundary condition as an
>> active factor in the scalability assessment.
>
> at a gross level it might be comparable, but I'm not sure it
> helps cost a device that'll fit in a half-rack and push 1600gbps
> (T1600-juniper/ASR9k-cisco).

I'm not looking for that cost. If I can demonstrate that there is an
upper-bound cost for building a router whose cost varies linearly with
the gbps pushed, without regard to the BGP table size then I can
eliminate the router's gbps rate from the equation that describes the
upper bound for processing BGP.

This says nothing about the average case, in which I can build a
cheaper router whose cost does vary with the BGP table size. But I
don't need to find BGP's average case to calculate an upper bound. And
I certainly don't need to find the average case to demonstrate that a
calculable upper bound exists.

Regards,
Bill Herrin

-- 
William D. Herrin ................ herrin@dirtside.com  bill@herrin.us
3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
Falls Church, VA 22042-3004
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Fri Jan  2 12:12:16 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0F4043A6A11;
	Fri,  2 Jan 2009 12:12:16 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D2EFB3A6A11
	for <rrg@core3.amsl.com>; Fri,  2 Jan 2009 12:12:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.563
X-Spam-Level: 
X-Spam-Status: No, score=-2.563 tagged_above=-999 required=5 tests=[AWL=0.036, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id CZxvn+qPKlW0 for <rrg@core3.amsl.com>;
	Fri,  2 Jan 2009 12:12:12 -0800 (PST)
Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.189])
	by core3.amsl.com (Postfix) with ESMTP id 3CC623A67A3
	for <rrg@irtf.org>; Fri,  2 Jan 2009 12:12:11 -0800 (PST)
Received: by ti-out-0910.google.com with SMTP id b8so5527966tic.11
	for <rrg@irtf.org>; Fri, 02 Jan 2009 12:11:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from
	:organization:user-agent:mime-version:to:cc:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=Wk1uEQhjpnPPwBYQz4KsSwxnjvgcwxEF2cFBUH8cRhs=;
	b=m8seBiTfIJ5iPvVg0fHrKbncsngTqPMgrz7Bca+1v9YKwK6//K+01EwASCbhszip8w
	nkXqr8da04gg2d9wleyUpxcw5hU10DFNE7wYC/S1IQTgv2l2vj4frn6qwVtyJI+s2uFQ
	mU1Fy0CBpV641WoENcKVot5g5b8a3vIlIC0w4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	b=CnzWCRc0ctZ3g3Q99SOPfCt8pQd8pU0mcOY3F1OODqCgWrcbb2cqVB6oxTPuqEH0XS
	WpHUEhSvuEx/x1oT0k3QCV2KAk2QgVXRT82RPptz5xyTYDaYItjNW4Wvz5qsWWFDG/M8
	H8IjRXVBcK1LfO1Gj5WAC4icoUX9kcgcIpY2E=
Received: by 10.110.16.9 with SMTP id 9mr20843931tip.39.1230927119653;
	Fri, 02 Jan 2009 12:11:59 -0800 (PST)
Received: from ?10.1.1.4? (118-92-100-9.dsl.dyn.ihug.co.nz [118.92.100.9])
	by mx.google.com with ESMTPS id b7sm13751970tic.23.2009.01.02.12.11.57
	(version=SSLv3 cipher=RC4-MD5); Fri, 02 Jan 2009 12:11:58 -0800 (PST)
Message-ID: <495E750A.8010304@gmail.com>
Date: Sat, 03 Jan 2009 09:11:54 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: William Herrin <bill@herrin.us>
References: <3c3e3fca0812310857y14a8233ag953a9441279a25b5@mail.gmail.com>	
	<EC6C5330-557A-4D5F-8FF9-10A639806C6C@extremenetworks.com>	
	<3c3e3fca0812311715r5cad842elfba98f56596bd033@mail.gmail.com>	
	<B761BA80-6FD2-4D83-89C2-ACDC521E8574@extremenetworks.com>	
	<3c3e3fca0901010837h34a191e9r7dacb7fc504ff15b@mail.gmail.com>	
	<495D1CE7.9010107@gmail.com>
	<3c3e3fca0901021016p11f1263bj93dd724bb5e5c555@mail.gmail.com>
In-Reply-To: <3c3e3fca0901021016p11f1263bj93dd724bb5e5c555@mail.gmail.com>
Cc: IRTF Routing RG <rrg@irtf.org>
Subject: Re: [rrg] solution strategies, nat?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Bill,

On 2009-01-03 07:16, William Herrin wrote:
> On Thu, Jan 1, 2009 at 2:43 PM, Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
>> On 2009-01-02 05:37, William Herrin wrote:
>>> I insist on me being able to
>>> satisfactorily explain how a particular approach would reduce the need
>>> or demand for core routing slots.
>> Slide 15 in
>> http://www.cs.auckland.ac.nz/~brian/RRG0708.pdf
> 
> 
> Thanks Brian.
> 
> I follow how slide 15 achieves reliable multihoming given two constraints:
> 
> 1. System contains client machines. If it contains servers, they are
> limited to those protocols which have a thoroughly defined layer-7
> multihoming process, such as SMTP.

Yes, layer 7 has to be able to cope with this.

> 2. Loss of session during a multihoming event deemed acceptable.

Yes, which implies that layer 7 transactions must have intrinsic
robustness (not a new idea in the transaction processing business).

> 
> I accept the proposition that some significant fraction of the
> multihoming demand could be satisfied with a system meeting criteria
> #2. Given a satisfactorily low rate of multihoming events, a pizza
> joint is happy as long as the SIP phones immediately re-establish and
> the web users can get the page by hitting reload.
> 
> I accept that slide 15 offers qualitatively different multihoming
> versus slide 16 in that slide 15 does not require hosts to deal with
> routing constructs with which they are not presently familiar. When
> fleshed out to provide a complete multihoming solution, slide 16
> evolves into strategy B.

Correct.

> 
> Question:
> 
> What's the cause to believe that systems meeting criteria #1 represent
> a more-than-negligible portion of the multihoming demand that is
> either unserved or served by BGP?

Well, I believe that all successful transaction-style layer 7s meet
this and have done since the earliest days of on-line transaction
processing. And I think there's a reason why the large business systems
of today are built on top of web services namespaces or similar, which
form an abstraction layer that basically hides *everything* we're talking
about here. But, indeed, anything that rides directly on the socket API
is exposed (a bit less so with getaddrinfo than gethostbyname, however).
> 
> 
> You may choose to dispute criteria #1. Before you do, I remind you
> that the primary API for access to the DNS (gethostbyname) is
> irretrievably defective, at least as it pertains to providing an
> ephemeral GUID to LOC map.
> 
> 
>> So if you were product manager for a highly reliable
>> distributed application, I'm sure you would insist that it was
>> coded to detect permanent transport failures and try alternative
>> addresses.
> 
> Like a web browser, let's say? Think HTTP handles this? Think again.
> Once the browser successfully connects to a particular IP address for
> a given server name, it nails itself to that address in order to avoid
> an otherwise unsolvable javascript+DNS hacking vector.

Indeed. I'm no lover of the Web Services monster, but again - that's
why they use a namespace abstracted above DNS and run their own security
at layer 7.

     Brian
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Fri Jan  2 12:19:51 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8F2CF28B797;
	Fri,  2 Jan 2009 12:19:51 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 79DC028B797
	for <rrg@core3.amsl.com>; Fri,  2 Jan 2009 12:19:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.964
X-Spam-Level: 
X-Spam-Status: No, score=-1.964 tagged_above=-999 required=5 tests=[AWL=0.013, 
	BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id pG2QoWdSzd-p for <rrg@core3.amsl.com>;
	Fri,  2 Jan 2009 12:19:49 -0800 (PST)
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.183])
	by core3.amsl.com (Postfix) with ESMTP id EA7EA3A6A26
	for <rrg@irtf.org>; Fri,  2 Jan 2009 12:19:48 -0800 (PST)
Received: by wa-out-1112.google.com with SMTP id j37so3614560waf.23
	for <rrg@irtf.org>; Fri, 02 Jan 2009 12:19:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:sender
	:to:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references
	:x-google-sender-auth;
	bh=cnyxSrXH7NNq/wVaoRXdGsZlheyerTevhXUeRq3zrD0=;
	b=wGbBrfCx6XXCPvPO4dIf/7hvYn9fRMajmSiFKvPFYYEYyOKlYQwt9T9KJ4sPxJW+qh
	Mbg0wKram0BGL6cSOz5kosvsCWnwII0jVR2bB4AYp8ITbiHao+/ltqcetkPbutSGNi5d
	3OFFyBedynRhjNn5fwSR1YqvdDd3253uumKwY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references:x-google-sender-auth;
	b=ncjyKz+j6N2Kzascvqqa0/TGi5bPexin8FiYe0ItU6C1Y9fvTK1c7Ys6U/SKVDxmeZ
	fPRdgWZx61L2OLkSepb9sYnp6bS6d9J//GOylQmkl1t5VRfn8GRR8nZ+Ujq6HW6h2A5m
	yW2cv9bipT+FOtUilzH+VkFjf8+AFFrICKqKE=
Received: by 10.114.67.2 with SMTP id p2mr11988701waa.208.1230927575688;
	Fri, 02 Jan 2009 12:19:35 -0800 (PST)
Received: by 10.115.74.12 with HTTP; Fri, 2 Jan 2009 12:19:35 -0800 (PST)
Message-ID: <3c3e3fca0901021219t2ab35dfsb2532e0c89be84af@mail.gmail.com>
Date: Fri, 2 Jan 2009 15:19:35 -0500
From: "William Herrin" <bill@herrin.us>
To: tony.li@tony.li
In-Reply-To: <87D9F0BA2807456A88B0427241A29F65@ad.redback.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com>
	<87D9F0BA2807456A88B0427241A29F65@ad.redback.com>
X-Google-Sender-Auth: 6679720387fe70c7
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On Wed, Dec 31, 2008 at 7:00 PM, Tony Li <tony.li@tony.li> wrote:
> |Do the folks on this group clearly understand the harm that the
> |Regional Internet Registries do by denying number resources to
> |multihomed registrants based on our assurance that it's a necessary
> |evil in order to keep BGP stable?
>
> AFAIK, the RIRs are, for v4, requiring sane and reasonable justification for
> PI prefixes.  For v6, they're effectively giving everyone PI.  Can you be
> more specific about the policies that you're objecting to.

Tony,

ARIN policy requires multihomed users to demonstrate a need to deploy
500 machines on the Internet in order to qualify for end-use IPv4
address assignments. This number was selected above the operations
minimum of 125 addresses based on the IETF and NANOG advice that their
assistance is required to conserve routing slots so as not to overload
the BGP system.

ARIN policy requires the same 500-machine demonstration for multihomed
users to qualify for IPv6 end-user address assignments. This is based
solely on the IETF and NANOG advice that their assistance is required
to conserve routing slots so as not to overload the BGP system.

Entities unable to demonstrate a need to multihome 500 machines are
refused direct assignments, resulting in tying to a single ISP and
incomplete propagation of multihoming addresses within BGP.


> |If we still can't reliably quantify a BGP scaling limit then our
> |request that the RIRs suppress BGP growth by suppressing resource
> |assignment is simply unconscionable.
>
> Do we need to reliably quantify where the Earth will reach the tipping point
> into a irreversible greenhouse effect before global warming is relevant?

Yes, we do.

Geology suggests that absent human behavior, the Earth's current trend
should be towards an ice age. This is a result we'd also like to
avoid. Until we clearly understand the growth pattern associated with
human induced climate change and that pattern's interaction with the
natural pattern, we won't be able to predict the overall pattern with
any accuracy and thus can't rule out the possibility that we need to
increase greenhouse emissions to avoid the next cycle of glaciation.

The 100-year projections for global temperatures are so much junk
science. We still only have a 50/50 chance of predicting the weather
next week.

Regards,
Bill Herrin




-- 
William D. Herrin ................ herrin@dirtside.com  bill@herrin.us
3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
Falls Church, VA 22042-3004
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Fri Jan  2 12:22:56 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DB1E13A692C;
	Fri,  2 Jan 2009 12:22:56 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3CEC13A6809
	for <rrg@core3.amsl.com>; Fri,  2 Jan 2009 12:22:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.964
X-Spam-Level: 
X-Spam-Status: No, score=-1.964 tagged_above=-999 required=5 tests=[AWL=0.013, 
	BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id X42Dbv5n2JkI for <rrg@core3.amsl.com>;
	Fri,  2 Jan 2009 12:22:54 -0800 (PST)
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.180])
	by core3.amsl.com (Postfix) with ESMTP id 22D613A6A26
	for <rrg@irtf.org>; Fri,  2 Jan 2009 12:21:07 -0800 (PST)
Received: by wa-out-1112.google.com with SMTP id j37so3614831waf.23
	for <rrg@irtf.org>; Fri, 02 Jan 2009 12:20:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:sender
	:to:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references
	:x-google-sender-auth;
	bh=3Em8t6JAMMWohGKFclvwej+pleEqpx0mqJfJb7RSKF4=;
	b=JkcVTy7ZYaQLI9pEJHt9hYGSz6WNyS71yLrG/x+UF/z5vtBy64sTOVDngKs8WM4g9J
	snfcmcDVBkuOPPWxDVpPgcDiD9vRaQBLNPeDhbVM9bYs+pJs7H9tnJq6CnhUZ+j0qaNn
	64il/6gneV82bTDYaFBm/DScj9d1CMMMNDUs0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references:x-google-sender-auth;
	b=NwCyP6VgHrhesN8sgT9BTR2KK2U8po7UYjJAB4kdCRNJL5MGFGh0iBmvL//nKZGHUy
	VjS61KxFNUq1KMV+defuP1riyF2kRDQ2YkZjcjNoPC2oq+3qZ5TrYFIZ2+faHu2V7zvY
	UcvsL0nY++16uiQfO0v3y7soGXDIijsIfAn88=
Received: by 10.114.81.1 with SMTP id e1mr11976790wab.212.1230927653606;
	Fri, 02 Jan 2009 12:20:53 -0800 (PST)
Received: by 10.115.74.12 with HTTP; Fri, 2 Jan 2009 12:20:53 -0800 (PST)
Message-ID: <3c3e3fca0901021220j7eaaeebbobe4de3be34eb5ab5@mail.gmail.com>
Date: Fri, 2 Jan 2009 15:20:53 -0500
From: "William Herrin" <bill@herrin.us>
To: "Ross Callon" <rcallon@juniper.net>
In-Reply-To: <3525C9833C09ED418C6FD6CD9514668C0566043E@emailwf1.jnpr.net>
MIME-Version: 1.0
Content-Disposition: inline
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com>
	<75cb24520812311427m31d4dae0nd5c37130cc485eaf@mail.gmail.com>
	<495C3FB6.8030808@firstpr.com.au>
	<1230828437.2961.38.camel@localhost.localdomain>
	<3525C9833C09ED418C6FD6CD9514668C0566043E@emailwf1.jnpr.net>
X-Google-Sender-Auth: 738c5c6206c94196
Cc: RRG <rrg@irtf.org>, Robin Whittle <rw@firstpr.com.au>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On Fri, Jan 2, 2009 at 11:30 AM, Ross Callon <rcallon@juniper.net> wrote:
> Early on in this discussion engineers from multiple router vendors
> stated publicly that that their engineers knew how to build routers that
> would handle FIBs that were at least 4M entries or more (10M was
> mentioned), using commodity hardware parts. It also became clear to
> me that the router hardware engineers working on the hardware forwarding
> parts of routers were not even considering any major change to the
> architecture, for the simple reason that they didn't need to.

Ross,

So, effective 2008 we can build routers that handle 4M routes.

Effective 1995, we scrambled to deploy CIDR so that among other things
we wouldn't hit the wall on our state of the art Cisco 7000 routers
which IIRC could handle about 50k routes, that by stretching
then-available hardware to its limits.

Over 13 intervening years, that's somewhere between a compound rate of
improvement of 40% per year and a fixed rate of improvement of 300k
entries per year.

If you fit a growth curve to http://bgp.potaroo.net/ , the BGP table
size is growing at a compound rate of roughly 25% per year.


If our ability to build routers is indeed compounding at 40% per year,
the BGP table size will never catch it.

If our ability to build routers is growing linearly by only 300k
entries per year, the BGP table size will finally catch up with it in
2024 when the routing table has 8.5M entries.

Yes?

Regards,
Bill Herrin


-- 
William D. Herrin ................ herrin@dirtside.com  bill@herrin.us
3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
Falls Church, VA 22042-3004
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Fri Jan  2 12:26:28 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 425203A6876;
	Fri,  2 Jan 2009 12:26:28 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D504F3A6876
	for <rrg@core3.amsl.com>; Fri,  2 Jan 2009 12:26:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.554
X-Spam-Level: 
X-Spam-Status: No, score=-2.554 tagged_above=-999 required=5 tests=[AWL=0.045, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id rXbvc1Pg5c7D for <rrg@core3.amsl.com>;
	Fri,  2 Jan 2009 12:26:26 -0800 (PST)
Received: from QMTA07.emeryville.ca.mail.comcast.net
	(qmta07.emeryville.ca.mail.comcast.net [76.96.30.64])
	by core3.amsl.com (Postfix) with ESMTP id 2FB2F3A6857
	for <rrg@irtf.org>; Fri,  2 Jan 2009 12:26:26 -0800 (PST)
Received: from OMTA08.emeryville.ca.mail.comcast.net ([76.96.30.12])
	by QMTA07.emeryville.ca.mail.comcast.net with comcast
	id ydvX1a0010FhH24A7kSFLQ; Fri, 02 Jan 2009 20:26:15 +0000
Received: from TONYLTM9XP ([155.53.1.254])
	by OMTA08.emeryville.ca.mail.comcast.net with comcast
	id ykS21a00D5Up7oj8UkS4vr; Fri, 02 Jan 2009 20:26:13 +0000
From: "Tony Li" <tony.li@tony.li>
To: "'William Herrin'" <bill@herrin.us>
References: <3c3e3fca0812310857y14a8233ag953a9441279a25b5@mail.gmail.com>
	<EC6C5330-557A-4D5F-8FF9-10A639806C6C@extremenetworks.com>
	<3c3e3fca0812311715r5cad842elfba98f56596bd033@mail.gmail.com>
	<B761BA80-6FD2-4D83-89C2-ACDC521E8574@extremenetworks.com>
	<3c3e3fca0901010837h34a191e9r7dacb7fc504ff15b@mail.gmail.com>
	<EDF52BB5C1194991BA849302ADA869D5@ad.redback.com>
	<3c3e3fca0901021011y7143a8bai4119cc32312e1c62@mail.gmail.com>
Date: Fri, 2 Jan 2009 12:25:32 -0800
Message-ID: <2ADBDCB7418F42A4ABCA208A3B201F69@ad.redback.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
In-Reply-To: <3c3e3fca0901021011y7143a8bai4119cc32312e1c62@mail.gmail.com>
Thread-Index: AcltBYFmDtsMk+buQaGaRyQDs1jmNwAEkYHA
Cc: 'RJ Atkinson' <rja@extremenetworks.com>, 'IRTF Routing RG' <rrg@irtf.org>
Subject: Re: [rrg] solution strategies, nat?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

 

Hi Bill,


|The status quo is: the number of entries in the BGP table has
|consistently grown and continues to grow year over year since BGP's
|inception. See: http://bgp.potaroo.net/


Reality check indeed: that's simply not true.  There are several blips where
there has been a decline.  Early 2001 and 2004 appear obvious.  And if the
graph were a bit larger, you'd see the post-CIDR decline.

Tony

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Fri Jan  2 12:35:16 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A40ED28C0E5;
	Fri,  2 Jan 2009 12:35:16 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1DD2B28C0E5
	for <rrg@core3.amsl.com>; Fri,  2 Jan 2009 12:35:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.555
X-Spam-Level: 
X-Spam-Status: No, score=-2.555 tagged_above=-999 required=5 tests=[AWL=0.044, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Xo0my+ZXyhzY for <rrg@core3.amsl.com>;
	Fri,  2 Jan 2009 12:35:15 -0800 (PST)
Received: from QMTA01.emeryville.ca.mail.comcast.net
	(qmta01.emeryville.ca.mail.comcast.net [76.96.30.16])
	by core3.amsl.com (Postfix) with ESMTP id 679C828C0E4
	for <rrg@irtf.org>; Fri,  2 Jan 2009 12:35:15 -0800 (PST)
Received: from OMTA02.emeryville.ca.mail.comcast.net ([76.96.30.19])
	by QMTA01.emeryville.ca.mail.comcast.net with comcast
	id ydkL1a00F0QkzPwA1kb4ua; Fri, 02 Jan 2009 20:35:04 +0000
Received: from TONYLTM9XP ([155.53.1.254])
	by OMTA02.emeryville.ca.mail.comcast.net with comcast
	id ykas1a00F5Up7oj8Nkau6r; Fri, 02 Jan 2009 20:35:02 +0000
From: "Tony Li" <tony.li@tony.li>
To: "'William Herrin'" <bill@herrin.us>
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com>
	<87D9F0BA2807456A88B0427241A29F65@ad.redback.com>
	<3c3e3fca0901021219t2ab35dfsb2532e0c89be84af@mail.gmail.com>
Date: Fri, 2 Jan 2009 12:34:22 -0800
Message-ID: <E99E41EB33084B5B899C7EED9DE607E9@ad.redback.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
In-Reply-To: <3c3e3fca0901021219t2ab35dfsb2532e0c89be84af@mail.gmail.com>
Thread-Index: AcltF3AmrOQufe74TRqroPPYZe7Y5wAAUc9Q
Cc: 'RRG' <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org


Hi Bill,
 
|Entities unable to demonstrate a need to multihome 500 machines are
|refused direct assignments, resulting in tying to a single ISP and
|incomplete propagation of multihoming addresses within BGP.


Seems not unreasonable to me.  Since our current architecture can't support
that kind of multi-homing load, we're trying to avoid the load.

If you're arguing that the status-quo doesn't meet users needs, I agree with
you, of course.  If you're arguing that we should do something to meet those
needs, I also agree.  However, in the case where we fail to do anything,
yes, those needs will be unmet.  This is the obvious outcome unless we can
overcome the partisan bickering and find compromise.


|> Do we need to reliably quantify where the Earth will reach 
|the tipping point
|> into a irreversible greenhouse effect before global warming 
|is relevant?
|
|Yes, we do.


Cool.  Enjoy your Hummer.

Why are you spending your time here then?

Tony

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Fri Jan  2 12:40:51 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E73413A6A33;
	Fri,  2 Jan 2009 12:40:51 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EE77A28B797
	for <rrg@core3.amsl.com>; Fri,  2 Jan 2009 12:40:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.555
X-Spam-Level: 
X-Spam-Status: No, score=-2.555 tagged_above=-999 required=5 tests=[AWL=0.044, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id PITKiLbt2syY for <rrg@core3.amsl.com>;
	Fri,  2 Jan 2009 12:40:50 -0800 (PST)
Received: from QMTA05.emeryville.ca.mail.comcast.net
	(qmta05.emeryville.ca.mail.comcast.net [76.96.30.48])
	by core3.amsl.com (Postfix) with ESMTP id 484353A6857
	for <rrg@irtf.org>; Fri,  2 Jan 2009 12:40:50 -0800 (PST)
Received: from OMTA07.emeryville.ca.mail.comcast.net ([76.96.30.59])
	by QMTA05.emeryville.ca.mail.comcast.net with comcast
	id yest1a0031GXsucA5kgfAl; Fri, 02 Jan 2009 20:40:39 +0000
Received: from TONYLTM9XP ([155.53.1.254])
	by OMTA07.emeryville.ca.mail.comcast.net with comcast
	id ykgQ1a00U5Up7oj8TkgS2d; Fri, 02 Jan 2009 20:40:37 +0000
From: "Tony Li" <tony.li@tony.li>
To: "'Ross Callon'" <rcallon@juniper.net>,
	"'Steven Blake'" <slblake@petri-meat.com>,
	"'Robin Whittle'" <rw@firstpr.com.au>
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com><75cb24520812311427m31d4dae0nd5c37130cc485eaf@mail.gmail.com><495C3FB6.8030808@firstpr.com.au><1230828437.2961.38.camel@localhost.localdomain>
	<3525C9833C09ED418C6FD6CD9514668C0566043E@emailwf1.jnpr.net>
Date: Fri, 2 Jan 2009 12:39:54 -0800
Message-ID: <7FFAD0AD95D440858E6BF2A4C5AF0EA4@ad.redback.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
In-Reply-To: <3525C9833C09ED418C6FD6CD9514668C0566043E@emailwf1.jnpr.net>
Thread-Index: AclsMJ8e3Ai5tWQqTqGoWFBwgq7fdwAwOlgwAAoF8GA=
Cc: 'RRG' <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

 
Hi Ross,


|There may be many reasons to consider making a major change to the way
|that the Internet does routing and addressing, but the inability to
|build equipment that can handle several million entries is NOT a valid
|reason. 


Please argue on point.

The argument is not about the absolute value of the number of routes
supported.  We can always scale things by throwing more money at gear.

The argument is that the rate of growth exceeds the constant cost curve
delivered by technological improvements, thus resulting in increasing costs
over time.  

Please understand the distinction.

Regards,
Tony

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Fri Jan  2 12:41:19 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2E8803A6965;
	Fri,  2 Jan 2009 12:41:19 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1DE9B3A6A37
	for <rrg@core3.amsl.com>; Fri,  2 Jan 2009 12:41:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.964
X-Spam-Level: 
X-Spam-Status: No, score=-1.964 tagged_above=-999 required=5 tests=[AWL=0.013, 
	BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id RCjUhb6Jr7nC for <rrg@core3.amsl.com>;
	Fri,  2 Jan 2009 12:41:17 -0800 (PST)
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.183])
	by core3.amsl.com (Postfix) with ESMTP id E76CB3A6965
	for <rrg@irtf.org>; Fri,  2 Jan 2009 12:41:00 -0800 (PST)
Received: by wa-out-1112.google.com with SMTP id j37so3618037waf.23
	for <rrg@irtf.org>; Fri, 02 Jan 2009 12:40:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:sender
	:to:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references
	:x-google-sender-auth;
	bh=e154mjyb71c1Ldd3NuGelP5+TOnmNuAf6zF/kZnCbM4=;
	b=cwFla7iPLtBPHro67lPKLratrAlWZrLGbW+0FsmpGSQLdeUUlrGK04RUEr003nZQxF
	Nf6YFD1MiHSHsIhAxvx4Sxu2XTAvAY5wfqLb8X6ib6x/BhM9LCQcnO1q1nTwStCkeCRX
	RRzWpfPyWDo1zvPBi2pMtkQkEzy8NZLQY9Mgw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references:x-google-sender-auth;
	b=XrOSGzKDDt7oJyv+5EhWVzG0a99nQ6vOsiAsqCad//X/xnwaVirfCAZurycxE8I8Q2
	2lf+bCUxqm2Q4fmtsNS8jM9dCvCRe9SwDkDxHZLuxqiqUUeqAvtg4gC0cllcGexxp1CT
	lpAaHr2JxxvfkCFRKq5om7P5wjt6FLmoZO8Kw=
Received: by 10.115.33.1 with SMTP id l1mr582536waj.130.1230928846925;
	Fri, 02 Jan 2009 12:40:46 -0800 (PST)
Received: by 10.115.74.12 with HTTP; Fri, 2 Jan 2009 12:40:46 -0800 (PST)
Message-ID: <3c3e3fca0901021240s3f1d4615u44200a19c4cfe0a@mail.gmail.com>
Date: Fri, 2 Jan 2009 15:40:46 -0500
From: "William Herrin" <bill@herrin.us>
To: tony.li@tony.li
In-Reply-To: <2ADBDCB7418F42A4ABCA208A3B201F69@ad.redback.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <3c3e3fca0812310857y14a8233ag953a9441279a25b5@mail.gmail.com>
	<EC6C5330-557A-4D5F-8FF9-10A639806C6C@extremenetworks.com>
	<3c3e3fca0812311715r5cad842elfba98f56596bd033@mail.gmail.com>
	<B761BA80-6FD2-4D83-89C2-ACDC521E8574@extremenetworks.com>
	<3c3e3fca0901010837h34a191e9r7dacb7fc504ff15b@mail.gmail.com>
	<EDF52BB5C1194991BA849302ADA869D5@ad.redback.com>
	<3c3e3fca0901021011y7143a8bai4119cc32312e1c62@mail.gmail.com>
	<2ADBDCB7418F42A4ABCA208A3B201F69@ad.redback.com>
X-Google-Sender-Auth: 9a36853ff2fe22db
Cc: RJ Atkinson <rja@extremenetworks.com>, IRTF Routing RG <rrg@irtf.org>
Subject: Re: [rrg] solution strategies, nat?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On Fri, Jan 2, 2009 at 3:25 PM, Tony Li <tony.li@tony.li> wrote:
> |The status quo is: the number of entries in the BGP table has
> |consistently grown and continues to grow year over year since BGP's
> |inception. See: http://bgp.potaroo.net/
>
>
> Reality check indeed: that's simply not true.  There are several blips where
> there has been a decline.  Early 2001 and 2004 appear obvious.  And if the
> graph were a bit larger, you'd see the post-CIDR decline.

In 15 years of data, the only start points you can pick in the graph
which were not higher 12 months later are within that short blip in
2001. What's more, the blip is clearly an outlier: only one of the
several BGP feeds plotted exhibits that behavior. Even for the blip,
they're higher 24 months later.

Regards,
Bill Herrin


-- 
William D. Herrin ................ herrin@dirtside.com  bill@herrin.us
3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
Falls Church, VA 22042-3004
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Fri Jan  2 13:34:34 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 922613A68CB;
	Fri,  2 Jan 2009 13:34:34 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EC69C3A68A5
	for <rrg@core3.amsl.com>; Fri,  2 Jan 2009 13:34:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.965
X-Spam-Level: 
X-Spam-Status: No, score=-1.965 tagged_above=-999 required=5 tests=[AWL=0.012, 
	BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id VkU5s4s+iLJU for <rrg@core3.amsl.com>;
	Fri,  2 Jan 2009 13:34:32 -0800 (PST)
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.177])
	by core3.amsl.com (Postfix) with ESMTP id BAD9A3A6784
	for <rrg@irtf.org>; Fri,  2 Jan 2009 13:34:32 -0800 (PST)
Received: by wa-out-1112.google.com with SMTP id j37so3627256waf.23
	for <rrg@irtf.org>; Fri, 02 Jan 2009 13:34:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:sender
	:to:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references
	:x-google-sender-auth;
	bh=7kW/0tA2Gnl/00uWTWrhnACQvKwZTIM21mkE6JAMSz0=;
	b=gsp1QnVWpWJGPKXBp/pqHh6OHaDAAm8MDrFCmjW2qAqoS7bqA4TBk12a+ccRCfuRPv
	/VqOEYA5wXa4fW9Gui3Jl/EFgJSwsb8+umtUNa89tbtPBQ8RnyGnLN8yhYgg39wTNiW3
	fz+VaLVH57yqdga1vWIUYwwzSUKMFn2v/ZImo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references:x-google-sender-auth;
	b=mEjuzwHnjzroEDemUTjtzISn5BXMcEFpx1LJyyY4biaucywRdL1Vyqr+mdeWhsU2/C
	N5bzZ6w2Bin8nHygMo6HHfiBHGQW+nJlPjiu2fclNyVnaqBvKKHGmn8ZVJcFUv3clXnT
	OsCm827RTSgwe7TL1trhwmVOde76QDhWj5Vro=
Received: by 10.114.137.16 with SMTP id k16mr12030338wad.189.1230932060232;
	Fri, 02 Jan 2009 13:34:20 -0800 (PST)
Received: by 10.115.74.12 with HTTP; Fri, 2 Jan 2009 13:34:20 -0800 (PST)
Message-ID: <3c3e3fca0901021334j22d17e54iec4bbf41b6c00480@mail.gmail.com>
Date: Fri, 2 Jan 2009 16:34:20 -0500
From: "William Herrin" <bill@herrin.us>
To: tony.li@tony.li
In-Reply-To: <E99E41EB33084B5B899C7EED9DE607E9@ad.redback.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com>
	<87D9F0BA2807456A88B0427241A29F65@ad.redback.com>
	<3c3e3fca0901021219t2ab35dfsb2532e0c89be84af@mail.gmail.com>
	<E99E41EB33084B5B899C7EED9DE607E9@ad.redback.com>
X-Google-Sender-Auth: 51c69a5dc11cce3a
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On Fri, Jan 2, 2009 at 3:34 PM, Tony Li <tony.li@tony.li> wrote:
> |Entities unable to demonstrate a need to multihome 500 machines are
> |refused direct assignments, resulting in tying to a single ISP and
> |incomplete propagation of multihoming addresses within BGP.
>
> Seems not unreasonable to me.  Since our current architecture can't support
> that kind of multi-homing load, we're trying to avoid the load.

Tony,

Now wait a minute; Brian just told us that we can't say with any
scientific or engineering certainty what kind of multihoming load the
current architecture can or can't support. Which is it? Can we? Or
can't we?

You follow the logical inconsistency, right? You can't in one breath
say that we can't determine X and then in the next breath say that
because of X we can confidently say Y.


> Cool.  Enjoy your Hummer.

Mustang GT I'll have you know. Bought it for dirt right before the
price of gas started its nose dive. My 20 mile commute includes a 15
mile stretch of nearly empty freeway. I'm lovin' it!

Regards,
Bill Herrin


-- 
William D. Herrin ................ herrin@dirtside.com  bill@herrin.us
3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
Falls Church, VA 22042-3004
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Fri Jan  2 13:58:26 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0B9CD3A68A5;
	Fri,  2 Jan 2009 13:58:26 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 083F23A68A5
	for <rrg@core3.amsl.com>; Fri,  2 Jan 2009 13:58:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level: 
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id FRDuzG+PF-6e for <rrg@core3.amsl.com>;
	Fri,  2 Jan 2009 13:58:24 -0800 (PST)
Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.30])
	by core3.amsl.com (Postfix) with ESMTP id 1EEC13A6784
	for <rrg@irtf.org>; Fri,  2 Jan 2009 13:58:23 -0800 (PST)
Received: by yx-out-2324.google.com with SMTP id 8so2661635yxg.37
	for <rrg@irtf.org>; Fri, 02 Jan 2009 13:58:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:sender
	:to:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references
	:x-google-sender-auth;
	bh=mvrG9SUJsRXTqBZl++WjToihb6mGtt8AL5DYHXkKZjg=;
	b=w2fgy65w34MooMFROR8o53SP6vm4LV7NMdBnlB7zNy1DzGW0yTV9oE3XT4cRyXLh8g
	Yuo5AJmHQIzZqLAOkpSv0FUZ+/V5H5CyoRq5K6vJSUoB6GofToq2Cdd3g9qgmBW1XprK
	ccP+KPDDvJcKhaVtUms7UlSm29N/gNqqCGvVE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references:x-google-sender-auth;
	b=qqj1oBdQreyvAwiPHaAc/l0k76jrT8QmKwrbO4lKiPSB13FVgpL0t15z14B1+SAIjQ
	jOrmoNYdDUp5pLniQT1CDCAS9vE4tJxb4dYn0qeX44v/R1XWF1k0lG4CKLmhfX/p1BFJ
	1XLCnFEeVcM4V+jdMq/1/INIp2IN8ylKlcxlM=
Received: by 10.100.139.20 with SMTP id m20mr9995254and.147.1230933490538;
	Fri, 02 Jan 2009 13:58:10 -0800 (PST)
Received: by 10.100.38.12 with HTTP; Fri, 2 Jan 2009 13:58:10 -0800 (PST)
Message-ID: <75cb24520901021358k4dcc2abfna04eb093e45cdf07@mail.gmail.com>
Date: Fri, 2 Jan 2009 16:58:10 -0500
From: "Christopher Morrow" <morrowc.lists@gmail.com>
To: "William Herrin" <bill@herrin.us>
In-Reply-To: <3c3e3fca0901021219t2ab35dfsb2532e0c89be84af@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com>
	<87D9F0BA2807456A88B0427241A29F65@ad.redback.com>
	<3c3e3fca0901021219t2ab35dfsb2532e0c89be84af@mail.gmail.com>
X-Google-Sender-Auth: 1c616e33b99f50d9
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On Fri, Jan 2, 2009 at 3:19 PM, William Herrin <bill@herrin.us> wrote:
>
> ARIN policy requires multihomed users to demonstrate a need to deploy
> 500 machines on the Internet in order to qualify for end-use IPv4
> address assignments. This number was selected above the operations
> minimum of 125 addresses based on the IETF and NANOG advice that their
> assistance is required to conserve routing slots so as not to overload
> the BGP system.

I believe actually if you can demonstrate a 'unique routing policy'
you can at least get a /24 from one provider, and an ASN from
ARIN/RIPE/APNIC and enjoy a routing slot in the DFZ all your own. When
I was last doing allocation-policy-bits for an ISP we regularly
pointed out to customers that tying themselves to our ip space might
not be in their best interest, and that it really wasn't all that hard
to show usage such that a /22 was a viable option from their local
registry.

-Chris
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Fri Jan  2 14:15:46 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 69C613A67EF;
	Fri,  2 Jan 2009 14:15:46 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E50C33A67EF
	for <rrg@core3.amsl.com>; Fri,  2 Jan 2009 14:15:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.965
X-Spam-Level: 
X-Spam-Status: No, score=-1.965 tagged_above=-999 required=5 tests=[AWL=0.012, 
	BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id BQphdyIQ9kHD for <rrg@core3.amsl.com>;
	Fri,  2 Jan 2009 14:15:43 -0800 (PST)
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.183])
	by core3.amsl.com (Postfix) with ESMTP id BBAE23A6784
	for <rrg@irtf.org>; Fri,  2 Jan 2009 14:15:43 -0800 (PST)
Received: by wa-out-1112.google.com with SMTP id j37so3634035waf.23
	for <rrg@irtf.org>; Fri, 02 Jan 2009 14:15:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:sender
	:to:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references
	:x-google-sender-auth;
	bh=JuBXDUE5AeIUZ0Di5CCP8mi9zilS5GVavDsNj8BXPOw=;
	b=EoGQ8ksy2QEZq5DnVuQM6XM/8WJbfAhzcs3lL/1I48wBZpFTlH06zWCT/kRf3u9Bt3
	Mu98iLxGNexGGLsj/EnkCX5io6IJUJZjV2l1PAClWGnx9DoOEZ/VyUd+i1eN93Crpzdz
	UpkZE+4mPgvrnPo1j7Pgq9JJ1taVlchEkzSlE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references:x-google-sender-auth;
	b=S6iNT5kB9hj3GGutIbXHDkKxihFI4NHcaS4KaUM3pBvZ/jGSMqENP9EWxOwJ5wzup/
	PSXurlNb2e8o4BSIBsTP64IUwfB+KVaX1NqgEhnmRH/tIqqSWYiCRHBwH+4ZMspNEnfo
	Ew2d6msWsF1CZneQoH+sSmEF4yHHWDlS5/fu8=
Received: by 10.114.180.1 with SMTP id c1mr12058905waf.192.1230934530250;
	Fri, 02 Jan 2009 14:15:30 -0800 (PST)
Received: by 10.115.74.12 with HTTP; Fri, 2 Jan 2009 14:15:30 -0800 (PST)
Message-ID: <3c3e3fca0901021415p667c53d1s5c9ef423dcfdeb31@mail.gmail.com>
Date: Fri, 2 Jan 2009 17:15:30 -0500
From: "William Herrin" <bill@herrin.us>
To: "Christopher Morrow" <morrowc.lists@gmail.com>
In-Reply-To: <75cb24520901021358k4dcc2abfna04eb093e45cdf07@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com>
	<87D9F0BA2807456A88B0427241A29F65@ad.redback.com>
	<3c3e3fca0901021219t2ab35dfsb2532e0c89be84af@mail.gmail.com>
	<75cb24520901021358k4dcc2abfna04eb093e45cdf07@mail.gmail.com>
X-Google-Sender-Auth: 7519f2ac61c3c7b0
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On Fri, Jan 2, 2009 at 4:58 PM, Christopher Morrow
<morrowc.lists@gmail.com> wrote:
> On Fri, Jan 2, 2009 at 3:19 PM, William Herrin <bill@herrin.us> wrote:
>> ARIN policy requires multihomed users to demonstrate a need to deploy
>> 500 machines on the Internet in order to qualify for end-use IPv4
>> address assignments. This number was selected above the operations
>> minimum of 125 addresses based on the IETF and NANOG advice that their
>> assistance is required to conserve routing slots so as not to overload
>> the BGP system.
>
> I believe actually if you can demonstrate a 'unique routing policy'
> you can at least get a /24 from one provider, and an ASN from
> ARIN/RIPE/APNIC and enjoy a routing slot in the DFZ all your own.

Hi Chris,

Correct. Your ISP can justify giving you a /24 in their next request
if you request the /24 for multihoming purposes. And ARIN will then
give you an AS#. However, that /24 will often come from a /8 where
ARIN has declared the minimum allocation size to be /20. Though
fortunately few, some carriers treat all /24 cutouts in such blocks as
traffic engineering and filter them out. This results in an incomplete
multihoming solution which still consumes a slot in most folks'
routing table.

I'd be lying if I said I thought the policy was internally consistent.
Nevertheless, it exists and it springs from the assurance by the IETF
and NANOG that we really must suppress multihoming or else BGP will
overload and collapse.

Regards,
Bill Herrin



-- 
William D. Herrin ................ herrin@dirtside.com  bill@herrin.us
3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
Falls Church, VA 22042-3004
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Fri Jan  2 15:17:48 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 127B13A6A3B;
	Fri,  2 Jan 2009 15:17:48 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1A7C128C0DC
	for <rrg@core3.amsl.com>; Fri,  2 Jan 2009 15:17:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.556
X-Spam-Level: 
X-Spam-Status: No, score=-2.556 tagged_above=-999 required=5 tests=[AWL=0.043, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id XunNZylSVKf8 for <rrg@core3.amsl.com>;
	Fri,  2 Jan 2009 15:17:45 -0800 (PST)
Received: from QMTA07.emeryville.ca.mail.comcast.net
	(qmta07.emeryville.ca.mail.comcast.net [76.96.30.64])
	by core3.amsl.com (Postfix) with ESMTP id ED1BF3A6A3B
	for <rrg@irtf.org>; Fri,  2 Jan 2009 15:16:04 -0800 (PST)
Received: from OMTA07.emeryville.ca.mail.comcast.net ([76.96.30.59])
	by QMTA07.emeryville.ca.mail.comcast.net with comcast
	id ydJh1a00A1GXsucA7nFspS; Fri, 02 Jan 2009 23:15:52 +0000
Received: from TONYLTM9XP ([155.53.1.254])
	by OMTA07.emeryville.ca.mail.comcast.net with comcast
	id ynFe1a00e5Up7oj8TnFgPe; Fri, 02 Jan 2009 23:15:50 +0000
From: "Tony Li" <tony.li@tony.li>
To: "'William Herrin'" <bill@herrin.us>
References: <3c3e3fca0812310857y14a8233ag953a9441279a25b5@mail.gmail.com>
	<EC6C5330-557A-4D5F-8FF9-10A639806C6C@extremenetworks.com>
	<3c3e3fca0812311715r5cad842elfba98f56596bd033@mail.gmail.com>
	<B761BA80-6FD2-4D83-89C2-ACDC521E8574@extremenetworks.com>
	<3c3e3fca0901010837h34a191e9r7dacb7fc504ff15b@mail.gmail.com>
	<EDF52BB5C1194991BA849302ADA869D5@ad.redback.com>
	<3c3e3fca0901021011y7143a8bai4119cc32312e1c62@mail.gmail.com>
	<2ADBDCB7418F42A4ABCA208A3B201F69@ad.redback.com>
	<3c3e3fca0901021240s3f1d4615u44200a19c4cfe0a@mail.gmail.com>
Date: Fri, 2 Jan 2009 15:14:54 -0800
Message-ID: <8A84F9307CD54B51A353DAB59BFE472B@ad.redback.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
In-Reply-To: <3c3e3fca0901021240s3f1d4615u44200a19c4cfe0a@mail.gmail.com>
Thread-Index: AcltGmgbcN9mt1axR+CW/pUVuBqJuAAFXaaw
Cc: 'RJ Atkinson' <rja@extremenetworks.com>, 'IRTF Routing RG' <rrg@irtf.org>
Subject: Re: [rrg] solution strategies, nat?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

 

|In 15 years of data, the only start points you can pick in the graph
|which were not higher 12 months later are within that short blip in
|2001. What's more, the blip is clearly an outlier: only one of the
|several BGP feeds plotted exhibits that behavior. Even for the blip,
|they're higher 24 months later.


Thank you, that's much more accurate.

Tony

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Fri Jan  2 17:35:54 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1FEA928C18D;
	Fri,  2 Jan 2009 17:35:54 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0D1A328C18D
	for <rrg@core3.amsl.com>; Fri,  2 Jan 2009 17:35:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.555
X-Spam-Level: 
X-Spam-Status: No, score=-2.555 tagged_above=-999 required=5 tests=[AWL=0.044, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id K6lNjSgSyvDB for <rrg@core3.amsl.com>;
	Fri,  2 Jan 2009 17:35:52 -0800 (PST)
Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.30])
	by core3.amsl.com (Postfix) with ESMTP id 106EB3A6835
	for <rrg@irtf.org>; Fri,  2 Jan 2009 17:35:51 -0800 (PST)
Received: by yw-out-2324.google.com with SMTP id 3so2684718ywj.37
	for <rrg@irtf.org>; Fri, 02 Jan 2009 17:35:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:sender
	:to:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references
	:x-google-sender-auth;
	bh=vIBQgkUGfdtXD4828Jbp7/0wns778v+TVGIveJNhJKE=;
	b=KOpoRmAHdBJQ63rL0psljD3/2lCYoAkAtYz7mtebDFDABp6CerNlh/mI480ht2cfcx
	HVY7qgbd7wAvOL5by4CvbjEy/UUtvfrjSq9+FrEBKEOprNsZZLO8yb4yUVOvfnAqepI6
	aBWox9cJ72lBlJSL+Yyja9dZXtXEStdqnAvGA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references:x-google-sender-auth;
	b=W+QW12+u2x5J5WeYqjYZMTeK9SsE+febR63kfqoCV3ESXfJuMyIQUg17ZOLpMYEiPN
	ZwXBuv2A6N4mRJPzJlf+ug3QS0igYPV7Z1WfFweomNmSBIirsUbegxSzMhic9u4L9k8W
	6z/3hh76wEJcT1B8K5KcSFhWeUVo3HcEvTNow=
Received: by 10.100.107.17 with SMTP id f17mr10091961anc.51.1230946538609;
	Fri, 02 Jan 2009 17:35:38 -0800 (PST)
Received: by 10.100.38.12 with HTTP; Fri, 2 Jan 2009 17:35:38 -0800 (PST)
Message-ID: <75cb24520901021735r64615a51t26404d20aa2939f8@mail.gmail.com>
Date: Fri, 2 Jan 2009 20:35:38 -0500
From: "Christopher Morrow" <morrowc.lists@gmail.com>
To: "William Herrin" <bill@herrin.us>
In-Reply-To: <3c3e3fca0901021415p667c53d1s5c9ef423dcfdeb31@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com>
	<87D9F0BA2807456A88B0427241A29F65@ad.redback.com>
	<3c3e3fca0901021219t2ab35dfsb2532e0c89be84af@mail.gmail.com>
	<75cb24520901021358k4dcc2abfna04eb093e45cdf07@mail.gmail.com>
	<3c3e3fca0901021415p667c53d1s5c9ef423dcfdeb31@mail.gmail.com>
X-Google-Sender-Auth: 51af6a24fe087188
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On Fri, Jan 2, 2009 at 5:15 PM, William Herrin <bill@herrin.us> wrote:
> On Fri, Jan 2, 2009 at 4:58 PM, Christopher Morrow
> <morrowc.lists@gmail.com> wrote:
>> On Fri, Jan 2, 2009 at 3:19 PM, William Herrin <bill@herrin.us> wrote:
>>> ARIN policy requires multihomed users to demonstrate a need to deploy
>>> 500 machines on the Internet in order to qualify for end-use IPv4
>>> address assignments. This number was selected above the operations
>>> minimum of 125 addresses based on the IETF and NANOG advice that their
>>> assistance is required to conserve routing slots so as not to overload
>>> the BGP system.
>>
>> I believe actually if you can demonstrate a 'unique routing policy'
>> you can at least get a /24 from one provider, and an ASN from
>> ARIN/RIPE/APNIC and enjoy a routing slot in the DFZ all your own.
>
> Hi Chris,
>
> Correct. Your ISP can justify giving you a /24 in their next request
> if you request the /24 for multihoming purposes. And ARIN will then
> give you an AS#. However, that /24 will often come from a /8 where
> ARIN has declared the minimum allocation size to be /20. Though

that really depends on the ISP, their allocations and the person(s)
doing the allocation at the time...There was no distinction like that
where I was recently doing this.

> fortunately few, some carriers treat all /24 cutouts in such blocks as
> traffic engineering and filter them out. This results in an incomplete

sure, there are examples of this, mostly those folks are limiting
prefixes for financial reasons (don't want to upgrade 7500's or ...)

> multihoming solution which still consumes a slot in most folks'
> routing table.

also true.  My point, and I realized as I hit send I was splitting
hairs, was that routing slot allocations come from a range of places,
just noting that RIR's don't allocation without (hopefully) just cause
isn't the only way a slot is won.

Also, one point that I feel needs to be addressed is that internal
route tables are most often quite a bit larger than the globally
visible table. Ted and I both made this point at the RAWS meeting in
AMS (and it's in the slides I pointed to previously). That growth is
not as easy to quantify from the outside, unfortunately, and also not
well documented.

-Chris
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Fri Jan  2 21:12:27 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7ADA43A698C;
	Fri,  2 Jan 2009 21:12:27 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2DCFC3A698C
	for <rrg@core3.amsl.com>; Fri,  2 Jan 2009 21:12:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.684
X-Spam-Level: 
X-Spam-Status: No, score=-0.684 tagged_above=-999 required=5
	tests=[AWL=-0.648, BAYES_20=-0.74, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id QZUpXwbjykyZ for <rrg@core3.amsl.com>;
	Fri,  2 Jan 2009 21:12:25 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123])
	by core3.amsl.com (Postfix) with ESMTP id 418883A63EB
	for <rrg@irtf.org>; Fri,  2 Jan 2009 21:12:25 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6])
	by gair.firstpr.com.au (Postfix) with ESMTP id BBDD5175C57;
	Sat,  3 Jan 2009 16:12:11 +1100 (EST)
Message-ID: <495EF3B1.1030408@firstpr.com.au>
Date: Sat, 03 Jan 2009 16:12:17 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: RRG <rrg@irtf.org>
References: <4959B44C.2030709@firstpr.com.au>	<885A118B-76C8-4E8D-91C0-7C5C6996784F@cs.colostate.edu>	<4959C284.4060805@firstpr.com.au>
	<1230690036.5700.7.camel@localhost>	<3c3e3fca0812301907y2feb8904r410845562929a8ed@mail.gmail.com>
	<1230720711.5901.25.camel@localhost>
In-Reply-To: <1230720711.5901.25.camel@localhost>
Subject: Re: [rrg] Proposals which match rrgarchitectures.html pls check the
 page
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Here is a page:

  http://www.firstpr.com.au/ip/ivip/rrgarch/

in which I attempt to match proposals to Bill's Summary of architectures:

  http://www.firstpr.com.au/ip/ivip/rrgarch/

Please let me know via the list of any suggestions for improving this.

  - Robin

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Fri Jan  2 22:54:46 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4AE9E3A680B;
	Fri,  2 Jan 2009 22:54:46 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 629103A680B
	for <rrg@core3.amsl.com>; Fri,  2 Jan 2009 22:54:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.598
X-Spam-Level: 
X-Spam-Status: No, score=-1.598 tagged_above=-999 required=5 tests=[AWL=0.297, 
	BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 1q8W+wr1n5Qh for <rrg@core3.amsl.com>;
	Fri,  2 Jan 2009 22:54:44 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123])
	by core3.amsl.com (Postfix) with ESMTP id 131003A67AA
	for <rrg@irtf.org>; Fri,  2 Jan 2009 22:54:43 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6])
	by gair.firstpr.com.au (Postfix) with ESMTP id 22B96175D22;
	Sat,  3 Jan 2009 17:54:29 +1100 (EST)
Message-ID: <495F0BAA.2040303@firstpr.com.au>
Date: Sat, 03 Jan 2009 17:54:34 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: RRG <rrg@irtf.org>
Subject: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Short version:     We should reject Strategy B.  (I think no-one
                   argues against rejecting C and above.)

                   It would make no sense to recommend the IETF
                   actively develop such a scheme, even if we
                   thought it was desirable to push responsibility
                   for multihoming etc. to hosts, since:

                   1 - There are no substantial Strategy B proposals
                       while there are several substantial Strategy A
                       proposals.

                   2 - All possible Strategy B solutions have much
                       steeper barriers to widespread adoption than
                       any Strategy A solution, since all Strategy
                       B solutions involve changes to host stacks
                       and applications (as well as most or all
                       networks abandoning IPv4 in favour of IPv6)
                       and because Strategy B solutions only provide
                       multihoming etc. when both hosts are upgraded.

Our task is to recommend one (or more than one?) architectural
solutions to the routing scaling problem, to be developed further by
the IETF.

I believe we should recommend one or more architectural solutions
which both:

1 - Show good promise of being able to solve the problem, if widely
    adopted.

2 - Show good promise of being very widely adopted.

    We need close to 100% adoption.  50% or 95% isn't good enough,
    since those end-user networks which want multihoming and don't
    adopt the solution will continue to use the PI and BGP approaches
    to multihoming.  We can't enforce a solution - it has to be
    attractive to virtually all end-user networks which want
    multihoming, TE and portability.  This means end-user networks of
    all types and sizes.  These networks don't necessarily care about
    routing scaling - so the solution must provide immediate,
    substantial benefits over whatever costs, risks and disruption
    the solution involves.

Strategy A solutions are all "core-edge separation schemes".  Apart
from Six/One Router's inability to work with IPv4, they all have a
chance of meeting these two criteria - although opinions vary on
which proposal meets them both best.

I believe there is such a sharp distinction between the Strategy A
and Strategy B proposals that we should only seriously consider
Strategy A proposals for recommendation to the IETF.

How well could Strategies A and B resolve the only scaling problem we
currently have - IPv4's?

  Most of the Strategy A proposals (LISP-NERD, LISP-ALT, APT, Ivip
  and TRRP) are intended to work with IPv4.

  Strategy B proposals cannot help with the IPv4 routing scaling
  problem because there is not enough space for each multihomed
  end-user  network to be given a prefix by each of its two or more
  ISPs.

How many reasonably well documented proposals are there?

  Strategy A:   Six: LISP-NERD, LISP-ALT, APT, Ivip, TRRP and Six/One
                     Router.

                (However, I am not sure that Six/One Router is still
                being actively developed.  There have been no
                updates since my critique in July 2008.  The last
                update to the LISP-NERD I-D was April 2008.
                Six/One Router has no mapping system and TRRP
                documentation is minimal.)

   Strategy B:  There are no properly documented proposals.

                ILNP may be a Strategy B approach but it is not
                properly documented as a scalable routing solution.
                There is no Summary and Analysis in the RRG wiki.

                HIP has been mentioned, but no-one seems to be
                proposing it as a scalable routing solution.

Every possible Strategy B approach would be vastly harder to have
adopted by the majority of end-user networks which want multihoming,
TE and portability (or its functional equivalent) than any Strategy A
approach, for at least two reasons:

  1 - Strategy B solutions require most or all current Internet users
      to adopt IPv6 - and furthermore IPv6 with a modified host
      stack, API and applications.

  2 - Strategy B solutions provides benefits to adoptors only when
      the other host in a session (stack and relevant applications)
      has been upgraded too.  So until almost all networks and their
      hosts adopted it, the scheme could only provide multihoming for
      a fraction of communication sessions.

Also, I argue that any approach which involves pushing
responsibilities and management traffic to all hosts (all potential
Strategy B approaches) is fundamentally flawed:

  http://www.irtf.org/pipermail/rrg/2008-November/000233.html


I find it impossible to imagine how a Strategy B solution could
succeed if we fail to solve the problem via the best one or more
Strategy A solutions being properly developed and offered for adoption.

RRG rejection of Strategy B solutions is not to suggest that people
shouldn't work on such schemes.  Just that we have no confidence that
any such scheme could turn out to be technically better and/or easier
to have widely adopted than a well developed version of the best of
the Strategy A schemes.

Of course, if the best efforts with Strategy A schemes fails, then
everything would be up for reconsideration.  However, that is a
potential scenario in the post-2020 future.  Then, any Strategy B
solution would still involve much higher barriers to development and
adoption than any Strategy A solution.


 - Robin
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sat Jan  3 03:18:46 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 93B0D3A68D7;
	Sat,  3 Jan 2009 03:18:46 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6F5FB3A68D7
	for <rrg@core3.amsl.com>; Sat,  3 Jan 2009 03:18:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.638
X-Spam-Level: 
X-Spam-Status: No, score=-4.638 tagged_above=-999 required=5 tests=[AWL=0.471, 
	BAYES_05=-1.11, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 8sUoNw+OKBp2 for <rrg@core3.amsl.com>;
	Sat,  3 Jan 2009 03:18:44 -0800 (PST)
Received: from smtp02.uc3m.es (smtp02.uc3m.es [163.117.176.132])
	by core3.amsl.com (Postfix) with ESMTP id 2B7803A6405
	for <rrg@irtf.org>; Sat,  3 Jan 2009 03:18:42 -0800 (PST)
Received: from localhost (webcartero01.uc3m.es [163.117.136.131])by 
	smtp02.uc3m.es (Postfix) with ESMTP id D41A6653E3Ffor <rrg@irtf.org>;
	Sat, 3 Jan 2009 12:18:26 +0100 (CET)
Received: from 
	r190-132-67-3.dialup.mobile.ancel.net.uy(r190-132-67-3.dialup.mobile.ancel.
	net.uy [190.132.67.3]) bywebcartero01.uc3m.es (Horde MIME library) with
	HTTP; Sat, 03 Jan 200912:18:25 +0100
Message-ID: <20090103121825.co8r3bgpwkwwggk4@webcartero01.uc3m.es>
Date: Sat, 03 Jan 2009 12:18:25 +0100
From: MARCELO BAGNULO BRAUN <marcelo@it.uc3m.es>
To: rrg@irtf.org
References: <4959B44C.2030709@firstpr.com.au><885A118B-76C8-4E8D-91C0-7C5C6 
	996784F@cs.colostate.edu><4959C284.4060805@firstpr.com.au><1230690036.5700
	.7.camel@localhost><3c3e3fca0812301907y2feb8904r410845562929a8ed@mail.gmail
	.com><1230720711.5901.25.camel@localhost><495EF3B1.1030408@firstpr.com.au>
In-Reply-To: <495EF3B1.1030408@firstpr.com.au>
MIME-Version: 1.0
Content-Disposition: inline
User-Agent: Internet Messaging Program (IMP) H3 (4.0.4)
X-imss-version: 2.051
X-imss-result: Passed
X-imss-scanInfo: M:B L:E SM:2
X-imss-tmaseResult: TT:1 TS:-21.2594 TC:1F TRN:41 TV:5.5.1026(16378.006)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
Subject: Re: [rrg] Proposals which match rrgarchitectures.html pls check
	thepage
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

In the page you mention:

Strategy B
This is the elimination class of proposals.  Any such proposal requires 
new host functions, including changes to host stacks, APIs and 
applications.  Strategy B solutions do not not require changes to the 
interdomain routing system or to the rest of the network, except 
perhaps improvements to DNS.

No-one is suggesting such a solution for IPv4 - they are all 
modifications to IPv6.  This is due, in part, to the lack of IPv4 
address space required for this technique, in which each multihomed 
end-user network has a block of space from each upstream ISP, of the 
same size as its network's address space.

ILNP is one such proposal, I think.  HIP may be another.  However 
neither of these is fully documented as a solution to the routing 
scaling problem.

SHIM6 may match this class, but it does not provide proper multihoming, 
with ease of choosing a new ISP, as we are trying to achieve with a 
scalable routing solution.


MB> Shim6 does not requires changes in the APIs nor in the 
applications. So under the definition included in the page, SHIM6 is 
not a strategy B proposal.. Second, i certainly don't agree with the 
statement that shim6 does not provides multihoming.
In addition, i think ProxyShim6 is likely to fit in a strategy B proposal.
Finally, there are tons of geo aggregation proposals, since Deering's 
metro addressing, IXP based addressing, Iljitsch geo addressing.

Regards, marcelo

Robin Whittle <rw@firstpr.com.au> dijo:

> Here is a page:
>
>  http://www.firstpr.com.au/ip/ivip/rrgarch/
>
> in which I attempt to match proposals to Bill's Summary of architectures:
>
>  http://www.firstpr.com.au/ip/ivip/rrgarch/
>
> Please let me know via the list of any suggestions for improving this.
>
>  - Robin
>
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> https://www.irtf.org/mailman/listinfo/rrg
>



-- 
----
MARCELO BAGNULO BRAUN
WebCartero
Universidad Carlos III de Madrid

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sat Jan  3 04:32:10 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D11533A67F3;
	Sat,  3 Jan 2009 04:32:10 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D65C53A67F3
	for <rrg@core3.amsl.com>; Sat,  3 Jan 2009 04:32:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id jtacVYkSVPba for <rrg@core3.amsl.com>;
	Sat,  3 Jan 2009 04:32:09 -0800 (PST)
Received: from QMTA04.emeryville.ca.mail.comcast.net
	(qmta04.emeryville.ca.mail.comcast.net [76.96.30.40])
	by core3.amsl.com (Postfix) with ESMTP id 3548E3A6783
	for <rrg@irtf.org>; Sat,  3 Jan 2009 04:32:09 -0800 (PST)
Received: from OMTA07.emeryville.ca.mail.comcast.net ([76.96.30.59])
	by QMTA04.emeryville.ca.mail.comcast.net with comcast
	id z0Uc1a00B1GXsucA40XwuV; Sat, 03 Jan 2009 12:31:56 +0000
Received: from TONYLTM9XP ([24.6.155.154])
	by OMTA07.emeryville.ca.mail.comcast.net with comcast
	id z0Xu1a00D3L8a8Q8T0XuQP; Sat, 03 Jan 2009 12:31:56 +0000
From: "Tony Li" <tony.li@tony.li>
To: "'William Herrin'" <bill@herrin.us>
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com>
	<87D9F0BA2807456A88B0427241A29F65@ad.redback.com>
	<3c3e3fca0901021219t2ab35dfsb2532e0c89be84af@mail.gmail.com>
	<E99E41EB33084B5B899C7EED9DE607E9@ad.redback.com>
	<3c3e3fca0901021334j22d17e54iec4bbf41b6c00480@mail.gmail.com>
Date: Sat, 3 Jan 2009 04:31:02 -0800
Message-ID: <BCFF32A1356842BF839C7DF7D059F15F@ad.redback.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
In-Reply-To: <3c3e3fca0901021334j22d17e54iec4bbf41b6c00480@mail.gmail.com>
Thread-Index: AcltIeKc0gY5XJCvTFaa4xloB3bo4gAfPrpQ
Cc: 'RRG' <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

 

|> Seems not unreasonable to me.  Since our current 
|architecture can't support
|> that kind of multi-homing load, we're trying to avoid the load.
|
|Now wait a minute; Brian just told us that we can't say with any
|scientific or engineering certainty what kind of multihoming load the
|current architecture can or can't support. Which is it? Can we? Or
|can't we?


We already know that we're growing the table faster than technology can keep
up.  That much is clear.


|You follow the logical inconsistency, right?


If you're expecting Brian and I to be consistent, I have a bridge to sell
you.  ;-)

Tony

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sat Jan  3 06:32:55 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1F0903A6807;
	Sat,  3 Jan 2009 06:32:55 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 93A293A6893
	for <rrg@core3.amsl.com>; Sat,  3 Jan 2009 06:32:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.455
X-Spam-Level: 
X-Spam-Status: No, score=-0.455 tagged_above=-999 required=5
	tests=[AWL=-0.860, BAYES_00=-2.599, HELO_EQ_AU=0.377,
	HOST_EQ_AU=0.327, MANGLED_TOOL=2.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 1vKFK8iu47iI for <rrg@core3.amsl.com>;
	Sat,  3 Jan 2009 06:32:52 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123])
	by core3.amsl.com (Postfix) with ESMTP id 567FD3A6821
	for <rrg@irtf.org>; Sat,  3 Jan 2009 06:32:52 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6])
	by gair.firstpr.com.au (Postfix) with ESMTP id C02FF1759FA;
	Sun,  4 Jan 2009 01:32:38 +1100 (EST)
Message-ID: <495F770C.4070004@firstpr.com.au>
Date: Sun, 04 Jan 2009 01:32:44 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: rrg@irtf.org
References: <4959B44C.2030709@firstpr.com.au><885A118B-76C8-4E8D-91C0-7C5C6
	996784F@cs.colostate.edu><4959C284.4060805@firstpr.com.au><1230690036.5700	.7.camel@localhost><3c3e3fca0812301907y2feb8904r410845562929a8ed@mail.gmail	.com><1230720711.5901.25.camel@localhost><495EF3B1.1030408@firstpr.com.au>
	<20090103121825.co8r3bgpwkwwggk4@webcartero01.uc3m.es>
In-Reply-To: <20090103121825.co8r3bgpwkwwggk4@webcartero01.uc3m.es>
Cc: Randall Atkinson <rja@extremenetworks.com>
Subject: Re: [rrg] Proposals which match rrgarchitectures.html pls
	check	thepage
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Short version:     I need help in deciding which existing proposals
                   (including those not really discussed much in the
                   RRG) - if any - fit Strategy B.

                   Is ProxyShim6 a scalable routing proposal?  If so
                   does it really fit Strategy B, or is a new
                   classification needed?

Hi Marcelo,

Thanks very much for this:

> Shim6 does not requires changes in the APIs nor in the applications.
> So under the definition included in the page, SHIM6 is not a strategy B
> proposal.. Second, i certainly don't agree with the statement that shim6
> does not provides multihoming.

OK - I agree.  Perhaps the objections to Shim6 in terms of it being a
scalable routing solution, in addition to it not being helpful for
IPv4, include:

  1 - It is host-based rather than router based.  (Questions of
      where it is implemented and where it is controlled and
      monitored from.)

  2 - It provides no portability - networks still need to renumber
      when choosing a new ISP.  Renumbering is still disruptive
      and expensive, including due to the appearance of IP addresses
      in various places inside and outside the network which are not
      amenable to secure automatic changes.

  3 - Problems with maintaining ACLs in other networks for hosts
      using SHIM6.

  4 - Need for both hosts to support Shim6, when it is still being
      developed and is not widely deployed.


> In addition, i think ProxyShim6 is likely to fit in a strategy B proposal.

Ahh, I see that your I-D:

  http://tools.ietf.org/html/draft-bagnulo-pshim6-02

includes a list of problems with Shim6 which mentions points 1 and 2
above.

A quick scan of the I-D makes me think that it doesn't match Bill's
text:

   "GUID to LOC maps are pushed from the host towards a distributed
    registry as they change. Hosts request and temporarily cache
    individual mappings from the registry as needed."?

Are you suggesting that ProxyShim6 is, or is an important part of, a
solution to the IPv6 routing scaling problem?

If so, then I suggest it would be good to write up a summary and
analysis document and add a link to it from the RRG wiki.  (See:
http://psg.com/lists/rrg/2007/msg00908.html .)  Also, does it really
fit Strategy B or should Bill make a new strategy to match it?


> Finally, there are tons of geo aggregation proposals, since Deering's
> metro addressing, IXP based addressing, Iljitsch geo addressing.

I have updated the page from version 00 to 01.  The start of the page
tells how to see the older versions.  At the end of the page is a
Loose Ends and Discussion section.

Here are the changes:

Deleted this mention of SHIM6 from Strategy B and retained its
mention in Strategy G.

Added to the Loose Ends and Discussion section some queries about
whether ILNP or HIP really match Bill's description.  For instance,
do they involve a mapping system, to match: "GUID to LOC maps are
pushed from the host towards a distributed registry as they change.
Hosts request and temporarily cache individual mappings from the
registry as needed."?

Linked to this message regarding the status of ProxyShim6.

  - Robin
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sat Jan  3 09:47:58 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3DC3E3A6A78;
	Sat,  3 Jan 2009 09:47:58 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AFD8E3A6A78
	for <rrg@core3.amsl.com>; Sat,  3 Jan 2009 09:47:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.41
X-Spam-Level: 
X-Spam-Status: No, score=-6.41 tagged_above=-999 required=5 tests=[AWL=0.189, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id neKpkqPIUUeZ for <rrg@core3.amsl.com>;
	Sat,  3 Jan 2009 09:47:55 -0800 (PST)
Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159])
	by core3.amsl.com (Postfix) with ESMTP id CEE3C3A69E2
	for <rrg@irtf.org>; Sat,  3 Jan 2009 09:47:53 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by
	exprod7ob103.postini.com ([64.18.6.12]) with SMTP
	ID DSNKSV+kuzXHahYtPQ1Pq765wM5VAaiivcxp@postini.com;
	Sat, 03 Jan 2009 09:47:43 PST
Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net
	(172.24.192.35) with Microsoft SMTP Server id 8.1.336.0;
	Sat, 3 Jan 2009 09:47:36 -0800
Received: from p-emlb02-sac.jnpr.net ([66.129.254.47]) by
	p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959);
	Sat, 3 Jan 2009 09:47:35 -0800
Received: from emailwf1.jnpr.net ([10.10.2.33]) by p-emlb02-sac.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.3959);	 Sat, 3 Jan 2009 09:47:35 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Date: Sat, 3 Jan 2009 12:47:34 -0500
Message-ID: <3525C9833C09ED418C6FD6CD9514668C0566045E@emailwf1.jnpr.net>
In-Reply-To: <BCFF32A1356842BF839C7DF7D059F15F@ad.redback.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] BGP scaling limit?
Thread-Index: AcltIeKc0gY5XJCvTFaa4xloB3bo4gAfPrpQAAk8AcA=
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com><87D9F0BA2807456A88B0427241A29F65@ad.redback.com><3c3e3fca0901021219t2ab35dfsb2532e0c89be84af@mail.gmail.com><E99E41EB33084B5B899C7EED9DE607E9@ad.redback.com><3c3e3fca0901021334j22d17e54iec4bbf41b6c00480@mail.gmail.com>
	<BCFF32A1356842BF839C7DF7D059F15F@ad.redback.com>
From: Ross Callon <rcallon@juniper.net>
To: <tony.li@tony.li>,
	"William Herrin" <bill@herrin.us>
X-OriginalArrivalTime: 03 Jan 2009 17:47:35.0548 (UTC)
	FILETIME=[5C8FB3C0:01C96DCB]
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org


> We already know that we're growing the table faster than technology
> can keep up.  That much is clear. (Tony Li)

Tony;

I have a question and a comment.

First the question: What do you mean by "we're growing the table faster
than technology can keep up". Are you referring to Forwarding Table
size, BGP processing and traffic loads, or something else? Do you mean
"with a table of 100,000,000 entries, there will need to be at a minimum
some incremental update to existing deployed implementations" (to which
my teenage daughter might say "duh!"), or do you mean "it won't be
economically reasonable to build products unless we make some localized
internal (within a router) change to a few algorithms?", or do you mean
"it will be financially too expensive to build products that can handle
some future table size", or do you mean "it will not be technically
possible to build the routers", or do you mean something else? 

Secondly, depending upon precisely what you mean by "faster than the
technology can keep up", speaking as an individual, it is quite likely
that I disagree. I hope that any disagreement is not automatically
declared to be off-topic. 

Ross

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sat Jan  3 11:32:40 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 37D803A6821;
	Sat,  3 Jan 2009 11:32:40 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F33AE3A6821
	for <rrg@core3.amsl.com>; Sat,  3 Jan 2009 11:32:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.566
X-Spam-Level: 
X-Spam-Status: No, score=-2.566 tagged_above=-999 required=5 tests=[AWL=0.033, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ZJU6KQ6wdn9T for <rrg@core3.amsl.com>;
	Sat,  3 Jan 2009 11:32:38 -0800 (PST)
Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.184])
	by core3.amsl.com (Postfix) with ESMTP id D20303A6820
	for <rrg@irtf.org>; Sat,  3 Jan 2009 11:32:37 -0800 (PST)
Received: by ti-out-0910.google.com with SMTP id b8so5763108tic.11
	for <rrg@irtf.org>; Sat, 03 Jan 2009 11:32:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from
	:organization:user-agent:mime-version:to:cc:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=gJGygOYciDua3qax6G9GGxqQd2qrN8OjJYeL9X7oToA=;
	b=RCABpVuvfjVR97F8RAVrnYT225XLFXhjge97UyFVi9Bk711H5E66O6qvLoa7ohgC7Y
	lfRPkMGHFyHA0UOfYRZkviz0Wun6hh/UbuDCFB4lqjebE8um/LifzQLZfnS+PI8j8Mne
	kZCOcrlaFbmZJyElXh+W/pv35dUt80AGHEuAo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	b=xAwAZsPdIvZtr1XMGu2yzG7oe3/GtxbqDgfADWZ3w4rSPjlVu2uxn0PmR2cAviJupX
	eLVlfnl1R9/xvdX66D7OE7QYF6DK5bKzu9N4qGqUjw9hUlkZseYRUXJNCmf++cplbx5n
	VRAcykM1MrU4/pKuB/KpJgCk0pFmrPhIVg3ZI=
Received: by 10.110.39.20 with SMTP id m20mr1014660tim.42.1231011144795;
	Sat, 03 Jan 2009 11:32:24 -0800 (PST)
Received: from ?10.1.1.4? (118-93-170-114.dsl.dyn.ihug.co.nz [118.93.170.114])
	by mx.google.com with ESMTPS id
	d7sm16434320tib.37.2009.01.03.11.32.21
	(version=SSLv3 cipher=RC4-MD5); Sat, 03 Jan 2009 11:32:23 -0800 (PST)
Message-ID: <495FBD42.5060504@gmail.com>
Date: Sun, 04 Jan 2009 08:32:18 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: tony.li@tony.li
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com>	<87D9F0BA2807456A88B0427241A29F65@ad.redback.com>	<3c3e3fca0901021219t2ab35dfsb2532e0c89be84af@mail.gmail.com>	<E99E41EB33084B5B899C7EED9DE607E9@ad.redback.com>	<3c3e3fca0901021334j22d17e54iec4bbf41b6c00480@mail.gmail.com>
	<BCFF32A1356842BF839C7DF7D059F15F@ad.redback.com>
In-Reply-To: <BCFF32A1356842BF839C7DF7D059F15F@ad.redback.com>
Cc: 'RRG' <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On 2009-01-04 01:31, Tony Li wrote:
>  
> 
> |> Seems not unreasonable to me.  Since our current 
> |architecture can't support
> |> that kind of multi-homing load, we're trying to avoid the load.
> |
> |Now wait a minute; Brian just told us that we can't say with any
> |scientific or engineering certainty what kind of multihoming load the
> |current architecture can or can't support. Which is it? Can we? Or
> |can't we?
> 
> 
> We already know that we're growing the table faster than technology can keep
> up.  That much is clear.
> 
> 
> |You follow the logical inconsistency, right?
> 
> 
> If you're expecting Brian and I to be consistent, I have a bridge to sell
> you.  ;-)

I will expect commission on that deal. However, the fact that the esteemed
Mr Li and the esteemed Mr Callon appear to disagree supports my assertion
that we don't know when we'll hit the wall. We do know it's two years
closer than it was at the RAWS workshop, though, so the conclusion that
we need a solution in hand stands, IMHO.

   Brian
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sat Jan  3 13:20:34 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A19203A684F;
	Sat,  3 Jan 2009 13:20:34 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 04B803A684F
	for <rrg@core3.amsl.com>; Sat,  3 Jan 2009 13:20:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.965
X-Spam-Level: 
X-Spam-Status: No, score=-1.965 tagged_above=-999 required=5 tests=[AWL=0.012, 
	BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 7EYTRq6oV3ao for <rrg@core3.amsl.com>;
	Sat,  3 Jan 2009 13:20:32 -0800 (PST)
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.183])
	by core3.amsl.com (Postfix) with ESMTP id 008F43A67AC
	for <rrg@irtf.org>; Sat,  3 Jan 2009 13:20:31 -0800 (PST)
Received: by wa-out-1112.google.com with SMTP id j37so3811024waf.23
	for <rrg@irtf.org>; Sat, 03 Jan 2009 13:20:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:sender
	:to:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references
	:x-google-sender-auth;
	bh=T/1xeMjv78Ud+0hn570DDcMdDrm5dBOch75YkGrhjuY=;
	b=HvHYawnbOs3BVrRKZrcqNgg4dGFIM6lOReItT4LKL80AfY+CthzcWwapaZPuYUjn4M
	EnTRuDUWDodfbDEoZDYqf1fZp1koUHGT79nHP9/B/P+uSnvrgdcaD5ML/CMA7A69dht8
	WZRJcSK3t4/CvzQnpmIXX37gcFlrgxmTDSHgI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references:x-google-sender-auth;
	b=QkypOvbvKwmGHT7Ex59NN0ny+xNeNZ4WRMZlQwwiEjOdmtPkxVBP4V5hZboobTa9+8
	RnbA9eUumjr/VaWZM6fE/eY8w+MW5eEQ3+i2+yJ7so4lFHvNdpgGhIAr28ErJpoMC/W4
	+6n2sikcwaxkGBC2L9i0xHGiJQluM5HWkiM2M=
Received: by 10.115.110.1 with SMTP id n1mr12699448wam.102.1231017618589;
	Sat, 03 Jan 2009 13:20:18 -0800 (PST)
Received: by 10.115.74.12 with HTTP; Sat, 3 Jan 2009 13:20:18 -0800 (PST)
Message-ID: <3c3e3fca0901031320o1253fcd3s3b6597aef77fba33@mail.gmail.com>
Date: Sat, 3 Jan 2009 16:20:18 -0500
From: "William Herrin" <bill@herrin.us>
To: tony.li@tony.li
In-Reply-To: <BCFF32A1356842BF839C7DF7D059F15F@ad.redback.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com>
	<87D9F0BA2807456A88B0427241A29F65@ad.redback.com>
	<3c3e3fca0901021219t2ab35dfsb2532e0c89be84af@mail.gmail.com>
	<E99E41EB33084B5B899C7EED9DE607E9@ad.redback.com>
	<3c3e3fca0901021334j22d17e54iec4bbf41b6c00480@mail.gmail.com>
	<BCFF32A1356842BF839C7DF7D059F15F@ad.redback.com>
X-Google-Sender-Auth: a404d9ad02b33c44
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On Sat, Jan 3, 2009 at 7:31 AM, Tony Li <tony.li@tony.li> wrote:
> |> Seems not unreasonable to me.  Since our current
> |architecture can't support
> |> that kind of multi-homing load, we're trying to avoid the load.
> |
> |Now wait a minute; Brian just told us that we can't say with any
> |scientific or engineering certainty what kind of multihoming load the
> |current architecture can or can't support. Which is it? Can we? Or
> |can't we?
>
>
> We already know that we're growing the table faster than technology can keep
> up.  That much is clear.

Tony,

Is that a falsifiable scientific theory or is it a consensus opinion
without quantitative grounding?

Devil's advocate:

The well-grounded trend lines I posted suggest that the BGP table size
at the edge of what we can build cost-effectively may be compounding
at a rate of 40% per year while the actual size of the BGP table may
only be compounding at around 25% per year. If true, one consequence
should be that the minimum cost of an edge device capable of
participating in the BGP backbone has fallen significantly. This
appears to be the case; a $1400 Cisco 2811 is now capable of
interacting with the full BGP table while 15 years ago you had to
spend $60k on a Cisco 7000 to seriously think about a full BGP table.

So no, the truth of the claim that we're growing the table faster than
technology can keep up is not at all clear.

Regards,
Bill Herrin





-- 
William D. Herrin ................ herrin@dirtside.com  bill@herrin.us
3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
Falls Church, VA 22042-3004
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sat Jan  3 13:39:48 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0935B3A689B;
	Sat,  3 Jan 2009 13:39:48 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 79DA23A689B
	for <rrg@core3.amsl.com>; Sat,  3 Jan 2009 13:39:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.557
X-Spam-Level: 
X-Spam-Status: No, score=-2.557 tagged_above=-999 required=5 tests=[AWL=0.042, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id L3Gfus-6AEDF for <rrg@core3.amsl.com>;
	Sat,  3 Jan 2009 13:39:45 -0800 (PST)
Received: from QMTA09.emeryville.ca.mail.comcast.net
	(qmta09.emeryville.ca.mail.comcast.net [76.96.30.96])
	by core3.amsl.com (Postfix) with ESMTP id B8CB13A67AC
	for <rrg@irtf.org>; Sat,  3 Jan 2009 13:39:45 -0800 (PST)
Received: from OMTA03.emeryville.ca.mail.comcast.net ([76.96.30.27])
	by QMTA09.emeryville.ca.mail.comcast.net with comcast
	id z97q1a0070b6N64A99fZQT; Sat, 03 Jan 2009 21:39:33 +0000
Received: from TONYLTM9XP ([155.53.1.254])
	by OMTA03.emeryville.ca.mail.comcast.net with comcast
	id z9fJ1a0095Up7oj8P9fM0i; Sat, 03 Jan 2009 21:39:31 +0000
From: "Tony Li" <tony.li@tony.li>
To: "'Ross Callon'" <rcallon@juniper.net>, "'William Herrin'" <bill@herrin.us>
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com><87D9F0BA2807456A88B0427241A29F65@ad.redback.com><3c3e3fca0901021219t2ab35dfsb2532e0c89be84af@mail.gmail.com><E99E41EB33084B5B899C7EED9DE607E9@ad.redback.com><3c3e3fca0901021334j22d17e54iec4bbf41b6c00480@mail.gmail.com>
	<BCFF32A1356842BF839C7DF7D059F15F@ad.redback.com>
	<3525C9833C09ED418C6FD6CD9514668C0566045E@emailwf1.jnpr.net>
Date: Sat, 3 Jan 2009 13:38:43 -0800
Message-ID: <354C0AE786D1424C886C4A3570611291@ad.redback.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
In-Reply-To: <3525C9833C09ED418C6FD6CD9514668C0566045E@emailwf1.jnpr.net>
Thread-Index: AcltIeKc0gY5XJCvTFaa4xloB3bo4gAfPrpQAAk8AcAACZ85sA==
Cc: 'RRG' <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org


Hi Ross,

|> We already know that we're growing the table faster than technology
|> can keep up.  That much is clear. (Tony Li)
|
|First the question: What do you mean by "we're growing the table faster
|than technology can keep up". Are you referring to Forwarding Table
|size, BGP processing and traffic loads, or something else?


I'm referring to the growth rate of the full set of prefixes and the
capabilities of the control plane to support it.

Note that I've been saying this pretty consistently for two full years now.


|Do you mean
|"with a table of 100,000,000 entries, there will need to be at 
|a minimum
|some incremental update to existing deployed implementations" (to which
|my teenage daughter might say "duh!"), or do you mean "it won't be
|economically reasonable to build products unless we make some localized
|internal (within a router) change to a few algorithms?", or do you mean
|"it will be financially too expensive to build products that can handle
|some future table size", or do you mean "it will not be technically
|possible to build the routers", or do you mean something else? 


Once again, with feeling:

The growth rate of prefixes that are circulating within the DFZ exceeds the
rate of speed improvement in the underlying DRAM that we use to implement
the control plane.  This will undoubtedly result in architectural changes
and cost increases.  The concern then becomes that over the long term, as
this continues, the cost increases must be absorbed somewhere in the system,
and it is most likely to propagate to the end users, with a net detriment to
the growth of the network.



|Secondly, depending upon precisely what you mean by "faster than the
|technology can keep up", speaking as an individual, it is quite likely
|that I disagree. I hope that any disagreement is not automatically
|declared to be off-topic. 


You're more than welcome to disagree.  However, I hope that we can have a
more constructive discussion that simply reiterating the size of our
personal FIB.

Tony

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sat Jan  3 13:46:45 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4E1F13A69D0;
	Sat,  3 Jan 2009 13:46:45 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9313E3A69D1
	for <rrg@core3.amsl.com>; Sat,  3 Jan 2009 13:46:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.814
X-Spam-Level: 
X-Spam-Status: No, score=-1.814 tagged_above=-999 required=5
	tests=[AWL=-0.704, BAYES_05=-1.11]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Qfm0ZwQ4Mb9l for <rrg@core3.amsl.com>;
	Sat,  3 Jan 2009 13:46:43 -0800 (PST)
Received: from QMTA02.emeryville.ca.mail.comcast.net
	(qmta02.emeryville.ca.mail.comcast.net [76.96.30.24])
	by core3.amsl.com (Postfix) with ESMTP id C79AD3A69D0
	for <rrg@irtf.org>; Sat,  3 Jan 2009 13:46:43 -0800 (PST)
Received: from OMTA05.emeryville.ca.mail.comcast.net ([76.96.30.43])
	by QMTA02.emeryville.ca.mail.comcast.net with comcast
	id z4Hi1a00m0vp7WLA29mY5r; Sat, 03 Jan 2009 21:46:32 +0000
Received: from TONYLTM9XP ([155.53.1.254])
	by OMTA05.emeryville.ca.mail.comcast.net with comcast
	id z9mN1a0085Up7oj8R9mQCL; Sat, 03 Jan 2009 21:46:30 +0000
From: "Tony Li" <tony.li@tony.li>
To: "'William Herrin'" <bill@herrin.us>
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com>
	<87D9F0BA2807456A88B0427241A29F65@ad.redback.com>
	<3c3e3fca0901021219t2ab35dfsb2532e0c89be84af@mail.gmail.com>
	<E99E41EB33084B5B899C7EED9DE607E9@ad.redback.com>
	<3c3e3fca0901021334j22d17e54iec4bbf41b6c00480@mail.gmail.com>
	<BCFF32A1356842BF839C7DF7D059F15F@ad.redback.com>
	<3c3e3fca0901031320o1253fcd3s3b6597aef77fba33@mail.gmail.com>
Date: Sat, 3 Jan 2009 13:45:46 -0800
Message-ID: <A071B6FF07CD4B708EC6CA2B9938096D@ad.redback.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
In-Reply-To: <3c3e3fca0901031320o1253fcd3s3b6597aef77fba33@mail.gmail.com>
Thread-Index: Aclt6RaOhRkx3mYfTQGxi411X7jRGAAApfhg
Cc: 'RRG' <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

 

|> We already know that we're growing the table faster than 
|technology can keep
|> up.  That much is clear.
|
|Is that a falsifiable scientific theory or is it a consensus opinion
|without quantitative grounding?


Worse, that's an opinion, with some quantitative grounding, held by an
apparent minority.


|The well-grounded trend lines I posted suggest that the BGP table size
|at the edge of what we can build cost-effectively may be compounding
|at a rate of 40% per year while the actual size of the BGP table may
|only be compounding at around 25% per year. If true, one consequence
|should be that the minimum cost of an edge device capable of
|participating in the BGP backbone has fallen significantly. This
|appears to be the case; a $1400 Cisco 2811 is now capable of
|interacting with the full BGP table while 15 years ago you had to
|spend $60k on a Cisco 7000 to seriously think about a full BGP table.


More than something of a red herring, given that they are violently
different generations of hardware, with very different levels of hardware
optimization.  The 7000, for example, was built before the networking
industry was on to the ASIC bandwagon.  Since we've transitioned from
technology laggards to being near cutting edge, there have been some one
time advances.


|So no, the truth of the claim that we're growing the table faster than
|technology can keep up is not at all clear.


Fair enough.  

So, why do we keep debating this?  We've been over this to death.  The horse
is dead already.  For folks that feel that there's no problem, why not leave
the rest of us in peace to do what we feel we need to do?

Tony

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sat Jan  3 17:21:00 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BB5783A6952;
	Sat,  3 Jan 2009 17:21:00 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 271653A6952
	for <rrg@core3.amsl.com>; Sat,  3 Jan 2009 17:20:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.965
X-Spam-Level: 
X-Spam-Status: No, score=-1.965 tagged_above=-999 required=5 tests=[AWL=0.012, 
	BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id JIVIoUCPYhgc for <rrg@core3.amsl.com>;
	Sat,  3 Jan 2009 17:20:58 -0800 (PST)
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.177])
	by core3.amsl.com (Postfix) with ESMTP id E56B33A694C
	for <rrg@irtf.org>; Sat,  3 Jan 2009 17:20:57 -0800 (PST)
Received: by wa-out-1112.google.com with SMTP id j37so3838221waf.23
	for <rrg@irtf.org>; Sat, 03 Jan 2009 17:20:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:sender
	:to:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references
	:x-google-sender-auth;
	bh=ioz4X9K8183Bg29Ae9IVkpMN+iO7kQQeiVcka+1Nrc0=;
	b=THdLMUS9wZ/Px8z6Dz2PvTLoPvXFEu+CjErWlHR6e1vpIBELlhi8IFRSFcP3WKbNJD
	wn5w0gX0MZlqv+uO85U1YeMed6MospubEga0Xos4BU5SH3yEWsVMqwRKLY4i3f50WPNQ
	WxoxKb1KLVkKVohSxWmzf8k5VFEQQHfBJq228=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references:x-google-sender-auth;
	b=EBcgglZ8FmagQ8mM87kgQXezraLiWmt/6mspTYvbMNMWphDACMxzZh1J3V9m1mkAqZ
	78QFTHfM5ETh9g4fo4h8igfjSUc7eJFdaE/WL7Yiuud3vFbj4YMCBKZTua6KsX6vyWSh
	pagAajjyVF1lt5sqrtWX5m11R4cw9xD1RoLO8=
Received: by 10.114.159.6 with SMTP id h6mr12781165wae.211.1231032044468;
	Sat, 03 Jan 2009 17:20:44 -0800 (PST)
Received: by 10.115.74.12 with HTTP; Sat, 3 Jan 2009 17:20:44 -0800 (PST)
Message-ID: <3c3e3fca0901031720w602d931ev42707b169f51fba9@mail.gmail.com>
Date: Sat, 3 Jan 2009 20:20:44 -0500
From: "William Herrin" <bill@herrin.us>
To: tony.li@tony.li
In-Reply-To: <A071B6FF07CD4B708EC6CA2B9938096D@ad.redback.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com>
	<87D9F0BA2807456A88B0427241A29F65@ad.redback.com>
	<3c3e3fca0901021219t2ab35dfsb2532e0c89be84af@mail.gmail.com>
	<E99E41EB33084B5B899C7EED9DE607E9@ad.redback.com>
	<3c3e3fca0901021334j22d17e54iec4bbf41b6c00480@mail.gmail.com>
	<BCFF32A1356842BF839C7DF7D059F15F@ad.redback.com>
	<3c3e3fca0901031320o1253fcd3s3b6597aef77fba33@mail.gmail.com>
	<A071B6FF07CD4B708EC6CA2B9938096D@ad.redback.com>
X-Google-Sender-Auth: 5bc2140fdd72be03
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On Sat, Jan 3, 2009 at 4:45 PM, Tony Li <tony.li@tony.li> wrote:
> |The well-grounded trend lines I posted suggest that the BGP table size
> |at the edge of what we can build cost-effectively may be compounding
> |at a rate of 40% per year while the actual size of the BGP table may
> |only be compounding at around 25% per year. If true, one consequence
> |should be that the minimum cost of an edge device capable of
> |participating in the BGP backbone has fallen significantly. This
> |appears to be the case; a $1400 Cisco 2811 is now capable of
> |interacting with the full BGP table while 15 years ago you had to
> |spend $60k on a Cisco 7000 to seriously think about a full BGP table.
>
> More than something of a red herring, given that they are violently
> different generations of hardware, with very different levels of hardware
> optimization.  The 7000, for example, was built before the networking
> industry was on to the ASIC bandwagon.  Since we've transitioned from
> technology laggards to being near cutting edge, there have been some one
> time advances.

The history of the computing industry is one of regularly encountered
one-time advances. Moore's Law isn't built on the back of purely
evolutionary improvement.

That today's router hardware is radically different than that of 15
years ago doesn't refute the sustainability of the growth trend; it
demonstrates it.


> |So no, the truth of the claim that we're growing the table faster than
> |technology can keep up is not at all clear.
>
> Fair enough.
>
> So, why do we keep debating this?  We've been over this to death.  The horse
> is dead already.  For folks that feel that there's no problem, why not leave
> the rest of us in peace to do what we feel we need to do?


I'm debating it because I'm tired of watching us bounce off the
pinball bumpers. Resolving this issue impacts our work here in three
very important ways:

1. It affects whether as a group we reject strategy F, and if we
don't, the language with which we present it.

2. Engineer's maxim: if it ain't broke, don't fix it. If failure does
not loom on BGP's horizon, there is little justification for moving
any disruptive strategy forward from research to engineering. The
desirable output from our efforts is *very* different depending on
whether or not BGP is failing.

3. RIRs make painful, real-world-hurtful decisions based on the
credence they lend the warning of BGP's impending failure. If the end
of the world is no longer nigh, we have a moral responsibility to let
them know.


#3 hits me particularly hard at work where an $800k continuing
operations component of a multi-million dollar project can't justify a
/24 from ARIN for multihoming.

However frightful the monsters under the bed may be, there is
insufficient proof of their existence to justify giving your toddler a
shotgun.

Regards,
Bill Herrin


-- 
William D. Herrin ................ herrin@dirtside.com  bill@herrin.us
3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
Falls Church, VA 22042-3004
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sat Jan  3 18:21:09 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E1E143A6827;
	Sat,  3 Jan 2009 18:21:09 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EDAA43A6827
	for <rrg@core3.amsl.com>; Sat,  3 Jan 2009 18:21:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.427
X-Spam-Level: 
X-Spam-Status: No, score=-1.427 tagged_above=-999 required=5 tests=[AWL=0.153, 
	BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327,
	SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id za1mmFYAdWcC for <rrg@core3.amsl.com>;
	Sat,  3 Jan 2009 18:21:08 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123])
	by core3.amsl.com (Postfix) with ESMTP id A21B13A63EC
	for <rrg@irtf.org>; Sat,  3 Jan 2009 18:21:07 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6])
	by gair.firstpr.com.au (Postfix) with ESMTP id 832DF175E6F;
	Sun,  4 Jan 2009 13:20:53 +1100 (EST)
Message-ID: <49601D0B.6040803@firstpr.com.au>
Date: Sun, 04 Jan 2009 13:20:59 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: RRG <rrg@irtf.org>
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com>	<87D9F0BA2807456A88B0427241A29F65@ad.redback.com>	<3c3e3fca0901021219t2ab35dfsb2532e0c89be84af@mail.gmail.com>	<E99E41EB33084B5B899C7EED9DE607E9@ad.redback.com>	<3c3e3fca0901021334j22d17e54iec4bbf41b6c00480@mail.gmail.com>	<BCFF32A1356842BF839C7DF7D059F15F@ad.redback.com>	<3c3e3fca0901031320o1253fcd3s3b6597aef77fba33@mail.gmail.com>	<A071B6FF07CD4B708EC6CA2B9938096D@ad.redback.com>
	<3c3e3fca0901031720w602d931ev42707b169f51fba9@mail.gmail.com>
In-Reply-To: <3c3e3fca0901031720w602d931ev42707b169f51fba9@mail.gmail.com>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Short version:    The current DFZ growth rates are not our target.
                  In the long term - including ideally the next
                  6 to 10 years - we need to alter the architecture
                  so it can cope well with hundreds of millions of
                  multihomed end-user networks.


I eyeballed the graph:

  http://bgp.potaroo.net

and estimated 16 to 17% per annum growth in the last 3 or 4 years.

I expect this rate of growth will increase in the next few years as
IPv4 space is subdivided more intensively once the last of the fresh
pastures at the edge of town are engulfed.

I think there is little point in discussing whether DRAM speeds, CPU
speeds etc. can cope with the current rate of growth in the DFZ in
the long term.

In the long term, we need to enhance the architecture of the Net to
cope happily with a much larger growth in the numbers of end-user
networks which have multihoming, TE and portability.

I suggest we should be happy with a system which is technically and
commercially agreeable with numbers of such end-user networks like:

  2016      1M
  2020     16M
  2024    256M

This is 100% PA growth.  Each end-user network will probably have
multiple prefixes too, for load sharing over multiple links and for
their multiple sites - so the total number of portable, multihomable,
prefixes needed will be 2 to 10 times this.

Ideally, the scalable routing solution should be technically and
commercially capable of scaling within a few years of introduction to
a hundred million or so separate prefixes (or non-binary length
spans) of end-user network address space.  However, I guess it would
take a few years for such levels of demand to eventuate (not counting
the immense demand for stable IP addresses for mobile devices).

There's no way that CPUs and RAM, for either the RIB or the FIB, can
cope with this sort of growth, as long as the prefixes are provided
by the current BGP-based techniques.

Even if we could somehow build and afford the routers, this would be
an inelegant, unstable and probably unmanageable number of prefixes
to expect the interdomain routing system to cope with.

The current system is unacceptable since it doesn't fit the needs of
many end-user networks.  The disparity between the unadorned BGP
system's capabilities and the needs of end-user networks will get
worse with every passing year.

I don't think there is any brick wall where the interdomain routing
system as we run it today will stop working.  I am sure DFZ routers
can be built to handle 20% PA growth in DFZ prefixes.  (Despite what
I wrote about DRAM latency, routers could be built with faster
memories, including static RAM and/or with multiple CPU-RAM systems
sharing the RIB and FIB loads.)

Our success will be measured in how soon we can devise a better way
of providing hundreds of millions of end-user networks with
multihoming, TE and portability.

IPv4 address space will become harder and harder to get, since every
customer needs one such address.  A good core-edge separation scheme
could improve on this considerably, by enabling improved address
utilization.  It could do this by enabling many end-user networks to
multihome etc. with as small a number of addresses as they really
need - not in multiples of 256, 512 etc.

Another measure of our success will be how well the scalable routing
solution enables more efficient IPv4 address utilization.  That will
provide more time for figuring out an alternative to IPv4.

Ideally, a well designed solution to the routing scaling problem
could help with the transition to whatever lies beyond IPv4.

Ideally, it will help with mobility too.

  - Robin

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sat Jan  3 18:26:25 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 368323A6818;
	Sat,  3 Jan 2009 18:26:25 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4E35C3A6818
	for <rrg@core3.amsl.com>; Sat,  3 Jan 2009 18:26:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.131
X-Spam-Level: 
X-Spam-Status: No, score=-0.131 tagged_above=-999 required=5
	tests=[AWL=-1.151, BAYES_50=0.001, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, 
	SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6WSLOrx77ICu for <rrg@core3.amsl.com>;
	Sat,  3 Jan 2009 18:26:23 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123])
	by core3.amsl.com (Postfix) with ESMTP id AF73C3A63EC
	for <rrg@irtf.org>; Sat,  3 Jan 2009 18:26:22 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6])
	by gair.firstpr.com.au (Postfix) with ESMTP id BACA5175E6F;
	Sun,  4 Jan 2009 13:26:09 +1100 (EST)
Message-ID: <49601E47.9000704@firstpr.com.au>
Date: Sun, 04 Jan 2009 13:26:15 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: RRG <rrg@irtf.org>
Subject: [rrg] 10M ... 100M end-user networks
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Short version:    The current number and rate of growth in the number
                  of multihomed end-user networks is not our
                  primary concern.

                  Our aim, as best I understand it, is to design
                  an architectural enhancement for the Internet
                  by which the much higher numbers of end-user
                  networks which want/need multihoming, TE and
                  address portability can have these in a manner
                  which is technically and economically sustainable
                  for ISPs and for the end-user networks
                  themselves.

                  A system which would work nicely with 10M
                  such end-user networks would be good.  One
                  which scales well to 100M or 1B would be better.

                  Ideally the system should have an architecture
                  and business arrangements whereby each end-user
                  network does not impose unreasonable burdens on
                  others due to its activities, including how
                  many prefixes they advertise, how often they
                  change these advertisements and other matters
                  such as their share of traffic on OITRDs
                  (Open ITRs in the DFZ = LISP PTRs).  When
                  such a system can technically scale well to
                  100s of millions of end-user networks - or
                  perhaps billions - and can be run as a series
                  of profitable businesses, then there will be
                  no scaling limits (or at least not for decades
                  to come) and little or no unreasonable burden
                  of costs.

                  I think Ivip has a much better chance of
                  achieving this than other proposals.

                  http://www.firstpr.com.au/ip/ivip/Ivip-summary.pdf


In "Re: BGP scaling limit?" Tony wrote:

> We already know that we're growing the table faster than
> technology can keep up.  That much is clear.

I am not convinced that this is the case right now, since I can
imagine the continued advances in multi-CPU chips (with each CPU
running at 3GHz or more, with its own cache) with sufficiently large
amounts of static RAM, would be able to perform (separately) the RIB
and 1/10/40 Gbps FIB functions.  However, that would be expensive and
inelegant - and would raise the real cost of DFZ routers in a manner
I think is unreasonable.  Keeping the current system and souping up
the routers like this would perpetuate and exacerbate the current
problems, including:

  1 - Difficulty and high costs for any end-user network which wants
      or needs multihoming, TE and portability.

  2 - Every such network advertising its one, two or more prefixes
      placing an unreasonable burden on ISPs and multihomed end-user
      networks all over the world by adding to the RIB and FIB
      workload of their routers.   (Assuming these DFZ routers do
      carry the prefixes.)

  3 - This burden is shared across all Internet users.  A result of
      this is higher barriers to Internet use than would otherwise be
      the case - which shuts out some poorer people from using the
      Net at all.

  4 - A grey area of investment, unreasonable burdens and risk as
      DFZ router operators are increasing tempted not to accept
      some prefixes of multihomed end-user networks.

  5 - Consequently, an increasing number of end-user networks
      not getting the reliable service they need, at a time of
      increasing demand, increasingly diverse usage, and increasing
      moment-to-moment dependence on Internet communications.


I thought we agreed that our task is to modify the Net so the current
scaling difficulties with the BGP routing system are resolved, not
just for a continuation of current growth rates, but for 10s or 100s
of millions of multihomed end-user networks gaining multihoming, TE
and portability.

If not, I think now would be a good time to check consensus that we
are not just trying to cope with the existing, unacceptably
constrained, growth in the number of end-user networks with
multihoming, TE and portability, but to create a network which
technically and commercially cope well with some very large number of
such end-user networks.

A scheme which could clearly cope with 100M would be a good start.

Ideally - in my view - the system would be extendible to support a
form of mobility in which billions of mobile devices could keep their
IP address, or prefix, no matter where they physically connect to the
Net.  A plan for this is in the paper Steve Russert and I wrote:

  TTR Mobility Extensions for Core-Edge Separation Solutions to the
  Internet's Routing Scaling Problem
  http://www.firstpr.com.au/ip/ivip/#mobile

The key to this is that a mapping change is only needed when the
point of attachment moves such a distance (such as ~1000km) from the
currently used TTR that it is best to choose another TTR.  This will
happen far less frequently than the changes in connection point, or
change of which access networks are used for the connection.

Each Ivip mapping change is paid for, so there are little or no
unreasonable cost burdens resulting from these changes.

 - Robin

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sat Jan  3 20:28:40 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9FEA13A6821;
	Sat,  3 Jan 2009 20:28:40 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D6BF03A6821
	for <rrg@core3.amsl.com>; Sat,  3 Jan 2009 20:28:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.566
X-Spam-Level: 
X-Spam-Status: No, score=-2.566 tagged_above=-999 required=5 tests=[AWL=0.033, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id tXc2Cv5zwK6Q for <rrg@core3.amsl.com>;
	Sat,  3 Jan 2009 20:28:39 -0800 (PST)
Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.191])
	by core3.amsl.com (Postfix) with ESMTP id B13643A67A7
	for <rrg@irtf.org>; Sat,  3 Jan 2009 20:28:38 -0800 (PST)
Received: by ti-out-0910.google.com with SMTP id b8so5834756tic.11
	for <rrg@irtf.org>; Sat, 03 Jan 2009 20:28:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from
	:organization:user-agent:mime-version:to:cc:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=EXqS6TU5A4Qoi5y5GAa+D9ysFAbLobcB3QvEZYivvbM=;
	b=rwskgTbQhwG1oN7BVvB47B3WIqXqfeV1EgtInvcgbjFuJL42AUTIFaiRsJDqEg5Nmd
	n/XOlNtatH41LUMgJ891l3/oAFsuK56qxw8/+9XBgO3apzQPVSc66Fufh2bOTOns3prO
	7JkM2ymT3FhqF1MRICpufzE9r2c4InYNllzE8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	b=KSILGYaSMTl7SyyvGceijEFKemzQYbEiG0Zy4inJuDyX/soNiIXZhlVMdwDh4hWNji
	10eped00u54X2qSivS94Ex6TpAzR4WQ/9cLDemCBrbiSZTxQy520Pj6MIGrdNvpRXNi4
	Ogtp9I5XlP6JDaTCQ2IiTdQ59CECUHRS+VG14=
Received: by 10.110.5.18 with SMTP id 18mr9055278tie.54.1231043305108;
	Sat, 03 Jan 2009 20:28:25 -0800 (PST)
Received: from ?10.1.1.4? (118-93-170-114.dsl.dyn.ihug.co.nz [118.93.170.114])
	by mx.google.com with ESMTPS id
	u12sm2102583tia.29.2009.01.03.20.28.22
	(version=SSLv3 cipher=RC4-MD5); Sat, 03 Jan 2009 20:28:24 -0800 (PST)
Message-ID: <49603AE9.9000005@gmail.com>
Date: Sun, 04 Jan 2009 17:28:25 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: William Herrin <bill@herrin.us>
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com>	<87D9F0BA2807456A88B0427241A29F65@ad.redback.com>	<3c3e3fca0901021219t2ab35dfsb2532e0c89be84af@mail.gmail.com>	<E99E41EB33084B5B899C7EED9DE607E9@ad.redback.com>	<3c3e3fca0901021334j22d17e54iec4bbf41b6c00480@mail.gmail.com>	<BCFF32A1356842BF839C7DF7D059F15F@ad.redback.com>	<3c3e3fca0901031320o1253fcd3s3b6597aef77fba33@mail.gmail.com>	<A071B6FF07CD4B708EC6CA2B9938096D@ad.redback.com>
	<3c3e3fca0901031720w602d931ev42707b169f51fba9@mail.gmail.com>
In-Reply-To: <3c3e3fca0901031720w602d931ev42707b169f51fba9@mail.gmail.com>
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On 2009-01-04 14:20, William Herrin wrote:
...
> 3. RIRs make painful, real-world-hurtful decisions based on the
> credence they lend the warning of BGP's impending failure. If the end
> of the world is no longer nigh, we have a moral responsibility to let
> them know.

The warning is a bit more subtle than that. It's more like (and I write
with no authority whatever):

If the DFZ growth curve reverts to the pattern it showed in the first
months of 1994, or in late 2000, or sustains the pattern it seems to have
shown since about mid-2006, it's liable to oustrip the increase in
performance that's possible by upgrading core routers. To prevent this,
continued damping of the growth in announced prefixes is essential.
RIR policy is the only damping mechanism proven to work.

    Brian
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sat Jan  3 21:49:03 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AD2233A6A29;
	Sat,  3 Jan 2009 21:49:03 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2A69C3A6A29
	for <rrg@core3.amsl.com>; Sat,  3 Jan 2009 21:49:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.544
X-Spam-Level: 
X-Spam-Status: No, score=-2.544 tagged_above=-999 required=5 tests=[AWL=0.055, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 2DKNK8KRIo0M for <rrg@core3.amsl.com>;
	Sat,  3 Jan 2009 21:49:01 -0800 (PST)
Received: from QMTA09.emeryville.ca.mail.comcast.net
	(qmta09.emeryville.ca.mail.comcast.net [76.96.30.96])
	by core3.amsl.com (Postfix) with ESMTP id 3B0D43A685B
	for <rrg@irtf.org>; Sat,  3 Jan 2009 21:49:01 -0800 (PST)
Received: from OMTA07.emeryville.ca.mail.comcast.net ([76.96.30.59])
	by QMTA09.emeryville.ca.mail.comcast.net with comcast
	id zC8b1a00m1GXsucA9HonCz; Sun, 04 Jan 2009 05:48:47 +0000
Received: from TONYLTM9XP ([155.53.1.254])
	by OMTA07.emeryville.ca.mail.comcast.net with comcast
	id zHob1a0075Up7oj8THodU0; Sun, 04 Jan 2009 05:48:45 +0000
From: "Tony Li" <tony.li@tony.li>
To: "'William Herrin'" <bill@herrin.us>
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com>
	<87D9F0BA2807456A88B0427241A29F65@ad.redback.com>
	<3c3e3fca0901021219t2ab35dfsb2532e0c89be84af@mail.gmail.com>
	<E99E41EB33084B5B899C7EED9DE607E9@ad.redback.com>
	<3c3e3fca0901021334j22d17e54iec4bbf41b6c00480@mail.gmail.com>
	<BCFF32A1356842BF839C7DF7D059F15F@ad.redback.com>
	<3c3e3fca0901031320o1253fcd3s3b6597aef77fba33@mail.gmail.com>
	<A071B6FF07CD4B708EC6CA2B9938096D@ad.redback.com>
	<3c3e3fca0901031720w602d931ev42707b169f51fba9@mail.gmail.com>
Date: Sat, 3 Jan 2009 21:48:21 -0800
Message-ID: <2BD330FB290F484F80D5910F18316328@ad.redback.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
In-Reply-To: <3c3e3fca0901031720w602d931ev42707b169f51fba9@mail.gmail.com>
Thread-Index: AcluCqvu2ickgtAgSPufbgABiISi8QAJE4TA
Cc: 'RRG' <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

 
Bill,

|The history of the computing industry is one of regularly encountered
|one-time advances. Moore's Law isn't built on the back of purely
|evolutionary improvement.


True, but one time advances from the networking industry catching up to the
rest of computing are all expended.  It now tracks it quite well, albeit
with some lag due to the ASIC houses trailing the process houses.  You do
NOT want router vendors going down the path of building their own fabs and
exploring process technology.  That's on the order of a $1B investment every
year.  ;-(


|I'm debating it because I'm tired of watching us bounce off the
|pinball bumpers. Resolving this issue impacts our work here in three
|very important ways:
|
|1. It affects whether as a group we reject strategy F, and if we
|don't, the language with which we present it.


That's easy.  

<co-chair>
As the RRG is chartered to deliver a routing architecture, strategy F (no
changes to the routing architecture) is out-of-scope.
</co-chair>


|2. Engineer's maxim: if it ain't broke, don't fix it. If failure does
|not loom on BGP's horizon, there is little justification for moving
|any disruptive strategy forward from research to engineering. The
|desirable output from our efforts is *very* different depending on
|whether or not BGP is failing.


Again, it's not BGP, it's the number of prefixes.  Any other protocol would
have to deal with the implications of a DFZ with a full set of prefixes as
well.  Thus, it's the architecture that must change.  And, once again, if
you don't believe that it needs to be fixed, I refer you to the problem
statement.


|However frightful the monsters under the bed may be, there is
|insufficient proof of their existence to justify giving your toddler a
|shotgun.


Hopefully there are better solutions than that regardless of motivation.  My
toddler has horrible aim.  ;-)

Tony

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sun Jan  4 05:54:27 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 81E5428C0E1;
	Sun,  4 Jan 2009 05:54:27 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D290F3A6951
	for <rrg@core3.amsl.com>; Sun,  4 Jan 2009 05:54:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.81
X-Spam-Level: 
X-Spam-Status: No, score=-2.81 tagged_above=-999 required=5 tests=[AWL=-1.349, 
	BAYES_00=-2.599, MANGLED_TOOL=2.3, RCVD_BAD_ID=2.837,
	RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id oR04-ZKBDu2r for <rrg@core3.amsl.com>;
	Sun,  4 Jan 2009 05:54:26 -0800 (PST)
Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.176.133])
	by core3.amsl.com (Postfix) with ESMTP id 9ABCD3A69FB
	for <rrg@irtf.org>; Sun,  4 Jan 2009 05:54:25 -0800 (PST)
Received: from localhost (webcartero01.uc3m.es [163.117.136.131])by 
	smtp03.uc3m.es (Postfix) with ESMTP id 1DC0472B651;Sun,  4 Jan 2009 
	14:54:10 +0100 (CET)
Received: from 
	r190-132-74-108.dialup.mobile.ancel.net.uy(r190-132-74-108.dialup.mobile.an
	cel.net.uy [190.132.74.108]) bywebcartero01.uc3m.es (Horde MIME
	library) with HTTP; Sun, 04 Jan 200914:54:08 +0100
Message-ID: <20090104145408.q0i0wpgtck48kssg@webcartero01.uc3m.es>
Date: Sun, 04 Jan 2009 14:54:08 +0100
From: MARCELO BAGNULO BRAUN <marcelo@it.uc3m.es>
To: Robin Whittle <rw@firstpr.com.au>
References: <4959B44C.2030709@firstpr.com.au><885A118B-76C8-4E8D-91C0-7C5C69
	96784F@cs.colostate.edu><4959C284.4060805@firstpr.com.au><1230690036.5700.7
	.camel@localhost><3c3e3fca0812301907y2feb8904r410845562929a8ed@mail.gmail
	.com><1230720711.5901.25.camel@localhost><495EF3B1.1030408@firstpr.com.au>
	<20090103121825.co8r3bgpwkwwggk4@webcartero01.uc3m.es><495F770C.4070004@firstpr.com.au>
In-Reply-To: <495F770C.4070004@firstpr.com.au>
MIME-Version: 1.0
Content-Disposition: inline
User-Agent: Internet Messaging Program (IMP) H3 (4.0.4)
X-imss-version: 2.051
X-imss-result: Passed
X-imss-scanInfo: M:B L:E SM:2
X-imss-tmaseResult: TT:1 TS:-14.0263 TC:1F TRN:65 TV:5.5.1026(16380.007)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
Cc: rrg@irtf.org, Randall Atkinson <rja@extremenetworks.com>
Subject: Re: [rrg] Proposals which match rrgarchitectures.html pls
	checkthepage
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Robin Whittle <rw@firstpr.com.au> dijo:

> Short version:     I need help in deciding which existing proposals
>                   (including those not really discussed much in the
>                   RRG) - if any - fit Strategy B.
>
>                   Is ProxyShim6 a scalable routing proposal?  If so
>                   does it really fit Strategy B, or is a new
>                   classification needed?
>
> Hi Marcelo,
>
> Thanks very much for this:
>
>> Shim6 does not requires changes in the APIs nor in the applications.
>> So under the definition included in the page, SHIM6 is not a strategy B
>> proposal.. Second, i certainly don't agree with the statement that shim6
>> does not provides multihoming.
>
> OK - I agree.  Perhaps the objections to Shim6 in terms of it being a
> scalable routing solution, in addition to it not being helpful for
> IPv4, include:
>
>  1 - It is host-based rather than router based.  (Questions of
>      where it is implemented and where it is controlled and
>      monitored from.)
>

I don't see this as a problem, but i guess there has already been 
enough debeate about this...

>  2 - It provides no portability - networks still need to renumber
>      when choosing a new ISP.  Renumbering is still disruptive
>      and expensive, including due to the appearance of IP addresses
>      in various places inside and outside the network which are not
>      amenable to secure automatic changes.
>

Shim6 supports PI identfiiers and uses PA locators, as i guess any 
other ID/loc solution that aims to deal with the routing system 
scalability
The PA locators are visible in the end nodes in end host based shim6 
and are visible in the proxy in the proxy shim6, whcih would reduce 
ever further the renumbering burden.

>  3 - Problems with maintaining ACLs in other networks for hosts
>      using SHIM6.
>

I don't understand this one

>  4 - Need for both hosts to support Shim6, when it is still being
>      developed and is not widely deployed.
>

I guess most of the solutions requires that some device near the other 
end supports the new protocol. The support in the other end in shim6 
can be in the end host itself or in the proxy shim6 box located in the 
target network, or in the target ISP

>
>> In addition, i think ProxyShim6 is likely to fit in a strategy B proposal.
>
> Ahh, I see that your I-D:
>
>  http://tools.ietf.org/html/draft-bagnulo-pshim6-02
>
> includes a list of problems with Shim6 which mentions points 1 and 2
> above.
>
> A quick scan of the I-D makes me think that it doesn't match Bill's
> text:
>
>   "GUID to LOC maps are pushed from the host towards a distributed
>    registry as they change. Hosts request and temporarily cache
>    individual mappings from the registry as needed."?
>
> Are you suggesting that ProxyShim6 is, or is an important part of, a
> solution to the IPv6 routing scaling problem?
>

PA addressing is a solution fo rthe routing scalability problem
Shim6 or proxy shim6 are means to fix what the usage of PA addressing breaks

> If so, then I suggest it would be good to write up a summary and
> analysis document and add a link to it from the RRG wiki.  (See:
> http://psg.com/lists/rrg/2007/msg00908.html .)  Also, does it really
> fit Strategy B or should Bill make a new strategy to match it?
>

mmm, my goal here is just to clarify what i think are misunderstandings 
about shim6
I am certainly not trying to push shim6 nor proxy shim6 here.

Regards, marcelo

>
>> Finally, there are tons of geo aggregation proposals, since Deering's
>> metro addressing, IXP based addressing, Iljitsch geo addressing.
>
> I have updated the page from version 00 to 01.  The start of the page
> tells how to see the older versions.  At the end of the page is a
> Loose Ends and Discussion section.
>
> Here are the changes:
>
> Deleted this mention of SHIM6 from Strategy B and retained its
> mention in Strategy G.
>
> Added to the Loose Ends and Discussion section some queries about
> whether ILNP or HIP really match Bill's description.  For instance,
> do they involve a mapping system, to match: "GUID to LOC maps are
> pushed from the host towards a distributed registry as they change.
> Hosts request and temporarily cache individual mappings from the
> registry as needed."?
>
> Linked to this message regarding the status of ProxyShim6.
>
>  - Robin
>



-- 
----
MARCELO BAGNULO BRAUN
WebCartero
Universidad Carlos III de Madrid

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sun Jan  4 08:34:27 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C22B23A6A8E;
	Sun,  4 Jan 2009 08:34:26 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2719C3A6A8E
	for <rrg@core3.amsl.com>; Sun,  4 Jan 2009 08:34:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.262
X-Spam-Level: 
X-Spam-Status: No, score=0.262 tagged_above=-999 required=5 tests=[AWL=-1.136, 
	BAYES_50=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Zuvy2J9zA2ND for <rrg@core3.amsl.com>;
	Sun,  4 Jan 2009 08:34:25 -0800 (PST)
Received: from imo-d03.mx.aol.com (imo-d03.mx.aol.com [205.188.157.35])
	by core3.amsl.com (Postfix) with ESMTP id F06683A6A8C
	for <rrg@irtf.org>; Sun,  4 Jan 2009 08:34:24 -0800 (PST)
Received: from HeinerHummel@aol.com
	by imo-d03.mx.aol.com  (mail_out_v39.1.) id n.cc4.453cf32f (14502);
	Sun, 4 Jan 2009 11:34:02 -0500 (EST)
From: HeinerHummel@aol.com
Message-ID: <cc4.453cf32f.36923efa@aol.com>
Date: Sun, 4 Jan 2009 11:34:02 EST
To: rw@firstpr.com.au, rrg@irtf.org
MIME-Version: 1.0
X-Mailer: 9.0 SE for Windows sub 5021
Subject: Re: [rrg] Critique of Compact Routing
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0719444841=="
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org


--===============0719444841==
Content-Type: multipart/alternative; boundary="-----------------------------1231086842"


-------------------------------1231086842
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

=20
Even worse:
In =A7 4.4 of this document the authors postolate that there is a   ~15 time=
s=20
path lengths increase due to hierarchical routing (obviously I mixed  up thi=
s=20
number with (only!) stretch-3 mentioned at some other lines).
Either the research work is not trust-worthy or the authors had a very very=20=
=20
bad hierarchical routing model in mind.=20
Again: the conclusion that  any hierarchical routing model has such a  bad=20
stretch behavior - note:
fifteen times the shortest path length !  - tells me that the authors  have=20
never heard of Kurt Mehlhorn's algorithm, published in 1988,  including his=20=
=20
proof that the distilled hierarchical mesh contains all  shortest path trees=
=20
that interconnect the hierarchical nodes.
=20
Heiner
=20
In einer eMail vom 29.12.2008 23:56:13 Westeurop=E4ische Normalzeit schreibt=
 =20
rw@firstpr.com.au:

In an  earlier message 000565 I mentioned a paper:

On Compact  Routing for the Internet
Dmitri Krioukov, kc claffy, Kevin  Fall, Arthur Brady
ACM SIGCOMM CCR, v.37, n.3, p.41-52,  2007

This is available at:

http://arxiv.org/abs/0708.2309

-  Robin
_______________________________________________
rrg mailing  list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg





-------------------------------1231086842
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3DISO-8859-1">
<META content=3D"MSHTML 6.00.6000.16788" name=3DGENERATOR></HEAD>
<BODY id=3Drole_body style=3D"FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY:=20=
Arial"=20
bottomMargin=3D7 leftMargin=3D7 topMargin=3D7 rightMargin=3D7><FONT id=3Drol=
e_document=20
face=3DArial color=3D#000000 size=3D2>
<DIV>
<DIV>Even worse:</DIV>
<DIV>In =A7&nbsp;4.4 of this document the authors postolate that there is a&=
nbsp;=20
~15 times path lengths increase due to hierarchical routing (obviously I mix=
ed=20
up this number with (only!) stretch-3 mentioned at some other lines).</DIV>
<DIV>Either the research work is not trust-worthy or the authors had a very=20=
very=20
bad hierarchical routing model in mind. </DIV>
<DIV>Again: the conclusion that&nbsp; any hierarchical routing model has suc=
h a=20
bad stretch behavior -&nbsp;note:</DIV>
<DIV>fifteen times the shortest path length !&nbsp; - tells me that the auth=
ors=20
have never heard of Kurt Mehlhorn's algorithm, published in 1988,=20
including&nbsp;his&nbsp; proof that the distilled hierarchical mesh contains=
 all=20
shortest path trees that interconnect the hierarchical nodes.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Heiner</DIV>
<DIV>&nbsp;</DIV>
<DIV>In einer eMail vom 29.12.2008 23:56:13 Westeurop=E4ische Normalzeit sch=
reibt=20
rw@firstpr.com.au:</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid"><=
FONT=20
  style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000 size=
=3D2>In an=20
  earlier message 000565 I mentioned a paper:<BR><BR>&nbsp; &nbsp; On Compac=
t=20
  Routing for the Internet<BR>&nbsp; &nbsp; Dmitri Krioukov, kc claffy, Kevi=
n=20
  Fall, Arthur Brady<BR>&nbsp; &nbsp; ACM SIGCOMM CCR, v.37, n.3, p.41-52,=20
  2007<BR><BR>This is available at:<BR><BR>&nbsp; &nbsp;=20
  http://arxiv.org/abs/0708.2309<BR><BR>&nbsp; -=20
  Robin<BR>_______________________________________________<BR>rrg mailing=20
  list<BR>rrg@irtf.org<BR>https://www.irtf.org/mailman/listinfo/rrg<BR></FON=
T></BLOCKQUOTE></DIV>
<DIV></DIV>
<DIV>&nbsp;</DIV></FONT></BODY></HTML>

-------------------------------1231086842--

--===============0719444841==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg

--===============0719444841==--


From rrg-bounces@irtf.org  Sun Jan  4 08:37:41 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AD1FF3A6A7E;
	Sun,  4 Jan 2009 08:37:41 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 89E783A6A7E
	for <rrg@core3.amsl.com>; Sun,  4 Jan 2009 08:37:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.366
X-Spam-Level: 
X-Spam-Status: No, score=0.366 tagged_above=-999 required=5 tests=[AWL=-1.032, 
	BAYES_50=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id npoS+FBfC+5n for <rrg@core3.amsl.com>;
	Sun,  4 Jan 2009 08:37:39 -0800 (PST)
Received: from imo-d23.mx.aol.com (imo-d23.mx.aol.com [205.188.139.137])
	by core3.amsl.com (Postfix) with ESMTP id B6D973A67E9
	for <rrg@irtf.org>; Sun,  4 Jan 2009 08:37:39 -0800 (PST)
Received: from HeinerHummel@aol.com
	by imo-d23.mx.aol.com  (mail_out_v39.1.) id n.cf7.49842725 (14502);
	Sun, 4 Jan 2009 11:37:19 -0500 (EST)
From: HeinerHummel@aol.com
Message-ID: <cf7.49842725.36923fbf@aol.com>
Date: Sun, 4 Jan 2009 11:37:19 EST
To: rw@firstpr.com.au, rrg@irtf.org
MIME-Version: 1.0
X-Mailer: 9.0 SE for Windows sub 5021
Subject: Re: [rrg] 10M ... 100M end-user networks
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0750080143=="
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org


--===============0750080143==
Content-Type: multipart/alternative; boundary="-----------------------------1231087039"


-------------------------------1231087039
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

=20
In einer eMail vom 04.01.2009 03:26:38 Westeurop=E4ische Normalzeit schreibt=
 =20
rw@firstpr.com.au:

Short  version:    The current number and rate of growth in the  number
of  multihomed end-user networks is not our
primary concern.

Our aim, as best I understand it, is  to design
an  architectural enhancement for the Internet
by which the much higher numbers of  end-user
networks which want/need multihoming, TE and
address portability can have these in a  manner
which  is technically and economically sustainable
for ISPs and for the end-user  networks
themselves.

A system which would work nicely with 10M
such end-user networks would be  good.  One
which scales well to 100M or 1B would be  better.



A system which doesn't care how many end-users are attached would even  be=20
better :-)
Heiner

-------------------------------1231087039
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3DISO-8859-1">
<META content=3D"MSHTML 6.00.6000.16788" name=3DGENERATOR></HEAD>
<BODY id=3Drole_body style=3D"FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY:=20=
Arial"=20
bottomMargin=3D7 leftMargin=3D7 topMargin=3D7 rightMargin=3D7><FONT id=3Drol=
e_document=20
face=3DArial color=3D#000000 size=3D2>
<DIV>
<DIV>In einer eMail vom 04.01.2009 03:26:38 Westeurop=E4ische Normalzeit sch=
reibt=20
rw@firstpr.com.au:</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid"><=
FONT=20
  style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000 size=
=3D2>Short=20
  version:&nbsp; &nbsp; The current number and rate of growth in the=20
  number<BR>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; o=
f=20
  multihomed end-user networks is not our<BR>&nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp;=20
  &nbsp; &nbsp; &nbsp; &nbsp; primary concern.<BR><BR>&nbsp; &nbsp; &nbsp;=20
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Our aim, as best I understand it=
, is=20
  to design<BR>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
; an=20
  architectural enhancement for the Internet<BR>&nbsp; &nbsp; &nbsp; &nbsp;=20
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; by which the much higher numbers of=20
  end-user<BR>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
=20
  networks which want/need multihoming, TE and<BR>&nbsp; &nbsp; &nbsp; &nbsp=
;=20
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; address portability can have these in a=
=20
  manner<BR>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; w=
hich=20
  is technically and economically sustainable<BR>&nbsp; &nbsp; &nbsp; &nbsp;=
=20
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; for ISPs and for the end-user=20
  networks<BR>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
=20
  themselves.<BR><BR>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
=20
  &nbsp; A system which would work nicely with 10M<BR>&nbsp; &nbsp; &nbsp;=20
  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; such end-user networks would be=20
  good.&nbsp; One<BR>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
=20
  &nbsp; which scales well to 100M or 1B would be=20
better.<BR></FONT></BLOCKQUOTE></DIV>
<DIV></DIV>
<DIV>A system which doesn't care how many end-users are attached&nbsp;would=20=
even=20
be better :-)</DIV>
<DIV>Heiner</DIV></FONT></BODY></HTML>

-------------------------------1231087039--

--===============0750080143==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg

--===============0750080143==--


From rrg-bounces@irtf.org  Sun Jan  4 12:08:40 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7BD113A6972;
	Sun,  4 Jan 2009 12:08:40 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 73AF33A689C
	for <rrg@core3.amsl.com>; Sun,  4 Jan 2009 12:08:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.478
X-Spam-Level: 
X-Spam-Status: No, score=-2.478 tagged_above=-999 required=5 tests=[AWL=0.121, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id fth+7qD-DRds for <rrg@core3.amsl.com>;
	Sun,  4 Jan 2009 12:08:38 -0800 (PST)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.229])
	by core3.amsl.com (Postfix) with ESMTP id AC7AF3A6A0F
	for <rrg@irtf.org>; Sun,  4 Jan 2009 12:08:38 -0800 (PST)
Received: by rv-out-0506.google.com with SMTP id f6so8780104rvb.7
	for <rrg@irtf.org>; Sun, 04 Jan 2009 12:08:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from
	:organization:user-agent:mime-version:to:cc:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=SCKngCjRRWzWj8zHsfHAdXmTxudh4o8nvGphs36sEGA=;
	b=U0U2RBAEoFVWmt4DSfH2YiLUq9RFcdcYg43+Xo44W59o0HbiKN+wVUeODw/OV5Fc3C
	RiQNqf0kEQycwOPyOr4DJMqb/lDl0LnzrBq9HdKd2CaPcZBcP2cbXJf7s4yY3Ue1XdVr
	dT87XHGT6PpUybyxXYXO7iOdLpPLa6u2rqXBM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	b=gyYxdih77/g67lFzP8SU86a2TTbcaZ6CH+AMY12Fk/Yg0V9gIVo4V1NZjXaf5eVF1D
	iJk9xRNZrZNnWPcpGnUnmg0volhZBBu2wMRKxfR7Nq2JygvPDJ+nM4ctIFHhE/OcbJyI
	B1ADDqt29Fk7Sscu4kjz0uYtCWru8Zx0vXoqU=
Received: by 10.140.139.4 with SMTP id m4mr5007337rvd.50.1231099704918;
	Sun, 04 Jan 2009 12:08:24 -0800 (PST)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz
	[130.216.38.124])
	by mx.google.com with ESMTPS id b8sm60188801rvf.3.2009.01.04.12.08.23
	(version=SSLv3 cipher=RC4-MD5); Sun, 04 Jan 2009 12:08:24 -0800 (PST)
Message-ID: <49611727.5000806@gmail.com>
Date: Mon, 05 Jan 2009 09:08:07 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: MARCELO BAGNULO BRAUN <marcelo@it.uc3m.es>
References: <4959B44C.2030709@firstpr.com.au><885A118B-76C8-4E8D-91C0-7C5C69	96784F@cs.colostate.edu><4959C284.4060805@firstpr.com.au><1230690036.5700.7	.camel@localhost><3c3e3fca0812301907y2feb8904r410845562929a8ed@mail.gmail	.com><1230720711.5901.25.camel@localhost><495EF3B1.1030408@firstpr.com.au>	<20090103121825.co8r3bgpwkwwggk4@webcartero01.uc3m.es><495F770C.4070004@firstpr.com.au>
	<20090104145408.q0i0wpgtck48kssg@webcartero01.uc3m.es>
In-Reply-To: <20090104145408.q0i0wpgtck48kssg@webcartero01.uc3m.es>
Cc: rrg@irtf.org
Subject: [rrg] Remote ACLs [Proposals which match rrg architectures.html pls
 check the page]
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On 2009-01-05 02:54, MARCELO BAGNULO BRAUN wrote:

> 
>>  3 - Problems with maintaining ACLs in other networks for hosts
>>      using SHIM6.
>>
> 
> I don't understand this one 

Isn't this in fact a (perceived) problem with the multi-prefix
model? If an endpoint has multiple locators, then any site that
puts one of those locators in an ACL needs to put all of them
in the ACL. So if you want to put somehost.example.net in an
ACL, you need to look up all its A/AAAA records and put all the
results in the ACL. I don't think this has anything to do with
shim6.

   Brian
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sun Jan  4 12:21:13 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A8A753A689C;
	Sun,  4 Jan 2009 12:21:13 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0FA273A689C
	for <rrg@core3.amsl.com>; Sun,  4 Jan 2009 12:21:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.591
X-Spam-Level: 
X-Spam-Status: No, score=-6.591 tagged_above=-999 required=5 tests=[AWL=0.007, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id N2P3r0r914Ke for <rrg@core3.amsl.com>;
	Sun,  4 Jan 2009 12:21:11 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122])
	by core3.amsl.com (Postfix) with ESMTP id 2B7093A6801
	for <rrg@irtf.org>; Sun,  4 Jan 2009 12:21:11 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178)
	id 946896BE56A; Sun,  4 Jan 2009 15:20:55 -0500 (EST)
To: rrg@irtf.org
Message-Id: <20090104202055.946896BE56A@mercury.lcs.mit.edu>
Date: Sun,  4 Jan 2009 15:20:55 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [rrg] Remote ACLs [Proposals which match rrg architectures.html
	pls check the page]
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

    > From: Brian E Carpenter <brian.e.carpenter@gmail.com>

    > Isn't this in fact a (perceived) problem with the multi-prefix model?
    > If an endpoint has multiple locators, then any site that puts one of
    > those locators in an ACL needs to put all of them in the ACL.

Why are people putting locators in ACLs anyway?

(Note: This is not the same thing as the question 'why is the hardware
looking at locators to implement ACLs?'. Looking at locators might be a fine
engineering choice for the _implementation_ of ACLs.)

	Noel
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sun Jan  4 12:39:49 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A8D4B3A689C;
	Sun,  4 Jan 2009 12:39:49 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0401D3A689C
	for <rrg@core3.amsl.com>; Sun,  4 Jan 2009 12:39:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.48
X-Spam-Level: 
X-Spam-Status: No, score=-2.48 tagged_above=-999 required=5 tests=[AWL=0.119, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id BTFKDT9WIv3D for <rrg@core3.amsl.com>;
	Sun,  4 Jan 2009 12:39:47 -0800 (PST)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.170])
	by core3.amsl.com (Postfix) with ESMTP id 0354C3A6813
	for <rrg@irtf.org>; Sun,  4 Jan 2009 12:39:46 -0800 (PST)
Received: by wf-out-1314.google.com with SMTP id 24so9494945wfg.7
	for <rrg@irtf.org>; Sun, 04 Jan 2009 12:39:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from
	:organization:user-agent:mime-version:to:cc:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=bldMDov8NbUESfusEBcMYr6iCG8GmuWF1b3xY45VfH0=;
	b=Mz3+0QMSRsxC/m4elf7IntkeXX5nthxyKG4w69B49SakOW6mQFHOOE2hJQkqZxaaBE
	P2lEAi9JdomejnsnylfiEl7B5isQhWnc3Qrg5ENLCkomRznCWtzuhvqWSwL4qP9xGWD4
	huDqb8qsOl08rpBIUUC8rnJ85JJk0yQJHHVX0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	b=ibfM+lyGUTb02aysMblNFcBBCO9AAvvXPiFDPk9P3CfBcfiFMKFXwTXkBGojIMGe8h
	9paxJj4bW02jpqCAq257uHSpcasOp3os/2KXnJmOPjB0EteoQH4scVzAEoGriBnqKOXL
	PKwjBlOD8ZD++qUn6XM9TAJKiSFbMvBb0kqhY=
Received: by 10.142.177.5 with SMTP id z5mr8348809wfe.40.1231101574679;
	Sun, 04 Jan 2009 12:39:34 -0800 (PST)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz
	[130.216.38.124])
	by mx.google.com with ESMTPS id 24sm35893450wfc.2.2009.01.04.12.39.33
	(version=SSLv3 cipher=RC4-MD5); Sun, 04 Jan 2009 12:39:34 -0800 (PST)
Message-ID: <49611E83.8050301@gmail.com>
Date: Mon, 05 Jan 2009 09:39:31 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Robin Whittle <rw@firstpr.com.au>
References: <495F0BAA.2040303@firstpr.com.au>
In-Reply-To: <495F0BAA.2040303@firstpr.com.au>
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org


On 2009-01-03 19:54, Robin Whittle wrote:
> Short version:     We should reject Strategy B.  

For the record, I disagree, for reasons given earlier.
However, that doesn't mean we shouldn't recommend that a
strategy A approach be brought to fruition. There's no
reason why this group is limited to a binary choice.

<snip>

> 
>   Most of the Strategy A proposals (LISP-NERD, LISP-ALT, APT, Ivip
>   and TRRP) are intended to work with IPv4.
> 
>   Strategy B proposals cannot help with the IPv4 routing scaling
>   problem because there is not enough space for each multihomed
>   end-user  network to be given a prefix by each of its two or more
>   ISPs.

Correct. And is it unthinkable that the fix for IPv4 (which is running out
of addresses) should be different from the architecture for IPv6 (which
isn't)? On the contrary, it would be very strange if the solution was the
same.

<snip>

>    Strategy B:  There are no properly documented proposals.

> 
>                 ILNP may be a Strategy B approach but it is not
>                 properly documented as a scalable routing solution.
>                 There is no Summary and Analysis in the RRG wiki.

It's unclear to me that ILNP belongs in B since it has characteristics
of A as well. Whether it's jumped through the hoops of the wiki strikes
me as uninteresting; it seems to be well documented.

> 
>                 HIP has been mentioned, but no-one seems to be
>                 proposing it as a scalable routing solution.

I think Pekka observed that this wasn't even a goal. (My quick answer
is that it only becomes a routing solution if it solves the same
mapping problem that strategy A generates.)

Shim6 has also been mentioned, as a mitigation of some the issues
with the multiprefix PA model. That is already chartered IETF work
with full documentation.


> Every possible Strategy B approach would be vastly harder to have
> adopted by the majority of end-user networks which want multihoming,
> TE and portability (or its functional equivalent) than any Strategy A
> approach, for at least two reasons:
> 
>   1 - Strategy B solutions require most or all current Internet users
>       to adopt IPv6 - and furthermore IPv6 with a modified host
>       stack, API and applications.

The first half of this is increasingly likely to happen anyway. It isn't
certain that the API and apps have to be touched; rolling out new stacks
over five to ten years really isn't a valid objection.

But I fully agree: strategy B == IPv6.

> 
>   2 - Strategy B solutions provides benefits to adoptors only when
>       the other host in a session (stack and relevant applications)
>       has been upgraded too.  So until almost all networks and their
>       hosts adopted it, the scheme could only provide multihoming for
>       a fraction of communication sessions.

This is true. The question is whether this (piecemeal incentives, highly
distributed low costs) is really less effective than the incentives to pay
the highly concentrated per-network costs of strategy A.

> 
> Also, I argue that any approach which involves pushing
> responsibilities and management traffic to all hosts (all potential
> Strategy B approaches) is fundamentally flawed:
> 
>   http://www.irtf.org/pipermail/rrg/2008-November/000233.html

Highly distributed = scaleable. And in any cases, hosts have always
been responsible for traffic management (that's called TCP)
and approaches like SCTP and the proposed multipath TCP extend that.
So I don't think we should condemn this in the abstract.

> 
> 
> I find it impossible to imagine how a Strategy B solution could
> succeed if we fail to solve the problem via the best one or more
> Strategy A solutions being properly developed and offered for adoption.
> 
> RRG rejection of Strategy B solutions is not to suggest that people
> shouldn't work on such schemes.  Just that we have no confidence that
> any such scheme could turn out to be technically better and/or easier
> to have widely adopted than a well developed version of the best of
> the Strategy A schemes.


> 
> Of course, if the best efforts with Strategy A schemes fails, then
> everything would be up for reconsideration.  However, that is a
> potential scenario in the post-2020 future.  Then, any Strategy B
> solution would still involve much higher barriers to development and
> adoption than any Strategy A solution.

Exactly. Which is why my preference is to recommend development work
on strategy A and continued R&D on strategy B; I'd be very concerned
if we shrugged our shoulders and dropped it for 12 years.

    Brian
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sun Jan  4 12:41:06 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7F7AD3A68B4;
	Sun,  4 Jan 2009 12:41:06 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F20553A6813
	for <rrg@core3.amsl.com>; Sun,  4 Jan 2009 12:41:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.592
X-Spam-Level: 
X-Spam-Status: No, score=-6.592 tagged_above=-999 required=5 tests=[AWL=0.007, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 4E8QLc3PSC4t for <rrg@core3.amsl.com>;
	Sun,  4 Jan 2009 12:41:05 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122])
	by core3.amsl.com (Postfix) with ESMTP id 2B6633A68B4
	for <rrg@irtf.org>; Sun,  4 Jan 2009 12:41:05 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178)
	id 5273B6BE56A; Sun,  4 Jan 2009 15:40:52 -0500 (EST)
To: rrg@irtf.org
Message-Id: <20090104204052.5273B6BE56A@mercury.lcs.mit.edu>
Date: Sun,  4 Jan 2009 15:40:52 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [rrg] Remote ACLs [Proposals which match rrg architectures.html
	pls check the page]
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

    > From: Brian E Carpenter <brian.e.carpenter@gmail.com>

    > Isn't this in fact a (perceived) problem with the multi-prefix model?
    > If an endpoint has multiple locators, then any site that puts one of
    > those locators in an ACL needs to put all of them in the ACL.

To expand a tiny bit on that 'Why are people putting locators in ACLs
anyway?' (since what I meant might not have been obvious) ....

It would seem to me that this would get us right back in the soup, in that a
change local to a site (e.g. changing ISPs) would, if ACLs were given in
terms of locators, be basically 'non-visible' to sites elsewhere in the
network which had configuration(s) which only included locator information
about that site.`

Put another way, unless some 'out of band' communication happens, there's no
way for e.g. a filter box Cf at client site C to know that the server site S
has moved from locator S1 to new locator S2. Since the highest level
semantics in which Cf has information about S is 'S1', unless there was some
sort of 'forwarding service' (e.g. an ICMP redirect from S1 to S2, sent back
to C - and I shudder to think about how to secure that so that it doesn't
become an attack vector), when S moves to S2, then Cf is just left entirely
in the dark.

On the other hand, if Cf knows of S at some higher semantic level, then it's
possible to imagine that Cf might be able to discover without human
intervention that S had moved from S1 to S2.

	Noel
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sun Jan  4 13:17:02 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1384528B56A;
	Sun,  4 Jan 2009 13:17:02 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A12653A6A91
	for <rrg@core3.amsl.com>; Sun,  4 Jan 2009 13:17:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.485
X-Spam-Level: 
X-Spam-Status: No, score=-2.485 tagged_above=-999 required=5 tests=[AWL=0.114, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id t5ZMkTj3F5Ff for <rrg@core3.amsl.com>;
	Sun,  4 Jan 2009 13:17:00 -0800 (PST)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.228])
	by core3.amsl.com (Postfix) with ESMTP id D86E33A6A8C
	for <rrg@irtf.org>; Sun,  4 Jan 2009 13:17:00 -0800 (PST)
Received: by rv-out-0506.google.com with SMTP id f6so8798331rvb.7
	for <rrg@irtf.org>; Sun, 04 Jan 2009 13:16:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:reply-to
	:organization:user-agent:mime-version:to:cc:subject:content-type
	:content-transfer-encoding;
	bh=CmdtTB6rWcrm5/kEhQ626hi6bffE5jY4A2Aj7WFfx1c=;
	b=Z50noNIiblgf8/jaAC6J9LIl+Xx1WzUPeTiH57qe61RVoOfhFTeFnYpG9TUtDxOX/e
	A+Tjtz1oztYTBbOLCYToRCykQWRTgDQgB8Qtir26Riq3ZS5wiJ0M98eSxiis9aqXiPXS
	EIOfVb8IXQ+vazEuxdrCjHIse+9mAWlH378t8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:reply-to:organization:user-agent:mime-version
	:to:cc:subject:content-type:content-transfer-encoding;
	b=qyqP6TMPypBUbCweLlMPPEIIO9pzIc5KjuI+yAFK8H8L882NulBccbX7MzU9NHfzeL
	cGjESEw6LNGLfTj+SJRv6ITwRSGoi4IwLlmM2e6zJnNiPuMU1RUPqKjdG+7DySO4Mysj
	Ii09RxVexW+prrSj//GtDpXTGxAhWuLn4VPII=
Received: by 10.141.142.15 with SMTP id u15mr10028608rvn.16.1231103807431;
	Sun, 04 Jan 2009 13:16:47 -0800 (PST)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz
	[130.216.38.124])
	by mx.google.com with ESMTPS id k2sm50254269rvb.6.2009.01.04.13.16.46
	(version=SSLv3 cipher=RC4-MD5); Sun, 04 Jan 2009 13:16:47 -0800 (PST)
Message-ID: <4961273D.6090209@gmail.com>
Date: Mon, 05 Jan 2009 10:16:45 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: RRG <rrg@irtf.org>
Cc: RJ Atkinson <rja@extremenetworks.com>
Subject: [rrg] Renumbering needs work
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ops-area@ietf.org
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

A draft on this topic has been updated:
http://www.ietf.org/internet-drafts/draft-carpenter-renum-needs-work-01.txt

Comments and discussion are invited on the OPS Area list,
ops-area@ietf.org

  Brian Carpenter
  Ran Atkinson
  Hannu Flinck

P.S. Apologies if you receive multiple copies, but that seems
preferable to cross-posting to multiple lists.


_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sun Jan  4 13:41:57 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A08413A6861;
	Sun,  4 Jan 2009 13:41:57 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DD2043A6861
	for <rrg@core3.amsl.com>; Sun,  4 Jan 2009 13:41:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id DrHhDLxVnerO for <rrg@core3.amsl.com>;
	Sun,  4 Jan 2009 13:41:56 -0800 (PST)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133])
	by core3.amsl.com (Postfix) with ESMTP id 137553A682B
	for <rrg@irtf.org>; Sun,  4 Jan 2009 13:41:55 -0800 (PST)
Received: by dog.tcb.net (Postfix, from userid 0)
	id 93FFF2684EA; Sun,  4 Jan 2009 14:41:43 -0700 (MST)
Received: from [192.168.0.100] (97-122-99-176.hlrn.qwest.net [97.122.99.176])
	(authenticated-user danny) (TLSv1/SSLv3 AES128-SHA 128/128)
	by dog.tcb.net with SMTP; for rrg@irtf.org;
	Sun, 04 Jan 2009 14:41:43 -0700 (MST) (envelope-from danny@arbor.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=97.122.99.176;
	client-port=56055; syn-fingerprint=65535:55:1:64:M1316,N,W3,N,N,T,S;
	data-bytes=0
Message-Id: <D581207B-4A49-4F86-B3B2-9F44B395F209@arbor.net>
From: Danny McPherson <danny@arbor.net>
To: RRG <rrg@irtf.org>
In-Reply-To: <E99B4060-F44C-4FF0-9455-B2CDBADF5A7D@arbor.net>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Sun, 4 Jan 2009 14:41:41 -0700
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com>
	<87D9F0BA2807456A88B0427241A29F65@ad.redback.com>
	<3c3e3fca0901021219t2ab35dfsb2532e0c89be84af@mail.gmail.com>
	<E99E41EB33084B5B899C7EED9DE607E9@ad.redback.com>
	<3c3e3fca0901021334j22d17e54iec4bbf41b6c00480@mail.gmail.com>
	<BCFF32A1356842BF839C7DF7D059F15F@ad.redback.com>
	<3c3e3fca0901031320o1253fcd3s3b6597aef77fba33@mail.gmail.com>
	<A071B6FF07CD4B708EC6CA2B9938096D@ad.redback.com>
	<3c3e3fca0901031720w602d931ev42707b169f51fba9@mail.gmail.com>
	<2BD330FB290F484F80D5910F18316328@ad.redback.com>
	<E99B4060-F44C-4FF0-9455-B2CDBADF5A7D@arbor.net>
X-Mailer: Apple Mail (2.930.3)
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org


On Jan 3, 2009, at 10:48 PM, Tony Li wrote:

>
> Again, it's not BGP, it's the number of prefixes.  Any other  
> protocol would
> have to deal with the implications of a DFZ with a full set of  
> prefixes as
> well.  Thus, it's the architecture that must change.  And, once  
> again, if
> you don't believe that it needs to be fixed, I refer you to the  
> problem
> statement.

Yep, and again, not strictly the number of prefixes,
but the number of paths, especially when one focuses on
RIB size and churn and implications on FIB updates and
an eye on some future security - versus sole focus on
"DFZ FIB size".

Many networks today have FIB sizes < 500k, but BGP
table sizes on the order of 5M or more.  As the denseness
of inter-domain interconnection continues to increases,
the number of paths increases (more steeply than the
DFZ table size).  A multi-homed AS with a PI prefix
might mean 100 *unique* paths or more in a network only
3 AS hops away.  Each change in reachability for that
prefix means all those paths have to be withdraw.

Ohh, and in an ideal world, those 100 viable paths would
have to be authorized in some manner.  Today this would
be done with static prefix lists at each interconnect,
although the current number of paths and absence of a
formally verifiable source for who's authorized (e.g.,
SIDR) to advertise (much less "transit" a given prefix)
what prefixes means there is essentially no inter-domain
route advertisement security in today's Internet.

More path attributes also means less efficiency in things
like update packing that allow some scaling of today's
routing system.

It's not just DFZ size that's the concern here.

-danny

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sun Jan  4 13:59:01 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 342583A6A95;
	Sun,  4 Jan 2009 13:59:01 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3C3083A6A8E
	for <rrg@core3.amsl.com>; Sun,  4 Jan 2009 13:58:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.532
X-Spam-Level: 
X-Spam-Status: No, score=-6.532 tagged_above=-999 required=5 tests=[AWL=0.067, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id GfhweSl4UWYH for <rrg@core3.amsl.com>;
	Sun,  4 Jan 2009 13:58:58 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id 52BE33A6A8D
	for <rrg@irtf.org>; Sun,  4 Jan 2009 13:58:58 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.36,329,1228089600"; d="scan'208";a="124659951"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-1.cisco.com with ESMTP; 04 Jan 2009 21:58:38 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n04LwbM0001564; 
	Sun, 4 Jan 2009 13:58:37 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n04LwbLW021923;
	Sun, 4 Jan 2009 21:58:37 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 4 Jan 2009 13:58:37 -0800
Received: from moveme.cisco.com ([10.21.125.110]) by
	xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 4 Jan 2009 13:58:37 -0800
Message-Id: <1580F23C-BAB4-4586-98ED-9305AA89EF53@cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
In-Reply-To: <20090104202055.946896BE56A@mercury.lcs.mit.edu>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Sun, 4 Jan 2009 13:58:37 -0800
References: <20090104202055.946896BE56A@mercury.lcs.mit.edu>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 04 Jan 2009 21:58:37.0287 (UTC)
	FILETIME=[98786F70:01C96EB7]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=817; t=1231106317; x=1231970317;
	c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dino@cisco.com;
	z=From:=20Dino=20Farinacci=20<dino@cisco.com>
	|Subject:=20Re=3A=20[rrg]=20Remote=20ACLs=20[Proposals=20wh
	ich=20match=20rrg=20architectures.html=20pls=20check=20the=2
	0page] |Sender:=20;
	bh=ANsvZSESdXqJrA11blZryOmruwPv66HlwAUjWpnTgiU=;
	b=cEhDwwpriPNq2fvjQD4k0fjVdhPjjcyUNIJskdgvQD2sUkljiKFW9Yrl6v
	ofj5i4zfyrjJFBOHIqy60o8APK5+/SGNWFTdv1mlBmyJBPbg8XeTBmi6Zl6n
	MFvkv0kR9NjQxWcl/tK6jO6XPKZ1h8gUivx/FM4l5+snDMMqvn5AI=;
Authentication-Results: sj-dkim-1; header.From=dino@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: rrg@irtf.org
Subject: Re: [rrg] Remote ACLs [Proposals which match rrg architectures.html
	pls check the page]
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

The simple/short answer is because they are being used as IDs.

Dino

On Jan 4, 2009, at 12:20 PM, Noel Chiappa wrote:

>> From: Brian E Carpenter <brian.e.carpenter@gmail.com>
>
>> Isn't this in fact a (perceived) problem with the multi-prefix model?
>> If an endpoint has multiple locators, then any site that puts one of
>> those locators in an ACL needs to put all of them in the ACL.
>
> Why are people putting locators in ACLs anyway?
>
> (Note: This is not the same thing as the question 'why is the hardware
> looking at locators to implement ACLs?'. Looking at locators might  
> be a fine
> engineering choice for the _implementation_ of ACLs.)
>
> 	Noel
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> https://www.irtf.org/mailman/listinfo/rrg

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sun Jan  4 15:51:19 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0693E28C124;
	Sun,  4 Jan 2009 15:51:19 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EE3F028C124
	for <rrg@core3.amsl.com>; Sun,  4 Jan 2009 15:51:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.623
X-Spam-Level: 
X-Spam-Status: No, score=-1.623 tagged_above=-999 required=5
	tests=[AWL=-0.869, BAYES_05=-1.11, SARE_SUB_6CONS_WORD=0.356]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id EmsJvdMdMyf9 for <rrg@core3.amsl.com>;
	Sun,  4 Jan 2009 15:51:17 -0800 (PST)
Received: from QMTA08.emeryville.ca.mail.comcast.net
	(qmta08.emeryville.ca.mail.comcast.net [76.96.30.80])
	by core3.amsl.com (Postfix) with ESMTP id 6170628C122
	for <rrg@irtf.org>; Sun,  4 Jan 2009 15:51:16 -0800 (PST)
Received: from OMTA09.emeryville.ca.mail.comcast.net ([76.96.30.20])
	by QMTA08.emeryville.ca.mail.comcast.net with comcast
	id zaTm1a0040S2fkCA8br4qp; Sun, 04 Jan 2009 23:51:04 +0000
Received: from TONYLTM9XP ([155.53.1.254])
	by OMTA09.emeryville.ca.mail.comcast.net with comcast
	id zbqq1a0075Up7oj8VbqtgS; Sun, 04 Jan 2009 23:51:01 +0000
From: "Tony Li" <tony.li@tony.li>
To: "'Dino Farinacci'" <dino@cisco.com>,
	"'Noel Chiappa'" <jnc@mercury.lcs.mit.edu>
References: <20090104202055.946896BE56A@mercury.lcs.mit.edu>
	<1580F23C-BAB4-4586-98ED-9305AA89EF53@cisco.com>
Date: Sun, 4 Jan 2009 15:50:45 -0800
Message-ID: <0B3DFC41B4BE49839158486ACE2B0795@ad.redback.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
In-Reply-To: <1580F23C-BAB4-4586-98ED-9305AA89EF53@cisco.com>
Thread-Index: Aclut6aa6g2p0rVuRzmokRgbG20GOwAD4meA
Cc: rrg@irtf.org
Subject: Re: [rrg] Remote ACLs [Proposals which match rrg
	architectures.htmlpls check the page]
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

 

|The simple/short answer is because they are being used as IDs.


And this is an architectural bug that we should endeavour to fix, not
propagate.

Tony

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sun Jan  4 17:09:08 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E058B3A69D5;
	Sun,  4 Jan 2009 17:09:08 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D59893A69D5
	for <rrg@core3.amsl.com>; Sun,  4 Jan 2009 17:09:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.535
X-Spam-Level: 
X-Spam-Status: No, score=-6.535 tagged_above=-999 required=5 tests=[AWL=0.064, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id SjgzLOBururQ for <rrg@core3.amsl.com>;
	Sun,  4 Jan 2009 17:09:06 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 32E7A3A69CC
	for <rrg@irtf.org>; Sun,  4 Jan 2009 17:09:06 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.36,329,1228089600"; d="scan'208";a="223625627"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 05 Jan 2009 01:08:53 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n0518rR5006940; 
	Sun, 4 Jan 2009 17:08:53 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id n0518p1s009731;
	Mon, 5 Jan 2009 01:08:51 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 4 Jan 2009 17:08:53 -0800
Received: from moveme.cisco.com ([10.21.149.142]) by
	xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 4 Jan 2009 17:08:53 -0800
Message-Id: <480765D0-01B8-472B-B132-2320CC346480@cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: Pekka Nikander <pekka.nikander@nomadiclab.com>
In-Reply-To: <47BA4B32-C6A1-44DE-A040-1EE7017C39AC@nomadiclab.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Sun, 4 Jan 2009 17:08:52 -0800
References: <20081216190034.CB6236BE587@mercury.lcs.mit.edu>
	<66EAB6CC-9438-44BE-ACF2-86AD17307FB5@nomadiclab.com>
	<A26562FE-AE8B-4B16-9FBF-3A50EB39429E@cisco.com>
	<1A4C4166-0A84-40FF-9599-6281237844AF@nomadiclab.com>
	<D1B3196D-D935-47BF-9B84-C4376A455D38@cisco.com>
	<47BA4B32-C6A1-44DE-A040-1EE7017C39AC@nomadiclab.com>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 05 Jan 2009 01:08:53.0199 (UTC)
	FILETIME=[2CE25DF0:01C96ED2]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=12072; t=1231117733;
	x=1231981733; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dino@cisco.com;
	z=From:=20Dino=20Farinacci=20<dino@cisco.com>
	|Subject:=20Re=3A=20[rrg]=20Map=20and=20Encaps |Sender:=20;
	bh=t/UNUnAjXpyyi9bpl7g+8oFPRTz7ciutKlaBCpc87f8=;
	b=vWKn3mjHFd3ykmmHzaft6xadyOTgydvzPhkmu9clKgiNjr7HXJg8g5OiuM
	NJLMkpeMrdB0Eis6WTLqXZtwK3BeEyjPXX8T/DHw2OqcPJqqUv1HRbMn6UHT
	4K5bfInx5w;
Authentication-Results: sj-dkim-3; header.From=dino@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: rrg@irtf.org, Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: [rrg] Map and Encaps
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Thanks for your detailed responses Pekka. You answered all my questions.

Dino

On Dec 28, 2008, at 12:01 PM, Pekka Nikander wrote:

> [Those who do not care about details, may skip to the end where I  
> generalise.]
>
>>> The current implementation supports both IPv4 and IPv6 legacy  
>>> hosts.  So, it does support an IPv4 legacy site, if that is what  
>>> you ask.  IIRC, currently you manually configure the mapping  
>>> between Host Identities and the IPv4 addresses given to the legacy  
>>> hosts.  But that could be automated.
>>
>> And is it one-to-one? Or is the IPv4 address the HIP-proxy box at  
>> the edge of a site perhaps?
>
> In the implementation today, the mapping between the internal legacy  
> IPv4 or IPv6 addresses (EIDs in LISPish) and the HIP Host Identies  
> maintained at the proxy is one-to-one.  The external IPv4 or IPv6  
> address of the HIP-proxy box is just liked the RLOC in LISP.  I can  
> imagine a HIP-based box that has only one Host Identity (HI), or  
> fewer HIs than there are internal legacy hosts, but I wouldn't call  
> it a proxy but perhaps a "HIP tunnel box" or something else  
> instead.  (It wouldn't be too different from an IPsec security GW,  
> and therefore it wouldn't be very interesting to me.)
>
> The idea of the proxy is that from the HIP point of view a proxy  
> looks like a number of HIP hosts sitting at one shared IP address  
> (or a few shared IP addresses if the proxy is multihomed).  Hence,  
> from the HIP protocol point of view, it doesn't really matter if  
> what looks like a proxy is really a proxy, a host having a number of  
> Host Identities, or perhaps a host running a number of virtual  
> machines each having a separate Host Identity.  (HIP allows multiple  
> Host Identities to be assigned to a single host.)
>
>>> The current implementation supports connecting to both IPv4 and  
>>> IPv6 hosts from legacy IPv4 and IPv6 hosts.  Just like host HIP,  
>>> the proxy can do IPv4-IPv6 protocol translation in the fly if  
>>> needed.  (Apps that carry IP addresses in the payload are likely  
>>> to break, unless you do ALG, too.)
>>
>> The translation is a big deal when it comes to details. How does an  
>> IPv6 HIT get translated into an IPv4 address, presumably used as a  
>> HIT on IPv4 system?
>
> The HIT is the internal representation (handle) for a Host Identity,  
> used in the protocol itself.  When proxied, the internal legacy IP  
> addresses (EIDs) used between the proxy and the legacy hosts do not  
> need to be HITs -- they can be basically any IP addresses.  Such  
> addresses, at least when used at the host-internal legacy socket API  
> for HIP hosts, are called Local Scope Identifiers (LSIs) in the HIP  
> architecture document.  For the proxy, the usage could probably be  
> extended, so that LISPish EID would be LSI in HIPpish.  :-)
>
> For IPv6, it might well make sense to use ORCHID-based HITs as LSIs,  
> but obviously you cannot use that for IPv4.
>
> When there is an incoming packet, either internally at a host  
> through the legacy API, or through the internal interface at a  
> proxy, the LSIs are mapped to the HIs, as I already explained.  At  
> the same time, the TCP (and UDP) checksums are recomputed as if  
> there was an IPv6 pseudo-header and the SRC and DST address fields  
> contained the HITs.  See Section 4.5.1. of RFC 5201 for the exact  
> details.
>
> Hence, in the packets between any two HIP hosts, the checksums are  
> always based on the HITs, using the IPv6 pseudo-header format.   
> Then, obviously, if something else is used between the HIP proxy and  
> legacy hosts, the checksums must be recomputed.  This then leads to  
> the situation where simple protocols, such as SSH, benefit from an  
> implicit IPv4-IPv6 conversion in the case where one end uses IPv4  
> LSIs and the other end IPv6 LSIs.
>
> But as you say, once you go to more complex protocols, such as  
> tunnel-mode IPsec or protocols carrying IP addresses in the  
> playloads, things get complicated and typically require that the  
> same LSIs are used at both ends.
>
>>> From the RRG point of view, of course, there are a number of  
>>> operational issues that we haven't thought, and that I think you  
>>> LISP folks have thought a lot, like managing the mappings  
>>> automatically and in a large scale.
>>
>> Meaning that HIP-proxy isn't ready to be deployed yet?
>
> The HIP proxy has never been meant to solve the RRG problem, at  
> least not until now :-).   The proxy was developed to solve a  
> completely different problem: to make it possible to provide  
> simultaneous mobility and multi-homing to a number of co-operating  
> legacy sites and hosts.
>
> So, the HIP proxy is ready to be deployed if you have a single  
> organisation that cares about its internal connectivity over the  
> Internet and wants to make such communication more robust.
>
> For multi-organisation situation, the protocols themselves work.   
> However, AFAIK, nobody has cared to think about the operational  
> aspects, such as how to maintain the mappings between the  
> organisations etc.  Hence, if you mean that HIP-proxy is not ready  
> to be deployed in such a situation, you are right.
>
>>> In more detail, from the functional point of view, the proxy does  
>>> as follows:
>>>
>>> 1. The IP addresses in an incoming packet from a proxied legacy  
>>> host are mapped to Host Identities.  (If the destination address  
>>> cannot be mapped, the packet is not processed by the proxy and  
>>> typically NATed out.  Furthermore, as this mapping is a one-to-one  
>>> mapping (equivalence relation), and therefore the implementation  
>>> does not have to do it in practise.
>>
>> So a mapping database would have to hold entries for all globally  
>> reachable hosts?
>
> As you can see from above, the focus has been on the single- 
> organisation situation, where one can easily maintain the LSI->HI  
> mappings for all reachable destinations.
>
> OTOH, if you consider a situation where the destination LSI is a  
> legacy IP address and there is no information about how to map it  
> into a HI, I could imagine opportunistic HIP could be used; see  
> Section 4.1.6. of RFC 5201.  That could probably be combined with  
> some additional mapping mechanism, such as any of those proposed for  
> LISP.  The result would still support HIP-based combined mobility  
> and multi-homing, as the database would only be used for the initial  
> HIP association setup.
>
>>> 2. The "tunnels" (encapsulation format + destination locator)  
>>> associated with destination Host Identity are determined, and one  
>>> of them is selected for the packet, according to a policy.  Right  
>>> now HIP supports only ESP BEET mode tunnels, but adding other  
>>> types of tunnels (like IPv4 encapsulation) is quite easy, mostly  
>>> details.
>>>
>>> 3. The packet is encapsulated and sent out.
>>
>> Do you know ahead of time the destination locator is reachable?  
>> That is, by another means than having the destination locator's  
>> route in the routing table?
>
> That is addressed in the HIP mobility and multihoming RFC.  See  
> Section 5.4. of RFC 5206.  Furthermore, as the HIP control packet  
> format is bit-by-bit compatible with the SHIM6 control packet  
> format, the protocol defined in draft-ietf-shim6-failure- 
> detection-09 can be trivially reused.  (AFAIK, some HIP  
> implementations do so already now.)
>
>>> At the other end, the processing continues:
>>>
>>> 4. The packet is decapsulated and the right Host Identities are  
>>> determined.
>>
>> If the mapping is 1-to-1, how does the HIP-proxy know to  
>> decapsulate? And how does it know a HIP encapsulated packet is  
>> transited through the box that shouldn't be decapsualted?
>
> I don't quite understand your questions, so forgive me if I don't  
> address just what you ask for.
>
> The HIP proxy knows that it needs to decapsulate since a) the packet  
> has, as its destination address, one of the local addresses  
> configured to the proxy box and b) the packet has the encapsulation  
> format (currently ESP).  As the packet is destined to the proxy  
> itself, the packet is handed up in the stack and not forwarded.  As  
> a result, the packet goes to the protocol module that handles the  
> decapsulation.  So, there is no magic involved in that.
>
> In the light of that, I don't understand your latter question at all.
>
> ------------------
>
>>> This is quite flexible.  For example, I don't see any reason why  
>>> the LISP IPv4-in-IPv4 encapsulation header format couldn't be  
>>> used, if so desired.  The only data plane "difference"
>>
>> The encapsulation format in LISP is one of many values LISP brings,  
>> but there are more important ones.
>
> I completely agree that LISP has lots of functions, and many  
> functions that AFAICS could be reused for HIP-proxy based solution.   
> HIP also has lots of values that it brings.  Like baseline security,  
> mobility at different levels of granularity from sites to individual  
> flows, and multi-homing tightly integrated with mobility.
>
> -------------------
>
>> Well, we know today (haven't proved it yet) that two HIP hosts can  
>> talk to each other over an IPv4 Internet using LISP encapsulation.  
>> And since the packets to the LISP ITR look like regular IPv6  
>> packets, those embedded addresses (the HITs) *are* EIDs from the  
>> LISP router point of view. So they would be used as keys for the  
>> mapping database lookup to get locators returned.
>
> So, if I understand you Dino correctly, we seem to agree that from  
> the functional point of view, a HIP proxy and LISP xTRs perform a  
> pretty similar function.  That was the point I had, in reaction to  
> what Noel wrote:
>
>>>>>> As far as HIP goes, I think it's a neat concept, includes good  
>>>>>> ideas, and I
>>>>>> hope it catches on. However, two things. First, the installed- 
>>>>>> base/evolution
>>>>>> issues are significant - while new applications can use it, HIP  
>>>>>> isn't a great
>>>>>> deal of help when dealing with legacy hosts/applications/etc.  
>>>>>> Second, HIP
>>>>>> does nothing to provide us with a superior internetwork layer  
>>>>>> (including a
>>>>>> new routing architecture).
>
> In the light of the discussion above, I believe that it should now  
> be clear that Noel was wrong in what comes to HIP being able to help  
> legacy hosts or applications, and what comes to its *potential* in  
> helping to build a superior internetworking layer.  Granted, HIP and  
> not even the HIP proxy does not as such provide "a superior  
> internetworking layer".  But it *could* help building one, if so  
> desired.
>
> At this point, my only addition would be to again refer to the  
> expired "generix" draft, http://tools.ietf.org/html/draft-nikander-ram-generix-proxying-00 
> , from two years ago.  I still maintain that there is no real  
> difference, from the deployment point of view, between host-based  
> and network-based solutions.  One can implement a host-based  
> solution in the network, as the HIP proxy example shows.  Or one can  
> "squeeze" a network-based solution into a host.
>
> When solving the final target architecture, I think people should  
> think about the eventual, potential features it could give.  And  
> then work out the deployment path.
>
> My understanding is that the LISP folks have done a great job in  
> terms of thinking how it could be widely deployed already at step  
> 1.  Obviously, the HIP community has had a completely different  
> focus, thinking in small and trying to figure out how to deploy HIP  
> first within single organisations, and then gradually get benefits  
> from other organisations perhaps also adopting HIP.
>
> --Pekka
>

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sun Jan  4 17:11:18 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1DD8B3A69EA;
	Sun,  4 Jan 2009 17:11:18 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C9E613A69E8
	for <rrg@core3.amsl.com>; Sun,  4 Jan 2009 17:11:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.421
X-Spam-Level: 
X-Spam-Status: No, score=0.421 tagged_above=-999 required=5 tests=[AWL=0.560, 
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 
	RDNS_NONE=0.1, SARE_SUB_6CONS_WORD=0.356]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id z1p7ioUebmXd for <rrg@core3.amsl.com>;
	Sun,  4 Jan 2009 17:11:16 -0800 (PST)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66])
	by core3.amsl.com (Postfix) with ESMTP id 149E13A69EA
	for <rrg@irtf.org>; Sun,  4 Jan 2009 17:11:16 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0KCZ00KJT4M5ER@szxga03-in.huawei.com> for
	rrg@irtf.org; Mon, 05 Jan 2009 09:10:53 +0800 (CST)
Received: from x41208a ([10.111.12.103])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0KCZ006X84M1Q5@szxga03-in.huawei.com> for
	rrg@irtf.org; Mon, 05 Jan 2009 09:10:53 +0800 (CST)
Date: Mon, 05 Jan 2009 09:10:51 +0800
From: Xu Xiaohu <xuxh@huawei.com>
In-reply-to: <0B3DFC41B4BE49839158486ACE2B0795@ad.redback.com>
To: tony.li@tony.li, 'Dino Farinacci' <dino@cisco.com>,
	'Noel Chiappa' <jnc@mercury.lcs.mit.edu>
Message-id: <000c01c96ed2$73fa70b0$670c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Mailer: Microsoft Office Outlook 11
Thread-index: Aclut6aa6g2p0rVuRzmokRgbG20GOwAD4meAAAIwTBA=
Cc: rrg@irtf.org
Subject: Re: [rrg] Remote ACLs [Proposals which match
 rrg	architectures.htmlpls check the page]
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org


> 
> |The simple/short answer is because they are being used as IDs.
> 
> 
> And this is an architectural bug that we should endeavour to 
> fix, not propagate.
 
If we want to use ID in the ACL, should it also have some structure in
semantics? since the flat ID will cause a scaling issue with ACL and a huge
burden for manually configuration.

Xiaohu


_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sun Jan  4 17:19:34 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6EE033A682E;
	Sun,  4 Jan 2009 17:19:34 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6E5F23A682E
	for <rrg@core3.amsl.com>; Sun,  4 Jan 2009 17:19:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.361
X-Spam-Level: 
X-Spam-Status: No, score=-6.361 tagged_above=-999 required=5
	tests=[AWL=-0.118, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	SARE_SUB_6CONS_WORD=0.356]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id FZNHiOrm3LIL for <rrg@core3.amsl.com>;
	Sun,  4 Jan 2009 17:19:32 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id B40A83A67B3
	for <rrg@irtf.org>; Sun,  4 Jan 2009 17:19:32 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.36,329,1228089600"; d="scan'208";a="124685653"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-1.cisco.com with ESMTP; 05 Jan 2009 01:19:09 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n051J8mT007643; 
	Sun, 4 Jan 2009 17:19:08 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n051J8Vc027830;
	Mon, 5 Jan 2009 01:19:08 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 4 Jan 2009 17:19:08 -0800
Received: from moveme.cisco.com ([10.21.149.142]) by
	xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 4 Jan 2009 17:19:08 -0800
Message-Id: <417CE10E-C5DE-4825-B250-42F6751112EC@cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: Xu Xiaohu <xuxh@huawei.com>
In-Reply-To: <000c01c96ed2$73fa70b0$670c6f0a@china.huawei.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Sun, 4 Jan 2009 17:19:07 -0800
References: <000c01c96ed2$73fa70b0$670c6f0a@china.huawei.com>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 05 Jan 2009 01:19:08.0242 (UTC)
	FILETIME=[9B7A7B20:01C96ED3]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=694; t=1231118348; x=1231982348;
	c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dino@cisco.com;
	z=From:=20Dino=20Farinacci=20<dino@cisco.com>
	|Subject:=20Re=3A=20[rrg]=20Remote=20ACLs=20[Proposals=20wh
	ich=20match=20rrg=09architectures.htmlpls=20check=20the=20pa
	ge] |Sender:=20;
	bh=2kjmxLs/rNJSX2NozhlXYTOS96uCEaLsDrOFukNDhpg=;
	b=F9ajSFYkFb7WhIOwdtKEZ2XBDO1TROkKVJfUhqmFLlfdPnOj4RmiTuoii7
	tAdaOAL9LPCzSW/u7j9ESfXRAWpXJGRTW6u47+t3+xlIYPO7sjG9glec5GQK
	S1ojZbpdpYiMzLQBUgJ0Gi4duMVF8PSklBnweoBvE0V8rnjET7BpQ=;
Authentication-Results: sj-dkim-1; header.From=dino@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: rrg@irtf.org, 'Noel Chiappa' <jnc@mercury.lcs.mit.edu>
Subject: Re: [rrg] Remote ACLs [Proposals which match
	rrg	architectures.htmlpls check the page]
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

If EID-prefixes are allocated from RIRs, we can have structure. That  
is what the LISP architecture defines. Since it's a different  
namespace from the RLOC namespace, it's aggregation boundaries (in the  
address itself) can be different.

Dino

On Jan 4, 2009, at 5:10 PM, Xu Xiaohu wrote:

>
>>
>> |The simple/short answer is because they are being used as IDs.
>>
>>
>> And this is an architectural bug that we should endeavour to
>> fix, not propagate.
>
> If we want to use ID in the ACL, should it also have some structure in
> semantics? since the flat ID will cause a scaling issue with ACL and  
> a huge
> burden for manually configuration.
>
> Xiaohu
>
>

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sun Jan  4 18:02:42 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3CFD03A682E;
	Sun,  4 Jan 2009 18:02:42 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 739EF3A67B3
	for <rrg@core3.amsl.com>; Sun,  4 Jan 2009 18:02:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.965
X-Spam-Level: 
X-Spam-Status: No, score=-1.965 tagged_above=-999 required=5 tests=[AWL=0.012, 
	BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id E51ENvGMQpSU for <rrg@core3.amsl.com>;
	Sun,  4 Jan 2009 18:02:39 -0800 (PST)
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.178])
	by core3.amsl.com (Postfix) with ESMTP id 6C40B3A682E
	for <rrg@irtf.org>; Sun,  4 Jan 2009 18:02:39 -0800 (PST)
Received: by wa-out-1112.google.com with SMTP id j37so4023151waf.23
	for <rrg@irtf.org>; Sun, 04 Jan 2009 18:02:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:sender
	:to:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references
	:x-google-sender-auth;
	bh=TbGGmDJA/C/Bef7ERQgnSVF+sAOhCOp5hfLC+hm5DTk=;
	b=L8yHLmPt453F8PUyCtSlDPFqt3wWp9fTAgz9tOs1GFkGoj9qc5G10VYcpoIZmfLPcn
	f9iq6+dz1FVw3q56ROnPtHQQVnmgvK761j6li2clOXMF7gghqLfHGUzVYCRHOjhWtVcn
	+cTe8em/AVRwHIvBQv48n7n1uAUPZl8+VA5VE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references:x-google-sender-auth;
	b=qHnKWzNBI0pcly6+Rl3YBgr9MkEJ3fAGhqMXrWoakpxWgDVOlQEcDzzxviAEf63rBp
	JM1vz7D6phqt0jbI/TnlPhRGnyQNPh+J0BThjhPh5I0MEsy5yZHXeC4Ho414FweNKjuU
	0siKEMDe37TYfc9YmfQAsLEFoM3zR5p1BlJAg=
Received: by 10.114.24.1 with SMTP id 1mr13455527wax.179.1231120945429;
	Sun, 04 Jan 2009 18:02:25 -0800 (PST)
Received: by 10.115.74.12 with HTTP; Sun, 4 Jan 2009 18:02:25 -0800 (PST)
Message-ID: <3c3e3fca0901041802x503945b4q68e142ae229d02f@mail.gmail.com>
Date: Sun, 4 Jan 2009 21:02:25 -0500
From: "William Herrin" <bill@herrin.us>
To: tony.li@tony.li
In-Reply-To: <2BD330FB290F484F80D5910F18316328@ad.redback.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com>
	<87D9F0BA2807456A88B0427241A29F65@ad.redback.com>
	<3c3e3fca0901021219t2ab35dfsb2532e0c89be84af@mail.gmail.com>
	<E99E41EB33084B5B899C7EED9DE607E9@ad.redback.com>
	<3c3e3fca0901021334j22d17e54iec4bbf41b6c00480@mail.gmail.com>
	<BCFF32A1356842BF839C7DF7D059F15F@ad.redback.com>
	<3c3e3fca0901031320o1253fcd3s3b6597aef77fba33@mail.gmail.com>
	<A071B6FF07CD4B708EC6CA2B9938096D@ad.redback.com>
	<3c3e3fca0901031720w602d931ev42707b169f51fba9@mail.gmail.com>
	<2BD330FB290F484F80D5910F18316328@ad.redback.com>
X-Google-Sender-Auth: 2c1d30b29fe5b1ca
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On Sun, Jan 4, 2009 at 12:48 AM, Tony Li <tony.li@tony.li> wrote:
> |The history of the computing industry is one of regularly encountered
> |one-time advances. Moore's Law isn't built on the back of purely
> |evolutionary improvement.
>
> True, but one time advances from the networking industry catching up to the
> rest of computing are all expended.  It now tracks it quite well, albeit

So routing improvement now "tracks quite well" with general computing
improvement which is predicted by Moore's Law to compound at 40%
annually, just like I claimed for routers?


> |2. Engineer's maxim: if it ain't broke, don't fix it. If failure does
> |not loom on BGP's horizon, there is little justification for moving
> |any disruptive strategy forward from research to engineering. The
> |desirable output from our efforts is *very* different depending on
> |whether or not BGP is failing.
>
> Again, it's not BGP, it's the number of prefixes.  Any other protocol would
> have to deal with the implications of a DFZ with a full set of prefixes as
> well.  Thus, it's the architecture that must change.

Please take it as a given that "BGP failing" is in fact shorthand
referring to the failure of the routing architecture in which every
multihomed system requires a slot in the routing tables of every core
router with all the attendant data transmission and computation. Et
cetera.


>  And, once again, if
> you don't believe that it needs to be fixed, I refer you to the problem
> statement.

I've long been convinced that BGP's scaling problem -should- be addressed.

Whether it -needs- to be addressed is an entirely different issue
which has a major practical impact on the intermediate research goals
and on the appropriate research posture that focuses our efforts.

Stance matters.

Proposals based on the presumption that BGP -needs- to be replaced
will far overreach proposals based on the proposition that we should
steadily nudge the architecture towards something more desirable.
Without a clear case that BGP -needs- to be replaced, that overreach
will almost certainly render the proposals into operational
non-starters.

As we overreach, we'll tend not to closely examine the more moderate
proposals for evolving in to an improved architecture that do not
immediately form into a comprehensive solution.


Tony, you've long complained that we're jumping straight to concrete
action proposals instead of doing research, but the research stance
based on the proposition that BGP will fail compels us to focus on
comprehensive solutions, for which concrete action proposals are
required.


> |However frightful the monsters under the bed may be, there is
> |insufficient proof of their existence to justify giving your toddler a
> |shotgun.
>
> Hopefully there are better solutions than that regardless of motivation.  My
> toddler has horrible aim.  ;-)

When we asked the RIRs obstruct PI prefixes for multihomed IPv4 and
IPv6 users, we upgraded them from cap guns to bullets. It's a very
*harmful* practice which should be discouraged absent testable and
quantitatively substantiated growth predictions projecting routing
table growth which outstrips our ability to build hardware. The IPv6
side is especially harmful, given the looming free pool crisis whose
projections are very well grounded. As a group, we should withdraw
that recommendation and discourage obstructing PI space for
multihomers.

Regards,
Bill Herrin

-- 
William D. Herrin ................ herrin@dirtside.com  bill@herrin.us
3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
Falls Church, VA 22042-3004
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sun Jan  4 19:34:19 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 00C0B3A6963;
	Sun,  4 Jan 2009 19:34:19 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EE2EF3A6963
	for <rrg@core3.amsl.com>; Sun,  4 Jan 2009 19:34:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[AWL=0.113, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id BERxBXG5Kkma for <rrg@core3.amsl.com>;
	Sun,  4 Jan 2009 19:34:17 -0800 (PST)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.235])
	by core3.amsl.com (Postfix) with ESMTP id 2BD913A67B3
	for <rrg@irtf.org>; Sun,  4 Jan 2009 19:34:17 -0800 (PST)
Received: by rv-out-0506.google.com with SMTP id f6so8921959rvb.7
	for <rrg@irtf.org>; Sun, 04 Jan 2009 19:34:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from
	:organization:user-agent:mime-version:to:cc:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=8h4JbYr51DJL0fi/JWKYYoTiHywHdbitiPqmfcM7z7E=;
	b=pn37BcjxTt0LaiIIG8ZPCXbZLe1FdT4zOhgxVFxk3S4HxmKizIMIkfVSccKRP6mG/3
	xKx7Bk8O7PQfVMvJY9LYxjB8vQsMRH07FgY+j+G9XrV5Wg5N/+kYps5pFFtGYj2KNevy
	ypC6fHe0z1+oqk097mekfInlryRUkz0aqFBNY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	b=gCiRjJeBGScgBDzVOE7X7SME6GZsy/bQpo2Msk7wn9IxNIiJXkyGxqsAtsAVJEMTK/
	xfSJEJjirH3AAOsF/7HVOFxv9sc7wsOI3EhVVaf4keR77HAYL+8wowDqP+hux92P+V18
	ZLpB2sF6N9Y/3nMi9aHWLhJLsocfpA6IbQw4k=
Received: by 10.140.202.21 with SMTP id z21mr10161049rvf.68.1231126443430;
	Sun, 04 Jan 2009 19:34:03 -0800 (PST)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz
	[130.216.38.124])
	by mx.google.com with ESMTPS id l31sm61785020rvb.2.2009.01.04.19.34.02
	(version=SSLv3 cipher=RC4-MD5); Sun, 04 Jan 2009 19:34:03 -0800 (PST)
Message-ID: <49617FA8.9090607@gmail.com>
Date: Mon, 05 Jan 2009 16:34:00 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: William Herrin <bill@herrin.us>
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com>	<87D9F0BA2807456A88B0427241A29F65@ad.redback.com>	<3c3e3fca0901021219t2ab35dfsb2532e0c89be84af@mail.gmail.com>	<E99E41EB33084B5B899C7EED9DE607E9@ad.redback.com>	<3c3e3fca0901021334j22d17e54iec4bbf41b6c00480@mail.gmail.com>	<BCFF32A1356842BF839C7DF7D059F15F@ad.redback.com>	<3c3e3fca0901031320o1253fcd3s3b6597aef77fba33@mail.gmail.com>	<A071B6FF07CD4B708EC6CA2B9938096D@ad.redback.com>	<3c3e3fca0901031720w602d931ev42707b169f51fba9@mail.gmail.com>	<2BD330FB290F484F80D5910F18316328@ad.redback.com>
	<3c3e3fca0901041802x503945b4q68e142ae229d02f@mail.gmail.com>
In-Reply-To: <3c3e3fca0901041802x503945b4q68e142ae229d02f@mail.gmail.com>
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On 2009-01-05 15:02, William Herrin wrote:
...
> When we asked the RIRs obstruct PI prefixes for multihomed IPv4 and
> IPv6 users, we upgraded them from cap guns to bullets.

That was in early 1994, I believe. If you were looking at the DFZ
growth curve back then, the bullets seemed inadequate, but they worked
for a while.

> It's a very
> *harmful* practice which should be discouraged absent testable and
> quantitatively substantiated growth predictions projecting routing
> table growth which outstrips our ability to build hardware. The IPv6
> side is especially harmful, given the looming free pool crisis whose
> projections are very well grounded. 

As I've always understood things, the challenge is to find the best
possible distribution of the harm; if the RIRs hadn't succeeded in
damping prefix growth, who knows when things would have ground to a
painful halt? My conclusion is exactly the opposite of yours: absent
substantiated growth predictions, the priority must continue to be
precautionary damping of the growth, as a matter of public importance.

> As a group, we should withdraw
> that recommendation and discourage obstructing PI space for
> multihomers.

Didn't you forget to add "as soon as there is a proven way to
ensure that the resulting growth in prefixes can be handled by the
routing system"?

(Not that the RRG can withdraw CIDR, anyway.)

    Brian
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sun Jan  4 19:45:12 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 688F33A67E4;
	Sun,  4 Jan 2009 19:45:12 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B7A563A67E4
	for <rrg@core3.amsl.com>; Sun,  4 Jan 2009 19:45:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.965
X-Spam-Level: 
X-Spam-Status: No, score=-1.965 tagged_above=-999 required=5 tests=[AWL=0.012, 
	BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 3QlLPTJKrp0d for <rrg@core3.amsl.com>;
	Sun,  4 Jan 2009 19:45:09 -0800 (PST)
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.176])
	by core3.amsl.com (Postfix) with ESMTP id AAED33A67B3
	for <rrg@irtf.org>; Sun,  4 Jan 2009 19:45:09 -0800 (PST)
Received: by wa-out-1112.google.com with SMTP id j37so4043430waf.23
	for <rrg@irtf.org>; Sun, 04 Jan 2009 19:44:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:sender
	:to:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references
	:x-google-sender-auth;
	bh=MeXmHgA4/ZRzfP97cXRl8K3LcKADx0Q00eTxRXPNdRs=;
	b=ajxeUPqjVwMEeBID2z/EECTU2qmy0MpLUcd3h/n17bXq+FkPGQrPwv4LLv8I0MBPb2
	DlqtHS5T9Z9JYn18LYAMtiDBvrDRSRMgCmOd1Mdy1PWiAsugNY1utcvJDXa8RYDJ9ZI2
	yUA5WTJSoRVj4LXqBL/d/9FoOSRTP14otXesU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references:x-google-sender-auth;
	b=nbycYY8j6SaBod8du3S8BQtVReLaZFck/hwMehyJTx+rKg6oeYLp9teDRtwTszz2nx
	bDhC3sjMLy3WGfvVnIQzPlD8eDnKAFDU2Z2l9GSOSDwJ4sVL1iiQCkz5pB+VUWrjakMf
	fDmpqLO7bVIUlBRiDnJB/HYOa69i3CcRYUW1o=
Received: by 10.114.194.1 with SMTP id r1mr13531325waf.18.1231127096489;
	Sun, 04 Jan 2009 19:44:56 -0800 (PST)
Received: by 10.115.74.12 with HTTP; Sun, 4 Jan 2009 19:44:56 -0800 (PST)
Message-ID: <3c3e3fca0901041944t53c7587g7a1e65a9a5777fac@mail.gmail.com>
Date: Sun, 4 Jan 2009 22:44:56 -0500
From: "William Herrin" <bill@herrin.us>
To: "MARCELO BAGNULO BRAUN" <marcelo@it.uc3m.es>
In-Reply-To: <49611727.5000806@gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <4959B44C.2030709@firstpr.com.au> <4959C284.4060805@firstpr.com.au>
	<1230720711.5901.25.camel@localhost> <495EF3B1.1030408@firstpr.com.au>
	<20090103121825.co8r3bgpwkwwggk4@webcartero01.uc3m.es>
	<495F770C.4070004@firstpr.com.au>
	<20090104145408.q0i0wpgtck48kssg@webcartero01.uc3m.es>
	<49611727.5000806@gmail.com>
X-Google-Sender-Auth: 17f2ead2618e7e21
Cc: rrg@irtf.org
Subject: Re: [rrg] Remote ACLs [Proposals which match rrg architectures.html
	pls check the page]
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

> On 2009-01-05 02:54, MARCELO BAGNULO BRAUN wrote:
>>>  3 - Problems with maintaining ACLs in other networks for hosts
>>>      using SHIM6.
>> I don't understand this one

Marcello,

Shim6 has several weaknesses that can be revealed by comparing it to
the Strategy B criteria. This particular weakness is the lack of
accompanying dynamic source routing protocol.

Unless the IGP in a stratgy B system moves packets first to a valid
exit for the source address and only then to the optimal exit for the
destination address, you end up with a nasty spoofing problem where
routers require extensive manual configuration to tell the difference
between a spoofed source address and a valid multiprefix source
address.

Regards,
Bill Herrin


-- 
William D. Herrin ................ herrin@dirtside.com  bill@herrin.us
3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
Falls Church, VA 22042-3004
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sun Jan  4 21:51:14 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BA9C83A68B0;
	Sun,  4 Jan 2009 21:51:14 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D31F53A68B0
	for <rrg@core3.amsl.com>; Sun,  4 Jan 2009 21:51:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.529
X-Spam-Level: 
X-Spam-Status: No, score=-2.529 tagged_above=-999 required=5 tests=[AWL=0.070, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6pwvvkKxl6nz for <rrg@core3.amsl.com>;
	Sun,  4 Jan 2009 21:51:10 -0800 (PST)
Received: from QMTA04.emeryville.ca.mail.comcast.net
	(qmta04.emeryville.ca.mail.comcast.net [76.96.30.40])
	by core3.amsl.com (Postfix) with ESMTP id DC7D13A6837
	for <rrg@irtf.org>; Sun,  4 Jan 2009 21:51:10 -0800 (PST)
Received: from OMTA02.emeryville.ca.mail.comcast.net ([76.96.30.19])
	by QMTA04.emeryville.ca.mail.comcast.net with comcast
	id zTWF1a0070QkzPwA4hqy3T; Mon, 05 Jan 2009 05:50:58 +0000
Received: from TONYLTM9XP ([155.53.1.254])
	by OMTA02.emeryville.ca.mail.comcast.net with comcast
	id zhql1a0075Up7oj8Nhqnm0; Mon, 05 Jan 2009 05:50:55 +0000
From: "Tony Li" <tony.li@tony.li>
To: "'William Herrin'" <bill@herrin.us>
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com>
	<87D9F0BA2807456A88B0427241A29F65@ad.redback.com>
	<3c3e3fca0901021219t2ab35dfsb2532e0c89be84af@mail.gmail.com>
	<E99E41EB33084B5B899C7EED9DE607E9@ad.redback.com>
	<3c3e3fca0901021334j22d17e54iec4bbf41b6c00480@mail.gmail.com>
	<BCFF32A1356842BF839C7DF7D059F15F@ad.redback.com>
	<3c3e3fca0901031320o1253fcd3s3b6597aef77fba33@mail.gmail.com>
	<A071B6FF07CD4B708EC6CA2B9938096D@ad.redback.com>
	<3c3e3fca0901031720w602d931ev42707b169f51fba9@mail.gmail.com>
	<2BD330FB290F484F80D5910F18316328@ad.redback.com>
	<3c3e3fca0901041802x503945b4q68e142ae229d02f@mail.gmail.com>
Date: Sun, 4 Jan 2009 21:50:08 -0800
Message-ID: <48545DC21F554925BF49412DB6C903D5@ad.redback.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
In-Reply-To: <3c3e3fca0901041802x503945b4q68e142ae229d02f@mail.gmail.com>
Thread-Index: Aclu2akO5/bT8bKnTJ+/cp36HhfffQAH1nNQ
Cc: 'RRG' <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

 

|So routing improvement now "tracks quite well" with general computing
|improvement which is predicted by Moore's Law to compound at 40%
|annually, just like I claimed for routers?


Correct, but please again see my presentation.  Moore's law only applies to
transistor density (and it's not 40%), which doesn't necessarily help us.


|Please take it as a given that "BGP failing" is in fact shorthand
|referring to the failure of the routing architecture in which every
|multihomed system requires a slot in the routing tables of every core
|router with all the attendant data transmission and computation. Et
|cetera.


Please fix your misleading shorthand.


|Tony, you've long complained that we're jumping straight to concrete
|action proposals instead of doing research, but the research stance
|based on the proposition that BGP will fail compels us to focus on
|comprehensive solutions, for which concrete action proposals are
|required.


What I've tried to do is to encourage architectural discussion PRIOR to
going to the concrete.  There are lots of big upper layer issues (exactly at
the level of your strategies) that need to be dealt with before getting into
the bits and the bytes.


Tony

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan  5 01:16:24 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 34ECA3A67DD;
	Mon,  5 Jan 2009 01:16:24 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3545C3A67A4
	for <rrg@core3.amsl.com>; Mon,  5 Jan 2009 01:16:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.405
X-Spam-Level: 
X-Spam-Status: No, score=-1.405 tagged_above=-999 required=5 tests=[AWL=0.175, 
	BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327,
	SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id YuSylOXsmqAJ for <rrg@core3.amsl.com>;
	Mon,  5 Jan 2009 01:16:21 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123])
	by core3.amsl.com (Postfix) with ESMTP id B8B113A63D3
	for <rrg@irtf.org>; Mon,  5 Jan 2009 01:16:18 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6])
	by gair.firstpr.com.au (Postfix) with ESMTP id 3E66F175AED;
	Mon,  5 Jan 2009 20:16:03 +1100 (EST)
Message-ID: <4961CFD3.2050304@firstpr.com.au>
Date: Mon, 05 Jan 2009 20:16:03 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: RRG <rrg@irtf.org>
References: <495F0BAA.2040303@firstpr.com.au> <49611E83.8050301@gmail.com>
In-Reply-To: <49611E83.8050301@gmail.com>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Short version:   I broadly agree with Brian's "... my preference is
                 to recommend development work on strategy A and
                 continued R&D on strategy B."


Hi Brian,

Thanks for your detailed response.

You wrote, in part:

>>                 HIP has been mentioned, but no-one seems to be
>>                 proposing it as a scalable routing solution.
> 
> I think Pekka observed that this wasn't even a goal. (My quick answer
> is that it only becomes a routing solution if it solves the same
> mapping problem that strategy A generates.)

I don't understand your comment, but if the HIP proponents do not see
it as a solution to the routing scaling problem, then unless someone
on the RRG feels strongly that it is, then HIP is out of scope for
discussion and for matching against any of Bill's architectures.

> Shim6 has also been mentioned, as a mitigation of some the issues
> with the multiprefix PA model. That is already chartered IETF work
> with full documentation.

Yes - and Shim6 matches Bill's Strategy G:

  http://bill.herrin.us/network/rrgarchitectures.html
  http://www.firstpr.com.au/ip/ivip/rrgarch/



>> Every possible Strategy B approach would be vastly harder to have
>> adopted by the majority of end-user networks which want multihoming,
>> TE and portability (or its functional equivalent) than any Strategy A
>> approach, for at least two reasons:
>>
>>   1 - Strategy B solutions require most or all current Internet users
>>       to adopt IPv6 - and furthermore IPv6 with a modified host
>>       stack, API and applications.
> 
> The first half of this is increasingly likely to happen anyway. 

So people have been saying since 1996.  I will believe it when I see it.

> It isn't certain that the API and apps have to be touched; rolling out new 
> stacks over five to ten years really isn't a valid objection.

I agree that if only the stacks need to be changed, then that would
be a much lower impediment - especially with IPv6 which is hardly
used at present.

ILNP supposedly requires no API or application changes - but as far
as I can see, it won't handle referrals, or at least won't provide
multihoming for referrals.  Ran suggests rewriting apps to avoid the
need for referrals.  I think this would be a major barrier to
adoption.  My next two messages concern ILNP.

Would SIP need to be changed to avoid referrals or to do the same
thing in ILNP-friendly ways?

> But I fully agree: strategy B == IPv6.

OK.


>>   2 - Strategy B solutions provides benefits to adoptors only when
>>       the other host in a session (stack and relevant applications)
>>       has been upgraded too.  So until almost all networks and their
>>       hosts adopted it, the scheme could only provide multihoming for
>>       a fraction of communication sessions.
> 
> This is true. The question is whether this (piecemeal incentives, highly
> distributed low costs) is really less effective than the incentives to pay
> the highly concentrated per-network costs of strategy A.

With Ivip, I anticipate that the businesses which provide the mapping
service and who rent out Mapped Address Blocks, splitting them up
into thousands of smaller pieces for end-user networks to split
further into micronets (EIDs) will be offering a valuable service
from the start.  This is because Ivip supports multihoming, TE and
portability, including for all packets coming from hosts in
non-upgraded networks.  I expect this to be a profitable business,
not some cold, dead, thing we reluctantly put millions of dollars
into in order to avoid a future DFZ meltdown.


>> Also, I argue that any approach which involves pushing
>> responsibilities and management traffic to all hosts (all potential
>> Strategy B approaches) is fundamentally flawed:
>>
>>   http://www.irtf.org/pipermail/rrg/2008-November/000233.html
> 
> Highly distributed = scaleable. And in any cases, hosts have always
> been responsible for traffic management (that's called TCP)
> and approaches like SCTP and the proposed multipath TCP extend that.
> So I don't think we should condemn this in the abstract.

Yes - but the existing host functions (with the possible exception of
some of SCTP's functions) are all coping with things which must be
handled in the hosts.

Multihoming, TE and portability can be handled in the network,
without touching the hosts or burdening them with the resulting
management traffic.

I think ILNP is not an exact match for Bill's Strategy B, but it is
close enough for general discussion.  That adds a lot of state to
each host for every IP address the host communicates with.  There is
extra management traffic, in the form of longer DNS responses and
sending and receiving Nonce Destination Options.  That requires more
code to handle the resulting PMTUD problems, and as far as I can see,
will restrict the maximum packet length any application can send to
20 bytes less than whatever it would otherwise be.

I think ILNP is an absolutely minimal proposal.  If fully developed,
it would need to be more complex, I am sure.

HIP is another potential host-based approach, though it too does not
seem to match Strategy B directly.  HIP is much more complicated,
with every host being required to do fancy cryptography, and there
being several RTTs of exchanges between two hosts before any real
work can be done.

  http://infrahip.hiit.fi/index.php?index=how

A fully developed HIP would involve multiple cryptography options,
further increasing complexity.

I stand by my objections to forcing such complexity and extra traffic
onto every host in the future IPv6 Net - for things which happen in
the network and can best be handled there: multihoming, TE and the
need for portability as the only reasonable way (for all but the
smallest networks) of selecting a new ISP without major costs and risks.


>> I find it impossible to imagine how a Strategy B solution could
>> succeed if we fail to solve the problem via the best one or more
>> Strategy A solutions being properly developed and offered for adoption.
>>
>> RRG rejection of Strategy B solutions is not to suggest that people
>> shouldn't work on such schemes.  Just that we have no confidence that
>> any such scheme could turn out to be technically better and/or easier
>> to have widely adopted than a well developed version of the best of
>> the Strategy A schemes.
> 
> 
>> Of course, if the best efforts with Strategy A schemes fails, then
>> everything would be up for reconsideration.  However, that is a
>> potential scenario in the post-2020 future.  Then, any Strategy B
>> solution would still involve much higher barriers to development and
>> adoption than any Strategy A solution.
> 
> Exactly. Which is why my preference is to recommend development work
> on strategy A and continued R&D on strategy B; I'd be very concerned
> if we shrugged our shoulders and dropped it for 12 years.

OK.  I agree - except I guess we will recommend something more
specific than any architecture which fits Bill's Strategy A definition.

My notion of the RRG rejecting Strategy B - and any other comparable
elimination schemes which involve new host functionality and
management traffic - is that we are rejecting the notion of
considering any such scheme for recommendation to the IETF for
development in order to solve the routing scaling problem in the
foreseeable future.

The RRG not recommending any such architecture for IETF development
is not a message to developers to stop working on such things.

  - Robin
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan  5 01:24:40 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 838E13A6AF3;
	Mon,  5 Jan 2009 01:24:40 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D83DF3A693E
	for <rrg@core3.amsl.com>; Mon,  5 Jan 2009 01:24:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.167
X-Spam-Level: 
X-Spam-Status: No, score=-1.167 tagged_above=-999 required=5
	tests=[AWL=-0.071, BAYES_00=-2.599, HELO_EQ_AU=0.377,
	HOST_EQ_AU=0.327, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id kFb23Bu-cX1z for <rrg@core3.amsl.com>;
	Mon,  5 Jan 2009 01:24:37 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123])
	by core3.amsl.com (Postfix) with ESMTP id 486903A63D3
	for <rrg@irtf.org>; Mon,  5 Jan 2009 01:24:37 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6])
	by gair.firstpr.com.au (Postfix) with ESMTP id 2A02E175AED;
	Mon,  5 Jan 2009 20:24:24 +1100 (EST)
Message-ID: <4961D1C8.8070902@firstpr.com.au>
Date: Mon, 05 Jan 2009 20:24:24 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: RRG <rrg@irtf.org>
Cc: Randall Atkinson <rja@extremenetworks.com>
Subject: [rrg] ILNP I-Ds and place in rrgarchitectures.html
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Short version:  ILNP's new and updated Internet Drafts.
                I think ILNP not not fully match Bill's Strategy B.

Brian Carpenter wrote, ("Re: [rrg] Rejecting all but Strategy A" you
wrote) in part:

>>  Strategy B:  There are no properly documented proposals.
>>               ILNP may be a Strategy B approach but it is not
>>               properly documented as a scalable routing solution.
>>               There is no Summary and Analysis in the RRG wiki.
>
> It's unclear to me that ILNP belongs in B since it has
> characteristics of A as well.

ILNP is an "elimination" approach.  I can't think of any any
characteristics it has in common with the "core-edge separation"
proposals which match Strategy A.


> Whether it's jumped through the hoops of the wiki strikes me as
> uninteresting; it seems to be well documented.

I see now that these I-Ds were updated on 10 December:

  ILNP Concept of Operations
    http://tools.ietf.org/html/draft-rja-ilnp-intro-02

  Additional DNS Resource Records
    http://tools.ietf.org/html/draft-rja-ilnp-dns-01

  Nonce Destination Option
    http://tools.ietf.org/html/draft-rja-ilnp-nonce-01

and one was added:

  ICMP Locator Update message
    http://tools.ietf.org/html/draft-rja-ilnp-icmp-00

There's about 29 pages of actual material here.  I think the proposal
is better documented than before.  I read them all and have written
some notes about them in a separate "ILNP critique 3" message.

Ran never mentioned these new or updated I-Ds on the RRG list.  I
consider that to be one form of lack of documentation.  Its not
realistic to expect RRG people to methodically check for new I-Ds.

Likewise, since Ran is proposing ILNP as a solution to the routing
scaling problem, out of respect for the time and energy of RRG
members, I think he should write up a summary and analysis document:

  http://psg.com/lists/rrg/2007/msg00908.html

and link to it from the RRG wiki.  (I haven't been able to access the
 wiki recently.)

	
I think that ILNP almost matches Bill's Strategy B:

  http://bill.herrin.us/network/rrgarchitectures.html  (6th draft)

I wasn't sure about these sentences, but here is my understanding of
why I think ILNP only partially matches them.

   GUID to LOC maps are pushed from the host towards a distributed
   registry as they change. Hosts request and temporarily cache
   individual mappings from the registry as needed.

In ILNP, an initiating host S is supposed to begin contact with a
responding host R by looking up R's FQDN in the DNS, and receiving
two new types of record.

Bill's GUID concept is implemented in ILNP by the host's FQDN.

In the case of R being multihomed via two ISPs, the first new new
type of record would be:

  L for R's ISP 1:  64 bits which will be used as MSB of IP address
                    to which S will send a packet.  Has a priority
                    number as well.

  L for R's ISP 2:  64 bits which will be used as MS 64 bits of IP
                    address to which S will send a packet.  Has a
                    priority number as well.

These L records and their 64 bits implement Bill's LOC function.

There would also be at least one:

  I 64 bits of (ideally) unique Identifier, with a priority to choose
    between multiple such identifiers if there were more than one.
    This will be used to form the LS 64 bits of the address to which
    S will send a packet.


The I bits seem to implement Bill's SID function.

So the DNS maps a FQDN to one or potentially more I (identifiers) and
(for multihoming) to two or more L locators.  (See my forthcoming
critique for how this can't support round-robin addressing for hosts
in different end-user networks.)

When R changes its locators (for instance one goes down in a
multihoming failure condition), R updates S's notion of its locators
and S can continue the session.  R is also supposed to update the DNS
server for its FQDN to reflect the changed set of L locators.

At the start of the session, S sends R a nonce and R sends S a
separate nonce.  These are used to secure the sending an updated set
of LOCs by either host to the other.  The nonce is also sent with a
data packet to uniquely identify this host (otherwise known by its I
bits) when the host starts sending packets with a source address
involving another set of L bits than what it used before.  This
enables the other host to recognise this securely as a continuation
of a session which came from another L prefix.

To match Bill's first sentence, I would say the DNS is the
distributed registry.  However, I think that ILNP does not match the
second sentence:

   Hosts request and temporarily cache individual mappings from the
   registry as needed.

ILNP hosts do not cache those I and L bits they get from the DNS.
The caching time is zero, in hosts and in any caching nameservers
which handle the request and response.  These bits are used purely to
initiate a session.  After that, the hosts communicate with each
other, secured by nonces, to inform each other of changes in their L
bits.  Also, CE routers can tell remote hosts a new set of LOCs for a
host in the local network - however, it is not clear how the router
tells this to the local host.

Ran - do you or anyone else think that ILNP fits one of Bill's
strategies?  If not, perhaps you could suggest a new strategy to add.

  - Robin
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan  5 01:43:25 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 07F4C3A6A45;
	Mon,  5 Jan 2009 01:43:25 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1381E3A6A45
	for <rrg@core3.amsl.com>; Mon,  5 Jan 2009 01:43:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.165
X-Spam-Level: 
X-Spam-Status: No, score=-1.165 tagged_above=-999 required=5
	tests=[AWL=-0.069, BAYES_00=-2.599, HELO_EQ_AU=0.377,
	HOST_EQ_AU=0.327, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 2yip4l3epqHV for <rrg@core3.amsl.com>;
	Mon,  5 Jan 2009 01:43:22 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123])
	by core3.amsl.com (Postfix) with ESMTP id 4933E3A67A4
	for <rrg@irtf.org>; Mon,  5 Jan 2009 01:43:21 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6])
	by gair.firstpr.com.au (Postfix) with ESMTP id 0DE33175AF2;
	Mon,  5 Jan 2009 20:43:08 +1100 (EST)
Message-ID: <4961D62C.1040207@firstpr.com.au>
Date: Mon, 05 Jan 2009 20:43:08 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: RRG <rrg@irtf.org>
Cc: Randall Atkinson <rja@extremenetworks.com>
Subject: [rrg] ILNP critique 3
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Here is my third attempt at understanding and critiquing ILNP.
I think I understand it better than in the past.

Please see my previous message for why I think ILNP does not fit into
any of Bill's strategies, and why I think it needs to have a Summary
and Analysis document.

  - Robin



My previous critiques of ILNP were:

  http://psg.com/lists/rrg/2008/msg02464.html
  2008-09-15

  http://www.irtf.org/pipermail/rrg/2008-November/000169.html
  2008-11-17

The current I-Ds are from 2008-12-10:

  ILNP Concept of Operations
    http://tools.ietf.org/html/draft-rja-ilnp-intro-02

  Additional DNS Resource Records
    http://tools.ietf.org/html/draft-rja-ilnp-dns-01

  ICMP Locator Update message
    http://tools.ietf.org/html/draft-rja-ilnp-icmp-00

  Nonce Destination Option
    http://tools.ietf.org/html/draft-rja-ilnp-nonce-01


My general critique of requiring hosts to handle multihoming etc.
applies to ILNP:

  http://www.irtf.org/pipermail/rrg/2008-November/000268.html
  2208-11-24

Here are some notes and critiques of the current I-Ds.

ILNP Concept of Operations
http://tools.ietf.org/html/draft-rja-ilnp-intro-02

  The lack of guaranteed uniqueness for IDs (lower 64 bits of
  address) strikes me as a potential problem - for obvious reasons.

  Although a host is supposed to be able to tell the difference
  between two hosts it is communicating using the same ID, based
  on the nonce value, (P15) it is not clear how this would be
  conveyed to applications, since the stack apparently only gives
  the lower 64 bits to the applications.

  It is not clear to me how ILNP would work with unmodified
  applications.  The app would look up DNS and the stack would
  intercept the response, replacing the AAAA result with one
  created from the I and one or more R items.  The stack would give
  the application the resulting 128 bit IP address and the
  application would open a socket bound to that address.  Is this
  right?  A detailed example would be helpful.


  TCP needs to be changed to use only the lower 64 bits in its
  pseudo-header calculations.  But this changed behavior must only
  be implemented on sessions with other ILNP hosts.

  (P6) Each ILNP host is required to use Secure Dynamic DNS to
  update its I and L records in the DNS server which is authoritative
  for its FQDN.  As I noted earlier, this involves some potentially
  prohibitive security and administrative arrangements.  For instance,
  if the ILNP host is at a hosting company, and runs web sites for
  20 companies, it will need to have the authority to update the
  I and L records of its FQDN in the authoritative DNS servers of
  these 20 companies - which are not necessarily run by this hosting
  company.

  I know nothing about RFC 3007, but is it technically possible to
  give some remote host the credentials to do this update, and only
  this update, on a company's primary DNS server?

  There is also an option for CE routers changing the LOC bits of
  the source and destination addresses of outgoing packets, and for
  updating DNS to reflect these choices.  So now it is not just
  the host, but CE routers changing these things.  They need the
  credentials too.  It is not clear how the CE router tells the
  host of these changes.

  How can all these permissions be reliably and securely organised
  when someone walks into an end-user site and connects their own
  personal device (for instance a laptop computer) to the network,
  via cabled or wireless Ethernet?


  (P8) Localised addressing - how to handle packets sent between
  hosts in a site.  The split horizon DNS system sounds to me like a
  nightmare.  Are there any arguments to the contrary?  The
  alternative simpler in terms of DNS, but involves trickier and
  more expensive routing which I haven't yet fully understood.


  (P9) IPsec needs to be changed - so it has additional modes
  just for use with ILNP sessions.  Since applications can't
  know which sessions are ILNP or not, I guess the IPsec code
  has to know and behave accordingly.  The changes are not just
  to the packet handling code for AH and ESP, but to the
  key management code too.  This sounds very messy.

  DNS servers for any ILNP hosts need to be changed - but this
  wouldn't be too hard.  On page 10, there is mention of DNS
  servers creating an AAAA record (one or more?) for non-ILNP
  hosts automatically from the I and L records.


  (P10)  It is not at all clear how reverse DNS can be implemented.
  The reverse DNS is often administered by a completely different
  organisation than the ordinary DNS.

  In the case of a 2-ISP multihomed site, there would be two
  separate reverse DNS systems, one for each ISP.  How could
  they be updated every time a host changed its LOC bits -
  such as in a multihoming failure where one set formerly to
  be used should now not be used?  It is bad enough that the
  host has to securely update the DNS of its one or more
  FQDNs (a web-host company's hosts might have dozens or a
  hundred such FQDNs, each in a different customer company's
  DNS).  However, to update the reverse DNS system, each host would
  need to be able to securely update a subset of both ISP's reverse
  DNS system.

  How could all this authority be securely given to some guest host
  in an end-user network such as the phone or laptop connected
  temporarily via Wi-Fi?

  There needs to be very short or zero caching times for
  DNS queries for these FQDNs.  Otherwise, if a host changes
  its LOC bits, other hosts using DNS and trying to establish
  a session with this host will have stale information and
  will send packets to a non-functional address.

  This looks like it would dramatically increase the load on the
  entire DNS system.


  (P10 - 11) I am not sure how address referrals can work.

  Referrals occur at the application level and there is no
  DNS involvement.

  If host A is having an ILNP session with B, using LB upper
  64 bits and IB lower 64 bits, it gives these 128 bits to
  and application running on ILNP-capable C.  Assuming A is still
  reachable on this address when C sends packets to it, how is
  the stack in either C or A to know this is supposed to be an
  ILNP session?

  Would C recognise that this address for A was not it its
  ILNP-specific session cache and so generate a fresh nonce - sending
  Nonce Destination Options along with the initial packets?

  Clearly, referrals can't work if A is no longer available
  on this 128 bit address.  So multihoming can't work for
  referrals.  Hence the mention on page 11 of creating a new
  API, and modifying applications, so they can operate differently
  and avoid referrals.  But that involves changing applications,
  which raises probably the most prohibitive barriers imaginable
  to development and adoption.

  Multihoming only works between upgraded hosts anyway, so ILNP
  only provides its benefits (multihoming and perhaps inbound TE)
  to a very small fraction of sessions, on average, in the early
  days of deployment.



Additional DNS Resource Records
http://tools.ietf.org/html/draft-rja-ilnp-dns-01

  I understand how a 2 ISP multihomed host with I bits "zzzz"
  can work with two sets of L bits "xxxx" for the /64 of ISP
  1's address range where this host resides and likewise "yyyy" for
  ISP-2.

  A DNS query for its FQDN returns either "xxxx zzzz" or
  "yyyy zzzz" for the AAAA record (for non-ILNP hosts to use)
  and, for instance, giving priority to ISP 1:

    L (first of two)             xxxx     priority 1
    L (second of two)            yyyy     priority 2
    I                            zzzz     (priority any value)

  Conventional round-robin techniques enable the one DNS name to
  give out multiple AAAA addresses, spreading the load of sessions
  from multiple requesting hosts over multiple responding hosts.
  Since each AAAA address can be for any host on the Net, this
  enables the spreading of load over hosts in different networks.

  AFAIK, such round-robin techniques are not possible with ILNP.

  In the multihomed example above, (I guess) it would be possible to
  spread incoming sessions over the two links, for the one physical
  host, by setting both L priorities to the same value.

  However, suppose there was a need to spread the load over
  multiple physical hosts.  The only obvious approach would be to
  add a second I record "gggg", and give it the same priority as
  "zzzz".

  Then, there could be two physical hosts, both getting incoming
  sessions via both ISP links.  However, the two hosts need
  to be in the same end-user network.

  There seems to be no way of doing round-robin session sharing
  between physical hosts in separate networks with ILNP.

  How does the extra length of this new response information affect
  the ability to reply in a single packet?



ICMP Locator Update message
http://tools.ietf.org/html/draft-rja-ilnp-icmp-00

  I think it would be helpful to add that the authentication for
  this message is always provided by the Nonce Destination Option.

  This provides a new list of LOCs for the a host's ID address and
  nonce.

  Normally, it is sent by the host.  However, it could be sent
  by a CE router.  Would the CE router spoof the host's sending
  address?  (Then, the host gets any ICMP error messages - not
  the CE router.)  If CE routers are to do this, then I think the
  protocol needs to be extended to include the address of the
  host concerned.  Presumably the CE router would pick up the
  nonce from passing traffic.

  If this is sent by a CE router, as noted above, how does the CE
  router tell the host whose LOC addresses it has just updated in
  some remote correspondent host?

  Presumably this message overrides whatever the destination host
  has learned about LOCs and priorities from a DNS lookup, or from
  any previous such Update message.

  There appears to be no provision for acknowledging this message
  - yet there surely needs to be acknowledgement, since the
  message is so important that the sending host (or router)
  should persist in trying to get it through.




Nonce Destination Option
http://tools.ietf.org/html/draft-rja-ilnp-nonce-01

  The ILNP stack can add this Destination Option to any packet.

  The destination option may be 8 pr 20 bytes long.

  The application can't know that this is to be added, so I think
  the stack has to tell applications to always send packets at least
  20 bytes shorter than what could normally be carried according to
  the PMTUD limits of the path to the destination host.  This would
  seem to reduce the efficiency of many ILNP sessions.

  Also, I guess the RFC 1191 part of the stack would need to be
  aware of the presence or absence of this Header Option.


Tentative conclusion

  ILNP suffers from all the problems I noted about any proposal which
  pushes the responsibility for multihoming out to hosts.  It also
  does not provide portability.

  I am not sure how ACLs would work with ILNP's multiple addresses
  for each host.

  It offers early adopters very little incentive to use it, since
  multihoming only works with other upgraded networks.  Until
  essentially all hosts on the net are upgraded, it will not
  provide robust multihoming for all communications.

  In addition to upgrading host stacks, DNS servers needs to be
  changed and there will often need to be elaborate trust
  relationships established and managed between different
  organisations for multihoming to work.

  This is an "elimination" strategy, which could, in principle,
  remove the need for end-user networks to use PI addresses.  However
  all such networks need to be motivated to adopt this modified form
  of IPv6.

  Could DNS servers be multihomed in this fashion?  Wouldn't
  that require additional I and L information in responses from
  one request, which point to the address of another server to
  query next?

  There appears to be a scaling problem due to ILNP apparently
  requiring much more frequent requests to the authoritative DNS
  servers.

  The level of complexity seems to be minimal, with no actual
  cryptography - quite a contrast with crypto-laden HIP:

   http://infrahip.hiit.fi/index.php?index=how

  Unless reverse DNS is fully supported - and this does not seem to
  be discussed in detail in this I-Ds - then there is no mapping
  from a 64 bit ID to its one or more 64 bit LOCs.  There is only
  mapping from a FQDN to one ID with multiple LOCs - for multihoming.
  There appears to be no method of doing round-robin for multiple
  hosts in separate networks - which would be a major barrier to
  adoption for some end-user networks.







_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan  5 03:01:26 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C52173A6781;
	Mon,  5 Jan 2009 03:01:26 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 942423A6781
	for <rrg@core3.amsl.com>; Mon,  5 Jan 2009 03:01:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.825
X-Spam-Level: 
X-Spam-Status: No, score=-3.825 tagged_above=-999 required=5
	tests=[AWL=-0.064, BAYES_00=-2.599, RCVD_BAD_ID=2.837,
	RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id OcqGCuGrk4dc for <rrg@core3.amsl.com>;
	Mon,  5 Jan 2009 03:01:24 -0800 (PST)
Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.176.133])
	by core3.amsl.com (Postfix) with ESMTP id 0D9A73A63CB
	for <rrg@irtf.org>; Mon,  5 Jan 2009 03:01:23 -0800 (PST)
Received: from localhost (webcartero01.uc3m.es [163.117.136.131])by 
	smtp03.uc3m.es (Postfix) with ESMTP id 904F772B75E;Mon,  5 Jan 2009 
	12:01:06 +0100 (CET)
Received: from 
	r190-132-87-88.dialup.mobile.ancel.net.uy(r190-132-87-88.dialup.mobile.ance
	l.net.uy [190.132.87.88]) bywebcartero01.uc3m.es (Horde MIME library)
	with HTTP; Mon, 05 Jan 200912:01:04 +0100
Message-ID: <20090105120104.f4knjsaeqsgo0840@webcartero01.uc3m.es>
Date: Mon, 05 Jan 2009 12:01:04 +0100
From: MARCELO BAGNULO BRAUN <marcelo@it.uc3m.es>
To: William Herrin <bill@herrin.us>
References: <4959B44C.2030709@firstpr.com.au><4959C284.4060805@firstpr.com.a
	u> 
	<1230720711.5901.25.camel@localhost><495EF3B1.1030408@firstpr.com.au><20090
	103121825.co8r3bgpwkwwggk4@webcartero01.uc3m.es><495F770C.4070004@firstpr.c
	om.au><20090104145408.q0i0wpgtck48kssg@webcartero01.uc3m.es><49611727.50008
	06@gmail.com><3c3e3fca0901041944t53c7587g7a1e65a9a5777fac@mail.gmail.com>
In-Reply-To: <3c3e3fca0901041944t53c7587g7a1e65a9a5777fac@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
User-Agent: Internet Messaging Program (IMP) H3 (4.0.4)
X-imss-version: 2.051
X-imss-result: Passed
X-imss-scanInfo: M:B L:E SM:2
X-imss-tmaseResult: TT:1 TS:-7.9753 TC:1F TRN:29 TV:5.5.1026(16382.006)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
Cc: rrg@irtf.org
Subject: Re: [rrg] Remote ACLs [Proposals which match rrgarchitectures.html
	pls check the page]
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

William Herrin <bill@herrin.us> dijo:

>> On 2009-01-05 02:54, MARCELO BAGNULO BRAUN wrote:
>>>>  3 - Problems with maintaining ACLs in other networks for hosts
>>>>      using SHIM6.
>>> I don't understand this one
>
> Marcello,
>
> Shim6 has several weaknesses that can be revealed by comparing it to
> the Strategy B criteria. This particular weakness is the lack of
> accompanying dynamic source routing protocol.
>
> Unless the IGP in a stratgy B system moves packets first to a valid
> exit for the source address and only then to the optimal exit for the
> destination address, you end up with a nasty spoofing problem where
> routers require extensive manual configuration to tell the difference
> between a spoofed source address and a valid multiprefix source
> address.

but this is not specific to shim6, but it is s general problem of 
configuring multiple PA blocks from multiple ISPs that are performing 
ingress filtering.
I mean, if you don't have shim6 and you configure multiple PA prefixes, 
you end up in the same problem.
We have tried to address this problem in the shim6 wg, but the guidance 
was that this was a general problem that was to be addressed in general 
for IPv6, which hasn't been addressed yet

Also, note that Proxy Shim6 does not suffers from this problem, since 
the proxy rewrites the source address and can make it compliant with 
the filters

Regards, marcelo


>
> Regards,
> Bill Herrin
>
>
> --
> William D. Herrin ................ herrin@dirtside.com  bill@herrin.us
> 3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
> Falls Church, VA 22042-3004
>



-- 
----
MARCELO BAGNULO BRAUN
WebCartero
Universidad Carlos III de Madrid

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan  5 03:05:42 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1944B3A6870;
	Mon,  5 Jan 2009 03:05:42 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2BBE53A6870
	for <rrg@core3.amsl.com>; Mon,  5 Jan 2009 03:05:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.06
X-Spam-Level: 
X-Spam-Status: No, score=-5.06 tagged_above=-999 required=5 tests=[AWL=1.182, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_6CONS_WORD=0.356,
	UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id q6RXfadtCNFY for <rrg@core3.amsl.com>;
	Mon,  5 Jan 2009 03:05:40 -0800 (PST)
Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.176.133])
	by core3.amsl.com (Postfix) with ESMTP id 243A13A63CB
	for <rrg@irtf.org>; Mon,  5 Jan 2009 03:05:39 -0800 (PST)
Received: from localhost (webcartero01.uc3m.es [163.117.136.131])by 
	smtp03.uc3m.es (Postfix) with ESMTP id EB34B729E32for <rrg@irtf.org>;
	Mon, 5 Jan 2009 12:05:25 +0100 (CET)
Received: from 
	r190-132-87-88.dialup.mobile.ancel.net.uy(r190-132-87-88.dialup.mobile.ance
	l.net.uy [190.132.87.88]) bywebcartero01.uc3m.es (Horde MIME library)
	with HTTP; Mon, 05 Jan 200912:05:24 +0100
Message-ID: <20090105120524.hh0eyj0miskw8c08@webcartero01.uc3m.es>
Date: Mon, 05 Jan 2009 12:05:24 +0100
From: MARCELO BAGNULO BRAUN <marcelo@it.uc3m.es>
To: rrg@irtf.org
References: <20090104202055.946896BE56A@mercury.lcs.mit.edu>
In-Reply-To: <20090104202055.946896BE56A@mercury.lcs.mit.edu>
MIME-Version: 1.0
Content-Disposition: inline
User-Agent: Internet Messaging Program (IMP) H3 (4.0.4)
X-imss-version: 2.051
X-imss-result: Passed
X-imss-scanInfo: M:B L:E SM:2
X-imss-tmaseResult: TT:1 TS:-16.4673 TC:1F TRN:34 TV:5.5.1026(16382.006)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
Subject: Re: [rrg] Remote ACLs [Proposals which match rrg
	architectures.htmlpls check the page]
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Noel Chiappa <jnc@mercury.lcs.mit.edu> dijo:

>    > From: Brian E Carpenter <brian.e.carpenter@gmail.com>
>
>    > Isn't this in fact a (perceived) problem with the multi-prefix model?
>    > If an endpoint has multiple locators, then any site that puts one of
>    > those locators in an ACL needs to put all of them in the ACL.
>
> Why are people putting locators in ACLs anyway?

I guess that one of the problems with using identifier is how can you 
trust the idnetifiers in the packet?
I mean, if you include botht eh ID and the locator in the packet e.g. a 
tunnel, the source locator has some inherent security features, since 
it is the token that will be used by the routing system to send packets 
back, so spoofing it will result in retrun packet going somewhere else.
The identifier does not have such property and spoofing it is trivial.
I guess that if we want to use identifiers in the ACL and make them 
minimally useful, the device holding the ACL needs to verify the ID loc 
mapping, which seems somehow more complex than current practice.

Regards, marcelo

>
> (Note: This is not the same thing as the question 'why is the hardware
> looking at locators to implement ACLs?'. Looking at locators might be a fine
> engineering choice for the _implementation_ of ACLs.)
>
> 	Noel
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> https://www.irtf.org/mailman/listinfo/rrg
>



-- 
----
MARCELO BAGNULO BRAUN
WebCartero
Universidad Carlos III de Madrid

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan  5 05:36:44 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 026E03A6868;
	Mon,  5 Jan 2009 05:36:44 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 754C03A6868
	for <rrg@core3.amsl.com>; Mon,  5 Jan 2009 05:36:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.521
X-Spam-Level: 
X-Spam-Status: No, score=-6.521 tagged_above=-999 required=5 tests=[AWL=0.079, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id GNvjWtUoqLRF for <rrg@core3.amsl.com>;
	Mon,  5 Jan 2009 05:36:42 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86])
	by core3.amsl.com (Postfix) with ESMTP id D1D4C3A67A5
	for <rrg@irtf.org>; Mon,  5 Jan 2009 05:36:42 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.36,332,1228089600"; d="scan'208";a="27315374"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-4.cisco.com with ESMTP; 05 Jan 2009 13:36:16 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n05DaGZG030794; 
	Mon, 5 Jan 2009 05:36:16 -0800
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id n05DaG5R004354;
	Mon, 5 Jan 2009 13:36:16 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Jan 2009 08:36:15 -0500
Received: from sbrim-mbp.local.cisco.com ([64.102.8.172]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Jan 2009 08:36:15 -0500
MIME-Version: 1.0
Message-ID: <18786.3278.670093.505832@sbrim-mbp.local>
Date: Mon, 5 Jan 2009 08:36:14 -0500
From: Scott Brim <swb@employees.org>
To: Dan Jen <jenster@cs.ucla.edu>
In-Reply-To: <1230690036.5700.7.camel@localhost>
References: <4959B44C.2030709@firstpr.com.au>
	<885A118B-76C8-4E8D-91C0-7C5C6996784F@cs.colostate.edu>
	<4959C284.4060805@firstpr.com.au>
	<1230690036.5700.7.camel@localhost>
X-Mailer: VM 8.0.12 under 22.2.1 (i386-apple-darwin9.2.2)
X-OriginalArrivalTime: 05 Jan 2009 13:36:15.0177 (UTC)
	FILETIME=[94C93390:01C96F3A]
Authentication-Results: sj-dkim-1; header.From=swb@employees.org; dkim=neutral
Cc: RRG <rrg@irtf.org>, Robin Whittle <rw@firstpr.com.au>
Subject: Re: [rrg] Proposals which match rrgarchitectures.html
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Excerpts from Dan Jen at 18:20:36 -0800 on Tue 30 Dec 2008:
> None of the A2s fit APT exactly.

Let's get away from trying to compare entire _packages_ and instead
look at functional components.  Whether APT fits a particular approach
isn't as important as whether APT's pieces do.  When we know which
approaches we prefer, we select building blocks to put them together.
Let's not get trapped arguing about packages.

Scott (back at work)
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan  5 06:13:21 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 356F13A686B;
	Mon,  5 Jan 2009 06:13:21 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9AFA23A6868
	for <rrg@core3.amsl.com>; Mon,  5 Jan 2009 06:13:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.564
X-Spam-Level: 
X-Spam-Status: No, score=-1.564 tagged_above=-999 required=5 tests=[AWL=0.331, 
	BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id TRiHBWkJN3wA for <rrg@core3.amsl.com>;
	Mon,  5 Jan 2009 06:13:19 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123])
	by core3.amsl.com (Postfix) with ESMTP id 699E93A67AB
	for <rrg@irtf.org>; Mon,  5 Jan 2009 06:13:19 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6])
	by gair.firstpr.com.au (Postfix) with ESMTP id 1F2F1175B14;
	Tue,  6 Jan 2009 01:13:05 +1100 (EST)
Message-ID: <49621571.2020107@firstpr.com.au>
Date: Tue, 06 Jan 2009 01:13:05 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: RRG <rrg@irtf.org>
References: <4959B44C.2030709@firstpr.com.au>	<885A118B-76C8-4E8D-91C0-7C5C6996784F@cs.colostate.edu>	<4959C284.4060805@firstpr.com.au>	<1230690036.5700.7.camel@localhost>
	<18786.3278.670093.505832@sbrim-mbp.local>
In-Reply-To: <18786.3278.670093.505832@sbrim-mbp.local>
Subject: Re: [rrg] Proposals which match rrgarchitectures.html
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Hi Scott,

You wrote:

>> None of the A2s fit APT exactly.
> 
> Let's get away from trying to compare entire _packages_ and instead
> look at functional components.  Whether APT fits a particular approach
> isn't as important as whether APT's pieces do.  When we know which
> approaches we prefer, we select building blocks to put them together.
> Let's not get trapped arguing about packages.

While I think it is interesting to break down a proposal into it's
various distinctive functional blocks - especially when contemplating
how to improve this or other proposals - ultimately, I believe it
will be complete, carefully designed, proposals which have the best
chance of solving the scaling problem.

It is no good trying to build a car from a collection of GM and Ford
parts - they will never fit together as well as a car made with a
unified design, so all the components are combined to maximise
synergy between the various sub-systems.

I think it is valuable that Bill's page attempts to identify
commonalities and distinctions between the various approaches to
designing a new architecture.

An important test of Bill's taxonomy of architectural design
approaches is whether all the major, real, live proposals actually
fit clearly within it.

If Bill's page isn't updated to the point where the designers of APT
and ILNP are happy that there is a place in the taxonomy for their
designs, then I think the taxonomy would be only a loose and somewhat
misleading account of the actual design choices which are available.

I think it would be best if the designers suggest changes to Bill's
taxonomy - specific words to modify the current Strategies, or to
create new ones.  I did this with Ivip, and Bill used a subset of
what I suggested.

While the taxonomy doesn't consider a number of architectural aspects
which I think are important distinctions between Ivip and other
proposals, at least Ivip has a place in Bill's taxonomy, as does
LISP-ALT, TRRP and LISP-NERD.

 - Robin

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan  5 06:15:45 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 780C53A6868;
	Mon,  5 Jan 2009 06:15:45 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1567F3A67AB
	for <rrg@core3.amsl.com>; Mon,  5 Jan 2009 06:15:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.487
X-Spam-Level: 
X-Spam-Status: No, score=-6.487 tagged_above=-999 required=5 tests=[AWL=0.112, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 8I0C6bdsnWz8 for <rrg@core3.amsl.com>;
	Mon,  5 Jan 2009 06:15:43 -0800 (PST)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163])
	by core3.amsl.com (Postfix) with ESMTP id 321A43A67AF
	for <rrg@irtf.org>; Mon,  5 Jan 2009 06:15:43 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by
	exprod7ob105.postini.com ([64.18.6.12]) with SMTP
	ID DSNKSWIV/7kOiP7aRlkaokSrJlNpXMN7axTp@postini.com;
	Mon, 05 Jan 2009 06:15:31 PST
Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net
	(172.24.192.35) with Microsoft SMTP Server id 8.1.336.0;
	Mon, 5 Jan 2009 06:13:22 -0800
Received: from p-emlb01-sac.jnpr.net ([66.129.254.46]) by
	p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959);
	Mon, 5 Jan 2009 06:13:22 -0800
Received: from emailsmtp56.jnpr.net ([172.24.60.77]) by p-emlb01-sac.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.3959); Mon, 5 Jan 2009 06:13:22 -0800
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.3959); Mon, 5 Jan 2009 06:13:22 -0800
Received: from juniper.net (sapphire.juniper.net [172.17.28.108])	by
	magenta.juniper.net (8.11.3/8.11.3) with ESMTP id n05EDMM80111;
	Mon, 5 Jan
	2009 06:13:22 -0800 (PST)	(envelope-from yakov@juniper.net)
Message-ID: <200901051413.n05EDMM80111@magenta.juniper.net>
To: Robin Whittle <rw@firstpr.com.au>
In-Reply-To: <49601D0B.6040803@firstpr.com.au> 
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com>
	<87D9F0BA2807456A88B0427241A29F65@ad.redback.com>
	<3c3e3fca0901021219t2ab35dfsb2532e0c89be84af@mail.gmail.com>
	<E99E41EB33084B5B899C7EED9DE607E9@ad.redback.com>
	<3c3e3fca0901021334j22d17e54iec4bbf41b6c00480@mail.gmail.com>
	<BCFF32A1356842BF839C7DF7D059F15F@ad.redback.com>
	<3c3e3fca0901031320o1253fcd3s3b6597aef77fba33@mail.gmail.com>
	<A071B6FF07CD4B708EC6CA2B9938096D@ad.redback.com>
	<3c3e3fca0901031720w602d931ev42707b169f51fba9@mail.gmail.com>
	<49601D0B.6040803@firstpr.com.au>
X-MH-In-Reply-To: Robin Whittle <rw@firstpr.com.au>
	message dated "Sun, 04 Jan 2009 13:20:59 +1100."
MIME-Version: 1.0
Content-ID: <54993.1231164802.1@juniper.net>
Date: Mon, 5 Jan 2009 06:13:22 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-OriginalArrivalTime: 05 Jan 2009 14:13:22.0027 (UTC)
	FILETIME=[C4178BB0:01C96F3F]
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Robin,


> I expect this rate of growth will increase in the next few years as
> IPv4 space is subdivided more intensively once the last of the fresh
> pastures at the edge of town are engulfed.
> 
> I think there is little point in discussing whether DRAM speeds, CPU
> speeds etc. can cope with the current rate of growth in the DFZ in
> the long term.
> 
> In the long term, we need to enhance the architecture of the Net to
> cope happily with a much larger growth in the numbers of end-user
> networks which have multihoming, TE and portability.

Some folks think that the (large) majority of users will be mobile
devices. If that is indeed the case, then one should ask whether
the current solution for supporting host mobility (Mobile IP) is
viewed as adequate for this scenario. As if not, then enhancing the
architecture without taking into account the need to provide an
adequate support for a (very) large number of mobile hosts would
be rather myopic.
 
Yakov.
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan  5 06:21:25 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4803E3A67AB;
	Mon,  5 Jan 2009 06:21:25 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B338C3A67AB
	for <rrg@core3.amsl.com>; Mon,  5 Jan 2009 06:21:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.49
X-Spam-Level: 
X-Spam-Status: No, score=-6.49 tagged_above=-999 required=5 tests=[AWL=0.109, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id IoBZzvAUMz3A for <rrg@core3.amsl.com>;
	Mon,  5 Jan 2009 06:21:23 -0800 (PST)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171])
	by core3.amsl.com (Postfix) with ESMTP id E02CB3A657C
	for <rrg@irtf.org>; Mon,  5 Jan 2009 06:21:22 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by
	exprod7ob109.postini.com ([64.18.6.12]) with SMTP
	ID DSNKSWIXVDZVsakEmpE1O3/zDpBaF5y9UCJh@postini.com;
	Mon, 05 Jan 2009 06:21:10 PST
Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net
	(172.24.192.35) with Microsoft SMTP Server id 8.1.336.0;
	Mon, 5 Jan 2009 06:18:02 -0800
Received: from p-emlb01-sac.jnpr.net ([66.129.254.46]) by
	p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959);
	Mon, 5 Jan 2009 06:18:02 -0800
Received: from emailsmtp56.jnpr.net ([172.24.60.77]) by p-emlb01-sac.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.3959); Mon, 5 Jan 2009 06:18:01 -0800
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.3959); Mon, 5 Jan 2009 06:18:01 -0800
Received: from juniper.net (sapphire.juniper.net [172.17.28.108])	by
	magenta.juniper.net (8.11.3/8.11.3) with ESMTP id n05EI1M81833;
	Mon, 5 Jan
	2009 06:18:01 -0800 (PST)	(envelope-from yakov@juniper.net)
Message-ID: <200901051418.n05EI1M81833@magenta.juniper.net>
To: Robin Whittle <rw@firstpr.com.au>
In-Reply-To: <49601D0B.6040803@firstpr.com.au> 
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com>
	<87D9F0BA2807456A88B0427241A29F65@ad.redback.com>
	<3c3e3fca0901021219t2ab35dfsb2532e0c89be84af@mail.gmail.com>
	<E99E41EB33084B5B899C7EED9DE607E9@ad.redback.com>
	<3c3e3fca0901021334j22d17e54iec4bbf41b6c00480@mail.gmail.com>
	<BCFF32A1356842BF839C7DF7D059F15F@ad.redback.com>
	<3c3e3fca0901031320o1253fcd3s3b6597aef77fba33@mail.gmail.com>
	<A071B6FF07CD4B708EC6CA2B9938096D@ad.redback.com>
	<3c3e3fca0901031720w602d931ev42707b169f51fba9@mail.gmail.com>
	<49601D0B.6040803@firstpr.com.au>
X-MH-In-Reply-To: Robin Whittle <rw@firstpr.com.au>
	message dated "Sun, 04 Jan 2009 13:20:59 +1100."
MIME-Version: 1.0
Content-ID: <55064.1231165081.1@juniper.net>
Date: Mon, 5 Jan 2009 06:18:01 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-OriginalArrivalTime: 05 Jan 2009 14:18:01.0520 (UTC)
	FILETIME=[6AAECB00:01C96F40]
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Robin,

> The current system is unacceptable since it doesn't fit the needs of
> many end-user networks.  

The current system is *acceptable* to a very large number of users - for
number of users for whom the current system is acceptable just count
the number of users in the Internet.

Yakov.
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan  5 07:12:39 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C823E28B23E;
	Mon,  5 Jan 2009 07:12:39 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8F0FF28B23E
	for <rrg@core3.amsl.com>; Mon,  5 Jan 2009 07:12:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.492
X-Spam-Level: 
X-Spam-Status: No, score=-6.492 tagged_above=-999 required=5 tests=[AWL=0.107, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id jF+xc7LkTcTj for <rrg@core3.amsl.com>;
	Mon,  5 Jan 2009 07:12:37 -0800 (PST)
Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155])
	by core3.amsl.com (Postfix) with ESMTP id 688453A6AF1
	for <rrg@irtf.org>; Mon,  5 Jan 2009 07:12:36 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by
	exprod7ob101.postini.com ([64.18.6.12]) with SMTP
	ID DSNKSWIjUU1dUFjVenZzR5U714ckKts5TELv@postini.com;
	Mon, 05 Jan 2009 07:12:25 PST
Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net
	(172.24.192.35) with Microsoft SMTP Server id 8.1.336.0;
	Mon, 5 Jan 2009 07:09:50 -0800
Received: from p-emlb01-sac.jnpr.net ([66.129.254.46]) by
	p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959);
	Mon, 5 Jan 2009 07:09:50 -0800
Received: from emailsmtp56.jnpr.net ([172.24.60.77]) by p-emlb01-sac.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.3959); Mon, 5 Jan 2009 07:09:50 -0800
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.3959); Mon, 5 Jan 2009 07:09:49 -0800
Received: from juniper.net (sapphire.juniper.net [172.17.28.108])	by
	magenta.juniper.net (8.11.3/8.11.3) with ESMTP id n05F9nM02828;
	Mon, 5 Jan
	2009 07:09:49 -0800 (PST)	(envelope-from yakov@juniper.net)
Message-ID: <200901051509.n05F9nM02828@magenta.juniper.net>
To: tony.li@tony.li
In-Reply-To: <354C0AE786D1424C886C4A3570611291@ad.redback.com> 
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com><87D9F0BA2807456A88B0427241A29F65@ad.redback.com><3c3e3fca0901021219t2ab35dfsb2532e0c89be84af@mail.gmail.com><E99E41EB33084B5B899C7EED9DE607E9@ad.redback.com><3c3e3fca0901021334j22d17e54iec4bbf41b6c00480@mail.gmail.com>
	<BCFF32A1356842BF839C7DF7D059F15F@ad.redback.com>
	<3525C9833C09ED418C6FD6CD9514668C0566045E@emailwf1.jnpr.net>
	<354C0AE786D1424C886C4A3570611291@ad.redback.com>
X-MH-In-Reply-To: "Tony Li" <tony.li@tony.li>
	message dated "Sat, 03 Jan 2009 13:38:43 -0800."
MIME-Version: 1.0
Content-ID: <57022.1231168188.1@juniper.net>
Date: Mon, 5 Jan 2009 07:09:49 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-OriginalArrivalTime: 05 Jan 2009 15:09:49.0597 (UTC)
	FILETIME=[A73DB4D0:01C96F47]
Cc: 'RRG' <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Tony,

> Hi Ross,
> 
> |> We already know that we're growing the table faster than technology
> |> can keep up.  That much is clear. (Tony Li)
> |
> |First the question: What do you mean by "we're growing the table faster
> |than technology can keep up". Are you referring to Forwarding Table
> |size, BGP processing and traffic loads, or something else?
> 
> 
> I'm referring to the growth rate of the full set of prefixes and the
> capabilities of the control plane to support it.
> 
> Note that I've been saying this pretty consistently for two full years now.
> 
> |Do you mean
> |"with a table of 100,000,000 entries, there will need to be at 
> |a minimum
> |some incremental update to existing deployed implementations" (to which
> |my teenage daughter might say "duh!"), or do you mean "it won't be
> |economically reasonable to build products unless we make some localized
> |internal (within a router) change to a few algorithms?", or do you mean
> |"it will be financially too expensive to build products that can handle
> |some future table size", or do you mean "it will not be technically
> |possible to build the routers", or do you mean something else? 
> 
> 
> Once again, with feeling:
> 
> The growth rate of prefixes that are circulating within the DFZ exceeds the
> rate of speed improvement in the underlying DRAM that we use to implement
> the control plane.  This will undoubtedly result in architectural changes
> and cost increases.  The concern then becomes that over the long term, as
> this continues, the cost increases must be absorbed somewhere in the system,
> and it is most likely to propagate to the end users, with a net detriment to
> the growth of the network.

Few points:

 - The above assumes that DRAM will continue to be used to implement control 
   plane memory. As had been discussed before on this list, DRAM is not the 
   only option  - another alternative is RLDRAM. 

 - Even if one assumes that the growth rate of prefixes exceeds the
   rate of speed improvements in the underlying DRAM that is used to
   implement control plane, and that, in turn, would result in cost
   increases, let's not forget that deploying new routing architecture
   may have its own cost, thus resulting in cost increases. Moreover,
   these increases may be higher relative to what would result from
   the growth rate of prefixes exceeding the rate of speed improvements
   in the underlying DRAM.

   These increases, just like the increases you mentioned above,
   would need to be absorbed by the system, and "most likely to
   propagate to the end users, with a net detriment to the growth
   of the network".  Moreover, these increases would need to be
   absorbed by the system in the short/medium term, well before we
   will reach "the promise" of the cost reduction in the *long
   term*. Would the industry be willing to buy into the *promise* of
   "a paradise" in the *long* term at the price of fairly certain
   cost increases in the *short/medium* term ? 

   All of the above means that a "promise" of cost reduction in the
   *long* term may not be sufficient - the new routing architecture
   needs to deliver in the *short/medium* term sufficient *tangible*
   benefits to justify its *short/medium* term cost.

 - One may argue that the real problem is not in the cost increases,
   but in the way how these increases are absorbed by the system.
   Namely, the real problem is that those who do not benefit
   are still required to pay for covering the cost imposed by those
   who do benefit. That applies both to the current system, as well 
   as to any proposal for a new routing architecture.

Yakov.
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan  5 08:48:30 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 71B8F3A6A3A;
	Mon,  5 Jan 2009 08:48:30 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A6A493A6A3A
	for <rrg@core3.amsl.com>; Mon,  5 Jan 2009 08:48:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.132
X-Spam-Level: 
X-Spam-Status: No, score=-9.132 tagged_above=-999 required=5 tests=[AWL=1.467, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id QvjlVdqWTQLu for <rrg@core3.amsl.com>;
	Mon,  5 Jan 2009 08:48:28 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 154D13A689E
	for <rrg@irtf.org>; Mon,  5 Jan 2009 08:48:27 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.36,332,1228089600"; d="scan'208";a="30090977"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 05 Jan 2009 16:48:10 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n05GmAkW003107; 
	Mon, 5 Jan 2009 17:48:10 +0100
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
	[144.254.231.87])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n05GmAdt006009;
	Mon, 5 Jan 2009 16:48:10 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Jan 2009 17:48:10 +0100
Received: from adsl-247-5-fixip.tiscali.ch ([10.61.97.61]) by
	xfe-ams-332.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Jan 2009 17:48:09 +0100
Message-ID: <496239BC.5070606@cisco.com>
Date: Mon, 05 Jan 2009 17:47:56 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US;
	rv:1.9.1b3pre) Gecko/20081221 Shredder/3.0b2pre
MIME-Version: 1.0
To: Yakov Rekhter <yakov@juniper.net>
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com><87D9F0BA2807456A88B0427241A29F65@ad.redback.com><3c3e3fca0901021219t2ab35dfsb2532e0c89be84af@mail.gmail.com><E99E41EB33084B5B899C7EED9DE607E9@ad.redback.com><3c3e3fca0901021334j22d17e54iec4bbf41b6c00480@mail.gmail.com>	<BCFF32A1356842BF839C7DF7D059F15F@ad.redback.com>	<3525C9833C09ED418C6FD6CD9514668C0566045E@emailwf1.jnpr.net>	<354C0AE786D1424C886C4A3570611291@ad.redback.com>
	<200901051509.n05F9nM02828@magenta.juniper.net>
In-Reply-To: <200901051509.n05F9nM02828@magenta.juniper.net>
X-OriginalArrivalTime: 05 Jan 2009 16:48:09.0417 (UTC)
	FILETIME=[63CECB90:01C96F55]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=5122; t=1231174090;
	x=1232038090; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=lear@cisco.com;
	z=From:=20Eliot=20Lear=20<lear@cisco.com>
	|Subject:=20Re=3A=20[rrg]=20BGP=20scaling=20limit? |Sender:=20;
	bh=qIgZIoZ9duOLyPGIBYZL2LUnNA8PCDq/Y3IQbA9pUlo=;
	b=HpRcljN+XH/cGYiL6I+bF2AeQN6KaSyykVbRvBW4zbiQK7TdIdmb2ZLHSx
	HlgNE9diGRaQPYKbsE0FvOub+uEOJC/VitarqSZTq+YmX/UxacsAiX42uZ9o
	lfLVg1z6lA;
Authentication-Results: ams-dkim-1; header.From=lear@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Cc: 'RRG' <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On 1/5/09 4:09 PM, Yakov Rekhter wrote:
> Tony,
>
>    
>> Hi Ross,
>>
>> |>  We already know that we're growing the table faster than technology
>> |>  can keep up.  That much is clear. (Tony Li)
>> |
>> |First the question: What do you mean by "we're growing the table faster
>> |than technology can keep up". Are you referring to Forwarding Table
>> |size, BGP processing and traffic loads, or something else?
>>
>>
>> I'm referring to the growth rate of the full set of prefixes and the
>> capabilities of the control plane to support it.
>>
>> Note that I've been saying this pretty consistently for two full years now.
>>
>> |Do you mean
>> |"with a table of 100,000,000 entries, there will need to be at
>> |a minimum
>> |some incremental update to existing deployed implementations" (to which
>> |my teenage daughter might say "duh!"), or do you mean "it won't be
>> |economically reasonable to build products unless we make some localized
>> |internal (within a router) change to a few algorithms?", or do you mean
>> |"it will be financially too expensive to build products that can handle
>> |some future table size", or do you mean "it will not be technically
>> |possible to build the routers", or do you mean something else?
>>
>>
>> Once again, with feeling:
>>
>> The growth rate of prefixes that are circulating within the DFZ exceeds the
>> rate of speed improvement in the underlying DRAM that we use to implement
>> the control plane.  This will undoubtedly result in architectural changes
>> and cost increases.  The concern then becomes that over the long term, as
>> this continues, the cost increases must be absorbed somewhere in the system,
>> and it is most likely to propagate to the end users, with a net detriment to
>> the growth of the network.
>>      
>
> Few points:
>
>   - The above assumes that DRAM will continue to be used to implement control
>     plane memory. As had been discussed before on this list, DRAM is not the
>     only option  - another alternative is RLDRAM.
>    

So in other words, Tony should have said "architectural changes OR cost 
increases".  My recollection was that when the workshop happened, one of 
the key points was that we were not going to drop dead tomorrow, but 
simply ride the bleeding edge into oblivion as costs go up and up.  Now 
I know nothing about RLDRAM, but I'll hazard a guess that it is at least 
for now more expensive than DRAM.

>   - Even if one assumes that the growth rate of prefixes exceeds the
>     rate of speed improvements in the underlying DRAM that is used to
>     implement control plane, and that, in turn, would result in cost
>     increases, let's not forget that deploying new routing architecture
>     may have its own cost, thus resulting in cost increases. Moreover,
>     these increases may be higher relative to what would result from
>     the growth rate of prefixes exceeding the rate of speed improvements
>     in the underlying DRAM.
>    

Yes, the intersection of engineering and architecture is when you 
actually have to make design choices that require use of a crystal ball.

>     These increases, just like the increases you mentioned above,
>     would need to be absorbed by the system, and "most likely to
>     propagate to the end users, with a net detriment to the growth
>     of the network".

I'm not convinced the two statements follow.  If the cost is a change in 
failure mode behavior, with associated mitigation techniques, perhaps 
there's a considerable net gain?  Early results with LISP show precisely 
this.  And we've discussed this before, so why are we looping?  If this 
is really an RG, let's not do that.


>    Moreover, these increases would need to be
>     absorbed by the system in the short/medium term, well before we
>     will reach "the promise" of the cost reduction in the *long
>     term*. Would the industry be willing to buy into the *promise* of
>     "a paradise" in the *long* term at the price of fairly certain
>     cost increases in the *short/medium* term ?
>
>     All of the above means that a "promise" of cost reduction in the
>     *long* term may not be sufficient - the new routing architecture
>     needs to deliver in the *short/medium* term sufficient *tangible*
>     benefits to justify its *short/medium* term cost.
>
>    
To restate, vague generalities are not helpful.

>   - One may argue that the real problem is not in the cost increases,
>     but in the way how these increases are absorbed by the system.
>     Namely, the real problem is that those who do not benefit
>     are still required to pay for covering the cost imposed by those
>     who do benefit. That applies both to the current system, as well
>     as to any proposal for a new routing architecture.
>    

Absolutely proven with BGP.  Do we have enough of an understanding of 
all proposals to make such sweeping statements?  Perhaps you could take 
us through that work and in particular specific value chain shifts and 
failures?

Eliot


_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan  5 08:54:37 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1B2893A6849;
	Mon,  5 Jan 2009 08:54:37 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 700A53A6849
	for <rrg@core3.amsl.com>; Mon,  5 Jan 2009 08:54:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.421
X-Spam-Level: 
X-Spam-Status: No, score=-6.421 tagged_above=-999 required=5
	tests=[AWL=-0.178, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	SARE_SUB_6CONS_WORD=0.356]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id xv4+hYVT9hi0 for <rrg@core3.amsl.com>;
	Mon,  5 Jan 2009 08:54:34 -0800 (PST)
Received: from virtualized.org (trantor.virtualized.org [204.152.189.190])
	by core3.amsl.com (Postfix) with ESMTP id B840D3A67DA
	for <rrg@irtf.org>; Mon,  5 Jan 2009 08:54:34 -0800 (PST)
Received: from wlan39-077.mdr.icann.org (wlan39-077.mdr.icann.org
	[192.0.39.77])
	by virtualized.org (Postfix) with ESMTP id EB477413931;
	Mon,  5 Jan 2009 08:53:56 -0800 (PST)
Message-Id: <3B101E43-106C-4B31-A943-B5F7AD1EA995@virtualized.org>
From: David Conrad <drc@virtualized.org>
To: Dino Farinacci <dino@cisco.com>
In-Reply-To: <417CE10E-C5DE-4825-B250-42F6751112EC@cisco.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Mon, 5 Jan 2009 08:53:55 -0800
References: <000c01c96ed2$73fa70b0$670c6f0a@china.huawei.com>
	<417CE10E-C5DE-4825-B250-42F6751112EC@cisco.com>
X-Mailer: Apple Mail (2.930.3)
Cc: RRG RG <rrg@irtf.org>
Subject: Re: [rrg] Remote ACLs [Proposals which match
	rrg	architectures.htmlpls check the page]
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Dino,

On Jan 4, 2009, at 5:19 PM, Dino Farinacci wrote:
>> If we want to use ID in the ACL, should it also have some structure  
>> in
>> semantics? since the flat ID will cause a scaling issue with ACL  
>> and a huge
>> burden for manually configuration.
> If EID-prefixes are allocated from RIRs, we can have structure.

Depends on the allocation rules for EIDs, which obviously don't exist  
now.  Right now, the RIRs try to juggle conservation of address space  
with conservation of 'routing slots' with a bias towards the latter,  
resulting in allocations of power-of-2 size blocks aligned on CIDR  
boundaries.  If the RIRs were to allocate EIDs, they would not need to  
be concerned about conservation of 'routing slots', hence non-CIDR  
aligned and non-power-of-2 blocks can be allocated.  If this isn't  
what people want, the RIR public policy process would have to be  
engaged to come up with the EID allocation rules.

Regards,
-drc

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan  5 09:37:10 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C15A93A68CD;
	Mon,  5 Jan 2009 09:37:10 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 51A2F3A68CD
	for <rrg@core3.amsl.com>; Mon,  5 Jan 2009 09:37:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.355
X-Spam-Level: 
X-Spam-Status: No, score=-6.355 tagged_above=-999 required=5
	tests=[AWL=-0.112, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	SARE_SUB_6CONS_WORD=0.356]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id J3SER+JKugLX for <rrg@core3.amsl.com>;
	Mon,  5 Jan 2009 09:37:09 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 5BAF83A67E2
	for <rrg@irtf.org>; Mon,  5 Jan 2009 09:37:09 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.36,332,1228089600"; d="scan'208";a="224043971"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 05 Jan 2009 17:36:56 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n05Haudh031277; 
	Mon, 5 Jan 2009 09:36:56 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n05HauiL019099;
	Mon, 5 Jan 2009 17:36:56 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Jan 2009 09:36:55 -0800
Received: from [192.168.7.124] ([10.21.72.30]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Jan 2009 09:36:55 -0800
Message-Id: <DB736143-9A90-42C0-8518-CC6782FB071D@cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: David Conrad <drc@virtualized.org>
In-Reply-To: <3B101E43-106C-4B31-A943-B5F7AD1EA995@virtualized.org>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Mon, 5 Jan 2009 09:36:55 -0800
References: <000c01c96ed2$73fa70b0$670c6f0a@china.huawei.com>
	<417CE10E-C5DE-4825-B250-42F6751112EC@cisco.com>
	<3B101E43-106C-4B31-A943-B5F7AD1EA995@virtualized.org>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 05 Jan 2009 17:36:55.0423 (UTC)
	FILETIME=[33D7E0F0:01C96F5C]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1150; t=1231177016;
	x=1232041016; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dino@cisco.com;
	z=From:=20Dino=20Farinacci=20<dino@cisco.com>
	|Subject:=20Re=3A=20[rrg]=20Remote=20ACLs=20[Proposals=20wh
	ich=20match=20rrg=09architectures.htmlpls=20check=20the=20pa
	ge] |Sender:=20;
	bh=SieK6wNBoBClCTbBrdegJr98+T6rPb62gECCanoSEps=;
	b=M0IfSYocCs9x9xwj1o1f+TATP9JGmNC6HHZSMLA41IlSWQbiN6/uQg8eWT
	TIOBusmsVEwIKIeMZAy8c9QESsPBRV/qYuQb2akk7RN96fgbvC177fR/5E5Q
	rokJkW6RjP;
Authentication-Results: sj-dkim-3; header.From=dino@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: RRG RG <rrg@irtf.org>
Subject: Re: [rrg] Remote ACLs [Proposals which match
	rrg	architectures.htmlpls check the page]
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

So don't you think the decoupling is a good thing? I can see benefits.

Dino

On Jan 5, 2009, at 8:53 AM, David Conrad wrote:

> Dino,
>
> On Jan 4, 2009, at 5:19 PM, Dino Farinacci wrote:
>>> If we want to use ID in the ACL, should it also have some  
>>> structure in
>>> semantics? since the flat ID will cause a scaling issue with ACL  
>>> and a huge
>>> burden for manually configuration.
>> If EID-prefixes are allocated from RIRs, we can have structure.
>
> Depends on the allocation rules for EIDs, which obviously don't  
> exist now.  Right now, the RIRs try to juggle conservation of  
> address space with conservation of 'routing slots' with a bias  
> towards the latter, resulting in allocations of power-of-2 size  
> blocks aligned on CIDR boundaries.  If the RIRs were to allocate  
> EIDs, they would not need to be concerned about conservation of  
> 'routing slots', hence non-CIDR aligned and non-power-of-2 blocks  
> can be allocated.  If this isn't what people want, the RIR public  
> policy process would have to be engaged to come up with the EID  
> allocation rules.
>
> Regards,
> -drc
>

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan  5 09:41:07 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2E3A43A68EF;
	Mon,  5 Jan 2009 09:41:07 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 025B93A67D6
	for <rrg@core3.amsl.com>; Mon,  5 Jan 2009 09:41:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id r32SnBj1p6NP for <rrg@core3.amsl.com>;
	Mon,  5 Jan 2009 09:41:05 -0800 (PST)
Received: from n2.nomadiclab.com (n2.nomadiclab.com
	[IPv6:2001:14b8:400:101::2])
	by core3.amsl.com (Postfix) with ESMTP id E8B483A68EF
	for <rrg@irtf.org>; Mon,  5 Jan 2009 09:41:04 -0800 (PST)
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 23C3D1EF12C;
	Mon,  5 Jan 2009 19:40:50 +0200 (EET)
Received: from [127.0.0.1] (localhost [IPv6:::1])
	by n2.nomadiclab.com (Postfix) with ESMTP id A2ED31EF125;
	Mon,  5 Jan 2009 19:40:49 +0200 (EET)
Message-Id: <D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com>
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
To: Robin Whittle <rw@firstpr.com.au>
In-Reply-To: <4961CFD3.2050304@firstpr.com.au>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Mon, 5 Jan 2009 19:40:49 +0200
References: <495F0BAA.2040303@firstpr.com.au> <49611E83.8050301@gmail.com>
	<4961CFD3.2050304@firstpr.com.au>
X-Mailer: Apple Mail (2.930.3)
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

>>>               HIP has been mentioned, but no-one seems to be
>>>               proposing it as a scalable routing solution.
>>
>> I think Pekka observed that this wasn't even a goal. (My quick answer
>> is that it only becomes a routing solution if it solves the same
>> mapping problem that strategy A generates.)
>
> I don't understand your comment, but if the HIP proponents do not see
> it as a solution to the routing scaling problem, then unless someone
> on the RRG feels strongly that it is, then HIP is out of scope for
> discussion and for matching against any of Bill's architectures.

To clarify what I have already stated:  As far as I can see, HIP was  
never meant to be a solution to the RRG problem (HIP started in 1999,  
RRG around 2006 IIRC).  HIP is an architectural change, and its  
official IETF status is, if I understand correctly, "ongoing  
experiment".  People are encouraged to run HIP in the Internet and  
report any experiences to the HIP-RG.  There are open source  
implementations for Linux, FreeBSD, Windows, and Mac OS X.

As a protocol and architecture, HIP is basically ready; it has been so  
for 1-2 years now.  There are a few open loops, such as the details of  
NAT traversals, but they are gradually being closed. There has also  
been some discussions on reopening the discussion of whether it should  
re-chartered for standards track, but I have only heard rumours, not  
been active myself.

What comes to HIP and RRG, I do believe that HIP *could* help in  
solving the RRG problem.  It *could* form a core for what people now  
call "Strategy B" solutions, and a HIP-proxy based solution *could* be  
deployed as a "Strategy A" solution.  I don't know the details of  
LISP, but the recent discussion between Dino and me seem to indicate  
that HIP proxy and LISP xTRs are functionally close enough so that a  
HIP proxy could be "plugged in" to the LISP architecture, yielding a  
"Strategy A" HIP-based network-level solution that could eventually  
lead to full HIP deployment at all hosts, which *could* lead to an  
architecture where renumbering is never needed due to full transparent  
support of multiple IP addresses at all hosts.

But, obviously, developing a HIP-based RRG solution would require  
work.  Few if any HIP folks are active at the RRG, AFAIK.  So, there  
doesn't seem to be anyone who would be interested enough to invest the  
time and effort.  (For example, I don't normally have enough of time  
to browse the RRG ML...)

--Pekka

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan  5 09:41:46 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 65B593A67FD;
	Mon,  5 Jan 2009 09:41:46 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8D8043A67FD
	for <rrg@core3.amsl.com>; Mon,  5 Jan 2009 09:41:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.35
X-Spam-Level: 
X-Spam-Status: No, score=-6.35 tagged_above=-999 required=5 tests=[AWL=-0.107, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	SARE_SUB_6CONS_WORD=0.356]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ovzH93DSywrl for <rrg@core3.amsl.com>;
	Mon,  5 Jan 2009 09:41:44 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71])
	by core3.amsl.com (Postfix) with ESMTP id C653B3A67D6
	for <rrg@irtf.org>; Mon,  5 Jan 2009 09:41:44 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.36,332,1228089600"; d="scan'208";a="119743445"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-2.cisco.com with ESMTP; 05 Jan 2009 17:41:32 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id n05HfWDl032015; 
	Mon, 5 Jan 2009 09:41:32 -0800
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n05HfVTv022665;
	Mon, 5 Jan 2009 17:41:32 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Jan 2009 09:41:28 -0800
Received: from [192.168.7.124] ([10.21.72.30]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Jan 2009 09:41:28 -0800
Message-Id: <C6610220-EA04-4DAA-8354-7E599C02DEA0@cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: MARCELO BAGNULO BRAUN <marcelo@it.uc3m.es>
In-Reply-To: <20090105120524.hh0eyj0miskw8c08@webcartero01.uc3m.es>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Mon, 5 Jan 2009 09:41:28 -0800
References: <20090104202055.946896BE56A@mercury.lcs.mit.edu>
	<20090105120524.hh0eyj0miskw8c08@webcartero01.uc3m.es>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 05 Jan 2009 17:41:28.0147 (UTC)
	FILETIME=[D6664230:01C96F5C]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=958; t=1231177292; x=1232041292;
	c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dino@cisco.com;
	z=From:=20Dino=20Farinacci=20<dino@cisco.com>
	|Subject:=20Re=3A=20[rrg]=20Remote=20ACLs=20[Proposals=20wh
	ich=20match=20rrg=20architectures.htmlpls=20check=20the=20pa
	ge] |Sender:=20;
	bh=Z2wXsjeXaLEw1lbhZiBcGpROKwyZFTxuXusRhcfy10A=;
	b=JBRxx5kzrBF/f2ygEoWxCT4MLZ6vmFCKtBd/bELjvFkHm3Kr4OqMd61jSt
	+e3fJ43b1rF6vSBWrIs38QufvH8E5AeEURa9FYsYhZ/ZhIzQHSBEKXjBgiyp
	cnYX3fSTu/;
Authentication-Results: sj-dkim-4; header.From=dino@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: rrg@irtf.org
Subject: Re: [rrg] Remote ACLs [Proposals which match rrg
	architectures.htmlpls check the page]
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

> I guess that one of the problems with using identifier is how can  
> you trust the idnetifiers in the packet?
> I mean, if you include botht eh ID and the locator in the packet  
> e.g. a tunnel, the source locator has some inherent security  
> features, since it is the token that will be used by the routing  
> system to send packets back,

Don't assume this.

> so spoofing it will result in retrun packet going somewhere else.
> The identifier does not have such property and spoofing it is trivial.

You could do a EID-to-RLOC map check at access points (i.e. PE  
routers). That is just a different form or URPF.

> I guess that if we want to use identifiers in the ACL and make them  
> minimally useful, the device holding the ACL needs to verify the ID  
> loc mapping, which seems somehow more complex than current practice.

On the PE box, you may know what customer link has EID-prefixes and do  
the ACL there.

Dino

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan  5 09:44:42 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CF1383A6937;
	Mon,  5 Jan 2009 09:44:42 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 60E4F3A6937
	for <rrg@core3.amsl.com>; Mon,  5 Jan 2009 09:44:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.523
X-Spam-Level: 
X-Spam-Status: No, score=-6.523 tagged_above=-999 required=5 tests=[AWL=0.076, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id mCv3v7MPxwe9 for <rrg@core3.amsl.com>;
	Mon,  5 Jan 2009 09:44:40 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71])
	by core3.amsl.com (Postfix) with ESMTP id AB87D3A68EF
	for <rrg@irtf.org>; Mon,  5 Jan 2009 09:44:40 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.36,332,1228089600"; d="scan'208";a="119744442"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-2.cisco.com with ESMTP; 05 Jan 2009 17:44:25 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id n05HiPst004400; 
	Mon, 5 Jan 2009 09:44:25 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n05HiPBV024968;
	Mon, 5 Jan 2009 17:44:25 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Jan 2009 09:44:25 -0800
Received: from [192.168.7.124] ([10.21.72.30]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Jan 2009 09:44:24 -0800
Message-Id: <20EEF623-B503-4994-B099-64715E567B2D@cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: Pekka Nikander <pekka.nikander@nomadiclab.com>
In-Reply-To: <D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Mon, 5 Jan 2009 09:44:24 -0800
References: <495F0BAA.2040303@firstpr.com.au> <49611E83.8050301@gmail.com>
	<4961CFD3.2050304@firstpr.com.au>
	<D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 05 Jan 2009 17:44:24.0739 (UTC)
	FILETIME=[3FA80F30:01C96F5D]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=982; t=1231177465; x=1232041465;
	c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dino@cisco.com;
	z=From:=20Dino=20Farinacci=20<dino@cisco.com>
	|Subject:=20Re=3A=20[rrg]=20Rejecting=20all=20but=20Strateg
	y=20A |Sender:=20;
	bh=b6nhYl2BYwewLNyvnJDT4tch1BEUEJ0xVBnOZZVmntc=;
	b=E+vSm92rsOLolMgE2Y89SoWsCYoGMOZOo5gNBWEvb7K0h7c5d5kAtfSKO9
	W5K3cum8jjbkidkjdoXFjHKFtCLueUOTe2VjmZQR/rlZmSw/0HPcZEBOzLvE
	L6Kipkf9sx;
Authentication-Results: sj-dkim-4; header.From=dino@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: RRG <rrg@irtf.org>, Robin Whittle <rw@firstpr.com.au>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

> What comes to HIP and RRG, I do believe that HIP *could* help in  
> solving the RRG problem.  It *could* form a core for what people now  
> call "Strategy B" solutions, and a HIP-proxy based solution *could*  
> be deployed as a "Strategy A" solution.  I don't know the details of  
> LISP, but the recent discussion between Dino and me seem to indicate  
> that HIP proxy and LISP xTRs are functionally close enough so that a  
> HIP proxy could be "plugged in" to the LISP architecture, yielding a  
> "Strategy A" HIP-based network-level solution that could eventually  
> lead to full HIP deployment at all hosts, which *could* lead to an  
> architecture where renumbering is never needed due to full  
> transparent support of multiple IP addresses at all hosts.

And since I don't know the details of HIP-proxy, saying LISP and HIP- 
proxy are functionally equivalent only occurs at a conversational  
level. The devil is in the details of course.

Dino

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan  5 10:06:12 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E38A23A6962;
	Mon,  5 Jan 2009 10:06:12 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1452E3A6962
	for <rrg@core3.amsl.com>; Mon,  5 Jan 2009 10:06:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.362
X-Spam-Level: 
X-Spam-Status: No, score=-6.362 tagged_above=-999 required=5
	tests=[AWL=-0.119, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	SARE_SUB_6CONS_WORD=0.356]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id TABxCtNKuYxa for <rrg@core3.amsl.com>;
	Mon,  5 Jan 2009 10:06:11 -0800 (PST)
Received: from virtualized.org (trantor.virtualized.org [204.152.189.190])
	by core3.amsl.com (Postfix) with ESMTP id 5E1443A63D2
	for <rrg@irtf.org>; Mon,  5 Jan 2009 10:06:11 -0800 (PST)
Received: from wlan39-077.mdr.icann.org (wlan39-077.mdr.icann.org
	[192.0.39.77])
	by virtualized.org (Postfix) with ESMTP id 1E9D5413BE1;
	Mon,  5 Jan 2009 10:05:35 -0800 (PST)
Message-Id: <A95DB8C8-1C1A-498A-AC16-6142E2FCB99C@virtualized.org>
From: David Conrad <drc@virtualized.org>
To: Dino Farinacci <dino@cisco.com>
In-Reply-To: <DB736143-9A90-42C0-8518-CC6782FB071D@cisco.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Mon, 5 Jan 2009 10:05:33 -0800
References: <000c01c96ed2$73fa70b0$670c6f0a@china.huawei.com>
	<417CE10E-C5DE-4825-B250-42F6751112EC@cisco.com>
	<3B101E43-106C-4B31-A943-B5F7AD1EA995@virtualized.org>
	<DB736143-9A90-42C0-8518-CC6782FB071D@cisco.com>
X-Mailer: Apple Mail (2.930.3)
Cc: RRG RG <rrg@irtf.org>
Subject: Re: [rrg] Remote ACLs [Proposals which match
	rrg	architectures.htmlpls check the page]
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On Jan 5, 2009, at 9:36 AM, Dino Farinacci wrote:
> So don't you think the decoupling is a good thing? I can see benefits.

Decoupling is good, but it can go farther...

As I hinted at (oh so long ago) during my presentation at the AMS  
workshop, one advantage of indirection-based approaches is that EIDs  
do not need to be allocated hierarchically, thus the existing policy  
constraints for address allocation no longer apply.  The RIRs could  
continue to hand out 'routing slot conservation policy'-constrained  
LOCs since they have the technical expertise to know what this means.   
They could also hand out the EIDs, but since the policy regime for EID  
allocation is fundamentally different than LOCs, it might make sense  
for other bodies (e.g., national allocation entities like NANPA in the  
+1 telephone region) to handle that task.

Of course, if EIDs aren't handed out hierarchically, the existing ACL  
models that rely on locator semantics would obviously break.  Some  
argue this wouldn't necessarily be a bad thing...

Regards,
-drc



_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan  5 10:26:57 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B426F28C0D0;
	Mon,  5 Jan 2009 10:26:57 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BF5AC28C0D0
	for <rrg@core3.amsl.com>; Mon,  5 Jan 2009 10:26:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.477
X-Spam-Level: 
X-Spam-Status: No, score=-6.477 tagged_above=-999 required=5 tests=[AWL=0.122, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id cub5teeihf6H for <rrg@core3.amsl.com>;
	Mon,  5 Jan 2009 10:26:56 -0800 (PST)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com
	[130.76.96.56]) by core3.amsl.com (Postfix) with ESMTP id D97FB3A69D1
	for <rrg@irtf.org>; Mon,  5 Jan 2009 10:26:55 -0800 (PST)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231])
	by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id n05IQ9xL021804
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 5 Jan 2009 12:26:09 -0600 (CST)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	n05IQ8Mw009928; Mon, 5 Jan 2009 10:26:08 -0800 (PST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	n05IQ8Oh009892; Mon, 5 Jan 2009 10:26:08 -0800 (PST)
Received: from XCH-NW-6V1.nw.nos.boeing.com ([130.247.55.53]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 5 Jan 2009 10:26:00 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 5 Jan 2009 10:26:00 -0800
Message-ID: <474EEBD229DF754FB83D256004D021080AD5E3B7@XCH-NW-6V1.nw.nos.boeing.com>
In-Reply-To: <3c3e3fca0812301514t733f0a11v96799c7c6d229b24@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] Solution space summary: rejection phase: B is not blackand
	white
Thread-Index: Aclq1G2jBsumN4LiRgOy0TqgOz76QQEi8mwg
References: <3c3e3fca0812231920vde6d6c4j458adc465e5c1e8@mail.gmail.com><495955C7.7010103@gmail.com><3c3e3fca0812291613i22924bb8qdf5c3f33fb6fbb6@mail.gmail.com><495972E0.9060900@gmail.com>
	<3c3e3fca0812301514t733f0a11v96799c7c6d229b24@mail.gmail.com>
From: "Fleischman, Eric" <eric.fleischman@boeing.com>
To: "William Herrin" <bill@herrin.us>,
	"Brian E Carpenter" <brian.e.carpenter@gmail.com>
X-OriginalArrivalTime: 05 Jan 2009 18:26:00.0562 (UTC)
	FILETIME=[0F486D20:01C96F63]
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] Solution space summary: rejection phase: B is not
	blackand white
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

>From: William Herrin [mailto:bill@herrin.us] 
>>From: Brian Carpenter
>> But it is my opinion that B is a lost cause for IPv4.

>It is and it isn't.

>If you fix the layer 4/5 problem where the locator gets 
>mixed in with the session ID, why should the resulting protocol 
>not be layer-3 agnostic? You just put both protocol and locator 
>in the guid to locator map instead of just putting a locator there. 
>Presto! Done.

>Such a strategy-B protocol should be able to run on any layer-3 
>protocol available, which means it should coexist happily with the
>IPv4 backbone for as long a transition period as necessary. So in 
>that sense, it isn't a lost cause for IPv4. Quite the contrary, 
>IPv4 is part of the deployment bridge.

I apologize for my delay in noticing this dialog -- I'm currently
catching up on emails received during the Christmas break.

I'd like to support Bill Herrin's observation by reporting that in 2008
Boeing coworkers demonstrated that highly mobile (e.g., aeronautical)
applications that use HIP have a side benefit of being agnostic of
whether the underlying network was IPv4 or IPv6, including maintaining
session coherence when transparently switching between underlying
network systems using IPv4 and IPv6 (and vice-versa) during continuous
application sessions.
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan  5 11:08:05 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 84ED83A69E0;
	Mon,  5 Jan 2009 11:08:05 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E780E3A69E0
	for <rrg@core3.amsl.com>; Mon,  5 Jan 2009 11:08:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.348
X-Spam-Level: 
X-Spam-Status: No, score=-6.348 tagged_above=-999 required=5
	tests=[AWL=-0.105, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	SARE_SUB_6CONS_WORD=0.356]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 17+HoKAAnTXN for <rrg@core3.amsl.com>;
	Mon,  5 Jan 2009 11:08:04 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71])
	by core3.amsl.com (Postfix) with ESMTP id 1E29A3A6937
	for <rrg@irtf.org>; Mon,  5 Jan 2009 11:08:04 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.36,333,1228089600"; d="scan'208";a="119776357"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-2.cisco.com with ESMTP; 05 Jan 2009 19:03:26 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id n05J3QhD021601; 
	Mon, 5 Jan 2009 11:03:26 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id n05J3QEG023823;
	Mon, 5 Jan 2009 19:03:26 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Jan 2009 11:03:24 -0800
Received: from [192.168.7.124] ([10.21.72.30]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Jan 2009 11:03:23 -0800
Message-Id: <59A87AAB-66C9-4284-84DA-13E07E6951C9@cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: David Conrad <drc@virtualized.org>
In-Reply-To: <A95DB8C8-1C1A-498A-AC16-6142E2FCB99C@virtualized.org>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Mon, 5 Jan 2009 11:03:24 -0800
References: <000c01c96ed2$73fa70b0$670c6f0a@china.huawei.com>
	<417CE10E-C5DE-4825-B250-42F6751112EC@cisco.com>
	<3B101E43-106C-4B31-A943-B5F7AD1EA995@virtualized.org>
	<DB736143-9A90-42C0-8518-CC6782FB071D@cisco.com>
	<A95DB8C8-1C1A-498A-AC16-6142E2FCB99C@virtualized.org>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 05 Jan 2009 19:03:24.0106 (UTC)
	FILETIME=[488A12A0:01C96F68]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2072; t=1231182206;
	x=1232046206; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dino@cisco.com;
	z=From:=20Dino=20Farinacci=20<dino@cisco.com>
	|Subject:=20Re=3A=20[rrg]=20Remote=20ACLs=20[Proposals=20wh
	ich=20match=20rrg=09architectures.htmlpls=20check=20the=20pa
	ge] |Sender:=20;
	bh=eGlNbxOFr1vAPseqMi5pD4LN9fKxVX5vC5Y6lp4OlTk=;
	b=M30D7jhyVPNWnHAkFHVfP8u6OUc76DTpJ/8q9yRFVUz92cbv9MA9sWaeL2
	o1f9+807DUT0tlA2kAoZVfn5sU29DKJaVi5WetyQp2MC32Yd+RNmm9O/WYqn
	yg3qnikIJf;
Authentication-Results: sj-dkim-4; header.From=dino@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: RRG RG <rrg@irtf.org>
Subject: Re: [rrg] Remote ACLs [Proposals which match
	rrg	architectures.htmlpls check the page]
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

> On Jan 5, 2009, at 9:36 AM, Dino Farinacci wrote:
>> So don't you think the decoupling is a good thing? I can see  
>> benefits.
>
> Decoupling is good, but it can go farther...
>
> As I hinted at (oh so long ago) during my presentation at the AMS  
> workshop, one advantage of indirection-based approaches is that EIDs  
> do not need to be allocated hierarchically, thus the

To be clear, do you mean according to network topology hierarchy or  
you mean in power-of-2 blocks? For the later, you want to allocate in  
power-of-2 chunks so your access-lists are kept small. And if the EID  
could encode an AS-number of domain-id that the RIR allocates to the  
site (read: IPv6 allcoations), then we don't have to have the large  
prefix-lists per AS we do today in IPv4.

> existing policy constraints for address allocation no longer apply.   
> The RIRs could continue to hand out 'routing slot conservation  
> policy'-constrained LOCs since they have the technical

Let's not go this route. Let's have service providers allocate RLOCs  
to sites. And just have RIRs allocate EID-prefixes to sites. But RIRs  
would allocate PA RLOC prefixes to service providers.

Make sense?

> expertise to know what this means.  They could also hand out the  
> EIDs, but since the policy regime for EID allocation is  
> fundamentally different than LOCs, it might make sense for other  
> bodies (e.g., national allocation entities like NANPA in the +1  
> telephone region) to handle that task.

By allocating EID-prefixes based solely on address usage, you only  
have a one-dimensional variable.

Let me be clear, I am not disagreeing with anything you are saying,  
I'm just adding more to it. Hope you agree with my statements.

> Of course, if EIDs aren't handed out hierarchically, the existing  
> ACL models that rely on locator semantics would obviously break.   
> Some argue this wouldn't necessarily be a bad thing...

I think a non-starter. We shouldn't let this happen.

Dino

>
>
> Regards,
> -drc
>
>
>

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan  5 12:00:31 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B1D873A6A99;
	Mon,  5 Jan 2009 12:00:31 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4B4C53A6A12
	for <rrg@core3.amsl.com>; Mon,  5 Jan 2009 12:00:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id SHVpH-TX5+hb for <rrg@core3.amsl.com>;
	Mon,  5 Jan 2009 12:00:29 -0800 (PST)
Received: from ashesmtp03.verizonbusiness.com (ashesmtp03.verizonbusiness.com
	[198.4.8.167]) by core3.amsl.com (Postfix) with ESMTP id A243D3A6A45
	for <rrg@irtf.org>; Mon,  5 Jan 2009 12:00:18 -0800 (PST)
Received: from dgismtp03.wcomnet.com ([166.38.58.143])
	by firewall.verizonbusiness.com
	(Sun Java(tm) System Messaging Server 6.3-5.02 (built Oct 12 2007;
	32bit))
	with ESMTP id <0KD0007AZKW41R00@firewall.verizonbusiness.com> for
	rrg@irtf.org; Mon, 05 Jan 2009 20:00:04 +0000 (GMT)
Received: from dgismtp03.wcomnet.com ([127.0.0.1])
	by dgismtp03.mcilink.com (iPlanet Messaging Server 5.2 HotFix 2.08
	(built Sep
	22 2005)) with SMTP id <0KD000FPEKW4F2@dgismtp03.mcilink.com> for
	rrg@irtf.org; Mon, 05 Jan 2009 20:00:04 +0000 (GMT)
Received: from meno.corp.us.uu.net ([153.39.146.71])
	by dgismtp03.mcilink.com (iPlanet Messaging Server 5.2 HotFix 2.08
	(built Sep
	22 2005)) with ESMTP id <0KD000F2EKW3ZF@dgismtp03.mcilink.com> for
	rrg@irtf.org; Mon, 05 Jan 2009 20:00:03 +0000 (GMT)
Date: Mon, 05 Jan 2009 15:00:02 -0500 (EST)
From: Jason Schiller <schiller@uu.net>
In-reply-to: <200901051509.n05F9nM02828@magenta.juniper.net>
X-Sender: schiller@meno.corp.us.uu.net
To: Yakov Rekhter <yakov@juniper.net>
Message-id: <Pine.GSO.4.20.0901051209330.29070-100000@meno.corp.us.uu.net>
MIME-version: 1.0
Cc: 'RRG' <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On Mon, 5 Jan 2009, Yakov Rekhter wrote:

> Few points:
> 
>  - Even if one assumes that the growth rate of prefixes exceeds the
>    rate of speed improvements in the underlying DRAM that is used to
>    implement control plane, and that, in turn, would result in cost
>    increases, let's not forget that deploying new routing architecture
>    may have its own cost, thus resulting in cost increases. Moreover,
>    these increases may be higher relative to what would result from
>    the growth rate of prefixes exceeding the rate of speed improvements
>    in the underlying DRAM.
> 
>    These increases, just like the increases you mentioned above,
>    would need to be absorbed by the system, and "most likely to
>    propagate to the end users, with a net detriment to the growth
>    of the network".  Moreover, these increases would need to be
>    absorbed by the system in the short/medium term, well before we
>    will reach "the promise" of the cost reduction in the *long
>    term*. Would the industry be willing to buy into the *promise* of
>    "a paradise" in the *long* term at the price of fairly certain
>    cost increases in the *short/medium* term ? 
> 
>    All of the above means that a "promise" of cost reduction in the
>    *long* term may not be sufficient - the new routing architecture
>    needs to deliver in the *short/medium* term sufficient *tangible*
>    benefits to justify its *short/medium* term cost.
> 
>  - One may argue that the real problem is not in the cost increases,
>    but in the way how these increases are absorbed by the system.
>    Namely, the real problem is that those who do not benefit
>    are still required to pay for covering the cost imposed by those
>    who do benefit. That applies both to the current system, as well 
>    as to any proposal for a new routing architecture.

It is important to point out that in the past the need driving the cost
increases to scale routers was either amount of bandwidth (as customers
wish to pass more traffic) or port density (as more customers desire to
connect).  Both of these come with an increase in revenue for the
provider, and as such (if the economics make sense) can justify the cost
of the upgrades.

We are currently faced with a need to upgrade routers due to the amount of
the routing state (and potentially the frequency with which it
changes).  These conditions are not necessarily a reflection of
increasing customer demand or increasing revue, and in fact a large
portion of this problem is originated by non-customers.

<insert Geoff Huston discussion on problems with a routing economy>

Charging non-customers per prefix to install routes in my routing table
seems like it would take the Network Neutrality problem to a whole new
level.

Finally WRT absorbing the cost within the system you will need to
consider:

1. What pricing model do vendors use for routers such that a moderately
low end CPE that can carry multiple views of full routes (think cisco
7200 for customer with a single T1 to each of four different
providers) remains affordable to small enterprises without making the cost
of high end routes grow logarithmically as they keep up with table growth.

2. Routers have to be of sufficient scale to provide large ISPs enough
time to complete certification, schedule maint windows and fully deploy
all of the new devices, and hopefully depreciate the assets for 5 years
before starting the cycle all over.

3. Are the added costs a one time event?  Can this even be roll into a
normal refresh cycle?  Or are the added costs recurring, such as upgrading
chassis every 3 years at a cost increase?

4. who should bear the burden of the extra cost?
Should ISPs that must be default free carry a larger burden?  

What about end-sites that are not required to be default free, but desire
it for better TE? 

Should ISPs that are default free with many routers carry a larger burden
than DFZ ISPs with few routers?  Consider that the number of routers in an
ISPs network does not necessarily impact the number of routes they source
into the DFZ.  

Should this cost just be passed along to an ISP's customers?  If so then
you reward the ISP that flood the DFZ with routes, and penalize the ISPs
who aggregate well.

__Jason

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan  5 12:13:50 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8AAFA3A6836;
	Mon,  5 Jan 2009 12:13:50 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D205728C0EB
	for <rrg@core3.amsl.com>; Mon,  5 Jan 2009 12:13:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.187
X-Spam-Level: 
X-Spam-Status: No, score=-6.187 tagged_above=-999 required=5
	tests=[AWL=-0.188, BAYES_00=-2.599, J_CHICKENPOX_13=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id SdWxFimb9hWJ for <rrg@core3.amsl.com>;
	Mon,  5 Jan 2009 12:13:49 -0800 (PST)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com
	[130.76.96.56]) by core3.amsl.com (Postfix) with ESMTP id CD2D93A6836
	for <rrg@irtf.org>; Mon,  5 Jan 2009 12:13:48 -0800 (PST)
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4])
	by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id n05KDOwv003106
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 5 Jan 2009 14:13:24 -0600 (CST)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1])
	by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	n05KDO6N024457; Mon, 5 Jan 2009 12:13:24 -0800 (PST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	n05KDMGm024407; Mon, 5 Jan 2009 12:13:23 -0800 (PST)
Received: from XCH-NW-6V1.nw.nos.boeing.com ([130.247.55.53]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 5 Jan 2009 12:13:21 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 5 Jan 2009 12:13:20 -0800
Message-ID: <474EEBD229DF754FB83D256004D021080AD5E539@XCH-NW-6V1.nw.nos.boeing.com>
In-Reply-To: <20EEF623-B503-4994-B099-64715E567B2D@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] Rejecting all but Strategy A
Thread-Index: AclvXUYmvoVeJr1nR6SW0ForHgo4ugADW/rQ
References: <495F0BAA.2040303@firstpr.com.au>
	<49611E83.8050301@gmail.com><4961CFD3.2050304@firstpr.com.au><D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com>
	<20EEF623-B503-4994-B099-64715E567B2D@cisco.com>
From: "Fleischman, Eric" <eric.fleischman@boeing.com>
To: "Dino Farinacci" <dino@cisco.com>,
	"Pekka Nikander" <pekka.nikander@nomadiclab.com>
X-OriginalArrivalTime: 05 Jan 2009 20:13:21.0838 (UTC)
	FILETIME=[0E9524E0:01C96F72]
Cc: RRG <rrg@irtf.org>, Robin Whittle <rw@firstpr.com.au>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

 
>From: Dino Farinacci [mailto:dino@cisco.com] 
>>From: Pekka Nikander
>> What comes to HIP and RRG, I do believe that HIP *could* help in 
>> solving the RRG problem.  It *could* form a core for what people now 
>> call "Strategy B" solutions, and a HIP-proxy based solution *could*
be 
>> deployed as a "Strategy A" solution.  I don't know the details of 
>> LISP, but the recent discussion between Dino and me seem to indicate 
>> that HIP proxy and LISP xTRs are functionally close enough so that a 
>> HIP proxy could be "plugged in" to the LISP architecture, yielding a 
>> "Strategy A" HIP-based network-level solution that could eventually 
>> lead to full HIP deployment at all hosts, which *could* lead to an 
>> architecture where renumbering is never needed due to full
transparent 
>> support of multiple IP addresses at all hosts.

>And since I don't know the details of HIP-proxy, saying LISP and HIP- 
>proxy are functionally equivalent only occurs at a conversational
level. 
>The devil is in the details of course.

I strongly resonate with Pekka's posting.

Speaking solely for myself, I view LISP's original claims to be a
locator-identifier split to be a redefinition of what those terms have
historically meant (i.e., to be marketing -- not reality). By contrast,
HIP is a true locator-identifier split technology in every sense of the
historic meaning.

LISP, by contrast, is a map-and-encaps solution to the RRG problem.

There is no necessary relationship between HIP (or any other
locator-identifier split) and LISP (or any other map-and-encaps).
Specifically, I believe that locator-identifier splits are a session
layer concept and therefore are primarily host-related. I believe that
map-and-encaps is primarily a network layer concept.

By combining a true locator-identifier split (i.e., HIP) with a
map-and-encaps (e.g., LISP) one gets the combined benefits of both
approaches. Those benefits are

*  For HIP-based applications (i.e., hosts) this creates a full
decoupling of application issues from network issues. This
simultaneously solves many different problems including the following: a
transparent solution to application multihoming; complete agnosticism
concerning network issues including IPv4 or IPv6; strong session
coherence in the face of substantial mobility; solution to the "IP
identity problem", thereby solving a great many festering security
issues including a clean integration with IPsec, providing
best-current-practice Denial-of-service (DoS) attack resistance,
exponentially increasing the ability to identify and defend against
spoofing attacks, substantially increased protection against session
hijacking, and (by solving the identity problem) making existing
application authentication and authorization systems become more viable.
*  HIP also provides a formal (secure) delegation capability that
permits HIP users (e.g., hosts) to delegate authority to other entities
to act on their behalf. This would, for instance, allow a host that
wants to hide its current location to use network proxies to forward its
traffic. For example, DoS attacks could also be deflected to network
proxies.

*  For map-and-encaps based systems this provides a scalable network
integration capability to resolve a wide variety of different network
scalability and integration challenges including: 
1) IPv4-IPv6 coexistence: ISATAP, Teredo, IPvLX, etc.
2) Military Communications Security (COMSEC)
3) IPsec's ESP in tunnel mode
4) L3VPN (including how my employer relates to our ISPs (please note the
plural))
5) ecommerce
6) ARINC 664 enclave protections
7) Architectures that leverage IP to join together distributed legacy
(i.e., non-IP) protocol systems. It is also used to merge legacy
populations into IP networks (e.g., RFC 1006).
 
--Eric
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan  5 13:27:58 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8FEB23A6836;
	Mon,  5 Jan 2009 13:27:58 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1F3273A6836
	for <rrg@core3.amsl.com>; Mon,  5 Jan 2009 13:27:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.161
X-Spam-Level: 
X-Spam-Status: No, score=-6.161 tagged_above=-999 required=5
	tests=[AWL=-0.162, BAYES_00=-2.599, J_CHICKENPOX_13=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id yl0Q6bj9g933 for <rrg@core3.amsl.com>;
	Mon,  5 Jan 2009 13:27:56 -0800 (PST)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com
	[130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id 1CF343A67EC
	for <rrg@irtf.org>; Mon,  5 Jan 2009 13:27:55 -0800 (PST)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6])
	by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id n05LRMe1020674
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 5 Jan 2009 13:27:22 -0800 (PST)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	n05LRML4008257; Mon, 5 Jan 2009 15:27:22 -0600 (CST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	n05LRG65008116; Mon, 5 Jan 2009 15:27:21 -0600 (CST)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 5 Jan 2009 13:27:19 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 5 Jan 2009 13:27:18 -0800
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A105623AC3@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <474EEBD229DF754FB83D256004D021080AD5E539@XCH-NW-6V1.nw.nos.boeing.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] Rejecting all but Strategy A
Thread-Index: AclvXUYmvoVeJr1nR6SW0ForHgo4ugADW/rQAARP0WA=
References: <495F0BAA.2040303@firstpr.com.au><49611E83.8050301@gmail.com><4961CFD3.2050304@firstpr.com.au><D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com><20EEF623-B503-4994-B099-64715E567B2D@cisco.com>
	<474EEBD229DF754FB83D256004D021080AD5E539@XCH-NW-6V1.nw.nos.boeing.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Fleischman, Eric" <eric.fleischman@boeing.com>,
	"Dino Farinacci" <dino@cisco.com>,
	"Pekka Nikander" <pekka.nikander@nomadiclab.com>
X-OriginalArrivalTime: 05 Jan 2009 21:27:19.0694 (UTC)
	FILETIME=[63C03AE0:01C96F7C]
Cc: RRG <rrg@irtf.org>, Robin Whittle <rw@firstpr.com.au>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org



>-----Original Message-----
>From: Fleischman, Eric
>Sent: Monday, January 05, 2009 12:13 PM
>To: Dino Farinacci; Pekka Nikander
>Cc: RRG; Robin Whittle
>Subject: Re: [rrg] Rejecting all but Strategy A
>
>
>
>>From: Dino Farinacci [mailto:dino@cisco.com]
>>>From: Pekka Nikander
>>> What comes to HIP and RRG, I do believe that HIP *could* help in
>>> solving the RRG problem.  It *could* form a core for what people now
>>> call "Strategy B" solutions, and a HIP-proxy based solution *could*
>be
>>> deployed as a "Strategy A" solution.  I don't know the details of
>>> LISP, but the recent discussion between Dino and me seem to indicate
>>> that HIP proxy and LISP xTRs are functionally close enough so that a
>>> HIP proxy could be "plugged in" to the LISP architecture, yielding a
>>> "Strategy A" HIP-based network-level solution that could eventually
>>> lead to full HIP deployment at all hosts, which *could* lead to an
>>> architecture where renumbering is never needed due to full
>transparent
>>> support of multiple IP addresses at all hosts.
>
>>And since I don't know the details of HIP-proxy, saying LISP and HIP-
>>proxy are functionally equivalent only occurs at a conversational
>level.
>>The devil is in the details of course.
>
>I strongly resonate with Pekka's posting.

Pekka, is "HIP-proxy" and "HIP mobile router" one and the
same thing? If so, IMHO it is absolutely realistic that the
HIP-proxy and xTR could occur on exactly the same platform.
Note that they are complementary functions, however; not
competing ones. I think this also goes with what Eric was
saying below?

Fred
fred.l.templin@boeing.com

>Speaking solely for myself, I view LISP's original claims to be a
>locator-identifier split to be a redefinition of what those terms have
>historically meant (i.e., to be marketing -- not reality). By contrast,
>HIP is a true locator-identifier split technology in every sense of the
>historic meaning.
>
>LISP, by contrast, is a map-and-encaps solution to the RRG problem.
>
>There is no necessary relationship between HIP (or any other
>locator-identifier split) and LISP (or any other map-and-encaps).
>Specifically, I believe that locator-identifier splits are a session
>layer concept and therefore are primarily host-related. I believe that
>map-and-encaps is primarily a network layer concept.
>
>By combining a true locator-identifier split (i.e., HIP) with a
>map-and-encaps (e.g., LISP) one gets the combined benefits of both
>approaches. Those benefits are
>
>*  For HIP-based applications (i.e., hosts) this creates a full
>decoupling of application issues from network issues. This
>simultaneously solves many different problems including the following:
a
>transparent solution to application multihoming; complete agnosticism
>concerning network issues including IPv4 or IPv6; strong session
>coherence in the face of substantial mobility; solution to the "IP
>identity problem", thereby solving a great many festering security
>issues including a clean integration with IPsec, providing
>best-current-practice Denial-of-service (DoS) attack resistance,
>exponentially increasing the ability to identify and defend against
>spoofing attacks, substantially increased protection against session
>hijacking, and (by solving the identity problem) making existing
>application authentication and authorization systems become more
viable.
>*  HIP also provides a formal (secure) delegation capability that
>permits HIP users (e.g., hosts) to delegate authority to other entities
>to act on their behalf. This would, for instance, allow a host that
>wants to hide its current location to use network proxies to forward
its
>traffic. For example, DoS attacks could also be deflected to network
>proxies.
>
>*  For map-and-encaps based systems this provides a scalable network
>integration capability to resolve a wide variety of different network
>scalability and integration challenges including:
>1) IPv4-IPv6 coexistence: ISATAP, Teredo, IPvLX, etc.
>2) Military Communications Security (COMSEC)
>3) IPsec's ESP in tunnel mode
>4) L3VPN (including how my employer relates to our ISPs (please note
the
>plural))
>5) ecommerce
>6) ARINC 664 enclave protections
>7) Architectures that leverage IP to join together distributed legacy
>(i.e., non-IP) protocol systems. It is also used to merge legacy
>populations into IP networks (e.g., RFC 1006).
>
>--Eric
>_______________________________________________
>rrg mailing list
>rrg@irtf.org
>https://www.irtf.org/mailman/listinfo/rrg
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan  5 13:30:29 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CB14D3A6979;
	Mon,  5 Jan 2009 13:30:29 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 57E813A6979
	for <rrg@core3.amsl.com>; Mon,  5 Jan 2009 13:30:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.473
X-Spam-Level: 
X-Spam-Status: No, score=-6.473 tagged_above=-999 required=5 tests=[AWL=0.127, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id JXJD4s0NULAu for <rrg@core3.amsl.com>;
	Mon,  5 Jan 2009 13:30:27 -0800 (PST)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com
	[130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id 9B5363A6903
	for <rrg@irtf.org>; Mon,  5 Jan 2009 13:30:27 -0800 (PST)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231])
	by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id n05LUBw1022555
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 5 Jan 2009 13:30:12 -0800 (PST)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	n05LUBp7002201; Mon, 5 Jan 2009 13:30:11 -0800 (PST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	n05LUB04002186; Mon, 5 Jan 2009 13:30:11 -0800 (PST)
Received: from XCH-NW-6V1.nw.nos.boeing.com ([130.247.55.53]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 5 Jan 2009 13:30:10 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 5 Jan 2009 13:30:10 -0800
Message-ID: <474EEBD229DF754FB83D256004D021080AD5E66C@XCH-NW-6V1.nw.nos.boeing.com>
In-Reply-To: <49592F54.60600@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] Consensus call: Reject proposed strategy F?
Thread-Index: Aclp8eTERMstVLWrRD2jVJ7iRhcNuQFiIvKA
References: <3c3e3fca0812231929s233ffdbavb24ae9cf7d6c091a@mail.gmail.com>
	<49592F54.60600@gmail.com>
From: "Fleischman, Eric" <eric.fleischman@boeing.com>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>,
	"William Herrin" <bill@herrin.us>
X-OriginalArrivalTime: 05 Jan 2009 21:30:10.0867 (UTC)
	FILETIME=[C9C72830:01C96F7C]
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] Consensus call: Reject proposed strategy F?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

>From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com] 
>>From: William Herrin
 
>> I propose that we REJECT strategy F.
>> 
>> As we use it now, BGP lacks sufficient scalability to see the
Internet 
>> into the coming decades.

>Before we take this as revealed truth, let's not forget that BGP4 has
in fact scaled amazingly well since 1994. 

Yes and no... BGP has scaled remarkably well in supporting Internet
growth since 1994 from a pure routing growth perspective but the
resulting high-human-management care-and-feeding requirement of the
current infrastructure system combined with site hijacking and other
fundamental security challenges paint an entirely different picture of
its adequacy. I fear that BGP weaknesses have resulted in the Internet
being currently held together by bailing wire so that the system can be
readily subverted by accidental administrative mistakes or purposeful
cyber attacks. 
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan  5 14:01:36 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BABF83A6917;
	Mon,  5 Jan 2009 14:01:36 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7345E3A6917
	for <rrg@core3.amsl.com>; Mon,  5 Jan 2009 14:01:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.222
X-Spam-Level: 
X-Spam-Status: No, score=-6.222 tagged_above=-999 required=5
	tests=[AWL=-0.223, BAYES_00=-2.599, J_CHICKENPOX_13=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id UpIe1VHg5OS0 for <rrg@core3.amsl.com>;
	Mon,  5 Jan 2009 14:01:34 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id 726683A67A1
	for <rrg@irtf.org>; Mon,  5 Jan 2009 14:01:34 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.36,334,1228089600"; d="scan'208";a="126711574"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-3.cisco.com with ESMTP; 05 Jan 2009 22:01:22 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n05M1LsU007757; 
	Mon, 5 Jan 2009 14:01:21 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id n05M1LuE023022;
	Mon, 5 Jan 2009 22:01:21 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Jan 2009 14:01:21 -0800
Received: from moveme.cisco.com ([10.21.149.210]) by
	xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Jan 2009 14:01:20 -0800
Message-Id: <4FF36C8D-761D-4D45-BB99-A5E72B9E33C9@cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A105623AC3@XCH-NW-7V2.nw.nos.boeing.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Mon, 5 Jan 2009 14:01:20 -0800
References: <495F0BAA.2040303@firstpr.com.au><49611E83.8050301@gmail.com><4961CFD3.2050304@firstpr.com.au><D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com><20EEF623-B503-4994-B099-64715E567B2D@cisco.com>
	<474EEBD229DF754FB83D256004D021080AD5E539@XCH-NW-6V1.nw.nos.boeing.com>
	<39C363776A4E8C4A94691D2BD9D1C9A105623AC3@XCH-NW-7V2.nw.nos.boeing.com>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 05 Jan 2009 22:01:21.0154 (UTC)
	FILETIME=[248E4E20:01C96F81]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=5260; t=1231192881;
	x=1232056881; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dino@cisco.com;
	z=From:=20Dino=20Farinacci=20<dino@cisco.com>
	|Subject:=20Re=3A=20[rrg]=20Rejecting=20all=20but=20Strateg
	y=20A |Sender:=20;
	bh=7s7gBIdLr5iYjMMmVr32QK5rYKwArpLMoiQJPL1s1jo=;
	b=2Rphh3Cp0s3Ibq/THEKplM2FC68t6PK9rhv6UZyqKKHcxif8rQBTVPBsMP
	bdTu7PzRqgf3y4qs7M5s6RETRb/TEImm0lOGFr+u7I9JFZfIU0O55gI4uxeo
	g28aZxe6HO;
Authentication-Results: sj-dkim-2; header.From=dino@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: RRG <rrg@irtf.org>, Robin Whittle <rw@firstpr.com.au>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Before we get carried away with what looks like a convergence of "HIP- 
proxy and LISP", tell me what HIP offers to a LISP router that the  
LISP architecture does not already provide?

If is solely a add a pure definition to IDs and RLOCs, then I think  
it's not worth the cost of deployment to do so.

Dino

On Jan 5, 2009, at 1:27 PM, Templin, Fred L wrote:

>
>
>> -----Original Message-----
>> From: Fleischman, Eric
>> Sent: Monday, January 05, 2009 12:13 PM
>> To: Dino Farinacci; Pekka Nikander
>> Cc: RRG; Robin Whittle
>> Subject: Re: [rrg] Rejecting all but Strategy A
>>
>>
>>
>>> From: Dino Farinacci [mailto:dino@cisco.com]
>>>> From: Pekka Nikander
>>>> What comes to HIP and RRG, I do believe that HIP *could* help in
>>>> solving the RRG problem.  It *could* form a core for what people  
>>>> now
>>>> call "Strategy B" solutions, and a HIP-proxy based solution *could*
>> be
>>>> deployed as a "Strategy A" solution.  I don't know the details of
>>>> LISP, but the recent discussion between Dino and me seem to  
>>>> indicate
>>>> that HIP proxy and LISP xTRs are functionally close enough so  
>>>> that a
>>>> HIP proxy could be "plugged in" to the LISP architecture,  
>>>> yielding a
>>>> "Strategy A" HIP-based network-level solution that could eventually
>>>> lead to full HIP deployment at all hosts, which *could* lead to an
>>>> architecture where renumbering is never needed due to full
>> transparent
>>>> support of multiple IP addresses at all hosts.
>>
>>> And since I don't know the details of HIP-proxy, saying LISP and  
>>> HIP-
>>> proxy are functionally equivalent only occurs at a conversational
>> level.
>>> The devil is in the details of course.
>>
>> I strongly resonate with Pekka's posting.
>
> Pekka, is "HIP-proxy" and "HIP mobile router" one and the
> same thing? If so, IMHO it is absolutely realistic that the
> HIP-proxy and xTR could occur on exactly the same platform.
> Note that they are complementary functions, however; not
> competing ones. I think this also goes with what Eric was
> saying below?
>
> Fred
> fred.l.templin@boeing.com
>
>> Speaking solely for myself, I view LISP's original claims to be a
>> locator-identifier split to be a redefinition of what those terms  
>> have
>> historically meant (i.e., to be marketing -- not reality). By  
>> contrast,
>> HIP is a true locator-identifier split technology in every sense of  
>> the
>> historic meaning.
>>
>> LISP, by contrast, is a map-and-encaps solution to the RRG problem.
>>
>> There is no necessary relationship between HIP (or any other
>> locator-identifier split) and LISP (or any other map-and-encaps).
>> Specifically, I believe that locator-identifier splits are a session
>> layer concept and therefore are primarily host-related. I believe  
>> that
>> map-and-encaps is primarily a network layer concept.
>>
>> By combining a true locator-identifier split (i.e., HIP) with a
>> map-and-encaps (e.g., LISP) one gets the combined benefits of both
>> approaches. Those benefits are
>>
>> *  For HIP-based applications (i.e., hosts) this creates a full
>> decoupling of application issues from network issues. This
>> simultaneously solves many different problems including the  
>> following:
> a
>> transparent solution to application multihoming; complete agnosticism
>> concerning network issues including IPv4 or IPv6; strong session
>> coherence in the face of substantial mobility; solution to the "IP
>> identity problem", thereby solving a great many festering security
>> issues including a clean integration with IPsec, providing
>> best-current-practice Denial-of-service (DoS) attack resistance,
>> exponentially increasing the ability to identify and defend against
>> spoofing attacks, substantially increased protection against session
>> hijacking, and (by solving the identity problem) making existing
>> application authentication and authorization systems become more
> viable.
>> *  HIP also provides a formal (secure) delegation capability that
>> permits HIP users (e.g., hosts) to delegate authority to other  
>> entities
>> to act on their behalf. This would, for instance, allow a host that
>> wants to hide its current location to use network proxies to forward
> its
>> traffic. For example, DoS attacks could also be deflected to network
>> proxies.
>>
>> *  For map-and-encaps based systems this provides a scalable network
>> integration capability to resolve a wide variety of different network
>> scalability and integration challenges including:
>> 1) IPv4-IPv6 coexistence: ISATAP, Teredo, IPvLX, etc.
>> 2) Military Communications Security (COMSEC)
>> 3) IPsec's ESP in tunnel mode
>> 4) L3VPN (including how my employer relates to our ISPs (please note
> the
>> plural))
>> 5) ecommerce
>> 6) ARINC 664 enclave protections
>> 7) Architectures that leverage IP to join together distributed legacy
>> (i.e., non-IP) protocol systems. It is also used to merge legacy
>> populations into IP networks (e.g., RFC 1006).
>>
>> --Eric
>> _______________________________________________
>> rrg mailing list
>> rrg@irtf.org
>> https://www.irtf.org/mailman/listinfo/rrg

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan  5 14:06:16 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2769F28C0D8;
	Mon,  5 Jan 2009 14:06:16 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 61F603A68B9
	for <rrg@core3.amsl.com>; Mon,  5 Jan 2009 14:06:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.155
X-Spam-Level: 
X-Spam-Status: No, score=-6.155 tagged_above=-999 required=5
	tests=[AWL=-0.156, BAYES_00=-2.599, J_CHICKENPOX_13=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id YJ5muglbvTua for <rrg@core3.amsl.com>;
	Mon,  5 Jan 2009 14:06:14 -0800 (PST)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com
	[130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id 4A6623A67A1
	for <rrg@irtf.org>; Mon,  5 Jan 2009 14:06:14 -0800 (PST)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231])
	by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id n05M5r4u014989
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 5 Jan 2009 14:05:53 -0800 (PST)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	n05M5rMp028279; Mon, 5 Jan 2009 14:05:53 -0800 (PST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	n05M5ru7028255; Mon, 5 Jan 2009 14:05:53 -0800 (PST)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 5 Jan 2009 14:05:52 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 5 Jan 2009 14:05:52 -0800
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A105623B39@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <4FF36C8D-761D-4D45-BB99-A5E72B9E33C9@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] Rejecting all but Strategy A
Thread-Index: AclvgScRpg6glLHgRzCEOswhAPjfgQAADBLw
References: <495F0BAA.2040303@firstpr.com.au><49611E83.8050301@gmail.com><4961CFD3.2050304@firstpr.com.au><D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com><20EEF623-B503-4994-B099-64715E567B2D@cisco.com>
	<474EEBD229DF754FB83D256004D021080AD5E539@XCH-NW-6V1.nw.nos.boeing.com>
	<39C363776A4E8C4A94691D2BD9D1C9A105623AC3@XCH-NW-7V2.nw.nos.boeing.com>
	<4FF36C8D-761D-4D45-BB99-A5E72B9E33C9@cisco.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Dino Farinacci" <dino@cisco.com>
X-OriginalArrivalTime: 05 Jan 2009 22:05:52.0865 (UTC)
	FILETIME=[C6821D10:01C96F81]
Cc: RRG <rrg@irtf.org>, Robin Whittle <rw@firstpr.com.au>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Dino,

>-----Original Message-----
>From: Dino Farinacci [mailto:dino@cisco.com]
>Sent: Monday, January 05, 2009 2:01 PM
>To: Templin, Fred L
>Cc: Fleischman, Eric; Pekka Nikander; RRG; Robin Whittle
>Subject: Re: [rrg] Rejecting all but Strategy A
>
>Before we get carried away with what looks like a convergence of "HIP-
>proxy and LISP", tell me what HIP offers to a LISP router that the
>LISP architecture does not already provide?

I was actually saying convergence of "HIP-proxy and xTR";
xTR does not necessarily mean LISP.

>If is solely a add a pure definition to IDs and RLOCs, then I think
>it's not worth the cost of deployment to do so.

In my understanding there's a lot more to it than that,
but would welcome clarifications.

Fred
fred.l.templin@boeing.com

>
>Dino
>
>On Jan 5, 2009, at 1:27 PM, Templin, Fred L wrote:
>
>>
>>
>>> -----Original Message-----
>>> From: Fleischman, Eric
>>> Sent: Monday, January 05, 2009 12:13 PM
>>> To: Dino Farinacci; Pekka Nikander
>>> Cc: RRG; Robin Whittle
>>> Subject: Re: [rrg] Rejecting all but Strategy A
>>>
>>>
>>>
>>>> From: Dino Farinacci [mailto:dino@cisco.com]
>>>>> From: Pekka Nikander
>>>>> What comes to HIP and RRG, I do believe that HIP *could* help in
>>>>> solving the RRG problem.  It *could* form a core for what people
>>>>> now
>>>>> call "Strategy B" solutions, and a HIP-proxy based solution
*could*
>>> be
>>>>> deployed as a "Strategy A" solution.  I don't know the details of
>>>>> LISP, but the recent discussion between Dino and me seem to
>>>>> indicate
>>>>> that HIP proxy and LISP xTRs are functionally close enough so
>>>>> that a
>>>>> HIP proxy could be "plugged in" to the LISP architecture,
>>>>> yielding a
>>>>> "Strategy A" HIP-based network-level solution that could
eventually
>>>>> lead to full HIP deployment at all hosts, which *could* lead to an
>>>>> architecture where renumbering is never needed due to full
>>> transparent
>>>>> support of multiple IP addresses at all hosts.
>>>
>>>> And since I don't know the details of HIP-proxy, saying LISP and
>>>> HIP-
>>>> proxy are functionally equivalent only occurs at a conversational
>>> level.
>>>> The devil is in the details of course.
>>>
>>> I strongly resonate with Pekka's posting.
>>
>> Pekka, is "HIP-proxy" and "HIP mobile router" one and the
>> same thing? If so, IMHO it is absolutely realistic that the
>> HIP-proxy and xTR could occur on exactly the same platform.
>> Note that they are complementary functions, however; not
>> competing ones. I think this also goes with what Eric was
>> saying below?
>>
>> Fred
>> fred.l.templin@boeing.com
>>
>>> Speaking solely for myself, I view LISP's original claims to be a
>>> locator-identifier split to be a redefinition of what those terms
>>> have
>>> historically meant (i.e., to be marketing -- not reality). By
>>> contrast,
>>> HIP is a true locator-identifier split technology in every sense of
>>> the
>>> historic meaning.
>>>
>>> LISP, by contrast, is a map-and-encaps solution to the RRG problem.
>>>
>>> There is no necessary relationship between HIP (or any other
>>> locator-identifier split) and LISP (or any other map-and-encaps).
>>> Specifically, I believe that locator-identifier splits are a session
>>> layer concept and therefore are primarily host-related. I believe
>>> that
>>> map-and-encaps is primarily a network layer concept.
>>>
>>> By combining a true locator-identifier split (i.e., HIP) with a
>>> map-and-encaps (e.g., LISP) one gets the combined benefits of both
>>> approaches. Those benefits are
>>>
>>> *  For HIP-based applications (i.e., hosts) this creates a full
>>> decoupling of application issues from network issues. This
>>> simultaneously solves many different problems including the
>>> following:
>> a
>>> transparent solution to application multihoming; complete
agnosticism
>>> concerning network issues including IPv4 or IPv6; strong session
>>> coherence in the face of substantial mobility; solution to the "IP
>>> identity problem", thereby solving a great many festering security
>>> issues including a clean integration with IPsec, providing
>>> best-current-practice Denial-of-service (DoS) attack resistance,
>>> exponentially increasing the ability to identify and defend against
>>> spoofing attacks, substantially increased protection against session
>>> hijacking, and (by solving the identity problem) making existing
>>> application authentication and authorization systems become more
>> viable.
>>> *  HIP also provides a formal (secure) delegation capability that
>>> permits HIP users (e.g., hosts) to delegate authority to other
>>> entities
>>> to act on their behalf. This would, for instance, allow a host that
>>> wants to hide its current location to use network proxies to forward
>> its
>>> traffic. For example, DoS attacks could also be deflected to network
>>> proxies.
>>>
>>> *  For map-and-encaps based systems this provides a scalable network
>>> integration capability to resolve a wide variety of different
network
>>> scalability and integration challenges including:
>>> 1) IPv4-IPv6 coexistence: ISATAP, Teredo, IPvLX, etc.
>>> 2) Military Communications Security (COMSEC)
>>> 3) IPsec's ESP in tunnel mode
>>> 4) L3VPN (including how my employer relates to our ISPs (please note
>> the
>>> plural))
>>> 5) ecommerce
>>> 6) ARINC 664 enclave protections
>>> 7) Architectures that leverage IP to join together distributed
legacy
>>> (i.e., non-IP) protocol systems. It is also used to merge legacy
>>> populations into IP networks (e.g., RFC 1006).
>>>
>>> --Eric
>>> _______________________________________________
>>> rrg mailing list
>>> rrg@irtf.org
>>> https://www.irtf.org/mailman/listinfo/rrg

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan  5 14:12:39 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9507E28C129;
	Mon,  5 Jan 2009 14:12:39 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 718EA28C12A
	for <rrg@core3.amsl.com>; Mon,  5 Jan 2009 14:12:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.214
X-Spam-Level: 
X-Spam-Status: No, score=-6.214 tagged_above=-999 required=5
	tests=[AWL=-0.215, BAYES_00=-2.599, J_CHICKENPOX_13=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id QuKqq32-Vend for <rrg@core3.amsl.com>;
	Mon,  5 Jan 2009 14:12:37 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71])
	by core3.amsl.com (Postfix) with ESMTP id 6E86B3A6809
	for <rrg@irtf.org>; Mon,  5 Jan 2009 14:12:37 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.36,334,1228089600"; d="scan'208";a="119831619"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-2.cisco.com with ESMTP; 05 Jan 2009 22:12:25 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n05MCOQB028286; 
	Mon, 5 Jan 2009 14:12:24 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n05MCOeD009500;
	Mon, 5 Jan 2009 22:12:24 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Jan 2009 14:12:24 -0800
Received: from moveme.cisco.com ([10.21.149.210]) by
	xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Jan 2009 14:12:24 -0800
Message-Id: <E294A8E4-57E3-48D3-BE17-B0EF2BD46DA4@cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: "Fleischman, Eric" <eric.fleischman@boeing.com>
In-Reply-To: <474EEBD229DF754FB83D256004D021080AD5E539@XCH-NW-6V1.nw.nos.boeing.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Mon, 5 Jan 2009 14:12:23 -0800
References: <495F0BAA.2040303@firstpr.com.au>
	<49611E83.8050301@gmail.com><4961CFD3.2050304@firstpr.com.au><D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com>
	<20EEF623-B503-4994-B099-64715E567B2D@cisco.com>
	<474EEBD229DF754FB83D256004D021080AD5E539@XCH-NW-6V1.nw.nos.boeing.com>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 05 Jan 2009 22:12:24.0274 (UTC)
	FILETIME=[AFCE6320:01C96F82]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=5115; t=1231193544;
	x=1232057544; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dino@cisco.com;
	z=From:=20Dino=20Farinacci=20<dino@cisco.com>
	|Subject:=20Re=3A=20[rrg]=20Rejecting=20all=20but=20Strateg
	y=20A |Sender:=20;
	bh=mltWzUTwDHuLiMyZWQoFnLyYdLoAB8aEPI0IpNY+Y00=;
	b=t+6CtV4jseKxNe4k8AmUHMKnwpGh5RuFavEvwkg7KYkNHSRMdbhA6n0Fff
	1jmUeyW75eZ7p2QmvYqUTgMoWup9+4s4iorJinVGVSUBNJ/Am3Nvch9DHDrE
	G+INPiOPe+;
Authentication-Results: sj-dkim-2; header.From=dino@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: RRG <rrg@irtf.org>, Robin Whittle <rw@firstpr.com.au>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

>> From: Dino Farinacci [mailto:dino@cisco.com]
>>> From: Pekka Nikander
>>> What comes to HIP and RRG, I do believe that HIP *could* help in
>>> solving the RRG problem.  It *could* form a core for what people now
>>> call "Strategy B" solutions, and a HIP-proxy based solution *could*
> be
>>> deployed as a "Strategy A" solution.  I don't know the details of
>>> LISP, but the recent discussion between Dino and me seem to indicate
>>> that HIP proxy and LISP xTRs are functionally close enough so that a
>>> HIP proxy could be "plugged in" to the LISP architecture, yielding a
>>> "Strategy A" HIP-based network-level solution that could eventually
>>> lead to full HIP deployment at all hosts, which *could* lead to an
>>> architecture where renumbering is never needed due to full
> transparent
>>> support of multiple IP addresses at all hosts.
>
>> And since I don't know the details of HIP-proxy, saying LISP and HIP-
>> proxy are functionally equivalent only occurs at a conversational
> level.
>> The devil is in the details of course.
>
> I strongly resonate with Pekka's posting.
>
> Speaking solely for myself, I view LISP's original claims to be a
> locator-identifier split to be a redefinition of what those terms have
> historically meant (i.e., to be marketing -- not reality). By  
> contrast,
> HIP is a true locator-identifier split technology in every sense of  
> the
> historic meaning.

Well IDs are used for TCP/UDP socket endpoint demuxing. And RLOCs are  
according to the original definition. But we extended to have IDs  
*also* be routable inside of a site. We had to for incremental  
deployability. We don't want to force renumbering of all site-based  
hosts, switches, routers, firewall devices, etc.

> LISP, by contrast, is a map-and-encaps solution to the RRG problem.

With LISP, you can move a host to a new RLOC while keeping a TCP  
connection up. That is the EID does not have to change for the host.

> There is no necessary relationship between HIP (or any other
> locator-identifier split) and LISP (or any other map-and-encaps).
> Specifically, I believe that locator-identifier splits are a session
> layer concept and therefore are primarily host-related. I believe that
> map-and-encaps is primarily a network layer concept.

Definitely agree on session-layer concept.

> By combining a true locator-identifier split (i.e., HIP) with a
> map-and-encaps (e.g., LISP) one gets the combined benefits of both
> approaches. Those benefits are

But you add another layer of addressing that is probably more than the  
user wants. It could get this bad:

  HIT -> EID -> private-RLOC -> public-RLOC    when behind a NAT

or

  HIT -> private-EID -> public-EID -> RLOC     when behind a NAT

2-levels of mapping is plenty, adding 2 more probably is a non- 
starter. Remember folks, we have to incrementally deploy this with  
minimal cost, see Yakov's post early today, he makes good points.

> *  For HIP-based applications (i.e., hosts) this creates a full
> decoupling of application issues from network issues. This
> simultaneously solves many different problems including the  
> following: a
> transparent solution to application multihoming; complete agnosticism
> concerning network issues including IPv4 or IPv6; strong session
> coherence in the face of substantial mobility; solution to the "IP
> identity problem", thereby solving a great many festering security
> issues including a clean integration with IPsec, providing
> best-current-practice Denial-of-service (DoS) attack resistance,
> exponentially increasing the ability to identify and defend against
> spoofing attacks, substantially increased protection against session
> hijacking, and (by solving the identity problem) making existing
> application authentication and authorization systems become more  
> viable.

And it cleans your dirty dishes as well. ;-)

Eric, care to quantify the cost of deploying all this machinery?

Dino

> *  HIP also provides a formal (secure) delegation capability that
> permits HIP users (e.g., hosts) to delegate authority to other  
> entities
> to act on their behalf. This would, for instance, allow a host that
> wants to hide its current location to use network proxies to forward  
> its
> traffic. For example, DoS attacks could also be deflected to network
> proxies.
>
> *  For map-and-encaps based systems this provides a scalable network
> integration capability to resolve a wide variety of different network
> scalability and integration challenges including:
> 1) IPv4-IPv6 coexistence: ISATAP, Teredo, IPvLX, etc.
> 2) Military Communications Security (COMSEC)
> 3) IPsec's ESP in tunnel mode
> 4) L3VPN (including how my employer relates to our ISPs (please note  
> the
> plural))
> 5) ecommerce
> 6) ARINC 664 enclave protections
> 7) Architectures that leverage IP to join together distributed legacy
> (i.e., non-IP) protocol systems. It is also used to merge legacy
> populations into IP networks (e.g., RFC 1006).
>
> --Eric

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan  5 14:14:24 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 125C728C12C;
	Mon,  5 Jan 2009 14:14:24 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A748428C12C
	for <rrg@core3.amsl.com>; Mon,  5 Jan 2009 14:14:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.206
X-Spam-Level: 
X-Spam-Status: No, score=-6.206 tagged_above=-999 required=5
	tests=[AWL=-0.207, BAYES_00=-2.599, J_CHICKENPOX_13=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id iSxcOUI1liF6 for <rrg@core3.amsl.com>;
	Mon,  5 Jan 2009 14:14:22 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71])
	by core3.amsl.com (Postfix) with ESMTP id 5E0AB28C12B
	for <rrg@irtf.org>; Mon,  5 Jan 2009 14:14:22 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.36,334,1228089600"; d="scan'208";a="119832332"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-2.cisco.com with ESMTP; 05 Jan 2009 22:14:09 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n05ME9rN007114; 
	Mon, 5 Jan 2009 14:14:09 -0800
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n05ME9s8009345;
	Mon, 5 Jan 2009 22:14:09 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Jan 2009 14:14:07 -0800
Received: from moveme.cisco.com ([10.21.149.210]) by
	xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Jan 2009 14:14:07 -0800
Message-Id: <274E9F88-C258-4948-9024-462697DF554A@cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A105623B39@XCH-NW-7V2.nw.nos.boeing.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Mon, 5 Jan 2009 14:14:06 -0800
References: <495F0BAA.2040303@firstpr.com.au><49611E83.8050301@gmail.com><4961CFD3.2050304@firstpr.com.au><D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com><20EEF623-B503-4994-B099-64715E567B2D@cisco.com>
	<474EEBD229DF754FB83D256004D021080AD5E539@XCH-NW-6V1.nw.nos.boeing.com>
	<39C363776A4E8C4A94691D2BD9D1C9A105623AC3@XCH-NW-7V2.nw.nos.boeing.com>
	<4FF36C8D-761D-4D45-BB99-A5E72B9E33C9@cisco.com>
	<39C363776A4E8C4A94691D2BD9D1C9A105623B39@XCH-NW-7V2.nw.nos.boeing.com>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 05 Jan 2009 22:14:07.0446 (UTC)
	FILETIME=[ED4D2F60:01C96F82]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=6497; t=1231193649;
	x=1232057649; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dino@cisco.com;
	z=From:=20Dino=20Farinacci=20<dino@cisco.com>
	|Subject:=20Re=3A=20[rrg]=20Rejecting=20all=20but=20Strateg
	y=20A |Sender:=20;
	bh=0ZgmQD//FCqWx0CoP1owFW9th2bHSqjHGSdEyBNBB8o=;
	b=rPflsNl2ce4sFxcjLecW7p7CVRzHxpr4f1bbYvs9j05HWPE1V7YYSmYWSO
	L2HcxQs3z+WWAvzoaoNWPf1u0k/6wpFvANQ+/dp3erlf4n4NUM0GD3Gka+eo
	YRgIRt56BXpL4enc+z3cjYniV9HBkabRLSJfqUP2KPJrgxD+yt22c=;
Authentication-Results: sj-dkim-1; header.From=dino@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: RRG <rrg@irtf.org>, Robin Whittle <rw@firstpr.com.au>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

>> -----Original Message-----
>> From: Dino Farinacci [mailto:dino@cisco.com]
>> Sent: Monday, January 05, 2009 2:01 PM
>> To: Templin, Fred L
>> Cc: Fleischman, Eric; Pekka Nikander; RRG; Robin Whittle
>> Subject: Re: [rrg] Rejecting all but Strategy A
>>
>> Before we get carried away with what looks like a convergence of  
>> "HIP-
>> proxy and LISP", tell me what HIP offers to a LISP router that the
>> LISP architecture does not already provide?
>
> I was actually saying convergence of "HIP-proxy and xTR";
> xTR does not necessarily mean LISP.

Sorry, I'm not going to let you off that easy. If you don't define xTR  
then you can't way what or what not HIP-proxy can offer it. Because  
"it" might already have the feature, but since you don't want to be  
concrete, you leave it all open ended. Which makes for a non- 
productive conversation.

>> If is solely a add a pure definition to IDs and RLOCs, then I think
>> it's not worth the cost of deployment to do so.
>
> In my understanding there's a lot more to it than that,
> but would welcome clarifications.

Well there really isn't. It's just this list that makes a mountain out  
of a mole-hill.

Dino

>
>
> Fred
> fred.l.templin@boeing.com
>
>>
>> Dino
>>
>> On Jan 5, 2009, at 1:27 PM, Templin, Fred L wrote:
>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: Fleischman, Eric
>>>> Sent: Monday, January 05, 2009 12:13 PM
>>>> To: Dino Farinacci; Pekka Nikander
>>>> Cc: RRG; Robin Whittle
>>>> Subject: Re: [rrg] Rejecting all but Strategy A
>>>>
>>>>
>>>>
>>>>> From: Dino Farinacci [mailto:dino@cisco.com]
>>>>>> From: Pekka Nikander
>>>>>> What comes to HIP and RRG, I do believe that HIP *could* help in
>>>>>> solving the RRG problem.  It *could* form a core for what people
>>>>>> now
>>>>>> call "Strategy B" solutions, and a HIP-proxy based solution
> *could*
>>>> be
>>>>>> deployed as a "Strategy A" solution.  I don't know the details of
>>>>>> LISP, but the recent discussion between Dino and me seem to
>>>>>> indicate
>>>>>> that HIP proxy and LISP xTRs are functionally close enough so
>>>>>> that a
>>>>>> HIP proxy could be "plugged in" to the LISP architecture,
>>>>>> yielding a
>>>>>> "Strategy A" HIP-based network-level solution that could
> eventually
>>>>>> lead to full HIP deployment at all hosts, which *could* lead to  
>>>>>> an
>>>>>> architecture where renumbering is never needed due to full
>>>> transparent
>>>>>> support of multiple IP addresses at all hosts.
>>>>
>>>>> And since I don't know the details of HIP-proxy, saying LISP and
>>>>> HIP-
>>>>> proxy are functionally equivalent only occurs at a conversational
>>>> level.
>>>>> The devil is in the details of course.
>>>>
>>>> I strongly resonate with Pekka's posting.
>>>
>>> Pekka, is "HIP-proxy" and "HIP mobile router" one and the
>>> same thing? If so, IMHO it is absolutely realistic that the
>>> HIP-proxy and xTR could occur on exactly the same platform.
>>> Note that they are complementary functions, however; not
>>> competing ones. I think this also goes with what Eric was
>>> saying below?
>>>
>>> Fred
>>> fred.l.templin@boeing.com
>>>
>>>> Speaking solely for myself, I view LISP's original claims to be a
>>>> locator-identifier split to be a redefinition of what those terms
>>>> have
>>>> historically meant (i.e., to be marketing -- not reality). By
>>>> contrast,
>>>> HIP is a true locator-identifier split technology in every sense of
>>>> the
>>>> historic meaning.
>>>>
>>>> LISP, by contrast, is a map-and-encaps solution to the RRG problem.
>>>>
>>>> There is no necessary relationship between HIP (or any other
>>>> locator-identifier split) and LISP (or any other map-and-encaps).
>>>> Specifically, I believe that locator-identifier splits are a  
>>>> session
>>>> layer concept and therefore are primarily host-related. I believe
>>>> that
>>>> map-and-encaps is primarily a network layer concept.
>>>>
>>>> By combining a true locator-identifier split (i.e., HIP) with a
>>>> map-and-encaps (e.g., LISP) one gets the combined benefits of both
>>>> approaches. Those benefits are
>>>>
>>>> *  For HIP-based applications (i.e., hosts) this creates a full
>>>> decoupling of application issues from network issues. This
>>>> simultaneously solves many different problems including the
>>>> following:
>>> a
>>>> transparent solution to application multihoming; complete
> agnosticism
>>>> concerning network issues including IPv4 or IPv6; strong session
>>>> coherence in the face of substantial mobility; solution to the "IP
>>>> identity problem", thereby solving a great many festering security
>>>> issues including a clean integration with IPsec, providing
>>>> best-current-practice Denial-of-service (DoS) attack resistance,
>>>> exponentially increasing the ability to identify and defend against
>>>> spoofing attacks, substantially increased protection against  
>>>> session
>>>> hijacking, and (by solving the identity problem) making existing
>>>> application authentication and authorization systems become more
>>> viable.
>>>> *  HIP also provides a formal (secure) delegation capability that
>>>> permits HIP users (e.g., hosts) to delegate authority to other
>>>> entities
>>>> to act on their behalf. This would, for instance, allow a host that
>>>> wants to hide its current location to use network proxies to  
>>>> forward
>>> its
>>>> traffic. For example, DoS attacks could also be deflected to  
>>>> network
>>>> proxies.
>>>>
>>>> *  For map-and-encaps based systems this provides a scalable  
>>>> network
>>>> integration capability to resolve a wide variety of different
> network
>>>> scalability and integration challenges including:
>>>> 1) IPv4-IPv6 coexistence: ISATAP, Teredo, IPvLX, etc.
>>>> 2) Military Communications Security (COMSEC)
>>>> 3) IPsec's ESP in tunnel mode
>>>> 4) L3VPN (including how my employer relates to our ISPs (please  
>>>> note
>>> the
>>>> plural))
>>>> 5) ecommerce
>>>> 6) ARINC 664 enclave protections
>>>> 7) Architectures that leverage IP to join together distributed
> legacy
>>>> (i.e., non-IP) protocol systems. It is also used to merge legacy
>>>> populations into IP networks (e.g., RFC 1006).
>>>>
>>>> --Eric
>>>> _______________________________________________
>>>> rrg mailing list
>>>> rrg@irtf.org
>>>> https://www.irtf.org/mailman/listinfo/rrg
>

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan  5 14:26:13 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B0BD93A6A41;
	Mon,  5 Jan 2009 14:26:13 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0787D3A6A41
	for <rrg@core3.amsl.com>; Mon,  5 Jan 2009 14:26:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.15
X-Spam-Level: 
X-Spam-Status: No, score=-6.15 tagged_above=-999 required=5 tests=[AWL=-0.151, 
	BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Ua-m+IRZHQXa for <rrg@core3.amsl.com>;
	Mon,  5 Jan 2009 14:26:11 -0800 (PST)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com
	[130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id C4BF03A6A22
	for <rrg@irtf.org>; Mon,  5 Jan 2009 14:26:11 -0800 (PST)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231])
	by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id n05MPkLg025857
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 5 Jan 2009 14:25:46 -0800 (PST)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	n05MPk7p014046; Mon, 5 Jan 2009 14:25:46 -0800 (PST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	n05MPjbp013982; Mon, 5 Jan 2009 14:25:46 -0800 (PST)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 5 Jan 2009 14:25:45 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 5 Jan 2009 14:25:45 -0800
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A105623B8B@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <274E9F88-C258-4948-9024-462697DF554A@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] Rejecting all but Strategy A
Thread-Index: AclvgvDQtCMuB3rrSfKsbRkAvbEezwAALyMQ
References: <495F0BAA.2040303@firstpr.com.au><49611E83.8050301@gmail.com><4961CFD3.2050304@firstpr.com.au><D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com><20EEF623-B503-4994-B099-64715E567B2D@cisco.com>
	<474EEBD229DF754FB83D256004D021080AD5E539@XCH-NW-6V1.nw.nos.boeing.com>
	<39C363776A4E8C4A94691D2BD9D1C9A105623AC3@XCH-NW-7V2.nw.nos.boeing.com>
	<4FF36C8D-761D-4D45-BB99-A5E72B9E33C9@cisco.com>
	<39C363776A4E8C4A94691D2BD9D1C9A105623B39@XCH-NW-7V2.nw.nos.boeing.com>
	<274E9F88-C258-4948-9024-462697DF554A@cisco.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Dino Farinacci" <dino@cisco.com>
X-OriginalArrivalTime: 05 Jan 2009 22:25:45.0920 (UTC)
	FILETIME=[8D9FDC00:01C96F84]
Cc: RRG <rrg@irtf.org>, Robin Whittle <rw@firstpr.com.au>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Dino,

>-----Original Message-----
>From: Dino Farinacci [mailto:dino@cisco.com]
>Sent: Monday, January 05, 2009 2:14 PM
>To: Templin, Fred L
>Cc: Fleischman, Eric; Pekka Nikander; RRG; Robin Whittle
>Subject: Re: [rrg] Rejecting all but Strategy A
>
>>> -----Original Message-----
>>> From: Dino Farinacci [mailto:dino@cisco.com]
>>> Sent: Monday, January 05, 2009 2:01 PM
>>> To: Templin, Fred L
>>> Cc: Fleischman, Eric; Pekka Nikander; RRG; Robin Whittle
>>> Subject: Re: [rrg] Rejecting all but Strategy A
>>>
>>> Before we get carried away with what looks like a convergence of
>>> "HIP-
>>> proxy and LISP", tell me what HIP offers to a LISP router that the
>>> LISP architecture does not already provide?
>>
>> I was actually saying convergence of "HIP-proxy and xTR";
>> xTR does not necessarily mean LISP.
>
>Sorry, I'm not going to let you off that easy. If you don't define xTR
>then you can't way what or what not HIP-proxy can offer it. Because
>"it" might already have the feature, but since you don't want to be
>concrete, you leave it all open ended. Which makes for a non-
>productive conversation.

All I am saying is that HIP can run over a tunnel virtual
interface (on an "xTR") just the same as it can run over
a physical interface. How the xTR makes its mapping and
encapping decisions to send things over a tunnel virtual
interface is largely orthogonal wrt what HIP brings.

>>> If is solely a add a pure definition to IDs and RLOCs, then I think
>>> it's not worth the cost of deployment to do so.
>>
>> In my understanding there's a lot more to it than that,
>> but would welcome clarifications.
>
>Well there really isn't. It's just this list that makes a mountain out
>of a mole-hill.

No; there really is. For example, that is why I asked
Pekka about HIP mobile router.

If a HIP proxy can do mobility signaling on behalf of
end systems, then that is beyond the capabilities being
offered by just the map-encaps solution.

Fred
fred.l.templin@boeing.com

>Dino
>
>>
>>
>> Fred
>> fred.l.templin@boeing.com
>>
>>>
>>> Dino
>>>
>>> On Jan 5, 2009, at 1:27 PM, Templin, Fred L wrote:
>>>
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: Fleischman, Eric
>>>>> Sent: Monday, January 05, 2009 12:13 PM
>>>>> To: Dino Farinacci; Pekka Nikander
>>>>> Cc: RRG; Robin Whittle
>>>>> Subject: Re: [rrg] Rejecting all but Strategy A
>>>>>
>>>>>
>>>>>
>>>>>> From: Dino Farinacci [mailto:dino@cisco.com]
>>>>>>> From: Pekka Nikander
>>>>>>> What comes to HIP and RRG, I do believe that HIP *could* help in
>>>>>>> solving the RRG problem.  It *could* form a core for what people
>>>>>>> now
>>>>>>> call "Strategy B" solutions, and a HIP-proxy based solution
>> *could*
>>>>> be
>>>>>>> deployed as a "Strategy A" solution.  I don't know the details
of
>>>>>>> LISP, but the recent discussion between Dino and me seem to
>>>>>>> indicate
>>>>>>> that HIP proxy and LISP xTRs are functionally close enough so
>>>>>>> that a
>>>>>>> HIP proxy could be "plugged in" to the LISP architecture,
>>>>>>> yielding a
>>>>>>> "Strategy A" HIP-based network-level solution that could
>> eventually
>>>>>>> lead to full HIP deployment at all hosts, which *could* lead to
>>>>>>> an
>>>>>>> architecture where renumbering is never needed due to full
>>>>> transparent
>>>>>>> support of multiple IP addresses at all hosts.
>>>>>
>>>>>> And since I don't know the details of HIP-proxy, saying LISP and
>>>>>> HIP-
>>>>>> proxy are functionally equivalent only occurs at a conversational
>>>>> level.
>>>>>> The devil is in the details of course.
>>>>>
>>>>> I strongly resonate with Pekka's posting.
>>>>
>>>> Pekka, is "HIP-proxy" and "HIP mobile router" one and the
>>>> same thing? If so, IMHO it is absolutely realistic that the
>>>> HIP-proxy and xTR could occur on exactly the same platform.
>>>> Note that they are complementary functions, however; not
>>>> competing ones. I think this also goes with what Eric was
>>>> saying below?
>>>>
>>>> Fred
>>>> fred.l.templin@boeing.com
>>>>
>>>>> Speaking solely for myself, I view LISP's original claims to be a
>>>>> locator-identifier split to be a redefinition of what those terms
>>>>> have
>>>>> historically meant (i.e., to be marketing -- not reality). By
>>>>> contrast,
>>>>> HIP is a true locator-identifier split technology in every sense
of
>>>>> the
>>>>> historic meaning.
>>>>>
>>>>> LISP, by contrast, is a map-and-encaps solution to the RRG
problem.
>>>>>
>>>>> There is no necessary relationship between HIP (or any other
>>>>> locator-identifier split) and LISP (or any other map-and-encaps).
>>>>> Specifically, I believe that locator-identifier splits are a
>>>>> session
>>>>> layer concept and therefore are primarily host-related. I believe
>>>>> that
>>>>> map-and-encaps is primarily a network layer concept.
>>>>>
>>>>> By combining a true locator-identifier split (i.e., HIP) with a
>>>>> map-and-encaps (e.g., LISP) one gets the combined benefits of both
>>>>> approaches. Those benefits are
>>>>>
>>>>> *  For HIP-based applications (i.e., hosts) this creates a full
>>>>> decoupling of application issues from network issues. This
>>>>> simultaneously solves many different problems including the
>>>>> following:
>>>> a
>>>>> transparent solution to application multihoming; complete
>> agnosticism
>>>>> concerning network issues including IPv4 or IPv6; strong session
>>>>> coherence in the face of substantial mobility; solution to the "IP
>>>>> identity problem", thereby solving a great many festering security
>>>>> issues including a clean integration with IPsec, providing
>>>>> best-current-practice Denial-of-service (DoS) attack resistance,
>>>>> exponentially increasing the ability to identify and defend
against
>>>>> spoofing attacks, substantially increased protection against
>>>>> session
>>>>> hijacking, and (by solving the identity problem) making existing
>>>>> application authentication and authorization systems become more
>>>> viable.
>>>>> *  HIP also provides a formal (secure) delegation capability that
>>>>> permits HIP users (e.g., hosts) to delegate authority to other
>>>>> entities
>>>>> to act on their behalf. This would, for instance, allow a host
that
>>>>> wants to hide its current location to use network proxies to
>>>>> forward
>>>> its
>>>>> traffic. For example, DoS attacks could also be deflected to
>>>>> network
>>>>> proxies.
>>>>>
>>>>> *  For map-and-encaps based systems this provides a scalable
>>>>> network
>>>>> integration capability to resolve a wide variety of different
>> network
>>>>> scalability and integration challenges including:
>>>>> 1) IPv4-IPv6 coexistence: ISATAP, Teredo, IPvLX, etc.
>>>>> 2) Military Communications Security (COMSEC)
>>>>> 3) IPsec's ESP in tunnel mode
>>>>> 4) L3VPN (including how my employer relates to our ISPs (please
>>>>> note
>>>> the
>>>>> plural))
>>>>> 5) ecommerce
>>>>> 6) ARINC 664 enclave protections
>>>>> 7) Architectures that leverage IP to join together distributed
>> legacy
>>>>> (i.e., non-IP) protocol systems. It is also used to merge legacy
>>>>> populations into IP networks (e.g., RFC 1006).
>>>>>
>>>>> --Eric
>>>>> _______________________________________________
>>>>> rrg mailing list
>>>>> rrg@irtf.org
>>>>> https://www.irtf.org/mailman/listinfo/rrg
>>

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan  5 15:17:59 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EC1CD3A68D5;
	Mon,  5 Jan 2009 15:17:58 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8F6403A6836
	for <rrg@core3.amsl.com>; Mon,  5 Jan 2009 15:17:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.182
X-Spam-Level: 
X-Spam-Status: No, score=-6.182 tagged_above=-999 required=5
	tests=[AWL=-0.183, BAYES_00=-2.599, J_CHICKENPOX_13=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id e6ydxMHLWMJU for <rrg@core3.amsl.com>;
	Mon,  5 Jan 2009 15:17:56 -0800 (PST)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com
	[130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id 667FC3A68A5
	for <rrg@irtf.org>; Mon,  5 Jan 2009 15:17:56 -0800 (PST)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231])
	by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id n05NHSjh014660
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);
	Mon, 5 Jan 2009 15:17:33 -0800 (PST)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	n05NHSfY026068; Mon, 5 Jan 2009 15:17:28 -0800 (PST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	n05NHSv6026064; Mon, 5 Jan 2009 15:17:28 -0800 (PST)
Received: from XCH-NW-6V1.nw.nos.boeing.com ([130.247.55.53]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 5 Jan 2009 15:17:21 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 5 Jan 2009 15:17:19 -0800
Message-ID: <474EEBD229DF754FB83D256004D021080AD5E7F7@XCH-NW-6V1.nw.nos.boeing.com>
In-Reply-To: <E294A8E4-57E3-48D3-BE17-B0EF2BD46DA4@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] Rejecting all but Strategy A
Thread-Index: AclvgrJG3UWoq6fcSWyv5YM3xOFIAgAAEcDw
References: <495F0BAA.2040303@firstpr.com.au>
	<49611E83.8050301@gmail.com><4961CFD3.2050304@firstpr.com.au><D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com>
	<20EEF623-B503-4994-B099-64715E567B2D@cisco.com>
	<474EEBD229DF754FB83D256004D021080AD5E539@XCH-NW-6V1.nw.nos.boeing.com>
	<E294A8E4-57E3-48D3-BE17-B0EF2BD46DA4@cisco.com>
From: "Fleischman, Eric" <eric.fleischman@boeing.com>
To: "Dino Farinacci" <dino@cisco.com>
X-OriginalArrivalTime: 05 Jan 2009 23:17:21.0768 (UTC)
	FILETIME=[C2E4C680:01C96F8B]
Cc: RRG <rrg@irtf.org>, Robin Whittle <rw@firstpr.com.au>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Dino,

I don't know the operational cost of HIP in stable networked
environments because our many laboratory experiments have focused on
very high mobility environments where the HIP overheads are trivial
compared with the multiple advantages of using HIP (i.e., without HIP
the applications become very brittle). 

We have operationally deployed HIP as a basis for securing our
IP-connected SCADA machine controllers in our factories. This is the
most viable way to secure IP networked-attached SCADA devices that we
know about. Again, the operational costs of doing this are trivial
compared with the risks with leaving these machines inadequately
secured. 

I myself am not aware of the NAT impacts to HIP though I have noted (but
not yet read) the existence of a HIP I-D on that topic (see
http://www.ietf.org/internet-drafts/draft-ietf-hip-nat-traversal-05.txt)
. I suspect that you are overstating the problems with NATs because HIP
has proven to be surprisingly clean and the HIP proxy capability is
powerful. However, I myself have not envisioned using HIP in
environments having NATs except for the narrow context of overcoming
ARINC 664-based limitations impacting aircraft's generic (public) IP
addresses.

By contrast, the more significant issue in civil aviation is whether the
aeronautical air-to-ground and air-to-air networking will occur within
the context of VPNs (i.e., hierarchical routing/addressing systems
perhaps resembling military COMSEC; e.g., each VPN domain perhaps
associated with a specific ARINC 664 intra-aircraft partition) or
whether the civil aviation addressing/routing will alternatively be a
common (flat) system with the intra-aircraft partitions accomplished by
air-gaps and firewalls.

--Eric

-----Original Message-----
From: Dino Farinacci [mailto:dino@cisco.com] 
Sent: Monday, January 05, 2009 2:12 PM
To: Fleischman, Eric
Cc: Pekka Nikander; RRG; Robin Whittle
Subject: Re: [rrg] Rejecting all but Strategy A

>> From: Dino Farinacci [mailto:dino@cisco.com]
>>> From: Pekka Nikander
>>> What comes to HIP and RRG, I do believe that HIP *could* help in 
>>> solving the RRG problem.  It *could* form a core for what people now

>>> call "Strategy B" solutions, and a HIP-proxy based solution *could*
> be
>>> deployed as a "Strategy A" solution.  I don't know the details of 
>>> LISP, but the recent discussion between Dino and me seem to indicate

>>> that HIP proxy and LISP xTRs are functionally close enough so that a

>>> HIP proxy could be "plugged in" to the LISP architecture, yielding a

>>> "Strategy A" HIP-based network-level solution that could eventually 
>>> lead to full HIP deployment at all hosts, which *could* lead to an 
>>> architecture where renumbering is never needed due to full
> transparent
>>> support of multiple IP addresses at all hosts.
>
>> And since I don't know the details of HIP-proxy, saying LISP and HIP-

>> proxy are functionally equivalent only occurs at a conversational
> level.
>> The devil is in the details of course.
>
> I strongly resonate with Pekka's posting.
>
> Speaking solely for myself, I view LISP's original claims to be a 
> locator-identifier split to be a redefinition of what those terms have

> historically meant (i.e., to be marketing -- not reality). By 
> contrast, HIP is a true locator-identifier split technology in every 
> sense of the historic meaning.

Well IDs are used for TCP/UDP socket endpoint demuxing. And RLOCs are
according to the original definition. But we extended to have IDs
*also* be routable inside of a site. We had to for incremental
deployability. We don't want to force renumbering of all site-based
hosts, switches, routers, firewall devices, etc.

> LISP, by contrast, is a map-and-encaps solution to the RRG problem.

With LISP, you can move a host to a new RLOC while keeping a TCP
connection up. That is the EID does not have to change for the host.

> There is no necessary relationship between HIP (or any other 
> locator-identifier split) and LISP (or any other map-and-encaps).
> Specifically, I believe that locator-identifier splits are a session 
> layer concept and therefore are primarily host-related. I believe that

> map-and-encaps is primarily a network layer concept.

Definitely agree on session-layer concept.

> By combining a true locator-identifier split (i.e., HIP) with a 
> map-and-encaps (e.g., LISP) one gets the combined benefits of both 
> approaches. Those benefits are

But you add another layer of addressing that is probably more than the
user wants. It could get this bad:

  HIT -> EID -> private-RLOC -> public-RLOC    when behind a NAT

or

  HIT -> private-EID -> public-EID -> RLOC     when behind a NAT

2-levels of mapping is plenty, adding 2 more probably is a non- starter.
Remember folks, we have to incrementally deploy this with minimal cost,
see Yakov's post early today, he makes good points.

> *  For HIP-based applications (i.e., hosts) this creates a full 
> decoupling of application issues from network issues. This 
> simultaneously solves many different problems including the
> following: a
> transparent solution to application multihoming; complete agnosticism 
> concerning network issues including IPv4 or IPv6; strong session 
> coherence in the face of substantial mobility; solution to the "IP 
> identity problem", thereby solving a great many festering security 
> issues including a clean integration with IPsec, providing 
> best-current-practice Denial-of-service (DoS) attack resistance, 
> exponentially increasing the ability to identify and defend against 
> spoofing attacks, substantially increased protection against session 
> hijacking, and (by solving the identity problem) making existing 
> application authentication and authorization systems become more 
> viable.

And it cleans your dirty dishes as well. ;-)

Eric, care to quantify the cost of deploying all this machinery?

Dino

> *  HIP also provides a formal (secure) delegation capability that 
> permits HIP users (e.g., hosts) to delegate authority to other 
> entities to act on their behalf. This would, for instance, allow a 
> host that wants to hide its current location to use network proxies to

> forward its traffic. For example, DoS attacks could also be deflected 
> to network proxies.
>
> *  For map-and-encaps based systems this provides a scalable network 
> integration capability to resolve a wide variety of different network 
> scalability and integration challenges including:
> 1) IPv4-IPv6 coexistence: ISATAP, Teredo, IPvLX, etc.
> 2) Military Communications Security (COMSEC)
> 3) IPsec's ESP in tunnel mode
> 4) L3VPN (including how my employer relates to our ISPs (please note 
> the
> plural))
> 5) ecommerce
> 6) ARINC 664 enclave protections
> 7) Architectures that leverage IP to join together distributed legacy 
> (i.e., non-IP) protocol systems. It is also used to merge legacy 
> populations into IP networks (e.g., RFC 1006).
>
> --Eric

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan  5 15:50:01 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 621983A682A;
	Mon,  5 Jan 2009 15:50:01 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D5BB93A682A
	for <rrg@core3.amsl.com>; Mon,  5 Jan 2009 15:50:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.198
X-Spam-Level: 
X-Spam-Status: No, score=-6.198 tagged_above=-999 required=5
	tests=[AWL=-0.199, BAYES_00=-2.599, J_CHICKENPOX_13=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id jCOwxKEAEHPe for <rrg@core3.amsl.com>;
	Mon,  5 Jan 2009 15:49:59 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id A98EC3A677E
	for <rrg@irtf.org>; Mon,  5 Jan 2009 15:49:59 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.36,334,1228089600"; d="scan'208";a="125115017"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-1.cisco.com with ESMTP; 05 Jan 2009 23:49:47 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n05NnjPs022567; 
	Mon, 5 Jan 2009 15:49:45 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n05NnfTL028718;
	Mon, 5 Jan 2009 23:49:45 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Jan 2009 15:49:45 -0800
Received: from moveme.cisco.com ([10.21.149.210]) by
	xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Jan 2009 15:49:44 -0800
Message-Id: <6565A0E6-FBA5-4769-A19C-4B83B20C4C8E@cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: "Fleischman, Eric" <eric.fleischman@boeing.com>
In-Reply-To: <474EEBD229DF754FB83D256004D021080AD5E7F7@XCH-NW-6V1.nw.nos.boeing.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Mon, 5 Jan 2009 15:49:44 -0800
References: <495F0BAA.2040303@firstpr.com.au>
	<49611E83.8050301@gmail.com><4961CFD3.2050304@firstpr.com.au><D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com>
	<20EEF623-B503-4994-B099-64715E567B2D@cisco.com>
	<474EEBD229DF754FB83D256004D021080AD5E539@XCH-NW-6V1.nw.nos.boeing.com>
	<E294A8E4-57E3-48D3-BE17-B0EF2BD46DA4@cisco.com>
	<474EEBD229DF754FB83D256004D021080AD5E7F7@XCH-NW-6V1.nw.nos.boeing.com>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 05 Jan 2009 23:49:44.0849 (UTC)
	FILETIME=[490F6810:01C96F90]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=6849; t=1231199385;
	x=1232063385; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dino@cisco.com;
	z=From:=20Dino=20Farinacci=20<dino@cisco.com>
	|Subject:=20Re=3A=20[rrg]=20Rejecting=20all=20but=20Strateg
	y=20A |Sender:=20;
	bh=48uwTO75fj7XE59FYkScv/+opEucQlm9/umnmH2oOYM=;
	b=geOFk9/OsPOK7vr7OEVOPdATKTrJATxP4+eHQB/LgZAVFEh0EAi88BhXVx
	vPtj5uqvgf6sjgacJkdbDE0MwCBqSFpxwhKCNP3/pdK29t6Vl1kyKpiUg3x0
	cEK82p/LGTerTiIgLBbiUQYoOleaAn8ibqjUPq51sZdsB9r3gvdKQ=;
Authentication-Results: sj-dkim-1; header.From=dino@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: RRG <rrg@irtf.org>, Robin Whittle <rw@firstpr.com.au>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

> I myself am not aware of the NAT impacts to HIP though I have noted  
> (but
> not yet read) the existence of a HIP I-D on that topic (see
> http://www.ietf.org/internet-drafts/draft-ietf-hip-nat-traversal-05.txt)
> . I suspect that you are overstating the problems with NATs because  
> HIP
> has proven to be surprisingly clean and the HIP proxy capability is
> powerful. However, I myself have not envisioned using HIP in
> environments having NATs except for the narrow context of overcoming
> ARINC 664-based limitations impacting aircraft's generic (public) IP
> addresses.

I am not making a claim or judgement call about HIP with NATs. I was  
making a statement about HIP coupled with a map-n-encap scheme with  
NATs.

Dino

> By contrast, the more significant issue in civil aviation is whether  
> the
> aeronautical air-to-ground and air-to-air networking will occur within
> the context of VPNs (i.e., hierarchical routing/addressing systems
> perhaps resembling military COMSEC; e.g., each VPN domain perhaps
> associated with a specific ARINC 664 intra-aircraft partition) or
> whether the civil aviation addressing/routing will alternatively be a
> common (flat) system with the intra-aircraft partitions accomplished  
> by
> air-gaps and firewalls.
>
> --Eric
>
> -----Original Message-----
> From: Dino Farinacci [mailto:dino@cisco.com]
> Sent: Monday, January 05, 2009 2:12 PM
> To: Fleischman, Eric
> Cc: Pekka Nikander; RRG; Robin Whittle
> Subject: Re: [rrg] Rejecting all but Strategy A
>
>>> From: Dino Farinacci [mailto:dino@cisco.com]
>>>> From: Pekka Nikander
>>>> What comes to HIP and RRG, I do believe that HIP *could* help in
>>>> solving the RRG problem.  It *could* form a core for what people  
>>>> now
>
>>>> call "Strategy B" solutions, and a HIP-proxy based solution *could*
>> be
>>>> deployed as a "Strategy A" solution.  I don't know the details of
>>>> LISP, but the recent discussion between Dino and me seem to  
>>>> indicate
>
>>>> that HIP proxy and LISP xTRs are functionally close enough so  
>>>> that a
>
>>>> HIP proxy could be "plugged in" to the LISP architecture,  
>>>> yielding a
>
>>>> "Strategy A" HIP-based network-level solution that could eventually
>>>> lead to full HIP deployment at all hosts, which *could* lead to an
>>>> architecture where renumbering is never needed due to full
>> transparent
>>>> support of multiple IP addresses at all hosts.
>>
>>> And since I don't know the details of HIP-proxy, saying LISP and  
>>> HIP-
>
>>> proxy are functionally equivalent only occurs at a conversational
>> level.
>>> The devil is in the details of course.
>>
>> I strongly resonate with Pekka's posting.
>>
>> Speaking solely for myself, I view LISP's original claims to be a
>> locator-identifier split to be a redefinition of what those terms  
>> have
>
>> historically meant (i.e., to be marketing -- not reality). By
>> contrast, HIP is a true locator-identifier split technology in every
>> sense of the historic meaning.
>
> Well IDs are used for TCP/UDP socket endpoint demuxing. And RLOCs are
> according to the original definition. But we extended to have IDs
> *also* be routable inside of a site. We had to for incremental
> deployability. We don't want to force renumbering of all site-based
> hosts, switches, routers, firewall devices, etc.
>
>> LISP, by contrast, is a map-and-encaps solution to the RRG problem.
>
> With LISP, you can move a host to a new RLOC while keeping a TCP
> connection up. That is the EID does not have to change for the host.
>
>> There is no necessary relationship between HIP (or any other
>> locator-identifier split) and LISP (or any other map-and-encaps).
>> Specifically, I believe that locator-identifier splits are a session
>> layer concept and therefore are primarily host-related. I believe  
>> that
>
>> map-and-encaps is primarily a network layer concept.
>
> Definitely agree on session-layer concept.
>
>> By combining a true locator-identifier split (i.e., HIP) with a
>> map-and-encaps (e.g., LISP) one gets the combined benefits of both
>> approaches. Those benefits are
>
> But you add another layer of addressing that is probably more than the
> user wants. It could get this bad:
>
>  HIT -> EID -> private-RLOC -> public-RLOC    when behind a NAT
>
> or
>
>  HIT -> private-EID -> public-EID -> RLOC     when behind a NAT
>
> 2-levels of mapping is plenty, adding 2 more probably is a non-  
> starter.
> Remember folks, we have to incrementally deploy this with minimal  
> cost,
> see Yakov's post early today, he makes good points.
>
>> *  For HIP-based applications (i.e., hosts) this creates a full
>> decoupling of application issues from network issues. This
>> simultaneously solves many different problems including the
>> following: a
>> transparent solution to application multihoming; complete agnosticism
>> concerning network issues including IPv4 or IPv6; strong session
>> coherence in the face of substantial mobility; solution to the "IP
>> identity problem", thereby solving a great many festering security
>> issues including a clean integration with IPsec, providing
>> best-current-practice Denial-of-service (DoS) attack resistance,
>> exponentially increasing the ability to identify and defend against
>> spoofing attacks, substantially increased protection against session
>> hijacking, and (by solving the identity problem) making existing
>> application authentication and authorization systems become more
>> viable.
>
> And it cleans your dirty dishes as well. ;-)
>
> Eric, care to quantify the cost of deploying all this machinery?
>
> Dino
>
>> *  HIP also provides a formal (secure) delegation capability that
>> permits HIP users (e.g., hosts) to delegate authority to other
>> entities to act on their behalf. This would, for instance, allow a
>> host that wants to hide its current location to use network proxies  
>> to
>
>> forward its traffic. For example, DoS attacks could also be deflected
>> to network proxies.
>>
>> *  For map-and-encaps based systems this provides a scalable network
>> integration capability to resolve a wide variety of different network
>> scalability and integration challenges including:
>> 1) IPv4-IPv6 coexistence: ISATAP, Teredo, IPvLX, etc.
>> 2) Military Communications Security (COMSEC)
>> 3) IPsec's ESP in tunnel mode
>> 4) L3VPN (including how my employer relates to our ISPs (please note
>> the
>> plural))
>> 5) ecommerce
>> 6) ARINC 664 enclave protections
>> 7) Architectures that leverage IP to join together distributed legacy
>> (i.e., non-IP) protocol systems. It is also used to merge legacy
>> populations into IP networks (e.g., RFC 1006).
>>
>> --Eric
>

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan  5 17:09:35 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3A7723A65A5;
	Mon,  5 Jan 2009 17:09:35 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 735BC3A65A5
	for <rrg@core3.amsl.com>; Mon,  5 Jan 2009 17:09:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.826
X-Spam-Level: 
X-Spam-Status: No, score=-0.826 tagged_above=-999 required=5
	tests=[AWL=-0.420, BAYES_05=-1.11, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id AcW5-RHwcz5f for <rrg@core3.amsl.com>;
	Mon,  5 Jan 2009 17:09:32 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123])
	by core3.amsl.com (Postfix) with ESMTP id 69F533A63D2
	for <rrg@irtf.org>; Mon,  5 Jan 2009 17:09:31 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6])
	by gair.firstpr.com.au (Postfix) with ESMTP id E3531175AC3;
	Tue,  6 Jan 2009 12:09:16 +1100 (EST)
Message-ID: <4962AF3D.30400@firstpr.com.au>
Date: Tue, 06 Jan 2009 12:09:17 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: Yakov Rekhter <yakov@juniper.net>, 'RRG' <rrg@irtf.org>
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com><87D9F0BA2807456A88B0427241A29F65@ad.redback.com><3c3e3fca0901021219t2ab35dfsb2532e0c89be84af@mail.gmail.com><E99E41EB33084B5B899C7EED9DE607E9@ad.redback.com><3c3e3fca0901021334j22d17e54iec4bbf41b6c00480@mail.gmail.com>	<BCFF32A1356842BF839C7DF7D059F15F@ad.redback.com>	<3525C9833C09ED418C6FD6CD9514668C0566045E@emailwf1.jnpr.net>	<354C0AE786D1424C886C4A3570611291@ad.redback.com>
	<200901051509.n05F9nM02828@magenta.juniper.net>
In-Reply-To: <200901051509.n05F9nM02828@magenta.juniper.net>
Subject: Re: [rrg] BGP scaling limit? Mobility, RLDRAM
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Replying to    Yakov Rekhter:  Mobility for billions of users.

                               Whether the current system is
                               "acceptable".

                               RLDRAM (Reduced Latency Dynamic RAM)
                               is not much faster than DDR SDRAM.

               Eliot Lear:     RLDRAM costs.

Hi Yakov,

You wrote:

>> The current system is unacceptable since it doesn't fit the needs
>> of many end-user networks.
>
> The current system is *acceptable* to a very large number of users
> - for number of users for whom the current system is acceptable
> just count the number of users in the Internet.

OK - everyone who uses the Internet accepts it as it is, because
there is no alternative.

We are attempting to redesign the Net so that in the decades to come
the needs and desires of end-users will be better met.  I think one
important thing we need to provide is much easier access to
multihoming than is currently possible.  In that sense, I meant that
"the current system" is unacceptable - *we* shouldn't accept the
current difficulties with multihoming as something which should
remain in the decades to come.

This is a restatement of:

>> In the long term, we need to enhance the architecture of the Net
>> to cope happily with a much larger growth in the numbers of
>> end-user networks which have multihoming, TE and portability.

By "portability" I meant keeping the the network's address range when
selecting another ISP.  Renumbering can never be anywhere near as
inexpensive and risk-free as not having to renumber - in part because
network addresses appear in all sorts of places, including DNS files
and ACLs in other networks.

> Some folks think that the (large) majority of users will be mobile
> devices.

I do, since I think there is a huge demand and that it will be
perfectly feasible to achieve this - with both IPv4 and IPv6.  IPv6
or at least something other than IPv4 is needed for billions of
cell-phone / media-players / PCs.

The desire, demand, need or whatever for physical mobility -
including with session continuity during all physical movements and
access network changes - is very strong indeed.  I think the demand
is worth hundreds of billions of dollars (to whoever satisfies it) -
just like in the cellphone industry.

> If that is indeed the case, then one should ask whether
> the current solution for supporting host mobility (Mobile IP) is
> viewed as adequate for this scenario.

I don't think it is adequate for supporting global mobility with each
host retaining its IP address(es) year after year, while achieving
generally optimal path lengths for all packets.

> As if not, then enhancing the architecture without taking into
> account the need to provide an adequate support for a (very) large
> number of mobile hosts would be rather myopic.

I agree.  Steve Russert and I wrote:

  TTR Mobility Extensions for Core-Edge Separation Solutions to the
  Internet's Routing Scaling Problem  (2008-08-25)
  http://www.firstpr.com.au/ip/ivip/TTR-Mobility.pdf

This imposes no architectural complications on the basic Ivip
core-edge separation scalable routing solution.  It extends it with a
type of ETRs called a Translating Tunnel Router.  Mobile hosts,
connecting by any means whatsoever - including Mobile IP - choose a
TTR physically and topologically nearby, such as 1000km or less.
They create one or more tunnels to the TTR, which acts as an ETR and
also sends outgoing packets to the rest of the Net.

There would be extra mapping changes in such a system, but the
mapping changes are only needed infrequently - such as when the
mobile node moves so much as to benefit from a closer TTR.  Mapping
changes are not required when the MN changes its access networks, as
long as they are all close nought to the current TTR.

In Ivip, each mapping change is paid for by the end-user - so the
mapping changes of mobile users will pay their way, and indeed help
make the overall Ivip system profitable for its operators.


Quoting Tony Li:

  http://www.irtf.org/pipermail/rrg/2009-January/000674.html

>> The growth rate of prefixes that are circulating within the DFZ exceeds the
>> rate of speed improvement in the underlying DRAM that we use to implement
>> the control plane.  This will undoubtedly result in architectural changes
>> and cost increases.  The concern then becomes that over the long term, as
>> this continues, the cost increases must be absorbed somewhere in the system,
>> and it is most likely to propagate to the end users, with a net detriment to
>> the growth of the network.
> 
> Few points:
> 
>  - The above assumes that DRAM will continue to be used to implement control 
>    plane memory. As had been discussed before on this list, DRAM is not the 
>    only option  - another alternative is RLDRAM. 

A 2006-02 article comparing Reduced Latency DRAM and Quad Data Rate
SRAM is:

http://www.networksystemsdesignline.com/shared/article/showArticle.jhtml?articleId=180200010

RLDRAM provides only marginal improvements.  There is still a long
cycle time due to the need to precharge the sense amplifiers.
Splitting the chip into different independent segments helps
somewhat, but the cycle time is still a limitation when reading or
writing to the same segment in quick succession.

QDR SRAM has no such problem - reads and writes can follow one after
the other every 3nsec or so, as I wrote:

  http://www.irtf.org/pipermail/rrg/2008-December/000632.html

Looking at the latest Micron parts

  http://www.micron.com/products/dram/rldram/partlist

There is a 575M bit RLDRAM II chip and less than 2ns "cycle times" -
but that is the interface cycle time.  Looking at the datasheet:

  http://download.micron.com/pdf/datasheets/rldram/MT49H16M36A.pdf

the cycle time between successive reads is 15ns.

This is only marginally less than for the latest PC-style DDR3 SDRAMs:

  http://www.micron.com/products/dram/ddr3/partlist.aspx

The fanciest of these is the 4G bit (twin chip) MT41J1G4.  The timing
information is found in the top link at the right from:

  http://www.micron.com/products/partdetail?part=MT41J512M8THU-15E

A 170 page data sheet for a memory chip . . .

I spent 15 minutes looking at this and couldn't easily find the cycle
time of interest.  The read latency (CL) figures on page 1 are 13ns
to 15ns.  This is the delay in producing the first read data.  The
total cycle time before another read or write could be performed
would be longer than this.  I guess 20 to 25 nsec.

RLDRAMs are less dense (a factor of 4 is evident in the above chips)
than DDR3 SDRAM.  This is partly a function of the massive demand for
the latter, which is likely to remain, since SDRAMs are highly
optimised for filling the on-chip caches of Pentium, Core, AMD etc.
mass market 32/64 bit CPUs.


I agree with the rest of your message.

However, I think our target shouldn't be keeping up with current
rates of growth in multihomed end-user networks, but in meeting the
real demand - which is much higher than the small subset who overcome
the currently very steep cost and administrative barriers to get
their own PI prefixes advertised in the DFZ.


Eliot wrote:

> Now I know nothing about RLDRAM, but I'll hazard a guess that it is
> at least for now more expensive than DRAM.

You can bet your sweet bippy on that - now and in the future.

As noted above, the latest Micron RLDRAM chips have 1/4 the capacity
of their DDR3 SDRAM contempories.

RLDRAM only provides marginal speed increases, but the chips have
fancier interfaces, since they allow all address bits to presented in
a single cycle, in contrast to the decades old DRAM tradition of
clocking the address bits in two cycles on half the number of pins.

Digikey has Micron 288M bit RLDRAM (MT49H8M36FM-25 TR in a 144 "pin"
Ball Grid Array package) for USD$52 in 1k quantities.

A Micron 1G bit DDR3 DRAM (MT41J256M4HX-187E:D TR in a 78 "pin" BGA
package) costs USD$9.40 in 2k quantities.

On this basis, the raw cost ratio between RLDRAM and DDR3 SDRAM is:

  (52 / 288) / (9.4 / 1024) = 19.6.

However, the larger size of the RLDRAM packages, and the fact that
four times as many packages are needed for a given amount of data,
means the real cost of using RLDRAM relative to DDR3 DRAM is higher
still.  Furthermore, RLDRAM would involve greater power supply costs,
heat dissipation, cooling costs etc.

Since RLDRAM provides only a marginally faster total cycle time
between reads or writes, I would say these costs are prohibitive.

A better option would be to go straight to QDR SRAM, which is
probably the same or somewhat higher price than RLDRAM, and has a
much shorter cycle time (3ns) between successive reads and/or writes.

 - Robin
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan  5 17:38:22 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EB3AA3A68D5;
	Mon,  5 Jan 2009 17:38:21 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6A8923A68D5
	for <rrg@core3.amsl.com>; Mon,  5 Jan 2009 17:38:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.965
X-Spam-Level: 
X-Spam-Status: No, score=-1.965 tagged_above=-999 required=5 tests=[AWL=0.012, 
	BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id cmcTZcwDpKzK for <rrg@core3.amsl.com>;
	Mon,  5 Jan 2009 17:38:20 -0800 (PST)
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.177])
	by core3.amsl.com (Postfix) with ESMTP id BB5C13A63D2
	for <rrg@irtf.org>; Mon,  5 Jan 2009 17:38:20 -0800 (PST)
Received: by wa-out-1112.google.com with SMTP id j37so4323019waf.23
	for <rrg@irtf.org>; Mon, 05 Jan 2009 17:38:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:sender
	:to:subject:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references
	:x-google-sender-auth;
	bh=0E8Ge5wAxBY2M8TD1rhZFZTxzftUIibBLzks1jJDTk0=;
	b=h5DGxXqRe/P8EFsCKZMy9fbTsBrInIs7T2eUeMFYdyT7v0AjugHcKFSt9NR0DhBqYu
	QP+XQBxpF5CTlXiENm696dzV5p9/NzIvWG5EIRpRUlXGJkpJZl6PJ13hmxzR+fldBFEa
	of2sq2K2VY9Jfl75lX+J5mte8GWXlKX7aI+KM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:sender:to:subject:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references:x-google-sender-auth;
	b=NuAPO/Znkpw/3FFVuobqyuArmcVgvGusANI4+OoWwYE0fBrtTzU5Gr2klZ/aJN0Zeu
	HxDpJtIVkwhxvTg6CW/iHwQFVCELBkNTpPAba2E0SNze8L/VcbuvJlzX9gA5zfq+sK6R
	CiZiW0kgj+Ezl73A4E0FXl4X6+N8PDtMRRqcc=
Received: by 10.114.72.1 with SMTP id u1mr14198207waa.39.1231205886820;
	Mon, 05 Jan 2009 17:38:06 -0800 (PST)
Received: by 10.115.74.12 with HTTP; Mon, 5 Jan 2009 17:38:06 -0800 (PST)
Message-ID: <3c3e3fca0901051738p2e39816bp2466765722e0c803@mail.gmail.com>
Date: Mon, 5 Jan 2009 20:38:06 -0500
From: "William Herrin" <bill@herrin.us>
To: RRG <rrg@irtf.org>
In-Reply-To: <3c3e3fca0901051722l46bb0196pfb87eaba35c753ee@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <200901051509.n05F9nM02828@magenta.juniper.net>
	<Pine.GSO.4.20.0901051209330.29070-100000@meno.corp.us.uu.net>
	<3c3e3fca0901051722l46bb0196pfb87eaba35c753ee@mail.gmail.com>
X-Google-Sender-Auth: 7f8b368694c9c6e4
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

> On Mon, Jan 5, 2009 at 3:00 PM, Jason Schiller <schiller@uu.net> wrote:
>> 1. What pricing model do vendors use for routers such that a moderately
>> low end CPE that can carry multiple views of full routes (think cisco
>> 7200 for customer with a single T1 to each of four different
>> providers) remains affordable to small enterprises without making the cost
>> of high end routes grow logarithmically as they keep up with table growth.

Jason,

I'm picking a nit but...

A Cisco 7200 is overkill for a customer today running 4 BGP sessions
over 4 T1's. A 2811 is more than capable of the task. For anyone not
familiar with it, the 2811 is this generation's version of the 2500
series. In the described configuration it costs $2000-$3000 depending
on how carefully you shop.

Regards,
Bill Herrin


-- 
William D. Herrin ................ herrin@dirtside.com  bill@herrin.us
3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
Falls Church, VA 22042-3004
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan  5 17:40:46 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6C9433A6958;
	Mon,  5 Jan 2009 17:40:46 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A45FE3A6958
	for <rrg@core3.amsl.com>; Mon,  5 Jan 2009 17:40:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.966
X-Spam-Level: 
X-Spam-Status: No, score=-1.966 tagged_above=-999 required=5 tests=[AWL=0.011, 
	BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 64FJjH3S8Dit for <rrg@core3.amsl.com>;
	Mon,  5 Jan 2009 17:40:44 -0800 (PST)
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.176])
	by core3.amsl.com (Postfix) with ESMTP id 16A3D3A63D2
	for <rrg@irtf.org>; Mon,  5 Jan 2009 17:40:44 -0800 (PST)
Received: by wa-out-1112.google.com with SMTP id j37so4323517waf.23
	for <rrg@irtf.org>; Mon, 05 Jan 2009 17:40:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:sender
	:to:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references
	:x-google-sender-auth;
	bh=BVMNcfGH58vH3IbpFZfB5MjMjXbVbyXaRO118P0ALzo=;
	b=gcAPdLgJ9Ofb3Xt+KWIo0m2/6M+4SxO6EwHLLHRZnd4/YwryKov3WOPBVWSVafR2z+
	3Q7SLOnFl5gsA21FVe5VE58A+BWaIDoQNyrAZL5yiHcuDfbZi1gyQaoLKGv1wuPvQnxe
	YYpqLKdejBnNuJb0DHjFu4zQi/HSiR8sK8cUc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references:x-google-sender-auth;
	b=E4HLOGZ7gtya14HsMshhitTwAhpJdsa0uVWkQD4nfno0n+jLnrVmcJEkhIRPRQoGXb
	pFp9nZZlGWfu7535dctN9POneM0teGV7YZbouURSDz3v2MKBvPc5Gd8it/D1ufXv5O3Y
	w9xvWanPvH4pBuwnfYqBS7UysJbMHf0/Wrozg=
Received: by 10.115.32.18 with SMTP id k18mr14180339waj.98.1231206030102;
	Mon, 05 Jan 2009 17:40:30 -0800 (PST)
Received: by 10.115.74.12 with HTTP; Mon, 5 Jan 2009 17:40:29 -0800 (PST)
Message-ID: <3c3e3fca0901051740q6d930083sfdad766d26c1ee36@mail.gmail.com>
Date: Mon, 5 Jan 2009 20:40:29 -0500
From: "William Herrin" <bill@herrin.us>
To: "Yakov Rekhter" <yakov@juniper.net>
In-Reply-To: <200901051413.n05EDMM80111@magenta.juniper.net>
MIME-Version: 1.0
Content-Disposition: inline
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com>
	<3c3e3fca0901021219t2ab35dfsb2532e0c89be84af@mail.gmail.com>
	<E99E41EB33084B5B899C7EED9DE607E9@ad.redback.com>
	<3c3e3fca0901021334j22d17e54iec4bbf41b6c00480@mail.gmail.com>
	<BCFF32A1356842BF839C7DF7D059F15F@ad.redback.com>
	<3c3e3fca0901031320o1253fcd3s3b6597aef77fba33@mail.gmail.com>
	<A071B6FF07CD4B708EC6CA2B9938096D@ad.redback.com>
	<3c3e3fca0901031720w602d931ev42707b169f51fba9@mail.gmail.com>
	<49601D0B.6040803@firstpr.com.au>
	<200901051413.n05EDMM80111@magenta.juniper.net>
X-Google-Sender-Auth: e4db6889e1a6f5b7
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On Mon, Jan 5, 2009 at 9:13 AM, Yakov Rekhter <yakov@juniper.net> wrote:
> enhancing the
> architecture without taking into account the need to provide an
> adequate support for a (very) large number of mobile hosts would
> be rather myopic.

Ditto, assuming BGP's architecture is not collapsing.

Regards.
Bill Herrin



-- 
William D. Herrin ................ herrin@dirtside.com  bill@herrin.us
3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
Falls Church, VA 22042-3004
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan  5 18:11:09 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 628823A68DA;
	Mon,  5 Jan 2009 18:11:09 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 82DDA3A68DA
	for <rrg@core3.amsl.com>; Mon,  5 Jan 2009 18:11:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.341
X-Spam-Level: 
X-Spam-Status: No, score=0.341 tagged_above=-999 required=5 tests=[AWL=0.480, 
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 
	RDNS_NONE=0.1, SARE_SUB_6CONS_WORD=0.356]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id M6XsyZuqmaTA for <rrg@core3.amsl.com>;
	Mon,  5 Jan 2009 18:11:07 -0800 (PST)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65])
	by core3.amsl.com (Postfix) with ESMTP id ACEC33A6856
	for <rrg@irtf.org>; Mon,  5 Jan 2009 18:11:07 -0800 (PST)
Received: from huawei.com (szxga02-in [172.24.2.6])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0KD1008RJ21UGG@szxga02-in.huawei.com> for
	rrg@irtf.org; Tue, 06 Jan 2009 10:10:42 +0800 (CST)
Received: from x41208a ([10.111.12.103])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0KD1003X821QRW@szxga02-in.huawei.com> for
	rrg@irtf.org; Tue, 06 Jan 2009 10:10:41 +0800 (CST)
Date: Tue, 06 Jan 2009 10:10:38 +0800
From: Xu Xiaohu <xuxh@huawei.com>
In-reply-to: <59A87AAB-66C9-4284-84DA-13E07E6951C9@cisco.com>
To: 'Dino Farinacci' <dino@cisco.com>, 'David Conrad' <drc@virtualized.org>
Message-id: <000c01c96fa3$f7eaea90$670c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Mailer: Microsoft Office Outlook 11
Thread-index: AclvaOGoc+Avj1uRQme/d2DDiMNIVAANzGcg
Cc: 'RRG RG' <rrg@irtf.org>
Subject: Re: [rrg] Remote ACLs [Proposals which match
 rrg	architectures.htmlpls check the page]
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org


> > existing policy constraints for address allocation no 
> longer apply.   
> > The RIRs could continue to hand out 'routing slot conservation 
> > policy'-constrained LOCs since they have the technical
> 
> Let's not go this route. Let's have service providers 
> allocate RLOCs to sites. And just have RIRs allocate 
> EID-prefixes to sites. But RIRs would allocate PA RLOC 
> prefixes to service providers.
> 
> Make sense?

IMHO,  It doesn't matter whether RIRs or NANPA like national allocation
entities allocate EID resources, as long as the allocation is irrelevant to
the service providers, to which the site is connected.

> > expertise to know what this means.  They could also hand 
> out the EIDs, 
> > but since the policy regime for EID allocation is fundamentally 
> > different than LOCs, it might make sense for other bodies (e.g., 
> > national allocation entities like NANPA in the +1 telephone 
> region) to 
> > handle that task.
> 
> By allocating EID-prefixes based solely on address usage, you 
> only have a one-dimensional variable.
> 
> Let me be clear, I am not disagreeing with anything you are 
> saying, I'm just adding more to it. Hope you agree with my statements.
> 
> > Of course, if EIDs aren't handed out hierarchically, the existing  
> > ACL models that rely on locator semantics would obviously break.   
> > Some argue this wouldn't necessarily be a bad thing...
> 
> I think a non-starter. We shouldn't let this happen.

I agree with Dino's opinion. I believe that the flat ID is easy to use for
users but hard to manage for network operators. Freedom (e.g. information
privacy benefits from the flat ID)  sometimes conflicts with Administration,
we should consider some tradeoff between them.

Xiaohu


_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan  5 20:34:50 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AC1AD3A6823;
	Mon,  5 Jan 2009 20:34:50 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DCA163A6823
	for <rrg@core3.amsl.com>; Mon,  5 Jan 2009 20:34:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.243
X-Spam-Level: 
X-Spam-Status: No, score=-6.243 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	SARE_SUB_6CONS_WORD=0.356]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id RgtaTQx99dxA for <rrg@core3.amsl.com>;
	Mon,  5 Jan 2009 20:34:49 -0800 (PST)
Received: from virtualized.org (trantor.virtualized.org [204.152.189.190])
	by core3.amsl.com (Postfix) with ESMTP id 2B2373A6810
	for <rrg@irtf.org>; Mon,  5 Jan 2009 20:34:48 -0800 (PST)
Received: from [192.168.1.111] (pool-71-106-24-59.lsanca.dsl-w.verizon.net
	[71.106.24.59])
	by virtualized.org (Postfix) with ESMTP id 02209414B99;
	Mon,  5 Jan 2009 20:33:42 -0800 (PST)
Message-Id: <79D79FB9-AC0F-411A-95BB-4F8278022FEB@virtualized.org>
From: David Conrad <drc@virtualized.org>
To: Dino Farinacci <dino@cisco.com>
In-Reply-To: <59A87AAB-66C9-4284-84DA-13E07E6951C9@cisco.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Mon, 5 Jan 2009 20:33:41 -0800
References: <000c01c96ed2$73fa70b0$670c6f0a@china.huawei.com>
	<417CE10E-C5DE-4825-B250-42F6751112EC@cisco.com>
	<3B101E43-106C-4B31-A943-B5F7AD1EA995@virtualized.org>
	<DB736143-9A90-42C0-8518-CC6782FB071D@cisco.com>
	<A95DB8C8-1C1A-498A-AC16-6142E2FCB99C@virtualized.org>
	<59A87AAB-66C9-4284-84DA-13E07E6951C9@cisco.com>
X-Mailer: Apple Mail (2.930.3)
Cc: RRG RG <rrg@irtf.org>
Subject: Re: [rrg] Remote ACLs [Proposals which match
	rrg	architectures.htmlpls check the page]
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Dino,

On Jan 5, 2009, at 11:03 AM, Dino Farinacci wrote:
> By allocating EID-prefixes based solely on address usage, you only  
> have a one-dimensional variable.

So, you'd like to overload multiple semantics onto a single namespace  
again?  :-)

Regards,
-drc

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Tue Jan  6 09:47:04 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DE9973A6405;
	Tue,  6 Jan 2009 09:47:04 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 05A803A6405
	for <rrg@core3.amsl.com>; Tue,  6 Jan 2009 09:47:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.313
X-Spam-Level: 
X-Spam-Status: No, score=-6.313 tagged_above=-999 required=5
	tests=[AWL=-0.070, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	SARE_SUB_6CONS_WORD=0.356]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id slq4Yi+c0C7t for <rrg@core3.amsl.com>;
	Tue,  6 Jan 2009 09:47:03 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86])
	by core3.amsl.com (Postfix) with ESMTP id 4BF6C3A63D2
	for <rrg@irtf.org>; Tue,  6 Jan 2009 09:47:03 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.36,340,1228089600"; d="scan'208";a="27497158"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-4.cisco.com with ESMTP; 06 Jan 2009 17:46:27 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n06HkR27026718; 
	Tue, 6 Jan 2009 09:46:27 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id n06HkRuQ000868;
	Tue, 6 Jan 2009 17:46:27 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 6 Jan 2009 09:46:27 -0800
Received: from moveme.cisco.com ([10.21.150.142]) by
	xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 6 Jan 2009 09:46:27 -0800
Message-Id: <9FDAB770-93DD-4952-8248-98B98542FCC9@cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: David Conrad <drc@virtualized.org>
In-Reply-To: <79D79FB9-AC0F-411A-95BB-4F8278022FEB@virtualized.org>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Tue, 6 Jan 2009 09:46:27 -0800
References: <000c01c96ed2$73fa70b0$670c6f0a@china.huawei.com>
	<417CE10E-C5DE-4825-B250-42F6751112EC@cisco.com>
	<3B101E43-106C-4B31-A943-B5F7AD1EA995@virtualized.org>
	<DB736143-9A90-42C0-8518-CC6782FB071D@cisco.com>
	<A95DB8C8-1C1A-498A-AC16-6142E2FCB99C@virtualized.org>
	<59A87AAB-66C9-4284-84DA-13E07E6951C9@cisco.com>
	<79D79FB9-AC0F-411A-95BB-4F8278022FEB@virtualized.org>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 06 Jan 2009 17:46:27.0119 (UTC)
	FILETIME=[B30383F0:01C97026]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=380; t=1231263987; x=1232127987;
	c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dino@cisco.com;
	z=From:=20Dino=20Farinacci=20<dino@cisco.com>
	|Subject:=20Re=3A=20[rrg]=20Remote=20ACLs=20[Proposals=20wh
	ich=20match=20rrg=09architectures.htmlpls=20check=20the=20pa
	ge] |Sender:=20;
	bh=x8oIwePhTCGNpiz7/l+TY9B0ZA0DCCdhQ8RR7ZtFBFc=;
	b=SvoRt1YBMJI87b/jTIy0TzOrQ+zFkyrhUQkyPMheqAwB09i7BzMolQleIs
	COtdXxhUFKzZAwmJGFJBtEM6CQVAoAHihatHdbwSKNYXYe3C6rnMar1V2pAn
	O1mAMSChno;
Authentication-Results: sj-dkim-2; header.From=dino@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: RRG RG <rrg@irtf.org>
Subject: Re: [rrg] Remote ACLs [Proposals which match
	rrg	architectures.htmlpls check the page]
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

> Dino,
>
> On Jan 5, 2009, at 11:03 AM, Dino Farinacci wrote:
>> By allocating EID-prefixes based solely on address usage, you only  
>> have a one-dimensional variable.
>
> So, you'd like to overload multiple semantics onto a single  
> namespace again?  :-)

No, you have my polarity wrong. I'm saying single dimension is good.

Dino

>
>
> Regards,
> -drc
>

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Tue Jan  6 11:37:40 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 369A63A6900;
	Tue,  6 Jan 2009 11:37:40 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0A3E63A6900
	for <rrg@core3.amsl.com>; Tue,  6 Jan 2009 11:37:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.532
X-Spam-Level: 
X-Spam-Status: No, score=-2.532 tagged_above=-999 required=5 tests=[AWL=0.067, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 0g0hR4VUjcbY for <rrg@core3.amsl.com>;
	Tue,  6 Jan 2009 11:37:38 -0800 (PST)
Received: from QMTA01.westchester.pa.mail.comcast.net
	(qmta01.westchester.pa.mail.comcast.net [76.96.62.16])
	by core3.amsl.com (Postfix) with ESMTP id E65CC3A67A5
	for <rrg@irtf.org>; Tue,  6 Jan 2009 11:37:37 -0800 (PST)
Received: from OMTA05.westchester.pa.mail.comcast.net ([76.96.62.43])
	by QMTA01.westchester.pa.mail.comcast.net with comcast
	id 0Jka1b00w0vyq2s51KdDoP; Tue, 06 Jan 2009 19:37:13 +0000
Received: from TONYLTM9XP ([155.53.41.237])
	by OMTA05.westchester.pa.mail.comcast.net with comcast
	id 0KcW1b00j570qEr3RKcZhq; Tue, 06 Jan 2009 19:36:44 +0000
From: "Tony Li" <tony.li@tony.li>
To: "'Yakov Rekhter'" <yakov@juniper.net>
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com><87D9F0BA2807456A88B0427241A29F65@ad.redback.com><3c3e3fca0901021219t2ab35dfsb2532e0c89be84af@mail.gmail.com><E99E41EB33084B5B899C7EED9DE607E9@ad.redback.com><3c3e3fca0901021334j22d17e54iec4bbf41b6c00480@mail.gmail.com>
	<BCFF32A1356842BF839C7DF7D059F15F@ad.redback.com>
	<3525C9833C09ED418C6FD6CD9514668C0566045E@emailwf1.jnpr.net>
	<354C0AE786D1424C886C4A3570611291@ad.redback.com>
	<200901051509.n05F9nM02828@magenta.juniper.net>
Date: Tue, 6 Jan 2009 11:36:11 -0800
Message-ID: <DD2FDA0A88E84736AB1F3D25A3F61986@ad.redback.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <200901051509.n05F9nM02828@magenta.juniper.net>
Thread-Index: AclvSAbZ53vdKwI9SuauMo9F2yzUZQA7E9pw
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Cc: 'RRG' <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org


Hi Yakov,

 
| - The above assumes that DRAM will continue to be used to 
|implement control 
|   plane memory. As had been discussed before on this list, 
|DRAM is not the 
|   only option  - another alternative is RLDRAM. 


I think that Robin did an excellent job of expanding on the tradeoffs
involved in this, and I agree with his conclusion.

I'll also point out that that's at best a one time benefit and that the
subsequent speed increases would seem likely to parallel the DRAM speed
curve.  This is likely since RLDRAM is still using the same basic DRAM cell
technology and improving on the electrical interface.  Thus, RLDRAM would
give us a one-time bump up the speed curve, but it would do nothing to
change the shape or slope of the curve.

Again, the most important thing here is the slope (or more generally the
shape) of the curve.  As long as the slope of the prefix curve exceeds the
slope of the technology curve, you will eventually and necessarily run into
a problem.


| - Even if one assumes that the growth rate of prefixes exceeds the
|   rate of speed improvements in the underlying DRAM that is used to
|   implement control plane, and that, in turn, would result in cost
|   increases, let's not forget that deploying new routing architecture
|   may have its own cost, thus resulting in cost increases. Moreover,
|   these increases may be higher relative to what would result from
|   the growth rate of prefixes exceeding the rate of speed improvements
|   in the underlying DRAM.


True, but deploying a new architecture will have a one-time cost impact.
Paid for, over and done.  It will be spread out over each system that needs
to be upgraded, but it is a fixed and finite cost.  

Paying for a more expensive control plane is likely to be an ongoing, ever
increasing cost.


|   Would the industry be willing to buy into the *promise* of
|   "a paradise" in the *long* term at the price of fairly certain
|   cost increases in the *short/medium* term ? 
|
|   All of the above means that a "promise" of cost reduction in the
|   *long* term may not be sufficient - the new routing architecture
|   needs to deliver in the *short/medium* term sufficient *tangible*
|   benefits to justify its *short/medium* term cost.


One might look it at it instead as avoiding the guarantee of long term
higher costs.

In any case, there are numerous problems that we do feel we need to overcome
with the new architecture.  Whether the deployment costs are sufficiently
justified will in part depend on what we produce, and we will not know that
until we have consensus on a workable architecture.


| - One may argue that the real problem is not in the cost increases,
|   but in the way how these increases are absorbed by the system.
|   Namely, the real problem is that those who do not benefit
|   are still required to pay for covering the cost imposed by those
|   who do benefit. That applies both to the current system, as well 
|   as to any proposal for a new routing architecture.


Agreed.  The fundamental problem is that the architecture is a ready-made
tragedy of the commons.

Tony

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Tue Jan  6 12:11:32 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E04BB3A6817;
	Tue,  6 Jan 2009 12:11:32 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 01A633A6817
	for <rrg@core3.amsl.com>; Tue,  6 Jan 2009 12:11:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.752
X-Spam-Level: 
X-Spam-Status: No, score=-0.752 tagged_above=-999 required=5 tests=[AWL=0.450, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id qLcuzu2QDB7v for <rrg@core3.amsl.com>;
	Tue,  6 Jan 2009 12:11:31 -0800 (PST)
Received: from imo-m21.mx.aol.com (imo-m21.mx.aol.com [64.12.137.2])
	by core3.amsl.com (Postfix) with ESMTP id EE9543A67A5
	for <rrg@irtf.org>; Tue,  6 Jan 2009 12:11:30 -0800 (PST)
Received: from HeinerHummel@aol.com
	by imo-m21.mx.aol.com  (mail_out_v39.1.) id i.d04.4a61f639 (48552);
	Tue, 6 Jan 2009 15:11:08 -0500 (EST)
From: HeinerHummel@aol.com
Message-ID: <d04.4a61f639.36951505@aol.com>
Date: Tue, 6 Jan 2009 15:11:49 EST
To: tony.li@tony.li, yakov@juniper.net
MIME-Version: 1.0
X-Mailer: 9.0 SE for Windows sub 5021
Cc: rrg@irtf.org
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0129849081=="
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org


--===============0129849081==
Content-Type: multipart/alternative; boundary="-----------------------------1231272709"


-------------------------------1231272709
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

=20
In einer eMail vom 06.01.2009 20:37:35 Westeurop=E4ische Normalzeit schreibt=
 =20
tony.li@tony.li:

True,  but deploying a new architecture will have a one-time cost impact.
Paid  for, over and done.  It will be spread out over each system that  need=
s
to be upgraded, but it is a fixed and finite cost.  =20

Paying for a more expensive control plane is likely to be an ongoing,  ever
increasing cost.


|   Would the industry be  willing to buy into the *promise* of
|   "a paradise" in the  *long* term at the price of fairly certain
|   cost increases in  the *short/medium* term ?=20
|
|   All of the above means that a  "promise" of cost reduction in the
|   *long* term may not be  sufficient - the new routing architecture
|   needs to deliver in  the *short/medium* term sufficient *tangible*
|   benefits to  justify its *short/medium* term cost.


One might look it at it  instead as avoiding the guarantee of long term
higher costs.

In any  case, there are numerous problems that we do feel we need to overcom=
e
with  the new architecture.  Whether the deployment costs are  sufficiently
justified will in part depend on what we produce, and we will  not know that
until we have consensus on a workable  architecture.


| - One may argue that the real problem is not in the  cost increases,
|   but in the way how these increases are  absorbed by the system.
|   Namely, the real problem is that  those who do not benefit
|   are still required to pay for  covering the cost imposed by those
|   who do benefit. That  applies both to the current system, as well=20
|   as to any  proposal for a new routing architecture.





Changing the topology agnostic BGP to a well-reduced topology aware BGP, =20
where there is no update churn anymore, where a router  may have to deal  wi=
th a=20
small number of nodes and strict/loose links only, where the next hop is =20
determined by either one or three lookups so that it doesn't need caching =20
capability either,=20
        =20
                          will reduce the monetary costs immensely.
=20
Yakov also mentioned the huge number of mobile IP users to be expected  in=20
the future.=20
Wrt to mobility it would be crazy to continue with LISP 's LOC  -routing, i.=
e=20
to NOT switch over to location routing. We may aso be  going to see=20
applications where users are only mobile, i.e. have no home place  at any ti=
me.
=20
Heiner

-------------------------------1231272709
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3DISO-8859-1">
<META content=3D"MSHTML 6.00.6000.16788" name=3DGENERATOR></HEAD>
<BODY id=3Drole_body style=3D"FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY:=20=
Arial"=20
bottomMargin=3D7 leftMargin=3D7 topMargin=3D7 rightMargin=3D7><FONT id=3Drol=
e_document=20
face=3DArial color=3D#000000 size=3D2>
<DIV>
<DIV>In einer eMail vom 06.01.2009 20:37:35 Westeurop=E4ische Normalzeit sch=
reibt=20
tony.li@tony.li:</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid"><=
FONT=20
  style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000 size=
=3D2>True,=20
  but deploying a new architecture will have a one-time cost impact.<BR>Paid=
=20
  for, over and done.&nbsp; It will be spread out over each system that=20
  needs<BR>to be upgraded, but it is a fixed and finite cost.&nbsp;=20
  <BR><BR>Paying for a more expensive control plane is likely to be an ongoi=
ng,=20
  ever<BR>increasing cost.<BR><BR><BR>|&nbsp;&nbsp; Would the industry be=20
  willing to buy into the *promise* of<BR>|&nbsp;&nbsp; "a paradise" in the=20
  *long* term at the price of fairly certain<BR>|&nbsp;&nbsp; cost increases=
 in=20
  the *short/medium* term ? <BR>|<BR>|&nbsp;&nbsp; All of the above means th=
at a=20
  "promise" of cost reduction in the<BR>|&nbsp;&nbsp; *long* term may not be=
=20
  sufficient - the new routing architecture<BR>|&nbsp;&nbsp; needs to delive=
r in=20
  the *short/medium* term sufficient *tangible*<BR>|&nbsp;&nbsp; benefits to=
=20
  justify its *short/medium* term cost.<BR><BR><BR>One might look it at it=20
  instead as avoiding the guarantee of long term<BR>higher costs.<BR><BR>In=20=
any=20
  case, there are numerous problems that we do feel we need to overcome<BR>w=
ith=20
  the new architecture.&nbsp; Whether the deployment costs are=20
  sufficiently<BR>justified will in part depend on what we produce, and we w=
ill=20
  not know that<BR>until we have consensus on a workable=20
  architecture.<BR><BR><BR>| - One may argue that the real problem is not in=
 the=20
  cost increases,<BR>|&nbsp;&nbsp; but in the way how these increases are=20
  absorbed by the system.<BR>|&nbsp;&nbsp; Namely, the real problem is that=20
  those who do not benefit<BR>|&nbsp;&nbsp; are still required to pay for=20
  covering the cost imposed by those<BR>|&nbsp;&nbsp; who do benefit. That=20
  applies both to the current system, as well <BR>|&nbsp;&nbsp; as to any=20
  proposal for a new routing architecture.<BR><BR></FONT></BLOCKQUOTE></DIV>
<DIV></DIV>
<DIV>&nbsp;</DIV>
<DIV>Changing the topology agnostic BGP to a well-reduced topology aware BGP=
,=20
where there is no update churn anymore, where a router &nbsp;may have to dea=
l=20
with a small number of nodes and strict/loose links only, where the next hop=
 is=20
determined by either one or three lookups so that it doesn't need caching=20
capability either,&nbsp;</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&nbsp; will reduce the monetary costs immensely.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Yakov also mentioned&nbsp;the huge number of mobile IP users to be expe=
cted=20
in the future. </DIV>
<DIV>Wrt to mobility&nbsp;it would be crazy to continue with LISP 's LOC=20
-routing, i.e&nbsp;to NOT&nbsp;switch over to location routing. We may aso b=
e=20
going to see applications where users are only mobile, i.e. have no home pla=
ce=20
at any time.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Heiner</DIV></FONT></BODY></HTML>

-------------------------------1231272709--

--===============0129849081==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg

--===============0129849081==--


From rrg-bounces@irtf.org  Tue Jan  6 13:03:49 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5C50F3A6A62;
	Tue,  6 Jan 2009 13:03:49 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 22A0C3A6AFD
	for <rrg@core3.amsl.com>; Tue,  6 Jan 2009 13:03:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.485
X-Spam-Level: 
X-Spam-Status: No, score=-2.485 tagged_above=-999 required=5 tests=[AWL=0.114, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id IzY+TawzlW9z for <rrg@core3.amsl.com>;
	Tue,  6 Jan 2009 13:03:47 -0800 (PST)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.225])
	by core3.amsl.com (Postfix) with ESMTP id BCE763A6AFC
	for <rrg@irtf.org>; Tue,  6 Jan 2009 13:03:46 -0800 (PST)
Received: by rv-out-0506.google.com with SMTP id f6so9990541rvb.7
	for <rrg@irtf.org>; Tue, 06 Jan 2009 13:03:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from
	:organization:user-agent:mime-version:to:cc:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=scnTbKgUGhRl084qB22WvDlB2Idgzxzi8w/ruLOQNeU=;
	b=aW+NkiQNjkSZh6I7Pdw7EXn1+qs4lferzkV2sZjO5JmbFi6hLpE2P3h07R9Pm50/TA
	9suYZZ4y4WMAzCo5uHCm/Loysy9KhI3DsFylOqI8yJu45ZZmKqEF3Ng/x1DuOldJ3kmp
	c9z+MtV8Hza/ZKb9mq/QSC/PB+/3vGIh6hSMY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	b=PuhmrPDudo1GsT9OSD8ToLiYnF4sy5z+UiMkBDXJdzU+hhxKjKFYgjggfEum3RwShK
	z7+7eJ4F7cieAbzDjbDOUMhxR3xqLwAwGyh1l3R5ckSruf1pnbpwhLj05NLfufRSdPY+
	l1OQLYd4H8IESo2GM/dOLGjnEyfHUWQb6P+o8=
Received: by 10.141.18.15 with SMTP id v15mr11101508rvi.197.1231275812500;
	Tue, 06 Jan 2009 13:03:32 -0800 (PST)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz
	[130.216.38.124])
	by mx.google.com with ESMTPS id g31sm60964953rvb.4.2009.01.06.13.03.31
	(version=SSLv3 cipher=RC4-MD5); Tue, 06 Jan 2009 13:03:32 -0800 (PST)
Message-ID: <4963C721.9080808@gmail.com>
Date: Wed, 07 Jan 2009 10:03:29 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: tony.li@tony.li
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com><87D9F0BA2807456A88B0427241A29F65@ad.redback.com><3c3e3fca0901021219t2ab35dfsb2532e0c89be84af@mail.gmail.com><E99E41EB33084B5B899C7EED9DE607E9@ad.redback.com><3c3e3fca0901021334j22d17e54iec4bbf41b6c00480@mail.gmail.com>	<BCFF32A1356842BF839C7DF7D059F15F@ad.redback.com>	<3525C9833C09ED418C6FD6CD9514668C0566045E@emailwf1.jnpr.net>	<354C0AE786D1424C886C4A3570611291@ad.redback.com>	<200901051509.n05F9nM02828@magenta.juniper.net>
	<DD2FDA0A88E84736AB1F3D25A3F61986@ad.redback.com>
In-Reply-To: <DD2FDA0A88E84736AB1F3D25A3F61986@ad.redback.com>
Cc: 'RRG' <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Tony,

On 2009-01-07 08:36, Tony Li wrote:
...
> 
> Again, the most important thing here is the slope (or more generally the
> shape) of the curve.  As long as the slope of the prefix curve exceeds the
> slope of the technology curve, you will eventually and necessarily run into
> a problem.

I know where to find data for the prefix curve, although it's very
nosiy data and there is no reliable model that allows us to fit the
curve and extrapolate. But where do I find useable data for the
technology curve? Marketing-style hockey sticks don't help.

    Brian
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Tue Jan  6 14:05:40 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F2A723A69D2;
	Tue,  6 Jan 2009 14:05:39 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1EE883A69D2
	for <rrg@core3.amsl.com>; Tue,  6 Jan 2009 14:05:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.559
X-Spam-Level: 
X-Spam-Status: No, score=-2.559 tagged_above=-999 required=5 tests=[AWL=0.040, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id X+FWpiA0lDMm for <rrg@core3.amsl.com>;
	Tue,  6 Jan 2009 14:05:37 -0800 (PST)
Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.30])
	by core3.amsl.com (Postfix) with ESMTP id 0F4543A69B1
	for <rrg@irtf.org>; Tue,  6 Jan 2009 14:05:36 -0800 (PST)
Received: by yx-out-2324.google.com with SMTP id 8so3322898yxg.37
	for <rrg@irtf.org>; Tue, 06 Jan 2009 14:05:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:sender
	:to:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references
	:x-google-sender-auth;
	bh=ic/Xfm316iKEc5AnrLhv7wEAtdap02Bac0FAk1ZLQCA=;
	b=b7LO7Rz/I/I14ord3DPsdLDyJ1HFniMgrZIAw2mW2nIjjjXBc2UklSww4XPY73ylqZ
	0TXHkeY5Vlap+auvngX4FJebwwDgrStgqcQo1njlGot0jgWtNHXypHsK0pwZMIu0IHAz
	ULJNYBt7nmgOJfusWdElYvLdYYaHGM4QcpcTg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references:x-google-sender-auth;
	b=VvRQ/As8sVFBk2mmiH++dHALm9SnLWSKiBg+h4MmD+yg1g/rMu8zR2X+NQp/X6fDNj
	aQTzm5Uk8DG8wVgvguUXAbjXxVXLuuk95AkmDjVZLXg36/igrwwLcX2M57TOm+U2beSV
	3cf5qGSfY+T+lRcSGzsNOysasvUoQfjFZa4D0=
Received: by 10.100.125.12 with SMTP id x12mr12050685anc.4.1231279523029;
	Tue, 06 Jan 2009 14:05:23 -0800 (PST)
Received: by 10.100.196.14 with HTTP; Tue, 6 Jan 2009 14:05:22 -0800 (PST)
Message-ID: <75cb24520901061405m50a63533p86d77284b149d4cf@mail.gmail.com>
Date: Tue, 6 Jan 2009 17:05:22 -0500
From: "Christopher Morrow" <morrowc.lists@gmail.com>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
In-Reply-To: <4963C721.9080808@gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com>
	<3c3e3fca0901021219t2ab35dfsb2532e0c89be84af@mail.gmail.com>
	<E99E41EB33084B5B899C7EED9DE607E9@ad.redback.com>
	<3c3e3fca0901021334j22d17e54iec4bbf41b6c00480@mail.gmail.com>
	<BCFF32A1356842BF839C7DF7D059F15F@ad.redback.com>
	<3525C9833C09ED418C6FD6CD9514668C0566045E@emailwf1.jnpr.net>
	<354C0AE786D1424C886C4A3570611291@ad.redback.com>
	<200901051509.n05F9nM02828@magenta.juniper.net>
	<DD2FDA0A88E84736AB1F3D25A3F61986@ad.redback.com>
	<4963C721.9080808@gmail.com>
X-Google-Sender-Auth: d92695fc034d1855
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On Tue, Jan 6, 2009 at 4:03 PM, Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:
> Tony,
>
> On 2009-01-07 08:36, Tony Li wrote:
> ...
>>
>> Again, the most important thing here is the slope (or more generally the
>> shape) of the curve.  As long as the slope of the prefix curve exceeds the
>> slope of the technology curve, you will eventually and necessarily run into
>> a problem.
>
> I know where to find data for the prefix curve, although it's very
> nosiy data and there is no reliable model that allows us to fit the

and as always remember that internal routing table growth happens
outside of globally visible changes, and often (ATT's CBB as an
example, sprint/nextel IMS deployments as another) is completely
internal... unfortunately they are also not as predictable. I would
guess that internal tables at most providers (based on the preso's
from AMS/RAWS) are 30-50% larger than the global table. Some providers
(ATT/Sprint) are looking at vastly larger internal tables.

-Chris

> curve and extrapolate. But where do I find useable data for the
> technology curve? Marketing-style hockey sticks don't help.
>
>    Brian
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> https://www.irtf.org/mailman/listinfo/rrg
>
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Tue Jan  6 15:24:34 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D351A3A6A37;
	Tue,  6 Jan 2009 15:24:34 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 162BF3A6A37
	for <rrg@core3.amsl.com>; Tue,  6 Jan 2009 15:24:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.533
X-Spam-Level: 
X-Spam-Status: No, score=-2.533 tagged_above=-999 required=5 tests=[AWL=0.066, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 5SvEowFmmgF7 for <rrg@core3.amsl.com>;
	Tue,  6 Jan 2009 15:24:33 -0800 (PST)
Received: from QMTA08.westchester.pa.mail.comcast.net
	(qmta08.westchester.pa.mail.comcast.net [76.96.62.80])
	by core3.amsl.com (Postfix) with ESMTP id 2C2E03A69DF
	for <rrg@irtf.org>; Tue,  6 Jan 2009 15:24:33 -0800 (PST)
Received: from OMTA14.westchester.pa.mail.comcast.net ([76.96.62.60])
	by QMTA08.westchester.pa.mail.comcast.net with comcast
	id 0P7b1b0091HzFnQ58PQKQp; Tue, 06 Jan 2009 23:24:19 +0000
Received: from TONYLTM9XP ([155.53.1.254])
	by OMTA14.westchester.pa.mail.comcast.net with comcast
	id 0PQ41b00V5Up7oj3aPQ7Kk; Tue, 06 Jan 2009 23:24:17 +0000
From: "Tony Li" <tony.li@tony.li>
To: "'Christopher Morrow'" <morrowc.lists@gmail.com>,
	"'Brian E Carpenter'" <brian.e.carpenter@gmail.com>
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com>
	<3c3e3fca0901021219t2ab35dfsb2532e0c89be84af@mail.gmail.com>
	<E99E41EB33084B5B899C7EED9DE607E9@ad.redback.com>
	<3c3e3fca0901021334j22d17e54iec4bbf41b6c00480@mail.gmail.com>
	<BCFF32A1356842BF839C7DF7D059F15F@ad.redback.com>
	<3525C9833C09ED418C6FD6CD9514668C0566045E@emailwf1.jnpr.net>
	<354C0AE786D1424C886C4A3570611291@ad.redback.com>
	<200901051509.n05F9nM02828@magenta.juniper.net>
	<DD2FDA0A88E84736AB1F3D25A3F61986@ad.redback.com>
	<4963C721.9080808@gmail.com>
	<75cb24520901061405m50a63533p86d77284b149d4cf@mail.gmail.com>
Date: Tue, 6 Jan 2009 15:23:50 -0800
Message-ID: <9FEF736036A74B148CC307D8FA35B720@ad.redback.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <75cb24520901061405m50a63533p86d77284b149d4cf@mail.gmail.com>
Thread-Index: AclwTw2edPKP1BOlSN6R/0SGAGX/ewABpwJQ
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Cc: 'RRG' <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

 
Hi Chris,

|and as always remember that internal routing table growth happens
|outside of globally visible changes, and often (ATT's CBB as an
|example, sprint/nextel IMS deployments as another) is completely
|internal... unfortunately they are also not as predictable. I would
|guess that internal tables at most providers (based on the preso's
|from AMS/RAWS) are 30-50% larger than the global table. Some providers
|(ATT/Sprint) are looking at vastly larger internal tables.


I know that the internal tables are always a pain, but since we have to deal
with the global issues, the internal, private growth (self-inflicted ;-) has
to necessarily be out of scope for RRG.

Tony

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Tue Jan  6 17:59:53 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 33AE93A6872;
	Tue,  6 Jan 2009 17:59:53 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7B8343A6872
	for <rrg@core3.amsl.com>; Tue,  6 Jan 2009 17:59:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id UKRU4MNYdNT7 for <rrg@core3.amsl.com>;
	Tue,  6 Jan 2009 17:59:51 -0800 (PST)
Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.250])
	by core3.amsl.com (Postfix) with ESMTP id 5971D3A6452
	for <rrg@irtf.org>; Tue,  6 Jan 2009 17:59:51 -0800 (PST)
Received: by an-out-0708.google.com with SMTP id c38so3367106ana.37
	for <rrg@irtf.org>; Tue, 06 Jan 2009 17:59:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:sender
	:to:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references
	:x-google-sender-auth;
	bh=sTJl/g4zvR6XI8GNUQbbXnT2Ce4qmXtBWZHGb5oORMA=;
	b=s4dIVf4M5y1uzkANiMa7XbW06f2898GXvSJSViq07EMQKg6w8FchIeR/CLTOu9XMak
	z0Ykz/0mJxePJ5d9Tic5g8lQHaO3BBfUJ39A6IVeq4ZBHipsODogXFrtvF4fAk1gXn9o
	g7dcfE3TEDWy6YyOmAnOYrSplK5hqzJDwqGx4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references:x-google-sender-auth;
	b=NgY2OM07lk5/wgQb/X89mh0Gu1jtEiGPBksF+geZGTlkKBfLpESHcQ3Afoy/XXzed7
	oBeX86w+x1/dUXfHcm6IcxFURg+ag0di3MQYDit4d77QXsOAON7AqGOo0hk6Q1XWF869
	BQi3nlm+7KHPAOeKL22+2kh80S/L74fgluB00=
Received: by 10.100.128.20 with SMTP id a20mr12118965and.148.1231293576855;
	Tue, 06 Jan 2009 17:59:36 -0800 (PST)
Received: by 10.100.196.14 with HTTP; Tue, 6 Jan 2009 17:59:36 -0800 (PST)
Message-ID: <75cb24520901061759g5f983ac1obcdb098c8067c96b@mail.gmail.com>
Date: Tue, 6 Jan 2009 20:59:36 -0500
From: "Christopher Morrow" <morrowc.lists@gmail.com>
To: tony.li@tony.li
In-Reply-To: <9FEF736036A74B148CC307D8FA35B720@ad.redback.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com>
	<3c3e3fca0901021334j22d17e54iec4bbf41b6c00480@mail.gmail.com>
	<BCFF32A1356842BF839C7DF7D059F15F@ad.redback.com>
	<3525C9833C09ED418C6FD6CD9514668C0566045E@emailwf1.jnpr.net>
	<354C0AE786D1424C886C4A3570611291@ad.redback.com>
	<200901051509.n05F9nM02828@magenta.juniper.net>
	<DD2FDA0A88E84736AB1F3D25A3F61986@ad.redback.com>
	<4963C721.9080808@gmail.com>
	<75cb24520901061405m50a63533p86d77284b149d4cf@mail.gmail.com>
	<9FEF736036A74B148CC307D8FA35B720@ad.redback.com>
X-Google-Sender-Auth: 4de7fdc329d690b1
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On Tue, Jan 6, 2009 at 6:23 PM, Tony Li <tony.li@tony.li> wrote:
>
> Hi Chris,
>
> |and as always remember that internal routing table growth happens
> |outside of globally visible changes, and often (ATT's CBB as an
> |example, sprint/nextel IMS deployments as another) is completely
> |internal... unfortunately they are also not as predictable. I would
> |guess that internal tables at most providers (based on the preso's
> |from AMS/RAWS) are 30-50% larger than the global table. Some providers
> |(ATT/Sprint) are looking at vastly larger internal tables.
>
>
> I know that the internal tables are always a pain, but since we have to deal
> with the global issues, the internal, private growth (self-inflicted ;-) has
> to necessarily be out of scope for RRG.

Sure, my point was that we should keep in mind that the 280k we see
externally today is a shadow of the internal situation, and if the
'new architecture' can address both internal and external, or make the
external much less painful then lots of things get easier. (could get
easier)

-Chris
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Wed Jan  7 03:30:08 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2675F3A6899;
	Wed,  7 Jan 2009 03:30:08 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0BE8228C119
	for <rrg@core3.amsl.com>; Wed,  7 Jan 2009 03:30:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id t++vNKKCe2Oz for <rrg@core3.amsl.com>;
	Wed,  7 Jan 2009 03:30:04 -0800 (PST)
Received: from n2.nomadiclab.com (n2.nomadiclab.com
	[IPv6:2001:14b8:400:101::2])
	by core3.amsl.com (Postfix) with ESMTP id 19BE63A6899
	for <rrg@irtf.org>; Wed,  7 Jan 2009 03:30:04 -0800 (PST)
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 5912E1EF126;
	Wed,  7 Jan 2009 13:29:49 +0200 (EET)
Received: from [127.0.0.1] (localhost [IPv6:::1])
	by n2.nomadiclab.com (Postfix) with ESMTP id E24181EF125;
	Wed,  7 Jan 2009 13:29:48 +0200 (EET)
Message-Id: <96CDEE57-28F3-416C-8AAD-D3F7330B3C5A@nomadiclab.com>
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A105623AC3@XCH-NW-7V2.nw.nos.boeing.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Wed, 7 Jan 2009 13:29:48 +0200
References: <495F0BAA.2040303@firstpr.com.au><49611E83.8050301@gmail.com><4961CFD3.2050304@firstpr.com.au><D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com><20EEF623-B503-4994-B099-64715E567B2D@cisco.com>
	<474EEBD229DF754FB83D256004D021080AD5E539@XCH-NW-6V1.nw.nos.boeing.com>
	<39C363776A4E8C4A94691D2BD9D1C9A105623AC3@XCH-NW-7V2.nw.nos.boeing.com>
X-Mailer: Apple Mail (2.930.3)
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: RRG <rrg@irtf.org>, Robin Whittle <rw@firstpr.com.au>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

I (Pekka) wrote:
>>>> I don't know the details of LISP, but the recent discussion  
>>>> between Dino and me seem to indicate that HIP proxy and LISP xTRs  
>>>> are functionally close enough so that a HIP proxy could be  
>>>> "plugged in" to the LISP architecture...

Dino replied:
>>> And since I don't know the details of HIP-proxy, saying LISP and  
>>> HIP-proxy are functionally equivalent only occurs at a  
>>> conversational level.  The devil is in the details of course.

Eric noted:
>> I strongly resonate with Pekka's posting.

Which make Fred to ask:
> Pekka, is "HIP-proxy" and "HIP mobile router" one and the same thing?

Briefly, a "HIP-proxy" (as I understand the term) could be implemented  
as a version of the "HIP mobile router" (draft-melen-hip-mr-01.txt)  
that has the additional feature of being able to support unmodified  
legacy IPv4 and IPv6 nodes in the mobile network.  For such legacy  
nodes, the MR node would create ephemeral HIP identities and assign an  
IP address in the moving network side for each identity.  Hence,  
typically, the legacy host would get a single stable the IP address  
through DHCP or ND, in which case the MR would act as the DHCP or ND  
server.  OTOH, there is no need for the MR to actually be mobile --  
the mobility aspect could simply refer to its ability to use  
interchangeably multiple PI addresses.

So, I guess my answer is a qualified "no".  They are not the same  
thing, though they could be close.

One old, outdated description of the HIP proxy functionality is  
available as Patrik's MSc thesis at http://www2.cs.hut.fi/~pmrg/index.cgi?id=148 
    But that is basically 4 years old and concerns only the case where  
there is a 3G legacy network, not generic legacy networks at both  
sides.  Quite obviously, the thinking has evolved quite a lot since  
then.

> If so, IMHO it is absolutely realistic that the HIP-proxy and xTR  
> could occur on exactly the same platform.  Note that they are  
> complementary functions, however; not competing ones. I think this  
> also goes with what Eric was saying below?

I don't see any problem at all in installing a HIP proxy and xTR at  
the same box -- they could even use the same mapping infrastructure to  
find out the RLOC of the peer HIP proxy/xTR, and then in parallel send  
an opportunistic HIP I1 and whatever LISP sends when an xTR contacts  
another xTR that it has no prior association with.  But that would be  
a (minor) waste of resources as two packets would be sent in parallel.

Initially, what I think would be interesting to understand is the  
possibility of two additional designs:

1. One where the LISP xTR-xTR protocol is replaced with the HIP  
protocol (providing the additional mobility and security features HIP  
provides).

2. One where the initial xTR->xTR opening message is a hybrid that  
indicates that the sender understands both LISP and HIP, allowing the  
receiver to pick which one to use.

And then I could imagine a few designs beyond either...

--Pekka

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Wed Jan  7 03:47:22 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BE1F928C148;
	Wed,  7 Jan 2009 03:47:22 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6639C28C13F
	for <rrg@core3.amsl.com>; Wed,  7 Jan 2009 03:47:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id xHXshnlZz547 for <rrg@core3.amsl.com>;
	Wed,  7 Jan 2009 03:47:20 -0800 (PST)
Received: from n2.nomadiclab.com (n2.nomadiclab.com
	[IPv6:2001:14b8:400:101::2])
	by core3.amsl.com (Postfix) with ESMTP id 1CA943A67D7
	for <rrg@irtf.org>; Wed,  7 Jan 2009 03:47:20 -0800 (PST)
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 524561EF126;
	Wed,  7 Jan 2009 13:47:05 +0200 (EET)
Received: from [127.0.0.1] (localhost [IPv6:::1])
	by n2.nomadiclab.com (Postfix) with ESMTP id D6D0E1EF125;
	Wed,  7 Jan 2009 13:47:04 +0200 (EET)
Message-Id: <14F8EAC5-AB88-45A1-A58D-AF270F0C7A90@nomadiclab.com>
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
To: Dino Farinacci <dino@cisco.com>
In-Reply-To: <4FF36C8D-761D-4D45-BB99-A5E72B9E33C9@cisco.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Wed, 7 Jan 2009 13:47:04 +0200
References: <495F0BAA.2040303@firstpr.com.au><49611E83.8050301@gmail.com><4961CFD3.2050304@firstpr.com.au><D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com><20EEF623-B503-4994-B099-64715E567B2D@cisco.com>
	<474EEBD229DF754FB83D256004D021080AD5E539@XCH-NW-6V1.nw.nos.boeing.com>
	<39C363776A4E8C4A94691D2BD9D1C9A105623AC3@XCH-NW-7V2.nw.nos.boeing.com>
	<4FF36C8D-761D-4D45-BB99-A5E72B9E33C9@cisco.com>
X-Mailer: Apple Mail (2.930.3)
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: RRG <rrg@irtf.org>, Robin Whittle <rw@firstpr.com.au>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On 6 Jan 2009, at 00:01, Dino Farinacci wrote:
> Before we get carried away with what looks like a convergence of  
> "HIP-proxy and LISP", tell me what HIP offers to a LISP router that  
> the LISP architecture does not already provide?

I don't know what LISP already provides, so the following are mere  
guesses.

- Security?  Both opportunistic, no-infrastructure-requiring security  
for multi-homing/mobility, and baseline-level signalling security for  
integrating any security infrastructure you want (such as PKI, AAA, ...)

- Mobility?  As HIP proxy can be trivially integrated with the HIP  
mobile router (MR), the legacy networks can be mobile without any  
extra effort.  (Provided that the mapping infra has the required  
updating capability...)

- Ability to move more cleanly to a host-based solution, better  
serving mobile and multi-interface hosts.  This includes the ability  
to support upgraded hosts in the legacy networks.

Obviously, the next question is what the drawbacks would be.  Here is  
my initial list:

- Crypto.  Current HIP requires PK crypto (but no PKI!) and ESP.  LHIP  
(which uses only hash functions) is an option if people generally shun  
PK, and, as I already explained, ESP can be replaced with any  
tunnelling or flow-identifying protocol.

- Lack of operational experience.  AFAIK, only Boeing has operational  
experience on HIP.  I guess there is more operational experience  
available on LISP, even though I haven't seen any.

(I am sure there are others, but I cannot figure out any other  
drawbacks right now.)

> If is solely a add a pure definition to IDs and RLOCs, then I think  
> it's not worth the cost of deployment to do so.

Agreed.

Obviously, _for_me_ the main benefit would be the ability to cleanly  
move to a host-based solution, in such a way that the upgraded mobile  
hosts could work both stand-alone in the "new internet" (at the non- 
legacy side of xTRs) and in the legacy networks, without any extra  
overhead.  (That is, any upgraded hosts at the legacy networks would  
report their existence to the xTR, which would understand their  
presence, avoiding double encapsulation and signalling overhead).

--Pekka

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Wed Jan  7 03:55:19 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1F53C28C154;
	Wed,  7 Jan 2009 03:55:19 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 50D2828C154
	for <rrg@core3.amsl.com>; Wed,  7 Jan 2009 03:55:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id tAmtML15vi0M for <rrg@core3.amsl.com>;
	Wed,  7 Jan 2009 03:55:16 -0800 (PST)
Received: from n2.nomadiclab.com (n2.nomadiclab.com
	[IPv6:2001:14b8:400:101::2])
	by core3.amsl.com (Postfix) with ESMTP id 06CE928C13F
	for <rrg@irtf.org>; Wed,  7 Jan 2009 03:55:16 -0800 (PST)
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 3192C1EF126;
	Wed,  7 Jan 2009 13:55:02 +0200 (EET)
Received: from [127.0.0.1] (localhost [IPv6:::1])
	by n2.nomadiclab.com (Postfix) with ESMTP id B7C801EF125;
	Wed,  7 Jan 2009 13:55:01 +0200 (EET)
Message-Id: <1E8EC4E2-2365-4826-BC5C-1ADCB97C0E06@nomadiclab.com>
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
To: Dino Farinacci <dino@cisco.com>
In-Reply-To: <E294A8E4-57E3-48D3-BE17-B0EF2BD46DA4@cisco.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Wed, 7 Jan 2009 13:55:01 +0200
References: <495F0BAA.2040303@firstpr.com.au>
	<49611E83.8050301@gmail.com><4961CFD3.2050304@firstpr.com.au><D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com>
	<20EEF623-B503-4994-B099-64715E567B2D@cisco.com>
	<474EEBD229DF754FB83D256004D021080AD5E539@XCH-NW-6V1.nw.nos.boeing.com>
	<E294A8E4-57E3-48D3-BE17-B0EF2BD46DA4@cisco.com>
X-Mailer: Apple Mail (2.930.3)
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: RRG <rrg@irtf.org>, Robin Whittle <rw@firstpr.com.au>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Eric wrote:
>> By combining a true locator-identifier split (i.e., HIP) with a
>> map-and-encaps (e.g., LISP) one gets the combined benefits of both
>> approaches. Those benefits are

Dino replied:
>
> But you add another layer of addressing that is probably more than  
> the user wants. It could get this bad:
>
> HIT -> EID -> private-RLOC -> public-RLOC    when behind a NAT
>
> or
>
> HIT -> private-EID -> public-EID -> RLOC     when behind a NAT

I don't think those mappings are right.

If there is a NAT between the xTR/HIP-proxy and the "new" internet,  
the mapping would be:

EID -> (HIT) -> private-RLOC -> public-RLOC

where the HIT would be invisible everywhere but inside the HIP proxies  
and within the signalling protocol between the HIP proxies.

If there is a NAT between the legacy host and the xTR/HIP-proxy, the  
mapping would be:

private-EID -> public-EID -> (HIT) -> RLOC

where again the HIT would be invisible, as explained above.

> 2-levels of mapping is plenty, adding 2 more probably is a non- 
> starter. Remember folks, we have to incrementally deploy this with  
> minimal cost, see Yakov's post early today, he makes good points.

I don't see how replacing the xTR internal functionality with the HIP- 
proxy functionality would add much cost.  It would change the protocol  
between the xTRs, yes.  HIP as a protocol is probably more complex  
than the present xTR-xTR protocol, but it is well tested, been in  
operational use at Boeing for a few years, as has three open source  
implementations.

There is an extra mapping, i.e. replacing the EID->RLOC mapping with a  
EID->(HIT)->RLOC mapping.  But that mapping is internal to the proxies  
and the signalling protocol, and not visible outside.  In the simplest  
case the HITs would be ephemeral and opportunistic, requiring no  
configuration or storage anywhere.  (The benefit from them is in terms  
of security and mobility, especially in more complex scenarios than  
the simplest case.)

--Pekka

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Wed Jan  7 08:00:32 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 855E63A6A37;
	Wed,  7 Jan 2009 08:00:32 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2C0463A6A37
	for <rrg@core3.amsl.com>; Wed,  7 Jan 2009 08:00:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.522
X-Spam-Level: 
X-Spam-Status: No, score=-6.522 tagged_above=-999 required=5 tests=[AWL=0.077, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 3FR6+LmZcU9t for <rrg@core3.amsl.com>;
	Wed,  7 Jan 2009 08:00:30 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 311903A695A
	for <rrg@irtf.org>; Wed,  7 Jan 2009 08:00:30 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,226,1231113600"; d="scan'208";a="32980663"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 07 Jan 2009 16:00:01 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n07G01d2031991
	for <rrg@irtf.org>; Wed, 7 Jan 2009 11:00:01 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n07G01DW026617
	for <rrg@irtf.org>; Wed, 7 Jan 2009 16:00:01 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 7 Jan 2009 11:00:01 -0500
Received: from cisco.com ([10.82.235.158]) by xfe-rtp-201.amer.cisco.com with
	Microsoft SMTPSVC(6.0.3790.1830); Wed, 7 Jan 2009 11:00:00 -0500
Date: Wed, 7 Jan 2009 10:59:58 -0500
From: Scott Brim <swb@employees.org>
To: rrg@irtf.org
Message-ID: <20090107155958.GA35370@cisco.com>
Mail-Followup-To: Scott Brim <swb@employees.org>, rrg@irtf.org
References: <3c3e3fca0812231929s233ffdbavb24ae9cf7d6c091a@mail.gmail.com>
	<49592F54.60600@gmail.com>
	<3c3e3fca0812291235w4707f0c1k19e5f7af8b44be94@mail.gmail.com>
	<49593CB8.2080101@gmail.com> <49594378.9000104@joelhalpern.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <49594378.9000104@joelhalpern.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-OriginalArrivalTime: 07 Jan 2009 16:00:01.0078 (UTC)
	FILETIME=[FF0CBD60:01C970E0]
Authentication-Results: rtp-dkim-2; header.From=swb@employees.org; dkim=neutral
Subject: Re: [rrg] Consensus call: Reject proposed strategy F?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Excerpts from Joel M. Halpern on Mon, Dec 29, 2008 04:39:04PM -0500:
> G says "constrain what people are allowed to do, even if they are  
> prepared to pay.  Not going to happen.
> F says "we give up."  Well, we may.  But if we are trying to get to a  
> useful conclusion, that isn't it.

F says "solve the problems by means outside of routing and
addressing architecture".  This is a reasonable thing to do if we can.
The activity might mainly be focused outside of RRG, but RRG's job
would be to discover that activity and show how it either helps or
doesn't.  We do this already.

> E says that economic factors may help.  They may.  They won't change the  
> architecture.  They will not stave off the problems forever.  Given that  
> this is an economic / business issue, it is not something the IETF (or  
> IRTF) is in a good position to influence.  We tried in the past.
> D says that we can be more clever.  And we can.  It will buy us some  
> runway.  Being more clever is engineering.  it takes good engineering,  
> but it is engineering.  Folks are looking at it.  We sure should not say  
> anything that tells them not to work on doing a better job for now. (The 
> more runway they can give us, the better chance we have of getting to a 
> good answer.)
>
> C is geographic aggregation, if I read your document right.  The  
> solutions I have seen to that tend to fall into three very different  
> camps, with very different problems.  While I personally find all three  
> kinds undesirable, we should be careful about how we comment on their  
> workability.  (Note, one of the strategies I have seen does line up with  
> the description in the web page.  One of the alternatives may or may not  
> line up, as I have not been able to read an understandble description of  
> how it would work.  And the third one is opportunistic.  The issue with  
> an opportunistic approach is that it is hard to evaluate how much good  
> we would get out of it.  But that is very different from undeployablity  
> or incomprehensibility as a concern.)

C isn't necessarily just 'geographic' aggregation.  It can include
creation of "superprefix" aggregates which are advertised in place of
longer prefixes but not tied to geography.  (Business-wise that
doesn't work either.)

> B (host based) and A (border-box based tunnels) are the primary
> areas we  tend to focus on.  While network-centric solutions using
> selective  placement looks more tractable to deploy, there are
> difficulties and  benefits for any of these strategies.  There are
> also hybrids which may  allow evolution driven by functionality
> increases.  It would seem quite  extreme to declare one side of this
> to be worth exploring, and the other  side to be a bad idea.  So I
> would hate to see either A or B declared  out of bounds for this
> community.

Agree.  
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Wed Jan  7 12:52:27 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7714F3A689C;
	Wed,  7 Jan 2009 12:52:27 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 77CFB3A689C
	for <rrg@core3.amsl.com>; Wed,  7 Jan 2009 12:52:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.234
X-Spam-Level: 
X-Spam-Status: No, score=-5.234 tagged_above=-999 required=5 tests=[AWL=1.365, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ONRc48ROXauT for <rrg@core3.amsl.com>;
	Wed,  7 Jan 2009 12:52:25 -0800 (PST)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com
	[130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id 0887C3A677D
	for <rrg@irtf.org>; Wed,  7 Jan 2009 12:52:25 -0800 (PST)
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4])
	by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id n07Kq09Z021508
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 7 Jan 2009 12:52:00 -0800 (PST)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1])
	by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	n07Kq041013649; Wed, 7 Jan 2009 12:52:00 -0800 (PST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	n07Kppdt013138; Wed, 7 Jan 2009 12:52:00 -0800 (PST)
Received: from XCH-NW-5V1.nw.nos.boeing.com ([130.247.55.44]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 7 Jan 2009 12:51:59 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 7 Jan 2009 12:51:58 -0800
Message-ID: <77F357662F8BFA4CA7074B0410171B6D07B0BC42@XCH-NW-5V1.nw.nos.boeing.com>
In-Reply-To: <96CDEE57-28F3-416C-8AAD-D3F7330B3C5A@nomadiclab.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] Rejecting all but Strategy A
Thread-Index: Aclwu0THNvEQo4tdREuwq6kI9DQf4AAQ3J4g
References: <495F0BAA.2040303@firstpr.com.au><49611E83.8050301@gmail.com><4961CFD3.2050304@firstpr.com.au><D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com><20EEF623-B503-4994-B099-64715E567B2D@cisco.com><474EEBD229DF754FB83D256004D021080AD5E539@XCH-NW-6V1.nw.nos.boeing.com><39C363776A4E8C4A94691D2BD9D1C9A105623AC3@XCH-NW-7V2.nw.nos.boeing.com>
	<96CDEE57-28F3-416C-8AAD-D3F7330B3C5A@nomadiclab.com>
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: "Pekka Nikander" <pekka.nikander@nomadiclab.com>,
	"Templin, Fred L" <Fred.L.Templin@boeing.com>
X-OriginalArrivalTime: 07 Jan 2009 20:51:59.0572 (UTC)
	FILETIME=[C8E2C940:01C97109]
Cc: RRG <rrg@irtf.org>, Robin Whittle <rw@firstpr.com.au>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

 

> -----Original Message-----
> From: Pekka Nikander [mailto:pekka.nikander@nomadiclab.com] 
> Sent: Wednesday, January 07, 2009 3:30 AM
> To: Templin, Fred L
> Cc: RRG; Robin Whittle
> Subject: Re: [rrg] Rejecting all but Strategy A
> 
> I (Pekka) wrote:
> >>>> I don't know the details of LISP, but the recent discussion  
> >>>> between Dino and me seem to indicate that HIP proxy and 
> LISP xTRs  
> >>>> are functionally close enough so that a HIP proxy could be  
> >>>> "plugged in" to the LISP architecture...
> 
> Dino replied:
> >>> And since I don't know the details of HIP-proxy, saying LISP and  
> >>> HIP-proxy are functionally equivalent only occurs at a  
> >>> conversational level.  The devil is in the details of course.
> 
> Eric noted:
> >> I strongly resonate with Pekka's posting.
> 
> Which make Fred to ask:
> > Pekka, is "HIP-proxy" and "HIP mobile router" one and the 
> same thing?
> 
> Briefly, a "HIP-proxy" (as I understand the term) could be 
> implemented  
> as a version of the "HIP mobile router" (draft-melen-hip-mr-01.txt)  
> that has the additional feature of being able to support unmodified  
> legacy IPv4 and IPv6 nodes in the mobile network.  For such legacy  
> nodes, the MR node would create ephemeral HIP identities and 
> assign an  
> IP address in the moving network side for each identity.  Hence,  
> typically, the legacy host would get a single stable the IP address  
> through DHCP or ND, in which case the MR would act as the DHCP or ND  
> server.  OTOH, there is no need for the MR to actually be mobile --  
> the mobility aspect could simply refer to its ability to use  
> interchangeably multiple PI addresses.
> 
> So, I guess my answer is a qualified "no".  They are not the same  
> thing, though they could be close.

I agree that HIP-proxy and xTR are not the same thing.  xTR tunnels,
mapping entries, cache entries can cover aggregates of hosts, while
HIP-proxy has per-host granularity.  xTR doesn't claim to represent any
host from a security point of view, while HIP-proxy seems to.

> 
> One old, outdated description of the HIP proxy functionality is  
> available as Patrik's MSc thesis at 
> http://www2.cs.hut.fi/~pmrg/index.cgi?id=148 
>     But that is basically 4 years old and concerns only the 
> case where  
> there is a 3G legacy network, not generic legacy networks at both  
> sides.  Quite obviously, the thinking has evolved quite a lot since  
> then.
> 
> > If so, IMHO it is absolutely realistic that the HIP-proxy and xTR  
> > could occur on exactly the same platform.  Note that they are  
> > complementary functions, however; not competing ones. I think this  
> > also goes with what Eric was saying below?
> 
> I don't see any problem at all in installing a HIP proxy and xTR at  
> the same box -- they could even use the same mapping 
> infrastructure to  
> find out the RLOC of the peer HIP proxy/xTR, and then in 
> parallel send  
> an opportunistic HIP I1 and whatever LISP sends when an xTR contacts  
> another xTR that it has no prior association with.  But that 
> would be  
> a (minor) waste of resources as two packets would be sent in parallel.

This would probably increase the load on the mapping system and xTRs
considerably, because of the per-host granularity.

I'm not sure how it would work for multiple ITRs and ETRs, are there
multiple proxy host identities, one for each xTR?  How is that handled
with mobility or path unavailability events?

It changes the security model for HIP-- when I move behind some ITR, am
I going to want my packets to flow unprotected between my host interface
and the ITR? Am I going to trust arbitrary ITRs to proxy for my host?
Also, are ITRs going to have any incentives to give me good (or any) HIP
service?

> 
> Initially, what I think would be interesting to understand is the  
> possibility of two additional designs:
> 
> 1. One where the LISP xTR-xTR protocol is replaced with the HIP  
> protocol (providing the additional mobility and security 
> features HIP  
> provides).
> 
> 2. One where the initial xTR->xTR opening message is a hybrid that  
> indicates that the sender understands both LISP and HIP, 
> allowing the  
> receiver to pick which one to use.
> 
> And then I could imagine a few designs beyond either...

Are you instead suggesting above to look at combining HIP with LISP, or
HIP-proxy with LISP?

I see the distinction being that HIP with LISP means that HIP keys are
used to name xTRs and to secure the xTR to xTR communications (and
possibly communications with the mapping system), but otherwise LISP
works as described.  Proxy-HIP keys would name individual hosts and
would play more of a role as an EID in the system.

- Tom
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Wed Jan  7 13:09:31 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 183123A69EF;
	Wed,  7 Jan 2009 13:09:31 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3BF2A3A69EF
	for <rrg@core3.amsl.com>; Wed,  7 Jan 2009 13:09:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.507
X-Spam-Level: 
X-Spam-Status: No, score=-5.507 tagged_above=-999 required=5 tests=[AWL=1.092, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 5ZyISTcdUImh for <rrg@core3.amsl.com>;
	Wed,  7 Jan 2009 13:09:29 -0800 (PST)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com
	[130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id 76B523A677D
	for <rrg@irtf.org>; Wed,  7 Jan 2009 13:09:29 -0800 (PST)
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4])
	by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id n07L95rg010483
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 7 Jan 2009 13:09:05 -0800 (PST)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1])
	by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	n07L95ca021482; Wed, 7 Jan 2009 13:09:05 -0800 (PST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	n07L91uE021302; Wed, 7 Jan 2009 13:09:05 -0800 (PST)
Received: from XCH-NW-5V1.nw.nos.boeing.com ([130.247.55.44]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 7 Jan 2009 13:09:04 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 7 Jan 2009 13:09:03 -0800
Message-ID: <77F357662F8BFA4CA7074B0410171B6D07B0BC43@XCH-NW-5V1.nw.nos.boeing.com>
In-Reply-To: <474EEBD229DF754FB83D256004D021080AD5E7F7@XCH-NW-6V1.nw.nos.boeing.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] Rejecting all but Strategy A
Thread-Index: AclvgrJG3UWoq6fcSWyv5YM3xOFIAgAAEcDwAGIQ2iA=
References: <495F0BAA.2040303@firstpr.com.au><49611E83.8050301@gmail.com><4961CFD3.2050304@firstpr.com.au><D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com><20EEF623-B503-4994-B099-64715E567B2D@cisco.com><474EEBD229DF754FB83D256004D021080AD5E539@XCH-NW-6V1.nw.nos.boeing.com><E294A8E4-57E3-48D3-BE17-B0EF2BD46DA4@cisco.com>
	<474EEBD229DF754FB83D256004D021080AD5E7F7@XCH-NW-6V1.nw.nos.boeing.com>
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: "Fleischman, Eric" <eric.fleischman@boeing.com>,
	"Dino Farinacci" <dino@cisco.com>
X-OriginalArrivalTime: 07 Jan 2009 21:09:04.0766 (UTC)
	FILETIME=[2BF2F9E0:01C9710C]
Cc: RRG <rrg@irtf.org>, Robin Whittle <rw@firstpr.com.au>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

 

> 
> We have operationally deployed HIP as a basis for securing our
> IP-connected SCADA machine controllers in our factories. This is the
> most viable way to secure IP networked-attached SCADA devices that we
> know about. Again, the operational costs of doing this are trivial
> compared with the risks with leaving these machines inadequately
> secured. 
> 

If people are interested in the deployment that Eric cited above, we
made a presentation at the last HIP RG meeting in Minneapolis:
http://www.ietf.org/proceedings/08nov/slides/HIPRG-0.pdf

To briefly summarize it technically, it is an adaptation of HIP to
provide a layer-2 VPN for unmodified hosts. 

We have also separately experimented with a HIP proxy, but only a single
middlebox, on-link with the unmodified legacy host; not an off-link
proxy serving many hosts.

Tom
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Wed Jan  7 13:21:08 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EB0C33A68B4;
	Wed,  7 Jan 2009 13:21:07 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7EE8A3A684C
	for <rrg@core3.amsl.com>; Wed,  7 Jan 2009 13:21:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.524
X-Spam-Level: 
X-Spam-Status: No, score=-6.524 tagged_above=-999 required=5 tests=[AWL=0.075, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id bQL40+-+Wn1r for <rrg@core3.amsl.com>;
	Wed,  7 Jan 2009 13:21:05 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 60F783A67EE
	for <rrg@irtf.org>; Wed,  7 Jan 2009 13:21:05 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,227,1231113600"; d="scan'208";a="33112946"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 07 Jan 2009 21:20:51 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n07LKpvH031927
	for <rrg@irtf.org>; Wed, 7 Jan 2009 16:20:51 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n07LKpkl021780
	for <rrg@irtf.org>; Wed, 7 Jan 2009 21:20:51 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 7 Jan 2009 16:20:51 -0500
Received: from cisco.com ([10.82.235.158]) by xfe-rtp-202.amer.cisco.com with
	Microsoft SMTPSVC(6.0.3790.1830); Wed, 7 Jan 2009 16:20:51 -0500
Date: Wed, 7 Jan 2009 16:20:44 -0500
From: Scott Brim <swb@employees.org>
To: rrg@irtf.org
Message-ID: <20090107212044.GA43816@cisco.com>
Mail-Followup-To: Scott Brim <swb@employees.org>, rrg@irtf.org
References: <495F0BAA.2040303@firstpr.com.au> <49611E83.8050301@gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <49611E83.8050301@gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-OriginalArrivalTime: 07 Jan 2009 21:20:51.0236 (UTC)
	FILETIME=[D109BE40:01C9710D]
Authentication-Results: rtp-dkim-2; header.From=swb@employees.org; dkim=neutral
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Excerpts from Brian E Carpenter on Mon, Jan 05, 2009 09:39:31AM +1300:
> >    Strategy B:  There are no properly documented proposals.
> 
> > 
> >                 ILNP may be a Strategy B approach but it is not
> >                 properly documented as a scalable routing
> >                 solution.  There is no Summary and Analysis in the
> >                 RRG wiki.
> 
> It's unclear to me that ILNP belongs in B since it has
> characteristics of A as well. Whether it's jumped through the hoops
> of the wiki strikes me as uninteresting; it seems to be well
> documented.

ILNP has multiple modes of operation.  One shouldn't be cataloging
entire "packages" because many of them cross taxonomic lines.  If you
must talk in terms of packages, allow a package to be in more than one
category.

> >                 HIP has been mentioned, but no-one seems to be
> >                 proposing it as a scalable routing solution.
> 
> I think Pekka observed that this wasn't even a goal. 

It's not one of HIP's goals, but HIP can help create a routing
solution by making it possible for locators to be assigned
hierarchically.

> (My quick answer
> is that it only becomes a routing solution if it solves the same
> mapping problem that strategy A generates.)

I don't understand this.  Strategy A's "mapping problem" is to find a
mapping from a locally-routed locator to a (more) globally-routed one.

Perhaps what you're saying is that we need a mapping from HIP
identifier to locator?  If so, I don't believe that's true.  If I, a
session initiator, am starting from scratch, I could look up both your
location and your HI in parallel, or I could connect to you and
discover your HI during authentication, and so on.

> But I fully agree: strategy B == IPv6.

If identity is based in transport-layer-or-above, as in Trilogy
multipath, you can have a "B" that could work with IPv4 or v6 (even
both simultaneously).

> > Also, I argue that any approach which involves pushing
> > responsibilities and management traffic to all hosts (all
> > potential Strategy B approaches) is fundamentally flawed:
> > 
> >   http://www.irtf.org/pipermail/rrg/2008-November/000233.html
> 
> Highly distributed = scaleable. And in any cases, hosts have always
> been responsible for traffic management (that's called TCP) and
> approaches like SCTP and the proposed multipath TCP extend that.  So
> I don't think we should condemn this in the abstract.

One of the places we clearly get into trouble pushing responsibility
to endpoints is path selection (with or without failures).  First you
may get a lot more control traffic.  Second, endpoint activities can
be at odds with SP activities -- each optimizing for the same thing
differently.  See previous discussion.

> Exactly. Which is why my preference is to recommend development work
> on strategy A and continued R&D on strategy B; I'd be very concerned
> if we shrugged our shoulders and dropped it for 12 years.

+1 on that.

Scott
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Wed Jan  7 14:50:11 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 468943A6A0D;
	Wed,  7 Jan 2009 14:50:11 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7AE113A6A0D
	for <rrg@core3.amsl.com>; Wed,  7 Jan 2009 14:50:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.45
X-Spam-Level: 
X-Spam-Status: No, score=-6.45 tagged_above=-999 required=5 tests=[AWL=0.149, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id j+nypOp0+iCt for <rrg@core3.amsl.com>;
	Wed,  7 Jan 2009 14:50:09 -0800 (PST)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com
	[130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id B9E3B3A684C
	for <rrg@irtf.org>; Wed,  7 Jan 2009 14:50:09 -0800 (PST)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6])
	by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id n07Mnq5G029205
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);
	Wed, 7 Jan 2009 14:49:53 -0800 (PST)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	n07Mnqt4011923; Wed, 7 Jan 2009 16:49:52 -0600 (CST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	n07MnkgT011721; Wed, 7 Jan 2009 16:49:52 -0600 (CST)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 7 Jan 2009 14:49:50 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 7 Jan 2009 14:49:49 -0800
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A10566DB53@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <77F357662F8BFA4CA7074B0410171B6D07B0BC42@XCH-NW-5V1.nw.nos.boeing.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] Rejecting all but Strategy A
Thread-Index: Aclwu0THNvEQo4tdREuwq6kI9DQf4AAQ3J4gAAaAAbA=
References: <495F0BAA.2040303@firstpr.com.au><49611E83.8050301@gmail.com><4961CFD3.2050304@firstpr.com.au><D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com><20EEF623-B503-4994-B099-64715E567B2D@cisco.com><474EEBD229DF754FB83D256004D021080AD5E539@XCH-NW-6V1.nw.nos.boeing.com><39C363776A4E8C4A94691D2BD9D1C9A105623AC3@XCH-NW-7V2.nw.nos.boeing.com>
	<96CDEE57-28F3-416C-8AAD-D3F7330B3C5A@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D07B0BC42@XCH-NW-5V1.nw.nos.boeing.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>,
	"Pekka Nikander" <pekka.nikander@nomadiclab.com>
X-OriginalArrivalTime: 07 Jan 2009 22:49:50.0837 (UTC)
	FILETIME=[3FB03250:01C9711A]
Cc: RRG <rrg@irtf.org>, Robin Whittle <rw@firstpr.com.au>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Regarding HIP + map/encaps, maybe it is obvious to everyone
else already but I think what that gives you is an endpoint
identity (the HIT), an inner routing locator (iRLOC), and an
outer RLOC (oRLOC). Up to now, LISP (and perhaps others) have
been using the term "EID" to refer to what I mean by "iRLOC",
and the term "RLOC" to refer to what I mean by "oRLOC".

In this sense, "oRLOC" is routable within the scope of an
interdomain region, while "iRLOC" is routable only within and
end site (or edge network, or whatever you want to call it).
The HIP HIT is not routable within any scope so it is purely
an identifier and not a locator.

Is this news to anyone, or already so obvious that it doesn't
even bear mention? (Will check back later; I really need to
be off doing other things...)

Fred
fred.l.templin@boeing.com 
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Wed Jan  7 16:46:30 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C848D28C0F6;
	Wed,  7 Jan 2009 16:46:30 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9209C3A6A96
	for <rrg@core3.amsl.com>; Wed,  7 Jan 2009 16:46:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.562
X-Spam-Level: 
X-Spam-Status: No, score=-1.562 tagged_above=-999 required=5 tests=[AWL=0.333, 
	BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id XuBIZcGz6Yo7 for <rrg@core3.amsl.com>;
	Wed,  7 Jan 2009 16:46:27 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123])
	by core3.amsl.com (Postfix) with ESMTP id 1606828C115
	for <rrg@irtf.org>; Wed,  7 Jan 2009 16:46:12 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6])
	by gair.firstpr.com.au (Postfix) with ESMTP id 04A81175D15;
	Thu,  8 Jan 2009 11:45:56 +1100 (EST)
Message-ID: <49654CC6.80802@firstpr.com.au>
Date: Thu, 08 Jan 2009 11:45:58 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: RRG <rrg@irtf.org>
Subject: [rrg] HIP, Hip-Proxy etc. (Strategy B)
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

I am hoping to draw the HIP discussion from the "Rejecting all but
Strategy A" thread into this thread with an appropriate title.

No-one has proposed HIP or anything related to HIP as an actual
solution to the routing scaling problem.  However, I understand we
are discussing how HIP might be used for this purpose, in which case
I think it would match, perhaps not exactly, Bill's Strategy B:

  http://bill.herrin.us/network/rrgarchitectures.html

The HIP RFCs and an overview are:

  http://tools.ietf.org/html/rfc5201  Main
  http://tools.ietf.org/html/rfc5202  EPS
  http://tools.ietf.org/html/rfc5203  Registration extension
  http://tools.ietf.org/html/rfc5204  Rendezvous extension
  http://tools.ietf.org/html/rfc5205  DNS extension
  http://tools.ietf.org/html/rfc5206  End-Host Mobility & Multihoming
  http://tools.ietf.org/html/rfc5207  NAT and Firewall Traversal

  http://infrahip.hiit.fi/index.php?index=how

There were several HIP related messages on 5 January.  Here I list
the most recent ones, from Pekka Nikander, Thomas Henderson, Scott
Brim and Fred Templin:

http://www.irtf.org/pipermail/rrg/2009-January/000741.html  PN

  "HIP-Proxy" as as a version of "HIP mobile router":
  http://tools.ietf.org/html/draft-melen-hip-mr-01

  Two additional designs:

    1. LISP xTR-xTR protocol is replaced with the HIP protocol
       (providing the additional mobility and security
       features HIP provides).

    2. One where the initial xTR->xTR opening message is a hybrid
       that indicates that the sender understands both LISP and HIP,
       allowing the receiver to pick which one to use.


http://www.irtf.org/pipermail/rrg/2009-January/000742.html  PN

  Advantages and disadvantages of above approach(es).


http://www.irtf.org/pipermail/rrg/2009-January/000743.html  PN

  Discussion with Dino on how the above approach(es) might
  compare with (or be combined with?) LISP.


http://www.irtf.org/pipermail/rrg/2009-January/000745.html  TH

  Distinctions between "xTR" (I think this means LISP and other
  core-edge separation solutions) and HIP / HIP-proxy.


http://www.irtf.org/pipermail/rrg/2009-January/000746.html  TH

  Pointer to slides describing Boeing's experience with HIP to
  provide secure Layer 2 VPN over untrusted wireless network -
  for instance in the airliner factory.
  http://www.ietf.org/proceedings/08nov/slides/HIPRG-0.pdf


http://www.irtf.org/pipermail/rrg/2009-January/000747.html  SB

  "Mapping" in HIP?  Potential problems with pushing path selection
  (as an example) responsibility to hosts.


http://www.irtf.org/pipermail/rrg/2009-January/000748.html  FT

  HIP: HIT   = identity
       iRLOC = inner routing locator
       oRLOC = outer routing locator

  LISP (and perhaps others): EID  ~= iRLOC
                             RLOC ~= oRLOC



  - Robin

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Wed Jan  7 19:33:13 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 333BD3A699C;
	Wed,  7 Jan 2009 19:33:13 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 519333A6984
	for <rrg@core3.amsl.com>; Wed,  7 Jan 2009 19:33:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.991
X-Spam-Level: 
X-Spam-Status: No, score=-1.991 tagged_above=-999 required=5
	tests=[AWL=-0.392, BAYES_00=-2.599, J_BACKHAIR_34=1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id GlfhTZkEg4DK for <rrg@core3.amsl.com>;
	Wed,  7 Jan 2009 19:33:11 -0800 (PST)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.235])
	by core3.amsl.com (Postfix) with ESMTP id 84B3A3A699C
	for <rrg@irtf.org>; Wed,  7 Jan 2009 19:33:11 -0800 (PST)
Received: by rv-out-0506.google.com with SMTP id f6so10807931rvb.7
	for <rrg@irtf.org>; Wed, 07 Jan 2009 19:32:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from
	:organization:user-agent:mime-version:to:cc:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=c/qoA1NrMDwqRKFE/GEwKiHwowdCxMKsijsvABNLueI=;
	b=Yj3CF8Jb7ikrwM9/NpC4YIcK90lykVmvDlOz6x6r5cUeMQ67ICjgD+Wy7BnpC9DN3B
	rm1dC5fGxnz9XTIT6gMtmhuGmRsdKf4IHMAIPVdxeJYdumQGgUArQNYNzcYuQbqAkht+
	TtVan0YVIOHl6fPFwDS3ZVW+ZBSZJAn0DRoVc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	b=IxArqj4vic5N+YSb2QW729zBMZEfJ/Wsv+Xfgq0uH1OmicwhumbQ7bqsNiceCk6zhL
	F87DQRQHDb82cvXU6pbUd2NDXYqcUqm7PPYwv7jTTQjKjmTzug9sfgxGgZOUBVJ8jH2h
	gJOtUqSPaEqOY+KV0KUarXhtWZXYVBPM8doVs=
Received: by 10.141.2.18 with SMTP id e18mr11862493rvi.142.1231385577105;
	Wed, 07 Jan 2009 19:32:57 -0800 (PST)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz
	[130.216.38.124])
	by mx.google.com with ESMTPS id l31sm1133565rvb.2.2009.01.07.19.32.55
	(version=SSLv3 cipher=RC4-MD5); Wed, 07 Jan 2009 19:32:56 -0800 (PST)
Message-ID: <496573E2.7000703@gmail.com>
Date: Thu, 08 Jan 2009 16:32:50 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
References: <495F0BAA.2040303@firstpr.com.au><49611E83.8050301@gmail.com><4961CFD3.2050304@firstpr.com.au><D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com><20EEF623-B503-4994-B099-64715E567B2D@cisco.com><474EEBD229DF754FB83D256004D021080AD5E539@XCH-NW-6V1.nw.nos.boeing.com><39C363776A4E8C4A94691D2BD9D1C9A105623AC3@XCH-NW-7V2.nw.nos.boeing.com>	<96CDEE57-28F3-416C-8AAD-D3F7330B3C5A@nomadiclab.com>	<77F357662F8BFA4CA7074B0410171B6D07B0BC42@XCH-NW-5V1.nw.nos.boeing.com>
	<39C363776A4E8C4A94691D2BD9D1C9A10566DB53@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A10566DB53@XCH-NW-7V2.nw.nos.boeing.com>
Cc: RRG <rrg@irtf.org>, Robin Whittle <rw@firstpr.com.au>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Fred,

That's my mental model, except that I think of the locators
as LOC0, LOC1, etc to allow for the inevitable hierarchy.
I had also assumed there would need to be a hierarchy of maps,
with HIT<->LOC0 as the lowest level map, but Scott Brim obviously
has another model in mind (I need to think a bit more before
replying to Scott).

   Brian

On 2009-01-08 11:49, Templin, Fred L wrote:
> Regarding HIP + map/encaps, maybe it is obvious to everyone
> else already but I think what that gives you is an endpoint
> identity (the HIT), an inner routing locator (iRLOC), and an
> outer RLOC (oRLOC). Up to now, LISP (and perhaps others) have
> been using the term "EID" to refer to what I mean by "iRLOC",
> and the term "RLOC" to refer to what I mean by "oRLOC".
> 
> In this sense, "oRLOC" is routable within the scope of an
> interdomain region, while "iRLOC" is routable only within and
> end site (or edge network, or whatever you want to call it).
> The HIP HIT is not routable within any scope so it is purely
> an identifier and not a locator.
> 
> Is this news to anyone, or already so obvious that it doesn't
> even bear mention? (Will check back later; I really need to
> be off doing other things...)
> 
> Fred
> fred.l.templin@boeing.com 
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> https://www.irtf.org/mailman/listinfo/rrg
> 
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Wed Jan  7 19:52:04 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B89303A6984;
	Wed,  7 Jan 2009 19:52:04 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8DE2B3A6948
	for <rrg@core3.amsl.com>; Wed,  7 Jan 2009 19:52:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.403
X-Spam-Level: 
X-Spam-Status: No, score=0.403 tagged_above=-999 required=5 tests=[AWL=0.298, 
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 
	J_CHICKENPOX_75=0.6, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id H2XGED+1uuEb for <rrg@core3.amsl.com>;
	Wed,  7 Jan 2009 19:52:02 -0800 (PST)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67])
	by core3.amsl.com (Postfix) with ESMTP id A05CD3A681F
	for <rrg@irtf.org>; Wed,  7 Jan 2009 19:52:02 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12])
	by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0KD4002JTVWQK6@szxga04-in.huawei.com> for
	rrg@irtf.org; Thu, 08 Jan 2009 11:48:26 +0800 (CST)
Received: from x41208a ([10.111.12.103])
	by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0KD4000PPVWMIR@szxga04-in.huawei.com> for
	rrg@irtf.org; Thu, 08 Jan 2009 11:48:26 +0800 (CST)
Date: Thu, 08 Jan 2009 11:48:22 +0800
From: Xu Xiaohu <xuxh@huawei.com>
In-reply-to: <39C363776A4E8C4A94691D2BD9D1C9A10566DB53@XCH-NW-7V2.nw.nos.boeing.com>
To: "'Templin, Fred L'" <Fred.L.Templin@boeing.com>,
	"'Henderson, Thomas R'" <thomas.r.henderson@boeing.com>,
	'Pekka Nikander' <pekka.nikander@nomadiclab.com>
Message-id: <002c01c97143$f45a35b0$670c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Mailer: Microsoft Office Outlook 11
Thread-index: Aclwu0THNvEQo4tdREuwq6kI9DQf4AAQ3J4gAAaAAbAACWrOwA==
Cc: 'RRG' <rrg@irtf.org>, 'Robin Whittle' <rw@firstpr.com.au>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org


> 
> Regarding HIP + map/encaps, maybe it is obvious to everyone 
> else already but I think what that gives you is an endpoint 
> identity (the HIT), an inner routing locator (iRLOC), and an 
> outer RLOC (oRLOC). Up to now, LISP (and perhaps others) have 
> been using the term "EID" to refer to what I mean by "iRLOC", 
> and the term "RLOC" to refer to what I mean by "oRLOC".

Since a pure id/locator split solution (e.g. HIP) could use multiple PA
address (locator) which are topologically aggregatable, there may be no need
to use the two layers of locator(iRLOC and oRLOC)

> In this sense, "oRLOC" is routable within the scope of an 
> interdomain region, while "iRLOC" is routable only within and 
> end site (or edge network, or whatever you want to call it).
> The HIP HIT is not routable within any scope so it is purely 
> an identifier and not a locator.

When a legecy host A initiates a communication with a HIP-enabled host B,  A
could send a packet to a nearby proxy (like ITR's role) by using B's HIT as
locator. Upon receiving the packet, the proxy will resolve B's HIT to B's
locator, and send the packet to B, while using its locator as the packet's
source locator and generating a temperay HIT for  A. B will then send
response packet to the above proxy. The proxy will do reverse mapping from
the temporary HIT of A to the IP address of A,  and then send the packet in
legacy IP format to A.  

It's just my assumption. 

Xiaohu



_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Wed Jan  7 20:09:16 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9BA293A681F;
	Wed,  7 Jan 2009 20:09:16 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D8C7F3A681F
	for <rrg@core3.amsl.com>; Wed,  7 Jan 2009 20:09:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.07
X-Spam-Level: 
X-Spam-Status: No, score=0.07 tagged_above=-999 required=5 tests=[AWL=0.565,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,
	RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 5VQVgbOTgDWq for <rrg@core3.amsl.com>;
	Wed,  7 Jan 2009 20:09:14 -0800 (PST)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67])
	by core3.amsl.com (Postfix) with ESMTP id B1F6C3A67B3
	for <rrg@irtf.org>; Wed,  7 Jan 2009 20:09:13 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12])
	by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0KD400GNUWUPVK@szxga04-in.huawei.com> for
	rrg@irtf.org; Thu, 08 Jan 2009 12:08:49 +0800 (CST)
Received: from x41208a ([10.111.12.103])
	by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0KD4002JTWUM5G@szxga04-in.huawei.com> for
	rrg@irtf.org; Thu, 08 Jan 2009 12:08:49 +0800 (CST)
Date: Thu, 08 Jan 2009 12:08:46 +0800
From: Xu Xiaohu <xuxh@huawei.com>
In-reply-to: <49654CC6.80802@firstpr.com.au>
To: 'Robin Whittle' <rw@firstpr.com.au>, 'RRG' <rrg@irtf.org>
Message-id: <002d01c97146$cd6b71f0$670c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Mailer: Microsoft Office Outlook 11
Thread-index: AclxKo1N8ldcg2rzQ92CDx4fc+ea2gAG44gA
Subject: Re: [rrg] HIP, Hip-Proxy etc. (Strategy B)
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

> I am hoping to draw the HIP discussion from the "Rejecting 
> all but Strategy A" thread into this thread with an appropriate title.
> 
> No-one has proposed HIP or anything related to HIP as an 
> actual solution to the routing scaling problem.  

Not ture. RANGI (http://www.cse.wustl.edu/~jain/ietf/rangi.htm) ( its old
version is HRA )is actually an id/locator split proposal related to HIP.
Compared with HIP,  RANGI has many differences on the aspects of ID/locator
namespace structures, mapping system and routing system. 

Xiaohu


_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Wed Jan  7 20:20:05 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1C3783A6984;
	Wed,  7 Jan 2009 20:20:05 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 132D33A6984
	for <rrg@core3.amsl.com>; Wed,  7 Jan 2009 20:20:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.026
X-Spam-Level: 
X-Spam-Status: No, score=-6.026 tagged_above=-999 required=5
	tests=[AWL=-0.427, BAYES_00=-2.599, J_BACKHAIR_34=1,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 2o-6OwEJJk0a for <rrg@core3.amsl.com>;
	Wed,  7 Jan 2009 20:20:02 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 116B23A681F
	for <rrg@irtf.org>; Wed,  7 Jan 2009 20:20:01 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,231,1231113600"; d="scan'208";a="33128030"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 08 Jan 2009 04:19:48 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n084JmY0025867; 
	Wed, 7 Jan 2009 23:19:48 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n084Jm3Y004603;
	Thu, 8 Jan 2009 04:19:48 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 7 Jan 2009 23:19:48 -0500
Received: from sbrim-mbp.local ([64.102.8.172]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 7 Jan 2009 23:19:47 -0500
Message-ID: <49657EE3.6000403@employees.org>
Date: Wed, 07 Jan 2009 23:19:47 -0500
From: Scott Brim <swb@employees.org>
User-Agent: Thunderbird 2.0.0.18 (Macintosh/20081105)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <495F0BAA.2040303@firstpr.com.au><49611E83.8050301@gmail.com><4961CFD3.2050304@firstpr.com.au><D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com><20EEF623-B503-4994-B099-64715E567B2D@cisco.com><474EEBD229DF754FB83D256004D021080AD5E539@XCH-NW-6V1.nw.nos.boeing.com><39C363776A4E8C4A94691D2BD9D1C9A105623AC3@XCH-NW-7V2.nw.nos.boeing.com>	<96CDEE57-28F3-416C-8AAD-D3F7330B3C5A@nomadiclab.com>	<77F357662F8BFA4CA7074B0410171B6D07B0BC42@XCH-NW-5V1.nw.nos.boeing.com>	<39C363776A4E8C4A94691D2BD9D1C9A10566DB53@XCH-NW-7V2.nw.nos.boeing.com>
	<496573E2.7000703@gmail.com>
In-Reply-To: <496573E2.7000703@gmail.com>
X-OriginalArrivalTime: 08 Jan 2009 04:19:47.0618 (UTC)
	FILETIME=[577D4020:01C97148]
Authentication-Results: rtp-dkim-1; header.From=swb@employees.org; dkim=neutral
Cc: RRG <rrg@irtf.org>, Robin Whittle <rw@firstpr.com.au>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Brian E Carpenter allegedly wrote on 1/7/09 10:32 PM:
> Fred,
> 
> That's my mental model, except that I think of the locators
> as LOC0, LOC1, etc to allow for the inevitable hierarchy.
> I had also assumed there would need to be a hierarchy of maps,
> with HIT<->LOC0 as the lowest level map, but Scott Brim obviously
> has another model in mind (I need to think a bit more before
> replying to Scott).
> 
>    Brian

What HIP gives you is an identifier that may be used for many things.
An HI can be, but does not have to be, part of the process of initially
finding a locator for an endpoint. For example, I can go straight from
domain name to locator (which actually might be an agent / proxy /
rendezvous point), and then validate identities via some other means.

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Wed Jan  7 20:22:11 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D19CA3A69CE;
	Wed,  7 Jan 2009 20:22:11 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D59843A69CE
	for <rrg@core3.amsl.com>; Wed,  7 Jan 2009 20:22:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.216
X-Spam-Level: 
X-Spam-Status: No, score=-6.216 tagged_above=-999 required=5
	tests=[AWL=-0.217, BAYES_00=-2.599, J_CHICKENPOX_75=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id P2zTrFgjjgDy for <rrg@core3.amsl.com>;
	Wed,  7 Jan 2009 20:22:10 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id D73423A6916
	for <rrg@irtf.org>; Wed,  7 Jan 2009 20:22:09 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,231,1231113600"; d="scan'208";a="33166884"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 08 Jan 2009 04:21:56 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n084LuEq031342; 
	Wed, 7 Jan 2009 23:21:56 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n084Luhg027175;
	Thu, 8 Jan 2009 04:21:56 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 7 Jan 2009 23:21:55 -0500
Received: from sbrim-mbp.local ([64.102.8.172]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 7 Jan 2009 23:21:55 -0500
Message-ID: <49657F62.5010303@employees.org>
Date: Wed, 07 Jan 2009 23:21:54 -0500
From: Scott Brim <swb@employees.org>
User-Agent: Thunderbird 2.0.0.18 (Macintosh/20081105)
MIME-Version: 1.0
To: Xu Xiaohu <xuxh@huawei.com>
References: <002c01c97143$f45a35b0$670c6f0a@china.huawei.com>
In-Reply-To: <002c01c97143$f45a35b0$670c6f0a@china.huawei.com>
X-OriginalArrivalTime: 08 Jan 2009 04:21:55.0665 (UTC)
	FILETIME=[A3CFAC10:01C97148]
Authentication-Results: rtp-dkim-2; header.From=swb@employees.org; dkim=neutral
Cc: 'RRG' <rrg@irtf.org>, 'Robin Whittle' <rw@firstpr.com.au>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Xu Xiaohu allegedly wrote on 1/7/09 10:48 PM:
>> Regarding HIP + map/encaps, maybe it is obvious to everyone 
>> else already but I think what that gives you is an endpoint 
>> identity (the HIT), an inner routing locator (iRLOC), and an 
>> outer RLOC (oRLOC). Up to now, LISP (and perhaps others) have 
>> been using the term "EID" to refer to what I mean by "iRLOC", 
>> and the term "RLOC" to refer to what I mean by "oRLOC".
> 
> Since a pure id/locator split solution (e.g. HIP) could use multiple PA
> address (locator) which are topologically aggregatable, there may be no need
> to use the two layers of locator(iRLOC and oRLOC)
> 
>> In this sense, "oRLOC" is routable within the scope of an 
>> interdomain region, while "iRLOC" is routable only within and 
>> end site (or edge network, or whatever you want to call it).
>> The HIP HIT is not routable within any scope so it is purely 
>> an identifier and not a locator.
> 
> When a legecy host A initiates a communication with a HIP-enabled host B,  A
> could send a packet to a nearby proxy (like ITR's role) by using B's HIT as
> locator. 

Would you replace host B's A record with a HIT?  Or would this require a
modification to host A?  If you're going to modify A, why not just
implement HIP?

Thanks ... Scott

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Wed Jan  7 21:26:17 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3C0763A680B;
	Wed,  7 Jan 2009 21:26:17 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F419B3A67B3
	for <rrg@core3.amsl.com>; Wed,  7 Jan 2009 21:26:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.489
X-Spam-Level: 
X-Spam-Status: No, score=-6.489 tagged_above=-999 required=5 tests=[AWL=0.110, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id kqy5Xrwo5Qak for <rrg@core3.amsl.com>;
	Wed,  7 Jan 2009 21:26:16 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 007EF3A680B
	for <rrg@irtf.org>; Wed,  7 Jan 2009 21:26:15 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,231,1231113600"; d="scan'208";a="225829143"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-6.cisco.com with ESMTP; 08 Jan 2009 05:25:56 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n085Pumr009511; 
	Wed, 7 Jan 2009 21:25:56 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n085Pucd011398;
	Thu, 8 Jan 2009 05:25:56 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 7 Jan 2009 21:25:56 -0800
Received: from moveme.cisco.com ([10.21.75.9]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 7 Jan 2009 21:25:56 -0800
Message-Id: <97BAE464-611E-419A-A519-B51BEA76F9E0@cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: Pekka Nikander <pekka.nikander@nomadiclab.com>
In-Reply-To: <14F8EAC5-AB88-45A1-A58D-AF270F0C7A90@nomadiclab.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Wed, 7 Jan 2009 21:25:54 -0800
References: <495F0BAA.2040303@firstpr.com.au><49611E83.8050301@gmail.com><4961CFD3.2050304@firstpr.com.au><D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com><20EEF623-B503-4994-B099-64715E567B2D@cisco.com>
	<474EEBD229DF754FB83D256004D021080AD5E539@XCH-NW-6V1.nw.nos.boeing.com>
	<39C363776A4E8C4A94691D2BD9D1C9A105623AC3@XCH-NW-7V2.nw.nos.boeing.com>
	<4FF36C8D-761D-4D45-BB99-A5E72B9E33C9@cisco.com>
	<14F8EAC5-AB88-45A1-A58D-AF270F0C7A90@nomadiclab.com>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 08 Jan 2009 05:25:56.0264 (UTC)
	FILETIME=[94FC9280:01C97151]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2551; t=1231392356;
	x=1232256356; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dino@cisco.com;
	z=From:=20Dino=20Farinacci=20<dino@cisco.com>
	|Subject:=20Re=3A=20[rrg]=20Rejecting=20all=20but=20Strateg
	y=20A |Sender:=20;
	bh=PaOGzCC4BpXmxay3lUv8fKOTM0lZKfarTnNekutpTxI=;
	b=ghAc3M8AdGXzhg5CshydmOEhKMTDJepvZ0ASy5TJeAOlb68hYCEneRjkhV
	xs74TlaRdonIjIG6PPr5T+vhhggaz25Ss+vy0dfXAbWDBzJluKrtsrccA2zt
	JI2wjcISaOL1fLLUzoSqRQXi+egqIJsVnIPvKnd2RzGdzaahGwstU=;
Authentication-Results: sj-dkim-1; header.From=dino@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: RRG <rrg@irtf.org>, Robin Whittle <rw@firstpr.com.au>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

With respect to security in LHIP by using hash-chains, we consider  
them for LISP, but requires 3 to 4 packet exchanges, so a non-starter.

Dino

On Jan 7, 2009, at 3:47 AM, Pekka Nikander wrote:

> On 6 Jan 2009, at 00:01, Dino Farinacci wrote:
>> Before we get carried away with what looks like a convergence of  
>> "HIP-proxy and LISP", tell me what HIP offers to a LISP router that  
>> the LISP architecture does not already provide?
>
> I don't know what LISP already provides, so the following are mere  
> guesses.
>
> - Security?  Both opportunistic, no-infrastructure-requiring  
> security for multi-homing/mobility, and baseline-level signalling  
> security for integrating any security infrastructure you want (such  
> as PKI, AAA, ...)
>
> - Mobility?  As HIP proxy can be trivially integrated with the HIP  
> mobile router (MR), the legacy networks can be mobile without any  
> extra effort.  (Provided that the mapping infra has the required  
> updating capability...)
>
> - Ability to move more cleanly to a host-based solution, better  
> serving mobile and multi-interface hosts.  This includes the ability  
> to support upgraded hosts in the legacy networks.
>
> Obviously, the next question is what the drawbacks would be.  Here  
> is my initial list:
>
> - Crypto.  Current HIP requires PK crypto (but no PKI!) and ESP.   
> LHIP (which uses only hash functions) is an option if people  
> generally shun PK, and, as I already explained, ESP can be replaced  
> with any tunnelling or flow-identifying protocol.
>
> - Lack of operational experience.  AFAIK, only Boeing has  
> operational experience on HIP.  I guess there is more operational  
> experience available on LISP, even though I haven't seen any.
>
> (I am sure there are others, but I cannot figure out any other  
> drawbacks right now.)
>
>> If is solely a add a pure definition to IDs and RLOCs, then I think  
>> it's not worth the cost of deployment to do so.
>
> Agreed.
>
> Obviously, _for_me_ the main benefit would be the ability to cleanly  
> move to a host-based solution, in such a way that the upgraded  
> mobile hosts could work both stand-alone in the "new internet" (at  
> the non-legacy side of xTRs) and in the legacy networks, without any  
> extra overhead.  (That is, any upgraded hosts at the legacy networks  
> would report their existence to the xTR, which would understand  
> their presence, avoiding double encapsulation and signalling  
> overhead).
>
> --Pekka
>

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Wed Jan  7 21:27:49 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 760793A67F2;
	Wed,  7 Jan 2009 21:27:49 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 125CD3A67F2
	for <rrg@core3.amsl.com>; Wed,  7 Jan 2009 21:27:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.493
X-Spam-Level: 
X-Spam-Status: No, score=-6.493 tagged_above=-999 required=5 tests=[AWL=0.106, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id BkAVHDrmNrEM for <rrg@core3.amsl.com>;
	Wed,  7 Jan 2009 21:27:48 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 4EFC33A67B3
	for <rrg@irtf.org>; Wed,  7 Jan 2009 21:27:48 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,231,1231113600"; d="scan'208";a="225829934"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 08 Jan 2009 05:27:35 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id n085RZNl002962; 
	Wed, 7 Jan 2009 21:27:35 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n085RZNv012730;
	Thu, 8 Jan 2009 05:27:35 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 7 Jan 2009 21:27:34 -0800
Received: from moveme.cisco.com ([10.21.75.9]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 7 Jan 2009 21:27:34 -0800
Message-Id: <256FCF06-2A53-4E8D-8B1A-8BBC336F03D2@cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: Pekka Nikander <pekka.nikander@nomadiclab.com>
In-Reply-To: <1E8EC4E2-2365-4826-BC5C-1ADCB97C0E06@nomadiclab.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Wed, 7 Jan 2009 21:27:32 -0800
References: <495F0BAA.2040303@firstpr.com.au>
	<49611E83.8050301@gmail.com><4961CFD3.2050304@firstpr.com.au><D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com>
	<20EEF623-B503-4994-B099-64715E567B2D@cisco.com>
	<474EEBD229DF754FB83D256004D021080AD5E539@XCH-NW-6V1.nw.nos.boeing.com>
	<E294A8E4-57E3-48D3-BE17-B0EF2BD46DA4@cisco.com>
	<1E8EC4E2-2365-4826-BC5C-1ADCB97C0E06@nomadiclab.com>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 08 Jan 2009 05:27:34.0717 (UTC)
	FILETIME=[CFAB4ED0:01C97151]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2396; t=1231392455;
	x=1232256455; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dino@cisco.com;
	z=From:=20Dino=20Farinacci=20<dino@cisco.com>
	|Subject:=20Re=3A=20[rrg]=20Rejecting=20all=20but=20Strateg
	y=20A |Sender:=20;
	bh=otSbZagwKoSo9Ru6RajIxWWI8JxLmUJjH1O+BC29SR0=;
	b=fyzU9UHViZia7CjYcc0S6ZBH3xVm2oZUkBYpRqNE5QrmKiPK/pGguVwI1v
	5o1NAE++RSQjtcr55uEP2FTyuT/skYEdBLx6gB6e3hjAxp707n+Cz/0kAGLN
	7iK5vk/76J;
Authentication-Results: sj-dkim-4; header.From=dino@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: RRG <rrg@irtf.org>, Robin Whittle <rw@firstpr.com.au>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

I'm not seeing any compelling benefit here Pekka. Just that HIP is  
different and the stuff it does have that LISP currently doesn't is  
too heavy-weight. This is just my opinion and a judgement.

Dino

On Jan 7, 2009, at 3:55 AM, Pekka Nikander wrote:

> Eric wrote:
>>> By combining a true locator-identifier split (i.e., HIP) with a
>>> map-and-encaps (e.g., LISP) one gets the combined benefits of both
>>> approaches. Those benefits are
>
> Dino replied:
>>
>> But you add another layer of addressing that is probably more than  
>> the user wants. It could get this bad:
>>
>> HIT -> EID -> private-RLOC -> public-RLOC    when behind a NAT
>>
>> or
>>
>> HIT -> private-EID -> public-EID -> RLOC     when behind a NAT
>
> I don't think those mappings are right.
>
> If there is a NAT between the xTR/HIP-proxy and the "new" internet,  
> the mapping would be:
>
> EID -> (HIT) -> private-RLOC -> public-RLOC
>
> where the HIT would be invisible everywhere but inside the HIP  
> proxies and within the signalling protocol between the HIP proxies.
>
> If there is a NAT between the legacy host and the xTR/HIP-proxy, the  
> mapping would be:
>
> private-EID -> public-EID -> (HIT) -> RLOC
>
> where again the HIT would be invisible, as explained above.
>
>> 2-levels of mapping is plenty, adding 2 more probably is a non- 
>> starter. Remember folks, we have to incrementally deploy this with  
>> minimal cost, see Yakov's post early today, he makes good points.
>
> I don't see how replacing the xTR internal functionality with the  
> HIP-proxy functionality would add much cost.  It would change the  
> protocol between the xTRs, yes.  HIP as a protocol is probably more  
> complex than the present xTR-xTR protocol, but it is well tested,  
> been in operational use at Boeing for a few years, as has three open  
> source implementations.
>
> There is an extra mapping, i.e. replacing the EID->RLOC mapping with  
> a EID->(HIT)->RLOC mapping.  But that mapping is internal to the  
> proxies and the signalling protocol, and not visible outside.  In  
> the simplest case the HITs would be ephemeral and opportunistic,  
> requiring no configuration or storage anywhere.  (The benefit from  
> them is in terms of security and mobility, especially in more  
> complex scenarios than the simplest case.)
>
> --Pekka
>

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Wed Jan  7 21:30:12 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A9E3F3A67F2;
	Wed,  7 Jan 2009 21:30:12 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3C2B73A67F2
	for <rrg@core3.amsl.com>; Wed,  7 Jan 2009 21:30:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.013
X-Spam-Level: 
X-Spam-Status: No, score=0.013 tagged_above=-999 required=5 tests=[AWL=0.508, 
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 
	RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id sWzX+NKPLXco for <rrg@core3.amsl.com>;
	Wed,  7 Jan 2009 21:30:10 -0800 (PST)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67])
	by core3.amsl.com (Postfix) with ESMTP id 582853A67B3
	for <rrg@irtf.org>; Wed,  7 Jan 2009 21:30:10 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12])
	by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0KD50066X0LM8Y@szxga04-in.huawei.com> for
	rrg@irtf.org; Thu, 08 Jan 2009 13:29:46 +0800 (CST)
Received: from x41208a ([10.111.12.103])
	by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0KD500AOV0LIN1@szxga04-in.huawei.com> for
	rrg@irtf.org; Thu, 08 Jan 2009 13:29:46 +0800 (CST)
Date: Thu, 08 Jan 2009 13:29:42 +0800
From: Xu Xiaohu <xuxh@huawei.com>
In-reply-to: <49657F62.5010303@employees.org>
To: 'Scott Brim' <swb@employees.org>
Message-id: <002e01c97152$1c15fdb0$670c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Mailer: Microsoft Office Outlook 11
Thread-index: AclxSSvo2f3ViwPjThC6Gb8x8ADmCwAB/Puw
Cc: 'RRG' <rrg@irtf.org>, 'Robin Whittle' <rw@firstpr.com.au>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org


> > When a legecy host A initiates a communication with a 
> HIP-enabled host 
> > B,  A could send a packet to a nearby proxy (like ITR's 
> role) by using 
> > B's HIT as locator.
> 
> Would you replace host B's A record with a HIT?  Or would 
> this require a modification to host A?  If you're going to 
> modify A, why not just implement HIP?

Replacing host B's AAAA record with a HIT is my thought. If a legacy host
got B's AAAA record from DNS, it will look that record as a IPv6 address
And the mapping between HIT and locator (IP address) can be maintained in a
seperate mapping system, e.g. a hierarchical DHT system. 
 
Xiaohu


_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Wed Jan  7 21:45:04 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C80C53A68B8;
	Wed,  7 Jan 2009 21:45:03 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3E2AE3A68B8
	for <rrg@core3.amsl.com>; Wed,  7 Jan 2009 21:45:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.53
X-Spam-Level: 
X-Spam-Status: No, score=-0.53 tagged_above=-999 required=5 tests=[AWL=-0.712, 
	BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327,
	SUBJ_ALL_CAPS=2.077]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ww2WXtPBkj5X for <rrg@core3.amsl.com>;
	Wed,  7 Jan 2009 21:45:01 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123])
	by core3.amsl.com (Postfix) with ESMTP id 235143A67A7
	for <rrg@irtf.org>; Wed,  7 Jan 2009 21:45:01 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6])
	by gair.firstpr.com.au (Postfix) with ESMTP id 63A1F17571E;
	Thu,  8 Jan 2009 16:44:46 +1100 (EST)
Message-ID: <496592D1.40602@firstpr.com.au>
Date: Thu, 08 Jan 2009 16:44:49 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: RRG <rrg@irtf.org>
Subject: [rrg] RANGI (~~= HIP?)
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Hi Xu,

Thanks for this pointer in the "HIP, Hip-Proxy etc. (Strategy B)" thread:

>> No-one has proposed HIP or anything related to HIP as an
>> actual solution to the routing scaling problem.
>
> Not ture. RANGI (http://www.cse.wustl.edu/~jain/ietf/rangi.htm)

and http://www.cse.wustl.edu/~jain/ietf/ftp/rangi.pdf

> (its old version is HRA )is actually an id/locator split proposal
> related to HIP.  Compared with HIP,  RANGI has many differences on
> the aspects of ID/locator namespace structures, mapping system and
> routing system.

I am only vaguely familiar with HIP and I looked only briefly at the
above slides, but I suggest that your proposal is not sufficiently
like HIP to consider it as part of a HIP discussion.

Do you and your colleagues suggest RANGI as the solution, or one of
the potential solutions, which the RRG should recommend to the IETF
for full-scale development?

If so, then I suggest it would be good to write up an Analysis and
Summary document and link to it from the RRG wiki.

Also, I suggest you either nominate a strategy in Bill's page which
it matches:

  http://bill.herrin.us/network/rrgarchitectures.html

or suggest changes to that page so your proposal fits in somewhere.
I think it is important that Bill's page covers every proposal which
anyone is seriously suggesting the RRG think about.  I think this
should include any idea for a potential solution, even if its
proponents don't think the IETF should start developing it soon.

  - Robin
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan  8 00:53:41 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 221B628C0F4;
	Thu,  8 Jan 2009 00:53:41 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4CFEF28C0F4
	for <rrg@core3.amsl.com>; Thu,  8 Jan 2009 00:53:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.785
X-Spam-Level: 
X-Spam-Status: No, score=-0.785 tagged_above=-999 required=5 tests=[AWL=1.214, 
	BAYES_00=-2.599, J_CHICKENPOX_35=0.6]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id GtYdzFQMOg1p for <rrg@core3.amsl.com>;
	Thu,  8 Jan 2009 00:53:32 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66])
	by core3.amsl.com (Postfix) with ESMTP id 01F453A6827
	for <rrg@irtf.org>; Thu,  8 Jan 2009 00:53:32 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0KD500M1X9VS17@szxga03-in.huawei.com> for
	rrg@irtf.org; Thu, 08 Jan 2009 16:50:16 +0800 (CST)
Received: from x41208a ([10.111.12.103])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0KD500M7P9VRO9@szxga03-in.huawei.com> for
	rrg@irtf.org; Thu, 08 Jan 2009 16:50:16 +0800 (CST)
Date: Thu, 08 Jan 2009 16:50:15 +0800
From: Xu Xiaohu <xuxh@huawei.com>
In-reply-to: <496592D1.40602@firstpr.com.au>
To: 'Robin Whittle' <rw@firstpr.com.au>, 'RRG' <rrg@irtf.org>
Message-id: <003001c9716e$20888950$670c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Mailer: Microsoft Office Outlook 11
Thread-index: AclxWDu7d9woZm3kTJGhVVOUTl9o7QAEdLGA
Subject: Re: [rrg] RANGI (~~= HIP?)
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Hi Robin,

> I am only vaguely familiar with HIP and I looked only briefly 
> at the above slides, but I suggest that your proposal is not 
> sufficiently like HIP to consider it as part of a HIP discussion.

It's better to discuss map&encap and pure id/loc split approach, but not
focus too much on one concrete proposal:)

> Do you and your colleagues suggest RANGI as the solution, or 
> one of the potential solutions, which the RRG should 
> recommend to the IETF for full-scale development?

Both map&encap and pure id/locator split approach have it's own pros and
cons, and maybe they can be complementary to each other. So I hope both of
them should be recommended and of course be optimized continually, which may
be the rough consensus to be reached finally :)

> If so, then I suggest it would be good to write up an 
> Analysis and Summary document and link to it from the RRG wiki.

Thanks for your kindly suggestion, I will try to write an updated draft.

> Also, I suggest you either nominate a strategy in Bill's page 
> which it matches:
> 
>   http://bill.herrin.us/network/rrgarchitectures.html
> 
> or suggest changes to that page so your proposal fits in somewhere.
> I think it is important that Bill's page covers every 
> proposal which anyone is seriously suggesting the RRG think 
> about.  I think this should include any idea for a potential 
> solution, even if its proponents don't think the IETF should 
> start developing it soon.

RANGI may be close to Stragety B. I'm not sure since I need some time to
read Bill's page carefully.

Xiaohu

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan  8 02:37:18 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9725D3A687C;
	Thu,  8 Jan 2009 02:37:18 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 86E383A687C
	for <rrg@core3.amsl.com>; Thu,  8 Jan 2009 02:37:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id lBjYn2Q-UWRa for <rrg@core3.amsl.com>;
	Thu,  8 Jan 2009 02:37:16 -0800 (PST)
Received: from n2.nomadiclab.com (n2.nomadiclab.com
	[IPv6:2001:14b8:400:101::2])
	by core3.amsl.com (Postfix) with ESMTP id EF6B93A680B
	for <rrg@irtf.org>; Thu,  8 Jan 2009 02:37:15 -0800 (PST)
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id CFE4A1EF126;
	Thu,  8 Jan 2009 12:37:00 +0200 (EET)
Received: from [127.0.0.1] (localhost [IPv6:::1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 5F14D1EF125;
	Thu,  8 Jan 2009 12:37:00 +0200 (EET)
Message-Id: <BA5C3152-6F86-474D-9EEF-314DF18B1190@nomadiclab.com>
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
To: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
In-Reply-To: <77F357662F8BFA4CA7074B0410171B6D07B0BC42@XCH-NW-5V1.nw.nos.boeing.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Thu, 8 Jan 2009 12:36:58 +0200
References: <495F0BAA.2040303@firstpr.com.au><49611E83.8050301@gmail.com><4961CFD3.2050304@firstpr.com.au><D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com><20EEF623-B503-4994-B099-64715E567B2D@cisco.com><474EEBD229DF754FB83D256004D021080AD5E539@XCH-NW-6V1.nw.nos.boeing.com><39C363776A4E8C4A94691D2BD9D1C9A105623AC3@XCH-NW-7V2.nw.nos.boeing.com>
	<96CDEE57-28F3-416C-8AAD-D3F7330B3C5A@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D07B0BC42@XCH-NW-5V1.nw.nos.boeing.com>
X-Mailer: Apple Mail (2.930.3)
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: RRG <rrg@irtf.org>, Robin Whittle <rw@firstpr.com.au>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

> [...] HIP-proxy and xTR are not the same thing.  xTR tunnels,  
> mapping entries, cache entries can cover aggregates of hosts, while  
> HIP-proxy has per-host granularity.  xTR doesn't claim to represent  
> any host from a security point of view, while HIP-proxy seems to.


While certainly so at the architectural level, the difference at the  
practical level does not need to be that big.  Everything depends on  
the details, which we obviously do not have.  (Shun me for empty talk,  
if you want.)

First, the packets between xTRs do have per-host granularity, as the  
EIDs are preserved in the inner header.  Hence, conceptually, if you  
want to look at the xTRs from this point of view, you could consider  
each pair of EIDs as a separate "state".  Those states are then  
aggregated to the per-site granularity.

Almost the same thing *could* be done with a HIP proxy, too.  The  
forwarding state could be at a per-site granularity.  (I go into very  
convoluted architectural thinking next, but bear with me to see the  
result).   The ideas is that the HIs representing proxied hosts would  
be expressed only as aggregated delegated state.  That is, from the  
HIP architecture point of view there would be a "virtual" HI for each  
proxied host, as well as for each proxied host at a remote site.   
However, each of the local "virtual" HIs would be "virtually"  
delegated to the HI of the local HIP-proxy; likewise for each remote  
site.  As a result, the HI of the HIP-proxy would represent all the  
"virtual" HIs of the hosts behind it.  In reality, no such "virtual"  
HIs would exist at all, the delegation being fully virtual (or even  
imaginary).  Then, I think, the state at the HIP-proxy would match, in  
terms of granularity, the state at an xTR.

The next obvious question is what's the point?  Why to have such  
virtual, ephemeral, opportunistic HIs for each host if they don't  
exist at all in practise?  The reason is that the architecture could,  
trivially, also allow real, non-virtual, HIs.  That is, in addition to  
representing the legacy hosts at the site through virtual delegation,  
the HIP-proxy could represent real HIP-enabled (mobile) hosts and  
subnetworks through real delegation.

To summarise the above:  In an imaginary world, there would be a HI  
for each legacy host at a site, all those HIs being delegated to the  
HI of the HIP-proxy.  In the real world, there would be only the HI of  
the HIP-proxy, representing the whole legacy site through the  
imaginary delegation.  For HIP-enabled hosts and subnetworks, there  
would of course be actual HIs and real delegation from the HIP-enabled  
host or subnetwork to the HIP-proxy.

>> I don't see any problem at all in installing a HIP proxy and xTR at  
>> the same box -- they could even use the same mapping infrastructure  
>> to find out the RLOC of the peer HIP proxy/xTR, and then in  
>> parallel send an opportunistic HIP I1 and whatever LISP sends when  
>> an xTR contacts another xTR that it has no prior association with.   
>> But that would be a (minor) waste of resources as two packets would  
>> be sent in parallel.
>
> This would probably increase the load on the mapping system and xTRs  
> considerably, because of the per-host granularity.

It does not necessarily increase the load, as should be obvious from  
the above.  First, even if the end-host HIs were real ones and not  
imaginary ones, there is no need to store them to the mapping system.   
Second, if they are imaginary ones, they don't even exist elsewhere  
but as a concept.  So, there is no operational cost and there are  
benefits you get if HIP becomes more common.

> I'm not sure how it would work for multiple ITRs and ETRs, are there  
> multiple proxy host identities, one for each xTR?  How is that  
> handled with mobility or path unavailability events?

As long as you speak about mobility of the mobility HIP-proxy or path  
unavailability between HIP-proxies, it works just as if the proxies  
were individual HIP hosts hosting multiple HIs.  If you speak about  
legacy host mobility, obviously it doesn't work.  For the details of  
mobile HIP hosts moving from one HIP-proxy to another HIP-proxy, I  
don't know if anyone has written down the details.

> It changes the security model for HIP-- when I move behind some ITR,  
> am
> I going to want my packets to flow unprotected between my host  
> interface
> and the ITR?

If you are a legacy host, what else could you do?  If you are a HIP  
host, the ITR would look like a HIP MR to you.

> Am I going to trust arbitrary ITRs to proxy for my host?

That is an operational choice that you have to make.

> Also, are ITRs going to have any incentives to give me good (or any)  
> HIP service?

What incentive do they to give you any service in the first place?

>> Initially, what I think would be interesting to understand is the  
>> possibility of two additional designs:
>>
>> 1. One where the LISP xTR-xTR protocol is replaced with the HIP  
>> protocol (providing the additional mobility and security features  
>> HIP provides).
>>
>> 2. One where the initial xTR->xTR opening message is a hybrid that  
>> indicates that the sender understands both LISP and HIP, allowing  
>> the receiver to pick which one to use.
>>
>> And then I could imagine a few designs beyond either...
>
> Are you instead suggesting above to look at combining HIP with LISP,  
> or HIP-proxy with LISP?

I'm suggesting them as potential starting points for looking at how to  
combine HIP-proxy with LISP.

> I see the distinction being that HIP with LISP means that HIP keys  
> are used to name xTRs and to secure the xTR to xTR communications  
> (and possibly communications with the mapping system), but otherwise  
> LISP works as described.  Proxy-HIP keys would name individual hosts  
> and would play more of a role as an EID in the system.

I see.  However, I don't see there a big difference, due to the  
imaginary HIs and imaginary delegation making the difference, well,  
imaginary.  :-)

--Pekka

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan  8 02:44:21 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 249D03A6A5E;
	Thu,  8 Jan 2009 02:44:21 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B3E853A6A5E
	for <rrg@core3.amsl.com>; Thu,  8 Jan 2009 02:44:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id j3gI9Vvt2xzi for <rrg@core3.amsl.com>;
	Thu,  8 Jan 2009 02:44:19 -0800 (PST)
Received: from n2.nomadiclab.com (n2.nomadiclab.com
	[IPv6:2001:14b8:400:101::2])
	by core3.amsl.com (Postfix) with ESMTP id 725883A687C
	for <rrg@irtf.org>; Thu,  8 Jan 2009 02:44:18 -0800 (PST)
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 71F4D1EF126;
	Thu,  8 Jan 2009 12:44:04 +0200 (EET)
Received: from [127.0.0.1] (localhost [IPv6:::1])
	by n2.nomadiclab.com (Postfix) with ESMTP id EE8971EF125;
	Thu,  8 Jan 2009 12:44:03 +0200 (EET)
Message-Id: <C83DB85A-CE29-4288-87F8-07447C2DF862@nomadiclab.com>
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A10566DB53@XCH-NW-7V2.nw.nos.boeing.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Thu, 8 Jan 2009 12:44:02 +0200
References: <495F0BAA.2040303@firstpr.com.au><49611E83.8050301@gmail.com><4961CFD3.2050304@firstpr.com.au><D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com><20EEF623-B503-4994-B099-64715E567B2D@cisco.com><474EEBD229DF754FB83D256004D021080AD5E539@XCH-NW-6V1.nw.nos.boeing.com><39C363776A4E8C4A94691D2BD9D1C9A105623AC3@XCH-NW-7V2.nw.nos.boeing.com>
	<96CDEE57-28F3-416C-8AAD-D3F7330B3C5A@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D07B0BC42@XCH-NW-5V1.nw.nos.boeing.com>
	<39C363776A4E8C4A94691D2BD9D1C9A10566DB53@XCH-NW-7V2.nw.nos.boeing.com>
X-Mailer: Apple Mail (2.930.3)
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: RRG <rrg@irtf.org>, Robin Whittle <rw@firstpr.com.au>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

> Regarding HIP + map/encaps, maybe it is obvious to everyone
> else already but I think what that gives you is an endpoint
> identity (the HIT), an inner routing locator (iRLOC), and an
> outer RLOC (oRLOC). Up to now, LISP (and perhaps others) have
> been using the term "EID" to refer to what I mean by "iRLOC",
> and the term "RLOC" to refer to what I mean by "oRLOC".

That is my basic model as well.  Further, as Brian observed, that can  
be applied recursively.

But then there are a few variations.

1. In the case of pure host-based HIP, there is no iRLOC but only the  
HIT:

    HIT -> oRLOC.

2. In the case of host-based HIP and HIP MR, the mapping is HIT ->  
iRLOC -> oRLOC, which can be applied recursively leading to:

    HIT -> LOC0 -> LOCi -> LOCn.

3a. In the case of legacy hosts and HIP proxy, for IPv6 you *can* make  
iRLOC == HIT (which is what we did in the first HIP proxy work,  
described in Patrik's thesis):

    iRLOC == HIT -> oRLOC

3b. Alternatively, you can make HITs and iRLOCs separate, as you need  
for IPv4 anyway:

    iRLOC <-> HIT -> oRLOC

Generalising, we get two cases:

a) host-based HIP generalised:  HIT -> LOC0 -> LOCi -> LOCn

b) proxy HIP generalised:  iRLOC <-> HIT -> LOC0 -> LOCi -> LOCn

In the latter case, the HIT can be "virtual" or "imaginary", if so  
desired.  (See my previous message.)

> In this sense, "oRLOC" is routable within the scope of an
> interdomain region, while "iRLOC" is routable only within and
> end site (or edge network, or whatever you want to call it).
> The HIP HIT is not routable within any scope so it is purely
> an identifier and not a locator.

That is the theory.  As I noted above, for IPv6 you can make HIT ==  
iRLOC if you want.  That is, the format allows that.

--Pekka

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan  8 02:49:04 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6E4833A6A07;
	Thu,  8 Jan 2009 02:49:04 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F11483A6A07
	for <rrg@core3.amsl.com>; Thu,  8 Jan 2009 02:49:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id w6UlOueihsqD for <rrg@core3.amsl.com>;
	Thu,  8 Jan 2009 02:49:02 -0800 (PST)
Received: from n2.nomadiclab.com (n2.nomadiclab.com
	[IPv6:2001:14b8:400:101::2])
	by core3.amsl.com (Postfix) with ESMTP id 21DC93A6A00
	for <rrg@irtf.org>; Thu,  8 Jan 2009 02:49:02 -0800 (PST)
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 157401EF126;
	Thu,  8 Jan 2009 12:48:48 +0200 (EET)
Received: from [127.0.0.1] (localhost [IPv6:::1])
	by n2.nomadiclab.com (Postfix) with ESMTP id D26CE1EF125;
	Thu,  8 Jan 2009 12:48:47 +0200 (EET)
Message-Id: <0FFCF0A4-82C1-43AD-BA67-7F62ED94AE74@nomadiclab.com>
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
To: Dino Farinacci <dino@cisco.com>
In-Reply-To: <97BAE464-611E-419A-A519-B51BEA76F9E0@cisco.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Thu, 8 Jan 2009 12:48:45 +0200
References: <495F0BAA.2040303@firstpr.com.au><49611E83.8050301@gmail.com><4961CFD3.2050304@firstpr.com.au><D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com><20EEF623-B503-4994-B099-64715E567B2D@cisco.com>
	<474EEBD229DF754FB83D256004D021080AD5E539@XCH-NW-6V1.nw.nos.boeing.com>
	<39C363776A4E8C4A94691D2BD9D1C9A105623AC3@XCH-NW-7V2.nw.nos.boeing.com>
	<4FF36C8D-761D-4D45-BB99-A5E72B9E33C9@cisco.com>
	<14F8EAC5-AB88-45A1-A58D-AF270F0C7A90@nomadiclab.com>
	<97BAE464-611E-419A-A519-B51BEA76F9E0@cisco.com>
X-Mailer: Apple Mail (2.930.3)
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: RRG <rrg@irtf.org>, Robin Whittle <rw@firstpr.com.au>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

> With respect to security in LHIP by using hash-chains, we consider  
> them for LISP, but requires 3 to 4 packet exchanges, so a non-starter.

I don't think so, but I'm no longer an expert there.  (I used to know  
crypto protocols around 1998-2002, but I no longer can claim so.)  For  
unprotected opportunistic case, I think you can simply send your hash  
anchors in the opening packet.

But then association initiation is a very subtle business with lots of  
DoS and other security pitfalls.   You have to make a balance between  
resource exhausting DoS protection and the number of roundtrips.

--Pekka

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan  8 04:46:19 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9A2533A6875;
	Thu,  8 Jan 2009 04:46:19 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D8B4A3A6875
	for <rrg@core3.amsl.com>; Thu,  8 Jan 2009 04:46:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.528
X-Spam-Level: 
X-Spam-Status: No, score=-3.528 tagged_above=-999 required=5 tests=[AWL=0.071, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id wWW9NLzf+FuT for <rrg@core3.amsl.com>;
	Thu,  8 Jan 2009 04:46:18 -0800 (PST)
Received: from hermes.mail.tigertech.net (hermes.mail.tigertech.net
	[64.62.209.72]) by core3.amsl.com (Postfix) with ESMTP id 01CD23A6781
	for <rrg@irtf.org>; Thu,  8 Jan 2009 04:46:17 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by hermes.tigertech.net (Postfix) with ESMTP id 91A024301B7
	for <rrg@irtf.org>; Thu,  8 Jan 2009 04:46:03 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at hermes.tigertech.net
Received: from [10.10.10.100] (pool-71-161-51-162.clppva.btas.verizon.net
	[71.161.51.162])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by hermes.tigertech.net (Postfix) with ESMTP id 066A2430180
	for <rrg@irtf.org>; Thu,  8 Jan 2009 04:46:02 -0800 (PST)
Message-ID: <4965F585.1050707@joelhalpern.com>
Date: Thu, 08 Jan 2009 07:45:57 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: RRG <rrg@irtf.org>
References: <495F0BAA.2040303@firstpr.com.au>	<49611E83.8050301@gmail.com><4961CFD3.2050304@firstpr.com.au><D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com>	<20EEF623-B503-4994-B099-64715E567B2D@cisco.com>	<474EEBD229DF754FB83D256004D021080AD5E539@XCH-NW-6V1.nw.nos.boeing.com>	<E294A8E4-57E3-48D3-BE17-B0EF2BD46DA4@cisco.com>	<1E8EC4E2-2365-4826-BC5C-1ADCB97C0E06@nomadiclab.com>
	<256FCF06-2A53-4E8D-8B1A-8BBC336F03D2@cisco.com>
In-Reply-To: <256FCF06-2A53-4E8D-8B1A-8BBC336F03D2@cisco.com>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

While there is room to discuss a lot of the other aspects, I at least 
consider the ability to migrate to a host based solution, which would 
easily support multi-interface hosts and site topology changes while 
preserving identity, to be a benefit.

Yours,
Joel

Dino Farinacci wrote:
> I'm not seeing any compelling benefit here Pekka. Just that HIP is 
> different and the stuff it does have that LISP currently doesn't is too 
> heavy-weight. This is just my opinion and a judgement.
> 
> Dino
> 
> On Jan 7, 2009, at 3:55 AM, Pekka Nikander wrote:
> 
>> Eric wrote:
>>>> By combining a true locator-identifier split (i.e., HIP) with a
>>>> map-and-encaps (e.g., LISP) one gets the combined benefits of both
>>>> approaches. Those benefits are
>>
>> Dino replied:
>>>
>>> But you add another layer of addressing that is probably more than 
>>> the user wants. It could get this bad:
>>>
>>> HIT -> EID -> private-RLOC -> public-RLOC    when behind a NAT
>>>
>>> or
>>>
>>> HIT -> private-EID -> public-EID -> RLOC     when behind a NAT
>>
>> I don't think those mappings are right.
>>
>> If there is a NAT between the xTR/HIP-proxy and the "new" internet, 
>> the mapping would be:
>>
>> EID -> (HIT) -> private-RLOC -> public-RLOC
>>
>> where the HIT would be invisible everywhere but inside the HIP proxies 
>> and within the signalling protocol between the HIP proxies.
>>
>> If there is a NAT between the legacy host and the xTR/HIP-proxy, the 
>> mapping would be:
>>
>> private-EID -> public-EID -> (HIT) -> RLOC
>>
>> where again the HIT would be invisible, as explained above.
>>
>>> 2-levels of mapping is plenty, adding 2 more probably is a 
>>> non-starter. Remember folks, we have to incrementally deploy this 
>>> with minimal cost, see Yakov's post early today, he makes good points.
>>
>> I don't see how replacing the xTR internal functionality with the 
>> HIP-proxy functionality would add much cost.  It would change the 
>> protocol between the xTRs, yes.  HIP as a protocol is probably more 
>> complex than the present xTR-xTR protocol, but it is well tested, been 
>> in operational use at Boeing for a few years, as has three open source 
>> implementations.
>>
>> There is an extra mapping, i.e. replacing the EID->RLOC mapping with a 
>> EID->(HIT)->RLOC mapping.  But that mapping is internal to the proxies 
>> and the signalling protocol, and not visible outside.  In the simplest 
>> case the HITs would be ephemeral and opportunistic, requiring no 
>> configuration or storage anywhere.  (The benefit from them is in terms 
>> of security and mobility, especially in more complex scenarios than 
>> the simplest case.)
>>
>> --Pekka
>>
> 
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> https://www.irtf.org/mailman/listinfo/rrg
> 
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan  8 08:26:18 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A34F13A6AEB;
	Thu,  8 Jan 2009 08:26:18 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A42B33A682C
	for <rrg@core3.amsl.com>; Thu,  8 Jan 2009 08:26:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.801
X-Spam-Level: 
X-Spam-Status: No, score=-4.801 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Y6Sgud3UNpva for <rrg@core3.amsl.com>;
	Thu,  8 Jan 2009 08:26:16 -0800 (PST)
Received: from mta-2.ms.rz.rwth-aachen.de (mta-2.ms.rz.RWTH-Aachen.DE
	[134.130.7.73]) by core3.amsl.com (Postfix) with ESMTP id 362D33A6AEB
	for <rrg@irtf.org>; Thu,  8 Jan 2009 08:26:16 -0800 (PST)
MIME-version: 1.0
Received: from ironport-out-1.rz.rwth-aachen.de ([134.130.5.40])
	by mta-2.ms.rz.RWTH-Aachen.de
	(Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008))
	with ESMTP id <0KD500ASYUZC0650@mta-2.ms.rz.RWTH-Aachen.de> for
	rrg@irtf.org; Thu, 08 Jan 2009 17:26:00 +0100 (CET)
X-IronPort-AV: E=Sophos;i="4.37,235,1231110000";   d="scan'208";a="95903064"
Received: from zelos.rz.rwth-aachen.de (HELO relay-auth.rwth-aachen.de)
	([134.130.3.23]) by ironport-in-1.rz.rwth-aachen.de with ESMTP; Thu,
	08 Jan 2009 17:26:00 +0100
Received: from umic-137-226-154-185.nn.RWTH-Aachen.DE
	(umic-137-226-154-185.nn.RWTH-Aachen.DE [137.226.154.185] (may be
	forged))
	(authenticated bits=0)	by relay-auth.rwth-aachen.de (8.13.8/8.13.1/1)
	with ESMTP id n08GPUfE032546
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu,
	08 Jan 2009 17:26:00 +0100
Message-id: <58A1DB9A-289C-4DA2-9F43-5D4EDE615BFE@cs.rwth-aachen.de>
From: Tobias Heer <heer@cs.rwth-aachen.de>
To: RRG <rrg@irtf.org>
In-reply-to: <0FFCF0A4-82C1-43AD-BA67-7F62ED94AE74@nomadiclab.com>
Date: Thu, 08 Jan 2009 17:25:29 +0100
References: <495F0BAA.2040303@firstpr.com.au> <49611E83.8050301@gmail.com>
	<4961CFD3.2050304@firstpr.com.au>
	<D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com>
	<20EEF623-B503-4994-B099-64715E567B2D@cisco.com>
	<474EEBD229DF754FB83D256004D021080AD5E539@XCH-NW-6V1.nw.nos.boeing.com>
	<39C363776A4E8C4A94691D2BD9D1C9A105623AC3@XCH-NW-7V2.nw.nos.boeing.com>
	<4FF36C8D-761D-4D45-BB99-A5E72B9E33C9@cisco.com>
	<14F8EAC5-AB88-45A1-A58D-AF270F0C7A90@nomadiclab.com>
	<97BAE464-611E-419A-A519-B51BEA76F9E0@cisco.com>
	<0FFCF0A4-82C1-43AD-BA67-7F62ED94AE74@nomadiclab.com>
X-Mailer: Apple Mail (2.930.3)
Cc: Robin Whittle <rw@firstpr.com.au>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org


Am 08.01.2009 um 11:48 schrieb Pekka Nikander:

>> With respect to security in LHIP by using hash-chains, we consider  
>> them for LISP, but requires 3 to 4 packet exchanges, so a non- 
>> starter.
>
> I don't think so, but I'm no longer an expert there.  (I used to  
> know crypto protocols around 1998-2002, but I no longer can claim  
> so.)  For unprotected opportunistic case, I think you can simply  
> send your hash anchors in the opening packet.
>
Regarding LHIP and authentication delay: The question is if this is  
about the payload channel (1), the signaling (2), or the initial  
handshake (as done by HIP) (3).

1. LHIP does not protect payload. Hence, there is no added security as  
well as no penalty in terms of additional packets and delay (in  
comparison to plain IP).

2. For signaling messages, LHIP uses delayed secret disclosure and  
requires three packets to be sent. Signaling events are quite rare for  
HIP.

3. Regarding the initial handshake: If one doesn't care about  
compatibility/interoperability between LHIP and HIP hosts, one could  
probably reduce the number of required handshake packets. LHIP uses  
the 4-way handshake for being as close to HIP as possible. When moving  
away from HIP one could indeed just send the anchors in the first data  
packet and still have hash-chain-signature protected signaling later  
but that is not what LHIP does right now.

Tobias

>
>
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> https://www.irtf.org/mailman/listinfo/rrg




--  

Dipl.-Inform. Tobias Heer, Ph.D. Student
Distributed Systems Group
RWTH Aachen University, Germany
tel: +49 241 80 207 76
web: http://ds.cs.rwth-aachen.de/members/heer







_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan  8 11:05:21 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F23193A6A68;
	Thu,  8 Jan 2009 11:05:20 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 871843A6A68
	for <rrg@core3.amsl.com>; Thu,  8 Jan 2009 11:05:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Level: 
X-Spam-Status: No, score=-6.454 tagged_above=-999 required=5 tests=[AWL=0.145, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id hrl5TPchc-3T for <rrg@core3.amsl.com>;
	Thu,  8 Jan 2009 11:05:19 -0800 (PST)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com
	[130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id AC55A3A6A4A
	for <rrg@irtf.org>; Thu,  8 Jan 2009 11:05:19 -0800 (PST)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6])
	by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id n08J4pRq015357
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);
	Thu, 8 Jan 2009 11:04:54 -0800 (PST)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	n08J4ptu010208; Thu, 8 Jan 2009 13:04:51 -0600 (CST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	n08J4ki1010047; Thu, 8 Jan 2009 13:04:51 -0600 (CST)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 8 Jan 2009 11:04:50 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 8 Jan 2009 11:04:50 -0800
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A10566DF39@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <C83DB85A-CE29-4288-87F8-07447C2DF862@nomadiclab.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] Rejecting all but Strategy A
Thread-Index: AclxfggIhoouQv0mRHy8GaYLfsgp2QAQ6XKQ
References: <495F0BAA.2040303@firstpr.com.au><49611E83.8050301@gmail.com><4961CFD3.2050304@firstpr.com.au><D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com><20EEF623-B503-4994-B099-64715E567B2D@cisco.com><474EEBD229DF754FB83D256004D021080AD5E539@XCH-NW-6V1.nw.nos.boeing.com><39C363776A4E8C4A94691D2BD9D1C9A105623AC3@XCH-NW-7V2.nw.nos.boeing.com>
	<96CDEE57-28F3-416C-8AAD-D3F7330B3C5A@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D07B0BC42@XCH-NW-5V1.nw.nos.boeing.com>
	<39C363776A4E8C4A94691D2BD9D1C9A10566DB53@XCH-NW-7V2.nw.nos.boeing.com>
	<C83DB85A-CE29-4288-87F8-07447C2DF862@nomadiclab.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Pekka Nikander" <pekka.nikander@nomadiclab.com>
X-OriginalArrivalTime: 08 Jan 2009 19:04:50.0639 (UTC)
	FILETIME=[FB5B35F0:01C971C3]
Cc: RRG <rrg@irtf.org>, Robin Whittle <rw@firstpr.com.au>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Pekka,

>-----Original Message-----
>From: Pekka Nikander [mailto:pekka.nikander@nomadiclab.com]
>Sent: Thursday, January 08, 2009 2:44 AM
>To: Templin, Fred L
>Cc: Henderson, Thomas R; RRG; Robin Whittle
>Subject: Re: [rrg] Rejecting all but Strategy A
>
>> Regarding HIP + map/encaps, maybe it is obvious to everyone
>> else already but I think what that gives you is an endpoint
>> identity (the HIT), an inner routing locator (iRLOC), and an
>> outer RLOC (oRLOC). Up to now, LISP (and perhaps others) have
>> been using the term "EID" to refer to what I mean by "iRLOC",
>> and the term "RLOC" to refer to what I mean by "oRLOC".
>
>That is my basic model as well.  Further, as Brian observed, that can
>be applied recursively.

Yes. One small but important distinction though is that recursion
is not meaning to say that there would be recursive encapsulations
(i.e., IP0-in-IP1-in-IP2-in ... in-IPN); else we would eat ourselves
out of MTU in a hurry.

Rather, we can talk about recursive RE-encapsulations. So, the
initial encapsulation would be: HIT-in-iRLOC-in-oRLOC0. The packet
would be forwarded within the scope within which oRLOC0 is routable,
then decapsulated and re-encapsulated as HIT-in-iRLOC-in-oRLOC1.
The packet is then forwarded within the oRLOC1 scope, then
re-encaps'd as HIT-in-iRLOC-in-oRLOC2, etc. etc.

It is exactly analogous to the way the L2 destination is changed
on each IP forwarding hop without the L3 destination address
changing. The only difference is that the outer IP protocol
is seen as L2 by the inner IP protocol. That is one of the
benefits of viewing the routing region in which oRLOCs are
valid as an NBMA link over which packets of the inner IP
protocol are forwarded, but there is much more to it than
just this.

Thanks - Fred
fred.l.templin@boeing.com   

>But then there are a few variations.
>
>1. In the case of pure host-based HIP, there is no iRLOC but only the
>HIT:
>
>    HIT -> oRLOC.
>
>2. In the case of host-based HIP and HIP MR, the mapping is HIT ->
>iRLOC -> oRLOC, which can be applied recursively leading to:
>
>    HIT -> LOC0 -> LOCi -> LOCn.
>
>3a. In the case of legacy hosts and HIP proxy, for IPv6 you *can* make
>iRLOC == HIT (which is what we did in the first HIP proxy work,
>described in Patrik's thesis):
>
>    iRLOC == HIT -> oRLOC
>
>3b. Alternatively, you can make HITs and iRLOCs separate, as you need
>for IPv4 anyway:
>
>    iRLOC <-> HIT -> oRLOC
>
>Generalising, we get two cases:
>
>a) host-based HIP generalised:  HIT -> LOC0 -> LOCi -> LOCn
>
>b) proxy HIP generalised:  iRLOC <-> HIT -> LOC0 -> LOCi -> LOCn
>
>In the latter case, the HIT can be "virtual" or "imaginary", if so
>desired.  (See my previous message.)
>
>> In this sense, "oRLOC" is routable within the scope of an
>> interdomain region, while "iRLOC" is routable only within and
>> end site (or edge network, or whatever you want to call it).
>> The HIP HIT is not routable within any scope so it is purely
>> an identifier and not a locator.
>
>That is the theory.  As I noted above, for IPv6 you can make HIT ==
>iRLOC if you want.  That is, the format allows that.
>
>--Pekka

_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan  8 11:11:44 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 74C1C3A6AAC;
	Thu,  8 Jan 2009 11:11:44 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4F8EA3A67B5
	for <rrg@core3.amsl.com>; Thu,  8 Jan 2009 11:11:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.459
X-Spam-Level: 
X-Spam-Status: No, score=-6.459 tagged_above=-999 required=5 tests=[AWL=0.140, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id MVrs3nioHeK4 for <rrg@core3.amsl.com>;
	Thu,  8 Jan 2009 11:11:42 -0800 (PST)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com
	[130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id 2D08128C0F6
	for <rrg@irtf.org>; Thu,  8 Jan 2009 11:11:42 -0800 (PST)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6])
	by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id n08JBSqN019831
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);
	Thu, 8 Jan 2009 11:11:28 -0800 (PST)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	n08JBR6c023541; Thu, 8 Jan 2009 13:11:27 -0600 (CST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	n08JBNNL023438; Thu, 8 Jan 2009 13:11:27 -0600 (CST)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 8 Jan 2009 11:11:20 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 8 Jan 2009 11:11:22 -0800
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A10566DF45@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <4965F585.1050707@joelhalpern.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] Rejecting all but Strategy A
Thread-Index: Aclxjxblw3/uduPlQ+e/j0tqPeYxzQANQz5Q
References: <495F0BAA.2040303@firstpr.com.au>	<49611E83.8050301@gmail.com><4961CFD3.2050304@firstpr.com.au><D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com>	<20EEF623-B503-4994-B099-64715E567B2D@cisco.com>	<474EEBD229DF754FB83D256004D021080AD5E539@XCH-NW-6V1.nw.nos.boeing.com>	<E294A8E4-57E3-48D3-BE17-B0EF2BD46DA4@cisco.com>	<1E8EC4E2-2365-4826-BC5C-1ADCB97C0E06@nomadiclab.com><256FCF06-2A53-4E8D-8B1A-8BBC336F03D2@cisco.com>
	<4965F585.1050707@joelhalpern.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, "RRG" <rrg@irtf.org>
X-OriginalArrivalTime: 08 Jan 2009 19:11:20.0766 (UTC)
	FILETIME=[E3E3DDE0:01C971C4]
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Joel,

I am seeing HIP proxy as having value both as a near-term
connectivity capability for legacy hosts and as a longer
term transition mechanism that encourages more and more
end hosts to deploy a host-based solution. However, I
see this as complementary to the network-based solution
rather than a replacement for the network-based solution.

IMHO, the network based-solution provides the substrate
on which the end-to-end solution builds.

Fred
fred.l.templin@boeing.com 

>-----Original Message-----
>From: Joel M. Halpern [mailto:jmh@joelhalpern.com]
>Sent: Thursday, January 08, 2009 4:46 AM
>To: RRG
>Subject: Re: [rrg] Rejecting all but Strategy A
>
>While there is room to discuss a lot of the other aspects, I at least
>consider the ability to migrate to a host based solution, which would
>easily support multi-interface hosts and site topology changes while
>preserving identity, to be a benefit.
>
>Yours,
>Joel
>
>Dino Farinacci wrote:
>> I'm not seeing any compelling benefit here Pekka. Just that HIP is
>> different and the stuff it does have that LISP currently doesn't is
too
>> heavy-weight. This is just my opinion and a judgement.
>>
>> Dino
>>
>> On Jan 7, 2009, at 3:55 AM, Pekka Nikander wrote:
>>
>>> Eric wrote:
>>>>> By combining a true locator-identifier split (i.e., HIP) with a
>>>>> map-and-encaps (e.g., LISP) one gets the combined benefits of both
>>>>> approaches. Those benefits are
>>>
>>> Dino replied:
>>>>
>>>> But you add another layer of addressing that is probably more than
>>>> the user wants. It could get this bad:
>>>>
>>>> HIT -> EID -> private-RLOC -> public-RLOC    when behind a NAT
>>>>
>>>> or
>>>>
>>>> HIT -> private-EID -> public-EID -> RLOC     when behind a NAT
>>>
>>> I don't think those mappings are right.
>>>
>>> If there is a NAT between the xTR/HIP-proxy and the "new" internet,
>>> the mapping would be:
>>>
>>> EID -> (HIT) -> private-RLOC -> public-RLOC
>>>
>>> where the HIT would be invisible everywhere but inside the HIP
proxies
>>> and within the signalling protocol between the HIP proxies.
>>>
>>> If there is a NAT between the legacy host and the xTR/HIP-proxy, the
>>> mapping would be:
>>>
>>> private-EID -> public-EID -> (HIT) -> RLOC
>>>
>>> where again the HIT would be invisible, as explained above.
>>>
>>>> 2-levels of mapping is plenty, adding 2 more probably is a
>>>> non-starter. Remember folks, we have to incrementally deploy this
>>>> with minimal cost, see Yakov's post early today, he makes good
points.
>>>
>>> I don't see how replacing the xTR internal functionality with the
>>> HIP-proxy functionality would add much cost.  It would change the
>>> protocol between the xTRs, yes.  HIP as a protocol is probably more
>>> complex than the present xTR-xTR protocol, but it is well tested,
been
>>> in operational use at Boeing for a few years, as has three open
source
>>> implementations.
>>>
>>> There is an extra mapping, i.e. replacing the EID->RLOC mapping with
a
>>> EID->(HIT)->RLOC mapping.  But that mapping is internal to the
proxies
>>> and the signalling protocol, and not visible outside.  In the
simplest
>>> case the HITs would be ephemeral and opportunistic, requiring no
>>> configuration or storage anywhere.  (The benefit from them is in
terms
>>> of security and mobility, especially in more complex scenarios than
>>> the simplest case.)
>>>
>>> --Pekka
>>>
>>
>> _______________________________________________
>> rrg mailing list
>> rrg@irtf.org
>> https://www.irtf.org/mailman/listinfo/rrg
>>
>_______________________________________________
>rrg mailing list
>rrg@irtf.org
>https://www.irtf.org/mailman/listinfo/rrg
_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan  8 15:53:53 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9BC0B3A68F9;
	Thu,  8 Jan 2009 15:53:53 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4C4033A68B2
	for <rrg@core3.amsl.com>; Thu,  8 Jan 2009 15:53:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.555
X-Spam-Level: 
X-Spam-Status: No, score=-1.555 tagged_above=-999 required=5 tests=[AWL=0.340, 
	BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id aMO4g2p0MLCB for <rrg@core3.amsl.com>;
	Thu,  8 Jan 2009 15:53:51 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123])
	by core3.amsl.com (Postfix) with ESMTP id DA3AB3A68DB
	for <rrg@irtf.org>; Thu,  8 Jan 2009 15:53:50 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6])
	by gair.firstpr.com.au (Postfix) with ESMTP id E8009175A1F;
	Fri,  9 Jan 2009 10:53:34 +1100 (EST)
Message-ID: <49669202.9090705@firstpr.com.au>
Date: Fri, 09 Jan 2009 10:53:38 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: RRG <rrg@irtf.org>
References: <49654CC6.80802@firstpr.com.au>
In-Reply-To: <49654CC6.80802@firstpr.com.au>
Subject: Re: [rrg] HIP, Hip-Proxy, LHIP etc. (Strategy B)
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

I am still hoping to draw discussion of HIP etc. out of the
"Rejecting all but Strategy A" thread into a thread with a relevant
subject line.  Here is a list of recent and older messages concerning
Lightweight HIP (LHIP):

  http://tools.ietf.org/html/draft-heer-hip-lhip-00
  2007-08-05 Tobias Heer

  http://www.ietf.org/proceedings/08mar/slides/HIPRG-4.pdf
  2008-03    Tobias Heer

  Early reference in 2003-12, by Pekka Nikander:
  http://tools.ietf.org/html/draft-nikander-multi6-hip-00

In the last few days:

  http://www.irtf.org/pipermail/rrg/2009-January/000742.html      PN
  http://www.irtf.org/pipermail/rrg/2009-January/000755.html      DF
  http://www.irtf.org/pipermail/rrg/2009-January/000762.html      PN
  http://www.irtf.org/pipermail/rrg/2009-January/000764.html      TH

Earlier:

  http://www.ietf.org/mail-archive/web/ram/current/msg00298.html  PN
  2007-01-03

  http://www.ietf.org/mail-archive/web/ram/current/msg00573.html  PN
  2007-02-15

  http://psg.com/lists/rrg/2007/msg00414.html      2007-10-09     PN
  http://psg.com/lists/rrg/2008/msg00806.html      2008-03-16     PN
  http://www.irtf.org/pipermail/rrg/2008-November/000338.html     PN

   - Robin


_______________________________________________
rrg mailing list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Fri Jan  9 00:31:30 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F1C903A6936;
	Fri,  9 Jan 2009 00:31:29 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9BC7C3A6936
	for <rrg@core3.amsl.com>; Fri,  9 Jan 2009 00:31:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id AZb1pCxWWS5l for <rrg@core3.amsl.com>;
	Fri,  9 Jan 2009 00:31:28 -0800 (PST)
Received: from n2.nomadiclab.com (n2.nomadiclab.com
	[IPv6:2001:14b8:400:101::2])
	by core3.amsl.com (Postfix) with ESMTP id 4662E3A692D
	for <rrg@irtf.org>; Fri,  9 Jan 2009 00:31:28 -0800 (PST)
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 88BFD1EF126;
	Fri,  9 Jan 2009 10:31:13 +0200 (EET)
Received: from [127.0.0.1] (localhost [IPv6:::1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 171EB1EF125;
	Fri,  9 Jan 2009 10:31:13 +0200 (EET)
Message-Id: <695CF996-623A-40FA-B349-0162A72374D7@nomadiclab.com>
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A10566DF39@XCH-NW-7V2.nw.nos.boeing.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Fri, 9 Jan 2009 10:31:12 +0200
References: <495F0BAA.2040303@firstpr.com.au><49611E83.8050301@gmail.com><4961CFD3.2050304@firstpr.com.au><D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com><20EEF623-B503-4994-B099-64715E567B2D@cisco.com><474EEBD229DF754FB83D256004D021080AD5E539@XCH-NW-6V1.nw.nos.boeing.com><39C363776A4E8C4A94691D2BD9D1C9A105623AC3@XCH-NW-7V2.nw.nos.boeing.com>
	<96CDEE57-28F3-416C-8AAD-D3F7330B3C5A@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D07B0BC42@XCH-NW-5V1.nw.nos.boeing.com>
	<39C363776A4E8C4A94691D2BD9D1C9A10566DB53@XCH-NW-7V2.nw.nos.boeing.com>
	<C83DB85A-CE29-4288-87F8-07447C2DF862@nomadiclab.com>
	<39C363776A4E8C4A94691D2BD9D1C9A10566DF39@XCH-NW-7V2.nw.nos.boeing.com>
X-Mailer: Apple Mail (2.930.3)
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: RRG <rrg@irtf.org>
Subject: [rrg] Recursive re-encapsulations
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

>>> Regarding HIP + map/encaps, maybe it is obvious to everyone else  
>>> already but I think what that gives you is an endpoint identity  
>>> (the HIT), an inner routing locator (iRLOC), and an outer RLOC  
>>> (oRLOC). Up to now, LISP (and perhaps others) have been using the  
>>> term "EID" to refer to what I mean by "iRLOC", and the term "RLOC"  
>>> to refer to what I mean by "oRLOC".
>>
>> That is my basic model as well.  Further, as Brian observed, that  
>> can be applied recursively.
>
> Yes. One small but important distinction though is that recursion is  
> not meaning to say that there would be recursive encapsulations  
> (i.e., IP0-in-IP1-in-IP2-in ... in-IPN); else we would eat ourselves  
> out of MTU in a hurry.

I agree.

> Rather, we can talk about recursive RE-encapsulations. So, the  
> initial encapsulation would be: HIT-in-iRLOC-in-oRLOC0. The packet  
> would be forwarded within the scope within which oRLOC0 is routable,
> then decapsulated and re-encapsulated as HIT-in-iRLOC-in-oRLOC1.

Well, I would expect 1-to-1 mapping between HITs and iRLOCs, allowing  
one to use just one encapsulation or even almost-null encapsulation.   
That is, e.g. iRLOC-in-oRLOCi, HIT-in-oRLOCi, or TAG-in-oRLOCi where  
TAG is whatever minimal encapsulation/tag is needed for demuxing at  
oRLOCi.

> It is exactly analogous to the way the L2 destination is changed on  
> each IP forwarding hop without the L3 destination address changing.  
> The only difference is that the outer IP protocol is seen as L2 by  
> the inner IP protocol.

I think that has been discussed more extensively in the following  
papers and drafts.  But I didn't check, I may be wrong.

Jukka Ylitalo, Patrik Salmela, and Hannes Tschofenig, "SPINAT:  
Integrating IPsec into Overlay Routing", in Proc. of the First  
International Conference on Security and Privacy for Emerging Areas in  
Communication Networks (SecureComm'05), pp. 315-326, Athens, Greece,  
September 5-9, 2005, ISBN 0-7695-2369-2

http://www.ietf.org/internet-drafts/draft-melen-spinat-01.txt

A. Eriksson and B. Ohlman, "Dynamic Internetworking Based on Late  
Locator Construction," IEEE Global Internet Symposium, 2007.

--Pekka

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Fri Jan  9 08:16:59 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2F4B73A6902;
	Fri,  9 Jan 2009 08:16:59 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4303A3A68F2
	for <rrg@core3.amsl.com>; Fri,  9 Jan 2009 08:16:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.163
X-Spam-Level: 
X-Spam-Status: No, score=-6.163 tagged_above=-999 required=5
	tests=[AWL=-0.164, BAYES_00=-2.599, J_CHICKENPOX_34=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id M3UEzxbDaOgt for <rrg@core3.amsl.com>;
	Fri,  9 Jan 2009 08:16:57 -0800 (PST)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com
	[130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id 3245D3A6902
	for <rrg@irtf.org>; Fri,  9 Jan 2009 08:16:57 -0800 (PST)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231])
	by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id n09GGVM4023174
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 9 Jan 2009 08:16:35 -0800 (PST)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	n09GGV1p018993; Fri, 9 Jan 2009 08:16:31 -0800 (PST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	n09GGVrO018988; Fri, 9 Jan 2009 08:16:31 -0800 (PST)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 9 Jan 2009 08:16:31 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 9 Jan 2009 08:16:29 -0800
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A10566E3D9@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <695CF996-623A-40FA-B349-0162A72374D7@nomadiclab.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Recursive re-encapsulations
Thread-Index: AclyNKQMdWy7sA5ERuWVBVBpyn9VFgAPHaFA
References: <495F0BAA.2040303@firstpr.com.au><49611E83.8050301@gmail.com><4961CFD3.2050304@firstpr.com.au><D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com><20EEF623-B503-4994-B099-64715E567B2D@cisco.com><474EEBD229DF754FB83D256004D021080AD5E539@XCH-NW-6V1.nw.nos.boeing.com><39C363776A4E8C4A94691D2BD9D1C9A105623AC3@XCH-NW-7V2.nw.nos.boeing.com>
	<96CDEE57-28F3-416C-8AAD-D3F7330B3C5A@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D07B0BC42@XCH-NW-5V1.nw.nos.boeing.com>
	<39C363776A4E8C4A94691D2BD9D1C9A10566DB53@XCH-NW-7V2.nw.nos.boeing.com>
	<C83DB85A-CE29-4288-87F8-07447C2DF862@nomadiclab.com>
	<39C363776A4E8C4A94691D2BD9D1C9A10566DF39@XCH-NW-7V2.nw.nos.boeing.com>
	<695CF996-623A-40FA-B349-0162A72374D7@nomadiclab.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Pekka Nikander" <pekka.nikander@nomadiclab.com>
X-OriginalArrivalTime: 09 Jan 2009 16:16:31.0047 (UTC)
	FILETIME=[A1F18570:01C97275]
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] Recursive re-encapsulations
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Pekka,

>-----Original Message-----
>From: Pekka Nikander [mailto:pekka.nikander@nomadiclab.com]
>Sent: Friday, January 09, 2009 12:31 AM
>To: Templin, Fred L
>Cc: RRG
>Subject: Recursive re-encapsulations
>
>>>> Regarding HIP + map/encaps, maybe it is obvious to everyone else
>>>> already but I think what that gives you is an endpoint identity
>>>> (the HIT), an inner routing locator (iRLOC), and an outer RLOC
>>>> (oRLOC). Up to now, LISP (and perhaps others) have been using the
>>>> term "EID" to refer to what I mean by "iRLOC", and the term "RLOC"
>>>> to refer to what I mean by "oRLOC".
>>>
>>> That is my basic model as well.  Further, as Brian observed, that
>>> can be applied recursively.
>>
>> Yes. One small but important distinction though is that recursion is
>> not meaning to say that there would be recursive encapsulations
>> (i.e., IP0-in-IP1-in-IP2-in ... in-IPN); else we would eat ourselves
>> out of MTU in a hurry.
>
>I agree.
>
>> Rather, we can talk about recursive RE-encapsulations. So, the
>> initial encapsulation would be: HIT-in-iRLOC-in-oRLOC0. The packet
>> would be forwarded within the scope within which oRLOC0 is routable,
>> then decapsulated and re-encapsulated as HIT-in-iRLOC-in-oRLOC1.
>
>Well, I would expect 1-to-1 mapping between HITs and iRLOCs, allowing
>one to use just one encapsulation or even almost-null encapsulation.
>That is, e.g. iRLOC-in-oRLOCi, HIT-in-oRLOCi, or TAG-in-oRLOCi where
>TAG is whatever minimal encapsulation/tag is needed for demuxing at
>oRLOCi.

I may not have made myself clear. I am talking about HIP in
conjunction with the RANGER/VET/SEAL model, and specifically
about the over-the-wire encapsulation format.

iRLOC refers to the IP addresses HIP sees, while oRLOC refers
to the outer encapsulation applied by RANGER/VET/SEAL. Both
iRLOCs and oRLOCs name interfaces (not end systems) hence they
are routable within a certain limited scope. My understanding
is that HITs are true end system identifiers (EIDs) and not
routable within any scope.

My assumption is that HIP can deal with multihomed hosts (i.e.,
there may be one HIT to many iRLOCs), but let's say there is
just one interface for now. So, when a HIP-aware transport
inserts a HIT (and then does BEET-mode encapsulation, I guess)
the packet goes out as:

  +--------------+
  |     data     |
  +--------------+
  |   transport  |
  +--------------+
  |      HIT     |
  +--------------+
  |   IPsec/ESP  |
  +--------------+
  | Inner IP hdr |
  |   src=iSRC   |
  |   dst=iDST   |
  +--------------+

Then, somewhere in the path (it may or may not be on the same
platform that sourced the packet), an ITR performs an iRLOC to
oRLOC mapping and appends an outer IP header:

  +--------------+
  |     data     |
  +--------------+
  |   transport  |
  +--------------+
  |      HIT     |
  +--------------+
  |   IPsec/ESP  |
  +--------------+
  | Inner IP hdr |
  |   src=iSRC   |
  |   dst=iDST   |
  +--------------+
  | Outer IP hdr |
  | src=oSRC(0)  |
  | dst=oDST(0)  |
  +--------------+

The packet is then routed according to the outer IP protocol
within the scope within which oSRC(0) and oDST(0) are valid,
then hits an ETR/ITR that decapsulates and re-encapsulates as:

  +--------------+
  |     data     |
  +--------------+
  |   transport  |
  +--------------+
  |      HIT     |
  +--------------+
  |   IPsec/ESP  |
  +--------------+
  | Inner IP hdr |
  |   src=iSRC   |
  |   dst=iDST   |
  +--------------+
  | Outer IP hdr |
  | src=oSRC(1)  |
  | dst=oDST(1)  |
  +--------------+

and the chain can continue recursively with an indefinite
number of ITR(i)->ETR(i), ITR(i+1)->ETR(i+1), etc. transitions,
with the decapsulation and re-encapsulation occurring at each
transition. The iRLOCs in the inner IP header never change, but
the inner IP TTL/Hop limit is decremented upon each ETR->ITR
transition. This is what I mean by HIP being used in conjunction
with map/encaps. But, HIP simply sees map/encaps as an ordinary
interface over which packets can be sent.

Does this clarify?

Fred
fred.l.templin@boeing.com 
  
>
>> It is exactly analogous to the way the L2 destination is changed on
>> each IP forwarding hop without the L3 destination address changing.
>> The only difference is that the outer IP protocol is seen as L2 by
>> the inner IP protocol.
>
>I think that has been discussed more extensively in the following
>papers and drafts.  But I didn't check, I may be wrong.
>
>Jukka Ylitalo, Patrik Salmela, and Hannes Tschofenig, "SPINAT:
>Integrating IPsec into Overlay Routing", in Proc. of the First
>International Conference on Security and Privacy for Emerging Areas in
>Communication Networks (SecureComm'05), pp. 315-326, Athens, Greece,
>September 5-9, 2005, ISBN 0-7695-2369-2
>
>http://www.ietf.org/internet-drafts/draft-melen-spinat-01.txt
>
>A. Eriksson and B. Ohlman, "Dynamic Internetworking Based on Late
>Locator Construction," IEEE Global Internet Symposium, 2007.
>
>--Pekka

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Fri Jan  9 08:27:44 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B90933A6B2A;
	Fri,  9 Jan 2009 08:27:44 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6685E3A6B2A
	for <rrg@core3.amsl.com>; Fri,  9 Jan 2009 08:27:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.099
X-Spam-Level: 
X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[AWL=1.500, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id z3qk5OlMIKHg for <rrg@core3.amsl.com>;
	Fri,  9 Jan 2009 08:27:42 -0800 (PST)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net
	[217.115.75.233])
	by core3.amsl.com (Postfix) with ESMTP id 57A9B3A699E
	for <rrg@irtf.org>; Fri,  9 Jan 2009 08:27:42 -0800 (PST)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56])
	by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id
	n09GRQqn027412
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <rrg@irtf.org>; Fri, 9 Jan 2009 17:27:26 +0100
Received: from demuexc024.nsn-intra.net (demuexc024.nsn-intra.net
	[10.159.32.11])
	by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP
	id n09GRQjp007694 for <rrg@irtf.org>; Fri, 9 Jan 2009 17:27:26 +0100
Received: from FIESEXC014.nsn-intra.net ([10.159.0.22]) by
	demuexc024.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 9 Jan 2009 17:27:25 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 9 Jan 2009 18:27:25 +0200
Message-ID: <2B5F3EA7272CFF47A66518E4FF3BE2350260512D@FIESEXC014.nsn-intra.net>
In-Reply-To: <002e01c97152$1c15fdb0$670c6f0a@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] Rejecting all but Strategy A
Thread-Index: AclxSSvo2f3ViwPjThC6Gb8x8ADmCwAB/PuwAElk4WA=
References: <49657F62.5010303@employees.org>
	<002e01c97152$1c15fdb0$670c6f0a@china.huawei.com>
From: "Flinck, Hannu (NSN - FI/Espoo)" <hannu.flinck@nsn.com>
To: "RRG" <rrg@irtf.org>
X-OriginalArrivalTime: 09 Jan 2009 16:27:25.0980 (UTC)
	FILETIME=[28505DC0:01C97277]
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org


 So HIT is routable IPv6 address to enable legacy to legacy
communication? Is that good?
 
 How about having a two faced DNS for upgraded nodes? HIT returned if
source is from EID space, AAAA if not?

- Hannu

>-----Original Message-----
>From: rrg-bounces@irtf.org [mailto:rrg-bounces@irtf.org] On 
>Behalf Of ext Xu Xiaohu
>Sent: Thursday, January 08, 2009 07:30
>To: 'Scott Brim'
>Cc: 'RRG'; 'Robin Whittle'
>Subject: Re: [rrg] Rejecting all but Strategy A
>
>
>> > When a legecy host A initiates a communication with a
>> HIP-enabled host
>> > B,  A could send a packet to a nearby proxy (like ITR's
>> role) by using
>> > B's HIT as locator.
>> 
>> Would you replace host B's A record with a HIT?  Or would 
>this require 
>> a modification to host A?  If you're going to modify A, why not just 
>> implement HIP?
>
>Replacing host B's AAAA record with a HIT is my thought. If a 
>legacy host got B's AAAA record from DNS, it will look that 
>record as a IPv6 address And the mapping between HIT and 
>locator (IP address) can be maintained in a seperate mapping 
>system, e.g. a hierarchical DHT system. 
> 
>Xiaohu
>
>
>_______________________________________________
>rrg mailing list
>rrg@irtf.org
>https://www.irtf.org/mailman/listinfo/rrg
>
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sat Jan 10 05:05:51 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 145A828C194;
	Sat, 10 Jan 2009 05:05:51 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C60C028C194
	for <rrg@core3.amsl.com>; Sat, 10 Jan 2009 05:05:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id mz72Q4F2qHin for <rrg@core3.amsl.com>;
	Sat, 10 Jan 2009 05:05:49 -0800 (PST)
Received: from n2.nomadiclab.com (n2.nomadiclab.com
	[IPv6:2001:14b8:400:101::2])
	by core3.amsl.com (Postfix) with ESMTP id BB02928C193
	for <rrg@irtf.org>; Sat, 10 Jan 2009 05:05:48 -0800 (PST)
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id ED4EF1EF126;
	Sat, 10 Jan 2009 15:05:31 +0200 (EET)
Received: from [127.0.0.1] (localhost [IPv6:::1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 738551EF125;
	Sat, 10 Jan 2009 15:05:31 +0200 (EET)
Message-Id: <BBEA3D1B-47DC-4003-B300-9F61A45F6775@nomadiclab.com>
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A10566E3D9@XCH-NW-7V2.nw.nos.boeing.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Sat, 10 Jan 2009 15:05:31 +0200
References: <495F0BAA.2040303@firstpr.com.au><49611E83.8050301@gmail.com><4961CFD3.2050304@firstpr.com.au><D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com><20EEF623-B503-4994-B099-64715E567B2D@cisco.com><474EEBD229DF754FB83D256004D021080AD5E539@XCH-NW-6V1.nw.nos.boeing.com><39C363776A4E8C4A94691D2BD9D1C9A105623AC3@XCH-NW-7V2.nw.nos.boeing.com>
	<96CDEE57-28F3-416C-8AAD-D3F7330B3C5A@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D07B0BC42@XCH-NW-5V1.nw.nos.boeing.com>
	<39C363776A4E8C4A94691D2BD9D1C9A10566DB53@XCH-NW-7V2.nw.nos.boeing.com>
	<C83DB85A-CE29-4288-87F8-07447C2DF862@nomadiclab.com>
	<39C363776A4E8C4A94691D2BD9D1C9A10566DF39@XCH-NW-7V2.nw.nos.boeing.com>
	<695CF996-623A-40FA-B349-0162A72374D7@nomadiclab.com>
	<39C363776A4E8C4A94691D2BD9D1C9A10566E3D9@XCH-NW-7V2.nw.nos.boeing.com>
X-Mailer: Apple Mail (2.930.3)
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] Recursive re-encapsulations
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

>>>>> Regarding HIP + map/encaps, maybe it is obvious to everyone else
>>>>> already but I think what that gives you is an endpoint identity
>>>>> (the HIT), an inner routing locator (iRLOC), and an outer RLOC
>>>>> (oRLOC). Up to now, LISP (and perhaps others) have been using the
>>>>> term "EID" to refer to what I mean by "iRLOC", and the term "RLOC"
>>>>> to refer to what I mean by "oRLOC".
>>>>
>>>> That is my basic model as well.  Further, as Brian observed, that
>>>> can be applied recursively.
>>>
>>> Yes. One small but important distinction though is that recursion is
>>> not meaning to say that there would be recursive encapsulations
>>> (i.e., IP0-in-IP1-in-IP2-in ... in-IPN); else we would eat ourselves
>>> out of MTU in a hurry.
>>
>> Well, I would expect 1-to-1 mapping between HITs and iRLOCs, allowing
>> one to use just one encapsulation or even almost-null encapsulation.
>> That is, e.g. iRLOC-in-oRLOCi, HIT-in-oRLOCi, or TAG-in-oRLOCi where
>> TAG is whatever minimal encapsulation/tag is needed for demuxing at
>> oRLOCi.
>
> I may not have made myself clear. I am talking about HIP in
> conjunction with the RANGER/VET/SEAL model, and specifically
> about the over-the-wire encapsulation format.

I suggest that we take this off-line, as there are many details.  If  
someone else is interested, feel free to drop a note.  It may be worth  
to wrap the details into a draft, perhaps.

Anyway, from my point of view, what you described in the message

http://www.ietf.org/mail-archive/web/rrg/current/msg04312.html

is the case of using vanilla HIP on a HIP-enabled host, landing on a  
network behind a lisp xTR or a similar device.  In that case you  
indeed get the packet structures you described.

However, if we aim for the kind of hybrid LISP-HIP-proxy design that  
I've been suggesting, I believe that the packet formats could be much  
simpler.

AFAICS, the crux will always be on how much demultiplexing / security  
verification state you need at the receiving end, at the unwrapping  
xTR.  If your trust model allows you to decapsulate without  
verification, you can live without such state and include the inner  
locators or identifiers into the packet.  However, if the trust model  
requires one to verify the inner locators or identifiers, then there  
must be the state at the receiving end, meaning that you get smaller  
overhead if you don't include the full inner header in the packet but  
just index to the state + any bits not directly stored in the state.

--Pekka

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sun Jan 11 02:55:43 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 14E993A68E1;
	Sun, 11 Jan 2009 02:55:43 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C997928C11B
	for <rrg@core3.amsl.com>; Sun, 11 Jan 2009 02:55:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.452
X-Spam-Level: 
X-Spam-Status: No, score=0.452 tagged_above=-999 required=5 tests=[AWL=-0.946, 
	BAYES_50=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id g8CeYh9grf+W for <rrg@core3.amsl.com>;
	Sun, 11 Jan 2009 02:55:40 -0800 (PST)
Received: from imo-d23.mx.aol.com (imo-d23.mx.aol.com [205.188.139.137])
	by core3.amsl.com (Postfix) with ESMTP id 7B6AB3A68E1
	for <rrg@irtf.org>; Sun, 11 Jan 2009 02:55:39 -0800 (PST)
Received: from HeinerHummel@aol.com
	by imo-d23.mx.aol.com  (mail_out_v39.1.) id n.cee.4d9f9208 (65099);
	Sun, 11 Jan 2009 05:55:16 -0500 (EST)
From: HeinerHummel@aol.com
Message-ID: <cee.4d9f9208.369b2a14@aol.com>
Date: Sun, 11 Jan 2009 05:55:16 EST
To: rw@firstpr.com.au, rrg@irtf.org
MIME-Version: 1.0
X-Mailer: 9.0 SE for Windows sub 5021
Subject: Re: [rrg] Critique of Compact Routing
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0549591607=="
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org


--===============0549591607==
Content-Type: multipart/alternative; boundary="-----------------------------1231671316"


-------------------------------1231671316
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

=20
I have realized that Dmitri Krioukov (I don't know him in person) has once =20
led a subgroup of this RRG.
Though I have already objected wrt TARA (which, by construction, enables =20
stretch-1), it might be interesting for all to know how the very big and pre=
cise =20
value stretch-15 had been determined and for which investigated  hierarchica=
l=20
routing architectures. If D.K.  still subscribes to this  RRG-mailinglist he=
=20
may explain his result, or maybe some aquainted  one can ask him and inform=20
the RRG-subscribers?
=20
Heiner
=20
=20
=20
=20
In einer eMail vom 29.12.2008 23:56:13 Westeurop=E4ische Normalzeit schreibt=
 =20
rw@firstpr.com.au:

In an  earlier message 000565 I mentioned a paper:

On Compact  Routing for the Internet
Dmitri Krioukov, kc claffy, Kevin  Fall, Arthur Brady
ACM SIGCOMM CCR, v.37, n.3, p.41-52,  2007

This is available at:

http://arxiv.org/abs/0708.2309

-  Robin
_______________________________________________
rrg mailing  list
rrg@irtf.org
https://www.irtf.org/mailman/listinfo/rrg





-------------------------------1231671316
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3DISO-8859-1">
<META content=3D"MSHTML 6.00.6000.16788" name=3DGENERATOR></HEAD>
<BODY id=3Drole_body style=3D"FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY:=20=
Arial"=20
bottomMargin=3D7 leftMargin=3D7 topMargin=3D7 rightMargin=3D7><FONT id=3Drol=
e_document=20
face=3DArial color=3D#000000 size=3D2>
<DIV>
<DIV>I have realized that Dmitri Krioukov (I don't know him in person) has o=
nce=20
led a subgroup of this RRG.</DIV>
<DIV>Though I have already objected wrt TARA (which, by construction, enable=
s=20
stretch-1), it might be interesting for all to know how the very big and pre=
cise=20
value stretch-15 had been determined and for&nbsp;which investigated=20
hierarchical routing architectures. If D.K.&nbsp; still subscribes to this=20
RRG-mailinglist he may explain&nbsp;his result, or maybe some aquainted=20
one&nbsp;can&nbsp;ask him and inform the RRG-subscribers?</DIV>
<DIV>&nbsp;</DIV>
<DIV>Heiner</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>In einer eMail vom 29.12.2008 23:56:13 Westeurop=E4ische Normalzeit sch=
reibt=20
rw@firstpr.com.au:</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid"><=
FONT=20
  style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000 size=
=3D2>In an=20
  earlier message 000565 I mentioned a paper:<BR><BR>&nbsp; &nbsp; On Compac=
t=20
  Routing for the Internet<BR>&nbsp; &nbsp; Dmitri Krioukov, kc claffy, Kevi=
n=20
  Fall, Arthur Brady<BR>&nbsp; &nbsp; ACM SIGCOMM CCR, v.37, n.3, p.41-52,=20
  2007<BR><BR>This is available at:<BR><BR>&nbsp; &nbsp;=20
  http://arxiv.org/abs/0708.2309<BR><BR>&nbsp; -=20
  Robin<BR>_______________________________________________<BR>rrg mailing=20
  list<BR>rrg@irtf.org<BR>https://www.irtf.org/mailman/listinfo/rrg<BR></FON=
T></BLOCKQUOTE></DIV>
<DIV></DIV>
<DIV>&nbsp;</DIV></FONT></BODY></HTML>

-------------------------------1231671316--

--===============0549591607==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

--===============0549591607==--


From rrg-bounces@irtf.org  Sun Jan 11 09:47:47 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 55EF128C1B1;
	Sun, 11 Jan 2009 09:47:47 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C9A4B28C1B1
	for <rrg@core3.amsl.com>; Sun, 11 Jan 2009 09:47:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.3
X-Spam-Level: 
X-Spam-Status: No, score=-5.3 tagged_above=-999 required=5 tests=[AWL=-0.190, 
	BAYES_05=-1.11, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 074ve7tJdsWQ for <rrg@core3.amsl.com>;
	Sun, 11 Jan 2009 09:47:44 -0800 (PST)
Received: from caida.org (rommie.caida.org [192.172.226.78])
	by core3.amsl.com (Postfix) with ESMTP id 44F103A6AC3
	for <rrg@irtf.org>; Sun, 11 Jan 2009 09:47:44 -0800 (PST)
Received: by caida.org (Postfix, from userid 2000)
	id ED1A0B925; Sun, 11 Jan 2009 09:47:27 -0800 (PST)
Date: Sun, 11 Jan 2009 09:47:27 -0800
From: k claffy <kc@caida.org>
To: HeinerHummel@aol.com
Message-ID: <20090111174727.GA78133@rommie.caida.org>
References: <cee.4d9f9208.369b2a14@aol.com>
Mime-Version: 1.0
Content-Disposition: inline
In-Reply-To: <cee.4d9f9208.369b2a14@aol.com>
User-Agent: Mutt/1.4.2.1i
Cc: rrg@irtf.org, rw@firstpr.com.au
Subject: Re: [rrg] Critique of Compact Routing
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org



Heiner,

have you read the appendix to dima's
'compact routing on Internet-like graphs'
http://www.ieee-infocom.org/2004/Papers/05_4.PDF 
and not found the answer to these two questions?

k



On Sun, Jan 11, 2009 at 05:55:16AM -0500, HeinerHummel@aol.com wrote:
   
  I have realized that Dmitri Krioukov (I don't know him in person) has once  
  led a subgroup of this RRG.
  Though I have already objected wrt TARA (which, by construction, enables  
  stretch-1), it might be interesting for all to know how the very big and precise  
  value stretch-15 had been determined and for which investigated  hierarchical 
  routing architectures. If D.K.  still subscribes to this  RRG-mailinglist he 
  may explain his result, or maybe some aquainted  one can ask him and inform 
  the RRG-subscribers?
   
  Heiner
   
   
   
   
  In einer eMail vom 29.12.2008 23:56:13 Westeurop?ische Normalzeit schreibt  
  rw@firstpr.com.au:
  
  In an  earlier message 000565 I mentioned a paper:
  
  On Compact  Routing for the Internet
  Dmitri Krioukov, kc claffy, Kevin  Fall, Arthur Brady
  ACM SIGCOMM CCR, v.37, n.3, p.41-52,  2007
  
  This is available at:
  
  http://arxiv.org/abs/0708.2309
  
  -  Robin
  _______________________________________________
  rrg mailing  list
  rrg@irtf.org
  https://www.irtf.org/mailman/listinfo/rrg
  
  
  
  

  _______________________________________________
  rrg mailing list
  rrg@irtf.org
  http://www.irtf.org/mailman/listinfo/rrg

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sun Jan 11 19:20:44 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4B93228C28A;
	Sun, 11 Jan 2009 19:20:44 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0A89C28C28A
	for <rrg@core3.amsl.com>; Sun, 11 Jan 2009 19:20:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.166
X-Spam-Level: 
X-Spam-Status: No, score=0.166 tagged_above=-999 required=5 tests=[AWL=0.061, 
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 
	J_CHICKENPOX_36=0.6, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Lai3dxXouUgx for <rrg@core3.amsl.com>;
	Sun, 11 Jan 2009 19:20:42 -0800 (PST)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66])
	by core3.amsl.com (Postfix) with ESMTP id 0A19328C28B
	for <rrg@irtf.org>; Sun, 11 Jan 2009 19:20:42 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0KDC00CGO99QGO@szxga03-in.huawei.com> for
	rrg@irtf.org; Mon, 12 Jan 2009 11:20:15 +0800 (CST)
Received: from x41208a ([10.111.12.103])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0KDC003YF99QGN@szxga03-in.huawei.com> for
	rrg@irtf.org; Mon, 12 Jan 2009 11:20:14 +0800 (CST)
Date: Mon, 12 Jan 2009 11:20:14 +0800
From: Xu Xiaohu <xuxh@huawei.com>
In-reply-to: <2B5F3EA7272CFF47A66518E4FF3BE2350260512D@FIESEXC014.nsn-intra.net>
To: "'Flinck, Hannu (NSN - FI/Espoo)'" <hannu.flinck@nsn.com>,
	'RRG' <rrg@irtf.org>
Message-id: <000a01c97464$af8bdbe0$670c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Mailer: Microsoft Office Outlook 11
Thread-index: AclxSSvo2f3ViwPjThC6Gb8x8ADmCwAB/PuwAElk4WAAengXEA==
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Hannu,

>  So HIT is routable IPv6 address to enable legacy to legacy 
> communication? Is that good?

I'm not sure this is the case for HIP. However, in RANGI, the host ID is an
IPv6 PI address in CGA alike format ( the first part of this ID is
Administrative Domain (AD) ID, the latter part is the hash of the AD ID and
its public key ). This specific PI address could be routable in site where
legacy hosts exist (just as map&encaps approach). This is just my rough
thought of the proxy mechanism for RANGI, and I think this is also workable
for HIP.

>  How about having a two faced DNS for upgraded nodes? HIT 
> returned if source is from EID space, AAAA if not?

This is a very interesting idea. BTW, if the DNS server is upgraded, we can
also define another field for the HIT/host ID value in DNS request/reply
msgs which can be used between upgraded hosts and upgraded DNS servers.

Xiaohu

> >-----Original Message-----
> >From: rrg-bounces@irtf.org [mailto:rrg-bounces@irtf.org] On 
> Behalf Of 
> >ext Xu Xiaohu
> >Sent: Thursday, January 08, 2009 07:30
> >To: 'Scott Brim'
> >Cc: 'RRG'; 'Robin Whittle'
> >Subject: Re: [rrg] Rejecting all but Strategy A
> >
> >
> >> > When a legecy host A initiates a communication with a
> >> HIP-enabled host
> >> > B,  A could send a packet to a nearby proxy (like ITR's
> >> role) by using
> >> > B's HIT as locator.
> >> 
> >> Would you replace host B's A record with a HIT?  Or would
> >this require
> >> a modification to host A?  If you're going to modify A, 
> why not just 
> >> implement HIP?
> >
> >Replacing host B's AAAA record with a HIT is my thought. If a legacy 
> >host got B's AAAA record from DNS, it will look that record 
> as a IPv6 
> >address And the mapping between HIT and locator (IP address) can be 
> >maintained in a seperate mapping system, e.g. a hierarchical DHT 
> >system.
> > 
> >Xiaohu
> >
> >
> >_______________________________________________
> >rrg mailing list
> >rrg@irtf.org
> >https://www.irtf.org/mailman/listinfo/rrg
> >
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> http://www.irtf.org/mailman/listinfo/rrg

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sun Jan 11 19:56:38 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E52DB3A691F;
	Sun, 11 Jan 2009 19:56:38 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C8D1628C294
	for <rrg@core3.amsl.com>; Sun, 11 Jan 2009 19:56:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[AWL=-0.401,
	BAYES_00=-2.599, J_BACKHAIR_34=1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id O5yYoThKX0RQ for <rrg@core3.amsl.com>;
	Sun, 11 Jan 2009 19:56:37 -0800 (PST)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.237])
	by core3.amsl.com (Postfix) with ESMTP id 168853A68E0
	for <rrg@irtf.org>; Sun, 11 Jan 2009 19:56:37 -0800 (PST)
Received: by rv-out-0506.google.com with SMTP id f6so13125241rvb.7
	for <rrg@irtf.org>; Sun, 11 Jan 2009 19:56:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from
	:organization:user-agent:mime-version:to:cc:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=+MMwNTCyZP2+mih7qBhnk20koI99FOEqVFjnSVkohmc=;
	b=YnndO0S1E0yRaUV14MMN89nQ2NPaCiJ9pMPwp0gGW7mN60YC+r1wX1NPlakGMlwDse
	mAkhc+Fy+XaSNrr3DF+bYOg/esyFBQtgb1huAgVofiOJLS/M0E9AdY47UuuVGaMCJFeH
	AekatEJ2uzClLVLN8XMtYxgt4H07xBwi5O0vw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	b=XHG0TnImmhwTHn1Z0lVSMJtZguMych6xw8rtPaZ82+ORVHI92G1bTTn8f0GUqAbxT9
	jT6o0oaO1UP5zg1sMs0dffLQZ3QURqEx0yrlgPGNP9wYkZw1ljTsG5zTBuOPRaAgUSO5
	5TttvEPQyz+Y/6UlZiqxWDh/xAzGiMIc0wGLE=
Received: by 10.141.48.6 with SMTP id a6mr6374448rvk.36.1231732581810;
	Sun, 11 Jan 2009 19:56:21 -0800 (PST)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz
	[130.216.38.124])
	by mx.google.com with ESMTPS id b8sm10922301rvf.9.2009.01.11.19.56.20
	(version=SSLv3 cipher=RC4-MD5); Sun, 11 Jan 2009 19:56:21 -0800 (PST)
Message-ID: <496ABF62.60600@gmail.com>
Date: Mon, 12 Jan 2009 16:56:18 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Scott Brim <swb@employees.org>
References: <495F0BAA.2040303@firstpr.com.au><49611E83.8050301@gmail.com><4961CFD3.2050304@firstpr.com.au><D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com><20EEF623-B503-4994-B099-64715E567B2D@cisco.com><474EEBD229DF754FB83D256004D021080AD5E539@XCH-NW-6V1.nw.nos.boeing.com><39C363776A4E8C4A94691D2BD9D1C9A105623AC3@XCH-NW-7V2.nw.nos.boeing.com>	<96CDEE57-28F3-416C-8AAD-D3F7330B3C5A@nomadiclab.com>	<77F357662F8BFA4CA7074B0410171B6D07B0BC42@XCH-NW-5V1.nw.nos.boeing.com>	<39C363776A4E8C4A94691D2BD9D1C9A10566DB53@XCH-NW-7V2.nw.nos.boeing.com>
	<496573E2.7000703@gmail.com> <49657EE3.6000403@employees.org>
In-Reply-To: <49657EE3.6000403@employees.org>
Cc: RRG <rrg@irtf.org>, Robin Whittle <rw@firstpr.com.au>
Subject: [rrg] Scope Re:  Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On 2009-01-08 17:19, Scott Brim wrote:
> Brian E Carpenter allegedly wrote on 1/7/09 10:32 PM:
>> Fred,
>>
>> That's my mental model, except that I think of the locators
>> as LOC0, LOC1, etc to allow for the inevitable hierarchy.
>> I had also assumed there would need to be a hierarchy of maps,
>> with HIT<->LOC0 as the lowest level map, but Scott Brim obviously
>> has another model in mind (I need to think a bit more before
>> replying to Scott).
>>
>>    Brian
> 
> What HIP gives you is an identifier that may be used for many things.
> An HI can be, but does not have to be, part of the process of initially
> finding a locator for an endpoint. For example, I can go straight from
> domain name to locator (which actually might be an agent / proxy /
> rendezvous point), and then validate identities via some other means.

Assuming I deem the DNS trustworthy, it seems much more natural
to treat the DNS as the source of an HI, and then for the locator to be
looked up as a function of the HI. I'm not saying your model doesn't work,
but surely the HI is fundamental and has universal validity, and the locator
(any of the locators) is transient and has non-universal scope? So starting
with a locator lookup seems funny.

    Brian
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sun Jan 11 20:21:15 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A70153A688A;
	Sun, 11 Jan 2009 20:21:15 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D0DF43A688A
	for <rrg@core3.amsl.com>; Sun, 11 Jan 2009 20:21:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.191
X-Spam-Level: 
X-Spam-Status: No, score=-1.191 tagged_above=-999 required=5 tests=[AWL=1.408, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 3-9x+wjaokLT for <rrg@core3.amsl.com>;
	Sun, 11 Jan 2009 20:21:14 -0800 (PST)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67])
	by core3.amsl.com (Postfix) with ESMTP id E4E8F3A6876
	for <rrg@irtf.org>; Sun, 11 Jan 2009 20:21:13 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12])
	by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0KDC003EZC2XY1@szxga04-in.huawei.com> for
	rrg@irtf.org; Mon, 12 Jan 2009 12:20:57 +0800 (CST)
Received: from x41208a ([10.111.12.103])
	by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0KDC00D5UC2XOA@szxga04-in.huawei.com> for
	rrg@irtf.org; Mon, 12 Jan 2009 12:20:57 +0800 (CST)
Date: Mon, 12 Jan 2009 12:20:57 +0800
From: Xu Xiaohu <xuxh@huawei.com>
In-reply-to: <496ABF62.60600@gmail.com>
To: 'Brian E Carpenter' <brian.e.carpenter@gmail.com>,
	'Scott Brim' <swb@employees.org>
Message-id: <000d01c9746d$2ad1f570$670c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Mailer: Microsoft Office Outlook 11
Thread-index: Acl0acwEB26YRnVgQsCEoGdHU2P9KgAAhjlg
Cc: 'RRG' <rrg@irtf.org>, 'Robin Whittle' <rw@firstpr.com.au>
Subject: Re: [rrg] Scope Re:  Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org


> > What HIP gives you is an identifier that may be used for 
> many things.
> > An HI can be, but does not have to be, part of the process of 
> > initially finding a locator for an endpoint. For example, I can go 
> > straight from domain name to locator (which actually might 
> be an agent 
> > / proxy / rendezvous point), and then validate identities 
> via some other means.
> 
> Assuming I deem the DNS trustworthy, it seems much more 
> natural to treat the DNS as the source of an HI, and then for 
> the locator to be looked up as a function of the HI. I'm not 
> saying your model doesn't work, but surely the HI is 
> fundamental and has universal validity, and the locator (any 
> of the locators) is transient and has non-universal scope? So 
> starting with a locator lookup seems funny.

I prefer Brain's opinion since there is no need for each host owns a FQDN
name. Once you tell me your host ID, I can resolve your locator from a
seperate ID/locator mapping system and then communicate with you. 

Xiaohu

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sun Jan 11 22:19:39 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DCFD93A6840;
	Sun, 11 Jan 2009 22:19:39 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D37533A6840
	for <rrg@core3.amsl.com>; Sun, 11 Jan 2009 22:19:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id IPznzvoErvuS for <rrg@core3.amsl.com>;
	Sun, 11 Jan 2009 22:19:37 -0800 (PST)
Received: from n2.nomadiclab.com (n2.nomadiclab.com
	[IPv6:2001:14b8:400:101::2])
	by core3.amsl.com (Postfix) with ESMTP id 5AD093A6830
	for <rrg@irtf.org>; Sun, 11 Jan 2009 22:19:35 -0800 (PST)
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id D5B441EF126;
	Mon, 12 Jan 2009 08:19:09 +0200 (EET)
Received: from [127.0.0.1] (localhost [IPv6:::1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 37DF31EF125;
	Mon, 12 Jan 2009 08:19:08 +0200 (EET)
Message-Id: <F4C912C6-0870-4EE2-A732-913BA7005AB8@nomadiclab.com>
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
To: Xu Xiaohu <xuxh@huawei.com>,
	Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <000d01c9746d$2ad1f570$670c6f0a@china.huawei.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Mon, 12 Jan 2009 08:19:05 +0200
References: <000d01c9746d$2ad1f570$670c6f0a@china.huawei.com>
X-Mailer: Apple Mail (2.930.3)
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: RRG <rrg@irtf.org>
Subject: [rrg]  Handling multiple layers of indirection
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Summary:  One can initially deploy multiple layers of indirection  
initially by "architecturally cheating"  or "hiding" some of the  
indirection layers so that they are not visible to the resolution  
system nor in data plane packets.

>>> What HIP gives you is an identifier that may be used for many  
>>> things.
>>
>> Assuming I deem the DNS trustworthy, it seems much more natural to  
>> treat the DNS as the source of an HI, and then for the locator to  
>> be looked up as a function of the HI. I'm not saying your model  
>> doesn't work, but surely the HI is fundamental and has universal  
>> validity, and the locator (any of the locators) is transient and  
>> has non-universal scope? So starting with a locator lookup seems  
>> funny.
>
> I prefer Brain's opinion since there is no need for each host owns a  
> FQDN name. Once you tell me your host ID, I can resolve your locator  
> from a seperate ID/locator mapping system and then communicate with  
> you.

 From an architectural orthodoxy point of view, i.e. from the layering  
point of view, what you and Brian describe may well be the "right"  
way.  Indeed, what you describe is more-or-less what happens with HIP  
as standardised today.  You get the HIT and a set of initial locators  
from the DNS.  The initial locators are typically those of rendezvous  
servers, which in turn know the current locator(s) of a mobile host.   
For details, see RFC5204 and RFC5205.

However, if you consider the various early deployment scenarios, the  
situation is different.  The question is no longer what is "right",  
from the architectural point of view, but what is the best deployment  
strategy.  From that point of view, a good strategy may be to  
initially get only the locators from the DNS, as that requires no  
changes to the DNS.  The HIT (or the HITs) can then be learned form  
the peer, along the opportunistic HIP model.  See Section 4.1.6 of RFC  
5201.  But I can also imagine other deployment models.

IMHO, if we want to consider the deployability a HIP-based solution,  
or any solution, what Noel wrote before Christmas is well worth  
reading again:

http://www.ietf.org/mail-archive/web/rrg/current/msg04037.html

(Remember, that is the message to which I reacted, causing the current  
thread of messages about HIP, where I have mainly tried to explain  
that HIP-proxy could have a quite different deployment model than the  
plain HIP has.)

In general, the question is very much about deployment cost.  With  
proxy HIP, by initially "hiding" the HITs and using the opportunistic  
HIP model and ephemeral or even imaginary HITs, we can "fold" the HIP  
model into what is essentially the map-and-encaps model.

[[Generalising more, once again: one can deploy architecturally host- 
based solutions initially as network-based ones, and vice versa.   
Conversely, one can design architecturally host-bast solutions that  
are *hard* to deploy as network-based ones, and one can design  
architecturally network-based solutions that are *hard* to utilise in  
single hosts.  And vice versa.  Hence, paying attention to the  
details, both in selecting the architectural approach and thinking  
about the deployment flexibility, should pay off to the community in  
the large.

I've been trying to say that now for over two years, and nobody still  
seems to pay any attention.  Am I completely bogged and off the road  
in my thinking?]]

--Pekka

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan 12 00:36:53 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 21DE53A695F;
	Mon, 12 Jan 2009 00:36:53 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C61BC3A695F
	for <rrg@core3.amsl.com>; Mon, 12 Jan 2009 00:36:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.517
X-Spam-Level: 
X-Spam-Status: No, score=-1.517 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, URIBL_RHS_DOB=1.083]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 0Kij5CeWKtlq for <rrg@core3.amsl.com>;
	Mon, 12 Jan 2009 00:36:51 -0800 (PST)
Received: from felwood.infrahip.net (felwood.infrahip.net
	[IPv6:2001:708:140:220::3])
	by core3.amsl.com (Postfix) with ESMTP id 40E063A67D0
	for <rrg@irtf.org>; Mon, 12 Jan 2009 00:36:49 -0800 (PST)
Received: from stargazer.pc.infrahip.net (stargazer.pc.infrahip.net
	[IPv6:2001:708:140:220:215:60ff:fe9f:60c4])
	by felwood.infrahip.net (8.14.2/8.14.2) with ESMTP id n0C8Zx61029955;
	Mon, 12 Jan 2009 10:36:00 +0200
Date: Mon, 12 Jan 2009 10:35:59 +0200 (EET)
From: Oleg Ponomarev <oleg.ponomarev@hiit.fi>
X-X-Sender: ponomare@stargazer.pc.infrahip.net
To: Xu Xiaohu <xuxh@huawei.com>
In-Reply-To: <000a01c97464$af8bdbe0$670c6f0a@china.huawei.com>
Message-ID: <alpine.LFD.2.00.0901121021250.17180@stargazer.pc.infrahip.net>
References: <000a01c97464$af8bdbe0$670c6f0a@china.huawei.com>
User-Agent: Alpine 2.00 (LFD 1167 2008-08-23)
X-GPG-FINGRPRINT: E94D 632A 70E4 3F92 9A7E  B04E 20BF FC6B 983B CA5E
X-GPG-PUBLIC_KEY: http://ponomarev.ru/oleg.asc
MIME-Version: 1.0
Cc: 'RRG' <rrg@irtf.org>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Hi! On Mon, 12 Jan 2009, Xu Xiaohu wrote:

>>  How about having a two faced DNS for upgraded nodes? HIT
>> returned if source is from EID space, AAAA if not?
>
> This is a very interesting idea. BTW, if the DNS server is upgraded, we can
> also define another field for the HIT/host ID value in DNS request/reply
> msgs which can be used between upgraded hosts and upgraded DNS servers.

Just in case, this is HIP RR defined in RFC5205 and given type 55 by IANA.

And yes, the DNS server / proxy replies with HIT in AAAA field for legacy 
applications. The locators can be found in records for 
5.7.d.1.c.c.8.d.0.6.3.b.a.4.6.2.5.0.5.2.e.4.7.5.e.1.0.0.1.0.0.2.hit-to-ip.net 
(when HIT is 2001:1e:574e:2505:264a:b360:d8cc:1d75)

-- 
Regards, Oleg.

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan 12 01:32:21 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7FC2C3A692D;
	Mon, 12 Jan 2009 01:32:21 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9B6913A692D
	for <rrg@core3.amsl.com>; Mon, 12 Jan 2009 01:32:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.302
X-Spam-Level: 
X-Spam-Status: No, score=0.302 tagged_above=-999 required=5 tests=[AWL=-0.286, 
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 
	RDNS_NONE=0.1, URIBL_RHS_DOB=1.083]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id rsmb9uKdzF-a for <rrg@core3.amsl.com>;
	Mon, 12 Jan 2009 01:32:19 -0800 (PST)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65])
	by core3.amsl.com (Postfix) with ESMTP id 4A4043A68A2
	for <rrg@irtf.org>; Mon, 12 Jan 2009 01:32:19 -0800 (PST)
Received: from huawei.com (szxga02-in [172.24.2.6])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0KDC000CRQH568@szxga02-in.huawei.com> for
	rrg@irtf.org; Mon, 12 Jan 2009 17:31:54 +0800 (CST)
Received: from x41208a ([10.111.12.103])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0KDC00KOWQH5T3@szxga02-in.huawei.com> for
	rrg@irtf.org; Mon, 12 Jan 2009 17:31:53 +0800 (CST)
Date: Mon, 12 Jan 2009 17:31:52 +0800
From: Xu Xiaohu <xuxh@huawei.com>
In-reply-to: <alpine.LFD.2.00.0901121021250.17180@stargazer.pc.infrahip.net>
To: 'Oleg Ponomarev' <oleg.ponomarev@hiit.fi>
Message-id: <002201c97498$9a8cf5b0$670c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Mailer: Microsoft Office Outlook 11
Thread-index: Acl0liypOK3QCC/aR66+1KXUiT6UGwAAP7HQ
Cc: 'RRG' <rrg@irtf.org>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org


Oleg,

> Hi! On Mon, 12 Jan 2009, Xu Xiaohu wrote:
> 
> >>  How about having a two faced DNS for upgraded nodes? HIT 
> returned if 
> >> source is from EID space, AAAA if not?
> >
> > This is a very interesting idea. BTW, if the DNS server is 
> upgraded, 
> > we can also define another field for the HIT/host ID value in DNS 
> > request/reply msgs which can be used between upgraded hosts 
> and upgraded DNS servers.
> 
> Just in case, this is HIP RR defined in RFC5205 and given 
> type 55 by IANA.
> 
> And yes, the DNS server / proxy replies with HIT in AAAA 
> field for legacy applications. The locators can be found in 
> records for 
> 5.7.d.1.c.c.8.d.0.6.3.b.a.4.6.2.5.0.5.2.e.4.7.5.e.1.0.0.1.0.0.
> 2.hit-to-ip.net
> (when HIT is 2001:1e:574e:2505:264a:b360:d8cc:1d75)

Perfect. The ID to locator mapping service can still use the DNS technology
just like what ENUM does. 

By the way, if the HIT can be modified to have some structure, the id to
locator mapping system will be more managable and scalable like current DNS.
^_^

Xiaohu.

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan 12 01:45:34 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 85EB528C0E8;
	Mon, 12 Jan 2009 01:45:34 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D18BD3A69FC
	for <rrg@core3.amsl.com>; Mon, 12 Jan 2009 01:45:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.321
X-Spam-Level: 
X-Spam-Status: No, score=0.321 tagged_above=-999 required=5 tests=[AWL=-0.267, 
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 
	RDNS_NONE=0.1, URIBL_RHS_DOB=1.083]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 2FWfpguALSIo for <rrg@core3.amsl.com>;
	Mon, 12 Jan 2009 01:45:33 -0800 (PST)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65])
	by core3.amsl.com (Postfix) with ESMTP id B0AF63A6853
	for <rrg@irtf.org>; Mon, 12 Jan 2009 01:45:32 -0800 (PST)
Received: from huawei.com (szxga02-in [172.24.2.6])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0KDC0000KR3768@szxga02-in.huawei.com> for
	rrg@irtf.org; Mon, 12 Jan 2009 17:45:07 +0800 (CST)
Received: from x41208a ([10.111.12.103])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0KDC00CUOR37P6@szxga02-in.huawei.com> for
	rrg@irtf.org; Mon, 12 Jan 2009 17:45:07 +0800 (CST)
Date: Mon, 12 Jan 2009 17:45:06 +0800
From: Xu Xiaohu <xuxh@huawei.com>
In-reply-to: <alpine.LFD.2.00.0901121021250.17180@stargazer.pc.infrahip.net>
To: 'Oleg Ponomarev' <oleg.ponomarev@hiit.fi>
Message-id: <002801c9749a$739d3d00$670c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Mailer: Microsoft Office Outlook 11
Thread-index: Acl0liypOK3QCC/aR66+1KXUiT6UGwAA7JeQ
Cc: 'RRG' <rrg@irtf.org>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org


> And yes, the DNS server / proxy replies with HIT in AAAA 
> field for legacy applications. The locators can be found in 
> records for 
> 5.7.d.1.c.c.8.d.0.6.3.b.a.4.6.2.5.0.5.2.e.4.7.5.e.1.0.0.1.0.0.
> 2.hit-to-ip.net
> (when HIT is 2001:1e:574e:2505:264a:b360:d8cc:1d75)

by the way,  is there any HIP related RFC or draft for the above method?

Thanks,

Xiaohu


_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan 12 01:56:46 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E52093A68A2;
	Mon, 12 Jan 2009 01:56:46 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6F2A23A67D8
	for <rrg@core3.amsl.com>; Mon, 12 Jan 2009 01:56:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.517
X-Spam-Level: 
X-Spam-Status: No, score=-1.517 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, URIBL_RHS_DOB=1.083]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id gnsotxj9rall for <rrg@core3.amsl.com>;
	Mon, 12 Jan 2009 01:56:44 -0800 (PST)
Received: from felwood.infrahip.net (felwood.infrahip.net
	[IPv6:2001:708:140:220::3])
	by core3.amsl.com (Postfix) with ESMTP id 0CBE93A68A2
	for <rrg@irtf.org>; Mon, 12 Jan 2009 01:56:42 -0800 (PST)
Received: from stargazer.pc.infrahip.net (stargazer.pc.infrahip.net
	[IPv6:2001:708:140:220:215:60ff:fe9f:60c4])
	by felwood.infrahip.net (8.14.2/8.14.2) with ESMTP id n0C9uCY4030097;
	Mon, 12 Jan 2009 11:56:12 +0200
Date: Mon, 12 Jan 2009 11:56:11 +0200 (EET)
From: Oleg Ponomarev <oleg.ponomarev@hiit.fi>
X-X-Sender: ponomare@stargazer.pc.infrahip.net
To: Xu Xiaohu <xuxh@huawei.com>
In-Reply-To: <002801c9749a$739d3d00$670c6f0a@china.huawei.com>
Message-ID: <alpine.LFD.2.00.0901121147220.17180@stargazer.pc.infrahip.net>
References: <002801c9749a$739d3d00$670c6f0a@china.huawei.com>
User-Agent: Alpine 2.00 (LFD 1167 2008-08-23)
X-GPG-FINGRPRINT: E94D 632A 70E4 3F92 9A7E  B04E 20BF FC6B 983B CA5E
X-GPG-PUBLIC_KEY: http://ponomarev.ru/oleg.asc
MIME-Version: 1.0
Cc: 'RRG' <rrg@irtf.org>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Hi! On Mon, 12 Jan 2009, Xu Xiaohu wrote:

>> And yes, the DNS server / proxy replies with HIT in AAAA
>> field for legacy applications. The locators can be found in
>> records for
>> 5.7.d.1.c.c.8.d.0.6.3.b.a.4.6.2.5.0.5.2.e.4.7.5.e.1.0.0.1.0.0.
>> 2.hit-to-ip.net
>> (when HIT is 2001:1e:574e:2505:264a:b360:d8cc:1d75)
>
> by the way,  is there any HIP related RFC or draft for the above method?

Unfortunately there is only a chapter in HIPL manual and an old 
workshop paper at the moment, but I will submit some draft soon.

http://hipl.hiit.fi/hipl/manual/ch24.html
http://trustinet.org/papers/ponomarev-ring-2007.pdf

-- 
Regards, Oleg.

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan 12 07:08:11 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4ABF03A6A57;
	Mon, 12 Jan 2009 07:08:11 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3488E28C113
	for <rrg@core3.amsl.com>; Mon, 12 Jan 2009 07:08:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id WkDc1PWQXTy4 for <rrg@core3.amsl.com>;
	Mon, 12 Jan 2009 07:08:09 -0800 (PST)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133])
	by core3.amsl.com (Postfix) with ESMTP id 6E0F928B797
	for <rrg@irtf.org>; Mon, 12 Jan 2009 07:08:09 -0800 (PST)
Received: by dog.tcb.net (Postfix, from userid 0)
	id B275A2684EA; Mon, 12 Jan 2009 08:07:54 -0700 (MST)
Received: from [192.168.0.100] (97-122-99-176.hlrn.qwest.net [97.122.99.176])
	(authenticated-user danny) (TLSv1/SSLv3 AES128-SHA 128/128)
	by dog.tcb.net with SMTP; Mon, 12 Jan 2009 08:07:54 -0700 (MST)
	(envelope-from danny@arbor.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=97.122.99.176;
	client-port=53509; syn-fingerprint=65535:55:1:64:M1316,N,W3,N,N,T,S;
	data-bytes=0
Message-Id: <6CB97876-3DB5-4355-9EC1-5599D71FF7D2@arbor.net>
From: Danny McPherson <danny@arbor.net>
To: tony.li@tony.li
In-Reply-To: <9FEF736036A74B148CC307D8FA35B720@ad.redback.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Mon, 12 Jan 2009 08:07:53 -0700
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com>
	<3c3e3fca0901021219t2ab35dfsb2532e0c89be84af@mail.gmail.com>
	<E99E41EB33084B5B899C7EED9DE607E9@ad.redback.com>
	<3c3e3fca0901021334j22d17e54iec4bbf41b6c00480@mail.gmail.com>
	<BCFF32A1356842BF839C7DF7D059F15F@ad.redback.com>
	<3525C9833C09ED418C6FD6CD9514668C0566045E@emailwf1.jnpr.net>
	<354C0AE786D1424C886C4A3570611291@ad.redback.com>
	<200901051509.n05F9nM02828@magenta.juniper.net>
	<DD2FDA0A88E84736AB1F3D25A3F61986@ad.redback.com>
	<4963C721.9080808@gmail.com>
	<75cb24520901061405m50a63533p86d77284b149d4cf@mail.gmail.com>
	<9FEF736036A74B148CC307D8FA35B720@ad.redback.com>
X-Mailer: Apple Mail (2.930.3)
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org


On Jan 6, 2009, at 4:23 PM, Tony Li wrote:
>
>
> I know that the internal tables are always a pain, but since we have  
> to deal
> with the global issues, the internal, private growth (self- 
> inflicted ;-) has
> to necessarily be out of scope for RRG.

That's quite odd to me, considering by today's definitions
"internal [BGP] tables" are where the routing scalability and
stability are it's worst - today, and unquestionably, the first
place things will break IF/WHEN they do, as a result of an
inter-domain routing protocol architecture that forces either
full-mesh or hierarchies such as route reflection that themselves
introduce additional paths and state in the network (even with
implicit aggregation effects).

And they're not going to break because of a 100k unique
internal-only routes, they're going to break because of
an order or magnitude or more paths (and all of their overhead)
- paths introduced as a result of "global issues" and solutions
that focus on solely minimizing DFZ size, rather than looking
at where the problem is actually worst - today.

-danny
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan 12 07:09:22 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8B03A3A68DA;
	Mon, 12 Jan 2009 07:09:22 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9C9DF3A68DA
	for <rrg@core3.amsl.com>; Mon, 12 Jan 2009 07:09:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.437
X-Spam-Level: 
X-Spam-Status: No, score=-6.437 tagged_above=-999 required=5 tests=[AWL=0.162, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id gF0FRuboRCzy for <rrg@core3.amsl.com>;
	Mon, 12 Jan 2009 07:09:19 -0800 (PST)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com
	[130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id 96E8F3A67AF
	for <rrg@irtf.org>; Mon, 12 Jan 2009 07:09:19 -0800 (PST)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231])
	by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id n0CF8oGa010968
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 12 Jan 2009 07:08:53 -0800 (PST)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	n0CF8owj022287; Mon, 12 Jan 2009 07:08:50 -0800 (PST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	n0CF8oMI022282; Mon, 12 Jan 2009 07:08:50 -0800 (PST)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 12 Jan 2009 07:08:49 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 12 Jan 2009 07:08:48 -0800
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1056AAC35@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <BBEA3D1B-47DC-4003-B300-9F61A45F6775@nomadiclab.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Recursive re-encapsulations
Thread-Index: AclzJCHos4T5nrMMSS22LzSfDRkfEQBorytg
References: <495F0BAA.2040303@firstpr.com.au><49611E83.8050301@gmail.com><4961CFD3.2050304@firstpr.com.au><D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com><20EEF623-B503-4994-B099-64715E567B2D@cisco.com><474EEBD229DF754FB83D256004D021080AD5E539@XCH-NW-6V1.nw.nos.boeing.com><39C363776A4E8C4A94691D2BD9D1C9A105623AC3@XCH-NW-7V2.nw.nos.boeing.com>
	<96CDEE57-28F3-416C-8AAD-D3F7330B3C5A@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D07B0BC42@XCH-NW-5V1.nw.nos.boeing.com>
	<39C363776A4E8C4A94691D2BD9D1C9A10566DB53@XCH-NW-7V2.nw.nos.boeing.com>
	<C83DB85A-CE29-4288-87F8-07447C2DF862@nomadiclab.com>
	<39C363776A4E8C4A94691D2BD9D1C9A10566DF39@XCH-NW-7V2.nw.nos.boeing.com>
	<695CF996-623A-40FA-B349-0162A72374D7@nomadiclab.com>
	<39C363776A4E8C4A94691D2BD9D1C9A10566E3D9@XCH-NW-7V2.nw.nos.boeing.com>
	<BBEA3D1B-47DC-4003-B300-9F61A45F6775@nomadiclab.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Pekka Nikander" <pekka.nikander@nomadiclab.com>
X-OriginalArrivalTime: 12 Jan 2009 15:08:49.0618 (UTC)
	FILETIME=[AC61E320:01C974C7]
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] Recursive re-encapsulations
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Hi Pekka,

>-----Original Message-----
>From: Pekka Nikander [mailto:pekka.nikander@nomadiclab.com]
>Sent: Saturday, January 10, 2009 5:06 AM
>To: Templin, Fred L
>Cc: RRG
>Subject: Re: Recursive re-encapsulations
>
>>>>>> Regarding HIP + map/encaps, maybe it is obvious to everyone else
>>>>>> already but I think what that gives you is an endpoint identity
>>>>>> (the HIT), an inner routing locator (iRLOC), and an outer RLOC
>>>>>> (oRLOC). Up to now, LISP (and perhaps others) have been using the
>>>>>> term "EID" to refer to what I mean by "iRLOC", and the term
"RLOC"
>>>>>> to refer to what I mean by "oRLOC".
>>>>>
>>>>> That is my basic model as well.  Further, as Brian observed, that
>>>>> can be applied recursively.
>>>>
>>>> Yes. One small but important distinction though is that recursion
is
>>>> not meaning to say that there would be recursive encapsulations
>>>> (i.e., IP0-in-IP1-in-IP2-in ... in-IPN); else we would eat
ourselves
>>>> out of MTU in a hurry.
>>>
>>> Well, I would expect 1-to-1 mapping between HITs and iRLOCs,
allowing
>>> one to use just one encapsulation or even almost-null encapsulation.
>>> That is, e.g. iRLOC-in-oRLOCi, HIT-in-oRLOCi, or TAG-in-oRLOCi where
>>> TAG is whatever minimal encapsulation/tag is needed for demuxing at
>>> oRLOCi.
>>
>> I may not have made myself clear. I am talking about HIP in
>> conjunction with the RANGER/VET/SEAL model, and specifically
>> about the over-the-wire encapsulation format.
>
>I suggest that we take this off-line, as there are many details.  If
>someone else is interested, feel free to drop a note.  It may be worth
>to wrap the details into a draft, perhaps.
>
>Anyway, from my point of view, what you described in the message
>
>http://www.ietf.org/mail-archive/web/rrg/current/msg04312.html
>
>is the case of using vanilla HIP on a HIP-enabled host, landing on a
>network behind a lisp xTR or a similar device.  In that case you
>indeed get the packet structures you described.

I'm actually meaning to refer to a HIP-enabled proxy router
landing on the same platform as an xTR (although the model
would be the same if the HIP-enabled proxy landed on a link
downstream from the xTR).

>However, if we aim for the kind of hybrid LISP-HIP-proxy design that
>I've been suggesting, I believe that the packet formats could be much
>simpler.

I'm not exactly sure how; xTR means IP-in-IP encapsulation.
Were you meaning for it to mean something else?

>AFAICS, the crux will always be on how much demultiplexing / security
>verification state you need at the receiving end, at the unwrapping
>xTR.  If your trust model allows you to decapsulate without
>verification, you can live without such state and include the inner
>locators or identifiers into the packet.  However, if the trust model
>requires one to verify the inner locators or identifiers, then there
>must be the state at the receiving end, meaning that you get smaller
>overhead if you don't include the full inner header in the packet but
>just index to the state + any bits not directly stored in the state.

With RANGER/VET/SEAL, I am looking for a way for the ITR to
establish sufficient securing state in the ETR through a single
message sent forward before any data messages are sent (i.e.,
a "1-way handshake"). Can HIP do that?

Thanks - Fred
fred.l.templin@boeing.com

>--Pekka

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan 12 07:10:03 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BDCAC28C0EB;
	Mon, 12 Jan 2009 07:10:03 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B994B28C0E4
	for <rrg@core3.amsl.com>; Mon, 12 Jan 2009 07:10:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.9
X-Spam-Level: 
X-Spam-Status: No, score=-5.9 tagged_above=-999 required=5 tests=[AWL=-0.384, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, URIBL_RHS_DOB=1.083]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id HuLt3LAdObrT for <rrg@core3.amsl.com>;
	Mon, 12 Jan 2009 07:10:01 -0800 (PST)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com
	[130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id AE6B93A67CF
	for <rrg@irtf.org>; Mon, 12 Jan 2009 07:10:00 -0800 (PST)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231])
	by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id n0CF9B9d023772
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);
	Mon, 12 Jan 2009 07:09:12 -0800 (PST)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	n0CF9BAN022926; Mon, 12 Jan 2009 07:09:11 -0800 (PST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	n0CF9A4I022898; Mon, 12 Jan 2009 07:09:11 -0800 (PST)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 12 Jan 2009 07:09:07 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 12 Jan 2009 07:09:06 -0800
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1056AAC38@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <alpine.LFD.2.00.0901121147220.17180@stargazer.pc.infrahip.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] Rejecting all but Strategy A
Thread-Index: Acl0nA2pF2elGORASXe8V1EWIQNE9AAKaXVw
References: <002801c9749a$739d3d00$670c6f0a@china.huawei.com>
	<alpine.LFD.2.00.0901121147220.17180@stargazer.pc.infrahip.net>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Oleg Ponomarev" <oleg.ponomarev@hiit.fi>, "Xu Xiaohu" <xuxh@huawei.com>
X-OriginalArrivalTime: 12 Jan 2009 15:09:07.0884 (UTC)
	FILETIME=[B7450EC0:01C974C7]
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Oleg and Xu,

There is clearly some synergy here with what is being
proposed in RANGER/VET/SEAL. Xu, you may in particular
be interested in looking at those documents for
parallels with RANGI.

Thanks - Fred
fred.l.templin@boeing.com


>-----Original Message-----
>From: Oleg Ponomarev [mailto:oleg.ponomarev@hiit.fi]
>Sent: Monday, January 12, 2009 1:56 AM
>To: Xu Xiaohu
>Cc: 'RRG'
>Subject: Re: [rrg] Rejecting all but Strategy A
>
>Hi! On Mon, 12 Jan 2009, Xu Xiaohu wrote:
>
>>> And yes, the DNS server / proxy replies with HIT in AAAA
>>> field for legacy applications. The locators can be found in
>>> records for
>>> 5.7.d.1.c.c.8.d.0.6.3.b.a.4.6.2.5.0.5.2.e.4.7.5.e.1.0.0.1.0.0.
>>> 2.hit-to-ip.net
>>> (when HIT is 2001:1e:574e:2505:264a:b360:d8cc:1d75)
>>
>> by the way,  is there any HIP related RFC or draft for the above
method?
>
>Unfortunately there is only a chapter in HIPL manual and an old
>workshop paper at the moment, but I will submit some draft soon.
>
>http://hipl.hiit.fi/hipl/manual/ch24.html
>http://trustinet.org/papers/ponomarev-ring-2007.pdf
>
>--
>Regards, Oleg.
>
>_______________________________________________
>rrg mailing list
>rrg@irtf.org
>http://www.irtf.org/mailman/listinfo/rrg
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan 12 08:46:22 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1F3CA3A6A14;
	Mon, 12 Jan 2009 08:46:22 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9F5483A6A14
	for <rrg@core3.amsl.com>; Mon, 12 Jan 2009 08:46:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 9W1jrgA22mdA for <rrg@core3.amsl.com>;
	Mon, 12 Jan 2009 08:46:20 -0800 (PST)
Received: from n2.nomadiclab.com (n2.nomadiclab.com
	[IPv6:2001:14b8:400:101::2])
	by core3.amsl.com (Postfix) with ESMTP id 36B683A683A
	for <rrg@irtf.org>; Mon, 12 Jan 2009 08:46:20 -0800 (PST)
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 04AD81EF2AD;
	Mon, 12 Jan 2009 18:46:05 +0200 (EET)
Received: from [127.0.0.1] (localhost [IPv6:::1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 7F0E61EF248;
	Mon, 12 Jan 2009 18:46:04 +0200 (EET)
Message-Id: <8F620506-C2F2-41DE-BA3C-5FA63A028B27@nomadiclab.com>
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A1056AAC35@XCH-NW-7V2.nw.nos.boeing.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Mon, 12 Jan 2009 18:46:04 +0200
References: <495F0BAA.2040303@firstpr.com.au><49611E83.8050301@gmail.com><4961CFD3.2050304@firstpr.com.au><D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com><20EEF623-B503-4994-B099-64715E567B2D@cisco.com><474EEBD229DF754FB83D256004D021080AD5E539@XCH-NW-6V1.nw.nos.boeing.com><39C363776A4E8C4A94691D2BD9D1C9A105623AC3@XCH-NW-7V2.nw.nos.boeing.com>
	<96CDEE57-28F3-416C-8AAD-D3F7330B3C5A@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D07B0BC42@XCH-NW-5V1.nw.nos.boeing.com>
	<39C363776A4E8C4A94691D2BD9D1C9A10566DB53@XCH-NW-7V2.nw.nos.boeing.com>
	<C83DB85A-CE29-4288-87F8-07447C2DF862@nomadiclab.com>
	<39C363776A4E8C4A94691D2BD9D1C9A10566DF39@XCH-NW-7V2.nw.nos.boeing.com>
	<695CF996-623A-40FA-B349-0162A72374D7@nomadiclab.com>
	<39C363776A4E8C4A94691D2BD9D1C9A10566E3D9@XCH-NW-7V2.nw.nos.boeing.com>
	<BBEA3D1B-47DC-4003-B300-9F61A45F6775@nomadiclab.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1056AAC35@XCH-NW-7V2.nw.nos.boeing.com>
X-Mailer: Apple Mail (2.930.3)
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] Recursive re-encapsulations
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

>> However, if we aim for the kind of hybrid LISP-HIP-proxy design that
>> I've been suggesting, I believe that the packet formats could be much
>> simpler.
>
> I'm not exactly sure how; xTR means IP-in-IP encapsulation.
> Were you meaning for it to mean something else?

What I have been trying to describe is taking the LISP architecture  
and then replacing some parts of the xTR functionality with proxy-HIP.

> With RANGER/VET/SEAL, I am looking for a way for the ITR to
> establish sufficient securing state in the ETR through a single
> message sent forward before any data messages are sent (i.e.,
> a "1-way handshake"). Can HIP do that?

Depends on your security requirements and what you store in your  
mapping system.

A very short answer is that if you care about all the security threats  
HIP cares about, then if the ETR stores the HIP puzzle into the  
mapping system so that the ITR gets the puzzle along the ETR RLOC,  
then HIP can do that.

--Pekka

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan 12 09:35:07 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A473828C120;
	Mon, 12 Jan 2009 09:35:07 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 93A8D28C157
	for <rrg@core3.amsl.com>; Mon, 12 Jan 2009 09:35:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.534
X-Spam-Level: 
X-Spam-Status: No, score=-2.534 tagged_above=-999 required=5 tests=[AWL=0.065, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Lc0PFULJmLcX for <rrg@core3.amsl.com>;
	Mon, 12 Jan 2009 09:35:05 -0800 (PST)
Received: from QMTA02.westchester.pa.mail.comcast.net
	(qmta02.westchester.pa.mail.comcast.net [76.96.62.24])
	by core3.amsl.com (Postfix) with ESMTP id 9BD9D3A6B15
	for <rrg@irtf.org>; Mon, 12 Jan 2009 09:35:05 -0800 (PST)
Received: from OMTA07.westchester.pa.mail.comcast.net ([76.96.62.59])
	by QMTA02.westchester.pa.mail.comcast.net with comcast
	id 2gqx1b03i1GhbT852haryw; Mon, 12 Jan 2009 17:34:51 +0000
Received: from TONYLTM9XP ([155.53.41.237])
	by OMTA07.westchester.pa.mail.comcast.net with comcast
	id 2hae1b00h570qEr3Thahot; Mon, 12 Jan 2009 17:34:49 +0000
From: "Tony Li" <tony.li@tony.li>
To: "'Danny McPherson'" <danny@arbor.net>
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com>
	<3c3e3fca0901021219t2ab35dfsb2532e0c89be84af@mail.gmail.com>
	<E99E41EB33084B5B899C7EED9DE607E9@ad.redback.com>
	<3c3e3fca0901021334j22d17e54iec4bbf41b6c00480@mail.gmail.com>
	<BCFF32A1356842BF839C7DF7D059F15F@ad.redback.com>
	<3525C9833C09ED418C6FD6CD9514668C0566045E@emailwf1.jnpr.net>
	<354C0AE786D1424C886C4A3570611291@ad.redback.com>
	<200901051509.n05F9nM02828@magenta.juniper.net>
	<DD2FDA0A88E84736AB1F3D25A3F61986@ad.redback.com>
	<4963C721.9080808@gmail.com>
	<75cb24520901061405m50a63533p86d77284b149d4cf@mail.gmail.com>
	<9FEF736036A74B148CC307D8FA35B720@ad.redback.com>
	<6CB97876-3DB5-4355-9EC1-5599D71FF7D2@arbor.net>
Date: Mon, 12 Jan 2009 09:34:34 -0800
Message-ID: <BC8BF03B917B468B84F547ACF190C9C5@ad.redback.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
In-Reply-To: <6CB97876-3DB5-4355-9EC1-5599D71FF7D2@arbor.net>
Thread-Index: Acl0x5CYpgQlD7XoQHeqKPz7CtM3rAAE34CA
Cc: 'RRG' <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org


Hi Danny, 

|> I know that the internal tables are always a pain, but since 
|we have  
|> to deal
|> with the global issues, the internal, private growth (self- 
|> inflicted ;-) has
|> to necessarily be out of scope for RRG.
|
|That's quite odd to me, considering by today's definitions
|"internal [BGP] tables" are where the routing scalability and
|stability are it's worst - today, and unquestionably, the first
|place things will break IF/WHEN they do, as a result of an
|inter-domain routing protocol architecture that forces either
|full-mesh or hierarchies such as route reflection that themselves
|introduce additional paths and state in the network (even with
|implicit aggregation effects).


As you point out, this is more to do with the specific protocol than it is
to do with the overall routing architecture.  As such, this is why it's
really much more of the domain of IDR than RRG.

BTW, AFAIK, route reflection _reduces_ the number of paths as compared to
full-mesh IBGP.  Am I missing something?


|And they're not going to break because of a 100k unique
|internal-only routes, they're going to break because of
|an order or magnitude or more paths (and all of their overhead)
|- paths introduced as a result of "global issues" and solutions
|that focus on solely minimizing DFZ size, rather than looking
|at where the problem is actually worst - today.


Paths that are introduced for the sake of traffic engineering are a well
understood and self-inflicted problem.  If those folks that introduced the
extra paths took equivalent interest in limiting their dispersion and
cooperated in filtering unnecessary long prefixes, this could readily be
addressed.  In short, this is not an issue with the fundamental
architecture, it's about how the architecture is being used.  Thus, this is
largely an operational issue.  

Further, if we did something to fundamentally remove the capability to
traffic engineer in the future, I strongly suspect that that would be an
architectural issue, most likely fatal.

Regards,
Tony

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan 12 09:47:46 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BFB3228C0D7;
	Mon, 12 Jan 2009 09:47:46 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B645828C352
	for <rrg@core3.amsl.com>; Mon, 12 Jan 2009 09:47:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.563
X-Spam-Level: 
X-Spam-Status: No, score=-2.563 tagged_above=-999 required=5 tests=[AWL=0.036, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id kj9uIQCcjRh6 for <rrg@core3.amsl.com>;
	Mon, 12 Jan 2009 09:47:44 -0800 (PST)
Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.29])
	by core3.amsl.com (Postfix) with ESMTP id 84A193A683A
	for <rrg@irtf.org>; Mon, 12 Jan 2009 09:47:37 -0800 (PST)
Received: by yw-out-2324.google.com with SMTP id 3so4285305ywj.37
	for <rrg@irtf.org>; Mon, 12 Jan 2009 09:47:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:sender
	:to:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references
	:x-google-sender-auth;
	bh=WnMin9zN/14OPeinSApBOxgwlpmBU5IOOLLgau2UQ7E=;
	b=ZlItoWDgc+me1Qkoyh9GxNTuIG9t7QhEV78qqOLAkbpiCiCcMi9Lz38DgkuAS2P0a5
	svq7H/JSziERQ8aeoYRihhD5ZuhslZ0DrOWekMdegGTxgf5eBbzJhoLLZbsrzVPgwejI
	bsWlBKT7gWD31w5UPCKlrtLNKqsStahscw2zU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references:x-google-sender-auth;
	b=YK9sh+yMA0dStRpET6TvNZO/SOsiGDu8TI96cj+/9zJkWaoDfFo+U/kOtel/TrkfP2
	/DzkP3pH0kWQP5fWeegRtGFqnIalRTfP0uPYGe+fP6bdpnkdZXrLLvDoM6dIPetsxRB7
	9er/X4WuDhxLFlcv6iD8A6B0NmA1hT3TFCVAo=
Received: by 10.100.135.16 with SMTP id i16mr15674999and.99.1231782441307;
	Mon, 12 Jan 2009 09:47:21 -0800 (PST)
Received: by 10.100.120.5 with HTTP; Mon, 12 Jan 2009 09:47:21 -0800 (PST)
Message-ID: <75cb24520901120947h5e6055b5kbe024fc95ab649f5@mail.gmail.com>
Date: Mon, 12 Jan 2009 12:47:21 -0500
From: "Christopher Morrow" <morrowc.lists@gmail.com>
To: tony.li@tony.li
In-Reply-To: <BC8BF03B917B468B84F547ACF190C9C5@ad.redback.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com>
	<3525C9833C09ED418C6FD6CD9514668C0566045E@emailwf1.jnpr.net>
	<354C0AE786D1424C886C4A3570611291@ad.redback.com>
	<200901051509.n05F9nM02828@magenta.juniper.net>
	<DD2FDA0A88E84736AB1F3D25A3F61986@ad.redback.com>
	<4963C721.9080808@gmail.com>
	<75cb24520901061405m50a63533p86d77284b149d4cf@mail.gmail.com>
	<9FEF736036A74B148CC307D8FA35B720@ad.redback.com>
	<6CB97876-3DB5-4355-9EC1-5599D71FF7D2@arbor.net>
	<BC8BF03B917B468B84F547ACF190C9C5@ad.redback.com>
X-Google-Sender-Auth: e104ebc88d306e5d
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On Mon, Jan 12, 2009 at 12:34 PM, Tony Li <tony.li@tony.li> wrote:
>
> Hi Danny,
>
> |> I know that the internal tables are always a pain, but since
> |we have
> |> to deal
> |> with the global issues, the internal, private growth (self-
> |> inflicted ;-) has
> |> to necessarily be out of scope for RRG.
> |
> |That's quite odd to me, considering by today's definitions
> |"internal [BGP] tables" are where the routing scalability and
> |stability are it's worst - today, and unquestionably, the first
> |place things will break IF/WHEN they do, as a result of an
> |inter-domain routing protocol architecture that forces either
> |full-mesh or hierarchies such as route reflection that themselves
> |introduce additional paths and state in the network (even with
> |implicit aggregation effects).
>
>
> As you point out, this is more to do with the specific protocol than it is
> to do with the overall routing architecture.  As such, this is why it's
> really much more of the domain of IDR than RRG.
>

So, it's not that RRG doesn't acknowledge this problem, it's that the
problem ought to be fixed (to some extent at least) with the work RRG
is doing?

> |And they're not going to break because of a 100k unique
> |internal-only routes, they're going to break because of
> |an order or magnitude or more paths (and all of their overhead)
> |- paths introduced as a result of "global issues" and solutions
> |that focus on solely minimizing DFZ size, rather than looking
> |at where the problem is actually worst - today.
>
>
> Paths that are introduced for the sake of traffic engineering are a well
> understood and self-inflicted problem.  If those folks that introduced the

I don't think it's just 'traffic engineering' that is the problem
here, it's often other things like L3vpn/2547-vpn/mpls-vpn, 'internal
services' or 'service networks' (Peter's notes about phones on IP
roaming around the sprint core).

Surely TE prefixes are issues, but that's not the only source of
internal route growth... one large one is 'this IP thing, it's kinda
successful!' (convergence).

-Chris

(btw, I support the idea that RRG's work will 'fix this problem', my
original note was just to continue to raise awareness that the numbers
for route growth need to keep in mind that 285k prefixes globally is
often dwarfed by internal table sizes.)
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan 12 10:30:15 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BD7F23A6B2E;
	Mon, 12 Jan 2009 10:30:15 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EA3A43A6B28
	for <rrg@core3.amsl.com>; Mon, 12 Jan 2009 10:30:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.535
X-Spam-Level: 
X-Spam-Status: No, score=-2.535 tagged_above=-999 required=5 tests=[AWL=0.064, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id o4FzAHru8D0j for <rrg@core3.amsl.com>;
	Mon, 12 Jan 2009 10:30:14 -0800 (PST)
Received: from QMTA03.westchester.pa.mail.comcast.net
	(qmta03.westchester.pa.mail.comcast.net [76.96.62.32])
	by core3.amsl.com (Postfix) with ESMTP id E2F033A6B23
	for <rrg@irtf.org>; Mon, 12 Jan 2009 10:30:13 -0800 (PST)
Received: from OMTA06.westchester.pa.mail.comcast.net ([76.96.62.51])
	by QMTA03.westchester.pa.mail.comcast.net with comcast
	id 2frM1b00616LCl053iW0GK; Mon, 12 Jan 2009 18:30:00 +0000
Received: from TONYLTM9XP ([155.53.1.254])
	by OMTA06.westchester.pa.mail.comcast.net with comcast
	id 2iVW1b00J5Up7oj3SiVZKo; Mon, 12 Jan 2009 18:29:43 +0000
From: "Tony Li" <tony.li@tony.li>
To: "'Christopher Morrow'" <morrowc.lists@gmail.com>
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com>
	<3525C9833C09ED418C6FD6CD9514668C0566045E@emailwf1.jnpr.net>
	<354C0AE786D1424C886C4A3570611291@ad.redback.com>
	<200901051509.n05F9nM02828@magenta.juniper.net>
	<DD2FDA0A88E84736AB1F3D25A3F61986@ad.redback.com>
	<4963C721.9080808@gmail.com>
	<75cb24520901061405m50a63533p86d77284b149d4cf@mail.gmail.com>
	<9FEF736036A74B148CC307D8FA35B720@ad.redback.com>
	<6CB97876-3DB5-4355-9EC1-5599D71FF7D2@arbor.net>
	<BC8BF03B917B468B84F547ACF190C9C5@ad.redback.com>
	<75cb24520901120947h5e6055b5kbe024fc95ab649f5@mail.gmail.com>
Date: Mon, 12 Jan 2009 10:29:34 -0800
Message-ID: <465A9B59DF9C455A9772D70BD0AFD94B@ad.redback.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
In-Reply-To: <75cb24520901120947h5e6055b5kbe024fc95ab649f5@mail.gmail.com>
Thread-Index: Acl03dZgEzHaLEJKSY+miiItE2jPkwABVQ7g
Cc: 'RRG' <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org


Hi Chris,
 

|So, it's not that RRG doesn't acknowledge this problem, it's that the
|problem ought to be fixed (to some extent at least) with the work RRG
|is doing?


Yes, of course the problem exists, but again, it's more to be fixed within
IDR.  BGP is not an architecture; it's a protocol.  Protocol changes are in
scope for IDR and architecture changes are in scope for RRG.


|> Paths that are introduced for the sake of traffic 
|engineering are a well
|> understood and self-inflicted problem.  If those folks that 
|introduced the
|
|I don't think it's just 'traffic engineering' that is the problem
|here, it's often other things like L3vpn/2547-vpn/mpls-vpn, 'internal
|services' or 'service networks' (Peter's notes about phones on IP
|roaming around the sprint core).
|
|Surely TE prefixes are issues, but that's not the only source of
|internal route growth... one large one is 'this IP thing, it's kinda
|successful!' (convergence).


VPN prefixes are also wholly self-inflicted and have been well discussed as
a scalability issue for a decade or more.  No one is required to run VPNs,
so it's also a self-inflicted problem, just as if you decided to run DECnet.
;-)

Tony

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan 12 11:47:55 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AC2D63A699E;
	Mon, 12 Jan 2009 11:47:55 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 839193A699E
	for <rrg@core3.amsl.com>; Mon, 12 Jan 2009 11:47:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id fKwag6u5jbix for <rrg@core3.amsl.com>;
	Mon, 12 Jan 2009 11:47:53 -0800 (PST)
Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.242])
	by core3.amsl.com (Postfix) with ESMTP id 607973A6783
	for <rrg@irtf.org>; Mon, 12 Jan 2009 11:47:53 -0800 (PST)
Received: by an-out-0708.google.com with SMTP id c38so4776811ana.37
	for <rrg@irtf.org>; Mon, 12 Jan 2009 11:47:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:sender
	:to:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references
	:x-google-sender-auth;
	bh=/CaJt2eMWmzUb7bvLwvZ6hvMBo7dHSNxOBpCAld18Ec=;
	b=l1j5enTSSQ5M+K8HoSUtaImel1kN8ocLwbR/+0SMIL+E4SvJ+APC5YZxNm5hecUGdp
	Icp9PO055CkJe+PM3LoOjDno9Xtfn8ExBguePuQrAXl0kVgKVwmEeQCx42Lk7JjKR8A+
	uaa3N2yWtHbo2od4nfH9ZNmSgJa+FTwauiEdA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references:x-google-sender-auth;
	b=aUoVHq/4xlxRFjF++N3LbmwtvOyclOH8CZE0UESB1VRBxrTRzHg5wvZ6b8yMAPEOvz
	G6nV1gmWf+hICynR+KetZABIhwAOFBIwu2qQgEg6lc8ieWyCNZgkCASOluIeU3uP72FW
	1aNbT31DEDJavwcLN6ZYj1U1Z8bTiRSw6fHkU=
Received: by 10.100.153.6 with SMTP id a6mr15847165ane.76.1231789657672;
	Mon, 12 Jan 2009 11:47:37 -0800 (PST)
Received: by 10.100.120.5 with HTTP; Mon, 12 Jan 2009 11:47:37 -0800 (PST)
Message-ID: <75cb24520901121147o554fe390m5a86fda61d14d1b0@mail.gmail.com>
Date: Mon, 12 Jan 2009 14:47:37 -0500
From: "Christopher Morrow" <morrowc.lists@gmail.com>
To: tony.li@tony.li
In-Reply-To: <465A9B59DF9C455A9772D70BD0AFD94B@ad.redback.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com>
	<200901051509.n05F9nM02828@magenta.juniper.net>
	<DD2FDA0A88E84736AB1F3D25A3F61986@ad.redback.com>
	<4963C721.9080808@gmail.com>
	<75cb24520901061405m50a63533p86d77284b149d4cf@mail.gmail.com>
	<9FEF736036A74B148CC307D8FA35B720@ad.redback.com>
	<6CB97876-3DB5-4355-9EC1-5599D71FF7D2@arbor.net>
	<BC8BF03B917B468B84F547ACF190C9C5@ad.redback.com>
	<75cb24520901120947h5e6055b5kbe024fc95ab649f5@mail.gmail.com>
	<465A9B59DF9C455A9772D70BD0AFD94B@ad.redback.com>
X-Google-Sender-Auth: ecc902005051a584
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On Mon, Jan 12, 2009 at 1:29 PM, Tony Li <tony.li@tony.li> wrote:
>
> Hi Chris,
>
>
> |So, it's not that RRG doesn't acknowledge this problem, it's that the
> |problem ought to be fixed (to some extent at least) with the work RRG
> |is doing?
>
>
> Yes, of course the problem exists, but again, it's more to be fixed within
> IDR.  BGP is not an architecture; it's a protocol.  Protocol changes are in
> scope for IDR and architecture changes are in scope for RRG.
>

ugh, my wording was unclear, but I think we are agreeing. ok, all done :)

> |Surely TE prefixes are issues, but that's not the only source of
> |internal route growth... one large one is 'this IP thing, it's kinda
> |successful!' (convergence).
>
>
> VPN prefixes are also wholly self-inflicted and have been well discussed as
> a scalability issue for a decade or more.  No one is required to run VPNs,
> so it's also a self-inflicted problem, just as if you decided to run DECnet.
> ;-)

hrm.. 'self-inflicted'... we could have a long discussion about why
this IP thing has been successful, and how, and where it may go in the
future, and why things like vpn-routes are perhaps important to
that... but, like above, I think we agree that the problem could be
fixed with an architecture shift and that's the point of RRG.

Apologies for the 7 extra messages about internal/external prefixes
and sizing.  back to William's paper!

-Chris
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan 12 13:01:51 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9D8CD3A695E;
	Mon, 12 Jan 2009 13:01:51 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C05C73A67EC
	for <rrg@core3.amsl.com>; Mon, 12 Jan 2009 13:01:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id KCBJAZif3a1l for <rrg@core3.amsl.com>;
	Mon, 12 Jan 2009 13:01:49 -0800 (PST)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133])
	by core3.amsl.com (Postfix) with ESMTP id 46F7C3A68D0
	for <rrg@irtf.org>; Mon, 12 Jan 2009 13:01:39 -0800 (PST)
Received: by dog.tcb.net (Postfix, from userid 0)
	id B828B2684E9; Mon, 12 Jan 2009 14:01:25 -0700 (MST)
Received: from [192.168.0.100] (97-122-99-176.hlrn.qwest.net [97.122.99.176])
	(authenticated-user danny) (TLSv1/SSLv3 AES128-SHA 128/128)
	by dog.tcb.net with SMTP; Mon, 12 Jan 2009 14:01:25 -0700 (MST)
	(envelope-from danny@arbor.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=97.122.99.176;
	client-port=58040; syn-fingerprint=65535:55:1:64:M1316,N,W3,N,N,T,S;
	data-bytes=0
Message-Id: <4CE4C113-3212-40AB-944B-377399024722@arbor.net>
From: Danny McPherson <danny@arbor.net>
To: <tony.li@tony.li>
In-Reply-To: <BC8BF03B917B468B84F547ACF190C9C5@ad.redback.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Mon, 12 Jan 2009 14:01:24 -0700
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com>
	<3c3e3fca0901021219t2ab35dfsb2532e0c89be84af@mail.gmail.com>
	<E99E41EB33084B5B899C7EED9DE607E9@ad.redback.com>
	<3c3e3fca0901021334j22d17e54iec4bbf41b6c00480@mail.gmail.com>
	<BCFF32A1356842BF839C7DF7D059F15F@ad.redback.com>
	<3525C9833C09ED418C6FD6CD9514668C0566045E@emailwf1.jnpr.net>
	<354C0AE786D1424C886C4A3570611291@ad.redback.com>
	<200901051509.n05F9nM02828@magenta.juniper.net>
	<DD2FDA0A88E84736AB1F3D25A3F61986@ad.redback.com>
	<4963C721.9080808@gmail.com>
	<75cb24520901061405m50a63533p86d77284b149d4cf@mail.gmail.com>
	<9FEF736036A74B148CC307D8FA35B720@ad.redback.com>
	<6CB97876-3DB5-4355-9EC1-5599D71FF7D2@arbor.net>
	<BC8BF03B917B468B84F547ACF190C9C5@ad.redback.com>
X-Mailer: Apple Mail (2.930.3)
Cc: 'RRG' <rrg@irtf.org>
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org


On Jan 12, 2009, at 10:34 AM, Tony Li wrote:
>
>
> As you point out, this is more to do with the specific protocol than  
> it is
> to do with the overall routing architecture.  As such, this is why  
> it's
> really much more of the domain of IDR than RRG.

Well, so long as the folks designing the next generation
understand the problem and mitigate the constraints.  I'm
not totally sure the former is the case, which has effects
on the latter.

> BTW, AFAIK, route reflection _reduces_ the number of paths as  
> compared to
> full-mesh IBGP.  Am I missing something?

Depends on the number of RRs, where the best path
is, network architecture, etc..  The growth curves
I've seen (which I hope to be able to share soon)
illustrate that the number of iBGP paths is growing
at anywhere from 6-14x the rate of the DFZ, and
the reason is because of external factors, protocol
design issues, and implementations.

> Paths that are introduced for the sake of traffic engineering are a  
> well
> understood and self-inflicted problem.

Really?  So a multi-homed AS is TE?  So networks that interconnect
in 10 places result in 10 paths for each prefix and that's self-
inflicted?  What's the alternative to avoiding this self-inflicted
pain?

>  If those folks that introduced the
> extra paths took equivalent interest in limiting their dispersion and
> cooperated in filtering unnecessary long prefixes, this could  
> readily be
> addressed.

No, I'm not talking about just extraneous or covered prefixes,
that's only a tiny part of the problem I'm referring to.
Denseness of external interconnection, unique attributes,
BGP as defined today AND TE have effects on these, I'd say the
latter the least.

>  In short, this is not an issue with the fundamental
> architecture, it's about how the architecture is being used.  Thus,  
> this is
> largely an operational issue.

I don't agree with this.  Offer me an alternative for 10 or
more interconnections between the largest networks today?
Offer me an alternative for how those paths and the current
inter-domain routing protocol amplify (not minimize) the number
of paths.

> Further, if we did something to fundamentally remove the capability to
> traffic engineer in the future, I strongly suspect that that would  
> be an
> architectural issue, most likely fatal.

Again, TE is only a tiny part of the problem I'm referring
to here - fully dependent on ones definition of TE, of course.

-danny

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan 12 15:29:24 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 407B33A67FC;
	Mon, 12 Jan 2009 15:29:24 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 55A743A67FC
	for <rrg@core3.amsl.com>; Mon, 12 Jan 2009 15:29:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.78
X-Spam-Level: 
X-Spam-Status: No, score=-0.78 tagged_above=-999 required=5 tests=[AWL=0.422, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id XANevOAkABpY for <rrg@core3.amsl.com>;
	Mon, 12 Jan 2009 15:29:22 -0800 (PST)
Received: from imo-m20.mx.aol.com (imo-m20.mx.aol.com [64.12.137.1])
	by core3.amsl.com (Postfix) with ESMTP id 5BF733A67C0
	for <rrg@irtf.org>; Mon, 12 Jan 2009 15:29:21 -0800 (PST)
Received: from HeinerHummel@aol.com
	by imo-m20.mx.aol.com  (mail_out_v39.1.) id v.c34.4c620ba9 (41809);
	Mon, 12 Jan 2009 18:29:01 -0500 (EST)
From: HeinerHummel@aol.com
Message-ID: <c34.4c620ba9.369d2c3d@aol.com>
Date: Mon, 12 Jan 2009 18:29:01 EST
To: danny@arbor.net, tony.li@tony.li
MIME-Version: 1.0
X-Mailer: 9.0 SE for Windows sub 5021
Cc: rrg@irtf.org
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1964770565=="
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org


--===============1964770565==
Content-Type: multipart/alternative; boundary="-----------------------------1231802941"


-------------------------------1231802941
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

=20
Danny,
I agree with you. It is not ok to say "we have to solve this inter-domain =20
scalability problem and don't care/ don't want to mingle it with any =20
intra-domain scalability problem".
=20
You hilight another big point of TARA being an architecture which doesn't =20
depend on/doesn't need user reachability information dissemination at all -=20=
=20
neither of inter-domain prefixes nor of intra-domain prefixes.=20
Its advantages of a much faster next-hop look-up will result in a much =20
faster forwarding for the entire path, if the same mechanism is applied from=
 the =20
ingress intra-domain router to the egress-intra-domain router.
=20
Heiner
=20
=20
=20
=20
In einer eMail vom 12.01.2009 16:08:08 Westeurop=E4ische Normalzeit schreibt=
 =20
danny@arbor.net:

On Jan  6, 2009, at 4:23 PM, Tony Li wrote:
>
>
> I know that the  internal tables are always a pain, but since we have =20
> to  deal
> with the global issues, the internal, private growth (self- =20
> inflicted ;-) has
> to necessarily be out of scope for  RRG.

That's quite odd to me, considering by today's  definitions
"internal [BGP] tables" are where the routing scalability  and
stability are it's worst - today, and unquestionably, the  first
place things will break IF/WHEN they do, as a result of  an
inter-domain routing protocol architecture that forces  either
full-mesh or hierarchies such as route reflection that  themselves
introduce additional paths and state in the network (even  with
implicit aggregation effects).

And they're not going to break  because of a 100k unique
internal-only routes, they're going to break  because of
an order or magnitude or more paths (and all of their  overhead)
- paths introduced as a result of "global issues" and  solutions
that focus on solely minimizing DFZ size, rather than  looking
at where the problem is actually worst -  today.

-danny
_______________________________________________
rrg  mailing  list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg





-------------------------------1231802941
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3DISO-8859-1">
<META content=3D"MSHTML 6.00.6000.16788" name=3DGENERATOR></HEAD>
<BODY id=3Drole_body style=3D"FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY:=20=
Arial"=20
bottomMargin=3D7 leftMargin=3D7 topMargin=3D7 rightMargin=3D7><FONT id=3Drol=
e_document=20
face=3DArial color=3D#000000 size=3D2>
<DIV>
<DIV>Danny,</DIV>
<DIV>I agree with you. It is not ok to say "we have to solve this inter-doma=
in=20
scalability problem and don't care/ don't want to mingle it with any=20
intra-domain scalability problem".</DIV>
<DIV>&nbsp;</DIV>
<DIV>You hilight another big point of TARA being an architecture which doesn=
't=20
depend on/doesn't need user reachability information dissemination at all -=20
neither of inter-domain prefixes nor of intra-domain prefixes.&nbsp;</DIV>
<DIV>Its advantages of&nbsp;a much faster next-hop look-up will result in a=20=
much=20
faster forwarding for the entire path, if the same mechanism is applied from=
 the=20
ingress intra-domain router to the egress-intra-domain router.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Heiner</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>In einer eMail vom 12.01.2009 16:08:08 Westeurop=E4ische Normalzeit sch=
reibt=20
danny@arbor.net:</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid"><=
FONT=20
  style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000 size=
=3D2>On Jan=20
  6, 2009, at 4:23 PM, Tony Li wrote:<BR>&gt;<BR>&gt;<BR>&gt; I know that th=
e=20
  internal tables are always a pain, but since we have&nbsp; <BR>&gt; to=20
  deal<BR>&gt; with the global issues, the internal, private growth (self-=20
  <BR>&gt; inflicted ;-) has<BR>&gt; to necessarily be out of scope for=20
  RRG.<BR><BR>That's quite odd to me, considering by today's=20
  definitions<BR>"internal [BGP] tables" are where the routing scalability=20
  and<BR>stability are it's worst - today, and unquestionably, the=20
  first<BR>place things will break IF/WHEN they do, as a result of=20
  an<BR>inter-domain routing protocol architecture that forces=20
  either<BR>full-mesh or hierarchies such as route reflection that=20
  themselves<BR>introduce additional paths and state in the network (even=20
  with<BR>implicit aggregation effects).<BR><BR>And they're not going to bre=
ak=20
  because of a 100k unique<BR>internal-only routes, they're going to break=20
  because of<BR>an order or magnitude or more paths (and all of their=20
  overhead)<BR>- paths introduced as a result of "global issues" and=20
  solutions<BR>that focus on solely minimizing DFZ size, rather than=20
  looking<BR>at where the problem is actually worst -=20
  today.<BR><BR>-danny<BR>_______________________________________________<BR=
>rrg=20
  mailing=20
  list<BR>rrg@irtf.org<BR>http://www.irtf.org/mailman/listinfo/rrg<BR></FONT=
></BLOCKQUOTE></DIV>
<DIV></DIV>
<DIV>&nbsp;</DIV></FONT></BODY></HTML>

-------------------------------1231802941--

--===============1964770565==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

--===============1964770565==--


From rrg-bounces@irtf.org  Mon Jan 12 17:10:26 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 14BDF28C158;
	Mon, 12 Jan 2009 17:10:26 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E99FB3A67AD
	for <rrg@core3.amsl.com>; Mon, 12 Jan 2009 17:10:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.413
X-Spam-Level: 
X-Spam-Status: No, score=-6.413 tagged_above=-999 required=5 tests=[AWL=0.186, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id oFivenxvXWb5 for <rrg@core3.amsl.com>;
	Mon, 12 Jan 2009 17:10:22 -0800 (PST)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com
	[130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id 0436F3A6836
	for <rrg@irtf.org>; Mon, 12 Jan 2009 17:10:21 -0800 (PST)
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4])
	by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id n0D1A22g014374
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 12 Jan 2009 17:10:03 -0800 (PST)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1])
	by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	n0D1A2uC025014; Mon, 12 Jan 2009 17:10:02 -0800 (PST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	n0D1A2QZ025011; Mon, 12 Jan 2009 17:10:02 -0800 (PST)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 12 Jan 2009 17:10:02 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 12 Jan 2009 17:10:01 -0800
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1056AB1FC@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <8F620506-C2F2-41DE-BA3C-5FA63A028B27@nomadiclab.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Recursive re-encapsulations
Thread-Index: Acl01mDNnziHEYXuQuqmUyfuKeSG2QAONllA
References: <495F0BAA.2040303@firstpr.com.au><49611E83.8050301@gmail.com><4961CFD3.2050304@firstpr.com.au><D8D7E372-9EE5-4368-94EB-B8BC26AF0028@nomadiclab.com><20EEF623-B503-4994-B099-64715E567B2D@cisco.com><474EEBD229DF754FB83D256004D021080AD5E539@XCH-NW-6V1.nw.nos.boeing.com><39C363776A4E8C4A94691D2BD9D1C9A105623AC3@XCH-NW-7V2.nw.nos.boeing.com>
	<96CDEE57-28F3-416C-8AAD-D3F7330B3C5A@nomadiclab.com>
	<77F357662F8BFA4CA7074B0410171B6D07B0BC42@XCH-NW-5V1.nw.nos.boeing.com>
	<39C363776A4E8C4A94691D2BD9D1C9A10566DB53@XCH-NW-7V2.nw.nos.boeing.com>
	<C83DB85A-CE29-4288-87F8-07447C2DF862@nomadiclab.com>
	<39C363776A4E8C4A94691D2BD9D1C9A10566DF39@XCH-NW-7V2.nw.nos.boeing.com>
	<695CF996-623A-40FA-B349-0162A72374D7@nomadiclab.com>
	<39C363776A4E8C4A94691D2BD9D1C9A10566E3D9@XCH-NW-7V2.nw.nos.boeing.com>
	<BBEA3D1B-47DC-4003-B300-9F61A45F6775@nomadiclab.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1056AAC35@XCH-NW-7V2.nw.nos.boeing.com>
	<8F620506-C2F2-41DE-BA3C-5FA63A028B27@nomadiclab.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Pekka Nikander" <pekka.nikander@nomadiclab.com>
X-OriginalArrivalTime: 13 Jan 2009 01:10:02.0427 (UTC)
	FILETIME=[A973B8B0:01C9751B]
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] Recursive re-encapsulations
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Pekka,

>-----Original Message-----
>From: Pekka Nikander [mailto:pekka.nikander@nomadiclab.com]
>Sent: Monday, January 12, 2009 8:46 AM
>To: Templin, Fred L
>Cc: RRG
>Subject: Re: Recursive re-encapsulations
>
>>> However, if we aim for the kind of hybrid LISP-HIP-proxy design that
>>> I've been suggesting, I believe that the packet formats could be
much
>>> simpler.
>>
>> I'm not exactly sure how; xTR means IP-in-IP encapsulation.
>> Were you meaning for it to mean something else?
>
>What I have been trying to describe is taking the LISP architecture
>and then replacing some parts of the xTR functionality with proxy-HIP.
>
>> With RANGER/VET/SEAL, I am looking for a way for the ITR to
>> establish sufficient securing state in the ETR through a single
>> message sent forward before any data messages are sent (i.e.,
>> a "1-way handshake"). Can HIP do that?
>
>Depends on your security requirements and what you store in your
>mapping system.
>
>A very short answer is that if you care about all the security threats
>HIP cares about, then if the ETR stores the HIP puzzle into the
>mapping system so that the ITR gets the puzzle along the ETR RLOC,
>then HIP can do that.

With RANGER, I was thinking that the ITR could send an
IPv6 Router Advertisement using SEND forward to the ETR and
then just start admitting packets into the tunnel. The ETR
will verify the credentials in the RA (e.g., by checking in
the mapping system, by consulting a certificate authority,
etc.) and set an ingress filter entry if the credentials
check out. The ETR can then start accepting packets from
the ITR.

If the ITR's credentials don't check out, the ETR will
instead drop packets and send back rate-limited ICMP
"Destination Unreachable; Administratively Prohibited"
messages. The ITR can then use SEAL as a loose method of
authenticating the ICMP messages, and can try again to
establish the ingress filter if it thinks it has the
correct credentials.

Does that match the model you were thinking of?

Thanks - Fred
fred.l.templin@boeing.com


>--Pekka

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan 12 19:35:24 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B86D73A69D1;
	Mon, 12 Jan 2009 19:35:24 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 891753A69D1
	for <rrg@core3.amsl.com>; Mon, 12 Jan 2009 19:35:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.098
X-Spam-Level: 
X-Spam-Status: No, score=-1.098 tagged_above=-999 required=5 tests=[AWL=1.186, 
	BAYES_00=-2.599, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id EAZQbYJt5k2r for <rrg@core3.amsl.com>;
	Mon, 12 Jan 2009 19:35:22 -0800 (PST)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67])
	by core3.amsl.com (Postfix) with ESMTP id 5AC533A67FF
	for <rrg@irtf.org>; Mon, 12 Jan 2009 19:35:22 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12])
	by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0KDE00KNH4MEAY@szxga04-in.huawei.com> for
	rrg@irtf.org; Tue, 13 Jan 2009 11:35:02 +0800 (CST)
Received: from x41208a ([10.111.12.103])
	by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0KDE00KV64MD49@szxga04-in.huawei.com> for
	rrg@irtf.org; Tue, 13 Jan 2009 11:35:02 +0800 (CST)
Date: Tue, 13 Jan 2009 11:35:01 +0800
From: Xu Xiaohu <xuxh@huawei.com>
In-reply-to: <77F357662F8BFA4CA7074B0410171B6D07B0BC78@XCH-NW-5V1.nw.nos.boeing.com>
To: "'Henderson, Thomas R'" <thomas.r.henderson@boeing.com>,
	'Oleg Ponomarev' <oleg.ponomarev@hiit.fi>
Message-id: <000a01c9752f$eaddffe0$670c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Mailer: Microsoft Office Outlook 11
Thread-index: Acl09c/J4vcDfFHYR6WH1nnr6p4n3gAAYA8gAA2L+iA=
Cc: 'RRG' <rrg@irtf.org>, hipsec-rg@listserv.cybertrust.com
Subject: Re: [rrg] [Hipsec-rg] reverse DNS lookups of HITs
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org


[Note: This email is also copied to RRG, I believe some RRGer will also have
interest on it. If not, sorry for disturbing you.]

> > When HIP gets widely deployed and there are millions of users, we 
> > might hope to use more resources :)
> > 
> 
> This type of question is precisely what this research group's 
> primary charter is to answer, in my opinion.  What are the 
> consequences of deploying HIP on a large scale in the 
> Internet?  If it means that we will have a few root servers 
> handling reverse DNS queries for all hosts, without any 
> aggregation, how will that architecture scale, and how will 
> the deployment incentives work?  

Hi Tom,

That's why I suggested the flat HIT should be modified to have some
structure during the IETF72 meeting. The thread is as follows:

https://listserv.cybertrust.com/pipermail/hipsec-rg/2008-July/000509.html

Xiaohu

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Tue Jan 13 07:56:54 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5220F3A67FF;
	Tue, 13 Jan 2009 07:56:54 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D96843A67D7
	for <rrg@core3.amsl.com>; Tue, 13 Jan 2009 07:56:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id eKlE-W61f2Y7 for <rrg@core3.amsl.com>;
	Tue, 13 Jan 2009 07:56:52 -0800 (PST)
Received: from smtp1.NoDak.edu (smtp1.NoDak.edu [134.129.111.50])
	by core3.amsl.com (Postfix) with ESMTP id 9D8403A67FF
	for <rrg@irtf.org>; Tue, 13 Jan 2009 07:56:52 -0800 (PST)
Received: from netmender.cc.ndsu.NoDak.edu (netmender.cc.ndsu.NoDak.edu
	[134.129.95.120]) (authenticated bits=0)
	by smtp1.NoDak.edu (8.13.1/8.13.1) with ESMTP id n0DFuBko021520
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO)
	for <rrg@irtf.org>; Tue, 13 Jan 2009 09:56:13 -0600
Message-Id: <120811DD-53AB-4EF6-85DD-87639197DF5A@ndsu.edu>
From: Bruce Curtis <bruce.curtis@ndsu.edu>
To: RRG <rrg@irtf.org>
In-Reply-To: <1D471F7666CB4482A947C3D07CC04C1F@ad.redback.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Tue, 13 Jan 2009 09:56:09 -0600
References: <3c3e3fca0812311340o6bd1d335ucb18e391a9fbd621@mail.gmail.com>
	<75cb24520812311427m31d4dae0nd5c37130cc485eaf@mail.gmail.com>
	<3c3e3fca0812311524o36bf8ae5k6837b7d15813685e@mail.gmail.com>
	<75cb24520812311536u6930dcd7o65394ae000c7b5f6@mail.gmail.com>
	<1D471F7666CB4482A947C3D07CC04C1F@ad.redback.com>
X-Mailer: Apple Mail (2.929.2)
Subject: Re: [rrg] BGP scaling limit?
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org


   One of the limits discussed in this thread was that the performance  
of DRAM will be limited by it's dependence on capacitors.

   While Floating Body Memory isn't yet mainstream and can't yet be  
counted on to solve future problems I was surprised that it wasn't at  
least mentioned.


   http://www.spectrum.ieee.org/oct08/6868

   http://en.wikipedia.org/wiki/Z-RAM

   http://en.wikipedia.org/wiki/TTRAM

   http://www.spectrum.ieee.org/jan07/4839

   http://www.innovativesilicon.com/technology_overview.php

   http://www.innovativesilicon.com/technology_benefits.php

   http://www.innovativesilicon.com/  (watch video overview)

   http://www.eetimes.com/showArticle.jhtml;jsessionid=BP5AO2PNJBYIEQSNDLOSKH0CJUNN2JVN?articleID=210604764


---
Bruce Curtis                         bruce.curtis@ndsu.edu
Certified NetAnalyst II                701-231-8527
North Dakota State University

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan 15 10:42:44 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BAFCC28C294;
	Thu, 15 Jan 2009 10:42:44 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D02CF28C294;
	Thu, 15 Jan 2009 10:42:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.169
X-Spam-Level: 
X-Spam-Status: No, score=-6.169 tagged_above=-999 required=5
	tests=[AWL=-0.170, BAYES_00=-2.599, J_CHICKENPOX_34=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id CUzwxX5tdq59; Thu, 15 Jan 2009 10:42:42 -0800 (PST)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com
	[130.76.96.56])
	by core3.amsl.com (Postfix) with ESMTP id A81DA28C278;
	Thu, 15 Jan 2009 10:42:42 -0800 (PST)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6])
	by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id n0FIgEi1001873
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Thu, 15 Jan 2009 12:42:14 -0600 (CST)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	n0FIgEU9000698; Thu, 15 Jan 2009 12:42:14 -0600 (CST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	n0FIgBCE000572; Thu, 15 Jan 2009 12:42:14 -0600 (CST)
Received: from XCH-NW-6V1.nw.nos.boeing.com ([130.247.55.53]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 15 Jan 2009 10:42:13 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 15 Jan 2009 10:42:12 -0800
Message-ID: <474EEBD229DF754FB83D256004D021080AE7ACF9@XCH-NW-6V1.nw.nos.boeing.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: No liveness requirement in the ID/Loc Split concept
Thread-Index: Acl3QPrVUmF2Ehb1QAOVLgoB8peYCQ==
From: "Fleischman, Eric" <eric.fleischman@boeing.com>
To: <lisp@ietf.org>
X-OriginalArrivalTime: 15 Jan 2009 18:42:13.0377 (UTC)
	FILETIME=[FB41B710:01C97740]
Cc: rrg@irtf.org
Subject: [rrg] No liveness requirement in the ID/Loc Split concept
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Coworkers,

In response to the draft-meyer-loc-id-implications-00.txt I-D, I sent
private observations to the authors of that I-D together with a small
subset of interested parties. Somebody (Dave Meyer??) requested that
this private dialog should rather be moved to this email list for
participation of the larger community. Towards that end, I would like to
summarize the view from my knothole about the RLOC/EID split issue to
this list:

1) Routing systems using RLOCs naturally reference RLOCs for routing
aggregation. Every network system that I have worked with except for IP
(e.g., OSI, SNA, BSC, XNS, etc.) instead does routing on EIDs. These
latter systems do not recognize RLOCs.

2) In historic IP, IP addresses became semantically overloaded with both
RLOC and EID semantics. I surmise that the IP designers originally
thought they were doing EIDs like every other protocol then existing but
they actually invented RLOCs, without recognizing the implications of
the difference. Regardless, both semantic concepts became located within
the IP layer. In practice this meant that EIDs were not operative for IP
routing at all: EID is usually NULL for traditional IP routing; EID
primarily semantically appears for protocols operating above the IP
layer, causing cross-layer protocol dependencies in such systems. 

3) IP combined the RLOC and EID concepts into a single system that
lacked the ability to disambiguate between them. Consequently, some
systems (e.g., routing) presumed that they were talking with an RLOC and
other systems presumed that they were talking with an EID. The IP system
didn't provide any assurance that either reference or presumption was
actually the case (e.g., anycast). This became known as the "IP identity
problem", which is a fundamental and pervasive security flaw within IP
systems that is solved by the RLOC/EID split concept (e.g., HIP). Within
historic IP we either locate something without identifying it or else we
identify it without locating it. This provides the foundation for
"Rekhter's Law". That we cannot authoritatively know which reference is
operative provides the foundation for the "IP identity problem".

4) Multihoming is an EID concept. EID-based routing systems naturally
and transparently support multihoming. RLOC-based routing systems cannot
naturally support multihoming because they lack the information to be
able to naturally recognize the occurrence of multihoming.

5) In RLOC/EID separation systems like HIP, the RLOC and EID each occurs
on different layers of the protocol stack. Therefore, attempting to get
IP routing, which works on the IP layer (i.e., RLOC layer) to be aware
of multi-homing, which occurs on the EID layer (i.e., the session layer
within HIP), is a protocol layer violation.

6) IP routing is not equipped to natively be able to do multi-homing and
attempts to enhance it to do so further complicate the RLOC-EID
confusion and actively harm the Internet. Attempting to enhance routers
to handle multi-homing inherently violates the loc/ID split concept. The
desired distinction between EID and RLOC needlessly becomes replaced by
mutual dependencies between the two concepts. By adding EID dependencies
to RLOC, there cannot be "better aggregation in the RLOC space" because
no RLOC space can exist. Rather, that space potentially becomes EID*RLOC
space, which probably represents significantly worse aggregation than
the historic IP routing system.

7) The RLOC-EID split concept therefore means that multihoming needs to
be solved at a layer above the IP layer that can naturally see the EID.
Attempts to simultaneously achieve a Loc/Id split and have routing doing
multihoming are vectors that internally war with each other. The net
result are the types of problems identified in
draft-meyer-loc-id-implications-00.txt, problems that cannot occur if
the RLOC-EID distinction is done properly (i.e., RLOC and EID at
different layers of the protocol stack).

8) When RLOC-EID is done properly (e.g., like HIP where each concept
appears on a different layer of the protocol stack), there is no
liveness problem (nor can there be one). Rather, the "liveness problem"
described in draft-meyer-loc-id-implications-00.txt is a generic problem
of map-and-encaps systems, not of RLOC-EID. The title and text of
draft-meyer-loc-id-implications-00.txt is therefore inappropriately
scoped as being caused by RLOC-EID when it is rather a common attribute
of map-and-encaps. Note that LISP is a map-and-encaps system.

9) It is useful to discuss both map-and-encaps and multihoming from the
insights contained within Fred Templin's VET/RANGER/SEAL I-D trilogy.
This trilogy discusses scalable map-and-encaps systems and indicates how
to resolve the liveness problem for those systems. It also provides an
important context for describing multihoming because it identifies the
recursive nature of the "enterprise" concept. Without leveraging the
insights of this trilogy, multihoming may appear to mean different
things in different contexts: Autonomous systems can be multihomed.
Mobile platforms can be multihomed. Hosts can be multihomed. Etc. These
different environments are recursive instances to different sized
"enterprise" entities. Failing to realize this complicates discussions
about multi-homing.

--Eric


_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan 15 10:48:43 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DBEEF3A6823;
	Thu, 15 Jan 2009 10:48:43 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 579363A6823;
	Thu, 15 Jan 2009 10:48:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.118
X-Spam-Level: 
X-Spam-Status: No, score=-6.118 tagged_above=-999 required=5
	tests=[AWL=-0.119, BAYES_00=-2.599, J_CHICKENPOX_34=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id tiPevTw0QMWF; Thu, 15 Jan 2009 10:48:41 -0800 (PST)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com
	[130.76.32.69])
	by core3.amsl.com (Postfix) with ESMTP id 3DB093A6774;
	Thu, 15 Jan 2009 10:48:41 -0800 (PST)
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4])
	by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id n0FImHl4028153
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 15 Jan 2009 10:48:21 -0800 (PST)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1])
	by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	n0FImHsd013430; Thu, 15 Jan 2009 10:48:17 -0800 (PST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	n0FImF5Z013349; Thu, 15 Jan 2009 10:48:17 -0800 (PST)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 15 Jan 2009 10:48:16 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 15 Jan 2009 10:48:15 -0800
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1056E76B6@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <474EEBD229DF754FB83D256004D021080AE7ACF9@XCH-NW-6V1.nw.nos.boeing.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] No liveness requirement in the ID/Loc Split concept
Thread-Index: Acl3QPrVUmF2Ehb1QAOVLgoB8peYCQAAGgBg
References: <474EEBD229DF754FB83D256004D021080AE7ACF9@XCH-NW-6V1.nw.nos.boeing.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Fleischman, Eric" <eric.fleischman@boeing.com>, <lisp@ietf.org>
X-OriginalArrivalTime: 15 Jan 2009 18:48:16.0488 (UTC)
	FILETIME=[D3B00E80:01C97741]
Cc: rrg@irtf.org
Subject: Re: [rrg] No liveness requirement in the ID/Loc Split concept
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Eric,

>-----Original Message-----
>From: Fleischman, Eric
>Sent: Thursday, January 15, 2009 10:42 AM
>To: lisp@ietf.org
>Cc: rrg@irtf.org
>Subject: [rrg] No liveness requirement in the ID/Loc Split concept
>
>Coworkers,
>
>In response to the draft-meyer-loc-id-implications-00.txt I-D, I sent
>private observations to the authors of that I-D together with a small
>subset of interested parties. Somebody (Dave Meyer??) requested that
>this private dialog should rather be moved to this email list for
>participation of the larger community. Towards that end, I would like
to
>summarize the view from my knothole about the RLOC/EID split issue to
>this list:
>
>1) Routing systems using RLOCs naturally reference RLOCs for routing
>aggregation. Every network system that I have worked with except for IP
>(e.g., OSI, SNA, BSC, XNS, etc.) instead does routing on EIDs. These
>latter systems do not recognize RLOCs.
>
>2) In historic IP, IP addresses became semantically overloaded with
both
>RLOC and EID semantics. I surmise that the IP designers originally
>thought they were doing EIDs like every other protocol then existing
but
>they actually invented RLOCs, without recognizing the implications of
>the difference. Regardless, both semantic concepts became located
within
>the IP layer. In practice this meant that EIDs were not operative for
IP
>routing at all: EID is usually NULL for traditional IP routing; EID
>primarily semantically appears for protocols operating above the IP
>layer, causing cross-layer protocol dependencies in such systems.
>
>3) IP combined the RLOC and EID concepts into a single system that
>lacked the ability to disambiguate between them. Consequently, some
>systems (e.g., routing) presumed that they were talking with an RLOC
and
>other systems presumed that they were talking with an EID. The IP
system
>didn't provide any assurance that either reference or presumption was
>actually the case (e.g., anycast). This became known as the "IP
identity
>problem", which is a fundamental and pervasive security flaw within IP
>systems that is solved by the RLOC/EID split concept (e.g., HIP).
Within
>historic IP we either locate something without identifying it or else
we
>identify it without locating it. This provides the foundation for
>"Rekhter's Law". That we cannot authoritatively know which reference is
>operative provides the foundation for the "IP identity problem".
>
>4) Multihoming is an EID concept. EID-based routing systems naturally
>and transparently support multihoming. RLOC-based routing systems
cannot
>naturally support multihoming because they lack the information to be
>able to naturally recognize the occurrence of multihoming.
>
>5) In RLOC/EID separation systems like HIP, the RLOC and EID each
occurs
>on different layers of the protocol stack. Therefore, attempting to get
>IP routing, which works on the IP layer (i.e., RLOC layer) to be aware
>of multi-homing, which occurs on the EID layer (i.e., the session layer
>within HIP), is a protocol layer violation.
>
>6) IP routing is not equipped to natively be able to do multi-homing
and
>attempts to enhance it to do so further complicate the RLOC-EID
>confusion and actively harm the Internet. Attempting to enhance routers
>to handle multi-homing inherently violates the loc/ID split concept.
The
>desired distinction between EID and RLOC needlessly becomes replaced by
>mutual dependencies between the two concepts. By adding EID
dependencies
>to RLOC, there cannot be "better aggregation in the RLOC space" because
>no RLOC space can exist. Rather, that space potentially becomes
EID*RLOC
>space, which probably represents significantly worse aggregation than
>the historic IP routing system.
>
>7) The RLOC-EID split concept therefore means that multihoming needs to
>be solved at a layer above the IP layer that can naturally see the EID.
>Attempts to simultaneously achieve a Loc/Id split and have routing
doing
>multihoming are vectors that internally war with each other. The net
>result are the types of problems identified in
>draft-meyer-loc-id-implications-00.txt, problems that cannot occur if
>the RLOC-EID distinction is done properly (i.e., RLOC and EID at
>different layers of the protocol stack).
>
>8) When RLOC-EID is done properly (e.g., like HIP where each concept
>appears on a different layer of the protocol stack), there is no
>liveness problem (nor can there be one). Rather, the "liveness problem"
>described in draft-meyer-loc-id-implications-00.txt is a generic
problem
>of map-and-encaps systems, not of RLOC-EID. The title and text of
>draft-meyer-loc-id-implications-00.txt is therefore inappropriately
>scoped as being caused by RLOC-EID when it is rather a common attribute
>of map-and-encaps. Note that LISP is a map-and-encaps system.
>
>9) It is useful to discuss both map-and-encaps and multihoming from the
>insights contained within Fred Templin's VET/RANGER/SEAL I-D trilogy.
>This trilogy discusses scalable map-and-encaps systems and indicates
how
>to resolve the liveness problem for those systems. It also provides an
>important context for describing multihoming because it identifies the
>recursive nature of the "enterprise" concept. Without leveraging the
>insights of this trilogy, multihoming may appear to mean different
>things in different contexts: Autonomous systems can be multihomed.
>Mobile platforms can be multihomed. Hosts can be multihomed. Etc. These
>different environments are recursive instances to different sized
>"enterprise" entities. Failing to realize this complicates discussions
>about multi-homing.

FWIW, this is completely consistent with the latest version of
VET that I have just posted:

http://www.ietf.org/internet-drafts/draft-templin-autoconf-dhcp-27.txt

but I think you will find that the new version is much more
comprehensive in terms of PI addressing, site multi-homing,
ingress filtering, routing scaling suppression, MTU robustness,
locator liveness determination, etc. etc.)

Thanks - Fred
fred.l.templin@boeing.com

>
>--Eric
>
>
>_______________________________________________
>rrg mailing list
>rrg@irtf.org
>http://www.irtf.org/mailman/listinfo/rrg
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan 15 10:56:18 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AF8413A6774;
	Thu, 15 Jan 2009 10:56:18 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B2D4A3A6778;
	Thu, 15 Jan 2009 10:56:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[AWL=0.113, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id k4vAAeD+pqZj; Thu, 15 Jan 2009 10:56:16 -0800 (PST)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9])
	by core3.amsl.com (Postfix) with ESMTP id 138AF3A6774;
	Thu, 15 Jan 2009 10:56:16 -0800 (PST)
Received: from m106.maoz.com (localhost [127.0.0.1])
	by m106.maoz.com (8.14.3/8.14.3/Debian-4) with ESMTP id n0FIu09P020124; 
	Thu, 15 Jan 2009 10:56:00 -0800
Received: (from dmm@localhost)
	by m106.maoz.com (8.14.3/8.14.3/Submit) id n0FIu01U020123;
	Thu, 15 Jan 2009 10:56:00 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using
	-f
Date: Thu, 15 Jan 2009 10:56:00 -0800
From: David Meyer <dmm@1-4-5.net>
To: "Fleischman, Eric" <eric.fleischman@boeing.com>
Message-ID: <20090115185600.GA20104@1-4-5.net>
References: <474EEBD229DF754FB83D256004D021080AE7ACF9@XCH-NW-6V1.nw.nos.boeing.com>
MIME-Version: 1.0
In-Reply-To: <474EEBD229DF754FB83D256004D021080AE7ACF9@XCH-NW-6V1.nw.nos.boeing.com>
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-gpg-fingerprint: 2409 8B50 B389 A307 BA5C 2A16 3918 03D6 A099 D8A7
X-philosophy: "I just had to let it go. John Lennon"
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: rrg@irtf.org, lisp@ietf.org
Subject: Re: [rrg] No liveness requirement in the ID/Loc Split concept
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0803731224=="
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org


--===============0803731224==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="YiEDa0DAkWCtVeE4"
Content-Disposition: inline


--YiEDa0DAkWCtVeE4
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

> subset of interested parties. Somebody (Dave Meyer??) requested that

	Guilty :-)

	But seriously, thanks Eric.


	Dave

--YiEDa0DAkWCtVeE4
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAklvhsAACgkQORgD1qCZ2KfjLQCfbsDTijzt4oy+IkLj8guFl/Bt
WOAAoIT2FPd07Qg6eGneGi3h6+YLjIDr
=h8u5
-----END PGP SIGNATURE-----

--YiEDa0DAkWCtVeE4--

--===============0803731224==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

--===============0803731224==--


From rrg-bounces@irtf.org  Thu Jan 15 11:32:43 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2D2F93A6A41;
	Thu, 15 Jan 2009 11:32:43 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AE1ED3A6A74
	for <rrg@core3.amsl.com>; Thu, 15 Jan 2009 11:32:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.215
X-Spam-Level: 
X-Spam-Status: No, score=-6.215 tagged_above=-999 required=5
	tests=[AWL=-0.216, BAYES_00=-2.599, J_CHICKENPOX_34=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id HiDYHnlwSi8E for <rrg@core3.amsl.com>;
	Thu, 15 Jan 2009 11:32:41 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 4F86D3A6A41
	for <rrg@irtf.org>; Thu, 15 Jan 2009 11:32:41 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,272,1231113600"; d="scan'208";a="33927483"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 15 Jan 2009 19:32:10 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n0FJWAGv003456; 
	Thu, 15 Jan 2009 14:32:10 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n0FJWAD7000377;
	Thu, 15 Jan 2009 19:32:10 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 15 Jan 2009 14:32:10 -0500
Received: from cisco.com ([64.102.8.172]) by xfe-rtp-201.amer.cisco.com with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 15 Jan 2009 14:32:10 -0500
Date: Thu, 15 Jan 2009 14:32:05 -0500
From: Scott Brim <swb@employees.org>
To: "Fleischman, Eric" <eric.fleischman@boeing.com>
Message-ID: <20090115193205.GA49353@cisco.com>
Mail-Followup-To: Scott Brim <swb@employees.org>,
	"Fleischman, Eric" <eric.fleischman@boeing.com>, lisp@ietf.org,
	rrg@irtf.org
References: <474EEBD229DF754FB83D256004D021080AE7ACF9@XCH-NW-6V1.nw.nos.boeing.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <474EEBD229DF754FB83D256004D021080AE7ACF9@XCH-NW-6V1.nw.nos.boeing.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-OriginalArrivalTime: 15 Jan 2009 19:32:10.0305 (UTC)
	FILETIME=[F590A310:01C97747]
Authentication-Results: rtp-dkim-1; header.From=swb@employees.org; dkim=neutral
Cc: rrg@irtf.org, lisp@ietf.org
Subject: Re: [rrg] No liveness requirement in the ID/Loc Split concept
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Excerpts from Fleischman, Eric on Thu, Jan 15, 2009 10:42:12AM -0800:
> 5) In RLOC/EID separation systems like HIP, the RLOC and EID each occurs
> on different layers of the protocol stack. Therefore, attempting to get
> IP routing, which works on the IP layer (i.e., RLOC layer) to be aware
> of multi-homing, which occurs on the EID layer (i.e., the session layer
> within HIP), is a protocol layer violation.

Nor should it.  IP routing itself should deal with finding paths to
destinations (and forwarding should deal with forwarding individual
packets).  Determining that that sending to either of two apparently
different destinations gets the packet to the same higher layer entity
has nothing to do with routing.

> 6) IP routing is not equipped to natively be able to do multi-homing
> and attempts to enhance it to do so further complicate the RLOC-EID
> confusion and actively harm the Internet. Attempting to enhance
> routers to handle multi-homing inherently violates the loc/ID split
> concept. The desired distinction between EID and RLOC needlessly
> becomes replaced by mutual dependencies between the two concepts. By
> adding EID dependencies to RLOC, there cannot be "better aggregation
> in the RLOC space" because no RLOC space can exist. Rather, that
> space potentially becomes EID*RLOC space, which probably represents
> significantly worse aggregation than the historic IP routing system.

However, map-and-encap adds a new control and OAM relationship,
between the "funnel" ingress and egress points.  These are beyond the
knowledge or control of endpoints, yet they promise to deliver
packets, therefore they have a responsibility to find and use viable
paths.  They are not _just_ routers at this point.  They are also
endpoints in their own right.  They are doing more than discovering
paths and forwarding packets.  Since _sites_ have multiple ingress
points, multihoming applies here too, they have a responsibility to
handle multihoming just as endpoint stacks do.  Even if the session
endpoints are already taking care of multihoming themselves, they are
only capable of doing so over the choices that are given to them by
the "funnel" endpoints.  I don't think you can say the endpoints
should take care of everything -- they can't.  Anymore than the
endpoints take care of everything when running over any underlying
switched network.

But the "funnel" endpoints do not know enough about what the session
endpoints want or need -- is the endpoint already taking care of
multipathing?  Does it require session continuity and thus must have
backup paths lined up at all times?  And so on.  Therefore the funnel
endpoints overdo their responsibility.

It's clear that pure endpoint-based multipathing, =E0 la Shim6 REAP,
cannot scale.  Putting path failure detection and recovery in ITRs
instead of in the endpoints can greatly reduce the number of messages
flying around, but a simple approach there doesn't scale either, and
without information they don't have much choice.  =


One thing we could do is to couple them.  The endpoint could
periodically tell "the network" what it needs, so the network only
needs to do just enough.  =


Another thing we can do is cut back on our requirements, at least for
a while.

> 7) The RLOC-EID split concept therefore means that multihoming needs to
> be solved at a layer above the IP layer that can naturally see the EID.
> Attempts to simultaneously achieve a Loc/Id split and have routing doing
> multihoming are vectors that internally war with each other. The net
> result are the types of problems identified in
> draft-meyer-loc-id-implications-00.txt, problems that cannot occur if
> the RLOC-EID distinction is done properly (i.e., RLOC and EID at
> different layers of the protocol stack).
> =

> 8) When RLOC-EID is done properly (e.g., like HIP where each concept
> appears on a different layer of the protocol stack), there is no
> liveness problem (nor can there be one). Rather, the "liveness problem"
> described in draft-meyer-loc-id-implications-00.txt is a generic problem
> of map-and-encaps systems, not of RLOC-EID. The title and text of
> draft-meyer-loc-id-implications-00.txt is therefore inappropriately
> scoped as being caused by RLOC-EID when it is rather a common attribute
> of map-and-encaps. Note that LISP is a map-and-encaps system.

I don't see it.  HIP properly removes dependency on location-based
names from identification functions, but it does nothing to solve the
multipath problem.  You still need to find viable paths, ascertain
that multiple locators refer to the same entity (difficult when one or
both are moving -- rendezvous servers may be required, tsk), detect
path failure and switch to another one.  The same is true for Shim6,
or Trilogy multipathing ... or anything where you have the chance of
using multiple paths.  A simple host in a simple PI-based AS can't,
and therefore doesn't have a problem to solve.  Adding HIP in fact
makes the problem possible.

> 9) It is useful to discuss both map-and-encaps and multihoming from the
> insights contained within Fred Templin's VET/RANGER/SEAL I-D trilogy.
> This trilogy discusses scalable map-and-encaps systems and indicates how
> to resolve the liveness problem for those systems. It also provides an
> important context for describing multihoming because it identifies the
> recursive nature of the "enterprise" concept. Without leveraging the
> insights of this trilogy, multihoming may appear to mean different
> things in different contexts: Autonomous systems can be multihomed.
> Mobile platforms can be multihomed. Hosts can be multihomed. Etc. These
> different environments are recursive instances to different sized
> "enterprise" entities. Failing to realize this complicates discussions
> about multi-homing.

I'm partway through them.  Sorry for not being able to respond about
this part.

Scott
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan 15 11:36:41 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 667EF3A69EB;
	Thu, 15 Jan 2009 11:36:41 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9C6853A69F6
	for <rrg@core3.amsl.com>; Thu, 15 Jan 2009 11:36:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.564
X-Spam-Level: 
X-Spam-Status: No, score=-2.564 tagged_above=-999 required=5 tests=[AWL=0.035, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id huywJdP6A68Q for <rrg@core3.amsl.com>;
	Thu, 15 Jan 2009 11:36:38 -0800 (PST)
Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.189])
	by core3.amsl.com (Postfix) with ESMTP id 3CAAD3A69EB
	for <rrg@irtf.org>; Thu, 15 Jan 2009 11:36:37 -0800 (PST)
Received: by ti-out-0910.google.com with SMTP id b8so733172tic.11
	for <rrg@irtf.org>; Thu, 15 Jan 2009 11:36:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from
	:organization:user-agent:mime-version:to:cc:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=YebR7Ga2EBVB75LZWK5+4t/6WnD+cuRspE8IuKNrBHw=;
	b=Jq+5HthCoovvjBG4KuRyG78BpfPSupkcvIV/mqWHuNVFTWMjZHiBD+CDkvnMuGb/te
	xgmbvbzVtkUQ2DOV85CvZ9DBU84ZpnRIguZlXNxzwlSt/PBGYTbODwZvKlbDRu9nKwbj
	7ugzsefKUwEkKOavhJE0zNiJ2RjPmr/rVQQOw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	b=sw8b0GQ8PJWS5No5d/QzhXb+aXTz366NGFFmLoZrdVgxmeIjzeOalbR099HbaHd85J
	gvHEOGe2zl8P2oiuh9ntdfV93kHerKT/0aRAnbQhtqu0rlhQOnhhSUHc8dT/0MvaW10L
	RiSDGP+haCa733SHy8GU8w3Lwocd3Zm1I76Zg=
Received: by 10.110.53.14 with SMTP id b14mr1970118tia.58.1232048182275;
	Thu, 15 Jan 2009 11:36:22 -0800 (PST)
Received: from ?10.1.1.5? (118-92-193-39.dsl.dyn.ihug.co.nz [118.92.193.39])
	by mx.google.com with ESMTPS id w5sm467633tib.14.2009.01.15.11.36.19
	(version=SSLv3 cipher=RC4-MD5); Thu, 15 Jan 2009 11:36:21 -0800 (PST)
Message-ID: <496F9030.20506@gmail.com>
Date: Fri, 16 Jan 2009 08:36:16 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Fleischman, Eric" <eric.fleischman@boeing.com>
References: <474EEBD229DF754FB83D256004D021080AE7ACF9@XCH-NW-6V1.nw.nos.boeing.com>
In-Reply-To: <474EEBD229DF754FB83D256004D021080AE7ACF9@XCH-NW-6V1.nw.nos.boeing.com>
Cc: rrg@irtf.org
Subject: Re: [rrg] No liveness requirement in the ID/Loc Split concept
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Eric,

(cross-post to lisp dropped)

On 2009-01-16 07:42, Fleischman, Eric wrote:
...
> 8) When RLOC-EID is done properly (e.g., like HIP where each concept
> appears on a different layer of the protocol stack), there is no
> liveness problem (nor can there be one). Rather, the "liveness problem"
> described in draft-meyer-loc-id-implications-00.txt is a generic problem
> of map-and-encaps systems, not of RLOC-EID. The title and text of
> draft-meyer-loc-id-implications-00.txt is therefore inappropriately
> scoped as being caused by RLOC-EID when it is rather a common attribute
> of map-and-encaps. Note that LISP is a map-and-encaps system.

I've said from day one that LISP's use of the term 'EID' is incorrect,
and it should be replaced by something like 'local locator' or
'level 0 locator' or some such. So a more positive spin on your
subject line is 'Liveness requirement in multi-locator architectures'.
Which is of course something that has been discovered many times
and is very widely implemented in robust distributed systems.

Another positive spin is 'Mapping requirement in ID/Loc split concept'.

   Brian
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan 15 11:46:53 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B16843A6951;
	Thu, 15 Jan 2009 11:46:53 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 377DF3A6951
	for <rrg@core3.amsl.com>; Thu, 15 Jan 2009 11:46:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.511
X-Spam-Level: 
X-Spam-Status: No, score=-6.511 tagged_above=-999 required=5 tests=[AWL=0.088, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id yKfEBcO55pM1 for <rrg@core3.amsl.com>;
	Thu, 15 Jan 2009 11:46:52 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 361703A67EF
	for <rrg@irtf.org>; Thu, 15 Jan 2009 11:46:52 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,272,1231113600"; d="scan'208";a="33890669"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 15 Jan 2009 19:46:21 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n0FJkLj4010863; 
	Thu, 15 Jan 2009 14:46:21 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n0FJkKHO024189;
	Thu, 15 Jan 2009 19:46:21 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 15 Jan 2009 14:46:20 -0500
Received: from cisco.com ([64.102.8.172]) by xfe-rtp-201.amer.cisco.com with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 15 Jan 2009 14:46:20 -0500
Date: Thu, 15 Jan 2009 14:46:15 -0500
From: Scott Brim <swb@employees.org>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <20090115194615.GI41383@cisco.com>
Mail-Followup-To: Scott Brim <swb@employees.org>,
	Brian E Carpenter <brian.e.carpenter@gmail.com>,
	"Fleischman, Eric" <eric.fleischman@boeing.com>, rrg@irtf.org
References: <474EEBD229DF754FB83D256004D021080AE7ACF9@XCH-NW-6V1.nw.nos.boeing.com>
	<496F9030.20506@gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <496F9030.20506@gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-OriginalArrivalTime: 15 Jan 2009 19:46:20.0274 (UTC)
	FILETIME=[F02F9D20:01C97749]
Authentication-Results: rtp-dkim-1; header.From=swb@employees.org; dkim=neutral
Cc: rrg@irtf.org
Subject: Re: [rrg] No liveness requirement in the ID/Loc Split concept
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Excerpts from Brian E Carpenter on Fri, Jan 16, 2009 08:36:16AM +1300:
> On 2009-01-16 07:42, Fleischman, Eric wrote: ...
> > 8) When RLOC-EID is done properly (e.g., like HIP where each
> > concept appears on a different layer of the protocol stack), there
> > is no liveness problem (nor can there be one). Rather, the
> > "liveness problem" described in
> > draft-meyer-loc-id-implications-00.txt is a generic problem of
> > map-and-encaps systems, not of RLOC-EID. The title and text of
> > draft-meyer-loc-id-implications-00.txt is therefore
> > inappropriately scoped as being caused by RLOC-EID when it is
> > rather a common attribute of map-and-encaps. Note that LISP is a
> > map-and-encaps system.
> 
> I've said from day one that LISP's use of the term 'EID' is
> incorrect, and it should be replaced by something like 'local
> locator' or 'level 0 locator' or some such. So a more positive spin
> on your subject line is 'Liveness requirement in multi-locator
> architectures'.  Which is of course something that has been
> discovered many times and is very widely implemented in robust
> distributed systems.

Identifier/locator separation makes the problem possible, and it can
make it possible at any point in the network.  At any point we can
have a separation of 

  - a name the packets are trying to get to
  - a name for a point in the network via which they can be delivered

and the problems are similar in all cases, whether you use
"identifier" and "locator" to name the things or not.

> Another positive spin is 'Mapping requirement in ID/Loc split
> concept'.

Mapping is just part of the problem.  You can map to all possible
paths, but you have to establish a session in the face of all the
choices, and track and recover from failures.

Scott
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan 15 12:37:35 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E29BC3A6848;
	Thu, 15 Jan 2009 12:37:35 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9CCD23A68C7
	for <rrg@core3.amsl.com>; Thu, 15 Jan 2009 12:37:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 8QkOuMxe9f9S for <rrg@core3.amsl.com>;
	Thu, 15 Jan 2009 12:37:33 -0800 (PST)
Received: from n2.nomadiclab.com (n2.nomadiclab.com
	[IPv6:2001:14b8:400:101::2])
	by core3.amsl.com (Postfix) with ESMTP id A56EB3A6842
	for <rrg@irtf.org>; Thu, 15 Jan 2009 12:37:33 -0800 (PST)
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 4DF001F2D08;
	Thu, 15 Jan 2009 22:37:17 +0200 (EET)
Received: from [127.0.0.1] (localhost [IPv6:::1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 9D9661EF125;
	Thu, 15 Jan 2009 22:37:16 +0200 (EET)
Message-Id: <9C72DD31-8EF8-484D-90F7-81BDBB5A28D2@nomadiclab.com>
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
To: Scott Brim <swb@employees.org>
In-Reply-To: <20090115193205.GA49353@cisco.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Thu, 15 Jan 2009 22:37:16 +0200
References: <474EEBD229DF754FB83D256004D021080AE7ACF9@XCH-NW-6V1.nw.nos.boeing.com>
	<20090115193205.GA49353@cisco.com>
X-Mailer: Apple Mail (2.930.3)
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: rrg@irtf.org, lisp@ietf.org
Subject: Re: [rrg] No liveness requirement in the ID/Loc Split concept
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

> It's clear that pure endpoint-based multipathing, a la Shim6 REAP,  
> cannot scale.


Would you please be more specific.  It is not at all clear to me.   
AFAIK, SCTP is doing essentially the same thing.  (I can see the  
signalling load there, causing potential packet storms; is that the  
"scalability" problem you are referring to?)

> Putting path failure detection and recovery in ITRs instead of in  
> the endpoints can greatly reduce the number of messages flying  
> around, but a simple approach there doesn't scale either, and  
> without information they don't have much choice.

AFAICS, the fundamental problem here is that the network today (BGP)  
cannot detect failures at the desired speed, leading to the situation  
where the hosts (or your funnel points) need to overcome the deficiency.

>> 8) When RLOC-EID is done properly (e.g., like HIP where each  
>> concept appears on a different layer of the protocol stack), there  
>> is no liveness problem (nor can there be one).
>
> I don't see it.  HIP properly removes dependency on location-based  
> names from identification functions, but it does nothing to solve  
> the multipath problem.  You still need to find viable paths,  
> ascertain that multiple locators refer to the same entity (difficult  
> when one or both are moving -- rendezvous servers may be required,  
> tsk), detect path failure and switch to another one.

I mostly agree.  In the HIP WG, years ago the decision was to leave  
the problem of path failure detection to the SHIM6 WG, with the  
intention to integrate REAP to HIP.  However, with HIP (even LHIP)  
verifying that the locators refer to the same entity is relatively  
easy, as long as at least one of the parties retains at least one  
stable locator.  Rendezvous servers are a nice way to introduce stable  
locator to an otherwise dynamic system...  And then, under those  
assumptions, finding paths and switching over is relatively easy.   
Works very well in practise.  We've multiple times tested it with both  
proxies and individual hosts, using 2-3 different radio interfaces at  
each mobile host/proxy, and moving at typical vehicle speeds in  
difficult terrain.  But I digress.

--Pekka

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan 15 13:11:14 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 73B7B3A69FF;
	Thu, 15 Jan 2009 13:11:14 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5DEE33A6A45
	for <rrg@core3.amsl.com>; Thu, 15 Jan 2009 13:11:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.513
X-Spam-Level: 
X-Spam-Status: No, score=-6.513 tagged_above=-999 required=5 tests=[AWL=0.086, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id GX4blTw5Bb5R for <rrg@core3.amsl.com>;
	Thu, 15 Jan 2009 13:11:13 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 088F83A67AB
	for <rrg@irtf.org>; Thu, 15 Jan 2009 13:11:12 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,272,1231113600"; d="scan'208";a="33941156"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 15 Jan 2009 21:10:42 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n0FLAeEG031368; 
	Thu, 15 Jan 2009 16:10:41 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n0FLAe7m005946;
	Thu, 15 Jan 2009 21:10:40 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 15 Jan 2009 16:10:40 -0500
Received: from cisco.com ([64.102.8.172]) by xfe-rtp-202.amer.cisco.com with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 15 Jan 2009 16:10:40 -0500
Date: Thu, 15 Jan 2009 16:10:38 -0500
From: Scott Brim <swb@employees.org>
To: Pekka Nikander <pekka.nikander@nomadiclab.com>
Message-ID: <20090115211038.GJ41383@cisco.com>
Mail-Followup-To: Scott Brim <swb@employees.org>,
	Pekka Nikander <pekka.nikander@nomadiclab.com>,
	"Fleischman, Eric" <eric.fleischman@boeing.com>, rrg@irtf.org,
	lisp@ietf.org
References: <474EEBD229DF754FB83D256004D021080AE7ACF9@XCH-NW-6V1.nw.nos.boeing.com>
	<20090115193205.GA49353@cisco.com>
	<9C72DD31-8EF8-484D-90F7-81BDBB5A28D2@nomadiclab.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <9C72DD31-8EF8-484D-90F7-81BDBB5A28D2@nomadiclab.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-OriginalArrivalTime: 15 Jan 2009 21:10:40.0180 (UTC)
	FILETIME=[B81FFF40:01C97755]
Authentication-Results: rtp-dkim-2; header.From=swb@employees.org; dkim=neutral
Cc: rrg@irtf.org, lisp@ietf.org
Subject: Re: [rrg] No liveness requirement in the ID/Loc Split concept
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Excerpts from Pekka Nikander on Thu, Jan 15, 2009 10:37:16PM +0200:
>> It's clear that pure endpoint-based multipathing, a la Shim6 REAP,
>> cannot scale.
>
> Would you please be more specific.  It is not at all clear to me.
> AFAIK, SCTP is doing essentially the same thing.  (I can see the
> signalling load there, causing potential packet storms; is that the
> "scalability" problem you are referring to?)

I should have done the math first but ... Let's assume,
conservatively, on the order of ten billion communicating endpoint
pairs and 2 locators per endpoint.  How often do you test locator
pairs that you are not using?  Let's be very conservative and assume
once per minute (endpoints can get away with this low level).  Even
so, that's an extra 2^10 packets per minute across the core ... when
things are going perfectly, just for steady state maintenance.  I
can't characterize what percentage of traffic that is, because, for
example, there may be plenty of HTTP sessions that are idle but being
kept open.  We could reduce that maintenance overhead.  Then we add in
what happens when there is a network problem.  I suspect that because
there are active sessions and data is flowing, you would try all
alternative paths at once, with fast probes and duplicate data
packets.  I really don't know what would happen, but I'm awed at the
thought.

>> Putting path failure detection and recovery in ITRs instead of in
>> the endpoints can greatly reduce the number of messages flying
>> around, but a simple approach there doesn't scale either, and
>> without information they don't have much choice.
>
> AFAICS, the fundamental problem here is that the network today (BGP)
> cannot detect failures at the desired speed, leading to the
> situation  where the hosts (or your funnel points) need to overcome
> the deficiency.

Suppose I am at locators A and B, you are talking to me at locator A
and A becomes unreachable.  Regardless of how fast routing detects
that, you (an endpoint) are going to need to detect it yourself,
verify that B is reachable, and switch to B, so you need your own
fault detection and recovery protocol.

>>> 8) When RLOC-EID is done properly (e.g., like HIP where each
>>> concept appears on a different layer of the protocol stack), there
>>> is no liveness problem (nor can there be one).
>>
>> I don't see it.  HIP properly removes dependency on location-based
>> names from identification functions, but it does nothing to solve
>> the multipath problem.  You still need to find viable paths,
>> ascertain that multiple locators refer to the same entity
>> (difficult when one or both are moving -- rendezvous servers may be
>> required, tsk), detect path failure and switch to another one.
>
> I mostly agree.  In the HIP WG, years ago the decision was to leave
> the problem of path failure detection to the SHIM6 WG, with the
> intention to integrate REAP to HIP.  However, with HIP (even LHIP)
> verifying that the locators refer to the same entity is relatively
> easy, as long as at least one of the parties retains at least one
> stable locator.  Rendezvous servers are a nice way to introduce
> stable locator to an otherwise dynamic system...  And then, under
> those assumptions, finding paths and switching over is relatively
> easy.  Works very well in practise.  We've multiple times tested it
> with both proxies and individual hosts, using 2-3 different radio
> interfaces at each mobile host/proxy, and moving at typical vehicle
> speeds in difficult terrain.  But I digress.

That's not a digression, that's real evidence :-).  My concern is not
that "finding paths and switching over is relatively easy", but what
happens when everyone does it.

Scott
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan 15 13:19:52 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 24C373A6A58;
	Thu, 15 Jan 2009 13:19:52 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BDD3C3A6A58
	for <rrg@core3.amsl.com>; Thu, 15 Jan 2009 13:19:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.906
X-Spam-Level: 
X-Spam-Status: No, score=-3.906 tagged_above=-999 required=5
	tests=[AWL=-0.144, BAYES_00=-2.599, RCVD_BAD_ID=2.837,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id vUhvCdz8RM0u for <rrg@core3.amsl.com>;
	Thu, 15 Jan 2009 13:19:49 -0800 (PST)
Received: from smtp01.uc3m.es (smtp01.uc3m.es [163.117.176.131])
	by core3.amsl.com (Postfix) with ESMTP id 7BFBD3A6804
	for <rrg@irtf.org>; Thu, 15 Jan 2009 13:19:49 -0800 (PST)
Received: from r190-135-12-111.dialup.adsl.anteldata.net.uy (unknown 
	[163.117.203.90])by smtp01.uc3m.es (Postfix) with ESMTP id 0F222B47B1F;
	Thu, 15 Jan 2009 22:19:29 +0100 (CET)
Message-ID: <496FA860.6060409@it.uc3m.es>
Date: Thu, 15 Jan 2009 22:19:28 +0100
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.18 (Macintosh/20081105)
MIME-Version: 1.0
To: Scott Brim <swb@employees.org>,
	Pekka Nikander <pekka.nikander@nomadiclab.com>,
	"Fleischman, Eric" <eric.fleischman@boeing.com>, rrg@irtf.org,
	lisp@ietf.org
References: <474EEBD229DF754FB83D256004D021080AE7ACF9@XCH-NW-6V1.nw.nos.boei
	ng.com>	<20090115193205.GA49353@cisco.com>	<9C72DD31-8EF8-484D-90F7-81BDBB5
	A28D2@nomadiclab.com> <20090115211038.GJ41383@cisco.com>
In-Reply-To: <20090115211038.GJ41383@cisco.com>
X-imss-version: 2.051
X-imss-result: Passed
X-imss-scanInfo: M:B L:E SM:2
X-imss-tmaseResult: TT:1 TS:-15.2475 TC:1F TRN:66 TV:5.5.1026(16404.002)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
Subject: Re: [rrg] No liveness requirement in the ID/Loc Split concept
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Scott Brim escribi=F3:
> Excerpts from Pekka Nikander on Thu, Jan 15, 2009 10:37:16PM +0200:
>   =

>>> It's clear that pure endpoint-based multipathing, a la Shim6 REAP,
>>> cannot scale.
>>>       =

>> Would you please be more specific.  It is not at all clear to me.
>> AFAIK, SCTP is doing essentially the same thing.  (I can see the
>> signalling load there, causing potential packet storms; is that the
>> "scalability" problem you are referring to?)
>>     =

>
> I should have done the math first but ... Let's assume,
> conservatively, on the order of ten billion communicating endpoint
> pairs and 2 locators per endpoint.  How often do you test locator
> pairs that you are not using?  =

what do you mean by a "locator pairs that you are not using"?

You mean a locator pair that is not the one that is the current locator =

pair, or do you mean the current locator pair, but that you don't have =

data packets to send in this moment?
regards, marcelo


> Let's be very conservative and assume
> once per minute (endpoints can get away with this low level).  Even
> so, that's an extra 2^10 packets per minute across the core ... when
> things are going perfectly, just for steady state maintenance.

>   I
> can't characterize what percentage of traffic that is, because, for
> example, there may be plenty of HTTP sessions that are idle but being
> kept open.  We could reduce that maintenance overhead.  Then we add in
> what happens when there is a network problem.  I suspect that because
> there are active sessions and data is flowing, you would try all
> alternative paths at once, with fast probes and duplicate data
> packets.  I really don't know what would happen, but I'm awed at the
> thought.
>
>   =

>>> Putting path failure detection and recovery in ITRs instead of in
>>> the endpoints can greatly reduce the number of messages flying
>>> around, but a simple approach there doesn't scale either, and
>>> without information they don't have much choice.
>>>       =

>> AFAICS, the fundamental problem here is that the network today (BGP)
>> cannot detect failures at the desired speed, leading to the
>> situation  where the hosts (or your funnel points) need to overcome
>> the deficiency.
>>     =

>
> Suppose I am at locators A and B, you are talking to me at locator A
> and A becomes unreachable.  Regardless of how fast routing detects
> that, you (an endpoint) are going to need to detect it yourself,
> verify that B is reachable, and switch to B, so you need your own
> fault detection and recovery protocol.
>
>   =

>>>> 8) When RLOC-EID is done properly (e.g., like HIP where each
>>>> concept appears on a different layer of the protocol stack), there
>>>> is no liveness problem (nor can there be one).
>>>>         =

>>> I don't see it.  HIP properly removes dependency on location-based
>>> names from identification functions, but it does nothing to solve
>>> the multipath problem.  You still need to find viable paths,
>>> ascertain that multiple locators refer to the same entity
>>> (difficult when one or both are moving -- rendezvous servers may be
>>> required, tsk), detect path failure and switch to another one.
>>>       =

>> I mostly agree.  In the HIP WG, years ago the decision was to leave
>> the problem of path failure detection to the SHIM6 WG, with the
>> intention to integrate REAP to HIP.  However, with HIP (even LHIP)
>> verifying that the locators refer to the same entity is relatively
>> easy, as long as at least one of the parties retains at least one
>> stable locator.  Rendezvous servers are a nice way to introduce
>> stable locator to an otherwise dynamic system...  And then, under
>> those assumptions, finding paths and switching over is relatively
>> easy.  Works very well in practise.  We've multiple times tested it
>> with both proxies and individual hosts, using 2-3 different radio
>> interfaces at each mobile host/proxy, and moving at typical vehicle
>> speeds in difficult terrain.  But I digress.
>>     =

>
> That's not a digression, that's real evidence :-).  My concern is not
> that "finding paths and switching over is relatively easy", but what
> happens when everyone does it.
>
> Scott
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> http://www.irtf.org/mailman/listinfo/rrg
>
>   =


_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan 15 13:24:59 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D898D3A6783;
	Thu, 15 Jan 2009 13:24:59 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1AD1C3A6804
	for <rrg@core3.amsl.com>; Thu, 15 Jan 2009 13:24:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.514
X-Spam-Level: 
X-Spam-Status: No, score=-6.514 tagged_above=-999 required=5 tests=[AWL=0.085, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id AB8NxV5Jr7di for <rrg@core3.amsl.com>;
	Thu, 15 Jan 2009 13:24:58 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id 50A733A6783
	for <rrg@irtf.org>; Thu, 15 Jan 2009 13:24:58 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,272,1231113600"; d="scan'208";a="129109088"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-3.cisco.com with ESMTP; 15 Jan 2009 21:24:43 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n0FLOhlg009767; 
	Thu, 15 Jan 2009 13:24:43 -0800
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n0FLOTVD007318;
	Thu, 15 Jan 2009 21:24:43 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 15 Jan 2009 16:24:40 -0500
Received: from cisco.com ([64.102.8.172]) by xfe-rtp-202.amer.cisco.com with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 15 Jan 2009 16:24:40 -0500
Date: Thu, 15 Jan 2009 16:24:31 -0500
From: Scott Brim <swb@employees.org>
To: marcelo bagnulo braun <marcelo@it.uc3m.es>
Message-ID: <20090115212431.GA52863@cisco.com>
Mail-Followup-To: Scott Brim <swb@employees.org>,
	marcelo bagnulo braun <marcelo@it.uc3m.es>,
	Pekka Nikander <pekka.nikander@nomadiclab.com>,
	"Fleischman, Eric" <eric.fleischman@boeing.com>, rrg@irtf.org,
	lisp@ietf.org
References: <474EEBD229DF754FB83D256004D021080AE7ACF9@XCH-NW-6V1.nw.nos.boeing.com>
	<20090115193205.GA49353@cisco.com>
	<9C72DD31-8EF8-484D-90F7-81BDBB5A28D2@nomadiclab.com>
	<20090115211038.GJ41383@cisco.com> <496FA860.6060409@it.uc3m.es>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <496FA860.6060409@it.uc3m.es>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-OriginalArrivalTime: 15 Jan 2009 21:24:40.0107 (UTC)
	FILETIME=[ACC2AFB0:01C97757]
Authentication-Results: sj-dkim-1; header.From=swb@employees.org; dkim=neutral
Cc: rrg@irtf.org, lisp@ietf.org
Subject: Re: [rrg] No liveness requirement in the ID/Loc Split concept
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Excerpts from marcelo bagnulo braun on Thu, Jan 15, 2009 10:19:28PM +0100:
> Scott Brim escribi=F3:
>> Excerpts from Pekka Nikander on Thu, Jan 15, 2009 10:37:16PM +0200:
>>   =

>>>> It's clear that pure endpoint-based multipathing, a la Shim6 REAP,
>>>> cannot scale.
>>>>       =

>>> Would you please be more specific.  It is not at all clear to me.
>>> AFAIK, SCTP is doing essentially the same thing.  (I can see the
>>> signalling load there, causing potential packet storms; is that the
>>> "scalability" problem you are referring to?)
>>>     =

>>
>> I should have done the math first but ... Let's assume,
>> conservatively, on the order of ten billion communicating endpoint
>> pairs and 2 locators per endpoint.  How often do you test locator
>> pairs that you are not using?  =

> what do you mean by a "locator pairs that you are not using"?
>
> You mean a locator pair that is not the one that is the current locator  =

> pair, or do you mean the current locator pair, but that you don't have  =

> data packets to send in this moment?
> regards, marcelo

If one end has locators A and B, and the other end has C and D ...
then unless you are multipathing you will use a single pair, e.g. A-C,
while A-D and B-C are not being used, just checked for liveness in
case a need arises.

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan 15 13:36:25 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6986A3A67AB;
	Thu, 15 Jan 2009 13:36:25 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E84713A67AB;
	Thu, 15 Jan 2009 13:36:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.459
X-Spam-Level: 
X-Spam-Status: No, score=-6.459 tagged_above=-999 required=5 tests=[AWL=0.140, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id AGJl1miH2vQg; Thu, 15 Jan 2009 13:36:23 -0800 (PST)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com
	[130.76.64.48])
	by core3.amsl.com (Postfix) with ESMTP id 12EF13A6783;
	Thu, 15 Jan 2009 13:36:23 -0800 (PST)
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4])
	by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id n0FLZuxv007355
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 15 Jan 2009 13:35:58 -0800 (PST)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1])
	by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	n0FLZuUB021869; Thu, 15 Jan 2009 13:35:56 -0800 (PST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	n0FLZo5L021620; Thu, 15 Jan 2009 13:35:56 -0800 (PST)
Received: from XCH-NW-6V1.nw.nos.boeing.com ([130.247.55.53]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 15 Jan 2009 13:35:55 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 15 Jan 2009 13:35:54 -0800
Message-ID: <474EEBD229DF754FB83D256004D021080AEBC805@XCH-NW-6V1.nw.nos.boeing.com>
In-Reply-To: <20090115193205.GA49353@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] No liveness requirement in the ID/Loc Split concept
Thread-Index: Acl3R/edsjtEHhWmThePy7KEy+cClgACX9+w
References: <474EEBD229DF754FB83D256004D021080AE7ACF9@XCH-NW-6V1.nw.nos.boeing.com>
	<20090115193205.GA49353@cisco.com>
From: "Fleischman, Eric" <eric.fleischman@boeing.com>
To: "Scott Brim" <swb@employees.org>
X-OriginalArrivalTime: 15 Jan 2009 21:35:55.0896 (UTC)
	FILETIME=[3F8FE780:01C97759]
Cc: rrg@irtf.org, lisp@ietf.org
Subject: Re: [rrg] No liveness requirement in the ID/Loc Split concept
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Scott,

>>Eric Fleischman wrote:
>> appears on a different layer of the protocol stack), there is no 
>> liveness problem (nor can there be one). Rather, the "liveness
problem"
>> described in draft-meyer-loc-id-implications-00.txt is a generic 
>> problem of map-and-encaps systems, not of RLOC-EID. The title and
text 
>> of draft-meyer-loc-id-implications-00.txt is therefore
inappropriately 
>> scoped as being caused by RLOC-EID when it is rather a common 
>> attribute of map-and-encaps. Note that LISP is a map-and-encaps
system.

>Scott Brim wrote:
>I don't see it.  HIP properly removes dependency on location-based 
>names from identification functions, but it does nothing to solve 
>the multipath problem.  You still need to find viable paths, ascertain 
>that multiple locators refer to the same entity (difficult when one or 
>both are moving -- rendezvous servers may be required, tsk), detect
path 
>failure and switch to another one.  The same is true for Shim6, or 
>Trilogy multipathing ... or anything where you have the chance of using

>multiple paths.  A simple host in a simple PI-based AS can't, and
therefore 
>doesn't have a problem to solve.  Adding HIP in fact makes the problem
possible.

Thank you for sharing your insights. Concerning this specific insight, I
believe that what RLOC-EID split systems like HIP primarily do is to
disambiguate the semantic confusion so that routing (i.e., RLOC) issues
are local to the IP layer and EID concepts are local to the HIP session
layer. 

I fully concur with you that the IP (routing) layer is responsible to
find viable paths between RLOCs, which can be challenging in the highly
mobile environments in which I primarily focus. 

Our research has demonstrated that a key benefit of HIP in highly mobile
environments is that the HIP session layer provides a buffer that
shields the transport and application layers from network effects such
as multihoming and mobility. Our experiments have demonstrated session
persistence even within highly unstable network environments caused by
substantial MANET mobility. We have demonstrated that HIP session layers
simply need not care about underlying IP layer issues such as whether
the underlying network is using IPv4 or IPv6. We've demonstrated HIP
sessions that cleanly and transparently persisted through real-time
underlying network swaps from IPv4 to IPv6 and back.

In our private discussions I observed that because routing can only see
RLOCs and therefore can't discern the existence of multihoming,
multihoming needs to be handled at a layer that has visibility into EIDs
where it can be seen. I received strong push-back on that private list
to my suggestion that multihoming should be an optional service function
of the session layer, perhaps using an optional timer value in the
session layer to substitute a different RLOC source ID value in the
underlying local IP layer if the current RLOC hasn't received any
traffic in a given time quantum. 

I am comfortable receiving push-back on my suggestion in the previous
paragraph because this idea of mine hasn't been adequately examined.
What I am not comfortable with is any approach that attempts to solve
multi-homing at the IP layer because I believe that routing should
solely aggregate and forward packets based on RLOCs -- anything else
needlessly complicates routing and harms Internet performance and
scaling. Therefore, multihoming is not a function of the IP layer. I
realize that this belief of mine conflicts with IETF work and thought
(e.g., the domain discussed by draft-meyer-loc-id-implications-00.txt),
but this nevertheless is how I see things.

--Eric
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan 15 13:37:52 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AB9DE3A67EF;
	Thu, 15 Jan 2009 13:37:52 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5FAAE3A67EF
	for <rrg@core3.amsl.com>; Thu, 15 Jan 2009 13:37:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.315
X-Spam-Level: 
X-Spam-Status: No, score=-5.315 tagged_above=-999 required=5 tests=[AWL=1.284, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id x+G8toDLdGIf for <rrg@core3.amsl.com>;
	Thu, 15 Jan 2009 13:37:50 -0800 (PST)
Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.176.133])
	by core3.amsl.com (Postfix) with ESMTP id 800B43A67EC
	for <rrg@irtf.org>; Thu, 15 Jan 2009 13:37:50 -0800 (PST)
Received: from r190-135-12-111.dialup.adsl.anteldata.net.uy (unknown
	[163.117.203.90])
	by smtp03.uc3m.es (Postfix) with ESMTP id BCAD1731748;
	Thu, 15 Jan 2009 22:37:31 +0100 (CET)
Message-ID: <496FAC99.4020602@it.uc3m.es>
Date: Thu, 15 Jan 2009 22:37:29 +0100
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.18 (Macintosh/20081105)
MIME-Version: 1.0
To: Scott Brim <swb@employees.org>, 
	marcelo bagnulo braun <marcelo@it.uc3m.es>,
	Pekka Nikander <pekka.nikander@nomadiclab.com>, 
	"Fleischman, Eric" <eric.fleischman@boeing.com>,
	rrg@irtf.org, lisp@ietf.org
References: <474EEBD229DF754FB83D256004D021080AE7ACF9@XCH-NW-6V1.nw.nos.boeing.com>
	<20090115193205.GA49353@cisco.com>
	<9C72DD31-8EF8-484D-90F7-81BDBB5A28D2@nomadiclab.com>
	<20090115211038.GJ41383@cisco.com> <496FA860.6060409@it.uc3m.es>
	<20090115212431.GA52863@cisco.com>
In-Reply-To: <20090115212431.GA52863@cisco.com>
X-TM-AS-Product-Ver: IMSS-7.0.0.3116-5.5.0.1026-16404.002
Subject: Re: [rrg] No liveness requirement in the ID/Loc Split concept
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Scott Brim escribi=F3:
> Excerpts from marcelo bagnulo braun on Thu, Jan 15, 2009 10:19:28PM +0100:
>   =

>> Scott Brim escribi=F3:
>>     =

>>> Excerpts from Pekka Nikander on Thu, Jan 15, 2009 10:37:16PM +0200:
>>>   =

>>>       =

>>>>> It's clear that pure endpoint-based multipathing, a la Shim6 REAP,
>>>>> cannot scale.
>>>>>       =

>>>>>           =

>>>> Would you please be more specific.  It is not at all clear to me.
>>>> AFAIK, SCTP is doing essentially the same thing.  (I can see the
>>>> signalling load there, causing potential packet storms; is that the
>>>> "scalability" problem you are referring to?)
>>>>     =

>>>>         =

>>> I should have done the math first but ... Let's assume,
>>> conservatively, on the order of ten billion communicating endpoint
>>> pairs and 2 locators per endpoint.  How often do you test locator
>>> pairs that you are not using?  =

>>>       =

>> what do you mean by a "locator pairs that you are not using"?
>>
>> You mean a locator pair that is not the one that is the current locator  =

>> pair, or do you mean the current locator pair, but that you don't have  =

>> data packets to send in this moment?
>> regards, marcelo
>>     =

>
> If one end has locators A and B, and the other end has C and D ...
> then unless you are multipathing you will use a single pair, e.g. A-C,
> while A-D and B-C are not being used, just checked for liveness in
> case a need arises.
>
>
>   =

That's not how REAP works
REAP does not probes for liveness of unused paths AFAICT

Regards, marcelo

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan 15 15:46:41 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9BD5F28C156;
	Thu, 15 Jan 2009 15:46:41 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C761C28C156;
	Thu, 15 Jan 2009 15:46:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.467
X-Spam-Level: 
X-Spam-Status: No, score=-6.467 tagged_above=-999 required=5 tests=[AWL=0.132, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id aIKSZukJr9qq; Thu, 15 Jan 2009 15:46:39 -0800 (PST)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com
	[130.76.96.56])
	by core3.amsl.com (Postfix) with ESMTP id C7EE63A6405;
	Thu, 15 Jan 2009 15:46:39 -0800 (PST)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6])
	by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id n0FNk9Wx011101
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Thu, 15 Jan 2009 17:46:19 -0600 (CST)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	n0FNk93G018474; Thu, 15 Jan 2009 17:46:09 -0600 (CST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	n0FNk3Cc018327; Thu, 15 Jan 2009 17:46:08 -0600 (CST)
Received: from XCH-NW-6V1.nw.nos.boeing.com ([130.247.55.53]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 15 Jan 2009 15:46:06 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 15 Jan 2009 15:46:03 -0800
Message-ID: <474EEBD229DF754FB83D256004D021080AEBC96B@XCH-NW-6V1.nw.nos.boeing.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] No liveness requirement in the ID/Loc Split concept
Thread-Index: Acl3R/edsjtEHhWmThePy7KEy+cClgACX9+wAASBkaA=
References: <474EEBD229DF754FB83D256004D021080AE7ACF9@XCH-NW-6V1.nw.nos.boeing.com>
	<20090115193205.GA49353@cisco.com> 
From: "Fleischman, Eric" <eric.fleischman@boeing.com>
To: <lisp@ietf.org>
X-OriginalArrivalTime: 15 Jan 2009 23:46:06.0691 (UTC)
	FILETIME=[6F28A330:01C9776B]
Cc: rrg@irtf.org
Subject: Re: [rrg] No liveness requirement in the ID/Loc Split concept
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

>From: Fleischman, Eric 
>In our private discussions I observed that because routing can 
>only see RLOCs and therefore can't discern the existence of 
>multihoming, multihoming needs to be handled at a layer that has 
>visibility into EIDs where it can be seen. I received strong push-back 
>on that private list to my suggestion that multihoming should be an 
>optional service function of the session layer, perhaps using an 
>optional timer value in the session layer to substitute a different 
>RLOC source ID value in the underlying local IP layer if the current 
>RLOC hasn't received any traffic in a given time quantum. 

>I am comfortable receiving push-back on my suggestion in the previous 
>paragraph because this idea of mine hasn't been adequately examined. 
>What I am not comfortable with is any approach that attempts to solve 
>multi-homing at the IP layer because I believe that routing should 
>solely aggregate and forward packets based on RLOCs -- anything else 
>needlessly complicates routing and harms Internet performance and 
>scaling. Therefore, multihoming is not a function of the IP layer. I 
>realize that this belief of mine conflicts with IETF work and thought 
>(e.g., the domain discussed by draft-meyer-loc-id-implications-00.txt),

>but this nevertheless is how I see things.

Scott Brim and I had a private discussion concerning the impact of HIP
on RLOC-EID liveness. As part of that discussion, he recommended that I
forward to the list my following additional opinion concerning the above
first paragraph:

My suggestion in my first paragraph above was a possible extension to
HIP or other EID-RLOC separation systems. HIP doesn't do liveness now in
the base HIP specs. However, the HIP community is currently considering
eventually possibly adopting two different liveness alternatives: using
SIP's ICE for NAT traversal and SHIM6's REAP for multihoming -- I
believe these proposed approaches are unacceptably resource consumptive,
which is why I made the above suggestion. Regardless, HIP doesn't do
either today but it currently does protect the transport layer and above
from having to care about multihoming or network issues. Specifically,
the session doesn't care what RLOC is used to support that session at
the IP layer -- any packet duplications will be handled at the transport
or application layer. It's simply not a problem.

My previous suggestion (above) was how to respond to the liveness
problem for HIP should the current network path fail in multihoming
environments. Currently, if the routing layer doesn't have a live path
to an RLOC supporting that EID, then the session is not receiving
packets. If the network layer is not aware of an alternative RLOC (which
is what I expect to be the norm), then it can't use that alternative
remote multihomed RLOC unless it is redirected to it by a mechanism that
is unrelated to routing tables (i.e., routers should only deal with
RLOCs). My original paragraph above suggested a way to alert the remote
peer to the existence of another RLOC supporting that EID so that it
could try that alternative path. This presumes a non-symmetric routing
blockage (i.e., not due to a blockage affecting all of a peer's
transmissions regardless). 

Regardless, I believe that the id/loc split concept presumes that the
session layer needs to handle multihoming and the IP layer need to
handle routing between RLOCs. The two concepts (RLOC, EID) need to
remain separated without becoming confused by needless dependencies.
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan 15 19:53:04 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7A55F3A67AB;
	Thu, 15 Jan 2009 19:53:04 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 24AC63A67AB
	for <rrg@core3.amsl.com>; Thu, 15 Jan 2009 19:53:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.561
X-Spam-Level: 
X-Spam-Status: No, score=-1.561 tagged_above=-999 required=5 tests=[AWL=0.334, 
	BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id lpD2pgUsXm90 for <rrg@core3.amsl.com>;
	Thu, 15 Jan 2009 19:53:01 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123])
	by core3.amsl.com (Postfix) with ESMTP id 4BE1C3A6783
	for <rrg@irtf.org>; Thu, 15 Jan 2009 19:53:01 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6])
	by gair.firstpr.com.au (Postfix) with ESMTP id 2EECD175EC2;
	Fri, 16 Jan 2009 14:52:43 +1100 (EST)
Message-ID: <49700412.7040507@firstpr.com.au>
Date: Fri, 16 Jan 2009 14:50:42 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: RRG <rrg@irtf.org>
Subject: [rrg] Taxonomy: Separation, Elimination, ID/Loc Split,
 map-and-encaps, HIP etc.
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Short version:   An attempt to clarify the current, too-loose, use
                 of the term "map-and-encaps" and to depict the
                 three current approaches to tunneling packets
                 in a Core-Edge Separation scheme.

I am happy to go along with the suggestion of Eric and others that
HIP is a genuine ID/Loc Split system and that LISP, APT, Ivip, TRRP
and Six/One Router are not.

Here is how I see things:

  Elimination:
     HIP, Six/One, SHIM6 and ILNP.  (GSE?)


  Separation:
     Map-Encap:
       LISP, APT, TRRP and Ivip using encapsulation.

     Map-Forward:
       Ivip's two Forwarding modes.

     Map-Rewrite:
       Six/One Router.


HIP (as part of a routing scaling solution) is an example of the
"Elimination" approach, as defined in:

  Towards a Future Internet Architecture: Arguments for
  Separating Edges from Transit Core
  Dan Jen, Lixia Zhang, Lan Wang, Beichuan Zhang
  http://conferences.sigcomm.org/hotnets/2008/papers/18.pdf

Elimination involves new responsibilities for each host.  Bill's
"Strategy B" - or a somewhat broader version of it - seems to cover
the Elimination approach:

  http://bill.herrin.us/network/rrgarchitectures.html

I think that ILNP, SHIM6 and Six/One are also part of the Elimination
class.  All these involve ever host which participates in multihoming
(including those which are not multihomed themselves) managing
multihoming via the use of multiple addresses at each multihomed host.

My critique of all such schemes - an argument against pushing this
responsibility to the hosts - is:

  Fundamental objections to a host-based scalable routing solution
  http://www.irtf.org/pipermail/rrg/2008-November/000233.html

However, see also my next message about the scaling problems of such
Elimination schemes as every host probes reachability via each of its
addresses to the one, two or more addresses of every host it is
communicating with.


The other major approach to the routing scaling problem (not counting
trying to soup up BGP, or to change the interdomain routing system in
a more drastic manner, such as with geo-aggregation) is "Separation".
 This is the approach preferred by Dan Jen et al.

Initially, the only proposals which fell into this class were map and
encapsulate proposals: APT and LISP (which came first?), then Ivip
and TRRP.  The term "Core-Edge Separation" came later, I think.

Then, in early 2008, Six/One Router was proposed. ("Six One" on its
own, was an earlier, host-based, Separation scheme.)  This uses
address rewriting rather than encapsulation.  The current version is:

http://users.piuha.net/chvogt/pub/2008/vogt-2008-six-one-router-design.pdf

In late 2008 I proposed two related but separate "Forwarding"
approaches, as an alternative to encapsulation or address rewriting.
    Both these use modified formats for the IP header, and require
upgrades to all DFZ routers.  This may well be feasible, and the
benefits include eliminating encapsulation overhead and the PMTUD
problems of encapsulation:

   ETR Address Forwarding (EAF) - for IPv4
   http://tools.ietf.org/html/draft-whittle-ivip4-etr-addr-forw-01

   Prefix Label Forwarding (PLF) - for IPv6
   http://www.firstpr.com.au/ip/ivip/ivip6/

Initially, the terms "ITR" and "ETR" were used with the map-encap
approaches solely - for Ingress and Egress Tunnel Routers.  This made
sense since tunnelling has traditionally been done by encapsulation
and was in all these proposals.

With the two Forwarding approaches, I keep the ITR and ETR terms for
the devices which rewrite the header and which restore it
respectively.  It is still like a tunnel - a one-way tunnel as with
map-encap - although there is no additional header.

The terms "ITR" and "ETR" are not used in Six/One Router, but it is
easy to think of the rewriting roles of the Tunnel Routers in these
terms.

All these Separation schemes involve:

  No changes to hosts.

  A mapping system.

  New devices (or additional functionality in existing devices) such
  as ITRs and ETRs in the network (although with Ivip at least, it is
  possible to integrate the ITR function in some sending hosts).

So Separation schemes are "Network-based" while Elimination schemes
are "Host-based".

Some host-based systems may not require changing the API and
applications, while others will require this.  All these host based
systems require IPv6 - since there is not enough address space in
IPv4 for hosts to have multiple addresses.

No host changes are required for the Separation approaches, except that:

 1 - Six/One Router is IPv6 only.

 2 - Ivip's IPv4 EAF Forwarding approach and Ivip's IPv4 map-encap
     approach to PMTUD both involve not sending fragmentable
     packets longer than a certain length, such as somewhat less
     than 1500 bytes.  EAF doesn't send fragments either.

 - Robin


_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan 15 19:54:21 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B72363A6891;
	Thu, 15 Jan 2009 19:54:21 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6E05E3A6891
	for <rrg@core3.amsl.com>; Thu, 15 Jan 2009 19:54:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.567
X-Spam-Level: 
X-Spam-Status: No, score=-1.567 tagged_above=-999 required=5 tests=[AWL=0.328, 
	BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id fI97BcY8SRqJ for <rrg@core3.amsl.com>;
	Thu, 15 Jan 2009 19:54:19 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123])
	by core3.amsl.com (Postfix) with ESMTP id 63FE23A6783
	for <rrg@irtf.org>; Thu, 15 Jan 2009 19:54:18 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6])
	by gair.firstpr.com.au (Postfix) with ESMTP id C3867175EC2;
	Fri, 16 Jan 2009 14:54:02 +1100 (EST)
Message-ID: <49700462.9020605@firstpr.com.au>
Date: Fri, 16 Jan 2009 14:52:02 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: "Fleischman, Eric" <eric.fleischman@boeing.com>
References: <474EEBD229DF754FB83D256004D021080AE7ACF9@XCH-NW-6V1.nw.nos.boeing.com>	<20090115193205.GA49353@cisco.com>
	<474EEBD229DF754FB83D256004D021080AEBC96B@XCH-NW-6V1.nw.nos.boeing.com>
In-Reply-To: <474EEBD229DF754FB83D256004D021080AEBC96B@XCH-NW-6V1.nw.nos.boeing.com>
Cc: rrg@irtf.org, lisp@ietf.org
Subject: Re: [rrg] No liveness requirement in the ID/Loc Split concept
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

I am responding to Eric Fleishman and Scott Brim, regarding:

  http://tools.ietf.org/html/draft-meyer-loc-id-implications-00

My previous RRG message explains the following taxonomy:

  Elimination (genuine, host-based, ID/Loc split):
     HIP, Six/One, SHIM6 and ILNP.


  Separation (network based ITRs and ETRs using a mapping system -
  with no host involvement in multihoming.  Arguably not a true
  ID/Loc Split arrangement):
     Map-Encap:
       LISP, APT, TRRP and Ivip using encapsulation.

     Map-Forward:
       Ivip's two Forwarding modes. (Modified IP headers
       and DFZ routers.)

     Map-Rewrite:
       Six/One Router.


Eric wrote:

> the "liveness problem" described in
> draft-meyer-loc-id-implications-00.txt is a generic problem
> of map-and-encaps systems, not of RLOC-EID. The title and text of
> draft-meyer-loc-id-implications-00.txt is therefore inappropriately
> scoped as being caused by RLOC-EID when it is rather a common
> attribute of map-and-encaps. Note that LISP is a map-and-encaps
> system.

I disagree that the objectionable scaling problems which are the main
concern in the "locator liveness problem" are inherent in map-encap
systems.

Ivip in both its map-encap and its (modified IP header) forwarding
modes does not have this scaling problem because the ITRs are not
responsible for deciding which LOC address to tunnel the traffic
packets to.

In Ivip, the mapping information for each micronet (roughly
equivalent to a LISP EID prefix) consists of a single LOC address -
the address of the ETR by which the destination network can currently
be reached.

The destination multihomed end-user network is responsible for
probing the reachability of their network via its two or more ETRs -
and for changing the mapping of their micronets in real-time so that
when the current ETR becomes unreachable, all ITRs will use another
ETR address instead.

Therefore, there is no scaling problem with thousands or hundreds of
thousands or whatever ITRs all simultaneously trying to test
reachability to the two or ETRs of this destination multihomed
end-user network.

The formal definition of the problem from the I-D is:

     Given a set of source locators and a set of destination
     locators, can bidirectional connectivity be determined between
     the <source locator,destination locator> address pairs?


(Strictly speaking, it is not necessarily to determine a single path
 for bidirectional communication.  For instance, it is OK for packets
 to flow like this, if the connectivity permits:

  CEA -> ITR1 -> ETR3 -> CEB
  CEA <- ETR2 <- ITR4 <- CEB )


Here is a diagram relevant to Core-Edge Separation schemes, depicting
two hosts, in separate multihomed end-user networks NA and NB, each
with two upstream ISPs:

                        ~~~~~~~~~~~
   NA           ISP1   ~           ~   ISP3         NB
            PE1      BR1---     ---BR3     PE3
 ........  /    ITR1   ~\         /~   ITR3   \  ........
 .      . /     ETR1   ~ \       / ~   ETR3    \ .      .
 . HA---CEA            ~    DFZ    ~           CEB---HB .
 .      . \            ~ /       \ ~           / .      .
 ........  \   ISP2    ~/         \~   ISP4   /  ........
            PE2      BR2---     ---BR4      PE4
               ITR2    ~           ~   ITR4
               ETR2     ~~~~~~~~~~~    ETR4

(Fig 1)

If the packet flow is NA --> NB, then CEA could send the packet to
either upstream ISP.  So for LISP etc. (not Ivip) either of both ITR1
and ITR2 need to continually check reachability to both ETR3 and ETR4
- or rather that firstly whether ETR3 and ETR4 can be reached and
secondly, that each ETR can reach the Customer Edge router of NB: CEB.

In practice, if CEA only sends packets addressed to HB out via the
ISP1 link then ITR2 never sees them, does not get mapping for HB's
EID prefix, and does not have to keep checking reachability to the
ETR addresses (LOCs) listed in the mapping.


Ivip's real-time mapping gives all the involved ITRs (ITR1 and/or
ITR2 in the above HA -> HB example) the information they need to be
able to tunnel packets to an ETR by which HB can be reached.  So Ivip
ITRs do no reachability checking.


Neither LISP etc. nor Ivip solve the problem of telling CEA which
upstream link to send packets from.  The CEA router needs to do its
own reachability testing to its two upstream ISPs, and ideally would
also determine whether each ISP was functioning in terms of
forwarding packets correctly to all destinations.


The real "locator liveness" problem is a scaling problem.  It occurs
in LISP etc. when there are host in thousands or hundreds of
thousands of networks such as NA sending packets to NB.  Since each
such sending host network will have one, two or more ITRs, the
scaling problem is the vast number of ITRs which need to be
continually probing reachability to both ETR3 and ETR4.

Ivip has no such problem because, irrespective of how many ITRs are
sending packets to the micronet in which HB is located, the
reachability testing is done by whatever purpose-built system the NB
uses.  The most likely arrangement is for NB to contract the services
of a company which specialises in this reachability testing, from
multiple locations in the DFZ.  The typical arrangement would be for
NB to give that company the credentials it needs to change the
mapping of NB's micronets in order to spread incoming load over NB's
upstream links, and to restore connectivity if an ISP or a link to
and ISP, fails.  This way, the mapping is changed quickly without any
reliance on NB's network being reachable at all.

Of course, NB could use one or more such reachability testing
companies and use the results in its own servers to make the final
mapping decisions.  Placing those servers in its own network would be
tricky, since they need to function reliably at times of partial
network failure.  It would be better to rely on the distributed,
highly robust, purpose built system of a company which specialises in
reachability testing.


Scott wrote:

> It's clear that pure endpoint-based multipathing, =E0 la Shim6 REAP,
> cannot scale.

Yes, for SHIM6, HIP, ILNP or whatever elimination scheme it is, the
problem is likely to be worse than depicted above using ITRs and ETRs.

With the above example, there could be 100 hosts in NA sending
packets to one or more hosts in NB, and there would be no extra
burden of probing traffic etc. - since the same number of ITRs (ITR1
and/or ITR2) are involved.

With HIP, or any other host-based Elimination scheme, the diagram
looks like this:


                        ~~~~~~~~~~~
   NA           ISP1   ~           ~   ISP3         NB
            PE1      BR1---     ---BR3     PE3
 ........  /           ~\         /~          \  ........
 .      . /            ~ \       / ~           \ .      .
 . HA---CEA            ~    DFZ    ~           CEB---HB .
 .      . \            ~ /       \ ~           / .      .
 ........  \   ISP2    ~/         \~   ISP4   /  ........
            PE2      BR2---     ---BR4      PE4
                       ~           ~
                        ~~~~~~~~~~~

  HA's addresses:                         HB's addresses:

    wwww (from ISP1)                      yyyy (from ISP3)
    xxxx (from ISP2)                      zzzz (from ISP4)

(Fig 2)

HA needs to probe reachability in these paths:

   wwww -> yyyy (presumably, with confirmation packets coming
                 back via xxxx <- yyyy)
   wwww -> zzzz (ditto wwww <- zzzz)

   xxxx -> yyyy (ditto xxxx <- yyyy)
   xxxx -> zzzz (ditto xxxx <- zzzz)

This exact situation is comparable to that depicted in Fig 1.  The
number of probes is roughly the same and the burden they place on the
DFZ is about the same.  The probing is more thorough, because it
tests complete host-to-host reachability, thereby picking up any
problems between each host and its CE router - which are not picked
up in LISP etc. or typically by the systems which would be used by Ivip.

There are at least two reasons why the "locator liveness" problem is
worse for HIP, ILNP etc. (any host-based Elimination scheme) compared
to LISP etc. (any Separation scheme in which the mapping lists
multiple ETR addresses and requires each ITR to test reachability to
them):

1 - The probe traffic goes all the way to and from the hosts.
    This is a major burden on any host on an expensive, slow and/or
    congested link - as is typically the case with any physically
    mobile device using one or more wireless links.

2 - There is an additional scaling factor in comparison to Fig 1
    when there are multiple hosts in each end-user network.

    For LISP etc. those additional hosts do not cause any burden
    on the probing effort.

    For HIP etc. the load multiplied directly with the number of
    hosts.

Point 1 is one of the aspects of my critique:

  Fundamental objections to a host-based scalable routing solution
  http://www.irtf.org/pipermail/rrg/2008-November/000233.html

and HIP, with all its cryptography, host-to-host handshaking before
any user traffic can proceed etc. exemplifies my other critiques
about delaying communications and burdening all hosts with excessive
protocol and computational complexity.

Point 2, I think, is what Scott is referring to regarding REAP not
scaling.

> Putting path failure detection and recovery in ITRs instead of in
> the endpoints can greatly reduce the number of messages flying
> around,

Yes, as illustrated above, for multiple sending hosts in one end-user
network.

> but a simple approach there doesn't scale either,

Yes: LISP, APT, TRRP and Six/One Router - or any scheme where the
ITRs are given non-real-time mapping and so need to continually find
out for themselves, independently, which ETRs are reachable.

> and without information they don't have much choice.

Ivip gives the ITRs the information in real-time - so the ITR has no
such choices to make.


> One thing we could do is to couple them.  The endpoint could
> periodically tell "the network" what it needs, so the network only
> needs to do just enough.

More and more complexity . . .

> Another thing we can do is cut back on our requirements, at least
> for a while.

I don't see how, other than by making LISP into something less robust
than it is intended to be.  No-one would want to invest in a system
which provides multihoming "sometimes".

Scott also criticised HIP's reliance on rendezvous servers to cope
with the messy situation of both hosts trying to retain consistent
communications at the HIT level when their underlying LOC addresses
are in flux, as will often be the case in the future as more and more
mobile devices are used.

> rendezvous servers may be required, tsk

"tsk" seems rather reserved.  How about:

  More and more complexity and management traffic . . . Arrrggg!!!!


 - Robin

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Thu Jan 15 21:47:08 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0F8183A683D;
	Thu, 15 Jan 2009 21:47:08 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E09463A67AA
	for <rrg@core3.amsl.com>; Thu, 15 Jan 2009 21:47:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.592
X-Spam-Level: 
X-Spam-Status: No, score=-6.592 tagged_above=-999 required=5 tests=[AWL=0.007, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id s2MRLjfGrxbJ for <rrg@core3.amsl.com>;
	Thu, 15 Jan 2009 21:47:05 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122])
	by core3.amsl.com (Postfix) with ESMTP id 9BB7F3A683D
	for <rrg@irtf.org>; Thu, 15 Jan 2009 21:47:05 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178)
	id 626B56BE594; Fri, 16 Jan 2009 00:46:47 -0500 (EST)
To: rrg@irtf.org
Message-Id: <20090116054647.626B56BE594@mercury.lcs.mit.edu>
Date: Fri, 16 Jan 2009 00:46:47 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [rrg] No liveness requirement in the ID/Loc Split concept
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

    > From: Brian E Carpenter <brian.e.carpenter@gmail.com>

    > I've said from day one that LISP's use of the term 'EID' is incorrect,
    > and it should be replaced by something like 'local locator' or 'level 0
    > locator' or some such. 

Sorry, but it's _not_ a locator, and more an 'endpoint identifier' than
anything else - at least, as far as the original definitions of those terms
go.

(And might I remind people that the term "locator" came from Nimrod, and "EID"
from you-know-where. So excuse me if I get a little cranky with people trying
to tell me whether or not they are applicable to something, when I am
perfectly darned happy with their use in that context.)

The thing that people seem to be forgetting, in making this claim, is that
it's also important _what kind of thing_ is being named, not just _the
attributes of the name itself_. Those are two orthagonal axes, and people
still don't seem to be clearly understanding/remembering that most concept
terms being thrown around here, such as locator, EID, etc, generally involves
a _set_ of choices, one on each axis.

There seems to be a tendency to think 'locator' means 'name with topological
significance', and that's _not_ what it was defined as - it meant '_interface
name_ with topological significance'. (Actually, it was defined to be
'interface name with topological significance which does not appear in all
packets', since people seemed terminally unable to wrap their minds around the
concept of an 'address' that didn't appear in all packets.) Similarly, an
'EID' is an '_endpoint_ identifier without topological significance', not just
'name with no topological significance'.

We don't really have a generally-accepted term for 'endpoint name with
topological significance'; 'address' has some of that flavour, but in
e.g. IPv4 it also 'sort of' names an interface.


With all this in hand, it's clear that a LISP EID does _not_ name an
interface, but rather a 'stack' - i.e. an endpoint, with a collection of TCP
connections. So to say that it's a 'locator' is wholly incorrect - it is
_exactly_ an 'endpoint name', as that term was formally defined.

There is no one-word description/term which _exactly_ describes a LISP EID;
it's a bit of a kludge (precisely because of installed base issues). To be
maximally precise, a LISP 'EID' is 'a globally-unique endpoint name with
topological significance within a local scope only'.

	Noel
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Fri Jan 16 09:16:46 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2FE9528C274;
	Fri, 16 Jan 2009 09:16:46 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1FBF328C27B
	for <rrg@core3.amsl.com>; Fri, 16 Jan 2009 09:16:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.415
X-Spam-Level: 
X-Spam-Status: No, score=-6.415 tagged_above=-999 required=5 tests=[AWL=0.184, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id MYPEHN-1c6TR for <rrg@core3.amsl.com>;
	Fri, 16 Jan 2009 09:16:38 -0800 (PST)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com
	[130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id E394A3A68B0
	for <rrg@irtf.org>; Fri, 16 Jan 2009 09:16:38 -0800 (PST)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231])
	by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id n0GHGCaM003395
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);
	Fri, 16 Jan 2009 09:16:22 -0800 (PST)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	n0GHGB7c011993; Fri, 16 Jan 2009 09:16:11 -0800 (PST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	n0GHGAO9011834; Fri, 16 Jan 2009 09:16:11 -0800 (PST)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 16 Jan 2009 09:16:09 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 16 Jan 2009 09:16:11 -0800
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1056E7C04@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <20090116054647.626B56BE594@mercury.lcs.mit.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] No liveness requirement in the ID/Loc Split concept
Thread-Index: Acl3ndbGshxc8eZwRjuQFkqqKxZV1AAWb1Og
References: <20090116054647.626B56BE594@mercury.lcs.mit.edu>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Noel Chiappa" <jnc@mercury.lcs.mit.edu>, <rrg@irtf.org>
X-OriginalArrivalTime: 16 Jan 2009 17:16:09.0833 (UTC)
	FILETIME=[1FF52D90:01C977FE]
Subject: Re: [rrg] No liveness requirement in the ID/Loc Split concept
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Hi Noel,

>-----Original Message-----
>From: Noel Chiappa [mailto:jnc@mercury.lcs.mit.edu]
>Sent: Thursday, January 15, 2009 9:47 PM
>To: rrg@irtf.org
>Cc: jnc@mercury.lcs.mit.edu
>Subject: Re: [rrg] No liveness requirement in the ID/Loc Split concept
>
>
>    > From: Brian E Carpenter <brian.e.carpenter@gmail.com>
>
>    > I've said from day one that LISP's use of the term 'EID' is
incorrect,
>    > and it should be replaced by something like 'local locator' or
'level 0
>    > locator' or some such.
>
>Sorry, but it's _not_ a locator, and more an 'endpoint identifier' than
>anything else - at least, as far as the original definitions of those
terms
>go.
>
>(And might I remind people that the term "locator" came from Nimrod,
and "EID"
>from you-know-where. So excuse me if I get a little cranky with people
trying
>to tell me whether or not they are applicable to something, when I am
>perfectly darned happy with their use in that context.)
>
>The thing that people seem to be forgetting, in making this claim, is
that
>it's also important _what kind of thing_ is being named, not just _the
>attributes of the name itself_. Those are two orthagonal axes, and
people
>still don't seem to be clearly understanding/remembering that most
concept
>terms being thrown around here, such as locator, EID, etc, generally
involves
>a _set_ of choices, one on each axis.
>
>There seems to be a tendency to think 'locator' means 'name with
topological
>significance', and that's _not_ what it was defined as - it meant
'_interface
>name_ with topological significance'. (Actually, it was defined to be
>'interface name with topological significance which does not appear in
all
>packets', since people seemed terminally unable to wrap their minds
around the
>concept of an 'address' that didn't appear in all packets.) Similarly,
an
>'EID' is an '_endpoint_ identifier without topological significance',
not just
>'name with no topological significance'.
>
>We don't really have a generally-accepted term for 'endpoint name with
>topological significance'; 'address' has some of that flavour, but in
>e.g. IPv4 it also 'sort of' names an interface.
>
>
>With all this in hand, it's clear that a LISP EID does _not_ name an
>interface, but rather a 'stack' - i.e. an endpoint, with a collection
of TCP
>connections.

I think that depends on where you assign the EID (using "EID"
and "RLOC" in the LISP sense of the words for the purpose of
this message). If you assign the EID to an interface used
for forwarding packets to the outside world (e.g., an interface
attached to an ethernet link, a tunnel virtual interface, etc.)
then it names the interface in the traditional sense. If you
instead assign the EID to an internal virtual interface (e.g.,
a loopback interface), then in some sense it could be
considered as naming the stack. But...

> So to say that it's a 'locator' is wholly incorrect - it is
>_exactly_ an 'endpoint name', as that term was formally defined.

...it is still a routing locator at least within a limited scope.

LISP RLOCs are routing locators within the interdomain region,
and LISP EIDs appear in mapping tables within the interdomain
region. However, the EIDs are still routing locators within
edge networks even if the "edge network" consists of a
singleton end system.

IMHO, there is no escaping the fact that LISP EIDs are still
IP addresses that name interfaces, even though we have these
"special" interfaces like loopbacks that can in some sense
be considered as a "handle" for naming a stack.

HIP HITs on the other hand are true endpoint identifiers
that name end systems only, and cannot be used as routing
locators in any scope.

Fred
fred.l.templin@boeing.com
 
>There is no one-word description/term which _exactly_ describes a LISP
EID;
>it's a bit of a kludge (precisely because of installed base issues). To
be
>maximally precise, a LISP 'EID' is 'a globally-unique endpoint name
with
>topological significance within a local scope only'.
>
>	Noel
>_______________________________________________
>rrg mailing list
>rrg@irtf.org
>http://www.irtf.org/mailman/listinfo/rrg
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Fri Jan 16 09:27:08 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B029C3A69F2;
	Fri, 16 Jan 2009 09:27:08 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 916BE28C277
	for <rrg@core3.amsl.com>; Fri, 16 Jan 2009 09:27:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.592
X-Spam-Level: 
X-Spam-Status: No, score=-6.592 tagged_above=-999 required=5 tests=[AWL=0.007, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id bqz0G1A2UskY for <rrg@core3.amsl.com>;
	Fri, 16 Jan 2009 09:27:06 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122])
	by core3.amsl.com (Postfix) with ESMTP id 9E12228C257
	for <rrg@irtf.org>; Fri, 16 Jan 2009 09:27:06 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178)
	id 489456BE5B7; Fri, 16 Jan 2009 12:26:48 -0500 (EST)
To: rrg@irtf.org
Message-Id: <20090116172648.489456BE5B7@mercury.lcs.mit.edu>
Date: Fri, 16 Jan 2009 12:26:48 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [rrg] No liveness requirement in the ID/Loc Split concept
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

    > From: jnc@mercury.lcs.mit.edu (Noel Chiappa)

    > a LISP EID does _not_ name an interface, but rather a 'stack' - i.e. an
    > endpoint, with a collection of TCP connections.

A private reply pointed out that a LISP EID in fact _also_ names an
interface, just like an IPv4 address. That's a consequence of the fact that a
LISP design goal was to allow unmodified hosts, so one can only change the
semantics of existing namespaces a little.


Interesting historical note: the Nimrod deployment plan:

  http://ana-3.lcs.mit.edu/~jnc/nimrod/deploy.txt

looked a lot like LISP's deployment plan - the existing IP layer was 'jacked
up' and a new layer inserted underneath; unmodified hosts were unaware that
this all was happening, and continued to emit and receive classic IPv4
packet; Nimrod agent-routers were responsible for invisibly translating the
IPv4 'addresses' in those packets into Nimrod locators, and doing the
encapsulation. Although the Nimrod deployment plan spoke of turning IPv4
'addresses' into endpoint names (EIDs, to be exact - ironically), it's clear
that there, IPv4 addresses also retained minimal interface naming semantics.


It's almost inevitable, in any plan which supports unmodified hosts, that
the IPvN addresses used by those hosts will retain the basic semantics of
IPvN addresses.

	Noel
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Fri Jan 16 11:10:19 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E667328C2BF;
	Fri, 16 Jan 2009 11:10:19 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2548328C2BE
	for <rrg@core3.amsl.com>; Fri, 16 Jan 2009 11:10:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id gQApJGjK-jGz for <rrg@core3.amsl.com>;
	Fri, 16 Jan 2009 11:10:18 -0800 (PST)
Received: from virtualized.org (trantor.virtualized.org [204.152.189.190])
	by core3.amsl.com (Postfix) with ESMTP id 3830C28C2BC
	for <rrg@irtf.org>; Fri, 16 Jan 2009 11:10:17 -0800 (PST)
Received: from [10.0.1.200] (c-71-198-3-247.hsd1.ca.comcast.net [71.198.3.247])
	by virtualized.org (Postfix) with ESMTP id 3A65D42ABC9
	for <rrg@irtf.org>; Fri, 16 Jan 2009 11:09:25 -0800 (PST)
Message-Id: <C8E588B7-8AA9-49B7-AC2C-AC3E2CBEA4C0@virtualized.org>
From: David Conrad <drc@virtualized.org>
To: RRG RG <rrg@irtf.org>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Fri, 16 Jan 2009 11:09:24 -0800
X-Mailer: Apple Mail (2.930.3)
Subject: [rrg] Apropos whether Moore's law can keep ahead of routing system
	growth
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

http://www.physorg.com/print151162452.html

Haven't read the actual paper this article summarizes (and I have to  
admit some skepticism)...

Regards,
-drc

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Fri Jan 16 12:05:47 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6E0543A69CA;
	Fri, 16 Jan 2009 12:05:47 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 07F413A69D7
	for <rrg@core3.amsl.com>; Fri, 16 Jan 2009 12:05:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.419
X-Spam-Level: 
X-Spam-Status: No, score=-6.419 tagged_above=-999 required=5 tests=[AWL=0.180, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id kXk8pUwDaLPt for <rrg@core3.amsl.com>;
	Fri, 16 Jan 2009 12:05:45 -0800 (PST)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com
	[130.76.96.56]) by core3.amsl.com (Postfix) with ESMTP id 249723A695E
	for <rrg@irtf.org>; Fri, 16 Jan 2009 12:05:45 -0800 (PST)
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4])
	by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id n0GK5GYI025619
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 16 Jan 2009 14:05:17 -0600 (CST)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1])
	by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	n0GK5GM0002392; Fri, 16 Jan 2009 12:05:16 -0800 (PST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	n0GK5FiW002349; Fri, 16 Jan 2009 12:05:16 -0800 (PST)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 16 Jan 2009 12:05:15 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 16 Jan 2009 12:05:14 -0800
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A10572584B@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <20090116172648.489456BE5B7@mercury.lcs.mit.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] No liveness requirement in the ID/Loc Split concept
Thread-Index: Acl4AT/rJ0uEcS3/RHSMgUf1gG7ZaQAFAJNQ
References: <20090116172648.489456BE5B7@mercury.lcs.mit.edu>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Noel Chiappa" <jnc@mercury.lcs.mit.edu>, <rrg@irtf.org>
X-OriginalArrivalTime: 16 Jan 2009 20:05:15.0413 (UTC)
	FILETIME=[BF31D450:01C97815]
Subject: Re: [rrg] No liveness requirement in the ID/Loc Split concept
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Noel,

>-----Original Message-----
>From: Noel Chiappa [mailto:jnc@mercury.lcs.mit.edu]
>Sent: Friday, January 16, 2009 9:27 AM
>To: rrg@irtf.org
>Cc: jnc@mercury.lcs.mit.edu
>Subject: Re: [rrg] No liveness requirement in the ID/Loc Split concept
>
>
>    > From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
>
>    > a LISP EID does _not_ name an interface, but rather a 'stack' -
i.e. an
>    > endpoint, with a collection of TCP connections.
>
>A private reply pointed out that a LISP EID in fact _also_ names an
>interface, just like an IPv4 address. That's a consequence of the fact
that a
>LISP design goal was to allow unmodified hosts, so one can only change
the
>semantics of existing namespaces a little.
>
>
>Interesting historical note: the Nimrod deployment plan:
>
>  http://ana-3.lcs.mit.edu/~jnc/nimrod/deploy.txt
>
>looked a lot like LISP's deployment plan - the existing IP layer was
'jacked
>up' and a new layer inserted underneath; unmodified hosts were unaware
that
>this all was happening, and continued to emit and receive classic IPv4
>packet; Nimrod agent-routers were responsible for invisibly translating
the
>IPv4 'addresses' in those packets into Nimrod locators, and doing the
>encapsulation. Although the Nimrod deployment plan spoke of turning
IPv4
>'addresses' into endpoint names (EIDs, to be exact - ironically), it's
clear
>that there, IPv4 addresses also retained minimal interface naming
semantics.
>
>
>It's almost inevitable, in any plan which supports unmodified hosts,
that
>the IPvN addresses used by those hosts will retain the basic semantics
of
>IPvN addresses.

If what LISP is calling an EID is indeed an IPvN address (it is)
then it is routable within a certain scope. Otherwise, all end
systems would have to also be xTRs, and we would have to get
into a messy discussion on strong vs. weak end system model.

Fred
fred.l.templin@boeing.com

>	Noel
>_______________________________________________
>rrg mailing list
>rrg@irtf.org
>http://www.irtf.org/mailman/listinfo/rrg
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Fri Jan 16 13:39:52 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 794113A6A55;
	Fri, 16 Jan 2009 13:39:52 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 861D73A6A55
	for <rrg@core3.amsl.com>; Fri, 16 Jan 2009 13:39:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.389
X-Spam-Level: 
X-Spam-Status: No, score=-103.389 tagged_above=-999 required=5
	tests=[AWL=0.210, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id OHFhqUeHbmIa for <rrg@core3.amsl.com>;
	Fri, 16 Jan 2009 13:39:50 -0800 (PST)
Received: from multicasttech.com (lennon.multicasttech.com [63.105.122.7])
	by core3.amsl.com (Postfix) with ESMTP id 570F43A695E
	for <rrg@irtf.org>; Fri, 16 Jan 2009 13:39:50 -0800 (PST)
Received: from [63.105.122.7] (account marshall_eubanks HELO [IPv6:::1])
	by multicasttech.com (CommuniGate Pro SMTP 3.4.8)
	with ESMTP-TLS id 14275405; Fri, 16 Jan 2009 16:39:23 -0500
Message-Id: <7CE9E43B-7459-4139-93F4-6BBC79959009@multicasttech.com>
From: Marshall Eubanks <tme@multicasttech.com>
To: David Conrad <drc@virtualized.org>
In-Reply-To: <C8E588B7-8AA9-49B7-AC2C-AC3E2CBEA4C0@virtualized.org>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Fri, 16 Jan 2009 16:39:31 -0500
References: <C8E588B7-8AA9-49B7-AC2C-AC3E2CBEA4C0@virtualized.org>
X-Mailer: Apple Mail (2.930.3)
Cc: RRG RG <rrg@irtf.org>
Subject: Re: [rrg] Apropos whether Moore's law can keep ahead of routing
	system growth
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Here is the PDF

<http://www.iop.org/EJ/article/1367-2630/10/12/123027/njp8_12_123027.pdf?request-id=0ed0b145-57ee-42d3-9d51-1805624f410f 
 >

Marshall


On Jan 16, 2009, at 2:09 PM, David Conrad wrote:

> http://www.physorg.com/print151162452.html
>
> Haven't read the actual paper this article summarizes (and I have to  
> admit some skepticism)...
>
> Regards,
> -drc
>
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> http://www.irtf.org/mailman/listinfo/rrg

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Fri Jan 16 13:42:46 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B28ED3A6AF7;
	Fri, 16 Jan 2009 13:42:46 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AA47F3A6AF7
	for <rrg@core3.amsl.com>; Fri, 16 Jan 2009 13:42:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.516
X-Spam-Level: 
X-Spam-Status: No, score=-6.516 tagged_above=-999 required=5 tests=[AWL=0.083, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id O0Uhne8xpQ+O for <rrg@core3.amsl.com>;
	Fri, 16 Jan 2009 13:42:45 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122])
	by core3.amsl.com (Postfix) with ESMTP id E96743A6A55
	for <rrg@irtf.org>; Fri, 16 Jan 2009 13:42:44 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178)
	id C00A56BE5F1; Fri, 16 Jan 2009 16:42:26 -0500 (EST)
To: rrg@irtf.org
Message-Id: <20090116214226.C00A56BE5F1@mercury.lcs.mit.edu>
Date: Fri, 16 Jan 2009 16:42:26 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [rrg] No liveness requirement in the ID/Loc Split concept
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

    > From: "Templin, Fred L" <Fred.L.Templin@boeing.com>

    > If what LISP is calling an EID is indeed an IPvN address (it is)

But it's not, not really, because it's not necessarily routable in a global
scope (depending on exactly where you are in the deployment process, e.g.
after routes to that part of the namespace have been withdrawn in the core).

Also, in later phases of the development of the network, depending on exactly
what happens (e.g. if we start to move the xTR functionality into first/last-
hop routers), some/most/all instances of legacy IPvN 'addresses' might have
zero routing functionality.

We're trying to fit these things into too few, Procrustean, terminological
bins (and having impressively useless debates in doing so). Best to describe
in detail exactly what the properties of a given namespace, in a particular
design, are, and leave aside the angels-on-pins arguments about what category
they fall into.

	Noel
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Fri Jan 16 14:29:35 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 08E163A6AFE;
	Fri, 16 Jan 2009 14:29:35 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E54D93A6AFE
	for <rrg@core3.amsl.com>; Fri, 16 Jan 2009 14:29:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.423
X-Spam-Level: 
X-Spam-Status: No, score=-6.423 tagged_above=-999 required=5 tests=[AWL=0.176, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id B0r77pksxAt5 for <rrg@core3.amsl.com>;
	Fri, 16 Jan 2009 14:29:33 -0800 (PST)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com
	[130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id 26D153A69DA
	for <rrg@irtf.org>; Fri, 16 Jan 2009 14:29:33 -0800 (PST)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6])
	by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id n0GMTAhB000948
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);
	Fri, 16 Jan 2009 14:29:12 -0800 (PST)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	n0GMT9mZ017513; Fri, 16 Jan 2009 16:29:09 -0600 (CST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	n0GMSuif017187; Fri, 16 Jan 2009 16:29:09 -0600 (CST)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 16 Jan 2009 14:29:08 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 16 Jan 2009 14:29:07 -0800
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A10572598B@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <20090116214226.C00A56BE5F1@mercury.lcs.mit.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] No liveness requirement in the ID/Loc Split concept
Thread-Index: Acl4I1cxZRhZmS5pTEaVUf4t3JaywgABO2gA
References: <20090116214226.C00A56BE5F1@mercury.lcs.mit.edu>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Noel Chiappa" <jnc@mercury.lcs.mit.edu>, <rrg@irtf.org>
X-OriginalArrivalTime: 16 Jan 2009 22:29:08.0250 (UTC)
	FILETIME=[D8C437A0:01C97829]
Subject: Re: [rrg] No liveness requirement in the ID/Loc Split concept
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org



>-----Original Message-----
>From: Noel Chiappa [mailto:jnc@mercury.lcs.mit.edu]
>Sent: Friday, January 16, 2009 1:42 PM
>To: rrg@irtf.org
>Cc: jnc@mercury.lcs.mit.edu
>Subject: Re: [rrg] No liveness requirement in the ID/Loc Split concept
>
>
>    > From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
>
>    > If what LISP is calling an EID is indeed an IPvN address (it is)
>
>But it's not, not really,

It's not really an IPvN address? Does it say that somewhere?

Fred
fred.l.templin@boeing.com

>because it's not necessarily routable in a global
>scope (depending on exactly where you are in the deployment process,
e.g.
>after routes to that part of the namespace have been withdrawn in the
core).
>
>Also, in later phases of the development of the network, depending on
exactly
>what happens (e.g. if we start to move the xTR functionality into
first/last-
>hop routers), some/most/all instances of legacy IPvN 'addresses' might
have
>zero routing functionality.
>
>We're trying to fit these things into too few, Procrustean,
terminological
>bins (and having impressively useless debates in doing so). Best to
describe
>in detail exactly what the properties of a given namespace, in a
particular
>design, are, and leave aside the angels-on-pins arguments about what
category
>they fall into.
>
>	Noel
>_______________________________________________
>rrg mailing list
>rrg@irtf.org
>http://www.irtf.org/mailman/listinfo/rrg
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Fri Jan 16 18:53:27 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 788F83A69FD;
	Fri, 16 Jan 2009 18:53:27 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EADBD3A69FD
	for <rrg@core3.amsl.com>; Fri, 16 Jan 2009 18:53:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[AWL=0.063, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6nqhNM7+Mbq6 for <rrg@core3.amsl.com>;
	Fri, 16 Jan 2009 18:53:26 -0800 (PST)
Received: from QMTA05.westchester.pa.mail.comcast.net
	(qmta05.westchester.pa.mail.comcast.net [76.96.62.48])
	by core3.amsl.com (Postfix) with ESMTP id CF10F3A689F
	for <rrg@irtf.org>; Fri, 16 Jan 2009 18:53:25 -0800 (PST)
Received: from OMTA11.westchester.pa.mail.comcast.net ([76.96.62.36])
	by QMTA05.westchester.pa.mail.comcast.net with comcast
	id 4Qo91b0060mv7h055St6X6; Sat, 17 Jan 2009 02:53:06 +0000
Received: from TONYLTM9XP ([155.53.41.237])
	by OMTA11.westchester.pa.mail.comcast.net with comcast
	id 4Ssr1b00P570qEr3XSsuf1; Sat, 17 Jan 2009 02:53:04 +0000
From: "Tony Li" <tony.li@tony.li>
To: "'Marshall Eubanks'" <tme@multicasttech.com>,
	"'David Conrad'" <drc@virtualized.org>
References: <C8E588B7-8AA9-49B7-AC2C-AC3E2CBEA4C0@virtualized.org>
	<7CE9E43B-7459-4139-93F4-6BBC79959009@multicasttech.com>
Date: Fri, 16 Jan 2009 18:52:13 -0800
Message-ID: <E0206F4FF526485E8B6190D6C30689A0@ad.redback.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <7CE9E43B-7459-4139-93F4-6BBC79959009@multicasttech.com>
Thread-Index: Acl4IvMgApUwqXRnTIeA6+CloV6vSwAK2fmQ
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Cc: 'RRG RG' <rrg@irtf.org>
Subject: Re: [rrg] Apropos whether Moore's law can keep ahead of
	routingsystem growth
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tony.li@tony.li
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

 

|Here is the PDF
|
|<http://www.iop.org/EJ/article/1367-2630/10/12/123027/njp8_12_1
|23027.pdf?request-id=0ed0b145-57ee-42d3-9d51-1805624f410f 
| >
|
|> http://www.physorg.com/print151162452.html
|>
|> Haven't read the actual paper this article summarizes (and I 
|have to  
|> admit some skepticism)...


I brief read show very interesting graph-theoretic properties about the
topology of the Internet.  However, as we all know, the topology and the
addressing (and thus routing) today are only loosely coupled.  Concerning
our problem, I didn't find anything here particularly compelling.

Tony

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sun Jan 18 18:28:25 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BB2B33A69EB;
	Sun, 18 Jan 2009 18:28:25 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 088983A69EB
	for <rrg@core3.amsl.com>; Sun, 18 Jan 2009 18:28:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.5
X-Spam-Level: 
X-Spam-Status: No, score=-2.5 tagged_above=-999 required=5 tests=[AWL=0.099,
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ccGXbuHdGBfa for <rrg@core3.amsl.com>;
	Sun, 18 Jan 2009 18:28:23 -0800 (PST)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.227])
	by core3.amsl.com (Postfix) with ESMTP id 2BE7A3A68C9
	for <rrg@irtf.org>; Sun, 18 Jan 2009 18:28:23 -0800 (PST)
Received: by rv-out-0506.google.com with SMTP id f6so2882727rvb.7
	for <rrg@irtf.org>; Sun, 18 Jan 2009 18:28:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from
	:organization:user-agent:mime-version:to:cc:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=wr4SlF0zJYv9xTBOsObYmB8bYPl7hawpInIgB7vUjlo=;
	b=hpwZ0IVF3WSkcMQ+ajbgJB1ZsPtNer7MsfkfdoHGPVnn3131uW/7YyhibLashZ5s8o
	p87NeVCNBaEUPBOoN43rIzta4a18xSQRFnjKlv1XvEW7+CMphedsXoaiW8Swn8kxXDWJ
	SekrofpZR43F9/Wsf7M1O3vnp6zpkEu8iez08=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	b=ZefSURG0jdKv9/DwOfaIySO8E6RvQIYruTRLRyEBDCMNbSKZFTMchUETtvwxB5IsjF
	nHV480g+vIEMYf1RLLjU/O04gUf77BqKYpSAxhtDEh242nwH1vrfoLpV18tcU7ZUrq5Q
	zjG8Fvcg4m6Y1PcyWCXvyh+WHug++IQcOwanc=
Received: by 10.141.48.6 with SMTP id a6mr2560020rvk.161.1232332086352;
	Sun, 18 Jan 2009 18:28:06 -0800 (PST)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz
	[130.216.38.124])
	by mx.google.com with ESMTPS id f21sm8900506rvb.7.2009.01.18.18.28.04
	(version=SSLv3 cipher=RC4-MD5); Sun, 18 Jan 2009 18:28:05 -0800 (PST)
Message-ID: <4973E52E.8000407@gmail.com>
Date: Mon, 19 Jan 2009 15:27:58 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
References: <20090116054647.626B56BE594@mercury.lcs.mit.edu>
In-Reply-To: <20090116054647.626B56BE594@mercury.lcs.mit.edu>
Cc: rrg@irtf.org
Subject: Re: [rrg] No liveness requirement in the ID/Loc Split concept
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Noel,

On 2009-01-16 18:46, Noel Chiappa wrote:
...
> There is no one-word description/term which _exactly_ describes a LISP EID;
> it's a bit of a kludge (precisely because of installed base issues). To be
> maximally precise, a LISP 'EID' is 'a globally-unique endpoint name with
> topological significance within a local scope only'.

I totally agree with that. My understanding of 'EID' has always
been that it has no topological significance at all, and indeed
that it identifies a stack rather than an interface. That's
where I'm quarrelling with the LISP usage.

It's a shame that draft-irtf-nsrg-report never made it.

    Brian
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Sun Jan 18 23:23:42 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5361128C158;
	Sun, 18 Jan 2009 23:23:42 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4D06F3A676A
	for <rrg@core3.amsl.com>; Sun, 18 Jan 2009 23:23:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id D5KDuLw4QMiy for <rrg@core3.amsl.com>;
	Sun, 18 Jan 2009 23:23:40 -0800 (PST)
Received: from n2.nomadiclab.com (n2.nomadiclab.com
	[IPv6:2001:14b8:400:101::2])
	by core3.amsl.com (Postfix) with ESMTP id C92C928C107
	for <rrg@irtf.org>; Sun, 18 Jan 2009 23:23:38 -0800 (PST)
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 8A0991F3572
	for <rrg@irtf.org>; Mon, 19 Jan 2009 09:23:21 +0200 (EET)
Received: from [127.0.0.1] (localhost [IPv6:::1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 133311F3571
	for <rrg@irtf.org>; Mon, 19 Jan 2009 09:23:21 +0200 (EET)
Message-Id: <B25790E2-8D3C-4A55-848C-F461982DC3F6@nomadiclab.com>
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
To: RRG <rrg@irtf.org>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Mon, 19 Jan 2009 08:23:19 +0100
X-Mailer: Apple Mail (2.930.3)
X-Virus-Scanned: ClamAV using ClamSMTP
Subject: [rrg] Why a host-based solution does not necessarily add signalling
	load
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

One of the repeated arguments against host-based solution is that it  =

increases signalling load.  Of course, that is true for a pure host- =

based solution where each host individually maintains the mapping from  =

EIDs to RLOCs.  So, from a signalling load point of view, such a  =

solution is not very good if the mapping granularity is at the site  =

level.

There is a relatively easy solution to this, which brings the inter- =

site signalling load to the level of tunnel-router-like maps-and- =

encaps solution.  The basic idea is that the hosts *delegate* the  =

signalling to a tunnel-router-like device at the site border.  (At the  =

same time, the hosts can still signal individually through another  =

interface; consider e.g. a laptop which is attached with a wire to a  =

corporate site but at the same time has a wireless interface using an  =

open WLAN.)

So, when both a host and a site support a (multi-homing/mobility)  =

solution, the following can be done:

1. The host detects that the site supports the solution, e.g. through  =

DHCP/ND.
2. The host delegates any mobility/multihoming/tunnelling signalling  =

to the TR at the site.
3. The site border TR/whatever takes care of signalling on the host's  =

behalf.

When considering HIP, the theory is discussed in length in Jukka  =

Ylitalo's Ph.D.
http://lib.tkk.fi/Diss/2008/isbn9789512295319/

For a practical example, see Section 4 of draft-melen-hip-mr-01.txt

For measurement results, see Jukka Ylitalo, Jan Mel=E9n, Patrik Salmela,  =

and Henrik Petander, "An Experimental Evaluation of a HIP based  =

Network Mobility Scheme", in Proc. of the 6th International Conference  =

on Wired/Wireless Internet Communications (WWIC 2008), pp. 139-151,

--Pekka Nikander

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan 19 12:49:32 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 695D328C1C4;
	Mon, 19 Jan 2009 12:49:32 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8F96928C1C4
	for <rrg@core3.amsl.com>; Mon, 19 Jan 2009 12:49:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.503
X-Spam-Level: 
X-Spam-Status: No, score=-2.503 tagged_above=-999 required=5 tests=[AWL=0.096, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 1-LDgVuDh5lN for <rrg@core3.amsl.com>;
	Mon, 19 Jan 2009 12:49:30 -0800 (PST)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.224])
	by core3.amsl.com (Postfix) with ESMTP id 2FD7928C1B2
	for <rrg@irtf.org>; Mon, 19 Jan 2009 12:49:30 -0800 (PST)
Received: by rv-out-0506.google.com with SMTP id f6so3289981rvb.7
	for <rrg@irtf.org>; Mon, 19 Jan 2009 12:49:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from
	:organization:user-agent:mime-version:to:cc:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=ZmBysCS/sU6nhd+HdaoRKqKhe5Dx7RRflbvojrq75BY=;
	b=AM01pFEuIimL7fO3CkdGm48HtGltB6v8rKqhtxYkx0x0cFK3P/UMEl0FfcKvkaKZDa
	mm7B9Ev3odfz3I/CsPqwzTORThAtCw6+2kikagz0YkRW/gOPjMHexAgVil6zfz560vsR
	aOLwBLgfyVisyZClGtaXomL4rXAYnJWbhHhCA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	b=yDEV4nwV7bb6hJ/SKj+hrm3BY2HRnaRBhcT9kVseYre9mcneFJzUm3IoRfsV4/O8mq
	glNZqDIYlKpyj2Hxc7H2LIGMgMMCwjnSKIlsdxlPynlNNfcgp0MVsBqwyvEj98VyUIwe
	k45ZLIG9Q2Slb2EixtosyZOUJ+c4LTX3ONMC0=
Received: by 10.140.186.20 with SMTP id j20mr61793rvf.236.1232398153279;
	Mon, 19 Jan 2009 12:49:13 -0800 (PST)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz
	[130.216.38.124])
	by mx.google.com with ESMTPS id k41sm4707734rvb.3.2009.01.19.12.49.12
	(version=SSLv3 cipher=RC4-MD5); Mon, 19 Jan 2009 12:49:12 -0800 (PST)
Message-ID: <4974E744.7030607@gmail.com>
Date: Tue, 20 Jan 2009 09:49:08 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Pekka Nikander <pekka.nikander@nomadiclab.com>
References: <B25790E2-8D3C-4A55-848C-F461982DC3F6@nomadiclab.com>
In-Reply-To: <B25790E2-8D3C-4A55-848C-F461982DC3F6@nomadiclab.com>
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] Why a host-based solution does not necessarily add
 signalling load
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

UGVra2EsCgpPbiAyMDA5LTAxLTE5IDIwOjIzLCBQZWtrYSBOaWthbmRlciB3cm90ZToKPiBPbmUg
b2YgdGhlIHJlcGVhdGVkIGFyZ3VtZW50cyBhZ2FpbnN0IGhvc3QtYmFzZWQgc29sdXRpb24gaXMg
dGhhdCBpdAo+IGluY3JlYXNlcyBzaWduYWxsaW5nIGxvYWQuICBPZiBjb3Vyc2UsIHRoYXQgaXMg
dHJ1ZSBmb3IgYSBwdXJlCj4gaG9zdC1iYXNlZCBzb2x1dGlvbiB3aGVyZSBlYWNoIGhvc3QgaW5k
aXZpZHVhbGx5IG1haW50YWlucyB0aGUgbWFwcGluZwo+IGZyb20gRUlEcyB0byBSTE9Dcy4gIFNv
LCBmcm9tIGEgc2lnbmFsbGluZyBsb2FkIHBvaW50IG9mIHZpZXcsIHN1Y2ggYQo+IHNvbHV0aW9u
IGlzIG5vdCB2ZXJ5IGdvb2QgaWYgdGhlIG1hcHBpbmcgZ3JhbnVsYXJpdHkgaXMgYXQgdGhlIHNp
dGUgbGV2ZWwuCj4gCj4gVGhlcmUgaXMgYSByZWxhdGl2ZWx5IGVhc3kgc29sdXRpb24gdG8gdGhp
cywgd2hpY2ggYnJpbmdzIHRoZSBpbnRlci1zaXRlCj4gc2lnbmFsbGluZyBsb2FkIHRvIHRoZSBs
ZXZlbCBvZiB0dW5uZWwtcm91dGVyLWxpa2UgbWFwcy1hbmQtZW5jYXBzCj4gc29sdXRpb24uICBU
aGUgYmFzaWMgaWRlYSBpcyB0aGF0IHRoZSBob3N0cyAqZGVsZWdhdGUqIHRoZSBzaWduYWxsaW5n
IHRvCj4gYSB0dW5uZWwtcm91dGVyLWxpa2UgZGV2aWNlIGF0IHRoZSBzaXRlIGJvcmRlci4gIAoK
UmFuIEF0a2luc29uIGhhcyBvYnNlcnZlZCB0aGF0IGZvciBJUHY2LCBSQSBtZXNzYWdlcyBjb3Vs
ZCBiZSB1c2VkIGFzIGEKd2F5IHRvIGluZGljYXRlIHByZWZpeCAibGl2ZW5lc3MiIGluIHJlYWwg
dGltZSAoc2VlIHNlY3Rpb24gMi4zIG9mCmRyYWZ0LWNhcnBlbnRlci1yZW51bS1uZWVkcy13b3Jr
LTAxKS4gTm8gZG91YnQgYSBzaW1pbGFyIG1lY2hhbmlzbSBjb3VsZApiZSByZXRyb2ZpdHRlZCB0
byBJUHY0LiBUaGF0IHdvdWxkIG1ha2UgaXQgZXF1YWxseSBwb3NzaWJsZSB0byBkZWxlZ2F0ZQp0
aGUgbGl2ZW5lc3MgZnVuY3Rpb24sIGlmIG5lZWRlZCwgdG8gdGhlIGJvcmRlciBkZXZpY2UuCgog
ICAgQnJpYW4KCj4gKEF0IHRoZSBzYW1lIHRpbWUsIHRoZQo+IGhvc3RzIGNhbiBzdGlsbCBzaWdu
YWwgaW5kaXZpZHVhbGx5IHRocm91Z2ggYW5vdGhlciBpbnRlcmZhY2U7IGNvbnNpZGVyCj4gZS5n
LiBhIGxhcHRvcCB3aGljaCBpcyBhdHRhY2hlZCB3aXRoIGEgd2lyZSB0byBhIGNvcnBvcmF0ZSBz
aXRlIGJ1dCBhdAo+IHRoZSBzYW1lIHRpbWUgaGFzIGEgd2lyZWxlc3MgaW50ZXJmYWNlIHVzaW5n
IGFuIG9wZW4gV0xBTi4pCj4gCj4gU28sIHdoZW4gYm90aCBhIGhvc3QgYW5kIGEgc2l0ZSBzdXBw
b3J0IGEgKG11bHRpLWhvbWluZy9tb2JpbGl0eSkKPiBzb2x1dGlvbiwgdGhlIGZvbGxvd2luZyBj
YW4gYmUgZG9uZToKPiAKPiAxLiBUaGUgaG9zdCBkZXRlY3RzIHRoYXQgdGhlIHNpdGUgc3VwcG9y
dHMgdGhlIHNvbHV0aW9uLCBlLmcuIHRocm91Z2gKPiBESENQL05ELgo+IDIuIFRoZSBob3N0IGRl
bGVnYXRlcyBhbnkgbW9iaWxpdHkvbXVsdGlob21pbmcvdHVubmVsbGluZyBzaWduYWxsaW5nIHRv
Cj4gdGhlIFRSIGF0IHRoZSBzaXRlLgo+IDMuIFRoZSBzaXRlIGJvcmRlciBUUi93aGF0ZXZlciB0
YWtlcyBjYXJlIG9mIHNpZ25hbGxpbmcgb24gdGhlIGhvc3Qncwo+IGJlaGFsZi4KPiAKPiBXaGVu
IGNvbnNpZGVyaW5nIEhJUCwgdGhlIHRoZW9yeSBpcyBkaXNjdXNzZWQgaW4gbGVuZ3RoIGluIEp1
a2thCj4gWWxpdGFsbydzIFBoLkQuCj4gaHR0cDovL2xpYi50a2suZmkvRGlzcy8yMDA4L2lzYm45
Nzg5NTEyMjk1MzE5Lwo+IAo+IEZvciBhIHByYWN0aWNhbCBleGFtcGxlLCBzZWUgU2VjdGlvbiA0
IG9mIGRyYWZ0LW1lbGVuLWhpcC1tci0wMS50eHQKPiAKPiBGb3IgbWVhc3VyZW1lbnQgcmVzdWx0
cywgc2VlIEp1a2thIFlsaXRhbG8sIEphbiBNZWzDqW4sIFBhdHJpayBTYWxtZWxhLAo+IGFuZCBI
ZW5yaWsgUGV0YW5kZXIsICJBbiBFeHBlcmltZW50YWwgRXZhbHVhdGlvbiBvZiBhIEhJUCBiYXNl
ZCBOZXR3b3JrCj4gTW9iaWxpdHkgU2NoZW1lIiwgaW4gUHJvYy4gb2YgdGhlIDZ0aCBJbnRlcm5h
dGlvbmFsIENvbmZlcmVuY2Ugb24KPiBXaXJlZC9XaXJlbGVzcyBJbnRlcm5ldCBDb21tdW5pY2F0
aW9ucyAoV1dJQyAyMDA4KSwgcHAuIDEzOS0xNTEsCj4gCj4gLS1QZWtrYSBOaWthbmRlcgo+IAo+
IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCj4gcnJnIG1h
aWxpbmcgbGlzdAo+IHJyZ0BpcnRmLm9yZwo+IGh0dHA6Ly93d3cuaXJ0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby9ycmcKPiAKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fCnJyZyBtYWlsaW5nIGxpc3QKcnJnQGlydGYub3JnCmh0dHA6Ly93d3cuaXJ0Zi5vcmcv
bWFpbG1hbi9saXN0aW5mby9ycmcK


From rrg-bounces@irtf.org  Mon Jan 19 13:37:24 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 415EC3A6864;
	Mon, 19 Jan 2009 13:37:24 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 29CD63A6852
	for <rrg@core3.amsl.com>; Mon, 19 Jan 2009 13:37:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.521
X-Spam-Level: 
X-Spam-Status: No, score=-6.521 tagged_above=-999 required=5 tests=[AWL=0.078, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id vuw12HcDGJBb for <rrg@core3.amsl.com>;
	Mon, 19 Jan 2009 13:37:22 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 0A5753A6806
	for <rrg@irtf.org>; Mon, 19 Jan 2009 13:37:21 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,290,1231113600"; d="scan'208";a="34204075"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 19 Jan 2009 21:37:05 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n0JLb5kx007314; 
	Mon, 19 Jan 2009 16:37:05 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n0JLb5co019269;
	Mon, 19 Jan 2009 21:37:05 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 19 Jan 2009 16:37:05 -0500
Received: from cisco.com ([64.102.8.172]) by xfe-rtp-202.amer.cisco.com with
	Microsoft SMTPSVC(6.0.3790.1830); Mon, 19 Jan 2009 16:37:04 -0500
Date: Mon, 19 Jan 2009 16:37:01 -0500
From: Scott Brim <swb@employees.org>
To: Pekka Nikander <pekka.nikander@nomadiclab.com>
Message-ID: <20090119213701.GA34129@cisco.com>
Mail-Followup-To: Scott Brim <swb@employees.org>,
	Pekka Nikander <pekka.nikander@nomadiclab.com>, RRG <rrg@irtf.org>
References: <B25790E2-8D3C-4A55-848C-F461982DC3F6@nomadiclab.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <B25790E2-8D3C-4A55-848C-F461982DC3F6@nomadiclab.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-OriginalArrivalTime: 19 Jan 2009 21:37:05.0191 (UTC)
	FILETIME=[12847B70:01C97A7E]
Authentication-Results: rtp-dkim-2; header.From=swb@employees.org; dkim=neutral
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] Why a host-based solution does not necessarily
	add	signalling load
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Excerpts from Pekka Nikander on Mon, Jan 19, 2009 08:23:19AM +0100:
> One of the repeated arguments against host-based solution is that it
> increases signalling load.  Of course, that is true for a pure host-
> based solution where each host individually maintains the mapping
> from  EIDs to RLOCs.  So, from a signalling load point of view, such
> a  solution is not very good if the mapping granularity is at the
> site  level.
>
> There is a relatively easy solution to this, which brings the
> inter-site signalling load to the level of tunnel-router-like
> maps-and-encaps solution.  The basic idea is that the hosts
> *delegate* the signalling to a tunnel-router-like device at the site
> border.  (At the same time, the hosts can still signal individually
> through another interface; consider e.g. a laptop which is attached
> with a wire to a corporate site but at the same time has a wireless
> interface using an open WLAN.)
>
> So, when both a host and a site support a (multi-homing/mobility)
> solution, the following can be done:
>
> 1. The host detects that the site supports the solution, e.g.
>    through  DHCP/ND.
> 2. The host delegates any mobility/multihoming/tunnelling signalling
>    to the TR at the site.
> 3. The site border TR/whatever takes care of signalling on the
>    host's  behalf.

Pekka, I don't think this is a win.  =


As an endpoint, you are interested in reachability of specific
endpoints.  You don't care if a whole prefix is reachable, if the
particular endpoint isn't reachable within that prefix.  So if you
delegate liveness monitoring to an agent, you are asking it to monitor
specific locators.  =


First of all the number of locators that need to be monitored does not
decrease.  The problem is a lack of parallelism between the different
sides of the transaction.  Intermediaries like ITRs and ETRs can
monitor the health of interfaces to whole prefixes, since that is what
they are responsible for.  Endpoints are responsible for communication
with other endpoints, not just prefixes, so that is the information
they need.

Second, as Fred Baker pointed out in many cases exchanges are short
and you don't need probing or monitoring, and in some cases there may
be different "grades" of continuity required which may allow "relaxed"
monitoring ... but a liveness agent won't be able to keep track of
that nearly as well as endpoints, so it will over-probe unnecessarily.

Does that make sense?  Do I understand correctly?

> When considering HIP, the theory is discussed in length in Jukka
> Ylitalo's Ph.D.  http://lib.tkk.fi/Diss/2008/isbn9789512295319/
>
> For a practical example, see Section 4 of draft-melen-hip-mr-01.txt
>
> For measurement results, see Jukka Ylitalo, Jan Mel=E9n, Patrik
> Salmela,  and Henrik Petander, "An Experimental Evaluation of a HIP
> based Network Mobility Scheme", in Proc. of the 6th International
> Conference on Wired/Wireless Internet Communications (WWIC 2008),
> pp. 139-151,

I'll take a look.

Scott
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan 19 16:01:18 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1A2C93A6A6D;
	Mon, 19 Jan 2009 16:01:18 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2736D3A6A6C
	for <rrg@core3.amsl.com>; Mon, 19 Jan 2009 16:01:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.506
X-Spam-Level: 
X-Spam-Status: No, score=-2.506 tagged_above=-999 required=5 tests=[AWL=0.093, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id CbiyBHW7iRbQ for <rrg@core3.amsl.com>;
	Mon, 19 Jan 2009 16:01:16 -0800 (PST)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.230])
	by core3.amsl.com (Postfix) with ESMTP id 6CFC63A6A5A
	for <rrg@irtf.org>; Mon, 19 Jan 2009 16:01:16 -0800 (PST)
Received: by rv-out-0506.google.com with SMTP id f6so3371466rvb.7
	for <rrg@irtf.org>; Mon, 19 Jan 2009 16:01:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from
	:organization:user-agent:mime-version:to:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=AqIxIdrtzhnhhXua5znC170MBcZQEHBwUllUhHWAclg=;
	b=N4gCiFG3KVvO/36TL5uWkF6WL7iy2JT1lZUmKC7gI2MV3tlhzdf23N/vLHWbIqJNoW
	GjXvGTyp47spqR7t3w1pGKl1moLzQP/5dUe6OH9HG1nz2zNqA4ZCmavLdIedWW2BpKNi
	t+AyKuopya/IyHpppu1c9fNVBuOgcGUu/87p0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	b=f1zDSP1MQ150JmZaVXDv7Z7euy9jNvliuAFWXvYvSgxfCMHkp4hCDWwRVL7BrKfK62
	uwMbqecOgCjhBtEeNiosOZQsXnKmUFQZhDrHbCSEDiX7CJSJ9kw6Je0ilucQbnSG0x7c
	GGq5IBL4KONnme1M3imKmqAzwTVY6Rvl8l2zY=
Received: by 10.141.44.13 with SMTP id w13mr3062237rvj.275.1232409660376;
	Mon, 19 Jan 2009 16:01:00 -0800 (PST)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz
	[130.216.38.124])
	by mx.google.com with ESMTPS id l31sm11221778rvb.2.2009.01.19.16.00.58
	(version=SSLv3 cipher=RC4-MD5); Mon, 19 Jan 2009 16:01:00 -0800 (PST)
Message-ID: <4975143E.9020404@gmail.com>
Date: Tue, 20 Jan 2009 13:01:02 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Scott Brim <swb@employees.org>, 
	Pekka Nikander <pekka.nikander@nomadiclab.com>, RRG <rrg@irtf.org>
References: <B25790E2-8D3C-4A55-848C-F461982DC3F6@nomadiclab.com>
	<20090119213701.GA34129@cisco.com>
In-Reply-To: <20090119213701.GA34129@cisco.com>
Subject: Re: [rrg] Why a host-based solution does not
 necessarily	add	signalling load
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Scott,

> As an endpoint, you are interested in reachability of specific
> endpoints.  You don't care if a whole prefix is reachable, if the
> particular endpoint isn't reachable within that prefix.  So if you
> delegate liveness monitoring to an agent, you are asking it to monitor
> specific locators. 

The e2e principle seems to make it clear that, ultimately, liveness is
the endpoint's responsibility, but that is usually interpreted as a
statement about what the transport layer or above should do. And they
already do it, 100% independently of what we do in layer 3 and below.
I think that limiting layer 3 liveness detection to the prefix level
(except presumably in the case of Mobile IP) is a perfectly good
engineering compromise, unless we're planning to repudiate [Saltzer].

    Brian

[Saltzer] End-To-End Arguments in System Design, J.H. Saltzer,
   D.P.Reed, D.D.Clark, ACM TOCS, Vol 2, Number 4, November 1984, pp
   277-288.
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Mon Jan 19 17:58:14 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4AB783A6A78;
	Mon, 19 Jan 2009 17:58:14 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4176928C1E5
	for <rrg@core3.amsl.com>; Mon, 19 Jan 2009 17:58:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.499
X-Spam-Level: 
X-Spam-Status: No, score=-3.499 tagged_above=-999 required=5 tests=[AWL=0.100, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 4LRC5TLQIuNo for <rrg@core3.amsl.com>;
	Mon, 19 Jan 2009 17:58:12 -0800 (PST)
Received: from hermes.mail.tigertech.net (hermes.mail.tigertech.net
	[64.62.209.72]) by core3.amsl.com (Postfix) with ESMTP id 644C63A6A78
	for <rrg@irtf.org>; Mon, 19 Jan 2009 17:58:12 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by hermes.tigertech.net (Postfix) with ESMTP id ADC344302A4;
	Mon, 19 Jan 2009 17:57:56 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at hermes.tigertech.net
Received: from [10.10.10.100] (pool-71-161-51-64.clppva.btas.verizon.net
	[71.161.51.64])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by hermes.tigertech.net (Postfix) with ESMTP id A365143029E;
	Mon, 19 Jan 2009 17:57:55 -0800 (PST)
Message-ID: <49752F9C.4050006@joelhalpern.com>
Date: Mon, 19 Jan 2009 20:57:48 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <B25790E2-8D3C-4A55-848C-F461982DC3F6@nomadiclab.com>	<20090119213701.GA34129@cisco.com>
	<4975143E.9020404@gmail.com>
In-Reply-To: <4975143E.9020404@gmail.com>
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] Why a host-based solution does not
 necessarily	add	signalling load
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

There are a couple of different issues, that are all too easy to 
confuse.  (No, I don't think Brian, Scott, Dave, etc. have individually 
confused them.  But I think that the discussion may have switched from 
one to another unintentionally.

There are prefixes on RLocs.  Such prefixes appear in routing.  Clearly, 
the presence of such a prefix in routing does not tell you enough to 
judge the reachability or liveness of an individual xTR within that 
prefix.  (The absence of a prefix, that's useful.  But that's the easy 
part of the problem.)

As far as I know, in terms of liveness testing of ETRs, there is no 
granularity finer than the ETR to test.  So if we are using an ID / RLoc 
split, the liveness testing we are interested in is the reachability / 
efficacy of a given ETR.  [There is the additional complication of the 
ETR being live, but not having reachability to the endpoint.  That is a 
different problem than the liveness problem described in the draft. 
There are many additional problems...)

Conversely, although the liveness testing must be on the basis of 
individual ETRs, it does seem likely that many hosts in a site will be 
trying to reach endpoints behind the same set of ETRs.  As such, having 
a border guy (or someone else, if you really want to complicate life) 
testing / monitoring that liveness / reachability on behalf of the 
various sources within the site would seem likely to
1) reduce the probing traffic
2) increase the odds of having accurate data when packets need to be sent.

Yours,
Joel

Brian E Carpenter wrote:
> Scott,
> 
>> As an endpoint, you are interested in reachability of specific
>> endpoints.  You don't care if a whole prefix is reachable, if the
>> particular endpoint isn't reachable within that prefix.  So if you
>> delegate liveness monitoring to an agent, you are asking it to monitor
>> specific locators. 
> 
> The e2e principle seems to make it clear that, ultimately, liveness is
> the endpoint's responsibility, but that is usually interpreted as a
> statement about what the transport layer or above should do. And they
> already do it, 100% independently of what we do in layer 3 and below.
> I think that limiting layer 3 liveness detection to the prefix level
> (except presumably in the case of Mobile IP) is a perfectly good
> engineering compromise, unless we're planning to repudiate [Saltzer].
> 
>     Brian
> 
> [Saltzer] End-To-End Arguments in System Design, J.H. Saltzer,
>    D.P.Reed, D.D.Clark, ACM TOCS, Vol 2, Number 4, November 1984, pp
>    277-288.
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> http://www.irtf.org/mailman/listinfo/rrg
> 
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Tue Jan 20 01:40:07 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DA6E728C0DB;
	Tue, 20 Jan 2009 01:40:07 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E135C28C0DB
	for <rrg@core3.amsl.com>; Tue, 20 Jan 2009 01:40:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.805
X-Spam-Level: 
X-Spam-Status: No, score=-1.805 tagged_above=-999 required=5 tests=[AWL=1.397, 
	BAYES_00=-2.599, GB_I_INVITATION=-2, HTML_MESSAGE=0.001,
	MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id CM-YlEiMEZ6l for <rrg@core3.amsl.com>;
	Tue, 20 Jan 2009 01:40:05 -0800 (PST)
Received: from imo-m22.mail.aol.com (imo-m22.mx.aol.com [64.12.137.3])
	by core3.amsl.com (Postfix) with ESMTP id 871773A6AFE
	for <rrg@irtf.org>; Tue, 20 Jan 2009 01:40:05 -0800 (PST)
Received: from HeinerHummel@aol.com
	by imo-m22.mx.aol.com  (mail_out_v39.1.) id t.c8a.32775060 (29673);
	Tue, 20 Jan 2009 04:39:39 -0500 (EST)
From: HeinerHummel@aol.com
Message-ID: <c8a.32775060.36a6f5db@aol.com>
Date: Tue, 20 Jan 2009 04:39:39 EST
To: jmh@joelhalpern.com, brian.e.carpenter@gmail.com
MIME-Version: 1.0
X-Mailer: 9.0 SE for Windows sub 5021
Cc: rrg@irtf.org
Subject: Re: [rrg] Why a host-based solution does not necessarily add
	signalling load
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1761094319=="
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org


--===============1761094319==
Content-Type: multipart/alternative; boundary="-----------------------------1232444379"


-------------------------------1232444379
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

In einer eMail vom 20.01.2009 02:58:08 Westeurop=E4ische Normalzeit schreibt=
 =20
jmh@joelhalpern.com:

As far  as I know, in terms of liveness testing of ETRs, there is no=20
granularity  finer than the ETR to test.  So if we are using an ID / RLoc=20
split,  the liveness testing we are interested in is the reachability /=20
efficacy  of a given ETR.  [There is the additional complication of the=20
ETR  being live, but not having reachability to the endpoint.  That is a =20
different problem than the liveness problem described in the draft. =20
There are many additional problems...)
...with strategy A   and B.  But back to this liveness  issue:
=20
If I want to drive/route from NY/Broadway to Sausolito / Main  Street my bes=
t=20
next hop might be derived from a proxy destination node in  L.A.(because the=
=20
US country map doesn't show the Main Street of  Sausolito) While doing so wh=
y=20
should I care for the liveness of this  L.A.-router ?!
Getting closer some S.F. -router might turn out to be the actual proxy  dest=
.=20
And that one might be ignored, too, getting still closer. Will say:  Problem=
=20
after problem which do not apply to strategy C.
=20
Further point: Now the Compact Routing experts may investigate stretch-ETR =20
:-)=20
Factor 17 was so far the biggest stretch value I have read. How big is =20
stretch-ETR ?
=20
Further point:
Mobile homing in combination with mobility. With this respect strategies A =20
and B are invitations to disaster.
Aren't they?
=20
Heiner
=20
=20
=20
=20



Conversely, although the liveness testing must be on the basis  of=20
individual ETRs, it does seem likely that many hosts in a site will be =20
trying to reach endpoints behind the same set of ETRs.  As such,  having=20
a border guy (or someone else, if you really want to complicate  life)=20
testing / monitoring that liveness / reachability on behalf of the =20
various sources within the site would seem likely to
1) reduce the  probing traffic
2) increase the odds of having accurate data when packets  need to be sent.

Yours,
Joel

Brian E Carpenter wrote:
>  Scott,
>=20
>> As an endpoint, you are interested in reachability  of specific
>> endpoints.  You don't care if a whole prefix is  reachable, if the
>> particular endpoint isn't reachable within that  prefix.  So if you
>> delegate liveness monitoring to an agent,  you are asking it to monitor
>> specific locators.=20
>=20
>  The e2e principle seems to make it clear that, ultimately, liveness is
>  the endpoint's responsibility, but that is usually interpreted as a
>  statement about what the transport layer or above should do. And they
>  already do it, 100% independently of what we do in layer 3 and below.
>  I think that limiting layer 3 liveness detection to the prefix level
>  (except presumably in the case of Mobile IP) is a perfectly good
>  engineering compromise, unless we're planning to repudiate [Saltzer].
> =20
>     Brian
>=20
> [Saltzer] End-To-End  Arguments in System Design, J.H. Saltzer,
>    D.P.Reed,  D.D.Clark, ACM TOCS, Vol 2, Number 4, November 1984, pp
>     277-288.
> _______________________________________________
> rrg  mailing list
> rrg@irtf.org
>  http://www.irtf.org/mailman/listinfo/rrg
> =20
_______________________________________________
rrg mailing  list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg




-------------------------------1232444379
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3DISO-8859-1">
<META content=3D"MSHTML 6.00.6000.16788" name=3DGENERATOR></HEAD>
<BODY id=3Drole_body style=3D"FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY:=20=
Arial"=20
bottomMargin=3D7 leftMargin=3D7 topMargin=3D7 rightMargin=3D7><FONT id=3Drol=
e_document=20
face=3DArial color=3D#000000 size=3D2>
<DIV>In einer eMail vom 20.01.2009 02:58:08 Westeurop=E4ische Normalzeit sch=
reibt=20
jmh@joelhalpern.com:</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid"><=
FONT=20
  style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000 size=
=3D2>As far=20
  as I know, in terms of liveness testing of ETRs, there is no <BR>granulari=
ty=20
  finer than the ETR to test.&nbsp; So if we are using an ID / RLoc <BR>spli=
t,=20
  the liveness testing we are interested in is the reachability / <BR>effica=
cy=20
  of a given ETR.&nbsp; [There is the additional complication of the <BR>ETR=
=20
  being live, but not having reachability to the endpoint.&nbsp; That is a=20
  <BR>different problem than the liveness problem described in the draft.=20
  <BR>There are many additional problems...)</FONT></BLOCKQUOTE>
<DIV>...with strategy A&nbsp;&nbsp;&nbsp;and B. &nbsp;But back to this liven=
ess=20
issue:</DIV>
<DIV>&nbsp;</DIV>
<DIV>If I want to&nbsp;drive/route from NY/Broadway to Sausolito&nbsp;/ Main=
=20
Street my best next hop might be derived from a proxy destination node in=20
L.A.(because the US country map doesn't show the Main Street of=20
Sausolito)&nbsp;While doing so why should I care for the liveness of this=20
L.A.-router ?!</DIV>
<DIV>Getting closer some S.F. -router might turn out to be the actual proxy=20
dest. And that one might be ignored, too,&nbsp;getting still closer. Will sa=
y:=20
Problem after problem which do not apply to strategy C.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Further point: Now the Compact Routing experts may investigate stretch-=
ETR=20
:-) </DIV>
<DIV>Factor 17 was so far the biggest stretch value I have read. How big is=20
stretch-ETR ?</DIV>
<DIV>&nbsp;</DIV>
<DIV>Further point:</DIV>
<DIV>Mobile homing in combination with mobility. With this respect strategie=
s A=20
and B are invitations to disaster.</DIV>
<DIV>Aren't they?</DIV>
<DIV>&nbsp;</DIV>
<DIV>Heiner</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid"><=
FONT=20
  style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000=20
  size=3D2><BR><BR>Conversely, although the liveness testing must be on the=20=
basis=20
  of <BR>individual ETRs, it does seem likely that many hosts in a site will=
 be=20
  <BR>trying to reach endpoints behind the same set of ETRs.&nbsp; As such,=20
  having <BR>a border guy (or someone else, if you really want to complicate=
=20
  life) <BR>testing / monitoring that liveness / reachability on behalf of t=
he=20
  <BR>various sources within the site would seem likely to<BR>1) reduce the=20
  probing traffic<BR>2) increase the odds of having accurate data when packe=
ts=20
  need to be sent.<BR><BR>Yours,<BR>Joel<BR><BR>Brian E Carpenter wrote:<BR>=
&gt;=20
  Scott,<BR>&gt; <BR>&gt;&gt; As an endpoint, you are interested in reachabi=
lity=20
  of specific<BR>&gt;&gt; endpoints.&nbsp; You don't care if a whole prefix=20=
is=20
  reachable, if the<BR>&gt;&gt; particular endpoint isn't reachable within t=
hat=20
  prefix.&nbsp; So if you<BR>&gt;&gt; delegate liveness monitoring to an age=
nt,=20
  you are asking it to monitor<BR>&gt;&gt; specific locators. <BR>&gt; <BR>&=
gt;=20
  The e2e principle seems to make it clear that, ultimately, liveness is<BR>=
&gt;=20
  the endpoint's responsibility, but that is usually interpreted as a<BR>&gt=
;=20
  statement about what the transport layer or above should do. And they<BR>&=
gt;=20
  already do it, 100% independently of what we do in layer 3 and below.<BR>&=
gt;=20
  I think that limiting layer 3 liveness detection to the prefix level<BR>&g=
t;=20
  (except presumably in the case of Mobile IP) is a perfectly good<BR>&gt;=20
  engineering compromise, unless we're planning to repudiate [Saltzer].<BR>&=
gt;=20
  <BR>&gt;&nbsp; &nbsp;&nbsp; Brian<BR>&gt; <BR>&gt; [Saltzer] End-To-End=20
  Arguments in System Design, J.H. Saltzer,<BR>&gt;&nbsp; &nbsp; D.P.Reed,=20
  D.D.Clark, ACM TOCS, Vol 2, Number 4, November 1984, pp<BR>&gt;&nbsp; &nbs=
p;=20
  277-288.<BR>&gt; _______________________________________________<BR>&gt; r=
rg=20
  mailing list<BR>&gt; rrg@irtf.org<BR>&gt;=20
  http://www.irtf.org/mailman/listinfo/rrg<BR>&gt;=20
  <BR>_______________________________________________<BR>rrg mailing=20
  list<BR>rrg@irtf.org<BR>http://www.irtf.org/mailman/listinfo/rrg<BR></FONT=
></BLOCKQUOTE>
<DIV></DIV>
<DIV>&nbsp;</DIV></FONT></BODY></HTML>

-------------------------------1232444379--

--===============1761094319==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

--===============1761094319==--


From rrg-bounces@irtf.org  Tue Jan 20 02:29:05 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 61DCD28C127;
	Tue, 20 Jan 2009 02:29:05 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0516E3A6BBB
	for <rrg@core3.amsl.com>; Tue, 20 Jan 2009 02:29:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id flwFw-uljfbt for <rrg@core3.amsl.com>;
	Tue, 20 Jan 2009 02:29:03 -0800 (PST)
Received: from n2.nomadiclab.com (n2.nomadiclab.com
	[IPv6:2001:14b8:400:101::2])
	by core3.amsl.com (Postfix) with ESMTP id 0BE463A6A36
	for <rrg@irtf.org>; Tue, 20 Jan 2009 02:29:03 -0800 (PST)
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 6B2441F0078;
	Tue, 20 Jan 2009 12:28:45 +0200 (EET)
Received: from [127.0.0.1] (localhost [IPv6:::1])
	by n2.nomadiclab.com (Postfix) with ESMTP id E641B1F0061;
	Tue, 20 Jan 2009 12:28:44 +0200 (EET)
Message-Id: <F2DA6B6C-6E73-4FA4-A2DD-2966FA400211@nomadiclab.com>
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
To: RRG <rrg@irtf.org>
In-Reply-To: <49752F9C.4050006@joelhalpern.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Tue, 20 Jan 2009 12:28:44 +0200
References: <B25790E2-8D3C-4A55-848C-F461982DC3F6@nomadiclab.com>	<20090119213701.GA34129@cisco.com>
	<4975143E.9020404@gmail.com> <49752F9C.4050006@joelhalpern.com>
X-Mailer: Apple Mail (2.930.3)
X-Virus-Scanned: ClamAV using ClamSMTP
Subject: Re: [rrg] Why a host-based solution does not necessarily	 add
	signalling load
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

> Conversely, although the liveness testing must be on the basis of  
> individual ETRs, it does seem likely that many hosts in a site will  
> be trying to reach endpoints behind the same set of ETRs.  As such,  
> having a border guy (or someone else, if you really want to  
> complicate life) testing / monitoring that liveness / reachability  
> on behalf of the various sources within the site would seem likely to
> 1) reduce the probing traffic
> 2) increase the odds of having accurate data when packets need to be  
> sent.

Exactly.

To recap what I tried to say:

So far we've had two models on the table:  tunnel-router-based and  
host-based.  The tunnel-router based obviously checks reachability at  
the TR granularity, and host-based on host granularity.  This has  
received criticism that a host-based model causes more signalling/ 
reachability testing traffic than the tunnel-router-based one.

My point was a simple one: not necessarily so.  If TR-level  
granularity is acceptable, then it is doable with a hybrid host+TR- 
based solution (like the one I've been hand waving during the last  
month or so), and in that case the amount of reachability testing /  
signalling will be at the *same* level as for a TR-only solution.

Of course, in a hybrid solution the hosts can do reachability testing  
themselves.  However, if the only interface they have is behind a TR,  
then it doesn't give any extra pay off to the host.  That is, the host  
has a slight pay off if it delegates the task to the TR, since the TR  
may do more efficiently, as it has better information about the  
multiple local links, and (at least sometimes) on the behalf of  
multiple hosts at the same time.

Still, in a hybrid solution, a multi-homed the host has the option of  
doing reachability testing on some interfaces itself, and on others  
delegate the task to the TR.

--Pekka

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Tue Jan 20 07:05:26 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0B4353A6991;
	Tue, 20 Jan 2009 07:05:26 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A3C8F3A6947
	for <rrg@core3.amsl.com>; Tue, 20 Jan 2009 07:05:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.427
X-Spam-Level: 
X-Spam-Status: No, score=-6.427 tagged_above=-999 required=5 tests=[AWL=0.172, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id NMSQ8lIul0iM for <rrg@core3.amsl.com>;
	Tue, 20 Jan 2009 07:05:23 -0800 (PST)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com
	[130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id AC1713A6991
	for <rrg@irtf.org>; Tue, 20 Jan 2009 07:05:23 -0800 (PST)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6])
	by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id n0KF4uoN007258
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 20 Jan 2009 07:04:58 -0800 (PST)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	n0KF4t0q018881; Tue, 20 Jan 2009 09:04:55 -0600 (CST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	n0KF4lBX018536; Tue, 20 Jan 2009 09:04:55 -0600 (CST)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 20 Jan 2009 07:04:48 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 20 Jan 2009 07:04:47 -0800
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A10572629B@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <F2DA6B6C-6E73-4FA4-A2DD-2966FA400211@nomadiclab.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] Why a host-based solution does not necessarily	
	addsignalling load
Thread-Index: Acl66eNqBZx3nOe2TqSO81GhlLrPRwAJLaUA
References: <B25790E2-8D3C-4A55-848C-F461982DC3F6@nomadiclab.com>	<20090119213701.GA34129@cisco.com><4975143E.9020404@gmail.com>
	<49752F9C.4050006@joelhalpern.com>
	<F2DA6B6C-6E73-4FA4-A2DD-2966FA400211@nomadiclab.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Pekka Nikander" <pekka.nikander@nomadiclab.com>, "RRG" <rrg@irtf.org>
X-OriginalArrivalTime: 20 Jan 2009 15:04:48.0684 (UTC)
	FILETIME=[701446C0:01C97B10]
Subject: Re: [rrg] Why a host-based solution does not necessarily	
	addsignalling load
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Hi Pekka,

> -----Original Message-----
> From: Pekka Nikander [mailto:pekka.nikander@nomadiclab.com] 
> Sent: Tuesday, January 20, 2009 2:29 AM
> To: RRG
> Subject: Re: [rrg] Why a host-based solution does not 
> necessarily addsignalling load
> 
> > Conversely, although the liveness testing must be on the basis of  
> > individual ETRs, it does seem likely that many hosts in a 
> site will  
> > be trying to reach endpoints behind the same set of ETRs.  
> As such,  
> > having a border guy (or someone else, if you really want to  
> > complicate life) testing / monitoring that liveness / reachability  
> > on behalf of the various sources within the site would seem 
> likely to
> > 1) reduce the probing traffic
> > 2) increase the odds of having accurate data when packets 
> need to be  
> > sent.
> 
> Exactly.
> 
> To recap what I tried to say:
> 
> So far we've had two models on the table:  tunnel-router-based and  
> host-based.  The tunnel-router based obviously checks 
> reachability at  
> the TR granularity, and host-based on host granularity.  This has  
> received criticism that a host-based model causes more signalling/ 
> reachability testing traffic than the tunnel-router-based one.
> 
> My point was a simple one: not necessarily so.  If TR-level  
> granularity is acceptable, then it is doable with a hybrid host+TR- 
> based solution (like the one I've been hand waving during the last  
> month or so), and in that case the amount of reachability testing /  
> signalling will be at the *same* level as for a TR-only solution.
> 
> Of course, in a hybrid solution the hosts can do reachability 
> testing  
> themselves.  However, if the only interface they have is 
> behind a TR,  
> then it doesn't give any extra pay off to the host.  That is, 
> the host  
> has a slight pay off if it delegates the task to the TR, 
> since the TR  
> may do more efficiently, as it has better information about the  
> multiple local links, and (at least sometimes) on the behalf of  
> multiple hosts at the same time.
> 
> Still, in a hybrid solution, a multi-homed the host has the 
> option of  
> doing reachability testing on some interfaces itself, and on others  
> delegate the task to the TR.

I'm not sure why you're still thinking of a hybrid HIP/xTR
as the preferred mode of operation. IMHO, in many cases the
HIP end system should have direct access to the underlying
physical links (ethernet, 802.11, etc. etc.) and not the
tunnel interfaces of a co-resident xTR. This to allow
choosing the correct physical link for the desired mode
of operation and possibly based on link metrics. It also
saves encapsulation overhead over underprivileged links.

The other thing is that the HIP end system may need to
do active testing of the path, where with RANGER the
xTR gets to do both active and passive testing of the
path (i.e., it listens for ICMP unreachables). So, I
think the two reachability tests are complementary and
not conflicting/interfering. So my answers are:

HIP? yes
xTR? yes
HIP/xTR hybrid? no

Fred
fred.l.templin@boeing.com
 
> 
> --Pekka
> 
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> http://www.irtf.org/mailman/listinfo/rrg
> 
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Tue Jan 20 08:05:57 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 86A7F3A6C0D;
	Tue, 20 Jan 2009 08:05:57 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CB4633A6B23
	for <rrg@core3.amsl.com>; Tue, 20 Jan 2009 08:05:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6lY2oeTrZSPO for <rrg@core3.amsl.com>;
	Tue, 20 Jan 2009 08:05:56 -0800 (PST)
Received: from hibernia.jakma.org (cl-9.dub-01.ie.sixxs.net
	[IPv6:2001:770:100:8::2])
	by core3.amsl.com (Postfix) with ESMTP id B35FF3A6880
	for <rrg@irtf.org>; Tue, 20 Jan 2009 08:05:55 -0800 (PST)
Received: from melandri.gla.jakma.org
	(IDENT:U2FsdGVkX1/LhuCOYCBJQ44Gwj3u5G7+SGx+Nz9Nz30@melandri.jakma.org
	[81.168.24.37]) (authenticated bits=0)
	by hibernia.jakma.org (8.14.3/8.14.2) with ESMTP id n0KG5VI4010292
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 20 Jan 2009 16:05:37 GMT
Date: Tue, 20 Jan 2009 16:05:31 +0000 (GMT)
From: Paul Jakma <paul@jakma.org>
X-X-Sender: paul@localhost.localdomain
To: Pekka Nikander <pekka.nikander@nomadiclab.com>
In-Reply-To: <F2DA6B6C-6E73-4FA4-A2DD-2966FA400211@nomadiclab.com>
Message-ID: <alpine.LFD.2.00.0901201604530.31066@localhost.localdomain>
References: <B25790E2-8D3C-4A55-848C-F461982DC3F6@nomadiclab.com>
	<20090119213701.GA34129@cisco.com> <4975143E.9020404@gmail.com>
	<49752F9C.4050006@joelhalpern.com>
	<F2DA6B6C-6E73-4FA4-A2DD-2966FA400211@nomadiclab.com>
User-Agent: Alpine 2.00 (LFD 1167 2008-08-23)
Mail-Copies-To: paul@jakma.org
Mail-Followup-To: paul@jakma.org
X-NSA: al aqsar fluffy jihad cute musharef kittens jet-A1 ear avgas wax
	ammonium bad qran dog inshallah allah al-akbar martyr iraq
	hammas hisballah rabin ayatollah korea revolt pelvix mustard
	gas x-ray british airways washington peroxide cool
MIME-Version: 1.0
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.1.1
	(hibernia.jakma.org [212.17.55.49]);
	Tue, 20 Jan 2009 16:05:37 +0000 (GMT)
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] Why a host-based solution does not necessarily add
 signalling load
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On Tue, 20 Jan 2009, Pekka Nikander wrote:

> This has received criticism that a host-based model causes more 
> signalling/reachability testing traffic than the 
> tunnel-router-based one.

What's the basis for thinking this, and are there any good 
studies/data to back it up? Intuitively, it doesn't seem like it 
should be so, to any significant degree at least.

regards,
-- 
Paul Jakma	paul@clubi.ie	paul@jakma.org	Key ID: 64A2FF6A
Fortune:
Tact is the art of making a point without making an enemy.
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Tue Jan 20 09:39:47 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6C62A3A69F3;
	Tue, 20 Jan 2009 09:39:47 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 109D93A69F3
	for <rrg@core3.amsl.com>; Tue, 20 Jan 2009 09:39:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id tOr9KuNonV4P for <rrg@core3.amsl.com>;
	Tue, 20 Jan 2009 09:39:45 -0800 (PST)
Received: from virtualized.org (trantor.virtualized.org [204.152.189.190])
	by core3.amsl.com (Postfix) with ESMTP id 1B8673A6883
	for <rrg@irtf.org>; Tue, 20 Jan 2009 09:39:45 -0800 (PST)
Received: from [10.0.1.13] (cpe-70-95-123-210.hawaii.res.rr.com
	[70.95.123.210])
	by virtualized.org (Postfix) with ESMTP id E195C431830;
	Tue, 20 Jan 2009 09:38:51 -0800 (PST)
Message-Id: <C29F67D7-AD89-43CD-9A3E-76672D216667@virtualized.org>
From: David Conrad <drc@virtualized.org>
To: Paul Jakma <paul@jakma.org>
In-Reply-To: <alpine.LFD.2.00.0901201604530.31066@localhost.localdomain>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Tue, 20 Jan 2009 09:38:50 -0800
References: <B25790E2-8D3C-4A55-848C-F461982DC3F6@nomadiclab.com>
	<20090119213701.GA34129@cisco.com> <4975143E.9020404@gmail.com>
	<49752F9C.4050006@joelhalpern.com>
	<F2DA6B6C-6E73-4FA4-A2DD-2966FA400211@nomadiclab.com>
	<alpine.LFD.2.00.0901201604530.31066@localhost.localdomain>
X-Mailer: Apple Mail (2.930.3)
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] Why a host-based solution does not necessarily add
	signalling load
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On Jan 20, 2009, at 8:05 AM, Paul Jakma wrote:
>> This has received criticism that a host-based model causes more  
>> signalling/reachability testing traffic than the tunnel-router- 
>> based one.
>
> What's the basis for thinking this, and are there any good studies/ 
> data to back it up? Intuitively, it doesn't seem like it should be  
> so, to any significant degree at least.

Well, for one thing, a tunnel-router-based solution would typically  
cover some number of hosts.

Regards,
-drc

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Tue Jan 20 09:56:53 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5BAC928C0CE;
	Tue, 20 Jan 2009 09:56:53 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A3F733A69D3
	for <rrg@core3.amsl.com>; Tue, 20 Jan 2009 09:56:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Wq3Tnj2zvz8O for <rrg@core3.amsl.com>;
	Tue, 20 Jan 2009 09:56:50 -0800 (PST)
Received: from hibernia.jakma.org (cl-9.dub-01.ie.sixxs.net
	[IPv6:2001:770:100:8::2])
	by core3.amsl.com (Postfix) with ESMTP id C7EFF3A6864
	for <rrg@irtf.org>; Tue, 20 Jan 2009 09:56:49 -0800 (PST)
Received: from melandri.gla.jakma.org
	(IDENT:U2FsdGVkX1+aeud5QFzKCYsA6dTPvzcDj0X8Cp70tfE@melandri.jakma.org
	[81.168.24.37]) (authenticated bits=0)
	by hibernia.jakma.org (8.14.3/8.14.2) with ESMTP id n0KHuOuD011677
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 20 Jan 2009 17:56:31 GMT
Date: Tue, 20 Jan 2009 17:56:24 +0000 (GMT)
From: Paul Jakma <paul@jakma.org>
X-X-Sender: paul@localhost.localdomain
To: David Conrad <drc@virtualized.org>
In-Reply-To: <C29F67D7-AD89-43CD-9A3E-76672D216667@virtualized.org>
Message-ID: <alpine.LFD.2.00.0901201754180.31066@localhost.localdomain>
References: <B25790E2-8D3C-4A55-848C-F461982DC3F6@nomadiclab.com>
	<20090119213701.GA34129@cisco.com> <4975143E.9020404@gmail.com>
	<49752F9C.4050006@joelhalpern.com>
	<F2DA6B6C-6E73-4FA4-A2DD-2966FA400211@nomadiclab.com>
	<alpine.LFD.2.00.0901201604530.31066@localhost.localdomain>
	<C29F67D7-AD89-43CD-9A3E-76672D216667@virtualized.org>
User-Agent: Alpine 2.00 (LFD 1167 2008-08-23)
Mail-Copies-To: paul@jakma.org
Mail-Followup-To: paul@jakma.org
X-NSA: al aqsar fluffy jihad cute musharef kittens jet-A1 ear avgas wax
	ammonium bad qran dog inshallah allah al-akbar martyr iraq
	hammas hisballah rabin ayatollah korea revolt pelvix mustard
	gas x-ray british airways washington peroxide cool
MIME-Version: 1.0
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.1.1
	(hibernia.jakma.org [212.17.55.49]);
	Tue, 20 Jan 2009 17:56:31 +0000 (GMT)
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] Why a host-based solution does not necessarily add
 signalling load
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On Tue, 20 Jan 2009, David Conrad wrote:

> On Jan 20, 2009, at 8:05 AM, Paul Jakma wrote:
>>> This has received criticism that a host-based model causes more 
>>> signalling/reachability testing traffic than the tunnel-router-based one.
>> 
>> What's the basis for thinking this, and are there any good studies/data to 
>> back it up? Intuitively, it doesn't seem like it should be so, to any 
>> significant degree at least.
>
> Well, for one thing, a tunnel-router-based solution would typically cover 
> some number of hosts.

Ok, sure.

I assumed there was an implied ", to a significant enough extent for 
it to matter" at the end of the sentence I quoted. It seems 
reasonable to assume that, for without it the criticism can be 
dismissed straight away.

regards,
-- 
Paul Jakma	paul@clubi.ie	paul@jakma.org	Key ID: 64A2FF6A
Fortune:
That must be wonderful: I don't understand it at all.
 		-- Moliere
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg


From rrg-bounces@irtf.org  Tue Jan 20 10:24:41 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 12D103A6C09;
	Tue, 20 Jan 2009 10:24:41 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 007993A6C09
	for <rrg@core3.amsl.com>; Tue, 20 Jan 2009 10:24:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.522
X-Spam-Level: 
X-Spam-Status: No, score=-6.522 tagged_above=-999 required=5 tests=[AWL=0.077, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6J30XuKnfO-A for <rrg@core3.amsl.com>;
	Tue, 20 Jan 2009 10:24:39 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id C09463A6895
	for <rrg@irtf.org>; Tue, 20 Jan 2009 10:24:38 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,295,1231113600"; d="scan'208";a="34335218"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 20 Jan 2009 18:24:22 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n0KIOMLt022385; 
	Tue, 20 Jan 2009 13:24:22 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n0KIOLDE001283;
	Tue, 20 Jan 2009 18:24:21 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 20 Jan 2009 13:24:21 -0500
Received: from sbrim-mbp.local ([64.102.8.172]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 20 Jan 2009 13:24:21 -0500
Message-ID: <497616D4.8090500@employees.org>
Date: Tue, 20 Jan 2009 13:24:20 -0500
From: Scott Brim <swb@employees.org>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>,
	"Joel M. Halpern" <jmh@joelhalpern.com>,
	Pekka Nikander <pekka.nikander@nomadiclab.com>
References: <4975143E.9020404@gmail.com> <49752F9C.4050006@joelhalpern.com>
	<F2DA6B6C-6E73-4FA4-A2DD-2966FA400211@nomadiclab.com>
	<B25790E2-8D3C-4A55-848C-F461982DC3F6@nomadiclab.com>
	<20090119213701.GA34129@cisco.com> <4975143E.9020404@gmail.com>
	<49752F9C.4050006@joelhalpern.com>
	<B25790E2-8D3C-4A55-848C-F461982DC3F6@nomadiclab.com>
	<20090119213701.GA34129@cisco.com> <4975143E.9020404@gmail.com>
In-Reply-To: <4975143E.9020404@gmail.com>
X-OriginalArrivalTime: 20 Jan 2009 18:24:21.0529 (UTC)
	FILETIME=[50737090:01C97B2C]
Authentication-Results: rtp-dkim-1; header.From=swb@employees.org; dkim=neutral
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] Why a host-based solution does not necessarily
 add	signalling load
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>,
	<mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Excerpts from Brian E Carpenter on Tue, Jan 20, 2009 01:01:02PM +1300:
> The e2e principle seems to make it clear that, ultimately, liveness
> is the endpoint's responsibility, but that is usually interpreted as
> a statement about what the transport layer or above should do. And
> they already do it, 100% independently of what we do in layer 3 and
> below.  I think that limiting layer 3 liveness detection to the
> prefix level (except presumably in the case of Mobile IP) is a
> perfectly good engineering compromise, unless we're planning to
> repudiate [Saltzer].

First let's step back and reiterate that we're talking about how to
scale e2e liveness monitoring and failure recovery.  xTRs and
map-and-encap are not (necessarily) involved, although _monitoring_
intermediaries may be.

Disregarding layers and what their responsibilities might be, if I
understand correctly you're saying you would do prefix-level liveness
monitoring for possible paths but only do specific address-level
monitoring for address pairs that are currently in use?  If so, are you
saying that if that's the best you can get, you'll take it?  Or do you
really think that's good enough for end users?


Excerpts from Joel M. Halpern on Mon, Jan 19, 2009 08:57:48PM -0500:
> There are prefixes on RLocs.  Such prefixes appear in routing.  Clearly,  
> the presence of such a prefix in routing does not tell you enough to  
> judge the reachability or liveness of an individual xTR within that  
> prefix.  (The absence of a prefix, that's useful.  But that's the easy  
> part of the problem.)

xTRs are only involved in a map-and-encap situation.  We _may_ have a
map-and-encap situation here but it's not required.

> As far as I know, in terms of liveness testing of ETRs, there is no  
> granularity finer than the ETR to test.  So if we are using an ID / RLoc  
> split, the liveness testing we are interested in is the reachability /  
> efficacy of a given ETR.  [There is the additional complication of the  
> ETR being live, but not having reachability to the endpoint.  That is a  
> different problem than the liveness problem described in the draft.  
> There are many additional problems...)

Right ... the requirements on xTRs for liveness is completely different
from those for end-to-end.  xTRs take responsibility for getting traffic
between _prefixes_, as opposed to endpoints.


Excerpts from Pekka Nikander on Tue, Jan 20, 2009 12:28:44PM +0200:
>> Conversely, although the liveness testing must be on the basis of  
>> individual ETRs, it does seem likely that many hosts in a site will be 
>> trying to reach endpoints behind the same set of ETRs.  As such,  
>> having a border guy (or someone else, if you really want to complicate 
>> life) testing / monitoring that liveness / reachability on behalf of 
>> the various sources within the site would seem likely to
>> 1) reduce the probing traffic
>> 2) increase the odds of having accurate data when packets need to be  
>> sent.
>
> Exactly.
>
> To recap what I tried to say:
>
> So far we've had two models on the table:  tunnel-router-based and  
> host-based.  The tunnel-router based obviously checks reachability at  
> the TR granularity, and host-based on host granularity.  This has  
> received criticism that a host-based model causes more signalling/ 
> reachability testing traffic than the tunnel-router-based one.
>
> My point was a simple one: not necessarily so.  If TR-level granularity 
> is acceptable, 

That's the big question.  I'm surprised people would find it acceptable.
Think about how individual machines are multihomed between different
providers today.  If one of your interfaces goes down, the prefix you
are part of in that provider is still available, so your peers would
continue to try to talk to you there.  I don't see how prefix liveness
tests could take the place of e2e liveness tests.  If I understand Brian
correctly he thinks higher layer tests will take care of this problem,
but we still need a way for those higher layer tests to be performed on
src/dst pairs other than the ones in use by transport already.

Happy Obama Day ... Scott


_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg



From rrg-bounces@irtf.org  Tue Jan 20 13:16:34 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8CC183A690A; Tue, 20 Jan 2009 13:16:34 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 31F133A690A for <rrg@core3.amsl.com>; Tue, 20 Jan 2009 13:16:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.509
X-Spam-Level: 
X-Spam-Status: No, score=-2.509 tagged_above=-999 required=5 tests=[AWL=0.090,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tCMj7acL-79i for <rrg@core3.amsl.com>; Tue, 20 Jan 2009 13:16:32 -0800 (PST)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.229]) by core3.amsl.com (Postfix) with ESMTP id 278633A67C1 for <rrg@irtf.org>; Tue, 20 Jan 2009 13:16:32 -0800 (PST)
Received: by rv-out-0506.google.com with SMTP id f6so3884458rvb.7 for <rrg@irtf.org>; Tue, 20 Jan 2009 13:16:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=ETcTWsxFj8JOKAzML5pnCZGJRy7JK3B8PTFrdE5KAOM=; b=YkfYlLNfoYNDKPla3hDwlEZn1QVLXpNUSMVL0xIvpr8z+X6MxzOo9GXeQzIrcAR11m gW6KTx6h0PmNzsxy/wr/e1Th5wLr1P427zKZaWTFiN4PJpBcKsCjBP0EgBxMRfUyjmsN Fl5UyvbFqTMLiXwb1njLowoAOBsxsQto0Ynfc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=WIrr3+xNFaLgNfwvrasktpPKAFTcltYkg5n6m3xTaIRw1rJmLKaxnr+3Z7A8SNepID GKhor/WbnBR8h3Rka+8dz9znIKDdBNsrXrQn02u8qaKhj9SQ8xbOoo3vkzL9uG4K5v3C KzVxFLZ24kPzP7A4x9cJwxm9hi+PTPepYSquA=
Received: by 10.141.96.10 with SMTP id y10mr754096rvl.249.1232486175465; Tue, 20 Jan 2009 13:16:15 -0800 (PST)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id g31sm13556992rvb.4.2009.01.20.13.16.13 (version=SSLv3 cipher=RC4-MD5); Tue, 20 Jan 2009 13:16:14 -0800 (PST)
Message-ID: <49763F1C.30601@gmail.com>
Date: Wed, 21 Jan 2009 10:16:12 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Scott Brim <swb@employees.org>
References: <4975143E.9020404@gmail.com> <49752F9C.4050006@joelhalpern.com> <F2DA6B6C-6E73-4FA4-A2DD-2966FA400211@nomadiclab.com> <B25790E2-8D3C-4A55-848C-F461982DC3F6@nomadiclab.com> <20090119213701.GA34129@cisco.com> <4975143E.9020404@gmail.com> <49752F9C.4050006@joelhalpern.com> <B25790E2-8D3C-4A55-848C-F461982DC3F6@nomadiclab.com> <20090119213701.GA34129@cisco.com> <4975143E.9020404@gmail.com> <497616D4.8090500@employees.org>
In-Reply-To: <497616D4.8090500@employees.org>
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] Why a host-based solution does not necessarily add	signalling load
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org Scott,

On 2009-01-21 07:24, Scott Brim wrote:
> Excerpts from Brian E Carpenter on Tue, Jan 20, 2009 01:01:02PM +1300:
>> The e2e principle seems to make it clear that, ultimately, liveness
>> is the endpoint's responsibility, but that is usually interpreted as
>> a statement about what the transport layer or above should do. And
>> they already do it, 100% independently of what we do in layer 3 and
>> below.  I think that limiting layer 3 liveness detection to the
>> prefix level (except presumably in the case of Mobile IP) is a
>> perfectly good engineering compromise, unless we're planning to
>> repudiate [Saltzer].
> 
> First let's step back and reiterate that we're talking about how to
> scale e2e liveness monitoring and failure recovery.  xTRs and
> map-and-encap are not (necessarily) involved, although _monitoring_
> intermediaries may be.
> 
> Disregarding layers and what their responsibilities might be, if I
> understand correctly you're saying you would do prefix-level liveness
> monitoring for possible paths but only do specific address-level
> monitoring for address pairs that are currently in use?  If so, are you
> saying that if that's the best you can get, you'll take it?  Or do you
> really think that's good enough for end users?
> 

I think I'm saying that's good enough for transport and session layers
that apply the e2e principle, and that the nature of RFC791 is such
that they all apply that principle today. It is not the network layer's
job to be perfect.

One thing that may be useful is an API that allows the upper layer to
tell the local IP stack "Hey, I'm seeing a liveness problem, please
check it out." That would make constant liveness checks by the network
layer unnecessary.

    Brian

> Excerpts from Joel M. Halpern on Mon, Jan 19, 2009 08:57:48PM -0500:
>> There are prefixes on RLocs.  Such prefixes appear in routing.  Clearly,  
>> the presence of such a prefix in routing does not tell you enough to  
>> judge the reachability or liveness of an individual xTR within that  
>> prefix.  (The absence of a prefix, that's useful.  But that's the easy  
>> part of the problem.)
> 
> xTRs are only involved in a map-and-encap situation.  We _may_ have a
> map-and-encap situation here but it's not required.
> 
>> As far as I know, in terms of liveness testing of ETRs, there is no  
>> granularity finer than the ETR to test.  So if we are using an ID / RLoc  
>> split, the liveness testing we are interested in is the reachability /  
>> efficacy of a given ETR.  [There is the additional complication of the  
>> ETR being live, but not having reachability to the endpoint.  That is a  
>> different problem than the liveness problem described in the draft.  
>> There are many additional problems...)
> 
> Right ... the requirements on xTRs for liveness is completely different
> from those for end-to-end.  xTRs take responsibility for getting traffic
> between _prefixes_, as opposed to endpoints.
> 
> 
> Excerpts from Pekka Nikander on Tue, Jan 20, 2009 12:28:44PM +0200:
>>> Conversely, although the liveness testing must be on the basis of  
>>> individual ETRs, it does seem likely that many hosts in a site will be 
>>> trying to reach endpoints behind the same set of ETRs.  As such,  
>>> having a border guy (or someone else, if you really want to complicate 
>>> life) testing / monitoring that liveness / reachability on behalf of 
>>> the various sources within the site would seem likely to
>>> 1) reduce the probing traffic
>>> 2) increase the odds of having accurate data when packets need to be  
>>> sent.
>> Exactly.
>>
>> To recap what I tried to say:
>>
>> So far we've had two models on the table:  tunnel-router-based and  
>> host-based.  The tunnel-router based obviously checks reachability at  
>> the TR granularity, and host-based on host granularity.  This has  
>> received criticism that a host-based model causes more signalling/ 
>> reachability testing traffic than the tunnel-router-based one.
>>
>> My point was a simple one: not necessarily so.  If TR-level granularity 
>> is acceptable, 
> 
> That's the big question.  I'm surprised people would find it acceptable.
> Think about how individual machines are multihomed between different
> providers today.  If one of your interfaces goes down, the prefix you
> are part of in that provider is still available, so your peers would
> continue to try to talk to you there.  I don't see how prefix liveness
> tests could take the place of e2e liveness tests.  If I understand Brian
> correctly he thinks higher layer tests will take care of this problem,
> but we still need a way for those higher layer tests to be performed on
> src/dst pairs other than the ones in use by transport already.
> 
> Happy Obama Day ... Scott
> 
> 
> 
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Tue Jan 20 13:35:51 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AF5DD3A690A; Tue, 20 Jan 2009 13:35:51 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0743A3A690A for <rrg@core3.amsl.com>; Tue, 20 Jan 2009 13:35:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.171
X-Spam-Level: 
X-Spam-Status: No, score=-2.171 tagged_above=-999 required=5 tests=[AWL=-0.172, BAYES_00=-2.599, J_CHICKENPOX_43=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NkcEMerjuYF1 for <rrg@core3.amsl.com>; Tue, 20 Jan 2009 13:35:50 -0800 (PST)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9]) by core3.amsl.com (Postfix) with ESMTP id 124BB3A67C1 for <rrg@irtf.org>; Tue, 20 Jan 2009 13:35:50 -0800 (PST)
Received: from m106.maoz.com (localhost [127.0.0.1]) by m106.maoz.com (8.14.3/8.14.3/Debian-4) with ESMTP id n0KLZUsf012184;  Tue, 20 Jan 2009 13:35:30 -0800
Received: (from dmm@localhost) by m106.maoz.com (8.14.3/8.14.3/Submit) id n0KLZUpO012183; Tue, 20 Jan 2009 13:35:30 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Tue, 20 Jan 2009 13:35:30 -0800
From: David Meyer <dmm@1-4-5.net>
To: rrg@irtf.org
Message-ID: <20090120213530.GA12120@1-4-5.net>
References: <20090120190744.GA9467@1-4-5.net>
MIME-Version: 1.0
In-Reply-To: <20090120190744.GA9467@1-4-5.net>
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-gpg-fingerprint: 2409 8B50 B389 A307 BA5C 2A16 3918 03D6 A099 D8A7
X-philosophy: "I just had to let it go. John Lennon"
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: [rrg] FYI [Re: Please respond: Questions from the IESG as to whether a	WG forming BOF is necessary for LISP]
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1559398236=="
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org --===============1559398236==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="C7zPtVaVf+AK4Oqc"
Content-Disposition: inline


--C7zPtVaVf+AK4Oqc
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

	I was given a list of IETF lists to post this to. The RRG
	list was added later. Please excuse any excessive
	cross-posting.=20

	Dave

On Tue, Jan 20, 2009 at 11:07:44AM -0800, David Meyer wrote:
>=20
> 	Folks,
>=20
> 	The IESG would like to know whether people believe that
> 	we can go directly to our first LISP WG meeting at the
> 	next IETF, or if another WG forming BOF is necessary.
>=20
> 	Here are the current facts on the ground:
>=20
> 	o We have fairly mature set of core drafts
> 	o There are a number of other (non-core) LISP drafts
> 	o Significant global deployment is underway
> 	o We have 2 (or more) implementations
> 	o We have been discussing a draft charter (see update below)
>=20
> 	The question is that I would like folks to respond to is
> 	 "Should a WG be formed based on the draft agenda
> 	 (see below), or should we have another BOF?"
>=20
> 	Please give your opinion as soon as possible so we can
> 	close on these administrative issues.=20
>=20
> 	Thanks,
>=20
> 	Dave
> --
>=20
> LISP (Locator/ID Separation Protocol)
>=20
> Last Modified: 2009-01-20
>=20
> Chair(s):
>  TBD
>=20
> Internet Area Director(s):
>  TBD
>=20
> Routing Area Advisor:
>  TBD
>=20
> Secretary(ies):
>  TBD
> =20
> Mailing Lists:
>  General Discussion: lisp@ietf.org
>=20
> Description of Working Group:
>=20
> LISP and companion documents (see below) are proposals that
> respond to the problems discussed at the IAB's October, 2006
> Routing and Addressing Workshop [0]. The purpose of the BOF is to
> form a working group whose charter (see below) is to work on the
> design on the LISP base protocol [1], the LISP+ALT mapping system
> [2], LISP Interworking [4] and LISP multicast [6]. The working
> group will encourage and support interoperable LISP
> implementations as well as defining requirements for alternate
> mapping systems. The Working Group may also create EID-prefix
> assignment guidelines for RIRs, as well as security profiles for
> the ALT (presumably using technology developed in the SIDR
> working group).
>=20
> Goals and Milestones:
>=20
> Mar 2010  Submit base LISP specification to the IESG for
>           Experimental.
>=20
> Mar 2010  Submit base ALT specification to the IESG for
>           Experimental.
>=20
> Mar 2010  Submit the LISP Interworking specification to the IESG
> 	  for Experimental.
>=20
> June 2010 Submit Recommendations for Allocation and Routing
> 	  of both EIDs and RLOCs to the IESG for Experimental.
>=20
> June 2010 Submit Recommendations for Securing the LISP Mapping
> 	  System to the IESG for Experimental.
>=20
> July 2010 Submit LISP for Multicast Environments to the IESG for
> 	  Experimental.=20
>=20
> Aug  2010  Re-charter or close.
>=20
> Internet-Drafts:
> 	draft-farinacci-lisp-11.txt
> 	draft-farinacci-lisp-multicast-01.txt
> 	draft-fuller-lisp-alt-03.txt
> 	draft-lewis-lisp-interworking-02.txt
>=20
> Request For Comments:
> 	  None
>=20
>=20
> References
> ----------
> [0]     Meyer, D. et. al., "Report from the IAB Workshop on
>         Routing and Addressing", RFC 4984.
>=20
> [1]     Farinacci, D. et. al., "Locator/ID Separation Protocol
>         (LISP)", draft-farinacci-lisp-11.txt.
>=20
> [2]	Fuller, V., et. al., "LISP Alternative Topology
> 	(LISP-ALT)", draft-fuller-lisp-alt-03.txt
>=20
> [3]	Iannone, L., and O. Bonaventure, "OpenLISP Implementation
> 	Report", draft-iannone-openlisp-implementation-00.txt.
>=20
> [4]	Lewis, D., et. al., "Interworking LISP with IPv4 and
> 	IPv6", draft-lewis-lisp-interworking-02.txt.
>=20
> [5]	Mathy, L., et. al., "LISP-DHT: Towards a DHT to map
> 	identifiers onto locators", draft-mathy-lisp-dht-00.txt.
>=20
> [6]     Farinacci, D., Meyer, D., Zwiebel, J., and S. Venaas,
> 	"LISP for Multicast Environments",
> 	draft-farinacci-lisp-multicast-01.txt. =20
>=20



> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www.ietf.org/mailman/listinfo/routing-discussion


--C7zPtVaVf+AK4Oqc
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkl2Q6IACgkQORgD1qCZ2KesWwCeNqRWk2bBcX6Iga4c+JEbJg6e
4gsAn36r4vbn6yaHeoPJetxE6YHC2gtR
=vbGu
-----END PGP SIGNATURE-----

--C7zPtVaVf+AK4Oqc--

--===============1559398236==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

--===============1559398236==--

From rrg-bounces@irtf.org  Wed Jan 21 08:10:54 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A153D28C15F; Wed, 21 Jan 2009 08:10:54 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 859F428C15F; Wed, 21 Jan 2009 08:10:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.066
X-Spam-Level: 
X-Spam-Status: No, score=-2.066 tagged_above=-999 required=5 tests=[AWL=-0.266, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wPjroMonsv1d; Wed, 21 Jan 2009 08:10:51 -0800 (PST)
Received: from mx3.bbn.com (mx3.bbn.com [128.33.1.81]) by core3.amsl.com (Postfix) with ESMTP id 41C583A6990; Wed, 21 Jan 2009 08:10:48 -0800 (PST)
Received: from dhcp89-081-021.bbn.com ([128.89.81.21] helo=nth.isi.edu) by mx3.bbn.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from <falk@bbn.com>) id 1LPfew-0006Zy-CF; Wed, 21 Jan 2009 11:10:30 -0500
Message-ID: <497748F6.4090200@bbn.com>
Date: Wed, 21 Jan 2009 11:10:30 -0500
From: Aaron Falk <falk@bbn.com>
Organization: BBN Technologies
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: The IESG <iesg-secretary@ietf.org>
Cc: Internet Research Steering Group <irsg@isi.edu>, rrg@irtf.org, Lixia Zhang <lixia@CS.UCLA.EDU>
Subject: [rrg] Request for IESG review of IRTF doc draft-irtf-routing-history-09.txt
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org This is a request for the IESG to perform a RFC3932bis review of
draft-irtf-routing-history-09.txt [1] to be published an an Historical
IRTF RFC.  The document has been approved for publication by the IRSG. 
See below for details on prior reviews.  Please copy all correspondence
to the document shepherd, Lixia Zhang <lixia@CS.UCLA.EDU>.

--aaron

[1] http://www.ietf.org/internet-drafts/draft-irtf-routing-history-09.txt

---
  Aaron Falk
  Chair
  Internet Research Task Force
  (617) 500-5960
  http://www.irtf.org


Begin forwarded message:
> Aaron,
>
> this is a request to publish the following document as a historical RFC:
> http://www.ietf.org/internet-drafts/draft-irtf-routing-history-09.txt
>
> This document has gone through RRG review and IRSG review.
> Please see the issue tracker under ticket #12:
>
>   http://trac.tools.ietf.org/group/irtf/trac/ticket/12
>
> Summary of review:
> - This document was a report on RRG activities around 2001-2002.
>   It went through RRG reviews around that time.
> - The last round of RRG review was conducted in early 2007, and
>   received no comments for changes.
> - The final revision was reviewed by the IRSG members David McGrew
>   and Kevin Fall, both voted YES on the IRSG Poll for this revision.
>   No objection was received during the IRSG Poll.
>
> I have updated the status to: IRSG review concluded.
>
> Let me know if I need to do anything else.
>
> thanks,
>
> Lixia Zhang
> Document Shepherd

also

>
>
> This document reports the analysis of the state of the Internet
> domain-based routing system, concentrating on Inter-Domain Routing
> (IDR) and also considering the relationship between inter-domain and
> intra-domain routing. This analysis was carried out around year 2001
> by looking at the routing system as appeared in 2001, with editorial
> additions reflecting developments up to 2006.
>
> Since this document summarizes discussions held several years ago by
> members of the IRTF Routing Research Group (IRTF RRG) and other
> interested parties, it is published with the support of the IRTF RRG
> as a historical RFC to serve as a record of the work completed around
> 2001, and with the understanding that it does not necessarily
> represent either the latest technical understanding or the technical
> consensus of the research group at the date of publication.
>
> Lixia Zhang Document Shepherd

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Wed Jan 21 08:31:13 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 769F23A6A7C; Wed, 21 Jan 2009 08:31:13 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2EF603A6A7C; Wed, 21 Jan 2009 08:31:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.926
X-Spam-Level: 
X-Spam-Status: No, score=-1.926 tagged_above=-999 required=5 tests=[AWL=-0.353, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kUbxJABhdmK7; Wed, 21 Jan 2009 08:31:11 -0800 (PST)
Received: from mx3.bbn.com (mx3.bbn.com [128.33.1.81]) by core3.amsl.com (Postfix) with ESMTP id 592373A67D8; Wed, 21 Jan 2009 08:31:11 -0800 (PST)
Received: from dhcp89-081-021.bbn.com ([128.89.81.21] helo=nth.isi.edu) by mx3.bbn.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from <falk@bbn.com>) id 1LPfey-0006a3-Cg; Wed, 21 Jan 2009 11:10:33 -0500
Message-ID: <497748F8.1010903@bbn.com>
Date: Wed, 21 Jan 2009 11:10:32 -0500
From: Aaron Falk <falk@bbn.com>
Organization: BBN Technologies
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: The IESG <iesg-secretary@ietf.org>
Cc: Internet Research Steering Group <irsg@isi.edu>, rrg@irtf.org, Lixia Zhang <lixia@CS.UCLA.EDU>
Subject: [rrg] Request for IESG review of IRTF doc draft-irtf-routing-reqs-10.txt
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org This is a request for the IESG to perform a RFC3932bis review of
draft-irtf-routing-reqs-10.txt [1] to be published an an Historical IRTF
RFC.  The document has been approved for publication by the IRSG.  See
below for details on prior reviews.  Please copy all correspondence to
the document shepherd, Lixia Zhang <lixia@CS.UCLA.EDU>.

--aaron

[1] http://tools.ietf.org/id/draft-irtf-routing-reqs-10.txt

---
  Aaron Falk
  Chair
  Internet Research Task Force
  (617) 500-5960
  http://www.irtf.org


Begin forwarded message:
> Aaron,
>
> this is a request to publish the following document as a historical RFC:
> http://tools.ietf.org/id/draft-irtf-routing-reqs-10.txt
>
> This document has gone through RRG review and IRSG review.
> Please see the issue tracker under ticket #16:
>
>   http://trac.tools.ietf.org/group/irtf/trac/ticket/16
> (somehow I could not change the version# from 09 to 10)
>
> Summary of review:
> - This document was a report on RRG activities around 2001-2002.
>   It went through RRG reviews around that time.
> - The last round of RRG review was conducted in early 2007, and
>   received no comments for changes.
> - IRSG members Jeremy Mineweaser and Juergen Schoenwaelder
>   reviewed -08 version during IRSG Poll and provided valuable comments.
>   After the authors addressed the comments in later revisions,
>   both voted YES for the revision. No objection was received.
>
> I have updated the status to: IRSG review concluded.
>
>
> thanks,
>
> Lixia Zhang
> Document Shepherd

also

>
>
> The requirements for routing architectures described in this document
> were produced by two sub-groups under the IRTF Routing Research Group
> in 2001, with some editorial updates up to 2006.
>
> Since this document summarizes discussions held sevenl years ago by
> members of the IRTF Routing Research Group (IRTF RRG) and other
> interested parties, it is published with the support of the IRTF RRG
> as a historical RFC to serve as a record of the work completed around
> 2001, and with the understanding that it does not necessarily
> represent either the latest technical understanding or the technical
> consensus of the research group at the date of publication.
>
> Lixia Zhang
>
> Document Shepherd



_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Wed Jan 21 11:25:05 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7BF453A69ED; Wed, 21 Jan 2009 11:25:05 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5AA7D3A69EF for <rrg@core3.amsl.com>; Wed, 21 Jan 2009 11:25:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.526
X-Spam-Level: 
X-Spam-Status: No, score=-6.526 tagged_above=-999 required=5 tests=[AWL=0.073,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JmM0eYjJIm0p for <rrg@core3.amsl.com>; Wed, 21 Jan 2009 11:25:03 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 4D6813A68F6 for <rrg@irtf.org>; Wed, 21 Jan 2009 11:25:03 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,301,1231113600"; d="scan'208";a="34434678"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 21 Jan 2009 19:24:31 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n0LJOVmk011388;  Wed, 21 Jan 2009 14:24:31 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n0LJOVS0018623; Wed, 21 Jan 2009 19:24:31 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 21 Jan 2009 14:24:31 -0500
Received: from cisco.com ([10.86.250.24]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 21 Jan 2009 14:24:30 -0500
Date: Wed, 21 Jan 2009 14:24:29 -0500
From: Scott Brim <swb@employees.org>
To: Xu Xiaohu <xuxh@huawei.com>
Message-ID: <20090121192429.GC71937@cisco.com>
Mail-Followup-To: Scott Brim <swb@employees.org>, Xu Xiaohu <xuxh@huawei.com>, 'Brian E Carpenter' <brian.e.carpenter@gmail.com>, 'RRG' <rrg@irtf.org>, 'Robin Whittle' <rw@firstpr.com.au>
References: <496ABF62.60600@gmail.com> <000d01c9746d$2ad1f570$670c6f0a@china.huawei.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <000d01c9746d$2ad1f570$670c6f0a@china.huawei.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-OriginalArrivalTime: 21 Jan 2009 19:24:30.0242 (UTC) FILETIME=[E1D31820:01C97BFD]
Authentication-Results: rtp-dkim-1; header.From=swb@employees.org; dkim=neutral
Cc: 'RRG' <rrg@irtf.org>, 'Robin Whittle' <rw@firstpr.com.au>
Subject: Re: [rrg] Scope Re:  Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org Excerpts from Xu Xiaohu on Mon, Jan 12, 2009 12:20:57PM +0800:
> 
> > > What HIP gives you is an identifier that may be used for many
> > > things.  An HI can be, but does not have to be, part of the
> > > process of initially finding a locator for an endpoint. For
> > > example, I can go straight from domain name to locator (which
> > > actually might be an agent / proxy / rendezvous point), and then
> > > validate identities via some other means.
> > 
> > Assuming I deem the DNS trustworthy, it seems much more natural to
> > treat the DNS as the source of an HI, and then for the locator to
> > be looked up as a function of the HI. I'm not saying your model
> > doesn't work, but surely the HI is fundamental and has universal
> > validity, and the locator (any of the locators) is transient and
> > has non-universal scope? So starting with a locator lookup seems
> > funny.
> 
> I prefer Brain's opinion since there is no need for each host owns a
> FQDN name. Once you tell me your host ID, I can resolve your locator
> from a seperate ID/locator mapping system and then communicate with
> you. 

This is an interesting point.  Thank you.
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Wed Jan 21 12:24:01 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5309E28C123; Wed, 21 Jan 2009 12:24:01 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5BB5828C123 for <rrg@core3.amsl.com>; Wed, 21 Jan 2009 12:24:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.511
X-Spam-Level: 
X-Spam-Status: No, score=-2.511 tagged_above=-999 required=5 tests=[AWL=0.088,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v5+x-SvnC940 for <rrg@core3.amsl.com>; Wed, 21 Jan 2009 12:23:59 -0800 (PST)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.233]) by core3.amsl.com (Postfix) with ESMTP id 95E7D28C105 for <rrg@irtf.org>; Wed, 21 Jan 2009 12:23:59 -0800 (PST)
Received: by rv-out-0506.google.com with SMTP id f6so4457248rvb.7 for <rrg@irtf.org>; Wed, 21 Jan 2009 12:23:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=SGfmCd9vff52Psfc4Hb2QsAygwWzgBeHcV6NgeqSOHc=; b=NodU2YKoWftfzkZmAj78wVEtegesNIe2nEG9yLFnwYVNDdqM32ir9nnrDkA0vcPE6X DNXgOJs8C5Q1uNoeFbc4ADluz3cYu7vSSXhnxn37Ot4uP5XTqrwanl7/u048yyu8YMxq EIIfLe2J2m38QQERoAdhDPrid9T+lvNufh+tE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=I8IAjfMK+YaZqSVBrzC4sqEfvg4CEXLO2Job2Xoz/Nc4RHPZAmkqA2moFIS/OGMLqv tABWXKqlfeAOMH3SaxClTtmQ4hGUWVgYMTu8KgfhcgcVimSXevu/HHe6P2L+uDR3kNDr BEyTWQysfhQVt2T6TUwfORZ2E2dBtjWvI5j/4=
Received: by 10.140.132.4 with SMTP id f4mr4131967rvd.211.1232569422525; Wed, 21 Jan 2009 12:23:42 -0800 (PST)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id f21sm16351279rvb.7.2009.01.21.12.23.40 (version=SSLv3 cipher=RC4-MD5); Wed, 21 Jan 2009 12:23:41 -0800 (PST)
Message-ID: <4977844B.6020702@gmail.com>
Date: Thu, 22 Jan 2009 09:23:39 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Scott Brim <swb@employees.org>, 'Robin Whittle' <rw@firstpr.com.au>
References: <496ABF62.60600@gmail.com> <000d01c9746d$2ad1f570$670c6f0a@china.huawei.com> <20090121192429.GC71937@cisco.com>
In-Reply-To: <20090121192429.GC71937@cisco.com>
Cc: 'RRG' <rrg@irtf.org>
Subject: Re: [rrg] Scope Re:  Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org On 2009-01-22 08:24, Scott Brim wrote:
> Excerpts from Xu Xiaohu on Mon, Jan 12, 2009 12:20:57PM +0800:
>>>> What HIP gives you is an identifier that may be used for many
>>>> things.  An HI can be, but does not have to be, part of the
>>>> process of initially finding a locator for an endpoint. For
>>>> example, I can go straight from domain name to locator (which
>>>> actually might be an agent / proxy / rendezvous point), and then
>>>> validate identities via some other means.
>>> Assuming I deem the DNS trustworthy, it seems much more natural to
>>> treat the DNS as the source of an HI, and then for the locator to
>>> be looked up as a function of the HI. I'm not saying your model
>>> doesn't work, but surely the HI is fundamental and has universal
>>> validity, and the locator (any of the locators) is transient and
>>> has non-universal scope? So starting with a locator lookup seems
>>> funny.
>> I prefer Brain's opinion since there is no need for each host owns a
>> FQDN name. Once you tell me your host ID, I can resolve your locator
>> from a seperate ID/locator mapping system and then communicate with
>> you. 
> 
> This is an interesting point.  Thank you.
> 

It occurs to me that this would be particularly relevant to massive
server virtualization (where a pool of physical servers synthesizes
virtual servers as workload arrives). The virtual servers would each
need an HI to locator map entry but would not particularly need an FQDN.

   Brian
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Wed Jan 21 19:19:42 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 80ED328C222; Wed, 21 Jan 2009 19:19:42 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4FCC128C222 for <rrg@core3.amsl.com>; Wed, 21 Jan 2009 19:19:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.579
X-Spam-Level: 
X-Spam-Status: No, score=-1.579 tagged_above=-999 required=5 tests=[AWL=0.316,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NoZBA8oTqC6w for <rrg@core3.amsl.com>; Wed, 21 Jan 2009 19:19:39 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123]) by core3.amsl.com (Postfix) with ESMTP id BEB8228C21E for <rrg@irtf.org>; Wed, 21 Jan 2009 19:19:38 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6]) by gair.firstpr.com.au (Postfix) with ESMTP id 959A8175DB1; Thu, 22 Jan 2009 14:19:21 +1100 (EST)
Message-ID: <4977E638.4060501@firstpr.com.au>
Date: Thu, 22 Jan 2009 14:21:28 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: RRG <rrg@irtf.org>
References: <B25790E2-8D3C-4A55-848C-F461982DC3F6@nomadiclab.com>	<20090119213701.GA34129@cisco.com>	<4975143E.9020404@gmail.com> <49752F9C.4050006@joelhalpern.com> <F2DA6B6C-6E73-4FA4-A2DD-2966FA400211@nomadiclab.com>
In-Reply-To: <F2DA6B6C-6E73-4FA4-A2DD-2966FA400211@nomadiclab.com>
Subject: Re: [rrg] Why a host-based solution does not necessarily	 add	signalling load
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org Short version:        ITR-based reachability testing scales better
                      than host-based reachability testing - and
                      so a hybrid might be worth thinking about.

                      However, neither of them scale acceptably, so
                      there is no point seriously considering a
                      hybrid.

                      The only reachability testing system which
                      scales acceptably is Ivip's approach of
                      using a separate set of servers to probe full
                      reachability, via multiple ETRs, to the
                      destination network.  The probing load does
                      not increase in proportion to either the number
                      of ITRs or sending hosts currently sending
                      packets to the destination network.

                      If the ITR was in the ISP, then Ivip's approach
                      does not cope with certain patterns of outages
                      which ITR-based or host-based reachability
                      testing approaches could probably cope with.
                      However, as long as the ITR is in the sending
                      host or the multihomed sending host's network
                      (or is an OITRD) then the outcome is just as
                      good as today, since BGP copes with those
                      outages pretty quickly.

                      While host-based probing could cope well with
                      an outage to the upstream ISP compared with
                      ITR-based probing from an ISP-located ITR, this
                      is already coped with perfectly well by LISP
                      etc. or Ivip where the multihomed end-user
                      network has its own ITRs.  (Non-multihomed
                      end-user networks can have their own ITRs or
                      use ITRs in the single upstream ISP.)


Pekka Nikander wrote, quoting Joel Halpern:

>> Conversely, although the liveness testing must be on the basis of
>> individual ETRs, it does seem likely that many hosts in a site will be
>> trying to reach endpoints behind the same set of ETRs.  As such,
>> having a border guy (or someone else, if you really want to complicate
>> life) testing / monitoring that liveness / reachability on behalf of
>> the various sources within the site would seem likely to
>>
>>   1) reduce the probing traffic
>>   2) increase the odds of having accurate data when packets need to be
>>      sent.
> 
> Exactly.

A further reduction in probing, and greater flexibility in deciding
which ETR the traffic packets will be tunneled to can be achieved by
the Ivip approach of using a completely separate reachability probing
system - separate from ITRs and from sending hosts.  The end-user
would either do this, or have some company do it for them.  The
probing could be done from multiple points all over the Net, to the
ETRs or more likely through the ETRs to routers and/or hosts in the
end-user network.

Most likely, that company's specialised probing system would be
configured to make the decision on how best to map the destination
network's micronets - and would change the mapping within seconds,
according to whatever criteria were specified by the administrators
of the destination network.  Within a few seconds, all ITRs in the
world handling packets addressed to these micronets would be
tunneling these packets to the ETR chosen in the new mapping decision.

This is a generalised DFZ->destination-network probing approach,
since the probing servers would, broadly speaking, be in the DFZ.
This is the only scalable approach, since the same level of probing
would still occur if 100,000 ITRs were sending packets to the
destination network as if one, none or a few were sending packets.

The key to using a separate, dedicated, reachability probing system
(quite outside the Ivip system itself, and so which can be made to
work on any principles, any protocols etc. which suit the destination
network being probed) is Ivip's real-time mapping distribution
system.  This tells all the ITRs which need to know which ETR to
tunnel the packets to.  This greatly simplifies the ITR and ETR
design and separates out reachability testing and the resulting
decision-making from the core-edge-separation system itself. (LISP,
APT, TRRP and Six/One Router monolithically integrate them.)

So having something other than the ITRs doing the probing and making
the decisions does involve some extra complexity - a real-time
mapping system.  I believe this is a small price to pay for the
greater flexibility, more robust probing (all the way to the
destination network, not just to the ETRs), greater simplicity in
ITRs and ETRs, reduction in probing traffic etc.  Also, it enables
real-time control of ETR address for incoming TE.


> To recap what I tried to say:
> 
> So far we've had two models on the table:  tunnel-router-based and
> host-based.  The tunnel-router based obviously checks reachability at
> the TR granularity, and host-based on host granularity.  

The last sentence applies to LISP, APT, TRRP etc. but not to Ivip.

With Ivip, end-user networks can and generally will probe
reachability as they choose, including most likely through each ETR
to their network, including to individual hosts if they like.

So this is finer grained at the receiving end than just to ETR
granularity.  One ETR in an ISP may be perfectly reachable and may
reach multiple destination end-user networks, but not the destination
end-user network in question.  Ivip copes with this perfectly well -
that network's micronets are mapped to an ETR (typically in another
ISP) which can reach the network.

The probing would typically be done from multiple sites, including
from actual ITRs or through actual ITRs, all over the Net.

Host-to-host reachability testing is arguably the most adaptable,
since it tests the full path used by traffic packets.  So this
approach can, in principle, cause the choices made by the sending
host (which address of the destination use to send the packets to) to
adapt to every conceivable network outage.

ITR-to-ETR probing on its own doesn't tell each ITR about the
destination network being unreachable - so it needs to be done in a
way that the ETR confirms the network is reachable.  This could be
done via:

1 - ITR->ETR probing, with a special protocol telling the ETR which
    end-user network (or perhaps an EID address within that network)
    the probe concerns.  In this way, the ETR can return a message
    that it is reachable, but that the destination network is not.

2 - ITR->(transparently through the ETR)->destination-network probing.
    This would require some new protocol or some identified router
    in the destination network which would always respond to
    existing probe protocols.  This would require extra information
    in the mapping data, to specify the one or more addresses in the
    destination network each ITR should probe.

I figure LISP etc. will need to do one of the above.  AFAIK, at
present, LISP only involves ITRs probing reachability of whole ETRs -
not the ability of the ETR to deliver the packets to any particular
destination EID.

In this diagram (from my message Re: No liveness requirement in the
ID/Loc Split concept 15 Jan) the sending host is HA, the ITRs are
shown in the ISP networks.  (However, the ITRs could be in the NA
sending host's network, or with Ivip, the ITR function could be built
into the sending host.  I depict this in Fig 2.)

                        ~~~~~~~~~~~
   NA           ISP1   ~           ~   ISP3         NB
            PE1      BR1---     ---BR3     PE3
 ........  /    ITR1   ~\         /~   ITR3   \  ........
 .      . /     ETR1   ~ \       / ~   ETR3    \ .      .
 . HA---CEA            ~    DFZ    ~           CEB---HB .
 .      . \            ~ /       \ ~           / .      .
 ........  \   ISP2    ~/         \~   ISP4   /  ........
            PE2      BR2---     ---BR4      PE4
               ITR2    ~           ~   ITR4
               ETR2     ~~~~~~~~~~~    ETR4

(Fig 1. LISP etc. or Ivip with ITRs in ISPs.)

Either form of probing from the ITR is able to cope fine with any DFZ
outages between the ITR (ITR1 or ITR2, depending on how CEA sends out
the packets) and the two ETRs in question: ETR3 and ETR4.

In addition, either form of probing from the ITR can cope separately
with (for instance) an outage between ITR1 and ETR4, while from some
other ITR, for another sending host, there is an outage to ETR3 but
not to ETR4.

Ivip's approach is not so flexible.  With Ivip, I am assuming that
each ETR is either:

1 - Reachable from essentially every ITR, or

2 - Unreachable from some (or all) ITRs to the degree that the
    destination-network's probing system will detect the problem and
    change the mapping to the ETR which is reachable.

So ITR-based probing appears to have this advantage over this
approach h (ITRs in the ISPs) to Ivip.  The advantage is limited,
however, since BGP already does a pretty good job of resolving loss
of links and routers between ISPs.   The proper way to deploy Ivip is
to ensure that every multihomed end-user network has its own ITRs.


Host-based probing has the additional advantage that it can detect
outages from the HA to the upstream ISPs ISP1 and ISP2.  The same
would apply for an ITR-based probing system, if the ITR was located
in the sending host's network NA.

However, the problem of outages from the sending host to the upstream
ISPs is not one which requires any special solutions, since the
sending-host's network's Customer Edge (CEA) router does this task
just fine.  This will continue to work fine for Ivip and for LISP,
APT, TRRP etc. no matter whether the ITR is located in the sending
host's network or in the upstream ISP.

Also, maybe in the case of non-upgraded networks in the Ivip-era or
LISP-era which are either single-homed or multihomed with current BGP
techniques,  here are no ITRs in the ISP or the sending host's
network.  In that case, there are Ivip OITRDs (Open ITRs in the DFZ)
or LISP PTRs (Proxy Tunnel Routers) somewhere in the DFZ.  Again, the
existing behavior of the CE router in the sending host's network
automatically sends outgoing packets to whichever ISP is currently
preferred according to outgoing TE preferences and which of the ISPs
are currently reachable and advertising the micronet (Ivip) or EID
(LISP) prefixes which are advertised by the OITRDs or PTRs.


The next section concerns how ITR-based probing or Ivip's approach
works when an upstream ISP is reachable, but that ISP has either no
connectivity to the rest of the Net, or patchy connectivity.

  LISP etc. with ITRs in the ISPs:

     Packets would be lost if the CE router sent packets to ISP1
     where ITR1 accepted them, but was then unable to send them to
     the ETR.

     (Would ITR1 recognise it couldn't reach beyond ISP1 and then
     somehow signal this so CEA would no longer send packets to
     ISP1?)


  Ivip with ITRs in the ISPs:

     As for LISP, but this is not how Ivip should be deployed -
     multihomed networks should either have their own ITRs, or
     rely entirely on OITRDs outside their network and outside
     their ISPs.

The problem in both cases is that CEA is sending packets to ISP1
which can't get them to their destination.  That is beyond the scope
of LISP etc. or Ivip to solve.

A better outcome is if the ITR is in the sending network, assuming
this is a multihomed end-user network.  For singlehomed end-user
networks, there is no difference in this probing respect between
having the ITR in the end-user network or in the single upstream ISP.
 (Also, OITRDs or PTRs are beyond these ISPs and are somewhere in the
DFZ.)

                            ~~~~~~~~~~~
   NA               ISP1   ~           ~   ISP3         NB
                PE1      BR1---     ---BR3     PE3
 ............  /           ~\         /~   ITR3   \  ........
 .          . /     ETR1   ~ \       / ~   ETR3    \ .      .
 . HA-ITRA-CEA            ~    DFZ    ~           CEB---HB .
 .          . \            ~ /       \ ~           / .      .
 ............  \   ISP2    ~/         \~   ISP4   /  ........
                PE2      BR2---     ---BR4      PE4
                           ~           ~   ITR4
                   ETR2     ~~~~~~~~~~~    ETR4

(Fig 2 - Sending host network has its own ITRs, and/or ITR function
in the sending host.)

  LISP etc. with ITRs in the sending host's network (NA):

    Now there is no problem, since CEA is handling packets which
    have already been encapsulated.  If ISP1 is disconnected from the
    Net, its PE router will not be advertising any prefixes, so CEA
    will send all outgoing packets to ISP2.

    Note, this is not applicable to Six/One Router - the equivalents
    of ITRs are always in the ISPs.

  Ivip with ITRs in the sending host's network (NA):

    As above and likewise with Ivip's forwarding approaches, based on
    the ETR address (or some of the address, for IPv6) being encoded
    into a modified IP header.  There is no need for the actual ITRs
    to do probing, since the disconnection of ISP1 from the Net is
    detected by CEA due to ISP1's PE1 router no longer advertising
    routes to any addresses outside ISP1.

So while host-based probing also detects problems as close as the
upstream ISP, the core-edge separation systems (LISP, APT, TRRP and
Ivip) have no problem in this regard, as long as each upgraded
multihomed end-user network has its own ITRs.  (Or non-upgraded
BGP-multihomed networks rely on OITRDs/PTRs rather than ITRs in their
upstream ISPs.)

> This has
> received criticism that a host-based model causes more
> signalling/reachability testing traffic than the tunnel-router-based one.

My critique along these lines is:

  Fundamental objections to a host-based scalable routing solution
  http://www.irtf.org/pipermail/rrg/2008-November/000233.html

> My point was a simple one: not necessarily so.  If TR-level granularity
> is acceptable, then it is doable with a hybrid host+TR-based solution
> (like the one I've been hand waving during the last month or so), and in
> that case the amount of reachability testing / signalling will be at the
> *same* level as for a TR-only solution.

I don't think ITR-based reachability testing is acceptable.

I think the only scalable approach is to have neither sending hosts
nor ITRs doing the reachability probing and decision-making.  The
only proposal so far which achieves this is Ivip.

 - Robin                           http://www.firstpr.com.au/ip/ivip/




_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Wed Jan 21 21:28:43 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1EAFE3A6801; Wed, 21 Jan 2009 21:28:43 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 57F563A6801 for <rrg@core3.amsl.com>; Wed, 21 Jan 2009 21:28:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.847
X-Spam-Level: 
X-Spam-Status: No, score=-0.847 tagged_above=-999 required=5 tests=[AWL=0.270,  BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rp0m0GnbYv6s for <rrg@core3.amsl.com>; Wed, 21 Jan 2009 21:28:41 -0800 (PST)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by core3.amsl.com (Postfix) with ESMTP id 322FF3A63D2 for <rrg@irtf.org>; Wed, 21 Jan 2009 21:28:40 -0800 (PST)
Received: by dog.tcb.net (Postfix, from userid 0) id D772926866A; Wed, 21 Jan 2009 22:28:23 -0700 (MST)
Received: from mbp.castlepoint.net (71-215-66-230.hlrn.qwest.net [71.215.66.230]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; Wed, 21 Jan 2009 22:28:23 -0700 (MST) (envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=71.215.66.230; client-port=4733; syn-fingerprint=65535:55:1:64:M1460,N,W3,N,N,T,S MacOS 10.4.8; data-bytes=0
Message-Id: <11CDEC3E-2ED2-413C-840F-11A40398640D@castlepoint.net>
From: Shane Amante <shane@castlepoint.net>
To: Robin Whittle <rw@firstpr.com.au>
In-Reply-To: <4977E638.4060501@firstpr.com.au>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Wed, 21 Jan 2009 22:28:22 -0700
References: <B25790E2-8D3C-4A55-848C-F461982DC3F6@nomadiclab.com>	<20090119213701.GA34129@cisco.com>	<4975143E.9020404@gmail.com> <49752F9C.4050006@joelhalpern.com> <F2DA6B6C-6E73-4FA4-A2DD-2966FA400211@nomadiclab.com> <4977E638.4060501@firstpr.com.au>
X-Mailer: Apple Mail (2.930.3)
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] Why a host-based solution does not necessarily	 add	signalling load
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org Robin,

I find this whole discussion of a separate reachability probing system  
to be fraught with a number of economic, security, more importantly,  
operational problems.

On Jan 21, 2009, at 8:21 PM, Robin Whittle wrote:
> A further reduction in probing, and greater flexibility in deciding
> which ETR the traffic packets will be tunneled to can be achieved by
> the Ivip approach of using a completely separate reachability probing
> system - separate from ITRs and from sending hosts.  The end-user
> would either do this, or have some company do it for them.  The
> probing could be done from multiple points all over the Net, to the
> ETRs or more likely through the ETRs to routers and/or hosts in the
> end-user network.

Really?  There is no way companies are going to allow one of these 3rd- 
party "probing/reachability companies", even if they have a paid  
relationship with them, to probe through their ETR's to their internal  
network.  Who's to say that the probing company (or companies) doesn't  
get hacked and they're used as a launching point to attack the inside  
network of a company using them for services?



> Most likely, that company's specialised probing system would be
> configured to make the decision on how best to map the destination
> network's micronets - and would change the mapping within seconds,
> according to whatever criteria were specified by the administrators
> of the destination network.  Within a few seconds, all ITRs in the
> world handling packets addressed to these micronets would be
> tunneling these packets to the ETR chosen in the new mapping decision.
>
> This is a generalised DFZ->destination-network probing approach,
> since the probing servers would, broadly speaking, be in the DFZ.
> This is the only scalable approach, since the same level of probing
> would still occur if 100,000 ITRs were sending packets to the
> destination network as if one, none or a few were sending packets.
>
> The key to using a separate, dedicated, reachability probing system
> (quite outside the Ivip system itself, and so which can be made to
> work on any principles, any protocols etc. which suit the destination
> network being probed) is Ivip's real-time mapping distribution
> system.  This tells all the ITRs which need to know which ETR to
> tunnel the packets to.  This greatly simplifies the ITR and ETR
> design and separates out reachability testing and the resulting
> decision-making from the core-edge-separation system itself. (LISP,
> APT, TRRP and Six/One Router monolithically integrate them.)

This won't fly operationally.  First, I can't envision an economic  
model that would cause someone or, better yet, multiple probing/ 
reachability companies to be launched as you envision.  Ultimately,  
you're talking about not only a lot of fixed costs for servers and  
such, but more importantly the OpEx for colocation costs and bandwidth  
that company would be burning to send out millions, billions or  
trillions of "probes" to everyone's ETR on the planet.

Second, these probes from a 3rd-party probing/reachability company  
will not reliably tell end-user networks that there is, in fact, known  
"good" connectivity to an ETR, because of ECMP and/or LAG being used  
along certain paths within SP's networks and not others.  More  
specifically, ECMP and/or LAG are load-balancing mechanisms that SP's  
widely use to scale the physical BW between nodes in their network,  
(e.g.: to scale BW between a city-pair to 100G and [much] larger by  
logically bonding together multiple OC-192's, etc. into a single  
"bundle").  The key part of those technologies is core routers use IP  
header information, (L3 addresses and/or L4 port information), as  
input keys to their load-hashing algorithms to determine the  
particular output link in a LAG or ECMP "bundle" that a particular  
flow goes on.  The problem observed in operational networks today is  
that "soft-failures" cause a particular link in a bundle to stop  
forwarding traffic, which goes unnoticed to IGP's (OSPF or IS-IS) or  
BGP and, unfortunately, results in blackholing of customer traffic  
until the problem is isolated and "bad" link in the bundle is taken  
out of service.  Unfortunately, there aren't tools to diagnose this  
problem today so it's very difficult and time-consuming to  
troubleshoot & resolve these problems.  More to the point of why your  
proposal of 3rd-party probing companies will not work is:
- When these 3rd-party probing companies are transmitting probes  
toward an ETR they're going to be unable to construct *identical* EID  
within RLOC packets that would cause them to be hashed and push on the  
same links that are bound for that customer's ETR.  IOW, the 3rd-party  
probe company *will* get false-positives that will either: a)  leave  
the ETR's in service when there is a bad link blackholing traffic on a  
parallel path unseen by the 3rd-party company; or, b) falsely take an  
ETR out-of-service because the 3rd-party probing company saw traffic  
being blackholed on a link that may, in fact, carry very little or  
know end-user traffic toward that ETR.
- Economically, it's infeasible for this imaginary probing company, or  
set of probing companies, to be able to deploy servers to every POP in  
every ISP to ensure full coverage of these LAG & ECMP paths ... or,  
for that matter, a decent percentage of each operator's network that  
it can reasonably approximate reachability across all paths in that  
every ISP's networks.
- As an operator, I don't have much (any?) faith in trusting others to  
determine connectivity (or lack thereof) to/from my ETR's.  I trust my  
network and the configuration of my ITR's/ETR's to determine that.   
Furthermore, when someone goes wrong (e.g.: probes aren't returned) I  
can easily login to those devices (since I own them) and quickly  
troubleshoot the problem and restore service how *I* deem appropriate  
for my network.

So, to summarize, *if* we have to do probing, the only operationally  
and economically feasible method is either to/from the ITR's/ETR's or  
the end-systems themselves.  (More on this just below).


> So having something other than the ITRs doing the probing and making
> the decisions does involve some extra complexity - a real-time
> mapping system.  I believe this is a small price to pay for the
> greater flexibility, more robust probing (all the way to the
> destination network, not just to the ETRs), greater simplicity in
> ITRs and ETRs, reduction in probing traffic etc.  Also, it enables
> real-time control of ETR address for incoming TE.

This discussion does raise an interesting architectural point with  
respect to all map-and-encap solutions, which depend on reachability  
probing between ITR's and ETR's.  Specifically, do these reachability  
probes faithfully represent end-user (host-machine originated and  
terminated) flows so they are travelling along the same path as host- 
to-host data flows?  I would argue that they do not, (without  
substantially increasing the probing traffic load/bandwidth to  
"search" through all possible paths used by end-user traffic).

OTOH, solutions that either:
a) do proactive probing originating from hosts at something at or just  
below the TCP/UDP layer; or, better yet,
b) piggyback ***reachability*** detection along with active TCP/UDP  
traffic flow (cf: TCP ACK's) between hosts
... would faithfully represent that a given path really is working.

FWIW, I don't think there's a straightforward solution for map-and- 
encap solutions to the aforementioned probing over LAG/ECMP paths  
problem.  If there is, I'm all ears.  OTOH, if there's not a solution,  
I do not think we should gloss over it and, instead, I would strongly  
recommend we should point this out out very clearly within an  
"Operational Considerations" section of any/all map-and-encaps  
protocol specs or an overall/all-encompassing companion "Operational  
Considerations" document noting this and other 'challenges' that map- 
and-encaps can't feasibly address.  Said document(s) may prove helpful  
in evaluating the final set of candidate solutions that the RRG will  
offer its recommendation on.

-shane
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Wed Jan 21 21:38:38 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9619A3A67F1; Wed, 21 Jan 2009 21:38:38 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 151D23A677D for <rrg@core3.amsl.com>; Wed, 21 Jan 2009 21:38:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DT8Klpc1NrDZ for <rrg@core3.amsl.com>; Wed, 21 Jan 2009 21:38:36 -0800 (PST)
Received: from virtualized.org (trantor.virtualized.org [204.152.189.190]) by core3.amsl.com (Postfix) with ESMTP id 74DD83A68E7 for <rrg@irtf.org>; Wed, 21 Jan 2009 21:38:36 -0800 (PST)
Received: from [10.0.1.200] (c-71-198-3-247.hsd1.ca.comcast.net [71.198.3.247]) by virtualized.org (Postfix) with ESMTP id 765E1434B24; Wed, 21 Jan 2009 21:37:55 -0800 (PST)
Message-Id: <59075E8E-99D2-4CA0-90F3-881DE80303E8@virtualized.org>
From: David Conrad <drc@virtualized.org>
To: Paul Jakma <paul@jakma.org>
In-Reply-To: <alpine.LFD.2.00.0901201754180.31066@localhost.localdomain>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Wed, 21 Jan 2009 21:37:54 -0800
References: <B25790E2-8D3C-4A55-848C-F461982DC3F6@nomadiclab.com> <20090119213701.GA34129@cisco.com> <4975143E.9020404@gmail.com> <49752F9C.4050006@joelhalpern.com> <F2DA6B6C-6E73-4FA4-A2DD-2966FA400211@nomadiclab.com> <alpine.LFD.2.00.0901201604530.31066@localhost.localdomain> <C29F67D7-AD89-43CD-9A3E-76672D216667@virtualized.org> <alpine.LFD.2.00.0901201754180.31066@localhost.localdomain>
X-Mailer: Apple Mail (2.930.3)
Cc: RRG RG <rrg@irtf.org>
Subject: Re: [rrg] Why a host-based solution does not necessarily add signalling load
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org Paul,

On Jan 20, 2009, at 9:56 AM, Paul Jakma wrote:
> On Tue, 20 Jan 2009, David Conrad wrote:
>> On Jan 20, 2009, at 8:05 AM, Paul Jakma wrote:
>>>> a host-based model causes more signalling/reachability testing  
>>>> traffic than the tunnel-router-based one.
>>> What's the basis for thinking this, and are there any good studies/ 
>>> data to back it up?
>> Well, for one thing, a tunnel-router-based solution would typically  
>> cover some number of hosts.
> I assumed there was an implied ", to a significant enough extent for  
> it to matter" at the end of the sentence I quoted.

What meets your requirement of enough "to matter"?  Depending on  
deployment scenario, a tunnel-router-based solution could cover  
thousands of hosts or more.  Is that enough to matter?

Regards,
-drc

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Wed Jan 21 22:29:12 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ACDF43A681D; Wed, 21 Jan 2009 22:29:12 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 68CBD3A67F1 for <rrg@core3.amsl.com>; Wed, 21 Jan 2009 22:29:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.793
X-Spam-Level: 
X-Spam-Status: No, score=-2.793 tagged_above=-999 required=5 tests=[AWL=-0.544, BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r0zu-MfvSkAf for <rrg@core3.amsl.com>; Wed, 21 Jan 2009 22:29:05 -0800 (PST)
Received: from amailer.gwdg.de (amailer.gwdg.de [134.76.10.18]) by core3.amsl.com (Postfix) with ESMTP id 3D7733A681D for <rrg@irtf.org>; Wed, 21 Jan 2009 22:29:05 -0800 (PST)
Received: from dsl54026089.pool.t-online.hu ([84.2.96.137] helo=[192.168.1.101]) by mailer.gwdg.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <fu@cs.uni-goettingen.de>) id 1LPt3W-00073J-Oy for rrg@irtf.org; Thu, 22 Jan 2009 07:28:47 +0100
Message-ID: <49781331.8050802@cs.uni-goettingen.de>
Date: Thu, 22 Jan 2009 07:33:21 +0100
From: Xiaoming Fu <fu@cs.uni-goettingen.de>
Organization: University of Goettingen, Germany
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: rrg@irtf.org
X-Authenticated: Id:xfu
X-Virus-Scanned: (clean) by exiscan+sophie
Subject: [rrg] Call for papers: ICNP 2009
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="windows-1252"; Format="flowed"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org [Sincere apologies if you receive multiple copies of this CFP.]

                          CALL FOR PAPERS
                             ICNP 2009
        17th IEEE International Conference on Network Protocols
                       October 13-16, 2009
                    Princeton, New Jersey, USA
                  http://www.ieee-icnp.org/2009

ICNP, the IEEE International Conference on Network Protocols is the
premier conference covering all aspects of network protocols. ICNP will
be held in its seventeenth year at Princeton, New Jersey from October
13-16th, 2009. Papers with significant research contributions on network
protocols are solicited for submission. Papers related to all aspects of
network protocols including design, implementation, analysis,
performance and specification are relevant. Papers must not be
previously published nor under review in any other conference or
journal. Only original papers that have not been published previously or
submitted for publication and under review by another conference or
journal elsewhere can be submitted. Papers containing plagiarized
material will be subject to the IEEE Plagiarism policy and will be
rejected without review. Topics of interest include, but are not limited to:
=95 Protocol design, implementation, testing and analysis.
=95 Measurement studies of protocol performance.
=95 Protocols for wireless ad hoc and sensor networks.
=95 Protocols for peer-to-peer networks.
=95 Protocols for specific functions such as routing, flow/congestion
control, network management.
=95 Protocols for security, survivability and fault-tolerance.

Papers must be directly relevant to protocols. Papers on general
networking where protocols are only a secondary focus will be considered
only if they are of exceptionally high quality.

Papers will be subject to a double-blind review process. The identity of
authors and referees will not be revealed to each other. To ensure blind
reviewing, the authors' names and affiliations should not appear in the
paper. Bibliographic references should protect the authors' anonymity.
Papers should adhere to the IEEE format and should not be more than 10
pages. The font size should not be smaller than 10pt.  Further
instructions will be posted on the ICNP website
(http://www.ieee-icnp.org/2009).

Authors of accepted papers will be expected to register for the
conference and the paper must be presented at the conference in order
for the paper to appear in the conference proceedings.

Important Dates:
Abstract Submission:        April 10, 2009 8:59 P.M. EDT
Paper Submission:           April 17, 2009 8:59 P.M. EDT (Hard Deadline)
Notification of Acceptance: July  28, 2009
Camera Ready Version Due:   September 4, 2009

Organizing Committee:

Executive Committee:
David Lee                   Ohio State University, USA (Chair)
Mostafa Ammar               Georgia Tech. USA
Ken Calvert                 University of Kentucky, USA
Teruo Higashino             Osaka University, Japan
Raymond Miller              University of Maryland, USA

General Chairs:
K.K. Ramakrishnan           AT & T Labs Research, USA
Henning Schulzrinne         Columbia University, USA

Program Chairs:
Timothy Griffin             University of Cambridge, U.K.
Srikanth V. Krishnamurthy   University of California, Riverside, USA

For more details, visit the conference webpage:
http://www.ieee-icnp.org/2009

Regards,
Xiaoming Fu
IEEE ICNP'09 Publicity Chair



_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Thu Jan 22 05:13:12 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0792728C16F; Thu, 22 Jan 2009 05:13:12 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6A96B28C16F for <rrg@core3.amsl.com>; Thu, 22 Jan 2009 05:13:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 51ZMpa-ItOdW for <rrg@core3.amsl.com>; Thu, 22 Jan 2009 05:13:09 -0800 (PST)
Received: from hibernia.jakma.org (cl-9.dub-01.ie.sixxs.net [IPv6:2001:770:100:8::2]) by core3.amsl.com (Postfix) with ESMTP id 8D51028C15A for <rrg@irtf.org>; Thu, 22 Jan 2009 05:13:08 -0800 (PST)
Received: from melandri.gla.jakma.org (melandri.jakma.org [81.168.24.37]) (authenticated bits=0) by hibernia.jakma.org (8.14.3/8.14.2) with ESMTP id n0MDCeTi028898 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 22 Jan 2009 13:12:47 GMT
Date: Thu, 22 Jan 2009 13:12:40 +0000 (GMT)
From: Paul Jakma <paul@jakma.org>
X-X-Sender: paul@localhost.localdomain
To: David Conrad <drc@virtualized.org>
In-Reply-To: <59075E8E-99D2-4CA0-90F3-881DE80303E8@virtualized.org>
Message-ID: <alpine.LFD.2.00.0901221312320.8689@localhost.localdomain>
References: <B25790E2-8D3C-4A55-848C-F461982DC3F6@nomadiclab.com> <20090119213701.GA34129@cisco.com> <4975143E.9020404@gmail.com> <49752F9C.4050006@joelhalpern.com> <F2DA6B6C-6E73-4FA4-A2DD-2966FA400211@nomadiclab.com> <alpine.LFD.2.00.0901201604530.31066@localhost.localdomain> <C29F67D7-AD89-43CD-9A3E-76672D216667@virtualized.org> <alpine.LFD.2.00.0901201754180.31066@localhost.localdomain> <59075E8E-99D2-4CA0-90F3-881DE80303E8@virtualized.org>
User-Agent: Alpine 2.00 (LFD 1167 2008-08-23)
Mail-Copies-To: paul@jakma.org
Mail-Followup-To: paul@jakma.org
X-NSA: al aqsar fluffy jihad cute musharef kittens jet-A1 ear avgas wax ammonium bad qran dog inshallah allah al-akbar martyr iraq hammas hisballah rabin ayatollah korea revolt pelvix mustard gas x-ray british airways washington peroxide cool
MIME-Version: 1.0
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.1.1 (hibernia.jakma.org [212.17.55.49]); Thu, 22 Jan 2009 13:12:49 +0000 (GMT)
Cc: RRG RG <rrg@irtf.org>
Subject: Re: [rrg] Why a host-based solution does not necessarily add signalling load
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org On Wed, 21 Jan 2009, David Conrad wrote:

> Paul,
>
>> I assumed there was an implied ", to a significant enough extent for it to 
>> matter" at the end of the sentence I quoted.
>
> What meets your requirement of enough "to matter"?  Depending on 
> deployment scenario, a tunnel-router-based solution could cover 
> thousands of hosts or more.  Is that enough to matter?

It's going to be subjective to a point, but determining "to matter" 
would involve comparing the control-overhead to the actual 
data-bearing traffic, rather than focusing solely on the difference 
in control traffic between end-host and intermediary based solutions.

Having a tunnel-router do the liveliness tests for 1000 hosts might 
save 999 instances of control traffic, but if the 999 instances of 
control traffic comprise 1-2% of the data traffic - then should we 
care? (Is there a data-communications version of Amdahl's Law I can 
quote here?).

By my back-of-the-envelope calculations, a Shim6/REAP solution has 
Order(1.2%) overhead relative to data-traffic (on a low amount of 
traffic, 24kB - e.g. fetching the google front-page) for the normal 
case. Failure cases presumably might take slightly more - but failure 
is not the common case. Solid quantitative studies would be really 
useful.

So basically, where's the awful overhead of host-based signalling, 
relative to what matters: the actual data?

It seems it would be good to have data to back up such an assertion, 
rather than accepting it blindly and introducing a lot of extra 
complexity (and losing much fate-sharing) to optimise an apparently 
relatively-trivial overhead.

regards,
-- 
Paul Jakma	paul@clubi.ie	paul@jakma.org	Key ID: 64A2FF6A
Fortune:
   "I always avoid prophesying beforehand because it is much better
   to prophesy after the event has already taken place. " - Winston
   Churchill
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Thu Jan 22 05:19:11 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5B9203A6911; Thu, 22 Jan 2009 05:19:11 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 70ECD3A685B for <rrg@core3.amsl.com>; Thu, 22 Jan 2009 05:19:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.585
X-Spam-Level: 
X-Spam-Status: No, score=-1.585 tagged_above=-999 required=5 tests=[AWL=0.310,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 10DzZkd4phR8 for <rrg@core3.amsl.com>; Thu, 22 Jan 2009 05:19:02 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123]) by core3.amsl.com (Postfix) with ESMTP id 21B6028C15A for <rrg@irtf.org>; Thu, 22 Jan 2009 05:19:01 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6]) by gair.firstpr.com.au (Postfix) with ESMTP id AEC4C175730; Fri, 23 Jan 2009 00:18:43 +1100 (EST)
Message-ID: <497872B2.2020609@firstpr.com.au>
Date: Fri, 23 Jan 2009 00:20:50 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: RRG <rrg@irtf.org>
Subject: [rrg] Ivip's separate reachability testing system, ECMP, LAG etc.
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org Hi Shane,

Thanks for your response to my message in the "Why a host-based
solution does not necessarily add signalling load" thread:

  http://www.irtf.org/pipermail/rrg/2009-January/000838.html

I am replying with a more specific Subject line.  You wrote:

> I find this whole discussion of a separate reachability probing
> system to be fraught with a number of economic, security, more
> importantly, operational problems.
>
>> A further reduction in probing, and greater flexibility in
>> deciding which ETR the traffic packets will be tunneled to can
>> be achieved by the Ivip approach of using a completely separate
>> reachability probing system - separate from ITRs and from
>> sending hosts.  The end-user would either do this, or have some
>> company do it for them.  The probing could be done from multiple
>> points all over the Net, to the ETRs or more likely through the
>> ETRs to routers and/or hosts in the end-user network.
>
> Really?  There is no way companies are going to allow one of these
>  3rd-party "probing/reachability companies", even if they have a
> paid relationship with them, to probe through their ETR's to their
> internal network.  Who's to say that the probing company (or
> companies) doesn't get hacked and they're used as a launching
> point to attack the inside network of a company using them for
> services?

I can't see any inherent security problem.  The probing could be by
some established protocol, or a new one.  In either case, there is no
need for the device which responds to do anything more than respond.
 So there is not any need for the protocol to be capable of altering
the responding device, running code on it etc.

Maybe some fancy protocol might be required, but ordinary ping should
do the trick.  Several (or perhaps dozens of) separately located,
probe servers send an ordinary ping packet to the CE router, to some
router or host behind the CE router - whatever the customer (the
administrators of the end-user network being probed) want.

The ping packet would contain a nonce, and the echo reply would
contain the nonce too - so it is easy to make it secure against an
of-path attacker sending forged echo replies.

The probing server would act in some ways as an ITR.  It generates a
ping packet and tunnels it to the device to be pinged.  ("Tunnel" in
this case means encapsulate, or for Ivip's forwarding modes, altering
the IP header and passing the packet to routers which recognise this
new header format and forward according to it.  See links at end.)

However, while an ITR always looks up the current mapping from a
local full database query server (assuming all ITRs are caching
ITRs), the probing server has its own arrangements for which ETR to
tunnel the packet to, in order to reach the probed device.

For instance multiple probing servers would each send probes to one
or perhaps more devices in the destination network.  For each such
device, which is on a micronet (EID in LISP terminology) address, the
device could be reached by two or more ETRs.  (I am assuming two or
more upstream ISPs, since this is a multihomed network.  Whether the
ETRs are physically at the ISPs, or physically at the destination
network, doesn't matter.)

So Probing Server A would periodically generate two packets with the
destination address of Device N in the destination network.  One
would be tunneled to some ETR X and the other to some ETR Y in
another ISP.  Each packet would have a different nonce so the probing
server could keep a track of reachability from itself to Device N via
the two ETRs.

The echo replies could come back via any one of the destination
network's upstream ISPs.  The purpose of this system is to test
reachability of the destination multihomed end-user network via
incoming packets (coming into this network) via multiple ETRs.

  {If it was desired to test outgoing reachability from the
   destination network to various parts of the DFZ - such as the
   various locations of probing servers - then this would be a
   separate process.  The result of that process would be to better
   inform the CE router's decision about where to send outgoing
   packets (via one upstream ISP or another) - including perhaps by
   sensing packet loss due to congestion in or beyond the various
   upstream ISPs.  However, that is a completely separate project
   from the need for test inbound reachability in order to change the
   mapping so traffic uses an ETR which is currently working better
   than one which is not working properly.}

Since all this could be done via ordinary ping, I don't see how there
are any security problems in this.   It would be up to the customer
which routers or hosts in their network were probed, how often etc.

If the ETRs are in the upstream ISPs, probably all that needs to be
tested is reachability to the CE router.

Even if there were security problems, how could Ivip's approach be
less secure than the alternatives: to have any number of ITRs or
sending hosts probing reachability in some way?  At least with Ivip's
approach, the customer can know, or specify, which probing servers
probe its network.  Then, if there were any security problems, the
responding devices could be configured to ignore probes from any
other IP addresses.


>> Most likely, that company's specialised probing system would be
>> configured to make the decision on how best to map the
>> destination network's micronets - and would change the mapping
>> within seconds, according to whatever criteria were specified by
>> the administrators of the destination network.  Within a few
>> seconds, all ITRs in the world handling packets addressed to
>> these micronets would be tunneling these packets to the ETR
>> chosen in the new mapping decision.
>>
>> This is a generalised DFZ->destination-network probing approach,
>>  since the probing servers would, broadly speaking, be in the
>> DFZ. This is the only scalable approach, since the same level of
>> probing would still occur if 100,000 ITRs were sending packets
>> to the destination network as if one, none or a few were sending
>> packets.
>>
>> The key to using a separate, dedicated, reachability probing
>> system (quite outside the Ivip system itself, and so which can
>> be made to work on any principles, any protocols etc. which suit
>> the destination network being probed) is Ivip's real-time
>> mapping distribution system.  This tells all the ITRs which need
>> to know which ETR to tunnel the packets to.  This greatly
>> simplifies the ITR and ETR design and separates out reachability
>> testing and the resulting decision-making from the
>> core-edge-separation system itself. (LISP, APT, TRRP and Six/One
>> Router monolithically integrate them.)
>
> This won't fly operationally.  First, I can't envision an economic
> model that would cause someone or, better yet, multiple
> probing/reachability companies to be launched as you envision.

Depending on the sophistication of the probing service, it shouldn't
be too hard to write the code, run the servers etc.  They need to be
securely linked together, be a redundant, distributed, network etc.
It is not trivial, but it is not inordinately expensive.  The servers
can be bog-standard COTS devices, which are perfectly fast and
reliable.  They can be sitting in data centres in various locations -
including simply by means of renting a few servers in various hosting
companies.

No-doubt there would be some open-source code for a probing system,
and then various folks might set up cooperative sets of servers to do
the work for themselves.  Small-time operators could use the
open-source code to make their own probing networks just by renting
servers in a bunch of data centres.


> Ultimately, you're talking about not only a lot of fixed costs for
> servers and such, but more importantly the OpEx for colocation
> costs and bandwidth that company would be burning to send out
> millions, billions or trillions of "probes" to everyone's ETR on
> the planet.

Sure, but the bandwidth is not high - the packets can be short.
Bandwidth is cheap, especially for continual rates of usage like
this.  A couple of hundred dollars a month per server would do the
trick, unless business was so brisk that the probe volume grew to
something really big - but by then, there would be plenty of cash to
spend more.

A good service would offer all sorts of flexible options in terms of
the probe rate, the number of probing servers which do the probing,
fancy algorithms for ignoring short outages if the customer wanted
them ignored etc.  However, a more straightforward reachability
probing service would take its marching orders something like this:

   One or more IP addresses to probe (eg CE router, internal routers,
   hosts etc.)

   List of two or more ETRs to probe these by.

   Frequency of probing.

   Success rate above which reachability will be considered good.

   How long to wait if probes from one or more probe servers are
   not acknowledged before changing the mapping to use another ETR.

   How long to wait once connectivity via the original ETR is found
   to be restored before changing the mapping back to the original
   ETR.

   List of the current micronets.

   Preference for each micronet for which ETR to use if both are
   working.

   Username and password by which the probing system could change the
   mapping of all these micronets, via whatever RUAS (Root Update
   Authority System) company, or intermediary to an RUAS, the
   destination network uses to send its real-time mapping changes.

   The end-user network retains control of their mapping by being
   able to generate such usernames and passwords for their mapped
   address space - so the end-user network can easily change these
   settings at the RUAS or whatever company to prevent the current
   probing service changing their mapping if the current company
   is abandoned in favour of some other company, or if the
   destination network wants to directly control its own mapping.


Any such service would also have to be secure.  I am assuming the
service itself would be given the credentials to alter the mapping of
the destination network's micronets.  If the probing service simply
conveyed the results to the destination network, then this is less of
a security risk - but the communication still has to be done securely.

I think most end-user networks would prefer some purpose built,
secure, distributed, external system to execute the decisions and
make the mapping changes - from outside their own network.

Probing companies would develop their probing and decision-making
algorithms in response to demand.

None of this probing stuff needs to be specified as part of Ivip or
any other such real-time mapping core-edge separation system.

The probing arrangements are completely separate from the core-edge
separation system itself and so it is up to the probing companies and
their customers exactly how it would be done.  IETF standards would
be good, of course, but they would be entirely modular and separate
from Ivip or whatever.  Such modularity and open-ended flexibility is
impossible with LISP, APT, TRRP (or Six/One Router I guess) because
these all build the probing and decision-making functionality into
the ITRs.  Host-based systems are equally monolithic.


> Second, these probes from a 3rd-party probing/reachability company
> will not reliably tell end-user networks that there is, in fact,
> known "good" connectivity to an ETR, because of ECMP and/or LAG
> being used along certain paths within SP's networks and not
> others.  More specifically, ECMP and/or LAG are load-balancing
> mechanisms that SP's widely use to scale the physical BW between
> nodes in their network, (e.g.: to scale BW between a city-pair to
> 100G and [much] larger by logically bonding together multiple
> OC-192's, etc. into a single "bundle").  The key part of those
> technologies is core routers use IP header information, (L3
> addresses and/or L4 port information), as input keys to their
> load-hashing algorithms to determine the particular output link in
> a LAG or ECMP "bundle" that a particular flow goes on.  The
> problem observed in operational networks today is that
> "soft-failures" cause a particular link in a bundle to stop
> forwarding traffic, which goes unnoticed to IGP's (OSPF or IS-IS)
> or BGP and, unfortunately, results in blackholing of customer
> traffic until the problem is isolated and "bad" link in the bundle
> is taken out of service.  Unfortunately, there aren't tools to
> diagnose this problem today so it's very difficult and
> time-consuming to troubleshoot & resolve these problems.  More to
> the point of why your proposal of 3rd-party probing companies will
> not work is: - When these 3rd-party probing companies are
> transmitting probes toward an ETR they're going to be unable to
> construct *identical* EID within RLOC packets that would cause
> them to be hashed and push on the same links that are bound for
> that customer's ETR.  IOW, the 3rd-party probe company *will* get
> false-positives that will either: a)  leave the ETR's in service
> when there is a bad link blackholing traffic on a parallel path
> unseen by the 3rd-party company; or, b) falsely take an ETR
> out-of-service because the 3rd-party probing company saw traffic
> being blackholed on a link that may, in fact, carry very little or
> know end-user traffic toward that ETR. - Economically, it's
> infeasible for this imaginary probing company, or set of probing
> companies, to be able to deploy servers to every POP in every ISP
> to ensure full coverage of these LAG & ECMP paths ... or, for that
> matter, a decent percentage of each operator's network that it can
>  reasonably approximate reachability across all paths in that
> every ISP's networks.

OK - but how is the scheme I propose going to be any more affected
(false detection of outages not actually affecting traffic, or not
detecting failures which do affect traffic) by the flaky nature of
these outages than a system in which ITRs probe reachability (to
ETRs, which is not enough - or to CE routers or beyond)?

Googling ECMP and LAG finds only 2.3k pages with a lot of stuff from
one vendor (Force 10), a US patent 7190696 (Rajeev Manur et al.) and
your own "draft-amante-oam-ng-requirements".  Without further
reseach, I can't easily tell how widely these techniques are used.
Assuming such techniques are widely used, what do the routers hash on?

Can you be sure that for every host-to-host session, that the
resulting tunneled packets from an ITR will hash to the same value
and so share the same physical path?  Can you be sure that the ITR's
attempt to probe reachability to the ETR, or through the ETR to the
CE router in the destination network, will hash to the same value?

If not, then your critique probably applies to ITR-based probing too.

What about host-based probing?  Depending on how a host-based system
works, how can you be sure these hash algorithms will send all
traffic packets for a particular host session on the same physical
path as whatever probe packets the host sends?

Likewise for all these approaches, including Ivip, what about similar
problems in the path by which the probe replies travel?

While I agree that the use of fancy techniques which lead to flakier
outage behaviour does pose a difficulty for Ivip's approach to
reachability testing, I would want to see a lot more detail before I
concluded these problems were significantly worse for Ivip than for
LISP etc. core-edge separation schemes or some as-yet not designed
host-based core-edge elimination schemes.

One major general advantage of Ivip's modular approach is that if the
destination network doesn't like how reachability testing is done,
and or doesn't like how this leads to decisions about real-time
changes to its mapping, then they can easily hire another company
which does a better job.  That is impossible for all proposals and
classes of proposals discussed in the RRG other than Ivip, since they
all build the reachability testing and decision making monolithically
into the scalable routing solution.


> - As an operator, I don't have much (any?)
> faith in trusting others to determine connectivity (or lack
> thereof) to/from my ETR's.

But if you don't like my suggested Ivip approach, you can always run
your own system as you wish.

I can't see that running your own system is going to be any less
secure, any less reliable etc. than the non-Ivip alternatives, in
which any Tom-Dick or Harriet ITR in the world (too many to know
about) expects to be able to probe reachability, and will do
something you don't want if your network fails to respond to pretty
much every one of their probe packets.

Worse still, a host-based solution: you are leaving reachability
testing to every host in the world which might want to send a packet
to your network.  Your network needs to work well with all them,
including potentially badly written host implementations which are
likely to be more numerous, complex and flaky than the smaller number
of ITR implementations in the LISP etc. model.

With Ivip, you don't have to worry about any of this.

You either hire a company which probes your network and makes mapping
decisions the way you like, or you do it yourself.

Ivip's approach is perfectly scalable.  Probe traffic is continual
and low-level.  It doesn't matter whether there are zero hosts or
ITRs sending packets to your network now, or a hundred million.

All the other architectures suffer grave scaling problems.  They are
all monolithic and restricted to being very inflexible, since their
probing arrangements need to be set in stone and implemented on every
ITR (and probably every ETR, with some method of testing reachability
all the way to the destination network), or worse still, every host
in the Net.

> I trust my network and the
> configuration of my ITR's/ETR's to determine that.

I am assuming that "you" are the administrator of a multihomed
end-user network using Ivip micronet space, or alternatively LISP
etc. EID space, or its equivalent in APT, TRRP or Six/One Router - or
its equivalent in a host-based core-edge elimination scheme.

Your own servers cannot on their own determine that they are
reachable from the hosts who currently want to send you packets.
Likewise, they can't determine on their own the reachability from all
corners of the Net to the ETRs your multihomed end-user network
depends on for incoming packets.

In principle sending hosts or ITRs can determine it, by probing your
ETR, routers, destination hosts or whatever.  They could also
communicate this back to your network, but it is they - the non-Ivip
ITRs or sending hosts (in a host-based system) which need to make the
decision about how to send traffic packets to your network.  However,
those approaches have insurmountable scaling problems.

Ivip's approach scales well and enables you to determine
reachability, and to control mapping in real-time, however you like.

I was just suggesting that for most end-user networks, the best
approach would be to hire a company to do this for them.

Having the probing and data collection done from within your network
would be possible - but you would need to rely on external servers to
reflect back your probes.  (It does not scale if you want to probe
every currently active ITR or sending host.)

You could collect the information and make your own decisions about
changed mapping within your own network.  However, you would need to
have a fancy arrangement to make this work robustly when you need it
most - when there is network instability and one or more outages on
your upstream ISP links, or between those ISPs and the rest of the
Net.  A well engineered, distributed, network of probing servers run
by a specialist reachability probing company would always be able to
communicate reliably with your mapping company and make the changes
you specified they should make, in response to whatever they have
just determined about reachability.


> Furthermore,
> when someone goes wrong (e.g.: probes aren't returned) I can
> easily login to those devices (since I own them) and quickly
> troubleshoot the problem and restore service how *I* deem
> appropriate for my network.

I am not sure how this relates to an objection to Ivip's approach.
If you hire a probing company, it is pretty obvious that they will be
able to automatically communicate to you (wherever you are, outside
or inside your own network - assuming it is reachable by some means)
that something has gone wrong.  It is up to you to instruct that
company how to probe, how to decide about mapping changes, how to
report trouble to you etc.

You could roll your own system if you really want, but I figure most
multihomed end-user networks would prefer to pay a modest annual fee
to some specialist company which is motivated to serve them reliably,
and provide whatever probing, decision making etc. services you and
other such companies want.


> So, to summarize, *if* we have to do probing, the only
> operationally and economically feasible method is either to/from
> the ITR's/ETR's or the end-systems themselves.  (More on this just
> below).

You haven't convinced me of this so far.


>> So having something other than the ITRs doing the probing and
>> making the decisions does involve some extra complexity - a
>> real-time mapping system.  I believe this is a small price to
>> pay for the greater flexibility, more robust probing (all the
>> way to the destination network, not just to the ETRs), greater
>> simplicity in ITRs and ETRs, reduction in probing traffic etc.
>> Also, it enables real-time control of ETR address for incoming
>> TE.
>
> This discussion does raise an interesting architectural point with
>  respect to all map-and-encap solutions, which depend on
> reachability probing between ITR's and ETR's.  Specifically, do
> these reachability probes faithfully represent end-user
> (host-machine originated and terminated) flows so they are
> travelling along the same path as host-to-host data flows?  I
> would argue that they do not, (without substantially increasing
> the probing traffic load/bandwidth to "search" through all
> possible paths used by end-user traffic).

OK - this is much the same concern as I raised above about LISP etc.
ITRs being able to reliably probe reachability via the ECMP and LAG
systems you mentioned.


> OTOH, solutions that either: a) do proactive probing originating
> from hosts at something at or just below the TCP/UDP layer; or,
> better yet, b) piggyback ***reachability*** detection along with
> active TCP/UDP traffic flow (cf: TCP ACK's) between hosts ...
> would faithfully represent that a given path really is working.

I think that reachability probing at the host or ITR level can't
depend on traffic packets.  Firstly, there are PMTUD and efficiency
problems bloating some or all traffic packets with whatever is
required to elicit a response indicating reachability.  Secondly, if
an ITR is currently sending packets to ETR-A, since this is currently
preferred, it also arguably needs to be probing reachability to
(really through) ETR-B, ETR-C or however many other ETRs the network
could be reached by so it can make a quick change-over to one of
these, in the event that ETR-A fails.  The probing of those other
ITRs - ITR-B and ITR-C etc. - can't involve traffic packets because
all traffic is currently being tunneled via ITR-A.


> FWIW, I don't think there's a straightforward solution for
> map-and-encap solutions to the aforementioned probing over
> LAG/ECMP paths problem.  If there is, I'm all ears.

I agree, these techniques do pose problems - for any reachability
probing system.

I am not convinced yet that Ivip's approach would fare significantly
worse than LISP's.

LISP must use the ITRs to do the probing.  Ivip can't use the ITRs
for this (because it doesn't scale and to keep ITRs simple) but you
can organise probing from special probing servers all around the
world if you like, and do anything you like with the results when
deciding how to change the mapping.


> OTOH, if
> there's not a solution, I do not think we should gloss over it
> and, instead, I would strongly recommend we should point this out
> out very clearly within an "Operational Considerations" section of
> any/all map-and-encaps protocol specs or an
> overall/all-encompassing companion "Operational Considerations"
> document noting this and other 'challenges' that map-and-encaps
> can't feasibly address.  Said document(s) may prove helpful in
> evaluating the final set of candidate solutions that the RRG will
> offer its recommendation on.

I agree entirely.

Is your draft:

  http://tools.ietf.org/html/draft-amante-oam-ng-requirements-01

the best place to understand ECMP, LAG and the like?  If not, can you
point to better references?

  - Robin


Ivip's forwarding modes, with modified IP headers and likewise
modified DFZ and other routers, are described in:

  ETR Address Forwarding (EAF) - for IPv4
  http://tools.ietf.org/html/draft-whittle-ivip4-etr-addr-forw

  Prefix Label Forwarding (PLF) - for IPv6
  http://www.firstpr.com.au/ip/ivip/ivip6/


_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Thu Jan 22 05:34:04 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 799CD3A6977; Thu, 22 Jan 2009 05:34:04 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A5BE63A6977 for <rrg@core3.amsl.com>; Thu, 22 Jan 2009 05:34:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.59
X-Spam-Level: 
X-Spam-Status: No, score=-1.59 tagged_above=-999 required=5 tests=[AWL=0.305,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d0d-qxRzh-8n for <rrg@core3.amsl.com>; Thu, 22 Jan 2009 05:34:01 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123]) by core3.amsl.com (Postfix) with ESMTP id B7F373A6911 for <rrg@irtf.org>; Thu, 22 Jan 2009 05:34:01 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6]) by gair.firstpr.com.au (Postfix) with ESMTP id D87DD175737; Fri, 23 Jan 2009 00:33:44 +1100 (EST)
Message-ID: <49787638.90307@firstpr.com.au>
Date: Fri, 23 Jan 2009 00:35:52 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: RRG <rrg@irtf.org>
References: <497872B2.2020609@firstpr.com.au>
In-Reply-To: <497872B2.2020609@firstpr.com.au>
Subject: Re: [rrg] Ivip's separate reachability testing system, ECMP, LAG etc.
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org One further point:

Let's say Ivip is implemented and there are flaky losses of
connectivity with ECMP, LAG etc. - including especially new or
altered arrangements with different technical characteristics.

An Ivip-style reachability probing system (meaning it is completely
outside the Ivip system itself) could be updated to handle all these
potential problems.  For instance, from any one probing server to any
one ETR, the probing server could emit probe packets to the ETR which
are constructed to be hashed differently and so be sent via separate
paths.  With full knowledge of the potential multipath techniques
deployed between itself and any ETR, the probing server could
systematically try to have its probes go along every possible path.
Then it would be able to see the outages specifically, and so form an
estimate of general packet loss via the overall path, due to one or
more physical paths dropping packets.

Such sophistication and updating of probing protocols to meet the
challenges of the day would be out of the question in any ITR-based
system (LISP etc.) or any host-based system, because it is completely
impractical to upgrade all such ITRs or hosts to perform ever-more
complex probing.

 - Robin

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Thu Jan 22 10:40:50 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A258028C102; Thu, 22 Jan 2009 10:40:50 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0B75C28C102 for <rrg@core3.amsl.com>; Thu, 22 Jan 2009 10:40:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yaEaePJM51Gp for <rrg@core3.amsl.com>; Thu, 22 Jan 2009 10:40:47 -0800 (PST)
Received: from fridge.docomolabs-usa.com (fridge.docomolabs-usa.com [216.98.102.228]) by core3.amsl.com (Postfix) with ESMTP id C2C6A28C0FC for <rrg@irtf.org>; Thu, 22 Jan 2009 10:40:47 -0800 (PST)
Received: from dcl-ex.dcml.docomolabs-usa.com (viruswall.docomolabs-usa.com [172.21.96.230]) by fridge.docomolabs-usa.com (Postfix) with ESMTP id 110331B84C for <rrg@irtf.org>; Thu, 22 Jan 2009 10:40:31 -0800 (PST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 22 Jan 2009 10:40:30 -0800
Message-ID: <2FD61F37AFF16D4DB46149330E4273C701D72EBD@dcl-ex.dcml.docomolabs-usa.com>
In-Reply-To: <49781331.8050802@cs.uni-goettingen.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: CFP: Virtualized Infrastructure Systems and Architectures, VISA'09, March 6th 2009.
Thread-Index: Acl8Wrbbk/79KZ8kThGlO50v4CAC7AAZZkZw
References: <49781331.8050802@cs.uni-goettingen.de>
From: "Cedric J A. Westphal" <cwestphal@docomolabs-usa.com>
To: <rrg@irtf.org>
Subject: [rrg] CFP: Virtualized Infrastructure Systems and Architectures, VISA'09, March 6th 2009.
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org Please accept our apologies if you receive multiple copies of this call
for papers. 

*************************************
VISA 2009:   The First ACM SIGCOMM Workshop on Virtualized
Infrastructure Systems and Architectures

in conjunction with ACM SIGCOMM 2009, August 17th 2009, Barcelona,
Spain.

http://conferences.sigcomm.org/sigcomm/2009/workshops/visa/ 

PAPER SUBMISSION DEADLINE: March 6th, 2009.

                          * FIRST CALL FOR PAPERS *

Infrastructure virtualization has emerged as an important architecture
and experimentation concept for the Internet infrastructure. The global
computing and communication infrastructure will encompass (as it does
today) a diverse and huge collection of networking, computing and
storage resources. Together they need to form a coherent infrastructure
and meet our society's requirements for the 21st century. Infrastructure
virtualization involves creation of a virtual slice of network,
computing and storage resources in support of a service, an application,
or an experiment from a physical substrate of diverse resources. This
allows users of a virtualized infrastructure slice to access resources
on a potentially global scale without incurring the cost of building
such an infrastructure. Thus infrastructure virtualization provides a
platform to allow innovation on a global scale and enables new business
models. 

As we envision and research Future Internet, there is increasing
recognition that Infrastructure Virtualization will play an important
role. However, there are many technical problems to solve: how to
discover and advertise the resources; how to create and manage an
infrastructure slice across diverse resources; how does virtualization
extend to the wireless edge; how to implement virtualization across
diverse resources and across layers of protocol stack; how to map an
application or service to run on an infrastructure slice; what
applications and capabilities are enabled by infrastructure
virtualization; what kind of cross-layer protocols are possible; how
does infrastructure virtualization impact the business models of network
operators; and others. 

                           * TOPICS OF INTEREST *

We solicit previously unpublished work on the following, non exhaustive,
list of topics:

*     Infrastructure virtualization architecture;
*     Resource allocation to virtual slices;  
*     Management tools for infrastructure virtualization;
*     Implementation and transition map for infrastructure
virtualization;
*     Isolation and slice independence in a virtualized infrastructure;
*     Integration of the wireless edge into a virtualized network;
*     Inter-operability and federation of virtualized infrastructures;
*     Cross-layer protocols for virtualized networks;
*     Applications and services enabled by virtualized infrastructure;
and 
*     Security issues with virtualized infrastructure. 

                            * IMPORTANT DEADLINES *

Paper submission deadline:          Friday March 6, 2009
Acceptance notification:            Friday April 10, 2009
Camera ready final submission:      Monday May 4, 2009
Workshop:                           Monday August 17, 2009

                           * WORKSHOP ORGANIZATION *

Steering Committee:
- Tomonori Aoyama, Keio University and NICT
- Anja Feldmann, TU Berlin and T Labs
- Nick McKeown, Stanford University
- Guru Parulkar, Stanford University
- Larry Peterson, Princeton University
- Cedric Westphal, DoCoMo Labs USA

Program Chairs:
- Guru Parulkar, Stanford University
- Cedric Westphal, DoCoMo Labs USA

Program Committee Members:
- Hasan Alkhatib, Microsoft
- Tomonori Aoyama, Keio University and NICT
- Jack Brassil, HP Labs
- Stephan Baucke, Ericsson
- Simon Crosby, Citrix Systems
- Christophe Diot, Thomson Labs
- Lars Eggert, Nokia Research Center
- Serge Fdida, UPMC - Paris 6
- Nick Feamster, Georgia Tech
- Anja Feldmann, TU Berlin and T Labs
- Silvano Gai, Cisco Systems
- Albert Greenberg, Microsoft
- James Kempf, Ericsson
- Dae Young Kim, Chungnam National University
- Ulas Kozat, Docomo Labs USA
- Laurent Mathy, Lancaster University
- Nick McKeown, Stanford University
- Sue Moon, KAIST
- Akihiro Nakao, The University of Tokyo
- K.K. Ramakrishnan, AT&T Labs
- Dipankar Raychaudhuri, Rutgers University
- Jennifer Rexford, Princeton University
- Robert Ricci, University of Utah
- Martin Stiemerling, NEC Labs Europe
- Amin Vahdat, UCSD

                  * INSTRUCTIONS FOR AUTHORS *

Authors should submit pdf papers exclusively, to the EasyChair
conference management system:
http://www.easychair.org/conferences/?conf=visa09. 

Please follow the format of ACM Sigcomm 2009 submissions, except
anonymity is not required and the page limit is eight pages. This
workshop strongly encourages the submission of exploratory results that
point to new directions and challenges in the design and management of a
virtualized infrastructure.

Please contact visa09@easychair.org for any inquiry regarding the
workshop.

 

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Thu Jan 22 11:19:56 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8FE6428C279; Thu, 22 Jan 2009 11:19:56 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2B69B3A67D7 for <rrg@core3.amsl.com>; Thu, 22 Jan 2009 11:19:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.529
X-Spam-Level: 
X-Spam-Status: No, score=-6.529 tagged_above=-999 required=5 tests=[AWL=0.070,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MI2yt4NrsfBk for <rrg@core3.amsl.com>; Thu, 22 Jan 2009 11:19:49 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 7D92328C279 for <rrg@irtf.org>; Thu, 22 Jan 2009 11:19:49 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,307,1231113600"; d="scan'208";a="34568527"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 22 Jan 2009 19:19:29 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n0MJJT1g005846;  Thu, 22 Jan 2009 14:19:29 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n0MJJTYv010600; Thu, 22 Jan 2009 19:19:29 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Thu, 22 Jan 2009 14:19:29 -0500
Received: from cisco.com ([64.102.8.172]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 22 Jan 2009 14:19:28 -0500
Date: Thu, 22 Jan 2009 14:19:19 -0500
From: Scott Brim <swb@employees.org>
To: rrg@irtf.org
Message-ID: <20090122191919.GI3162@cisco.com>
Mail-Followup-To: Scott Brim <swb@employees.org>, rrg@irtf.org, paul@jakma.org
References: <B25790E2-8D3C-4A55-848C-F461982DC3F6@nomadiclab.com> <20090119213701.GA34129@cisco.com> <4975143E.9020404@gmail.com> <49752F9C.4050006@joelhalpern.com> <F2DA6B6C-6E73-4FA4-A2DD-2966FA400211@nomadiclab.com> <alpine.LFD.2.00.0901201604530.31066@localhost.localdomain> <C29F67D7-AD89-43CD-9A3E-76672D216667@virtualized.org> <alpine.LFD.2.00.0901201754180.31066@localhost.localdomain> <59075E8E-99D2-4CA0-90F3-881DE80303E8@virtualized.org> <alpine.LFD.2.00.0901221312320.8689@localhost.localdomain>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <alpine.LFD.2.00.0901221312320.8689@localhost.localdomain>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-OriginalArrivalTime: 22 Jan 2009 19:19:28.0975 (UTC) FILETIME=[58AB25F0:01C97CC6]
Authentication-Results: rtp-dkim-1; header.From=swb@employees.org; dkim=neutral
Subject: Re: [rrg] Why a host-based solution does not necessarily add	signalling load
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org Excerpts from Paul Jakma on Thu, Jan 22, 2009 01:12:40PM +0000:
> On Wed, 21 Jan 2009, David Conrad wrote:
>
>> Paul,
>>
>>> I assumed there was an implied ", to a significant enough extent for 
>>> it to matter" at the end of the sentence I quoted.
>>
>> What meets your requirement of enough "to matter"?  Depending on  
>> deployment scenario, a tunnel-router-based solution could cover  
>> thousands of hosts or more.  Is that enough to matter?
>
> It's going to be subjective to a point, but determining "to matter"  
> would involve comparing the control-overhead to the actual data-bearing 
> traffic, rather than focusing solely on the difference in control traffic 
> between end-host and intermediary based solutions.
>
> Having a tunnel-router do the liveliness tests for 1000 hosts might save 
> 999 instances of control traffic, but if the 999 instances of control 
> traffic comprise 1-2% of the data traffic - then should we care? (Is 
> there a data-communications version of Amdahl's Law I can quote here?).
>
> By my back-of-the-envelope calculations, a Shim6/REAP solution has  
> Order(1.2%) overhead relative to data-traffic (on a low amount of  
> traffic, 24kB - e.g. fetching the google front-page) for the normal  
> case. Failure cases presumably might take slightly more - but failure is 
> not the common case. Solid quantitative studies would be really useful.

Could you show us your BOTEC?  I've been meaning to go gather some
real numbers.

Scott
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Thu Jan 22 14:17:52 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2CF053A6828; Thu, 22 Jan 2009 14:17:52 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1497E3A6852 for <rrg@core3.amsl.com>; Thu, 22 Jan 2009 14:17:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.531
X-Spam-Level: 
X-Spam-Status: No, score=-6.531 tagged_above=-999 required=5 tests=[AWL=0.068,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cOPoZSmErHaY for <rrg@core3.amsl.com>; Thu, 22 Jan 2009 14:17:50 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 05D583A67F5 for <rrg@irtf.org>; Thu, 22 Jan 2009 14:17:49 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,308,1231113600"; d="scan'208";a="34629716"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 22 Jan 2009 22:17:32 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n0MMHX6J010788 for <rrg@irtf.org>; Thu, 22 Jan 2009 17:17:33 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n0MMHWW8015566 for <rrg@irtf.org>; Thu, 22 Jan 2009 22:17:32 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Thu, 22 Jan 2009 17:17:32 -0500
Received: from cisco.com ([64.102.8.172]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 22 Jan 2009 17:17:32 -0500
Date: Thu, 22 Jan 2009 17:17:25 -0500
From: Scott Brim <swb@employees.org>
To: "'RRG'" <rrg@irtf.org>
Message-ID: <20090122221725.GD388@cisco.com>
Mail-Followup-To: Scott Brim <swb@employees.org>, 'RRG' <rrg@irtf.org>
References: <496ABF62.60600@gmail.com> <000d01c9746d$2ad1f570$670c6f0a@china.huawei.com> <20090121192429.GC71937@cisco.com> <4977844B.6020702@gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <4977844B.6020702@gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-OriginalArrivalTime: 22 Jan 2009 22:17:32.0656 (UTC) FILETIME=[38A37F00:01C97CDF]
Authentication-Results: rtp-dkim-1; header.From=swb@employees.org; dkim=neutral
Subject: Re: [rrg] Scope Re:  Rejecting all but Strategy A
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org Excerpts from Brian E Carpenter on Thu, Jan 22, 2009 09:23:39AM +1300:
> On 2009-01-22 08:24, Scott Brim wrote:
> > Excerpts from Xu Xiaohu on Mon, Jan 12, 2009 12:20:57PM +0800:
> >>>> What HIP gives you is an identifier that may be used for many
> >>>> things.  An HI can be, but does not have to be, part of the
> >>>> process of initially finding a locator for an endpoint. For
> >>>> example, I can go straight from domain name to locator (which
> >>>> actually might be an agent / proxy / rendezvous point), and
> >>>> then validate identities via some other means.
> >>> Assuming I deem the DNS trustworthy, it seems much more natural
> >>> to treat the DNS as the source of an HI, and then for the
> >>> locator to be looked up as a function of the HI. I'm not saying
> >>> your model doesn't work, but surely the HI is fundamental and
> >>> has universal validity, and the locator (any of the locators) is
> >>> transient and has non-universal scope? So starting with a
> >>> locator lookup seems funny.
> >> I prefer Brain's opinion since there is no need for each host
> >> owns a FQDN name. Once you tell me your host ID, I can resolve
> >> your locator from a seperate ID/locator mapping system and then
> >> communicate with you. 
> > 
> > This is an interesting point.  Thank you.
> > 
> 
> It occurs to me that this would be particularly relevant to massive
> server virtualization (where a pool of physical servers synthesizes
> virtual servers as workload arrives). The virtual servers would each
> need an HI to locator map entry but would not particularly need an
> FQDN.
> 
>    Brian

Brian (aka Brain): While I agree with the original point, but on this
point: all you need here is a level of indirection when mapping from
name to interface.  "Name" can be anything -- I don't see the
difference if you start from a HI or a FQDN and take one step from it.  
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Thu Jan 22 14:26:22 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DEA7D3A68AF; Thu, 22 Jan 2009 14:26:22 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E84763A6856; Thu, 22 Jan 2009 14:26:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.495
X-Spam-Level: 
X-Spam-Status: No, score=-2.495 tagged_above=-999 required=5 tests=[AWL=0.104,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AA2xeSG-e4xx; Thu, 22 Jan 2009 14:26:14 -0800 (PST)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9]) by core3.amsl.com (Postfix) with ESMTP id 8B5D93A67F5; Thu, 22 Jan 2009 14:26:14 -0800 (PST)
Received: from m106.maoz.com (localhost [127.0.0.1]) by m106.maoz.com (8.14.3/8.14.3/Debian-4) with ESMTP id n0MMPwLw022785;  Thu, 22 Jan 2009 14:25:58 -0800
Received: (from dmm@localhost) by m106.maoz.com (8.14.3/8.14.3/Submit) id n0MMPw45022784; Thu, 22 Jan 2009 14:25:58 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Thu, 22 Jan 2009 14:25:57 -0800
From: David Meyer <dmm@1-4-5.net>
To: rrg@irtf.org, lisp@ietf.org
Message-ID: <20090122222557.GA22719@1-4-5.net>
MIME-Version: 1.0
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-gpg-fingerprint: 2409 8B50 B389 A307 BA5C 2A16 3918 03D6 A099 D8A7
X-philosophy: "I just had to let it go. John Lennon"
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: [rrg] draft-meyer-loc-id-implications-01.txt posted
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1497612874=="
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org --===============1497612874==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="W/nzBZO5zC0uMSeA"
Content-Disposition: inline


--W/nzBZO5zC0uMSeA
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

	See http://www.1-4-5.net/~dmm/draft-meyer-loc-id-implications-01.txt
	until the internet-drafts people get around to it.

	Dave

=09


--W/nzBZO5zC0uMSeA
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkl48nUACgkQORgD1qCZ2KcIKgCdHIfDEqN21arc8Hpo/F4DRoSs
Wa8AmwcglTy6wvjvwdW9upfQa9lq5Ekd
=zWq4
-----END PGP SIGNATURE-----

--W/nzBZO5zC0uMSeA--

--===============1497612874==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

--===============1497612874==--

From rrg-bounces@irtf.org  Thu Jan 22 15:41:14 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 52B2A3A6944; Thu, 22 Jan 2009 15:41:14 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 69BAD3A6944 for <rrg@core3.amsl.com>; Thu, 22 Jan 2009 15:41:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.172
X-Spam-Level: 
X-Spam-Status: No, score=-6.172 tagged_above=-999 required=5 tests=[AWL=-0.173, BAYES_00=-2.599, J_CHICKENPOX_43=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1CZwIW7TUQX6 for <rrg@core3.amsl.com>; Thu, 22 Jan 2009 15:41:12 -0800 (PST)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by core3.amsl.com (Postfix) with ESMTP id 677E83A67AF for <rrg@irtf.org>; Thu, 22 Jan 2009 15:41:10 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP ID DSNKSXkEBRrC32P7j9uQ+mZGg5r+q7SoCV21@postini.com; Thu, 22 Jan 2009 15:40:55 PST
Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server id 8.1.336.0; Thu, 22 Jan 2009 15:39:42 -0800
Received: from p-emlb02-sac.jnpr.net ([66.129.254.47]) by p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Thu, 22 Jan 2009 15:39:42 -0800
Received: from emailsmtp56.jnpr.net ([172.24.60.77]) by p-emlb02-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Thu, 22 Jan 2009 15:39:42 -0800
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Thu, 22 Jan 2009 15:39:41 -0800
Received: from juniper.net (sapphire.juniper.net [172.17.28.108])	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id n0MNddM88868; Thu, 22 Jan 2009 15:39:39 -0800 (PST)	(envelope-from yakov@juniper.net)
Message-ID: <200901222339.n0MNddM88868@magenta.juniper.net>
To: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <49765FFB.1010709@piuha.net> 
References: <20090120190744.GA9467@1-4-5.net> <49765FFB.1010709@piuha.net>
X-MH-In-Reply-To: Jari Arkko <jari.arkko@piuha.net> message dated "Wed, 21 Jan 2009 01:36:27 +0200."
MIME-Version: 1.0
Content-ID: <22055.1232667579.1@juniper.net>
Date: Thu, 22 Jan 2009 15:39:39 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-OriginalArrivalTime: 22 Jan 2009 23:39:41.0966 (UTC) FILETIME=[B2BC82E0:01C97CEA]
Cc: rrg <rrg@irtf.org>, int-area@ietf.org, routing-discussion@ietf.org
Subject: Re: [rrg] [Int-area] Please respond: Questions from the IESG as to whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org Jari,

> I wanted to provide some background on this question.
> 
> As you recall, a BOF was held on EXPLISP in Dublin. In Minneapolis we 
> had a number of WGs and the RRG talk about LISP. Implementation and 
> small scale deployment is going on. The RRG is still continuing its 
> work, and they are looking at a number of different solutions, including 
> map-and-encap, translation, host changes, and combinations thereof. I do 
> not want to preempt the RRG's efforts and at this time we are NOT 
> considering any IETF standards in this area. We are, however, 
> potentially interested in working groups targeting experimental 
> specifications so that we can get more experience about the various 
> technical solutions, different people can build systems that work 
> together, etc. Some of you may be familiar with the HIP effort; they 
> also had a working group that produced experimental RFCs to complement 
> the more research oriented work in the IRTF HIP group.
> 
> My interpretation of the outcome of the first BOF was that the topic was 
> very interesting for the people in the room but that at the time they 
> felt it was more in research than IETF scope. There were also technical 
> debates. That being said, we did not spend enough time on the WG 
> formation question. So I did not view the results as final. 
> Nevertheless, several attempts were made in the autumn to create some 
> form of a subgroup in RRG to do this work. However, the proponents were 
> only interested in a working group.
> 
> So what is happening now is what we did with many other BOF efforts as 
> well. We got feedback in the BOF, there's been further discussion, and 
> work on various fronts has progressed. Its time to complete the 
> discussion about the fate of this effort. We need to see if additional 
> information or further changes can result in a WG proposal that is 
> acceptable to the community or not. If we can reach a decision on the 
> list, fine, if not I will reserve a second BOF slot for the discussion. 
> I am mindful of the fact that the list discussion may not reach quite 
> the same crowd as a f2f meeting, so unless we get a fairly strong signal 
> in the list we probably need to meet as well.
> 
> But back to the proposal. In particular, I would like to know how people 
> feel about this work being ready for an (Experimental) IETF WG, what the 
> scope should be, whether the charter is reasonable. And if not, what 
> would make it so.

The question to ask is whether LISP is an appropriate solution to
the problems discussed at the IAB's October, 2006 Routing and
Addressing Workshop.

In answering this question we need to keep in mind that such
techniques as (a) caching routing and forwarding information, (b)
use of separate mapping system for Loc/ID mapping, (c) relying on
probing for determining path feasibility are essential/fundamental
to LISP. In other words, these techniques form the foundation of
LISP. Concerns with scaling and operational properties of these
techniques have been raised many times before (both at the previous
BOF, as well as on the RRG mailing list). Yet the LISP proponents
still did not adequately address these concerns.

Unless these concerns are adequately addressed, claiming that LISP
is an appropriate solution to the problems discussed at the IAB's
October 2006 Routing and Addressing Workshop is nothing more than
a proof by an emphatic assertion.

Addressing these concerns does *not* require LISP protocol specs.
Addressing these concerns does *not* require experimentation with
LISP protocols either. Addressing these concerns does *not* require
interoperable LISP implementations. Therefore, forming a WG to "work
on the design on the LISP base protocol , the LISP+ALT mapping
system, LISP Interworking  and LISP multicast", and to "encourage
and support interoperable LISP implementations as well as defining
requirements for alternate mapping systems" (as was proposed in
Dave's e-mail) is *not* going to address these concerns.

Unless the concerns I mentioned above are adequately addressed,
LISP can not be accepted as a feasible/practical approach towards
routing scalability. Therefore, unless and until these concerns are
adequately addressed, it is totally premature to form LISP WG.

Yakov.
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Thu Jan 22 15:57:34 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A76813A68E8; Thu, 22 Jan 2009 15:57:34 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E928A3A68E8 for <rrg@core3.amsl.com>; Thu, 22 Jan 2009 15:57:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.503
X-Spam-Level: 
X-Spam-Status: No, score=-6.503 tagged_above=-999 required=5 tests=[AWL=0.096,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SdiTy9gzo4IV for <rrg@core3.amsl.com>; Thu, 22 Jan 2009 15:57:33 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 3B29E3A67AF for <rrg@irtf.org>; Thu, 22 Jan 2009 15:57:33 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,309,1231113600"; d="scan'208";a="130546782"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-3.cisco.com with ESMTP; 22 Jan 2009 23:57:16 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id n0MNvGHE012030;  Thu, 22 Jan 2009 15:57:16 -0800
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n0MNvGm8014672; Thu, 22 Jan 2009 23:57:16 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Thu, 22 Jan 2009 15:57:16 -0800
Received: from [192.168.1.2] ([10.21.126.152]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Thu, 22 Jan 2009 15:57:16 -0800
Message-Id: <37764799-9CC3-451C-9CA2-0453BB42FE82@cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: Yakov Rekhter <yakov@juniper.net>
In-Reply-To: <200901222339.n0MNddM88868@magenta.juniper.net>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Thu, 22 Jan 2009 15:57:15 -0800
References: <20090120190744.GA9467@1-4-5.net> <49765FFB.1010709@piuha.net> <200901222339.n0MNddM88868@magenta.juniper.net>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 22 Jan 2009 23:57:16.0173 (UTC) FILETIME=[2717BBD0:01C97CED]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=550; t=1232668636; x=1233532636; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dino@cisco.com; z=From:=20Dino=20Farinacci=20<dino@cisco.com> |Subject:=20Re=3A=20[rrg]=20[Int-area]=20Please=20respond=3 A=20Questions=20from=20the=20IESG=20as=20to=20whether=20a=20 WG=20forming=20BOF=20is=20necessary=20for=20LISP |Sender:=20; bh=4HTNSiYxVRd3B1XTS5rAYLnEsgFLFmyOrSUjg+JOJiU=; b=cw06z6zCOzAyh6puWy3RRywVjRN+9gI8kN8f0v2AqDXaCVH1XSfzlkioVE AzXZbrKYk9Hi+MIKHIYDzm2ESMZMn+sBhwFXU9HWKBuETmy8uV4ZPEhe78i1 KPHU5JDsxc;
Authentication-Results: sj-dkim-4; header.From=dino@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; ); 
Cc: int-area@ietf.org, rrg <rrg@irtf.org>, routing-discussion@ietf.org
Subject: Re: [rrg] [Int-area] Please respond: Questions from the IESG as to whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org > In answering this question we need to keep in mind that such
> techniques as (a) caching routing and forwarding information, (b)
> use of separate mapping system for Loc/ID mapping, (c) relying on
> probing for determining path feasibility are essential/fundamental
> to LISP. In other words, these techniques form the foundation of
> LISP. Concerns with scaling and operational properties of these

Correction. LISP does not use probing. It isn't in the current spec  
and has never been documented. Just want to state the facts.

Dino


_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Thu Jan 22 16:05:17 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 589E03A69A8; Thu, 22 Jan 2009 16:05:17 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9B9513A677C; Thu, 22 Jan 2009 16:05:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.498
X-Spam-Level: 
X-Spam-Status: No, score=-2.498 tagged_above=-999 required=5 tests=[AWL=0.101,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rWNl-jHycgCV; Thu, 22 Jan 2009 16:05:15 -0800 (PST)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9]) by core3.amsl.com (Postfix) with ESMTP id D721C3A69AC; Thu, 22 Jan 2009 16:05:14 -0800 (PST)
Received: from m106.maoz.com (localhost [127.0.0.1]) by m106.maoz.com (8.14.3/8.14.3/Debian-4) with ESMTP id n0N04qo4026044;  Thu, 22 Jan 2009 16:04:52 -0800
Received: (from dmm@localhost) by m106.maoz.com (8.14.3/8.14.3/Submit) id n0N04qos026043; Thu, 22 Jan 2009 16:04:52 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Thu, 22 Jan 2009 16:04:52 -0800
From: David Meyer <dmm@1-4-5.net>
To: Yakov Rekhter <yakov@juniper.net>
Message-ID: <20090123000452.GA25882@1-4-5.net>
References: <20090120190744.GA9467@1-4-5.net> <49765FFB.1010709@piuha.net> <200901222339.n0MNddM88868@magenta.juniper.net>
MIME-Version: 1.0
In-Reply-To: <200901222339.n0MNddM88868@magenta.juniper.net>
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-gpg-fingerprint: 2409 8B50 B389 A307 BA5C 2A16 3918 03D6 A099 D8A7
X-philosophy: "I just had to let it go. John Lennon"
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: int-area@ietf.org, rrg <rrg@irtf.org>, routing-discussion@ietf.org
Subject: Re: [rrg] [Int-area] Please respond: Questions from the IESG as to	whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1182894251=="
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org --===============1182894251==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="NzB8fVQJ5HfG6fxh"
Content-Disposition: inline


--NzB8fVQJ5HfG6fxh
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

	Yakov,

> In answering this question we need to keep in mind that such
> techniques as (a) caching routing and forwarding information, (b)
> use of separate mapping system for Loc/ID mapping, (c) relying on
> probing for determining path feasibility are essential/fundamental
> to LISP.

	(c) is clearly not fundemental to LISP.=20

	What is fundemental (IMO) to any Loc/ID split
	architecture is what have what we have termed the Locator
	Path Liveness problem. How that problem is solved is a
	matter for each architecture to consider.=20

	In particular, probing is a solution to the Locator Path
	Liveness problem, but as we know from shim6 (etc), the
	complexity of that isn't pretty. But then either is the
	O(n!) complexity of BGP path hunting. In any event, the
	space of potential solutions for map-and-encap schemes
	such as LISP (or eFIT, Ivip, etc) haven't been throughly
	explored. This is part of the reason why we think LISP
	should be EXPERIMENTAL.

> In other words, these techniques form the foundation of
> LISP.

	With respect to LISP and probing, that statement is
	incorrect.=20

	Dave

--NzB8fVQJ5HfG6fxh
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkl5CaQACgkQORgD1qCZ2KdMrgCfflweK8IGx0diEaIEFCy8uh1e
LEgAniH+p447+fwMkxDEUlZeJCjBS7Jq
=AGKw
-----END PGP SIGNATURE-----

--NzB8fVQJ5HfG6fxh--

--===============1182894251==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

--===============1182894251==--

From rrg-bounces@irtf.org  Thu Jan 22 16:39:41 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B7C4F3A69A8; Thu, 22 Jan 2009 16:39:41 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 649E53A69A8; Thu, 22 Jan 2009 16:39:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.435
X-Spam-Level: 
X-Spam-Status: No, score=-6.435 tagged_above=-999 required=5 tests=[AWL=0.164,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jHPiB7nMRH1J; Thu, 22 Jan 2009 16:39:38 -0800 (PST)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id A97FF3A677C; Thu, 22 Jan 2009 16:39:38 -0800 (PST)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n0N0cfAQ005018 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 22 Jan 2009 16:38:47 -0800 (PST)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n0N0cfro002754; Thu, 22 Jan 2009 18:38:41 -0600 (CST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n0N0cfWU002742; Thu, 22 Jan 2009 18:38:41 -0600 (CST)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 22 Jan 2009 16:38:36 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 22 Jan 2009 16:38:35 -0800
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A105764A90@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <20090123000452.GA25882@1-4-5.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] [Int-area] Please respond: Questions from the IESG asto	whether a WG forming BOF is necessary for LISP
Thread-Index: Acl87j4IHCn3I6PpQ42dLjnFEfs4AQAAhb6Q
References: <20090120190744.GA9467@1-4-5.net> <49765FFB.1010709@piuha.net><200901222339.n0MNddM88868@magenta.juniper.net> <20090123000452.GA25882@1-4-5.net>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "David Meyer" <dmm@1-4-5.net>, "Yakov Rekhter" <yakov@juniper.net>
X-OriginalArrivalTime: 23 Jan 2009 00:38:36.0160 (UTC) FILETIME=[ED47B800:01C97CF2]
Cc: rrg <rrg@irtf.org>, int-area@ietf.org, routing-discussion@ietf.org
Subject: Re: [rrg] [Int-area] Please respond: Questions from the IESG asto	whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org Hi Dave, 

> -----Original Message-----
> From: David Meyer [mailto:dmm@1-4-5.net] 
> Sent: Thursday, January 22, 2009 4:05 PM
> To: Yakov Rekhter
> Cc: int-area@ietf.org; rrg; routing-discussion@ietf.org
> Subject: Re: [rrg] [Int-area] Please respond: Questions from 
> the IESG asto whether a WG forming BOF is necessary for LISP
> 
> 	Yakov,
> 
> > In answering this question we need to keep in mind that such
> > techniques as (a) caching routing and forwarding information, (b)
> > use of separate mapping system for Loc/ID mapping, (c) relying on
> > probing for determining path feasibility are essential/fundamental
> > to LISP.
> 
> 	(c) is clearly not fundemental to LISP. 
> 
> 	What is fundemental (IMO) to any Loc/ID split
> 	architecture is what have what we have termed the Locator
> 	Path Liveness problem. How that problem is solved is a
> 	matter for each architecture to consider. 
> 
> 	In particular, probing is a solution to the Locator Path
> 	Liveness problem, but as we know from shim6 (etc), the
> 	complexity of that isn't pretty. But then either is the
> 	O(n!) complexity of BGP path hunting. In any event, the
> 	space of potential solutions for map-and-encap schemes
> 	such as LISP (or eFIT, Ivip, etc) haven't been throughly
> 	explored. This is part of the reason why we think LISP
> 	should be EXPERIMENTAL.

Not meaning to pick on you, but I don't understand why RANGER
hasn't made it onto the "short list" of proposals yet; maybe
you could answer that for me? AFAICT, RANGER is in the top-two
map/encaps proposals in terms of technical completeness (maybe
even the top-one) so can we have folks add it to their lists?

Thanks - Fred
fred.l.templin@boeing.com

> > In other words, these techniques form the foundation of
> > LISP.
> 
> 	With respect to LISP and probing, that statement is
> 	incorrect. 
> 
> 	Dave
> 
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Thu Jan 22 18:25:14 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9C73F28C149; Thu, 22 Jan 2009 18:25:14 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 16FE03A69D7; Thu, 22 Jan 2009 18:25:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level: 
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S8yQby9YZJ1e; Thu, 22 Jan 2009 18:25:02 -0800 (PST)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9]) by core3.amsl.com (Postfix) with ESMTP id 6EC533A6932; Thu, 22 Jan 2009 18:25:02 -0800 (PST)
Received: from m106.maoz.com (localhost [127.0.0.1]) by m106.maoz.com (8.14.3/8.14.3/Debian-4) with ESMTP id n0N2OUw5027449;  Thu, 22 Jan 2009 18:24:30 -0800
Received: (from dmm@localhost) by m106.maoz.com (8.14.3/8.14.3/Submit) id n0N2OUiH027448; Thu, 22 Jan 2009 18:24:30 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Thu, 22 Jan 2009 18:24:30 -0800
From: David Meyer <dmm@1-4-5.net>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Message-ID: <20090123022430.GA27375@1-4-5.net>
References: <20090120190744.GA9467@1-4-5.net> <20090123000452.GA25882@1-4-5.net> <39C363776A4E8C4A94691D2BD9D1C9A105764A90@XCH-NW-7V2.nw.nos.boeing.com>
MIME-Version: 1.0
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A105764A90@XCH-NW-7V2.nw.nos.boeing.com>
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-gpg-fingerprint: 2409 8B50 B389 A307 BA5C 2A16 3918 03D6 A099 D8A7
X-philosophy: "I just had to let it go. John Lennon"
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: rrg <rrg@irtf.org>, int-area@ietf.org, routing-discussion@ietf.org
Subject: Re: [rrg] [Int-area] Please respond: Questions from the IESG asto	whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1326660871=="
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org --===============1326660871==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="Nq2Wo0NMKNjxTN9z"
Content-Disposition: inline


--Nq2Wo0NMKNjxTN9z
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Jan 22, 2009 at 04:38:35PM -0800, Templin, Fred L wrote:
> Hi Dave,=20
>=20
> > -----Original Message-----
> > From: David Meyer [mailto:dmm@1-4-5.net]=20
> > Sent: Thursday, January 22, 2009 4:05 PM
> > To: Yakov Rekhter
> > Cc: int-area@ietf.org; rrg; routing-discussion@ietf.org
> > Subject: Re: [rrg] [Int-area] Please respond: Questions from=20
> > the IESG asto whether a WG forming BOF is necessary for LISP
> >=20
> > 	Yakov,
> >=20
> > > In answering this question we need to keep in mind that such
> > > techniques as (a) caching routing and forwarding information, (b)
> > > use of separate mapping system for Loc/ID mapping, (c) relying on
> > > probing for determining path feasibility are essential/fundamental
> > > to LISP.
> >=20
> > 	(c) is clearly not fundemental to LISP.=20
> >=20
> > 	What is fundemental (IMO) to any Loc/ID split
> > 	architecture is what have what we have termed the Locator
> > 	Path Liveness problem. How that problem is solved is a
> > 	matter for each architecture to consider.=20
> >=20
> > 	In particular, probing is a solution to the Locator Path
> > 	Liveness problem, but as we know from shim6 (etc), the
> > 	complexity of that isn't pretty. But then either is the
> > 	O(n!) complexity of BGP path hunting. In any event, the
> > 	space of potential solutions for map-and-encap schemes
> > 	such as LISP (or eFIT, Ivip, etc) haven't been throughly
> > 	explored. This is part of the reason why we think LISP
> > 	should be EXPERIMENTAL.
>=20
> Not meaning to pick on you, but I don't understand why RANGER
> hasn't made it onto the "short list" of proposals yet; maybe
> you could answer that for me? AFAICT, RANGER is in the top-two
> map/encaps proposals in terms of technical completeness (maybe
> even the top-one) so can we have folks add it to their lists?

	Fred,

	No "picking" interpreted. You're right, and its my
	omission (and to be honest, you've been gracious enough
	to mention this to me privately several times).=20

	I'll be sure to add RANGER the list going forward.

	Consider it done.

	Dave

--Nq2Wo0NMKNjxTN9z
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEUEARECAAYFAkl5Kl4ACgkQORgD1qCZ2KeORQCggeTEKg8KMVe4knVf5B53ByNZ
/R4AljpRB+nUP7zTJ+UeWpwWVd1l/KE=
=rszx
-----END PGP SIGNATURE-----

--Nq2Wo0NMKNjxTN9z--

--===============1326660871==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

--===============1326660871==--

From rrg-bounces@irtf.org  Thu Jan 22 18:34:45 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0FF813A69D8; Thu, 22 Jan 2009 18:34:45 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 934223A69E4 for <rrg@core3.amsl.com>; Thu, 22 Jan 2009 18:34:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.566
X-Spam-Level: 
X-Spam-Status: No, score=-2.566 tagged_above=-999 required=5 tests=[AWL=0.033,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0etnQO+9BNeH for <rrg@core3.amsl.com>; Thu, 22 Jan 2009 18:34:42 -0800 (PST)
Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.30]) by core3.amsl.com (Postfix) with ESMTP id 2EDAA3A682B for <rrg@irtf.org>; Thu, 22 Jan 2009 18:34:42 -0800 (PST)
Received: by yx-out-2324.google.com with SMTP id 8so1909508yxg.37 for <rrg@irtf.org>; Thu, 22 Jan 2009 18:34:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=/dGFsxRiSTKv2gAyky8K80nqKW9x3DNQ5njURACrTNk=; b=cKzh5CLUKGnOwPJNq6vlQGYdoG8vNdrHEAzxD19jEiYZmd/GmBr5+QYLgVZiTGlzUi 9bjLAegE/DgOgdZFErezkoqAw7XDTzvYMyDP5yIY6aWfQZVAYtlZovqtxpApkmofSXdN sKg451MpaDZlaZTeo8MBDtb2cnYMY2i/eVRRA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=MANWug88pq7S4zaK8avGdsnPnzxw/Nb6ifhmp1nSytzuu6jWe9Rt00Q1KzvkbgnOA0 HoyKd+4G8YSDL7SQ9FI9gyXMqomTONQcmK06jw+klc3GTuxU1GuGpKIxV37tbKbtettg cJyEvW2nuuVVG356ebe/qW4/TH/IKwbRusQ2s=
MIME-Version: 1.0
Received: by 10.100.171.10 with SMTP id t10mr699376ane.53.1232678064880; Thu,  22 Jan 2009 18:34:24 -0800 (PST)
In-Reply-To: <200901222339.n0MNddM88868@magenta.juniper.net>
References: <20090120190744.GA9467@1-4-5.net> <49765FFB.1010709@piuha.net> <200901222339.n0MNddM88868@magenta.juniper.net>
Date: Thu, 22 Jan 2009 21:34:24 -0500
X-Google-Sender-Auth: 319b5de036dfdf9a
Message-ID: <75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com>
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Yakov Rekhter <yakov@juniper.net>
Cc: int-area@ietf.org, rrg <rrg@irtf.org>, routing-discussion@ietf.org
Subject: Re: [rrg] [Int-area] Please respond: Questions from the IESG as to whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org Sorry for jumping into the fray at this juncture, I missed Jari's
original message :(

On Thu, Jan 22, 2009 at 6:39 PM, Yakov Rekhter <yakov@juniper.net> wrote:
> Jari,
>
>> I wanted to provide some background on this question.
>>
>> As you recall, a BOF was held on EXPLISP in Dublin. In Minneapolis we
>> had a number of WGs and the RRG talk about LISP. Implementation and
>> small scale deployment is going on. The RRG is still continuing its
>> work, and they are looking at a number of different solutions, including
>> map-and-encap, translation, host changes, and combinations thereof. I do
>> not want to preempt the RRG's efforts and at this time we are NOT
>> considering any IETF standards in this area. We are, however,
>> potentially interested in working groups targeting experimental
>> specifications so that we can get more experience about the various
>> technical solutions, different people can build systems that work
>> together, etc. Some of you may be familiar with the HIP effort; they
>> also had a working group that produced experimental RFCs to complement
>> the more research oriented work in the IRTF HIP group.
>>

I think having a focused group that can work out some of the large
scale deployment, operations and design issues with this bit of
technology would be helpful. We have spent the better part of 2 years
(we == the community) working in the RRG and in side groups attempting
to design and test a new routing architecture. Putting that work into
an official spot, allowing it to work through issues and determine if
the design/plan will bare fruit, I think is a good thing.

>> My interpretation of the outcome of the first BOF was that the topic was
>> very interesting for the people in the room but that at the time they
>> felt it was more in research than IETF scope. There were also technical
>> debates. That being said, we did not spend enough time on the WG

in every WG meeting that this subject came up in both Dublin and
Minneapolis there was a great deal of interest, discussion and debate.
This, it seems to me, signals that there is interest in seeing how
this technology may work out for the community as a whole. I believe
this shows a WG would be helpful in containing the work and scope so a
result and direction can be determined.

>> formation question. So I did not view the results as final.
>> Nevertheless, several attempts were made in the autumn to create some
>> form of a subgroup in RRG to do this work. However, the proponents were
>> only interested in a working group.
>>
>> So what is happening now is what we did with many other BOF efforts as
>> well. We got feedback in the BOF, there's been further discussion, and
>> work on various fronts has progressed. Its time to complete the
>> discussion about the fate of this effort. We need to see if additional
>> information or further changes can result in a WG proposal that is
>> acceptable to the community or not. If we can reach a decision on the
>> list, fine, if not I will reserve a second BOF slot for the discussion.
>> I am mindful of the fact that the list discussion may not reach quite
>> the same crowd as a f2f meeting, so unless we get a fairly strong signal
>> in the list we probably need to meet as well.
>>
>> But back to the proposal. In particular, I would like to know how people
>> feel about this work being ready for an (Experimental) IETF WG, what the
>> scope should be, whether the charter is reasonable. And if not, what
>> would make it so.

I'd like to see an experimental wg, I think at least the scope could cover:
o fleshing out/finalizing the proposed LISP protocol suite
o working through and documenting some of the use cases and operations of LISP
o characterization of true scalability impact at current traffic rates

I think that 'LISP' is a might narrow though, there are other
map/encap solutions which may work as well. I'd like to see how
something like map/encap works, and if it shows itself to be helpful.

>
> The question to ask is whether LISP is an appropriate solution to
> the problems discussed at the IAB's October, 2006 Routing and
> Addressing Workshop.

Yakov,
I'm not sure there have been any other credible solutions aside from
'map/encap', this seems promising, though certainly it hasn't been
proven out in the way that v4 routing as we know it today has been.

Certainly there are use cases where there will be issues, certainly
there are ways to deal with these use cases. Without some direct
experimentation, thought about the problems and focus, we won't be
able to address these things. (we == community)

> In answering this question we need to keep in mind that such
> techniques as (a) caching routing and forwarding information, (b)
> use of separate mapping system for Loc/ID mapping, (c) relying on
> probing for determining path feasibility are essential/fundamental
> to LISP. In other words, these techniques form the foundation of
> LISP. Concerns with scaling and operational properties of these
> techniques have been raised many times before (both at the previous
> BOF, as well as on the RRG mailing list). Yet the LISP proponents
> still did not adequately address these concerns.

I thought they had addressed some of them, both on-list and in-person
at a few of the meetings. Perhaps some details were lacking?

> Unless these concerns are adequately addressed, claiming that LISP
> is an appropriate solution to the problems discussed at the IAB's
> October 2006 Routing and Addressing Workshop is nothing more than
> a proof by an emphatic assertion.

I don't think anyone has said one thing or another is 'the solution',
I think so far 'a solution might be' has been used though. Without
some work, investigation and engineering I don't think we'll be much
further toward a solution in  another 2 years. I think it's important
to gain some experience with the options.

> Unless the concerns I mentioned above are adequately addressed,
> LISP can not be accepted as a feasible/practical approach towards
> routing scalability. Therefore, unless and until these concerns are
> adequately addressed, it is totally premature to form LISP WG.

we can't know if an approach is feasible/practical until we make an
honest attempt to work through both the engineering issues and the
operational issues... Did you have options we should also discuss?

-Chris
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Thu Jan 22 19:35:28 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AC6E33A694C; Thu, 22 Jan 2009 19:35:28 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4684C3A694C for <rrg@core3.amsl.com>; Thu, 22 Jan 2009 19:35:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.327
X-Spam-Level: 
X-Spam-Status: No, score=0.327 tagged_above=-999 required=5 tests=[AWL=-0.378,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  J_CHICKENPOX_35=0.6, J_CHICKENPOX_36=0.6, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EAs2gyIuXaLa for <rrg@core3.amsl.com>; Thu, 22 Jan 2009 19:35:27 -0800 (PST)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id F15A63A68FE for <rrg@irtf.org>; Thu, 22 Jan 2009 19:35:26 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KDW00BI3N1QQL@szxga03-in.huawei.com> for rrg@irtf.org; Fri, 23 Jan 2009 11:29:50 +0800 (CST)
Received: from x41208a ([10.111.12.103]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KDW00G48N1PED@szxga03-in.huawei.com> for rrg@irtf.org; Fri, 23 Jan 2009 11:29:50 +0800 (CST)
Date: Fri, 23 Jan 2009 11:29:49 +0800
From: Xu Xiaohu <xuxh@huawei.com>
In-reply-to: <75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com>
To: 'Christopher Morrow' <morrowc.lists@gmail.com>, 'Yakov Rekhter' <yakov@juniper.net>
Message-id: <001a01c97d0a$d9070270$670c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Thread-index: Acl9AyLc3RoX3zYnTwO3AITSPxUJ3wAA20Qw
Cc: 'rrg' <rrg@irtf.org>, int-area@ietf.org, routing-discussion@ietf.org
Subject: Re: [rrg] [Int-area] Please respond: Questions from the IESG as towhether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org  
> I think having a focused group that can work out some of the 
> large scale deployment, operations and design issues with 
> this bit of technology would be helpful. 

I agree.

> I think that 'LISP' is a might narrow though, there are other 
> map/encap solutions which may work as well. I'd like to see 
> how something like map/encap works, and if it shows itself to 
> be helpful.

Exactly. The to-be-formed WG should not only focus on LISP, but also focus
on other map&encap solutions. Just as Yakov etc. pointed out, there are
still some open issues in LISP need to be answered. If many different
map&encaps solutions can be explored further simultaneously under this WG
charter, we may find they are complementary and can be converged finally to
form a successful short-term solution.

Xiaohu

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Thu Jan 22 19:36:59 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 759673A6A1E; Thu, 22 Jan 2009 19:36:59 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EF4DF3A6A1E for <rrg@core3.amsl.com>; Thu, 22 Jan 2009 19:36:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.968
X-Spam-Level: 
X-Spam-Status: No, score=-1.968 tagged_above=-999 required=5 tests=[AWL=-0.569, BAYES_00=-2.599, J_CHICKENPOX_35=0.6, J_CHICKENPOX_36=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0zY8uIFZt05c for <rrg@core3.amsl.com>; Thu, 22 Jan 2009 19:36:52 -0800 (PST)
Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.30]) by core3.amsl.com (Postfix) with ESMTP id 91CE73A68FE for <rrg@irtf.org>; Thu, 22 Jan 2009 19:36:52 -0800 (PST)
Received: by yw-out-2324.google.com with SMTP id 3so1911511ywj.37 for <rrg@irtf.org>; Thu, 22 Jan 2009 19:36:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=yMfEwcyL+RGwe/MqpeV/3FNcl1qL6Yhh2JKGhh00ids=; b=ma3RwV3oUBU026XY5a239QiXZ6cF2J3X+CBi4yvQkGkGMvppyJI3z/Ygz139qyOqoM HykN26v+oytGhaZUoMsMabE5ewcgMolrxOTf2kG7+yXL1mcGw/e28ryLYCn/EFHnXn+I GHMifFTy21TaU2EYlz7JHY2xlFOIoUTijcCcU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=WtlTbT1Ft8DAzwP1GFp4G0ttn8RyzXfMo7kWJICRvnC8kACOjQWwV9bkqogez6VSW7 r6pNV9Co9DG0RPwWU01ptiSqQhf7Ru7cr2RTBoXPBbO0sjVDXlnlFYL6wZ+4j4iuWX2w A7qAp9RYN6uGj9GMNuh9jVHxgwRuYXh31DBGQ=
MIME-Version: 1.0
Received: by 10.100.128.20 with SMTP id a20mr933918and.148.1232681795597; Thu,  22 Jan 2009 19:36:35 -0800 (PST)
In-Reply-To: <001a01c97d0a$d9070270$670c6f0a@china.huawei.com>
References: <75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com> <001a01c97d0a$d9070270$670c6f0a@china.huawei.com>
Date: Thu, 22 Jan 2009 22:36:35 -0500
X-Google-Sender-Auth: 46d385f5f7f7cc59
Message-ID: <75cb24520901221936p5f714c14r98bdc84a674d4a92@mail.gmail.com>
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Xu Xiaohu <xuxh@huawei.com>
Cc: rrg <rrg@irtf.org>, int-area@ietf.org, routing-discussion@ietf.org
Subject: Re: [rrg] [Int-area] Please respond: Questions from the IESG as towhether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org On Thu, Jan 22, 2009 at 10:29 PM, Xu Xiaohu <xuxh@huawei.com> wrote:
>
>> I think having a focused group that can work out some of the
>> large scale deployment, operations and design issues with
>> this bit of technology would be helpful.
>
> I agree.
>
>> I think that 'LISP' is a might narrow though, there are other
>> map/encap solutions which may work as well. I'd like to see
>> how something like map/encap works, and if it shows itself to
>> be helpful.
>
> Exactly. The to-be-formed WG should not only focus on LISP, but also focus
> on other map&encap solutions. Just as Yakov etc. pointed out, there are
> still some open issues in LISP need to be answered. If many different
> map&encaps solutions can be explored further simultaneously under this WG
> charter, we may find they are complementary and can be converged finally to
> form a successful short-term solution.

they might also feedback into RRG as inputs useful to the discussion
William's been putting together...
-Chris
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Thu Jan 22 20:34:55 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6745D3A68F7; Thu, 22 Jan 2009 20:34:55 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DA6AD3A68F7 for <rrg@core3.amsl.com>; Thu, 22 Jan 2009 20:34:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.527
X-Spam-Level: 
X-Spam-Status: No, score=-6.527 tagged_above=-999 required=5 tests=[AWL=0.072,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ABfi5i-SHhgB for <rrg@core3.amsl.com>; Thu, 22 Jan 2009 20:34:52 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by core3.amsl.com (Postfix) with ESMTP id B4DD23A67F7 for <rrg@irtf.org>; Thu, 22 Jan 2009 20:34:52 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 44D976BE56B; Thu, 22 Jan 2009 23:34:25 -0500 (EST)
To: rrg@irtf.org
Message-Id: <20090123043435.44D976BE56B@mercury.lcs.mit.edu>
Date: Thu, 22 Jan 2009 23:34:25 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [rrg] [Int-area] Please respond: Questions from the IESG as to whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org     > From: Yakov Rekhter <yakov@juniper.net>

    > ... claiming that LISP is an appropriate solution to the problems
    > discussed at the IAB's October 2006 Routing and Addressing Workshop

Yakov, perhaps I'm confused, but I don't hear anyone claiming that LISP
should be 'anointed' as _the_ solution. In fact, it's explicitly being put
forward as an Experimental protocol.

What other path forward would you suggest for that work? Should LISP work not
be done in the IETF at all, but rather as a closed, private, outside effort?

        Noel
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Thu Jan 22 20:53:02 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BC3903A6A0D; Thu, 22 Jan 2009 20:53:02 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BE83C3A69BF for <rrg@core3.amsl.com>; Thu, 22 Jan 2009 20:53:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.222
X-Spam-Level: 
X-Spam-Status: No, score=-6.222 tagged_above=-999 required=5 tests=[AWL=-0.223, BAYES_00=-2.599, J_CHICKENPOX_35=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 20D41XeaIJSt for <rrg@core3.amsl.com>; Thu, 22 Jan 2009 20:53:01 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by core3.amsl.com (Postfix) with ESMTP id 99BAA3A67F7 for <rrg@irtf.org>; Thu, 22 Jan 2009 20:53:01 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id AF0976BE56F; Thu, 22 Jan 2009 23:52:44 -0500 (EST)
To: rrg@irtf.org
Message-Id: <20090123045244.AF0976BE56F@mercury.lcs.mit.edu>
Date: Thu, 22 Jan 2009 23:52:44 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: Re: [rrg] [Int-area] Please respond: Questions from the IESG as towhether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org     > From: Xu Xiaohu <xuxh@huawei.com>

    > The to-be-formed WG should not only focus on LISP, but also focus on
    > other map&encap solutions.

The problem is that if you diffuse the WG focus like this, it will slow
things down. The IETF practise in the past has been, when there are multiple
protocols which overlap in functionality, to do each one in a separate WG
precisely so each can focus on their own protocol.

        Noel
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Thu Jan 22 21:23:24 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A2C343A6A2F; Thu, 22 Jan 2009 21:23:24 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5E6613A6A2F for <rrg@core3.amsl.com>; Thu, 22 Jan 2009 21:23:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.442
X-Spam-Level: *
X-Spam-Status: No, score=1.442 tagged_above=-999 required=5 tests=[AWL=-1.452,  BAYES_00=-2.599, CN_BODY_35=0.339, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_35=0.6, MIME_CHARSET_FARAWAY=2.45, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F-dbigAMQ5wT for <rrg@core3.amsl.com>; Thu, 22 Jan 2009 21:23:22 -0800 (PST)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 897E03A689D for <rrg@irtf.org>; Thu, 22 Jan 2009 21:23:22 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KDW0048RSA7H5@szxga03-in.huawei.com> for rrg@irtf.org; Fri, 23 Jan 2009 13:22:55 +0800 (CST)
Received: from x41208a ([10.111.12.103]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KDW00CLMSA6BM@szxga03-in.huawei.com> for rrg@irtf.org; Fri, 23 Jan 2009 13:22:55 +0800 (CST)
Date: Fri, 23 Jan 2009 13:22:54 +0800
From: Xu Xiaohu <xuxh@huawei.com>
In-reply-to: <20090123045244.AF0976BE56F@mercury.lcs.mit.edu>
To: 'Noel Chiappa' <jnc@mercury.lcs.mit.edu>, rrg@irtf.org
Message-id: <001c01c97d1a$a5434240$670c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Thread-index: Acl9FnJ4hLRR35KVQOm4JEiMwbrnwQAAJR5Q
Subject: Re: [rrg] [Int-area] Please respond: Questions from the IESG astowhether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org CgogCgo+IC0tLS0t08q8/tStvP4tLS0tLQo+ILeivP7IyzogcnJnLWJvdW5jZXNAaXJ0Zi5vcmcg
W21haWx0bzpycmctYm91bmNlc0BpcnRmLm9yZ10gtPqx7SAKPiBOb2VsIENoaWFwcGEKPiC3osvN
yrG85DogMjAwOcTqMdTCMjPI1SAxMjo1Mwo+IMrVvP7IyzogcnJnQGlydGYub3JnCj4g1vfM4jog
UmU6IFtycmddIFtJbnQtYXJlYV0gUGxlYXNlIHJlc3BvbmQ6IFF1ZXN0aW9ucyBmcm9tIHRoZSAK
PiBJRVNHIGFzdG93aGV0aGVyIGEgV0cgZm9ybWluZyBCT0YgaXMgbmVjZXNzYXJ5IGZvciBMSVNQ
Cj4gCj4gICAgID4gRnJvbTogWHUgWGlhb2h1IDx4dXhoQGh1YXdlaS5jb20+Cj4gCj4gICAgID4g
VGhlIHRvLWJlLWZvcm1lZCBXRyBzaG91bGQgbm90IG9ubHkgZm9jdXMgb24gTElTUCwgYnV0IAo+
IGFsc28gZm9jdXMgb24KPiAgICAgPiBvdGhlciBtYXAmZW5jYXAgc29sdXRpb25zLgo+IAo+IFRo
ZSBwcm9ibGVtIGlzIHRoYXQgaWYgeW91IGRpZmZ1c2UgdGhlIFdHIGZvY3VzIGxpa2UgdGhpcywg
aXQgCj4gd2lsbCBzbG93IHRoaW5ncyBkb3duLiAKClN1cmUuIEhvd2V2ZXIsIHJvdXRpbmcgc2Nh
bGFiaWxpdHkgaXMgYW4gaW1wb3J0YW50IGlzc3VlLCBidXQgaXMgaXQgYWxzbyBhCnVyZ2VudCBp
c3N1ZT8gaWYgbm90LCBzbG93aW5nIGRvd24gIGEgbGl0dGxlIG1heSBub3QgYmUgYSBjb25jZXJu
LiBPbiB0aGUKY29udHJhcnksIGl0IHdpbGwgaGVscCB1cyBjb25zaWRlciB0aGluZ3MgbW9yZSBj
b21wcmVoZW5zaXZlbHkKCj4gIFRoZSBJRVRGIHByYWN0aXNlIGluIHRoZSBwYXN0IGhhcyAKPiBi
ZWVuLCB3aGVuIHRoZXJlIGFyZSBtdWx0aXBsZSBwcm90b2NvbHMgd2hpY2ggb3ZlcmxhcCBpbiAK
PiBmdW5jdGlvbmFsaXR5LCB0byBkbyBlYWNoIG9uZSBpbiBhIHNlcGFyYXRlIFdHIHByZWNpc2Vs
eSBzbyAKPiBlYWNoIGNhbiBmb2N1cyBvbiB0aGVpciBvd24gcHJvdG9jb2wuCgpJdCdzIGFsc28g
YSByZWFzb25hYmxlIHdheS4gSG93ZXZlciwgd2Ugd291bGQgaGF2ZSB0byBmb3JtIGEgbG90IG9m
CiJsaWFpc29ucyIgIHRvIHNoYXJlIGluZm9ybWF0aW9uIGFuZCBleHBlcmllbmNlIGFtb25nIHRo
ZXNlIHNlcGFyYXRlIFdHcy4gCgpYaWFvaHUKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fCnJyZyBtYWlsaW5nIGxpc3QKcnJnQGlydGYub3JnCmh0dHA6Ly93
d3cuaXJ0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9ycmcK

From rrg-bounces@irtf.org  Fri Jan 23 07:17:13 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9500228C15C; Fri, 23 Jan 2009 07:17:13 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5885928C15C for <rrg@core3.amsl.com>; Fri, 23 Jan 2009 07:17:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.503
X-Spam-Level: 
X-Spam-Status: No, score=-2.503 tagged_above=-999 required=5 tests=[AWL=0.096,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TEJjNpwY4UAw for <rrg@core3.amsl.com>; Fri, 23 Jan 2009 07:17:11 -0800 (PST)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9]) by core3.amsl.com (Postfix) with ESMTP id DE3D928C137 for <rrg@irtf.org>; Fri, 23 Jan 2009 07:17:09 -0800 (PST)
Received: from m106.maoz.com (localhost [127.0.0.1]) by m106.maoz.com (8.14.3/8.14.3/Debian-4) with ESMTP id n0NFGpBn010556;  Fri, 23 Jan 2009 07:16:51 -0800
Received: (from dmm@localhost) by m106.maoz.com (8.14.3/8.14.3/Submit) id n0NFGpoT010555; Fri, 23 Jan 2009 07:16:51 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Fri, 23 Jan 2009 07:16:51 -0800
From: David Meyer <dmm@1-4-5.net>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Message-ID: <20090123151651.GA10495@1-4-5.net>
References: <20090120190744.GA9467@1-4-5.net> <20090123000452.GA25882@1-4-5.net> <39C363776A4E8C4A94691D2BD9D1C9A105764A90@XCH-NW-7V2.nw.nos.boeing.com> <20090123022430.GA27375@1-4-5.net>
MIME-Version: 1.0
In-Reply-To: <20090123022430.GA27375@1-4-5.net>
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-gpg-fingerprint: 2409 8B50 B389 A307 BA5C 2A16 3918 03D6 A099 D8A7
X-philosophy: "I just had to let it go. John Lennon"
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: rrg <rrg@irtf.org>
Subject: [rrg] BTW, reference.I-D.draft-templin-ranger.xml
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0100957513=="
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org --===============0100957513==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="y0ulUmNC+osPPQO6"
Content-Disposition: inline


--y0ulUmNC+osPPQO6
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

	Fred,=20

> Not meaning to pick on you, but I don't understand why RANGER
> hasn't made it onto the "short list" of proposals yet; maybe
> you could answer that for me? AFAICT, RANGER is in the top-two
> map/encaps proposals in terms of technical completeness (maybe
> even the top-one) so can we have folks add it to their lists?

	I just noticed that the reference repository doesn't have
	a reference.I-D.draft-templin-ranger.xml. I built the one
	below (but haven't submitted it). Let me know if its ok.

	Dave

---

<?xml version=3D'1.0' encoding=3D'UTF-8'?>

<reference anchor=3D'I-D.templin-ranger>
<front>
<title>Routing and Addressing in Next-Generation EnteRprises (RANGER)</titl=
e>

<author initials=3D'F' surname=3D'Templin' fullname=3D'Fred Templin'>
    <organization />
</author>

<date month=3D'January' day=3D'19' year=3D'2009' />

<abstract><t>
   Next-generation enterprise networks including the global Internet
   itself will require an architected solution for the coordination of
   internal routing and addressing plans and with accommodations for
   Provider-Independent (PI) addressing, scalability, mobility, multi-
   homing and security.  Additionally, next-generation networks will
   require support for both Internet protocol versions (IPv4 and IPv6)
   for an indeterminant period; perhaps even indefinitely.  These
   considerations are particularly true for existing deployments, but
   the same principles apply even for clean-slate approaches.  The
   RANGER architecture addresses these requirements, and provides a
   comprehensive framework for IPv6/IPv4 coexistence.
</t></abstract>

</front>

<seriesInfo name=3D'Internet-Draft' value=3D'draft-templin-ranger-06' />
<format type=3D'TXT'
        target=3D'http://www.ietf.org/internet-drafts/draft-templin-ranger-=
06.txt' />
</reference>

--y0ulUmNC+osPPQO6
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkl532MACgkQORgD1qCZ2KegxACcD06+06ISw2eBJo2TbjbPlfYO
JjUAoIwN3nVLPcH1irXAe/nszx8TP4n2
=ckEd
-----END PGP SIGNATURE-----

--y0ulUmNC+osPPQO6--

--===============0100957513==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

--===============0100957513==--

From rrg-bounces@irtf.org  Fri Jan 23 07:26:30 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 462D53A689F; Fri, 23 Jan 2009 07:26:30 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 212083A689F for <rrg@core3.amsl.com>; Fri, 23 Jan 2009 07:26:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.534
X-Spam-Level: 
X-Spam-Status: No, score=-6.534 tagged_above=-999 required=5 tests=[AWL=0.065,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5mWQstbk6xtS for <rrg@core3.amsl.com>; Fri, 23 Jan 2009 07:26:29 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id CA20D3A67F2 for <rrg@irtf.org>; Fri, 23 Jan 2009 07:26:28 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,312,1231113600"; d="scan'208";a="34652511"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 23 Jan 2009 15:25:11 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n0NFP8tY014386;  Fri, 23 Jan 2009 10:25:08 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n0NFP4Hj005627; Fri, 23 Jan 2009 15:25:08 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Fri, 23 Jan 2009 10:25:07 -0500
Received: from cisco.com ([10.86.248.108]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 23 Jan 2009 10:25:06 -0500
Date: Fri, 23 Jan 2009 10:25:00 -0500
From: Scott Brim <swb@employees.org>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Message-ID: <20090123152500.GH4159@cisco.com>
Mail-Followup-To: Scott Brim <swb@employees.org>, "Templin, Fred L" <Fred.L.Templin@boeing.com>, David Meyer <dmm@1-4-5.net>, Yakov Rekhter <yakov@juniper.net>, rrg <rrg@irtf.org>, int-area@ietf.org, routing-discussion@ietf.org
References: <20090120190744.GA9467@1-4-5.net> <20090123000452.GA25882@1-4-5.net> <39C363776A4E8C4A94691D2BD9D1C9A105764A90@XCH-NW-7V2.nw.nos.boeing.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A105764A90@XCH-NW-7V2.nw.nos.boeing.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-OriginalArrivalTime: 23 Jan 2009 15:25:06.0850 (UTC) FILETIME=[C566E820:01C97D6E]
Authentication-Results: rtp-dkim-1; header.From=swb@employees.org; dkim=neutral
Cc: rrg <rrg@irtf.org>, int-area@ietf.org, routing-discussion@ietf.org
Subject: Re: [rrg] [Int-area] Please respond: Questions from the IESG asto	whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org Excerpts from Templin, Fred L on Thu, Jan 22, 2009 04:38:35PM -0800:
> Not meaning to pick on you, but I don't understand why RANGER
> hasn't made it onto the "short list" of proposals yet; maybe
> you could answer that for me? AFAICT, RANGER is in the top-two
> map/encaps proposals in terms of technical completeness (maybe
> even the top-one) so can we have folks add it to their lists?
> 
> Thanks - Fred
> fred.l.templin@boeing.com

To start with, could we pick one list to discuss RANGER on?  How about
RRG?  Fred?
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Fri Jan 23 09:02:23 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DB20028C19E; Fri, 23 Jan 2009 09:02:23 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D07993A6929; Fri, 23 Jan 2009 09:02:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.438
X-Spam-Level: 
X-Spam-Status: No, score=-6.438 tagged_above=-999 required=5 tests=[AWL=0.161,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M7Skue9OGAxe; Fri, 23 Jan 2009 09:02:16 -0800 (PST)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id B33603A67F2; Fri, 23 Jan 2009 09:02:16 -0800 (PST)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n0NH1Mia028174 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 23 Jan 2009 09:01:24 -0800 (PST)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n0NH1LC9024939; Fri, 23 Jan 2009 11:01:21 -0600 (CST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n0NH1HOn024846; Fri, 23 Jan 2009 11:01:21 -0600 (CST)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 23 Jan 2009 09:01:19 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 23 Jan 2009 09:01:18 -0800
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A105764CB7@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <20090123152500.GH4159@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] [Int-area] Please respond: Questions from the IESG astowhether a WG forming BOF is necessary for LISP
Thread-Index: Acl9b0QzCSCTgC+VTIKziDqjssELfAABYjgQ
References: <20090120190744.GA9467@1-4-5.net> <20090123000452.GA25882@1-4-5.net> <39C363776A4E8C4A94691D2BD9D1C9A105764A90@XCH-NW-7V2.nw.nos.boeing.com> <20090123152500.GH4159@cisco.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Scott Brim" <swb@employees.org>
X-OriginalArrivalTime: 23 Jan 2009 17:01:19.0281 (UTC) FILETIME=[3609FA10:01C97D7C]
Cc: rrg <rrg@irtf.org>, int-area@ietf.org, routing-discussion@ietf.org
Subject: Re: [rrg] [Int-area] Please respond: Questions from the IESG astowhether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org Hi Scott, 

> -----Original Message-----
> From: Scott Brim [mailto:swb@employees.org] 
> Sent: Friday, January 23, 2009 7:25 AM
> To: Templin, Fred L
> Cc: David Meyer; Yakov Rekhter; rrg; int-area@ietf.org; 
> routing-discussion@ietf.org
> Subject: Re: [rrg] [Int-area] Please respond: Questions from 
> the IESG astowhether a WG forming BOF is necessary for LISP
> 
> Excerpts from Templin, Fred L on Thu, Jan 22, 2009 04:38:35PM -0800:
> > Not meaning to pick on you, but I don't understand why RANGER
> > hasn't made it onto the "short list" of proposals yet; maybe
> > you could answer that for me? AFAICT, RANGER is in the top-two
> > map/encaps proposals in terms of technical completeness (maybe
> > even the top-one) so can we have folks add it to their lists?
> > 
> > Thanks - Fred
> > fred.l.templin@boeing.com
> 
> To start with, could we pick one list to discuss RANGER on?  How about
> RRG?  Fred?

My leaning would be toward int-area based on the maturiy of
the specs. I already have a head start on running code:

http://osprey67.com/vet/
http://osprey67.com/seal/

but this is an excellent opportunity for linux, *BSD, etc.
enthusiasts who might be interested in developing independent
implementations (commercial vendor implementations are also
welcome).

Thanks - Fred
fred.l.templin
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Sat Jan 24 06:00:48 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 24BB63A6B76; Sat, 24 Jan 2009 06:00:48 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3654B3A6B84 for <rrg@core3.amsl.com>; Sat, 24 Jan 2009 06:00:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.538
X-Spam-Level: 
X-Spam-Status: No, score=-0.538 tagged_above=-999 required=5 tests=[AWL=-0.758, BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, J_CHICKENPOX_35=0.6, J_CHICKENPOX_36=0.6, J_CHICKENPOX_43=0.6, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rqOhWW3n0rhL for <rrg@core3.amsl.com>; Sat, 24 Jan 2009 06:00:45 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123]) by core3.amsl.com (Postfix) with ESMTP id 4F1163A6B76 for <rrg@irtf.org>; Sat, 24 Jan 2009 06:00:44 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6]) by gair.firstpr.com.au (Postfix) with ESMTP id BF962175C80; Sun, 25 Jan 2009 01:00:25 +1100 (EST)
Message-ID: <497B1F7A.9030407@firstpr.com.au>
Date: Sun, 25 Jan 2009 01:02:34 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: int-area@ietf.org, rrg <rrg@irtf.org>
References: <20090120190744.GA9467@1-4-5.net> <49765FFB.1010709@piuha.net>	<200901222339.n0MNddM88868@magenta.juniper.net> <75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com>
In-Reply-To: <75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com>
Cc: routing-discussion@ietf.org
Subject: Re: [rrg] [Int-area] Please respond: Questions from the IESG as to whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

I am responding to Yakov Rekhter, Christopher Morrow and Xu Xiaohu.

Short version:

   I think it is still early days for routing scaling solutions.

   LISP has too many fundamental problems to be considered a
   potentially practical solution.  Some of these problems require
   design changes and others are probably solvable via extensions
   to the current design.  These problems are well documented.
   Running more experiments, writing interoperable implementations
   etc. will not help solve these problems.

   The other core-edge separation schemes (APT, Ivip, TRRP and
   Six/One Router) need a lot more development before a sufficient
   number of people in this field would agree that it was a (or
   "the") promising solution.

   Whether in a WG or independent of the IETF, I think each
   proposal should be developed vigorously - but with all
   developers taking a keen interest in the other proposals and
   responding fully in a public discussion list (their own, or
   the RRG) to those who make constructive critiques of their
   proposals.


Yakov Rekhter wrote:

> In answering this question we need to keep in mind that such
> techniques as (a) caching routing and forwarding information, (b)
> use of separate mapping system for Loc/ID mapping, (c) relying on
> probing for determining path feasibility are essential/fundamental
> to LISP. In other words, these techniques form the foundation of
> LISP. Concerns with scaling and operational properties of these
> techniques have been raised many times before (both at the previous
> BOF, as well as on the RRG mailing list). Yet the LISP proponents
> still did not adequately address these concerns.

Some LISP problems which I think are unresolved include the
following, many of which are mentioned in the critiques section of:

  http://www.firstpr.com.au/ip/ivip/lisp-links/

1 - Delays in delivering initial packets in a flow.  This is either
    due to sending the packets along the ALT network (which takes
    time and involves sending substantial volumes of data packets
    over the ALT network, rather than just mapping requests) or to
    sending mapping requests only, and waiting for the ITR to get a
    response before it attempts to send traffic packets.

    According to: http://www.lisp4.net/docs/lisp-ausnog02.ppt pp 10
    & 11 the experimental LISP ALT network's ITRs drop initial
    packets and send brief map request messages.   Even if we think
    this delay doesn't matter, I am sure enough potential adopters
    would - and therefore make it difficult or impossible for LISP or
    any other such solution to be widely enough adopted to solve the
    routing scaling problem.

      [Fix?  This seems to be inherent in the ALT architecture.
       There's no obvious fix by caching in the ALT network and
       with millions of nodes (ITRs and ETRs) in the ALT network,
       there are going to be multiple hops in the network which
       result in inherent delays which would affect all session
       establishment, and even single byte communications such
       as ping, some DNS queries and responses etc.]

      {Experiments?  The problem won't show up in any experimental
       network - only in real use with tens or hundreds of thousands
       of ALT routers.}

2 - LISP-ALT's long-path problem
      http://psg.com/lists/rrg/2008/msg01676.html
      http://www.antd.nist.gov/~ksriram/strong_aggregation.png

      [Fix? Another fundamental problem in the architecture.  Could
       be partially solved by more meshiness, but that would greatly
       increase the complexity of the network and so raise more
       scaling problems.]

      {Experiments?  As for 1 above.}

3 - Problems creating a highly aggregated ALT network in order to
    speed the flow of packets up and down the hierarchy, while also
    making the network robust against the failure of its routers and
    tunnels.  This has not been discussed much on the RRG, but it is
    an obvious problem.

      [Fix?  Again, only by making it meshier, which detracts from
       the ALT network's primary design goal - of being highly
       aggregated to enhance efficiency and to minimise scaling
       problems.]

      {Experiments?  As for 1 above.)

4 - LISP-ALT's Aggregation implies provider dependence.
    This is Christian Vogt's critique:
    http://psg.com/lists/rrg/2008/msg00259.html

      [Fix?  Seems to be a fundamental problem, but every core-edge
       separation scheme involves supplying stable EID, micronet etc.
       address space to end-user networks, so there must be some
       kind of dependence on some organisation - though not
       necessarily an ISP.]

      {Experiments?  There's no need for experiment - problems such
       as this can be clearly foreseen.}

5 - Path MTU Discovery problems.  Despite Fred Templin, myself and
    others discussing the inherent PMTUD problems in any map-encap
    proposal, there has been nothing from the LISP team to indicate
    they have a solution.  They seem to think there is no problem.

      [Fix?  Add some arrangements such as I propose:
       http://www.firstpr.com.au/ip/ivip/pmtud-frag/ or maybe
       like something Fred proposes.]

      {Experiments?  Experiment with such a fix, but the real
       test only comes with many years of full deployment, with a
       rich mix of jumboframe compatible edge networks and DFZ paths,
       and with 1500 byte and slightly smaller MTU links still being
       used in some or many places.}

6 - Lack of business case for LISP's Proxy Tunnel Routers:
    http://psg.com/lists/rrg/2008/msg02021.html

      [Fix: Develop a detailed proposal for how end-users would
       gain their EID address space in a way in which some
       organisation would have a financial incentive to build
       and run a set of PTRs all round the world which would
       advertise a single prefix in the DFZ which would cover
       the EID space of many (thousands or more) end-user
       networks.  AFAIK LISP could adopt something similar to
       Ivip's arrangements:
       http://psg.com/lists/rrg/2008/msg01158.html ]

     {Experiments?  This is not amenable to experiment - there
      needs to be a good proposal which can only be tested in the
      commercial reality of widespread deployment.  In other words:
      there will be no widespread deployment of any proposal until
      the proposal is found to be attractive by the end-user networks
      which we need to adopt the scalable routing proposal -
      essentially all of them.  That will only happen if the proposal
      fully supports multihoming etc. of packets sent by hosts in
      non-upgraded networks.  Ivip's OITRDs and LISP's PTRs are the
      only ways to do this.  (APT has an arrangement with some
      similar business case difficulties as LISP's and TRRP's
      solution involves a worrying number of carrots and sticks.)
      So there needs to be an attractive business case for these
      OITRDs or PTRs.}

7 - The scaling problems of potentially thousands of ITRs each
    probing reachability to one ETR, and likewise, one ITR probing
    reachability to many ETRs - this is one view of the "Locator Path
    Liveness Problem" of draft-meyer-loc-id-implications-00.
    http://www.irtf.org/pipermail/rrg/2009-January/000809.html

      [Fix?   The problems of ITRs having to determine reachability
       and make decisions about which ETR to use seem to be
       fundamental to LISP, APT, TRRP or to any other core-edge
       elimination scheme which does not have a real-time mapping
       distribution system.]

      {Experiments?  Not useful at all - this problem won't show up
       in an experimental network, but can be clearly foreseen in
       a full-scale deployment scenario.}

> Unless these concerns are adequately addressed, claiming that LISP
> is an appropriate solution to the problems discussed at the IAB's
> October 2006 Routing and Addressing Workshop is nothing more than
> a proof by an emphatic assertion.

I agree entirely.

I believe the LISP team could have made much better use of the RRG -
by participating fully in the debates resulting from these critiques.

Experiments won't help solve most of these problems.  I am not
against experimentation and I think it is great that there is a LISP
experimental network.

However, I would never have taken a proposal to the point of writing
code, running a network and inviting others to write compatible
implementations when the proposal had so many fundamental problems.

I would have worked first to resolve the problems - and if they could
not be resolved, I would have abandoned the proposal.  LISP's
problems are generally not amenable to solution by experiment.

I think that a proposal should proceed to experiment once the
fundamental problems (which are not amenable to experimental
solution) are either resolved, or well on the way to being resolved.

The starting point for solving LISP's problems would be admitting
them as problems and then discussing them.

draft-meyer-loc-id-implications is a step in the right direction, but
the problems of having large numbers of ITRs probing large numbers of
ETRs, making their own decisions etc. has been obvious since the
inception of LISP and APT two years ago.


> Addressing these concerns does *not* require LISP protocol specs.
> Addressing these concerns does *not* require experimentation with
> LISP protocols either. Addressing these concerns does *not* require
> interoperable LISP implementations. Therefore, forming a WG to work
> on the design on the LISP base protocol , the LISP+ALT mapping
> system, LISP Interworking  and LISP multicast", and to "encourage
> and support interoperable LISP implementations as well as defining
> requirements for alternate mapping systems" (as was proposed in
> Dave's e-mail) is *not* going to address these concerns.
>
> Unless the concerns I mentioned above are adequately addressed,
> LISP can not be accepted as a feasible/practical approach towards
> routing scalability.

I agree entirely.

> Therefore, unless and until these concerns are adequately
> addressed, it is totally premature to form LISP WG.

Is the criteria for forming a WG is that the proposal is either "the"
solution to the given problem or one of a few such proposals which
show sufficient promise to warrant serious effort to develop into a
full set of technical specifications?

If so, then I don't think LISP is anywhere near the mark, due to the
large number of fundamental problems which are nowhere near being solved.


Christopher Morrow wrote:

> I'm not sure there have been any other credible solutions aside from
> 'map/encap', this seems promising, though certainly it hasn't been
> proven out in the way that v4 routing as we know it today has been.

I would agree with a reworded version of the above, replacing
'map/encap' with:

   core-edge separation schemes (all of which - apart from Six/One
   Router - started as map-encap)

Although I haven't read draft-templin-ranger, I think it is fair to
say there are no Core-Edge Elimination proposals (inherently
host-based, and limited to IPv6) which are developed to the level of
the three most developed core-edge separation schemes:

  LISP (ALT and NERD, which is widely regarded as unscalable)
  APT
  Ivip

    (Six/One Router is IPv6-only, and needs to steal a bit from the
     IPv6 header - which I think would require DFZ router upgrades,
     which may well be practical.  See my critiques:

       http://psg.com/lists/rrg/2008/msg02034.html
       http://psg.com/lists/rrg/2008/msg02218.html )


LISP and APT are purely map-encap.

Ivip in the longer term, or ideally from the start, is intended to
use modified DFZ (and other) routers so some or all of the ETR
address can be encoded into a modified version of the IPv4 or IPv6
header.  This removes the encapsulation overhead efficiency problem
and more importantly involves no PMTUD problems.  Ideally, Ivip
wouldn't use map-encap at all, but it could use map-encap initially.


> Certainly there are use cases where there will be issues, certainly
> there are ways to deal with these use cases. Without some direct
> experimentation, thought about the problems and focus, we won't be
> able to address these things. (we == community)

I disagree.  The most pressing problems with LISP can be clearly
foreseen and do not need any illumination from experimentation.  Most
of them need to be solved by changing the architecture, though the
PMTUD and PTR business case models could be solved by adding to the
current architecture.  If they can't be solved clearly by changing
the design, then it needs to be recognised that these fundamental
problems are a strong argument against adopting any such proposal as
the solution to the routing scaling problem.


Xu Xiaohu wrote:

> Exactly. The to-be-formed WG should not only focus on LISP, but
> also focus on other map&encap solutions.

I think it is widely agreed that each WG should have a single,
concrete, focus.

I think the best way forward, in addition to the RRG discussions
(which I guess will continue after we make our recommendation at the
end of March) is for the most promising proposals to be developed as
vigorously as possible, while learning from and cross-fertilising the
other proposals.

I think each such proposal should have its own, potentially private,
mailing list so the people concerned can work together in whatever
way suits them best.

There is now a LISP-Interest mailing list - but my impression is that
LISP development to date has been based on private communications
between the largely Cisco-based developers.

> Just as Yakov etc. pointed out, there are still some open issues in
> LISP need to be answered. If many different map&encaps solutions
> can be explored further simultaneously under this WG charter, we
> may find they are complementary and can be converged finally to
> form a successful short-term solution.

I think the best way to develop a proposal is a dedicated project -
but one in which the developers take a keen interest in critiques of
their work, and in the work of other comparable projects.

My impression of LISP development to date is that it has been far too
 insular - uninterested in critiques or on how other proposals work.

I think the developers of APT, TRRP and Six/One Router have been much
more responsive to critiques.

There's no way of forcing the LISP developers to take a greater
interest in these things.

What would be the purpose of giving the LISP team their own IETF WG?

It doesn't allow them to develop anything they can't develop on their
own, with their own private or public mailing list, meetings etc.

If creating a LISP WG carries some implication that LISP, or anything
resembling it, is "nearly ready for widespread adoption" or similar,
then I think it would be a mistake.

However, if (like HIP and probably many other protocols IETF WGs
eventually produce full, interoperable, specifications for) LISP is
regarded as being worth working on for experimental purposes AND it
is thought that the best way to do this is to form a WG, then a LISP
WG would be a good idea.

However, I think it is mistaken to believe that writing code, running
an experimental network and writing interoperable implementations
will solve LISP's fundamental problems.


Ideally, after 2 years of developing various proposals and discussing
this stuff on the RAM and then the RRG lists, the RRG would be in a
position to say something like:

  This exact proposal, or an architecture with these principles and
  characteristics, is both a promising way to solve the routing
  scaling problem and by far the most promising solution.  Therefore,
  we recommend the IETF form a WG to develop this proposal /
  architecture into a fully fledged specification, with the intention
  that it be ready for widespread adoption by ISPs and end-user
   networks by the middle of the next decade.

However, I think the RRG is not ready to do this.  Despite this
problem having been foreseen since the early 1990s, it is still early
days in terms of developing the most promising solution.

LISP has too many problems, with no obvious solutions in sight and
with an apparent reluctance of the developers to discuss many of
these problems in public.

APT is the work of a smaller group than LISP.  It doesn't have LISP's
problem with delaying initial packets.  The hybrid push-pull mapping
system with local full-database query servers solves the delay
problem, removes the need for a global query server system (LISP ALT
and TRRP) and uses a slow mapping distribution system which doesn't
raise any obvious scaling problems.  But without running code and a
demo system, would the RRG be able to say for sure this might be a
practical solution, or the best possible solution?  I think not.

Ivip has a smaller team still - so far just me, with the help of
Steve Russert.  Ivip is more ambitious than LISP and APT in some
ways, but simpler in others.  It will be two years at least before
there is running code (but I hope to have a complete set of I-Ds
before March).  I like to think the RRG would see the promise of Ivip
and recommend it to the IETF . . . but it is early days yet for all
these proposals.


I think the most likely outcome of these last two years is that we
agree that a solution needs to be developed by about 2014 which we
can be confident will be very widely adopted for IPv4 - with
something cooking for IPv6 too.

I think we can rule out host-based core-edge elimination schemes on
grounds of excessive complexity in all hosts, excessive management
traffic to and from hosts - and also in terms of such changes (host
changes, probably including major changes to applications) being at
odds with the need to have the solution voluntarily adopted by the
great majority of end-user networks.

That leaves the core-edge separation schemes.

There is a big distinction between those which integrate reachability
probing and decision making into the ITRs and the architecture itself
(LISP, APT, TRRP and the IPv6-only Six/One Router) and those (only
one so far - Ivip) which use a real-time mapping system so the
reachability testing and "which ETR to use" decision making is under
the direct control of each end-user network, and modularly separated
from the scheme itself.

There is also a big distinction between those schemes (LISP, APT and
TRRP) which would forever be stuck with encapsulation overheads and
having to solve the PMTUD problems inherent in map-encap, and those
(so far Ivip and Six/One Router) which will get the packets across
the core without overheads or PMTUD problems.

I don't think any of these are developed enough to warrant the IETF
developing just one as "the" solution.

  - Robin           http://www.firstpr.com.au/ip/ivip/


_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Sat Jan 24 11:51:34 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EBAFF28C10E; Sat, 24 Jan 2009 11:51:34 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 097E63A6AEC for <rrg@core3.amsl.com>; Sat, 24 Jan 2009 11:51:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.505
X-Spam-Level: 
X-Spam-Status: No, score=-6.505 tagged_above=-999 required=5 tests=[AWL=0.094,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9Lyvgr5DFlRv for <rrg@core3.amsl.com>; Sat, 24 Jan 2009 11:51:33 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 5DF973A6A90 for <rrg@irtf.org>; Sat, 24 Jan 2009 11:51:33 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,318,1231113600"; d="scan'208";a="236067327"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-6.cisco.com with ESMTP; 24 Jan 2009 19:51:04 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n0OJp4J3005488;  Sat, 24 Jan 2009 11:51:04 -0800
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id n0OJp45A018355; Sat, 24 Jan 2009 19:51:04 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Sat, 24 Jan 2009 11:51:04 -0800
Received: from [10.224.151.60] ([10.21.121.232]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Sat, 24 Jan 2009 11:51:03 -0800
Message-Id: <6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: Robin Whittle <rw@firstpr.com.au>
In-Reply-To: <497B1F7A.9030407@firstpr.com.au>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Sat, 24 Jan 2009 10:26:11 -0800
References: <20090120190744.GA9467@1-4-5.net> <49765FFB.1010709@piuha.net>	<200901222339.n0MNddM88868@magenta.juniper.net> <75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com> <497B1F7A.9030407@firstpr.com.au>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 24 Jan 2009 19:51:03.0945 (UTC) FILETIME=[16FC1F90:01C97E5D]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=11412; t=1232826664; x=1233690664; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dino@cisco.com; z=From:=20Dino=20Farinacci=20<dino@cisco.com> |Subject:=20Re=3A=20[rrg]=20[Int-area]=20Please=20respond=3 A=20Questions=20from=20the=20IESG=20as=20to=20whether=20a=20 WG=20forming=20BOF=20is=20necessary=20for=20LISP |Sender:=20; bh=hBuGcYUVI8LVCGe45Tue55NR90KPSeHbbUAyOsoE0zQ=; b=rBt8KrUCNkDS3K9ue8VX4Zu8tRu4noMs1PnN4uya0969TQQXMKZF/7GQsq Kt8wPzrt4s9dxJHkhPoGgo5Ok4SFz0xdf7lonycAf9hdJXOxul3rdPZuXbKN VGdmxCJGoA;
Authentication-Results: sj-dkim-2; header.From=dino@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); 
Cc: rrg RG <rrg@irtf.org>, int-area@ietf.org, lisp@ietf.org, routing-discussion@ietf.org
Subject: Re: [rrg] [Int-area] Please respond: Questions from the IESG as to whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

>   LISP has too many fundamental problems to be considered a
>   potentially practical solution.  Some of these problems require

LISP is not perfect and still evolving but let me point out that every  
design has fundamental problems. At this scale, it's very hard to be  
perfect Robin. And as Noel has stated so many times, the hard  
decisions must be made to incrementally deploy this. So things might  
not look pretty on the surface, but jeez, you got to do what you got  
to do. Else, this will all be academic.

We really want to solve this problem, sincerely. This is not lip  
service, we are not just writing papers, we want to rev the Internet,  
this is serious.

I want to address each of your 7 points below. I have cc'ed the lisp@ietf.org 
  mailing list so the folks who want to focus on details of LISP can  
see this thread.

> 1 - Delays in delivering initial packets in a flow.  This is either
>    due to sending the packets along the ALT network (which takes
>    time and involves sending substantial volumes of data packets
>    over the ALT network, rather than just mapping requests) or to
>    sending mapping requests only, and waiting for the ITR to get a
>    response before it attempts to send traffic packets.

We have a memory/bandwidth tradeoff. So we have to make a hard design  
call. I'd rather have mappings cached and timed out so they can be  
updated when they need to then to hold all the possible mappings for  
the Internet in an ITR.

There is no such thing of a free lunch. You either store all possible  
mappings or you fetch them when you need them.

>    According to: http://www.lisp4.net/docs/lisp-ausnog02.ppt pp 10
>    & 11 the experimental LISP ALT network's ITRs drop initial
>    packets and send brief map request messages.   Even if we think
>    this delay doesn't matter, I am sure enough potential adopters
>    would - and therefore make it difficult or impossible for LISP or
>    any other such solution to be widely enough adopted to solve the
>    routing scaling problem.

Then why was/is ARP deployed in a 10^4 host-based bridged network with  
basically the same properties. First packet loss is not persistent  
when you look at all the traffic that originates from a source site to  
another destination site.

The host vendors are probably thinking, if we do LISP in the host, you  
could wait to send your TCP SYN before the mapping is available. Guess  
what, you don't send that TCP SYN before you get the DNS Reply. ;-) I  
wonder why? Well I'll spell it out. If a host needs an address to make  
the connection, we can say it also needs a locator to make a connection.

The design choice of LISP *is to just change software in CPE devices*  
to get the feature of decoupling rather than changing all the hosts at  
a site. That's a huge deployment advantage. So these CPE devices get  
packets before they have mappings. We don't even want to consider a  
host to CPE router signaling protocol and all it's complexities to  
solve this and to keep the architecture pure, we don't want to snoop  
on DNS, SIP, or any other protocol that can give us a hint on where  
the host is about to send a packet.

So the cost is *either* first packet loss or sending the packet on the  
ALT using it as a request for a mapping.

> 2 - LISP-ALT's long-path problem
>      http://psg.com/lists/rrg/2008/msg01676.html
>      http://www.antd.nist.gov/~ksriram/strong_aggregation.png
>
>      [Fix? Another fundamental problem in the architecture.  Could
>       be partially solved by more meshiness, but that would greatly
>       increase the complexity of the network and so raise more
>       scaling problems.]

Well this I believe is a duplicate of 1 above. So it's not really  
*another* problem.

> 3 - Problems creating a highly aggregated ALT network in order to
>    speed the flow of packets up and down the hierarchy, while also
>    making the network robust against the failure of its routers and
>    tunnels.  This has not been discussed much on the RRG, but it is
>    an obvious problem.

If we can do this with BGP, which we have decades of existence proof  
why can't we do this with a tunnel topology 1) where a tunnel can be  
rehomed much quicker and easily than physical links and boxes we have  
to do with today, allowing aggregation to occur at the edges of the  
ALT network, and 2) these tunnels stay up because there is robust  
connectivity below the tunnel level to keep them up, hence there will  
be less route-flaps for EID-prefixes.

I think it's the complete opposite of what you claim. I think BGP will  
be more stable and scalable then the underlying BGP. Plus, what we  
propose for the use-case of BGP uses quite a few features of it.  
Recall this is eBGP over GRE.

We have an infrastructure where we can 1) ping to see liveness of  
nodes on the ALT. We have traceroute to determine the path a Map- 
Request takes on the ALT. We can ping/traceroute "underneath" so we  
can see the diameter of the tunnel. Not only do we have a solution but  
we use existing rudimentary tools for management.

And the address allocation hierarchy can map this logical ALT  
topology. And if the Registries are involved in managing part of this  
ALT network (which we hope and think they will), we can keep this  
consistent relationship.

Do you realize the goodness of this? It's huge Robin.

There's more too, you then throw SIDR in the mix and we have secured  
the ALT, we have secured mappings, we created a PKI for routing use.  
In fact, the first SIDR deployment could happen on the ALT to be  
verified/experimented before it goes on the underlying BGP.

And note, that the infrastructure will/does carry exactly 2 address- 
families. So we can do 6-to-6-over-4 with this approach. That means we  
can get two site to be *IPv6-only* and be able to talk to each other.

If you are a IPv6-only site now or a dual-stack site, you could talk  
to the new IPv6 Google services. I think this is a pretty huge feature.

This is clean and architecturally pure, no double NATs, no CGNS, and  
no applications breaking.

> 4 - LISP-ALT's Aggregation implies provider dependence.
>    This is Christian Vogt's critique:
>    http://psg.com/lists/rrg/2008/msg00259.html

Not true. Aggregation here is for the EID-prefix. Service providers do  
not carry EID-prefixes in their cores so you don't depend on them. The  
decoupling of the address creates this. The dependence is now on the  
ALT. And if your site resides in a specific region of the world, you  
get your EID-prefixes from that registry. So readdressing your domain  
would only occur if you moved it from one region to another (let's  
leave mobile ASes out of this for now).

> 5 - Path MTU Discovery problems.  Despite Fred Templin, myself and
>    others discussing the inherent PMTUD problems in any map-encap
>    proposal, there has been nothing from the LISP team to indicate
>    they have a solution.  They seem to think there is no problem.

In section 5.4 of draft-farinacci-lisp-11.txt we describe two proposed  
solutions, one is stateless, and the other is stateful. The stateful  
creates no new table data structures but requires storing an addition  
2-bytes of effective-MTU state per mapping.

> 6 - Lack of business case for LISP's Proxy Tunnel Routers:
>    http://psg.com/lists/rrg/2008/msg02021.html

You cannot fault a technical design for a business case. A PTR is  
solving a technical problem. And if we want to *truly* keep lots of PI  
type routes out of the core *and* avoid NAT solutions which are just  
way too high in opex, the PTR is the only solution we have to turn to.

And on the contrary, I do believe service providers, interconnect  
providers, registries, third-parties and even governments will provide  
PTR services. Will they make a ton of money out of it, well that  
remains to be seen.

> 7 - The scaling problems of potentially thousands of ITRs each
>    probing reachability to one ETR, and likewise, one ITR probing
>    reachability to many ETRs - this is one view of the "Locator Path
>    Liveness Problem" of draft-meyer-loc-id-implications-00.
>    http://www.irtf.org/pipermail/rrg/2009-January/000809.html

That is not in the LISP design. Everyone just thinks it is.  ;-)

Dave and Darrel's draft is providing a warning about how bad probing  
can be. They do not take a position whether it should go into any  
proposal. They are just saying, beware of the Frankenstein that may  
result and can be an interpretation to not do probing at all.

Like I mentioned in a previous RRG email message, one has to ask the  
question if an ITR *should* switch from one RLOC to another when there  
*may* be a path failure *somewhere in the middle of the network*.  
Please note my very fine qualifications.

If we want to solve this problem, we could do this today by having a  
host switch it's TCP connection to another A record. This doesn't  
happen today because people deal with packet loss, since it doesn't  
last long *and* rerouting actually works quite well.

Van Jacobson always made this comment and I'll never forget it, "The  
fact that the Internet drops packets is it's greatest feature".

What else can either an xTR or TCP host do when sending ICMP  
Unreachables are off by default in most modern routers, or they are  
filtered by firewalls, and route aggregation hides failures close to  
packet sources.

>> Unless these concerns are adequately addressed, claiming that LISP
>> is an appropriate solution to the problems discussed at the IAB's
>> October 2006 Routing and Addressing Workshop is nothing more than
>> a proof by an emphatic assertion.
>
> I agree entirely.
>
> I believe the LISP team could have made much better use of the RRG -
> by participating fully in the debates resulting from these critiques.

We were asked to do research in RRG. That was a reasonable request. So  
the research stuff in LISP has been and will continue to be presented  
in RRG.

As for the engineering issues, the real details and bits and bytes, we  
want a forum to discuss and work out issues in an open forum. I've  
been going to IETF for 20 years now, that forum is called a working  
group.

The working group doesn't have to standardize what it is working on.  
And the charter and the numerous requests we have made requests *for  
an experimental working group*.

> Experiments won't help solve most of these problems.  I am not
> against experimentation and I think it is great that there is a LISP
> experimental network.
>
> However, I would never have taken a proposal to the point of writing
> code, running a network and inviting others to write compatible
> implementations when the proposal had so many fundamental problems.

There is constant implementation feedback back into the design.  
Experienced engineers know how this cycle works. You start with  
something you think can hold together, you try things out, you refine,  
you revisit design, you go forward with implementation. That's the  
process of *detailed* engineering.

For the old timers, that was the difference between TCP/IP and OSI.

Sorry for the long email,
Dino

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Sun Jan 25 09:20:48 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9618B3A6B5B; Sun, 25 Jan 2009 09:20:48 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D974E28C158; Sun, 25 Jan 2009 09:20:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.776
X-Spam-Level: 
X-Spam-Status: No, score=-0.776 tagged_above=-999 required=5 tests=[AWL=0.426,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MUijuU-de38x; Sun, 25 Jan 2009 09:20:45 -0800 (PST)
Received: from imo-d04.mx.aol.com (imo-d04.mx.aol.com [205.188.157.36]) by core3.amsl.com (Postfix) with ESMTP id 39DC03A6B55; Sun, 25 Jan 2009 09:20:45 -0800 (PST)
Received: from HeinerHummel@aol.com by imo-d04.mx.aol.com  (mail_out_v39.1.) id c.cea.4cba28ba (65097); Sun, 25 Jan 2009 12:19:52 -0500 (EST)
From: HeinerHummel@aol.com
Message-ID: <cea.4cba28ba.36adf938@aol.com>
Date: Sun, 25 Jan 2009 12:19:52 EST
To: dino@cisco.com, rw@firstpr.com.au
MIME-Version: 1.0
X-Mailer: 9.0 SE for Windows sub 5021
Cc: rrg@irtf.org, int-area@ietf.org, lisp@ietf.org, routing-discussion@ietf.org
Subject: Re: [rrg] [Int-area] Please respond: Questions from the IESG as to whether a ...
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1845881207=="
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

--===============1845881207==
Content-Type: multipart/alternative; boundary="-----------------------------1232903992"


-------------------------------1232903992
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

=20
Dino,
Just a simple question: Is the ALT GRE-tunnel hierarchy a tree ?
=20
Heiner
=20
=20
In einer eMail vom 24.01.2009 20:51:53 Westeurop=E4ische Normalzeit schreibt=
 =20
dino@cisco.com:

>   LISP has too many fundamental problems to be  considered a
>   potentially practical solution.  Some of  these problems require

LISP is not perfect and still evolving but let  me point out that every =20
design has fundamental problems. At this  scale, it's very hard to be =20
perfect Robin. And as Noel has stated so  many times, the hard =20
decisions must be made to incrementally deploy  this. So things might =20
not look pretty on the surface, but jeez, you  got to do what you got =20
to do. Else, this will all be  academic.

We really want to solve this problem, sincerely. This is not  lip =20
service, we are not just writing papers, we want to rev the  Internet, =20
this is serious.

I want to address each of your 7  points below. I have cc'ed the=20
lisp@ietf.org=20
mailing list so the  folks who want to focus on details of LISP can =20
see this  thread.

> 1 - Delays in delivering initial packets in a flow.   This is either
>    due to sending the packets along the ALT  network (which takes
>    time and involves sending  substantial volumes of data packets
>    over the ALT network,  rather than just mapping requests) or to
>    sending mapping  requests only, and waiting for the ITR to get a
>    response  before it attempts to send traffic packets.

We have a memory/bandwidth  tradeoff. So we have to make a hard design =20
call. I'd rather have  mappings cached and timed out so they can be =20
updated when they need  to then to hold all the possible mappings for =20
the Internet in an  ITR.

There is no such thing of a free lunch. You either store all  possible =20
mappings or you fetch them when you need  them.

>    According to:  http://www.lisp4.net/docs/lisp-ausnog02.ppt pp 10
>    &  11 the experimental LISP ALT network's ITRs drop initial
>     packets and send brief map request messages.   Even if we  think
>    this delay doesn't matter, I am sure enough  potential adopters
>    would - and therefore make it  difficult or impossible for LISP or
>    any other such  solution to be widely enough adopted to solve the
>    routing  scaling problem.

Then why was/is ARP deployed in a 10^4 host-based  bridged network with =20
basically the same properties. First packet  loss is not persistent =20
when you look at all the traffic that  originates from a source site to =20
another destination  site.

The host vendors are probably thinking, if we do LISP in the  host, you =20
could wait to send your TCP SYN before the mapping is  available. Guess =20
what, you don't send that TCP SYN before you get  the DNS Reply. ;-) I =20
wonder why? Well I'll spell it out. If a host  needs an address to make =20
the connection, we can say it also needs a  locator to make a connection.

The design choice of LISP *is to just  change software in CPE devices* =20
to get the feature of decoupling  rather than changing all the hosts at =20
a site. That's a huge  deployment advantage. So these CPE devices get =20
packets before they  have mappings. We don't even want to consider a =20
host to CPE router  signaling protocol and all it's complexities to =20
solve this and to  keep the architecture pure, we don't want to snoop =20
on DNS, SIP, or  any other protocol that can give us a hint on where =20
the host is  about to send a packet.

So the cost is *either* first packet loss or  sending the packet on the =20
ALT using it as a request for a  mapping.

> 2 - LISP-ALT's long-path problem
>     http://psg.com/lists/rrg/2008/msg01676.html
>       http://www.antd.nist.gov/~ksriram/strong_aggregation.png
>
>   [Fix? Another fundamental problem in the architecture.   Could
>       be partially solved by more meshiness,  but that would greatly
>       increase the  complexity of the network and so raise more
>        scaling problems.]

Well this I believe is a duplicate of 1 above. So  it's not really =20
*another* problem.

> 3 - Problems creating  a highly aggregated ALT network in order to
>    speed the  flow of packets up and down the hierarchy, while also
>     making the network robust against the failure of its routers and
>   tunnels.  This has not been discussed much on the RRG, but it  is
>    an obvious problem.

If we can do this with BGP,  which we have decades of existence proof =20
why can't we do this with a  tunnel topology 1) where a tunnel can be =20
rehomed much quicker and  easily than physical links and boxes we have =20
to do with today,  allowing aggregation to occur at the edges of the =20
ALT network, and  2) these tunnels stay up because there is robust =20
connectivity below  the tunnel level to keep them up, hence there will =20
be less  route-flaps for EID-prefixes.

I think it's the complete opposite of  what you claim. I think BGP will =20
be more stable and scalable then  the underlying BGP. Plus, what we =20
propose for the use-case of BGP  uses quite a few features of it. =20
Recall this is eBGP over  GRE.

We have an infrastructure where we can 1) ping to see liveness  of =20
nodes on the ALT. We have traceroute to determine the path a Map- =20
Request takes on the ALT. We can ping/traceroute "underneath" so we  =20
can see the diameter of the tunnel. Not only do we have a solution  but =20
we use existing rudimentary tools for management.

And the  address allocation hierarchy can map this logical ALT =20
topology. And  if the Registries are involved in managing part of this =20
ALT network  (which we hope and think they will), we can keep this =20
consistent  relationship.

Do you realize the goodness of this? It's huge  Robin.

There's more too, you then throw SIDR in the mix and we have  secured =20
the ALT, we have secured mappings, we created a PKI for  routing use. =20
In fact, the first SIDR deployment could happen on the  ALT to be =20
verified/experimented before it goes on the underlying  BGP.

And note, that the infrastructure will/does carry exactly 2  address-=20
families. So we can do 6-to-6-over-4 with this approach. That  means we =20
can get two site to be *IPv6-only* and be able to talk to  each other.

If you are a IPv6-only site now or a dual-stack site, you  could talk =20
to the new IPv6 Google services. I think this is a pretty  huge feature.

This is clean and architecturally pure, no double NATs,  no CGNS, and =20
no applications breaking.

> 4 - LISP-ALT's  Aggregation implies provider dependence.
>    This is  Christian Vogt's critique:
>     http://psg.com/lists/rrg/2008/msg00259.html

Not true. Aggregation here  is for the EID-prefix. Service providers do =20
not carry EID-prefixes  in their cores so you don't depend on them. The =20
decoupling of the  address creates this. The dependence is now on the =20
ALT. And if your  site resides in a specific region of the world, you =20
get your  EID-prefixes from that registry. So readdressing your domain =20
would  only occur if you moved it from one region to another (let's =20
leave  mobile ASes out of this for now).

> 5 - Path MTU Discovery  problems.  Despite Fred Templin, myself and
>    others  discussing the inherent PMTUD problems in any map-encap
>     proposal, there has been nothing from the LISP team to indicate
>   they have a solution.  They seem to think there is no  problem.

In section 5.4 of draft-farinacci-lisp-11.txt we describe two  proposed =20
solutions, one is stateless, and the other is stateful. The  stateful =20
creates no new table data structures but requires storing  an addition =20
2-bytes of effective-MTU state per mapping.

>  6 - Lack of business case for LISP's Proxy Tunnel Routers:
>   http://psg.com/lists/rrg/2008/msg02021.html

You cannot fault a  technical design for a business case. A PTR is =20
solving a technical  problem. And if we want to *truly* keep lots of PI =20
type routes out  of the core *and* avoid NAT solutions which are just =20
way too high in  opex, the PTR is the only solution we have to turn to.

And on the  contrary, I do believe service providers, interconnect =20
providers,  registries, third-parties and even governments will provide =20
PTR  services. Will they make a ton of money out of it, well that =20
remains  to be seen.

> 7 - The scaling problems of potentially thousands of  ITRs each
>    probing reachability to one ETR, and likewise,  one ITR probing
>    reachability to many ETRs - this is one  view of the "Locator Path
>    Liveness Problem" of  draft-meyer-loc-id-implications-00.
>     http://www.irtf.org/pipermail/rrg/2009-January/000809.html

That is not  in the LISP design. Everyone just thinks it is.  ;-)

Dave and  Darrel's draft is providing a warning about how bad probing =20
can be.  They do not take a position whether it should go into any =20
proposal.  They are just saying, beware of the Frankenstein that may =20
result and  can be an interpretation to not do probing at all.

Like I mentioned in  a previous RRG email message, one has to ask the =20
question if an ITR  *should* switch from one RLOC to another when there =20
*may* be a path  failure *somewhere in the middle of the network*. =20
Please note my  very fine qualifications.

If we want to solve this problem, we could do  this today by having a =20
host switch it's TCP connection to another A  record. This doesn't =20
happen today because people deal with packet  loss, since it doesn't =20
last long *and* rerouting actually works  quite well.

Van Jacobson always made this comment and I'll never forget  it, "The =20
fact that the Internet drops packets is it's greatest  feature".

What else can either an xTR or TCP host do when sending  ICMP =20
Unreachables are off by default in most modern routers, or they  are =20
filtered by firewalls, and route aggregation hides failures  close to =20
packet sources.

>> Unless these concerns are  adequately addressed, claiming that LISP
>> is an appropriate  solution to the problems discussed at the IAB's
>> October 2006  Routing and Addressing Workshop is nothing more than
>> a proof by an  emphatic assertion.
>
> I agree entirely.
>
> I  believe the LISP team could have made much better use of the RRG -
> by  participating fully in the debates resulting from these critiques.

We  were asked to do research in RRG. That was a reasonable request. So  =20
the research stuff in LISP has been and will continue to be  presented =20
in RRG.

As for the engineering issues, the real  details and bits and bytes, we =20
want a forum to discuss and work out  issues in an open forum. I've =20
been going to IETF for 20 years now,  that forum is called a working =20
group.

The working group  doesn't have to standardize what it is working on. =20
And the charter  and the numerous requests we have made requests *for =20
an experimental  working group*.

> Experiments won't help solve most of these  problems.  I am not
> against experimentation and I think it is  great that there is a LISP
> experimental network.
>
>  However, I would never have taken a proposal to the point of writing
>  code, running a network and inviting others to write compatible
>  implementations when the proposal had so many fundamental  problems.

There is constant implementation feedback back into the  design. =20
Experienced engineers know how this cycle works. You start  with =20
something you think can hold together, you try things out, you  refine, =20
you revisit design, you go forward with implementation.  That's the =20
process of *detailed* engineering.

For the old  timers, that was the difference between TCP/IP and OSI.

Sorry for the  long  email,
Dino

_______________________________________________
rrg  mailing  list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg





-------------------------------1232903992
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3DISO-8859-1">
<META content=3D"MSHTML 6.00.6000.16788" name=3DGENERATOR></HEAD>
<BODY id=3Drole_body style=3D"FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY:=20=
Arial"=20
bottomMargin=3D7 leftMargin=3D7 topMargin=3D7 rightMargin=3D7><FONT id=3Drol=
e_document=20
face=3DArial color=3D#000000 size=3D2>
<DIV>
<DIV>Dino,</DIV>
<DIV>Just a simple question: Is the ALT GRE-tunnel hierarchy a tree ?</DIV>
<DIV>&nbsp;</DIV>
<DIV>Heiner</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>In einer eMail vom 24.01.2009 20:51:53 Westeurop=E4ische Normalzeit sch=
reibt=20
dino@cisco.com:</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid"><=
FONT=20
  style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000=20
  size=3D2>&gt;&nbsp;&nbsp; LISP has too many fundamental problems to be=20
  considered a<BR>&gt;&nbsp;&nbsp; potentially practical solution.&nbsp; Som=
e of=20
  these problems require<BR><BR>LISP is not perfect and still evolving but l=
et=20
  me point out that every&nbsp; <BR>design has fundamental problems. At this=
=20
  scale, it's very hard to be&nbsp; <BR>perfect Robin. And as Noel has state=
d so=20
  many times, the hard&nbsp; <BR>decisions must be made to incrementally dep=
loy=20
  this. So things might&nbsp; <BR>not look pretty on the surface, but jeez,=20=
you=20
  got to do what you got&nbsp; <BR>to do. Else, this will all be=20
  academic.<BR><BR>We really want to solve this problem, sincerely. This is=20=
not=20
  lip&nbsp; <BR>service, we are not just writing papers, we want to rev the=20
  Internet,&nbsp; <BR>this is serious.<BR><BR>I want to address each of your=
 7=20
  points below. I have cc'ed the lisp@ietf.org <BR>&nbsp; mailing list so th=
e=20
  folks who want to focus on details of LISP can&nbsp; <BR>see this=20
  thread.<BR><BR>&gt; 1 - Delays in delivering initial packets in a flow.&nb=
sp;=20
  This is either<BR>&gt;&nbsp; &nbsp; due to sending the packets along the A=
LT=20
  network (which takes<BR>&gt;&nbsp; &nbsp; time and involves sending=20
  substantial volumes of data packets<BR>&gt;&nbsp; &nbsp; over the ALT netw=
ork,=20
  rather than just mapping requests) or to<BR>&gt;&nbsp; &nbsp; sending mapp=
ing=20
  requests only, and waiting for the ITR to get a<BR>&gt;&nbsp; &nbsp; respo=
nse=20
  before it attempts to send traffic packets.<BR><BR>We have a memory/bandwi=
dth=20
  tradeoff. So we have to make a hard design&nbsp; <BR>call. I'd rather have=
=20
  mappings cached and timed out so they can be&nbsp; <BR>updated when they n=
eed=20
  to then to hold all the possible mappings for&nbsp; <BR>the Internet in an=
=20
  ITR.<BR><BR>There is no such thing of a free lunch. You either store all=20
  possible&nbsp; <BR>mappings or you fetch them when you need=20
  them.<BR><BR>&gt;&nbsp; &nbsp; According to:=20
  http://www.lisp4.net/docs/lisp-ausnog02.ppt pp 10<BR>&gt;&nbsp; &nbsp; &am=
p;=20
  11 the experimental LISP ALT network's ITRs drop initial<BR>&gt;&nbsp; &nb=
sp;=20
  packets and send brief map request messages.&nbsp;&nbsp; Even if we=20
  think<BR>&gt;&nbsp; &nbsp; this delay doesn't matter, I am sure enough=20
  potential adopters<BR>&gt;&nbsp; &nbsp; would - and therefore make it=20
  difficult or impossible for LISP or<BR>&gt;&nbsp; &nbsp; any other such=20
  solution to be widely enough adopted to solve the<BR>&gt;&nbsp; &nbsp; rou=
ting=20
  scaling problem.<BR><BR>Then why was/is ARP deployed in a 10^4 host-based=20
  bridged network with&nbsp; <BR>basically the same properties. First packet=
=20
  loss is not persistent&nbsp; <BR>when you look at all the traffic that=20
  originates from a source site to&nbsp; <BR>another destination=20
  site.<BR><BR>The host vendors are probably thinking, if we do LISP in the=20
  host, you&nbsp; <BR>could wait to send your TCP SYN before the mapping is=20
  available. Guess&nbsp; <BR>what, you don't send that TCP SYN before you ge=
t=20
  the DNS Reply. ;-) I&nbsp; <BR>wonder why? Well I'll spell it out. If a ho=
st=20
  needs an address to make&nbsp; <BR>the connection, we can say it also need=
s a=20
  locator to make a connection.<BR><BR>The design choice of LISP *is to just=
=20
  change software in CPE devices*&nbsp; <BR>to get the feature of decoupling=
=20
  rather than changing all the hosts at&nbsp; <BR>a site. That's a huge=20
  deployment advantage. So these CPE devices get&nbsp; <BR>packets before th=
ey=20
  have mappings. We don't even want to consider a&nbsp; <BR>host to CPE rout=
er=20
  signaling protocol and all it's complexities to&nbsp; <BR>solve this and t=
o=20
  keep the architecture pure, we don't want to snoop&nbsp; <BR>on DNS, SIP,=20=
or=20
  any other protocol that can give us a hint on where&nbsp; <BR>the host is=20
  about to send a packet.<BR><BR>So the cost is *either* first packet loss o=
r=20
  sending the packet on the&nbsp; <BR>ALT using it as a request for a=20
  mapping.<BR><BR>&gt; 2 - LISP-ALT's long-path problem<BR>&gt;&nbsp; &nbsp;=
=20
  &nbsp; http://psg.com/lists/rrg/2008/msg01676.html<BR>&gt;&nbsp; &nbsp; &n=
bsp;=20
  http://www.antd.nist.gov/~ksriram/strong_aggregation.png<BR>&gt;<BR>&gt;&n=
bsp;=20
  &nbsp; &nbsp; [Fix? Another fundamental problem in the architecture.&nbsp;=
=20
  Could<BR>&gt;&nbsp; &nbsp; &nbsp;&nbsp; be partially solved by more meshin=
ess,=20
  but that would greatly<BR>&gt;&nbsp; &nbsp; &nbsp;&nbsp; increase the=20
  complexity of the network and so raise more<BR>&gt;&nbsp; &nbsp; &nbsp;&nb=
sp;=20
  scaling problems.]<BR><BR>Well this I believe is a duplicate of 1 above. S=
o=20
  it's not really&nbsp; <BR>*another* problem.<BR><BR>&gt; 3 - Problems crea=
ting=20
  a highly aggregated ALT network in order to<BR>&gt;&nbsp; &nbsp; speed the=
=20
  flow of packets up and down the hierarchy, while also<BR>&gt;&nbsp; &nbsp;=
=20
  making the network robust against the failure of its routers and<BR>&gt;&n=
bsp;=20
  &nbsp; tunnels.&nbsp; This has not been discussed much on the RRG, but it=20
  is<BR>&gt;&nbsp; &nbsp; an obvious problem.<BR><BR>If we can do this with=20=
BGP,=20
  which we have decades of existence proof&nbsp; <BR>why can't we do this wi=
th a=20
  tunnel topology 1) where a tunnel can be&nbsp; <BR>rehomed much quicker an=
d=20
  easily than physical links and boxes we have&nbsp; <BR>to do with today,=20
  allowing aggregation to occur at the edges of the&nbsp; <BR>ALT network, a=
nd=20
  2) these tunnels stay up because there is robust&nbsp; <BR>connectivity be=
low=20
  the tunnel level to keep them up, hence there will&nbsp; <BR>be less=20
  route-flaps for EID-prefixes.<BR><BR>I think it's the complete opposite of=
=20
  what you claim. I think BGP will&nbsp; <BR>be more stable and scalable the=
n=20
  the underlying BGP. Plus, what we&nbsp; <BR>propose for the use-case of BG=
P=20
  uses quite a few features of it.&nbsp; <BR>Recall this is eBGP over=20
  GRE.<BR><BR>We have an infrastructure where we can 1) ping to see liveness=
=20
  of&nbsp; <BR>nodes on the ALT. We have traceroute to determine the path a=20=
Map-=20
  <BR>Request takes on the ALT. We can ping/traceroute "underneath" so we&nb=
sp;=20
  <BR>can see the diameter of the tunnel. Not only do we have a solution=20
  but&nbsp; <BR>we use existing rudimentary tools for management.<BR><BR>And=
 the=20
  address allocation hierarchy can map this logical ALT&nbsp; <BR>topology.=20=
And=20
  if the Registries are involved in managing part of this&nbsp; <BR>ALT netw=
ork=20
  (which we hope and think they will), we can keep this&nbsp; <BR>consistent=
=20
  relationship.<BR><BR>Do you realize the goodness of this? It's huge=20
  Robin.<BR><BR>There's more too, you then throw SIDR in the mix and we have=
=20
  secured&nbsp; <BR>the ALT, we have secured mappings, we created a PKI for=20
  routing use.&nbsp; <BR>In fact, the first SIDR deployment could happen on=20=
the=20
  ALT to be&nbsp; <BR>verified/experimented before it goes on the underlying=
=20
  BGP.<BR><BR>And note, that the infrastructure will/does carry exactly 2=20
  address- <BR>families. So we can do 6-to-6-over-4 with this approach. That=
=20
  means we&nbsp; <BR>can get two site to be *IPv6-only* and be able to talk=20=
to=20
  each other.<BR><BR>If you are a IPv6-only site now or a dual-stack site, y=
ou=20
  could talk&nbsp; <BR>to the new IPv6 Google services. I think this is a pr=
etty=20
  huge feature.<BR><BR>This is clean and architecturally pure, no double NAT=
s,=20
  no CGNS, and&nbsp; <BR>no applications breaking.<BR><BR>&gt; 4 - LISP-ALT'=
s=20
  Aggregation implies provider dependence.<BR>&gt;&nbsp; &nbsp; This is=20
  Christian Vogt's critique:<BR>&gt;&nbsp; &nbsp;=20
  http://psg.com/lists/rrg/2008/msg00259.html<BR><BR>Not true. Aggregation h=
ere=20
  is for the EID-prefix. Service providers do&nbsp; <BR>not carry EID-prefix=
es=20
  in their cores so you don't depend on them. The&nbsp; <BR>decoupling of th=
e=20
  address creates this. The dependence is now on the&nbsp; <BR>ALT. And if y=
our=20
  site resides in a specific region of the world, you&nbsp; <BR>get your=20
  EID-prefixes from that registry. So readdressing your domain&nbsp; <BR>wou=
ld=20
  only occur if you moved it from one region to another (let's&nbsp; <BR>lea=
ve=20
  mobile ASes out of this for now).<BR><BR>&gt; 5 - Path MTU Discovery=20
  problems.&nbsp; Despite Fred Templin, myself and<BR>&gt;&nbsp; &nbsp; othe=
rs=20
  discussing the inherent PMTUD problems in any map-encap<BR>&gt;&nbsp; &nbs=
p;=20
  proposal, there has been nothing from the LISP team to indicate<BR>&gt;&nb=
sp;=20
  &nbsp; they have a solution.&nbsp; They seem to think there is no=20
  problem.<BR><BR>In section 5.4 of draft-farinacci-lisp-11.txt we describe=20=
two=20
  proposed&nbsp; <BR>solutions, one is stateless, and the other is stateful.=
 The=20
  stateful&nbsp; <BR>creates no new table data structures but requires stori=
ng=20
  an addition&nbsp; <BR>2-bytes of effective-MTU state per mapping.<BR><BR>&=
gt;=20
  6 - Lack of business case for LISP's Proxy Tunnel Routers:<BR>&gt;&nbsp;=20
  &nbsp; http://psg.com/lists/rrg/2008/msg02021.html<BR><BR>You cannot fault=
 a=20
  technical design for a business case. A PTR is&nbsp; <BR>solving a technic=
al=20
  problem. And if we want to *truly* keep lots of PI&nbsp; <BR>type routes o=
ut=20
  of the core *and* avoid NAT solutions which are just&nbsp; <BR>way too hig=
h in=20
  opex, the PTR is the only solution we have to turn to.<BR><BR>And on the=20
  contrary, I do believe service providers, interconnect&nbsp; <BR>providers=
,=20
  registries, third-parties and even governments will provide&nbsp; <BR>PTR=20
  services. Will they make a ton of money out of it, well that&nbsp; <BR>rem=
ains=20
  to be seen.<BR><BR>&gt; 7 - The scaling problems of potentially thousands=20=
of=20
  ITRs each<BR>&gt;&nbsp; &nbsp; probing reachability to one ETR, and likewi=
se,=20
  one ITR probing<BR>&gt;&nbsp; &nbsp; reachability to many ETRs - this is o=
ne=20
  view of the "Locator Path<BR>&gt;&nbsp; &nbsp; Liveness Problem" of=20
  draft-meyer-loc-id-implications-00.<BR>&gt;&nbsp; &nbsp;=20
  http://www.irtf.org/pipermail/rrg/2009-January/000809.html<BR><BR>That is=20=
not=20
  in the LISP design. Everyone just thinks it is.&nbsp; ;-)<BR><BR>Dave and=20
  Darrel's draft is providing a warning about how bad probing&nbsp; <BR>can=20=
be.=20
  They do not take a position whether it should go into any&nbsp; <BR>propos=
al.=20
  They are just saying, beware of the Frankenstein that may&nbsp; <BR>result=
 and=20
  can be an interpretation to not do probing at all.<BR><BR>Like I mentioned=
 in=20
  a previous RRG email message, one has to ask the&nbsp; <BR>question if an=20=
ITR=20
  *should* switch from one RLOC to another when there&nbsp; <BR>*may* be a p=
ath=20
  failure *somewhere in the middle of the network*.&nbsp; <BR>Please note my=
=20
  very fine qualifications.<BR><BR>If we want to solve this problem, we coul=
d do=20
  this today by having a&nbsp; <BR>host switch it's TCP connection to anothe=
r A=20
  record. This doesn't&nbsp; <BR>happen today because people deal with packe=
t=20
  loss, since it doesn't&nbsp; <BR>last long *and* rerouting actually works=20
  quite well.<BR><BR>Van Jacobson always made this comment and I'll never fo=
rget=20
  it, "The&nbsp; <BR>fact that the Internet drops packets is it's greatest=20
  feature".<BR><BR>What else can either an xTR or TCP host do when sending=20
  ICMP&nbsp; <BR>Unreachables are off by default in most modern routers, or=20=
they=20
  are&nbsp; <BR>filtered by firewalls, and route aggregation hides failures=20
  close to&nbsp; <BR>packet sources.<BR><BR>&gt;&gt; Unless these concerns a=
re=20
  adequately addressed, claiming that LISP<BR>&gt;&gt; is an appropriate=20
  solution to the problems discussed at the IAB's<BR>&gt;&gt; October 2006=20
  Routing and Addressing Workshop is nothing more than<BR>&gt;&gt; a proof b=
y an=20
  emphatic assertion.<BR>&gt;<BR>&gt; I agree entirely.<BR>&gt;<BR>&gt; I=20
  believe the LISP team could have made much better use of the RRG -<BR>&gt;=
 by=20
  participating fully in the debates resulting from these critiques.<BR><BR>=
We=20
  were asked to do research in RRG. That was a reasonable request. So&nbsp;=20
  <BR>the research stuff in LISP has been and will continue to be=20
  presented&nbsp; <BR>in RRG.<BR><BR>As for the engineering issues, the real=
=20
  details and bits and bytes, we&nbsp; <BR>want a forum to discuss and work=20=
out=20
  issues in an open forum. I've&nbsp; <BR>been going to IETF for 20 years no=
w,=20
  that forum is called a working&nbsp; <BR>group.<BR><BR>The working group=20
  doesn't have to standardize what it is working on.&nbsp; <BR>And the chart=
er=20
  and the numerous requests we have made requests *for&nbsp; <BR>an experime=
ntal=20
  working group*.<BR><BR>&gt; Experiments won't help solve most of these=20
  problems.&nbsp; I am not<BR>&gt; against experimentation and I think it is=
=20
  great that there is a LISP<BR>&gt; experimental network.<BR>&gt;<BR>&gt;=20
  However, I would never have taken a proposal to the point of writing<BR>&g=
t;=20
  code, running a network and inviting others to write compatible<BR>&gt;=20
  implementations when the proposal had so many fundamental=20
  problems.<BR><BR>There is constant implementation feedback back into the=20
  design.&nbsp; <BR>Experienced engineers know how this cycle works. You sta=
rt=20
  with&nbsp; <BR>something you think can hold together, you try things out,=20=
you=20
  refine,&nbsp; <BR>you revisit design, you go forward with implementation.=20
  That's the&nbsp; <BR>process of *detailed* engineering.<BR><BR>For the old=
=20
  timers, that was the difference between TCP/IP and OSI.<BR><BR>Sorry for t=
he=20
  long=20
  email,<BR>Dino<BR><BR>_______________________________________________<BR>r=
rg=20
  mailing=20
  list<BR>rrg@irtf.org<BR>http://www.irtf.org/mailman/listinfo/rrg<BR></FONT=
></BLOCKQUOTE></DIV>
<DIV></DIV>
<DIV>&nbsp;</DIV></FONT></BODY></HTML>

-------------------------------1232903992--

--===============1845881207==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

--===============1845881207==--

From rrg-bounces@irtf.org  Sun Jan 25 10:02:24 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2F76E3A6B57; Sun, 25 Jan 2009 10:02:24 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 275803A6B57 for <rrg@core3.amsl.com>; Sun, 25 Jan 2009 10:02:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.319
X-Spam-Level: 
X-Spam-Status: No, score=-6.319 tagged_above=-999 required=5 tests=[AWL=-0.280, BAYES_00=-2.599, DC_IMAGE_SPAM_HTML=0.001, DC_IMAGE_SPAM_TEXT=0.001, DC_PNG_UNO_LARGO=0.558, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TAUsY4CBPYLJ for <rrg@core3.amsl.com>; Sun, 25 Jan 2009 10:02:22 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id E51033A6954 for <rrg@irtf.org>; Sun, 25 Jan 2009 10:02:20 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,322,1231113600";  d="png'150?scan'150,208,150";a="34829119"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-1.cisco.com with ESMTP; 25 Jan 2009 18:02:00 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n0PI200t017598;  Sun, 25 Jan 2009 13:02:00 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n0PI20Rt016777; Sun, 25 Jan 2009 18:02:00 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Sun, 25 Jan 2009 13:02:00 -0500
Received: from dino-macbook.dhcp.nanog.merit.net ([10.82.244.143]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Sun, 25 Jan 2009 13:01:59 -0500
Message-Id: <DB97368A-351D-402E-9BC4-7A4F4030893E@cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: HeinerHummel@aol.com
In-Reply-To: <cea.4cba28ba.36adf938@aol.com>
Content-Type: multipart/mixed; boundary=Apple-Mail-18--951548461
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Sun, 25 Jan 2009 09:56:45 -0800
References: <cea.4cba28ba.36adf938@aol.com>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 25 Jan 2009 18:01:59.0919 (UTC) FILETIME=[04DABFF0:01C97F17]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=88046; t=1232906520; x=1233770520; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dino@cisco.com; z=From:=20Dino=20Farinacci=20<dino@cisco.com> |Subject:=20Re=3A=20[rrg]=20[Int-area]=20Please=20respond=3 A=20Questions=20from=20the=20IESG=20as=20to=20whether=20a=20 ... |Sender:=20 |To:=20HeinerHummel@aol.com; bh=EY9if89uBex2McRXOcWe0778CxA0ci7uFn4cvM043Rc=; b=iXj+XoSik5UD/K5resr5rQMYUp1nSiZf95+mdsRe6IyisdUjGqLKyRiEvP 58YDHK5i/qBc6e3spo6wRPBZvW2/48LYZdtOvHe0TScXKP6tLajhF3Od9HYQ WM6+wRZ1Dc;
Authentication-Results: rtp-dkim-2; header.From=dino@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; ); 
Cc: rrg@irtf.org, int-area@ietf.org, rw@firstpr.com.au, routing-discussion@ietf.org, lisp@ietf.org
Subject: Re: [rrg] [Int-area] Please respond: Questions from the IESG as to whether a ...
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

--Apple-Mail-18--951548461
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

> Just a simple question: Is the ALT GRE-tunnel hierarchy a tree ?

It is not required, but it should follow the address allocation  
delegation.

What we have deployed on the pilot is in the enclosed diagram and the  
EID-prefix assignments follow a registry allocation hierarchy. This  
topology supports both IPv4 and IPv6.

Once the apnic box is up, the container with ntt, dscott, and iij will  
connect to it.

Dino


--Apple-Mail-18--951548461
Content-Disposition: inline;
	filename="Picture 1.png"
Content-Type: image/png;
	x-mac-hide-extension=yes;
	x-unix-mode=0644;
	x-mac-type=504E4766;
	name="Picture 1.png"
Content-Transfer-Encoding: base64

iVBORw0KGgoAAAANSUhEUgAAAoAAAAHgCAIAAAC6s0uzAAAABGdBTUEAANkDQtZPoQAADzdpQ0NQ
Q29sb3IgTENEAAB4nJWXCThU3/vAz3Dt+zZ2xpJ9GYw969j37CSMGctYxjT2JUuhREkLKiJ9SQtS
EkpChUpRRFnKmgqJLCn53aG+3//z+z2/5/f8z/PcuZ/7nve877nnPXPf8wLAJYIjk8NpAAARpGiK
s6UpytPLG8XwBiAABPiAGBDB4aPIJk5OduC/ttXXsDbcXilTbdVanTila3yRCfLJN1fSOjH538dt
N3YK7BAAhBLMvME7bEzlgB12pXJcNDka5hAq40NwBJiTYVaiuDpjYa6i2gne4UYqB+xwF5Vj8cHU
sUMA0HOTCEQSAAxzMBsSAqPwcDfVL4EQhY+A+QQANIYREZGwfc5eWC6HJ1PgsZzrMEtT12VnyoQ1
APQg2Mbbf2ShEgBU3wZAROIfmex9AARwANxQ+Ee27Ly9Vgjki6ggDfVtEYLVFAC6sa2tZRl4bicB
2Mzf2vpRvrW1eQkA2hEAHoTjYyixv9cLgegB4H8977zz70YLO4QDTKNK6wCF0B2gP8twg7GdaYj5
M8sSGzM7P4cEpzKXHrcJjx2vK58H0pcfL0AUJAtFCUeLxIjGiyWJp6EyJDIkD0sdlT6+64zMedky
uSr5WoVGxU6lAeVxlVU0s5qkuoaGGyZJs0zrifa6rrweTv/87lFDcSOi8R1TVuw+s1sW3JYUqz4b
Vdtjdl8d7Bxr9nA4h7s8cRN2D/e478Xu7be3yuebL9bvqH9PAAfekXAy8EUwc4gJMSa0Jmw8godk
FhlHvr7/bRQUjY7xi82Nuxc/m8iVZJhMPlCa0pk6kjaRPn1w7tBixlLmatbmESib9ShXDl+u6DG5
4xp5+idM8q1O7jnlftr7jG8BvpBYFHY27BzxPLE4tCTkAq7Uu8zlom258SW1v+QrZCt3XZasQl0R
vSp4je86VzVnDWstXe2vG+t1yzfnb03XD9/ua3h2p6Oxqamu+frdK/cuthTcP9569EFGW3p7Ygfl
IekR6XF4J64L243snnhy82nqM5se/p6Z5/UvMnqd+8T75l8+eJXf7zegPLDx+ulg4RDujfKb728f
D+eNuI+Kjk6NVb+jvNd6/328eSJpUm9ydaphOnnG5APth+7Z3I8Onzg/vfpcOOc5LzA/tFD0xXNR
YHHga/6SwzLbcve3jBWTla3V+2uJ65rri9+rN8J+yP+Y+Vm+6f9L/Nfbrf1bW3D8IVpuCEnHS8/H
wMHIwsTItMn8neUL6xTbG/YejjbOOq5y7tM8mbxxfGHIffyOAlhBXSEtYSURVVEVMS1xQ5S5hJGk
jpSytNIuJRkFWbSckjxaQUsRq2Sj7KlCVE1AZ6uVqDdovMAsaHFpY3RcdBP1LusPGjAaahrtN642
mcUqmoWZ11qsW5lb59gM2anZJzv0OQnvCXZucEW42buf9Bjxkvcm773ps+ar43fAvxW3idcnxAbe
CVoOUSGGhl4N+xQhQ/KJLCK/pvBEuUbnxzyJY4y3Szie+ChpMvnzgS8pK6nf0zbSfx2iy2DN5MkS
PCx6RDobfVQvxzTX+pjjcc88nxP++YSToaciT5PPUAoiC0lF5LMR54LO+xd7ljhdMC/VKlO+qFyu
dEke3gdylTKXpaukrkhflbomfl2kWqhGsFbgBl8d902OWxz17LfZGtjucDUimwSaBe4K30O1yN5X
adV8oNtm2u7Q4f1w7yPLx6jHS53dXcXdEU9MnvI/nX/2qOfs84gX2F7R3tW+npflr+L6HQYkB1Ze
dw8WD0W+MXnL9XZ0+PpI8qjVGNfY8Lvy96HjKuOLE42TJ6ZCpo1m+GfmPzycPfuR9Mn8s+DnT3P3
5o8t7Pui8uXHYufXk0u+y/LLS9/urmStOq0JrI2sl38nbqA31n/c+5m2af6L/deLrYid+NOs0S5C
3+i+0M8zzDPOM40xD7P0sz5la2Gv4SjlzOGK4ybA3wA0HwffMrKP/5pAhqCPEFqYTnhQpEI0Rsxc
nEN8FFUhESGpJ0Uv9Vr6yq4UGTdZJTlGuQ/ynQpViseUopX3qpiqqqBF1JjU1tSnNfowDzRvaJVo
Z+vE6uL07PR370YZ0BssGg4Y3TY+ZRJrSsR6mFmY61jIWApY0VmtWn+0eWPbZddgX+lQ5JjtFA/v
DXcXO1d9NyV3cQ+kJ5sXjdc37497J3ze7uv37fHr8L+Pawloxt8kXArMDqIE+4VYEVVDhcIYwlbC
pyL6SPcja8jl+wsoR6Lio0NifGMd4gzjVRMkEnmToKTl5PcHnqfcT72Wdjo99WDQIccMTCYyC5G1
dnj+yGT226O9OZ25zcdqj1flFZ/IyU89ST5FOO12xqIAUyhdxHeW7uy3c9Pnh4p7Su5fuF5aUnbq
YmZ58qXIv3AVHpV7LltX6V+RvAqujly7d72omlLjWKtyg/3GQl3PzSu3cuojb7s0aN5B3llrHGlq
aS65m3IP14K9v6uVrnXyQUdbZXtGB+6hwSOhR6uPezsrunK6i5+0PZ14tvVc6IVur3df8sviV139
869FBh2Hct48G+YZ8R9tesfzPnX822T6NPvM5VmnT1yfX8/XfCn4mr9cslK3NrOB+un/K4Ua/53c
R230WgAUxQDgOQ6AcwUAeZtwqmMFAAnnUSc2AFx1AaI9DyCuZQKEad6f/AGov4yACz4TKAMj4ArC
QRa4BB6CaQQzQh3hgziCaER8pBGlcaM5TvOElpHWijaHtg8SgghQHbRF50h3ie47vRP9VQaIAcfw
gFGC8RDjLJM9Ux2zEHMG8xyLB0s7qzprCRsDWwzbBLsjewuHIkcRJwNnFOc4lxNXC7cidxEPHU8M
zzSvC28bH5qvDMmNzER+5w/nfy/gJfBC0FLwgdBuoQZhLeFmEUORdlEr0V4xT7FpcYr4FipXQkzi
lqS15LhUkjSvdN0up11LMoWyhrKTcrnyuvIzCmcUzRSXlSqVfVUEVHpVs9HmakCtRT1VwxRDi2nX
zNSy0xbTodFZ0B3Ua9e/tbvC4LRhplGccagJ3nQf1sXMytzUwsjS2MrY2tjG0tbJzts+0IHseMip
cE+dc7fLuBvCXdbD3jPOq9x70Idjn54v3u+0fztuGS9L8A0sDOoJoSdahmaH9URwktwjy8hfKCZR
OdHvYjFx2fEjicpJh5NnU8xSS9J+HHQ/1JQpnpVy+G220dHbuT7HRfIG8s+eCjgjVfCpqOZcSrH9
BZ7S8YsNl/IrCJetrqhc473+o2bhxoebU/VjDbONK3dZW6RaHdoiO1IflXU2d489Y3iO7vV8eaK/
a5D+DXY4Z3TkvcxE8tTAB4WPBz5PLtgsXllmWYlam9qw+HmPun+oJwnADJ8JpYEWsAOBIB1cBB3g
I4IbYYiIQJQiBmjYaKxosmge0zLROtIW0o5DilAi1EknQBdC10zPTk+k72SQZ8hm+MzoxFjPJMZ0
mOkrszdzF4smSzkrN+sh1lW2YLa3cOTbODQ5rnJKcZ7j4uQ6zPWLO5Z7iYfIM867l/c1nwPfE6QF
so3fgL9RQFvgjqCGYI2QmlCtsJpwIxz1DlFb0QExP7EF8WQUE6pIQkHigaSb5JxUlrSYdNMu912r
cNT1ZYfl0uRl5V8oxCuiFLuUopQllPtVMlQ1VKfQhWpWaptwFiNhpDFDmie07LWR2qs6E7pP9Rr0
L+8+Z5BtmGgUbuxn4mG6B2tlZmCubYGxxFhpWWvaGNha2DnZezsEOSY45e6pdG51GXRdcxf1MPWM
8CryfuZDtw/t6+F32L8eN4HnJVgFpgTVBc8QpUJxYaXhYySRSD9yxf6FKPXohJiHcezx7gnFidPJ
WgeyUl6miaeHH2zKYMvEZdUc3si2P3oTzmebeVX5vqcETz8rOFSkfXblfEMJqVSubLb8xl9xlcZV
PFc+XLtXfaY2ti7glu1trTtqTSp3MS0GrZ5thA6TR2qdQt2sTzafrT9f6P348lv/z0GWN0LDmFGP
d0nj5ZOvZqBZzKewufqFta8Gy+krL9flNyg/+/+OPwvgBzJAFziCEJABKkAnmEcgEVhEFKISMUbD
D//3C2nGaGVoo2kfQyJQHDRAp0NXRs9MnwTnnBCGCUZ/xjGmfXDmCWCeZiGyLLLGsW6xZbMj2cs5
VDlaOfdwTnMd4OblruGx55nnzefT5htB5vLv5p8T+EswQEhaaED4uIiVKEL0gViKuCkKQnVKnJDc
KyUntSLdsatAJkwWK4eU+yr/TOGyYrqSj7KhiqQqreo0ulutWr1QIx0TpOmgtVtbTUdb10DPWN96
t4cBzjDMKNb4kMkZ08vYW2bt5gMWn60gawEbTVtXuyj7kw71jsN76J0xLn6ueW7dHghPE69U704f
vn12vil+jf4LAfJ4AqEycDZYJiSc2BwGhbtGXCR9I9vur6RsRXvFNMUJxsclvEzCJJem0KeGpPUe
xBwqzWTPij08nG15tC3X/dhaXn6+xsnR06kFkoWPzoadFy5uu4AvY7nYdCm0greyqyrtqta1ueqK
WkKd/M2F+uqGhEbbZrG7Sy3PW++0JbTPPnR4dK8T3XX1idjTUz30zxNeLPd5vXzerzNQOgiGvN7c
GIZG3EYvjI29lx73mTg2eXdqaHrlA++s4kfjTw6fnecc5+0XbL4YLap/RS0xL31Z7vtWs5K7Slwz
XedcH/t+fSPxh/VP/p+jmyW/Oqjx36mXthszNjI8koKyw5r9j+Lu/9siwmP++OCGL1ZSgIPjb54l
RztRa0EkfG1ExbqYw3dOuNzhDCJaWP9mFAFnZguzCMzoxBCsA9UGzHZBFAvnHTsIz1CcjRPM7DCH
BpLcXH7L48nh2zUulY+So02p+gIwFwdGmf/RqU8McfX4PfYxJcbZDWZpmPvDIm2df/taJwSa/Z4b
DUQKd7DbmTMNLzHaeruWhVkBWAAcoIBg+CuqDH9LscDs9y8KlqNgioR7A0EUrDe1rfdHy337mfhv
o5RB0La92O0xYWAG5gg/4kEKbGtHoxvgYRkOkP5I0NfQH9E//+6negzf9vpHYvsfkj8z/EeXCAjw
/Y8c/0dO9RxxMyi2KDJBzz0EkoHUIU3IFDKADCFdgIKQkBBQhjCQDmQCGUH6cJ/u87k7c3/72Vmb
gL/f0Ra2GghitleE9B/rhf8/swE7tfv2GQde/2J/KrWuJ6X9+z6LDozfro+xkeQECjE4JBplQiaH
ByqhrEl4FSWUOhqtC/4FWOROX0OR2JYAAAAJcEhZcwAACxMAAAsTAQCanBgAAAAkdEVYdFNvZnR3
YXJlAFF1aWNrVGltZSA3LjUuNSAoTWFjIE9TIFgpAAw8WR8AAAAHdElNRQfZARkRNR6sTuBwAAAg
AElEQVR4nOydBXwURxuHd881ubu4GxCBhCjuEopr8fIhpbi7eylerGiLU4q7uzvBAiHudvHz29v7
Zm/DEUISLOTuknnaX9idlXtndmb+78zOzKJarRaBQCAQCARSsVAMbQAEAoFAIFURKMAQCAQCgRgA
KMAQCAQCgRgAKMAQCAQCgRgAKMAQCAQCgRgAKMAQCAQCgRgAKMAQyEdI8vPF4iypQmNYM5QymVgs
zpMoDWtGBRD//OqZexFwNiSkCoLCecCQysHTY392Grlm1qG7Ixo5FAaps+cOGR0uUeDA06TQGEwm
y8pi2IiZdT2tyeMPLh07cOBUHsf8p5+6d2/XiIoiw5rV3n7rFThEY7BCO/f65+9NVlzml/z632vm
5bKaTRrRnNwd0qXxjWib+08OWTJQMuTEgkkrLz82Fwo4LCaC44RJVCqTwaSZOy5btcSaiRa924W1
I9pN3EpuBzRstXzD9hZ+Tt+VOqqMCf2GUwNDV8wYjn7+7BJ4fXrFsKUnzYQWXA4D0RIA+xnAfip1
zvINHtbcb7MLlybaCNyyNHiaVG3Npn7bTSAQU0ULgVQKjs4ZCaRl7O5wfQiW88aZWryPp3P/LTg4
Jk/p26Q6BS0UIxRFBZ3Xq3Ft6wBHROgxauyYut6Eijs16pmn0nz2px9vXwJuZe7fRokXhtTzskOQ
WtHSD9duG9ezNOU79K6g2A13TmyOUGj9ho/t1NQfnGDuUis6X/U9iaPOuGdPQas166fBP39yiTz8
Z2Rp8vjX6TffblheDE33jNKl6m++CQRiokABhlQSjs4tLsCAnIzU+KiXVKKKF+47efLw4cNvknNx
TDqwNqEmXsGNVm7dd3jv38O7dN56IRKc37K2I+LdXaHVqiSZpDC8TJOV/bvq/NiaDrr2H88rWlGo
uKQAx0o/Em+lrCA5KXnP8sHg3DHbL8RFRzx58Oj5m6hPNXH7mGYInf08JQ9s/9a7BTh/y8MM8pBc
UlBQIFFjxe4sBYFKNVa4r1GriG1cJsnPysrGdT/wLuxhXDqIu+r54wdx2QqFJDc2NjZbIi96Hw1B
qRKtkktTExMOL+wO/JY6I7bHRkeFPbgf9uSFXPezuEYjk8kVqkIb5HkZ5y5dV+FatUpZzFq1SiGX
y8kfAqlHo1GLCjCwnTj6ya8Dy95v4gqFosgRXC5XfHI6BGICQAGGVBJKFGCALDOWSgFHWmar8I9D
kKuvEnLz8gok0vcKkRdgjVK9ugPJlWXFeeoEODKnzKYnjk3zcNY3bbeHicngEgWY5OW57eD8VrNP
ld4WVU4KpiI0dlhyHqaSTe9OdGsfjCjAcdXBP36lUQloDtV3X32hOxk7v3UGTRdKE9qsPn4fyO2y
ZnVotHrTRnQhT5556pUq8QKdRhs49lBO3FPgWFCpXva2fAqFQnWol6DTT0W+eMPsETQdvcauycwv
VdKSrmwGzf3ARjOK2p+V/KZrkCt5+bkX8eDQuvlDEBTlsGgsBhG46exjnBBp9eNLu3lsIiiozaDE
fPnHAqx5c/uwK52uu02XWLGEuLVG/fbB+bYhukAP/+PXw69sn0KnWR57k0v+dNix5eDY2ktxZT0m
CMQogQIMqSSUJsBycbyuLdsy570AY9J0XZuY6HmmEFCpIvu78UB2pUH2KFqt1v96tyCbv0iHZSq8
rE5b8fPdKNGP3Wjj4L7gH7/pJ8lwUoCjShLgiIt7CHdgVhkCrJ7WGAgwfdDIX63Mdf2+NVrna/CL
i1oU7fgVuAdiGvzhum5oka5tGouXK1M3CanxUR9xw+VvjswBp/UZsTU/8SXpfOgZvPmJPCdBxKUX
DXRwHYuVYl/q3Z0UykcCrMl97UQr0j+NUu7FFayY0fcjG1D0Ulz+lV2Liv62f8fBqrwPAvz6yNyi
tlEog4DTsWnaoI+77tGBnYik5ls56prQyhbexOUrLseX8ZggEOMEjoKGVBLUOPE3KNDhcyciVI51
gTjxyJ71gwb0bxcaaolrNNkpjatbvYyPyMxEtFGvdh24CrSt08gVWf9NoKOoPOV5h5CQIB2BgYGT
1x8mBy6qCjKDmgzSOmsFDSyOvLgMAgtOriQPaREN4uNpyyrhta+ZnSVQmSt3n2pKG/6IScPCtAim
3vHX9sw8jVe99s/PHaDnxP08/zo4uGLxtGp2IrDBY9G1mLL7nPPAjZ45b14NZxsialQKcB3IG7f9
eV1azBNC0tztGFRgCjCGLitIR3TjLmdvuxp1YRU4+C425vD0xtlS9c/TlufJlK/PrQGBaE13pJRX
1kJnF6CCefKb+pADcxcnYZqgRrOzCyQHpnZAtPiVK0+qCWyJhv7oDak5+ZtH1EK12tOnb/054Xct
wtly6nV+TlpTH7uwi3cT5bj+Pks2HAGaOmv7RUleeh0qBcd3PHh4Y9aGXVoLj+vvkjUarF5NV5C0
/ZYu6u5LKchM6fzX05d7J157i7vU6zuq2fcNUoNADAHN0AZAIOXDy9xELdH6wks7Qa93GrVcSbft
1n90135EmEYpmdfZ//eLibGZOQiGNOs3avn4QRZ2Tm721mTjMins2rknj/H312uqheOjESqKbxkV
GJ+nQfKQ3NQTV1XEIXFuKmg40iny/KxMxBwtUWG1pLDJSo8JqtHKECaHd+7iFWsbm+quTgwaRZqa
JgX3c7CfOmcZENBBY+dMmToJRXCJBkPsrJYuXAi86R6DJ02fPYPLIL1qrz//HmHDRd6+eilyqZF/
eSUIMvevrsULdEfrj+3XJHz7Tp0l6odnk8G/E3771YzNSIrNAPf3bRFS+ojk4tF6kJICggYsHSnk
cVt1bYkuP61SqNg0om5xCWhqK+C3atkZ2fw67e6Nu7lKnpV9n1AvPoPi4OaAhGcrP8zCUCQnxCHC
oDEDWnLp2m4BlIeP8azIiFy5tn6jzk2q24NkK5AC453dnF1mrdp+OHTw6TFd35kTr8mHjx7Ppn7b
4G4IxJDAFjCkkgDasUBiHIQssC3Nybx+8cSx848wTCWR5OuOpz98/OTR0zCZKq+vq7mFmXe0WIai
qEYtu37hyMkrcQgxL4ioxM1t7UKCg9wdrPVdu9XbjsvNzhZniMXinLy8gicHZoMTFelvf9+fglLp
6/Yce/70TXJy/P/qWBSkpN3JVBCtcRyxdhAxgFU4lhoXfmjzpqgM0gyEwTQj/klLx8qcAEihUgND
gmtWcwHqC3a1xBtUBElJ/annwndJWatmDHx46kiWGif0KzWzTptxL2PTd66c9PbMfykyte4GVDa4
kEKr5l1TxCnsXtYqcaVUCi5xGTnKkk0VWtiBQCxPrNI5FwoVhknSt+85Anaa+ruUZhiVbW6NIErV
B/NtmDzwN+l5LK5RrVm3F4SbW1qSh1RqYh7ziePHQLOb5+MDGumYQpWar5aLI1+8ikSE1kK6XjgZ
fIEQUYnfJeWpCtJ3hhGOlMicUHE1Jge2R93anhCfjVgFWrAo/s1/Hhhki2gT3uXm8dzbDe0R/Pn8
AYEYIYbuA4dAyodx3euA/Czq+HNtd3cqhQLEFbVp2rYaDWyTWZ0IQSkT99/5xY2QQAqF6h8SIKJS
dS9xkRr12uRmPXdC0c6TFn/Jz93auhhcxqvZXKYufBl6ZNNEECL4dZ9G/s6RgSKoRbcuofZU8PvE
i83fNp0gz8uJeax709klv7S3rFhWSyqFzTfPVX54haxR5jb1ddSZbdeoYR0qMBth/huR3amRly7Q
omGjerpAyuZHiY2Jd8A1E2QfLo85vgikSJ8R2+OeHgXJ4T38IPjt1Ac7gGk+dXtcWt4dBFLs/Ku5
FXbkbnuRXVrENXkv3SgUS88Q/XDpdxcWs3Vp6+SkazbbeUXlKM+vmooSHRIUFxcqkcBs20tvM1cO
qYnofAsWi3goP41brMqL0b8DXjyhF3EJl0c+Mq9Oy5UF8QG2ZuDJNevUsfD1sG8/me53xZFXSele
vOvalzwvCMQIgQIMqSTMG9aGVFkOl2dhae3o7Lzp2Nn/OTnZ2ds7OTm76AgKbf4kqaAgM9rd1clC
JACILCwdHJ3mrPlPNysmJ9Tfafrqg1/ycy8PbnFyrHEn5cNoYVVujKuzY5dVt3AspSaPqVMappm5
wMbW3qV5n3dp+YWnFaS5u7lO332n9Hsr5rZz8fTpKvtYoTGVfHQtbzsbaxsbG3sHx2HL9wOTQbt/
Ydvm9rZEqJ29Q6dJ61QY3qV1iLkwKLHIXJ6c14ecHB1n7Hskjrxpa2XZbPEVLTE5+L6VSBDcsiOm
VizoVsvaytLK2tacz3FCBA8ysOJG6cELRnRw7TTxQBHj8AsrZ4LbWohENnaOz5IJ8SYFmMI2EwqF
1jZ26y6+In5Rmvmrm4tIKBIIRU36Ty8AEcDyOzs72No3y1fhOC6fNaidpUgEDjs698ySEROTkp6d
c3a0s7CwtHewp1FcvLrPIEfFpb8+Tag0NyBFUrqpEIhxA1fCglQSNGpVTl4+EGA6g8lkMOgMOmjz
4bgG1NcUXTP3o5eExFxSYtkM0EQDp1Lfr9eh6+eloF/2PhGIH7jzRyG4BtV1ZMsLcqVKjEKhM1l0
whT6x4MtQKEr8zd0pRIt6RQtplbrFvai0j78NAjEdHZTyNYkplKoNCiH/dEaXhqdtSiiVSmVNAZL
157UKmRyhMpgMYF5IFwFkmN699p/ns55LUny4X7VulRalUoFEptKZ9J1feYXVk9rO2l5/y1PN/f3
otFBEtDeR41IeRA9FpOl6xoAyYhptBTyKvBclMRzQZhstn5ANE5Ma9bQZM8srBp6/zL/3o65KIot
68iffloxaf+NFX2awNe/EBMFDsKCVBKodIbl+1ePeoBQUUoc54BSWGx2CcHoV4yKKKa+5M+RG2y+
gM0v/crPKXyJ2kseodEZJQV+NIkI6OunBZtaaC3KYLL0F7I4HKDXmwcGrH+sYbEYygJx+Lt4h1p1
PDlfOzoEZTBKWLOTQaFxOB+lM0hh9scpD3yJDz+GUphFjsoS79RrN4yIHoWS8PZZPq7t2qYVgiLK
jOj5pxXghBGhwVB9IaYLFGAIpMqjsAh/fYXcdK/Zbut/26lf2AlQOgwK4SgIbXjfcxMKlSnLCI/O
KOylGz5z08ju9YBluekxhPz+tNpZxPlOOyEQAwK7oCGQqo4WxyUFuVK5ksJgWwjMi63U8W3gSsnL
8Bgffz/6990MUylycnI1GpxnYc1l0gpvptXERLwWVvMV0mADGGLCQAGGQBC1Iv/hk4T6DWoB6Ul8
9zpTRQms5Q2q+eiHDzjuvnaWJXzqR4vJHj57UzckqGigskD8OEnT0Nvmy386Jzkmm2nnYVnY76pV
Fzx8FV8noFYxYUmKeCGo5ssj3i9rwp89Tc1RePoFOFp+aF9Kc9IfPXtJEzo18Pd8L6Da+FdhFl7+
vI9VKjPmBd3BR6B775sS8ep1YoZzDV9PZ2t9zGLCbiXm6aoFNrtGNW87ER/HVC+f3HqXkG0ucqnX
IICmSHv8IqZIxcGr1ziIWdiPrHn74H5ivqJ6TX9Xewstrnl7716qEqtdp54FjwWEM+Hd63cJYs+A
Ok6WPK1GFR72JC1P7RtSx5rPQiCQqoZhx4BBIMaAJPUdx0wgJpYjxge09rHybq3S4DimcHeyPPws
qcRL1DlvnX1qF5tIFPvgoKD31s9/PqkQPDfhZStH2oz/IvQhO4b3cA7pWPSDCMCOd/dP0qlWj3KJ
4b4H5jQW2TQd0bubyKW2/P0waY0qo7Urv+7ACY62osXnw8nQhMcnaVSrZ7lFBgnjmqS3D+g03qU4
Yv2K+Ktb+GaiSVNGWQqtHqXnvz9JNakx3dk9FODt7cRmOj9Nl+9d1M3OtcaChYuDfd292o9/c+tQ
TZ/QZk3tUZTdMDTUz+9/KXLyNzX7hllb2zacOrytwMz9XpL02sbfLO0cf+sWwG70S75a8/z8Zp6t
29zZv7KYzJfpkm2z/yf0DJk+cQiHTk/OV35pskEglQUowBCIVotJ2jC5jxNztNKYes17DO4ccCZR
ppQkW/OC02T441M7a1tZdhm3mJwA8+rKf8GenuPmL3by9ismwPEPDgp1AvzgxK76fp5+gd2vvE7X
qBXjJi1fP2tQrZrB208+1p8sjz3CYQa1auqrF+Ck69s96wbX/ViA786e7BkcWAclpVTh6+TxNlsF
pPTlnet5Gjzh0pZt55/f2z2x7YAF4CpZThSX26lAjWvVmaFcr9aNg0gBnjtiYmS28sWWPx3dXZpS
uNd0AvzvkB7/G70X/NTZ+a0WX4p6/4OqaY2tX+QVfuFoQJe6IzdentiIejqV+CgFaAoP/LnX80xi
uyD9NYfeNl/9wVZcJekk5EekEl9XXDWj1/y9V4QCm7RcORDmvh1C/r4RO6aJ9VHdtxd3jq69cPOp
nrXd3+QpgYtxdV67P889Ks8HCoGYAnAlLAiEWB560sy658ISIs7u9m7YulurVivWX8x5e8pl0Pis
S1MmbLuy6+bdEYGUGiGDC5KuNhyzfe2REyFIklZT8rKX6tQrLeadWfff6U1z24wc1B3HNUf3LFLU
6v3vplkrRo8reL+mJdMhNFl8u2eb953YmtSWXTbs/nev1cevYAOmzHp6+04Lcq6NKilXoehSt1W9
hiG/LdvBQxGeo0ctNyuNWunoEwSuY7DtGOjFXAU2f2TvkLXr+tctXNCqfpv6AhbVs9/g8FdvO7Qp
LPXt5409vHdc/Xp1B6x52TfYschvqu7eu3vnzp1D2/+4cPN16ya1+0xZ1M3FIbheg/4jZkxYsd7P
8qNB13pQOvd4Vl4NW152xM0NO57X87OmcFh8NgNBKE0tHB6/jMbYlvVciWFTjZp0eJv+FtFkvI7K
QrTqS6fDU3LLWJwTAqmcQAGGQABo3YEztu+9u2rn5SatWoU0bRZ7avXVHSsm/6/R7Z2vosMfz5w4
bvWusynvjkbduhTar2/9mp49R49FqSUXH7ptk8WtbJfPnjrt940andwC8ezZvnmtxm0b1cL16orS
eQIeq1CNcax/aEibqQPV8W9zpNmPnr3S341lJuAwqVpS67WYRmy++/Lxu9evN5Q9/jeiQOjVsl4N
O1SDYPlKhPwlBHmxd+Ki14I2XuyIpKxH924qMfynzj0s2VQGl89n05H3bsPvk+f/PH7liVMnlv7W
ovvCU0W8Cc2rh/fv3rsTm8fed/ZxZ29zl3pDcjPfbl+3spm3eceAwMsReaWmI4o+ProhqOmYOVt3
t3Bi43ihu4ES3yakIlK1SoOS+0wqb+r67X/0b1y3fv00R0stHIwCqXpAAYZACLg2dfGr204+Kmga
6GzlGWKjfjZ/R2Y9DxuBPbVV9zFHjhzZt/+f6VOnWViZxb1LUmuR/KxERK8ZyoQWDQbJcG1eXqZW
Q0+89Pual9qFqzfu2bKA+HKB7ixSd0uf4Iu4hvRSJrzd9+/RlMyk05culaxHTDcrB4RBo1FoDC5O
o9MouEaNYbjAxjEm8hG4Qp7xXMHtbm7uPNTX8t/9+++9Sbh48GiBUqPSrW5RjARJnn+j+jZWti27
tXkZFl9EgNm/jZ84efKUKZMntKzriUuia/uEhGej/nUaDB03Jbi2MC6roJRI4E/2L+oz/9Bfl84M
7BhCZXGdJIrEXOAZaC4kvqvvU83KinnpeRo47/jR49UcamYkpe6//fL27Tvc/Og67s5f8pggkMoE
nAcMgRBQGZzOThk3fUa48GgoajWtT4OBe61t+KzOcxbMq9fuf3lvs+5t17TaM7NlW+cFXu0GJlFe
HsFx28KLmVaO2vO16rdIeflo1cUoM9HlnNuH9m3n3zjzr0RshuHaspfeIFbvoNAW/7GK2MFSur8Y
sWDq+GIXYBSKrunIGN05qG+Xtg08mPcx95ke3Df/9NmE/7J+0FCbqYGdB0vf7t/655WIhg1dGvYh
rto5sbv/vD8tudQGPjbrrsYH2xIjjdUUlGyGj+7bttvInnGdWm7ZcXjv5Qe0D7+FarQI+v57hFRz
r63ze7QLdPCp2zL86V0L+5+3hhDffNR+EiVMmhs6fGmOudvk3i3GqvKaTzq09a+BtZ1aD+mGPdW2
3hXikDh6dvvONeMG9Nr/QHtxfci9vUcn1G/bPMTsclb1RbWhAEOqHHAaEgRSCI5riMWsyEUatUTn
KbmMlhbHsrNyaGxzMx4D1R3KzRLT+RZsmn55KRCIZYtzmDwRj02EqKX5eXKNUGQODoBzNBoNeean
q1cSv4OiRVe/1J/8kW0aDUolP7mnlRdIpBguEpiBq3RmosBm0gCGmYjP/HCtfmnM9+tQFrsVolLK
c/MkAgsLRpHu9KIn6MEwdU5ODp1jbsZh6K391FQN8U2qQkC0gGHKgpw8FcVSZEZehanl2TkFIksr
GpHOWoU0XyLXiiwE5TH3GAIxMaAAQyAQCARiAOA7YAgEAoFADAAUYAgEAoFADAAUYAgEAoFADAAU
YAgEAoFADAAUYAgEAoFADAAUYAgEAoFADAAUYAgEAoFADAAUYAgEAoFADAAUYAgEAoFADAAUYAgE
AoFADAAUYAgEAoFADAAUYAgEAoFADECV/hhDVY47pNwp41u/lRVYgiCQYnxVPVCFBDg3N3fVqlUW
FhaGNgRSCTlx4sSpU6doNBqFQqFSqcR3+CqjHo8ePbpatWqGtgICKQ4obsagZWKxePbs2WCDrApQ
HWWcTyvjWOVj4MCBHh4ehrYCUgmJj4/PzMxkMBgsHXQ6nSyBhrarnOnWrVuLFi0MbQUEYqRMmDBB
Xw8wmUxQCQB3vAwNrloCDIH8OJKSkthstrkODoeD6r5Hb2ijIBBIxZGXl5ecnAyKv1AoNDMzAyFl
d4ZVIQHGcdzQJkAqM1FRUXw+38bGhuyFBo1gQ1tUzsASBIGUTVZWVkxMDFBfUFhADfDZeqAKCTAE
8kOJjIwUiUTA2+XxeGwdhrYIAoFUKKQAAy+cxWKBFjCTySy7HoACDIGUD2KxWKvVWlpaKhQKDMOM
YUgIBAKpSKRSKagHGAwG2FCpVKAdXHY9AAUYAikfQJED3i6pvrgOQ1tUzkCXAgIpG7VaLZPJ5HI5
UF+NRvPZSqBKC/DevXv1CWS0lUuPHj1YLBb6nmJHExMTr127Rm4bbRSEQmH79u2Rz41HQN5HwTgj
Qlpehv2gyGE6tDoq0DQIBGIUANHVN3y/pB6o0gI8fvz4tLQ0Y56vGR8fn5qaamVlRaPRyFf6xTTs
2bNnvXr1AkcNaORnCQ4ObtKkCTkegZycU2x4sLW1tZOTk6HM+xJycnLCwsIYDEYZ03z15a3Kqu+L
Fy+MPwX8/PzKmJ2Zn58fGxtLbhttLNhsdo0aNYpFAVT9r169IreN1nKk9PQXi8XJycn63WJRMJIY
mZubu7m5lSEZ+vz/hV64UVfcFYCRSxeo60EbV61W83g8Pp9PTjAFgUXPIaeaGcrCLwG4hCAWHA7H
zMyMy+WCKBQrgY0aNTp69KgBLfwsu3fvzszMBOkP6j79U4CzjIrRtWvXiIgIQ1tRFsBFkEgkwJGi
6vhUCa5fv96mTRsjL1B16tS5c+cO6QuSpoJYFBQUgMzp7u5uaOvKwtbWFjQqyCpLbzl5aP/+/cOG
Dfs05cEJxvM4Onbs+N9//+lbEZ9dZ+OzGLX8QADAKwS+LWgEg1xI02Foi74a4ECAWAiFQpBZ9WtF
GXPHQ4kAHwK4QQKBAEQE0XWnG9oio4N8voa2oixAxsvIyAAuFHAHwV+yQBV9lKDVYvweLShQpDtY
dLUHYDlZRRjaurIAOYS0HKQ/cIOKVWjGn/JKpVKf8mT++c4174z6aUEAMTEx4KnjOE6urkL24uqP
GknPTNkA+2NjY2UyGbAcOOl0HYY26qsBD0IkEgFnCDwIMgpGXllUMKYy6CwhIcHMzAx4UcCXArmx
2EM0iViQHi0ZC7IRBmIBcqah7foigOV8Ph8UJWC/yXmxoBJLSkoyNzcHKU9K73dGAQqwsQPyK3jG
XC7XwsICFDyTqCCKoVKpQK4FsQBRIAcHmoTfUIy4uDhQ/ID6guIHHgdoeRjaIuPCVJ4pEGCyD4Ns
gYG/+kOmMnqOfKdDDg0h3UFTsRzRpb+lpaXeckOb83XI5XKQ8gqFAtRmZN8DALaAKzMSHeCRA/U1
UekCTgOIAlAv0BQmp+gY2qJvITMzExQ2Gxsb8CxM9EH8UEwlQaKjo8FDBLUnOaii2DoJJpE5gQDH
x8eDTMjTQUbBJCxHdI4sOahFb7kJIZVKY2NjQSUGXHBynY2iDtw3AAXY2FHqMNG2LwmwHERB3/Y1
lZq6GMD5JWNBzvE10VhAxGIxaHgBj5B0B4s+R1PJnMDsrKwsIAAgT5J+OWI6DhCwHEgvcMf1LQoT
Gg4C8gyZ8sD+cmlLmFgXfBXky6eUGTP6WBjakG+HrC++ZHJ91cRUHq5CoSBnbJtuNwbIgSAK+v4k
04oF6cWWaLnxD6oAeUbfliiXlIcCDIF8KaZV00FKBDhSevU10QcKzDa5hq8efcO3mOUm4dfqU768
rIUCDIFAICaJyakviem6PuUOFOAvBfg9hjahHNFKCgpgCYBAIBADAgX4i3j2z1gOu3Gy4is0S1MQ
99fGzZFpBT/Oqm8m9eUVkcjhelIJtqW+PLl5875cZQkdLHFv7m/asqsSuCFxzy7/veMhDh0QQ4Op
VWpNqY9BKZdrKuNDkkkVhvhZrVwu/+aLNSoFpjGBLmKTMLIoUIC/iKTIFxpNAf413SZpd/aMHjPy
WFjSj7Pqm1HKs3GNBi2p7jsydtbIEb/E5Ks+PXR1/6qRkyarf7x5Pxjs71Ftfx28WFUJ63bTQjOq
TfWfuq0u5ajaz8N6yfYbnx6QJT/xsfaOM8qMmJ/26tbtp4rSvQp1wnFzAf9edF5FWgVIfHTC3Mwj
TPJN+oSr7R3smk/aUVqs8jISTx/Zt3brlhsPXskN11P4cvdoOq1Vulqb8Ob+/WqptDEAACAASURB
VCeRJlG+4TSkz4MhyKtHylIOKl88eeUXFPTpAYc2s9LShltaWX16CFfLM3KUttYCDFNSqExKhQ/C
pyClZs5RV8J65cosRaxPDw2at6ftGGkJB0wMZVYOEX3oexoaLDcrGecQ3UollQClUi7VYiXIbNyr
+xHiPBk4YnyrOKxr3H5uVOKjDFmQVckFRVmQptEY4FvRMkmmRqNCSvcMygBYC2zGS1HWgpi71p5N
VBh5FO09den+ZdMMMq8o+uktBKFi6uxRPvXvOzgnJ8QxKr5u/UpgLVQqWlXOcP9aXAqFQeHMvX5f
6+TKZ6AZkTf9atawsbZ2dPEYs3RT+JnNgXXq1ahVS8Dj2TpXq+HuKhKKGnTsg2uR+LOLa/r6v8wC
TUnl2nEd7KwBNtW9at6PztqwcLizi4NXdUcmg23l6Po2Q2aoODatbh80cCmoDc7tW8C3dEqSquZ0
aFE7dKpSixSkR4UE1nZ1cXH3qD5sxnIphuxePLhxq/aGMrU4atmDG2dPnjobl1noG717eGnO7Hnr
N+7NVBK1zIn9fz+LSj65a8OwEeOeZRCdfq9vHgoNCQ5t3u3fCKIdYGJ9VaaPFlNm50oQYi6HihQg
ms4RLK2OLC1ckZsGKi4qHdGoVMY2lmf01TNXbtzxETJT46KkxvS2hlq6z/2dMAR2A7r3OHb9RUpy
fF1f1wOnHstLf3Hw49bLBPcNu6frt6OKNrx6cOr0OToFFWfk4IQDAdyHH/Sz3wsU4FI5tHHO1ufR
feeu3b9ztSUbRdgsZcL9uj7NwyPjpy35g6kSn7wcpsZBFYBFvn6dJ5WmJ0ZHyvm1ajrdu3gvWY2/
fXQkKzNFo9Ue+mvehPVn6nQd1VwmjYoIP3vxiVKjUCtkMSkFq1fOVqUm3Hudaqg4ZqkUuJroi83P
SpfIZCiifZqckiqXqLIj6oUEPg6PHjl5Tm1Mtu2P6WHpBVEvr+ZkpRjK1KJE3fy7mrtr/eYdunTu
4G7D3nAz8veZv/rXa7N4ycJxYwbYsB0zJfmLp/8WVMOpy6CxWzevC/rfzrPz+tRt1uvS4yeXrl/M
BbX2T60ZMO9XLJsXjnB0dWvawI/JYLnXrheT9aWvJNPf3fmpRUMPDw/fwPpLd53QCXNy42puDBbL
0r7a6n/Pgv2bJ7cE1PQU6j5R1XL8XxUly7LRPRu72tuCH2Vxbd9K8TUjx4xafBrPe+Vb29MzsEkN
RxtrJ++WTRq4ODn5BvfN/kiZ1H/NHV7L28vLq+aUbVcrUCAkv/UM9XBzq+FZs9vgsWq1okVAjdqD
NmJaJDfqrqeT47xT0Xf3Lwzw8XJzcw9u0GTf3biyb8cUuW3Zu4Mef3PMqBFvY1JsHSwZpTc7y91h
0qqyJ7VuzEdRGmq25MlbxNGZi+aM/7nP3O0RyugjdjaikHp1BBya0NL6VHg2OH/ZiAF+3t6e3r7j
5uwtX0u+DVgJlcqbh7edavlvnjum94DhXj7VQIvp4bGTCRhj+tFXE4YOthZwAvydabqsVrvzqJzn
21AU3Xf49B9De6CqzPBMRVp0MnA6KSj6+Po5rZaRF3HmkFQqrB7ctHEt8v6Dtl0b3iVAjSByVQkv
XCsKilc1SyISICOoNHINnqZRIxj+4vzut0mq3/bemTrm1w71rBBExGcgOSni0pslFYn6t7FzojWi
v68/j7p/HDgNaVmxe7fup/g0/H3WLwhRyFN0Xq9WK/LYdvFqcypFi2tHbDtnE9QzJr0g4fERCgVF
5MYQkaqFBJPK88R3n0b/NrRv6ssH996kFz2K47gGw4glGj7uJpUmP2lds+mVu8/adeueGhW2budF
ta4Sl3PdZsya5YxlT+43/FFy/uU9f4ZFJg6cMWto12au1vyKiZE66d6uw3fotm6zp0/w9fDg05DH
r9+9yczUYArQ1E9+cSsyOSMz6e3VW/ecHXmvn/x76FGm/tojG8eOWbwlmWprqXqzalira+EZFWGx
VjO1R9Pthy4FNWmBRr45tmPfcylqQ5W+2Dn3YYLk/MFd75LyPAWxbX9dpOA7Bwp5T+/dWj19YzHN
BE8K0z0pzXs1lWdEdxk89sjxs3lSZddGwdQKXNnq4J+zVl9+1HzgmJlTBrGoCCIwY2GSZ29iIvIL
MFUuhiBPHzwK/qkXJydz2e7Hz/cOmr55j5RhxqdK1y0efzOztBeLFQcU4NLQyOQypVol12UyctY1
TuQ4Tcs67ihRweNqdWH+G75gEYNBvPKJT8m2cbRGUdnDiCzy7ToF0RTkFgBxS8ilz93wX9T9C/4O
ZjnRsXRbn9W9A7RaorcUU2AGiiNAGx6RWfgSjkFjkyvRpCuS3+RptbzBLWsC69aFibU8b2tzBtU4
5BfR5KTHpfXpM3FgE18tJgGPxJslTs9WSMPvzFpx2L9u62OPEq14RPL/b/Cswa2aHYgMTzs6GFOo
Gvfq4GrNs/OoaUJL31U+2iw7vXZmXwRF82Qf3ryIH20zZzCYuq/UOfk3x4pU+Ve373qFUYf/fX/d
iuU2Qk6zpl504vHZ3n58ZfGiRZdO/44giY9fZ9as7Yeq5ev/2Fu7y5Q1E/tUzAOm29RwFPGjwx48
SKFsOnTQgUl5q8EQYqwmCv7jWoQky8VWXGTG5nMn/14Nct3NJ/HvL9WcPXqG5V7vzdMrt57eZWu1
T8OiK8BgjUpx4GaEFrF5/fhGpFbrEFDPmc9Ys3YmE83et2nH7i1/23nVc3qwNl+OOZljx5+/pvMt
6ncNLZqYL09uY+o+ywaeFJPeKFlO1Ixc+5ritOTz+5aLzLmbF+zMwCruvcCjezeq1Wl6cse6JcvX
urvZIxiCyXOJVH6/UIZb98nndi0BBiWmxk8YfRhB7M9du3F29zoEydpzqiLSvGzgIKzSoPo1aZ1+
4i8rs4Y9GkluPYlEPHwFAhGKqDv1GLKyjfnDd5mI/OqkJm3AqRotznELtEGQzOgEgbcLqFzuP0xw
1b3swLQUj+qeyKVYd9/a3LyXvjV+ZbWc2IOiYbGYQLGpjr4CoHcJCQjiW5Fx05cPIZd35+CWX3nx
dy7sRrQChPA2tIgt26uhK4pmte8xfAjn9st3yYhfMwEd0eLgmDG8ctMgciQtKzwnO3XdgtnAIE93
Z2JNd63fzcdHqwm0l47+F1vtfyCASSU6w6zdPME2jU7bvWXvmE5NqAnPiH4wKtTgigb4nTTHwH/H
NMUi92IgN6k/dLvynYIGDB6o0DAFApaDd8OiLyy1xMQSvGdoTVTn/+F44YOj6DZyM7JBMItO6zlr
v4d/y0FTlo8d0P7yq1VH/phQEV4W3SksJnzyqJEHT2ysc+zfOHEiERglxXX2u/eeYs9ioSglTZLJ
s/FjU9Dnt18gTckrlTkpmZ7VG1jTqcCrRytqFUYtrsSIsVTpMrVo7YErQ9qHUHAtq+EwX485m5aP
A8W/+47lac+GgjMfPHvb6Zcxa5ctMGd/ZJi1l9/Agf/DEZTLtXT0DrJgUdLePd936tHI8b+26Ttl
6NZDy24oiKlltIopX1hBvgRHcZUWAUWdSMj3P6t9kZ9w9yXYmDN2BAWTgjYQSyKLAKoc1MtFwMrR
Ep2OOMvw8md4C4yWfhPWZCYmTPjz9N6Lun2p0m/wuFUvLk/YsGv4LV1IwrVEZCCQWy4LiCmuaxZr
ze3sQS64cyps4c8NkQMnzVj0iX/+l5XbY+neTVd0F52bPSR8fzj1UQy4EGG6CgVISkFSKQNBfzjb
lgz16T5nx987iR0GApr0wTT2Mzubmm0mbZz7YsSCv5frThOy6UDOXLxq0lIqevpECVDtqjWqfXL3
Ous96zU6P5fK8/VvVDP51oum/jWISgbHz7TuWuyiraMatp13PsTLjVyHB7kWpiFeEBjC/qqKBlFy
uGYcBKW6BvIRNCs+TX+IaRu4cev2Eq/iUkHew3qPnLerPTM8MSf88N3RPu4IktbQSTRpRM9Ff2zV
ams08ed0r2HL6Tj5n+2rQht3jU3Ir5gYJV5Z1XzSkXkLFlC14rX7XqVIdS6FG49KlmY5kDouk815
HZ5B49t6IUj+qxcI4q27lOPiF3Ds0MEek33OrF8E1KBeQPUKMJhCZdOJr/cofhk5gRp9WiBsU3fZ
vVsTg6d1rNVzzS2tW8NdA/zfqfwQ5EmtJqG92gQN+snvscQ6K/y2/g42Nepu21636D0fn94/ZfKK
ufO3jv3FYsXNx0jNrgJ6hZUrmqt/UMzq49YW7QY2zyCaCgGFI+NRHwGGSMGGyIxHM+eDKCU9DutL
oa18sqb/QEby5WUIYjuuS42KsrNUoACXDsoYt/rE0EVSBKWx2QxMo2VQaePWnhu8KFeDMsz47Nys
fIGl4OeCHhwOB0F8jt24YlstmGbBTY6NoogcrHgjFKNwBp2CIGZL9p6fvVUGXHkmuBGN2mrhnqGz
cV0bjHs3Mp3FE1SwELiE/JyX357D5aEus2WS8XK1hkFBMrMLXHjMzU9ebkQoNAo6bN7O/hPXaamU
wGqOIi83JoJM+OfJGK1RvLM4fOrq5XNnItOkipQb83//15LDOH7xbtjje2HhcXS+sFZgSEAN53dD
J9ZsX09/SZu5Z163v//w2SuOlbOTJV3C8akgHx3yHkvnaozwbMLvZDjyOEhcTtSXLLPRdOqskc9v
bTy8JPSwrl355t/I/Cng34LcnPlLtyBI4KWwwx4CloUDc/ua6fv/RIF3NXpgl4p5ycAVitJf3B/Q
pQ3w6uzd+vrxKb4UWoydBYsjdAG2cojXUiiKEv1KDIGvH3JBehWlAi0ghuzO/2Pj/ZvBx1bPA7uL
d9ytU134Q00lU5rCYD++drxeq58XTfgN7Fo6Vl//iw/Y6DJnY7W1tWt1GQGa6X5DNv4ZLpuwbte9
Y7uA5ePWrCLGTCBoaUPm2gyfMv7u/TVHbv6xCUFqNH9w9C9eBTq2ExdsSY5P23jk3Nqjuv2UbDVL
UA1B1G627kGNEeRfFoOGULk1qyEx8mvz48MPe/ke3gPUF5m2Zbcfp8LMLBUowGWBohQur3BABzlo
FqVQzQQWZIiFlQj81akvgFK3cXMy3MbZrfASOkV/H6B2+tvS6Ez++ymMIosSJgr/cIh4FdrD4vDI
GYtcvjlxhEoYHXZ0be/Z2+0cHXLeXYpKw5d0agFqNJRK+65PX5Yb+LlT52k2bnVFMeNWnwP1Ag94
NSx2cKPQ4EYfTho3b8XH73op3kENwP8Vbi2kkLELdvSfptH5nYKrT14J7dw4YwZgdF4pp/OeRqSy
hZY0OnXdwbszkhLUNJ6jnTD6XbKbl0vPvnNRXF0gU5pbWLHpRB/p5ssx85OSJEq1lb2ziF9BX5kV
BQ5Mye6YmpFFY5k5O9nSUPTw23cYhcmg08KyMoEvCM75Y9kqc0+Q65gL/30wQmnB9XJNSe1iZS2g
ogHXY3KTUsUog+/qaPmjHdvqTQenpXW1Mqci5s0j45PEWTlaCl0osmDo/FCa0PeROJPJExJKS2WP
W/PvoLnrJQqMay4w47BBMUqIjsHZ5iXqKp1juergtXk5YqkSt7CyZNIrVFOYPOsNB28vEGdqaWyR
gKNQIxwm/ZVcQmNxqYgmKaWbjS1RS6+8FT1Dac41t4iOT0hJzdTSeU72hqh4PwEKMKQEbGv4/NS8
QXp2vmvL3wa27DGyS0NDW1QEPHvu2P4viKFjCJXFn3j0uYBVwvszONLK2GByzOzetzmqe/ro/i1L
KYXWNuQGhcZwcK1Gbnt6u4O/DJ37yDX7cDKVOMe9nC3+PChfYAn+1+/TmFyySuULRGRIn4FDyQ0n
z2An3YatTaEHz2TzPdwraMA2SEQr60LJodBZ1rZ2xY6bCy0+7KComciqSOoiHKElUjoohWJuYW1e
TpZ+NRSqhbUtuclhEn+ZLK5uj+pgV5iFRLbu5POgMHiOLqX5fAYACjCkBGxrtf5zQyuy28rolIxi
efNNUlR0kgaludXwsjSroOYOBAKBlC9QgCGlYHTC+wEzkV2gqLgLD4FAIKaFUYypgUAgEAikqgEF
GAKBQCAQAwAFGAKBQCAQAwAFGAKBQCAQAwAFGAKBQCAQAwAFGAKBQCAQAwAF2AQw4glBEAgEAvlG
qvQ8YIlEEhwcbGgrykKlUvn4+FB1nxkvTYbr1Klj5AqN4ziNRiNjYWhbvp0yHgEEAoF8A1VagPPy
8rKysuJ0xMTEpKamymQytVqt1RrDR/cIgG4JhUJzc3MOh8NgMICGFdOADh06NGnSJDk5GdgfryM3
N5f4VrZGYyibiwEMBl6OQCDg8XhMJpNU4mLn/PTTT6tWrcrIyMjOzk5PT8/PzyejYDwPAtjs7+9P
fAOVySSfAhTjTwGlaciQIYa2oixABgNZkU6nk+5UiQ9x6NChRv5wQbkAtQEoSsViMWPGDD6//Ne2
xHH88yd9GaCCBZaD9C+xUTFo0KDy+qEfBLCZtL+82hJVWoBBJgCpyWazQZm0siIWSpXL5RiGGU+9
D8qYmZkZqcHATrLIFT0B7IJAcAicJhKJlEolEAmgXuVYZr4TYCEwD9gPzONyuSDBPy14//vf/8Ri
cWJiYlJSEnCGwDb5IAxl86eAIkdGAVRwLBYLpLmR19EGISIiIiEhATzEqKiolJQU4EiBDGk8viAA
lHTwEEFhAXmSlIFiz7Ft27bA0wJZEXi0sbGxQLBBVjQqpxwUn59//hlEgSxN+o4lELJ8+XKQ/rE6
gDtLWv6dVUH55vOBAweCckT64sU0eMyYMSDDgMwDUh5UAiAioIFkVG0JYG27du3IlCfbEt8vw1Va
gAEgB4MMAZ4xSEpQOI3qeSPv1QtU+tbW1iDXAms/LQ8gHwDRtbAg1lIHJxubDwEMBmaDLCvUUaJ6
keeACIJYgCobxAL8BRWH8cQC2AyiAOpu0hMqRxe40kA2DkAqgSQC7ix4dqCqMipfENE5UsAqkM3A
30+zItgGqgDqVlDiwDmguQbOAVnRqHxBYCSZFUFpIjWYjAJpOShE4JBUKgUxVSgUQIANbe9HAINB
Nau3vGghIhMfJDj5gEDOAXH5fgeiHAEWgppWb7++H+V77lmlBZjMsqC+AEkJHjbIr6CkGdXzBgDb
QKYEzxtYSPrsxc4BgeAoqO9IGQZZ1tjqCzKdyWZ6iQJMFjyQs0lnwtheBCA6dQEWksUP1M4gzWEL
uBhkVgSJQ747AM+aLFBG9RzJDAaKEnARStMA8ikDy0F0yKxobE65XmhB3UU2xYDlZBYFlgNrQQiI
oBFWBcBa0hcHdpJVQdGjpJtraWkJ4gI2gOtjVPWA3sUEKa+3Hwrwt0OWN7JrF+QMkFmNqqQh7y0E
5jF0lPi8yQIJNsjMbWxVHvK+n1wfhU/bjmQUyNqEdHtBFIzHE0J0FoIHAWpkkFuAkZ96QhC9AJNl
iuyJMaqHiOieIzCSzGYldimRAozo+sZAJUuqr1EVqKIeLUhtsvpC3nuxZHMCeD9k578RWg4SFtgJ
LAfpXEyAyW4wcA74C2TYqJq/JGTKk/aDv99fCVRpAUbevwYmy6RWh6EtKgHyZUlpY39IeSP9X9KB
MMJYUIrwaSz0JZPM30bV+ayHNB5klXJ591P50AsD+SiBL2iEz5FsKYKHqB8K9GlWJLuUyKEVoEAZ
mwYg74s8GQu9U062IElVA1WBEXo/SBFHtsR3qGQTUx8RY3MgkPcpTzbYyPGksAX8XZAPG9G9HDK0
Ld8OVYehrfgu9GNJyCJnbAUPeT8aBY5/LgMyE5ICTNb+xvkcy/AFyUxIVgtAgI3TKSfN1kehqM2k
QgABNiHLix7VN4eMM/8Utb9c5iVWdQGGGA96hTO0IZBvpxL4gmTdamgrvgWyE8J001/vD5luFL6W
KiTA4KEOGjRIqVTK5XKFDrKXxticLIMglaox7MP7bzabzmBUlTJQFKVSo1B8NHCUy2WAdsVnLwS5
qFWrVvpezcrqRsyfP3/GjBmg7JCFqEqUIBA9aT6i784F7R6uGVK5nq8RdlabKG5ubuSrNJLP1gNV
SIB5PN6JEyfImaaA+Ph4I5ynaCjUak1YWJpYLCcrU1DJ1Khh6eRkDjYMbVqFAmIfH58TFZWjUhXm
CpACtWrZWFvzQGkq40JQ2MzMzPTrjZj6sl+lcfLkyeTkZH0JysnJMbahtuWLVq1Sv3mGZ0gKV+1l
shn+DSh8c0PbBTFS2Gy2UCjUT/f4bCVQhQSY7LsnB0CCilImk5FrVkABJnF2dszNVZw/H6VWE+5w
ZKQ6OTm3UydP0KgztGkVir29XUgI/upVxsuXGWTI69eK2FisSRNXKytOaVeBrMXn80HBMzc3B2Wv
Us5T0pcgcjanVCoFMSVn+lbKRrAmI1l57wrQYETXG0Rz92YGNUIoVas4QL4Kch6zfqLzZxvBaKUs
OSUCYiqXy3Nzc7Ozs8ViMfhLzjOD3S9FUSiwe/cSb95MIHdB/qld2+ann6pVNRkGAHfk+vW458/T
yV1QjuzseN26eVtYlCDD5JIpAGtraxsbG/3qoRVr8o8FlCCFQkGWoCwd+lVfKl81Iju5F3v3HMEJ
7xxlcdjdh9LsnRC0EvZqQMoR/dKKoBKwAg47hwN2y2gHVyEBRoiOVjWoMkDbFzjvZN1hhCPdDQ5I
kISE3H37Xr19KyZDLC05PXv61K3rWPladWVADsdOSMg7ciQ8LOyDDAcE2Pbt62ttzSt6Mjl9hZx+
w+PxgCNM+r8GsPtHAooMKDig+IBCBDYqZfNX9SZMum8tLi584sz6rTndh1B4Zoa1CmISFJvoTA7q
LqParFoCDCoLUGUAGQZ/MR2V0nkvFzAMP38+cufOMLm8sIu+cWOngQMDbG15ZV9Y+QAZ5NGjpAMH
XkdEZJEhLBatU6canTt7CQQsMkQ/ABUUOf0cwcr3GhiUILUOshxVshKklcukJ3YqTuwih1xRhFbc
X8YyG7SpZEOuID8OchoYuSgKuWZA2V541RJg7Xv0Dd8qFf1vQCpVz5595cmTVKDHCLHYFnXOnKaN
GjlXwTHSGg1+7NjbvXtfZGRIyRAOhz5lSv2mTd2AHiOfzHGslL0F+hKE60AqUQnC4iLyV0zCot+Q
u/SaIeazN1CEloa1CmJakKW+aCUA3wFDvguQQR48SJo+/bJEoiJDXFzMN2xoZ2dX/h8+M35wXPvX
X4/273+pHybN4dA2bGhfq5Z1VRsxXnnAcdnpvZL1cxGNbjg3nWE2ZhGrfV/Y8IX8aKAAQ74IoDdb
tjzetes5uUujUbp395k8uUHVrKNkMvWaNfePHStsLYFEcHY2X7Ei1N1daFjDIF8LXpCbNbS1NjON
fOdPdakuXH8CvvGFVAxQgCFfCsgqUVHZU6deSkzMJ0McHPiTJzds3NjZsIYZBJAacXG5f/754M6d
whHjDAY1IMB20aLmIlGps5UgRoX8zH7JliVaSR6xg6K8YbPZnQegTLah7YJUFaAAQ74OjUZ76NDr
rVuf5OcrEd08pVat3CdNaiASVcVqC8e1Dx8mb9v2RD9bCchwly5ew4YFm5szDWsbpAw0makF6+eo
7lwgG740d2/+5JV0Lz9QJRraNEgVAgow5FtIS5OsWXPv6tVYMvtwOPRRo+p07epVBQdnIbrX5OfO
Re7aFRYdnUOG8PmMQYMCgBKbmUEZNjrk105K1s3R5hFj2lE6g911EHfgZJRVFT1IiGGBAgz5RkDG
uXUrfsWKO6mpEjLEz89m9uwmVfY9KIbh+/a92LfvZXa2nAyxtOTMmNGoQQOnKriMiXGC52VL/lqg
uHy08I2vnbPZrPV0nyBD2wWpokABhnwXQHXmz79+6VK0RkMuIo3071975MiQL/mAQaUEJMiSJbfO
n48kV/QECIWs7ds7OzubVcqJSSaDVquOfJUztiuiUhC7FAqzWUfzmevg0pIQAwIFGFIOJCTkjR9/
LiGhcHCWhQV7zZqffHysDGuVARGLZYsX37x9u3B8FoWC+vpa//57KxsbrmENq7Lkr5mhOHcAwXSf
uqLSBMv3M2rXheoLMSxQgCHlg0KBnT0buWLFXbWamCALJKdhQ+d585oIBFX01RqOayMjs1auvPvs
WRoZwmLRGjVynjGjkbk5y7C2VSnUEc/zF4/WJMeSu6xmHXljFlKEVdc7hBgPUIAh5Ulycv6GDQ8v
XYohdy0tOYMHB/TsWdOwVhkQDMNv3YrfvPlJdHQ2GcLnM3r08AHJwmbTDWtb5QdTS3askh/drlUS
3c4oX8AfvZDVqitcYQNiJEABhpQzoOV3/nzUX389SksrHJwVEuIwZUqDKjs4C9FNGt6798WBA6/S
0wuXsQSN4IkT67Vs6U4uYwkpd7C4d/mrp2GvHpG7jMBG/InLqPYuhrUKAikKFGDID0GjwZcvv3Pm
TKRCQSzvR6Ggv/0W2KePL5dbqb7Q91WoVJqtW58cPfqGnEINmmEODmZTpzasU8ehyo5Z+xFo1Ur5
qX2STQsQ3ae+UQ6fN3Q6u9MA2PCFGBtQgCE/kLi43DFjzurnKZmZMdevb+fjY1mVxwPLZOrZs6/e
vZtIft8C4OYm2LSpg4UFpwqnSrmByyS5U/pgb56Ru6jIymLbJfhNBYhxAgUY8mMBzb6TJyP++OM2
uQuaevXrO65c2YZKrdJqk5EhnTr10qtXGeQulUoJCLBdvrw1XLjje1BcPVGwZrpWWkDsoCh3wARu
vzEIDb5rhxgpUIAhFUFammTFirs3bsSRu0Iha8iQwJ49a1blLwjhuBYI8MqVd8PDM8kQLpfeurXH
+PF1eTwow18Hnpedt2ik+tmdwqUlXT3NZq2nefgY2i4IpCygAEMqCJDRLl+OXrfugb5HOijIfurU
Bh4eIsMaZljUas3FizFbtjxOSSkgQ0Qidt++vr/84geaxYa1zVRQXDsp2bIIz0gldzk//wbavii3
Kn4uE2JaQAGGVCh5ecqNGx+eOBGh0RBvQOl0yq+/BvXuXbMqD85CdLOVxE2AggAAIABJREFU/vnn
2cGDr3NzFWSItTV34sT6TZu6giQyrG3GDF6QK/l7ueLUnsKlJW0c+ZOXMwIbw/FWEJMACjDEAERE
ZE2dehG0+cjcZ2vLW726TY0aFoa2y8DI5djSpTevXYsDG4humLSnp+WsWY3B36rcV18yWi0W9y53
ci88R0zsUmmMwEaCpbuJ1VAhEBMBCjDEMICMt2/fS9Aa1q+ZXL++09KlLXm8Kt0URnSdBNOmXXr6
NBXHibKJoqi/v83y5aFCIVw/qxCtWiXZtlR+ZDvZ8EU5PPN5mxkhzQxtFwTydUABhhiSrCzZ7NnX
Hj1KJnf5fOb06Q3btKlmWKsMDpDelJSCCRMuxMYWft+QwaDWq+cAZBjOGMZiI3Jn/g9PTyJ3GXWa
m81cRzGrusu8QEwXKMAQA0Mu1rhgwQ2JREWGBAXZz5jRyNVVYFjDDA6Q4Tt3ElatupeUVPiVC4GA
1aOHz8CB/lV2/SzJrtXyg1u0ct2CYihqNv1PVrNOCB1ONIKYJFCAIUZBXp7yn3+e/vffa3J5Cjab
3qdPreHDg+G7T4UCO3Xq3T//PMvMLFzG0s6ON2BA7W7dfKrUXGosISp/+UQs/Cm5ywhqzJ+ymmpt
Z1irIJDvAQowxFgAOfH587QVK+5ERGSRIXZ2/NmzG4eEOEAZlkpVW7c+PXr0jVxOfFAPRRE3N+G4
cfXq13es9ImjVavkFw9L1sxAcN3Skjwzbu+RnD6j4FBniKkDBRhiXIAMuW3bk337XgHJQXRDkLp2
9Ro5MkQggEOQiGUsZ8688uhRslKpkyIU8fe3nTmzsYuLoLLKsEacVrB8kurxTZA1wC7VuZpg0d9U
Jw9D2wWBlANQgCHGSH6+cuTIMxERYjJ7MhiUuXObhYZ6VFaZ+SoyM2WTJl14+1asHybdsKHTwoXN
K9syllpccfNc/pLRCEY0+hEqlfvLePA/bPhCKg1QgCFGikaDv3qVOXbsWamUqH+B9Hp4CLdv7/RV
S3YcPXp06tSpP8zG8iEkJGTv3r3oe77kEpA4795lT5x4Qf9imM2mh4a6z57dtMQbVK9e3fhL+tu3
byngMb9PhOyJPbGXDwq/aGQmFG0+R7VxMF31PXbs2JQpU0o8pNHFsXIwa9asQYMGfVVmrspU0bGU
EOOHSqXUrm1z/HjvLVueHDkSDlp7kZHZoaF7+vXz+/XXQAaD+iU3yc/Pj4iIoFK/6GRD0aRJE2An
jUZjgFiBaOso+xJwlre35alTfa5di12+/G5OjlwuV584EXH7dkL//n69e/sWWz9ry5YtLVq0+JGR
+F6Cg4NBIoAUoNPpmme3pSsmackVNhCE020Id9BkU19asqCgwPiz4vezZMkSMjMDwKP8ksxclYFJ
AzFqhEL2tGmNNm5s7+VFfFFOqdT888+zIUNO6KcOl43xN/sQIlLK1NTUrKwsUEeD7S9vD9FolNat
PY4d6zV8eDDZ/5yVJV+79sGAAUcvXowmO6gRE0kEAEiEzIT4tFUzxTP+h2UTH6ig2jgKluzkjZpv
6upbdcjNzU1KSkpPT8/LywOZGcMwU8l+BgEKMMTYQVGkTh2Hf/7pPGxYEJtN9Nm8eSMeOfLM77/f
EotlZV9rEoVfoVDEx8enpaWRAozj+FddzuMxfv018NChn7t182YyifSJjMyeNevK0KEnnzxJQUwk
EQAxNy9FTflFfHqfSoNrtAizeSfh5rOM+q1Mt9u5CpKTk5OcnJyRkaH3Jk0l+xkEKMAQ04DBoA4d
GnT+fH9vb2JhZFCojx590737f/fuJYIyXtpVJlH4gQAnJCQAAQaNBrCtVqu/4SYWFpyZMxufPdvP
z88GtIx1c7rShw8/PWbMueTkvHK3+UcQsW5hRlJCAaZVc8x4C7aazd5IMa/SX8oyRUDbNyoqKjEx
USwWS6VSkJlNogwaCijAEFOCy2Xs3t1t2bJWdDrxLg0UcCAwffseyc9Xlni+SRR+0FAAjQZQYUkk
EpVK9T1DcszNmf/80/nQoZ729kSfLYg9cFC6dv2v/Iz9gaQpsGy1RulUg7/1Aj24maHNgXwL+hZw
PiiTX/M+pWoCBRhiYqAo0ry52+XLv3Tv7k2GREdnt2u3b/36B5+qrUkIMIZhBQUFoLkA1LdcWgxO
TmZHj/b666/2AgEbMZFEAEhxRBvaizN2MUKhmorNX0WlH4GFEF/0kufl5QFXUqFQgIwNBbhsoABD
TBLQFJ42rdH27Z0cHc0Q3XqNu3Y979Pn8OPHKYY27asBYgN0V6NDq+P770mjUerUcTh5sve8ec2+
cMS4waG27EqpVgvXTcupfAL8ta/2TRQguqQfiesor/xcWYECDDFVKBTU39/22LFev/0WxOEQy/FH
RWWPHn12yZKbBQUl90gbJ6CG+kG1FUiWjh1rnD3brxzv+QPh8Ml0MLQdkG8HPL5y9CMrPVCAIaYN
iqJAgHfv7hoURKzLj2H4sWNvO3c+cO1aHGhVGtq6r+MH1VnwE8sQiHECF+KAVAZcXQWbN3c8dy5y
zZr7OTny/Hzl1KkXAwJsXV2lhjYNAvkikpOTMzMzi4YYYSPSysrKwcEB0Tm+hralMgAFGFJJABVC
u3bVW7Vynz798s2b8aDuevo07eLFJ9OmGdoyCOQLWLly5Zo1awxtxWcYNWrU8uXLaTQaVQeU4e8E
dkFDKhUMBnX16jZ79nS1seEa2pZKhvbGmpYBAR2TpSbWsQ8pR6RSaXp6elZWFjloHw5y/k6gAEMq
Id7eVocO9ZwwoR6VCnN4eYG/uxr2POy0AoODpKouEokkNTVVv8hGpRyvXpHALmhI5YTDoffr55eT
U+97b6TO3vLH7lbDh3lYsZ6c3pMqrGelSXYPbGilG9kkjnkUrXKo62X/Pb+QkZGxadOm77WzTC5f
vvzV1+DyG7fC/GtXe3TnZpaC3r17x58WHTs/y9qdmbtkyjJRp4HB9DwZYt6wTi0aBdFqFA9u3EjL
1zjX8PH3doUfjays5ObmxsTE2NjYkN8OoVAoYAN2RH8zUIAhlRlybeTvIfX2/pHzJi6t02VyM7P6
XYdgQUMdH22pNXTpyU1TtbK0ul71Y9mdc7MOm9EqWx0kjz7RskU/7fuhQPvfZh5v3eWgdT/JrREH
V695uXoNsc4Wgg5bcWbDmPrj+3X568gN8uvEs3ffXdCvbmVLjh+PSTQl8/PzExMTganmOpjMyvUJ
6goHdtBBIGWhVmHgL59NQ8i5jUyroCCPc1um77mR8OjM+hg1PuD30XxqJZQbXCPHtVozK7t/9/wF
WjgSqeyKBtMyKRpJ+msEYbFtlm3+x01A3zxl/KG/Fm08cr3ByMVrp/XQ4nh4fApiAlIC+RYUCgVo
BEskErlcDuf7fj+wBQyBlA0hrm4OAgRREpu33v31bMGJgH6LJ3Rxefmczub93q9BJe6B23vmUfva
5s5OPgE1zacDXc3DqBxzGwRxH7Nlym8d26AX/IcduHbJFRy5s2n2beIDiN7rR7atxAlSxcEwDEiv
SqXSLx1jaItMG9gChkDKhlhU6/mb9MK9ej6Wfj0HdwmJCXt2TYPXH7nf1rwy98IxWAyExqnfpAmT
FFUeSjWzdADt46wCRIudWHYNSK8Mw0A17Bs47tmbGFXBzYg3kZihzYb8IMiFruCCZeUFbAFDIGVh
H9jSCkH+GNhinyUVwzQIA2gN9fd5E3Yc70vn2x9Y1O77Bxzx+Xx/f38rKytHR0dLS0uwy+WW5xwq
UGOWwzAZ3dtg5P1tHu8bFvJ42bPodMfGo0YP9Nh36Wp8zPnJo569vHUnE2ucobxiSYetYAjkM0AB
hkDKgmYVtH7bipNXH+J0nqeztbxmDQqCpDyLB4eCO02zY5dDHxKbzfb29nZ3d/f19XV1dbW2thYK
hd9/Wz1qtfrWrVtfexVd4BHaqoOdBZvcRens1ePGvPZoQy5ryXfwdatm79eg9fyF851E3BcOTlv/
vZgnV3mPCuk/chJUXwjkS4ACDIF8hp+HTOoxWP+ui2hMbjp9HGcJV60cakizfjAM2ybnLjT+0HRG
aQPmLyU21Ingj3eX6f8t66hfkbBWkx7rGncnR0FD7YVAvhD4DhgC+TzoB8Be5osbD2s3aRdiXZnf
/iKliqmWePuHYu9To8jZUH0rDm38u/DIxAxDmwH5LmALGAL5WiynLF9t1fgXStWUG7rDzC1rLBs3
NrQdVRpcrWjUqH6S10Ds5lrT+NozpCSgAEMgXwvabdA4Q9tgQKjdfh1raBuqOhQa68KFCxK23Zf0
Ycry8zR0Lp9FVanVDAbxEj8vO4crElK1uBqnMKCAGw7YBQ2BQCAmBq5Rjho27MT9cBRBHp36x8vR
ysLCvmlo51uxYkQj2TBnRJCft5dX7S69+otl0l6NHLy9QnzdbJlsTujonbLk6w4WopAmrWzNqRwW
Y+fNd4aOTdUFCjAEAoGYGDimeBv5NjVLLEm417fTkFSZdd/e7WJuX4iJTF81oNuYxZvVwuqegvwT
B/e9jBfLpdLkhLAUhU2HQJtLGxeI83OkCBJ264ptYAcbTL1g6y04pddQQAGGQCAQEwPXSNUqFYoi
e5b+GYWY77h3e/3G7Ykyxf9amO/Yf8m9Yd+wGyen/xwMzqzmJCIu4Fmdefaon785gsQpMeIbgpaB
oQ/P76CC/eQUuJyVoYACDIEYmOzs7LS0NLiqH+SrQBGEQaG8kmRa+dbr4klMHMdUSlz3gd5qTlwK
sW6K7mO9qpTkGKRBy4717KgZcXEgIP3Fa/C3w5C5NI0qk7hMA3OeoYACDIEYGAzDjh8//g1rZUCq
OEoN7se3znx92W/w7xf2rXG0tFq49xwLQa7dfnjt3vU2c06Bc55GpKlAe5dXG0FowW3agxBxbg74
6+hgQ2WbNQNbt+8pNAaNRhUGCjAEYnhA8/fUqVOLFi1SKpWGtgViAlCoXBqdKeIwBi1fN6id/+sd
s37qPzG9wK1N405rD/6hTnreokFziYJYk/tsWIqLPYIjCrDtHBQA/qKO1cFfPoeBUFiNiYCLBUr4
FtgwwGlIEIixcOfOnV9++WXXrl3luxQlpPJBYwlikzNpbB6Ngv59/N6ihDi1lmrn6sqkUJAa0yTZ
g9JzFdb2DvLUaIqVC/XnNAqXyFH2Tce/ed3F3dMzLbW70NoWhEy4HNclm2HLgS0xwwAFGAIxIl68
eNGhQ4cDBw40atTI0LZUNEUXG4N8FhaXT26gVLqDW/Wih7hCa3edC8dzraHbtyHDKRSOl48P2LCx
tSVD2CIXH1EFGQz5FCjAkMqMo6Nj+/bt5XK5VCqVyWRKpZL8irih7fqAWCzWaD56BZecnBwaGrpt
27bevXtTqeWzSsLq1auXLFki1aFQKDAM+4bPyaWmpha9Cthm+74e/06A6FKAOHA4TCaTRqOBO0MZ
hlQFoABDKjPNmjWrWbNmSkpKnI6srCwgxkB+DG3XB/Lz80+cOAGcg6KBwMj+/fuHhYUB1SSXLvoe
gJjt2rUL6Hp8fDxIBKCjEolErVZ/rSMCbgKu0u8CvWzbtu132kYC1JfP51tYWIC/LBYLCDAIKZc7
QyDGDBRgSGUG1OOgUcXj8UQikUql4nK5QEKAABtPIxioY+3atdeuXQt0sdihlStX3rt379KlS2z2
/9k7D/imqreP3+ydJt27pWVTKKvsvQVZgiDKFBQURFD2lKEI8pcXUZaAIEs2soeAgGyBsldL9947
O++THAixZZQ2zU3S5/uB9Obm5t7nntxzfuc54zmCcl6Cw+GAsMnlcqVSCS4mqYW8bSIUE0U4T5Uq
VcpjmPmZQc6lUqmrqyv8RlDnQAFGKgMowIgjA74UCA+oL4gQyHDZhKeiASX7448/1qxZs23btmIf
XbhwoUGDBocOHapatWqZzw9iBgIsk8kgESA1wNGEWkgZmqDBTvO3cM569epZqq0YRJdoMNgJdSZs
hUYqAyjAiCNDBBgUCMRDIpGQvk9bE2AikD/++GOLFi0mTZqkUCjMP3306FHLli1/+eWX/v37l+38
oGRw++BZQmrAa5k7wot1SIPNwcHBlpJJODlx0wEQY0t1fiOILYMCjDg4oD0gElCgCwQCnZGynQc8
VPPv1qhRo0OHDhaxkJgHMjxq1CjwdOE1Pj7e/IDU1NTBgwfHxMRMnDixbG2zcH6iauBcgvqWLRGK
XRreurm5leE8rzo5ABbiICyk8oACjDgyZHgt8YD1Rsp8qlmzZpkPVx4yZEjv3r0tYaMB0wycLl26
/PPPP926dXv48KH5AeC2gnP89OnTJUuWgBf7tueHFCAyDzJc5ipIyXNKJBKLnIrAMMOCp0UQmwUF
GHFwSGlu8TKdtOta9pyEgICA8PDwd9999/Tp08XEcuXKlbDzzJkzZZj/YxK2Mo9vKpmGFZQCCFJJ
wKGGCGJz8Hi848ePL1iwoKTmgWdcq1atO3fu0GIYgiAWBAUYQWwR8FNnzJixb9++kg3O2dnZrVu3
XrduHS2GIQhiKbAFCUFKRZcuXcz7gENCQqxw0d69e58+ffqDDz6Iiooy35+TkzN27NhHjx59//33
OGDYYZg4cSLdJrwBMqgC++ktBQowgpSKw4cP03LdJk2anDt3bvjw4adOnTLfr1Kpli5dGhERsX79
emdnjOdr98CvCfWq2NhY+E0jIyPj4uLgLfzKlho0V35Aelu0aCEWi4VCIZvNxmAp5QcFGEFKBY1V
fl9fX5D/kSNHbt++vVhxvH///nv37h08eLBGjRp0mYdYBDJM3RS4TaFQ8Pn8soVMqSBAcUUiEdgm
kUhAgzkcDk4YKycowAhiB0C5vGXLlkaNGk2ZMqVYLOsnT57Uq1fvzJkz4J3QZR5Sfsi4ehA2uVwO
PzGXyy0oKLCpuOUkkppUKnVzc4NXIsB0G2XfoAAjiN0wceLE9u3bt23bNjc313y/SqWCnXPmzJk9
ezZdtiHlhITsJlOrQYZdXV1J+7PtBG4jFkJdkEQMFQgEJMoN3XbZMSjACGJP1K9fPzw8vFevXnfv
3jXfD67SvHnzbt68uXPnTpyea6eQeG0gaUTkiPtrOwJMGWd+A2Ae2AlijN3A5QQzKoKUismTJ5v3
xjVu3HjQoEG0WFKlSpVTp06NGzdu165d5vu1Wu2+ffs6duwIGuzh4UGLbUiZMYUqIwHMSbxum1Jf
yiykmiliKHrA5QEFGEFKxbJly8ynIQ0dOpQuAQbc3d23bNlSs2bN7777ztwq4Ny5c1A52L59e6tW
regyDykbpBsYGzAqD9iAgCB2CbhK8+fP37hxY8mAzPHx8eAHg39sa/4TgiDmoAAjiB0zePDgmzdv
gkNcbL9KpRo4cGCxZnMEQWwKFGAEsW+Cg4MfPnwYFhZWbD+4v8uWLWvRooVNTWVBEMQEdjYgSKkY
MmSIuTfZsmVLGo0phlwuP3Xq1OzZs5cvX26+Hwy+cuVKrVq1Tp48GRgYSJN1yNthg2OvSoLjny0C
CjCClIoNGzbQbcLrkEgkS5curV69+vjx44sNy4qIiGjatOlvv/3WvXt3usxD3sjEiRMDAgLotuIN
PH78ePHixSwWyxQGC0dBlwcUYAQpFbZf0LDZ7M8//9zPz+/jjz9OT083/yg1NbVPnz4//fTT6NGj
bf9GKi0TJkyg24Q3MGzYMHiW+Hy+UCgkgTgwGmV5wGYEBHEoevbsefPmzbp16xbbr1arQZ5HjBih
UChoMQxxAPLy8uLj49PS0goKClQqVbG2FuRtQQFGEEfD19f3xo0bnTp1KrZfr9dv2rSpYcOG+fn5
tBiG2Ds5OTnR0dFJSUlkpSYSLYRuo+wYFGAEcUDYbPbhw4cXLFhQsnnwwYMHAQEBjx8/psUw5FXY
hZLl5ubGxcWBBwyusE0tlWinYB8wgpSKAQMGmDe4tWvX7osvvqDRnjfC5XKnT59eq1atDz74oNhM
pMzMzKZNm27YsKFv3750mYfYIwqFIjs7m6yWCA+VTa0VYY+gACNIqdi7d6+5AIvFYhqNKSUsFqtf
v34XLlx4//33Y2NjzT+CYhSqFFOnTn2pl4wgLwVEV2lEZwTVt5xgEzSCODhNmjS5cuVKydDQUJh+
9913oNAFBQW0GIbYHaC4pN8XG58tAgowgjg+np6eZ86cGThwYDFnF0rSffv21a9fPzExkS7bEKTS
ggKMIJUCNpu9ffv21atXs1isYh9FRET4+fldu3YNWxQRxJpgHzBSKSi/tIwdO9b8JGFhYRaXq4rr
i61WrRqxFl5BgEtO39TpdK1bt/bx8XmNDVlZWeZvExISqlatWk7DzBszoR5AAhxinzRSSUABRhyZ
TZs2icVii8Stbdu2bbE9+/fvL/9pgeXLlx87dgyMBGkkC55b5LTmgOPboUMHi5+2/JhutkGDBvn5
+eCmkxiHFZQOCGJToAAjjgw4WH369CnZ6GpTLF26ND09ncvlCgQCeCXh/Sx4fkgEu4jZm5SUJBKJ
oMJEYhziuvSIw4OPOOLI2EWnplKpjI+Pl0gkcrkc5AeU0uICbMGzVRyQCM7OzqSRHDxgUm+g2yj7
QKtSUFw+PDRaSD1MNPsBB2EhjoxdTJZQKBSxsbHJycm5ubmwbfH4uvYiwJAIqampGGLpbdEXJdbj
CbpPW9srTM5mMvdcuLNuzviNJ++QT28eXvvZjBUx/54UugRFqw2HD+/RavrqQ7SajDwDPWAEoZmi
oiLQHrVaDU4wWWTGsue3FzGLi4vjcrkymUwul2OU/9KjVebep6j7i0eTt9O+WyI5suWm64n30x6K
KO3wz0bf1nTt4JtVlJmXqaICOUUXr16oUxvk+V16zUYo9IARx8YutAekFzy/rKyswsJC2LYLmyuC
fCMY4LCMcARnHyd91b1VRIxiyapvqPRHtWr8GP7LoNtx1LhxYzw4FCV3ChYaDoRCX1tJHzGbAwUY
QWgGvD2lUgnSW8m1R6VSQQpojVTaRCgDRdk58CptPbZFVc9IZR6lo1qMGNe9CpUQMbn7xP0UVXPs
mHcMx+UXJiuffUWnx35imwAFGEFoBsSGCA+ZFFtptQdSgEQYptsQO0OjKILXsJ6D2AyqsdiZehCf
zXT5ds3PkJJJavWwxYtrOvP4EiGlztmx5/iRP3dnFFIcViV9xmwN7ANGEPohoovag5QBgZMcXuUi
DrxWdeFT1JmINGWLpr0oahxFuc0YZlgWunarTr7U5LmDu5GvoPzaCCjACIIgdgzfq+6jG5dd6tSF
7d7fLtnS4+tm3rwnJ/6Ct62mr67uYej4FfvWjyzMvHA53MnD7/Zf+/zb9qfZaMQICjCCIIhdw6ze
oCnZEniGfPReCGwc3/YTxRGumdDFdBBXIG/fvj1sNKw9mRYrkZJgHzCClAttUYFCpXnzcQ6I/szS
dg0a9EwowClDNoY+98T2cLGwfZCLiG5TkNeBHjCClB2dRlGtWkBqjaFZf/3IqXQDS3WPz4TfCs9R
aHQUZdPBPisdDOm2uJgCrgefVekeSvsCBRhBXom2KE/J4gu5HNOeorw8jlDMZlI6vZ5pWD+BM378
+DTXxkwHLejSYh/9e/uJyN2/VZN6TF3R2fPh9UOrXrtwLkPB6dev5zsL9h2Z6RHEz/1xxtK6Az9O
ubD9SRo1aeoMCR8LFpqRufvL6LYBeSOYTxDkBZfOHPht/ZaEPG3bbv3GffL+sJDa+1wbTGlXJTo+
r/eQSe+186ge6Ne2/7gHp7fdyuJu3PfXRy1871693mB4V3AAE+9f+nTEiIeZgt6Dh3/91WhvCb+U
F01NTV29ejX1fGmgTZs2DR482PwALpdrPkD6/PnzzZs3f80BERERgYGBZU2DFxzcuKDvqG90OkNM
Zq+OXz5YEdaxw2D98zHb2x6m7e3UZ7fX0Ozj/b9e9D0F/4w8Etb/Y3Kv8l8dQRwe7ANGEIL+5vZp
rTr12Xn80oN//5n6+dDND3M4Wp326sGfVm86dnjnB+93SSoqUikVW9f+EJXLcNEkzf18llajPHH2
1PVHj1XZj98LbX3yVqpQoFq78OvT16Lf7tpGyCzYkvOAtf/ljQeUJxVMqJLODx85V+7R9vyt8JZg
YZxGpy0C46RuXts3r4SqQn5B4UmNRs9nMxnGK3IEX6093lUq3rH7ssoiFiCIo4MCjCAGdCrFexNX
63S1rzx+umn+Fwyx54Dq4is6DUV1vB+f9vemJcz8hL33n61I/9etxyNbBylUd7SaXGVRIezZ/82i
qxrtopO3bt++l12k+KhDTVrvxgLEnt6Xpac2HtjasraXgEGxQxuxjKXFlsPXBg4c+s+ZvwfXcdJT
eipbTVzvsPadlw5rflmvpXRYrCBIqcCcgiDPAL9S0HNgNZmhx5fBZDCZ7K4cLhUW7CFmy739KCZD
o0hSFun7zP61vgeVFP3ItFgej8U8mxHnXK3j2Ja+8JbFZjtAj7CqCGobeo2hc1ufDRWUewnE8eby
uRRb2LxNGx65fSkz49ET+Ntm1GIGi92QyaIepisx0AOClAIUYAQxYlATPTt8+/kb4fuObNXlph6O
zOFTDMa9oxu275g7ZoZex/MTGaLYt6pZh8kQBNcPKyhQ6YxKo9TqggROmfE3Pv3f9n9P7+nVsf22
v2/QfDvlpkr3Ic4U49O+rZs2an5Nq0uJ/Sm18L9Ny89bwjkiQ6gHEY9DMdl1DW3T+9LzcWISgrwZ
HISFIAaYHP7asSMHzF3WPqwRpTe0qo6duHsYeMWF8WMHf6jX61sNnNCrVhCfD7pjUBe5n092QUIR
g81isUVc9sgZ0w5cu/n71MGbDcLkM3ThWywpKBKJqlevLpfLPTw8ZDIZbBc7YO7cueb9vn5+fsUO
mDNnjvlbOMlb3ftLEXh32PPrT+tO/aNjizq9OyD81hOhc7WunXv6uDy7NQZHuOKrL+9X7+5Vy2vk
8GFNq7lQDPbAee8/Pq0WcrFmjyBvBgUYQQiMLrP+9+TjsfcjEqtHmeEUAAAgAElEQVTUDGFnR8Tz
Av/o+C1VrfepDV9xuc7NG4Pjqz9z/qp/7Xpw9KDPvw1unyAXetx7HC2Qe/C5rFOX79y6fLFQx6nb
vIWMzy39hUGAw8LCgoKC6tatGxgY6O7uXuyAYvpaElDot73b0tB25Lg2H4+ljMOzoQYAr0ePd3zx
MYM95JtFZHPdbxvJRovx64+OrwhbEMQBQQFGkOcwGG4+wW19gg3bHmHelPYP2OC7t2jZhvesU5cR
0jiMbDn71ujmWwM25B7eZA+bJ2rUtrP1ra5QTP3cpg2k4oiOjqbbhDcAjwGTaWjeIK9IOUEBRpBX
oKdSKb0+V4NLFCFWYOnSpTk5ObGxsREREVFRUXFxcdnZ2SqVynbWyALRbdmypUQiEYlEHA4H3mK1
rJygACPIK2Cw1t26tVzDE2Ahg1Q8hrhqLJZAIHBycnJxcVGr1UKhEF5tZ31okFuxWCyTyeRyOdiG
Glx+UIAR5JXwxc6lDWeFIOWGzWaDAIPCgeML8lZQUPDSuCt0AVrL5/OlUqmrqysoMZfLhRoD3UbZ
NyjACIIg9APyBqIrkUhAccG/dHNzA/f3pZHRaAREl8fjET8YxBhqDOgBlwcUYARBEPoBJQM9A+ll
MpnwSnp/bacDmAAuLxgJFQVQX+IBowCXBxRgOyMmJoZs2FS9uJwIBAKo71PGMgjzM1JpAeklrdDg
ZdpU47M5xEjSY425tZygANsZ7du3v3r1qoM998OHD9+yZQtkaahZk7yNkxyQSghxggG6DUGsBP7S
dgYok6urK91WWJiioqKEhATStyQSibhcLiixg1UyEARBioECjNAPCHB8fDyor1arZbFYpI0LBRhB
EMcGBdiesM0+ofKTn5//9OlTuVxO5jmA+oITjK3QlQ3Gc+g2BEGsBAowQj+FhYUxMTHgB0skEmdn
Z6FQaMGqxoEDB2x/tiKJaUDCGlSEAv34448LFy6EdC4oKIB01mg0eiNa7dstW5Senq5S/WdNJG9v
7/KbR/o+yeAjSIrKM7oHHk6yYb9166CgoDp16mDNqWygACP0o1arc3NzQXcVCgVogwXHfw4aNCg5
OTk+Pj4yMjIqKgr0A+QHLmeRk1sEKLZ69uwplUpFIhHIT0W0vcMJN27cCIkAtZzo6OikpKS8vDwy
x/RtT3XkyBH4uvmed955p/wWguJCCsjlclN4h0rS/jF37tybN2/SbUW5GDt27JIlS+C5ZRmh2xw7
AwUYoR9QXJBepVJpWfWlnocWgmIdHGvw/8C7ggvZ1AQPUEeQXrkRqIJUUHQhuHE4OVwC6h9wRUiE
ssU45POLRwYLDAwsv3kgt5AIJASjKc5w+U+LWAHIVmlpafB0QUaDp9d2cpZdgAKM0A9pC4VXi8f9
gXIcNAOEB/QGxNjNzU2lUr1tu2uFAnJIhn9DFQHshFLM4rNQQNGhZAR5o4wK6urqStzfMnjAYGex
PaGhoeW3kCQCFOIyI2Bk5WmFtndyc3Pj4+Ph6YXKE/5kbwsKMOLIQDkOpTmU6aBqoEBEfW0quhCU
WWAkkR+JRFIRAmwKsURi/UNBaeoDfttTlfSAq1atahEjyRRwgRHSDWyR0yIVDQhwQkICPEvEA6bb
HDsDBRhxZMADhkKBiBwUEER9ba2VjAQBBsgQpIpofSUaT17LrL6UMRRwsT3u7u6WMJAiY9BImMNK
or629hyWDeIBw4NB+lDoNsfOQAF2EP7++2+6TXgzbdq0sfJoSSK9pGQH781mizyyzjlpd60IASYa
D4lQZukllPTOScu2pSC3jy2ZdoRCocjOzs7Ly1MqlTY1usIuQAF2EEQiUcOGDem24nU0adLk7Nmz
JJg7URrrlLNEzyqJU/UqSFKXP8FLngHjJlZyQHRVKpVGo7HBpSNsH8w8DoLtzwGAsjslJQXcUIFA
AK/EIUNfB0HsGjKCkkgvur9vCwowYj1iY2PFYjGZcmNqdKXbKARByo6pUwPVtwygACPWIyoqCqQX
KstkQBBpi6bbKARBEHrA2e6I9QABTkhIyMjIKCwsLFskJgRByoZSUfjGY/Q6bX5+kXFTW1ikrGiT
EBRgxHqkpaVlZWUVFBTggEkEsSZFKbf5AtHCvxNff9jpXd86u3uk5qnO/zRKJGweb0MxWx0TFGDE
epB4k2UOw4QgSBnRaeBl2fGrr6/zqgqzDH/0VGZKJEWpGZhHKxgUYMR6aI2QUBjo/iLIG4l9fDfP
EoFTOQJDiIzOQdVKOeuAY4FrIm8GBRixHibRRfVFkDeiTr0aElYvuGYDXze53COwcf26nh4ewTX7
Zho+1B1d8XVIzWAfH7+QBk2OPsrYPTOkWp1GYQ1C3N1c/FsPSom52DikhouTlMlkytzbJBrXkDy7
dHCgr6dEIn9v8grDe71q69xhNasG+Pj412/c/HJsLp13WylBAUYQBLFFdFpVXq4+LSI8IT07OzXm
+q279Wo4P320f+eV9MdHF/Ud/2MGy3tQj6b3wq+t238r6ea9iPs3/s3khwV4xUVEX7946vq9x03f
H/Xjwkl169Sm0lPhhMmPw4s8moTI+Pt2nsqnqOMrJgye/7vSJXRAu2q3rl/+81wk3Xdc6UABRhAE
sV3knh1ScmNchdQ3v53atXox7Dl5+d687rOUlNeRE0e+Htob9rzXh0TB8/r79PFpE8d+0K9brdrN
4P3R9csuxTJW/f6t1FjSc4UNb53b3SPIl4qNTC/M/r8vV/FENa+d2TN+QHv4tH2b6rTdZGUF5wEj
L0en1eiZbNbzLiO9TqvVMdhsrLEhiFXx6z9WxmTrGYzYzCShe00xRT26cLue4ZMCXzeJJsrQRax+
Nly5Tv0AF6fgz1p/ZHiTn/Lww2GfH/l92c4Td58cmgR7+i3d6Cniagz9P4Z1weAvh10k5nNydYbv
azQUxqWzMlieIi+lYEwjUdUP1prezxjTo37HnjrsukUQK6PQsDgyHl94914qR+pVg0WpHtzxE3Ip
Knfphm2fzv4FDln6v13FvrR9waCWH0z5+MtpAd7OVFRcntoQ8YZk34ZtRRT1ODJZ7cHn5Bck/X7o
WO+pG2H/pu1nTF/HjG4dUIARSqdWpGUYxl9oNEoyOkqXn/nvXY3i0imNUgk7dJQ+K+FJSkqeWo8T
AxHESvCkXoZGYaHwhR5yXerVpfJVl+cnP3GXi5Z89tGhv/+F3ZkXlxfEwd8C07whdw/vW2cO9Hmn
y73IlMGTpwZJebCze+dgeG3SqQ+83o5SLb33N6VRje79zt0nsbAn8vI2FptjzO+IlcAmaIRateCz
r5ftDwl2vXkn0jOozsKPGn6yYLMWvN24nVzBrq+Xz/t5wjcKw7TdpwI2T95nbeqeUSz7b6vCkdgW
oXImo5UWEREF38rPYwnELIb+jz92i/zqgCj/cDhypkbCk7glJqdlZOXyxU48hiojX+8iUA1TCeTP
S/SOn/yQO3BWfqGCJ5TIpWKwV6VUcozLOXu2HZeU8IGLpyeH6a8uys/ILhA5yZiq/AIdz0XKS+s1
10nK7TH/VO50tYRnjbuszKAAI1ShplCZn33rkWbyV5/839K1md5Tv11QZffP8+/mSxfMmdWqbXu/
Rdw9uzecu5Y5Y+GU6s3bMO1ZfSdPnmx3K7dotZaYCmoJIiIiiu2ZMGECLZbQwvDhw0NCQsgi05RV
ZJgvEhv/Mlp36kb2uHgHuRg3WFyBu4eAHOVtmOVLeZl/k8GUOMklZos1E/U1wvb09ny2xRd5eIoM
WwJn4zkomZNRFFgciRgnA1c4KMDIM/osO7qgW9b//e9XQUCjzz8dkHBw4dNYp0mTDGM3mtVrlB77
z7mY2ClTJ0nt3PlNT09fv3493Va8BVZbOLk0LF++nG4T6GTTpk1+fn48Ho/L5ZIFQG3np0HsERRg
hMqKjOL4Nfrt05baiC1aSq9VGfwtY7nywkfUQ0Fj/11D4PWSZRDpNgSxS1JTUxMSEpyM8Pl8kyuM
IGUDBRihdAyVUCgVUBQroIGYYqTHJlBUdbtpn0UQa5GZmZmSkqLT6YgHzOFgIy1SLtAVQCjXgKoc
DosCH5fnLxFRsdnR8GCwDOMvXjSvMZgsB3ha7KjfF7FBkpOTY2Ji0tLS8vPzVYaZtLbSN4/YKegB
I9SX8zePnKkz9u1KrzyKFcnc4cH49kDKFPWLQZAzv9s0ZrrK3juAK4MA2/I92nuPKfGAnZycFAqF
Wq225aRG7AIUYITi8ATy51Lr5e1LNoRSF6HZMTyR1FtkbcOQUtK/f/82bdrQbcXr2L59++nTp5lM
JovFglebGllWepRKZVFREfi+oL64oDVSflCAEcTuadWq1fjx4+m24nXcvHkzNTWVx+Px+XyBQMBm
s4kM023X26HRaEB64RWlF7EIKMAIYt/YixgkJiZKJBKZTEZGoXNfTEu1G3RG7CXBEdsHBRhBEGsQ
ERHh5uYG6gXSCx4wmRJGt1EIQicowAhi39iLQxYdHa3VakUikZOTE88I3RYhCM2gACMIYg0yMzOl
UmlhYaFarSbRQJGoqKi+ffvSbUW5YLFYUJcinfoY4uZtQQFGEMQagPQqlUocP2xOXFxcWlpadHR0
bGwsiHFGRoZCodBoNHTbVVpAd4ODg52cnMRiMQlOgt0KbwUKMIIg1gB0xSS9KMAEEDBwHyUSibOz
c1FRkUAggDqKHcX3AMUF4+VyOWgwGI+hwd4WFGAEQayB/jl0G2IrkFDSoFugvrANSgwabF/t80wm
k8/nkwoEvNrjyHZ6QQFGEAShBxBgodAQ8AZkTCaTEfW1ozoK1BvA6wXdhWoE3AgK8NuCAowgCEIP
4EGy2WwSmQRe7bF3nEQ3IzKMa0O9LSjADsKUKVOcnJzefBx9REZGhoaGQkYlwQhxwCSCkFZo4kfa
l+9rwrS+p/1GGKURFGAH4c8//0xNTY0xAlKXlpZma/Hi+/btK5PJJBIJn88nMox5FUFwUeHKDAqw
g0Bm44nFYmdn54KCAthWKpU2FbSWy+WC+rq6upLFzNlsNgqw7aMsKqQ4PB4bFQJBLA8KsIMAAgyq
JpfLYRv8S7JeqU0NpyQDPkF9QYOhogBGYis07WjVRRdO7l+1fjfDNfDT0Z+1aRh0+9TORT+s2Xn8
b/j06pOk2f0b5Hl16Rfm8ShBM2nBvGreErpNRhDHAQXYQSDyBv4u+L5SqZTMJrQd95cyNrWBE0zc
dKFQCBvY8kY7C77sOW/VKbK9fe2Pt6Pvvt9pUMTzT+8+TWewOReP/X7xmOHt2g3LEvI13iL81RDE
MqAAOwhkHAcZTgnaBuprU+4vARSXmEf6gM0/0un0YLJSqSksVOXkKCiqiMVSQxXCeB+GV+M22dBp
NHrYa3xLkT3PP3px5PMDXnwK51GrtUlJvitWXIU3Go3OeJgeNkyv5Hizt+b79cbrGrZVKpK2phrO
s/ASpjpPsWgT5m/J9vON1x35si++5Dxg38CBZfk5Mv7947tVp6o3GHn94k8TPD3X+wyu7i5gUhSH
y3tvyoqfxvWWu4rWpsYFNe955sCmqP3T232y5lZkinc977JcDCkFe/bsmTRpEt1WvIEmTZps3bqV
MmZnyljy0G2RHYMC7CCQsYggbGTDBtWXMjOSdACbsm56euGRI084nDSBIJ3Pf8zhSNhsEYNRQQ+n
76ZN4RVzZnooczuHWqlQU1StT74Q89iGX0LCYwmC9l49Mf3L8TsWfnpyy4pDf59x9fDlBfn5u8r1
IU2Z1BqqHJ0GRUd35AvY2WJ2hpCjYzNVHCbL3oruP+D/jcfUjWdv84z/SkleciE1fPgbjsnLi4qK
Kqt1VqJly5bZ2dlk3hFkZDKpgW6j7BUUYAdhzJgxXl5edFvxOn799ddr166ZplsU02B7BGwnMy/g
9b8bFNkw20mZPn2+8z/fNf9WyfO8Zg/8M/rBt8pyA3rQX6ow/M+4p7qLaiV15URkxO3D/9yf/svu
Prsmj1x09Pb9JBabGxn+5PS5v39fvALqdAI2lhgViE31Gb0KpVKZmJgoEomkUikJvoECXGYwOzkI
n376acOGDem24nUcPHgwJiaG5FsyENo0AYPLZXl6iiQSmbsBP4nEWSRyMmZshnGykuHVON//meSY
bRjyvumtcXax4VOyx/hFptlXYJduxYoVX3/9lekk5geUOP4/O8kZyOU4HChxSlt1qJg6xouTQoVm
xYqyCLBni35Dayz6fe03gevmGZtM7u/ZuWfBzPkquEmDEnhUcTeM6Yu/d7JTu7/0emajNhOaVHMv
s8UsDx+2XMpxl3NdnHhCPo/PZdlb9evChQtOMplUIpFIpfAAc7kcFrO0PeLs209efwCor202XBUD
BDg+Pp6EzySBROi2yI7BtEOsR2xsLEivVqslQ6BZRmC/VMpr3NgHqFu3bq1atTw8PCB7V0RYO7j0
xo3ZzZr5WvzMNFJ2FWM6b3r4eMr1q8k5uhbtWpz9c3f9Tr0+HzXi/JVwBte1Q+cWQiZzJUWFtH/3
fzPG81yC2zQIKo9gchu24letKgoJkdSsKXVxASWzu1F4Szt0aBjUsE6dOvCgenp6Orm4CASCUn5X
sHFjRZpmPQoLCyMjI4uKirhGoCKCSzuXGRRgxHpAvnVzc4NilyxeBlmXbosQdp1GLeoYt7r1HWD4
Iwns2TPQ/AgXb98unTpb37JKiL00QScnJ0PmdXV1lclkdrR4og2CAoxYj6SkJChi5HI5WfTULhrc
Kjl6nUKLv5K1sAsBhmxbZMR8fUmkbKAAI9ajoKAApFelUmG+tRfW77uk5srotgKxIUCASZQ9Ow1e
bVOgACPWA6SX5FvMuvaCq7c/3SYgtoVpXWeSizEjlwccPo5YD/1/odscBEEQOkEBRhAEQRAaQAFG
EARxfHIy09KzC0xvNSpFcnoGjfYgFAowgiCInVO0+MPQ5q1+0LyiV0dXEN2miq/Mxd3dw+NRukGD
N3zzhatM6uXm6vvFfuwKohEU4MqIIiNm+LDRkVlKug1BEKTcaFWXt9++c2eXSvtyMb25b8356IQe
Ixf8uXd/FbkACoBdO35judXYsOXAiZmd7CwamWOBAlwZSX58ecvmLTG5ZRPgwkWzp116kkbe6DXK
OTOmHb7x1ILmIQjyFrCcfr5zYtnaJTzj6hYFmQlH//zzyLFT8Zn58DYzJeHw0bsUJX9/YAuxsztb
XxRx9/ydhwXVazbzcxd6Oovptr5Sg9OQKh16vb4gL1df5spXwaP/fbsk37Nd06pdmQyGqjDnu8VL
GhSGdGtQxe5C+yKIQ6DZsnD4N4cL+vdKZ6beaN+ua3hMDuxl80Th0RED6vrfT4fsrh/RtRNHKFna
Qzphd6KOohJOru9ycv2Hmx9s+agG3fZXXlCAKxHZcXdH931/7630ql6ZOkpAMRkxt/75fskPB3Ye
SRV7H73+oFOQ4OyWxYMm/NLqvUEzp00MDfLSqQsO/bbm+M3I0Lb9hr3fZseEViNX/6vR678f/+6S
CUGLFvSePmuZVqe//tMw/i8jfj5yd3RnzMw0kJWVFR0dTbcVryM/P18qldr14lc2DMtZ4qfV3ler
daM//fxmdN7ybYdOfdjjgEL5NIu5YNnGJd+MvpZT7co/e10kzi7qiDzx5zM3/Nvn6w3/G9M2ILgK
3cZXalCAKw8ZdWvWiy809BI9jKMoIa+KE6dr8+6PEoxLmmbHHrgSHfjvuvZDl+n11K5ffzh+7mrG
7cMCoZNGqzUcsHrV3p3r+8lzNRrDW51Oq9Pl5Ko15FO93rC+vUKlovH2KjMTJ06Mi4uLioqKiIh4
+vRpdnY2CfZpmmx9+/bt1yg0h8Pp2LFjKVe/ALG/cOHCS8OIgr6GhYV5enqW3C82IhAIeDwek6wq
hVgMhtzNmWzlJCdSlPbLD3vAdrPxy7vWcOPUHPLXsd8eXWfUrx5sXPsibOKsWTM39Kldv14Qqi/d
oABXFiK2zwT13Xs+sndz/3Xf9B299CKl1xo8EpHzR4OnfDf7AyeJpK7PKr1v35h726RFGUnZ+uzo
K6Cvfaf+35qvBn7Wu8WVqC2Hd9/7eE1WkKtri/HLt3wzjsWg5kyaK5C4aEInFF75QcDGUpUeWCwW
yCconExmWNIRRE6pVGqNdaOYmJi///67qKjopV9ks9lt2rSpWrVq6RXR29sbjj937lxkZGSxj0Dv
r1696uPj07VrV3M5h8cMpBdsc3Jygg1cQdbiOAdVUav/Ti9U6DWGitH0VbvHvteBnR39ODarToBh
TcmsrEIl1LrNvhITn02TscgLUIArCfroxxHwJ7iGD5PFlnsGUNRFKLf/3L5u6mfTt62ZfuzPrVsO
b8pUqeYvm+kn4TMkPjJ36v7xDfCVsUMGuLl7entKlRE6KEpZbK5hDXgWg2X4Q7HYLMN6eAwOi4VF
Kj2QZVlB2EDe3NzcQAVB6lQqVWJi4v79+8EtftUXmzdv3q5dO/hWGS5arVq1O3fu7Ny5k8i8OQkJ
CXv37u3Zs2edOnVMFvL5fKgfgHlSqRQEmGVcabkM10VeCl9GfkRGtwZV/76fsv/XJWc3zL947Xbz
OUcuznuHQTEpAcuU3EzK6AlLOTQZi7wABbiSwKjesBFFnZo168fJHzb+Y9dpg2rqcs7eLpq5/Ujv
zcs+XrL616PRcNzJPb+9X19+/8rJq3G6CT0awp41v+zjvis6+c9t33ojmFhm2h6gZODIgrzpdDoO
hyOXyzMyMkAad+/erXpFpwDI54gRI+rXr1+e68LXO3fu/OOPP969e7fYR9nZ2Vu3bu3Tp8+wYcPA
JMrYyg0aDOoL5gmFQniLAmwR/jq8W+neKEDmS+n1eWrt1E3HpaFLz1+/p9GzxrXq9s30TnBMYUZa
gFcV08LFmU8NdfHmtbH9mX5QgCsL/j0XDux0bMfaGQfXGt8zpWm58dO/+jhDafBgeGLnzm0bNeve
cdbOX2pt/wX2BLUeNOfLte3qB+1aNXbXKkrq7r9x8UJjkcnQg8dLFSs9mTidn0ZAgMEDBj8YnMtr
165NmzYtPT39pUeC/o0ePXr48OEW0b/g4OCWLVsuX75848aNhYWF5h9BbQD84CtXrqxYsQJcYXB5
QXR5PB7IMHrAlkP189wvzuVW/+3b7pDi2QoNxZJ9NnnuZ/89aNHPW+ILRaa3Xu0/+edMo4atfa1s
K1ISFODKA2f7ifDFD++m5KuDa9XIT8308/d7Gv347MUbSo6wVesOnjI+1er4hxHhF8MjPQNDWzas
ymQyTl9/8u+Zo7HZ2pbtO3k6ky4k0ao1G4Oav0tOyuCIbx7aklelPQ+LU/oA6QUNTkxM/PDDD69e
vfrSY0D/OnToAEoJKmjZqy9cuBCu269fv5SUlGIfJSQkvPfee6DQgwYNgusSGQZrYcOyNlRWuCO7
vffntyv7DDjH5LvVcHv5pF6PoLoe5u+ZopbtWlvFPOQNoABXIsDnCKhVN8C47SI21IilnkE93wsy
P8SnaoP3qzZ48Z7JDOvYI+y/53nn/aHmXwnp+kGFmWx5HNLxgpuaPXv2smXLXtXm7OrqeuLEidDQ
0Aq6/RYtWkRFRYFvvXnz5pKffvnll7///vtff/0llUor4uqVmZ7zfzoQ6Lnm0J2Zy9YFQh0asStw
4AxSuXjp/Bm7Zs+ePb6+vosXL36p+oKv+ccff8TFxTVo0ABcT0aFIRAIwL0G/1sikZQ04/r164GB
gb/99lvFp0clg8nqOWr2of07m1fByo39gQKMIPZKbGxsly5dBg4cmJCQUPJTEMXhw4dHRkbCAXy+
NXwjEPiwsLAHDx707du35Kc5OTmffPJJ//79i/UWI0ilBQUYQeyP7Ozs+fPnBwUFnTx5suREICA0
NPT48ePgcQYEBFjZNh8fn7179/78888lG5zBVPDXg4ODT58+bWWrEMQGQQFGEHsCNOzgwYMhISFz
5859qfS6urouWbLk+vXrnTt3tr55JsaOHXvz5k1wiEv2OicnJ3fs2HHKlClQjaDFNgSxEVCAEcRu
SE1NbdeuXe/evV/a5sxms9u2bRsfHz958mRbGGYMDvqlS5e+/vprMhW4GD/88APIs42HsEaQCgUF
GEHsAHB2Z86c6evr+88//5giPJsDH926devMmTMWn2VUHqAeAEL74MEDDw+Pkp9GRERUr1596dKl
1jcMQWwBFGAEsXUOHjwIQvXdd9+p1eqSn4LI/fTTTyBytWvXts1JVsHBwffv3x8zZkzJj+COpkyZ
0qxZs6ysLOsbhiD0ggKMILbL48ePu3fv3rt376dPn5b8FOR21KhR0dHRX3zxhVhs0yurOzs7r1y5
cv/+/SVDT4NDf+XKFahhbNq0iRbbEIQuUIARxBZRKBTg8jZo0ODo0aMvbXMODQ09fPjwr7/+6utr
HzEFoboANYnIyMiePXuW9NTT09OHDx8+ZMiQVwXRRBDHAyNhITRAQjfQbYWNotFozp07N3DgwNfE
c54wYcKcOXOsbJhFcHFxOXDgwPfff79o0aLc3Nxin27ZsuXMmTP79u0LCwt76dcdG3d392bNmkHd
q8iIWq3WarUvrX7RiJubG5fL5XA4bDYbl3YuJyjADkJSUlJMTAzdVrwOlUpFAvFDvmWxWJhvX0pi
YuKIESNOnjz50mIX0q1z587btm0DDba+bRZk2rRp4Oy+8847d+7cKfZRQkICiNCMGTNmzpxpnfgh
tkOnTp1CQ0Pj4+OfPn0aFRWVkZFRWFgIFTLb0WDItiKRSCaTSaVSHo+Hq1qVExRgBwHybWZmJmRd
KL+io6NhG2rQNlV9btSoEdSdQTkgA0O+xfVwSjJp0qQVK1a8Kp4zpNvdu3cDAgIcI918fHxu3LgB
fnBJV16n0y1cuHDdunWXLl0KDAykwzp6IOtZkaWdXV1doaoK3vBLZ3vTBYk5CrkYLCTLStrChDf7
BQXYQQBtg5wAeZWUzlBFJVnXdgQY8qpYLIZiRSKRgGeDAmWQdyoAACAASURBVGzOiRMnxo0b9+TJ
k5d+CkXeDz/88PHHH8OGlQ2rUEBgZs2a1a1bN3CFwdsr9mlycjJUK+fNmzdhwgRazLMykB0gU8BP
7OzsDNkW8khBQQFphabbtBeAkeD4QkaGEgbsBGvhR6TbKDsG085BIFmXtEyC1BUWFkLWtamFB8BC
KFNAfUGDwZmDmj62QgPR0dFfffXVvn37XnXAwIEDwR2sWrWqNa2yGlCgk3AcX3zxxaZNm4rVF3Nz
cydOnHjq1Klff/3V09OTLiOtBskj4FxCFpZKpSqVCtTXpnIxZaw2QeYF9xdyMZQ56AGXBxRgBwHE
DGqmkHXhFbKuafiG7XjALCNgHuRbyL02K8DLly+3WqIlJCSsXLnyNYsTdO/evVmzZocOHSrnhUDe
TMsWlfNUZePkyZP37t17zQHg7LZo0eLChQslP4Lbr169OrjCFW18UyM0phJZ15m4laDEOiO2k4UJ
ZDln83FYdFtkx6AAOwhQZJCAfyRvkHxrUwJMBkxCjuUYIUvj0W3US4AUs2ab5w8//FDRl5DL5cOH
D2c/h5aRq9u2bXvjWoS0NzVPnz49JCSEPKLwcFr/EYXLkSGKYADIsE3lXxOmmpxpdUu6LbJjUIAd
BNKBBFkCsq4N1poJxfKtDWZd20y38pOUlMTj8YRGuEasrMF2kbD5+fmpqamgfKSLBLB++6opj1j5
uggtoAA7Dph1kVcRFRUFouJihDJ24+FzUpLs7Oy4uDgyBkosFhNnlG6jEEcGBRhBXmBTI04tCAiw
TCbT6XRk7ia8WnPwqm02pZYkKysLBFitVpMOTvJKt1GII4MCjCAvsAudKAPR0dGurq6guyDD4Apb
f2CtXSQseMDx8fHg9ZJUAmgxw/brK7bZf2SPoAA7CCtWrLDxTAuMGzfOxrOu7adh2cjIyABnLj8/
X6VS0TI/zS4StqioCJxgZ2dnpVJp/VSaOHGiNS9XNuD5Wbx4MdRRSPu8jWdn2wcF2EFo1qxZw4YN
6bbidTRt2tQ0FpeMF8OsazUUCgUUnRqNxqZis9gakD5k/h5dqbRs2TLrX/StgCyclpZGBvSR6VKY
kcsDCrCDQGbZ0m3FG0hJSeHz+ZB1TUGhMetaB3DmQF1scHKaTQHJYkolm51KQC/5+fkJCQlSqdTF
xYUUOJCR6TbKjkEBRqxHbGysWCyWy+XOzs5kwLbtVxocA5OWoKiUBkylV5GdnR0TE+Pm5ga1Z/CD
If9CWmE1usygACPW4+nTp6Y4tyTcAQowghDsQvVzc3NBgHU6HTjBMpmssi1XZXFwLiBiPaKjoxMS
Esgia7YWqrqcqNWaijy9Li83ryLPb8coCwuKlC9fPwqxOAqFIisrKz8/HzZMzfV0G2XHoAAj1iM9
PT07O7ugoIBEmXeYdtHbW6Zwua3iK0wFIs5sljoF3yp69lapUFbUlewM/YoZH7uIxEJ+wOU0jU6j
PLZxzfRpX02ft/DEhQd02+aYgOiC9CqVStuMU213oAAj1gPyLRmLS3Kvab+9u8IJkfcpqkBXYWVR
YX4KiA3TmEjp19bzBfyDD7Ir6mL2gybx+NRFv8mC63721djqcvaF1aPfGTFm/eY965Z+17VV7Y3h
mXQb6IBAViULNNl7nrURsA8YsR5kgodpLC7d5pQXvU6bl5unopjhVw3tw3pt4flTl5q3b68sLGBy
+GyGTqXWcHkCDpuZ/uhqmrhasCtfqdYJBXyoiFAMpkDAf83YFbVKqdZo2Rwel/Oin7wgJyPq4U3Y
eHA/qplnFTe5rJSm7ty5s1y3agk2b95c2kP1+rz8fJFYzGQw9FpNoVItEhoWQlYpFRqtnsPjcVhM
0IGHezYWUdRve0+2ruHMZ1M1Oo+YuqjjvMmDGUlneH4dd+2+MLx+zwq8HwQpN+gBI9bDYdqcAb0y
Y3igv6tc7iZ3nX3sHBUYnHFha5tOXXz9/d1d3Ty9ff18fDzc3cO69NFrVa06dK/XsKqPl5ebm7t/
gD/sd/fwPnQ59lUnP7Bhjp+Pt6enp6+f37LDt5/t1amC/f2bDP0FNqf2b+hZtUmudW7V6mQnXnV1
df3fsXDY/n3heHeP2nfzVBsmdPPx9oI08fPzPxJ+LzDAr81MwyLKfZpX9/bpkKim3Gu0nfdpo/ED
GwY27A/76zSoQfNtIMibQA8YoZ+8POW1awn37ytv3NDK5RkCgYzLFTOZbJBp44xMEpzvWYi+52/1
L/0UNkwO9su+q8/KatS16+bnhxU/lVarHjCgVDb/sWLW73Hpoxes7BjE+fqzT+K4HA5LByKZkpBg
+FiZmutVr0tzzonzt5N0enDUNKmZ6cYvJiYUvjdyzPEtq3eeu/puM38GeM7aZ816XB4PfL6bf67t
PXIBl99o5f/1+2rMjIf/3ulCIqww2Ds3b37y6PyoKf/X4Z0ZX45tJ66g34NuhFI/lUo1b8z/Rj9d
tX3VZoFP/bRdX49cfrxq64GjW/AnL9506kb60O4dvv11Kxz85cxvAv1ruhljNkfumr12T7jxHNL3
W/nTeQ8IUgpQgBH6Uam0KSkFHA4nPT2DzwcpK2SzRQxGBT2c3IyMold9ptOVdjDzg6v/eARXWz3r
M9j+fd1PcXHP9jcZNOP4rBryOsN27DtSPWn3iVPTb6WQ0VnVj986tmN40A3B+N2rFwcc2n7630iN
nlo/qc9nPx4g360y4IeIHZNOHNwmcA6+F3O1CufhrDEzguvUpSijqDOYbXq91ySaDQJcs9c7vXq0
KmsK2DpcieemPiHD9m9dssjreEr+oE9Hrxo9nKKqnjv8u+7abyDA7do36vlxm6qZW0fsqTN24gQf
wbO2/Nqj92S/n7Jnw6KRk5dPHbX29MHxtN6H7aLXqIvUeqEAY2jQDAow8gJtXvSaTcfeGThYrnzy
x5/Xewwb7idmR17e+9dd7tAR7woqeMouk8lgsRgcDpPLZXG5bBaLQ4LcGUN2GDbIOsKmVcCfvzUd
YL790p2A/tGjR7Vr1zY/0rQ8Mew0CvDj0iSVUqlQKhn5ekrMoLTqF2sojZo5jcc5ChtRcenNfT0o
qujyfaPr27Rn27o+O3iifOUNBpPly+FeunK3SKfv+MHY791bUBTfyYlXq2UPJpxap9aKJVXETEqp
g/OqlUqK9+LCz9ruHXPRJhPMob9tnXAk9NvZSymXevMnvTttEezMlwi42TpDbUahMIwA0qrh5V5O
kdoHhESv2jh3VqxLj5nj2w7+ZPTcycv1epyb9Eo+H9xp801m5qMzqMD0ggKMvCDpn03jxn+zqm6n
apc2fT59+fauAwdWlfw6dtbiG1GhPbKaeZVr0v1rVvpzcRF27Vrdx8enbt26tWrV8vDwcHZ2rogQ
d2DDqFH7Vq2a/KoDVCrVypWlEWBW3Tadsw+schE079+m8Og/96mqNbXGYdAanVbgHwrCm/o0VlLP
G/b8+2+cQTeVcPvcoFp1D5xXgC/bWMK59OBujlJXLazL1LAu5qd2dvNQxe4bNn+1/NqsNIo6cfbP
Xj2l5bxxmUzG4XD4RmDD+usBx8TEvN0XZPXqBvmeexg/YNRHVSW8Gj5yKib5+1VrT28wdIGv/XXv
+z8OIwc+i8KkV51Yu3p7yg+X/xn+5NqheIrduWczy96CI+EfXCOoQIPxq2gHBRh5gU+X6U+jR/n7
eVMtlsR+ONnbTwI7v7t8YVhMQQ1PDHnzHwZ//ZOuIH/cD/sOXmY4yZz0TLbEu6pEInEWCUANjKrA
kHh4CnjcG6fud5W57HOXg+Ix9CzQaBDgdh0kayIfpuap/YTFGxY+mb3y2JpTuxd/zWSxnKSSf09H
qPs2k4hF5DgWR2AIps19u5+jS5cuXl5etY1ARcfNzU0stl4Psl6vHzp06Nt+a/P/fRHy/rcTvxxP
Mfhz7tz4xTdk2bSJLDZbKhFn3jtEUR/dMrTct/eQGCtqTPGGx/eP+of8c2w3JO+4VQdXjHbYJvrs
pPuzJ89et/OgQq0+fDW2e5hvbnrSih/mP0nhDvpsbIdavME9P/1k0/5OgUJt2vWBY1a2a+h2IdFz
+y8TKJ1m/vD3gkcs9nfzfr9nI45eFxf+94z53+7bf7rAM+ze3Yu1XVARrAomN/KC6IPfhA5bfSky
6d6v0z/55WJs7CUnBuPKpq87jd918lFyCz96lke1VdhD52z6YOpaPYPF5bB0OorFYmSkp3MMjnuN
07fCXf1qspy4SQnxLLFcyB65jsFmM6ixS3b2yVCCEPdZdj3+G42L60t0lCX23JeZWVBYZJiDxNIX
qnRiAS89/TOusSGa69MpNTmZL5ZY+3atjn/XyenpE7lcw/AqnsQvKzO9UKHicPlMvVqphcoMe8Kp
3bWy/GTPyzC+1DcrK1OpVFFMFs/4LcdEmd4ruM7558MYzp696xd1uPXw8TlFhhb5TZtWfLdyxc5z
Jx+OnHrrr/+b1KH/nrvRsTnNrp19+tW3X9Qpuv7D1kP9Gw7XHtzxUPR4QvdA/4Ydn50o+drZu8m1
2/rSdFeVFJyGhJjQP7pxID83S8+g4jNSc1VFDGN/oyIjr0iRHx3vqHNeygODy+NDWc9ggLNq8G85
z5rNGbXqhrrJQDAZTi5uYh6byeKwmQan2MnNu3bNKrDB5IjcXJ1elf3gfOCh8nkcJpsrFvIpBlzI
1A/MEEkkrErResjgmukog8URiURQ12Fz+SLD6CFGUId+n/Vr8p80ZDB5fL4jq6+hM0OTWUSx2JzP
vlsffv3GpJENF0yeXsR1OXcn+vaGsXBA2x4fTu5V5+HV42lFqVtj4gM7zd4w8UNKk7rw6307p32Y
r9MP79w4Me4hg0HpdAbNprxqL//95M2bNwe38KH53iofKMDIC5Ij4uEVlCJLmUtp9STUjX9QDSjY
6DUMQRACg+d56ObJd5tUXTVjZMf+w69GxyXFZvv5hbYOCeCxDa0BQqF46Ojxqvwn7Vt1zcjTLJz/
cUi3YQNry07tGvH170+pJpOa1nJjaCkWg+nkH3ph+6Kw/Ogvh3YeMGJKYi4OW7M2KMDIC0gv4zOx
LdLojENuuRIhvN6JSKDNLARBnqMuyPjnXur8DUf+WjkqI+r26SM3dYZlevWJGemHL92AAx5GptZu
/25NZ+rezTs6/7AejQMolnTQl6MK8vIzmeydv47nG0t9qGDnpkZHqOtsvfv4q8Z1n4SfPHg1ieZ7
q3xgHzBiQk98XuNgXj0l4rCMWuxStZrhjwZDvyII/ShSHo8a/NHz5TiE3t51P54zYNT8nT6ubmTX
rr1bP2g6dcnMEb0mbVq+eauMY8i+XXoOlo5eqnGt2r22L1SumRSHyWDE3T03bOjH5Ft8iWuAt6NG
drFdUIARE8w6TVtROw6LuOxqEk+GNIMMEGKzhQYh5r3hywiCWAFJUPPsrNhdB0+o9PLufd7xkgoo
akffodOOXI5s3K6L9uGpZOdGcFiPL36+2GJcWJNq5FsCr9CImHtKaXURGzKzcNfVGDXX1UXCSXva
8PDfN7huvt07dnCq6Jn+SAlQgJEXNJp4UDVez2YxA75d8+ECze+fNR21OeJJ9F8uFJV+J1JPNcGu
YAShHb7Mb8iQkeZ7nIMbDA5uYNjy6VvHuIfJETZv1tD8GDf/2qZtqYsX2XCtEjqsSmjFmou8GuwD
RsxhsA2jeSkGg8lmcdsMGqFXZLVr0itNp3dtVAfVF0EQxIKgACOvJLjNx5PHDJAKxX0Gz53Wqy7d
5iAIgjgU2ASNvBIGi7dk5R/f6/WGoMl0G4MgCOJgoAAjr4XBYDJQfBEEQSwPNkEjiONj5aUX7BQG
1jUR64IeMIL8h6VLl27atIluKyxJXl5esXWQrK80cMUGDRpY+aJvC4vFglRiG4Ft1GOkokEBRpAX
QJl748aN+Pj4uLi4iIiIxMTEwsJClUql1+stcv64uJybN5Nho1OnIKHQSiGLw8LCpFKpTCYTi8U8
Ho8WaVm5cmVycjIkbFRUVExMTGZmZlFR0WtWqCTEGyOQCwRsFxeh+f7k5PyrVw2h2dq2DXRysswU
dUgWSB+5XC6RSCCVQINRgJGKBgUYQV4AZS6UvAKBwMnJyd3dHd4qlUq1Wq3TWSYQmEKRweUaIu76
+PhJJFZaDZ1ICwgwqItQKCQabJ1Lm9sA1wUzXFxcIEnBDKjWgAC/vmZz7Nh1eA0MFDRo4G++X6fL
5nIN6wF5e/sU0+Yyw2QyRSIRpJKzszPYyeVyrZ9KSGUDBRhBXgClMJS8oL4gDFD+glqURidKj1KZ
KBAYBLhmzVpyucAi53wjcFN8Ph/UBaSFuHdW7hKGegwkJogupCdl8GgF4P5qNJo3VmsEAkN0YldX
95CQkP+eMA3OARvVqtXy9rbMyoxgJKQMpBJUU6RSKaQYCjBS0aAAI8gLoBQGAQaV4nAMi9+Br6Yz
YikBTk0V8PmZlEE5arq5WcZ1eyPErSd3BOJHlwcMlwbhh6uDwqnVakjSNwown38XXp2dfWrVqmW+
Pz/fic9PgY3g4OqBgTKLWEhqCfDrg510tRMglQ0UYAR5gakUJq+l8dLeCienPDbb4LG5glvnbr3Y
96B8cEdEhmnpAyZNC3BdMADkDRK2NHUaklZCoaE7wHy/TKYkH7m4QDI6W8pIUlMxgUPHS8IwQuGI
cQuBAuwgDBkyBGruFjxhaRyUt+LRo0eNGjWCUpgMMbXZ0o1IBdw7SIWlHF8TQqGEzTb8TBKJ1MnJ
Mm2npYEUl2T8s6kMtSakZgMGkOaEUiYsSSseT+Tk5GS+XyzONktGp5d/uax2AqaEsuCZ38hXX311
9uzZpKSkuLi4hISElJSUvLw8C44/KD+QLA0aNJBIJFDUQO6gZTi9g4EC7CBcu3YtNTU1NjY2Jibm
6dOnsK1QKErpZ7yGw4efkI0ePaqV08LGjRvLZDKpVAoOEHExbTP3EqtYRix+cii2wMuCDa4Ri5/f
ljFp29t8xZBWLBanWFqBJ08+4nAcJxl9fHwgd4CvLzfi4uICAmzBEfjlB34+MlDc2dkZcjFqcPlB
AXYQSO8aGWhTUFAApZJSqQQBLudpudx0suHv7//6I98IZFeoO7u6ukIpA6YapQizLoI8w3wEPmRe
qP9BRrbgAMDyAxby+XzIv1A5wIHiFgEF2EEgMQSgckoZpQ6yrlqtfuM8yzciECSTjTp16pTfQihc
IPeCBkPuJQ3R5TwngjgMpIMcKqk6nQ78S8gm4P5acACgRQDRhXKGzGqja065I4EC7CAQASa5AkTO
UpNn+Pz7ZKN27dqvP/KNkAHGAOReMhbXZruBEcT6mCZrkRnJUJkmWdh2BJj0IHCMQGmDAlx+UIAd
BFJ9pgzdY4ZWLEsN3+VwpGTDw8OjnKci5QsZXUzG4pbbOgSxKhU9hI1kCtKdZFONz+aAeaT5CtW3
/KAAOwhE3ogMW7DZCmrkZIM0bpcf5nMommYyjBgxYteuXSkpKVFRUYmJiWSci9UGmqpUgRTVBDY+
+ugjJrPQOhe1ZwbA/wsXLnTqtMR8r1rtQ1EtYWP06NEsVrZ1TIH8VaVKFfBNSaDKimi/Id3AdlE3
Rem1CCjAjgPRYMuek8l8Fq8YCh3LnpkWIInq1auXnJzs4uICjjgUprm5uSTahnW8jYwM15gYw4a/
fwCXq7TCFe2aGzcMr/AzBQUFme/PyZFFRho2fH19BQKLzQN+DaRq62QE7KnQ6dSobZUHFGCkEkGK
UYFAIJPJPDw8yEBTa061ZLO5RIADAwNFIluZ32mzmAS4WrX/zIJLSOAQAfb395fJyjvSsJSAbyoW
i0GAnZ2dwSSowOEgBqScoAAjlQjSxAfFKGVsDIeSlEzWslpnm1pdcPWqIRRl9erV5XLMfW9gx444
eJVKpSEh//GAWawiijJMkAsODvbystI8YHhgBEbIulI4CQcpP1gEIJULEGChUAivUICCAFs82OTr
SUxMoiiDAFepUsXNjW+169otBgEGtSvmAefkpBEBDjBgpYieppDafD4fZLgM0dyio6MrxjQbApKF
BOjAGB2lAQXYzoiLi3Nzcyvz1982NEdw8GKyYalBWC8FFJEUZ6bxWRUHGcNJClOtVvtWkRHLj0iU
RzaMy95ZaTEGewcKdKgqme8RixVkQyp1cna2ZCjK12CKpkmiar+twAwaNCgtLS0lJSUhISEyMhIy
cmZmJlnssuJstj7169d3cnIyramMjQSvBwXYzoBMm56eDlXpp0YgP5OV3SpIQiIinm107dq1Is5P
ICFESIzZMhRtbwXpBoarVND5X49IlEY2pFIp3DEtNtgd8HsVq/+JRDlkQyqVVGjV8FWU4fnkcrlk
ai8obmFhIWRYkUhkg6E2ygnkZVM3OZnrj37wa0ABtjOIAwcuIwkIRxmWmK3AXkyTAHt5eVXE+QlQ
NsmMkLEtVlBHugoF03VJtH9abLA7Sk69Nb2lZWGJMkOCwYEMg+7Cc+7u7m7NKXDWgUwuMDbwOJM1
G+zoB7I+KMB2Bol4BXVMT09PMoyoQivR588/26hZs2ZFnJ9AlqqFm4IqhSnIe8VdDkGsD+n1gMcb
sirkYhLw2cHcX8pYQIEGw22aFk1CAX4NKMD2BMnDpMEWNsAJVigUpo7MirnmPfInJCSkYs7/Ygle
UrEgkywx0yKOBwlxRV7hUbfm8HurYYolAjkam6DfCAqwnWFa0pxMilCr1frnVMwFnwmwt7d3xZzf
AGlXJ3UL0gSNmRZxPOA5h3xKnnCbjTRZfojoktFqmJFfDwqwnUEqmESxdEZgpxVycnmGXr8Rkl0J
ZNgk5lvEIcFRwYg5KMD2BxEqK4/jJcErEARBEEuBQ10QBEEQhAZQgBEEQRCEBlCAEQRBEIQGUIAR
BEEQhAZQgBEEQRCEBlCAEQRBEIQGUIARBEEQhAZwHjBSKho3Xku3CQ5Fz57b6TYBQRCaQQ8YeR1O
Tjy6TUAqO0Ihh24TEKRCQA8YeR1//PH+uHFHCgsdas1wGikqUmdnGxaTd3cXsVhY/X0znp6iSZNa
0G0FglQIKMDI63BzE+7Y0Z9uKxyHgwcfz5v3N2ysW9fL21tCtzkIgtAJ1sERxHqY1pjAxSYQBEEB
RhAEQRAaQAFGEARBEBpAAUYQBEEQGkABRhAEQRAaQAFGEARBEBpAAUYQBEEQGsB5wG+NXq+n2wTE
XtEbMW7gg1Quniej3srJyMAJZIjlYGApUBq6dOni4+NTEXkPzmn9QgRBkDLQvXv3Xr16MZlMFovF
MEK3RYh9gx5wqdBqtevXr4eMR7chCILQBhQCmZmZfCNsI6jBSHlARUEQBCkVqampcXFx6enpBQUF
arUa6uV0W4TYN+gBvxlsH0YQBEhLS0tKSoICgcfjgfvL4eAyTUi5QAEuFajBCIKkpKTExsaC9Eql
Uj6fLxAI6LYIsW+wCRpBEKRU5OTkZGZm5ubmKpVKtVpNb7089f7ZX1Zty9dY1Yaov/7s17ffvykq
a17UgUEBRhAEKRUqlUqhUJDeX7onL+h+GfnRuM8/OnMv3ZpXvXvj/N79e6+lFlrzog4MCjCCIEip
AN3VaDREfem2RZ+TZLRBZ9WrPkiPMX+rVKpoTwi7BvuAEQRBSgXdXm+pUCnyHj94otQzvAKCPJyl
LONEKb1Om5+XU6hQcwVCJ4mYadypyM9+eOeBhiPwD67i4gRHqtdOGfkPu9vPnzfauu+oa/Wmfbs0
ZzMZBrFPjNi+74hG5PE0Po2iGD5Ohs7v+5un1hm6ZNnxRxO6VKf5nu0WFOAKx5Zz7KtmMVapUsXK
lpSBJ0+eMMww/6hNmzZxcXF0GVZKtmzZ0qxZM8r4K5ScYp6bmxsaGkqHXW/Ha34FICgoyJaffwK5
BdiAX8He5/Xmx5ytEto9PcfQRAz34vXB/0VvG8/IetqvXqsTqUkKFUVxeD6e7/37cEvB3Y1hncZl
5RUZvsblj5ixeO34buOXblEytu5azFDoDZ71hDlnls1re+r797vM2Kt78Tu6VnHhwZ+4qEvw+uhW
EoUCXFZQgC3P/fv3Z8+erdPpbLm+7Obm9tNPP7GMkHLHvOgZNmzY3LlzaTTvjcybNy87OxuM5xhh
s9nmpSeo79OnT+m18I0cOHAAbsFkP/khTJ/C83P69OnAwED6DHwzzs7OcAskJAWXyzU9S6YD4C6i
oqJotPCNhIeHZ2VlgeWmW7Cv8Bpy5/+MxP544EhQ389mLdM/2bt6x/nE7YeKNn/+ec/WB+KTgrp+
umhEm+8+//xW3PY7D2d9/96ErDz+t6vXRKz88rfbWbceJLLFsgCKeqzXKyj9itX/Wzjm63tPD2ZF
czvP2APF2Nq9R3308aP6fZIkErsa9JfqMHHHqXo3a7ZtQs+dOwQowJYnLS1t586dkJPpNuR1+Pr6
pqSkkKkUprA+pk9tP8wemAcqC5ZLJBKxWPzSW6DRvNKQmpqamJgI6S+VSkUiEVFic7Nt/1cA4uPj
IfHhJ4AfgsfjwS0Ue/Jt/BbIgwTSKxQK4YeAV9hpBxN8dbobWg38FQm5L3YqH12+EklR7uEH1l66
/YBiscdM+4qVeGLrhcQqzXvcP7aGq1VO/mq84cjEi6cz84Qy55Nr5vx9Owt2DOrVWVOQ+djwGXv5
8TujQ9NnjaFU+sLER/dBfb/cfe+TvrXhsyF9li85p5Qa8xlH4tW+t6eN/742Dg7Csjzg9dq4+lLG
4SQJCQlQV8jLy1OpVLYxruTtiI2NBQEzhSWyO/uTkpJAvZKTk3NzcxUKRbGwSvZyO+RXyMjIKCws
hAcJXF7TR/ZyC+CjQ16A+hD5IcxvwWbR63UxOsMDw2CYJbKiCN7IZKm3Y9J6Dxv7b2TSqoXdMm7f
h09CgruD16pRZBbl5FFUJw8JhyqiCjms83eofoOGPIzPnvRhR3IOvkg4pHVVTWFGjvEtm2kQW9fn
Ms9gsannF0y7utGVyVy67V8r3bMjgh5wJQUUC8odAccMdwAAIABJREFUNzc32IbqP5PJJK2gdNv1
Fjx+/NjZ2Rl0C7wW4nsRx8Veyn2QLrAffgJIf3AiwXi4C5M/YS93Ab+Ci4sLiBa48uQW6LborXn4
8CH8EB4eHuSH4Bmh26g3YOjcMtTYGlLK9Pt30h6GX/1x2dJqvacwuVR2NvXTkUM9q7vcPreh7adz
zpzYAKX848j9sfHvbJzYL61ATbWs7yoyuvgK/okrx4Ll7NNb5zVbevavU8tgH4fdX8Rjcz3rBFFU
dHwuTyiDnbO7Vws5fUGccWvxnnDwsCMLqHoiqiA5PpOiblwMpz5sTG9q2C8owJUUjUYDAgyvIpFI
JpNBuWMvJb6JuLg48FfAftAwiURiF46LOSkpKeB4QbK7urrCjYjFYrotKgvwK0BlDoyHXwE8YLt7
iihjTQjSH2qf5IeAZ4lui0qHoa52o4Gvr+n9LUbKovfenbjryPjuzYwNzRRPIJJU6zOsa+31x08G
+AUZ9zFZCpVL4w+//3T9rLWnOzaqSb7MF7Vy8/SADY1uf5HmV67AM9CPOh2Z4Nqyx//6Syftye3b
oeXzC+lIW01gr0lHdlWr1vpda92wA4ICXEkBucrOzgbpLSoqggLU7tQLyM/PB/WFQh+qEfZoP6R8
QUEBlPhEt4rdgr0oGfwKcBdKpbJkbAp7uYW8vDyhUEgibJT8IWwTJov7/fgPPpqxyt09sFXnLh3b
d2zfvmmgr6+AQ/X79sn5i5d1XL6rd9UG9eq4SAWr/7w64szRi3di69QP/Kj3B7WahYCDP3nlsUET
7509f5El4PpWCwsNqeEkYB/Zvq7QpYmUy6Qo0dCJ89sx/EUUZ+LOzD53r52+dIsrcWvcoEZyYk6I
kFjBf6f/QHrTwd5BAa6kQEEDJQ6Um0S97KWsNAeMN6mvPdoPxpNb0Bqxi3K/JCQoIwkOZac/BPkV
yA9hN7fAYH44fSX8K/mJV1DNAUE1zXboUlMzarfq0ayDbvnnnfOK1I1CDJ4uk8Xxr1l/SM365t99
54ORpgsMmzj7+SYrqG4z+Efe1TY/N1I+UIArKVDKmGL62EeJUwJSVhLdssdb0Bmx3/QnOMBdmOpw
dn0XryLz+hafxsPMdriO6N6GNmuQ/4ICXHlxmLLGYW4EQSyOrHaXWeM/uh9XCLlEJHOeNP/HUD8p
3UYhz0ABRhAEcViYAs8Fy7eU6lCdjioRkc066DUaBrsyihHOA0aQl5CTmUK3CW9NQW6ehc6kS45P
wGYF+0Wfk5z7+/rCs+fUqdml/Irm+tbUTm00Vl1mUK9NS6X0lD7tQlqXwIIryRV0GV12ts0+yyjA
No0qP0eNBaHVyYm8LHPxHLDhPt2GvAX3/lwmdgoOL7DAqdIeX/byq34qLtcC5yofmrTrAQEBc3eE
022InaH48zvFxrn58z7M+iAkrW9DxaM3a5v2CTztBXpLDgTU58/onD7m21eVX5rruzIGNsy7m0Qp
Mo0WaF9xYLnQ3t6V/l5I7vpzFXHy8oMCbLuoMqN5EpnL4A12OTrWnhHKDDNBH0bH21Hdp0iRD0We
RQKpaFSGIEhsG7h5RU56bGzszTRLefaVBp2G4no4LdstHjZEn5OaO6WPMq3oNYcbonpk5pveaiKv
KCPKu5aJXqVT3U/QPT6hLVS/9ABWzfaSST8KAp2pV/gYuoIcbWF5XXJW9Q7SGT8JO4dQOrW2wHg2
jaac57QglbHZvQzodLqS69VUNByx65yZUxmNGr4s1qo+v+D/27sKuKiWLn63e5elu0tKQUJEFCxE
FLu7O57Pzs/uZ3e3YqAozw5ELBBEEKS7G3bZ3v3m7oUVkPeeisqC96+/5d65c2fPmZk9/zmTAjqN
LJNIMMq9fVVxWszfL6I1dbQhsaCigqNp3NbbTQnXMchy4t49DYtMyc3Tt3Yb42MMgtoZqD29cz0h
q8J30BBjTZiSC1Lev4xOZajpuLk60/H8ncvWcHuO91flVvCJ7u7tSc1SDlLOpf1HP5VKy2PvQ7WH
w3JLc1+FR0EkTbeOznSCLOTRo7Yd3D+9DU3M4/kO7FsY/UrNtkNxXNj7pCwXb39rfbZUzA958LhK
DJnbO9qY6DaHGo2DrON45XJgz/4ekFQS9fJpxIvwXIHQsftwfw8riZB7/sQOIcW6q4+PmY5Kc0uq
hCAT2nYgtXXDYqWVpy4I7kSQJnQU3DvMCQiSCWU4CzvauJVEQ1r1yY3c6xdkIjyErYYIJhhACFJR
xfKpkmIr9YcB323zJCkvSqaNhAeVocpSfzO89xzV5X/wbx+pvhcsrYII7VxpE5dCBe+5l8+xuw74
hzTEVYu7CwvJBGMDSTGPPHoVrZuTJPMd5/BOUXouRs2APHghrUtbWXUR58A6QWQMRFYhuvajTxnL
3T5aAplBJZ9EyWl4v/VMbyLnzDH6Tl/BMpfqdySCJVOUmIBrN5G9/X9YcTX3/C5h3CcIRyW49qD1
G4z55T9hlIC/Cs0yz1bErwp7GjZ79CJAwLmf3u45cPBNTJaxndu8JYsEt+e6z3o+d2bXvQdPq3QY
lfLsjGrzmP//xtO7x8fN2qu47T9nubfbxmaUp1Hkxd7Vt/ervXPwSDsD/pyb6nxOfq937V3G4/3v
b+5wHrAYiaHnNODjswN3du4K2bnrf/IQn8n7go/N/sVlIBGW92TrPKnm19yzLUxosvdn9/nMWVxY
KQABGuaOqdHBfn18FI6ER9SJsL8Uaz2h7mNnBe9bObqn09U3eUjI2tPPp7T/lUr8Gwojbw8bPjkw
uUo9dJnnhP1IoMXbfN+A9VP7Opx+WiPz/U/lPa1YzSemUgIjFiXFyXISqu8+gm/pFPGHOxXbNmOM
XLHcJFFIHBdvgOnM4Fw8hW3ThaRLF4TckREZOJgQ8JQu/cRYe0wTPA4MS4fs7S8K/1tSKSR07Ets
ayu4s61y90FIw4GgyhUEH8ea+ZPVUqX5aZD0H02rTCCUleQJJRgML4O70Z9gFspZMlzMIRLt7ITh
T7kfc8gPHvP2zuI9fk9w6SQKf8TPiCB17yWODBWVhGJUbSFusehhuNiIKs2JkfKEkoJi0D4VfarE
W5qJIy8JC+bw13gKkyrxTj1l6RHVb4Mxjr40E9r36/xdQLuglReCisLHL1/EF1UJyj50aeO268SN
goKsMwc2e00/m5uTAUGZew9eMDEzLn99LSRTefvoBk3ZnpIQFxUdpk0CVkB93NgZzS1RI8hO/QA+
Z+4+X5j5YdPOJRp8+fAnBuu78MSfXd1yYpKLSxMB+5IoajeCrhhCUE5MWjG3IgTezUBj1a6jPV0s
7h/f9rH8V48VJP29CbDv/048FFSXDWvPhOez8Eo9p/1ZjlO7+iJ2bl97LA5HlEnh3fNpGtsCrtrB
3XoC5N1VhwN6ORuIJNIn17dffZM/e+uFxQ7wcTcJ75Xo9MDUxGfgE4eVxL4IBReHb7+Me3ptwaSR
YVf2nX5W2G/P/dKc2MG9xhprkJtZUCWEILdiWs/KdXPE5QU49xmMIc6C4P3wnhp6VElFGUSg442d
hM8vQSSa6vbTzBWHyZ0ca/pPIAx1+mrGlEFNOeQIq27GXLGPJOcz2txdtN7unF0HIZq++rnbdP9e
IJDg1kZang7BVfOfCFgi45ZjdB00bjxX2wEfjcq/sENcxMOQVIXhYfBXWPbASDN5D15CdFVZ+gNI
IsWoGWLlhzNi1JzUAu4QzK1xprrSnEy5TjV7rJNXB9B9ekAQV/j6vjCpCtt9t+qOk1Qfd1DLMM0x
AxwlYOVFVUUucrF/wJRkCFoXEB7x+Ba4Xbq0H2JvvEdNeRsEnDTBp/yvnev464ElEE0tzW+O9sgX
QHtOPuzvrP/f7/xytPWeCD4Pzh+taeig0a4t4sgymBNvbpuoR6NCRaDBkwNCBLySgf7DwA96R+AJ
UwbVAsQZunPt/CmH146HoKz8yn8bZvsZSH4Nn4g+aag3kaLi1L0nLGFlnJAv3no2eLCHLYVEZDBq
mGnX5QeLhgy+Ev7q+gZ4595OS+6tnTbk4OnAE1s3Zrx7A4zg/iWjtn2I0+8yYteWsb9Yi3+BlANb
ZzyONGLtIXAxvW9HG++V7V1srx1Zx9LUvTm3J1vX9urdM5aqyn52QjOAWktsfAhv44SBJJL8Qni9
z8tnWPvhalejGaM6SQqLISwGwstZAKdoxEgrRnUo6jFO8oPakzL4H5wWlorBEGo7iXDyLxVLZf/o
AZNwBmYYKhkQJ4ahCotVBs/VkpWnQWQW43Ck+uFlmMJE+OWKbHEhiTTjsnrAS4IaTMB4Cw8slqBy
6L7alikI72IgnkhOxLQOtpIC2K5Kq4rBV9Cn9QbXolQQokHQovyDJD8RKAErL5CqQ8MTpHAHOHmg
txUSTsDh46PgXscFqzdXlWUgIc0m5X9Ddm3jhLUxkO/8vdMHtW1uYRoHkaEpFnJjIp63NVWf4jcu
Uwj/rvtsnksE1gkuh5Ts0moQQiBTbjx9XVpZ3Y1dXSAgmoOgvDIQNezCSziVnzKL899AZ8LEE5kO
z3EtzyuSywCfToeTwaJIJRw+v2a+CV1eQ2ycO2hSYAvIUIE38zWxbW+mpyLmwXNk+v7x18eUrJhL
m1M/xP5qNf4LUqmEpefOqyx6EXxWG/o0ZvoimZiIw9b0FqYmJvN+ec63AIiN1O4nsbccwBAgwYkp
ZVs34Q3hCovtOIna17NyxYCSBQuJLp0gHqds2uTK7bP5Ye9qSBFC+kzSf2R9lg+uSiv5/LhY7p2H
4Fr0PBoOx/2H3ynNTKu8eLp02VoIplVbOCW2Pm3hXtHVxcXDOgi5evKXVckzduOlEaWj3DmPQhtN
RyaWyHneFUvE4m0c4JThZYZ8zvpdnEPzBG8iIKYhrjm6UVACVnZwxSICzAGE8zfv3wu6BkL2HXxQ
AnsG7R2Nmao6liDk9dumTln8ebixa/qQlRfAxd3rO53aOe048aC5JWoEQRsHqOtbTP9jZWYxF+ID
kwA32BF/1rWPCbjMl+r76UASoWDtwjkd25o6enieewv/giuf/2FvZzvlQrCO87COBtRfLHb7cVvI
BGw/e1sLE73NZ0OgagGXZkki4eeO8fdwd94emJCdEBOczW/kzc9eB6Zjv+Hgz9vAQ+OG+huaWQxb
tEUJpj/XQCJvCUnF5b3YRBMHz2VbDlYAQ4yn9BkzszTvk5mDs6OtsZmVxaabStdoaF5giCyIgMcQ
KATXfmrnnhGszCT52ZTJu4m2ttKXJzibZok+fsA7epEGriV3cpRkPODfvSnjCwEZy/d1xakcvMU+
fhlHaLIc8kOEMcDJxqqwtu+EBEVVc3oJ4xNBoPBjIIamCVM+BjyFW4eN1zphEf/4SkleEbHfetqU
JfQxE2Rl2dwN4/iPH0H6nnh9C9b2AxhiKf/ADO6RHRIuk2BmKeODpD7PncaqwieuYmksAuxFw6v0
8AaG8hBzap+u0g+Hqq9el4mltY2PXw1l9px+dxAIcBufRSGOObP9QKf+60f3QsIzL0xSHe0GhXKB
Y0xmwrvKXQ+Lks53V8rGlLSitNCjm4+FkSGFiMnLzmapKONZb+37zRmefia3sNxv8PhBo2dbGrKW
Llo0akQb8Mjeb/KAPqUmxiZX47I2bd2Vk1+KJ7vO9+w1sYfBU/D70W5vZ2fs7N51yZp1dHxTRs2+
Bww954TXd3YcvVEtwQ3WUueLKBoszY8vrm/ad6lUiF/c1ScrJoaCp3l38bYwqJknjCVQRvTu4dhe
XyGrY985L29rXbj9hCuUenbrNW7mn0xS8ZSJY4xYzd+v267/tAX5uk66mmtO7Tx6JbS0WjB69oLZ
f6601yMFYMjnH8bgqDaj5/ed0d+uuSVVLpCHriP6CxGDgNU0Zx98BneoYSCVffckBbkyoQSrpoWl
wuXLXHeLlpctw5Bw6mwZT4i4o8DLJLCbLgWGvuYxIYNLVIV5GN9+mEagtyinCKdnAlVlSyE1gi5L
zXkyjkKA9HurXnyH09JqJAkDO9aKXRCBRZRPzqdOWE8ZtkBSUglRGXhVVaARrn0/9ds+kvwCCE/C
gxSwGNxfQRDbUpECsd9K9a4LsAwa6VSkWEiGZ5aZeKvsuI6zao+j9iIPTpbh6JzV/cQU7WaxnygB
Ky/UrTxLCvLYGtoYjO6nhJTI9zFEdUMbQ3rws6xenga+q7n64BdEMo34O4js4KWU7AuAnbA+cEJz
C/Gf0LPreuhY17ohm7dtQy6oeh1u3L4hv2St37zzcwwJPCJF9Zh1+fK4X028dWDo5Lv3sG/dELqz
/+Ez/nVDej18orjGENkXg+t3QmDw7n1Ggv91gtSOnjj8E4T9ZrAtOu/cCZ8coNd/jnv/OXUfDZm3
eci8ZhJL+YEnYOl1HFiMooZicFp69aNicDoGNVeMpvu89UHVJLWp800sTSJLE75iWSJDwThmTXMc
r90I+8KvkChEyzb1QqhsPLVe6wBDIOMNjBS3eAun+mlgsQz4pG0MQ7NWPRLRyU2S/Kp48068vbM0
7qI4rZQ4uHnacCgBKzMwqprayBWOxnbxqDnDpL+vOvi0tVCX3xHa+/ZtHul+e8Djq1KRrHa0HgUK
FD8QWDoFI9X8WamLqzHiQvHrmxCOhfccyZw+/Wd90b8CJWAUKL4LOPbq64crLPoqa98DChQtG/TV
wfSfljjOupvamW4/LfmvBWo9UKD4PmA6DZzmZ9941xkKFM0IqYB35XjIgmm3/vjj7tvECiQwNuzd
sFGBZdVKOmU8533y0KE30hrbelLC4wtEUn5B+rBhV59mNDap8FdBJpGUlQl+YIIoAaNAgQJFq0LK
69TthxOevysIDc2aOfLKisMfQWBFUWl6WrlEojyT3OuhspiTmlrGk6+b4+VmLFv26FMxvEBOwud1
7Xnea/LzyrzylJSywOc/69Ckr8Gtg3d69rn0A5sAKAGjQIECRasCMpl5/J6B18/5WGuT7x9/E1cl
lUm/bWcNTln5x8TiJkoiruaWVn3dgQryloFccFl2eNLDh6lhsZUSmQxLIEwY6zC2nxFTE17mxyQT
/z2VgoLv3BaQz+E1fmpEHdh52owaafcDB27RMWAUKFCgaIUgMajaRlRDFdKnfCFf8NnxXT/mUrKx
6Zn1bqnv4yb9GX7hxkgNPP/8sTf3XhWqabJ6D3Ts7aWLxUAn9j0/F8T5+81IzSZscb5m1p2n1ZTB
NtjbL8rGTXUICfzIIVDXbfAhZaaOWPou4PFYI6JszugL+n3d/eUL5WRi4eAu59K5cD/5oYXXj7MZ
T4IHRoSmdJxmhIHgvvSyT6njBj9KL5Iu2d2vtyObU1p56czbNwmVpm1N5050yHnwetTaT+Ontwk+
/8nSx16tJCc6mdN3iud4PyOxkB94OizwSQFTk9lrQNt+3gZ1505KuaV9va5J3Ew70qsrpeTpczrZ
GFKryypvXo28G5qvYaw1fJSjq7VKTkJWbJoMD0lXLbhp7maZ8OJTVCp/zKreIzuofl/+oASMAgUK
FK0QRyaePyK/0Ha2bKeOe1kbnlhRXVoGe6W5SVlVVeJqgWTG7NvvE6rV2MSUlJyIdwVu98ZqMPH2
2mra1nh60w4YKRCLhCkVF1Pg6/1b31DoRCGXc+x2ig+1TMITVYkhiCjMyKzGl/KgmpXqGLYWvbqC
V1gipNBI6lo0iUD0IZmjmltdIoE33H1zKw5PIWL4wtUrI7oHdV4z/XJIGobFIkRHvM3GUkZh+MAJ
Pn0Y3pil6HoUhMMRsNL9uyKG9ta/PO/iwXCxmjolNTk34mWh/YuJZnW3vpJB4C7vTWoIjSDgiV5+
FDy73nlujysfMBgNLVpiQlJYFPf5nT6pUbnJscBLF0a8Lb77vJgK1OEIL55O+W4CRrugUaBAgaI1
Iz8i8WxYSZ0AjLGJfH4xDj7oTcLPSYznUCxUDUjw4CYOhyEQYV7oOtXjzvneP2R3t74TOg4yglga
Kk+ejLfSwycnVcH7T1NJpvLUwaW4dmYYBk84FjDs5lF4La/fFM/A8/6QgF9v3JrFCAkd04FOgAoK
455FhaRCLgOdHz8YbU3Hvz0WUSIfQta11bv0lwW4OHtz5LSe+lB5VUpiHmBfCCJIJfLTgElUlfob
T0r4vDwIUtMyDA2ZMNeRDRXm7doe8QGCrEZ53b0zUk8V19HPmASJUz5Vf35HV/fek0HwOlHK9zdS
UAJGgQIFilaI6cdGv3496faFzkQICrkZU/dRbnYtkWAwgpx8QLy8hOL3RfiJf3a5c3eMChnmhbDT
rwcPuV3Q9CMZ1DQXzmgjhp1MqQySERnE3E8l8D6vPGFW7fElDRisho7rjB2TcVj5DtVQ73EeJJmM
Lx8vzoiFt5b0G2oLtFCvsxp/ysquWLnYEpHMQg9oL4xK58qfiMrKRCNndwwOHqBW/xsJLIYR+LSE
g41s4T3C5KdEYGaPs6iREAunj69DmRPG2lCxjIDQ8YE7G2z98Q1ACRgFChQoWiFCz71av+bx4uVv
hfDJ0J/Xy+HJuIK4nMBb0cEPYbeYqq8nP9eCsnKDpyGuYvX8oIhcmBizCqvS04ormr7oRorBY7FG
1hShUCyRQKYkMlRUKsCTIJnk4rn3l85GlAqRwxr+DXyJFCunWDKLDGGwNjrgsoppCgt+cW9o8PXw
Vzyxhpu5inxMFU/A0rQ1Abflc0RGFrCvn5leM3N5xdauNnT+xmV3z72uf4IcFgNerYrPePIk7shN
kC14NhmWKehKTHxYbEmVNDI0D2kPKBokiDxECpHQBBZFx4BRoECBolUB6UP++DzlI/A/dZkTFrhO
HWkdHpiFnL47oIPmuotZG9e/gaNisVKS9rQpZodOpWxY8hQE4NUYC0gw9/Sb5KzpbmnatDP6GFic
/JwDDJ2Ek0gkwK20MyTceM+nWmhqQbLgo2+D5dGk9Q9jwMJbNoMQmOFwWBwGA1GJ8HAuuNXWAwJh
vX1YZ5KKsRZWY9xyzoWlrIEPCCZvX9FW9AxWCo/DEsgEDOxjS9VMWSCkqAi7ZaLFytPJG5fA27Iy
NBiDNRvZ6pxbXLp48Qtw0Xd2lyl92B8iMx4ef/UQefYpNbrAk87EYeUtEpkEkv7jScbfAJSAf1/g
cKBm16DBo6ioKD8/Py6XW11dzeFw+Hy+WCyWfuMyhp+Nbt26EQgEPB4PFMHWP9QMPOrduzcQniuH
cspvZ2dHJBIV8jcoBaDa3Llzq+UARQA+RSIRUEEmU6J1nFQqFaiAlAKiQgMtHBwcfH19ERVAQQgE
AmCFla0gPDw8kILAytHc4vwAGLpaXj5NE2AI6loq6qpkpPvUxdfrjC1HjY7v+0cv54H5mSVCTSbh
4dNsQzbJcmrXvsPdMrMrCDSKqSEbK49PUWN39WzqmQyb9vQuFxMB19n0tPPgleDxmG5THLO1Sjq3
N+4WOvp9TD5DXSX5bYqBm6GNAeWyia6ZfFSYZNBm12asTSd4h2eKqsrtW0Npaiwi3vDJI1sGC24R
2I3z22yQ5WbB7rx/gG9cVlmZwMrFXIWEhYZ1vO7hYGRA4FfpdvLQN1EjUQxMF00tsfIzb6dn32W8
a3J6OZ5CNtBXlRN0Q7CtTDbOM6FrarUxYoCKfPjcyI/v0/lkRjsb1bBn2XYapLZHRk0QAdLEL17d
wcb9BxxtjlGq37NyAmSRl5dXSEjIV8Z/9erV8OHDgaER10LZ7CYAnU4fMWKEkZFRmzZtzMzMVFVV
GQwGsEHIU2AoS0pKMjIyMjMzk5OT8/PzFQTQvGIrAIy+ioqKhoaGubm5paWllpYWuKVQ4B8nyGog
f2lpKZA/LS0tNTW1sLAQEACQX6lKgUajAfl1dHRAEYCCUFNTYzKZCgIA9aeqqipLDlAE4LOiogIh
sOYVuy6QUgCZbyGHuro6qEhkcs38FlBbQNOnuLg4PT09TY6ioiJQkcAvQnkKArQYwG9BU1PTwMDA
yspKX18fKYhGI3ft2tXJycnW1tbe3l5bWxvERKocihYPSdUwt0tcF8c7h1x+5deiHvCPh5ubW0xM
DCAtwF7AboLPyspKYP2Vx3QCowMMB5vNBtYT0AAwo4g3XDcCIGNgSYElAiYVmEtgN5XKdwHiIbKB
TyBnA/kBjYEQoCN4ClgByA+aF8pGwIoiQPzIBr4XUAeEANVAAYFoPB4PxAcErDxFANUpBcBhJBIJ
VKQGtQioAOIABVksFigIcIv0RihPQQAhgXggh4GEIIe/LAgUvwWksipgNzi/2kSjBPzjAX7SwPoD
0wlsq1AoBLdcLlep3EcAhFyBTVQQWN2n4BbYU2CVkGvgHwBFkAaEMphOxLIDcwnsPlABfIJrhQpI
RyiS/yDPgUkF8it8R2WQHwHIYUCuIP+BIwU44Ev2AiEgAhAe3IJoCupSHhWQVg5o3ABXHnwCjepW
JEUxIW048BR4jUhLVHlUAEICwUAVArUFyAmkVfQDofiNQGAGPBolI5P/O+YPBVrVfjzATxoYfWCP
EKMDftiI46I8BIw4uAiBIT23wNbXbfiDayA58AlAOOAGhL2Ux4OH5BIC2ZB8Rpz4uvID7cAjQFrg
AjwF1IUYfeWx+1CtkKChAFRA7P6XnRCggAClgWiApJVwDBgpBYTAAL50H4EKSEUCF0BNpCIpYUEA
IUE9ByqA4mgFBCwVch/duRkZ9UlGVe07cqydEby6Ju7NzfX7bh05fpxJ/u91q+uWz6Nad104tl+T
ZRHuXruy27Q19tq0b3rtwLblRWTz/82dqEhn26plvrPWfWs6Xw+6SlNSlnJ5Ehrlmw9UbvFVTTmB
NPyRxjWwPso2DIy4JgiBId1uDTxgqNYqIdZfIb9SqQBkQ/rJFZOA6kZAWhiIK490PiuV/JC8kuDl
QIz+lz2fSOYrmFjZ3F+otqsfyWRkHlODSViIHw/JdQFqKlRQKi2QioS0JBotiBaHxJDzPoNqDrhd
vnzB2hN/r57om5X48vqN63sOHvkaAr597XKSj5KUAAAgAElEQVSVLaHpBCwpjtr6v+1kr3nfSpwP
blyMJndUEDBIZ8eGv5jdF/w8Am4CJLs74v94pZFSkWvK/DZKRQn4pwCxrYAAwE9a2XxHBAgHI3J+
OQtX0YsODCXQAvHdlcpoItIiYn85/xYhLaACsKpAfkRypZIfqu0qVxREoxGQOcZIQSgbb0F1VGi0
FKDaggCPgCKKNqhSaYEIrCiFL1cEtEQgzenN9+P9qMkj+49eM2n6sOFpUvF/njXwGXDLSb4KSCoS
pGcXmhgbgIwpK8wVEVia7G+gQGFFfj4EkbBY+CgIZHb11woAlJAvRpJK0tOz1SV5RV+RjlgohHAE
PA4DKttXNqSquTwKjdK0Use2G9K/t5qUTsCKBALQGsXCY8rQ12iLEvBPAWJ3WnRflsKYfukctwgo
WKG5Bfl+tPQiQIA05ppbit8RTG09GxuTvjYWsaHRJRX12Lc4J+HUwUPvs6v6DJ04oJc7GYctS38/
bODgYoLZ7GWrR/V1l8fCSEX8PYuGLdj/MKusTJ+BH93doNBiUvj1o98ghPz3t2PKiIkJIUxVnxcx
l+10VUCdLi9IO3f44Kukgp4Dxw/u05lOxH0KCxw0coyGg/+qNWu82lshb8skoksbJ4xac+F6wP4G
6djrqoDn6R/Dd+8/JaOwFy5fbqBO9nPRx1lM1Ci7dzYs9fqbxAFttQWc4jN7tz94l2rR3nPujMm6
7Hp7a4rzn6rrdJ2+7xgl4yPLvMv8Kf2JWCgv4fX/Nu2pFNJ7DBk1ur/XlyEEYeacRUdHDutyfN9f
uSL1ywGnyznaNt391IXxRip2fbYdjz08+UUqFJtVaqvP5lWVhD66Fx6XY2Tv3LdHJxal/mlOMhT/
BdCY6ty5c3NLgQIFimaGt7f3n3/+efLkyfDw8KysrOrq6uaWqHEkPj4MbDuFzmQxGcCpb+MzUyST
/X1yPoHCKKgQFEaeIhIUvgFmxb0PMkG6E1Exfkl8kFDkYqnlNHjesvHecDoMV74Y7r2Y4OfUacS0
b5KkOvVmPb4hUD7lV5fEB5JJn4dLZ5wMzn9znoj/3FaOSK/s18HUynvoiZVD5AHWSe8DGqSTWcp/
HzBV8RaeRMurKu9gWCcOzosjFvd1/LwFGIHcvVpSTzxRXiirTmPBZs4NUdYdwudWO3bcsZgvQ6pi
DtaV5eTHouHgT+dlVdmP64a7zjsnLg43oX5mXIrDcmH9/GnB/gEKFChQoPgn8DiVFZVVgDmzI2/f
/VCoCB87fq1QpHU5NPlD8GEIRxrQxvD0hGmRQtGu29FCXlV4yCMPE3j5Q+S1PZtPP9WxtE/LDyPh
4J6YE0HhIecPfYcka08/E4rF8SFnCSLe86jURXPW8gUqxx/E58YEAR7uaWO7fMV2Ic06LKesuqIo
JCTKXh/ePzLhacCkDVcZapqppZF6TGKDdMI+5a3d/1TItn4Yn/EqYK1MwAUhOPngxsG7Hy/N9oAk
zxJvr7sdVdDBs087K3MQLtK2btAtLChKqICg0XP3pqV/6qklLbi+fJb7MJFUOnHWIF0NQM1SC1Pa
FyEqyLZd3cbNjX9yGlxgJeLLUJ2tvDQsIlKznSDo7bvYqZNnpVULj/79pro8Gy4RSsNRgBbcR9py
IZOPgSnhwGpdNDqk9wNRtxn4k76iiVCMDv5TPshqRzSVXwukK/6HlKai9iqtylD9Umsdw7rfgb9e
Fs5sR41+dqJb73l7Nm7/s1dNeKlQwPQeNKyTWfyDpxAWQyFhTyaladmPn9nHAdChc2dPOFJtnhVl
Zz2ILRzjqguuj2xblARZ7Fw6/Vsl0TU2J+BwuhZt8Xgov6K8jF9Na99lUg/rooRU8D0kiiQlI7lX
/yUd4V5lqHNndfidWt+QW1kZ/C5rklnDdHLL8/KTkzp0mdbd2rAI0wEHQcLqorJSqI3vuOm9LDZt
gfekzE6Gz0F8HXqHpaG/ce+JaVPGkerXBaqhPROCOvXraWxk6d7JOjy06G4hfGzDyQPX7bsN3zV/
zhBPTaPseiFDu+pz4NMOoaWLVlnbqBQW9FZlk8eD++iqirwC8Lfb8NlOeoxICN5gM7OwUrvbpMm+
rpy8JBDg0cGhwTxplIB/Kby9vdu1a9fcUvwHzMzMRo0ahcwL/Rn78928efPrtxVrLjx69AgIicwe
QjYqaZAJtra2PXv2bC7xvgZRUVHXr19HprsjKjTYruQ7MGTIEH39H7AD38/DhQsX4uPjkfl3ioL7
PTk4/PapA8/5b54GcyCIaQ67ZDUPZFJi4Yf3yZlRbx5AIlF4RokejhBa/C7gWaQTufz81dtD/1hc
WV7oM+N/R8bau7gPmuRl1busTI2Ef/Eo6IXQ9TsI+F7QZXPI/vzOZTwx5GCsHyWTEEqTwxMzC57e
EENQbFI2FsImRN97+3GYOO/D1eC381YvL85P7TBwcvDOqXYmrnN6WDk9O90gnXaGJs8MjEPDX98N
ffX45FYhBFlqEaq5kIepFwYiOHT2gUKCaVQN8JZ1x54Xj+0t/Bi2aOrkLQeOaDI+9wljyPBRghHP
n9pwoq5d/4TXdfSASoA7O/nPUwvG2z8OuPrHyxgPCKobMv91wga4x1m+YTUGr6GpIRNVwfd2DGFl
GfjbvksvDJ4ETMODl4nCjtj8hHcRHz8F7/gTPHJ1NmyYNd/Uof974geOAXt5ef2QdH4q1q5dGxsb
m5qaWlRUxOVyhUKhYg3SD0FgYOAPTO0nwdLSMjo6OiEhIScnp7Kysu5KYgTjx49vLtm+Ert27YqM
jPz48WNaWlpxcTGymWgT03z69OmPEO0nAjRwQcsDcHBmZmZZWRmPx6u79qmJaCljwEnPTigsPFtd
f/CcDTyZ7O6pPwgURn6F4NL0UfVmInluSn12VKN2FSwWp3ouPK6NBmHQ4s0gqSfnl4PA3a9zwPWH
0LtXg599kyT81DuK78HiCW6eewVS2d9rFzDqCuD858XV85i1tMjSNn2dku1pRPQePQOkEP9oFw4L
zds4v0E6Qqns6YYlrJq3cPauK/miwnZq0MiZR8Bbr0/NAqEv01OGuZopXtQ2tcspF9SX74Nit2si
lbnm5qeyqAsGarXbcRDI3f13fRlS9QGeEfbwYwmShlRYBXvunquKYgLB33V3kmUy0VI4CLpyYO7n
WV80aMmV5w3yB/WAUTRESUkJMC5sNhuuH3IPuEVP5/4+gGYHyARkIyrEcaybCTIl7n2ti4yMDGQn
S2QqchNnI7cUrQH10ul0NTU1pPOm6Yq3OJh3Gf3+pSUfS9E1MtXTZiNdN92GrgtrO1ODSRx+6HyP
Vf97ER5v1c5NnZ8UztczaWucmzP4yYNHUhKrs29PQBm9YjJIDFXwlvfItSku443N4fP/7Dv1sv9G
SUgmfkW5eRJIlFdUrGlorasCb53tu3pn1sx5T19Emdq6GBNyQwoofd1s+8xbeO/BC4qaZe/ujlgM
JigiU0aGJ0hZd5ubnOCnZWCyYsISaf10vFZsyZg2M+RVDFXbspuLBQaCLt1/STOGZWw7eOkpqVNb
HePLb5IP5KYkZRazdQwsjXQb7QmZsf6Ib1s9e3dvY3WgulVm8bBPHz5UiiBTcyt1FsyfDUMkpUcO
a7hbqiKvYwj0/PIcEUWDTsSEv3pl3t4UhC19c9/iA2XQYE+/YUvD3sWrkArcvEY6GTTsPfrtDCuK
/0ReXh5wf3V0dJBtsMAnsLw/sBOvRdhxgUCQlJQEjDiyqyWRSKy7z2KLUAEAePCAfYH7jsgP0JTU
WorWiYmJoOCA44tsD9JErVsmiG3dOzUIIlDpLo7myLWarnm/fsi1pq/8D57K7tl/iCKyupZOzRUG
b2pp0RRR1HW0waeWjkHdQJa6Yf/+SH+sbl9j+A9DVX/I8OGKCCrqitnLWGNzWADKP6Tj3/dzv651
e2QBFUSm64+fWLOJh5quGfj/LxK2denc18e6TgDO2sGxfpT6ITjVqdOG1n1MYukilcy5Q4cawSx7
TrSEbhze8qGU3NHJtLsfLIyJXsPTpVACRtEQpaWlOTk5wOFTVVUFPPR7nveCeMDgk8lkamhoKNtB
Dl8J4AHzeDxAQurq6shQQnNL9CsAPGBQb0HbEWiN7Ajb3BKhUFZIxGJ4s5GfVUOOXzx/N/Sj/JIy
f991R32VBhFQAkbREMBh4nK5wHAjW1gjYxU/MP0WYRCB4hwOB5hvxVnCLULsBqiqqqLRaKAokSMQ
mkjALSUHgNag4JDRX6Xagx2F0oHa7nV0jJFVk1z8f8GdJ5ElRcU8sZTFVmPRG/Fk0HXAKBoCGGvA
Okq49f+vBNAduIwK3mqhRhw0oepq8ZuUplAOwL5KePDDL4JMFPXiaVph5be+JxVxtm5eH5Zc8PWv
hNw+eyHg/dfE5JWk/7Vt84ZNWzKKed8q2E8DxsbBjkb6WY4oFk/U0NE1NNBvlH0h1ANG8SUazNNr
bnGaDQrSarmZ0ApU+A4gvPsbKq5AecILJ8+uwPxPXbl16tD+bW1M8V83hYNfmrd0+WqbctvYrQO/
7g3BgYXjUrWWjxr6H6srxZw8a3WTTPggVJZZj1FG6gZfRJHGvbhbqOLkZafTyPutFKgHjAIFChSt
DPBsQQKRcGz9Qmc7s/7TtgnEX9WFQ6bDi5FkHN5XN1uqKyoVm3ZAYpFI+g8tnryk8EwIM2DNbQ6v
fITLl+wLXi5d5NlnpN8q8e/UZkIJGAUKFChaIfa+zs+ICTXRUQk+tsSl9xhFeMCxbfPnLwt6EQff
SCU3jm7vaWbMZrOHrjyPUJ+FNnnv6rkeHj2CIzKQV1Jf35g9ffqqTbsziuSbTkCyByfW6LHZ7du0
f5yv2ISxyIHN/nPH5S8lKc5OuHXzHrigCiI2bDtcKYZWj+85ZfstEFIRd8Wr14zQGzvY6mb3ISg/
+6w6m73/wjVntm1YKvgu8cEZfgsPhZWnvt518nZm3Ktp44aNnr1bAn+l5NyujTNnzj1+7f5PysBf
ALQLGgUKFChaIWRYqYGtR2JK6txBvofuBkwKWHLIh+pu6xqZA2/YtGfPlqFbHswmHR70xw0k/tsn
14RzXMFF0OrBQfKQISOnlyX+/WbHCO8lAVIpTHo7tx+Lz49+OLb91IAP4D63vBwEUjxc5d9HlhC5
vGruF4IIZnazvpoIX13YshZ8dh/YOejMQ7ynC7TI/+bWaSH3K5K7zyqvkI9YS0UVFRUfHh99Vx73
Mauyg1bVrMN/Q528vApuL1gbugBJj/J405ZpUzzNH7zPhW8P7dvTedH7Z9twLXC7M9QDbmWQvgo8
PW3q1Flzjwhb5LShpkAacuUYrPu842J5m1xYXRX19m10XFpzC/ZtkEnEXK4AXCTcPzBtxl5OaynH
W6e27T/2urml+O2Ap7B3HtkKXMmPAU/29O0B2Hfj6ftJj4+DR16dbcsL4EMa/EYviQh/c2bvFmnt
yeVLjv29b/JgXnZOZkFal0VXpFKtGXOma0EQT4Tnl6ZOCfjgPHBDebUo+Qm8JxSGL38Hw4jO5uxb
OfELEUi77sb/Nb8rga4en1VQWl7V0YgOPD+iqSl4hpUfT+Ay4S+RoHKuK8TWNqgWipf6dwaBWpq1
Bw+LhVJ5tI5Tt4Tc2AsuCh6tA+zrP3yyv1t7cFvGI0EtkH0hlIBbGd4G/NVx4ITjJ07cun+G93Wj
Pq0GoSfXeg2fevLUqaD7p4USWeD5fbYmTCc3t3a2prrOA/Krhc0t4L9A+vby1q0XwpACO7B6tKqF
kwCSxd49c/TwlWpJMwv3gyC4uHXJ9aAnzS3GbwEer6zurVRehWRSblRoOgQZzxjZk0aEt3DU0mT5
rg6YPtLnyfmtzi5+z6Pj4AMEIMjQbeXaib50EgkkVCH3cSEo/9C+wzZ+Q28/u6HBg11V/7ljWRS8
QZt6G1aQqTQCrhFO0TO1tnZwAC40W1WFzaIjXCkTfv5JCiUQnggfUYjBIsfAyEMltX3b+RXyK7sL
e5Z49JmaFBPJS4gB90GXj4ek5k9fsiH6xfoWutUZSsCtCg9CnpDoZm/yuNkJL1nE36twg0JCySyb
t7mcrE8vqPj8xWPmluFMt504P9ffJu/dzfD08uYW8B8hE1fvHLF06ehVVSLY/BlZt3NxdQImSMyF
V4O0zJZ9PcBTkWWVxcWwLjKpkMNreCgbAi6HK/2N5t/8RFSW5YPPiqIKgUBQkp85f/oS4HAOnDxQ
znjUgpLShFT4cJ63kempsYnTVxxISgwzhYoPHTqFMIJlT3dgPFQYBAhKTiqqaQDee5d0es//ckJv
vMyCi2/VnCXvE1Kf3JW3qGoO+ZM+u3s7Njn/n6SSSGQipIBlBCwFqkh4l5aWklAE13ly/bFQAnxE
AhT+Oio1MQG+19eS2zICAQPhCCRzM0M2Qw3cdxo2K+r9u8l+Loe37xRKWmTV+b1sdMtFWsjFzn2n
VMsPMHx7atnk1eclMllB+scV86dMmbY0IrlAKhWFPrj5IjxKwOEF7Fi2JzC8RdbHxpD08ITXwDk8
ue4vj/wxc8ttqUyWmxy9bN6UaTNXvk8vlklFIfduhEfH8iuqL25buu9ONATpPE5JSk9PWTh+uKeX
GwSfSddM0kuFZzYtexiVfHzzom7dPM88/HBoZi+38fvEMqg8/oazq/+TZ4FYAkN+2vhTFSJu+ppr
NAK1g7sPsU4aMpkk8XXwkCFDp01b8io+pwWxlEzMD9g5j4rFWulbPimBZDjcnbU+DGrn2wdWOtm6
XroXunTKuIFDJpdUi2ScOCsWfdnJoCFebv5Ttz05tdO/T5+jt1pPNf6VwMhJc1k3YzKZrK5jdPz+
G8feQ5f0brPm/DQMJr6Njpr3uPUgwo0to2d06tbO1lzf0iMVglhsBmBJEC6Qn3Jv28kGfMbm0za5
MsGvp1d7CyNzm1mLV0RxtK/Md8XEXnK0NvOduAqOH5kMPpMuLfbu7b/l3JVGRcJKcRgCloCM0xJ1
vP3axUeeMDW12PioShFH0S7T7zjYGI/dOKWbpVNX+J6GrCb7XBfsZ243Y5NeXDlgqqft3Nln56Ej
YkmL7PBDJ2G1DCRH3g69c3nJhTl/DdDtPfuvEvURPpzQ8QdOVAvhH8zxo1ufPDzU1WcGEnn79t2Q
BWXmABfCv6b5T0hMLCkoSO7TR93ODr5dvPhhXp7Q3l5706ZuSAR//0vgc+PGrvb2WopbNze9FSvg
kZvCQu7kyfAcjt27e5mashURfHzMZs1y/R55Xt8ICfx73fUZ/+tG856+W2gq9Ui+NOVcAE+u+9FD
G8NfHPLyRXQv2rFjN3SbPbNPW0NTc0hU9sewHruvvQMPOhqrfldmNBUSXvH4FVsg8F8OLmUpMfh+
PEtVcmrO84u7I8NDkwsG1I1fLal4dffyrTjcjiWjFIHH/1o0c+Eusfz66NE9t99n9Wmr8R3CDBt2
lUCgTprk2K8fvPPt7t2vnzxJ09SkHT/uj0RASmruXLfu3eHxueXLH8fGFlpaqu3Y8X0HLwo3eRuu
elEEDGdiLtwDQXexiXu6FP6i2fBg8Ejfzki8x1i3nI3MHCy0bXI/+D7k7e1j8N/bwU9ciyvaqX1f
Rf59Ye49/v0Lw51bdly+H+rg1WfBHwv7dYWbofYjDyTZjL4XGqXfpr0uoTgsnTzRr83D4L9TCivM
HTt193ChkqDYd291rdsCnjTrMXHvRplPd0uLgcXDEqKjYlNwFBX7do4m+prY3i+dJ0ZFxiWrG1mp
kcQkbRtIJlkx5wSg6S3LZjYqUmlqIpVEZNTupr72+MPuYx5lFPNMtCUng7L0maCIMZM2XDDO1SEC
kqZbvEiIfvz8JYamVfouUOjey8XQaqNOtdbnZqlmTHre+3dvMgoqtQxN2znYUYktshMaJeCWAe/J
a2wXXA7evWyeYY+yauGaDQM3zR5KMOmY8ORm0tFxfdbeadNhfE5G93E9LKoMZz+5tRVPIn+30RKJ
JPKT62q6nkpKqnNzebq6TEWE3Fy40SoUSurelpbW7G4jkUiREJFIWjdCRYXg++TxmbfNcvXfQQfW
DSE7CCFo/7GhG/p1JVt1i3lwOXzXiBHb7pu3n5Cd0X2EtwW+3dI751YRSHAHVt67Wx5+E9MKSvX7
zw87uUWV0sxV/UVcxsGZXVMwGBLwBjq44DEQXp49+m5DJeKRu3uT/3wAZVYI9ZmyCS6TIajOTvri
otPrD+B1jP83SGvNoXCJRMBifufpAvn5HBxOwuXWeBoVFXxQNHVXXSIlxavtIi4p4YEQVdXv3Ayc
kxWz8kWRz9yzt3aOKo08pes2GeLXdEX0/WMH7+3J8ALW/aBjf9rYhQXcFa4fDoEmBsvmyMYBM+Zs
XXUhqBfnmvvUk8mpZe3UNL9PgN8WWDyprYfv2du+Zxs8wODMHDvNcqypXS7yz0Hjp9WNYuvkUpMI
UW3O8sXItWkbZ/C/bjqm9s7gf90XD0e+2YhV0/8HwzNkzWXveQIFTZJZ6j38a45e6Na7Jo6d10i7
2vh6pnZjTeV3Q/ohD5fXPx+BwmS7e/dyb/TLWg7QLuiWATzDevJs/7T45/3GrpNC2mN7mHMqBd28
ulrqqhLkjUo8jqBraKBOhISyUioV1PPWU7J4pu3o8T3iIu6NnLkdgnRGOrGqOcK+vr3MtNl4uZpY
LEHPUJ9NALqXw8c3wd1c4hETJ6cVkPZeepIZuMuQ3czn4XRZfsujjeHhG6/unoM9O1lWrqIbWSTG
YHF4gtwuYeDZJzKcBMLW6TEXl+ckVAj5eekrD0b0Gj7rYXiypwmzke9QPnArK8Cnx4AuJDwwzPWO
ozn8vznaakyIpObUxsq/OwgI5MjbcxMX7+zpbAeUt3Pv4uDtA0LeJWU3h+wovhmqhpYW+mr/9BRP
pGprNjwLCAXqAbcYDB4z5I/9QXGZkNvmeyZsKjDg2Tllufk59yJiwdPCCp46BW57iqVNnW1ka6vp
6NjG3Lzmt3TiRD8Gg1H3RNWIiKl14ze41dFh/HuE78CYiQNWn36YwIU8dgerkElA97T0wty8rCfv
P4GnZdVC5DRvkaSi5gVxXm5asbajtzQvfOO6UAyFNX7KdD2VZqNhAg7+oTHYGpCkkqIKiTJevot8
F5YkX0NJbGSUs+52QniGhiFwRiGty4/uttMQ37pwuIo7bkAXuy/f+k+EhExgMj+T95o1XuB/3QgN
SurIkT7f8S0K0FXgbv/V02Z0Prs++dFVOKi2XUgg4LQojIq8/HIJ3qGTH/QouKoKniFEZtGpLDKE
kUR8LBns3dYAFO7HRAhyaooYKFAoLVqPn9Tqoe86YKqhGp6pGTSvK4ZkPGCs99s7e/V09HcFpYCn
Z0KjIZlIwIUohFbYzDT2HD1Wn01UN3k4ryOGbNFncMfQgC16uoaH7sJrfE+9TgG6C6shGrFWdzyD
QqXkfwzbsGn7nr17Nq9dcTa8uVYDy/fsUdzhmKNmD+JxX7o7O2+6GiOrnVgiqTOAhcNSkVmlyKAv
RNKbt30em1wwvKuTtb3rkv2nsrI5v0z6poCm53Br41Bc8j2vDu0nrzwIQgTxWXg83AIA+lkQKVBp
aZUI0mnrAELyOCIivHcElkyiYzCY+KQSiKqhrQOll3zVRv8o6kEmzUkvLuU0Ptv8396TiENDktKL
v2G0KD0+Jya+4j8iyWQi+apIqVCQllz0ITo/IamUL67X9Kyu5MbG5ienlSPLJwWV3Pj4gugP+WlZ
la14b0rUA25BoO2JS5yTJ9CUe7rbzzyZ82dYeGqlWxev7AcXVbq0hWTciiKapotXc8v5M8A49DFh
abEUGY08eDVsYdTzqEyee5fOqbdP63Qwg6RlnFKaAbtjbXyV6PzqZhO2DnBUzYfHduv06aIIGbY2
oMPQN7HppaaG1BOX3nXQh3cbmHQwkjFZrAfvT4Df8yyLI6EDkhq1J8J+iVCDAI1buHvE7PWREdEQ
ldnOzoZMbCk/W6z/8iv8WYXhsYnaZnZqRAHE0KKIB/vmS9UpOEdvbVZQJZ0AaXlNGNivyNFjXOxH
D13LNhRBDovFamOhAkGqE6fMZniMbG4tWh7KkzP6jXgIYTAjF7hP6mvFpBO+chEAr7j8jz+f6gzu
HLTU+uteEe+aG1xkZHbxeLd/iXRmT/Ch4KqQh8OvTL60N65m+a+KrsrN60MQ0SrTUgYOeVzbd0e+
/WTkte3PztzNQe51u9lc3exBwraCFXkN0VJ+yShgkGmqduafbw0dPAxh5wHSHzZJHkD/u7AQIpCb
RbafDSpTo02doU9Tx86m8kkZumOQ+c86j4oKMUqoO4bQffK8+kFYI1t3I1v4aoe9NxLEMHCcVLtB
PYVeO+uJquFQW9xEMqNDp05QCwSepenuUWcWFUG9jQn813XC4dJxEBYLLLHF9Zvw0LiaTRv5C3pF
RcUY+AE0fe2+5hC5FUDOVTLZxZ0vrx4I7zas/YY5Dl/zGhluAkJVpdWyr12ALqwW/nc/qlQsRfxa
grxmL1zbOe5ezN+vykaOfRB4yQcHcaaOeQbY12WwnV5u6s2X1SnZ1UVVXIjGOHjQM2DTg2eP444+
MpnTU++rJGpRQAm4VYFEoTa3CM2G31n3lgmEZL/lAYpvwdjdg9pzs9duDr935nV2TuXpLTUNuKd3
Ij6mCx07W3g4aACSfn4n8t6j/BK+zKajxewh2iCCoQ458NSLl7HcwVM6uFuzQEjux8RrD3LpGsze
fWy14bkUsrfBb07dKqKSpHFcyFierKQ8c9i40JEzuw/00WogSbv2RjNNKKRaUnfsaDG8l8EntwvF
5SUSKXRqxaNkvqTbJM+tM9pAMvd5HAGdQb6HkUEUUltbfYcDg3v4Xi6qUOad7L4fKAGjQIECRSsE
jU316NQ2qIPhwjn3Xj+K3//UanoH4txRgW8zYTI7fTq237wefbAfFuwqQOKncLDT+6iDi7gLyElJ
0JtkwdNb/p9uhEzekoBsdHHyXNL1Oyp7iNYAAAhnSURBVEMid95dfS1HMTJLMZSvSseIC3O4edxG
hn5CgmIeFTImDrJAbs/uf8nNzE+FIFtHSzxWdP9dMc1Yb9kEy7ysosys8rIygYxGF4mldDou6kVC
4JX3PBFkrv6da+GUHCgBo0CBAkWrBZnF3rq2fZchzyKCUwKCEgH79prgNsZGNGpRpJohI/MhPH9q
8NQOfR1pCeV4Se0RLl1GuZqVZ5+8X5lXVj5hUwIEYafOsgs88KGoXFheUrbqWo6GleG5I93zQyLG
r/mATBfEsUwfvZyAJ365DliSlVGNoTIU9/dvxSMXODJGWJiWUyr16cWYM+xsfI5i1hjG2ADPyaqa
Pb8Ag8W4elkO6NTQq24dQLt6UKBAgaJVQVL/IBYCDV6lJ66qeBrKhyDiomltWfJ9afQMGL5Le7cx
pNw4+nrcjBCIQZXJZ+WTVLTWz22nRiVCYmFpCTIjWnr0wAeZNmPGei8tAUyTPWd3VKfjLZ3rjO7L
xBEvUnOKvuwrlskEEKbO0vaDV0bcutjL1ZzyISjqZWIeeEGVKioR4E1sNEb60yE6pOXlqE/F6LXT
Pbjb69b9cQd3eDG+dhpZCwNKwChQoEDRqlBaDG9Lh5FipFKZSCje91cUuLXqaS3frA4jFkl41TCt
pqdzJRDz8IXh9270VIXEe/96g5GP0hr0tKbiIDI861iYXFzjle4DrHltsLWsLKUUDrmwObSMJ8pK
rLMASVi8anHIpeDG1/vJ6qwlIpHxXL6YSpRAGJmERANfU0nWDwwacWRLp4tBHIgDzR9lBgJVNJiu
nSx12cRGE2wdQLugUaBAgaJ1Qb7E9tjMS9cYRCFfWF4p0rLRWzLAMKpIZdbx8sF9L4jkp3M+O/3s
xdLiLAKOScOXQxAb3sIVfhHZVNbKFu40Ti3C+DGg4Cpo2ZTrkEjC4Un6rfaf7o4//CqnT89zEgHc
+ywqkh+oQNTo4afTzvbLTddlktquZeTvlP7nkJ3g7Aa279q+nZlWdOD+5w/PvBRWw8/dJ3t1bce+
A7Xexb91gBIwChQoULQqmLiZrV0quBYQF5vGVddnTBznPKCfNRGLcZ06cKdh3Kv3RepGmho4/qdy
4ohFTvcep+WWC/UsdLt3tyCxsevXdLLqCC8UM+tkOci3oks7dZcH47yfpiSmlmPJJEtbvY4u2rg+
Y80fJCaklbG01JhEKVNfF/5WDG7p2r6NiUOY8r8u+VJ4abvfQs+q+7kEKlVbR8XcUrWNGbxzzsEj
fS9f+fApo4qppdK9Z5vOztrA9x43u7OQ1jK2XG0KUAJGgQIFilYFPJXiN7g9+N8gHIPFd+nt0KX2
8APklIOp9sZ14/j2tUEuCEzVZet9kGuvnjZedSNh8V696of8K+w6WiFbp6pamM20MGvwVFVfc+af
3RsEOrk3jNYqgY4Bo0CBAgUKFM0AlIBRoECBAgWKZgBKwCgaAovF4vF4HA4HLuouHvitABQnEAiK
TGih+UCQ43crSqAyWoFRtAigY8C/FOfPn4+Ojs7Pz8/Ozs7KysrNzeVwOEKhUCqV/vfLvwTAYNnZ
2amoqDAYDDKZDGzZD7di3bt3j4qKysnJAfmQnp5eUFAAMkEkEilPJgD06tWLzWYzmUz4cGUi8ctM
WLRo0fPnz4EWmZmZ4LOsrIzP50skkn9K8NcDyKylpcViseh0OolEQgipiWmqqak9ePAAFFxGRgbQ
uqqqCtRepdLa3NxcVVUVFByNRvtRWqNA8ZOAEvAvhY6ODiA2CoUCTAPgNmDclZCAgXgqcgDxgCfx
w+0XSNbY2BjkALgA9hHQA5fLVTYCBqUDcgDwDRAPEDDIhwYEbGRkBIoSKUfQUgEELBAIgAoypTk7
DRQcICHARoCDQZkizYimJAhyABQcRQ6QIeCzsrJSqWovAKhRoFzU1dUBByOlgzrBKJQWKAH/UgBb
ACwXsOnAQABLDS6A2wS4R3msNgCgE8RwAwYC119yTxMBaACYRWAlxWIxUBwYSpAJyPUP/JYmAthx
kAlASA0NDYSD62YCUo6AgYCXDPw/YOhBG0LZqAgICYoPqWygKBF3sIkJAq1BtoB2CSgsoD6PxwMF
p1Rag9oFBAOVChQcwsFN1BoFip8HlIB/KZCRRWATgZkAxhFYRmC/gAVXHu5BjCzgG+CeAlMLhPzh
9gvJBMBtCIdpamoi7q/yZAIkt+MkOUBhgXwAGVI3H5BcApkDmikgDqA3hfurPFoohARFCbQAWf2j
CBipvUB3pM2hPCpDciFBYYFCAXIq+t6bWygUKBoHSsC/GsAcIO4UICFgI5TNakNyCQGAeMB4IV3Q
P9YDVhAD8i2KJohSZQJWDkROpAu6QQTE0Ct0ASooIRUhKoByRFRo+mgCKDKQGtKHAXhdCQsOaA2E
rKs12gWNQmmBEvCvBmK4EQMhq0VzC1UPmFr8vHmkiAVHMgHpwFS2TIBqCQwAcaEa5AOiAtKcAgQM
KasKiBZAzh8ylxtpOCIFh8y9Uk6tkXr7o7RGgeInASXgXw2FTWxuQZoTiHFsbimaCkQLxI9vbll+
ERR89ltprQDSIEMZHcWPAkrAX4WlS5fu3bu3oKCgsLAQfFZVVSEdp80tFwoUKH4RgN9vZmZGpVKR
oRmUhlE0HSgBfxU6depkaWmZkZGRmZmZlZVVVlambMsfUaBA8VMBSJcth2Jl2m/ej4Wi6UAJ+KuA
w+HIZDKLxdLUhA+gBhfKtm4VBQoUPxXICmPw2wccTKFQkD1qmlsoFC0bKAH/N5CJJ1QqVUNDA7R8
wS+Qx+NJ5Whu0VCgQPGLgMwARxZ/M5lM0CJHCRhFE4FRwkmMSgjAtUKhUFALZPUFSsAoUPw+QJac
gbY4spMdXg50JBhFU/B/fw4BNbQT7KYAAAAASUVORK5CYII=

--Apple-Mail-18--951548461
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed
Content-Transfer-Encoding: 7bit





--Apple-Mail-18--951548461
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

--Apple-Mail-18--951548461--

From rrg-bounces@irtf.org  Sun Jan 25 13:26:28 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4B79128C1CE; Sun, 25 Jan 2009 13:26:28 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B4D3D3A6834; Sun, 25 Jan 2009 13:26:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.493
X-Spam-Level: 
X-Spam-Status: No, score=-2.493 tagged_above=-999 required=5 tests=[AWL=0.106,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id exVljrsm1LIC; Sun, 25 Jan 2009 13:26:26 -0800 (PST)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9]) by core3.amsl.com (Postfix) with ESMTP id DFCB23A680F; Sun, 25 Jan 2009 13:26:25 -0800 (PST)
Received: from m106.maoz.com (localhost [127.0.0.1]) by m106.maoz.com (8.14.3/8.14.3/Debian-4) with ESMTP id n0PLQ8ob012862;  Sun, 25 Jan 2009 13:26:08 -0800
Received: (from dmm@localhost) by m106.maoz.com (8.14.3/8.14.3/Submit) id n0PLQ8uJ012861; Sun, 25 Jan 2009 13:26:08 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Sun, 25 Jan 2009 13:26:08 -0800
From: David Meyer <dmm@1-4-5.net>
To: Benson Schliesser <bensons@queuefull.net>
Message-ID: <20090125212608.GA12742@1-4-5.net>
References: <9b942cbb0901251306h5cf184dbob1e672fce4b31dc2@mail.gmail.com>
MIME-Version: 1.0
In-Reply-To: <9b942cbb0901251306h5cf184dbob1e672fce4b31dc2@mail.gmail.com>
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-gpg-fingerprint: 2409 8B50 B389 A307 BA5C 2A16 3918 03D6 A099 D8A7
X-philosophy: "I just had to let it go. John Lennon"
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: rrg@irtf.org, lisp@ietf.org, routing-discussion@ietf.org
Subject: Re: [rrg] [lisp] Economic issues of long-path / stretched routing
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1365517040=="
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

--===============1365517040==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="T4sUOijqQbZv57TR"
Content-Disposition: inline


--T4sUOijqQbZv57TR
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

> Referring to the graphic Dino sent, which can also be found at
> http://www.lisp4.net/, one can see that ALT traffic between Savvis and
> Level(3) has several organizational AS-hops to traverse.=20

	This is just an artifact of the way I built it. You could
	put up a ALT tunnel betwen Savvis and L3 if that was of
	interest (and Savvis & L3 wouldn't have to further
	advertise those routes to the rest of the ALT). Also,
	its a somewhat artifcial observation because the L3 box
	is in London, so I thought it made sense to home it to
	RIPE. If L3 had ALT routers in the US, the situation
	would be likely different.

	BTW, the current configuration of the ALT is a first
	cut. There may be better ways to do it, but I did want to
	get something running so we could gain some experience.

	Or am I answering the wrong question?

	Dave

=09
=09

--T4sUOijqQbZv57TR
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkl82PAACgkQORgD1qCZ2Kc6PgCfbyr8MkXCj51s2RCWAXhwsoG7
2FsAnR0BHfqV/uhuyknUiD1ccR4R8ZhO
=ORNP
-----END PGP SIGNATURE-----

--T4sUOijqQbZv57TR--

--===============1365517040==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

--===============1365517040==--

From rrg-bounces@irtf.org  Sun Jan 25 14:24:13 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0465A3A6892; Sun, 25 Jan 2009 14:24:13 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D27153A6892 for <rrg@core3.amsl.com>; Sun, 25 Jan 2009 14:24:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.524
X-Spam-Level: 
X-Spam-Status: No, score=-6.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3wfNGI3ttOFT for <rrg@core3.amsl.com>; Sun, 25 Jan 2009 14:24:11 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id BE2A63A67E5 for <rrg@irtf.org>; Sun, 25 Jan 2009 14:24:11 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,323,1231113600"; d="scan'208";a="60932015"
Received: from sj-dkim-7.cisco.com ([171.68.10.88]) by sj-iport-5.cisco.com with ESMTP; 25 Jan 2009 22:22:52 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-7.cisco.com (8.12.11/8.12.11) with ESMTP id n0PMMqJ7032602;  Sun, 25 Jan 2009 14:22:52 -0800
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id n0PMMqfl001065; Sun, 25 Jan 2009 22:22:52 GMT
Received: from xmb-sjc-22c.amer.cisco.com ([128.107.191.47]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Sun, 25 Jan 2009 14:22:51 -0800
Received: from [10.0.1.4] ([10.21.64.235]) by xmb-sjc-22c.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 25 Jan 2009 14:22:33 -0800
In-Reply-To: <9b942cbb0901251349g105c86d9m98c54ba1b5596ec0@mail.gmail.com>
References: <9b942cbb0901251306h5cf184dbob1e672fce4b31dc2@mail.gmail.com> <20090125212608.GA12742@1-4-5.net> <9b942cbb0901251349g105c86d9m98c54ba1b5596ec0@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v753.1)
Message-Id: <FE47C611-5A41-44D5-8BDE-E531BFAEA902@cisco.com>
From: John Zwiebel <jzwiebel@cisco.com>
Date: Sun, 25 Jan 2009 12:22:35 -1000
To: Benson Schliesser <bensons@queuefull.net>
X-Mailer: Apple Mail (2.753.1)
X-OriginalArrivalTime: 25 Jan 2009 22:22:33.0425 (UTC) FILETIME=[6B267410:01C97F3B]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1943; t=1232922172; x=1233786172; c=relaxed/simple; s=sjdkim7002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jzwiebel@cisco.com; z=From:=20John=20Zwiebel=20<jzwiebel@cisco.com> |Subject:=20Re=3A=20[lisp]=20Economic=20issues=20of=20long- path=20/=20stretched=20routing |Sender:=20; bh=1OoWw6gyVFKcUTrRqtjBVOMEXPkX2V/fwQ1tRSt371c=; b=Qs4pmJk3/IYttalKpQS9hHeSjXV8ZaVtAa4i3gPWT5ZfIeJuwdFXUrJox3 BZsGe/wPAlX+OwXw8fs859im5fsG+eCntPdZ0T9cQjrFSuCEfSoRQSE8+G6O o76WuayY/e;
Authentication-Results: sj-dkim-7; header.From=jzwiebel@cisco.com; dkim=pass ( sig from cisco.com/sjdkim7002 verified; ); 
Cc: John Zwiebel <jzwiebel@cisco.com>, rrg@irtf.org, lisp@ietf.org, routing-discussion@ietf.org
Subject: Re: [rrg] [lisp] Economic issues of long-path / stretched routing
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

FWIW:
The sub-optimal routing will only be for the LISP map-request.
The reply and all encapsulated data traffic is between RLOCs
The ALT is merely there to provide the correct mapping.

Also, since a map-reply from any ETR for a given site will
provide you with all the RLOCs for that site, there is no
need to advertise any sub-prefix into the ALT.  Rather you
would advertise the most highly aggregated route you have
for your EID-site.  So the ALT table should be considerably smaller.


On Jan 25, 2009, at 11:49 AM, Benson Schliesser wrote:

> Dave-
>
> On Sun, Jan 25, 2009 at 3:26 PM, David Meyer <dmm@1-4-5.net> wrote:
>>        This is just an artifact of the way I built it. You could
>>        put up a ALT tunnel betwen Savvis and L3 if that was of
>>        interest (and Savvis & L3 wouldn't have to further
>>        advertise those routes to the rest of the ALT). Also,
>> ...
>>        Or am I answering the wrong question?
>
> I think you're answering the right question from the LISP-ALT
> perspective. It theoretically exists for other solutions in the same
> class, too, i.e. solutions that create a stretched path in order to
> follow address-assignment topology instead of underlying forwarding
> topology.
>
> In the LISP-ALT case, however, I'd like to explore your answer a bit
> further. Does this suggest that the answer is for my ALT AS to peer
> with all of my existing Internet peers, if I want to avoid suboptimal
> forwarding? If I did so, how would my ALT routing table size compare
> to my current routing table size? I'm imagining them the same size
> (i.e. comprised of supernets learned by my peers as well as
> less-specifics learned when my peers' customers multihome) but I might
> be missing something.
>
> Cheers,
> -Benson
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Sun Jan 25 15:54:10 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 663BE3A68DA; Sun, 25 Jan 2009 15:54:10 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 355B73A68DA for <rrg@core3.amsl.com>; Sun, 25 Jan 2009 15:54:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.976
X-Spam-Level: 
X-Spam-Status: No, score=-1.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jivGeLvdBSRR for <rrg@core3.amsl.com>; Sun, 25 Jan 2009 15:54:08 -0800 (PST)
Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.24]) by core3.amsl.com (Postfix) with ESMTP id 037533A67A8 for <rrg@irtf.org>; Sun, 25 Jan 2009 15:54:07 -0800 (PST)
Received: by qw-out-2122.google.com with SMTP id 9so1179613qwb.7 for <rrg@irtf.org>; Sun, 25 Jan 2009 15:53:49 -0800 (PST)
MIME-Version: 1.0
Received: by 10.215.41.6 with SMTP id t6mr1947198qaj.338.1232927629486; Sun,  25 Jan 2009 15:53:49 -0800 (PST)
In-Reply-To: <FE47C611-5A41-44D5-8BDE-E531BFAEA902@cisco.com>
References: <9b942cbb0901251306h5cf184dbob1e672fce4b31dc2@mail.gmail.com> <20090125212608.GA12742@1-4-5.net> <9b942cbb0901251349g105c86d9m98c54ba1b5596ec0@mail.gmail.com> <FE47C611-5A41-44D5-8BDE-E531BFAEA902@cisco.com>
Date: Sun, 25 Jan 2009 17:53:49 -0600
Message-ID: <9b942cbb0901251553u710be191s1dc960c4dd150ac8@mail.gmail.com>
From: Benson Schliesser <bensons@queuefull.net>
To: John Zwiebel <jzwiebel@cisco.com>
Cc: rrg@irtf.org, lisp@ietf.org, routing-discussion@ietf.org
Subject: Re: [rrg] [lisp] Economic issues of long-path / stretched routing
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1646328760=="
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

--===============1646328760==
Content-Type: multipart/alternative; boundary=0015175ce17263aa600461575581

--0015175ce17263aa600461575581
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

John-

I agree, in LISP the volume of ALT traffic is very small versus the volume
of encapsulated data traffic. This is one of the primary reasons I like
LISP-ALT as a near-term solution, to be honest.

The ALT peering, though, isn't 100% clear to me yet. Sorry if I'm just slow
today or have forgotten something that's already been discussed. (The recent
holiday seems to have effectively cleared my mind.)

My single-homed xTR (savvis) has one ALT peer right now (asp) and he
announces an aggregate net that covers my EID prefix. That's great from a
routing scale perspective. However if I were to multihome to another net
(dmm, for example) wouldn't I have to announce my EID into the ALT via that
path if I wanted to continue serving that EID during an outage of my primary
(asp) connectivity?

At the very least it has to be announced such that my primary upstream sees
it and can divert map-requests to my secondary path. So do all of my xTRs
need to have ALT tunnels to all of my EID allocators in order to avoid
de-aggregation in the ALT tables while maintaining fault tolerant
connectivity? What happens if an AS-wide fault takes down all of my
allocator's ALT routers? I understand that my RLOCs are still aggregated by
the underlying network's routing regardless.

It would be good to discuss what all of this looks like for network
engineering purposes. For instance from the perspective of ALT traffic
engineering, an end-site xTR with end users surfing the web will probably
have a moderate collection of EID mappings that stay refreshed (Google,
Twitter, corp intranet, etc) and a small collection of mappings that get
used and expire (my blog, which nobody reads twice). This is different from
an xTR in front of a public website, which will basically build a huge
collection of mappings and have to worry more about the database size than
anything else.

Cheers,
-Benson

PS - I hate to say this, but I will volunteer to edit a draft covering this
topic if one or more LISP researchers will help write it.

On Jan 25, 2009 4:22 PM, "John Zwiebel" <jzwiebel@cisco.com> wrote:

FWIW:
The sub-optimal routing will only be for the LISP map-request.
The reply and all encapsulated data traffic is between RLOCs
The ALT is merely there to provide the correct mapping.

Also, since a map-reply from any ETR for a given site will
provide you with all the RLOCs for that site, there is no
need to advertise any sub-prefix into the ALT.  Rather you
would advertise the most highly aggregated route you have
for your EID-site.  So the ALT table should be considerably smaller.

On Jan 25, 2009, at 11:49 AM, Benson Schliesser wrote:

> > Dave- > > On Sun, Jan 25, 2009 at 3:26 PM, David Meyer <dmm@1-4-5.net>
> wrote: >> >>       This is ...
>
> > _______________________________________________ > lisp mailing list >
> lisp@ietf.org > https://www....
>

--0015175ce17263aa600461575581
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<p>John-</p>
<p>I agree, in LISP the volume of ALT traffic is very small versus the volu=
me of encapsulated data traffic. This is one of the primary reasons I like =
LISP-ALT as a near-term solution, to be honest.</p>
<p>The ALT peering, though, isn&#39;t 100% clear to me yet. Sorry if I&#39;=
m just slow today or have forgotten something that&#39;s already been discu=
ssed. (The recent holiday seems to have effectively cleared my mind.)</p>

<p>My single-homed xTR (savvis) has one ALT peer right now (asp) and he ann=
ounces an aggregate net that covers my EID prefix. That&#39;s great from a =
routing scale perspective. However if I were to multihome to another net (d=
mm, for example) wouldn&#39;t I have to announce my EID into the ALT via th=
at path if I wanted to continue serving that EID during an outage of my pri=
mary (asp) connectivity?</p>

<p>At the very least it has to be announced such that my primary upstream s=
ees it and can divert map-requests to my secondary path. So do all of my xT=
Rs need to have ALT tunnels to all of my EID allocators in order to avoid d=
e-aggregation in the ALT tables while maintaining fault tolerant connectivi=
ty? What happens if an AS-wide fault takes down all of my allocator&#39;s A=
LT routers? I understand that my RLOCs are still aggregated by the underlyi=
ng network&#39;s routing regardless.</p>

<p>It would be good to discuss what all of this looks like for network engi=
neering purposes. For instance from the perspective of ALT traffic engineer=
ing, an end-site xTR with end users surfing the web will probably have a mo=
derate collection of EID mappings that stay refreshed (Google, Twitter, cor=
p intranet, etc) and a small collection of mappings that get used and expir=
e (my blog, which nobody reads twice). This is different from an xTR in fro=
nt of a public website, which will basically build a huge collection of map=
pings and have to worry more about the database size than anything else.</p=
>

<p>Cheers,<br>
-Benson</p>
<p>PS - I hate to say this, but I will volunteer to edit a draft covering t=
his topic if one or more LISP researchers will help write it.</p>
<p><blockquote>On Jan 25, 2009 4:22 PM, &quot;John Zwiebel&quot; &lt;<a hre=
f=3D"mailto:jzwiebel@cisco.com">jzwiebel@cisco.com</a>&gt; wrote:<br><br>FW=
IW:<br>
The sub-optimal routing will only be for the LISP map-request.<br>
The reply and all encapsulated data traffic is between RLOCs<br>
The ALT is merely there to provide the correct mapping.<br>
<br>
Also, since a map-reply from any ETR for a given site will<br>
provide you with all the RLOCs for that site, there is no<br>
need to advertise any sub-prefix into the ALT. &nbsp;Rather you<br>
would advertise the most highly aggregated route you have<br>
for your EID-site. &nbsp;So the ALT table should be considerably smaller.<p=
><font color=3D"#500050">


On Jan 25, 2009, at 11:49 AM, Benson Schliesser wrote:

</font></p><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex"><p><font color=3D"#500050">&gt; D=
ave-
&gt;
&gt; On Sun, Jan 25, 2009 at 3:26 PM, David Meyer &lt;<a href=3D"mailto:dmm=
@1-4-5.net">dmm@1-4-5.net</a>&gt; wrote:
&gt;&gt;
&gt;&gt; &nbsp; &nbsp; &nbsp; This is ...</font></p><p><font color=3D"#5000=
50">&gt; _______________________________________________
&gt; lisp mailing list
&gt; <a href=3D"mailto:lisp@ietf.org">lisp@ietf.org</a>
&gt; <a href=3D"https://www.">https://www.</a>...</font></p></blockquote>
<br>
</blockquote></p>

--0015175ce17263aa600461575581--

--===============1646328760==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

--===============1646328760==--

From rrg-bounces@irtf.org  Sun Jan 25 17:03:59 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 71E5B3A6828; Sun, 25 Jan 2009 17:03:59 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9D1463A6828 for <rrg@core3.amsl.com>; Sun, 25 Jan 2009 17:03:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.538
X-Spam-Level: 
X-Spam-Status: No, score=-6.538 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z3-LJsiee1wB for <rrg@core3.amsl.com>; Sun, 25 Jan 2009 17:03:58 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 8554C3A67A8 for <rrg@irtf.org>; Sun, 25 Jan 2009 17:03:58 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,323,1231113600";  d="scan'208,217";a="236462066"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-6.cisco.com with ESMTP; 26 Jan 2009 01:02:41 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n0Q12f0Y014282;  Sun, 25 Jan 2009 17:02:41 -0800
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id n0Q12f5A016521; Mon, 26 Jan 2009 01:02:41 GMT
Received: from xmb-sjc-22c.amer.cisco.com ([128.107.191.47]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Sun, 25 Jan 2009 17:02:41 -0800
Received: from [10.0.1.4] ([10.21.64.235]) by xmb-sjc-22c.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 25 Jan 2009 17:02:40 -0800
In-Reply-To: <9b942cbb0901251553u710be191s1dc960c4dd150ac8@mail.gmail.com>
References: <9b942cbb0901251306h5cf184dbob1e672fce4b31dc2@mail.gmail.com> <20090125212608.GA12742@1-4-5.net> <9b942cbb0901251349g105c86d9m98c54ba1b5596ec0@mail.gmail.com> <FE47C611-5A41-44D5-8BDE-E531BFAEA902@cisco.com> <9b942cbb0901251553u710be191s1dc960c4dd150ac8@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v753.1)
Message-Id: <DE783CA8-D2E1-4315-9FD2-2444255BDE81@cisco.com>
From: John Zwiebel <jzwiebel@cisco.com>
Date: Sun, 25 Jan 2009 15:02:37 -1000
To: Benson Schliesser <bensons@queuefull.net>
X-Mailer: Apple Mail (2.753.1)
X-OriginalArrivalTime: 26 Jan 2009 01:02:40.0680 (UTC) FILETIME=[C9853A80:01C97F51]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=7209; t=1232931761; x=1233795761; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jzwiebel@cisco.com; z=From:=20John=20Zwiebel=20<jzwiebel@cisco.com> |Subject:=20Re=3A=20[lisp]=20Economic=20issues=20of=20long- path=20/=20stretched=20routing |Sender:=20; bh=Un/S8mbEK+rN2/n+sp4S1iu+2gUyibLAT5sQLv1I2kk=; b=rcx4+peKNQL+w4gZoo0X30PlN96ICaqW98L0G9ZhyaAEDEswhYz3tOlJqg HGuHX39xdCKbTqR7AbBsOCcD/NXiAcuWUytwxVD7/FLjG+P63pA0EyQcCcE3 dpIDQj6nlV;
Authentication-Results: sj-dkim-2; header.From=jzwiebel@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); 
Cc: John Zwiebel <jzwiebel@cisco.com>, rrg@irtf.org, lisp@ietf.org, routing-discussion@ietf.org
Subject: Re: [rrg] [lisp] Economic issues of long-path / stretched routing
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1866717122=="
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

--===============1866717122==
Content-Type: multipart/alternative; boundary=Apple-Mail-59--925996064


--Apple-Mail-59--925996064
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed


On Jan 25, 2009, at 1:53 PM, Benson Schliesser wrote:

> My single-homed xTR (savvis) has one ALT peer right now (asp) and  
> he announces an aggregate net that covers my EID prefix. That's  
> great from a routing scale perspective. However if I were to  
> multihome to another net (dmm, for example) wouldn't I have to  
> announce my EID into the ALT via that path if I wanted to continue  
> serving that EID during an outage of my primary (asp) connectivity?
>

Yes you should, but that doesn't add another route to the ALT routing  
table.
> At the very least it has to be announced such that my primary  
> upstream sees it and can divert map-requests to my secondary path.
>
If your primary router goes down, yes.
> So do all of my xTRs need to have ALT tunnels to all of my EID  
> allocators in order to avoid de-aggregation in the ALT tables while  
> maintaining fault tolerant connectivity?
>
All of your xTRs need to connect to the ALT to get mapping  
information. (ie to send
map requests over the ALT and receive map-replies natively).  Each  
xTR would
advertise the same EID-prefix.  So no matter how many xTRs you have,  
only the
single EID-prefix is advertised. The ALT only carries EID-prefix  
routes (and next-hop
information for the ALT).  It need not carry the RLOC routes at all.   
Those are in the DFZ.
> What happens if an AS-wide fault takes down all of my allocator's  
> ALT routers? I understand that my RLOCs are still aggregated by the  
> underlying network's routing regardless.
>
Hopefully you'd have RLOCs from two different allocators.  When one  
goes down, the
other one is still available for map-requests.
>

Hope this helps
--Apple-Mail-59--925996064
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">
<br><div><div>On Jan 25, 2009, at 1:53 PM, Benson Schliesser =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: 2; text-align: =
auto; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0; "><p><span class=3D"Apple-style-span" =
style=3D"color: rgb(0, 0, 221); -webkit-text-stroke-width: -1; ">My =
single-homed xTR (savvis) has one ALT peer right now (asp) and he =
announces an aggregate net that covers my EID prefix. That's great from =
a routing scale perspective. However if I were to multihome to another =
net (dmm, for example) wouldn't I have to announce my EID into the ALT =
via that path if I wanted to continue serving that EID during an outage =
of my primary (asp) =
connectivity?</span></p></span></blockquote><div><br></div>Yes you =
should, but that doesn't add another route to the ALT routing =
table.<br><blockquote type=3D"cite"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0; "><p>At the very least it has to be =
announced such that my primary upstream sees it and can divert =
map-requests to my secondary path. </p></span></blockquote>If your =
primary router goes down, yes.<br><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0; "><p>So do all of my xTRs need to =
have ALT tunnels to all of my EID allocators in order to avoid =
de-aggregation in the ALT tables while maintaining fault tolerant =
connectivity? </p></span></blockquote><div>All of your xTRs need to =
connect to the ALT to get mapping information. (ie to =
send=A0</div><div>map requests over the ALT and receive map-replies =
natively). =A0Each xTR would</div><div>advertise the same EID-prefix. =
=A0So no matter how many xTRs you have, only the</div><div>single =
EID-prefix is advertised. The ALT only carries EID-prefix routes (and =
next-hop=A0</div><div>information for the ALT). =A0It need not carry the =
RLOC routes at all. =A0Those are in the DFZ.</div><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: 2; text-align: =
auto; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0; "><p>What happens if an AS-wide =
fault takes down all of my allocator's ALT routers? I understand that my =
RLOCs are still aggregated by the underlying network's routing =
regardless.</p></span></blockquote>Hopefully you'd have RLOCs from two =
different allocators. =A0When one goes down, the</div><div>other one is =
still available for map-requests. =A0<br><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0; =
"><p><br></p></span></blockquote><div><br></div>Hope this =
helps</div></body></html>=

--Apple-Mail-59--925996064--

--===============1866717122==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

--===============1866717122==--

From rrg-bounces@irtf.org  Sun Jan 25 20:36:38 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4767A3A68FD; Sun, 25 Jan 2009 20:36:38 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C141C3A68FD for <rrg@core3.amsl.com>; Sun, 25 Jan 2009 20:36:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.492
X-Spam-Level: 
X-Spam-Status: No, score=-6.492 tagged_above=-999 required=5 tests=[AWL=0.107,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VSrOQuzicqNA for <rrg@core3.amsl.com>; Sun, 25 Jan 2009 20:36:36 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by core3.amsl.com (Postfix) with ESMTP id 277043A679F for <rrg@irtf.org>; Sun, 25 Jan 2009 20:36:36 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 1761F6BE5F0; Sun, 25 Jan 2009 23:10:44 -0500 (EST)
To: lisp@ietf.org, routing-discussion@ietf.org, rrg@irtf.org
Message-Id: <20090126041045.1761F6BE5F0@mercury.lcs.mit.edu>
Date: Sun, 25 Jan 2009 23:10:44 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [rrg] Economic issues of long-path / stretched routing
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Can we _PLEASE_ stop cross-posting things to three lists at once? Thanks.

	Noel
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Mon Jan 26 01:11:43 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B69213A6A64; Mon, 26 Jan 2009 01:11:43 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2BEC93A6A64; Mon, 26 Jan 2009 01:11:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.138
X-Spam-Level: 
X-Spam-Status: No, score=-0.138 tagged_above=-999 required=5 tests=[AWL=-0.425, BAYES_05=-1.11, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7FBBGtbdIRHV; Mon, 26 Jan 2009 01:11:41 -0800 (PST)
Received: from imo-m11.mail.aol.com (imo-m11.mx.aol.com [64.12.143.99]) by core3.amsl.com (Postfix) with ESMTP id 5F4F13A6A60; Mon, 26 Jan 2009 01:11:41 -0800 (PST)
Received: from HeinerHummel@aol.com by imo-m11.mx.aol.com  (mail_out_v39.1.) id m.be9.46c7f8e2 (29678); Mon, 26 Jan 2009 04:11:16 -0500 (EST)
From: HeinerHummel@aol.com
Message-ID: <be9.46c7f8e2.36aed834@aol.com>
Date: Mon, 26 Jan 2009 04:11:16 EST
To: bensons@queuefull.net, lisp@ietf.org, routing-discussion@ietf.org, rrg@irtf.org
MIME-Version: 1.0
X-Mailer: 9.0 SE for Windows sub 5021
Subject: Re: [rrg] Economic issues of long-path / stretched routing
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0267168185=="
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

--===============0267168185==
Content-Type: multipart/alternative; boundary="-----------------------------1232961075"


-------------------------------1232961075
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

=20
In einer eMail vom 26.01.2009 04:07:23 Westeurop=E4ische Normalzeit schreibt=
 =20
bensons@queuefull.net:

I have a  concern about the economic aspects of stretch, specifically
related to  peering in routing systems where topology follows address
assignment more  closely than today's Internet.


This is one of the main differences with TARA: There a topological  view is=20
constructed such that stretch becomes 1 and  not like here  where stretch is=
=20
that what will turn out to be by chance.
=20
Heiner
=20

-------------------------------1232961075
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3DISO-8859-1">
<META content=3D"MSHTML 6.00.6000.16788" name=3DGENERATOR></HEAD>
<BODY id=3Drole_body style=3D"FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY:=20=
Arial"=20
bottomMargin=3D7 leftMargin=3D7 topMargin=3D7 rightMargin=3D7><FONT id=3Drol=
e_document=20
face=3DArial color=3D#000000 size=3D2>
<DIV>
<DIV>In einer eMail vom 26.01.2009 04:07:23 Westeurop=E4ische Normalzeit sch=
reibt=20
bensons@queuefull.net:</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid"><=
FONT=20
  style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000 size=
=3D2>I have a=20
  concern about the economic aspects of stretch, specifically<BR>related to=20
  peering in routing systems where topology follows address<BR>assignment mo=
re=20
  closely than today's Internet.</FONT></BLOCKQUOTE></DIV>
<DIV></DIV>
<DIV>This is one of the main differences with TARA: There&nbsp;a topological=
=20
view is constructed such that stretch&nbsp;becomes 1 and&nbsp; not like here=
=20
where stretch is that what will turn out to be by chance.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Heiner</DIV>
<DIV>&nbsp;</DIV></FONT></BODY></HTML>

-------------------------------1232961075--

--===============0267168185==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

--===============0267168185==--

From rrg-bounces@irtf.org  Mon Jan 26 01:46:42 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B12D628C1BD; Mon, 26 Jan 2009 01:46:42 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 366A828C1BD; Mon, 26 Jan 2009 01:46:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.86
X-Spam-Level: 
X-Spam-Status: No, score=-0.86 tagged_above=-999 required=5 tests=[AWL=0.342,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RdrNYnROCUTp; Mon, 26 Jan 2009 01:46:40 -0800 (PST)
Received: from imo-m22.mail.aol.com (imo-m22.mx.aol.com [64.12.137.3]) by core3.amsl.com (Postfix) with ESMTP id 6019728C1B1; Mon, 26 Jan 2009 01:46:39 -0800 (PST)
Received: from HeinerHummel@aol.com by imo-m22.mx.aol.com  (mail_out_v39.1.) id 9.c07.530a414a (29678); Mon, 26 Jan 2009 04:46:16 -0500 (EST)
From: HeinerHummel@aol.com
Message-ID: <c07.530a414a.36aee068@aol.com>
Date: Mon, 26 Jan 2009 04:46:16 EST
To: rrg@irtf.org, lisp@ietf.org, routing-discussion@ietf.org
MIME-Version: 1.0
X-Mailer: 9.0 SE for Windows sub 5021
Subject: Re: [rrg] [lisp] Economic issues of long-path / stretched routing
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0036552333=="
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

--===============0036552333==
Content-Type: multipart/alternative; boundary="-----------------------------1232963176"


-------------------------------1232963176
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

=20
In einer eMail vom 26.01.2009 04:07:41 Westeurop=E4ische Normalzeit schreibt=
 =20
jzwiebel@cisco.com:

The  sub-optimal routing will only be for the LISP map-request.
The reply and  all encapsulated data traffic is between RLOCs
The ALT is merely there to  provide the correct mapping.





Prior arguing with long-path, stretch etc. I have another informative =20
question (maybe I missed something too during the discussion): Why LISP 1.5=20=
?  Why=20
not LISP 2 ? or directly:
Why doesn't the ITR intercept and enhance the DNS lookup as to also request=20=
=20
the eRLOC address in addition to the dest IP address? It can also intercept=20
the  respective response and store (EID, eRLOC).
=20
I also ask this because wrt my TARA solution I would do the alike: The =20
difference is only that the eRLOC information, to be retrieved from  DNS, ar=
e just=20
the geographical coordinates of the ETR (as by experimental  RFC 1712).
So far I cannot see why there is a  (compelling ?) reason fro the ALT =20
hierarchy at all. =20
=20
Thanks for answers to my question,
Heiner
=20
=20

-------------------------------1232963176
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3DISO-8859-1">
<META content=3D"MSHTML 6.00.6000.16788" name=3DGENERATOR></HEAD>
<BODY id=3Drole_body style=3D"FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY:=20=
Arial"=20
bottomMargin=3D7 leftMargin=3D7 topMargin=3D7 rightMargin=3D7><FONT id=3Drol=
e_document=20
face=3DArial color=3D#000000 size=3D2>
<DIV>
<DIV>In einer eMail vom 26.01.2009 04:07:41 Westeurop=E4ische Normalzeit sch=
reibt=20
jzwiebel@cisco.com:</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid"><=
FONT=20
  style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000 size=
=3D2>The=20
  sub-optimal routing will only be for the LISP map-request.<BR>The reply an=
d=20
  all encapsulated data traffic is between RLOCs<BR>The ALT is merely there=20=
to=20
  provide the correct mapping.<BR><BR></FONT></BLOCKQUOTE></DIV>
<DIV></DIV>
<DIV>&nbsp;</DIV>
<DIV>Prior arguing with long-path, stretch etc. I have another informative=20
question (maybe I missed something too during the discussion): Why LISP 1.5=20=
?=20
Why not LISP 2 ? or directly:</DIV>
<DIV>Why doesn't the ITR intercept and enhance the DNS lookup as to also req=
uest=20
the eRLOC address in addition to the dest IP address? It can also intercept=20=
the=20
respective response and store (EID, eRLOC).</DIV>
<DIV>&nbsp;</DIV>
<DIV>I also ask this because wrt my TARA solution I would do the alike: The=20
difference is only that the eRLOC information, to be retrieved from=20
DNS,&nbsp;are just the geographical coordinates of the ETR (as by experiment=
al=20
RFC 1712).</DIV>
<DIV>So far I cannot see why there is a&nbsp; (compelling ?) reason fro the=20=
ALT=20
hierarchy at all.&nbsp;&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>Thanks for answers to my question,</DIV>
<DIV>Heiner</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV></FONT></BODY></HTML>

-------------------------------1232963176--

--===============0036552333==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

--===============0036552333==--

From rrg-bounces@irtf.org  Mon Jan 26 08:26:01 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9E9CE28C14F; Mon, 26 Jan 2009 08:26:01 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B003B28C237 for <rrg@core3.amsl.com>; Mon, 26 Jan 2009 08:25:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.509
X-Spam-Level: 
X-Spam-Status: No, score=-6.509 tagged_above=-999 required=5 tests=[AWL=0.090,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yBv0l7sLB8de for <rrg@core3.amsl.com>; Mon, 26 Jan 2009 08:25:59 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 8B77C3A687B for <rrg@irtf.org>; Mon, 26 Jan 2009 08:25:59 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,326,1231113600"; d="scan'208";a="236808136"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 26 Jan 2009 16:24:37 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n0QGOaOA016788;  Mon, 26 Jan 2009 08:24:36 -0800
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n0QGOaCa005266; Mon, 26 Jan 2009 16:24:36 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Mon, 26 Jan 2009 08:24:36 -0800
Received: from dino-macbook.dhcp.nanog.merit.net ([10.21.121.201]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Mon, 26 Jan 2009 08:24:36 -0800
Message-Id: <5F9CF4DF-64C8-4D1A-9FF5-DE4CA17B12C4@cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: HeinerHummel@aol.com
In-Reply-To: <c07.530a414a.36aee068@aol.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Mon, 26 Jan 2009 08:24:36 -0800
References: <c07.530a414a.36aee068@aol.com>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 26 Jan 2009 16:24:36.0301 (UTC) FILETIME=[943327D0:01C97FD2]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=671; t=1232987077; x=1233851077; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dino@cisco.com; z=From:=20Dino=20Farinacci=20<dino@cisco.com> |Subject:=20Re=3A=20[lisp]=20Economic=20issues=20of=20long- path=20/=20stretched=20routing |Sender:=20; bh=kmB7erxMlm7jtD4oabY5dE23ZdnPNQ7lRlKH+3QIWEM=; b=KGcAd3dGqbI6O0pdSsfnKrpe4L7rZCFbgzH88zAJwa/XOFLVomIfhmdZzK DP3Kg2YEjFJeBTzA2GNXqb0TvRU6u+fduwNJzTBwKsqI/lZTMZlpgUgMbqvl IkX6fHS5vg;
Authentication-Results: sj-dkim-3; header.From=dino@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); 
Cc: rrg@irtf.org, lisp@ietf.org, routing-discussion@ietf.org
Subject: Re: [rrg] [lisp] Economic issues of long-path / stretched routing
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

> Prior arguing with long-path, stretch etc. I have another  
> informative question (maybe I missed something too during the  
> discussion): Why LISP 1.5 ? Why not LISP 2 ? or directly:
> Why doesn't the ITR intercept and enhance the DNS lookup as to also  
> request the eRLOC address in addition to the dest IP address? It can  
> also intercept the respective response and store (EID, eRLOC).

1) Because not all communication uses DNS.
2) Because DNS queries go out one xTR and replies can come in through  
another xTR.
3) Because you don't want a architectural circular dependency between  
directory and routing.

Do you want more reasons?

Dino
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Mon Jan 26 08:28:42 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1864B3A6A45; Mon, 26 Jan 2009 08:28:42 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A032328C1FF for <rrg@core3.amsl.com>; Mon, 26 Jan 2009 08:28:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.51
X-Spam-Level: 
X-Spam-Status: No, score=-6.51 tagged_above=-999 required=5 tests=[AWL=0.089,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gWi2hxfjZM4K for <rrg@core3.amsl.com>; Mon, 26 Jan 2009 08:28:39 -0800 (PST)
Received: from virtualized.org (trantor.virtualized.org [204.152.189.190]) by core3.amsl.com (Postfix) with ESMTP id 42BEC3A6A45 for <rrg@irtf.org>; Mon, 26 Jan 2009 08:28:39 -0800 (PST)
Received: from wlan39-077.mdr.icann.org (wlan39-077.mdr.icann.org [192.0.39.77]) by virtualized.org (Postfix) with ESMTP id 18A56440066; Mon, 26 Jan 2009 08:27:56 -0800 (PST)
Message-Id: <A40E5693-884A-4A24-A18A-F72AD50F0BFA@virtualized.org>
From: David Conrad <drc@virtualized.org>
To: Yakov Rekhter <yakov@juniper.net>
In-Reply-To: <200901222312.n0MNClM76217@magenta.juniper.net>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Mon, 26 Jan 2009 08:27:56 -0800
References: <20090120190744.GA9467@1-4-5.net> <49765FFB.1010709@piuha.net> <200901222312.n0MNClM76217@magenta.juniper.net>
X-Mailer: Apple Mail (2.930.3)
Cc: RRG RG <rrg@irtf.org>
Subject: Re: [rrg] Please respond: Questions from the IESG as to whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

[cc's reduced to keep Noel's head from exploding :-)]

Yakov,

On Jan 22, 2009, at 3:12 PM, Yakov Rekhter wrote:
> The question to ask is whether LISP is an appropriate solution to
> the problems discussed at the IAB's October, 2006 Routing and
> Addressing Workshop.

That is _a_ question, but not necessarily _the_ question.  Perhaps a  
better question is whether or not experimenting with LISP will provide  
insights into appropriate solutions.

> Concerns with scaling and operational properties of these
> techniques have been raised many times before (both at the previous
> BOF, as well as on the RRG mailing list). Yet the LISP proponents
> still did not adequately address these concerns.

Oddly, I'm reminded of http://ars.userfriendly.org/cartoons/? 
id=20090125.

Perhaps the reasons LISP proponents haven't adequately addressed those  
concerns is because they are not addressable with the underlying LISP  
assumptions?  Your criticism feels approximately equivalent to the  
arguments made against IP by telco folks when they'd list all the ways  
in which IP violated circuit switching assumptions.  The appropriate  
response is probably along the lines of "well, duh."  When you change  
underlying assumption, you get a different answer with different costs  
and benefits.  TANSTAAFL.

LISP, as with _any_ loc/id approach I am aware of, requires a some  
form of mapping system to translate locators into identifiers.  You  
can argue about whether you want a pull-based mapping, a push-based  
mapping, or some hybrid, but it is a fundamental assumption that a  
separate mapping system exists.

It can be argued that the requirement for a mapping system will doom  
any loc/id approach (as it was argued that without bandwidth  
reservation from source to destination any packet switched approach  
would be doomed), however I, for one, remain unconvinced and hence  
believe experimentation to find out what the other characteristics of  
loc/id separation might be is worth the effort.

Regards,
-drc

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Mon Jan 26 08:35:35 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 104FB3A6A45; Mon, 26 Jan 2009 08:35:35 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A2C2328C229 for <rrg@core3.amsl.com>; Mon, 26 Jan 2009 08:35:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.511
X-Spam-Level: 
X-Spam-Status: No, score=-6.511 tagged_above=-999 required=5 tests=[AWL=0.088,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 91iNm6aLOS9J for <rrg@core3.amsl.com>; Mon, 26 Jan 2009 08:35:34 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 8D1623A687E for <rrg@irtf.org>; Mon, 26 Jan 2009 08:35:34 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,326,1231113600"; d="scan'208";a="133552594"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-1.cisco.com with ESMTP; 26 Jan 2009 16:34:17 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n0QGYHxH014143;  Mon, 26 Jan 2009 08:34:17 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id n0QGYHCJ006632; Mon, 26 Jan 2009 16:34:17 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Mon, 26 Jan 2009 08:34:16 -0800
Received: from dino-macbook.dhcp.nanog.merit.net ([10.21.121.201]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Mon, 26 Jan 2009 08:34:16 -0800
Message-Id: <59EA5644-C135-48AD-897A-5F0ED7156E17@cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: Benson Schliesser <bensons@queuefull.net>
In-Reply-To: <9b942cbb0901251553u710be191s1dc960c4dd150ac8@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Mon, 26 Jan 2009 08:34:15 -0800
References: <9b942cbb0901251306h5cf184dbob1e672fce4b31dc2@mail.gmail.com> <20090125212608.GA12742@1-4-5.net> <9b942cbb0901251349g105c86d9m98c54ba1b5596ec0@mail.gmail.com> <FE47C611-5A41-44D5-8BDE-E531BFAEA902@cisco.com> <9b942cbb0901251553u710be191s1dc960c4dd150ac8@mail.gmail.com>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 26 Jan 2009 16:34:16.0428 (UTC) FILETIME=[EDFB82C0:01C97FD3]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2759; t=1232987657; x=1233851657; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dino@cisco.com; z=From:=20Dino=20Farinacci=20<dino@cisco.com> |Subject:=20Re=3A=20[lisp]=20Economic=20issues=20of=20long- path=20/=20stretched=20routing |Sender:=20; bh=67umW8rbUIs2R2FNxLS17YT9OrSLMReNhzF+BxdQK5s=; b=ZvtM3tx/y9ucaubO1pEGuVntRZqBBcJWmowUgEGJYANsgzm7oV5l97AdHZ ttXk2mSTNIzn6T0eWXRH/6rD6JldD5lW77wN4V0BSKstObT3ryD+WxxDG75G OJNup9n2N/;
Authentication-Results: sj-dkim-2; header.From=dino@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); 
Cc: John Zwiebel <jzwiebel@cisco.com>, rrg@irtf.org, lisp@ietf.org, routing-discussion@ietf.org
Subject: Re: [rrg] [lisp] Economic issues of long-path / stretched routing
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

> My single-homed xTR (savvis) has one ALT peer right now (asp) and he  
> announces an aggregate net that covers my EID prefix. That's great  
> from a routing scale perspective. However if I were to multihome to  
> another net (dmm, for example) wouldn't I have to announce my EID  
> into the ALT via that path if I wanted to continue serving that EID  
> during an outage of my primary (asp) connectivity?
>

Yes, you would. And you would peer at the level before the aggregation  
level router. So in the real world, you would peer with sub-parts of  
your region's registry.

> At the very least it has to be announced such that my primary  
> upstream sees it and can divert map-requests to my secondary path.  
> So do all of my xTRs need to have ALT tunnels to all of my EID
>

Not divert, but you want the shortest path to your site for Map- 
Requests. So each of your xTRs will have GRE tunnels where their  
"tunnel source <foo>" configuration will have <foo> be the locator  
address from each attached upstream.

> allocators in order to avoid de-aggregation in the ALT tables while  
> maintaining fault tolerant connectivity? What happens if an AS-wide  
> fault takes down all of my allocator's ALT routers? I understand  
> that my RLOCs are still aggregated by the underlying network's  
> routing regardless.
>

Right, no deaggregation anywhere. You don't have to TE with more  
specific injection on the ALT, you use your tunnel locators for this.

Also, we want you to have a low opex xTRs, so when *you do not run BGP  
on your xTRs*, it will be your upstreams will "redistribute static tag  
<foo>". And they won't need to deaggregate as well because you will be  
*within* their aggregation level.

> It would be good to discuss what all of this looks like for network  
> engineering purposes. For instance from the perspective of ALT  
> traffic engineering, an end-site xTR with end users surfing the web  
> will probably have a moderate collection of EID mappings that stay  
> refreshed (Google, Twitter, corp intranet, etc) and a small  
> collection of mappings that get used and expire (my blog, which  
> nobody reads twice). This is different from an xTR in front of a  
> public website, which will basically build a huge collection of  
> mappings and have to worry more about the database size than  
> anything else.
>

Mappings get refreshed locally in the xTR based on data flow. So you  
don't need to continually Map-Request the site. Plus, you can use the  
old ARP trick. That is, give yourself enough time before the entry  
times out, to request to see if the mapping is still current. And only  
do that when there is data flow against the entry.

Dino



_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Mon Jan 26 08:52:21 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2BE7C3A6BBF; Mon, 26 Jan 2009 08:52:21 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A51B93A6807; Mon, 26 Jan 2009 08:52:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.441
X-Spam-Level: 
X-Spam-Status: No, score=-6.441 tagged_above=-999 required=5 tests=[AWL=0.158,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 80-tVEIvTkEg; Mon, 26 Jan 2009 08:52:17 -0800 (PST)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id 9384D3A6AC2; Mon, 26 Jan 2009 08:52:17 -0800 (PST)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231]) by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n0QGpSZL009934 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 26 Jan 2009 08:51:28 -0800 (PST)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n0QGpRQs026287; Mon, 26 Jan 2009 08:51:27 -0800 (PST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n0QGpRls026233; Mon, 26 Jan 2009 08:51:27 -0800 (PST)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 26 Jan 2009 08:51:27 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 26 Jan 2009 08:51:26 -0800
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1057A286E@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Int-area] [rrg] Please respond: Questions from the IESG as towhether a WG forming BOF is necessary for LISP
Thread-Index: Acl+XRwSDsratB6RTYiirIK+b/yWgABaw6XQ
References: <20090120190744.GA9467@1-4-5.net><49765FFB.1010709@piuha.net>	<200901222339.n0MNddM88868@magenta.juniper.net><75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com><497B1F7A.9030407@firstpr.com.au> <6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Dino Farinacci" <dino@cisco.com>, "Robin Whittle" <rw@firstpr.com.au>
X-OriginalArrivalTime: 26 Jan 2009 16:51:27.0390 (UTC) FILETIME=[547BD3E0:01C97FD6]
Cc: rrg RG <rrg@irtf.org>, int-area@ietf.org, lisp@ietf.org, routing-discussion@ietf.org
Subject: Re: [rrg] [Int-area] Please respond: Questions from the IESG as towhether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Here is some follow-up on Dino's message wrt RANGER
and LISP comparisons:

> -----Original Message-----
> From: Dino Farinacci [mailto:dino@cisco.com] 
> Sent: Saturday, January 24, 2009 10:26 AM
> To: Robin Whittle
> Cc: rrg RG; int-area@ietf.org; lisp@ietf.org; 
> routing-discussion@ietf.org
> Subject: Re: [Int-area] [rrg] Please respond: Questions from 
> the IESG as towhether a WG forming BOF is necessary for LISP
> 
> >   LISP has too many fundamental problems to be considered a
> >   potentially practical solution.  Some of these problems require
> 
> LISP is not perfect and still evolving but let me point out 
> that every  
> design has fundamental problems. At this scale, it's very hard to be  
> perfect Robin. And as Noel has stated so many times, the hard  
> decisions must be made to incrementally deploy this. So things might  
> not look pretty on the surface, but jeez, you got to do what you got  
> to do. Else, this will all be academic.
> 
> We really want to solve this problem, sincerely. This is not lip  
> service, we are not just writing papers, we want to rev the 
> Internet,  
> this is serious.
> 
> I want to address each of your 7 points below. I have cc'ed 
> the lisp@ietf.org 
>   mailing list so the folks who want to focus on details of LISP can  
> see this thread.
> 
> > 1 - Delays in delivering initial packets in a flow.  This is either
> >    due to sending the packets along the ALT network (which takes
> >    time and involves sending substantial volumes of data packets
> >    over the ALT network, rather than just mapping requests) or to
> >    sending mapping requests only, and waiting for the ITR to get a
> >    response before it attempts to send traffic packets.
> 
> We have a memory/bandwidth tradeoff. So we have to make a 
> hard design  
> call. I'd rather have mappings cached and timed out so they can be  
> updated when they need to then to hold all the possible mappings for  
> the Internet in an ITR.
> 
> There is no such thing of a free lunch. You either store all 
> possible  
> mappings or you fetch them when you need them.

RANGER is following the eFIT/APT model (and perhaps ALT
also?). It allows some stretch for initial packets then
route-optimized paths for the rest, i.e., intial packets
are forwarded; not dropped.
 
> >    According to: http://www.lisp4.net/docs/lisp-ausnog02.ppt pp 10
> >    & 11 the experimental LISP ALT network's ITRs drop initial
> >    packets and send brief map request messages.   Even if we think
> >    this delay doesn't matter, I am sure enough potential adopters
> >    would - and therefore make it difficult or impossible for LISP or
> >    any other such solution to be widely enough adopted to solve the
> >    routing scaling problem.
> 
> Then why was/is ARP deployed in a 10^4 host-based bridged 
> network with  
> basically the same properties. First packet loss is not persistent  
> when you look at all the traffic that originates from a 
> source site to  
> another destination site.
> 
> The host vendors are probably thinking, if we do LISP in the 
> host, you  
> could wait to send your TCP SYN before the mapping is 
> available. Guess  
> what, you don't send that TCP SYN before you get the DNS 
> Reply. ;-) I  
> wonder why? Well I'll spell it out. If a host needs an 
> address to make  
> the connection, we can say it also needs a locator to make a 
> connection.
> 
> The design choice of LISP *is to just change software in CPE 
> devices*  
> to get the feature of decoupling rather than changing all the 
> hosts at  
> a site. That's a huge deployment advantage. So these CPE devices get  
> packets before they have mappings. We don't even want to consider a  
> host to CPE router signaling protocol and all it's complexities to  
> solve this and to keep the architecture pure, we don't want to snoop  
> on DNS, SIP, or any other protocol that can give us a hint on where  
> the host is about to send a packet.
> 
> So the cost is *either* first packet loss or sending the 
> packet on the  
> ALT using it as a request for a mapping.
> 
> > 2 - LISP-ALT's long-path problem
> >      http://psg.com/lists/rrg/2008/msg01676.html
> >      http://www.antd.nist.gov/~ksriram/strong_aggregation.png
> >
> >      [Fix? Another fundamental problem in the architecture.  Could
> >       be partially solved by more meshiness, but that would greatly
> >       increase the complexity of the network and so raise more
> >       scaling problems.]
> 
> Well this I believe is a duplicate of 1 above. So it's not really  
> *another* problem.
> 
> > 3 - Problems creating a highly aggregated ALT network in order to
> >    speed the flow of packets up and down the hierarchy, while also
> >    making the network robust against the failure of its routers and
> >    tunnels.  This has not been discussed much on the RRG, but it is
> >    an obvious problem.
> 
> If we can do this with BGP, which we have decades of existence proof  
> why can't we do this with a tunnel topology 1) where a tunnel can be  
> rehomed much quicker and easily than physical links and boxes 
> we have  
> to do with today, allowing aggregation to occur at the edges of the  
> ALT network, and 2) these tunnels stay up because there is robust  
> connectivity below the tunnel level to keep them up, hence 
> there will  
> be less route-flaps for EID-prefixes.
> 
> I think it's the complete opposite of what you claim. I think 
> BGP will  
> be more stable and scalable then the underlying BGP. Plus, what we  
> propose for the use-case of BGP uses quite a few features of it.  
> Recall this is eBGP over GRE.
> 
> We have an infrastructure where we can 1) ping to see liveness of  
> nodes on the ALT. We have traceroute to determine the path a Map- 
> Request takes on the ALT. We can ping/traceroute "underneath" so we  
> can see the diameter of the tunnel. Not only do we have a 
> solution but  
> we use existing rudimentary tools for management.
> 
> And the address allocation hierarchy can map this logical ALT  
> topology. And if the Registries are involved in managing part 
> of this  
> ALT network (which we hope and think they will), we can keep this  
> consistent relationship.
> 
> Do you realize the goodness of this? It's huge Robin.
> 
> There's more too, you then throw SIDR in the mix and we have secured  
> the ALT, we have secured mappings, we created a PKI for routing use.  
> In fact, the first SIDR deployment could happen on the ALT to be  
> verified/experimented before it goes on the underlying BGP.

I think RANGER could potentially benefit from SIDR too,
but RANGER has a means for ingress filtering even on
networks where spoofing is possible. The philosophy in
RANGER is that sites guard their *own* borders even when
there is expectation that other sites will behave in a
trustworthy fashion.

> And note, that the infrastructure will/does carry exactly 2 address- 
> families. So we can do 6-to-6-over-4 with this approach. That 
> means we  
> can get two site to be *IPv6-only* and be able to talk to each other.
> 
> If you are a IPv6-only site now or a dual-stack site, you could talk  
> to the new IPv6 Google services. I think this is a pretty 
> huge feature.
> 
> This is clean and architecturally pure, no double NATs, no CGNS, and  
> no applications breaking.

You are describing here the exact use case that RANGER
was designed to accommodate. IPv6 over IPv4 across one or
several recursive enterprise-within-enterprise nestings
gives IPv6 end-to-end with no NATting. 
 
> > 4 - LISP-ALT's Aggregation implies provider dependence.
> >    This is Christian Vogt's critique:
> >    http://psg.com/lists/rrg/2008/msg00259.html
> 
> Not true. Aggregation here is for the EID-prefix. Service 
> providers do  
> not carry EID-prefixes in their cores so you don't depend on 
> them. The  
> decoupling of the address creates this. The dependence is now on the  
> ALT. And if your site resides in a specific region of the world, you  
> get your EID-prefixes from that registry. So readdressing 
> your domain  
> would only occur if you moved it from one region to another (let's  
> leave mobile ASes out of this for now).

RANGER supports true PI prefix delegation such that
readdressing is not needed when the site moves. End
systems that move from site to site may incur readdressing
and need a mobility handling mechanism like HIP or MIP,
but that is an end system mobility consideration and
not a site mobility consideration.

> > 5 - Path MTU Discovery problems.  Despite Fred Templin, myself and
> >    others discussing the inherent PMTUD problems in any map-encap
> >    proposal, there has been nothing from the LISP team to indicate
> >    they have a solution.  They seem to think there is no problem.
> 
> In section 5.4 of draft-farinacci-lisp-11.txt we describe two 
> proposed  
> solutions, one is stateless, and the other is stateful. The stateful  
> creates no new table data structures but requires storing an 
> addition  
> 2-bytes of effective-MTU state per mapping.

In the "stateless" case, having the LISP ITR return
packet-too-bigs with degenerate MTUs (i.e., MTUs less
than 1500) is going to leave source hosts with an
unsatisfactory experience that they would not incur
without an ITR/ETR in the middle.

In the stateful case, LISP relies on a brittle mechanism
that has known vulnerabilities (e.g., [RFC2923]) and can
easily be spoofed by off-path attackers.

RANGER/SEAL fixes both of these problems and much more.  

> > 6 - Lack of business case for LISP's Proxy Tunnel Routers:
> >    http://psg.com/lists/rrg/2008/msg02021.html
> 
> You cannot fault a technical design for a business case. A PTR is  
> solving a technical problem. And if we want to *truly* keep 
> lots of PI  
> type routes out of the core *and* avoid NAT solutions which are just  
> way too high in opex, the PTR is the only solution we have to turn to.
> 
> And on the contrary, I do believe service providers, interconnect  
> providers, registries, third-parties and even governments 
> will provide  
> PTR services. Will they make a ton of money out of it, well that  
> remains to be seen.
> 
> > 7 - The scaling problems of potentially thousands of ITRs each
> >    probing reachability to one ETR, and likewise, one ITR probing
> >    reachability to many ETRs - this is one view of the "Locator Path
> >    Liveness Problem" of draft-meyer-loc-id-implications-00.
> >    http://www.irtf.org/pipermail/rrg/2009-January/000809.html
> 
> That is not in the LISP design. Everyone just thinks it is.  ;-)
> 
> Dave and Darrel's draft is providing a warning about how bad probing  
> can be. They do not take a position whether it should go into any  
> proposal. They are just saying, beware of the Frankenstein that may  
> result and can be an interpretation to not do probing at all.
> 
> Like I mentioned in a previous RRG email message, one has to ask the  
> question if an ITR *should* switch from one RLOC to another 
> when there  
> *may* be a path failure *somewhere in the middle of the network*.  
> Please note my very fine qualifications.

Fine qualifications noted (I think). About the LISP
locator reachability bits, that seems like a lot of
overhead to carry on each and every packet, and it
also seems to assume symmetric paths. RANGER assumes
unidirectional tunnels and path asymmetry, i.e., if
Site 1's packets use ITR A and go through ETR B at
Site 2, the return traffic could actually come through
Site 2's ITR C. In the LISP locator reachability case,
how does C know anything about the reachability of A?

Although RANGER could send locator reachability bits
in control messages as an optimization, its primary
mechanism is through having the ITR probe the forward
path to the ITR. Probing is by setting an "ack request"
bit on every Nth data packet (+/- some delta if
randomization is desired) and then observing whether
a steady stream of ACKs comes back.

LISP also doesn't seem to take into account that a multi-
homed site can partition, such that locator reachability
does not necessarily imply end system reachability via
specific locators. Nor does it provide a means for an ETR
(A) to inform the ITR of a better ETR (B) when paths get
stretched. RANGER has a means to accommodate this.

> If we want to solve this problem, we could do this today by having a  
> host switch it's TCP connection to another A record. This doesn't  
> happen today because people deal with packet loss, since it doesn't  
> last long *and* rerouting actually works quite well.
> 
> Van Jacobson always made this comment and I'll never forget it, "The  
> fact that the Internet drops packets is it's greatest feature".
> 
> What else can either an xTR or TCP host do when sending ICMP  
> Unreachables are off by default in most modern routers, or they are  
> filtered by firewalls, and route aggregation hides failures close to  
> packet sources.

RANGER can listen for ICMP unreachables coming from network
middleboxes that it can verify as on-path by checking the
SEAL_ID. In a RANGER world, network middleboxes would be
encouraged to turn the ICMPs back on because site border
xTRs will have a means to detect spoofing (i.e., the SEAL_ID).
But, this is an optimization only; nothing in RANGER depends
on getting the ICMPs from middleboxes.

That's all for now.

Fred
fred.l.templin@boeing.com
 
> >> Unless these concerns are adequately addressed, claiming that LISP
> >> is an appropriate solution to the problems discussed at the IAB's
> >> October 2006 Routing and Addressing Workshop is nothing more than
> >> a proof by an emphatic assertion.
> >
> > I agree entirely.
> >
> > I believe the LISP team could have made much better use of the RRG -
> > by participating fully in the debates resulting from these 
> critiques.
> 
> We were asked to do research in RRG. That was a reasonable 
> request. So  
> the research stuff in LISP has been and will continue to be 
> presented  
> in RRG.
> 
> As for the engineering issues, the real details and bits and 
> bytes, we  
> want a forum to discuss and work out issues in an open forum. I've  
> been going to IETF for 20 years now, that forum is called a working  
> group.
> 
> The working group doesn't have to standardize what it is working on.  
> And the charter and the numerous requests we have made requests *for  
> an experimental working group*.
> 
> > Experiments won't help solve most of these problems.  I am not
> > against experimentation and I think it is great that there is a LISP
> > experimental network.
> >
> > However, I would never have taken a proposal to the point of writing
> > code, running a network and inviting others to write compatible
> > implementations when the proposal had so many fundamental problems.
> 
> There is constant implementation feedback back into the design.  
> Experienced engineers know how this cycle works. You start with  
> something you think can hold together, you try things out, 
> you refine,  
> you revisit design, you go forward with implementation. That's the  
> process of *detailed* engineering.
> 
> For the old timers, that was the difference between TCP/IP and OSI.
> 
> Sorry for the long email,
> Dino
> 
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area
> 
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Mon Jan 26 10:24:21 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 044C13A6A53; Mon, 26 Jan 2009 10:24:21 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1FBE53A6A53 for <rrg@core3.amsl.com>; Mon, 26 Jan 2009 10:24:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.806
X-Spam-Level: 
X-Spam-Status: No, score=-0.806 tagged_above=-999 required=5 tests=[AWL=0.396,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uKRbkRGPBjdP for <rrg@core3.amsl.com>; Mon, 26 Jan 2009 10:24:19 -0800 (PST)
Received: from imo-d21.mx.aol.com (imo-d21.mx.aol.com [205.188.144.207]) by core3.amsl.com (Postfix) with ESMTP id CAE7A3A6923 for <rrg@irtf.org>; Mon, 26 Jan 2009 10:24:17 -0800 (PST)
Received: from HeinerHummel@aol.com by imo-d21.mx.aol.com  (mail_out_v39.1.) id c.d04.4bf99f34 (32913); Mon, 26 Jan 2009 13:23:52 -0500 (EST)
From: HeinerHummel@aol.com
Message-ID: <d04.4bf99f34.36af59b8@aol.com>
Date: Mon, 26 Jan 2009 13:23:52 EST
To: dino@cisco.com
MIME-Version: 1.0
X-Mailer: 9.0 SE for Windows sub 5021
Cc: rrg@irtf.org
Subject: Re: [rrg] [lisp] Economic issues of long-path / stretched routing
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0617595829=="
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

--===============0617595829==
Content-Type: multipart/alternative; boundary="-----------------------------1232994232"


-------------------------------1232994232
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

In einer eMail vom 26.01.2009 17:24:51 Westeurop=E4ische Normalzeit schreibt=
 =20
dino@cisco.com:

>  Prior arguing with long-path, stretch etc. I have another =20
>  informative question (maybe I missed something too during the =20
>  discussion): Why LISP 1.5 ? Why not LISP 2 ? or directly:
> Why doesn't  the ITR intercept and enhance the DNS lookup as to also =20
> request  the eRLOC address in addition to the dest IP address? It can =20
>  also intercept the respective response and store (EID,  eRLOC).

OK. My concern is still how to get the geographical coordinates of the =20
egress-(DFZ-)router


1)  Because not all communication uses DNS.
OK. There will be other ways, too, as to get the geo.coordinates


2)  Because DNS queries go out one xTR and replies can come in through  =20
another xTR.
This shouldn't bother neither solution, particularly not if the mentioned =20
intercepting router is the ingress router nor in the ideal case when even th=
e =20
source host learns to handle  the returned geo.coordinates (e.g. by some  sm=
all=20
Microsoft update).
=20


3)  Because you don't want a architectural circular dependency between  =20
directory and routing.
OK. Wouldn't affect my solution.


Do  you want more reasons?
Please. I have always appreciated your answering of my  questions.
BTW, I am grateful for the default mapper mechanism, which helps me to  solv=
e=20
my incremental deployment issue.
Thank you so much.
=20
Heiner
=20
=20
=20
=20
=20



Dino




-------------------------------1232994232
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3DISO-8859-1">
<META content=3D"MSHTML 6.00.6000.16788" name=3DGENERATOR></HEAD>
<BODY id=3Drole_body style=3D"FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY:=20=
Arial"=20
bottomMargin=3D7 leftMargin=3D7 topMargin=3D7 rightMargin=3D7><FONT id=3Drol=
e_document=20
face=3DArial color=3D#000000 size=3D2>
<DIV>In einer eMail vom 26.01.2009 17:24:51 Westeurop=E4ische Normalzeit sch=
reibt=20
dino@cisco.com:</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid"><=
FONT=20
  style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000 size=
=3D2>&gt;=20
  Prior arguing with long-path, stretch etc. I have another&nbsp; <BR>&gt;=20
  informative question (maybe I missed something too during the&nbsp; <BR>&g=
t;=20
  discussion): Why LISP 1.5 ? Why not LISP 2 ? or directly:<BR>&gt; Why does=
n't=20
  the ITR intercept and enhance the DNS lookup as to also&nbsp; <BR>&gt; req=
uest=20
  the eRLOC address in addition to the dest IP address? It can&nbsp; <BR>&gt=
;=20
  also intercept the respective response and store (EID,=20
eRLOC).<BR></FONT></BLOCKQUOTE>
<DIV>OK. My concern is still how to get the geographical coordinates of the=20
egress-(DFZ-)router</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid"><=
FONT=20
  style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000 size=
=3D2><BR>1)=20
  Because not all communication uses DNS.</FONT></BLOCKQUOTE>
<DIV>OK. There will be other ways, too, as to get the geo.coordinates</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid"><=
FONT=20
  style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000 size=
=3D2><BR>2)=20
  Because DNS queries go out one xTR and replies can come in through&nbsp;=20
  <BR>another xTR.</FONT></BLOCKQUOTE>
<DIV>This shouldn't bother neither solution, particularly not if the mention=
ed=20
intercepting router is the ingress router nor in the ideal case when even th=
e=20
source host learns to handle&nbsp; the returned geo.coordinates (e.g. by som=
e=20
small Microsoft update).</DIV>
<DIV>&nbsp;</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid"><=
FONT=20
  style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000 size=
=3D2><BR>3)=20
  Because you don't want a architectural circular dependency between&nbsp;=20
  <BR>directory and routing.</FONT></BLOCKQUOTE>
<DIV>OK. Wouldn't affect my solution.</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid"><=
FONT=20
  style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000 size=
=3D2><BR>Do=20
  you want more reasons?</FONT></BLOCKQUOTE>
<DIV>Please. I have&nbsp;always appreciated your answering of my=20
questions.</DIV>
<DIV>BTW, I am grateful for the default mapper mechanism, which helps me&nbs=
p;to=20
solve my incremental deployment issue.</DIV>
<DIV>Thank you so much.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Heiner</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid"><=
FONT=20
  style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000=20
  size=3D2><BR><BR>Dino<BR></FONT></BLOCKQUOTE>
<DIV></DIV>
<DIV>&nbsp;</DIV></FONT></BODY></HTML>

-------------------------------1232994232--

--===============0617595829==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

--===============0617595829==--

From rrg-bounces@irtf.org  Mon Jan 26 10:35:41 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1239F28C265; Mon, 26 Jan 2009 10:35:41 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 905C528C265 for <rrg@core3.amsl.com>; Mon, 26 Jan 2009 10:35:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.495
X-Spam-Level: 
X-Spam-Status: No, score=-6.495 tagged_above=-999 required=5 tests=[AWL=0.104,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6VUi7MU5S1SZ for <rrg@core3.amsl.com>; Mon, 26 Jan 2009 10:35:39 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by core3.amsl.com (Postfix) with ESMTP id A203A28C25D for <rrg@irtf.org>; Mon, 26 Jan 2009 10:35:39 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 433406BE571; Mon, 26 Jan 2009 13:35:19 -0500 (EST)
To: rrg@irtf.org
Message-Id: <20090126183519.433406BE571@mercury.lcs.mit.edu>
Date: Mon, 26 Jan 2009 13:35:19 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [rrg] Please respond: Questions from the IESG as to whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

    > From: David Conrad <drc@virtualized.org>

    >> The question to ask is whether LISP is an appropriate solution to
    >> the problems discussed at the IAB's October, 2006 Routing and
    >> Addressing Workshop.
    >> ...
    >> Yet the LISP proponents still did not adequately address these concerns.

    > Perhaps the reasons LISP proponents haven't adequately addressed those
    > concerns is because they are not addressable with the underlying LISP
    > assumptions?

When thinking about the routing, it's also important to remember that LISP,
in the sense of 'a map-encaps scheme plus a mapping subsystem plus ancillary
glue' is likely (almost certainly?) just a component, almost more of a piece
of necessary substrate (to give us a way out of the current paint corner),
than a full-blown new routing approach. (I've referred before to how LISP
reminded me of simply the deployment plan for a new routing architecture I
worked on.)

Yes, LISP may do some routing-like things (e.g. support multi-homing, and
provide a certain amount of provider independence), but there's a limit to
what you can do with simply separating location and identity. At the end of
the day, we're still working with BGP, and if you want to do more with
_routing_ than BGP allows (e.g. control the paths for traffic aggregates),
then you need something _else_ new.

And deploying that new thing would almost certainly start with.... deploying
something that looks a lot like LISP. Add that to the fact that LISP gives
you a decent bang/buck _in and of itself_ (multi-homing, etc), and you soon
decide to focus on getting LISP done (right, with hooks for the future), and
worry about the rest later...

	Noel
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Mon Jan 26 11:03:29 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E65013A68B8; Mon, 26 Jan 2009 11:03:29 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 09A2E3A69DD for <rrg@core3.amsl.com>; Mon, 26 Jan 2009 11:03:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.5
X-Spam-Level: 
X-Spam-Status: No, score=-6.5 tagged_above=-999 required=5 tests=[AWL=0.099, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VuP8tvfHfTs6 for <rrg@core3.amsl.com>; Mon, 26 Jan 2009 11:03:27 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by core3.amsl.com (Postfix) with ESMTP id 4DA8D3A68B8 for <rrg@irtf.org>; Mon, 26 Jan 2009 11:03:27 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 275276BE571; Mon, 26 Jan 2009 14:03:07 -0500 (EST)
To: rrg@irtf.org
Message-Id: <20090126190307.275276BE571@mercury.lcs.mit.edu>
Date: Mon, 26 Jan 2009 14:03:07 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: Re: [rrg] [lisp] Economic issues of long-path / stretched routing
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

    > From: HeinerHummel@aol.com

    > Why LISP 1.5=20?  Why not LISP 2 ? or directly:
    > Why doesn't the ITR intercept and enhance the DNS lookup as to also request
    > the eRLOC address in addition to the dest IP address? It can also
    > intercept the respective response and store (EID, eRLOC).

I don't know what the thinking of other people working on LISP is, but I can
give you my thoughts on this point.

Simply put, I don't like designs which _invisibly, outside the host_ tie into
the DNS because it takes two separate subsystems (DNS resolution, and basic
packet forwarding), and tangles them together, which is bad engineering for a
number of reasons (makes it harder to make further changes, creates more
mutual dependencies, increases overall fragility/brittleness, etc).

Some NAT variants do this too, and I especially didn't like them either! :-)

        Noel
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Mon Jan 26 14:34:42 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 30D7B28C14D; Mon, 26 Jan 2009 14:34:42 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6526628C14D for <rrg@core3.amsl.com>; Mon, 26 Jan 2009 14:34:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.517
X-Spam-Level: 
X-Spam-Status: No, score=-6.517 tagged_above=-999 required=5 tests=[AWL=0.082,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BmVt7+7I14gn for <rrg@core3.amsl.com>; Mon, 26 Jan 2009 14:34:41 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 0B8213A67FB for <rrg@irtf.org>; Mon, 26 Jan 2009 14:34:41 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,327,1231113600"; d="scan'208";a="125845465"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-2.cisco.com with ESMTP; 26 Jan 2009 22:33:23 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n0QMXNpa015012;  Mon, 26 Jan 2009 14:33:23 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n0QMXNvK028836; Mon, 26 Jan 2009 22:33:23 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Mon, 26 Jan 2009 14:33:23 -0800
Received: from [70.151.3.229] ([10.21.88.125]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Mon, 26 Jan 2009 14:33:22 -0800
Message-Id: <C5685527-8D7E-41E7-AC48-DE4C868E0241@cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A1057A286E@XCH-NW-7V2.nw.nos.boeing.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Mon, 26 Jan 2009 12:12:29 -0800
References: <20090120190744.GA9467@1-4-5.net><49765FFB.1010709@piuha.net>	<200901222339.n0MNddM88868@magenta.juniper.net><75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com><497B1F7A.9030407@firstpr.com.au> <6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com> <39C363776A4E8C4A94691D2BD9D1C9A1057A286E@XCH-NW-7V2.nw.nos.boeing.com>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 26 Jan 2009 22:33:22.0773 (UTC) FILETIME=[189AD850:01C98006]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3961; t=1233009203; x=1233873203; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dino@cisco.com; z=From:=20Dino=20Farinacci=20<dino@cisco.com> |Subject:=20Re=3A=20[Int-area]=20[rrg]=20Please=20respond=3 A=20Questions=20from=20the=20IESG=20as=20towhether=20a=20WG= 20forming=20BOF=20is=20necessary=20for=20LISP |Sender:=20; bh=KeKXl1dmmwsr2GHwWnjFctw6IJ8mIDd52A1mzCbshAs=; b=RTxmhBD72ZxZi5jzOhYs1jHbDbGnqptza1YVy0tVOnNZsYbvGr0D0me9vt CeAWNWM32JBybyudfPmIe2pFmlD/o7CNrs3NrgZ86Y4CCoXdAXvi1XL4pKG8 BOPRKFN94N;
Authentication-Results: sj-dkim-2; header.From=dino@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); 
Cc: rrg RG <rrg@irtf.org>, int-area@ietf.org, Robin Whittle <rw@firstpr.com.au>, routing-discussion@ietf.org, lisp@ietf.org
Subject: Re: [rrg] [Int-area] Please respond: Questions from the IESG as towhether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

> In the "stateless" case, having the LISP ITR return
> packet-too-bigs with degenerate MTUs (i.e., MTUs less
> than 1500) is going to leave source hosts with an
> unsatisfactory experience that they would not incur
> without an ITR/ETR in the middle.

Ah, then that motivates to upgrade MTUs.

> In the stateful case, LISP relies on a brittle mechanism
> that has known vulnerabilities (e.g., [RFC2923]) and can
> easily be spoofed by off-path attackers.

Are you saying MTU Discovery is flawed?

> RANGER/SEAL fixes both of these problems and much more.

With a lot more machinery and state. Let's not start this conversation  
again.

> Fine qualifications noted (I think). About the LISP
> locator reachability bits, that seems like a lot of
> overhead to carry on each and every packet, and it

4 bytes per packet? Sorry, I don't think so.

> also seems to assume symmetric paths. RANGER assumes
> unidirectional tunnels and path asymmetry, i.e., if
> Site 1's packets use ITR A and go through ETR B at
> Site 2, the return traffic could actually come through
> Site 2's ITR C. In the LISP locator reachability case,
> how does C know anything about the reachability of A?

It can send a Map-Request. But active-active on ingress and egress  
will be the norm.

> Although RANGER could send locator reachability bits
> in control messages as an optimization, its primary
> mechanism is through having the ITR probe the forward
> path to the ITR. Probing is by setting an "ack request"
> bit on every Nth data packet (+/- some delta if
> randomization is desired) and then observing whether
> a steady stream of ACKs comes back.

This doesn't work because if you are going to claim liveness through a  
protocol, you have to send control packets all the time from M ITRs to  
N ETRs. If you claim liveness, you have to do this before you send  
packets. So putting the probe in data packets is not sufficient.

And if you send probes all the time from M ITRs to N ETRs, you have a  
huge scaling problem.

> LISP also doesn't seem to take into account that a multi-
> homed site can partition, such that locator reachability
> does not necessarily imply end system reachability via
> specific locators. Nor does it provide a means for an ETR
> (A) to inform the ITR of a better ETR (B) when paths get
> stretched. RANGER has a means to accommodate this.

Can you state some disadvantages of RANGER? There is no such thing as  
a free lunch, so your design has to make tradeoffs, but you seem to  
never state them.

>> If we want to solve this problem, we could do this today by having a
>> host switch it's TCP connection to another A record. This doesn't
>> happen today because people deal with packet loss, since it doesn't
>> last long *and* rerouting actually works quite well.
>>
>> Van Jacobson always made this comment and I'll never forget it, "The
>> fact that the Internet drops packets is it's greatest feature".
>>
>> What else can either an xTR or TCP host do when sending ICMP
>> Unreachables are off by default in most modern routers, or they are
>> filtered by firewalls, and route aggregation hides failures close to
>> packet sources.
>
> RANGER can listen for ICMP unreachables coming from network
> middleboxes that it can verify as on-path by checking the

Non-starter, you will not get ICMP unreachables, period. So if you  
solely depend on it, the solution is a non-starter.

> SEAL_ID. In a RANGER world, network middleboxes would be
> encouraged to turn the ICMPs back on because site border
> xTRs will have a means to detect spoofing (i.e., the SEAL_ID).
> But, this is an optimization only; nothing in RANGER depends
> on getting the ICMPs from middleboxes.

You have to turn it on in all transit routers. You will get objection  
to this. It will never happen and if you think it could possibly  
happen, it will take forever.

Dino

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Mon Jan 26 14:50:55 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 388DF3A69D3; Mon, 26 Jan 2009 14:50:55 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4CC4E3A69D3 for <rrg@core3.amsl.com>; Mon, 26 Jan 2009 14:50:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.505
X-Spam-Level: 
X-Spam-Status: No, score=-6.505 tagged_above=-999 required=5 tests=[AWL=0.094,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 64YqXK7i-mZA for <rrg@core3.amsl.com>; Mon, 26 Jan 2009 14:50:52 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by core3.amsl.com (Postfix) with ESMTP id 99DE53A68DC for <rrg@irtf.org>; Mon, 26 Jan 2009 14:50:52 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id C65A557EAFD; Mon, 26 Jan 2009 17:50:34 -0500 (EST)
To: rrg@irtf.org
Message-Id: <20090126225034.C65A557EAFD@mercury.lcs.mit.edu>
Date: Mon, 26 Jan 2009 17:50:34 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: Re: [rrg] [lisp] [Int-area] Please respond: Questions from the IESG as towhether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

    > From: Dino Farinacci <dino@cisco.com>

    > if you are going to claim liveness through a protocol, you have to send
    > control packets all the time from M ITRs to N ETRs.

I find this terminology somewhat non-intuitive, and wonder if it's too late
to change it. To me, "liveness" would imply as to whether something is live
or dead, i.e. up or down. (Such state detection can obviously be performed on
ITR I1's behalf by I2, and the result communicated locally from I2 to I1.)

The issue of whether packets from ITR Im can reach ETR En (which is where you
run into the need for M*N) I would describe as "reachability". (So if there's
a routing problem, or an access control setting, that prevents I1 from
getting to E7 even through I1 can get to E8 and I2 can get to E7, that would
be a reachability problem on the {I1, E7} pairing.) I seem to recall this
term being used in at least one routing protocol, although I can't now recall
which one.

        Noel
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Mon Jan 26 15:07:01 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B4DEB3A6953; Mon, 26 Jan 2009 15:07:01 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E4E3E3A6A4E for <rrg@core3.amsl.com>; Mon, 26 Jan 2009 15:06:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.832
X-Spam-Level: 
X-Spam-Status: No, score=-0.832 tagged_above=-999 required=5 tests=[AWL=0.370,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dipfSqsL-PNx for <rrg@core3.amsl.com>; Mon, 26 Jan 2009 15:06:58 -0800 (PST)
Received: from imo-d22.mx.aol.com (imo-d22.mx.aol.com [205.188.144.208]) by core3.amsl.com (Postfix) with ESMTP id A36513A6953 for <rrg@irtf.org>; Mon, 26 Jan 2009 15:06:57 -0800 (PST)
Received: from HeinerHummel@aol.com by imo-d22.mx.aol.com  (mail_out_v39.1.) id 9.d52.3ee34554 (14501); Mon, 26 Jan 2009 18:06:31 -0500 (EST)
From: HeinerHummel@aol.com
Message-ID: <d52.3ee34554.36af9bf7@aol.com>
Date: Mon, 26 Jan 2009 18:06:31 EST
To: jnc@mercury.lcs.mit.edu, rrg@irtf.org
MIME-Version: 1.0
X-Mailer: 9.0 SE for Windows sub 5021
Subject: Re: [rrg] Please respond: Questions from the IESG as to whether a WG forming ...
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0694998410=="
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

--===============0694998410==
Content-Type: multipart/alternative; boundary="-----------------------------1233011191"


-------------------------------1233011191
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

In einer eMail vom 26.01.2009 19:35:37 Westeurop=E4ische Normalzeit schreibt=
 =20
jnc@mercury.lcs.mit.edu:

> From: David Conrad <drc@virtualized.org>

>> The question to ask is whether LISP is an appropriate solution  to
>> the problems discussed at the IAB's October, 2006  Routing and
>> Addressing Workshop.
>> ...
>> Yet the LISP proponents still did not  adequately address these concerns.

> Perhaps the  reasons LISP proponents haven't adequately addressed those
> concerns is because they are not addressable with the underlying  LISP
> assumptions?

When thinking about the  routing, it's also important to remember that LISP,
in the sense of 'a  map-encaps scheme plus a mapping subsystem plus ancillar=
y
glue' is likely  (almost certainly?) just a component, almost more of a piec=
e
of necessary  substrate (to give us a way out of the current paint corner),
than a  full-blown new routing approach. (I've referred before to how LISP
reminded  me of simply the deployment plan for a new routing architecture I
worked  on.)

Yes, LISP may do some routing-like things (e.g. support  multi-homing, and
provide a certain amount of provider independence), but  there's a limit to
what you can do with simply separating location and  identity.=20
Right.
=20

At the  end of
the day, we're still working with BGP, and if you want to do more  with
_routing_ than BGP allows (e.g. control the paths for traffic  aggregates),
then you need something _else_ new.
Formerly I also thought, overcoming the DV algorithm required to replace =20
BGP. But meanwhile I see it differently: The fact that BGP is all present is=
 a =20
big help and not a big obstacle. Routing without disseminating any user  r
eachability prefixes is certainly something_else_new. But it can be  enabled=
 by=20
enhancing BGP !

And  deploying that new thing would almost certainly start with....  deployi=
ng
something that looks a lot like LISP. Add that to the fact that  LISP gives
you a decent bang/buck _in and of itself_ (multi-homing, etc),  and you soon
decide to focus on getting LISP done (right, with hooks for  the future), an=
d
worry about the rest later...
LISP will never get IP forwarding on the Moore's law applicability  track.=20
That's for sure :-(
=20
Heiner
=20



Noel
_______________________________________________
rrg mailing  list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg




-------------------------------1233011191
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3DISO-8859-1">
<META content=3D"MSHTML 6.00.6000.16788" name=3DGENERATOR></HEAD>
<BODY id=3Drole_body style=3D"FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY:=20=
Arial"=20
bottomMargin=3D7 leftMargin=3D7 topMargin=3D7 rightMargin=3D7><FONT id=3Drol=
e_document=20
face=3DArial color=3D#000000 size=3D2>
<DIV>In einer eMail vom 26.01.2009 19:35:37 Westeurop=E4ische Normalzeit sch=
reibt=20
jnc@mercury.lcs.mit.edu:</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid"><=
FONT=20
  style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000 size=
=3D2>&nbsp;=20
  &gt; From: David Conrad &lt;drc@virtualized.org&gt;<BR><BR>&nbsp; &nbsp;=20
  &gt;&gt; The question to ask is whether LISP is an appropriate solution=20
  to<BR>&nbsp; &nbsp; &gt;&gt; the problems discussed at the IAB's October,=20=
2006=20
  Routing and<BR>&nbsp; &nbsp; &gt;&gt; Addressing Workshop.<BR>&nbsp; &nbsp=
;=20
  &gt;&gt; ...<BR>&nbsp; &nbsp; &gt;&gt; Yet the LISP proponents still did n=
ot=20
  adequately address these concerns.<BR><BR>&nbsp; &nbsp; &gt; Perhaps the=20
  reasons LISP proponents haven't adequately addressed those<BR>&nbsp; &nbsp=
;=20
  &gt; concerns is because they are not addressable with the underlying=20
  LISP<BR>&nbsp; &nbsp; &gt; assumptions?<BR><BR>When thinking about the=20
  routing, it's also important to remember that LISP,<BR>in the sense of 'a=20
  map-encaps scheme plus a mapping subsystem plus ancillary<BR>glue' is like=
ly=20
  (almost certainly?) just a component, almost more of a piece<BR>of necessa=
ry=20
  substrate (to give us a way out of the current paint corner),<BR>than a=20
  full-blown new routing approach. (I've referred before to how LISP<BR>remi=
nded=20
  me of simply the deployment plan for a new routing architecture I<BR>worke=
d=20
  on.)<BR><BR>Yes, LISP may do some routing-like things (e.g. support=20
  multi-homing, and<BR>provide a certain amount of provider independence), b=
ut=20
  there's a limit to<BR>what you can do with simply separating location and=20
  identity. </FONT></BLOCKQUOTE>
<DIV>Right.</DIV>
<DIV>&nbsp;</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid"><=
FONT=20
  style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000 size=
=3D2>At the=20
  end of<BR>the day, we're still working with BGP, and if you want to do mor=
e=20
  with<BR>_routing_ than BGP allows (e.g. control the paths for traffic=20
  aggregates),<BR>then you need something _else_ new.</FONT></BLOCKQUOTE>
<DIV>Formerly I also thought, overcoming the DV algorithm required to replac=
e=20
BGP. But meanwhile I see it differently: The fact that BGP is all present is=
 a=20
big help and not a big obstacle.&nbsp;Routing without disseminating any user=
=20
reachability prefixes&nbsp;is certainly something_else_new. But it can be=20
enabled by enhancing BGP !</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid"><=
FONT=20
  style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000 size=
=3D2>And=20
  deploying that new thing would almost certainly start with....=20
  deploying<BR>something that looks a lot like LISP. Add that to the fact th=
at=20
  LISP gives<BR>you a decent bang/buck _in and of itself_ (multi-homing, etc=
),=20
  and you soon<BR>decide to focus on getting LISP done (right, with hooks fo=
r=20
  the future), and<BR>worry about the rest later...</FONT></BLOCKQUOTE>
<DIV>LISP will never get IP forwarding on the Moore's law applicability=20
track.&nbsp;That's for sure&nbsp;:-(</DIV>
<DIV>&nbsp;</DIV>
<DIV>Heiner</DIV>
<DIV>&nbsp;</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid"><=
FONT=20
  style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000=20
  size=3D2><BR><BR>&nbsp; &nbsp;=20
  Noel<BR>_______________________________________________<BR>rrg mailing=20
  list<BR>rrg@irtf.org<BR>http://www.irtf.org/mailman/listinfo/rrg<BR></FONT=
></BLOCKQUOTE>
<DIV></DIV>
<DIV>&nbsp;</DIV></FONT></BODY></HTML>

-------------------------------1233011191--

--===============0694998410==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

--===============0694998410==--

From rrg-bounces@irtf.org  Mon Jan 26 20:17:42 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9748C28C0DC; Mon, 26 Jan 2009 20:17:42 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5E8363A69C6; Mon, 26 Jan 2009 20:17:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.444
X-Spam-Level: 
X-Spam-Status: No, score=-6.444 tagged_above=-999 required=5 tests=[AWL=0.155,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QIu-ZtWk-6yt; Mon, 26 Jan 2009 20:17:40 -0800 (PST)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by core3.amsl.com (Postfix) with ESMTP id 3A9B33A6A41; Mon, 26 Jan 2009 20:17:40 -0800 (PST)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231]) by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n0R4Gu4q000407 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 26 Jan 2009 22:16:57 -0600 (CST)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n0R4Gufk009018; Mon, 26 Jan 2009 20:16:56 -0800 (PST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n0R4GuCS009015; Mon, 26 Jan 2009 20:16:56 -0800 (PST)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 26 Jan 2009 20:16:56 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 26 Jan 2009 20:16:55 -0800
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1057A2D8F@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <C5685527-8D7E-41E7-AC48-DE4C868E0241@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Int-area] [rrg] Please respond: Questions from the IESG as towhether a WG forming BOF is necessary for LISP
Thread-Index: AcmABhtY/zfU682ET2is/tkpY/4QjAAJRMkg
References: <20090120190744.GA9467@1-4-5.net><49765FFB.1010709@piuha.net>	<200901222339.n0MNddM88868@magenta.juniper.net><75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com><497B1F7A.9030407@firstpr.com.au> <6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com> <39C363776A4E8C4A94691D2BD9D1C9A1057A286E@XCH-NW-7V2.nw.nos.boeing.com> <C5685527-8D7E-41E7-AC48-DE4C868E0241@cisco.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Dino Farinacci" <dino@cisco.com>
X-OriginalArrivalTime: 27 Jan 2009 04:16:56.0407 (UTC) FILETIME=[1749C670:01C98036]
Cc: rrg RG <rrg@irtf.org>, int-area@ietf.org, Robin Whittle <rw@firstpr.com.au>, routing-discussion@ietf.org, lisp@ietf.org
Subject: Re: [rrg] [Int-area] Please respond: Questions from the IESG as towhether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Hi Dino, 

> -----Original Message-----
> From: Dino Farinacci [mailto:dino@cisco.com] 
> Sent: Monday, January 26, 2009 12:12 PM
> To: Templin, Fred L
> Cc: Robin Whittle; rrg RG; int-area@ietf.org; lisp@ietf.org; 
> routing-discussion@ietf.org
> Subject: Re: [Int-area] [rrg] Please respond: Questions from 
> the IESG as towhether a WG forming BOF is necessary for LISP
> 
> > In the "stateless" case, having the LISP ITR return
> > packet-too-bigs with degenerate MTUs (i.e., MTUs less
> > than 1500) is going to leave source hosts with an
> > unsatisfactory experience that they would not incur
> > without an ITR/ETR in the middle.
> 
> Ah, then that motivates to upgrade MTUs.

Upgrading to large MTUs everywhere is the desired
end-state goal. But, if you are talking about the LISP
"stateless" case, you would have no way of knowing when
all links everywhere have been updated such that you
can safely set the static value to something larger
than 1500.

> > In the stateful case, LISP relies on a brittle mechanism
> > that has known vulnerabilities (e.g., [RFC2923]) and can
> > easily be spoofed by off-path attackers.
> 
> Are you saying MTU Discovery is flawed?

You as much as said it yourself below...

> > RANGER/SEAL fixes both of these problems and much more.
> 
> With a lot more machinery and state. Let's not start this 
> conversation  
> again.

I'm not sure we finished the conversation last time,
and I know it wasn't conducted on the wider list
distributions that we are posting to here.

> > Fine qualifications noted (I think). About the LISP
> > locator reachability bits, that seems like a lot of
> > overhead to carry on each and every packet, and it
> 
> 4 bytes per packet? Sorry, I don't think so.

I was counting the UDP header as overhead, too.

> > also seems to assume symmetric paths. RANGER assumes
> > unidirectional tunnels and path asymmetry, i.e., if
> > Site 1's packets use ITR A and go through ETR B at
> > Site 2, the return traffic could actually come through
> > Site 2's ITR C. In the LISP locator reachability case,
> > how does C know anything about the reachability of A?
> 
> It can send a Map-Request. But active-active on ingress and egress  
> will be the norm.
> 
> > Although RANGER could send locator reachability bits
> > in control messages as an optimization, its primary
> > mechanism is through having the ITR probe the forward
> > path to the ITR. Probing is by setting an "ack request"
> > bit on every Nth data packet (+/- some delta if
> > randomization is desired) and then observing whether
> > a steady stream of ACKs comes back.
> 
> This doesn't work because if you are going to claim liveness 
> through a  
> protocol, you have to send control packets all the time from 
> M ITRs to  
> N ETRs. If you claim liveness, you have to do this before you send  
> packets. So putting the probe in data packets is not sufficient.

The RANGER model sends initial packets through a default
mapper, which returns an ICMP redirect; that is not really
a "protocol", but rather an alternate means of establishing
a FIB entry in the ITR.

Once the FIB entry is established, ITR->ETR liveness
testing is piggybacked on top of ordinary data packets.
That is 1x1; not MxN.

> And if you send probes all the time from M ITRs to N ETRs, 
> you have a  
> huge scaling problem.

RANGER piggybacks liveness testing on top of every Nth
(+/- delta) ordinary data packet that flows from one ITR
to one ETR. While packets are flowing, probing continues;
when no packets are flowing, probing ceases.

> > LISP also doesn't seem to take into account that a multi-
> > homed site can partition, such that locator reachability
> > does not necessarily imply end system reachability via
> > specific locators. Nor does it provide a means for an ETR
> > (A) to inform the ITR of a better ETR (B) when paths get
> > stretched. RANGER has a means to accommodate this.
> 
> Can you state some disadvantages of RANGER? There is no such 
> thing as  
> a free lunch, so your design has to make tradeoffs, but you seem to  
> never state them.

Forgive me, and I will try to take a more balanced
consideration from now on.

For one thing, RANGER requires a means for
synchronization of a very large distributed mapping
database between a limited number of nodes; that is
probably also the case for other map/encaps systems
too. This may be tenable if the number of nodes
participating in the protocol and the frequency
of updates is kept relatively small, but I have no
quantitative basis for the claim.

> >> If we want to solve this problem, we could do this today 
> by having a
> >> host switch it's TCP connection to another A record. This doesn't
> >> happen today because people deal with packet loss, since it doesn't
> >> last long *and* rerouting actually works quite well.
> >>
> >> Van Jacobson always made this comment and I'll never 
> forget it, "The
> >> fact that the Internet drops packets is it's greatest feature".
> >>
> >> What else can either an xTR or TCP host do when sending ICMP
> >> Unreachables are off by default in most modern routers, or they are
> >> filtered by firewalls, and route aggregation hides 
> failures close to
> >> packet sources.
> >
> > RANGER can listen for ICMP unreachables coming from network
> > middleboxes that it can verify as on-path by checking the
> 
> Non-starter, you will not get ICMP unreachables, period. So if you  
> solely depend on it, the solution is a non-starter.

...there - you said it yourself!

> > SEAL_ID. In a RANGER world, network middleboxes would be
> > encouraged to turn the ICMPs back on because site border
> > xTRs will have a means to detect spoofing (i.e., the SEAL_ID).
> > But, this is an optimization only; nothing in RANGER depends
> > on getting the ICMPs from middleboxes.
> 
> You have to turn it on in all transit routers. You will get 
> objection  
> to this. It will never happen and if you think it could possibly  
> happen, it will take forever.

Well, I did say "optimization only"; the ICMPs would be
nice to have, but RANGER can live without them.

Thanks - Fred
fred.l.templin@boeing.com

> 
> Dino
> 
> 
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Mon Jan 26 21:27:36 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4C7F83A69FB; Mon, 26 Jan 2009 21:27:36 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2F0BA3A69FB for <rrg@core3.amsl.com>; Mon, 26 Jan 2009 21:27:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.57
X-Spam-Level: 
X-Spam-Status: No, score=-1.57 tagged_above=-999 required=5 tests=[AWL=0.325,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KVkgqMVWcp5q for <rrg@core3.amsl.com>; Mon, 26 Jan 2009 21:27:32 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123]) by core3.amsl.com (Postfix) with ESMTP id 720F73A689B for <rrg@irtf.org>; Mon, 26 Jan 2009 21:27:32 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6]) by gair.firstpr.com.au (Postfix) with ESMTP id AD0CF175DB0; Tue, 27 Jan 2009 16:27:12 +1100 (EST)
Message-ID: <497E9BB2.5040101@firstpr.com.au>
Date: Tue, 27 Jan 2009 16:29:22 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: RRG <rrg@irtf.org>
Cc: lisp-interest@lists.civil-tongue.net
Subject: [rrg] LISP PMTU - 2 methods in draft-farinacci-lisp-11
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Short version:  Stateless approach is a really bad idea in the future
                when ~9000 byte MTU ITR to ETR paths become common.

                Stateful approach somewhat resembles Ivip's approach
                - which is documented in greater detail and limits
                the number of traffic packets for which state must
                be stored in case a PTB is received.

Here my thoughts on the two techniques (Stateless and Stateful) for
LISP Path MTU Discovery management in the latest (19 December) draft.

My understanding of the whole problem (for Ivip's map-encap modes or
for any other map-encap scheme, such as LISP or APT), together with
my solution for Ivip, is here:

  http://www.firstpr.com.au/ip/ivip/pmtud-frag/


Here is my critique of the Stateless approach, assuming L = 1500, as
is recommended at the end of:

  http://tools.ietf.org/html/draft-farinacci-lisp-11#section-5.4.1

The stateless approach was rejected by the OpenLISP team:

http://tools.ietf.org/html/draft-iannone-openlisp-implementation-01#section-6.8.1


Stateless IPv4 DF=0
-------------------

  L is chosen for the entire global LISP system to be a minimum
  value of MTU which can be expected of any ITR->ETR tunnel.  Here
  I assume 1500 bytes, as is recommended in the last line of section
  5.4.1.  Perhaps it would need to be less, such as 1470 or less.
  Google servers regularly send 1470 byte DF=0 packets:

http://www.firstpr.com.au/ip/ivip/ipv4-bits/actual-packets.html#google-no-pmtud


  IPv4 DF=0 packets longer than some size S will be fragmented
  into two fragments, each of which will be encapsulated.  The
  ETR decapsulates them separately and sends the two fragments
  to the destination network.

  S is set globally to a value is L minus the encapsulation
  overhead = 36 bytes.  (IPv4, UDP and LISP headers, in section
  5.1).  So S = 1464 bytes.

  This will not work when the packet length is more than about
  twice S (since fragmentation produces two packets whose
  combined length is marginally longer than the original packet).

  The statement:

    "This will ensure that the new, encapsulated packets are of
     size (S/2 + H), which is always below the effective tunnel MTU."

  will not apply when the incoming packets are more than about
  twice S in length.

  Still, with a bit of tightening of the spec, I see no major
  problems with this approach to IPv4 fragmentable packets compared
  to what I propose for Ivip.  I don't think a core-edge separation
  scheme should be required to support DF=0 packets longer than
  something like 1470 bytes into the indefinite future.

  RFC 1191 PMTUD has been around since the early 1990s and I think
  it is time that hosts stopped expecting the network to fragment
  packets.  The IPv6 designers evidently thought the same in 1996.



Stateless IPv4 DF=1 and IPv6
----------------------------

  This approach makes no sense for the long-term future since it
  forces all traffic to be in packets no longer than 1464 (IPv4)
  bytes:

      the ITR will drop the packet when the size is greater than L,
      and sends an ICMP Too Big message to the source with a value of
      S, where S is (L - H).

  Replacing the variables with constants for IPv4, this means:

      the ITR will drop the packet when the size is greater than 1500
      bytes, and sends an ICMP Too Big message to the source with a
      value of 1464 bytes.

  For IPv6, the limiting size is set by the 56 byte overhead, to 1444
  bytes.

  A proper solution should keep working well when the DFZ includes
  MTUs of 9000 bytes between ITR and ETR - and should allow the
  sending host to generate packets of nearly this size, so that once
  encapsulated they still fit within whatever the MTU is for the
  path to this ETR.

  Fred Templin raised similar concerns:

  http://www.irtf.org/pipermail/rrg/2009-January/000884.html

  (My guess is that the non-DF=0 part of this approach was written
  with an assumption that L would be individually determined by the
  ITR for each ETR - but that is not the way the I-D is written: L is
  fixed at 1500 bytes, and any such method would be stateful.)


Stateful approach for all packets
---------------------------------

I am reading the LISP version - I have not looked in detail at the
OpenLISP source of this approach.

This makes no reference to IPv4 DF=0 packets.  So this approach of
the ITR sending a PTB packet to the sending host when a DF=0 packet
exceeds some length is not going to result in any action on the part
of the sending host.  Such a DF=0 packet will be dropped by the ITR.
 That may be OK - Ivip will do much the same - but it needs to be
specified clearly.

This approach of determining the MTU to each ITR by receiving ICMP
messages from an intermediate router needs to be done securely.

It requires the ITR to cache significant amounts of information for
every packet it sends which might trigger such a PTB.

The intermediate router would need to send back sufficient of the
original packet to ITR to include the LISP nonce.  Otherwise, PTBs
spoofed by off-path attackers would be accepted and the whole system
could easily be DoSed.

The ITR needs to store an initial fragment of each incoming traffic
packet for some time, so it can generate a PTB message for the
sending host.  It can't rely on enough of the original packet coming
back in the PTB from the intermediate router.  The ITR needs to cache
this for a second or two at least - while it waits for a possible
PTB.  This is an onerous requirement in a high-volume ITR.

Ivip map-encap ITRs need to perform a stateful PMTU determination
process which is somewhat similar to this.  However, the Ivip
approach quickly narrows the zone of uncertainty so that the number
of packets involved in testing PMTU is very limited.

The Ivip approach is specified in greater detail, including
occasionally sending longer packets (if and when the current or some
other sending host generates them) to see if the MTU has grown
since the last PTB set a limit on it, as far as the ITR was concerned.

 - Robin







_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Mon Jan 26 23:41:46 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9716B28C0D6; Mon, 26 Jan 2009 23:41:46 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EC80528C0D6 for <rrg@core3.amsl.com>; Mon, 26 Jan 2009 23:41:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.423
X-Spam-Level: 
X-Spam-Status: No, score=0.423 tagged_above=-999 required=5 tests=[AWL=-1.626,  BAYES_00=-2.599, FB_INCREASE_VOL=3.629, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GZxbTmnBga3B for <rrg@core3.amsl.com>; Mon, 26 Jan 2009 23:41:42 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123]) by core3.amsl.com (Postfix) with ESMTP id E3EFF3A68C6 for <rrg@irtf.org>; Mon, 26 Jan 2009 23:41:40 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6]) by gair.firstpr.com.au (Postfix) with ESMTP id C6E13175723; Tue, 27 Jan 2009 18:15:26 +1100 (EST)
Message-ID: <497EB510.8060100@firstpr.com.au>
Date: Tue, 27 Jan 2009 18:17:36 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: RRG <rrg@irtf.org>
References: <20090120190744.GA9467@1-4-5.net>	<49765FFB.1010709@piuha.net>	<200901222339.n0MNddM88868@magenta.juniper.net>	<75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com>	<497B1F7A.9030407@firstpr.com.au> <6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com>
In-Reply-To: <6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com>
Cc: routing-discussion@ietf.org, int-area@ietf.org, lisp@ietf.org
Subject: Re: [rrg] [Int-area] Please respond: Questions from the IESG as to whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Short version:   Responding to Dino's reply to my critiques of LISP.

                 The LISP team should do detailed critiques of APT
                 and Ivip as part of convincing IETF folks of the
                 merits of LISP-ALT.

                 Will it be possible to do firmware upgrades so all
                 DFZ routers ca. 2014 will handle packets with
                 modified IPv4 and IPv6 headers, to forward the
                 packets the ISP network of the ETR, without
                 encapsulation, its overheads and PMTUD problems?

                 If so, then maybe we could go straight to this
                 approach and forget about encapsulation and all
                 its complexities.


Hi Dino,

Thanks for your reply:

> Sorry for the long email,

We are attempting to re-engineer one of humanity's most excellent and
important communication networks.  Long detailed messages are often
appropriate.


>>   LISP has too many fundamental problems to be considered a
>>   potentially practical solution.  Some of these problems require
>
> LISP is not perfect and still evolving but let me point out that
> every design has fundamental problems. At this scale, it's very
> hard to be perfect Robin. And as Noel has stated so many times, the
> hard decisions must be made to incrementally deploy this. So things
> might not look pretty on the surface, but jeez, you got to do what
> you got to do. Else, this will all be academic.

I wasn't suggesting a proposal should be perfect.  I pointed out
problems which I consider to be fundamental - not "on the surface".
Some can be fixed by adding new design elements, but I think the
others are only fixable by radically altering the current design.

I stand corrected about LISP's approach to PMTUD - the latest draft
does include an outline of a workable solution.


> We really want to solve this problem, sincerely. This is not lip
> service, we are not just writing papers, we want to rev the
> Internet, this is serious.

I have always known you and the other LISP folks really care for the
Net and are working hard to devise the best possible improvements.

Despite it only having had broad-based commercial, political and
inter-personal impact in the last 15 years, the Internet is a
momentous development in human relations.  We all want to see changes
which will enable it to remain technically viable - and hopefully
elegant - for the long-term future.

However, I think you jumped straight into some seemingly attractive
approaches which turn out to have problems I consider to be serious.

It seems that you and the APT folks thought for a few moments about a
real-time mapping system and figured it was out of the question.  I
think it is not at all out of the question - and when you have
real-time mapping distribution, you can do some elegant and valuable
things:

1 - Separate out reachability testing and ETR choice mechanisms and
    let (actually require) the end-user networks to do it themselves
    - or pay someone else to do it for them.

2 - Enable the end-user networks to do real-time incoming TE control.

3 - Send the mapping update stream to local query servers, so there
    is reliable and very fast responses to mapping requests - and
    therefore no need to delay or drop initial packets.

4 - Charge a small fee per update to pay for most of the mapping
    distribution system.

5 - Provide much better support for the TTR approach to mobility:

      http://www.firstpr.com.au/ip/ivip/TTR-Mobility.pdf

I think the ALT system is a lot niftier than CONS, but still, you are
delaying initial packets (APT and Ivip are not), forcing every ITR to
do its own reachability testing and monolithically integrating those
testing and ETR choice mechanisms into the core-edge separation
scheme itself.

I don't think we should be rushed into thinking we can't possibly
have local full-database query servers in ISPs and larger end-user
networks, or that it is impossible to push the mapping to them in a
few seconds (real-time).  One advantage of the real-time approach
over LISP-ALT, APT's approach or the TRRP DNS-like global query
server approach is that it is streamlined and includes multiple
mapping changes (dozens or perhaps a hundred IPv4 mapping changes) in
a single packet.


> I want to address each of your 7 points below. I have cc'ed the
> lisp@ietf.org mailing list so the folks who want to focus on details of
> LISP can see this thread.

OK, we are also transmitting to routing-discussion@ietf.org and
int-area@ietf.org .


>> 1 - Delays in delivering initial packets in a flow.  This is either
>>    due to sending the packets along the ALT network (which takes
>>    time and involves sending substantial volumes of data packets
>>    over the ALT network, rather than just mapping requests) or to
>>    sending mapping requests only, and waiting for the ITR to get a
>>    response before it attempts to send traffic packets.
> 
> We have a memory/bandwidth tradeoff. So we have to make a hard design
> call. I'd rather have mappings cached and timed out so they can be
> updated when they need to then to hold all the possible mappings for the
> Internet in an ITR.
> 
> There is no such thing of a free lunch. You either store all possible
> mappings or you fetch them when you need them.

That is the dichotomy between LISP-CONS/ALT and LISP-NERD.  However
there is another approach (APT and Ivip): full push to local query
servers.

RAM and hard drive space is very cheap.  The query servers don't need
to be Cisco-style routers.  They can be COTS or high-reliability
rack-mount PCs - with gigabytes of RAM and terabytes of hard disk
storage.

In Ivip, IPv4 mapping consists of 12 bytes:

  Start of the micronet  (32 bits)
  Length of the micronet (32 bits, but typically 16 or less)
  ETR address            (32 bits)

So if you have a COTS server with 16GB of RAM (this will no-doubt be
the common amount of RAM in PCs by the time a core-edge separation
scheme is deployed) then you can easily dedicate 12GB for mapping
information.  That is a billion micronets (more or less, depending on
the storage format), which will do the trick for many years to come.
 (IPv6 mapping is more bloated, but there is a longer time-frame for
implementing millions or billions of IPv6 micronets - time for RAM to
get cheaper still).

I think you - and the designers of APT and TRRP - have been somewhat
captive to established ways of thinking about how to solve a
"routing" problem: with more "routing" style structures.  This means
more routers, more messages and replies zipping around the world etc.
 It doesn't have to be like this.

I need to do more work on the fast-push system of Ivip - but you are
welcome to critique it in its current form:

  http://tools.ietf.org/html/draft-whittle-ivip-db-fast-push-00

If your design choice with LISP is optimal, or the only one you think
is available, then you should be able to point out why it is
impractical or undesirable to use an approach such as Ivip's:
real-time fast push on a global basis to local query servers, with
local pull from there to ITRs, followed by pushed updates from the
query server to the ITRs if a micronet's mapping changes within the
caching time of the mapping reply.

Likewise, you presumably have a critique about the practicality or
desirability of APT: slow push to local query servers (Default
Mappers) in each ISP, local pull from ITRs querying the Default
Mappers, local push of mapping updates from DMs to those ITRs which
need it (I think) and (again, my recollection) the Default Mappers,
rather than the ITRs, doing reachability testing and choosing which
ITR address an ITR uses.

The Net will soon be delivering gigabytes of video data to homes, in
near-real-time, for a few dollars.  Generally, a packet can be sent
from any host to any other host in 0.2 seconds or less.

In this scenario, why do you think global push to local query servers
- including high-speed, real-time push - is impractical or
undesirable?


>>    According to: http://www.lisp4.net/docs/lisp-ausnog02.ppt pp 10
>>    & 11 the experimental LISP ALT network's ITRs drop initial
>>    packets and send brief map request messages.   Even if we think
>>    this delay doesn't matter, I am sure enough potential adopters
>>    would - and therefore make it difficult or impossible for LISP or
>>    any other such solution to be widely enough adopted to solve the
>>    routing scaling problem.
> 
> Then why was/is ARP deployed in a 10^4 host-based bridged network with
> basically the same properties. First packet loss is not persistent when
> you look at all the traffic that originates from a source site to
> another destination site.

This doesn't apply to small end-user networks.  If there are to be
hundreds of millions of these sites, meaning hundreds of millions of
EIDs or (Ivip) micronets - then these are mainly going to be small
"sites", such as home offices, or more likely mobile devices.  The
initial packet delay will directly impact usability, since there may
only be one human user at each such "site".

If many small "sites" use a common ITRs in a large ISP, there will be
less trouble with this, since it will be more common for one site to
generate a packet to some EID/micronet which the ITR has mapping
from, due to another "site" sending a packet there too.  However, the
frequent delay of initial packets (actually, it seems you are
planning to drop all initial packets) will still be a problem.

If LISP is not meant to scale to a hundred million or a billion or
whatever "sites", then by whatever same smaller target number of
EIDs, micronets or whatever, this would make alternative approaches
such as Ivip or APT even more immune from whatever scalability
critiques you might make of them.

> The host vendors are probably thinking, if we do LISP in the host, you
> could wait to send your TCP SYN before the mapping is available. 

On IPv4, with most human-used hosts behind NAT, you can't put a LISP
ITR in the sending host, because the map reply won't come back to the
host.

In a scenario in which LISP is widely - ubiquitously - deployed, many
DNS servers are going to be on EID space.  This means the ITR will
often need to do a mapping lookup before it can send a DNS request.
The sending host will be on EID space and so the DNS server's ITR
will need to do a mapping lookup too before it can send the return
packet.  This will suck to a high degree in the current arrangement
where the DNS server sends a single packet.  The ITR of the DNS
server will drop that packet and send a mapping request for the
original sending host's EID.  Then, after a while, the sending host
will realise it got no DNS response.  If it sends the same request to
the same DNS server, it will get a response back quickly, since now,
the DNS server's ITR has the sending host's mapping in its cache.

But what if the sending hosts does it it might reasonably do: send
the request to a different DNS server?  Then the same pattern as
above occurs again.


> Guess
> what, you don't send that TCP SYN before you get the DNS Reply. ;-) I
> wonder why? Well I'll spell it out. If a host needs an address to make
> the connection, we can say it also needs a locator to make a connection.

So you are proposing that every DNS reply also include full LISP
mapping for every one or more EIDs of the one or more IP addresses
returned?  I doubt if that will always fit in one packet.

> The design choice of LISP *is to just change software in CPE devices* to
> get the feature of decoupling rather than changing all the hosts at a
> site. 

OK . . . LISP mutates again!   I have been following LISP intently
since about March 2007 and I don't recall any mention of changes to
hosts or to CPE - by which I guess you mean DSL, cable and fibre
router/firewalls.

Do you propose putting the ITR function in the DSL
modem-router-firewall?  That is not such a bad idea, since it has
(presumably) a public IP address and so can receive the map reply
message from the globally distant query server (in the case of LISP,
the mapping queries are typically answered by the destination
end-user network's ETR).

Ivip has the option for putting ITR functions in a sending host which
has a public address, or in a device such as a
DSL-modem-router-firewall.  It would not be out of the question to
put an ITR function in the sending host behind NAT, but then the
sending host would need to build a persistent tunnel through NAT to
the one or more local query servers - in order to receive mapping
updates from those query servers.  That is possible, but not part of
the current plan.

> That's a huge deployment advantage.

I don't see any advantage in terms of deployment, since it involves
changes to more and more equipment, including customer equipment.
Ivip's ITFH (ITR Function in Host) is optional - if it is cheap and
convenient to do this for servers or devices like DSL-routers, then
by all means do so.  It only makes sense when the device is
well-connected.  It would be a bad idea to put an ITR function in a
host or router at the edge of the network connected by a slow,
expensive or unreliable link such as a wireless link.

> So these CPE devices get packets before they have mappings.

OK - for instance, the ITR function is in a DSL-modem-router-firewall
device.

> We don't even want to consider a host
> to CPE router signaling protocol and all it's complexities to solve this
> and to keep the architecture pure, we don't want to snoop on DNS, SIP,
> or any other protocol that can give us a hint on where the host is about
> to send a packet.

I agree.


> So the cost is *either* first packet loss or sending the packet on the
> ALT using it as a request for a mapping.

These are not the only choices.

Another choice is to using a different architecture with local query
servers - as does APT and Ivip.   I think you have approached this
without thinking widely enough about the alternative ways of doing
things which are different from traditional approaches like routers
and DNS.

If you send the packet on the ALT network (for the purposes of
delivering it to the ETR ASAP, as well as to elicit a mapping reply
from that ETR) then you are going to greatly increase the volume of
traffic on the ALT network.  Many of these packets will be short -
but what if someone sends a 1500 or 9000 byte packet?

If you don't send the packet via the ALT network, then you either
drop it, or delay it until the mapping arrives.  But that could be
longer than 0.5 or 1.0 seconds, considering how many ALT routers the
mapping request packet needs to go through to get to the ETR, how
these ALT routers could be all over the world, and how the ETR could
be on the other side of the world anyway.  This is a lot slower than
the current system which usually takes 0.2 seconds or less to
delivers packet anywhere in the world.  (The round trip from
Melbourne Australia to Latvia is about 400ms.)


>> 2 - LISP-ALT's long-path problem
>>      http://psg.com/lists/rrg/2008/msg01676.html
>>      http://www.antd.nist.gov/~ksriram/strong_aggregation.png
>>
>>      [Fix? Another fundamental problem in the architecture.  Could
>>       be partially solved by more meshiness, but that would greatly
>>       increase the complexity of the network and so raise more
>>       scaling problems.]
> 
> Well this I believe is a duplicate of 1 above. So it's not really
> *another* problem.

In terms of delaying packets, I agree.  Do you agree the long-path
critique is valid?

The long path involves more than delay.  It involves traffic flowing
(often) all around the world due to the fact that the highly
aggregated structure of the ALT network will frequently result in
different levels of the ALT hierarchy of routers being distributed
all around the globe, since the physical location of organisations
who are responsible for various parts of the address space does not
correlate very strongly with geography or the topology of the Net.

This is a traffic burden, particularly if you are sending initial
packets on the ALT network for ASAP delivery to the ETR, rather than
just map requests.  (However, Ivip involves pumping mapping
information around the globe anyway, and if your ALT network only
handles requests, not traffic packets, the actual volume of traffic
should not be too much of a problem.)

Each operator of each ALT router needs to have a commercial
relationship with those other ALT routers they connect with.
Otherwise, why would they accept the traffic?  I haven't seen any
business plan for the commercial relationships which pay for the ALT
routers and their traffic.

Ivip's fast push system involves a charge per update, which will
finance the construction and running costs of most of the fast-push
system, which will be run collectively by the various RUAS (Root
Update Authorisation System) companies, each of which generates the
real-time mapping changes for multiple MABs (Mapped Address Blocks -
BGP-advertised prefixes encompassing thousands, or hundreds of
thousands of micronets).


>> 3 - Problems creating a highly aggregated ALT network in order to
>>    speed the flow of packets up and down the hierarchy, while also
>>    making the network robust against the failure of its routers and
>>    tunnels.  This has not been discussed much on the RRG, but it is
>>    an obvious problem.
> 
> If we can do this with BGP, which we have decades of existence proof why
> can't we do this with a tunnel topology 1) where a tunnel can be rehomed
> much quicker and easily than physical links and boxes we have to do with
> today, allowing aggregation to occur at the edges of the ALT network,
> and 2) these tunnels stay up because there is robust connectivity below
> the tunnel level to keep them up, hence there will be less route-flaps
> for EID-prefixes.

I don't recall any prior mention of rapidly reconstructing tunnels to
maintain the ALT topology.  I agree with your point 2 that the
tunnels will be reasonably robust due to relying on existing
connectivity which is generally ensured by BGP.

But what happens when two ALT routers loose their connection for a
moment?  Do they try to set up one or more tunnels with the same role
in the ALT topology as the one which just died?  This is your point
1.  It could get messy, but I guess it could be done, by using other
interfaces which, for some reason (I guess) have connectivity while
the interfaces used for the first tunnel don't.  But that is the sort
of situation which I think BGP would naturally resolve, generally in
a few seconds or less.

My concern is more about what happens if an ALT router dies.   In
your highly aggregated hierarchy, a mid-level ALT router is a single
point of failure for sending mapping requests to all the ETRs in the
branch below this router and from all the ITRs in that branch to ETRs
outside the branch.

When a mid-level router dies, you can't just re-establish tunnels -
it is dead.  The routers below need to establish tunnels to another
ALT router which can take the dead one's place.

How is this going to work?  Say one lower-level router finds it can't
reach the mid-level router in question, it is going to assume the
mid-level router is dead.  So the lower-level router tries to set up
a tunnel to the one or more backups.  If it does so, either this
won't work at all, or the next level up will have to adapt to the
original mid-level router having routes for most of its patch of the
ALT address space, but with the backup having the router for the
smaller patch of space handled by the lower-level router which just
made a tunnel to the backup mid-level router.

> I think it's the complete opposite of what you claim. I think BGP will
> be more stable and scalable then the underlying BGP. 

I assume you mean that the BGP of the ALT network, operating over
tunnels, will be more stable than the BGP of the Internet.  This is
your point 2, and I largely agree.  But what if an ALT router dies?

> Plus, what we
> propose for the use-case of BGP uses quite a few features of it. Recall
> this is eBGP over GRE.
> 
> We have an infrastructure where we can 1) ping to see liveness of nodes
> on the ALT. We have traceroute to determine the path a Map-Request takes
> on the ALT. We can ping/traceroute "underneath" so we can see the
> diameter of the tunnel. 

I don't understand "diameter" in this context.

> Not only do we have a solution but we use
> existing rudimentary tools for management.
> 
> And the address allocation hierarchy can map this logical ALT topology.
> And if the Registries are involved in managing part of this ALT network
> (which we hope and think they will), we can keep this consistent
> relationship.
> 
> Do you realize the goodness of this? It's huge Robin.

I am sure you can make the ALT network reasonably robust, at a cost
of complexity and with a loss of the original attractive design goal:
a very high degree of aggregation.

I imagine you can reduce the excessively long paths by collapsing the
network as much as possible to reduce the number of levels a packet
typically has to ascend and descend.  This will reduce the
"long-path" problem significantly.  But then, each participating
mid-level ALT router (there are fewer of them) covers a larger part
of the address space, and my concerns above become more acute, when
such a router fails or becomes really unreachable.

I imagine you can reduce the geographical scatter component of the
long-path problem by centralizing the ALT routers geographically.
However, that privileges some operators and creates costs and
difficulties for others.

I still think it is fundamentally wrong to have a global query server
network for any system like this, where waiting for mapping replies
involves delaying or dropping traffic packets.

I think a much better solution is to push the mapping to local query
servers in each ISP (APT and Ivip) - and into any larger end-user
networks which want to run their own local query servers (Ivip) so
their ITRs can get marginally faster, more reliable, responses than
by using the query servers of their ISPs.


> There's more too, you then throw SIDR in the mix and we have secured the
> ALT, we have secured mappings, we created a PKI for routing use. In
> fact, the first SIDR deployment could happen on the ALT to be
> verified/experimented before it goes on the underlying BGP.

PKI is a great idea, but I think most people believe it is highly
desirable to find solutions which do not require it.


> And note, that the infrastructure will/does carry exactly 2
> address-families. So we can do 6-to-6-over-4 with this approach. That
> means we can get two site to be *IPv6-only* and be able to talk to each
> other.
> 
> If you are a IPv6-only site now or a dual-stack site, you could talk to
> the new IPv6 Google services. I think this is a pretty huge feature.
> 
> This is clean and architecturally pure, no double NATs, no CGNS, and no
> applications breaking.

Are you discussing just the mapping queries going over the ALT
network?  Or are you discussing the use of LISP to enable, for
instance, two IPv6 sites to communicate via the IPv4 Internet, while
one or both sites has no native IPv6 connectivity?   A concrete
example would help.


>> 4 - LISP-ALT's Aggregation implies provider dependence.
>>    This is Christian Vogt's critique:
>>    http://psg.com/lists/rrg/2008/msg00259.html
> 
> Not true. Aggregation here is for the EID-prefix. Service providers do
> not carry EID-prefixes in their cores so you don't depend on them. The
> decoupling of the address creates this. 

Christian's critique is not that an end-user network which has
(permanently, by some arrangement) a slice of EID space is bound to
its current ISP (the one it uses for connectivity).

The critique is on this potentially erroneous basis: that the
end-user network is bound to maintaining connectivity (via a tunnel)
to the ALT router which handles this part of the EID space.  It needs
to do this so mapping queries for its EID space will get to its ETR.

The potentially faulty aspect of this is the assumption that the
end-user network runs its own ETR.

But if its one or more ISPs run the ETR this end-user network uses,
then the end-user network still depends on those ETRs having tunnels
to potentially distant ALT router for its section of the EID space.

I don't know if anyone has considered the scaling problems of a busy
ETR maintaining tunnels to about as many ALT routers as the end-user
networks it handles packets for.

The ALT router for this section of the EID space will, I assume, be
located at some ISP somewhere, or some other commercial organisation
which rents out the EID space to this end-user network.

Maybe that organisation is an RIR.  But when this scales to tens or
hundreds of millions of end-user networks (I assume this is a goal of
LISP - it is of Ivip) I doubt if RIRs will want to be dealing with a
hundred million end-user networks directly, either for address
assignment or for tunnels to receive mapping requests to their ETRs
from the ALT network.

For these large scaling arrangements, there will need to be
potentially multiple levels of address splitting.  Ivip allows for
this, and for multiple levels of companies providing interfaces to
accept mapping changes from end-user networks (or more likely from
reachability testing companies they hire) and funnelling them to the
limited number of RUAS organisations which run the fast-push mapping
distribution system.

Any way you do this core-edge separation business - LISP, APT, Ivip
or TRRP - if the end-user network gets a patch of stable address
space to call their own, year after year, then that network is going
to depend on some company or other organisation for that space.  The
end-user network will need to pay for this, and depend on the
organisation to handle mapping.

In the case of LISP-ALT, the organisation needs to run (or have
someone else run) an ALT router (plus backups) which has a tunnel to
the ETRs in the ISPs which the end-user network is currently using
for access.  If that organisation's ALT routers go down, it is not
the fault of the access ISPs - it is up to the end-user network to
ensure it obtains its EID address from an organisation which provides
a reliable ALT router service.

Also - assuming the space is covered by a PTR in order to provide
100% multihomed service for packets sent from hosts in non-upgraded
networks - this organisation has to run PTRs which covers this
end-user's EID space.  For this to be scalable (not to bloat the DFZ
routing table excessively, as we go to millions of end-user networks
with EID/micronet space), the PTRs needs to advertise a prefix which
covers the EID space of thousands or hundreds of thousands of
separate end-user networks.

Since the sending hosts (in non-upgraded networks) could be anywhere
in the world and since the ISPs used by all these end-user networks
(covered by the one BGP advertised route) could be anywhere in the
world, in order to ensure reasonably direct path for traffic packets,
there needs to be a largish number of PTRs physically all over the
Net.  Then the organisation which runs this PTR system needs to
recover costs from individual end-user networks according to the
traffic the PTRs carry.   (This is the Ivip business model for
OITRDs.  I am stating this as an imperative for LISP, because I can't
imagine any other business model for PTRs.)

In the case of Ivip, the equivalent organisation needs to do the same
as just stated for OITRDs and provide the real-time mapping
distribution service, with a small charge per update.

Either way, the end-user network has a long-term technical and
commercial dependency on whichever organisation supplies its EID
(LISP) or micronet (Ivip) address space.  This is why my message
continued to state that a problem such as this is common to all
core-edge separation schemes:

      [Fix?  Seems to be a fundamental problem, but every core-edge
       separation scheme involves supplying stable EID, micronet etc.
       address space to end-user networks, so there must be some
       kind of dependence on some organisation - though not
       necessarily an ISP.]

      {Experiments?  There's no need for experiment - problems such
       as this can be clearly foreseen.}

So while I could take this off the list of "unresolved" problems for
LISP, since other schemes have comparable problems - I think LISP
could be improved by more clearly stating the types of commercial and
technical relationships each participating end-user network will rely
upon.  Also, the physical distance to the ALT router from wherever
the end-user network's ETRs are directly affects the delay
experienced at the start of sessions.  I think that is part of
Christian Vogt's concern.

I think I have done a better job of explaining all this with Ivip's
business model for OITRDs:

  http://psg.com/lists/rrg/2008/msg01158.html

> The dependence is now on the
> ALT. And if your site resides in a specific region of the world, you get
> your EID-prefixes from that registry. So readdressing your domain would
> only occur if you moved it from one region to another (let's leave
> mobile ASes out of this for now).

I think a good core-edge separation scheme should make the EID
(micronet) space entirely portable, with little or no compromise in
performance or costs regarding mapping no matter where the end-user
network chooses to connect its EID space (or some part of it) to the Net.

This is easier for Ivip, since the mapping change command only
involves a few dozen bytes and is made quite infrequently.

For LISP-ALT, the mapping connection is an incoming stream of
requests or initial packets which also function as requests.  It is
time-sensitive, since only when a response arrives at the ITR can
communications without delay begin.  So the physical proximity (delay
and reliability) between the ALT router for this section of the EID
address space and the the ETRs of the ISPs currently used by the
end-user network is really important.  I don't mean San Jose to LA
distances - I mean Australia to the USA, Germany to China etc.

These do seem to be a fundamental difference between LISP-ALT and
Ivip.  However, both systems will only work well with a widespread
set of PTRs/OITRDs.


>> 5 - Path MTU Discovery problems.  Despite Fred Templin, myself and
>>    others discussing the inherent PMTUD problems in any map-encap
>>    proposal, there has been nothing from the LISP team to indicate
>>    they have a solution.  They seem to think there is no problem.
> 
> In section 5.4 of draft-farinacci-lisp-11.txt we describe two proposed
> solutions, one is stateless, and the other is stateful. The stateful
> creates no new table data structures but requires storing an addition
> 2-bytes of effective-MTU state per mapping.

OK - I apologise for stating that you thought there was no problem.

I haven't considered MTU problems of sending traffic packets along
the ALT network, in its GRE tunnels (which impose their own
encapsulation overhead) - but I understand the current LISP test
network doesn't send traffic packets over ALT.  It is my impression
that your long-term plans are to use the ALT network only for short
map request messages, not go get initial traffic packets to the ETR ASAP.

Version 08 (2008-07-10) introduced a stateless technique and version
11 (2008-12-19) adds a stateful approach, derived from the OpenLISP
project, who regarded the stateless approach as inadequate.

My assessment of both approaches is in a separate message:

  LISP PMTU - 2 methods in draft-farinacci-lisp-11
  http://www.irtf.org/pipermail/rrg/2009-January/000885.html

I think the stateless section is poorly written and ill-conceived.
The stateless approach for IPv4 DF=1 packets and IPv6 packets (that
is, virtually all traffic) would limit traffic packets to 1464 bytes
(IPv4) or 1444 bytes (IPv6).  Only once there was jumboframe links
between every ITR and ETR could L be globally adjusted upwards from
1500 bytes to ~9000 bytes or whatever - but this would not be
possible for a decade or two.  Fred Templin expressed the same
concerns in a recent RRG message.

The Stateful approach, which I understand is derived from OpenLISP,
is similar to Ivip's approach:

  http://www.firstpr.com.au/ip/ivip/pmtud-frag/

I need to write this up as an I-D, but it is a more detailed spec
than your LISP approach, with mechanisms for occasionally testing for
MTUs longer than the assumed limit and for strictly minimising the
number of traffic packets which are used to probe the PMTU.  Every
packet whose length, once encapsulated, is in the "zone of
uncertainty" for this ETR is either delivered or rejected with a PTB.
   The former raises the lower limit to the zone and the latter
reduces the upper limit.


>> 6 - Lack of business case for LISP's Proxy Tunnel Routers:
>>    http://psg.com/lists/rrg/2008/msg02021.html
> 
> You cannot fault a technical design for a business case. 

A complete solution to the routing scaling problem involves much more
than a technical design.

All the technical stuff (sometimes split into "architecture" vs.
"engineering") needs to facilitate someone wanting to build and run
each part of it - which generally means they (or someone not too far
removed from them) needs to be able to make money from it.


> A PTR is
> solving a technical problem. And if we want to *truly* keep lots of PI
> type routes out of the core *and* avoid NAT solutions which are just way
> too high in opex, the PTR is the only solution we have to turn to.
> 
> And on the contrary, I do believe service providers, interconnect
> providers, registries, third-parties and even governments will provide
> PTR services. Will they make a ton of money out of it, well that remains
> to be seen.

I think my critique is valid - you seem to have no business case for
LISP's Proxy Tunnel Routers.

You are welcome to adopt the Ivip approach for address management and
OITRDs:

  http://psg.com/lists/rrg/2008/msg01158.html

This is directly applicable to LISP and PTRs, as long as you have a
concept of a Mapped Address Block, containing many EIDs.  For that to
be the case, you need to develop business arrangements concerning who
really "owns" the MAB and how they rent this space out as EID space
for thousands of end-user networks.


>> 7 - The scaling problems of potentially thousands of ITRs each
>>    probing reachability to one ETR, and likewise, one ITR probing
>>    reachability to many ETRs - this is one view of the "Locator Path
>>    Liveness Problem" of draft-meyer-loc-id-implications-00.
>>    http://www.irtf.org/pipermail/rrg/2009-January/000809.html
> 
> That is not in the LISP design. Everyone just thinks it is.  ;-)
> 
> Dave and Darrel's draft is providing a warning about how bad probing can
> be. They do not take a position whether it should go into any proposal.
> They are just saying, beware of the Frankenstein that may result and can
> be an interpretation to not do probing at all.

The scaling problem of thousands of ITRs continually test
reachability for one ETR (or to every ETR on the LISP mapping list
for a given EID), plus reachability through each ETR to a given
destination network, or of each ITR having to test reachability to
thousands or tens of thousands of ETRs have been obvious from the
start: early 2007.

This is true of LISP, TRRP and to a somewhat lesser extent APT. (I
haven't read RANGER yet.)

Only Ivip avoids these scaling problems by making the end-user
network responsible for their reachability testing and for deciding
which ETR the packets for each micronet should be tunneled to.


> Like I mentioned in a previous RRG email message, one has to ask the
> question if an ITR *should* switch from one RLOC to another when there
> *may* be a path failure *somewhere in the middle of the network*. Please
> note my very fine qualifications.
> 
> If we want to solve this problem, we could do this today by having a
> host switch it's TCP connection to another A record. This doesn't happen
> today because people deal with packet loss, since it doesn't last long
> *and* rerouting actually works quite well.
> 
> Van Jacobson always made this comment and I'll never forget it, "The
> fact that the Internet drops packets is it's greatest feature".
> 
> What else can either an xTR or TCP host do when sending ICMP
> Unreachables are off by default in most modern routers, or they are
> filtered by firewalls, and route aggregation hides failures close to
> packet sources.

The alternative has been available to you and anyone else since July
2007: Ivip.  A fast-push mapping system to local query servers means
the ITRs don't need to test reachability or make any decisions about
which ETR to use.  The mapping has a single ETR address.

What is wrong with this approach?


>>> Unless these concerns are adequately addressed, claiming that LISP
>>> is an appropriate solution to the problems discussed at the IAB's
>>> October 2006 Routing and Addressing Workshop is nothing more than
>>> a proof by an emphatic assertion.
>>
>> I agree entirely.
>>
>> I believe the LISP team could have made much better use of the RRG -
>> by participating fully in the debates resulting from these critiques.
> 
> We were asked to do research in RRG. That was a reasonable request. So
> the research stuff in LISP has been and will continue to be presented in
> RRG.

OK.

> As for the engineering issues, the real details and bits and bytes, we
> want a forum to discuss and work out issues in an open forum. I've been
> going to IETF for 20 years now, that forum is called a working group.
> 
> The working group doesn't have to standardize what it is working on. And
> the charter and the numerous requests we have made requests *for an
> experimental working group*.

I think this is fine.

However, I think there are sufficient fundamental, well known
problems with LISP-ALT that if this was my proposal, I would fix them
before asking people in general to join an IETF WG and help me with
it - or drop the proposal.


>> Experiments won't help solve most of these problems.  I am not
>> against experimentation and I think it is great that there is a LISP
>> experimental network.
>>
>> However, I would never have taken a proposal to the point of writing
>> code, running a network and inviting others to write compatible
>> implementations when the proposal had so many fundamental problems.
> 
> There is constant implementation feedback back into the design.
> Experienced engineers know how this cycle works. You start with
> something you think can hold together, you try things out, you refine,
> you revisit design, you go forward with implementation. That's the
> process of *detailed* engineering.
>
> For the old timers, that was the difference between TCP/IP and OSI.

I am all for detailed engineering, running tests etc.  However, the
worst problems I perceive with LISP-ALT will not be illuminated by
any amount of testing, as I explained in the message you are
responding to.


Do you think Ivip is so overblown and over-complex that it warrant's
no serious consideration?

Just because I write stuff in detail doesn't mean the system itself
is over-complex.  Ivip ITRs and ETRs are much simpler than LISP ITRs
and ETRs.


I have been giving your work the honour of detailed critiques for 18
months.  I would appreciate you and your colleagues returning the
favour by reading:

  http://www.firstpr.com.au/ip/ivip/Ivip-summary.pdf

  http://tools.ietf.org/html/draft-whittle-ivip-db-fast-push-00

  Ivip business models: fast push & OITRDs
  http://psg.com/lists/rrg/2008/msg01158.html

and telling me - and the RRG - what you think.


Also, I am keen to know from you, your Cisco colleagues and from the
folks at Juniper how practical it would be to create firmware
upgrades for all the DFZ routers in use ca. 2014 or whatever -
whenever the routing scaling solution is to be implemented.

I think it is practical and highly desirable to encode the ETR
address in the IPv4 header (actually 30 bits, which is fine) or a 20
bit prefix label in the IPv6 header.  Then, in the longer term, we
don't need encapsulation, its complexity, its overhead and its damn
PMTUD problems.

As far as I know, both these proposals could be implemented as
firmware upgrades, or built-in optional features, in the DFZ routers
which are likely to be in use in 5 years time, but only you guys can
say this is so or not:

  ETR Address Forwarding (EAF) - for IPv4
  http://tools.ietf.org/html/draft-whittle-ivip4-etr-addr-forw-01

  Prefix Label Forwarding (PLF) - for IPv6
  http://www.firstpr.com.au/ip/ivip/ivip6/

Maybe we can do that in time for the introduction of the routing
scaling solution - and thereby completely avoid encapsulation and its
PMTUD complexities.


On mobility - what is your objection to this arrangement?  ETR-like
Translating Tunnel Routers with two-way encrypted tunnels to mobile
nodes.  Mapping only changes to a new TTR when one is really needed 0
which is typically only when the MN moves 1000km or more.  So mapping
changes are not at all frequent and in particular are not needed
every time the MN gets a new CoA:

  http://www.firstpr.com.au/ip/ivip/TTR-Mobility.pdf


If I was proposing to the IETF that a WG be formed for my project, I
would first want to establish for myself - and for IETF people in
general - that my project was either the best in its class, or one of
the very few with the most promise.

I don't see how you can do that when you fail to read - or at least
fail to discuss in public - alternative schemes to LISP.

Ivip and APT are broadly comparable to LISP - they are all core-edge
elimination schemes for both IPv4 and IPv6.  They are both well
enough documented to be suitable for serious critiques from anyone
who believes LISP's approach is superior.

Just because you have more people - with more experience and
resources - working on LISP and have running code, doesn't mean your
LISP-ALT design is better than APT or Ivip.


  - Robin

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Tue Jan 27 01:02:11 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EDE853A6BC6; Tue, 27 Jan 2009 01:02:10 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3C8883A6BC6 for <rrg@core3.amsl.com>; Tue, 27 Jan 2009 01:02:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.984
X-Spam-Level: 
X-Spam-Status: No, score=-5.984 tagged_above=-999 required=5 tests=[AWL=-0.454, BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id exglAeGjVfXX for <rrg@core3.amsl.com>; Tue, 27 Jan 2009 01:02:09 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 59F823A6A53 for <rrg@irtf.org>; Tue, 27 Jan 2009 01:02:09 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,331,1231113600"; d="scan'208";a="133908786"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-1.cisco.com with ESMTP; 27 Jan 2009 09:01:39 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n0R91dDs012068;  Tue, 27 Jan 2009 01:01:39 -0800
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n0R91cVU022653; Tue, 27 Jan 2009 09:01:39 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Tue, 27 Jan 2009 01:01:39 -0800
Received: from [10.196.3.15] ([10.21.81.201]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Tue, 27 Jan 2009 01:01:38 -0800
Message-Id: <86333BD4-91F8-4E9A-82E2-E59AEB63447F@cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
In-Reply-To: <20090126225034.C65A557EAFD@mercury.lcs.mit.edu>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Mon, 26 Jan 2009 18:05:01 -0800
References: <20090126225034.C65A557EAFD@mercury.lcs.mit.edu>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 27 Jan 2009 09:01:39.0163 (UTC) FILETIME=[DD677AB0:01C9805D]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1431; t=1233046899; x=1233910899; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dino@cisco.com; z=From:=20Dino=20Farinacci=20<dino@cisco.com> |Subject:=20Re=3A=20[rrg]=20[lisp]=20[Int-area]=20Please=20 respond=3A=20Questions=20from=20the=20IESG=20as=20towhether= 20a=20WG=20forming=20BOF=20is=20necessary=20for=20LISP |Sender:=20; bh=JZOf4n6ICssI0Ba4N7JDpvP6ZwoyefGJ4wumBuybdYA=; b=jAtiQFdeyyAWf6TlSmfF+qeS8AhJTq2/Abs5lgYRkJiPQlYTLNu0XSARA1 xQMa55KTHDqgH0uvQKMo2A47rHonH9HnLuJ3SiSP7SNroCiSPhO6LXnx1PXc ijQP7ABr4WUU6SicTyQBWa5GXETQu4DunGsmnCkzHAfTA5B31a178=;
Authentication-Results: sj-dkim-1; header.From=dino@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); 
Cc: rrg@irtf.org
Subject: Re: [rrg] [lisp] [Int-area] Please respond: Questions from the IESG as towhether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

>> if you are going to claim liveness through a protocol, you have to  
>> send
>> control packets all the time from M ITRs to N ETRs.
>
> I find this terminology somewhat non-intuitive, and wonder if it's  
> too late
> to change it. To me, "liveness" would imply as to whether something  
> is live
> or dead, i.e. up or down. (Such state detection can obviously be  
> performed on
> ITR I1's behalf by I2, and the result communicated locally from I2  
> to I1.)

I think its only documented in the Dave/Darrel draft. But they use the  
term "path liveness" so I think that is a more appropriate term.

> The issue of whether packets from ITR Im can reach ETR En (which is  
> where you
> run into the need for M*N) I would describe as "reachability". (So  
> if there's
> a routing problem, or an access control setting, that prevents I1 from
> getting to E7 even through I1 can get to E8 and I2 can get to E7,  
> that would
> be a reachability problem on the {I1, E7} pairing.) I seem to recall  
> this
> term being used in at least one routing protocol, although I can't  
> now recall
> which one.

Right, Dave/Darrel referred to it as "reachable paths", "testing  
reachability", "is there path liveness". Those sorts of terms.

Dino

>
>
>        Noel
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> http://www.irtf.org/mailman/listinfo/rrg

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Tue Jan 27 01:12:31 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B761E3A6A48; Tue, 27 Jan 2009 01:12:31 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 567DC3A6A48 for <rrg@core3.amsl.com>; Tue, 27 Jan 2009 01:12:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.206
X-Spam-Level: 
X-Spam-Status: No, score=-2.206 tagged_above=-999 required=5 tests=[AWL=0.043,  BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CA6BC-rlugaG for <rrg@core3.amsl.com>; Tue, 27 Jan 2009 01:12:29 -0800 (PST)
Received: from mail.net.t-labs.tu-berlin.de (mail.net.t-labs.tu-berlin.de [130.149.220.252]) by core3.amsl.com (Postfix) with ESMTP id 7B1E43A69E0 for <rrg@irtf.org>; Tue, 27 Jan 2009 01:12:29 -0800 (PST)
Received: from [130.149.220.21] (kea.net.t-labs.tu-berlin.de [130.149.220.21]) by mail.net.t-labs.tu-berlin.de (Postfix) with ESMTP id 4341E70015D8; Tue, 27 Jan 2009 10:12:11 +0100 (CET)
Message-ID: <497ECFCF.7020207@net.t-labs.tu-berlin.de>
Date: Tue, 27 Jan 2009 10:11:43 +0100
From: Luigi Iannone <luigi@net.t-labs.tu-berlin.de>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
References: <20090126190307.275276BE571@mercury.lcs.mit.edu>
In-Reply-To: <20090126190307.275276BE571@mercury.lcs.mit.edu>
X-Enigmail-Version: 0.95.0
Cc: rrg@irtf.org
Subject: Re: [rrg] [lisp] Economic issues of long-path / stretched routing
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Noel Chiappa wrote:
>     > From: HeinerHummel@aol.com
>
>     > Why LISP 1.5=20?  Why not LISP 2 ? or directly:
>     > Why doesn't the ITR intercept and enhance the DNS lookup as to also request
>     > the eRLOC address in addition to the dest IP address? It can also
>     > intercept the respective response and store (EID, eRLOC).
>
>   
Besides the reasons the Noel gave, which I agree on, using DNS generates
more issues than solutions IMHO.

Not all DNS queries go through an ITR, since probably there will be a
DNS cache inside the domain.
Using DNS in this case means that synchronization between DNS caches and
LISP caches is needed!
This is already difficult IMO, and it is even worse if you think that
DNS cache has been designed for a totally different purpose, which I do
not think fits in the requirements of the LISP cache.

Luigi

> I don't know what the thinking of other people working on LISP is, but I can
> give you my thoughts on this point.
>
> Simply put, I don't like designs which _invisibly, outside the host_ tie into
> the DNS because it takes two separate subsystems (DNS resolution, and basic
> packet forwarding), and tangles them together, which is bad engineering for a
> number of reasons (makes it harder to make further changes, creates more
> mutual dependencies, increases overall fragility/brittleness, etc).
>
> Some NAT variants do this too, and I especially didn't like them either! :-)
>
>         Noel
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> http://www.irtf.org/mailman/listinfo/rrg
>   

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Tue Jan 27 01:40:44 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F18583A6BD1; Tue, 27 Jan 2009 01:40:43 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8B8403A6BD0 for <rrg@core3.amsl.com>; Tue, 27 Jan 2009 01:40:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.212
X-Spam-Level: 
X-Spam-Status: No, score=-2.212 tagged_above=-999 required=5 tests=[AWL=0.038,  BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CJZxB6fyHQsD for <rrg@core3.amsl.com>; Tue, 27 Jan 2009 01:40:41 -0800 (PST)
Received: from mail.net.t-labs.tu-berlin.de (mail.net.t-labs.tu-berlin.de [130.149.220.252]) by core3.amsl.com (Postfix) with ESMTP id 3C0033A685F for <rrg@irtf.org>; Tue, 27 Jan 2009 01:40:41 -0800 (PST)
Received: from [130.149.220.21] (kea.net.t-labs.tu-berlin.de [130.149.220.21]) by mail.net.t-labs.tu-berlin.de (Postfix) with ESMTP id 1E1CF70015D8; Tue, 27 Jan 2009 10:40:23 +0100 (CET)
Message-ID: <497ED66B.8000505@net.t-labs.tu-berlin.de>
Date: Tue, 27 Jan 2009 10:39:55 +0100
From: Luigi Iannone <luigi@net.t-labs.tu-berlin.de>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: Robin Whittle <rw@firstpr.com.au>
References: <497E9BB2.5040101@firstpr.com.au>
In-Reply-To: <497E9BB2.5040101@firstpr.com.au>
X-Enigmail-Version: 0.95.0
Cc: RRG <rrg@irtf.org>, lisp-interest@lists.civil-tongue.net
Subject: Re: [rrg] LISP PMTU - 2 methods in draft-farinacci-lisp-11
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Hi Robin,

See few comments inline

Robin Whittle wrote:
> Short version:  Stateless approach is a really bad idea in the future
>                 when ~9000 byte MTU ITR to ETR paths become common.
>
>                 Stateful approach somewhat resembles Ivip's approach
>                 - which is documented in greater detail and limits
>                 the number of traffic packets for which state must
>                 be stored in case a PTB is received.
>
> Here my thoughts on the two techniques (Stateless and Stateful) for
> LISP Path MTU Discovery management in the latest (19 December) draft.
>
> My understanding of the whole problem (for Ivip's map-encap modes or
> for any other map-encap scheme, such as LISP or APT), together with
> my solution for Ivip, is here:
>
>   http://www.firstpr.com.au/ip/ivip/pmtud-frag/
>
>
> Here is my critique of the Stateless approach, assuming L = 1500, as
> is recommended at the end of:
>
>   http://tools.ietf.org/html/draft-farinacci-lisp-11#section-5.4.1
>
> The stateless approach was rejected by the OpenLISP team:
>   
As a member of the OpenLISP team, let me say that we do not *accept* or
*reject* anything.
AFAICT, that is left to the  community and to the (future) LISP WG.

What we proposed is just an alternative approach that takes advantage of
ICMP messages (if they are present).
> http://tools.ietf.org/html/draft-iannone-openlisp-implementation-01#section-6.8.1
>
>
>   
[snip]
> Stateful approach for all packets
> ---------------------------------
>
> I am reading the LISP version - I have not looked in detail at the
> OpenLISP source of this approach.
>
> This makes no reference to IPv4 DF=0 packets.  So this approach of
> the ITR sending a PTB packet to the sending host when a DF=0 packet
> exceeds some length is not going to result in any action on the part
> of the sending host.  Such a DF=0 packet will be dropped by the ITR.
>  That may be OK - Ivip will do much the same - but it needs to be
> specified clearly.
>   
The text that we provided is just a first cut. I agree that there are
several points to clarify.
> This approach of determining the MTU to each ITR by receiving ICMP
> messages from an intermediate router needs to be done securely.
>   
Am I wrong if I say that this means to change the ICMP protocol?
Our goal was not to introduce new mechanisms in the core, but rather to
take advantage of what exists.
> It requires the ITR to cache significant amounts of information for
> every packet it sends which might trigger such a PTB.
>   
Why should the ITR cache information?
> The intermediate router would need to send back sufficient of the
> original packet to ITR to include the LISP nonce.  Otherwise, PTBs
> spoofed by off-path attackers would be accepted and the whole system
> could easily be DoSed.
>   
Probably there is a DoS risk, but IMO is from on-path attackers. How can
an off-path attacker know that a specific ITR is sending packets to a
specific ETR and sen a fake ICMP message to shrink the MTU toward that
specific ETR?
> The ITR needs to store an initial fragment of each incoming traffic
> packet for some time, so it can generate a PTB message for the
> sending host.  It can't rely on enough of the original packet coming
> back in the PTB from the intermediate router.  The ITR needs to cache
> this for a second or two at least - while it waits for a possible
> PTB.  This is an onerous requirement in a high-volume ITR.
>
>   
No. This is not the case.
Assume the following topology:

H1-----------ITR1-----<DFZ>----------ETR2-----------H2

where host H1 send packets to host H2.  If a first packets triggers a
ICMP PTB in the DFZ, this is sent back to ITR1, which sjust stores the
fact that to reach ETR2 a smaller MTU must be used. Nothing is sent back
to H1.
H1 sends a second packet. On the ITR1 there will be a check on the MTU
triggering a second ICMP PTB to be sent back to H1.

So, you need to big packets in order to make the feedback reach the
original sender, but the ITR does not need to store packets.

Hope this clearer now.

Cheers

Luigi


_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Tue Jan 27 05:48:28 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 63F2B3A6B6B; Tue, 27 Jan 2009 05:48:28 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F3E9A3A6B6B for <rrg@core3.amsl.com>; Tue, 27 Jan 2009 05:48:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.53
X-Spam-Level: 
X-Spam-Status: No, score=-1.53 tagged_above=-999 required=5 tests=[AWL=0.365,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Qcwb2WBtsqF for <rrg@core3.amsl.com>; Tue, 27 Jan 2009 05:48:25 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123]) by core3.amsl.com (Postfix) with ESMTP id 26E013A677E for <rrg@irtf.org>; Tue, 27 Jan 2009 05:48:24 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6]) by gair.firstpr.com.au (Postfix) with ESMTP id 0D6F8175716; Wed, 28 Jan 2009 00:22:54 +1100 (EST)
Message-ID: <497F0B30.1010404@firstpr.com.au>
Date: Wed, 28 Jan 2009 00:25:04 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: RRG <rrg@irtf.org>
References: <497E9BB2.5040101@firstpr.com.au> <497ED66B.8000505@net.t-labs.tu-berlin.de>
In-Reply-To: <497ED66B.8000505@net.t-labs.tu-berlin.de>
Cc: lisp@ietf.org
Subject: Re: [rrg] LISP PMTU - 2 methods in draft-farinacci-lisp-11
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Short version:     Luigi suggests a method by which the ITR
                   can perform PMTUD to an ETR without having
                   to cache the original packet.  This requires
                   three things to be done to achieve the goals
                   without the most obvious DoS vulnerabilities:

                   1 - The intermediate router sends back at least
                       16 bytes of original packet in the PTB -
                       8 bytes more than RFC 1191 requires.

                   2 - It is acceptable for the system not to
                       deliver the first "too long" packet.

                   3 - The sending host sends a second "too long"
                       packet after the ITR has received and
                       processed the PTB from the intermediate
                       router.

                   If the system is supposed to work without the
                   PTB check requiring the LISP nonce in the PTB's
                   original packet fragment, then I think the ITR
                   still needs to store some details of recently
                   sent packets, to force the attacker to set some
                   other parts of the PTB's original packet fragment
                   to hard-to-guess actual values of packets sent.

                   I modify my critique of LISP accordingly - this
                   looks like a reasonable way to do PMTUD without
                   the ITR maintaining a lot of state.  However the
                   smallest amount of state would be the LISP
                   nonce of recently sent packets and this requires
                   all intermediate routers which might have an
                   MTU problem to send back more than the RFC 1191
                   minimum of 8 bytes.

                   The process of checking PTBs in a busy ITR could
                   become so expensive (due to the large number of
                   LISP nonces or other details to be checked, of
                   recently sent packets) that it could become a DoS
                   vulnerability in itself.

                   How I think an off-path attacker could find the
                   addresses of some, many or most ITRs which are
                   tunneling packets to some ETR the attacker wants
                   to DoS.

                   An ITR occasionally needs to allow longer packets
                   to the ETR than its current MTU setting allows -
                   otherwise it has no way of adapting to an
                   increased actual path MTU.


Hi Luigi,

Thanks for your reply, in which you wrote:

> As a member of the OpenLISP team, let me say that we do not
> *accept* or *reject* anything.  AFAICT, that is left to the
> community and to the (future) LISP WG.

OK - "rejected" was my way of stating that you didn't find the
stateless approach suitable for OpenLISP:

http://tools.ietf.org/html/draft-iannone-openlisp-implementation-01#section-6.8.1

   6.8.1. OpenLISP local MTU Management

   During preliminary tests, we observed that the MTU issue is at the
   origin of many problems.  OpenLISP does not (and will not)
   implement the fragmentation mechanism proposed in Sec. 5.4 of
   [I-D.farinacci-lisp].  The reason is because the proposed method
   sounds very primitive and does not appear to be efficient.  The
   original LISP specification is based on an architectural constant
   used by the xTR to limit the MTU of LISP encapsulated packets.
   OpenLISP uses a more advanced solution, based on the real MTU of
   the local RLOCs present on the xTR, as described below.


> What we proposed is just an alternative approach that takes advantage of
> ICMP messages (if they are present).

OK - your approach makes sense.  I am reading it now.


>> Stateful approach for all packets
>> ---------------------------------
>>
>> I am reading the LISP version - I have not looked in detail at the
>> OpenLISP source of this approach.
>>
>> This makes no reference to IPv4 DF=0 packets.  So this approach of
>> the ITR sending a PTB packet to the sending host when a DF=0 packet
>> exceeds some length is not going to result in any action on the part
>> of the sending host.  Such a DF=0 packet will be dropped by the ITR.
>>  That may be OK - Ivip will do much the same - but it needs to be
>> specified clearly.
>   
> The text that we provided is just a first cut. I agree that there are
> several points to clarify.

OK.

>> This approach of determining the MTU to each ITR by receiving ICMP
>> messages from an intermediate router needs to be done securely.
>   
> Am I wrong if I say that this means to change the ICMP protocol?

I meant securely enough to prevent spoofing by an off-path attacker
intent on DoS.  (Full description below.)

The LISP nonce should do the trick - but that requires the
intermediate router to send back to the ITR, in the PTB message, the
8 byte LISP header after the UDP header.  RFC 1191 only requires it
to send back the outer IP header and the next 8 bytes - which in a
LISP packet is the UDP header.

This was a pretty short-sighted requirement, I think.  I don't know
how DFZ routers behave, but I recall someone (Bill Herrin?) stating
some months ago that it was common to send back more bytes than the
bare minimum of 8.  If LISP or something similar was implemented in 5
years time, I guess it wouldn't be too much to ask the router
manufacturers to create firmware updates if their routers don't
already send back a decent number of bytes such as 32 or whatever.

Without this, the ITR can't "securely" respond to ICMP PTB messages.

> Our goal was not to introduce new mechanisms in the core, but rather to
> take advantage of what exists.

OK.

>> It requires the ITR to cache significant amounts of information for
>> every packet it sends which might trigger such a PTB.
>   
> Why should the ITR cache information?

Skip the following if you like:

    My understanding of what ITRs would have to do, before I read the
    rest of your message:

    For every encapsulated packet the ITR sends which might generate
    a PTB message in some router en-route to the ETR, the ITR needs
    to cache - I mean store for a few seconds - the start of the
    original packet and the nonce it put in the LISP header of the
    encapsulating header.   I guess the ITR needs to store it for a
    few seconds, since it might take that long for the PTB to come
    back.  Technically, maybe it should hold it for longer, but my
    guess is that 2 seconds should do the trick.

    Then, when a PTB arrives, the ITR needs to compare the LISP nonce
    in the PTB's fragment of the initial packet (see discussion above
    about how this requires more bytes than RFC 1191 requires) with
    its cached information about recently sent packets.  It should
    also check other things such as the destination address in the
    packet fragment, to ensure it is the same as the ETR to which it
    tunnelled the packet.  This will enable the ITR to uniquely
    identify one of the packets it recently sent.  Then it can adjust
    for that ETR its record of path MTU, and generate a PTB packet to
    be sent to the sending host, from its cached fragment of the
    start of the original packet.

    After that, the ITR can use the stored value of MTU for that ETR
    and use it to decide whether to accept or reject with a PTB any
    packet to be tunneled to that ETR.

I don't think your I-D doesn't mention this, but the ITR also needs
to occasionally let a longer packet be encapsulated to this ETR - a
packet long enough that once encapsulated it would exceed the ITR's
current notion of path MTU to this ETR.  This will only occur if and
when one of the following occur:

  1 - The original sending host, in the same communication session
      tries its luck with a longer packet for the same reason.  RFC
      1191 specifies the one sending host should not try a longer
      packet to a given destination address for 10 minutes after
      receiving a PTB.

  2 - Some other sending host sending a longer packet through this
      ITR to an EID address which is mapped to the same ETR.

  3 - The same sending host, in the same or another application,
      sending a long packet to a different destination address,
      which may or may not be in the same EID as the first
      destination address, which is mapped to the same ETR.

Then, if the longer packet does not result in a PTB, the ITR should
probably raise its notion of the MTU to that ETR accordingly.

However, packet loss here (loss of the too long packet before the
intermediate router with the limiting MTU, or loss of the PTB message
from that router) could result in a too-long MTU setting in the ITR.
This is not such a problem, since it would probably soon be corrected
if subsequent packets passed through the ITR due to this too-high
value and did result in a PTB being received by the ITR.

The Ivip approach can use PTBs from intermediate routers, but does
not rely on them absolutely.  It uses positive and negative
acknowledgement from the ETR for a small subset of packets which,
once encapsulated, are of a length which falls within the ITR's "zone
of uncertainty" for the path MTU to this ETR.  This zone is reduced
by every such packet and would, in general, quickly diminish to zero
- after which the technique is only needed occasionally to test
whether the MTU limit has risen.

I think would be best to store the path MTU value in a separate body
of data from however you store the mapping information.  The mapping
information is indexed on EID, I assume.  You might have in the
mapping cache thousands of entries which all use the same ETR.  It
makes no sense to store the ETR's path MTU in every one of those
entries.  I think the encapsulation process needs to check the path
MTU to the ETR after it has determined which ETR address to tunnel
each packet to.


>> The intermediate router would need to send back sufficient of the
>> original packet to ITR to include the LISP nonce.  Otherwise, PTBs
>> spoofed by off-path attackers would be accepted and the whole system
>> could easily be DoSed.
>   
> Probably there is a DoS risk, but IMO is from on-path attackers. How can
> an off-path attacker know that a specific ITR is sending packets to a
> specific ETR and send a fake ICMP message to shrink the MTU toward that
> specific ETR?

It is easy to find out where the ITRs of a particular ISP or end-user
network are.  Attackers could discover this by various means, but
here is one:  They get their own EID space, which is mapped to an
RLOC address of one of their own machines - which pretends to be, or
is, an ETR.  Then, the attacker sends to some host in the ISP or
end-user network a ping packet or any other packet which will elicit
a response.  That packet has a source address in the attacker's EID
range, so the targeted host will send back a response to that
address.  The ITR in the targeted site will look up the mapping for
the attacker's EID address and so tunnel the response packet to the
attacker's "ETR".  With LISP, APT and TRRP, the encapsulation outer
header's source address is that of the ITR, so the attacker's "ETR"
learns the address of the ITR.  (With Ivip, the source address is
that of the sending host.)

So attackers can easily find the address of an ITR in some network of
its choice where there are sending hosts.  It could do this en-masse
and so discover the addresses of ITRs in many such networks.

The attacker presumably has some idea of where the sending hosts are
for the destination network it wants to DoS.

The attacker could find the addresses of Proxy Tunnel Routers which
handle the attacker's EID.  The attacker simply send packets from one
of its own EID addresses to random IP addresses to get responses from
a bunch of hosts, many of which will use a PTR (all those which don't
have an ITR in their own network).  If there were a single set of
PTRs which handled every EID, then this would suffice to locate all
PTRs in the world.

However, at least in the Ivip model, there probably won't be OITRDs
(the Ivip version of LISP's PTR) which handle every micronet.  There
seems to be no business plan for LISP PTRs, so I can't say how they
would be organised.  Assuming that there is one set of PTRs for one
subset of the EID address space, and another set for another subset,
then the above method will only allow the attacker to discover the
PTRs which handle its subset.

I can't easily think of a way an off-path attacker could find the
addresses of the PTRs which handle the EID space of some network
which the attacker wants to DoS.  Nonetheless, attackers in general
could figure out the addresses of PTRs in various PTR networks and
share this information between themselves.

So an attacker could find the addresses of some, many or most ITRs
which might be tunneling packets to the site they want to DoS.

The attacker presumably has a motivation to DoS a particular ETR.  If
the attacker wants to DoS the ETR(s) of a particular organisation, it
can easily look up the mapping for that organisation's EID prefix to
obtain the ETR addresses.

With the ETR address and a list of ITR addresses, the attacker can
inexpensively generate a sequence of spoofed PTB packets.  (But see
discussion below on how much information the ITR needs to store about
recently sent packets, to force the attacker to correctly set length,
checksum and (IPv4 only) Identification bits to match a packet
actually sent, which the attacker, being off-path, can't see.

Each such spoofed PTB, if recognised by the ITR, can be used to
clobber the MTU the ITR perceives for the targeted ETR, so causing
significant and reasonably persistent DoS for a potentially large
number of sending hosts which rely on that ITR - and a potentially
large number of destination hosts in potentially multiple destination
networks which rely on this ETR.

If the ITR requires the LISP nonce to be in the PTB fragment, then
the system is secure against such spoofing, but then this PMTUD
system will only work if all the intermediate routers which might
cause an MTU problem send back at least 16 bytes rather than the RFC
1191 minimum of 8 bytes after the IP header.


>> The ITR needs to store an initial fragment of each incoming traffic
>> packet for some time, so it can generate a PTB message for the
>> sending host.  It can't rely on enough of the original packet coming
>> back in the PTB from the intermediate router.  The ITR needs to cache
>> this for a second or two at least - while it waits for a possible
>> PTB.  This is an onerous requirement in a high-volume ITR.
>   
> No. This is not the case.
> Assume the following topology:
> 
> H1-----------ITR1-----<DFZ>----------ETR2-----------H2
> 
> where host H1 send packets to host H2.  If a first packets triggers a
> ICMP PTB in the DFZ, this is sent back to ITR1, which sjust stores the
> fact that to reach ETR2 a smaller MTU must be used. Nothing is sent back
> to H1.

But that involves data loss.  The Ivip approach is intended to avoid
this.

> H1 sends a second packet. On the ITR1 there will be a check on the MTU
> triggering a second ICMP PTB to be sent back to H1.

Ahh . . . OK, you can make it work this way if you accept data loss
on the first large packet, expecting the sending host to generate
another similarly large packet, which seems reasonable.

I don't think this technique can be used with Ivip, but I will
consider it when I write the PMTUD I-D.

I withdraw my critique of LISP's stateful approach to PMTUD requiring
storage of the initial part of longer packets for a few seconds.
However, I think the text of draft-farinacci-lisp and your own
OpenLISP I-D should be revised to make this process clearer.

Still, if you are to check the nonce, you do need to store each nonce
of recently sent packets.

To do a proper check of the PTB, you need to store some packet
details - to force the attacker to generate the correct
Identification (IPv4 only) and Length bits from the IP header.

Likewise, if you store the UDP checksum of recently sent packets,
then you can force the attacker to get that right, which would be
generally impossible except by lots of attempts for data packets.  It
would be easier to spoof the checksum and length of TCP SYN packets
or some other commonly used short packets.  To protect against that,
your ITR would need to store the length of such (generally short)
packets and make sure the potentially spoofed PTB message's MTU limit
was not longer than the actual packet.  This, combined with some
general limit on how low you would accept the MTU to be according to
any PTB, would probably make the system immune to this kind of attack.


Also, I think you need to either check the LISP nonce (and accept the
system will fail if the PTB original packet fragment doesn't contain
it) or not expect it and so recognise that the system is open to a
powerful DoS attack if you don't store a bunch of details of recent
packets, and use them to carefully check all PTBs.

This PTB checking process itself could represent a DoS vulnerability
for a busy ITR.  If it has a lot of details of packets recently sent
- potentially hundreds of thousands or millions, I guess, and you are
not requiring LISP nonces, then you still have to search through some
long and constantly changing lists of packet details such as length,
UDP checksum (IPv4 only) Identification etc.  for every PTB received.

This could easily get way out of hand - those cached lists of recent
packet details are expensive enough to add to and clean out, and I
guess they can't inexpensively be optimised for inexpensive searching
to see which one matches a PTB.

PTB messages are pretty short (inexpensive for the attacker to send)
and could chew up a lot of ITR CPU power to process.  Checking only a
fraction of these PTBs (in order to limit the CPU time spent chewing
through a flood of spoofed PTBs) would slow down the ITR's ability to
adapt properly to actual MTU problems.


> So, you need two big packets in order to make the feedback reach the
> original sender, but the ITR does not need to store packets.
> 
> Hope this clearer now.

Yes - thanks.

  - Robin
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Tue Jan 27 05:55:39 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B5FA13A6BD8; Tue, 27 Jan 2009 05:55:39 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9F02928C11F; Tue, 27 Jan 2009 05:55:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.447
X-Spam-Level: 
X-Spam-Status: No, score=-6.447 tagged_above=-999 required=5 tests=[AWL=0.152,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GC5xEhdHSCAn; Tue, 27 Jan 2009 05:55:36 -0800 (PST)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id 968F03A6B14; Tue, 27 Jan 2009 05:55:36 -0800 (PST)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n0RDt02q028190 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 27 Jan 2009 05:55:05 -0800 (PST)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n0RDsxfQ006264; Tue, 27 Jan 2009 07:55:00 -0600 (CST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n0RDsuha006169; Tue, 27 Jan 2009 07:54:59 -0600 (CST)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 27 Jan 2009 05:54:53 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 27 Jan 2009 05:54:49 -0800
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1057A2DD3@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <497F0B30.1010404@firstpr.com.au>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] LISP PMTU - 2 methods in draft-farinacci-lisp-11
Thread-Index: AcmAheclODNzlk9FSf6JKCDdi9bX8gAAHRYQ
References: <497E9BB2.5040101@firstpr.com.au><497ED66B.8000505@net.t-labs.tu-berlin.de> <497F0B30.1010404@firstpr.com.au>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Robin Whittle" <rw@firstpr.com.au>, "RRG" <rrg@irtf.org>
X-OriginalArrivalTime: 27 Jan 2009 13:54:53.0790 (UTC) FILETIME=[D49E7FE0:01C98086]
Cc: lisp@ietf.org
Subject: Re: [rrg] LISP PMTU - 2 methods in draft-farinacci-lisp-11
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Robin,

FWIW, the LISP stateful/stateless approaches follow
those specified in RFC4213. Check there for caveats
about the stateful approach, and see also RFC2003
and its predecessors.

Fred
fred.l.templin@boeing.com

> -----Original Message-----
> From: Robin Whittle [mailto:rw@firstpr.com.au] 
> Sent: Tuesday, January 27, 2009 5:25 AM
> To: RRG
> Cc: lisp@ietf.org
> Subject: Re: [rrg] LISP PMTU - 2 methods in draft-farinacci-lisp-11
> 
> Short version:     Luigi suggests a method by which the ITR
>                    can perform PMTUD to an ETR without having
>                    to cache the original packet.  This requires
>                    three things to be done to achieve the goals
>                    without the most obvious DoS vulnerabilities:
> 
>                    1 - The intermediate router sends back at least
>                        16 bytes of original packet in the PTB -
>                        8 bytes more than RFC 1191 requires.
> 
>                    2 - It is acceptable for the system not to
>                        deliver the first "too long" packet.
> 
>                    3 - The sending host sends a second "too long"
>                        packet after the ITR has received and
>                        processed the PTB from the intermediate
>                        router.
> 
>                    If the system is supposed to work without the
>                    PTB check requiring the LISP nonce in the PTB's
>                    original packet fragment, then I think the ITR
>                    still needs to store some details of recently
>                    sent packets, to force the attacker to set some
>                    other parts of the PTB's original packet fragment
>                    to hard-to-guess actual values of packets sent.
> 
>                    I modify my critique of LISP accordingly - this
>                    looks like a reasonable way to do PMTUD without
>                    the ITR maintaining a lot of state.  However the
>                    smallest amount of state would be the LISP
>                    nonce of recently sent packets and this requires
>                    all intermediate routers which might have an
>                    MTU problem to send back more than the RFC 1191
>                    minimum of 8 bytes.
> 
>                    The process of checking PTBs in a busy ITR could
>                    become so expensive (due to the large number of
>                    LISP nonces or other details to be checked, of
>                    recently sent packets) that it could become a DoS
>                    vulnerability in itself.
> 
>                    How I think an off-path attacker could find the
>                    addresses of some, many or most ITRs which are
>                    tunneling packets to some ETR the attacker wants
>                    to DoS.
> 
>                    An ITR occasionally needs to allow longer packets
>                    to the ETR than its current MTU setting allows -
>                    otherwise it has no way of adapting to an
>                    increased actual path MTU.
> 
> 
> Hi Luigi,
> 
> Thanks for your reply, in which you wrote:
> 
> > As a member of the OpenLISP team, let me say that we do not
> > *accept* or *reject* anything.  AFAICT, that is left to the
> > community and to the (future) LISP WG.
> 
> OK - "rejected" was my way of stating that you didn't find the
> stateless approach suitable for OpenLISP:
> 
> http://tools.ietf.org/html/draft-iannone-openlisp-implementati
> on-01#section-6.8.1
> 
>    6.8.1. OpenLISP local MTU Management
> 
>    During preliminary tests, we observed that the MTU issue is at the
>    origin of many problems.  OpenLISP does not (and will not)
>    implement the fragmentation mechanism proposed in Sec. 5.4 of
>    [I-D.farinacci-lisp].  The reason is because the proposed method
>    sounds very primitive and does not appear to be efficient.  The
>    original LISP specification is based on an architectural constant
>    used by the xTR to limit the MTU of LISP encapsulated packets.
>    OpenLISP uses a more advanced solution, based on the real MTU of
>    the local RLOCs present on the xTR, as described below.
> 
> 
> > What we proposed is just an alternative approach that takes 
> advantage of
> > ICMP messages (if they are present).
> 
> OK - your approach makes sense.  I am reading it now.
> 
> 
> >> Stateful approach for all packets
> >> ---------------------------------
> >>
> >> I am reading the LISP version - I have not looked in detail at the
> >> OpenLISP source of this approach.
> >>
> >> This makes no reference to IPv4 DF=0 packets.  So this approach of
> >> the ITR sending a PTB packet to the sending host when a DF=0 packet
> >> exceeds some length is not going to result in any action 
> on the part
> >> of the sending host.  Such a DF=0 packet will be dropped 
> by the ITR.
> >>  That may be OK - Ivip will do much the same - but it needs to be
> >> specified clearly.
> >   
> > The text that we provided is just a first cut. I agree that 
> there are
> > several points to clarify.
> 
> OK.
> 
> >> This approach of determining the MTU to each ITR by receiving ICMP
> >> messages from an intermediate router needs to be done securely.
> >   
> > Am I wrong if I say that this means to change the ICMP protocol?
> 
> I meant securely enough to prevent spoofing by an off-path attacker
> intent on DoS.  (Full description below.)
> 
> The LISP nonce should do the trick - but that requires the
> intermediate router to send back to the ITR, in the PTB message, the
> 8 byte LISP header after the UDP header.  RFC 1191 only requires it
> to send back the outer IP header and the next 8 bytes - which in a
> LISP packet is the UDP header.
> 
> This was a pretty short-sighted requirement, I think.  I don't know
> how DFZ routers behave, but I recall someone (Bill Herrin?) stating
> some months ago that it was common to send back more bytes than the
> bare minimum of 8.  If LISP or something similar was implemented in 5
> years time, I guess it wouldn't be too much to ask the router
> manufacturers to create firmware updates if their routers don't
> already send back a decent number of bytes such as 32 or whatever.
> 
> Without this, the ITR can't "securely" respond to ICMP PTB messages.
> 
> > Our goal was not to introduce new mechanisms in the core, 
> but rather to
> > take advantage of what exists.
> 
> OK.
> 
> >> It requires the ITR to cache significant amounts of information for
> >> every packet it sends which might trigger such a PTB.
> >   
> > Why should the ITR cache information?
> 
> Skip the following if you like:
> 
>     My understanding of what ITRs would have to do, before I read the
>     rest of your message:
> 
>     For every encapsulated packet the ITR sends which might generate
>     a PTB message in some router en-route to the ETR, the ITR needs
>     to cache - I mean store for a few seconds - the start of the
>     original packet and the nonce it put in the LISP header of the
>     encapsulating header.   I guess the ITR needs to store it for a
>     few seconds, since it might take that long for the PTB to come
>     back.  Technically, maybe it should hold it for longer, but my
>     guess is that 2 seconds should do the trick.
> 
>     Then, when a PTB arrives, the ITR needs to compare the LISP nonce
>     in the PTB's fragment of the initial packet (see discussion above
>     about how this requires more bytes than RFC 1191 requires) with
>     its cached information about recently sent packets.  It should
>     also check other things such as the destination address in the
>     packet fragment, to ensure it is the same as the ETR to which it
>     tunnelled the packet.  This will enable the ITR to uniquely
>     identify one of the packets it recently sent.  Then it can adjust
>     for that ETR its record of path MTU, and generate a PTB packet to
>     be sent to the sending host, from its cached fragment of the
>     start of the original packet.
> 
>     After that, the ITR can use the stored value of MTU for that ETR
>     and use it to decide whether to accept or reject with a PTB any
>     packet to be tunneled to that ETR.
> 
> I don't think your I-D doesn't mention this, but the ITR also needs
> to occasionally let a longer packet be encapsulated to this ETR - a
> packet long enough that once encapsulated it would exceed the ITR's
> current notion of path MTU to this ETR.  This will only occur if and
> when one of the following occur:
> 
>   1 - The original sending host, in the same communication session
>       tries its luck with a longer packet for the same reason.  RFC
>       1191 specifies the one sending host should not try a longer
>       packet to a given destination address for 10 minutes after
>       receiving a PTB.
> 
>   2 - Some other sending host sending a longer packet through this
>       ITR to an EID address which is mapped to the same ETR.
> 
>   3 - The same sending host, in the same or another application,
>       sending a long packet to a different destination address,
>       which may or may not be in the same EID as the first
>       destination address, which is mapped to the same ETR.
> 
> Then, if the longer packet does not result in a PTB, the ITR should
> probably raise its notion of the MTU to that ETR accordingly.
> 
> However, packet loss here (loss of the too long packet before the
> intermediate router with the limiting MTU, or loss of the PTB message
> from that router) could result in a too-long MTU setting in the ITR.
> This is not such a problem, since it would probably soon be corrected
> if subsequent packets passed through the ITR due to this too-high
> value and did result in a PTB being received by the ITR.
> 
> The Ivip approach can use PTBs from intermediate routers, but does
> not rely on them absolutely.  It uses positive and negative
> acknowledgement from the ETR for a small subset of packets which,
> once encapsulated, are of a length which falls within the ITR's "zone
> of uncertainty" for the path MTU to this ETR.  This zone is reduced
> by every such packet and would, in general, quickly diminish to zero
> - after which the technique is only needed occasionally to test
> whether the MTU limit has risen.
> 
> I think would be best to store the path MTU value in a separate body
> of data from however you store the mapping information.  The mapping
> information is indexed on EID, I assume.  You might have in the
> mapping cache thousands of entries which all use the same ETR.  It
> makes no sense to store the ETR's path MTU in every one of those
> entries.  I think the encapsulation process needs to check the path
> MTU to the ETR after it has determined which ETR address to tunnel
> each packet to.
> 
> 
> >> The intermediate router would need to send back sufficient of the
> >> original packet to ITR to include the LISP nonce.  Otherwise, PTBs
> >> spoofed by off-path attackers would be accepted and the 
> whole system
> >> could easily be DoSed.
> >   
> > Probably there is a DoS risk, but IMO is from on-path 
> attackers. How can
> > an off-path attacker know that a specific ITR is sending 
> packets to a
> > specific ETR and send a fake ICMP message to shrink the MTU 
> toward that
> > specific ETR?
> 
> It is easy to find out where the ITRs of a particular ISP or end-user
> network are.  Attackers could discover this by various means, but
> here is one:  They get their own EID space, which is mapped to an
> RLOC address of one of their own machines - which pretends to be, or
> is, an ETR.  Then, the attacker sends to some host in the ISP or
> end-user network a ping packet or any other packet which will elicit
> a response.  That packet has a source address in the attacker's EID
> range, so the targeted host will send back a response to that
> address.  The ITR in the targeted site will look up the mapping for
> the attacker's EID address and so tunnel the response packet to the
> attacker's "ETR".  With LISP, APT and TRRP, the encapsulation outer
> header's source address is that of the ITR, so the attacker's "ETR"
> learns the address of the ITR.  (With Ivip, the source address is
> that of the sending host.)
> 
> So attackers can easily find the address of an ITR in some network of
> its choice where there are sending hosts.  It could do this en-masse
> and so discover the addresses of ITRs in many such networks.
> 
> The attacker presumably has some idea of where the sending hosts are
> for the destination network it wants to DoS.
> 
> The attacker could find the addresses of Proxy Tunnel Routers which
> handle the attacker's EID.  The attacker simply send packets from one
> of its own EID addresses to random IP addresses to get responses from
> a bunch of hosts, many of which will use a PTR (all those which don't
> have an ITR in their own network).  If there were a single set of
> PTRs which handled every EID, then this would suffice to locate all
> PTRs in the world.
> 
> However, at least in the Ivip model, there probably won't be OITRDs
> (the Ivip version of LISP's PTR) which handle every micronet.  There
> seems to be no business plan for LISP PTRs, so I can't say how they
> would be organised.  Assuming that there is one set of PTRs for one
> subset of the EID address space, and another set for another subset,
> then the above method will only allow the attacker to discover the
> PTRs which handle its subset.
> 
> I can't easily think of a way an off-path attacker could find the
> addresses of the PTRs which handle the EID space of some network
> which the attacker wants to DoS.  Nonetheless, attackers in general
> could figure out the addresses of PTRs in various PTR networks and
> share this information between themselves.
> 
> So an attacker could find the addresses of some, many or most ITRs
> which might be tunneling packets to the site they want to DoS.
> 
> The attacker presumably has a motivation to DoS a particular ETR.  If
> the attacker wants to DoS the ETR(s) of a particular organisation, it
> can easily look up the mapping for that organisation's EID prefix to
> obtain the ETR addresses.
> 
> With the ETR address and a list of ITR addresses, the attacker can
> inexpensively generate a sequence of spoofed PTB packets.  (But see
> discussion below on how much information the ITR needs to store about
> recently sent packets, to force the attacker to correctly set length,
> checksum and (IPv4 only) Identification bits to match a packet
> actually sent, which the attacker, being off-path, can't see.
> 
> Each such spoofed PTB, if recognised by the ITR, can be used to
> clobber the MTU the ITR perceives for the targeted ETR, so causing
> significant and reasonably persistent DoS for a potentially large
> number of sending hosts which rely on that ITR - and a potentially
> large number of destination hosts in potentially multiple destination
> networks which rely on this ETR.
> 
> If the ITR requires the LISP nonce to be in the PTB fragment, then
> the system is secure against such spoofing, but then this PMTUD
> system will only work if all the intermediate routers which might
> cause an MTU problem send back at least 16 bytes rather than the RFC
> 1191 minimum of 8 bytes after the IP header.
> 
> 
> >> The ITR needs to store an initial fragment of each incoming traffic
> >> packet for some time, so it can generate a PTB message for the
> >> sending host.  It can't rely on enough of the original 
> packet coming
> >> back in the PTB from the intermediate router.  The ITR 
> needs to cache
> >> this for a second or two at least - while it waits for a possible
> >> PTB.  This is an onerous requirement in a high-volume ITR.
> >   
> > No. This is not the case.
> > Assume the following topology:
> > 
> > H1-----------ITR1-----<DFZ>----------ETR2-----------H2
> > 
> > where host H1 send packets to host H2.  If a first packets 
> triggers a
> > ICMP PTB in the DFZ, this is sent back to ITR1, which sjust 
> stores the
> > fact that to reach ETR2 a smaller MTU must be used. Nothing 
> is sent back
> > to H1.
> 
> But that involves data loss.  The Ivip approach is intended to avoid
> this.
> 
> > H1 sends a second packet. On the ITR1 there will be a check 
> on the MTU
> > triggering a second ICMP PTB to be sent back to H1.
> 
> Ahh . . . OK, you can make it work this way if you accept data loss
> on the first large packet, expecting the sending host to generate
> another similarly large packet, which seems reasonable.
> 
> I don't think this technique can be used with Ivip, but I will
> consider it when I write the PMTUD I-D.
> 
> I withdraw my critique of LISP's stateful approach to PMTUD requiring
> storage of the initial part of longer packets for a few seconds.
> However, I think the text of draft-farinacci-lisp and your own
> OpenLISP I-D should be revised to make this process clearer.
> 
> Still, if you are to check the nonce, you do need to store each nonce
> of recently sent packets.
> 
> To do a proper check of the PTB, you need to store some packet
> details - to force the attacker to generate the correct
> Identification (IPv4 only) and Length bits from the IP header.
> 
> Likewise, if you store the UDP checksum of recently sent packets,
> then you can force the attacker to get that right, which would be
> generally impossible except by lots of attempts for data packets.  It
> would be easier to spoof the checksum and length of TCP SYN packets
> or some other commonly used short packets.  To protect against that,
> your ITR would need to store the length of such (generally short)
> packets and make sure the potentially spoofed PTB message's MTU limit
> was not longer than the actual packet.  This, combined with some
> general limit on how low you would accept the MTU to be according to
> any PTB, would probably make the system immune to this kind of attack.
> 
> 
> Also, I think you need to either check the LISP nonce (and accept the
> system will fail if the PTB original packet fragment doesn't contain
> it) or not expect it and so recognise that the system is open to a
> powerful DoS attack if you don't store a bunch of details of recent
> packets, and use them to carefully check all PTBs.
> 
> This PTB checking process itself could represent a DoS vulnerability
> for a busy ITR.  If it has a lot of details of packets recently sent
> - potentially hundreds of thousands or millions, I guess, and you are
> not requiring LISP nonces, then you still have to search through some
> long and constantly changing lists of packet details such as length,
> UDP checksum (IPv4 only) Identification etc.  for every PTB received.
> 
> This could easily get way out of hand - those cached lists of recent
> packet details are expensive enough to add to and clean out, and I
> guess they can't inexpensively be optimised for inexpensive searching
> to see which one matches a PTB.
> 
> PTB messages are pretty short (inexpensive for the attacker to send)
> and could chew up a lot of ITR CPU power to process.  Checking only a
> fraction of these PTBs (in order to limit the CPU time spent chewing
> through a flood of spoofed PTBs) would slow down the ITR's ability to
> adapt properly to actual MTU problems.
> 
> 
> > So, you need two big packets in order to make the feedback reach the
> > original sender, but the ITR does not need to store packets.
> > 
> > Hope this clearer now.
> 
> Yes - thanks.
> 
>   - Robin
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> http://www.irtf.org/mailman/listinfo/rrg
> 
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Tue Jan 27 09:59:59 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3D1093A6B85; Tue, 27 Jan 2009 09:59:59 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 18CD43A6B85 for <rrg@core3.amsl.com>; Tue, 27 Jan 2009 09:59:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.535
X-Spam-Level: 
X-Spam-Status: No, score=-6.535 tagged_above=-999 required=5 tests=[AWL=0.064,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vWYjqdUBbhmk for <rrg@core3.amsl.com>; Tue, 27 Jan 2009 09:59:58 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 032A13A6B84 for <rrg@irtf.org>; Tue, 27 Jan 2009 09:59:58 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,333,1231113600"; d="scan'208";a="134132309"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-1.cisco.com with ESMTP; 27 Jan 2009 17:58:40 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n0RHweG0026894;  Tue, 27 Jan 2009 09:58:40 -0800
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n0RHwVDj017851; Tue, 27 Jan 2009 17:58:40 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Tue, 27 Jan 2009 12:58:33 -0500
Received: from cisco.com ([10.86.245.114]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 27 Jan 2009 12:58:32 -0500
Date: Tue, 27 Jan 2009 12:58:29 -0500
From: Scott Brim <swb@employees.org>
To: Benson Schliesser <bensons@queuefull.net>
Message-ID: <20090127175829.GL39727@cisco.com>
Mail-Followup-To: Scott Brim <swb@employees.org>, Benson Schliesser <bensons@queuefull.net>, lisp@ietf.org, routing-discussion@ietf.org, rrg@irtf.org, David Meyer <dmm@1-4-5.net>, John Zwiebel <jzwiebel@cisco.com>
References: <9b942cbb0901251306h5cf184dbob1e672fce4b31dc2@mail.gmail.com> <20090125212608.GA12742@1-4-5.net> <9b942cbb0901251349g105c86d9m98c54ba1b5596ec0@mail.gmail.com> <FE47C611-5A41-44D5-8BDE-E531BFAEA902@cisco.com> <9b942cbb0901251553u710be191s1dc960c4dd150ac8@mail.gmail.com> <9b942cbb0901251306h5cf184dbob1e672fce4b31dc2@mail.gmail.com> <20090125212608.GA12742@1-4-5.net> <9b942cbb0901251349g105c86d9m98c54ba1b5596ec0@mail.gmail.com> <9b942cbb0901251306h5cf184dbob1e672fce4b31dc2@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <9b942cbb0901251553u710be191s1dc960c4dd150ac8@mail.gmail.com> <9b942cbb0901251349g105c86d9m98c54ba1b5596ec0@mail.gmail.com> <9b942cbb0901251306h5cf184dbob1e672fce4b31dc2@mail.gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-OriginalArrivalTime: 27 Jan 2009 17:58:32.0888 (UTC) FILETIME=[DE47D380:01C980A8]
Authentication-Results: sj-dkim-3; header.From=swb@employees.org; dkim=neutral
Cc: John Zwiebel <jzwiebel@cisco.com>, rrg@irtf.org, lisp@ietf.org, routing-discussion@ietf.org
Subject: Re: [rrg] [lisp] Economic issues of long-path / stretched routing
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

I don't know which of the lists this is going to should be trimmed, or
I would gladly do so.

Excerpts from Benson Schliesser on Sun, Jan 25, 2009 05:53:49PM -0600:
> My single-homed xTR (savvis) has one ALT peer right now (asp) and he
> announces an aggregate net that covers my EID prefix. That's great
> from a routing scale perspective. However if I were to multihome to
> another net (dmm, for example) wouldn't I have to announce my EID
> into the ALT via that path if I wanted to continue serving that EID
> during an outage of my primary (asp) connectivity?

You peer with your upstream ALT routers based on prefixes they are
responsible for, and where the ALT routers are doesn't (necessarily)
follow physical topology.  For any prefix there will probably be more
than one upstream ALT router.  Yes, you announce your prefix to all
upstream ALT routers responsible for the shorter including prefix.
Table size should be minimal, depending on how things are configured
in your neighborhood.  It could just be default from each.  At most it
would be a set of highest-level prefixes, maybe some special ones, and
some longer ones for local efficiency.  

> At the very least it has to be announced such that my primary
> upstream sees it and can divert map-requests to my secondary path.
> So do all of my xTRs need to have ALT tunnels to all of my EID
> allocators in order to avoid de-aggregation in the ALT tables while
> maintaining fault tolerant connectivity? What happens if an AS-wide
> fault takes down all of my allocator's ALT routers? I understand
> that my RLOCs are still aggregated by the underlying network's
> routing regardless.

Allocation is decoupled from ALT routers.  RIRs may run high-level ALT
routers but there may be intermediate ones too.  For a particular
prefix there should be multiple redundant ALT routers.  For the most
part they need to be within the region in which they are most used,
even though some prefixes may be allocated and then move to completely
different continents.

> It would be good to discuss what all of this looks like for network
> engineering purposes. For instance from the perspective of ALT traffic
> engineering, an end-site xTR with end users surfing the web will probably
> have a moderate collection of EID mappings that stay refreshed (Google,
> Twitter, corp intranet, etc) and a small collection of mappings that get
> used and expire (my blog, which nobody reads twice). This is different from
> an xTR in front of a public website, which will basically build a huge
> collection of mappings and have to worry more about the database size than
> anything else.

Right.  The range in possible tactics is huge, and they all work as
long as they speak the same protocol.  

Scott
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Tue Jan 27 15:57:07 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 86BFE3A68CD; Tue, 27 Jan 2009 15:57:07 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 47DE73A68CD for <rrg@core3.amsl.com>; Tue, 27 Jan 2009 15:57:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BJ0YDX7SeZ4s for <rrg@core3.amsl.com>; Tue, 27 Jan 2009 15:57:05 -0800 (PST)
Received: from aunswsmtp6.maginet.net (aunswsmtp6.maginet.net [218.185.67.148]) by core3.amsl.com (Postfix) with ESMTP id 597473A67EF for <rrg@irtf.org>; Tue, 27 Jan 2009 15:57:05 -0800 (PST)
Received: (qmail 23125 invoked by uid 89); 27 Jan 2009 23:50:00 -0000
Received: from unknown (HELO ?10.65.160.140?) (rjainet@119.73.251.195) by aunswsmtp6.docomointertouch.net with ESMTPA; 27 Jan 2009 23:50:00 -0000
Message-Id: <1F501131-8AF5-49AA-8E6B-0AEC425921FB@extremenetworks.com>
From: RJ Atkinson <rja@extremenetworks.com>
To: IRTF Routing RG <rrg@irtf.org>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Tue, 27 Jan 2009 18:49:59 -0500
X-Mailer: Apple Mail (2.930.3)
Subject: [rrg] paper on DNS-based mobility
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Folks might find this paper from the IEEE London Communications
Symposium (way back in 2002) interesting.

<http://www.ee.ucl.ac.uk/lcs/papers2002/LCS072.pdf>

Cheers,

Ran Atkinson
rja@extremenetworks.com

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Wed Jan 28 05:16:27 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6A0B528C272; Wed, 28 Jan 2009 05:16:27 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8FD7D28C276 for <rrg@core3.amsl.com>; Wed, 28 Jan 2009 05:16:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.509
X-Spam-Level: 
X-Spam-Status: No, score=-6.509 tagged_above=-999 required=5 tests=[AWL=0.090,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GjHaEp-MewUY for <rrg@core3.amsl.com>; Wed, 28 Jan 2009 05:16:26 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 1471D28C1D2 for <rrg@irtf.org>; Wed, 28 Jan 2009 05:16:02 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,338,1231113600"; d="scan'208";a="126424202"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-2.cisco.com with ESMTP; 28 Jan 2009 13:14:44 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n0SDEiPc018717;  Wed, 28 Jan 2009 05:14:44 -0800
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n0SDEiU9010801; Wed, 28 Jan 2009 13:14:44 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 28 Jan 2009 05:14:44 -0800
Received: from [10.31.245.108] ([10.21.84.68]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 28 Jan 2009 05:14:43 -0800
Message-Id: <1358FE71-B2B7-484B-9915-86CE35985C66@cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: Scott Brim <swb@employees.org>
In-Reply-To: <20090127175829.GL39727@cisco.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Wed, 28 Jan 2009 05:14:41 -0800
References: <9b942cbb0901251306h5cf184dbob1e672fce4b31dc2@mail.gmail.com> <20090125212608.GA12742@1-4-5.net> <9b942cbb0901251349g105c86d9m98c54ba1b5596ec0@mail.gmail.com> <FE47C611-5A41-44D5-8BDE-E531BFAEA902@cisco.com> <9b942cbb0901251553u710be191s1dc960c4dd150ac8@mail.gmail.com> <9b942cbb0901251306h5cf184dbob1e672fce4b31dc2@mail.gmail.com> <20090125212608.GA12742@1-4-5.net> <9b942cbb0901251349g105c86d9m98c54ba1b5596ec0@mail.gmail.com> <9b942cbb0901251306h5cf184dbob1e672fce4b31dc2@mail.gmail.com> <20090127175829.GL39727@cisco.com>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 28 Jan 2009 13:14:43.0538 (UTC) FILETIME=[6268FB20:01C9814A]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=911; t=1233148484; x=1234012484; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dino@cisco.com; z=From:=20Dino=20Farinacci=20<dino@cisco.com> |Subject:=20Re=3A=20[lisp]=20Economic=20issues=20of=20long- path=20/=20stretched=20routing |Sender:=20; bh=kjjbTHGHMsF3J7m9Du18LrECg9vknpmUZPqb5D3dRec=; b=VeEonZ4l0TwN04cLurIJ+IvYMaWcbPyfymc7gPw4V5zH0aHIQpzSP6SGUR ZfWq5tariMugz1TDtQT83O6hpu9tIW8B7OS5cUKhQ/uGsGI7GOGaFtr19oK2 KawOAxQjVr;
Authentication-Results: sj-dkim-3; header.From=dino@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); 
Cc: rrg@irtf.org, lisp@ietf.org, routing-discussion@ietf.org
Subject: Re: [rrg] [lisp] Economic issues of long-path / stretched routing
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

> You peer with your upstream ALT routers based on prefixes they are
> responsible for, and where the ALT routers are doesn't (necessarily)
> follow physical topology.  For any prefix there will probably be more
> than one upstream ALT router.  Yes, you announce your prefix to all
> upstream ALT routers responsible for the shorter including prefix.
> Table size should be minimal, depending on how things are configured
> in your neighborhood.  It could just be default from each.  At most it
> would be a set of highest-level prefixes, maybe some special ones, and
> some longer ones for local efficiency.

And your neighborhood really doesn't need back-doors so we can keep  
the ALT hierarchical by shaping it as an acyclic tree and not a mesh  
of trees or a mess of links connecting up and down at *different*  
hierarchical levels like the underlying Internet is configured today.

Dino

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Wed Jan 28 08:37:59 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7DBE43A6B2A; Wed, 28 Jan 2009 08:37:59 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 90C2B3A6B2A; Wed, 28 Jan 2009 08:37:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.478
X-Spam-Level: 
X-Spam-Status: No, score=-4.478 tagged_above=-999 required=5 tests=[AWL=-1.823, BAYES_00=-2.599, FB_INCREASE_VOL=3.629, RCVD_IN_DNSWL_MED=-4, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mzEdYBuKrraV; Wed, 28 Jan 2009 08:37:54 -0800 (PST)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id 61EB33A6A26; Wed, 28 Jan 2009 08:37:54 -0800 (PST)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231]) by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n0SGbM3J018341 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 28 Jan 2009 08:37:26 -0800 (PST)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n0SGbLKO015547; Wed, 28 Jan 2009 08:37:21 -0800 (PST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n0SGbKon015447; Wed, 28 Jan 2009 08:37:21 -0800 (PST)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 28 Jan 2009 08:37:21 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 28 Jan 2009 08:37:20 -0800
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1057DFFA6@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <497EB510.8060100@firstpr.com.au>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Int-area] [rrg] Please respond: Questions from the IESG as towhether a WG forming BOF is necessary for LISP
Thread-Index: AcmBHC/P3HfVxvCKT8OfMQi2cQGTfgARvXEA
References: <20090120190744.GA9467@1-4-5.net>	<49765FFB.1010709@piuha.net>	<200901222339.n0MNddM88868@magenta.juniper.net>	<75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com>	<497B1F7A.9030407@firstpr.com.au><6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com> <497EB510.8060100@firstpr.com.au>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Robin Whittle" <rw@firstpr.com.au>, "RRG" <rrg@irtf.org>
X-OriginalArrivalTime: 28 Jan 2009 16:37:21.0517 (UTC) FILETIME=[B12159D0:01C98166]
Cc: int-area@ietf.org, lisp@ietf.org, routing-discussion@ietf.org
Subject: Re: [rrg] [Int-area] Please respond: Questions from the IESG as towhether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Robin, 

> -----Original Message-----
> From: Robin Whittle [mailto:rw@firstpr.com.au] 
> Sent: Monday, January 26, 2009 11:18 PM
> To: RRG
> Cc: routing-discussion@ietf.org; int-area@ietf.org; 
> lisp@ietf.org; Dino Farinacci
> Subject: Re: [Int-area] [rrg] Please respond: Questions from 
> the IESG as towhether a WG forming BOF is necessary for LISP
> 
> Short version:   Responding to Dino's reply to my critiques of LISP.
> 
>                  The LISP team should do detailed critiques of APT
>                  and Ivip as part of convincing IETF folks of the
>                  merits of LISP-ALT.
> 
>                  Will it be possible to do firmware upgrades so all
>                  DFZ routers ca. 2014 will handle packets with
>                  modified IPv4 and IPv6 headers, to forward the
>                  packets the ISP network of the ETR, without
>                  encapsulation, its overheads and PMTUD problems?
> 
>                  If so, then maybe we could go straight to this
>                  approach and forget about encapsulation and all
>                  its complexities.
> 
> 
> Hi Dino,
> 
> Thanks for your reply:
> 
> > Sorry for the long email,
> 
> We are attempting to re-engineer one of humanity's most excellent and
> important communication networks.  Long detailed messages are often
> appropriate.
> 
> 
> >>   LISP has too many fundamental problems to be considered a
> >>   potentially practical solution.  Some of these problems require
> >
> > LISP is not perfect and still evolving but let me point out that
> > every design has fundamental problems. At this scale, it's very
> > hard to be perfect Robin. And as Noel has stated so many times, the
> > hard decisions must be made to incrementally deploy this. So things
> > might not look pretty on the surface, but jeez, you got to do what
> > you got to do. Else, this will all be academic.
> 
> I wasn't suggesting a proposal should be perfect.  I pointed out
> problems which I consider to be fundamental - not "on the surface".
> Some can be fixed by adding new design elements, but I think the
> others are only fixable by radically altering the current design.
> 
> I stand corrected about LISP's approach to PMTUD - the latest draft
> does include an outline of a workable solution.

I don't know if you were fishing for a response, but the
stateful solution outlined in the latest LISP draft still
has problems. It should also be mentioned that the approach
(drop first; return PTBs for subsequent) is not new and
has been proposed many times over the years.

The approach in the current LISP draft still relies on ICMPs
coming from anonymous network middleboxes (which Dino himself
has said that we cannot depend on), and provides insufficient
means for authenticating any ICMPs that may come. For example,
even if the ICMPs were delivered, and even if they included
the LISP nonce, it would be impractical for the ITR to cache
enough nonces of enough recently-sent packets especially at
high data rates. So, the only option is to ignore ICMPs
(leads to black holes) or honor ICMPs (leads to denial
of large packet service).

I have said this before, but AFAICT DF=1 is busted.

Fred
fred.l.templin@boeing.com 


> > We really want to solve this problem, sincerely. This is not lip
> > service, we are not just writing papers, we want to rev the
> > Internet, this is serious.
> 
> I have always known you and the other LISP folks really care for the
> Net and are working hard to devise the best possible improvements.
> 
> Despite it only having had broad-based commercial, political and
> inter-personal impact in the last 15 years, the Internet is a
> momentous development in human relations.  We all want to see changes
> which will enable it to remain technically viable - and hopefully
> elegant - for the long-term future.
> 
> However, I think you jumped straight into some seemingly attractive
> approaches which turn out to have problems I consider to be serious.
> 
> It seems that you and the APT folks thought for a few moments about a
> real-time mapping system and figured it was out of the question.  I
> think it is not at all out of the question - and when you have
> real-time mapping distribution, you can do some elegant and valuable
> things:
> 
> 1 - Separate out reachability testing and ETR choice mechanisms and
>     let (actually require) the end-user networks to do it themselves
>     - or pay someone else to do it for them.
> 
> 2 - Enable the end-user networks to do real-time incoming TE control.
> 
> 3 - Send the mapping update stream to local query servers, so there
>     is reliable and very fast responses to mapping requests - and
>     therefore no need to delay or drop initial packets.
> 
> 4 - Charge a small fee per update to pay for most of the mapping
>     distribution system.
> 
> 5 - Provide much better support for the TTR approach to mobility:
> 
>       http://www.firstpr.com.au/ip/ivip/TTR-Mobility.pdf
> 
> I think the ALT system is a lot niftier than CONS, but still, you are
> delaying initial packets (APT and Ivip are not), forcing every ITR to
> do its own reachability testing and monolithically integrating those
> testing and ETR choice mechanisms into the core-edge separation
> scheme itself.
> 
> I don't think we should be rushed into thinking we can't possibly
> have local full-database query servers in ISPs and larger end-user
> networks, or that it is impossible to push the mapping to them in a
> few seconds (real-time).  One advantage of the real-time approach
> over LISP-ALT, APT's approach or the TRRP DNS-like global query
> server approach is that it is streamlined and includes multiple
> mapping changes (dozens or perhaps a hundred IPv4 mapping changes) in
> a single packet.
> 
> 
> > I want to address each of your 7 points below. I have cc'ed the
> > lisp@ietf.org mailing list so the folks who want to focus 
> on details of
> > LISP can see this thread.
> 
> OK, we are also transmitting to routing-discussion@ietf.org and
> int-area@ietf.org .
> 
> 
> >> 1 - Delays in delivering initial packets in a flow.  This is either
> >>    due to sending the packets along the ALT network (which takes
> >>    time and involves sending substantial volumes of data packets
> >>    over the ALT network, rather than just mapping requests) or to
> >>    sending mapping requests only, and waiting for the ITR to get a
> >>    response before it attempts to send traffic packets.
> > 
> > We have a memory/bandwidth tradeoff. So we have to make a 
> hard design
> > call. I'd rather have mappings cached and timed out so they can be
> > updated when they need to then to hold all the possible 
> mappings for the
> > Internet in an ITR.
> > 
> > There is no such thing of a free lunch. You either store 
> all possible
> > mappings or you fetch them when you need them.
> 
> That is the dichotomy between LISP-CONS/ALT and LISP-NERD.  However
> there is another approach (APT and Ivip): full push to local query
> servers.
> 
> RAM and hard drive space is very cheap.  The query servers don't need
> to be Cisco-style routers.  They can be COTS or high-reliability
> rack-mount PCs - with gigabytes of RAM and terabytes of hard disk
> storage.
> 
> In Ivip, IPv4 mapping consists of 12 bytes:
> 
>   Start of the micronet  (32 bits)
>   Length of the micronet (32 bits, but typically 16 or less)
>   ETR address            (32 bits)
> 
> So if you have a COTS server with 16GB of RAM (this will no-doubt be
> the common amount of RAM in PCs by the time a core-edge separation
> scheme is deployed) then you can easily dedicate 12GB for mapping
> information.  That is a billion micronets (more or less, depending on
> the storage format), which will do the trick for many years to come.
>  (IPv6 mapping is more bloated, but there is a longer time-frame for
> implementing millions or billions of IPv6 micronets - time for RAM to
> get cheaper still).
> 
> I think you - and the designers of APT and TRRP - have been somewhat
> captive to established ways of thinking about how to solve a
> "routing" problem: with more "routing" style structures.  This means
> more routers, more messages and replies zipping around the world etc.
>  It doesn't have to be like this.
> 
> I need to do more work on the fast-push system of Ivip - but you are
> welcome to critique it in its current form:
> 
>   http://tools.ietf.org/html/draft-whittle-ivip-db-fast-push-00
> 
> If your design choice with LISP is optimal, or the only one you think
> is available, then you should be able to point out why it is
> impractical or undesirable to use an approach such as Ivip's:
> real-time fast push on a global basis to local query servers, with
> local pull from there to ITRs, followed by pushed updates from the
> query server to the ITRs if a micronet's mapping changes within the
> caching time of the mapping reply.
> 
> Likewise, you presumably have a critique about the practicality or
> desirability of APT: slow push to local query servers (Default
> Mappers) in each ISP, local pull from ITRs querying the Default
> Mappers, local push of mapping updates from DMs to those ITRs which
> need it (I think) and (again, my recollection) the Default Mappers,
> rather than the ITRs, doing reachability testing and choosing which
> ITR address an ITR uses.
> 
> The Net will soon be delivering gigabytes of video data to homes, in
> near-real-time, for a few dollars.  Generally, a packet can be sent
> from any host to any other host in 0.2 seconds or less.
> 
> In this scenario, why do you think global push to local query servers
> - including high-speed, real-time push - is impractical or
> undesirable?
> 
> 
> >>    According to: http://www.lisp4.net/docs/lisp-ausnog02.ppt pp 10
> >>    & 11 the experimental LISP ALT network's ITRs drop initial
> >>    packets and send brief map request messages.   Even if we think
> >>    this delay doesn't matter, I am sure enough potential adopters
> >>    would - and therefore make it difficult or impossible 
> for LISP or
> >>    any other such solution to be widely enough adopted to solve the
> >>    routing scaling problem.
> > 
> > Then why was/is ARP deployed in a 10^4 host-based bridged 
> network with
> > basically the same properties. First packet loss is not 
> persistent when
> > you look at all the traffic that originates from a source site to
> > another destination site.
> 
> This doesn't apply to small end-user networks.  If there are to be
> hundreds of millions of these sites, meaning hundreds of millions of
> EIDs or (Ivip) micronets - then these are mainly going to be small
> "sites", such as home offices, or more likely mobile devices.  The
> initial packet delay will directly impact usability, since there may
> only be one human user at each such "site".
> 
> If many small "sites" use a common ITRs in a large ISP, there will be
> less trouble with this, since it will be more common for one site to
> generate a packet to some EID/micronet which the ITR has mapping
> from, due to another "site" sending a packet there too.  However, the
> frequent delay of initial packets (actually, it seems you are
> planning to drop all initial packets) will still be a problem.
> 
> If LISP is not meant to scale to a hundred million or a billion or
> whatever "sites", then by whatever same smaller target number of
> EIDs, micronets or whatever, this would make alternative approaches
> such as Ivip or APT even more immune from whatever scalability
> critiques you might make of them.
> 
> > The host vendors are probably thinking, if we do LISP in 
> the host, you
> > could wait to send your TCP SYN before the mapping is available. 
> 
> On IPv4, with most human-used hosts behind NAT, you can't put a LISP
> ITR in the sending host, because the map reply won't come back to the
> host.
> 
> In a scenario in which LISP is widely - ubiquitously - deployed, many
> DNS servers are going to be on EID space.  This means the ITR will
> often need to do a mapping lookup before it can send a DNS request.
> The sending host will be on EID space and so the DNS server's ITR
> will need to do a mapping lookup too before it can send the return
> packet.  This will suck to a high degree in the current arrangement
> where the DNS server sends a single packet.  The ITR of the DNS
> server will drop that packet and send a mapping request for the
> original sending host's EID.  Then, after a while, the sending host
> will realise it got no DNS response.  If it sends the same request to
> the same DNS server, it will get a response back quickly, since now,
> the DNS server's ITR has the sending host's mapping in its cache.
> 
> But what if the sending hosts does it it might reasonably do: send
> the request to a different DNS server?  Then the same pattern as
> above occurs again.
> 
> 
> > Guess
> > what, you don't send that TCP SYN before you get the DNS 
> Reply. ;-) I
> > wonder why? Well I'll spell it out. If a host needs an 
> address to make
> > the connection, we can say it also needs a locator to make 
> a connection.
> 
> So you are proposing that every DNS reply also include full LISP
> mapping for every one or more EIDs of the one or more IP addresses
> returned?  I doubt if that will always fit in one packet.
> 
> > The design choice of LISP *is to just change software in 
> CPE devices* to
> > get the feature of decoupling rather than changing all the 
> hosts at a
> > site. 
> 
> OK . . . LISP mutates again!   I have been following LISP intently
> since about March 2007 and I don't recall any mention of changes to
> hosts or to CPE - by which I guess you mean DSL, cable and fibre
> router/firewalls.
> 
> Do you propose putting the ITR function in the DSL
> modem-router-firewall?  That is not such a bad idea, since it has
> (presumably) a public IP address and so can receive the map reply
> message from the globally distant query server (in the case of LISP,
> the mapping queries are typically answered by the destination
> end-user network's ETR).
> 
> Ivip has the option for putting ITR functions in a sending host which
> has a public address, or in a device such as a
> DSL-modem-router-firewall.  It would not be out of the question to
> put an ITR function in the sending host behind NAT, but then the
> sending host would need to build a persistent tunnel through NAT to
> the one or more local query servers - in order to receive mapping
> updates from those query servers.  That is possible, but not part of
> the current plan.
> 
> > That's a huge deployment advantage.
> 
> I don't see any advantage in terms of deployment, since it involves
> changes to more and more equipment, including customer equipment.
> Ivip's ITFH (ITR Function in Host) is optional - if it is cheap and
> convenient to do this for servers or devices like DSL-routers, then
> by all means do so.  It only makes sense when the device is
> well-connected.  It would be a bad idea to put an ITR function in a
> host or router at the edge of the network connected by a slow,
> expensive or unreliable link such as a wireless link.
> 
> > So these CPE devices get packets before they have mappings.
> 
> OK - for instance, the ITR function is in a DSL-modem-router-firewall
> device.
> 
> > We don't even want to consider a host
> > to CPE router signaling protocol and all it's complexities 
> to solve this
> > and to keep the architecture pure, we don't want to snoop 
> on DNS, SIP,
> > or any other protocol that can give us a hint on where the 
> host is about
> > to send a packet.
> 
> I agree.
> 
> 
> > So the cost is *either* first packet loss or sending the 
> packet on the
> > ALT using it as a request for a mapping.
> 
> These are not the only choices.
> 
> Another choice is to using a different architecture with local query
> servers - as does APT and Ivip.   I think you have approached this
> without thinking widely enough about the alternative ways of doing
> things which are different from traditional approaches like routers
> and DNS.
> 
> If you send the packet on the ALT network (for the purposes of
> delivering it to the ETR ASAP, as well as to elicit a mapping reply
> from that ETR) then you are going to greatly increase the volume of
> traffic on the ALT network.  Many of these packets will be short -
> but what if someone sends a 1500 or 9000 byte packet?
> 
> If you don't send the packet via the ALT network, then you either
> drop it, or delay it until the mapping arrives.  But that could be
> longer than 0.5 or 1.0 seconds, considering how many ALT routers the
> mapping request packet needs to go through to get to the ETR, how
> these ALT routers could be all over the world, and how the ETR could
> be on the other side of the world anyway.  This is a lot slower than
> the current system which usually takes 0.2 seconds or less to
> delivers packet anywhere in the world.  (The round trip from
> Melbourne Australia to Latvia is about 400ms.)
> 
> 
> >> 2 - LISP-ALT's long-path problem
> >>      http://psg.com/lists/rrg/2008/msg01676.html
> >>      http://www.antd.nist.gov/~ksriram/strong_aggregation.png
> >>
> >>      [Fix? Another fundamental problem in the architecture.  Could
> >>       be partially solved by more meshiness, but that would greatly
> >>       increase the complexity of the network and so raise more
> >>       scaling problems.]
> > 
> > Well this I believe is a duplicate of 1 above. So it's not really
> > *another* problem.
> 
> In terms of delaying packets, I agree.  Do you agree the long-path
> critique is valid?
> 
> The long path involves more than delay.  It involves traffic flowing
> (often) all around the world due to the fact that the highly
> aggregated structure of the ALT network will frequently result in
> different levels of the ALT hierarchy of routers being distributed
> all around the globe, since the physical location of organisations
> who are responsible for various parts of the address space does not
> correlate very strongly with geography or the topology of the Net.
> 
> This is a traffic burden, particularly if you are sending initial
> packets on the ALT network for ASAP delivery to the ETR, rather than
> just map requests.  (However, Ivip involves pumping mapping
> information around the globe anyway, and if your ALT network only
> handles requests, not traffic packets, the actual volume of traffic
> should not be too much of a problem.)
> 
> Each operator of each ALT router needs to have a commercial
> relationship with those other ALT routers they connect with.
> Otherwise, why would they accept the traffic?  I haven't seen any
> business plan for the commercial relationships which pay for the ALT
> routers and their traffic.
> 
> Ivip's fast push system involves a charge per update, which will
> finance the construction and running costs of most of the fast-push
> system, which will be run collectively by the various RUAS (Root
> Update Authorisation System) companies, each of which generates the
> real-time mapping changes for multiple MABs (Mapped Address Blocks -
> BGP-advertised prefixes encompassing thousands, or hundreds of
> thousands of micronets).
> 
> 
> >> 3 - Problems creating a highly aggregated ALT network in order to
> >>    speed the flow of packets up and down the hierarchy, while also
> >>    making the network robust against the failure of its routers and
> >>    tunnels.  This has not been discussed much on the RRG, but it is
> >>    an obvious problem.
> > 
> > If we can do this with BGP, which we have decades of 
> existence proof why
> > can't we do this with a tunnel topology 1) where a tunnel 
> can be rehomed
> > much quicker and easily than physical links and boxes we 
> have to do with
> > today, allowing aggregation to occur at the edges of the 
> ALT network,
> > and 2) these tunnels stay up because there is robust 
> connectivity below
> > the tunnel level to keep them up, hence there will be less 
> route-flaps
> > for EID-prefixes.
> 
> I don't recall any prior mention of rapidly reconstructing tunnels to
> maintain the ALT topology.  I agree with your point 2 that the
> tunnels will be reasonably robust due to relying on existing
> connectivity which is generally ensured by BGP.
> 
> But what happens when two ALT routers loose their connection for a
> moment?  Do they try to set up one or more tunnels with the same role
> in the ALT topology as the one which just died?  This is your point
> 1.  It could get messy, but I guess it could be done, by using other
> interfaces which, for some reason (I guess) have connectivity while
> the interfaces used for the first tunnel don't.  But that is the sort
> of situation which I think BGP would naturally resolve, generally in
> a few seconds or less.
> 
> My concern is more about what happens if an ALT router dies.   In
> your highly aggregated hierarchy, a mid-level ALT router is a single
> point of failure for sending mapping requests to all the ETRs in the
> branch below this router and from all the ITRs in that branch to ETRs
> outside the branch.
> 
> When a mid-level router dies, you can't just re-establish tunnels -
> it is dead.  The routers below need to establish tunnels to another
> ALT router which can take the dead one's place.
> 
> How is this going to work?  Say one lower-level router finds it can't
> reach the mid-level router in question, it is going to assume the
> mid-level router is dead.  So the lower-level router tries to set up
> a tunnel to the one or more backups.  If it does so, either this
> won't work at all, or the next level up will have to adapt to the
> original mid-level router having routes for most of its patch of the
> ALT address space, but with the backup having the router for the
> smaller patch of space handled by the lower-level router which just
> made a tunnel to the backup mid-level router.
> 
> > I think it's the complete opposite of what you claim. I 
> think BGP will
> > be more stable and scalable then the underlying BGP. 
> 
> I assume you mean that the BGP of the ALT network, operating over
> tunnels, will be more stable than the BGP of the Internet.  This is
> your point 2, and I largely agree.  But what if an ALT router dies?
> 
> > Plus, what we
> > propose for the use-case of BGP uses quite a few features 
> of it. Recall
> > this is eBGP over GRE.
> > 
> > We have an infrastructure where we can 1) ping to see 
> liveness of nodes
> > on the ALT. We have traceroute to determine the path a 
> Map-Request takes
> > on the ALT. We can ping/traceroute "underneath" so we can see the
> > diameter of the tunnel. 
> 
> I don't understand "diameter" in this context.
> 
> > Not only do we have a solution but we use
> > existing rudimentary tools for management.
> > 
> > And the address allocation hierarchy can map this logical 
> ALT topology.
> > And if the Registries are involved in managing part of this 
> ALT network
> > (which we hope and think they will), we can keep this consistent
> > relationship.
> > 
> > Do you realize the goodness of this? It's huge Robin.
> 
> I am sure you can make the ALT network reasonably robust, at a cost
> of complexity and with a loss of the original attractive design goal:
> a very high degree of aggregation.
> 
> I imagine you can reduce the excessively long paths by collapsing the
> network as much as possible to reduce the number of levels a packet
> typically has to ascend and descend.  This will reduce the
> "long-path" problem significantly.  But then, each participating
> mid-level ALT router (there are fewer of them) covers a larger part
> of the address space, and my concerns above become more acute, when
> such a router fails or becomes really unreachable.
> 
> I imagine you can reduce the geographical scatter component of the
> long-path problem by centralizing the ALT routers geographically.
> However, that privileges some operators and creates costs and
> difficulties for others.
> 
> I still think it is fundamentally wrong to have a global query server
> network for any system like this, where waiting for mapping replies
> involves delaying or dropping traffic packets.
> 
> I think a much better solution is to push the mapping to local query
> servers in each ISP (APT and Ivip) - and into any larger end-user
> networks which want to run their own local query servers (Ivip) so
> their ITRs can get marginally faster, more reliable, responses than
> by using the query servers of their ISPs.
> 
> 
> > There's more too, you then throw SIDR in the mix and we 
> have secured the
> > ALT, we have secured mappings, we created a PKI for routing use. In
> > fact, the first SIDR deployment could happen on the ALT to be
> > verified/experimented before it goes on the underlying BGP.
> 
> PKI is a great idea, but I think most people believe it is highly
> desirable to find solutions which do not require it.
> 
> 
> > And note, that the infrastructure will/does carry exactly 2
> > address-families. So we can do 6-to-6-over-4 with this 
> approach. That
> > means we can get two site to be *IPv6-only* and be able to 
> talk to each
> > other.
> > 
> > If you are a IPv6-only site now or a dual-stack site, you 
> could talk to
> > the new IPv6 Google services. I think this is a pretty huge feature.
> > 
> > This is clean and architecturally pure, no double NATs, no 
> CGNS, and no
> > applications breaking.
> 
> Are you discussing just the mapping queries going over the ALT
> network?  Or are you discussing the use of LISP to enable, for
> instance, two IPv6 sites to communicate via the IPv4 Internet, while
> one or both sites has no native IPv6 connectivity?   A concrete
> example would help.
> 
> 
> >> 4 - LISP-ALT's Aggregation implies provider dependence.
> >>    This is Christian Vogt's critique:
> >>    http://psg.com/lists/rrg/2008/msg00259.html
> > 
> > Not true. Aggregation here is for the EID-prefix. Service 
> providers do
> > not carry EID-prefixes in their cores so you don't depend 
> on them. The
> > decoupling of the address creates this. 
> 
> Christian's critique is not that an end-user network which has
> (permanently, by some arrangement) a slice of EID space is bound to
> its current ISP (the one it uses for connectivity).
> 
> The critique is on this potentially erroneous basis: that the
> end-user network is bound to maintaining connectivity (via a tunnel)
> to the ALT router which handles this part of the EID space.  It needs
> to do this so mapping queries for its EID space will get to its ETR.
> 
> The potentially faulty aspect of this is the assumption that the
> end-user network runs its own ETR.
> 
> But if its one or more ISPs run the ETR this end-user network uses,
> then the end-user network still depends on those ETRs having tunnels
> to potentially distant ALT router for its section of the EID space.
> 
> I don't know if anyone has considered the scaling problems of a busy
> ETR maintaining tunnels to about as many ALT routers as the end-user
> networks it handles packets for.
> 
> The ALT router for this section of the EID space will, I assume, be
> located at some ISP somewhere, or some other commercial organisation
> which rents out the EID space to this end-user network.
> 
> Maybe that organisation is an RIR.  But when this scales to tens or
> hundreds of millions of end-user networks (I assume this is a goal of
> LISP - it is of Ivip) I doubt if RIRs will want to be dealing with a
> hundred million end-user networks directly, either for address
> assignment or for tunnels to receive mapping requests to their ETRs
> from the ALT network.
> 
> For these large scaling arrangements, there will need to be
> potentially multiple levels of address splitting.  Ivip allows for
> this, and for multiple levels of companies providing interfaces to
> accept mapping changes from end-user networks (or more likely from
> reachability testing companies they hire) and funnelling them to the
> limited number of RUAS organisations which run the fast-push mapping
> distribution system.
> 
> Any way you do this core-edge separation business - LISP, APT, Ivip
> or TRRP - if the end-user network gets a patch of stable address
> space to call their own, year after year, then that network is going
> to depend on some company or other organisation for that space.  The
> end-user network will need to pay for this, and depend on the
> organisation to handle mapping.
> 
> In the case of LISP-ALT, the organisation needs to run (or have
> someone else run) an ALT router (plus backups) which has a tunnel to
> the ETRs in the ISPs which the end-user network is currently using
> for access.  If that organisation's ALT routers go down, it is not
> the fault of the access ISPs - it is up to the end-user network to
> ensure it obtains its EID address from an organisation which provides
> a reliable ALT router service.
> 
> Also - assuming the space is covered by a PTR in order to provide
> 100% multihomed service for packets sent from hosts in non-upgraded
> networks - this organisation has to run PTRs which covers this
> end-user's EID space.  For this to be scalable (not to bloat the DFZ
> routing table excessively, as we go to millions of end-user networks
> with EID/micronet space), the PTRs needs to advertise a prefix which
> covers the EID space of thousands or hundreds of thousands of
> separate end-user networks.
> 
> Since the sending hosts (in non-upgraded networks) could be anywhere
> in the world and since the ISPs used by all these end-user networks
> (covered by the one BGP advertised route) could be anywhere in the
> world, in order to ensure reasonably direct path for traffic packets,
> there needs to be a largish number of PTRs physically all over the
> Net.  Then the organisation which runs this PTR system needs to
> recover costs from individual end-user networks according to the
> traffic the PTRs carry.   (This is the Ivip business model for
> OITRDs.  I am stating this as an imperative for LISP, because I can't
> imagine any other business model for PTRs.)
> 
> In the case of Ivip, the equivalent organisation needs to do the same
> as just stated for OITRDs and provide the real-time mapping
> distribution service, with a small charge per update.
> 
> Either way, the end-user network has a long-term technical and
> commercial dependency on whichever organisation supplies its EID
> (LISP) or micronet (Ivip) address space.  This is why my message
> continued to state that a problem such as this is common to all
> core-edge separation schemes:
> 
>       [Fix?  Seems to be a fundamental problem, but every core-edge
>        separation scheme involves supplying stable EID, micronet etc.
>        address space to end-user networks, so there must be some
>        kind of dependence on some organisation - though not
>        necessarily an ISP.]
> 
>       {Experiments?  There's no need for experiment - problems such
>        as this can be clearly foreseen.}
> 
> So while I could take this off the list of "unresolved" problems for
> LISP, since other schemes have comparable problems - I think LISP
> could be improved by more clearly stating the types of commercial and
> technical relationships each participating end-user network will rely
> upon.  Also, the physical distance to the ALT router from wherever
> the end-user network's ETRs are directly affects the delay
> experienced at the start of sessions.  I think that is part of
> Christian Vogt's concern.
> 
> I think I have done a better job of explaining all this with Ivip's
> business model for OITRDs:
> 
>   http://psg.com/lists/rrg/2008/msg01158.html
> 
> > The dependence is now on the
> > ALT. And if your site resides in a specific region of the 
> world, you get
> > your EID-prefixes from that registry. So readdressing your 
> domain would
> > only occur if you moved it from one region to another (let's leave
> > mobile ASes out of this for now).
> 
> I think a good core-edge separation scheme should make the EID
> (micronet) space entirely portable, with little or no compromise in
> performance or costs regarding mapping no matter where the end-user
> network chooses to connect its EID space (or some part of it) 
> to the Net.
> 
> This is easier for Ivip, since the mapping change command only
> involves a few dozen bytes and is made quite infrequently.
> 
> For LISP-ALT, the mapping connection is an incoming stream of
> requests or initial packets which also function as requests.  It is
> time-sensitive, since only when a response arrives at the ITR can
> communications without delay begin.  So the physical proximity (delay
> and reliability) between the ALT router for this section of the EID
> address space and the the ETRs of the ISPs currently used by the
> end-user network is really important.  I don't mean San Jose to LA
> distances - I mean Australia to the USA, Germany to China etc.
> 
> These do seem to be a fundamental difference between LISP-ALT and
> Ivip.  However, both systems will only work well with a widespread
> set of PTRs/OITRDs.
> 
> 
> >> 5 - Path MTU Discovery problems.  Despite Fred Templin, myself and
> >>    others discussing the inherent PMTUD problems in any map-encap
> >>    proposal, there has been nothing from the LISP team to indicate
> >>    they have a solution.  They seem to think there is no problem.
> > 
> > In section 5.4 of draft-farinacci-lisp-11.txt we describe 
> two proposed
> > solutions, one is stateless, and the other is stateful. The stateful
> > creates no new table data structures but requires storing 
> an addition
> > 2-bytes of effective-MTU state per mapping.
> 
> OK - I apologise for stating that you thought there was no problem.
> 
> I haven't considered MTU problems of sending traffic packets along
> the ALT network, in its GRE tunnels (which impose their own
> encapsulation overhead) - but I understand the current LISP test
> network doesn't send traffic packets over ALT.  It is my impression
> that your long-term plans are to use the ALT network only for short
> map request messages, not go get initial traffic packets to 
> the ETR ASAP.
> 
> Version 08 (2008-07-10) introduced a stateless technique and version
> 11 (2008-12-19) adds a stateful approach, derived from the OpenLISP
> project, who regarded the stateless approach as inadequate.
> 
> My assessment of both approaches is in a separate message:
> 
>   LISP PMTU - 2 methods in draft-farinacci-lisp-11
>   http://www.irtf.org/pipermail/rrg/2009-January/000885.html
> 
> I think the stateless section is poorly written and ill-conceived.
> The stateless approach for IPv4 DF=1 packets and IPv6 packets (that
> is, virtually all traffic) would limit traffic packets to 1464 bytes
> (IPv4) or 1444 bytes (IPv6).  Only once there was jumboframe links
> between every ITR and ETR could L be globally adjusted upwards from
> 1500 bytes to ~9000 bytes or whatever - but this would not be
> possible for a decade or two.  Fred Templin expressed the same
> concerns in a recent RRG message.
> 
> The Stateful approach, which I understand is derived from OpenLISP,
> is similar to Ivip's approach:
> 
>   http://www.firstpr.com.au/ip/ivip/pmtud-frag/
> 
> I need to write this up as an I-D, but it is a more detailed spec
> than your LISP approach, with mechanisms for occasionally testing for
> MTUs longer than the assumed limit and for strictly minimising the
> number of traffic packets which are used to probe the PMTU.  Every
> packet whose length, once encapsulated, is in the "zone of
> uncertainty" for this ETR is either delivered or rejected with a PTB.
>    The former raises the lower limit to the zone and the latter
> reduces the upper limit.
> 
> 
> >> 6 - Lack of business case for LISP's Proxy Tunnel Routers:
> >>    http://psg.com/lists/rrg/2008/msg02021.html
> > 
> > You cannot fault a technical design for a business case. 
> 
> A complete solution to the routing scaling problem involves much more
> than a technical design.
> 
> All the technical stuff (sometimes split into "architecture" vs.
> "engineering") needs to facilitate someone wanting to build and run
> each part of it - which generally means they (or someone not too far
> removed from them) needs to be able to make money from it.
> 
> 
> > A PTR is
> > solving a technical problem. And if we want to *truly* keep 
> lots of PI
> > type routes out of the core *and* avoid NAT solutions which 
> are just way
> > too high in opex, the PTR is the only solution we have to turn to.
> > 
> > And on the contrary, I do believe service providers, interconnect
> > providers, registries, third-parties and even governments 
> will provide
> > PTR services. Will they make a ton of money out of it, well 
> that remains
> > to be seen.
> 
> I think my critique is valid - you seem to have no business case for
> LISP's Proxy Tunnel Routers.
> 
> You are welcome to adopt the Ivip approach for address management and
> OITRDs:
> 
>   http://psg.com/lists/rrg/2008/msg01158.html
> 
> This is directly applicable to LISP and PTRs, as long as you have a
> concept of a Mapped Address Block, containing many EIDs.  For that to
> be the case, you need to develop business arrangements concerning who
> really "owns" the MAB and how they rent this space out as EID space
> for thousands of end-user networks.
> 
> 
> >> 7 - The scaling problems of potentially thousands of ITRs each
> >>    probing reachability to one ETR, and likewise, one ITR probing
> >>    reachability to many ETRs - this is one view of the 
> "Locator Path
> >>    Liveness Problem" of draft-meyer-loc-id-implications-00.
> >>    http://www.irtf.org/pipermail/rrg/2009-January/000809.html
> > 
> > That is not in the LISP design. Everyone just thinks it is.  ;-)
> > 
> > Dave and Darrel's draft is providing a warning about how 
> bad probing can
> > be. They do not take a position whether it should go into 
> any proposal.
> > They are just saying, beware of the Frankenstein that may 
> result and can
> > be an interpretation to not do probing at all.
> 
> The scaling problem of thousands of ITRs continually test
> reachability for one ETR (or to every ETR on the LISP mapping list
> for a given EID), plus reachability through each ETR to a given
> destination network, or of each ITR having to test reachability to
> thousands or tens of thousands of ETRs have been obvious from the
> start: early 2007.
> 
> This is true of LISP, TRRP and to a somewhat lesser extent APT. (I
> haven't read RANGER yet.)
> 
> Only Ivip avoids these scaling problems by making the end-user
> network responsible for their reachability testing and for deciding
> which ETR the packets for each micronet should be tunneled to.
> 
> 
> > Like I mentioned in a previous RRG email message, one has to ask the
> > question if an ITR *should* switch from one RLOC to another 
> when there
> > *may* be a path failure *somewhere in the middle of the 
> network*. Please
> > note my very fine qualifications.
> > 
> > If we want to solve this problem, we could do this today by having a
> > host switch it's TCP connection to another A record. This 
> doesn't happen
> > today because people deal with packet loss, since it 
> doesn't last long
> > *and* rerouting actually works quite well.
> > 
> > Van Jacobson always made this comment and I'll never forget it, "The
> > fact that the Internet drops packets is it's greatest feature".
> > 
> > What else can either an xTR or TCP host do when sending ICMP
> > Unreachables are off by default in most modern routers, or they are
> > filtered by firewalls, and route aggregation hides failures close to
> > packet sources.
> 
> The alternative has been available to you and anyone else since July
> 2007: Ivip.  A fast-push mapping system to local query servers means
> the ITRs don't need to test reachability or make any decisions about
> which ETR to use.  The mapping has a single ETR address.
> 
> What is wrong with this approach?
> 
> 
> >>> Unless these concerns are adequately addressed, claiming that LISP
> >>> is an appropriate solution to the problems discussed at the IAB's
> >>> October 2006 Routing and Addressing Workshop is nothing more than
> >>> a proof by an emphatic assertion.
> >>
> >> I agree entirely.
> >>
> >> I believe the LISP team could have made much better use of 
> the RRG -
> >> by participating fully in the debates resulting from these 
> critiques.
> > 
> > We were asked to do research in RRG. That was a reasonable 
> request. So
> > the research stuff in LISP has been and will continue to be 
> presented in
> > RRG.
> 
> OK.
> 
> > As for the engineering issues, the real details and bits 
> and bytes, we
> > want a forum to discuss and work out issues in an open 
> forum. I've been
> > going to IETF for 20 years now, that forum is called a 
> working group.
> > 
> > The working group doesn't have to standardize what it is 
> working on. And
> > the charter and the numerous requests we have made requests *for an
> > experimental working group*.
> 
> I think this is fine.
> 
> However, I think there are sufficient fundamental, well known
> problems with LISP-ALT that if this was my proposal, I would fix them
> before asking people in general to join an IETF WG and help me with
> it - or drop the proposal.
> 
> 
> >> Experiments won't help solve most of these problems.  I am not
> >> against experimentation and I think it is great that there 
> is a LISP
> >> experimental network.
> >>
> >> However, I would never have taken a proposal to the point 
> of writing
> >> code, running a network and inviting others to write compatible
> >> implementations when the proposal had so many fundamental problems.
> > 
> > There is constant implementation feedback back into the design.
> > Experienced engineers know how this cycle works. You start with
> > something you think can hold together, you try things out, 
> you refine,
> > you revisit design, you go forward with implementation. That's the
> > process of *detailed* engineering.
> >
> > For the old timers, that was the difference between TCP/IP and OSI.
> 
> I am all for detailed engineering, running tests etc.  However, the
> worst problems I perceive with LISP-ALT will not be illuminated by
> any amount of testing, as I explained in the message you are
> responding to.
> 
> 
> Do you think Ivip is so overblown and over-complex that it warrant's
> no serious consideration?
> 
> Just because I write stuff in detail doesn't mean the system itself
> is over-complex.  Ivip ITRs and ETRs are much simpler than LISP ITRs
> and ETRs.
> 
> 
> I have been giving your work the honour of detailed critiques for 18
> months.  I would appreciate you and your colleagues returning the
> favour by reading:
> 
>   http://www.firstpr.com.au/ip/ivip/Ivip-summary.pdf
> 
>   http://tools.ietf.org/html/draft-whittle-ivip-db-fast-push-00
> 
>   Ivip business models: fast push & OITRDs
>   http://psg.com/lists/rrg/2008/msg01158.html
> 
> and telling me - and the RRG - what you think.
> 
> 
> Also, I am keen to know from you, your Cisco colleagues and from the
> folks at Juniper how practical it would be to create firmware
> upgrades for all the DFZ routers in use ca. 2014 or whatever -
> whenever the routing scaling solution is to be implemented.
> 
> I think it is practical and highly desirable to encode the ETR
> address in the IPv4 header (actually 30 bits, which is fine) or a 20
> bit prefix label in the IPv6 header.  Then, in the longer term, we
> don't need encapsulation, its complexity, its overhead and its damn
> PMTUD problems.
> 
> As far as I know, both these proposals could be implemented as
> firmware upgrades, or built-in optional features, in the DFZ routers
> which are likely to be in use in 5 years time, but only you guys can
> say this is so or not:
> 
>   ETR Address Forwarding (EAF) - for IPv4
>   http://tools.ietf.org/html/draft-whittle-ivip4-etr-addr-forw-01
> 
>   Prefix Label Forwarding (PLF) - for IPv6
>   http://www.firstpr.com.au/ip/ivip/ivip6/
> 
> Maybe we can do that in time for the introduction of the routing
> scaling solution - and thereby completely avoid encapsulation and its
> PMTUD complexities.
> 
> 
> On mobility - what is your objection to this arrangement?  ETR-like
> Translating Tunnel Routers with two-way encrypted tunnels to mobile
> nodes.  Mapping only changes to a new TTR when one is really needed 0
> which is typically only when the MN moves 1000km or more.  So mapping
> changes are not at all frequent and in particular are not needed
> every time the MN gets a new CoA:
> 
>   http://www.firstpr.com.au/ip/ivip/TTR-Mobility.pdf
> 
> 
> If I was proposing to the IETF that a WG be formed for my project, I
> would first want to establish for myself - and for IETF people in
> general - that my project was either the best in its class, or one of
> the very few with the most promise.
> 
> I don't see how you can do that when you fail to read - or at least
> fail to discuss in public - alternative schemes to LISP.
> 
> Ivip and APT are broadly comparable to LISP - they are all core-edge
> elimination schemes for both IPv4 and IPv6.  They are both well
> enough documented to be suitable for serious critiques from anyone
> who believes LISP's approach is superior.
> 
> Just because you have more people - with more experience and
> resources - working on LISP and have running code, doesn't mean your
> LISP-ALT design is better than APT or Ivip.
> 
> 
>   - Robin
> 
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area
> 
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Wed Jan 28 09:43:43 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C1F8F3A6A8E; Wed, 28 Jan 2009 09:43:43 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E4FBE3A6A8E for <rrg@core3.amsl.com>; Wed, 28 Jan 2009 09:43:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.507
X-Spam-Level: 
X-Spam-Status: No, score=-6.507 tagged_above=-999 required=5 tests=[AWL=0.092,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OEVE-YTUyPSV for <rrg@core3.amsl.com>; Wed, 28 Jan 2009 09:43:41 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by core3.amsl.com (Postfix) with ESMTP id 878C23A6A74 for <rrg@irtf.org>; Wed, 28 Jan 2009 09:43:41 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 9465E6BE600; Wed, 28 Jan 2009 12:43:20 -0500 (EST)
To: rrg@irtf.org
Message-Id: <20090128174320.9465E6BE600@mercury.lcs.mit.edu>
Date: Wed, 28 Jan 2009 12:43:20 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: Re: [rrg] [lisp] [Int-area] Please respond: Questions from the IESG as to whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

    > From: Robin Whittle <rw@firstpr.com.au>

    > The LISP team should do detailed critiques of APT and Ivip as part of
    > convincing IETF folks of the merits of LISP-ALT.

Perhaps I'm confused, but I don't think the people working on LISP are trying
to "convince" the IETF as a whole of the "merits of LISP".

If some people out there in the Internet technical community think it looks
good, and want to work on it, run it, etc, that's great; but if other people
reach a contrary conclusion, and don't want to work on it, run it, etc (as is
their choice), that's fine too.

Sure, the people working on LISP would like to convince _some_ people that
it's a good idea, so they get i) some help working on it (as much remains to
be done), and ii) some places to deploy it (so some practical experience can
be gained, in seeing how well it works, what problems crop up in actual
service, etc), but that's a very different kettle of fish.

	Noel
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Wed Jan 28 15:18:47 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2CEE93A6C16; Wed, 28 Jan 2009 15:18:47 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8FBC23A6BF7; Wed, 28 Jan 2009 15:18:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O0dXF9NIpN-f; Wed, 28 Jan 2009 15:18:44 -0800 (PST)
Received: from mo-p05-ob.rzone.de (mo-p05-ob.rzone.de [81.169.146.181]) by core3.amsl.com (Postfix) with ESMTP id C6F233A6B2A; Wed, 28 Jan 2009 15:18:43 -0800 (PST)
X-RZG-CLASS-ID: mo05
X-RZG-AUTH: :IW0NeQWrc+lwhhNjh1Z2K6NdlYX3YUP3q0u9XxCxGfSzuaPVaZi9ctfI
Received: from [10.154.162.186] ([129.192.147.67]) by post.strato.de (mrclete mo3) (RZmta 18.13) with ESMTP id g061b3l0SMP2mf ; Thu, 29 Jan 2009 00:18:21 +0100 (MET)
Message-Id: <3103F803-D3A2-4757-86B6-7D8A97C679AC@ericsson.com>
From: Christian Vogt <christian.vogt@ericsson.com>
To: Dino Farinacci <dino@cisco.com>
In-Reply-To: <6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 28 Jan 2009 15:18:20 -0800
References: <20090120190744.GA9467@1-4-5.net> <49765FFB.1010709@piuha.net>	<200901222339.n0MNddM88868@magenta.juniper.net> <75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com> <497B1F7A.9030407@firstpr.com.au> <6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com>
X-Mailer: Apple Mail (2.929.2)
Cc: rrg RG <rrg@irtf.org>, int-area@ietf.org, Robin Whittle <rw@firstpr.com.au>, routing-discussion@ietf.org, lisp@ietf.org
Subject: Re: [rrg] Please respond: Questions from the IESG as to whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On Jan 24, 2009, Dino Farinacci wrote:

>> 4 - LISP-ALT's Aggregation implies provider dependence.
>>     This is Christian Vogt's critique:
>>     http://psg.com/lists/rrg/2008/msg00259.html
>
> Not true. Aggregation here is for the EID-prefix. Service providers do
> not carry EID-prefixes in their cores so you don't depend on them. The
> decoupling of the address creates this. The dependence is now on the
> ALT. And if your site resides in a specific region of the world, you  
> get
> your EID-prefixes from that registry. So readdressing your domain  
> would
> only occur if you moved it from one region to another (let's leave
> mobile ASes out of this for now).


Dino -

There is a tradeoff between EID portability and path stretch along the
ALT topology, and I believe the tradeoff made in LISP/ALT has been
revised a few times.

Portability of EID prefixes requires that the ALT topology follows
EID-addressing.  This leads to potentially longer-than-optimal paths
along the ALT topology.  Vice versa, if path stretch is to be limited,
then portability of EID prefixes must be restricted.

According to your email to Robin, LISP/ALT currently makes the following
tradeoff:  Portability of EID prefixes is limited geographically in
order to curb path stretch along the ALT topology to the maximum that
can happen within a geographical region.

That's possible, of course.  The cost is that networks scattered over
different parts of the world, such as those of enterprises with global
presence, cannot use a continuous address space internally -- even if
they all attach to the same provider.

- Christian


_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Wed Jan 28 17:10:34 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A8DF728C251; Wed, 28 Jan 2009 17:10:34 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D440928C1FA for <rrg@core3.amsl.com>; Wed, 28 Jan 2009 17:10:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aEO5ekQrGbs8 for <rrg@core3.amsl.com>; Wed, 28 Jan 2009 17:10:32 -0800 (PST)
Received: from mo-p05-ob.rzone.de (mo-p05-ob.rzone.de [81.169.146.181]) by core3.amsl.com (Postfix) with ESMTP id 6044D28C1B5 for <rrg@irtf.org>; Wed, 28 Jan 2009 17:10:32 -0800 (PST)
X-RZG-CLASS-ID: mo05
X-RZG-AUTH: :IW0NeQWrc+lwhhNjh1Z2K6NdlYX3YUP3q0u9XxCxGfSzuaPVaZi9ctfI
Received: from [10.154.162.186] ([129.192.147.67]) by post.strato.de (fruni mo63) (RZmta 18.13) with ESMTP id 2010ccl0SNwIWV ; Thu, 29 Jan 2009 02:10:11 +0100 (MET)
Message-Id: <0D2323EA-9F1D-43E8-9793-DF4D2E391B56@ericsson.com>
From: Christian Vogt <christian.vogt@ericsson.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <49763F1C.30601@gmail.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 28 Jan 2009 17:10:10 -0800
References: <4975143E.9020404@gmail.com> <49752F9C.4050006@joelhalpern.com> <F2DA6B6C-6E73-4FA4-A2DD-2966FA400211@nomadiclab.com> <B25790E2-8D3C-4A55-848C-F461982DC3F6@nomadiclab.com> <20090119213701.GA34129@cisco.com> <4975143E.9020404@gmail.com> <49752F9C.4050006@joelhalpern.com> <B25790E2-8D3C-4A55-848C-F461982DC3F6@nomadiclab.com> <20090119213701.GA34129@cisco.com> <4975143E.9020404@gmail.com> <497616D4.8090500@employees.org> <49763F1C.30601@gmail.com>
X-Mailer: Apple Mail (2.929.2)
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] Why a host-based solution does not necessarily add signalling load
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Brian E Carpenter wrote:

> One thing that may be useful is an API that allows the upper layer to
> tell the local IP stack "Hey, I'm seeing a liveness problem, please
> check it out." That would make constant liveness checks by the network
> layer unnecessary.

Right.  This would also account for the fact that the result of probing
does not necessarily correspond to the success/failure of data delivery
-- independent of whether the probing packets are sent by a host or a
router.  One potential cause for incorrect probing results is that data
packets get filtered due to the protocol they carry, whereas probing
packets pass through filters.  Another potential cause is that data
packets and probing packets are routed via different paths (cf. ECMP) of
which only one is functional.

Only the use of data packets themselves as probes can avoid this issue.
But then, if we use data packets as probes, we eliminate the overhead of
probing in the first place...

- Christian


_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Wed Jan 28 17:20:31 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D576928C180; Wed, 28 Jan 2009 17:20:31 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 23AF328C180 for <rrg@core3.amsl.com>; Wed, 28 Jan 2009 17:20:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.511
X-Spam-Level: 
X-Spam-Status: No, score=-6.511 tagged_above=-999 required=5 tests=[AWL=0.088,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AdBIPvnnSu-r for <rrg@core3.amsl.com>; Wed, 28 Jan 2009 17:20:30 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 02C9528C17E for <rrg@irtf.org>; Wed, 28 Jan 2009 17:20:30 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,340,1231113600"; d="scan'208";a="238637065"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 29 Jan 2009 01:19:11 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n0T1JBWe005291;  Wed, 28 Jan 2009 17:19:11 -0800
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n0T1JBKv008599; Thu, 29 Jan 2009 01:19:11 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 28 Jan 2009 17:19:11 -0800
Received: from [10.24.197.109] ([10.21.74.187]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 28 Jan 2009 17:19:10 -0800
Message-Id: <440A01B3-E96C-461A-93EC-6FD8E74FC7D2@cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A1057DFFA6@XCH-NW-7V2.nw.nos.boeing.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Wed, 28 Jan 2009 17:19:06 -0800
References: <20090120190744.GA9467@1-4-5.net>	<49765FFB.1010709@piuha.net>	<200901222339.n0MNddM88868@magenta.juniper.net>	<75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com>	<497B1F7A.9030407@firstpr.com.au><6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com> <497EB510.8060100@firstpr.com.au> <39C363776A4E8C4A94691D2BD9D1C9A1057DFFA6@XCH-NW-7V2.nw.nos.boeing.com>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 29 Jan 2009 01:19:11.0257 (UTC) FILETIME=[97308890:01C981AF]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=483; t=1233191951; x=1234055951; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dino@cisco.com; z=From:=20Dino=20Farinacci=20<dino@cisco.com> |Subject:=20Re=3A=20[Int-area]=20[rrg]=20Please=20respond=3 A=20Questions=20from=20the=20IESG=20as=20towhether=20a=20WG= 20forming=20BOF=20is=20necessary=20for=20LISP |Sender:=20; bh=9XQpk/a4R50JNyPkCQ9KVggNFSRunZDTl0IT9fFHD1c=; b=oLuxsZOx8t/OkkPL7cnWTRSNnAO9d0UDHasmGxBy2jsrKHdjgrSSCoWwhX n4cYroDPQNp4yrJv702DPMF+L6gOIVTgJeJ8ieJERGlEVuyeF54lydIxxezG WDcag4smhh;
Authentication-Results: sj-dkim-3; header.From=dino@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); 
Cc: RRG <rrg@irtf.org>, int-area@ietf.org, Robin Whittle <rw@firstpr.com.au>, routing-discussion@ietf.org, lisp@ietf.org
Subject: Re: [rrg] [Int-area] Please respond: Questions from the IESG as towhether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

> The approach in the current LISP draft still relies on ICMPs
> coming from anonymous network middleboxes (which Dino himself
> has said that we cannot depend on), and provides insufficient

I did not say that. I said you cannot depend on ICMP Unreachables. But  
ICMP TooBig and Time-Exceeded message are sent and are more  
dependable. That is, they can get lost when they are transmitted since  
they are single transmitted datagrams. But at least they are sent.

Dino
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Wed Jan 28 18:53:40 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 30D7D3A6C2E; Wed, 28 Jan 2009 18:53:40 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 97F933A6C2E for <rrg@core3.amsl.com>; Wed, 28 Jan 2009 18:53:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.513
X-Spam-Level: 
X-Spam-Status: No, score=-6.513 tagged_above=-999 required=5 tests=[AWL=0.086,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7f6BywNK0Era for <rrg@core3.amsl.com>; Wed, 28 Jan 2009 18:53:38 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 784813A691E for <rrg@irtf.org>; Wed, 28 Jan 2009 18:53:38 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,340,1231113600"; d="scan'208";a="134906643"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-1.cisco.com with ESMTP; 29 Jan 2009 02:52:13 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n0T2qDhL003672;  Wed, 28 Jan 2009 18:52:13 -0800
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id n0T2qDwm003525; Thu, 29 Jan 2009 02:52:13 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 28 Jan 2009 18:52:13 -0800
Received: from [10.24.197.109] ([10.21.74.187]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 28 Jan 2009 18:52:11 -0800
Message-Id: <83BCD1E8-9EDB-4D81-94E1-0823B957E08F@cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: Christian Vogt <christian.vogt@ericsson.com>
In-Reply-To: <3103F803-D3A2-4757-86B6-7D8A97C679AC@ericsson.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Wed, 28 Jan 2009 18:52:04 -0800
References: <20090120190744.GA9467@1-4-5.net> <49765FFB.1010709@piuha.net>	<200901222339.n0MNddM88868@magenta.juniper.net> <75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com> <497B1F7A.9030407@firstpr.com.au> <6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com> <3103F803-D3A2-4757-86B6-7D8A97C679AC@ericsson.com>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 29 Jan 2009 02:52:12.0315 (UTC) FILETIME=[95C266B0:01C981BC]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3589; t=1233197533; x=1234061533; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dino@cisco.com; z=From:=20Dino=20Farinacci=20<dino@cisco.com> |Subject:=20Re=3A=20Please=20respond=3A=20Questions=20from= 20the=20IESG=20as=20to=20whether=20a=20WG=20forming=20BOF=20 is=20necessary=20for=20LISP |Sender:=20; bh=qrd/RARkhtJ0Gdwe9KVtZD0CdEsZ95qCkmw2o0nNFMY=; b=trULZT7LPldfpPJgTFohnC6aK2reDgzQ5+I0KVsuEOK/53uE+fUYfJUeps hqq1Fs+qQ0egdf11Aqd73z8FV0huKkhV/f/Z7n03utKrH+YtWHoCfZdZuk9q lodnfSYX1p;
Authentication-Results: sj-dkim-2; header.From=dino@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); 
Cc: rrg RG <rrg@irtf.org>, int-area@ietf.org, Robin Whittle <rw@firstpr.com.au>, routing-discussion@ietf.org, lisp@ietf.org
Subject: Re: [rrg] Please respond: Questions from the IESG as to whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

> On Jan 24, 2009, Dino Farinacci wrote:
>
>>> 4 - LISP-ALT's Aggregation implies provider dependence.
>>>    This is Christian Vogt's critique:
>>>    http://psg.com/lists/rrg/2008/msg00259.html
>>
>> Not true. Aggregation here is for the EID-prefix. Service providers  
>> do
>> not carry EID-prefixes in their cores so you don't depend on them.  
>> The
>> decoupling of the address creates this. The dependence is now on the
>> ALT. And if your site resides in a specific region of the world,  
>> you get
>> your EID-prefixes from that registry. So readdressing your domain  
>> would
>> only occur if you moved it from one region to another (let's leave
>> mobile ASes out of this for now).
>
>
> Dino -
>
> There is a tradeoff between EID portability and path stretch along the
> ALT topology, and I believe the tradeoff made in LISP/ALT has been
> revised a few times.

Yes, but if you are portable within an aggregate boundary, you are okay.

> Portability of EID prefixes requires that the ALT topology follows
> EID-addressing.  This leads to potentially longer-than-optimal paths

And it does.

> along the ALT topology.  Vice versa, if path stretch is to be limited,
> then portability of EID prefixes must be restricted.

I envision the number of hops a Map-Request takes is 4 ALT-router  
hops. I think we can do that with how the aggregation and allocation  
assignment is done on the LISP network now.

Now if the diameter of the tunnels are large, then there will be  
longer delays because the Map-Request will have to travel more  
physical hops.

But I really think you are not going to find a better way.

> According to your email to Robin, LISP/ALT currently makes the  
> following
> tradeoff:  Portability of EID prefixes is limited geographically in
> order to curb path stretch along the ALT topology to the maximum that
> can happen within a geographical region.

Right that is the tradeoff, but a site in Europe is not going to move  
to the US. A new site that is added in the US will get EID-prefixes  
from ARIN and terminate it's tunnels to the routers in the allocation  
assignment hierarchy for ARIN.

> That's possible, of course.  The cost is that networks scattered over
> different parts of the world, such as those of enterprises with global
> presence, cannot use a continuous address space internally -- even if
> they all attach to the same provider.

Christian, when you come to IETF in the US and you use your VPN client  
to connect back home to Finland, and you go to a URL in San Jose (when  
you are at the SF IETF), your packets will to east over the Atlantic  
twice and back to the west coast. That's a delay we all seem to live  
with everyday.

I am not justifying delay and I'm not at all saying this is going to  
happen on the ALT either. Remember this only happens for the first few  
packets to a new site when there is a cache miss from each ITR.

You cannot push around 10^10 entries and store them everywhere. In  
fact there are chances with a push technology that you might have to  
store them in nodes that won't need them for use but will need to  
store them for distribution. That will be a big cost. So then you go  
get them when you need them.

Please recall, for LISP to support such a large database (10^10  
entries), it must be distributed. And you want them to be stored where  
the policy holders are for the mapping and you wan them to reside at  
the site that the mapping describes them.

Dino

>
>
> - Christian
>
>

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Wed Jan 28 20:06:25 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8F2D528C275; Wed, 28 Jan 2009 20:06:25 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7C9AD28C273 for <rrg@core3.amsl.com>; Wed, 28 Jan 2009 20:06:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.514
X-Spam-Level: 
X-Spam-Status: No, score=-6.514 tagged_above=-999 required=5 tests=[AWL=0.085,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EUF12yeeykIL for <rrg@core3.amsl.com>; Wed, 28 Jan 2009 20:06:24 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by core3.amsl.com (Postfix) with ESMTP id E04BB28C275 for <rrg@irtf.org>; Wed, 28 Jan 2009 20:06:19 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 7846D6BE603; Wed, 28 Jan 2009 23:06:01 -0500 (EST)
To: rrg@irtf.org
Message-Id: <20090129040601.7846D6BE603@mercury.lcs.mit.edu>
Date: Wed, 28 Jan 2009 23:06:01 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: Re: [rrg] Please respond: Questions from the IESG as to whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

    > From: Christian Vogt <christian.vogt@ericsson.com>

    > Portability of EID prefixes requires that the ALT topology follows
    > EID-addressing. This leads to potentially longer-than-optimal paths
    > along the ALT topology. Vice versa, if path stretch is to be limited,
    > then portability of EID prefixes must be restricted.

Yes, but this is only for the first packet(s), until the mapping gets back to
the ITR. Do you really think a few extra hops there are going to be a
problem? (Especially given that due to EGP/IGP information flow barriers,
paths probably aren't completely optimal anyway....)

Also, what percentage of DNS resolutions take more than one round-trip
(because of the use of multi-level DNS names)? Surely that's an even worse
delay (several round-trips, as opposed to simply a few extra hops), but I
don't think I've heard complaints about that?

        Noel
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Thu Jan 29 06:05:45 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 367113A6B5A; Thu, 29 Jan 2009 06:05:45 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EA0963A6A56; Thu, 29 Jan 2009 06:05:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.416
X-Spam-Level: 
X-Spam-Status: No, score=-6.416 tagged_above=-999 required=5 tests=[AWL=0.183,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rKAEVQ3OpJJK; Thu, 29 Jan 2009 06:05:43 -0800 (PST)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id 245163A6A71; Thu, 29 Jan 2009 06:05:42 -0800 (PST)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n0TE4wsc010132 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 29 Jan 2009 06:04:58 -0800 (PST)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n0TE4v3l021095; Thu, 29 Jan 2009 08:04:57 -0600 (CST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n0TE4vdu021090; Thu, 29 Jan 2009 08:04:57 -0600 (CST)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 29 Jan 2009 06:04:57 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 29 Jan 2009 06:04:55 -0800
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1057E05C1@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <440A01B3-E96C-461A-93EC-6FD8E74FC7D2@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Int-area] [rrg] Please respond: Questions from the IESG as towhether a WG forming BOF is necessary for LISP
Thread-Index: AcmBr5h3nX66/9E7RIOwuGbOr3U3zwAaVyPA
References: <20090120190744.GA9467@1-4-5.net>	<49765FFB.1010709@piuha.net>	<200901222339.n0MNddM88868@magenta.juniper.net>	<75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com>	<497B1F7A.9030407@firstpr.com.au><6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com> <497EB510.8060100@firstpr.com.au> <39C363776A4E8C4A94691D2BD9D1C9A1057DFFA6@XCH-NW-7V2.nw.nos.boeing.com> <440A01B3-E96C-461A-93EC-6FD8E74FC7D2@cisco.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Dino Farinacci" <dino@cisco.com>
X-OriginalArrivalTime: 29 Jan 2009 14:04:57.0258 (UTC) FILETIME=[9123E8A0:01C9821A]
Cc: RRG <rrg@irtf.org>, int-area@ietf.org, Robin Whittle <rw@firstpr.com.au>, routing-discussion@ietf.org, lisp@ietf.org
Subject: Re: [rrg] [Int-area] Please respond: Questions from the IESG as towhether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

 

> -----Original Message-----
> From: Dino Farinacci [mailto:dino@cisco.com] 
> Sent: Wednesday, January 28, 2009 5:19 PM
> To: Templin, Fred L
> Cc: Robin Whittle; RRG; routing-discussion@ietf.org; 
> int-area@ietf.org; lisp@ietf.org
> Subject: Re: [Int-area] [rrg] Please respond: Questions from 
> the IESG as towhether a WG forming BOF is necessary for LISP
> 
> > The approach in the current LISP draft still relies on ICMPs
> > coming from anonymous network middleboxes (which Dino himself
> > has said that we cannot depend on), and provides insufficient
> 
> I did not say that. I said you cannot depend on ICMP 
> Unreachables. But

Yes, that is what you said. And, an IPv4 PTB is just an
ICMP unreachable with code=4.
 
> ICMP TooBig and Time-Exceeded message are sent and are more  
> dependable. That is, they can get lost when they are 
> transmitted since  
> they are single transmitted datagrams. But at least they are sent.

There is evidence (e.g., RFC2923, RFC4821, etc.) that
this is not always true.

Fred
fred.l.templin@boeing.com

> 
> Dino
> 
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Thu Jan 29 18:21:45 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 333F43A6898; Thu, 29 Jan 2009 18:21:45 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8D0963A6898 for <rrg@core3.amsl.com>; Thu, 29 Jan 2009 18:21:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.54
X-Spam-Level: 
X-Spam-Status: No, score=-1.54 tagged_above=-999 required=5 tests=[AWL=0.355,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XAoRFBI+Mg8B for <rrg@core3.amsl.com>; Thu, 29 Jan 2009 18:21:43 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123]) by core3.amsl.com (Postfix) with ESMTP id E68183A6870 for <rrg@irtf.org>; Thu, 29 Jan 2009 18:21:42 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6]) by gair.firstpr.com.au (Postfix) with ESMTP id 7D64A175D74; Fri, 30 Jan 2009 13:04:24 +1100 (EST)
Message-ID: <498260AB.902@firstpr.com.au>
Date: Fri, 30 Jan 2009 13:06:35 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: RRG <rrg@irtf.org>
References: <497E9BB2.5040101@firstpr.com.au><497ED66B.8000505@net.t-labs.tu-berlin.de>	<497F0B30.1010404@firstpr.com.au> <39C363776A4E8C4A94691D2BD9D1C9A1057A2DD3@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A1057A2DD3@XCH-NW-7V2.nw.nos.boeing.com>
Cc: lisp@ietf.org
Subject: Re: [rrg] LISP PMTU - 2 methods in draft-farinacci-lisp-11
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Hi Fred,

Thanks for these references, and some other PMTUD discussion in
the "Please respond: Questions from the IESG as to whether a WG
forming BOF is necessary for LISP" thread, which I will respond
to here:

>> I stand corrected about LISP's approach to PMTUD - the latest
>> draft does include an outline of a workable solution.
>
> I don't know if you were fishing for a response,

No.  I meant it was at least going to work, if the PTBs
contained the nonce.  It may not work very well, but that is
better than the stateless approach, which won't work at all.

> but the
> stateful solution outlined in the latest LISP draft still
> has problems. It should also be mentioned that the approach
> (drop first; return PTBs for subsequent) is not new and
> has been proposed many times over the years.

I hadn't heard of this approach before.  I still think it has
problems.

> The approach in the current LISP draft still relies on ICMPs
> coming from anonymous network middleboxes (which Dino himself
> has said that we cannot depend on),

Dino clarified this to say that he thinks we can rely on PTBs
being sent - and generally rely on them being received:

  http://www.irtf.org/pipermail/rrg/2009-January/000899.html

    But ICMP TooBig and Time-Exceeded message are sent and are
    more dependable. That is, they can get lost when they are
    transmitted since they are single transmitted datagrams. But
    at least they are sent.

I assume this is true - it makes sense.  Anyone configuring a
DFZ router or an internal router between any ITR and ETR would
be badly mistaken not to allow generation of any PTBs.


> and provides insufficient
> means for authenticating any ICMPs that may come. For example,
> even if the ICMPs were delivered, and even if they included
> the LISP nonce, it would be impractical for the ITR to cache
> enough nonces of enough recently-sent packets especially at
> high data rates.

I tend to agree, but it depends on how smart the ITR is about
recognising "longer packets" and only caching details for that
subset.  There's no need for the ITR to cache a LISP nonce for
the purposes of PMTUD if the packet is shorter than some
constant below which it can be assumed there are no MTU
problems.  So VoIP packets and quite a few others will not need
to have any nonce or other details cached.

I wonder if there is a cryptographic approach to generating 32
bit nonces such that it is not necessary to cache each one in
order to be able to verify that a nonce in a PTB matched a
recently sent packet?

For instance, for a period of a second or two, set a randomly
selected set of 16 bits in the 32 bit nonce to some particular
bit pattern, which is pseudo-random, which remains the same for
the period and is cached.  Then, change the other 16 bits for
each generated nonce.

Hmmm - this just makes it easier for an attacker to spoof a nonce.

Maybe send the same nonce for all packets for 0.1 seconds . . .
No - if an attacker can get a tunneled packet from this ITR to
its own ETR then it use the nonce to spoof a PTB apparently from
a tunnel to another ETR.

Maybe there is some snappy crypto approach to this, but it needs
to be lightweight when checking the nonce in a PTB - and
knowledge of another recent nonce must not allow an attacker to
improve their chances of spoofing a valid nonce of another
packet tunneled to some other ETR.


My plan in:

  http://www.firstpr.com.au/ip/ivip/pmtud-frag/

is that a very small subset of packets get the special PMTUD
treatment.  Every such packet will result in a reduction of the
zone of uncertainty about the path MTU to the ETR.  Data will
either be delivered or the ETR and therefore the destination
network or the ITR will send a valid PTB to the sending host.

Pretty quickly, ordinary RFC 1191 sending host behaviour will
result in the zone of uncertainty being reduced to zero.  Then,
except for occasional attempts to try longer packets than the
current estimate allows, or to confirm that packets are getting
through when they are close to, or at, the current MTU limit,
there is no special treatment of packets and so nothing to
cache.  (In Ivip, ordinarily tunneled packets hitting an MTU
limit will not generate a PTB to the ITR - the PTB will go to
the sending host and not be recognised there.)

> So, the only option is to ignore ICMPs (leads to black holes)
> or honor ICMPs (leads to denial of large packet service).

If the ITR doesn't attempt to recognise PTBs, then it needs some
other way of determining PMTU to the ETR - which involves
special protocols between the ITR and ETR.  This is part of what
I am proposing.

My approach does recognise PTBs if they are sent with enough of
the offending packet to contain the nonce in the "Packet B",
which is the same length as the original traffic packet would
become with ordinary Ivip encapsulation.  This requires the
intermediate router send back at least 8 bytes more than the
bare minimum 8 bytes required by RFC 1911.

I think it is reasonable to expect DFZ and internal routers to
do this.  I recall someone writing that many do it already.  It
would be a straightforward config change or firmware update to
make sure they all did it in time for the introduction of Ivip
or any similar system.

So secure recognition of PTBs is used by my system, but the
system will still work without PTBs.

> I have said this before, but AFAICT DF=1 is busted.

I don't understand why.  My approach should support any RFC 1191
 sending host creating DF=1 packets as long as it likes,
including as more and more paths between ITRs and ETRs change
from ~1500 to ~9000 or whatever in the future.

It is the DF=0 packets I think are a problem.  I intend to
handle them up to a certain length - something a little below
1500 bytes.  Longer than that and the ITR will drop them.

I think it is unreasonable for a sending host to expect the
network to fragment its excessively long packets ca. 2015 or
whenever Ivip or the like is deployed.  RFC 1191 is a perfectly
good approach and has been available since 1990.

  - Robin

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Thu Jan 29 18:25:47 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 845D63A6AA4; Thu, 29 Jan 2009 18:25:47 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DCE443A6AA4; Thu, 29 Jan 2009 18:25:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.419
X-Spam-Level: 
X-Spam-Status: No, score=-6.419 tagged_above=-999 required=5 tests=[AWL=0.180,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FkjQQq85bv1N; Thu, 29 Jan 2009 18:25:45 -0800 (PST)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id B39C93A6870; Thu, 29 Jan 2009 18:25:45 -0800 (PST)
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n0U2P9NU016945 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 29 Jan 2009 18:25:12 -0800 (PST)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n0U2P9YO001418; Thu, 29 Jan 2009 18:25:09 -0800 (PST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n0U2P9p7001413; Thu, 29 Jan 2009 18:25:09 -0800 (PST)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 29 Jan 2009 18:25:09 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 29 Jan 2009 18:25:08 -0800
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A10581EB88@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <498260AB.902@firstpr.com.au>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rrg] LISP PMTU - 2 methods in draft-farinacci-lisp-11
Thread-Index: AcmCfxZ/lX1Hn7nISoSN6LVUcgNQVgAAnkaQ
References: <497E9BB2.5040101@firstpr.com.au><497ED66B.8000505@net.t-labs.tu-berlin.de>	<497F0B30.1010404@firstpr.com.au> <39C363776A4E8C4A94691D2BD9D1C9A1057A2DD3@XCH-NW-7V2.nw.nos.boeing.com> <498260AB.902@firstpr.com.au>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Robin Whittle" <rw@firstpr.com.au>, "RRG" <rrg@irtf.org>
X-OriginalArrivalTime: 30 Jan 2009 02:25:09.0185 (UTC) FILETIME=[F8B62B10:01C98281]
Cc: lisp@ietf.org
Subject: Re: [rrg] LISP PMTU - 2 methods in draft-farinacci-lisp-11
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Robin,

I may comment further later, but one clarification for
sure for now:

> -----Original Message-----
> From: Robin Whittle [mailto:rw@firstpr.com.au] 
> Sent: Thursday, January 29, 2009 6:07 PM
> To: RRG
> Cc: Templin, Fred L; lisp@ietf.org
> Subject: Re: [rrg] LISP PMTU - 2 methods in draft-farinacci-lisp-11
> 
> Hi Fred,
> 
> Thanks for these references, and some other PMTUD discussion in
> the "Please respond: Questions from the IESG as to whether a WG
> forming BOF is necessary for LISP" thread, which I will respond
> to here:
> 
> >> I stand corrected about LISP's approach to PMTUD - the latest
> >> draft does include an outline of a workable solution.
> >
> > I don't know if you were fishing for a response,
> 
> No.  I meant it was at least going to work, if the PTBs
> contained the nonce.  It may not work very well, but that is
> better than the stateless approach, which won't work at all.
> 
> > but the
> > stateful solution outlined in the latest LISP draft still
> > has problems. It should also be mentioned that the approach
> > (drop first; return PTBs for subsequent) is not new and
> > has been proposed many times over the years.
> 
> I hadn't heard of this approach before.  I still think it has
> problems.
> 
> > The approach in the current LISP draft still relies on ICMPs
> > coming from anonymous network middleboxes (which Dino himself
> > has said that we cannot depend on),
> 
> Dino clarified this to say that he thinks we can rely on PTBs
> being sent - and generally rely on them being received:
> 
>   http://www.irtf.org/pipermail/rrg/2009-January/000899.html
> 
>     But ICMP TooBig and Time-Exceeded message are sent and are
>     more dependable. That is, they can get lost when they are
>     transmitted since they are single transmitted datagrams. But
>     at least they are sent.
> 
> I assume this is true - it makes sense.  Anyone configuring a
> DFZ router or an internal router between any ITR and ETR would
> be badly mistaken not to allow generation of any PTBs.
> 
> 
> > and provides insufficient
> > means for authenticating any ICMPs that may come. For example,
> > even if the ICMPs were delivered, and even if they included
> > the LISP nonce, it would be impractical for the ITR to cache
> > enough nonces of enough recently-sent packets especially at
> > high data rates.
> 
> I tend to agree, but it depends on how smart the ITR is about
> recognising "longer packets" and only caching details for that
> subset.  There's no need for the ITR to cache a LISP nonce for
> the purposes of PMTUD if the packet is shorter than some
> constant below which it can be assumed there are no MTU
> problems.  So VoIP packets and quite a few others will not need
> to have any nonce or other details cached.
> 
> I wonder if there is a cryptographic approach to generating 32
> bit nonces such that it is not necessary to cache each one in
> order to be able to verify that a nonce in a PTB matched a
> recently sent packet?
> 
> For instance, for a period of a second or two, set a randomly
> selected set of 16 bits in the 32 bit nonce to some particular
> bit pattern, which is pseudo-random, which remains the same for
> the period and is cached.  Then, change the other 16 bits for
> each generated nonce.
> 
> Hmmm - this just makes it easier for an attacker to spoof a nonce.
> 
> Maybe send the same nonce for all packets for 0.1 seconds . . .
> No - if an attacker can get a tunneled packet from this ITR to
> its own ETR then it use the nonce to spoof a PTB apparently from
> a tunnel to another ETR.
> 
> Maybe there is some snappy crypto approach to this, but it needs
> to be lightweight when checking the nonce in a PTB - and
> knowledge of another recent nonce must not allow an attacker to
> improve their chances of spoofing a valid nonce of another
> packet tunneled to some other ETR.
> 
> 
> My plan in:
> 
>   http://www.firstpr.com.au/ip/ivip/pmtud-frag/
> 
> is that a very small subset of packets get the special PMTUD
> treatment.  Every such packet will result in a reduction of the
> zone of uncertainty about the path MTU to the ETR.  Data will
> either be delivered or the ETR and therefore the destination
> network or the ITR will send a valid PTB to the sending host.
> 
> Pretty quickly, ordinary RFC 1191 sending host behaviour will
> result in the zone of uncertainty being reduced to zero.  Then,
> except for occasional attempts to try longer packets than the
> current estimate allows, or to confirm that packets are getting
> through when they are close to, or at, the current MTU limit,
> there is no special treatment of packets and so nothing to
> cache.  (In Ivip, ordinarily tunneled packets hitting an MTU
> limit will not generate a PTB to the ITR - the PTB will go to
> the sending host and not be recognised there.)
> 
> > So, the only option is to ignore ICMPs (leads to black holes)
> > or honor ICMPs (leads to denial of large packet service).
> 
> If the ITR doesn't attempt to recognise PTBs, then it needs some
> other way of determining PMTU to the ETR - which involves
> special protocols between the ITR and ETR.  This is part of what
> I am proposing.
> 
> My approach does recognise PTBs if they are sent with enough of
> the offending packet to contain the nonce in the "Packet B",
> which is the same length as the original traffic packet would
> become with ordinary Ivip encapsulation.  This requires the
> intermediate router send back at least 8 bytes more than the
> bare minimum 8 bytes required by RFC 1911.
> 
> I think it is reasonable to expect DFZ and internal routers to
> do this.  I recall someone writing that many do it already.  It
> would be a straightforward config change or firmware update to
> make sure they all did it in time for the introduction of Ivip
> or any similar system.
> 
> So secure recognition of PTBs is used by my system, but the
> system will still work without PTBs.
> 
> > I have said this before, but AFAICT DF=1 is busted.
> 
> I don't understand why.  My approach should support any RFC 1191
>  sending host creating DF=1 packets as long as it likes,
> including as more and more paths between ITRs and ETRs change
> from ~1500 to ~9000 or whatever in the future.

No - I was not meaning to imply any particular behavior
on the part of the sending host. The sender can set
DF to anything it likes and the ITR can't do anything
about it. I was meaning to say that DF=0 in the *outer*
IP header appended by the ITR during encapsulation.

Fred
fred.l.templin@boeing.com

> It is the DF=0 packets I think are a problem.  I intend to
> handle them up to a certain length - something a little below
> 1500 bytes.  Longer than that and the ITR will drop them.
> 
> I think it is unreasonable for a sending host to expect the
> network to fragment its excessively long packets ca. 2015 or
> whenever Ivip or the like is deployed.  RFC 1191 is a perfectly
> good approach and has been available since 1990.
> 
>   - Robin
> 
> 
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Thu Jan 29 20:55:34 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 44E873A686A; Thu, 29 Jan 2009 20:55:34 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0735B3A686A for <rrg@core3.amsl.com>; Thu, 29 Jan 2009 20:55:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.546
X-Spam-Level: 
X-Spam-Status: No, score=-1.546 tagged_above=-999 required=5 tests=[AWL=0.349,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rMaNWmsU2F-B for <rrg@core3.amsl.com>; Thu, 29 Jan 2009 20:55:31 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123]) by core3.amsl.com (Postfix) with ESMTP id 9661B3A6822 for <rrg@irtf.org>; Thu, 29 Jan 2009 20:55:30 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6]) by gair.firstpr.com.au (Postfix) with ESMTP id 2F12A175D5D; Fri, 30 Jan 2009 15:55:11 +1100 (EST)
Message-ID: <498288B2.6090505@firstpr.com.au>
Date: Fri, 30 Jan 2009 15:57:22 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: rrg@irtf.org
References: <20090128174320.9465E6BE600@mercury.lcs.mit.edu>
In-Reply-To: <20090128174320.9465E6BE600@mercury.lcs.mit.edu>
Cc: int-area@ietf.org, Noel Chiappa <jnc@mercury.lcs.mit.edu>, routing-discussion@ietf.org
Subject: Re: [rrg] [lisp] [Int-area] Please respond: Questions from the IESG as to whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Short version:   Timeline of the LISP-ALT/CONS proposal with
                 respect to APT and Ivip.

                 LISP-ALT development looks rather hasty so far
                 and could proceed quite well without a WG.

                 But maybe a WG is the best way - develop
                 LISP-ALT ASAP and see how attractive it is to
                 the great majority of end-user networks.

                 We need most end-user networks, of all sizes,
                 to want to adopt the solution for their own
                 immediate reasons - otherwise, the solution
                 won't cover enough networks to solve the
                 scaling problem.

                 There is a LISP-ALT snowball.  Forming a
                 LISP WG would push the snowball faster.

                 The more prominence and IETF-given
                 credibility LISP gets, the more this might
                 detract attention from the alternative
                 approaches, including APT and Ivip so far.

                 I think these are more sound from technical
                 and business perspectives than LISP-ALT.
                 These are developed by smaller teams with
                 less resources and experience than the LISP
                 team - but maybe these efforts will result in
                 a better architecture.

Hi Noel,

You wrote:

>> The LISP team should do detailed critiques of APT and Ivip as
>> part of convincing IETF folks of the merits of LISP-ALT.
>
> Perhaps I'm confused, but I don't think the people working on
> LISP are trying to "convince" the IETF as a whole of the
> "merits of LISP".

I don't know the criteria is for creating a WG, but I guess the
IETF doesn't create them except for projects which have
sufficient merit in general, as well as meeting formal criteria.


> If some people out there in the Internet technical community
> think it looks good, and want to work on it, run it, etc,
> that's great; but if other people reach a contrary conclusion,
> and don't want to work on it, run it, etc (as is their
> choice), that's fine too.

I am not completely opposed to there being a LISP-WG.  I am just
saying that I think the LISP development has been hurried in a
number of respects, that it doesn't necessarily need a WG and
that a WG could detract attention from more promising other
approaches.

I think the LISP team could best facilitate progress towards
scalable routing solutions by taking more interest in other
proposals and by discussing in public why they think their
LISP-ALT approach is better than the alternatives.

Their goal is 10 billion EIDs.  Assuming this is not an
unrealistic scaling goal, they need to show why ALT could
work well with this, while APT and Ivip could never do so.


The history, as reflected in Internet Drafts, is something like
this (ignoring LISP-NERD, which doesn't scale due to the need
for every ITR to have a copy of the full mapping database):


2007-01-17 draft-farinacci-lisp-00

           This is a conceptual overview which assumes it is
           impossible to get real-time mapping to the ITRs.
           Therefore, ITRs get multiple ETR addresses and have
           to do reachability testing and ETR choice on their
           own.

           There is detailed description of a useful mapping
           system.

           There is no support for packets sent by hosts in
           networks without ITRs.


2007-07-02 draft-jen-apt-00

           APT is the first core-edge separation scheme to
           document a scalable mapping distribution system in
           in Internet Draft.  The full mapping database is
           distributed (slowly) to local query servers -
           Default Mappers.  As with LISP, ITRs - or rather
           Default Mappers - do their own reachability testing
           and make their own ETR choices.

           It later emerged that APT can support packets sent
           from hosts in non-APT networks, but only, for IPv4,
           if the EID prefix is no longer than the in-practice
           limit of the DFZ: 24 bits.  This limit would
           disappear if APT networks connected not only by
           direct router links, but by tunnels, so there was
           only one global "APT Island".


2007-07-03 draft-meyer-lisp-cons-00

           CONS is LISP's first mapping system which is intended
           to be practical in a scalable routing solution.  It
           is a global query server system which involves delays
           for initial packets.  CONS uses a a novel network
           structure comprised of special router-like devices
           called CARs and CDRs.


2007-07-15 draft-whittle-ivip-arch-00

           Fast (effectively real-time) push of all mapping info
           to local query servers.  I developed this
           independently of APT, but the two proposals involve
           some commonalities: the local query server means that
           there is no significant delay for initial (or any)
           packets.

           Ivip includes Open ITRs in the DFZ (then known,
           incorrectly, as "Anycast ITRs in the Core").  These
           support multihoming, TE etc. for packets sent by
           hosts in networks without ITRs.  A business plan for
           OITRDs appeared in 2008-04-18:

             http://psg.com/lists/rrg/2008/msg01158.html


2007-11-11 draft-fuller-lisp-alt-00

           LISP-ALT replaces CONS as the preferred mapping
           distribution system.  Like CONS, it is a global
           query server system, so it has the problem of
           delaying initial packets.  The ALT routers and
           the overall ALT network are created from pre-
           existing components: BGP, RIB, FIB and GRE.


2007-12-04 RRG message that there will be a LISP BOF regarding
           forming a LISP WG.


2007-12-05 draft-lewis-lisp-interworking-00

           LISP Proxy Tunnel Routers provide support for packets
           sent by hosts in non-upgraded networks.  AFAICT, PTRs
           are functionally identical to Ivip's OITRDs.

           However there was no business plan for PTRs or the
           related questions of how EID space is allocated.
           Dino's reply to my point 6:

             http://www.irtf.org/pipermail/rrg/2009-January/000864.html

           indicates there still is no such business plan.


In the view of many people, the delay of initial packets remains
a serious problem for LISP-ALT.  Part if this delay is due to the
global nature of the query server system.  This is made worse by
the long-path problem where the highly aggregated structure of the
ALT network leads to geographically long tunnels between the ALT
routers, which will often be physically located without much regard
for their place in the ALT topology.

In a recent message:

  http://www.irtf.org/pipermail/rrg/2009-January/000900.html

Dino confirmed the problem of initial packet delay and indicated
there is no alternative to a fully distributed query server system
(as opposed to having the full mapping data in hundreds of
thousands of local query servers, as with APT and Ivip) if the
number of EIDs, micronets etc. is to scale to 10 billion.

Yet in the same message he states (presumably about the
long-term future with 10^10 EIDs) that:

   I envision the number of hops a Map-Request takes is 4
   ALT-router hops.

In LISP-ALT, map queries (or initial traffic packets which are
implicitly map queries) arise in ITRs and need to ascend the
highly aggregated ALT hierarchy until they can cross over to the
part of the hierarchy which matches the destination address.
Then they descend, and reach the authoritative query server -
the ETR which is currently advertising this EID in the ALT
network.  (The map reply from the ETR goes to the ITR directly
via the ordinary Internet.)

There's no way that the ALT network could handle 10 billion
separate EID prefixes and avoid large numbers of ALT routers
- and therefore large numbers of hops up and down the ALT
hierarchy for the typical map request.

A 10 billion EID system could only materialise when most EIDs
are for "end-user networks" are for mobile devices which
everyone and their dog has at least one of.

There will be some number of ITRs and some number of ETRs
- I guess a million or so of each, perhaps often combined
into the one device.

The ETRs collectively advertise 10 billion separate EIDs to
the first level (L1) of ALT router.  How numerous are these?

Each such L1 ALT router needs a GRE tunnel (AFAIK) to every
ETR which is one of those currently active for a EID in the
address range the L1 router is aggregating.

The whole idea of a core-edge separation scheme is that the
EIDs (micronets for Ivip) can be freely used with any ISP
for Internet access - and that each EID can be used with
two or more arbitrarily located ISPs for the purpose of
multihoming.

Ignoring multihoming for a moment, there is still the need
for this first level (L1) of ALT routers to collectively
handle 10 billion EID prefixes.  For any one of these L1
ALT routers, there will sometimes be two or more such EIDs
advertised by the same ETR.  Those two routes share the one
ETR to ALT router GRE tunnel.  (AFAIK, GRE tunnels are used
to link ETRs to ALT routers.)

That is a lot of tunnels - and a lot of L1 routers, such as
a hundred thousand or a million or so.

We don't know how much aggregation will be achieved from
ETR to L1, or from L1 to L2 ALT routers.  Many packets
from ITRs will need to ascend to some high level in the
ALT hierarchy before there is a route to the branch of
the hierarchy they need to descend in order to reach
the ETR.

So I don't think it is reasonable for LISP people to say
their system scales to 10^10 EIDs while any other
system definitely can't.

See also a recent RRG discussion "Economic issues of long-
path / stretched routing" where Scott Brim discusses each ETR
announcing its EID prefix to ALT routers at multiple levels
above the first level.  Each such announcement involves a
GRE tunnel (AFAIK) and perhaps constitutes a BGP neighbour
for the ALT router.  This sort of thing is needed to make the
ALT network robust against failure, but it also makes it much
more complex and less able to be flattened into a few levels
- as would be required to reduce the total path length from
ITRs to ETRs.

I mention these difficulties as an example of the mismatch
between the expectations the LISP developers have - for LISP
and therefore, implicitly for APT, Ivip etc. - and the
confidence some LISP developers express in solving the
fundamental problems which have been identified with ALT.


> Sure, the people working on LISP would like to convince _some_
> people that it's a good idea, so they get i) some help working
> on it (as much remains to be done), and ii) some places to
> deploy it (so some practical experience can be gained, in
> seeing how well it works, what problems crop up in actual
> service, etc), but that's a very different kettle of fish.

I fully support all this.  As far as I know an IETF WG is not
required to do any of this.  Maybe a WG would help.  Maybe
the imprimatur of the IETF in deciding that LISP in its current
state is worthy of a WG will encourage more people to help with
LISP.

However, if a WG results in LISP gaining still more prominence,
then I think there could be a serious downside: making it
harder for other proposals to attract the same sort of interest,
attention and involvement.

I believe the initial packet delay problems and the general
fragility of any global query server system such as LISP-ALT
will ultimately sink any such proposal.  Maybe it won't sink in
the IETF, but it will fail to gain the widespread, ideally
ubiquitous,support from end-user networks which will be required
for any routing scaling solution to succeed.

I am sure that the only practical solution is of the core-edge
separation class (LISP, APT, Ivip, TRRP and maybe RANGER - I
still have to read it).

The only scalable way to avoid initial packet delays is to use
local query servers.  I think a system such as APT of Ivip would
be scalable, practical and attractive - and that something like
LISP-ALT will never be attractive enough to be widely accepted.

By the time we get to 10 billion EIDs, micronets or whatever -
which may be never - RAM and CPU power for local query servers
will be way cheaper and more plentiful than today.

Local query servers based on COTS servers today would be fine
with 100 million EIDs in RAM.  For IPv4, for Ivip, each
micronet's mapping information is only 12 bytes and could
probably be stored in less.  IPv6 mapping is more bloated, but
still, there is even more time before that is widely adopted -
more time for RAM to get more plentiful still.

The rate of change of mapping is well within practical limits
for sending to hundreds of thousands of query servers -
especially using a purpose built, streamlined, crosslinked
fan-out system as I propose with Ivip.  Even with mobility,
using the TTR approach to mobility does not result in high
rates of change of mapping.  For instance a mapping change
is only typically required when the MN moves more than about
1000km.


LISP-ALT is the most frequently discussed solution to the routing
scaling problem.  Yet it is a more recent development than APT or
Ivip - and I think it is the most problematic of the three.

I think the prominence of LISP-ALT is not a function of its
technical merits, but more a result of:

  1 - Four or more people working on it, rather than two or so
      (APT) or basically one (Ivip).

  2 - Some employer support for the LISP developers, including
      for travel to meetings and hardware to run a test
      network.  (The APT developers are studying and I am
      self employed.)

  3 - The greater experience of the LISP developers compared
      to that of the other developers - and likewise being
      better known to RRG participants.

  4 - Greater brand recognition for "Cisco" compared to
      the names of developers of alternatives: APT, Ivip,
      TRRP, Six/One Router and now, I think, RANGER.


A WG may overly focus attention on on LISP-ALT and so detract
from the attention and effort needed to develop the more
promising approaches.

 - Robin



_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Thu Jan 29 21:26:20 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9EAA93A6A19; Thu, 29 Jan 2009 21:26:20 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BDD7D3A6A19 for <rrg@core3.amsl.com>; Thu, 29 Jan 2009 21:26:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.515
X-Spam-Level: 
X-Spam-Status: No, score=-6.515 tagged_above=-999 required=5 tests=[AWL=0.084,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E7v6C4NDgSoo for <rrg@core3.amsl.com>; Thu, 29 Jan 2009 21:26:19 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by core3.amsl.com (Postfix) with ESMTP id 067613A6880 for <rrg@irtf.org>; Thu, 29 Jan 2009 21:26:18 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 5B9806BE56F; Fri, 30 Jan 2009 00:25:57 -0500 (EST)
To: rrg@irtf.org
Message-Id: <20090130052557.5B9806BE56F@mercury.lcs.mit.edu>
Date: Fri, 30 Jan 2009 00:25:57 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: Re: [rrg] [lisp] [Int-area] Please respond: Questions from the IESG as to whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

    > From: Robin Whittle <rw@firstpr.com.au>

    >> I don't think the people working on LISP are trying to "convince" the
    >> IETF as a whole of the "merits of LISP".

    > I don't know the criteria is for creating a WG, but I guess the IETF
    > doesn't create them except for projects which have sufficient merit in
    > general

Sure - but that is not in contradiction to my statement above. The IETF has a
long history of creating WG's to work on different alternatives. In such
circumstances, WG's simply serve to create standards in an _open_ way; they
do not in any way imply any sort of official IETF preference.

    > I think the LISP team could best facilitate progress towards scalable
    > routing solutions by ... discussing in public why they think their
    > LISP-ALT approach is better than the alternatives.

The community has been discussing these issues for years, going back to
things like Multi6. It's been discussed to death already.

	Noel
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Thu Jan 29 21:37:27 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1CB783A6A64; Thu, 29 Jan 2009 21:37:27 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 766E03A6A64 for <rrg@core3.amsl.com>; Thu, 29 Jan 2009 21:37:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.556
X-Spam-Level: 
X-Spam-Status: No, score=-1.556 tagged_above=-999 required=5 tests=[AWL=0.339,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WPaGg9Af7zBF for <rrg@core3.amsl.com>; Thu, 29 Jan 2009 21:37:25 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123]) by core3.amsl.com (Postfix) with ESMTP id 94E423A6A59 for <rrg@irtf.org>; Thu, 29 Jan 2009 21:37:25 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6]) by gair.firstpr.com.au (Postfix) with ESMTP id 86F71175F4B; Fri, 30 Jan 2009 16:37:05 +1100 (EST)
Message-ID: <49829284.5060209@firstpr.com.au>
Date: Fri, 30 Jan 2009 16:39:16 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: rrg@irtf.org
References: <20090130052557.5B9806BE56F@mercury.lcs.mit.edu>
In-Reply-To: <20090130052557.5B9806BE56F@mercury.lcs.mit.edu>
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: [rrg] [lisp] [Int-area] Please respond: Questions from the IESG as to whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Only to the RRG list, following Noel's lead:

Hi Noel,

You wrote:

>> I don't know the criteria is for creating a WG, but I guess the IETF
>> doesn't create them except for projects which have sufficient merit in
>> general
> 
> Sure - but that is not in contradiction to my statement above. The IETF has a
> long history of creating WG's to work on different alternatives. In such
> circumstances, WG's simply serve to create standards in an _open_ way; they
> do not in any way imply any sort of official IETF preference.

OK.  I understand that especially for an experimental set of
RFCs establishing a WG doesn't mean an implication that other
alternatives are not so viable.  Still, it involves the IETF
devoting resources and implicitly inviting others to devote
resources.

I understand the desire to have something developed in an open
and indeed rather standardized manner, in preference to a more
closed or ad-hoc approach.


>> I think the LISP team could best facilitate progress towards scalable
>> routing solutions by ... discussing in public why they think their
>> LISP-ALT approach is better than the alternatives.
> 
> The community has been discussing these issues for years, going back to
> things like Multi6. It's been discussed to death already.

Yet there's still plenty of life in the debate!

  - Robin

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Fri Jan 30 10:05:44 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C8D0028C2E4; Fri, 30 Jan 2009 10:05:44 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5A22928C2E4 for <rrg@core3.amsl.com>; Fri, 30 Jan 2009 10:05:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.514
X-Spam-Level: 
X-Spam-Status: No, score=-6.514 tagged_above=-999 required=5 tests=[AWL=0.085,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6v6apnktdCXr for <rrg@core3.amsl.com>; Fri, 30 Jan 2009 10:05:43 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 3992D28C2E2 for <rrg@irtf.org>; Fri, 30 Jan 2009 10:05:43 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,352,1231113600"; d="scan'208";a="239999315"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-6.cisco.com with ESMTP; 30 Jan 2009 18:04:25 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n0UI4Pvr010963;  Fri, 30 Jan 2009 10:04:25 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id n0UI4P6Y003589; Fri, 30 Jan 2009 18:04:25 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Fri, 30 Jan 2009 10:04:24 -0800
Received: from [10.24.197.201] ([10.21.145.160]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Fri, 30 Jan 2009 10:04:24 -0800
Message-Id: <B0585DFE-4A47-481C-BABB-881BF179F827@cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: Robin Whittle <rw@firstpr.com.au>
In-Reply-To: <498288B2.6090505@firstpr.com.au>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Fri, 30 Jan 2009 10:04:21 -0800
References: <20090128174320.9465E6BE600@mercury.lcs.mit.edu> <498288B2.6090505@firstpr.com.au>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 30 Jan 2009 18:04:24.0283 (UTC) FILETIME=[2EF7B2B0:01C98305]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=327; t=1233338665; x=1234202665; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dino@cisco.com; z=From:=20Dino=20Farinacci=20<dino@cisco.com> |Subject:=20Re=3A=20[rrg]=20[lisp]=20[Int-area]=20Please=20 respond=3A=20Questions=20from=20the=20IESG=20as=20to=20wheth er=20a=20WG=20forming=20BOF=20is=20necessary=20for=20LISP |Sender:=20; bh=jbZgLrjJ71oMqaR/4gi0EfxvAMT1v51H4Ds7bzDYa1I=; b=MaADd9KwKRrQaJYpIlL0oG9Qa+dasIhcpfVr+iW3xH3996o6fpFhNiv70m az0cEL1kWaaRgqUVUuPjco0eDKA9cKF+JpaklMdE/dHqeR+zCFp7BEggS+ou dFparWf+jB;
Authentication-Results: sj-dkim-2; header.From=dino@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); 
Cc: rrg@irtf.org, int-area@ietf.org, Noel Chiappa <jnc@mercury.lcs.mit.edu>, routing-discussion@ietf.org
Subject: Re: [rrg] [lisp] [Int-area] Please respond: Questions from the IESG as to whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

> I am not completely opposed to there being a LISP-WG.  I am just
> saying that I think the LISP development has been hurried in a
> number of respects, that it doesn't necessarily need a WG and
> that a WG could detract attention from more promising other
> approaches.

How about the world is going too slow?

Dino

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Fri Jan 30 13:21:25 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C153D28C122; Fri, 30 Jan 2009 13:21:25 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 438B63A6B04; Fri, 30 Jan 2009 13:21:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.423
X-Spam-Level: 
X-Spam-Status: No, score=-6.423 tagged_above=-999 required=5 tests=[AWL=0.176,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id niYcOwkv4kwk; Fri, 30 Jan 2009 13:21:23 -0800 (PST)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by core3.amsl.com (Postfix) with ESMTP id 0FE433A67FA; Fri, 30 Jan 2009 13:21:22 -0800 (PST)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n0ULKln6013010 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 30 Jan 2009 15:20:52 -0600 (CST)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n0ULKlXw018180; Fri, 30 Jan 2009 15:20:47 -0600 (CST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n0ULKVmJ017920; Fri, 30 Jan 2009 15:20:47 -0600 (CST)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 30 Jan 2009 13:20:45 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 30 Jan 2009 13:20:45 -0800
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A10581F02F@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <B0585DFE-4A47-481C-BABB-881BF179F827@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RANGER BOF - call for participation
Thread-Index: AcmDBTLZUbaYGQdGQ1aj2tAZfubKMAAGdDEA
References: <20090128174320.9465E6BE600@mercury.lcs.mit.edu><498288B2.6090505@firstpr.com.au> <B0585DFE-4A47-481C-BABB-881BF179F827@cisco.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: <rrg@irtf.org>, <int-area@ietf.org>
X-OriginalArrivalTime: 30 Jan 2009 21:20:45.0736 (UTC) FILETIME=[9D42C280:01C98320]
Subject: [rrg] RANGER BOF - call for participation
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

A community of interest is being formed to gauge
whether there is sufficient interest to host a BOF
on "Routing and Addressing in Next-Generation
EnteRprises (RANGER)" at IETF74.

Please see below for proposed BOF agenda, and comment
on the RRG and int-area lists while we wait for the
ranger list to come up.

Fred Templin
fred.l.templin@boeing.com



Routing and Addressing in Next-Generation EnteRprises (RANGER) BOF
===================================================================

Chairs:  TBD

Reponsible AD:  TBD (INT Area; Routing Area)

Mailing List:  ranger at ietf.org
To Subscribe: https://www.ietf.org/mailman/listinfo/ranger
Archive: http://www.ietf.org/mail-archive/web/ranger

Duration:  2 hours

Expected Attendance: 50

Conflicts: LISP BOF, NAT66 BOF, int-area open meeting,
           IRTF rrg meeting

Summary
=======

RANGER [1] is a scalable architecture for routing and
addressing in next-generation enterprise networks, where
an "enterprise" [2] can be as small as a SOHO network,
as dynamic as a Mobile Ad-hoc Network (MANET) [3] or as
large as the global Internet itself [4]. The architecture
is manifested through Virtual Enterprise Traversal (VET)
[5], in which IP-in-IP encapsulation provides a virtual
view of each enterprise as a Non-Broadcast, Multiple-
Access (NBMA) link.

RANGER is recursive, in that multiple enterprises can be
joined together in a nested "enterprise-within-enterprise"
fashion. In this way, the same RANGER principles that
apply in lower levels of recursion can extend upwards
to parent enterprises and ultimately to the core of the
global Internet itself. Furthermore, it is also worth
considering whether today's global Internet represents a
limiting condition for recursion, or if other Internets
could be manifested as "parallel universes" and joined
together at still higher levels of recursion.

The RANGER architecture is manifested through composite
technologies including Virtual Enterprise Traversal (VET),
the Subnetwork Encapsulation and Adaptation Layer (SEAL)
[6], the Intra-Site Automatic Tunnel Addressing Protocol
(ISATAP) [7], and many others. Noting that combinations
with other technologies are also possible, the issues
addressed either in full or in part by RANGER include:

- IPv6/IPv4 coexistence and transition
- scalable routing and addressing
- provider-independent addressing and its
  relation to provide-aggregated addressing
- site mobility and multi-homing
- ingress filtering for multi-homed sites
- address and prefix autoconfiguration
- border router discovery
- router-to-router tunneling
- neighbor discovery over tunnels
- MTU determination for tunnels.

As seen in the above list, the RANGER architecture
provides a framework for addressing a broad range of
problem areas that currently limit the functionality,
growth and maturation of today's Internet. Therefore,
it is the purpose of this BOF to discuss the formation
of an IETF WG to produce the following work items:

1) An Informational RFC describing the RANGER architecture.
   This document to provide a high-level overview of the
   RANGER enterprise-within-enterprise framework, its
   constituent technologies, and its domain of
   applicability.

2) An RFC specification of Virtual Enterprise Traversal
   (VET). This document to specify the inner workings of
   IP-in-IP encapsulation and its associated mechanisms
   within the RANGER context.

3) An RFC specification of the Subnetwork Encapsulation
   and Adaptation Layer (SEAL). This document to specify
   an encapsulation sublayer used to provide enhanced
   packet identification and tunnel MTU robustness.

4) Other work items within scope as determined, e.g.,
   by working group/BOF consensus, etc.

Agenda
======

- Administrivia (Chairs, 5 min)

- Purpose of BOF (Chairs, 10 min) [see above]

- Routing and Addressing in Next Generation EnteRprises
  (RANGER) (20 min)

- Virtual Enterprise Traversal (VET) (20 min)

- Subnetwork Encapsulation and Adaptation Layer (SEAL)
  (20 min)

- Proposed Charter (Chairs, 10 min)

- Questions/Next Steps (Chairs, 30 min)


Documents:
==========

[1] Templin, F., "Routing and Addressing in Next-Generation
    EnteRprises (RANGER), 'draft-templin-ranger',
    work-in-progress, January 2009.

[2] Bound, J., et. al., "IPv6 Enterprise Network Analysis -
    IP Layer 3 Focus", IETF RFC 4852, April 2007.

[3] Corson, S., et. al., "Mobile Ad hoc Networking (MANET):
    Routing Protocol Performance Issues and Evaluation
    Considerations", IETF RFC 2501, January 1999.

[4] IRTF Routing Research Group, http://www.irtf.org/rrg

[5] Templin, F., "Virtual Enterprise Traversal (VET)",
    'draft-templin-autoconf-dhcp', work-in-progress,
    January 2009.

[6] Templin, F., "Subnetwork Encapsulation and Adaptation
    Layer (SEAL)", 'draft-templin-seal', work-in-progress,
    December 2009.

[7] Templin, F., et. al., "Intra-Site Automatic Tunnel
    Addressing Protocol (ISATAP)", IETF RFC 5214, March 2008. 
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Fri Jan 30 15:10:23 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BD8FE28C163; Fri, 30 Jan 2009 15:10:23 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B9EDB28C15E for <rrg@core3.amsl.com>; Fri, 30 Jan 2009 15:10:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_43=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O0VjgGr4Za5E for <rrg@core3.amsl.com>; Fri, 30 Jan 2009 15:10:21 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 9AE0028C153 for <rrg@irtf.org>; Fri, 30 Jan 2009 15:10:21 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,354,1231113600"; d="scan'208";a="132114753"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-3.cisco.com with ESMTP; 30 Jan 2009 23:09:03 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n0UN933q028292;  Fri, 30 Jan 2009 15:09:03 -0800
Received: from vaf-lnx1.cisco.com (vaf-lnx1.cisco.com [171.71.118.48]) by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n0UN932E009281; Fri, 30 Jan 2009 23:09:03 GMT
Received: by vaf-lnx1.cisco.com (Postfix, from userid 113818) id 343555CC033; Fri, 30 Jan 2009 15:18:40 -0800 (PST)
Date: Fri, 30 Jan 2009 15:18:40 -0800
From: Vince Fuller <vaf@cisco.com>
To: Robin Whittle <rw@firstpr.com.au>
Message-ID: <20090130231840.GA24291@cisco.com>
References: <20090128174320.9465E6BE600@mercury.lcs.mit.edu> <498288B2.6090505@firstpr.com.au>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <498288B2.6090505@firstpr.com.au>
User-Agent: Mutt/1.5.17+20080114 (2008-01-14)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1062; t=1233356943; x=1234220943; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=vaf@cisco.com; z=From:=20Vince=20Fuller=20<vaf@cisco.com> |Subject:=20Re=3A=20[rrg]=20[lisp]=20[Int-area]=20Please=20 respond=3A=20Questions=20from=20the=0A=09IESG=20as=20to=20wh ether=20a=20WG=20forming=20BOF=20is=20necessary=20for=20LISP |Sender:=20; bh=z1i3jhzYWvU0c0HPtmo7AaAjgtQamKZZkVota8VfNho=; b=cWpXQNkuhoBTJLadd1UBUHXRRejrAsZ6gHigAlW+1S3pB2tkBDaPJxURSy 12YklcgE8lK8CWe+0B9LgnjDj3oZRJDHarNwIY+hu/s/z4JA6473Govssbt9 9EhqLkrSuF;
Authentication-Results: sj-dkim-2; header.From=vaf@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); 
Cc: rrg@irtf.org, int-area@ietf.org, Noel Chiappa <jnc@mercury.lcs.mit.edu>, routing-discussion@ietf.org
Subject: Re: [rrg] [lisp] [Int-area] Please respond: Questions from the	IESG as to whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

> LISP-ALT is the most frequently discussed solution to the routing
> scaling problem.  Yet it is a more recent development than APT or
> Ivip - and I think it is the most problematic of the three.

As I have explained more than once already, your timeline is simply wrong.

The base LISP spec, draft-farinacci-lisp-11.txt in its current incarnation,
was a direct result of design discussions that occurred in October, 2006,
at the IAB-sponsored Routing and Addressing Workshop in Amsterdam. The first
version of draft-farinacci-lisp appeared for select reviewers on December 1st,
2006 and was published on January 22nd, 2007.

The LISP+ALT spec, draft-fuller-lisp-alt-03.txt in its current incarnation
(and originally termed "LISP 1.5"), was a direct result of discussions at a
lunch meeting during the November, 2006 IETF plenary in San Diego. Small
group discussions occurred for several months prior to taking it to the RAM
list in June, 2007 though the first version of the draft was not published 
until November, 11th, 2007.

	--Vince
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Fri Jan 30 20:28:26 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 554133A695A; Fri, 30 Jan 2009 20:28:26 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 143CF3A695A for <rrg@core3.amsl.com>; Fri, 30 Jan 2009 20:28:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.261
X-Spam-Level: 
X-Spam-Status: No, score=-1.261 tagged_above=-999 required=5 tests=[AWL=0.034,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, J_CHICKENPOX_43=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3GUVUU5tDzWm for <rrg@core3.amsl.com>; Fri, 30 Jan 2009 20:28:23 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123]) by core3.amsl.com (Postfix) with ESMTP id A82403A6784 for <rrg@irtf.org>; Fri, 30 Jan 2009 20:28:22 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6]) by gair.firstpr.com.au (Postfix) with ESMTP id 9AF64175B84; Sat, 31 Jan 2009 14:59:47 +1100 (EST)
Message-ID: <4983CD37.2000207@firstpr.com.au>
Date: Sat, 31 Jan 2009 15:01:59 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: rrg@irtf.org
References: <20090128174320.9465E6BE600@mercury.lcs.mit.edu>	<498288B2.6090505@firstpr.com.au> <20090130231840.GA24291@cisco.com>
In-Reply-To: <20090130231840.GA24291@cisco.com>
Cc: int-area@ietf.org, Noel Chiappa <jnc@mercury.lcs.mit.edu>, routing-discussion@ietf.org
Subject: Re: [rrg] [lisp] [Int-area] Please respond: Questions from the	IESG as to whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Short version:      LISP-ALT seems liked a rushed development
                    which won't be widely enough adopted even if
                    there are RFCs and interoperable
                    implementations by 2012.

                    The work which preceded the various I-Ds.


Dino, in response to my concern that the LISP-ALT development is
too rushed, you wrote:

> How about the world is going too slow?

In the 2.3 years since RAWS in Amsterdam the DFZ routing table
has grown from about 200k to about 275k.  There may be a slight
glitch downwards due to the economic crisis in recent months:

  http://bgp.potaroo.net/bgprpts/bgp-active.png

That is a growth rate of about 15% PA.

We have growing problems with:

  1 - This growth rate increasing the cost of of routers
      in the DFZ, which is a burden on all ISPs and therefore
      all Internet users.

  2 - Excessive constraints in PI space which is an attempt to
      reduce the above growth rate.

  3 - With the increasing number of end-user networks which want
      multihoming, inbound traffic engineering and portability
      either not being able to get any of these, or having to
      pay much more for it (and cause burdens on the DFZ) than
      would be the case with a good scalable routing solution.

Whenever IPv6 is widely adopted, the same things will happen
there too.

However, I don't think these problems are so urgent that we
should rush into re-engineering the Net with a poorer solution
than if we spent a few more years working on it.  We will be
stuck with the solution for decades.

I imagine you could create LISP-ALT RFCs by the end of 2010 and
have interoperable implementations in software and in some
hardware routers by the end of 2011.

But I can't see how you are going to get the widespread adoption
of LISP-ALT EID space by most end-user networks (which want
multihoming, TE and portability), from the smallest (SOHO etc.)
to the largest (corporations, universities and government
departments) in 2012 or at any other time.

By then you will probably have figured out business arrangements
for EID allocation and for running PTRs.  I imagine it would be
be similar to parts of:

  http://psg.com/lists/rrg/2008/msg01158.html

You will probably have also solved the PMTUD problem with a
judicious use of the OpenLISP stateful approach, requiring all
DFZ routers to return 16 bytes or more past the IP header in
their PTB messages, minimising the number of packets the ITR
stores the nonce for and allowing for occasional checking for
growth or reduction in the path MTU to each ETR.  I think the
result would resemble:

  http://www.firstpr.com.au/ip/ivip/pmtud-frag/


LISP-ALT would still have the initial packet delay problem, the
long-path problem and the difficulties in building a big ALT
network which has redundancy and meshiness - or whatever is
required for robustness.

None of these problems would present serious practical
difficulties in the test network or in the first months or year
or two of deployment - because there would be small number of
ALT routers.

However, anyone concerned about the long-term future would be
well aware of these problems.  I don't think you can solve these
problems in any elegant, efficient manner - because they are
fundamental problems with the LISP-ALT architecture.

ALT is certainly more elegant than CONS, with its new network
elements of CARs and CDRs which needed to be created from scratch.

AFAIK, an ALT router can be created by correctly configuring
various functional elements which are already present in a good,
flexible, hardware-based or software-only router.

The ITR and ETR functions need new code.

By 2011, I figure you would also have figured out standardised
approaches by which an ISP could manage its ETRs to securely
make tunnels to the upstream ALT routers it needs to get map
request messages.

You would also need a secure and reasonably automated method by
which end-user networks could identify themselves to ISP ETRs
for the purposes of telling the ETR their EID, so the ETR would
be prepared to convey mapping for that EID to the ALT routers.

Maybe you will make the ALT network handle the initial packets
(which also function as map requests) - but then the ALT network
needs much greater capacity, for a small reduction in the delay
of initial packets.

That would worsen the traffic burden on ALT routers and require
more care about the commercial relationships between all the
organisations who run these ALT routers.  No-one is going to
carry packets with a bunch of mapping requests, and especially
the greater volume of initial traffic packets, unless they get
paid by whoever sends them and/or whoever accepts them.


Circa 2012, I think it would be unlikely that any large end-user
network which already has PI space would want to convert it to
LISP EID space.  They would need to run PTRs for that space.
That is not so hard if all the EIDs are still in the one
geographic area.  However, if they wanted to use their EIDs
anywhere on the Net, they would need PTRs in or near such
locations.  They would gain the ability to split their address
space for physically separate (in terms of BGP border router)
sites into smaller pieces than the current BGP /24 limitation
allows.  This will become more important as IPv4 space becomes
more and more valuable - but only for networks which have many
sites they want to connect via multiple, physically separate, ISPs.

However, all their network would now suffer from the initial
packet delay problem.  Initially, that might be tolerable for a
university.  But any corporation which is vying for customers
and wants its web-sites to be responsive would look into the
future and see that LISP-ALT's long-path problem is going to get
worse if and when it becomes very widely adopted.

You may well be able to get some adoption of LISP EID space by
smaller networks which can't get PI space today.

ISPs would presumably be able to run ITRs and ETRs without major
expense - either with firmware updates for their existing
routers of via inexpensive or open-source software to run on
COTS servers, at least initially.

By then - 2013 or beyond - other scalable routing solutions will
be better developed and probably have their own WGs, test
networks etc.  I think the scalable routing problem would be
more widely known within and beyond the IETF - especially as
IPv4 space becomes more scarce and valuable.

I can't imagine that LISP-ALT could scale well to your stated
goal of 10^10 EIDs.  As I wrote previously, the ALT network
would have to be so vast that the initial packet delay problem
would be serious, - especially with meshiness or whatever for it
to be robust.  This will affect some DNS requests and replies
too, not just TCP SYN and ACK packets.

The smaller and more numerous the ITRs (to spread the load of
traffic) the more problems there will be with initial packet
delay due to the ITRs not having the mapping already cached.
More numerous ITRs will also drive up the query traffic on the
ALT network.

The local query server schemes (APT and Ivip) have no initial
packet delay problems.  They need to distribute and store
mapping data all over the Net, slowly or in real-time.  Today's
COTS (Commercial Off The Shelf) servers can store and transfer
the data just fine for 10^8 to 10^9 EIDs/micronets.  If and when
we get to 10^10 EIDs/micronets (the vast majority of which must
be for personal mobile devices), a COTS server will probably
have 10^1 or 10^2 times more RAM, CPU power etc.

The mapping distribution for APT and Ivip can be done with
purpose-built, streamlined, mechanisms which are not as fussy as
a LISP-ALT-style global query server network where the whole
thing depends on a lonely query packet traversing a global-scale
network, and its equally lonesome response packet making its way
back via the Internet.

I doubt that anything other people write will convince you not
to push/rush ahead with LISP-ALT.  If you can't imagine a better
architecture, then I think you should develop it ASAP - in a WG.

My point in writing is to remind onlookers that there are other
people in this field who think ALT has too many fundamental
problems to be the optimal long-term scalable routing
architectural enhancement for the Internet - and that there are
other approaches, which are being developing more slowly, which
show much greater promise.


Vince, thanks for filling in the background on the Internet
Draft dates I listed.  You wrote:

>> LISP-ALT is the most frequently discussed solution to the routing
>> scaling problem.  Yet it is a more recent development than APT or
>> Ivip - and I think it is the most problematic of the three.
> 
> As I have explained more than once already, your timeline is simply wrong.

My timeline was stated to be in terms of I-D publication dates,
which are correct.


> The base LISP spec, draft-farinacci-lisp-11.txt in its current incarnation,
> was a direct result of design discussions that occurred in October, 2006,
> at the IAB-sponsored Routing and Addressing Workshop in Amsterdam. The first
> version of draft-farinacci-lisp appeared for select reviewers on December 1st,
> 2006 and was published on January 22nd, 2007.

I recall someone writing that APT development was taking place
in late 2006 too.


> The LISP+ALT spec, draft-fuller-lisp-alt-03.txt in its current incarnation
> (and originally termed "LISP 1.5"), was a direct result of discussions at a
> lunch meeting during the November, 2006 IETF plenary in San Diego. Small
> group discussions occurred for several months prior to taking it to the RAM
> list in June, 2007 though the first version of the draft was not published 
> until November, 11th, 2007.

The only June 2007 message I can find which relates to ALT is
your "Preliminary thoughts on LISP 1.5" (2007-07-21), which is
largely a private message from 2007-04-04:

  http://www.ietf.org/mail-archive/web/ram/current/msg01562.html

This includes "we're looking for alternative methods  that don't
introduce enormous amounts of  complexity".  Looking back, this
is clearly an early description of LISP-ALT.  Maybe it is also
an early description of CONS, which appeared in an I-D on
2007-07-30.

If you developed ALT so early, then I don't understand why you
published and promote CONS in July 2007  CONS is harder to
understand, design and implement than ALT, and is still a global
query server system.

I was the only person to write a substantial response to the
above mentioned message, noting that I couldn't clearly
understand it - and that point 6 appeared to describe the same
thing as my Ivip "Anycast ITRs in the core", now known as Open
ITRs in the DFZ (OITRDs).

Despite Dino and I think others either criticised or ignored my
"Anycast ITR in the Core" idea from 2007-06-15 onwards.  The the
same idea materialised as LISP Proxy Tunnel Routers on
2007-12-05 in draft-lewis-lisp-interworking-00.

My timeline concerned I-D dates.  Since you mention the work
which preceded this, here are the Ivip dates:

I thought of (what were later known as) OITRDs and the overall
TTR mobility scheme on 2007-06-14 and posted it to the RAM list
the next day.  All other Ivip things were developed after that.

Urged on by Dino and others, I wrote up an I-D ASAP.  This, in
2007-07-15, also included the fast push mapping distribution
system and local query servers - both full-database and caching,
with the ITR being notified if the mapping changed for any
micronet it recently requested mapping for.  This I-D also
included ITR functions in sending hosts.

 - Robin

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Sat Jan 31 01:50:39 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E9ED73A69F3; Sat, 31 Jan 2009 01:50:38 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0A5243A687C for <rrg@core3.amsl.com>; Sat, 31 Jan 2009 01:50:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.516
X-Spam-Level: 
X-Spam-Status: No, score=-6.516 tagged_above=-999 required=5 tests=[AWL=0.083,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o1P8Bduh-bVw for <rrg@core3.amsl.com>; Sat, 31 Jan 2009 01:50:37 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 217833A6A95 for <rrg@irtf.org>; Sat, 31 Jan 2009 01:50:37 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,355,1231113600"; d="scan'208";a="240393524"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-6.cisco.com with ESMTP; 31 Jan 2009 09:50:18 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n0V9oImd012606;  Sat, 31 Jan 2009 01:50:18 -0800
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n0V9oIL4015618; Sat, 31 Jan 2009 09:50:18 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Sat, 31 Jan 2009 01:50:18 -0800
Received: from [10.140.1.116] ([10.21.114.115]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Sat, 31 Jan 2009 01:50:17 -0800
Message-Id: <6B3C8F95-1569-40B5-B2CD-9DEE4DDFDDBA@cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: Robin Whittle <rw@firstpr.com.au>
In-Reply-To: <4983CD37.2000207@firstpr.com.au>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Fri, 30 Jan 2009 23:55:42 -0800
References: <20090128174320.9465E6BE600@mercury.lcs.mit.edu>	<498288B2.6090505@firstpr.com.au> <20090130231840.GA24291@cisco.com> <4983CD37.2000207@firstpr.com.au>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 31 Jan 2009 09:50:18.0106 (UTC) FILETIME=[52E1D5A0:01C98389]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=873; t=1233395418; x=1234259418; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dino@cisco.com; z=From:=20Dino=20Farinacci=20<dino@cisco.com> |Subject:=20Re=3A=20[rrg]=20[lisp]=20[Int-area]=20Please=20 respond=3A=20Questions=20from=20the=09IESG=20as=20to=20wheth er=20a=20WG=20forming=20BOF=20is=20necessary=20for=20LISP |Sender:=20; bh=qnXDgfJTDVowhsgn8TIAW8z6oQP493Ufk5ALKzemlxc=; b=IyEr9FRGO0WxbJPBC4SzRDJVaRlU5GsQgOfVv6pFF4qUT+QzpLBzQvpK7Y n/zq7NbEaIcaLGqmXnck3oKSI14gLIZXTSIpjPOWNcMedZ2Hm5luQOyy3WWl tudJFtNF+4;
Authentication-Results: sj-dkim-2; header.From=dino@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); 
Cc: rrg@irtf.org, int-area@ietf.org, Noel Chiappa <jnc@mercury.lcs.mit.edu>, routing-discussion@ietf.org
Subject: Re: [rrg] [lisp] [Int-area] Please respond: Questions from the	IESG as to whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

> I imagine you could create LISP-ALT RFCs by the end of 2010 and
> have interoperable implementations in software and in some
> hardware routers by the end of 2011.

Writing RFCs is probably the first 10% to completion.

You know how long it takes for multiple vendor implementations to get  
released, documentation to be complete and accurate? And then the long  
evaluation cycle for deployment and then what you learn through this  
process needs to be fed back in. And sometimes you have to restart  
some of these steps?

Of course we don't want to rush, but never assume we have time.

Did we assume we had time for Dual-Stack deployment so when IPv6-only  
sites get deployed (which might possibly happen in the next year or  
so), we could have IPv6 in the infrastructure? We missed that boat and  
we are in a heap of trouble now. Sad.

Dino
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Sat Jan 31 11:50:16 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8530C3A6A8E; Sat, 31 Jan 2009 11:50:16 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 16EC63A6A8E; Sat, 31 Jan 2009 11:50:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7kwwtJ4weDxQ; Sat, 31 Jan 2009 11:50:14 -0800 (PST)
Received: from mo-p05-ob.rzone.de (mo-p05-ob.rzone.de [81.169.146.182]) by core3.amsl.com (Postfix) with ESMTP id 7C0AB3A67DA; Sat, 31 Jan 2009 11:50:13 -0800 (PST)
X-RZG-CLASS-ID: mo05
X-RZG-AUTH: :IW0NeQWrc+lwhhNjh1Z2K6NdlYX3YUP3q0u9WROmBvx7THszQ1iClCjh
Received: from [10.0.1.2] (c-71-198-187-109.hsd1.ca.comcast.net [71.198.187.109]) by post.strato.de (klopstock mo40) (RZmta 18.15) with ESMTP id L02617l0VJZoUu ; Sat, 31 Jan 2009 20:49:47 +0100 (MET)
Message-Id: <4829FA05-B2FF-4F39-8B4F-1810C472E447@ericsson.com>
From: Christian Vogt <christian.vogt@ericsson.com>
To: Dino Farinacci <dino@cisco.com>
In-Reply-To: <83BCD1E8-9EDB-4D81-94E1-0823B957E08F@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Sat, 31 Jan 2009 11:49:46 -0800
References: <20090120190744.GA9467@1-4-5.net> <49765FFB.1010709@piuha.net>	<200901222339.n0MNddM88868@magenta.juniper.net> <75cb24520901221834s31095bffr252336804e9a94bd@mail.gmail.com> <497B1F7A.9030407@firstpr.com.au> <6CF20960-E0C1-4BB5-A310-1CDC6577561A@cisco.com> <3103F803-D3A2-4757-86B6-7D8A97C679AC@ericsson.com> <83BCD1E8-9EDB-4D81-94E1-0823B957E08F@cisco.com>
X-Mailer: Apple Mail (2.929.2)
Cc: rrg RG <rrg@irtf.org>, int-area@ietf.org, lisp@ietf.org, routing-discussion@ietf.org
Subject: Re: [rrg] [lisp] Please respond: Questions from the IESG as to whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

On Jan 28, 2009, Dino Farinacci wrote:

> You cannot push around 10^10 entries and store them everywhere. [...]



Dino -

I think we should experimentally compare ALT with other mapping systems
before we decide whether pull-based or push-based mapping systems are
better.  Dismissing push-based mapping systems without corroborating
data would be a bit premature in my opinion.

In the absence of experimentation results, I would actually argue in
favor of push-based mapping systems based on some analytical reasoning:
Pull-based mapping systems have two important disadvantages compared to
push-based mapping systems:

- Performance penalty, i.e., additional propagation latencies for some
   packets, and higher loss probabilities for packets that take a sub-
   optimal path

- Robustness penalty due to a new online dependency on components off
   the actual transmission path.  (FWIW: All pull-based mapping systems
   have this penalty.  Mapping requests must be routed via overlay
   infrastructure because the direct route is unknown at that time.)

Furthermore, I do not share your concerns regarding push-based mapping
systems:  BGP is pushing routing data already today, and this works
fine.  Any routing-scalability-related issues with BGP are not due to
BGP being push-based; they are due to frequent updates and a high load
for core routers.  Both of these issues would go away in an address
indirection architecture (be it LISP, Ivip, APT, or Six/One Router),
independent of whether you use a pull- or push-based mapping system.

In conclusion:  The overlay approach of ALT is certainly an interesting
idea.  But I think it would be premature to conclude that it is the only
viable solution before we have more evidence to back this claim.

- Christian


PS:  I admit that I have never been really good in avoiding cross-
posting.  But this is obviously my all-time negative record...



_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Sat Jan 31 12:24:54 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 632DA3A6830; Sat, 31 Jan 2009 12:24:54 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6ED133A698B for <rrg@core3.amsl.com>; Sat, 31 Jan 2009 12:24:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.519
X-Spam-Level: 
X-Spam-Status: No, score=-6.519 tagged_above=-999 required=5 tests=[AWL=0.080,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ql3RrPhhVT9R for <rrg@core3.amsl.com>; Sat, 31 Jan 2009 12:24:53 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by core3.amsl.com (Postfix) with ESMTP id D83B63A682D for <rrg@irtf.org>; Sat, 31 Jan 2009 12:24:52 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id ECCC16BE58D; Sat, 31 Jan 2009 15:24:33 -0500 (EST)
To: rrg@irtf.org
Message-Id: <20090131202433.ECCC16BE58D@mercury.lcs.mit.edu>
Date: Sat, 31 Jan 2009 15:24:33 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: Re: [rrg] [lisp] Please respond: Questions from the IESG as to whether a WG forming BOF is necessary for LISP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

    > From: Christian Vogt <christian.vogt@ericsson.com>

    > Any routing-scalability-related issues with BGP are not due to BGP
    > being push-based; they are due to frequent updates ... [this]
    > issue[] would go away in an address indirection architecture 

Not necessarily. It all depends on what functionality you're trying to get
out of that layer of binding, i.e. how often the average binding changes.
E.g. if you try and do some mobility through that binding layer (I'm not
saying we should, just as an illustration) that will radically increase the
rate/amount of updates.


On a more general note, I actually did some 'back of the envelope'
calculations a year or two ago, trying to decide whether to use push or pull,
and my recollection is that the update rate numbers (i.e. the control traffic
at each and every ITR) for push got fairly significant (in terms of the
number of updates per second) even with only moderate numbers of mapping
entries, and a fairly low assumed per-entry update rate (e.g. for provider
changes only).

Certainly, a full-push system is going to be distributing lots of mappings to
boxes that never use them - my guess was something in the 99% region, if not
much higher. (Long digression on the optimal mapping distribution system
omitted - the points you raise are certainly valid, but there are good points
on both sides, and I don't think the answer is clear-cut - if it were,
we probably wouldn't still be discussing it.)


Also, I'm not sure that for those working on LISP, ALT is the 'preferred'
long-range answer to the question of 'what does the mapping subsystem look
like'. I think the focus is on ALT at the moment in large part because it's
fairly easy to deploy, because it re-uses existing code. (Dino et al, please
correct me to the degree I am confused here.)

It might well make sense to transition to something else in the long run -
but then of course one has the transition issue to deal with, and from what
thinking I have put into that particular problem, it's more problematic that
some of the other long-term transition issues (e.g. to a different inter-xTR
packet format, etc). So that would argue to make replacement of that
subsystem priority number one...

	Noel
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg

From rrg-bounces@irtf.org  Sat Jan 31 18:35:33 2009
Return-Path: <rrg-bounces@irtf.org>
X-Original-To: rrg-archive@ietf.org
Delivered-To: ietfarch-rrg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9F4EB3A68BB; Sat, 31 Jan 2009 18:35:33 -0800 (PST)
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D311128C0E3 for <rrg@core3.amsl.com>; Sat, 31 Jan 2009 18:35:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.561
X-Spam-Level: 
X-Spam-Status: No, score=-1.561 tagged_above=-999 required=5 tests=[AWL=0.334,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yG0z2NOguBbe for <rrg@core3.amsl.com>; Sat, 31 Jan 2009 18:35:30 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123]) by core3.amsl.com (Postfix) with ESMTP id 76C6B3A67BD for <rrg@irtf.org>; Sat, 31 Jan 2009 18:35:29 -0800 (PST)
Received: from [10.0.0.6] (wira.firstpr.com.au [10.0.0.6]) by gair.firstpr.com.au (Postfix) with ESMTP id 33D18175DAB; Sun,  1 Feb 2009 13:35:09 +1100 (EST)
Message-ID: <49850AE1.1030703@firstpr.com.au>
Date: Sun, 01 Feb 2009 13:37:21 +1100
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: RRG <rrg@irtf.org>
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: [rrg] Mobility, frequency of mapping changes and TTRs
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/pipermail/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rrg-bounces@irtf.org
Errors-To: rrg-bounces@irtf.org

Hi Noel,

In "Please respond: Questions from the IESG as to whether a WG
forming BOF is necessary for LISP" you wrote:

> Not necessarily. It all depends on what functionality you're
> trying to get out of that layer of binding, i.e. how often the
> average binding changes.   E.g. if you try and do some
> mobility through that binding layer (I'm not saying we should,
> just as an illustration) that will radically increase the
> rate/amount of updates.

The most obvious thought about using a core-edge separation
scheme such as LISP, APT, Ivip, etc.  (Six/One Router too?) for
mobility is that the mapping needs to change every time the
Mobile Node (MN) gets a new Care of Address (CoA).  This is not
the case, since the best way to cater for MNs is to have them
establish two-way tunnels to a "nearby" Translating Tunnel
Router (TTR).

The TTR acts as an ETR for packets going to the MN, and probably
as an ITR for packets coming from the MN.  The MN may have
multiple CoAs and would establish a tunnel from each to the
"nearby" TTR.  It is up to the MN and the TTR (not a concern of
the core-edge separation scheme) how traffic is directed over
these multiple tunnels.

If one or more of the new CoAs are not "near" the current TTR,
the MN can keep the current TTR and establish tunnel(s) from the
CoA(s) to another TTR which is "nearby".

There only needs to be a mapping change from the first TTR's
address to the second TTR's address when the excessive distance,
(or perhaps some other impediment, such as congestion) to the
first TTR makes the second preferable.

With Ivip, the end-user network (in this case, the owner of the
MN) pays a small fee per mapping change.  So the frequency of
mapping changes and their impact on the fast-push mapping
distribution system will tend to be a commercially agreeable
arrangement.

The consortium of Root Update Authority System organisations
which build and run the network (or all but the last stages,
near the ISPs) will be charging their end-user customers
directly or indirectly.  They will try to reduce fees and costs,
while making the system have the greatest capacity and performance.

The end-users pay for most of the fast-push infrastructure and
if they are not paying enough to run it well, the operators put
up the prices.  So the "tragedy of the commons" arrangement
where people can impose their changes on a global system without
in some way paying for the cost of these changes is largely or
entirely avoided.

I think we should encourage mobility for Ivip, since mobility is
so valuable and the revenues from this potentially huge number
of end-users will help pay for the fast-push mapping system.

The TTR approach to mobility for core-edge separation schemes is
described here:

  TTR Mobility Extensions for Core-Edge Separation Solutions to
  the Internet's Routing Scaling Problem

  Robin Whittle (First Principles) and Steven Russert (Boeing)
  2008-08-25
  http://www.firstpr.com.au/ip/ivip/TTR-Mobility.pdf

This is not a peer-reviewed paper.  RRG folks are peers - so
please review it on the RRG list!


Not using something like the TTR approach turns out to be
difficult or impossible.  When a MN gets a CoA, it might be
behind NAT.  Also, the CoA address is probably not a place where
the MN could successfully send packets to the rest of the Net
with the source address being its EID/micronet address.

An ETR could presumably connect to some MN, if the ETR was wise
to the local network in which the MN had its CoA.  However, this
is impossible if the CoA is behind NAT - so in this situation
and perhaps in others, the MN needs to connect to the ETR by
establishing a two-way tunnel to the ETR *from* its CoA.

To get outgoing packets to the Net, the MN needs to have some
device which it can tunnel to which is able to forward these
packets.  When you look at doing all this starting with the
ordinary, non-mobile, ETR as a starting point, pretty soon you
realise the MN needs to create a two-way tunnel to the ETR
anyway.  Then, you might as well make this ETR handle outgoing
packets too - in which case it probably makes sense for it to be
an ITR too.  Then, you realise that this combined device - the
same thing as a TTR - does not have to be in the same access
network as the MN.  For efficiency (short physical paths, low
hop count, short delays, less packet loss), it needs to be
"near" to wherever the MN connects to an access network - but it
will still work, with more delays and greater risk of packet
loss, if the TTR and the MN are on opposite sides of the world.

"Near" probably means something like 1000km or so.  So a mapping
change is typically "needed" - more likely is desirable, but not
absolutely needed - when the MN moves more than 1000 km.   Some
MNs will move this far once or more a day - but only when on
commercial airliners or by car or train on long, linear, journeys.

Most MNs will stay in the same area for months or years and so
can keep using the one TTR - so there is no need for a mapping
change - despite connecting and disconnecting potentially
thousands of times to different access networks and so having at
various times potentially thousands of different CoAs.


While I agree that mobility would drive a much greater number of
mapping changes, this is not due to MNs getting new CoAs.  It
would be caused primarily by there being a vastly greater number
of mobile "end-user networks", each a handset or PC etc. than
there are conventional, non-mobile, end-user networks with any
need for multihoming, TE and portability.

A new CoA could happen very frequently, such as switching to
WiFi in a subway tunnel and then back to 3G when out of the
tunnel.  Just walking around a large city on a 3G network could
put the MN in an area for a different IP gateway, so it gets a
different CoA.

Moving something like 1000km - or whatever change in CoA is
required to make the now more distant current TTR a problem - is
a far less frequent event.


You are not saying that mobility should be handled by a
core-edge separation scheme but I am saying emphatically that it
should be.

The LISP folks must be assuming the use of their system for
mobility.  How else would there be 10^10 EIDs?  This is the
target set by Dino in recent posts for LISP-ALT and any other
core-edge separation scheme.

Mobility is at least as big a deal for TCP/IP as it is for
telephony.  The TTR approach enables the MN to retain its one or
more IP addresses - an EID prefix, micronet or whatever -
indefinitely.  As long as there is a mapping change to the new
TTR when the MN moves so far as to make it worth tunneling to a
new, closer, TTR, then the overall path of packets to and from
the MN and all its correspondent nodes is either optimal or
generally close to optimal.

Other than some tunneling and TTR communications software in the
MN, there are no stack, API or application changes in the MN.
Correspondent nodes require no changes whatsoever.  This will
work fine with IPv4 or IPv6.

However, global mobility for anything more than a billion or so
devices is going to require IPv6.

A billion single IPv4 address micronets would probably be fine
with Ivip.  The system can use address space close to 100%
efficiently, for instance breaking a /12 Mapped Address Block
(MAB) into 2^20 single IP address micronets, one for each
cellphone-PC-media-player-whatever.


Massive global mobile IP access networks will generally need to
be built with IPv6.  A MN can always tunnel to a TTR via IPv6
and conduct IPv4 communications to the rest of the world through
that tunnel - but in the long-term, if billions of people are to
have these things, even with 100% efficient utilization of IPv4
space with one IPv4 address micronet per each device, there is
not going to be enough IPv4 space to go around.

  - Robin

_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg
