Re: [dispatch] New Version Notification - draft-hardie-dispatch-rfc3405-update-04.txt

Barry Leiba <barryleiba@gmail.com> Thu, 15 October 2020 20:44 UTC

Return-Path: <barryleiba@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 77A943A03F1 for <dispatch@ietfa.amsl.com>; Thu, 15 Oct 2020 13:44:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, 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 Ph2rzpwodjgV for <dispatch@ietfa.amsl.com>; Thu, 15 Oct 2020 13:44:23 -0700 (PDT)
Received: from mail-vs1-xe2c.google.com (mail-vs1-xe2c.google.com [IPv6:2607:f8b0:4864:20::e2c]) (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 D429D3A03C9 for <dispatch@ietf.org>; Thu, 15 Oct 2020 13:44:22 -0700 (PDT)
Received: by mail-vs1-xe2c.google.com with SMTP id d19so200516vso.10 for <dispatch@ietf.org>; Thu, 15 Oct 2020 13:44:22 -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:content-transfer-encoding; bh=0wc0yZ+ryDs6WJRwV4BdsMFQuk8RGKU1dBdJkUtnbOw=; b=JWubw+6xI5PH3DACZJ57L7QtgyKOx3/6iuGaRXpCp57xwqVPet6mS+8cPC9vzL/+uq KQskCTlYBkrYa0HgHbcslfjPBNPw0ZY7WiaLBuP1nNtLwvv6rLR5cC6kdhkjp/KJhNas S38AQCglemJtunNQMdRMeHXV3A1qoGCpLoIAq5t/hSWxGUoXoczAqMccoZuqK0vkzzcr uJkvVkLVPWROLcZt4JTgQAQgvUNvlVUzSC4IYenGfbt+XYNA5RG5gGErSx64iVtNxU7l dKV+tNkIMf+R1iX+dse6LT8cMw/9qE345IIpbrfC2I/aWnnVFKNVAMxPyob11IXARgae tnXw==
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:content-transfer-encoding; bh=0wc0yZ+ryDs6WJRwV4BdsMFQuk8RGKU1dBdJkUtnbOw=; b=qC/nCI7oCRQLcuy3+i121k2iHiMUUBJLOhgAx2nEfXI4IH7fvPrWHRWTJgJwnLoPMF xx6h0sBd5ADPu5wN+IofgezEqTq3OgIZlKZ1bNABaXTQn/ZFTDaHnJVNb3oLIGRjzpWU qp+J3E8LciAG9Dx/Ijjmc8SJYw5LWh8gn3Tx45ZCzFEgMg6P34oL3BsAvQOXa5+JdbiO Q0Vst2SuLfTCzfCOqPlhGAmL7BqyggEUm9oTeyJfRhc2xcVF4XS9GSS/kh8VHrmULpPN 0o4ao5fYQwu3XqS7XLPTBk7101s3YFz51PBsQ9WEWdq+Kvw/cknB+gVXk4cCo3a86ikB y4gw==
X-Gm-Message-State: AOAM531iLUOHnZl5d5nLgbeiOEPFvZCgIkNMwwqWp34iDR3lj7nycyj9 tNp7wZkAXGLCb1jCkifwcjrMDSB/qeZEw2RI0Ik=
X-Google-Smtp-Source: ABdhPJwjzKfyY1d1bs78BiJn4Q4fO35A+GPNgYSbCsIel44i4+RudisGGvCEJbSrdyA9usBKx7F75fRrxMBP1qzUFRM=
X-Received: by 2002:a67:383:: with SMTP id 125mr259108vsd.9.1602794661536; Thu, 15 Oct 2020 13:44:21 -0700 (PDT)
MIME-Version: 1.0
References: <160278762498.6279.12834691771462136672@ietfa.amsl.com> <695687617.30027.1602790280802@email.ionos.com> <CA+9kkMCh=BAMCm4-9HnSVDhW7qgzRJS6j+Q-LvVQ+P3GwYN3mg@mail.gmail.com> <894177016.33315.1602793596709@email.ionos.com>
In-Reply-To: <894177016.33315.1602793596709@email.ionos.com>
From: Barry Leiba <barryleiba@gmail.com>
Date: Thu, 15 Oct 2020 16:44:09 -0400
Message-ID: <CALaySJLnq53+Cr4-=yLSBoP2-cFAvNzED5r1X7sBdirrW2TMKg@mail.gmail.com>
To: Timothy Mcsweeney <tim@dropnumber.com>
Cc: Ted Hardie <ted.ietf@gmail.com>, Dispatch WG <dispatch@ietf.org>, Spencer Dawkins <spencerdawkins.ietf@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/S3PLkdIM_EpR119t4maECeDNY44>
Subject: Re: [dispatch] New Version Notification - draft-hardie-dispatch-rfc3405-update-04.txt
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: Thu, 15 Oct 2020 20:44:25 -0000

Your proposed changes are well outside the scope of the document, and
there was no support for expanding the scope during discussions of the
document.  As Ted says, you may propose such changes in a draft of
your own and bring it to DISPATCH for consideration.

Barry

On Thu, Oct 15, 2020 at 4:26 PM Timothy Mcsweeney <tim@dropnumber.com> wrote:
>
> Ted,
> These changes were already proposed during the last call of your update but the Shepard did not do anything about them.  So I don't understand where you are coming from.
>
> Tim
>
> On 10/15/2020 4:18 PM Ted Hardie <ted.ietf@gmail.com> wrote:
>
>
> Hi Timothy,
>
> The two small changes done for this version were to respond to IESG comments which sought to improve the clarity of the existing proposal; they did not introduce new elements to the proposal in the document.  I think your comments propose a much more significant change, and document updates post-IESG processing is not the time for that type of change.  If you wish to see other changes, I suggest you propose them in a new document.
>
> regards,
>
> Ted Hardie
>
> On Thu, Oct 15, 2020 at 12:33 PM Timothy Mcsweeney <tim@dropnumber.com> wrote:
>
> I would like to see the following changes made to this version (-04) because it does not specify what will be exactly will be reviewed:
>
> 2. Updated Requirements
> This document removes and replaces the normative requirements from sections 3.1.1
> and section 3.1.2 of RFC3405 with:
> The registration of a NAPTR record for a URI scheme MUST NOT precede registration of that scheme.  IANA will review the request against for
>   1. correctness and technical soundness (eg. valid databases, service parameters etc.) and
>   2. consistency with the published URI resolution application specification [RFC3404], and
>   3. to ensure that the NAPTR record for a DNS-based URI does not delegate resolution of the URI to a party other than the holder of the DNS name. This last rule is to insure that a given URI's resolution hint doesn't hijack (inadvertently or otherwise) network traffic for a given domain.
>
> 3. IANA Considerations
>
> This update does not change the IANA submission procedure in Section 5 of RFC 3405.
>
>
> _______________________________________________
> 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