[rfc-dist] RFC 4848 on Domain-Based Application Service Location Using URIs and the Dynamic Delegation Discovery Service (DDDS)

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Mon Apr 30 20:57:47 PDT 2007


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

        
        RFC 4848

        Title:      Domain-Based Application Service Location Using 
                    URIs and the Dynamic Delegation Discovery 
                    Service (DDDS) 
        Author:     L. Daigle
        Status:     Standards Track
        Date:       April 2007
        Mailbox:    leslie at thinkingcat.com
        Pages:      10
        Characters: 19341
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-daigle-unaptr-02.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4848.txt

The purpose of this document is to define a new, straightforward
Dynamic Delegation Discovery Service (DDDS) application to allow
mapping of domain names to URIs for particular application services
and protocols.  Although defined as a new DDDS application, dubbed
U-NAPTR, this is effectively an extension of the Straightforward
NAPTR (S-NAPTR) DDDS Application.  [STANDARDS TRACK]

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

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at 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 at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...




More information about the rfc-dist mailing list