IETF Logo Mail Archive

Re: [core] Conclusion -- Endpoint Client Name / Endpoint Name in RD draft

Hannes Tschofenig <Hannes.Tschofenig@arm.com> Tue, 08 May 2018 11:20 UTC

Return-Path: <Hannes.Tschofenig@arm.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D78212D943 for <core@ietfa.amsl.com>; Tue, 8 May 2018 04:20:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=armh.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 fQ2VNSfVNTJr for <core@ietfa.amsl.com>; Tue, 8 May 2018 04:20:28 -0700 (PDT)
Received: from EUR02-AM5-obe.outbound.protection.outlook.com (mail-eopbgr00079.outbound.protection.outlook.com [40.107.0.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D02612D944 for <core@ietf.org>; Tue, 8 May 2018 04:20:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com; s=selector1-arm-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=P0D+sZWg0tyj0U0LJ5qO7PX6jsx4wevO85rNugpBzTQ=; b=mWOTh8xdzzjg3Lx4WQQCMegA3qfqeqIOpteo2OYUXUKV5jBJu9rzFbocTvs5SovLfiCYXqccjvZIXGhZ/ybSvKxRontpKck3YzYZjVCm2OnRGhSA6qKh+xG6QgTiSrJ2UcCJI4eDSTBuNJOi2rzhrZiHHpNRRvC1sXcmU7Btgr8=
Received: from VI1PR0801MB2112.eurprd08.prod.outlook.com (10.173.75.16) by VI1PR0801MB1293.eurprd08.prod.outlook.com (10.167.197.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.735.17; Tue, 8 May 2018 11:20:24 +0000
Received: from VI1PR0801MB2112.eurprd08.prod.outlook.com ([fe80::4004:973e:4b3:ef88]) by VI1PR0801MB2112.eurprd08.prod.outlook.com ([fe80::4004:973e:4b3:ef88%18]) with mapi id 15.20.0735.018; Tue, 8 May 2018 11:20:24 +0000
From: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
To: "consultancy@vanderstok.org" <consultancy@vanderstok.org>, "Kovatsch, Matthias" <matthias.kovatsch@siemens.com>
CC: Mohit Sethi <mohit.m.sethi@ericsson.com>, "core@ietf.org" <core@ietf.org>
Thread-Topic: [core] Conclusion -- Endpoint Client Name / Endpoint Name in RD draft
Thread-Index: AdPmCfncz1IX5t6GRJaeO0C+mMHM9QAAOSUAAADDndAAA/ZdAAAf4kIAAAgtFAA=
Date: Tue, 08 May 2018 11:20:24 +0000
Message-ID: <VI1PR0801MB21120759DA3370D6B44E11E0FA9A0@VI1PR0801MB2112.eurprd08.prod.outlook.com>
References: <VI1PR0801MB2112B9A4410DA3EDE39183BEFA9B0@VI1PR0801MB2112.eurprd08.prod.outlook.com> <bd85e420-c6ce-3e87-406a-4cd5a4fafaa6@ericsson.com> <VI1PR0801MB21121FAE34CE76841CF6DBE1FA9B0@VI1PR0801MB2112.eurprd08.prod.outlook.com> <4EBB3DDD0FBF694CA2A87838DF129B3C01F36340@DEFTHW99EL4MSX.ww902.siemens.net> <f046a8bc9f54328a4c29f9b2426d761e@xs4all.nl>
In-Reply-To: <f046a8bc9f54328a4c29f9b2426d761e@xs4all.nl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Hannes.Tschofenig@arm.com;
x-originating-ip: [213.120.252.178]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; VI1PR0801MB1293; 7:KBuAvJc7o7pOUblJmEQj/fXcsBWTmnSYl/k5LTaGIDGh2J6crWszciH+T4FFCxBtJexVkDRGejoZkEGM9zGbto9/2Srwk9kHJQfI/tHp1ZzqddbxEZzfcYIayVLC/rJLJzqmVha4/BPr9IVxYXN5x3NNuL+/LT9nAgn+HJJuW18RjwZrkvNK/DnFy2d37LVJnAd46HtYOTuoO8E5qKFvGbTiQczeahBJphYsQTxufqa3Lz+M/Q135bK5Iysz4VuV
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(48565401081)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:VI1PR0801MB1293;
x-ms-traffictypediagnostic: VI1PR0801MB1293:
x-microsoft-antispam-prvs: <VI1PR0801MB1293E9D95C51BFFFA1C578E1FA9A0@VI1PR0801MB1293.eurprd08.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(10201501046)(3002001)(93006095)(93001095)(3231254)(944501410)(52105095)(6055026)(149027)(150027)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123564045)(20161123558120)(20161123562045)(6072148)(201708071742011); SRVR:VI1PR0801MB1293; BCL:0; PCL:0; RULEID:; SRVR:VI1PR0801MB1293;
x-forefront-prvs: 0666E15D35
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(346002)(366004)(39380400002)(396003)(376002)(189003)(199004)(40434004)(377424004)(13464003)(110136005)(66066001)(55016002)(54906003)(25786009)(478600001)(53936002)(9686003)(476003)(2906002)(6246003)(486006)(4326008)(102836004)(72206003)(74316002)(3280700002)(86362001)(68736007)(59450400001)(316002)(3660700001)(105586002)(6506007)(26005)(53546011)(6116002)(8676002)(93886005)(3846002)(76176011)(7736002)(7696005)(33656002)(99286004)(8936002)(305945005)(5250100002)(446003)(229853002)(186003)(5660300001)(14454004)(106356001)(5890100001)(81166006)(97736004)(2501003)(81156014)(11346002)(6436002)(2900100001); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR0801MB1293; H:VI1PR0801MB2112.eurprd08.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: arm.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: CNIBDYp6q8atOu72Tva0cXhjzeNLW6V50TDBuwKEjrijIw2qoo1CbjQHLnli7BSZpZBMiBqAYpr+N1ZwTN4v3Sv2Cfy8YXq4nJNpgrM+RV+azvX5pqZMAK6jhHsZwfzzIHjia1eys7uPN634GdcWUkczRy2zitA7490/uxPH1TEeYhl1HEOrb5Zp/IvuKE/g
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: e46ff2b6-2be2-4357-0d75-08d5b4d5b1c3
X-OriginatorOrg: arm.com
X-MS-Exchange-CrossTenant-Network-Message-Id: e46ff2b6-2be2-4357-0d75-08d5b4d5b1c3
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 May 2018 11:20:24.5083 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: f34e5979-57d9-4aaa-ad4d-b122a662184d
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0801MB1293
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/JwKdzADW67rJIsSjiN66kQQtAVc>
Subject: Re: [core] Conclusion -- Endpoint Client Name / Endpoint Name in RD draft
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 May 2018 11:20:34 -0000

Peter,

I would personally feel more comfortable if we standardize functionality that some people have gained some experience already. If we don't involve the domain experts then we will most likely get it wrong.

What about separating this functionality from the RD draft, reach out to these companies, and then put the result of the investigations into a separate document? There are some folks in the group who work closely with indoor commercial lighting companies and they could for sure help.

Ciao
Hannes


-----Original Message-----
From: peter van der Stok [mailto:stokcons@xs4all.nl]
Sent: 08 May 2018 08:22
To: Kovatsch, Matthias
Cc: Hannes Tschofenig; Mohit Sethi; core@ietf.org
Subject: Re: [core] Conclusion -- Endpoint Client Name / Endpoint Name in RD draft

Kovatsch, Matthias schreef op 2018-05-07 18:09:
> Dear Hannes,
>
> dear list
>
> To my knowledge, third-party provisioning functionality is in
> particular used for lighting systems; maybe Peter can comment on this.

On request, some background.
For buildings, the installation is done by installation companies with their own tools and procedures.
Installation can be done in phases by different companies.
Their is at this moment not one general approach or installation protocol.

The problem is that the architect and people around have produced drawings with cabling and equipment situated at precise physical locations in the drawing.
Equipment, cabling etc are identified with numbers ,names, what have you.
There are descriptions which discuss the functionality and the relation between the equipment.
All this knowledge has to be transferred to the equipment without making too many "one of a kind" pieces.
In he "olde times" much was solved by the cabling, that limited the control possibilities.
These IP times, anything can reach anything else.
One approach is to store parts of this information into the RD, which can be queried by the equipment.

I hope this make the wish for an RD with third party access understandable.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

v2.23.0 | Report a Bug | By Email