From owner-ietf-fax@mail.imc.org Fri May 17 07:46:13 2002 Received: from above.proper.com (mail.imc.org [208.184.76.43]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09274 for ; Fri, 17 May 2002 07:46:13 -0400 (EDT) Received: by above.proper.com (8.11.6/8.11.3) id g4HBPlN20866 for ietf-fax-bks; Fri, 17 May 2002 04:25:47 -0700 (PDT) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g4HBPkL20862 for ; Fri, 17 May 2002 04:25:46 -0700 (PDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08288; Fri, 17 May 2002 07:25:30 -0400 (EDT) Message-Id: <200205171125.HAA08288@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ietf-fax@imc.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-fax-tiff-regbis-05.txt Date: Fri, 17 May 2002 07:25:30 -0400 Sender: owner-ietf-fax@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Internet Fax Working Group of the IETF. Title : Tag Image File Format (TIFF) - image/tiff MIME Sub-type Registration Author(s) : G. Parsons, J. Rafferty Filename : draft-ietf-fax-tiff-regbis-05.txt Pages : 8 Date : 16-May-02 This document describes the registration of the MIME sub-type image/tiff. The baseline encoding of TIFF (Tag Image File Format) is defined by [TIFF]. This document refines an earlier sub-type registration in RFC 1528 [TPC.INT]. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-fax-tiff-regbis-05.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-fax-tiff-regbis-05.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-fax-tiff-regbis-05.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20020516145507.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-fax-tiff-regbis-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-fax-tiff-regbis-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20020516145507.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-ietf-fax@mail.imc.org Tue May 28 02:15:28 2002 Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09405 for ; Tue, 28 May 2002 02:15:27 -0400 (EDT) Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g4S5rbO07589 for ietf-fax-bks; Mon, 27 May 2002 22:53:37 -0700 (PDT) Received: from bulls.mei.co.jp (bulls.mei.co.jp [202.224.189.25]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g4S5rZJ07585 for ; Mon, 27 May 2002 22:53:35 -0700 (PDT) Received: by bulls.mei.co.jp (8.12.2/3.7W/jazz) with ESMTP id g4S5qpmP023235; Tue, 28 May 2002 14:52:51 +0900 (JST) Received: by mail.jp.panasonic.com (8.11.6/3.7W/bluejays) with SMTP id g4S5qpT23863; Tue, 28 May 2002 14:52:51 +0900 (JST) Received: from no.name.available by m-bb2.mgcs.mei.co.jp via smtpd (for [157.8.1.150]) with SMTP; 28 May 2002 05:52:51 UT Received: from mlsv1.mgcs.mei.co.jp by mlsv0-1.mgcs.mei.co.jp (8.12.2/3.7W-HUB) with ESMTP id g4S5obCW015723; Tue, 28 May 2002 14:50:37 +0900 (JST) Received: from mlsv2.rdmg.mgcs.mei.co.jp by mlsv1.mgcs.mei.co.jp (8.9.3/3.7W-MGCS) with ESMTP id OAA13776; Tue, 28 May 2002 14:52:50 +0900 (JST) Received: from d23n59.rdmg.mgcs.mei.co.jp by mlsv2.rdmg.mgcs.mei.co.jp (8.12.2/3.7W-RDMG) with SMTP id g4S5qWlI027277; Tue, 28 May 2002 14:52:32 +0900 (JST) Message-Id: <200205280600.AA01259@d23n59.rdmg.mgcs.mei.co.jp> From: "Toyoda, Kiyoshi" Date: Tue, 28 May 2002 15:00:00 +0900 To: Richard Shockey Cc: Patrik =?ISO-2022-JP?B?RhskQmdNGyhCdHN0chskQiIuGyhC?= , enum@ietf.org, ietf-fax@imc.org Subject: Re: [Enum] SchemaSet strawman In-Reply-To: <5.1.0.14.2.20020527125808.021ed588@popd.ix.netcom.com> References: <5.1.0.14.2.20020527125808.021ed588@popd.ix.netcom.com> MIME-Version: 1.0 X-Mailer: AL-Mail32 Version 1.12 Content-Type: text/plain; charset=us-ascii Sender: owner-ietf-fax@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Shockey-san, I would like to propose ifax services of ENUM. I comment below. Richard Shockey wrote: >> >>What I have heard is more like: >> >> NAPTR blabla "E2U+telvoice" blabla tel:+4317978032;svc=voice >> NAPTR blabla "E2U+telfax" blabla tel:+4317978013;svc=fax >> NAPTR blabla "E2U+telsms" blabla tel:+436644204100;sms=sms >> >>I.e. in your first example, what is the meaning of "tel"? What is the >>registration of "voice"? What if only "tel" exists and not "voice"? What if >>"voice" exists and not "tel"? >> >>The '+' sign is to separate enumservices alltogether. If we are going down >>the path of "subservices" then we need to use a different separator, like >>'-'. I would like to NOT go down that path if not really really needed. And >>I really mean needed from a technical standpoint and not only "because the >>design looks nice". > >On reflection, I stand corrected Patrik ..I think you are right ... the '+' >should separate distinct services. > >So to follow your example in the case of SMTP you would >suggest "E2U+smtpfaxs" for possibly designating Simple Mode Fax [RFC2503] >and "E2U+smptfaxf" for Full Mode or something like that. A single >enumservice designator. > I want to use ENUM for two services of IFAX. One is a service to get simply e-mail address of destination. Another is a service to get URI of directory server such as LDAP which has the e-mail address and capability of destination IFAX. I think that the former service will be acceptable easier by IFAX WG and ENUM WG than latter. So, I made a simple draft below at first. Please comment. ------------------------------------------------------------------- Network Working Group K. Toyoda, MGCS Internet Draft May 2002 Expires: November 2002 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. 1. Functional Specification An IFax client makes an Enum DNS query with 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] 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 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. Example $ORIGIN 4.3.2.1.6.7.9.8.6.4.e164.arpa IN NAPTR 10 10 "u" "E2U+ifax" "!^.*$!mailto:paf@ifax.net!" 2.3 Intended usage COMMON 3 Security Consideration The Security Considerations section of [RFC2305] and [RFC2532] applies to this document. 4. ACKNOWLEDGEMENTS Dave Crocker provided useful suggestions to an earlier draft. 5. REFERENCES [ENUMbis] Falstrom, P., M. Mealling, "The E.164 to URI DDDS Application", draft-ietf-enum-rfc2916bis-00, February 22, 2002 [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 6. AUTHORS' ADDRESSES Kiyoshi Toyoda Matsushita Graphic Communication Systems,Inc 2-3-8 Shimomeguro, Meguro-Ku Tokyo 153 JAPAN +81.3.5434.7161 ktoyoda@rdmg.mgcs.mei.co.jp 7. 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. Kiyoshi Toyoda