Re: [payload] I-D Action: draft-ietf-payload-rtp-howto-08.txt

[Magnus Westerlund <[e-mail]>]

WG,

This update is triggered by comments I received from the shepherd (Ali)
as result of my request for publication. It is mostly editorials. I want
to point out the few parts where the meaning of the text has been changed:

Section 3.2.2

   FEC Framework:  The Forward Error Correction (FEC) Framework
      [RFC6363] defines how to use FEC protection for arbitrary packet
      flows.  This framework can be applied for RTP/RTCP packet flows,
      including using RTP for transmission of repair symbols, an example
      is the RTP Payload for Raptor FEC [RFC6682].

   RTP Retransmission:  The RTP retransmission scheme [RFC4588] is used
      for semi-reliability of the most important RTP packets in a media
      stream.  The level of reliability between semi and in practice
      full reliability depends on the targeted properties and situation
      where paramters such as round-trip time (RTT) allowed additional
      overhead, and allowable delay.  It often requires the application
      to be quite delay tolerant as a minimum of one round-trip time
      plus processing delay is required to perform a retransmission.
      Thus it is mostly suitable for streaming applications but may also
      be usable in certain other cases when operating in networks with
      short round-trip times.


   RFC 3611:  The RTCP Extended Reports (RTCP XR) [RFC3611] consists of
      a framework for reports sent within RTCP.  It can easily be
      extended by defining new report formats, which has and is
      occuring.  The XRBLOCK WG in IETF is chartered (at the time of
      writing) with defining new report formats.  The list of specified
      formats are available in IANA's RTCP XR Block Type registry (http:
      //www.iana.org/assignments/rtcp-xr-block-types/rtcp-xr-block-
      types.xhtml).  The report formats that are defined in RFC3611
      provide report information on packet loss, packet duplication,
      packet reception times, RTCP statistics summary and VoIP Quality.
      [RFC3611] also defines a mechanism that allows receivers to
      calculate the RTT to other session participants when used.


The spelling errors (paramters, and occuring) has been fixed in my
source and will be fixed in the next submission.

Cheers

Magnus

On 2013-10-11 11:28, [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 Working Group of the IETF.
> 
> 	Title           : How to Write an RTP Payload Format
> 	Author(s)       : Magnus Westerlund
> 	Filename        : draft-ietf-payload-rtp-howto-08.txt
> 	Pages           : 58
> 	Date            : 2013-10-11
> 
> Abstract:
>    This document contains information on how to best write an RTP
>    payload format specification.  It provides reading tips, design
>    practices, and practical tips on how to produce an RTP payload format
>    specification quickly and with good results.  A template is also
>    included with instructions.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-payload-rtp-howto
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-payload-rtp-howto-08
> 
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-payload-rtp-howto-08
> 
> 
> 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]
> 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

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  [phone]
Färögatan 6                | Mobile [phone]
SE-164 80 Stockholm, Sweden| mailto: [e-mail]
----------------------------------------------------------------------