Opened 5 years ago

#23 new defect

'C' flag

Reported by: mohamed.boucadair@… Owned by: draft-ietf-sfc-nsh@…
Priority: major Milestone:
Component: nsh Version:
Severity: Active WG Document Keywords:



Unless I'm mistaken, I didn't see any follow-up for this issue.


De : Dave Dolson ddolson@…
Envoyé : mardi 6 septembre 2016 20:25
À : BOUCADAIR Mohamed IMT/OLN; Paul Quinn (paulq); sfc@…
Objet : RE: [sfc] Fwd: I-D Action: draft-ietf-sfc-nsh-06.txt

Do the authors have a response to this question?
I'm also wondering about whether the 'C' flag might be for the
administrator vs. IANA.

From: sfc sfc-bounces@… On Behalf Of
Sent: Thursday, August 25, 2016 11:40 AM
To: Paul Quinn (paulq); sfc@…
Subject: Re: [sfc] Fwd: I-D Action: draft-ietf-sfc-nsh-06.txt

Hi Paul,

I have a comment about this text:

Type: the Type field is split into two ranges - 0 to 127 for non-
critical options and 128-255 for critical options. While the value
allocation is the responsibility of the MD Class owner, critical
options MUST NOT be allocated from the 0 to 127 range and non-
critical options MUST NOT be allocated from the 128-255 range.

  • Do you have an example of metadata that is critical for all chains, all


  • Wouldn't be more appropriate to have one single registry for "type" with

C-bit be a configurable parameter to be set by the administrator of the
SFC-enabled domain?

Thank you.


De : sfc sfc-bounces@… De la part de Paul Quinn (paulq)
Envoyé : mardi 23 août 2016 16:02
À : sfc@…
Objet : [sfc] Fwd: I-D Action: draft-ietf-sfc-nsh-06.txt

Dear WG,

This version includes much of the feedback/review/comments from this


Begin forwarded message:

From: internet-drafts@…
Subject: [sfc] I-D Action: draft-ietf-sfc-nsh-06.txt
Date: August 23, 2016 at 9:54:21 AM EDT
To: <i-d-announce@…>
Cc: sfc@…

A New Internet-Draft is available from the on-line Internet-Drafts


This draft is a work item of the Service Function Chaining of the


Title : Network Service Header
Authors : Paul Quinn

Uri Elzur

Filename : draft-ietf-sfc-nsh-06.txt
Pages : 37
Date : 2016-08-23


This document describes a Network Service Header (NSH) inserted onto
packets or frames to realize service function paths. NSH also
provides a mechanism for metadata exchange along the instantiated
service path. NSH is the SFC encapsulation required to support the
Service Function Chaining (SFC) Architecture (defined in RFC7665).

The IETF datatracker status page for this draft is:

There's also a htmlized version available at:

A diff from the previous version is available at:

Please note that it may take a couple of minutes from the time of


until the htmlized version and diff are available at

Internet-Drafts are also available by anonymous FTP at:

Change History (0)

Note: See TracTickets for help on using tickets.