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

Job Snijders <job@ntt.net> Sat, 19 November 2016 12:11 UTC

Return-Path: <job@ntt.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 E89F8129860 for <idr@ietfa.amsl.com>; Sat, 19 Nov 2016 04:11:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.432
X-Spam-Level:
X-Spam-Status: No, score=-3.432 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.497, SPF_SOFTFAIL=0.665] 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 hjse8DFMFClg for <idr@ietfa.amsl.com>; Sat, 19 Nov 2016 04:11:22 -0800 (PST)
Received: from mail3.mlpsca01.us.to.gin.ntt.net (mail3.mlpsca01.us.to.gin.ntt.net [IPv6:2001:418:3ff:3::22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98AA11296A4 for <idr@ietf.org>; Sat, 19 Nov 2016 04:11:22 -0800 (PST)
Received: by mail3.mlpsca01.us.to.gin.ntt.net with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <job@ntt.net>) id 1c84UJ-0006yo-6T (job@us.ntt.net); Sat, 19 Nov 2016 12:11:22 +0000
Date: Sat, 19 Nov 2016 13:11:15 +0100
From: Job Snijders <job@ntt.net>
To: idr@ietf.org
Message-ID: <20161119121115.GA47336@dhcp-9d92.meeting.ietf.org>
References: <20161116061556.GG1073@dhcp-9341.meeting.ietf.org> <20161117013640.GB6217@pfrc.org> <16426_1479400131_582DDAC3_16426_1669_1_53C29892C857584299CBF5D05346208A1EC87201@OPEXCNORM2F.corporate.adroot.infra.ftgroup> <20161118004548.GK1072@dhcp-9341.meeting.ietf.org> <16418_1479457940_582EBC93_16418_290_1_53C29892C857584299CBF5D05346208A1EC8DEA5@OPEXCLILM21.corporate.adroot.infra.ftgroup> <CACWOCC8ENYuX2LeJKWP0tmMoCPJ4J-qxJjOXiHHLaP8Fqe4USg@mail.gmail.com> <13357_1479459134_582EC13E_13357_5786_1_53C29892C857584299CBF5D05346208A1EC8FF18@OPEXCLILM21.corporate.adroot.infra.ftgroup> <37224750-4065-40E3-B6F4-571DED698563@cisco.com> <20161119103226.GN1072@dhcp-9341.meeting.ietf.org> <CA+b+ERkAowcpeCL=_XEX1piNP__TVDdX3Lhvp8qYJSPvivoG1w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CA+b+ERkAowcpeCL=_XEX1piNP__TVDdX3Lhvp8qYJSPvivoG1w@mail.gmail.com>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.7.1 (2016-10-04)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/udI1U4bHeSXMdLZya9U5kAlKW3U>
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: Sat, 19 Nov 2016 12:11:24 -0000

Hi Robert,

On Sat, Nov 19, 2016 at 12:24:51PM +0100, Robert Raszuk wrote:
> The alternative to the below which could be attractive both to senders and
> receivers is indirection ... meaning that we would only extend current
> cease sub 2 with say 21 octets which would be basic UTF8 string of URL
> shortcut: https://goo.gl/V5as9h 

While I am aware that David Wheeler said: "All problems in computer
science can be solved by another level of indirection", there are some
practicalities to be considered:

    https://www.schneier.com/blog/archives/2016/04/security_risks_11.html
    https://freedom-to-tinker.com/2016/04/14/gone-in-six-characters-short-urls-considered-harmful-for-cloud-services/
    https://www.cs.cornell.edu/~shmat/shmat_urls.pdf

In addition to that, the user behind the router which received the
Shutdown Communication might no longer have access to the web due to
that shutdown event.

> That way anyone receiving the link in the cease admin down or any
> other sub type can click on it and read any arbitrary info or even get
> guide how to configure his peer to say support new peering types being
> currently prepared for cooking.

Ofcourse, people are free to put a URL in the 128 octets worth of
Shutdown Communication. This is for the operators to decide.

Kind regards,

Job