<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.ietf.rmt">
    <title>gmane.ietf.rmt</title>
    <link>http://blog.gmane.org/gmane.ietf.rmt</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.rmt/1232"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.rmt/1230"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.rmt/1229"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.rmt/1228"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.rmt/1222"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.rmt/1220"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.rmt/1219"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.rmt/1216"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.rmt/1212"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.rmt/1211"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.rmt/1208"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.rmt/1206"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.rmt/1205"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.rmt/1204"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.rmt/1203"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.rmt/1203"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.rmt/1202"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.rmt/1201"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.rmt/1200"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.rmt/1198"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.rmt/1232">
    <title>I-D Action: draft-ietf-rmt-sec-discussion-08.txt</title>
    <link>http://comments.gmane.org/gmane.ietf.rmt/1232</link>
    <description>&lt;pre&gt;
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 th&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2013-05-17T14:31:27</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.rmt/1230">
    <title>Change in RMT chair position</title>
    <link>http://comments.gmane.org/gmane.ietf.rmt/1230</link>
    <description>&lt;pre&gt;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

&lt;/pre&gt;</description>
    <dc:creator>Martin Stiemerling</dc:creator>
    <dc:date>2013-04-30T11:58:43</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.rmt/1229">
    <title>Document Action: 'FCAST: Object Delivery for the ALC andNORMProtocols' to Experimental RFC (draft-ietf-rmt-fcast-08.txt)</title>
    <link>http://comments.gmane.org/gmane.ietf.rmt/1229</link>
    <description>&lt;pre&gt;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-rev&lt;/pre&gt;</description>
    <dc:creator>The IESG</dc:creator>
    <dc:date>2013-04-29T19:04:52</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.rmt/1228">
    <title>I-D Action: draft-ietf-rmt-fcast-08.txt</title>
    <link>http://comments.gmane.org/gmane.ietf.rmt/1228</link>
    <description>&lt;pre&gt;
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?u&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2013-03-26T10:06:07</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.rmt/1222">
    <title>Last Call: &lt;draft-ietf-rmt-flute-sdp-03.txt&gt; (SDP DescriptorsforFLUTE) to Proposed Standard</title>
    <link>http://comments.gmane.org/gmane.ietf.rmt/1222</link>
    <description>&lt;pre&gt;
The IESG has received a request from the Reliable Multicast Transport WG
(rmt) to consider the following document:
- 'SDP Descriptors for FLUTE'
  &amp;lt;draft-ietf-rmt-flute-sdp-03.txt&amp;gt; as Proposed Standard

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&amp;lt; at &amp;gt;ietf.org mailing lists by 2013-01-22. Exceptionally, comments may be
sent to iesg&amp;lt; at &amp;gt;ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   This document specifies the use of SDP to describe the parameters
   required to begin, join, receive data from, and/or end FLUTE
   sessions.  It also provides a Composite Session SDP media grouping
   semantic for grouping media streams into protocol-specific sessions,
   such as multiple-channel FLUTE sessions.




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

IESG discussion can be tracked via
http://datatracker.ietf&lt;/pre&gt;</description>
    <dc:creator>The IESG</dc:creator>
    <dc:date>2013-01-08T14:59:38</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.rmt/1220">
    <title>WG Last Call: draft-ietf-rmt-sec-discussion-07</title>
    <link>http://comments.gmane.org/gmane.ietf.rmt/1220</link>
    <description>&lt;pre&gt;The RMT Security Discussion draft has been updated to reflect comment received from Gorry Fairhurst during the WGLC issued for this document some time ago.

A new WGLC is being issued.  Because of the upcoming holidays, the deadline for this WGLC will be 11 January 2013.

For your convenience, the document is available at:  http://www.ietf.org/id/draft-ietf-rmtsec-discussion-07.txt

best regards,

Brian Adamson
brian.adamson&amp;lt; at &amp;gt;nrl.navy.mil







_______________________________________________
Rmt mailing list
Rmt&amp;lt; at &amp;gt;ietf.org
https://www.ietf.org/mailman/listinfo/rmt
&lt;/pre&gt;</description>
    <dc:creator>brian.adamson&lt; at &gt;nrl.navy.mil</dc:creator>
    <dc:date>2012-12-14T17:29:17</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.rmt/1219">
    <title>WG Last Call: draft-ietf-rmt-flute-sdp-03</title>
    <link>http://comments.gmane.org/gmane.ietf.rmt/1219</link>
    <description>&lt;pre&gt;The FLUTE SDP document is approaching publication and a the AD has refreshed an old IPR declaration that had been submitted against the older incarnation of this document.  Given, this update a short WGLC is being issued to provide an opportunity for working group members to review this and provide any final comments.

Please provide any comments on the document to the mailing list by 21 December 2012.

For your convenience, the document is available at:  http://www.ietf.org/id/draft-ietf-rmt-flute-sdp-03.txt

