Re: [DNSOP] I-D Action: draft-ietf-dnsop-extended-error-03.txt

Jared Mauch <jared@puck.nether.net> Fri, 21 December 2018 16:49 UTC

Return-Path: <jared@puck.nether.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C75FB130E82 for <dnsop@ietfa.amsl.com>; Fri, 21 Dec 2018 08:49:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 4wCrU4D3Gj6T for <dnsop@ietfa.amsl.com>; Fri, 21 Dec 2018 08:49:02 -0800 (PST)
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C06E0130E9A for <dnsop@ietf.org>; Fri, 21 Dec 2018 08:49:02 -0800 (PST)
Received: from [IPv6:2603:3015:3606:cbe1:f4d8:310e:405a:3c4f] (unknown [IPv6:2603:3015:3606:cbe1:f4d8:310e:405a:3c4f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id DBA48541182; Fri, 21 Dec 2018 11:49:00 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <yblwoo3bxah.fsf@w7.hardakers.net>
Date: Fri, 21 Dec 2018 11:49:00 -0500
Cc: dnsop@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <48B3C12B-DE2A-4008-8E4E-D1C508C762BF@puck.nether.net>
References: <154534677023.19023.8195828695262063685@ietfa.amsl.com> <yblwoo3bxah.fsf@w7.hardakers.net>
To: Wes Hardaker <wjhns1@hardakers.net>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/0xoyn4A5_pHf_Gl6eptm4jjZ5gs>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-extended-error-03.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Dec 2018 16:49:11 -0000


> On Dec 20, 2018, at 6:20 PM, Wes Hardaker <wjhns1@hardakers.net>; wrote:
> 
> 1.5 DONE encoding of the EXTRA-TEXT field
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 
>  In any case, I think the encoding of this field should be specified as
>  either ASCII or UTF-8. I prefer UTF-8, because otherwise I won't be
>  able to send back 🤯 emoji in error messages (and the authors won't be
>  able to use the 🍄 emoji that they clearly want).
> 
>  + Resolution: we're proposing ASCII to keep the protocol simple and to
>    match TXT records.  These are not intended to be end user messages
>    but rather administrative hints for operators.
> 
>  + resulting text:
> 
>    A variable length, ASCII encoded, EXTRA-TEXT field holding
>    additional textual information. It may be zero length when no
>    additional textual information is included.
> 

We went through some of this in IDR about routing protocols and how to leave
a partner device a message.  UTF-8 is the supported method.  7-bit ASCII lacks
language support.

- Jared