IETF Logo Mail Archive

Re: [dispatch] Tiny update to RFC 3405

Scott Kitterman <sklist@kitterman.com> Fri, 05 June 2020 00:30 UTC

Return-Path: <sklist@kitterman.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 70B143A10C5 for <dispatch@ietfa.amsl.com>; Thu, 4 Jun 2020 17:30:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, SPF_HELO_FAIL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=kitterman.com header.b=Rg6XA+O+; dkim=pass (2048-bit key) header.d=kitterman.com header.b=AGnko6os
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 fTqj8duakvL6 for <dispatch@ietfa.amsl.com>; Thu, 4 Jun 2020 17:30:17 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [IPv6:2604:a00:6:1039:225:90ff:feaa:b169]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 763663A10D7 for <dispatch@ietf.org>; Thu, 4 Jun 2020 17:29:58 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) by interserver.kitterman.com (Postfix) with ESMTPS id C343EF8030C; Thu, 4 Jun 2020 20:29:54 -0400 (EDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1591316994; h=date : in-reply-to : references : mime-version : content-type : content-transfer-encoding : subject : to : from : message-id : from; bh=dUzElARHvl/14DCmNovfrkt/IPZ2Z86fwskCw14RphQ=; b=Rg6XA+O+z0hKt7uO1UCHTeLwj5P1F/1UsdVwscjQRwnQdCiXfXX8X17yhstfyZWM4Y4qv Nba55m9su6ZZWPICw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1591316994; h=date : in-reply-to : references : mime-version : content-type : content-transfer-encoding : subject : to : from : message-id : from; bh=dUzElARHvl/14DCmNovfrkt/IPZ2Z86fwskCw14RphQ=; b=AGnko6osqV9PyiZi8LLAOrMJW1k4lN13/xc49TuP6TLZDjRHfxMBnv7Qi5RUzumF9eJoX qPN2lAWRpQNKhBCn9iclrBOUKi+qke1+Yl4JAQxDfTA2fCTtzcOfmuc3UVK5QVM7QlmDDYs yB4g34YPDk0E5d3XOTgP221wZMI7i/0O8v2s+gklBQOfHWxlLgT3YrjaXggnHbkwjyJjU4U C526dC+kgVNWs56tFvTgCnGn90lnoizVUMSjBgGvas7pxdXoNAlNx2pfhrY8N+eMX5dqYfU R8lPKh/kOSaJsNRwHTfjYCnEItkJYlTAx5oMub8gZy1eDA/UPL0rshZF1VRg==
Received: from [192.168.1.184] (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) by interserver.kitterman.com (Postfix) with ESMTPSA id 8DA09F80256; Thu, 4 Jun 2020 20:29:54 -0400 (EDT)
Date: Fri, 05 Jun 2020 00:29:53 +0000
In-Reply-To: <CAOdDvNo36eOKn0ZWi67LeO_YEhTJoj=U0uBh02b9aD3RdggE+A@mail.gmail.com>
References: <CA+9kkMC2dFjvgEWKDDqThF3jJipcZeP4ZTofvhQ0oAx7NvB7tg@mail.gmail.com> <CAOdDvNo36eOKn0ZWi67LeO_YEhTJoj=U0uBh02b9aD3RdggE+A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
To: dispatch@ietf.org
From: Scott Kitterman <sklist@kitterman.com>
Message-ID: <836C0462-1643-45E2-AD78-84B1F1BF3534@kitterman.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/2JfaFiNPgqqb68RcwgOKec3bmSI>
Subject: Re: [dispatch] Tiny update to RFC 3405
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Jun 2020 00:30:20 -0000

What did you have in mind as an alternative to an mailing list?

Scott K

On June 5, 2020 12:08:08 AM UTC, Patrick McManus <mcmanus@ducksong.com> wrote:
>does the group have any thoughts on what the appropriate dispatch for
>Ted's
>work (below) would be?
>
>We certainly can do this outside of a list if there is participation
>and
>rough consensus.. would be good to build that skill in this remote-only
>period, right?
>
>-Patrick
>
>
>On Wed, Jun 3, 2020 at 7:13 PM Ted Hardie <ted.ietf@gmail.com> wrote:
>
>> Howdy,
>>
>> This is one the shortest drafts I've ever written:
>>
>https://datatracker.ietf.org/doc/draft-hardie-dispatch-rfc3405-update/
>>
><https://datatracker.ietf..org/doc/draft-hardie-dispatch-rfc3405-update/>
>> .   Basically, RFC 3405 used to require that registrations in
>URI.ARPA be
>> from the "IETF Tree".  That tree was deprecated after the document
>was
>> published.  As it happens, there are very few registrations in
>URI.ARPA, so
>> we did not catch it and fix it before now.
>>
>> This draft updates RFC 3405 to require "permanent" scheme
>registrations.
>> The salient bit is this:
>>
>> All registrations in URI.ARPA MUST be for schemes which are permanent
>>    registrations, as they are described in BCP 35.
>>
>> I'm hoping for a quick dispatch of this, but happy to discuss.
>>
>> regards,
>>
>> Ted Hardie
>>
>> _______________________________________________
>> dispatch mailing list
>> dispatch@ietf.org
>> https://www.ietf.org/mailman/listinfo/dispatch
>>

v2.23.0 | Report a Bug | By Email