RFC 6950 on Architectural Considerations on Application Features in the DNS
rfc-editor@rfc-editor.org Wed, 09 October 2013 16:18 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 8339D11E81CA for <ietf-announce@ietfa.amsl.com>; Wed, 9 Oct 2013 09:18:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.54
X-Spam-Level:
X-Spam-Status: No, score=-102.54 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, 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 KLnK9hXMhBDa for <ietf-announce@ietfa.amsl.com>; Wed, 9 Oct 2013 09:18:52 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id B53E411E81A9 for <ietf-announce@ietf.org>; Wed, 9 Oct 2013 09:18:52 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 3FB88B1E013; Wed, 9 Oct 2013 09:11:08 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6950 on Architectural Considerations on Application Features in the DNS
From: rfc-editor@rfc-editor.org
Message-Id: <20131009161108.3FB88B1E013@rfc-editor.org>
Date: Wed, 09 Oct 2013 09:11:08 -0700
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 09 Oct 2013 16:18:53 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6950
Title: Architectural Considerations on Application Features
in the DNS
Author: J. Peterson, O. Kolkman,
H. Tschofenig, B. Aboba
Status: Informational
Stream: IAB
Date: October 2013
Mailbox: jon.peterson@neustar.biz,
olaf@nlnetlabs.nl,
Hannes.Tschofenig@gmx.net,
Bernard_aboba@hotmail.com
Pages: 31
Characters: 85548
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-iab-dns-applications-07.txt
URL: http://www.rfc-editor.org/rfc/rfc6950.txt
A number of Internet applications rely on the Domain Name System
(DNS) to support their operations. Many applications use the DNS to
locate services for a domain; some, for example, transform identifiers
other than domain names into formats that the DNS can process, and
then fetch application data or service location data from the DNS.
Proposals incorporating sophisticated application behavior using DNS
as a substrate have raised questions about the role of the DNS as an
application platform. This document explores the architectural
consequences of using the DNS to implement certain application
features, and it provides guidance to future application designers as to
the limitations of the DNS as a substrate and the situations in which
alternative designs should be considered.
This document is a product of the Internet Architecture Board.
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
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/search/rfc_search.php
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