Re: IPmix.

Stephane Bortzmeyer <bortzmeyer@nic.fr> Sun, 20 November 2016 19:13 UTC

Return-Path: <bortzmeyer@nic.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07544129481; Sun, 20 Nov 2016 11:13:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KFEl9HAXpo0G; Sun, 20 Nov 2016 11:13:09 -0800 (PST)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [217.70.190.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4177512941A; Sun, 20 Nov 2016 11:13:09 -0800 (PST)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id EE0A631D66; Sun, 20 Nov 2016 20:13:06 +0100 (CET)
Received: by mail.sources.org (Postfix, from userid 1000) id 14E0FCBDBC; Sun, 20 Nov 2016 20:10:50 +0100 (CET)
Date: Sun, 20 Nov 2016 20:10:50 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Khaled Omar <eng.khaled.omar@hotmail.com>
Subject: Re: IPmix.
Message-ID: <20161120191049.GB32028@sources.org>
References: <HE1PR04MB144901D56F1E2DC6A770D2EEBDB20@HE1PR04MB1449.eurprd04.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <HE1PR04MB144901D56F1E2DC6A770D2EEBDB20@HE1PR04MB1449.eurprd04.prod.outlook.com>
X-Transport: UUCP rules
X-Operating-System: Debian GNU/Linux 8.6
X-Charlie: Je suis Charlie
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/buG1xXLmJhCU0LWbACEjAbzgmzM>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Nov 2016 19:13:11 -0000

On Sun, Nov 20, 2016 at 05:44:20PM +0000,
 Khaled Omar <eng.khaled.omar@hotmail.com> wrote 
 a message of 848 lines which said:

> You can find the new modified IPmix text RFC version attached.

Strange UTF-16 encoding... Well, once decoded, I can say that:

* you are very detailed when it comes of describing the current issues
and much less so when you describe your solution;

* the way I understand it (but there is zero high-level description
of IPmix, I rely mostly on the schemas):

   * everything is done by new gateways in both networks. What makes
   you think that IPv4-only networks will deploy these gateways, when
   they don't even deploy IPv6 (which is typically simpler)?

   * what do you thing will happen to the new IPmix packets in the
   core? Existing routers won't know what to do with them

Also, your proposal is extremely sketchy and seems to ignore
completely the issues which were discovered with the transition to
IPv6. For instance, some applications transmit IP addresses as payload
(which breaks things like NAT64). How do you address these?

Really, the problems of migrating the Internet to a new L3 protocol
have been discussed by many people in many years. It is unlikely that
a 8-pages proposal will suddenly solve them.