RFC 4002 on IANA Registration for Enumservice 'web' and 'ft'

rfc-editor@rfc-editor.org Mon, 14 February 2005 23:57 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04563; Mon, 14 Feb 2005 18:57:56 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0qRF-0000Px-KP; Mon, 14 Feb 2005 19:19:37 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0pzd-0001ml-Ph; Mon, 14 Feb 2005 18:51:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0px1-0001Yx-0o; Mon, 14 Feb 2005 18:48:23 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03621; Mon, 14 Feb 2005 18:48:19 -0500 (EST)
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0qHw-00008W-K6; Mon, 14 Feb 2005 19:10:01 -0500
Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id j1ENj3Q03247; Mon, 14 Feb 2005 15:45:03 -0800 (PST)
Message-Id: <200502142345.j1ENj3Q03247@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Mon, 14 Feb 2005 15:45:03 -0800
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Cc: enum@ietf.org, rfc-editor@rfc-editor.org
Subject: RFC 4002 on IANA Registration for Enumservice 'web' and 'ft'
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6

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


        RFC 4002

        Title:      IANA Registration for Enumservice 'web' and 'ft'
        Author(s):  R. Brandner, L. Conroy, R. Stastny
        Status:     Standards Track
        Date:       February 2005
        Mailbox:    rudolf.brandner@siemens.com, lwc@roke.co.uk,
                    richard.stastny@oefeg.at
        Pages:      10
        Characters: 18072
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-enum-webft-01.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4002.txt


This document registers the Enumservices 'web' and 'ft' by using the
URI schemes 'http:', 'https:' and 'ftp:' as per the IANA
registration process defined in the ENUM specification (RFC 3761).

This document is a product of the Telephone Number Mapping 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.

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/rfc4002.txt"><ftp://ftp.isi.edu/in-notes/rfc4002.txt>
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce