Re: [sfc] TTL field within the NSH base header

James N Guichard <james.n.guichard@huawei.com> Thu, 27 April 2017 21:02 UTC

Return-Path: <james.n.guichard@huawei.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 EA8E7129BAC for <sfc@ietfa.amsl.com>; Thu, 27 Apr 2017 14:02:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, 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 pUcVkVJ8ca_0 for <sfc@ietfa.amsl.com>; Thu, 27 Apr 2017 14:02:33 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 15DAD129B1A for <sfc@ietf.org>; Thu, 27 Apr 2017 13:58:31 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml703-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DFQ11184; Thu, 27 Apr 2017 20:58:30 +0000 (GMT)
Received: from SJCEML703-CHM.china.huawei.com (10.208.112.39) by lhreml703-cah.china.huawei.com (10.201.108.44) with Microsoft SMTP Server (TLS) id 14.3.301.0; Thu, 27 Apr 2017 21:58:29 +0100
Received: from SJCEML701-CHM.china.huawei.com ([169.254.3.8]) by SJCEML703-CHM.china.huawei.com ([169.254.5.195]) with mapi id 14.03.0235.001; Thu, 27 Apr 2017 13:58:23 -0700
From: James N Guichard <james.n.guichard@huawei.com>
To: "Andrew G. Malis" <agmalis@gmail.com>, Jim Guichard <jguichard1966@gmail.com>
CC: "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: [sfc] TTL field within the NSH base header
Thread-Index: AdK/h0bahW5bvXGwSoCeYu3QIaIxxgARxo4AAACXi4AAAKVngAAOmEvQ
Date: Thu, 27 Apr 2017 20:58:22 +0000
Message-ID: <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>
In-Reply-To: <CAA=duU2a4X_-uhShJvqpqhs-EkQrPCy7NUo7CiziA=DpwKrgLQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.149.48]
Content-Type: multipart/alternative; boundary="_000_BF1BE6D99B52F84AB9B48B7CF6F17DA3DD610ASJCEML701CHMchina_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020205.59025B76.0169, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.3.8, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 2dd44c1b41feabef88ba909b94eff50f
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/hGuGEQbioeC9vPtg3-7J0ckKkp0>
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:02:35 -0000

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<mailto: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<mailto: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<mailto: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<mailto:sfc@ietf.org>


https://www.ietf.org/mailman/listinfo/sfc





_______________________________________________

sfc mailing list

sfc@ietf.org<mailto:sfc@ietf.org>

https://www.ietf.org/mailman/listinfo/sfc