Re: [pkix] Is it time for a pkix extensions (or similar) wg?

Wei Chuang <weihaw@google.com> Sat, 06 February 2016 07:23 UTC

Return-Path: <weihaw@google.com>
X-Original-To: pkix@ietfa.amsl.com
Delivered-To: pkix@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 455281ACD5F for <pkix@ietfa.amsl.com>; Fri, 5 Feb 2016 23:23:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.379
X-Spam-Level:
X-Spam-Status: No, score=-1.379 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=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 YmPNtniYEDli for <pkix@ietfa.amsl.com>; Fri, 5 Feb 2016 23:23:55 -0800 (PST)
Received: from mail-ig0-x231.google.com (mail-ig0-x231.google.com [IPv6:2607:f8b0:4001:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85CE71ACD5C for <pkix@ietf.org>; Fri, 5 Feb 2016 23:23:55 -0800 (PST)
Received: by mail-ig0-x231.google.com with SMTP id 5so28724766igt.0 for <pkix@ietf.org>; Fri, 05 Feb 2016 23:23:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=JEIZshVOg1Q8GK7ShP4bxVdkbTVv1kCM5UgarZwVQaE=; b=jmylw6UA5MQpn6TQTYT5DL6SXtt3MyLOyMjF4538NUHU1XE/qrdCbZIjAIz7KwuxDD ucL/ozNbAfFMSNh/5MgjELfUgcWCZTKXjUOJzM03LaxKN60F1WGTwJhqY8i8uLy2q5kZ DoFQBMi5LisxipOfRdaTKxtWo7lhq/LwCRHN6AJ/akn9jT0mUizqpULE4+UthOOj0TAy ZkwxyaDt4reUrssFxTkaFZdDff2Kh1dCdpbuNbXnLvySVSZVIyC1HQGNw5KaJ2VMeuol rhUv+U3kPghRUKCnemlrXXfI84jI6nn3214H3WdQsofbfJz4GZIntOaP41nXhu98SmST 9XeQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=JEIZshVOg1Q8GK7ShP4bxVdkbTVv1kCM5UgarZwVQaE=; b=i4F7oZU4fI6RLpW3/0UZJlgzwvDBvhDVajJSLH+JH7MFfDhd3t8sc4iDwyiW7o/BzK sXo4udSdJZafh7qaXxS7N0uL2iAMemn7Hul8zv5pEQl9KIRZwjtgPAs8o3glbCvvV5/N wW2/QMY4kxy4Ay9g7TK/4oARcsFkQlW+I4GIiSx2igQLAzKaPof6LqX057ZLrxymsYlG 0KEKX9i4R++ssvl8vLyefGPf15ugMBmfiuaAdC4ZFxKx17EtvVKAS37ROPbN3VCvmi0r 1NT7130b2H547k5+rXCQuVMzUU9qIkCzTgIYbldbdlatYw6xFkKtVgyy4tvd017A5IU6 u6Fg==
X-Gm-Message-State: AG10YOT5SsnH0Kycv7MINe3wpLIvTG0PoSYaq60ydtDnRLgdOglffY7QbzIKfYpxgUFSWcxN6GDl6w6XBzkHffUX
MIME-Version: 1.0
X-Received: by 10.50.138.4 with SMTP id qm4mr13891543igb.81.1454743434655; Fri, 05 Feb 2016 23:23:54 -0800 (PST)
Received: by 10.64.149.39 with HTTP; Fri, 5 Feb 2016 23:23:54 -0800 (PST)
In-Reply-To: <CAAFsWK2czHNii6xS-Lh86y3cz6NGvUvnCdmg4hEMMYMHgvP+fg@mail.gmail.com>
References: <56B48DED.5080202@cs.tcd.ie> <CAAFsWK2czHNii6xS-Lh86y3cz6NGvUvnCdmg4hEMMYMHgvP+fg@mail.gmail.com>
Date: Fri, 05 Feb 2016 23:23:54 -0800
Message-ID: <CAAFsWK3GGadD5f5mkuN-K4Jm+LoAMNtdoPm5TRYRfYi++yWOLw@mail.gmail.com>
From: Wei Chuang <weihaw@google.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: multipart/alternative; boundary="001a11360006a9d0ff052b14d91e"
Archived-At: <http://mailarchive.ietf.org/arch/msg/pkix/D8Ni8mu29hRisX_ZNg8uOymUe7o>
Cc: pkix <pkix@ietf.org>
Subject: Re: [pkix] Is it time for a pkix extensions (or similar) wg?
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.15
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: Sat, 06 Feb 2016 07:23:57 -0000

On Fri, Feb 5, 2016 at 2:32 PM, Wei Chuang <weihaw@google.com> wrote:

>
>
> On Fri, Feb 5, 2016 at 3:56 AM, Stephen Farrell <stephen.farrell@cs.tcd.ie
> > wrote:
>
>>
>> Hiya,
>>
>> We seem to be seeing a number of drafts that folks are
>> writing that define new certificate extensions or that
>> want to update/modify PKIX specs.
>>
>> Do folks think it is now time to form a working group
>> to process those?
>>
>
> Yes.
>
>
>>
>> If no, please say why.
>>
>> If yes, please say what draft(s) and propose any other
>> scoping. If you know of people who are or would implement
>> and deploy, that is very useful information. (It is fine
>> to say "I think we should work on topic <foo>" but it is
>> *much* better if you can point at a draft you've written
>> about <foo> and say that you or someone is implementing
>> that and that it'll get deployed.)
>>
>
> We are interested in specifying internationalization support for the email
> address local-part, and we've written a draft for that:
> http://www.ietf.org/id/draft-lbaudoin-iemax-02.txt
> We're aware of at least one other prior draft on this topic.
>

Mentioned else where but also updating Unicode in query and path parts of
the URL in uniformResourceIdentifier should also be considered for in scope
of the WG.  Would definitely need help here with a draft as I'm not as
familiar with URL precedence as with email.

-Wei


> Another related but distinct area of work would be handling the
> discrepancy between mail providers treating email addresses as case
> insensitive (and is acknowledged in RFC5321) yet is required by RFC5280.
> Moreover some email providers have other complicated normalization rules
> e.g. Gmail.  We don't have a draft for this topic but could write something
> up.
>
>
>> If you think this requires face to face discussion at
>> IETF95 (e.g. to tease out scope) please say that too.
>> We still have a couple of weeks before the BoF deadline
>> and if a short session is needed that can be arranged.
>> Note though that there is no need to have such a BoF
>> session to form a WG, if everything is clear already.
>>
>> FWIW, my impression is that we do seem to have a handful
>> of drafts where folks seem willing to do the work and
>> where the work might be (or has been) implemented. So
>> if there's enough interest, I'd be supportive of forming
>> a (hopefully:-) short-lived, tightly scoped, WG to handle
>> that work.
>>
>
> +1
>
> That would be much appreciated.
>
> -Wei
>
>
>> Cheers,
>> S.
>>
>> _______________________________________________
>> pkix mailing list
>> pkix@ietf.org
>> https://www.ietf.org/mailman/listinfo/pkix
>>
>
>