Re: [Pidloc] PIdLoc Webex

Dino Farinacci <> Fri, 07 December 2018 18:42 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E218E130FA9 for <>; Fri, 7 Dec 2018 10:42:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2
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: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id SHPEnE3eoUZc for <>; Fri, 7 Dec 2018 10:42:55 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::12c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 01A3B130F9C for <>; Fri, 7 Dec 2018 10:42:54 -0800 (PST)
Received: by with SMTP id m8so2208360itk.0 for <>; Fri, 07 Dec 2018 10:42:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=YskGj/1TCZu/ZMRcvWHrn1DsHPlJvPmKSxYTrGhG02k=; b=BvFPddmVNLClzovNGUZKXvl7KZ9zaKld/+so2QQQJ4ioAY8Q2t4TtMNzBtJT7Obg4P IkkB7ZHjfs9Kt72p6PKOmApyZso7nNYt7jJsHp3baqkruGwmJIqWF73ZcyiqnduFKz7i IKzvz+LzQnnETER7k12TtZrHCc908IxRS5fcsIQX5B08w7NgKLQJ+F9XaFab6HuoW44/ MOb+TPt6u1z0KxAU5GVdrutFQpLKL+QYeiJzkvLGOxkddLBv6qMvMd12C4D3SEfZuL5u Q0favYa4YfGE3XzYcQMVAaRFXeEa+u+FEitlrLnp+pA/3nLcmk9kG4rAPkYbe5dIyC9w r8Fg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=YskGj/1TCZu/ZMRcvWHrn1DsHPlJvPmKSxYTrGhG02k=; b=hjIfdHGz68HrJ5YoCcKA0eutnlB07MODTlyu0QPxZUZWUc5HlII1ntxmBX4QerZkpn b9B+0EnnZrbwHmPgg9RtzYr7ygYXgkgngFJ4SZiO2SwsHUsbE6stk5UX4G3ZHODQk066 EnMk191YtQ5yn4w9XOYK55Fal/WnK3LlFYCypuaWaAm9esosLrIrYkxfRnUQ+gYmkM3x U6RsNgYlWS8tP+55RVp78JRuj1P7pBn8eeBQTgOf6viyVdW5id2KEIcyhZOCf6JFRk+c jPZUuI13j9zd0FBi9NAmHHTxs1+IEYibAXxGov803csoUYiVo1tF0XRXsraJ1Ef4AkoW o7Ew==
X-Gm-Message-State: AA+aEWaVVNLmXC41Hh5+ob9XRcB5Sqgkj8G5Zipr4LDI9JeDSFVQymOF gMkckZkberPs7i4/1jORwjQ=
X-Google-Smtp-Source: AFSGD/U3t+WFyswDc2B5M+JN1Q67qAjUsPRzs2C/me/SIaaJA6Yy2duPk48yZCKGejUdm4NkSUs+jg==
X-Received: by 2002:a24:3a09:: with SMTP id m9mr2798596itm.98.1544208174297; Fri, 07 Dec 2018 10:42:54 -0800 (PST)
Received: from [] ([]) by with ESMTPSA id 196sm2064956itu.37.2018. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 07 Dec 2018 10:42:53 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Dino Farinacci <>
In-Reply-To: <>
Date: Fri, 7 Dec 2018 10:42:40 -0800
Cc:, RJ Atkinson <>, Saleem Bhatti <>, Shunsuke Homma <>, Behcet Sarikaya <>, Luigi Iannone <>,,
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <FRAPR01MB0801A22EEC0D55414EFFEC2ED1D00@FRAPR01MB0801.DEUPRD01.PROD.OUTLOOK.DE> <FRAPR01MB0801CDFD28647B7A02D700D2D1D00@FRAPR01MB0801.DEUPRD01.PROD.OUTLOOK.DE> <FRAPR01MB0801A452C8111F16940D4D65D1D10@FRAPR01MB0801.DEUPRD01.PROD.OUTLOOK.DE> <FRAPR01MB080121A9C90A6F78BBD7E4B7D1AF0@FRAPR01MB0801.DEUPRD01.PROD.OUTLOOK.DE> <> <> <> <> <> <> <> <>
To: Tom Herbert <>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <>
Subject: Re: [Pidloc] PIdLoc Webex
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 07 Dec 2018 18:42:57 -0000

>> You are bringing up a different issue now. And we have discussed this at length before. But as long as you have an underlay and plaintext headers, you still lose privacy even when EIDs are obfuscated.
> The underlay protocol is not relevant to privacy, it is only the
> mechanism used in a closed provider's network to deliver packets to

Yes it is for the reasons you have stated before. If I run LISP from my house and obfuscate on EIDs, any eavesdropper can look at the source RLOC to determine I’m a Comcast customer (and can find out the head-end and tail-end connections - my house). That is a violation of my privacy. They can’t tell what transport connections I’m using and who I cam talking to but as long as the outer header is plaintext and “hidden aggreagated", it is a granular privacy invasion. If the LISP xTR was in Comcast, then it looks like some obfuscated EIDs are sending from Comcast. That doesn’t violate my personal privacy.

> their destination. Outside of the network, only plain IP packets are
> seen. It is the privacy attributes of the packets visible to the world
> that are interesting.

That is what I’m talking about.