Re: [xrblock] RFC 7509 on RTP Control Protocol (RTCP) Extended Report (XR) for Post-Repair Loss Count Metrics

"Huangyihong (Rachel)" <rachel.huang@huawei.com> Thu, 14 May 2015 09:10 UTC

Return-Path: <rachel.huang@huawei.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81B3D1A8873 for <xrblock@ietfa.amsl.com>; Thu, 14 May 2015 02:10:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XMxZ0hiTAR9l for <xrblock@ietfa.amsl.com>; Thu, 14 May 2015 02:10:25 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE2901A884C for <xrblock@ietf.org>; Thu, 14 May 2015 02:10:24 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BSN37606; Thu, 14 May 2015 09:10:23 +0000 (GMT)
Received: from NKGEML410-HUB.china.huawei.com (10.98.56.41) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 14 May 2015 10:10:22 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.244]) by nkgeml410-hub.china.huawei.com ([10.98.56.41]) with mapi id 14.03.0158.001; Thu, 14 May 2015 17:10:15 +0800
From: "Huangyihong (Rachel)" <rachel.huang@huawei.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, "xrblock@ietf.org" <xrblock@ietf.org>
Thread-Topic: [xrblock] RFC 7509 on RTP Control Protocol (RTCP) Extended Report (XR) for Post-Repair Loss Count Metrics
Thread-Index: AQHQjcHrOBa+RMnAT0Wbb6jbdZ4OdJ16ojoAgACNi/A=
Date: Thu, 14 May 2015 09:10:14 +0000
Message-ID: <51E6A56BD6A85142B9D172C87FC3ABBB86311D5F@nkgeml501-mbs.china.huawei.com>
References: <20150513211307.68337180209@rfc-editor.org> <9904FB1B0159DA42B0B887B7FA8119CA5CA2E39C@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA5CA2E39C@AZ-FFEXMB04.global.avaya.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.41.144]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/xrblock/IX6FHqeOAwpsu2K2eoDmkrSTkEQ>
Subject: Re: [xrblock] RFC 7509 on RTP Control Protocol (RTCP) Extended Report (XR) for Post-Repair Loss Count Metrics
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock/>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 May 2015 09:10:27 -0000

Thank you, Dan. We can't do it without you^^.

BR,
Rachel


