From nobody Sun Jan 17 19:55:35 2021 Return-Path: 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 8E7A33A0CD5 for ; Sun, 17 Jan 2021 19:55:33 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.101 X-Spam-Level: X-Spam-Status: No, score=-2.101 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b=lDTctgYN; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=QX+yKfJO 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 z6SkKy9YhCVq for ; Sun, 17 Jan 2021 19:55:32 -0800 (PST) Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8CB8B3A0CC0 for ; Sun, 17 Jan 2021 19:55:32 -0800 (PST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 06E471521 for ; Sun, 17 Jan 2021 22:55:28 -0500 (EST) Received: from imap10 ([10.202.2.60]) by compute1.internal (MEProxy); Sun, 17 Jan 2021 22:55:29 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:date:from:to:subject:content-type; s= fm1; bh=DzlBHcuLTxoE5B+ttl+F4DSemoHwyFq0ObqQt5ngajU=; b=lDTctgYN HbYih8A7oLlvvzOLs3d0owfJYJ5dZGDs3j2LRVcdZXJZ5tZkR7YLHpwjhCAMs1DF Ax5AbEU4a7hH5fX3+v0Ze3s5qZKxDuHJj5SQ5PUzON/E96zrD3Jn9QyCph/JPHyY UVu+dj+smV8QlGNQWNZtN1PGWcSazFJAGhpk1edOqWVCLxMLymQUTrbvZ+8u/miT lVdlXgZj88Rilc+bUzbI6IEnaww7KG9emII80vFTG6mY3kvmxQHPnxZi8RI3I1hm cBPCYhPH3WBA12ejhwiP7ItV3oowVOYUj05z+G1iAE3YCH1oXn1NmQHQn7yZnJWR McywfHWErrtGJg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=DzlBHcuLTxoE5B+ttl+F4DSemoHwy Fq0ObqQt5ngajU=; b=QX+yKfJO+t5uQs3RlwbVJqMDGm1YUaI19YwlJkrVrLL1N zYTC/FDBnfQh13VHbhelsq7KuHGuyt2i/39JF7ZL2R2T6Q6aQV9zNLnb0LF34HA8 6Sk6B13wGT8tTTVuv6yQT6nCAo/eemLDTPlYS9e/I/TpPL1OGv3T/7uZ0Mys5u0/ lIH4bINit7Ugu1gRQk/u2U5Y+4vk6yo019uR2gTHiCjIGl/oZPWb0w6jydi3jqNd PJBTKlr5AUxmG0U4nJJdTTV6BSLYOwoLub/8HKBlOiqnSpVb7yKeqjs5a/AYbQdr m6gTt82BvXiweg29NrlRWOuzyXWJpwKmN5hB65rsQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrtdejgdeigecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkfffhvffutgesthdtredtre ertdenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehlohifvghn thhrohhphidrnhgvtheqnecuggftrfgrthhtvghrnhepvefguddtgfejfeduueehkeehke duueegheefgeevkeekgeelveevffeuudffheehnecuvehluhhsthgvrhfuihiivgeptden ucfrrghrrghmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhrohhphidrnhgvth X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 2F5CA200C5; Sun, 17 Jan 2021 22:55:28 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.5.0-alpha0-45-g4839256-fm-20210104.001-g48392560 Mime-Version: 1.0 Message-Id: <56b88e14-1bb2-4e9c-8439-2721169ba29b@www.fastmail.com> Date: Mon, 18 Jan 2021 14:55:09 +1100 From: "Martin Thomson" To: dispatch@ietf.org Content-Type: text/plain Archived-At: Subject: [dispatch] Cutoff for 110? X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jan 2021 03:55:34 -0000 I'm looking at the wiki and its very much out of date. Based on the one example of the dates in the Wiki, the dates might have passed already, but I haven't seen any notices to the list. Where are we at? (Answer to the obvious question: I'm working on something with others, but it's not quite ready yet.) From nobody Mon Jan 18 13:17:39 2021 Return-Path: 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 6E4923A0B39 for ; Mon, 18 Jan 2021 13:17:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EOOMOIOh4YIf for ; Mon, 18 Jan 2021 13:17:36 -0800 (PST) Received: from mail-ot1-x331.google.com (mail-ot1-x331.google.com [IPv6:2607:f8b0:4864:20::331]) (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 78B1D3A03F3 for ; Mon, 18 Jan 2021 13:17:28 -0800 (PST) Received: by mail-ot1-x331.google.com with SMTP id n42so17672670ota.12 for ; Mon, 18 Jan 2021 13:17:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=CLvpTp1FaC4Zu32h0By9LxAjKT0shFLvsk6IU/nHGvw=; b=rbY+HMQx3m54OfibeNBz1A6CUUyAZdJs55CrmXKAFZdGP3reLaufWI+Ccc0xYWhrkJ UTiM6FfoHa8kVBHSKGX7rXErIhwcMloADT8qIwst0wzMQRyvv5p3Q+CrWUTujCOtTPwk xK5UVFn8ZA7fvI9fiS4baYNTbJkjS+endV0U1ElvOHCL6ZjlQPrhx0c1HYnbePFPOFAr iIKvfsb6wF7jM190n0fbjxm2ARM8k4ND8T1xT0UklNfkmqr3n7h9JLuk3z1ODSxVldzw H+bzGD1HM8VIGerp6ip0vSnLb4csxboVzifSbfcW/pX6Q4UkWT84PHQrR2k4hbLzYBGO 0rYg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=CLvpTp1FaC4Zu32h0By9LxAjKT0shFLvsk6IU/nHGvw=; b=BS0axPsRpow+eDyG7NJHznWGLkFTPFcONilrbPaTV6H2+v1xJ/Ql4m4d4R6UxCAmt8 +na7cGZsLCl+PxPvLX+/CVm1FLpX817OejsTKqvS9krBsRF30tk7qR53qsMGfj7FFFhe jl2ZpKm5YIylAzvgYDkQ8OdYFV38kmTV/nnPiXw8NmYOJGp9HA4aYAsJlBSb4Xa0rCMw PcdhRiWAPbDUuOXEf6jnUfDujr894r4RNy+UjNSA/g/1rj9kVemSWAFJkGMvliYr3CM+ HrpVz0JNujCbqmPjjMjquNFHxlL8nsv816c1rSNiTloNfBrrA2M0MSjpLL89v2zGFFqR ph5Q== X-Gm-Message-State: AOAM531C/oduKQjfL9PyEeCW1jPcMT5KQRzBYGSl89DBcnwZYKUS9NxH E6JIb8atCaMMNu7WgjAg7Q1EH1W4uFHW8Axf/jJQ6lqk X-Google-Smtp-Source: ABdhPJwTWQbQpTKKO5MLO5FezbpzWvMQCLK+Np/YP9L9H/fB0wGI2h6iJWjJ4SHXtq2lePFytQjTPrvtmsmTBbvZdvg= X-Received: by 2002:a9d:3e2:: with SMTP id f89mr1102202otf.278.1611004647689; Mon, 18 Jan 2021 13:17:27 -0800 (PST) MIME-Version: 1.0 References: <56b88e14-1bb2-4e9c-8439-2721169ba29b@www.fastmail.com> In-Reply-To: <56b88e14-1bb2-4e9c-8439-2721169ba29b@www.fastmail.com> From: Mary Barnes Date: Mon, 18 Jan 2021 15:17:16 -0600 Message-ID: To: Martin Thomson Cc: DISPATCH Content-Type: multipart/alternative; boundary="000000000000c1d1fd05b9333fdb" Archived-At: Subject: Re: [dispatch] Cutoff for 110? X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jan 2021 21:17:39 -0000 --000000000000c1d1fd05b9333fdb Content-Type: text/plain; charset="UTF-8" That's because no one has updated the wiki since I was removed as a co-chair. Personally, I found it extremely helpful to have the dates there and to keep up with how work items were dispatched since names of activities change. But, that's for the new chairs to decide if they want to spend the time on it (I did it as part of pre- and post- meeting activities). As far as IETF-110 dates, I had expected to find them at least in the IETF-109 chair slides, but they're not there either. So, I guess there are no deadlines other than the draft deadline this time :) Regards, Mary. On Sun, Jan 17, 2021 at 9:55 PM Martin Thomson wrote: > I'm looking at the wiki and its very much out of date. Based on the one > example of the dates in the Wiki, the dates might have passed already, but > I haven't seen any notices to the list. Where are we at? > > (Answer to the obvious question: I'm working on something with others, but > it's not quite ready yet.) > > _______________________________________________ > dispatch mailing list > dispatch@ietf.org > https://www.ietf.org/mailman/listinfo/dispatch > --000000000000c1d1fd05b9333fdb Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
That's because no one has updated the wiki since I was= removed as a co-chair.=C2=A0 Personally, I found it extremely helpful to h= ave the dates there and to keep up with how work items were dispatched sinc= e names of activities change.=C2=A0 But, that's for the new chairs to d= ecide if they want to spend the time on it (I did it as part of pre- and po= st- meeting activities).

As far as IETF-110 dates, I had= expected to find them at least in the IETF-109 chair slides, but they'= re not there either.=C2=A0

So, I guess there are n= o deadlines other than the draft deadline this time :)

Regards,
Mary.=C2=A0

On Sun, Jan 17, 2021 at 9:55 P= M Martin Thomson <mt@lowentropy.net= > wrote:
= I'm looking at the wiki and its very much out of date.=C2=A0 Based on t= he one example of the dates in the Wiki, the dates might have passed alread= y, but I haven't seen any notices to the list.=C2=A0 Where are we at?
(Answer to the obvious question: I'm working on something with others, = but it's not quite ready yet.)

_______________________________________________
dispatch mailing list
dispatch@ietf.org
https://www.ietf.org/mailman/listinfo/dispatch
--000000000000c1d1fd05b9333fdb-- From nobody Mon Jan 18 13:52:08 2021 Return-Path: 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 9A2D03A1D95 for ; Mon, 18 Jan 2021 13:52:01 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TVwzJxfju0S5 for ; Mon, 18 Jan 2021 13:51:59 -0800 (PST) Received: from mail-vk1-xa2d.google.com (mail-vk1-xa2d.google.com [IPv6:2607:f8b0:4864:20::a2d]) (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 48D463A0D50 for ; Mon, 18 Jan 2021 13:48:40 -0800 (PST) Received: by mail-vk1-xa2d.google.com with SMTP id m145so4328863vke.7 for ; Mon, 18 Jan 2021 13:48:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0n1AW1FBLuRwABraYDunIuNDzmOsq68TegDIoQH9DEE=; b=KSD5Umu+1SWvf/NDMCff1Nk6fm4126kbSEGlbS6S1CmH8RYdlEi7ycfKGCqpNLZYPW fUo8AQu5+D7sw+bv6z/6hqOsmQ4pRVeX/1G6NY1G4dd/1ypF4IPtHMYSGlvIs7FAe4TD xzta3m+xeXX7CNtqN9peg73BQ05Y/8I6hS2DxIucdkstzl/aFvlA4djNPYlwCR/QMp72 GMPNM8sAlLwssH6x43jE4BQtIau8xxIeqlnYG1qjuwNuIFxGI2ZmisjD8pwKnU9E0bWX bprXXY/UOf/QxX2JWZOZVsVpktdalCnsbp5A12QRMcqxlyJyHqvQik5WUOyA/WbMPUC0 eaOg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=0n1AW1FBLuRwABraYDunIuNDzmOsq68TegDIoQH9DEE=; b=k1JYEyDn2Cflr33BcKDI71+V6woY3VqFJe4MYurupCE1QI+dlZ4HcByYOG6ET0TFFk ml8a6qL5OeY7qv35z+ROJWBRE119EkzFGRWQgT0ByahR20DmeHxamlPKGUfBhg4aKBhb ja/PB4ntL4YHYXXbEXKpfBzedcygYDx2sqmWnkzUq3iSPnqzYf4RPfRyrUzXk5UT5ssJ EvyVLQMSatkj+sRqrgTQ/QiamcrP63wEjTRdq9mMufKTakt1lFwz58yIgchrW0rx259T lxaOWJ3fUH920swx3TzJ6+V3WiI9Q9g8ROFvK4t1p7lBuvIOKnfxYLlI4IowXJxC07TH RkmA== X-Gm-Message-State: AOAM530w2++lT1l+Txy6OzGNVIm8CD0uAccp3gxJH/Isv5w8LxdRNQx/ S7JBOXpCfH27RQGDsPd13th41ZEWC7AIjN61q8o= X-Google-Smtp-Source: ABdhPJwuXfQCljNa88GVf32vUcw63RbpDnv9kDky8yDNYPDjTx3IfmhUakaHNdwHcCuJg+/sPc0kTLjxYvwJxbvjYwo= X-Received: by 2002:a1f:a796:: with SMTP id q144mr1234544vke.19.1611006519322; Mon, 18 Jan 2021 13:48:39 -0800 (PST) MIME-Version: 1.0 References: <56b88e14-1bb2-4e9c-8439-2721169ba29b@www.fastmail.com> In-Reply-To: From: Ira McDonald Date: Mon, 18 Jan 2021 16:48:22 -0500 Message-ID: To: Mary Barnes , Ira McDonald Cc: Martin Thomson , DISPATCH Content-Type: multipart/alternative; boundary="00000000000050aba205b933af90" Archived-At: Subject: Re: [dispatch] Cutoff for 110? X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jan 2021 21:52:08 -0000 --00000000000050aba205b933af90 Content-Type: text/plain; charset="UTF-8" Hi, All the usual deadlines for IETF 110 are here in the Datatracker: https://datatracker.ietf.org/meeting/important-dates/ Cheers, - Ira *Ira McDonald (Musician / Software Architect)* *Chair - SAE Trust Anchors and Authentication TF* *Co-Chair - TCG Trusted Mobility Solutions WG* *Co-Chair - TCG Metadata Access Protocol SG* *Chair - Linux Foundation Open Printing WGSecretary - IEEE-ISTO Printer Working GroupCo-Chair - IEEE-ISTO PWG Internet Printing Protocol WGIETF Designated Expert - IPP & Printer MIBBlue Roof Music / High North Inchttp://sites.google.com/site/blueroofmusic http://sites.google.com/site/highnorthinc mailto: blueroofmusic@gmail.com (permanent) PO Box 221 Grand Marais, MI 49839 906-494-2434* On Mon, Jan 18, 2021 at 4:17 PM Mary Barnes wrote: > That's because no one has updated the wiki since I was removed as a > co-chair. Personally, I found it extremely helpful to have the dates there > and to keep up with how work items were dispatched since names of > activities change. But, that's for the new chairs to decide if they want > to spend the time on it (I did it as part of pre- and post- meeting > activities). > > As far as IETF-110 dates, I had expected to find them at least in the > IETF-109 chair slides, but they're not there either. > > So, I guess there are no deadlines other than the draft deadline this time > :) > > Regards, > Mary. > > On Sun, Jan 17, 2021 at 9:55 PM Martin Thomson wrote: > >> I'm looking at the wiki and its very much out of date. Based on the one >> example of the dates in the Wiki, the dates might have passed already, but >> I haven't seen any notices to the list. Where are we at? >> >> (Answer to the obvious question: I'm working on something with others, >> but it's not quite ready yet.) >> >> _______________________________________________ >> dispatch mailing list >> dispatch@ietf.org >> https://www.ietf.org/mailman/listinfo/dispatch >> > _______________________________________________ > dispatch mailing list > dispatch@ietf.org > https://www.ietf.org/mailman/listinfo/dispatch > --00000000000050aba205b933af90 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

All the usual deadlines = for IETF 110 are here in the Datatracker:


Cheers,<= /div>
- Ira

=
Ira McDonald (Musician / Software Arch= itect)
Chair - SAE Trust Anchors a= nd Authentication TF
Co-Chair - TCG Trusted Mobility Solutions WG
Co-Chair - TCG Metadata Access Protocol SG
Chair - Linux Foundation Open Printi= ng WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-IST= O PWG Internet Printing Protocol WG
IETF Designated Expert - IPP & P= rinter MIB
Blue Roof Music / High North Inc
http://sites.google.com/site/blueroofmusic
http://sites.google.com/site/highnorthinc
mailto: blueroofmusic@gmail.com
(permanent) PO Box 221=C2=A0 Grand Marais, MI 49839=C2=A0 906-494-243= 4


On Mon, Jan 18= , 2021 at 4:17 PM Mary Barnes <mary.ietf.barnes@gmail.com> wrote:
That's because no one= has updated the wiki since I was removed as a co-chair.=C2=A0 Personally, = I found it extremely helpful to have the dates there and to keep up with ho= w work items were dispatched since names of activities change.=C2=A0 But, t= hat's for the new chairs to decide if they want to spend the time on it= (I did it as part of pre- and post- meeting activities).

As far as IETF-110 dates, I had expected to find them at least in the IET= F-109 chair slides, but they're not there either.=C2=A0

<= /div>
So, I guess there are no deadlines other than the draft deadline = this time :)

Regards,
Mary.=C2=A0

On Sun, Jan 17, 2021 at 9:55 PM Martin Thomson <mt@lowentropy.net> wrote:
I'm looking at the w= iki and its very much out of date.=C2=A0 Based on the one example of the da= tes in the Wiki, the dates might have passed already, but I haven't see= n any notices to the list.=C2=A0 Where are we at?

(Answer to the obvious question: I'm working on something with others, = but it's not quite ready yet.)

_______________________________________________
dispatch mailing list
dispatch@ietf.org
https://www.ietf.org/mailman/listinfo/dispatch
_______________________________________________
dispatch mailing list
dispatch@ietf.org
https://www.ietf.org/mailman/listinfo/dispatch
--00000000000050aba205b933af90-- From nobody Mon Jan 18 15:21:49 2021 Return-Path: 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 A50713A0CCD for ; Mon, 18 Jan 2021 15:21:48 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.12 X-Spam-Level: X-Spam-Status: No, score=-2.12 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=jwlczuSi; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=K3ciQj1v 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 jmjTICQ5RRHv for ; Mon, 18 Jan 2021 15:21:46 -0800 (PST) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB0703A0CC7 for ; Mon, 18 Jan 2021 15:21:46 -0800 (PST) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id DB4935C01B4; Mon, 18 Jan 2021 18:21:45 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Mon, 18 Jan 2021 18:21:45 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=D KdhSameFVIKDaf2svpOmwjB7GHMWclaUqndiLLy+kg=; b=jwlczuSifMXrIMcA8 mcsLBXBLt8X5K3ZCymLsP/pgxcJmhsS9jyWiJIsKX+w5g58IJDiBRBy7ir0A7Neo 3JZRozUhS33YhJrnB4r5b8H1ENjRBJvU+UJic6InQ2iYX0RKbmL0FuQhtiEDWryy 1bhkA8Hs4UsxfPrlI9UTaI3e+lYv5N4TbPDMsu8R+l8VV+IIe4WE5jiXfCFAv7Jc fj7K1dQ/lQyEvOTz0r+hitfyJ0Xw9OQkKQI4GN2CflX1YG7yDsOfOUAMyohuafxK 9UeYOXPSeLM419t0TAwI4DBLl7OTZj75g3hTxmZaVnin5pZqCynCtwGN4zr/cdzl zb2pQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=DKdhSameFVIKDaf2svpOmwjB7GHMWclaUqndiLLy+ kg=; b=K3ciQj1vbyM+dji6josm66rp1JDCsmDTKSkW32a/On8TIHMfhzs4EtRsc i/t/pWGpLeXEiD4tG9y+eBkUgKq1Is2qlT39qw4Ebxic4B2yqMtftBKLSaGbMluy Q/8bLpDl9movRCeT6FURSHi54FtoPoCHkw/BYY4HgW+NO2xrBI3SKfOxuEben8Xe jI0rbj1vk+WFpYA0zvXZjlwdTFGRsTKt0/PtvxvdmI/yl6YU+4mqB+lEGNw7laM5 1QM68PKElmbqYSME9xX28vBBwRLlczE+i16m4g4mgsEWxTANCmOYBh3J4Lxtr6Dp PTjMZyK23AKvYP17J6hXXS9TPX+xg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrtdelgddtjecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtddvnecuhfhrohhmpeforghrkhcu pfhothhtihhnghhhrghmuceomhhnohhtsehmnhhothdrnhgvtheqnecuggftrfgrthhtvg hrnhepkeduvdeljeegtefhveekhfdtveekleevkeefgeeludeihfdugedvieeuffdttdfh necuffhomhgrihhnpehivghtfhdrohhrghdpmhhnohhtrdhnvghtnecukfhppeduudelrd dujedrudehkedrvdehudenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgr ihhlfhhrohhmpehmnhhothesmhhnohhtrdhnvght X-ME-Proxy: Received: from [192.168.7.30] (119-17-158-251.77119e.mel.static.aussiebb.net [119.17.158.251]) by mail.messagingengine.com (Postfix) with ESMTPA id EB65D24005E; Mon, 18 Jan 2021 18:21:43 -0500 (EST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\)) From: Mark Nottingham In-Reply-To: Date: Tue, 19 Jan 2021 10:21:41 +1100 Cc: Martin Thomson , DISPATCH Content-Transfer-Encoding: quoted-printable Message-Id: References: <56b88e14-1bb2-4e9c-8439-2721169ba29b@www.fastmail.com> To: Mary Barnes X-Mailer: Apple Mail (2.3654.40.0.2.32) Archived-At: Subject: Re: [dispatch] Cutoff for 110? X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jan 2021 23:21:49 -0000 I'd interpret the current situation being 'no deadlines' as well. If so, that's a good outcome; I always found the seeming rigidity* of = the DISPATCH process distinctly unwelcoming, especially in a group = that's very likely to be someone's first experience of the IETF. Regardless of whether there are deadlines or not, I think DISPATCH has a = duty to clearly document and publicise its processes, expectations and = norms. Expecting them to find RFC7957 is *not* adequate. Cheers, * I know that there was supposed to be flexibility in the dates, etc., = but that was less than clear unless you were an 'insider.' > On 19 Jan 2021, at 8:17 am, Mary Barnes = wrote: >=20 > That's because no one has updated the wiki since I was removed as a = co-chair. Personally, I found it extremely helpful to have the dates = there and to keep up with how work items were dispatched since names of = activities change. But, that's for the new chairs to decide if they = want to spend the time on it (I did it as part of pre- and post- meeting = activities). >=20 > As far as IETF-110 dates, I had expected to find them at least in the = IETF-109 chair slides, but they're not there either.=20 >=20 > So, I guess there are no deadlines other than the draft deadline this = time :) >=20 > Regards, > Mary.=20 >=20 > On Sun, Jan 17, 2021 at 9:55 PM Martin Thomson = wrote: > I'm looking at the wiki and its very much out of date. Based on the = one example of the dates in the Wiki, the dates might have passed = already, but I haven't seen any notices to the list. Where are we at? >=20 > (Answer to the obvious question: I'm working on something with others, = but it's not quite ready yet.) >=20 > _______________________________________________ > dispatch mailing list > dispatch@ietf.org > https://www.ietf.org/mailman/listinfo/dispatch > _______________________________________________ > dispatch mailing list > dispatch@ietf.org > https://www.ietf.org/mailman/listinfo/dispatch -- Mark Nottingham https://www.mnot.net/ From nobody Fri Jan 22 07:05:38 2021 Return-Path: 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 6F5E53A12F9 for ; Fri, 22 Jan 2021 07:05:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.471 X-Spam-Level: X-Spam-Status: No, score=-2.471 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.373, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ducksong.com header.b=Ar5MN/md; dkim=pass (2048-bit key) header.d=outbound.mailhop.org header.b=MMGL8Rlc 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 ukF6SZ1TAi_H for ; Fri, 22 Jan 2021 07:05:34 -0800 (PST) Received: from outbound5d.ore.mailhop.org (outbound5d.ore.mailhop.org [100.20.105.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44BCE3A12E7 for ; Fri, 22 Jan 2021 07:05:33 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1611327934; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=tTsgIKlvbxN1tpPYTgXPPkq7qqQwSZNHobh76DKoKoMfXZSBHA7MPLp34KEARMAIYZcG1u46G0Ncm uEHQTNHQD33ObgQhHdPq5N0bYuxcZRqOV7kZFZsijzgurH19f17XoLYS+gUK/Oz2yg+4gUcNkIQRF2 +npLvl3DqI+WXCng5/Sh+U2lcwg5J4QxnQp+wVUrJKSpdacEOXaJhxZJdS+Y8pFAEkfD11FkP06C0p QcpimjKpjO4qN+KWzP36X36dbtLQGMJTgjw7SCKZX1eC3p/H5AyH8g4VtEO40kbcvZZZFbX/lCkKti 4My9UjXAzFTdKVwnQi+WxumEt215gDw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-type:cc:to:subject:message-id:date:from:in-reply-to:references: mime-version:dkim-signature:dkim-signature:from; bh=qzU3PnQT2sMHukUlH6NqWpmBk7Avmq2bWKthn9nPxxs=; b=cm+0kRdjlYWCURyDlCYe4zOvsbbu05fQ3lVv5wTNtfJrbjKmMxJdcizMwda8unXUbmhD/RNduuCwr z6RexnB/qpxkfvL1x8EDj7gGDtXrrmIZ1yP297lqJX0Y8tf7o/kvFPfPcTafcPxlUwSFNBTLicOUwG oQbuVu9UNggs8IhKH03WZOE5HYf+muF6rYPh9VQFq++iaP0xS2NQvjKcVEYairVY57ZmtD0x3rGsZV sZswNcjlC3Ii/PWh9PbjD7TP5guw4InqMZKPSbLVnCuAA0q+j6RpUTw15q5ygxeNbbxEvA1AJzBX6G sG7pijJTBTwPZ2tXuuOsDSzVz7MZP6A== ARC-Authentication-Results: i=1; outbound3.ore.mailhop.org; spf=pass smtp.mailfrom=ducksong.com smtp.remote-ip=209.85.167.173; dmarc=none header.from=ducksong.com; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ducksong.com; s=duo-1537391512170-ea99bbb3; h=content-type:cc:to:subject:message-id:date:from:in-reply-to:references: mime-version:from; bh=qzU3PnQT2sMHukUlH6NqWpmBk7Avmq2bWKthn9nPxxs=; b=Ar5MN/mdCuVtmoybFupSO5H9DaSdh4SA1hZNdA76WUSZ3wDz8s0uD8+tbFbOe3sUCN/ebNZO8Y/YF gw4m5Mlzvwnr1OeVzM+MdFP8MlCDOAhneFFHKf9STZbi77floE38RI4Xz7t0ju0hUXNDagSwvp2sMr lH+fFtaLbeRHS3Vw= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-type:cc:to:subject:message-id:date:from:in-reply-to:references: mime-version:from; bh=qzU3PnQT2sMHukUlH6NqWpmBk7Avmq2bWKthn9nPxxs=; b=MMGL8RlcpbPkMUZsNEBlmVqHUqgsa9+9jxgzktFpYodE2RPwCod98BKhWmaBPTq6AlbBscB/OpVx9 PfYnKZ2DEvvPLp4QoRr8pMwZNKZAuRv3lqIbqyix1qtyfRdppTRE4UCuMoTVj8EQy/3p7UC+64Gtzk hIod6tXsXiXEpuslMIwrR7NyO4uGwvBRcdxnOnqUWrrKHKtd3oRdJokdkArR+5871rzhA+5TIZWAj+ vNvNhPSIHPskGgOJBImVtpeT1aDlXDUkeoAyoUzJ3QYQx3TIV3G/iOiSiOI7wjYw/TbBiV/aQVKdip S0Plt0U7nIN4PssXvpWZh1yOlrv4XMA== X-Originating-IP: 209.85.167.173 X-MHO-RoutePath: bWNtYW51cw== X-MHO-User: 45588206-5cc3-11eb-8ba0-614106969e8d X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Mail-Handler: DuoCircle Outbound SMTP Received: from mail-oi1-f173.google.com (mail-oi1-f173.google.com [209.85.167.173]) by outbound3.ore.mailhop.org (Halon) with ESMTPSA id 45588206-5cc3-11eb-8ba0-614106969e8d; Fri, 22 Jan 2021 15:05:32 +0000 (UTC) Received: by mail-oi1-f173.google.com with SMTP id r189so6265491oih.4 for ; Fri, 22 Jan 2021 07:05:31 -0800 (PST) X-Gm-Message-State: AOAM533UNWy47JJcJXWbceC1EWb1ig6aYBOiNgFSegkBytLky5hzRl+N ruzPT6vhQM9N7Ie0hkqXfAYFqkG/knem8lY7c0M= X-Google-Smtp-Source: ABdhPJwrn0ARBqVz2WkWo8xyKcOYNvwpbPbO+y8diP5E8M51AXDKQPNyjzg0ROp7PD4KyF7t7jR45FxTWyHdVV23cEE= X-Received: by 2002:aca:d80a:: with SMTP id p10mr3612694oig.118.1611327931489; Fri, 22 Jan 2021 07:05:31 -0800 (PST) MIME-Version: 1.0 References: <56b88e14-1bb2-4e9c-8439-2721169ba29b@www.fastmail.com> In-Reply-To: From: Patrick McManus Date: Fri, 22 Jan 2021 10:05:20 -0500 X-Gmail-Original-Message-ID: Message-ID: To: Mark Nottingham Cc: Mary Barnes , DISPATCH Content-Type: multipart/alternative; boundary="000000000000f9293205b97e84dc" Archived-At: Subject: Re: [dispatch] Cutoff for 110? X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jan 2021 15:05:36 -0000 --000000000000f9293205b97e84dc Content-Type: text/plain; charset="UTF-8" We'll update the wiki. point taken. But yes, we're hoping to be more flexible with presentations and responsive to the mailing list in particular. So Martin, it might not be a bad idea to send a FYI with even a half-baked idea to the list. But its certainly not too late. If things are too busy we can do first come first served as necessary, but we don't seem to have that problem at the moment. -P On Mon, Jan 18, 2021 at 6:21 PM Mark Nottingham wrote: > I'd interpret the current situation being 'no deadlines' as well. > > If so, that's a good outcome; I always found the seeming rigidity* of the > DISPATCH process distinctly unwelcoming, especially in a group that's very > likely to be someone's first experience of the IETF. > > Regardless of whether there are deadlines or not, I think DISPATCH has a > duty to clearly document and publicise its processes, expectations and > norms. Expecting them to find RFC7957 is *not* adequate. > > Cheers, > > > * I know that there was supposed to be flexibility in the dates, etc., but > that was less than clear unless you were an 'insider.' > > > > > On 19 Jan 2021, at 8:17 am, Mary Barnes > wrote: > > > > That's because no one has updated the wiki since I was removed as a > co-chair. Personally, I found it extremely helpful to have the dates there > and to keep up with how work items were dispatched since names of > activities change. But, that's for the new chairs to decide if they want > to spend the time on it (I did it as part of pre- and post- meeting > activities). > > > > As far as IETF-110 dates, I had expected to find them at least in the > IETF-109 chair slides, but they're not there either. > > > > So, I guess there are no deadlines other than the draft deadline this > time :) > > > > Regards, > > Mary. > > > > On Sun, Jan 17, 2021 at 9:55 PM Martin Thomson > wrote: > > I'm looking at the wiki and its very much out of date. Based on the one > example of the dates in the Wiki, the dates might have passed already, but > I haven't seen any notices to the list. Where are we at? > > > > (Answer to the obvious question: I'm working on something with others, > but it's not quite ready yet.) > > > > _______________________________________________ > > dispatch mailing list > > dispatch@ietf.org > > https://www.ietf.org/mailman/listinfo/dispatch > > _______________________________________________ > > dispatch mailing list > > dispatch@ietf.org > > https://www.ietf.org/mailman/listinfo/dispatch > > -- > Mark Nottingham https://www.mnot.net/ > > _______________________________________________ > dispatch mailing list > dispatch@ietf.org > https://www.ietf.org/mailman/listinfo/dispatch > > --000000000000f9293205b97e84dc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
We'll update the wiki. point taken.

