[Rum] Magnus Westerlund's Block on charter-ietf-rum-00-02: (with BLOCK)
Magnus Westerlund via Datatracker <noreply@ietf.org> Wed, 10 April 2019 13:39 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: rum@ietf.org
Delivered-To: rum@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 446D51203B8; Wed, 10 Apr 2019 06:39:56 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Magnus Westerlund via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: rum-chairs@ietf.org, rum@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.95.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <155490359622.22876.4380616673767598799.idtracker@ietfa.amsl.com>
Date: Wed, 10 Apr 2019 06:39:56 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rum/U1mXbAPsvdaHchpnXR6tqSjdPK4>
Subject: [Rum] Magnus Westerlund's Block on charter-ietf-rum-00-02: (with BLOCK)
X-BeenThere: rum@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Relay User Machine <rum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rum>, <mailto:rum-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rum/>
List-Post: <mailto:rum@ietf.org>
List-Help: <mailto:rum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rum>, <mailto:rum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Apr 2019 13:40:00 -0000
Magnus Westerlund has entered the following ballot position for charter-ietf-rum-00-02: Block 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.) The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/charter-ietf-rum/ ---------------------------------------------------------------------- BLOCK: ---------------------------------------------------------------------- Why are the no discussion of security mechanism being part of the profile? Considering that the profile includes the media plane, I assume at least mandatory to implement media protection security mechansism and what ciphers should be defined. Then is the of the key-management and its tie into the establishment signalling. I understand that one want to establisha a border for what is in scope and out of scope. But as I read the charter now it is completely missing. All that I find are this part: The working group will consider issues related to authentication of the parties involved in the video relay call. No protocol changes are anticipated by this work. This sounds like actually discusssing the security model. It is possible to be more explicit of how one handle the fact that one have three parties, where only one part talks to both.
- [Rum] Magnus Westerlund's Block on charter-ietf-r… Magnus Westerlund via Datatracker
- Re: [Rum] Magnus Westerlund's Block on charter-ie… Brian Rosen
- Re: [Rum] Magnus Westerlund's Block on charter-ie… Adam Roach
- Re: [Rum] Magnus Westerlund's Block on charter-ie… Magnus Westerlund
- Re: [Rum] Magnus Westerlund's Block on charter-ie… Olle E. Johansson
- Re: [Rum] Magnus Westerlund's Block on charter-ie… Adam Roach