Subject: Re: [sfc] draft-quinn-sfc-nsh: O bit

From: "Paul Quinn (paulq)" <[email-masked]>
Date: Mon, 2 Mar 2015 15:56:22 +0000

On Feb 25, 2015, at 10:53 AM, [email-masked]<mailto:[email-masked]> wrote:

Hi Paul,

The current text states:

“
   O bit: Indicates that this packet is an operations and management
   (OAM) packet.  SFF and SFs nodes MUST examine the payload and take
   appropriate action (e.g. return status information).

   OAM message specifics and handling details are outside the scope of
   this document.
“

Is there any particular reason why this is declared out of scope?

The specific of an OAM protocol aren’t being specified in NSH, rather, there are SFC OAM drafts that will define the protocols (similar, I believe to what MPLS did and NVO3 is doing).  NSH simply defines that when O-bit=1, that OAM handling must occur, as per the text below.

If the current scope is to be maintained, then you can remove this sentence as it is useless since appropriate actions are not defined in the document.

“SFF and SFs nodes MUST examine the payload and take
   appropriate action (e.g. return status information).”

Thank you.

Cheers,
Med