[Docs] [txt|pdf] [Tracker] [WG] [Email] [Nits]

Versions: 00 01 02 03 RFC 4143

Network Working Group                         K. Toyoda, PCC
Internet Draft                       D. Crocker, Brandenburg
draft-ietf-fax-faxservice-enum-00
Expires: August 2003                           February 2003




                   IFAX service of ENUM



     STATUS OF THIS MEMO

     This document is an Internet-Draft and is in full
     conformance with all provisions of Section 10 of
     RFC2026. Internet-Drafts are working documents of the
     Internet Engineering Task Force (IETF), its areas, and
     its working groups.  Note that other groups may also
     distribute working documents as Internet-Drafts.

     Internet-Drafts are draft documents valid for a maximum
     of six months and may be updated, replaced, or
     obsoleted by other documents at any time.  It is
     inappropriate to use Internet-Drafts as reference
     material or to cite them other than as "work in
     progress."

     The list of current Internet-Drafts can be accessed at
          http://www.ietf.org/ietf/1id-abstracts.txt

     The list of Internet-Draft Shadow Directories can be
     accessed at
          http://www.ietf.org/shadow.html.

     COPYRIGHT NOTICE

     Copyright (C) The Internet Society (2001).  All Rights
     Reserved.

     The key words "MUST", "MUST NOT", "SHOULD", "SHOULD
     NOT", and "MAY" in this document are to be interpreted
     as defined in "Key words for use in RFCs to Indicate
     Requirement Levels" [KEYWORDS].


Abstract

     This document describes the functional specification
     and the definition of the ENUM NAPTR record, for IFax
     service. IFax is "Facsimile using Internet Mail".  For
     this use, the DNS returns the email address of the
     referenced IFax system. This mechanism allows email-based
     fax communication to use telephone numbers, rather than
     requiring that the sender already know the recipient
     email address.


1.   Functional Specification

    An IFax client makes an [ENUMbis] DNS query, using the target
    system's telephone number.  The returned NAPTR record
    specifies an email address that is to be used for reaching
    the target system.  The email address is then used in
    accordance with "Simple Mode of Facsimile using Internet
    Mail" [RFC2305] or "Extended Facsimile using Internet
    Mail" [RFC2532]. "Full Mode Fax Profile for Internet Mail"
    is applied when it is approved as an Internet standards-track
    specification.

2.   Definition of NAPTR record
2.1 Service Name
    Service Name = "ifax"
    The scope of this service is facsimile using Internet mail.
    It includes "Simple Mode of Facsimile using Internet Mail"
    and "Extended Facsimile using Internet Mail". "Full Mode
    Fax Profile for Internet Mail" is applied when it is
    approved as an Internet standards-track specification.

2.2 Type
    Type = "ifax"

2.3 Subtype
    Subtype = "mailto"

2.4 URI Scheme
    Scheme = "mailto"

    The URI Scheme is "mailto" because facsimile using
    Internet Mail is a profile for standard Internet mail and
    uses standard Internet mail addressing.

2.5 Example
    $ORIGIN 4.3.2.1.6.7.9.8.6.4.e164.arpa
      IN NAPTR 10 10 "u" "E2U+ifax:mailto" "!^.*$!mailto:toyo@ifax.com!"

2.6 Intended usage
    COMMON


3 Security Consideration
    The Security Considerations section of [RFC2305] and
    [RFC2532] applies to this document. In addition, note
    that DNS records are public.  Therefore the mapping between
    a telephone number and a specific email address is public.


4.   REFERENCES
     [ENUMbis]  Falstrom, P., M. Mealling, "The E.164 to URI
     DDDS Application", draft-ietf-enum-rfc2916bis-03,
     January 22, 2003

     [RFC2305] Toyoda, K., Ohno, H., Murai, J. and  D. Wing, "A
     Simple Mode of Facsimile Using Internet Mail", RFC 2305,
     March 1998.

     [RFC2532] Masinter, L., D. Wing, "Extended Facsimile Using
     Internet Mail", March 1999

     [FFPIM] Crocker, D., G. Klyne, L. Masinter, "Full-mode
     Fax Profile for Internet Mail", DRAFT-IETF-FAX-FFPIM-03,
     March, 2002


5.       AUTHORS' ADDRESSES

     Kiyoshi Toyoda
     Network Technology Development Center
     Panasonic Communications Co., Ltd.
     2-3-8 Shimomeguro, Meguro-ku, Tokyo 153-8687, Japan

     tel: +81-3-5434-7161
     fax: +81-3-5434-7156
     toyoda.kiyoshi@jp.panasonic.com


     Dave Crocker
     Brandenburg InternetWorking
     675 Spruce Drive
     Sunnyvale, CA  94086  USA

     Tel: +1.408.246.8253
     dcrocker@brandenburg.com


6.       FULL COPYRIGHT STATEMENT

     Copyright (C) The Internet Society (2001).  All Rights
     Reserved.

     This document and translations of it may be copied and
     furnished to others, and derivative works that comment
     on or otherwise explain it or assist in its
     implementation may be prepared, copied, published and
     distributed, in whole or in part, without restriction
     of any kind, provided that the above copyright notice
     and this paragraph are included on all such copies and
     derivative works.  However, this document itself may
     not be modified in any way, such as by removing the
     copyright notice or references to the Internet Society
     or other Internet organizations, except as needed for
     the purpose of developing Internet standards in which
     case the procedures for copyrights defined in the
     Internet Standards process must be followed, or as
     required to translate it into languages other than
     English.

     The limited permissions granted above are perpetual and
     will not be revoked by the Internet Society or its
     successors or assigns.

     This document and the information contained herein is
     provided on an "AS IS" basis and THE INTERNET SOCIETY
     AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL
     WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT
     LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
     HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
     WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
     PARTICULAR PURPOSE.


Html markup produced by rfcmarkup 1.107, available from http://tools.ietf.org/tools/rfcmarkup/