Re: [lamps] Interest to standardize PKI REST APIs?

"Salz, Rich" <rsalz@akamai.com> Mon, 10 June 2019 15:04 UTC

Return-Path: <rsalz@akamai.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 87E581201B5 for <spasm@ietfa.amsl.com>; Mon, 10 Jun 2019 08:04:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.71
X-Spam-Level:
X-Spam-Status: No, score=-2.71 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_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.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 ErouE-0QoxJc for <spasm@ietfa.amsl.com>; Mon, 10 Jun 2019 08:04:02 -0700 (PDT)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (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 AABE61201B0 for <spasm@ietf.org>; Mon, 10 Jun 2019 08:04:02 -0700 (PDT)
Received: from pps.filterd (m0122332.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x5AF41M4024301; Mon, 10 Jun 2019 16:04:01 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=cQ3nHfrSmBZvb6y1Bk7l3ky10t7IaBkN3WW0GkuoLk0=; b=EtLKPoott8gaXCQRo7slNJkYmVvzbFViGPmAHmV/IAM3u9v3cS1T3HFTOrR1xmfKBa6S dwiR8N0+2LqZG1RXB9eIrRVODm7vihUDB2DnHtWES9/Ups+X2hwl++AeIq7q3pWkZEv7 KQN34rN5Dnm65IWJRDBtLc3JIJ6vMNDGmKLKER9f2Ey7spkPR8yugsOforx/XoIhU4Ck +alQpZNEzRAEqy7doWH5pqdJtSKo+qXc+U125F1+IX64W9ntzGebbRj4+aKnxo0cDtAC VZsBRsQTyYy0yZKWnKBTHVxi77MVo3VabDt1gmhqHfuNtTVDGoid5TqTS9HsdSsde8Eg Bg==
Received: from prod-mail-ppoint1 (prod-mail-ppoint1.akamai.com [184.51.33.18] (may be forged)) by mx0a-00190b01.pphosted.com with ESMTP id 2t1q0m0e3h-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 10 Jun 2019 16:04:01 +0100
Received: from pps.filterd (prod-mail-ppoint1.akamai.com [127.0.0.1]) by prod-mail-ppoint1.akamai.com (8.16.0.27/8.16.0.27) with SMTP id x5AF3UtX002539; Mon, 10 Jun 2019 11:04:00 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.34]) by prod-mail-ppoint1.akamai.com with ESMTP id 2t08bvxx3n-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 10 Jun 2019 11:04:00 -0400
Received: from USMA1EX-DAG1MB3.msg.corp.akamai.com (172.27.123.103) by usma1ex-dag1mb2.msg.corp.akamai.com (172.27.123.102) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 10 Jun 2019 11:03:59 -0400
Received: from USMA1EX-DAG1MB3.msg.corp.akamai.com ([::1]) by usma1ex-dag1mb3.msg.corp.akamai.com ([fe80::9049:d725:bf4b:d545%18]) with mapi id 15.00.1473.003; Mon, 10 Jun 2019 11:03:59 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Tomas Gustavsson <tomas.gustavsson@primekey.com>, "spasm@ietf.org" <spasm@ietf.org>
Thread-Topic: [lamps] Interest to standardize PKI REST APIs?
Thread-Index: AQHVGHCubVVgCDqctkmtGReH7tQ+IaaQvXOAgAAr9ACAAu2wAIAABAyAgADTYICAACuTgIAAZr+A///JvwA=
Date: Mon, 10 Jun 2019 15:03:58 +0000
Message-ID: <9E9CA336-DBCC-4625-86D2-44655AEB5721@akamai.com>
References: <AM0PR10MB24028210BCE560C64195A74EFE320@AM0PR10MB2402.EURPRD10.PROD.OUTLOOK.COM> <AM0PR10MB2402B5BB06E4FB59A8ECB16BFE060@AM0PR10MB2402.EURPRD10.PROD.OUTLOOK.COM> <AM0PR10MB2402C7C1AAA09EABF047F0CEFE1D0@AM0PR10MB2402.EURPRD10.PROD.OUTLOOK.COM> <29FAEBF1-2D67-469F-BE78-AF58F78D055E@vigilsec.com> <BN7PR11MB2547D526E00CE7C5DDCDB3E9C91E0@BN7PR11MB2547.namprd11.prod.outlook.com> <17374.1559083024@localhost> <HE1PR0701MB24447D45A6A7461DEC49FE7B9B1F0@HE1PR0701MB2444.eurprd07.prod.outlook.com> <12129.1559329924@localhost> <7f83213b-2e63-57f5-5a1a-956d47b58683@primekey.com> <AM0PR10MB2402726EDDA7074FEDFF917DFE100@AM0PR10MB2402.EURPRD10.PROD.OUTLOOK.COM> <6992.1559937612@localhost> <83b511c0-4047-9431-196b-9b4028ee726d@primekey.com> <E313E304-95EA-4EEF-B23D-E43F919593FF@akamai.com> <28f0bc85-fd3f-e811-baf6-220ed8564c58@primekey.com> <42C0B0A7-792A-4DBD-B984-15A30B5C0FD0@akamai.com> <aa3265eb-40af-6d7d-5b35-adb6f14649a7@primekey.com>
In-Reply-To: <aa3265eb-40af-6d7d-5b35-adb6f14649a7@primekey.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1a.0.190530
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.33.137]
Content-Type: text/plain; charset="utf-8"
Content-ID: <905DD5A9DE1DA1409923892E387D85C1@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-06-10_07:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=253 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1906100104
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-06-10_07:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=346 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1906100104
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/ctynI4bv5AOc3wRK-BvPu6JZvyM>
Subject: Re: [lamps] Interest to standardize PKI REST APIs?
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: Mon, 10 Jun 2019 15:04:05 -0000

    Are there any examples of such additions to the base spec publicly
    available?

Many.  Look at https://datatracker.ietf.org/wg/acme/documents/ to see the document list; the "authority token" is for phones, the rest should be obvious.