Re: [Idr] [GROW] draft-snijders-idr-shutdown-00: Drop a line in the peer's syslog at shutdown

md@Linux.IT (Marco d'Itri) Wed, 16 November 2016 11:47 UTC

Return-Path: <md@Linux.IT>
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 2436A129692; Wed, 16 Nov 2016 03:47:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.879
X-Spam-Level:
X-Spam-Status: No, score=-0.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no 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 KG4X8HokPTkb; Wed, 16 Nov 2016 03:47:50 -0800 (PST)
Received: from attila.bofh.it (attila.bofh.it [IPv6:2001:4b78:2000::1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10014129485; Wed, 16 Nov 2016 03:39:01 -0800 (PST)
Received: by attila.bofh.it (Postfix, from userid 10) id 4CD701266F0; Wed, 16 Nov 2016 12:38:58 +0100 (CET)
Received: by bongo.bofh.it (Postfix, from userid 1000) id CBAFF2C01FE; Wed, 16 Nov 2016 12:38:49 +0100 (CET)
Date: Wed, 16 Nov 2016 12:38:49 +0100
Message-ID: <20161116113849.udbrfvdhaj3be7nx@bongo.bofh.it>
References: <20161116061556.GG1073@dhcp-9341.meeting.ietf.org> <20161116105535.GW79185@Space.Net> <1479295774707.77855@dacor.de>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="jfzoichjyvf2glhy"
Content-Disposition: inline
In-Reply-To: <1479295774707.77855@dacor.de>
User-Agent: NeoMutt/20161104 (1.7.1)
From: md@Linux.IT
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/PovK5QKjDOCq17wIVXYTNPINzS0>
Cc: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Subject: Re: [Idr] [GROW] draft-snijders-idr-shutdown-00: Drop a line in the peer's syslog at shutdown
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: Wed, 16 Nov 2016 11:47:51 -0000

On Nov 16, Julian Seifert <js@dacor.de> wrote:

> I agree with both points. Maybe not use utf8/unicode or reduce to only alphanumerics?
Not supporting UTF-8 is not acceptable for a new IETF protocol and would 
preclude using it in some cultures.

Customers with really crappy management infrastructure could ask their 
vendors to implement a knob to report the strings as base64, but 
I really wonder which real world use cases there are for this.

-- 
ciao,
Marco