Re: [arch-d] Possible IAB Adoption of draft-kpw-iab-privacy-partitioning

Dhruv Dhody <dhruv.ietf@gmail.com> Wed, 07 December 2022 13:50 UTC

Return-Path: <dhruv.ietf@gmail.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 F0742C152572 for <architecture-discuss@ietfa.amsl.com>; Wed, 7 Dec 2022 05:50:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 HUzqqRNXiU8r for <architecture-discuss@ietfa.amsl.com>; Wed, 7 Dec 2022 05:50:08 -0800 (PST)
Received: from mail-wm1-x335.google.com (mail-wm1-x335.google.com [IPv6:2a00:1450:4864:20::335]) (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 56CB0C15270C for <architecture-discuss@ietf.org>; Wed, 7 Dec 2022 05:50:08 -0800 (PST)
Received: by mail-wm1-x335.google.com with SMTP id r65-20020a1c4444000000b003d1e906ca23so1065281wma.3 for <architecture-discuss@ietf.org>; Wed, 07 Dec 2022 05:50:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=cDsx4Zy54dSDeDHC21UxOy3auVLEhhSjEczpyA4wHwI=; b=X2hMz8q7GXXB/vSzlLRNgikXsmlkiYse0BYeKij96kGgtFOobcHomfNNUJ7UwfDF6Y NfeSwcr/g9rZXI++a/8mq8kxKNKjaOeR5QHMveK4D3wrRbdQTtyewQIyANs5aULF4BTi EMFOx/g/AZr9yRyo5gXC9XZJntcfw79AkKziDyvSIjPV3SBz3CzPY1x750OC1Mkd/L6t 4jJqQg5wDPjqISjBESG+yvmaMmdhGEjFwPqIGQ6oeoSBlBPLWf03cLrk7tbOSLdu7LBf nr7zQyohNg0AGwUAUfX5/MMFVtqwDX+OAHwCQkE0cYHKH6oTYUODXu9DY0TEGPCLTHIY weJg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=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=cDsx4Zy54dSDeDHC21UxOy3auVLEhhSjEczpyA4wHwI=; b=taHp1kwRRvstKcp9vI9Tt+/bcqi1xBph7PE8hZetEjmxPbXDJs2ZZL6EW9U55cyu+z W5IjI8Tc6kYdGbGC+wk4JdUXdlCrp3YhoONFVmnOKF/PCA6NqSdNPtMK8SFAyaEztw4r seBA2R64x0ZkP6ArL7+Y0SZnN/xIbsQuhYdwbfr18f0VoGdT8uSRuGTx7QCsCLhf4tSW ds0eFGVQ9G3/I+gH7/siats7+Kl/M8lnIn9/GKNWeYYhi9sYTCU0sanqSpI9g3vQ95OD PpXtpMQPsLDvRubAohs9v6KrA063MEtyzuZQy08myDLqXHxKTgpluo5ZyAXR//edfjyF dixw==
X-Gm-Message-State: ANoB5pk8zBg307czWrn5gXmwsc0LIYb1H9RR3SI17haAuDd+aLjyRwb/ BpK0T9S9+GeKUCdPnbwO2qVQ0Dk3daWZlirWriVkOaIi
X-Google-Smtp-Source: AA0mqf5MgCQmes+GLpal0AtvZ8NcOHG/VR414wXqqFJToUrjnlxb8m4soqQUUCLkrwyfR5xkTzka+tp+S0F3F0RA4DQ=
X-Received: by 2002:a05:600c:3543:b0:3cf:74bb:feb1 with SMTP id i3-20020a05600c354300b003cf74bbfeb1mr64834383wmq.102.1670421005941; Wed, 07 Dec 2022 05:50:05 -0800 (PST)
MIME-Version: 1.0
References: <166862348898.27211.16338265887689375983@ietfa.amsl.com>
In-Reply-To: <166862348898.27211.16338265887689375983@ietfa.amsl.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Wed, 07 Dec 2022 19:19:28 +0530
Message-ID: <CAB75xn4LkVX2WLGm7biwPrD5E=CHpdSyMoruvWgwPwniV908dA@mail.gmail.com>
To: architecture-discuss@ietf.org, iab@iab.org
Content-Type: multipart/alternative; boundary="000000000000af431505ef3d32f0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/myas9SVNTNu6eHl7LZbHw3IzoAQ>
Subject: Re: [arch-d] Possible IAB Adoption of draft-kpw-iab-privacy-partitioning
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.39
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, 07 Dec 2022 13:50:12 -0000

Hi,

This seems like a good I-D for IAB to work on.

I suggest explicitly stating the scope and who the "user" is! I ask for
this because I don't think we would do this to a control plane protocol
inside the service provider network for instance. Otherwise the document
provides a good summary of the efforts and how they could be applied in
future protocols.

Nits
- Expand OHAI, MASQUE, PPM
- Section 3.1 uses the term "target" whereas figure 4 and 5 uses "server"!

Thanks!
Dhruv

On Thu, Nov 17, 2022 at 12:02 AM IAB Executive Administrative Manager <
execd@iab.org> wrote:

> The IAB will discuss adoption of draft-kpw-iab-privacy-partitioning
> (Partitioning as an Architecture for Privacy) on the IAB stream at its
> meeting on 2022-12-07.
>
> The draft can be found here:
> https://datatracker.ietf.org/doc/draft-kpw-iab-privacy-partitioning/
>
> The agenda for the meeting will be posted 48 hours ahead of the meeting
> here: https://www.iab.org/wiki/index.php/Agenda
>
> Feedback about this draft can be sent in response to this mail on
> architecture-discuss@ietf.org, or to the IAB directly at iab@iab.org.
>
> _______________________________________________
> Architecture-discuss mailing list
> Architecture-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/architecture-discuss
>