Re: [payload] I-D Action: draft-ietf-payload-flexible-fec-scheme-12.txt

[Magnus Westerlund <[e-mail]>]

Hi Authors.

With the exception of the id-nits and RID reference this is ready. But can you please addresses the below relevant ID-nits and update the reference to RID to the WG version. Authors should always run ID-nits before submitting a version. It avoids so many small errors.


/tmp/draft-ietf-payload-flexible-fec-scheme-12.txt(1946): Found possible IPv4 address '143.163.151.157' in position 18; this doesn't match the suggested documentation address ranges specified in RFC 6890 (or successor): blocks 192.0.2.0/24 (TEST-NET-1), 198.51.100.0/24 (TEST-NET-2), and 203.0.113.0/24 (TEST-NET-3); or the 233.252.0.0/24 (MCAST-TEST-NET) example multicast address range specified in RFC 5771.


  == Unused Reference: 'RFC6709' is defined on line 1735, but no explicit
     reference was found in the text
     '[RFC6709]  Carpenter, B., Aboba, B., Ed., and S. Cheshire, "Design C...'

  == Unused Reference: 'RFC2733' is defined on line 1762, but no explicit
     reference was found in the text
     '[RFC2733]  Rosenberg, J. and H. Schulzrinne, "An RTP Payload Format...'

  == Unused Reference: 'SMPTE2022-1' is defined on line 1801, but no explicit
     reference was found in the text
     '[SMPTE2022-1] SMPTE 2022-1-2007, "Forward Error Correction for Real-...'

  ** Obsolete normative reference: RFC 3555 (Obsoleted by RFC 4855, RFC 4856)

  ** Downref: Normative reference to an Informational RFC: RFC 6709

  -- Obsolete informational reference (is this intentional?): RFC 2326
     (Obsoleted by RFC 7826)

  -- Obsolete informational reference (is this intentional?): RFC 2733
     (Obsoleted by RFC 5109)

  -- Obsolete informational reference (is this intentional?): RFC 5246
     (Obsoleted by RFC 8446)

Replace I-D.roach-avtext-rid] with

https://tools.ietf.org/html/draft-ietf-avtext-rid-09

Cheers

Magnus

On 2018-12-08 00:32, [e-mail]<mailto:[e-mail]> wrote:


A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Audio/Video Transport Payloads WG of the IETF.

        Title           : RTP Payload Format for Flexible Forward Error Correction (FEC)
        Authors         : Mo Zanaty
                          Varun Singh
                          Ali Begen
                          Giridhar Mandyam
        Filename        : draft-ietf-payload-flexible-fec-scheme-12.txt
        Pages           : 41
        Date            : 2018-12-07

Abstract:
   This document defines new RTP payload formats for the Forward Error
   Correction (FEC) packets that are generated by the non-interleaved
   and interleaved parity codes from source media encapsulated in RTP.
   These parity codes are systematic codes, where a number of FEC repair
   packets are generated from a set of source packets from one or more
   source RTP streams.  These FEC repair packets are sent in a
   redundancy RTP stream separate from the source RTP stream(s) that
   carries the source packets.  RTP source packets that were lost in
   transmission can be reconstructed using the source and repair packets
   that were received.  The non-interleaved and interleaved parity codes
   which are defined in this specification offer a good protection
   against random and bursty packet losses, respectively, at a cost of
   decent complexity.  The RTP payload formats that are defined in this
   document address the scalability issues experienced with the earlier
   specifications including RFC 2733, RFC 5109 and SMPTE 2022-1, and
   offer several improvements.  Due to these changes, the new payload
   formats are not backward compatible with the earlier specifications,
   but endpoints that do not implement this specification can still work
   by simply ignoring the FEC repair packets.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-payload-flexible-fec-scheme/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-payload-flexible-fec-scheme-12
https://datatracker.ietf.org/doc/html/draft-ietf-payload-flexible-fec-scheme-12

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-payload-flexible-fec-scheme-12


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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

_______________________________________________
I-D-Announce mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt




--

Magnus Westerlund

----------------------------------------------------------------------
Network Architecture & Protocols, Ericsson Research
----------------------------------------------------------------------
Ericsson AB                 | Phone  [phone]
Torshamnsgatan 23           | Mobile [phone]
SE-164 80 Stockholm, Sweden | mailto: [e-mail]<mailto:[e-mail]>
----------------------------------------------------------------------