IETF Logo Mail Archive

Re: [DNSOP] [Last-Call] Artart last call review of draft-ietf-dnsop-dns-tcp-requirements-12

Bob Hinden <bob.hinden@gmail.com> Sat, 11 September 2021 16:03 UTC

Return-Path: <bob.hinden@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 C01EE3A1B8C; Sat, 11 Sep 2021 09:03:59 -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 Q0d6Stngu4F2; Sat, 11 Sep 2021 09:03:56 -0700 (PDT)
Received: from mail-wr1-x42c.google.com (mail-wr1-x42c.google.com [IPv6:2a00:1450:4864:20::42c]) (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 947FD3A1B8A; Sat, 11 Sep 2021 09:03:56 -0700 (PDT)
Received: by mail-wr1-x42c.google.com with SMTP id g16so7393736wrb.3; Sat, 11 Sep 2021 09:03:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=0/F/Z1Lkk0qvgfNOCcP7dHMxe/Wag8r4V/PeMvr0U5I=; b=nOFuO+mozWByQcxLYd5SPkQ3BCeckuLE1KP/kVE8VuCT2WZswqBDrtdupuAO6kxa1S CWZ+sCSqU78rl2CRw0n0+1rwShORVFeIarYliazECXHMiemPuBwHCa6SIqsBgTFsfzgw 8k4Se9EDpOi4Y7pcs/YBMQAPr8922XParxMjtvXXGSeyoyf0E5Z9hBVXaAXQ8PRY/Cme MtpXpc/j6laCdWzjXj3GlTxJJOb2qcxqlyvd+2dIeIk5DS22cZnQ8JRvvuAiUXzMnWMq HBh5jpSDo/huXGmYen6N+BhhCeqapEhc+ZxOBVORenR4tHgJyOFsCcLGOoQF9Mmv8J2T ww+w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=0/F/Z1Lkk0qvgfNOCcP7dHMxe/Wag8r4V/PeMvr0U5I=; b=BYFiGAPetW2EgURavfdOVrw+3nYX7WGgAwfzXxI4KINFFvWwaeVJibGMNax4xo9CvE jbkh3wDkyNa9UtgEuKUPwpMIHzE7DHv4S1vxgXosWc8/81Zc1SM11r1f4sAC8v1eMTUq /Zdw0MfZHhOJIP2w78mzXU4NIM3bdmXeiN4mfMX1meFVY9j0OlXZOxj7q9jLBvf5jHKV oJzWC1suRdQgMI5oeY+EoRs2HyzBH9n4ZjqZGiG7RFLqTcTS6xRntZY7ZfOTorT4xegv QeX0Lvks0Rkl1CXxSWMySvXkrjFlvQaSBfgNr3Xe4tzU1L7a+Bf6ZeYdaSt8Z0LLyFSE pEGw==
X-Gm-Message-State: AOAM5320WxVATtqwi/lJ6A0X9KnaYQ/U+dwD4BdE/Hc0KlbhpYfmau7i kUYf2uHD00jT3hw74gZSEzA=
X-Google-Smtp-Source: ABdhPJxCDXOTchjgZTQfodVjaD8DSiaygI5wYu7Nh/odZXt38JX/e3zsctI19bTUc1xaBN1Mi7J3OA==
X-Received: by 2002:a5d:60c8:: with SMTP id x8mr1030244wrt.293.1631376233100; Sat, 11 Sep 2021 09:03:53 -0700 (PDT)
Received: from ?IPv6:2601:647:5a00:659:b487:ad1c:b24e:e36c? ([2601:647:5a00:659:b487:ad1c:b24e:e36c]) by smtp.gmail.com with ESMTPSA id r25sm2208818wrc.26.2021.09.11.09.03.50 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 11 Sep 2021 09:03:52 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <C6266BF5-B352-46EF-BCFF-B7BF3FB4A139@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_91BFABFA-F3F9-4875-9369-7BD0DC3204DA"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
Date: Sat, 11 Sep 2021 09:03:48 -0700
In-Reply-To: <CAHw9_iJcaH1f_tvW0_uptq_Gny7ejBSJeNHuE_oohNVm8i8Qow@mail.gmail.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, "A. Jean Mahoney" <mahoney@nostrum.com>, "Wessels, Duane" <dwessels=40verisign.com@dmarc.ietf.org>, "art@ietf.org" <art@ietf.org>, "dnsop@ietf.org" <dnsop@ietf.org>, "draft-ietf-dnsop-dns-tcp-requirements.all@ietf.org" <draft-ietf-dnsop-dns-tcp-requirements.all@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>
To: Warren Kumari <warren@kumari.net>
References: <163071535768.12872.16291782186298428894@ietfa.amsl.com> <7A0EC9A6-AF64-40F0-A229-C56E93CCE8DE@verisign.com> <18ba445b-e768-2c33-fca3-76c4aa102b20@nostrum.com> <CAHw9_iJcaH1f_tvW0_uptq_Gny7ejBSJeNHuE_oohNVm8i8Qow@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.104.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/x2dn5OM-c4d-mhbvPOF2HvNM674>
Subject: Re: [DNSOP] [Last-Call] Artart last call review of draft-ietf-dnsop-dns-tcp-requirements-12
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 11 Sep 2021 16:04:00 -0000

Hi Warren,

> On Sep 10, 2021, at 4:19 PM, Warren Kumari <warren@kumari.net> wrote:
> 
> > Seems reasonable to consider, assuming a BCP can update an Informational RFC?
> 
> Any RFC can update any previous RFC?  There are some questions about the
> use of "Updates" (see draft-kuehlewind-update-tag); different WGs use it
> for different things. If you are trying to catch the eye of
> implementers, maybe it would help, but perhaps ask your AD.
> 
> Yup, it should be able to.
> W

Are you sure?

For example, can an “Experimental" RFC update an RFC at “Standard”?    Can an RFC from one Stream update an RFC in another Stream?   Lots of other cases come to mind.

This seems a lot more subtle than any RFC can update any other RFC.

Bob

v2.23.0 | Report a Bug | By Email