Re: [dispatch] Bron's Large Email problem

Lucas Pardue <lucaspardue.24.7@gmail.com> Fri, 12 August 2022 00:24 UTC

Return-Path: <lucaspardue.24.7@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87C27C159496 for <dispatch@ietfa.amsl.com>; Thu, 11 Aug 2022 17:24:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.853
X-Spam-Level:
X-Spam-Status: No, score=-1.853 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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 tRSN_-rfBOwM for <dispatch@ietfa.amsl.com>; Thu, 11 Aug 2022 17:24:51 -0700 (PDT)
Received: from mail-qv1-xf30.google.com (mail-qv1-xf30.google.com [IPv6:2607:f8b0:4864:20::f30]) (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 1B26EC14F74A for <dispatch@ietf.org>; Thu, 11 Aug 2022 17:24:51 -0700 (PDT)
Received: by mail-qv1-xf30.google.com with SMTP id h8so14544340qvs.6 for <dispatch@ietf.org>; Thu, 11 Aug 2022 17:24:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc; bh=pMW0oVyq/7w5707Nc+Qc38Tj6lQdkUwHrrsW0dRiPD0=; b=YVxJp9Qm8YkvreTnkxUllqzWnKWfto3BkDY3YS3xxA/b9vUMD01BjQCABbe1sUl30h HZJ40cm+D2n7Oklhp/BTc5461DaWqOOenAKcf32cjn1rZx92ODla5YrQVjXbhIgQ75PN 3VU+iXOcruMTR0fu7RnUkc9dwvy8LQxVOpjS0HXvqSu3UQQOXuMOQk+CMbaDhytVwzMG c+qtNXa2ikZchcSkLFNFwElov38GH05ASIIf5GuXbULl9gzNoVhb7YvS2qTQ1Hvq1Xtb jEoyf+L7GKTDrNgldz0x9V9sVQtGlv2MOA3UiJp1gGb9k9+1r9u2hD+SSK3YBO3ErOE/ IJ1Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=pMW0oVyq/7w5707Nc+Qc38Tj6lQdkUwHrrsW0dRiPD0=; b=0Ah/e+PBAcIk80i3TWX0X/6M6fkB3XrdNg/oP0l14IZxGOTzy+Y/MX89BtvjPHpfYt LY5yC7inMJnfKeEO8dkmzj1Qi8wNd5zASxr7yTDzqF3zYr4YSTQlG6crhunBkxNqKdNW lDxuTkcMZYj67YKsXfdypxbNun3b0nJrE94DmFm8ZQ5QrYzD8JfUzNffkHFO0Pn21+sS G/Q5r4KJbBQNlfcpjkfCx82v6cc0oRHO4xCcjD68fcZDxz8agdv5UhgHYUUI6DtY3eUE aIi2pv8e3XPJBGENarrvz+fNWkGiAbsLW+XOv1zXAlLp8ZqFJ1q2/xsYqNk8/xPvRRpn R8Ng==
X-Gm-Message-State: ACgBeo3Sm4Nmsi/9Vk+yACGFwLLYlCeUUInOh2e51Vu8p/kB+7MfSuwm NWhuuIkBHuyfdfzkJEf84Zb3gf+VQ8vRTmcwamyGmFCh
X-Google-Smtp-Source: AA6agR6XkE2nbe9ELSWUq1xnC4CblRIeXzkD820a7ioopvwesLIKgXPYzfZBMVOTBvw3OoNBja4CU8hgWX/ldmgA634=
X-Received: by 2002:a05:6214:131:b0:476:73ea:406b with SMTP id w17-20020a056214013100b0047673ea406bmr1593993qvs.94.1660263889767; Thu, 11 Aug 2022 17:24:49 -0700 (PDT)
MIME-Version: 1.0
References: <18738.1660262896@localhost>
In-Reply-To: <18738.1660262896@localhost>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Fri, 12 Aug 2022 01:24:38 +0100
Message-ID: <CALGR9obnAHggY157BTagmskuQD_ygHy-8n-Q7BSFNR42zdvjtA@mail.gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: DISPATCH WG <dispatch@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000062162505e6004f04"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/lAaITSjNFlIPfzX9LRLq_oaTOKA>
Subject: Re: [dispatch] Bron's Large Email problem
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Aug 2022 00:24:55 -0000

Hey Michael,

To respond to one point on recordings:

On Fri, Aug 12, 2022 at 1:08 AM Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> Having just watched DISPATCH from 2022-07-25, I want to encourage Bron and
> others to continue work on this problem.
>
> It seems that we ought to spin up a ML for this discussion: we could write
> a
> clearer problem statement and come back to dispatch.  It might be trivially
> enough a solution that it will fit into another WG, or AD-sponsor.
>
> I had to slow down my playback to catch what Mark Nottingham said.
> (that's a cool thing... black background... floating head.)
> I think that he said:
>    * prone to over-engineering
>    * the most obvious way to do this is fragment identifiers
>    ( http://foo.example/bar#IDENTIFIER )
> Alas, the chat is not recorded by the youtube version.
>

In case folks have missed it, the sessions can also be replayed via
meetecho, which provides on a single page the video, time-synced chat logs,
and a searchable transcript. For instance, the IETF 114 DISPATCH session is
available at

https://play.conf.meetecho.com/Playout/?session=IETF114-DISPATCH-20220725-1400

These sessions can be found at https://www.meetecho.com/ietf114/recordings
or via the "Session recording" button on each session in
https://datatracker.ietf.org/meeting/agenda

Personally, I found this very useful to catch up on a few sessions where I
was double booked. So thanks to the folks behind this!

Cheers
Lucas


>
>