One document matched: draft-ietf-fax-faxservice-enum-03.txt

Differences from draft-ietf-fax-faxservice-enum-02.txt

Network Working Group                         K. Toyoda, PCC
Internet Draft                       D. Crocker, Brandenburg
draft-ietf-fax-faxservice-enum-03                   
Expires: December 2004                             June 2004




                   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" [FFPIM]
    is applied when it is approved as an Internet standards-track 
    specification.


2.  IFax service Registration 

    Service Name : "E2U+ifax"

    Type: "ifax"

    Subtype: "mailto"

    URI Scheme: "mailto"
    The URI Scheme is "mailto" because facsimile is a profile of  
    standard Internet mail and uses standard Internet mail addressing.

    Functional Specification: see section 1

    Security Considerations: see section 3

    Intended usage: COMMON

    Author: Kiyoshi Toyoda(toyoda.kiyoshi@jp.panasonic.com)
            Dave Crocker(dcrocker@brandenburg.com)


3. Security Consideration

   DNS, as used by ENUM, is a global, distributed database. Thus any
   information stored there is visible to anyone anonymously. Whilst
   this is not qualitatively different from publication in a Telephone
   Directory, it does open the data subject to having "their"
   information collected automatically without any indication that 
   this has been done or by whom.

   Such data harvesting by third parties is often used to generate 
   lists of targets for unrequested information; in short, they are 
   used to address "spam". Publication of a telephone number in ENUM, 
   especially when it is an associated Internet Fax service, may be 
   used to send "junk faxes" for example.

   In the case of electronic mail, users subscribed to mailing lists
   can have "sacrificial" email accounts. These special-purpose
   addresses help the user to filter out unrequested email that is
   sent to them. This is not so easy with published telephone
   numbers. The PSTN E.164 number assignment process is much more
   involved and less flexible; usually a single E.164 number (or a
   fixed range of numbers) is associated with each PSTN access. Thus
   it is not possible to use a "sacrificial" phone number.

   Due to the implications of publishing data on a globally accessible
   database, as a principle the data subject MUST give their explicit
   informed consent to data being published in ENUM.

   Internet Fax is based on use of existing Internet mail. Developers 
   and users should also consider the Security Consideration section 
   in [RFC2305] and [RFC2532].

   In addition to the specific security considerations given above, 
   the Security Consideration section of [ENUMbis] applies to this 
   document.


4.  Example
    The following is an example of the use of IFax service

    in a NAPTR record.

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


5. IANA CONSIDERATIONS

     This specification creates a DNS NAPTR registration, according to
     the terms specified in [ENUMbis]

     The registration details are contained in section 2, 
     "Fax service Registration", above.


6. REFERENCES
6.1  NORMATIVE REFERENCES
     [KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate
     Requirement Levels", RFC2119, March 1997

     [ENUMbis]  Falstrom, P., M. Mealling, "The E.164 to Uniform 
     Resource Identifiers (URI) Dynamic Delegation Discovery 
     System (DDDS) Application (ENUM)", RFC3761, April 2004

     [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, "Full-mode Fax Profile for 
     Internet Mail", DRAFT-IETF-FAX-FFPIM-04(work in progress), 
     June 2004


7.       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-5745-3921
     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
     

8.       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.