[xrblock] any implementations or plans to implement draft-ietf-xrblock-rtcp-xr-psi-decodability-03?
"Romascanu, Dan (Dan)" <dromasca@avaya.com> Wed, 30 April 2014 11:34 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 05BEA1A6F38 for <xrblock@ietfa.amsl.com>; Wed, 30 Apr 2014 04:34:11 -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 eSyKVLVJiRcq for <xrblock@ietfa.amsl.com>; Wed, 30 Apr 2014 04:34:08 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id DE7841A081E for <xrblock@ietf.org>; Wed, 30 Apr 2014 04:34:07 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmYFAG7fYFOHCzIm/2dsb2JhbABZgkIjIU9XrR+OJIh7gScWdIInAQEDEhteAQwJFVYmAQQbGogfAQyXFYRZri0XjiCDXIEVBJpfhU6LYIFygT+CKw
X-IronPort-AV: E=Sophos; i="4.97,957,1389762000"; d="scan'208,217"; a="52492344"
Received: from unknown (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([135.11.50.38]) by de307622-de-outbound.net.avaya.com with ESMTP; 30 Apr 2014 07:34:04 -0400
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC01.global.avaya.com) ([135.64.58.11]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/AES128-SHA; 30 Apr 2014 07:32:55 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC01.global.avaya.com ([135.64.58.11]) with mapi id 14.03.0174.001; Wed, 30 Apr 2014 13:34:02 +0200
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "xrblock@ietf.org" <xrblock@ietf.org>
Thread-Topic: any implementations or plans to implement draft-ietf-xrblock-rtcp-xr-psi-decodability-03?
Thread-Index: Ac9kaBVwpsUefi9yRkutqPaYcvHg1Q==
Date: Wed, 30 Apr 2014 11:34:02 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5C7CCC4E@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.45]
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA5C7CCC4EAZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/xrblock/KMC2BzE2cV9mv-YXOb2YeRXnsRQ
Subject: [xrblock] any implementations or plans to implement draft-ietf-xrblock-rtcp-xr-psi-decodability-03?
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: Wed, 30 Apr 2014 11:34:11 -0000
Hi, I am preparing the shepherd write-up to submit draft-ietf-xrblock-rtcp-xr-psi-decodability-03<http://datatracker.ietf.org/doc/draft-ietf-xrblock-rtcp-xr-psi-decodability/> to the IESG. It would be useful if you can share either on the WG list, or in mails to the chairs which will be kept confidential if so you wish, whether you have written any early implementations of the I-D, or plan to write such implementations soon or after the document becomes an RFC. Thanks and Regards, Dan
- [xrblock] any implementations or plans to impleme… Romascanu, Dan (Dan)