IETF Logo Mail Archive

Re: [Idr] draft-snijders-idr-rfc8203bis

Jeffrey Haas <jhaas@pfrc.org> Thu, 14 December 2017 17:43 UTC

Return-Path: <jhaas@pfrc.org>
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 6D3D9129435 for <idr@ietfa.amsl.com>; Thu, 14 Dec 2017 09:43:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 5Nwe5Xc4XX3j for <idr@ietfa.amsl.com>; Thu, 14 Dec 2017 09:43:31 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id EF849128616 for <idr@ietf.org>; Thu, 14 Dec 2017 09:43:30 -0800 (PST)
Received: from dresden.attlocal.net (99-59-193-67.lightspeed.livnmi.sbcglobal.net [99.59.193.67]) by slice.pfrc.org (Postfix) with ESMTPSA id 83A481E33E; Thu, 14 Dec 2017 12:47:26 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Jeffrey Haas <jhaas@pfrc.org>
In-Reply-To: <20171214171446.GN95845@vurt.meerval.net>
Date: Thu, 14 Dec 2017 12:43:29 -0500
Cc: bruno.decraene@orange.com, "idr@ietf.org" <idr@ietf.org>, Peter Hessler <phessler@theapt.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <4D213F3F-DAC8-4F18-ABA6-517A8213BFA7@pfrc.org>
References: <20171208154735.GH61799@vurt.meerval.net> <3238CB61-EDB3-4C5D-813D-AC19362AB2CF@puck.nether.net> <CAEm8Q109fbvUuCMOOvnDBianMnTsYR9zdBzp-Jc84uVYt03TUA@mail.gmail.com> <20171214160102.GS37665@gir.theapt.org> <13067_1513271281_5A32AFF1_13067_469_1_53C29892C857584299CBF5D05346208A479212FF@OPEXCLILM21.corporate.adroot.infra.ftgroup> <20171214171446.GN95845@vurt.meerval.net>
To: Job Snijders <job@ntt.net>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/uYl6fICUeDiTFFC7BmfTrw5wZx8>
Subject: Re: [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: Thu, 14 Dec 2017 17:43:32 -0000

> On Dec 14, 2017, at 12:14 PM, Job Snijders <job@ntt.net> wrote:
> 
> On Thu, Dec 14, 2017 at 05:08:00PM +0000, bruno.decraene@orange.com wrote:
>>> From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Peter Hessler
>>> The len field is 8 bits, which allows for a max of 255.
>>> 
>>> If longer is desired, then we'll need a new error code point.
>> 
>> Alternatively, another field may be added after the existing "Shutdown
>> Communication" field.  Either as a replacement (setting the length of
>> the first field to zero) or as a concatenation. 
> 
> Bruno is right (of course, since the length field was his idea to begin
> with :-), there are options available to extend beyond 255 if needed.

If the limit was 127 rather than 128, the top bit could have been used. 

The closest thing that can be done will depend partly on what deployed implementations do when 128 is exceed.  The spec says nothing right now... and thus you might not do anything beyond saying "up to 255 is fine".  

To get beyond 255, the simplest but gross one is to say "there may be a second message after the shutdown communication field".

-- Jeff (and people wonder why I'm pushy about using large "length" fields.)

v2.23.0 | Report a Bug | By Email