Re: [mpls] New Version Notification for draft-xu-sfc-using-mpls-spring-04.txt

Thomas Narten <narten@us.ibm.com> Fri, 30 October 2015 20:33 UTC

Return-Path: <narten@us.ibm.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D636E1A9100 for <mpls@ietfa.amsl.com>; Fri, 30 Oct 2015 13:33:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.911
X-Spam-Level:
X-Spam-Status: No, score=-6.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=unavailable
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 dxTdEJL3Y283 for <mpls@ietfa.amsl.com>; Fri, 30 Oct 2015 13:33:12 -0700 (PDT)
Received: from e33.co.us.ibm.com (e33.co.us.ibm.com [32.97.110.151]) (using TLSv1 with cipher CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2EA181A90F9 for <mpls@ietf.org>; Fri, 30 Oct 2015 13:33:12 -0700 (PDT)
Received: from localhost by e33.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <mpls@ietf.org> from <narten@us.ibm.com>; Fri, 30 Oct 2015 14:33:11 -0600
Received: from d03dlp03.boulder.ibm.com (9.17.202.179) by e33.co.us.ibm.com (192.168.1.133) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Fri, 30 Oct 2015 14:33:10 -0600
X-IBM-Helo: d03dlp03.boulder.ibm.com
X-IBM-MailFrom: narten@us.ibm.com
X-IBM-RcptTo: mpls@ietf.org;sfc@ietf.org
Received: from b03cxnp07029.gho.boulder.ibm.com (b03cxnp07029.gho.boulder.ibm.com [9.17.130.16]) by d03dlp03.boulder.ibm.com (Postfix) with ESMTP id C292C19D8042; Fri, 30 Oct 2015 14:21:18 -0600 (MDT)
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by b03cxnp07029.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id t9UKX9nA11665848; Fri, 30 Oct 2015 13:33:09 -0700
Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id t9UKX9Jc025176; Fri, 30 Oct 2015 14:33:09 -0600
Received: from cichlid.raleigh.ibm.com ([9.80.96.118]) by d03av04.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id t9UKX7nb025081 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 30 Oct 2015 14:33:09 -0600
Received: from cichlid.raleigh.ibm.com.us.ibm.com (localhost.localdomain [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id t9UKX6h8015866; Fri, 30 Oct 2015 16:33:07 -0400
Date: Fri, 30 Oct 2015 16:33:06 -0400
Message-ID: <m3vb9oumf1.wl-narten@us.ibm.com>
From: Thomas Narten <narten@us.ibm.com>
To: Xuxiaohu <xuxiaohu@huawei.com>
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0CB3E2EE@NKGEML512-MBS.china.huawei.com>
References: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0CB3DFAF@NKGEML512-MBS.china.huawei.com> <m3a8r3dkvk.wl-narten@us.ibm.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0CB3E2EE@NKGEML512-MBS.china.huawei.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (Gojō) APEL/10.8 EasyPG/1.0.0 Emacs/23.1 (x86_64-redhat-linux-gnu) MULE/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
X-TM-AS-MML: disable
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 15103020-0009-0000-0000-00000F5D4DA4
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/-amZ6-2-rZh7GVNUBaFCGOl36Ac>
Cc: "'mpls@ietf.org'" <mpls@ietf.org>, "mpls-chairs@tools.ietf.org" <mpls-chairs@tools.ietf.org>, "'sfc@ietf.org'" <sfc@ietf.org>, "sfc-chairs@tools.ietf.org" <sfc-chairs@tools.ietf.org>
Subject: Re: [mpls] New Version Notification for draft-xu-sfc-using-mpls-spring-04.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Oct 2015 20:33:14 -0000

> According to the following statement quoted from the current SFC charter:
> 
> "... The WG will examine existing identifier schemes,
>   if there is a need for such identifiers in the context of the Generic SFC
>   encapsulation, before defining any new identifier scheme.
> ..."
> 
> It seems that this MPLS-SPRING-based SFC encapsulation scheme should be
> relevant to the SFC WG. At least, it could be investigated as a light-weight
> SFC encapsulation approach (from the aspect of reducing and even avoiding any
> impact on the data plane).

The charter also says:

   3. Generic SFC Encapsulation: This document will describe a single 
      service-level data plane encapsulation format that:

I want to emphasize the term "a single ... encapsulation format" It
has been my understanding that the intention of this WG from the
beginning was to produce one encapsulation, not multiple ones.

I think it has been clear for some time already that the WG has
selected the NSH document as its desired approach.

Are you suggesting that the WG take on this document as an additional
encapsulation for SFC? I do not think that is consistent with the
intent of the charter. Also, my read of the overall list discussion
with respect to this document is that the WG has not shown a strong
interest in this document nor indicated a compelling need for it.

If the WG disagrees with this assessment, I expect folk would speak
up.

Thomas