best regards,

Brian Adamson
brian.adamson&amp;lt; at &amp;gt;nrl.navy.mil







_______________________________________________
Rmt mailing list
Rmt&amp;lt; at &amp;gt;ietf.org
https://www.ietf.org/mailman/listinfo/rmt
&lt;/pre&gt;</description>
    <dc:creator>brian.adamson&lt; at &gt;nrl.navy.mil</dc:creator>
    <dc:date>2012-12-14T15:50:39</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.rmt/1216">
    <title>WG Last Call: draft-ietf-rmt-fcast-02</title>
    <link>http://comments.gmane.org/gmane.ietf.rmt/1216</link>
    <description>&lt;pre&gt;The FCAST draft has been recently updated based on Area Directory comments.  Since the prior WGLC some time ago, there have been a few different updates resulting in a number of changes so a new WGLC last call is in order to provide an opportunity for a final review.

Please provide any comments on the document to the mailing list by 21 December 2012.

For your convenience, the document is available at:  http://www.ietf.org/id/draft-ietf-rmt-fcast-07.txt

best regards,

Brian Adamson
brian.adamson&amp;lt; at &amp;gt;nrl.navy.mil







_______________________________________________
Rmt mailing list
Rmt&amp;lt; at &amp;gt;ietf.org
https://www.ietf.org/mailman/listinfo/rmt
&lt;/pre&gt;</description>
    <dc:creator>brian.adamson&lt; at &gt;nrl.navy.mil</dc:creator>
    <dc:date>2012-12-12T14:16:11</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.rmt/1212">
    <title>I-D Action: draft-ietf-rmt-sec-discussion-07.txt</title>
    <link>http://comments.gmane.org/gmane.ietf.rmt/1212</link>
    <description>&lt;pre&gt;
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-07.txt
Pages           : 28
Date            : 2012-11-30

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 th&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2012-11-30T17:41:55</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.rmt/1211">
    <title>I-D Action: draft-ietf-rmt-fcast-07.txt</title>
    <link>http://comments.gmane.org/gmane.ietf.rmt/1211</link>
    <description>&lt;pre&gt;
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: Scalable Object Delivery for the ALC and NORM Protocols
Author(s)       : Vincent Roca
                          Brian Adamson
Filename        : draft-ietf-rmt-fcast-07.txt
Pages           : 36
Date            : 2012-11-30

Abstract:
   This document introduces the FCAST object (e.g., file) delivery
   application on top of the ALC and NORM reliable multicast protocols.
   FCAST is a highly scalable application that provides a reliable
   object delivery service.


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-07

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


Internet-Drafts are also available by&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2012-11-30T15:45:39</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.rmt/1208">
    <title>I-D Action: draft-ietf-rmt-flute-sdp-03.txt</title>
    <link>http://comments.gmane.org/gmane.ietf.rmt/1208</link>
    <description>&lt;pre&gt;
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           : SDP Descriptors for FLUTE
Author(s)       : Rod Walsh
                          Jani Peltotalo
                          Sami Peltotalo
                          Igor D.D. Curcio
                          Harsh Mehta
Filename        : draft-ietf-rmt-flute-sdp-03.txt
Pages           : 35
Date            : 2012-09-12

Abstract:
   This document specifies the use of SDP to describe the parameters
   required to begin, join, receive data from, and/or end FLUTE
   sessions.  It also provides a Composite Session SDP media grouping
   semantic for grouping media streams into protocol-specific sessions,
   such as multiple-channel FLUTE sessions.


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

There's also a htmlized version available at:
http://tools.ietf.org/&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2012-09-12T09:04:39</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.rmt/1206">
    <title>IETF 84 RMT Draft Agenda submitted</title>
    <link>http://comments.gmane.org/gmane.ietf.rmt/1206</link>
    <description>&lt;pre&gt;I have submitted a draft agenda with the following items:

1) Working Group Status Summary - Brian Adamson

2) FCAST Status (short!) - Vincent Roca

3) Supercharged Codes - Eric Stouffer

4) Open Discussion on GOE, UOD, and RMT Next Steps


The posted agenda points to the relevant Internet Drafts.

There is room for additional agenda items if requested.

best regards,

Brian Adamson
brian.adamson&amp;lt; at &amp;gt;nrl.navy.mil



_______________________________________________
Rmt mailing list
Rmt&amp;lt; at &amp;gt;ietf.org
https://www.ietf.org/mailman/listinfo/rmt
&lt;/pre&gt;</description>
    <dc:creator>Brian Adamson</dc:creator>
    <dc:date>2012-07-20T21:07:32</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.rmt/1205">
    <title>IETF 84 RMT - Call for Agenda Items</title>
    <link>http://comments.gmane.org/gmane.ietf.rmt/1205</link>
    <description>&lt;pre&gt;
