
From brian.e.carpenter@gmail.com  Tue Sep  4 09:17:59 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7761121F84CD for <int-area@ietfa.amsl.com>; Tue,  4 Sep 2012 09:17:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.691
X-Spam-Level: 
X-Spam-Status: No, score=-101.691 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UN77eFNTRAzv for <int-area@ietfa.amsl.com>; Tue,  4 Sep 2012 09:17:59 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id C551121F84C4 for <int-area@ietf.org>; Tue,  4 Sep 2012 09:17:58 -0700 (PDT)
Received: by eekb45 with SMTP id b45so2585046eek.31 for <int-area@ietf.org>; Tue, 04 Sep 2012 09:17:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=NFRkkB/IY2C0eK/GpJqZ6p8N6fFgVbXKKRD3e8wunpw=; b=PdQKn2ej8qOeRYZee5/TWvI0RaveDBq7okFrjUDoMAuNUvImBbss6fQD/syfqRWtdb IgHVfW2OqS0HDC3raUg+wSOseK8svMkKvMJ+sITFfyWedqukZoajizHfN11GffRFR/fa c0Hm7U50yozFyBoVT/A3Q5kWGPQLSx2uJL2T3OUj7Bb+IdBDb2BYG3D4hUD9JFpFOBAU 11Z6I9JfSia5SxIjRgRpvpgW/FhDR1FMgkIAUXPb40rbU3e8aNtceoEtmPK8A3kj/Wlq fKAz8jHLi1gdAlIKEOJliunHsoUeQdJX8IXpufCJ3tUFSbn4N3jDhQ3jUN9/z7ZB9AKY M8wQ==
Received: by 10.14.206.201 with SMTP id l49mr27287766eeo.3.1346775478027; Tue, 04 Sep 2012 09:17:58 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-217-100.as13285.net. [2.102.217.100]) by mx.google.com with ESMTPS id r45sm46682759eem.6.2012.09.04.09.17.55 (version=SSLv3 cipher=OTHER); Tue, 04 Sep 2012 09:17:56 -0700 (PDT)
Message-ID: <504629B7.7080703@gmail.com>
Date: Tue, 04 Sep 2012 17:17:59 +0100
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: Internet Area <int-area@ietf.org>,  draft-bonica-v6-multihome@tools.ietf.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: [Int-area] draft-bonica-v6-multihome
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Sep 2012 16:17:59 -0000

Hi,

As far as I understand it without seeing a complete "life cycle" of
a multihoming failover, this proposal only works because of a three-way
collaboration between both ISPs concerned and the site. Unless I've
misunderstood something, that is almost the same as is required to make
the draft-ietf-v6ops-ipv6-multihoming-without-ipv6nat solution work too.
In both cases, something is needed to avoid packets with ISP A's prefix
being discarded by ISP B's ingress filters. The fact that their internal
prefix has been translated in one case is beside the point.

If that is correct, this common aspect should be in its own draft. Then
we can see a straight comparison between the two approaches.

I'd also like to see a detailed goal-by-goal comparison with the goals defined
in RFC 3582. Back in the MULTI6 WG, that was the approach we took in
comparing proposed solutions.

The multihoming-without-ipv6nat draft notes that e2e address transparency
wasn't listed as a goal in RFC 3582. Having been co-chair of that WG, I'm
pretty sure that's because we never imagined anyone proposing anything else
for IPv6. That was obviously a failure of the imagination. But apart from
that, I don't think it's reasonable to sweep it (and the referral problem
that derives from it) under the carpet. It's a problem faced by essentially
every distributed app. So I think all proposals for multihoming that affect
e2e address transparency need to analyse their impact on referrals.

Regards
   Brian

From rbonica@juniper.net  Wed Sep  5 17:42:55 2012
Return-Path: <rbonica@juniper.net>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84D4D21F871A for <int-area@ietfa.amsl.com>; Wed,  5 Sep 2012 17:42:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.524
X-Spam-Level: 
X-Spam-Status: No, score=-106.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FtJUvvYALmE9 for <int-area@ietfa.amsl.com>; Wed,  5 Sep 2012 17:42:55 -0700 (PDT)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by ietfa.amsl.com (Postfix) with ESMTP id E711321F8718 for <int-area@ietf.org>; Wed,  5 Sep 2012 17:42:53 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP ID DSNKUEfxioQX8pkHkDYPnAStzodNjqdJ8Wmz@postini.com; Wed, 05 Sep 2012 17:42:55 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 5 Sep 2012 17:40:44 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Wed, 5 Sep 2012 20:40:43 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Internet Area <int-area@ietf.org>, "draft-bonica-v6-multihome@tools.ietf.org" <draft-bonica-v6-multihome@tools.ietf.org>
Date: Wed, 5 Sep 2012 20:40:41 -0400
Thread-Topic: draft-bonica-v6-multihome
Thread-Index: Ac2KuOhddXtjBCyGRoSAOklqVnMdbABDPSyQ
Message-ID: <13205C286662DE4387D9AF3AC30EF456D782F2F752@EMBX01-WF.jnpr.net>
References: <504629B7.7080703@gmail.com>
In-Reply-To: <504629B7.7080703@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [Int-area] draft-bonica-v6-multihome
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Sep 2012 00:42:55 -0000

SGkgQnJpYW4sDQoNCkNvbW1lbnRzIGlubGluZS4uLi4uDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNz
YWdlLS0tLS0NCj4gRnJvbTogQnJpYW4gRSBDYXJwZW50ZXIgW21haWx0bzpicmlhbi5lLmNhcnBl
bnRlckBnbWFpbC5jb21dDQo+IFNlbnQ6IFR1ZXNkYXksIFNlcHRlbWJlciAwNCwgMjAxMiAxMjox
OCBQTQ0KPiBUbzogSW50ZXJuZXQgQXJlYTsgZHJhZnQtYm9uaWNhLXY2LW11bHRpaG9tZUB0b29s
cy5pZXRmLm9yZw0KPiBTdWJqZWN0OiBkcmFmdC1ib25pY2EtdjYtbXVsdGlob21lDQo+IA0KPiBI
aSwNCj4gDQo+IEFzIGZhciBhcyBJIHVuZGVyc3RhbmQgaXQgd2l0aG91dCBzZWVpbmcgYSBjb21w
bGV0ZSAibGlmZSBjeWNsZSIgb2YgYQ0KPiBtdWx0aWhvbWluZyBmYWlsb3ZlciwgdGhpcyBwcm9w
b3NhbCBvbmx5IHdvcmtzIGJlY2F1c2Ugb2YgYSB0aHJlZS13YXkNCj4gY29sbGFib3JhdGlvbiBi
ZXR3ZWVuIGJvdGggSVNQcyBjb25jZXJuZWQgYW5kIHRoZSBzaXRlLiBVbmxlc3MgSSd2ZQ0KPiBt
aXN1bmRlcnN0b29kIHNvbWV0aGluZywgdGhhdCBpcyBhbG1vc3QgdGhlIHNhbWUgYXMgaXMgcmVx
dWlyZWQgdG8gbWFrZQ0KPiB0aGUgZHJhZnQtaWV0Zi12Nm9wcy1pcHY2LW11bHRpaG9taW5nLXdp
dGhvdXQtaXB2Nm5hdCBzb2x1dGlvbiB3b3JrDQo+IHRvby4NCj4NCj4gSW4gYm90aCBjYXNlcywg
c29tZXRoaW5nIGlzIG5lZWRlZCB0byBhdm9pZCBwYWNrZXRzIHdpdGggSVNQIEEncyBwcmVmaXgN
Cj4gYmVpbmcgZGlzY2FyZGVkIGJ5IElTUCBCJ3MgaW5ncmVzcyBmaWx0ZXJzLiBUaGUgZmFjdCB0
aGF0IHRoZWlyDQo+IGludGVybmFsIHByZWZpeCBoYXMgYmVlbiB0cmFuc2xhdGVkIGluIG9uZSBj
YXNlIGlzIGJlc2lkZSB0aGUgcG9pbnQuDQoNClllcyEgVGhlcmUgaXMgc2lnbmlmaWNhbnQgY29t
bW9uYWxpdHkgYmV0d2VlbiBkcmFmdC1pZXRmLXY2b3BzLWlwdjYtbXVsdGlob21pbmctd2l0aG91
dC1pcHY2bmF0IGFuZCBkcmFmdC1ib25pY2EtdjYtbXVsdGlob21lLiBCb3RoIGRyYWZ0cyBzZXQg
b3V0IHRvIHNhdGlzZnkgdGhlIHJlcXVpcmVtZW50cyBvZiBSRkMgMzU4Mi4gSW4gYm90aCBkcmFm
dHMsIGEgbWVjaGFuaXNtIGlzIHJlcXVpcmVkIHRvIHByZXZlbnQgb3V0Ym91bmQgcGFja2V0cyBm
cm9tIGJlaW5nIGRpc2NhcmRlZCBieSBJU1AgdVJQRiBmaWx0ZXJzLiBJbiBib3RoIGRyYWZ0cywg
dGhhdCBtZWNoYW5pc20gcmVxdWlyZXMgY29sbGFib3JhdGlvbiBhbW9uZyB0aGUgc2l0ZSBhbmQg
aXRzIElTUHMuDQoNCj4gDQo+IElmIHRoYXQgaXMgY29ycmVjdCwgdGhpcyBjb21tb24gYXNwZWN0
IHNob3VsZCBiZSBpbiBpdHMgb3duIGRyYWZ0LiBUaGVuDQo+IHdlIGNhbiBzZWUgYSBzdHJhaWdo
dCBjb21wYXJpc29uIGJldHdlZW4gdGhlIHR3byBhcHByb2FjaGVzLg0KPiANCj4gSSdkIGFsc28g
bGlrZSB0byBzZWUgYSBkZXRhaWxlZCBnb2FsLWJ5LWdvYWwgY29tcGFyaXNvbiB3aXRoIHRoZSBn
b2Fscw0KPiBkZWZpbmVkIGluIFJGQyAzNTgyLiBCYWNrIGluIHRoZSBNVUxUSTYgV0csIHRoYXQg
d2FzIHRoZSBhcHByb2FjaCB3ZQ0KPiB0b29rIGluIGNvbXBhcmluZyBwcm9wb3NlZCBzb2x1dGlv
bnMuDQoNCkkgYWdyZWUgdGhhdCBhIGNvbXBhcmUtYW5kLWNvbnRyYXN0IGRyYWZ0IHdvdWxkIGJl
IGhlbHBmdWwhIE1heWJlIHlvdSwgYSBjb3VwbGUgb2YgdGhlIGF1dGhvcnMgb2YgZHJhZnQtaWV0
Zi12Nm9wcy1pcHY2LW11bHRpaG9taW5nLXdpdGhvdXQtaXB2Nm5hdCBhbmQgSSBjb3VsZCBjb2xs
YWJvcmF0ZSBvbiBzdWNoIGEgZHJhZnQuIExldCdzIGRpc2N1c3MgdGhpcyBwb3NzaWJpbGl0eSBv
ZmYgbGluZS4NCg0KPiANCj4gVGhlIG11bHRpaG9taW5nLXdpdGhvdXQtaXB2Nm5hdCBkcmFmdCBu
b3RlcyB0aGF0IGUyZSBhZGRyZXNzDQo+IHRyYW5zcGFyZW5jeSB3YXNuJ3QgbGlzdGVkIGFzIGEg
Z29hbCBpbiBSRkMgMzU4Mi4gSGF2aW5nIGJlZW4gY28tY2hhaXINCj4gb2YgdGhhdCBXRywgSSdt
IHByZXR0eSBzdXJlIHRoYXQncyBiZWNhdXNlIHdlIG5ldmVyIGltYWdpbmVkIGFueW9uZQ0KPiBw
cm9wb3NpbmcgYW55dGhpbmcgZWxzZSBmb3IgSVB2Ni4gVGhhdCB3YXMgb2J2aW91c2x5IGEgZmFp
bHVyZSBvZiB0aGUNCj4gaW1hZ2luYXRpb24uIEJ1dCBhcGFydCBmcm9tIHRoYXQsIEkgZG9uJ3Qg
dGhpbmsgaXQncyByZWFzb25hYmxlIHRvDQo+IHN3ZWVwIGl0IChhbmQgdGhlIHJlZmVycmFsIHBy
b2JsZW0gdGhhdCBkZXJpdmVzIGZyb20gaXQpIHVuZGVyIHRoZQ0KPiBjYXJwZXQuIEl0J3MgYSBw
cm9ibGVtIGZhY2VkIGJ5IGVzc2VudGlhbGx5IGV2ZXJ5IGRpc3RyaWJ1dGVkIGFwcC4gU28gSQ0K
PiB0aGluayBhbGwgcHJvcG9zYWxzIGZvciBtdWx0aWhvbWluZyB0aGF0IGFmZmVjdCBlMmUgYWRk
cmVzcw0KPiB0cmFuc3BhcmVuY3kgbmVlZCB0byBhbmFseXNlIHRoZWlyIGltcGFjdCBvbiByZWZl
cnJhbHMuDQoNCkFsc28gYWdyZWVkLiBXZSBtaWdodCBhbHNvIHdhbnQgdG8gcmVpbnZpZ29yYXRl
IHlvdXIgd29yayBvbiByZWZlcnJhbHMuDQoNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgIFJvbg0KDQo+IA0KPiBSZWdhcmRzDQo+ICAgIEJyaWFuDQo=

From pars.mutaf@gmail.com  Mon Sep 10 02:07:13 2012
Return-Path: <pars.mutaf@gmail.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EAE821F845B for <int-area@ietfa.amsl.com>; Mon, 10 Sep 2012 02:07:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.998
X-Spam-Level: 
X-Spam-Status: No, score=-0.998 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yUIywzBGzkUr for <int-area@ietfa.amsl.com>; Mon, 10 Sep 2012 02:07:12 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 40E7A21F853B for <int-area@ietf.org>; Mon, 10 Sep 2012 02:07:12 -0700 (PDT)
Received: by vbbfc26 with SMTP id fc26so270138vbb.31 for <int-area@ietf.org>; Mon, 10 Sep 2012 02:07:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=iacJVa058hFwbEYqoCfrL3IB6E1IzE97k8GMvUl5/Dc=; b=Mei20tj9l+U7WflcZyOJHOo1Ukip0tCHKaCQETbw1N3t3yQ70OvfERP9ERSW4bMWZ5 UKEPF46E9d4N+tVlgv1fy5mjyLjlf88F/uG1i8Ugh/0R/V0mXteENr68G1zqVI0YgcBI d4hzPIUt9ComyLVijN0YrrB8Mq6VhghjDcZUOZY68m+3qk1DGe63K+fxvc3JgrX6ZneX 6H/L3alxkBl7p0EPHxeE6CWE5U/0DZ/2l2HGlEeFwBMI0kUyaMXPJEkP31ad+N21j09/ NgKl/qqll2VrQW3ig08A2bt9occHenZNA13mzDtcgLzyY2eaa8p2X3EFSweuBklNfOG5 QImg==
MIME-Version: 1.0
Received: by 10.58.35.166 with SMTP id i6mr709454vej.10.1347268030950; Mon, 10 Sep 2012 02:07:10 -0700 (PDT)
Received: by 10.58.213.101 with HTTP; Mon, 10 Sep 2012 02:07:10 -0700 (PDT)
Date: Mon, 10 Sep 2012 12:07:10 +0300
Message-ID: <CACQuieaOfyC5pJ2MyHBRTZYWCYfZMp58Ujh8rn0-yBBQL+kkzg@mail.gmail.com>
From: Pars Mutaf <pars.mutaf@gmail.com>
To: Internet Area <int-area@ietf.org>
Content-Type: multipart/alternative; boundary=047d7b5d4c4066ed5d04c955486f
Subject: [Int-area] Discrete IP
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Sep 2012 09:07:13 -0000

--047d7b5d4c4066ed5d04c955486f
Content-Type: text/plain; charset=ISO-8859-1

Dear colleagues,

I believe that the next step in IP's evolution would not be IPv6. It would
be "Discrete IP" allowing any IP version.
I concluded that Discrete IP better respects the end-to-end principles
therefore it is economically more viable.

Please read the full document here:

http://www.scribd.com/doc/105448105/Discrete-IP

Cheers,

Pars

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

Dear colleagues, <br><br>I believe that the next step in IP&#39;s evolution=
 would not be IPv6. It would be &quot;Discrete IP&quot; allowing any IP ver=
sion.<br>I concluded that Discrete IP better respects the end-to-end princi=
ples therefore it is economically more viable.<br>
<br>Please read the full document here:<br><br><a href=3D"http://www.scribd=
.com/doc/105448105/Discrete-IP">http://www.scribd.com/doc/105448105/Discret=
e-IP</a><br><br>Cheers, <br><br>Pars<br>

--047d7b5d4c4066ed5d04c955486f--

From touch@isi.edu  Mon Sep 10 14:35:38 2012
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A95421F8741 for <int-area@ietfa.amsl.com>; Mon, 10 Sep 2012 14:35:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.202
X-Spam-Level: 
X-Spam-Status: No, score=-101.202 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EGA25let7lIP for <int-area@ietfa.amsl.com>; Mon, 10 Sep 2012 14:35:37 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 76CE021F8697 for <int-area@ietf.org>; Mon, 10 Sep 2012 14:35:37 -0700 (PDT)
Received: from [59.10.124.171] ([59.10.124.171]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id q8ALZ0Hn018912 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 10 Sep 2012 14:35:04 -0700 (PDT)
References: <CACQuieaOfyC5pJ2MyHBRTZYWCYfZMp58Ujh8rn0-yBBQL+kkzg@mail.gmail.com>
In-Reply-To: <CACQuieaOfyC5pJ2MyHBRTZYWCYfZMp58Ujh8rn0-yBBQL+kkzg@mail.gmail.com>
Mime-Version: 1.0 (1.0)
Content-Type: multipart/alternative; boundary=Apple-Mail-7DF5C11A-BE1C-44AF-9CF3-978B902687D3
Message-Id: <FAD8796F-0B15-4197-B952-AEE7FD56EDED@isi.edu>
Content-Transfer-Encoding: 7bit
X-Mailer: iPad Mail (9B206)
From: Joe Touch <touch@isi.edu>
Date: Tue, 11 Sep 2012 06:34:57 +0900
To: Pars Mutaf <pars.mutaf@gmail.com>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] Discrete IP
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Sep 2012 21:35:38 -0000

--Apple-Mail-7DF5C11A-BE1C-44AF-9CF3-978B902687D3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

You might want to look at Vintage Cerf's Catenet paper (which this reinvents=
 - , http://en.wikipedia.org/wiki/Catenet), and consider the whole point of a=
 single common internerworking layer (of which the Internet is an example).

Joe

On Sep 10, 2012, at 6:07 PM, Pars Mutaf <pars.mutaf@gmail.com> wrote:

> Dear colleagues,=20
>=20
> I believe that the next step in IP's evolution would not be IPv6. It would=
 be "Discrete IP" allowing any IP version.
> I concluded that Discrete IP better respects the end-to-end principles the=
refore it is economically more viable.
>=20
> Please read the full document here:
>=20
> http://www.scribd.com/doc/105448105/Discrete-IP
>=20
> Cheers,=20
>=20
> Pars
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area

--Apple-Mail-7DF5C11A-BE1C-44AF-9CF3-978B902687D3
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=utf-8

<html><head></head><body bgcolor="#FFFFFF"><div>You might want to look at Vintage Cerf's Catenet paper (which this reinvents - , <a href="http://en.wikipedia.org/wiki/Catenet">http://en.wikipedia.org/wiki/Catenet</a>), and consider the whole point of a single common internerworking layer (of which the Internet is an example).</div><div><br></div><div>Joe</div><div><br>On Sep 10, 2012, at 6:07 PM, Pars Mutaf &lt;<a href="mailto:pars.mutaf@gmail.com">pars.mutaf@gmail.com</a>&gt; wrote:<br><br></div><div></div><blockquote type="cite"><div>Dear colleagues, <br><br>I believe that the next step in IP's evolution would not be IPv6. It would be "Discrete IP" allowing any IP version.<br>I concluded that Discrete IP better respects the end-to-end principles therefore it is economically more viable.<br>
<br>Please read the full document here:<br><br><a href="http://www.scribd.com/doc/105448105/Discrete-IP">http://www.scribd.com/doc/105448105/Discrete-IP</a><br><br>Cheers, <br><br>Pars<br>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Int-area mailing list</span><br><span><a href="mailto:Int-area@ietf.org">Int-area@ietf.org</a></span><br><span><a href="https://www.ietf.org/mailman/listinfo/int-area">https://www.ietf.org/mailman/listinfo/int-area</a></span><br></div></blockquote></body></html>
--Apple-Mail-7DF5C11A-BE1C-44AF-9CF3-978B902687D3--

From fred@cisco.com  Mon Sep 10 17:08:04 2012
Return-Path: <fred@cisco.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 243AE21F857A for <int-area@ietfa.amsl.com>; Mon, 10 Sep 2012 17:08:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zkvya8Hoag31 for <int-area@ietfa.amsl.com>; Mon, 10 Sep 2012 17:08:02 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 6907121F852A for <int-area@ietf.org>; Mon, 10 Sep 2012 17:07:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1970; q=dns/txt; s=iport; t=1347322078; x=1348531678; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=D1yJzClU3egpzIVqsuNedcFpQBxF8W15SUHgFuqjXv0=; b=miuel6HMtHMO0E7ytoZLlBBU5Is5r7BL/mNlRlx0W4ZdtYW+1GWjBy3A DO7PM+SMWm7SShL+i/EFNWmheX366brRwS6MPzBNpdY0uLXuDOmU/We/x WwnIz4VObu4GmKez82Lg9U82IjRN+Ixo5bdeKWFPm1xSKCpP2sFb24++h c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAKN/TlCtJXHB/2dsb2JhbABFu1iBB4IgAQEBAwESASc/BQsCAQg2EDIlAgQOJ4doBgubXqApBIsMhVZgA5VdjjaBZ4Jm
X-IronPort-AV: E=Sophos;i="4.80,400,1344211200"; d="scan'208";a="120199618"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-7.cisco.com with ESMTP; 11 Sep 2012 00:07:58 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id q8B07v5v019644 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 11 Sep 2012 00:07:57 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.97]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.02.0298.004; Mon, 10 Sep 2012 19:07:57 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Thread-Topic: [Int-area] draft-bonica-v6-multihome
Thread-Index: AQHNirjgL6qzht3KxUCQUn0/l9X2RpeEoVuA
Date: Tue, 11 Sep 2012 00:07:57 +0000
Message-ID: <37F823E3-F6AB-4A5D-A925-E4B8691FFFF6@cisco.com>
References: <504629B7.7080703@gmail.com>
In-Reply-To: <504629B7.7080703@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.32.244.221]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19176.000
x-tm-as-result: No--36.156100-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-ID: <BD40A0B524A12A449D87793BBF5DC173@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<draft-bonica-v6-multihome@tools.ietf.org>" <draft-bonica-v6-multihome@tools.ietf.org>, Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] draft-bonica-v6-multihome
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Sep 2012 00:08:04 -0000

On Sep 4, 2012, at 9:17 AM, Brian E Carpenter wrote:

> The multihoming-without-ipv6nat draft notes that e2e address transparency
> wasn't listed as a goal in RFC 3582. Having been co-chair of that WG, I'm
> pretty sure that's because we never imagined anyone proposing anything el=
se
> for IPv6. That was obviously a failure of the imagination. But apart from
> that, I don't think it's reasonable to sweep it (and the referral problem
> that derives from it) under the carpet. It's a problem faced by essential=
ly
> every distributed app. So I think all proposals for multihoming that affe=
ct
> e2e address transparency need to analyse their impact on referrals.

If the working group that came up with 3582 had a failure of imagination, i=
t also had a failure of memory. The GSE proposal of 1996 and the 8+8 propos=
al that came later certainly imagined that the locator might change its enc=
oding as the packet wandered around.

In any event, the implications for the fact that the locator might change e=
nd to end is addressed in https://tools.ietf.org/html/rfc6296#section-5. Th=
e same considerations apply to ILNP when it is permitted to translate betwe=
en internal and external prefixes in the locator. In short, DNS needs to so=
mehow know that the translation occurs and what the related addresses are, =
so that it can deliver them all in a DNS response. RFC 6296 also discussed =
hair pinning, because RFC 4787 among others do as well. IMHO, that is actua=
lly something that should be disabled; the host should use Happy Eyeballs, =
and should discover (whether from a split DNS or by trying all the addresse=
s) that the one that works internally is the internal one. That addresses a=
 list of ills. Similar considerations apply to SIP/SDP and probably other p=
rotocols that are silly enough to use a network layer address as an applica=
tion layer identifier - and so, by the way, have problems with mobility.=

From touch@isi.edu  Mon Sep 10 22:18:09 2012
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30E7321F8617 for <int-area@ietfa.amsl.com>; Mon, 10 Sep 2012 22:18:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rapVJLC-2xtg for <int-area@ietfa.amsl.com>; Mon, 10 Sep 2012 22:18:08 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 7E4E221F8619 for <int-area@ietf.org>; Mon, 10 Sep 2012 22:18:08 -0700 (PDT)
Received: from [192.168.0.15] ([210.114.91.71]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id q8B5HddV028530 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 10 Sep 2012 22:17:50 -0700 (PDT)
Message-ID: <504EC973.70706@isi.edu>
Date: Mon, 10 Sep 2012 22:17:39 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Pars Mutaf <pars.mutaf@gmail.com>
References: <CACQuieaOfyC5pJ2MyHBRTZYWCYfZMp58Ujh8rn0-yBBQL+kkzg@mail.gmail.com> <FAD8796F-0B15-4197-B952-AEE7FD56EDED@isi.edu>
In-Reply-To: <FAD8796F-0B15-4197-B952-AEE7FD56EDED@isi.edu>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] Discrete IP
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Sep 2012 05:18:09 -0000

PS - I just updated the Wikipedia page to provide the current URL for 
IENs. Here is this one for convenience:

http://www.rfc-editor.org/in-notes/ien/ien48.txt

Joe

On 9/10/2012 2:34 PM, Joe Touch wrote:
> You might want to look at Vintage Cerf's Catenet paper (which this
> reinvents - , http://en.wikipedia.org/wiki/Catenet), and consider the
> whole point of a single common internerworking layer (of which the
> Internet is an example).
>
> Joe
>
> On Sep 10, 2012, at 6:07 PM, Pars Mutaf <pars.mutaf@gmail.com
> <mailto:pars.mutaf@gmail.com>> wrote:
>
>> Dear colleagues,
>>
>> I believe that the next step in IP's evolution would not be IPv6. It
>> would be "Discrete IP" allowing any IP version.
>> I concluded that Discrete IP better respects the end-to-end principles
>> therefore it is economically more viable.
>>
>> Please read the full document here:
>>
>> http://www.scribd.com/doc/105448105/Discrete-IP
>>
>> Cheers,
>>
>> Pars
>> _______________________________________________
>> Int-area mailing list
>> Int-area@ietf.org <mailto:Int-area@ietf.org>
>> https://www.ietf.org/mailman/listinfo/int-area

From pars.mutaf@gmail.com  Mon Sep 10 22:34:41 2012
Return-Path: <pars.mutaf@gmail.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 810D021F8619 for <int-area@ietfa.amsl.com>; Mon, 10 Sep 2012 22:34:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.298
X-Spam-Level: 
X-Spam-Status: No, score=-2.298 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W09VK6FT8nmz for <int-area@ietfa.amsl.com>; Mon, 10 Sep 2012 22:34:40 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3B11721F85B8 for <int-area@ietf.org>; Mon, 10 Sep 2012 22:34:40 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so157523vcb.31 for <int-area@ietf.org>; Mon, 10 Sep 2012 22:34:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=OKSG5M8ob5DTzyl2uRNLQZZsrhWOAWvTc3yKPYYw2xI=; b=LYWgIed5pP27zMNyEeME+OQ+NIimsDhKohGuQ45abZ6LNcx31XS4+KwHjiUys3xOpR rZFZnTVX94UBM7zeDUi+A0bpDHM5xiJfpA5pNvYyc1i2l6pi+W07B90BhonRByJm3TD4 sA1fyuU5R3hDB+9kRpDwapx3+PJ4IoWNdeI+BWE2uXXbZxMeBvsCOTftjXV83hqf15eV 0MIV63hmide5CYaxMn6RAc/50b1JWJMvEMAFIzmi4Av2fhVr6FHd5x1XLbWMrZP6bNa3 zLJNjJ2Mpldr0nC7zoj47uXEMyXhKG3zjfPLVXYZ33oLjk3yeph1qN4RMiIjcP9ODoNO UjOA==
MIME-Version: 1.0
Received: by 10.52.22.111 with SMTP id c15mr18965192vdf.2.1347341679331; Mon, 10 Sep 2012 22:34:39 -0700 (PDT)
Received: by 10.58.213.101 with HTTP; Mon, 10 Sep 2012 22:34:39 -0700 (PDT)
In-Reply-To: <FAD8796F-0B15-4197-B952-AEE7FD56EDED@isi.edu>
References: <CACQuieaOfyC5pJ2MyHBRTZYWCYfZMp58Ujh8rn0-yBBQL+kkzg@mail.gmail.com> <FAD8796F-0B15-4197-B952-AEE7FD56EDED@isi.edu>
Date: Tue, 11 Sep 2012 08:34:39 +0300
Message-ID: <CACQuiebgTXDmUmaE2n1yAbt4vS+V0M60fjXujqtMrh2n1WhPgQ@mail.gmail.com>
From: Pars Mutaf <pars.mutaf@gmail.com>
To: Joe Touch <touch@isi.edu>
Content-Type: multipart/alternative; boundary=20cf307ca5b030083d04c9666e00
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] Discrete IP
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Sep 2012 05:34:41 -0000

--20cf307ca5b030083d04c9666e00
Content-Type: text/plain; charset=ISO-8859-1

A single common internetworking layer helps reach other nodes regardless of
their underlying technology.

Current situation shows that, now we need to reach other nodes regardless
of their underlying technology, and regardless of their IP version. This is
what Discrete IP does.

Not allowing different IP versions is a technology blocker. IPv6 is ready,
some entities need it, but they cannot use it fully.
This is because it is required that other entities also transition to IPv6.
They do not have to because they do not see the economical incentive. We
clearly have a paradox here. Some entities need IPv6, others do not. It is
also assumed that IP research is done. Someone may invent a totally new and
wonderful concept of IP and call it IPv7. Some entities may use it, while
others still use IPv6 and IPv4.

Discrete IP solves this paradox: Everybody do what they wish. It is
possible that all entities agree on the same IP version. But we cannot make
this decision for them. Discrete IP allows Continuous IP too.

Technology is free.

Pars


On Tue, Sep 11, 2012 at 12:34 AM, Joe Touch <touch@isi.edu> wrote:

> You might want to look at Vintage Cerf's Catenet paper (which this
> reinvents - , http://en.wikipedia.org/wiki/Catenet), and consider the
> whole point of a single common internerworking layer (of which the Internet
> is an example).
>
> Joe
>
> On Sep 10, 2012, at 6:07 PM, Pars Mutaf <pars.mutaf@gmail.com> wrote:
>
> Dear colleagues,
>
> I believe that the next step in IP's evolution would not be IPv6. It would
> be "Discrete IP" allowing any IP version.
> I concluded that Discrete IP better respects the end-to-end principles
> therefore it is economically more viable.
>
> Please read the full document here:
>
> http://www.scribd.com/doc/105448105/Discrete-IP
>
> Cheers,
>
> Pars
>
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area
>
>

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

A single common internetworking layer helps reach other nodes regardless of=
 their underlying technology.<br><br>Current situation shows that, now we n=
eed to reach other nodes regardless of their underlying technology, and reg=
ardless of their IP version. This is what Discrete IP does.<br>
<br>Not allowing different IP versions is a technology blocker. IPv6 is rea=
dy, some entities need it, but they cannot use it fully.<br>This is because=
 it is required that other entities also transition to IPv6. They do not ha=
ve to because they do not see the economical incentive. We clearly have a p=
aradox here. Some entities need IPv6, others do not. It is also assumed tha=
t IP research is done. Someone may invent a totally new and wonderful conce=
pt of IP and call it IPv7. Some entities may use it, while others still use=
 IPv6 and IPv4.<br>
