Re: [Idr] Last Call: <draft-ietf-idr-shutdown-08.txt> (BGP Administrative Shutdown Communication) to Proposed Standard

"Jakob Heitz (jheitz)" <jheitz@cisco.com> Mon, 08 May 2017 19:13 UTC

Return-Path: <jheitz@cisco.com>
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 925C0129649; Mon, 8 May 2017 12:13:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level:
X-Spam-Status: No, score=-14.523 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 i55sqf4HX5Vd; Mon, 8 May 2017 12:13:42 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9F2A124D37; Mon, 8 May 2017 12:13:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3004; q=dns/txt; s=iport; t=1494270821; x=1495480421; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=wukmENlBzFNd+y7ItLBkWrEfBo13BiixpOu4wRuuwgo=; b=aORqdZWKQHC3y3jFJ1IpyH1F23EO0OBCYFVI2yHhwhzlFWNPpCiJUjr7 PfcORmzI0n3I3pVy59z/HJPjVSDaRdPwIYmyW7XhvptZr4UFgO/TTnaq1 xziP8gP8PltmqNefroOumSVsT9TXhpLPXUc8Yovp8E4ZuFhgOn8lh7dq0 A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DNAACCwhBZ/4QNJK1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1VigQwHjXmRV5Vygg8hC4V4AoRlPxgBAgEBAQEBAQFrKIUVAQE?= =?us-ascii?q?BAQMBATg0CwwEAgEIEQQBAQEeBQsnCx0IAgQBDQUIihgOtX+KdQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBARgFhl+BXoMbikwFnXkBhxuLc4INhTyKLJQ9AR84gQpwFUZ?= =?us-ascii?q?AhGmBSnaHXgGBDAEBAQ?=
X-IronPort-AV: E=Sophos;i="5.38,310,1491264000"; d="scan'208";a="245740763"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 08 May 2017 19:13:40 +0000
Received: from XCH-RCD-005.cisco.com (xch-rcd-005.cisco.com [173.37.102.15]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id v48JDeuZ013631 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 8 May 2017 19:13:40 GMT
Received: from xch-aln-014.cisco.com (173.36.7.24) by XCH-RCD-005.cisco.com (173.37.102.15) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 8 May 2017 14:13:39 -0500
Received: from xch-aln-014.cisco.com ([173.36.7.24]) by XCH-ALN-014.cisco.com ([173.36.7.24]) with mapi id 15.00.1210.000; Mon, 8 May 2017 14:13:39 -0500
From: "Jakob Heitz (jheitz)" <jheitz@cisco.com>
To: "Enke Chen (enkechen)" <enkechen@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>
CC: "draft-ietf-idr-shutdown@ietf.org" <draft-ietf-idr-shutdown@ietf.org>, "idr@ietf.org" <idr@ietf.org>, "idr-chairs@ietf.org" <idr-chairs@ietf.org>
Thread-Topic: [Idr] Last Call: <draft-ietf-idr-shutdown-08.txt> (BGP Administrative Shutdown Communication) to Proposed Standard
Thread-Index: AQHSxciggI3I1x2tSEiYPH6G0J5TkKHqIuMAgACuc/A=
Date: Mon, 8 May 2017 19:13:39 +0000
Message-ID: <a9996bc76e604acfbe797389ed0d81f6@XCH-ALN-014.cisco.com>
References: <149400686065.8457.16928207738917615877.idtracker@ietfa.amsl.com> <9d8cf31a-fc21-096b-543e-58750894a22a@cisco.com>
In-Reply-To: <9d8cf31a-fc21-096b-543e-58750894a22a@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [128.107.151.51]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/nGKJFK-CEH_w_4Ekk9ZOTMce6SA>
Subject: Re: [Idr] Last Call: <draft-ietf-idr-shutdown-08.txt> (BGP Administrative Shutdown Communication) to Proposed Standard
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: Mon, 08 May 2017 19:13:44 -0000

It is deliberately kept short to minimize the potential for abuse.
We could have argued about the length. Should it be 100, 120, 127,
but it's not an argument worth wasting time on.
Not using the whole range of the length byte opens the door to using
the rest of the range to indicate a future new information field.

Thanks,
Jakob.


> -----Original Message-----
> From: Enke Chen (enkechen)
> Sent: Sunday, May 07, 2017 8:44 PM
> To: ietf@ietf.org
> Cc: draft-ietf-idr-shutdown@ietf.org; idr@ietf.org; idr-chairs@ietf.org; Enke Chen (enkechen) <enkechen@cisco.com>
> Subject: Re: [Idr] Last Call: <draft-ietf-idr-shutdown-08.txt> (BGP Administrative Shutdown Communication) to
> Proposed Standard
> 
> Hi, Folks:
> 
> Just spotted this (apologies for not catching it earlier):
> 
> The draft specifies only 0 - 128 as valid in the one-octet length field.
> Not sure if there is a strong reason for such an apparent over-specification.
> 
> It seems to me that the spec can and should be simplified by removing the
> restriction, that is, to allow any value (0 - 255) to be valid.  That would
> also eliminate one error condition for the implementation.
> 
> Thanks.  -- Enke
> 
> ---
> 2.  Shutdown Communication
> 
> Length:  this 8-bit field represents the length of the Shutdown
>       Communication field in octets.  The length value MUST range from 0
>       to 128 inclusive.
> 
> 4.  Error Handling
> 
>    If a Shutdown Communication with an invalid Length value,
> ----
> 
> On 5/5/17 10:54 AM, The IESG wrote:
> >
> > The IESG has received a request from the Inter-Domain Routing WG (idr) to
> > consider the following document:
> > - 'BGP Administrative Shutdown Communication'
> >   <draft-ietf-idr-shutdown-08.txt> as Proposed Standard
> >
> > The IESG plans to make a decision in the next few weeks, and solicits
> > final comments on this action. Please send substantive comments to the
> > ietf@ietf.org mailing lists by 2017-05-19. Exceptionally, comments may be
> > sent to iesg@ietf.org instead. In either case, please retain the
> > beginning of the Subject line to allow automated sorting.
> >
> > Abstract
> >
> >
> >    This document enhances the BGP Cease NOTIFICATION message
> >    "Administrative Shutdown" and "Administrative Reset" subcodes for
> >    operators to transmit a short freeform message to describe why a BGP
> >    session was shutdown or reset.  This document updates RFC 4486.
> >
> >
> >
> >
> >
> > The file can be obtained via
> > https://datatracker.ietf.org/doc/draft-ietf-idr-shutdown/
> >
> > IESG discussion can be tracked via
> > https://datatracker.ietf.org/doc/draft-ietf-idr-shutdown/ballot/
> >
> >
> > No IPR declarations have been submitted directly on this I-D.
> >
> >
> >
> >
> > _______________________________________________
> > Idr mailing list
> > Idr@ietf.org
> > https://www.ietf.org/mailman/listinfo/idr
> >