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

Job Snijders <job@instituut.net> Fri, 18 November 2016 08:46 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 959BE12953C for <idr@ietfa.amsl.com>; Fri, 18 Nov 2016 00:46:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=instituut-net.20150623.gappssmtp.com
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 7qXc_yJ_JFQs for <idr@ietfa.amsl.com>; Fri, 18 Nov 2016 00:46:09 -0800 (PST)
Received: from mail-oi0-x231.google.com (mail-oi0-x231.google.com [IPv6:2607:f8b0:4003:c06::231]) (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 B62AD1295B4 for <idr@ietf.org>; Fri, 18 Nov 2016 00:46:08 -0800 (PST)
Received: by mail-oi0-x231.google.com with SMTP id z62so81845673oiz.1 for <idr@ietf.org>; Fri, 18 Nov 2016 00:46:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=instituut-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=4BllRRNqRIl/G1itSmRKxAjOoxrdbELguU4Bbl/ZmW4=; b=iaOGjq3etFPf4RQPNBfIs/YsyMGa26ShnN1/+AyJyZAX1bbKX7B2+djF/nYd0yHGgm 9+YKAl1M2P/Rpmff/RsSWtU27MnkCdcm/G8eoDObYI/QIAkPDRQRxhpxDiwOzxutr9qq Zui1hr+qoxa9+BtjuZB+K3SkA+2ejgsMVMU8OM0BFAExWuKMnRNqS4Xy7HK1OyOVHGN8 mwfrah4Yjl29qsrfZEOWY24xZll6w5KhacLcx7+cMG8n02Eu4EsaBdPM/LcMQ8Nm/nl+ EQyD0zu92y7dmWoU2ETBAFuZq/YIS1lmJCEjDyXyh5Sb8/zgU/DoX6NxsylzVGxUGF2k xVmg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=4BllRRNqRIl/G1itSmRKxAjOoxrdbELguU4Bbl/ZmW4=; b=QpHsiaCkB51xgGqO+Yp5D1lkmouv0z6Hn802T1FNxcZ9DCOeMcN1iDMuOIkEYt4l1v 7u2GsxX2ov02TuEfAnKYFf0FRqalIUDd7StAHYDNiA47srthRb1EnNsuvPJSVCeAcRhw UEsitg1rINpVYnylYKx9j+hmduVZPNH3o7HEPxh8QE6q+YQJH9MkiCqE8eci7UI9ECCL ZkLYApKgptzWHodUw89AEP74gyQYB4fVjRMwURRL+RxztMRDjpFP0jNtQ7biX0f0hWjb xDzxO9bBXv5ppX5g2tkG5egi8UL1HFqrZJFAR0P9gE+jY50KOzpw5AB74FpplPAbviGz zwtw==
X-Gm-Message-State: AKaTC03i3pamVr9gCGMb1y5jeVmys6d9DVsBzIcRdkT5dqeQ4T3VCWyK/KWX58FJVXGSGssshu7cOBlPp3HPFw==
X-Received: by 10.157.48.112 with SMTP id w45mr4080489otd.198.1479458767975; Fri, 18 Nov 2016 00:46:07 -0800 (PST)
MIME-Version: 1.0
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>
In-Reply-To: <16418_1479457940_582EBC93_16418_290_1_53C29892C857584299CBF5D05346208A1EC8DEA5@OPEXCLILM21.corporate.adroot.infra.ftgroup>
From: Job Snijders <job@instituut.net>
Date: Fri, 18 Nov 2016 08:45:56 +0000
Message-ID: <CACWOCC8ENYuX2LeJKWP0tmMoCPJ4J-qxJjOXiHHLaP8Fqe4USg@mail.gmail.com>
To: bruno.decraene@orange.com
Content-Type: multipart/alternative; boundary="001a1141f8705345a405418f5679"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/O61WxdmdP8qb7KXsoiV3DBuwC8g>
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: Fri, 18 Nov 2016 08:46:11 -0000

Hi Bruno,

John Scudder was kind enough to provide extensive argumentation offlist on
why something along these lines should be done. We'll work on a proposal.
The length indicator is a neat idea, thanks for sharing.

Job

On Fri, 18 Nov 2016 at 17:32, <bruno.decraene@orange.com> wrote:

>
>
> > From: Job Snijders [mailto:job@instituut.net]  > Sent: Friday, November
> 18, 2016 1:46 AM
> >
>  > On Thu, Nov 17, 2016 at 04:28:50PM +0000, bruno.decraene@orange.com
> wrote:
>  > > I support the draft.
>  > > I also support Jeff's idea to re-use existing sub-code(s).
>  >
>  > Thanks for your support. Based on the feedback received so far the next
>  > version of this draft will recycle Cease subcode 2.
>  >
>  > > 1 possible comment: the length of the "Shutdown Communication" field
>  > > seems implied from the length of the data field, rather than being
>  > > explicitly indicated.
>  >
>  > The text is explicit about the length:
>  >
>  >     "followed by a freeform UTF-8 encoded string with a REQUIRED maximum
>  >     length of 128 octets. "
>  >
>  > and further:
>  >
>  >     "This document tries to minimize the effects of visual spoofing by
>  >     allowing UNICODE only where local script is expected and needed, and
>  >     by limiting the length of the Shutdown Communication."
>  >
>  > > If so, it seems that we are closing the possibility to advertise
>  > > additional data/usage, in some future. What about adding a TLV format?
>  >
>  > I object to using a TLV. Don't forget this is already at a TLV level:
>  > Cease NOTIFICATION. If one would want to define a TLV inside this TLV, a
>  > new Cease subcode can be requested from IANA.
>
> What if someone needs to advertise additional info to an existing cease
> subcode? cf Jeff's email regarding the pain of changing subcodes.
> So let's forget about the TLV. What about just adding the length of the
> string? This would still allow adding fields after the string, while having
> a negligible/null cost?
>
> Kind regards,
> -- Bruno
>
>  > Kind regards,
>  >
>  > Job
>
>
> _________________________________________________________________________________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez
> recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
> electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou
> falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged
> information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and
> delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been
> modified, changed or falsified.
> Thank you.
>
>