Re: [core] Endpoint Client Name / Endpoint Name in RD draft
Hannes Tschofenig <Hannes.Tschofenig@arm.com> Wed, 04 April 2018 19:02 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 45C0512D952 for <core@ietfa.amsl.com>; Wed, 4 Apr 2018 12:02:12 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 7tO_XfzNA6g2 for <core@ietfa.amsl.com>; Wed, 4 Apr 2018 12:02:09 -0700 (PDT)
Received: from EUR02-HE1-obe.outbound.protection.outlook.com (mail-eopbgr10079.outbound.protection.outlook.com [40.107.1.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 8AAD412E8F1 for <core@ietf.org>; Wed, 4 Apr 2018 12:01:39 -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=EAVaG4CfjTUe35lbIeSkHLVKlwPtHlUxRxrMmFro33Q=; b=JGxBPysyjJle1mBX9rTgXpc/X6MgB16QxjEaqmexE5Ub5Mq3K5VO3jILIUe5Pg282nhLgi6J0T3WIjK1PPWnq2sz40syd1SStpM+FwiVr+d0DbJ9Suu7E3+Svnvhzf4mEb1APv6w7YkHpPaBn66syFTFEKY0E0fkxIvpOJVQXhM=
Received: from VI1PR0801MB2112.eurprd08.prod.outlook.com (10.173.75.16) by VI1PR0801MB1727.eurprd08.prod.outlook.com (10.168.67.17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.653.12; Wed, 4 Apr 2018 19:01:29 +0000
Received: from VI1PR0801MB2112.eurprd08.prod.outlook.com ([fe80::64d4:b973:bf81:cfbf]) by VI1PR0801MB2112.eurprd08.prod.outlook.com ([fe80::64d4:b973:bf81:cfbf%18]) with mapi id 15.20.0631.013; Wed, 4 Apr 2018 19:01:29 +0000
From: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
To: Jim Schaad <ietf@augustcellars.com>, 'Jaime Jiménez' <jaime.jimenez@ericsson.com>
CC: "core@ietf.org" <core@ietf.org>
Thread-Topic: [core] Endpoint Client Name / Endpoint Name in RD draft
Thread-Index: AdPMGk8Ajq5nOeuWRv+BrgbskCDzwf//7S4A//+qDBCAALM9gP//8agg
Date: Wed, 04 Apr 2018 19:01:29 +0000
Message-ID: <VI1PR0801MB2112FB25797DCB8F546C148DFAA40@VI1PR0801MB2112.eurprd08.prod.outlook.com>
References: <VI1PR0801MB2112B52094B182F5D44C4F64FAA40@VI1PR0801MB2112.eurprd08.prod.outlook.com> <A484D917-677C-4B29-BBAD-DDDE34B50303@ericsson.com> <VI1PR0801MB21128EA2B70DEEE7C5775A62FAA40@VI1PR0801MB2112.eurprd08.prod.outlook.com> <070801d3cc3f$8d59e0c0$a80da240$@augustcellars.com>
In-Reply-To: <070801d3cc3f$8d59e0c0$a80da240$@augustcellars.com>
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: [194.136.97.66]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; VI1PR0801MB1727; 7:dENgOH8OMUraYNg48QUIGRr0ENcag9l4Ey4DSdh6K5OeGaRjdYDy/UOIp2/FyiQ/vH1U29OKvqxHlGKgabJePGZgXPZZH4ZMnDPS+akn3WpRk897qH5KppJITfNPDwd4jWC8c5fjld3fZcVZnrUQ/2qHaChJB3xYtGaQ1sgJVVdoTT7Nlm+foDkDsPmRYT7y5GHNN6ZprUeF+wsHUzQSz+XITEODyZV48w0nHGe9B1ru2xj8crVN8dFHTmorVuzF
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 98d9a1b3-e46e-410c-e95d-08d59a5e796d
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4604075)(3008032)(48565401081)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:VI1PR0801MB1727;
x-ms-traffictypediagnostic: VI1PR0801MB1727:
x-microsoft-antispam-prvs: <VI1PR0801MB172760D7A947600EF1513B61FAA40@VI1PR0801MB1727.eurprd08.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(37575265505322)(28532068793085)(180628864354917)(192374486261705)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(3231221)(944501327)(52105095)(93006095)(93001095)(3002001)(10201501046)(6055026)(6041310)(20161123562045)(20161123560045)(20161123564045)(20161123558120)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011); SRVR:VI1PR0801MB1727; BCL:0; PCL:0; RULEID:; SRVR:VI1PR0801MB1727;
x-forefront-prvs: 0632519F33
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(396003)(39380400002)(376002)(346002)(366004)(53754006)(189003)(199004)(40434004)(478600001)(105586002)(72206003)(3846002)(3660700001)(59450400001)(790700001)(66066001)(53546011)(229853002)(6116002)(33656002)(6506007)(966005)(2900100001)(110136005)(476003)(7696005)(606006)(7736002)(486006)(5660300001)(2906002)(97736004)(81156014)(76176011)(25786009)(3280700002)(74316002)(8936002)(5890100001)(86362001)(55016002)(102836004)(5250100002)(106356001)(81166006)(186003)(26005)(9326002)(446003)(99286004)(316002)(93886005)(14454004)(6436002)(4326008)(11346002)(68736007)(54896002)(9686003)(236005)(53936002)(6306002)(6246003)(8676002); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR0801MB1727; 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: FN+Yz2Ia7bwcboQnNHPcTXtnQLDCc34k0RQOlubFjvIrIj193rnPsfXZreXHBbkMGtJC24s3kUn5W8DYsTySHvdlz7yQ1BkjJJKrzMUZmT0Zsh0Vbl5ZMJpdxF/8VPwqwa3v1Z3wXNrkz6aHTAMFc8vY12WdDEbGTI56aAh+mkmEFBEhLHBazVi97tZPQYHOcS7iv0n5pDRrJ2cTu5lettt8zNWH7YRfW6LZXAWyjz3hlMjoFc2Xh1wUSkqghOWXz2L1pAaXKa0/0fhU4HUmk8fv8t2qW0VPyr36kNWth8FW8QJyuWJoGzIuGHu9xIwHzCxieHxYTU2cKDPEuEZyi+4OVMdOKNcb5WK/yr9a+NHw8jBZboXcoErPRTIHxfvoRjv/4MsDE3tuaifnSooJXXSuVSDT8M/sXpDRz7aq1QM=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_VI1PR0801MB2112FB25797DCB8F546C148DFAA40VI1PR0801MB2112_"
MIME-Version: 1.0
X-OriginatorOrg: arm.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 98d9a1b3-e46e-410c-e95d-08d59a5e796d
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Apr 2018 19:01:29.6549 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: f34e5979-57d9-4aaa-ad4d-b122a662184d
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0801MB1727
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/kNGJgkIQF7ZqXLYJFNq4LGXuBs0>
Subject: Re: [core] 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: Wed, 04 Apr 2018 19:02:12 -0000
Hi Jim, I had various comments: First, I argue that the LwM2M spec and the RD draft should be in sync regarding the name of the parameter. Second, I believe that the security consideration section is correct in the threat description but came to the wrong conclusion regarding the use of the parameter. In essence, the parameter should be optional and probably only used for debugging. Third, I went as far as saying that the endpoint name parameter should actually be removed altogether. I can already see how those deploying it will get it wrong and will introduce security problems. Ciao Hannes From: Jim Schaad [mailto:ietf@augustcellars.com] Sent: 04 April 2018 21:06 To: Hannes Tschofenig; 'Jaime Jiménez' Cc: core@ietf.org Subject: RE: [core] Endpoint Client Name / Endpoint Name in RD draft Hannes, I am not completely clear. Are you saying that the RD should not have the endpoint name parameter as a defined property or something else? Jim From: core <core-bounces@ietf.org<mailto:core-bounces@ietf.org>> On Behalf Of Hannes Tschofenig Sent: Wednesday, April 4, 2018 10:41 AM To: Jaime Jiménez <jaime.jimenez@ericsson.com<mailto:jaime.jimenez@ericsson.com>> Cc: core@ietf.org<mailto:core@ietf.org> WG <core@ietf.org<mailto:core@ietf.org>> Subject: Re: [core] Endpoint Client Name / Endpoint Name in RD draft Hi Jaime, using IP address and port for an endpoint (client) name would not be a good idea. In general, it was not a good idea to have this parameter defined in the first place. It might actually be better to remove it altogether. Ciao Hannes From: Jaime Jiménez [mailto:jaime.jimenez@ericsson.com] Sent: 04 April 2018 17:32 To: Hannes Tschofenig Cc: core@ietf.org<mailto:core@ietf.org> WG; Carsten Bormann Subject: Re: [core] Endpoint Client Name / Endpoint Name in RD draft Hi, Note that endpoint can refer to both source and destination, being and IP:port in its simplest form: https://tools.ietf.org/html/rfc7252#page-6 The fact that LWM2M swaps those role names might actually add to the confusion, probably OMA LWM2M should be the one changing the terminology as the device is mostly a “server” hosting resources and only is a “client” during bootstrapping and registration. We could have used terms like “servient” instead but it might be too late for that. Ciao! - - Jaime Jiménez On 4 Apr 2018, at 16.41, Hannes Tschofenig <Hannes.Tschofenig@arm.com<mailto:Hannes.Tschofenig@arm.com>> wrote: Hi all, I noticed that the term “endpoint name” is used in the IETF RD draft while the OMA LwM2M spec uses the term “endpoint client name”. Endpoint is a confusing term since it is used differently in the CoAP spec than in the Web environment. For this reason I believe it would be better to use the term “endpoint client name” also in the RD draft. This would improve alignment between the two specs. Ciao Hannes 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. _______________________________________________ core mailing list core@ietf.org<mailto:core@ietf.org> https://www.ietf.org/mailman/listinfo/core 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. 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.
- [core] Endpoint Client Name / Endpoint Name in RD… Hannes Tschofenig
- Re: [core] Endpoint Client Name / Endpoint Name i… Jaime Jiménez
- Re: [core] Endpoint Client Name / Endpoint Name i… Hannes Tschofenig
- Re: [core] Endpoint Client Name / Endpoint Name i… Jim Schaad
- Re: [core] Endpoint Client Name / Endpoint Name i… Hannes Tschofenig
- Re: [core] Endpoint Client Name / Endpoint Name i… Jaime Jiménez
- Re: [core] Endpoint Client Name / Endpoint Name i… Hannes Tschofenig
- Re: [core] Endpoint Client Name / Endpoint Name i… Jim Schaad
- Re: [core] Endpoint Client Name / Endpoint Name i… peter van der Stok
- Re: [core] Endpoint Client Name / Endpoint Name i… Carsten Bormann
- Re: [core] Endpoint Client Name / Endpoint Name i… Christian Amsüss
- Re: [core] Endpoint Client Name / Endpoint Name i… Jim Schaad
- Re: [core] Endpoint Client Name / Endpoint Name i… Kovatsch, Matthias
- Re: [core] Endpoint Client Name / Endpoint Name i… Jim Schaad
- Re: [core] Endpoint Client Name / Endpoint Name i… Hannes Tschofenig
- Re: [core] Endpoint Client Name / Endpoint Name i… Hannes Tschofenig
- Re: [core] Endpoint Client Name / Endpoint Name i… Kovatsch, Matthias
- Re: [core] Endpoint Client Name / Endpoint Name i… peter van der Stok
- Re: [core] Endpoint Client Name / Endpoint Name i… peter van der Stok
- Re: [core] Endpoint Client Name / Endpoint Name i… Hannes Tschofenig
- Re: [core] Endpoint Client Name / Endpoint Name i… Hannes Tschofenig
- Re: [core] Endpoint Client Name / Endpoint Name i… peter van der Stok
- Re: [core] Endpoint Client Name / Endpoint Name i… Hannes Tschofenig
- Re: [core] Endpoint Client Name / Endpoint Name i… Kovatsch, Matthias
- Re: [core] Endpoint Client Name / Endpoint Name i… Hannes Tschofenig
- Re: [core] Endpoint Client Name / Endpoint Name i… peter van der Stok
- Re: [core] Endpoint Client Name / Endpoint Name i… Hannes Tschofenig