<br>Discrete IP solves this paradox: Everybody do what they wish. It is pos=
sible that all entities agree on the same IP version. But we cannot make th=
is decision for them. Discrete IP allows Continuous IP too.=A0 <br><br>Tech=
nology is free.<br>
<br>Pars<br><br><br><div class=3D"gmail_quote">On Tue, Sep 11, 2012 at 12:3=
4 AM, Joe Touch <span dir=3D"ltr">&lt;<a href=3D"mailto:touch@isi.edu" targ=
et=3D"_blank">touch@isi.edu</a>&gt;</span> wrote:<br><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex">
<div bgcolor=3D"#FFFFFF"><div>You might want to look at Vintage Cerf&#39;s =
Catenet paper (which this reinvents - , <a href=3D"http://en.wikipedia.org/=
wiki/Catenet" target=3D"_blank">http://en.wikipedia.org/wiki/Catenet</a>), =
and consider the whole point of a single common internerworking layer (of w=
hich the Internet is an example).</div>
<div><br></div><div>Joe</div><div><div class=3D"h5"><div><br>On Sep 10, 201=
2, at 6:07 PM, Pars Mutaf &lt;<a href=3D"mailto:pars.mutaf@gmail.com" targe=
t=3D"_blank">pars.mutaf@gmail.com</a>&gt; wrote:<br><br></div><div></div><b=
lockquote type=3D"cite">
<div>Dear colleagues, <br><br>I believe that the next step in IP&#39;s evol=
ution would not be IPv6. It would be &quot;Discrete IP&quot; allowing any I=
P version.<br>I concluded that Discrete IP better respects the end-to-end p=
rinciples therefore it is economically more viable.<br>

<br>Please read the full document here:<br><br><a href=3D"http://www.scribd=
.com/doc/105448105/Discrete-IP" target=3D"_blank">http://www.scribd.com/doc=
/105448105/Discrete-IP</a><br><br>Cheers, <br><br>Pars<br>
</div></blockquote></div></div><blockquote type=3D"cite"><div><span>_______=
________________________________________</span><br><span>Int-area mailing l=
ist</span><br><span><a href=3D"mailto:Int-area@ietf.org" target=3D"_blank">=
Int-area@ietf.org</a></span><br>
<span><a href=3D"https://www.ietf.org/mailman/listinfo/int-area" target=3D"=
_blank">https://www.ietf.org/mailman/listinfo/int-area</a></span><br></div>=
</blockquote></div></blockquote></div><br>

--20cf307ca5b030083d04c9666e00--

From touch@isi.edu  Mon Sep 10 22:45:42 2012
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E43821F84F8 for <int-area@ietfa.amsl.com>; Mon, 10 Sep 2012 22:45:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b+j24g9ZiZUG for <int-area@ietfa.amsl.com>; Mon, 10 Sep 2012 22:45:41 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 58BCC21F84E7 for <int-area@ietf.org>; Mon, 10 Sep 2012 22:45:41 -0700 (PDT)
Received: from [192.168.0.15] ([210.114.91.71]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id q8B5ivHp003503 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 10 Sep 2012 22:45:08 -0700 (PDT)
Message-ID: <504ECFD9.4090107@isi.edu>
Date: Mon, 10 Sep 2012 22:44:57 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Pars Mutaf <pars.mutaf@gmail.com>
References: <CACQuieaOfyC5pJ2MyHBRTZYWCYfZMp58Ujh8rn0-yBBQL+kkzg@mail.gmail.com> <FAD8796F-0B15-4197-B952-AEE7FD56EDED@isi.edu> <CACQuiebgTXDmUmaE2n1yAbt4vS+V0M60fjXujqtMrh2n1WhPgQ@mail.gmail.com>
In-Reply-To: <CACQuiebgTXDmUmaE2n1yAbt4vS+V0M60fjXujqtMrh2n1WhPgQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] Discrete IP
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Sep 2012 05:45:42 -0000

On 9/10/2012 10:34 PM, Pars Mutaf wrote:
> A single common internetworking layer helps reach other nodes regardless
> of their underlying technology.
>
> Current situation shows that, now we need to reach other nodes
> regardless of their underlying technology, and regardless of their IP
> version. This is what Discrete IP does.

The Internet asks each new technology to support IP, and thus leverage 
everyone else who already speaks IP. In that case, ONE node (the new 
node) needs to be modified.

Your proposal asks others (potentially many others) to adjust to you. 
The Internet was created because that doesn't scale.

> Not allowing different IP versions is a technology blocker.  IPv6 is
> ready, some entities need it, but they cannot use it fully.
> This is because it is required that other entities also transition to
> IPv6.

We already use the kind of translators you're thinking of to support 
allowing IPv4 to talk to IPv6. It works, but it's cumbersome and has a 
lot of opportunity for error.

That's why we try to minimize the number of IP versions - at most, to 
the "preferred" one and sometimes (and hopefully briefly) a "legacy" one.

> They do not have to because they do not see the economical
> incentive. We clearly have a paradox here. Some entities need IPv6,
> others do not. It is also assumed that IP research is done. Someone may
> invent a totally new and wonderful concept of IP and call it IPv7. Some
> entities may use it, while others still use IPv6 and IPv4.
>
> Discrete IP solves this paradox: Everybody do what they wish.

People can do that today, but in the paragraph above this one you 
explain why that didn't work - in the 1960's and today.

Joe

From brian.e.carpenter@gmail.com  Tue Sep 11 00:06:26 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFBCD21F8743 for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 00:06:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.644
X-Spam-Level: 
X-Spam-Status: No, score=-101.644 tagged_above=-999 required=5 tests=[AWL=0.047, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UlEGVfrwL-vA for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 00:06:26 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id BE66A21F8742 for <int-area@ietf.org>; Tue, 11 Sep 2012 00:06:24 -0700 (PDT)
Received: by eaai11 with SMTP id i11so76029eaa.31 for <int-area@ietf.org>; Tue, 11 Sep 2012 00:06:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=edCYWzRbhNurVdgikzSUV/QdhHZkBAcN7r++UlW3lvo=; b=vH9VQOB0X0K6kLR2Gcjef8cRnacI6kL5ZJkYuZ5XoM29ox17sgVpvUyYCtNMp8Xogt nWHLyf1ENd7biE7zCOrhfB7d5NTLuwoqq/IulxNM2Qmuki33MBvzK9x4vv/YM1nAVvDh 3fia0UncwxRaiwpVbi4Hq0QiIv5LxXoBYV9N8MykvmjS+ooV+WHq8cZGm0AIeRi0WQhP bbZEYo+o9XQmCO5fpt5zTB3rUbBNrxNUf13TU5uqRY6ib88Q5HIZeTpLQ1dG8ILfWLqj CkaCteyIjXXAXhzVwqmuhU0WbIqNvfzjo7rXscul7jFtRfEzY442fldilihhoHs+9qjN Eyfw==
Received: by 10.14.205.6 with SMTP id i6mr23739945eeo.13.1347347184020; Tue, 11 Sep 2012 00:06:24 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-219-157.as13285.net. [2.102.219.157]) by mx.google.com with ESMTPS id i8sm44330124eeo.16.2012.09.11.00.06.22 (version=SSLv3 cipher=OTHER); Tue, 11 Sep 2012 00:06:23 -0700 (PDT)
Message-ID: <504EE2F1.4060208@gmail.com>
Date: Tue, 11 Sep 2012 08:06:25 +0100
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: "Fred Baker (fred)" <fred@cisco.com>
References: <504629B7.7080703@gmail.com> <37F823E3-F6AB-4A5D-A925-E4B8691FFFF6@cisco.com>
In-Reply-To: <37F823E3-F6AB-4A5D-A925-E4B8691FFFF6@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: draft-bonica-v6-multihome@tools.ietf.org, Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] draft-bonica-v6-multihome
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Sep 2012 07:06:26 -0000

Hi Fred,

On 11/09/2012 01:07, Fred Baker (fred) wrote:
> On Sep 4, 2012, at 9:17 AM, Brian E Carpenter wrote:
> 
>> The multihoming-without-ipv6nat draft notes that e2e address transparency
>> wasn't listed as a goal in RFC 3582. Having been co-chair of that WG, I'm
>> pretty sure that's because we never imagined anyone proposing anything else
>> for IPv6. That was obviously a failure of the imagination. But apart from
>> that, I don't think it's reasonable to sweep it (and the referral problem
>> that derives from it) under the carpet. It's a problem faced by essentially
>> every distributed app. So I think all proposals for multihoming that affect
>> e2e address transparency need to analyse their impact on referrals.
> 
> If the working group that came up with 3582 had a failure of imagination, it also had a failure of memory. The GSE proposal of 1996 and the 8+8 proposal that came later certainly imagined that the locator might change its encoding as the packet wandered around.

That's true, but those proposals did respect e2e address transparency
and uniqueness as far as the least significant 64 address bits went.
I really think everybody took it for granted.

> In any event, the implications for the fact that the locator might change end to end is addressed in https://tools.ietf.org/html/rfc6296#section-5. 

Indeed, and the nub of that from the point of view of referrals is this:

   o  An application instance wishing to establish communication with a
      peer "behind" an NPTv6 Translator may need to use a different
      address to reach that peer depending on whether the instance is
      behind the same NPTv6 Translator or external to it.

> The same considerations apply to ILNP when it is permitted to translate between internal and external prefixes in the locator. In short, DNS needs to somehow know that the translation occurs and what the related addresses are, so that it can deliver them all in a DNS response. RFC 6296 also discussed hair pinning, because RFC 4787 among others do as well. IMHO, that is actually something that should be disabled; the host should use Happy Eyeballs, and should discover (whether from a split DNS or by trying all the addresses) that the one that works internally is the internal one. That addresses a list of ills. Similar considerations apply to SIP/SDP and probably other protocols that are silly enough to use a network layer address as an application layer identifier - and so, by the way, have problems with mobility.

Well yes, that is the whole point of the referrals discussion, which
also includes discussion of the fact that DNS isn't a complete
solution. My point is that encouraging NPTv6 propagates this set
of problems in the IPv6 world. They aren't going to go away
along with IPv4.

If that's going to be part of the future I think we'd better face up
to it (hence http://tools.ietf.org/html/draft-carpenter-referral-ps).

   Brian

From pars.mutaf@gmail.com  Tue Sep 11 00:20:51 2012
Return-Path: <pars.mutaf@gmail.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A5E021F8587 for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 00:20:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.948
X-Spam-Level: 
X-Spam-Status: No, score=-2.948 tagged_above=-999 required=5 tests=[AWL=0.650,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V5Z3pEduKyqf for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 00:20:50 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6464521E803D for <int-area@ietf.org>; Tue, 11 Sep 2012 00:20:50 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so257733vcb.31 for <int-area@ietf.org>; Tue, 11 Sep 2012 00:20:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=bbkk3stHkESrHdQb+aRTKKU/oGKdHv8+EFewDgifVSE=; b=j9srNddlcGubhB9XcvPmhO+3W/KvO1WbgA3Z6UOtdNIgI9g29SOA8j/S9KTUx+bfQt nCT+f8K4BSz2iylj+U6FMEqSAbftKCjAQoPNuaraFhNsAvz3pSc/sJ7KpQ59p4nOjXAC afL9qbaFpKN0fwXysTuSqGWzvN3ESs5359Lj0RLpY/4RjSpKDYe9vKo4GFmglpDwNO4Z mqnZR/VDee6rH9Xd+jW+3olF8cMJkNtnPfyQ6S4vFayX9sI6kem2wXGslmg+W82iIlNY zsLTUSLjzCT+8Qe7f17elf7z2jH6LfBSeWuxpnB+9wmKyULU3A3CwE9xkAt8hJLSZuPF cQvg==
MIME-Version: 1.0
Received: by 10.221.10.81 with SMTP id oz17mr23630640vcb.67.1347348049886; Tue, 11 Sep 2012 00:20:49 -0700 (PDT)
Received: by 10.58.213.101 with HTTP; Tue, 11 Sep 2012 00:20:49 -0700 (PDT)
In-Reply-To: <504ECFD9.4090107@isi.edu>
References: <CACQuieaOfyC5pJ2MyHBRTZYWCYfZMp58Ujh8rn0-yBBQL+kkzg@mail.gmail.com> <FAD8796F-0B15-4197-B952-AEE7FD56EDED@isi.edu> <CACQuiebgTXDmUmaE2n1yAbt4vS+V0M60fjXujqtMrh2n1WhPgQ@mail.gmail.com> <504ECFD9.4090107@isi.edu>
Date: Tue, 11 Sep 2012 10:20:49 +0300
Message-ID: <CACQuieZZiotwm9RinsuBAfPt6df21Y_z6JJPg4KNTMND2+E5RA@mail.gmail.com>
From: Pars Mutaf <pars.mutaf@gmail.com>
To: Joe Touch <touch@isi.edu>
Content-Type: multipart/alternative; boundary=bcaec54fb75ce6fc3504c967e925
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] Discrete IP
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Sep 2012 07:20:51 -0000

--bcaec54fb75ce6fc3504c967e925
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Sep 11, 2012 at 8:44 AM, Joe Touch <touch@isi.edu> wrote:

>
>
> On 9/10/2012 10:34 PM, Pars Mutaf wrote:
>
>> A single common internetworking layer helps reach other nodes regardless
>> of their underlying technology.
>>
>> Current situation shows that, now we need to reach other nodes
>> regardless of their underlying technology, and regardless of their IP
>> version. This is what Discrete IP does.
>>
>
> The Internet asks each new technology to support IP, and thus leverage
> everyone else who already speaks IP. In that case, ONE node (the new node)
> needs to be modified.
>
> Your proposal asks others (potentially many others) to adjust to you. The
> Internet was created because that doesn't scale.



The situation changed now, we have new problems like IP version transition.
In my view, we are all adjusting to China with the current proposal, and
China is waiting for us.

We can set up Discrete IP and solve this IP transition problem forever.



>
>
>  Not allowing different IP versions is a technology blocker.  IPv6 is
>> ready, some entities need it, but they cannot use it fully.
>> This is because it is required that other entities also transition to
>> IPv6.
>>
>
> We already use the kind of translators you're thinking of to support
> allowing IPv4 to talk to IPv6. It works, but it's cumbersome and has a lot
> of opportunity for error.
>
>
Of course. What I am saying is: Let entities do what they wish. If they
find that translators do not work well, or they are now convinced that
changing their core network is beneficial for them, they can remove the
translators and transition to IPv6. I believe that not everybody will take
the same decisions.

Discrete IP can allow Continuous IP. Let everybody decide for themselves.

The best technology wins.

Discrete IP:

1. Can be a very good transition mechanism to worldwide IPv6 without
enforcement (meaning that we have no idea what is good for others)
2. Can solve the IP transition problem forever.

Everybody, including us, suffer less because we do not decide for others,
we do not pretend to know the future.

The IETF's problem here is choosing between:

1. Designing Discrete IP and solving this IP transition problem forever. We
do not intervene in others' affairs anymore because there is Discrete IP.
2. Working on pushing everybody to IPv6 and see what happens later.

Pars




> That's why we try to minimize the number of IP versions - at most, to the
> "preferred" one and sometimes (and hopefully briefly) a "legacy" one.
>
>
In my opinion, there is too much "we" here. We are blocking the technology.



>
>  They do not have to because they do not see the economical
>> incentive. We clearly have a paradox here. Some entities need IPv6,
>> others do not. It is also assumed that IP research is done. Someone may
>> invent a totally new and wonderful concept of IP and call it IPv7. Some
>> entities may use it, while others still use IPv6 and IPv4.
>>
>> Discrete IP solves this paradox: Everybody do what they wish.
>>
>
> People can do that today, but in the paragraph above this one you explain
> why that didn't work - in the 1960's and today.
>
> Joe
>

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

<br><br><div class=3D"gmail_quote">On Tue, Sep 11, 2012 at 8:44 AM, Joe Tou=
ch <span dir=3D"ltr">&lt;<a href=3D"mailto:touch@isi.edu" target=3D"_blank"=
>touch@isi.edu</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class=3D"im"><br>
<br>
On 9/10/2012 10:34 PM, Pars Mutaf wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
A single common internetworking layer helps reach other nodes regardless<br=
>
of their underlying technology.<br>
<br>
Current situation shows that, now we need to reach other nodes<br>
regardless of their underlying technology, and regardless of their IP<br>
version. This is what Discrete IP does.<br>
</blockquote>
<br></div>
The Internet asks each new technology to support IP, and thus leverage ever=
yone else who already speaks IP. In that case, ONE node (the new node) need=
s to be modified.<br>
<br>
Your proposal asks others (potentially many others) to adjust to you. The I=
nternet was created because that doesn&#39;t scale.</blockquote><div><br><b=
r>The situation changed now, we have new problems like IP version transitio=
n.<br>
In my view, we are all adjusting to China with the current proposal, and Ch=
ina is waiting for us.<br><br>We can set up Discrete IP and solve this IP t=
ransition problem forever.<br><br>=A0</div><blockquote class=3D"gmail_quote=
" style=3D"margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);=
padding-left:1ex">
<div class=3D"im"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Not allowing different IP versions is a technology blocker. =A0IPv6 is<br>
ready, some entities need it, but they cannot use it fully.<br>
This is because it is required that other entities also transition to<br>
IPv6.<br>
</blockquote>
<br></div>
We already use the kind of translators you&#39;re thinking of to support al=
lowing IPv4 to talk to IPv6. It works, but it&#39;s cumbersome and has a lo=
t of opportunity for error.<br>
<br></blockquote><div><br>Of course. What I am saying is: Let entities do w=
hat they wish. If they find that translators do not work well, or they are =
now convinced that changing their core network is beneficial for them, they=
 can remove the translators and transition to IPv6. I believe that not ever=
ybody will take the same decisions.<br>
<br>Discrete IP can allow Continuous IP. Let everybody decide for themselve=
s.<br><br>The best technology wins. <br><br>Discrete IP:<br><br>1. Can be a=
 very good transition mechanism to worldwide IPv6 without enforcement (mean=
ing that we have no idea what is good for others)<br>
2. Can solve the IP transition problem forever. <br><br>Everybody, includin=
g us, suffer less because we do not decide for others, we do not pretend to=
 know the future.<br><br>The IETF&#39;s problem here is choosing between: <=
br>
<br>1. Designing Discrete IP and solving this IP transition problem forever=
. We do not intervene in others&#39; affairs anymore because there is Discr=
ete IP.<br>2. Working on pushing everybody to IPv6 and see what happens lat=
er.<br>
<br>Pars<br><br><br>=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex">
That&#39;s why we try to minimize the number of IP versions - at most, to t=
he &quot;preferred&quot; one and sometimes (and hopefully briefly) a &quot;=
legacy&quot; one.<div class=3D"im"><br></div></blockquote><div><br>In my op=
inion, there is too much &quot;we&quot; here. We are blocking the technolog=
y. <br>
<br>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0pt 0pt 0pt =
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class=
=3D"im">
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
They do not have to because they do not see the economical<br>
incentive. We clearly have a paradox here. Some entities need IPv6,<br>
others do not. It is also assumed that IP research is done. Someone may<br>
invent a totally new and wonderful concept of IP and call it IPv7. Some<br>
entities may use it, while others still use IPv6 and IPv4.<br>
<br>
Discrete IP solves this paradox: Everybody do what they wish.<br>
</blockquote>
<br></div>
People can do that today, but in the paragraph above this one you explain w=
hy that didn&#39;t work - in the 1960&#39;s and today.<span class=3D"HOEnZb=
"><font color=3D"#888888"><br>
<br>
Joe<br>
</font></span></blockquote></div><br>

--bcaec54fb75ce6fc3504c967e925--

From fred@cisco.com  Tue Sep 11 00:21:37 2012
Return-Path: <fred@cisco.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8182A21E8047 for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 00:21:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sMJaCVRsxWXz for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 00:21:36 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id C795B21E803F for <int-area@ietf.org>; Tue, 11 Sep 2012 00:21:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1184; q=dns/txt; s=iport; t=1347348096; x=1348557696; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=RmxfgEV59xaFd3W2yWbkGapknY/8M/ljxbEtQpbCFKc=; b=iH35cNciW9w+88U+miinWhIHYlvcglPcXgsJCHLTcV316znFRlATHhip sxDn/kzn+9mIjMfSLwos2MjeUoG52E0G6Bw8eK0U6+a15/fUw8e/OAdY5 Z5WvedO6Q+p/KUEtn2ym7Z1Wk/QnjoY2BCJeFEEJGS8hsE87ZZ4vB+T4g c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EADrmTlCtJXG9/2dsb2JhbABFu0+BB4IgAQEBAwESASc/BQsCAQg2EDIlAgQOIAeHaAabY6BFixCFRmADlV2ONoFngmY
X-IronPort-AV: E=Sophos;i="4.80,402,1344211200"; d="scan'208";a="120289838"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-5.cisco.com with ESMTP; 11 Sep 2012 07:21:36 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id q8B7LabH028524 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 11 Sep 2012 07:21:36 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.97]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.02.0298.004; Tue, 11 Sep 2012 02:21:35 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Thread-Topic: [Int-area] draft-bonica-v6-multihome
Thread-Index: AQHNirjgL6qzht3KxUCQUn0/l9X2RpeEoVuAgAB07oCAAAQ5AA==
Date: Tue, 11 Sep 2012 07:21:35 +0000
Message-ID: <4619D3A0-E6E0-455C-8825-33CD6BFD2BBC@cisco.com>
References: <504629B7.7080703@gmail.com> <37F823E3-F6AB-4A5D-A925-E4B8691FFFF6@cisco.com> <504EE2F1.4060208@gmail.com>
In-Reply-To: <504EE2F1.4060208@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.32.244.221]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19176.004
x-tm-as-result: No--25.148200-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-ID: <503926FB208E2140BAA181C295082F0F@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<draft-bonica-v6-multihome@tools.ietf.org>" <draft-bonica-v6-multihome@tools.ietf.org>, Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] draft-bonica-v6-multihome
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Sep 2012 07:21:37 -0000

On Sep 11, 2012, at 12:06 AM, Brian E Carpenter wrote:

>   o  An application instance wishing to establish communication with a
>      peer "behind" an NPTv6 Translator may need to use a different
>      address to reach that peer depending on whether the instance is
>      behind the same NPTv6 Translator or external to it.

a problem Happy Eyeballs easily addresses, and which RFC 3484 and 3484-bis =
do not.

> my point is that encouraging NPTv6 propagates this set
> of problems in the IPv6 world. They aren't going to go away
> along with IPv4.

Well, yes, but since edge networks are *not* getting PA addresses from each=
 of their upstream providers and putting a /64 on each LAN from each such a=
ddress, but instead getting PI address space, we have no scalable solution =
for that issue.

What's that rule called? TAANSTAAFL, as I recall. Pretending won't make it =
otherwise. Either the service providers deal with the complexities of the I=
Pv4 route table, or the edge networks deal with the complexities of managin=
g prefixes from each of multiple upstream PA prefixes, or DNS advertises in=
side and outside addresses somehow. Pick one. =

From aservin@lacnic.net  Tue Sep 11 02:22:29 2012
Return-Path: <aservin@lacnic.net>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 087CC21F8545 for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 02:22:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.962
X-Spam-Level: 
X-Spam-Status: No, score=-0.962 tagged_above=-999 required=5 tests=[AWL=0.085,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f6ETINJmAIKR for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 02:22:28 -0700 (PDT)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 0C10521F8543 for <int-area@ietf.org>; Tue, 11 Sep 2012 02:22:28 -0700 (PDT)
Received: from 85-7-200.lacnic.net.uy (unknown [200.7.85.90]) by mail.lacnic.net.uy (Postfix) with ESMTP id 54596308432; Tue, 11 Sep 2012 06:22:17 -0300 (UYT)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: multipart/alternative; boundary="Apple-Mail=_FBB95166-176B-464F-8B68-1EEDF17D89F9"
From: Arturo Servin <aservin@lacnic.net>
In-Reply-To: <CACQuieZZiotwm9RinsuBAfPt6df21Y_z6JJPg4KNTMND2+E5RA@mail.gmail.com>
Date: Tue, 11 Sep 2012 10:22:11 +0100
Message-Id: <987000F4-9B41-4A4F-BF0B-0A207882194B@lacnic.net>
References: <CACQuieaOfyC5pJ2MyHBRTZYWCYfZMp58Ujh8rn0-yBBQL+kkzg@mail.gmail.com> <FAD8796F-0B15-4197-B952-AEE7FD56EDED@isi.edu> <CACQuiebgTXDmUmaE2n1yAbt4vS+V0M60fjXujqtMrh2n1WhPgQ@mail.gmail.com> <504ECFD9.4090107@isi.edu> <CACQuieZZiotwm9RinsuBAfPt6df21Y_z6JJPg4KNTMND2+E5RA@mail.gmail.com>
To: Pars Mutaf <pars.mutaf@gmail.com>
X-Mailer: Apple Mail (2.1278)
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] Discrete IP
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Sep 2012 09:22:29 -0000

--Apple-Mail=_FBB95166-176B-464F-8B68-1EEDF17D89F9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On 11 Sep 2012, at 08:20, Pars Mutaf wrote:

> Discrete IP:
>=20
> 1. Can be a very good transition mechanism to worldwide IPv6 without =
enforcement (meaning that we have no idea what is good for others)

	Do you have some running code?

> 2. Can solve the IP transition problem forever.=20

	Forgive for being sceptical of those all magical technologies =
that solve all the problems of the world. Of course, if you had running =
code that would change my view.

Cheers,
as=

--Apple-Mail=_FBB95166-176B-464F-8B68-1EEDF17D89F9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On 11 Sep 2012, at 08:20, Pars Mutaf wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-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: 0px; font-size: medium; ">Discrete =
IP:<br><br>1. Can be a very good transition mechanism to worldwide IPv6 =
without enforcement (meaning that we have no idea what is good for =
others)<br></span></blockquote><div><br></div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>Do you =
have some running code?</div><br><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-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: 0px; font-size: medium; ">2. Can solve =
the IP transition problem forever.<span =
class=3D"Apple-converted-space">&nbsp;</span></span></blockquote></div><br=
><div><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>Forgive for being&nbsp;sceptical of those all magical =
technologies that solve all the problems of the world. Of course, if you =
had running code that would change my =
view.</div><div><br></div><div>Cheers,</div><div>as</div></body></html>=

--Apple-Mail=_FBB95166-176B-464F-8B68-1EEDF17D89F9--

From brian.e.carpenter@gmail.com  Tue Sep 11 02:36:54 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA34421F87A2 for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 02:36:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sHssTSw0fsJg for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 02:36:54 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id A6D7521F879B for <int-area@ietf.org>; Tue, 11 Sep 2012 02:36:53 -0700 (PDT)
Received: by eekb45 with SMTP id b45so229325eek.31 for <int-area@ietf.org>; Tue, 11 Sep 2012 02:36:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=BZ21ndmWjW7VXDEuEnH60PueZFsLtnBOz/gxsq+5ANs=; b=o5MXTre9C9K1F2yw7zU/OswHI1ip9WmI2jg/X/b5tTheEAn5q1Im59jX+2XeuUa3+2 x4eKmnLqdQyVceWMPVf8VQFBy0B5IqcWAHTb3izTG7QIbA/e9LnVDas5MJH81MTElebp DMiMqLpNq73O8toWqQNNF9/u6QOjQqNyEjebs906FWT8ryrahIpxXpzQ84KX5eBnAfkP r2c7pd09f9+v/xONdAE+ML+JY/hC63pAY4Yg2h+YJgJ1nuM/5BV+Iw+AWhNl85Wdao4Q XPtUxVdqvwdy3QKGBpM0hHJ/Y9tMG565yHTkmWK7tBfPwxxiTbqCsBTwYZ607qY61/G0 TUVA==
Received: by 10.14.202.71 with SMTP id c47mr24688568eeo.42.1347356211594; Tue, 11 Sep 2012 02:36:51 -0700 (PDT)
Received: from [128.232.110.207] (c207.al.cl.cam.ac.uk. [128.232.110.207]) by mx.google.com with ESMTPS id k41sm45442287eep.13.2012.09.11.02.36.50 (version=SSLv3 cipher=OTHER); Tue, 11 Sep 2012 02:36:50 -0700 (PDT)
Message-ID: <504F0635.7050301@gmail.com>
Date: Tue, 11 Sep 2012 10:36:53 +0100
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: "Fred Baker (fred)" <fred@cisco.com>
References: <504629B7.7080703@gmail.com> <37F823E3-F6AB-4A5D-A925-E4B8691FFFF6@cisco.com> <504EE2F1.4060208@gmail.com> <4619D3A0-E6E0-455C-8825-33CD6BFD2BBC@cisco.com>
In-Reply-To: <4619D3A0-E6E0-455C-8825-33CD6BFD2BBC@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: draft-bonica-v6-multihome@tools.ietf.org, Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] draft-bonica-v6-multihome
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Sep 2012 09:36:54 -0000

On 11/09/2012 08:21, Fred Baker (fred) wrote:
> On Sep 11, 2012, at 12:06 AM, Brian E Carpenter wrote:
> 
>>   o  An application instance wishing to establish communication with a
>>      peer "behind" an NPTv6 Translator may need to use a different
>>      address to reach that peer depending on whether the instance is
>>      behind the same NPTv6 Translator or external to it.
> 
> a problem Happy Eyeballs easily addresses, and which RFC 3484 and 3484-bis do not.
> 
>> my point is that encouraging NPTv6 propagates this set
>> of problems in the IPv6 world. They aren't going to go away
>> along with IPv4.
> 
> Well, yes, but since edge networks are *not* getting PA addresses from each of their upstream providers and putting a /64 on each LAN from each such address, but instead getting PI address space, we have no scalable solution for that issue.
> 
> What's that rule called? TAANSTAAFL, as I recall. Pretending won't make it otherwise. Either the service providers deal with the complexities of the IPv4 route table, or the edge networks deal with the complexities of managing prefixes from each of multiple upstream PA prefixes, or DNS advertises inside and outside addresses somehow. Pick one. 

This being the Internet, I expect we'll pick several. But indeed, we have
to deal with current reality and also try to influence long term trends
in a desirable way. I think that getting the problem area well described
is the first step.

    Brian

From pars.mutaf@gmail.com  Tue Sep 11 02:55:26 2012
Return-Path: <pars.mutaf@gmail.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0563221F8786 for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 02:55:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.165
X-Spam-Level: 
X-Spam-Status: No, score=-3.165 tagged_above=-999 required=5 tests=[AWL=0.433,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tPYjv27FKrdo for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 02:55:25 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6955C21F876D for <int-area@ietf.org>; Tue, 11 Sep 2012 02:55:25 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so436395vcb.31 for <int-area@ietf.org>; Tue, 11 Sep 2012 02:55:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Jn9YzRXbjvq02vc4vQ3aNEN7hHhrMVPvJm0WFk0Q/Qc=; b=tpBm/lEQrbe63ge/OdbvXku1xY8JBTwB52liz+QyrRj7tZGTxQ87MsU7hhrRL30cd6 W7nLhmoKxZLdd51f4fZMPjvHgW5bhyJlGihSXLS0X2qsEotgFWNiaWH+oCiZNDc2ASO0 FVJwjoK1DpfyhNstg0oId7sC4lQ2MDoKD6j2OvHBUQNRg2pDo4VJx8BxFJLQrRu7FVs9 ngV+ltjIcnVQYp8rZyt8ThQFVuw8dBNfqOjtgszx9jGNBIq56pnGuPjfuxrXVsGUGWx3 2XS1Gj//hvqzgaRSRJn0qNtLzZnjjjiDTZwmiE2aETZbhvYM41PcRRHgOPHexuhSyGey y1lQ==
MIME-Version: 1.0
Received: by 10.221.10.81 with SMTP id oz17mr24123498vcb.67.1347357324753; Tue, 11 Sep 2012 02:55:24 -0700 (PDT)
Received: by 10.58.213.101 with HTTP; Tue, 11 Sep 2012 02:55:24 -0700 (PDT)
In-Reply-To: <987000F4-9B41-4A4F-BF0B-0A207882194B@lacnic.net>
References: <CACQuieaOfyC5pJ2MyHBRTZYWCYfZMp58Ujh8rn0-yBBQL+kkzg@mail.gmail.com> <FAD8796F-0B15-4197-B952-AEE7FD56EDED@isi.edu> <CACQuiebgTXDmUmaE2n1yAbt4vS+V0M60fjXujqtMrh2n1WhPgQ@mail.gmail.com> <504ECFD9.4090107@isi.edu> <CACQuieZZiotwm9RinsuBAfPt6df21Y_z6JJPg4KNTMND2+E5RA@mail.gmail.com> <987000F4-9B41-4A4F-BF0B-0A207882194B@lacnic.net>
Date: Tue, 11 Sep 2012 12:55:24 +0300
Message-ID: <CACQuiea5gMXjkAT_ywA13EO2+HhY0v_OwwB+4_H_nz-Ddd=MEg@mail.gmail.com>
From: Pars Mutaf <pars.mutaf@gmail.com>
To: Arturo Servin <aservin@lacnic.net>
Content-Type: multipart/alternative; boundary=bcaec54fb75cba3a8b04c96a12db
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] Discrete IP
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Sep 2012 09:55:26 -0000

--bcaec54fb75cba3a8b04c96a12db
Content-Type: text/plain; charset=ISO-8859-1

"Do you have some running code?"

These are all ideas and behavior that we adopted without questioning. We
use them in wrong situations generally.

We first discuss the idea, then implement.

The fact that there is running code doesn't mean that it is a good idea.


On Tue, Sep 11, 2012 at 12:22 PM, Arturo Servin <aservin@lacnic.net> wrote:

>
> On 11 Sep 2012, at 08:20, Pars Mutaf wrote:
>
> Discrete IP:
>
> 1. Can be a very good transition mechanism to worldwide IPv6 without
> enforcement (meaning that we have no idea what is good for others)
>
>
> Do you have some running code?
>
> 2. Can solve the IP transition problem forever.
>
>
> Forgive for being sceptical of those all magical technologies that solve
> all the problems of the world. Of course, if you had running code that
> would change my view.
>
> Cheers,
> as
>

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

<br>&quot;Do you have some running code?&quot;<br><br>These are all ideas a=
nd behavior that we adopted without questioning. We use them in wrong situa=
tions generally. <br><br>We first discuss the idea, then implement.<br><br>
The fact that there is running code doesn&#39;t mean that it is a good idea=
.<br><br><br><div class=3D"gmail_quote">On Tue, Sep 11, 2012 at 12:22 PM, A=
rturo Servin <span dir=3D"ltr">&lt;<a href=3D"mailto:aservin@lacnic.net" ta=
rget=3D"_blank">aservin@lacnic.net</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word"><br><div=
><div class=3D"im"><div>On 11 Sep 2012, at 08:20, Pars Mutaf wrote:</div><b=
r><blockquote type=3D"cite">
<span style=3D"border-collapse:separate;font-family:Helvetica;font-style:no=
rmal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-heig=
ht:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white=
-space:normal;word-spacing:0px;font-size:medium">Discrete IP:<br>
<br>1. Can be a very good transition mechanism to worldwide IPv6 without en=
forcement (meaning that we have no idea what is good for others)<br></span>=
</blockquote><div><br></div></div><div><span style=3D"white-space:pre-wrap"=
>	</span>Do you have some running code?</div>
<div class=3D"im"><br><blockquote type=3D"cite"><span style=3D"border-colla=
pse:separate;font-family:Helvetica;font-style:normal;font-variant:normal;fo=
nt-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webki=
t-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:=
0px;font-size:medium">2. Can solve the IP transition problem forever.<span>=
=A0</span></span></blockquote>
</div></div><br><div><span style=3D"white-space:pre-wrap">	</span>Forgive f=
or being=A0sceptical of those all magical technologies that solve all the p=
roblems of the world. Of course, if you had running code that would change =
my view.</div>
<div><br></div><div>Cheers,</div><div>as</div></div></blockquote></div><br>

--bcaec54fb75cba3a8b04c96a12db--

From aservin@lacnic.net  Tue Sep 11 03:04:46 2012
Return-Path: <aservin@lacnic.net>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D31F621F8613 for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 03:04:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.972
X-Spam-Level: 
X-Spam-Status: No, score=-0.972 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t2sqYuQfDOXL for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 03:04:46 -0700 (PDT)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id B967421F8610 for <int-area@ietf.org>; Tue, 11 Sep 2012 03:04:45 -0700 (PDT)
Received: from 85-7-200.lacnic.net.uy (unknown [200.7.85.90]) by mail.lacnic.net.uy (Postfix) with ESMTP id E03E0308455; Tue, 11 Sep 2012 07:04:29 -0300 (UYT)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: multipart/alternative; boundary="Apple-Mail=_F8B643DC-9EBD-4B95-8CBD-1CF11BF15D32"
From: Arturo Servin <aservin@lacnic.net>
In-Reply-To: <CACQuiea5gMXjkAT_ywA13EO2+HhY0v_OwwB+4_H_nz-Ddd=MEg@mail.gmail.com>
Date: Tue, 11 Sep 2012 11:04:22 +0100
Message-Id: <0E3416E0-1F00-42C8-B867-DF8726D9AC26@lacnic.net>
References: <CACQuieaOfyC5pJ2MyHBRTZYWCYfZMp58Ujh8rn0-yBBQL+kkzg@mail.gmail.com> <FAD8796F-0B15-4197-B952-AEE7FD56EDED@isi.edu> <CACQuiebgTXDmUmaE2n1yAbt4vS+V0M60fjXujqtMrh2n1WhPgQ@mail.gmail.com> <504ECFD9.4090107@isi.edu> <CACQuieZZiotwm9RinsuBAfPt6df21Y_z6JJPg4KNTMND2+E5RA@mail.gmail.com> <987000F4-9B41-4A4F-BF0B-0A207882194B@lacnic.net> <CACQuiea5gMXjkAT_ywA13EO2+HhY0v_OwwB+4_H_nz-Ddd=MEg@mail.gmail.com>
To: Pars Mutaf <pars.mutaf@gmail.com>
X-Mailer: Apple Mail (2.1278)
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] Discrete IP
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Sep 2012 10:04:47 -0000

--Apple-Mail=_F8B643DC-9EBD-4B95-8CBD-1CF11BF15D32
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On 11 Sep 2012, at 10:55, Pars Mutaf wrote:

