RFC 8567 on Customer Management DNS Resource Records

rfc-editor@rfc-editor.org Mon, 01 April 2019 19:38 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 []) by ietfa.amsl.com (Postfix) with ESMTP id A8F10120505 for <ietf-announce@ietfa.amsl.com>; Mon, 1 Apr 2019 12:38:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id NVhWWoDZ-QY9 for <ietf-announce@ietfa.amsl.com>; Mon, 1 Apr 2019 12:38:18 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B30A1204F6 for <ietf-announce@ietf.org>; Mon, 1 Apr 2019 12:38:18 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 76D1FB81D60; Mon, 1 Apr 2019 12:38:04 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg1Njcgb24gQ3VzdG9tZXIgTWFuYWdlbWVudCBETlMgUmVzb3VyY2UgUmVjb3Jkcw==?=
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20190401193804.76D1FB81D60@rfc-editor.org>
Date: Mon, 1 Apr 2019 12:38:04 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/SqHT53TsH6UX37Yd68FEx1Vtd6w>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Mon, 01 Apr 2019 19:38:27 -0000

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

        RFC 8567

        Title:      Customer Management DNS Resource Records 
        Author:     E. Rye, R. Beverly
        Status:     Informational
        Stream:     Independent
        Date:       April 2019 
        Mailbox:    rye@cmand.org, 
        Pages:      11
        Characters: 25215
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-cust-mgmt-dns-01.txt

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

        DOI:        10.17487/RFC8567

Maintaining high Quality of Experience (QoE) increasingly requires
end-to-end, holistic network management, including managed Customer
Premises Equipment (CPE).  Because customer management is a shared
global responsibility, the Domain Name System (DNS) provides an ideal
existing infrastructure for maintaining authoritative customer
information that must be readily, reliably, and publicly accessible.

This document describes four new DNS resource record types for
encoding customer information in the DNS.  These records are intended
to better facilitate high customer QoE via inter-provider cooperation
and management of customer data.

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

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