Re: [Ideas] WG Review: IDentity Enabled Networks (ideas)

Dino Farinacci <farinacci@gmail.com> Thu, 05 October 2017 16:28 UTC

Return-Path: <farinacci@gmail.com>
X-Original-To: ideas@ietfa.amsl.com
Delivered-To: ideas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBBFD132F3F; Thu, 5 Oct 2017 09:28:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 TaI981RKifZs; Thu, 5 Oct 2017 09:28:49 -0700 (PDT)
Received: from mail-pf0-x232.google.com (mail-pf0-x232.google.com [IPv6:2607:f8b0:400e:c00::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD2C11342DC; Thu, 5 Oct 2017 09:28:25 -0700 (PDT)
Received: by mail-pf0-x232.google.com with SMTP id g62so2579357pfk.12; Thu, 05 Oct 2017 09:28:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=GFKysEwiuGShd470p545259mQzwacL/eL+IQEzQZSnk=; b=RqxM7SVujloO+WRjLXDuOg4MWDwOFfCclqdTaF8Z6+3kyJifzG2k5U7tHHJbgZhxRj GYH5j2kspyfOId5u2o8lXs297DnqDJ9iNuUxiQ4Vs8ECWHaMv8LNuHTkllLaw3hgM+N+ zIwU1Z6N2LnUuxns63yCAUq634RexLGRFak7q4XhJXvBLDBG62m7+LQl3UYHaZDNGRDq ehaIe8TfoXmIv7u0Gu6DJ7ZMJLwzbJT+sze5qx5Ky1mv9uFmoQQ/+91ZTr7gi9Zc2PeH SuQWTV9Ixt/6yJjy0LLgITsDMERWvl/UqmEkCG0hu1d/BYmxPC2CnaZEBkuYixf4FJaJ 36mA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=GFKysEwiuGShd470p545259mQzwacL/eL+IQEzQZSnk=; b=ly1KdjehAsT3lNjBiZqpteIordSHvGvkFYZpG0UWFKr4rsrbUjKAMTG/kGKcWJvBxG OTfOngxbNT5mywBXSQX+4abqHxsxVa1YYGskFmtI65JzcgeHI8AxZ8qmRD6RIVz0uXHC T7cAeJJcXg28o5Nx09mrSuvcf9M3Cun6iVa7mNElYkgcwICIqxXcfJyaNdtDlvPKLMIb Oew2Bc5bsopn+Cm/C+fT1PneYEpRtQ1DyaOn04f4QiFF0O+FkcRSub5fGpgzJONtVnfT baTEjokaH2f7sTDQki4YUgp+15ZJCHmx52oGH+r+A4Yvl8fMgqaRUrmMbV4iuCohd1LO 76FQ==
X-Gm-Message-State: AHPjjUg3V8Sq0sDBG6UyzR4r0lpVCyv+Ugl5lrmVp+Q+2liRKwCXVFXM 4H2W0D2eJ27N759dMliQxrp+FqyL
X-Google-Smtp-Source: AOwi7QDJucgWIi+3FwaXCjIRafFYelY+XLqBxqIcgxQpOVo19oZayCVa3YRuAwb1QOxoh2mrG2cQxA==
X-Received: by 10.99.107.73 with SMTP id g70mr19677855pgc.279.1507220905469; Thu, 05 Oct 2017 09:28:25 -0700 (PDT)
Received: from [10.197.31.157] (173-11-119-245-SFBA.hfc.comcastbusiness.net. [173.11.119.245]) by smtp.gmail.com with ESMTPSA id y7sm30909716pfy.35.2017.10.05.09.28.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 05 Oct 2017 09:28:24 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <67067a23-bb7f-08e4-3766-8802d8f3121f@huitema.net>
Date: Thu, 5 Oct 2017 09:28:23 -0700
Cc: The IESG <iesg@ietf.org>, ideas@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <408B974C-2C4F-497F-9FDE-B9AAD86547B2@gmail.com>
References: <e476f817-580b-9083-48bb-72de1745f1c1@huitema.net> <67067a23-bb7f-08e4-3766-8802d8f3121f@huitema.net>
To: Christian Huitema <huitema@huitema.net>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ideas/qhO9aJcPXXTHAt_Iaxxzf-sb_BQ>
Subject: Re: [Ideas] WG Review: IDentity Enabled Networks (ideas)
X-BeenThere: ideas@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussions relating to the development, clarification, and implementation of control-plane infrastructures and functionalities in ID enabled networks." <ideas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ideas>, <mailto:ideas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ideas/>
List-Post: <mailto:ideas@ietf.org>
List-Help: <mailto:ideas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ideas>, <mailto:ideas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Oct 2017 16:28:51 -0000

> Similarly, consider a node that connects several times to the same
> network, and each time uses IPv6 temporary addresses. The web servers
> that it contact cannot use the IP addresses to correlate different
> connections that happened at different times. This would change if the
> identifier in an ID/LOC architecture remained constant.
> 
> Multipath TCP and planned multipath extensions of QUIC are example of
> transport protocol that allow transport connections to use multiple
> network paths simultaneously. In both cases, there s significant work
> going on to ensure that intermediaries cannot easily associate the
> traffic on the multiple paths with a single connection. If the
> multi-homing function was delegated to an ID/LOC system, intermediaries
> could potentially observe the identifiers and associate these connections.

Christian, just to be clear, in LISP, temporary/ephemeral EIDs can be used for the public case. For a private use case, one uses crypto-EID authentication to regsiter and to get mappings from the mapping database (can be used within a closed user-group VPN). And both for the public and private case, crypto-EIDs can be used so a hash is pretty opaque to trackers. And there is no reason you cannot use a set of private/public key pairs and crypto hashes to send packets.

So there are solutions to this. And they are implmented and ARE NOT complicated.

Dino