>=20
> "Do you have some running code?"
>=20
> These are all ideas and behavior that we adopted without questioning. =
We use them in wrong situations generally.=20

	Which already exists in many forms of translation mechanisms =
that we know are not the best way to solve the problem. There are plenty =
of documents on the Internet that will tell you why.

>=20
> We first discuss the idea, then implement.
>=20
> The fact that there is running code doesn't mean that it is a good =
idea.


	But if it were, it would help to convince the sceptical like me.

	Also, the fact that there is not running code could mean that =
the idea is impractical and infeasible.

Cheers,
as

>=20
>=20
> On Tue, Sep 11, 2012 at 12:22 PM, Arturo Servin <aservin@lacnic.net> =
wrote:
>=20
> On 11 Sep 2012, at 08:20, Pars Mutaf wrote:
>=20
>> Discrete IP:
>>=20
>> 1. Can be a very good transition mechanism to worldwide IPv6 without =
enforcement (meaning that we have no idea what is good for others)
>=20
> 	Do you have some running code?
>=20
>> 2. Can solve the IP transition problem forever.=20
>=20
> 	Forgive for being sceptical of those all magical technologies =
that solve all the problems of the world. Of course, if you had running =
code that would change my view.
>=20
> Cheers,
> as
>=20


--Apple-Mail=_F8B643DC-9EBD-4B95-8CBD-1CF11BF15D32
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 11 Sep 2012, at 10:55, Pars Mutaf wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><br>"Do you have some running code?"<br><br>These are all ideas and behavior that we adopted without questioning. We use them in wrong situations generally. <br></blockquote><div><br></div><div><span class="Apple-tab-span" style="white-space:pre">	</span>Which already exists in many forms of translation mechanisms that we know are not the best way to solve the problem. There are plenty of documents on the Internet that will tell you why.</div><br><blockquote type="cite"><br>We first discuss the idea, then implement.<br><br>
The fact that there is running code doesn't mean that it is a good idea.<br></blockquote><div><br></div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre">	</span>But if it were, it would help to convince the sceptical like me.</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre">	</span>Also, the fact that there is not running code could mean that the idea is impractical and infeasible.</div><div><br></div><div>Cheers,</div><div>as</div><br><blockquote type="cite"><br><br><div class="gmail_quote">On Tue, Sep 11, 2012 at 12:22 PM, Arturo Servin <span dir="ltr">&lt;<a href="mailto:aservin@lacnic.net" target="_blank">aservin@lacnic.net</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><div class="im"><div>On 11 Sep 2012, at 08:20, Pars Mutaf wrote:</div><br><blockquote type="cite">
<span style="border-collapse:separate;font-family:Helvetica;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium">Discrete IP:<br>
<br>1. Can be a very good transition mechanism to worldwide IPv6 without enforcement (meaning that we have no idea what is good for others)<br></span></blockquote><div><br></div></div><div><span style="white-space:pre-wrap">	</span>Do you have some running code?</div>
<div class="im"><br><blockquote type="cite"><span style="border-collapse:separate;font-family:Helvetica;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium">2. Can solve the IP transition problem forever.<span>&nbsp;</span></span></blockquote>
</div></div><br><div><span style="white-space:pre-wrap">	</span>Forgive for being&nbsp;sceptical of those all magical technologies that solve all the problems of the world. Of course, if you had running code that would change my view.</div>
<div><br></div><div>Cheers,</div><div>as</div></div></blockquote></div><br>
</blockquote></div><br></body></html>
--Apple-Mail=_F8B643DC-9EBD-4B95-8CBD-1CF11BF15D32--

From pars.mutaf@gmail.com  Tue Sep 11 03:21:54 2012
Return-Path: <pars.mutaf@gmail.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D26D21F8790 for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 03:21:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.273
X-Spam-Level: 
X-Spam-Status: No, score=-3.273 tagged_above=-999 required=5 tests=[AWL=0.325,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cK2xir9fbqsU for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 03:21:53 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id C50B621F8775 for <int-area@ietf.org>; Tue, 11 Sep 2012 03:21:53 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so582865obb.31 for <int-area@ietf.org>; Tue, 11 Sep 2012 03:21:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=72B+4vF4auydZ9LeMgA1ye6d9LyHJZmtHjf3kHm0+tQ=; b=ZQ4eYOL6SUQC2W/bqmXXYdNhvaHC0rWDyjI0iZqBUizw558605R+gXnL9iYmKjiZX8 5fDGqw2pJ0VvzJevhsGV70tQPP0GZr9qAMp0fkNJzspZhwK/yCjLVB7PEP8GQ1qLl0FB kr9mXmXomO/jSZq6tfRcktWbkyssO5ohaNxlTi3sBsfuezWWLUqwhAuDJzDsZdAdDVbR JEMupjYsf5XgBsJ0i1mxHeeQGsb6mfV3VMkKNaEI8gfgd9Ft5JoIF5f3L5KLHFvEHd56 9nzdCtuFQD8cLRcKzvYJoXIsYPwGEZzPe8ZQ1/HiQqbeoyN1YUbcwR7eYwyA4nZmSZ25 HTpw==
MIME-Version: 1.0
Received: by 10.182.5.200 with SMTP id u8mr17085959obu.91.1347358913421; Tue, 11 Sep 2012 03:21:53 -0700 (PDT)
Received: by 10.76.28.1 with HTTP; Tue, 11 Sep 2012 03:21:52 -0700 (PDT)
In-Reply-To: <0E3416E0-1F00-42C8-B867-DF8726D9AC26@lacnic.net>
References: <CACQuieaOfyC5pJ2MyHBRTZYWCYfZMp58Ujh8rn0-yBBQL+kkzg@mail.gmail.com> <FAD8796F-0B15-4197-B952-AEE7FD56EDED@isi.edu> <CACQuiebgTXDmUmaE2n1yAbt4vS+V0M60fjXujqtMrh2n1WhPgQ@mail.gmail.com> <504ECFD9.4090107@isi.edu> <CACQuieZZiotwm9RinsuBAfPt6df21Y_z6JJPg4KNTMND2+E5RA@mail.gmail.com> <987000F4-9B41-4A4F-BF0B-0A207882194B@lacnic.net> <CACQuiea5gMXjkAT_ywA13EO2+HhY0v_OwwB+4_H_nz-Ddd=MEg@mail.gmail.com> <0E3416E0-1F00-42C8-B867-DF8726D9AC26@lacnic.net>
Date: Tue, 11 Sep 2012 13:21:52 +0300
Message-ID: <CACQuieYuXPMNCteb_HNvGZrSmx3red7NPFmFbBE8cY9KT8LOQg@mail.gmail.com>
From: Pars Mutaf <pars.mutaf@gmail.com>
To: Arturo Servin <aservin@lacnic.net>
Content-Type: multipart/alternative; boundary=f46d0447898d6b611b04c96a717f
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] Discrete IP
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Sep 2012 10:21:54 -0000

--f46d0447898d6b611b04c96a717f
Content-Type: text/plain; charset=ISO-8859-1

Hi Arturo,

On Tue, Sep 11, 2012 at 1:04 PM, Arturo Servin <aservin@lacnic.net> wrote:

>
> On 11 Sep 2012, at 10:55, Pars Mutaf wrote:
>
>
> "Do you have some running code?"
>
> These are all ideas and behavior that we adopted without questioning. We
> use them in wrong situations generally.
>
>
> Which already exists in many forms of translation mechanisms that we know
> are not the best way to solve the problem. There are plenty of documents on
> the Internet that will tell you why.
>


I believe that people should be able to choose their own solutions. Would
you transition to IPv6 if Discrete IP worked for you? Some entities may,
others may not, others may do it when they have money, yet others may
invent and use IPv7. We cannot know.

This means that China may use IPv6, Uruguay may not. We see what people
decide, we cannot force them. They use translators if they wish. I want to
develop and test a new IPvX in my university and be reachable to the world,
who can say no?

Not knowing what is good for others, not knowing the future, helps
technology develop. It also reduces our suffering because we do not try to
know the unknowable.



>
> We first discuss the idea, then implement.
>
> The fact that there is running code doesn't mean that it is a good idea.
>
>
>
> But if it were, it would help to convince the sceptical like me.
>
>
I don't see why this would convince you.



> Also, the fact that there is not running code could mean that the idea is
> impractical and infeasible.
>
>
No you can implement anything. Even the worst idea.

Pars



> Cheers,
> as
>
>
>
> On Tue, Sep 11, 2012 at 12:22 PM, Arturo Servin <aservin@lacnic.net>wrote:
>
>>
>> On 11 Sep 2012, at 08:20, Pars Mutaf wrote:
>>
>> Discrete IP:
>>
>> 1. Can be a very good transition mechanism to worldwide IPv6 without
>> enforcement (meaning that we have no idea what is good for others)
>>
>>
>> Do you have some running code?
>>
>> 2. Can solve the IP transition problem forever.
>>
>>
>> Forgive for being sceptical of those all magical technologies that solve
>> all the problems of the world. Of course, if you had running code that
>> would change my view.
>>
>> Cheers,
>> as
>>
>
>
>

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

Hi Arturo,<br><br><div class=3D"gmail_quote">On Tue, Sep 11, 2012 at 1:04 P=
M, Arturo Servin <span dir=3D"ltr">&lt;<a href=3D"mailto:aservin@lacnic.net=
" target=3D"_blank">aservin@lacnic.net</a>&gt;</span> wrote:<br><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex">
<div style=3D"word-wrap:break-word"><br><div><div class=3D"im"><div>On 11 S=
ep 2012, at 10:55, Pars Mutaf wrote:</div><br><blockquote type=3D"cite"><br=
>&quot;Do you have some running code?&quot;<br><br>These are all ideas and =
behavior that we adopted without questioning. We use them in wrong situatio=
ns generally. <br>
</blockquote><div><br></div></div><div><span style=3D"white-space:pre-wrap"=
>	</span>Which already exists in many forms of translation mechanisms that =
we know are not the best way to solve the problem. There are plenty of docu=
ments on the Internet that will tell you why.</div>
</div></div></blockquote><div><br><br>I believe that people should be able =
to choose their own solutions. Would you transition to IPv6 if Discrete IP =
worked for you? Some entities may, others may not, others may do it when th=
ey have money, yet others may invent and use IPv7. We cannot know. <br>
<br>This means that China may use IPv6, Uruguay may not. We see what people=
 decide, we cannot force them. They use translators if they wish. I want to=
 develop and test a new IPvX in my university and be reachable to the world=
, who can say no?<br>
<br>Not knowing what is good for others, not knowing the future, helps tech=
nology develop. It also reduces our suffering because we do not try to know=
 the unknowable.<br>
<br>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0pt 0pt 0pt =
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style=
=3D"word-wrap:break-word"><div><div class=3D"im"><blockquote type=3D"cite">=
<br>We first discuss the idea, then implement.<br>
<br>
The fact that there is running code doesn&#39;t mean that it is a good idea=
.<br></blockquote><div><br></div><div><br></div></div><div><span style=3D"w=
hite-space:pre-wrap">	</span>But if it were, it would help to convince the =
sceptical like me.</div>
<div><br></div></div></div></blockquote><div><br>I don&#39;t see why this w=
ould convince you. <br><br>=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">
<div style=3D"word-wrap:break-word"><div><div></div><div><span style=3D"whi=
te-space:pre-wrap">	</span>Also, the fact that there is not running code co=
uld mean that the idea is impractical and infeasible.</div><div><br></div><=
/div>
</div></blockquote><div><br>No you can implement anything. Even the worst i=
dea.<br><br>Pars<br><br>=A0</div><blockquote class=3D"gmail_quote" style=3D=
"margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex">
<div style=3D"word-wrap:break-word"><div><div></div><div>Cheers,</div><div>=
as</div><div class=3D"im"><br><blockquote type=3D"cite"><br><br><div class=
=3D"gmail_quote">On Tue, Sep 11, 2012 at 12:22 PM, Arturo Servin <span dir=
=3D"ltr">&lt;<a href=3D"mailto:aservin@lacnic.net" target=3D"_blank">aservi=
n@lacnic.net</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word"><br><div=
><div><div>On 11 Sep 2012, at 08:20, Pars Mutaf wrote:</div><br><blockquote=
 type=3D"cite">

<span style=3D"border-collapse:separate;font-family:Helvetica;font-style:no=
rmal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-heig=
ht:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white=
-space:normal;word-spacing:0px;font-size:medium">Discrete IP:<br>

<br>1. Can be a very good transition mechanism to worldwide IPv6 without en=
forcement (meaning that we have no idea what is good for others)<br></span>=
</blockquote><div><br></div></div><div><span style=3D"white-space:pre-wrap"=
>	</span>Do you have some running code?</div>

<div><br><blockquote type=3D"cite"><span style=3D"border-collapse:separate;=
font-family:Helvetica;font-style:normal;font-variant:normal;font-weight:nor=
mal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-i=
ndent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size=
:medium">2. Can solve the IP transition problem forever.<span>=A0</span></s=
pan></blockquote>

</div></div><br><div><span style=3D"white-space:pre-wrap">	</span>Forgive f=
or being=A0sceptical of those all magical technologies that solve all the p=
roblems of the world. Of course, if you had running code that would change =
my view.</div>

<div><br></div><div>Cheers,</div><div>as</div></div></blockquote></div><br>
</blockquote></div></div><br></div></blockquote></div><br>

--f46d0447898d6b611b04c96a717f--

From aservin@lacnic.net  Tue Sep 11 03:38:51 2012
Return-Path: <aservin@lacnic.net>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED49321F87C1 for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 03:38:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.981
X-Spam-Level: 
X-Spam-Status: No, score=-0.981 tagged_above=-999 required=5 tests=[AWL=0.066,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nd0Q6ub4WGkl for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 03:38:50 -0700 (PDT)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 7C66C21F87BA for <int-area@ietf.org>; Tue, 11 Sep 2012 03:38:49 -0700 (PDT)
Received: from 85-7-200.lacnic.net.uy (unknown [200.7.85.90]) by mail.lacnic.net.uy (Postfix) with ESMTP id BACE4308436; Tue, 11 Sep 2012 07:38:44 -0300 (UYT)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: multipart/alternative; boundary="Apple-Mail=_D889ED7B-FFA0-4AD4-86BA-94E2B5941D54"
From: Arturo Servin <aservin@lacnic.net>
In-Reply-To: <CACQuieYuXPMNCteb_HNvGZrSmx3red7NPFmFbBE8cY9KT8LOQg@mail.gmail.com>
Date: Tue, 11 Sep 2012 11:38:37 +0100
Message-Id: <C83D6793-ED56-41ED-9892-2D51F3BA0851@lacnic.net>
References: <CACQuieaOfyC5pJ2MyHBRTZYWCYfZMp58Ujh8rn0-yBBQL+kkzg@mail.gmail.com> <FAD8796F-0B15-4197-B952-AEE7FD56EDED@isi.edu> <CACQuiebgTXDmUmaE2n1yAbt4vS+V0M60fjXujqtMrh2n1WhPgQ@mail.gmail.com> <504ECFD9.4090107@isi.edu> <CACQuieZZiotwm9RinsuBAfPt6df21Y_z6JJPg4KNTMND2+E5RA@mail.gmail.com> <987000F4-9B41-4A4F-BF0B-0A207882194B@lacnic.net> <CACQuiea5gMXjkAT_ywA13EO2+HhY0v_OwwB+4_H_nz-Ddd=MEg@mail.gmail.com> <0E3416E0-1F00-42C8-B867-DF8726D9AC26@lacnic.net> <CACQuieYuXPMNCteb_HNvGZrSmx3red7NPFmFbBE8cY9KT8LOQg@mail.gmail.com>
To: Pars Mutaf <pars.mutaf@gmail.com>
X-Mailer: Apple Mail (2.1278)
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] Discrete IP
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Sep 2012 10:38:51 -0000

--Apple-Mail=_D889ED7B-FFA0-4AD4-86BA-94E2B5941D54
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


	The big flaw of your idea is that you suppose that translation =
magically works, which it is not true due to the complexity of some =
protocols. That is why I am sceptical.

	You are very welcome to try your idea. Let me know how it goes.

/as
=09

On 11 Sep 2012, at 11:21, Pars Mutaf wrote:

> Hi Arturo,
>=20
> On Tue, Sep 11, 2012 at 1:04 PM, Arturo Servin <aservin@lacnic.net> =
wrote:
>=20
> On 11 Sep 2012, at 10:55, Pars Mutaf wrote:
>=20
>>=20
>> "Do you have some running code?"
>>=20
>> These are all ideas and behavior that we adopted without questioning. =
We use them in wrong situations generally.=20
>=20
> 	Which already exists in many forms of translation mechanisms =
that we know are not the best way to solve the problem. There are plenty =
of documents on the Internet that will tell you why.
>=20
>=20
> I believe that people should be able to choose their own solutions. =
Would you transition to IPv6 if Discrete IP worked for you? Some =
entities may, others may not, others may do it when they have money, yet =
others may invent and use IPv7. We cannot know.=20
>=20
> This means that China may use IPv6, Uruguay may not. We see what =
people decide, we cannot force them. They use translators if they wish. =
I want to develop and test a new IPvX in my university and be reachable =
to the world, who can say no?
>=20
> Not knowing what is good for others, not knowing the future, helps =
technology develop. It also reduces our suffering because we do not try =
to know the unknowable.
>=20
> =20
>>=20
>> We first discuss the idea, then implement.
>>=20
>> The fact that there is running code doesn't mean that it is a good =
idea.
>=20
>=20
> 	But if it were, it would help to convince the sceptical like me.
>=20
>=20
> I don't see why this would convince you.=20
>=20
> =20
> 	Also, the fact that there is not running code could mean that =
the idea is impractical and infeasible.
>=20
>=20
> No you can implement anything. Even the worst idea.
>=20
> Pars
>=20
> =20
> Cheers,
> as
>=20
>>=20
>>=20
>> On Tue, Sep 11, 2012 at 12:22 PM, Arturo Servin <aservin@lacnic.net> =
wrote:
>>=20
>> On 11 Sep 2012, at 08:20, Pars Mutaf wrote:
>>=20
>>> Discrete IP:
>>>=20
>>> 1. Can be a very good transition mechanism to worldwide IPv6 without =
enforcement (meaning that we have no idea what is good for others)
>>=20
>> 	Do you have some running code?
>>=20
>>> 2. Can solve the IP transition problem forever.=20
>>=20
>> 	Forgive for being sceptical of those all magical technologies =
that solve all the problems of the world. Of course, if you had running =
code that would change my view.
>>=20
>> Cheers,
>> as
>>=20
>=20
>=20


--Apple-Mail=_D889ED7B-FFA0-4AD4-86BA-94E2B5941D54
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><br></div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>The big flaw of your idea is that =
you suppose that translation magically works, which it is not true due =
to the complexity of some protocols. That is why I am =
sceptical.</div><div><br></div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>You are very welcome to try your =
idea. Let me know how it =
goes.</div><div><br></div><div>/as</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span></div><br><div><div>On 11 Sep 2012, at 11:21, Pars Mutaf =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">Hi Arturo,<br><br><div class=3D"gmail_quote">On Tue, Sep =
11, 2012 at 1:04 PM, Arturo Servin <span dir=3D"ltr">&lt;<a =
href=3D"mailto:aservin@lacnic.net" =
target=3D"_blank">aservin@lacnic.net</a>&gt;</span> =
wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word"><br><div><div class=3D"im"><div>On =
11 Sep 2012, at 10:55, Pars Mutaf wrote:</div><br><blockquote =
type=3D"cite"><br>"Do you have some running code?"<br><br>These are all =
ideas and behavior that we adopted without questioning. We use them in =
wrong situations generally. <br>
</blockquote><div><br></div></div><div><span =
style=3D"white-space:pre-wrap">	</span>Which already exists in many =
forms of translation mechanisms that we know are not the best way to =
solve the problem. There are plenty of documents on the Internet that =
will tell you why.</div>
</div></div></blockquote><div><br><br>I believe that people should be =
able to choose their own solutions. Would you transition to IPv6 if =
Discrete IP worked for you? Some entities may, others may not, others =
may do it when they have money, yet others may invent and use IPv7. We =
cannot know. <br>
<br>This means that China may use IPv6, Uruguay may not. We see what =
people decide, we cannot force them. They use translators if they wish. =
I want to develop and test a new IPvX in my university and be reachable =
to the world, who can say no?<br>
<br>Not knowing what is good for others, not knowing the future, helps =
technology develop. It also reduces our suffering because we do not try =
to know the unknowable.<br>
<br>&nbsp;</div><blockquote class=3D"gmail_quote" style=3D"margin:0pt =
0pt 0pt 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex"><div =
style=3D"word-wrap:break-word"><div><div class=3D"im"><blockquote =
type=3D"cite"><br>We first discuss the idea, then implement.<br>
<br>
The fact that there is running code doesn't mean that it is a good =
idea.<br></blockquote><div><br></div><div><br></div></div><div><span =
style=3D"white-space:pre-wrap">	</span>But if it were, it would help to =
convince the sceptical like me.</div>
<div><br></div></div></div></blockquote><div><br>I don't see why this =
would convince you. <br><br>&nbsp;</div><blockquote class=3D"gmail_quote" =
style=3D"margin:0pt 0pt 0pt 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex">
<div style=3D"word-wrap:break-word"><div><div></div><div><span =
style=3D"white-space:pre-wrap">	</span>Also, the fact that there is not =
running code could mean that the idea is impractical and =
infeasible.</div><div><br></div></div>
</div></blockquote><div><br>No you can implement anything. Even the =
worst idea.<br><br>Pars<br><br>&nbsp;</div><blockquote =
class=3D"gmail_quote" style=3D"margin:0pt 0pt 0pt 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex">
<div =
style=3D"word-wrap:break-word"><div><div></div><div>Cheers,</div><div>as</=
div><div class=3D"im"><br><blockquote type=3D"cite"><br><br><div =
class=3D"gmail_quote">On Tue, Sep 11, 2012 at 12:22 PM, Arturo Servin =
<span dir=3D"ltr">&lt;<a href=3D"mailto:aservin@lacnic.net" =
target=3D"_blank">aservin@lacnic.net</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div =
style=3D"word-wrap:break-word"><br><div><div><div>On 11 Sep 2012, at =
08:20, Pars Mutaf wrote:</div><br><blockquote type=3D"cite">

<span =
style=3D"border-collapse:separate;font-family:Helvetica;font-style:normal;=
font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:n=
ormal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-sp=
ace:normal;word-spacing:0px;font-size:medium">Discrete IP:<br>

<br>1. Can be a very good transition mechanism to worldwide IPv6 without =
enforcement (meaning that we have no idea what is good for =
others)<br></span></blockquote><div><br></div></div><div><span =
style=3D"white-space:pre-wrap">	</span>Do you have some running =
code?</div>

<div><br><blockquote type=3D"cite"><span =
style=3D"border-collapse:separate;font-family:Helvetica;font-style:normal;=
font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:n=
ormal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-sp=
ace:normal;word-spacing:0px;font-size:medium">2. Can solve the IP =
transition problem forever.<span>&nbsp;</span></span></blockquote>

</div></div><br><div><span style=3D"white-space:pre-wrap">	=
</span>Forgive for being&nbsp;sceptical of those all magical =
technologies that solve all the problems of the world. Of course, if you =
had running code that would change my view.</div>

=
<div><br></div><div>Cheers,</div><div>as</div></div></blockquote></div><br=
>
</blockquote></div></div><br></div></blockquote></div><br>
</blockquote></div><br></body></html>=

--Apple-Mail=_D889ED7B-FFA0-4AD4-86BA-94E2B5941D54--

From pars.mutaf@gmail.com  Tue Sep 11 04:58:04 2012
Return-Path: <pars.mutaf@gmail.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E112821F87CC for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 04:58:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.338
X-Spam-Level: 
X-Spam-Status: No, score=-3.338 tagged_above=-999 required=5 tests=[AWL=0.260,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fAAMs2wKkLxm for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 04:58:03 -0700 (PDT)
Received: from mail-oa0-f44.google.com (mail-oa0-f44.google.com [209.85.219.44]) by ietfa.amsl.com (Postfix) with ESMTP id B739E21F87C7 for <int-area@ietf.org>; Tue, 11 Sep 2012 04:58:03 -0700 (PDT)
Received: by oagk14 with SMTP id k14so226136oag.31 for <int-area@ietf.org>; Tue, 11 Sep 2012 04:58:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=VAJMh37vkxwfI82duZjE6iQgRj6VQtAqJNPv5W6iBMY=; b=HbsPDFav3k7g0VJT4/a1jO9EW8gInrt8bNsTzynsafUTanZSeQlS1H9NYOHSkSZ2jl xPRqIlFZF+Tfi9SFma7XJkANSdbzDbRA/H2FJ/+a8rxq46l2fQqhNi2DOuO5FDWg/7DT Owvf/roex5hX6DvvuLdR9b7ZLZ2N2f7Lka1G1Yge02rOa37t6UOkU4wUPDfDEAXNIzPI b6dL3qaSeTFYicbdImFWHJ5YFCFGrc79J4iGpjrAjlQJ0ogPqADnx1TWYihW7VTVdvVt PKnLr140kOS3S0/LF/tQX8Fyr2HA+74NaxJ+WINcvV35wXu09NSBa5NcFVGux+Bqs/m/ VUOA==
MIME-Version: 1.0
Received: by 10.60.8.71 with SMTP id p7mr18027613oea.56.1347364683354; Tue, 11 Sep 2012 04:58:03 -0700 (PDT)
Received: by 10.76.28.1 with HTTP; Tue, 11 Sep 2012 04:58:03 -0700 (PDT)
In-Reply-To: <C83D6793-ED56-41ED-9892-2D51F3BA0851@lacnic.net>
References: <CACQuieaOfyC5pJ2MyHBRTZYWCYfZMp58Ujh8rn0-yBBQL+kkzg@mail.gmail.com> <FAD8796F-0B15-4197-B952-AEE7FD56EDED@isi.edu> <CACQuiebgTXDmUmaE2n1yAbt4vS+V0M60fjXujqtMrh2n1WhPgQ@mail.gmail.com> <504ECFD9.4090107@isi.edu> <CACQuieZZiotwm9RinsuBAfPt6df21Y_z6JJPg4KNTMND2+E5RA@mail.gmail.com> <987000F4-9B41-4A4F-BF0B-0A207882194B@lacnic.net> <CACQuiea5gMXjkAT_ywA13EO2+HhY0v_OwwB+4_H_nz-Ddd=MEg@mail.gmail.com> <0E3416E0-1F00-42C8-B867-DF8726D9AC26@lacnic.net> <CACQuieYuXPMNCteb_HNvGZrSmx3red7NPFmFbBE8cY9KT8LOQg@mail.gmail.com> <C83D6793-ED56-41ED-9892-2D51F3BA0851@lacnic.net>
Date: Tue, 11 Sep 2012 14:58:03 +0300
Message-ID: <CACQuieZc2s6EdDRJPO1LPBokKh5-jaboNs_M1w4BYqwJ80GK4g@mail.gmail.com>
From: Pars Mutaf <pars.mutaf@gmail.com>
To: Arturo Servin <aservin@lacnic.net>
Content-Type: multipart/alternative; boundary=e89a8ff1c5545593ab04c96bc912
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] Discrete IP
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Sep 2012 11:58:05 -0000

--e89a8ff1c5545593ab04c96bc912
Content-Type: text/plain; charset=ISO-8859-1

By "translation" I mean something completely new. It is written in the
paper:

Splitting the path to two (or more) parts. One part is IPv4, the other part
is IPv6.

Source IPv4 <-> Translator IPv4
Translator IPv6 <-> Destination IPv6

We take the data found in the IPv4 packet, we put it in an IPv6 packet (and
vice versa).

By translation, I do not mean translating the information found the in the
headers. We only copy data. (from IPv4 packet to IPv6 packet and vice
versa). See the paper for illustration (Figure 2).

How TCP works on this, I don't know yet. I don't have to know it right now.
What is important is "What we want".

1. Worry about the core network, i.e. others' IP version preferences
forever, or
2. Change the end-node TCP design, if necessary to solve this problem.

Sending a packet from an IPv4 host to an IPv6 host, connected using such a
translator, is a routing problem. The problem is that TCP assumes same IP
version for source and destination. We need another type of identifier,
perhaps. Such proposals exist already. But again, what is important here is
not the solution. What is important is "What we want". It is one of the two
possibilities mentioned above. The second one, better respects the
end-to-end principle.

Pars


On Tue, Sep 11, 2012 at 1:38 PM, Arturo Servin <aservin@lacnic.net> wrote:

>
> The big flaw of your idea is that you suppose that translation magically
> works, which it is not true due to the complexity of some protocols. That
> is why I am sceptical.
>
> You are very welcome to try your idea. Let me know how it goes.
>
> /as
>
> On 11 Sep 2012, at 11:21, Pars Mutaf wrote:
>
> Hi Arturo,
>
> On Tue, Sep 11, 2012 at 1:04 PM, Arturo Servin <aservin@lacnic.net> wrote:
>
>>
>> On 11 Sep 2012, at 10:55, Pars Mutaf wrote:
>>
>>
>> "Do you have some running code?"
>>
>> These are all ideas and behavior that we adopted without questioning. We
>> use them in wrong situations generally.
>>
>>
>> Which already exists in many forms of translation mechanisms that we know
>> are not the best way to solve the problem. There are plenty of documents on
>> the Internet that will tell you why.
>>
>
>
> I believe that people should be able to choose their own solutions. Would
> you transition to IPv6 if Discrete IP worked for you? Some entities may,
> others may not, others may do it when they have money, yet others may
> invent and use IPv7. We cannot know.
>
> This means that China may use IPv6, Uruguay may not. We see what people
> decide, we cannot force them. They use translators if they wish. I want to
> develop and test a new IPvX in my university and be reachable to the world,
> who can say no?
>
> Not knowing what is good for others, not knowing the future, helps
> technology develop. It also reduces our suffering because we do not try to
> know the unknowable.
>
>
>
>>
>> We first discuss the idea, then implement.
>>
>> The fact that there is running code doesn't mean that it is a good idea.
>>
>>
>>
>> But if it were, it would help to convince the sceptical like me.
>>
>>
> I don't see why this would convince you.
>
>
>
>>  Also, the fact that there is not running code could mean that the idea
>> is impractical and infeasible.
>>
>>
> No you can implement anything. Even the worst idea.
>
> Pars
>
>
>
>> Cheers,
>> as
>>
>>
>>
>> On Tue, Sep 11, 2012 at 12:22 PM, Arturo Servin <aservin@lacnic.net>wrote:
>>
>>>
>>> On 11 Sep 2012, at 08:20, Pars Mutaf wrote:
>>>
>>> Discrete IP:
>>>
>>> 1. Can be a very good transition mechanism to worldwide IPv6 without
>>> enforcement (meaning that we have no idea what is good for others)
>>>
>>>
>>> Do you have some running code?
>>>
>>> 2. Can solve the IP transition problem forever.
>>>
>>>
>>> Forgive for being sceptical of those all magical technologies that solve
>>> all the problems of the world. Of course, if you had running code that
>>> would change my view.
>>>
>>> Cheers,
>>> as
>>>
>>
>>
>>
>
>

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

By &quot;translation&quot; I mean something completely new. It is written i=
n the paper:<br><br>Splitting the path to two (or more) parts. One part is =
IPv4, the other part is IPv6. <br><br>Source IPv4 &lt;-&gt; Translator IPv4=
<br>
Translator IPv6 &lt;-&gt; Destination IPv6<br><br>We take the data found in=
 the IPv4 packet, we put it in an IPv6 packet (and vice versa).<br><br>By t=
ranslation, I do not mean translating the information found the in the head=
ers. We only copy data. (from IPv4 packet to IPv6 packet and vice versa). S=
ee the paper for illustration (Figure 2).<br>
<br>How TCP works on this, I don&#39;t know yet. I don&#39;t have to know i=
t right now. What is important is &quot;What we want&quot;.<br><br>1. Worry=
 about the core network, i.e. others&#39; IP version preferences forever, o=
r<br>
2. Change the end-node TCP design, if necessary to solve this problem.<br><=
br>Sending a packet from an IPv4 host to an IPv6 host, connected using such=
 a translator, is a routing problem. The problem is that TCP assumes same I=
P version for source and destination. We need another type of identifier, p=
erhaps. Such proposals exist already. But again, what is important here is =
not the solution. What is important is &quot;What we want&quot;. It is one =
of the two possibilities mentioned above. The second one, better respects t=
he end-to-end principle.<br>
<br>Pars<br><br><br><div class=3D"gmail_quote">On Tue, Sep 11, 2012 at 1:38=
 PM, Arturo Servin <span dir=3D"ltr">&lt;<a href=3D"mailto:aservin@lacnic.n=
et" target=3D"_blank">aservin@lacnic.net</a>&gt;</span> wrote:<br><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex">
<div style=3D"word-wrap:break-word"><div><br></div><div><span style=3D"whit=
e-space:pre-wrap">	</span>The big flaw of your idea is that you suppose tha=
t translation magically works, which it is not true due to the complexity o=
f some protocols. That is why I am sceptical.</div>
<div><br></div><div><span style=3D"white-space:pre-wrap">	</span>You are ve=
ry welcome to try your idea. Let me know how it goes.</div><span class=3D"H=
OEnZb"><font color=3D"#888888"><div><br></div><div>/as</div></font></span><=
div>
<div class=3D"h5"><div><span style=3D"white-space:pre-wrap">	</span></div><=
br><div><div>On 11 Sep 2012, at 11:21, Pars Mutaf wrote:</div><br><blockquo=
te type=3D"cite">Hi Arturo,<br><br><div class=3D"gmail_quote">On Tue, Sep 1=
1, 2012 at 1:04 PM, Arturo Servin <span dir=3D"ltr">&lt;<a href=3D"mailto:a=
servin@lacnic.net" target=3D"_blank">aservin@lacnic.net</a>&gt;</span> wrot=
e:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word"><br><div><div><div>On 11 Sep 2012, at 1=
0:55, Pars Mutaf wrote:</div><br><blockquote type=3D"cite"><br>&quot;Do you=
 have some running code?&quot;<br><br>These are all ideas and behavior that=
 we adopted without questioning. We use them in wrong situations generally.=
 <br>

</blockquote><div><br></div></div><div><span style=3D"white-space:pre-wrap"=
>	</span>Which already exists in many forms of translation mechanisms that =
we know are not the best way to solve the problem. There are plenty of docu=
ments on the Internet that will tell you why.</div>

</div></div></blockquote><div><br><br>I believe that people should be able =
to choose their own solutions. Would you transition to IPv6 if Discrete IP =
worked for you? Some entities may, others may not, others may do it when th=
ey have money, yet others may invent and use IPv7. We cannot know. <br>

<br>This means that China may use IPv6, Uruguay may not. We see what people=
 decide, we cannot force them. They use translators if they wish. I want to=
 develop and test a new IPvX in my university and be reachable to the world=
, who can say no?<br>

<br>Not knowing what is good for others, not knowing the future, helps tech=
nology develop. It also reduces our suffering because we do not try to know=
 the unknowable.<br>
<br>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0pt 0pt 0pt =
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style=
=3D"word-wrap:break-word"><div><div><blockquote type=3D"cite"><br>We first =
discuss the idea, then implement.<br>

