Please submit any RMT Working Group agenda items by Monday, 12 March 2012. The RMT Meeting is scheduled for Monday, 26 March 2012 at 3:10 PM. best regards, Brian Adamson adamson <at> itd.nrl.navy.mil
Hi Brian, We would like to have a few minutes to discus 'Universal Object Delivery using RaptorQ' <draft-luby-uod-raptorq-00> (which is currently expired). 5-10 minutes should be sufficient. I won't be there, but Kevin Fall will be there and make the presentation if this is acceptable. Thanks, Mike On 3/7/12 7:06 AM, "Brian Adamson" <Brian.Adamson <at> nrl.navy.mil> wrote: >Please submit any RMT Working Group agenda items by Monday, 12 March 2012. > >The RMT Meeting is scheduled for Monday, 26 March 2012 at 3:10 PM. > >best regards, > >Brian Adamson >adamson <at> itd.nrl.navy.mil > > > > >
Hello Brian, I'd like to discuss our two Generalized Object Encoding (GOE) I-Ds: - draft-roca-rmt-goe-fec-01 (new version available) - draft-roca-rmt-goe-ldpc-00 (submitted in Oct but never discussed) 10mn are sufficient (for both), the proposal is relatively simple. Cheers, Vincent > Please submit any RMT Working Group agenda items by Monday, 12 March 2012. > > The RMT Meeting is scheduled for Monday, 26 March 2012 at 3:10 PM. > > best regards, > > Brian Adamson > adamson <at> itd.nrl.navy.mil > > > > > _______________________________________________ > Rmt mailing list > Rmt <at> ietf.org > https://www.ietf.org/mailman/listinfo/rmt
Hi RMTers, New version for FLUTE-SDP updated according to WGLC comments is now available. Updates includes: 1. Term "FEC OTI" is changed to "FEC scheme" where appropriate to avoid misunderstandings between the current specification's use for OTI capability requirements description and the wider application of OTI for receiver FEC configuration for LCT/FLUTE objects (the latter being beyond the scope of the present specification). 2. More specific reference to Section 7.3.1 in draft-ietf-rmt-flute-revised-13 for attacks against session descriptions is added to Section 5. 3. The note on out of scope congestion control is moved to a more sensible place. 4. Small change in Section 3.2.1.: "It is useful for describing..." --> "It is used for describing..." Some clarifications for "no action" comments: 1. t-line is mandatory in SDP description and "t= 0 0" can be used for unbounded sessions. 2. The "counted" number for FLUTE/ALC/LCT channels should always be right and the "a=flute-ch" should never be different from that. 1st bullet point of 3.6.1 explains what to do at the client end if a problem comes up. Cheers, Jani & Rod > 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.(Continue reading)
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-14.txt
Pages : 45
Date : 2012-03-12
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.
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rmt-flute-revised-14.txt
Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/
This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-rmt-flute-revised-14.txt
Hi everybody, I haven't yet finished, but I'm making progress... Here is an intermediate version that addresses some of the IESG comments. I'll continue working on it. Cheers, Vincent > 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-14.txt > Pages : 45 > Date : 2012-03-12 > > 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. > >(Continue reading)
The FLUTE SDP " draft-ietf-rmt-flute-sdp-02" has been revised based on comments received during the last WGLC and is ready for RMT Working Group Last Call. Please provide any final comments on this document by the RMT WG meeting on 26 March 2012. Unless there are objections, this will be submitted for publication after the IETF best regards, Brian Adamson brian.adamson <at> nrl.navy.mil
_______________________________________________ Rmt mailing list Rmt <at> ietf.org https://www.ietf.org/mailman/listinfo/rmt
RSS Feed1 | |
|---|---|
1 | |
3 | |
1 | |
4 | |
4 | |
5 | |
1 | |
5 | |
2 | |
2 | |
8 | |
2 | |
1 | |
1 | |
4 | |
5 | |
2 | |
2 | |
5 | |
5 | |
6 | |
5 | |
16 | |
15 | |
17 | |
6 | |
10 | |
4 | |
11 | |
19 | |
1 | |
6 | |
4 | |
18 | |
10 | |
12 | |
14 | |
21 | |
7 | |
11 | |
10 | |
8 | |
24 | |
16 | |
5 | |
1 | |
9 | |
5 | |
9 | |
6 | |
20 | |
1 | |
2 | |
11 | |
9 | |
9 | |
5 | |
6 | |
10 | |
11 | |
10 | |
1 | |
10 | |
9 | |
5 | |
14 | |
18 | |
7 | |
8 | |
11 | |
13 | |
5 | |
2 | |
6 | |
30 | |
8 | |
9 | |
29 | |
24 | |
16 | |
20 | |
55 | |
30 | |
64 | |
18 | |
31 | |
14 | |
1 | |
1 | |
8 | |
4 | |
1 | |
2 | |
9 | |
9 | |
16 | |
6 | |
11 | |
6 | |
3 | |
2 | |
2 | |
16 | |
2 | |
3 | |
26 | |
30 | |
2 | |
6 | |
7 | |
6 | |
2 | |
19 | |
13 | |
1 | |
9 | |
4 | |
7 | |
6 | |
12 | |
1 | |
2 | |
3 |
