[xrblock] implementations or plans to implement draft-ietf-xrblock-rtcp-xr-psi-decodability
"Romascanu, Dan (Dan)" <dromasca@avaya.com> Tue, 13 May 2014 18:01 UTC
Return-Path: <dromasca@avaya.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 217ED1A01C5 for <xrblock@ietfa.amsl.com>; Tue, 13 May 2014 11:01:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.25
X-Spam-Level:
X-Spam-Status: No, score=-3.25 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.651] 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 gtdzIXH2Ycd6 for <xrblock@ietfa.amsl.com>; Tue, 13 May 2014 11:01:30 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 550611A01B7 for <xrblock@ietf.org>; Tue, 13 May 2014 11:01:30 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8FAPdcclPGmAcV/2dsb2JhbABZgkIjIU9Yq1UBAQEBAQEGmh0BgSMWdIInAQEDEhteARUVViYBBBsaiB8BnHCEWaVLF4VUiEmDY4EVBIlXlwqLf4F3gT+CMA
X-IronPort-AV: E=Sophos;i="4.97,1044,1389762000"; d="scan'208,217";a="62756274"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by co300216-co-outbound.net.avaya.com with ESMTP; 13 May 2014 14:01:23 -0400
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/AES128-SHA; 13 May 2014 13:44:35 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.03.0174.001; Tue, 13 May 2014 14:01:16 -0400
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "xrblock@ietf.org" <xrblock@ietf.org>
Thread-Topic: implementations or plans to implement draft-ietf-xrblock-rtcp-xr-psi-decodability
Thread-Index: Ac9u1VRnMgLDaObOR7eMCHedR/W+ng==
Date: Tue, 13 May 2014 18:01:15 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5C7E5046@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.64.58.46]
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA5C7E5046AZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/xrblock/7YsApyp0Ue5tJHF490IjNDuBPlc
Subject: [xrblock] implementations or plans to implement draft-ietf-xrblock-rtcp-xr-psi-decodability
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: Tue, 13 May 2014 18:01:35 -0000
I am preparing the shepherd write-up to submit draft-ietf-xrblock-rtcp-xr-psi-decodability-03. Two of the questions in the Document Quality section of the write-up are: Ø Are there existing implementations of the protocol? Have a significant number of vendors indicated their plan to implement the specification? Any relevant information about existing or planned implementations are very useful. You can answer directly to the chairs (me or Shida) in case you want to keep this information confidential. Thanks and Regards, Dan
- [xrblock] implementations or plans to implement d… Romascanu, Dan (Dan)