<br>
The fact that there is running code doesn&#39;t mean that it is a good idea=
.<br></blockquote><div><br></div><div><br></div></div><div><span style=3D"w=
hite-space:pre-wrap">	</span>But if it were, it would help to convince the =
sceptical like me.</div>

<div><br></div></div></div></blockquote><div><br>I don&#39;t see why this w=
ould convince you. <br><br>=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">

<div style=3D"word-wrap:break-word"><div><div></div><div><span style=3D"whi=
te-space:pre-wrap">	</span>Also, the fact that there is not running code co=
uld mean that the idea is impractical and infeasible.</div><div><br></div>
</div>
</div></blockquote><div><br>No you can implement anything. Even the worst i=
dea.<br><br>Pars<br><br>=A0</div><blockquote class=3D"gmail_quote" style=3D=
"margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex">

<div style=3D"word-wrap:break-word"><div><div></div><div>Cheers,</div><div>=
as</div><div><br><blockquote type=3D"cite"><br><br><div class=3D"gmail_quot=
e">On Tue, Sep 11, 2012 at 12:22 PM, Arturo Servin <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:aservin@lacnic.net" target=3D"_blank">aservin@lacnic.net</a=
>&gt;</span> wrote:<br>


<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word"><br><div=
><div><div>On 11 Sep 2012, at 08:20, Pars Mutaf wrote:</div><br><blockquote=
 type=3D"cite">


<span style=3D"border-collapse:separate;font-family:Helvetica;font-style:no=
rmal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-heig=
ht:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white=
-space:normal;word-spacing:0px;font-size:medium">Discrete IP:<br>


<br>1. Can be a very good transition mechanism to worldwide IPv6 without en=
forcement (meaning that we have no idea what is good for others)<br></span>=
</blockquote><div><br></div></div><div><span style=3D"white-space:pre-wrap"=
>	</span>Do you have some running code?</div>


<div><br><blockquote type=3D"cite"><span style=3D"border-collapse:separate;=
font-family:Helvetica;font-style:normal;font-variant:normal;font-weight:nor=
mal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-i=
ndent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size=
:medium">2. Can solve the IP transition problem forever.<span>=A0</span></s=
pan></blockquote>


</div></div><br><div><span style=3D"white-space:pre-wrap">	</span>Forgive f=
or being=A0sceptical of those all magical technologies that solve all the p=
roblems of the world. Of course, if you had running code that would change =
my view.</div>


<div><br></div><div>Cheers,</div><div>as</div></div></blockquote></div><br>
</blockquote></div></div><br></div></blockquote></div><br>
</blockquote></div><br></div></div></div></blockquote></div><br>

--e89a8ff1c5545593ab04c96bc912--

From pars.mutaf@gmail.com  Tue Sep 11 07:31:46 2012
Return-Path: <pars.mutaf@gmail.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A39C21F87FA for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 07:31:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.381
X-Spam-Level: 
X-Spam-Status: No, score=-3.381 tagged_above=-999 required=5 tests=[AWL=0.217,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GbZjx+0AIpUF for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 07:31:45 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id DA58E21F8807 for <int-area@ietf.org>; Tue, 11 Sep 2012 07:31:44 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so998629obb.31 for <int-area@ietf.org>; Tue, 11 Sep 2012 07:31:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Coht6DSUBnCJcin1whox3Jn7448pSb+JnwE+CsZOOaA=; b=t1337wTwT06veWmgSWti4FLUsbgHawcBr01cC/+Y4hVPo02m2u2vV2QqNcyknpONa1 pcOuYI2++sRtAG39cFDtYeOq88VBDb0Jl3xAQ7bGS2vOqJiq3z6sl6CZmLErUHe2t8UW JQHZ51EtigOKozBLQ4SloEftJKQ0+p7xytlaDvZGPMTGd8qJ4OJtVPGTnS5SPwqHoa5C lNHZfRNM3wbOspo3aQxrbLNgbT2sVteyyoRFAb8CutMJQbIA8sFNLhiBNTvwkbRU+2Rs m3vOKwKOUGmOw8BP46shabi8m+IivyJwc7eBGL9aBrFoA2aOSymRcsmpLsQ/8/roaNjI kolQ==
MIME-Version: 1.0
Received: by 10.60.30.201 with SMTP id u9mr18299549oeh.51.1347373904388; Tue, 11 Sep 2012 07:31:44 -0700 (PDT)
Received: by 10.76.28.1 with HTTP; Tue, 11 Sep 2012 07:31:43 -0700 (PDT)
In-Reply-To: <CACQuieZc2s6EdDRJPO1LPBokKh5-jaboNs_M1w4BYqwJ80GK4g@mail.gmail.com>
References: <CACQuieaOfyC5pJ2MyHBRTZYWCYfZMp58Ujh8rn0-yBBQL+kkzg@mail.gmail.com> <FAD8796F-0B15-4197-B952-AEE7FD56EDED@isi.edu> <CACQuiebgTXDmUmaE2n1yAbt4vS+V0M60fjXujqtMrh2n1WhPgQ@mail.gmail.com> <504ECFD9.4090107@isi.edu> <CACQuieZZiotwm9RinsuBAfPt6df21Y_z6JJPg4KNTMND2+E5RA@mail.gmail.com> <987000F4-9B41-4A4F-BF0B-0A207882194B@lacnic.net> <CACQuiea5gMXjkAT_ywA13EO2+HhY0v_OwwB+4_H_nz-Ddd=MEg@mail.gmail.com> <0E3416E0-1F00-42C8-B867-DF8726D9AC26@lacnic.net> <CACQuieYuXPMNCteb_HNvGZrSmx3red7NPFmFbBE8cY9KT8LOQg@mail.gmail.com> <C83D6793-ED56-41ED-9892-2D51F3BA0851@lacnic.net> <CACQuieZc2s6EdDRJPO1LPBokKh5-jaboNs_M1w4BYqwJ80GK4g@mail.gmail.com>
Date: Tue, 11 Sep 2012 17:31:43 +0300
Message-ID: <CACQuieYSs0GP=nyx==x3-u61Ri8DCrcOhDP8e5tBH1xstyyzHQ@mail.gmail.com>
From: Pars Mutaf <pars.mutaf@gmail.com>
To: Arturo Servin <aservin@lacnic.net>
Content-Type: multipart/alternative; boundary=e89a8ff1c584f361e504c96dee4c
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] Discrete IP
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Sep 2012 14:31:46 -0000

--e89a8ff1c584f361e504c96dee4c
Content-Type: text/plain; charset=ISO-8859-1

Hi all,

Instead of IP translator, I use the new term "IP payload copier". It copies
payload between different IP versions. TCP does not work on this because it
assumes same IP version for source and destination.

We probably need a new host identifier, and change TCP to use this
identifier but the IP version transition problem is solved
forever. Everybody use the IP version of their preference. This is the
end-to-end princple, we do not care about the core Internet, we change the
end-hosts.

See details in the paper:

http://www.scribd.com/doc/105448105/Discrete-IP


On Tue, Sep 11, 2012 at 2:58 PM, Pars Mutaf <pars.mutaf@gmail.com> wrote:

> By "translation" I mean something completely new. It is written in the
> paper:
>
> Splitting the path to two (or more) parts. One part is IPv4, the other
> part is IPv6.
>
> Source IPv4 <-> Translator IPv4
> Translator IPv6 <-> Destination IPv6
>
> We take the data found in the IPv4 packet, we put it in an IPv6 packet
> (and vice versa).
>
> By translation, I do not mean translating the information found the in the
> headers. We only copy data. (from IPv4 packet to IPv6 packet and vice
> versa). See the paper for illustration (Figure 2).
>
> How TCP works on this, I don't know yet. I don't have to know it right
> now. What is important is "What we want".
>
> 1. Worry about the core network, i.e. others' IP version preferences
> forever, or
> 2. Change the end-node TCP design, if necessary to solve this problem.
>
> Sending a packet from an IPv4 host to an IPv6 host, connected using such a
> translator, is a routing problem. The problem is that TCP assumes same IP
> version for source and destination. We need another type of identifier,
> perhaps. Such proposals exist already. But again, what is important here is
> not the solution. What is important is "What we want". It is one of the two
> possibilities mentioned above. The second one, better respects the
> end-to-end principle.
>
> Pars
>
>
>
> On Tue, Sep 11, 2012 at 1:38 PM, Arturo Servin <aservin@lacnic.net> wrote:
>
>>
>> The big flaw of your idea is that you suppose that translation magically
>> works, which it is not true due to the complexity of some protocols. That
>> is why I am sceptical.
>>
>> You are very welcome to try your idea. Let me know how it goes.
>>
>> /as
>>
>> On 11 Sep 2012, at 11:21, Pars Mutaf wrote:
>>
>> Hi Arturo,
>>
>> On Tue, Sep 11, 2012 at 1:04 PM, Arturo Servin <aservin@lacnic.net>wrote:
>>
>>>
>>> On 11 Sep 2012, at 10:55, Pars Mutaf wrote:
>>>
>>>
>>> "Do you have some running code?"
>>>
>>> These are all ideas and behavior that we adopted without questioning. We
>>> use them in wrong situations generally.
>>>
>>>
>>> Which already exists in many forms of translation mechanisms that we
>>> know are not the best way to solve the problem. There are plenty of
>>> documents on the Internet that will tell you why.
>>>
>>
>>
>> I believe that people should be able to choose their own solutions. Would
>> you transition to IPv6 if Discrete IP worked for you? Some entities may,
>> others may not, others may do it when they have money, yet others may
>> invent and use IPv7. We cannot know.
>>
>> This means that China may use IPv6, Uruguay may not. We see what people
>> decide, we cannot force them. They use translators if they wish. I want to
>> develop and test a new IPvX in my university and be reachable to the world,
>> who can say no?
>>
>> Not knowing what is good for others, not knowing the future, helps
>> technology develop. It also reduces our suffering because we do not try to
>> know the unknowable.
>>
>>
>>
>>>
>>> We first discuss the idea, then implement.
>>>
>>> The fact that there is running code doesn't mean that it is a good idea.
>>>
>>>
>>>
>>> But if it were, it would help to convince the sceptical like me.
>>>
>>>
>> I don't see why this would convince you.
>>
>>
>>
>>>  Also, the fact that there is not running code could mean that the idea
>>> is impractical and infeasible.
>>>
>>>
>> No you can implement anything. Even the worst idea.
>>
>> Pars
>>
>>
>>
>>> Cheers,
>>> as
>>>
>>>
>>>
>>> On Tue, Sep 11, 2012 at 12:22 PM, Arturo Servin <aservin@lacnic.net>wrote:
>>>
>>>>
>>>> On 11 Sep 2012, at 08:20, Pars Mutaf wrote:
>>>>
>>>> Discrete IP:
>>>>
>>>> 1. Can be a very good transition mechanism to worldwide IPv6 without
>>>> enforcement (meaning that we have no idea what is good for others)
>>>>
>>>>
>>>> Do you have some running code?
>>>>
>>>> 2. Can solve the IP transition problem forever.
>>>>
>>>>
>>>> Forgive for being sceptical of those all magical technologies that
>>>> solve all the problems of the world. Of course, if you had running code
>>>> that would change my view.
>>>>
>>>> Cheers,
>>>> as
>>>>
>>>
>>>
>>>
>>
>>
>

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

<div>Hi all,=A0</div><div><br></div><div>Instead of IP translator, I use th=
e new term &quot;IP payload copier&quot;. It copies payload between differe=
nt IP versions. TCP does not work on this because it assumes same IP versio=
n for source and destination.</div>
<div><br></div><div>We probably need a new host identifier, and change=A0TC=
P to use this identifier but the IP version transition problem is solved fo=
rever.=A0Everybody use the IP version of their preference.=A0This is the en=
d-to-end princple, we do not care about the core Internet, we change the en=
d-hosts.</div>
<div><br></div><div>See details in the paper:</div><div><br></div><a href=
=3D"http://www.scribd.com/doc/105448105/Discrete-IP">http://www.scribd.com/=
doc/105448105/Discrete-IP</a>=A0<br><br><br><div class=3D"gmail_quote">On T=
ue, Sep 11, 2012 at 2:58 PM, Pars Mutaf <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:pars.mutaf@gmail.com" target=3D"_blank">pars.mutaf@gmail.com</a>&gt;</=
span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">By &quot;translation&quot; I mean something =
completely new. It is written in the paper:<br><br>Splitting the path to tw=
o (or more) parts. One part is IPv4, the other part is IPv6. <br>
<br>Source IPv4 &lt;-&gt; Translator IPv4<br>
Translator IPv6 &lt;-&gt; Destination IPv6<br><br>We take the data found in=
 the IPv4 packet, we put it in an IPv6 packet (and vice versa).<br><br>By t=
ranslation, I do not mean translating the information found the in the head=
ers. We only copy data. (from IPv4 packet to IPv6 packet and vice versa). S=
ee the paper for illustration (Figure 2).<br>

<br>How TCP works on this, I don&#39;t know yet. I don&#39;t have to know i=
t right now. What is important is &quot;What we want&quot;.<br><br>1. Worry=
 about the core network, i.e. others&#39; IP version preferences forever, o=
r<br>

2. Change the end-node TCP design, if necessary to solve this problem.<br><=
br>Sending a packet from an IPv4 host to an IPv6 host, connected using such=
 a translator, is a routing problem. The problem is that TCP assumes same I=
P version for source and destination. We need another type of identifier, p=
erhaps. Such proposals exist already. But again, what is important here is =
not the solution. What is important is &quot;What we want&quot;. It is one =
of the two possibilities mentioned above. The second one, better respects t=
he end-to-end principle.<span class=3D"HOEnZb"><font color=3D"#888888"><br>

<br>Pars</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br><br><br><=
div class=3D"gmail_quote">On Tue, Sep 11, 2012 at 1:38 PM, Arturo Servin <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:aservin@lacnic.net" target=3D"_blank"=
>aservin@lacnic.net</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word"><div><br></div><div><span style=3D"whit=
e-space:pre-wrap">	</span>The big flaw of your idea is that you suppose tha=
t translation magically works, which it is not true due to the complexity o=
f some protocols. That is why I am sceptical.</div>

<div><br></div><div><span style=3D"white-space:pre-wrap">	</span>You are ve=
ry welcome to try your idea. Let me know how it goes.</div><span><font colo=
r=3D"#888888"><div><br></div><div>/as</div></font></span><div>
<div><div><span style=3D"white-space:pre-wrap">	</span></div><br><div><div>=
On 11 Sep 2012, at 11:21, Pars Mutaf wrote:</div><br><blockquote type=3D"ci=
te">Hi Arturo,<br><br><div class=3D"gmail_quote">On Tue, Sep 11, 2012 at 1:=
04 PM, Arturo Servin <span dir=3D"ltr">&lt;<a href=3D"mailto:aservin@lacnic=
.net" target=3D"_blank">aservin@lacnic.net</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word"><br><div><div><div>On 11 Sep 2012, at 1=
0:55, Pars Mutaf wrote:</div><br><blockquote type=3D"cite"><br>&quot;Do you=
 have some running code?&quot;<br><br>These are all ideas and behavior that=
 we adopted without questioning. We use them in wrong situations generally.=
 <br>


</blockquote><div><br></div></div><div><span style=3D"white-space:pre-wrap"=
>	</span>Which already exists in many forms of translation mechanisms that =
we know are not the best way to solve the problem. There are plenty of docu=
ments on the Internet that will tell you why.</div>


</div></div></blockquote><div><br><br>I believe that people should be able =
to choose their own solutions. Would you transition to IPv6 if Discrete IP =
worked for you? Some entities may, others may not, others may do it when th=
ey have money, yet others may invent and use IPv7. We cannot know. <br>


<br>This means that China may use IPv6, Uruguay may not. We see what people=
 decide, we cannot force them. They use translators if they wish. I want to=
 develop and test a new IPvX in my university and be reachable to the world=
, who can say no?<br>


<br>Not knowing what is good for others, not knowing the future, helps tech=
nology develop. It also reduces our suffering because we do not try to know=
 the unknowable.<br>
<br>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0pt 0pt 0pt =
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style=
=3D"word-wrap:break-word"><div><div><blockquote type=3D"cite"><br>We first =
discuss the idea, then implement.<br>


<br>
The fact that there is running code doesn&#39;t mean that it is a good idea=
.<br></blockquote><div><br></div><div><br></div></div><div><span style=3D"w=
hite-space:pre-wrap">	</span>But if it were, it would help to convince the =
sceptical like me.</div>


<div><br></div></div></div></blockquote><div><br>I don&#39;t see why this w=
ould convince you. <br><br>=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">


<div style=3D"word-wrap:break-word"><div><div></div><div><span style=3D"whi=
te-space:pre-wrap">	</span>Also, the fact that there is not running code co=
uld mean that the idea is impractical and infeasible.</div><div><br></div>

</div>
</div></blockquote><div><br>No you can implement anything. Even the worst i=
dea.<br><br>Pars<br><br>=A0</div><blockquote class=3D"gmail_quote" style=3D=
"margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex">


<div style=3D"word-wrap:break-word"><div><div></div><div>Cheers,</div><div>=
as</div><div><br><blockquote type=3D"cite"><br><br><div class=3D"gmail_quot=
e">On Tue, Sep 11, 2012 at 12:22 PM, Arturo Servin <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:aservin@lacnic.net" target=3D"_blank">aservin@lacnic.net</a=
>&gt;</span> wrote:<br>



<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word"><br><div=
><div><div>On 11 Sep 2012, at 08:20, Pars Mutaf wrote:</div><br><blockquote=
 type=3D"cite">



<span style=3D"border-collapse:separate;font-family:Helvetica;font-style:no=
rmal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-heig=
ht:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white=
-space:normal;word-spacing:0px;font-size:medium">Discrete IP:<br>



<br>1. Can be a very good transition mechanism to worldwide IPv6 without en=
forcement (meaning that we have no idea what is good for others)<br></span>=
</blockquote><div><br></div></div><div><span style=3D"white-space:pre-wrap"=
>	</span>Do you have some running code?</div>



<div><br><blockquote type=3D"cite"><span style=3D"border-collapse:separate;=
font-family:Helvetica;font-style:normal;font-variant:normal;font-weight:nor=
mal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-i=
ndent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size=
:medium">2. Can solve the IP transition problem forever.<span>=A0</span></s=
pan></blockquote>



</div></div><br><div><span style=3D"white-space:pre-wrap">	</span>Forgive f=
or being=A0sceptical of those all magical technologies that solve all the p=
roblems of the world. Of course, if you had running code that would change =
my view.</div>



<div><br></div><div>Cheers,</div><div>as</div></div></blockquote></div><br>
</blockquote></div></div><br></div></blockquote></div><br>
</blockquote></div><br></div></div></div></blockquote></div><br>
</div></div></blockquote></div><br>

--e89a8ff1c584f361e504c96dee4c--

From fred@cisco.com  Tue Sep 11 09:38:51 2012
Return-Path: <fred@cisco.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AD3E21F849A for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 09:38:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8nHFn++H3okU for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 09:38:51 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id E10AF21F84C5 for <int-area@ietf.org>; Tue, 11 Sep 2012 09:38:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1066; q=dns/txt; s=iport; t=1347381531; x=1348591131; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=TS2wJDVpBn2ZxacPz5Dd4xfhMQmBcIa0jR2DCqqwXWI=; b=XbSCD3i8gZdH6e+6Foqa+cabbayhDD1PsQClEzdXi5CxQ94ZH0RtlVmL QBc53EkMdsaU3VfAEs1FQK0P+hg/1CrEgNY6gYBuSMCEP10G3UdhT1Y+y ODexJrDrLj33kTrS3D3ecQxaKpfOxwAKQkxEcqE1in2stfwStx4ogR78s g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAN1oT1CtJXG9/2dsb2JhbABFu1KBB4IgAQEBAwESASc/EAIBCDYQMiUCBA4nh2gGmyugUYsQhUZgA5VfjjaBZ4Jm
X-IronPort-AV: E=Sophos;i="4.80,406,1344211200"; d="scan'208";a="120434192"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-2.cisco.com with ESMTP; 11 Sep 2012 16:38:50 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id q8BGcoh3024365 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 11 Sep 2012 16:38:50 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.97]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.02.0298.004; Tue, 11 Sep 2012 11:38:50 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Thread-Topic: [Int-area] draft-bonica-v6-multihome
Thread-Index: AQHNirjgL6qzht3KxUCQUn0/l9X2RpeEoVuAgAB07oCAAAQ5AIAAJdGAgAB14AA=
Date: Tue, 11 Sep 2012 16:38:49 +0000
Message-ID: <E343B94A-E574-4C6D-B849-754C9A0D1B5C@cisco.com>
References: <504629B7.7080703@gmail.com> <37F823E3-F6AB-4A5D-A925-E4B8691FFFF6@cisco.com> <504EE2F1.4060208@gmail.com> <4619D3A0-E6E0-455C-8825-33CD6BFD2BBC@cisco.com> <504F0635.7050301@gmail.com>
In-Reply-To: <504F0635.7050301@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.32.244.221]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19176.006
x-tm-as-result: No--27.742100-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-ID: <B835834C05E01A419BFB2606AA575D36@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<draft-bonica-v6-multihome@tools.ietf.org>" <draft-bonica-v6-multihome@tools.ietf.org>, Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] draft-bonica-v6-multihome
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Sep 2012 16:38:51 -0000

On Sep 11, 2012, at 2:36 AM, Brian E Carpenter wrote:

>> What's that rule called? TAANSTAAFL, as I recall. Pretending won't make =
it otherwise. Either the service providers deal with the complexities of th=
e IPv4 route table, or the edge networks deal with the complexities of mana=
ging prefixes from each of multiple upstream PA prefixes, or DNS advertises=
 inside and outside addresses somehow. Pick one.=20
>=20
> This being the Internet, I expect we'll pick several. But indeed, we have
> to deal with current reality and also try to influence long term trends
> in a desirable way. I think that getting the problem area well described
> is the first step.

I'll suggest that you and I collaborate on a note describing the issue, and=
 why having applications know anything about network layer addresses in the=
 first place is unwise. Sometimes necessary, perhaps, but implies the desig=
n decision to make this issue hard for that application, and to be avoided =
or mitigated when possible. We can refer to RFC 3439's section 2.2.2.=

From pars.mutaf@gmail.com  Tue Sep 11 09:44:47 2012
Return-Path: <pars.mutaf@gmail.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9287621F86EF for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 09:44:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.412
X-Spam-Level: 
X-Spam-Status: No, score=-3.412 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nOVcYFzpjX-Q for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 09:44:46 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 403C121F86A8 for <int-area@ietf.org>; Tue, 11 Sep 2012 09:44:46 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so1050354vcb.31 for <int-area@ietf.org>; Tue, 11 Sep 2012 09:44:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=GdZcKpdUys5CCj3idkV8q4Ws6W742hFZiDQYDcJZKFc=; b=N3BK1rvIAJJCur0WP5RV3+/A3Z046ly4xgHwRdJpGwWH2kuUBDmMjuhd2pw4nMIhcx pUiFQgnpihUMZeMDO/9XOlLv0osZYYJ501Qufm+btezcrhdbMHlWgNL6JWrE99xdcTLE 4tnnmIuGtjukRZWyIBA9RaKAEaor+QaGXClRk3d72bwV7e/j0wqAP3STgxcbu0abM9ml vjxyzdnLIF3wLDoO0uHGuYKv1cT+eC1JYZ1ae8A96CS+8y1BSY5Tyj4C0872HdiyQQyM mCi50A2Em7aGJthSARBFzZQsYHYZp9HgzGKSXObgeYvZr3QAu4uVq6DkFiaJM2JjZI38 vpgQ==
MIME-Version: 1.0
Received: by 10.52.22.40 with SMTP id a8mr21185021vdf.4.1347381885472; Tue, 11 Sep 2012 09:44:45 -0700 (PDT)
Received: by 10.58.213.101 with HTTP; Tue, 11 Sep 2012 09:44:45 -0700 (PDT)
In-Reply-To: <AC4D2CAF-C76C-4AFD-98AC-7A7D512378BA@kumari.net>
References: <CACQuieaOfyC5pJ2MyHBRTZYWCYfZMp58Ujh8rn0-yBBQL+kkzg@mail.gmail.com> <FAD8796F-0B15-4197-B952-AEE7FD56EDED@isi.edu> <CACQuiebgTXDmUmaE2n1yAbt4vS+V0M60fjXujqtMrh2n1WhPgQ@mail.gmail.com> <504ECFD9.4090107@isi.edu> <CACQuieZZiotwm9RinsuBAfPt6df21Y_z6JJPg4KNTMND2+E5RA@mail.gmail.com> <987000F4-9B41-4A4F-BF0B-0A207882194B@lacnic.net> <CACQuiea5gMXjkAT_ywA13EO2+HhY0v_OwwB+4_H_nz-Ddd=MEg@mail.gmail.com> <0E3416E0-1F00-42C8-B867-DF8726D9AC26@lacnic.net> <CACQuieYuXPMNCteb_HNvGZrSmx3red7NPFmFbBE8cY9KT8LOQg@mail.gmail.com> <C83D6793-ED56-41ED-9892-2D51F3BA0851@lacnic.net> <CACQuieZc2s6EdDRJPO1LPBokKh5-jaboNs_M1w4BYqwJ80GK4g@mail.gmail.com> <CACQuieYSs0GP=nyx==x3-u61Ri8DCrcOhDP8e5tBH1xstyyzHQ@mail.gmail.com> <AC4D2CAF-C76C-4AFD-98AC-7A7D512378BA@kumari.net>
Date: Tue, 11 Sep 2012 19:44:45 +0300
Message-ID: <CACQuieaTufrR=emTP3PgvDv9qYV7WWiKTKyrjBfjWx-ykbp=3A@mail.gmail.com>
From: Pars Mutaf <pars.mutaf@gmail.com>
To: Warren Kumari <warren@kumari.net>
Content-Type: multipart/alternative; boundary=20cf30776473a90e4004c96fcab2
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] Discrete IP
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Sep 2012 16:44:47 -0000

--20cf30776473a90e4004c96fcab2
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On Tue, Sep 11, 2012 at 5:38 PM, Warren Kumari <warren@kumari.net> wrote:

>
> On Sep 11, 2012, at 10:31 AM, Pars Mutaf wrote:
>
> > Hi all,
> >
> > Instead of IP translator, I use the new term "IP payload copier". It
> copies payload between different IP versions.
>
> Right=85 And who runs these? And who pays for them? And how many do you
> need? And how do you scale them? And how does discovery work? And how are
> they different to current NAT64 type things?
>
> W
>
>


They are like other routing devices. ISPs pay.

NAT64 works by translating the headers if I am not wrong (I just checked).
IP payload copiers that I propose, copy payload from one version to
another.

We need 1 or 2 between this Internet and China's IPv6 Internet. Then
another one, etc. As I see they are not different from backbone routers.

The real question is not how it works, for the moment. The real question
is: What do we want:

1. Worry about the whole core Internet, others' IP version choices? (a
question that has no end no answer), or
2. Change the end nodes.



Pars






>
>
> > TCP does not work on this because it assumes same IP version for source
> and destination.
> >
> > We probably need a new host identifier, and change TCP to use this
> identifier but the IP version transition problem is solved forever.
> Everybody use the IP version of their preference. This is the end-to-end
> princple, we do not care about the core Internet, we change the end-hosts=
.
> >
> > See details in the paper:
> >
> > http://www.scribd.com/doc/105448105/Discrete-IP
> >
> >
> > On Tue, Sep 11, 2012 at 2:58 PM, Pars Mutaf <pars.mutaf@gmail.com>
> wrote:
> > By "translation" I mean something completely new. It is written in the
> paper:
> >
> > Splitting the path to two (or more) parts. One part is IPv4, the other
> part is IPv6.
> >
> > Source IPv4 <-> Translator IPv4
> > Translator IPv6 <-> Destination IPv6
> >
> > We take the data found in the IPv4 packet, we put it in an IPv6 packet
> (and vice versa).
> >
> > By translation, I do not mean translating the information found the in
> the headers. We only copy data. (from IPv4 packet to IPv6 packet and vice
> versa). See the paper for illustration (Figure 2).
> >
> > How TCP works on this, I don't know yet. I don't have to know it right
> now. What is important is "What we want".
> >
> > 1. Worry about the core network, i.e. others' IP version preferences
> forever, or
> > 2. Change the end-node TCP design, if necessary to solve this problem.
> >
> > Sending a packet from an IPv4 host to an IPv6 host, connected using suc=
h
> a translator, is a routing problem. The problem is that TCP assumes same =
IP
> version for source and destination. We need another type of identifier,
> perhaps. Such proposals exist already. But again, what is important here =
is
> not the solution. What is important is "What we want". It is one of the t=
wo
> possibilities mentioned above. The second one, better respects the
> end-to-end principle.
> >
> > Pars
> >
> >
> >
> > On Tue, Sep 11, 2012 at 1:38 PM, Arturo Servin <aservin@lacnic.net>
> wrote:
> >
> >       The big flaw of your idea is that you suppose that translation
> magically works, which it is not true due to the complexity of some
> protocols. That is why I am sceptical.
> >
> >       You are very welcome to try your idea. Let me know how it goes.
> >
> > /as
> >
> >
> > On 11 Sep 2012, at 11:21, Pars Mutaf wrote:
> >
> >> Hi Arturo,
> >>
> >> On Tue, Sep 11, 2012 at 1:04 PM, Arturo Servin <aservin@lacnic.net>
> wrote:
> >>
> >> On 11 Sep 2012, at 10:55, Pars Mutaf wrote:
> >>
> >>>
> >>> "Do you have some running code?"
> >>>
> >>> These are all ideas and behavior that we adopted without questioning.
> We use them in wrong situations generally.
> >>
> >>      Which already exists in many forms of translation mechanisms that
> we know are not the best way to solve the problem. There are plenty of
> documents on the Internet that will tell you why.
> >>
> >>
> >> I believe that people should be able to choose their own solutions.
> Would you transition to IPv6 if Discrete IP worked for you? Some entities
> may, others may not, others may do it when they have money, yet others ma=
y
> invent and use IPv7. We cannot know.
> >>
> >> This means that China may use IPv6, Uruguay may not. We see what peopl=
e
> decide, we cannot force them. They use translators if they wish. I want t=
o
> develop and test a new IPvX in my university and be reachable to the worl=
d,
> who can say no?
> >>
> >> Not knowing what is good for others, not knowing the future, helps
> technology develop. It also reduces our suffering because we do not try t=
o
> know the unknowable.
> >>
> >>
> >>>
> >>> We first discuss the idea, then implement.
> >>>
> >>> The fact that there is running code doesn't mean that it is a good
> idea.
> >>
> >>
> >>      But if it were, it would help to convince the sceptical like me.
> >>
> >>
> >> I don't see why this would convince you.
> >>
> >>
> >>      Also, the fact that there is not running code could mean that the
> idea is impractical and infeasible.
> >>
> >>
> >> No you can implement anything. Even the worst idea.
> >>
> >> Pars
> >>
> >>
> >> Cheers,
> >> as
> >>
> >>>
> >>>
> >>> On Tue, Sep 11, 2012 at 12:22 PM, Arturo Servin <aservin@lacnic.net>
> wrote:
> >>>
> >>> On 11 Sep 2012, at 08:20, Pars Mutaf wrote:
> >>>
> >>>> Discrete IP:
> >>>>
> >>>> 1. Can be a very good transition mechanism to worldwide IPv6 without
> enforcement (meaning that we have no idea what is good for others)
> >>>
> >>>     Do you have some running code?
> >>>
> >>>> 2. Can solve the IP transition problem forever.
> >>>
> >>>     Forgive for being sceptical of those all magical technologies tha=
t
> solve all the problems of the world. Of course, if you had running code
> that would change my view.
> >>>
> >>> Cheers,
> >>> as
> >>>
> >>
> >>
> >
> >
> >
> > _______________________________________________
> > Int-area mailing list
> > Int-area@ietf.org
> > https://www.ietf.org/mailman/listinfo/int-area
>
> --
> After you'd known Christine for any length of time, you found yourself
> fighting a desire to look into her ear to see if you could spot daylight
> coming the other way.
>
>     -- (Terry Pratchett, Maskerade)
>
>
>
>
>

--20cf30776473a90e4004c96fcab2
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<br><br>
<div class=3D"gmail_quote">On Tue, Sep 11, 2012 at 5:38 PM, Warren Kumari <=
span dir=3D"ltr">&lt;<a href=3D"mailto:warren@kumari.net" target=3D"_blank"=
>warren@kumari.net</a>&gt;</span> wrote:<br>
<blockquote style=3D"BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PA=
DDING-LEFT:1ex" class=3D"gmail_quote">
<div><br>On Sep 11, 2012, at 10:31 AM, Pars Mutaf wrote:<br><br>&gt; Hi all=
,<br>&gt;<br>&gt; Instead of IP translator, I use the new term &quot;IP pay=
load copier&quot;. It copies payload between different IP versions.<br>
<br></div>Right=85 And who runs these? And who pays for them? And how many =
do you need? And how do you scale them? And how does discovery work? And ho=
w are they different to current NAT64 type things?<br><br>W<br>
<div>
<div><br></div></div></blockquote>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>They are like other routing devices. ISPs pay. </div>
<div>=A0</div>
<div>NAT64 works by translating the headers if I am not wrong (I just check=
ed). IP payload copiers that I propose, copy payload from one version to an=
other. </div>
<div>=A0</div>
<div>We need 1 or 2 between this Internet and China&#39;s IPv6 Internet. Th=
en another one, etc. As I see they are not different from backbone routers.=
</div>
<div>=A0</div>
<div>The real question is not how it works, for the moment. The real questi=
on is: What do we want: </div>
<div>=A0</div>
<div>1. Worry about the whole core Internet, others&#39; IP version choices=
? (a question that has no end no answer), or</div>
<div>2. Change the end nodes.</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>Pars</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<div>=A0</div>
<blockquote style=3D"BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PA=
DDING-LEFT:1ex" class=3D"gmail_quote">
<div>
<div><br><br>&gt; TCP does not work on this because it assumes same IP vers=
ion for source and destination.<br>&gt;<br>&gt; We probably need a new host=
 identifier, and change TCP to use this identifier but the IP version trans=
ition problem is solved forever. Everybody use the IP version of their pref=
erence. This is the end-to-end princple, we do not care about the core Inte=
rnet, we change the end-hosts.<br>
&gt;<br>&gt; See details in the paper:<br>&gt;<br>&gt; <a href=3D"http://ww=
w.scribd.com/doc/105448105/Discrete-IP" target=3D"_blank">http://www.scribd=
.com/doc/105448105/Discrete-IP</a><br>&gt;<br>&gt;<br>&gt; On Tue, Sep 11, =
2012 at 2:58 PM, Pars Mutaf &lt;<a href=3D"mailto:pars.mutaf@gmail.com" tar=
get=3D"_blank">pars.mutaf@gmail.com</a>&gt; wrote:<br>
&gt; By &quot;translation&quot; I mean something completely new. It is writ=
ten in the paper:<br>&gt;<br>&gt; Splitting the path to two (or more) parts=
. One part is IPv4, the other part is IPv6.<br>&gt;<br>&gt; Source IPv4 &lt=
;-&gt; Translator IPv4<br>
&gt; Translator IPv6 &lt;-&gt; Destination IPv6<br>&gt;<br>&gt; We take the=
 data found in the IPv4 packet, we put it in an IPv6 packet (and vice versa=
).<br>&gt;<br>&gt; By translation, I do not mean translating the informatio=
n found the in the headers. We only copy data. (from IPv4 packet to IPv6 pa=
cket and vice versa). See the paper for illustration (Figure 2).<br>
&gt;<br>&gt; How TCP works on this, I don&#39;t know yet. I don&#39;t have =
to know it right now. What is important is &quot;What we want&quot;.<br>&gt=
;<br>&gt; 1. Worry about the core network, i.e. others&#39; IP version pref=
erences forever, or<br>
&gt; 2. Change the end-node TCP design, if necessary to solve this problem.=
<br>&gt;<br>&gt; Sending a packet from an IPv4 host to an IPv6 host, connec=
ted using such a translator, is a routing problem. The problem is that TCP =
assumes same IP version for source and destination. We need another type of=
 identifier, perhaps. Such proposals exist already. But again, what is impo=
