Re: [Gen-art] Genart last call review of draft-op3ft-leaptofrogans-uri-scheme-03

Benjamin PHISTER <benjamin.phister@op3ft.org> Thu, 07 February 2019 10:40 UTC

Return-Path: <benjamin.phister@op3ft.org>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97BE4131104 for <gen-art@ietfa.amsl.com>; Thu, 7 Feb 2019 02:40:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.689
X-Spam-Level:
X-Spam-Status: No, score=-0.689 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_RP_RNBL=1.31, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=op3ft.org
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 JGl7CkkJ6cj1 for <gen-art@ietfa.amsl.com>; Thu, 7 Feb 2019 02:40:23 -0800 (PST)
Received: from beige.cedar.relay.mailchannels.net (beige.cedar.relay.mailchannels.net [23.83.210.16]) (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 0C21D13107E for <gen-art@ietf.org>; Thu, 7 Feb 2019 02:40:20 -0800 (PST)
X-Sender-Id: 5ei546bipu|env-sender|benjamin.phister@op3ft.org
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 496F45E3690 for <gen-art@ietf.org>; Thu, 7 Feb 2019 10:40:20 +0000 (UTC)
Received: from mail0.stg-interactive.net (unknown [100.96.19.78]) (Authenticated sender: 5ei546bipu) by relay.mailchannels.net (Postfix) with ESMTPA id 852F65E0DE7 for <gen-art@ietf.org>; Thu, 7 Feb 2019 10:40:19 +0000 (UTC)
X-Sender-Id: 5ei546bipu|env-sender|benjamin.phister@op3ft.org
Received: from mail0.stg-interactive.net (mx2.fr.stgi.io [5.135.29.244]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.16.2); Thu, 07 Feb 2019 10:40:20 +0000
X-MC-Relay: Junk
X-MailChannels-SenderId: 5ei546bipu|env-sender|benjamin.phister@op3ft.org
X-MailChannels-Auth-Id: 5ei546bipu
X-Harbor-Robust: 7e0017d82f0dc1e6_1549536020188_2580597221
X-MC-Loop-Signature: 1549536020188:1769598063
X-MC-Ingress-Time: 1549536020188
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=op3ft.org; s=mail; t=1549536014; bh=26YfFBx0SEnwigvzRNIswf5Jb/1DTP+qOqaJ7on2BrM=; h=Subject:To:References:Cc:From:Date:In-Reply-To; b=d0WgOAHg56zNpCOlzMBKKmEAnYMEAchNHCqlpILg/3GTCIjOHcj8t6JX6BvnZiRRe zGE7zS+FJGdJ0YmrATN9h/0StOIlqyU8y8D5BcoXgUlyukNywLzui6DprSEfGIizhs EN9Ymg+vNawkUy2RKy0nn5Lx1H12mcWZviph69ao=
To: Alissa Cooper <alissa@cooperw.in>, ek@loon.co
References: <154209157324.4186.13787008047570111006@ietfa.amsl.com> <878t1w479d.fsf@hobgoblin.ariadne.com> <CAAedzxp4PEdeB06K2WmEHZbfQZVZ9PJ_1qopj9REnvW6romJSg@mail.gmail.com> <C1BF6635-E38F-488A-BAB6-2A6E2A6F314B@cooperw.in>
Cc: Dale Worley <worley@ariadne.com>, IETF Gen-ART <gen-art@ietf.org>, Erik Kline <ek=40google.com@dmarc.ietf.org>, draft-op3ft-leaptofrogans-uri-scheme.all@ietf.org, Alexis TAMAS <alexis.tamas@op3ft.org>, Alexey Melnikov <aamelnikov@fastmail.fm>, Peter Saint-Andre <stpeter@mozilla.com>, Jean-Emmanuel RODRIGUEZ <jean-emmanuel.rodriguez@contrib.op3ft.org>
From: Benjamin PHISTER <benjamin.phister@op3ft.org>
Message-ID: <ad8e9678-6137-0edc-ab63-5177cdb8688b@op3ft.org>
Date: Thu, 7 Feb 2019 11:40:14 +0100
User-Agent: Evolution 2.22.1
MIME-Version: 1.0
In-Reply-To: <C1BF6635-E38F-488A-BAB6-2A6E2A6F314B@cooperw.in>
Content-Type: multipart/alternative; boundary="------------90BE263279CFCD100A755712"
X-DSPAM-Result: Innocent
X-DSPAM-Processed: Thu Feb 7 11:40:17 2019
X-DSPAM-Confidence: 1.0000
X-DSPAM-Probability: 0.0023
X-DSPAM-Signature: 6815,5c5c0b1141301683415433
X-DSPAM-Factors: 27, within+#+#+of, 0.40000, within+#+#+of, 0.40000, Subject*Genart+#+#+#+of, 0.40000, might+#+#+itch, 0.40000, might+#+#+itch, 0.40000, available+#+#+think, 0.40000, available+#+#+think, 0.40000, w+r, 0.40000, w+r, 0.40000, certainly+#+#+worth, 0.40000, certainly+#+#+worth, 0.40000, use+#+so, 0.40000, use+#+so, 0.40000, format+#+#+readily, 0.40000, format+#+#+readily, 0.40000, Cc*Gen-ART+#+ietf.org, 0.40000, that+#+address, 0.40000, that+#+address, 0.40000, ietf+#+mailto, 0.40000, ietf+#+mailto, 0.40000, list+#+#+ietf, 0.40000, list+#+#+ietf, 0.40000, starting+#+#+#+at, 0.40000, starting+#+#+#+at, 0.40000, there+isn't, 0.40000, there+isn't, 0.40000, 99+#+#+#+Thanks, 0.40000
X-Virus-Scanned: ClamAV using ClamSMTP
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/cXuUTjDjdmCnjcUWMZcWJooZLAI>
Subject: Re: [Gen-art] Genart last call review of draft-op3ft-leaptofrogans-uri-scheme-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Feb 2019 10:40:25 -0000

Hi Alissa, Hi Erik,

Sorry that we didn't respond directly to your comment, Erik.

Following your suggestion and after a brief discussion with Alexey and 
Peter, we added examples to the I-D starting with version -04, at the 
end of section 4.1, as follows:

>     Examples of 'leaptofrogans' URIs:
>
>     -  if the Frogans address is the string of US-ASCII characters
>        "Network-Name*Site-Name":
>
>          leaptofrogans:Network-Name*Site-Name
>
>     -  if the Frogans address is the string of Unicode characters U+7F51,
>        U+7EDC, U+540D, U+002A, U+7AD9, U+540D (which is a Chinese
>        translation of the Frogans address in the previous example):
>
>          leaptofrogans:%E7%BD%91%E7%BB%9C%E5%90%8D*%E7%AB%99%E5%90%8D

Thanks again for your input!

Alissa, we will respond to the IPR questions you raised and to Brad's 
comments within a couple of hours.

Best regards,

Ben and Alexis


------------------------------------------------------------------------
*From:* Alissa Cooper <alissa@cooperw.in>;
*Subject:* [Gen-art] Genart last call review of 
draft-op3ft-leaptofrogans-uri-scheme-03
*Date:* Wednesday, Feb 6, 2019 10:51 PM CET
*To:* ek@loon.co
*Cc:* Dale Worley <worley@ariadne.com>;, IETF Gen-ART <gen-art@ietf.org>;, 
Erik Kline <ek=40google.com@dmarc.ietf.org>;, 
draft-op3ft-leaptofrogans-uri-scheme.all@ietf.org

> Erik, thanks for your review. I entered a DISCUSS position to ask an 
> IPR question and pointed to your review.
>
> Alissa
>
>> On Nov 13, 2018, at 11:53 PM, Erik Kline <ek@loon.co 
>> <mailto:ek@loon.co>> wrote:
>>
>> On Tue, 13 Nov 2018 at 20:23, Dale R. Worley <worley@ariadne.com 
>> <mailto:worley@ariadne.com>wrote:
>>>
>>> Erik Kline <ek=40google.com@dmarc.ietf.org 
>>> <mailto:ek=40google.com@dmarc.ietf.org>> writes:
>>>> Nits/editorial comments: I can't help but wonder if an example or 
>>>> two wouldn't
>>>> round out the document.  But maybe leaptofrogans: URIs/IRIs aren't 
>>>> amenable to
>>>> constructing an example?
>>>
>>> I agree in principle with this.  Looking at reference [IFAP], here are
>>> two examples:
>>>
>>>    leaptofrogans:mynetwork*mysite
>>>    leaptofrogans:my-network*MySite
>>>
>>> The syntax of frogan addresses is very carefully specified, but most of
>>> the work seems to revolve around using Unicode well:  Frogans are fully
>>> internationalized, so there's a lot of work in [IFAP] specifying how to
>>> use Unicode so that an address aligns with the intuitive sense of "a
>>> text string".
>>>
>>> But beyond the fact that a frogan address is split into two parts by a
>>> "*" character, there isn't much syntax that's easily displayed by a
>>> series of ASCII examples.
>>
>> I understand about the limitations of the current RFC format w.r.t.
>> non-ASCII characters (but I suspect you wouldn't want to wait for the
>> new format to be readily available :-).
>>
>> FWIW I think those two examples would be perfectly fine.  They may not
>> seem overly expressive or especially illustrative, but including them
>> might scratch an itch for some readers.
>>
>> But it's certainly not anything worth holding up publication for, IMHO.
>>
>> _______________________________________________
>> Gen-art mailing list
>> Gen-art@ietf.org <mailto:Gen-art@ietf.org>
>> https://www.ietf.org/mailman/listinfo/gen-art
>

-- 
Benjamin Phister
Head of Technical Specifications
benjamin.phister@op3ft.org

OP3FT
6 square Mozart
75016 Paris - France
Tel: +33 1 5392 0040
https://www.op3ft.org/
frogans*op3ft