Re: [DNSOP] [Ext] Genart last call review of draft-ietf-dnsop-rfc5933-bis-10

Tim Wicinski <tjw.ietf@gmail.com> Wed, 19 October 2022 15:27 UTC

Return-Path: <tjw.ietf@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1638CC14CE33; Wed, 19 Oct 2022 08:27:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 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, T_SCC_BODY_TEXT_LINE=-0.01] 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 dsfCyUZQxLoB; Wed, 19 Oct 2022 08:27:39 -0700 (PDT)
Received: from mail-oi1-x233.google.com (mail-oi1-x233.google.com [IPv6:2607:f8b0:4864:20::233]) (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 93EB7C14CE2B; Wed, 19 Oct 2022 08:27:39 -0700 (PDT)
Received: by mail-oi1-x233.google.com with SMTP id o64so19595221oib.12; Wed, 19 Oct 2022 08:27:39 -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:subject:date:message-id:reply-to; bh=+sf1JXJSZcc51I+pY9QFcUo4YBa1KRdk/rlqMWGj9/0=; b=UbxcRSafGtj3ziNiLglMcSVrpTAh02Re3FGJ/W8IQ2O1I+4Wg29YnAHzJPtk2ismD2 6qNmt2tC5q7MiNoz66FCYGJKb7jyX4XMADwu9OoMsadfY8yrIdEQhMICGfDDFXn1pwy8 +wvSZ6fHWmf1bRqQY1d7GVkB74Q7k/bsPaeMimDWRgtO10VhyZgZp1xwrARORBc/5aKN QJhk/UdFNUQmPLKDr1HyWtJk2ING0p2uFzBYivX90kuQL4ftFzwF+fj/jSOZhx/dysnu /ALjiOBB2LJV5juHdlHaU2ZOUO9eFCQDTJOjCFNS1hvJ3IcuuecKd0T8M0Qno8DdVS3P f1pw==
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:subject:date:message-id :reply-to; bh=+sf1JXJSZcc51I+pY9QFcUo4YBa1KRdk/rlqMWGj9/0=; b=dJugMCf8QMhOQRQHhpdjUQm+j2WhfvN5UxXbFWL91mhX/v713A9MDlLfd3YNCAnTfm YCR7NBQFt8du90gbrbXlQrqQls2xbMJDHdrHUl+MM70G4nE2tX7ZShKe/Y1MRSf4WUdm mEb4V27IXkpfJMjy+vacgVYW/ZBDhb4EyQmvc8LVg67Yk3SUES6an3CNrmoQA1K5/VCM KPnxP014bZvilnD5hqK+q+6NzOpKoIAVifaANUtgFBmh7sjANxug2c3OiLZ3xgy0b2Vv hYPHucSR/s9vzAP+tdkBgYHdAS7TwWuPzlSZE5xo2t+/pj70aR7ZLV8530TdL1qg04Ib cZVg==
X-Gm-Message-State: ACrzQf2kZmBj33DkAqlz9XPgptRgTIfnopEvrwix4JmteE8K/ya1UqLw UzsUkIb+k+Wevwjd04/yrnrP/+0ssyR8czXSjRsGv/f9
X-Google-Smtp-Source: AMsMyM6R1aba0QuklDAixDayyHw8c6Qz12+dpCGOGeWlMfYDfc2mQjugztrI/zfSLrD7m2vwcHj4YBBpbceQITYZOPQ=
X-Received: by 2002:aca:acd3:0:b0:354:d607:2af8 with SMTP id v202-20020acaacd3000000b00354d6072af8mr19342827oie.234.1666193258832; Wed, 19 Oct 2022 08:27:38 -0700 (PDT)
MIME-Version: 1.0
References: <166566129313.28471.9552612703046827117@ietfa.amsl.com> <147c2505-8b8e-e956-badf-ec633b030547@tcinet.ru> <CAHy0fzBcN9Vd9GRFB157W_23akhpy22yZa=9bV2_91hVdicYPA@mail.gmail.com> <BD832679-C3E6-4EB8-82B6-84D83A47B53D@icann.org> <CAHw9_iJYOPKoAsRR-EWEZUh_MzOWbiAJdMnKTy7CMV6ahErbGA@mail.gmail.com>
In-Reply-To: <CAHw9_iJYOPKoAsRR-EWEZUh_MzOWbiAJdMnKTy7CMV6ahErbGA@mail.gmail.com>
From: Tim Wicinski <tjw.ietf@gmail.com>
Date: Wed, 19 Oct 2022 11:27:27 -0400
Message-ID: <CADyWQ+GbaiNdkP7_kzNG4UXJfZb_y2x+gk0s9TJBx_Nm86wr5g@mail.gmail.com>
To: Warren Kumari <warren@kumari.net>
Cc: Paul Hoffman <paul.hoffman@icann.org>, Ron Even <ron.even.tlv@gmail.com>, gen-art@ietf.org, dnsop <dnsop@ietf.org>, draft-ietf-dnsop-rfc5933-bis.all@ietf.org, last-call@ietf.org
Content-Type: multipart/alternative; boundary="00000000000051e67f05eb64d9ed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/JQbmLpO_1r8jGvm6O6xW4Tk6q64>
Subject: Re: [DNSOP] [Ext] Genart last call review of draft-ietf-dnsop-rfc5933-bis-10
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Oct 2022 15:27:40 -0000

I agree with Warren on this, as the chair he and I had several discussions
sorting out this situation,
and Mr Hoffman did the work in cleaning up the IANA registrations.

tim




On Wed, Oct 19, 2022 at 11:13 AM Warren Kumari <warren@kumari.net> wrote:

>
>
>
>
> On Wed, Oct 19, 2022 at 7:22 AM, Paul Hoffman <paul.hoffman@icann.org>
> wrote:
>
>> On Oct 18, 2022, at 7:58 AM, Ron Even <ron.even.tlv@gmail.com> wrote:
>>
>> 1. whis is this an informational RFC and not a standard track RFC.
>>
>> That's a reasonable question with a simple answer: because the WG changed
>> its mind on what the status of this protocol should be. RFC 5933 describes
>> a national standard that is thinly deployed. At the time, it was necessary
>> to have the protocol on standards track; now it no longer is required.
>>
>
> One or two people had also poked me off-list, asking if the process allows
> for an informational document to update a non-informational document. This
> appears to be fully allowed by process (and I had checked before advancing
> the document).
> I checked on a few documents which Update other documents, and here is a
> selection of prior instances where this was done.
>
> RFC2026 - "The Internet Standards Process -- Revision 3" (BCP) was updated
> by both
> RFC7841 - "RFC Streams, Headers, and Boilerplates" (Informational)
> and RFC3669 - "Guidelines for Working Groups on Intellectual Property
> Issues" (Informational)
>
>
> RFC9120 - "Nameservers for the Address and Routing Parameter Area ("arpa")
> Domain" (Info) updates RFC3172 - "Management Guidelines \& Operational
> Requirements for the Address and Routing Parameter Area Domain
> ("arpa") (Best Current Practice)
>
>
> RFC7722 - "Multi-Topology Extension for the Optimized Link State Routing
> Protocol Version 2 (OLSRv2)" (Exp) updates both RFC7188 - "Optimized Link
> State Routing Protocol Version 2 (OLSRv2) and MANET Neighborhood Discovery
> Protocol (NHDP) Extension TLVs" (Standards Track)
> and RFC7631 - "TLV Naming in the Mobile Ad Hoc Network (MANET) Generalized
> Packet/Message Format" (Standards Track)
>
>
> RFC7419 - "Common Interval Support in Bidirectional Forwarding
> Detection" (Informational) updates  RFC5880 - "Bidirectional Forwarding
> Detection (BFD)" (Standards Track).
>
> W
>
>
>> 2. What is requested from IANA. ths text you wrote and I copied is not a
>> directive to IANA that is clear
>>
>> You are correct that the IANA Considerations section is quite unclear,
>> and needs to be clarified before the IESG considers it.
>>
>> --Paul Hoffman
>>
>
>