[rfc-i] should a bis document obsoleting a document, inherit its Updates: ?

Paul Wouters paul at nohats.ca
Mon Feb 18 11:11:31 PST 2019


Hi,

Is this the correct procedure? Should draft-ietf-dnsop-algorithm-update
which is obsoleting 6944 adopt all the Updates: from 6944 ?

Paul

---------- Forwarded message ----------
Date: Mon, 18 Feb 2019 12:05:29
From: Mats Dufberg <mats.dufberg at internetstiftelsen.se>
To: "ietf at ietf.org" <ietf at ietf.org>, "dnsop at ietf.org" <dnsop at ietf.org>
Subject: Re: [DNSOP] Last Call: <draft-ietf-dnsop-algorithm-update-05.txt>
     (Algorithm Implementation Requirements and Usage Guidance for DNSSEC) to
     Proposed Standard

If this draft is approved, the new RFC will obsolete RFC 6944. RFC 6944, in turn, updates eight other RFCs. As I interpret it, the new RFC will inherit that role. I think that should be explicitly stated in the new RFC.


Yours,
Mats

---
Mats Dufberg
DNS Specialist, IIS
Mobile: +46 73 065 3899
https://www.iis.se/en/


-----Original Message-----
From: DNSOP <dnsop-bounces at ietf.org> on behalf of The IESG <iesg-secretary at ietf.org>
Reply-To: "ietf at ietf.org" <ietf at ietf.org>
Date: Wednesday, 13 February 2019 at 20:30
To: IETF-Announce <ietf-announce at ietf.org>
Cc: Tim Wicinski <tjw.ietf at gmail.com>, "draft-ietf-dnsop-algorithm-update at ietf.org" <draft-ietf-dnsop-algorithm-update at ietf.org>, "dnsop at ietf.org" <dnsop at ietf.org>, "dnsop-chairs at ietf.org" <dnsop-chairs at ietf.org>
Subject: [DNSOP] Last Call: <draft-ietf-dnsop-algorithm-update-05.txt> (Algorithm Implementation Requirements and Usage Guidance for DNSSEC) to Proposed Standard


     The IESG has received a request from the Domain Name System Operations WG
     (dnsop) to consider the following document: - 'Algorithm Implementation
     Requirements and Usage Guidance for DNSSEC'
       <draft-ietf-dnsop-algorithm-update-05.txt> as Proposed Standard

     The IESG plans to make a decision in the next few weeks, and solicits final
     comments on this action. Please send substantive comments to the
     ietf at ietf.org mailing lists by 2019-02-27. Exceptionally, comments may be
     sent to iesg at ietf.org instead. In either case, please retain the beginning of
     the Subject line to allow automated sorting.

     Abstract


        The DNSSEC protocol makes use of various cryptographic algorithms in
        order to provide authentication of DNS data and proof of non-
        existence.  To ensure interoperability between DNS resolvers and DNS
        authoritative servers, it is necessary to specify a set of algorithm
        implementation requirements and usage guidelines to ensure that there
        is at least one algorithm that all implementations support.  This
        document defines the current algorithm implementation requirements
        and usage guidance for DNSSEC.  This document obsoletes [RFC6944].




     The file can be obtained via
     https://datatracker.ietf.org/doc/draft-ietf-dnsop-algorithm-update/

     IESG discussion can be tracked via
     https://datatracker.ietf.org/doc/draft-ietf-dnsop-algorithm-update/ballot/


     No IPR declarations have been submitted directly on this I-D.




     _______________________________________________
     DNSOP mailing list
     DNSOP at ietf.org
     https://www.ietf.org/mailman/listinfo/dnsop


_______________________________________________
DNSOP mailing list
DNSOP at ietf.org
https://www.ietf.org/mailman/listinfo/dnsop


More information about the rfc-interest mailing list