[Jmap] Question regarding RFC 9007

Jonathan Harker <jon@jon.geek.nz> Sat, 10 April 2021 11:52 UTC

Return-Path: <jon@jon.geek.nz>
X-Original-To: jmap@ietfa.amsl.com
Delivered-To: jmap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 220553A2F4D for <jmap@ietfa.amsl.com>; Sat, 10 Apr 2021 04:52:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=jon.geek.nz
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 5QPJhZA0x-Ga for <jmap@ietfa.amsl.com>; Sat, 10 Apr 2021 04:52:04 -0700 (PDT)
Received: from debussy.pauken.co.uk (debussy.pauken.co.uk [80.87.131.62]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E50113A2F47 for <jmap@ietf.org>; Sat, 10 Apr 2021 04:52:02 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by debussy.pauken.co.uk (Postfix) with ESMTP id 33BC641FEC for <jmap@ietf.org>; Sat, 10 Apr 2021 12:52:00 +0100 (BST)
X-Virus-Scanned: Debian amavisd-new at debussy.pauken.co.uk
Received: from debussy.pauken.co.uk ([127.0.0.1]) by localhost (debussy.pauken.co.uk [127.0.0.1]) (amavisd-new, port 10024) with LMTP id E2fVK3Ow7kyc for <jmap@ietf.org>; Sat, 10 Apr 2021 12:51:58 +0100 (BST)
Received: from [192.168.101.87] (9.109.124.202.static.snap.net.nz [202.124.109.9]) by debussy.pauken.co.uk (Postfix) with ESMTPSA id 615B541FEB for <jmap@ietf.org>; Sat, 10 Apr 2021 12:51:56 +0100 (BST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=jon.geek.nz; s=mail; t=1618055518; bh=RKEvdKGE+/ptiNIqNNzDYJMH4qwiddOajRd/RXTFSQg=; h=To:Subject:From:Date:From; b=W4ZdYCH4/9J+idxuC65yrKc4j/sRF45l6AjLgQom4NInkwra5rnR99Ql440GrQaNt h8U4CyYUUl04ZO6iweZeTRlsIzIRCDv6aJHxn+HkS9QbzHyXCvNUbYwnyWmk1tu2Ij 4O8XIgBbvOXjo8EpDVXAfa1efoLk8WTWEAmuc+YU=
To: jmap@ietf.org
From: Jonathan Harker <jon@jon.geek.nz>
Message-ID: <c6ae4f06-78d1-a199-3c97-f4b483a35c7b@jon.geek.nz>
Date: Sat, 10 Apr 2021 23:51:54 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.9.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/6KYduziaSdiGf8ZjZCC9hX3E4TM>
X-Mailman-Approved-At: Sun, 11 Apr 2021 04:35:41 -0700
Subject: [Jmap] Question regarding RFC 9007
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: JSON Message Access Protocol <jmap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jmap>, <mailto:jmap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jmap/>
List-Post: <mailto:jmap@ietf.org>
List-Help: <mailto:jmap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jmap>, <mailto:jmap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Apr 2021 11:54:14 -0000

Hi,

Whilst I can't wait to use JMAP in production some time, I'm just 
wondering why the IETF is still using Python 2.7 to (fail to) parse UTF8 
in 2021?

https://tools.ietf.org/html/rfc9007

UnicodeDecodeError:
     'ascii' codec can't decode byte 0xc3 in position 5: ordinal not in 
range(128)
     'Raphaël Ouazana <rouazana@linagora.com>'