[xrblock] Mirja Kühlewind's No Objection on draft-ietf-xrblock-independent-burst-gap-discard-02: (with COMMENT)

"Mirja Kuehlewind" <ietf@kuehlewind.net> Tue, 02 August 2016 15:17 UTC

Return-Path: <ietf@kuehlewind.net>
X-Original-To: xrblock@ietf.org
Delivered-To: xrblock@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EC5912D695; Tue, 2 Aug 2016 08:17:27 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "Mirja Kuehlewind" <ietf@kuehlewind.net>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160802151727.27859.51417.idtracker@ietfa.amsl.com>
Date: Tue, 02 Aug 2016 08:17:27 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/xrblock/3xQh6Gal_bOYfqONmCbrPMwZ2P0>
Cc: draft-ietf-xrblock-independent-burst-gap-discard@ietf.org, xrblock-chairs@ietf.org, xrblock@ietf.org
Subject: [xrblock] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draf?= =?utf-8?q?t-ietf-xrblock-independent-burst-gap-discard-02=3A_=28with_COMM?= =?utf-8?q?ENT=29?=
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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, 02 Aug 2016 15:17:28 -0000

Mirja Kühlewind has entered the following ballot position for
draft-ietf-xrblock-independent-burst-gap-discard-02: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-xrblock-independent-burst-gap-discard/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Sorry still not an RT(C)P expert, but one question out of curiosity:

Would it be a valid operation if I send one MIR Block per burst (by
adapting the measurement duration dynamically), in case I really want to
know the length of each burst separately? 

If so (or also if not, I guess), would it make sense to give
recommendations about how often one should send feedback, or is this
generally covered elsewhere (provide pointer!) that applies for this
case?