Re: [OPSAWG] I-D Action: draft-ietf-opsawg-sdi-06.txt

Warren

Where I think I get confused with this is its context.  Abstract talks of travelling to a datacentre and elsewhere there are references to a POP, both of which to me have a flavour of a well-staffed high in technical expertise locations where this sort of work is little needed.  I think more of enterprise, where an organisation may have two well equipped data centres and dozens or hundreds of locations with little or no support staff where this issue is paramount.  I think that this is more a question of language than of changing the technical details but it does keep jarring with me.  In the same vein, the references to routers jars with me since while that may be an issue in an operator POP, I see the need to configure other kinds of servers as more pressing.

The other more technical issue is TFTP which yes, I expect will be widely used but which, IMHO, is only ever used over a LAN and so, short of VLAN, which indeed some enterprise do use, implies that the device and config server are on the same LAN, ie in the same building or at least campus.  Again, it is a question of context, is it assumed that device and server are proximal?

I would like to see these two points nailed down more after which I could propose some refinement to the language.

Tom Petch

________________________________________
From: OPSAWG <opsawg-bounces@ietf.org> on behalf of internet-drafts@ietf.org <internet-drafts@ietf.org>
Sent: 03 April 2020 21:40
To: i-d-announce@ietf.org
Cc: opsawg@ietf.org
Subject: [OPSAWG] I-D Action: draft-ietf-opsawg-sdi-06.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Operations and Management Area Working Group WG of the IETF.

        Title           : Secure Device Install
        Authors         : Warren Kumari
                          Colin Doyle
        Filename        : draft-ietf-opsawg-sdi-06.txt
        Pages           : 18
        Date            : 2020-04-03

Abstract:
   Deploying a new network device often requires that an employee
   physically travel to a datacenter to perform the initial install and
   configuration, even in shared datacenters with "smart-hands" type
   support.  In many cases, this could be avoided if there were a
   standard, secure way to initially provision the devices.

   This document extends existing auto-install / Zero-Touch Provisioning
   mechanisms to make the process more secure.

   [ Ed note: Text inside square brackets ([]) is additional background
   information, answers to frequently asked questions, general musings,
   etc.  They will be removed before publication.  This document is
   being collaborated on in Github at: https://github.com/wkumari/draft-
   wkumari-opsawg-sdi.  The most recent version of the document, open
   issues, etc should all be available here.  The authors (gratefully)
   accept pull requests. ]

   [ Ed note: This document introduces concepts and serves as the basic
   for discussion - because of this, it is conversational, and would
   need to be firmed up before being published ]

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-opsawg-sdi/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-opsawg-sdi-06
https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-sdi-06

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-opsawg-sdi-06

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg