[OPSAWG] Erik Kline's No Objection on draft-ietf-opsawg-sdi-11: (with COMMENT)

Erik Kline via Datatracker <noreply@ietf.org> Thu, 21 May 2020 00:57 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: opsawg@ietf.org
Delivered-To: opsawg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 12E583A0969; Wed, 20 May 2020 17:57:59 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Erik Kline via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-opsawg-sdi@ietf.org, opsawg-chairs@ietf.org, opsawg@ietf.org, Michael Richardson <mcr+ietf@sandelman.ca>, mcr+ietf@sandelman.ca
X-Test-IDTracker: no
X-IETF-IDTracker: 7.0.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Erik Kline <ek.ietf@gmail.com>
Message-ID: <159002267905.20638.7070753703953679900@ietfa.amsl.com>
Date: Wed, 20 May 2020 17:57:59 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/DKhljtZU1s_E0SictzR4vVMaJrk>
Subject: [OPSAWG] Erik Kline's No Objection on draft-ietf-opsawg-sdi-11: (with COMMENT)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 May 2020 00:58:00 -0000

Erik Kline has entered the following ballot position for
draft-ietf-opsawg-sdi-11: 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-opsawg-sdi/



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

[[ comments ]]

* Perhaps a suggestion that vendors might want to have a factory-installed
  option for interested customers that /only/ an encrypted config can be tried
  and no attempt to use a plaintext config will be made.

* Security considerations paragraph about control of the configuration server
  should include a mention that the key is not required for interference if
  the booting device will happily fall back to loading a cleartext config.

* Though less common than DHCPv4, consider acknowledging the broader (open)
  issue of file/TFTP server service discovery (DHCPv6, RAs plus resolution of
  a well-known hostname, DNSSD, ...).


[[ nits ]]

[ section 4.2 ]
* "Publish TFTP Server" --> "Publish to TFTP Server", perhaps