Re: [I18nrp] Appropriate status for draft-faltstrom-unicode11-05
"Patrik Fältström " <paf@frobbit.se> Wed, 05 December 2018 08:03 UTC
Return-Path: <paf@frobbit.se>
X-Original-To: i18nrp@ietfa.amsl.com
Delivered-To: i18nrp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id 1B948129533
for <i18nrp@ietfa.amsl.com>; Wed, 5 Dec 2018 00:03:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.722
X-Spam-Level:
X-Spam-Status: No, score=-1.722 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, FROM_EXCESS_BASE64=0.979, RCVD_IN_DNSWL_LOW=-0.7,
SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key)
header.d=frobbit.se
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 G7c2KFmV8mwf for <i18nrp@ietfa.amsl.com>;
Wed, 5 Dec 2018 00:03:51 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.185])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 7A0D0124D68
for <i18nrp@ietf.org>; Wed, 5 Dec 2018 00:03:51 -0800 (PST)
Received: from [77.72.226.228] (unknown
[IPv6:2a01:3f0:1:0:a812:db3b:3bc3:c7a8])
by mail.frobbit.se (Postfix) with ESMTPSA id 6DD4F234E0;
Wed, 5 Dec 2018 09:03:49 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=frobbit.se; s=mail;
t=1543997029; bh=WhaFgj51d29mHh8fO3nVrCsbez9wOGUh+eUNKQL2Qn4=;
h=From:To:Cc:Subject:Date:In-Reply-To:References:From;
b=iTakxdZuQUHBxQPgI9Oo32kYMChKB+h46/Df4u1oiYzF7/GwFPZz26nqOIHYwvF5d
gslZMgcBQ6NqO2kIAg7sez88gxTaY8bHeQa8EwNEYeWAoKEbsV90aD7MPfBsvBESEt
jtDXSkf3wupMWnriMVSyIBidevZlbz+BIqPy/Y90=
From: "Patrik =?utf-8?b?RsOkbHRzdHLDtm0=?=" <paf@frobbit.se>
To: "Ted Hardie" <ted.ietf@gmail.com>
Cc: i18nrp@ietf.org
Date: Wed, 05 Dec 2018 09:03:48 +0100
X-Mailer: MailMate (1.12.2r5568)
Message-ID: <4453AC3F-F50C-4DC1-BFF1-9DBE55CBD7F4@frobbit.se>
In-Reply-To: <CA+9kkMCwTy=kVw22kBBmog+7aKeNf_kdVtWJ3EKdy1m8BHPkYw@mail.gmail.com>
References: <CA+9kkMCwTy=kVw22kBBmog+7aKeNf_kdVtWJ3EKdy1m8BHPkYw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed;
boundary="=_MailMate_3DC7DB25-A917-4BC6-BFC1-74713C61BAE6_=";
micalg=pgp-sha1; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18nrp/XIc9O9F0BryLHzpT7DVA27wcUEQ>
Subject: Re: [I18nrp] Appropriate status for draft-faltstrom-unicode11-05
X-BeenThere: i18nrp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Internationalization Review Procedures <i18nrp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i18nrp>,
<mailto:i18nrp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i18nrp/>
List-Post: <mailto:i18nrp@ietf.org>
List-Help: <mailto:i18nrp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i18nrp>,
<mailto:i18nrp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Dec 2018 08:03:53 -0000
On 4 Dec 2018, at 22:18, Ted Hardie wrote: > The simplest way to do that, though, would be to mark 6452 as historic. I disagree. I think it is important to have it recorded that IETF for Unicode version 6.0 decided to explicitly follow the Unicode Standard. Just like this draft of mine when becoming an RFC says the same to Unicode 11.0.0. These two could be historic together with a complete new document replacing not only these two but also for example 5892. To conclude: after following the discussions my view is that even if this draft suggest not to update 5892, it could have done so, and because of that this draft of mine IS an update to 5892. Just like 6452 is. But of course I will as an author follow whatever the outcome of this discussion will be. Patrik
- [I18nrp] Appropriate status for draft-faltstrom-u… Ted Hardie
- Re: [I18nrp] Appropriate status for draft-faltstr… Patrik Fältström
- Re: [I18nrp] Appropriate status for draft-faltstr… Asmus Freytag
- Re: [I18nrp] Appropriate status for draft-faltstr… Ted Hardie