Re: [netext] second revision of the new charter for theworking group

Jari Arkko <jari.arkko@piuha.net> Mon, 25 January 2010 21:49 UTC

Return-Path: <jari.arkko@piuha.net>
X-Original-To: netext@core3.amsl.com
Delivered-To: netext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4796B3A68F1 for <netext@core3.amsl.com>; Mon, 25 Jan 2010 13:49:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.453
X-Spam-Level:
X-Spam-Status: No, score=-2.453 tagged_above=-999 required=5 tests=[AWL=0.146, 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 utTciisXNEhZ for <netext@core3.amsl.com>; Mon, 25 Jan 2010 13:49:10 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id 62F303A68E1 for <netext@ietf.org>; Mon, 25 Jan 2010 13:49:10 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 6DFC2D4928; Mon, 25 Jan 2010 23:49:17 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1FeMMRlCIJBM; Mon, 25 Jan 2010 23:49:17 +0200 (EET)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id C1AD4D4925; Mon, 25 Jan 2010 23:49:16 +0200 (EET)
Message-ID: <4B5E11DC.90408@piuha.net>
Date: Mon, 25 Jan 2010 23:49:16 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: pierrick.seite@orange-ftgroup.com
References: <C77ACD0B.36E5D%sgundave@cisco.com> <4B559E01.6030704@piuha.net><853DD750D9C3724FBF2DF7164FCF641C03F9781D@FRVELSMBS14.ad2.ad.alcatel.com> <BF345F63074F8040B58C00A186FCA57F1C67584E1E@NALASEXMB04.na.qualcomm.com> <10171_1263982320_4B56D6F0_10171_25834_1_843DA8228A1BA74CA31FB4E111A5C462993FAA@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <10171_1263982320_4B56D6F0_10171_25834_1_843DA8228A1BA74CA31FB4E111A5C462993FAA@ftrdmel0.rd.francetelecom.fr>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: netext@ietf.org, Telemaco.Melia@alcatel-lucent.com
Subject: Re: [netext] second revision of the new charter for theworking group
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Mailing list for discusion of extensions to network mobility protocol, i.e PMIP6. " <netext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/netext>, <mailto:netext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netext>
List-Post: <mailto:netext@ietf.org>
List-Help: <mailto:netext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netext>, <mailto:netext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jan 2010 21:49:11 -0000

Pierrick,

> Actually, the "single interface" approach may not be the only way. For instance, draft-bernardos-mif-pmip leverages on the weak host model (RFC 1122) to address IP flow mobility issue and leave the host unmodified. This is why we think the charter should not be so "solution oriented".
>   

Lets talk about this for a second.

It seems that there are a number of different host impacts.

1) We might need a new protocol between the host and the network. This 
implies new code on hosts and network and new protocol messages on the wire.

2) We might need just new code on the host, but still be able to 
determine all necessary information from existing exchanges.

3) We might need to assume that the host implements something which is 
allowed according to the RFCs but has not been implemented.

4) We might need to assume some code on the host that is often but not 
universally there on all current hosts.

5) We might need to assume some configuration on the host.

Obviously, on a network where someone is in full control we can assume 
anything, and build any amount of new protocols and code to optimize the 
behavior. Such networks are VERY rare, however. For instance, I'm 
writing this mail on my laptop which is connected over my cell phone to 
3G network, and the network can make no assumptions about what features 
my kernel has on my laptop. Or what my config is. Yet, a phone or a USB 
stick that implements 2G to 3G switching works just fine with this 
configuration.

My point is that we are not after no host impacts in some theoretical 
standardization sense. We actually want devices to work, old devices, 
current devices, new devices. Out of the box. And whether they work is 
affected by a number of things, including lack of code or config. I 
don't feel any happier about my hosed connection if the RFCs would have 
allowed it work. Or if the code is there but I didn't know I needed to 
turn it on. If it doesn't work, it doesn't work.

Jari