[pkix] Fwd: Re: [Spasm] WG Review: Some PKIX and SMIME (spasm)

Stephen Farrell <stephen.farrell@cs.tcd.ie> Wed, 29 June 2016 15:05 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: pkix@ietfa.amsl.com
Delivered-To: pkix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63D8612B004; Wed, 29 Jun 2016 08:05:07 -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 qsgyKN38TREv; Wed, 29 Jun 2016 08:05:01 -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 3727012DF0C; Wed, 29 Jun 2016 08:04:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 083BFBE47; Wed, 29 Jun 2016 16:04:50 +0100 (IST)
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 XibsiNzxXeSp; Wed, 29 Jun 2016 16:04:49 +0100 (IST)
Received: from [134.226.36.93] (bilbo.dsg.cs.tcd.ie [134.226.36.93]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 602CCBE35; Wed, 29 Jun 2016 16:04:49 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1467212689; bh=TfSZdygX5OWgNnjFqar+DzFPh3TrO0bTiCEYiDMd/ys=; h=Subject:References:To:From:Date:In-Reply-To:From; b=1x9y6LGKCmosegqaP7HQ0UNUnl+vf2fVIM1/CRcXJO4CYqj/IycAhAkxblSMQjwTZ RP68WEioh4ArsQc8Rd2BJ70Gxnm6UvML/5NHRfuodVc9ab1HqnI1E86G8UxukLs1h0 gmzP5REKDw+8UN3fj3IXIPGzkOwrwRDtg8a7RzXg=
References: <5773E34B.9080503@cs.tcd.ie>
To: pkix <pkix@ietf.org>, 'IETF SMIME' <smime@ietf.org>, "saag@ietf.org" <saag@ietf.org>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
X-Forwarded-Message-Id: <5773E34B.9080503@cs.tcd.ie>
Message-ID: <5773E391.6080308@cs.tcd.ie>
Date: Wed, 29 Jun 2016 16:04:49 +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: <5773E34B.9080503@cs.tcd.ie>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms040806050400030107030207"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pkix/Ts_5Vfn06XyqTt2zD7eUlRW3JlU>
Subject: [pkix] Fwd: Re: [Spasm] WG Review: Some PKIX and SMIME (spasm)
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: PKIX Working Group <pkix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pkix>, <mailto:pkix-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pkix/>
List-Post: <mailto:pkix@ietf.org>
List-Help: <mailto:pkix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pkix>, <mailto:pkix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jun 2016 15:05:08 -0000

FYI - a late name-change for a proposed WG.

S.


-------- Forwarded Message --------
Subject: Re: [Spasm] WG Review: Some PKIX and SMIME (spasm)
Date: Wed, 29 Jun 2016 16:03:39 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: IETF-Announce <ietf-announce@ietf.org>
CC: spasm@ietf.org, IETF-Discussion <ietf@ietf.org>


Hi,

During chartering we got a comment that the proposed name of
this WG might be considered insensitive. We don't need to
have a discussion about that, as it makes little difference
otherwise, but we will be changing the name of the proposed
working group to:

lamps - Limited Additional Mechanisms for PKIX and SMIME

Thanks to Michael Jenkins for the suggestion on the current
WG mailing list. [1]

The secretariat will handle migrating the mailing list in
the coming weeks, and the IETF96 agenda will be updated
accordingly, assuming that the IESG approve the new working
group on the telechat tomorrow. If approved, the announcement
of the working group will use the new name, "lamps."

There are no other substantive changes to the draft charter. [2]

Thanks,
S.

[1] https://mailarchive.ietf.org/arch/msg/spasm/t4f5LKRJILn0KsLQdzA1fo8B1lM
[2] https://datatracker.ietf.org/doc/charter-ietf-spasm/


On 17/06/16 17:33, The IESG wrote:
> A new IETF WG has been proposed in the Security Area. The IESG has not
> made any determination yet. The following draft charter was submitted,
> and is provided for informational purposes only. Please send your
> comments to the IESG mailing list (iesg@ietf.org) by 2016-06-27.
> 
> Some PKIX and SMIME (spasm)
> -----------------------------------------------------------------------
> Current status: Proposed WG
> 
> Chairs:
>   TBD
> 
> Assigned Area Director:
>   Stephen Farrell <stephen.farrell@cs.tcd.ie>
> 
> Security Area Directors:
>   Stephen Farrell <stephen.farrell@cs.tcd.ie>
>   Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>
>  
> Mailing list:
>   Address: spasm@ietf.org
>   To subscribe: https://www.ietf.org/mailman/listinfo/spasm
>   Archive: https://www.ietf.org/mail-archive/web/spasm/
> 
> Charter: https://datatracker.ietf.org/doc/charter-ietf-spasm/
> 
> 
> The PKIX and S/MIME Working Groups have been closed for some time.  Some
> updates have been proposed to the X.509 certificate documents produced 
> by the PKIX Working Group and the electronic mail security documents 
> produced by the S/MIME Working Group.
> 
> The SPASM (Some PKIX and S/MIME) Working Group is chartered to make
> updates where there is a known constituency interested in real 
> deployment and there is at least one sufficiently well specified 
> approach to the update so that the working group can sensibly evaluate 
> whether to adopt a proposal.  The current charter encompasses updates to 
> satisfy the following needs:
> 
> 1. Specify the way to include an i18n email address as a subject
>    alternative name and an issuer alternative name.
>    draft-melnikov-spasm-eai-addresses is a proposal in this space. 
> 
> 2. Specify the way to use authenticated encryption in S/MIME. 
>    draft-schaad-rfc5751-bis is a proposal in this space.
> 
> In addition, the SPASM Working Group may investigate other updates to 
> the documents produced by the PKIX and S/MIME Working Groups, but the 
> SPASM Working Group shall not adopt any of these potential work items 
> without rechartering. No such re-chartering is envisaged until one or 
> more of the above work items have been successfully delivered to the RFC 
> editor queue. 
> 
> Milestones:
> 
> TBD
> 
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://www.ietf.org/mailman/listinfo/spasm
>