New Version Notification for draft-gudmundsson-dnsext-srv-clarify-02 (fwd)

Alfred Hönes <ah@TR-Sys.de> Fri, 22 October 2010 17:30 UTC

Return-Path: <A.Hoenes@TR-Sys.de>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 96EE73A6936; Fri, 22 Oct 2010 10:30:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.268
X-Spam-Level:
X-Spam-Status: No, score=-98.268 tagged_above=-999 required=5 tests=[AWL=0.481, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QDpBH2qehiGj; Fri, 22 Oct 2010 10:30:29 -0700 (PDT)
Received: from TR-Sys.de (gateway.tr-sys.de [213.178.172.147]) by core3.amsl.com (Postfix) with ESMTP id D47F828C0E8; Fri, 22 Oct 2010 10:30:26 -0700 (PDT)
Received: from ZEUS.TR-Sys.de by w. with ESMTP ($Revision: 1.37.109.26 $/16.3.2) id AA082568713; Fri, 22 Oct 2010 19:31:53 +0200
Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id TAA28915; Fri, 22 Oct 2010 19:31:51 +0200 (MESZ)
From: Alfred Hönes <ah@TR-Sys.de>
Message-Id: <201010221731.TAA28915@TR-Sys.de>
Subject: New Version Notification for draft-gudmundsson-dnsext-srv-clarify-02 (fwd)
To: apps-discuss@ietf.org, tsvwg@ietf.org
Date: Fri, 22 Oct 2010 19:31:51 +0200
X-Mailer: ELM [$Revision: 1.17.214.3 $]
Mime-Version: 1.0
Content-Type: text/plain; charset="hp-roman8"
Content-Transfer-Encoding: 8bit
Cc: nfsv4@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 17:30:36 -0000

Folks,
Apologies for cross-posting,
but DNS-based service discovery is such a pervasive subject...

We have uploaded a new version of our DNS SRV clarifications draft
that, according to an agreement at IETF 76, is planned for coordinated
publication with the document that lays the foundation for the upcoming
unified IANA "Service Name and Transport Protocol Port Number" Registry,
and with another Informational document (still in progress) that will
describe cleanup operations for related IANA registries that have
become outdated (or will do so due to this major streamlining), and
that will give recommendations for how to update use cases of DNS SRV
specified in RFCs (or currently being discussed in the IETF) that
do not conform to the emerging new rules (and arguably never did
so with the previous rules).

The new version addresses comments by giving even more background
information and providing additional clarifications, and it has
been brought in close alignment with the recent updates to the
registry document per draft-ietf-tsvwg-iana-ports-07.
Beyond that, the revised draft contains numerous editorial improvements.

Kind regards,
  Alfred Hönes.


----- Forwarded message from IETF I-D Submission Tool -----

> Message-Id: <20101022164123.7AF403A690A@core3.amsl.com>
> Date: Fri, 22 Oct 2010 09:41:22 -0700 (PDT)
> Subject: New Version Notification for draft-gudmundsson-dnsext-srv-clarify-02

A new version of I-D, draft-gudmundsson-dnsext-srv-clarify-02.txt
has been successfully submitted by Alfred Hoenes and posted
to the IETF repository.

Filename:        draft-gudmundsson-dnsext-srv-clarify
Revision:        02
Title:           DNS SRV Usage Guidelines and Owner Name Recommendations
Creation_date:   2010-10-22
WG ID:           Independent Submission
Number_of_pages: 20

Abstract:
The DNS SRV record has been specified in RFC 2052 and RFC 2782 for
use in dynamic service discovery for a domain.  These two RFCs did
not clearly specify an IANA registry for the names of the services
and their underlying protocols.  This document clarifies RFC 2782
regarding the formation and use of the Service Prefix in the owner
name of SRV records, based on the unified IANA "Service Name and
Transport Protocol Port Number" registry and provides a few other
corrections, clarifications, and usage recommendations.


The IETF Secretariat.


----- End of forwarded message from IETF I-D Submission Tool -----