IETF Logo Mail Archive

Re: [DNSOP] Last Call: <draft-ietf-dnsop-algorithm-update-05.txt> (Algorithm Implementation Requirements and Usage Guidance for DNSSEC) to Proposed Standard

Mats Dufberg <mats.dufberg@internetstiftelsen.se> Mon, 18 February 2019 17:05 UTC

Return-Path: <mats.dufberg@internetstiftelsen.se>
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 E7193129A87 for <dnsop@ietfa.amsl.com>; Mon, 18 Feb 2019 09:05:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.189
X-Spam-Level:
X-Spam-Status: No, score=-4.189 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
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 43whCVfJBRqe for <dnsop@ietfa.amsl.com>; Mon, 18 Feb 2019 09:05:35 -0800 (PST)
Received: from relay1.iis.se (relay1.iis.se [IPv6:2a00:801:f0:106::38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DCC651295D8 for <dnsop@ietf.org>; Mon, 18 Feb 2019 09:05:34 -0800 (PST)
Received: from exchange01.office.nic.se (unknown [2001:67c:124c:100e::20]) by relay1.iis.se (Halon) with ESMTPS id 6527ae25-339f-11e9-ae35-005056827d92; Mon, 18 Feb 2019 17:05:30 +0000 (UTC)
Received: from exchange02.office.nic.se (2001:67c:124c:2043::25) by exchange01.office.nic.se (2001:67c:124c:100e::20) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Mon, 18 Feb 2019 18:05:29 +0100
Received: from exchange02.office.nic.se ([fe80::681b:9cef:675b:d880]) by exchange02.office.nic.se ([fe80::681b:9cef:675b:d880%14]) with mapi id 15.00.1347.000; Mon, 18 Feb 2019 18:05:29 +0100
From: Mats Dufberg <mats.dufberg@internetstiftelsen.se>
To: "ietf@ietf.org" <ietf@ietf.org>, "dnsop@ietf.org" <dnsop@ietf.org>
Thread-Topic: [DNSOP] Last Call: <draft-ietf-dnsop-algorithm-update-05.txt> (Algorithm Implementation Requirements and Usage Guidance for DNSSEC) to Proposed Standard
Thread-Index: AQHUw9KLGKozXl4ll0SlO9p22BRRN6Xl0KeA
Date: Mon, 18 Feb 2019 17:05:29 +0000
Message-ID: <D87AFE0D-3073-4461-BC65-EA3E60AED78C@iis.se>
References: <155008617010.9548.7174990317415826094.idtracker@ietfa.amsl.com>
In-Reply-To: <155008617010.9548.7174990317415826094.idtracker@ietfa.amsl.com>
Accept-Language: en-US, sv-SE
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.10.7.190210
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [2001:67c:124c:5024::161e]
Content-Type: text/plain; charset="utf-8"
Content-ID: <039D48592346A34199E7C2A5C5546B91@iis.se>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/vlXKErA0Oe8zOzbDfY-tVTudhic>
Subject: Re: [DNSOP] Last Call: <draft-ietf-dnsop-algorithm-update-05.txt> (Algorithm Implementation Requirements and Usage Guidance for DNSSEC) to Proposed Standard
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: Mon, 18 Feb 2019 17:05:39 -0000

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@ietf.org> on behalf of The IESG <iesg-secretary@ietf.org>
Reply-To: "ietf@ietf.org" <ietf@ietf.org>
Date: Wednesday, 13 February 2019 at 20:30
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Tim Wicinski <tjw.ietf@gmail.com>, "draft-ietf-dnsop-algorithm-update@ietf.org" <draft-ietf-dnsop-algorithm-update@ietf.org>, "dnsop@ietf.org" <dnsop@ietf.org>, "dnsop-chairs@ietf.org" <dnsop-chairs@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@ietf.org mailing lists by 2019-02-27. Exceptionally, comments may be
    sent to iesg@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@ietf.org
    https://www.ietf.org/mailman/listinfo/dnsop

v2.23.0 | Report a Bug | By Email