RMT WG Issues - FEC Basic Schemes, ALC/LCT, FLUTE

All:

Recently a few RMT Working Group issues have arisen:

Most notably, we received this note from the editors:

>> We have <draft-mehta-rmt-flute-sdp-05.txt> in our queue for  
>> publication, and it has the following normative references that are  
>> not yet in our queue:
>> REF1 draft-ietf-rmt-flute-revised
>> ID Tracker State: dead
>> REF2 draft-ietf-rmt-pi-alc-revised
>> ID Tracker State: dead
>> REF3 draft-ietf-rmt-bb-lct-revised
>> ID Tracker State: dead
>> REF4 draft-ietf-rmt-bb-fec-basic-schemes-revised
>> ID Tracker State: AD Eval -- Revised ID needed
>> Will REF1, REF2, and REF3 be revised and resubmitted?  Or, should  
>> these references be updated?  Should <draft-mehta-rmt-flute- 
>> sdp-05.txt> be removed from the RFC Editor queue?
>> Please let us know how to proceed.
>> Thank you.

So, the FLUTE, ALC, LCT, and FEC Basic Schemes documents need  
attention!  I haven't heard anything recently from the authors here,  
and we need to establish some definitive status and plan on these  
issues.  I don't think this should wait until Dublin.

I think we have an approach to address the security considerations  
issues that have been raised so that these documents can be completed  

RMT WG Issues - FEC Basic Schemes, ALC/LCT, FLUTE

All:

Recently a few RMT Working Group issues have arisen:

Most notably, we received this note from the editors:

>> We have <draft-mehta-rmt-flute-sdp-05.txt> in our queue for  
>> publication, and it has the following normative references that are  
>> not yet in our queue:
>> REF1 draft-ietf-rmt-flute-revised
>> ID Tracker State: dead
>> REF2 draft-ietf-rmt-pi-alc-revised
>> ID Tracker State: dead
>> REF3 draft-ietf-rmt-bb-lct-revised
>> ID Tracker State: dead
>> REF4 draft-ietf-rmt-bb-fec-basic-schemes-revised
>> ID Tracker State: AD Eval -- Revised ID needed
>> Will REF1, REF2, and REF3 be revised and resubmitted?  Or, should  
>> these references be updated?  Should <draft-mehta-rmt-flute- 
>> sdp-05.txt> be removed from the RFC Editor queue?
>> Please let us know how to proceed.
>> Thank you.

So, the FLUTE, ALC, LCT, and FEC Basic Schemes documents need  
attention!  I haven't heard anything recently from the authors here,  
and we need to establish some definitive status and plan on these  
issues.  I don't think this should wait until Dublin.

I think we have an approach to address the security considerations  
issues that have been raised so that these documents can be completed  

IETF 72 RMT WG Meeting Agenda Requests

Please submit any requests for RMT WG meeting agenda slots as soon as  
possible to the RMT WG Chairs:

Lorenzo Vicisana - lorenzo <at> vicisano.net
Brian Adamson - adamson <at> itd.nrl.navy.mil

We need to submit a draft agenda next week.

best regards,

I-D Action:draft-ietf-rmt-bb-lct-revised-07.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           : Layered Coding Transport (LCT) Building Block
	Author(s)       : M. Luby, et al.
	Filename        : draft-ietf-rmt-bb-lct-revised-07.txt
	Pages           : 41
	Date            : 2008-07-12

Layered Coding Transport (LCT) provides transport level support for
reliable content delivery and stream delivery protocols.  LCT is
specifically designed to support protocols using IP multicast, but
also provides support to protocols that use unicast.  LCT is
compatible with congestion control that provides multiple rate
delivery to receivers and is also compatible with coding techniques
that provide reliable delivery of content.  This document obsoletes
RFC3451

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rmt-bb-lct-revised-07.txt

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

Re: AD comments on draft-ietf-rmt-bb-fec-basic-schemes-revised-04

I propose to address item 3 by changing the SHOULDs to MUSTs. The other
comments all seem fine to me and I will submit an update shortly.

...Mark

On 4/18/08 2:52 AM, "Magnus Westerlund" <magnus.westerlund <at> ericsson.com>
wrote:

