Re: [xmpp] AD review: draft-ietf-xmpp-address-04

Jehan Pagès <jehan.marmottard@gmail.com> Tue, 05 October 2010 17:15 UTC

Return-Path: <jehan.marmottard@gmail.com>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7D8053A6ED0 for <xmpp@core3.amsl.com>; Tue, 5 Oct 2010 10:15:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.148
X-Spam-Level:
X-Spam-Status: No, score=-2.148 tagged_above=-999 required=5 tests=[AWL=0.151, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7ACOIE-1+cGl for <xmpp@core3.amsl.com>; Tue, 5 Oct 2010 10:14:51 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id ACBBA3A6FBD for <xmpp@ietf.org>; Tue, 5 Oct 2010 10:14:45 -0700 (PDT)
Received: by iwn3 with SMTP id 3so10201475iwn.31 for <xmpp@ietf.org>; Tue, 05 Oct 2010 10:15:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=L7xLjvbiOypDDNS88hAjsu+tE7oxvw9jntJQbrZV6js=; b=hiFuXZCXM6UaiRcuil94cr5+dYFb6ksdarnX9cQhhI9p7oPuF2x5sIDCq02elEdEgo atuCKQpoSZBzsm2j/LA5LkiyBAg3KmjtzFfNbKrnGbSXddcsfPFJkxcsePXigZ2ZEAWo lRziowLqddJmp+guKraWTq26ZfUDJvz9xaBkM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=KMqtyzw7To2MxbQJ0B1vTD2D+zL1O/3Vcj3HqxphqJvR/wIYqoyvS7xmm5f28o7uKq Ve5BJM0rz3H01+baPcujKjVKtmb/Q6LzZxsW98f19JNrpqp+r/OZPwZvjmnM6NQQe1hu VDP0m6o4RZKl1tXBnkkyBfnbgzEKv4e1dyKGI=
MIME-Version: 1.0
Received: by 10.231.170.79 with SMTP id c15mr12458156ibz.82.1286298943629; Tue, 05 Oct 2010 10:15:43 -0700 (PDT)
Received: by 10.231.179.151 with HTTP; Tue, 5 Oct 2010 10:15:43 -0700 (PDT)
In-Reply-To: <4CAB3C26.3060502@stpeter.im>
References: <4CA81CB9.5020509@ericsson.com> <4CA9E5F9.8080209@stpeter.im> <AANLkTimH10=OumpbhzSRJ5dBnSp=D7DDOkLDrTxyaafu@mail.gmail.com> <4CAB3360.3000407@stpeter.im> <AANLkTink5dsbwAzVrX9hUNYKgtXDvymVVWQ6ODCgwQTs@mail.gmail.com> <4CAB3C26.3060502@stpeter.im>
Date: Wed, 06 Oct 2010 02:15:43 +0900
Message-ID: <AANLkTiniZ111r7K0fdZv+XS2pDvehJ7rXre4xJNMjaJ3@mail.gmail.com>
From: Jehan Pagès <jehan.marmottard@gmail.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: xmpp@ietf.org
Subject: Re: [xmpp] AD review: draft-ietf-xmpp-address-04
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Oct 2010 17:15:16 -0000

Hi,

2010/10/5 Peter Saint-Andre <stpeter@stpeter.im>:
> On 10/5/10 8:44 AM, Jehan Pagès wrote:
>> Hum... but if at the end, each protocol/technology does that (folding
>> back into their own spec), at the beginning, everyone will have the
>> same spec at first; but with time, this "consistent" approach to
>> internationalized name might derive in every different spec, hence
>> become "not so consistent" in the end. I think that's the point of
>> having a single RFC for all so that each technologies simply have to
>> reference it (instead of copying it then modifying it).
>
> I didn't say there would be a single RFC for internationalized strings
> in SASL, iSCSI, LDAP, XMPP, etc. The PRECIS WG is trying to define a
> common approach or framework that each technology can use by writing
> their own specifications. See here:
>
> http://tools.ietf.org/html/draft-blanchet-precis-problem-statement
>
> http://tools.ietf.org/html/draft-blanchet-precis-framework
>
> My input to that thought process was:
>
> http://tools.ietf.org/html/draft-saintandre-xmpp-i18n-01
>

Ok I see better.

>
>>> Hope that helps,
>>>
>>
>> It does, thanks. Still for someone wishing to implement right now
>> something from this, what would you advise then? Should I focus on
>> IDNA2003 only for now?
>
> Are you writing your own IDNA parser? Typically people use libidn.
>

I don't really know what I am doing exactly. For now I was rather
beginning to study what should be done or not, what exists already,
etc. So yes I'll have a look at libidn then. :-)
Thanks.

Jehan