But yes, we're hoping to be more flexible=C2=A0with presentations and = responsive to the mailing list=C2=A0 in=C2=A0 particular. So Martin, it mig= ht not be a=C2=A0 bad idea to send a FYI with even a half-baked idea to the= list. But its certainly not too late. If things are too busy we can do fir= st come first served as necessary, but we don't seem to have that probl= em at the moment.

-P

On Mon, J= an 18, 2021 at 6:21 PM Mark Nottingham <mnot@mnot.net> wrote:
I'd interpret the current situation be= ing 'no deadlines' as well.

If so, that's a good outcome; I always found the seeming rigidity* of t= he DISPATCH process distinctly unwelcoming, especially in a group that'= s very likely to be someone's first experience of the IETF.

Regardless of whether there are deadlines or not, I think DISPATCH has a du= ty to clearly document and publicise its processes, expectations and norms.= Expecting them to find RFC7957 is *not* adequate.

Cheers,


* I know that there was supposed to be flexibility in the dates, etc., but = that was less than clear unless you were an 'insider.'



> On 19 Jan 2021, at 8:17 am, Mary Barnes <mary.ietf.barnes@gmail.com> wr= ote:
>
> That's because no one has updated the wiki since I was removed as = a co-chair.=C2=A0 Personally, I found it extremely helpful to have the date= s there and to keep up with how work items were dispatched since names of a= ctivities change.=C2=A0 But, that's for the new chairs to decide if the= y want to spend the time on it (I did it as part of pre- and post- meeting = activities).
>
> As far as IETF-110 dates, I had expected to find them at least in the = IETF-109 chair slides, but they're not there either.
>
> So, I guess there are no deadlines other than the draft deadline this = time :)
>
> Regards,
> Mary.
>
> On Sun, Jan 17, 2021 at 9:55 PM Martin Thomson <mt@lowentropy.net> wrote:
> I'm looking at the wiki and its very much out of date.=C2=A0 Based= on the one example of the dates in the Wiki, the dates might have passed a= lready, but I haven't seen any notices to the list.=C2=A0 Where are we = at?
>
> (Answer to the obvious question: I'm working on something with oth= ers, but it's not quite ready yet.)
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.o= rg
> https://www.ietf.org/mailman/listinfo/dispatch
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.o= rg
> https://www.ietf.org/mailman/listinfo/dispatch

