Re: [pkix] New Version Notification for draft-belyavskiy-certificate-limitation-policy-04.txt

Peter Bowen <pzbowen@gmail.com> Sun, 08 October 2017 03:31 UTC

Return-Path: <pzbowen@gmail.com>
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 7C26A13331E; Sat, 7 Oct 2017 20:31:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 HEoUoE651Y-u; Sat, 7 Oct 2017 20:31:21 -0700 (PDT)
Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (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 0B7E2133078; Sat, 7 Oct 2017 20:31:20 -0700 (PDT)
Received: by mail-lf0-x235.google.com with SMTP id c82so20174030lfc.6; Sat, 07 Oct 2017 20:31:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Prd6OgF7t7YAi6BCUrTaOlcSYcyIAeTLoc4K4V2s8j4=; b=d4my61sYNBVlPOeMxkf+5RIyZgwT+SenU42iKIX7D1gHjHZFjYQ9QbPtdqbYqvdlJK BDbsD6rnVLMismMHxOGKkBxVWzlSuLJElKv+iS3c6saW68gOknjcFdzJByXaMCE9xfmr vv/e3jfJxVjyndkmbUn1/9zLibCFYafV4ELlO1+lrykKrVmFQ9XSSAd/uwklsLUoVi0a Z35N6GbkNVuix1qqcikOz1j/8YJigsbgn0zbw0VCGAFM2vYGO6T6WCdb78T5cG9jRkQV RIm0pNPi1WvNv+MuPLAMGknAJSiIMnAlCz5panmQ7V7R1C4L0KrwcH9HDFLg448MQM0d +dHA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Prd6OgF7t7YAi6BCUrTaOlcSYcyIAeTLoc4K4V2s8j4=; b=iBX89SxVt7xHfOsdVYSF1u54w/n4Qp5ETvVTEpArRKIGQAitLyI9W/isAFZmYZQipz k5ENfKnvw9eC3DOcnYtEjiPXgqjjBu9FudubH1oEleJ08BjEo1OjwLmEC4AZGtIHys6M Y57N6v5LeM8+Q4E4vUsjtgkZS0P21gqNMOlrYNsMa6Aft111TQFgHrg577qDHDrS2E6O P9JkMgftyMPLz+yZqAhBBud65eVIsEw9V5FZonesJ70ELxa9t42vLRdr7IZmQc08ouSd 5KxKm3q3xZ1faDrQJ/Mo5/NBY0bSFHlGkXRsW1GsrEisNEC61M7vRaeAMXcf77axsqQS h4zg==
X-Gm-Message-State: AMCzsaV5jHLfC2832mFSkaGl4RYaDze9kIivgXxTS5DttKgE3HPVNU0S LPJXyXYke+b4iCIVon4uwQ/oNYxRCoKmq5EsJr8=
X-Google-Smtp-Source: AOwi7QAXUoA4L06mmq/nwvpTnFH+Ygyomp3o6mS2ux9w29TjL4W7W19ID59obXswesQhxHJXS6zq1S3rwvNxFbK9/P8=
X-Received: by 10.25.143.156 with SMTP id s28mr2521530lfk.236.1507433478938; Sat, 07 Oct 2017 20:31:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.28.19 with HTTP; Sat, 7 Oct 2017 20:31:18 -0700 (PDT)
In-Reply-To: <CADqLbz+OB86s4E-Ntr6eaEow+sBtxscJ703nGN+PAS7zQmJ==Q@mail.gmail.com>
References: <150522092693.4724.2532571098567577114.idtracker@ietfa.amsl.com> <CADqLbz+OB86s4E-Ntr6eaEow+sBtxscJ703nGN+PAS7zQmJ==Q@mail.gmail.com>
From: Peter Bowen <pzbowen@gmail.com>
Date: Sat, 7 Oct 2017 20:31:18 -0700
Message-ID: <CAK6vND90Fryurf4QZYnjaw8iMmhn7=pE4YgW+5R2i5ertMGWsg@mail.gmail.com>
To: Dmitry Belyavsky <beldmit@gmail.com>
Cc: "saag@ietf.org" <saag@ietf.org>, LAMPS <spasm@ietf.org>, "mozilla-dev-security-policy@lists.mozilla.org" <dev-security-policy@lists.mozilla.org>, "<pkix@ietf.org>" <pkix@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pkix/ykLzNBbeb4Go7cm0a_ZgG9msfFQ>
Subject: Re: [pkix] New Version Notification for draft-belyavskiy-certificate-limitation-policy-04.txt
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.22
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: Sun, 08 Oct 2017 03:31:22 -0000

On Tue, Sep 12, 2017 at 5:59 AM, Dmitry Belyavsky via
dev-security-policy <dev-security-policy@lists.mozilla.org> wrote:
> Here is the new version of the draft updated according to the discussion on
> mozilla-dev-security list.

Given that RFC 5914 already defines a TrustAnchorList and
TrustAnchorInfo object and that the Trust Anchor List object is
explicitly contemplated as being included in a signed CMS message,
would it not make more sense to start from 5914 and define new
extensions encode constraints not currently defined?

Thanks,
Peter