From nobody Tue Feb 28 03:22:20 2023 Return-Path: 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 60C98C15170B; Tue, 28 Feb 2023 03:22:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.112 X-Spam-Level: X-Spam-Status: No, score=-1.112 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, PDS_RDNS_DYNAMIC_FP=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_DYNAMIC=0.982, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=um.es Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JMA0mLp3911s; Tue, 28 Feb 2023 03:22:13 -0800 (PST) Received: from mx07-006a4e02.pphosted.com (mx07-006a4e02.pphosted.com [143.55.146.78]) (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 C2FF7C15171E; Tue, 28 Feb 2023 03:22:12 -0800 (PST) Received: from pps.filterd (m0316692.ppops.net [127.0.0.1]) by m0316692.ppops.net (8.17.1.19/8.17.1.19) with ESMTP id 31SBIjE5027462; Tue, 28 Feb 2023 12:22:10 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=um.es; h=from : content-type : mime-version : subject : date : references : cc : to : message-id; s=dkim3; bh=D/kyVlh+KYR3fQUx08Kdc3yvi77/+ZzrqfCO2SnqcCU=; b=B3pKpwzz/UR+rP1YojeJaekHGrlnFWlzQCyRe0oaTTvo0uuFbz7c70Qc+RxbjXe7QH3X OIf8WnHdfCTz3w+Y7/6+rB5TGRXqivyRozn0JmEeAtO5Pk/I6f9oM2mWjCvKXw9e3ir9 EJFd4LAKwudu9xy7zPu05koM2ul4ustQvrMSZmdg+gERM1Ki/MGH885e4OSWyQAAsRP9 IRH4VGGB+/sVNCYivNefbQwb85o32ZrugYExN9hEg3E+1fASLj+jMDO7He3E9yDOsjFA wmT8DYKOgyURQMQ4KL2xRAX69HeGGsKqPSAr8y2ziIkPAGFZv+eDW5Fcxw9JF8ssf+mO ig== Received: from xenon44.um.es (xenon44.um.es [155.54.212.171]) by m0316692.ppops.net (PPS) with ESMTP id 3nywyt8puj-1; Tue, 28 Feb 2023 12:22:10 +0100 Received: from localhost (localhost [127.0.0.1]) by xenon44.um.es (Postfix) with ESMTP id 7E7E51FF3F; Tue, 28 Feb 2023 12:22:09 +0100 (CET) X-Virus-Scanned: by antispam in UMU at xenon44.um.es Received: from xenon44.um.es ([127.0.0.1]) by localhost (xenon44.um.es [127.0.0.1]) (amavisd-new, port 10024) with LMTP id QYpDW9luEQ33; Tue, 28 Feb 2023 12:22:09 +0100 (CET) Received: from smtpclient.apple (inf-205-228.inf.um.es [155.54.205.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: rafa@um.es) by xenon44.um.es (Postfix) with ESMTPSA id 42BFC20171; Tue, 28 Feb 2023 12:22:06 +0100 (CET) From: Rafa Marin-Lopez Content-Type: multipart/alternative; boundary="Apple-Mail=_E0C2C1FE-B969-4F8C-B813-DDEC5EA8BFE4" Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.400.51.1.1\)) Date: Tue, 28 Feb 2023 12:21:56 +0100 References: <167756362118.37305.7488370234488588306@ietfa.amsl.com> Cc: Rafa Marin-Lopez , Gabriel Lopez , Laurent Toutain , Alex Fernandez , t2trg@irtf.org, i2nsf@ietf.org To: core@ietf.org Message-Id: <58401FDD-6114-48B4-B484-A0E81D52966F@um.es> X-Mailer: Apple Mail (2.3731.400.51.1.1) X-Proofpoint-GUID: rzrMu18qzAHQ_kCtj8k8kcswgTC3x8PZ X-Proofpoint-ORIG-GUID: rzrMu18qzAHQ_kCtj8k8kcswgTC3x8PZ X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.219,Aquarius:18.0.930,Hydra:6.0.562,FMLib:17.11.170.22 definitions=2023-02-28_06,2023-02-28_01,2023-02-09_01 X-Proofpoint-Spam-Details: rule=outbounddefault_notspam policy=outbounddefault score=0 lowpriorityscore=0 bulkscore=0 adultscore=0 priorityscore=1501 suspectscore=0 clxscore=1011 malwarescore=0 mlxlogscore=787 impostorscore=0 mlxscore=0 spamscore=0 phishscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2212070000 definitions=main-2302280091 Archived-At: Subject: [core] Fwd: New Version Notification for draft-marin-yang-edhoc-oscore-00.txt X-BeenThere: core@ietf.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Feb 2023 11:22:17 -0000 --Apple-Mail=_E0C2C1FE-B969-4F8C-B813-DDEC5EA8BFE4 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Dear all: We have just submitted an I-D that might be of interest of this WG. It = is inspired in the RFC 9061, but now for EDHOC and OSCORE.=20 The basic idea is to configure, from a centralized controller (e.g SDN = controller), certain parameters in EDHOC or OSCORE that allow to protect = Thing-to-Thing CoAP communication or between a Thing and a non-so = constrained node. This configuration can be carried out by using = CORECONF.=20 Any comment is welcome. Best Regards. > Inicio del mensaje reenviado: >=20 > De: internet-drafts@ietf.org > Asunto: New Version Notification for = draft-marin-yang-edhoc-oscore-00.txt > Fecha: 28 de febrero de 2023, 6:53:41 CET > Para: "Alex Fernandez" = , "Gabriel = Lopez-Millan" , "Laurent Toutain" = , "Rafa Marin-Lopez" , = "Rafael Marin-Lopez" >=20 >=20 > A new version of I-D, draft-marin-yang-edhoc-oscore-00.txt > has been successfully submitted by Rafa Marin-Lopez and posted to the > IETF repository. >=20 > Name: draft-marin-yang-edhoc-oscore > Revision: 00 > Title: A YANG data model for SDN-based key management = with EDHOC and OSCORE > Document date: 2023-02-28 > Group: Individual Submission > Pages: 43 > URL: = https://urldefense.com/v3/__https://www.ietf.org/archive/id/draft-marin-ya= ng-edhoc-oscore-00.txt__;!!D9dNQwwGXtA!XfBqZHN-41hQ8oty5hgpehvcuW4-mQHFMJt= Rz_tJ5gcpA5siCU1193cxUDC5YM3aRGE7c24M65NTSwCYd5qq$=20 > Status: = https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-marin-y= ang-edhoc-oscore/__;!!D9dNQwwGXtA!XfBqZHN-41hQ8oty5hgpehvcuW4-mQHFMJtRz_tJ= 5gcpA5siCU1193cxUDC5YM3aRGE7c24M65NTS2O2-ims$=20 > Html: = https://urldefense.com/v3/__https://www.ietf.org/archive/id/draft-marin-ya= ng-edhoc-oscore-00.html__;!!D9dNQwwGXtA!XfBqZHN-41hQ8oty5hgpehvcuW4-mQHFMJ= tRz_tJ5gcpA5siCU1193cxUDC5YM3aRGE7c24M65NTS2ENiHCj$=20 > Htmlized: = https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draft-ma= rin-yang-edhoc-oscore__;!!D9dNQwwGXtA!XfBqZHN-41hQ8oty5hgpehvcuW4-mQHFMJtR= z_tJ5gcpA5siCU1193cxUDC5YM3aRGE7c24M65NTSwW3o6T4$=20 >=20 >=20 > Abstract: > This document defines YANG data models which allow a = Software-Defined > Networking (SDN) Controller (Controller) using NETCONF, RESTCONF or > CORECONF to provide configuration and monitoring Internet-of-Things > devices (Things) that support Ephemeral Diffie-Hellman Over COSE > (EDHOC) and/or OSCORE. In particular, a YANG data model defines the > required configuration parameters to perform EDHOC between two = Things > (EDHOC case). Another YANG data model is to configure the OSCORE > contexts directly into the Thing (OSCORE case). The service > described in this document allows the configuration and monitoring = of > Things that supports EDHOC and OSCORE or only OSCORE by allowing a > protected Thing-to-Thing communication based on CoAP. >=20 > This document focuses on providing YANG data models for configuring > EDHOC or OSCORE. This allows OSCORE establishment with minimal > intervention by the network administrator. >=20 >=20 >=20 >=20 > The IETF Secretariat >=20 >=20 ------------------------------------------------------- Rafa Marin-Lopez, PhD Dept. Information and Communications Engineering (DIIC) Faculty of Computer Science-University of Murcia 30100 Murcia - Spain Telf: +34868888501 Fax: +34868884151 e-mail: rafa@um.es ------------------------------------------------------- --Apple-Mail=_E0C2C1FE-B969-4F8C-B813-DDEC5EA8BFE4 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
Dear all:

