[dispatch] Roman Danyliw's No Objection on charter-ietf-sframe-00-00: (with COMMENT)

Roman Danyliw via Datatracker <noreply@ietf.org> Wed, 09 September 2020 20:41 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: dispatch@ietf.org
Delivered-To: dispatch@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 887213A0DEA; Wed, 9 Sep 2020 13:41:36 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Roman Danyliw via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: sframe-chairs@ietf.org, sframe@ietf.org, dispatch@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.16.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Roman Danyliw <rdd@cert.org>
Message-ID: <159968409648.6670.955964550557674225@ietfa.amsl.com>
Date: Wed, 09 Sep 2020 13:41:36 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/JqGXgKJhnyJ6rHcO0B0n-yAxB4Y>
Subject: [dispatch] Roman Danyliw's No Objection on charter-ietf-sframe-00-00: (with COMMENT)
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Sep 2020 20:41:37 -0000

Roman Danyliw has entered the following ballot position for
charter-ietf-sframe-00-00: 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.)



The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/charter-ietf-sframe/



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

** I share Éric Vyncke concerns with the bulleted list of what SFRAME
encapsulation will provide.  My recommendation would be to reframe this text
around what security properties/assurances/services this encapsulation will
provide (rather than a functional list).

** If configuring the security services is out of scope, where is it
anticipated that this signalling protocol work would occur?