[MMUSIC] Stephen Farrell's Discuss on draft-ietf-mmusic-msid-14: (with DISCUSS)
"Stephen Farrell" <stephen.farrell@cs.tcd.ie> Thu, 16 June 2016 11:39 UTC
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 152FB12D192; Thu, 16 Jun 2016 04:39:38 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.22.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160616113938.10476.41211.idtracker@ietfa.amsl.com>
Date: Thu, 16 Jun 2016 04:39:38 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/azAPqY1lIvpFwlBRKDFhIssQ0Pc>
Cc: fandreas@cisco.com, mmusic-chairs@ietf.org, draft-ietf-mmusic-msid@ietf.org, mmusic@ietf.org
Subject: [MMUSIC] Stephen Farrell's Discuss on draft-ietf-mmusic-msid-14: (with DISCUSS)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jun 2016 11:39:38 -0000
Stephen Farrell has entered the following ballot position for draft-ietf-mmusic-msid-14: Discuss 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-mmusic-msid/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- I'm not sure that the answer to this question will require any change to the document but wanted to check... I wondered about the privacy properties of these (and related) WebRTC identifiers, esp. if they are being handled at various different layers. Is there work somewhere in the WebRTC space that's analysing that? For example, one concern might be that msid-appdata could end up with some kind of privacy sensitive value, but there's no guidance here about that and as the examples use UUIDs it's not clear to me those represent nor what typical values will be used. (Note: I'm not saying that I believe this is a problem, I'm just checking if it's been considered.) I hope that there's no reason why these can't be very ephemeral values that don't identify (or help re-identification of) people or their preferences, locations etc., and I'd imagine there's little reason to e.g. log them. If that's the case wouldn't it be useful to add such guidance (somewhere, maybe not here) to help developers to do the right thing?
- Re: [MMUSIC] Stephen Farrell's Discuss on draft-i… Harald Alvestrand
- Re: [MMUSIC] Stephen Farrell's Discuss on draft-i… Stephen Farrell
- Re: [MMUSIC] Stephen Farrell's Discuss on draft-i… Alissa Cooper
- [MMUSIC] Stephen Farrell's Discuss on draft-ietf-… Stephen Farrell