RFC Errata System | 23 Jan 07:55 2014

[Technical Errata Reported] RFC6726 (3870)

The following errata report has been submitted for RFC6726,
"FLUTE - File Delivery over Unidirectional Transport".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6726&eid=3870

--------------------------------------
Type: Technical
Reported by: Thomas Stockhammer <stockhammer <at> nomor.de>

Section: 11.1

Original Text
-------------
Incremented the FLUTE protocol version from 1 to 2, due to concerns
   about backwards compatibility.  For instance, the LCT header changed
   between RFC 3451 and [RFC5651].  In RFC 3451, the T and R fields of
   the LCT header indicate the presence of Sender Current Time and
   Expected Residual Time, respectively.  In [RFC5651], these fields
   MUST be set to zero and MUST be ignored by receivers (instead, the
   EXT_TIME Header Extensions can convey this information if needed).
   Thus, [RFC5651] is not backwards compatible with RFC 3451, even
   though both use LCT version 1.  FLUTE version 1 as specified in
   [RFC3926] MUST use RFC 3451.  FLUTE version 2 as specified in this
   document MUST use [RFC5651].  Therefore, an implementation that
   relies on [RFC3926] and RFC 3451 will not be backwards compatible
   with FLUTE as specified in this document.

Corrected Text
(Continue reading)

RFC Errata System | 16 Dec 16:38 2013

[Technical Errata Reported] RFC5651 (3843)

The following errata report has been submitted for RFC5651,
"Layered Coding Transport (LCT) Building Block".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=5651&eid=3843

--------------------------------------
Type: Technical
Reported by: Eric Turcotte <eric.turcotte <at> ericsson.com>

Section: 5.2.1

Original Text
-------------
There are two formats for Header Extension fields, as depicted in
Figure 2. The first format is used for variable-length extensions,
with Header Extension Type (HET) values between 0 and 127. The
second format is used for fixed-length (one 32-bit word) extensions,
using HET values from 127 to 255.

Corrected Text
--------------
There are two formats for Header Extension fields, as depicted in
Figure 2. The first format is used for variable-length extensions,
with Header Extension Type (HET) values between 0 and 127. The
second format is used for fixed-length (one 32-bit word) extensions,
using HET values from 128 to 255.

Notes
(Continue reading)

IESG Secretary | 6 Sep 21:13 2013
Picon

WG Action: Conclusion of Reliable Multicast Transport (rmt)

The Reliable Multicast Transport (rmt) working group in the Transport 
Area has concluded after having completed most of its chartered work. 
The IESG contact persons are Spencer Dawkins and Martin Stiemerling.

There are two milestones that have not been completed:

- Submit FLUTE SDP document for publication
- Submit RMT Security documents for publication

The RMT mailing list (rmt <at> ietf.org) will remain open in order to
enable continued discussion among people that are implementing or
using protocols developed by the RMT working group.

Thanks to the RMT participants and the chairs!

rfc-editor | 9 Jul 18:52 2013

RFC 6968 on FCAST: Object Delivery for the Asynchronous Layered Coding (ALC) and NACK-Oriented Reliable Multicast (NORM) Protocols

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6968

        Title:      FCAST: Object Delivery for the 
                    Asynchronous Layered Coding (ALC) and
                    NACK-Oriented Reliable Multicast (NORM)
                    Protocols 
        Author:     V. Roca, B. Adamson
        Status:     Experimental
        Stream:     IETF
        Date:       July 2013
        Mailbox:    vincent.roca <at> inria.fr, 
                    adamson <at> itd.nrl.navy.mil
        Pages:      40
        Characters: 96399
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rmt-fcast-08.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6968.txt

This document introduces the FCAST reliable object (e.g., file)
delivery application.  It is designed to operate either on top of the
underlying Asynchronous Layered Coding (ALC) / Layered Coding
Transport (LCT) reliable multicast transport protocol or the
NACK-Oriented Reliable Multicast (NORM) transport protocol.

This document is a product of the Reliable Multicast Transport Working Group of the IETF.
(Continue reading)

The IESG | 6 Jun 16:24 2013
Picon

Last Call: <draft-ietf-rmt-sec-discussion-08.txt> (Security and Reliable Multicast Transport Protocols: Discussions and Guidelines) to Informational RFC


The IESG has received a request from the Reliable Multicast Transport WG
(rmt) to consider the following document:
- 'Security and Reliable Multicast Transport Protocols: Discussions and
   Guidelines'
  <draft-ietf-rmt-sec-discussion-08.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf <at> ietf.org mailing lists by 2013-06-20. Exceptionally, comments may be
sent to iesg <at> ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract

   This document describes general security considerations for Reliable
   Multicast Transport (RMT) building blocks and protocols.  An emphasis
   is placed on risks that might be resolved in the scope of transport
   protocol design.  However, relevant security issues related to IP
   Multicast control-plane and other concerns not strictly within the
   scope of reliable transport protocol design are also discussed.  The
   document also begins an exploration of approaches that could be
   embraced to mitigate these risks.  The purpose of this document is to
   provide a consolidated security discussion and provide a basis for
   further discussions and potential resolution of any significant
   security issues that may exist in the current set of RMT standards.

The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-rmt-sec-discussion/

(Continue reading)

internet-drafts | 17 May 16:31 2013
Picon