We have = just submitted an I-D that might be of interest of this WG. It is inspired = in the RFC 9061, but now for EDHOC and = OSCORE. 

The basic idea is to configure, from a centralized = controller (e.g SDN controller), certain parameters in EDHOC or OSCORE = that allow to protect Thing-to-Thing CoAP communication or between a = Thing and a non-so constrained node. This configuration can be carried = out by using CORECONF. 

Any comment is welcome.

Best Regards.

Inicio del mensaje reenviado:

De: internet-drafts@ietf.org
Asunto: New = Version Notification for = draft-marin-yang-edhoc-oscore-00.txt
Fecha: 28 de = febrero de 2023, 6:53:41 CET
Para: "Alex Fernandez" = <javier-alejandro.fernandez-cordova@imt-atlantique.net>, "Gabriel = Lopez-Millan" <gabilm@um.es>, "Laurent Toutain" = <laurent.toutain@imt-atlantique.fr>, "Rafa Marin-Lopez" = <rafa@um.es>, "Rafael Marin-Lopez" = <rafa@um.es>


A new version of = I-D, draft-marin-yang-edhoc-oscore-00.txt
has been successfully = submitted by Rafa Marin-Lopez and posted to the
IETF = repository.

Name: = draft-marin-yang-edhoc-oscore
Revision: = 00
Title: A YANG data model for SDN-based = key management with EDHOC and OSCORE
Document date: = 2023-02-28
Group: Individual = Submission
Pages: 43
URL: =            https://= urldefense.com/v3/__https://www.ietf.org/archive/id/draft-marin-yang-edhoc= -oscore-00.txt__;!!D9dNQwwGXtA!XfBqZHN-41hQ8oty5hgpehvcuW4-mQHFMJtRz_tJ5gc= pA5siCU1193cxUDC5YM3aRGE7c24M65NTSwCYd5qq$
Status: =         https://urldefense.com/v3/= __https://datatracker.ietf.org/doc/draft-marin-yang-edhoc-oscore/__;!!D9dN= QwwGXtA!XfBqZHN-41hQ8oty5hgpehvcuW4-mQHFMJtRz_tJ5gcpA5siCU1193cxUDC5YM3aRG= E7c24M65NTS2O2-ims$
Html: =           https://urldef= ense.com/v3/__https://www.ietf.org/archive/id/draft-marin-yang-edhoc-oscor= e-00.html__;!!D9dNQwwGXtA!XfBqZHN-41hQ8oty5hgpehvcuW4-mQHFMJtRz_tJ5gcpA5si= CU1193cxUDC5YM3aRGE7c24M65NTS2ENiHCj$
Htmlized: =       https://urldefense.com/v3/__https://da= tatracker.ietf.org/doc/html/draft-marin-yang-edhoc-oscore__;!!D9dNQwwGXtA!= XfBqZHN-41hQ8oty5hgpehvcuW4-mQHFMJtRz_tJ5gcpA5siCU1193cxUDC5YM3aRGE7c24M65= NTSwW3o6T4$