rtant here is not the solution. What is important is &quot;What we want&quo=
t;. It is one of the two possibilities mentioned above. The second one, bet=
ter respects the end-to-end principle.<br>
&gt;<br>&gt; Pars<br>&gt;<br>&gt;<br>&gt;<br>&gt; On Tue, Sep 11, 2012 at 1=
:38 PM, Arturo Servin &lt;<a href=3D"mailto:aservin@lacnic.net" target=3D"_=
blank">aservin@lacnic.net</a>&gt; wrote:<br>&gt;<br>&gt; =A0 =A0 =A0 The bi=
g flaw of your idea is that you suppose that translation magically works, w=
hich it is not true due to the complexity of some protocols. That is why I =
am sceptical.<br>
&gt;<br>&gt; =A0 =A0 =A0 You are very welcome to try your idea. Let me know=
 how it goes.<br>&gt;<br>&gt; /as<br>&gt;<br>&gt;<br>&gt; On 11 Sep 2012, a=
t 11:21, Pars Mutaf wrote:<br>&gt;<br>&gt;&gt; Hi Arturo,<br>&gt;&gt;<br>&g=
t;&gt; On Tue, Sep 11, 2012 at 1:04 PM, Arturo Servin &lt;<a href=3D"mailto=
:aservin@lacnic.net" target=3D"_blank">aservin@lacnic.net</a>&gt; wrote:<br=
>
&gt;&gt;<br>&gt;&gt; On 11 Sep 2012, at 10:55, Pars Mutaf wrote:<br>&gt;&gt=
;<br>&gt;&gt;&gt;<br>&gt;&gt;&gt; &quot;Do you have some running code?&quot=
;<br>&gt;&gt;&gt;<br>&gt;&gt;&gt; These are all ideas and behavior that we =
adopted without questioning. We use them in wrong situations generally.<br>
&gt;&gt;<br>&gt;&gt; =A0 =A0 =A0Which already exists in many forms of trans=
lation mechanisms that we know are not the best way to solve the problem. T=
here are plenty of documents on the Internet that will tell you why.<br>&gt=
;&gt;<br>
&gt;&gt;<br>&gt;&gt; I believe that people should be able to choose their o=
wn solutions. Would you transition to IPv6 if Discrete IP worked for you? S=
ome entities may, others may not, others may do it when they have money, ye=
t others may invent and use IPv7. We cannot know.<br>
&gt;&gt;<br>&gt;&gt; This means that China may use IPv6, Uruguay may not. W=
e see what people decide, we cannot force them. They use translators if the=
y wish. I want to develop and test a new IPvX in my university and be reach=
able to the world, who can say no?<br>
&gt;&gt;<br>&gt;&gt; Not knowing what is good for others, not knowing the f=
uture, helps technology develop. It also reduces our suffering because we d=
o not try to know the unknowable.<br>&gt;&gt;<br>&gt;&gt;<br>&gt;&gt;&gt;<b=
r>
&gt;&gt;&gt; We first discuss the idea, then implement.<br>&gt;&gt;&gt;<br>=
&gt;&gt;&gt; The fact that there is running code doesn&#39;t mean that it i=
s a good idea.<br>&gt;&gt;<br>&gt;&gt;<br>&gt;&gt; =A0 =A0 =A0But if it wer=
e, it would help to convince the sceptical like me.<br>
&gt;&gt;<br>&gt;&gt;<br>&gt;&gt; I don&#39;t see why this would convince yo=
u.<br>&gt;&gt;<br>&gt;&gt;<br>&gt;&gt; =A0 =A0 =A0Also, the fact that there=
 is not running code could mean that the idea is impractical and infeasible=
.<br>
&gt;&gt;<br>&gt;&gt;<br>&gt;&gt; No you can implement anything. Even the wo=
rst idea.<br>&gt;&gt;<br>&gt;&gt; Pars<br>&gt;&gt;<br>&gt;&gt;<br>&gt;&gt; =
Cheers,<br>&gt;&gt; as<br>&gt;&gt;<br>&gt;&gt;&gt;<br>&gt;&gt;&gt;<br>&gt;&=
gt;&gt; On Tue, Sep 11, 2012 at 12:22 PM, Arturo Servin &lt;<a href=3D"mail=
to:aservin@lacnic.net" target=3D"_blank">aservin@lacnic.net</a>&gt; wrote:<=
br>
&gt;&gt;&gt;<br>&gt;&gt;&gt; On 11 Sep 2012, at 08:20, Pars Mutaf wrote:<br=
>&gt;&gt;&gt;<br>&gt;&gt;&gt;&gt; Discrete IP:<br>&gt;&gt;&gt;&gt;<br>&gt;&=
gt;&gt;&gt; 1. Can be a very good transition mechanism to worldwide IPv6 wi=
thout enforcement (meaning that we have no idea what is good for others)<br=
>
&gt;&gt;&gt;<br>&gt;&gt;&gt; =A0 =A0 Do you have some running code?<br>&gt;=
&gt;&gt;<br>&gt;&gt;&gt;&gt; 2. Can solve the IP transition problem forever=
.<br>&gt;&gt;&gt;<br>&gt;&gt;&gt; =A0 =A0 Forgive for being sceptical of th=
ose all magical technologies that solve all the problems of the world. Of c=
ourse, if you had running code that would change my view.<br>
&gt;&gt;&gt;<br>&gt;&gt;&gt; Cheers,<br>&gt;&gt;&gt; as<br>&gt;&gt;&gt;<br>=
&gt;&gt;<br>&gt;&gt;<br>&gt;<br>&gt;<br>&gt;<br></div></div>
<div>&gt; _______________________________________________<br>&gt; Int-area =
mailing list<br>&gt; <a href=3D"mailto:Int-area@ietf.org" target=3D"_blank"=
>Int-area@ietf.org</a><br>&gt; <a href=3D"https://www.ietf.org/mailman/list=
info/int-area" target=3D"_blank">https://www.ietf.org/mailman/listinfo/int-=
area</a><br>
<br></div>--<br>After you&#39;d known Christine for any length of time, you=
 found yourself fighting a desire to look into her ear to see if you could =
spot daylight coming the other way.<br><br>=A0 =A0 -- (Terry Pratchett, Mas=
kerade)<br>
<br><br><br><br></blockquote></div><br>

--20cf30776473a90e4004c96fcab2--

From touch@isi.edu  Tue Sep 11 12:07:43 2012
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B649221F851C for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 12:07:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.202
X-Spam-Level: 
X-Spam-Status: No, score=-101.202 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ugUig5yJpukO for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 12:07:41 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 4547921F8535 for <int-area@ietf.org>; Tue, 11 Sep 2012 12:07:41 -0700 (PDT)
Received: from [59.10.124.171] ([59.10.124.171]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id q8BJ74kJ008732 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 11 Sep 2012 12:07:15 -0700 (PDT)
References: <CACQuieaOfyC5pJ2MyHBRTZYWCYfZMp58Ujh8rn0-yBBQL+kkzg@mail.gmail.com> <FAD8796F-0B15-4197-B952-AEE7FD56EDED@isi.edu> <CACQuiebgTXDmUmaE2n1yAbt4vS+V0M60fjXujqtMrh2n1WhPgQ@mail.gmail.com> <504ECFD9.4090107@isi.edu> <CACQuieZZiotwm9RinsuBAfPt6df21Y_z6JJPg4KNTMND2+E5RA@mail.gmail.com> <987000F4-9B41-4A4F-BF0B-0A207882194B@lacnic.net> <CACQuiea5gMXjkAT_ywA13EO2+HhY0v_OwwB+4_H_nz-Ddd=MEg@mail.gmail.com> <0E3416E0-1F00-42C8-B867-DF8726D9AC26@lacnic.net> <CACQuieYuXPMNCteb_HNvGZrSmx3red7NPFmFbBE8cY9KT8LOQg@mail.gmail.com> <C83D6793-ED56-41ED-9892-2D51F3BA0851@lacnic.net> <CACQuieZc2s6EdDRJPO1LPBokKh5-jaboNs_M1w4BYqwJ80GK4g@mail.gmail.com> <CACQuieYSs0GP=nyx==x3-u61Ri8DCrcOhDP8e5tBH1xstyyzHQ@mail.gmail.com>
In-Reply-To: <CACQuieYSs0GP=nyx==x3-u61Ri8DCrcOhDP8e5tBH1xstyyzHQ@mail.gmail.com>
Mime-Version: 1.0 (1.0)
Content-Type: multipart/alternative; boundary=Apple-Mail-047C39DE-325D-4B2F-9598-D940A18E77F6
Message-Id: <56839629-0B52-4DCC-B2C3-682AFC40D231@isi.edu>
Content-Transfer-Encoding: 7bit
X-Mailer: iPad Mail (9B206)
From: Joe Touch <touch@isi.edu>
Date: Wed, 12 Sep 2012 04:07:04 +0900
To: Pars Mutaf <pars.mutaf@gmail.com>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] Discrete IP
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Sep 2012 19:07:43 -0000

--Apple-Mail-047C39DE-325D-4B2F-9598-D940A18E77F6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii



On Sep 11, 2012, at 11:31 PM, Pars Mutaf <pars.mutaf@gmail.com> wrote:

> Hi all,=20
>=20
> Instead of IP translator, I use the new term "IP payload copier". It copie=
s payload between different IP versions. TCP does not work on this because i=
t assumes same IP version for source and destination.
>=20
> We probably need a new host identifier,

And that is IPv6 right now.

Call us when you fix that. and maybe also look at realm-specific IP.

> and change TCP to use this identifier but the IP version transition proble=
m is solved forever. Everybody use the IP version of their preference. This i=
s the end-to-end princple, we do not care about the core Internet, we change=
 the end-hosts.
>=20
> See details in the paper:
>=20
> http://www.scribd.com/doc/105448105/Discrete-IP=20

There are no details.

E.g., let's say I'm ipv4 and want to talk to you who are ipv6 right now. So I=
 go to the DNS and ask for you.  First, you have to assume a global namespac=
e above IP - the DNS name - the identifies endpoints.  Second, what will you=
 give me? I don't understand an ipv6 address.  So you hand me the ipv4 of th=
e translator? Then if I send a packet there, it won't know who to send it on=
ward to.

You have a paper, but it is lacking in exactly the solutions everyone has be=
en trying to find for years, and some have shown don't or can't exist.

So I agree with some others that if you insist a solution can exist, you nee=
d to demonstrate that with code..that is how the IETF works when the communi=
ty is skeptical of your approach, which is the case here.

Joe=

--Apple-Mail-047C39DE-325D-4B2F-9598-D940A18E77F6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head></head><body bgcolor=3D"#FFFFFF"><div><br><br>On Sep 11, 2012, a=
t 11:31 PM, Pars Mutaf &lt;<a href=3D"mailto:pars.mutaf@gmail.com">pars.muta=
f@gmail.com</a>&gt; wrote:<br><br></div><div></div><blockquote type=3D"cite"=
><div><div>Hi all,&nbsp;</div><div><br></div><div>Instead of IP translator, I=
 use the new term "IP payload copier". It copies payload between different I=
P versions. TCP does not work on this because it assumes same IP version for=
 source and destination.</div>
<div><br></div><div>We probably need a new host identifier, </div></div></bl=
ockquote><div><br></div>And that is IPv6 right now.<br><div><br></div><div>C=
all us when you fix that. and maybe also look at realm-specific IP.</div><br=
><blockquote type=3D"cite"><div><div>and change&nbsp;TCP to use this identif=
ier but the IP version transition problem is solved forever.&nbsp;Everybody u=
se the IP version of their preference.&nbsp;This is the end-to-end princple,=
 we do not care about the core Internet, we change the end-hosts.</div>
<div><br></div><div>See details in the paper:</div><div><br></div><a href=3D=
"http://www.scribd.com/doc/105448105/Discrete-IP">http://www.scribd.com/doc/=
105448105/Discrete-IP</a>&nbsp;<br></div></blockquote><div><br></div><div>Th=
ere are no details.</div><div><br></div><div>E.g., let's say I'm ipv4 and wa=
nt to talk to you who are ipv6 right now. So I go to the DNS and ask for you=
. &nbsp;First, you have to assume a global namespace above IP - the DNS name=
 - the identifies endpoints. &nbsp;Second, what will you give me? I don't un=
derstand an ipv6 address. &nbsp;So you hand me the ipv4 of the translator? T=
hen if I send a packet there, it won't know who to send it onward to.</div><=
div><br></div><div>You have a paper, but it is lacking in exactly the soluti=
ons everyone has been trying to find for years, and some have shown don't or=
 can't exist.</div><div><br></div><div>So I agree with some others that if y=
ou insist a solution can exist, you need to demonstrate that with code..that=
 is how the IETF works when the community is skeptical of your approach, whi=
ch is the case here.</div><div><br></div><div>Joe</div></body></html>=

--Apple-Mail-047C39DE-325D-4B2F-9598-D940A18E77F6--

From touch@isi.edu  Tue Sep 11 12:18:05 2012
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7DDC21F8617 for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 12:18:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.203
X-Spam-Level: 
X-Spam-Status: No, score=-101.203 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QsDD-u6Iv53H for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 12:18:05 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 5E11921F8613 for <int-area@ietf.org>; Tue, 11 Sep 2012 12:18:05 -0700 (PDT)
Received: from [59.10.124.171] ([59.10.124.171]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id q8BJHebt010665 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 11 Sep 2012 12:17:51 -0700 (PDT)
References: <CACQuieaOfyC5pJ2MyHBRTZYWCYfZMp58Ujh8rn0-yBBQL+kkzg@mail.gmail.com> <FAD8796F-0B15-4197-B952-AEE7FD56EDED@isi.edu> <CACQuiebgTXDmUmaE2n1yAbt4vS+V0M60fjXujqtMrh2n1WhPgQ@mail.gmail.com> <504ECFD9.4090107@isi.edu> <CACQuieZZiotwm9RinsuBAfPt6df21Y_z6JJPg4KNTMND2+E5RA@mail.gmail.com> <987000F4-9B41-4A4F-BF0B-0A207882194B@lacnic.net> <CACQuiea5gMXjkAT_ywA13EO2+HhY0v_OwwB+4_H_nz-Ddd=MEg@mail.gmail.com> <0E3416E0-1F00-42C8-B867-DF8726D9AC26@lacnic.net> <CACQuieYuXPMNCteb_HNvGZrSmx3red7NPFmFbBE8cY9KT8LOQg@mail.gmail.com> <C83D6793-ED56-41ED-9892-2D51F3BA0851@lacnic.net> <CACQuieZc2s6EdDRJPO1LPBokKh5-jaboNs_M1w4BYqwJ80GK4g@mail.gmail.com>
In-Reply-To: <CACQuieZc2s6EdDRJPO1LPBokKh5-jaboNs_M1w4BYqwJ80GK4g@mail.gmail.com>
Mime-Version: 1.0 (1.0)
Content-Type: text/plain; charset=us-ascii
Message-Id: <5697CD44-14DB-4172-9990-398BB44D64A0@isi.edu>
Content-Transfer-Encoding: quoted-printable
X-Mailer: iPad Mail (9B206)
From: Joe Touch <touch@isi.edu>
Date: Wed, 12 Sep 2012 04:17:40 +0900
To: Pars Mutaf <pars.mutaf@gmail.com>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] Discrete IP
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Sep 2012 19:18:05 -0000

On Sep 11, 2012, at 8:58 PM, Pars Mutaf <pars.mutaf@gmail.com> wrote:

> By "translation" I mean something completely new. It is written in the pap=
er:
>=20
> Splitting the path to two (or more) parts. One part is IPv4, the other par=
t is IPv6.=20
>=20
> Source IPv4 <-> Translator IPv4
> Translator IPv6 <-> Destination IPv6
>=20
> We take the data found in the IPv4 packet, we put it in an IPv6 packet (an=
d vice versa).

Addressed to where? The translator needs the state - like a nat would - to m=
ap packets it receives to destinations.  The ipv4 destination is what - the t=
ranslator itself? Or some alias for the ipv6 destination? The former cant wo=
rk because the translator can't know where to send the packet. The latter ca=
n't work because ipv4 addresses aren't large enough to support aliases for a=
ll of ipv6.=20

> By translation, I do not mean translating the information found the in the=
 headers. We only copy data. (from IPv4 packet to IPv6 packet and vice versa=
). See the paper for illustration (Figure 2).
>=20
> How TCP works on this, I don't know yet. I don't have to know it right now=
.

Yes you do.

....
> Sending a packet from an IPv4 host to an IPv6 host, connected using such a=
 translator, is a routing problem. The problem is that TCP assumes same IP v=
ersion for source and destination. We need another type of identifier, perha=
ps.

Yes you do.  But that would render ipv4 and ipv6 into link layers over which=
 your new packets with their addresses would traverse.

> Such proposals exist already. But again, what is important here is not the=
 solution. What is important is "What we want".

What is important is whether you have a solution.  This is not a research ve=
nue. =20

Joe=

From pars.mutaf@gmail.com  Tue Sep 11 20:50:35 2012
Return-Path: <pars.mutaf@gmail.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F82F21E8048 for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 20:50:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.436
X-Spam-Level: 
X-Spam-Status: No, score=-3.436 tagged_above=-999 required=5 tests=[AWL=0.162,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ndvhtlPCgqmV for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 20:50:34 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id E147621E804C for <int-area@ietf.org>; Tue, 11 Sep 2012 20:50:33 -0700 (PDT)
Received: by vbbfc26 with SMTP id fc26so1731324vbb.31 for <int-area@ietf.org>; Tue, 11 Sep 2012 20:50:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=iwOZr65+UvAs3+N21hexugmWYIwkexrt7IzMvxjlDtE=; b=fVJjRAXy7/XXreoJZqWuW4SLgig+89DkZOMQLnd2QP5kU/b9yZ4CvcS3EaIkPJ6gO6 PVzuQNiukOkrRJpx21uLcN47GGW33/oZi4+UchR0DMGq42UOdrtU+GiykAIsXvSocRuT dCoLtDWRo/pULMuziopInpifhLwSDFcCpvrXgvHPH5WCI+8ymlgdMDBv1TVkBV6Etd3G r/H4GN4jcjSxHMMRToOJL9BXP0gzEn/oQMS7Oy9pXYhuhnhHRbmUNBaX1mV1HMdEnH4d hujepxf5B/x6hNTE0sH0Brd/+FXOmJCZ4nfsjyB0n/bZWjXB8mo9ykNRSAFipt00zRVN +yAQ==
MIME-Version: 1.0
Received: by 10.58.74.3 with SMTP id p3mr30513307vev.27.1347421833031; Tue, 11 Sep 2012 20:50:33 -0700 (PDT)
Received: by 10.58.213.101 with HTTP; Tue, 11 Sep 2012 20:50:32 -0700 (PDT)
In-Reply-To: <30024711-4DB2-4CD2-B20A-530DAD47DFAC@kumari.net>
References: <CACQuieaOfyC5pJ2MyHBRTZYWCYfZMp58Ujh8rn0-yBBQL+kkzg@mail.gmail.com> <FAD8796F-0B15-4197-B952-AEE7FD56EDED@isi.edu> <CACQuiebgTXDmUmaE2n1yAbt4vS+V0M60fjXujqtMrh2n1WhPgQ@mail.gmail.com> <504ECFD9.4090107@isi.edu> <CACQuieZZiotwm9RinsuBAfPt6df21Y_z6JJPg4KNTMND2+E5RA@mail.gmail.com> <987000F4-9B41-4A4F-BF0B-0A207882194B@lacnic.net> <CACQuiea5gMXjkAT_ywA13EO2+HhY0v_OwwB+4_H_nz-Ddd=MEg@mail.gmail.com> <0E3416E0-1F00-42C8-B867-DF8726D9AC26@lacnic.net> <CACQuieYuXPMNCteb_HNvGZrSmx3red7NPFmFbBE8cY9KT8LOQg@mail.gmail.com> <C83D6793-ED56-41ED-9892-2D51F3BA0851@lacnic.net> <CACQuieZc2s6EdDRJPO1LPBokKh5-jaboNs_M1w4BYqwJ80GK4g@mail.gmail.com> <CACQuieYSs0GP=nyx==x3-u61Ri8DCrcOhDP8e5tBH1xstyyzHQ@mail.gmail.com> <AC4D2CAF-C76C-4AFD-98AC-7A7D512378BA@kumari.net> <CACQuieaTufrR=emTP3PgvDv9qYV7WWiKTKyrjBfjWx-ykbp=3A@mail.gmail.com> <30024711-4DB2-4CD2-B20A-530DAD47DFAC@kumari.net>
Date: Wed, 12 Sep 2012 06:50:32 +0300
Message-ID: <CACQuiebHeMz-GaaKb6=TMJ0k7_WdY1PMcqoN6uBqA+f4Xs9O_g@mail.gmail.com>
From: Pars Mutaf <pars.mutaf@gmail.com>
To: Warren Kumari <warren@kumari.net>
Content-Type: multipart/alternative; boundary=047d7bae44c8b86f5e04c979177b
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] Discrete IP
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Sep 2012 03:50:35 -0000

--047d7bae44c8b86f5e04c979177b
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Warren,

On Tue, Sep 11, 2012 at 8:12 PM, Warren Kumari <warren@kumari.net> wrote:

>
> On Sep 11, 2012, at 12:44 PM, Pars Mutaf wrote:
>
> >
> >
> > On Tue, Sep 11, 2012 at 5:38 PM, Warren Kumari <warren@kumari.net>
> wrote:
> >
> > On Sep 11, 2012, at 10:31 AM, Pars Mutaf wrote:
> >
> > > Hi all,
> > >
> > > Instead of IP translator, I use the new term "IP payload copier". It
> copies payload between different IP versions.
> >
> > Right=85 And who runs these? And who pays for them? And how many do you
> need? And how do you scale them? And how does discovery work? And how are
> they different to current NAT64 type things?
> >
> > W
> >
> >
> >
> >
> > They are like other routing devices. ISPs pay.
>
> And their incentive for this is?
>

Same incentives for buying a router. The copier is like a router but it is
not a router.


>
> >
> > NAT64 works by translating the headers if I am not wrong (I just
> checked). IP payload copiers that I propose, copy payload from one versio=
n
> to another.
> >
> > We need 1 or 2 between this Internet and China's IPv6 Internet. Then
> another one, etc. As I see they are not different from backbone routers.
> >
> > The real question is not how it works, for the moment. The real questio=
n
> is: What do we want:
> >
> > 1. Worry about the whole core Internet, others' IP version choices? (a
> question that has no end no answer), or
> > 2. Change the end nodes.
>
> You left out:
> 3. Not have a small number of devices that break the end-to-end principle=
,
> cause performance issues,  end up as monitoring / choke points and make
> debugging hard.
>


I don't understand what you mean exactly, it is not clear. In any case,
this is their problem, you cannot intervene in others' affairs.


>
> W
>
>
> >
> >
> >
> > Pars
> >
> >
> >
> >
> >
> >
> >
> > > TCP does not work on this because it assumes same IP version for
> source and destination.
> > >
> > > We probably need a new host identifier, and change TCP to use this
> identifier but the IP version transition problem is solved forever.
> Everybody use the IP version of their preference. This is the end-to-end
> princple, we do not care about the core Internet, we change the end-hosts=
.
> > >
> > > See details in the paper:
> > >
> > > http://www.scribd.com/doc/105448105/Discrete-IP
> > >
> > >
> > > On Tue, Sep 11, 2012 at 2:58 PM, Pars Mutaf <pars.mutaf@gmail.com>
> wrote:
> > > By "translation" I mean something completely new. It is written in th=
e
> paper:
> > >
> > > Splitting the path to two (or more) parts. One part is IPv4, the othe=
r
> part is IPv6.
> > >
> > > Source IPv4 <-> Translator IPv4
> > > Translator IPv6 <-> Destination IPv6
> > >
> > > We take the data found in the IPv4 packet, we put it in an IPv6 packe=
t
> (and vice versa).
> > >
> > > By translation, I do not mean translating the information found the i=
n
> the headers. We only copy data. (from IPv4 packet to IPv6 packet and vice
> versa). See the paper for illustration (Figure 2).
> > >
> > > How TCP works on this, I don't know yet. I don't have to know it righ=
t
> now. What is important is "What we want".
> > >
> > > 1. Worry about the core network, i.e. others' IP version preferences
> forever, or
> > > 2. Change the end-node TCP design, if necessary to solve this problem=
.
> > >
> > > Sending a packet from an IPv4 host to an IPv6 host, connected using
> such a translator, is a routing problem. The problem is that TCP assumes
> same IP version for source and destination. We need another type of
> identifier, perhaps. Such proposals exist already. But again, what is
> important here is not the solution. What is important is "What we want". =
It
> is one of the two possibilities mentioned above. The second one, better
> respects the end-to-end principle.
> > >
> > > Pars
> > >
> > >
> > >
> > > On Tue, Sep 11, 2012 at 1:38 PM, Arturo Servin <aservin@lacnic.net>
> wrote:
> > >
> > >       The big flaw of your idea is that you suppose that translation
> magically works, which it is not true due to the complexity of some
> protocols. That is why I am sceptical.
> > >
> > >       You are very welcome to try your idea. Let me know how it goes.
> > >
> > > /as
> > >
> > >
> > > On 11 Sep 2012, at 11:21, Pars Mutaf wrote:
> > >
> > >> Hi Arturo,
> > >>
> > >> On Tue, Sep 11, 2012 at 1:04 PM, Arturo Servin <aservin@lacnic.net>
> wrote:
> > >>
> > >> On 11 Sep 2012, at 10:55, Pars Mutaf wrote:
> > >>
> > >>>
> > >>> "Do you have some running code?"
> > >>>
> > >>> These are all ideas and behavior that we adopted without
> questioning. We use them in wrong situations generally.
> > >>
> > >>      Which already exists in many forms of translation mechanisms
> that we know are not the best way to solve the problem. There are plenty =
of
> documents on the Internet that will tell you why.
> > >>
> > >>
> > >> I believe that people should be able to choose their own solutions.
> Would you transition to IPv6 if Discrete IP worked for you? Some entities
> may, others may not, others may do it when they have money, yet others ma=
y
> invent and use IPv7. We cannot know.
> > >>
> > >> This means that China may use IPv6, Uruguay may not. We see what
> people decide, we cannot force them. They use translators if they wish. I
> want to develop and test a new IPvX in my university and be reachable to
> the world, who can say no?
> > >>
> > >> Not knowing what is good for others, not knowing the future, helps
> technology develop. It also reduces our suffering because we do not try t=
o
> know the unknowable.
> > >>
> > >>
> > >>>
> > >>> We first discuss the idea, then implement.
> > >>>
> > >>> The fact that there is running code doesn't mean that it is a good
> idea.
> > >>
> > >>
> > >>      But if it were, it would help to convince the sceptical like me=
.
> > >>
> > >>
> > >> I don't see why this would convince you.
> > >>
> > >>
> > >>      Also, the fact that there is not running code could mean that
> the idea is impractical and infeasible.
> > >>
> > >>
> > >> No you can implement anything. Even the worst idea.
> > >>
> > >> Pars
> > >>
> > >>
> > >> Cheers,
> > >> as
> > >>
> > >>>
> > >>>
> > >>> On Tue, Sep 11, 2012 at 12:22 PM, Arturo Servin <aservin@lacnic.net=
>
> wrote:
> > >>>
> > >>> On 11 Sep 2012, at 08:20, Pars Mutaf wrote:
> > >>>
> > >>>> Discrete IP:
> > >>>>
> > >>>> 1. Can be a very good transition mechanism to worldwide IPv6
> without enforcement (meaning that we have no idea what is good for others=
)
> > >>>
> > >>>     Do you have some running code?
> > >>>
> > >>>> 2. Can solve the IP transition problem forever.
> > >>>
> > >>>     Forgive for being sceptical of those all magical technologies
> that solve all the problems of the world. Of course, if you had running
> code that would change my view.
> > >>>
> > >>> Cheers,
> > >>> as
> > >>>
> > >>
> > >>
> > >
> > >
> > >
> > > _______________________________________________
> > > Int-area mailing list
> > > Int-area@ietf.org
> > > https://www.ietf.org/mailman/listinfo/int-area
> >
> > --
> > After you'd known Christine for any length of time, you found yourself
> fighting a desire to look into her ear to see if you could spot daylight
> coming the other way.
> >
> >     -- (Terry Pratchett, Maskerade)
> >
> >
> >
> >
> >
>
> --
> "Working the ICANN process is like being nibbled to death by ducks,
> it takes forever, it doesn't make sense, and in the end we're still dead
> in the water."
>     -- Tom Galvin, VeriSign's vice president for government relations.
>
>
>
>

--047d7bae44c8b86f5e04c979177b
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Warren, <br><br><div class=3D"gmail_quote">On Tue, Sep 11, 2012 at 8:12 =
PM, Warren Kumari <span dir=3D"ltr">&lt;<a href=3D"mailto:warren@kumari.net=
" target=3D"_blank">warren@kumari.net</a>&gt;</span> wrote:<br><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid=
;padding-left:1ex">
<div class=3D"im"><br>
On Sep 11, 2012, at 12:44 PM, Pars Mutaf wrote:<br>
<br>
&gt;<br>
&gt;<br>
&gt; On Tue, Sep 11, 2012 at 5:38 PM, Warren Kumari &lt;<a href=3D"mailto:w=
arren@kumari.net">warren@kumari.net</a>&gt; wrote:<br>
&gt;<br>
&gt; On Sep 11, 2012, at 10:31 AM, Pars Mutaf wrote:<br>
&gt;<br>
&gt; &gt; Hi all,<br>
&gt; &gt;<br>
&gt; &gt; Instead of IP translator, I use the new term &quot;IP payload cop=
ier&quot;. It copies payload between different IP versions.<br>
&gt;<br>
&gt; Right=85 And who runs these? And who pays for them? And how many do yo=
u need? And how do you scale them? And how does discovery work? And how are=
 they different to current NAT64 type things?<br>
&gt;<br>
&gt; W<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; They are like other routing devices. ISPs pay.<br>
<br>
</div>And their incentive for this is?<br></blockquote><div><br>Same incent=
ives for buying a router. The copier is like a router but it is not a route=
r. <br>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0pt 0pt 0=
pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">

<div class=3D"im"><br>
&gt;<br>
&gt; NAT64 works by translating the headers if I am not wrong (I just check=
ed). IP payload copiers that I propose, copy payload from one version to an=
other.<br>
&gt;<br>
&gt; We need 1 or 2 between this Internet and China&#39;s IPv6 Internet. Th=
en another one, etc. As I see they are not different from backbone routers.=
<br>
&gt;<br>
&gt; The real question is not how it works, for the moment. The real questi=
on is: What do we want:<br>
&gt;<br>
&gt; 1. Worry about the whole core Internet, others&#39; IP version choices=
? (a question that has no end no answer), or<br>
&gt; 2. Change the end nodes.<br>
<br>
</div>You left out:<br>
3. Not have a small number of devices that break the end-to-end principle, =
cause performance issues, =A0end up as monitoring / choke points and make d=
ebugging hard.<br></blockquote><div><br><br>I don&#39;t understand what you=
 mean exactly, it is not clear. In any case, this is their problem, you can=
not intervene in others&#39; affairs. <br>
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0pt 0pt 0pt 0.8e=
x;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div><div class=3D"h5"><br>
W<br>
<br>
<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Pars<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; &gt; TCP does not work on this because it assumes same IP version for =
source and destination.<br>
&gt; &gt;<br>
&gt; &gt; We probably need a new host identifier, and change TCP to use thi=
s identifier but the IP version transition problem is solved forever. Every=
body use the IP version of their preference. This is the end-to-end princpl=
e, we do not care about the core Internet, we change the end-hosts.<br>

&gt; &gt;<br>
&gt; &gt; See details in the paper:<br>
&gt; &gt;<br>
&gt; &gt; <a href=3D"http://www.scribd.com/doc/105448105/Discrete-IP" targe=
t=3D"_blank">http://www.scribd.com/doc/105448105/Discrete-IP</a><br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; On Tue, Sep 11, 2012 at 2:58 PM, Pars Mutaf &lt;<a href=3D"mailto=
:pars.mutaf@gmail.com">pars.mutaf@gmail.com</a>&gt; wrote:<br>
&gt; &gt; By &quot;translation&quot; I mean something completely new. It is=
 written in the paper:<br>
&gt; &gt;<br>
&gt; &gt; Splitting the path to two (or more) parts. One part is IPv4, the =
other part is IPv6.<br>
&gt; &gt;<br>
&gt; &gt; Source IPv4 &lt;-&gt; Translator IPv4<br>
&gt; &gt; Translator IPv6 &lt;-&gt; Destination IPv6<br>
&gt; &gt;<br>
&gt; &gt; We take the data found in the IPv4 packet, we put it in an IPv6 p=
acket (and vice versa).<br>
&gt; &gt;<br>
&gt; &gt; By translation, I do not mean translating the information found t=
he in the headers. We only copy data. (from IPv4 packet to IPv6 packet and =
vice versa). See the paper for illustration (Figure 2).<br>
&gt; &gt;<br>
&gt; &gt; How TCP works on this, I don&#39;t know yet. I don&#39;t have to =
know it right now. What is important is &quot;What we want&quot;.<br>
&gt; &gt;<br>
&gt; &gt; 1. Worry about the core network, i.e. others&#39; IP version pref=
erences forever, or<br>
&gt; &gt; 2. Change the end-node TCP design, if necessary to solve this pro=
blem.<br>
&gt; &gt;<br>
&gt; &gt; Sending a packet from an IPv4 host to an IPv6 host, connected usi=
ng such a translator, is a routing problem. The problem is that TCP assumes=
 same IP version for source and destination. We need another type of identi=
fier, perhaps. Such proposals exist already. But again, what is important h=
ere is not the solution. What is important is &quot;What we want&quot;. It =
is one of the two possibilities mentioned above. The second one, better res=
pects the end-to-end principle.<br>

