Re: [TLS] New Liaison Statement, "Liaison to SG17"

"Yang, Xiaoya" <> Sat, 29 June 2019 07:17 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 133B4120969; Sat, 29 Jun 2019 00:17:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.926
X-Spam-Status: No, score=-3.926 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DEAR_SOMETHING=1.973, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.999, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id bqJ2cbVUo2mT; Sat, 29 Jun 2019 00:16:57 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 46A621200E6; Sat, 29 Jun 2019 00:16:56 -0700 (PDT)
Received: from TUCM04.TUECSP.UNICC.ORG (unknown []) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6A5C84000F; Sat, 29 Jun 2019 07:16:54 +0000 (UTC)
Received: from TUCM02.TUECSP.UNICC.ORG ( by TUCM04.TUECSP.UNICC.ORG ( with Microsoft SMTP Server (TLS) id 15.0.1395.4; Sat, 29 Jun 2019 07:16:53 +0000
Received: from TUCM02.TUECSP.UNICC.ORG ([]) by TUCM02.TUECSP.UNICC.ORG ([]) with mapi id 15.00.1395.000; Sat, 29 Jun 2019 07:16:53 +0000
From: "Yang, Xiaoya" <>
To: Liaison Statement Management Tool <>, "TSB SG17 Secretariat, ITU" <>
CC: Transport Layer Security Discussion List <>, "" <>, Scott Mansfield <>, "" <>, Sean Turner <>, "Benjamin Kaduk" <>, Christopher Wood <>, Joseph Salowey <>, Roman Danyliw <>, "" <>, "" <>
Thread-Topic: New Liaison Statement, "Liaison to SG17"
Thread-Index: AQHVLfoaQv78uXCe7EiOmRLIMf9cgqayOUxV
Date: Sat, 29 Jun 2019 07:16:53 +0000
Message-ID: <0867b98372a844029fb18d576ccdef73@TUCM02.TUECSP.UNICC.ORG>
References: <>
In-Reply-To: <>
Accept-Language: en-GB, en-US
Content-Language: en-GB
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: multipart/alternative; boundary="_000_0867b98372a844029fb18d576ccdef73TUCM02TUECSPUNICCORG_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [TLS] New Liaison Statement, "Liaison to SG17"
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 29 Jun 2019 07:17:01 -0000

Dear Sir/Madame,

This IETF liaison is received by SG17 with appreciation.

Sent from my Samsung Galaxy smartphone.

-------- Original message --------
From: Liaison Statement Management Tool <>
Date: 6/28/19 23:40 (GMT+01:00)
To: "TSB SG17 Secretariat, ITU" <>
Cc: Transport Layer Security Discussion List <>rg>, "Yang, Xiaoya" <>nt>,, Scott Mansfield <>om>,, Sean Turner <>om>, Benjamin Kaduk <>du>, Christopher Wood <>et>, Joseph Salowey <>et>, Roman Danyliw <>rg>,,,,
Subject: New Liaison Statement, "Liaison to SG17"

Title: Liaison to SG17
Submission Date: 2019-06-28
URL of the IETF Web page:

From: Christopher Wood <>
Cc: Transport Layer Security Discussion List <>,Scott Mansfield <>,Sean Turner <>,Benjamin Kaduk <>,Christopher Wood <>,Joseph Salowey <>,Roman Danyliw <>,,,Benjamin Kaduk,Eric Resorla
Response Contacts: Christopher Wood <>,Joseph Salowey <>,Sean Turner <>
Technical Contacts:, ,
Purpose: For information

Referenced liaison: LS on SG17 work item X.ibc-iot: Security framework for using Identity Based Cryptography for IoT services over telecom networks (

Body: Thank you for the LS concerning SG17’s work item X.ibc-iot [1].  As you are no doubt aware, the TLS WG and the IANA TLS Designated Experts worked with the X.ibc-iot authors, who also are authors of draft-wang-tls-raw-public-key-with-ibc [2], to register four TLS Signature Schemes: eccsi_sha256, ibs1_sha256, ibs2_sha256, sm9_ibs_sm3.  These values can be found in the IANA TLS Signature Scheme registry [3].

We would like to thank those authors for working through the IETF process by 1) modifying their draft to add ibs1_sha256, ibs2_sha256, and sm9_ibs_sm3 so that all of the requested values from X.ibc-iot were included, 2) presenting their draft to the TLS WG at IETF 104, 3) resolving comments from the WG and the Designated Experts, and 4) for their patience throughout this process.




No document has been attached