Re: [lamps] Need SHAKE text strings, add to draft-ietf-lamps-pkix-shake?

"Panos Kampanakis (pkampana)" <pkampana@cisco.com> Thu, 04 April 2019 14:50 UTC

Return-Path: <pkampana@cisco.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E60BF1204AD for <spasm@ietfa.amsl.com>; Thu, 4 Apr 2019 07:50:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=TCne3urV; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=XXIA912L
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 vTxzchvuKk7z for <spasm@ietfa.amsl.com>; Thu, 4 Apr 2019 07:50:08 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 682661206A5 for <spasm@ietf.org>; Thu, 4 Apr 2019 07:50:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2858; q=dns/txt; s=iport; t=1554389408; x=1555599008; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=HtlmM/5zpTg4vNt9g4gFDycguZ5FCLEvfwA15rIoIXo=; b=TCne3urVTgvsRqI6ZBg/9Ah2EDBFAhhhCh5QtGEpk8RVIig9TRE6LIPp otO+KE94sUpIU3ANI4F8VbAZXysjhYqG52areJC1F8jQL8ZRn/aW1IyfJ eLriAm5Rday4gljthqcl4lHsEaosuhHXoBK8U8V20UbTVEPMX3yuDn0kl 0=;
IronPort-PHdr: =?us-ascii?q?9a23=3AN0ANrh8QIkZacP9uRHGN82YQeigqvan1NQcJ65?= =?us-ascii?q?0hzqhDabmn44+8ZR7E/fs4iljPUM2b8P9Ch+fM+4HYEW0bqdfk0jgZdYBUER?= =?us-ascii?q?oMiMEYhQslVdaGAEjjJfjjRyc7B89FElRi+iLzPA=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0A1AAAdGaZc/5pdJa1bChoBAQEBAQI?= =?us-ascii?q?BAQEBBwIBAQEBgVQCAQEBAQsBgT1QA2hUIAQLJ4QOg0cDjyKCV5cVglIDVA4?= =?us-ascii?q?BARgNB4RAAheFNiI3Bg0BAQMBAQkBAwJtHAyFSgEBAQECAQEBIREMAQEsDAQ?= =?us-ascii?q?HBAIBCBEEAQEDAiYCAgIlCxUICAIEARIIgxuBXQMNCAEOonICihRxgS+CeQE?= =?us-ascii?q?BBYUKGIIMAwWBCyUBizIXgUA/gRFGgh4uPoJhAQECgTQtFYJzMYImilmCNYR?= =?us-ascii?q?HlBgJAod+jBSCBYlwiFqIJoMpgRiFBI1UAgQCBAUCDgEBBYFlIoFWcBU7gmy?= =?us-ascii?q?CCgsBF4NMgX+DFYU/cgELgRyPPQEB?=
X-IronPort-AV: E=Sophos;i="5.60,308,1549929600"; d="scan'208";a="253825552"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 04 Apr 2019 14:50:06 +0000
Received: from XCH-ALN-004.cisco.com (xch-aln-004.cisco.com [173.36.7.14]) by rcdn-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id x34Eo6Hr017273 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 4 Apr 2019 14:50:06 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-ALN-004.cisco.com (173.36.7.14) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 4 Apr 2019 09:50:05 -0500
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 4 Apr 2019 10:50:04 -0400
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 4 Apr 2019 10:50:04 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector1-cisco-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=HtlmM/5zpTg4vNt9g4gFDycguZ5FCLEvfwA15rIoIXo=; b=XXIA912Le1s1nOHzdsoJJ12u5jey1HAatwmXF+lvp8Ejcj+iIJV1WdPCPg/jX0+DR09Ui8c0h7fh2HenUOcpNlbuavb70LFxWSXuYblEm/GBKK2hINwnukQxJjIfDFzMSaVFdQU7kjqvbqpKXb93j6kz+ohWex57wi6PQ/Lao4A=
Received: from CY4PR11MB1527.namprd11.prod.outlook.com (10.172.70.18) by CY4PR11MB1335.namprd11.prod.outlook.com (10.169.252.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1750.19; Thu, 4 Apr 2019 14:50:03 +0000
Received: from CY4PR11MB1527.namprd11.prod.outlook.com ([fe80::11b1:a7a0:b5b8:bef]) by CY4PR11MB1527.namprd11.prod.outlook.com ([fe80::11b1:a7a0:b5b8:bef%8]) with mapi id 15.20.1771.016; Thu, 4 Apr 2019 14:50:03 +0000
From: "Panos Kampanakis (pkampana)" <pkampana@cisco.com>
To: Sean Leonard <dev+ietf@seantek.com>, SPASM <spasm@ietf.org>
Thread-Topic: [lamps] Need SHAKE text strings, add to draft-ietf-lamps-pkix-shake?
Thread-Index: AQHU6qHeoogdjLzcwEaYbIaaJw/Dc6YsBXQg
Date: Thu, 4 Apr 2019 14:50:03 +0000
Message-ID: <CY4PR11MB1527156AE6031586C8BBE93DC9500@CY4PR11MB1527.namprd11.prod.outlook.com>
References: <0d9b3a03-e20a-4daa-166a-4ef2cbeeba83@seantek.com>
In-Reply-To: <0d9b3a03-e20a-4daa-166a-4ef2cbeeba83@seantek.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=pkampana@cisco.com;
x-originating-ip: [2001:420:c0c4:1007::244]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 0a934576-c84c-4d42-0c02-08d6b90cd23b
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600139)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:CY4PR11MB1335;
x-ms-traffictypediagnostic: CY4PR11MB1335:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <CY4PR11MB1335014B96606D03FC4D9309C9500@CY4PR11MB1335.namprd11.prod.outlook.com>
x-forefront-prvs: 0997523C40
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(396003)(136003)(376002)(346002)(39860400002)(13464003)(199004)(189003)(8936002)(99286004)(52536014)(5660300002)(316002)(6436002)(33656002)(102836004)(476003)(14444005)(7736002)(446003)(110136005)(6506007)(305945005)(186003)(229853002)(106356001)(53546011)(11346002)(25786009)(105586002)(256004)(7696005)(486006)(46003)(966005)(71200400001)(76176011)(9686003)(55016002)(68736007)(8676002)(74316002)(2906002)(81156014)(478600001)(86362001)(97736004)(53936002)(71190400001)(6116002)(6306002)(14454004)(6246003)(81166006); DIR:OUT; SFP:1101; SCL:1; SRVR:CY4PR11MB1335; H:CY4PR11MB1527.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: aLgoUqiLNW4XRlDU7SBFBPHFL2aXXhjyqEuddpKZOBXBFC62hVZvQciHvwQe+1+SkbgsLLIPRqXAqub+mRYg0zkrNILBZxOWepCHaZ56posNwgmWPRx9kPj5FJMYg4EdvTc0A/mgp5H9olLkhDoRIICE4b5xPx8lhlGCC4nMUuCEf2WAA0l0/Ej1wzpMApyYj/YADTYEPujhpSSzK1CQcriT+7Wq9uunf0aF9Xt30FXKpV2a0DIYpoydZXvtaMmLx5kiwcZSAr4DW4ElUf5n9qSImikkOhww6HCySwrwrf45E6HLExfuQdarkTO8pLel2yR0+rwGhAJMTFO2BZqhHSLvyChYzvuEdOhQzX/ITioIAMZGlxcRK7esYZYX1H7LY4I9yfBEabGyy46ZVwsdk5SnAGY6Vb/UfGBqIVQ2/4E=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 0a934576-c84c-4d42-0c02-08d6b90cd23b
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Apr 2019 14:50:03.5213 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR11MB1335
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.14, xch-aln-004.cisco.com
X-Outbound-Node: rcdn-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/IcnoMq2kX-zsLZR9PkMumnwrG0Y>
Subject: Re: [lamps] Need SHAKE text strings, add to draft-ietf-lamps-pkix-shake?
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Apr 2019 14:50:12 -0000