&gt; &gt;<br>
&gt; &gt; Pars<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; On Tue, Sep 11, 2012 at 1:38 PM, Arturo Servin &lt;<a href=3D"mai=
lto:aservin@lacnic.net">aservin@lacnic.net</a>&gt; wrote:<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 The big flaw of your idea is that you suppose that tr=
anslation magically works, which it is not true due to the complexity of so=
me protocols. That is why I am sceptical.<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 You are very welcome to try your idea. Let me know ho=
w it goes.<br>
&gt; &gt;<br>
&gt; &gt; /as<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; On 11 Sep 2012, at 11:21, Pars Mutaf wrote:<br>
&gt; &gt;<br>
&gt; &gt;&gt; Hi Arturo,<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; On Tue, Sep 11, 2012 at 1:04 PM, Arturo Servin &lt;<a href=3D=
"mailto:aservin@lacnic.net">aservin@lacnic.net</a>&gt; wrote:<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; On 11 Sep 2012, at 10:55, Pars Mutaf wrote:<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; &quot;Do you have some running code?&quot;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; These are all ideas and behavior that we adopted without =
questioning. We use them in wrong situations generally.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; =A0 =A0 =A0Which already exists in many forms of translation =
mechanisms that we know are not the best way to solve the problem. There ar=
e plenty of documents on the Internet that will tell you why.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; I believe that people should be able to choose their own solu=
tions. Would you transition to IPv6 if Discrete IP worked for you? Some ent=
ities may, others may not, others may do it when they have money, yet other=
s may invent and use IPv7. We cannot know.<br>

&gt; &gt;&gt;<br>
&gt; &gt;&gt; This means that China may use IPv6, Uruguay may not. We see w=
hat people decide, we cannot force them. They use translators if they wish.=
 I want to develop and test a new IPvX in my university and be reachable to=
 the world, who can say no?<br>

&gt; &gt;&gt;<br>
&gt; &gt;&gt; Not knowing what is good for others, not knowing the future, =
helps technology develop. It also reduces our suffering because we do not t=
ry to know the unknowable.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; We first discuss the idea, then implement.<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; The fact that there is running code doesn&#39;t mean that=
 it is a good idea.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; =A0 =A0 =A0But if it were, it would help to convince the scep=
tical like me.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; I don&#39;t see why this would convince you.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; =A0 =A0 =A0Also, the fact that there is not running code coul=
d mean that the idea is impractical and infeasible.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; No you can implement anything. Even the worst idea.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Pars<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Cheers,<br>
&gt; &gt;&gt; as<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; On Tue, Sep 11, 2012 at 12:22 PM, Arturo Servin &lt;<a hr=
ef=3D"mailto:aservin@lacnic.net">aservin@lacnic.net</a>&gt; wrote:<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; On 11 Sep 2012, at 08:20, Pars Mutaf wrote:<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; Discrete IP:<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; 1. Can be a very good transition mechanism to worldwi=
de IPv6 without enforcement (meaning that we have no idea what is good for =
others)<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; =A0 =A0 Do you have some running code?<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; 2. Can solve the IP transition problem forever.<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; =A0 =A0 Forgive for being sceptical of those all magical =
technologies that solve all the problems of the world. Of course, if you ha=
d running code that would change my view.<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Cheers,<br>
&gt; &gt;&gt;&gt; as<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; Int-area mailing list<br>
&gt; &gt; <a href=3D"mailto:Int-area@ietf.org">Int-area@ietf.org</a><br>
&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/int-area" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/int-area</a><br>
&gt;<br>
&gt; --<br>
&gt; After you&#39;d known Christine for any length of time, you found your=
self fighting a desire to look into her ear to see if you could spot daylig=
ht coming the other way.<br>
&gt;<br>
&gt; =A0 =A0 -- (Terry Pratchett, Maskerade)<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
<br>
</div></div>--<br>
&quot;Working the ICANN process is like being nibbled to death by ducks,<br=
>
it takes forever, it doesn&#39;t make sense, and in the end we&#39;re still=
 dead in the water.&quot;<br>
=A0 =A0 -- Tom Galvin, VeriSign&#39;s vice president for government relatio=
ns.<br>
<br>
<br>
<br>
</blockquote></div><br>

--047d7bae44c8b86f5e04c979177b--

From pars.mutaf@gmail.com  Tue Sep 11 21:07:42 2012
Return-Path: <pars.mutaf@gmail.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BAB321F847C for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 21:07:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.454
X-Spam-Level: 
X-Spam-Status: No, score=-3.454 tagged_above=-999 required=5 tests=[AWL=0.144,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H6Qmf3bQVIwT for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 21:07:41 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id EFE5321F847F for <int-area@ietf.org>; Tue, 11 Sep 2012 21:07:37 -0700 (PDT)
Received: by vbbfc26 with SMTP id fc26so1743455vbb.31 for <int-area@ietf.org>; Tue, 11 Sep 2012 21:07:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=BrjMUXUWSAELx1zT6/6SSwLWGbg+Tvcz/AdZiHo/eb4=; b=QYAJ3F59IV1xFakNllOYfHjbfJ34BKZY1VZgARi5ka7qAuev93QhQj3SH+gEXYJ84o eQW2JV3LS7qw4bS8VGuE67BSUqYtpR/brJo37FH9Sy56c8p2lPNO+3BPrVeLjBXg1Nii qR83HwTzcqm7opvTRs9gUGdoM05XWEG3QMvtb7NXVRviKQc+fORU8OppMjUXh5z6RTaN kCTSE3/V+n16481GJype2FyIcdKcFUFzwnUC5rx6mv0KBqYK3MW0ksRCWhWd3YDgLxmC PaHAxYBhKQcAC96oVNbzV4clLE5KUQJnMuHHvjXYTK4j14m80voEb1x6uyt233GbJsHV 6jHw==
MIME-Version: 1.0
Received: by 10.52.70.46 with SMTP id j14mr22111260vdu.42.1347422857468; Tue, 11 Sep 2012 21:07:37 -0700 (PDT)
Received: by 10.58.213.101 with HTTP; Tue, 11 Sep 2012 21:07:37 -0700 (PDT)
In-Reply-To: <56839629-0B52-4DCC-B2C3-682AFC40D231@isi.edu>
References: <CACQuieaOfyC5pJ2MyHBRTZYWCYfZMp58Ujh8rn0-yBBQL+kkzg@mail.gmail.com> <FAD8796F-0B15-4197-B952-AEE7FD56EDED@isi.edu> <CACQuiebgTXDmUmaE2n1yAbt4vS+V0M60fjXujqtMrh2n1WhPgQ@mail.gmail.com> <504ECFD9.4090107@isi.edu> <CACQuieZZiotwm9RinsuBAfPt6df21Y_z6JJPg4KNTMND2+E5RA@mail.gmail.com> <987000F4-9B41-4A4F-BF0B-0A207882194B@lacnic.net> <CACQuiea5gMXjkAT_ywA13EO2+HhY0v_OwwB+4_H_nz-Ddd=MEg@mail.gmail.com> <0E3416E0-1F00-42C8-B867-DF8726D9AC26@lacnic.net> <CACQuieYuXPMNCteb_HNvGZrSmx3red7NPFmFbBE8cY9KT8LOQg@mail.gmail.com> <C83D6793-ED56-41ED-9892-2D51F3BA0851@lacnic.net> <CACQuieZc2s6EdDRJPO1LPBokKh5-jaboNs_M1w4BYqwJ80GK4g@mail.gmail.com> <CACQuieYSs0GP=nyx==x3-u61Ri8DCrcOhDP8e5tBH1xstyyzHQ@mail.gmail.com> <56839629-0B52-4DCC-B2C3-682AFC40D231@isi.edu>
Date: Wed, 12 Sep 2012 07:07:37 +0300
Message-ID: <CACQuiebwB4M_ASmFNW8X53-911vyc9AmOd=2KpJQMaD2rGVkHA@mail.gmail.com>
From: Pars Mutaf <pars.mutaf@gmail.com>
To: Joe Touch <touch@isi.edu>
Content-Type: multipart/alternative; boundary=20cf307f39aac81c1804c97954a1
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] Discrete IP
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Sep 2012 04:07:42 -0000

--20cf307f39aac81c1804c97954a1
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Sep 11, 2012 at 10:07 PM, Joe Touch <touch@isi.edu> wrote:

>
>
> On Sep 11, 2012, at 11:31 PM, Pars Mutaf <pars.mutaf@gmail.com> wrote:
>
> Hi all,
>
> Instead of IP translator, I use the new term "IP payload copier". It
> copies payload between different IP versions. TCP does not work on this
> because it assumes same IP version for source and destination.
>
> We probably need a new host identifier,
>
>
> And that is IPv6 right now.
>
> Call us when you fix that. and maybe also look at realm-specific IP.
>
> and change TCP to use this identifier but the IP version transition
> problem is solved forever. Everybody use the IP version of their
> preference. This is the end-to-end princple, we do not care about the core
> Internet, we change the end-hosts.
>
> See details in the paper:
>
> http://www.scribd.com/doc/105448105/Discrete-IP
>
>
> There are no details.
>
> E.g., let's say I'm ipv4 and want to talk to you who are ipv6 right now.
> So I go to the DNS and ask for you.  First, you have to assume a global
> namespace above IP - the DNS name - the identifies endpoints.  Second, what
> will you give me? I don't understand an ipv6 address.  So you hand me the
> ipv4 of the translator? Then if I send a packet there, it won't know who to
> send it onward to.
>


All these are explained in the paper Joe. I tunnel the first packet to the
copier. (I don't use the term translator to avoid confusion)

Why do you refuse to *read it?*



>
> You have a paper, but it is lacking in exactly the solutions everyone has
> been trying to find for years, and some have shown don't or can't exist.
>
> So I agree with some others that if you insist a solution can exist, you
> need to demonstrate that with code..that is how the IETF works when the
> community is skeptical of your approach, which is the case here.
>


This is just loss of time. There are many IETF protocols that are designed
first, implemented later. Ex: IPv6, MIPv6 etc.  So...

In addition, as I said earlier, having running code doesn't mean that it is
a good idea.

The correct approach is:

1. Decide what we want.
2. See if it is feasible. If it is not, we know that what we want is not
feasible. (I would be surprised because anything is feasible)

In my opinion Discrete IP is feasible. The paper (you did not read before
entering this discussion) gives enough evidence. But if you look for
unnecessary details like running code you cannot see this.





>
> Joe
>

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

<br><br><div class=3D"gmail_quote">On Tue, Sep 11, 2012 at 10:07 PM, Joe To=
uch <span dir=3D"ltr">&lt;<a href=3D"mailto:touch@isi.edu" target=3D"_blank=
">touch@isi.edu</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor=3D"#FFFFFF"><div class=3D"im"><div><br><br>On Sep 11, 2012, at=
 11:31 PM, Pars Mutaf &lt;<a href=3D"mailto:pars.mutaf@gmail.com" target=3D=
"_blank">pars.mutaf@gmail.com</a>&gt; wrote:<br><br></div><div></div><block=
quote type=3D"cite">
<div><div>Hi all,=A0</div><div><br></div><div>Instead of IP translator, I u=
se the new term &quot;IP payload copier&quot;. It copies payload between di=
fferent IP versions. TCP does not work on this because it assumes same IP v=
ersion for source and destination.</div>

<div><br></div><div>We probably need a new host identifier, </div></div></b=
lockquote><div><br></div></div>And that is IPv6 right now.<br><div><br></di=
v><div>Call us when you fix that. and maybe also look at realm-specific IP.=
</div>
<div class=3D"im"><br><blockquote type=3D"cite"><div><div>and change=A0TCP =
to use this identifier but the IP version transition problem is solved fore=
ver.=A0Everybody use the IP version of their preference.=A0This is the end-=
to-end princple, we do not care about the core Internet, we change the end-=
hosts.</div>

<div><br></div><div>See details in the paper:</div><div><br></div><a href=
=3D"http://www.scribd.com/doc/105448105/Discrete-IP" target=3D"_blank">http=
://www.scribd.com/doc/105448105/Discrete-IP</a>=A0<br></div></blockquote><d=
iv>
<br></div></div><div>There are no details.</div><div><br></div><div>E.g., l=
et&#39;s say I&#39;m ipv4 and want to talk to you who are ipv6 right now. S=
o I go to the DNS and ask for you. =A0First, you have to assume a global na=
mespace above IP - the DNS name - the identifies endpoints. =A0Second, what=
 will you give me? I don&#39;t understand an ipv6 address. =A0So you hand m=
e the ipv4 of the translator? Then if I send a packet there, it won&#39;t k=
now who to send it onward to.</div>
</div></blockquote><div><br><br>All these are explained in the paper Joe. I=
 tunnel the first packet to the copier. (I don&#39;t use the term translato=
r to avoid confusion)<br><br>Why do you refuse to *read it?*<br><br>=A0<br>
</div><blockquote class=3D"gmail_quote" style=3D"margin:0pt 0pt 0pt 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor=3D"#FF=
FFFF"><div><br></div><div>You have a paper, but it is lacking in exactly th=
e solutions everyone has been trying to find for years, and some have shown=
 don&#39;t or can&#39;t exist.</div>
<div><br></div><div>So I agree with some others that if you insist a soluti=
on can exist, you need to demonstrate that with code..that is how the IETF =
works when the community is skeptical of your approach, which is the case h=
ere.</div>
</div></blockquote><div><br><br>This is just loss of time. There are many I=
ETF protocols that are designed first, implemented later. Ex: IPv6, MIPv6 e=
tc.=A0 So...<br><br>In addition, as I said earlier, having running code doe=
sn&#39;t mean that it is a good idea. <br>
<br>The correct approach is: <br><br>1. Decide what we want.<br>2. See if i=
t is feasible. If it is not, we know that what we want is not feasible. (I =
would be surprised because anything is feasible)<br><br>In my opinion Discr=
ete IP is feasible. The paper (you did not read before entering this discus=
sion) gives enough evidence. But if you look for unnecessary details like r=
unning code you cannot see this.<br>
<br><br><br>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0pt =
0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div=
 bgcolor=3D"#FFFFFF"><span class=3D"HOEnZb"><font color=3D"#888888"><div><b=
r></div>
<div>Joe</div></font></span></div></blockquote></div><br>

--20cf307f39aac81c1804c97954a1--

From touch@isi.edu  Tue Sep 11 21:38:08 2012
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D342D21F851B for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 21:38:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_57=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BDXbAAu52+IM for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 21:38:06 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 0EEFB21F84FA for <int-area@ietf.org>; Tue, 11 Sep 2012 21:38:06 -0700 (PDT)
Received: from [192.168.0.17] ([210.114.91.73]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id q8C4bRo8021155 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 11 Sep 2012 21:37:37 -0700 (PDT)
Message-ID: <50501186.3060200@isi.edu>
Date: Tue, 11 Sep 2012 21:37:26 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Pars Mutaf <pars.mutaf@gmail.com>
References: <CACQuieaOfyC5pJ2MyHBRTZYWCYfZMp58Ujh8rn0-yBBQL+kkzg@mail.gmail.com> <FAD8796F-0B15-4197-B952-AEE7FD56EDED@isi.edu> <CACQuiebgTXDmUmaE2n1yAbt4vS+V0M60fjXujqtMrh2n1WhPgQ@mail.gmail.com> <504ECFD9.4090107@isi.edu> <CACQuieZZiotwm9RinsuBAfPt6df21Y_z6JJPg4KNTMND2+E5RA@mail.gmail.com> <987000F4-9B41-4A4F-BF0B-0A207882194B@lacnic.net> <CACQuiea5gMXjkAT_ywA13EO2+HhY0v_OwwB+4_H_nz-Ddd=MEg@mail.gmail.com> <0E3416E0-1F00-42C8-B867-DF8726D9AC26@lacnic.net> <CACQuieYuXPMNCteb_HNvGZrSmx3red7NPFmFbBE8cY9KT8LOQg@mail.gmail.com> <C83D6793-ED56-41ED-9892-2D51F3BA0851@lacnic.net> <CACQuieZc2s6EdDRJPO1LPBokKh5-jaboNs_M1w4BYqwJ80GK4g@mail.gmail.com> <CACQuieYSs0GP=nyx==x3-u61Ri8DCrcOhDP8e5tBH1xstyyzHQ@mail.gmail.com> <56839629-0B52-4DCC-B2C3-682AFC40D231@isi.edu> <CACQuiebwB4M_ASmFNW8X53-911vyc9AmOd=2KpJQMaD2rGVkHA@mail.gmail.com>
In-Reply-To: <CACQuiebwB4M_ASmFNW8X53-911vyc9AmOd=2KpJQMaD2rGVkHA@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] Discrete IP
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Sep 2012 04:38:08 -0000

On 9/11/2012 9:07 PM, Pars Mutaf wrote:
...
> Why do you refuse to *read it?*

 From the paper:

-----
> All nodes in all Internets are registered to the DNS. The following
> example designis illustrated in Figure 2. IP payload copier, IPPC,
> copies the payload in IPv4 packets to IPv6 packets, and vice versa.
> It is different from IP translators which translate header
> information. I discuss later how TCP can work over this scheme.
>
> 1. Node A makes a DNS request, obtains the destination address D and
> the IPaddress of the IPPC to reach the address D. In this example,
> the IPPC address is B.
>
> 2. Node A tunnels the packet to the IPPC.
>
> 3. IPPC creates state for the addresses A and D.
>
> 4. IPPC copies the payload found in IPv4 packets to IPv6 packets, and
> vice versa,between A and D.
>
> 5. Tunneling is done for the first packet only.

----

So the IPPC acts as a NAT, and the state is setup by the first request 
to the DNS.

Known problems, in no specific order:

	a) like NAT, this fails for all protocols that use in-band
	identifiers (e.g., FTP) unless the entire body of the packet
	is translated too, and that might not be possible for some
	services

	b) you fail to explain why this needs to happen for the
	first packet and not all subsequent packets, or what to do
	with subsequent packets (and what happens when the second
	packet arrives - e.g., at the translator or elsewhere -
	before the first one?)

	c) the first packet won't be tunneled unless you upgrade
	the source endpoint node to speak your new version of things;
	if we could do that, everyone would be speaking IPv6

	d) what name/ID are you looking up in the DNS?
	the node application already did a lookup for the
	destination, and you now need to rewrite every application
	to use your solution instead

	(i.e., right now the DNS use is decoupled from network
	packet processing; you want to integrate it - have you
	seen Cheriton's I3 proposal along these lines?)

	e) which DNS do you register endpoints in? (answer: all of
	them, except that you can't know where the ones outside your
	"IP version" bubble are) so basically you're never going to
	find the endpoints in other bubbles anyway

	f) which payload-only are you forwarding? the one in the
	tunneled packet includes headers the next bubble doesn't
	understand; if you strip off those headers, you lose a lot
	of state

Again, from your paper: "We do not need to use NATs anymore" only 
because you don't call them that, but you're implementing a stateful NAT 
as a translator.

You claim:

---

> We do not touch the core network, i.e. the current IPv4
> infrastructurewhich works. Those who wish, add additional infrastructure
> if necessary(IPv4, IPv6, etc.)

You change the DNS and add translators on that IPv4 network.

> We modify the end-hosts only

Your translators are not end-hosts.

> We do not have worry about others' IP version preferences, we do not have to implement IPv6 for example

Your translators have to worry a lot about version preference.

---

Please read the Catenet paper.

You are treating each IP version as a link layer, your translators are 
IP routers, and your DNS works like ARP.

Unfortunately, that doesn't remove the need for an end-to-end 
internetworking layer with global addresses, which you don't have and 
don't address at all.

Joe


From pars.mutaf@gmail.com  Tue Sep 11 22:20:26 2012
Return-Path: <pars.mutaf@gmail.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74C2A21E8056 for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 22:20:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.168
X-Spam-Level: 
X-Spam-Status: No, score=-3.168 tagged_above=-999 required=5 tests=[AWL=-0.170, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_57=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iaPc5wthjB+O for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 22:20:25 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id BDC2B21E8051 for <int-area@ietf.org>; Tue, 11 Sep 2012 22:20:24 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so1780372vcb.31 for <int-area@ietf.org>; Tue, 11 Sep 2012 22:20:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=H/IYYf0l2d3e9XTwtcg6SpTjfq/TswwgbqlT6pZEtaA=; b=rffpQysySrgOM78HM/UFez1Sks/GqaAV/fGB2J3Wy9fia35j7+DnTCgT5SkUb0EtBv 8dZdxn1BPPyDNeUhtZSMXkV9r90uCTGBtByTrd3VzTpG8TXmmyUrsdpCcYwLdtyqsaYb 4osFc2ZQ7Q8+DTGknlLuqaiR6gPOo/5nkHcBMm5M2iCzKwllPs/agvZNOGUP0HZcnQJM 3FgIMkh8bNKj8qV49ti8XMNAECtNf6Ib0ZUYSvKPMmHKvGdSEIqpIWqImKgmjdnMC9g/ wb1gi23zzEzWe4jx5qzTdQ123QPZ16zY4lMyinwxwopjnYinVQPnyOLvq8/KbMbC4zRC 8Rag==
MIME-Version: 1.0
Received: by 10.58.35.166 with SMTP id i6mr11071000vej.10.1347427224007; Tue, 11 Sep 2012 22:20:24 -0700 (PDT)
Received: by 10.58.213.101 with HTTP; Tue, 11 Sep 2012 22:20:23 -0700 (PDT)
In-Reply-To: <50501186.3060200@isi.edu>
References: <CACQuieaOfyC5pJ2MyHBRTZYWCYfZMp58Ujh8rn0-yBBQL+kkzg@mail.gmail.com> <FAD8796F-0B15-4197-B952-AEE7FD56EDED@isi.edu> <CACQuiebgTXDmUmaE2n1yAbt4vS+V0M60fjXujqtMrh2n1WhPgQ@mail.gmail.com> <504ECFD9.4090107@isi.edu> <CACQuieZZiotwm9RinsuBAfPt6df21Y_z6JJPg4KNTMND2+E5RA@mail.gmail.com> <987000F4-9B41-4A4F-BF0B-0A207882194B@lacnic.net> <CACQuiea5gMXjkAT_ywA13EO2+HhY0v_OwwB+4_H_nz-Ddd=MEg@mail.gmail.com> <0E3416E0-1F00-42C8-B867-DF8726D9AC26@lacnic.net> <CACQuieYuXPMNCteb_HNvGZrSmx3red7NPFmFbBE8cY9KT8LOQg@mail.gmail.com> <C83D6793-ED56-41ED-9892-2D51F3BA0851@lacnic.net> <CACQuieZc2s6EdDRJPO1LPBokKh5-jaboNs_M1w4BYqwJ80GK4g@mail.gmail.com> <CACQuieYSs0GP=nyx==x3-u61Ri8DCrcOhDP8e5tBH1xstyyzHQ@mail.gmail.com> <56839629-0B52-4DCC-B2C3-682AFC40D231@isi.edu> <CACQuiebwB4M_ASmFNW8X53-911vyc9AmOd=2KpJQMaD2rGVkHA@mail.gmail.com> <50501186.3060200@isi.edu>
Date: Wed, 12 Sep 2012 08:20:23 +0300
Message-ID: <CACQuieb1aGAqBYMqEmX2KYteSqp_g8G44hHm0FqQ6bQXMuWmgg@mail.gmail.com>
From: Pars Mutaf <pars.mutaf@gmail.com>
To: Joe Touch <touch@isi.edu>
Content-Type: multipart/alternative; boundary=047d7b5d4c400c343a04c97a59e8
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] Discrete IP
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Sep 2012 05:20:26 -0000

--047d7b5d4c400c343a04c97a59e8
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Sep 12, 2012 at 7:37 AM, Joe Touch <touch@isi.edu> wrote:

> On 9/11/2012 9:07 PM, Pars Mutaf wrote:
> ...
>
>  Why do you refuse to *read it?*
>>
>
> From the paper:
>
> -----
>
>> All nodes in all Internets are registered to the DNS. The following
>> example designis illustrated in Figure 2. IP payload copier, IPPC,
>> copies the payload in IPv4 packets to IPv6 packets, and vice versa.
>> It is different from IP translators which translate header
>> information. I discuss later how TCP can work over this scheme.
>>
>> 1. Node A makes a DNS request, obtains the destination address D and
>> the IPaddress of the IPPC to reach the address D. In this example,
>> the IPPC address is B.
>>
>> 2. Node A tunnels the packet to the IPPC.
>>
>> 3. IPPC creates state for the addresses A and D.
>>
>> 4. IPPC copies the payload found in IPv4 packets to IPv6 packets, and
>> vice versa,between A and D.
>>
>> 5. Tunneling is done for the first packet only.
>>
>
> ----
>
> So the IPPC acts as a NAT, and the state is setup by the first request to
> the DNS.
>
> Known problems, in no specific order:
>
>         a) like NAT, this fails for all protocols that use in-band
>         identifiers (e.g., FTP) unless the entire body of the packet
>         is translated too, and that might not be possible for some
>         services
>

I don't understand. I just copy the whole payload. Or, replace the IPv4
header with an IPv6 header. I don't have to know what's in the payload.



>
>         b) you fail to explain why this needs to happen for the
>         first packet and not all subsequent packets, or what to do
>         with subsequent packets (and what happens when the second
>         packet arrives - e.g., at the translator or elsewhere -
>         before the first one?)
>


1. I send the first packet to the copier. In the same message, I tell the
destination IPv6 address that I learned using DNS for example. (this is not
exactly a tunnel I don't have to speak IPv6)
3. The copier creates state for my IPv4 address and destination IPv6
address.
4. Forwards packets in both directions



>         c) the first packet won't be tunneled unless you upgrade
>         the source endpoint node to speak your new version of things;
>         if we could do that, everyone would be speaking IPv6
>

Yes it is not a tunnel exactly. This is my bad. The first packet is a
special packet, call it a Discrete IP packet, telling the copier the
destination IPv6 address.



>         d) what name/ID are you looking up in the DNS?
>         the node application already did a lookup for the
>         destination, and you now need to rewrite every application
>         to use your solution instead
>

I assume a new host identifier, other than IP address.


>
>         (i.e., right now the DNS use is decoupled from network
>         packet processing; you want to integrate it - have you
>         seen Cheriton's I3 proposal along these lines?)
>


I am not sure if it should be integrated.



>         e) which DNS do you register endpoints in? (answer: all of
>         them, except that you can't know where the ones outside your
>         "IP version" bubble are) so basically you're never going to
>         find the endpoints in other bubbles anyway
>

You do not know what we can or cannot do yet. We didn't even discuss if we
want my proposal.
We attacked the details.



>         f) which payload-only are you forwarding? the one in the
>         tunneled packet includes headers the next bubble doesn't
>         understand; if you strip off those headers, you lose a lot
>         of state
>

No. The copier copies IPv4 payload to the IPv6 header that it creates
itself.


>
> Again, from your paper: "We do not need to use NATs anymore" only because
> you don't call them that, but you're implementing a stateful NAT as a
> translator.
>
>
The question is not they are like NATs or not, we are changing the
architecture. I can reuse yahoo's global IP address at home.


> You claim:
>
> ---
>
>  We do not touch the core network, i.e. the current IPv4
>> infrastructurewhich works. Those who wish, add additional infrastructure
>> if necessary(IPv4, IPv6, etc.)
>>
>
> You change the DNS and add translators on that IPv4 network.
>
>
I change DNS, I also change TCP. IPsec doesn't work, multicast is gone. But
this is a trade-off:

We are now free from core Internet's IP version decisions forever. This is
the real discussion that we should have here. Do we want this approach or
not? Once we decided that it is desirable, anything is designable. Because
we do not depend on core network anymore, we change the end points. This is
the end-to-end principle.

Do we want to be free from this IP version problem forever? What can we
sacrifice to solve this problem?



>  We modify the end-hosts only
>>
>
> Your translators are not end-hosts.
>
>
It is not a modification. People add them and remove them as they wish. It
is not like modifying all Internet routers.



>  We do not have worry about others' IP version preferences, we do not have
>> to implement IPv6 for example
>>
>
> Your translators have to worry a lot about version preference.
>

They are designed for that. And it is not big deal, they just copy payload.


>
> ---
>
> Please read the Catenet paper.
>
> You are treating each IP version as a link layer, your translators are IP
> routers, and your DNS works like ARP.
>
> Unfortunately, that doesn't remove the need for an end-to-end
> internetworking layer with global addresses, which you don't have and don't
> address at all.
>

Let's first discuss what we want. We may have a host identification layer
above IP for example but it is early to discuss technical details. We do
not even know what we want.


>
> Joe
>
>

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

<br><br><div class=3D"gmail_quote">On Wed, Sep 12, 2012 at 7:37 AM, Joe Tou=
ch <span dir=3D"ltr">&lt;<a href=3D"mailto:touch@isi.edu" target=3D"_blank"=
>touch@isi.edu</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 9/11/2012 9:07 PM, Pars Mutaf wrote:<br>
...<div class=3D"im"><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Why do you refuse to *read it?*<br>
</blockquote>
<br></div>
>From the paper:<br>
<br>
-----<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
All nodes in all Internets are registered to the DNS. The following<br>
example designis illustrated in Figure 2. IP payload copier, IPPC,<br>
copies the payload in IPv4 packets to IPv6 packets, and vice versa.<br>
It is different from IP translators which translate header<br>
information. I discuss later how TCP can work over this scheme.<br>
<br>
1. Node A makes a DNS request, obtains the destination address D and<br>
the IPaddress of the IPPC to reach the address D. In this example,<br>
the IPPC address is B.<br>
<br>
2. Node A tunnels the packet to the IPPC.<br>
<br>
3. IPPC creates state for the addresses A and D.<br>
<br>
4. IPPC copies the payload found in IPv4 packets to IPv6 packets, and<br>
vice versa,between A and D.<br>
<br>
5. Tunneling is done for the first packet only.<br>
</blockquote>
<br>
----<br>
<br>
So the IPPC acts as a NAT, and the state is setup by the first request to t=
he DNS.<br>
<br>
Known problems, in no specific order:<br>
<br>
=A0 =A0 =A0 =A0 a) like NAT, this fails for all protocols that use in-band<=
br>
=A0 =A0 =A0 =A0 identifiers (e.g., FTP) unless the entire body of the packe=
t<br>
=A0 =A0 =A0 =A0 is translated too, and that might not be possible for some<=
br>
=A0 =A0 =A0 =A0 services<br></blockquote><div><br>I don&#39;t understand. I=
 just copy the whole payload. Or, replace the IPv4<br>header with an IPv6 h=
eader. I don&#39;t have to know what&#39;s in the payload.<br><br>=A0</div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0pt 0pt 0pt 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">

<br>
=A0 =A0 =A0 =A0 b) you fail to explain why this needs to happen for the<br>
=A0 =A0 =A0 =A0 first packet and not all subsequent packets, or what to do<=
br>
=A0 =A0 =A0 =A0 with subsequent packets (and what happens when the second<b=
r>
=A0 =A0 =A0 =A0 packet arrives - e.g., at the translator or elsewhere -<br>
=A0 =A0 =A0 =A0 before the first one?)<br></blockquote><div><br><br>1. I se=
nd the first packet to the copier. In the same message, I tell the destinat=
ion IPv6 address that I learned using DNS for example. (this is not exactly=
 a tunnel I don&#39;t have to speak IPv6)<br>
3. The copier creates state for my IPv4 address and destination IPv6 addres=
s. <br>4. Forwards packets in both directions<br><br>=A0</div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0pt 0pt 0pt 0.8ex;border-left:1px soli=
d rgb(204,204,204);padding-left:1ex">


=A0 =A0 =A0 =A0 c) the first packet won&#39;t be tunneled unless you upgrad=
e<br>
=A0 =A0 =A0 =A0 the source endpoint node to speak your new version of thing=
s;<br>
=A0 =A0 =A0 =A0 if we could do that, everyone would be speaking IPv6<br></b=
lockquote><div><br>Yes it is not a tunnel exactly. This is my bad. The firs=
t packet is a special packet, call it a Discrete IP packet, telling the cop=
ier the destination IPv6 address.<br>
<br>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0pt 0pt 0pt =
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
=A0 =A0 =A0 =A0 d) what name/ID are you looking up in the DNS?<br>
=A0 =A0 =A0 =A0 the node application already did a lookup for the<br>
=A0 =A0 =A0 =A0 destination, and you now need to rewrite every application<=
br>
=A0 =A0 =A0 =A0 to use your solution instead<br></blockquote><div><br>I ass=
ume a new host identifier, other than IP address.<br>=A0</div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0pt 0pt 0pt 0.8ex;border-left:1px soli=
d rgb(204,204,204);padding-left:1ex">

<br>
=A0 =A0 =A0 =A0 (i.e., right now the DNS use is decoupled from network<br>
=A0 =A0 =A0 =A0 packet processing; you want to integrate it - have you<br>
=A0 =A0 =A0 =A0 seen Cheriton&#39;s I3 proposal along these lines?)<br></bl=
ockquote><div><br><br>I am not sure if it should be integrated. <br><br>=A0=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0pt 0pt 0pt 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex">

=A0 =A0 =A0 =A0 e) which DNS do you register endpoints in? (answer: all of<=
br>
=A0 =A0 =A0 =A0 them, except that you can&#39;t know where the ones outside=
 your<br>
=A0 =A0 =A0 =A0 &quot;IP version&quot; bubble are) so basically you&#39;re =
never going to<br>
=A0 =A0 =A0 =A0 find the endpoints in other bubbles anyway<br></blockquote>=
<div><br>You do not know what we can or cannot do yet. We didn&#39;t even d=
iscuss if we want my proposal.<br>We attacked the details.<br><br>=A0</div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0pt 0pt 0pt 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">


=A0 =A0 =A0 =A0 f) which payload-only are you forwarding? the one in the<br=
>
=A0 =A0 =A0 =A0 tunneled packet includes headers the next bubble doesn&#39;=
t<br>
=A0 =A0 =A0 =A0 understand; if you strip off those headers, you lose a lot<=
br>
=A0 =A0 =A0 =A0 of state<br></blockquote><div><br>No. The copier copies IPv=
4 payload to the IPv6 header that it creates itself.<br>=A0</div><blockquot=
e class=3D"gmail_quote" style=3D"margin:0pt 0pt 0pt 0.8ex;border-left:1px s=
olid rgb(204,204,204);padding-left:1ex">

<br>
Again, from your paper: &quot;We do not need to use NATs anymore&quot; only=
 because you don&#39;t call them that, but you&#39;re implementing a statef=
ul NAT as a translator.<br>
<br></blockquote><div><br>The question is not they are like NATs or not, we=
 are changing the architecture. I can reuse yahoo&#39;s global IP address a=
t home.<br>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0pt 0=
pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">

You claim:<br>
<br>
---<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
We do not touch the core network, i.e. the current IPv4<br>
infrastructurewhich works. Those who wish, add additional infrastructure<br=
>
if necessary(IPv4, IPv6, etc.)<br>
</blockquote>
<br>
You change the DNS and add translators on that IPv4 network.<br>
<br></blockquote><div><br>I change DNS, I also change TCP. IPsec doesn&#39;=
t work, multicast is gone. But this is a trade-off: <br><br>We are now free=
 from core Internet&#39;s IP version decisions forever. This is the real di=
scussion that we should have here. Do we want this approach or not? Once we=
 decided that it is desirable, anything is designable. Because we do not de=
pend on core network anymore, we change the end points. This is the end-to-=
end principle. <br>
<br>Do we want to be free from this IP version problem forever? What can we=
 sacrifice to solve this problem?<br><br>=A0</div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,20=
