Re: [tram] Genart telechat review of draft-ietf-tram-stunbis-16

worley@ariadne.com (Dale R. Worley) Tue, 15 May 2018 02:18 UTC

Return-Path: <worley@alum.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E6D212EAA7 for <ietf@ietfa.amsl.com>; Mon, 14 May 2018 19:18:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.684
X-Spam-Level:
X-Spam-Status: No, score=-1.684 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 sA571VwnzDn2 for <ietf@ietfa.amsl.com>; Mon, 14 May 2018 19:18:03 -0700 (PDT)
Received: from resqmta-ch2-10v.sys.comcast.net (resqmta-ch2-10v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:42]) (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 4DAB112E8C7 for <ietf@ietf.org>; Mon, 14 May 2018 19:18:03 -0700 (PDT)
Received: from resomta-ch2-09v.sys.comcast.net ([69.252.207.105]) by resqmta-ch2-10v.sys.comcast.net with ESMTP id IPLCfHX6yFnRMIPXOffIjh; Tue, 15 May 2018 02:18:02 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-09v.sys.comcast.net with ESMTPA id IPXNfYyOYPhUCIPXNfXVMZ; Tue, 15 May 2018 02:18:02 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id w4F2I0SH021154; Mon, 14 May 2018 22:18:01 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id w4F2I0BS021151; Mon, 14 May 2018 22:18:00 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: Marc Petit-Huguenin <petithug@acm.org>
Cc: gen-art@ietf.org, draft-ietf-tram-stunbis.all@ietf.org, ietf@ietf.org, tram@ietf.org
Subject: Re: [tram] Genart telechat review of draft-ietf-tram-stunbis-16
In-Reply-To: <387eea8b-6f77-c94e-d67e-180ef17cd0f0@acm.org> (petithug@acm.org)
Sender: worley@ariadne.com
Date: Mon, 14 May 2018 22:18:00 -0400
Message-ID: <877eo5vezr.fsf@hobgoblin.ariadne.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-CMAE-Envelope: MS4wfCZArg1CqpTngJJvZPGQjADBTYcFKuNP7Tgh6La5vcruVByqLR9ghk+aCTo9icMqRkANL46U+0cz8wNBRCA7/Ord6oHmfPQLevgxiCKAKx2E/ja0NqsC QJptPF9BUDBJ44029Z9gZHdMkf3BZFdgw6qhvGnn0MM69Q5ucJFP2k8aoy37ecQ9uUxJ4lcsE70FK8E6tJaOnNg4Nr1Ah4kGS9vzAXFBVpuLEkiNh5+R8Kd2 g6y0o6ad6qiAcLl23VOuN23A3nnAgTGpHG2gfwoPsSvfX/FmZKmMeqV7lDWgp0G8j2q+ln844V+R0gs9cxNiBNrogQ3JQ3irttij6Q61L/XN7KfDpdS4XVeP mB+OAdWRFz3QGiKTtxt9YQ94flU8Xg==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/159aHhEz8MqW3nRqZJkoaRfN4J0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 May 2018 02:18:05 -0000

Marc Petit-Huguenin <petithug@acm.org> writes:
>>    To do that, it follows the
>>    identification procedures defined in [RFC6125], with a certificate
>>    containing an identifier of type DNS-ID or CN-ID, eventually with
>>    wildcards, but not of type SRV-ID or URI-ID.
>> 
>> The meaning of "eventually" here is not clear.
>
> Rephrased as:
>
>    [...]
>    containing an identifier of type DNS-ID or CN-ID, eventually with a
>    wildcard character as leftmost label, but not of type SRV-ID or URI-
>    [...]

I have some doubt about the use of "eventually" here.  As I use it,
"eventually" means that the thing will happen at some unspecified time
in the future.  Wiktionary gives this meaning also.  But I looked
"eventually" up in my paper dictionary, and it also has the meaning
"dependent on circumstance; contingent".

In this context, I do not see how the meaning about unspecified future
time works.  But perhaps you mean that having a wildcard character as
leftmost label is contingent?  That meaning works.  But in that case, I
would find "optionally" to be clearer.  (And Google Translate says that
"éventuellement" can be translated into English as either "eventually"
or "optionally", although it provides "facultativement" as the first
translation into French of "optionally".)

You may wish to consult the RFC Editor about this.

Dale