Re: [lisp] Roman Danyliw's Block on charter-ietf-lisp-04-06: (with BLOCK and COMMENT)

Padma Pillay-Esnault <padma.ietf@gmail.com> Thu, 04 January 2024 16:44 UTC

Return-Path: <padma.ietf@gmail.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 694DCC14F685; Thu, 4 Jan 2024 08:44:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1LvC0hMu-SlB; Thu, 4 Jan 2024 08:44:26 -0800 (PST)
Received: from mail-lj1-x22b.google.com (mail-lj1-x22b.google.com [IPv6:2a00:1450:4864:20::22b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C612C14F682; Thu, 4 Jan 2024 08:44:26 -0800 (PST)
Received: by mail-lj1-x22b.google.com with SMTP id 38308e7fff4ca-2cd17a979bcso8629441fa.0; Thu, 04 Jan 2024 08:44:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1704386665; x=1704991465; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=nYYorSU4qtHXnulB7fcl2AK8LWCuTCdy/+8liOsaQlw=; b=T5Q2DEhU936cAMMKDd/3b83xG4FG+v5i6VA+9utpdQVJSS7/Sf/u5TCqptq3QyCjUs ccvPeHL4WDU7FcIpnWhzYq3CCDVgC0hjJ2upyQ6lf9OBXliTeUArVNfGWfvzuRqAK5s8 M8VtuoE165bdWoGP9ltUQqhOGcR+IeztA1Xg4glifKIMAqOtincZq/4syxNAk5pCXpPC oEkyzbL5cDH/zx0H8geF9UTAI3Tti8IsQZiXa7m1DxiQvJKUQibHMO2ALweToiffZbb9 mi3VA1tKJGAuWIZojRO1ZblZQTYsoqFEdxxfxtdXIAnYKkEnpPX0wLQ9dqqzQ0atQmry +bJQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704386665; x=1704991465; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=nYYorSU4qtHXnulB7fcl2AK8LWCuTCdy/+8liOsaQlw=; b=TclzWYDybcGHGZAZoiNH394ixGopYnDMWm6lFP4zHpGaTvC66ydhqw/74o3Gsy7qpp XPs44so+fEM6Ay4UcdEjU2lH3QkzKGFjzoQZ4JJ4UXD3jRKBCqZ8/fPSNIn4MTVtgdwb DZArzumH+22fNnTU6LbP6Ca7X1B3qYC571IfAj//cZVsWqucjSbyeSEbQwpCA/QxIO2g bn4A7ElO5XNRguymoKvTdLA3cDx5Duc75IbpAJDby8txpiL/UL066JCQvjOVUSrjYpyv WVZp1LmR1aW3SjiR+pP4IpbrKNC+ffc2gARHBBh5JIK9KkCXXuT6M+eTb0ZNpBQPXlAR UoaQ==
X-Gm-Message-State: AOJu0YxzcPmjoTOGnnKKgQr076RzV/+QfNWXKvXHEuhLtpmaVtVNMXlQ +afVCmGp/DNCWT/Q9Ay3hZ6mCUKE3rcbTV9K9xVeiE7qCEE=
X-Google-Smtp-Source: AGHT+IE3SNYzVnoKDtREHPUNJMDOCWBIKmOXMzujbAi02BYIqf8VwoxympiQeLohE6kwoKcxMCQ/u1o6uxYQOisEq+M=
X-Received: by 2002:a2e:9d86:0:b0:2cc:e8d2:10be with SMTP id c6-20020a2e9d86000000b002cce8d210bemr239745ljj.93.1704386664456; Thu, 04 Jan 2024 08:44:24 -0800 (PST)
MIME-Version: 1.0
References: <170431647814.62985.15974782567928382830@ietfa.amsl.com>
In-Reply-To: <170431647814.62985.15974782567928382830@ietfa.amsl.com>
From: Padma Pillay-Esnault <padma.ietf@gmail.com>
Date: Thu, 04 Jan 2024 08:44:13 -0800
Message-ID: <CAG-CQxqE0Wit+WZ29_0Y_n-7yJreuCt9kxPPN26ZjNchFkU1qg@mail.gmail.com>
To: Roman Danyliw <rdd@cert.org>
Cc: The IESG <iesg@ietf.org>, lisp-chairs@ietf.org, lisp@ietf.org
Content-Type: multipart/alternative; boundary="000000000000b1e574060e21710b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/lqAJusvtRgcPI_tvtX4mPNazAiM>
Subject: Re: [lisp] Roman Danyliw's Block on charter-ietf-lisp-04-06: (with BLOCK and COMMENT)
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lisp/>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jan 2024 16:44:30 -0000

Hi Roman

Please see PPE for my comments inline

On Wed, Jan 3, 2024 at 1:14 PM Roman Danyliw via Datatracker <
noreply@ietf.org> wrote:

> Roman Danyliw has entered the following ballot position for
> charter-ietf-lisp-04-06: Block
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/charter-ietf-lisp/
>
>
>
> ----------------------------------------------------------------------
> BLOCK:
> ----------------------------------------------------------------------
>
> Per the following set of work "Privacy and Security: The WG will work on
> EID
> anonymity, VPN segmentation leveraging on the Instance ID, and traffic
> anonymization. The reuse of existing mechanisms will be prioritized.":
>
> -- What is the threat model assumed for "traffic anonymization" and "EID
> anonymity"?  Could the desired security properties be clarified?
>
> PPE - LISP has an (EID, Routing Location) pair, it is possible to learn of
> a specific long lived EID and then poll the mapping system to know its new
> bindings over time. It would be therefore possible to record and track long
> lived EIDs and identify the traffic specifically for that endpoint. Some
> desired security properties would be to have short lived EIDs as well as
> secured and restricted access to binding of an EID and locator for privacy.
>


> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Per the following set of work "Privacy and Security: The WG will work on
> EID
> anonymity, VPN segmentation leveraging on the Instance ID, and traffic
> anonymization. The reuse of existing mechanisms will be prioritized.":
>
> -- What will the output of this work look like?  Which milestone is it
> associated with?
>
> PPE - There are currently 2 WG drafts and the milestone is
> March 2025 Submit LISP Privacy and Security document(s) to the IESG for
> consideration (Privacy and Security) [EXPERIMENTAL]
>
> Thanks
Padma