Abstract:
  This document defines = YANG data models which allow a Software-Defined
=   Networking (SDN) Controller (Controller) using NETCONF, = RESTCONF or
  CORECONF to provide configuration and = monitoring Internet-of-Things
  devices (Things) that = support Ephemeral Diffie-Hellman Over COSE
  (EDHOC) = and/or OSCORE.  In particular, a YANG data model defines the
=   required configuration parameters to perform EDHOC between = two Things
  (EDHOC case).  Another YANG data model = is to configure the OSCORE
  contexts directly into the = Thing (OSCORE case).  The service
  described in this = document allows the configuration and monitoring of
=   Things that supports EDHOC and OSCORE or only OSCORE by = allowing a
  protected Thing-to-Thing communication based = on CoAP.

  This document focuses on providing YANG = data models for configuring
  EDHOC or OSCORE.  This = allows OSCORE establishment with minimal
  intervention by = the network administrator.




The IETF = Secretariat



-------------------------------------------------------
Rafa = Marin-Lopez, PhD
Dept. Information = and Communications Engineering (DIIC)
Faculty of = Computer Science-University of Murcia
30100 Murcia - = Spain
Telf: +34868888501 Fax: +34868884151 = e-mail: rafa@um.es
-----------------------------------------------= --------




= --Apple-Mail=_E0C2C1FE-B969-4F8C-B813-DDEC5EA8BFE4--