Re: [sfc] TTL field within the NSH base header
"Andrew G. Malis" <agmalis@gmail.com> Thu, 27 April 2017 21:00 UTC
Return-Path: <agmalis@gmail.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40D08129C49 for <sfc@ietfa.amsl.com>; Thu, 27 Apr 2017 14:00:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 esg605jpuRs7 for <sfc@ietfa.amsl.com>; Thu, 27 Apr 2017 14:00:24 -0700 (PDT)
Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::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 03055129BBE for <sfc@ietf.org>; Thu, 27 Apr 2017 13:56:15 -0700 (PDT)
Received: by mail-it0-x231.google.com with SMTP id g66so25053552ite.1 for <sfc@ietf.org>; Thu, 27 Apr 2017 13:56:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=RgO6GjCwfYvVYjBU4LlLzSqEmojc1b0IeppzCvIVG8E=; b=GsPWbueegqHTpyYMG5O9f+5FgtsJFk3X7AGD6uxOKAUzUMnrxpahLfQeyAz+TN/L33 1/UiLwGQ9gAgtt4dFBCKTMK+RfRfD1OZx94njeYmgtq/Ynr1x4RHaCpRlSr1ZdpDaatI 9kvSOILPANgcqj60tbfV4pDSFJCB7wNw+2RZoQvF0TyxuGt9Qdbjc4IBHQB0evuCqSDN jOnOPQAH4cJ/xBdaI4SoZtZSZoxLR9f6+3O/bDlGUhMDTzni93+SWTBg56T6d2Ljdbqy 3mIMyN5iJjq8OjmYFPpMh3SSG7ERXIVc0LZR5Xv8vsragWl0fFRUtfrLMEHlSimHN/yV vHMQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=RgO6GjCwfYvVYjBU4LlLzSqEmojc1b0IeppzCvIVG8E=; b=CgnBhZMd/EMrYM8L6p8AM16s+4ov1GVSxjKoSteyaVfP8GLc4o27XqAK51EOBhofuM eX52F0jhFIbK4/LvoymbWp3620AAmjDa2GCx5EeJkOXsal1PR0m+NNR5d/n+uXKOP15r mQhf77+ZloIp7NQhqcU8d4G0udFoVdlyjGPhkkPNEt6fpI4T7Na54rBrhCLfJr+HBLP1 NnhvZurnl2xjfMs9X2CDqTQSP9xTa4JlAxMgINmhJN2ySk2CVS5/70IFFQ9Z06yGRrpM LUgAD6BKXcpJIBxpXyh0AEXZfhrDnE23Abr0ByytH+HF4oVdsT4yyvYCHm8nBbk5BIGb Oqig==
X-Gm-Message-State: AN3rC/4qqD8+KZgiEEHaAStAX4PrJwDQO8G8dgYbXDxZruh1D4IWbYNk p2RUz25PuEkrsG7HXLhSjZsypxvLyQ==
X-Received: by 10.202.81.196 with SMTP id f187mr3063031oib.126.1493326574307; Thu, 27 Apr 2017 13:56:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.231.132 with HTTP; Thu, 27 Apr 2017 13:55:53 -0700 (PDT)
In-Reply-To: <CAJn5=KcxP8R7wBWuUohAnhHP9tKqsV+QfQHVAsOVXcpu10tdoQ@mail.gmail.com>
References: <BF1BE6D99B52F84AB9B48B7CF6F17DA3DD5F8E@SJCEML701-CHM.china.huawei.com> <CAA=duU3vKSmH=+nfECeczpUp3+UXSe=F4OHSP4uPg+j7ZQzdTg@mail.gmail.com> <CAJn5=KcxP8R7wBWuUohAnhHP9tKqsV+QfQHVAsOVXcpu10tdoQ@mail.gmail.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Thu, 27 Apr 2017 16:55:53 -0400
Message-ID: <CAA=duU2a4X_-uhShJvqpqhs-EkQrPCy7NUo7CiziA=DpwKrgLQ@mail.gmail.com>
To: Jim Guichard <jguichard1966@gmail.com>
Cc: James N Guichard <james.n.guichard@huawei.com>, "sfc@ietf.org" <sfc@ietf.org>
Content-Type: multipart/alternative; boundary="001a113b013efed0fe054e2c2f22"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/5bfSzvFdit1MAHF-ExQ1leoDd74>
Subject: Re: [sfc] TTL field within the NSH base header
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Network Service Chaining <sfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sfc>, <mailto:sfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sfc/>
List-Post: <mailto:sfc@ietf.org>
List-Help: <mailto:sfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sfc>, <mailto:sfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 21:00:26 -0000
Jim, In that case, you need to remove the word “reserved” from the replacement text. Cheers, Andy On Thu, Apr 27, 2017 at 4:37 PM, Jim Guichard <jguichard1966@gmail.com> wrote: > Yes but I also counted the other 3 bits that were reserved and are now > allocated.. > > On Thu, Apr 27, 2017 at 4:25 PM Andrew G. Malis <agmalis@gmail.com> wrote: > >> Jim, >> >> The replacement text says: >> >> There are eight reserved bits in the NSH Base Header. New bits >> >> are assigned via Standards Action [RFC5226]. >> >> There are now actually five reserved bits. >> >> Cheers, >> Andy >> >> >> On Thu, Apr 27, 2017 at 2:54 PM, James N Guichard < >> james.n.guichard@huawei.com> wrote: >> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> Dear WG: >>> >>> >>> >>> >>> >>> Having reviewed all of the email discussion on the mailing list it >>> appears to the chairs that we have consensus to add a TTL field to the NSH >>> base header. We would like to propose the following changes: >>> >>> >>> >>> >>> >>> Section 3.2: >>> >>> >>> Update figure 2 as follows: >>> >>> >>> >>> >>> >>> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 >>> >>> >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> >>> >>> |Ver|O|R| TTL | Length |R|R|R|R|MD Type| Next Protocol | >>> >>> >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> >>> >>> >>> >>> >>> Add the following text after figure 2: >>> >>> >>> >>> >>> >>> TTL: Service plane time-to-live. An SFF MUST decrement the TTL by a >>> value of 1 for all NSH packets it receives. Decrementing by a value of 1 >>> from 0 shall result in a TTL value of 63. The default for originating an >>> NSH packet is a TTL value >>> >>> of 63. The decrement SHALL occur before testing for 0. After decrement, >>> if the TTL is 0, the NSH packet MUST NOT be forwarded. >>> >>> >>> >>> >>> >>> Section 3.4: >>> >>> >>> Update figure 4 to reflect the new base header format as per section 3.2 >>> base header. >>> >>> >>> >>> >>> >>> Section 3.5: >>> >>> >>> Update figure 5 to reflect the new base header format as per section 3.2 >>> base header. >>> >>> >>> >>> >>> >>> Section 12.2.1: >>> >>> >>> Current text is as follows: >>> >>> >>> >>> >>> >>> There are ten bits at the beginning of the NSH Base Header. New bits >>> >>> >>> are assigned via Standards Action [RFC5226]. >>> >>> >>> >>> >>> >>> Bits 0-1 - Version >>> >>> >>> Bit 2 - OAM (O bit) >>> >>> >>> Bit 3 - Critical TLV (C bit) >>> >>> >>> Bits 4-9 - Reserved >>> >>> >>> >>> >>> >>> Replace entire text as follows: >>> >>> >>> >>> >>> >>> There are eight reserved bits in the NSH Base Header. New bits >>> >>> >>> are assigned via Standards Action [RFC5226]. >>> >>> >>> >>> >>> >>> Bits 0-1 - Version >>> >>> >>> Bit 2 - OAM (O bit) >>> >>> >>> Bit 3 - Reserved >>> >>> >>> Bits 16-19 - Reserved >>> >>> >>> >>> >>> >>> Section 12.2.3: >>> >>> >>> Current text has the MD-type as 8-bit values. >>> >>> >>> >>> >>> >>> Update text for this section and table 1 to reflect 4-bit values *not* >>> 8-bit values. >>> >>> >>> >>> >>> >>> *Please review carefully and indicate support for these changes (or any >>> changes to the suggested text).* >>> >>> >>> >>> >>> >>> Thanks, >>> >>> >>> >>> >>> >>> Jim & Joel >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> >>> >>> sfc mailing list >>> >>> >>> sfc@ietf.org >>> >>> >>> https://www.ietf.org/mailman/listinfo/sfc >>> >>> >>> >>> >> >> >> _______________________________________________ >> >> sfc mailing list >> >> sfc@ietf.org >> >> https://www.ietf.org/mailman/listinfo/sfc >> >>
- Re: [sfc] TTL field within the NSH base header Ron Parker
- Re: [sfc] TTL field within the NSH base header Dave Dolson
- [sfc] TTL field within the NSH base header James N Guichard
- Re: [sfc] TTL field within the NSH base header James N Guichard
- Re: [sfc] TTL field within the NSH base header James N Guichard
- Re: [sfc] TTL field within the NSH base header Andrew G. Malis
- Re: [sfc] TTL field within the NSH base header Ron Parker
- Re: [sfc] TTL field within the NSH base header Joel M. Halpern
- Re: [sfc] TTL field within the NSH base header Jim Guichard
- Re: [sfc] TTL field within the NSH base header Andrew G. Malis
- Re: [sfc] TTL field within the NSH base header Ron Parker
- Re: [sfc] TTL field within the NSH base header Dave Dolson
- Re: [sfc] TTL field within the NSH base header Joe Clarke
- Re: [sfc] TTL field within the NSH base header Ron Parker
- Re: [sfc] TTL field within the NSH base header mohamed.boucadair
- Re: [sfc] TTL field within the NSH base header Dave Dolson
- Re: [sfc] TTL field within the NSH base header jmh.direct
- Re: [sfc] TTL field within the NSH base header Dave Dolson
- Re: [sfc] TTL field within the NSH base header Joel M. Halpern
- Re: [sfc] TTL field within the NSH base header Joel M. Halpern
- Re: [sfc] TTL field within the NSH base header mohamed.boucadair
- Re: [sfc] TTL field within the NSH base header mohamed.boucadair
- Re: [sfc] TTL field within the NSH base header Dave Dolson
- Re: [sfc] TTL field within the NSH base header Dave Dolson
- Re: [sfc] TTL field within the NSH base header Dave Dolson
- Re: [sfc] TTL field within the NSH base header mohamed.boucadair
- Re: [sfc] TTL field within the NSH base header Andrew G. Malis
- Re: [sfc] TTL field within the NSH base header James N Guichard
- Re: [sfc] TTL field within the NSH base header Ron Parker
- Re: [sfc] TTL field within the NSH base header Kyle Larose
- Re: [sfc] TTL field within the NSH base header James N Guichard
- Re: [sfc] TTL field within the NSH base header Ron Parker
- Re: [sfc] TTL field within the NSH base header Joel M. Halpern
- Re: [sfc] TTL field within the NSH base header Dave Dolson
- Re: [sfc] TTL field within the NSH base header Ron Parker
- Re: [sfc] TTL field within the NSH base header Dave Dolson
- Re: [sfc] TTL field within the NSH base header Ron Parker
- Re: [sfc] TTL field within the NSH base header Dave Dolson
- Re: [sfc] TTL field within the NSH base header Ron Parker
- Re: [sfc] TTL field within the NSH base header Joel M. Halpern
- Re: [sfc] TTL field within the NSH base header Greg Mirsky
- Re: [sfc] TTL field within the NSH base header James N Guichard
- Re: [sfc] TTL field within the NSH base header Ron Parker
- Re: [sfc] TTL field within the NSH base header Ron Parker
- Re: [sfc] TTL field within the NSH base header Eric C Rosen
- Re: [sfc] TTL field within the NSH base header Joel Halpern Direct
- Re: [sfc] TTL field within the NSH base header James N Guichard
- Re: [sfc] TTL field within the NSH base header Joe Clarke
- Re: [sfc] TTL field within the NSH base header mohamed.boucadair
- Re: [sfc] TTL field within the NSH base header Greg Mirsky
- Re: [sfc] TTL field within the NSH base header mohamed.boucadair
- Re: [sfc] TTL field within the NSH base header mohamed.boucadair
- Re: [sfc] TTL field within the NSH base header mohamed.boucadair
- Re: [sfc] TTL field within the NSH base header mohamed.boucadair
- Re: [sfc] TTL field within the NSH base header Dave Dolson
- Re: [sfc] TTL field within the NSH base header mohamed.boucadair
- Re: [sfc] TTL field within the NSH base header Dave Dolson
- Re: [sfc] TTL field within the NSH base header mohamed.boucadair
- Re: [sfc] TTL field within the NSH base header James N Guichard
- Re: [sfc] TTL field within the NSH base header Dave Dolson
- Re: [sfc] TTL field within the NSH base header Ron Parker
- Re: [sfc] TTL field within the NSH base header mohamed.boucadair
- Re: [sfc] TTL field within the NSH base header Joel M. Halpern
- Re: [sfc] TTL field within the NSH base header Joel M. Halpern
- Re: [sfc] TTL field within the NSH base header Dave Dolson
- Re: [sfc] TTL field within the NSH base header Dave Dolson
- Re: [sfc] TTL field within the NSH base header Greg Mirsky
- Re: [sfc] TTL field within the NSH base header James N Guichard
- Re: [sfc] TTL field within the NSH base header mohamed.boucadair