[Idr] draft-snijders-idr-rfc8203bis

Job Snijders <job@ntt.net> Fri, 08 December 2017 15:47 UTC

Return-Path: <job@instituut.net>
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 4D73B126B6D for <idr@ietfa.amsl.com>; Fri, 8 Dec 2017 07:47:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.418
X-Spam-Level:
X-Spam-Status: No, score=-1.418 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, UNPARSEABLE_RELAY=0.001] 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 MUVt3w9ut79D for <idr@ietfa.amsl.com>; Fri, 8 Dec 2017 07:47:37 -0800 (PST)
Received: from mail-lf0-f42.google.com (mail-lf0-f42.google.com [209.85.215.42]) (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 384331243F6 for <idr@ietf.org>; Fri, 8 Dec 2017 07:47:37 -0800 (PST)
Received: by mail-lf0-f42.google.com with SMTP id 74so12347193lfs.0 for <idr@ietf.org>; Fri, 08 Dec 2017 07:47:36 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-disposition:user-agent; bh=9FTacRVetZhcVP1SbXzfLsANVxBhlpHYMWPBt65WI9U=; b=t75YfT+PtWN0jsLXc17IvFX2HMZUE9L0lKRS20lKJrNKO9E/lZIkywRAxkKK2aABgC FUS78fAWd6bqEivLFhLZpLUJYgC2srd0MzVqDcqtCR1T7p4CT0ie/u92PP0CdAbmfKYn /ylWHmpjkNwG3ZJYUXTSc3wPRRYW+Aoz7v4PmJtGMbC6ZkmJHI+dc1vxmJpmKDAmcCQB BIotLLnjqu+wpsBhQ7Weorbdi5FJiJrQCNBPAWAS+nfxjqj7hE697AHVN2a1s/y0XXN7 UZOGAHvTEJOoZxxk4yVX2QuWWcXDCQXqJS99TzIChmy1XGD734GkF1QYIek/pu7U/4Sd B/mQ==
X-Gm-Message-State: AJaThX6+Fzai4lPfCVqqnEazjlJM08CQP4NAwg0nBv7y08kPBDtWL3r7 sRrfgU2Khue0/DZMWgqNjt2wxVRXpxQ=
X-Google-Smtp-Source: AGs4zMYei6gvxT9zz9PfYGRHqDz3f04YSkY/h5ucUdk53j6YHZ+bsDibhnbcQgDkwZDMicjfmWuMwQ==
X-Received: by 10.46.17.70 with SMTP id f67mr15873539lje.160.1512748055065; Fri, 08 Dec 2017 07:47:35 -0800 (PST)
Received: from vurt.meerval.net ([95.143.124.62]) by smtp.gmail.com with ESMTPSA id u27sm1489862ljd.70.2017.12.08.07.47.33 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 08 Dec 2017 07:47:34 -0800 (PST)
Received: from localhost (vurt.meerval.net [local]) by vurt.meerval.net (OpenSMTPD) with ESMTPA id 3e05f48c; Fri, 8 Dec 2017 15:47:35 +0000 (UTC)
Date: Fri, 08 Dec 2017 15:47:35 +0000
From: Job Snijders <job@ntt.net>
To: idr@ietf.org
Message-ID: <20171208154735.GH61799@vurt.meerval.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.9.1 (2017-09-22)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/HmmNkdT0PQq6suUbwv-7QTkopT4>
Subject: [Idr] draft-snijders-idr-rfc8203bis
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 08 Dec 2017 15:47:39 -0000

Dear IDR,

So, it appears I was wrong to push for the arbitrary maximum length of
128 octets when we worked on the BGP Administrative Shutdown
Communication (RFC 8203). At the time, multiple people pointed out that
it might be better to let the the thing be a little bit longer (255),
and in retrospect that indeed would've been better. I'm sorry :(

At this month's peering forum meeting of the Moscow Internet Exchange,
Misha Grishin (MSK-IX) reported on experiences with the shutdown
communication, and indicated that the concept was considered useful, but
that 128 octets is too small in context of multibyte character sets such
as Cyrillic script and they couldn't easily fit the short messages they
wanted to send in the communication. The GoBGP authors also questioned
the 128 limit during the implementation phase, I now see why.
Operational feedback like this is invaluable and worth our
consideration.

I think that allowing all possible values in the shutdown communication
length field will allow more societies to use the shutdown communication
feature in their native script, and this outweights the additional risk
of visual spoofing that an additional 127 octets could bring. I think
it won't be too hard to update the existing implementations.

We've posted a short draft to update use of the length field in rfc8203.

Thoughts?

Kind regards,

Job

----- Forwarded message from internet-drafts@ietf.org -----

Date: Fri, 08 Dec 2017 07:22:57 -0800
From: internet-drafts@ietf.org
To: Job Snijders <job@ntt.net>, Alexander Azimov <aa@qrator.net>
Subject: New Version Notification for draft-snijders-idr-rfc8203bis-00.txt


A new version of I-D, draft-snijders-idr-rfc8203bis-00.txt
has been successfully submitted by Job Snijders and posted to the
IETF repository.

Name:		draft-snijders-idr-rfc8203bis
Revision:	00
Title:		Extended BGP Administrative Shutdown Communication
Document date:	2017-12-07
Group:		Individual Submission
Pages:		4
URL:            https://www.ietf.org/internet-drafts/draft-snijders-idr-rfc8203bis-00.txt
Status:         https://datatracker.ietf.org/doc/draft-snijders-idr-rfc8203bis/
Htmlized:       https://tools.ietf.org/html/draft-snijders-idr-rfc8203bis-00
Htmlized:       https://datatracker.ietf.org/doc/html/draft-snijders-idr-rfc8203bis-00


Abstract:
   This document updates RFC8203 by defining an Extended BGP
   Administrative Shutdown Communication to improve communication using
   multibyte character sets.


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat


----- End forwarded message -----