Please submit any RMT Working Group agenda items ASAP.  The first draft agenda is due to tomorrow and I overlooked requesting this on the list earlier.

The RMT WG is scheduled for Tuesday, 31 July 2012.

best regards,

Brian Adamson
brian.adamson&amp;lt; at &amp;gt;nrl.navy.mil



Brian Adamson
brian.adamson&amp;lt; at &amp;gt;nrl.navy.mil



_______________________________________________
Rmt mailing list
Rmt&amp;lt; at &amp;gt;ietf.org
https://www.ietf.org/mailman/listinfo/rmt
&lt;/pre&gt;</description>
    <dc:creator>Brian Adamson</dc:creator>
    <dc:date>2012-07-17T15:10:48</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.rmt/1204">
    <title>Protocol Action: 'FLUTE - File Delivery overUnidirectionalTransport' to Proposed Standard(draft-ietf-rmt-flute-revised-16.txt)</title>
    <link>http://comments.gmane.org/gmane.ietf.rmt/1204</link>
    <description>&lt;pre&gt;The IESG has approved the following document:
- 'FLUTE - File Delivery over Unidirectional Transport'
  (draft-ietf-rmt-flute-revised-16.txt) as Proposed Standard

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

The IESG contact persons are Martin Stiemerling and Wesley Eddy.

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




Technical Summary
 
   This document defines FLUTE, a protocol for the unidirectional
   delivery of files over the Internet, which is particularly suited to
   multicast networks.  The specification builds on Asynchronous Layered
   Coding, the base protocol designed for massively scalable multicast
   distribution.  This document obsoletes RFC3926.
 
Working Group Summary
 
This document represents a solid consensus of the RMT WG.
Flute version 1 was published as an Experimental protocol.
It has been widely implemented, including most of the changes in this document.
Many implementers compared notes and &lt;/pre&gt;</description>
    <dc:creator>The IESG</dc:creator>
    <dc:date>2012-07-12T22:52:13</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.rmt/1203">
    <title>[Editorial Errata Reported] RFC4654 (3274)</title>
    <link>http://comments.gmane.org/gmane.ietf.rmt/1203</link>
    <description>&lt;pre&gt;
The following errata report has been submitted for RFC4654,
"TCP-Friendly Multicast Congestion Control (TFMCC): Protocol Specification".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=4654&amp;amp;eid=3274

--------------------------------------
Type: Editorial
Reported by: Dongwook Kim &amp;lt;kdw&amp;lt; at &amp;gt;neowiz.com&amp;gt;

Section: 5.3

Original Text
-------------
If a loss interval, A, is determined to have started with packet
sequence number S_A and the next loss interval, B, started with
packet sequence number S_B, then the number of packets in loss
interval A is given by (S_B - S_A).


Corrected Text
--------------
If a loss event, A, is determined to have started with packet
sequence number S_A and the next loss event, B, started with
packet sequence number S_B, then the number of packets in the loss
interval between A and B is given by (S_B - S_A).


Notes
-----


Instructions:
-------------
This errata is currently posted as "Reported". If necessa&lt;/pre&gt;</description>
    <dc:creator>RFC Errata System</dc:creator>
    <dc:date>2012-07-03T06:29:37</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.rmt/1203">
    <title>[Editorial Errata Reported] RFC4654 (3274)</title>
    <link>http://comments.gmane.org/gmane.ietf.rmt/1203</link>
    <description>&lt;pre&gt;
The following errata report has been submitted for RFC4654,
"TCP-Friendly Multicast Congestion Control (TFMCC): Protocol Specification".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=4654&amp;amp;eid=3274

--------------------------------------
Type: Editorial
Reported by: Dongwook Kim &amp;lt;kdw&amp;lt; at &amp;gt;neowiz.com&amp;gt;

Section: 5.3

Original Text
-------------
If a loss interval, A, is determined to have started with packet
sequence number S_A and the next loss interval, B, started with
packet sequence number S_B, then the number of packets in loss
interval A is given by (S_B - S_A).


Corrected Text
--------------
If a loss event, A, is determined to have started with packet
sequence number S_A and the next loss event, B, started with
packet sequence number S_B, then the number of packets in the loss
interval between A and B is given by (S_B - S_A).


Notes
-----


Instructions:
-------------
This errata is currently posted as "Reported". If necessa&lt;/pre&gt;</description>
    <dc:creator>RFC Errata System</dc:creator>
    <dc:date>2012-07-03T06:29:37</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.rmt/1202">
    <title>I-D Action: draft-ietf-rmt-flute-revised-16.txt</title>
    <link>http://comments.gmane.org/gmane.ietf.rmt/1202</link>
    <description>&lt;pre&gt;
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           : FLUTE - File Delivery over Unidirectional Transport
Author(s)       : Toni Paila
                          Rod Walsh
                          Michael Luby
                          Vincent Roca
                          Rami Lehtonen
