< draft-ietf-fax-faxservice-enum-02.txt		draft-ietf-fax-faxservice-enum-03.txt >
	Network Working Group K. Toyoda, PCC		Network Working Group K. Toyoda, PCC
	Internet Draft D. Crocker, Brandenburg		Internet Draft D. Crocker, Brandenburg
	draft-ietf-fax-faxservice-enum-02		draft-ietf-fax-faxservice-enum-03
	Expires: September 2004 March 2004		Expires: December 2004 June 2004
	IFAX service of ENUM		IFAX service of ENUM
	STATUS OF THIS MEMO		STATUS OF THIS MEMO
	This document is an Internet-Draft and is in full		This document is an Internet-Draft and is in full
	conformance with all provisions of Section 10 of		conformance with all provisions of Section 10 of
	RFC2026. Internet-Drafts are working documents of the		RFC2026. Internet-Drafts are working documents of the
	Internet Engineering Task Force (IETF), its areas, and		Internet Engineering Task Force (IETF), its areas, and
	its working groups. Note that other groups may also		its working groups. Note that other groups may also
	skipping to change at line 61 ¶		skipping to change at line 61 ¶
	email address.		email address.
	1. Functional Specification		1. Functional Specification
	An IFax client makes an [ENUMbis] DNS query, using the target		An IFax client makes an [ENUMbis] DNS query, using the target
	system's telephone number. The returned NAPTR record		system's telephone number. The returned NAPTR record
	specifies an email address that is to be used for reaching		specifies an email address that is to be used for reaching
	the target system. The email address is then used in		the target system. The email address is then used in
	accordance with "Simple Mode of Facsimile using Internet		accordance with "Simple Mode of Facsimile using Internet
	Mail" [RFC2305] or "Extended Facsimile using Internet		Mail" [RFC2305] or "Extended Facsimile using Internet
	Mail" [RFC2532]. "Full Mode Fax Profile for Internet Mail"		Mail" [RFC2532]. "Full Mode Fax Profile for Internet Mail" [FFPIM]
	is applied when it is approved as an Internet standards-track		is applied when it is approved as an Internet standards-track
	specification.		specification.
	2. IFax service Registration		2. IFax service Registration
	Service Name : "E2U+ifax"		Service Name : "E2U+ifax"
	Type: "ifax"		Type: "ifax"
	Subtype: "mailto"		Subtype: "mailto"
	skipping to change at line 92 ¶		skipping to change at line 92 ¶
	Author: Kiyoshi Toyoda(toyoda.kiyoshi@jp.panasonic.com)		Author: Kiyoshi Toyoda(toyoda.kiyoshi@jp.panasonic.com)
	Dave Crocker(dcrocker@brandenburg.com)		Dave Crocker(dcrocker@brandenburg.com)
	3. Security Consideration		3. Security Consideration
	DNS, as used by ENUM, is a global, distributed database. Thus any		DNS, as used by ENUM, is a global, distributed database. Thus any
	information stored there is visible to anyone anonymously. Whilst		information stored there is visible to anyone anonymously. Whilst
	this is not qualitatively different from publication in a Telephone		this is not qualitatively different from publication in a Telephone
	Directory, it does open the data subject to having "their"		Directory, it does open the data subject to having "their"
	information collected automatically without any indication that this		information collected automatically without any indication that
	has been done or by whom.		this has been done or by whom.
	Such data harvesting by third parties is often used to generate lists		Such data harvesting by third parties is often used to generate
	of targets for unrequested information; in short, they are used to		lists of targets for unrequested information; in short, they are
	address "spam". Publication of a telephone number in ENUM, expecially		used to address "spam". Publication of a telephone number in ENUM,
	when it as an associated Internet Fax service, may be used to send		especially when it is an associated Internet Fax service, may be
	"junk faxes" for example.		used to send "junk faxes" for example.
	In the case of electronic mail, users subscribed to mailing list		In the case of electronic mail, users subscribed to mailing lists
	can have "sacrificial" email accounts. These special-purpose		can have "sacrificial" email accounts. These special-purpose
	addresses help the user to filter out unrequested email that is		addresses help the user to filter out unrequested email that is
	sent to them. This is not so easy with published telephone		sent to them. This is not so easy with published telephone
	numbers. The PSTN E.164 number assignment process is much more		numbers. The PSTN E.164 number assignment process is much more
	involved and less flexible; usually a single E.164 number (or a		involved and less flexible; usually a single E.164 number (or a
	fixed range of numbers) is associated with each PSTN access. Thus		fixed range of numbers) is associated with each PSTN access. Thus
	it is not possible to use a "sacrificial" phone number.		it is not possible to use a "sacrificial" phone number.
	Due to the implications of publishing data on a globally accessible		Due to the implications of publishing data on a globally accessible
	database, as a principle the data subject MUST give their explicit		database, as a principle the data subject MUST give their explicit
	informed consent to data being published in ENUM.		informed consent to data being published in ENUM.
	Internet Fax is based on use of existing Internet mail. Developers and		Internet Fax is based on use of existing Internet mail. Developers
	users should also consider the Security Consideration section in [RFC2305].		and users should also consider the Security Consideration section
	and [RFC2532].		in [RFC2305] and [RFC2532].
	In addition to the specific security considerations given above, the Security		In addition to the specific security considerations given above,
	Consideration section of [ENUMbis] applies to this document.		the Security Consideration section of [ENUMbis] applies to this
			document.
	4. Example		4. Example
	The following is an example of the use of IFax service		The following is an example of the use of IFax service
	in a NAPTR record.		in a NAPTR record.
	$ORIGIN 4.3.2.1.6.7.9.8.6.4.e164.arpa		$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!"		IN NAPTR 10 10 "u" "E2U+ifax:mailto"
			"!^.*$!mailto:toyo@example.com!"
	5. IANA CONSIDERATIONS		5. IANA CONSIDERATIONS
	This specification creates a DNS NAPTR registration, according to		This specification creates a DNS NAPTR registration, according to
	the terms specified in [ENUMbis]		the terms specified in [ENUMbis]
	The registration details are contained in section 2,		The registration details are contained in section 2,
	"Fax service Registration", above.		"Fax service Registration", above.
	6. REFERENCES		6. REFERENCES
	[ENUMbis] Falstrom, P., M. Mealling, "The E.164 to URI		6.1 NORMATIVE REFERENCES
	DDDS Application", draft-ietf-enum-rfc2916bis-07(work in progress),		[KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate
	November, 2003		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		[RFC2305] Toyoda, K., Ohno, H., Murai, J. and D. Wing, "A
	Simple Mode of Facsimile Using Internet Mail", RFC 2305,		Simple Mode of Facsimile Using Internet Mail", RFC 2305,
	March 1998.		March 1998.
	[RFC2532] Masinter, L., D. Wing, "Extended Facsimile Using		[RFC2532] Masinter, L., D. Wing, "Extended Facsimile Using
	Internet Mail", March 1999		Internet Mail", March 1999
	[FFPIM] Crocker, D., G. Klyne, L. Masinter, "Full-mode		[FFPIM] Crocker, D., G. Klyne, "Full-mode Fax Profile for
	Fax Profile for Internet Mail", DRAFT-IETF-FAX-FFPIM-02(work in progress),		Internet Mail", DRAFT-IETF-FAX-FFPIM-04(work in progress),
	February, 2004		June 2004
	7. AUTHORS' ADDRESSES		7. AUTHORS' ADDRESSES
	Kiyoshi Toyoda		Kiyoshi Toyoda
	Network Technology Development Center		Network Technology Development Center
	Panasonic Communications Co., Ltd.		Panasonic Communications Co., Ltd.
	2-3-8 Shimomeguro, Meguro-ku, Tokyo 153-8687, Japan		2-3-8 Shimomeguro, Meguro-ku, Tokyo 153-8687, Japan
	tel: +81-3-5745-3921		tel: +81-3-5745-3921
	fax: +81-3-5434-7156		fax: +81-3-5434-7156
End of changes. 10 change blocks.
	24 lines changed or deleted		30 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/