4,204);padding-left:1ex">

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
We modify the end-hosts only<br>
</blockquote>
<br>
Your translators are not end-hosts.<br>
<br></blockquote><div><br>It is not a modification. People add them and rem=
ove them as they wish. It is not like modifying all Internet routers.<br><b=
r>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0pt 0pt 0pt 0.=
8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
We do not have worry about others&#39; IP version preferences, we do not ha=
ve to implement IPv6 for example<br>
</blockquote>
<br>
Your translators have to worry a lot about version preference.<br></blockqu=
ote><div><br>They are designed for that. And it is not big deal, they just =
copy payload. <br>=A0</div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex=
">

<br>
---<br>
<br>
Please read the Catenet paper.<br>
<br>
You are treating each IP version as a link layer, your translators are IP r=
outers, and your DNS works like ARP.<br>
<br>
Unfortunately, that doesn&#39;t remove the need for an end-to-end internetw=
orking layer with global addresses, which you don&#39;t have and don&#39;t =
address at all.<span class=3D"HOEnZb"><font color=3D"#888888"><br></font></=
span></blockquote>
<div><br>Let&#39;s first discuss what we want. We may have a host identific=
ation layer above IP for example but it is early to discuss technical detai=
ls. We do not even know what we want. <br>=A0</div><blockquote class=3D"gma=
il_quote" style=3D"margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,2=
04,204);padding-left:1ex">
<span class=3D"HOEnZb"><font color=3D"#888888">
<br>
Joe<br>
<br>
</font></span></blockquote></div><br>

--047d7b5d4c400c343a04c97a59e8--

From touch@isi.edu  Tue Sep 11 22:36:39 2012
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 502F221F853D for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 22:36:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.524
X-Spam-Level: 
X-Spam-Status: No, score=-102.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WPFQCK3t6GAv for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 22:36:38 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id C0BDD21F854C for <int-area@ietf.org>; Tue, 11 Sep 2012 22:36:33 -0700 (PDT)
Received: from [192.168.0.17] ([210.114.91.73]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id q8C5ZekQ002304 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 11 Sep 2012 22:35:51 -0700 (PDT)
Message-ID: <50501F2B.2040206@isi.edu>
Date: Tue, 11 Sep 2012 22:35:39 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Pars Mutaf <pars.mutaf@gmail.com>
References: <CACQuieaOfyC5pJ2MyHBRTZYWCYfZMp58Ujh8rn0-yBBQL+kkzg@mail.gmail.com> <FAD8796F-0B15-4197-B952-AEE7FD56EDED@isi.edu> <CACQuiebgTXDmUmaE2n1yAbt4vS+V0M60fjXujqtMrh2n1WhPgQ@mail.gmail.com> <504ECFD9.4090107@isi.edu> <CACQuieZZiotwm9RinsuBAfPt6df21Y_z6JJPg4KNTMND2+E5RA@mail.gmail.com> <987000F4-9B41-4A4F-BF0B-0A207882194B@lacnic.net> <CACQuiea5gMXjkAT_ywA13EO2+HhY0v_OwwB+4_H_nz-Ddd=MEg@mail.gmail.com> <0E3416E0-1F00-42C8-B867-DF8726D9AC26@lacnic.net> <CACQuieYuXPMNCteb_HNvGZrSmx3red7NPFmFbBE8cY9KT8LOQg@mail.gmail.com> <C83D6793-ED56-41ED-9892-2D51F3BA0851@lacnic.net> <CACQuieZc2s6EdDRJPO1LPBokKh5-jaboNs_M1w4BYqwJ80GK4g@mail.gmail.com> <CACQuieYSs0GP=nyx==x3-u61Ri8DCrcOhDP8e5tBH1xstyyzHQ@mail.gmail.com> <56839629-0B52-4DCC-B2C3-682AFC40D231@isi.edu> <CACQuiebwB4M_ASmFNW8X53-911vyc9AmOd=2KpJQMaD2rGVkHA@mail.gmail.com> <50501186.3060200@isi.edu> <CACQuieb1aGAqBYMqEmX2KYteSqp_g8G44hHm0FqQ6bQXMuWmgg@mail.gmail.com>
In-Reply-To: <CACQuieb1aGAqBYMqEmX2KYteSqp_g8G44hHm0FqQ6bQXMuWmgg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] Discrete IP
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Sep 2012 05:36:39 -0000

On 9/11/2012 10:20 PM, Pars Mutaf wrote:
...
>     Known problems, in no specific order:
>
>              a) like NAT, this fails for all protocols that use in-band
>              identifiers (e.g., FTP) unless the entire body of the packet
>              is translated too, and that might not be possible for some
>              services
>
> I don't understand. I just copy the whole payload. Or, replace the IPv4
> header with an IPv6 header. I don't have to know what's in the payload.

If the payload includes an IP address (take a look at how FTP works), 
then you have to translate that. That's how current NATs work for *many* 
protocols.

>              b) you fail to explain why this needs to happen for the
>              first packet and not all subsequent packets, or what to do
>              with subsequent packets (and what happens when the second
>              packet arrives - e.g., at the translator or elsewhere -
>              before the first one?)
>
> 1. I send the first packet to the copier. In the same message, I tell
> the destination IPv6 address that I learned using DNS for example. (this
> is not exactly a tunnel I don't have to speak IPv6)
> 3. The copier creates state for my IPv4 address and destination IPv6
> address.
> 4. Forwards packets in both directions

Why does the second packet not also need to be tunneled?

FWIW, what happens if the second packet shows up at the copier before 
the first one? Keep in mind that many protocols (including some variants 
of TCP) don't wait for an exchange to complete before sending the 
second, third, etc., packets.

>              c) the first packet won't be tunneled unless you upgrade
>              the source endpoint node to speak your new version of things;
>              if we could do that, everyone would be speaking IPv6
>
> Yes it is not a tunnel exactly. This is my bad. The first packet is a
> special packet, call it a Discrete IP packet, telling the copier the
> destination IPv6 address.

Is this from the DNS or the source?

And if this is a signalling packet, it's not a tunnel at all, FWIW.

>              d) what name/ID are you looking up in the DNS?
>              the node application already did a lookup for the
>              destination, and you now need to rewrite every application
>              to use your solution instead
>
> I assume a new host identifier, other than IP address.

Have you considered the implications of this assumption? Aren't you then 
assuming that this identifier *never changes* as you deploy new versions 
of IP, e.g.? Why do you think that will be true if it wasn't for IPv4?

>              (i.e., right now the DNS use is decoupled from network
>              packet processing; you want to integrate it - have you
>              seen Cheriton's I3 proposal along these lines?)
>
> I am not sure if it should be integrated.
>
>              e) which DNS do you register endpoints in? (answer: all of
>              them, except that you can't know where the ones outside your
>              "IP version" bubble are) so basically you're never going to
>              find the endpoints in other bubbles anyway
>
> You do not know what we can or cannot do yet. We didn't even discuss if
> we want my proposal.
> We attacked the details.

I do know that you need to register in every DNS or you won't find the 
name (or you need to tie the DNSes together - and if you do that, you 
provably already have a common internetworking layer, but you can't 
assume a common internetworking layer in your solution to provide one).

Until you prove otherwise.

Having a blank margin and a claim didn't work for Fermat, and it isn't 
sufficient here either.

>              f) which payload-only are you forwarding? the one in the
>              tunneled packet includes headers the next bubble doesn't
>              understand; if you strip off those headers, you lose a lot
>              of state
>
> No. The copier copies IPv4 payload to the IPv6 header that it creates
> itself.

OK, so that's just a NAT at that point.

>     Again, from your paper: "We do not need to use NATs anymore" only
>     because you don't call them that, but you're implementing a stateful
>     NAT as a translator.
>
> The question is not they are like NATs or not, we are changing the
> architecture. I can reuse yahoo's global IP address at home.
>
>     You claim:
>
>     ---
>
>         We do not touch the core network, i.e. the current IPv4
>         infrastructurewhich works. Those who wish, add additional
>         infrastructure
>         if necessary(IPv4, IPv6, etc.)
>
>
>     You change the DNS and add translators on that IPv4 network.
>
>
> I change DNS, I also change TCP.

DNS is part of the core of the network - at least it's in-network 
infrastructure, not an end service on the user's host.

> IPsec doesn't work, multicast is gone.

How do you restore those capabilities? Or will security not work here?

> But this is a trade-off:
>
> We are now free from core Internet's IP version decisions forever. This
> is the real discussion that we should have here. Do we want this
> approach or not? Once we decided that it is desirable, anything is
> designable. Because we do not depend on core network anymore, we change
> the end points. This is the end-to-end principle.
>
> Do we want to be free from this IP version problem forever? What can we
> sacrifice to solve this problem?
>
>         We modify the end-hosts only
>
>     Your translators are not end-hosts.
>
> It is not a modification. People add them and remove them as they wish.

If I remove them - all of them - then the system won't work. You need to 
have them for your solution.

> It is not like modifying all Internet routers.

It's a lot like installing new boxes that act a lot like routers, except 
that you refuse to call them routers and they're not nearly as robust or 
useful as routers.

>         We do not have worry about others' IP version preferences, we do
>         not have to implement IPv6 for example
>
>     Your translators have to worry a lot about version preference.
>
> They are designed for that. And it is not big deal, they just copy payload.
>
>     ---
>
>     Please read the Catenet paper.
>
>     You are treating each IP version as a link layer, your translators
>     are IP routers, and your DNS works like ARP.
>
>     Unfortunately, that doesn't remove the need for an end-to-end
>     internetworking layer with global addresses, which you don't have
>     and don't address at all.
>
> Let's first discuss what we want. We may have a host identification
> layer above IP for example but it is early to discuss technical details.

That's not a technical detail; that's the key to the solution. That IS 
what IP *is*. That's why shifting from IPv4 to IPv6 is hard.

> We do not even know what we want.

Then write a paper on the requirements. But you cannot expect to satisfy 
a want you *agree* we do not currently understand.

Joe

From pars.mutaf@gmail.com  Tue Sep 11 23:36:14 2012
Return-Path: <pars.mutaf@gmail.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1423121F84C2 for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 23:36:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.453
X-Spam-Level: 
X-Spam-Status: No, score=-3.453 tagged_above=-999 required=5 tests=[AWL=0.145,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uN3Bj5xHm-aC for <int-area@ietfa.amsl.com>; Tue, 11 Sep 2012 23:36:12 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 50BC021E8039 for <int-area@ietf.org>; Tue, 11 Sep 2012 23:36:12 -0700 (PDT)
Received: by vbbfc26 with SMTP id fc26so1855951vbb.31 for <int-area@ietf.org>; Tue, 11 Sep 2012 23:36:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Mnu3+qlRxHOFGqhmecyyYd6GA0cHWebrwfRyZqPHDL8=; b=DMP4BMTcftP+vJg/rsJ/N5gO0kOPsjMt8QQFstQsHOr8Y/eTKrj8YZH1K3Fd6+GABi bAeLPa5lhPHp4fV92LKcCdadOL5nTAk4d004EeTz72j9KJ82jW/5Xl3uklxdBjzw0RN+ QaObU53bd5rzh0i3P+8hxDoak6oMPJFoLq0OI0sMKUdlNZm/QFC4W2ffBnCiWUPmOWAx zb4AtHIND6eF0VS4pGfiXdjeZI/W+lwiBji0Nv+tFAGKbrPmXAg2BiFbHdO1txUNYf/X gxFjI6tk70t7jQr67Rd0qvDB0w8CCZi1njQiQKmuH3dOmw2+DiVV+TZuz7kFcm4TIAfc p+GQ==
MIME-Version: 1.0
Received: by 10.58.35.166 with SMTP id i6mr11164112vej.10.1347431767350; Tue, 11 Sep 2012 23:36:07 -0700 (PDT)
Received: by 10.58.213.101 with HTTP; Tue, 11 Sep 2012 23:36:07 -0700 (PDT)
In-Reply-To: <50501F2B.2040206@isi.edu>
References: <CACQuieaOfyC5pJ2MyHBRTZYWCYfZMp58Ujh8rn0-yBBQL+kkzg@mail.gmail.com> <FAD8796F-0B15-4197-B952-AEE7FD56EDED@isi.edu> <CACQuiebgTXDmUmaE2n1yAbt4vS+V0M60fjXujqtMrh2n1WhPgQ@mail.gmail.com> <504ECFD9.4090107@isi.edu> <CACQuieZZiotwm9RinsuBAfPt6df21Y_z6JJPg4KNTMND2+E5RA@mail.gmail.com> <987000F4-9B41-4A4F-BF0B-0A207882194B@lacnic.net> <CACQuiea5gMXjkAT_ywA13EO2+HhY0v_OwwB+4_H_nz-Ddd=MEg@mail.gmail.com> <0E3416E0-1F00-42C8-B867-DF8726D9AC26@lacnic.net> <CACQuieYuXPMNCteb_HNvGZrSmx3red7NPFmFbBE8cY9KT8LOQg@mail.gmail.com> <C83D6793-ED56-41ED-9892-2D51F3BA0851@lacnic.net> <CACQuieZc2s6EdDRJPO1LPBokKh5-jaboNs_M1w4BYqwJ80GK4g@mail.gmail.com> <CACQuieYSs0GP=nyx==x3-u61Ri8DCrcOhDP8e5tBH1xstyyzHQ@mail.gmail.com> <56839629-0B52-4DCC-B2C3-682AFC40D231@isi.edu> <CACQuiebwB4M_ASmFNW8X53-911vyc9AmOd=2KpJQMaD2rGVkHA@mail.gmail.com> <50501186.3060200@isi.edu> <CACQuieb1aGAqBYMqEmX2KYteSqp_g8G44hHm0FqQ6bQXMuWmgg@mail.gmail.com> <50501F2B.2040206@isi.edu>
Date: Wed, 12 Sep 2012 09:36:07 +0300
Message-ID: <CACQuieZYS1ykagcQpPB4kzm-aP2vEecvpeMQcBryCkRWRoY5eA@mail.gmail.com>
From: Pars Mutaf <pars.mutaf@gmail.com>
To: Joe Touch <touch@isi.edu>
Content-Type: multipart/alternative; boundary=047d7b5d4c40da1df704c97b6714
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] Discrete IP
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Sep 2012 06:36:14 -0000

--047d7b5d4c40da1df704c97b6714
Content-Type: text/plain; charset=ISO-8859-1

Hi Joe, all,

We really shouldn't enter in design questions before we understand what we
want. Please question everything you learned, even the research method.

As I see it, the following research style would be ideal:

-I propose that we do not touch the core Internet.
-People should be free to choose the IP version that they wish because
deciding for others is a technology blocker. IETF designs IPv6, IETF blocks
its development. Because IETF does not give freedom of choice. This is not
normal. Some entities may use IPv6 others IPv4 yet others IPv7 for unknown
reasons. Everybody may agree on IPv6, or not. We do not know. We do not
have to.
-To give such freedom of choice, we need to change the end-nodes.
-This is the end-to-end principle.

Here is a picture:
http://htmlimg3.scribdassets.com/2hdm1jwfcw1sxm1y/images/4-5930b39cea.jpg

Is this the model that we would prefer? Could we first answer this
question? Anything can be designed. The hard part of research is deciding
on the best solution.

Thanks,
Pars




On Wed, Sep 12, 2012 at 8:35 AM, Joe Touch <touch@isi.edu> wrote:

>
>
> On 9/11/2012 10:20 PM, Pars Mutaf wrote:
> ...
>
>>     Known problems, in no specific order:
>>
>>
>>              a) like NAT, this fails for all protocols that use in-band
>>              identifiers (e.g., FTP) unless the entire body of the packet
>>              is translated too, and that might not be possible for some
>>              services
>>
>> I don't understand. I just copy the whole payload. Or, replace the IPv4
>> header with an IPv6 header. I don't have to know what's in the payload.
>>
>
> If the payload includes an IP address (take a look at how FTP works), then
> you have to translate that. That's how current NATs work for *many*
> protocols.
>
>
>               b) you fail to explain why this needs to happen for the
>>              first packet and not all subsequent packets, or what to do
>>              with subsequent packets (and what happens when the second
>>              packet arrives - e.g., at the translator or elsewhere -
>>              before the first one?)
>>
>> 1. I send the first packet to the copier. In the same message, I tell
>> the destination IPv6 address that I learned using DNS for example. (this
>> is not exactly a tunnel I don't have to speak IPv6)
>> 3. The copier creates state for my IPv4 address and destination IPv6
>> address.
>> 4. Forwards packets in both directions
>>
>
> Why does the second packet not also need to be tunneled?
>
> FWIW, what happens if the second packet shows up at the copier before the
> first one? Keep in mind that many protocols (including some variants of
> TCP) don't wait for an exchange to complete before sending the second,
> third, etc., packets.
>
>
>               c) the first packet won't be tunneled unless you upgrade
>>              the source endpoint node to speak your new version of things;
>>              if we could do that, everyone would be speaking IPv6
>>
>> Yes it is not a tunnel exactly. This is my bad. The first packet is a
>> special packet, call it a Discrete IP packet, telling the copier the
>> destination IPv6 address.
>>
>
> Is this from the DNS or the source?
>
> And if this is a signalling packet, it's not a tunnel at all, FWIW.
>
>
>               d) what name/ID are you looking up in the DNS?
>>              the node application already did a lookup for the
>>              destination, and you now need to rewrite every application
>>              to use your solution instead
>>
>> I assume a new host identifier, other than IP address.
>>
>
> Have you considered the implications of this assumption? Aren't you then
> assuming that this identifier *never changes* as you deploy new versions of
> IP, e.g.? Why do you think that will be true if it wasn't for IPv4?
>
>
>               (i.e., right now the DNS use is decoupled from network
>>              packet processing; you want to integrate it - have you
>>              seen Cheriton's I3 proposal along these lines?)
>>
>> I am not sure if it should be integrated.
>>
>>              e) which DNS do you register endpoints in? (answer: all of
>>              them, except that you can't know where the ones outside your
>>              "IP version" bubble are) so basically you're never going to
>>              find the endpoints in other bubbles anyway
>>
>> You do not know what we can or cannot do yet. We didn't even discuss if
>> we want my proposal.
>> We attacked the details.
>>
>
> I do know that you need to register in every DNS or you won't find the
> name (or you need to tie the DNSes together - and if you do that, you
> provably already have a common internetworking layer, but you can't assume
> a common internetworking layer in your solution to provide one).
>
> Until you prove otherwise.
>
> Having a blank margin and a claim didn't work for Fermat, and it isn't
> sufficient here either.
>
>
>               f) which payload-only are you forwarding? the one in the
>>              tunneled packet includes headers the next bubble doesn't
>>              understand; if you strip off those headers, you lose a lot
>>              of state
>>
>> No. The copier copies IPv4 payload to the IPv6 header that it creates
>> itself.
>>
>
> OK, so that's just a NAT at that point.
>
>
>      Again, from your paper: "We do not need to use NATs anymore" only
>>     because you don't call them that, but you're implementing a stateful
>>     NAT as a translator.
>>
>> The question is not they are like NATs or not, we are changing the
>> architecture. I can reuse yahoo's global IP address at home.
>>
>>     You claim:
>>
>>     ---
>>
>>         We do not touch the core network, i.e. the current IPv4
>>         infrastructurewhich works. Those who wish, add additional
>>         infrastructure
>>         if necessary(IPv4, IPv6, etc.)
>>
>>
>>     You change the DNS and add translators on that IPv4 network.
>>
>>
>> I change DNS, I also change TCP.
>>
>
> DNS is part of the core of the network - at least it's in-network
> infrastructure, not an end service on the user's host.
>
>
>  IPsec doesn't work, multicast is gone.
>>
>
> How do you restore those capabilities? Or will security not work here?
>
>
>  But this is a trade-off:
>>
>> We are now free from core Internet's IP version decisions forever. This
>> is the real discussion that we should have here. Do we want this
>> approach or not? Once we decided that it is desirable, anything is
>> designable. Because we do not depend on core network anymore, we change
>> the end points. This is the end-to-end principle.
>>
>> Do we want to be free from this IP version problem forever? What can we
>> sacrifice to solve this problem?
>>
>>         We modify the end-hosts only
>>
>>     Your translators are not end-hosts.
>>
>> It is not a modification. People add them and remove them as they wish.
>>
>
> If I remove them - all of them - then the system won't work. You need to
> have them for your solution.
>
>
>  It is not like modifying all Internet routers.
>>
>
> It's a lot like installing new boxes that act a lot like routers, except
> that you refuse to call them routers and they're not nearly as robust or
> useful as routers.
>
>
>          We do not have worry about others' IP version preferences, we do
>>         not have to implement IPv6 for example
>>
>>     Your translators have to worry a lot about version preference.
>>
>> They are designed for that. And it is not big deal, they just copy
>> payload.
>>
>>     ---
>>
>>     Please read the Catenet paper.
>>
>>     You are treating each IP version as a link layer, your translators
>>     are IP routers, and your DNS works like ARP.
>>
>>     Unfortunately, that doesn't remove the need for an end-to-end
>>     internetworking layer with global addresses, which you don't have
>>     and don't address at all.
>>
>> Let's first discuss what we want. We may have a host identification
>> layer above IP for example but it is early to discuss technical details.
>>
>
> That's not a technical detail; that's the key to the solution. That IS
> what IP *is*. That's why shifting from IPv4 to IPv6 is hard.
>
>
>  We do not even know what we want.
>>
>
> Then write a paper on the requirements. But you cannot expect to satisfy a
> want you *agree* we do not currently understand.
>
> Joe
>

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

Hi Joe, all, <br><br>We really shouldn&#39;t enter in design questions befo=
re we understand what we want. Please question everything you learned, even=
 the research method. <br><br>As I see it, the following research style wou=
ld be ideal:<br>
<br>-I propose that we do not touch the core Internet.<br>-People should be=
 free to choose the IP version that they wish because deciding for others i=
s a technology blocker. IETF designs IPv6, IETF blocks its development. Bec=
ause IETF does not give freedom of choice. This is not normal. Some entitie=
s may use IPv6 others IPv4 yet others IPv7 for unknown reasons. Everybody m=
ay agree on IPv6, or not. We do not know. We do not have to.<br>
-To give such freedom of choice, we need to change the end-nodes.<br>-This =
is the end-to-end principle.<br><br>Here is a picture:<br><a href=3D"http:/=
/htmlimg3.scribdassets.com/2hdm1jwfcw1sxm1y/images/4-5930b39cea.jpg">http:/=
/htmlimg3.scribdassets.com/2hdm1jwfcw1sxm1y/images/4-5930b39cea.jpg</a><br>
<br>Is this the model that we would prefer? Could we first answer this ques=
tion? Anything can be designed. The hard part of research is deciding on th=
e best solution.<br><br>Thanks, <br>Pars<br><br><br><br><br><div class=3D"g=
mail_quote">
On Wed, Sep 12, 2012 at 8:35 AM, Joe Touch <span dir=3D"ltr">&lt;<a href=3D=
"mailto:touch@isi.edu" target=3D"_blank">touch@isi.edu</a>&gt;</span> wrote=
:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">
<div class=3D"im"><br>
<br>
On 9/11/2012 10:20 PM, Pars Mutaf wrote:<br>
...<br>
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">
=A0 =A0 Known problems, in no specific order:<div class=3D"im"><br>
<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0a) like NAT, this fails for all protocols that u=
se in-band<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0identifiers (e.g., FTP) unless the entire body o=
f the packet<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0is translated too, and that might not be possibl=
e for some<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0services<br>
<br>
I don&#39;t understand. I just copy the whole payload. Or, replace the IPv4=
<br>
header with an IPv6 header. I don&#39;t have to know what&#39;s in the payl=
oad.<br>
</div></blockquote>
<br>
If the payload includes an IP address (take a look at how FTP works), then =
you have to translate that. That&#39;s how current NATs work for *many* pro=
tocols.<div class=3D"im"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=A0 =A0 =A0 =A0 =A0 =A0 =A0b) you fail to explain why this needs to happen =
for the<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0first packet and not all subsequent packets, or =
what to do<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0with subsequent packets (and what happens when t=
he second<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0packet arrives - e.g., at the translator or else=
where -<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0before the first one?)<br>
<br>
1. I send the first packet to the copier. In the same message, I tell<br>
the destination IPv6 address that I learned using DNS for example. (this<br=
>
is not exactly a tunnel I don&#39;t have to speak IPv6)<br>
3. The copier creates state for my IPv4 address and destination IPv6<br>
address.<br>
4. Forwards packets in both directions<br>
</blockquote>
<br></div>
Why does the second packet not also need to be tunneled?<br>
<br>
FWIW, what happens if the second packet shows up at the copier before the f=
irst one? Keep in mind that many protocols (including some variants of TCP)=
 don&#39;t wait for an exchange to complete before sending the second, thir=
d, etc., packets.<div class=3D"im">
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=A0 =A0 =A0 =A0 =A0 =A0 =A0c) the first packet won&#39;t be tunneled unless=
 you upgrade<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0the source endpoint node to speak your new versi=
on of things;<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0if we could do that, everyone would be speaking =
IPv6<br>
<br>
Yes it is not a tunnel exactly. This is my bad. The first packet is a<br>
special packet, call it a Discrete IP packet, telling the copier the<br>
destination IPv6 address.<br>
</blockquote>
<br></div>
Is this from the DNS or the source?<br>
<br>
And if this is a signalling packet, it&#39;s not a tunnel at all, FWIW.<div=
 class=3D"im"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=A0 =A0 =A0 =A0 =A0 =A0 =A0d) what name/ID are you looking up in the DNS?<b=
r>
=A0 =A0 =A0 =A0 =A0 =A0 =A0the node application already did a lookup for th=
e<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0destination, and you now need to rewrite every a=
pplication<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0to use your solution instead<br>
<br>
I assume a new host identifier, other than IP address.<br>
</blockquote>
<br></div>
Have you considered the implications of this assumption? Aren&#39;t you the=
n assuming that this identifier *never changes* as you deploy new versions =
of IP, e.g.? Why do you think that will be true if it wasn&#39;t for IPv4?<=
div class=3D"im">
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=A0 =A0 =A0 =A0 =A0 =A0 =A0(i.e., right now the DNS use is decoupled from n=
etwork<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0packet processing; you want to integrate it - ha=
ve you<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0seen Cheriton&#39;s I3 proposal along these line=
s?)<br>
<br>
I am not sure if it should be integrated.<br>
<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0e) which DNS do you register endpoints in? (answ=
er: all of<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0them, except that you can&#39;t know where the o=
nes outside your<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0&quot;IP version&quot; bubble are) so basically =
you&#39;re never going to<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0find the endpoints in other bubbles anyway<br>
<br>
You do not know what we can or cannot do yet. We didn&#39;t even discuss if=
<br>
we want my proposal.<br>
We attacked the details.<br>
</blockquote>
<br></div>
I do know that you need to register in every DNS or you won&#39;t find the =
name (or you need to tie the DNSes together - and if you do that, you prova=
bly already have a common internetworking layer, but you can&#39;t assume a=
 common internetworking layer in your solution to provide one).<br>

<br>
Until you prove otherwise.<br>
<br>
Having a blank margin and a claim didn&#39;t work for Fermat, and it isn&#3=
9;t sufficient here either.<div class=3D"im"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=A0 =A0 =A0 =A0 =A0 =A0 =A0f) which payload-only are you forwarding? the on=
e in the<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0tunneled packet includes headers the next bubble=
 doesn&#39;t<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0understand; if you strip off those headers, you =
lose a lot<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0of state<br>
<br>
No. The copier copies IPv4 payload to the IPv6 header that it creates<br>
itself.<br>
</blockquote>
<br></div>
OK, so that&#39;s just a NAT at that point.<div class=3D"im"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=A0 =A0 Again, from your paper: &quot;We do not need to use NATs anymore&qu=
ot; only<br>
=A0 =A0 because you don&#39;t call them that, but you&#39;re implementing a=
 stateful<br>
=A0 =A0 NAT as a translator.<br>
<br>
The question is not they are like NATs or not, we are changing the<br>
architecture. I can reuse yahoo&#39;s global IP address at home.<br>
<br>
=A0 =A0 You claim:<br>
<br>
=A0 =A0 ---<br>
<br>
=A0 =A0 =A0 =A0 We do not touch the core network, i.e. the current IPv4<br>
=A0 =A0 =A0 =A0 infrastructurewhich works. Those who wish, add additional<b=
r>
=A0 =A0 =A0 =A0 infrastructure<br>
=A0 =A0 =A0 =A0 if necessary(IPv4, IPv6, etc.)<br>
<br>
<br>
=A0 =A0 You change the DNS and add translators on that IPv4 network.<br>
<br>
<br>
I change DNS, I also change TCP.<br>
</blockquote>
<br></div>
DNS is part of the core of the network - at least it&#39;s in-network infra=
structure, not an end service on the user&#39;s host.<div class=3D"im"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
IPsec doesn&#39;t work, multicast is gone.<br>
</blockquote>
<br></div>
How do you restore those capabilities? Or will security not work here?<div =
class=3D"im"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
But this is a trade-off:<br>
<br>
We are now free from core Internet&#39;s IP version decisions forever. This=
<br>
is the real discussion that we should have here. Do we want this<br>
approach or not? Once we decided that it is desirable, anything is<br>
designable. Because we do not depend on core network anymore, we change<br>
the end points. This is the end-to-end principle.<br>
<br>
Do we want to be free from this IP version problem forever? What can we<br>
sacrifice to solve this problem?<br>
<br>
=A0 =A0 =A0 =A0 We modify the end-hosts only<br>
<br>
=A0 =A0 Your translators are not end-hosts.<br>
<br>
It is not a modification. People add them and remove them as they wish.<br>
</blockquote>
<br></div>
If I remove them - all of them - then the system won&#39;t work. You need t=
o have them for your solution.<div class=3D"im"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
It is not like modifying all Internet routers.<br>
</blockquote>
<br></div>
It&#39;s a lot like installing new boxes that act a lot like routers, excep=
t that you refuse to call them routers and they&#39;re not nearly as robust=
 or useful as routers.<div class=3D"im"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=A0 =A0 =A0 =A0 We do not have worry about others&#39; IP version preferenc=
es, we do<br>
=A0 =A0 =A0 =A0 not have to implement IPv6 for example<br>
<br>
=A0 =A0 Your translators have to worry a lot about version preference.<br>
<br>
They are designed for that. And it is not big deal, they just copy payload.=
<br>
<br>
=A0 =A0 ---<br>
<br>
=A0 =A0 Please read the Catenet paper.<br>
<br>
=A0 =A0 You are treating each IP version as a link layer, your translators<=
br>
=A0 =A0 are IP routers, and your DNS works like ARP.<br>
<br>
=A0 =A0 Unfortunately, that doesn&#39;t remove the need for an end-to-end<b=
r>
=A0 =A0 internetworking layer with global addresses, which you don&#39;t ha=
ve<br>
=A0 =A0 and don&#39;t address at all.<br>
<br>
Let&#39;s first discuss what we want. We may have a host identification<br>
layer above IP for example but it is early to discuss technical details.<br=
>
</blockquote>
<br></div>
That&#39;s not a technical detail; that&#39;s the key to the solution. That=
 IS what IP *is*. That&#39;s why shifting from IPv4 to IPv6 is hard.<div cl=
ass=3D"im"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
We do not even know what we want.<br>
</blockquote>
<br></div>
Then write a paper on the requirements. But you cannot expect to satisfy a =
want you *agree* we do not currently understand.<span class=3D"HOEnZb"><fon=
t color=3D"#888888"><br>
<br>
Joe<br>
</font></span></blockquote></div><br>

--047d7b5d4c40da1df704c97b6714--

From touch@isi.edu  Wed Sep 12 00:10:58 2012
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 055C621E805E for <int-area@ietfa.amsl.com>; Wed, 12 Sep 2012 00:10:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.539
X-Spam-Level: 
X-Spam-Status: No, score=-102.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hsSHf+5WuiRa for <int-area@ietfa.amsl.com>; Wed, 12 Sep 2012 00:10:57 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id D92F321E8064 for <int-area@ietf.org>; Wed, 12 Sep 2012 00:10:56 -0700 (PDT)
Received: from [192.168.0.17] ([210.114.91.73]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id q8C7AXid020577 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 12 Sep 2012 00:10:37 -0700 (PDT)
Message-ID: <50503568.5050503@isi.edu>
Date: Wed, 12 Sep 2012 00:10:32 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Pars Mutaf <pars.mutaf@gmail.com>
References: <CACQuieaOfyC5pJ2MyHBRTZYWCYfZMp58Ujh8rn0-yBBQL+kkzg@mail.gmail.com> <CACQuiebgTXDmUmaE2n1yAbt4vS+V0M60fjXujqtMrh2n1WhPgQ@mail.gmail.com> <504ECFD9.4090107@isi.edu> <CACQuieZZiotwm9RinsuBAfPt6df21Y_z6JJPg4KNTMND2+E5RA@mail.gmail.com> <987000F4-9B41-4A4F-BF0B-0A207882194B@lacnic.net> <CACQuiea5gMXjkAT_ywA13EO2+HhY0v_OwwB+4_H_nz-Ddd=MEg@mail.gmail.com> <0E3416E0-1F00-42C8-B867-DF8726D9AC26@lacnic.net> <CACQuieYuXPMNCteb_HNvGZrSmx3red7NPFmFbBE8cY9KT8LOQg@mail.gmail.com> <C83D6793-ED56-41ED-9892-2D51F3BA0851@lacnic.net> <CACQuieZc2s6EdDRJPO1LPBokKh5-jaboNs_M1w4BYqwJ80GK4g@mail.gmail.com> <CACQuieYSs0GP=nyx==x3-u61Ri8DCrcOhDP8e5tBH1xstyyzHQ@mail.gmail.com> <56839629-0B52-4DCC-B2C3-682AFC40D231@isi.edu> <CACQuiebwB4M_ASmFNW8X53-911vyc9AmOd=2KpJQMaD2rGVkHA@mail.gmail.com> <50501186.3060200@isi.edu> <CACQuieb1aGAqBYMqEmX2KYteSqp_g8G44hHm0FqQ6bQXMuWmgg@mail.gmail.com> <50501F2B.2040206@isi.edu> <CACQuieZYS1ykagcQpPB4kzm-aP2vEecvpeMQcBryCkRWRoY5eA@mail.gmail.com>
In-Reply-To: <CACQuieZYS1ykagcQpPB4kzm-aP2vEecvpeMQcBryCkRWRoY5eA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] Discrete IP
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Sep 2012 07:10:58 -0000

Hi, Pars,

On 9/11/2012 11:36 PM, Pars Mutaf wrote:
> Hi Joe, all,
>
> We really shouldn't enter in design questions before we understand what
> we want.

Sure. However, INT-AREA isn't the place for this sort of discussion. You 
might consider trying at end2end-interest@postel.org, which is the 
typical place where end-to-end discussions on architecture are first made.

The IETF is a place for engineering solutions, not research. The IRTF 
serves that purpose, and the above list is the original IRTF list for 
these sorts of discussions.

You (and others) are welcome to take this discussion there, but I expect 
the thread has lost its usefulness to the INTAREA WG.

Joe

