IETF Logo Mail Archive

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

tom petch <ietfc@btconnect.com> Tue, 07 April 2020 09:15 UTC

Return-Path: <ietfc@btconnect.com>
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 330883A198B for <opsawg@ietfa.amsl.com>; Tue, 7 Apr 2020 02:15:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.com
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 8tcjq-B1fTNb for <opsawg@ietfa.amsl.com>; Tue, 7 Apr 2020 02:15:41 -0700 (PDT)
Received: from EUR03-AM5-obe.outbound.protection.outlook.com (mail-eopbgr30111.outbound.protection.outlook.com [40.107.3.111]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08BC13A198A for <opsawg@ietf.org>; Tue, 7 Apr 2020 02:15:40 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=OQjokelcdp3zxc7eis7/GBniNga3p9qMEfVxtCwOBylf0gzMSwgiK7Ycgrhju5tdweo1rIP5XKhXwKQgG8L75T4Pg9Y7lC3qceOcxgQxSAplcZ9S6Aici1u7SglSefurkU8dtid+WiHWLsCDp1GqPXnT0cnZzhcfHEVPaw27Furx+77D9a6Cf7UhVzheUrb4ms2tXfl3O0kz6pyWbrpXGzCh/2KDWIJCJz/esFrRvxyuIMDJkqi48u7kR+SlsoG6uPWUMVRJaUuGK+G/TBdjz/gUTGMssmRC6cTuStnc4rtAUsR0UmeHy3bJSlh1Sry1mH8Q3awD+4bsXlKfnQcWfg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=GScDpNOK0Zm/EricZxbSihRRRahZZmtPgaad9+92zgw=; b=EtkuRnJ+hNV3cpxcAkVlAkZbmJ8vTURWLvQb+LQ5V08nA34344LjnvK/5gT1+AldWyqgCM/u/OWnATMCov3BrxwhQU8+Y6OYtmP+dE8UQOHBTGIPl/r3tJR0ZXXyGPer45QJHGroVnWYVIach6j7O6ePxaj/Pe5SD4LZGaJDP8Cf2cDfc4eqyonwnfOEPpX8s282fT0gW0PG6LF8OapAioKS7KZcx+oYxBbYwRiMRWmaLCsaZOyCPo7A3Iqx2HZDEK6u28qC5doD/hjlA5GyguqX99chKCxY10mHumbjVMTaRGmwbVwmaDXyH+bhht7/KbX/ZHoAFbh93DUfJekc+A==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=GScDpNOK0Zm/EricZxbSihRRRahZZmtPgaad9+92zgw=; b=IBH24AzH/uK/E/2gymBbqBhRsaPXyifg/AYg7F1Oh99iW0B+zJwmbh6uUyoUczgA05HC2xtELuxhySqxPh5eM9WJyFatvvM4Ub/TrmX4af2qvKVHT7azxbLrs/ztpGCD6Idk99yMSF1QFxlxZF0qarfwsPtJunQzqI7IHs3Wz30=
Received: from DB7PR07MB5657.eurprd07.prod.outlook.com (20.178.85.222) by DB7PR07MB5466.eurprd07.prod.outlook.com (20.178.46.207) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2900.14; Tue, 7 Apr 2020 09:15:38 +0000
Received: from DB7PR07MB5657.eurprd07.prod.outlook.com ([fe80::a438:bbc9:2ffe:33ee]) by DB7PR07MB5657.eurprd07.prod.outlook.com ([fe80::a438:bbc9:2ffe:33ee%5]) with mapi id 15.20.2900.012; Tue, 7 Apr 2020 09:15:38 +0000
From: tom petch <ietfc@btconnect.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: [OPSAWG] I-D Action: draft-ietf-opsawg-sdi-06.txt
Thread-Index: AQHWCfg7OICJyubiukuZB1JQVnMIPahr51s+gABOyoCAAAibX4AAKeGAgAD70T8=
Date: Tue, 07 Apr 2020 09:15:38 +0000
Message-ID: <DB7PR07MB5657D95DFDC8AA5591FEF278A0C30@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>, <767.1586196471@localhost>
In-Reply-To: <767.1586196471@localhost>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ietfc@btconnect.com;
x-originating-ip: [81.131.229.19]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: c9707eab-a818-4b1b-0b49-08d7dad43cbe
x-ms-traffictypediagnostic: DB7PR07MB5466:
x-microsoft-antispam-prvs: <DB7PR07MB5466E00352812E75C7446AD3A0C30@DB7PR07MB5466.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 036614DD9C
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DB7PR07MB5657.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(10019020)(136003)(376002)(396003)(366004)(39860400002)(346002)(9686003)(5660300002)(71200400001)(6506007)(8936002)(64756008)(55016002)(66476007)(66946007)(81156014)(26005)(81166006)(66446008)(66556008)(33656002)(76116006)(2906002)(7696005)(91956017)(110136005)(52536014)(186003)(8676002)(316002)(478600001)(86362001); DIR:OUT; SFP:1102;
received-spf: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: uy9GkeE5C9Kj4xluDeIJWp4Rq5nW1jm8y7PGWV7ahk1fDntlQ4+PTKWYUstr91pLAgQqEucQR1hcKK/VLM+rniRmFHR0nHPbJB2S+WmymJBCTKWGUp1xdqE4f2AXAHLb58wAslvwm+x08BMK78Svd5s8X15EsHVflSmgRAFhr5sOPD30403YCLA946vM7mECUOLLHfPORz0ZyUeTQBEASQG12hHMIBN/3f6LvQkuqSlngL9BfoR0AkG9e6Pcu0PANnxknWysL/0KkV1FKqFxg6wZ00jRtBnz0+Dj5E2DAoBygCHv7tJeL0M58WCedutEnSL7VrTR+yVSDKYbmOKrENhxl2bzG6dKOieAAN0agHOVx6iTbGLp16t+GJYdAUlhrMPUGz4Hu7mBNBE/xB3JnhZqqJL2TG1jT6FBENllr/maIUfdCvYeCPci/4CE9hi3
x-ms-exchange-antispam-messagedata: 5T7wDF4XoIvNeuAmFOg7ysY6SvUgCdBXHXMTPT5FFPCQh/cpQFXpbdYchx8jBf/fSvWbwn4WVIRrdpTowsSnfTJ3IADy3msd4M00rLZ5Y3hoEvH1oQxiVd0McksyGkUQQsNqvawWsL+KKULZIAj8Xw==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: c9707eab-a818-4b1b-0b49-08d7dad43cbe
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Apr 2020 09:15:38.2244 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: DJN8HyljraEYBnV3jLN6PIs3DaxbDg1TtUUpwgJpCWscx+zrVv76skK1Sc/xdCitVCH17HCfeXaNzuN5gPNE5A==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB7PR07MB5466
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/tJ73HOE0QfrEL1MvEFLJMoJmjMM>
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: Tue, 07 Apr 2020 09:15:43 -0000

From: OPSAWG <opsawg-bounces@ietf.org> on behalf of Michael Richardson <mcr+ietf@sandelman.ca>
Sent: 06 April 2020 19:07

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.

<tp>
Hole in the Wall is ATM or cash dispenser - an isolated device in a hostile location at the end of a piece of wire where security is paramount.

Apologies if my responses are not as easy to see as they might be; I am currently stuck with a web interface that does lots of things that I wish it did not and does not do what I had taken for granted for decades, like indenting all old text with '> '.  Even the way in which existing e-mails are displayed to me seems random, sometimes using indentation with spaces, sometimes  '> ' (to me the obviously best way to do it) sometimes coloured lines down the side of the screen, all of which seems outside my control - sigh.

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

v2.23.0 | Report a Bug | By Email