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

Joe Abley <jabley@hopcount.ca> Fri, 21 December 2018 17:25 UTC

Return-Path: <jabley@hopcount.ca>
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 2524A130EE4 for <dnsop@ietfa.amsl.com>; Fri, 21 Dec 2018 09:25:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopcount.ca
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 B78z7appoTZr for <dnsop@ietfa.amsl.com>; Fri, 21 Dec 2018 09:25:32 -0800 (PST)
Received: from mail-qk1-x736.google.com (mail-qk1-x736.google.com [IPv6:2607:f8b0:4864:20::736]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38EB3130EDF for <dnsop@ietf.org>; Fri, 21 Dec 2018 09:25:32 -0800 (PST)
Received: by mail-qk1-x736.google.com with SMTP id q1so3497948qkf.13 for <dnsop@ietf.org>; Fri, 21 Dec 2018 09:25:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=E59XZD+Qua9O79vIpS5voKVUO/DwA6tib7P39dqVhDQ=; b=ljrHaS1Tj4ozKCGIK02HYBmrpkx6U4+GWP9/a6ECYZHWfV5GdOJy8QnpdljxmboOKX wHHvZUf+LfR3Hzl86L4/sR0eG4q5gyZKiG49RBWQiKguYUkCrksTEtuwP0wXmgFj6p7s XsNDt+y1WCklQ5/pnrADSX3XehaB0jp6v6QRE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=E59XZD+Qua9O79vIpS5voKVUO/DwA6tib7P39dqVhDQ=; b=GVou+/zxequ0K5PN12Qe2TwcpGObHb0QoiS2ceHK85ovWE75U7x39qM9a4XJnRvj3o +vG4+zdP/qhXMXZxtoWfn8RcdbQijlN3YCWAJvBCm8U0MyCNaQitkMgsM8muXq5f81wp WKqJ12iMwL46YwEFcz61MdCLc1bHckwJ4GYnCJ223Ys2MueBQCmTJ0jO1kADv5CV0h2p l6EV1VVFqeaklsw5FrCNNsmVZNPk1RNUtOSf6Auu4q/aA6xtMjnFzKe53c0nwDkO8OGa 3kBlBNCueGoG76urku9BpPNXCCqElqMK3PQw/eJl7AqcNN6o2qt1oPzAJkfB5Kjtevvz WuTw==
X-Gm-Message-State: AJcUukcfmpqB+/HsqGZ8ld9s2ZmKiNHdmqagNqQAkrHJelWJnT0398xb QA8oleQ2vG/OL8sMLb9KSYJG6w==
X-Google-Smtp-Source: ALg8bN4kfGVe7A+CP7gLtn7JIPrWtrDVzyHNIxpJ1haIlZyF/F7OqWsZVLfW7+onn4Y09f6WCKBhLA==
X-Received: by 2002:a37:8ac3:: with SMTP id m186mr3090241qkd.263.1545413131282; Fri, 21 Dec 2018 09:25:31 -0800 (PST)
Received: from ?IPv6:2607:f2c0:101:3:38d6:711f:f311:7231? ([2607:f2c0:101:3:38d6:711f:f311:7231]) by smtp.gmail.com with ESMTPSA id g25sm4735019qki.29.2018.12.21.09.25.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 21 Dec 2018 09:25:30 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.1 \(3445.101.1\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <48B3C12B-DE2A-4008-8E4E-D1C508C762BF@puck.nether.net>
Date: Fri, 21 Dec 2018 12:25:28 -0500
Cc: Wes Hardaker <wjhns1@hardakers.net>, dnsop@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <A23C42BF-737B-4729-9153-AF18AB00F77B@hopcount.ca>
References: <154534677023.19023.8195828695262063685@ietfa.amsl.com> <yblwoo3bxah.fsf@w7.hardakers.net> <48B3C12B-DE2A-4008-8E4E-D1C508C762BF@puck.nether.net>
To: Jared Mauch <jared@puck.nether.net>
X-Mailer: Apple Mail (2.3445.101.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/B24n5iIVZaEeNrDCDmB4YHmVFJ8>
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 17:25:41 -0000


On 21 Dec 2018, at 11:49, Jared Mauch <jared@puck.nether.net>; wrote:

> On Dec 20, 2018, at 6:20 PM, Wes Hardaker <wjhns1@hardakers.net>; wrote:
> 
>> + 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.

Isn't there some standing IAB advice on this kind of thing, and doesn't it strongly recommend UTF-8? Using UTF-8 would also simplify the transformation of DNS wire-format parameters into other formats like XML or JSON. Administrative hints for operators still need to be human-readable (operators are humans, too!)

All of these issues and more are elegantly eliminated by specifying UTF-8. Conversely, I don't see a problem that is solved by choosing US-ASCII.


Joe