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

Enke Chen <enkechen@cisco.com> Mon, 08 May 2017 03:43 UTC

Return-Path: <enkechen@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 A903412025C; Sun, 7 May 2017 20:43:59 -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 N95JqMe6N0Un; Sun, 7 May 2017 20:43:58 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1CF8120046; Sun, 7 May 2017 20:43:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2130; q=dns/txt; s=iport; t=1494215038; x=1495424638; h=subject:references:cc:to:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=LYH46W9o2esjrq0H0tHZcx/6S3jShixYQ4+vB29E5gY=; b=EHbGSokBplOCQKk5tEHZG6vFHHN2hQsE6WAGfqwWzEH8UPkD5Iu9h6kS 0u6mWj4m1mze9clX4nDRjKxKytdZsnOE+33A8zM9N8Am2KtJkcKLJBDk6 FvBUEvf4OY1I1Ngt/0HdtMa2LHdtuMuJ5Y216mIjXQnxgriIGjnMw2Hk+ Q=;
X-IronPort-AV: E=Sophos;i="5.38,307,1491264000"; d="scan'208";a="418118842"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 May 2017 03:43:57 +0000
Received: from [10.24.44.82] ([10.24.44.82]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id v483hurm014391; Mon, 8 May 2017 03:43:56 GMT
References: <149400686065.8457.16928207738917615877.idtracker@ietfa.amsl.com>
Cc: draft-ietf-idr-shutdown@ietf.org, idr@ietf.org, idr-chairs@ietf.org, Enke Chen <enkechen@cisco.com>
To: ietf@ietf.org
From: Enke Chen <enkechen@cisco.com>
Message-ID: <9d8cf31a-fc21-096b-543e-58750894a22a@cisco.com>
Date: Sun, 7 May 2017 20:43:56 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <149400686065.8457.16928207738917615877.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/9PULAni_V_tdwCUhfPiDgAJz7eA>
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 03:44:00 -0000

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
>