PWG> FW: RFC 4143 on Facsimile Using Internet Mail (IFAX) Service of E NUM

PWG> FW: RFC 4143 on Facsimile Using Internet Mail (IFAX) Service of E NUM

PWG> FW: RFC 4143 on Facsimile Using Internet Mail (IFAX) Service of E NUM

McDonald, Ira imcdonald at sharplabs.com
Sat Nov 19 10:54:58 EST 2005


-----Original Message-----
From: owner-ietf-fax at mail.imc.org [mailto:owner-ietf-fax at mail.imc.org]On
Behalf Of rfc-editor at rfc-editor.org
Sent: Friday, November 18, 2005 6:18 PM
To: ietf-announce at ietf.org
Cc: rfc-editor at rfc-editor.org; ietf-fax at imc.org
Subject: RFC 4143 on Facsimile Using Internet Mail (IFAX) Service of
ENUM



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


        RFC 4143

        Title:      Facsimile Using Internet Mail (IFAX) Service of
                    ENUM
        Author(s):  K. Toyoda, D. Crocker
        Status:     Standards Track
        Date:       November 2005
        Mailbox:    toyoda.kiyoshi at jp.panasonic.com, dcrocker at bbiw.net
        Pages:      5
        Characters: 8642
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-fax-faxservice-enum-03.txt

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


This document describes the functional specification and definition of
the ENUM Naming Authority Pointer (NAPTR) record for IFax service.
IFax is "facsimile using Internet mail".  For this use, the Domain
Name System (DNS) returns the email address of the referenced IFax
system.  This mechanism allows email-based fax communication to use
telephone numbers instead of requiring the sender to already know the
recipient email address. 

This document is a product of the Internet Fax 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 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.


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.

-------------- next part --------------
An embedded message was scrubbed...
From: unknown sender
Subject: 
Date: Sat, 19 Nov 2005 07:55:00 -0800
Size: 869
Url: http://www.pwg.org/archives/pwg/attachments/20051119/b173d327/attachment.mht


More information about the Pwg mailing list