Re: [Idr] WG Adoption call for draft-snijders-idr-shutdown (11/16 to 11/30)

Jeffrey Haas <jhaas@pfrc.org> Mon, 21 November 2016 18:23 UTC

Return-Path: <jhaas@pfrc.org>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21900129B3E for <idr@ietfa.amsl.com>; Mon, 21 Nov 2016 10:23:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.398
X-Spam-Level:
X-Spam-Status: No, score=-3.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-1.497, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham 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 hzPQjHoUoPAx for <idr@ietfa.amsl.com>; Mon, 21 Nov 2016 10:23:22 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 6DA88129603 for <idr@ietf.org>; Mon, 21 Nov 2016 10:23:21 -0800 (PST)
Received: from dresden.attlocal.net (99-59-193-67.lightspeed.livnmi.sbcglobal.net [99.59.193.67]) by slice.pfrc.org (Postfix) with ESMTPSA id 510291E337; Mon, 21 Nov 2016 13:26:25 -0500 (EST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_63B0BC3C-39EF-41EB-81A8-2578F362D352"
Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\))
From: Jeffrey Haas <jhaas@pfrc.org>
In-Reply-To: <CAJL_ZMPTLUNLo6MVLM8Gtu4k+KvPJwzKWE7P6YPmuzUax3a2tA@mail.gmail.com>
Date: Mon, 21 Nov 2016 13:23:20 -0500
Message-Id: <2A27EAB2-2057-4BC5-9D47-49316D58D601@pfrc.org>
References: <013f01d2404d$3dfff610$b9ffe230$@ndzh.com> <39991BB5-28C6-414F-A1BE-F5132DE2E012@microsoft.com> <20161121165418.GI1236@Hanna.local> <CAJL_ZMPTLUNLo6MVLM8Gtu4k+KvPJwzKWE7P6YPmuzUax3a2tA@mail.gmail.com>
To: jim deleskie <deleskie@gmail.com>
X-Mailer: Apple Mail (2.3251)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/AN-67QvrCVGulm421q6LjUKnIiM>
Cc: idr wg <idr@ietf.org>
Subject: Re: [Idr] WG Adoption call for draft-snijders-idr-shutdown (11/16 to 11/30)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Nov 2016 18:23:28 -0000

Jim,

> On Nov 21, 2016, at 1:03 PM, jim deleskie <deleskie@gmail.com> wrote:
> 
> I understand people may want the characters in their language, but is there a technical reason for UTF-8, like many of you I've worked with many engineers, in ehe past 20 years,for who english is not their native language. I suspect many of those of you that know me have questioned if it is mine :)  However  these engineers typically, while thinking in their first language, "work" in english, as its the defacto standard, much like with air travel.
> 
> 

Minimally, the IESG tends to require that anything that contains textual strings use UTF-8 encoding.  Internationalization needs to be considered up front in IETF protocol and related work.  Whether an implementation chooses to support a subset of behaviors is up to the implementors.  (E.g. ASCII only.)

-- Jeff