Hi Sean,

> I have a need to identify SHAKE128 and SHAKE256 algorithms by text strings. 

The OIDs for SHAKEs are defined by NIST https://csrc.nist.gov/projects/computer-security-objects-register/algorithm-registration#Hash That, along with the new OIDs in the draft-ietf-lamps-pkix-shake draft, are enough for introducing SHAKEs in X.509 which is what this draft is doing. 

Does your need relate to PKIX at all? 

Rgs,
Panos


-----Original Message-----
From: Spasm <spasm-bounces@ietf.org> On Behalf Of Sean Leonard
Sent: Thursday, April 04, 2019 12:48 AM
To: SPASM <spasm@ietf.org>
Subject: [lamps] Need SHAKE text strings, add to draft-ietf-lamps-pkix-shake?

I have a need to identify SHAKE128 and SHAKE256 algorithms by text strings.

There is an IANA registry aptly named “Hash Function Textual Names”: 
<https://www.iana.org/assignments/hash-function-text-names/hash-function-text-names.xhtml>.

I request the following change to draft-ietf-lamps-pkix-shake:

Change 6. IANA Considerations to read:

~~~

    IANA is directed to update the Hash Function Textual Names
    registry [RFC8122] with two additional entries for SHAKE128
    and SHAKE256. Table 1 contains the new values of this registry.

        +--------------------+-------------------------+-----------+
        | Hash Function Name |          OID            | Reference |
        +--------------------+-------------------------+-----------+
        |     "shake256"     | 2.16.840.1.101.3.4.2.11 |  [THIS]   |
        |     "shake512"     | 2.16.840.1.101.3.4.2.12 |  [THIS]   |
        +--------------------+-------------------------+-----------+


             Table 1: IANA Hash Function Textual Names Registry


~~~

Furthermore, RFC 8122 says that the registering Standards Track RFC has to update RFC 3279. So, the status of draft-ietf-lamps-pkix-shake is supposed to be changed to Updates: RFC 3279.

Thank you,

Sean

_______________________________________________
Spasm mailing list
Spasm@ietf.org
https://www.ietf.org/mailman/listinfo/spasm