> -----Original Message-----
> From: xrblock [mailto:xrblock-bounces@ietf.org] On Behalf Of Romascanu, Dan
> (Dan)
> Sent: Thursday, May 14, 2015 4:43 PM
> To: xrblock@ietf.org
> Subject: Re: [xrblock] RFC 7509 on RTP Control Protocol (RTCP) Extended
> Report (XR) for Post-Repair Loss Count Metrics
> 
> Special thanks to the authors, congratulations to the whole WG!
> 
> Regards,
> 
> Dan
> 
> 
> > -----Original Message-----
> > From: xrblock [mailto:xrblock-bounces@ietf.org] On Behalf Of rfc-
> > editor@rfc-editor.org
> > Sent: Thursday, May 14, 2015 12:13 AM
> > To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org
> > Cc: drafts-update-ref@iana.org; xrblock@ietf.org;
> > rfc-editor@rfc-editor.org
> > Subject: [xrblock] RFC 7509 on RTP Control Protocol (RTCP) Extended
> > Report
> > (XR) for Post-Repair Loss Count Metrics
> >
> > A new Request for Comments is now available in online RFC libraries.
> >
> >
> >         RFC 7509
> >
> >         Title:      RTP Control Protocol (RTCP) Extended
> >                     Report (XR) for Post-Repair Loss Count
> >                     Metrics
> >         Author:     R. Huang, V. Singh
> >         Status:     Standards Track
> >         Stream:     IETF
> >         Date:       May 2015
> >         Mailbox:    rachel.huang@huawei.com,
> >                     varun@comnet.tkk.fi
> >         Pages:      11
> >         Characters: 23350
> >         Updates/Obsoletes/SeeAlso:   None
> >
> >         I-D Tag:    draft-ietf-xrblock-rtcp-xr-post-repair-loss-count-11.txt
> >
> >         URL:        https://urldefense.proofpoint.com/v2/url?u=https-
> > 3A__www.rfc-
> >
> 2Deditor.org_info_rfc7509&d=AwICAg&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4d
> > zGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=C0mhwLTDMDzD63lKeq
> > Mf8A2BqfL3g-OQWPOUdh9GShY&s=2e-
> > FvkyM9kgsxP32bnjs0fFVu3aN2y1tXLB5tuvnJiU&e=
> >
> >         DOI:        https://urldefense.proofpoint.com/v2/url?u=http-
> > 3A__dx.doi.org_10.17487_RFC7509&d=AwICAg&c=BFpWQw8bsuKpl1SgiZH6
> > 4Q&r=I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=C0mhwLTDMD
> > zD63lKeqMf8A2BqfL3g-
> > OQWPOUdh9GShY&s=lBl3PrUZW_AX3VAAwzopv52oIkrVqIzLUHu09b9yjuY&
> > e=
> >
> > This document defines an RTP Control Protocol (RTCP) Extended Report
> > (XR) block that allows reporting of a post-repair loss count metric
> > for a range of RTP applications.  In addition, another metric,
> > repaired loss count, is also introduced in this report block for
> > calculating the pre-repair loss count when needed, so that the RTP
> > sender or a third-party entity is able to evaluate the effectiveness of the
> repair methods used by the system.
> >
> > This document is a product of the Metric Blocks for use with RTCPs
> > Extended Report Framework Working Group of the IETF.
> >
> > This is now a Proposed Standard.
> >
> > STANDARDS TRACK: This document specifies an Internet Standards Track
> > protocol for the Internet community, and requests discussion and
> > suggestions for improvements.  Please refer to the current edition of
> > the Official Internet Protocol Standards
> > (https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-
> >
> 2Deditor.org_standards&d=AwICAg&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzG
> > xR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=C0mhwLTDMDzD63lKeqMf
> > 8A2BqfL3g-
> > OQWPOUdh9GShY&s=IAZmcUtgcwbiZVRsO4ceCzIwoHnDK1M52IZR7YkuCB4
> > &e= ) for the standardization state and status of this protocol.
> > Distribution of this memo is unlimited.
> >
> > This announcement is sent to the IETF-Announce and rfc-dist lists.
> > To subscribe or unsubscribe, see
> >   https://urldefense.proofpoint.com/v2/url?u=https-
> > 3A__www.ietf.org_mailman_listinfo_ietf-
> > 2Dannounce&d=AwICAg&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGxR31OcNX
> > CJfQzvlsiLQfucBXRucPvdrphpBsFA&m=C0mhwLTDMDzD63lKeqMf8A2BqfL3g
> > -OQWPOUdh9GShY&s=4ZeYLGyhXBPZlz4NrZNX0p8m28Gy3y-
> > vyeDjSgVhQyw&e=
> >   https://urldefense.proofpoint.com/v2/url?u=https-3A__mailman.rfc-
> > 2Deditor.org_mailman_listinfo_rfc-
> >
> 2Ddist&d=AwICAg&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGxR31OcNXCJfQzvl
> > siLQfucBXRucPvdrphpBsFA&m=C0mhwLTDMDzD63lKeqMf8A2BqfL3g-
> > OQWPOUdh9GShY&s=khacJPQAlKrnLlB4rdRsl8Snt2T3jYRYoghdtg7JVVg&e=
> >
> > For searching the RFC series, see
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-
> > 2Deditor.org_search&d=AwICAg&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGxR
> > 31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=C0mhwLTDMDzD63lKeqMf8A
> > 2BqfL3g-OQWPOUdh9GShY&s=UgwYXCwLoY4H-
> > ko3XKRtifN9Qa1GM2x3KQeqn-4ETf8&e=
> > For downloading RFCs, see
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-
> > 2Deditor.org_rfc.html&d=AwICAg&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGx
> > R31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=C0mhwLTDMDzD63lKeqMf8
> > A2BqfL3g-OQWPOUdh9GShY&s=J2f4rrLR6RPCdoF4AkcWbpFcdb-
> > 3q7jfMKlsheAKBKc&e=
> >
> > Requests for special distribution should be addressed to either the
> > author of the RFC in question, or to rfc-editor@rfc-editor.org.
> > Unless specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
> >
> >
> > The RFC Editor Team
> > Association Management Solutions, LLC
> >
> >
> > _______________________________________________
> > xrblock mailing list
> > xrblock@ietf.org
> > https://urldefense.proofpoint.com/v2/url?u=https-
> > 3A__www.ietf.org_mailman_listinfo_xrblock&d=AwICAg&c=BFpWQw8bsuK
> > pl1SgiZH64Q&r=I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=C0mh
> > wLTDMDzD63lKeqMf8A2BqfL3g-
> > OQWPOUdh9GShY&s=s4C13h7J5JUYEQYpMttFPLkZuGByXar6RPp60PcIHzQ&
> > e=
> 
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock