Last Call: <draft-ietf-dnsop-multi-provider-dnssec-04.txt> (Multi Signer DNSSEC models) to Informational RFC

The IESG <iesg-secretary@ietf.org> Tue, 10 March 2020 13:33 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-dnsop-multi-provider-dnssec-04.txt> (Multi Signer DNSSEC models) to Informational RFC
Auto-Submitted: auto-generated
Precedence: bulk
CC: dnsop@ietf.org, dnsop-chairs@ietf.org, benno@NLnetLabs.nl, draft-ietf-dnsop-multi-provider-dnssec@ietf.org, Benno Overeinder <benno@NLnetLabs.nl>, warren@kumari.net
Reply-To: last-call@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <158384720184.15539.16584307443274359482@ietfa.amsl.com>
Date: Tue, 10 Mar 2020 06:33:21 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/nOuJljDzk2LBfjCM7IEppmqifIg>

The IESG has received a request from the Domain Name System Operations WG
(dnsop) to consider the following document: - 'Multi Signer DNSSEC models'
  <draft-ietf-dnsop-multi-provider-dnssec-04.txt> as Informational RFC

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
last-call@ietf.org mailing lists by 2020-03-31. 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


   Many enterprises today employ the service of multiple DNS providers
   to distribute their authoritative DNS service.  Deploying DNSSEC in
   such an environment may present some challenges depending on the
   configuration and feature set in use.  In particular, when each DNS
   provider independently signs zone data with their own keys,
   additional key management mechanisms are necessitated.  This document
   presents deployment models that accommodate this scenario and
   describe these key management requirements.  These models do not
   require any changes to the behavior of validating resolvers, nor do
   they impose the new key management requirements on authoritative
   servers not involved in multi signer configurations.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-dnsop-multi-provider-dnssec/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-dnsop-multi-provider-dnssec/ballot/


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

Last Call: <draft-ietf-dnsop-multi-provider-dnsse… The IESG