> Please question everything you learned, even the research method.
>
> As I see it, the following research style would be ideal:
>
> -I propose that we do not touch the core Internet.
> -People should be free to choose the IP version that they wish because
> deciding for others is a technology blocker. IETF designs IPv6, IETF
> blocks its development. Because IETF does not give freedom of choice.
> This is not normal. Some entities may use IPv6 others IPv4 yet others
> IPv7 for unknown reasons. Everybody may agree on IPv6, or not. We do not
> know. We do not have to.
> -To give such freedom of choice, we need to change the end-nodes.
> -This is the end-to-end principle.
>
> Here is a picture:
> http://htmlimg3.scribdassets.com/2hdm1jwfcw1sxm1y/images/4-5930b39cea.jpg
>
> Is this the model that we would prefer? Could we first answer this
> question? Anything can be designed. The hard part of research is
> deciding on the best solution.
>
> Thanks,
> Pars
>
>
>
>
> On Wed, Sep 12, 2012 at 8:35 AM, Joe Touch <touch@isi.edu
> <mailto:touch@isi.edu>> wrote:
>
>
>
>     On 9/11/2012 10:20 PM, Pars Mutaf wrote:
>     ...
>
>              Known problems, in no specific order:
>
>
>                       a) like NAT, this fails for all protocols that use
>         in-band
>                       identifiers (e.g., FTP) unless the entire body of
>         the packet
>                       is translated too, and that might not be possible
>         for some
>                       services
>
>         I don't understand. I just copy the whole payload. Or, replace
>         the IPv4
>         header with an IPv6 header. I don't have to know what's in the
>         payload.
>
>
>     If the payload includes an IP address (take a look at how FTP
>     works), then you have to translate that. That's how current NATs
>     work for *many* protocols.
>
>
>                       b) you fail to explain why this needs to happen
>         for the
>                       first packet and not all subsequent packets, or
>         what to do
>                       with subsequent packets (and what happens when the
>         second
>                       packet arrives - e.g., at the translator or
>         elsewhere -
>                       before the first one?)
>
>         1. I send the first packet to the copier. In the same message, I
>         tell
>         the destination IPv6 address that I learned using DNS for
>         example. (this
>         is not exactly a tunnel I don't have to speak IPv6)
>         3. The copier creates state for my IPv4 address and destination IPv6
>         address.
>         4. Forwards packets in both directions
>
>
>     Why does the second packet not also need to be tunneled?
>
>     FWIW, what happens if the second packet shows up at the copier
>     before the first one? Keep in mind that many protocols (including
>     some variants of TCP) don't wait for an exchange to complete before
>     sending the second, third, etc., packets.
>
>
>                       c) the first packet won't be tunneled unless you
>         upgrade
>                       the source endpoint node to speak your new version
>         of things;
>                       if we could do that, everyone would be speaking IPv6
>
>         Yes it is not a tunnel exactly. This is my bad. The first packet
>         is a
>         special packet, call it a Discrete IP packet, telling the copier the
>         destination IPv6 address.
>
>
>     Is this from the DNS or the source?
>
>     And if this is a signalling packet, it's not a tunnel at all, FWIW.
>
>
>                       d) what name/ID are you looking up in the DNS?
>                       the node application already did a lookup for the
>                       destination, and you now need to rewrite every
>         application
>                       to use your solution instead
>
>         I assume a new host identifier, other than IP address.
>
>
>     Have you considered the implications of this assumption? Aren't you
>     then assuming that this identifier *never changes* as you deploy new
>     versions of IP, e.g.? Why do you think that will be true if it
>     wasn't for IPv4?
>
>
>                       (i.e., right now the DNS use is decoupled from network
>                       packet processing; you want to integrate it - have you
>                       seen Cheriton's I3 proposal along these lines?)
>
>         I am not sure if it should be integrated.
>
>                       e) which DNS do you register endpoints in?
>         (answer: all of
>                       them, except that you can't know where the ones
>         outside your
>                       "IP version" bubble are) so basically you're never
>         going to
>                       find the endpoints in other bubbles anyway
>
>         You do not know what we can or cannot do yet. We didn't even
>         discuss if
>         we want my proposal.
>         We attacked the details.
>
>
>     I do know that you need to register in every DNS or you won't find
>     the name (or you need to tie the DNSes together - and if you do
>     that, you provably already have a common internetworking layer, but
>     you can't assume a common internetworking layer in your solution to
>     provide one).
>
>     Until you prove otherwise.
>
>     Having a blank margin and a claim didn't work for Fermat, and it
>     isn't sufficient here either.
>
>
>                       f) which payload-only are you forwarding? the one
>         in the
>                       tunneled packet includes headers the next bubble
>         doesn't
>                       understand; if you strip off those headers, you
>         lose a lot
>                       of state
>
>         No. The copier copies IPv4 payload to the IPv6 header that it
>         creates
>         itself.
>
>
>     OK, so that's just a NAT at that point.
>
>
>              Again, from your paper: "We do not need to use NATs
>         anymore" only
>              because you don't call them that, but you're implementing a
>         stateful
>              NAT as a translator.
>
>         The question is not they are like NATs or not, we are changing the
>         architecture. I can reuse yahoo's global IP address at home.
>
>              You claim:
>
>              ---
>
>                  We do not touch the core network, i.e. the current IPv4
>                  infrastructurewhich works. Those who wish, add additional
>                  infrastructure
>                  if necessary(IPv4, IPv6, etc.)
>
>
>              You change the DNS and add translators on that IPv4 network.
>
>
>         I change DNS, I also change TCP.
>
>
>     DNS is part of the core of the network - at least it's in-network
>     infrastructure, not an end service on the user's host.
>
>
>         IPsec doesn't work, multicast is gone.
>
>
>     How do you restore those capabilities? Or will security not work here?
>
>
>         But this is a trade-off:
>
>         We are now free from core Internet's IP version decisions
>         forever. This
>         is the real discussion that we should have here. Do we want this
>         approach or not? Once we decided that it is desirable, anything is
>         designable. Because we do not depend on core network anymore, we
>         change
>         the end points. This is the end-to-end principle.
>
>         Do we want to be free from this IP version problem forever? What
>         can we
>         sacrifice to solve this problem?
>
>                  We modify the end-hosts only
>
>              Your translators are not end-hosts.
>
>         It is not a modification. People add them and remove them as
>         they wish.
>
>
>     If I remove them - all of them - then the system won't work. You
>     need to have them for your solution.
>
>
>         It is not like modifying all Internet routers.
>
>
>     It's a lot like installing new boxes that act a lot like routers,
>     except that you refuse to call them routers and they're not nearly
>     as robust or useful as routers.
>
>
>                  We do not have worry about others' IP version
>         preferences, we do
>                  not have to implement IPv6 for example
>
>              Your translators have to worry a lot about version preference.
>
>         They are designed for that. And it is not big deal, they just
>         copy payload.
>
>              ---
>
>              Please read the Catenet paper.
>
>              You are treating each IP version as a link layer, your
>         translators
>              are IP routers, and your DNS works like ARP.
>
>              Unfortunately, that doesn't remove the need for an end-to-end
>              internetworking layer with global addresses, which you
>         don't have
>              and don't address at all.
>
>         Let's first discuss what we want. We may have a host identification
>         layer above IP for example but it is early to discuss technical
>         details.
>
>
>     That's not a technical detail; that's the key to the solution. That
>     IS what IP *is*. That's why shifting from IPv4 to IPv6 is hard.
>
>
>         We do not even know what we want.
>
>
>     Then write a paper on the requirements. But you cannot expect to
>     satisfy a want you *agree* we do not currently understand.
>
>     Joe
>
>

From pars.mutaf@gmail.com  Wed Sep 12 00:33:00 2012
Return-Path: <pars.mutaf@gmail.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8537021F85A7 for <int-area@ietfa.amsl.com>; Wed, 12 Sep 2012 00:33:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.465
X-Spam-Level: 
X-Spam-Status: No, score=-3.465 tagged_above=-999 required=5 tests=[AWL=0.133,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id inmvnQr-NN48 for <int-area@ietfa.amsl.com>; Wed, 12 Sep 2012 00:32:59 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id B8A7521F85A4 for <int-area@ietf.org>; Wed, 12 Sep 2012 00:32:58 -0700 (PDT)
Received: by vbbfc26 with SMTP id fc26so1910233vbb.31 for <int-area@ietf.org>; Wed, 12 Sep 2012 00:32:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=YM6gM4uKgK6tJh/RcqQsCbKUypVQWrLyDJlWmI9XMM4=; b=wNTzKu6amMngRUMi2g4bFhxe958UAc5KGwpRoCAX+4JVCarLNIm+6hf+DyUT465oOH KcFkVtrVtaFE3gHMJbcOThWtMIHCT+9AXB+nnyjeavEEKIkzRH58yE/hnDf4pfs+sS8v i0Z7WyVyH3o7KEDImY4fWltU5aCty4kIGXBM+C8IQUH0+J50jnmwRObNgDQzToNbsKBE nxqZ70HodlxpsI6AePgUZut0bw3An/+WIhwbX3Ucdp5a5ZOz12hC9/rEuiGXDbj99rJ0 VsxjBED5soBFyaxJJ9qevLGeR5fCNe38+idUpHSFglPjVrUJv679GEPQvZSNLKmwAec5 smCg==
MIME-Version: 1.0
Received: by 10.220.214.208 with SMTP id hb16mr28060793vcb.56.1347435178094; Wed, 12 Sep 2012 00:32:58 -0700 (PDT)
Received: by 10.58.213.101 with HTTP; Wed, 12 Sep 2012 00:32:57 -0700 (PDT)
In-Reply-To: <50503568.5050503@isi.edu>
References: <CACQuieaOfyC5pJ2MyHBRTZYWCYfZMp58Ujh8rn0-yBBQL+kkzg@mail.gmail.com> <CACQuiebgTXDmUmaE2n1yAbt4vS+V0M60fjXujqtMrh2n1WhPgQ@mail.gmail.com> <504ECFD9.4090107@isi.edu> <CACQuieZZiotwm9RinsuBAfPt6df21Y_z6JJPg4KNTMND2+E5RA@mail.gmail.com> <987000F4-9B41-4A4F-BF0B-0A207882194B@lacnic.net> <CACQuiea5gMXjkAT_ywA13EO2+HhY0v_OwwB+4_H_nz-Ddd=MEg@mail.gmail.com> <0E3416E0-1F00-42C8-B867-DF8726D9AC26@lacnic.net> <CACQuieYuXPMNCteb_HNvGZrSmx3red7NPFmFbBE8cY9KT8LOQg@mail.gmail.com> <C83D6793-ED56-41ED-9892-2D51F3BA0851@lacnic.net> <CACQuieZc2s6EdDRJPO1LPBokKh5-jaboNs_M1w4BYqwJ80GK4g@mail.gmail.com> <CACQuieYSs0GP=nyx==x3-u61Ri8DCrcOhDP8e5tBH1xstyyzHQ@mail.gmail.com> <56839629-0B52-4DCC-B2C3-682AFC40D231@isi.edu> <CACQuiebwB4M_ASmFNW8X53-911vyc9AmOd=2KpJQMaD2rGVkHA@mail.gmail.com> <50501186.3060200@isi.edu> <CACQuieb1aGAqBYMqEmX2KYteSqp_g8G44hHm0FqQ6bQXMuWmgg@mail.gmail.com> <50501F2B.2040206@isi.edu> <CACQuieZYS1ykagcQpPB4kzm-aP2vEecvpeMQcBryCkRWRoY5eA@mail.gmail.com> <50503568.5050503@isi.edu>
Date: Wed, 12 Sep 2012 10:32:57 +0300
Message-ID: <CACQuieYuWf8ntqxiTjgP3PncgiJkrrt4PsAo0naoOMJye0H4Fw@mail.gmail.com>
From: Pars Mutaf <pars.mutaf@gmail.com>
To: Joe Touch <touch@isi.edu>
Content-Type: multipart/alternative; boundary=bcaec54ee63825eff704c97c33ee
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] Discrete IP
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Sep 2012 07:33:00 -0000

--bcaec54ee63825eff704c97c33ee
Content-Type: text/plain; charset=ISO-8859-1

OK. See you there.
Cheers,
Pars

On Wed, Sep 12, 2012 at 10:10 AM, Joe Touch <touch@isi.edu> wrote:

> Hi, Pars,
>
>
> On 9/11/2012 11:36 PM, Pars Mutaf wrote:
>
>> Hi Joe, all,
>>
>> We really shouldn't enter in design questions before we understand what
>> we want.
>>
>
> Sure. However, INT-AREA isn't the place for this sort of discussion. You
> might consider trying at end2end-interest@postel.org, which is the
> typical place where end-to-end discussions on architecture are first made.
>
> The IETF is a place for engineering solutions, not research. The IRTF
> serves that purpose, and the above list is the original IRTF list for these
> sorts of discussions.
>
> You (and others) are welcome to take this discussion there, but I expect
> the thread has lost its usefulness to the INTAREA WG.
>
> Joe
>
>  Please question everything you learned, even the research method.
>>
>> As I see it, the following research style would be ideal:
>>
>> -I propose that we do not touch the core Internet.
>> -People should be free to choose the IP version that they wish because
>> deciding for others is a technology blocker. IETF designs IPv6, IETF
>> blocks its development. Because IETF does not give freedom of choice.
>> This is not normal. Some entities may use IPv6 others IPv4 yet others
>> IPv7 for unknown reasons. Everybody may agree on IPv6, or not. We do not
>> know. We do not have to.
>> -To give such freedom of choice, we need to change the end-nodes.
>> -This is the end-to-end principle.
>>
>> Here is a picture:
>> http://htmlimg3.scribdassets.**com/2hdm1jwfcw1sxm1y/images/4-**
>> 5930b39cea.jpg<http://htmlimg3.scribdassets.com/2hdm1jwfcw1sxm1y/images/4-5930b39cea.jpg>
>>
>> Is this the model that we would prefer? Could we first answer this
>> question? Anything can be designed. The hard part of research is
>> deciding on the best solution.
>>
>> Thanks,
>> Pars
>>
>>
>>
>>
>> On Wed, Sep 12, 2012 at 8:35 AM, Joe Touch <touch@isi.edu
>> <mailto:touch@isi.edu>> wrote:
>>
>>
>>
>>     On 9/11/2012 10:20 PM, Pars Mutaf wrote:
>>     ...
>>
>>              Known problems, in no specific order:
>>
>>
>>                       a) like NAT, this fails for all protocols that use
>>         in-band
>>                       identifiers (e.g., FTP) unless the entire body of
>>         the packet
>>                       is translated too, and that might not be possible
>>         for some
>>                       services
>>
>>         I don't understand. I just copy the whole payload. Or, replace
>>         the IPv4
>>         header with an IPv6 header. I don't have to know what's in the
>>         payload.
>>
>>
>>     If the payload includes an IP address (take a look at how FTP
>>     works), then you have to translate that. That's how current NATs
>>     work for *many* protocols.
>>
>>
>>                       b) you fail to explain why this needs to happen
>>         for the
>>                       first packet and not all subsequent packets, or
>>         what to do
>>                       with subsequent packets (and what happens when the
>>         second
>>                       packet arrives - e.g., at the translator or
>>         elsewhere -
>>                       before the first one?)
>>
>>         1. I send the first packet to the copier. In the same message, I
>>         tell
>>         the destination IPv6 address that I learned using DNS for
>>         example. (this
>>         is not exactly a tunnel I don't have to speak IPv6)
>>         3. The copier creates state for my IPv4 address and destination
>> IPv6
>>         address.
>>         4. Forwards packets in both directions
>>
>>
>>     Why does the second packet not also need to be tunneled?
>>
>>     FWIW, what happens if the second packet shows up at the copier
>>     before the first one? Keep in mind that many protocols (including
>>     some variants of TCP) don't wait for an exchange to complete before
>>     sending the second, third, etc., packets.
>>
>>
>>                       c) the first packet won't be tunneled unless you
>>         upgrade
>>                       the source endpoint node to speak your new version
>>         of things;
>>                       if we could do that, everyone would be speaking IPv6
>>
>>         Yes it is not a tunnel exactly. This is my bad. The first packet
>>         is a
>>         special packet, call it a Discrete IP packet, telling the copier
>> the
>>         destination IPv6 address.
>>
>>
>>     Is this from the DNS or the source?
>>
>>     And if this is a signalling packet, it's not a tunnel at all, FWIW.
>>
>>
>>                       d) what name/ID are you looking up in the DNS?
>>                       the node application already did a lookup for the
>>                       destination, and you now need to rewrite every
>>         application
>>                       to use your solution instead
>>
>>         I assume a new host identifier, other than IP address.
>>
>>
>>     Have you considered the implications of this assumption? Aren't you
>>     then assuming that this identifier *never changes* as you deploy new
>>     versions of IP, e.g.? Why do you think that will be true if it
>>     wasn't for IPv4?
>>
>>
>>                       (i.e., right now the DNS use is decoupled from
>> network
>>                       packet processing; you want to integrate it - have
>> you
>>                       seen Cheriton's I3 proposal along these lines?)
>>
>>         I am not sure if it should be integrated.
>>
>>                       e) which DNS do you register endpoints in?
>>         (answer: all of
>>                       them, except that you can't know where the ones
>>         outside your
>>                       "IP version" bubble are) so basically you're never
>>         going to
>>                       find the endpoints in other bubbles anyway
>>
>>         You do not know what we can or cannot do yet. We didn't even
>>         discuss if
>>         we want my proposal.
>>         We attacked the details.
>>
>>
>>     I do know that you need to register in every DNS or you won't find
>>     the name (or you need to tie the DNSes together - and if you do
>>     that, you provably already have a common internetworking layer, but
>>     you can't assume a common internetworking layer in your solution to
>>     provide one).
>>
>>     Until you prove otherwise.
>>
>>     Having a blank margin and a claim didn't work for Fermat, and it
>>     isn't sufficient here either.
>>
>>
>>                       f) which payload-only are you forwarding? the one
>>         in the
>>                       tunneled packet includes headers the next bubble
>>         doesn't
>>                       understand; if you strip off those headers, you
>>         lose a lot
>>                       of state
>>
>>         No. The copier copies IPv4 payload to the IPv6 header that it
>>         creates
>>         itself.
>>
>>
>>     OK, so that's just a NAT at that point.
>>
>>
>>              Again, from your paper: "We do not need to use NATs
>>         anymore" only
>>              because you don't call them that, but you're implementing a
>>         stateful
>>              NAT as a translator.
>>
>>         The question is not they are like NATs or not, we are changing the
>>         architecture. I can reuse yahoo's global IP address at home.
>>
>>              You claim:
>>
>>              ---
>>
>>                  We do not touch the core network, i.e. the current IPv4
>>                  infrastructurewhich works. Those who wish, add additional
>>                  infrastructure
>>                  if necessary(IPv4, IPv6, etc.)
>>
>>
>>              You change the DNS and add translators on that IPv4 network.
>>
>>
>>         I change DNS, I also change TCP.
>>
>>
>>     DNS is part of the core of the network - at least it's in-network
>>     infrastructure, not an end service on the user's host.
>>
>>
>>         IPsec doesn't work, multicast is gone.
>>
>>
>>     How do you restore those capabilities? Or will security not work here?
>>
>>
>>         But this is a trade-off:
>>
>>         We are now free from core Internet's IP version decisions
>>         forever. This
>>         is the real discussion that we should have here. Do we want this
>>         approach or not? Once we decided that it is desirable, anything is
>>         designable. Because we do not depend on core network anymore, we
>>         change
>>         the end points. This is the end-to-end principle.
>>
>>         Do we want to be free from this IP version problem forever? What
>>         can we
>>         sacrifice to solve this problem?
>>
>>                  We modify the end-hosts only
>>
>>              Your translators are not end-hosts.
>>
>>         It is not a modification. People add them and remove them as
>>         they wish.
>>
>>
>>     If I remove them - all of them - then the system won't work. You
>>     need to have them for your solution.
>>
>>
>>         It is not like modifying all Internet routers.
>>
>>
>>     It's a lot like installing new boxes that act a lot like routers,
>>     except that you refuse to call them routers and they're not nearly
>>     as robust or useful as routers.
>>
>>
>>                  We do not have worry about others' IP version
>>         preferences, we do
>>                  not have to implement IPv6 for example
>>
>>              Your translators have to worry a lot about version
>> preference.
>>
>>         They are designed for that. And it is not big deal, they just
>>         copy payload.
>>
>>              ---
>>
>>              Please read the Catenet paper.
>>
>>              You are treating each IP version as a link layer, your
>>         translators
>>              are IP routers, and your DNS works like ARP.
>>
>>              Unfortunately, that doesn't remove the need for an end-to-end
>>              internetworking layer with global addresses, which you
>>         don't have
>>              and don't address at all.
>>
>>         Let's first discuss what we want. We may have a host
>> identification
>>         layer above IP for example but it is early to discuss technical
>>         details.
>>
>>
>>     That's not a technical detail; that's the key to the solution. That
>>     IS what IP *is*. That's why shifting from IPv4 to IPv6 is hard.
>>
>>
>>         We do not even know what we want.
>>
>>
>>     Then write a paper on the requirements. But you cannot expect to
>>     satisfy a want you *agree* we do not currently understand.
>>
>>     Joe
>>
>>
>>

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

OK. See you there. <br>Cheers,<br>Pars<br><br><div class=3D"gmail_quote">On=
 Wed, Sep 12, 2012 at 10:10 AM, Joe Touch <span dir=3D"ltr">&lt;<a href=3D"=
mailto:touch@isi.edu" target=3D"_blank">touch@isi.edu</a>&gt;</span> wrote:=
<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex">
Hi, Pars,<div class=3D"im"><br>
<br>
On 9/11/2012 11:36 PM, Pars Mutaf wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Hi Joe, all,<br>
<br>
We really shouldn&#39;t enter in design questions before we understand what=
<br>
we want.<br>
</blockquote>
<br></div>
Sure. However, INT-AREA isn&#39;t the place for this sort of discussion. Yo=
u might consider trying at <a href=3D"mailto:end2end-interest@postel.org" t=
arget=3D"_blank">end2end-interest@postel.org</a>, which is the typical plac=
e where end-to-end discussions on architecture are first made.<br>

<br>
The IETF is a place for engineering solutions, not research. The IRTF serve=
s that purpose, and the above list is the original IRTF list for these sort=
s of discussions.<br>
<br>
You (and others) are welcome to take this discussion there, but I expect th=
e thread has lost its usefulness to the INTAREA WG.<span class=3D"HOEnZb"><=
font color=3D"#888888"><br>
<br>
Joe<br>
<br>
</font></span><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><div class=3D"im">
Please question everything you learned, even the research method.<br>
<br>
As I see it, the following research style would be ideal:<br>
<br>
-I propose that we do not touch the core Internet.<br>
-People should be free to choose the IP version that they wish because<br>
deciding for others is a technology blocker. IETF designs IPv6, IETF<br>
blocks its development. Because IETF does not give freedom of choice.<br>
This is not normal. Some entities may use IPv6 others IPv4 yet others<br>
IPv7 for unknown reasons. Everybody may agree on IPv6, or not. We do not<br=
>
know. We do not have to.<br>
-To give such freedom of choice, we need to change the end-nodes.<br>
-This is the end-to-end principle.<br>
<br>
Here is a picture:<br>
<a href=3D"http://htmlimg3.scribdassets.com/2hdm1jwfcw1sxm1y/images/4-5930b=
39cea.jpg" target=3D"_blank">http://htmlimg3.scribdassets.<u></u>com/2hdm1j=
wfcw1sxm1y/images/4-<u></u>5930b39cea.jpg</a><br>
<br>
Is this the model that we would prefer? Could we first answer this<br>
question? Anything can be designed. The hard part of research is<br>
deciding on the best solution.<br>
<br>
Thanks,<br>
Pars<br>
<br>
<br>
<br>
<br>
On Wed, Sep 12, 2012 at 8:35 AM, Joe Touch &lt;<a href=3D"mailto:touch@isi.=
edu" target=3D"_blank">touch@isi.edu</a><br></div><div><div class=3D"h5">
&lt;mailto:<a href=3D"mailto:touch@isi.edu" target=3D"_blank">touch@isi.edu=
</a>&gt;&gt; wrote:<br>
<br>
<br>
<br>
=A0 =A0 On 9/11/2012 10:20 PM, Pars Mutaf wrote:<br>
=A0 =A0 ...<br>
<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0Known problems, in no specific order:<br>
<br>
<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 a) like NAT, this fails for all=
 protocols that use<br>
=A0 =A0 =A0 =A0 in-band<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 identifiers (e.g., FTP) unless =
the entire body of<br>
=A0 =A0 =A0 =A0 the packet<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 is translated too, and that mig=
ht not be possible<br>
=A0 =A0 =A0 =A0 for some<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 services<br>
<br>
=A0 =A0 =A0 =A0 I don&#39;t understand. I just copy the whole payload. Or, =
replace<br>
=A0 =A0 =A0 =A0 the IPv4<br>
=A0 =A0 =A0 =A0 header with an IPv6 header. I don&#39;t have to know what&#=
39;s in the<br>
=A0 =A0 =A0 =A0 payload.<br>
<br>
<br>
=A0 =A0 If the payload includes an IP address (take a look at how FTP<br>
=A0 =A0 works), then you have to translate that. That&#39;s how current NAT=
s<br>
=A0 =A0 work for *many* protocols.<br>
<br>
<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 b) you fail to explain why this=
 needs to happen<br>
=A0 =A0 =A0 =A0 for the<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 first packet and not all subseq=
uent packets, or<br>
=A0 =A0 =A0 =A0 what to do<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 with subsequent packets (and wh=
at happens when the<br>
=A0 =A0 =A0 =A0 second<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 packet arrives - e.g., at the t=
ranslator or<br>
=A0 =A0 =A0 =A0 elsewhere -<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 before the first one?)<br>
<br>
=A0 =A0 =A0 =A0 1. I send the first packet to the copier. In the same messa=
ge, I<br>
=A0 =A0 =A0 =A0 tell<br>
=A0 =A0 =A0 =A0 the destination IPv6 address that I learned using DNS for<b=
r>
=A0 =A0 =A0 =A0 example. (this<br>
=A0 =A0 =A0 =A0 is not exactly a tunnel I don&#39;t have to speak IPv6)<br>
=A0 =A0 =A0 =A0 3. The copier creates state for my IPv4 address and destina=
tion IPv6<br>
=A0 =A0 =A0 =A0 address.<br>
=A0 =A0 =A0 =A0 4. Forwards packets in both directions<br>
<br>
<br>
=A0 =A0 Why does the second packet not also need to be tunneled?<br>
<br>
=A0 =A0 FWIW, what happens if the second packet shows up at the copier<br>
=A0 =A0 before the first one? Keep in mind that many protocols (including<b=
r>
=A0 =A0 some variants of TCP) don&#39;t wait for an exchange to complete be=
fore<br>
=A0 =A0 sending the second, third, etc., packets.<br>
<br>
<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 c) the first packet won&#39;t b=
e tunneled unless you<br>
=A0 =A0 =A0 =A0 upgrade<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 the source endpoint node to spe=
ak your new version<br>
=A0 =A0 =A0 =A0 of things;<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 if we could do that, everyone w=
ould be speaking IPv6<br>
<br>
=A0 =A0 =A0 =A0 Yes it is not a tunnel exactly. This is my bad. The first p=
acket<br>
=A0 =A0 =A0 =A0 is a<br>
=A0 =A0 =A0 =A0 special packet, call it a Discrete IP packet, telling the c=
opier the<br>
=A0 =A0 =A0 =A0 destination IPv6 address.<br>
<br>
<br>
=A0 =A0 Is this from the DNS or the source?<br>
<br>
=A0 =A0 And if this is a signalling packet, it&#39;s not a tunnel at all, F=
WIW.<br>
<br>
<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 d) what name/ID are you looking=
 up in the DNS?<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 the node application already di=
d a lookup for the<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 destination, and you now need t=
o rewrite every<br>
=A0 =A0 =A0 =A0 application<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 to use your solution instead<br=
>
<br>
=A0 =A0 =A0 =A0 I assume a new host identifier, other than IP address.<br>
<br>
<br>
=A0 =A0 Have you considered the implications of this assumption? Aren&#39;t=
 you<br>
=A0 =A0 then assuming that this identifier *never changes* as you deploy ne=
w<br>
=A0 =A0 versions of IP, e.g.? Why do you think that will be true if it<br>
=A0 =A0 wasn&#39;t for IPv4?<br>
<br>
<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 (i.e., right now the DNS use is=
 decoupled from network<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 packet processing; you want to =
integrate it - have you<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 seen Cheriton&#39;s I3 proposal=
 along these lines?)<br>
<br>
=A0 =A0 =A0 =A0 I am not sure if it should be integrated.<br>
<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 e) which DNS do you register en=
dpoints in?<br>
=A0 =A0 =A0 =A0 (answer: all of<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 them, except that you can&#39;t=
 know where the ones<br>
=A0 =A0 =A0 =A0 outside your<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 &quot;IP version&quot; bubble a=
re) so basically you&#39;re never<br>
=A0 =A0 =A0 =A0 going to<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 find the endpoints in other bub=
bles anyway<br>
<br>
=A0 =A0 =A0 =A0 You do not know what we can or cannot do yet. We didn&#39;t=
 even<br>
=A0 =A0 =A0 =A0 discuss if<br>
=A0 =A0 =A0 =A0 we want my proposal.<br>
=A0 =A0 =A0 =A0 We attacked the details.<br>
<br>
<br>
=A0 =A0 I do know that you need to register in every DNS or you won&#39;t f=
ind<br>
=A0 =A0 the name (or you need to tie the DNSes together - and if you do<br>
=A0 =A0 that, you provably already have a common internetworking layer, but=
<br>
=A0 =A0 you can&#39;t assume a common internetworking layer in your solutio=
n to<br>
=A0 =A0 provide one).<br>
<br>
=A0 =A0 Until you prove otherwise.<br>
<br>
=A0 =A0 Having a blank margin and a claim didn&#39;t work for Fermat, and i=
t<br>
=A0 =A0 isn&#39;t sufficient here either.<br>
<br>
<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 f) which payload-only are you f=
orwarding? the one<br>
=A0 =A0 =A0 =A0 in the<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 tunneled packet includes header=
s the next bubble<br>
=A0 =A0 =A0 =A0 doesn&#39;t<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 understand; if you strip off th=
ose headers, you<br>
=A0 =A0 =A0 =A0 lose a lot<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 of state<br>
<br>
=A0 =A0 =A0 =A0 No. The copier copies IPv4 payload to the IPv6 header that =
it<br>
=A0 =A0 =A0 =A0 creates<br>
=A0 =A0 =A0 =A0 itself.<br>
<br>
<br>
=A0 =A0 OK, so that&#39;s just a NAT at that point.<br>
<br>
<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0Again, from your paper: &quot;We do not need to =
use NATs<br>
=A0 =A0 =A0 =A0 anymore&quot; only<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0because you don&#39;t call them that, but you&#3=
9;re implementing a<br>
=A0 =A0 =A0 =A0 stateful<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0NAT as a translator.<br>
<br>
=A0 =A0 =A0 =A0 The question is not they are like NATs or not, we are chang=
ing the<br>
=A0 =A0 =A0 =A0 architecture. I can reuse yahoo&#39;s global IP address at =
home.<br>
<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0You claim:<br>
<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0---<br>
<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0We do not touch the core network, i.e. t=
he current IPv4<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0infrastructurewhich works. Those who wis=
h, add additional<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0infrastructure<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0if necessary(IPv4, IPv6, etc.)<br>
<br>
<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0You change the DNS and add translators on that I=
Pv4 network.<br>
<br>
<br>
=A0 =A0 =A0 =A0 I change DNS, I also change TCP.<br>
<br>
<br>
=A0 =A0 DNS is part of the core of the network - at least it&#39;s in-netwo=
rk<br>
=A0 =A0 infrastructure, not an end service on the user&#39;s host.<br>
<br>
<br>
=A0 =A0 =A0 =A0 IPsec doesn&#39;t work, multicast is gone.<br>
<br>
<br>
=A0 =A0 How do you restore those capabilities? Or will security not work he=
re?<br>
<br>
<br>
=A0 =A0 =A0 =A0 But this is a trade-off:<br>
<br>
=A0 =A0 =A0 =A0 We are now free from core Internet&#39;s IP version decisio=
ns<br>
=A0 =A0 =A0 =A0 forever. This<br>
=A0 =A0 =A0 =A0 is the real discussion that we should have here. Do we want=
 this<br>
=A0 =A0 =A0 =A0 approach or not? Once we decided that it is desirable, anyt=
hing is<br>
=A0 =A0 =A0 =A0 designable. Because we do not depend on core network anymor=
e, we<br>
=A0 =A0 =A0 =A0 change<br>
=A0 =A0 =A0 =A0 the end points. This is the end-to-end principle.<br>
<br>
=A0 =A0 =A0 =A0 Do we want to be free from this IP version problem forever?=
 What<br>
=A0 =A0 =A0 =A0 can we<br>
=A0 =A0 =A0 =A0 sacrifice to solve this problem?<br>
<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0We modify the end-hosts only<br>
<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0Your translators are not end-hosts.<br>
<br>
=A0 =A0 =A0 =A0 It is not a modification. People add them and remove them a=
s<br>
=A0 =A0 =A0 =A0 they wish.<br>
<br>
<br>
=A0 =A0 If I remove them - all of them - then the system won&#39;t work. Yo=
u<br>
=A0 =A0 need to have them for your solution.<br>
<br>
<br>
=A0 =A0 =A0 =A0 It is not like modifying all Internet routers.<br>
<br>
<br>
=A0 =A0 It&#39;s a lot like installing new boxes that act a lot like router=
s,<br>
=A0 =A0 except that you refuse to call them routers and they&#39;re not nea=
rly<br>
=A0 =A0 as robust or useful as routers.<br>
<br>
<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0We do not have worry about others&#39; I=
P version<br>
=A0 =A0 =A0 =A0 preferences, we do<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0not have to implement IPv6 for example<b=
r>
<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0Your translators have to worry a lot about versi=
on preference.<br>
<br>
=A0 =A0 =A0 =A0 They are designed for that. And it is not big deal, they ju=
st<br>
=A0 =A0 =A0 =A0 copy payload.<br>
<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0---<br>
<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0Please read the Catenet paper.<br>
<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0You are treating each IP version as a link layer=
, your<br>
=A0 =A0 =A0 =A0 translators<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0are IP routers, and your DNS works like ARP.<br>
<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0Unfortunately, that doesn&#39;t remove the need =
for an end-to-end<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0internetworking layer with global addresses, whi=
ch you<br>
=A0 =A0 =A0 =A0 don&#39;t have<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0and don&#39;t address at all.<br>
<br>
=A0 =A0 =A0 =A0 Let&#39;s first discuss what we want. We may have a host id=
entification<br>
=A0 =A0 =A0 =A0 layer above IP for example but it is early to discuss techn=
ical<br>
=A0 =A0 =A0 =A0 details.<br>
<br>
<br>
=A0 =A0 That&#39;s not a technical detail; that&#39;s the key to the soluti=
on. That<br>
=A0 =A0 IS what IP *is*. That&#39;s why shifting from IPv4 to IPv6 is hard.=
<br>
<br>
<br>
=A0 =A0 =A0 =A0 We do not even know what we want.<br>
<br>
<br>
=A0 =A0 Then write a paper on the requirements. But you cannot expect to<br=
>
=A0 =A0 satisfy a want you *agree* we do not currently understand.<br>
<br>
=A0 =A0 Joe<br>
<br>
<br>
</div></div></blockquote>
</blockquote></div><br>

--bcaec54ee63825eff704c97c33ee--
