RFC 7958 on DNSSEC Trust Anchor Publication for the Root Zone

rfc-editor@rfc-editor.org Thu, 01 September 2016 01:39 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88BF812D810 for <ietf-announce@ietfa.amsl.com>; Wed, 31 Aug 2016 18:39:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.17
X-Spam-Level:
X-Spam-Status: No, score=-103.17 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham 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 Yhbnr89VSTcY for <ietf-announce@ietfa.amsl.com>; Wed, 31 Aug 2016 18:39:53 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18A3212D830 for <ietf-announce@ietf.org>; Wed, 31 Aug 2016 18:38:56 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 12BFEB80D26; Wed, 31 Aug 2016 18:38:56 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7958 on DNSSEC Trust Anchor Publication for the Root Zone
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160901013856.12BFEB80D26@rfc-editor.org>
Date: Wed, 31 Aug 2016 18:38:56 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/s6NHM69Sitdl5IzP1FA8u4eqgBw>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Sep 2016 01:39:54 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7958

        Title:      DNSSEC Trust Anchor Publication for 
                    the Root Zone 
        Author:     J. Abley, J. Schlyter,
                    G. Bailey, P. Hoffman
        Status:     Informational
        Stream:     Independent
        Date:       August 2016
        Mailbox:    jabley@dyn.com, 
                    jakob@kirei.se, 
                    guillaumebailey@outlook.com, 
                    paul.hoffman@icann.org
        Pages:      14
        Characters: 26072
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-jabley-dnssec-trust-anchor-16.txt

        URL:        https://www.rfc-editor.org/info/rfc7958

        DOI:        http://dx.doi.org/10.17487/RFC7958

The root zone of the Domain Name System (DNS) has been
cryptographically signed using DNS Security Extensions (DNSSEC).

In order to obtain secure answers from the root zone of the DNS using
DNSSEC, a client must configure a suitable trust anchor.  This
document describes the format and publication mechanisms IANA has
used to distribute the DNSSEC trust anchors.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC