IETF Logo Mail Archive

Re: [dispatch] Tiny update to RFC 3405

Patrick McManus <patrick.ducksong@gmail.com> Tue, 09 June 2020 21:12 UTC

Return-Path: <patrick.ducksong@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 985E03A08E1 for <dispatch@ietfa.amsl.com>; Tue, 9 Jun 2020 14:12:59 -0700 (PDT)
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 wQ7dNtvJccVa for <dispatch@ietfa.amsl.com>; Tue, 9 Jun 2020 14:12:58 -0700 (PDT)
Received: from mail-oi1-x235.google.com (mail-oi1-x235.google.com [IPv6:2607:f8b0:4864:20::235]) (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 218BA3A08CB for <dispatch@ietf.org>; Tue, 9 Jun 2020 14:12:58 -0700 (PDT)
Received: by mail-oi1-x235.google.com with SMTP id t25so71079oij.7 for <dispatch@ietf.org>; Tue, 09 Jun 2020 14:12:58 -0700 (PDT)
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=kvtLAEz80TNXrIMiMVeaBzg2W9bq1lYfWHZ+X0j2CAo=; b=Sfpj1eL1MgZhi7VjUUpHy2ZYiWsRA77T2/2lMLXFAlFs8oVNipvAU23S6O7P/9LaTE E2KGhWAq2okTfMmp8HLi1UfqDX+OyVaCmIj4ScMDrrFwVqxbayVdBQbvhQdb5KjHiRQP KMS+4w2u605qMI2Q84ok3zeNWUNKfFjPdJ2QK4EuiViadyku0FDQLkv7Q8ZeI/pCeH7c 6cj67e2futpktJ/Ig308Ib9tg5xuqxQJ8ZUb2HjrqgCA+pc4FgM8jgXeCYR+bj+imgY0 D1zazbTSRmBqaKanDOqQ7IAcEmAsCu5yKLJ9uA8oJ0cRIxY6DycHkMnTTp71w8+i57X8 JTSA==
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=kvtLAEz80TNXrIMiMVeaBzg2W9bq1lYfWHZ+X0j2CAo=; b=P+sWPK2J0wbphXfy58IMW4OCTDFcBEz0XH/JtvvqgQR1r4LawE7IRhnDee/bfKTb2E UGWZdcNYgDV3N3R1ZTN/ic9eZt7GivWuCRmdyKlgtPyFzPFVB4so5tu8CtjYTCLoB+RC nwFJIevwYX9d5rjHotU8oEvzBodStLPVwhmj92YuqANsTfqYuglcNfDQ6BKRX/1zSj16 xU2TjFoXlsPsw1eLcnC58zKCf/+xG3jOA3NoUY273XH5BvEAa/RCwqYt9gBWZd/Iav4X fED7c/MAIlzvzmEvxL9d1+rdfZrbxGzYDBZxDfDyTpqcM+8vM/EGf1YtdjZbv+adv0nC tjvw==
X-Gm-Message-State: AOAM530qEw70z56fqHnIs+94LUnf+soZ9MAN8lxpIKk10zjwJ9KghG/5 KdKTa+rG/T3tdDneCzAx1M6Y+4WQrMpam5cRD+ejyPGs
X-Google-Smtp-Source: ABdhPJwuVPlrWH78DXKkj3QEtTazom2HnWzhrEBkzBKGSmPpWV0CTwGKnosOht3xz/dL+CBBRrHVGd1KgQ+t2spPNv8=
X-Received: by 2002:aca:5b0b:: with SMTP id p11mr207389oib.82.1591737176811; Tue, 09 Jun 2020 14:12:56 -0700 (PDT)
MIME-Version: 1.0
References: <CA+9kkMC2dFjvgEWKDDqThF3jJipcZeP4ZTofvhQ0oAx7NvB7tg@mail.gmail.com> <CAOdDvNo36eOKn0ZWi67LeO_YEhTJoj=U0uBh02b9aD3RdggE+A@mail.gmail.com> <836C0462-1643-45E2-AD78-84B1F1BF3534@kitterman.com> <49903CF4-A164-4350-AC1F-4DF7A1A75440@nostrum.com>
In-Reply-To: <49903CF4-A164-4350-AC1F-4DF7A1A75440@nostrum.com>
From: Patrick McManus <patrick.ducksong@gmail.com>
Date: Tue, 09 Jun 2020 17:12:45 -0400
Message-ID: <CAOdDvNpKBuaEEpTB+S0V-7Q4hm297G-cAbMATs2FFk84FLa5_Q@mail.gmail.com>
To: Ben Campbell <ben@nostrum.com>
Cc: Scott Kitterman <sklist@kitterman.com>, Dispatch WG <dispatch@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ffed1205a7ad301d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/4AYTMkFV93vu-eH1FpZ_FRci36w>
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: Tue, 09 Jun 2020 21:13:00 -0000

I asked the question in an open ended spirit with all of the usual dispatch
outcomes on the table. (but expressed it in phone keyboard speak - sorry.)

I would anticipate that this would generate an AD sponsored recommendation
due to its nature, but it would be nice to hear a few more comments
responsive to that before considering the consensus question..

On Tue, Jun 9, 2020 at 4:57 PM Ben Campbell <ben@nostrum.com> wrote:

> I suspect Patrick meant “outside of a working group”. Patrick?
>
> > On Jun 4, 2020, at 7:29 PM, Scott Kitterman <sklist@kitterman.com>
> wrote:
> >
> > 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
> >>>
> >
> > _______________________________________________
> > dispatch mailing list
> > dispatch@ietf.org
> > https://www.ietf.org/mailman/listinfo/dispatch
>
>

v2.23.0 | Report a Bug | By Email