I-D Action: draft-ietf-rmt-sec-discussion-08.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Reliable Multicast Transport Working Group of the IETF.

	Title           : Security and Reliable Multicast Transport Protocols: Discussions and Guidelines
	Author(s)       : Brian Adamson
                          Vincent Roca
                          Hitoshi Asaeda
	Filename        : draft-ietf-rmt-sec-discussion-08.txt
	Pages           : 26
	Date            : 2013-05-17

Abstract:
   This document describes general security considerations for Reliable
   Multicast Transport (RMT) building blocks and protocols.  An emphasis
   is placed on risks that might be resolved in the scope of transport
   protocol design.  However, relevant security issues related to IP
   Multicast control-plane and other concerns not strictly within the
   scope of reliable transport protocol design are also discussed.  The
   document also begins an exploration of approaches that could be
   embraced to mitigate these risks.  The purpose of this document is to
   provide a consolidated security discussion and provide a basis for
   further discussions and potential resolution of any significant
   security issues that may exist in the current set of RMT standards.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-rmt-sec-discussion

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-rmt-sec-discussion-08
(Continue reading)

Martin Stiemerling | 30 Apr 13:58 2013
Picon

Change in RMT chair position

Dear all,

Here is an update about the change in the RMT chair position for your 
information.

Lorenzo Vicisano stepped down as co-chair of the RMT WG on my request.
The RMT is approaching its end of lifetime and one chair seems to be 
sufficient to handle the WG.

Let me thank Lorenzo Vicisano for his long-time contribution to the RMT WG!

   Martin

--

-- 
IETF Transport Area Director

martin.stiemerling <at> neclab.eu

NEC Laboratories Europe
NEC Europe Limited
Registered Office:
Athene, Odyssey Business Park, West End  Road, London, HA4 6QE, GB
Registered in England 2832014
The IESG | 29 Apr 21:04 2013
Picon

Document Action: 'FCAST: Object Delivery for the ALC and NORM Protocols' to Experimental RFC (draft-ietf-rmt-fcast-08.txt)

The IESG has approved the following document:
- 'FCAST: Object Delivery for the ALC and NORM Protocols'
  (draft-ietf-rmt-fcast-08.txt) as Experimental RFC

This document is the product of the Reliable Multicast Transport Working
Group.

The IESG contact person is Martin Stiemerling.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-rmt-fcast/

    Technical Summary

This document specifies a set of data formats and instructions on how to use ALC
(RFC 5775) and NORM (RFC 5740) to implement a file-casting service. In particular
this document specifies an in-band method to advertise the content and duration
of a file-casting session. It also specifies exactly how instantiate an ALC or
NORM transport session for use within this context.

   Working Group Summary

FCAST represents the consensus of the RMT WG participants.  FCAST was initially
proposed at the beginning of the RMT effort (circa 2001) and then superseded
by a more comprehensive approach (FLUTE, draft-ietf-rmt-flute-revised-11). Due
to late reported IPR claims on FLUTE, FCAST was re-added to the WG scope to
offer an alternative to FLUTE.

    Document Quality

(Continue reading)

internet-drafts | 26 Mar 11:06 2013
Picon

I-D Action: draft-ietf-rmt-fcast-08.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Reliable Multicast Transport Working Group of the IETF.

	Title           : FCAST: Object Delivery for the ALC and NORM Protocols
	Author(s)       : Vincent Roca
                          Brian Adamson
	Filename        : draft-ietf-rmt-fcast-08.txt
	Pages           : 38
	Date            : 2013-03-26

Abstract:
   This document introduces the FCAST reliable object (e.g., file)
   delivery application.  It is designed to operate either on top of the
   underlying Asynchronous Layer Coding (ALC)/Layered Coding Transport
   (LCT) or the NACK-Oriented Reliable Multicast (NORM) reliable
   multicast transport protocols.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-rmt-fcast

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-rmt-fcast-08

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-rmt-fcast-08

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/
(Continue reading)

IETF Secretariat | 15 Feb 17:50 2013
Picon

IPR Disclosure: QUALCOMM Incorporated's Statement about IPR related to RFC 6330


Dear Lorenz Minder, Amin Shokrollahi, Mark Watson, Michael Luby, Thomas Stockhammer:

 An IPR disclosure that pertains to your RFC entitled "RaptorQ Forward Error
Correction Scheme for Object Delivery" (RFC6330) was submitted to the IETF
Secretariat on 2013-02-06 and has been posted on the "IETF Page of Intellectual
Property Rights Disclosures" (https://datatracker.ietf.org/ipr/1958/). The title
of the IPR disclosure is "QUALCOMM Incorporated's Statement about IPR related to
RFC 6330."");

The IETF Secretariat
IETF Secretariat | 15 Feb 17:49 2013
Picon

IPR Disclosure: QUALCOMM Incorporated's Statement about IPR related to RFC 5053 (5)


Dear Amin Shokrollahi, Thomas Stockhammer, Michael Luby, Mark Watson:

 An IPR disclosure that pertains to your RFC entitled "Raptor Forward Error
Correction Scheme for Object Delivery" (RFC5053) was submitted to the IETF
Secretariat on 2013-02-06 and has been posted on the "IETF Page of Intellectual
Property Rights Disclosures" (https://datatracker.ietf.org/ipr/1957/). The title
of the IPR disclosure is "QUALCOMM Incorporated's Statement about IPR related to
RFC 5053 (5)."");

The IETF Secretariat

Gmane