Subject: [xrblock] [IANA #798819] Last Call: <draft-ietf-xrblock-rtcp-xr-post-repair-loss-count-07.txt> (RTP Control Protocol (RTCP) Extended Report (XR) for Post-Repair Loss Count Metrics) to Proposed Standard

From: "Pearl Liang via RT" <[email-masked]>
Date: Mon, 22 Dec 2014 19:04:37 +0000

(BEGIN IANA LAST CALL COMMENTS)

IESG/Authors/WG Chairs:

IANA has reviewed draft-ietf-xrblock-rtcp-xr-post-repair-loss-count-07.  Authors should review the comments and/or questions below.  Please report any inaccuracies and respond to any questions as soon as possible.

We received the following comments/questions from the IANA's reviewer:

IANA understands that, upon approval of this document, there are two actions which IANA must complete.

First, in the RTCP XR Block Type subregistry of the RTP Control Protocol Extended Reports (RTCP XR) Block Type Registry located at:

http://www.iana.org/assignments/rtcp-xr-block-types/

a new block type will be registered as follows:

BT: [ TBD-at-registration ]
Name: Post-Repair Loss Count Metrics Report Block
Reference: [ RFC-to-be ]

IANA Note: As this document requests registrations in a Specification Required (see RFC 5226) registry, we will initiate the required Expert Review via a separate request. Expert review will need to be completed before your document can be approved for publication as an RFC.

Second, in the RTCP XR SDP Parameters registry in the RTP Control Protocol Extended Reports (RTCP XR) Session Description Protocol (SDP) Parameters Registry located at:

http://www.iana.org/assignments/rtcp-xr-sdp-parameters/

a new XR SDP parameter is to be registered as follows:

Parameter: post-repair-loss-count
Reference: [ RFC-to-be ]

IANA Note: As this document requests registrations in a Specification Required (see RFC 5226) registry, we will initiate the required Expert Review via a separate request. Expert review will need to be completed before your document can be approved for publication as an RFC.

IANA understands that, upon approval of this document, these two actions are the only ones required to be completed.

Note:  The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is only to confirm what actions will be performed.  

Please note that IANA cannot reserve specific values. However, early allocation is available for some types of registrations. For more information, please see RFC 7120. 

Thanks,

Pearl Liang
ICANN

(END IANA LAST CALL COMMENTS)

On Fri Dec 12 22:23:06 2014, [email-masked] wrote:
> 
> The IESG has received a request from the Metric Blocks for use with
> RTCP's Extended Report Framework WG (xrblock) to consider the
> following
> document:
> - 'RTP Control Protocol (RTCP) Extended Report (XR) for Post-Repair
> Loss
>    Count Metrics'
>   <draft-ietf-xrblock-rtcp-xr-post-repair-loss-count-07.txt> 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
> [email-masked] mailing lists by 2014-12-26. Exceptionally, comments may
> be
> sent to [email-masked] instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>    This document defines an RTP Control Protocol (RTCP) Extended
> Report
>    (XR) Block that allows reporting of post-repair loss count metrics
>    for a range of RTP applications.
> 
> 
> 
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-xrblock-rtcp-xr-post-
> repair-loss-count/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-xrblock-rtcp-xr-post-
> repair-loss-count/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
>