Re: [arch-d] ipv4 and ipv6 Coexistence.

Vittorio Bertola <vittorio.bertola@open-xchange.com> Wed, 26 February 2020 11:52 UTC

Return-Path: <vittorio.bertola@open-xchange.com>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A7183A0896 for <architecture-discuss@ietfa.amsl.com>; Wed, 26 Feb 2020 03:52:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.088
X-Spam-Level:
X-Spam-Status: No, score=-2.088 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=open-xchange.com
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 i2OuA3KqGVDr for <architecture-discuss@ietfa.amsl.com>; Wed, 26 Feb 2020 03:52:56 -0800 (PST)
Received: from mx4.open-xchange.com (alcatraz.open-xchange.com [87.191.39.187]) (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 362B03A0891 for <architecture-discuss@ietf.org>; Wed, 26 Feb 2020 03:52:55 -0800 (PST)
Received: from open-xchange.com (imap.open-xchange.com [10.20.30.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx4.open-xchange.com (Postfix) with ESMTPS id 7669F6A275; Wed, 26 Feb 2020 12:52:51 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=open-xchange.com; s=201705; t=1582717971; bh=psXJkKYE5yqffghLY8okrTwsBWtjYItOLfvD2XGHZJo=; h=Date:From:To:Cc:In-Reply-To:References:Subject:From; b=rP1Wtl6ygELPTttdAxNWWVFUNkK6ENaUhCEOTJ+81ZYezqdgdhlOjV2fpep4Ygi/l GYvwV5S+Nkqrdbi60BpPU4cmT0wJARmLlI1RdNrwkhg5rw/snmEEXTslmRV8R29Sga DnbWqg9MJTnzWi7lf6Keu2ZBu82nMD61ZHfqmrFRZFNmOmPR7l0FqD+s7STAj6qpBO b8Tmva+AVI6rxwT+fkcweJGOXVtGt1Rs13uoOgJCT+gOws4kNwOE6ubSz2Z/UesDNd 8cSR1jNh2sAZQ0OWilx/b/t6klvR6DpPsFriHd+WnAXumn6WIN4+tpDu09RB0zILi0 SSvOSCAnDvf6A==
Received: from appsuite-gw1.open-xchange.com (appsuite-gw1.open-xchange.com [10.20.28.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by open-xchange.com (Postfix) with ESMTPSA id 699853C04CD; Wed, 26 Feb 2020 12:52:51 +0100 (CET)
Date: Wed, 26 Feb 2020 12:52:51 +0100
From: Vittorio Bertola <vittorio.bertola@open-xchange.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: architecture-discuss@ietf.org
Message-ID: <1050951832.15584.1582717971339@appsuite-gw1.open-xchange.com>
In-Reply-To: <75ecdea9-ab6f-f20b-bb1f-8740cbe9c159@cs.tcd.ie>
References: <PR3P194MB0843ACAE01F33CEC57266A1AAE100@PR3P194MB0843.EURP194.PROD.OUTLOOK.COM> <EDAE6375-EE0B-4864-9834-C1FBC209D581@sobco.com> <PR3P194MB08431E138262F2A43C1D0621AE100@PR3P194MB0843.EURP194.PROD.OUTLOOK.COM> <8ADEA0E1-291A-4400-9925-F65A26116372@consulintel.es> <PR3P194MB0843939F3B38426960A66E70AE130@PR3P194MB0843.EURP194.PROD.OUTLOOK.COM> <D8063303-7DDA-41F8-A63A-C0244E3E9E25@isc.org> <20200224222715.GA49892@faui48f.informatik.uni-erlangen.de> <28C4725E-E4C5-4937-835F-C6DEA9B710CF@gmail.com> <20200225202403.GG39574@faui48f.informatik.uni-erlangen.de> <0755B3F6-D90F-4F85-8D33-7C9C118FB475@gmail.com> <75ecdea9-ab6f-f20b-bb1f-8740cbe9c159@cs.tcd.ie>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
Importance: Normal
X-Mailer: Open-Xchange Mailer v7.10.3-Rev5
X-Originating-Client: open-xchange-appsuite
Autocrypt: addr=vittorio.bertola@open-xchange.com; prefer-encrypt=mutual; keydata= mQENBFhFR+UBCACfoywFKBRfzasiiR9/6dwY36eLePXcdScumDMR8qoXvRS55QYDjp5bs+yMq41qWV9 xp/cqryY9jnvHbeF3TsE5yEazpD1dleRbkpElUBpPwXqkrSP8uXO9KkS9KoX6gdml6M4L+F82WpqYC1 uTzOE6HPmhmQ4cGSgoia2jolxAhRpzoYN99/BwpvoZeTSLP5K6yPlMPYkMev/uZlAkMMhelli9IN6yA yxcC0AeHSnOAcNKUr13yXyMlTyi1cdMJ4sk88zIbefxwg3PAtYjkz3wgvP96cNVwAgSt4+j/ZuVaENP pgVuM512m051j9SlspWDHtzrci5pBKKFsibnTelrABEBAAG0NUJlcnRvbGEsIFZpdHRvcmlvIDx2aXR 0b3Jpby5iZXJ0b2xhQG9wZW4teGNoYW5nZS5jb20+iQFABBMBAgAqBAsJCAcGFQoJCAsCBRYCAwEAAp 4BAhsDBYkSzAMABQMAAAAABYJYRUflAAoJEIU2cHmzj8qNaG0H/ROY+suCP86hoN+9RIV66Ej8b3sb8 UgwFJOJMupZfeb9yTIJwE4VQT5lTt146CcJJ5jvxD6FZn1Htw9y4/45pPAF7xLE066jg3OqRvzeWRZ3 IDUfJJIiM5YGk1xWxDqppSwhnKcMOuI72iioWxX0nGQrWxpnWJsjt08IEEwuYucDkul1PHsrLJbTd58 fiMKLVwag+IE1SPHOwkPF6arZQZIfB5ThtOZV+36Jn8Hok9XfeXWBVyPkiWCQYVX39QsIbr0JNR9kQy 4g2ZFexOcTe8Jo12jPRL7V8OqStdDes3cje9lWFLnX05nrfLuE0l0JKWEg8akN+McFXc+oV68h7nu5A Q0EWEVH5QEIAIDKanNBe1uRfk8AjLirflZO291VNkOAeUu+dIhecGnZeQW6htlDinlYOnXhtsY1mK9W PUu+xshDq7lXn2G0LxldYwyJYZaJtDgIKqVqwxfA34Lj27oqPuXwcvGhdCgt0SW/YcalRdAi0/AzUCu 5GSaj2kaGUSnBYYUP4szGJXjaK2psP5toQSCtx2pfSXQ6MaqPK9Zzy+D5xc6VWQRp/iRImodAcPf8fg JJvRyJ8Jla3lKWyvBBzJDg6MOf6Fts78bJSt23X0uPp93g7GgbYkuRMnFI4RGoTVkxjD/HBEJ0CNg22 hoHJondhmKnZVrHEluFuSnW0wBEIYomcPSPB+cAEQEAAYkBMQQYAQIAGwUCWEVH5QIbDAQLCQgHBhUK CQgLAgUJEswDAAAKCRCFNnB5s4/KjdO8B/wNpvWtOpLdotR/Xh4fu08Fd63nnNfbIGIETWsVi0Sbr8i E5duuGaaWIcMmUvgKe/BM0Fpj9X01Zjm90uoPrlVVuQWrf+vFlbalUYVZr51gl5UyUFHk+iAZCAA0WB rsmACKvuV1P7GuiX3UV9b59T9taYJxN3dNFuftrEuvsqHimFtlekUjUwoCekTJdncFusBhwz2OrKhHr WWrEsXkfh0+pURWYAlKlTxvXuI7gAfHEQM+6OnrWvXYtlhd0M1sBPnCjbyG63Qws7Rek9bEWKtH6dA6 dmT2FQT+g1S9Mdf0WkPTQNX0x24dm8IoHuD3KYwX7Svx43Xa17aZnXqUjtj1
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/laHHSedVZQTJJbHZckSk8uiaw3w>
Subject: Re: [arch-d] ipv4 and ipv6 Coexistence.
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Feb 2020 11:53:00 -0000


> Il 26/02/2020 11:45 Stephen Farrell <stephen.farrell@cs.tcd.ie> ha scritto:
> 
> If you do want to rehash the cryptowars debate again,
> maybe at least change the subject line? If doing so,
> and I hope you decide not to, because there's no gain,
> please recognise that there are many (me included) who
> do not share the views you quoted for sound technical
> reasons (e.g. [1] is perhaps the most-cited recent
> paper on that) that have garnered rough consensus in
> the IETF every time we've done that rehashing.

I think that no one here wants to reopen that discussion - we all agree that, from a technical standpoint, putting backdoors in cryptography is a bad idea. However, I wholeheartedly share the rant that Toerless posted; the problem is that, outside of the IETF, there are real public order issues that the IETF refuses to address, just continuing to deny their relevance or to suggest that they are technically impossible to solve. 

This behaviour will not make the issues disappear, nor the push by non-technical stakeholders to get them addressed, so either the IETF can come up with a workable technical reply to "what should we do then to enforce the law on a fully encrypted Internet?", or the push will simply break the Internet as we know it, and then you will have more countries building great firewalls, or mandating really bad technical solutions by law, because no one built a good one for them.

There could be solutions to the above question that impact the architecture of the Internet without breaking the communication protocols - for example, related to where the endpoints are located and who runs/gets access to them. Can this be done securely, with a reasonable compromise between privacy and access, etc.? I don't know, but AFAIK the IETF until now has refused to even discuss the issue - and even if it is mostly a policy issue, sound technical know-how and possibly bits of specific protocol development are likely to be part of any good solution. (Think of the RDAP protocol designed to handle global tiered access to domain registrant information, though it's not really working yet because the policy part has not been agreed - still, without building the appropriate technical tool there would be no way to address the policy issue.)

I understand that this is hard because it is not something that technologists can do alone; it requires interdisciplinary cooperation among many open minded people (open minded in the sense that they have to listen to and acknowledge very different views on what the Internet should be and do). But I see this as the big architectural challenge in the near future.

-- 
 
Vittorio Bertola | Head of Policy & Innovation, Open-Xchange
vittorio.bertola@open-xchange.com 
Office @ Via Treviso 12, 10144 Torino, Italy