RFC 8222 on Selecting Labels for Use with Conventional DNS and Other Resolution Systems in DNS-Based Service Discovery
rfc-editor@rfc-editor.org Thu, 21 September 2017 23:36 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 C45F61341F8; Thu, 21 Sep 2017 16:36:24 -0700 (PDT)
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 Eex0zFdve6qc; Thu, 21 Sep 2017 16:36:17 -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 CAF9513337F; Thu, 21 Sep 2017 16:36:17 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 8F701B817A3; Thu, 21 Sep 2017 16:35:56 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8222 on Selecting Labels for Use with Conventional DNS and Other Resolution Systems in DNS-Based Service Discovery
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, dnssd@ietf.org
Message-Id: <20170921233556.8F701B817A3@rfc-editor.org>
Date: Thu, 21 Sep 2017 16:35:56 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/3CmtB83U9BjcZ7BcUSL2NstH4DY>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 21 Sep 2017 23:36:25 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8222
Title: Selecting Labels for Use with
Conventional DNS and Other Resolution Systems
in DNS-Based Service Discovery
Author: A. Sullivan
Status: Informational
Stream: IETF
Date: September 2017
Mailbox: asullivan@dyn.com
Pages: 11
Characters: 28735
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-dnssd-mdns-dns-interop-04.txt
URL: https://www.rfc-editor.org/info/rfc8222
DOI: 10.17487/RFC8222
Despite its name, DNS-Based Service Discovery (DNS-SD) can use naming
systems other than DNS when looking for services. Moreover, when it
uses DNS, DNS-SD uses the full capability of DNS, rather than using a
subset of available octets. This is of particular relevance where
some environments use DNS labels that conform to Internationalized
Domain Names for Applications (IDNA), and other environments use
labels containing Unicode characters (such as containing octets
corresponding to characters encoded as UTF-8). In order for DNS-SD
to be used effectively in environments where multiple different name
systems and conventions for their operation are in use, it is
important to attend to differences in the underlying technology and
operational environment. This memo presents an outline of the
requirements for the selection of labels for conventional DNS and
other resolution systems when they are expected to interoperate in
this manner.
This document is a product of the Extensions for Scalable DNS Service Discovery Working Group of the IETF.
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
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