[dnsext] STD 88, RFC 3596 on DNS Extensions to Support IP Version 6
rfc-editor@rfc-editor.org Fri, 14 July 2017 17:41 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C85513144F; Fri, 14 Jul 2017 10:41:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-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 bnqzVPWAiMEM; Fri, 14 Jul 2017 10:41:28 -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 44F0B126CD6; Fri, 14 Jul 2017 10:41:28 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id BA5F6B80D56; Fri, 14 Jul 2017 10:41:24 -0700 (PDT)
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, dnsext@ietf.org
Message-Id: <20170714174124.BA5F6B80D56@rfc-editor.org>
Date: Fri, 14 Jul 2017 10:41:24 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsext/fN5sejsJVTThutWO6xkhGg6cZ-U>
Subject: [dnsext] STD 88, RFC 3596 on DNS Extensions to Support IP Version 6
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsext/>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jul 2017 17:41:29 -0000
RFC 3596 has been elevated to Internet Standard.
STD 88
RFC 3596
Title: DNS Extensions to Support IP Version 6
Author: S. Thomson,
C. Huitema,
V. Ksinant,
M. Souissi
Status: Standards Track
Stream: IETF
Date: October 2003
Pages: 8
Characters: 14093
Obsoletes: RFC 3152, RFC 1886
See Also: STD 88
I-D Tag: draft-ietf-dnsext-rfc1886bis-03.txt
URL: https://www.rfc-editor.org/info/rfc3596
DOI: 10.17487/RFC3596
This document defines the changes that need to be made to the Domain Name System (DNS) to support hosts running IP version 6 (IPv6). The changes include a resource record type to store an IPv6 address, a domain to support lookups based on an IPv6 address, and updated definitions of existing query types that return Internet addresses as part of additional section processing. The extensions are designed to be compatible with existing applications and, in particular, DNS implementations themselves.
This document is a product of the DNS Extensions Working Group of the IETF.
This is now an Internet Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. 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