[dnsext] RFC 6604 on xNAME RCODE and Status Bits Clarification
rfc-editor@rfc-editor.org Fri, 13 April 2012 18:03 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 4DD4411E80A2; Fri, 13 Apr 2012 11:03:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.176
X-Spam-Level:
X-Spam-Status: No, score=-102.176 tagged_above=-999 required=5 tests=[AWL=-0.176, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uHuekuHdocYi; Fri, 13 Apr 2012 11:03:19 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id D312D11E809C; Fri, 13 Apr 2012 11:03:19 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id C4C4AB1E002; Fri, 13 Apr 2012 11:02:24 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20120413180224.C4C4AB1E002@rfc-editor.org>
Date: Fri, 13 Apr 2012 11:02:24 -0700
Cc: dnsext@ietf.org, rfc-editor@rfc-editor.org
Subject: [dnsext] RFC 6604 on xNAME RCODE and Status Bits Clarification
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 13 Apr 2012 18:03:20 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6604
Title: xNAME RCODE and Status Bits
Clarification
Author: D. Eastlake 3rd
Status: Standards Track
Stream: IETF
Date: April 2012
Mailbox: d3e3e3@gmail.com
Pages: 5
Characters: 10790
Updates: RFC1035, RFC2308, RFC2672
I-D Tag: draft-ietf-dnsext-xnamercode-00.txt
URL: http://www.rfc-editor.org/rfc/rfc6604.txt
The Domain Name System (DNS) has long provided means, such as the CNAME
(Canonical Name), whereby a DNS query can be redirected to a different
name. A DNS response header has an RCODE (Response Code) field, used
for indicating errors, and response status bits. This document
clarifies, in the case of such redirected queries, how the RCODE and
status bits correspond to the initial query cycle (where the CNAME or
the like was detected) and subsequent or final query cycles.
[STANDARDS-TRACK]
This document is a product of the DNS Extensions Working Group of the IETF.
This is now a Proposed Standard Protocol.
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 Internet
Official Protocol Standards (STD 1) 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
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
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