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

Marc Petit-Huguenin <> Tue, 15 May 2018 10:14 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3443512D7F0; Tue, 15 May 2018 03:14:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.441
X-Spam-Status: No, score=-0.441 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id yd47t1aqSKjR; Tue, 15 May 2018 03:14:12 -0700 (PDT)
Received: from (unknown []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E384612D868; Tue, 15 May 2018 03:14:02 -0700 (PDT)
Received: from [IPv6:2601:648:8300:e8a:d578:c438:f732:cb38] (unknown [IPv6:2601:648:8300:e8a:d578:c438:f732:cb38]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "Marc Petit-Huguenin", Issuer "" (verified OK)) by (Postfix) with ESMTPS id B48D3AE844; Tue, 15 May 2018 12:13:59 +0200 (CEST)
To: "Dale R. Worley" <>
References: <>
From: Marc Petit-Huguenin <>
Message-ID: <>
Date: Tue, 15 May 2018 03:13:45 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="D0y4dtMtx4nkC3esTkz21W5hO1b5B24lK"
Archived-At: <>
Subject: Re: [tram] Genart telechat review of draft-ietf-tram-stunbis-16
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 15 May 2018 10:14:14 -0000

On 05/14/2018 07:18 PM, Dale R. Worley wrote:
> Marc Petit-Huguenin <> 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.

No, you are right, I was using "eventually" incorrectly all this time.  I changed "eventually" to "optionally" in my copy.


Marc Petit-Huguenin