[DNSOP] BCP 219, RFC 8499 on DNS Terminology

rfc-editor@rfc-editor.org Thu, 03 January 2019 02:44 UTC

Return-Path: <wwwrun@rfc-editor.org>
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 9241F130FFF; Wed, 2 Jan 2019 18:44:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EjfsqnBSv0Ua; Wed, 2 Jan 2019 18:44:04 -0800 (PST)
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 4F990130E3F; Wed, 2 Jan 2019 18:44:04 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 319C7B81052; Wed, 2 Jan 2019 18:43:56 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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, dnsop@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20190103024356.319C7B81052@rfc-editor.org>
Date: Wed, 2 Jan 2019 18:43:56 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/8Otrtz1JKtNJH7HIAyZDJfeqkv0>
Subject: [DNSOP] =?utf-8?q?BCP_219=2C_RFC_8499_on_DNS_Terminology?=
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: Thu, 03 Jan 2019 02:44:09 -0000

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

        BCP 219        
        RFC 8499

        Title:      DNS Terminology 
        Author:     P. Hoffman,
                    A. Sullivan,
                    K. Fujiwara
        Status:     Best Current Practice
        Stream:     IETF
        Date:       January 2019
        Mailbox:    paul.hoffman@icann.org, 
                    ajs@anvilwalrusden.com, 
                    fujiwara@jprs.co.jp
        Pages:      50
        Characters: 119094
        Obsoletes:  RFC 7719
        Updates:    RFC 2308
        See Also:   BCP 219

        I-D Tag:    draft-ietf-dnsop-terminology-bis-14.txt

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

        DOI:        10.17487/RFC8499

The Domain Name System (DNS) is defined in literally dozens of
different RFCs.  The terminology used by implementers and developers
of DNS protocols, and by operators of DNS systems, has sometimes
changed in the decades since the DNS was first defined.  This
document gives current definitions for many of the terms used in the
DNS in a single document.

This document obsoletes RFC 7719 and updates RFC 2308.

This document is a product of the Domain Name System Operations Working Group of the IETF.


BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. 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