< draft-ietf-rmt-flute-revised-15.txt		draft-ietf-rmt-flute-revised-16.txt >
	Reliable Multicast Transport (RMT) T. Paila		Reliable Multicast Transport (RMT) T. Paila
	Internet-Draft Nokia		Internet-Draft Nokia
	Obsoletes: 3926 (if approved) R. Walsh		Obsoletes: 3926 (if approved) R. Walsh
	Intended status: Standards Track Tampere University of Technology		Intended status: Standards Track Tampere University of Technology
	Expires: December 15, 2012 M. Luby		Expires: December 29, 2012 M. Luby
	Qualcomm, Inc.		Qualcomm, Inc.
	V. Roca		V. Roca
	INRIA		INRIA
	R. Lehtonen		R. Lehtonen
	TeliaSonera		TeliaSonera
	June 13, 2012		June 27, 2012
	FLUTE - File Delivery over Unidirectional Transport		FLUTE - File Delivery over Unidirectional Transport
	draft-ietf-rmt-flute-revised-15		draft-ietf-rmt-flute-revised-16
	Abstract		Abstract
	This document defines FLUTE, a protocol for the unidirectional		This document defines FLUTE, a protocol for the unidirectional
	delivery of files over the Internet, which is particularly suited to		delivery of files over the Internet, which is particularly suited to
	multicast networks. The specification builds on Asynchronous Layered		multicast networks. The specification builds on Asynchronous Layered
	Coding, the base protocol designed for massively scalable multicast		Coding, the base protocol designed for massively scalable multicast
	distribution. This document obsoletes RFC3926.		distribution. This document obsoletes RFC3926.
	Status of this Memo		Status of this Memo
	skipping to change at page 1, line 41 ¶		skipping to change at page 1, line 41 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on December 15, 2012.		This Internet-Draft will expire on December 29, 2012.
	Copyright Notice		Copyright Notice
	Copyright (c) 2012 IETF Trust and the persons identified as the		Copyright (c) 2012 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 3, line 43 ¶		skipping to change at page 3, line 43 ¶
	7.3.1. Attacks against the Session Description . . . . . . . 31		7.3.1. Attacks against the Session Description . . . . . . . 31
	7.3.2. Attacks against the FDT Instances . . . . . . . . . . 31		7.3.2. Attacks against the FDT Instances . . . . . . . . . . 31
	7.3.3. Attacks against the ALC/LCT parameters . . . . . . . . 32		7.3.3. Attacks against the ALC/LCT parameters . . . . . . . . 32
	7.3.4. Attacks against the associated Building Blocks . . . . 32		7.3.4. Attacks against the associated Building Blocks . . . . 32
	7.4. Other Security Considerations . . . . . . . . . . . . . . 33		7.4. Other Security Considerations . . . . . . . . . . . . . . 33
	7.5. Minimum Security Recommendations . . . . . . . . . . . . . 34		7.5. Minimum Security Recommendations . . . . . . . . . . . . . 34
	8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34		8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34
	8.1. Registration of the FDT Instance XML Namespace . . . . . . 34		8.1. Registration of the FDT Instance XML Namespace . . . . . . 34
	8.2. Registration of the FDT Instance XML Schema . . . . . . . 35		8.2. Registration of the FDT Instance XML Schema . . . . . . . 35
	8.3. Registration of the application/fdt+xml Media-Type . . . . 35		8.3. Registration of the application/fdt+xml Media-Type . . . . 35
	8.4. Registration of the Content Encoding Algorithm . . . . . . 36		8.4. Creation of the FLUTE Content Encoding Algorithms
	8.4.1. Explicit IANA Assignment Guidelines . . . . . . . . . 36		registry . . . . . . . . . . . . . . . . . . . . . . . . . 36
	8.5. Registration of the EXT_FDT LCT Header Extension Type . . 36		8.5. Registration of LCT Header Extension Types . . . . . . . . 36
	8.6. Registration of the EXT_CENC LCT Header Extension Type . . 37
	9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 37		9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 37
	10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 37		10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 37
	11. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 38		11. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 37
	11.1. RFC3926 to draft-ietf-rmt-flute-revised-12 . . . . . . . . 38		11.1. RFC3926 to draft-ietf-rmt-flute-revised-12 . . . . . . . . 37
	12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 40		12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 40
	12.1. Normative references . . . . . . . . . . . . . . . . . . . 40		12.1. Normative references . . . . . . . . . . . . . . . . . . . 40
	12.2. Informative references . . . . . . . . . . . . . . . . . . 42		12.2. Informative references . . . . . . . . . . . . . . . . . . 41
	Appendix A. Receiver operation (informative) . . . . . . . . . . 44		Appendix A. Receiver operation (informative) . . . . . . . . . . 44
	Appendix B. Example of FDT Instance (informative) . . . . . . . . 45		Appendix B. Example of FDT Instance (informative) . . . . . . . . 45
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 46		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 45
	1. Introduction		1. Introduction
	This document defines FLUTE version 2, a protocol for unidirectional		This document defines FLUTE version 2, a protocol for unidirectional
	delivery of files over the Internet. This specification is not		delivery of files over the Internet. This specification is not
	backwards compatible with the previous experimental version defined		backwards compatible with the previous experimental version defined
	in [RFC3926] (see Section 11 for details). The specification builds		in [RFC3926] (see Section 11 for details). The specification builds
	on Asynchronous Layered Coding (ALC), version 1 [RFC5775], the base		on Asynchronous Layered Coding (ALC), version 1 [RFC5775], the base
	protocol designed for massively scalable multicast distribution. ALC		protocol designed for massively scalable multicast distribution. ALC
	defines transport of arbitrary binary objects. For file delivery		defines transport of arbitrary binary objects. For file delivery
	skipping to change at page 34, line 39 ¶		skipping to change at page 34, line 39 ¶
	This specification contains six separate items for IANA		This specification contains six separate items for IANA
	Considerations:		Considerations:
	1. Registration of the FDT Instance XML Namespace.		1. Registration of the FDT Instance XML Namespace.
	2. Registration of the FDT Instance XML Schema.		2. Registration of the FDT Instance XML Schema.
	3. Registration of the application/fdt+xml Media-Type.		3. Registration of the application/fdt+xml Media-Type.
	4. Registration of the Content Encoding Algorithm.		4. Registration of the Content Encoding Algorithms.
	5. Registration of the EXT_FDT LCT Header Extension Type
	6. Registration of the EXT_CENC LCT Header Extension Type		5. Registration of two LCT Header Extension Types.
	8.1. Registration of the FDT Instance XML Namespace		8.1. Registration of the FDT Instance XML Namespace
	Document [RFC3688] defines an IANA maintained registry of XML		Please register the following new XML Namespace in the IETF XML
	documents used within IETF protocols. The following is the		Registry [RFC3688].
	registration request for the FDT Instance XML Namespace.		http://www.iana.org/assignments/xml-registry/ns.html
	URI: urn:ietf:params:xml:ns:fdt		URI: urn:ietf:params:xml:ns:fdt
	Registrant Contact: Toni Paila (toni.paila (at) nokia.com)		Registrant Contact: Toni Paila (toni.paila (at) nokia.com)
	XML: N/A		XML: N/A
	8.2. Registration of the FDT Instance XML Schema		8.2. Registration of the FDT Instance XML Schema
	Document [RFC3688] defines an IANA maintained registry of XML		Please register the following new XML Schema in the IETF XML Registry
	documents used within IETF protocols. The following is the		[RFC3688]. http://www.iana.org/assignments/xml-registry/schema.html
	registration request for the FDT Instance XML Schema.
	URI: urn:ietf:params:xml:schema:fdt		URI: urn:ietf:params:xml:schema:fdt
	Registrant Contact: Toni Paila (toni.paila (at) nokia.com)		Registrant Contact: Toni Paila (toni.paila (at) nokia.com)
	XML: The XML Schema specified in Section 3.4.2		XML: The XML Schema specified in Section 3.4.2
	8.3. Registration of the application/fdt+xml Media-Type		8.3. Registration of the application/fdt+xml Media-Type
	IANA is asked to register a new namespace in the IETF XML Registry		Please register a new Application XML Media Type in the Media Types
	(http://www.iana.org/assignments/xml-registry/ns.html) [RFC3688],		registry, according to [RFC3023].
	using the following registration template:		http://www.iana.org/assignments/media-types/application/
	Type name: application		Type name: application
	Subtype name: fdt+xml		Subtype name: fdt+xml
	Required parameters: none		Required parameters: none
	Optional parameters: charset="utf-8"		Optional parameters: charset="utf-8"
	Encoding considerations: binary (the FLUTE file delivery protocol		Encoding considerations: binary (the FLUTE file delivery protocol
	skipping to change at page 35, line 51 ¶		skipping to change at page 35, line 47 ¶
	Restrictions on usage: none		Restrictions on usage: none
	Security considerations: fdt+xml data is passive, and does not		Security considerations: fdt+xml data is passive, and does not
	generally represent a unique or new security threat. However, there		generally represent a unique or new security threat. However, there
	is some risk in sharing any kind of data, in that unintentional		is some risk in sharing any kind of data, in that unintentional
	information may be exposed, and that risk applies to fdt+xml data as		information may be exposed, and that risk applies to fdt+xml data as
	well.		well.
	Interoperability considerations: None		Interoperability considerations: None
	Published specification: The present document including section		Published specification: [[RFCxxxx]], especially noting section
	3.4.2. The specified FDT Instance functions as an actual media		3.4.2. The specified FDT Instance functions as an actual media
	format of use to the general Internet community and thus media type		format of use to the general Internet community and thus media type
	registration under the Standards Tree is appropriate to maximize		registration under the Standards Tree is appropriate to maximize
	interoperability.		interoperability.
	Applications which use this media type: file and object delivery		Applications which use this media type: file and object delivery
	applications and protocols (e.g., FLUTE).		applications and protocols (e.g., FLUTE).
	Additional information:		Additional information:
	skipping to change at page 36, line 25 ¶		skipping to change at page 36, line 22 ¶
	FDT Instance as a file);		FDT Instance as a file);
	Macintosh File Type Code(s): none		Macintosh File Type Code(s): none
	Person and email address to contact for further information: Toni		Person and email address to contact for further information: Toni
	Paila (toni.paila@nokia.com)		Paila (toni.paila@nokia.com)
	Intended usage: Common		Intended usage: Common
	Author/Change controller: IETF		Author/Change controller: IETF
	8.4. Registration of the Content Encoding Algorithm		8.4. Creation of the FLUTE Content Encoding Algorithms registry
	Values of Content Encoding Algorithms are subject to IANA
	registration. The value of Content Encoding Algorithm is a numeric
	non-negative index. In this document, the range of values for
	Content Encoding Algorithms is 0 to 255. This specification already
	assigns the values 0, 1, 2 and 3 as described in section 3.4.3.
	8.4.1. Explicit IANA Assignment Guidelines
	This document defines a name-space called "Content Encoding		Please create a new registry, "FLUTE Content Encoding Algorithms",
	Algorithms".		with a reference to [[RFCxxxx]] Section 3.4.3. The registry entries
			will consist of a numeric value from 0 to 255, inclusive, and may be
			registered using the Specification Required policy [RFC5226].
	IANA has established and manages the new registry for the "FLUTE		The initial contents of the registry are as follows, with unspecified
	Content Encoding Algorithm" name-space. The values that can be		values available for new registrations:
	assigned within this name-space are numeric indexes in the range [0,
	255], boundaries included. Assignment requests are granted on a
	"Specification Required" basis as defined in [RFC5226]. Note that
	the values 0, 1, 2 and 3 of this registry are already assigned by
	this document as described in section 3.4.3.
	8.5. Registration of the EXT_FDT LCT Header Extension Type		+-------+----------------+-------------+
			| Value | Algorithm name | Reference |
			+-------+----------------+-------------+
			| 0 | null | [[RFCxxxx]] |
			| 1 | ZLIB | [RFC1950] |
			| 2 | DEFLATE | [RFC1951] |
			| 3 | GZIP | [RFC1952] |
			+-------+----------------+-------------+
	This document registers value 192 for the EXT_FDT LCT Header		8.5. Registration of LCT Header Extension Types
	Extension defined in Section 3.4.1.
	8.6. Registration of the EXT_CENC LCT Header Extension Type		Please register two new entries in the Layered Coding Transport (LCT)
			Header Extension Types registry [RFC5651], as follows:
	This document registers value 193 for the EXT_CENC LCT Header		+--------+----------+---------------------------+
	Extension defined in Section 3.4.3.		| Number | Name | Reference |
			+--------+----------+---------------------------+
			| 192 | EXT_FDT | [[RFCxxxx]] Section 3.4.1 |
			| 193 | EXT_CENC | [[RFCxxxx]] Section 3.4.3 |
			+--------+----------+---------------------------+
	9. Acknowledgments		9. Acknowledgments
	The following persons have contributed to this specification: Brian		The following persons have contributed to this specification: Brian
	Adamson, Mark Handley, Esa Jalonen, Roger Kermode, Juha-Pekka Luoma,		Adamson, Mark Handley, Esa Jalonen, Roger Kermode, Juha-Pekka Luoma,
	Topi Pohjolainen, Lorenzo Vicisano, Mark Watson, David Harrington,		Topi Pohjolainen, Lorenzo Vicisano, Mark Watson, David Harrington,
	Ben Campbell, Stephen Farrell, Robert Sparks, Ronald Bonica, Francis		Ben Campbell, Stephen Farrell, Robert Sparks, Ronald Bonica, Francis
	Dupont, Peter Saint-Andre and Don Gillies. The authors would like to		Dupont, Peter Saint-Andre, Don Gillies and Barry Leiba. The authors
	thank all the contributors for their valuable work in reviewing and		would like to thank all the contributors for their valuable work in
	providing feedback regarding this specification.		reviewing and providing feedback regarding this specification.
	10. Contributors		10. Contributors
	Jani Peltotalo		Jani Peltotalo
	Tampere University of Technology		Tampere University of Technology
	P.O. Box 553 (Korkeakoulunkatu 1)		P.O. Box 553 (Korkeakoulunkatu 1)
	Tampere FIN-33101		Tampere FIN-33101
	Finland		Finland
	Email: jani.peltotalo (at) tut.fi		Email: jani.peltotalo (at) tut.fi
End of changes. 23 change blocks.
	54 lines changed or deleted		50 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/