Re: [Spasm] certspec work (draft-seantek-certspec-06.txt)

Stephen Farrell <stephen.farrell@cs.tcd.ie> Thu, 09 June 2016 13:44 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 8F0D912B01F for <spasm@ietfa.amsl.com>; Thu, 9 Jun 2016 06:44:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.727
X-Spam-Level:
X-Spam-Status: No, score=-5.727 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_MED=-2.3, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 LIP7WQImHDKv for <spasm@ietfa.amsl.com>; Thu, 9 Jun 2016 06:44:49 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 160B912D67D for <spasm@ietf.org>; Thu, 9 Jun 2016 06:44:49 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id CC39CBDCC; Thu, 9 Jun 2016 14:44:47 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vbJB_OePdksf; Thu, 9 Jun 2016 14:44:43 +0100 (IST)
Received: from [10.87.48.210] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id EF601BDCA; Thu, 9 Jun 2016 14:44:42 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1465479883; bh=tAw7XID8ggSfELIF6PFTVBD5k8D32RmtPxrgY88cEX4=; h=Subject:To:References:From:Date:In-Reply-To:From; b=WCpN9jOy3TKZIZ3HiKlsAMQCA19GoaEzV7qoC9pEiOdzrfmEz8H+ZWZfaU5fCiezn 9ZnnNsXCg2R1Fdmn/ZN3VCQoGZj7AXY1vvjg/ao+xKk9QX4je8VkQ43FP5JzMa8gyV p+hr7PV/bd5xBYkcoL9MRZTJH7p05O3AVMJtCGik=
To: Sean Leonard <dev+ietf@seantek.com>, spasm@ietf.org
References: <20160608161629.19935.86198.idtracker@ietfa.amsl.com> <f7c50b01-9d68-11ac-c343-9ffff7dbf143@seantek.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <575972CA.2090806@cs.tcd.ie>
Date: Thu, 09 Jun 2016 14:44:42 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0
MIME-Version: 1.0
In-Reply-To: <f7c50b01-9d68-11ac-c343-9ffff7dbf143@seantek.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms000905080805060802060005"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/eW73pG9GRKLRu34LGqKPhCEvFM0>
Subject: Re: [Spasm] certspec work (draft-seantek-certspec-06.txt)
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.17
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, 09 Jun 2016 13:44:50 -0000

Sean,

On 08/06/16 17:28, Sean Leonard wrote:
> Hello SPASM:
> 
> I would like to propose "certspec" as a work item for this WG, and that
> it be considered in-scope as we debate the WG's scope.
> 
> certspec is a string specification for certificates. It allows protocols
> and systems to identify a certificate in a textual form, and is designed
> with human usability in mind (specifically, copy-and-paste operations).
> 
> Previous versions of this draft tried to define certspec as a URN, and
> then as a series of URI schemes. Those approaches were not successful.
> This draft just calls it a string. You can look at the diffs
> (particularly the diff between 04 and 05) to see the differences.
> 
> Thanks to Russ Housley for feedback on the most recent versions of this
> draft.

If there's a bunch of folks saying they'd implement and deploy
that'd be good. Absent that, see earlier charter discussion.

Cheers,
S.

> 
> Regards,
> 
> Sean
> 
> -------- Forwarded Message --------
> Subject:     New Version Notification for draft-seantek-certspec-06.txt
> Date:     Wed, 08 Jun 2016 09:16:29 -0700
> From:     internet-drafts@ietf.org
> 
> 
> 
> A new version of I-D, draft-seantek-certspec-06.txt
> has been successfully submitted by Sean Leonard and posted to the
> IETF repository.
> 
> Name:        draft-seantek-certspec
> Revision:    06
> Title:        String Specification for Certificates
> Document date:    2016-06-08
> Group:        Individual Submission
> Pages:        27
> URL:           
> https://www.ietf.org/internet-drafts/draft-seantek-certspec-06.txt
> Status:         https://datatracker.ietf.org/doc/draft-seantek-certspec/
> Htmlized:       https://tools.ietf.org/html/draft-seantek-certspec-06
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-seantek-certspec-06
> 
> Abstract:
>    Digital certificates are used in many systems and protocols to
>    identify and authenticate parties.  This document describes a string
>    format that identifies certificates, along with optional attributes.
>    This string format has been engineered to work without re-encoding in
>    a variety of protocol slots.
> 
>                                                                                  
> 
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://www.ietf.org/mailman/listinfo/spasm
>