> Hi,
> 
> I have made my AD review of the document and have the following comments.
> 
> 1. Obsolete information in header, abstract and introduction. If I
> understand this correctly this document will replace RFC 3695 and parts
> of RFC 3452 that wasn't included in the already obsoleted one.
> 
> 2. There is a missing "." in the last sentence of section 1.
> 
> 3. Section 3.2.2.2:
> 
> "   The "Reserved" field in the Encoded FEC Object Transmission
>     Information SHOULD be set to zero by senders and its value SHOULD be
>     ignored by receivers."
> 
> Using the definition of SHOULD here makes it pretty difficult to use
> this field in the future. I normally recommends that at least setting it
> needs to be MUST and usually also the ignore on receiver. So that if one
> deploys a new spec that uses these bits would not throw up on them. As I
> am uncertain how widely deployed this definition already is I only ask
> the WG to consider if this should be changed or not.

Re: I-D Action:draft-ietf-rmt-bb-lct-revised-07.txt

There is a typo in section 5.2.1:

"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."

The last sentence should be saying "from 128 to 255".

Thank you,
Igor Slepchin

Internet-Drafts <at> ietf.org wrote:
> 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           : Layered Coding Transport (LCT) Building Block
> 	Author(s)       : M. Luby, et al.
> 	Filename        : draft-ietf-rmt-bb-lct-revised-07.txt
> 	Pages           : 41
> 	Date            : 2008-07-12

Re: AD comments on draft-ietf-rmt-bb-fec-basic-schemes-revised-04

Thanks Mark!

Brian Adamson
adamson <at> itd.nrl.navy.mil

On Jul 12, 2008, at 5:14 PM, Mark Watson wrote:

> I propose to address item 3 by changing the SHOULDs to MUSTs. The  
> other
> comments all seem fine to me and I will submit an update shortly.
>
> ...Mark
>
>
> On 4/18/08 2:52 AM, "Magnus Westerlund" <magnus.westerlund <at> ericsson.com 
> >
> wrote:
>
>> Hi,
>>
>> I have made my AD review of the document and have the following  
>> comments.
>>
>> 1. Obsolete information in header, abstract and introduction. If I
>> understand this correctly this document will replace RFC 3695 and  
>> parts
>> of RFC 3452 that wasn't included in the already obsoleted one.
>>
>> 2. There is a missing "." in the last sentence of section 1.
>>

I-D Action:draft-ietf-rmt-bb-fec-basic-schemes-revised-05.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           : Basic Forward Error Correction (FEC) Schemes
	Author(s)       : M. Watson
	Filename        : draft-ietf-rmt-bb-fec-basic-schemes-revised-05.txt
	Pages           : 27
	Date            : 2008-07-14

This document provides FEC Scheme specifications according to the RMT
FEC Building Block for the Compact No-Code FEC Scheme, the Small
Block, Large Block and Expandable FEC Scheme, the Small Block
Systematic FEC Scheme and the Compact FEC Scheme.  This document
obsoletes RFC3695 and assumes responsibility for the FEC Schemes
defined in RFC3452.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rmt-bb-fec-basic-schemes-revised-05.txt

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

_______________________________________________
Rmt mailing list

I-D Action:draft-ietf-rmt-sec-discussion-02.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)       : B. Adamson, V. Roca
	Filename        : draft-ietf-rmt-sec-discussion-02.txt
	Pages           : 26
	Date            : 2008-07-14

This document describes general security considerations for the
Reliable Multicast Transport (RMT) Working Group set of 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 discussion and
potential resolution of any significant security issues that may
exist in the current set of RMT standards.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rmt-sec-discussion-02.txt

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the

I-D Action:draft-ietf-rmt-bb-norm-revised-06.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           : Multicast Negative-Acknowledgment (NACK) Building Blocks
	Author(s)       : B. Adamson, et al.
	Filename        : draft-ietf-rmt-bb-norm-revised-06.txt
	Pages           : 40
	Date            : 2008-07-14

This document discusses the creation of reliable multicast protocols
utilizing negative-acknowledgment (NACK) feedback.  The rationale for
protocol design goals and assumptions are presented.  Technical
challenges for NACK-based (and in some cases general) reliable
multicast protocol operation are identified.  These goals and
challenges are resolved into a set of functional "building blocks"
that address different aspects of reliable multicast protocol
operation.  It is anticipated that these building blocks will be
useful in generating different instantiations of reliable multicast
protocols.  This document obsoletes RFC 3941.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rmt-bb-norm-revised-06.txt

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.