IETF Logo Mail Archive

Re: [Trans] draft-ietf-trans-rfc6962-bis-31

Paul Wouters <paul@nohats.ca> Wed, 26 June 2019 04:31 UTC

Return-Path: <paul@nohats.ca>
X-Original-To: trans@ietfa.amsl.com
Delivered-To: trans@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB27012060A for <trans@ietfa.amsl.com>; Tue, 25 Jun 2019 21:31:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 wbO1SijbKCKi for <trans@ietfa.amsl.com>; Tue, 25 Jun 2019 21:31:20 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5195120608 for <trans@ietf.org>; Tue, 25 Jun 2019 21:31:20 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 45YVTf1tBkz3J8; Wed, 26 Jun 2019 06:31:18 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1561523478; bh=7NJAMsLCy9L2gbmL752FNG8MiucOfMT5G0Hb/TR7zvI=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=fVtftRAk8ZFbYnK9tVaWrlSujrnti5Aw9ejOSml3DR1uw8QW4+iHV/WZwk8W06Cv4 HtJJL+VZZu2DkO/r9LteST1cEEPccVAH4WYIu2TR7JS5jTclp4r8nd+UkXqM+1unJu 60I3wTb39dYS6+XG5kc7y5Z9guJVnVy6Zip2zqp4=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id y56eIEiFuTmT; Wed, 26 Jun 2019 06:31:16 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Wed, 26 Jun 2019 06:31:15 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 09C9E3547F5; Wed, 26 Jun 2019 00:31:14 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca 09C9E3547F5
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id EEE2540D35BF; Wed, 26 Jun 2019 00:31:14 -0400 (EDT)
Date: Wed, 26 Jun 2019 00:31:14 -0400 (EDT)
From: Paul Wouters <paul@nohats.ca>
To: Rashmi Jha <rashmij@microsoft.com>
cc: "trans@ietf.org" <trans@ietf.org>
In-Reply-To: <MWHPR21MB0846B70FF84DE41A3B16BB9AA7E20@MWHPR21MB0846.namprd21.prod.outlook.com>
Message-ID: <alpine.LRH.2.21.1906260028020.14406@bofh.nohats.ca>
References: <MWHPR21MB0846D2C92633AE28A7B012EAA7E50@MWHPR21MB0846.namprd21.prod.outlook.com> <alpine.LRH.2.21.1906191936520.28894@bofh.nohats.ca> <CALzYgEefnThirThr=LwvD-T=L_b1nmNSGG90kxffwb9rc8ry=g@mail.gmail.com> <MWHPR21MB084622793C06701F9A7CCD8CA7E20@MWHPR21MB0846.namprd21.prod.outlook.com> <CACsn0cn_RHjtUHzVvVporJPENteMLQnF+6tW-ncBnt+dR3CVdA@mail.gmail.com> <MWHPR21MB0846B70FF84DE41A3B16BB9AA7E20@MWHPR21MB0846.namprd21.prod.outlook.com>
User-Agent: Alpine 2.21 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/39KtGpYutSeE4hezw1Zdfs83kY0>
Subject: Re: [Trans] draft-ietf-trans-rfc6962-bis-31
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Public Notary Transparency working group discussion list <trans.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trans>, <mailto:trans-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trans/>
List-Post: <mailto:trans@ietf.org>
List-Help: <mailto:trans-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trans>, <mailto:trans-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jun 2019 04:31:23 -0000

On Wed, 26 Jun 2019, Rashmi Jha wrote:

> 1. We can surely argue critical or non-critical.  Named constraints can be critical or non-critical

What is a non-critical named constraint? If the client does not
understand the named constraint, and it is non-critical, wouldn't it
mean the client may continue and ignore the thing, not knowing it is a
name constraint? That seems odd to me, as it would defeat the purpose
of it.

> 3. One of the CT issue is that the persona used to build the solution is thinking of only an application developer, site operator. The cloud scenario is a miss - The scenario is that I want to deploy my application in ~100 regions worldwide. I want to deploy my application at the same time across the world.

How is CT preventing this for you?

> 4. Wildcard - just  search or google it and there are numerous articles conveying the issue with wildcards.
>
> A question from my side : What is the role of this WG ?

https://datatracker.ietf.org/wg/trans/about/

Paul

v2.8.7 | Report a Bug | By Email