Re: [Ila] [5gangip] PS draft: New Version Notification for draft-hspab-5gangip-atticps-00.txt

Dino Farinacci <farinacci@gmail.com> Thu, 01 February 2018 01:33 UTC

Return-Path: <farinacci@gmail.com>
X-Original-To: ila@ietfa.amsl.com
Delivered-To: ila@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D121612F4E0; Wed, 31 Jan 2018 17:33:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=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 t6jSiHCxju91; Wed, 31 Jan 2018 17:33:01 -0800 (PST)
Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::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 ED10F12EB14; Wed, 31 Jan 2018 17:33:00 -0800 (PST)
Received: by mail-it0-x232.google.com with SMTP id p139so2072262itb.1; Wed, 31 Jan 2018 17:33:00 -0800 (PST)
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=SgjwitqsOg223QQA5V7IP7Fb56BVdUBW5524Xgj6wzY=; b=mG6u4Kd94ZyKUlmGoHr04Qcf5mdtZ6iUW1rE4t7uy9p57n0GYLGgN3HX+Mr+ZeFIVZ Tv7dbuplvMOfjSWtOrczjUfws+7ONs7sqqXCnDeuoblT9Ct+h9BCJvhESGBjJarp1FIK nppoDViCHFphJa7QwFTqg28UE66reIER0Fe2PXySgXIwHTxMej72MYJ3CFtPyOSRkfEZ jkimh5LgGsfBYwJ/Mm/cghM/474yED/2+6Uw0zMfvhdld9cffcXsniWeY27SFodX8xUb J5ddoxvR2AQJNvJANaXbqHpmgx4FOM1ut/tPPTOIpatI51avGBUzCM22YTmtuQIszPUF 8HvA==
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=SgjwitqsOg223QQA5V7IP7Fb56BVdUBW5524Xgj6wzY=; b=g06DDJXO4oM2cXiyGzkNsxiJZBCeWXd9rlb0/iMpvcuBy55lnalEXtNidjp+Hh6+Vn rFfHY9fPtEAJgdL872jTPR8teX7ucz7nDFiiP0qqJGHXI/GGOyOXCWiLZQilMxtHEQSU z1E9xIVQnk6EOawKbebnAmPAl1P+gWzQt1zsRKT4TWko82wiVWYgyzaRITVInvNdkduZ J6xER/7W1Qyn8+fDL0R/6zk/WaRMTcqjA5MuC0S2YLPORDmiMUX90v8ZkeDPRQYeBZwB 44bHaBKmRCUYabSx/2fNjLPklaWKjImCo7uOZxPJHnd4BT07ys2ITKS2bXxnUi80MQZU WLIQ==
X-Gm-Message-State: AKwxytdYY32dINwwa1gmofT6iXJLeQfzNY1G8UMVTVL/y5XYNQzMKuhl k3vXE2GxZ5cAjDCmaTxc0k5OMAwR
X-Google-Smtp-Source: AH8x227PupsoLgOViTjxdZi4jIMSo5y+iLgCkZtMRPYpTgi/gnggbFaSrIOHHPLoFqRuccVkelpwiA==
X-Received: by 10.36.51.201 with SMTP id k192mr40736892itk.71.1517448780160; Wed, 31 Jan 2018 17:33:00 -0800 (PST)
Received: from dino-macbook.attlocal.net (adsl-108-94-0-209.dsl.pltn13.sbcglobal.net. [108.94.0.209]) by smtp.gmail.com with ESMTPSA id l69sm8222876ioi.11.2018.01.31.17.32.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 31 Jan 2018 17:32:59 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <CAPDqMepctwrfL9ums5xfBSWo6ErrBrKWHpskYWbX20z87zww=A@mail.gmail.com>
Date: Wed, 31 Jan 2018 17:32:58 -0800
Cc: Tom Herbert <tom@herbertland.com>, 5GANGIP <5gangip@ietf.org>, Behcet Sarikaya <sarikaya@ieee.org>, ila@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <B162521A-FA48-49F9-ABF6-B31E87F2B3B8@gmail.com>
References: <CAC8QAceokC+Fv5AV5KG7fB1CamstqOomOyFrNeKRQ5+sgb3T4Q@mail.gmail.com> <CALx6S34GoMbt=HqHRjt_N7ZUqk=L6YNjK8qChL9oHLoFTO2hfw@mail.gmail.com> <CAC8QAccoZ9mcweHc-pqNqtsR7PRamVFaTL2_G4fJ1YTZ6gu=zw@mail.gmail.com> <CALx6S34gEVLKzxvf08-JfvSCtptPXXi-4Qkew19JeO8fcu0+HQ@mail.gmail.com> <84E8607E-06E2-41DA-A1F6-1123E87F1E11@gmail.com> <CAPDqMeqAXZvFjftTs85brXmX5LhGL9gG9AoR4doaVk4JyU3DeQ@mail.gmail.com> <621D5B0B-4DDC-456F-9D36-C54D1417A8D9@gmail.com> <CAPDqMeo8-TP6MT8+ji2Qguh7ZFJeYqVDcczTe9sOAJEFM1zhrg@mail.gmail.com> <2A078F4A-72ED-4CBC-8918-D5C0186C34A7@gmail.com> <CAPDqMepctwrfL9ums5xfBSWo6ErrBrKWHpskYWbX20z87zww=A@mail.gmail.com>
To: Tom Herbert <tom@quantonium.net>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ila/4ikXTQxZ-s2_ee9rMErtRZb5Ywk>
Subject: Re: [Ila] [5gangip] PS draft: New Version Notification for draft-hspab-5gangip-atticps-00.txt
X-BeenThere: ila@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Identifier Locator Addressing <ila.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ila>, <mailto:ila-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ila/>
List-Post: <mailto:ila@ietf.org>
List-Help: <mailto:ila-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ila>, <mailto:ila-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Feb 2018 01:33:03 -0000

What if you and I are running ILA and are attached to different providers. How do you get packets to me if my locators are not exposed outside my provider?

Dino

> On Jan 31, 2018, at 4:08 PM, Tom Herbert <tom@quantonium.net> wrote:
> 
> On Wed, Jan 31, 2018 at 3:25 PM, Dino Farinacci <farinacci@gmail.com> wrote:
>>> That should only be true if you are my network provider. To anyone
>>> else the only thing they should be able to deduce from an address is
>>> that the packet originated from a random user of my network provider.
>> 
>> I can tcpdump packets on my router for packets you send before the locator is translated back to the sir-prefix. And count on the locator being in DNS for a reverse lookup so I can get some ascii text that gives me a clue.
> 
> Again, that is only true if your router is in the provider network  If
> locators imply geo-location, which they likely would in a mobile
> network, then exposing them to anyone outside of the trusted network
> is asking for trouble.
>> 
>>> 
>>>> You have to change and obfuscate EIDs and you have to keep using different RLOCs. Cat and mouse game.
>>>> 
>>> For best privacy you would keep using different source addresses
>>> (identifiers) for different flows, Locators are not an issue if their
>>> visibility is restricted to the provider network, so that neither UEs
>>> nor external nodes ever see them .
>> 
>> Don’t you want your provider to not track you?
> 
> It's inherent in the operations  that my provider tracks me in order
> to be able to forward packets. But, I have a contractual agreement
> with the provider to do that and protect privacy. For anyone outside
> of my provider, I don't want them to be able to track me. This is why
> I don't want locators to be visible outside of the network. That would
> include UEs attached to the network (they are not trusted devices) and
> putting locators in DNS.
> 
> Tom
> 
> 
> 
>> 
>> Dino
>>