IETF Logo Mail Archive

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

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 06 April 2020 18:07 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF3EF3A0B59 for <opsawg@ietfa.amsl.com>; Mon, 6 Apr 2020 11:07:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8cPqw1uHYmF8 for <opsawg@ietfa.amsl.com>; Mon, 6 Apr 2020 11:07:54 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5ED6C3A0DF2 for <opsawg@ietf.org>; Mon, 6 Apr 2020 11:07:54 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 7A0293897A for <opsawg@ietf.org>; Mon, 6 Apr 2020 14:06:17 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id D9FCB11A for <opsawg@ietf.org>; Mon, 6 Apr 2020 14:07:51 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "opsawg@ietf.org" <opsawg@ietf.org>
In-Reply-To: <DB7PR07MB5657A3756C15B82A65F2D72DA0C20@DB7PR07MB5657.eurprd07.prod.outlook.com>
References: <158594643249.23574.16483224996635431528@ietfa.amsl.com> <DB7PR07MB5657863B6A4D9948881C2DBCA0C20@DB7PR07MB5657.eurprd07.prod.outlook.com>, <CAHw9_iKn56LbAwgPvXjsXuQ=6JDQGozvMO4P6LjQgTzM2X0-6g@mail.gmail.com> <DB7PR07MB5657A3756C15B82A65F2D72DA0C20@DB7PR07MB5657.eurprd07.prod.outlook.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 25.1.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Mon, 06 Apr 2020 14:07:51 -0400
Message-ID: <767.1586196471@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/ad5BNJxMunV7zo-od-4W0_oakWg>
Subject: Re: [OPSAWG] I-D Action: draft-ietf-opsawg-sdi-06.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Mon, 06 Apr 2020 18:07:58 -0000

Tom, please quote better.

    > <tp>
    > Warren, thanks for that.,  I sort of guessed the first but not the
    > second.   For the second, do you get TFTP over a newly laid fibre?  I
    > was thinking not based on what I have seen but if you do then that is
    > fine..

If you buy an ethernet extension service then you can do TFTP if you want.
If you buy dark fiber, then you get whatever you decide to enable on the port
that you plug the other end into.
Would I want to enable DHCP and TFTP on that port? Not really, but it can be done.
(That's why BRSKI uses IPv6 LL addresses instead)

    > Scenarios I have encountered do not fit either of these two
    > e.g. upgrades to a remote enterprise office with lots of staff but no
    > technical expertise or the installation of a single device that must be
    > secure (e.g.  Hole in the Wall) but that is ok, it is just that I do
    > not quite see the draft excluding them,

I don't think would use SDI for either purpose you state.
Upgrades to equipment either imply it is already bootstrapped.
I don't understand the "Hole in the Wall" reference.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email