IETF Logo Mail Archive

Re: [Spasm] BoF in Berlin or what?

"Jim Schaad" <ietf@augustcellars.com> Tue, 14 June 2016 09:59 UTC

Return-Path: <ietf@augustcellars.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 402EA12D192 for <spasm@ietfa.amsl.com>; Tue, 14 Jun 2016 02:59:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
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 SaIMrKacAmRe for <spasm@ietfa.amsl.com>; Tue, 14 Jun 2016 02:59:38 -0700 (PDT)
Received: from smtp3.pacifier.net (smtp3.pacifier.net [64.255.237.177]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD44112B064 for <spasm@ietf.org>; Tue, 14 Jun 2016 02:59:38 -0700 (PDT)
Received: from hebrews (c-24-21-96-37.hsd1.or.comcast.net [24.21.96.37]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: schaad@nwlink.com) by smtp3.pacifier.net (Postfix) with ESMTPSA id 5A7CA38EFD; Tue, 14 Jun 2016 02:59:38 -0700 (PDT)
From: Jim Schaad <ietf@augustcellars.com>
To: 'Russ Housley' <housley@vigilsec.com>, spasm@ietf.org
References: <57519BBB.8050604@cs.tcd.ie> <7255B25B-9278-461C-9480-D4326F63D37B@vigilsec.com>
In-Reply-To: <7255B25B-9278-461C-9480-D4326F63D37B@vigilsec.com>
Date: Tue, 14 Jun 2016 02:59:37 -0700
Message-ID: <09f701d1c623$767b4480$6371cd80$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQHW8767gWSD88kXh4etiVhlBOiuaAHTypiSn8/BDAA=
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/vaYyqKvDfN0kn8rqAH65DHDRmOo>
Subject: Re: [Spasm] BoF in Berlin or what?
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: Tue, 14 Jun 2016 09:59:40 -0000

I will definitely be able to do this.

> -----Original Message-----
> From: Spasm [mailto:spasm-bounces@ietf.org] On Behalf Of Russ Housley
> Sent: Tuesday, June 14, 2016 2:50 AM
> To: spasm@ietf.org
> Subject: Re: [Spasm] BoF in Berlin or what?
> 
> My understanding is that a one hour meeting slot for SPASM was approved
for
> Berlin:
> 
> 	https://mailarchive.ietf.org/arch/msg/spasm/23XSrpv0Gc8knO8bU0MA
> wsGGXKY
> 
> We have two work items in the most recent charter:
> 
> 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.
> 
> Can we count on Alexey and Jim to give status and open issues on these
drafts?
> 
> Russ
> 
> 
> 
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://www.ietf.org/mailman/listinfo/spasm

v2.23.0 | Report a Bug | By Email