--
Mark Nottingham=C2=A0 =C2=A0https://www.mnot.net/

_______________________________________________
dispatch mailing list
dispatch@ietf.org
https://www.ietf.org/mailman/listinfo/dispatch

--000000000000f9293205b97e84dc-- From nobody Fri Jan 22 21:33:36 2021 Return-Path: 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 5B5693A0C8B for ; Fri, 22 Jan 2021 21:33:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PHhq-3au08ey for ; Fri, 22 Jan 2021 21:33:30 -0800 (PST) Received: from mail-vk1-xa34.google.com (mail-vk1-xa34.google.com [IPv6:2607:f8b0:4864:20::a34]) (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 366753A0C86 for ; Fri, 22 Jan 2021 21:33:30 -0800 (PST) Received: by mail-vk1-xa34.google.com with SMTP id d23so1882085vkf.3 for ; Fri, 22 Jan 2021 21:33:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=pIbVVi2xQG75otd0s6hL8gur6tSrPirLqtJikoJgDXU=; b=NTJmVH/mDnk6mduRCxn6NUPWdLJHdJG0z1yc9OCo9OyhtwegwJwou6DuwbfmHnIDcB 79q64SVz/+Pg588pHDEfTynb5l6mBc9Na8LubgLvhEaLCsPJLE2i8AIspbjhVYmIL5BG 9AGvwwCk+nHvn1nWR8MUhx4F8vXbuU4TLi9U9jIZ0yGWjjrrRbK+/QV+ubv4EVIE0Kqn Fy+VWhqzjflvwTqdKfqWLipubDb9ocFSiYxJxQjiDOxTKPcIlm7pVlOoL3iB4kqBeaKC qYPHOXWqzi7kaD4inPEMOJDLxcSwZxs9fNrrJ3TycwA9YRxeRFjMUmehdtnnL3Jgc9sS myIw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=pIbVVi2xQG75otd0s6hL8gur6tSrPirLqtJikoJgDXU=; b=Zvg9nt0RcZj6j6gIDDtn4alsFh94E5OA8Zn0nsmKnZZbyiSucxU7ufc7/4FYQXkysF gVHWHrrPAw8xG2E3LmVqngYm+Q/bU/Sks4sAsmttUlTwp2jNe6daib7jZDtbxdCGc4JW ZtrTc1dgQxjHzfBfsDDsbe3ENLxnjmQceg56mUsPw6bzYWtIxpCUmQGpwvP+xzeEfpA6 CzFKA0g1CnP1ss1j1abMj7O0qwTiebuxQLjL1IquqT1GOGtSms0DaqZs5av1zi2JTJfi ryej1M3GZ5qz9ib8Cd0yxJfbp7nMaCLIZFiKNihzI2s9lxzlQLf227HZ7J4C8844KNz7 DAsQ== X-Gm-Message-State: AOAM531g7IfaOWFF0eiknT9cf70y8/+bx+5FFWE7bT4fwe/vkQzgDdrS h/+ygu9EqjlehigfFECVfo3PN33PCmFRrN74R4yohb9MROg= X-Google-Smtp-Source: ABdhPJzZnsVz76FJ96Somhaec1fnO+ZiBzP/JnXuVB9ZU18Xy/7MyDeMpn5OPgr2GdqX3UIxVpW7vNqq72yKKz0OlHc= X-Received: by 2002:ac5:cc75:: with SMTP id w21mr202762vkm.14.1611380009112; Fri, 22 Jan 2021 21:33:29 -0800 (PST) MIME-Version: 1.0 References: <87wnygveuv.fsf@hobgoblin.ariadne.com> In-Reply-To: From: "Murray S. Kucherawy" Date: Fri, 22 Jan 2021 21:33:11 -0800 Message-ID: To: Yeshwant Muthusamy Cc: "Dale R. Worley" , David Singer , Chris Ullrich , "dispatch@ietf.org" Content-Type: multipart/alternative; boundary="0000000000000a96fa05b98aa5c8" Archived-At: Subject: Re: [dispatch] Proposal to add 'haptics' as a new top-level media type - Comments welcome [Was RE: draft-muthusamy-dispatch-haptics-00.txt] X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Jan 2021 05:33:34 -0000 --0000000000000a96fa05b98aa5c8 Content-Type: text/plain; charset="UTF-8" What is the view of the working group in terms of appropriate processing for this work? How do we think it should be dispatched? Seems to me the only options are AD sponsorship (this is not me volunteering, yet) or spin up a working group to do it. I can't think of an existing working group with a charter in this space or close to it. -MSK On Fri, Nov 20, 2020 at 10:29 AM Yeshwant Muthusamy < ymuthusamy@immersion.com> wrote: > Hi Dale, > > Not sure if you were aware, but I posted a new version of the haptics I-D > late Sunday evening: > > https://datatracker.ietf.org/doc/draft-muthusamy-dispatch-haptics/ > > It was sent out just in time for my presentation in the DISPATCH session > at IETF 109. > > This new version (hopefully) addresses all the feedback that I received on > version 00, including draft registration of subtypes. > > Comments/questions welcome. > > Regards, > Yeshwant > > > Yeshwant Muthusamy, Ph.D. | Senior Director, Standards > > ymuthusamy@immersion.com | +1 469-583-2171 > > -----Original Message----- > From: Dale R. Worley > Sent: Thursday, November 19, 2020 10:20 PM > To: David Singer > Cc: dispatch@ietf.org; Chris Ullrich ; Yeshwant > Muthusamy > Subject: Re: [dispatch] Proposal to add 'haptics' as a new top-level media > type - Comments welcome [Was RE: draft-muthusamy-dispatch-haptics-00.txt] > > David Singer writes: > > I don't think we should mix up what's needed for sub-type > > registration, with establishment of the top-level type. Yeshwant can > > and should cite examples in the industry, but it's not for him to > > register other people's formats, of course. > > As a general rule, I agree. But in practice, the best thing to drive the > creation of a top-level media type is a bunch of subtypes that people > *want* to see registered. And the best thing to drive that is > minimally-encumbered interoperability. > > Dale > > _______________________________________________ > dispatch mailing list > dispatch@ietf.org > https://www.ietf.org/mailman/listinfo/dispatch > --0000000000000a96fa05b98aa5c8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
What is the view of the working group in terms of app= ropriate processing for this work?=C2=A0 How do we think it should be dispa= tched?

Seems to me the only options are AD sponsor= ship (this is not me volunteering, yet) or spin up a working group to do it= .=C2=A0 I can't think of an existing working group with a charter in th= is space or close to it.

-MSK

<= br>
On Fri,= Nov 20, 2020 at 10:29 AM Yeshwant Muthusamy <ymuthusamy@immersion.com> wrote:
Hi Dale,

Not sure if you were aware, but I posted a new version of the haptics I-D l= ate Sunday evening:

https://datatracker.ietf.org/doc/d= raft-muthusamy-dispatch-haptics/

It was sent out just in time for my presentation in the DISPATCH session at= IETF 109.

This new version (hopefully) addresses all the feedback that I received on = version 00, including draft registration of subtypes.

Comments/questions welcome.

Regards,
Yeshwant


Yeshwant Muthusamy, Ph.D. | Senior Director, Standards

ymuthusamy@im= mersion.com | +1 469-583-2171

-----Original Message-----
From: Dale R. Worley <worley@ariadne.com>
Sent: Thursday, November 19, 2020 10:20 PM
To: David Singer <singer=3D40apple.com@dmarc.ietf.org>
Cc: dispatch@ietf.or= g; Chris Ullrich <cullrich@immersion.com>; Yeshwant Muthusamy <ymuthusamy@immersion= .com>
Subject: Re: [dispatch] Proposal to add 'haptics' as a new top-leve= l media type - Comments welcome [Was RE: draft-muthusamy-dispatch-haptics-0= 0.txt]

David Singer <singer=3D40apple.com@dmarc.ietf.org> writes:
> I don't think we should mix up what's needed for sub-type
> registration, with establishment of the top-level type. Yeshwant can <= br> > and should cite examples in the industry, but it's not for him to =
> register other people's formats, of course.

As a general rule, I agree.=C2=A0 But in practice, the best thing to drive = the creation of a top-level media type is a bunch of subtypes that people *= want* to see registered.=C2=A0 And the best thing to drive that is minimall= y-encumbered interoperability.

Dale

_______________________________________________
dispatch mailing list
dispatch@ietf.org
https://www.ietf.org/mailman/listinfo/dispatch
--0000000000000a96fa05b98aa5c8-- From nobody Sun Jan 24 02:55:51 2021 Return-Path: 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 81FEC3A12D9 for ; Sun, 24 Jan 2021 02:55:48 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.118 X-Spam-Level: X-Spam-Status: No, score=-2.118 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=Hv77kU5Q; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=BsAsL4ha 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 opynasP8mbxZ for ; Sun, 24 Jan 2021 02:55:45 -0800 (PST) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90D563A12DB for ; Sun, 24 Jan 2021 02:55:45 -0800 (PST) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id B995C5C00B4; Sun, 24 Jan 2021 05:55:44 -0500 (EST) Received: from imap7 ([10.202.2.57]) by compute2.internal (MEProxy); Sun, 24 Jan 2021 05:55:44 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:date:from:to:cc :subject:content-type; s=fm1; bh=ApzrZVOijnZ8xo4VmkyTYdtH/Drveis qwgiXoVP7Hwk=; b=Hv77kU5Qb1038JesPNA+6yN29w+MMs/kU0eDChosI3NTXyi 1/RjZzX5PyJkMgLitvt93Jpb+C6brE8X9H96QUtl9TeCg01e221QRx/4Rq3qKrcA O09AuoJ27LG0eVwZ5u0t8IFsgCCKhFD3G9ektOFe1/AR/dDzx50kC44tS45+5wvd 2BsK2CueYNoDarLLcP93275szyuCkdQvM3l3EnrbfG4K2s40JUj10bJBLSZRVrsD cXydrdGTimbK5wEPEjxorHXTLm7bchtsB9nIUD0s+aGNNzvKBQwkGODLJ3tQvnBZ J3qPfwtDHwKKKfFjwPj6eym+21Vcv0214LMsTxQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:message-id :mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=ApzrZVOijnZ8xo4VmkyTYdtH/Drve isqwgiXoVP7Hwk=; b=BsAsL4han+atng+V7MHLyW/02IXj6rMZNWjEE6Vm9nPu/ 9HdVrQs2U4PMiCjq7AMHyOZIU/TdKAz8OrM4YKOLusARa5RtTYBqoFA5iH1r58sC zKPWgJxDxkTqkAyhXQve9zb2egX5uw2MsrH7BDPZFgW7zHfFu9uk5NWxFQVJLb1G 547JHbLiCGItmhyOAwkJhO6jxL0RGgn3+o7aC8bb30YtC1ZugKEO2tnQkAA0B56o EGkScjdZgE/YwUWNRAHXdL/IlmwVVNv2QPi3WB13SsEpyNGJZ+RkjzxbG3Z3SgsL yxYmlSDItA+8GtfXcHwrjVLDH3YaqS/wbDrsh8s4w== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvddugddvfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkfffhvffutgesrgdtreerre ertdenucfhrhhomhepfdeurhhonhcuifhonhgufigrnhgrfdcuoegsrhhonhhgsehfrghs thhmrghilhhtvggrmhdrtghomheqnecuggftrfgrthhtvghrnhepkefhtdfggefhjefggf efkeekuddvudegfffhfeduvdduffeijefhfeehjefhgedvnecuffhomhgrihhnpehivght fhdrohhrghdpghhithhhuhgsrdgtohhmnecuvehluhhsthgvrhfuihiivgeptdenucfrrg hrrghmpehmrghilhhfrhhomhepsghrohhnghesfhgrshhtmhgrihhlthgvrghmrdgtohhm X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 63C34360068; Sun, 24 Jan 2021 05:55:43 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.5.0-alpha0-78-g36b56e88ef-fm-20210120.001-g36b56e88 Mime-Version: 1.0 x-forwarded-message-id: Message-Id: Date: Sun, 24 Jan 2021 21:55:23 +1100 From: "Bron Gondwana" To: dispatch@ietf.org Content-Type: multipart/alternative; boundary=ff72aa2023e74aeb831e42a5745b507c Archived-At: Subject: [dispatch] Fwd: Re: [calsify] New Timestamp Draft X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jan 2021 10:55:49 -0000 --ff72aa2023e74aeb831e42a5745b507c Content-Type: text/plain Hi, A request for dispatching this work. I suggested a call for adoption on the calsify mailing list for adoption into the CALEXT working group, but the responses made it very clear that there isn't consensus there, including a response which states that it falls outside our current charter, which means the dispatch options will be either somewhere else or if to CALEXT, will include a requirement to recharter to allow it. Thanks, Bron. ----- Original message ----- From: Ujjwal Sharma To: calsify@ietf.org Subject: Re: [calsify] New Timestamp Draft Date: Friday, January 22, 2021 23:19 Hi Bron, CalExt Friends! I made a new revision of the draft, which shifts the focus to defining the syntax/format and defers the standardization of the actual key-value pairs to sibling organizations like IANA and Unicode Consortium. I'd love to hear your opinions on this version, which you can find at https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/, which can be filed as issues on the GitHub repository or emailed to me directly. In the meantime, I will address the remaining concerns/polish issues like fixing the references section. How "complete" does the document need to be in order to initiate the call for adoption? If the current version works, can we start it as soon as possible? Of course, if my understanding of "adoption" is correct, I'd be happy to iterate on the document further after the adoption by the WG. Best, Ujjwal On 14/01/2021 8.34 am, Bron Gondwana wrote: > Sounds great. Let me know :) > > When we do the call for adoption I'll also advertise the fact over to > the wider IETF - probably dispatch and tzdata lists at least. > > Cheers, > > Bron. > > > On Thu, Jan 14, 2021, at 13:48, Ujjwal Sharma wrote: >> Thanks Bron! >> >> I'll make a few more changes, release a 01 version, ask for more >> feedback and then let you know, hopefully by the end of this week. >> >> Ujjwal >> >> On 14/01/2021 7.03 am, Bron Gondwana wrote: >> > I can do a call for adoption straight away if you like - the next >> > meeting isn't for a couple of months. >> > >> > Bron. >> > >> > On Thu, Jan 14, 2021, at 05:24, Ujjwal Sharma wrote: >> >> One question: given things move forward smoothly, how do I proceed? >> >> Should I apply for this document to be adopted by the calext WG? I >> >> suppose the fastest way to proceed is to present it at the next IETF >> >> meeting? >> >> >> >> >> >> >> >> Ujjwal >> >> >> >> On 12/01/2021 4.03 am, Ujjwal Sharma wrote: >> >> > Hi Calsify folks! >> >> > >> >> > I am sorry for the long delay, I got a little sidetracked working on >> >> > other things, but I'm happy to inform you all that I have >> something that >> >> > resembles a first draft for the updated timestamps RFC. >> >> > >> >> > Here's where you can find it: >> >> > >> >> > Datatracker: >> >> >> > https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/ >> >> >> >> > > >> >> > >> >> >> GitHub: https://github.com/ryzokuken/draft-ryzokuken-datetime-extended >> >> >> > > >> >> > >> >> > I would request you all to take a look at it when you can and let me >> >> > know what you think. You can file a GitHub issue or email me >> directly. >> >> > >> >> > There's a few open discussions regarding the exact format and how the >> >> > interaction with bodies like the Unicode consortium work, so >> please feel >> >> > free to send me your thoughts regarding that as well. >> >> > >> >> > Also, some references/bibliography is not perfectly functional yet >> >> > because I am still relatively new to authoring RFCs using >> Metanorma but >> >> > I'm actively looking into it. >> >> > >> >> > Thanks and looking forward to hear from you, >> >> > Ujjwal >> >> > >> >> >> >> -- >> >> Ujjwal "Ryzokuken" Sharma (he/him) >> >> >> >> Compilers Hacker, Node.js Core Collaborator and Speaker >> >> >> >> _______________________________________________ >> >> calsify mailing list >> >> calsify@ietf.org > > >> >> https://www.ietf.org/mailman/listinfo/calsify >> >> >> > > >> >> >> > >> > -- >> > Bron Gondwana, CEO, Fastmail Pty Ltd >> > brong@fastmailteam.com >> > >> > >> > _______________________________________________ >> > calsify mailing list >> > calsify@ietf.org >> > https://www.ietf.org/mailman/listinfo/calsify >> >> > >> >> -- >> Ujjwal "Ryzokuken" Sharma (he/him) >> >> Compilers Hacker, Node.js Core Collaborator and Speaker >> >> _______________________________________________ >> calsify mailing list >> calsify@ietf.org >> https://www.ietf.org/mailman/listinfo/calsify >> >> > > -- > Bron Gondwana, CEO, Fastmail Pty Ltd > brong@fastmailteam.com > > > > _______________________________________________ > calsify mailing list > calsify@ietf.org > https://www.ietf.org/mailman/listinfo/calsify > -- Ujjwal "Ryzokuken" Sharma (he/him) Compilers Hacker, Node.js Core Collaborator and Speaker _______________________________________________ calsify mailing list calsify@ietf.org https://www.ietf.org/mailman/listinfo/calsify -- Bron Gondwana, CEO, Fastmail Pty Ltd brong@fastmailteam.com --ff72aa2023e74aeb831e42a5745b507c Content-Type: text/html Content-Transfer-Encoding: quoted-printable
Hi,

<= div style=3D"font-family:Arial;">A request for dispatching this work.&nb= sp; I suggested a call for adoption on the calsify mailing list for adop= tion into the CALEXT working group, but the responses made it very clear= that there isn't consensus there, including a response which states tha= t it falls outside our current charter, which means the dispatch options= will be either somewhere else or if to CALEXT, will include a requireme= nt to recharter to allow it.
=
Thanks,

Bron.

----- Original = message -----
From: Ujjwal Sharma <ryzokuken@igalia.com>
S= ubject: Re: [calsify] New Timestamp Draft
Date: Friday, Ja= nuary 22, 2021 23:19

Hi Bron, CalExt Friends!<= br>

I made a new revision of the draft, which shifts the focu= s to defining
the syntax/form= at and defers the standardization of the actual key-value
pairs to sibling organizations like IANA an= d Unicode Consortium.

I'd love to hear your opinions on t= his version, which you can find at
which can be f= iled as issues on the GitHub repository or emailed to me
directly. In the meantime, I will address th= e remaining concerns/polish
i= ssues like fixing the references section.

How "complete" = does the document need to be in order to initiate the
call for adoption? If the current version works= , can we start it as soon
as = possible? Of course, if my understanding of "adoption" is correct,
I'd be happy to iterate on the doc= ument further after the adoption by
the WG.

Best,
Ujjwal

On 14/01/2021 8.34 am, Bron Gondwana wrote:=
> Sounds great.  Let= me know :)
> 
> When we do the call for adopti= on I'll also advertise the fact over to
> the wider IETF - probably dispatch and tzdata lists at l= east.
> 
> Cheers,
> 
>= ; Bron.
> 
<= div style=3D"font-family:Arial;">> 
> On Thu, Jan 14, 2021, at 13:48, Ujjwal Sharma wrote:=
>> Thanks Bron!
>>
>> I'll make a few more changes, release a 01 ver= sion, ask for more
>> f= eedback and then let you know, hopefully by the end of this week.
>>
>> Ujjwal
>>
>> On 14/0= 1/2021 7.03 am, Bron Gondwana wrote:
>> > I can do a call for adoption straight away if you = like - the next
>> >= meeting isn't for a couple of months.
>> > 
>> > Bron.
>>= > 
>> > On = Thu, Jan 14, 2021, at 05:24, Ujjwal Sharma wrote:
>> >> One question: given things move f= orward smoothly, how do I proceed?
>> >> Should I apply for this document to be adopted b= y the calext WG? I
>> &= gt;> suppose the fastest way to proceed is to present it at the next = IETF
>> >> meetin= g?
>> >>
>> >>
>> >>
>> >> Ujjwal
>> >>
&g= t;> >> On 12/01/2021 4.03 am, Ujjwal Sharma wrote:
>> >> > Hi Calsify folks!<= br>
>> >> > <= br>
>> >> > I am s= orry for the long delay, I got a little sidetracked working on
=
>> >> > other things, b= ut I'm happy to inform you all that I have
>> something that
>> >> > resembles a first draft for the updated = timestamps RFC.
>> >= > > 
>> >= > > Here's where you can find it:
>> >> > 
>> >> > Datatracker:
>> >>
>> >>
>> >>
>&= gt; >> > 
>&= gt; >> > I would request you all to take a look at it when you = can and let me
>> >&= gt; > know what you think. You can file a GitHub issue or email me
>> directly.
>> >> > 
>> >> > There's a few open= discussions regarding the exact format and how the
>> >> > interaction with bodies like= the Unicode consortium work, so
>> please feel
>= > >> > free to send me your thoughts regarding that as well.=
>> >> > =
>> >> > Also,= some references/bibliography is not perfectly functional yet
<= div style=3D"font-family:Arial;">>> >> > because I am sti= ll relatively new to authoring RFCs using
>> Metanorma but
>> >> > I'm actively looking into it.
>> >> > 
>> >> > Thanks and looking= forward to hear from you,
&g= t;> >> > Ujjwal
&= gt;> >> > 
&= gt;> >>
>> >= ;> -- 
>> >&= gt; Ujjwal "Ryzokuken" Sharma (he/him)
>> >>
&= gt;> >> Compilers Hacker, Node.js Core Collaborator and Speaker=
>> >>
<= div style=3D"font-family:Arial;">>> >> _____________________= __________________________
&g= t;> >> calsify mailing list
>> <mail= to:calsify@ietf.org>>
<= /div>
>> >>
>&g= t; > 
>> > -= -
>> >   Bron G= ondwana, CEO, Fastmail Pty Ltd
>> > 
&= gt;> > 
>> &= gt; _______________________________________________
>> > calsify mailing list
>> > <= br>
>>
>> -- 
>> Ujjwal "Ryzokuken" Sharma (he/him)
>>
>> Compilers Hacker, Node.js Core Collaborator and Speaker
>>
>> __________________________________________= _____
>> calsify mailin= g list
>> https://www.ietf.org/mailman/listinfo/calsify
<= /div>
>><= br>
> 
> --
>   Bron Gondwana, CEO, Fastmail Pty Ltd
> 
> = ;
> 
> ________________________________________= _______
> calsify mailing = list
> 

