Re: [Model-t] Potential next steps with model-t & meeting

Eric Rescorla <ekr@rtfm.com> Tue, 05 April 2022 02:13 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: model-t@ietfa.amsl.com
Delivered-To: model-t@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C0573A10F5 for <model-t@ietfa.amsl.com>; Mon, 4 Apr 2022 19:13:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Level:
X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20210112.gappssmtp.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 m6mO87D64C6q for <model-t@ietfa.amsl.com>; Mon, 4 Apr 2022 19:13:10 -0700 (PDT)
Received: from mail-il1-x130.google.com (mail-il1-x130.google.com [IPv6:2607:f8b0:4864:20::130]) (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 972153A1DBD for <model-t@iab.org>; Mon, 4 Apr 2022 19:13:10 -0700 (PDT)
Received: by mail-il1-x130.google.com with SMTP id e9so8225795ilu.9 for <model-t@iab.org>; Mon, 04 Apr 2022 19:13:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=OCiKoTNlVoY27nAFSYopbvbyEWtMjkIwuS58OTop1QE=; b=HiUnxjua3rUbyI6FPQb53ZRu93CVSNFel9VScPW0ckVbb+bpZ8cHZ92NUsQMv/+LGk eUaXQdN+4m1NJsIfTi33B9NB5bIR5my8L6BLKL324qAc4TQBs8tN19pAIif4xWLyVhUA 2QkiktYXGvjU2s4lC1UEQ91oQF6S11Y0DJmsLoNAcZWfcBo7qGrGHJkMp6ltYofNtEdB Zvhkh5R7XWn/VM5Cx+nP/crxoLFk4mUqq+w2XxETKJcVbaREXCsFwOx84x2B/l62USll jKLBJP7UFUxOfw/j67A1PqM2tHB6W50i7LqIjZ2AA9q1TEuYoLo6m10AqxBmNxUGTWIP bDIQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=OCiKoTNlVoY27nAFSYopbvbyEWtMjkIwuS58OTop1QE=; b=iGUZlpgWmq7kirQmV8yABotbNSMrGw1R/M5ntUJL78P8uXwlBtGC4IC0drn3LUc9Rz wmrGYRGgdGBofdpjYTP4JvDyjxcAiyFOnXbwpa3rbKouCyWfIyY4W6KfQyjVpJqVyraV f/WV6R013DWwTGBQ/RQoHFvRQpEeapRC9EsUS182cUJGJiNdMMr29RPbZmBb+mlJh4fO 0M/3geSopPu5MamsPBW5ufI/T9FePfXKXpL2m0Rqgi0XO/bYB/0nnay3ZKJFOyr0Zh+m Ka6h8W6H2UOMbK49W8g/fQWXMDIhfPpWlLbVu31AAqsd9JSU1Q5cX2AaKQ4l/0mPzV1A fUKA==
X-Gm-Message-State: AOAM531HMb4P/Y+SYGuJEmO2mNvGVAgq6VmBnue1IxKyjjDtce7W4ogc aMqjrDan/Zyn0FdcFkvRBc+AqUGd1h256SP5okAGpGH8F6A=
X-Google-Smtp-Source: ABdhPJxX2IoegDwPBC5yX/orwccRnJkT5GWGrrqTpNeAPzUBtoiUkZsTVAIWX8992mIOo3Q2y5z3F6ER1tKUR7S/CBQ=
X-Received: by 2002:a92:d2cf:0:b0:2ca:34e9:8b8a with SMTP id w15-20020a92d2cf000000b002ca34e98b8amr604367ilg.10.1649124789413; Mon, 04 Apr 2022 19:13:09 -0700 (PDT)
MIME-Version: 1.0
References: <E03CFB96-614A-4C7A-9895-FB719D9FB9D1@piuha.net>
In-Reply-To: <E03CFB96-614A-4C7A-9895-FB719D9FB9D1@piuha.net>
From: Eric Rescorla <ekr@rtfm.com>
Date: Mon, 04 Apr 2022 19:12:33 -0700
Message-ID: <CABcZeBN1dzSScGDX72OViJBs-wSOCC7_wnETsGUw0_Qigq=zDA@mail.gmail.com>
To: Jari Arkko <jari.arkko@piuha.net>
Cc: model-t@iab.org
Content-Type: multipart/alternative; boundary="0000000000004383b405dbdec94b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/model-t/L_jS6a4fjRJuJM50BmQdwwCu0PQ>
Subject: Re: [Model-t] Potential next steps with model-t & meeting
X-BeenThere: model-t@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussions of changes in Internet deployment patterns and their impact on the Internet threat model <model-t.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/model-t>, <mailto:model-t-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/model-t/>
List-Post: <mailto:model-t@iab.org>
List-Help: <mailto:model-t-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/model-t>, <mailto:model-t-request@iab.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Apr 2022 02:13:16 -0000

I doubt I will be able to make the meeting because I have a conflict. Mark,
any chance of a written summary of what you have come up with?

-Ekr


On Wed, Mar 23, 2022 at 10:39 AM Jari Arkko <jari.arkko@piuha.net> wrote:

>
> Hi,
>
> Since the December meeting we’ve had some amount of discussion on the
> list, including three drafts posted this year. I think we also have at one
> other document being worked that could be posted soon. I’m sorry we have
> not organised a meeting early in the year as promised in December, but I
> think there is some basis for moving forward.
>
> In the December meeting, we divided potentially useful things we could do
> in two categories:
>
> 1/ documenting specific design principles motivated by evolving situation,
> to be published as short IAB RFCs
> 2/ proposing a way forward to document a change in the threat model
>
> I did not actually form a design team of two people for item 1, but Martin
> and I have both discussed the documents and are trying to move them to a
> more reasonable state; mine in particular was heavily revised based on
> Martin’s input, and his draft was already in pretty good shape. My thought
> for this work item is that whatever we produce should not be an
> all-encompassing-cover-everything documents, but address specific, narrow
> issues that we believe are reasonable guidance at present time. The IAB is
> I think happy to publish documents, particularly when there are member(s)
> in the IAB that act as drivers for taking the documents through, which I
> think we have. Given the desire for specific guidance, the effort at least
> when it came to my document was to distill it more to the essential general
> principle. In my case the principle is about being careful about what data
> gets sent out (“only do it on a need-to-know-basis”), and in Martin’s case
> it is about being careful about the use of intermediaries. These are of
> course suggested drafts and principles, we can replace them with other
> ideas or change them if needed.
>
> Mark had formed a design team for item 2, worked on a proposal, and
> organised a small meeting to talk about it. Mark, could you report on where
> you think you are?
>
> I’d like to suggest a meeting in the weeks after the IETF. I realise the
> usual participants are from around many different timezones, so it seems
> appropriate to have a poll about the potential times for the meeting. The
> poll is here, please vote:
> https://doodle.com/meeting/participate/id/DbDg6Eka
>
> Thoughts and comments on any of this?
>
> For further information, see:
>
> Archive: https://mailarchive.ietf.org/arch/browse/model-t/
> Notes from December:
> https://github.com/intarchboard/program-model-t/blob/master/notes/notes-2021-12-07.md
> Potential input drafts for work item 1, principles:
> https://datatracker.ietf.org/doc/html/draft-thomson-tmi-03 and
> https://datatracker.ietf.org/doc/html/draft-arkko-iab-data-minimization-principle
>
> Other drafts posted to the list:
> https://datatracker.ietf.org/doc/html/draft-bertola-everything-but-the-user
>
>
> Jari
>
>
> --
> Model-t mailing list
> Model-t@iab.org
> https://www.iab.org/mailman/listinfo/model-t
>