Re: [sfc] TTL field within the NSH base header
"Andrew G. Malis" <agmalis@gmail.com> Fri, 28 April 2017 14:16 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 4BAD8129B3F for <sfc@ietfa.amsl.com>; Fri, 28 Apr 2017 07:16:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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] 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 GuQ8qfG-1Sut for <sfc@ietfa.amsl.com>; Fri, 28 Apr 2017 07:15:59 -0700 (PDT)
Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::236]) (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 2D8EC129B01 for <sfc@ietf.org>; Fri, 28 Apr 2017 07:13:11 -0700 (PDT)
Received: by mail-it0-x236.google.com with SMTP id x188so38780661itb.0 for <sfc@ietf.org>; Fri, 28 Apr 2017 07:13:11 -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=IPDOu+Lhifk8wjUi8vzIFLcg55XC3hx9u/nWSWPXSWs=; b=IpHNCkWyuYKLNHJL8nK4yjAE6d392kOS12G5wi6CSFChfV2/iiMY2ozVZN8ndn/bpW AJyK6OdHJByHRpfAIcNRYo4gSwKDGqwDw5r8T+nNiLcm+OIVCvYisOEGkEq8z/2dEBz5 DRj4KwRpo01HiFnYUpNNDuQsTYp8/tISrpSTvHeps4Io0jhXW4T9TsC1vr0xPWmOUwQ7 1ZgvSqO1uRDBBttOa+v1wlfGuTARPz3hVqwVdc573Y+3O0fqcNneiMybimYlmJrr0pMU S2SWQPDLgjEwNZtPSDn7P1wZPOhYELMm3EirxTqRF7+q09jOuyYASgzQG6zbnujO3E8t 1SxQ==
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=IPDOu+Lhifk8wjUi8vzIFLcg55XC3hx9u/nWSWPXSWs=; b=FzWoouqE1mRAjhuwYw7ul39itzyTWNzf48UT0Gkga/mBCXMH6txskvHdAKoP+mTCUp PIss9+QpMVupmd2Xc77Qba7kVnRAKO4hrJM5YtYHzlK4aTtAY1X8V0lCHCasFdyLoIGv k88ZNsIW/KIHVWXdG8MNZ8AiPuCusNxsZG1taoXrRv5O6PQlh9hRBEXp0o447VDWBgzq 3WrxrtsNWJdBDzBUPJCeoI+JXMtg6sW450PR6nhpI/hK0vlqLUQLOKms7EPsfgIGmyng OtUPMbg3VjT5VnSLL9b8GInK36dCZl+/M79Q0xUQHNBwl7xaN4sJ0FiJBCg3v41+0+KA YDmQ==
X-Gm-Message-State: AN3rC/4xKFGYGTo/5fuVnRilBiyneIlYggXoXNldlbbJyef6XEcJcJcq 1KwLZjcW9kt8HKMdsPQB6AwHhF0Y6w==
X-Received: by 10.202.81.199 with SMTP id f190mr4534256oib.22.1493388789788; Fri, 28 Apr 2017 07:13:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.231.132 with HTTP; Fri, 28 Apr 2017 07:12:49 -0700 (PDT)
In-Reply-To: <BF1BE6D99B52F84AB9B48B7CF6F17DA3DD610A@SJCEML701-CHM.china.huawei.com>
References: <BF1BE6D99B52F84AB9B48B7CF6F17DA3DD5F8E@SJCEML701-CHM.china.huawei.com> <CAA=duU3vKSmH=+nfECeczpUp3+UXSe=F4OHSP4uPg+j7ZQzdTg@mail.gmail.com> <CAJn5=KcxP8R7wBWuUohAnhHP9tKqsV+QfQHVAsOVXcpu10tdoQ@mail.gmail.com> <CAA=duU2a4X_-uhShJvqpqhs-EkQrPCy7NUo7CiziA=DpwKrgLQ@mail.gmail.com> <BF1BE6D99B52F84AB9B48B7CF6F17DA3DD610A@SJCEML701-CHM.china.huawei.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Fri, 28 Apr 2017 10:12:49 -0400
Message-ID: <CAA=duU1L5MSc8n=4hTD_RtMNQhh6OMk339iaR6c73_dN-DZ9dg@mail.gmail.com>
To: James N Guichard <james.n.guichard@huawei.com>
Cc: Jim Guichard <jguichard1966@gmail.com>, "sfc@ietf.org" <sfc@ietf.org>
Content-Type: multipart/alternative; boundary="001a113d798a53b324054e3aac4b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/FDowaJNFaZVY-XVKtwmJdWnV77g>
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: Fri, 28 Apr 2017 14:16:02 -0000
Jim, This looks good to me. Thanks, Andy On Thu, Apr 27, 2017 at 4:58 PM, James N Guichard < james.n.guichard@huawei.com> wrote: > Sorry from 8 to 5 .. geez > > > > *From:* Andrew G. Malis [mailto:agmalis@gmail.com] > *Sent:* Thursday, April 27, 2017 4:56 PM > *To:* Jim Guichard <jguichard1966@gmail.com> > *Cc:* James N Guichard <james.n.guichard@huawei.com>; sfc@ietf.org > *Subject:* Re: [sfc] TTL field within the NSH base header > > > > 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