-- 
Ujjwal "Ryzokuken" Sharma (he/him)<= br>

Compilers Hacker, Node.js Core Collaborator and Speaker

_______________________________________________
<= div style=3D"font-family:Arial;">calsify mailing list


=
--
  Bro= n Gondwana, CEO, Fastmail Pty Ltd
&nbs= p; brong@fastmailteam.com


--ff72aa2023e74aeb831e42a5745b507c-- From nobody Thu Jan 28 16:30:02 2021 Return-Path: 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 A50863A096C for ; Thu, 28 Jan 2021 16:29:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.101 X-Spam-Level: X-Spam-Status: No, score=-2.101 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b=VKqv1iQf; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Cmvx43us 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 o01RdzOEW_tp for ; Thu, 28 Jan 2021 16:29:53 -0800 (PST) Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1FF063A0147 for ; Thu, 28 Jan 2021 16:29:43 -0800 (PST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 6B1E11398 for ; Thu, 28 Jan 2021 19:29:42 -0500 (EST) Received: from imap10 ([10.202.2.60]) by compute1.internal (MEProxy); Thu, 28 Jan 2021 19:29:42 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:date:from:to:subject:content-type; s= fm1; bh=Vo76Cy4lNNuHhR2dCClx4pPKHQTSBrxZ3Kne4V2ObzA=; b=VKqv1iQf pXPQVDp4SLN87JeWhUGQUUGjlLO0Kawguz/wPHNLu7Qw0Cbj3OxSFuJ4TnkZ/bwv WJq1zl4lhHekm73eQMEVYy1tR9cFvV4npDE7yt86tfjEoJ2ll77mSrIzU2/7JYmQ TNUNfrh0RTNcFcaPgAZHGmSaEs7iEcPc7JyJPzsogQ5aQEyl29utOMZY++sBfRER j+nE4BVg1QbtoTiz9QLL3E0Kc4IIBrx9Y+pq8lvxkXFnV6AoF14Q7yeKGH3fK1v9 wIMMSS8GRPqGe3wDTsSo9MuQCOVfJSCSADStgm1GQ64jDyLoq/MWF5YTHZ2FxXe0 NIrHlWe0S4BTGg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=Vo76Cy4lNNuHhR2dCClx4pPKHQTSB rxZ3Kne4V2ObzA=; b=Cmvx43usxM0zR+vbVMEQEoq5cMNcdLTVRPjoiNzlHwcQx z0sFNe0lCxIphcZQ7Z8IvDRl9DhEcuXbSNIXWJG+kKmdYtldvd0awKCXedvKgho0 IBswlFU8VPB0iqTY0pzyQalgv2og/yjrLDaJialo+vUHNykpHC5m0Y98jI6RZkiW Xkr0FhsIU0S3pGInHp/9VRcUIFepRg8/K6NCBd9O37zv6WUog8TChWQkoJvWpYEo N8Jz5hO9jAqQpxmCXfkZU5CMZ+zgi0mIU4Yo+u5I4mNE0xUfGZ1L9Wwns9L9vMT0 r2D16dE/R1bugZDpuZEVMSmU+UaWnAJH0ODBY4Y7A== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfedugddulecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkfffhvffutgesthdtredtre ertdenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehlohifvghn thhrohhphidrnhgvtheqnecuggftrfgrthhtvghrnhepgfehieeggfeileekhfdthfdtff egjeffvdekudffgfeltddujefhieeihffhveegnecuffhomhgrihhnpehivghtfhdrohhr ghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmth eslhhofigvnhhtrhhophihrdhnvght X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 59D064E006B; Thu, 28 Jan 2021 19:29:41 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.5.0-alpha0-84-gfc141fe8b8-fm-20210125.001-gfc141fe8 Mime-Version: 1.0 Message-Id: <2c911f1e-67b0-4d52-9dd7-b468280a30ec@www.fastmail.com> Date: Fri, 29 Jan 2021 11:29:24 +1100 From: "Martin Thomson" To: dispatch@ietf.org Content-Type: text/plain Archived-At: Subject: [dispatch] FYI: Oblivious HTTP X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jan 2021 00:30:01 -0000 As a follow up to my previous email regarding schedule, in case people were curious, I've posted the work that I foreshadowed. After consideration, we've taken the work to SECDISPATCH. See https://mailarchive.ietf.org/arch/msg/secdispatch/VmFQCZGKlukgfnmgPh8ufQt_5Fo/ From nobody Fri Jan 29 11:05:38 2021 Return-Path: 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 ABEA53A123C; Fri, 29 Jan 2021 11:05:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.223 X-Spam-Level: X-Spam-Status: No, score=-3.223 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.25, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FROM_GOV_DKIM_AU=-0.873, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ncsc.gov.uk 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 T2Nn1so9NgLh; Fri, 29 Jan 2021 11:05:35 -0800 (PST) Received: from GBR01-CWL-obe.outbound.protection.outlook.com (mail-eopbgr110105.outbound.protection.outlook.com [40.107.11.105]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CEDBE3A1239; Fri, 29 Jan 2021 11:05:34 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Hjb/8OSxFjZW8FgowQ1ot6gRqZLAkUdgk9QUJ/vAuR73KIrA7ilpUviSrNFzI6CudQS8RVi05ztDpjV/Ik/tkhQiIZao+r/AzgsRQ40fhGRkyUOtDSYvF00dyNsSxhgAc24DP4DwVj+j6WOkiRikH/3oBhDsqwt7Rf5+ZB9JmqoD3qxZAAVlPqvBst65sUrnZ0R4WmTfc4KqfvLqvIS0bWUDQ3RmK0JZzgaqeEGOTBh0OtFW2TFLhn5rMy1IjdRGzPyCkpwfkX9sUU47J6xBC9+YhCVMtaxUHtYuZ6n/PbDSLHMY3pr6NzvYdi1998QiObUogGJM/JlA8yZFNjBh8Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=vayf2S3xciDc5emEiPsjQ8iAWDqgJu3KEreWZZSnXAQ=; b=dwTNMYBFSbbF5wZEzakkuEFqOfsve1tkf7uy7MPHMRSGfKviEU8sFkxWZqYyERaezoyVFcmqG625krv/2vbxps8mpELipqTX+AZsenwcWOQoOlK69QgH4y3L2JjwhX3L9f3BpeL2Yb/4sBdhTmCo4dV8Ac97jMkbq93YlU+HZRwr7nHzZcjljPZtnHu14I/m8Qb7n3duaTmFnNi24srW8Z9DcU7u3YUhI2vISLrCgzSOj3t6DLEWTWQcqKz3TnLX6u9MHad3ajOrxc2Wp5TGBQoX8d7yahMbMcSj+VFnh/xYVLJLKDwq9xcLNcmWwsMY1Q+4MZUk9/7BMyO8cgKJDA== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ncsc.gov.uk; dmarc=pass action=none header.from=ncsc.gov.uk; dkim=pass header.d=ncsc.gov.uk; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ncsc.gov.uk; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=vayf2S3xciDc5emEiPsjQ8iAWDqgJu3KEreWZZSnXAQ=; b=I1UEnw2qCBMdGPoKKHGhdsYP4pCLpuWj4vNlSlKo+f6EBk/CP+A7m3iOHaN4h4K6odOG18duwFp/6HT24ivphFYo+Wwxnw+IyVPML//jmajMHBAGBtl+on1+9rvGECZt5+POP+wd23c2Fe+e0voAjDfoCuezK9I7EscAA2mXJAdJ/lorukOwZnGKyVH1grchmWNLPWr4bP24v4d2VOTlHwY1qKE3DbId3efgn8r+HqT5Gh2sWhli73Ef7JT0JW3P8EbHApiKjqXR9lyZbUnYam7CkccSwncoHzyEUTOPBF4NYXjFjlNGBLhL17G2PDzs5uPI/x9u1DPRbICIW4g33A== Received: from LO2P123MB3599.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:12c::10) by LO2P123MB2221.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:c9::15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3805.17; Fri, 29 Jan 2021 19:05:32 +0000 Received: from LO2P123MB3599.GBRP123.PROD.OUTLOOK.COM ([fe80::149b:fdfd:8037:edf3]) by LO2P123MB3599.GBRP123.PROD.OUTLOOK.COM ([fe80::149b:fdfd:8037:edf3%7]) with mapi id 15.20.3805.019; Fri, 29 Jan 2021 19:05:32 +0000 From: Kirsty P To: "dispatch@ietf.org" CC: dispatch chairs Thread-Topic: IETF 110 meeting - call for topics Thread-Index: AQHW9nBePDUOGbIdM0GLPkdiyb3PVw== Date: Fri, 29 Jan 2021 19:05:32 +0000 Message-ID: Accept-Language: en-GB, en-US Content-Language: en-GB X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=ncsc.gov.uk; x-originating-ip: [51.132.68.128] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 4cd01d67-21dc-450c-ec50-08d8c488d9d4 x-ms-traffictypediagnostic: LO2P123MB2221: x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:8882; x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: 6VWo6y4jMllrXWHKtIbDWuXBNwnefhyPnoYTuAa4wCY3BjxcO3KEf+n4fpJhxWylANswWIibW2d3zvj21EeIksqj0viwHIqraaS0e+EqyY4wRy+NtN4DFGRCwRXo05SYs8URSs7VW8zkpexaxeiPQTCO3TU/Y216NvfHK6T7sDF1kmIfektJQc7SM/KVT8GK/ymmI3xtp43ssSa3+1Gs+h7qnewY5nAcQMWpEcbYuhcpPX2aNgieZxCoMrJN0cbwXWq5/lMF4gJeQQla7eA3h54gFPza9UVhGLnWSVAxyqWVhkxWqaHk07YOlgiqDhMYYdjIxwteWASD6RsK6mJTmd1WmYdUyQ3lIFMudg/LOWqrdr/ynTRFsvdNMN6mvra68EKP9QS7YtKDvf1lsddzzgR6H+DLAZ3wpACrlt5JFW0DD7JRtr/u+zsHYsDWndAmYxyLCnfzpv3kkLgIFHJlVRIaSyWlNiFVFUkdsTu/7w2y8d5/M4hm8lCaaUwL48Up37UVropZOrDEMAQYO+w2fA== x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:LO2P123MB3599.GBRP123.PROD.OUTLOOK.COM; PTR:; CAT:NONE; SFS:(4636009)(39850400004)(396003)(136003)(366004)(376002)(346002)(6506007)(71200400001)(186003)(26005)(2906002)(4326008)(450100002)(9686003)(52536014)(86362001)(66476007)(66946007)(7696005)(76116006)(66556008)(64756008)(66446008)(6916009)(316002)(8676002)(19627405001)(478600001)(8936002)(5660300002)(33656002)(4744005)(83380400001)(55016002); DIR:OUT; SFP:1102; x-ms-exchange-antispam-messagedata: =?iso-8859-1?Q?wglm+CulAV6hDc6zsRQfCKJ4qfi80FndnGcx0PZ88SfJg2oWt4RzBtJXSn?= =?iso-8859-1?Q?0Iaq6bg1e2A00r6Mxje/ixzpxM+aEyVlQpgOps/S4EGkEAy+vMpZ+2m5LV?= =?iso-8859-1?Q?5S1az43A/UZ3DI6hLqotvQSh6rA2HJmaQ8TzFccyzSc9wSl9W9HFUSjI/J?= =?iso-8859-1?Q?+YGN3dnMSRQ5trSojmONdDCkKK2TDb/VjQ6R7PwU5j9a1aMOkaGCvIUdlQ?= =?iso-8859-1?Q?5o9ibapj2K6HoCeIXiJzCvxWxqCFNeJisgADjGXCbvtFs8LX2x9xtMlR9w?= =?iso-8859-1?Q?Vcx+T6k7vTZWjnAw3nXmIcOonWN1RHcx9AWaRkndhTlj+wt0WdTV0NuoUD?= =?iso-8859-1?Q?TcoR+HAT4mIQW2FyAKTD7ijD1yue+LlDZvn+sBs6cvXoWit18ulK+rYqZt?= =?iso-8859-1?Q?UymswVHzjM6sZObc44YKSBWV8dLwHRNzeri/54shNW6n+HeNzzeaxPRBrf?= =?iso-8859-1?Q?NAT8/QbPvZJfUVNQjInlADKpb8v4bltylhWI1pBT3vfdF5MI1BjSzlbmQB?= =?iso-8859-1?Q?cB5qFUgQJdwHmcDoXZZsgIU9gyFSIUdwlltmGpAVRddLnD7psHj4fUd0ib?= =?iso-8859-1?Q?FZeUgUqH4zUjAQW0a08bWYFvRmEc7XeAq6TW2GswEZzZm+djd3SrDylamm?= =?iso-8859-1?Q?DEaXpfGwdxrY791zn/i/39aZUbwz8sZ0yTO5rujW+cIkd5Ptz690RJLtMx?= =?iso-8859-1?Q?Mviz+L28WXAMpJhQSdNtal8xSkPLKyBlA8qaZ565EcCJ93QSz4Ee6LhT53?= =?iso-8859-1?Q?dgHeu29PvRysXHoOCylR115nhJYrDqcjPsdAtzCry916K/KTFSBZ+7hchF?= =?iso-8859-1?Q?NMEyrG3nvprQ3ChTf6RrqcU5ijb3bkSrxbSOgHcfFy5xlI5H6CyXlj0PN6?= =?iso-8859-1?Q?4TyszXRppDzRdAes+LeQqcaaxq6VYVzOuH0YaQ3SSG/qaF/DAcKmThUnAx?= =?iso-8859-1?Q?yhptKaK0qfyFmPijWGqlroZukQq3goEWmyGoitrZI0MD9BxtFcoCUygkH6?= =?iso-8859-1?Q?kQfg6q4lKKiu5l6upsFk3q9Ahv9rHN46Ncs5zpIcEUFW5Z/y7Z3h3EFhVc?= =?iso-8859-1?Q?FTgR/UnuXGPF+/wT46GI3J7SoMrJuTZnxhiWcvcNU/T7?= x-ms-exchange-transport-forked: True Content-Type: multipart/alternative; boundary="_000_LO2P123MB35992007361016DAB674F9A4D7B99LO2P123MB3599GBRP_" MIME-Version: 1.0 X-OriginatorOrg: ncsc.gov.uk X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: LO2P123MB3599.GBRP123.PROD.OUTLOOK.COM X-MS-Exchange-CrossTenant-Network-Message-Id: 4cd01d67-21dc-450c-ec50-08d8c488d9d4 X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Jan 2021 19:05:32.1325 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 14aa5744-ece1-474e-a2d7-34f46dda64a1 X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: MmP1GxbLmnmN0PnyEEnzqCkZ9QnOAt/4gNAAIhV+C1fzCOc6JgAY4+eDVOgGBdHSMH/nfcxaBi/v8F3s+NPP5Q== X-MS-Exchange-Transport-CrossTenantHeadersStamped: LO2P123MB2221 Archived-At: Subject: [dispatch] IETF 110 meeting - call for topics X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jan 2021 19:05:37 -0000 --_000_LO2P123MB35992007361016DAB674F9A4D7B99LO2P123MB3599GBRP_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi everyone, We're putting together an agenda for the DISPATCH meeting at IETF 110, so p= lease get in touch with me and Patrick on the dispatch chairs email (CC'd) = if you would like a time slot at the meeting or if you have questions about= bringing new work. We're keen to hear from you. Additionally, please excuse our delay in reaching out to call for work. As = usual, we'll post a draft agenda in advance of the meeting and be more on i= t in future. Kirsty This information is exempt under the Freedom of Information Act 2000 (FOIA)= and may be exempt under other UK information legislation. Refer any FOIA q= ueries to ncscinfoleg@ncsc.gov.uk. All material is UK Crown Copyright =A9 --_000_LO2P123MB35992007361016DAB674F9A4D7B99LO2P123MB3599GBRP_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi everyone,

We're putting together an agenda for the DISPATCH meeting at IETF 110, so p= lease get in touch with me and Patrick on the dispatch chairs email (CC'd) = if you would like a time slot at the meeting or if you have questions about= bringing new work. We're keen to hear from you.

Additionally, please excuse our delay in reaching out to call for work. As = usual, we'll post a draft agenda in advance of the meeting and be more o= n it in future. 

Kirsty
This information is exempt under the Freedom of Information Act 2000 (FOIA)= and may be exempt under other UK information legislation. Refer any FOIA q= ueries to ncscinfoleg@ncsc.gov.uk. All material is UK Crown Copyright =A9 --_000_LO2P123MB35992007361016DAB674F9A4D7B99LO2P123MB3599GBRP_--