Filename        : draft-ietf-rmt-flute-revised-16.txt
Pages           : 46
Date            : 2012-06-27

Abstract:
   This document defines FLUTE, a protocol for the unidirectional
   delivery of files over the Internet, which is particularly suited to
   multicast networks.  The specification builds on Asynchronous Layered
   Coding, the base protocol designed for massively scalable multicast
   distribution.  This document obsoletes RFC3926.


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

There's also a htmlized vers&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2012-06-27T14:52:17</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.rmt/1201">
    <title>I-D Action: draft-ietf-rmt-flute-revised-15.txt</title>
    <link>http://comments.gmane.org/gmane.ietf.rmt/1201</link>
    <description>&lt;pre&gt;
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           : FLUTE - File Delivery over Unidirectional Transport
Author(s)       : Toni Paila
                          Rod Walsh
                          Michael Luby
                          Vincent Roca
                          Rami Lehtonen
Filename        : draft-ietf-rmt-flute-revised-15.txt
Pages           : 46
Date            : 2012-06-13

Abstract:
   This document defines FLUTE, a protocol for the unidirectional
   delivery of files over the Internet, which is particularly suited to
   multicast networks.  The specification builds on Asynchronous Layered
   Coding, the base protocol designed for massively scalable multicast
   distribution.  This document obsoletes RFC3926.


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

There's also a htmlized vers&lt;/pre&gt;</description>
    <dc:creator>internet-drafts&lt; at &gt;ietf.org</dc:creator>
    <dc:date>2012-06-13T10:23:50</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.rmt/1200">
    <title>RFC 6584 on Simple Authentication Schemes for theAsynchronous Layered Coding (ALC) and NACK-Oriented ReliableMulticast (NORM) Protocols</title>
    <link>http://comments.gmane.org/gmane.ietf.rmt/1200</link>
    <description>&lt;pre&gt;
A new Request for Comments is now available in online RFC libraries.

        
        RFC 6584

        Title:      Simple Authentication Schemes for the 
                    Asynchronous Layered Coding (ALC) and NACK-Oriented 
                    Reliable Multicast (NORM) Protocols 
        Author:     V. Roca
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2012
        Mailbox:    vincent.roca&amp;lt; at &amp;gt;inria.fr
        Pages:      30
        Characters: 67466
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rmt-simple-auth-for-alc-norm-06.txt

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

This document introduces four schemes that provide per-packet
authentication, integrity, and anti-replay services in the context of
the Asynchronous Layered Coding (ALC) and NACK-Oriented Reliable
Multicast (NORM) protocols.  The first scheme is based on RSA Digital
Signatures.  The second scheme relies on the Elliptic Curve Digital
Signature Algori&lt;/pre&gt;</description>
    <dc:creator>rfc-editor&lt; at &gt;rfc-editor.org</dc:creator>
    <dc:date>2012-04-13T18:01:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.rmt/1198">
    <title>IPR Disclosure: QUALCOMM Incorporated's Statement about IPRrelatedto RFC 5170 (3)</title>
    <link>http://comments.gmane.org/gmane.ietf.rmt/1198</link>
    <description>&lt;pre&gt;
Dear Christoph Neumann, Vincent Roca, David Furodet:

 An IPR disclosure that pertains to your RFC entitled "Low Density Parity Check
(LDPC) Staircase and Triangle Forward Error Correction (FEC) Schemes" (RFC5170)
was submitted to the IETF Secretariat on 2012-04-05 and has been posted on the "IETF Page of Intellectual Property Rights Disclosures"
(https://datatracker.ietf.org/ipr/1743/). The title of the IPR disclosure is
"QUALCOMM Incorporated's Statement about IPR related to RFC 5170 (3)."");

The IETF Secretariat
&lt;/pre&gt;</description>
    <dc:creator>IETF Secretariat</dc:creator>
    <dc:date>2012-04-13T14:53:04</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.rmt/1197">
    <title>Initial IETF 83 RMT Agenda Submitted</title>
    <link>http://comments.gmane.org/gmane.ietf.rmt/1197</link>
    <description>&lt;pre&gt;I have submitted and initial RMT agenda based on feedback received from the call for agenda items.  Please review this and provide any suggestions or comments to the list.

best regards,


Brian Adamson
brian.adamson&amp;lt; at &amp;gt;nrl.navy.mil





_______________________________________________
Rmt mailing list
Rmt&amp;lt; at &amp;gt;ietf.org
https://www.ietf.org/mailman/listinfo/rmt
&lt;/pre&gt;</description>
    <dc:creator>Brian Adamson</dc:creator>
    <dc:date>2012-03-14T15:31:48</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.ietf.rmt">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.ietf.rmt</link>
  </textinput>
</rdf:RDF>
