RFC 2782 on DNS SRV RR

RFC Editor <rfc-ed@ISI.EDU> Fri, 25 February 2000 01:08 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13527; Thu, 24 Feb 2000 20:08:02 -0500 (EST)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id UAA13031 for ietf-123-outbound.10@ietf.org; Thu, 24 Feb 2000 20:05:05 -0500 (EST)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id TAA12929 for <all-ietf@loki.ietf.org>; Thu, 24 Feb 2000 19:48:00 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13263 for <all-ietf@ietf.org>; Thu, 24 Feb 2000 19:47:56 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id QAA25242; Thu, 24 Feb 2000 16:47:43 -0800 (PST)
Message-Id: <200002250047.QAA25242@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2782 on DNS SRV RR
Cc: rfc-ed@ISI.EDU, namedroppers@internic.net
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 24 Feb 2000 16:47:43 -0800
From: RFC Editor <rfc-ed@ISI.EDU>

A new Request for Comments is now available in online RFC libraries.


        RFC 2782

        Title:	    A DNS RR for specifying the location of services
                    (DNS SRV)
        Author(s):  A. Gulbrandsen, P. Vixie, L. Esibov
        Status:     Standards Track
	Date:       February 2000
        Mailbox:    agulbra@troll.no, vixie@isc.org,
                    levone@microsoft.com 
        Pages:      12
        Characters: 24013
	Obsoletes:  2052
        I-D Tag:    draft-ietf-dnsind-rfc2052bis-05.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2782.txt


This document describes a DNS RR which specifies the location of the
server(s) for a specific protocol and domain.

This document is a product of the DNS IXFR, Notification, and Dynamic
Update Working Group of the IETF.

This is now a Proposed Standard Protocol.

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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
ftp://ftp.isi.edu/in-notes/rfc2782.txt"><ftp://ftp.isi.edu/in-notes/rfc2782.txt>