Re: [mpls] [sfc] I-D Action: draft-ietf-sfc-nsh-01.txt

Xuxiaohu <> Fri, 24 July 2015 07:24 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 5F4281B2FAC; Fri, 24 Jul 2015 00:24:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.761
X-Spam-Status: No, score=-1.761 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Fh-wXU9ASL8a; Fri, 24 Jul 2015 00:24:45 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2D13C1B2FAA; Fri, 24 Jul 2015 00:24:45 -0700 (PDT)
Received: from (EHLO ([]) by (MOS 4.3.7-GA FastPath queued) with ESMTP id BZC59397; Fri, 24 Jul 2015 07:24:43 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id; Fri, 24 Jul 2015 08:24:09 +0100
Received: from ([]) by ([]) with mapi id 14.03.0158.001; Fri, 24 Jul 2015 15:24:05 +0800
From: Xuxiaohu <>
To: "" <>
Thread-Topic: [sfc] I-D Action: draft-ietf-sfc-nsh-01.txt
Thread-Index: AQHQxXi9Tgyhos48PEq9TRyTCNQEgp3qNSbA
Date: Fri, 24 Jul 2015 07:24:04 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Cc: "" <>
Subject: Re: [mpls] [sfc] I-D Action: draft-ietf-sfc-nsh-01.txt
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-Protocol Label Switching WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 24 Jul 2015 07:24:47 -0000

Hi co-authors,

I wonder whether the NSH encapsulation would strictly follow the transport-independance principle as defined in the SFC architecture draft. If so, it's possible that the NSH would be transported over MPLS networks someday. As such, it's better to consider the first nibble issue associated with the current MPLS architecture from the beginning. I have not seen any text in this regard in this new version.

Best regards,

发件人: sfc [] 代表 []
发送时间: 2015年7月24日 2:51
主题: [sfc] I-D Action: draft-ietf-sfc-nsh-01.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Service Function Chaining Working Group of the IETF.

        Title           : Network Service Header
        Authors         : Paul Quinn
                          Uri Elzur
        Filename        : draft-ietf-sfc-nsh-01.txt
        Pages           : 43
        Date            : 2015-07-23

   This draft describes a Network Service Header (NSH) inserted onto
   encapsulated 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 as per SFC
   Architecture [SFC-arch]

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 submission
until the htmlized version and diff are available at

Internet-Drafts are also available by anonymous FTP at:

sfc mailing list