
From nobody Sun Mar  1 17:24:24 2015
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFB1F1A1BDC for <sfc@ietfa.amsl.com>; Sun,  1 Mar 2015 17:24:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 Sw9TMzq0U_SZ for <sfc@ietfa.amsl.com>; Sun,  1 Mar 2015 17:24:18 -0800 (PST)
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 61DD41A1F02 for <sfc@ietf.org>; Sun,  1 Mar 2015 17:24:17 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml404-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BPT42288; Mon, 02 Mar 2015 01:24:15 +0000 (GMT)
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 2 Mar 2015 01:24:14 +0000
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.115]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.03.0158.001; Mon, 2 Mar 2015 09:24:10 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: "Zarny, Myo" <Myo.Zarny@gs.com>, "'Jim Guichard (jguichar)'" <jguichar@cisco.com>, "'sfc@ietf.org'" <sfc@ietf.org>
Thread-Topic: WG call for adoption of draft-quinn-sfc-nsh
Thread-Index: AQHQUcJRZDObBxbiIUWmIP9lX1xWp50F0KkggABL97CAAk1VoA==
Date: Mon, 2 Mar 2015 01:24:10 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0830EE0A@NKGEML512-MBS.china.huawei.com>
References: <D1147FF5.844D%jguichar@cisco.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0830EBDD@NKGEML512-MBS.china.huawei.com> <A3233753A4B65F43BCA1B64DA99A9C23071C76FD42@GSCMAMP19EX.firmwide.corp.gs.com>
In-Reply-To: <A3233753A4B65F43BCA1B64DA99A9C23071C76FD42@GSCMAMP19EX.firmwide.corp.gs.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.99.55]
Content-Type: multipart/alternative; boundary="_000_1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0830EE0ANKGEML512MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/sWQcmtHzNGX0rKugIX9oW1DreVc>
Subject: Re: [sfc] WG call for adoption of draft-quinn-sfc-nsh
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 02 Mar 2015 01:24:22 -0000

--_000_1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0830EE0ANKGEML512MBSchi_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Myo,

Thanks for your response. It's great that the NSH is allowed to contain onl=
y the metadata by ignoring the service path header (e.g., set the SPID to z=
ero). That's what I had expected. Thanks again for your explanation.

Best regards,
Xiaohu

From: Zarny, Myo [mailto:Myo.Zarny@gs.com]
Sent: Saturday, February 28, 2015 10:42 PM
To: Xuxiaohu; 'Jim Guichard (jguichar)'; 'sfc@ietf.org'
Subject: RE: WG call for adoption of draft-quinn-sfc-nsh

Hi Xiaohu,

Currently, the draft certainly supports two of your three scenarios: (1) SF=
C path only and (3) SFC path info and metadata.

As for the scenario of carrying just the metadata, can you clarify your ask=
? I take that you're not mandating that the base header not contain a servi=
ce path header; but rather that the NSH be used to carry just the metadata =
only, correct? If it's the latter, the NSH does support your scenario. Yes,=
 the Service Path Header is a required component of the header. But you can=
 choose an implementation method to ignore the SP header values (SPID and S=
PI). (Implementation methods could range from zeroing the fields out to ins=
tructing NSH-aware devices to ignore them; etc.) If that meets your expecta=
tions, then, the header supports all three scenarios.

Now, to be precise and for full disclosure, all three scenarios are support=
ed through MD-Type 2, which the draft currently recommends as a "SHOULD" im=
plementation [Section 3.2].

Myo

From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of Xuxiaohu
Sent: 28 February 2015 4:52 AM
To: Jim Guichard (jguichar); sfc@ietf.org<mailto:sfc@ietf.org>
Subject: Re: [sfc] WG call for adoption of draft-quinn-sfc-nsh

Support.

By the way, I hope the NSH could be capable of: 1) containing the service c=
hain/path info only; 2) containing the metadata only ;3) containing both se=
rvice chain/path info and the metadata. Otherwise, we may need to design a =
separate header for containing the metadata in the case where the service c=
hain/path info has been embodied by other means than the NSH itself. In thi=
s way, it's aligned with the following statement in the SFC architecture dr=
aft:

"4.3.1<https://tools.ietf.org/html/draft-ietf-sfc-architecture-04#section-4=
.3.1>.  Transport Derived SFF


   Service function forwarding, as described above, directly depends
   upon the use of the service path information contained in the SFC
   encapsulation.  However, existing implementations may not be able to
   act on the SFC encapsulation.  These platforms may opt to use
   existing transport information if it can be arranged to provide
   explicit service path information.

   This results in the same architectural behavior and meaning for
   service function forwarding and service function paths.  It is the
   responsibility of the control components to ensure that the transport
   path executed in such a case is fully aligned with the path
   identified by the information in the service chaining encapsulation.

"

Xiaohu

From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of Jim Guichard (jguichar=
)
Sent: Thursday, February 26, 2015 8:47 PM
To: sfc@ietf.org<mailto:sfc@ietf.org>
Subject: [sfc] WG call for adoption of draft-quinn-sfc-nsh

Greetings WG:

The document draft-quinn-sfc-nsh-07 (https://datatracker.ietf.org/doc/draft=
-quinn-sfc-nsh/) has recently been reissued. The authors of draft-zhang-sfc=
-sch-03 (http://datatracker.ietf.org/doc/draft-zhang-sfc-sch/) have joined =
the NSH document so that the WG can focus on a single encapsulation documen=
t going forward. This new version of NSH includes an open items section bas=
ed on discussion between co-authors and members of the list. The WG will wo=
rk through this list (and any other issues that need to be added) over the =
next weeks. We appreciate and recognize the hard work of both the NSH and S=
CH authors in pushing the SFC encapsulation work forward.

With that said, the chairs are calling for WG adoption of draft-quinn-sfc-n=
sh-07 as a WG document. The call for adoption will run for 2 weeks ending 3=
/12/2015.

Please note that this is a call for adoption, and not a last call for conte=
nt of the document. Adopting a WG document simply means that the WG will fo=
cus its efforts on that particular draft going forward, and use that docume=
nt for resolving open issues and documenting the WG's decisions.

Please indicate whether you support adoption for not, and if not why. Issue=
s you have with the current document itself can also be raised, but they sh=
ould be raised in the context of what should be changed in the document goi=
ng forward, rather than a pre-condition for adoption.

Finally, now is also a good time to poll for knowledge of any IPR that appl=
ies to this draft, in line with the IPR disclosure obligations for WG parti=
cipants (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are l=
isted as a document author please respond to this email (to the chairs) whe=
ther or not you are aware of any relevant IPR.

Jim & Thomas

--_000_1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0830EE0ANKGEML512MBSchi_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Cambria;
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
h4
	{mso-style-priority:9;
	mso-style-link:"\6807\9898 4 Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	font-weight:normal;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML \9884\8BBE\683C\5F0F Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"\6279\6CE8\6846\6587\672C Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.4Char
	{mso-style-name:"\6807\9898 4 Char";
	mso-style-priority:9;
	mso-style-link:"\6807\9898 4";
	font-family:"Courier New";
	font-weight:bold;}
span.HTMLChar
	{mso-style-name:"HTML \9884\8BBE\683C\5F0F Char";
	mso-style-priority:99;
	mso-style-link:"HTML \9884\8BBE\683C\5F0F";
	font-family:SimSun;}
span.Char
	{mso-style-name:"\6279\6CE8\6846\6587\672C Char";
	mso-style-priority:99;
	mso-style-link:\6279\6CE8\6846\6587\672C;
	font-family:SimSun;}
p.Heading4, li.Heading4, div.Heading4
	{mso-style-name:"Heading 4";
	mso-style-link:"Heading 4 Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.Heading4Char
	{mso-style-name:"Heading 4 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 4";
	font-family:"Cambria","serif";
	color:#4F81BD;
	font-weight:bold;
	font-style:italic;}
p.HTMLPreformatted, li.HTMLPreformatted, div.HTMLPreformatted
	{mso-style-name:"HTML Preformatted";
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.EmailStyle26
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
p.BalloonText, li.BalloonText, div.BalloonText
	{mso-style-name:"Balloon Text";
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle29
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle30
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"ZH-CN" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi Myo,<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks for=
 your response. It&#8217;s great that the NSH is allowed to contain only th=
e metadata by ignoring the service path header (e.g., set the SPID
 to zero). That&#8217;s what I had expected. Thanks again for your explanat=
ion.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Best regar=
ds,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Xiaohu<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> Zarny, Myo [mailto:Myo.Zarny@gs.com]
<br>
<b>Sent:</b> Saturday, February 28, 2015 10:42 PM<br>
<b>To:</b> Xuxiaohu; 'Jim Guichard (jguichar)'; 'sfc@ietf.org'<br>
<b>Subject:</b> RE: WG call for adoption of draft-quinn-sfc-nsh<o:p></o:p><=
/span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi Xiaohu,=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Currently,=
 the draft certainly supports two of your three scenarios: (1) SFC path onl=
y and (3) SFC path info and metadata.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">As for the=
 scenario of carrying just the metadata, can you clarify your ask? I take t=
hat you&#8217;re not mandating that the base header not contain
 a service path header; but rather that the NSH be used to carry just the m=
etadata only, correct? If it&#8217;s the latter, the NSH does support your =
scenario. Yes, the Service Path Header is a required component of the heade=
r. But you can choose an implementation
 method to ignore the SP header values (SPID and SPI). (Implementation meth=
ods could range from zeroing the fields out to instructing NSH-aware device=
s to ignore them; etc.) If that meets your expectations, then, the header s=
upports all three scenarios.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Now, to be=
 precise and for full disclosure, all three scenarios are supported through=
 MD-Type 2, which the draft currently recommends as a &#8220;SHOULD&#8221;
 implementation [Section 3.2].<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Myo<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><b><span lang=3D"EN-US"=
 style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&=
quot;">From:</span></b><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> sfc [<a href=3D"mailto:s=
fc-bounces@ietf.org">mailto:sfc-bounces@ietf.org</a>]
<b>On Behalf Of </b>Xuxiaohu<br>
<b>Sent:</b> 28 February 2015 4:52 AM<br>
<b>To:</b> Jim Guichard (jguichar); <a href=3D"mailto:sfc@ietf.org">sfc@iet=
f.org</a><br>
<b>Subject:</b> Re: [sfc] WG call for adoption of draft-quinn-sfc-nsh<o:p><=
/o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US"><o=
:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US" st=
yle=3D"font-size:16.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:#1F497D">Support.
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US" st=
yle=3D"font-size:16.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US" st=
yle=3D"font-size:16.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:#1F497D">By the way, I hope the NSH could be capable of: 1) conta=
ining the service chain/path info only; 2) containing the metadata
 only ;3) containing both service chain/path info and the metadata. Otherwi=
se, we may need to design a separate header for containing the metadata in =
the case where the service chain/path info has been embodied by other means=
 than the NSH itself. In this way,
 it&#8217;s aligned with the following statement in the SFC architecture dr=
aft:<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US" st=
yle=3D"font-size:16.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<h4 style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left=
:36.0pt;mso-line-height-alt:0pt;page-break-before:always">
<b><span lang=3D"EN-US" style=3D"font-size:16.0pt;font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;;color:#1F497D">&#8220;</span></b><a name=3D"s=
ection-4.3.1"></a><b><span lang=3D"EN-US" style=3D"font-family:&quot;Courie=
r New&quot;"><a href=3D"https://tools.ietf.org/html/draft-ietf-sfc-architec=
ture-04#section-4.3.1"><span lang=3D"EN" style=3D"font-size:11.0pt;color:bl=
ack">4.3.1</span></a></span></b><b><span lang=3D"EN" style=3D"font-size:11.=
0pt;font-family:&quot;Courier New&quot;">.&nbsp;
 Transport Derived SFF<o:p></o:p></span></b></h4>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt;page-break-before:always=
"><span lang=3D"EN" style=3D"font-size:11.0pt;font-family:SimSun"><o:p>&nbs=
p;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt;page-break-before:always=
"><span lang=3D"EN" style=3D"font-size:11.0pt;font-family:SimSun"><o:p>&nbs=
p;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt;page-break-before:always=
"><span lang=3D"EN" style=3D"font-size:11.0pt;font-family:SimSun">&nbsp;&nb=
sp; Service function forwarding, as described above, directly depends<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt;page-break-before:always=
"><span lang=3D"EN" style=3D"font-size:11.0pt;font-family:SimSun">&nbsp;&nb=
sp; upon the use of the service path information contained in the SFC<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt;page-break-before:always=
"><span lang=3D"EN" style=3D"font-size:11.0pt;font-family:SimSun">&nbsp;&nb=
sp; encapsulation.&nbsp; However, existing implementations may not be able =
to<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt;page-break-before:always=
"><span lang=3D"EN" style=3D"font-size:11.0pt;font-family:SimSun">&nbsp;&nb=
sp; act on the SFC encapsulation.&nbsp; These platforms may opt to use<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt;page-break-before:always=
"><span lang=3D"EN" style=3D"font-size:11.0pt;font-family:SimSun">&nbsp;&nb=
sp; existing transport information if it can be arranged to provide<o:p></o=
:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt;page-break-before:always=
"><span lang=3D"EN" style=3D"font-size:11.0pt;font-family:SimSun">&nbsp;&nb=
sp; explicit service path information.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt;page-break-before:always=
"><span lang=3D"EN" style=3D"font-size:11.0pt;font-family:SimSun"><o:p>&nbs=
p;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt;page-break-before:always=
"><span lang=3D"EN" style=3D"font-size:11.0pt;font-family:SimSun">&nbsp;&nb=
sp; This results in the same architectural behavior and meaning for<o:p></o=
:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt;page-break-before:always=
"><span lang=3D"EN" style=3D"font-size:11.0pt;font-family:SimSun">&nbsp;&nb=
sp; service function forwarding and service function paths.&nbsp; It is the=
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt;page-break-before:always=
"><span lang=3D"EN" style=3D"font-size:11.0pt;font-family:SimSun">&nbsp;&nb=
sp; responsibility of the control components to ensure that the transport<o=
:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt;page-break-before:always=
"><span lang=3D"EN" style=3D"font-size:11.0pt;font-family:SimSun">&nbsp;&nb=
sp; path executed in such a case is fully aligned with the path<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt;page-break-before:always=
"><span lang=3D"EN" style=3D"font-size:11.0pt;font-family:SimSun">&nbsp;&nb=
sp; identified by the information in the service chaining encapsulation.<o:=
p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt;page-break-before:always=
"><span lang=3D"EN" style=3D"font-size:11.0pt;font-family:SimSun"><o:p>&nbs=
p;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US" st=
yle=3D"font-size:16.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:#1F497D">&#8221;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US" st=
yle=3D"font-size:16.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US" st=
yle=3D"font-size:16.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:#1F497D">Xiaohu<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US" st=
yle=3D"font-size:16.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><b><span lang=3D"EN-US"=
 style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&=
quot;">From:</span></b><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> sfc [<a href=3D"mailto:s=
fc-bounces@ietf.org">mailto:sfc-bounces@ietf.org</a>]
<b>On Behalf Of </b>Jim Guichard (jguichar)<br>
<b>Sent:</b> Thursday, February 26, 2015 8:47 PM<br>
<b>To:</b> <a href=3D"mailto:sfc@ietf.org">sfc@ietf.org</a><br>
<b>Subject:</b> [sfc] WG call for adoption of draft-quinn-sfc-nsh<o:p></o:p=
></span></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US"><o=
:p>&nbsp;</o:p></span></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US" st=
yle=3D"font-size:9.0pt;font-family:Consolas;color:black">Greetings WG:</spa=
n><span lang=3D"EN-US" style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US" st=
yle=3D"color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US" st=
yle=3D"font-size:9.0pt;font-family:Consolas;color:black">The document draft=
-quinn-sfc-nsh-07 (<a href=3D"https://datatracker.ietf.org/doc/draft-quinn-=
sfc-nsh">https://datatracker.ietf.org/doc/draft-quinn-sfc-nsh</a>/)
 has recently been reissued. The authors of draft-zhang-sfc-sch-03 (<a href=
=3D"http://datatracker.ietf.org/doc/draft-zhang-sfc-sch">http://datatracker=
.ietf.org/doc/draft-zhang-sfc-sch</a>/) have joined the NSH document so tha=
t the WG can focus on a single encapsulation
 document going forward. This new version of NSH includes an <b>open items =
</b>section based on discussion between co-authors and members of the list.=
 The WG will work through this list (and any other issues that need to be a=
dded) over the next weeks. We appreciate
 and recognize the hard work of both the NSH and SCH authors in pushing the=
 SFC encapsulation work forward.</span><span lang=3D"EN-US" style=3D"color:=
black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US" st=
yle=3D"color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US" st=
yle=3D"font-size:9.0pt;font-family:Consolas;color:black">With that said, th=
e chairs are calling for WG adoption of draft-quinn-sfc-nsh-07 as a WG docu=
ment. The call for adoption will run for
 2 weeks ending 3/12/2015.</span><span lang=3D"EN-US" style=3D"color:black"=
><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US" st=
yle=3D"color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US" st=
yle=3D"font-size:9.0pt;font-family:Consolas">Please note that this is a cal=
l for adoption, and not a last call for content of the document. Adopting a=
 WG document simply means that the WG will
 focus its efforts on that particular draft going forward, and use that doc=
ument for resolving open issues and documenting the WG&#8217;s decisions.</=
span><span lang=3D"EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US"><o=
:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US" st=
yle=3D"font-size:9.0pt;font-family:Consolas">Please indicate whether you su=
pport adoption for not, and if not why. Issues you have with the current do=
cument itself can also be raised, but they
 should be raised in the context of what should be changed in the document =
going forward, rather than a pre-condition for adoption.&nbsp;</span><span =
lang=3D"EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US"><o=
:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US" st=
yle=3D"font-size:9.0pt;font-family:Consolas">Finally, now is also a good ti=
me to poll for knowledge of any IPR that applies to this draft, in line wit=
h the IPR disclosure obligations for WG
 participants (see RFCs 3979, 4879, 3669 and 5378 for more details). If you=
 are listed as a document author please respond to this email (to the chair=
s) whether or not you are aware of any relevant IPR.</span><span lang=3D"EN=
-US"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US" st=
yle=3D"font-size:13.5pt;font-family:Consolas;color:black"><o:p>&nbsp;</o:p>=
</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US" st=
yle=3D"font-size:9.0pt;font-family:Consolas;color:black">Jim &amp; Thomas</=
span><span lang=3D"EN-US" style=3D"font-family:Consolas;color:black"><o:p><=
/o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0830EE0ANKGEML512MBSchi_--


From nobody Mon Mar  2 05:19:23 2015
Return-Path: <paulq@cisco.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AE201A875C for <sfc@ietfa.amsl.com>; Mon,  2 Mar 2015 05:19:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 NJo_jEB9njfb for <sfc@ietfa.amsl.com>; Mon,  2 Mar 2015 05:19:20 -0800 (PST)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4036E1A875D for <sfc@ietf.org>; Mon,  2 Mar 2015 05:19:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7128; q=dns/txt; s=iport; t=1425302360; x=1426511960; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Ghm7EAcmPeeZh6rertAINSk1pt8hrvEGHZjI6Ash95s=; b=AnMUiXcPK+CIGqcuO4HebhfnNR7Db5l5IcjDQtPnYHSCRh+N/ULDV4Sn TUZJjrXM8KXnZTS/Sfy+F9jsE/xz3bHKsg4Hh7+e9N738uxbNLD5lFYlZ hPeCf9UWv1h92qmq0H1YGy8iJBTKlxsntFtoG+uGNUuQstm4gFBIxXhSD 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CJBQDmYvRU/5tdJa1agj9DUl6DBr4tAQmFcAIcgQNNAQEBAQEBfIQQAQEEAQEBIApBCxACAQg/AwICAiULFBEBAQQOBYgvDbwVmSUBAQEBAQEBAQEBAQEBAQEBAQEBAQETBIsShG4HgmgvgRQFjXuBfYlHgRqFc4kPgz4jg25vgUR/AQEB
X-IronPort-AV: E=Sophos;i="5.09,675,1418083200";  d="scan'208,217";a="114357991"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by mtv-iport-2.cisco.com with ESMTP; 02 Mar 2015 13:19:19 +0000
Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t22DJIKE012633 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 2 Mar 2015 13:19:19 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.229]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.03.0195.001; Mon, 2 Mar 2015 07:19:18 -0600
From: "Paul Quinn (paulq)" <paulq@cisco.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Thread-Topic: [sfc] draft-quinn-sfc-nsh: Remove Section 2.2
Thread-Index: AdBRDfvGncaUVepTRKWBBq+ZY1ywcwED8uIA
Date: Mon, 2 Mar 2015 13:19:18 +0000
Message-ID: <B3F0AE57-C0FB-4D2D-A273-8AF67A6F0A6D@cisco.com>
References: <787AE7BB302AE849A7480A190F8B933004914121@OPEXCLILM23.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B933004914121@OPEXCLILM23.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.17.229]
Content-Type: multipart/alternative; boundary="_000_B3F0AE57C0FB4D2DA2738AF67A6F0A6Dciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/qYSgLVK9TKNcNsC0IkGy3XumD6Q>
Cc: "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] draft-quinn-sfc-nsh: Remove Section 2.2
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 02 Mar 2015 13:19:21 -0000

--_000_B3F0AE57C0FB4D2DA2738AF67A6F0A6Dciscocom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgTWVkLA0KDQpGaXJzdCBvZmYsIHRoYW5rIHlvdSBmb3IgeW91ciBzdWdnZXN0aW9ucyBhbmQg
ZmVlZGJhY2ssIEnigJltIHdvcmtpbmcgbXkgd2F5IHRocm91Z2ggeW91ciBlbWFpbHMgbm93Lg0K
DQpUaGUgc2VjdGlvbiB3YXMgaW5jbHVkZWQgYXMgYSB3YXkgb2YgcHJvdmlkaW5nIGJhY2tncm91
bmQgdG8gYSByZWFkZXIgd2hvIGp1c3QgY2hvc2UgdG8gcmVhZCB0aGUgTlNIIGRyYWZ0LiAgTm93
IHRoYXQgdGhlIHByb2JsZW0gc3RhdGVtZW50IGlzIGNvbXBsZXRlLCBJIGRvbuKAmXQgaGF2ZSBh
bnkgaXNzdWVzIGluY2x1ZGluZyBhIG5vcm1hdGl2ZSByZWZlcmVuY2UuICBPZiBjb3Vyc2UsIHNp
bmNlIE5TSCBoYXMgYmVlbiBjYWxsZWQgZm9yIGFkb3B0aW9uLCBJ4oCZbGwgd2FpdCB1bnRpbCB0
aGF0IGlzIGRvbmUsIHRoZW4gYXNzdW1pbmcgYWRvcHRpb24gaXMgc3VjY2Vzc2Z1bCwgc29saWNp
dCBmZWVkYmFjayBmcm9tIHRoZSBXRyBmb3IgdGhlIGNoYW5nZS4NCg0KUGF1bA0KDQoNCk9uIEZl
YiAyNSwgMjAxNSwgYXQgMTA6MTYgQU0sIG1vaGFtZWQuYm91Y2FkYWlyQG9yYW5nZS5jb208bWFp
bHRvOm1vaGFtZWQuYm91Y2FkYWlyQG9yYW5nZS5jb20+IHdyb3RlOg0KDQpIaSBQYXVsLA0KDQpJ
IHN1Z2dlc3QgdG8gcmVtb3ZlIFNlY3Rpb24gMi4yLiBBIHBvaW50ZXIgdG8gdGhlIFNGQyBQUyBJ
LUQgd291bGQgc3VmZmljZS4gTm8gbmVlZCB0byBiZSByZWR1bmRhbnQgaGVyZS4NCg0KVGhhbmsg
eW91Lg0KDQpDaGVlcnMsDQpNZWQNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fDQpzZmMgbWFpbGluZyBsaXN0DQpzZmNAaWV0Zi5vcmc8bWFpbHRvOnNmY0Bp
ZXRmLm9yZz4NCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vc2ZjDQoNCg==

--_000_B3F0AE57C0FB4D2DA2738AF67A6F0A6Dciscocom_
Content-Type: text/html; charset="utf-8"
Content-ID: <48E54B47361F874A9965E0F8666AB708@emea.cisco.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsiIGNsYXNzPSIiPg0KSGkgTWVkLA0KPGRpdiBjbGFzcz0i
Ij48YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+Rmlyc3Qgb2ZmLCB0aGFuayB5
b3UgZm9yIHlvdXIgc3VnZ2VzdGlvbnMgYW5kIGZlZWRiYWNrLCBJ4oCZbSB3b3JraW5nIG15IHdh
eSB0aHJvdWdoIHlvdXIgZW1haWxzIG5vdy48L2Rpdj4NCjxkaXYgY2xhc3M9IiI+PGJyIGNsYXNz
PSIiPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPlRoZSBzZWN0aW9uIHdhcyBpbmNsdWRlZCBhcyBh
IHdheSBvZiBwcm92aWRpbmcgYmFja2dyb3VuZCB0byBhIHJlYWRlciB3aG8ganVzdCBjaG9zZSB0
byByZWFkIHRoZSBOU0ggZHJhZnQuICZuYnNwO05vdyB0aGF0IHRoZSBwcm9ibGVtIHN0YXRlbWVu
dCBpcyBjb21wbGV0ZSwgSSBkb27igJl0IGhhdmUgYW55IGlzc3VlcyBpbmNsdWRpbmcgYSBub3Jt
YXRpdmUgcmVmZXJlbmNlLiAmbmJzcDtPZiBjb3Vyc2UsIHNpbmNlIE5TSCBoYXMgYmVlbiBjYWxs
ZWQNCiBmb3IgYWRvcHRpb24sIEnigJlsbCB3YWl0IHVudGlsIHRoYXQgaXMgZG9uZSwgdGhlbiBh
c3N1bWluZyBhZG9wdGlvbiBpcyBzdWNjZXNzZnVsLCBzb2xpY2l0IGZlZWRiYWNrIGZyb20gdGhl
IFdHIGZvciB0aGUgY2hhbmdlLjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj48YnIgY2xhc3M9IiI+DQo8
L2Rpdj4NCjxkaXYgY2xhc3M9IiI+UGF1bDwvZGl2Pg0KPGRpdiBjbGFzcz0iIj48YnIgY2xhc3M9
IiI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPg0KPGRpdj4NCjxibG9ja3F1
b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj5PbiBGZWIgMjUsIDIwMTUs
IGF0IDEwOjE2IEFNLCA8YSBocmVmPSJtYWlsdG86bW9oYW1lZC5ib3VjYWRhaXJAb3JhbmdlLmNv
bSIgY2xhc3M9IiI+DQptb2hhbWVkLmJvdWNhZGFpckBvcmFuZ2UuY29tPC9hPiB3cm90ZTo8L2Rp
dj4NCjxiciBjbGFzcz0iQXBwbGUtaW50ZXJjaGFuZ2UtbmV3bGluZSI+DQo8ZGl2IGNsYXNzPSIi
Pg0KPG1ldGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxNCAoZmls
dGVyZWQgbWVkaXVtKSIgY2xhc3M9IiI+DQo8c3R5bGUgY2xhc3M9IiI+PCEtLQ0KLyogRm9udCBE
ZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDYWxpYnJpOw0KCXBhbm9z
ZS0xOjIgMTUgNSAyIDIgMiA0IDMgMiA0O30NCi8qIFN0eWxlIERlZmluaXRpb25zICovDQpwLk1z
b05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjowY207DQoJbWFy
Z2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNh
bGlicmkiLCJzYW5zLXNlcmlmIjsNCgltc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUzt9DQphOmxp
bmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpi
bHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5
cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7
DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpzcGFuLkVtYWlsU3R5bGUxNw0KCXttc28t
c3R5bGUtdHlwZTpwZXJzb25hbC1jb21wb3NlOw0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7
DQoJY29sb3I6d2luZG93dGV4dDsNCglmb250LXdlaWdodDpub3JtYWw7DQoJZm9udC1zdHlsZTpu
b3JtYWw7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJ
Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgltc28tZmFyZWFzdC1sYW5ndWFn
ZTpFTi1VUzt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJ
bWFyZ2luOjcwLjg1cHQgNzAuODVwdCA3MC44NXB0IDcwLjg1cHQ7fQ0KZGl2LldvcmRTZWN0aW9u
MQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48
eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwv
eG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQg
djpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hh
cGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8ZGl2IGxhbmc9IkZSIiBsaW5rPSJibHVlIiB2
bGluaz0icHVycGxlIiBjbGFzcz0iIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWls
eTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyIgY2xhc3M9IiI+SGkgUGF1bCw8bzpwIGNsYXNzPSIi
PjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyIgY2xhc3M9
IiI+Jm5ic3A7PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5l
dyZxdW90OyIgY2xhc3M9IiI+SSBzdWdnZXN0IHRvIHJlbW92ZSBTZWN0aW9uIDIuMi4gQSBwb2lu
dGVyIHRvIHRoZSBTRkMgUFMgSS1EIHdvdWxkIHN1ZmZpY2UuIE5vIG5lZWQgdG8gYmUgcmVkdW5k
YW50IGhlcmUuPG86cCBjbGFzcz0iIj48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7IiBjbGFzcz0iIj4mbmJzcDs8L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6
MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7IiBjbGFzcz0iIj5UaGFu
ayB5b3UuPG86cCBjbGFzcz0iIj48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7IiBjbGFzcz0iIj4mbmJzcDs8L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7IiBjbGFzcz0iIj5DaGVlcnMs
PG86cCBjbGFzcz0iIj48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NvdXJpZXIgTmV3JnF1b3Q7IiBjbGFzcz0iIj5NZWQ8bzpwIGNsYXNzPSIiPjwvbzpwPjwvc3Bh
bj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX188YnIgY2xhc3M9IiI+DQpzZmMgbWFpbGluZyBsaXN0PGJyIGNsYXNzPSIi
Pg0KPGEgaHJlZj0ibWFpbHRvOnNmY0BpZXRmLm9yZyIgY2xhc3M9IiI+c2ZjQGlldGYub3JnPC9h
PjxiciBjbGFzcz0iIj4NCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vc2Zj
PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjxiciBjbGFzcz0i
Ij4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_B3F0AE57C0FB4D2DA2738AF67A6F0A6Dciscocom_--


From nobody Mon Mar  2 07:17:36 2015
Return-Path: <paulq@cisco.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4A171A8704 for <sfc@ietfa.amsl.com>; Mon,  2 Mar 2015 07:17:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 ow5XD2LkCvXQ for <sfc@ietfa.amsl.com>; Mon,  2 Mar 2015 07:17:33 -0800 (PST)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9BA021A88D9 for <sfc@ietf.org>; Mon,  2 Mar 2015 07:13:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6730; q=dns/txt; s=iport; t=1425309228; x=1426518828; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=/4Yu+zQ4CqO9pqXQ8eWNOY7YOsr0+9JWzLSzR2wICNs=; b=mh52oR6IAKaBpAwGqjB0GwUny1LVcz7xgh+90eiqYlv0XEs54g5BwJed mlRC57+2kWB9izCDfD5X2GChvc1foUfcPQJ/7RyGPRG9mqL3Dv2imJPDG 1QNyGnz4VQDsVIaAxrol0HxWSn9jIoz9MFHvAYaoEp5usojnRIzVJa0wK 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CJBQAmffRU/4UNJK1agj9DUl6DBr4vAQmFcAIcgQVNAQEBAQEBfIQQAQEEAQEBIApBCxACAQg/AwICAiULFBEBAQQOBYgvDbxcmTUBAQEBAQEBAQEBAQEBAQEBAQEBAQETBIsShG4HgmgvgRQFj3iJR5NaI4Nub4FEfwEBAQ
X-IronPort-AV: E=Sophos;i="5.09,675,1418083200";  d="scan'208,217";a="128185436"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by alln-iport-7.cisco.com with ESMTP; 02 Mar 2015 15:13:48 +0000
Received: from xhc-aln-x14.cisco.com (xhc-aln-x14.cisco.com [173.36.12.88]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id t22FDlVS024019 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 2 Mar 2015 15:13:47 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.229]) by xhc-aln-x14.cisco.com ([173.36.12.88]) with mapi id 14.03.0195.001; Mon, 2 Mar 2015 09:13:47 -0600
From: "Paul Quinn (paulq)" <paulq@cisco.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Thread-Topic: [sfc] draft-quinn-sfc-nsh: relatniship with the use cases drafts
Thread-Index: AdBRDaI7xfMTZEmzRd6IIps3ZiTmogEICK4A
Date: Mon, 2 Mar 2015 15:13:46 +0000
Message-ID: <CA29E3DA-324E-4FA3-AC0B-4148E46999D5@cisco.com>
References: <787AE7BB302AE849A7480A190F8B9330049140FD@OPEXCLILM23.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B9330049140FD@OPEXCLILM23.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.17.229]
Content-Type: multipart/alternative; boundary="_000_CA29E3DA324E4FA3AC0B4148E46999D5ciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/TLCHcAKQKKLVbSFscrwz8l2ZC2o>
Cc: "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] draft-quinn-sfc-nsh: relatniship with the use cases drafts
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 02 Mar 2015 15:17:35 -0000

--_000_CA29E3DA324E4FA3AC0B4148E46999D5ciscocom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgTWVkLA0KDQoNCkFyZSB5b3Ugc3VnZ2VzdGluZyB0aGF0IHRoZSB1c2UgY2FzZXMgYmUgaW5j
bHVkZWQgYXMgcmVmZXJlbmNlcywgb3IgZXhwbGljaXQgcmVmZXJlbmNlZD8gIFBlcmhhcHMgYSBs
b2dpY2FsIHBhdGggZm9yd2FyZCwgaWYgTlNIIGlzIGFkb3B0ZWQsIHRoYXQgcGVyaGFwcyB0aGUg
dXNlIGNhc2VzIGNhbiBiZSB1cGRhdGVkIHRvIHJlZmxlY3QgdGhlIOKAnFNGQyBlbmNhcOKAnS4N
Cg0KUGF1bA0KDQoNCk9uIEZlYiAyNSwgMjAxNSwgYXQgMTA6MTMgQU0sIG1vaGFtZWQuYm91Y2Fk
YWlyQG9yYW5nZS5jb208bWFpbHRvOm1vaGFtZWQuYm91Y2FkYWlyQG9yYW5nZS5jb20+IHdyb3Rl
Og0KDQpSZS0sDQoNCkl0IGlzIHVuZm9ydHVuYXRlIHRoZSBjdXJyZW50IE5TSCBzcGVjaWZpY2F0
aW9uIGRvZXMgbm90IHJlbHkgb24gdGhlIFNGQyB1c2UgY2FzZXMgYXMgZG9jdW1lbnRlZCBieSB0
aGUgV0cuDQoNCkRvZXMgdGhpcyBtZWFuIHRoYXQgdGhvc2UgYXJlIHVzZWxlc3M/IFRoYXQgbm8g
KGNvbW1vbikgcmVxdWlyZW1lbnRzIGNhbiBiZSBkZXJpdmVkIGZyb20gdGhvc2UgSS1EcyB0byBn
dWlkZSB0aGUgc3BlY2lmaWNhdGlvbiBvZiB0aGUgTlNIIGhlYWRlcj8NCg0KQ2hlZXJzLA0KTWVk
DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0Kc2ZjIG1h
aWxpbmcgbGlzdA0Kc2ZjQGlldGYub3JnPG1haWx0bzpzZmNAaWV0Zi5vcmc+DQpodHRwczovL3d3
dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NmYw0KDQo=

--_000_CA29E3DA324E4FA3AC0B4148E46999D5ciscocom_
Content-Type: text/html; charset="utf-8"
Content-ID: <C6B39DFE43C87B47A21316CAD7959B6B@emea.cisco.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsiIGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj5IaSBNZWQs
PC9kaXY+DQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0i
Ij48YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+QXJlIHlvdSBzdWdnZXN0aW5n
IHRoYXQgdGhlIHVzZSBjYXNlcyBiZSBpbmNsdWRlZCBhcyByZWZlcmVuY2VzLCBvciBleHBsaWNp
dCByZWZlcmVuY2VkPyAmbmJzcDtQZXJoYXBzIGEgbG9naWNhbCBwYXRoIGZvcndhcmQsIGlmIE5T
SCBpcyBhZG9wdGVkLCB0aGF0IHBlcmhhcHMgdGhlIHVzZSBjYXNlcyBjYW4gYmUgdXBkYXRlZCB0
byByZWZsZWN0IHRoZSDigJxTRkMgZW5jYXDigJ0uPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPjxiciBj
bGFzcz0iIj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj5QYXVsPC9kaXY+DQo8ZGl2IGNsYXNzPSIi
PjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGJyIGNsYXNzPSIiPg0KPGRpdj4NCjxibG9ja3F1b3Rl
IHR5cGU9ImNpdGUiIGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj5PbiBGZWIgMjUsIDIwMTUsIGF0
IDEwOjEzIEFNLCA8YSBocmVmPSJtYWlsdG86bW9oYW1lZC5ib3VjYWRhaXJAb3JhbmdlLmNvbSIg
Y2xhc3M9IiI+DQptb2hhbWVkLmJvdWNhZGFpckBvcmFuZ2UuY29tPC9hPiB3cm90ZTo8L2Rpdj4N
CjxiciBjbGFzcz0iQXBwbGUtaW50ZXJjaGFuZ2UtbmV3bGluZSI+DQo8ZGl2IGNsYXNzPSIiPg0K
PG1ldGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxNCAoZmlsdGVy
ZWQgbWVkaXVtKSIgY2xhc3M9IiI+DQo8c3R5bGUgY2xhc3M9IiI+PCEtLQ0KLyogRm9udCBEZWZp
bml0aW9ucyAqLw0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDYWxpYnJpOw0KCXBhbm9zZS0x
OjIgMTUgNSAyIDIgMiA0IDMgMiA0O30NCi8qIFN0eWxlIERlZmluaXRpb25zICovDQpwLk1zb05v
cm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjowY207DQoJbWFyZ2lu
LWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGli
cmkiLCJzYW5zLXNlcmlmIjsNCgltc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUzt9DQphOmxpbmss
IHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpibHVl
Ow0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVy
bGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7DQoJ
dGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpzcGFuLkVtYWlsU3R5bGUxNw0KCXttc28tc3R5
bGUtdHlwZTpwZXJzb25hbC1jb21wb3NlOw0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7DQoJ
Y29sb3I6d2luZG93dGV4dDsNCglmb250LXdlaWdodDpub3JtYWw7DQoJZm9udC1zdHlsZTpub3Jt
YWw7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9u
dC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgltc28tZmFyZWFzdC1sYW5ndWFnZTpF
Ti1VUzt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFy
Z2luOjcwLjg1cHQgNzAuODVwdCA3MC44NXB0IDcwLjg1cHQ7fQ0KZGl2LldvcmRTZWN0aW9uMQ0K
CXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1s
Pg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1s
PjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpl
eHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVs
YXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8ZGl2IGxhbmc9IkZSIiBsaW5rPSJibHVlIiB2bGlu
az0icHVycGxlIiBjbGFzcz0iIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTom
cXVvdDtDb3VyaWVyIE5ldyZxdW90OyIgY2xhc3M9IiI+UmUtLDxvOnAgY2xhc3M9IiI+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7IiBjbGFzcz0iIj4mbmJz
cDs8L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0
eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7
IiBjbGFzcz0iIj5JdCBpcyB1bmZvcnR1bmF0ZSB0aGUgY3VycmVudCBOU0ggc3BlY2lmaWNhdGlv
biBkb2VzIG5vdCByZWx5IG9uIHRoZSBTRkMgdXNlIGNhc2VzIGFzIGRvY3VtZW50ZWQgYnkgdGhl
IFdHLg0KPG86cCBjbGFzcz0iIj48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7IiBjbGFzcz0iIj4mbmJzcDs8L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7IiBjbGFzcz0iIj5Eb2VzIHRo
aXMgbWVhbiB0aGF0IHRob3NlIGFyZSB1c2VsZXNzPyBUaGF0IG5vIChjb21tb24pIHJlcXVpcmVt
ZW50cyBjYW4gYmUgZGVyaXZlZCBmcm9tIHRob3NlIEktRHMgdG8gZ3VpZGUgdGhlIHNwZWNpZmlj
YXRpb24gb2YgdGhlIE5TSCBoZWFkZXI/DQo8bzpwIGNsYXNzPSIiPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6
ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDsiIGNsYXNzPSIiPiZu
YnNwOzwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIg
c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVv
dDsiIGNsYXNzPSIiPkNoZWVycyw8bzpwIGNsYXNzPSIiPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDsiIGNsYXNzPSIiPk1lZA0KPG86
cCBjbGFzcz0iIj48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCl9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPGJyIGNsYXNzPSIiPg0Kc2ZjIG1h
aWxpbmcgbGlzdDxiciBjbGFzcz0iIj4NCjxhIGhyZWY9Im1haWx0bzpzZmNAaWV0Zi5vcmciIGNs
YXNzPSIiPnNmY0BpZXRmLm9yZzwvYT48YnIgY2xhc3M9IiI+DQpodHRwczovL3d3dy5pZXRmLm9y
Zy9tYWlsbWFuL2xpc3RpbmZvL3NmYzxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3Rl
Pg0KPC9kaXY+DQo8YnIgY2xhc3M9IiI+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_CA29E3DA324E4FA3AC0B4148E46999D5ciscocom_--


From nobody Mon Mar  2 07:42:49 2015
Return-Path: <N.Leymann@telekom.de>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A37431A0054 for <sfc@ietfa.amsl.com>; Mon,  2 Mar 2015 07:42:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.859
X-Spam-Level: 
X-Spam-Status: No, score=-3.859 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 oPTBdqIYQ5kj for <sfc@ietfa.amsl.com>; Mon,  2 Mar 2015 07:42:44 -0800 (PST)
Received: from tcmail43.telekom.de (tcmail43.telekom.de [80.149.113.173]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C46B81A1BA3 for <sfc@ietf.org>; Mon,  2 Mar 2015 07:42:25 -0800 (PST)
Received: from qdezc2.de.t-internal.com ([10.125.181.10]) by tcmail41.telekom.de with ESMTP; 02 Mar 2015 16:42:21 +0100
X-IronPort-AV: E=Sophos;i="5.09,676,1418079600";  d="scan'208,217";a="221763333"
Received: from he113598.emea1.cds.t-internal.com ([10.125.65.117]) by qde0ps.de.t-internal.com with ESMTP/TLS/AES128-SHA; 02 Mar 2015 16:42:20 +0100
Received: from HE100014.emea1.cds.t-internal.com (10.125.65.197) by HE113598.emea1.cds.t-internal.com (10.125.65.117) with Microsoft SMTP Server (TLS) id 8.3.377.0; Mon, 2 Mar 2015 16:42:20 +0100
Received: from HE111543.emea1.cds.t-internal.com ([10.125.90.96]) by HE100014.emea1.cds.t-internal.com ([10.125.65.197]) with mapi; Mon, 2 Mar 2015 16:42:19 +0100
From: <N.Leymann@telekom.de>
To: <jguichar@cisco.com>, <sfc@ietf.org>
Date: Mon, 2 Mar 2015 16:42:18 +0100
Thread-Topic: WG call for adoption of draft-quinn-sfc-nsh
Thread-Index: AQHQUcJRZDObBxbiIUWmIP9lX1xWp50JWzug
Message-ID: <9762ACF04FA26B4388476841256BDE020130FE55A571@HE111543.emea1.cds.t-internal.com>
References: <D1147FF5.844D%jguichar@cisco.com>
In-Reply-To: <D1147FF5.844D%jguichar@cisco.com>
Accept-Language: de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE
Content-Type: multipart/alternative; boundary="_000_9762ACF04FA26B4388476841256BDE020130FE55A571HE111543eme_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/xzsRk0N1KO8oYxweiTbHvGncQLk>
Subject: Re: [sfc] WG call for adoption of draft-quinn-sfc-nsh
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 02 Mar 2015 15:42:48 -0000

--_000_9762ACF04FA26B4388476841256BDE020130FE55A571HE111543eme_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

support.

  Regards

     Nic

Von: sfc [mailto:sfc-bounces@ietf.org] Im Auftrag von Jim Guichard (jguicha=
r)
Gesendet: Donnerstag, 26. Februar 2015 13:47
An: sfc@ietf.org
Betreff: [sfc] WG call for adoption of draft-quinn-sfc-nsh

Greetings WG:

The document draft-quinn-sfc-nsh-07 (https://datatracker.ietf.org/doc/draft=
-quinn-sfc-nsh/) has recently been reissued. The authors of draft-zhang-sfc=
-sch-03 (http://datatracker.ietf.org/doc/draft-zhang-sfc-sch/) have joined =
the NSH document so that the WG can focus on a single encapsulation documen=
t going forward. This new version of NSH includes an open items section bas=
ed on discussion between co-authors and members of the list. The WG will wo=
rk through this list (and any other issues that need to be added) over the =
next weeks. We appreciate and recognize the hard work of both the NSH and S=
CH authors in pushing the SFC encapsulation work forward.

With that said, the chairs are calling for WG adoption of draft-quinn-sfc-n=
sh-07 as a WG document. The call for adoption will run for 2 weeks ending 3=
/12/2015.

Please note that this is a call for adoption, and not a last call for conte=
nt of the document. Adopting a WG document simply means that the WG will fo=
cus its efforts on that particular draft going forward, and use that docume=
nt for resolving open issues and documenting the WG's decisions.

Please indicate whether you support adoption for not, and if not why. Issue=
s you have with the current document itself can also be raised, but they sh=
ould be raised in the context of what should be changed in the document goi=
ng forward, rather than a pre-condition for adoption.

Finally, now is also a good time to poll for knowledge of any IPR that appl=
ies to this draft, in line with the IPR disclosure obligations for WG parti=
cipants (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are l=
isted as a document author please respond to this email (to the chairs) whe=
ther or not you are aware of any relevant IPR.

Jim & Thomas

--_000_9762ACF04FA26B4388476841256BDE020130FE55A571HE111543eme_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV=3D"Content-Type" CONTENT=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.E-MailFormatvorlage17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DDE link=3Dblue vlink=
=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'fon=
t-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi,<o:p></o=
:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-fam=
ily:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p cl=
ass=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans=
-serif";color:#1F497D'>support.<o:p></o:p></span></p><p class=3DMsoNormal><=
span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F=
497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-=
size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp; Regard=
s<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt=
;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span>=
</p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calib=
ri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp; Nic<o:p></o:p></sp=
an></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Ca=
libri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div st=
yle=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm=
'><p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Taho=
ma","sans-serif"'>Von:</span></b><span style=3D'font-size:10.0pt;font-famil=
y:"Tahoma","sans-serif"'> sfc [mailto:sfc-bounces@ietf.org] <b>Im Auftrag v=
on </b>Jim Guichard (jguichar)<br><b>Gesendet:</b> Donnerstag, 26. Februar =
2015 13:47<br><b>An:</b> sfc@ietf.org<br><b>Betreff:</b> [sfc] WG call for =
adoption of draft-quinn-sfc-nsh<o:p></o:p></span></p></div></div><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p class=3DMsoNormal><span styl=
e=3D'font-size:9.0pt;font-family:Consolas;color:black'>Greetings WG:</span>=
<span style=3D'color:black'><o:p></o:p></span></p></div><div><p class=3DMso=
Normal><span style=3D'color:black'><o:p>&nbsp;</o:p></span></p></div><div><=
p class=3DMsoNormal><span style=3D'font-size:9.0pt;font-family:Consolas;col=
or:black'>The document draft-quinn-sfc-nsh-07 (<a href=3D"https://datatrack=
er.ietf.org/doc/draft-quinn-sfc-nsh">https://datatracker.ietf.org/doc/draft=
-quinn-sfc-nsh</a>/) has recently been reissued. The authors of draft-zhang=
-sfc-sch-03 (<a href=3D"http://datatracker.ietf.org/doc/draft-zhang-sfc-sch=
">http://datatracker.ietf.org/doc/draft-zhang-sfc-sch</a>/) have joined the=
 NSH document so that the WG can focus on a single encapsulation document g=
oing forward. This new version of NSH includes an <b>open items </b>section=
 based on discussion between co-authors and members of the list. The WG wil=
l work through this list (and any other issues that need to be added) over =
the next weeks. We appreciate and recognize the hard work of both the NSH a=
nd SCH authors in pushing the SFC encapsulation work forward.</span><span s=
tyle=3D'color:black'><o:p></o:p></span></p></div><div><p class=3DMsoNormal>=
<span style=3D'color:black'><o:p>&nbsp;</o:p></span></p></div><div><p class=
=3DMsoNormal><span style=3D'font-size:9.0pt;font-family:Consolas;color:blac=
k'>With that said, the chairs are calling for WG adoption of draft-quinn-sf=
c-nsh-07 as a WG document. The call for adoption will run for 2 weeks endin=
g 3/12/2015.</span><span style=3D'color:black'><o:p></o:p></span></p></div>=
<div><p class=3DMsoNormal><span style=3D'color:black'><o:p>&nbsp;</o:p></sp=
an></p></div><div><p class=3DMsoNormal><span style=3D'font-size:9.0pt;font-=
family:Consolas'>Please note that this is a call for adoption, and not a la=
st call for content of the document. Adopting a WG document simply means th=
at the WG will focus its efforts on that particular draft going forward, an=
d use that document for resolving open issues and documenting the WG&#8217;=
s decisions.</span><o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbs=
p;</o:p></p></div><div><p class=3DMsoNormal><span style=3D'font-size:9.0pt;=
font-family:Consolas'>Please indicate whether you support adoption for not,=
 and if not why. Issues you have with the current document itself can also =
be raised, but they should be raised in the context of what should be chang=
ed in the document going forward, rather than a pre-condition for adoption.=
&nbsp;</span><o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:=
p></p></div><div><p class=3DMsoNormal><span style=3D'font-size:9.0pt;font-f=
amily:Consolas'>Finally, now is also a good time to poll for knowledge of a=
ny IPR that applies to this draft, in line with the IPR disclosure obligati=
ons for WG participants (see RFCs 3979, 4879, 3669 and 5378 for more detail=
s). If you are listed as a document author please respond to this email (to=
 the chairs) whether or not you are aware of any relevant IPR.</span><o:p><=
/o:p></p></div><div><p class=3DMsoNormal><span style=3D'font-size:13.5pt;fo=
nt-family:Consolas;color:black'><o:p>&nbsp;</o:p></span></p></div><div><p c=
lass=3DMsoNormal><span style=3D'font-size:9.0pt;font-family:Consolas;color:=
black'>Jim &amp; Thomas</span><span style=3D'font-family:Consolas;color:bla=
ck'><o:p></o:p></span></p></div></div></div></body></html>=

--_000_9762ACF04FA26B4388476841256BDE020130FE55A571HE111543eme_--


From nobody Mon Mar  2 07:48:36 2015
Return-Path: <paulq@cisco.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAB5F1A0067 for <sfc@ietfa.amsl.com>; Mon,  2 Mar 2015 07:48:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 eBaB0hcmX6Ye for <sfc@ietfa.amsl.com>; Mon,  2 Mar 2015 07:48:31 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 842D41A0023 for <sfc@ietf.org>; Mon,  2 Mar 2015 07:48:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8792; q=dns/txt; s=iport; t=1425311312; x=1426520912; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=1TU+5jHy5Tj5Ax5MZUmlXvLjxgH4IoMCkV/9e7RMpAY=; b=gngWvOqqoGSZHMq/pLPzlrTczvRIAxP/WOkADBD8Yi1Dsn7BIIS9pISB ZRBVIOoGLIg6OFACIl3xOhypGtuZbawVhTdntgJnVFEta6RmV/xhTimsF cxhV4PWxbZa0ozOPU7GrwQKzMf3HYHLXHZIUb7ERwAbx7iXva1byN3DFO 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CEBQDdhfRU/4ENJK1agj9DgTCDBsQpAhyBB00BAQEBAQF8hBABAQQjCkwQAgEIPwMCAgIwFBEBAQQOBYgvvHWZOgEBAQEBAQEBAQEBAQEBAQEBAQEBAReLEoRuB4JoL4EUBY94iUeTWiOBfYFxb4FEfwEBAQ
X-IronPort-AV: E=Sophos;i="5.09,676,1418083200";  d="scan'208,217";a="397122613"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-9.cisco.com with ESMTP; 02 Mar 2015 15:48:31 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id t22FmU1A014572 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 2 Mar 2015 15:48:30 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.229]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.03.0195.001; Mon, 2 Mar 2015 09:48:30 -0600
From: "Paul Quinn (paulq)" <paulq@cisco.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Thread-Topic: draft-quinn-sfc-nsh: Service Index
Thread-Index: AdBREQqj5oD1Ue4YR+yaXvgR38hh1QEIZR4A
Date: Mon, 2 Mar 2015 15:48:30 +0000
Message-ID: <2D75BF2B-CC3B-4548-808D-F018F62660B1@cisco.com>
References: <787AE7BB302AE849A7480A190F8B933004914174@OPEXCLILM23.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B933004914174@OPEXCLILM23.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.17.229]
Content-Type: multipart/alternative; boundary="_000_2D75BF2BCC3B4548808DF018F62660B1ciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/oX8TjmjErjC-rs_7gtrCNLWeQXQ>
Cc: "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] draft-quinn-sfc-nsh: Service Index
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 02 Mar 2015 15:48:33 -0000

--_000_2D75BF2BCC3B4548808DF018F62660B1ciscocom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgTWVkLA0KDQoNCk9uIEZlYiAyNSwgMjAxNSwgYXQgMTA6MzggQU0sIG1vaGFtZWQuYm91Y2Fk
YWlyQG9yYW5nZS5jb208bWFpbHRvOm1vaGFtZWQuYm91Y2FkYWlyQG9yYW5nZS5jb20+IHdyb3Rl
Og0KDQpIaSBQYXVsLA0KDQpUaGUgY3VycmVudCB0ZXh0IGlzIGNsZWFyIGFib3V0IHRoZSBTZXJ2
aWNlIEluZGV4IGJ1dCBpcyBpdCBtYW5kYXRvcnkgdG8gaW5jbHVkZSBpdCBpbiB0aGUgaGVhZGVy
PyBXb3VsZG7igJl0IHRoaXMgaW5mb3JtYXRpb24gYmUgYXZhaWxhYmxlIGxvY2FsbHkgaW4gdGhl
IHNlcnZpY2Ugbm9kZXM/DQoNCg0KDQpUaGUgaW5kZXggaW4gbWFuZGF0b3J5LCBpdCBwcm92aWRl
cyBzZXZlcmFsIGtleSBiZW5lZml0cyBmb3IgdGhlIHByb3RvY29sOg0KDQoxLiAgUHJvdmlkZXMg
c2ltcGxlIGxvY2F0aW9uIHdpdGhpbiBhIHNlcnZpY2UgcGF0aCwgdXNlZCBmb3IgU0ZGIG92ZXJs
YXkgbWFwcGluZw0KMi4gIFByb3ZpZGVzIHNpbXBsZSBzdXBwb3J0IGZvciBjeWNsZXMgKGFuZCBz
cGlyYWxzKSB3aXRoIHRoZSBncmFwaC4NCjMuICBQcm92aWRlcywgdG8gYW4gYWRtaW5pc3RyYXRv
ciwgdGhlIGFiaWxpdHkgdG8gcXVpY2tseSBhbmFseXplIGEgcGFja2V0IGFuZCBrbm93IHdoZXJl
IGl0IGlzLCBhbmQgd2hlcmUgaXQgaGFzIGJlZW4gYW5kIHdoZXJlIGl0cyBnb2luZy4NCjQuICBM
b29wIGRldGVjdGlvbiB3aXRoaW4gYSBnaXZlbiBwYXRoDQoNCg0KDQpUaGUgdGV4dCBleHBsYWlu
IHRoYXQgU0kgYWxsb3dzIHRvIGRldGVjdCBsb29wcywgYnV0IGlzbuKAmXQgdGhlIGxvb3AgZGV0
ZWN0ZWQgdG9vIGxhdGUgaW4gdGhlIHNlcnZpY2UgY2hhaW4/IFdvdWxkbuKAmXQgYmUgb3B0aW1h
bCB0byBkZXRlY3QgdGhlIGxvb3AgZWFybGllcj8NCg0KSWYgeW91IGFyZSBhc2tpbmcgaWYgdGhl
IGNvbnRyb2wgcGxhbmUgc2hvdWxkIGVuc3VyZSB0aGF0IGEgbG9vcCBpc27igJl0IHByb3Zpc2lv
bmVkLCBzdXJlLCBpbiB0aGUgaWRlYWwgY2FzZSBidXQgaGF2aW5nIGRhdGFwbGFuZSBkZXRlY3Rp
b24gaXMgdmVyeSBpbXBvcnRhbnQgdG8gZW5zdXJlIHBhY2tldCBmb3J3YXJkaW5nIGlzbuKAmXQg
YnJva2VuLg0KDQoNCg0KQlRXLCB3aGF0IGlzIHRoZSBiZWhhdmlvciB3aGVuIHNldmVyYWwgU0Zz
IGFyZSBlbWJlZGRlZCBpbiB0aGUgc2FtZSBub2RlICh3aGljaCBpbmZvcm1hdGlvbiBpcyB1c2Vk
IHRvIGRpcmVjdCB0aGUgdHJhZmZpYyB0byB0aGUgYXBwcm9wcmlhdGUgU0YpPw0KDQpUaGUgYmVo
YXZpb3Igc2hvdWxkIHJlbWFpbiBjb25zaXN0ZW50OiB0aGUgU0YocykgZGVjcmVtZW50cyB0aGUg
aW5kZXguDQoNCg0K

--_000_2D75BF2BCC3B4548808DF018F62660B1ciscocom_
Content-Type: text/html; charset="utf-8"
Content-ID: <8F5058A67992A44692EEC41EAA3C922F@emea.cisco.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsiIGNsYXNzPSIiPg0KSGkgTWVkLA0KPGRpdiBjbGFzcz0i
Ij48YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPg0KPC9k
aXY+DQo8ZGl2IGNsYXNzPSIiPg0KPGRpdj4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNz
PSIiPg0KPGRpdiBjbGFzcz0iIj5PbiBGZWIgMjUsIDIwMTUsIGF0IDEwOjM4IEFNLCA8YSBocmVm
PSJtYWlsdG86bW9oYW1lZC5ib3VjYWRhaXJAb3JhbmdlLmNvbSIgY2xhc3M9IiI+DQptb2hhbWVk
LmJvdWNhZGFpckBvcmFuZ2UuY29tPC9hPiB3cm90ZTo8L2Rpdj4NCjxiciBjbGFzcz0iQXBwbGUt
aW50ZXJjaGFuZ2UtbmV3bGluZSI+DQo8ZGl2IGNsYXNzPSIiPg0KPG1ldGEgbmFtZT0iR2VuZXJh
dG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxNCAoZmlsdGVyZWQgbWVkaXVtKSIgY2xhc3M9
IiI+DQo8c3R5bGUgY2xhc3M9IiI+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQt
ZmFjZQ0KCXtmb250LWZhbWlseTpDYWxpYnJpOw0KCXBhbm9zZS0xOjIgMTUgNSAyIDIgMiA0IDMg
MiA0O30NCi8qIFN0eWxlIERlZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFs
LCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjowY207DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0K
CWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsN
Cgltc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUzt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5r
DQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlv
bjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21z
by1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVu
ZGVybGluZTt9DQpzcGFuLkVtYWlsU3R5bGUxNw0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1j
b21wb3NlOw0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7DQoJY29sb3I6d2luZG93dGV4dDsN
Cglmb250LXdlaWdodDpub3JtYWw7DQoJZm9udC1zdHlsZTpub3JtYWw7fQ0KLk1zb0NocERlZmF1
bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmki
LCJzYW5zLXNlcmlmIjsNCgltc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUzt9DQpAcGFnZSBXb3Jk
U2VjdGlvbjENCgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcwLjg1cHQgNzAuODVw
dCA3MC44NXB0IDcwLjg1cHQ7fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9u
MTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0
cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1b
aWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRt
YXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5k
aWZdLS0+DQo8ZGl2IGxhbmc9IkZSIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIiBjbGFzcz0i
Ij4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZx
dW90OyIgY2xhc3M9IiI+SGkgUGF1bCw8bzpwIGNsYXNzPSIiPjwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZh
bWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyIgY2xhc3M9IiI+Jm5ic3A7PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXpl
OjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyIgY2xhc3M9IiI+VGhl
IGN1cnJlbnQgdGV4dCBpcyBjbGVhciBhYm91dCB0aGUgU2VydmljZSBJbmRleCBidXQgaXMgaXQg
bWFuZGF0b3J5IHRvIGluY2x1ZGUgaXQgaW4gdGhlIGhlYWRlcj8gV291bGRu4oCZdCB0aGlzIGlu
Zm9ybWF0aW9uIGJlIGF2YWlsYWJsZSBsb2NhbGx5IGluIHRoZSBzZXJ2aWNlDQogbm9kZXM/IDxv
OnAgY2xhc3M9IiI+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjwvcD4N
CjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+PGJyIGNsYXNzPSIi
Pg0KPC9kaXY+DQo8ZGl2PjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRpdj48YnIgY2xhc3M9IiI+
DQo8L2Rpdj4NCjxkaXY+VGhlIGluZGV4IGluIG1hbmRhdG9yeSwgaXQgcHJvdmlkZXMgc2V2ZXJh
bCBrZXkgYmVuZWZpdHMgZm9yIHRoZSBwcm90b2NvbDo8L2Rpdj4NCjxkaXY+PGJyIGNsYXNzPSIi
Pg0KPC9kaXY+DQo8ZGl2PjEuICZuYnNwO1Byb3ZpZGVzIHNpbXBsZSBsb2NhdGlvbiB3aXRoaW4g
YSBzZXJ2aWNlIHBhdGgsIHVzZWQgZm9yIFNGRiBvdmVybGF5IG1hcHBpbmc8L2Rpdj4NCjxkaXY+
Mi4gJm5ic3A7UHJvdmlkZXMgc2ltcGxlIHN1cHBvcnQgZm9yIGN5Y2xlcyAoYW5kIHNwaXJhbHMp
IHdpdGggdGhlIGdyYXBoLiAmbmJzcDs8L2Rpdj4NCjxkaXY+My4gJm5ic3A7UHJvdmlkZXMsIHRv
IGFuIGFkbWluaXN0cmF0b3IsIHRoZSBhYmlsaXR5IHRvIHF1aWNrbHkgYW5hbHl6ZSBhIHBhY2tl
dCBhbmQga25vdyB3aGVyZSBpdCBpcywgYW5kIHdoZXJlIGl0IGhhcyBiZWVuIGFuZCB3aGVyZSBp
dHMgZ29pbmcuPC9kaXY+DQo8ZGl2PjQuICZuYnNwO0xvb3AgZGV0ZWN0aW9uIHdpdGhpbiBhIGdp
dmVuIHBhdGg8L2Rpdj4NCjxkaXY+PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8YnIgY2xhc3M9IiI+
DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIiBjbGFzcz0iIj4NCjxkaXYgY2xhc3M9IiI+DQo8ZGl2
IGxhbmc9IkZSIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIiBjbGFzcz0iIj4NCjxkaXYgY2xh
c3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1V
UyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcm
cXVvdDsiIGNsYXNzPSIiPiZuYnNwOzwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q291cmllciBOZXcmcXVvdDsiIGNsYXNzPSIiPlRoZSB0ZXh0IGV4cGxhaW4gdGhhdCBTSSBh
bGxvd3MgdG8gZGV0ZWN0IGxvb3BzLCBidXQgaXNu4oCZdCB0aGUgbG9vcCBkZXRlY3RlZCB0b28g
bGF0ZSBpbiB0aGUgc2VydmljZSBjaGFpbj8gV291bGRu4oCZdCBiZSBvcHRpbWFsIHRvIGRldGVj
dCB0aGUgbG9vcCBlYXJsaWVyPzxvOnAgY2xhc3M9IiI+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90
ZT4NCjxkaXY+PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8ZGl2PklmIHlvdSBhcmUgYXNraW5nIGlm
IHRoZSBjb250cm9sIHBsYW5lIHNob3VsZCBlbnN1cmUgdGhhdCBhIGxvb3AgaXNu4oCZdCBwcm92
aXNpb25lZCwgc3VyZSwgaW4gdGhlIGlkZWFsIGNhc2UgYnV0IGhhdmluZyBkYXRhcGxhbmUgZGV0
ZWN0aW9uIGlzIHZlcnkgaW1wb3J0YW50IHRvIGVuc3VyZSBwYWNrZXQgZm9yd2FyZGluZyBpc27i
gJl0IGJyb2tlbi4gJm5ic3A7PC9kaXY+DQo8ZGl2PjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGJy
IGNsYXNzPSIiPg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSIgY2xhc3M9IiI+DQo8ZGl2IGNsYXNz
PSIiPg0KPGRpdiBsYW5nPSJGUiIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSIgY2xhc3M9IiI+
DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
bGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nv
dXJpZXIgTmV3JnF1b3Q7IiBjbGFzcz0iIj4mbmJzcDs8L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7IiBjbGFzcz0iIj5CVFcsIHdoYXQgaXMgdGhl
IGJlaGF2aW9yIHdoZW4gc2V2ZXJhbCBTRnMgYXJlIGVtYmVkZGVkIGluIHRoZSBzYW1lIG5vZGUg
KHdoaWNoIGluZm9ybWF0aW9uIGlzIHVzZWQgdG8gZGlyZWN0IHRoZSB0cmFmZmljIHRvIHRoZSBh
cHByb3ByaWF0ZSBTRik/ICZuYnNwOzwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+
DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2PjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRpdj5UaGUgYmVo
YXZpb3Igc2hvdWxkIHJlbWFpbiBjb25zaXN0ZW50OiB0aGUgU0YocykgZGVjcmVtZW50cyB0aGUg
aW5kZXguPC9kaXY+DQo8ZGl2PjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPC9kaXY+DQo8YnIgY2xh
c3M9IiI+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_2D75BF2BCC3B4548808DF018F62660B1ciscocom_--


From nobody Mon Mar  2 07:56:27 2015
Return-Path: <paulq@cisco.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8250D1A0068 for <sfc@ietfa.amsl.com>; Mon,  2 Mar 2015 07:56:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 yzkOelb3gDHB for <sfc@ietfa.amsl.com>; Mon,  2 Mar 2015 07:56:24 -0800 (PST)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F40A1A0023 for <sfc@ietf.org>; Mon,  2 Mar 2015 07:56:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11862; q=dns/txt; s=iport; t=1425311784; x=1426521384; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=QZPQAUBoCbJAJQ+h33eKa0P7UDEGAMVfILw7ObG6VdM=; b=F+1BPq7v653YiM5BI12iVwq8gX3fei9+haqO75HCwOANwtn6qRNJXiGh Q8uR3RHCDaF/Fphd3nmgII1CQR4WopiQEBFWDdP13Wc48wp7sNl+Hhoas JFSLeGocv2zY07Nav21/a2hgSXKn3oc3YrnxLPcbQUDxYFGgooaZHL7yn A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CEBQAzh/RU/5hdJa1agj9DgTCDBsQpAhyBB00BAQEBAQF8hBABAQQjCkwQAgEIPwMCAgIwFBEBAQQOBYgvvHKZBQEBAQEBAQEBAQEBAQEBAQEBAQEBAReLEoRuB4JoL4EUBY17gX2JR5NaI4ICHIFQb4FEfwEBAQ
X-IronPort-AV: E=Sophos;i="5.09,676,1418083200";  d="scan'208,217";a="114409584"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by mtv-iport-2.cisco.com with ESMTP; 02 Mar 2015 15:56:23 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id t22FuNIf010406 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 2 Mar 2015 15:56:23 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.229]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.03.0195.001; Mon, 2 Mar 2015 09:56:23 -0600
From: "Paul Quinn (paulq)" <paulq@cisco.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Thread-Topic: draft-quinn-sfc-nsh: O bit
Thread-Index: AdBREzsXkwltKcHTSMi8A93b3Y+HuAEIH1cA
Date: Mon, 2 Mar 2015 15:56:22 +0000
Message-ID: <08825924-F422-4C85-BEC0-8F71DD36427D@cisco.com>
References: <787AE7BB302AE849A7480A190F8B9330049141E3@OPEXCLILM23.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B9330049141E3@OPEXCLILM23.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.17.229]
Content-Type: multipart/alternative; boundary="_000_08825924F4224C85BEC08F71DD36427Dciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/LjdkdONEWAJTrnNmwhOJVOeH_r8>
Cc: "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] draft-quinn-sfc-nsh: O bit
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 02 Mar 2015 15:56:25 -0000

--_000_08825924F4224C85BEC08F71DD36427Dciscocom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

DQpPbiBGZWIgMjUsIDIwMTUsIGF0IDEwOjUzIEFNLCBtb2hhbWVkLmJvdWNhZGFpckBvcmFuZ2Uu
Y29tPG1haWx0bzptb2hhbWVkLmJvdWNhZGFpckBvcmFuZ2UuY29tPiB3cm90ZToNCg0KSGkgUGF1
bCwNCg0KVGhlIGN1cnJlbnQgdGV4dCBzdGF0ZXM6DQoNCuKAnA0KICAgTyBiaXQ6IEluZGljYXRl
cyB0aGF0IHRoaXMgcGFja2V0IGlzIGFuIG9wZXJhdGlvbnMgYW5kIG1hbmFnZW1lbnQNCiAgIChP
QU0pIHBhY2tldC4gIFNGRiBhbmQgU0ZzIG5vZGVzIE1VU1QgZXhhbWluZSB0aGUgcGF5bG9hZCBh
bmQgdGFrZQ0KICAgYXBwcm9wcmlhdGUgYWN0aW9uIChlLmcuIHJldHVybiBzdGF0dXMgaW5mb3Jt
YXRpb24pLg0KDQogICBPQU0gbWVzc2FnZSBzcGVjaWZpY3MgYW5kIGhhbmRsaW5nIGRldGFpbHMg
YXJlIG91dHNpZGUgdGhlIHNjb3BlIG9mDQogICB0aGlzIGRvY3VtZW50Lg0K4oCcDQoNCklzIHRo
ZXJlIGFueSBwYXJ0aWN1bGFyIHJlYXNvbiB3aHkgdGhpcyBpcyBkZWNsYXJlZCBvdXQgb2Ygc2Nv
cGU/DQoNClRoZSBzcGVjaWZpYyBvZiBhbiBPQU0gcHJvdG9jb2wgYXJlbuKAmXQgYmVpbmcgc3Bl
Y2lmaWVkIGluIE5TSCwgcmF0aGVyLCB0aGVyZSBhcmUgU0ZDIE9BTSBkcmFmdHMgdGhhdCB3aWxs
IGRlZmluZSB0aGUgcHJvdG9jb2xzIChzaW1pbGFyLCBJIGJlbGlldmUgdG8gd2hhdCBNUExTIGRp
ZCBhbmQgTlZPMyBpcyBkb2luZykuICBOU0ggc2ltcGx5IGRlZmluZXMgdGhhdCB3aGVuIE8tYml0
PTEsIHRoYXQgT0FNIGhhbmRsaW5nIG11c3Qgb2NjdXIsIGFzIHBlciB0aGUgdGV4dCBiZWxvdy4N
Cg0KDQpJZiB0aGUgY3VycmVudCBzY29wZSBpcyB0byBiZSBtYWludGFpbmVkLCB0aGVuIHlvdSBj
YW4gcmVtb3ZlIHRoaXMgc2VudGVuY2UgYXMgaXQgaXMgdXNlbGVzcyBzaW5jZSBhcHByb3ByaWF0
ZSBhY3Rpb25zIGFyZSBub3QgZGVmaW5lZCBpbiB0aGUgZG9jdW1lbnQuDQoNCuKAnFNGRiBhbmQg
U0ZzIG5vZGVzIE1VU1QgZXhhbWluZSB0aGUgcGF5bG9hZCBhbmQgdGFrZQ0KICAgYXBwcm9wcmlh
dGUgYWN0aW9uIChlLmcuIHJldHVybiBzdGF0dXMgaW5mb3JtYXRpb24pLuKAnQ0KDQpUaGFuayB5
b3UuDQoNCkNoZWVycywNCk1lZA0KDQo=

--_000_08825924F4224C85BEC08F71DD36427Dciscocom_
Content-Type: text/html; charset="utf-8"
Content-ID: <06CE5F2EAC8F6840927E4524341387E4@emea.cisco.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsiIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KPGRpdj4N
CjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj5PbiBGZWIg
MjUsIDIwMTUsIGF0IDEwOjUzIEFNLCA8YSBocmVmPSJtYWlsdG86bW9oYW1lZC5ib3VjYWRhaXJA
b3JhbmdlLmNvbSIgY2xhc3M9IiI+DQptb2hhbWVkLmJvdWNhZGFpckBvcmFuZ2UuY29tPC9hPiB3
cm90ZTo8L2Rpdj4NCjxiciBjbGFzcz0iQXBwbGUtaW50ZXJjaGFuZ2UtbmV3bGluZSI+DQo8ZGl2
IGNsYXNzPSIiPg0KPG1ldGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29y
ZCAxNCAoZmlsdGVyZWQgbWVkaXVtKSIgY2xhc3M9IiI+DQo8c3R5bGUgY2xhc3M9IiI+PCEtLQ0K
LyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDYWxpYnJp
Ow0KCXBhbm9zZS0xOjIgMTUgNSAyIDIgMiA0IDMgMiA0O30NCi8qIFN0eWxlIERlZmluaXRpb25z
ICovDQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjow
Y207DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1m
YW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgltc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1V
Uzt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsN
Cgljb2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBz
cGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xv
cjpwdXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwcmUNCgl7bXNvLXN0eWxl
LXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJQclwwMEU5Zm9ybWF0XDAwRTkgSFRNTCBD
YXIiOw0KCW1hcmdpbjowY207DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZTox
MC4wcHQ7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQpzcGFuLkVtYWlsU3R5bGUxNw0K
CXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1jb21wb3NlOw0KCWZvbnQtZmFtaWx5OiJDb3VyaWVy
IE5ldyI7DQoJY29sb3I6d2luZG93dGV4dDsNCglmb250LXdlaWdodDpub3JtYWw7DQoJZm9udC1z
dHlsZTpub3JtYWw7fQ0Kc3Bhbi5QcmZvcm1hdEhUTUxDYXINCgl7bXNvLXN0eWxlLW5hbWU6IlBy
XDAwRTlmb3JtYXRcMDBFOSBIVE1MIENhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1z
by1zdHlsZS1saW5rOiJQclwwMEU5Zm9ybWF0XDAwRTkgSFRNTCI7DQoJZm9udC1mYW1pbHk6IkNv
dXJpZXIgTmV3IjsNCgltc28tZmFyZWFzdC1sYW5ndWFnZTpGUjt9DQouTXNvQ2hwRGVmYXVsdA0K
CXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNh
bnMtc2VyaWYiOw0KCW1zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTO30NCkBwYWdlIFdvcmRTZWN0
aW9uMQ0KCXtzaXplOjYxMi4wcHQgNzkyLjBwdDsNCgltYXJnaW46NzAuODVwdCA3MC44NXB0IDcw
Ljg1cHQgNzAuODVwdDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30N
Ci0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6
ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBn
dGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2
OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0t
LT4NCjxkaXYgbGFuZz0iRlIiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiIGNsYXNzPSIiPg0K
PGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7
IiBjbGFzcz0iIj5IaSBQYXVsLDxvOnAgY2xhc3M9IiI+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7IiBjbGFzcz0iIj4mbmJzcDs8L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7IiBjbGFzcz0iIj5UaGUgY3Vy
cmVudCB0ZXh0IHN0YXRlczogJm5ic3A7PG86cCBjbGFzcz0iIj48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6
MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7IiBjbGFzcz0iIj4mbmJz
cDs8L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0
eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7
IiBjbGFzcz0iIj7igJw8bzpwIGNsYXNzPSIiPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RlIi
IGNsYXNzPSIiPiZuYnNwOyZuYnNwOyBPIGJpdDogSW5kaWNhdGVzIHRoYXQgdGhpcyBwYWNrZXQg
aXMgYW4gb3BlcmF0aW9ucyBhbmQgbWFuYWdlbWVudDxvOnAgY2xhc3M9IiI+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9u
dC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Ozttc28tZmFy
ZWFzdC1sYW5ndWFnZTpGUiIgY2xhc3M9IiI+Jm5ic3A7Jm5ic3A7IChPQU0pIHBhY2tldC4mbmJz
cDsgU0ZGIGFuZCBTRnMgbm9kZXMgTVVTVCBleGFtaW5lIHRoZSBwYXlsb2FkIGFuZCB0YWtlPG86
cCBjbGFzcz0iIj48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
bGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nv
dXJpZXIgTmV3JnF1b3Q7O21zby1mYXJlYXN0LWxhbmd1YWdlOkZSIiBjbGFzcz0iIj4mbmJzcDsm
bmJzcDsgYXBwcm9wcmlhdGUgYWN0aW9uIChlLmcuIHJldHVybiBzdGF0dXMgaW5mb3JtYXRpb24p
LjxvOnAgY2xhc3M9IiI+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVv
dDtDb3VyaWVyIE5ldyZxdW90Ozttc28tZmFyZWFzdC1sYW5ndWFnZTpGUiIgY2xhc3M9IiI+Jm5i
c3A7PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBz
dHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90
Ozttc28tZmFyZWFzdC1sYW5ndWFnZTpGUiIgY2xhc3M9IiI+Jm5ic3A7Jm5ic3A7IE9BTSBtZXNz
YWdlIHNwZWNpZmljcyBhbmQgaGFuZGxpbmcgZGV0YWlscyBhcmUgb3V0c2lkZSB0aGUgc2NvcGUg
b2Y8bzpwIGNsYXNzPSIiPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q291cmllciBOZXcmcXVvdDs7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RlIiIGNsYXNzPSIiPiZu
YnNwOyZuYnNwOw0KPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O21zby1mYXJlYXN0LWxhbmd1YWdlOkZSIiBjbGFz
cz0iIj50aGlzIGRvY3VtZW50LjxvOnAgY2xhc3M9IiI+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBw
dDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyIgY2xhc3M9IiI+4oCcPG86cCBj
bGFzcz0iIj48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFu
Zz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJp
ZXIgTmV3JnF1b3Q7IiBjbGFzcz0iIj4mbmJzcDs8L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7IiBjbGFzcz0iIj5JcyB0aGVyZSBhbnkgcGFydGlj
dWxhciByZWFzb24gd2h5IHRoaXMgaXMgZGVjbGFyZWQgb3V0IG9mIHNjb3BlPw0KPC9zcGFuPjwv
cD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+PGJyIGNsYXNz
PSIiPg0KPC9kaXY+DQo8ZGl2PlRoZSBzcGVjaWZpYyBvZiBhbiBPQU0gcHJvdG9jb2wgYXJlbuKA
mXQgYmVpbmcgc3BlY2lmaWVkIGluIE5TSCwgcmF0aGVyLCB0aGVyZSBhcmUgU0ZDIE9BTSBkcmFm
dHMgdGhhdCB3aWxsIGRlZmluZSB0aGUgcHJvdG9jb2xzIChzaW1pbGFyLCBJIGJlbGlldmUgdG8g
d2hhdCBNUExTIGRpZCBhbmQgTlZPMyBpcyBkb2luZykuICZuYnNwO05TSCBzaW1wbHkgZGVmaW5l
cyB0aGF0IHdoZW4gTy1iaXQ9MSwgdGhhdCBPQU0gaGFuZGxpbmcgbXVzdCBvY2N1ciwNCiBhcyBw
ZXIgdGhlIHRleHQgYmVsb3cuPC9kaXY+DQo8YnIgY2xhc3M9IiI+DQo8YmxvY2txdW90ZSB0eXBl
PSJjaXRlIiBjbGFzcz0iIj4NCjxkaXYgY2xhc3M9IiI+DQo8ZGl2IGxhbmc9IkZSIiBsaW5rPSJi
bHVlIiB2bGluaz0icHVycGxlIiBjbGFzcz0iIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6
ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDsiIGNsYXNzPSIiPjxv
OnAgY2xhc3M9IiI+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtD
b3VyaWVyIE5ldyZxdW90OyIgY2xhc3M9IiI+Jm5ic3A7PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250
LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyIgY2xhc3M9IiI+SWYgdGhlIGN1cnJlbnQg
c2NvcGUgaXMgdG8gYmUgbWFpbnRhaW5lZCwgdGhlbiB5b3UgY2FuIHJlbW92ZSB0aGlzIHNlbnRl
bmNlIGFzIGl0IGlzIHVzZWxlc3Mgc2luY2UgYXBwcm9wcmlhdGUgYWN0aW9ucyBhcmUgbm90IGRl
ZmluZWQgaW4gdGhlIGRvY3VtZW50LjxvOnAgY2xhc3M9IiI+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyIgY2xhc3M9IiI+Jm5ic3A7
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHls
ZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyIg
Y2xhc3M9IiI+4oCcPC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Ozttc28tZmFyZWFzdC1sYW5n
dWFnZTpGUiIgY2xhc3M9IiI+U0ZGIGFuZCBTRnMgbm9kZXMgTVVTVCBleGFtaW5lIHRoZSBwYXls
b2FkIGFuZA0KIHRha2U8bzpwIGNsYXNzPSIiPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RlIi
IGNsYXNzPSIiPiZuYnNwOyZuYnNwOyBhcHByb3ByaWF0ZSBhY3Rpb24gKGUuZy4gcmV0dXJuIHN0
YXR1cyBpbmZvcm1hdGlvbiku4oCdPG86cCBjbGFzcz0iIj48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7IiBjbGFzcz0iIj4mbmJzcDs8
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxl
PSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7IiBj
bGFzcz0iIj5UaGFuayB5b3UuPG86cCBjbGFzcz0iIj48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7IiBjbGFzcz0iIj4mbmJzcDs8L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJm
b250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7IiBjbGFz
cz0iIj5DaGVlcnMsPG86cCBjbGFzcz0iIj48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7IiBjbGFzcz0iIj5NZWQ8bzpwIGNsYXNzPSIi
PjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+
DQo8L2Rpdj4NCjxiciBjbGFzcz0iIj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_08825924F4224C85BEC08F71DD36427Dciscocom_--


From nobody Mon Mar  2 07:59:47 2015
Return-Path: <paulq@cisco.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D47F1A0089 for <sfc@ietfa.amsl.com>; Mon,  2 Mar 2015 07:59:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 ces1aoFz4JDO for <sfc@ietfa.amsl.com>; Mon,  2 Mar 2015 07:59:44 -0800 (PST)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C94721A0068 for <sfc@ietf.org>; Mon,  2 Mar 2015 07:59:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8128; q=dns/txt; s=iport; t=1425311984; x=1426521584; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=uQi72oZgikuI5pBugGh931clzqy3GQ/qdp57QUxdouE=; b=DMo0Pr3LRYEtvBVEj18NQm9PKv4iqW3gi/4jeeVJUeQI+J4+pryI1+kU dLhFt501jzWX77/1QKBYWGfHLxqOju4WVhQPRH01iJzoErUVIgyYD/fC5 lClohKDnmZTue64XRP21KmmmKNtnow57BgcsnFtoItquFxZIMFBYw2+Gz g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CEBQC+h/RU/49dJa1agj9DgTCDBsQpAhyBCE0BAQEBAQF8hBABAQQjCkwQAgEIEi0DAgICMBQDDgEBBA4FiC+8c5kEAQEBAQEBAQEBAQEBAQEBAQEBAQEBF4sShG4HgmgvgRQFjXuBfYlHgRqDII8gI4Nub4FEfwEBAQ
X-IronPort-AV: E=Sophos;i="5.09,676,1418083200";  d="scan'208,217";a="111109553"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by mtv-iport-1.cisco.com with ESMTP; 02 Mar 2015 15:59:44 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id t22FxiBr016190 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 2 Mar 2015 15:59:44 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.229]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.03.0195.001; Mon, 2 Mar 2015 09:59:43 -0600
From: "Paul Quinn (paulq)" <paulq@cisco.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Thread-Topic: draft-quinn-sfc-nsh: Relatnship with the SFC Architecture I-D
Thread-Index: AdBRDomOOT0eIim0Q9CLRef0gO0ktgEJaayA
Date: Mon, 2 Mar 2015 15:59:43 +0000
Message-ID: <FB009E84-2FC2-4109-992E-5AE1C497161C@cisco.com>
References: <787AE7BB302AE849A7480A190F8B933004914138@OPEXCLILM23.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B933004914138@OPEXCLILM23.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.17.229]
Content-Type: multipart/alternative; boundary="_000_FB009E842FC24109992E5AE1C497161Cciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/RntySK-aVpblFPOV_4rWG63Dp1Q>
Cc: "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] draft-quinn-sfc-nsh: Relatnship with the SFC Architecture I-D
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 02 Mar 2015 15:59:46 -0000

--_000_FB009E842FC24109992E5AE1C497161Cciscocom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

TWVkLA0KDQpUaGUgU0ZDIEFyY2hpdGVjdHVyZSBkcmFmdCBpcyByZWZlcmVuY2VkIGF0IHRoZSBi
ZWdpbm5pbmcsIGhvd2V2ZXIsIGl0IHNob3VsZCBwcm9iYWJseSBiZSBtb3ZlZCB0byBhIE5vcm1h
dGl2ZSByZWZlcmVuY2UgKHZzLiBJbmZvcm1hdGl2ZSkgdG8gYmUgbW9zdCBjb3JyZWN0LiAgSeKA
mW0gaGFwcHkgdG8gZG8gc28gd2hlbiBhcHByb3ByaWF0ZS4gICBPdGhlciB0aGFuIHRoYXQsIE5T
SCBpcyDigJxjb21wbGlhbnTigJ0gd2l0aCB0aGUgYXJjaGl0ZWN0dXJlLiAgSWYgeW91IGhhdmUg
c3BlY2lmaWMgYXJlYXMgeW914oCZZCBsaWtlIGhpZ2hsaWdodGVkLCBwbGVhc2UgZG8gc2VuZCBv
dXQgc29tZSB0ZXh0LCBJIGtub3cgbXkgY28tYXV0aG9ycyBhbmQgSSB3b3VsZCBiZSBoYXBweSB0
byByZXZpZXcuDQoNClBhdWwNCg0KT24gRmViIDI1LCAyMDE1LCBhdCAxMDoyMCBBTSwgbW9oYW1l
ZC5ib3VjYWRhaXJAb3JhbmdlLmNvbTxtYWlsdG86bW9oYW1lZC5ib3VjYWRhaXJAb3JhbmdlLmNv
bT4gd3JvdGU6DQoNCkhpIFBhdWwsDQoNClRoZSBjdXJyZW50IE5TSCBJLUQgY2l0ZXMgdGhlIFNG
QyBhcmNoaXRlY3R1cmUgZHJhZnQgb25jZS4gVGhpcyB3ZWFrIGFkaGVyZW5jZSB3aXRoIHRoZSBT
RkMgYXJjaGl0ZWN0dXJlIGlzIGFsYXJtaW5nIGdpdmVuIHRoYXQgdGhlIFdHIGhhZCBhIGxvdCBv
ZiBkaXNjdXNzaW9uIGFib3V0IHZhcmlvdXMgYXNwZWN0cyBvZiB0aGUgb3ZlcmFsbCBwcm9jZWR1
cmU6IGUuZy4sIGZ1bGx5IGRpc3RyaWJ1dGVkIGZvcndhcmRpbmcgcGF0aCwgZm9yY2UgdGhlIGZv
cndhcmRpbmcgcGF0aCwgYSBtaXggb2YgdGhvc2UsIGV0Yy4NCg0KSW5jbHVkaW5nIGEgZGVzY3Jp
cHRpb24gb2YgaG93IHRoZXNlIGFzcGVjdHMgYXJlIGZ1bGZpbGxlZCBpbiB0aGUgY3VycmVudCBO
U0ggc3BlY2lmaWNhdGlvbiB3b3VsZCBhdm9pZCBoYXZpbmcgdGhlIHNhbWUgZGlzY3Vzc2lvbiB3
ZSBoYWQgaW4gdGhlIGxpc3QuDQoNClRoYW5rIHlvdS4NCg0KQ2hlZXJzLA0KTWVkDQoNCg0KDQoN
Cg==

--_000_FB009E842FC24109992E5AE1C497161Cciscocom_
Content-Type: text/html; charset="utf-8"
Content-ID: <A38C8558125E2047B7E223537A4EE493@emea.cisco.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsiIGNsYXNzPSIiPg0KTWVkLA0KPGRpdiBjbGFzcz0iIj48
YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+VGhlIFNGQyBBcmNoaXRlY3R1cmUg
ZHJhZnQgaXMgcmVmZXJlbmNlZCBhdCB0aGUgYmVnaW5uaW5nLCBob3dldmVyLCBpdCBzaG91bGQg
cHJvYmFibHkgYmUgbW92ZWQgdG8gYSBOb3JtYXRpdmUgcmVmZXJlbmNlICh2cy4gSW5mb3JtYXRp
dmUpIHRvIGJlIG1vc3QgY29ycmVjdC4gJm5ic3A7SeKAmW0gaGFwcHkgdG8gZG8gc28gd2hlbiBh
cHByb3ByaWF0ZS4gJm5ic3A7IE90aGVyIHRoYW4gdGhhdCwgTlNIIGlzIOKAnGNvbXBsaWFudOKA
nSB3aXRoIHRoZQ0KIGFyY2hpdGVjdHVyZS4gJm5ic3A7SWYgeW91IGhhdmUgc3BlY2lmaWMgYXJl
YXMgeW914oCZZCBsaWtlIGhpZ2hsaWdodGVkLCBwbGVhc2UgZG8gc2VuZCBvdXQgc29tZSB0ZXh0
LCBJIGtub3cgbXkgY28tYXV0aG9ycyBhbmQgSSB3b3VsZCBiZSBoYXBweSB0byByZXZpZXcuPC9k
aXY+DQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj5Q
YXVsPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFzcz0iIj4NCjxkaXY+DQo8YmxvY2txdW90
ZSB0eXBlPSJjaXRlIiBjbGFzcz0iIj4NCjxkaXYgY2xhc3M9IiI+T24gRmViIDI1LCAyMDE1LCBh
dCAxMDoyMCBBTSwgPGEgaHJlZj0ibWFpbHRvOm1vaGFtZWQuYm91Y2FkYWlyQG9yYW5nZS5jb20i
IGNsYXNzPSIiPg0KbW9oYW1lZC5ib3VjYWRhaXJAb3JhbmdlLmNvbTwvYT4gd3JvdGU6PC9kaXY+
DQo8YnIgY2xhc3M9IkFwcGxlLWludGVyY2hhbmdlLW5ld2xpbmUiPg0KPGRpdiBjbGFzcz0iIj4N
CjxtZXRhIG5hbWU9IkdlbmVyYXRvciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRl
cmVkIG1lZGl1bSkiIGNsYXNzPSIiPg0KPHN0eWxlIGNsYXNzPSIiPjwhLS0NCi8qIEZvbnQgRGVm
aW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2Ut
MToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29O
b3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdp
bi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxp
YnJpIiwic2Fucy1zZXJpZiI7DQoJbXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVM7fQ0KYTpsaW5r
LCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1
ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBl
cmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0K
CXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTcNCgl7bXNvLXN0
eWxlLXR5cGU6cGVyc29uYWwtY29tcG9zZTsNCglmb250LWZhbWlseToiQ291cmllciBOZXciOw0K
CWNvbG9yOndpbmRvd3RleHQ7DQoJZm9udC13ZWlnaHQ6bm9ybWFsOw0KCWZvbnQtc3R5bGU6bm9y
bWFsO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZv
bnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJbXNvLWZhcmVhc3QtbGFuZ3VhZ2U6
RU4tVVM7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3OTIuMHB0Ow0KCW1h
cmdpbjo3MC44NXB0IDcwLjg1cHQgNzAuODVwdCA3MC44NXB0O30NCmRpdi5Xb3JkU2VjdGlvbjEN
Cgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHht
bD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3ht
bD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6
ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBl
bGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPGRpdiBsYW5nPSJGUiIgbGluaz0iYmx1ZSIgdmxp
bms9InB1cnBsZSIgY2xhc3M9IiI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q291cmllciBOZXcmcXVvdDsiIGNsYXNzPSIiPkhpIFBhdWwsPG86cCBjbGFzcz0iIj48
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDsiIGNsYXNzPSIi
PiZuYnNwOzwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1V
UyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcm
cXVvdDsiIGNsYXNzPSIiPlRoZSBjdXJyZW50IE5TSCBJLUQgY2l0ZXMgdGhlIFNGQyBhcmNoaXRl
Y3R1cmUgZHJhZnQgb25jZS4gVGhpcyB3ZWFrIGFkaGVyZW5jZSB3aXRoIHRoZSBTRkMgYXJjaGl0
ZWN0dXJlIGlzIGFsYXJtaW5nIGdpdmVuIHRoYXQgdGhlIFdHIGhhZCBhIGxvdCBvZiBkaXNjdXNz
aW9uDQogYWJvdXQgdmFyaW91cyBhc3BlY3RzIG9mIHRoZSBvdmVyYWxsIHByb2NlZHVyZTogZS5n
LiwgZnVsbHkgZGlzdHJpYnV0ZWQgZm9yd2FyZGluZyBwYXRoLCBmb3JjZSB0aGUgZm9yd2FyZGlu
ZyBwYXRoLCBhIG1peCBvZiB0aG9zZSwgZXRjLg0KPG86cCBjbGFzcz0iIj48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250
LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7IiBjbGFzcz0i
Ij4mbmJzcDs8L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3
JnF1b3Q7IiBjbGFzcz0iIj5JbmNsdWRpbmcgYSBkZXNjcmlwdGlvbiBvZiBob3cgdGhlc2UgYXNw
ZWN0cyBhcmUgZnVsZmlsbGVkIGluIHRoZSBjdXJyZW50IE5TSCBzcGVjaWZpY2F0aW9uIHdvdWxk
IGF2b2lkIGhhdmluZyB0aGUgc2FtZSBkaXNjdXNzaW9uIHdlIGhhZCBpbiB0aGUgbGlzdC48bzpw
IGNsYXNzPSIiPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBs
YW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291
cmllciBOZXcmcXVvdDsiIGNsYXNzPSIiPiZuYnNwOzwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDsiIGNsYXNzPSIiPlRoYW5rIHlvdS48bzpwIGNs
YXNzPSIiPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5n
PSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmll
ciBOZXcmcXVvdDsiIGNsYXNzPSIiPiZuYnNwOzwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDsiIGNsYXNzPSIiPkNoZWVycyw8bzpwIGNsYXNzPSIi
PjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1V
UyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcm
cXVvdDsiIGNsYXNzPSIiPk1lZDxvOnAgY2xhc3M9IiI+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBw
dDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyIgY2xhc3M9IiI+Jm5ic3A7PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0i
Zm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyIgY2xh
c3M9IiI+Jm5ic3A7PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9
IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVy
IE5ldyZxdW90OyIgY2xhc3M9IiI+Jm5ic3A7PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8
L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8L2Jv
ZHk+DQo8L2h0bWw+DQo=

--_000_FB009E842FC24109992E5AE1C497161Cciscocom_--


From nobody Mon Mar  2 08:15:34 2015
Return-Path: <walter.haeffner@vodafone.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31DD51A0115 for <sfc@ietfa.amsl.com>; Mon,  2 Mar 2015 08:15:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.199
X-Spam-Level: 
X-Spam-Status: No, score=-3.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001] autolearn=ham
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 cGnz2VJd84ZN for <sfc@ietfa.amsl.com>; Mon,  2 Mar 2015 08:15:29 -0800 (PST)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.112]) by ietfa.amsl.com (Postfix) with ESMTP id BA70A1A0067 for <sfc@ietf.org>; Mon,  2 Mar 2015 08:15:28 -0800 (PST)
Received: from [193.109.255.99] by server-8.bemta-14.messagelabs.com id 86/38-03168-F9C84F45; Mon, 02 Mar 2015 16:15:27 +0000
X-Env-Sender: walter.haeffner@vodafone.com
X-Msg-Ref: server-12.tower-48.messagelabs.com!1425312922!8493257!6
X-Originating-IP: [195.232.224.73]
X-StarScan-Received: 
X-StarScan-Version: 6.13.4; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 31839 invoked from network); 2 Mar 2015 16:15:26 -0000
Received: from mailout04.vodafone.com (HELO mailout04.vodafone.com) (195.232.224.73) by server-12.tower-48.messagelabs.com with SMTP; 2 Mar 2015 16:15:26 -0000
Received: from mailint04.vodafone.com (localhost [127.0.0.1]) by mailout04.vodafone.com (Postfix) with ESMTP id 9F349800FC for <sfc@ietf.org>; Mon,  2 Mar 2015 17:15:26 +0100 (CET)
Received: from VOEXC02W.internal.vodafone.com (voexc02w.dc-ratingen.de [145.230.101.22]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailint04.vodafone.com (Postfix) with ESMTPS id 89342800C2; Mon,  2 Mar 2015 17:15:26 +0100 (CET)
Received: from VOEXM20W.internal.vodafone.com ([169.254.4.55]) by VOEXC02W.internal.vodafone.com ([145.230.101.22]) with mapi id 14.03.0224.002; Mon, 2 Mar 2015 17:15:25 +0100
From: "Haeffner, Walter, Vodafone DE" <walter.haeffner@vodafone.com>
To: "Paul Quinn (paulq)" <paulq@cisco.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Thread-Topic: [sfc] draft-quinn-sfc-nsh: relatniship with the use cases drafts
Thread-Index: AdBRDaI7xfMTZEmzRd6IIps3ZiTmogEICK4AAAwm2PA=
Date: Mon, 2 Mar 2015 16:15:25 +0000
Message-ID: <C8C844F84E550E43865561FAE10471854C5F0C8B@VOEXM20W.internal.vodafone.com>
References: <787AE7BB302AE849A7480A190F8B9330049140FD@OPEXCLILM23.corporate.adroot.infra.ftgroup> <CA29E3DA-324E-4FA3-AC0B-4148E46999D5@cisco.com>
In-Reply-To: <CA29E3DA-324E-4FA3-AC0B-4148E46999D5@cisco.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_C8C844F84E550E43865561FAE10471854C5F0C8BVOEXM20Winterna_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/Mvg0KqrJbYE_N5XVNQpVfMTPEZ4>
Cc: "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] draft-quinn-sfc-nsh: relatniship with the use cases drafts
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 02 Mar 2015 16:15:33 -0000

--_000_C8C844F84E550E43865561FAE10471854C5F0C8BVOEXM20Winterna_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgUGF1bCwgTWVkLA0KDQpJbiB0aGUgbW9iaWxlIHVzZSBjYXNlIGRyYWZ0IHdlIG1lbnRpb25l
ZCB1c2FnZSBhbmQgaW1wYWN0IG9mIG1ldGFkYXRhIG9uIFNGQy4gV2UgYWxzbyBtZW50aW9uZWQg
dGhhdCBhIE5TSCBtYXkgYmUgYXBwcm9wcmlhdGUuIEJlY2F1c2UgYXQgdGltZSBvZiB3cml0aW5n
IE5TSCB3YXMgbm90IChhbmQgaXMgbm90IGJ5IHRvZGF5KSBpbXBsZW1lbnRlZCBpbiBTRnMsIHdl
IGNvdWxkbuKAmXQgZ2l2ZSBhbiBleHBsaWNpdCBleGFtcGxlLiBBbmQgd2Ugd2VyZSBhc2tlZCBu
b3QgdG8gaW5jbHVkZSByZXF1aXJlbWVudHMgaW4gdGhlIGRyYWZ0Lg0KDQpXYWx0ZXINClZvbjog
c2ZjIFttYWlsdG86c2ZjLWJvdW5jZXNAaWV0Zi5vcmddIEltIEF1ZnRyYWcgdm9uIFBhdWwgUXVp
bm4gKHBhdWxxKQ0KR2VzZW5kZXQ6IE1vbnRhZywgMi4gTcOkcnogMjAxNSAxNjoxNA0KQW46IG1v
aGFtZWQuYm91Y2FkYWlyQG9yYW5nZS5jb20NCkNjOiBzZmNAaWV0Zi5vcmcNCkJldHJlZmY6IFJl
OiBbc2ZjXSBkcmFmdC1xdWlubi1zZmMtbnNoOiByZWxhdG5pc2hpcCB3aXRoIHRoZSB1c2UgY2Fz
ZXMgZHJhZnRzDQoNCkhpIE1lZCwNCg0KDQpBcmUgeW91IHN1Z2dlc3RpbmcgdGhhdCB0aGUgdXNl
IGNhc2VzIGJlIGluY2x1ZGVkIGFzIHJlZmVyZW5jZXMsIG9yIGV4cGxpY2l0IHJlZmVyZW5jZWQ/
ICBQZXJoYXBzIGEgbG9naWNhbCBwYXRoIGZvcndhcmQsIGlmIE5TSCBpcyBhZG9wdGVkLCB0aGF0
IHBlcmhhcHMgdGhlIHVzZSBjYXNlcyBjYW4gYmUgdXBkYXRlZCB0byByZWZsZWN0IHRoZSDigJxT
RkMgZW5jYXDigJ0uDQoNClBhdWwNCg0KDQpPbiBGZWIgMjUsIDIwMTUsIGF0IDEwOjEzIEFNLCBt
b2hhbWVkLmJvdWNhZGFpckBvcmFuZ2UuY29tPG1haWx0bzptb2hhbWVkLmJvdWNhZGFpckBvcmFu
Z2UuY29tPiB3cm90ZToNCg0KUmUtLA0KDQpJdCBpcyB1bmZvcnR1bmF0ZSB0aGUgY3VycmVudCBO
U0ggc3BlY2lmaWNhdGlvbiBkb2VzIG5vdCByZWx5IG9uIHRoZSBTRkMgdXNlIGNhc2VzIGFzIGRv
Y3VtZW50ZWQgYnkgdGhlIFdHLg0KDQpEb2VzIHRoaXMgbWVhbiB0aGF0IHRob3NlIGFyZSB1c2Vs
ZXNzPyBUaGF0IG5vIChjb21tb24pIHJlcXVpcmVtZW50cyBjYW4gYmUgZGVyaXZlZCBmcm9tIHRo
b3NlIEktRHMgdG8gZ3VpZGUgdGhlIHNwZWNpZmljYXRpb24gb2YgdGhlIE5TSCBoZWFkZXI/DQoN
CkNoZWVycywNCk1lZA0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX18NCnNmYyBtYWlsaW5nIGxpc3QNCnNmY0BpZXRmLm9yZzxtYWlsdG86c2ZjQGlldGYub3Jn
Pg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9zZmMNCg0K

--_000_C8C844F84E550E43865561FAE10471854C5F0C8BVOEXM20Winterna_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
V2luZ2RpbmdzOw0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseTpCYXRhbmc7DQoJcGFub3NlLTE6MiAzIDYgMCAwIDEgMSAxIDEgMTt9DQpA
Zm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkJhdGFuZzsNCglwYW5vc2UtMToyIDMgNiAwIDAgMSAx
IDEgMSAxO30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToy
IDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OlRhaG9tYTsN
CglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFt
aWx5OiJcQEJhdGFuZyI7DQoJcGFub3NlLTE6MiAzIDYgMCAwIDEgMSAxIDEgMTt9DQovKiBTdHls
ZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1h
bA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEu
MHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7fQ0KYTpsaW5rLCBzcGFu
Lk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0
ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtG
b2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQt
ZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcC5Nc29MaXN0UGFyYWdyYXBoLCBsaS5Nc29MaXN0UGFy
YWdyYXBoLCBkaXYuTXNvTGlzdFBhcmFncmFwaA0KCXttc28tc3R5bGUtcHJpb3JpdHk6MzQ7DQoJ
bWFyZ2luLXRvcDowY207DQoJbWFyZ2luLXJpZ2h0OjBjbTsNCgltYXJnaW4tYm90dG9tOjEyLjBw
dDsNCgltYXJnaW4tbGVmdDozNi4wcHQ7DQoJbXNvLWFkZC1zcGFjZTphdXRvOw0KCWZvbnQtc2l6
ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQpwLk1zb0xpc3RQYXJhZ3Jh
cGhDeFNwRmlyc3QsIGxpLk1zb0xpc3RQYXJhZ3JhcGhDeFNwRmlyc3QsIGRpdi5Nc29MaXN0UGFy
YWdyYXBoQ3hTcEZpcnN0DQoJe21zby1zdHlsZS1wcmlvcml0eTozNDsNCgltc28tc3R5bGUtdHlw
ZTpleHBvcnQtb25seTsNCgltYXJnaW4tdG9wOjBjbTsNCgltYXJnaW4tcmlnaHQ6MGNtOw0KCW1h
cmdpbi1ib3R0b206MGNtOw0KCW1hcmdpbi1sZWZ0OjM2LjBwdDsNCgltYXJnaW4tYm90dG9tOi4w
MDAxcHQ7DQoJbXNvLWFkZC1zcGFjZTphdXRvOw0KCWZvbnQtc2l6ZToxMi4wcHQ7DQoJZm9udC1m
YW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQpwLk1zb0xpc3RQYXJhZ3JhcGhDeFNwTWlkZGxlLCBsaS5N
c29MaXN0UGFyYWdyYXBoQ3hTcE1pZGRsZSwgZGl2Lk1zb0xpc3RQYXJhZ3JhcGhDeFNwTWlkZGxl
DQoJe21zby1zdHlsZS1wcmlvcml0eTozNDsNCgltc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsN
CgltYXJnaW4tdG9wOjBjbTsNCgltYXJnaW4tcmlnaHQ6MGNtOw0KCW1hcmdpbi1ib3R0b206MGNt
Ow0KCW1hcmdpbi1sZWZ0OjM2LjBwdDsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJbXNvLWFk
ZC1zcGFjZTphdXRvOw0KCWZvbnQtc2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIg
TmV3Ijt9DQpwLk1zb0xpc3RQYXJhZ3JhcGhDeFNwTGFzdCwgbGkuTXNvTGlzdFBhcmFncmFwaEN4
U3BMYXN0LCBkaXYuTXNvTGlzdFBhcmFncmFwaEN4U3BMYXN0DQoJe21zby1zdHlsZS1wcmlvcml0
eTozNDsNCgltc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCgltYXJnaW4tdG9wOjBjbTsNCglt
YXJnaW4tcmlnaHQ6MGNtOw0KCW1hcmdpbi1ib3R0b206MTIuMHB0Ow0KCW1hcmdpbi1sZWZ0OjM2
LjBwdDsNCgltc28tYWRkLXNwYWNlOmF1dG87DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZh
bWlseToiQ291cmllciBOZXciO30NCnNwYW4uRS1NYWlsRm9ybWF0dm9ybGFnZTE3DQoJe21zby1z
dHlsZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7DQoJY29sb3I6
d2luZG93dGV4dDsNCglmb250LXdlaWdodDpub3JtYWw7DQoJZm9udC1zdHlsZTpub3JtYWw7fQ0K
c3Bhbi5FLU1haWxGb3JtYXR2b3JsYWdlMTgNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVw
bHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjojMUY0OTdE
O30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQt
c2l6ZToxMC4wcHQ7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3OTIuMHB0
Ow0KCW1hcmdpbjo3MC44NXB0IDcwLjg1cHQgNzAuODVwdCA3MC44NXB0O30NCmRpdi5Xb3JkU2Vj
dGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLyogTGlzdCBEZWZpbml0aW9ucyAqLw0KQGxp
c3QgbDANCgl7bXNvLWxpc3QtaWQ6MTgxNzE0NTA0NjsNCgltc28tbGlzdC10eXBlOmh5YnJpZDsN
Cgltc28tbGlzdC10ZW1wbGF0ZS1pZHM6MjA3ODE4MzMwOCA2NzY5ODY4OSA2NzY5ODY4OSA2NzY5
ODY5MyA2NzY5ODY4OSA2NzY5ODY5MSA2NzY5ODY5MyA2NzY5ODY4OSA2NzY5ODY5MSA2NzY5ODY5
Mzt9DQpAbGlzdCBsMDpsZXZlbDENCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0K
CW1zby1sZXZlbC10ZXh0Ou+CtzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2
ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJbWFyZ2luLWxlZnQ6NTcuNnB0Ow0KCXRleHQtaW5k
ZW50Oi0xOC4wcHQ7DQoJZm9udC1mYW1pbHk6U3ltYm9sO30NCkBsaXN0IGwwOmxldmVsMg0KCXtt
c28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674K3Ow0KCW1z
by1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsN
CgltYXJnaW4tbGVmdDo5My42cHQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCglmb250LWZhbWls
eTpTeW1ib2w7fQ0KQGxpc3QgbDA6bGV2ZWwzDQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1
bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJ
bXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCW1hcmdpbi1sZWZ0OjEyOS42cHQ7DQoJ
dGV4dC1pbmRlbnQ6LTE4LjBwdDsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0KQGxpc3QgbDA6
bGV2ZWw0DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4
dDrvgrc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3Np
dGlvbjpsZWZ0Ow0KCW1hcmdpbi1sZWZ0OjE2NS42cHQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsN
Cglmb250LWZhbWlseTpTeW1ib2w7fQ0KQGxpc3QgbDA6bGV2ZWw1DQoJe21zby1sZXZlbC1udW1i
ZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDpvOw0KCW1zby1sZXZlbC10YWItc3Rv
cDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgltYXJnaW4tbGVmdDoy
MDEuNnB0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3
Ijt9DQpAbGlzdCBsMDpsZXZlbDYNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0K
CW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2
ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJbWFyZ2luLWxlZnQ6MjM3LjZwdDsNCgl0ZXh0LWlu
ZGVudDotMTguMHB0Ow0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9DQpAbGlzdCBsMDpsZXZlbDcN
Cgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CtzsN
Cgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxl
ZnQ7DQoJbWFyZ2luLWxlZnQ6MjczLjZwdDsNCgl0ZXh0LWluZGVudDotMTguMHB0Ow0KCWZvbnQt
ZmFtaWx5OlN5bWJvbDt9DQpAbGlzdCBsMDpsZXZlbDgNCgl7bXNvLWxldmVsLW51bWJlci1mb3Jt
YXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Om87DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7
DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCW1hcmdpbi1sZWZ0OjMwOS42cHQ7
DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCglmb250LWZhbWlseToiQ291cmllciBOZXciO30NCkBs
aXN0IGwwOmxldmVsOQ0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxl
dmVsLXRleHQ674KnOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1i
ZXItcG9zaXRpb246bGVmdDsNCgltYXJnaW4tbGVmdDozNDUuNnB0Ow0KCXRleHQtaW5kZW50Oi0x
OC4wcHQ7DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzO30NCkBsaXN0IGwxDQoJe21zby1saXN0LWlk
OjE4MjQyMDEyMzA7DQoJbXNvLWxpc3QtdHlwZTpoeWJyaWQ7DQoJbXNvLWxpc3QtdGVtcGxhdGUt
aWRzOi0xOTk4MTc0MDYwIDY3Njk4NjkxIDY3Njk4NjkxIDY3Njk4NjkzIDY3Njk4Njg5IDY3Njk4
NjkxIDY3Njk4NjkzIDY3Njk4Njg5IDY3Njk4NjkxIDY3Njk4NjkzO30NCkBsaXN0IGwxOmxldmVs
MQ0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6bzsN
Cgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxl
ZnQ7DQoJbWFyZ2luLWxlZnQ6MzkuNnB0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJZm9udC1m
YW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQpAbGlzdCBsMTpsZXZlbDINCgl7bXNvLWxldmVsLW51bWJl
ci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Om87DQoJbXNvLWxldmVsLXRhYi1zdG9w
Om5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCW1hcmdpbi1sZWZ0Ojc1
LjZwdDsNCgl0ZXh0LWluZGVudDotMTguMHB0Ow0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7
fQ0KQGxpc3QgbDE6bGV2ZWwzDQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCglt
c28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVs
LW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCW1hcmdpbi1sZWZ0OjExMS42cHQ7DQoJdGV4dC1pbmRl
bnQ6LTE4LjBwdDsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0KQGxpc3QgbDE6bGV2ZWw0DQoJ
e21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgrc7DQoJ
bXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0
Ow0KCW1hcmdpbi1sZWZ0OjE0Ny42cHQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCglmb250LWZh
bWlseTpTeW1ib2w7fQ0KQGxpc3QgbDE6bGV2ZWw1DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0
OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDpvOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0K
CW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgltYXJnaW4tbGVmdDoxODMuNnB0Ow0K
CXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQpAbGlz
dCBsMTpsZXZlbDYNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZl
bC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVy
LXBvc2l0aW9uOmxlZnQ7DQoJbWFyZ2luLWxlZnQ6MjE5LjZwdDsNCgl0ZXh0LWluZGVudDotMTgu
MHB0Ow0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9DQpAbGlzdCBsMTpsZXZlbDcNCgl7bXNvLWxl
dmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CtzsNCgltc28tbGV2
ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJbWFy
Z2luLWxlZnQ6MjU1LjZwdDsNCgl0ZXh0LWluZGVudDotMTguMHB0Ow0KCWZvbnQtZmFtaWx5OlN5
bWJvbDt9DQpAbGlzdCBsMTpsZXZlbDgNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0
Ow0KCW1zby1sZXZlbC10ZXh0Om87DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxl
dmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCW1hcmdpbi1sZWZ0OjI5MS42cHQ7DQoJdGV4dC1p
bmRlbnQ6LTE4LjBwdDsNCglmb250LWZhbWlseToiQ291cmllciBOZXciO30NCkBsaXN0IGwxOmxl
dmVsOQ0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6
74KnOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRp
b246bGVmdDsNCgltYXJnaW4tbGVmdDozMjcuNnB0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJ
Zm9udC1mYW1pbHk6V2luZ2RpbmdzO30NCm9sDQoJe21hcmdpbi1ib3R0b206MGNtO30NCnVsDQoJ
e21hcmdpbi1ib3R0b206MGNtO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+
DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+
PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4
dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxh
eW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5r
PSJibHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+SGkgUGF1bCwgTWVk
LDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+SW4gdGhlIG1vYmlsZSB1c2Ug
Y2FzZSBkcmFmdCB3ZSBtZW50aW9uZWQgdXNhZ2UgYW5kIGltcGFjdCBvZiBtZXRhZGF0YSBvbiBT
RkMuIFdlIGFsc28gbWVudGlvbmVkIHRoYXQgYSBOU0ggbWF5IGJlIGFwcHJvcHJpYXRlLiBCZWNh
dXNlIGF0IHRpbWUgb2Ygd3JpdGluZyBOU0ggd2FzIG5vdCAoYW5kIGlzIG5vdCBieSB0b2RheSkg
aW1wbGVtZW50ZWQgaW4gU0ZzLA0KIHdlIGNvdWxkbuKAmXQgZ2l2ZSBhbiBleHBsaWNpdCBleGFt
cGxlLiBBbmQgd2Ugd2VyZSBhc2tlZCBub3QgdG8gaW5jbHVkZSByZXF1aXJlbWVudHMgaW4gdGhl
IGRyYWZ0LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+V2FsdGVyPG86cD48
L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10
b3A6c29saWQgI0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBjbSAwY20gMGNtIj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIGxhbmc9IkRFIiBzdHlsZT0iZm9udC1zaXplOjEwLjBw
dDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+
Vm9uOjwvc3Bhbj48L2I+PHNwYW4gbGFuZz0iREUiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4gc2Zj
IFttYWlsdG86c2ZjLWJvdW5jZXNAaWV0Zi5vcmddDQo8Yj5JbSBBdWZ0cmFnIHZvbiA8L2I+UGF1
bCBRdWlubiAocGF1bHEpPGJyPg0KPGI+R2VzZW5kZXQ6PC9iPiBNb250YWcsIDIuIDwvc3Bhbj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVv
dDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+TcOkcnogMjAxNSAxNjoxNDxicj4NCjxiPkFuOjwv
Yj4gbW9oYW1lZC5ib3U8L3NwYW4+PHNwYW4gbGFuZz0iREUiIHN0eWxlPSJmb250LXNpemU6MTAu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7
Ij5jYWRhaXJAb3JhbmdlLmNvbTxicj4NCjxiPkNjOjwvYj4gc2ZjQGlldGYub3JnPGJyPg0KPGI+
QmV0cmVmZjo8L2I+IFJlOiBbc2ZjXSBkcmFmdC1xdWlubi1zZmMtbnNoOiByZWxhdG5pc2hpcCB3
aXRoIHRoZSB1c2UgY2FzZXMgZHJhZnRzPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8
L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPkhpIE1lZCw8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5BcmUgeW91IHN1Z2dlc3RpbmcgdGhhdCB0aGUg
dXNlIGNhc2VzIGJlIGluY2x1ZGVkIGFzIHJlZmVyZW5jZXMsIG9yIGV4cGxpY2l0IHJlZmVyZW5j
ZWQ/ICZuYnNwO1BlcmhhcHMgYSBsb2dpY2FsIHBhdGggZm9yd2FyZCwgaWYgTlNIIGlzIGFkb3B0
ZWQsIHRoYXQgcGVyaGFwcyB0aGUgdXNlIGNhc2VzIGNhbiBiZSB1cGRhdGVkIHRvIHJlZmxlY3Qg
dGhlIOKAnFNGQyBlbmNhcOKAnS48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+UGF1bDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxibG9ja3F1b3RlIHN0
eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPk9uIEZlYiAyNSwgMjAxNSwgYXQgMTA6MTMgQU0sIDxhIGhyZWY9Im1h
aWx0bzptb2hhbWVkLmJvdWNhZGFpckBvcmFuZ2UuY29tIj4NCm1vaGFtZWQuYm91Y2FkYWlyQG9y
YW5nZS5jb208L2E+IHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gbGFuZz0iRlIiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7Ij5SZS0sPC9zcGFuPjxzcGFuIGxhbmc9IkZSIj48
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJG
UiIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcm
cXVvdDsiPiZuYnNwOzwvc3Bhbj48c3BhbiBsYW5nPSJGUiI+PG86cD48L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDsiPkl0IGlzIHVuZm9ydHVuYXRlIHRoZSBj
dXJyZW50IE5TSCBzcGVjaWZpY2F0aW9uIGRvZXMgbm90IHJlbHkgb24gdGhlIFNGQyB1c2UgY2Fz
ZXMgYXMgZG9jdW1lbnRlZCBieSB0aGUgV0cuDQo8L3NwYW4+PHNwYW4gbGFuZz0iRlIiPjxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7Ij4mbmJzcDs8
L3NwYW4+PHNwYW4gbGFuZz0iRlIiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NvdXJpZXIgTmV3JnF1b3Q7Ij5Eb2VzIHRoaXMgbWVhbiB0aGF0IHRob3NlIGFyZSB1c2VsZXNz
PyBUaGF0IG5vIChjb21tb24pIHJlcXVpcmVtZW50cyBjYW4gYmUgZGVyaXZlZCBmcm9tIHRob3Nl
IEktRHMgdG8gZ3VpZGUgdGhlIHNwZWNpZmljYXRpb24gb2YgdGhlIE5TSCBoZWFkZXI/DQo8L3Nw
YW4+PHNwYW4gbGFuZz0iRlIiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nv
dXJpZXIgTmV3JnF1b3Q7Ij4mbmJzcDs8L3NwYW4+PHNwYW4gbGFuZz0iRlIiPjxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7Ij5DaGVlcnMsPC9zcGFu
PjxzcGFuIGxhbmc9IkZSIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3Vy
aWVyIE5ldyZxdW90OyI+TWVkDQo8L3NwYW4+PHNwYW4gbGFuZz0iRlIiPjxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7LCZxdW90
O3NlcmlmJnF1b3Q7Ij5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fXzxicj4NCnNmYyBtYWlsaW5nIGxpc3Q8YnI+DQo8YSBocmVmPSJtYWlsdG86c2ZjQGlldGYu
b3JnIj5zZmNAaWV0Zi5vcmc8L2E+PGJyPg0KPGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcv
bWFpbG1hbi9saXN0aW5mby9zZmMiPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGlu
Zm8vc2ZjPC9hPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0K
PC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBw
dDtmb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDssJnF1b3Q7c2VyaWYmcXVv
dDsiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1s
Pg0K

--_000_C8C844F84E550E43865561FAE10471854C5F0C8BVOEXM20Winterna_--


From nobody Mon Mar  2 09:50:59 2015
Return-Path: <paulq@cisco.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED7001A883A for <sfc@ietfa.amsl.com>; Mon,  2 Mar 2015 09:50:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 xSicyaR1JzVD for <sfc@ietfa.amsl.com>; Mon,  2 Mar 2015 09:50:56 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5FD091A8855 for <sfc@ietf.org>; Mon,  2 Mar 2015 09:50:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8105; q=dns/txt; s=iport; t=1425318656; x=1426528256; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=T5nF02/+q+fp3/y15ajqxE9zIWH0ccWNw23Z5nRR8dI=; b=k41i+o09p7GkXA1ZDsZsWpmOXjLnqXIl66WiP7uRTX06WLXUP+lTU2Z5 wbHNJYBt3gIbnMZdjygG89A7cnTa1VVOhz+h95EZTWb3TnEGbTad2Lils ccCbvlqzmitCbQuTB+THQIqKLsR/QKbj5Lrc0Yl/dgHQyCK5p4wPArMDs E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AjBQBzovRU/5BdJa1agwJSXsE1CoVwAoEkTQEBAQEBAXyEDwEBAQMBAQEBawsFCwIBCBgnBycLFBEBAQQOBYgnCA3WOQEBAQEBAQEBAQEBAQEBAQEBAQEBARMEixKELA8zB4MXgRQFj3iEKoUdgRqSQCOCAhyBUG+BAgIEGiJ/AQEB
X-IronPort-AV: E=Sophos;i="5.09,676,1418083200"; d="scan'208";a="400608594"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-2.cisco.com with ESMTP; 02 Mar 2015 17:50:55 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id t22Hosnc027633 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 2 Mar 2015 17:50:54 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.229]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.03.0195.001; Mon, 2 Mar 2015 11:50:54 -0600
From: "Paul Quinn (paulq)" <paulq@cisco.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Thread-Topic: [sfc] draft-quinn-sfc-nsh: version number
Thread-Index: AdBRDDloSX0/55xiS1KsQav7+px1wQAMyamAACHBoQAADvQcAADQYBIA
Date: Mon, 2 Mar 2015 17:50:53 +0000
Message-ID: <55A3CDAE-9D74-4174-AC1B-D3F500FABDCE@cisco.com>
References: <787AE7BB302AE849A7480A190F8B9330049140B4@OPEXCLILM23.corporate.adroot.infra.ftgroup> <54EDE5B7.6080102@joelhalpern.com> <787AE7BB302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.adroot.infra.ftgroup> <54EF2C9A.3040008@joelhalpern.com>
In-Reply-To: <54EF2C9A.3040008@joelhalpern.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.17.229]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <CAFED23FE327C44FBFA13761AF2043EB@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/cLCXnEAvuk0xlWhygXz8Mn98FCw>
Cc: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] draft-quinn-sfc-nsh: version number
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 02 Mar 2015 17:50:59 -0000

Hi,

Jumping in mid-thread. =20

Overall, I tend to agree with Joel.  Having an explicit version provides a =
simple way to handle dataplane format changes.  As Med points out, quickly =
correctly, IMHO, there are other way to signal changes via reserved bit.  I=
n practice though reserved bits are less useful since the convention is to =
ignore unknown bits, it makes using them for feature changes quite difficul=
t, which then brings up back to explicit versioning that cannot be ignored.=
 =20

I think Joel=92s suggestion below makes perfect sense and should be added t=
o the draft.

Paul


> On Feb 26, 2015, at 9:24 AM, Joel M. Halpern <jmh@joelhalpern.com> wrote:
>=20
> In one sense you are correct.  If you could count on everything being upg=
raded at once, sure you could just assume common interpretation.
> However, we have found over the years that such simultaneous upgrading ne=
ver works.  You need to be able to transition.
>=20
> I do agree that we should add text about what to do with version numbers =
that are not understood.  There are multiple choices that affect how we can=
 make changes.  My personal preference is:
>=20
> If an packet presumed to carry an NSH header is received at an SFF, and t=
he SFF does not understnad the version of the protocol as indicated in the =
base header, the packet MUST be discarded, and the event SHOULD be logged.
>=20
> This would allow an orderly transition, where devices can be upgraded to =
understand a new version, then generation of the new version header can be =
enabled.  If a configuration error is made, the packets will be dropped and=
 operators following good practices will get notifications.
>=20
> Yours,
> Joel
>=20
> On 2/26/15 2:16 AM, mohamed.boucadair@orange.com wrote:
>> Hi Joel,
>>=20
>> I fully agree with the extendibility of the header, but the question is =
why having a version number will be of help in the context of SFC? Second, =
having a version number without specifying the behavior when several versio=
ns are supported, when the version number is not supported by an SFC-aware =
element, etc. leaves open issues out of the spec.
>>=20
>> The other problem is that the current I-D includes several open doors le=
ft for extending the header:
>> * version
>> * reserved bits
>> * optional data
>>=20
>> This is too much for a header that is supposed to be compact and simple!
>>=20
>> There are other means to extend the header without signaling the version=
 in the packet. Having a distinct RFC number may be just fine in the contex=
t of an unidirectional stream such as SFC.
>>=20
>> Let us consider the situation where a version number is not explicitly s=
ignaled in the packet (but a new RFC updates the base SFC header). Several =
options can be considered, indeed (those are provided as examples for illus=
tration purposes):
>> * An operator can make sure that its SFC-enabled domain is configured in=
 a consistent manner to support one and only one version of the header. No =
interoperability issues is encountered in this case.
>> * An operator that wants to upgrade its SFC-enabled domain to support a =
new specification of the SFC header: An operator can decide to proceed to a=
 software/hardware updates but can maintain the old header in operation unt=
il all involved elements are upgraded to support the new version. Once the =
SFC-enabled domain is upgraded, then the new header can be enabled.
>>=20
>> Let's consider now that a version is signaled in the packet: to what ext=
ent signaling this information simplifies the SFC operations, and whether i=
t increases/decreases the serviceability of an SFC-enabled domain? Let's al=
so assess to what extent having the version number add more complexity in t=
he SFC header treatment when several versions are supported by a node/withi=
n an SFC enabled domain? How it helps interoperability? Some points for dis=
cussion are elaborated below:
>>=20
>> * If the SFC-enabled domain is configured to support the same version (w=
hich is likely): having the version number is not of any help.
>> * If the SFC-enabled domain involves some nodes that support version (v1=
) while others support (v2) (simple case): If these version are not backwar=
d compatible, this will lead to failures when two adjacent elements in a se=
rvice chain do not support the same version. The SFC system is broken. Havi=
ng the version number is not of any help in this case.
>> * If the SFC-enabled domain involves some nodes that support version (v1=
) while others support (v1 and v2):
>>=20
>> (a) The nodes that support both v1 and v2 should be instructed to decide=
 which version to be used. This can be either part of the specification or =
be driven by configuration. If a version number is included in the spec, I =
would expect to clarify the behavior in such case.
>>=20
>> (b) Suppose a node that supports only v1 receives a packet with header (=
v2): If this node does not support a notification procedure to inform the s=
ource that it does not support that header version, then FAILURES are intro=
duced in the network. This is a degradation of the service compared to lega=
cy scheme to structure services. This is not recommended, IMHO.
>>=20
>> (c) If a notification is received from an element about its supported ve=
rsion: a node can use another version (the logic to select other version is=
 another point to discuss) for that communication, but what to do for the n=
ext flows in the context of the same service chain or other chains that inv=
olves these two nodes as adjacent elements in the same chain? Shouldn't the=
se nodes cache the version to use for subsequent exchange to avoid receivin=
g the notification error each time? Wouldn't that complexity the behavior o=
f the SFC-aware elements?
>>=20
>> (d) If a notification is received from an element about its supported ve=
rsion: As this may occurs in various segments of a given service chain, e.g=
., (A(v1), B(v1,v2), C(v2), D(v1,v2), E(v1)). Notifying the adjacent node e=
ach time there is a version mismatch induce an extra delay, that may be not=
 be acceptable for every flow.
>>=20
>> I hope this clarifies my initial concern.
>>=20
>> Thank you.
>>=20
>> Cheers,
>> Med
>>=20
>>> -----Message d'origine-----
>>> De : Joel M. Halpern [mailto:jmh@joelhalpern.com]
>>> Envoy=E9 : mercredi 25 f=E9vrier 2015 16:10
>>> =C0 : BOUCADAIR Mohamed IMT/OLN; paulq@cisco.com
>>> Cc : sfc@ietf.org
>>> Objet : Re: [sfc] draft-quinn-sfc-nsh: version number
>>>=20
>>> I would really prefer to keep the version number.  Even though we have
>>> the MD-type identifier and for some MD we have the TLVs.
>>>=20
>>> The reason is that we may want to change the base header.  For example,
>>> suppose that the ciscussion about including a flow identifier in the
>>> base header had not come up now.  If it came up later, we would want to
>>> be able to have the discussion and make the choice, rather than being
>>> constrained by the lack of a version field.
>>>=20
>>> Yours,
>>> Joel
>>>=20
>>>=20
>>> On 2/25/15 10:03 AM, mohamed.boucadair@orange.com wrote:
>>>> Hi Paul, all,
>>>>=20
>>>> What is the purpose of having a version number in the header? Is there=
 a
>>>> kind of version negotiation that needs to be in place?
>>>>=20
>>>> I checked the I-D but failed to find text that explains the rationale,
>>>> the use of the such field and whether an error will be returned if the
>>>> version is not supported by the receiving node.
>>>>=20
>>>> Wouldn't be preferable to get rid of this field given that SFC header
>>>> can be extended using optional objects and consistent setup &
>>>> configuration within an SFC-enabled domain should be assumed?
>>>>=20
>>>> Thank you
>>>>=20
>>>> Cheers,
>>>>=20
>>>> Med
>>>>=20
>>>>=20
>>>>=20
>>>> _______________________________________________
>>>> sfc mailing list
>>>> sfc@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/sfc
>>>>=20
>>=20


From nobody Mon Mar  2 10:15:45 2015
Return-Path: <paulq@cisco.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F33C1A888C for <sfc@ietfa.amsl.com>; Mon,  2 Mar 2015 10:15:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 djB-ghph_Qwz for <sfc@ietfa.amsl.com>; Mon,  2 Mar 2015 10:15:41 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 228031A8884 for <sfc@ietf.org>; Mon,  2 Mar 2015 10:15:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11633; q=dns/txt; s=iport; t=1425320141; x=1426529741; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=3TRJxBfSBljNVVSZdSkAje2LocROuneTJo3DK4zOAV8=; b=kkYk3xBJXSCYrQm0NSkAN6jGtkgpX+elEi10yffGl2HOwGVpW222Fmlk ixxRC2HKmx2Vlr84AWkaxZiRTaXzeYxE6L7iBdH9aH89HkSPV8suwqOaV eISBRZ8VHO91dcqRoXCDb8r8LfIZ3+l4S7Sro8thgHfh01Fj6JQfHEpWx o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AkBQB4qPRU/5BdJa1agwJSXsE1CoVwAoEkTQEBAQEBAXyEDwEBAQMBAQEBJEcLBQcEAgEIDgMEAQEBJwcnCxQJCAIEDgUJEogMCA3WMwEBAQEBAQEBAQEBAQEBAQEBAQEBAReLEoQMEAIBHDMCBQaDEYEUBYVwigiDYIVngRo5gmeLYoM+I4NubwGBQ38BAQE
X-IronPort-AV: E=Sophos;i="5.09,676,1418083200"; d="scan'208";a="400612424"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-2.cisco.com with ESMTP; 02 Mar 2015 18:15:40 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id t22IFcvm013174 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 2 Mar 2015 18:15:39 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.229]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.03.0195.001; Mon, 2 Mar 2015 12:15:38 -0600
From: "Paul Quinn (paulq)" <paulq@cisco.com>
To: Dave Dolson <ddolson@sandvine.com>
Thread-Topic: [sfc] draft-quinn-sfc-nsh: Support of SF Spirals
Thread-Index: AdBRyhUadMfMQp0TQVyP+AHUYniSlAAOnhUAAABleoAAAFj2AAACvdgAAABVPAAAAMCGAAAA6mWAAABpgIAAysHQgA==
Date: Mon, 2 Mar 2015 18:15:38 +0000
Message-ID: <9E04808D-86A3-4FCC-8392-E9CBC392A4A6@cisco.com>
References: <787AE7BB302AE849A7480A190F8B9330049159EC@OPEXCLILM23.corporate.adroot.infra.ftgroup> <54EF3086.8040700@joelhalpern.com> <787AE7BB302AE849A7480A190F8B933004915B0E@OPEXCLILM23.corporate.adroot.infra.ftgroup> <54EF3584.2080005@joelhalpern.com> <E8355113905631478EFF04F5AA706E9830B556B4@wtl-exchp-2.sandvine.com> <CDF2F015F4429F458815ED2A6C2B6B0B2E83562F@MBX021-W3-CA-2.exch021.domain.local> <E8355113905631478EFF04F5AA706E9830B557B5@wtl-exchp-2.sandvine.com> <D1149479.B757%repenno@cisco.com> <E8355113905631478EFF04F5AA706E9830B55933@wtl-exchp-2.sandvine.com>
In-Reply-To: <E8355113905631478EFF04F5AA706E9830B55933@wtl-exchp-2.sandvine.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.17.229]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <A599C3276EA6B04AB24CD2A7169BA9E7@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/bZ_T2DebHj17yMXU6uz3VUczPoA>
Cc: "Joel M. Halpern" <jmh@joelhalpern.com>, "sfc@ietf.org" <sfc@ietf.org>, "Reinaldo Penno \(repenno\)" <repenno@cisco.com>, Ron Parker <Ron_Parker@affirmednetworks.com>, "Ben Wright \(Ben.Wright@metaswitch.com\)" <Ben.Wright@metaswitch.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Subject: Re: [sfc] draft-quinn-sfc-nsh: Support of SF Spirals
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 02 Mar 2015 18:15:44 -0000

> On Feb 26, 2015, at 12:30 PM, Dave Dolson <ddolson@sandvine.com> wrote:
>=20
> For the sake of argument, suppose I have a firewall SF, and I want to use=
=20
> it more than once in a chain. (Maybe I want to book-end the chain with in=
gress
> and egress rules.)
>=20
> Do you agree it would be sufficient to use the Path Index to select which=
 of
> the ingress or egress rule sets should be used?

I do, since it effect it acts a node identifier within a path, and _logical=
ly_ you have two firewalls.   There are, as others have pointed out, other =
ways to handle this (multiple network locators, metadata) but I believe tha=
t the index use is straightforward should a service want to use it as such.=
  If they can=92t or don=92t want to, I think multiple locators will be use=
d.  They need to be mutually exclusive.





>=20
> I'm probably missing something; I don't understand how the context header=
s
> define functionality. Maybe the device could communicate with itself=20
> (e.g., the ingress portion sending a tag to the egress portion)
> by sending state in the packet. Is that what you are mean by "contextual =
info" ?
>=20
>=20
>=20
> -----Original Message-----
> From: Reinaldo Penno (repenno) [mailto:repenno@cisco.com]=20
> Sent: Thursday, February 26, 2015 12:18 PM
> To: Dave Dolson; Ron Parker; Joel M. Halpern; mohamed.boucadair@orange.co=
m; sfc@ietf.org
> Cc: Ben Wright (Ben.Wright@metaswitch.com)
> Subject: Re: [sfc] draft-quinn-sfc-nsh: Support of SF Spirals
>=20
> Agreed on all points. I thought I was missing something so before writing
> this email I retested our implementation and it worked off the bat. The
> RSP constructed has the the same (SFF, SF) tuple but different indexes.
>=20
> The same SF is visited multiple times until the path ends.  If the SF
> wants contextual info across visits than context headers are the way to
> go.=20
>=20
>=20
> On 2/26/15, 8:52 AM, "Dave Dolson" <ddolson@sandvine.com> wrote:
>=20
>> Maybe naively, I thought the service functions would be provisioned with
>> a table:
>>=20
>> E.g., for element foo:
>> Path | Path Index | Next Hop  | Function
>> 123 |  4         |   SF-bar  | first behavior
>> 123 |  2         | SF-foobar | second behavior
>>=20
>>=20
>> The Function is clearly implementation specific. Maybe it points to a
>> configuration set or a policy set. I think completely out of scope here.
>>=20
>> I suggest that this is not a problem for the wire protocol, rather for
>> the configuration model (netconf or whatever).
>>=20
>> It becomes very much vendor-specific if the behaviors are complex
>> configurations of specialized features.
>>=20
>> If a person were manually configuring chains, I don't think they'd have =
a
>> conceptual problem, because they'd have a diagram they need to implement=
:
>> {SF-foo (first-behavior), SF-bar, SF-foo (second-behavior), SF-foobar}
>>=20
>> If we wanted to standardize it, we could maybe make the Function simply =
a
>> label that means something to the device--an indirection to a
>> configuration set.
>>=20
>> -Dave
>>=20
>>=20
>>=20
>> -----Original Message-----
>> From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of Ron Parker
>> Sent: Thursday, February 26, 2015 11:31 AM
>> To: Dave Dolson; Joel M. Halpern; mohamed.boucadair@orange.com;
>> sfc@ietf.org
>> Cc: Ben Wright (Ben.Wright@metaswitch.com)
>> Subject: Re: [sfc] draft-quinn-sfc-nsh: Support of SF Spirals
>>=20
>> Hi, Dave.
>>=20
>> I agree that on the wire, this is the way it would work.
>>=20
>> But, when composing the chain, it seems like information would be lackin=
g
>> if a chain were expressed simply as {SF-foo, SF-bar, SF-foo, SF-foobar}.
>> It is completely implicit that since SF-foo appears twice, it perhaps
>> should perform some different duty when index =3D 0 vs when index =3D 2.
>>=20
>> At first, I thought that an alternative way to handle this would be to
>> use multiple logical identities for SF-foo.  In this case, the chain
>> above would be expressed as {SF-foo-first-behavior, SF-bar,
>> SF-foo-second-behavior, SF-foobar}.   But, the problem here is selecting
>> the RSP, assuming that SF-foo has multiple instances.   Nothing in this
>> second flavor of chain says that the same instance of SF-foo-* must be
>> selected to satisfy SF-foo-first-behavior and SF-foo-second-behavior
>> (which may not be required, but should be possible to force as such).
>>=20
>> I guess what I'm saying is that spiraling has a subtlety to it that isn'=
t
>> yet adequately addressed and that I don't have a specific proposal to
>> solve it, either.
>>=20
>>  Ron
>>=20
>>=20
>> -----Original Message-----
>> From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of Dave Dolson
>> Sent: Thursday, February 26, 2015 11:21 AM
>> To: Joel M. Halpern; mohamed.boucadair@orange.com; sfc@ietf.org
>> Cc: Ben Wright (Ben.Wright@metaswitch.com)
>> Subject: Re: [sfc] draft-quinn-sfc-nsh: Support of SF Spirals
>>=20
>> If I may try to put it simply, I've always thought of it this way:
>> --> Each node in the chain selects the context for processing and the
>> next hop on the basis of BOTH path ID and Index, while decrementing the
>> index for the next hop.
>>=20
>> That behavior supports spiraling.
>>=20
>>=20
>>=20
>> -Dave
>>=20
>>=20
>> -----Original Message-----
>> From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of Joel M. Halpern
>> Sent: Thursday, February 26, 2015 10:02 AM
>> To: mohamed.boucadair@orange.com; sfc@ietf.org
>> Cc: Ben Wright (Ben.Wright@metaswitch.com)
>> Subject: Re: [sfc] draft-quinn-sfc-nsh: Support of SF Spirals
>>=20
>> There are two different aspects of Spirals.
>>=20
>> One of the two aspects is enabling a packet that repeatedly arrives at
>> the same SFF to get the correct services provided each time it arrives,
>> and to go to the correct next SFF each time it arrives.  The Service Pat=
h
>> Index, used by the SFF to select service functions and next SFF, provide=
s
>> that capability.
>>=20
>> The other aspect is how the Service Functions themselves handle spirals.
>> To a large degree, that depends upon the individual service function.
>> I normally assume that it would use packet context (as described in the
>> text you quote) to determine what to do.
>>=20
>> Since I would prefer that service functions are independent of the
>> underlying service function chaining infrastructure, and are not
>> sensitive to how many functions are before or after them in the chain, I
>> would personally prefer that they not use the path index for that.  I
>> would recommend that if the packet does not carry enough context that th=
e
>> service function could and should use metadata to carry its needed state
>> information.  But neither I personally nor the SFC Working Group get to
>> tell folks how to build their service functions.  So they may come up
>> with other methods for addressing their needs.  Which is also fine.
>>=20
>> Thus, I would not expect this document to discuss how service functions
>> themselves handle revisiting.  But metadata clearly allows for a range o=
f
>> behaviors that will work.  And the path index handles the SFF needs
>> relative to spirals, which is what we need to handle.
>>=20
>> Yours,
>> Joel
>>=20
>> On 2/26/15 9:52 AM, mohamed.boucadair@orange.com wrote:
>>> Re-,
>>>=20
>>> Spiral is not mentioned in the draft, but SF loop is.
>>>=20
>>> I'm asking the question because I don't get from the draft how spirals
>>> could work (that is a SF invoked several time in the context of the sam=
e
>>> SFC).
>>>=20
>>> Before proposing text, I would like to understand first how it works.
>>> If you can provide an example, this will be even great.
>>>=20
>>> Thank you.
>>>=20
>>> Cheers,
>>> Med
>>>=20
>>>> -----Message d'origine-----
>>>> De : Joel M. Halpern [mailto:jmh@joelhalpern.com] Envoy=E9 : jeudi 26
>>>> f=E9vrier 2015 15:41 =C0 : BOUCADAIR Mohamed IMT/OLN; sfc@ietf.org Cc =
:
>>>> Ben Wright (Ben.Wright@metaswitch.com) Objet : Re: [sfc]
>>>> draft-quinn-sfc-nsh: Support of SF Spirals
>>>>=20
>>>> The SF Spirals requirement is one of the key drivers for the index.
>>>> The index allows one to tell where one is in the spiral, and also to
>>>> break a loop if one has a loop instead of a spiral.
>>>>=20
>>>> Is there text that we could add that would help make this clear,
>>>> since your earlier question about the path index suggests that it is
>>>> not as clear as it should be?
>>>>=20
>>>> Yours,
>>>> Joel
>>>>=20
>>>> On 2/26/15 8:42 AM, mohamed.boucadair@orange.com wrote:
>>>>> Hi Paul, all,
>>>>>=20
>>>>> There were a discussion in the mailing list
>>>>> (http://www.ietf.org/mail-archive/web/sfc/current/msg01701.html)
>>>>> that led to defining what is meant by SF Spirals: (below is provided
>>>>> an excerpt from
>>>>> http://tools.ietf.org/html/draft-boucadair-sfc-requirements-06 where
>>>>> the conclusions of that discussion were recorded)
>>>>>=20
>>>>> "   o  Service Function Spiral: denotes a Service Function Chain in
>>>> which
>>>>>=20
>>>>>        data is handled by a Service Function, forwarded onwards,
>>>>> and
>>>>>=20
>>>>>        arrives once again at that Service Function.
>>>>>=20
>>>>>        *  Note that some Service Functions support built-in
>>>>> functions to
>>>>>=20
>>>>>           accommodate spirals; these service-specific functions may
>>>>>=20
>>>>>           require that the data received in a spiral should differ
>>>>> in a
>>>>>=20
>>>>>           way that will result in a different processing decision
>>>>> than
>>>>>=20
>>>>>           the original data.  This document does not make such
>>>>>=20
>>>>>           assumption.
>>>>>=20
>>>>>        *  A Service Function Chain may involve one or more Service
>>>>>=20
>>>>>           Function Spirals.
>>>>>=20
>>>>>        *  Unlike Service Function loop, spirals are not considered
>>>>> as
>>>>>=20
>>>>>           errors."
>>>>>=20
>>>>> And this companion requirement:
>>>>>=20
>>>>> "               A.  Service Functions MAY be invoked multiple times i=
n
>>>>>=20
>>>>>                     the same Service Function Chain (denoted as SF
>>>>>=20
>>>>>                     Spiral), but the solution MUST prevent infinite
>>>>>=20
>>>>>                     forwarding loops. =BB
>>>>>=20
>>>>> Reading the current draft-quinn-sfc-nsh, I don't see how this is met.
>>>>>=20
>>>>> Can you please clarify whether this is supported and how?
>>>>>=20
>>>>> Thank you.
>>>>>=20
>>>>> Cheers,
>>>>>=20
>>>>> Med
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> _______________________________________________
>>>>> sfc mailing list
>>>>> sfc@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/sfc
>>>>>=20
>>>=20
>>=20
>> _______________________________________________
>> sfc mailing list
>> sfc@ietf.org
>> https://www.ietf.org/mailman/listinfo/sfc
>>=20
>> _______________________________________________
>> sfc mailing list
>> sfc@ietf.org
>> https://www.ietf.org/mailman/listinfo/sfc
>>=20
>> _______________________________________________
>> sfc mailing list
>> sfc@ietf.org
>> https://www.ietf.org/mailman/listinfo/sfc
>>=20
>> _______________________________________________
>> sfc mailing list
>> sfc@ietf.org
>> https://www.ietf.org/mailman/listinfo/sfc
>=20
> _______________________________________________
> sfc mailing list
> sfc@ietf.org
> https://www.ietf.org/mailman/listinfo/sfc


From nobody Mon Mar  2 11:08:39 2015
Return-Path: <narten@us.ibm.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8F5F1A88A6 for <sfc@ietfa.amsl.com>; Mon,  2 Mar 2015 11:08:36 -0800 (PST)
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=ham
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 RumP_BJlF_IA for <sfc@ietfa.amsl.com>; Mon,  2 Mar 2015 11:08:35 -0800 (PST)
Received: from e36.co.us.ibm.com (e36.co.us.ibm.com [32.97.110.154]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D0811A88D8 for <sfc@ietf.org>; Mon,  2 Mar 2015 11:08:32 -0800 (PST)
Received: from /spool/local by e36.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <sfc@ietf.org> from <narten@us.ibm.com>; Mon, 2 Mar 2015 12:08:32 -0700
Received: from d03dlp03.boulder.ibm.com (9.17.202.179) by e36.co.us.ibm.com (192.168.1.136) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Mon, 2 Mar 2015 12:08:30 -0700
Received: from b03cxnp07028.gho.boulder.ibm.com (b03cxnp07028.gho.boulder.ibm.com [9.17.130.15]) by d03dlp03.boulder.ibm.com (Postfix) with ESMTP id ADFC119D8026 for <sfc@ietf.org>; Mon,  2 Mar 2015 11:59:37 -0700 (MST)
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by b03cxnp07028.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id t22J6tdA28573704 for <sfc@ietf.org>; Mon, 2 Mar 2015 12:06:55 -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 t22J84Lt013397 for <sfc@ietf.org>; Mon, 2 Mar 2015 12:08:04 -0700
Received: from cichlid.raleigh.ibm.com ([9.80.106.58]) by d03av04.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id t22J838R012135 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <sfc@ietf.org>; Mon, 2 Mar 2015 12:08:04 -0700
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 t22J7r45002750 for <sfc@ietf.org>; Mon, 2 Mar 2015 14:07:53 -0500
Date: Mon, 02 Mar 2015 14:07:52 -0500
Message-ID: <m3lhjfp69j.wl-narten@us.ibm.com>
From: Thomas Narten <narten@us.ibm.com>
To: sfc@ietf.org
User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) 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=ISO-8859-7
Content-Transfer-Encoding: quoted-printable
X-TM-AS-MML: disable
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 15030219-0021-0000-0000-000008F575DA
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/BBTNE6SumpRX3H7mb925IS8rN6k>
Subject: [sfc] Call for Dallas SFC Agenda Topics
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 02 Mar 2015 19:08:37 -0000

Greetings WG:

Our meeting at the upcoming Dallas venue is fast approaching.  As always, t=
he
goal of the meeting will be to make the best use of limited face-to-face ti=
me.

As we build the meeting agenda we welcome requests for agenda time. As alwa=
ys,
the goal of a meeting slot is to best further the work of the WG, and that
generally means focussing on key charter deliverables and topics with
important open issues to resolve. In the case of individual IDs, the goal
isn=A2t necessarily to present what is in the draft but rather to help the =
WG
decide what to do with the ID. With that in mind, when making an agenda
request please consider what you think the WG should do with its content. F=
or
example:

  * Does the document have useful content that should be moved into another=
 WG
    document or progress on it=A2s own merit
  * Does the content have a good basis for one of the WG documents per the
    charter (in order for that to happen the document needs to be the most
    appropriate out of the collection of related documents)
  * Should the document content be merged with one or more other documents,=
 so
    that a combined document could become a WG document

Jim & Thomas



From nobody Tue Mar  3 11:43:29 2015
Return-Path: <sunilvk@f5.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22A4D1A870C for <sfc@ietfa.amsl.com>; Tue,  3 Mar 2015 11:43:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.01
X-Spam-Level: 
X-Spam-Status: No, score=-7.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 u-kpGSWtxY1l for <sfc@ietfa.amsl.com>; Tue,  3 Mar 2015 11:43:20 -0800 (PST)
Received: from mail.f5.com (mail.f5.com [208.85.209.139]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A6A3F1A0070 for <sfc@ietf.org>; Tue,  3 Mar 2015 11:43:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=f5.com; i=@f5.com; q=dns/txt; s=seattle; t=1425411801; x=1456947801; h=from:to:subject:date:message-id:mime-version; bh=QzaOkNMWLwNIeyTtpHsVtUgKf1OEZUt8qrgcp7xYW5U=; b=HUG/WhJfwRNCfea3aZUMvQjNvFQH38jG6u39lw43Y/Hwes/GrOwKbGx1 xdb/RkEIuP/Jww2BPAzajHkdkUlGLd0Z/ToGOQUXL89lpnUtleaKqi+ck t3e7Yr3KR9Uhnz0IQEgUEBaMclxpDxJtY0ONA8HPkyyi/3wA+nbloNJn4 U=;
X-IronPort-AV: E=Sophos;i="5.09,683,1418083200";  d="scan'208,217";a="151533422"
X-IPAS-Result: A2A+BQAnDvZU/+sKqMBagj+BFVoEwRshAQmFcIF5AQEBAQEBfIQPAQEBAQIBAQEBKkEQDQEIFAEjBy4LFBIBBBMIAYgSAwkV0QkDhSgBCwEfixKEHQEBDTENgjhNgTEFii+DTYVdSoY5OZIMgiUcgVBvAYEBAgQDOX8BAQE
Received: from oracle-apps.f5net.com (HELO exchmail.f5net.com) ([192.168.10.235]) by mail.f5.com with ESMTP/TLS/AES256-SHA; 03 Mar 2015 19:43:19 +0000
Received: from SEAEXCHMBX05.olympus.F5Net.com (192.168.15.227) by SEAEXCHMBX05.olympus.F5Net.com (192.168.15.227) with Microsoft SMTP Server (TLS) id 15.0.1044.25; Tue, 3 Mar 2015 11:43:18 -0800
Received: from SEAEXCHMBX05.olympus.F5Net.com ([fe80::9cc0:5dc7:726d:3b50]) by SEAEXCHMBX05.olympus.F5Net.com ([fe80::9cc0:5dc7:726d:3b50%21]) with mapi id 15.00.1044.021; Tue, 3 Mar 2015 11:43:18 -0800
From: Sunil Vallamkonda <sunilvk@f5.com>
To: "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: Re: [sfc] draft-quinn-sfc-nsh: version number
Thread-Index: AdBV6VnhN9N2Adv/Rs2PZVkjw6sDlQ==
Date: Tue, 3 Mar 2015 19:43:17 +0000
Message-ID: <01f9e1a4e6514854a26556e4c6a3e36e@SEAEXCHMBX05.olympus.F5Net.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.168.15.239]
Content-Type: multipart/alternative; boundary="_000_01f9e1a4e6514854a26556e4c6a3e36eSEAEXCHMBX05olympusF5Ne_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/pAKWRB-mSxbiAsnx9uZn4eogFA4>
Subject: Re: [sfc] draft-quinn-sfc-nsh: version number
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 03 Mar 2015 19:43:27 -0000

--_000_01f9e1a4e6514854a26556e4c6a3e36eSEAEXCHMBX05olympusF5Ne_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,

Just going through the thread on version number (jumping in mid-thread),

Apart from the version mismatched (unsupported) packet dropped and logged, =
is there a plan for a back off mechanism by SFF to notify sender and avoid =
being overwhelmed with such packets ?

Thank you,
Sunil.


Re: [sfc] draft-quinn-sfc-nsh: version number
________________________________

  *   From: "Paul Quinn (paulq)" <paulq at cisco.com<mailto:paulq@DOMAIN.HI=
DDEN>>
  *   To: "Joel M. Halpern" <jmh at joelhalpern.com<mailto:jmh@DOMAIN.HIDDE=
N>>
  *   Cc: "mohamed.boucadair at orange.com<mailto:mohamed.boucadair@DOMAIN.=
HIDDEN>" <mohamed.boucadair at orange.com<mailto:mohamed.boucadair@DOMAIN.H=
IDDEN>>, "sfc at ietf.org<mailto:sfc@DOMAIN.HIDDEN>" <sfc at ietf.org<mailt=
o:sfc@DOMAIN.HIDDEN>>
  *   Date: Mon, 2 Mar 2015 17:50:53 +0000
  *   In-reply-to: <54EF2C9A.3040008@joelhalpern.com<http://www.ietf.org/ma=
il-archive/web/sfc/current/msg03181.html>>
  *   References: <787AE7BB302AE849A7480A190F8B9330049140B4@OPEXCLILM23.cor=
porate.adroot.infra.ftgroup> <54EDE5B7.6080102@joelhalpern.com<http://www.i=
etf.org/mail-archive/web/sfc/current/msg03151.html>> <787AE7BB302AE849A7480=
A190F8B9330049156A9@OPEXCLILM23.corporate.adroot.infra.ftgroup> <54EF2C9A.3=
040008@joelhalpern.com<http://www.ietf.org/mail-archive/web/sfc/current/msg=
03181.html>>
  *   List-id: Network Service Chaining <sfc.ietf.org>

________________________________

Hi,



Jumping in mid-thread.



Overall, I tend to agree with Joel.  Having an explicit version provides a =
simple way to handle dataplane format changes.  As Med points out, quickly =
correctly, IMHO, there are other way to signal changes via reserved bit.  I=
n practice though reserved bits are less useful since the convention is to =
ignore unknown bits, it makes using them for feature changes quite difficul=
t, which then brings up back to explicit versioning that cannot be ignored.



I think Joel's suggestion below makes perfect sense and should be added to =
the draft.



Paul





> On Feb 26, 2015, at 9:24 AM, Joel M. Halpern <jmh at joelhalpern.com> wro=
te:

>

> In one sense you are correct.  If you could count on everything being upg=
raded at once, sure you could just assume common interpretation.

> However, we have found over the years that such simultaneous upgrading ne=
ver works.  You need to be able to transition.

>

> I do agree that we should add text about what to do with version numbers =
that are not understood.  There are multiple choices that affect how we can=
 make changes.  My personal preference is:

>

> If an packet presumed to carry an NSH header is received at an SFF, and t=
he SFF does not understnad the version of the protocol as indicated in the =
base header, the packet MUST be discarded, and the event SHOULD be logged.

>

> This would allow an orderly transition, where devices can be upgraded to =
understand a new version, then generation of the new version header can be =
enabled.  If a configuration error is made, the packets will be dropped and=
 operators following good practices will get notifications.

>

> Yours,

> Joel

>

> On 2/26/15 2:16 AM, mohamed.boucadair at orange.com wrote:

>> Hi Joel,

>>

>> I fully agree with the extendibility of the header, but the question is =
why having a version number will be of help in the context of SFC? Second, =
having a version number without specifying the behavior when several versio=
ns are supported, when the version number is not supported by an SFC-aware =
element, etc. leaves open issues out of the spec.

>>

>> The other problem is that the current I-D includes several open doors le=
ft for extending the header:

>> * version

>> * reserved bits

>> * optional data

>>

>> This is too much for a header that is supposed to be compact and simple!

>>

>> There are other means to extend the header without signaling the version=
 in the packet. Having a distinct RFC number may be just fine in the contex=
t of an unidirectional stream such as SFC.

>>

>> Let us consider the situation where a version number is not explicitly s=
ignaled in the packet (but a new RFC updates the base SFC header). Several =
options can be considered, indeed (those are provided as examples for illus=
tration purposes):

>> * An operator can make sure that its SFC-enabled domain is configured in=
 a consistent manner to support one and only one version of the header. No =
interoperability issues is encountered in this case.

>> * An operator that wants to upgrade its SFC-enabled domain to support a =
new specification of the SFC header: An operator can decide to proceed to a=
 software/hardware updates but can maintain the old header in operation unt=
il all involved elements are upgraded to support the new version. Once the =
SFC-enabled domain is upgraded, then the new header can be enabled.

>>

>> Let's consider now that a version is signaled in the packet: to what ext=
ent signaling this information simplifies the SFC operations, and whether i=
t increases/decreases the serviceability of an SFC-enabled domain? Let's al=
so assess to what extent having the version number add more complexity in t=
he SFC header treatment when several versions are supported by a node/withi=
n an SFC enabled domain? How it helps interoperability? Some points for dis=
cussion are elaborated below:

>>

>> * If the SFC-enabled domain is configured to support the same version (w=
hich is likely): having the version number is not of any help.

>> * If the SFC-enabled domain involves some nodes that support version (v1=
) while others support (v2) (simple case): If these version are not backwar=
d compatible, this will lead to failures when two adjacent elements in a se=
rvice chain do not support the same version. The SFC system is broken. Havi=
ng the version number is not of any help in this case.

>> * If the SFC-enabled domain involves some nodes that support version (v1=
) while others support (v1 and v2):

>>

>> (a) The nodes that support both v1 and v2 should be instructed to decide=
 which version to be used. This can be either part of the specification or =
be driven by configuration. If a version number is included in the spec, I =
would expect to clarify the behavior in such case.

>>

>> (b) Suppose a node that supports only v1 receives a packet with header (=
v2): If this node does not support a notification procedure to inform the s=
ource that it does not support that header version, then FAILURES are intro=
duced in the network. This is a degradation of the service compared to lega=
cy scheme to structure services. This is not recommended, IMHO.

>>

>> (c) If a notification is received from an element about its supported ve=
rsion: a node can use another version (the logic to select other version is=
 another point to discuss) for that communication, but what to do for the n=
ext flows in the context of the same service chain or other chains that inv=
olves these two nodes as adjacent elements in the same chain? Shouldn't the=
se nodes cache the version to use for subsequent exchange to avoid receivin=
g the notification error each time? Wouldn't that complexity the behavior o=
f the SFC-aware elements?

>>

>> (d) If a notification is received from an element about its supported ve=
rsion: As this may occurs in various segments of a given service chain, e.g=
., (A(v1), B(v1,v2), C(v2), D(v1,v2), E(v1)). Notifying the adjacent node e=
ach time there is a version mismatch induce an extra delay, that may be not=
 be acceptable for every flow.

>>

>> I hope this clarifies my initial concern.

>>

>> Thank you.

>>

>> Cheers,

>> Med

>>

>>> -----Message d'origine-----

>>> De : Joel M. Halpern [mailto:jmh at joelhalpern.com]

>>> Envoy=E9 : mercredi 25 f=E9vrier 2015 16:10

>>> =C0 : BOUCADAIR Mohamed IMT/OLN; paulq at cisco.com

>>> Cc : sfc at ietf.org

>>> Objet : Re: [sfc] draft-quinn-sfc-nsh: version number

>>>

>>> I would really prefer to keep the version number.  Even though we have

>>> the MD-type identifier and for some MD we have the TLVs.

>>>

>>> The reason is that we may want to change the base header.  For example,

>>> suppose that the ciscussion about including a flow identifier in the

>>> base header had not come up now.  If it came up later, we would want to

>>> be able to have the discussion and make the choice, rather than being

>>> constrained by the lack of a version field.

>>>

>>> Yours,

>>> Joel

>>>

>>>

>>> On 2/25/15 10:03 AM, mohamed.boucadair at orange.com wrote:

>>>> Hi Paul, all,

>>>>

>>>> What is the purpose of having a version number in the header? Is there=
 a

>>>> kind of version negotiation that needs to be in place?

>>>>

>>>> I checked the I-D but failed to find text that explains the rationale,

>>>> the use of the such field and whether an error will be returned if the

>>>> version is not supported by the receiving node.

>>>>

>>>> Wouldn't be preferable to get rid of this field given that SFC header

>>>> can be extended using optional objects and consistent setup &

>>>> configuration within an SFC-enabled domain should be assumed?

>>>>

>>>> Thank you

>>>>

>>>> Cheers,

>>>>

>>>> Med

>>>>

>>>>

>>>>

>>>> _______________________________________________

>>>> sfc mailing list

>>>> sfc at ietf.org

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

>>>>

>>




--_000_01f9e1a4e6514854a26556e4c6a3e36eSEAEXCHMBX05olympusF5Ne_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
h1
	{mso-style-priority:9;
	mso-style-link:"Heading 1 Char";
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:24.0pt;
	font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.Heading1Char
	{mso-style-name:"Heading 1 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 1";
	font-family:"Times New Roman",serif;
	font-weight:bold;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1172985525;
	mso-list-template-ids:1467404642;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Just going through the thread on version number (jum=
ping in mid-thread),<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Apart from the version mismatched (unsupported) pack=
et dropped and logged, is there a plan for a back off mechanism by SFF to n=
otify sender and avoid being overwhelmed with such packets ?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thank you,<o:p></o:p></p>
<p class=3D"MsoNormal">Sunil.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<h1><span style=3D"font-size:14.0pt;font-weight:normal">Re: [sfc] draft-qui=
nn-sfc-nsh: version number<o:p></o:p></span></h1>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"100%" align=3D"center">
</div>
<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;=
mso-fareast-language:EN-US">
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto;mso-list:l0 level1 lfo1">
<em><span style=3D"font-family:&quot;Calibri&quot;,sans-serif">From</span><=
/em>: &quot;Paul Quinn (paulq)&quot; &lt;<a href=3D"mailto:paulq@DOMAIN.HID=
DEN">paulq at cisco.com</a>&gt;<o:p></o:p></li><li class=3D"MsoNormal" styl=
e=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 =
lfo1">
<em><span style=3D"font-family:&quot;Calibri&quot;,sans-serif">To</span></e=
m>: &quot;Joel M. Halpern&quot; &lt;<a href=3D"mailto:jmh@DOMAIN.HIDDEN">jm=
h at joelhalpern.com</a>&gt;<o:p></o:p></li><li class=3D"MsoNormal" style=
=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 l=
fo1">
<em><span style=3D"font-family:&quot;Calibri&quot;,sans-serif">Cc</span></e=
m>: &quot;<a href=3D"mailto:mohamed.boucadair@DOMAIN.HIDDEN">mohamed.boucad=
air at orange.com</a>&quot; &lt;<a href=3D"mailto:mohamed.boucadair@DOMAIN.=
HIDDEN">mohamed.boucadair at orange.com</a>&gt;, &quot;<a href=3D"mailto:sf=
c@DOMAIN.HIDDEN">sfc
 at ietf.org</a>&quot; &lt;<a href=3D"mailto:sfc@DOMAIN.HIDDEN">sfc at ietf=
.org</a>&gt;<o:p></o:p></li><li class=3D"MsoNormal" style=3D"mso-margin-top=
-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<em><span style=3D"font-family:&quot;Calibri&quot;,sans-serif">Date</span><=
/em>: Mon, 2 Mar 2015 17:50:53 &#43;0000<o:p></o:p></li><li class=3D"MsoNor=
mal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l=
0 level1 lfo1">
<em><span style=3D"font-family:&quot;Calibri&quot;,sans-serif">In-reply-to<=
/span></em>: &lt;<a href=3D"http://www.ietf.org/mail-archive/web/sfc/curren=
t/msg03181.html">54EF2C9A.3040008@joelhalpern.com</a>&gt;<o:p></o:p></li><l=
i class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al=
t:auto;mso-list:l0 level1 lfo1">
<em><span style=3D"font-family:&quot;Calibri&quot;,sans-serif">References</=
span></em>: &lt;787AE7BB302AE849A7480A190F8B9330049140B4@OPEXCLILM23.corpor=
ate.adroot.infra.ftgroup&gt; &lt;<a href=3D"http://www.ietf.org/mail-archiv=
e/web/sfc/current/msg03151.html">54EDE5B7.6080102@joelhalpern.com</a>&gt;
 &lt;787AE7BB302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.adroot.=
infra.ftgroup&gt; &lt;<a href=3D"http://www.ietf.org/mail-archive/web/sfc/c=
urrent/msg03181.html">54EF2C9A.3040008@joelhalpern.com</a>&gt;<o:p></o:p></=
li><li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto;mso-list:l0 level1 lfo1">
<em><span style=3D"font-family:&quot;Calibri&quot;,sans-serif">List-id</spa=
n></em>: Network Service Chaining &lt;sfc.ietf.org&gt;<o:p></o:p></li></ul>
</span>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"100%" align=3D"center">
</div>
<pre>Hi,<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Jumping in mid-thread.&nbsp; <o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Overall, I tend to agree with Joel.&nbsp; Having an explicit version p=
rovides a simple way to handle dataplane format changes.&nbsp; As Med point=
s out, quickly correctly, IMHO, there are other way to signal changes via r=
eserved bit.&nbsp; In practice though reserved bits are less useful since t=
he convention is to ignore unknown bits, it makes using them for feature ch=
anges quite difficult, which then brings up back to explicit versioning tha=
t cannot be ignored.&nbsp; <o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>I think Joel&#8217;s suggestion below makes perfect sense and should b=
e added to the draft.<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Paul<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>&gt; On Feb 26, 2015, at 9:24 AM, Joel M. Halpern &lt;jmh at joelhalpe=
rn.com&gt; wrote:<o:p></o:p></pre>
<pre>&gt; <o:p></o:p></pre>
<pre>&gt; In one sense you are correct.&nbsp; If you could count on everyth=
ing being upgraded at once, sure you could just assume common interpretatio=
n.<o:p></o:p></pre>
<pre>&gt; However, we have found over the years that such simultaneous upgr=
ading never works.&nbsp; You need to be able to transition.<o:p></o:p></pre=
>
<pre>&gt; <o:p></o:p></pre>
<pre>&gt; I do agree that we should add text about what to do with version =
numbers that are not understood.&nbsp; There are multiple choices that affe=
ct how we can make changes.&nbsp; My personal preference is:<o:p></o:p></pr=
e>
<pre>&gt; <o:p></o:p></pre>
<pre>&gt; If an packet presumed to carry an NSH header is received at an SF=
F, and the SFF does not understnad the version of the protocol as indicated=
 in the base header, the packet MUST be discarded, and the event SHOULD be =
logged.<o:p></o:p></pre>
<pre>&gt; <o:p></o:p></pre>
<pre>&gt; This would allow an orderly transition, where devices can be upgr=
aded to understand a new version, then generation of the new version header=
 can be enabled.&nbsp; If a configuration error is made, the packets will b=
e dropped and operators following good practices will get notifications.<o:=
p></o:p></pre>
<pre>&gt; <o:p></o:p></pre>
<pre>&gt; Yours,<o:p></o:p></pre>
<pre>&gt; Joel<o:p></o:p></pre>
<pre>&gt; <o:p></o:p></pre>
<pre>&gt; On 2/26/15 2:16 AM, mohamed.boucadair at orange.com wrote:<o:p></=
o:p></pre>
<pre>&gt;&gt; Hi Joel,<o:p></o:p></pre>
<pre>&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt; I fully agree with the extendibility of the header, but the q=
uestion is why having a version number will be of help in the context of SF=
C? Second, having a version number without specifying the behavior when sev=
eral versions are supported, when the version number is not supported by an=
 SFC-aware element, etc. leaves open issues out of the spec.<o:p></o:p></pr=
e>
<pre>&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt; The other problem is that the current I-D includes several op=
en doors left for extending the header:<o:p></o:p></pre>
<pre>&gt;&gt; * version<o:p></o:p></pre>
<pre>&gt;&gt; * reserved bits<o:p></o:p></pre>
<pre>&gt;&gt; * optional data<o:p></o:p></pre>
<pre>&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt; This is too much for a header that is supposed to be compact =
and simple!<o:p></o:p></pre>
<pre>&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt; There are other means to extend the header without signaling =
the version in the packet. Having a distinct RFC number may be just fine in=
 the context of an unidirectional stream such as SFC.<o:p></o:p></pre>
<pre>&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt; Let us consider the situation where a version number is not e=
xplicitly signaled in the packet (but a new RFC updates the base SFC header=
). Several options can be considered, indeed (those are provided as example=
s for illustration purposes):<o:p></o:p></pre>
<pre>&gt;&gt; * An operator can make sure that its SFC-enabled domain is co=
nfigured in a consistent manner to support one and only one version of the =
header. No interoperability issues is encountered in this case.<o:p></o:p><=
/pre>
<pre>&gt;&gt; * An operator that wants to upgrade its SFC-enabled domain to=
 support a new specification of the SFC header: An operator can decide to p=
roceed to a software/hardware updates but can maintain the old header in op=
eration until all involved elements are upgraded to support the new version=
. Once the SFC-enabled domain is upgraded, then the new header can be enabl=
ed.<o:p></o:p></pre>
<pre>&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt; Let's consider now that a version is signaled in the packet: =
to what extent signaling this information simplifies the SFC operations, an=
d whether it increases/decreases the serviceability of an SFC-enabled domai=
n? Let's also assess to what extent having the version number add more comp=
lexity in the SFC header treatment when several versions are supported by a=
 node/within an SFC enabled domain? How it helps interoperability? Some poi=
nts for discussion are elaborated below:<o:p></o:p></pre>
<pre>&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt; * If the SFC-enabled domain is configured to support the same=
 version (which is likely): having the version number is not of any help.<o=
:p></o:p></pre>
<pre>&gt;&gt; * If the SFC-enabled domain involves some nodes that support =
version (v1) while others support (v2) (simple case): If these version are =
not backward compatible, this will lead to failures when two adjacent eleme=
nts in a service chain do not support the same version. The SFC system is b=
roken. Having the version number is not of any help in this case.<o:p></o:p=
></pre>
<pre>&gt;&gt; * If the SFC-enabled domain involves some nodes that support =
version (v1) while others support (v1 and v2):<o:p></o:p></pre>
<pre>&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt; (a) The nodes that support both v1 and v2 should be instructe=
d to decide which version to be used. This can be either part of the specif=
ication or be driven by configuration. If a version number is included in t=
he spec, I would expect to clarify the behavior in such case.<o:p></o:p></p=
re>
<pre>&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt; (b) Suppose a node that supports only v1 receives a packet wi=
th header (v2): If this node does not support a notification procedure to i=
nform the source that it does not support that header version, then FAILURE=
S are introduced in the network. This is a degradation of the service compa=
red to legacy scheme to structure services. This is not recommended, IMHO.<=
o:p></o:p></pre>
<pre>&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt; (c) If a notification is received from an element about its s=
upported version: a node can use another version (the logic to select other=
 version is another point to discuss) for that communication, but what to d=
o for the next flows in the context of the same service chain or other chai=
ns that involves these two nodes as adjacent elements in the same chain? Sh=
ouldn't these nodes cache the version to use for subsequent exchange to avo=
id receiving the notification error each time? Wouldn't that complexity the=
 behavior of the SFC-aware elements?<o:p></o:p></pre>
<pre>&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt; (d) If a notification is received from an element about its s=
upported version: As this may occurs in various segments of a given service=
 chain, e.g., (A(v1), B(v1,v2), C(v2), D(v1,v2), E(v1)). Notifying the adja=
cent node each time there is a version mismatch induce an extra delay, that=
 may be not be acceptable for every flow.<o:p></o:p></pre>
<pre>&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt; I hope this clarifies my initial concern.<o:p></o:p></pre>
<pre>&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt; Thank you.<o:p></o:p></pre>
<pre>&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt; Cheers,<o:p></o:p></pre>
<pre>&gt;&gt; Med<o:p></o:p></pre>
<pre>&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt;&gt; -----Message d'origine-----<o:p></o:p></pre>
<pre>&gt;&gt;&gt; De : Joel M. Halpern [<a href=3D"mailto:jmh">mailto:jmh</=
a> at joelhalpern.com]<o:p></o:p></pre>
<pre>&gt;&gt;&gt; Envoy=E9 : mercredi 25 f=E9vrier 2015 16:10<o:p></o:p></p=
re>
<pre>&gt;&gt;&gt; =C0 : BOUCADAIR Mohamed IMT/OLN; paulq at cisco.com<o:p><=
/o:p></pre>
<pre>&gt;&gt;&gt; Cc : sfc at ietf.org<o:p></o:p></pre>
<pre>&gt;&gt;&gt; Objet : Re: [sfc] draft-quinn-sfc-nsh: version number<o:p=
></o:p></pre>
<pre>&gt;&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt;&gt; I would really prefer to keep the version number.&nbsp; E=
ven though we have<o:p></o:p></pre>
<pre>&gt;&gt;&gt; the MD-type identifier and for some MD we have the TLVs.<=
o:p></o:p></pre>
<pre>&gt;&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt;&gt; The reason is that we may want to change the base header.=
&nbsp; For example,<o:p></o:p></pre>
<pre>&gt;&gt;&gt; suppose that the ciscussion about including a flow identi=
fier in the<o:p></o:p></pre>
<pre>&gt;&gt;&gt; base header had not come up now.&nbsp; If it came up late=
r, we would want to<o:p></o:p></pre>
<pre>&gt;&gt;&gt; be able to have the discussion and make the choice, rathe=
r than being<o:p></o:p></pre>
<pre>&gt;&gt;&gt; constrained by the lack of a version field.<o:p></o:p></p=
re>
<pre>&gt;&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt;&gt; Yours,<o:p></o:p></pre>
<pre>&gt;&gt;&gt; Joel<o:p></o:p></pre>
<pre>&gt;&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt;&gt; On 2/25/15 10:03 AM, mohamed.boucadair at orange.com wrot=
e:<o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; Hi Paul, all,<o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; What is the purpose of having a version number in the=
 header? Is there a<o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; kind of version negotiation that needs to be in place=
?<o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; I checked the I-D but failed to find text that explai=
ns the rationale,<o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; the use of the such field and whether an error will b=
e returned if the<o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; version is not supported by the receiving node.<o:p><=
/o:p></pre>
<pre>&gt;&gt;&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; Wouldn't be preferable to get rid of this field given=
 that SFC header<o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; can be extended using optional objects and consistent=
 setup &amp;<o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; configuration within an SFC-enabled domain should be =
assumed?<o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; Thank you<o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; Cheers,<o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; Med<o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; _______________________________________________<o:p><=
/o:p></pre>
<pre>&gt;&gt;&gt;&gt; sfc mailing list<o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; sfc at ietf.org<o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/sfc"=
>https://www.ietf.org/mailman/listinfo/sfc</a><o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt; <o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_01f9e1a4e6514854a26556e4c6a3e36eSEAEXCHMBX05olympusF5Ne_--


From nobody Tue Mar  3 11:47:33 2015
Return-Path: <sunilvk@f5.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7D6F1A6EF4 for <sfc@ietfa.amsl.com>; Tue,  3 Mar 2015 11:47:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.01
X-Spam-Level: 
X-Spam-Status: No, score=-7.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 UJgHcnkEESBU for <sfc@ietfa.amsl.com>; Tue,  3 Mar 2015 11:47:25 -0800 (PST)
Received: from mail.f5.com (mail.f5.com [208.85.209.139]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F2DA1A0070 for <sfc@ietf.org>; Tue,  3 Mar 2015 11:47:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=f5.com; i=@f5.com; q=dns/txt; s=seattle; t=1425412046; x=1456948046; h=from:to:subject:date:message-id:mime-version; bh=va9cT9/kR6uVkq8hEHORijs5j1V4hPiQeABWotky43Y=; b=yV4FDklhIeLYcC6M8471Dxaaez7rWNtXRyQPKuh4dBHHVUEuivw/O+JF /KzPbiG0ufMJMRf1u7DEUcd1TJLL8L9fmprFYH1w6xUwFoaLnAkv0GwQm iqgau9E3rha/gR02ZyxxDUAg1TlFPtVemLjpeFbwLXT1UVQKeTzL+y+0q I=;
X-IronPort-AV: E=Sophos;i="5.09,683,1418083200";  d="scan'208,217";a="151533914"
X-IPAS-Result: A2A+BQBUD/ZU/+sKqMBagj+BFVoEwSMZAQmFcIF6AQEBAQEBfIQPAQEBAQIBAQEBKkEQDQEIFAEjAQYuCxQSAQQTCAGIEgMJFdEGA4UoAQsBH4sShB0BAQ0xDYI4TYExBYovg02FXUqGOTmSDIIlHIFQbwEBgQACBAM5fwEBAQ
Received: from oracle-apps.f5net.com (HELO exchmail.f5net.com) ([192.168.10.235]) by mail.f5.com with ESMTP/TLS/AES256-SHA; 03 Mar 2015 19:47:24 +0000
Received: from SEAEXCHMBX05.olympus.F5Net.com (192.168.15.227) by seaexchmbx02.olympus.F5Net.com (192.168.15.224) with Microsoft SMTP Server (TLS) id 15.0.1044.25; Tue, 3 Mar 2015 11:47:23 -0800
Received: from SEAEXCHMBX05.olympus.F5Net.com ([fe80::9cc0:5dc7:726d:3b50]) by SEAEXCHMBX05.olympus.F5Net.com ([fe80::9cc0:5dc7:726d:3b50%21]) with mapi id 15.00.1044.021; Tue, 3 Mar 2015 11:47:23 -0800
From: Sunil Vallamkonda <sunilvk@f5.com>
To: "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: Re:  draft-quinn-sfc-nsh: version number
Thread-Index: AdBV6r/FN0JMQHAoR4aalOEAFqQ5yw==
Date: Tue, 3 Mar 2015 19:47:22 +0000
Message-ID: <569e5fda6aa0486aaa7ff1853ed85576@SEAEXCHMBX05.olympus.F5Net.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.168.15.239]
Content-Type: multipart/alternative; boundary="_000_569e5fda6aa0486aaa7ff1853ed85576SEAEXCHMBX05olympusF5Ne_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/yd3d2moVI4rLCateKc98crKdgaE>
Subject: Re: [sfc] draft-quinn-sfc-nsh: version number
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 03 Mar 2015 19:47:31 -0000

--_000_569e5fda6aa0486aaa7ff1853ed85576SEAEXCHMBX05olympusF5Ne_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,

Just going through the thread on version number (jumping in mid-thread),

Apart from the version mismatched (unsupported) packet dropped and logged, =
is there a plan for a back off mechanism by SFF to notify sender and avoid =
being overwhelmed with such packets ?

Thank you,
Sunil.


--
Re: [sfc] draft-quinn-sfc-nsh: version number
________________________________

  *   From: "Paul Quinn (paulq)" <paulq at cisco.com<mailto:paulq@DOMAIN.HI=
DDEN>>
  *   To: "Joel M. Halpern" <jmh at joelhalpern.com<mailto:jmh@DOMAIN.HIDDE=
N>>
  *   Cc: "mohamed.boucadair at orange.com<mailto:mohamed.boucadair@DOMAIN.=
HIDDEN>" <mohamed.boucadair at orange.com<mailto:mohamed.boucadair@DOMAIN.H=
IDDEN>>, "sfc at ietf.org<mailto:sfc@DOMAIN.HIDDEN>" <sfc at ietf.org<mailt=
o:sfc@DOMAIN.HIDDEN>>
  *   Date: Mon, 2 Mar 2015 17:50:53 +0000
  *   In-reply-to: <54EF2C9A.3040008@joelhalpern.com<http://www.ietf.org/ma=
il-archive/web/sfc/current/msg03181.html>>
  *   References: <787AE7BB302AE849A7480A190F8B9330049140B4@OPEXCLILM23.cor=
porate.adroot.infra.ftgroup<mailto:787AE7BB302AE849A7480A190F8B9330049140B4=
@OPEXCLILM23.corporate.adroot.infra.ftgroup>> <54EDE5B7.6080102@joelhalpern=
.com<http://www.ietf.org/mail-archive/web/sfc/current/msg03151.html>> <787A=
E7BB302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.adroot.infra.ftg=
roup<mailto:787AE7BB302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.=
adroot.infra.ftgroup>> <54EF2C9A.3040008@joelhalpern.com<http://www.ietf.or=
g/mail-archive/web/sfc/current/msg03181.html>>
  *   List-id: Network Service Chaining <sfc.ietf.org>

________________________________

Hi,



Jumping in mid-thread.



Overall, I tend to agree with Joel.  Having an explicit version provides a =
simple way to handle dataplane format changes.  As Med points out, quickly =
correctly, IMHO, there are other way to signal changes via reserved bit.  I=
n practice though reserved bits are less useful since the convention is to =
ignore unknown bits, it makes using them for feature changes quite difficul=
t, which then brings up back to explicit versioning that cannot be ignored.



I think Joel's suggestion below makes perfect sense and should be added to =
the draft.



Paul





> On Feb 26, 2015, at 9:24 AM, Joel M. Halpern <jmh at joelhalpern.com> wro=
te:

>

> In one sense you are correct.  If you could count on everything being upg=
raded at once, sure you could just assume common interpretation.

> However, we have found over the years that such simultaneous upgrading ne=
ver works.  You need to be able to transition.

>

> I do agree that we should add text about what to do with version numbers =
that are not understood.  There are multiple choices that affect how we can=
 make changes.  My personal preference is:

>

> If an packet presumed to carry an NSH header is received at an SFF, and t=
he SFF does not understnad the version of the protocol as indicated in the =
base header, the packet MUST be discarded, and the event SHOULD be logged.

>

> This would allow an orderly transition, where devices can be upgraded to =
understand a new version, then generation of the new version header can be =
enabled.  If a configuration error is made, the packets will be dropped and=
 operators following good practices will get notifications.

>

> Yours,

> Joel

>

> On 2/26/15 2:16 AM, mohamed.boucadair at orange.com wrote:

>> Hi Joel,

>>

>> I fully agree with the extendibility of the header, but the question is =
why having a version number will be of help in the context of SFC? Second, =
having a version number without specifying the behavior when several versio=
ns are supported, when the version number is not supported by an SFC-aware =
element, etc. leaves open issues out of the spec.

>>

>> The other problem is that the current I-D includes several open doors le=
ft for extending the header:

>> * version

>> * reserved bits

>> * optional data

>>

>> This is too much for a header that is supposed to be compact and simple!

>>

>> There are other means to extend the header without signaling the version=
 in the packet. Having a distinct RFC number may be just fine in the contex=
t of an unidirectional stream such as SFC.

>>

>> Let us consider the situation where a version number is not explicitly s=
ignaled in the packet (but a new RFC updates the base SFC header). Several =
options can be considered, indeed (those are provided as examples for illus=
tration purposes):

>> * An operator can make sure that its SFC-enabled domain is configured in=
 a consistent manner to support one and only one version of the header. No =
interoperability issues is encountered in this case.

>> * An operator that wants to upgrade its SFC-enabled domain to support a =
new specification of the SFC header: An operator can decide to proceed to a=
 software/hardware updates but can maintain the old header in operation unt=
il all involved elements are upgraded to support the new version. Once the =
SFC-enabled domain is upgraded, then the new header can be enabled.

>>

>> Let's consider now that a version is signaled in the packet: to what ext=
ent signaling this information simplifies the SFC operations, and whether i=
t increases/decreases the serviceability of an SFC-enabled domain? Let's al=
so assess to what extent having the version number add more complexity in t=
he SFC header treatment when several versions are supported by a node/withi=
n an SFC enabled domain? How it helps interoperability? Some points for dis=
cussion are elaborated below:

>>

>> * If the SFC-enabled domain is configured to support the same version (w=
hich is likely): having the version number is not of any help.

>> * If the SFC-enabled domain involves some nodes that support version (v1=
) while others support (v2) (simple case): If these version are not backwar=
d compatible, this will lead to failures when two adjacent elements in a se=
rvice chain do not support the same version. The SFC system is broken. Havi=
ng the version number is not of any help in this case.

>> * If the SFC-enabled domain involves some nodes that support version (v1=
) while others support (v1 and v2):

>>

>> (a) The nodes that support both v1 and v2 should be instructed to decide=
 which version to be used. This can be either part of the specification or =
be driven by configuration. If a version number is included in the spec, I =
would expect to clarify the behavior in such case.

>>

>> (b) Suppose a node that supports only v1 receives a packet with header (=
v2): If this node does not support a notification procedure to inform the s=
ource that it does not support that header version, then FAILURES are intro=
duced in the network. This is a degradation of the service compared to lega=
cy scheme to structure services. This is not recommended, IMHO.

>>

>> (c) If a notification is received from an element about its supported ve=
rsion: a node can use another version (the logic to select other version is=
 another point to discuss) for that communication, but what to do for the n=
ext flows in the context of the same service chain or other chains that inv=
olves these two nodes as adjacent elements in the same chain? Shouldn't the=
se nodes cache the version to use for subsequent exchange to avoid receivin=
g the notification error each time? Wouldn't that complexity the behavior o=
f the SFC-aware elements?

>>

>> (d) If a notification is received from an element about its supported ve=
rsion: As this may occurs in various segments of a given service chain, e.g=
., (A(v1), B(v1,v2), C(v2), D(v1,v2), E(v1)). Notifying the adjacent node e=
ach time there is a version mismatch induce an extra delay, that may be not=
 be acceptable for every flow.

>>

>> I hope this clarifies my initial concern.

>>

>> Thank you.

>>

>> Cheers,

>> Med

>>

>>> -----Message d'origine-----

>>> De : Joel M. Halpern [mailto:jmh at joelhalpern.com]

>>> Envoy=E9 : mercredi 25 f=E9vrier 2015 16:10

>>> =C0 : BOUCADAIR Mohamed IMT/OLN; paulq at cisco.com

>>> Cc : sfc at ietf.org

>>> Objet : Re: [sfc] draft-quinn-sfc-nsh: version number

>>>

>>> I would really prefer to keep the version number.  Even though we have

>>> the MD-type identifier and for some MD we have the TLVs.

>>>

>>> The reason is that we may want to change the base header.  For example,

>>> suppose that the ciscussion about including a flow identifier in the

>>> base header had not come up now.  If it came up later, we would want to

>>> be able to have the discussion and make the choice, rather than being

>>> constrained by the lack of a version field.

>>>

>>> Yours,

>>> Joel

>>>

>>>

>>> On 2/25/15 10:03 AM, mohamed.boucadair at orange.com wrote:

>>>> Hi Paul, all,

>>>>

>>>> What is the purpose of having a version number in the header? Is there=
 a

>>>> kind of version negotiation that needs to be in place?

>>>>

>>>> I checked the I-D but failed to find text that explains the rationale,

>>>> the use of the such field and whether an error will be returned if the

>>>> version is not supported by the receiving node.

>>>>

>>>> Wouldn't be preferable to get rid of this field given that SFC header

>>>> can be extended using optional objects and consistent setup &

>>>> configuration within an SFC-enabled domain should be assumed?

>>>>

>>>> Thank you

>>>>

>>>> Cheers,

>>>>

>>>> Med

>>>>

>>>>

>>>>

>>>> _______________________________________________

>>>> sfc mailing list

>>>> sfc at ietf.org

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

>>>>

>>





--_000_569e5fda6aa0486aaa7ff1853ed85576SEAEXCHMBX05olympusF5Ne_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
h1
	{mso-style-priority:9;
	mso-style-link:"Heading 1 Char";
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:24.0pt;
	font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.Heading1Char
	{mso-style-name:"Heading 1 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 1";
	font-family:"Times New Roman",serif;
	font-weight:bold;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:171454125;
	mso-list-template-ids:-641565516;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1
	{mso-list-id:1172985525;
	mso-list-template-ids:1467404642;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Just going through the thread on version number (jum=
ping in mid-thread),<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Apart from the version mismatched (unsupported) pack=
et dropped and logged, is there a plan for a back off mechanism by SFF to n=
otify sender and avoid being overwhelmed with such packets ?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thank you,<o:p></o:p></p>
<p class=3D"MsoNormal">Sunil.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">--<o:p></o:p></p>
<h1><span style=3D"font-size:14.0pt;font-weight:normal">Re: [sfc] draft-qui=
nn-sfc-nsh: version number</span><o:p></o:p></h1>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"100%" align=3D"center">
</div>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto;mso-list:l1 level1 lfo2">
<em><span style=3D"font-family:&quot;Calibri&quot;,sans-serif">From</span><=
/em>: &quot;Paul Quinn (paulq)&quot; &lt;<a href=3D"mailto:paulq@DOMAIN.HID=
DEN">paulq at cisco.com</a>&gt;<o:p></o:p></li><li class=3D"MsoNormal" styl=
e=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 =
lfo2">
<em><span style=3D"font-family:&quot;Calibri&quot;,sans-serif">To</span></e=
m>: &quot;Joel M. Halpern&quot; &lt;<a href=3D"mailto:jmh@DOMAIN.HIDDEN">jm=
h at joelhalpern.com</a>&gt;<o:p></o:p></li><li class=3D"MsoNormal" style=
=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 l=
fo2">
<em><span style=3D"font-family:&quot;Calibri&quot;,sans-serif">Cc</span></e=
m>: &quot;<a href=3D"mailto:mohamed.boucadair@DOMAIN.HIDDEN">mohamed.boucad=
air at orange.com</a>&quot; &lt;<a href=3D"mailto:mohamed.boucadair@DOMAIN.=
HIDDEN">mohamed.boucadair at orange.com</a>&gt;, &quot;<a href=3D"mailto:sf=
c@DOMAIN.HIDDEN">sfc
 at ietf.org</a>&quot; &lt;<a href=3D"mailto:sfc@DOMAIN.HIDDEN">sfc at ietf=
.org</a>&gt;<o:p></o:p></li><li class=3D"MsoNormal" style=3D"mso-margin-top=
-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo2">
<em><span style=3D"font-family:&quot;Calibri&quot;,sans-serif">Date</span><=
/em>: Mon, 2 Mar 2015 17:50:53 &#43;0000<o:p></o:p></li><li class=3D"MsoNor=
mal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l=
1 level1 lfo2">
<em><span style=3D"font-family:&quot;Calibri&quot;,sans-serif">In-reply-to<=
/span></em>: &lt;<a href=3D"http://www.ietf.org/mail-archive/web/sfc/curren=
t/msg03181.html">54EF2C9A.3040008@joelhalpern.com</a>&gt;<o:p></o:p></li><l=
i class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al=
t:auto;mso-list:l1 level1 lfo2">
<em><span style=3D"font-family:&quot;Calibri&quot;,sans-serif">References</=
span></em>: &lt;<a href=3D"mailto:787AE7BB302AE849A7480A190F8B9330049140B4@=
OPEXCLILM23.corporate.adroot.infra.ftgroup">787AE7BB302AE849A7480A190F8B933=
0049140B4@OPEXCLILM23.corporate.adroot.infra.ftgroup</a>&gt;
 &lt;<a href=3D"http://www.ietf.org/mail-archive/web/sfc/current/msg03151.h=
tml">54EDE5B7.6080102@joelhalpern.com</a>&gt; &lt;<a href=3D"mailto:787AE7B=
B302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.adroot.infra.ftgrou=
p">787AE7BB302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.adroot.in=
fra.ftgroup</a>&gt;
 &lt;<a href=3D"http://www.ietf.org/mail-archive/web/sfc/current/msg03181.h=
tml">54EF2C9A.3040008@joelhalpern.com</a>&gt;<o:p></o:p></li><li class=3D"M=
soNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-l=
ist:l1 level1 lfo2">
<em><span style=3D"font-family:&quot;Calibri&quot;,sans-serif">List-id</spa=
n></em>: Network Service Chaining &lt;sfc.ietf.org&gt;<o:p></o:p></li></ul>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"100%" align=3D"center">
</div>
<pre>Hi,<o:p></o:p></pre>
<pre>&nbsp;<o:p></o:p></pre>
<pre>Jumping in mid-thread.&nbsp; <o:p></o:p></pre>
<pre>&nbsp;<o:p></o:p></pre>
<pre>Overall, I tend to agree with Joel.&nbsp; Having an explicit version p=
rovides a simple way to handle dataplane format changes.&nbsp; As Med point=
s out, quickly correctly, IMHO, there are other way to signal changes via r=
eserved bit.&nbsp; In practice though reserved bits are less useful since t=
he convention is to ignore unknown bits, it makes using them for feature ch=
anges quite difficult, which then brings up back to explicit versioning tha=
t cannot be ignored.&nbsp; <o:p></o:p></pre>
<pre>&nbsp;<o:p></o:p></pre>
<pre>I think Joel&#8217;s suggestion below makes perfect sense and should b=
e added to the draft.<o:p></o:p></pre>
<pre>&nbsp;<o:p></o:p></pre>
<pre>Paul<o:p></o:p></pre>
<pre>&nbsp;<o:p></o:p></pre>
<pre>&nbsp;<o:p></o:p></pre>
<pre>&gt; On Feb 26, 2015, at 9:24 AM, Joel M. Halpern &lt;jmh at joelhalpe=
rn.com&gt; wrote:<o:p></o:p></pre>
<pre>&gt; <o:p></o:p></pre>
<pre>&gt; In one sense you are correct.&nbsp; If you could count on everyth=
ing being upgraded at once, sure you could just assume common interpretatio=
n.<o:p></o:p></pre>
<pre>&gt; However, we have found over the years that such simultaneous upgr=
ading never works.&nbsp; You need to be able to transition.<o:p></o:p></pre=
>
<pre>&gt; <o:p></o:p></pre>
<pre>&gt; I do agree that we should add text about what to do with version =
numbers that are not understood.&nbsp; There are multiple choices that affe=
ct how we can make changes.&nbsp; My personal preference is:<o:p></o:p></pr=
e>
<pre>&gt; <o:p></o:p></pre>
<pre>&gt; If an packet presumed to carry an NSH header is received at an SF=
F, and the SFF does not understnad the version of the protocol as indicated=
 in the base header, the packet MUST be discarded, and the event SHOULD be =
logged.<o:p></o:p></pre>
<pre>&gt; <o:p></o:p></pre>
<pre>&gt; This would allow an orderly transition, where devices can be upgr=
aded to understand a new version, then generation of the new version header=
 can be enabled.&nbsp; If a configuration error is made, the packets will b=
e dropped and operators following good practices will get notifications.<o:=
p></o:p></pre>
<pre>&gt; <o:p></o:p></pre>
<pre>&gt; Yours,<o:p></o:p></pre>
<pre>&gt; Joel<o:p></o:p></pre>
<pre>&gt; <o:p></o:p></pre>
<pre>&gt; On 2/26/15 2:16 AM, mohamed.boucadair at orange.com wrote:<o:p></=
o:p></pre>
<pre>&gt;&gt; Hi Joel,<o:p></o:p></pre>
<pre>&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt; I fully agree with the extendibility of the header, but the q=
uestion is why having a version number will be of help in the context of SF=
C? Second, having a version number without specifying the behavior when sev=
eral versions are supported, when the version number is not supported by an=
 SFC-aware element, etc. leaves open issues out of the spec.<o:p></o:p></pr=
e>
<pre>&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt; The other problem is that the current I-D includes several op=
en doors left for extending the header:<o:p></o:p></pre>
<pre>&gt;&gt; * version<o:p></o:p></pre>
<pre>&gt;&gt; * reserved bits<o:p></o:p></pre>
<pre>&gt;&gt; * optional data<o:p></o:p></pre>
<pre>&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt; This is too much for a header that is supposed to be compact =
and simple!<o:p></o:p></pre>
<pre>&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt; There are other means to extend the header without signaling =
the version in the packet. Having a distinct RFC number may be just fine in=
 the context of an unidirectional stream such as SFC.<o:p></o:p></pre>
<pre>&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt; Let us consider the situation where a version number is not e=
xplicitly signaled in the packet (but a new RFC updates the base SFC header=
). Several options can be considered, indeed (those are provided as example=
s for illustration purposes):<o:p></o:p></pre>
<pre>&gt;&gt; * An operator can make sure that its SFC-enabled domain is co=
nfigured in a consistent manner to support one and only one version of the =
header. No interoperability issues is encountered in this case.<o:p></o:p><=
/pre>
<pre>&gt;&gt; * An operator that wants to upgrade its SFC-enabled domain to=
 support a new specification of the SFC header: An operator can decide to p=
roceed to a software/hardware updates but can maintain the old header in op=
eration until all involved elements are upgraded to support the new version=
. Once the SFC-enabled domain is upgraded, then the new header can be enabl=
ed.<o:p></o:p></pre>
<pre>&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt; Let's consider now that a version is signaled in the packet: =
to what extent signaling this information simplifies the SFC operations, an=
d whether it increases/decreases the serviceability of an SFC-enabled domai=
n? Let's also assess to what extent having the version number add more comp=
lexity in the SFC header treatment when several versions are supported by a=
 node/within an SFC enabled domain? How it helps interoperability? Some poi=
nts for discussion are elaborated below:<o:p></o:p></pre>
<pre>&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt; * If the SFC-enabled domain is configured to support the same=
 version (which is likely): having the version number is not of any help.<o=
:p></o:p></pre>
<pre>&gt;&gt; * If the SFC-enabled domain involves some nodes that support =
version (v1) while others support (v2) (simple case): If these version are =
not backward compatible, this will lead to failures when two adjacent eleme=
nts in a service chain do not support the same version. The SFC system is b=
roken. Having the version number is not of any help in this case.<o:p></o:p=
></pre>
<pre>&gt;&gt; * If the SFC-enabled domain involves some nodes that support =
version (v1) while others support (v1 and v2):<o:p></o:p></pre>
<pre>&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt; (a) The nodes that support both v1 and v2 should be instructe=
d to decide which version to be used. This can be either part of the specif=
ication or be driven by configuration. If a version number is included in t=
he spec, I would expect to clarify the behavior in such case.<o:p></o:p></p=
re>
<pre>&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt; (b) Suppose a node that supports only v1 receives a packet wi=
th header (v2): If this node does not support a notification procedure to i=
nform the source that it does not support that header version, then FAILURE=
S are introduced in the network. This is a degradation of the service compa=
red to legacy scheme to structure services. This is not recommended, IMHO.<=
o:p></o:p></pre>
<pre>&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt; (c) If a notification is received from an element about its s=
upported version: a node can use another version (the logic to select other=
 version is another point to discuss) for that communication, but what to d=
o for the next flows in the context of the same service chain or other chai=
ns that involves these two nodes as adjacent elements in the same chain? Sh=
ouldn't these nodes cache the version to use for subsequent exchange to avo=
id receiving the notification error each time? Wouldn't that complexity the=
 behavior of the SFC-aware elements?<o:p></o:p></pre>
<pre>&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt; (d) If a notification is received from an element about its s=
upported version: As this may occurs in various segments of a given service=
 chain, e.g., (A(v1), B(v1,v2), C(v2), D(v1,v2), E(v1)). Notifying the adja=
cent node each time there is a version mismatch induce an extra delay, that=
 may be not be acceptable for every flow.<o:p></o:p></pre>
<pre>&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt; I hope this clarifies my initial concern.<o:p></o:p></pre>
<pre>&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt; Thank you.<o:p></o:p></pre>
<pre>&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt; Cheers,<o:p></o:p></pre>
<pre>&gt;&gt; Med<o:p></o:p></pre>
<pre>&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt;&gt; -----Message d'origine-----<o:p></o:p></pre>
<pre>&gt;&gt;&gt; De : Joel M. Halpern [<a href=3D"mailto:jmh">mailto:jmh</=
a> at joelhalpern.com]<o:p></o:p></pre>
<pre>&gt;&gt;&gt; Envoy=E9 : mercredi 25 f=E9vrier 2015 16:10<o:p></o:p></p=
re>
<pre>&gt;&gt;&gt; =C0 : BOUCADAIR Mohamed IMT/OLN; paulq at cisco.com<o:p><=
/o:p></pre>
<pre>&gt;&gt;&gt; Cc : sfc at ietf.org<o:p></o:p></pre>
<pre>&gt;&gt;&gt; Objet : Re: [sfc] draft-quinn-sfc-nsh: version number<o:p=
></o:p></pre>
<pre>&gt;&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt;&gt; I would really prefer to keep the version number.&nbsp; E=
ven though we have<o:p></o:p></pre>
<pre>&gt;&gt;&gt; the MD-type identifier and for some MD we have the TLVs.<=
o:p></o:p></pre>
<pre>&gt;&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt;&gt; The reason is that we may want to change the base header.=
&nbsp; For example,<o:p></o:p></pre>
<pre>&gt;&gt;&gt; suppose that the ciscussion about including a flow identi=
fier in the<o:p></o:p></pre>
<pre>&gt;&gt;&gt; base header had not come up now.&nbsp; If it came up late=
r, we would want to<o:p></o:p></pre>
<pre>&gt;&gt;&gt; be able to have the discussion and make the choice, rathe=
r than being<o:p></o:p></pre>
<pre>&gt;&gt;&gt; constrained by the lack of a version field.<o:p></o:p></p=
re>
<pre>&gt;&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt;&gt; Yours,<o:p></o:p></pre>
<pre>&gt;&gt;&gt; Joel<o:p></o:p></pre>
<pre>&gt;&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt;&gt; On 2/25/15 10:03 AM, mohamed.boucadair at orange.com wrot=
e:<o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; Hi Paul, all,<o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; What is the purpose of having a version number in the=
 header? Is there a<o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; kind of version negotiation that needs to be in place=
?<o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; I checked the I-D but failed to find text that explai=
ns the rationale,<o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; the use of the such field and whether an error will b=
e returned if the<o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; version is not supported by the receiving node.<o:p><=
/o:p></pre>
<pre>&gt;&gt;&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; Wouldn't be preferable to get rid of this field given=
 that SFC header<o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; can be extended using optional objects and consistent=
 setup &amp;<o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; configuration within an SFC-enabled domain should be =
assumed?<o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; Thank you<o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; Cheers,<o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; Med<o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; _______________________________________________<o:p><=
/o:p></pre>
<pre>&gt;&gt;&gt;&gt; sfc mailing list<o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; sfc at ietf.org<o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/sfc"=
>https://www.ietf.org/mailman/listinfo/sfc</a><o:p></o:p></pre>
<pre>&gt;&gt;&gt;&gt; <o:p></o:p></pre>
<pre>&gt;&gt; <o:p></o:p></pre>
<pre>&nbsp;<o:p></o:p></pre>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_569e5fda6aa0486aaa7ff1853ed85576SEAEXCHMBX05olympusF5Ne_--


From nobody Tue Mar  3 11:50:19 2015
Return-Path: <sunilvk@f5.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECAF91A8855 for <sfc@ietfa.amsl.com>; Tue,  3 Mar 2015 11:50:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level: 
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 bXLUrZqjfTlS for <sfc@ietfa.amsl.com>; Tue,  3 Mar 2015 11:50:16 -0800 (PST)
Received: from mail.f5.com (mail.f5.com [208.85.209.139]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 846ED1A8865 for <sfc@ietf.org>; Tue,  3 Mar 2015 11:50:16 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.09,683,1418083200";  d="scan'208,217";a="151641168"
X-IPAS-Result: A2CmBAAKEPZU/+sKqMBagj+BFV7BN4d5AQEBAQEBfIQQBi1eAQh4JgEEG95VDAEfixKJIAWNfJ8lgiUcgVCCM38BAQE
Received: from oracle-apps.f5net.com (HELO exchmail.f5net.com) ([192.168.10.235]) by mail.f5.com with ESMTP/TLS/AES256-SHA; 03 Mar 2015 19:50:17 +0000
Received: from SEAEXCHMBX06.olympus.F5Net.com (192.168.15.49) by seaexchmbx01.olympus.F5Net.com (192.168.15.223) with Microsoft SMTP Server (TLS) id 15.0.1044.25; Tue, 3 Mar 2015 11:50:15 -0800
Received: from SEAEXCHMBX05.olympus.F5Net.com (192.168.15.227) by SEAEXCHMBX06.olympus.F5Net.com (192.168.15.49) with Microsoft SMTP Server (TLS) id 15.0.1044.25; Tue, 3 Mar 2015 11:50:15 -0800
Received: from SEAEXCHMBX05.olympus.F5Net.com ([fe80::9cc0:5dc7:726d:3b50]) by SEAEXCHMBX05.olympus.F5Net.com ([fe80::9cc0:5dc7:726d:3b50%21]) with mapi id 15.00.1044.021; Tue, 3 Mar 2015 11:50:15 -0800
From: Sunil Vallamkonda <sunilvk@f5.com>
To: "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: draft-quinn-sfc-nsh: version number
Thread-Index: AdBV6zYtUqmnkfKISViAGHEhNWXS1w==
Date: Tue, 3 Mar 2015 19:50:14 +0000
Message-ID: <9ef52ae35391409eb47d1c032406822d@SEAEXCHMBX05.olympus.F5Net.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.168.15.239]
Content-Type: multipart/alternative; boundary="_000_9ef52ae35391409eb47d1c032406822dSEAEXCHMBX05olympusF5Ne_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/eYyxmqcbvTm5KG6YeZCzkjKts50>
Subject: Re: [sfc] draft-quinn-sfc-nsh: version number
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 03 Mar 2015 19:50:18 -0000

--_000_9ef52ae35391409eb47d1c032406822dSEAEXCHMBX05olympusF5Ne_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

Just going through the thread on version number (jumping in mid-thread),

Apart from the version mismatched (unsupported) packet dropped and logged, =
is there a plan for a back off mechanism by SFF to notify sender and avoid =
being overwhelmed with such packets ?

Thank you,
Sunil.




--_000_9ef52ae35391409eb47d1c032406822dSEAEXCHMBX05olympusF5Ne_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
h1
	{mso-style-priority:9;
	mso-style-link:"Heading 1 Char";
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:24.0pt;
	font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.Heading1Char
	{mso-style-name:"Heading 1 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 1";
	font-family:"Times New Roman",serif;
	font-weight:bold;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1031541194;
	mso-list-template-ids:1700672388;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1
	{mso-list-id:1172985525;
	mso-list-template-ids:1467404642;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Just going through the thread on version number (jum=
ping in mid-thread),<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Apart from the version mismatched (unsupported) pack=
et dropped and logged, is there a plan for a back off mechanism by SFF to n=
otify sender and avoid being overwhelmed with such packets ?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thank you,<o:p></o:p></p>
<p class=3D"MsoNormal">Sunil.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_9ef52ae35391409eb47d1c032406822dSEAEXCHMBX05olympusF5Ne_--


From nobody Tue Mar  3 19:30:51 2015
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F6E01A0145; Tue,  3 Mar 2015 19:30:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 gwj31IW6wMTB; Tue,  3 Mar 2015 19:30:48 -0800 (PST)
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 048A51A0122; Tue,  3 Mar 2015 19:30:47 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BTG07393; Wed, 04 Mar 2015 03:30:46 +0000 (GMT)
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 4 Mar 2015 03:30:46 +0000
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.115]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.03.0158.001; Wed, 4 Mar 2015 11:30:41 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: "sfc@ietf.org" <sfc@ietf.org>, "<spring@ietf.org>" <spring@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
Thread-Topic: New Version Notification for draft-xu-sfc-using-mpls-spring-02.txt
Thread-Index: AQHQViqf+3y6NXpdeEGpQGeCsEhFG50LqPsA
Date: Wed, 4 Mar 2015 03:30:40 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0830F7A4@NKGEML512-MBS.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.99.55]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/PS6YmJrgNzZXBJ7nhefKK16ZZUY>
Subject: [sfc] FW: New Version Notification for draft-xu-sfc-using-mpls-spring-02.txt
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 04 Mar 2015 03:30:50 -0000

SGkgYWxsLA0KDQpUaGlzIGRvY3VtZW50IGRlc2NyaWJlcyBob3cgdG8gbGV2ZXJhZ2UgdGhlIE1Q
TFMtYmFzZWQgc291cmNlIHJvdXRpbmcgKGkuZS4sIE1QTFMtU1BSSU5HKSBtZWNoYW5pc20gYXMg
ZGV2ZWxvcGVkIGJ5IHRoZSBTUFJJTkcgV0cgdG8gcmVhbGl6ZSB0aGUgc2VydmljZSBwYXRoIGxh
eWVyIGZ1bmN0aW9uYWxpdHkgb2YgdGhlIHNlcnZpY2UgZnVuY3Rpb24gY2hhaW5pbmcuIEluIGFk
ZGl0aW9uLCB0aGlzIGRvY3VtZW50IGFsc28gZGVzY3JpYmVzIGhvdyB0byBjYXJyeSBtZXRhZGF0
YSBpbiBhbiBNUExTIHBhY2tldCBieSB1c2luZyB0aGUgTlNIIGFzIGEgbWV0YWRhdGEgY29udGFp
bmVyLiANCg0KQW55IGNvbW1lbnRzIGFyZSBzdWdnZXN0aW9ucyBhcmUgd2VsY29tZS4NCg0KQmVz
dCByZWdhcmRzLA0KWGlhb2h1DQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJv
bTogaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnIFttYWlsdG86aW50ZXJuZXQtZHJhZnRzQGlldGYu
b3JnXQ0KPiBTZW50OiBXZWRuZXNkYXksIE1hcmNoIDA0LCAyMDE1IDExOjI0IEFNDQo+IFRvOiBM
aXpoZW5iaW47IEx1aXMgTS4gQ29udHJlcmFzOyBYdXhpYW9odTsgSGltYW5zaHUgQy4gU2hhaDsg
WHV4aWFvaHU7DQo+IEhpbWFuc2h1IFNoYWg7IEx1aXMgTS4gQ29udHJlcmFzOyBMaXpoZW5iaW4N
Cj4gU3ViamVjdDogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC14dS1zZmMtdXNp
bmctbXBscy1zcHJpbmctMDIudHh0DQo+IA0KPiANCj4gQSBuZXcgdmVyc2lvbiBvZiBJLUQsIGRy
YWZ0LXh1LXNmYy11c2luZy1tcGxzLXNwcmluZy0wMi50eHQNCj4gaGFzIGJlZW4gc3VjY2Vzc2Z1
bGx5IHN1Ym1pdHRlZCBieSBYaWFvaHUgWHUgYW5kIHBvc3RlZCB0byB0aGUgSUVURiByZXBvc2l0
b3J5Lg0KPiANCj4gTmFtZToJCWRyYWZ0LXh1LXNmYy11c2luZy1tcGxzLXNwcmluZw0KPiBSZXZp
c2lvbjoJMDINCj4gVGl0bGU6CQlTZXJ2aWNlIEZ1bmN0aW9uIENoYWluaW5nIFVzaW5nIE1QTFMt
U1BSSU5HDQo+IERvY3VtZW50IGRhdGU6CTIwMTUtMDMtMDMNCj4gR3JvdXA6CQlJbmRpdmlkdWFs
IFN1Ym1pc3Npb24NCj4gUGFnZXM6CQk4DQo+IFVSTDoNCj4gaHR0cDovL3d3dy5pZXRmLm9yZy9p
bnRlcm5ldC1kcmFmdHMvZHJhZnQteHUtc2ZjLXVzaW5nLW1wbHMtc3ByaW5nLTAyLnR4dA0KPiBT
dGF0dXM6DQo+IGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LXh1LXNmYy11
c2luZy1tcGxzLXNwcmluZy8NCj4gSHRtbGl6ZWQ6ICAgICAgIGh0dHA6Ly90b29scy5pZXRmLm9y
Zy9odG1sL2RyYWZ0LXh1LXNmYy11c2luZy1tcGxzLXNwcmluZy0wMg0KPiBEaWZmOg0KPiBodHRw
Oi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJsMj1kcmFmdC14dS1zZmMtdXNpbmctbXBscy1zcHJp
bmctMDINCj4gDQo+IEFic3RyYWN0Og0KPiAgICBTb3VyY2UgUGFja2V0IFJvdXRpbmcgaW4gTmV0
d29ya2luZyAoU1BSSU5HKSBXRyBzcGVjaWZpZXMgYSBzcGVjaWFsDQo+ICAgIHNvdXJjZSByb3V0
aW5nIG1lY2hhbmlzbS4gIFN1Y2ggc291cmNlIHJvdXRpbmcgbWVjaGFuaXNtIGNhbiBiZQ0KPiAg
ICBsZXZlcmFnZWQgdG8gcmVhbGl6ZSB0aGUgc2VydmljZSBwYXRoIGxheWVyIGZ1bmN0aW9uYWxp
dHkgb2YgdGhlDQo+ICAgIHNlcnZpY2UgZnVuY3Rpb24gY2hhaW5pbmcgKGkuZSwgc3RlZXJpbmcg
dHJhZmZpYyB0aHJvdWdoIGEgcGFydGljdWxhcg0KPiAgICBzZXJ2aWNlIGZ1bmN0aW9uIHBhdGgp
IGJ5IGVuY29kaW5nIHRoZSBzZXJ2aWNlIGZ1bmN0aW9uIHBhdGggb3IgdGhlDQo+ICAgIHNlcnZp
Y2UgZnVuY3Rpb24gY2hhaW4gaW5mb3JtYXRpb24gYXMgdGhlIGV4cGxpY2l0IHBhdGggaW5mb3Jt
YXRpb24uDQo+ICAgIFRoaXMgZG9jdW1lbnQgZGVzY3JpYmVzIGhvdyB0byBsZXZlcmFnZSB0aGUg
TVBMUy1iYXNlZCBzb3VyY2Ugcm91dGluZw0KPiAgICBtZWNoYW5pc20gYXMgZGV2ZWxvcGVkIGJ5
IHRoZSBTUFJJTkcgV0cgdG8gcmVhbGl6ZSB0aGUgc2VydmljZSBwYXRoDQo+ICAgIGxheWVyIGZ1
bmN0aW9uYWxpdHkgb2YgdGhlIHNlcnZpY2UgZnVuY3Rpb24gY2hhaW5pbmcuDQo+IA0KPiANCj4g
DQo+IA0KPiBQbGVhc2Ugbm90ZSB0aGF0IGl0IG1heSB0YWtlIGEgY291cGxlIG9mIG1pbnV0ZXMg
ZnJvbSB0aGUgdGltZSBvZiBzdWJtaXNzaW9uDQo+IHVudGlsIHRoZSBodG1saXplZCB2ZXJzaW9u
IGFuZCBkaWZmIGFyZSBhdmFpbGFibGUgYXQgdG9vbHMuaWV0Zi5vcmcuDQo+IA0KPiBUaGUgSUVU
RiBTZWNyZXRhcmlhdA0KDQo=


From nobody Tue Mar  3 20:10:33 2015
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E87891A01EC; Tue,  3 Mar 2015 20:10:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 nGeyIWREZhFt; Tue,  3 Mar 2015 20:10:30 -0800 (PST)
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 67B221A017F; Tue,  3 Mar 2015 20:10:29 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BPW03831; Wed, 04 Mar 2015 04:10:27 +0000 (GMT)
Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 4 Mar 2015 04:10:26 +0000
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.115]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.03.0158.001; Wed, 4 Mar 2015 12:10:14 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Xuxiaohu <xuxiaohu@huawei.com>, "sfc@ietf.org" <sfc@ietf.org>, "<spring@ietf.org>" <spring@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
Thread-Topic: New Version Notification for draft-xu-sfc-using-mpls-spring-02.txt
Thread-Index: AQHQViqf+3y6NXpdeEGpQGeCsEhFG50LqPsAgAAGTiA=
Date: Wed, 4 Mar 2015 04:10:13 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0830F7C0@NKGEML512-MBS.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.99.55]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/jRu7GyhS-KgTvWz_KOE9_5MPxnY>
Subject: Re: [sfc] New Version Notification for draft-xu-sfc-using-mpls-spring-02.txt
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 04 Mar 2015 04:10:32 -0000

VGhlIHJhdGlvbmFsZXMgZm9yIGxldmVyYWdpbmcgdGhlIE1QTFMtU1BSSU5HIG1lY2hhbmlzbSB0
byByZWFsaXplIHRoZSBzZXJ2aWNlIHBhdGggbGF5ZXIgZnVuY3Rpb25hbGl0eSBvZiB0aGUgc2Vy
dmljZSBmdW5jdGlvbiBjaGFpbmluZyBhcmUgYXMgZm9sbG93czoNCg0KMSkgZWxpbWluYXRlIHRo
ZSBTRkMvU0ZQIHN0YXRlcyBvbiBTRkZzLiBUaGlzIGZvbGxvd3MgdGhlIHNhbWUgbG9naWMgYXMg
TVBMUy1TUFJJTkcgYW5kIEJJRVIuDQoyKSB1dGlsaXplIHRoZSBleGlzdGluZyBlbmNhcHN1bGF0
aW9uIChlLmcuLCB0aGUgTVBMUy1TUFJJTkcpIHRvIGEgbWF4aW11bSBleHRlbnQuIFRoaXMgZm9s
bG93cyB0aGUgVHJhbnNwb3J0IERlcml2ZWQgU0ZGIGNvbmNlcHQgYXMgZGVzY3JpYmVkIGluIFNl
Y3Rpb24gNC4zLjEgb2YgZHJhZnQtaWV0Zi1zZmMtYXJjaGl0ZWN0dXJlLiBNZWFud2hpbGUsIHRo
aXMgaXMgYWxpZ25lZCB3aXRoIHRoZSBjdXJyZW50IFNGQyBjaGFydGVyLCBlLmcuLCAiLi4uVGhl
IHdvcmtpbmcgZ3JvdXAgd2lsbCBjb25zaWRlciB1c2luZyBhbiBleGlzdGluZyBlbmNhcHN1bGF0
aW9uICh3aXRoIGV4dGVuc2lvbnMgYXMgYXBwcm9wcmlhdGUpIGlmIGEgc3VpdGFibGUgY2FuZGlk
YXRlIGlzIGZvdW5kLi4uIg0KMykgc2VhbWxlc3NseSBzdXBwb3J0IHRoZSBTRkMgaW4gYSBtdWx0
aS10ZW5hbnQgZW52aXJvbm1lbnQgKGUuZy4sIE1QTFMgVlBOKS4gRm9yIGV4YW1wbGUsIHRoZSBN
UExTIFZQTiBwYWNrZXQgKGNvbnRhaW5pbmcgbWV0YWRhdGEpIGNvdWxkIGJlIGZ1cnRoZXIgaW1w
b3NlZCB3aXRoIGEgbGFiZWwgc3RhY2sgd2hpY2ggaW5kaWNhdGVzIGFuIFNGQyBvciBTRlAgYXNz
b2NpYXRlZCB3aXRoIHRoYXQgcGFja2V0LiBTRkZzIHJlY2VpdmluZyB0aGUgYWJvdmUgcGFja2V0
IHdvdWxkIHN0cmlwIHRoZSB3aG9sZSBsYWJlbCBzdGFjayBhbmQgdGhlbiBzZW5kIHRoZSBwYXls
b2FkIG9mIHRoZSBNUExTIHBhY2tldCAod2l0aCBtZXRhZGF0YSkgdG8gdGhlIGNvcnJlc3BvbmRp
bmcgU0ZzIHdoaWNoIGFyZSB0ZW5hbnQtYXdhcmUgYW5kIHRoZXJlZm9yZSBlYXNpbHkgY291bGQg
ZGV0ZXJtaW5lIHRoZSB0ZW5hbnQgcHJvZmlsZSBhY2NvcmRpbmcgdG8gdGhlIHRlbmFudCBpbmZv
IGNvbnRhaW5lZCBpbiB0aGUgbWV0YWRhdGEgKGEuay5hLiwgdGhlIE5TSCkuIA0KDQpCZXN0IHJl
Z2FyZHMsDQpYaWFvaHUNCiANCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9t
OiBYdXhpYW9odQ0KPiBTZW50OiBXZWRuZXNkYXksIE1hcmNoIDA0LCAyMDE1IDExOjMxIEFNDQo+
IFRvOiBzZmNAaWV0Zi5vcmc7ICc8c3ByaW5nQGlldGYub3JnPic7IG1wbHNAaWV0Zi5vcmcNCj4g
U3ViamVjdDogRlc6IE5ldyBWZXJzaW9uIE5vdGlmaWNhdGlvbiBmb3IgZHJhZnQteHUtc2ZjLXVz
aW5nLW1wbHMtc3ByaW5nLTAyLnR4dA0KPiANCj4gSGkgYWxsLA0KPiANCj4gVGhpcyBkb2N1bWVu
dCBkZXNjcmliZXMgaG93IHRvIGxldmVyYWdlIHRoZSBNUExTLWJhc2VkIHNvdXJjZSByb3V0aW5n
IChpLmUuLA0KPiBNUExTLVNQUklORykgbWVjaGFuaXNtIGFzIGRldmVsb3BlZCBieSB0aGUgU1BS
SU5HIFdHIHRvIHJlYWxpemUgdGhlDQo+IHNlcnZpY2UgcGF0aCBsYXllciBmdW5jdGlvbmFsaXR5
IG9mIHRoZSBzZXJ2aWNlIGZ1bmN0aW9uIGNoYWluaW5nLiBJbiBhZGRpdGlvbiwgdGhpcw0KPiBk
b2N1bWVudCBhbHNvIGRlc2NyaWJlcyBob3cgdG8gY2FycnkgbWV0YWRhdGEgaW4gYW4gTVBMUyBw
YWNrZXQgYnkgdXNpbmcgdGhlDQo+IE5TSCBhcyBhIG1ldGFkYXRhIGNvbnRhaW5lci4NCj4gDQo+
IEFueSBjb21tZW50cyBhcmUgc3VnZ2VzdGlvbnMgYXJlIHdlbGNvbWUuDQo+IA0KPiBCZXN0IHJl
Z2FyZHMsDQo+IFhpYW9odQ0KPiANCj4gPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiA+
IEZyb206IGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZyBbbWFpbHRvOmludGVybmV0LWRyYWZ0c0Bp
ZXRmLm9yZ10NCj4gPiBTZW50OiBXZWRuZXNkYXksIE1hcmNoIDA0LCAyMDE1IDExOjI0IEFNDQo+
ID4gVG86IExpemhlbmJpbjsgTHVpcyBNLiBDb250cmVyYXM7IFh1eGlhb2h1OyBIaW1hbnNodSBD
LiBTaGFoOw0KPiA+IFh1eGlhb2h1OyBIaW1hbnNodSBTaGFoOyBMdWlzIE0uIENvbnRyZXJhczsg
TGl6aGVuYmluDQo+ID4gU3ViamVjdDogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvcg0KPiA+
IGRyYWZ0LXh1LXNmYy11c2luZy1tcGxzLXNwcmluZy0wMi50eHQNCj4gPg0KPiA+DQo+ID4gQSBu
ZXcgdmVyc2lvbiBvZiBJLUQsIGRyYWZ0LXh1LXNmYy11c2luZy1tcGxzLXNwcmluZy0wMi50eHQN
Cj4gPiBoYXMgYmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5IFhpYW9odSBYdSBhbmQgcG9z
dGVkIHRvIHRoZSBJRVRGDQo+IHJlcG9zaXRvcnkuDQo+ID4NCj4gPiBOYW1lOgkJZHJhZnQteHUt
c2ZjLXVzaW5nLW1wbHMtc3ByaW5nDQo+ID4gUmV2aXNpb246CTAyDQo+ID4gVGl0bGU6CQlTZXJ2
aWNlIEZ1bmN0aW9uIENoYWluaW5nIFVzaW5nIE1QTFMtU1BSSU5HDQo+ID4gRG9jdW1lbnQgZGF0
ZToJMjAxNS0wMy0wMw0KPiA+IEdyb3VwOgkJSW5kaXZpZHVhbCBTdWJtaXNzaW9uDQo+ID4gUGFn
ZXM6CQk4DQo+ID4gVVJMOg0KPiA+IGh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRz
L2RyYWZ0LXh1LXNmYy11c2luZy1tcGxzLXNwcmluZy0wMi4NCj4gPiB0eHQNCj4gPiBTdGF0dXM6
DQo+ID4gaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQteHUtc2ZjLXVzaW5n
LW1wbHMtc3ByaW5nLw0KPiA+IEh0bWxpemVkOiAgICAgICBodHRwOi8vdG9vbHMuaWV0Zi5vcmcv
aHRtbC9kcmFmdC14dS1zZmMtdXNpbmctbXBscy1zcHJpbmctMDINCj4gPiBEaWZmOg0KPiA+IGh0
dHA6Ly93d3cuaWV0Zi5vcmcvcmZjZGlmZj91cmwyPWRyYWZ0LXh1LXNmYy11c2luZy1tcGxzLXNw
cmluZy0wMg0KPiA+DQo+ID4gQWJzdHJhY3Q6DQo+ID4gICAgU291cmNlIFBhY2tldCBSb3V0aW5n
IGluIE5ldHdvcmtpbmcgKFNQUklORykgV0cgc3BlY2lmaWVzIGEgc3BlY2lhbA0KPiA+ICAgIHNv
dXJjZSByb3V0aW5nIG1lY2hhbmlzbS4gIFN1Y2ggc291cmNlIHJvdXRpbmcgbWVjaGFuaXNtIGNh
biBiZQ0KPiA+ICAgIGxldmVyYWdlZCB0byByZWFsaXplIHRoZSBzZXJ2aWNlIHBhdGggbGF5ZXIg
ZnVuY3Rpb25hbGl0eSBvZiB0aGUNCj4gPiAgICBzZXJ2aWNlIGZ1bmN0aW9uIGNoYWluaW5nIChp
LmUsIHN0ZWVyaW5nIHRyYWZmaWMgdGhyb3VnaCBhIHBhcnRpY3VsYXINCj4gPiAgICBzZXJ2aWNl
IGZ1bmN0aW9uIHBhdGgpIGJ5IGVuY29kaW5nIHRoZSBzZXJ2aWNlIGZ1bmN0aW9uIHBhdGggb3Ig
dGhlDQo+ID4gICAgc2VydmljZSBmdW5jdGlvbiBjaGFpbiBpbmZvcm1hdGlvbiBhcyB0aGUgZXhw
bGljaXQgcGF0aCBpbmZvcm1hdGlvbi4NCj4gPiAgICBUaGlzIGRvY3VtZW50IGRlc2NyaWJlcyBo
b3cgdG8gbGV2ZXJhZ2UgdGhlIE1QTFMtYmFzZWQgc291cmNlIHJvdXRpbmcNCj4gPiAgICBtZWNo
YW5pc20gYXMgZGV2ZWxvcGVkIGJ5IHRoZSBTUFJJTkcgV0cgdG8gcmVhbGl6ZSB0aGUgc2Vydmlj
ZSBwYXRoDQo+ID4gICAgbGF5ZXIgZnVuY3Rpb25hbGl0eSBvZiB0aGUgc2VydmljZSBmdW5jdGlv
biBjaGFpbmluZy4NCj4gPg0KPiA+DQo+ID4NCj4gPg0KPiA+IFBsZWFzZSBub3RlIHRoYXQgaXQg
bWF5IHRha2UgYSBjb3VwbGUgb2YgbWludXRlcyBmcm9tIHRoZSB0aW1lIG9mDQo+ID4gc3VibWlz
c2lvbiB1bnRpbCB0aGUgaHRtbGl6ZWQgdmVyc2lvbiBhbmQgZGlmZiBhcmUgYXZhaWxhYmxlIGF0
IHRvb2xzLmlldGYub3JnLg0KPiA+DQo+ID4gVGhlIElFVEYgU2VjcmV0YXJpYXQNCg0K


From nobody Tue Mar  3 22:37:45 2015
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC4F91A00E9 for <sfc@ietfa.amsl.com>; Tue,  3 Mar 2015 22:37:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 BQc68lPgKVhj for <sfc@ietfa.amsl.com>; Tue,  3 Mar 2015 22:37:34 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 94B551A038E for <sfc@ietf.org>; Tue,  3 Mar 2015 22:37:33 -0800 (PST)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm12.si.francetelecom.fr (ESMTP service) with ESMTP id 4015718C335; Wed,  4 Mar 2015 07:37:30 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.30]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 1D3AB23807B; Wed,  4 Mar 2015 07:37:30 +0100 (CET)
Received: from OPEXCLILM23.corporate.adroot.infra.ftgroup ([169.254.2.231]) by OPEXCLILH02.corporate.adroot.infra.ftgroup ([10.114.31.30]) with mapi id 14.03.0224.002; Wed, 4 Mar 2015 07:37:30 +0100
From: <mohamed.boucadair@orange.com>
To: "Paul Quinn (paulq)" <paulq@cisco.com>, "Joel M. Halpern" <jmh@joelhalpern.com>
Thread-Topic: [sfc] draft-quinn-sfc-nsh: version number
Thread-Index: AdBRDDloSX0/55xiS1KsQav7+px1wQAMyamAACHBoQAADvQcAADQYBIAAEAyuoA=
Date: Wed, 4 Mar 2015 06:37:29 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933004919B15@OPEXCLILM23.corporate.adroot.infra.ftgroup>
References: <787AE7BB302AE849A7480A190F8B9330049140B4@OPEXCLILM23.corporate.adroot.infra.ftgroup> <54EDE5B7.6080102@joelhalpern.com> <787AE7BB302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.adroot.infra.ftgroup> <54EF2C9A.3040008@joelhalpern.com> <55A3CDAE-9D74-4174-AC1B-D3F500FABDCE@cisco.com>
In-Reply-To: <55A3CDAE-9D74-4174-AC1B-D3F500FABDCE@cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.1]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.12.16.112421
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/ftPfMaZ1b_eomX89BUBIXwGJK9E>
Cc: "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] draft-quinn-sfc-nsh: version number
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 04 Mar 2015 06:37:40 -0000

Hi Paul,

Issues related to co-existence and managing several versions of the header =
within a SFC-enabled domain won't disappear with aversion field. As I said =
in another message, many open doors are left in the current version of the =
draft for future extensions: version, optional elements, reserved bits, and=
 MD type. This is not optimal for a header that is supposed to be compact a=
s possible.

My initial concern is how to ensure the extendibility of the header while a=
voiding operational burden and avoid failures because of the header design =
choices.=20

In addition to the issue related to the version number side effects, there =
also failures that will be induced by the non-support of MD Type (note, I'm=
 not convinced yet MD type is needed)

Adding a sentence that says a packet will be dropped if the received node d=
oes not support that version is not sufficient. I listed several points in =
this thread that need to be addressed.=20

Thank you.

Cheers,
Med=20

> -----Message d'origine-----
> De=A0: Paul Quinn (paulq) [mailto:paulq@cisco.com]
> Envoy=E9=A0: lundi 2 mars 2015 18:51
> =C0=A0: Joel M. Halpern
> Cc=A0: BOUCADAIR Mohamed IMT/OLN; sfc@ietf.org
> Objet=A0: Re: [sfc] draft-quinn-sfc-nsh: version number
>=20
> Hi,
>=20
> Jumping in mid-thread.
>=20
> Overall, I tend to agree with Joel.  Having an explicit version provides =
a
> simple way to handle dataplane format changes.  As Med points out, quickl=
y
> correctly, IMHO, there are other way to signal changes via reserved bit.
> In practice though reserved bits are less useful since the convention is
> to ignore unknown bits, it makes using them for feature changes quite
> difficult, which then brings up back to explicit versioning that cannot b=
e
> ignored.
>=20
> I think Joel's suggestion below makes perfect sense and should be added t=
o
> the draft.
>=20
> Paul
>=20
>=20
> > On Feb 26, 2015, at 9:24 AM, Joel M. Halpern <jmh@joelhalpern.com>
> wrote:
> >
> > In one sense you are correct.  If you could count on everything being
> upgraded at once, sure you could just assume common interpretation.
> > However, we have found over the years that such simultaneous upgrading
> never works.  You need to be able to transition.
> >
> > I do agree that we should add text about what to do with version number=
s
> that are not understood.  There are multiple choices that affect how we
> can make changes.  My personal preference is:
> >
> > If an packet presumed to carry an NSH header is received at an SFF, and
> the SFF does not understnad the version of the protocol as indicated in
> the base header, the packet MUST be discarded, and the event SHOULD be
> logged.
> >
> > This would allow an orderly transition, where devices can be upgraded t=
o
> understand a new version, then generation of the new version header can b=
e
> enabled.  If a configuration error is made, the packets will be dropped
> and operators following good practices will get notifications.
> >
> > Yours,
> > Joel
> >
> > On 2/26/15 2:16 AM, mohamed.boucadair@orange.com wrote:
> >> Hi Joel,
> >>
> >> I fully agree with the extendibility of the header, but the question i=
s
> why having a version number will be of help in the context of SFC? Second=
,
> having a version number without specifying the behavior when several
> versions are supported, when the version number is not supported by an
> SFC-aware element, etc. leaves open issues out of the spec.
> >>
> >> The other problem is that the current I-D includes several open doors
> left for extending the header:
> >> * version
> >> * reserved bits
> >> * optional data
> >>
> >> This is too much for a header that is supposed to be compact and
> simple!
> >>
> >> There are other means to extend the header without signaling the
> version in the packet. Having a distinct RFC number may be just fine in
> the context of an unidirectional stream such as SFC.
> >>
> >> Let us consider the situation where a version number is not explicitly
> signaled in the packet (but a new RFC updates the base SFC header).
> Several options can be considered, indeed (those are provided as examples
> for illustration purposes):
> >> * An operator can make sure that its SFC-enabled domain is configured
> in a consistent manner to support one and only one version of the header.
> No interoperability issues is encountered in this case.
> >> * An operator that wants to upgrade its SFC-enabled domain to support =
a
> new specification of the SFC header: An operator can decide to proceed to
> a software/hardware updates but can maintain the old header in operation
> until all involved elements are upgraded to support the new version. Once
> the SFC-enabled domain is upgraded, then the new header can be enabled.
> >>
> >> Let's consider now that a version is signaled in the packet: to what
> extent signaling this information simplifies the SFC operations, and
> whether it increases/decreases the serviceability of an SFC-enabled
> domain? Let's also assess to what extent having the version number add
> more complexity in the SFC header treatment when several versions are
> supported by a node/within an SFC enabled domain? How it helps
> interoperability? Some points for discussion are elaborated below:
> >>
> >> * If the SFC-enabled domain is configured to support the same version
> (which is likely): having the version number is not of any help.
> >> * If the SFC-enabled domain involves some nodes that support version
> (v1) while others support (v2) (simple case): If these version are not
> backward compatible, this will lead to failures when two adjacent element=
s
> in a service chain do not support the same version. The SFC system is
> broken. Having the version number is not of any help in this case.
> >> * If the SFC-enabled domain involves some nodes that support version
> (v1) while others support (v1 and v2):
> >>
> >> (a) The nodes that support both v1 and v2 should be instructed to
> decide which version to be used. This can be either part of the
> specification or be driven by configuration. If a version number is
> included in the spec, I would expect to clarify the behavior in such case=
.
> >>
> >> (b) Suppose a node that supports only v1 receives a packet with header
> (v2): If this node does not support a notification procedure to inform th=
e
> source that it does not support that header version, then FAILURES are
> introduced in the network. This is a degradation of the service compared
> to legacy scheme to structure services. This is not recommended, IMHO.
> >>
> >> (c) If a notification is received from an element about its supported
> version: a node can use another version (the logic to select other versio=
n
> is another point to discuss) for that communication, but what to do for
> the next flows in the context of the same service chain or other chains
> that involves these two nodes as adjacent elements in the same chain?
> Shouldn't these nodes cache the version to use for subsequent exchange to
> avoid receiving the notification error each time? Wouldn't that complexit=
y
> the behavior of the SFC-aware elements?
> >>
> >> (d) If a notification is received from an element about its supported
> version: As this may occurs in various segments of a given service chain,
> e.g., (A(v1), B(v1,v2), C(v2), D(v1,v2), E(v1)). Notifying the adjacent
> node each time there is a version mismatch induce an extra delay, that ma=
y
> be not be acceptable for every flow.
> >>
> >> I hope this clarifies my initial concern.
> >>
> >> Thank you.
> >>
> >> Cheers,
> >> Med
> >>
> >>> -----Message d'origine-----
> >>> De : Joel M. Halpern [mailto:jmh@joelhalpern.com]
> >>> Envoy=E9 : mercredi 25 f=E9vrier 2015 16:10
> >>> =C0 : BOUCADAIR Mohamed IMT/OLN; paulq@cisco.com
> >>> Cc : sfc@ietf.org
> >>> Objet : Re: [sfc] draft-quinn-sfc-nsh: version number
> >>>
> >>> I would really prefer to keep the version number.  Even though we hav=
e
> >>> the MD-type identifier and for some MD we have the TLVs.
> >>>
> >>> The reason is that we may want to change the base header.  For
> example,
> >>> suppose that the ciscussion about including a flow identifier in the
> >>> base header had not come up now.  If it came up later, we would want
> to
> >>> be able to have the discussion and make the choice, rather than being
> >>> constrained by the lack of a version field.
> >>>
> >>> Yours,
> >>> Joel
> >>>
> >>>
> >>> On 2/25/15 10:03 AM, mohamed.boucadair@orange.com wrote:
> >>>> Hi Paul, all,
> >>>>
> >>>> What is the purpose of having a version number in the header? Is
> there a
> >>>> kind of version negotiation that needs to be in place?
> >>>>
> >>>> I checked the I-D but failed to find text that explains the
> rationale,
> >>>> the use of the such field and whether an error will be returned if
> the
> >>>> version is not supported by the receiving node.
> >>>>
> >>>> Wouldn't be preferable to get rid of this field given that SFC heade=
r
> >>>> can be extended using optional objects and consistent setup &
> >>>> configuration within an SFC-enabled domain should be assumed?
> >>>>
> >>>> Thank you
> >>>>
> >>>> Cheers,
> >>>>
> >>>> Med
> >>>>
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> sfc mailing list
> >>>> sfc@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/sfc
> >>>>
> >>


From nobody Tue Mar  3 22:46:50 2015
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9608C1A0163 for <sfc@ietfa.amsl.com>; Tue,  3 Mar 2015 22:46:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 XvvVQNiHjrp8 for <sfc@ietfa.amsl.com>; Tue,  3 Mar 2015 22:46:41 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C52C1A00DF for <sfc@ietf.org>; Tue,  3 Mar 2015 22:46:40 -0800 (PST)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm14.si.francetelecom.fr (ESMTP service) with ESMTP id B9C1922C20A; Wed,  4 Mar 2015 07:46:38 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.30]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 9BC4F4C108; Wed,  4 Mar 2015 07:46:38 +0100 (CET)
Received: from OPEXCLILM23.corporate.adroot.infra.ftgroup ([169.254.2.231]) by OPEXCLILH02.corporate.adroot.infra.ftgroup ([10.114.31.30]) with mapi id 14.03.0224.002; Wed, 4 Mar 2015 07:46:38 +0100
From: <mohamed.boucadair@orange.com>
To: Sunil Vallamkonda <sunilvk@f5.com>
Thread-Topic: Re: [sfc] draft-quinn-sfc-nsh: version number
Thread-Index: AdBV6VnhN9N2Adv/Rs2PZVkjw6sDlQAXRdTw
Date: Wed, 4 Mar 2015 06:46:37 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933004919B76@OPEXCLILM23.corporate.adroot.infra.ftgroup>
References: <01f9e1a4e6514854a26556e4c6a3e36e@SEAEXCHMBX05.olympus.F5Net.com>
In-Reply-To: <01f9e1a4e6514854a26556e4c6a3e36e@SEAEXCHMBX05.olympus.F5Net.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.1]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B933004919B76OPEXCLILM23corp_"
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.12.22.190922
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/rF1zQ4-zBc43TGDPg6A_V7qM5e8>
Cc: "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] draft-quinn-sfc-nsh: version number
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 04 Mar 2015 06:46:48 -0000

--_000_787AE7BB302AE849A7480A190F8B933004919B76OPEXCLILM23corp_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Sunil,

There is no such notification in the current spec.

Below my thoughts about this point:

=3D=3D

(b) Suppose a node that supports only v1 receives a packet with header (v2)=
: If this node does not support a notification procedure to inform the sour=
ce that it does not support that header version, then FAILURES are introduc=
ed in the network. This is a degradation of the service compared to legacy =
scheme to structure services. This is not recommended, IMHO.



(c) If a notification is received from an element about its supported versi=
on: a node can use another version (the logic to select other version is an=
other point to discuss) for that communication, but what to do for the next=
 flows in the context of the same service chain or other chains that involv=
es these two nodes as adjacent elements in the same chain? Shouldn't these =
nodes cache the version to use for subsequent exchange to avoid receiving t=
he notification error each time? Wouldn't that complexity the behavior of t=
he SFC-aware elements?



(d) If a notification is received from an element about its supported versi=
on: As this may occurs in various segments of a given service chain, e.g., =
(A(v1), B(v1,v2), C(v1), D(v1,v2), E(v1)). Notifying the adjacent node each=
 time there is a version mismatch induce an extra delay, that may be not be=
 acceptable for every flow.
=3D=3D

Thank you.

Cheers,
Med


De : sfc [mailto:sfc-bounces@ietf.org] De la part de Sunil Vallamkonda
Envoy=E9 : mardi 3 mars 2015 20:43
=C0 : sfc@ietf.org
Objet : Re: [sfc] draft-quinn-sfc-nsh: version number

Hi,

Just going through the thread on version number (jumping in mid-thread),

Apart from the version mismatched (unsupported) packet dropped and logged, =
is there a plan for a back off mechanism by SFF to notify sender and avoid =
being overwhelmed with such packets ?

Thank you,
Sunil.


Re: [sfc] draft-quinn-sfc-nsh: version number
________________________________

  *   From: "Paul Quinn (paulq)" <paulq at cisco.com<mailto:paulq@DOMAIN.HI=
DDEN>>
  *   To: "Joel M. Halpern" <jmh at joelhalpern.com<mailto:jmh@DOMAIN.HIDDE=
N>>
  *   Cc: "mohamed.boucadair at orange.com<mailto:mohamed.boucadair@DOMAIN.=
HIDDEN>" <mohamed.boucadair at orange.com<mailto:mohamed.boucadair@DOMAIN.H=
IDDEN>>, "sfc at ietf.org<mailto:sfc@DOMAIN.HIDDEN>" <sfc at ietf.org<mailt=
o:sfc@DOMAIN.HIDDEN>>
  *   Date: Mon, 2 Mar 2015 17:50:53 +0000
  *   In-reply-to: <54EF2C9A.3040008@joelhalpern.com<http://www.ietf.org/ma=
il-archive/web/sfc/current/msg03181.html>>
  *   References: <787AE7BB302AE849A7480A190F8B9330049140B4@OPEXCLILM23.cor=
porate.adroot.infra.ftgroup<mailto:787AE7BB302AE849A7480A190F8B9330049140B4=
@OPEXCLILM23.corporate.adroot.infra.ftgroup>> <54EDE5B7.6080102@joelhalpern=
.com<http://www.ietf.org/mail-archive/web/sfc/current/msg03151.html>> <787A=
E7BB302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.adroot.infra.ftg=
roup<mailto:787AE7BB302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.=
adroot.infra.ftgroup>> <54EF2C9A.3040008@joelhalpern.com<http://www.ietf.or=
g/mail-archive/web/sfc/current/msg03181.html>>
  *   List-id: Network Service Chaining <sfc.ietf.org>

________________________________

Hi,



Jumping in mid-thread.



Overall, I tend to agree with Joel.  Having an explicit version provides a =
simple way to handle dataplane format changes.  As Med points out, quickly =
correctly, IMHO, there are other way to signal changes via reserved bit.  I=
n practice though reserved bits are less useful since the convention is to =
ignore unknown bits, it makes using them for feature changes quite difficul=
t, which then brings up back to explicit versioning that cannot be ignored.



I think Joel's suggestion below makes perfect sense and should be added to =
the draft.



Paul





> On Feb 26, 2015, at 9:24 AM, Joel M. Halpern <jmh at joelhalpern.com> wro=
te:

>

> In one sense you are correct.  If you could count on everything being upg=
raded at once, sure you could just assume common interpretation.

> However, we have found over the years that such simultaneous upgrading ne=
ver works.  You need to be able to transition.

>

> I do agree that we should add text about what to do with version numbers =
that are not understood.  There are multiple choices that affect how we can=
 make changes.  My personal preference is:

>

> If an packet presumed to carry an NSH header is received at an SFF, and t=
he SFF does not understnad the version of the protocol as indicated in the =
base header, the packet MUST be discarded, and the event SHOULD be logged.

>

> This would allow an orderly transition, where devices can be upgraded to =
understand a new version, then generation of the new version header can be =
enabled.  If a configuration error is made, the packets will be dropped and=
 operators following good practices will get notifications.

>

> Yours,

> Joel

>

> On 2/26/15 2:16 AM, mohamed.boucadair at orange.com wrote:

>> Hi Joel,

>>

>> I fully agree with the extendibility of the header, but the question is =
why having a version number will be of help in the context of SFC? Second, =
having a version number without specifying the behavior when several versio=
ns are supported, when the version number is not supported by an SFC-aware =
element, etc. leaves open issues out of the spec.

>>

>> The other problem is that the current I-D includes several open doors le=
ft for extending the header:

>> * version

>> * reserved bits

>> * optional data

>>

>> This is too much for a header that is supposed to be compact and simple!

>>

>> There are other means to extend the header without signaling the version=
 in the packet. Having a distinct RFC number may be just fine in the contex=
t of an unidirectional stream such as SFC.

>>

>> Let us consider the situation where a version number is not explicitly s=
ignaled in the packet (but a new RFC updates the base SFC header). Several =
options can be considered, indeed (those are provided as examples for illus=
tration purposes):

>> * An operator can make sure that its SFC-enabled domain is configured in=
 a consistent manner to support one and only one version of the header. No =
interoperability issues is encountered in this case.

>> * An operator that wants to upgrade its SFC-enabled domain to support a =
new specification of the SFC header: An operator can decide to proceed to a=
 software/hardware updates but can maintain the old header in operation unt=
il all involved elements are upgraded to support the new version. Once the =
SFC-enabled domain is upgraded, then the new header can be enabled.

>>

>> Let's consider now that a version is signaled in the packet: to what ext=
ent signaling this information simplifies the SFC operations, and whether i=
t increases/decreases the serviceability of an SFC-enabled domain? Let's al=
so assess to what extent having the version number add more complexity in t=
he SFC header treatment when several versions are supported by a node/withi=
n an SFC enabled domain? How it helps interoperability? Some points for dis=
cussion are elaborated below:

>>

>> * If the SFC-enabled domain is configured to support the same version (w=
hich is likely): having the version number is not of any help.

>> * If the SFC-enabled domain involves some nodes that support version (v1=
) while others support (v2) (simple case): If these version are not backwar=
d compatible, this will lead to failures when two adjacent elements in a se=
rvice chain do not support the same version. The SFC system is broken. Havi=
ng the version number is not of any help in this case.

>> * If the SFC-enabled domain involves some nodes that support version (v1=
) while others support (v1 and v2):

>>

>> (a) The nodes that support both v1 and v2 should be instructed to decide=
 which version to be used. This can be either part of the specification or =
be driven by configuration. If a version number is included in the spec, I =
would expect to clarify the behavior in such case.

>>

>> (b) Suppose a node that supports only v1 receives a packet with header (=
v2): If this node does not support a notification procedure to inform the s=
ource that it does not support that header version, then FAILURES are intro=
duced in the network. This is a degradation of the service compared to lega=
cy scheme to structure services. This is not recommended, IMHO.

>>

>> (c) If a notification is received from an element about its supported ve=
rsion: a node can use another version (the logic to select other version is=
 another point to discuss) for that communication, but what to do for the n=
ext flows in the context of the same service chain or other chains that inv=
olves these two nodes as adjacent elements in the same chain? Shouldn't the=
se nodes cache the version to use for subsequent exchange to avoid receivin=
g the notification error each time? Wouldn't that complexity the behavior o=
f the SFC-aware elements?

>>

>> (d) If a notification is received from an element about its supported ve=
rsion: As this may occurs in various segments of a given service chain, e.g=
., (A(v1), B(v1,v2), C(v2), D(v1,v2), E(v1)). Notifying the adjacent node e=
ach time there is a version mismatch induce an extra delay, that may be not=
 be acceptable for every flow.

>>

>> I hope this clarifies my initial concern.

>>

>> Thank you.

>>

>> Cheers,

>> Med

>>

>>> -----Message d'origine-----

>>> De : Joel M. Halpern [mailto:jmh at joelhalpern.com]

>>> Envoy=E9 : mercredi 25 f=E9vrier 2015 16:10

>>> =C0 : BOUCADAIR Mohamed IMT/OLN; paulq at cisco.com

>>> Cc : sfc at ietf.org

>>> Objet : Re: [sfc] draft-quinn-sfc-nsh: version number

>>>

>>> I would really prefer to keep the version number.  Even though we have

>>> the MD-type identifier and for some MD we have the TLVs.

>>>

>>> The reason is that we may want to change the base header.  For example,

>>> suppose that the ciscussion about including a flow identifier in the

>>> base header had not come up now.  If it came up later, we would want to

>>> be able to have the discussion and make the choice, rather than being

>>> constrained by the lack of a version field.

>>>

>>> Yours,

>>> Joel

>>>

>>>

>>> On 2/25/15 10:03 AM, mohamed.boucadair at orange.com wrote:

>>>> Hi Paul, all,

>>>>

>>>> What is the purpose of having a version number in the header? Is there=
 a

>>>> kind of version negotiation that needs to be in place?

>>>>

>>>> I checked the I-D but failed to find text that explains the rationale,

>>>> the use of the such field and whether an error will be returned if the

>>>> version is not supported by the receiving node.

>>>>

>>>> Wouldn't be preferable to get rid of this field given that SFC header

>>>> can be extended using optional objects and consistent setup &

>>>> configuration within an SFC-enabled domain should be assumed?

>>>>

>>>> Thank you

>>>>

>>>> Cheers,

>>>>

>>>> Med

>>>>

>>>>

>>>>

>>>> _______________________________________________

>>>> sfc mailing list

>>>> sfc at ietf.org

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

>>>>

>>




--_000_787AE7BB302AE849A7480A190F8B933004919B76OPEXCLILM23corp_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
h1
	{mso-style-priority:9;
	mso-style-link:"Titre 1 Car";
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:24.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Texte brut Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;
	mso-fareast-language:EN-US;}
pre
	{mso-style-priority:99;
	mso-style-link:"Pr=E9format=E9 HTML Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Texte de bulles Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.Titre1Car
	{mso-style-name:"Titre 1 Car";
	mso-style-priority:9;
	mso-style-link:"Titre 1";
	font-family:"Cambria","serif";
	color:#365F91;
	font-weight:bold;}
span.PrformatHTMLCar
	{mso-style-name:"Pr=E9format=E9 HTML Car";
	mso-style-priority:99;
	mso-style-link:"Pr=E9format=E9 HTML";
	font-family:Consolas;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
p.Heading1, li.Heading1, div.Heading1
	{mso-style-name:"Heading 1";
	mso-style-link:"Heading 1 Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.Heading1Char
	{mso-style-name:"Heading 1 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 1";
	font-family:"Times New Roman","serif";
	font-weight:bold;}
p.HTMLPreformatted, li.HTMLPreformatted, div.HTMLPreformatted
	{mso-style-name:"HTML Preformatted";
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.TextedebullesCar
	{mso-style-name:"Texte de bulles Car";
	mso-style-priority:99;
	mso-style-link:"Texte de bulles";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle28
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;}
span.TextebrutCar
	{mso-style-name:"Texte brut Car";
	mso-style-priority:99;
	mso-style-link:"Texte brut";
	font-family:"Courier New";
	color:black;
	mso-fareast-language:EN-US;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:748039232;
	mso-list-template-ids:-1756190096;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"FR" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Hi Sunil,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">There is no such notification i=
n the current spec.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Below my thoughts about this po=
int:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">=3D=3D<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">(b) Suppose a node that supp=
orts only v1 receives a packet with header (v2): If this node does not supp=
ort a notification procedure to inform the source that it does not support =
that header version, then FAILURES are
 introduced in the network. This is a degradation of the service compared t=
o legacy scheme to structure services. This is not recommended, IMHO.<o:p><=
/o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">(c) If a notification is rec=
eived from an element about its supported version: a node can use another v=
ersion (the logic to select other version is another point to discuss) for =
that communication, but what to do for
 the next flows in the context of the same service chain or other chains th=
at involves these two nodes as adjacent elements in the same chain? Shouldn=
't these nodes cache the version to use for subsequent exchange to avoid re=
ceiving the notification error each
 time? Wouldn't that complexity the behavior of the SFC-aware elements?<o:p=
></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">(d) If a notification is rec=
eived from an element about its supported version: As this may occurs in va=
rious segments of a given service chain, e.g., (A(v1), B(v1,v2), C(v1), D(v=
1,v2), E(v1)). Notifying the adjacent
 node each time there is a version mismatch induce an extra delay, that may=
 be not be acceptable for every flow.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">=3D=3D<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Thank you.<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Cheers,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Med<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">De&nbsp;:</span></b><span style=3D"fo=
nt-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> sfc =
[mailto:sfc-bounces@ietf.org]
<b>De la part de</b> Sunil Vallamkonda<br>
<b>Envoy=E9&nbsp;:</b> mardi 3 mars 2015 20:43<br>
<b>=C0&nbsp;:</b> sfc@ietf.org<br>
<b>Objet&nbsp;:</b> Re: [sfc] draft-quinn-sfc-nsh: version number<o:p></o:p=
></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hi,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Just going through the thread o=
n version number (jumping in mid-thread),<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Apart from the version mismatch=
ed (unsupported) packet dropped and logged, is there a plan for a back off =
mechanism by SFF to notify sender and avoid being overwhelmed with such pac=
kets ?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Thank you,<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Sunil.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;<o:p></o:p></span></p>
<h1><span lang=3D"EN-US" style=3D"font-size:14.0pt;font-weight:normal">Re: =
[sfc] draft-quinn-sfc-nsh: version number</span><span lang=3D"EN-US"><o:p><=
/o:p></span></h1>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 lang=3D"EN-US">
<hr size=3D"2" width=3D"100%" align=3D"center">
</span></div>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto;mso-list:l0 level1 lfo1">
<em><span lang=3D"EN-US" style=3D"font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;;mso-fareast-language:EN-US">From</span></em><span lang=3D"EN-=
US" style=3D"mso-fareast-language:EN-US">: &quot;Paul Quinn (paulq)&quot; &=
lt;<a href=3D"mailto:paulq@DOMAIN.HIDDEN">paulq at cisco.com</a>&gt;<o:p></=
o:p></span></li><li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;ms=
o-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<em><span lang=3D"EN-US" style=3D"font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;;mso-fareast-language:EN-US">To</span></em><span lang=3D"EN-US=
" style=3D"mso-fareast-language:EN-US">: &quot;Joel M. Halpern&quot; &lt;<a=
 href=3D"mailto:jmh@DOMAIN.HIDDEN">jmh at joelhalpern.com</a>&gt;<o:p></o:p=
></span></li><li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-m=
argin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<em><span lang=3D"EN-US" style=3D"font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;;mso-fareast-language:EN-US">Cc</span></em><span lang=3D"EN-US=
" style=3D"mso-fareast-language:EN-US">: &quot;<a href=3D"mailto:mohamed.bo=
ucadair@DOMAIN.HIDDEN">mohamed.boucadair at orange.com</a>&quot; &lt;<a hre=
f=3D"mailto:mohamed.boucadair@DOMAIN.HIDDEN">mohamed.boucadair
 at orange.com</a>&gt;, &quot;<a href=3D"mailto:sfc@DOMAIN.HIDDEN">sfc at i=
etf.org</a>&quot; &lt;<a href=3D"mailto:sfc@DOMAIN.HIDDEN">sfc at ietf.org<=
/a>&gt;<o:p></o:p></span></li><li class=3D"MsoNormal" style=3D"mso-margin-t=
op-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<em><span lang=3D"EN-US" style=3D"font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;;mso-fareast-language:EN-US">Date</span></em><span lang=3D"EN-=
US" style=3D"mso-fareast-language:EN-US">: Mon, 2 Mar 2015 17:50:53 &#43;00=
00<o:p></o:p></span></li><li class=3D"MsoNormal" style=3D"mso-margin-top-al=
t:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<em><span lang=3D"EN-US" style=3D"font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;;mso-fareast-language:EN-US">In-reply-to</span></em><span lang=
=3D"EN-US" style=3D"mso-fareast-language:EN-US">: &lt;<a href=3D"http://www=
.ietf.org/mail-archive/web/sfc/current/msg03181.html">54EF2C9A.3040008@joel=
halpern.com</a>&gt;<o:p></o:p></span></li><li class=3D"MsoNormal" style=3D"=
mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1"=
>
<em><span lang=3D"EN-US" style=3D"font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;;mso-fareast-language:EN-US">References</span></em><span lang=
=3D"EN-US" style=3D"mso-fareast-language:EN-US">: &lt;<a href=3D"mailto:787=
AE7BB302AE849A7480A190F8B9330049140B4@OPEXCLILM23.corporate.adroot.infra.ft=
group">787AE7BB302AE849A7480A190F8B9330049140B4@OPEXCLILM23.corporate.adroo=
t.infra.ftgroup</a>&gt;
 &lt;<a href=3D"http://www.ietf.org/mail-archive/web/sfc/current/msg03151.h=
tml">54EDE5B7.6080102@joelhalpern.com</a>&gt; &lt;<a href=3D"mailto:787AE7B=
B302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.adroot.infra.ftgrou=
p">787AE7BB302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.adroot.in=
fra.ftgroup</a>&gt;
 &lt;<a href=3D"http://www.ietf.org/mail-archive/web/sfc/current/msg03181.h=
tml">54EF2C9A.3040008@joelhalpern.com</a>&gt;<o:p></o:p></span></li><li cla=
ss=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:aut=
o;mso-list:l0 level1 lfo1">
<em><span lang=3D"EN-US" style=3D"font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;;mso-fareast-language:EN-US">List-id</span></em><span lang=3D"=
EN-US" style=3D"mso-fareast-language:EN-US">: Network Service Chaining &lt;=
sfc.ietf.org&gt;<o:p></o:p></span></li></ul>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 lang=3D"EN-US">
<hr size=3D"2" width=3D"100%" align=3D"center">
</span></div>
<pre><span lang=3D"EN-US">Hi,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&nbsp;<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">Jumping in mid-thread.&nbsp; <o:p></o:p></span></=
pre>
<pre><span lang=3D"EN-US">&nbsp;<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">Overall, I tend to agree with Joel.&nbsp; Having =
an explicit version provides a simple way to handle dataplane format change=
s.&nbsp; As Med points out, quickly correctly, IMHO, there are other way to=
 signal changes via reserved bit.&nbsp; In practice though reserved bits ar=
e less useful since the convention is to ignore unknown bits, it makes usin=
g them for feature changes quite difficult, which then brings up back to ex=
plicit versioning that cannot be ignored.&nbsp; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&nbsp;<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">I think Joel&#8217;s suggestion below makes perfe=
ct sense and should be added to the draft.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&nbsp;<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">Paul<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&nbsp;<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&nbsp;<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt; On Feb 26, 2015, at 9:24 AM, Joel M. Halpern=
 &lt;jmh at joelhalpern.com&gt; wrote:<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt; In one sense you are correct.&nbsp; If you c=
ould count on everything being upgraded at once, sure you could just assume=
 common interpretation.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt; However, we have found over the years that s=
uch simultaneous upgrading never works.&nbsp; You need to be able to transi=
tion.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt; I do agree that we should add text about wha=
t to do with version numbers that are not understood.&nbsp; There are multi=
ple choices that affect how we can make changes.&nbsp; My personal preferen=
ce is:<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt; If an packet presumed to carry an NSH header=
 is received at an SFF, and the SFF does not understnad the version of the =
protocol as indicated in the base header, the packet MUST be discarded, and=
 the event SHOULD be logged.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt; This would allow an orderly transition, wher=
e devices can be upgraded to understand a new version, then generation of t=
he new version header can be enabled.&nbsp; If a configuration error is mad=
e, the packets will be dropped and operators following good practices will =
get notifications.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt; Yours,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt; Joel<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt; On 2/26/15 2:16 AM, mohamed.boucadair at ora=
nge.com wrote:<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; Hi Joel,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; I fully agree with the extendibility of =
the header, but the question is why having a version number will be of help=
 in the context of SFC? Second, having a version number without specifying =
the behavior when several versions are supported, when the version number i=
s not supported by an SFC-aware element, etc. leaves open issues out of the=
 spec.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; The other problem is that the current I-=
D includes several open doors left for extending the header:<o:p></o:p></sp=
an></pre>
<pre><span lang=3D"EN-US">&gt;&gt; * version<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; * reserved bits<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; * optional data<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; This is too much for a header that is su=
pposed to be compact and simple!<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; There are other means to extend the head=
er without signaling the version in the packet. Having a distinct RFC numbe=
r may be just fine in the context of an unidirectional stream such as SFC.<=
o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; Let us consider the situation where a ve=
rsion number is not explicitly signaled in the packet (but a new RFC update=
s the base SFC header). Several options can be considered, indeed (those ar=
e provided as examples for illustration purposes):<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; * An operator can make sure that its SFC=
-enabled domain is configured in a consistent manner to support one and onl=
y one version of the header. No interoperability issues is encountered in t=
his case.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; * An operator that wants to upgrade its =
SFC-enabled domain to support a new specification of the SFC header: An ope=
rator can decide to proceed to a software/hardware updates but can maintain=
 the old header in operation until all involved elements are upgraded to su=
pport the new version. Once the SFC-enabled domain is upgraded, then the ne=
w header can be enabled.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; Let's consider now that a version is sig=
naled in the packet: to what extent signaling this information simplifies t=
he SFC operations, and whether it increases/decreases the serviceability of=
 an SFC-enabled domain? Let's also assess to what extent having the version=
 number add more complexity in the SFC header treatment when several versio=
ns are supported by a node/within an SFC enabled domain? How it helps inter=
operability? Some points for discussion are elaborated below:<o:p></o:p></s=
pan></pre>
<pre><span lang=3D"EN-US">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; * If the SFC-enabled domain is configure=
d to support the same version (which is likely): having the version number =
is not of any help.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; * If the SFC-enabled domain involves som=
e nodes that support version (v1) while others support (v2) (simple case): =
If these version are not backward compatible, this will lead to failures wh=
en two adjacent elements in a service chain do not support the same version=
. The SFC system is broken. Having the version number is not of any help in=
 this case.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; * If the SFC-enabled domain involves som=
e nodes that support version (v1) while others support (v1 and v2):<o:p></o=
:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; (a) The nodes that support both v1 and v=
2 should be instructed to decide which version to be used. This can be eith=
er part of the specification or be driven by configuration. If a version nu=
mber is included in the spec, I would expect to clarify the behavior in suc=
h case.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; (b) Suppose a node that supports only v1=
 receives a packet with header (v2): If this node does not support a notifi=
cation procedure to inform the source that it does not support that header =
version, then FAILURES are introduced in the network. This is a degradation=
 of the service compared to legacy scheme to structure services. This is no=
t recommended, IMHO.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; (c) If a notification is received from a=
n element about its supported version: a node can use another version (the =
logic to select other version is another point to discuss) for that communi=
cation, but what to do for the next flows in the context of the same servic=
e chain or other chains that involves these two nodes as adjacent elements =
in the same chain? Shouldn't these nodes cache the version to use for subse=
quent exchange to avoid receiving the notification error each time? Wouldn'=
t that complexity the behavior of the SFC-aware elements?<o:p></o:p></span>=
</pre>
<pre><span lang=3D"EN-US">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; (d) If a notification is received from a=
n element about its supported version: As this may occurs in various segmen=
ts of a given service chain, e.g., (A(v1), B(v1,v2), C(v2), D(v1,v2), E(v1)=
). Notifying the adjacent node each time there is a version mismatch induce=
 an extra delay, that may be not be acceptable for every flow.<o:p></o:p></=
span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; I hope this clarifies my initial concern=
.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; Thank you.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; Cheers,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; Med<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt; -----Message d'origine-----<o:p></o:=
p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt; De : Joel M. Halpern [<a href=3D"mai=
lto:jmh">mailto:jmh</a> at joelhalpern.com]<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt; Envoy=E9 : mercredi 25 f=E9vrier 201=
5 16:10<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt; =C0 : BOUCADAIR Mohamed IMT/OLN; pau=
lq at cisco.com<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt; Cc : sfc at ietf.org<o:p></o:p></spa=
n></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt; Objet : Re: [sfc] draft-quinn-sfc-ns=
h: version number<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt; I would really prefer to keep the ve=
rsion number.&nbsp; Even though we have<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt; the MD-type identifier and for some =
MD we have the TLVs.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt; The reason is that we may want to ch=
ange the base header.&nbsp; For example,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt; suppose that the ciscussion about in=
cluding a flow identifier in the<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt; base header had not come up now.&nbs=
p; If it came up later, we would want to<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt; be able to have the discussion and m=
ake the choice, rather than being<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt; constrained by the lack of a version=
 field.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt; Yours,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt; Joel<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt; On 2/25/15 10:03 AM, mohamed.boucada=
ir at orange.com wrote:<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt;&gt; Hi Paul, all,<o:p></o:p></span><=
/pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt;&gt; What is the purpose of having a =
version number in the header? Is there a<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt;&gt; kind of version negotiation that=
 needs to be in place?<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt;&gt; I checked the I-D but failed to =
find text that explains the rationale,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt;&gt; the use of the such field and wh=
ether an error will be returned if the<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt;&gt; version is not supported by the =
receiving node.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt;&gt; Wouldn't be preferable to get ri=
d of this field given that SFC header<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt;&gt; can be extended using optional o=
bjects and consistent setup &amp;<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt;&gt; configuration within an SFC-enab=
led domain should be assumed?<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt;&gt; Thank you<o:p></o:p></span></pre=
>
<pre><span lang=3D"EN-US">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt;&gt; Cheers,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt;&gt; Med<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt;&gt; ________________________________=
_______________<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt;&gt; sfc mailing list<o:p></o:p></spa=
n></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt;&gt; sfc at ietf.org<o:p></o:p></span=
></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/=
mailman/listinfo/sfc">https://www.ietf.org/mailman/listinfo/sfc</a><o:p></o=
:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US">&nbsp;<o:p></o:p></span></pre>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;<o:p></o:p></span></p>
</div>
</div>
</body>
</html>

--_000_787AE7BB302AE849A7480A190F8B933004919B76OPEXCLILM23corp_--


From nobody Wed Mar  4 06:01:06 2015
Return-Path: <c.raiciu@cs.ucl.ac.uk>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A5F91A0222 for <sfc@ietfa.amsl.com>; Wed,  4 Mar 2015 06:01:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.011
X-Spam-Level: 
X-Spam-Status: No, score=-0.011 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 LxN6KEx3O4_S for <sfc@ietfa.amsl.com>; Wed,  4 Mar 2015 06:01:03 -0800 (PST)
Received: from bells2.cs.ucl.ac.uk (bells2.cs.ucl.ac.uk [128.16.5.33]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 417F71A1A0B for <sfc@ietf.org>; Wed,  4 Mar 2015 06:01:03 -0800 (PST)
Received: from 5-12-111-73.residential.rdsnet.ro ([5.12.111.73] helo=192-168-0-105.rdsnet.ro) by bells2.cs.ucl.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (C.Raiciu authenticated) (Exim 4.54) id 1YT9r7-000Fvw-Ek for sfc@ietf.org; Wed, 04 Mar 2015 14:00:57 +0000
From: Costin Raiciu <c.raiciu@cs.ucl.ac.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <63520A5D-435F-4E2E-B607-B9BBDF0A67A7@cs.ucl.ac.uk>
Date: Wed, 4 Mar 2015 16:00:53 +0200
To: sfc@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/2nQ9vdBRdaAHAHKT8YpbkX1ZlUw>
Subject: [sfc] HotMiddleboxes 2015
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 04 Mar 2015 14:01:05 -0000

Dear all,

I would like to draw you attention to the HotMiddleboxes workshop =
organised with Sigcomm this year in London. HotMiddleboxes aims to =
showcase early work in the broad areas of middle boxes / NFV / SDN.=20

As co-chiar of this workshop, I strongly encourage you to submit the =
relevant work that you have been doing on service function chaining to =
our workshop.

The deadline for abstract registration is march 24th, and full papers =
are expected by march 31th. You can find more info =
here:http://conferences.sigcomm.org/sigcomm/2015/hotmiddlebox.php

Looking forward to your contributions.
Costin Raiciu and Theo Benson (TPC Chairs)=


From nobody Wed Mar  4 07:02:58 2015
Return-Path: <Ron_Parker@affirmednetworks.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 604C71A1F70 for <sfc@ietfa.amsl.com>; Wed,  4 Mar 2015 07:02:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 z39Rju1aiPsB for <sfc@ietfa.amsl.com>; Wed,  4 Mar 2015 07:02:47 -0800 (PST)
Received: from hub021-ca-6.exch021.serverdata.net (hub021-ca-6.exch021.serverdata.net [64.78.56.71]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8878E1A1BE7 for <sfc@ietf.org>; Wed,  4 Mar 2015 07:02:47 -0800 (PST)
Received: from MBX021-W3-CA-2.exch021.domain.local ([10.254.4.78]) by HUB021-CA-6.exch021.domain.local ([10.254.4.92]) with mapi id 14.03.0224.002;  Wed, 4 Mar 2015 07:02:46 -0800
From: Ron Parker <Ron_Parker@affirmednetworks.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "Sunil Vallamkonda" <sunilvk@f5.com>
Thread-Topic: Re: [sfc] draft-quinn-sfc-nsh: version number
Thread-Index: AdBV6VnhN9N2Adv/Rs2PZVkjw6sDlQAXRdTwABFWhuA=
Date: Wed, 4 Mar 2015 15:02:46 +0000
Message-ID: <CDF2F015F4429F458815ED2A6C2B6B0B2E85379B@MBX021-W3-CA-2.exch021.domain.local>
References: <01f9e1a4e6514854a26556e4c6a3e36e@SEAEXCHMBX05.olympus.F5Net.com> <787AE7BB302AE849A7480A190F8B933004919B76@OPEXCLILM23.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B933004919B76@OPEXCLILM23.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [50.203.66.100]
Content-Type: multipart/alternative; boundary="_000_CDF2F015F4429F458815ED2A6C2B6B0B2E85379BMBX021W3CA2exch_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/BV5zLyDtaAN1MwGYyIRg2ddzeU4>
Cc: "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] draft-quinn-sfc-nsh: version number
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 04 Mar 2015 15:02:55 -0000

--_000_CDF2F015F4429F458815ED2A6C2B6B0B2E85379BMBX021W3CA2exch_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

When we take up OAM, we could consider these ICMP-like behaviors - i.e., OA=
M packet containing "Version Incompatible" sent in the reverse direction on=
 the involved RSP.   But I'm not sure what should be discussed in this draf=
t, since OAM is explicitly out of scope.

   Ron



From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of mohamed.boucadair@oran=
ge.com
Sent: Wednesday, March 4, 2015 1:47 AM
To: Sunil Vallamkonda
Cc: sfc@ietf.org
Subject: Re: [sfc] draft-quinn-sfc-nsh: version number

Hi Sunil,

There is no such notification in the current spec.

Below my thoughts about this point:

=3D=3D

(b) Suppose a node that supports only v1 receives a packet with header (v2)=
: If this node does not support a notification procedure to inform the sour=
ce that it does not support that header version, then FAILURES are introduc=
ed in the network. This is a degradation of the service compared to legacy =
scheme to structure services. This is not recommended, IMHO.



(c) If a notification is received from an element about its supported versi=
on: a node can use another version (the logic to select other version is an=
other point to discuss) for that communication, but what to do for the next=
 flows in the context of the same service chain or other chains that involv=
es these two nodes as adjacent elements in the same chain? Shouldn't these =
nodes cache the version to use for subsequent exchange to avoid receiving t=
he notification error each time? Wouldn't that complexity the behavior of t=
he SFC-aware elements?



(d) If a notification is received from an element about its supported versi=
on: As this may occurs in various segments of a given service chain, e.g., =
(A(v1), B(v1,v2), C(v1), D(v1,v2), E(v1)). Notifying the adjacent node each=
 time there is a version mismatch induce an extra delay, that may be not be=
 acceptable for every flow.
=3D=3D

Thank you.

Cheers,
Med


De : sfc [mailto:sfc-bounces@ietf.org] De la part de Sunil Vallamkonda
Envoy=E9 : mardi 3 mars 2015 20:43
=C0 : sfc@ietf.org<mailto:sfc@ietf.org>
Objet : Re: [sfc] draft-quinn-sfc-nsh: version number

Hi,

Just going through the thread on version number (jumping in mid-thread),

Apart from the version mismatched (unsupported) packet dropped and logged, =
is there a plan for a back off mechanism by SFF to notify sender and avoid =
being overwhelmed with such packets ?

Thank you,
Sunil.


Re: [sfc] draft-quinn-sfc-nsh: version number
________________________________

  *   From: "Paul Quinn (paulq)" <paulq at cisco.com<mailto:paulq@DOMAIN.HI=
DDEN>>
  *   To: "Joel M. Halpern" <jmh at joelhalpern.com<mailto:jmh@DOMAIN.HIDDE=
N>>
  *   Cc: "mohamed.boucadair at orange.com<mailto:mohamed.boucadair@DOMAIN.=
HIDDEN>" <mohamed.boucadair at orange.com<mailto:mohamed.boucadair@DOMAIN.H=
IDDEN>>, "sfc at ietf.org<mailto:sfc@DOMAIN.HIDDEN>" <sfc at ietf.org<mailt=
o:sfc@DOMAIN.HIDDEN>>
  *   Date: Mon, 2 Mar 2015 17:50:53 +0000
  *   In-reply-to: <54EF2C9A.3040008@joelhalpern.com<http://www.ietf.org/ma=
il-archive/web/sfc/current/msg03181.html>>
  *   References: <787AE7BB302AE849A7480A190F8B9330049140B4@OPEXCLILM23.cor=
porate.adroot.infra.ftgroup<mailto:787AE7BB302AE849A7480A190F8B9330049140B4=
@OPEXCLILM23.corporate.adroot.infra.ftgroup>> <54EDE5B7.6080102@joelhalpern=
.com<http://www.ietf.org/mail-archive/web/sfc/current/msg03151.html>> <787A=
E7BB302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.adroot.infra.ftg=
roup<mailto:787AE7BB302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.=
adroot.infra.ftgroup>> <54EF2C9A.3040008@joelhalpern.com<http://www.ietf.or=
g/mail-archive/web/sfc/current/msg03181.html>>
  *   List-id: Network Service Chaining <sfc.ietf.org>

________________________________

Hi,



Jumping in mid-thread.



Overall, I tend to agree with Joel.  Having an explicit version provides a =
simple way to handle dataplane format changes.  As Med points out, quickly =
correctly, IMHO, there are other way to signal changes via reserved bit.  I=
n practice though reserved bits are less useful since the convention is to =
ignore unknown bits, it makes using them for feature changes quite difficul=
t, which then brings up back to explicit versioning that cannot be ignored.



I think Joel's suggestion below makes perfect sense and should be added to =
the draft.



Paul





> On Feb 26, 2015, at 9:24 AM, Joel M. Halpern <jmh at joelhalpern.com> wro=
te:

>

> In one sense you are correct.  If you could count on everything being upg=
raded at once, sure you could just assume common interpretation.

> However, we have found over the years that such simultaneous upgrading ne=
ver works.  You need to be able to transition.

>

> I do agree that we should add text about what to do with version numbers =
that are not understood.  There are multiple choices that affect how we can=
 make changes.  My personal preference is:

>

> If an packet presumed to carry an NSH header is received at an SFF, and t=
he SFF does not understnad the version of the protocol as indicated in the =
base header, the packet MUST be discarded, and the event SHOULD be logged.

>

> This would allow an orderly transition, where devices can be upgraded to =
understand a new version, then generation of the new version header can be =
enabled.  If a configuration error is made, the packets will be dropped and=
 operators following good practices will get notifications.

>

> Yours,

> Joel

>

> On 2/26/15 2:16 AM, mohamed.boucadair at orange.com wrote:

>> Hi Joel,

>>

>> I fully agree with the extendibility of the header, but the question is =
why having a version number will be of help in the context of SFC? Second, =
having a version number without specifying the behavior when several versio=
ns are supported, when the version number is not supported by an SFC-aware =
element, etc. leaves open issues out of the spec.

>>

>> The other problem is that the current I-D includes several open doors le=
ft for extending the header:

>> * version

>> * reserved bits

>> * optional data

>>

>> This is too much for a header that is supposed to be compact and simple!

>>

>> There are other means to extend the header without signaling the version=
 in the packet. Having a distinct RFC number may be just fine in the contex=
t of an unidirectional stream such as SFC.

>>

>> Let us consider the situation where a version number is not explicitly s=
ignaled in the packet (but a new RFC updates the base SFC header). Several =
options can be considered, indeed (those are provided as examples for illus=
tration purposes):

>> * An operator can make sure that its SFC-enabled domain is configured in=
 a consistent manner to support one and only one version of the header. No =
interoperability issues is encountered in this case.

>> * An operator that wants to upgrade its SFC-enabled domain to support a =
new specification of the SFC header: An operator can decide to proceed to a=
 software/hardware updates but can maintain the old header in operation unt=
il all involved elements are upgraded to support the new version. Once the =
SFC-enabled domain is upgraded, then the new header can be enabled.

>>

>> Let's consider now that a version is signaled in the packet: to what ext=
ent signaling this information simplifies the SFC operations, and whether i=
t increases/decreases the serviceability of an SFC-enabled domain? Let's al=
so assess to what extent having the version number add more complexity in t=
he SFC header treatment when several versions are supported by a node/withi=
n an SFC enabled domain? How it helps interoperability? Some points for dis=
cussion are elaborated below:

>>

>> * If the SFC-enabled domain is configured to support the same version (w=
hich is likely): having the version number is not of any help.

>> * If the SFC-enabled domain involves some nodes that support version (v1=
) while others support (v2) (simple case): If these version are not backwar=
d compatible, this will lead to failures when two adjacent elements in a se=
rvice chain do not support the same version. The SFC system is broken. Havi=
ng the version number is not of any help in this case.

>> * If the SFC-enabled domain involves some nodes that support version (v1=
) while others support (v1 and v2):

>>

>> (a) The nodes that support both v1 and v2 should be instructed to decide=
 which version to be used. This can be either part of the specification or =
be driven by configuration. If a version number is included in the spec, I =
would expect to clarify the behavior in such case.

>>

>> (b) Suppose a node that supports only v1 receives a packet with header (=
v2): If this node does not support a notification procedure to inform the s=
ource that it does not support that header version, then FAILURES are intro=
duced in the network. This is a degradation of the service compared to lega=
cy scheme to structure services. This is not recommended, IMHO.

>>

>> (c) If a notification is received from an element about its supported ve=
rsion: a node can use another version (the logic to select other version is=
 another point to discuss) for that communication, but what to do for the n=
ext flows in the context of the same service chain or other chains that inv=
olves these two nodes as adjacent elements in the same chain? Shouldn't the=
se nodes cache the version to use for subsequent exchange to avoid receivin=
g the notification error each time? Wouldn't that complexity the behavior o=
f the SFC-aware elements?

>>

>> (d) If a notification is received from an element about its supported ve=
rsion: As this may occurs in various segments of a given service chain, e.g=
., (A(v1), B(v1,v2), C(v2), D(v1,v2), E(v1)). Notifying the adjacent node e=
ach time there is a version mismatch induce an extra delay, that may be not=
 be acceptable for every flow.

>>

>> I hope this clarifies my initial concern.

>>

>> Thank you.

>>

>> Cheers,

>> Med

>>

>>> -----Message d'origine-----

>>> De : Joel M. Halpern [mailto:jmh at joelhalpern.com]

>>> Envoy=E9 : mercredi 25 f=E9vrier 2015 16:10

>>> =C0 : BOUCADAIR Mohamed IMT/OLN; paulq at cisco.com

>>> Cc : sfc at ietf.org

>>> Objet : Re: [sfc] draft-quinn-sfc-nsh: version number

>>>

>>> I would really prefer to keep the version number.  Even though we have

>>> the MD-type identifier and for some MD we have the TLVs.

>>>

>>> The reason is that we may want to change the base header.  For example,

>>> suppose that the ciscussion about including a flow identifier in the

>>> base header had not come up now.  If it came up later, we would want to

>>> be able to have the discussion and make the choice, rather than being

>>> constrained by the lack of a version field.

>>>

>>> Yours,

>>> Joel

>>>

>>>

>>> On 2/25/15 10:03 AM, mohamed.boucadair at orange.com wrote:

>>>> Hi Paul, all,

>>>>

>>>> What is the purpose of having a version number in the header? Is there=
 a

>>>> kind of version negotiation that needs to be in place?

>>>>

>>>> I checked the I-D but failed to find text that explains the rationale,

>>>> the use of the such field and whether an error will be returned if the

>>>> version is not supported by the receiving node.

>>>>

>>>> Wouldn't be preferable to get rid of this field given that SFC header

>>>> can be extended using optional objects and consistent setup &

>>>> configuration within an SFC-enabled domain should be assumed?

>>>>

>>>> Thank you

>>>>

>>>> Cheers,

>>>>

>>>> Med

>>>>

>>>>

>>>>

>>>> _______________________________________________

>>>> sfc mailing list

>>>> sfc at ietf.org

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

>>>>

>>




--_000_CDF2F015F4429F458815ED2A6C2B6B0B2E85379BMBX021W3CA2exch_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"Segoe UI";
	panose-1:2 11 5 2 4 2 4 2 2 3;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:Cambria;
	panose-1:2 4 5 3 5 4 6 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
h1
	{mso-style-priority:9;
	mso-style-link:"Heading 1 Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	font-weight:normal;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma",sans-serif;}
span.Heading1Char
	{mso-style-name:"Heading 1 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 1";
	font-family:"Times New Roman",serif;
	font-weight:bold;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Segoe UI",sans-serif;}
p.Titre1, li.Titre1, div.Titre1
	{mso-style-name:"Titre 1";
	mso-style-link:"Titre 1 Car";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.Titre1Car
	{mso-style-name:"Titre 1 Car";
	mso-style-priority:9;
	mso-style-link:"Titre 1";
	font-family:"Cambria",serif;
	color:#365F91;
	font-weight:bold;}
p.PrformatHTML, li.PrformatHTML, div.PrformatHTML
	{mso-style-name:"Pr=E9format=E9 HTML";
	mso-style-link:"Pr=E9format=E9 HTML Car";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.PrformatHTMLCar
	{mso-style-name:"Pr=E9format=E9 HTML Car";
	mso-style-priority:99;
	mso-style-link:"Pr=E9format=E9 HTML";
	font-family:Consolas;}
span.EmailStyle28
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
p.Textedebulles, li.Textedebulles, div.Textedebulles
	{mso-style-name:"Texte de bulles";
	mso-style-link:"Texte de bulles Car";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.TextedebullesCar
	{mso-style-name:"Texte de bulles Car";
	mso-style-priority:99;
	mso-style-link:"Texte de bulles";
	font-family:"Tahoma",sans-serif;}
span.EmailStyle31
	{mso-style-type:personal;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;}
p.Textebrut, li.Textebrut, div.Textebrut
	{mso-style-name:"Texte brut";
	mso-style-link:"Texte brut Car";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.TextebrutCar
	{mso-style-name:"Texte brut Car";
	mso-style-priority:99;
	mso-style-link:"Texte brut";
	font-family:"Courier New";
	color:black;
	mso-fareast-language:EN-US;}
span.EmailStyle35
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:31078211;
	mso-list-template-ids:-1485522332;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1
	{mso-list-id:748039232;
	mso-list-template-ids:-1756190096;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">When we take up OAM, w=
e could consider these ICMP-like behaviors &#8211; i.e., OAM packet contain=
ing &#8220;Version Incompatible&#8221; sent in the reverse direction on the=
 involved RSP.&nbsp;&nbsp; But I&#8217;m not sure what should be discussed
 in this draft, since OAM is explicitly out of scope.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp; Ron<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><a name=3D"_MailEndCompose"><span style=3D"color:#1F=
497D"><o:p>&nbsp;</o:p></span></a></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> sfc [mailto:sfc-bounces@ietf.org] <b>On=
 Behalf Of
</b>mohamed.boucadair@orange.com<br>
<b>Sent:</b> Wednesday, March 4, 2015 1:47 AM<br>
<b>To:</b> Sunil Vallamkonda<br>
<b>Cc:</b> sfc@ietf.org<br>
<b>Subject:</b> Re: [sfc] draft-quinn-sfc-nsh: version number<o:p></o:p></p=
>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Hi Sunil,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">There is no such notification in the current s=
pec.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Below my thoughts about this point:<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">=3D=3D<o:p></o:p></span></p>
<p class=3D"MsoPlainText">(b) Suppose a node that supports only v1 receives=
 a packet with header (v2): If this node does not support a notification pr=
ocedure to inform the source that it does not support that header version, =
then FAILURES are introduced in the
 network. This is a degradation of the service compared to legacy scheme to=
 structure services. This is not recommended, IMHO.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">(c) If a notification is received from an element=
 about its supported version: a node can use another version (the logic to =
select other version is another point to discuss) for that communication, b=
ut what to do for the next flows in
 the context of the same service chain or other chains that involves these =
two nodes as adjacent elements in the same chain? Shouldn't these nodes cac=
he the version to use for subsequent exchange to avoid receiving the notifi=
cation error each time? Wouldn't
 that complexity the behavior of the SFC-aware elements?<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">(d) If a notification is received from an element=
 about its supported version: As this may occurs in various segments of a g=
iven service chain, e.g., (A(v1), B(v1,v2), C(v1), D(v1,v2), E(v1)). Notify=
ing the adjacent node each time there
 is a version mismatch induce an extra delay, that may be not be acceptable=
 for every flow.<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">=3D=3D<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Thank you.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Cheers,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Med<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span lang=3D"FR" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,sans-serif">De&nbsp;:</span></b><span lang=3D"FR"=
 style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,sans-serif"> sfc =
[<a href=3D"mailto:sfc-bounces@ietf.org">mailto:sfc-bounces@ietf.org</a>]
<b>De la part de</b> Sunil Vallamkonda<br>
<b>Envoy=E9&nbsp;:</b> mardi 3 mars 2015 20:43<br>
<b>=C0&nbsp;:</b> <a href=3D"mailto:sfc@ietf.org">sfc@ietf.org</a><br>
<b>Objet&nbsp;:</b> Re: [sfc] draft-quinn-sfc-nsh: version number<o:p></o:p=
></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"FR"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">Just going through the thread on version number (jum=
ping in mid-thread),<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">Apart from the version mismatched (unsupported) pack=
et dropped and logged, is there a plan for a back off mechanism by SFF to n=
otify sender and avoid being overwhelmed with such packets ?<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">Thank you,<o:p></o:p></p>
<p class=3D"MsoNormal">Sunil.<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<h1 style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span styl=
e=3D"font-size:14.0pt;font-family:&quot;Times New Roman&quot;,serif">Re: [s=
fc] draft-quinn-sfc-nsh: version number</span><b><span style=3D"font-size:2=
4.0pt;font-family:&quot;Times New Roman&quot;,serif"><o:p></o:p></span></b>=
</h1>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"100%" align=3D"center">
</div>
<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;=
mso-fareast-language:EN-US">
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto;mso-list:l1 level1 lfo3">
<em><span style=3D"font-family:&quot;Calibri&quot;,sans-serif">From</span><=
/em>: &quot;Paul Quinn (paulq)&quot; &lt;<a href=3D"mailto:paulq@DOMAIN.HID=
DEN">paulq at cisco.com</a>&gt;<o:p></o:p></li><li class=3D"MsoNormal" styl=
e=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 =
lfo3">
<em><span style=3D"font-family:&quot;Calibri&quot;,sans-serif">To</span></e=
m>: &quot;Joel M. Halpern&quot; &lt;<a href=3D"mailto:jmh@DOMAIN.HIDDEN">jm=
h at joelhalpern.com</a>&gt;<o:p></o:p></li><li class=3D"MsoNormal" style=
=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 l=
fo3">
<em><span style=3D"font-family:&quot;Calibri&quot;,sans-serif">Cc</span></e=
m>: &quot;<a href=3D"mailto:mohamed.boucadair@DOMAIN.HIDDEN">mohamed.boucad=
air at orange.com</a>&quot; &lt;<a href=3D"mailto:mohamed.boucadair@DOMAIN.=
HIDDEN">mohamed.boucadair at orange.com</a>&gt;, &quot;<a href=3D"mailto:sf=
c@DOMAIN.HIDDEN">sfc
 at ietf.org</a>&quot; &lt;<a href=3D"mailto:sfc@DOMAIN.HIDDEN">sfc at ietf=
.org</a>&gt;<o:p></o:p></li><li class=3D"MsoNormal" style=3D"mso-margin-top=
-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo3">
<em><span style=3D"font-family:&quot;Calibri&quot;,sans-serif">Date</span><=
/em>: Mon, 2 Mar 2015 17:50:53 &#43;0000<o:p></o:p></li><li class=3D"MsoNor=
mal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l=
1 level1 lfo3">
<em><span style=3D"font-family:&quot;Calibri&quot;,sans-serif">In-reply-to<=
/span></em>: &lt;<a href=3D"http://www.ietf.org/mail-archive/web/sfc/curren=
t/msg03181.html">54EF2C9A.3040008@joelhalpern.com</a>&gt;<o:p></o:p></li><l=
i class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al=
t:auto;mso-list:l1 level1 lfo3">
<em><span style=3D"font-family:&quot;Calibri&quot;,sans-serif">References</=
span></em>: &lt;<a href=3D"mailto:787AE7BB302AE849A7480A190F8B9330049140B4@=
OPEXCLILM23.corporate.adroot.infra.ftgroup">787AE7BB302AE849A7480A190F8B933=
0049140B4@OPEXCLILM23.corporate.adroot.infra.ftgroup</a>&gt;
 &lt;<a href=3D"http://www.ietf.org/mail-archive/web/sfc/current/msg03151.h=
tml">54EDE5B7.6080102@joelhalpern.com</a>&gt; &lt;<a href=3D"mailto:787AE7B=
B302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.adroot.infra.ftgrou=
p">787AE7BB302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.adroot.in=
fra.ftgroup</a>&gt;
 &lt;<a href=3D"http://www.ietf.org/mail-archive/web/sfc/current/msg03181.h=
tml">54EF2C9A.3040008@joelhalpern.com</a>&gt;<o:p></o:p></li><li class=3D"M=
soNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-l=
ist:l1 level1 lfo3">
<em><span style=3D"font-family:&quot;Calibri&quot;,sans-serif">List-id</spa=
n></em>: Network Service Chaining &lt;sfc.ietf.org&gt;<o:p></o:p></li></ul>
</span>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"100%" align=3D"center">
</div>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">H=
i,<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
nbsp;<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">J=
umping in mid-thread.&nbsp; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
nbsp;<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">O=
verall, I tend to agree with Joel.&nbsp; Having an explicit version provide=
s a simple way to handle dataplane format changes.&nbsp; As Med points out,=
 quickly correctly, IMHO, there are other way to signal changes via reserve=
d bit.&nbsp; In practice though reserved bits are less useful since the con=
vention is to ignore unknown bits, it makes using them for feature changes =
quite difficult, which then brings up back to explicit versioning that cann=
ot be ignored.&nbsp; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
nbsp;<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">I=
 think Joel&#8217;s suggestion below makes perfect sense and should be adde=
d to the draft.<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
nbsp;<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">P=
aul<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
nbsp;<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
nbsp;<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt; On Feb 26, 2015, at 9:24 AM, Joel M. Halpern &lt;jmh at joelhalpern.com=
&gt; wrote:<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt; In one sense you are correct.&nbsp; If you could count on everything be=
ing upgraded at once, sure you could just assume common interpretation.<o:p=
></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt; However, we have found over the years that such simultaneous upgrading =
never works.&nbsp; You need to be able to transition.<o:p></o:p></span></pr=
e>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt; I do agree that we should add text about what to do with version number=
s that are not understood.&nbsp; There are multiple choices that affect how=
 we can make changes.&nbsp; My personal preference is:<o:p></o:p></span></p=
re>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt; If an packet presumed to carry an NSH header is received at an SFF, and=
 the SFF does not understnad the version of the protocol as indicated in th=
e base header, the packet MUST be discarded, and the event SHOULD be logged=
.<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt; This would allow an orderly transition, where devices can be upgraded t=
o understand a new version, then generation of the new version header can b=
e enabled.&nbsp; If a configuration error is made, the packets will be drop=
ped and operators following good practices will get notifications.<o:p></o:=
p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt; Yours,<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt; Joel<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt; On 2/26/15 2:16 AM, mohamed.boucadair at orange.com wrote:<o:p></o:p></=
span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; Hi Joel,<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; I fully agree with the extendibility of the header, but the questio=
n is why having a version number will be of help in the context of SFC? Sec=
ond, having a version number without specifying the behavior when several v=
ersions are supported, when the version number is not supported by an SFC-a=
ware element, etc. leaves open issues out of the spec.<o:p></o:p></span></p=
re>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; The other problem is that the current I-D includes several open doo=
rs left for extending the header:<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; * version<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; * reserved bits<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; * optional data<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; This is too much for a header that is supposed to be compact and si=
mple!<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; There are other means to extend the header without signaling the ve=
rsion in the packet. Having a distinct RFC number may be just fine in the c=
ontext of an unidirectional stream such as SFC.<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; Let us consider the situation where a version number is not explici=
tly signaled in the packet (but a new RFC updates the base SFC header). Sev=
eral options can be considered, indeed (those are provided as examples for =
illustration purposes):<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; * An operator can make sure that its SFC-enabled domain is configur=
ed in a consistent manner to support one and only one version of the header=
. No interoperability issues is encountered in this case.<o:p></o:p></span>=
</pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; * An operator that wants to upgrade its SFC-enabled domain to suppo=
rt a new specification of the SFC header: An operator can decide to proceed=
 to a software/hardware updates but can maintain the old header in operatio=
n until all involved elements are upgraded to support the new version. Once=
 the SFC-enabled domain is upgraded, then the new header can be enabled.<o:=
p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; Let's consider now that a version is signaled in the packet: to wha=
t extent signaling this information simplifies the SFC operations, and whet=
her it increases/decreases the serviceability of an SFC-enabled domain? Let=
's also assess to what extent having the version number add more complexity=
 in the SFC header treatment when several versions are supported by a node/=
within an SFC enabled domain? How it helps interoperability? Some points fo=
r discussion are elaborated below:<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; * If the SFC-enabled domain is configured to support the same versi=
on (which is likely): having the version number is not of any help.<o:p></o=
:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; * If the SFC-enabled domain involves some nodes that support versio=
n (v1) while others support (v2) (simple case): If these version are not ba=
ckward compatible, this will lead to failures when two adjacent elements in=
 a service chain do not support the same version. The SFC system is broken.=
 Having the version number is not of any help in this case.<o:p></o:p></spa=
n></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; * If the SFC-enabled domain involves some nodes that support versio=
n (v1) while others support (v1 and v2):<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; (a) The nodes that support both v1 and v2 should be instructed to d=
ecide which version to be used. This can be either part of the specificatio=
n or be driven by configuration. If a version number is included in the spe=
c, I would expect to clarify the behavior in such case.<o:p></o:p></span></=
pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; (b) Suppose a node that supports only v1 receives a packet with hea=
der (v2): If this node does not support a notification procedure to inform =
the source that it does not support that header version, then FAILURES are =
introduced in the network. This is a degradation of the service compared to=
 legacy scheme to structure services. This is not recommended, IMHO.<o:p></=
o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; (c) If a notification is received from an element about its support=
ed version: a node can use another version (the logic to select other versi=
on is another point to discuss) for that communication, but what to do for =
the next flows in the context of the same service chain or other chains tha=
t involves these two nodes as adjacent elements in the same chain? Shouldn'=
t these nodes cache the version to use for subsequent exchange to avoid rec=
eiving the notification error each time? Wouldn't that complexity the behav=
ior of the SFC-aware elements?<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; (d) If a notification is received from an element about its support=
ed version: As this may occurs in various segments of a given service chain=
, e.g., (A(v1), B(v1,v2), C(v2), D(v1,v2), E(v1)). Notifying the adjacent n=
ode each time there is a version mismatch induce an extra delay, that may b=
e not be acceptable for every flow.<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; I hope this clarifies my initial concern.<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; Thank you.<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; Cheers,<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; Med<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; -----Message d'origine-----<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; De : Joel M. Halpern [<a href=3D"mailto:jmh">mailto:jmh</a> at =
joelhalpern.com]<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; Envoy=E9 : mercredi 25 f=E9vrier 2015 16:10<o:p></o:p></span></=
pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; =C0 : BOUCADAIR Mohamed IMT/OLN; paulq at cisco.com<o:p></o:p><=
/span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; Cc : sfc at ietf.org<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; Objet : Re: [sfc] draft-quinn-sfc-nsh: version number<o:p></o:p=
></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; I would really prefer to keep the version number.&nbsp; Even th=
ough we have<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; the MD-type identifier and for some MD we have the TLVs.<o:p></=
o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; The reason is that we may want to change the base header.&nbsp;=
 For example,<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; suppose that the ciscussion about including a flow identifier i=
n the<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; base header had not come up now.&nbsp; If it came up later, we =
would want to<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; be able to have the discussion and make the choice, rather than=
 being<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; constrained by the lack of a version field.<o:p></o:p></span></=
pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; Yours,<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; Joel<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; On 2/25/15 10:03 AM, mohamed.boucadair at orange.com wrote:<o:p=
></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; Hi Paul, all,<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; What is the purpose of having a version number in the heade=
r? Is there a<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; kind of version negotiation that needs to be in place?<o:p>=
</o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; I checked the I-D but failed to find text that explains the=
 rationale,<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; the use of the such field and whether an error will be retu=
rned if the<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; version is not supported by the receiving node.<o:p></o:p><=
/span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; Wouldn't be preferable to get rid of this field given that =
SFC header<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; can be extended using optional objects and consistent setup=
 &amp;<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; configuration within an SFC-enabled domain should be assume=
d?<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; Thank you<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; Cheers,<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; Med<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; _______________________________________________<o:p></o:p><=
/span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; sfc mailing list<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; sfc at ietf.org<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/sfc">https=
://www.ietf.org/mailman/listinfo/sfc</a><o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
nbsp;<o:p></o:p></span></pre>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
</div>
</body>
</html>

--_000_CDF2F015F4429F458815ED2A6C2B6B0B2E85379BMBX021W3CA2exch_--


From nobody Wed Mar  4 07:42:56 2015
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 391991A870F for <sfc@ietfa.amsl.com>; Wed,  4 Mar 2015 07:42:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 ulgoO5zOtzPg for <sfc@ietfa.amsl.com>; Wed,  4 Mar 2015 07:42:43 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6291F1A023E for <sfc@ietf.org>; Wed,  4 Mar 2015 07:42:42 -0800 (PST)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id D847C3B412F; Wed,  4 Mar 2015 16:42:40 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.30]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id B910F27C072; Wed,  4 Mar 2015 16:42:40 +0100 (CET)
Received: from OPEXCLILM23.corporate.adroot.infra.ftgroup ([169.254.2.231]) by OPEXCLILH02.corporate.adroot.infra.ftgroup ([10.114.31.30]) with mapi id 14.03.0224.002; Wed, 4 Mar 2015 16:42:40 +0100
From: <mohamed.boucadair@orange.com>
To: Ron Parker <Ron_Parker@affirmednetworks.com>, Sunil Vallamkonda <sunilvk@f5.com>
Thread-Topic: Re: [sfc] draft-quinn-sfc-nsh: version number
Thread-Index: AdBV6VnhN9N2Adv/Rs2PZVkjw6sDlQAXRdTwABFWhuAAAVpygA==
Date: Wed, 4 Mar 2015 15:42:39 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93300491A1AF@OPEXCLILM23.corporate.adroot.infra.ftgroup>
References: <01f9e1a4e6514854a26556e4c6a3e36e@SEAEXCHMBX05.olympus.F5Net.com> <787AE7BB302AE849A7480A190F8B933004919B76@OPEXCLILM23.corporate.adroot.infra.ftgroup> <CDF2F015F4429F458815ED2A6C2B6B0B2E85379B@MBX021-W3-CA-2.exch021.domain.local>
In-Reply-To: <CDF2F015F4429F458815ED2A6C2B6B0B2E85379B@MBX021-W3-CA-2.exch021.domain.local>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.1]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B93300491A1AFOPEXCLILM23corp_"
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.12.16.73920
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/5Q7sZD3i6bwDT5_iHML4lrcnTKU>
Cc: "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] draft-quinn-sfc-nsh: version number
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 04 Mar 2015 15:42:55 -0000

--_000_787AE7BB302AE849A7480A190F8B93300491A1AFOPEXCLILM23corp_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Ron,

If the version number is maintained, discussing the behavior of a node if i=
t supports several versions, if it does not support the version of a packet=
 it receives, etc. is not about OAM. This is part of the behavior that need=
s to be specified in the document.

Cheers,
Med


De : Ron Parker [mailto:Ron_Parker@affirmednetworks.com]
Envoy=E9 : mercredi 4 mars 2015 16:03
=C0 : BOUCADAIR Mohamed IMT/OLN; Sunil Vallamkonda
Cc : sfc@ietf.org
Objet : RE: Re: [sfc] draft-quinn-sfc-nsh: version number

When we take up OAM, we could consider these ICMP-like behaviors - i.e., OA=
M packet containing "Version Incompatible" sent in the reverse direction on=
 the involved RSP.   But I'm not sure what should be discussed in this draf=
t, since OAM is explicitly out of scope.

   Ron



From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of mohamed.boucadair@oran=
ge.com<mailto:mohamed.boucadair@orange.com>
Sent: Wednesday, March 4, 2015 1:47 AM
To: Sunil Vallamkonda
Cc: sfc@ietf.org<mailto:sfc@ietf.org>
Subject: Re: [sfc] draft-quinn-sfc-nsh: version number

Hi Sunil,

There is no such notification in the current spec.

Below my thoughts about this point:

=3D=3D

(b) Suppose a node that supports only v1 receives a packet with header (v2)=
: If this node does not support a notification procedure to inform the sour=
ce that it does not support that header version, then FAILURES are introduc=
ed in the network. This is a degradation of the service compared to legacy =
scheme to structure services. This is not recommended, IMHO.



(c) If a notification is received from an element about its supported versi=
on: a node can use another version (the logic to select other version is an=
other point to discuss) for that communication, but what to do for the next=
 flows in the context of the same service chain or other chains that involv=
es these two nodes as adjacent elements in the same chain? Shouldn't these =
nodes cache the version to use for subsequent exchange to avoid receiving t=
he notification error each time? Wouldn't that complexity the behavior of t=
he SFC-aware elements?



(d) If a notification is received from an element about its supported versi=
on: As this may occurs in various segments of a given service chain, e.g., =
(A(v1), B(v1,v2), C(v1), D(v1,v2), E(v1)). Notifying the adjacent node each=
 time there is a version mismatch induce an extra delay, that may be not be=
 acceptable for every flow.
=3D=3D

Thank you.

Cheers,
Med


De : sfc [mailto:sfc-bounces@ietf.org] De la part de Sunil Vallamkonda
Envoy=E9 : mardi 3 mars 2015 20:43
=C0 : sfc@ietf.org<mailto:sfc@ietf.org>
Objet : Re: [sfc] draft-quinn-sfc-nsh: version number

Hi,

Just going through the thread on version number (jumping in mid-thread),

Apart from the version mismatched (unsupported) packet dropped and logged, =
is there a plan for a back off mechanism by SFF to notify sender and avoid =
being overwhelmed with such packets ?

Thank you,
Sunil.


Re: [sfc] draft-quinn-sfc-nsh: version number
________________________________

  *   From: "Paul Quinn (paulq)" <paulq at cisco.com<mailto:paulq@DOMAIN.HI=
DDEN>>
  *   To: "Joel M. Halpern" <jmh at joelhalpern.com<mailto:jmh@DOMAIN.HIDDE=
N>>
  *   Cc: "mohamed.boucadair at orange.com<mailto:mohamed.boucadair@DOMAIN.=
HIDDEN>" <mohamed.boucadair at orange.com<mailto:mohamed.boucadair@DOMAIN.H=
IDDEN>>, "sfc at ietf.org<mailto:sfc@DOMAIN.HIDDEN>" <sfc at ietf.org<mailt=
o:sfc@DOMAIN.HIDDEN>>
  *   Date: Mon, 2 Mar 2015 17:50:53 +0000
  *   In-reply-to: <54EF2C9A.3040008@joelhalpern.com<http://www.ietf.org/ma=
il-archive/web/sfc/current/msg03181.html>>
  *   References: <787AE7BB302AE849A7480A190F8B9330049140B4@OPEXCLILM23.cor=
porate.adroot.infra.ftgroup<mailto:787AE7BB302AE849A7480A190F8B9330049140B4=
@OPEXCLILM23.corporate.adroot.infra.ftgroup>> <54EDE5B7.6080102@joelhalpern=
.com<http://www.ietf.org/mail-archive/web/sfc/current/msg03151.html>> <787A=
E7BB302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.adroot.infra.ftg=
roup<mailto:787AE7BB302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.=
adroot.infra.ftgroup>> <54EF2C9A.3040008@joelhalpern.com<http://www.ietf.or=
g/mail-archive/web/sfc/current/msg03181.html>>
  *   List-id: Network Service Chaining <sfc.ietf.org>

________________________________

Hi,



Jumping in mid-thread.



Overall, I tend to agree with Joel.  Having an explicit version provides a =
simple way to handle dataplane format changes.  As Med points out, quickly =
correctly, IMHO, there are other way to signal changes via reserved bit.  I=
n practice though reserved bits are less useful since the convention is to =
ignore unknown bits, it makes using them for feature changes quite difficul=
t, which then brings up back to explicit versioning that cannot be ignored.



I think Joel's suggestion below makes perfect sense and should be added to =
the draft.



Paul





> On Feb 26, 2015, at 9:24 AM, Joel M. Halpern <jmh at joelhalpern.com> wro=
te:

>

> In one sense you are correct.  If you could count on everything being upg=
raded at once, sure you could just assume common interpretation.

> However, we have found over the years that such simultaneous upgrading ne=
ver works.  You need to be able to transition.

>

> I do agree that we should add text about what to do with version numbers =
that are not understood.  There are multiple choices that affect how we can=
 make changes.  My personal preference is:

>

> If an packet presumed to carry an NSH header is received at an SFF, and t=
he SFF does not understnad the version of the protocol as indicated in the =
base header, the packet MUST be discarded, and the event SHOULD be logged.

>

> This would allow an orderly transition, where devices can be upgraded to =
understand a new version, then generation of the new version header can be =
enabled.  If a configuration error is made, the packets will be dropped and=
 operators following good practices will get notifications.

>

> Yours,

> Joel

>

> On 2/26/15 2:16 AM, mohamed.boucadair at orange.com wrote:

>> Hi Joel,

>>

>> I fully agree with the extendibility of the header, but the question is =
why having a version number will be of help in the context of SFC? Second, =
having a version number without specifying the behavior when several versio=
ns are supported, when the version number is not supported by an SFC-aware =
element, etc. leaves open issues out of the spec.

>>

>> The other problem is that the current I-D includes several open doors le=
ft for extending the header:

>> * version

>> * reserved bits

>> * optional data

>>

>> This is too much for a header that is supposed to be compact and simple!

>>

>> There are other means to extend the header without signaling the version=
 in the packet. Having a distinct RFC number may be just fine in the contex=
t of an unidirectional stream such as SFC.

>>

>> Let us consider the situation where a version number is not explicitly s=
ignaled in the packet (but a new RFC updates the base SFC header). Several =
options can be considered, indeed (those are provided as examples for illus=
tration purposes):

>> * An operator can make sure that its SFC-enabled domain is configured in=
 a consistent manner to support one and only one version of the header. No =
interoperability issues is encountered in this case.

>> * An operator that wants to upgrade its SFC-enabled domain to support a =
new specification of the SFC header: An operator can decide to proceed to a=
 software/hardware updates but can maintain the old header in operation unt=
il all involved elements are upgraded to support the new version. Once the =
SFC-enabled domain is upgraded, then the new header can be enabled.

>>

>> Let's consider now that a version is signaled in the packet: to what ext=
ent signaling this information simplifies the SFC operations, and whether i=
t increases/decreases the serviceability of an SFC-enabled domain? Let's al=
so assess to what extent having the version number add more complexity in t=
he SFC header treatment when several versions are supported by a node/withi=
n an SFC enabled domain? How it helps interoperability? Some points for dis=
cussion are elaborated below:

>>

>> * If the SFC-enabled domain is configured to support the same version (w=
hich is likely): having the version number is not of any help.

>> * If the SFC-enabled domain involves some nodes that support version (v1=
) while others support (v2) (simple case): If these version are not backwar=
d compatible, this will lead to failures when two adjacent elements in a se=
rvice chain do not support the same version. The SFC system is broken. Havi=
ng the version number is not of any help in this case.

>> * If the SFC-enabled domain involves some nodes that support version (v1=
) while others support (v1 and v2):

>>

>> (a) The nodes that support both v1 and v2 should be instructed to decide=
 which version to be used. This can be either part of the specification or =
be driven by configuration. If a version number is included in the spec, I =
would expect to clarify the behavior in such case.

>>

>> (b) Suppose a node that supports only v1 receives a packet with header (=
v2): If this node does not support a notification procedure to inform the s=
ource that it does not support that header version, then FAILURES are intro=
duced in the network. This is a degradation of the service compared to lega=
cy scheme to structure services. This is not recommended, IMHO.

>>

>> (c) If a notification is received from an element about its supported ve=
rsion: a node can use another version (the logic to select other version is=
 another point to discuss) for that communication, but what to do for the n=
ext flows in the context of the same service chain or other chains that inv=
olves these two nodes as adjacent elements in the same chain? Shouldn't the=
se nodes cache the version to use for subsequent exchange to avoid receivin=
g the notification error each time? Wouldn't that complexity the behavior o=
f the SFC-aware elements?

>>

>> (d) If a notification is received from an element about its supported ve=
rsion: As this may occurs in various segments of a given service chain, e.g=
., (A(v1), B(v1,v2), C(v2), D(v1,v2), E(v1)). Notifying the adjacent node e=
ach time there is a version mismatch induce an extra delay, that may be not=
 be acceptable for every flow.

>>

>> I hope this clarifies my initial concern.

>>

>> Thank you.

>>

>> Cheers,

>> Med

>>

>>> -----Message d'origine-----

>>> De : Joel M. Halpern [mailto:jmh at joelhalpern.com]

>>> Envoy=E9 : mercredi 25 f=E9vrier 2015 16:10

>>> =C0 : BOUCADAIR Mohamed IMT/OLN; paulq at cisco.com

>>> Cc : sfc at ietf.org

>>> Objet : Re: [sfc] draft-quinn-sfc-nsh: version number

>>>

>>> I would really prefer to keep the version number.  Even though we have

>>> the MD-type identifier and for some MD we have the TLVs.

>>>

>>> The reason is that we may want to change the base header.  For example,

>>> suppose that the ciscussion about including a flow identifier in the

>>> base header had not come up now.  If it came up later, we would want to

>>> be able to have the discussion and make the choice, rather than being

>>> constrained by the lack of a version field.

>>>

>>> Yours,

>>> Joel

>>>

>>>

>>> On 2/25/15 10:03 AM, mohamed.boucadair at orange.com wrote:

>>>> Hi Paul, all,

>>>>

>>>> What is the purpose of having a version number in the header? Is there=
 a

>>>> kind of version negotiation that needs to be in place?

>>>>

>>>> I checked the I-D but failed to find text that explains the rationale,

>>>> the use of the such field and whether an error will be returned if the

>>>> version is not supported by the receiving node.

>>>>

>>>> Wouldn't be preferable to get rid of this field given that SFC header

>>>> can be extended using optional objects and consistent setup &

>>>> configuration within an SFC-enabled domain should be assumed?

>>>>

>>>> Thank you

>>>>

>>>> Cheers,

>>>>

>>>> Med

>>>>

>>>>

>>>>

>>>> _______________________________________________

>>>> sfc mailing list

>>>> sfc at ietf.org

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

>>>>

>>




--_000_787AE7BB302AE849A7480A190F8B93300491A1AFOPEXCLILM23corp_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Cambria;
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"Segoe UI";
	panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
h1
	{mso-style-priority:9;
	mso-style-link:"Titre 1 Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	font-weight:normal;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Texte brut Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"Pr=E9format=E9 HTML Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Texte de bulles Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.Titre1Car
	{mso-style-name:"Titre 1 Car";
	mso-style-priority:9;
	mso-style-link:"Titre 1";
	font-family:"Cambria","serif";
	color:#365F91;
	font-weight:bold;}
span.PrformatHTMLCar
	{mso-style-name:"Pr=E9format=E9 HTML Car";
	mso-style-priority:99;
	mso-style-link:"Pr=E9format=E9 HTML";
	font-family:Consolas;}
span.TextebrutCar
	{mso-style-name:"Texte brut Car";
	mso-style-priority:99;
	mso-style-link:"Texte brut";
	font-family:"Courier New";
	color:black;
	mso-fareast-language:EN-US;}
span.TextedebullesCar
	{mso-style-name:"Texte de bulles Car";
	mso-style-priority:99;
	mso-style-link:"Texte de bulles";
	font-family:"Tahoma","sans-serif";}
p.Heading1, li.Heading1, div.Heading1
	{mso-style-name:"Heading 1";
	mso-style-link:"Heading 1 Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.Heading1Char
	{mso-style-name:"Heading 1 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 1";
	font-family:"Times New Roman","serif";
	font-weight:bold;}
p.HTMLPreformatted, li.HTMLPreformatted, div.HTMLPreformatted
	{mso-style-name:"HTML Preformatted";
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
p.PlainText, li.PlainText, div.PlainText
	{mso-style-name:"Plain Text";
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
p.BalloonText, li.BalloonText, div.BalloonText
	{mso-style-name:"Balloon Text";
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Segoe UI","sans-serif";}
span.EmailStyle32
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle33
	{mso-style-type:personal;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;}
span.EmailStyle34
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle36
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:2139057662;
	mso-list-template-ids:-391481046;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"FR" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Hi Ron,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">If the version number is mainta=
ined, discussing the behavior of a node if it supports several versions, if=
 it does not support the version of a packet it
 receives, etc. is not about OAM. This is part of the behavior that needs t=
o be specified in the document.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Cheers,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Med<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">De&nbsp;:</span></b><span style=3D"fo=
nt-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Ron =
Parker [mailto:Ron_Parker@affirmednetworks.com]
<br>
<b>Envoy=E9&nbsp;:</b> mercredi 4 mars 2015 16:03<br>
<b>=C0&nbsp;:</b> BOUCADAIR Mohamed IMT/OLN; Sunil Vallamkonda<br>
<b>Cc&nbsp;:</b> sfc@ietf.org<br>
<b>Objet&nbsp;:</b> RE: Re: [sfc] draft-quinn-sfc-nsh: version number<o:p><=
/o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">When we=
 take up OAM, we could consider these ICMP-like behaviors &#8211; i.e., OAM=
 packet containing &#8220;Version Incompatible&#8221; sent in the reverse d=
irection on the involved RSP.&nbsp;&nbsp; But I&#8217;m not sure what shoul=
d
 be discussed in this draft, since OAM is explicitly out of scope.<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp; Ron<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><a name=3D"_MailEndCompose"></a><span lang=3D"EN-US"=
 style=3D"color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US">From:</span></b><span lang=
=3D"EN-US"> sfc [<a href=3D"mailto:sfc-bounces@ietf.org">mailto:sfc-bounces=
@ietf.org</a>]
<b>On Behalf Of </b><a href=3D"mailto:mohamed.boucadair@orange.com">mohamed=
.boucadair@orange.com</a><br>
<b>Sent:</b> Wednesday, March 4, 2015 1:47 AM<br>
<b>To:</b> Sunil Vallamkonda<br>
<b>Cc:</b> <a href=3D"mailto:sfc@ietf.org">sfc@ietf.org</a><br>
<b>Subject:</b> Re: [sfc] draft-quinn-sfc-nsh: version number<o:p></o:p></s=
pan></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Hi Sunil,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">There is no such notification i=
n the current spec.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Below my thoughts about this po=
int:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">=3D=3D<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Courier New&quot;;color:black">(b) Suppose a node that supp=
orts only v1 receives a packet with header (v2): If this node does not supp=
ort a notification procedure to inform the source
 that it does not support that header version, then FAILURES are introduced=
 in the network. This is a degradation of the service compared to legacy sc=
heme to structure services. This is not recommended, IMHO.<o:p></o:p></span=
></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Courier New&quot;;color:black">(c) If a notification is rec=
eived from an element about its supported version: a node can use another v=
ersion (the logic to select other version is another
 point to discuss) for that communication, but what to do for the next flow=
s in the context of the same service chain or other chains that involves th=
ese two nodes as adjacent elements in the same chain? Shouldn't these nodes=
 cache the version to use for subsequent
 exchange to avoid receiving the notification error each time? Wouldn't tha=
t complexity the behavior of the SFC-aware elements?<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Courier New&quot;;color:black">(d) If a notification is rec=
eived from an element about its supported version: As this may occurs in va=
rious segments of a given service chain, e.g., (A(v1),
 B(v1,v2), C(v1), D(v1,v2), E(v1)). Notifying the adjacent node each time t=
here is a version mismatch induce an extra delay, that may be not be accept=
able for every flow.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">=3D=3D<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Thank you.<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Cheers,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Med<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">De&nbsp;:</span></b><span style=3D"fo=
nt-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> sfc =
[<a href=3D"mailto:sfc-bounces@ietf.org">mailto:sfc-bounces@ietf.org</a>]
<b>De la part de</b> Sunil Vallamkonda<br>
<b>Envoy=E9&nbsp;:</b> mardi 3 mars 2015 20:43<br>
<b>=C0&nbsp;:</b> <a href=3D"mailto:sfc@ietf.org">sfc@ietf.org</a><br>
<b>Objet&nbsp;:</b> Re: [sfc] draft-quinn-sfc-nsh: version number<o:p></o:p=
></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hi,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Just going through the thread o=
n version number (jumping in mid-thread),<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Apart from the version mismatch=
ed (unsupported) packet dropped and logged, is there a plan for a back off =
mechanism by SFF to notify sender and avoid being overwhelmed with such pac=
kets ?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Thank you,<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Sunil.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;<o:p></o:p></span></p>
<h1 style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang=
=3D"EN-US" style=3D"font-size:14.0pt;font-family:&quot;Times New Roman&quot=
;,&quot;serif&quot;">Re: [sfc] draft-quinn-sfc-nsh: version number</span><b=
><span lang=3D"EN-US" style=3D"font-size:24.0pt;font-family:&quot;Times New=
 Roman&quot;,&quot;serif&quot;"><o:p></o:p></span></b></h1>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 lang=3D"EN-US">
<hr size=3D"2" width=3D"100%" align=3D"center">
</span></div>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto;mso-list:l0 level1 lfo1">
<em><span lang=3D"EN-US" style=3D"font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;;mso-fareast-language:EN-US">From</span></em><span lang=3D"EN-=
US" style=3D"mso-fareast-language:EN-US">: &quot;Paul Quinn (paulq)&quot; &=
lt;<a href=3D"mailto:paulq@DOMAIN.HIDDEN">paulq at cisco.com</a>&gt;<o:p></=
o:p></span></li><li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;ms=
o-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<em><span lang=3D"EN-US" style=3D"font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;;mso-fareast-language:EN-US">To</span></em><span lang=3D"EN-US=
" style=3D"mso-fareast-language:EN-US">: &quot;Joel M. Halpern&quot; &lt;<a=
 href=3D"mailto:jmh@DOMAIN.HIDDEN">jmh at joelhalpern.com</a>&gt;<o:p></o:p=
></span></li><li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-m=
argin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<em><span lang=3D"EN-US" style=3D"font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;;mso-fareast-language:EN-US">Cc</span></em><span lang=3D"EN-US=
" style=3D"mso-fareast-language:EN-US">: &quot;<a href=3D"mailto:mohamed.bo=
ucadair@DOMAIN.HIDDEN">mohamed.boucadair at orange.com</a>&quot; &lt;<a hre=
f=3D"mailto:mohamed.boucadair@DOMAIN.HIDDEN">mohamed.boucadair
 at orange.com</a>&gt;, &quot;<a href=3D"mailto:sfc@DOMAIN.HIDDEN">sfc at i=
etf.org</a>&quot; &lt;<a href=3D"mailto:sfc@DOMAIN.HIDDEN">sfc at ietf.org<=
/a>&gt;<o:p></o:p></span></li><li class=3D"MsoNormal" style=3D"mso-margin-t=
op-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<em><span lang=3D"EN-US" style=3D"font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;;mso-fareast-language:EN-US">Date</span></em><span lang=3D"EN-=
US" style=3D"mso-fareast-language:EN-US">: Mon, 2 Mar 2015 17:50:53 &#43;00=
00<o:p></o:p></span></li><li class=3D"MsoNormal" style=3D"mso-margin-top-al=
t:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<em><span lang=3D"EN-US" style=3D"font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;;mso-fareast-language:EN-US">In-reply-to</span></em><span lang=
=3D"EN-US" style=3D"mso-fareast-language:EN-US">: &lt;<a href=3D"http://www=
.ietf.org/mail-archive/web/sfc/current/msg03181.html">54EF2C9A.3040008@joel=
halpern.com</a>&gt;<o:p></o:p></span></li><li class=3D"MsoNormal" style=3D"=
mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1"=
>
<em><span lang=3D"EN-US" style=3D"font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;;mso-fareast-language:EN-US">References</span></em><span lang=
=3D"EN-US" style=3D"mso-fareast-language:EN-US">: &lt;<a href=3D"mailto:787=
AE7BB302AE849A7480A190F8B9330049140B4@OPEXCLILM23.corporate.adroot.infra.ft=
group">787AE7BB302AE849A7480A190F8B9330049140B4@OPEXCLILM23.corporate.adroo=
t.infra.ftgroup</a>&gt;
 &lt;<a href=3D"http://www.ietf.org/mail-archive/web/sfc/current/msg03151.h=
tml">54EDE5B7.6080102@joelhalpern.com</a>&gt; &lt;<a href=3D"mailto:787AE7B=
B302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.adroot.infra.ftgrou=
p">787AE7BB302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.adroot.in=
fra.ftgroup</a>&gt;
 &lt;<a href=3D"http://www.ietf.org/mail-archive/web/sfc/current/msg03181.h=
tml">54EF2C9A.3040008@joelhalpern.com</a>&gt;<o:p></o:p></span></li><li cla=
ss=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:aut=
o;mso-list:l0 level1 lfo1">
<em><span lang=3D"EN-US" style=3D"font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;;mso-fareast-language:EN-US">List-id</span></em><span lang=3D"=
EN-US" style=3D"mso-fareast-language:EN-US">: Network Service Chaining &lt;=
sfc.ietf.org&gt;<o:p></o:p></span></li></ul>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 lang=3D"EN-US">
<hr size=3D"2" width=3D"100%" align=3D"center">
</span></div>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">Hi,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&nbsp;<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">Jumping in mid-thread.&nbsp; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&nbsp;<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">Overall, I tend to agree with Joel.&nbsp; Having an explicit =
version provides a simple way to handle dataplane format changes.&nbsp; As =
Med points out, quickly correctly, IMHO, there are other way to signal chan=
ges via reserved bit.&nbsp; In practice though reserved bits are less usefu=
l since the convention is to ignore unknown bits, it makes using them for f=
eature changes quite difficult, which then brings up back to explicit versi=
oning that cannot be ignored.&nbsp; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&nbsp;<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">I think Joel&#8217;s suggestion below makes perfect sense and=
 should be added to the draft.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&nbsp;<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">Paul<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&nbsp;<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&nbsp;<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt; On Feb 26, 2015, at 9:24 AM, Joel M. Halpern &lt;jmh at =
joelhalpern.com&gt; wrote:<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt; In one sense you are correct.&nbsp; If you could count o=
n everything being upgraded at once, sure you could just assume common inte=
rpretation.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt; However, we have found over the years that such simultan=
eous upgrading never works.&nbsp; You need to be able to transition.<o:p></=
o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt; I do agree that we should add text about what to do with=
 version numbers that are not understood.&nbsp; There are multiple choices =
that affect how we can make changes.&nbsp; My personal preference is:<o:p><=
/o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt; If an packet presumed to carry an NSH header is received=
 at an SFF, and the SFF does not understnad the version of the protocol as =
indicated in the base header, the packet MUST be discarded, and the event S=
HOULD be logged.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt; This would allow an orderly transition, where devices ca=
n be upgraded to understand a new version, then generation of the new versi=
on header can be enabled.&nbsp; If a configuration error is made, the packe=
ts will be dropped and operators following good practices will get notifica=
tions.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt; Yours,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt; Joel<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt; On 2/26/15 2:16 AM, mohamed.boucadair at orange.com wrot=
e:<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; Hi Joel,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; I fully agree with the extendibility of the header, =
but the question is why having a version number will be of help in the cont=
ext of SFC? Second, having a version number without specifying the behavior=
 when several versions are supported, when the version number is not suppor=
ted by an SFC-aware element, etc. leaves open issues out of the spec.<o:p><=
/o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; The other problem is that the current I-D includes s=
everal open doors left for extending the header:<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; * version<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; * reserved bits<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; * optional data<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; This is too much for a header that is supposed to be=
 compact and simple!<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; There are other means to extend the header without s=
ignaling the version in the packet. Having a distinct RFC number may be jus=
t fine in the context of an unidirectional stream such as SFC.<o:p></o:p></=
span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; Let us consider the situation where a version number=
 is not explicitly signaled in the packet (but a new RFC updates the base S=
FC header). Several options can be considered, indeed (those are provided a=
s examples for illustration purposes):<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; * An operator can make sure that its SFC-enabled dom=
ain is configured in a consistent manner to support one and only one versio=
n of the header. No interoperability issues is encountered in this case.<o:=
p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; * An operator that wants to upgrade its SFC-enabled =
domain to support a new specification of the SFC header: An operator can de=
cide to proceed to a software/hardware updates but can maintain the old hea=
der in operation until all involved elements are upgraded to support the ne=
w version. Once the SFC-enabled domain is upgraded, then the new header can=
 be enabled.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; Let's consider now that a version is signaled in the=
 packet: to what extent signaling this information simplifies the SFC opera=
tions, and whether it increases/decreases the serviceability of an SFC-enab=
led domain? Let's also assess to what extent having the version number add =
more complexity in the SFC header treatment when several versions are suppo=
rted by a node/within an SFC enabled domain? How it helps interoperability?=
 Some points for discussion are elaborated below:<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; * If the SFC-enabled domain is configured to support=
 the same version (which is likely): having the version number is not of an=
y help.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; * If the SFC-enabled domain involves some nodes that=
 support version (v1) while others support (v2) (simple case): If these ver=
sion are not backward compatible, this will lead to failures when two adjac=
ent elements in a service chain do not support the same version. The SFC sy=
stem is broken. Having the version number is not of any help in this case.<=
o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; * If the SFC-enabled domain involves some nodes that=
 support version (v1) while others support (v1 and v2):<o:p></o:p></span></=
pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; (a) The nodes that support both v1 and v2 should be =
instructed to decide which version to be used. This can be either part of t=
he specification or be driven by configuration. If a version number is incl=
uded in the spec, I would expect to clarify the behavior in such case.<o:p>=
</o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; (b) Suppose a node that supports only v1 receives a =
packet with header (v2): If this node does not support a notification proce=
dure to inform the source that it does not support that header version, the=
n FAILURES are introduced in the network. This is a degradation of the serv=
ice compared to legacy scheme to structure services. This is not recommende=
d, IMHO.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; (c) If a notification is received from an element ab=
out its supported version: a node can use another version (the logic to sel=
ect other version is another point to discuss) for that communication, but =
what to do for the next flows in the context of the same service chain or o=
ther chains that involves these two nodes as adjacent elements in the same =
chain? Shouldn't these nodes cache the version to use for subsequent exchan=
ge to avoid receiving the notification error each time? Wouldn't that compl=
exity the behavior of the SFC-aware elements?<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; (d) If a notification is received from an element ab=
out its supported version: As this may occurs in various segments of a give=
n service chain, e.g., (A(v1), B(v1,v2), C(v2), D(v1,v2), E(v1)). Notifying=
 the adjacent node each time there is a version mismatch induce an extra de=
lay, that may be not be acceptable for every flow.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; I hope this clarifies my initial concern.<o:p></o:p>=
</span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; Thank you.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; Cheers,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; Med<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; -----Message d'origine-----<o:p></o:p></span></p=
re>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; De : Joel M. Halpern [<a href=3D"mailto:jmh">mai=
lto:jmh</a> at joelhalpern.com]<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; Envoy=E9 : mercredi 25 f=E9vrier 2015 16:10<o:p>=
</o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; =C0 : BOUCADAIR Mohamed IMT/OLN; paulq at cisco.=
com<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; Cc : sfc at ietf.org<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; Objet : Re: [sfc] draft-quinn-sfc-nsh: version n=
umber<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; I would really prefer to keep the version number=
.&nbsp; Even though we have<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; the MD-type identifier and for some MD we have t=
he TLVs.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; The reason is that we may want to change the bas=
e header.&nbsp; For example,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; suppose that the ciscussion about including a fl=
ow identifier in the<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; base header had not come up now.&nbsp; If it cam=
e up later, we would want to<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; be able to have the discussion and make the choi=
ce, rather than being<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; constrained by the lack of a version field.<o:p>=
</o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; Yours,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; Joel<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; On 2/25/15 10:03 AM, mohamed.boucadair at orange=
.com wrote:<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; Hi Paul, all,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; What is the purpose of having a version numb=
er in the header? Is there a<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; kind of version negotiation that needs to be=
 in place?<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; I checked the I-D but failed to find text th=
at explains the rationale,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; the use of the such field and whether an err=
or will be returned if the<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; version is not supported by the receiving no=
de.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; Wouldn't be preferable to get rid of this fi=
eld given that SFC header<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; can be extended using optional objects and c=
onsistent setup &amp;<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; configuration within an SFC-enabled domain s=
hould be assumed?<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; Thank you<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; Cheers,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; Med<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; ____________________________________________=
___<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; sfc mailing list<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; sfc at ietf.org<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/list=
info/sfc">https://www.ietf.org/mailman/listinfo/sfc</a><o:p></o:p></span></=
pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&nbsp;<o:p></o:p></span></pre>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;<o:p></o:p></span></p>
</div>
</div>
</div>
</body>
</html>

--_000_787AE7BB302AE849A7480A190F8B93300491A1AFOPEXCLILM23corp_--


From nobody Wed Mar  4 07:50:31 2015
Return-Path: <Ron_Parker@affirmednetworks.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1F6F1A8AD2 for <sfc@ietfa.amsl.com>; Wed,  4 Mar 2015 07:50:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 d4yD1rSRRYnd for <sfc@ietfa.amsl.com>; Wed,  4 Mar 2015 07:50:11 -0800 (PST)
Received: from hub021-ca-5.exch021.serverdata.net (hub021-ca-5.exch021.serverdata.net [64.78.56.70]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0A361A1AA6 for <sfc@ietf.org>; Wed,  4 Mar 2015 07:50:11 -0800 (PST)
Received: from MBX021-W3-CA-2.exch021.domain.local ([10.254.4.78]) by HUB021-CA-5.exch021.domain.local ([10.254.4.89]) with mapi id 14.03.0224.002;  Wed, 4 Mar 2015 07:50:11 -0800
From: Ron Parker <Ron_Parker@affirmednetworks.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "Sunil Vallamkonda" <sunilvk@f5.com>
Thread-Topic: Re: [sfc] draft-quinn-sfc-nsh: version number
Thread-Index: AdBV6VnhN9N2Adv/Rs2PZVkjw6sDlQAXRdTwABFWhuAAAVpygAAAT27g
Date: Wed, 4 Mar 2015 15:50:09 +0000
Message-ID: <CDF2F015F4429F458815ED2A6C2B6B0B2E8558D0@MBX021-W3-CA-2.exch021.domain.local>
References: <01f9e1a4e6514854a26556e4c6a3e36e@SEAEXCHMBX05.olympus.F5Net.com> <787AE7BB302AE849A7480A190F8B933004919B76@OPEXCLILM23.corporate.adroot.infra.ftgroup> <CDF2F015F4429F458815ED2A6C2B6B0B2E85379B@MBX021-W3-CA-2.exch021.domain.local> <787AE7BB302AE849A7480A190F8B93300491A1AF@OPEXCLILM23.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B93300491A1AF@OPEXCLILM23.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [50.203.66.100]
Content-Type: multipart/alternative; boundary="_000_CDF2F015F4429F458815ED2A6C2B6B0B2E8558D0MBX021W3CA2exch_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/5axCYQo6OgHjQcgtMkXULrAhtFo>
Cc: "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] draft-quinn-sfc-nsh: version number
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 04 Mar 2015 15:50:20 -0000

--_000_CDF2F015F4429F458815ED2A6C2B6B0B2E8558D0MBX021W3CA2exch_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Med,

I agree that we should add additional text around the expected behavior reg=
arding version incompatibility.   We could state that the SFF or SF perceiv=
ing this incompatibility MUST drop such a packet and MAY generate an OAM re=
sponse in the reverse direction, although the exact nature of that response=
 is outside the scope of the NSH draft.

   Ron





From: mohamed.boucadair@orange.com [mailto:mohamed.boucadair@orange.com]
Sent: Wednesday, March 4, 2015 10:43 AM
To: Ron Parker; Sunil Vallamkonda
Cc: sfc@ietf.org
Subject: RE: Re: [sfc] draft-quinn-sfc-nsh: version number

Hi Ron,

If the version number is maintained, discussing the behavior of a node if i=
t supports several versions, if it does not support the version of a packet=
 it receives, etc. is not about OAM. This is part of the behavior that need=
s to be specified in the document.

Cheers,
Med


De : Ron Parker [mailto:Ron_Parker@affirmednetworks.com]
Envoy=E9 : mercredi 4 mars 2015 16:03
=C0 : BOUCADAIR Mohamed IMT/OLN; Sunil Vallamkonda
Cc : sfc@ietf.org<mailto:sfc@ietf.org>
Objet : RE: Re: [sfc] draft-quinn-sfc-nsh: version number

When we take up OAM, we could consider these ICMP-like behaviors - i.e., OA=
M packet containing "Version Incompatible" sent in the reverse direction on=
 the involved RSP.   But I'm not sure what should be discussed in this draf=
t, since OAM is explicitly out of scope.

   Ron



From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of mohamed.boucadair@oran=
ge.com<mailto:mohamed.boucadair@orange.com>
Sent: Wednesday, March 4, 2015 1:47 AM
To: Sunil Vallamkonda
Cc: sfc@ietf.org<mailto:sfc@ietf.org>
Subject: Re: [sfc] draft-quinn-sfc-nsh: version number

Hi Sunil,

There is no such notification in the current spec.

Below my thoughts about this point:

=3D=3D

(b) Suppose a node that supports only v1 receives a packet with header (v2)=
: If this node does not support a notification procedure to inform the sour=
ce that it does not support that header version, then FAILURES are introduc=
ed in the network. This is a degradation of the service compared to legacy =
scheme to structure services. This is not recommended, IMHO.



(c) If a notification is received from an element about its supported versi=
on: a node can use another version (the logic to select other version is an=
other point to discuss) for that communication, but what to do for the next=
 flows in the context of the same service chain or other chains that involv=
es these two nodes as adjacent elements in the same chain? Shouldn't these =
nodes cache the version to use for subsequent exchange to avoid receiving t=
he notification error each time? Wouldn't that complexity the behavior of t=
he SFC-aware elements?



(d) If a notification is received from an element about its supported versi=
on: As this may occurs in various segments of a given service chain, e.g., =
(A(v1), B(v1,v2), C(v1), D(v1,v2), E(v1)). Notifying the adjacent node each=
 time there is a version mismatch induce an extra delay, that may be not be=
 acceptable for every flow.
=3D=3D

Thank you.

Cheers,
Med


De : sfc [mailto:sfc-bounces@ietf.org] De la part de Sunil Vallamkonda
Envoy=E9 : mardi 3 mars 2015 20:43
=C0 : sfc@ietf.org<mailto:sfc@ietf.org>
Objet : Re: [sfc] draft-quinn-sfc-nsh: version number

Hi,

Just going through the thread on version number (jumping in mid-thread),

Apart from the version mismatched (unsupported) packet dropped and logged, =
is there a plan for a back off mechanism by SFF to notify sender and avoid =
being overwhelmed with such packets ?

Thank you,
Sunil.


Re: [sfc] draft-quinn-sfc-nsh: version number
________________________________

  *   From: "Paul Quinn (paulq)" <paulq at cisco.com<mailto:paulq@DOMAIN.HI=
DDEN>>
  *   To: "Joel M. Halpern" <jmh at joelhalpern.com<mailto:jmh@DOMAIN.HIDDE=
N>>
  *   Cc: "mohamed.boucadair at orange.com<mailto:mohamed.boucadair@DOMAIN.=
HIDDEN>" <mohamed.boucadair at orange.com<mailto:mohamed.boucadair@DOMAIN.H=
IDDEN>>, "sfc at ietf.org<mailto:sfc@DOMAIN.HIDDEN>" <sfc at ietf.org<mailt=
o:sfc@DOMAIN.HIDDEN>>
  *   Date: Mon, 2 Mar 2015 17:50:53 +0000
  *   In-reply-to: <54EF2C9A.3040008@joelhalpern.com<http://www.ietf.org/ma=
il-archive/web/sfc/current/msg03181.html>>
  *   References: <787AE7BB302AE849A7480A190F8B9330049140B4@OPEXCLILM23.cor=
porate.adroot.infra.ftgroup<mailto:787AE7BB302AE849A7480A190F8B9330049140B4=
@OPEXCLILM23.corporate.adroot.infra.ftgroup>> <54EDE5B7.6080102@joelhalpern=
.com<http://www.ietf.org/mail-archive/web/sfc/current/msg03151.html>> <787A=
E7BB302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.adroot.infra.ftg=
roup<mailto:787AE7BB302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.=
adroot.infra.ftgroup>> <54EF2C9A.3040008@joelhalpern.com<http://www.ietf.or=
g/mail-archive/web/sfc/current/msg03181.html>>
  *   List-id: Network Service Chaining <sfc.ietf.org>

________________________________

Hi,



Jumping in mid-thread.



Overall, I tend to agree with Joel.  Having an explicit version provides a =
simple way to handle dataplane format changes.  As Med points out, quickly =
correctly, IMHO, there are other way to signal changes via reserved bit.  I=
n practice though reserved bits are less useful since the convention is to =
ignore unknown bits, it makes using them for feature changes quite difficul=
t, which then brings up back to explicit versioning that cannot be ignored.



I think Joel's suggestion below makes perfect sense and should be added to =
the draft.



Paul





> On Feb 26, 2015, at 9:24 AM, Joel M. Halpern <jmh at joelhalpern.com> wro=
te:

>

> In one sense you are correct.  If you could count on everything being upg=
raded at once, sure you could just assume common interpretation.

> However, we have found over the years that such simultaneous upgrading ne=
ver works.  You need to be able to transition.

>

> I do agree that we should add text about what to do with version numbers =
that are not understood.  There are multiple choices that affect how we can=
 make changes.  My personal preference is:

>

> If an packet presumed to carry an NSH header is received at an SFF, and t=
he SFF does not understnad the version of the protocol as indicated in the =
base header, the packet MUST be discarded, and the event SHOULD be logged.

>

> This would allow an orderly transition, where devices can be upgraded to =
understand a new version, then generation of the new version header can be =
enabled.  If a configuration error is made, the packets will be dropped and=
 operators following good practices will get notifications.

>

> Yours,

> Joel

>

> On 2/26/15 2:16 AM, mohamed.boucadair at orange.com wrote:

>> Hi Joel,

>>

>> I fully agree with the extendibility of the header, but the question is =
why having a version number will be of help in the context of SFC? Second, =
having a version number without specifying the behavior when several versio=
ns are supported, when the version number is not supported by an SFC-aware =
element, etc. leaves open issues out of the spec.

>>

>> The other problem is that the current I-D includes several open doors le=
ft for extending the header:

>> * version

>> * reserved bits

>> * optional data

>>

>> This is too much for a header that is supposed to be compact and simple!

>>

>> There are other means to extend the header without signaling the version=
 in the packet. Having a distinct RFC number may be just fine in the contex=
t of an unidirectional stream such as SFC.

>>

>> Let us consider the situation where a version number is not explicitly s=
ignaled in the packet (but a new RFC updates the base SFC header). Several =
options can be considered, indeed (those are provided as examples for illus=
tration purposes):

>> * An operator can make sure that its SFC-enabled domain is configured in=
 a consistent manner to support one and only one version of the header. No =
interoperability issues is encountered in this case.

>> * An operator that wants to upgrade its SFC-enabled domain to support a =
new specification of the SFC header: An operator can decide to proceed to a=
 software/hardware updates but can maintain the old header in operation unt=
il all involved elements are upgraded to support the new version. Once the =
SFC-enabled domain is upgraded, then the new header can be enabled.

>>

>> Let's consider now that a version is signaled in the packet: to what ext=
ent signaling this information simplifies the SFC operations, and whether i=
t increases/decreases the serviceability of an SFC-enabled domain? Let's al=
so assess to what extent having the version number add more complexity in t=
he SFC header treatment when several versions are supported by a node/withi=
n an SFC enabled domain? How it helps interoperability? Some points for dis=
cussion are elaborated below:

>>

>> * If the SFC-enabled domain is configured to support the same version (w=
hich is likely): having the version number is not of any help.

>> * If the SFC-enabled domain involves some nodes that support version (v1=
) while others support (v2) (simple case): If these version are not backwar=
d compatible, this will lead to failures when two adjacent elements in a se=
rvice chain do not support the same version. The SFC system is broken. Havi=
ng the version number is not of any help in this case.

>> * If the SFC-enabled domain involves some nodes that support version (v1=
) while others support (v1 and v2):

>>

>> (a) The nodes that support both v1 and v2 should be instructed to decide=
 which version to be used. This can be either part of the specification or =
be driven by configuration. If a version number is included in the spec, I =
would expect to clarify the behavior in such case.

>>

>> (b) Suppose a node that supports only v1 receives a packet with header (=
v2): If this node does not support a notification procedure to inform the s=
ource that it does not support that header version, then FAILURES are intro=
duced in the network. This is a degradation of the service compared to lega=
cy scheme to structure services. This is not recommended, IMHO.

>>

>> (c) If a notification is received from an element about its supported ve=
rsion: a node can use another version (the logic to select other version is=
 another point to discuss) for that communication, but what to do for the n=
ext flows in the context of the same service chain or other chains that inv=
olves these two nodes as adjacent elements in the same chain? Shouldn't the=
se nodes cache the version to use for subsequent exchange to avoid receivin=
g the notification error each time? Wouldn't that complexity the behavior o=
f the SFC-aware elements?

>>

>> (d) If a notification is received from an element about its supported ve=
rsion: As this may occurs in various segments of a given service chain, e.g=
., (A(v1), B(v1,v2), C(v2), D(v1,v2), E(v1)). Notifying the adjacent node e=
ach time there is a version mismatch induce an extra delay, that may be not=
 be acceptable for every flow.

>>

>> I hope this clarifies my initial concern.

>>

>> Thank you.

>>

>> Cheers,

>> Med

>>

>>> -----Message d'origine-----

>>> De : Joel M. Halpern [mailto:jmh at joelhalpern.com]

>>> Envoy=E9 : mercredi 25 f=E9vrier 2015 16:10

>>> =C0 : BOUCADAIR Mohamed IMT/OLN; paulq at cisco.com

>>> Cc : sfc at ietf.org

>>> Objet : Re: [sfc] draft-quinn-sfc-nsh: version number

>>>

>>> I would really prefer to keep the version number.  Even though we have

>>> the MD-type identifier and for some MD we have the TLVs.

>>>

>>> The reason is that we may want to change the base header.  For example,

>>> suppose that the ciscussion about including a flow identifier in the

>>> base header had not come up now.  If it came up later, we would want to

>>> be able to have the discussion and make the choice, rather than being

>>> constrained by the lack of a version field.

>>>

>>> Yours,

>>> Joel

>>>

>>>

>>> On 2/25/15 10:03 AM, mohamed.boucadair at orange.com wrote:

>>>> Hi Paul, all,

>>>>

>>>> What is the purpose of having a version number in the header? Is there=
 a

>>>> kind of version negotiation that needs to be in place?

>>>>

>>>> I checked the I-D but failed to find text that explains the rationale,

>>>> the use of the such field and whether an error will be returned if the

>>>> version is not supported by the receiving node.

>>>>

>>>> Wouldn't be preferable to get rid of this field given that SFC header

>>>> can be extended using optional objects and consistent setup &

>>>> configuration within an SFC-enabled domain should be assumed?

>>>>

>>>> Thank you

>>>>

>>>> Cheers,

>>>>

>>>> Med

>>>>

>>>>

>>>>

>>>> _______________________________________________

>>>> sfc mailing list

>>>> sfc at ietf.org

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

>>>>

>>




--_000_CDF2F015F4429F458815ED2A6C2B6B0B2E8558D0MBX021W3CA2exch_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"Segoe UI";
	panose-1:2 11 5 2 4 2 4 2 2 3;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:Cambria;
	panose-1:2 4 5 3 5 4 6 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
h1
	{mso-style-priority:9;
	mso-style-link:"Heading 1 Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	font-weight:normal;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.Heading1Char
	{mso-style-name:"Heading 1 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 1";
	font-family:"Times New Roman",serif;
	font-weight:bold;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Segoe UI",sans-serif;}
p.Titre1, li.Titre1, div.Titre1
	{mso-style-name:"Titre 1";
	mso-style-link:"Titre 1 Car";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.Titre1Car
	{mso-style-name:"Titre 1 Car";
	mso-style-priority:9;
	mso-style-link:"Titre 1";
	font-family:"Cambria",serif;
	color:#365F91;
	font-weight:bold;}
p.PrformatHTML, li.PrformatHTML, div.PrformatHTML
	{mso-style-name:"Pr=E9format=E9 HTML";
	mso-style-link:"Pr=E9format=E9 HTML Car";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.PrformatHTMLCar
	{mso-style-name:"Pr=E9format=E9 HTML Car";
	mso-style-priority:99;
	mso-style-link:"Pr=E9format=E9 HTML";
	font-family:Consolas;}
p.Textebrut, li.Textebrut, div.Textebrut
	{mso-style-name:"Texte brut";
	mso-style-link:"Texte brut Car";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.TextebrutCar
	{mso-style-name:"Texte brut Car";
	mso-style-priority:99;
	mso-style-link:"Texte brut";
	font-family:"Courier New";
	color:black;
	mso-fareast-language:EN-US;}
p.Textedebulles, li.Textedebulles, div.Textedebulles
	{mso-style-name:"Texte de bulles";
	mso-style-link:"Texte de bulles Car";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.TextedebullesCar
	{mso-style-name:"Texte de bulles Car";
	mso-style-priority:99;
	mso-style-link:"Texte de bulles";
	font-family:"Tahoma",sans-serif;}
span.EmailStyle32
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle33
	{mso-style-type:personal;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;}
span.EmailStyle34
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
span.EmailStyle35
	{mso-style-type:personal;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;}
span.EmailStyle37
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:32000932;
	mso-list-template-ids:632072226;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1
	{mso-list-id:2139057662;
	mso-list-template-ids:-391481046;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Med,<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I agree that we should=
 add additional text around the expected behavior regarding version incompa=
tibility.&nbsp;&nbsp; We could state that the SFF or SF perceiving this inc=
ompatibility MUST drop such a packet and MAY generate
 an OAM response in the reverse direction, although the exact nature of tha=
t response is outside the scope of the NSH draft.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp; Ron<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><a name=3D"_MailEndCompose"><span style=3D"color:#1F=
497D"><o:p>&nbsp;</o:p></span></a></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> mohamed.boucadair@orange.com [mailto:mo=
hamed.boucadair@orange.com]
<br>
<b>Sent:</b> Wednesday, March 4, 2015 10:43 AM<br>
<b>To:</b> Ron Parker; Sunil Vallamkonda<br>
<b>Cc:</b> sfc@ietf.org<br>
<b>Subject:</b> RE: Re: [sfc] draft-quinn-sfc-nsh: version number<o:p></o:p=
></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:10.0pt;font-fam=
ily:&quot;Courier New&quot;;color:black">Hi Ron,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:10.0pt;font-fam=
ily:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">If the version number is maintained, discussin=
g the behavior of a node if it supports several versions, if it does not su=
pport the version of a packet it receives, etc.
 is not about OAM. This is part of the behavior that needs to be specified =
in the document.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Cheers,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Med<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span lang=3D"FR" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,sans-serif">De&nbsp;:</span></b><span lang=3D"FR"=
 style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,sans-serif"> Ron =
Parker [<a href=3D"mailto:Ron_Parker@affirmednetworks.com">mailto:Ron_Parke=
r@affirmednetworks.com</a>]
<br>
<b>Envoy=E9&nbsp;:</b> mercredi 4 mars 2015 16:03<br>
<b>=C0&nbsp;:</b> BOUCADAIR Mohamed IMT/OLN; Sunil Vallamkonda<br>
<b>Cc&nbsp;:</b> <a href=3D"mailto:sfc@ietf.org">sfc@ietf.org</a><br>
<b>Objet&nbsp;:</b> RE: Re: [sfc] draft-quinn-sfc-nsh: version number<o:p><=
/o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"FR"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">When we take up OAM, w=
e could consider these ICMP-like behaviors &#8211; i.e., OAM packet contain=
ing &#8220;Version Incompatible&#8221; sent in the reverse direction on the=
 involved RSP.&nbsp;&nbsp; But I&#8217;m not sure what should be discussed
 in this draft, since OAM is explicitly out of scope.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp; Ron<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> sfc [<a href=3D"mailto:sfc-bounces@ietf=
.org">mailto:sfc-bounces@ietf.org</a>]
<b>On Behalf Of </b><a href=3D"mailto:mohamed.boucadair@orange.com">mohamed=
.boucadair@orange.com</a><br>
<b>Sent:</b> Wednesday, March 4, 2015 1:47 AM<br>
<b>To:</b> Sunil Vallamkonda<br>
<b>Cc:</b> <a href=3D"mailto:sfc@ietf.org">sfc@ietf.org</a><br>
<b>Subject:</b> Re: [sfc] draft-quinn-sfc-nsh: version number<o:p></o:p></p=
>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Hi Sunil,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">There is no such notification in the current s=
pec.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Below my thoughts about this point:<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">=3D=3D<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:10.0pt;font-family:&quot=
;Courier New&quot;;color:black">(b) Suppose a node that supports only v1 re=
ceives a packet with header (v2): If this node does not support a notificat=
ion procedure to inform the source that it does
 not support that header version, then FAILURES are introduced in the netwo=
rk. This is a degradation of the service compared to legacy scheme to struc=
ture services. This is not recommended, IMHO.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:10.0pt;font-family:&quot=
;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:10.0pt;font-family:&quot=
;Courier New&quot;;color:black">(c) If a notification is received from an e=
lement about its supported version: a node can use another version (the log=
ic to select other version is another point to
 discuss) for that communication, but what to do for the next flows in the =
context of the same service chain or other chains that involves these two n=
odes as adjacent elements in the same chain? Shouldn't these nodes cache th=
e version to use for subsequent
 exchange to avoid receiving the notification error each time? Wouldn't tha=
t complexity the behavior of the SFC-aware elements?<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:10.0pt;font-family:&quot=
;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:10.0pt;font-family:&quot=
;Courier New&quot;;color:black">(d) If a notification is received from an e=
lement about its supported version: As this may occurs in various segments =
of a given service chain, e.g., (A(v1), B(v1,v2),
 C(v1), D(v1,v2), E(v1)). Notifying the adjacent node each time there is a =
version mismatch induce an extra delay, that may be not be acceptable for e=
very flow.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">=3D=3D<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Thank you.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Cheers,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Med<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span lang=3D"FR" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,sans-serif">De&nbsp;:</span></b><span lang=3D"FR"=
 style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,sans-serif"> sfc =
[<a href=3D"mailto:sfc-bounces@ietf.org">mailto:sfc-bounces@ietf.org</a>]
<b>De la part de</b> Sunil Vallamkonda<br>
<b>Envoy=E9&nbsp;:</b> mardi 3 mars 2015 20:43<br>
<b>=C0&nbsp;:</b> <a href=3D"mailto:sfc@ietf.org">sfc@ietf.org</a><br>
<b>Objet&nbsp;:</b> Re: [sfc] draft-quinn-sfc-nsh: version number<o:p></o:p=
></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"FR"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">Just going through the thread on version number (jum=
ping in mid-thread),<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">Apart from the version mismatched (unsupported) pack=
et dropped and logged, is there a plan for a back off mechanism by SFF to n=
otify sender and avoid being overwhelmed with such packets ?<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">Thank you,<o:p></o:p></p>
<p class=3D"MsoNormal">Sunil.<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<h1 style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span styl=
e=3D"font-size:14.0pt;font-family:&quot;Times New Roman&quot;,serif">Re: [s=
fc] draft-quinn-sfc-nsh: version number</span><b><span style=3D"font-size:2=
4.0pt;font-family:&quot;Times New Roman&quot;,serif"><o:p></o:p></span></b>=
</h1>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"100%" align=3D"center">
</div>
<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;=
mso-fareast-language:EN-US">
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto;mso-list:l1 level1 lfo3">
<em><span style=3D"font-family:&quot;Calibri&quot;,sans-serif">From</span><=
/em>: &quot;Paul Quinn (paulq)&quot; &lt;<a href=3D"mailto:paulq@DOMAIN.HID=
DEN">paulq at cisco.com</a>&gt;<o:p></o:p></li><li class=3D"MsoNormal" styl=
e=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 =
lfo3">
<em><span style=3D"font-family:&quot;Calibri&quot;,sans-serif">To</span></e=
m>: &quot;Joel M. Halpern&quot; &lt;<a href=3D"mailto:jmh@DOMAIN.HIDDEN">jm=
h at joelhalpern.com</a>&gt;<o:p></o:p></li><li class=3D"MsoNormal" style=
=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 l=
fo3">
<em><span style=3D"font-family:&quot;Calibri&quot;,sans-serif">Cc</span></e=
m>: &quot;<a href=3D"mailto:mohamed.boucadair@DOMAIN.HIDDEN">mohamed.boucad=
air at orange.com</a>&quot; &lt;<a href=3D"mailto:mohamed.boucadair@DOMAIN.=
HIDDEN">mohamed.boucadair at orange.com</a>&gt;, &quot;<a href=3D"mailto:sf=
c@DOMAIN.HIDDEN">sfc
 at ietf.org</a>&quot; &lt;<a href=3D"mailto:sfc@DOMAIN.HIDDEN">sfc at ietf=
.org</a>&gt;<o:p></o:p></li><li class=3D"MsoNormal" style=3D"mso-margin-top=
-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo3">
<em><span style=3D"font-family:&quot;Calibri&quot;,sans-serif">Date</span><=
/em>: Mon, 2 Mar 2015 17:50:53 &#43;0000<o:p></o:p></li><li class=3D"MsoNor=
mal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l=
1 level1 lfo3">
<em><span style=3D"font-family:&quot;Calibri&quot;,sans-serif">In-reply-to<=
/span></em>: &lt;<a href=3D"http://www.ietf.org/mail-archive/web/sfc/curren=
t/msg03181.html">54EF2C9A.3040008@joelhalpern.com</a>&gt;<o:p></o:p></li><l=
i class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al=
t:auto;mso-list:l1 level1 lfo3">
<em><span style=3D"font-family:&quot;Calibri&quot;,sans-serif">References</=
span></em>: &lt;<a href=3D"mailto:787AE7BB302AE849A7480A190F8B9330049140B4@=
OPEXCLILM23.corporate.adroot.infra.ftgroup">787AE7BB302AE849A7480A190F8B933=
0049140B4@OPEXCLILM23.corporate.adroot.infra.ftgroup</a>&gt;
 &lt;<a href=3D"http://www.ietf.org/mail-archive/web/sfc/current/msg03151.h=
tml">54EDE5B7.6080102@joelhalpern.com</a>&gt; &lt;<a href=3D"mailto:787AE7B=
B302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.adroot.infra.ftgrou=
p">787AE7BB302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.adroot.in=
fra.ftgroup</a>&gt;
 &lt;<a href=3D"http://www.ietf.org/mail-archive/web/sfc/current/msg03181.h=
tml">54EF2C9A.3040008@joelhalpern.com</a>&gt;<o:p></o:p></li><li class=3D"M=
soNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-l=
ist:l1 level1 lfo3">
<em><span style=3D"font-family:&quot;Calibri&quot;,sans-serif">List-id</spa=
n></em>: Network Service Chaining &lt;sfc.ietf.org&gt;<o:p></o:p></li></ul>
</span>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"100%" align=3D"center">
</div>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">H=
i,<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
nbsp;<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">J=
umping in mid-thread.&nbsp; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
nbsp;<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">O=
verall, I tend to agree with Joel.&nbsp; Having an explicit version provide=
s a simple way to handle dataplane format changes.&nbsp; As Med points out,=
 quickly correctly, IMHO, there are other way to signal changes via reserve=
d bit.&nbsp; In practice though reserved bits are less useful since the con=
vention is to ignore unknown bits, it makes using them for feature changes =
quite difficult, which then brings up back to explicit versioning that cann=
ot be ignored.&nbsp; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
nbsp;<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">I=
 think Joel&#8217;s suggestion below makes perfect sense and should be adde=
d to the draft.<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
nbsp;<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">P=
aul<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
nbsp;<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
nbsp;<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt; On Feb 26, 2015, at 9:24 AM, Joel M. Halpern &lt;jmh at joelhalpern.com=
&gt; wrote:<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt; In one sense you are correct.&nbsp; If you could count on everything be=
ing upgraded at once, sure you could just assume common interpretation.<o:p=
></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt; However, we have found over the years that such simultaneous upgrading =
never works.&nbsp; You need to be able to transition.<o:p></o:p></span></pr=
e>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt; I do agree that we should add text about what to do with version number=
s that are not understood.&nbsp; There are multiple choices that affect how=
 we can make changes.&nbsp; My personal preference is:<o:p></o:p></span></p=
re>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt; If an packet presumed to carry an NSH header is received at an SFF, and=
 the SFF does not understnad the version of the protocol as indicated in th=
e base header, the packet MUST be discarded, and the event SHOULD be logged=
.<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt; This would allow an orderly transition, where devices can be upgraded t=
o understand a new version, then generation of the new version header can b=
e enabled.&nbsp; If a configuration error is made, the packets will be drop=
ped and operators following good practices will get notifications.<o:p></o:=
p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt; Yours,<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt; Joel<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt; On 2/26/15 2:16 AM, mohamed.boucadair at orange.com wrote:<o:p></o:p></=
span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; Hi Joel,<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; I fully agree with the extendibility of the header, but the questio=
n is why having a version number will be of help in the context of SFC? Sec=
ond, having a version number without specifying the behavior when several v=
ersions are supported, when the version number is not supported by an SFC-a=
ware element, etc. leaves open issues out of the spec.<o:p></o:p></span></p=
re>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; The other problem is that the current I-D includes several open doo=
rs left for extending the header:<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; * version<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; * reserved bits<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; * optional data<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; This is too much for a header that is supposed to be compact and si=
mple!<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; There are other means to extend the header without signaling the ve=
rsion in the packet. Having a distinct RFC number may be just fine in the c=
ontext of an unidirectional stream such as SFC.<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; Let us consider the situation where a version number is not explici=
tly signaled in the packet (but a new RFC updates the base SFC header). Sev=
eral options can be considered, indeed (those are provided as examples for =
illustration purposes):<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; * An operator can make sure that its SFC-enabled domain is configur=
ed in a consistent manner to support one and only one version of the header=
. No interoperability issues is encountered in this case.<o:p></o:p></span>=
</pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; * An operator that wants to upgrade its SFC-enabled domain to suppo=
rt a new specification of the SFC header: An operator can decide to proceed=
 to a software/hardware updates but can maintain the old header in operatio=
n until all involved elements are upgraded to support the new version. Once=
 the SFC-enabled domain is upgraded, then the new header can be enabled.<o:=
p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; Let's consider now that a version is signaled in the packet: to wha=
t extent signaling this information simplifies the SFC operations, and whet=
her it increases/decreases the serviceability of an SFC-enabled domain? Let=
's also assess to what extent having the version number add more complexity=
 in the SFC header treatment when several versions are supported by a node/=
within an SFC enabled domain? How it helps interoperability? Some points fo=
r discussion are elaborated below:<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; * If the SFC-enabled domain is configured to support the same versi=
on (which is likely): having the version number is not of any help.<o:p></o=
:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; * If the SFC-enabled domain involves some nodes that support versio=
n (v1) while others support (v2) (simple case): If these version are not ba=
ckward compatible, this will lead to failures when two adjacent elements in=
 a service chain do not support the same version. The SFC system is broken.=
 Having the version number is not of any help in this case.<o:p></o:p></spa=
n></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; * If the SFC-enabled domain involves some nodes that support versio=
n (v1) while others support (v1 and v2):<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; (a) The nodes that support both v1 and v2 should be instructed to d=
ecide which version to be used. This can be either part of the specificatio=
n or be driven by configuration. If a version number is included in the spe=
c, I would expect to clarify the behavior in such case.<o:p></o:p></span></=
pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; (b) Suppose a node that supports only v1 receives a packet with hea=
der (v2): If this node does not support a notification procedure to inform =
the source that it does not support that header version, then FAILURES are =
introduced in the network. This is a degradation of the service compared to=
 legacy scheme to structure services. This is not recommended, IMHO.<o:p></=
o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; (c) If a notification is received from an element about its support=
ed version: a node can use another version (the logic to select other versi=
on is another point to discuss) for that communication, but what to do for =
the next flows in the context of the same service chain or other chains tha=
t involves these two nodes as adjacent elements in the same chain? Shouldn'=
t these nodes cache the version to use for subsequent exchange to avoid rec=
eiving the notification error each time? Wouldn't that complexity the behav=
ior of the SFC-aware elements?<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; (d) If a notification is received from an element about its support=
ed version: As this may occurs in various segments of a given service chain=
, e.g., (A(v1), B(v1,v2), C(v2), D(v1,v2), E(v1)). Notifying the adjacent n=
ode each time there is a version mismatch induce an extra delay, that may b=
e not be acceptable for every flow.<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; I hope this clarifies my initial concern.<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; Thank you.<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; Cheers,<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; Med<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; -----Message d'origine-----<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; De : Joel M. Halpern [<a href=3D"mailto:jmh">mailto:jmh</a> at =
joelhalpern.com]<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; Envoy=E9 : mercredi 25 f=E9vrier 2015 16:10<o:p></o:p></span></=
pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; =C0 : BOUCADAIR Mohamed IMT/OLN; paulq at cisco.com<o:p></o:p><=
/span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; Cc : sfc at ietf.org<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; Objet : Re: [sfc] draft-quinn-sfc-nsh: version number<o:p></o:p=
></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; I would really prefer to keep the version number.&nbsp; Even th=
ough we have<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; the MD-type identifier and for some MD we have the TLVs.<o:p></=
o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; The reason is that we may want to change the base header.&nbsp;=
 For example,<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; suppose that the ciscussion about including a flow identifier i=
n the<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; base header had not come up now.&nbsp; If it came up later, we =
would want to<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; be able to have the discussion and make the choice, rather than=
 being<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; constrained by the lack of a version field.<o:p></o:p></span></=
pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; Yours,<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; Joel<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt; On 2/25/15 10:03 AM, mohamed.boucadair at orange.com wrote:<o:p=
></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; Hi Paul, all,<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; What is the purpose of having a version number in the heade=
r? Is there a<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; kind of version negotiation that needs to be in place?<o:p>=
</o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; I checked the I-D but failed to find text that explains the=
 rationale,<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; the use of the such field and whether an error will be retu=
rned if the<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; version is not supported by the receiving node.<o:p></o:p><=
/span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; Wouldn't be preferable to get rid of this field given that =
SFC header<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; can be extended using optional objects and consistent setup=
 &amp;<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; configuration within an SFC-enabled domain should be assume=
d?<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; Thank you<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; Cheers,<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; Med<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; _______________________________________________<o:p></o:p><=
/span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; sfc mailing list<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; sfc at ietf.org<o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/sfc">https=
://www.ietf.org/mailman/listinfo/sfc</a><o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
gt;&gt; <o:p></o:p></span></pre>
<pre><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&=
nbsp;<o:p></o:p></span></pre>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>

--_000_CDF2F015F4429F458815ED2A6C2B6B0B2E8558D0MBX021W3CA2exch_--


From nobody Wed Mar  4 08:10:17 2015
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AF251A9074 for <sfc@ietfa.amsl.com>; Wed,  4 Mar 2015 08:10:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 6HG-GsXy7lTA for <sfc@ietfa.amsl.com>; Wed,  4 Mar 2015 08:10:06 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 47D081A907A for <sfc@ietf.org>; Wed,  4 Mar 2015 08:09:45 -0800 (PST)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm14.si.francetelecom.fr (ESMTP service) with ESMTP id 4A65A22C3D7; Wed,  4 Mar 2015 17:09:43 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.16]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 219CC23812F; Wed,  4 Mar 2015 17:09:43 +0100 (CET)
Received: from OPEXCLILM23.corporate.adroot.infra.ftgroup ([169.254.2.231]) by OPEXCLILH05.corporate.adroot.infra.ftgroup ([10.114.31.16]) with mapi id 14.03.0224.002; Wed, 4 Mar 2015 17:09:42 +0100
From: <mohamed.boucadair@orange.com>
To: Ron Parker <Ron_Parker@affirmednetworks.com>, Sunil Vallamkonda <sunilvk@f5.com>
Thread-Topic: Re: [sfc] draft-quinn-sfc-nsh: version number
Thread-Index: AdBV6VnhN9N2Adv/Rs2PZVkjw6sDlQAXRdTwABFWhuAAAVpygAAAT27gAABcXnA=
Date: Wed, 4 Mar 2015 16:09:41 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93300491A1F7@OPEXCLILM23.corporate.adroot.infra.ftgroup>
References: <01f9e1a4e6514854a26556e4c6a3e36e@SEAEXCHMBX05.olympus.F5Net.com> <787AE7BB302AE849A7480A190F8B933004919B76@OPEXCLILM23.corporate.adroot.infra.ftgroup> <CDF2F015F4429F458815ED2A6C2B6B0B2E85379B@MBX021-W3-CA-2.exch021.domain.local> <787AE7BB302AE849A7480A190F8B93300491A1AF@OPEXCLILM23.corporate.adroot.infra.ftgroup> <CDF2F015F4429F458815ED2A6C2B6B0B2E8558D0@MBX021-W3-CA-2.exch021.domain.local>
In-Reply-To: <CDF2F015F4429F458815ED2A6C2B6B0B2E8558D0@MBX021-W3-CA-2.exch021.domain.local>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.1]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B93300491A1F7OPEXCLILM23corp_"
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.12.16.112421
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/rrKbmKl43vSzeSnfrMeoyC6cgbw>
Cc: "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] draft-quinn-sfc-nsh: version number
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 04 Mar 2015 16:10:15 -0000

--_000_787AE7BB302AE849A7480A190F8B93300491A1F7OPEXCLILM23corp_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Re-,

That would be a good start, but still not sufficient IMHO.

If no notification is sent back (which can be the case with the MAY languag=
e), the failure will be experienced till an action is done by the domain op=
erator. This is not desirable.

Having a more strong language for sending back the response (that needs to =
include at least the received packet with the unsupported version) will hav=
e the effect to resend the packet with an adequate version (if multiple ver=
sions are supported). The exact behavior when a version mismatch error is r=
eceived should be explicated in the document IMO.

Cheers,
Med

De : Ron Parker [mailto:Ron_Parker@affirmednetworks.com]
Envoy=E9 : mercredi 4 mars 2015 16:50
=C0 : BOUCADAIR Mohamed IMT/OLN; Sunil Vallamkonda
Cc : sfc@ietf.org
Objet : RE: Re: [sfc] draft-quinn-sfc-nsh: version number

Med,

I agree that we should add additional text around the expected behavior reg=
arding version incompatibility.   We could state that the SFF or SF perceiv=
ing this incompatibility MUST drop such a packet and MAY generate an OAM re=
sponse in the reverse direction, although the exact nature of that response=
 is outside the scope of the NSH draft.

   Ron





From: mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com> [ma=
ilto:mohamed.boucadair@orange.com]
Sent: Wednesday, March 4, 2015 10:43 AM
To: Ron Parker; Sunil Vallamkonda
Cc: sfc@ietf.org<mailto:sfc@ietf.org>
Subject: RE: Re: [sfc] draft-quinn-sfc-nsh: version number

Hi Ron,

If the version number is maintained, discussing the behavior of a node if i=
t supports several versions, if it does not support the version of a packet=
 it receives, etc. is not about OAM. This is part of the behavior that need=
s to be specified in the document.

Cheers,
Med


De : Ron Parker [mailto:Ron_Parker@affirmednetworks.com]
Envoy=E9 : mercredi 4 mars 2015 16:03
=C0 : BOUCADAIR Mohamed IMT/OLN; Sunil Vallamkonda
Cc : sfc@ietf.org<mailto:sfc@ietf.org>
Objet : RE: Re: [sfc] draft-quinn-sfc-nsh: version number

When we take up OAM, we could consider these ICMP-like behaviors - i.e., OA=
M packet containing "Version Incompatible" sent in the reverse direction on=
 the involved RSP.   But I'm not sure what should be discussed in this draf=
t, since OAM is explicitly out of scope.

   Ron



From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of mohamed.boucadair@oran=
ge.com<mailto:mohamed.boucadair@orange.com>
Sent: Wednesday, March 4, 2015 1:47 AM
To: Sunil Vallamkonda
Cc: sfc@ietf.org<mailto:sfc@ietf.org>
Subject: Re: [sfc] draft-quinn-sfc-nsh: version number

Hi Sunil,

There is no such notification in the current spec.

Below my thoughts about this point:

=3D=3D

(b) Suppose a node that supports only v1 receives a packet with header (v2)=
: If this node does not support a notification procedure to inform the sour=
ce that it does not support that header version, then FAILURES are introduc=
ed in the network. This is a degradation of the service compared to legacy =
scheme to structure services. This is not recommended, IMHO.



(c) If a notification is received from an element about its supported versi=
on: a node can use another version (the logic to select other version is an=
other point to discuss) for that communication, but what to do for the next=
 flows in the context of the same service chain or other chains that involv=
es these two nodes as adjacent elements in the same chain? Shouldn't these =
nodes cache the version to use for subsequent exchange to avoid receiving t=
he notification error each time? Wouldn't that complexity the behavior of t=
he SFC-aware elements?



(d) If a notification is received from an element about its supported versi=
on: As this may occurs in various segments of a given service chain, e.g., =
(A(v1), B(v1,v2), C(v1), D(v1,v2), E(v1)). Notifying the adjacent node each=
 time there is a version mismatch induce an extra delay, that may be not be=
 acceptable for every flow.
=3D=3D

Thank you.

Cheers,
Med


De : sfc [mailto:sfc-bounces@ietf.org] De la part de Sunil Vallamkonda
Envoy=E9 : mardi 3 mars 2015 20:43
=C0 : sfc@ietf.org<mailto:sfc@ietf.org>
Objet : Re: [sfc] draft-quinn-sfc-nsh: version number

Hi,

Just going through the thread on version number (jumping in mid-thread),

Apart from the version mismatched (unsupported) packet dropped and logged, =
is there a plan for a back off mechanism by SFF to notify sender and avoid =
being overwhelmed with such packets ?

Thank you,
Sunil.


Re: [sfc] draft-quinn-sfc-nsh: version number
________________________________

  *   From: "Paul Quinn (paulq)" <paulq at cisco.com<mailto:paulq@DOMAIN.HI=
DDEN>>
  *   To: "Joel M. Halpern" <jmh at joelhalpern.com<mailto:jmh@DOMAIN.HIDDE=
N>>
  *   Cc: "mohamed.boucadair at orange.com<mailto:mohamed.boucadair@DOMAIN.=
HIDDEN>" <mohamed.boucadair at orange.com<mailto:mohamed.boucadair@DOMAIN.H=
IDDEN>>, "sfc at ietf.org<mailto:sfc@DOMAIN.HIDDEN>" <sfc at ietf.org<mailt=
o:sfc@DOMAIN.HIDDEN>>
  *   Date: Mon, 2 Mar 2015 17:50:53 +0000
  *   In-reply-to: <54EF2C9A.3040008@joelhalpern.com<http://www.ietf.org/ma=
il-archive/web/sfc/current/msg03181.html>>
  *   References: <787AE7BB302AE849A7480A190F8B9330049140B4@OPEXCLILM23.cor=
porate.adroot.infra.ftgroup<mailto:787AE7BB302AE849A7480A190F8B9330049140B4=
@OPEXCLILM23.corporate.adroot.infra.ftgroup>> <54EDE5B7.6080102@joelhalpern=
.com<http://www.ietf.org/mail-archive/web/sfc/current/msg03151.html>> <787A=
E7BB302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.adroot.infra.ftg=
roup<mailto:787AE7BB302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.=
adroot.infra.ftgroup>> <54EF2C9A.3040008@joelhalpern.com<http://www.ietf.or=
g/mail-archive/web/sfc/current/msg03181.html>>
  *   List-id: Network Service Chaining <sfc.ietf.org>

________________________________

Hi,



Jumping in mid-thread.



Overall, I tend to agree with Joel.  Having an explicit version provides a =
simple way to handle dataplane format changes.  As Med points out, quickly =
correctly, IMHO, there are other way to signal changes via reserved bit.  I=
n practice though reserved bits are less useful since the convention is to =
ignore unknown bits, it makes using them for feature changes quite difficul=
t, which then brings up back to explicit versioning that cannot be ignored.



I think Joel's suggestion below makes perfect sense and should be added to =
the draft.



Paul





> On Feb 26, 2015, at 9:24 AM, Joel M. Halpern <jmh at joelhalpern.com> wro=
te:

>

> In one sense you are correct.  If you could count on everything being upg=
raded at once, sure you could just assume common interpretation.

> However, we have found over the years that such simultaneous upgrading ne=
ver works.  You need to be able to transition.

>

> I do agree that we should add text about what to do with version numbers =
that are not understood.  There are multiple choices that affect how we can=
 make changes.  My personal preference is:

>

> If an packet presumed to carry an NSH header is received at an SFF, and t=
he SFF does not understnad the version of the protocol as indicated in the =
base header, the packet MUST be discarded, and the event SHOULD be logged.

>

> This would allow an orderly transition, where devices can be upgraded to =
understand a new version, then generation of the new version header can be =
enabled.  If a configuration error is made, the packets will be dropped and=
 operators following good practices will get notifications.

>

> Yours,

> Joel

>

> On 2/26/15 2:16 AM, mohamed.boucadair at orange.com wrote:

>> Hi Joel,

>>

>> I fully agree with the extendibility of the header, but the question is =
why having a version number will be of help in the context of SFC? Second, =
having a version number without specifying the behavior when several versio=
ns are supported, when the version number is not supported by an SFC-aware =
element, etc. leaves open issues out of the spec.

>>

>> The other problem is that the current I-D includes several open doors le=
ft for extending the header:

>> * version

>> * reserved bits

>> * optional data

>>

>> This is too much for a header that is supposed to be compact and simple!

>>

>> There are other means to extend the header without signaling the version=
 in the packet. Having a distinct RFC number may be just fine in the contex=
t of an unidirectional stream such as SFC.

>>

>> Let us consider the situation where a version number is not explicitly s=
ignaled in the packet (but a new RFC updates the base SFC header). Several =
options can be considered, indeed (those are provided as examples for illus=
tration purposes):

>> * An operator can make sure that its SFC-enabled domain is configured in=
 a consistent manner to support one and only one version of the header. No =
interoperability issues is encountered in this case.

>> * An operator that wants to upgrade its SFC-enabled domain to support a =
new specification of the SFC header: An operator can decide to proceed to a=
 software/hardware updates but can maintain the old header in operation unt=
il all involved elements are upgraded to support the new version. Once the =
SFC-enabled domain is upgraded, then the new header can be enabled.

>>

>> Let's consider now that a version is signaled in the packet: to what ext=
ent signaling this information simplifies the SFC operations, and whether i=
t increases/decreases the serviceability of an SFC-enabled domain? Let's al=
so assess to what extent having the version number add more complexity in t=
he SFC header treatment when several versions are supported by a node/withi=
n an SFC enabled domain? How it helps interoperability? Some points for dis=
cussion are elaborated below:

>>

>> * If the SFC-enabled domain is configured to support the same version (w=
hich is likely): having the version number is not of any help.

>> * If the SFC-enabled domain involves some nodes that support version (v1=
) while others support (v2) (simple case): If these version are not backwar=
d compatible, this will lead to failures when two adjacent elements in a se=
rvice chain do not support the same version. The SFC system is broken. Havi=
ng the version number is not of any help in this case.

>> * If the SFC-enabled domain involves some nodes that support version (v1=
) while others support (v1 and v2):

>>

>> (a) The nodes that support both v1 and v2 should be instructed to decide=
 which version to be used. This can be either part of the specification or =
be driven by configuration. If a version number is included in the spec, I =
would expect to clarify the behavior in such case.

>>

>> (b) Suppose a node that supports only v1 receives a packet with header (=
v2): If this node does not support a notification procedure to inform the s=
ource that it does not support that header version, then FAILURES are intro=
duced in the network. This is a degradation of the service compared to lega=
cy scheme to structure services. This is not recommended, IMHO.

>>

>> (c) If a notification is received from an element about its supported ve=
rsion: a node can use another version (the logic to select other version is=
 another point to discuss) for that communication, but what to do for the n=
ext flows in the context of the same service chain or other chains that inv=
olves these two nodes as adjacent elements in the same chain? Shouldn't the=
se nodes cache the version to use for subsequent exchange to avoid receivin=
g the notification error each time? Wouldn't that complexity the behavior o=
f the SFC-aware elements?

>>

>> (d) If a notification is received from an element about its supported ve=
rsion: As this may occurs in various segments of a given service chain, e.g=
., (A(v1), B(v1,v2), C(v2), D(v1,v2), E(v1)). Notifying the adjacent node e=
ach time there is a version mismatch induce an extra delay, that may be not=
 be acceptable for every flow.

>>

>> I hope this clarifies my initial concern.

>>

>> Thank you.

>>

>> Cheers,

>> Med

>>

>>> -----Message d'origine-----

>>> De : Joel M. Halpern [mailto:jmh at joelhalpern.com]

>>> Envoy=E9 : mercredi 25 f=E9vrier 2015 16:10

>>> =C0 : BOUCADAIR Mohamed IMT/OLN; paulq at cisco.com

>>> Cc : sfc at ietf.org

>>> Objet : Re: [sfc] draft-quinn-sfc-nsh: version number

>>>

>>> I would really prefer to keep the version number.  Even though we have

>>> the MD-type identifier and for some MD we have the TLVs.

>>>

>>> The reason is that we may want to change the base header.  For example,

>>> suppose that the ciscussion about including a flow identifier in the

>>> base header had not come up now.  If it came up later, we would want to

>>> be able to have the discussion and make the choice, rather than being

>>> constrained by the lack of a version field.

>>>

>>> Yours,

>>> Joel

>>>

>>>

>>> On 2/25/15 10:03 AM, mohamed.boucadair at orange.com wrote:

>>>> Hi Paul, all,

>>>>

>>>> What is the purpose of having a version number in the header? Is there=
 a

>>>> kind of version negotiation that needs to be in place?

>>>>

>>>> I checked the I-D but failed to find text that explains the rationale,

>>>> the use of the such field and whether an error will be returned if the

>>>> version is not supported by the receiving node.

>>>>

>>>> Wouldn't be preferable to get rid of this field given that SFC header

>>>> can be extended using optional objects and consistent setup &

>>>> configuration within an SFC-enabled domain should be assumed?

>>>>

>>>> Thank you

>>>>

>>>> Cheers,

>>>>

>>>> Med

>>>>

>>>>

>>>>

>>>> _______________________________________________

>>>> sfc mailing list

>>>> sfc at ietf.org

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

>>>>

>>




--_000_787AE7BB302AE849A7480A190F8B93300491A1F7OPEXCLILM23corp_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Cambria;
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"Segoe UI";
	panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
h1
	{mso-style-priority:9;
	mso-style-link:"Titre 1 Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	font-weight:normal;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Texte brut Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"Pr=E9format=E9 HTML Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Texte de bulles Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.Titre1Car
	{mso-style-name:"Titre 1 Car";
	mso-style-priority:9;
	mso-style-link:"Titre 1";
	font-family:"Cambria","serif";
	color:#365F91;
	font-weight:bold;}
span.PrformatHTMLCar
	{mso-style-name:"Pr=E9format=E9 HTML Car";
	mso-style-priority:99;
	mso-style-link:"Pr=E9format=E9 HTML";
	font-family:Consolas;}
span.TextebrutCar
	{mso-style-name:"Texte brut Car";
	mso-style-priority:99;
	mso-style-link:"Texte brut";
	font-family:"Courier New";
	color:black;
	mso-fareast-language:EN-US;}
span.TextedebullesCar
	{mso-style-name:"Texte de bulles Car";
	mso-style-priority:99;
	mso-style-link:"Texte de bulles";
	font-family:"Tahoma","sans-serif";}
p.Heading1, li.Heading1, div.Heading1
	{mso-style-name:"Heading 1";
	mso-style-link:"Heading 1 Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.Heading1Char
	{mso-style-name:"Heading 1 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 1";
	font-family:"Times New Roman","serif";
	font-weight:bold;}
p.HTMLPreformatted, li.HTMLPreformatted, div.HTMLPreformatted
	{mso-style-name:"HTML Preformatted";
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
p.PlainText, li.PlainText, div.PlainText
	{mso-style-name:"Plain Text";
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
p.BalloonText, li.BalloonText, div.BalloonText
	{mso-style-name:"Balloon Text";
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Segoe UI","sans-serif";}
span.EmailStyle32
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle33
	{mso-style-type:personal;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;}
span.EmailStyle34
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle35
	{mso-style-type:personal;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;}
span.EmailStyle36
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle38
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1094283961;
	mso-list-template-ids:-714036274;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"FR" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Re-,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">That would be a good start, but=
 still not sufficient IMHO.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">If no notification is sent back=
 (which can be the case with the MAY language), the failure will be experie=
nced till an action is done by the domain operator.
 This is not desirable. <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Having a more strong language f=
or sending back the response (that needs to include at least the received p=
acket with the unsupported version) will have the
 effect to resend the packet with an adequate version (if multiple versions=
 are supported). The exact behavior when a version mismatch error is receiv=
ed should be explicated in the document IMO.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Cheers,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Med<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">De&nbsp;:</span></b><span style=3D"fo=
nt-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Ron =
Parker [mailto:Ron_Parker@affirmednetworks.com]
<br>
<b>Envoy=E9&nbsp;:</b> mercredi 4 mars 2015 16:50<br>
<b>=C0&nbsp;:</b> BOUCADAIR Mohamed IMT/OLN; Sunil Vallamkonda<br>
<b>Cc&nbsp;:</b> sfc@ietf.org<br>
<b>Objet&nbsp;:</b> RE: Re: [sfc] draft-quinn-sfc-nsh: version number<o:p><=
/o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Med,<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">I agree=
 that we should add additional text around the expected behavior regarding =
version incompatibility.&nbsp;&nbsp; We could state that the SFF or SF perc=
eiving this incompatibility MUST drop such a packet
 and MAY generate an OAM response in the reverse direction, although the ex=
act nature of that response is outside the scope of the NSH draft.<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp; Ron<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><a name=3D"_MailEndCompose"></a><span lang=3D"EN-US"=
 style=3D"color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US">From:</span></b><span lang=
=3D"EN-US"> <a href=3D"mailto:mohamed.boucadair@orange.com">
mohamed.boucadair@orange.com</a> [<a href=3D"mailto:mohamed.boucadair@orang=
e.com">mailto:mohamed.boucadair@orange.com</a>]
<br>
<b>Sent:</b> Wednesday, March 4, 2015 10:43 AM<br>
<b>To:</b> Ron Parker; Sunil Vallamkonda<br>
<b>Cc:</b> <a href=3D"mailto:sfc@ietf.org">sfc@ietf.org</a><br>
<b>Subject:</b> RE: Re: [sfc] draft-quinn-sfc-nsh: version number<o:p></o:p=
></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Hi Ron,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">If the version number is mainta=
ined, discussing the behavior of a node if it supports several versions, if=
 it does not support the version of a packet it
 receives, etc. is not about OAM. This is part of the behavior that needs t=
o be specified in the document.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Cheers,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Med<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">De&nbsp;:</span></b><span style=3D"fo=
nt-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Ron =
Parker [<a href=3D"mailto:Ron_Parker@affirmednetworks.com">mailto:Ron_Parke=
r@affirmednetworks.com</a>]
<br>
<b>Envoy=E9&nbsp;:</b> mercredi 4 mars 2015 16:03<br>
<b>=C0&nbsp;:</b> BOUCADAIR Mohamed IMT/OLN; Sunil Vallamkonda<br>
<b>Cc&nbsp;:</b> <a href=3D"mailto:sfc@ietf.org">sfc@ietf.org</a><br>
<b>Objet&nbsp;:</b> RE: Re: [sfc] draft-quinn-sfc-nsh: version number<o:p><=
/o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">When we=
 take up OAM, we could consider these ICMP-like behaviors &#8211; i.e., OAM=
 packet containing &#8220;Version Incompatible&#8221; sent in the reverse d=
irection on the involved RSP.&nbsp;&nbsp; But I&#8217;m not sure what shoul=
d
 be discussed in this draft, since OAM is explicitly out of scope.<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp; Ron<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US">From:</span></b><span lang=
=3D"EN-US"> sfc [<a href=3D"mailto:sfc-bounces@ietf.org">mailto:sfc-bounces=
@ietf.org</a>]
<b>On Behalf Of </b><a href=3D"mailto:mohamed.boucadair@orange.com">mohamed=
.boucadair@orange.com</a><br>
<b>Sent:</b> Wednesday, March 4, 2015 1:47 AM<br>
<b>To:</b> Sunil Vallamkonda<br>
<b>Cc:</b> <a href=3D"mailto:sfc@ietf.org">sfc@ietf.org</a><br>
<b>Subject:</b> Re: [sfc] draft-quinn-sfc-nsh: version number<o:p></o:p></s=
pan></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Hi Sunil,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">There is no such notification i=
n the current spec.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Below my thoughts about this po=
int:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">=3D=3D<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Courier New&quot;;color:black">(b) Suppose a node that supp=
orts only v1 receives a packet with header (v2): If this node does not supp=
ort a notification procedure to inform the source
 that it does not support that header version, then FAILURES are introduced=
 in the network. This is a degradation of the service compared to legacy sc=
heme to structure services. This is not recommended, IMHO.<o:p></o:p></span=
></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Courier New&quot;;color:black">(c) If a notification is rec=
eived from an element about its supported version: a node can use another v=
ersion (the logic to select other version is another
 point to discuss) for that communication, but what to do for the next flow=
s in the context of the same service chain or other chains that involves th=
ese two nodes as adjacent elements in the same chain? Shouldn't these nodes=
 cache the version to use for subsequent
 exchange to avoid receiving the notification error each time? Wouldn't tha=
t complexity the behavior of the SFC-aware elements?<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Courier New&quot;;color:black">(d) If a notification is rec=
eived from an element about its supported version: As this may occurs in va=
rious segments of a given service chain, e.g., (A(v1),
 B(v1,v2), C(v1), D(v1,v2), E(v1)). Notifying the adjacent node each time t=
here is a version mismatch induce an extra delay, that may be not be accept=
able for every flow.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">=3D=3D<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Thank you.<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Cheers,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Med<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">De&nbsp;:</span></b><span style=3D"fo=
nt-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> sfc =
[<a href=3D"mailto:sfc-bounces@ietf.org">mailto:sfc-bounces@ietf.org</a>]
<b>De la part de</b> Sunil Vallamkonda<br>
<b>Envoy=E9&nbsp;:</b> mardi 3 mars 2015 20:43<br>
<b>=C0&nbsp;:</b> <a href=3D"mailto:sfc@ietf.org">sfc@ietf.org</a><br>
<b>Objet&nbsp;:</b> Re: [sfc] draft-quinn-sfc-nsh: version number<o:p></o:p=
></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hi,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Just going through the thread o=
n version number (jumping in mid-thread),<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Apart from the version mismatch=
ed (unsupported) packet dropped and logged, is there a plan for a back off =
mechanism by SFF to notify sender and avoid being overwhelmed with such pac=
kets ?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Thank you,<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Sunil.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;<o:p></o:p></span></p>
<h1 style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang=
=3D"EN-US" style=3D"font-size:14.0pt;font-family:&quot;Times New Roman&quot=
;,&quot;serif&quot;">Re: [sfc] draft-quinn-sfc-nsh: version number</span><b=
><span lang=3D"EN-US" style=3D"font-size:24.0pt;font-family:&quot;Times New=
 Roman&quot;,&quot;serif&quot;"><o:p></o:p></span></b></h1>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 lang=3D"EN-US">
<hr size=3D"2" width=3D"100%" align=3D"center">
</span></div>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto;mso-list:l0 level1 lfo1">
<em><span lang=3D"EN-US" style=3D"font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;;mso-fareast-language:EN-US">From</span></em><span lang=3D"EN-=
US" style=3D"mso-fareast-language:EN-US">: &quot;Paul Quinn (paulq)&quot; &=
lt;<a href=3D"mailto:paulq@DOMAIN.HIDDEN">paulq at cisco.com</a>&gt;<o:p></=
o:p></span></li><li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;ms=
o-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<em><span lang=3D"EN-US" style=3D"font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;;mso-fareast-language:EN-US">To</span></em><span lang=3D"EN-US=
" style=3D"mso-fareast-language:EN-US">: &quot;Joel M. Halpern&quot; &lt;<a=
 href=3D"mailto:jmh@DOMAIN.HIDDEN">jmh at joelhalpern.com</a>&gt;<o:p></o:p=
></span></li><li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-m=
argin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<em><span lang=3D"EN-US" style=3D"font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;;mso-fareast-language:EN-US">Cc</span></em><span lang=3D"EN-US=
" style=3D"mso-fareast-language:EN-US">: &quot;<a href=3D"mailto:mohamed.bo=
ucadair@DOMAIN.HIDDEN">mohamed.boucadair at orange.com</a>&quot; &lt;<a hre=
f=3D"mailto:mohamed.boucadair@DOMAIN.HIDDEN">mohamed.boucadair
 at orange.com</a>&gt;, &quot;<a href=3D"mailto:sfc@DOMAIN.HIDDEN">sfc at i=
etf.org</a>&quot; &lt;<a href=3D"mailto:sfc@DOMAIN.HIDDEN">sfc at ietf.org<=
/a>&gt;<o:p></o:p></span></li><li class=3D"MsoNormal" style=3D"mso-margin-t=
op-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<em><span lang=3D"EN-US" style=3D"font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;;mso-fareast-language:EN-US">Date</span></em><span lang=3D"EN-=
US" style=3D"mso-fareast-language:EN-US">: Mon, 2 Mar 2015 17:50:53 &#43;00=
00<o:p></o:p></span></li><li class=3D"MsoNormal" style=3D"mso-margin-top-al=
t:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<em><span lang=3D"EN-US" style=3D"font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;;mso-fareast-language:EN-US">In-reply-to</span></em><span lang=
=3D"EN-US" style=3D"mso-fareast-language:EN-US">: &lt;<a href=3D"http://www=
.ietf.org/mail-archive/web/sfc/current/msg03181.html">54EF2C9A.3040008@joel=
halpern.com</a>&gt;<o:p></o:p></span></li><li class=3D"MsoNormal" style=3D"=
mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1"=
>
<em><span lang=3D"EN-US" style=3D"font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;;mso-fareast-language:EN-US">References</span></em><span lang=
=3D"EN-US" style=3D"mso-fareast-language:EN-US">: &lt;<a href=3D"mailto:787=
AE7BB302AE849A7480A190F8B9330049140B4@OPEXCLILM23.corporate.adroot.infra.ft=
group">787AE7BB302AE849A7480A190F8B9330049140B4@OPEXCLILM23.corporate.adroo=
t.infra.ftgroup</a>&gt;
 &lt;<a href=3D"http://www.ietf.org/mail-archive/web/sfc/current/msg03151.h=
tml">54EDE5B7.6080102@joelhalpern.com</a>&gt; &lt;<a href=3D"mailto:787AE7B=
B302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.adroot.infra.ftgrou=
p">787AE7BB302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.adroot.in=
fra.ftgroup</a>&gt;
 &lt;<a href=3D"http://www.ietf.org/mail-archive/web/sfc/current/msg03181.h=
tml">54EF2C9A.3040008@joelhalpern.com</a>&gt;<o:p></o:p></span></li><li cla=
ss=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:aut=
o;mso-list:l0 level1 lfo1">
<em><span lang=3D"EN-US" style=3D"font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;;mso-fareast-language:EN-US">List-id</span></em><span lang=3D"=
EN-US" style=3D"mso-fareast-language:EN-US">: Network Service Chaining &lt;=
sfc.ietf.org&gt;<o:p></o:p></span></li></ul>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 lang=3D"EN-US">
<hr size=3D"2" width=3D"100%" align=3D"center">
</span></div>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">Hi,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&nbsp;<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">Jumping in mid-thread.&nbsp; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&nbsp;<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">Overall, I tend to agree with Joel.&nbsp; Having an explicit =
version provides a simple way to handle dataplane format changes.&nbsp; As =
Med points out, quickly correctly, IMHO, there are other way to signal chan=
ges via reserved bit.&nbsp; In practice though reserved bits are less usefu=
l since the convention is to ignore unknown bits, it makes using them for f=
eature changes quite difficult, which then brings up back to explicit versi=
oning that cannot be ignored.&nbsp; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&nbsp;<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">I think Joel&#8217;s suggestion below makes perfect sense and=
 should be added to the draft.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&nbsp;<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">Paul<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&nbsp;<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&nbsp;<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt; On Feb 26, 2015, at 9:24 AM, Joel M. Halpern &lt;jmh at =
joelhalpern.com&gt; wrote:<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt; In one sense you are correct.&nbsp; If you could count o=
n everything being upgraded at once, sure you could just assume common inte=
rpretation.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt; However, we have found over the years that such simultan=
eous upgrading never works.&nbsp; You need to be able to transition.<o:p></=
o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt; I do agree that we should add text about what to do with=
 version numbers that are not understood.&nbsp; There are multiple choices =
that affect how we can make changes.&nbsp; My personal preference is:<o:p><=
/o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt; If an packet presumed to carry an NSH header is received=
 at an SFF, and the SFF does not understnad the version of the protocol as =
indicated in the base header, the packet MUST be discarded, and the event S=
HOULD be logged.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt; This would allow an orderly transition, where devices ca=
n be upgraded to understand a new version, then generation of the new versi=
on header can be enabled.&nbsp; If a configuration error is made, the packe=
ts will be dropped and operators following good practices will get notifica=
tions.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt; Yours,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt; Joel<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt; On 2/26/15 2:16 AM, mohamed.boucadair at orange.com wrot=
e:<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; Hi Joel,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; I fully agree with the extendibility of the header, =
but the question is why having a version number will be of help in the cont=
ext of SFC? Second, having a version number without specifying the behavior=
 when several versions are supported, when the version number is not suppor=
ted by an SFC-aware element, etc. leaves open issues out of the spec.<o:p><=
/o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; The other problem is that the current I-D includes s=
everal open doors left for extending the header:<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; * version<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; * reserved bits<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; * optional data<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; This is too much for a header that is supposed to be=
 compact and simple!<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; There are other means to extend the header without s=
ignaling the version in the packet. Having a distinct RFC number may be jus=
t fine in the context of an unidirectional stream such as SFC.<o:p></o:p></=
span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; Let us consider the situation where a version number=
 is not explicitly signaled in the packet (but a new RFC updates the base S=
FC header). Several options can be considered, indeed (those are provided a=
s examples for illustration purposes):<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; * An operator can make sure that its SFC-enabled dom=
ain is configured in a consistent manner to support one and only one versio=
n of the header. No interoperability issues is encountered in this case.<o:=
p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; * An operator that wants to upgrade its SFC-enabled =
domain to support a new specification of the SFC header: An operator can de=
cide to proceed to a software/hardware updates but can maintain the old hea=
der in operation until all involved elements are upgraded to support the ne=
w version. Once the SFC-enabled domain is upgraded, then the new header can=
 be enabled.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; Let's consider now that a version is signaled in the=
 packet: to what extent signaling this information simplifies the SFC opera=
tions, and whether it increases/decreases the serviceability of an SFC-enab=
led domain? Let's also assess to what extent having the version number add =
more complexity in the SFC header treatment when several versions are suppo=
rted by a node/within an SFC enabled domain? How it helps interoperability?=
 Some points for discussion are elaborated below:<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; * If the SFC-enabled domain is configured to support=
 the same version (which is likely): having the version number is not of an=
y help.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; * If the SFC-enabled domain involves some nodes that=
 support version (v1) while others support (v2) (simple case): If these ver=
sion are not backward compatible, this will lead to failures when two adjac=
ent elements in a service chain do not support the same version. The SFC sy=
stem is broken. Having the version number is not of any help in this case.<=
o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; * If the SFC-enabled domain involves some nodes that=
 support version (v1) while others support (v1 and v2):<o:p></o:p></span></=
pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; (a) The nodes that support both v1 and v2 should be =
instructed to decide which version to be used. This can be either part of t=
he specification or be driven by configuration. If a version number is incl=
uded in the spec, I would expect to clarify the behavior in such case.<o:p>=
</o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; (b) Suppose a node that supports only v1 receives a =
packet with header (v2): If this node does not support a notification proce=
dure to inform the source that it does not support that header version, the=
n FAILURES are introduced in the network. This is a degradation of the serv=
ice compared to legacy scheme to structure services. This is not recommende=
d, IMHO.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; (c) If a notification is received from an element ab=
out its supported version: a node can use another version (the logic to sel=
ect other version is another point to discuss) for that communication, but =
what to do for the next flows in the context of the same service chain or o=
ther chains that involves these two nodes as adjacent elements in the same =
chain? Shouldn't these nodes cache the version to use for subsequent exchan=
ge to avoid receiving the notification error each time? Wouldn't that compl=
exity the behavior of the SFC-aware elements?<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; (d) If a notification is received from an element ab=
out its supported version: As this may occurs in various segments of a give=
n service chain, e.g., (A(v1), B(v1,v2), C(v2), D(v1,v2), E(v1)). Notifying=
 the adjacent node each time there is a version mismatch induce an extra de=
lay, that may be not be acceptable for every flow.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; I hope this clarifies my initial concern.<o:p></o:p>=
</span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; Thank you.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; Cheers,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; Med<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; -----Message d'origine-----<o:p></o:p></span></p=
re>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; De : Joel M. Halpern [<a href=3D"mailto:jmh">mai=
lto:jmh</a> at joelhalpern.com]<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; Envoy=E9 : mercredi 25 f=E9vrier 2015 16:10<o:p>=
</o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; =C0 : BOUCADAIR Mohamed IMT/OLN; paulq at cisco.=
com<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; Cc : sfc at ietf.org<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; Objet : Re: [sfc] draft-quinn-sfc-nsh: version n=
umber<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; I would really prefer to keep the version number=
.&nbsp; Even though we have<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; the MD-type identifier and for some MD we have t=
he TLVs.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; The reason is that we may want to change the bas=
e header.&nbsp; For example,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; suppose that the ciscussion about including a fl=
ow identifier in the<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; base header had not come up now.&nbsp; If it cam=
e up later, we would want to<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; be able to have the discussion and make the choi=
ce, rather than being<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; constrained by the lack of a version field.<o:p>=
</o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; Yours,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; Joel<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt; On 2/25/15 10:03 AM, mohamed.boucadair at orange=
.com wrote:<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; Hi Paul, all,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; What is the purpose of having a version numb=
er in the header? Is there a<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; kind of version negotiation that needs to be=
 in place?<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; I checked the I-D but failed to find text th=
at explains the rationale,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; the use of the such field and whether an err=
or will be returned if the<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; version is not supported by the receiving no=
de.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; Wouldn't be preferable to get rid of this fi=
eld given that SFC header<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; can be extended using optional objects and c=
onsistent setup &amp;<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; configuration within an SFC-enabled domain s=
hould be assumed?<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; Thank you<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; Cheers,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; Med<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; ____________________________________________=
___<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; sfc mailing list<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; sfc at ietf.org<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/list=
info/sfc">https://www.ietf.org/mailman/listinfo/sfc</a><o:p></o:p></span></=
pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;">&nbsp;<o:p></o:p></span></pre>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_787AE7BB302AE849A7480A190F8B93300491A1F7OPEXCLILM23corp_--


From nobody Wed Mar  4 08:15:14 2015
Return-Path: <paulq@cisco.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 079781A87A1 for <sfc@ietfa.amsl.com>; Wed,  4 Mar 2015 08:15:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 KTrKpaEhUoFR for <sfc@ietfa.amsl.com>; Wed,  4 Mar 2015 08:15:11 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AEA291A7008 for <sfc@ietf.org>; Wed,  4 Mar 2015 08:14:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11294; q=dns/txt; s=iport; t=1425485688; x=1426695288; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=xh3QRW5cQAW/Vbn7ff0yDa7w0se9HzIhHL9m9mGmuXA=; b=PVz3VV40GvpNM5r/eQtdc/8sCGIxDqzkRHti7N90qHn1qBS1C/fMMgi+ c0idw1q9qSInK9j8zWI3AzUS64/AlqSVXFjf8KkBcI5g4e0Cf3cvSbI+B B7Ouq+kyKT9KMq1zhLS9O7O5WgueuIpWgbHvB0FEiXyXM8h+1tJj04pYd Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AvBQCnLvdU/4oNJK1agj9DgSwExwoCgSlNAQEBAQEBfIQQAQEELUwQAgEIPwcyFBECBA4FiC/XZQEBAQEBAQEBAQEBAQEBAQEBAQEBAReLEoRuB4MXgRQBBI9/iUyBGoMli2mDQCODbm+BRH8BAQE
X-IronPort-AV: E=Sophos;i="5.09,687,1418083200";  d="scan'208,217";a="128880953"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-3.cisco.com with ESMTP; 04 Mar 2015 16:14:48 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id t24GElYu016572 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 4 Mar 2015 16:14:48 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.229]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.03.0195.001; Wed, 4 Mar 2015 10:14:47 -0600
From: "Paul Quinn (paulq)" <paulq@cisco.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Thread-Topic: [sfc] draft-quinn-sfc-nsh: version number
Thread-Index: AQHQVpZVMpEUplI0GU+5ain/rUjPxA==
Date: Wed, 4 Mar 2015 16:14:47 +0000
Message-ID: <08AFD2FB-AC81-479A-9098-0FFEDDBF0A58@cisco.com>
References: <01f9e1a4e6514854a26556e4c6a3e36e@SEAEXCHMBX05.olympus.F5Net.com> <787AE7BB302AE849A7480A190F8B933004919B76@OPEXCLILM23.corporate.adroot.infra.ftgroup> <CDF2F015F4429F458815ED2A6C2B6B0B2E85379B@MBX021-W3-CA-2.exch021.domain.local> <787AE7BB302AE849A7480A190F8B93300491A1AF@OPEXCLILM23.corporate.adroot.infra.ftgroup> <CDF2F015F4429F458815ED2A6C2B6B0B2E8558D0@MBX021-W3-CA-2.exch021.domain.local> <787AE7BB302AE849A7480A190F8B93300491A1F7@OPEXCLILM23.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B93300491A1F7@OPEXCLILM23.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.17.229]
Content-Type: multipart/alternative; boundary="_000_08AFD2FBAC81479A90980FFEDDBF0A58ciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/SGDmqxYrsgk3_-ungd82XCBSfJw>
Cc: Sunil Vallamkonda <sunilvk@f5.com>, "sfc@ietf.org" <sfc@ietf.org>, Ron Parker <Ron_Parker@affirmednetworks.com>
Subject: Re: [sfc] draft-quinn-sfc-nsh: version number
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 04 Mar 2015 16:15:13 -0000

--_000_08AFD2FBAC81479A90980FFEDDBF0A58ciscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable


On Mar 4, 2015, at 11:09 AM, mohamed.boucadair@orange.com<mailto:mohamed.bo=
ucadair@orange.com> wrote:

Re-,

That would be a good start, but still not sufficient IMHO.

If no notification is sent back (which can be the case with the MAY languag=
e), the failure will be experienced till an action is done by the domain op=
erator. This is not desirable.

Having a more strong language for sending back the response (that needs to =
include at least the received packet with the unsupported version) will hav=
e the effect to resend the packet with an adequate version (if multiple ver=
sions are supported). The exact behavior when a version mismatch error is r=
eceived should be explicated in the document IMO.

Perhaps the best way forward: can you please suggest some text that we can =
all review?  I=92m inclined to keep things simple (i.e. simple error messag=
e of sorts) but since you=92ve given this a lot of thought, I=92d love to s=
ee your suggestions.



--_000_08AFD2FBAC81479A90980FFEDDBF0A58ciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <A18BCAF65F73234ABD1DB24CC0A633F8@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;" class=3D"">
<br class=3D"">
<div>
<blockquote type=3D"cite" class=3D"">
<div class=3D"">On Mar 4, 2015, at 11:09 AM, <a href=3D"mailto:mohamed.bouc=
adair@orange.com" class=3D"">
mohamed.boucadair@orange.com</a> wrote:</div>
<br class=3D"Apple-interchange-newline">
<div class=3D"">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)" cl=
ass=3D"">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style class=3D""><!--
/* Font Definitions */
@font-face
	{font-family:Cambria;
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"Segoe UI";
	panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
h1
	{mso-style-priority:9;
	mso-style-link:"Titre 1 Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	font-weight:normal;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Texte brut Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"Pr=E9format=E9 HTML Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Texte de bulles Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.Titre1Car
	{mso-style-name:"Titre 1 Car";
	mso-style-priority:9;
	mso-style-link:"Titre 1";
	font-family:"Cambria","serif";
	color:#365F91;
	font-weight:bold;}
span.PrformatHTMLCar
	{mso-style-name:"Pr=E9format=E9 HTML Car";
	mso-style-priority:99;
	mso-style-link:"Pr=E9format=E9 HTML";
	font-family:Consolas;}
span.TextebrutCar
	{mso-style-name:"Texte brut Car";
	mso-style-priority:99;
	mso-style-link:"Texte brut";
	font-family:"Courier New";
	color:black;
	mso-fareast-language:EN-US;}
span.TextedebullesCar
	{mso-style-name:"Texte de bulles Car";
	mso-style-priority:99;
	mso-style-link:"Texte de bulles";
	font-family:"Tahoma","sans-serif";}
p.Heading1, li.Heading1, div.Heading1
	{mso-style-name:"Heading 1";
	mso-style-link:"Heading 1 Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.Heading1Char
	{mso-style-name:"Heading 1 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 1";
	font-family:"Times New Roman","serif";
	font-weight:bold;}
p.HTMLPreformatted, li.HTMLPreformatted, div.HTMLPreformatted
	{mso-style-name:"HTML Preformatted";
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
p.PlainText, li.PlainText, div.PlainText
	{mso-style-name:"Plain Text";
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
p.BalloonText, li.BalloonText, div.BalloonText
	{mso-style-name:"Balloon Text";
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Segoe UI","sans-serif";}
span.EmailStyle32
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle33
	{mso-style-type:personal;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;}
span.EmailStyle34
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle35
	{mso-style-type:personal;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;}
span.EmailStyle36
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle38
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1094283961;
	mso-list-template-ids:-714036274;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
<div lang=3D"FR" link=3D"#0563C1" vlink=3D"#954F72" class=3D"">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; font-family: 'Courie=
r New';" class=3D"">Re-,<o:p class=3D""></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; font-family: 'Courie=
r New';" class=3D"">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New';" class=3D"">That would be a good start, but still no=
t sufficient IMHO.<o:p class=3D""></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New';" class=3D"">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New';" class=3D"">If no notification is sent back (which c=
an be the case with the MAY language), the failure will be experienced till=
 an action is done by the domain operator.
 This is not desirable. <o:p class=3D""></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New';" class=3D"">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New';" class=3D"">Having a more strong language for sendin=
g back the response (that needs to include at least the received packet wit=
h the unsupported version) will have the
 effect to resend the packet with an adequate version (if multiple versions=
 are supported). The exact behavior when a version mismatch error is receiv=
ed should be explicated in the document IMO.
<o:p class=3D""></o:p></span></p>
<p class=3D"MsoNormal"></p>
</div>
</div>
</div>
</blockquote>
<div><br class=3D"">
</div>
<div>Perhaps the best way forward: can you please suggest some text that we=
 can all review? &nbsp;I=92m inclined to keep things simple (i.e. simple er=
ror message of sorts) but since you=92ve given this a lot of thought, I=92d=
 love to see your suggestions.</div>
<div><br class=3D"">
</div>
<div><br class=3D"">
</div>
</div>
</body>
</html>

--_000_08AFD2FBAC81479A90980FFEDDBF0A58ciscocom_--


From nobody Wed Mar  4 08:41:02 2015
Return-Path: <Ron_Parker@affirmednetworks.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87D5A1A87C5; Wed,  4 Mar 2015 08:40:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 IiChRcDyB-R7; Wed,  4 Mar 2015 08:40:57 -0800 (PST)
Received: from hub021-ca-4.exch021.serverdata.net (hub021-ca-4.exch021.serverdata.net [64.78.22.171]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E73B1A879C; Wed,  4 Mar 2015 08:40:57 -0800 (PST)
Received: from MBX021-W3-CA-2.exch021.domain.local ([10.254.4.78]) by HUB021-CA-4.exch021.domain.local ([10.254.4.39]) with mapi id 14.03.0224.002;  Wed, 4 Mar 2015 08:40:56 -0800
From: Ron Parker <Ron_Parker@affirmednetworks.com>
To: Xuxiaohu <xuxiaohu@huawei.com>, "sfc@ietf.org" <sfc@ietf.org>, "<spring@ietf.org>" <spring@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
Thread-Topic: [sfc] New Version Notification for draft-xu-sfc-using-mpls-spring-02.txt
Thread-Index: AQHQViqf+3y6NXpdeEGpQGeCsEhFG50LqPsAgAAGTiCAAMftMA==
Date: Wed, 4 Mar 2015 16:40:55 +0000
Message-ID: <CDF2F015F4429F458815ED2A6C2B6B0B2E855978@MBX021-W3-CA-2.exch021.domain.local>
References: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0830F7C0@NKGEML512-MBS.china.huawei.com>
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0830F7C0@NKGEML512-MBS.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [50.203.66.100]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/MKF9pFdFx6Oliw_b8gi5QoGmqzs>
Subject: Re: [sfc] New Version Notification for draft-xu-sfc-using-mpls-spring-02.txt
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 04 Mar 2015 16:40:59 -0000

Xiaohu,

I read your latest draft and I do see the elegance of describing a sequence=
 of must-visit nodes as a stack of MPLS labels.   And I see that you've add=
ressed the transport-independence requirement by stating that the MPLS fram=
es could be carried within IP tunnels (i.e., MPLS in UDP, etc.).    But, I =
have a couple of issues that I suggest be addressed.

First, the text is written as if the NSH header is optional and present onl=
y if metadata is required.    The SFC architecture is such that the NSH is =
mandatory.   I think this issue can be combined with the second issue that =
I'll raise below.

Second, the notion is that the SFF's strip the label stack and then restore=
 the label stack.    And since the text states that even when NSH is presen=
t, the SFP ID is not used, the only remaining basis to do this is flow lear=
ning in the SFF.    While I think there are many reasons that may cause SFF=
's to utilize flow learning advantageously, it should not be a fundamental =
necessity to realize an SFF, IMO.   But even if the SFF is a flow learner, =
this is still inadequate since the SF may change the 5-tuple (e.g., NAT) or=
 may launch internally generated flows (e.g., HTTP proxy).   Both cases cou=
ld not be satisfied by flow learning.

What I suggest, instead, is a tighter coupling between the NSH header and t=
he MPLS label stack.   That there be a 1:1 equivalency between {SFP ID, SFP=
 hop index} and the label stack.   Thus, when the SFC-aware SF returns a pa=
cket to the SFF, the {SFP ID, SFP hop index} contained in the NSH be used t=
o push the appropriate label stack onto the packet.    I believe this would=
 bring the approach into conformance with the SFC architectural requirement=
s (mandatory NSH, transport independence) and would solve the problems with=
 flow learning identified above.

   Ron



-----Original Message-----
From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of Xuxiaohu
Sent: Tuesday, March 3, 2015 11:10 PM
To: Xuxiaohu; sfc@ietf.org; <spring@ietf.org>; mpls@ietf.org
Subject: Re: [sfc] New Version Notification for draft-xu-sfc-using-mpls-spr=
ing-02.txt

The rationales for leveraging the MPLS-SPRING mechanism to realize the serv=
ice path layer functionality of the service function chaining are as follow=
s:

1) eliminate the SFC/SFP states on SFFs. This follows the same logic as MPL=
S-SPRING and BIER.
2) utilize the existing encapsulation (e.g., the MPLS-SPRING) to a maximum =
extent. This follows the Transport Derived SFF concept as described in Sect=
ion 4.3.1 of draft-ietf-sfc-architecture. Meanwhile, this is aligned with t=
he current SFC charter, e.g., "...The working group will consider using an =
existing encapsulation (with extensions as appropriate) if a suitable candi=
date is found..."
3) seamlessly support the SFC in a multi-tenant environment (e.g., MPLS VPN=
). For example, the MPLS VPN packet (containing metadata) could be further =
imposed with a label stack which indicates an SFC or SFP associated with th=
at packet. SFFs receiving the above packet would strip the whole label stac=
k and then send the payload of the MPLS packet (with metadata) to the corre=
sponding SFs which are tenant-aware and therefore easily could determine th=
e tenant profile according to the tenant info contained in the metadata (a.=
k.a., the NSH).=20

Best regards,
Xiaohu
=20

> -----Original Message-----
> From: Xuxiaohu
> Sent: Wednesday, March 04, 2015 11:31 AM
> To: sfc@ietf.org; '<spring@ietf.org>'; mpls@ietf.org
> Subject: FW: New Version Notification for=20
> draft-xu-sfc-using-mpls-spring-02.txt
>=20
> Hi all,
>=20
> This document describes how to leverage the MPLS-based source routing=20
> (i.e.,
> MPLS-SPRING) mechanism as developed by the SPRING WG to realize the=20
> service path layer functionality of the service function chaining. In=20
> addition, this document also describes how to carry metadata in an=20
> MPLS packet by using the NSH as a metadata container.
>=20
> Any comments are suggestions are welcome.
>=20
> Best regards,
> Xiaohu
>=20
> > -----Original Message-----
> > From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> > Sent: Wednesday, March 04, 2015 11:24 AM
> > To: Lizhenbin; Luis M. Contreras; Xuxiaohu; Himanshu C. Shah;=20
> > Xuxiaohu; Himanshu Shah; Luis M. Contreras; Lizhenbin
> > Subject: New Version Notification for=20
> > draft-xu-sfc-using-mpls-spring-02.txt
> >
> >
> > A new version of I-D, draft-xu-sfc-using-mpls-spring-02.txt
> > has been successfully submitted by Xiaohu Xu and posted to the IETF
> repository.
> >
> > Name:		draft-xu-sfc-using-mpls-spring
> > Revision:	02
> > Title:		Service Function Chaining Using MPLS-SPRING
> > Document date:	2015-03-03
> > Group:		Individual Submission
> > Pages:		8
> > URL:
> > http://www.ietf.org/internet-drafts/draft-xu-sfc-using-mpls-spring-02.
> > txt
> > Status:
> > https://datatracker.ietf.org/doc/draft-xu-sfc-using-mpls-spring/
> > Htmlized:       http://tools.ietf.org/html/draft-xu-sfc-using-mpls-spri=
ng-02
> > Diff:
> > http://www.ietf.org/rfcdiff?url2=3Ddraft-xu-sfc-using-mpls-spring-02
> >
> > Abstract:
> >    Source Packet Routing in Networking (SPRING) WG specifies a special
> >    source routing mechanism.  Such source routing mechanism can be
> >    leveraged to realize the service path layer functionality of the
> >    service function chaining (i.e, steering traffic through a particula=
r
> >    service function path) by encoding the service function path or the
> >    service function chain information as the explicit path information.
> >    This document describes how to leverage the MPLS-based source routin=
g
> >    mechanism as developed by the SPRING WG to realize the service path
> >    layer functionality of the service function chaining.
> >
> >
> >
> >
> > Please note that it may take a couple of minutes from the time of=20
> > submission until the htmlized version and diff are available at tools.i=
etf.org.
> >
> > The IETF Secretariat

_______________________________________________
sfc mailing list
sfc@ietf.org
https://www.ietf.org/mailman/listinfo/sfc


From nobody Wed Mar  4 08:50:21 2015
Return-Path: <paulq@cisco.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0502C1A87A4 for <sfc@ietfa.amsl.com>; Wed,  4 Mar 2015 08:50:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 Xpc8PMGQ-usq for <sfc@ietfa.amsl.com>; Wed,  4 Mar 2015 08:50:11 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B2181A885B for <sfc@ietf.org>; Wed,  4 Mar 2015 08:50:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10710; q=dns/txt; s=iport; t=1425487812; x=1426697412; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=+Xf6349i/ZwC6CRx5MdqgESVdQYaA1UQR3qBAFzu30Y=; b=hQFeMx92O3AeZdwp6RJL6m2osL4aiOpKQtbJGzhIOxpjnedwEw9qs6iC 3AKSrkN5XHOuCIx0VqcqaLmWhoPnXMysoiiWZKjS8LyBnWLRR7MftNMWG rVLU7l9nhckBH9xmLK5mg+2By8/vlu4FJWYxlL7yDoIbFQ7KRU7bQjQEm w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AzBQDgNvdU/5pdJa1agwJSWgTBDwqFcQKBK00BAQEBAQF8hA8BAQEDAQEBAWsLBQsCAQgYJwcnCxQRAgQOBYgnCA3XcQEBAQEBAQEBAQEBAQEBAQEBAQEBARMEixKEDBEBDg8zB4QrBY9/hC2FH4Eakk4jggIcgVBvgQICBAMXIn8BAQE
X-IronPort-AV: E=Sophos;i="5.09,688,1418083200"; d="scan'208";a="400858388"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-5.cisco.com with ESMTP; 04 Mar 2015 16:50:11 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id t24GoAij010539 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 4 Mar 2015 16:50:10 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.229]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.03.0195.001; Wed, 4 Mar 2015 10:50:10 -0600
From: "Paul Quinn (paulq)" <paulq@cisco.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Thread-Topic: [sfc] draft-quinn-sfc-nsh: version number
Thread-Index: AdBRDDloSX0/55xiS1KsQav7+px1wQAMyamAACHBoQAADvQcAADQYBIAAEAyuoAAIkN7AA==
Date: Wed, 4 Mar 2015 16:50:09 +0000
Message-ID: <39532B21-38F9-41C1-9E32-876393353196@cisco.com>
References: <787AE7BB302AE849A7480A190F8B9330049140B4@OPEXCLILM23.corporate.adroot.infra.ftgroup> <54EDE5B7.6080102@joelhalpern.com> <787AE7BB302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.adroot.infra.ftgroup> <54EF2C9A.3040008@joelhalpern.com> <55A3CDAE-9D74-4174-AC1B-D3F500FABDCE@cisco.com> <787AE7BB302AE849A7480A190F8B933004919B15@OPEXCLILM23.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B933004919B15@OPEXCLILM23.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.17.229]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <35512AA40503AC419EB5774E21EBE021@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/RChP-XtKXY30o2vqieDPQp3P1UE>
Cc: "Joel M. Halpern" <jmh@joelhalpern.com>, "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] draft-quinn-sfc-nsh: version number
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 04 Mar 2015 16:50:18 -0000

Hi Med,

I replied to a later email in the thread =97 my sorting was odd =97 but als=
o wanted to give some comments here.

Paul

> On Mar 4, 2015, at 1:37 AM, mohamed.boucadair@orange.com wrote:
>=20
> Hi Paul,
>=20
> Issues related to co-existence and managing several versions of the heade=
r within a SFC-enabled domain won't disappear with aversion field. As I sai=
d in another message, many open doors are left in the current version of th=
e draft for future extensions: version, optional elements, reserved bits, a=
nd MD type. This is not optimal for a header that is supposed to be compact=
 as possible.

I understand you concern, however, given how reserved bits are handled, the=
y don=92t provide the needed dataplane signaling.


>=20
> My initial concern is how to ensure the extendibility of the header while=
 avoiding operational burden and avoid failures because of the header desig=
n choices.=20

We share the same goal :) but I think the cost of a few version bit far out=
weighs the downside.  =20

>=20
> In addition to the issue related to the version number side effects, ther=
e also failures that will be induced by the non-support of MD Type (note, I=
'm not convinced yet MD type is needed)
>=20
> Adding a sentence that says a packet will be dropped if the received node=
 does not support that version is not sufficient. I listed several points i=
n this thread that need to be addressed.=20

I don=92t think a specific version field changes many of the points you lis=
t, in other words, if a protocol=92s =93features=94 change, you still need =
a method to ensure that the correct format is supported and backward compat=
ibility is understood (to some extent).  If for example, we use a reserved =
bit _and_ mandate parsing of all reserved bits, in essence you just create =
a bigger version field.

>=20
> Thank you.
>=20
> Cheers,
> Med=20
>=20
>> -----Message d'origine-----
>> De : Paul Quinn (paulq) [mailto:paulq@cisco.com]
>> Envoy=E9 : lundi 2 mars 2015 18:51
>> =C0 : Joel M. Halpern
>> Cc : BOUCADAIR Mohamed IMT/OLN; sfc@ietf.org
>> Objet : Re: [sfc] draft-quinn-sfc-nsh: version number
>>=20
>> Hi,
>>=20
>> Jumping in mid-thread.
>>=20
>> Overall, I tend to agree with Joel.  Having an explicit version provides=
 a
>> simple way to handle dataplane format changes.  As Med points out, quick=
ly
>> correctly, IMHO, there are other way to signal changes via reserved bit.
>> In practice though reserved bits are less useful since the convention is
>> to ignore unknown bits, it makes using them for feature changes quite
>> difficult, which then brings up back to explicit versioning that cannot =
be
>> ignored.
>>=20
>> I think Joel's suggestion below makes perfect sense and should be added =
to
>> the draft.
>>=20
>> Paul
>>=20
>>=20
>>> On Feb 26, 2015, at 9:24 AM, Joel M. Halpern <jmh@joelhalpern.com>
>> wrote:
>>>=20
>>> In one sense you are correct.  If you could count on everything being
>> upgraded at once, sure you could just assume common interpretation.
>>> However, we have found over the years that such simultaneous upgrading
>> never works.  You need to be able to transition.
>>>=20
>>> I do agree that we should add text about what to do with version number=
s
>> that are not understood.  There are multiple choices that affect how we
>> can make changes.  My personal preference is:
>>>=20
>>> If an packet presumed to carry an NSH header is received at an SFF, and
>> the SFF does not understnad the version of the protocol as indicated in
>> the base header, the packet MUST be discarded, and the event SHOULD be
>> logged.
>>>=20
>>> This would allow an orderly transition, where devices can be upgraded t=
o
>> understand a new version, then generation of the new version header can =
be
>> enabled.  If a configuration error is made, the packets will be dropped
>> and operators following good practices will get notifications.
>>>=20
>>> Yours,
>>> Joel
>>>=20
>>> On 2/26/15 2:16 AM, mohamed.boucadair@orange.com wrote:
>>>> Hi Joel,
>>>>=20
>>>> I fully agree with the extendibility of the header, but the question i=
s
>> why having a version number will be of help in the context of SFC? Secon=
d,
>> having a version number without specifying the behavior when several
>> versions are supported, when the version number is not supported by an
>> SFC-aware element, etc. leaves open issues out of the spec.
>>>>=20
>>>> The other problem is that the current I-D includes several open doors
>> left for extending the header:
>>>> * version
>>>> * reserved bits
>>>> * optional data
>>>>=20
>>>> This is too much for a header that is supposed to be compact and
>> simple!
>>>>=20
>>>> There are other means to extend the header without signaling the
>> version in the packet. Having a distinct RFC number may be just fine in
>> the context of an unidirectional stream such as SFC.
>>>>=20
>>>> Let us consider the situation where a version number is not explicitly
>> signaled in the packet (but a new RFC updates the base SFC header).
>> Several options can be considered, indeed (those are provided as example=
s
>> for illustration purposes):
>>>> * An operator can make sure that its SFC-enabled domain is configured
>> in a consistent manner to support one and only one version of the header=
.
>> No interoperability issues is encountered in this case.
>>>> * An operator that wants to upgrade its SFC-enabled domain to support =
a
>> new specification of the SFC header: An operator can decide to proceed t=
o
>> a software/hardware updates but can maintain the old header in operation
>> until all involved elements are upgraded to support the new version. Onc=
e
>> the SFC-enabled domain is upgraded, then the new header can be enabled.
>>>>=20
>>>> Let's consider now that a version is signaled in the packet: to what
>> extent signaling this information simplifies the SFC operations, and
>> whether it increases/decreases the serviceability of an SFC-enabled
>> domain? Let's also assess to what extent having the version number add
>> more complexity in the SFC header treatment when several versions are
>> supported by a node/within an SFC enabled domain? How it helps
>> interoperability? Some points for discussion are elaborated below:
>>>>=20
>>>> * If the SFC-enabled domain is configured to support the same version
>> (which is likely): having the version number is not of any help.
>>>> * If the SFC-enabled domain involves some nodes that support version
>> (v1) while others support (v2) (simple case): If these version are not
>> backward compatible, this will lead to failures when two adjacent elemen=
ts
>> in a service chain do not support the same version. The SFC system is
>> broken. Having the version number is not of any help in this case.
>>>> * If the SFC-enabled domain involves some nodes that support version
>> (v1) while others support (v1 and v2):
>>>>=20
>>>> (a) The nodes that support both v1 and v2 should be instructed to
>> decide which version to be used. This can be either part of the
>> specification or be driven by configuration. If a version number is
>> included in the spec, I would expect to clarify the behavior in such cas=
e.
>>>>=20
>>>> (b) Suppose a node that supports only v1 receives a packet with header
>> (v2): If this node does not support a notification procedure to inform t=
he
>> source that it does not support that header version, then FAILURES are
>> introduced in the network. This is a degradation of the service compared
>> to legacy scheme to structure services. This is not recommended, IMHO.
>>>>=20
>>>> (c) If a notification is received from an element about its supported
>> version: a node can use another version (the logic to select other versi=
on
>> is another point to discuss) for that communication, but what to do for
>> the next flows in the context of the same service chain or other chains
>> that involves these two nodes as adjacent elements in the same chain?
>> Shouldn't these nodes cache the version to use for subsequent exchange t=
o
>> avoid receiving the notification error each time? Wouldn't that complexi=
ty
>> the behavior of the SFC-aware elements?
>>>>=20
>>>> (d) If a notification is received from an element about its supported
>> version: As this may occurs in various segments of a given service chain=
,
>> e.g., (A(v1), B(v1,v2), C(v2), D(v1,v2), E(v1)). Notifying the adjacent
>> node each time there is a version mismatch induce an extra delay, that m=
ay
>> be not be acceptable for every flow.
>>>>=20
>>>> I hope this clarifies my initial concern.
>>>>=20
>>>> Thank you.
>>>>=20
>>>> Cheers,
>>>> Med
>>>>=20
>>>>> -----Message d'origine-----
>>>>> De : Joel M. Halpern [mailto:jmh@joelhalpern.com]
>>>>> Envoy=E9 : mercredi 25 f=E9vrier 2015 16:10
>>>>> =C0 : BOUCADAIR Mohamed IMT/OLN; paulq@cisco.com
>>>>> Cc : sfc@ietf.org
>>>>> Objet : Re: [sfc] draft-quinn-sfc-nsh: version number
>>>>>=20
>>>>> I would really prefer to keep the version number.  Even though we hav=
e
>>>>> the MD-type identifier and for some MD we have the TLVs.
>>>>>=20
>>>>> The reason is that we may want to change the base header.  For
>> example,
>>>>> suppose that the ciscussion about including a flow identifier in the
>>>>> base header had not come up now.  If it came up later, we would want
>> to
>>>>> be able to have the discussion and make the choice, rather than being
>>>>> constrained by the lack of a version field.
>>>>>=20
>>>>> Yours,
>>>>> Joel
>>>>>=20
>>>>>=20
>>>>> On 2/25/15 10:03 AM, mohamed.boucadair@orange.com wrote:
>>>>>> Hi Paul, all,
>>>>>>=20
>>>>>> What is the purpose of having a version number in the header? Is
>> there a
>>>>>> kind of version negotiation that needs to be in place?
>>>>>>=20
>>>>>> I checked the I-D but failed to find text that explains the
>> rationale,
>>>>>> the use of the such field and whether an error will be returned if
>> the
>>>>>> version is not supported by the receiving node.
>>>>>>=20
>>>>>> Wouldn't be preferable to get rid of this field given that SFC heade=
r
>>>>>> can be extended using optional objects and consistent setup &
>>>>>> configuration within an SFC-enabled domain should be assumed?
>>>>>>=20
>>>>>> Thank you
>>>>>>=20
>>>>>> Cheers,
>>>>>>=20
>>>>>> Med
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> _______________________________________________
>>>>>> sfc mailing list
>>>>>> sfc@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/sfc
>>>>>>=20
>>>>=20
>=20


From nobody Wed Mar  4 10:48:48 2015
Return-Path: <smkumar@cisco.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E07E1A872A for <sfc@ietfa.amsl.com>; Wed,  4 Mar 2015 10:48:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 eOxDUrwqwKE7 for <sfc@ietfa.amsl.com>; Wed,  4 Mar 2015 10:48:45 -0800 (PST)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 089C21A1A22 for <sfc@ietf.org>; Wed,  4 Mar 2015 10:48:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2151; q=dns/txt; s=iport; t=1425494925; x=1426704525; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=Z649LhpVIkX5Kph6Vi/EyzCBicpSU3Gd9uASMMVDSBA=; b=e2hUP6BwBs4Wg5Gpq4eWd2aEyRFtcqVWkki5DCSAXw5RPtm+eiMBj1Fi wbzgTaSz2aunfhOcqyRJl4JYDG9sZ14fx3kwl1hliqz8Z73j5FMRonak1 oejw3AnVBAp3V0Mmbfh6KzfmeQUacljaxzcHckl37We8jHSoykCMfXpSw 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AxBQBKU/dU/4UNJK1agwJSWgTBGoVxAoEtTQEBAQEBAXyEEAEBBDo9EgIBCDYQMhsBBgMCBBMJEIgWDdd6AQEBAQEBBAEBAQEBAQEbixKEdYQrBY9/g2OFaYEaOYJsi2mDQCODbm8BgUN/AQEB
X-IronPort-AV: E=Sophos;i="5.09,689,1418083200"; d="scan'208";a="128935445"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by alln-iport-5.cisco.com with ESMTP; 04 Mar 2015 18:48:43 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id t24ImhbT025688 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <sfc@ietf.org>; Wed, 4 Mar 2015 18:48:43 GMT
Received: from xmb-aln-x09.cisco.com ([169.254.4.43]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.03.0195.001; Wed, 4 Mar 2015 12:48:43 -0600
From: "Surendra Kumar (smkumar)" <smkumar@cisco.com>
To: "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: New Version Notification for draft-kumar-sfc-offloads-00.txt
Thread-Index: AQHQVqoghYWONTwLLESkPa19GEYCJJ0MiM+A
Date: Wed, 4 Mar 2015 18:48:43 +0000
Message-ID: <D11C90EC.18D0C%smkumar@cisco.com>
References: <20150304183622.20056.47379.idtracker@ietfa.amsl.com>
In-Reply-To: <20150304183622.20056.47379.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.7.141117
x-originating-ip: [10.24.155.148]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F917C757DD4E644BAA5A7D8FA468BD68@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/O9iDAKbI1PoFW5K13biJg01V_fo>
Subject: [sfc] FW: New Version Notification for draft-kumar-sfc-offloads-00.txt
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 04 Mar 2015 18:48:46 -0000

Hi all:

We posted a new draft, but with old content. After the presentation on
simple offloads + Optimization at HNL, we received a lot of feedback.

In including it, we have split the SFP Path Optimization draft into two:
1) this one which limits itself to the offload between SF and SFF
2) the original sfp optimization draft, which focuses on optimization of
the SFP among the SFFs

#2 will be updated to reflect the split

Thanks and we appreciate your comments/questions,
Surendra.

On 3/4/15, 10:36 AM, "internet-drafts@ietf.org" <internet-drafts@ietf.org>
wrote:

>
>A new version of I-D, draft-kumar-sfc-offloads-00.txt
>has been successfully submitted by Surendra Kumar and posted to the
>IETF repository.
>
>Name:		draft-kumar-sfc-offloads
>Revision:	00
>Title:		Service Function Simple Offloads
>Document date:	2015-03-04
>Group:		Individual Submission
>Pages:		15
>URL:           =20
>http://www.ietf.org/internet-drafts/draft-kumar-sfc-offloads-00.txt
>Status:         https://datatracker.ietf.org/doc/draft-kumar-sfc-offloads/
>Htmlized:       http://tools.ietf.org/html/draft-kumar-sfc-offloads-00
>
>
>Abstract:
>   Service Function Chaining (SFC) enables services to be delivered by
>   selective traffic steering through an ordered set of service
>   functions.  Once classified into an SFC, the traffic for a given flow
>   is steered through all the service functions of the SFC for the life
>   of the traffic flow even though this is often not necessary.
>   Steering traffic to service functions only while required and not
>   otherwise, leads to shorter SFC forwarding paths with improved
>   latencies, reduced resource consumption and better user experience.
>
>   This document describes the rationale, techniques and necessary
>   protocol extensions to achieve such optimization, with focus on one
>   such technique termed "simple offloads".
>
>
>                 =20
>       =20
>
>
>Please note that it may take a couple of minutes from the time of
>submission
>until the htmlized version and diff are available at tools.ietf.org.
>
>The IETF Secretariat
>


From nobody Wed Mar  4 11:54:55 2015
Return-Path: <jmh@joelhalpern.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 583481A88AF for <sfc@ietfa.amsl.com>; Wed,  4 Mar 2015 11:54:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 bNOE-Soym5zl for <sfc@ietfa.amsl.com>; Wed,  4 Mar 2015 11:54:50 -0800 (PST)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B36871ACE37 for <sfc@ietf.org>; Wed,  4 Mar 2015 11:54:45 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 9864924723E; Wed,  4 Mar 2015 11:54:45 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from Joels-MacBook-Pro.local (unknown [88.131.67.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 364DB24032F; Wed,  4 Mar 2015 11:54:44 -0800 (PST)
Message-ID: <54F76301.8050906@joelhalpern.com>
Date: Wed, 04 Mar 2015 14:54:41 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: mohamed.boucadair@orange.com,  Ron Parker <Ron_Parker@affirmednetworks.com>, Sunil Vallamkonda <sunilvk@f5.com>
References: <01f9e1a4e6514854a26556e4c6a3e36e@SEAEXCHMBX05.olympus.F5Net.com> <787AE7BB302AE849A7480A190F8B933004919B76@OPEXCLILM23.corporate.adroot.infra.ftgroup> <CDF2F015F4429F458815ED2A6C2B6B0B2E85379B@MBX021-W3-CA-2.exch021.domain.local> <787AE7BB302AE849A7480A190F8B93300491A1AF@OPEXCLILM23.corporate.adroot.infra.ftgroup> <CDF2F015F4429F458815ED2A6C2B6B0B2E8558D0@MBX021-W3-CA-2.exch021.domain.local> <787AE7BB302AE849A7480A190F8B93300491A1F7@OPEXCLILM23.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B93300491A1F7@OPEXCLILM23.corporate.adroot.infra.ftgroup>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/ZERGU6iN4XsXnQBu0MQORsDbzeI>
Cc: "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] draft-quinn-sfc-nsh: version number
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 04 Mar 2015 19:54:53 -0000

Med, you seem to be assuming that misconfiguration MUST be addressed by 
immediate data plane response.
That is a major protocol requirement which is often counter-productive. 
  It is not at all clear that the ingress classifier would know what to 
do with such a notification any more than the device which does not 
understand the specific version.

It is extremely likely that repair will require human intervention.  It 
is also likely that management plane notifications will go to the same 
controller that set up the ingress instructions, so if there is feasible 
automatic response, the sytem can respond.

Requiring an in-band response to the classifier adds complication 
without significantly improving responsiveness.

Yours,
Joel

On 3/4/15 11:09 AM, mohamed.boucadair@orange.com wrote:
> Re-,
>
> That would be a good start, but still not sufficient IMHO.
>
> If no notification is sent back (which can be the case with the MAY
> language), the failure will be experienced till an action is done by the
> domain operator. This is not desirable.
>
> Having a more strong language for sending back the response (that needs
> to include at least the received packet with the unsupported version)
> will have the effect to resend the packet with an adequate version (if
> multiple versions are supported). The exact behavior when a version
> mismatch error is received should be explicated in the document IMO.
>
> Cheers,
>
> Med
>
> *De :*Ron Parker [mailto:Ron_Parker@affirmednetworks.com]
> *Envoyé :* mercredi 4 mars 2015 16:50
> *À :* BOUCADAIR Mohamed IMT/OLN; Sunil Vallamkonda
> *Cc :* sfc@ietf.org
> *Objet :* RE: Re: [sfc] draft-quinn-sfc-nsh: version number
>
> Med,
>
> I agree that we should add additional text around the expected behavior
> regarding version incompatibility.   We could state that the SFF or SF
> perceiving this incompatibility MUST drop such a packet and MAY generate
> an OAM response in the reverse direction, although the exact nature of
> that response is outside the scope of the NSH draft.
>
>     Ron
>
> *From:*mohamed.boucadair@orange.com
> <mailto:mohamed.boucadair@orange.com> [mailto:mohamed.boucadair@orange.com]
> *Sent:* Wednesday, March 4, 2015 10:43 AM
> *To:* Ron Parker; Sunil Vallamkonda
> *Cc:* sfc@ietf.org <mailto:sfc@ietf.org>
> *Subject:* RE: Re: [sfc] draft-quinn-sfc-nsh: version number
>
> Hi Ron,
>
> If the version number is maintained, discussing the behavior of a node
> if it supports several versions, if it does not support the version of a
> packet it receives, etc. is not about OAM. This is part of the behavior
> that needs to be specified in the document.
>
> Cheers,
>
> Med
>
> *De :*Ron Parker [mailto:Ron_Parker@affirmednetworks.com]
> *Envoyé :* mercredi 4 mars 2015 16:03
> *À :* BOUCADAIR Mohamed IMT/OLN; Sunil Vallamkonda
> *Cc :* sfc@ietf.org <mailto:sfc@ietf.org>
> *Objet :* RE: Re: [sfc] draft-quinn-sfc-nsh: version number
>
> When we take up OAM, we could consider these ICMP-like behaviors – i.e.,
> OAM packet containing “Version Incompatible” sent in the reverse
> direction on the involved RSP.   But I’m not sure what should be
> discussed in this draft, since OAM is explicitly out of scope.
>
>     Ron
>
> *From:*sfc [mailto:sfc-bounces@ietf.org] *On Behalf Of
> *mohamed.boucadair@orange.com <mailto:mohamed.boucadair@orange.com>
> *Sent:* Wednesday, March 4, 2015 1:47 AM
> *To:* Sunil Vallamkonda
> *Cc:* sfc@ietf.org <mailto:sfc@ietf.org>
> *Subject:* Re: [sfc] draft-quinn-sfc-nsh: version number
>
> Hi Sunil,
>
> There is no such notification in the current spec.
>
> Below my thoughts about this point:
>
> ==
>
> (b) Suppose a node that supports only v1 receives a packet with header
> (v2): If this node does not support a notification procedure to inform
> the source that it does not support that header version, then FAILURES
> are introduced in the network. This is a degradation of the service
> compared to legacy scheme to structure services. This is not
> recommended, IMHO.
>
> (c) If a notification is received from an element about its supported
> version: a node can use another version (the logic to select other
> version is another point to discuss) for that communication, but what to
> do for the next flows in the context of the same service chain or other
> chains that involves these two nodes as adjacent elements in the same
> chain? Shouldn't these nodes cache the version to use for subsequent
> exchange to avoid receiving the notification error each time? Wouldn't
> that complexity the behavior of the SFC-aware elements?
>
> (d) If a notification is received from an element about its supported
> version: As this may occurs in various segments of a given service
> chain, e.g., (A(v1), B(v1,v2), C(v1), D(v1,v2), E(v1)). Notifying the
> adjacent node each time there is a version mismatch induce an extra
> delay, that may be not be acceptable for every flow.
>
> ==
>
> Thank you.
>
> Cheers,
>
> Med
>
> *De :*sfc [mailto:sfc-bounces@ietf.org] *De la part de* Sunil Vallamkonda
> *Envoyé :* mardi 3 mars 2015 20:43
> *À :* sfc@ietf.org <mailto:sfc@ietf.org>
> *Objet :* Re: [sfc] draft-quinn-sfc-nsh: version number
>
> Hi,
>
> Just going through the thread on version number (jumping in mid-thread),
>
> Apart from the version mismatched (unsupported) packet dropped and
> logged, is there a plan for a back off mechanism by SFF to notify sender
> and avoid being overwhelmed with such packets ?
>
> Thank you,
>
> Sunil.
>
>
>   Re: [sfc] draft-quinn-sfc-nsh: version number**
>
> ------------------------------------------------------------------------
>
>   * /From/: "Paul Quinn (paulq)" <paulq at cisco.com
>     <mailto:paulq@DOMAIN.HIDDEN>>
>   * /To/: "Joel M. Halpern" <jmh at joelhalpern.com
>     <mailto:jmh@DOMAIN.HIDDEN>>
>   * /Cc/: "mohamed.boucadair at orange.com
>     <mailto:mohamed.boucadair@DOMAIN.HIDDEN>" <mohamed.boucadair at
>     orange.com <mailto:mohamed.boucadair@DOMAIN.HIDDEN>>, "sfc at
>     ietf.org <mailto:sfc@DOMAIN.HIDDEN>" <sfc at ietf.org
>     <mailto:sfc@DOMAIN.HIDDEN>>
>   * /Date/: Mon, 2 Mar 2015 17:50:53 +0000
>   * /In-reply-to/: <54EF2C9A.3040008@joelhalpern.com
>     <http://www.ietf.org/mail-archive/web/sfc/current/msg03181.html>>
>   * /References/:
>     <787AE7BB302AE849A7480A190F8B9330049140B4@OPEXCLILM23.corporate.adroot.infra.ftgroup
>     <mailto:787AE7BB302AE849A7480A190F8B9330049140B4@OPEXCLILM23.corporate.adroot.infra.ftgroup>>
>     <54EDE5B7.6080102@joelhalpern.com
>     <http://www.ietf.org/mail-archive/web/sfc/current/msg03151.html>>
>     <787AE7BB302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.adroot.infra.ftgroup
>     <mailto:787AE7BB302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.adroot.infra.ftgroup>>
>     <54EF2C9A.3040008@joelhalpern.com
>     <http://www.ietf.org/mail-archive/web/sfc/current/msg03181.html>>
>   * /List-id/: Network Service Chaining <sfc.ietf.org>
>
> ------------------------------------------------------------------------
>
> Hi,
>
>
>
> Jumping in mid-thread.
>
>
>
> Overall, I tend to agree with Joel.  Having an explicit version provides a simple way to handle dataplane format changes.  As Med points out, quickly correctly, IMHO, there are other way to signal changes via reserved bit.  In practice though reserved bits are less useful since the convention is to ignore unknown bits, it makes using them for feature changes quite difficult, which then brings up back to explicit versioning that cannot be ignored.
>
>
>
> I think Joel’s suggestion below makes perfect sense and should be added to the draft.
>
>
>
> Paul
>
>
>
>
>
>> On Feb 26, 2015, at 9:24 AM, Joel M. Halpern <jmh at joelhalpern.com> wrote:
>
>>
>
>> In one sense you are correct.  If you could count on everything being upgraded at once, sure you could just assume common interpretation.
>
>> However, we have found over the years that such simultaneous upgrading never works.  You need to be able to transition.
>
>>
>
>> I do agree that we should add text about what to do with version numbers that are not understood.  There are multiple choices that affect how we can make changes.  My personal preference is:
>
>>
>
>> If an packet presumed to carry an NSH header is received at an SFF, and the SFF does not understnad the version of the protocol as indicated in the base header, the packet MUST be discarded, and the event SHOULD be logged.
>
>>
>
>> This would allow an orderly transition, where devices can be upgraded to understand a new version, then generation of the new version header can be enabled.  If a configuration error is made, the packets will be dropped and operators following good practices will get notifications.
>
>>
>
>> Yours,
>
>> Joel
>
>>
>
>> On 2/26/15 2:16 AM, mohamed.boucadair at orange.com wrote:
>
>>> Hi Joel,
>
>>>
>
>>> I fully agree with the extendibility of the header, but the question is why having a version number will be of help in the context of SFC? Second, having a version number without specifying the behavior when several versions are supported, when the version number is not supported by an SFC-aware element, etc. leaves open issues out of the spec.
>
>>>
>
>>> The other problem is that the current I-D includes several open doors left for extending the header:
>
>>> * version
>
>>> * reserved bits
>
>>> * optional data
>
>>>
>
>>> This is too much for a header that is supposed to be compact and simple!
>
>>>
>
>>> There are other means to extend the header without signaling the version in the packet. Having a distinct RFC number may be just fine in the context of an unidirectional stream such as SFC.
>
>>>
>
>>> Let us consider the situation where a version number is not explicitly signaled in the packet (but a new RFC updates the base SFC header). Several options can be considered, indeed (those are provided as examples for illustration purposes):
>
>>> * An operator can make sure that its SFC-enabled domain is configured in a consistent manner to support one and only one version of the header. No interoperability issues is encountered in this case.
>
>>> * An operator that wants to upgrade its SFC-enabled domain to support a new specification of the SFC header: An operator can decide to proceed to a software/hardware updates but can maintain the old header in operation until all involved elements are upgraded to support the new version. Once the SFC-enabled domain is upgraded, then the new header can be enabled.
>
>>>
>
>>> Let's consider now that a version is signaled in the packet: to what extent signaling this information simplifies the SFC operations, and whether it increases/decreases the serviceability of an SFC-enabled domain? Let's also assess to what extent having the version number add more complexity in the SFC header treatment when several versions are supported by a node/within an SFC enabled domain? How it helps interoperability? Some points for discussion are elaborated below:
>
>>>
>
>>> * If the SFC-enabled domain is configured to support the same version (which is likely): having the version number is not of any help.
>
>>> * If the SFC-enabled domain involves some nodes that support version (v1) while others support (v2) (simple case): If these version are not backward compatible, this will lead to failures when two adjacent elements in a service chain do not support the same version. The SFC system is broken. Having the version number is not of any help in this case.
>
>>> * If the SFC-enabled domain involves some nodes that support version (v1) while others support (v1 and v2):
>
>>>
>
>>> (a) The nodes that support both v1 and v2 should be instructed to decide which version to be used. This can be either part of the specification or be driven by configuration. If a version number is included in the spec, I would expect to clarify the behavior in such case.
>
>>>
>
>>> (b) Suppose a node that supports only v1 receives a packet with header (v2): If this node does not support a notification procedure to inform the source that it does not support that header version, then FAILURES are introduced in the network. This is a degradation of the service compared to legacy scheme to structure services. This is not recommended, IMHO.
>
>>>
>
>>> (c) If a notification is received from an element about its supported version: a node can use another version (the logic to select other version is another point to discuss) for that communication, but what to do for the next flows in the context of the same service chain or other chains that involves these two nodes as adjacent elements in the same chain? Shouldn't these nodes cache the version to use for subsequent exchange to avoid receiving the notification error each time? Wouldn't that complexity the behavior of the SFC-aware elements?
>
>>>
>
>>> (d) If a notification is received from an element about its supported version: As this may occurs in various segments of a given service chain, e.g., (A(v1), B(v1,v2), C(v2), D(v1,v2), E(v1)). Notifying the adjacent node each time there is a version mismatch induce an extra delay, that may be not be acceptable for every flow.
>
>>>
>
>>> I hope this clarifies my initial concern.
>
>>>
>
>>> Thank you.
>
>>>
>
>>> Cheers,
>
>>> Med
>
>>>
>
>>>> -----Message d'origine-----
>
>>>> De : Joel M. Halpern [mailto:jmh  at joelhalpern.com]
>
>>>> Envoyé : mercredi 25 février 2015 16:10
>
>>>> À : BOUCADAIR Mohamed IMT/OLN; paulq at cisco.com
>
>>>> Cc : sfc at ietf.org
>
>>>> Objet : Re: [sfc] draft-quinn-sfc-nsh: version number
>
>>>>
>
>>>> I would really prefer to keep the version number.  Even though we have
>
>>>> the MD-type identifier and for some MD we have the TLVs.
>
>>>>
>
>>>> The reason is that we may want to change the base header.  For example,
>
>>>> suppose that the ciscussion about including a flow identifier in the
>
>>>> base header had not come up now.  If it came up later, we would want to
>
>>>> be able to have the discussion and make the choice, rather than being
>
>>>> constrained by the lack of a version field.
>
>>>>
>
>>>> Yours,
>
>>>> Joel
>
>>>>
>
>>>>
>
>>>> On 2/25/15 10:03 AM, mohamed.boucadair at orange.com wrote:
>
>>>>> Hi Paul, all,
>
>>>>>
>
>>>>> What is the purpose of having a version number in the header? Is there a
>
>>>>> kind of version negotiation that needs to be in place?
>
>>>>>
>
>>>>> I checked the I-D but failed to find text that explains the rationale,
>
>>>>> the use of the such field and whether an error will be returned if the
>
>>>>> version is not supported by the receiving node.
>
>>>>>
>
>>>>> Wouldn't be preferable to get rid of this field given that SFC header
>
>>>>> can be extended using optional objects and consistent setup &
>
>>>>> configuration within an SFC-enabled domain should be assumed?
>
>>>>>
>
>>>>> Thank you
>
>>>>>
>
>>>>> Cheers,
>
>>>>>
>
>>>>> Med
>
>>>>>
>
>>>>>
>
>>>>>
>
>>>>> _______________________________________________
>
>>>>> sfc mailing list
>
>>>>> sfc at ietf.org
>
>>>>>https://www.ietf.org/mailman/listinfo/sfc
>
>>>>>
>
>>>
>
>
>
>
>
> _______________________________________________
> sfc mailing list
> sfc@ietf.org
> https://www.ietf.org/mailman/listinfo/sfc
>


From nobody Wed Mar  4 14:30:18 2015
Return-Path: <sunilvk@f5.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75EF01A8988 for <sfc@ietfa.amsl.com>; Wed,  4 Mar 2015 14:30:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.01
X-Spam-Level: 
X-Spam-Status: No, score=-7.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 RcsBe4aLFuJY for <sfc@ietfa.amsl.com>; Wed,  4 Mar 2015 14:30:16 -0800 (PST)
Received: from mail.f5.com (mail.f5.com [208.85.209.139]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 251421A88EA for <sfc@ietf.org>; Wed,  4 Mar 2015 14:30:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=f5.com; i=@f5.com; q=dns/txt; s=seattle; t=1425508217; x=1457044217; h=from:to:subject:date:message-id:mime-version; bh=RXv3tOdvSPuszAah3SwGjTg301NixKET2e5is8jTfBI=; b=X9emA4hWsjr/RLagP89gYuC4Bh6bSfAdu1UpERNtQJZJnVKuqTbyy1pB HYNOJjs5dPLbp+JANBYAiyya5sVmekfSqSIQd7mAiA/AJHzr5iyoA3NnE P0PDNlf8HCOEIrHMstmiViKVKAuGfsVBglVs1hRDIFjfg48zm1egADQWg 8=;
X-IronPort-AV: E=Sophos;i="5.11,343,1422921600";  d="scan'208,217";a="151744219"
X-IPAS-Result: A2AmBgDIhvdU/+sKqMBagj+BFVsDvyWBUBYFAQmFcYFyAQEBAQEBfIQWLV4BDHQmAQQbiDTYT498gjgMQYExBYFMkhqHPZIXhBGCM38BAQE
Received: from oracle-apps.f5net.com (HELO exchmail.f5net.com) ([192.168.10.235]) by mail.f5.com with ESMTP/TLS/AES256-SHA; 04 Mar 2015 22:30:12 +0000
Received: from SEAEXCHMBX05.olympus.F5Net.com (192.168.15.227) by seaexchmbx01.olympus.F5Net.com (192.168.15.223) with Microsoft SMTP Server (TLS) id 15.0.1044.25; Wed, 4 Mar 2015 14:30:11 -0800
Received: from SEAEXCHMBX05.olympus.F5Net.com ([fe80::9cc0:5dc7:726d:3b50]) by SEAEXCHMBX05.olympus.F5Net.com ([fe80::9cc0:5dc7:726d:3b50%21]) with mapi id 15.00.1044.021; Wed, 4 Mar 2015 14:30:11 -0800
From: Sunil Vallamkonda <sunilvk@f5.com>
To: "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: VxLAN-gpe vs nvo3
Thread-Index: AdBWyasoNMCWbHukTmuokx+wl7gJEg==
Date: Wed, 4 Mar 2015 22:30:11 +0000
Message-ID: <6f6ce3fa863b4adbbdd6a534ddbf2e4f@SEAEXCHMBX05.olympus.F5Net.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.168.15.239]
Content-Type: multipart/alternative; boundary="_000_6f6ce3fa863b4adbbdd6a534ddbf2e4fSEAEXCHMBX05olympusF5Ne_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/nBbsDlWHG82dTn9GqczhlZA8rOo>
Subject: [sfc] VxLAN-gpe vs nvo3
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 04 Mar 2015 22:30:17 -0000

--_000_6f6ce3fa863b4adbbdd6a534ddbf2e4fSEAEXCHMBX05olympusF5Ne_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Per http://tools.ietf.org/html/draft-quinn-sfc-nsh-07
Section 11.2, VxLAN-gpe can be an encapsulation.
However,  how does the VxLAN-gpe header co-exist with overlapping VxLAN hea=
der modification by nvo3:
https://datatracker.ietf.org/doc/draft-chen-nvo3-load-banlancing/

Sunil




--_000_6f6ce3fa863b4adbbdd6a534ddbf2e4fSEAEXCHMBX05olympusF5Ne_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Per <a href=3D"http://tools.ietf.org/html/draft-quin=
n-sfc-nsh-07">
http://tools.ietf.org/html/draft-quinn-sfc-nsh-07</a><o:p></o:p></p>
<p class=3D"MsoNormal">Section 11.2, VxLAN-gpe can be an encapsulation.<o:p=
></o:p></p>
<p class=3D"MsoNormal">However,&nbsp; how does the VxLAN-gpe header co-exis=
t with overlapping VxLAN header modification by nvo3:<o:p></o:p></p>
<p class=3D"MsoNormal"><a href=3D"https://datatracker.ietf.org/doc/draft-ch=
en-nvo3-load-banlancing/">https://datatracker.ietf.org/doc/draft-chen-nvo3-=
load-banlancing/</a><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Sunil<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_6f6ce3fa863b4adbbdd6a534ddbf2e4fSEAEXCHMBX05olympusF5Ne_--


From nobody Wed Mar  4 14:55:58 2015
Return-Path: <kreeger@cisco.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE4411A89A9; Wed,  4 Mar 2015 14:55:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 hDfJKSdWbOoF; Wed,  4 Mar 2015 14:55:55 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 55DE01A1BE0; Wed,  4 Mar 2015 14:55:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5457; q=dns/txt; s=iport; t=1425509755; x=1426719355; h=from:to:subject:date:message-id:mime-version; bh=Jp7sjPXQIgA1s6njEQhrpDBWHIZi16j5MnLrQTY2hpI=; b=YN5gc3E7iPz9VufsHKCBZWOZV6Ny5yOHS5rRknUPJoNz61FstXlC4C0h bGIEVUa1cjF7tTuifFArRD5ZIAjGcE6OGZ5y2i2B+d2Vh23DsBpd1+wa9 2L+T6nXKd8c7gkfX8Wk4mTs7GkQPZqcYM8xkWsoW3WTEbkRSuinD99j8l o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ChBgDxi/dU/40NJK1agj9DUloEvyWBdYVxgSVNAQEBAQEBfIQPAQIELV4BCBEDAQIoORQJCgQBEogvDdgGAQEBAQYBAQEBAR2LEoRdDYQ2BYFMjjeDY4VqgRo5jleDQCOCAhyBUG+BRH8BAQE
X-IronPort-AV: E=Sophos;i="5.11,343,1422921600";  d="scan'208,217";a="397856558"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by rcdn-iport-9.cisco.com with ESMTP; 04 Mar 2015 22:55:54 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id t24Mts5e020405 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 4 Mar 2015 22:55:54 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.159]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.03.0195.001; Wed, 4 Mar 2015 16:55:54 -0600
From: "Larry Kreeger (kreeger)" <kreeger@cisco.com>
To: Sunil Vallamkonda <sunilvk@f5.com>, "sfc@ietf.org" <sfc@ietf.org>, "nvo3@ietf.org" <nvo3@ietf.org>
Thread-Topic: [sfc] VxLAN-gpe vs nvo3
Thread-Index: AQHQVs5dZmHcPmdvhEKaP2UIX18Xzg==
Date: Wed, 4 Mar 2015 22:55:53 +0000
Message-ID: <D11CCB38.13A67D%kreeger@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.8.150116
x-originating-ip: [10.155.166.41]
Content-Type: multipart/alternative; boundary="_000_D11CCB3813A67Dkreegerciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/2BokVISpxOstT5aDKqV84RnI_6c>
Subject: Re: [sfc] VxLAN-gpe vs nvo3
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 04 Mar 2015 22:55:57 -0000

--_000_D11CCB3813A67Dkreegerciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Sunil,

It seems like your question would be more appropriate for the NVO3 mailer t=
han the SFC one (so I added NVO3).

Note that the ideas covered in draft-chen-nvo3-load-banlancing do not seem =
to be part of the NVO3 charter, nor is it part of the NVO3 problem statemen=
t, nor has it been discussed on the NVO3 mailer to my knowledge.  I did tak=
e a look at the draft, and I am skeptical of its cost/benefit for implement=
ation.

 - Larry

From: Sunil Vallamkonda <sunilvk@f5.com<mailto:sunilvk@f5.com>>
Date: Wednesday, March 4, 2015 2:30 PM
To: "sfc@ietf.org<mailto:sfc@ietf.org>" <sfc@ietf.org<mailto:sfc@ietf.org>>
Subject: [sfc] VxLAN-gpe vs nvo3

Per http://tools.ietf.org/html/draft-quinn-sfc-nsh-07
Section 11.2, VxLAN-gpe can be an encapsulation.
However,  how does the VxLAN-gpe header co-exist with overlapping VxLAN hea=
der modification by nvo3:
https://datatracker.ietf.org/doc/draft-chen-nvo3-load-banlancing/

Sunil




--_000_D11CCB3813A67Dkreegerciscocom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <8C29BD433EA6A0409D1294A81CDBC392@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif; ">
<div>Hi Sunil,</div>
<div><br>
</div>
<div>It seems like your question would be more appropriate for the NVO3 mai=
ler than the SFC one (so I added NVO3).</div>
<div><br>
</div>
<div>Note that the ideas covered in draft-chen-nvo3-load-banlancing&nbsp;do=
 not seem to be part of the NVO3 charter, nor is it part of the NVO3 proble=
m statement, nor has it been discussed on the NVO3 mailer to my knowledge. =
&nbsp;I did take a look at the draft, and
 I am skeptical of its cost/benefit for implementation.</div>
<div><br>
</div>
<div>&nbsp;- Larry</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>Sunil Vallamkonda &lt;<a href=
=3D"mailto:sunilvk@f5.com">sunilvk@f5.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Wednesday, March 4, 2015 2:30=
 PM<br>
<span style=3D"font-weight:bold">To: </span>&quot;<a href=3D"mailto:sfc@iet=
f.org">sfc@ietf.org</a>&quot; &lt;<a href=3D"mailto:sfc@ietf.org">sfc@ietf.=
org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>[sfc] VxLAN-gpe vs nvo3<br=
>
</div>
<div><br>
</div>
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
<div lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Per <a href=3D"http://tools.ietf.org/html/draft-quin=
n-sfc-nsh-07">
http://tools.ietf.org/html/draft-quinn-sfc-nsh-07</a><o:p></o:p></p>
<p class=3D"MsoNormal">Section 11.2, VxLAN-gpe can be an encapsulation.<o:p=
></o:p></p>
<p class=3D"MsoNormal">However,&nbsp; how does the VxLAN-gpe header co-exis=
t with overlapping VxLAN header modification by nvo3:<o:p></o:p></p>
<p class=3D"MsoNormal"><a href=3D"https://datatracker.ietf.org/doc/draft-ch=
en-nvo3-load-banlancing/">https://datatracker.ietf.org/doc/draft-chen-nvo3-=
load-banlancing/</a><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Sunil<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_D11CCB3813A67Dkreegerciscocom_--


From nobody Wed Mar  4 17:01:13 2015
Return-Path: <therbert@google.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34D611A0013 for <sfc@ietfa.amsl.com>; Wed,  4 Mar 2015 16:51:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.389
X-Spam-Level: 
X-Spam-Status: No, score=-1.389 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 CIWnv-Xw1GrG for <sfc@ietfa.amsl.com>; Wed,  4 Mar 2015 16:51:30 -0800 (PST)
Received: from mail-ig0-x22b.google.com (mail-ig0-x22b.google.com [IPv6:2607:f8b0:4001:c05::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE4231A700B for <sfc@ietf.org>; Wed,  4 Mar 2015 16:51:29 -0800 (PST)
Received: by igkb16 with SMTP id b16so41782818igk.1 for <sfc@ietf.org>; Wed, 04 Mar 2015 16:51:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=pVYHexGBLMtMRSMkTcf/0UhhKJYdFea0xqn1++E9RAg=; b=C8WJpa3wOL1eyavKpMSxCwNGgBqbWC59cq5jLm7A23Zi4f4nuE60FjidtA7q+C5hmK adqi6wNf30pPb/xsZbhVdSoyb3gkNAinEgLeAPMtmr4AaiXvybXf0OsBlNZWNNPG16Ed If/iT/A9u6mnYMfmV9ja9ANYAW3bmShLG//b3r7UYlQLgzW1yByp4Ly/9hZZrnUS+W5I /AWIw24r6qhCDw4bWT1Of8IZ/EEFANAYU1c/K7M66WRkzCWlAbHZ8CKn1qnTAW6vGi6e xAptEUy3QZFLDwxJmkjspIkWmpvGvHoqmrYuFaXQ1VY7KTpV0ipubL7wVK73Ow/ZWX24 VGMw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=pVYHexGBLMtMRSMkTcf/0UhhKJYdFea0xqn1++E9RAg=; b=aB6Y72y3IPSY42bMgHlSCoi2OWeZy2NuKD/mo/pdX4C36xd+SFnptFDuMOftTMrAlG lEervCfA7UAzKsj6RzpIoj3iLMvBl0m4zHFsYlap1GytmOAD5MPiUL/BmNQ5mQ4omb0W dFyENW7rSlm1hrM0fxqT2Bf90elm/J7Zas87TpykwVbLNVBua4ll/bl5brTH8vHMXlQc HMdiQ13S+go+Gc3UzGckO/G4hv/Cs+NqFiQfB8CCiyo9D6yyo4sz+LWkpgboLKLHpJAm mLjWhqp8S6RqamLFQoFb99FoWHg0qVVk1QUJUmnLestSfDeTsWWFdzIWEcnhpp8lXvKE LD0w==
X-Gm-Message-State: ALoCoQlaEV/3Tkz/u/zNkzeG52mLuFjmkp9EiRlYThww2vBeHnXE/RT13CCNaGgcxTRUCf+beol4
MIME-Version: 1.0
X-Received: by 10.107.33.79 with SMTP id h76mr16237213ioh.36.1425516689317; Wed, 04 Mar 2015 16:51:29 -0800 (PST)
Received: by 10.64.29.144 with HTTP; Wed, 4 Mar 2015 16:51:29 -0800 (PST)
In-Reply-To: <D11CCB38.13A67D%kreeger@cisco.com>
References: <D11CCB38.13A67D%kreeger@cisco.com>
Date: Wed, 4 Mar 2015 16:51:29 -0800
Message-ID: <CA+mtBx9NXVO+YFe9s4XKmdUL0NfxKyorNA5m2jtFywmgvsBF-g@mail.gmail.com>
From: Tom Herbert <therbert@google.com>
To: "Larry Kreeger (kreeger)" <kreeger@cisco.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/9k_SkUe3kHR9H3lD__odu7uhyGc>
X-Mailman-Approved-At: Wed, 04 Mar 2015 17:01:11 -0800
Cc: "nvo3@ietf.org" <nvo3@ietf.org>, Sunil Vallamkonda <sunilvk@f5.com>, "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] [nvo3]  VxLAN-gpe vs nvo3
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 05 Mar 2015 00:51:31 -0000

https://www.cs.purdue.edu/homes/kompella/publications/infocom13.pdf

On Wed, Mar 4, 2015 at 2:55 PM, Larry Kreeger (kreeger)
<kreeger@cisco.com> wrote:
> Hi Sunil,
>
> It seems like your question would be more appropriate for the NVO3 mailer
> than the SFC one (so I added NVO3).
>
> Note that the ideas covered in draft-chen-nvo3-load-banlancing do not seem
> to be part of the NVO3 charter, nor is it part of the NVO3 problem
> statement, nor has it been discussed on the NVO3 mailer to my knowledge.  I
> did take a look at the draft, and I am skeptical of its cost/benefit for
> implementation.
>
Yes, it seems like a lot of additional protocol machinery. If we
didn't have to worry about OOO packets then simply modulating the UDP
source port will allow packets in the same flow to go over different
ECMP paths. In fact, we are seeing renewed interested in this for
packet spraying in DCs. UDP encap is compelling because of the ability
source route via the source port.

https://www.cs.purdue.edu/homes/kompella/publications/infocom13.pdf

Tom

>  - Larry
>
> From: Sunil Vallamkonda <sunilvk@f5.com>
> Date: Wednesday, March 4, 2015 2:30 PM
> To: "sfc@ietf.org" <sfc@ietf.org>
> Subject: [sfc] VxLAN-gpe vs nvo3
>
> Per http://tools.ietf.org/html/draft-quinn-sfc-nsh-07
>
> Section 11.2, VxLAN-gpe can be an encapsulation.
>
> However,  how does the VxLAN-gpe header co-exist with overlapping VxLAN
> header modification by nvo3:
>
> https://datatracker.ietf.org/doc/draft-chen-nvo3-load-banlancing/
>
>
>
> Sunil
>
>
>
>
>
>
>
>
> _______________________________________________
> nvo3 mailing list
> nvo3@ietf.org
> https://www.ietf.org/mailman/listinfo/nvo3
>


From nobody Wed Mar  4 17:58:51 2015
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E034A1A892C; Wed,  4 Mar 2015 17:58:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 vIVxVcI_IdVQ; Wed,  4 Mar 2015 17:58:47 -0800 (PST)
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 D35081AD06A; Wed,  4 Mar 2015 17:58:46 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BTH19146; Thu, 05 Mar 2015 01:58:45 +0000 (GMT)
Received: from NKGEML406-HUB.china.huawei.com (10.98.56.37) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 5 Mar 2015 01:58:44 +0000
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.115]) by nkgeml406-hub.china.huawei.com ([10.98.56.37]) with mapi id 14.03.0158.001; Thu, 5 Mar 2015 09:58:39 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Ron Parker <Ron_Parker@affirmednetworks.com>, "sfc@ietf.org" <sfc@ietf.org>, "<spring@ietf.org>" <spring@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
Thread-Topic: [sfc] New Version Notification for draft-xu-sfc-using-mpls-spring-02.txt
Thread-Index: AQHQVpoBw/osczeJOECv3v/Yp11/SZ0NHpTQ
Date: Thu, 5 Mar 2015 01:58:39 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0830FC8E@NKGEML512-MBS.china.huawei.com>
References: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0830F7C0@NKGEML512-MBS.china.huawei.com> <CDF2F015F4429F458815ED2A6C2B6B0B2E855978@MBX021-W3-CA-2.exch021.domain.local>
In-Reply-To: <CDF2F015F4429F458815ED2A6C2B6B0B2E855978@MBX021-W3-CA-2.exch021.domain.local>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.99.55]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/6nY9X-7hF8tLhHHicwBKGqCsxqM>
Subject: Re: [sfc] New Version Notification for draft-xu-sfc-using-mpls-spring-02.txt
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 05 Mar 2015 01:58:50 -0000

Hi Ron,

Thanks a lot for your insightful comments and suggestions. By the way, in t=
he case where there is no need to deliver metadata, does it mean the NSH ju=
st only needs to be contained the packets exchanged between SFFs and SFs? I=
n other words, the NSH is used as a way for the SFF to retrieve the label s=
tack which has been stripped by that SFF before.

Best regards,
Xiaohu=20

> -----Original Message-----
> From: Ron Parker [mailto:Ron_Parker@affirmednetworks.com]
> Sent: Thursday, March 05, 2015 12:41 AM
> To: Xuxiaohu; sfc@ietf.org; <spring@ietf.org>; mpls@ietf.org
> Subject: RE: [sfc] New Version Notification for
> draft-xu-sfc-using-mpls-spring-02.txt
>=20
> Xiaohu,
>=20
> I read your latest draft and I do see the elegance of describing a sequen=
ce of
> must-visit nodes as a stack of MPLS labels.   And I see that you've addre=
ssed
> the transport-independence requirement by stating that the MPLS frames co=
uld
> be carried within IP tunnels (i.e., MPLS in UDP, etc.).    But, I have a =
couple of
> issues that I suggest be addressed.
>=20
> First, the text is written as if the NSH header is optional and present o=
nly if
> metadata is required.    The SFC architecture is such that the NSH is
> mandatory.   I think this issue can be combined with the second issue tha=
t I'll
> raise below.
>=20
> Second, the notion is that the SFF's strip the label stack and then resto=
re the
> label stack.    And since the text states that even when NSH is present, =
the SFP
> ID is not used, the only remaining basis to do this is flow learning in t=
he SFF.
> While I think there are many reasons that may cause SFF's to utilize flow
> learning advantageously, it should not be a fundamental necessity to real=
ize an
> SFF, IMO.   But even if the SFF is a flow learner, this is still inadequa=
te since the
> SF may change the 5-tuple (e.g., NAT) or may launch internally generated =
flows
> (e.g., HTTP proxy).   Both cases could not be satisfied by flow learning.
>=20
> What I suggest, instead, is a tighter coupling between the NSH header and=
 the
> MPLS label stack.   That there be a 1:1 equivalency between {SFP ID, SFP =
hop
> index} and the label stack.   Thus, when the SFC-aware SF returns a packe=
t to
> the SFF, the {SFP ID, SFP hop index} contained in the NSH be used to push=
 the
> appropriate label stack onto the packet.    I believe this would bring th=
e
> approach into conformance with the SFC architectural requirements
> (mandatory NSH, transport independence) and would solve the problems with
> flow learning identified above.
>=20
>    Ron
>=20
>=20
>=20
> -----Original Message-----
> From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of Xuxiaohu
> Sent: Tuesday, March 3, 2015 11:10 PM
> To: Xuxiaohu; sfc@ietf.org; <spring@ietf.org>; mpls@ietf.org
> Subject: Re: [sfc] New Version Notification for
> draft-xu-sfc-using-mpls-spring-02.txt
>=20
> The rationales for leveraging the MPLS-SPRING mechanism to realize the se=
rvice
> path layer functionality of the service function chaining are as follows:
>=20
> 1) eliminate the SFC/SFP states on SFFs. This follows the same logic as
> MPLS-SPRING and BIER.
> 2) utilize the existing encapsulation (e.g., the MPLS-SPRING) to a maximu=
m
> extent. This follows the Transport Derived SFF concept as described in Se=
ction
> 4.3.1 of draft-ietf-sfc-architecture. Meanwhile, this is aligned with the=
 current
> SFC charter, e.g., "...The working group will consider using an existing
> encapsulation (with extensions as appropriate) if a suitable candidate is=
 found..."
> 3) seamlessly support the SFC in a multi-tenant environment (e.g., MPLS V=
PN).
> For example, the MPLS VPN packet (containing metadata) could be further
> imposed with a label stack which indicates an SFC or SFP associated with =
that
> packet. SFFs receiving the above packet would strip the whole label stack=
 and
> then send the payload of the MPLS packet (with metadata) to the correspon=
ding
> SFs which are tenant-aware and therefore easily could determine the tenan=
t
> profile according to the tenant info contained in the metadata (a.k.a., t=
he NSH).
>=20
> Best regards,
> Xiaohu
>=20
>=20
> > -----Original Message-----
> > From: Xuxiaohu
> > Sent: Wednesday, March 04, 2015 11:31 AM
> > To: sfc@ietf.org; '<spring@ietf.org>'; mpls@ietf.org
> > Subject: FW: New Version Notification for
> > draft-xu-sfc-using-mpls-spring-02.txt
> >
> > Hi all,
> >
> > This document describes how to leverage the MPLS-based source routing
> > (i.e.,
> > MPLS-SPRING) mechanism as developed by the SPRING WG to realize the
> > service path layer functionality of the service function chaining. In
> > addition, this document also describes how to carry metadata in an
> > MPLS packet by using the NSH as a metadata container.
> >
> > Any comments are suggestions are welcome.
> >
> > Best regards,
> > Xiaohu
> >
> > > -----Original Message-----
> > > From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> > > Sent: Wednesday, March 04, 2015 11:24 AM
> > > To: Lizhenbin; Luis M. Contreras; Xuxiaohu; Himanshu C. Shah;
> > > Xuxiaohu; Himanshu Shah; Luis M. Contreras; Lizhenbin
> > > Subject: New Version Notification for
> > > draft-xu-sfc-using-mpls-spring-02.txt
> > >
> > >
> > > A new version of I-D, draft-xu-sfc-using-mpls-spring-02.txt
> > > has been successfully submitted by Xiaohu Xu and posted to the IETF
> > repository.
> > >
> > > Name:		draft-xu-sfc-using-mpls-spring
> > > Revision:	02
> > > Title:		Service Function Chaining Using MPLS-SPRING
> > > Document date:	2015-03-03
> > > Group:		Individual Submission
> > > Pages:		8
> > > URL:
> > > http://www.ietf.org/internet-drafts/draft-xu-sfc-using-mpls-spring-02=
.
> > > txt
> > > Status:
> > > https://datatracker.ietf.org/doc/draft-xu-sfc-using-mpls-spring/
> > > Htmlized:
> http://tools.ietf.org/html/draft-xu-sfc-using-mpls-spring-02
> > > Diff:
> > > http://www.ietf.org/rfcdiff?url2=3Ddraft-xu-sfc-using-mpls-spring-02
> > >
> > > Abstract:
> > >    Source Packet Routing in Networking (SPRING) WG specifies a specia=
l
> > >    source routing mechanism.  Such source routing mechanism can be
> > >    leveraged to realize the service path layer functionality of the
> > >    service function chaining (i.e, steering traffic through a particu=
lar
> > >    service function path) by encoding the service function path or th=
e
> > >    service function chain information as the explicit path informatio=
n.
> > >    This document describes how to leverage the MPLS-based source
> routing
> > >    mechanism as developed by the SPRING WG to realize the service pat=
h
> > >    layer functionality of the service function chaining.
> > >
> > >
> > >
> > >
> > > Please note that it may take a couple of minutes from the time of
> > > submission until the htmlized version and diff are available at tools=
.ietf.org.
> > >
> > > The IETF Secretariat
>=20
> _______________________________________________
> sfc mailing list
> sfc@ietf.org
> https://www.ietf.org/mailman/listinfo/sfc


From nobody Wed Mar  4 18:20:16 2015
Return-Path: <Ron_Parker@affirmednetworks.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9ACB1A87B3; Wed,  4 Mar 2015 18:20:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 tbBlXyVWriOK; Wed,  4 Mar 2015 18:20:12 -0800 (PST)
Received: from hub021-ca-8.exch021.serverdata.net (hub021-ca-8.exch021.serverdata.net [64.78.56.73]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B1F981A8A66; Wed,  4 Mar 2015 18:20:12 -0800 (PST)
Received: from MBX021-W3-CA-2.exch021.domain.local ([10.254.4.78]) by HUB021-CA-8.exch021.domain.local ([10.254.4.112]) with mapi id 14.03.0224.002; Wed, 4 Mar 2015 18:20:12 -0800
From: Ron Parker <Ron_Parker@affirmednetworks.com>
To: Xuxiaohu <xuxiaohu@huawei.com>
Thread-Topic: [sfc] New Version Notification for draft-xu-sfc-using-mpls-spring-02.txt
Thread-Index: AQHQViqf+3y6NXpdeEGpQGeCsEhFG50LqPsAgAAGTiCAAMftMIABMl2A//9/6A8=
Date: Thu, 5 Mar 2015 02:20:11 +0000
Message-ID: <34ECE28B-F7AB-4FB9-9CE1-06289FB739B4@affirmednetworks.com>
References: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0830F7C0@NKGEML512-MBS.china.huawei.com> <CDF2F015F4429F458815ED2A6C2B6B0B2E855978@MBX021-W3-CA-2.exch021.domain.local>, <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0830FC8E@NKGEML512-MBS.china.huawei.com>
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0830FC8E@NKGEML512-MBS.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/5cLq2XNn-F_KZQIKVajjLzlvSQY>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "<spring@ietf.org>" <spring@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] New Version Notification for draft-xu-sfc-using-mpls-spring-02.txt
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 05 Mar 2015 02:20:16 -0000

I think it needs to be there between SFF's, too.  In the case where there i=
s no metadata, you could argue that the data in NSH and the label stack are=
 redundantly saying the same thing, but an optimization along these lines w=
ould not be justified, IMO.

   Ron


> On Mar 4, 2015, at 8:58 PM, Xuxiaohu <xuxiaohu@huawei.com> wrote:
>=20
> Hi Ron,
>=20
> Thanks a lot for your insightful comments and suggestions. By the way, in=
 the case where there is no need to deliver metadata, does it mean the NSH =
just only needs to be contained the packets exchanged between SFFs and SFs?=
 In other words, the NSH is used as a way for the SFF to retrieve the label=
 stack which has been stripped by that SFF before.
>=20
> Best regards,
> Xiaohu=20
>=20
>> -----Original Message-----
>> From: Ron Parker [mailto:Ron_Parker@affirmednetworks.com]
>> Sent: Thursday, March 05, 2015 12:41 AM
>> To: Xuxiaohu; sfc@ietf.org; <spring@ietf.org>; mpls@ietf.org
>> Subject: RE: [sfc] New Version Notification for
>> draft-xu-sfc-using-mpls-spring-02.txt
>>=20
>> Xiaohu,
>>=20
>> I read your latest draft and I do see the elegance of describing a seque=
nce of
>> must-visit nodes as a stack of MPLS labels.   And I see that you've addr=
essed
>> the transport-independence requirement by stating that the MPLS frames c=
ould
>> be carried within IP tunnels (i.e., MPLS in UDP, etc.).    But, I have a=
 couple of
>> issues that I suggest be addressed.
>>=20
>> First, the text is written as if the NSH header is optional and present =
only if
>> metadata is required.    The SFC architecture is such that the NSH is
>> mandatory.   I think this issue can be combined with the second issue th=
at I'll
>> raise below.
>>=20
>> Second, the notion is that the SFF's strip the label stack and then rest=
ore the
>> label stack.    And since the text states that even when NSH is present,=
 the SFP
>> ID is not used, the only remaining basis to do this is flow learning in =
the SFF.
>> While I think there are many reasons that may cause SFF's to utilize flo=
w
>> learning advantageously, it should not be a fundamental necessity to rea=
lize an
>> SFF, IMO.   But even if the SFF is a flow learner, this is still inadequ=
ate since the
>> SF may change the 5-tuple (e.g., NAT) or may launch internally generated=
 flows
>> (e.g., HTTP proxy).   Both cases could not be satisfied by flow learning=
.
>>=20
>> What I suggest, instead, is a tighter coupling between the NSH header an=
d the
>> MPLS label stack.   That there be a 1:1 equivalency between {SFP ID, SFP=
 hop
>> index} and the label stack.   Thus, when the SFC-aware SF returns a pack=
et to
>> the SFF, the {SFP ID, SFP hop index} contained in the NSH be used to pus=
h the
>> appropriate label stack onto the packet.    I believe this would bring t=
he
>> approach into conformance with the SFC architectural requirements
>> (mandatory NSH, transport independence) and would solve the problems wit=
h
>> flow learning identified above.
>>=20
>>   Ron
>>=20
>>=20
>>=20
>> -----Original Message-----
>> From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of Xuxiaohu
>> Sent: Tuesday, March 3, 2015 11:10 PM
>> To: Xuxiaohu; sfc@ietf.org; <spring@ietf.org>; mpls@ietf.org
>> Subject: Re: [sfc] New Version Notification for
>> draft-xu-sfc-using-mpls-spring-02.txt
>>=20
>> The rationales for leveraging the MPLS-SPRING mechanism to realize the s=
ervice
>> path layer functionality of the service function chaining are as follows=
:
>>=20
>> 1) eliminate the SFC/SFP states on SFFs. This follows the same logic as
>> MPLS-SPRING and BIER.
>> 2) utilize the existing encapsulation (e.g., the MPLS-SPRING) to a maxim=
um
>> extent. This follows the Transport Derived SFF concept as described in S=
ection
>> 4.3.1 of draft-ietf-sfc-architecture. Meanwhile, this is aligned with th=
e current
>> SFC charter, e.g., "...The working group will consider using an existing
>> encapsulation (with extensions as appropriate) if a suitable candidate i=
s found..."
>> 3) seamlessly support the SFC in a multi-tenant environment (e.g., MPLS =
VPN).
>> For example, the MPLS VPN packet (containing metadata) could be further
>> imposed with a label stack which indicates an SFC or SFP associated with=
 that
>> packet. SFFs receiving the above packet would strip the whole label stac=
k and
>> then send the payload of the MPLS packet (with metadata) to the correspo=
nding
>> SFs which are tenant-aware and therefore easily could determine the tena=
nt
>> profile according to the tenant info contained in the metadata (a.k.a., =
the NSH).
>>=20
>> Best regards,
>> Xiaohu
>>=20
>>=20
>>> -----Original Message-----
>>> From: Xuxiaohu
>>> Sent: Wednesday, March 04, 2015 11:31 AM
>>> To: sfc@ietf.org; '<spring@ietf.org>'; mpls@ietf.org
>>> Subject: FW: New Version Notification for
>>> draft-xu-sfc-using-mpls-spring-02.txt
>>>=20
>>> Hi all,
>>>=20
>>> This document describes how to leverage the MPLS-based source routing
>>> (i.e.,
>>> MPLS-SPRING) mechanism as developed by the SPRING WG to realize the
>>> service path layer functionality of the service function chaining. In
>>> addition, this document also describes how to carry metadata in an
>>> MPLS packet by using the NSH as a metadata container.
>>>=20
>>> Any comments are suggestions are welcome.
>>>=20
>>> Best regards,
>>> Xiaohu
>>>=20
>>>> -----Original Message-----
>>>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>>>> Sent: Wednesday, March 04, 2015 11:24 AM
>>>> To: Lizhenbin; Luis M. Contreras; Xuxiaohu; Himanshu C. Shah;
>>>> Xuxiaohu; Himanshu Shah; Luis M. Contreras; Lizhenbin
>>>> Subject: New Version Notification for
>>>> draft-xu-sfc-using-mpls-spring-02.txt
>>>>=20
>>>>=20
>>>> A new version of I-D, draft-xu-sfc-using-mpls-spring-02.txt
>>>> has been successfully submitted by Xiaohu Xu and posted to the IETF
>>> repository.
>>>>=20
>>>> Name:        draft-xu-sfc-using-mpls-spring
>>>> Revision:    02
>>>> Title:        Service Function Chaining Using MPLS-SPRING
>>>> Document date:    2015-03-03
>>>> Group:        Individual Submission
>>>> Pages:        8
>>>> URL:
>>>> http://www.ietf.org/internet-drafts/draft-xu-sfc-using-mpls-spring-02.
>>>> txt
>>>> Status:
>>>> https://datatracker.ietf.org/doc/draft-xu-sfc-using-mpls-spring/
>>>> Htmlized:
>> http://tools.ietf.org/html/draft-xu-sfc-using-mpls-spring-02
>>>> Diff:
>>>> http://www.ietf.org/rfcdiff?url2=3Ddraft-xu-sfc-using-mpls-spring-02
>>>>=20
>>>> Abstract:
>>>>   Source Packet Routing in Networking (SPRING) WG specifies a special
>>>>   source routing mechanism.  Such source routing mechanism can be
>>>>   leveraged to realize the service path layer functionality of the
>>>>   service function chaining (i.e, steering traffic through a particula=
r
>>>>   service function path) by encoding the service function path or the
>>>>   service function chain information as the explicit path information.
>>>>   This document describes how to leverage the MPLS-based source
>> routing
>>>>   mechanism as developed by the SPRING WG to realize the service path
>>>>   layer functionality of the service function chaining.
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> Please note that it may take a couple of minutes from the time of
>>>> submission until the htmlized version and diff are available at tools.=
ietf.org.
>>>>=20
>>>> The IETF Secretariat
>>=20
>> _______________________________________________
>> sfc mailing list
>> sfc@ietf.org
>> https://www.ietf.org/mailman/listinfo/sfc


From nobody Wed Mar  4 22:46:51 2015
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF5E51B29C8 for <sfc@ietfa.amsl.com>; Wed,  4 Mar 2015 22:46:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 h7Iz-p1XnfQc for <sfc@ietfa.amsl.com>; Wed,  4 Mar 2015 22:46:48 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias245.francetelecom.com [80.12.204.245]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E7CA1A1AD9 for <sfc@ietf.org>; Wed,  4 Mar 2015 22:46:47 -0800 (PST)
Received: from omfeda06.si.francetelecom.fr (unknown [xx.xx.xx.199]) by omfeda13.si.francetelecom.fr (ESMTP service) with ESMTP id 8EA42190748; Thu,  5 Mar 2015 07:46:45 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.30]) by omfeda06.si.francetelecom.fr (ESMTP service) with ESMTP id 6C942C809B; Thu,  5 Mar 2015 07:46:45 +0100 (CET)
Received: from OPEXCLILM23.corporate.adroot.infra.ftgroup ([169.254.2.181]) by OPEXCLILH02.corporate.adroot.infra.ftgroup ([10.114.31.30]) with mapi id 14.03.0224.002; Thu, 5 Mar 2015 07:46:43 +0100
From: <mohamed.boucadair@orange.com>
To: "Paul Quinn (paulq)" <paulq@cisco.com>
Thread-Topic: [sfc] draft-quinn-sfc-nsh: version number
Thread-Index: AQHQVpZZlsbbenTwMkmQOaMIFOQDuZ0NcFhQ
Date: Thu, 5 Mar 2015 06:46:43 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933004922B46@OPEXCLILM23.corporate.adroot.infra.ftgroup>
References: <01f9e1a4e6514854a26556e4c6a3e36e@SEAEXCHMBX05.olympus.F5Net.com> <787AE7BB302AE849A7480A190F8B933004919B76@OPEXCLILM23.corporate.adroot.infra.ftgroup> <CDF2F015F4429F458815ED2A6C2B6B0B2E85379B@MBX021-W3-CA-2.exch021.domain.local> <787AE7BB302AE849A7480A190F8B93300491A1AF@OPEXCLILM23.corporate.adroot.infra.ftgroup> <CDF2F015F4429F458815ED2A6C2B6B0B2E8558D0@MBX021-W3-CA-2.exch021.domain.local> <787AE7BB302AE849A7480A190F8B93300491A1F7@OPEXCLILM23.corporate.adroot.infra.ftgroup> <08AFD2FB-AC81-479A-9098-0FFEDDBF0A58@cisco.com>
In-Reply-To: <08AFD2FB-AC81-479A-9098-0FFEDDBF0A58@cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.1]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B933004922B46OPEXCLILM23corp_"
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.3.4.224522
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/wE6OnoO1V4e5qnLS8_LRiHW4fug>
Cc: Sunil Vallamkonda <sunilvk@f5.com>, "sfc@ietf.org" <sfc@ietf.org>, Ron Parker <Ron_Parker@affirmednetworks.com>
Subject: Re: [sfc] draft-quinn-sfc-nsh: version number
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 05 Mar 2015 06:46:51 -0000

--_000_787AE7BB302AE849A7480A190F8B933004922B46OPEXCLILM23corp_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Paul,

Glad to see that we are sharing the same objective to design simple things,=
 but the design should not cause another yet set of failure cases (which is=
 the case of the current spec: the non-support of the MD type will be a cau=
se of failure too).

I already provided a long message with my thoughts (http://www.ietf.org/mai=
l-archive/web/sfc/current/msg03175.html).

I can propose text, but we need to agree first. I'm still questioning the n=
eed to have the version field in addition to other fields such as MD type.

I hope to see more feedback from the WG participants other than the authors=
 of the draft so that I can adjust the proposed text.

Cheers,
Med

De : Paul Quinn (paulq) [mailto:paulq@cisco.com]
Envoy=E9 : mercredi 4 mars 2015 17:15
=C0 : BOUCADAIR Mohamed IMT/OLN
Cc : Ron Parker; Sunil Vallamkonda; sfc@ietf.org
Objet : Re: [sfc] draft-quinn-sfc-nsh: version number


On Mar 4, 2015, at 11:09 AM, mohamed.boucadair@orange.com<mailto:mohamed.bo=
ucadair@orange.com> wrote:

Re-,

That would be a good start, but still not sufficient IMHO.

If no notification is sent back (which can be the case with the MAY languag=
e), the failure will be experienced till an action is done by the domain op=
erator. This is not desirable.

Having a more strong language for sending back the response (that needs to =
include at least the received packet with the unsupported version) will hav=
e the effect to resend the packet with an adequate version (if multiple ver=
sions are supported). The exact behavior when a version mismatch error is r=
eceived should be explicated in the document IMO.

Perhaps the best way forward: can you please suggest some text that we can =
all review?  I'm inclined to keep things simple (i.e. simple error message =
of sorts) but since you've given this a lot of thought, I'd love to see you=
r suggestions.



--_000_787AE7BB302AE849A7480A190F8B933004922B46OPEXCLILM23corp_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Cambria;
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"Segoe UI";
	panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
h1
	{mso-style-priority:9;
	mso-style-link:"Titre 1 Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	font-weight:normal;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Texte brut Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"Pr=E9format=E9 HTML Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Texte de bulles Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.Titre1Car
	{mso-style-name:"Titre 1 Car";
	mso-style-priority:9;
	mso-style-link:"Titre 1";
	font-family:"Cambria","serif";
	color:#365F91;
	font-weight:bold;}
span.PrformatHTMLCar
	{mso-style-name:"Pr=E9format=E9 HTML Car";
	mso-style-priority:99;
	mso-style-link:"Pr=E9format=E9 HTML";
	font-family:Consolas;}
span.TextebrutCar
	{mso-style-name:"Texte brut Car";
	mso-style-priority:99;
	mso-style-link:"Texte brut";
	font-family:"Courier New";
	color:black;
	mso-fareast-language:EN-US;}
span.TextedebullesCar
	{mso-style-name:"Texte de bulles Car";
	mso-style-priority:99;
	mso-style-link:"Texte de bulles";
	font-family:"Tahoma","sans-serif";}
span.Heading1Char
	{mso-style-name:"Heading 1 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 1";
	font-family:"Times New Roman","serif";
	font-weight:bold;}
p.Heading1, li.Heading1, div.Heading1
	{mso-style-name:"Heading 1";
	mso-style-link:"Heading 1 Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
p.HTMLPreformatted, li.HTMLPreformatted, div.HTMLPreformatted
	{mso-style-name:"HTML Preformatted";
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
p.PlainText, li.PlainText, div.PlainText
	{mso-style-name:"Plain Text";
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Segoe UI","sans-serif";}
p.BalloonText, li.BalloonText, div.BalloonText
	{mso-style-name:"Balloon Text";
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle32
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle33
	{mso-style-type:personal;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;}
span.EmailStyle34
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle35
	{mso-style-type:personal;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;}
span.EmailStyle36
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle37
	{mso-style-type:personal;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;}
span.EmailStyle38
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"FR" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Hi Paul,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Glad to see that we are sharing=
 the same objective to design simple things, but the design should not caus=
e another yet set of failure cases (which is the
 case of the current spec: the non-support of the MD type will be a cause o=
f failure too).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">I already provided a long messa=
ge with my thoughts (<a href=3D"http://www.ietf.org/mail-archive/web/sfc/cu=
rrent/msg03175.html">http://www.ietf.org/mail-archive/web/sfc/current/msg03=
175.html</a>).
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">I can propose text, but we need=
 to agree first. I&#8217;m still questioning the need to have the version f=
ield in addition to other fields such as MD type.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">I hope to see more feedback fro=
m the WG participants other than the authors of the draft so that I can adj=
ust the proposed text.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Cheers,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Med<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">De&nbsp;:</span></b><span style=3D"fo=
nt-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Paul=
 Quinn (paulq) [mailto:paulq@cisco.com]
<br>
<b>Envoy=E9&nbsp;:</b> mercredi 4 mars 2015 17:15<br>
<b>=C0&nbsp;:</b> BOUCADAIR Mohamed IMT/OLN<br>
<b>Cc&nbsp;:</b> Ron Parker; Sunil Vallamkonda; sfc@ietf.org<br>
<b>Objet&nbsp;:</b> Re: [sfc] draft-quinn-sfc-nsh: version number<o:p></o:p=
></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">On Mar 4, 2015, at 11:09 AM, <a href=3D"mailto:moham=
ed.boucadair@orange.com">
mohamed.boucadair@orange.com</a> wrote:<o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Re-,</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;">That would be a good start, but still not s=
ufficient IMHO.</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;">If no notification is sent back (which can =
be the case with the MAY language), the failure will be experienced till an=
 action is done by the domain operator. This is
 not desirable. </span><o:p></o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;">Having a more strong language for sending b=
ack the response (that needs to include at least the received packet with t=
he unsupported version) will have the effect to
 resend the packet with an adequate version (if multiple versions are suppo=
rted). The exact behavior when a version mismatch error is received should =
be explicated in the document IMO.
</span><o:p></o:p></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;">Perhaps the best way forward: can yo=
u please suggest some text that we can all review? &nbsp;I&#8217;m inclined=
 to keep things simple (i.e. simple error message of sorts) but since
 you&#8217;ve given this a lot of thought, I&#8217;d love to see your sugge=
stions.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_787AE7BB302AE849A7480A190F8B933004922B46OPEXCLILM23corp_--


From nobody Wed Mar  4 23:49:08 2015
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 868D71B2A22 for <sfc@ietfa.amsl.com>; Wed,  4 Mar 2015 23:49:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.598
X-Spam-Level: 
X-Spam-Status: No, score=-1.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=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 EKg99L6vspb6 for <sfc@ietfa.amsl.com>; Wed,  4 Mar 2015 23:49:04 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3442B1B2A25 for <sfc@ietf.org>; Wed,  4 Mar 2015 23:49:04 -0800 (PST)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id 3FB433240A4; Thu,  5 Mar 2015 08:49:02 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.5]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 1A16A23808F; Thu,  5 Mar 2015 08:49:02 +0100 (CET)
Received: from OPEXCLILM23.corporate.adroot.infra.ftgroup ([169.254.2.181]) by OPEXCLILH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0224.002; Thu, 5 Mar 2015 08:49:01 +0100
From: <mohamed.boucadair@orange.com>
To: "Haeffner, Walter, Vodafone DE" <walter.haeffner@vodafone.com>, "Paul Quinn (paulq)" <paulq@cisco.com>
Thread-Topic: [sfc] draft-quinn-sfc-nsh: relatniship with the use cases drafts
Thread-Index: AdBRDaI7xfMTZEmzRd6IIps3ZiTmogEICK4AAAwm2PAAbmjuYA==
Date: Thu, 5 Mar 2015 07:49:00 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933004923BBE@OPEXCLILM23.corporate.adroot.infra.ftgroup>
References: <787AE7BB302AE849A7480A190F8B9330049140FD@OPEXCLILM23.corporate.adroot.infra.ftgroup> <CA29E3DA-324E-4FA3-AC0B-4148E46999D5@cisco.com> <C8C844F84E550E43865561FAE10471854C5F0C8B@VOEXM20W.internal.vodafone.com>
In-Reply-To: <C8C844F84E550E43865561FAE10471854C5F0C8B@VOEXM20W.internal.vodafone.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.1]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B933004923BBEOPEXCLILM23corp_"
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.3.5.62721
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/ppVHKd7UE-DS2C7RSOdhD2OSUSE>
Cc: "sfc@ietf.org" <sfc@ietf.org>, "stbryant@cisco.com" <stbryant@cisco.com>
Subject: Re: [sfc] draft-quinn-sfc-nsh: relatniship with the use cases drafts
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 05 Mar 2015 07:49:06 -0000

--_000_787AE7BB302AE849A7480A190F8B933004923BBEOPEXCLILM23corp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgV2FsdGVyLCBQYXVsLA0KDQoNCldoYXQgSSdtIGV4cGVjdGluZyBpcyB0byBkZXJpdmUgcmVx
dWlyZW1lbnRzIGZyb20gdGhlIHVzZSBjYXNlcywgZXhhY3RseSBpbiBsaW5lIHdpdGggd2hhdCB3
YXMgbWVudGlvbmVkIGJ5IFN0ZXdhcnQgQnJ5YW50IGhlcmU6IGh0dHA6Ly93d3cuaWV0Zi5vcmcv
bWFpbC1hcmNoaXZlL3dlYi9zZmMvY3VycmVudC9tc2cwMTc1MS5odG1sLCBlc3BlY2lhbGx5IHRo
aXMgcGFydDoNCg0KDQoNCiJJIGFzc3VtZSB0aGF0IHRoZSBwbGFuIGlzIHRvIHdyaXRlIGRvd24g
dGhlIHVzZSBjYXNlcywgdGhlbiB0byBkaXN0aWxsIGZyb20NCg0KdGhlIHVzZSBjYXNlcyB0aGUg
cmVxdWlyZW1lbnRzLCB0byB3cml0ZSB0aGUgYXJjaGl0ZWN0dXJlIChvciBmcmFtZXdvcmspDQoN
CmJhc2VkIG9uIHRoZSB0aGUgcmVxdWlyZW1lbnRzIGFuZCB0aGUgdG8gd3JpdGUgdGhlIHNvbHV0
aW9ucyB0byBzYXRpc2Z5IHRoZQ0KDQpyZXF1aXJlbWVudHMgY29uc2lzdGVudCB3aXRoIHRoZSBh
cmNoaXRlY3R1cmUuIg0KDQoNCg0KVGhlIHVzZSBjYXNlIEktRHMgc2hvdWxkIG5vdCBjaXRlIHRo
ZSBoZWFkZXIgc3BlY2lmaWNhdGlvbiBkcmFmdCBidXQgdGhlIG90aGVyIHdheSBhcm91bmQ6IHRo
ZSBuc2ggc2hvdWxkIGF0IGxlYXN0IGluY2x1ZGUgcG9pbnRlcnMgdG8gdGhlIHVzZSBjYXNlIEkt
RHMgcHJvZHVjZWQgYnkgdGhlIFdHLCBhbmQgcHJlZmVyYWJseSBtb3RpdmF0ZSBzb21lIG9mIGl0
cyBkZXNpZ24gY2hvaWNlcyBieSBleHBsaWNpdCByZXF1aXJlbWVudHMgZGVyaXZlZCBmcm9tIHRo
b3NlIHVzZSBjYXNlcyBJLURzLg0KDQoNCg0KQ2hlZXJzLA0KDQpNZWQNCg0KRGUgOiBIYWVmZm5l
ciwgV2FsdGVyLCBWb2RhZm9uZSBERSBbbWFpbHRvOndhbHRlci5oYWVmZm5lckB2b2RhZm9uZS5j
b21dDQpFbnZvecOpIDogbHVuZGkgMiBtYXJzIDIwMTUgMTc6MTUNCsOAIDogUGF1bCBRdWlubiAo
cGF1bHEpOyBCT1VDQURBSVIgTW9oYW1lZCBJTVQvT0xODQpDYyA6IHNmY0BpZXRmLm9yZw0KT2Jq
ZXQgOiBBVzogW3NmY10gZHJhZnQtcXVpbm4tc2ZjLW5zaDogcmVsYXRuaXNoaXAgd2l0aCB0aGUg
dXNlIGNhc2VzIGRyYWZ0cw0KDQpIaSBQYXVsLCBNZWQsDQoNCkluIHRoZSBtb2JpbGUgdXNlIGNh
c2UgZHJhZnQgd2UgbWVudGlvbmVkIHVzYWdlIGFuZCBpbXBhY3Qgb2YgbWV0YWRhdGEgb24gU0ZD
LiBXZSBhbHNvIG1lbnRpb25lZCB0aGF0IGEgTlNIIG1heSBiZSBhcHByb3ByaWF0ZS4gQmVjYXVz
ZSBhdCB0aW1lIG9mIHdyaXRpbmcgTlNIIHdhcyBub3QgKGFuZCBpcyBub3QgYnkgdG9kYXkpIGlt
cGxlbWVudGVkIGluIFNGcywgd2UgY291bGRu4oCZdCBnaXZlIGFuIGV4cGxpY2l0IGV4YW1wbGUu
IEFuZCB3ZSB3ZXJlIGFza2VkIG5vdCB0byBpbmNsdWRlIHJlcXVpcmVtZW50cyBpbiB0aGUgZHJh
ZnQuDQoNCldhbHRlcg0KVm9uOiBzZmMgW21haWx0bzpzZmMtYm91bmNlc0BpZXRmLm9yZ10gSW0g
QXVmdHJhZyB2b24gUGF1bCBRdWlubiAocGF1bHEpDQpHZXNlbmRldDogTW9udGFnLCAyLiBNw6Ry
eiAyMDE1IDE2OjE0DQpBbjogbW9oYW1lZC5ib3VjYWRhaXJAb3JhbmdlLmNvbTxtYWlsdG86bW9o
YW1lZC5ib3VjYWRhaXJAb3JhbmdlLmNvbT4NCkNjOiBzZmNAaWV0Zi5vcmc8bWFpbHRvOnNmY0Bp
ZXRmLm9yZz4NCkJldHJlZmY6IFJlOiBbc2ZjXSBkcmFmdC1xdWlubi1zZmMtbnNoOiByZWxhdG5p
c2hpcCB3aXRoIHRoZSB1c2UgY2FzZXMgZHJhZnRzDQoNCkhpIE1lZCwNCg0KDQpBcmUgeW91IHN1
Z2dlc3RpbmcgdGhhdCB0aGUgdXNlIGNhc2VzIGJlIGluY2x1ZGVkIGFzIHJlZmVyZW5jZXMsIG9y
IGV4cGxpY2l0IHJlZmVyZW5jZWQ/ICBQZXJoYXBzIGEgbG9naWNhbCBwYXRoIGZvcndhcmQsIGlm
IE5TSCBpcyBhZG9wdGVkLCB0aGF0IHBlcmhhcHMgdGhlIHVzZSBjYXNlcyBjYW4gYmUgdXBkYXRl
ZCB0byByZWZsZWN0IHRoZSDigJxTRkMgZW5jYXDigJ0uDQoNClBhdWwNCg0KDQpPbiBGZWIgMjUs
IDIwMTUsIGF0IDEwOjEzIEFNLCBtb2hhbWVkLmJvdWNhZGFpckBvcmFuZ2UuY29tPG1haWx0bzpt
b2hhbWVkLmJvdWNhZGFpckBvcmFuZ2UuY29tPiB3cm90ZToNCg0KUmUtLA0KDQpJdCBpcyB1bmZv
cnR1bmF0ZSB0aGUgY3VycmVudCBOU0ggc3BlY2lmaWNhdGlvbiBkb2VzIG5vdCByZWx5IG9uIHRo
ZSBTRkMgdXNlIGNhc2VzIGFzIGRvY3VtZW50ZWQgYnkgdGhlIFdHLg0KDQpEb2VzIHRoaXMgbWVh
biB0aGF0IHRob3NlIGFyZSB1c2VsZXNzPyBUaGF0IG5vIChjb21tb24pIHJlcXVpcmVtZW50cyBj
YW4gYmUgZGVyaXZlZCBmcm9tIHRob3NlIEktRHMgdG8gZ3VpZGUgdGhlIHNwZWNpZmljYXRpb24g
b2YgdGhlIE5TSCBoZWFkZXI/DQoNCkNoZWVycywNCk1lZA0KX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX18NCnNmYyBtYWlsaW5nIGxpc3QNCnNmY0BpZXRmLm9y
ZzxtYWlsdG86c2ZjQGlldGYub3JnPg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby9zZmMNCg0K

--_000_787AE7BB302AE849A7480A190F8B933004923BBEOPEXCLILM23corp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQov
KiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1z
b05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNp
emU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7fQ0KYTpsaW5r
LCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1
ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBl
cmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0K
CXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcC5Nc29QbGFpblRleHQsIGxpLk1zb1BsYWlu
VGV4dCwgZGl2Lk1zb1BsYWluVGV4dA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0
eWxlLWxpbms6IlRleHRlIGJydXQgQ2FyIjsNCgltYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206
LjAwMDFwdDsNCglmb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7
DQoJY29sb3I6YmxhY2s7DQoJbXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVM7fQ0KcC5Nc29BY2V0
YXRlLCBsaS5Nc29BY2V0YXRlLCBkaXYuTXNvQWNldGF0ZQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6
OTk7DQoJbXNvLXN0eWxlLWxpbms6IlRleHRlIGRlIGJ1bGxlcyBDYXIiOw0KCW1hcmdpbjowY207
DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZTo4LjBwdDsNCglmb250LWZhbWls
eToiVGFob21hIiwic2Fucy1zZXJpZiI7fQ0KcC5Nc29MaXN0UGFyYWdyYXBoLCBsaS5Nc29MaXN0
UGFyYWdyYXBoLCBkaXYuTXNvTGlzdFBhcmFncmFwaA0KCXttc28tc3R5bGUtcHJpb3JpdHk6MzQ7
DQoJbWFyZ2luLXRvcDowY207DQoJbWFyZ2luLXJpZ2h0OjBjbTsNCgltYXJnaW4tYm90dG9tOjEy
LjBwdDsNCgltYXJnaW4tbGVmdDozNi4wcHQ7DQoJbXNvLWFkZC1zcGFjZTphdXRvOw0KCWZvbnQt
c2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQpwLk1zb0xpc3RQYXJh
Z3JhcGhDeFNwRmlyc3QsIGxpLk1zb0xpc3RQYXJhZ3JhcGhDeFNwRmlyc3QsIGRpdi5Nc29MaXN0
UGFyYWdyYXBoQ3hTcEZpcnN0DQoJe21zby1zdHlsZS1wcmlvcml0eTozNDsNCgltc28tc3R5bGUt
dHlwZTpleHBvcnQtb25seTsNCgltYXJnaW4tdG9wOjBjbTsNCgltYXJnaW4tcmlnaHQ6MGNtOw0K
CW1hcmdpbi1ib3R0b206MGNtOw0KCW1hcmdpbi1sZWZ0OjM2LjBwdDsNCgltYXJnaW4tYm90dG9t
Oi4wMDAxcHQ7DQoJbXNvLWFkZC1zcGFjZTphdXRvOw0KCWZvbnQtc2l6ZToxMi4wcHQ7DQoJZm9u
dC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQpwLk1zb0xpc3RQYXJhZ3JhcGhDeFNwTWlkZGxlLCBs
aS5Nc29MaXN0UGFyYWdyYXBoQ3hTcE1pZGRsZSwgZGl2Lk1zb0xpc3RQYXJhZ3JhcGhDeFNwTWlk
ZGxlDQoJe21zby1zdHlsZS1wcmlvcml0eTozNDsNCgltc28tc3R5bGUtdHlwZTpleHBvcnQtb25s
eTsNCgltYXJnaW4tdG9wOjBjbTsNCgltYXJnaW4tcmlnaHQ6MGNtOw0KCW1hcmdpbi1ib3R0b206
MGNtOw0KCW1hcmdpbi1sZWZ0OjM2LjBwdDsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJbXNv
LWFkZC1zcGFjZTphdXRvOw0KCWZvbnQtc2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IkNvdXJp
ZXIgTmV3Ijt9DQpwLk1zb0xpc3RQYXJhZ3JhcGhDeFNwTGFzdCwgbGkuTXNvTGlzdFBhcmFncmFw
aEN4U3BMYXN0LCBkaXYuTXNvTGlzdFBhcmFncmFwaEN4U3BMYXN0DQoJe21zby1zdHlsZS1wcmlv
cml0eTozNDsNCgltc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCgltYXJnaW4tdG9wOjBjbTsN
CgltYXJnaW4tcmlnaHQ6MGNtOw0KCW1hcmdpbi1ib3R0b206MTIuMHB0Ow0KCW1hcmdpbi1sZWZ0
OjM2LjBwdDsNCgltc28tYWRkLXNwYWNlOmF1dG87DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250
LWZhbWlseToiQ291cmllciBOZXciO30NCnNwYW4uRW1haWxTdHlsZTE4DQoJe21zby1zdHlsZS10
eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7DQoJY29sb3I6d2luZG93
dGV4dDsNCglmb250LXdlaWdodDpub3JtYWw7DQoJZm9udC1zdHlsZTpub3JtYWw7fQ0Kc3Bhbi5F
bWFpbFN0eWxlMTkNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJZm9udC1mYW1pbHk6IkNh
bGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjojMUY0OTdEO30NCnNwYW4uVGV4dGVkZWJ1bGxl
c0Nhcg0KCXttc28tc3R5bGUtbmFtZToiVGV4dGUgZGUgYnVsbGVzIENhciI7DQoJbXNvLXN0eWxl
LXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJUZXh0ZSBkZSBidWxsZXMiOw0KCWZvbnQt
ZmFtaWx5OiJUYWhvbWEiLCJzYW5zLXNlcmlmIjt9DQpzcGFuLkVtYWlsU3R5bGUyMg0KCXttc28t
c3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToiQ291cmllciBOZXciOw0K
CWNvbG9yOmJsYWNrOw0KCWZvbnQtd2VpZ2h0Om5vcm1hbDsNCglmb250LXN0eWxlOm5vcm1hbDt9
DQpzcGFuLlRleHRlYnJ1dENhcg0KCXttc28tc3R5bGUtbmFtZToiVGV4dGUgYnJ1dCBDYXIiOw0K
CW1zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiVGV4dGUgYnJ1dCI7DQoJ
Zm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3IjsNCgljb2xvcjpibGFjazsNCgltc28tZmFyZWFzdC1s
YW5ndWFnZTpFTi1VUzt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQt
b25seTsNCglmb250LXNpemU6MTAuMHB0O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjYx
Mi4wcHQgNzkyLjBwdDsNCgltYXJnaW46NzAuODVwdCA3MC44NXB0IDcwLjg1cHQgNzAuODVwdDt9
DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEt
LVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlk
bWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+
DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0
YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxi
b2R5IGxhbmc9IkZSIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9Ildv
cmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+
SGkgV2FsdGVyLCBQYXVsLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJp
ZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+V2hhdCBJJ20gZXhwZWN0
aW5nIGlzIHRvIGRlcml2ZSByZXF1aXJlbWVudHMgZnJvbSB0aGUgdXNlIGNhc2VzLCBleGFjdGx5
IGluIGxpbmUgd2l0aCB3aGF0IHdhcyBtZW50aW9uZWQgYnkgU3Rld2FydCBCcnlhbnQgaGVyZToN
Cjwvc3Bhbj48YSBocmVmPSJodHRwOi8vd3d3LmlldGYub3JnL21haWwtYXJjaGl2ZS93ZWIvc2Zj
L2N1cnJlbnQvbXNnMDE3NTEuaHRtbCI+PHNwYW4gbGFuZz0iRU4tVVMiPmh0dHA6Ly93d3cuaWV0
Zi5vcmcvbWFpbC1hcmNoaXZlL3dlYi9zZmMvY3VycmVudC9tc2cwMTc1MS5odG1sPC9zcGFuPjwv
YT48c3BhbiBsYW5nPSJFTi1VUyI+LCBlc3BlY2lhbGx5IHRoaXMgcGFydDo8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+PG86
cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4g
bGFuZz0iRU4tVVMiPiZxdW90O0kgYXNzdW1lIHRoYXQgdGhlIHBsYW4gaXMgdG8gd3JpdGUgZG93
biB0aGUgdXNlIGNhc2VzLCB0aGVuIHRvIGRpc3RpbGwgZnJvbTxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj50aGUgdXNlIGNh
c2VzIHRoZSByZXF1aXJlbWVudHMsIHRvIHdyaXRlIHRoZSBhcmNoaXRlY3R1cmUgKG9yIGZyYW1l
d29yayk8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3Bh
biBsYW5nPSJFTi1VUyI+YmFzZWQgb24gdGhlIHRoZSByZXF1aXJlbWVudHMgYW5kIHRoZSB0byB3
cml0ZSB0aGUgc29sdXRpb25zIHRvIHNhdGlzZnkgdGhlPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPnJlcXVpcmVtZW50cyBj
b25zaXN0ZW50IHdpdGggdGhlIGFyY2hpdGVjdHVyZS4mcXVvdDs8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJz
cDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0i
RU4tVVMiPlRoZSB1c2UgY2FzZSBJLURzIHNob3VsZCBub3QgY2l0ZSB0aGUgaGVhZGVyIHNwZWNp
ZmljYXRpb24gZHJhZnQgYnV0IHRoZSBvdGhlciB3YXkgYXJvdW5kOiB0aGUgbnNoIHNob3VsZCBh
dCBsZWFzdCBpbmNsdWRlIHBvaW50ZXJzIHRvIHRoZSB1c2UgY2FzZSBJLURzIHByb2R1Y2VkIGJ5
IHRoZSBXRywgYW5kIHByZWZlcmFibHkgbW90aXZhdGUgc29tZSBvZiBpdHMgZGVzaWduDQogY2hv
aWNlcyBieSBleHBsaWNpdCByZXF1aXJlbWVudHMgZGVyaXZlZCBmcm9tIHRob3NlIHVzZSBjYXNl
cyBJLURzLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxz
cGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+Q2hlZXJzLDxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj5NZWQ8L3Nw
YW4+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250
LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8
L286cD48L3NwYW4+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29s
aWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDQuMHB0Ij4NCjxkaXY+DQo8ZGl2IHN0
eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzoz
LjBwdCAwY20gMGNtIDBjbSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fu
cy1zZXJpZiZxdW90OyI+RGUmbmJzcDs6PC9zcGFuPjwvYj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZx
dW90OyI+IEhhZWZmbmVyLCBXYWx0ZXIsIFZvZGFmb25lIERFIFttYWlsdG86d2FsdGVyLmhhZWZm
bmVyQHZvZGFmb25lLmNvbV0NCjxicj4NCjxiPkVudm95w6kmbmJzcDs6PC9iPiBsdW5kaSAyIG1h
cnMgMjAxNSAxNzoxNTxicj4NCjxiPsOAJm5ic3A7OjwvYj4gUGF1bCBRdWlubiAocGF1bHEpOyBC
T1VDQURBSVIgTW9oYW1lZCBJTVQvT0xOPGJyPg0KPGI+Q2MmbmJzcDs6PC9iPiBzZmNAaWV0Zi5v
cmc8YnI+DQo8Yj5PYmpldCZuYnNwOzo8L2I+IEFXOiBbc2ZjXSBkcmFmdC1xdWlubi1zZmMtbnNo
OiByZWxhdG5pc2hpcCB3aXRoIHRoZSB1c2UgY2FzZXMgZHJhZnRzPG86cD48L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJj
b2xvcjojMUY0OTdEIj5IaSBQYXVsLCBNZWQsPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xvcjojMUY0OTdEIj48
bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBs
YW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPkluIHRoZSBtb2JpbGUgdXNlIGNhc2Ug
ZHJhZnQgd2UgbWVudGlvbmVkIHVzYWdlIGFuZCBpbXBhY3Qgb2YgbWV0YWRhdGEgb24gU0ZDLiBX
ZSBhbHNvIG1lbnRpb25lZCB0aGF0IGEgTlNIIG1heSBiZSBhcHByb3ByaWF0ZS4gQmVjYXVzZSBh
dCB0aW1lIG9mIHdyaXRpbmcgTlNIIHdhcyBub3QgKGFuZCBpcyBub3QgYnkgdG9kYXkpIGltcGxl
bWVudGVkDQogaW4gU0ZzLCB3ZSBjb3VsZG7igJl0IGdpdmUgYW4gZXhwbGljaXQgZXhhbXBsZS4g
QW5kIHdlIHdlcmUgYXNrZWQgbm90IHRvIGluY2x1ZGUgcmVxdWlyZW1lbnRzIGluIHRoZSBkcmFm
dC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5n
PSJFTi1VUyIgc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iY29sb3I6
IzFGNDk3RCI+V2FsdGVyPG86cD48L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxkaXYgc3R5bGU9
ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0
IDBjbSAwY20gMGNtIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIGxhbmc9IkRFIiBz
dHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1
b3Q7c2Fucy1zZXJpZiZxdW90OyI+Vm9uOjwvc3Bhbj48L2I+PHNwYW4gbGFuZz0iREUiIHN0eWxl
PSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtz
YW5zLXNlcmlmJnF1b3Q7Ij4gc2ZjIFs8YSBocmVmPSJtYWlsdG86c2ZjLWJvdW5jZXNAaWV0Zi5v
cmciPm1haWx0bzpzZmMtYm91bmNlc0BpZXRmLm9yZzwvYT5dDQo8Yj5JbSBBdWZ0cmFnIHZvbiA8
L2I+UGF1bCBRdWlubiAocGF1bHEpPGJyPg0KPGI+R2VzZW5kZXQ6PC9iPiBNb250YWcsIDIuIDwv
c3Bhbj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPk3DpHJ6IDIwMTUg
MTY6MTQ8YnI+DQo8Yj5Bbjo8L2I+IDxhIGhyZWY9Im1haWx0bzptb2hhbWVkLmJvdWNhZGFpckBv
cmFuZ2UuY29tIj5tb2hhbWVkLmJvdTxzcGFuIGxhbmc9IkRFIj5jYWRhaXJAb3JhbmdlLmNvbTwv
c3Bhbj48L2E+PC9zcGFuPjxzcGFuIGxhbmc9IkRFIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtm
b250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PGJy
Pg0KPGI+Q2M6PC9iPiA8YSBocmVmPSJtYWlsdG86c2ZjQGlldGYub3JnIj5zZmNAaWV0Zi5vcmc8
L2E+PGJyPg0KPGI+QmV0cmVmZjo8L2I+IFJlOiBbc2ZjXSBkcmFmdC1xdWlubi1zZmMtbnNoOiBy
ZWxhdG5pc2hpcCB3aXRoIHRoZSB1c2UgY2FzZXMgZHJhZnRzPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVT
Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gbGFuZz0iRU4tVVMiPkhpIE1lZCw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4m
bmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj5BcmUgeW91
IHN1Z2dlc3RpbmcgdGhhdCB0aGUgdXNlIGNhc2VzIGJlIGluY2x1ZGVkIGFzIHJlZmVyZW5jZXMs
IG9yIGV4cGxpY2l0IHJlZmVyZW5jZWQ/ICZuYnNwO1BlcmhhcHMgYSBsb2dpY2FsIHBhdGggZm9y
d2FyZCwgaWYgTlNIIGlzIGFkb3B0ZWQsIHRoYXQgcGVyaGFwcyB0aGUgdXNlIGNhc2VzIGNhbiBi
ZSB1cGRhdGVkIHRvIHJlZmxlY3QgdGhlIOKAnFNGQyBlbmNhcOKAnS48bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJF
Ti1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPlBhdWw8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1V
UyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRp
dj4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4w
cHQiPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj5PbiBG
ZWIgMjUsIDIwMTUsIGF0IDEwOjEzIEFNLCA8YSBocmVmPSJtYWlsdG86bW9oYW1lZC5ib3VjYWRh
aXJAb3JhbmdlLmNvbSI+DQptb2hhbWVkLmJvdWNhZGFpckBvcmFuZ2UuY29tPC9hPiB3cm90ZTo8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7Ij5SZS0sPC9zcGFuPjxvOnA+PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDsiPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9u
dC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyI+SXQgaXMg
dW5mb3J0dW5hdGUgdGhlIGN1cnJlbnQgTlNIIHNwZWNpZmljYXRpb24gZG9lcyBub3QgcmVseSBv
biB0aGUgU0ZDIHVzZSBjYXNlcyBhcyBkb2N1bWVudGVkIGJ5IHRoZSBXRy4NCjwvc3Bhbj48bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHls
ZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyI+
Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
bGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nv
dXJpZXIgTmV3JnF1b3Q7Ij5Eb2VzIHRoaXMgbWVhbiB0aGF0IHRob3NlIGFyZSB1c2VsZXNzPyBU
aGF0IG5vIChjb21tb24pIHJlcXVpcmVtZW50cyBjYW4gYmUgZGVyaXZlZCBmcm9tIHRob3NlIEkt
RHMgdG8gZ3VpZGUgdGhlIHNwZWNpZmljYXRpb24gb2YgdGhlIE5TSCBoZWFkZXI/DQo8L3NwYW4+
PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIg
c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVv
dDsiPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVv
dDtDb3VyaWVyIE5ldyZxdW90OyI+Q2hlZXJzLDwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBw
dDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyI+TWVkDQo8L3NwYW4+PG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVT
IiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9t
YW4mcXVvdDssJnF1b3Q7c2VyaWYmcXVvdDsiPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fPGJyPg0Kc2ZjIG1haWxpbmcgbGlzdDxicj4NCjxhIGhyZWY9Im1h
aWx0bzpzZmNAaWV0Zi5vcmciPnNmY0BpZXRmLm9yZzwvYT48YnI+DQo8YSBocmVmPSJodHRwczov
L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NmYyI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcv
bWFpbG1hbi9saXN0aW5mby9zZmM8L2E+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8
L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcg
Um9tYW4mcXVvdDssJnF1b3Q7c2VyaWYmcXVvdDsiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_787AE7BB302AE849A7480A190F8B933004923BBEOPEXCLILM23corp_--


From nobody Thu Mar  5 00:59:19 2015
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C442D1B2AE6 for <sfc@ietfa.amsl.com>; Thu,  5 Mar 2015 00:59:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 sJKgdyGtSKRR for <sfc@ietfa.amsl.com>; Thu,  5 Mar 2015 00:59:11 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7EED31B2AE3 for <sfc@ietf.org>; Thu,  5 Mar 2015 00:59:11 -0800 (PST)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id 8C6463247E1; Thu,  5 Mar 2015 09:59:09 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.16]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 67666238153; Thu,  5 Mar 2015 09:59:09 +0100 (CET)
Received: from OPEXCLILM23.corporate.adroot.infra.ftgroup ([169.254.2.181]) by OPEXCLILH05.corporate.adroot.infra.ftgroup ([10.114.31.16]) with mapi id 14.03.0224.002; Thu, 5 Mar 2015 09:59:09 +0100
From: <mohamed.boucadair@orange.com>
To: "Surendra Kumar (smkumar)" <smkumar@cisco.com>
Thread-Topic: [sfc] FW: New Version Notification for draft-kumar-sfc-offloads-00.txt
Thread-Index: AQHQVqoghYWONTwLLESkPa19GEYCJJ0MiM+AgAEGBuA=
Date: Thu, 5 Mar 2015 08:59:08 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933004924D0F@OPEXCLILM23.corporate.adroot.infra.ftgroup>
References: <20150304183622.20056.47379.idtracker@ietfa.amsl.com> <D11C90EC.18D0C%smkumar@cisco.com>
In-Reply-To: <D11C90EC.18D0C%smkumar@cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.1]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.12.16.112421
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/PYoVdDZIfDAMbLO-Cj7oH_aV2nU>
Cc: "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] FW: New Version Notification for draft-kumar-sfc-offloads-00.txt
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 05 Mar 2015 08:59:13 -0000

Hi Surendra,

Thank you for sharing this I-D that touches on classification complications=
 in an SFC architecture. Interesting!

I have some quick comments about the draft:=20

* It seems that you are assuming that SF and SFF are always separate nodes.=
 SF and SFF are functional elements that may be co-located or not. Whether =
those are collocated in the same physical node or not is deployment-specifi=
c.=20

* What would be the behavior when a node hosting several SFs, serviced by t=
he same SFF, receives the offload indication?

* In addition to the potential classification issue you mentioned in your d=
raft, there are other issues that are worth to be considered, e.g.,
   o  Rationalize the management of classification rules.
   o  Help assessing the impact of removing or modifying a
      classification rule.
   o  Check the coherency of instantiated classification rules.
   o  Help aggregating rules: this allows to optimize the classification
      rule table and therefor accelerate packet/flow processing (mainly
      reduce lookup delays).
   o  Adjust classification rules when rules are based on volatile
      identifiers (e.g., IP address).
   o  Maintain an global overview of instantiated rules in involved
      Network Elements.
   o  Rapidly restore state during failure events.
   o  Network Elements can retrieve their table after failure events
      whiteout requiring permanent storage capacity.

Whether classification-related issues should be discussed as a package or i=
ndividually can be useful to discuss. IMHO, classification burden and SFC O=
AM are the KEY challenging parts of an SFC architecture.=20

* It would be fair to cite this I-D for the control part discussion: https:=
//datatracker.ietf.org/doc/draft-ww-sfc-control-plane/=20

Thank you.

Cheers,
Med

> -----Message d'origine-----
> De=A0: sfc [mailto:sfc-bounces@ietf.org] De la part de Surendra Kumar
> (smkumar)
> Envoy=E9=A0: mercredi 4 mars 2015 19:49
> =C0=A0: sfc@ietf.org
> Objet=A0: [sfc] FW: New Version Notification for draft-kumar-sfc-offloads=
-
> 00.txt
>=20
> Hi all:
>=20
> We posted a new draft, but with old content. After the presentation on
> simple offloads + Optimization at HNL, we received a lot of feedback.
>=20
> In including it, we have split the SFP Path Optimization draft into two:
> 1) this one which limits itself to the offload between SF and SFF
> 2) the original sfp optimization draft, which focuses on optimization of
> the SFP among the SFFs
>=20
> #2 will be updated to reflect the split
>=20
> Thanks and we appreciate your comments/questions,
> Surendra.
>=20
> On 3/4/15, 10:36 AM, "internet-drafts@ietf.org" <internet-drafts@ietf.org=
>
> wrote:
>=20
> >
> >A new version of I-D, draft-kumar-sfc-offloads-00.txt
> >has been successfully submitted by Surendra Kumar and posted to the
> >IETF repository.
> >
> >Name:		draft-kumar-sfc-offloads
> >Revision:	00
> >Title:		Service Function Simple Offloads
> >Document date:	2015-03-04
> >Group:		Individual Submission
> >Pages:		15
> >URL:
> >http://www.ietf.org/internet-drafts/draft-kumar-sfc-offloads-00.txt
> >Status:         https://datatracker.ietf.org/doc/draft-kumar-sfc-
> offloads/
> >Htmlized:       http://tools.ietf.org/html/draft-kumar-sfc-offloads-00
> >
> >
> >Abstract:
> >   Service Function Chaining (SFC) enables services to be delivered by
> >   selective traffic steering through an ordered set of service
> >   functions.  Once classified into an SFC, the traffic for a given flow
> >   is steered through all the service functions of the SFC for the life
> >   of the traffic flow even though this is often not necessary.
> >   Steering traffic to service functions only while required and not
> >   otherwise, leads to shorter SFC forwarding paths with improved
> >   latencies, reduced resource consumption and better user experience.
> >
> >   This document describes the rationale, techniques and necessary
> >   protocol extensions to achieve such optimization, with focus on one
> >   such technique termed "simple offloads".
> >
> >
> >
> >
> >
> >
> >Please note that it may take a couple of minutes from the time of
> >submission
> >until the htmlized version and diff are available at tools.ietf.org.
> >
> >The IETF Secretariat
> >
>=20
> _______________________________________________
> sfc mailing list
> sfc@ietf.org
> https://www.ietf.org/mailman/listinfo/sfc


From nobody Thu Mar  5 02:31:28 2015
Return-Path: <walter.haeffner@vodafone.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31CA91A897E for <sfc@ietfa.amsl.com>; Thu,  5 Mar 2015 02:31:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham
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 2pEbz8sNpdkn for <sfc@ietfa.amsl.com>; Thu,  5 Mar 2015 02:31:25 -0800 (PST)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.162]) by ietfa.amsl.com (Postfix) with ESMTP id C4BA31A895B for <sfc@ietf.org>; Thu,  5 Mar 2015 02:31:24 -0800 (PST)
Received: from [195.245.230.51] by server-2.bemta-3.messagelabs.com id AA/90-02991-B7038F45; Thu, 05 Mar 2015 10:31:23 +0000
X-Env-Sender: walter.haeffner@vodafone.com
X-Msg-Ref: server-13.tower-33.messagelabs.com!1425551482!10260630!1
X-Originating-IP: [195.232.224.77]
X-StarScan-Received: 
X-StarScan-Version: 6.13.4; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 17088 invoked from network); 5 Mar 2015 10:31:22 -0000
Received: from mailout08.vodafone.com (HELO mailout08.vodafone.com) (195.232.224.77) by server-13.tower-33.messagelabs.com with SMTP; 5 Mar 2015 10:31:22 -0000
Received: from mailint08.vodafone.com (localhost [127.0.0.1]) by mailout08.vodafone.com (Postfix) with ESMTP id 587AD22065C for <sfc@ietf.org>; Thu,  5 Mar 2015 11:31:22 +0100 (CET)
Received: from VOEXC06W.internal.vodafone.com (voexc06w.dc-ratingen.de [145.230.101.26]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailint08.vodafone.com (Postfix) with ESMTPS id 3B4AC2205C0; Thu,  5 Mar 2015 11:31:22 +0100 (CET)
Received: from AVOEXC03W.internal.vodafone.com (145.230.15.132) by VOEXC06W.internal.vodafone.com (145.230.101.26) with Microsoft SMTP Server (TLS) id 14.3.224.2; Thu, 5 Mar 2015 11:31:21 +0100
Received: from VOEXM20W.internal.vodafone.com ([169.254.4.55]) by AVOEXC03W.internal.vodafone.com ([145.230.15.132]) with mapi id 14.03.0224.002; Thu, 5 Mar 2015 11:31:20 +0100
From: "Haeffner, Walter, Vodafone DE" <walter.haeffner@vodafone.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "Paul Quinn (paulq)" <paulq@cisco.com>, Jim Guichard <jguichar@cisco.com>, "Thomas Narten" <narten@us.ibm.com>, Jeff Napper <jenapper@cisco.com>, "Martin Stiemerling" <martin.stiemerling@h-da.de>, "Surendra Kumar (smkumar)" <smkumar@cisco.com>
Thread-Topic: [sfc] draft-quinn-sfc-nsh: relatniship with the use cases drafts
Thread-Index: AdBRDaI7xfMTZEmzRd6IIps3ZiTmogEICK4AAAwm2PAAbmjuYAAF4EVZ
Date: Thu, 5 Mar 2015 10:31:20 +0000
Message-ID: <C8C844F84E550E43865561FAE10471854C5F3EBB@VOEXM20W.internal.vodafone.com>
References: <787AE7BB302AE849A7480A190F8B9330049140FD@OPEXCLILM23.corporate.adroot.infra.ftgroup> <CA29E3DA-324E-4FA3-AC0B-4148E46999D5@cisco.com> <C8C844F84E550E43865561FAE10471854C5F0C8B@VOEXM20W.internal.vodafone.com>, <787AE7BB302AE849A7480A190F8B933004923BBE@OPEXCLILM23.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B933004923BBE@OPEXCLILM23.corporate.adroot.infra.ftgroup>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_C8C844F84E550E43865561FAE10471854C5F3EBBVOEXM20Winterna_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/aUYMhka8MIxWmfC6jP3XFr6xIcs>
Cc: "sfc@ietf.org" <sfc@ietf.org>, "stbryant@cisco.com" <stbryant@cisco.com>
Subject: Re: [sfc] draft-quinn-sfc-nsh: relatniship with the use cases drafts
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 05 Mar 2015 10:31:28 -0000

--_000_C8C844F84E550E43865561FAE10471854C5F3EBBVOEXM20Winterna_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi,

As said, originally we had requirements derived from the individual use cas=
es included in the mobility use case draft itself.

1) We could add these again in the use case draft. But this requires agreem=
ent by the WG (Chairs). Personally I prefer this approach.

Jim, Tom, what is your position?

2) We could check how derived requirements and functional design recommenda=
tions would fit into the requirements draft. But this may be more time cons=
uming.

Wrt references to use cases I am fully in line with Med.

Cheers,
Walter


Gesendet mit meinem HTC

----- Reply message -----
Von: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
An: "Haeffner, Walter, Vodafone DE" <walter.haeffner@vodafone.com>, "Paul Q=
uinn (paulq)" <paulq@cisco.com>
Cc: "sfc@ietf.org" <sfc@ietf.org>, "stbryant@cisco.com" <stbryant@cisco.com=
>
Betreff: [sfc] draft-quinn-sfc-nsh: relatniship with the use cases drafts
Datum: Do., M=E4r 5, 2015 08:49

Hi Walter, Paul,


What I'm expecting is to derive requirements from the use cases, exactly in=
 line with what was mentioned by Stewart Bryant here: http://www.ietf.org/m=
ail-archive/web/sfc/current/msg01751.html, especially this part:



"I assume that the plan is to write down the use cases, then to distill fro=
m

the use cases the requirements, to write the architecture (or framework)

based on the the requirements and the to write the solutions to satisfy the

requirements consistent with the architecture."



The use case I-Ds should not cite the header specification draft but the ot=
her way around: the nsh should at least include pointers to the use case I-=
Ds produced by the WG, and preferably motivate some of its design choices b=
y explicit requirements derived from those use cases I-Ds.



Cheers,

Med

De : Haeffner, Walter, Vodafone DE [mailto:walter.haeffner@vodafone.com]
Envoy=E9 : lundi 2 mars 2015 17:15
=C0 : Paul Quinn (paulq); BOUCADAIR Mohamed IMT/OLN
Cc : sfc@ietf.org
Objet : AW: [sfc] draft-quinn-sfc-nsh: relatniship with the use cases draft=
s

Hi Paul, Med,

In the mobile use case draft we mentioned usage and impact of metadata on S=
FC. We also mentioned that a NSH may be appropriate. Because at time of wri=
ting NSH was not (and is not by today) implemented in SFs, we couldn=92t gi=
ve an explicit example. And we were asked not to include requirements in th=
e draft.

Walter
Von: sfc [mailto:sfc-bounces@ietf.org] Im Auftrag von Paul Quinn (paulq)
Gesendet: Montag, 2. M=E4rz 2015 16:14
An: mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>
Cc: sfc@ietf.org<mailto:sfc@ietf.org>
Betreff: Re: [sfc] draft-quinn-sfc-nsh: relatniship with the use cases draf=
ts

Hi Med,


Are you suggesting that the use cases be included as references, or explici=
t referenced?  Perhaps a logical path forward, if NSH is adopted, that perh=
aps the use cases can be updated to reflect the =93SFC encap=94.

Paul


On Feb 25, 2015, at 10:13 AM, mohamed.boucadair@orange.com<mailto:mohamed.b=
oucadair@orange.com> wrote:

Re-,

It is unfortunate the current NSH specification does not rely on the SFC us=
e cases as documented by the WG.

Does this mean that those are useless? That no (common) requirements can be=
 derived from those I-Ds to guide the specification of the NSH header?

Cheers,
Med
_______________________________________________
sfc mailing list
sfc@ietf.org<mailto:sfc@ietf.org>
https://www.ietf.org/mailman/listinfo/sfc


--_000_C8C844F84E550E43865561FAE10471854C5F3EBBVOEXM20Winterna_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<style>
<!--
@font-face
	{font-family:Calibri}
@font-face
	{font-family:Tahoma}
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif"}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif"}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{margin-top:0cm;
	margin-right:0cm;
	margin-bottom:12.0pt;
	margin-left:36.0pt;
	font-size:12.0pt;
	font-family:"Courier New"}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParag=
raphCxSpFirst
	{margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Courier New"}
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListPar=
agraphCxSpMiddle
	{margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Courier New"}
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagra=
phCxSpLast
	{margin-top:0cm;
	margin-right:0cm;
	margin-bottom:12.0pt;
	margin-left:36.0pt;
	font-size:12.0pt;
	font-family:"Courier New"}
span.EmailStyle18
	{font-family:"Courier New";
	color:windowtext;
	font-weight:normal;
	font-style:normal}
span.EmailStyle19
	{font-family:"Calibri","sans-serif";
	color:#1F497D}
span.TextedebullesCar
	{font-family:"Tahoma","sans-serif"}
span.EmailStyle22
	{font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal}
span.TextebrutCar
	{font-family:"Courier New";
	color:black}
.MsoChpDefault
	{font-size:10.0pt}
@page WordSection1
	{margin:70.85pt 70.85pt 70.85pt 70.85pt}
div.WordSection1
	{}
-->
</style>
</head>
<body lang=3D"FR" link=3D"blue" vlink=3D"purple">
<style>
<!--
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif"}
-->
</style>
<div style=3D"font-size:12pt; font-family:Calibri,sans-serif">
<div>Hi,</div>
<div>&nbsp;</div>
<div>As said, originally we had requirements derived from the individual us=
e cases included in the mobility use case draft itself.</div>
<div><br>
</div>
<div>1) We could add these again in the use case draft. But this requires a=
greement by&nbsp;the WG (Chairs). Personally I prefer this approach.</div>
<div><br>
</div>
<div>Jim, Tom, what is your position?</div>
<div><br>
</div>
<div>2) We could check how derived requirements and functional design recom=
mendations would fit into the requirements draft. But this may be more time=
 consuming.</div>
<div><br>
</div>
<div>Wrt references to use cases I am fully in line with Med.</div>
<div><br>
</div>
<div>Cheers,</div>
<div>Walter</div>
<div><br>
</div>
<div><br>
</div>
<div>Gesendet mit meinem HTC</div>
<br>
<div id=3D"htc_header">----- Reply message -----<br>
Von: &quot;mohamed.boucadair@orange.com&quot; &lt;mohamed.boucadair@orange.=
com&gt;<br>
An: &quot;Haeffner, Walter, Vodafone DE&quot; &lt;walter.haeffner@vodafone.=
com&gt;, &quot;Paul Quinn (paulq)&quot; &lt;paulq@cisco.com&gt;<br>
Cc: &quot;sfc@ietf.org&quot; &lt;sfc@ietf.org&gt;, &quot;stbryant@cisco.com=
&quot; &lt;stbryant@cisco.com&gt;<br>
Betreff: [sfc] draft-quinn-sfc-nsh: relatniship with the use cases drafts<b=
r>
Datum: Do., M=E4r 5, 2015 08:49</div>
</div>
<br>
<div>
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
ourier New&quot;; color:black">Hi Walter, Paul,</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
ourier New&quot;; color:black">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">What I'm expecting is to der=
ive requirements from the use cases, exactly in line with what was mentione=
d by Stewart Bryant here:
</span><a href=3D"http://www.ietf.org/mail-archive/web/sfc/current/msg01751=
.html"><span lang=3D"EN-US">http://www.ietf.org/mail-archive/web/sfc/curren=
t/msg01751.html</span></a><span lang=3D"EN-US">, especially this part:</spa=
n></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&quot;I assume that the plan=
 is to write down the use cases, then to distill from</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">the use cases the requiremen=
ts, to write the architecture (or framework)</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">based on the the requirement=
s and the to write the solutions to satisfy the</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">requirements consistent with=
 the architecture.&quot;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">The use case I-Ds should not=
 cite the header specification draft but the other way around: the nsh shou=
ld at least include pointers to the use case I-Ds produced by the WG, and p=
referably motivate some of its design
 choices by explicit requirements derived from those use cases I-Ds.</span>=
</p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Cheers,</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Med</span><span lang=3D"EN-U=
S"></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Courier New&quot;; color:black">&nbsp;</span></p>
<div style=3D"border:none; border-left:solid blue 1.5pt; padding:0cm 0cm 0c=
m 4.0pt">
<div>
<div style=3D"border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0c=
m 0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt; font-family:&quo=
t;Tahoma&quot;,&quot;sans-serif&quot;">De&nbsp;:</span></b><span style=3D"f=
ont-size:10.0pt; font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Ha=
effner, Walter, Vodafone DE [mailto:walter.haeffner@vodafone.com]
<br>
<b>Envoy=E9&nbsp;:</b> lundi 2 mars 2015 17:15<br>
<b>=C0&nbsp;:</b> Paul Quinn (paulq); BOUCADAIR Mohamed IMT/OLN<br>
<b>Cc&nbsp;:</b> sfc@ietf.org<br>
<b>Objet&nbsp;:</b> AW: [sfc] draft-quinn-sfc-nsh: relatniship with the use=
 cases drafts</span></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Hi Paul=
, Med,</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">In the =
mobile use case draft we mentioned usage and impact of metadata on SFC. We =
also mentioned that a NSH may be appropriate. Because at time of writing NS=
H was not (and is not by today) implemented
 in SFs, we couldn=92t give an explicit example. And we were asked not to i=
nclude requirements in the draft.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Walter<=
/span></p>
<div>
<div style=3D"border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0c=
m 0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"DE" style=3D"font-size:10.0pt; font=
-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">Von:</span></b><span lan=
g=3D"DE" style=3D"font-size:10.0pt; font-family:&quot;Tahoma&quot;,&quot;sa=
ns-serif&quot;"> sfc [<a href=3D"mailto:sfc-bounces@ietf.org">mailto:sfc-bo=
unces@ietf.org</a>]
<b>Im Auftrag von </b>Paul Quinn (paulq)<br>
<b>Gesendet:</b> Montag, 2. </span><span lang=3D"EN-US" style=3D"font-size:=
10.0pt; font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">M=E4rz 2015 =
16:14<br>
<b>An:</b> <a href=3D"mailto:mohamed.boucadair@orange.com">mohamed.bou<span=
 lang=3D"DE">cadair@orange.com</span></a></span><span lang=3D"DE" style=3D"=
font-size:10.0pt; font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"><b=
r>
<b>Cc:</b> <a href=3D"mailto:sfc@ietf.org">sfc@ietf.org</a><br>
<b>Betreff:</b> Re: [sfc] draft-quinn-sfc-nsh: relatniship with the use cas=
es drafts</span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hi Med,</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Are you suggesting that the use=
 cases be included as references, or explicit referenced? &nbsp;Perhaps a l=
ogical path forward, if NSH is adopted, that perhaps the use cases can be u=
pdated to reflect the =93SFC encap=94.</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Paul</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<div>
<blockquote style=3D"margin-top:5.0pt; margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">On Feb 25, 2015, at 10:13 AM, <=
a href=3D"mailto:mohamed.boucadair@orange.com">
mohamed.boucadair@orange.com</a> wrote:</span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
ourier New&quot;">Re-,</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
ourier New&quot;">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Courier New&quot;">It is unfortunate the current NSH specific=
ation does not rely on the SFC use cases as documented by the WG.
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Courier New&quot;">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Courier New&quot;">Does this mean that those are useless? Tha=
t no (common) requirements can be derived from those I-Ds to guide the spec=
ification of the NSH header?
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Courier New&quot;">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Courier New&quot;">Cheers,</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Courier New&quot;">Med
</span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:12.0pt; font=
-family:&quot;Times New Roman&quot;,&quot;serif&quot;">____________________=
___________________________<br>
sfc mailing list<br>
<a href=3D"mailto:sfc@ietf.org">sfc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/sfc">https://www.ietf.org/=
mailman/listinfo/sfc</a></span></p>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:12.0pt; font=
-family:&quot;Times New Roman&quot;,&quot;serif&quot;">&nbsp;</span></p>
</div>
</div>
</div>
</body>
</html>

--_000_C8C844F84E550E43865561FAE10471854C5F3EBBVOEXM20Winterna_--


From nobody Thu Mar  5 02:56:14 2015
Return-Path: <jmh@joelhalpern.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 319C61B2BD5 for <sfc@ietfa.amsl.com>; Thu,  5 Mar 2015 02:56:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 3JeuKTPxnr7f for <sfc@ietfa.amsl.com>; Thu,  5 Mar 2015 02:56:09 -0800 (PST)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A9441B2BCA for <sfc@ietf.org>; Thu,  5 Mar 2015 02:56:09 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 9C1811BC0897; Thu,  5 Mar 2015 02:56:08 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from Joels-MacBook-Pro.local (unknown [192.165.183.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id EE1AC1BC0833; Thu,  5 Mar 2015 02:55:47 -0800 (PST)
Message-ID: <54F83617.2080105@joelhalpern.com>
Date: Thu, 05 Mar 2015 05:55:19 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: mohamed.boucadair@orange.com,  "Surendra Kumar (smkumar)" <smkumar@cisco.com>
References: <20150304183622.20056.47379.idtracker@ietfa.amsl.com> <D11C90EC.18D0C%smkumar@cisco.com> <787AE7BB302AE849A7480A190F8B933004924D0F@OPEXCLILM23.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B933004924D0F@OPEXCLILM23.corporate.adroot.infra.ftgroup>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/jo9ZpRd8ejU_rJFr9MH0El7G3Q0>
Cc: "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] FW: New Version Notification for draft-kumar-sfc-offloads-00.txt
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 05 Mar 2015 10:56:12 -0000

I am not sure I understand your concern about co-location.
The mechanisms proposed has to, and as far as I can tell does, work 
whether the SFF is colocated with the SF or in a separate node.  Is the 
confusion caused by some of the example discussion?

As for the case where there are multiple SF handled by the same SFF, 
that is the assumed case.  The SFF can tell which SF is requesting the 
bypass, and apply it only to that SF.

Yours,
Joel

On 3/5/15 3:59 AM, mohamed.boucadair@orange.com wrote:
> Hi Surendra,
>
> Thank you for sharing this I-D that touches on classification complications in an SFC architecture. Interesting!
>
> I have some quick comments about the draft:
>
> * It seems that you are assuming that SF and SFF are always separate nodes. SF and SFF are functional elements that may be co-located or not. Whether those are collocated in the same physical node or not is deployment-specific.
>
> * What would be the behavior when a node hosting several SFs, serviced by the same SFF, receives the offload indication?
>
> * In addition to the potential classification issue you mentioned in your draft, there are other issues that are worth to be considered, e.g.,
>     o  Rationalize the management of classification rules.
>     o  Help assessing the impact of removing or modifying a
>        classification rule.
>     o  Check the coherency of instantiated classification rules.
>     o  Help aggregating rules: this allows to optimize the classification
>        rule table and therefor accelerate packet/flow processing (mainly
>        reduce lookup delays).
>     o  Adjust classification rules when rules are based on volatile
>        identifiers (e.g., IP address).
>     o  Maintain an global overview of instantiated rules in involved
>        Network Elements.
>     o  Rapidly restore state during failure events.
>     o  Network Elements can retrieve their table after failure events
>        whiteout requiring permanent storage capacity.
>
> Whether classification-related issues should be discussed as a package or individually can be useful to discuss. IMHO, classification burden and SFC OAM are the KEY challenging parts of an SFC architecture.
>
> * It would be fair to cite this I-D for the control part discussion: https://datatracker.ietf.org/doc/draft-ww-sfc-control-plane/
>
> Thank you.
>
> Cheers,
> Med
>
>> -----Message d'origine-----
>> De : sfc [mailto:sfc-bounces@ietf.org] De la part de Surendra Kumar
>> (smkumar)
>> Envoyé : mercredi 4 mars 2015 19:49
>> À : sfc@ietf.org
>> Objet : [sfc] FW: New Version Notification for draft-kumar-sfc-offloads-
>> 00.txt
>>
>> Hi all:
>>
>> We posted a new draft, but with old content. After the presentation on
>> simple offloads + Optimization at HNL, we received a lot of feedback.
>>
>> In including it, we have split the SFP Path Optimization draft into two:
>> 1) this one which limits itself to the offload between SF and SFF
>> 2) the original sfp optimization draft, which focuses on optimization of
>> the SFP among the SFFs
>>
>> #2 will be updated to reflect the split
>>
>> Thanks and we appreciate your comments/questions,
>> Surendra.
>>
>> On 3/4/15, 10:36 AM, "internet-drafts@ietf.org" <internet-drafts@ietf.org>
>> wrote:
>>
>>>
>>> A new version of I-D, draft-kumar-sfc-offloads-00.txt
>>> has been successfully submitted by Surendra Kumar and posted to the
>>> IETF repository.
>>>
>>> Name:		draft-kumar-sfc-offloads
>>> Revision:	00
>>> Title:		Service Function Simple Offloads
>>> Document date:	2015-03-04
>>> Group:		Individual Submission
>>> Pages:		15
>>> URL:
>>> http://www.ietf.org/internet-drafts/draft-kumar-sfc-offloads-00.txt
>>> Status:         https://datatracker.ietf.org/doc/draft-kumar-sfc-
>> offloads/
>>> Htmlized:       http://tools.ietf.org/html/draft-kumar-sfc-offloads-00
>>>
>>>
>>> Abstract:
>>>    Service Function Chaining (SFC) enables services to be delivered by
>>>    selective traffic steering through an ordered set of service
>>>    functions.  Once classified into an SFC, the traffic for a given flow
>>>    is steered through all the service functions of the SFC for the life
>>>    of the traffic flow even though this is often not necessary.
>>>    Steering traffic to service functions only while required and not
>>>    otherwise, leads to shorter SFC forwarding paths with improved
>>>    latencies, reduced resource consumption and better user experience.
>>>
>>>    This document describes the rationale, techniques and necessary
>>>    protocol extensions to achieve such optimization, with focus on one
>>>    such technique termed "simple offloads".
>>>
>>>
>>>
>>>
>>>
>>>
>>> Please note that it may take a couple of minutes from the time of
>>> submission
>>> until the htmlized version and diff are available at tools.ietf.org.
>>>
>>> The IETF Secretariat
>>>
>>
>> _______________________________________________
>> sfc mailing list
>> sfc@ietf.org
>> https://www.ietf.org/mailman/listinfo/sfc
>
> _______________________________________________
> sfc mailing list
> sfc@ietf.org
> https://www.ietf.org/mailman/listinfo/sfc
>


From nobody Thu Mar  5 04:09:52 2015
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A46811A0141 for <sfc@ietfa.amsl.com>; Thu,  5 Mar 2015 04:09:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 N4B9UABfGzdD for <sfc@ietfa.amsl.com>; Thu,  5 Mar 2015 04:09:44 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias243.francetelecom.com [80.12.204.243]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3EB5E1B29B8 for <sfc@ietf.org>; Thu,  5 Mar 2015 04:09:44 -0800 (PST)
Received: from omfeda06.si.francetelecom.fr (unknown [xx.xx.xx.199]) by omfeda09.si.francetelecom.fr (ESMTP service) with ESMTP id 60704C0BC2; Thu,  5 Mar 2015 13:09:42 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.16]) by omfeda06.si.francetelecom.fr (ESMTP service) with ESMTP id 36682C80B8; Thu,  5 Mar 2015 13:09:42 +0100 (CET)
Received: from OPEXCLILM23.corporate.adroot.infra.ftgroup ([169.254.2.181]) by OPEXCLILH05.corporate.adroot.infra.ftgroup ([10.114.31.16]) with mapi id 14.03.0224.002; Thu, 5 Mar 2015 13:09:41 +0100
From: <mohamed.boucadair@orange.com>
To: "Haeffner, Walter, Vodafone DE" <walter.haeffner@vodafone.com>, "Paul Quinn (paulq)" <paulq@cisco.com>, Jim Guichard <jguichar@cisco.com>, "Thomas Narten" <narten@us.ibm.com>, Jeff Napper <jenapper@cisco.com>, "Martin Stiemerling" <martin.stiemerling@h-da.de>, "Surendra Kumar (smkumar)" <smkumar@cisco.com>
Thread-Topic: [sfc] draft-quinn-sfc-nsh: relatniship with the use cases drafts
Thread-Index: AdBRDaI7xfMTZEmzRd6IIps3ZiTmogEICK4AAAwm2PAAbmjuYAAF4EVZAAMmuvA=
Date: Thu, 5 Mar 2015 12:09:41 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933004926027@OPEXCLILM23.corporate.adroot.infra.ftgroup>
References: <787AE7BB302AE849A7480A190F8B9330049140FD@OPEXCLILM23.corporate.adroot.infra.ftgroup> <CA29E3DA-324E-4FA3-AC0B-4148E46999D5@cisco.com> <C8C844F84E550E43865561FAE10471854C5F0C8B@VOEXM20W.internal.vodafone.com>, <787AE7BB302AE849A7480A190F8B933004923BBE@OPEXCLILM23.corporate.adroot.infra.ftgroup> <C8C844F84E550E43865561FAE10471854C5F3EBB@VOEXM20W.internal.vodafone.com>
In-Reply-To: <C8C844F84E550E43865561FAE10471854C5F3EBB@VOEXM20W.internal.vodafone.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.1]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B933004926027OPEXCLILM23corp_"
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.3.5.100039
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/aTj521yTvJwaSlY0R6qV_QLVkNc>
Cc: "sfc@ietf.org" <sfc@ietf.org>, "stbryant@cisco.com" <stbryant@cisco.com>
Subject: Re: [sfc] draft-quinn-sfc-nsh: relatniship with the use cases drafts
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 05 Mar 2015 12:09:50 -0000

--_000_787AE7BB302AE849A7480A190F8B933004926027OPEXCLILM23corp_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Walter,

Looks like a good plan to me.

Thank you.

Cheers,
Med

De : Haeffner, Walter, Vodafone DE [mailto:walter.haeffner@vodafone.com]
Envoy=E9 : jeudi 5 mars 2015 11:31
=C0 : BOUCADAIR Mohamed IMT/OLN; Paul Quinn (paulq); Jim Guichard; Thomas N=
arten; Jeff Napper; Martin Stiemerling; Surendra Kumar (smkumar)
Cc : sfc@ietf.org; stbryant@cisco.com
Objet : AW: [sfc] draft-quinn-sfc-nsh: relatniship with the use cases draft=
s

Hi,

As said, originally we had requirements derived from the individual use cas=
es included in the mobility use case draft itself.

1) We could add these again in the use case draft. But this requires agreem=
ent by the WG (Chairs). Personally I prefer this approach.

Jim, Tom, what is your position?

2) We could check how derived requirements and functional design recommenda=
tions would fit into the requirements draft. But this may be more time cons=
uming.

Wrt references to use cases I am fully in line with Med.

Cheers,
Walter


Gesendet mit meinem HTC

----- Reply message -----
Von: "mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>" <m=
ohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>>
An: "Haeffner, Walter, Vodafone DE" <walter.haeffner@vodafone.com<mailto:wa=
lter.haeffner@vodafone.com>>, "Paul Quinn (paulq)" <paulq@cisco.com<mailto:=
paulq@cisco.com>>
Cc: "sfc@ietf.org<mailto:sfc@ietf.org>" <sfc@ietf.org<mailto:sfc@ietf.org>>=
, "stbryant@cisco.com<mailto:stbryant@cisco.com>" <stbryant@cisco.com<mailt=
o:stbryant@cisco.com>>
Betreff: [sfc] draft-quinn-sfc-nsh: relatniship with the use cases drafts
Datum: Do., M=E4r 5, 2015 08:49

Hi Walter, Paul,


What I'm expecting is to derive requirements from the use cases, exactly in=
 line with what was mentioned by Stewart Bryant here: http://www.ietf.org/m=
ail-archive/web/sfc/current/msg01751.html, especially this part:



"I assume that the plan is to write down the use cases, then to distill fro=
m

the use cases the requirements, to write the architecture (or framework)

based on the the requirements and the to write the solutions to satisfy the

requirements consistent with the architecture."



The use case I-Ds should not cite the header specification draft but the ot=
her way around: the nsh should at least include pointers to the use case I-=
Ds produced by the WG, and preferably motivate some of its design choices b=
y explicit requirements derived from those use cases I-Ds.



Cheers,

Med

De : Haeffner, Walter, Vodafone DE [mailto:walter.haeffner@vodafone.com]
Envoy=E9 : lundi 2 mars 2015 17:15
=C0 : Paul Quinn (paulq); BOUCADAIR Mohamed IMT/OLN
Cc : sfc@ietf.org<mailto:sfc@ietf.org>
Objet : AW: [sfc] draft-quinn-sfc-nsh: relatniship with the use cases draft=
s

Hi Paul, Med,

In the mobile use case draft we mentioned usage and impact of metadata on S=
FC. We also mentioned that a NSH may be appropriate. Because at time of wri=
ting NSH was not (and is not by today) implemented in SFs, we couldn't give=
 an explicit example. And we were asked not to include requirements in the =
draft.

Walter
Von: sfc [mailto:sfc-bounces@ietf.org] Im Auftrag von Paul Quinn (paulq)
Gesendet: Montag, 2. M=E4rz 2015 16:14
An: mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>
Cc: sfc@ietf.org<mailto:sfc@ietf.org>
Betreff: Re: [sfc] draft-quinn-sfc-nsh: relatniship with the use cases draf=
ts

Hi Med,


Are you suggesting that the use cases be included as references, or explici=
t referenced?  Perhaps a logical path forward, if NSH is adopted, that perh=
aps the use cases can be updated to reflect the "SFC encap".

Paul


On Feb 25, 2015, at 10:13 AM, mohamed.boucadair@orange.com<mailto:mohamed.b=
oucadair@orange.com> wrote:

Re-,

It is unfortunate the current NSH specification does not rely on the SFC us=
e cases as documented by the WG.

Does this mean that those are useless? That no (common) requirements can be=
 derived from those I-Ds to guide the specification of the NSH header?

Cheers,
Med
_______________________________________________
sfc mailing list
sfc@ietf.org<mailto:sfc@ietf.org>
https://www.ietf.org/mailman/listinfo/sfc


--_000_787AE7BB302AE849A7480A190F8B933004926027OPEXCLILM23corp_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Texte brut Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Texte de bulles Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:12.0pt;
	margin-left:36.0pt;
	font-size:12.0pt;
	font-family:"Courier New";}
span.TextebrutCar
	{mso-style-name:"Texte brut Car";
	mso-style-priority:99;
	mso-style-link:"Texte brut";
	font-family:Consolas;}
span.TextedebullesCar
	{mso-style-name:"Texte de bulles Car";
	mso-style-priority:99;
	mso-style-link:"Texte de bulles";
	font-family:"Tahoma","sans-serif";}
p.msolistparagraphcxspfirst, li.msolistparagraphcxspfirst, div.msolistparag=
raphcxspfirst
	{mso-style-name:msolistparagraphcxspfirst;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Courier New";}
p.msolistparagraphcxspmiddle, li.msolistparagraphcxspmiddle, div.msolistpar=
agraphcxspmiddle
	{mso-style-name:msolistparagraphcxspmiddle;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Courier New";}
p.msolistparagraphcxsplast, li.msolistparagraphcxsplast, div.msolistparagra=
phcxsplast
	{mso-style-name:msolistparagraphcxsplast;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:12.0pt;
	margin-left:36.0pt;
	font-size:12.0pt;
	font-family:"Courier New";}
p.msochpdefault, li.msochpdefault, div.msochpdefault
	{mso-style-name:msochpdefault;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:10.0pt;
	font-family:"Times New Roman","serif";}
span.emailstyle18
	{mso-style-name:emailstyle18;
	font-family:"Courier New";
	color:windowtext;
	font-weight:normal;
	font-style:normal;}
span.emailstyle19
	{mso-style-name:emailstyle19;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.textedebullescar0
	{mso-style-name:textedebullescar;
	font-family:"Tahoma","sans-serif";}
span.emailstyle22
	{mso-style-name:emailstyle22;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;}
span.textebrutcar0
	{mso-style-name:textebrutcar;
	font-family:"Courier New";
	color:black;}
span.EmailStyle31
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"FR" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Hi Walter,
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Looks like a good plan to me.<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Thank you.<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Cheers,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Med<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">De&nbsp;:</span></b><span style=3D"fo=
nt-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Haef=
fner, Walter, Vodafone DE [mailto:walter.haeffner@vodafone.com]
<br>
<b>Envoy=E9&nbsp;:</b> jeudi 5 mars 2015 11:31<br>
<b>=C0&nbsp;:</b> BOUCADAIR Mohamed IMT/OLN; Paul Quinn (paulq); Jim Guicha=
rd; Thomas Narten; Jeff Napper; Martin Stiemerling; Surendra Kumar (smkumar=
)<br>
<b>Cc&nbsp;:</b> sfc@ietf.org; stbryant@cisco.com<br>
<b>Objet&nbsp;:</b> AW: [sfc] draft-quinn-sfc-nsh: relatniship with the use=
 cases drafts<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">Hi,<o:p></o:p></spa=
n></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">&nbsp;<o:p></o:p></=
span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">As said, originally=
 we had requirements derived from the individual use cases included in the =
mobility use case draft itself.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">1) We could add the=
se again in the use case draft. But this requires agreement by&nbsp;the WG =
(Chairs). Personally I prefer this approach.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">Jim, Tom, what is y=
our position?<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">2) We could check h=
ow derived requirements and functional design recommendations would fit int=
o the requirements draft. But this may be more time consuming.<o:p></o:p></=
span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">Wrt references to u=
se cases I am fully in line with Med.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">Cheers,<o:p></o:p><=
/span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">Walter<o:p></o:p></=
span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">Gesendet mit meinem=
 HTC<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
<div id=3D"htc_header">
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">----- Reply message=
 -----<br>
Von: &quot;<a href=3D"mailto:mohamed.boucadair@orange.com">mohamed.boucadai=
r@orange.com</a>&quot; &lt;<a href=3D"mailto:mohamed.boucadair@orange.com">=
mohamed.boucadair@orange.com</a>&gt;<br>
An: &quot;Haeffner, Walter, Vodafone DE&quot; &lt;<a href=3D"mailto:walter.=
haeffner@vodafone.com">walter.haeffner@vodafone.com</a>&gt;, &quot;Paul Qui=
nn (paulq)&quot; &lt;<a href=3D"mailto:paulq@cisco.com">paulq@cisco.com</a>=
&gt;<br>
Cc: &quot;<a href=3D"mailto:sfc@ietf.org">sfc@ietf.org</a>&quot; &lt;<a hre=
f=3D"mailto:sfc@ietf.org">sfc@ietf.org</a>&gt;, &quot;<a href=3D"mailto:stb=
ryant@cisco.com">stbryant@cisco.com</a>&quot; &lt;<a href=3D"mailto:stbryan=
t@cisco.com">stbryant@cisco.com</a>&gt;<br>
Betreff: [sfc] draft-quinn-sfc-nsh: relatniship with the use cases drafts<b=
r>
Datum: Do., M=E4r 5, 2015 08:49<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Hi Walter, Paul,</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">What I'm expecting is to der=
ive requirements from the use cases, exactly in line with what was mentione=
d by Stewart Bryant here:
</span><a href=3D"http://www.ietf.org/mail-archive/web/sfc/current/msg01751=
.html"><span lang=3D"EN-US">http://www.ietf.org/mail-archive/web/sfc/curren=
t/msg01751.html</span></a><span lang=3D"EN-US">, especially this part:</spa=
n><o:p></o:p></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&quot;I assume that the plan=
 is to write down the use cases, then to distill from</span><o:p></o:p></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">the use cases the requiremen=
ts, to write the architecture (or framework)</span><o:p></o:p></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">based on the the requirement=
s and the to write the solutions to satisfy the</span><o:p></o:p></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">requirements consistent with=
 the architecture.&quot;</span><o:p></o:p></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">The use case I-Ds should not=
 cite the header specification draft but the other way around: the nsh shou=
ld at least include pointers to the use case I-Ds produced by the WG, and p=
referably motivate some of its design
 choices by explicit requirements derived from those use cases I-Ds.</span>=
<o:p></o:p></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Cheers,</span><o:p></o:p></p=
>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Med</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">&nbsp;</span><o:p></o:p></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">De&nbsp;:</span></b><span style=3D"fo=
nt-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Haef=
fner, Walter, Vodafone DE [<a href=3D"mailto:walter.haeffner@vodafone.com">=
mailto:walter.haeffner@vodafone.com</a>]
<br>
<b>Envoy=E9&nbsp;:</b> lundi 2 mars 2015 17:15<br>
<b>=C0&nbsp;:</b> Paul Quinn (paulq); BOUCADAIR Mohamed IMT/OLN<br>
<b>Cc&nbsp;:</b> <a href=3D"mailto:sfc@ietf.org">sfc@ietf.org</a><br>
<b>Objet&nbsp;:</b> AW: [sfc] draft-quinn-sfc-nsh: relatniship with the use=
 cases drafts</span><o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Hi Paul=
, Med,</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span><o:p></o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">In the =
mobile use case draft we mentioned usage and impact of metadata on SFC. We =
also mentioned that a NSH may be appropriate. Because at time of writing NS=
H was not (and is not by today) implemented
 in SFs, we couldn&#8217;t give an explicit example. And we were asked not =
to include requirements in the draft.</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span><o:p></o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Walter<=
/span><o:p></o:p></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"DE" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">Von:</span></b><span lang=
=3D"DE" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans=
-serif&quot;"> sfc [<a href=3D"mailto:sfc-bounces@ietf.org">mailto:sfc-boun=
ces@ietf.org</a>]
<b>Im Auftrag von </b>Paul Quinn (paulq)<br>
<b>Gesendet:</b> Montag, 2. </span><span lang=3D"EN-US" style=3D"font-size:=
10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">M=E4rz 2015 1=
6:14<br>
<b>An:</b> <a href=3D"mailto:mohamed.boucadair@orange.com">mohamed.bou<span=
 lang=3D"DE">cadair@orange.com</span></a></span><span lang=3D"DE" style=3D"=
font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"><br=
>
<b>Cc:</b> <a href=3D"mailto:sfc@ietf.org">sfc@ietf.org</a><br>
<b>Betreff:</b> Re: [sfc] draft-quinn-sfc-nsh: relatniship with the use cas=
es drafts</span><o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span><o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hi Med,</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Are you suggesting that the use=
 cases be included as references, or explicit referenced? &nbsp;Perhaps a l=
ogical path forward, if NSH is adopted, that perhaps the use cases can be u=
pdated to reflect the &#8220;SFC encap&#8221;.</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Paul</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span><o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span><o:p></o:p></p>
<div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">On Feb 25, 2015, at 10:13 AM, <=
a href=3D"mailto:mohamed.boucadair@orange.com">
mohamed.boucadair@orange.com</a> wrote:</span><o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Re-,</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;">It is unfortunate the current NSH specifica=
tion does not rely on the SFC use cases as documented by the WG.
</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;">Does this mean that those are useless? That=
 no (common) requirements can be derived from those I-Ds to guide the speci=
fication of the NSH header?
</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;">Cheers,</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;">Med
</span><o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:12.0pt;font-=
family:&quot;Times New Roman&quot;,&quot;serif&quot;">_____________________=
__________________________<br>
sfc mailing list<br>
<a href=3D"mailto:sfc@ietf.org">sfc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/sfc">https://www.ietf.org/=
mailman/listinfo/sfc</a></span><o:p></o:p></p>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:12.0pt;font-=
family:&quot;Times New Roman&quot;,&quot;serif&quot;">&nbsp;</span><o:p></o=
:p></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_787AE7BB302AE849A7480A190F8B933004926027OPEXCLILM23corp_--


From nobody Thu Mar  5 06:27:16 2015
Return-Path: <Ron_Parker@affirmednetworks.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 562321A0204 for <sfc@ietfa.amsl.com>; Thu,  5 Mar 2015 06:27:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 rQIbyuPkbuEc for <sfc@ietfa.amsl.com>; Thu,  5 Mar 2015 06:27:07 -0800 (PST)
Received: from hub021-ca-4.exch021.serverdata.net (hub021-ca-4.exch021.serverdata.net [64.78.22.171]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DF571A0233 for <sfc@ietf.org>; Thu,  5 Mar 2015 06:20:41 -0800 (PST)
Received: from MBX021-W3-CA-2.exch021.domain.local ([10.254.4.78]) by HUB021-CA-4.exch021.domain.local ([10.254.4.39]) with mapi id 14.03.0224.002;  Thu, 5 Mar 2015 06:20:40 -0800
From: Ron Parker <Ron_Parker@affirmednetworks.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "Paul Quinn (paulq)" <paulq@cisco.com>
Thread-Topic: [sfc] draft-quinn-sfc-nsh: version number
Thread-Index: AQHQVpZW8SURGK4OQ02kqAeqyFHktJ0N+TeA///3w4A=
Date: Thu, 5 Mar 2015 14:20:40 +0000
Message-ID: <CDF2F015F4429F458815ED2A6C2B6B0B2E85A202@MBX021-W3-CA-2.exch021.domain.local>
References: <01f9e1a4e6514854a26556e4c6a3e36e@SEAEXCHMBX05.olympus.F5Net.com> <787AE7BB302AE849A7480A190F8B933004919B76@OPEXCLILM23.corporate.adroot.infra.ftgroup> <CDF2F015F4429F458815ED2A6C2B6B0B2E85379B@MBX021-W3-CA-2.exch021.domain.local> <787AE7BB302AE849A7480A190F8B93300491A1AF@OPEXCLILM23.corporate.adroot.infra.ftgroup> <CDF2F015F4429F458815ED2A6C2B6B0B2E8558D0@MBX021-W3-CA-2.exch021.domain.local> <787AE7BB302AE849A7480A190F8B93300491A1F7@OPEXCLILM23.corporate.adroot.infra.ftgroup> <08AFD2FB-AC81-479A-9098-0FFEDDBF0A58@cisco.com> <787AE7BB302AE849A7480A190F8B933004922B46@OPEXCLILM23.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B933004922B46@OPEXCLILM23.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [50.203.66.100]
Content-Type: multipart/alternative; boundary="_000_CDF2F015F4429F458815ED2A6C2B6B0B2E85A202MBX021W3CA2exch_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/erkMtH9PU33HwgfWVZpDCJxixKI>
Cc: Sunil Vallamkonda <sunilvk@f5.com>, "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] draft-quinn-sfc-nsh: version number
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 05 Mar 2015 14:27:15 -0000

--_000_CDF2F015F4429F458815ED2A6C2B6B0B2E85A202MBX021W3CA2exch_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Med,

Albeit, from a co-author's perspective, the MD type, as I see it, is the cu=
rrent grand compromise, attempting to balance ease of parsing (MD type 1) a=
nd unconstrained flexibility (MD type 2).

   Ron



From: mohamed.boucadair@orange.com [mailto:mohamed.boucadair@orange.com]
Sent: Thursday, March 5, 2015 1:47 AM
To: Paul Quinn (paulq)
Cc: Ron Parker; Sunil Vallamkonda; sfc@ietf.org
Subject: RE: [sfc] draft-quinn-sfc-nsh: version number

Hi Paul,

Glad to see that we are sharing the same objective to design simple things,=
 but the design should not cause another yet set of failure cases (which is=
 the case of the current spec: the non-support of the MD type will be a cau=
se of failure too).

I already provided a long message with my thoughts (http://www.ietf.org/mai=
l-archive/web/sfc/current/msg03175.html).

I can propose text, but we need to agree first. I'm still questioning the n=
eed to have the version field in addition to other fields such as MD type.

I hope to see more feedback from the WG participants other than the authors=
 of the draft so that I can adjust the proposed text.

Cheers,
Med

De : Paul Quinn (paulq) [mailto:paulq@cisco.com]
Envoy=E9 : mercredi 4 mars 2015 17:15
=C0 : BOUCADAIR Mohamed IMT/OLN
Cc : Ron Parker; Sunil Vallamkonda; sfc@ietf.org<mailto:sfc@ietf.org>
Objet : Re: [sfc] draft-quinn-sfc-nsh: version number


On Mar 4, 2015, at 11:09 AM, mohamed.boucadair@orange.com<mailto:mohamed.bo=
ucadair@orange.com> wrote:

Re-,

That would be a good start, but still not sufficient IMHO.

If no notification is sent back (which can be the case with the MAY languag=
e), the failure will be experienced till an action is done by the domain op=
erator. This is not desirable.

Having a more strong language for sending back the response (that needs to =
include at least the received packet with the unsupported version) will hav=
e the effect to resend the packet with an adequate version (if multiple ver=
sions are supported). The exact behavior when a version mismatch error is r=
eceived should be explicated in the document IMO.

Perhaps the best way forward: can you please suggest some text that we can =
all review?  I'm inclined to keep things simple (i.e. simple error message =
of sorts) but since you've given this a lot of thought, I'd love to see you=
r suggestions.



--_000_CDF2F015F4429F458815ED2A6C2B6B0B2E85A202MBX021W3CA2exch_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"Segoe UI";
	panose-1:2 11 5 2 4 2 4 2 2 3;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:Cambria;
	panose-1:2 4 5 3 5 4 6 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
h1
	{mso-style-priority:9;
	mso-style-link:"Heading 1 Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	font-weight:normal;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.Heading1Char
	{mso-style-name:"Heading 1 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 1";
	font-family:"Times New Roman",serif;
	font-weight:bold;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Segoe UI",sans-serif;}
p.Titre1, li.Titre1, div.Titre1
	{mso-style-name:"Titre 1";
	mso-style-link:"Titre 1 Car";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.Titre1Car
	{mso-style-name:"Titre 1 Car";
	mso-style-priority:9;
	mso-style-link:"Titre 1";
	font-family:"Cambria",serif;
	color:#365F91;
	font-weight:bold;}
p.PrformatHTML, li.PrformatHTML, div.PrformatHTML
	{mso-style-name:"Pr=E9format=E9 HTML";
	mso-style-link:"Pr=E9format=E9 HTML Car";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.PrformatHTMLCar
	{mso-style-name:"Pr=E9format=E9 HTML Car";
	mso-style-priority:99;
	mso-style-link:"Pr=E9format=E9 HTML";
	font-family:Consolas;}
p.Textebrut, li.Textebrut, div.Textebrut
	{mso-style-name:"Texte brut";
	mso-style-link:"Texte brut Car";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.TextebrutCar
	{mso-style-name:"Texte brut Car";
	mso-style-priority:99;
	mso-style-link:"Texte brut";
	font-family:"Courier New";
	color:black;
	mso-fareast-language:EN-US;}
p.Textedebulles, li.Textedebulles, div.Textedebulles
	{mso-style-name:"Texte de bulles";
	mso-style-link:"Texte de bulles Car";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.TextedebullesCar
	{mso-style-name:"Texte de bulles Car";
	mso-style-priority:99;
	mso-style-link:"Texte de bulles";
	font-family:"Tahoma",sans-serif;}
span.EmailStyle32
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle33
	{mso-style-type:personal;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;}
span.EmailStyle34
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
span.EmailStyle35
	{mso-style-type:personal;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;}
span.EmailStyle36
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
span.EmailStyle37
	{mso-style-type:personal;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;}
span.EmailStyle38
	{mso-style-type:personal;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;}
span.EmailStyle39
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Med,<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Albeit, from a co-auth=
or&#8217;s perspective, the MD type, as I see it, is the current grand comp=
romise, attempting to balance ease of parsing (MD type 1) and unconstrained=
 flexibility (MD type 2).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp; Ron<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><a name=3D"_MailEndCompose"><span style=3D"color:#1F=
497D"><o:p>&nbsp;</o:p></span></a></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> mohamed.boucadair@orange.com [mailto:mo=
hamed.boucadair@orange.com]
<br>
<b>Sent:</b> Thursday, March 5, 2015 1:47 AM<br>
<b>To:</b> Paul Quinn (paulq)<br>
<b>Cc:</b> Ron Parker; Sunil Vallamkonda; sfc@ietf.org<br>
<b>Subject:</b> RE: [sfc] draft-quinn-sfc-nsh: version number<o:p></o:p></p=
>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:10.0pt;font-fam=
ily:&quot;Courier New&quot;;color:black">Hi Paul,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:10.0pt;font-fam=
ily:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Glad to see that we are sharing the same objec=
tive to design simple things, but the design should not cause another yet s=
et of failure cases (which is the case of the
 current spec: the non-support of the MD type will be a cause of failure to=
o).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">I already provided a long message with my thou=
ghts (<a href=3D"http://www.ietf.org/mail-archive/web/sfc/current/msg03175.=
html">http://www.ietf.org/mail-archive/web/sfc/current/msg03175.html</a>).
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">I can propose text, but we need to agree first=
. I&#8217;m still questioning the need to have the version field in additio=
n to other fields such as MD type.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">I hope to see more feedback from the WG partic=
ipants other than the authors of the draft so that I can adjust the propose=
d text.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Cheers,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Med<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span lang=3D"FR" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,sans-serif">De&nbsp;:</span></b><span lang=3D"FR"=
 style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,sans-serif"> Paul=
 Quinn (paulq) [<a href=3D"mailto:paulq@cisco.com">mailto:paulq@cisco.com</=
a>]
<br>
<b>Envoy=E9&nbsp;:</b> mercredi 4 mars 2015 17:15<br>
<b>=C0&nbsp;:</b> BOUCADAIR Mohamed IMT/OLN<br>
<b>Cc&nbsp;:</b> Ron Parker; Sunil Vallamkonda; <a href=3D"mailto:sfc@ietf.=
org">sfc@ietf.org</a><br>
<b>Objet&nbsp;:</b> Re: [sfc] draft-quinn-sfc-nsh: version number<o:p></o:p=
></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"FR"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR"><o:p>&nbsp;</o:p></span></p>
<div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal"><span lang=3D"FR">On Mar 4, 2015, at 11:09 AM, <a hr=
ef=3D"mailto:mohamed.boucadair@orange.com">
mohamed.boucadair@orange.com</a> wrote:<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"FR"><o:p>&nbsp;</o:p></span></p>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:10.0pt;font-fam=
ily:&quot;Courier New&quot;">Re-,</span><span lang=3D"FR"><o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:10.0pt;font-fam=
ily:&quot;Courier New&quot;">&nbsp;</span><span lang=3D"FR"><o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">That would be a good start, but still not sufficient IMHO.=
</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">If no notification is sent back (which can be the case wit=
h the MAY language), the failure will be experienced till an action is done=
 by the domain operator. This is not desirable.
</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;</span><span lang=3D"FR"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Having a more strong language for sending back the respons=
e (that needs to include at least the received packet with the unsupported =
version) will have the effect to resend the packet
 with an adequate version (if multiple versions are supported). The exact b=
ehavior when a version mismatch error is received should be explicated in t=
he document IMO.
</span><span lang=3D"FR"><o:p></o:p></span></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:12.0pt;font-fam=
ily:&quot;Times New Roman&quot;,serif"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:12.0pt;font-fam=
ily:&quot;Times New Roman&quot;,serif">Perhaps the best way forward: can yo=
u please suggest some text that we can all review? &nbsp;I&#8217;m inclined=
 to keep things simple (i.e. simple error message of sorts)
 but since you&#8217;ve given this a lot of thought, I&#8217;d love to see =
your suggestions.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:12.0pt;font-fam=
ily:&quot;Times New Roman&quot;,serif"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-size:12.0pt;font-fam=
ily:&quot;Times New Roman&quot;,serif"><o:p>&nbsp;</o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_CDF2F015F4429F458815ED2A6C2B6B0B2E85A202MBX021W3CA2exch_--


From nobody Thu Mar  5 07:11:01 2015
Return-Path: <jguichar@cisco.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAB181A00EC; Thu,  5 Mar 2015 07:10:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 qlKyDUltsugV; Thu,  5 Mar 2015 07:10:57 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 109DF1A00F1; Thu,  5 Mar 2015 07:10:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8573; q=dns/txt; s=iport; t=1425568257; x=1426777857; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=oykqFIs/7z0IUbL4Zfge2fnvrLkbijJ8j+4/0RRCxIw=; b=OcZwpPckK91gkQtPgYiChwvcZpxFqJn/Hukiw4Y+NirTIc5vgoU4Lzep lhfgmCXNMhT2rWoEhGi7sqj5kdm8sXNVxyjUO1snlCLhlHWmlc+8ncno9 l0uDVX5cQkvIIOBA3+GtSNx8jmI04kPrLU0MqosUr/gSukgAQigoafToe U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AWBQCicfhU/5RdJa1agwZSVQUEwSgKhXECgTZNAQEBAQEBfIQPAQEBBAEBATctBgEJAgwEAgEIEQEDAQEBHgkHJwsUAwYIAgQBDQUJC4gbCAXXYgEBAQEBAQEBAQEBAQEBAQEBAQEBAReLFIRDKwcCBIQlBZAFg2OFaoEaOYJtglOJGYNAI4IHF4FQb4FEfwEBAQ
X-IronPort-AV: E=Sophos;i="5.11,347,1422921600"; d="scan'208";a="129239855"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-4.cisco.com with ESMTP; 05 Mar 2015 15:10:55 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id t25FAtoT016526 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 5 Mar 2015 15:10:55 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.159]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.03.0195.001; Thu, 5 Mar 2015 09:10:55 -0600
From: "Jim Guichard (jguichar)" <jguichar@cisco.com>
To: Ron Parker <Ron_Parker@affirmednetworks.com>, Xuxiaohu <xuxiaohu@huawei.com>
Thread-Topic: [sfc] New Version Notification for draft-xu-sfc-using-mpls-spring-02.txt
Thread-Index: AQHQVpoI7gzyPgBE9Ui3i2CAn8f8sZ0Nhy2AgAAGBICAAIOCAA==
Date: Thu, 5 Mar 2015 15:10:55 +0000
Message-ID: <D11DD3D6.BD0C%jguichar@cisco.com>
References: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0830F7C0@NKGEML512-MBS.china.huawei.com> <CDF2F015F4429F458815ED2A6C2B6B0B2E855978@MBX021-W3-CA-2.exch021.domain.local> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0830FC8E@NKGEML512-MBS.china.huawei.com> <34ECE28B-F7AB-4FB9-9CE1-06289FB739B4@affirmednetworks.com>
In-Reply-To: <34ECE28B-F7AB-4FB9-9CE1-06289FB739B4@affirmednetworks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.7.141117
x-originating-ip: [10.98.43.182]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <486F6B61E57C4B4598F57B2215D99590@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/vsAjq9bLAIJR0aXIFou04sL3Qtw>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "<spring@ietf.org>" <spring@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] New Version Notification for draft-xu-sfc-using-mpls-spring-02.txt
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 05 Mar 2015 15:11:00 -0000

Hi Xiaohu,

Thomas and I read your latest draft and believe that you will need to take
it to the MPLS WG as a first step. There are a number of things within the
document that may require changes to the base MPLS architecture and the
SFC WG is not the right community to address those. Given this we will not
be able to consider this document in the SFC WG without agreement from the
broader MPLS community.

Regards,

Jim & Thomas


On 3/4/15, 9:20 PM, "Ron Parker" <Ron_Parker@affirmednetworks.com> wrote:

>I think it needs to be there between SFF's, too.  In the case where there
>is no metadata, you could argue that the data in NSH and the label stack
>are redundantly saying the same thing, but an optimization along these
>lines would not be justified, IMO.
>
>   Ron
>
>
>> On Mar 4, 2015, at 8:58 PM, Xuxiaohu <xuxiaohu@huawei.com> wrote:
>>=20
>> Hi Ron,
>>=20
>> Thanks a lot for your insightful comments and suggestions. By the way,
>>in the case where there is no need to deliver metadata, does it mean the
>>NSH just only needs to be contained the packets exchanged between SFFs
>>and SFs? In other words, the NSH is used as a way for the SFF to
>>retrieve the label stack which has been stripped by that SFF before.
>>=20
>> Best regards,
>> Xiaohu=20
>>=20
>>> -----Original Message-----
>>> From: Ron Parker [mailto:Ron_Parker@affirmednetworks.com]
>>> Sent: Thursday, March 05, 2015 12:41 AM
>>> To: Xuxiaohu; sfc@ietf.org; <spring@ietf.org>; mpls@ietf.org
>>> Subject: RE: [sfc] New Version Notification for
>>> draft-xu-sfc-using-mpls-spring-02.txt
>>>=20
>>> Xiaohu,
>>>=20
>>> I read your latest draft and I do see the elegance of describing a
>>>sequence of
>>> must-visit nodes as a stack of MPLS labels.   And I see that you've
>>>addressed
>>> the transport-independence requirement by stating that the MPLS frames
>>>could
>>> be carried within IP tunnels (i.e., MPLS in UDP, etc.).    But, I have
>>>a couple of
>>> issues that I suggest be addressed.
>>>=20
>>> First, the text is written as if the NSH header is optional and
>>>present only if
>>> metadata is required.    The SFC architecture is such that the NSH is
>>> mandatory.   I think this issue can be combined with the second issue
>>>that I'll
>>> raise below.
>>>=20
>>> Second, the notion is that the SFF's strip the label stack and then
>>>restore the
>>> label stack.    And since the text states that even when NSH is
>>>present, the SFP
>>> ID is not used, the only remaining basis to do this is flow learning
>>>in the SFF.
>>> While I think there are many reasons that may cause SFF's to utilize
>>>flow
>>> learning advantageously, it should not be a fundamental necessity to
>>>realize an
>>> SFF, IMO.   But even if the SFF is a flow learner, this is still
>>>inadequate since the
>>> SF may change the 5-tuple (e.g., NAT) or may launch internally
>>>generated flows
>>> (e.g., HTTP proxy).   Both cases could not be satisfied by flow
>>>learning.
>>>=20
>>> What I suggest, instead, is a tighter coupling between the NSH header
>>>and the
>>> MPLS label stack.   That there be a 1:1 equivalency between {SFP ID,
>>>SFP hop
>>> index} and the label stack.   Thus, when the SFC-aware SF returns a
>>>packet to
>>> the SFF, the {SFP ID, SFP hop index} contained in the NSH be used to
>>>push the
>>> appropriate label stack onto the packet.    I believe this would bring
>>>the
>>> approach into conformance with the SFC architectural requirements
>>> (mandatory NSH, transport independence) and would solve the problems
>>>with
>>> flow learning identified above.
>>>=20
>>>   Ron
>>>=20
>>>=20
>>>=20
>>> -----Original Message-----
>>> From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of Xuxiaohu
>>> Sent: Tuesday, March 3, 2015 11:10 PM
>>> To: Xuxiaohu; sfc@ietf.org; <spring@ietf.org>; mpls@ietf.org
>>> Subject: Re: [sfc] New Version Notification for
>>> draft-xu-sfc-using-mpls-spring-02.txt
>>>=20
>>> The rationales for leveraging the MPLS-SPRING mechanism to realize the
>>>service
>>> path layer functionality of the service function chaining are as
>>>follows:
>>>=20
>>> 1) eliminate the SFC/SFP states on SFFs. This follows the same logic as
>>> MPLS-SPRING and BIER.
>>> 2) utilize the existing encapsulation (e.g., the MPLS-SPRING) to a
>>>maximum
>>> extent. This follows the Transport Derived SFF concept as described in
>>>Section
>>> 4.3.1 of draft-ietf-sfc-architecture. Meanwhile, this is aligned with
>>>the current
>>> SFC charter, e.g., "...The working group will consider using an
>>>existing
>>> encapsulation (with extensions as appropriate) if a suitable candidate
>>>is found..."
>>> 3) seamlessly support the SFC in a multi-tenant environment (e.g.,
>>>MPLS VPN).
>>> For example, the MPLS VPN packet (containing metadata) could be further
>>> imposed with a label stack which indicates an SFC or SFP associated
>>>with that
>>> packet. SFFs receiving the above packet would strip the whole label
>>>stack and
>>> then send the payload of the MPLS packet (with metadata) to the
>>>corresponding
>>> SFs which are tenant-aware and therefore easily could determine the
>>>tenant
>>> profile according to the tenant info contained in the metadata
>>>(a.k.a., the NSH).
>>>=20
>>> Best regards,
>>> Xiaohu
>>>=20
>>>=20
>>>> -----Original Message-----
>>>> From: Xuxiaohu
>>>> Sent: Wednesday, March 04, 2015 11:31 AM
>>>> To: sfc@ietf.org; '<spring@ietf.org>'; mpls@ietf.org
>>>> Subject: FW: New Version Notification for
>>>> draft-xu-sfc-using-mpls-spring-02.txt
>>>>=20
>>>> Hi all,
>>>>=20
>>>> This document describes how to leverage the MPLS-based source routing
>>>> (i.e.,
>>>> MPLS-SPRING) mechanism as developed by the SPRING WG to realize the
>>>> service path layer functionality of the service function chaining. In
>>>> addition, this document also describes how to carry metadata in an
>>>> MPLS packet by using the NSH as a metadata container.
>>>>=20
>>>> Any comments are suggestions are welcome.
>>>>=20
>>>> Best regards,
>>>> Xiaohu
>>>>=20
>>>>> -----Original Message-----
>>>>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>>>>> Sent: Wednesday, March 04, 2015 11:24 AM
>>>>> To: Lizhenbin; Luis M. Contreras; Xuxiaohu; Himanshu C. Shah;
>>>>> Xuxiaohu; Himanshu Shah; Luis M. Contreras; Lizhenbin
>>>>> Subject: New Version Notification for
>>>>> draft-xu-sfc-using-mpls-spring-02.txt
>>>>>=20
>>>>>=20
>>>>> A new version of I-D, draft-xu-sfc-using-mpls-spring-02.txt
>>>>> has been successfully submitted by Xiaohu Xu and posted to the IETF
>>>> repository.
>>>>>=20
>>>>> Name:        draft-xu-sfc-using-mpls-spring
>>>>> Revision:    02
>>>>> Title:        Service Function Chaining Using MPLS-SPRING
>>>>> Document date:    2015-03-03
>>>>> Group:        Individual Submission
>>>>> Pages:        8
>>>>> URL:
>>>>>=20
>>>>>http://www.ietf.org/internet-drafts/draft-xu-sfc-using-mpls-spring-02.
>>>>> txt
>>>>> Status:
>>>>> https://datatracker.ietf.org/doc/draft-xu-sfc-using-mpls-spring/
>>>>> Htmlized:
>>> http://tools.ietf.org/html/draft-xu-sfc-using-mpls-spring-02
>>>>> Diff:
>>>>> http://www.ietf.org/rfcdiff?url2=3Ddraft-xu-sfc-using-mpls-spring-02
>>>>>=20
>>>>> Abstract:
>>>>>   Source Packet Routing in Networking (SPRING) WG specifies a special
>>>>>   source routing mechanism.  Such source routing mechanism can be
>>>>>   leveraged to realize the service path layer functionality of the
>>>>>   service function chaining (i.e, steering traffic through a
>>>>>particular
>>>>>   service function path) by encoding the service function path or the
>>>>>   service function chain information as the explicit path
>>>>>information.
>>>>>   This document describes how to leverage the MPLS-based source
>>> routing
>>>>>   mechanism as developed by the SPRING WG to realize the service path
>>>>>   layer functionality of the service function chaining.
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> Please note that it may take a couple of minutes from the time of
>>>>> submission until the htmlized version and diff are available at
>>>>>tools.ietf.org.
>>>>>=20
>>>>> The IETF Secretariat
>>>=20
>>> _______________________________________________
>>> sfc mailing list
>>> sfc@ietf.org
>>> https://www.ietf.org/mailman/listinfo/sfc
>
>_______________________________________________
>sfc mailing list
>sfc@ietf.org
>https://www.ietf.org/mailman/listinfo/sfc


From nobody Thu Mar  5 07:31:57 2015
Return-Path: <smkumar@cisco.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14C871A0302 for <sfc@ietfa.amsl.com>; Thu,  5 Mar 2015 07:31:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 BCyWmcv_z_cl for <sfc@ietfa.amsl.com>; Thu,  5 Mar 2015 07:31:49 -0800 (PST)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E197E1A0387 for <sfc@ietf.org>; Thu,  5 Mar 2015 07:31:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5864; q=dns/txt; s=iport; t=1425569508; x=1426779108; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=DqJfFo3DyPWl+tVgBOuROtJrpLjX40FBoFrBfkdWxio=; b=hPGBfpGK50dP7ic+rxCWq16mKGV09hKXYGR7AB1pRNpLwJxgSeH5KOYa sQpd5Fv1RBBcml8eOJuch/KOr534guUbTGfuqLRKgBAUep7OKeI4BC96k njpFY329aI0oYRgI+czMQAiw08aNbsJxDbOr22ZOFIoVLLaRiUwS+tHis s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AOBQDTdfhU/5FdJa1agwZSWgTBKAqFcQKBNk0BAQEBAQF8hA8BAQEEAQEBawkCEAIBCBIGJwcnCxQDBQkCBAENBQkQiBYN12gBAQEBAQEBAQEBAQEBAQEBAQEBGYsUhCUWMweEKwWKNYVQg2OFaoEaOYJti2yDQCODbm8BgQJBfwEBAQ
X-IronPort-AV: E=Sophos;i="5.11,347,1422921600"; d="scan'208";a="129240897"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by alln-iport-2.cisco.com with ESMTP; 05 Mar 2015 15:31:47 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id t25FVk4u013923 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 5 Mar 2015 15:31:47 GMT
Received: from xmb-aln-x09.cisco.com ([169.254.4.43]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.03.0195.001; Thu, 5 Mar 2015 09:31:43 -0600
From: "Surendra Kumar (smkumar)" <smkumar@cisco.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Thread-Topic: [sfc] FW: New Version Notification for draft-kumar-sfc-offloads-00.txt
Thread-Index: AQHQVzL9q5L6T6TaPk6jOUxclppgZp0N4weA
Date: Thu, 5 Mar 2015 15:31:42 +0000
Message-ID: <D11DAD19.19276%smkumar@cisco.com>
References: <20150304183622.20056.47379.idtracker@ietfa.amsl.com> <D11C90EC.18D0C%smkumar@cisco.com> <787AE7BB302AE849A7480A190F8B933004924D0F@OPEXCLILM23.corporate.adroot.infra.ftgroup> <54F83617.2080105@joelhalpern.com>
In-Reply-To: <54F83617.2080105@joelhalpern.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.7.141117
x-originating-ip: [10.24.219.83]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <40C027DED1329C4188EB8EFA4788B143@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/CJvFwUQsZW9woI3DzodRsHb15Pk>
Cc: "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] FW: New Version Notification for draft-kumar-sfc-offloads-00.txt
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 05 Mar 2015 15:31:55 -0000

Med,

The offload decision is cached only against the SF requesting it. We don=B9=
t
assume their co-location.

Further, these offload decisions are assumed to be on a flow boundary and
any changes to SF or other classification aspects will take effect with
control actions that lead to the clearing of the offload cache.

Thanks for reviewing the draft,
Surendra.

On 3/5/15, 2:55 AM, "Joel M. Halpern" <jmh@joelhalpern.com> wrote:

>I am not sure I understand your concern about co-location.
>The mechanisms proposed has to, and as far as I can tell does, work
>whether the SFF is colocated with the SF or in a separate node.  Is the
>confusion caused by some of the example discussion?
>
>As for the case where there are multiple SF handled by the same SFF,
>that is the assumed case.  The SFF can tell which SF is requesting the
>bypass, and apply it only to that SF.
>
>Yours,
>Joel
>
>On 3/5/15 3:59 AM, mohamed.boucadair@orange.com wrote:
>> Hi Surendra,
>>
>> Thank you for sharing this I-D that touches on classification
>>complications in an SFC architecture. Interesting!
>>
>> I have some quick comments about the draft:
>>
>> * It seems that you are assuming that SF and SFF are always separate
>>nodes. SF and SFF are functional elements that may be co-located or not.
>>Whether those are collocated in the same physical node or not is
>>deployment-specific.
>>
>> * What would be the behavior when a node hosting several SFs, serviced
>>by the same SFF, receives the offload indication?
>>
>> * In addition to the potential classification issue you mentioned in
>>your draft, there are other issues that are worth to be considered, e.g.,
>>     o  Rationalize the management of classification rules.
>>     o  Help assessing the impact of removing or modifying a
>>        classification rule.
>>     o  Check the coherency of instantiated classification rules.
>>     o  Help aggregating rules: this allows to optimize the
>>classification
>>        rule table and therefor accelerate packet/flow processing (mainly
>>        reduce lookup delays).
>>     o  Adjust classification rules when rules are based on volatile
>>        identifiers (e.g., IP address).
>>     o  Maintain an global overview of instantiated rules in involved
>>        Network Elements.
>>     o  Rapidly restore state during failure events.
>>     o  Network Elements can retrieve their table after failure events
>>        whiteout requiring permanent storage capacity.
>>
>> Whether classification-related issues should be discussed as a package
>>or individually can be useful to discuss. IMHO, classification burden
>>and SFC OAM are the KEY challenging parts of an SFC architecture.
>>
>> * It would be fair to cite this I-D for the control part discussion:
>>https://datatracker.ietf.org/doc/draft-ww-sfc-control-plane/
>>
>> Thank you.
>>
>> Cheers,
>> Med
>>
>>> -----Message d'origine-----
>>> De : sfc [mailto:sfc-bounces@ietf.org] De la part de Surendra Kumar
>>> (smkumar)
>>> Envoy=E9 : mercredi 4 mars 2015 19:49
>>> =C0 : sfc@ietf.org
>>> Objet : [sfc] FW: New Version Notification for
>>>draft-kumar-sfc-offloads-
>>> 00.txt
>>>
>>> Hi all:
>>>
>>> We posted a new draft, but with old content. After the presentation on
>>> simple offloads + Optimization at HNL, we received a lot of feedback.
>>>
>>> In including it, we have split the SFP Path Optimization draft into
>>>two:
>>> 1) this one which limits itself to the offload between SF and SFF
>>> 2) the original sfp optimization draft, which focuses on optimization
>>>of
>>> the SFP among the SFFs
>>>
>>> #2 will be updated to reflect the split
>>>
>>> Thanks and we appreciate your comments/questions,
>>> Surendra.
>>>
>>> On 3/4/15, 10:36 AM, "internet-drafts@ietf.org"
>>><internet-drafts@ietf.org>
>>> wrote:
>>>
>>>>
>>>> A new version of I-D, draft-kumar-sfc-offloads-00.txt
>>>> has been successfully submitted by Surendra Kumar and posted to the
>>>> IETF repository.
>>>>
>>>> Name:		draft-kumar-sfc-offloads
>>>> Revision:	00
>>>> Title:		Service Function Simple Offloads
>>>> Document date:	2015-03-04
>>>> Group:		Individual Submission
>>>> Pages:		15
>>>> URL:
>>>> http://www.ietf.org/internet-drafts/draft-kumar-sfc-offloads-00.txt
>>>> Status:         https://datatracker.ietf.org/doc/draft-kumar-sfc-
>>> offloads/
>>>> Htmlized:       http://tools.ietf.org/html/draft-kumar-sfc-offloads-00
>>>>
>>>>
>>>> Abstract:
>>>>    Service Function Chaining (SFC) enables services to be delivered by
>>>>    selective traffic steering through an ordered set of service
>>>>    functions.  Once classified into an SFC, the traffic for a given
>>>>flow
>>>>    is steered through all the service functions of the SFC for the
>>>>life
>>>>    of the traffic flow even though this is often not necessary.
>>>>    Steering traffic to service functions only while required and not
>>>>    otherwise, leads to shorter SFC forwarding paths with improved
>>>>    latencies, reduced resource consumption and better user experience.
>>>>
>>>>    This document describes the rationale, techniques and necessary
>>>>    protocol extensions to achieve such optimization, with focus on one
>>>>    such technique termed "simple offloads".
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Please note that it may take a couple of minutes from the time of
>>>> submission
>>>> until the htmlized version and diff are available at tools.ietf.org.
>>>>
>>>> The IETF Secretariat
>>>>
>>>
>>> _______________________________________________
>>> sfc mailing list
>>> sfc@ietf.org
>>> https://www.ietf.org/mailman/listinfo/sfc
>>
>> _______________________________________________
>> sfc mailing list
>> sfc@ietf.org
>> https://www.ietf.org/mailman/listinfo/sfc
>>


From nobody Thu Mar  5 12:17:34 2015
Return-Path: <smkumar@cisco.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25D7A1A89EF for <sfc@ietfa.amsl.com>; Thu,  5 Mar 2015 12:17:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 w8siF0iwXVOR for <sfc@ietfa.amsl.com>; Thu,  5 Mar 2015 12:17:26 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 041991A8991 for <sfc@ietf.org>; Thu,  5 Mar 2015 12:17:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=67269; q=dns/txt; s=iport; t=1425586646; x=1426796246; h=from:to:cc:subject:date:message-id:mime-version; bh=DYaB5f2RphXa3pIgHY/ROgLS/hciUC6hJJmptHgOAx4=; b=ZZtWgbswaGzNnOROgQ1McJ1WkAa728p5m7nQ3dvjCGKulsRF9DQDFq4p 5LiuaON33n+BEIXYQRdXH2sDypy4t5s2UNFKNzRGNIBEU1zVKQSjWyd9g /YputmW5XADHKay7U/fouvFwxTvgHPcLrGuiJjmQweg5o4xRhGLP284ac c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ASBQCVufhU/5xdJa1agkNDUloEwRUZAQmFcAKBO00BAQEBAQF8hA8BAQEDAQEBARcTQAELBQ0BCBEBAgEBASEBBi4LFAMGCgQBDQUJiBIDCQgN0mcDhT4BAQEBAQEBAQEBAQEBAQEBAQEBAQEXixeEHQEBDRUCBxMHBgQGAwQDhCIFhiqHXYIAg2NKhSCBGjmSHCOCAhyBUG8BAYEAAgQDFyJ/AQEB
X-IronPort-AV: E=Sophos;i="5.11,348,1422921600";  d="scan'208,217";a="129278063"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-1.cisco.com with ESMTP; 05 Mar 2015 20:17:17 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id t25KHHkO015338 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 5 Mar 2015 20:17:17 GMT
Received: from xmb-aln-x09.cisco.com ([169.254.4.43]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.03.0195.001; Thu, 5 Mar 2015 14:17:16 -0600
From: "Surendra Kumar (smkumar)" <smkumar@cisco.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, Ron Parker <Ron_Parker@affirmednetworks.com>, Sunil Vallamkonda <sunilvk@f5.com>
Thread-Topic: [sfc] draft-quinn-sfc-nsh: version number
Thread-Index: AQHQV4Fer3RnebCP60euLuaPOYFkkA==
Date: Thu, 5 Mar 2015 20:17:16 +0000
Message-ID: <D11DBC70.19374%smkumar@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.7.141117
x-originating-ip: [10.24.219.83]
Content-Type: multipart/alternative; boundary="_000_D11DBC7019374smkumarciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/tGmYCxPkUl6ugAnDMXCB-qlfXnE>
Cc: "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] draft-quinn-sfc-nsh: version number
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 05 Mar 2015 20:17:32 -0000

--_000_D11DBC7019374smkumarciscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable



From: "mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>" <=
mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>>
Date: Wednesday, March 4, 2015 at 8:09 AM
To: Ron Parker <Ron_Parker@affirmednetworks.com<mailto:Ron_Parker@affirmedn=
etworks.com>>, Sunil Vallamkonda <sunilvk@f5.com<mailto:sunilvk@f5.com>>
Cc: "sfc@ietf.org<mailto:sfc@ietf.org>" <sfc@ietf.org<mailto:sfc@ietf.org>>
Subject: Re: [sfc] draft-quinn-sfc-nsh: version number

Re-,

That would be a good start, but still not sufficient IMHO.

If no notification is sent back (which can be the case with the MAY languag=
e), the failure will be experienced till an action is done by the domain op=
erator. This is not desirable.

Having a more strong language for sending back the response (that needs to =
include at least the received packet with the unsupported version) will hav=
e the effect to resend the packet with an adequate version (if multiple ver=
sions are supported). The exact behavior when a version mismatch error is r=
eceived should be explicated in the document IMO.
SK> Version incompatibility (with version numbers as opposed to flags) is a=
 transient issue when there exists a control-plane. It is very likely that =
there will exist SFs/SFFs/Classifiers which understand different versions o=
f the header and they must continue to inter-operate. The control plane mus=
t ensure a highest common version among the participants.

In the absence of such an over-arching control plane, there is a need to re=
solve the versions and this may or may not require data plane learning of t=
he versions based on how seamlessly the participants are required to be ins=
erted into the architecture. One could make a case either way but seems mor=
e appropriate to be left to the control plane, particularly given the exten=
sibility built into the header - hopefully it is some time before we have a=
 need to bump the version.

Surendra.

Cheers,
Med

De : Ron Parker [mailto:Ron_Parker@affirmednetworks.com]
Envoy=E9 : mercredi 4 mars 2015 16:50
=C0 : BOUCADAIR Mohamed IMT/OLN; Sunil Vallamkonda
Cc : sfc@ietf.org<mailto:sfc@ietf.org>
Objet : RE: Re: [sfc] draft-quinn-sfc-nsh: version number

Med,

I agree that we should add additional text around the expected behavior reg=
arding version incompatibility.   We could state that the SFF or SF perceiv=
ing this incompatibility MUST drop such a packet and MAY generate an OAM re=
sponse in the reverse direction, although the exact nature of that response=
 is outside the scope of the NSH draft.

   Ron





From: mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com> [ma=
ilto:mohamed.boucadair@orange.com]
Sent: Wednesday, March 4, 2015 10:43 AM
To: Ron Parker; Sunil Vallamkonda
Cc: sfc@ietf.org<mailto:sfc@ietf.org>
Subject: RE: Re: [sfc] draft-quinn-sfc-nsh: version number

Hi Ron,

If the version number is maintained, discussing the behavior of a node if i=
t supports several versions, if it does not support the version of a packet=
 it receives, etc. is not about OAM. This is part of the behavior that need=
s to be specified in the document.

Cheers,
Med


De : Ron Parker [mailto:Ron_Parker@affirmednetworks.com]
Envoy=E9 : mercredi 4 mars 2015 16:03
=C0 : BOUCADAIR Mohamed IMT/OLN; Sunil Vallamkonda
Cc : sfc@ietf.org<mailto:sfc@ietf.org>
Objet : RE: Re: [sfc] draft-quinn-sfc-nsh: version number

When we take up OAM, we could consider these ICMP-like behaviors =96 i.e., =
OAM packet containing =93Version Incompatible=94 sent in the reverse direct=
ion on the involved RSP.   But I=92m not sure what should be discussed in t=
his draft, since OAM is explicitly out of scope.

   Ron



From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of mohamed.boucadair@oran=
ge.com<mailto:mohamed.boucadair@orange.com>
Sent: Wednesday, March 4, 2015 1:47 AM
To: Sunil Vallamkonda
Cc: sfc@ietf.org<mailto:sfc@ietf.org>
Subject: Re: [sfc] draft-quinn-sfc-nsh: version number

Hi Sunil,

There is no such notification in the current spec.

Below my thoughts about this point:

=3D=3D

(b) Suppose a node that supports only v1 receives a packet with header (v2)=
: If this node does not support a notification procedure to inform the sour=
ce that it does not support that header version, then FAILURES are introduc=
ed in the network. This is a degradation of the service compared to legacy =
scheme to structure services. This is not recommended, IMHO.



(c) If a notification is received from an element about its supported versi=
on: a node can use another version (the logic to select other version is an=
other point to discuss) for that communication, but what to do for the next=
 flows in the context of the same service chain or other chains that involv=
es these two nodes as adjacent elements in the same chain? Shouldn't these =
nodes cache the version to use for subsequent exchange to avoid receiving t=
he notification error each time? Wouldn't that complexity the behavior of t=
he SFC-aware elements?



(d) If a notification is received from an element about its supported versi=
on: As this may occurs in various segments of a given service chain, e.g., =
(A(v1), B(v1,v2), C(v1), D(v1,v2), E(v1)). Notifying the adjacent node each=
 time there is a version mismatch induce an extra delay, that may be not be=
 acceptable for every flow.
=3D=3D

Thank you.

Cheers,
Med


De : sfc [mailto:sfc-bounces@ietf.org] De la part de Sunil Vallamkonda
Envoy=E9 : mardi 3 mars 2015 20:43
=C0 : sfc@ietf.org<mailto:sfc@ietf.org>
Objet : Re: [sfc] draft-quinn-sfc-nsh: version number

Hi,

Just going through the thread on version number (jumping in mid-thread),

Apart from the version mismatched (unsupported) packet dropped and logged, =
is there a plan for a back off mechanism by SFF to notify sender and avoid =
being overwhelmed with such packets ?

Thank you,
Sunil.


Re: [sfc] draft-quinn-sfc-nsh: version number
________________________________

  *   From: "Paul Quinn (paulq)" <paulq at cisco.com<mailto:paulq@DOMAIN.HI=
DDEN>>
  *   To: "Joel M. Halpern" <jmh at joelhalpern.com<mailto:jmh@DOMAIN.HIDDE=
N>>
  *   Cc: "mohamed.boucadair at orange.com<mailto:mohamed.boucadair@DOMAIN.=
HIDDEN>" <mohamed.boucadair at orange.com<mailto:mohamed.boucadair@DOMAIN.H=
IDDEN>>, "sfc at ietf.org<mailto:sfc@DOMAIN.HIDDEN>" <sfc at ietf.org<mailt=
o:sfc@DOMAIN.HIDDEN>>
  *   Date: Mon, 2 Mar 2015 17:50:53 +0000
  *   In-reply-to: <54EF2C9A.3040008@joelhalpern.com<http://www.ietf.org/ma=
il-archive/web/sfc/current/msg03181.html>>
  *   References: <787AE7BB302AE849A7480A190F8B9330049140B4@OPEXCLILM23.cor=
porate.adroot.infra.ftgroup<mailto:787AE7BB302AE849A7480A190F8B9330049140B4=
@OPEXCLILM23.corporate.adroot.infra.ftgroup>> <54EDE5B7.6080102@joelhalpern=
.com<http://www.ietf.org/mail-archive/web/sfc/current/msg03151.html>> <787A=
E7BB302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.adroot.infra.ftg=
roup<mailto:787AE7BB302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.=
adroot.infra.ftgroup>> <54EF2C9A.3040008@joelhalpern.com<http://www.ietf.or=
g/mail-archive/web/sfc/current/msg03181.html>>
  *   List-id: Network Service Chaining <sfc.ietf.org>

________________________________

Hi,



Jumping in mid-thread.



Overall, I tend to agree with Joel.  Having an explicit version provides a =
simple way to handle dataplane format changes.  As Med points out, quickly =
correctly, IMHO, there are other way to signal changes via reserved bit.  I=
n practice though reserved bits are less useful since the convention is to =
ignore unknown bits, it makes using them for feature changes quite difficul=
t, which then brings up back to explicit versioning that cannot be ignored.



I think Joel=92s suggestion below makes perfect sense and should be added t=
o the draft.



Paul





> On Feb 26, 2015, at 9:24 AM, Joel M. Halpern <jmh at joelhalpern.com> wro=
te:

>

> In one sense you are correct.  If you could count on everything being upg=
raded at once, sure you could just assume common interpretation.

> However, we have found over the years that such simultaneous upgrading ne=
ver works.  You need to be able to transition.

>

> I do agree that we should add text about what to do with version numbers =
that are not understood.  There are multiple choices that affect how we can=
 make changes.  My personal preference is:

>

> If an packet presumed to carry an NSH header is received at an SFF, and t=
he SFF does not understnad the version of the protocol as indicated in the =
base header, the packet MUST be discarded, and the event SHOULD be logged.

>

> This would allow an orderly transition, where devices can be upgraded to =
understand a new version, then generation of the new version header can be =
enabled.  If a configuration error is made, the packets will be dropped and=
 operators following good practices will get notifications.

>

> Yours,

> Joel

>

> On 2/26/15 2:16 AM, mohamed.boucadair at orange.com wrote:

>> Hi Joel,

>>

>> I fully agree with the extendibility of the header, but the question is =
why having a version number will be of help in the context of SFC? Second, =
having a version number without specifying the behavior when several versio=
ns are supported, when the version number is not supported by an SFC-aware =
element, etc. leaves open issues out of the spec.

>>

>> The other problem is that the current I-D includes several open doors le=
ft for extending the header:

>> * version

>> * reserved bits

>> * optional data

>>

>> This is too much for a header that is supposed to be compact and simple!

>>

>> There are other means to extend the header without signaling the version=
 in the packet. Having a distinct RFC number may be just fine in the contex=
t of an unidirectional stream such as SFC.

>>

>> Let us consider the situation where a version number is not explicitly s=
ignaled in the packet (but a new RFC updates the base SFC header). Several =
options can be considered, indeed (those are provided as examples for illus=
tration purposes):

>> * An operator can make sure that its SFC-enabled domain is configured in=
 a consistent manner to support one and only one version of the header. No =
interoperability issues is encountered in this case.

>> * An operator that wants to upgrade its SFC-enabled domain to support a =
new specification of the SFC header: An operator can decide to proceed to a=
 software/hardware updates but can maintain the old header in operation unt=
il all involved elements are upgraded to support the new version. Once the =
SFC-enabled domain is upgraded, then the new header can be enabled.

>>

>> Let's consider now that a version is signaled in the packet: to what ext=
ent signaling this information simplifies the SFC operations, and whether i=
t increases/decreases the serviceability of an SFC-enabled domain? Let's al=
so assess to what extent having the version number add more complexity in t=
he SFC header treatment when several versions are supported by a node/withi=
n an SFC enabled domain? How it helps interoperability? Some points for dis=
cussion are elaborated below:

>>

>> * If the SFC-enabled domain is configured to support the same version (w=
hich is likely): having the version number is not of any help.

>> * If the SFC-enabled domain involves some nodes that support version (v1=
) while others support (v2) (simple case): If these version are not backwar=
d compatible, this will lead to failures when two adjacent elements in a se=
rvice chain do not support the same version. The SFC system is broken. Havi=
ng the version number is not of any help in this case.

>> * If the SFC-enabled domain involves some nodes that support version (v1=
) while others support (v1 and v2):

>>

>> (a) The nodes that support both v1 and v2 should be instructed to decide=
 which version to be used. This can be either part of the specification or =
be driven by configuration. If a version number is included in the spec, I =
would expect to clarify the behavior in such case.

>>

>> (b) Suppose a node that supports only v1 receives a packet with header (=
v2): If this node does not support a notification procedure to inform the s=
ource that it does not support that header version, then FAILURES are intro=
duced in the network. This is a degradation of the service compared to lega=
cy scheme to structure services. This is not recommended, IMHO.

>>

>> (c) If a notification is received from an element about its supported ve=
rsion: a node can use another version (the logic to select other version is=
 another point to discuss) for that communication, but what to do for the n=
ext flows in the context of the same service chain or other chains that inv=
olves these two nodes as adjacent elements in the same chain? Shouldn't the=
se nodes cache the version to use for subsequent exchange to avoid receivin=
g the notification error each time? Wouldn't that complexity the behavior o=
f the SFC-aware elements?

>>

>> (d) If a notification is received from an element about its supported ve=
rsion: As this may occurs in various segments of a given service chain, e.g=
., (A(v1), B(v1,v2), C(v2), D(v1,v2), E(v1)). Notifying the adjacent node e=
ach time there is a version mismatch induce an extra delay, that may be not=
 be acceptable for every flow.

>>

>> I hope this clarifies my initial concern.

>>

>> Thank you.

>>

>> Cheers,

>> Med

>>

>>> -----Message d'origine-----

>>> De : Joel M. Halpern [mailto:jmh at joelhalpern.com]

>>> Envoy=E9 : mercredi 25 f=E9vrier 2015 16:10

>>> =C0 : BOUCADAIR Mohamed IMT/OLN; paulq at cisco.com

>>> Cc : sfc at ietf.org

>>> Objet : Re: [sfc] draft-quinn-sfc-nsh: version number

>>>

>>> I would really prefer to keep the version number.  Even though we have

>>> the MD-type identifier and for some MD we have the TLVs.

>>>

>>> The reason is that we may want to change the base header.  For example,

>>> suppose that the ciscussion about including a flow identifier in the

>>> base header had not come up now.  If it came up later, we would want to

>>> be able to have the discussion and make the choice, rather than being

>>> constrained by the lack of a version field.

>>>

>>> Yours,

>>> Joel

>>>

>>>

>>> On 2/25/15 10:03 AM, mohamed.boucadair at orange.com wrote:

>>>> Hi Paul, all,

>>>>

>>>> What is the purpose of having a version number in the header? Is there=
 a

>>>> kind of version negotiation that needs to be in place?

>>>>

>>>> I checked the I-D but failed to find text that explains the rationale,

>>>> the use of the such field and whether an error will be returned if the

>>>> version is not supported by the receiving node.

>>>>

>>>> Wouldn't be preferable to get rid of this field given that SFC header

>>>> can be extended using optional objects and consistent setup &

>>>> configuration within an SFC-enabled domain should be assumed?

>>>>

>>>> Thank you

>>>>

>>>> Cheers,

>>>>

>>>> Med

>>>>

>>>>

>>>>

>>>> _______________________________________________

>>>> sfc mailing list

>>>> sfc at ietf.org

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

>>>>

>>




--_000_D11DBC7019374smkumarciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <4327037199A1C5419C495708864BEE78@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div><br>
</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>&quot;<a href=3D"mailto:moham=
ed.boucadair@orange.com">mohamed.boucadair@orange.com</a>&quot; &lt;<a href=
=3D"mailto:mohamed.boucadair@orange.com">mohamed.boucadair@orange.com</a>&g=
t;<br>
<span style=3D"font-weight:bold">Date: </span>Wednesday, March 4, 2015 at 8=
:09 AM<br>
<span style=3D"font-weight:bold">To: </span>Ron Parker &lt;<a href=3D"mailt=
o:Ron_Parker@affirmednetworks.com">Ron_Parker@affirmednetworks.com</a>&gt;,=
 Sunil Vallamkonda &lt;<a href=3D"mailto:sunilvk@f5.com">sunilvk@f5.com</a>=
&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>&quot;<a href=3D"mailto:sfc@iet=
f.org">sfc@ietf.org</a>&quot; &lt;<a href=3D"mailto:sfc@ietf.org">sfc@ietf.=
org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Re: [sfc] draft-quinn-sfc-=
nsh: version number<br>
</div>
<div><br>
</div>
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Cambria;
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"Segoe UI";
	panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
h1
	{mso-style-priority:9;
	mso-style-link:"Titre 1 Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	font-weight:normal;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Texte brut Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"Pr=E9format=E9 HTML Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Texte de bulles Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.Titre1Car
	{mso-style-name:"Titre 1 Car";
	mso-style-priority:9;
	mso-style-link:"Titre 1";
	font-family:"Cambria","serif";
	color:#365F91;
	font-weight:bold;}
span.PrformatHTMLCar
	{mso-style-name:"Pr=E9format=E9 HTML Car";
	mso-style-priority:99;
	mso-style-link:"Pr=E9format=E9 HTML";
	font-family:Consolas;}
span.TextebrutCar
	{mso-style-name:"Texte brut Car";
	mso-style-priority:99;
	mso-style-link:"Texte brut";
	font-family:"Courier New";
	color:black;
	mso-fareast-language:EN-US;}
span.TextedebullesCar
	{mso-style-name:"Texte de bulles Car";
	mso-style-priority:99;
	mso-style-link:"Texte de bulles";
	font-family:"Tahoma","sans-serif";}
p.Heading1, li.Heading1, div.Heading1
	{mso-style-name:"Heading 1";
	mso-style-link:"Heading 1 Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.Heading1Char
	{mso-style-name:"Heading 1 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 1";
	font-family:"Times New Roman","serif";
	font-weight:bold;}
p.HTMLPreformatted, li.HTMLPreformatted, div.HTMLPreformatted
	{mso-style-name:"HTML Preformatted";
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
p.PlainText, li.PlainText, div.PlainText
	{mso-style-name:"Plain Text";
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
p.BalloonText, li.BalloonText, div.BalloonText
	{mso-style-name:"Balloon Text";
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Segoe UI","sans-serif";}
span.EmailStyle32
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle33
	{mso-style-type:personal;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;}
span.EmailStyle34
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle35
	{mso-style-type:personal;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;}
span.EmailStyle36
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle38
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1094283961;
	mso-list-template-ids:-714036274;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
<div lang=3D"FR" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; font-family: 'Courie=
r New'; color: black;">Re-,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; font-family: 'Courie=
r New'; color: black;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New'; color: black;">That would be a good start, but still=
 not sufficient IMHO.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New'; color: black;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New'; color: black;">If no notification is sent back (whic=
h can be the case with the MAY language), the failure will be experienced t=
ill an action is done by the domain operator.
 This is not desirable. <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New'; color: black;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New'; color: black;">Having a more strong language for sen=
ding back the response (that needs to include at least the received packet =
with the unsupported version) will have
 the effect to resend the packet with an adequate version (if multiple vers=
ions are supported). The exact behavior when a version mismatch error is re=
ceived should be explicated in the document IMO.</span></p>
</div>
</div>
</div>
</span>
<div>SK&gt; Version incompatibility (with version numbers as opposed to fla=
gs) is a transient issue when there exists a control-plane. It is very like=
ly that there will exist SFs/SFFs/Classifiers which understand different ve=
rsions of the header and they must
 continue to inter-operate. The control plane must ensure a highest common =
version among the participants.</div>
<div><br>
</div>
<div>In the absence of such an over-arching control plane, there is a need =
to resolve the versions and this may or may not require data plane learning=
 of the versions based on how seamlessly the participants are required to b=
e inserted into the architecture.
 One could make a case either way but seems more appropriate to be left to =
the control plane, particularly given the extensibility built into the head=
er - hopefully it is some time before we have a need to bump the version.</=
div>
<div><br>
</div>
<div>Surendra.</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<div lang=3D"FR" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New'; color: black;"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New'; color: black;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New'; color: black;">Cheers,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New'; color: black;">Med<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New'; color: black;"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size: 10pt; font-family: Taho=
ma, sans-serif;">De&nbsp;:</span></b><span style=3D"font-size: 10pt; font-f=
amily: Tahoma, sans-serif;"> Ron Parker [<a href=3D"mailto:Ron_Parker@affir=
mednetworks.com">mailto:Ron_Parker@affirmednetworks.com</a>]
<br>
<b>Envoy=E9&nbsp;:</b> mercredi 4 mars 2015 16:50<br>
<b>=C0&nbsp;:</b> BOUCADAIR Mohamed IMT/OLN; Sunil Vallamkonda<br>
<b>Cc&nbsp;:</b> <a href=3D"mailto:sfc@ietf.org">sfc@ietf.org</a><br>
<b>Objet&nbsp;:</b> RE: Re: [sfc] draft-quinn-sfc-nsh: version number<o:p><=
/o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Med,<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">I agree=
 that we should add additional text around the expected behavior regarding =
version incompatibility.&nbsp;&nbsp; We could state that the SFF or SF perc=
eiving this incompatibility MUST drop such a packet
 and MAY generate an OAM response in the reverse direction, although the ex=
act nature of that response is outside the scope of the NSH draft.<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp; Ron<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><a name=3D"_MailEndCompose"></a><span lang=3D"EN-US"=
 style=3D"color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US">From:</span></b><span lang=
=3D"EN-US"> <a href=3D"mailto:mohamed.boucadair@orange.com">
mohamed.boucadair@orange.com</a> [<a href=3D"mailto:mohamed.boucadair@orang=
e.com">mailto:mohamed.boucadair@orange.com</a>]
<br>
<b>Sent:</b> Wednesday, March 4, 2015 10:43 AM<br>
<b>To:</b> Ron Parker; Sunil Vallamkonda<br>
<b>Cc:</b> <a href=3D"mailto:sfc@ietf.org">sfc@ietf.org</a><br>
<b>Subject:</b> RE: Re: [sfc] draft-quinn-sfc-nsh: version number<o:p></o:p=
></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; font-family: 'Courie=
r New'; color: black;">Hi Ron,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; font-family: 'Courie=
r New'; color: black;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New'; color: black;">If the version number is maintained, =
discussing the behavior of a node if it supports several versions, if it do=
es not support the version of a packet
 it receives, etc. is not about OAM. This is part of the behavior that need=
s to be specified in the document.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New'; color: black;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New'; color: black;">Cheers,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New'; color: black;">Med<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New'; color: black;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New'; color: black;"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size: 10pt; font-family: Taho=
ma, sans-serif;">De&nbsp;:</span></b><span style=3D"font-size: 10pt; font-f=
amily: Tahoma, sans-serif;"> Ron Parker [<a href=3D"mailto:Ron_Parker@affir=
mednetworks.com">mailto:Ron_Parker@affirmednetworks.com</a>]
<br>
<b>Envoy=E9&nbsp;:</b> mercredi 4 mars 2015 16:03<br>
<b>=C0&nbsp;:</b> BOUCADAIR Mohamed IMT/OLN; Sunil Vallamkonda<br>
<b>Cc&nbsp;:</b> <a href=3D"mailto:sfc@ietf.org">sfc@ietf.org</a><br>
<b>Objet&nbsp;:</b> RE: Re: [sfc] draft-quinn-sfc-nsh: version number<o:p><=
/o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">When we=
 take up OAM, we could consider these ICMP-like behaviors =96 i.e., OAM pac=
ket containing =93Version Incompatible=94 sent in the reverse direction on =
the involved RSP.&nbsp;&nbsp; But I=92m not sure what should
 be discussed in this draft, since OAM is explicitly out of scope.<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp; Ron<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US">From:</span></b><span lang=
=3D"EN-US"> sfc [<a href=3D"mailto:sfc-bounces@ietf.org">mailto:sfc-bounces=
@ietf.org</a>]
<b>On Behalf Of </b><a href=3D"mailto:mohamed.boucadair@orange.com">mohamed=
.boucadair@orange.com</a><br>
<b>Sent:</b> Wednesday, March 4, 2015 1:47 AM<br>
<b>To:</b> Sunil Vallamkonda<br>
<b>Cc:</b> <a href=3D"mailto:sfc@ietf.org">sfc@ietf.org</a><br>
<b>Subject:</b> Re: [sfc] draft-quinn-sfc-nsh: version number<o:p></o:p></s=
pan></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New'; color: black;">Hi Sunil,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New'; color: black;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New'; color: black;">There is no such notification in the =
current spec.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New'; color: black;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New'; color: black;">Below my thoughts about this point:<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New'; color: black;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New'; color: black;">=3D=3D<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size: 10pt; fo=
nt-family: 'Courier New'; color: black;">(b) Suppose a node that supports o=
nly v1 receives a packet with header (v2): If this node does not support a =
notification procedure to inform the source
 that it does not support that header version, then FAILURES are introduced=
 in the network. This is a degradation of the service compared to legacy sc=
heme to structure services. This is not recommended, IMHO.<o:p></o:p></span=
></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size: 10pt; fo=
nt-family: 'Courier New'; color: black;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size: 10pt; fo=
nt-family: 'Courier New'; color: black;">(c) If a notification is received =
from an element about its supported version: a node can use another version=
 (the logic to select other version is
 another point to discuss) for that communication, but what to do for the n=
ext flows in the context of the same service chain or other chains that inv=
olves these two nodes as adjacent elements in the same chain? Shouldn't the=
se nodes cache the version to use
 for subsequent exchange to avoid receiving the notification error each tim=
e? Wouldn't that complexity the behavior of the SFC-aware elements?<o:p></o=
:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size: 10pt; fo=
nt-family: 'Courier New'; color: black;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size: 10pt; fo=
nt-family: 'Courier New'; color: black;">(d) If a notification is received =
from an element about its supported version: As this may occurs in various =
segments of a given service chain, e.g.,
 (A(v1), B(v1,v2), C(v1), D(v1,v2), E(v1)). Notifying the adjacent node eac=
h time there is a version mismatch induce an extra delay, that may be not b=
e acceptable for every flow.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New'; color: black;">=3D=3D<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New'; color: black;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New'; color: black;">Thank you.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New'; color: black;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New'; color: black;">Cheers,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New'; color: black;">Med<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New'; color: black;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-=
family: 'Courier New'; color: black;"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size: 10pt; font-family: Taho=
ma, sans-serif;">De&nbsp;:</span></b><span style=3D"font-size: 10pt; font-f=
amily: Tahoma, sans-serif;"> sfc [<a href=3D"mailto:sfc-bounces@ietf.org">m=
ailto:sfc-bounces@ietf.org</a>]
<b>De la part de</b> Sunil Vallamkonda<br>
<b>Envoy=E9&nbsp;:</b> mardi 3 mars 2015 20:43<br>
<b>=C0&nbsp;:</b> <a href=3D"mailto:sfc@ietf.org">sfc@ietf.org</a><br>
<b>Objet&nbsp;:</b> Re: [sfc] draft-quinn-sfc-nsh: version number<o:p></o:p=
></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hi,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Just going through the thread o=
n version number (jumping in mid-thread),<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Apart from the version mismatch=
ed (unsupported) packet dropped and logged, is there a plan for a back off =
mechanism by SFF to notify sender and avoid being overwhelmed with such pac=
kets ?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Thank you,<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Sunil.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;<o:p></o:p></span></p>
<h1 style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang=
=3D"EN-US" style=3D"font-size: 14pt; font-family: 'Times New Roman', serif;=
">Re: [sfc] draft-quinn-sfc-nsh: version number</span><b><span lang=3D"EN-U=
S" style=3D"font-size: 24pt; font-family: 'Times New Roman', serif;"><o:p><=
/o:p></span></b></h1>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 lang=3D"EN-US">
<hr size=3D"2" width=3D"100%" align=3D"center">
</span></div>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto;mso-list:l0 level1 lfo1">
<em><span lang=3D"EN-US" style=3D"font-family: Calibri, sans-serif;">From</=
span></em><span lang=3D"EN-US" style=3D"mso-fareast-language:EN-US">: &quot=
;Paul Quinn (paulq)&quot; &lt;<a href=3D"mailto:paulq@DOMAIN.HIDDEN">paulq =
at cisco.com</a>&gt;<o:p></o:p></span></li><li class=3D"MsoNormal" style=3D=
"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1=
">
<em><span lang=3D"EN-US" style=3D"font-family: Calibri, sans-serif;">To</sp=
an></em><span lang=3D"EN-US" style=3D"mso-fareast-language:EN-US">: &quot;J=
oel M. Halpern&quot; &lt;<a href=3D"mailto:jmh@DOMAIN.HIDDEN">jmh at joelha=
lpern.com</a>&gt;<o:p></o:p></span></li><li class=3D"MsoNormal" style=3D"ms=
o-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<em><span lang=3D"EN-US" style=3D"font-family: Calibri, sans-serif;">Cc</sp=
an></em><span lang=3D"EN-US" style=3D"mso-fareast-language:EN-US">: &quot;<=
a href=3D"mailto:mohamed.boucadair@DOMAIN.HIDDEN">mohamed.boucadair at oran=
ge.com</a>&quot; &lt;<a href=3D"mailto:mohamed.boucadair@DOMAIN.HIDDEN">moh=
amed.boucadair
 at orange.com</a>&gt;, &quot;<a href=3D"mailto:sfc@DOMAIN.HIDDEN">sfc at i=
etf.org</a>&quot; &lt;<a href=3D"mailto:sfc@DOMAIN.HIDDEN">sfc at ietf.org<=
/a>&gt;<o:p></o:p></span></li><li class=3D"MsoNormal" style=3D"mso-margin-t=
op-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<em><span lang=3D"EN-US" style=3D"font-family: Calibri, sans-serif;">Date</=
span></em><span lang=3D"EN-US" style=3D"mso-fareast-language:EN-US">: Mon, =
2 Mar 2015 17:50:53 &#43;0000<o:p></o:p></span></li><li class=3D"MsoNormal"=
 style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 le=
vel1 lfo1">
<em><span lang=3D"EN-US" style=3D"font-family: Calibri, sans-serif;">In-rep=
ly-to</span></em><span lang=3D"EN-US" style=3D"mso-fareast-language:EN-US">=
: &lt;<a href=3D"http://www.ietf.org/mail-archive/web/sfc/current/msg03181.=
html">54EF2C9A.3040008@joelhalpern.com</a>&gt;<o:p></o:p></span></li><li cl=
ass=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:au=
to;mso-list:l0 level1 lfo1">
<em><span lang=3D"EN-US" style=3D"font-family: Calibri, sans-serif;">Refere=
nces</span></em><span lang=3D"EN-US" style=3D"mso-fareast-language:EN-US">:=
 &lt;<a href=3D"mailto:787AE7BB302AE849A7480A190F8B9330049140B4@OPEXCLILM23=
.corporate.adroot.infra.ftgroup">787AE7BB302AE849A7480A190F8B9330049140B4@O=
PEXCLILM23.corporate.adroot.infra.ftgroup</a>&gt;
 &lt;<a href=3D"http://www.ietf.org/mail-archive/web/sfc/current/msg03151.h=
tml">54EDE5B7.6080102@joelhalpern.com</a>&gt; &lt;<a href=3D"mailto:787AE7B=
B302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.adroot.infra.ftgrou=
p">787AE7BB302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.adroot.in=
fra.ftgroup</a>&gt;
 &lt;<a href=3D"http://www.ietf.org/mail-archive/web/sfc/current/msg03181.h=
tml">54EF2C9A.3040008@joelhalpern.com</a>&gt;<o:p></o:p></span></li><li cla=
ss=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:aut=
o;mso-list:l0 level1 lfo1">
<em><span lang=3D"EN-US" style=3D"font-family: Calibri, sans-serif;">List-i=
d</span></em><span lang=3D"EN-US" style=3D"mso-fareast-language:EN-US">: Ne=
twork Service Chaining &lt;sfc.ietf.org&gt;<o:p></o:p></span></li></ul>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 lang=3D"EN-US">
<hr size=3D"2" width=3D"100%" align=3D"center">
</span></div>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">Hi,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&nbsp;<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">Jumping in mid-thread.&nbsp; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&nbsp;<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">Overall, I tend to agree with Joel.&nbsp; Having an explicit version =
provides a simple way to handle dataplane format changes.&nbsp; As Med poin=
ts out, quickly correctly, IMHO, there are other way to signal changes via =
reserved bit.&nbsp; In practice though reserved bits are less useful since =
the convention is to ignore unknown bits, it makes using them for feature c=
hanges quite difficult, which then brings up back to explicit versioning th=
at cannot be ignored.&nbsp; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&nbsp;<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">I think Joel=92s suggestion below makes perfect sense and should be a=
dded to the draft.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&nbsp;<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">Paul<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&nbsp;<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&nbsp;<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt; On Feb 26, 2015, at 9:24 AM, Joel M. Halpern &lt;jmh at joelhalp=
ern.com&gt; wrote:<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt; In one sense you are correct.&nbsp; If you could count on everyt=
hing being upgraded at once, sure you could just assume common interpretati=
on.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt; However, we have found over the years that such simultaneous upg=
rading never works.&nbsp; You need to be able to transition.<o:p></o:p></sp=
an></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt; I do agree that we should add text about what to do with version=
 numbers that are not understood.&nbsp; There are multiple choices that aff=
ect how we can make changes.&nbsp; My personal preference is:<o:p></o:p></s=
pan></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt; If an packet presumed to carry an NSH header is received at an S=
FF, and the SFF does not understnad the version of the protocol as indicate=
d in the base header, the packet MUST be discarded, and the event SHOULD be=
 logged.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt; This would allow an orderly transition, where devices can be upg=
raded to understand a new version, then generation of the new version heade=
r can be enabled.&nbsp; If a configuration error is made, the packets will =
be dropped and operators following good practices will get notifications.<o=
:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt; Yours,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt; Joel<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt; On 2/26/15 2:16 AM, mohamed.boucadair at orange.com wrote:<o:p><=
/o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; Hi Joel,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; I fully agree with the extendibility of the header, but the =
question is why having a version number will be of help in the context of S=
FC? Second, having a version number without specifying the behavior when se=
veral versions are supported, when the version number is not supported by a=
n SFC-aware element, etc. leaves open issues out of the spec.<o:p></o:p></s=
pan></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; The other problem is that the current I-D includes several o=
pen doors left for extending the header:<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; * version<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; * reserved bits<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; * optional data<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; This is too much for a header that is supposed to be compact=
 and simple!<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; There are other means to extend the header without signaling=
 the version in the packet. Having a distinct RFC number may be just fine i=
n the context of an unidirectional stream such as SFC.<o:p></o:p></span></p=
re>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; Let us consider the situation where a version number is not =
explicitly signaled in the packet (but a new RFC updates the base SFC heade=
r). Several options can be considered, indeed (those are provided as exampl=
es for illustration purposes):<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; * An operator can make sure that its SFC-enabled domain is c=
onfigured in a consistent manner to support one and only one version of the=
 header. No interoperability issues is encountered in this case.<o:p></o:p>=
</span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; * An operator that wants to upgrade its SFC-enabled domain t=
o support a new specification of the SFC header: An operator can decide to =
proceed to a software/hardware updates but can maintain the old header in o=
peration until all involved elements are upgraded to support the new versio=
n. Once the SFC-enabled domain is upgraded, then the new header can be enab=
led.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; Let's consider now that a version is signaled in the packet:=
 to what extent signaling this information simplifies the SFC operations, a=
nd whether it increases/decreases the serviceability of an SFC-enabled doma=
in? Let's also assess to what extent having the version number add more com=
plexity in the SFC header treatment when several versions are supported by =
a node/within an SFC enabled domain? How it helps interoperability? Some po=
ints for discussion are elaborated below:<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; * If the SFC-enabled domain is configured to support the sam=
e version (which is likely): having the version number is not of any help.<=
o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; * If the SFC-enabled domain involves some nodes that support=
 version (v1) while others support (v2) (simple case): If these version are=
 not backward compatible, this will lead to failures when two adjacent elem=
ents in a service chain do not support the same version. The SFC system is =
broken. Having the version number is not of any help in this case.<o:p></o:=
p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; * If the SFC-enabled domain involves some nodes that support=
 version (v1) while others support (v1 and v2):<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; (a) The nodes that support both v1 and v2 should be instruct=
ed to decide which version to be used. This can be either part of the speci=
fication or be driven by configuration. If a version number is included in =
the spec, I would expect to clarify the behavior in such case.<o:p></o:p></=
span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; (b) Suppose a node that supports only v1 receives a packet w=
ith header (v2): If this node does not support a notification procedure to =
inform the source that it does not support that header version, then FAILUR=
ES are introduced in the network. This is a degradation of the service comp=
ared to legacy scheme to structure services. This is not recommended, IMHO.=
<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; (c) If a notification is received from an element about its =
supported version: a node can use another version (the logic to select othe=
r version is another point to discuss) for that communication, but what to =
do for the next flows in the context of the same service chain or other cha=
ins that involves these two nodes as adjacent elements in the same chain? S=
houldn't these nodes cache the version to use for subsequent exchange to av=
oid receiving the notification error each time? Wouldn't that complexity th=
e behavior of the SFC-aware elements?<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; (d) If a notification is received from an element about its =
supported version: As this may occurs in various segments of a given servic=
e chain, e.g., (A(v1), B(v1,v2), C(v2), D(v1,v2), E(v1)). Notifying the adj=
acent node each time there is a version mismatch induce an extra delay, tha=
t may be not be acceptable for every flow.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; I hope this clarifies my initial concern.<o:p></o:p></span><=
/pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; Thank you.<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; Cheers,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; Med<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt; -----Message d'origine-----<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt; De : Joel M. Halpern [<a href=3D"mailto:jmh">mailto:jmh<=
/a> at joelhalpern.com]<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt; Envoy=E9 : mercredi 25 f=E9vrier 2015 16:10<o:p></o:p></=
span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt; =C0 : BOUCADAIR Mohamed IMT/OLN; paulq at cisco.com<o:p>=
</o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt; Cc : sfc at ietf.org<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt; Objet : Re: [sfc] draft-quinn-sfc-nsh: version number<o:=
p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt; I would really prefer to keep the version number.&nbsp; =
Even though we have<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt; the MD-type identifier and for some MD we have the TLVs.=
<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt; The reason is that we may want to change the base header=
.&nbsp; For example,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt; suppose that the ciscussion about including a flow ident=
ifier in the<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt; base header had not come up now.&nbsp; If it came up lat=
er, we would want to<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt; be able to have the discussion and make the choice, rath=
er than being<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt; constrained by the lack of a version field.<o:p></o:p></=
span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt; Yours,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt; Joel<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt; On 2/25/15 10:03 AM, mohamed.boucadair at orange.com wro=
te:<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt;&gt; Hi Paul, all,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt;&gt; What is the purpose of having a version number in th=
e header? Is there a<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt;&gt; kind of version negotiation that needs to be in plac=
e?<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt;&gt; I checked the I-D but failed to find text that expla=
ins the rationale,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt;&gt; the use of the such field and whether an error will =
be returned if the<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt;&gt; version is not supported by the receiving node.<o:p>=
</o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt;&gt; Wouldn't be preferable to get rid of this field give=
n that SFC header<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt;&gt; can be extended using optional objects and consisten=
t setup &amp;<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt;&gt; configuration within an SFC-enabled domain should be=
 assumed?<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt;&gt; Thank you<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt;&gt; Cheers,<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt;&gt; Med<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt;&gt; _______________________________________________<o:p>=
</o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt;&gt; sfc mailing list<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt;&gt; sfc at ietf.org<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/sfc=
">https://www.ietf.org/mailman/listinfo/sfc</a><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt;&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&gt;&gt; <o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: 'Courier N=
ew';">&nbsp;<o:p></o:p></span></pre>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_D11DBC7019374smkumarciscocom_--


From nobody Thu Mar  5 16:49:03 2015
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5C561A90A3; Thu,  5 Mar 2015 16:49:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 jShKReflGnTP; Thu,  5 Mar 2015 16:48:59 -0800 (PST)
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 347C01A909C; Thu,  5 Mar 2015 16:48:58 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BPY11093; Fri, 06 Mar 2015 00:48:56 +0000 (GMT)
Received: from NKGEML406-HUB.china.huawei.com (10.98.56.37) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 6 Mar 2015 00:48:55 +0000
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.115]) by nkgeml406-hub.china.huawei.com ([10.98.56.37]) with mapi id 14.03.0158.001; Fri, 6 Mar 2015 08:48:48 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: "Jim Guichard (jguichar)" <jguichar@cisco.com>, Ron Parker <Ron_Parker@affirmednetworks.com>
Thread-Topic: [sfc] New Version Notification for draft-xu-sfc-using-mpls-spring-02.txt
Thread-Index: AQHQV1aYsfxG7/vV/kuy6NqPt9ZGW50On1Jw
Date: Fri, 6 Mar 2015 00:48:47 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08310605@NKGEML512-MBS.china.huawei.com>
References: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0830F7C0@NKGEML512-MBS.china.huawei.com> <CDF2F015F4429F458815ED2A6C2B6B0B2E855978@MBX021-W3-CA-2.exch021.domain.local> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0830FC8E@NKGEML512-MBS.china.huawei.com> <34ECE28B-F7AB-4FB9-9CE1-06289FB739B4@affirmednetworks.com> <D11DD3D6.BD0C%jguichar@cisco.com>
In-Reply-To: <D11DD3D6.BD0C%jguichar@cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.99.55]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/oU-NxqAipD4qYv1r_SYYpLds6Jo>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "<spring@ietf.org>" <spring@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] New Version Notification for draft-xu-sfc-using-mpls-spring-02.txt
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 06 Mar 2015 00:49:02 -0000

Hi Jim,

Understood.

Best regards,
Xiaohu

> -----Original Message-----
> From: Jim Guichard (jguichar) [mailto:jguichar@cisco.com]
> Sent: Thursday, March 05, 2015 11:11 PM
> To: Ron Parker; Xuxiaohu
> Cc: mpls@ietf.org; <spring@ietf.org>; sfc@ietf.org
> Subject: Re: [sfc] New Version Notification for
> draft-xu-sfc-using-mpls-spring-02.txt
>=20
> Hi Xiaohu,
>=20
> Thomas and I read your latest draft and believe that you will need to tak=
e it to
> the MPLS WG as a first step. There are a number of things within the docu=
ment
> that may require changes to the base MPLS architecture and the SFC WG is =
not
> the right community to address those. Given this we will not be able to c=
onsider
> this document in the SFC WG without agreement from the broader MPLS
> community.
>=20
> Regards,
>=20
> Jim & Thomas
>=20
>=20
> On 3/4/15, 9:20 PM, "Ron Parker" <Ron_Parker@affirmednetworks.com>
> wrote:
>=20
> >I think it needs to be there between SFF's, too.  In the case where
> >there is no metadata, you could argue that the data in NSH and the
> >label stack are redundantly saying the same thing, but an optimization
> >along these lines would not be justified, IMO.
> >
> >   Ron
> >
> >
> >> On Mar 4, 2015, at 8:58 PM, Xuxiaohu <xuxiaohu@huawei.com> wrote:
> >>
> >> Hi Ron,
> >>
> >> Thanks a lot for your insightful comments and suggestions. By the
> >>way, in the case where there is no need to deliver metadata, does it
> >>mean the NSH just only needs to be contained the packets exchanged
> >>between SFFs and SFs? In other words, the NSH is used as a way for the
> >>SFF to retrieve the label stack which has been stripped by that SFF bef=
ore.
> >>
> >> Best regards,
> >> Xiaohu
> >>
> >>> -----Original Message-----
> >>> From: Ron Parker [mailto:Ron_Parker@affirmednetworks.com]
> >>> Sent: Thursday, March 05, 2015 12:41 AM
> >>> To: Xuxiaohu; sfc@ietf.org; <spring@ietf.org>; mpls@ietf.org
> >>> Subject: RE: [sfc] New Version Notification for
> >>> draft-xu-sfc-using-mpls-spring-02.txt
> >>>
> >>> Xiaohu,
> >>>
> >>> I read your latest draft and I do see the elegance of describing a
> >>>sequence of
> >>> must-visit nodes as a stack of MPLS labels.   And I see that you've
> >>>addressed
> >>> the transport-independence requirement by stating that the MPLS
> >>>frames could
> >>> be carried within IP tunnels (i.e., MPLS in UDP, etc.).    But, I hav=
e
> >>>a couple of
> >>> issues that I suggest be addressed.
> >>>
> >>> First, the text is written as if the NSH header is optional and
> >>>present only if
> >>> metadata is required.    The SFC architecture is such that the NSH is
> >>> mandatory.   I think this issue can be combined with the second issue
> >>>that I'll
> >>> raise below.
> >>>
> >>> Second, the notion is that the SFF's strip the label stack and then
> >>>restore the
> >>> label stack.    And since the text states that even when NSH is
> >>>present, the SFP
> >>> ID is not used, the only remaining basis to do this is flow learning
> >>>in the SFF.
> >>> While I think there are many reasons that may cause SFF's to utilize
> >>>flow  learning advantageously, it should not be a fundamental
> >>>necessity to realize an
> >>> SFF, IMO.   But even if the SFF is a flow learner, this is still
> >>>inadequate since the
> >>> SF may change the 5-tuple (e.g., NAT) or may launch internally
> >>>generated flows
> >>> (e.g., HTTP proxy).   Both cases could not be satisfied by flow
> >>>learning.
> >>>
> >>> What I suggest, instead, is a tighter coupling between the NSH
> >>>header and the
> >>> MPLS label stack.   That there be a 1:1 equivalency between {SFP ID,
> >>>SFP hop
> >>> index} and the label stack.   Thus, when the SFC-aware SF returns a
> >>>packet to
> >>> the SFF, the {SFP ID, SFP hop index} contained in the NSH be used to
> >>>push the
> >>> appropriate label stack onto the packet.    I believe this would brin=
g
> >>>the
> >>> approach into conformance with the SFC architectural requirements
> >>>(mandatory NSH, transport independence) and would solve the problems
> >>>with  flow learning identified above.
> >>>
> >>>   Ron
> >>>
> >>>
> >>>
> >>> -----Original Message-----
> >>> From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of Xuxiaohu
> >>> Sent: Tuesday, March 3, 2015 11:10 PM
> >>> To: Xuxiaohu; sfc@ietf.org; <spring@ietf.org>; mpls@ietf.org
> >>> Subject: Re: [sfc] New Version Notification for
> >>> draft-xu-sfc-using-mpls-spring-02.txt
> >>>
> >>> The rationales for leveraging the MPLS-SPRING mechanism to realize
> >>>the service  path layer functionality of the service function
> >>>chaining are as
> >>>follows:
> >>>
> >>> 1) eliminate the SFC/SFP states on SFFs. This follows the same logic
> >>>as  MPLS-SPRING and BIER.
> >>> 2) utilize the existing encapsulation (e.g., the MPLS-SPRING) to a
> >>>maximum  extent. This follows the Transport Derived SFF concept as
> >>>described in Section
> >>> 4.3.1 of draft-ietf-sfc-architecture. Meanwhile, this is aligned
> >>>with the current  SFC charter, e.g., "...The working group will
> >>>consider using an existing  encapsulation (with extensions as
> >>>appropriate) if a suitable candidate is found..."
> >>> 3) seamlessly support the SFC in a multi-tenant environment (e.g.,
> >>>MPLS VPN).
> >>> For example, the MPLS VPN packet (containing metadata) could be
> >>>further  imposed with a label stack which indicates an SFC or SFP
> >>>associated with that  packet. SFFs receiving the above packet would
> >>>strip the whole label stack and  then send the payload of the MPLS
> >>>packet (with metadata) to the corresponding  SFs which are
> >>>tenant-aware and therefore easily could determine the tenant  profile
> >>>according to the tenant info contained in the metadata (a.k.a., the
> >>>NSH).
> >>>
> >>> Best regards,
> >>> Xiaohu
> >>>
> >>>
> >>>> -----Original Message-----
> >>>> From: Xuxiaohu
> >>>> Sent: Wednesday, March 04, 2015 11:31 AM
> >>>> To: sfc@ietf.org; '<spring@ietf.org>'; mpls@ietf.org
> >>>> Subject: FW: New Version Notification for
> >>>> draft-xu-sfc-using-mpls-spring-02.txt
> >>>>
> >>>> Hi all,
> >>>>
> >>>> This document describes how to leverage the MPLS-based source
> >>>> routing (i.e.,
> >>>> MPLS-SPRING) mechanism as developed by the SPRING WG to realize the
> >>>> service path layer functionality of the service function chaining.
> >>>> In addition, this document also describes how to carry metadata in
> >>>> an MPLS packet by using the NSH as a metadata container.
> >>>>
> >>>> Any comments are suggestions are welcome.
> >>>>
> >>>> Best regards,
> >>>> Xiaohu
> >>>>
> >>>>> -----Original Message-----
> >>>>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> >>>>> Sent: Wednesday, March 04, 2015 11:24 AM
> >>>>> To: Lizhenbin; Luis M. Contreras; Xuxiaohu; Himanshu C. Shah;
> >>>>> Xuxiaohu; Himanshu Shah; Luis M. Contreras; Lizhenbin
> >>>>> Subject: New Version Notification for
> >>>>> draft-xu-sfc-using-mpls-spring-02.txt
> >>>>>
> >>>>>
> >>>>> A new version of I-D, draft-xu-sfc-using-mpls-spring-02.txt
> >>>>> has been successfully submitted by Xiaohu Xu and posted to the
> >>>>> IETF
> >>>> repository.
> >>>>>
> >>>>> Name:        draft-xu-sfc-using-mpls-spring
> >>>>> Revision:    02
> >>>>> Title:        Service Function Chaining Using MPLS-SPRING
> >>>>> Document date:    2015-03-03
> >>>>> Group:        Individual Submission
> >>>>> Pages:        8
> >>>>> URL:
> >>>>>
> >>>>>http://www.ietf.org/internet-drafts/draft-xu-sfc-using-mpls-spring-0=
2.
> >>>>> txt
> >>>>> Status:
> >>>>> https://datatracker.ietf.org/doc/draft-xu-sfc-using-mpls-spring/
> >>>>> Htmlized:
> >>> http://tools.ietf.org/html/draft-xu-sfc-using-mpls-spring-02
> >>>>> Diff:
> >>>>> http://www.ietf.org/rfcdiff?url2=3Ddraft-xu-sfc-using-mpls-spring-0=
2
> >>>>>
> >>>>> Abstract:
> >>>>>   Source Packet Routing in Networking (SPRING) WG specifies a speci=
al
> >>>>>   source routing mechanism.  Such source routing mechanism can be
> >>>>>   leveraged to realize the service path layer functionality of the
> >>>>>   service function chaining (i.e, steering traffic through a
> >>>>>particular
> >>>>>   service function path) by encoding the service function path or t=
he
> >>>>>   service function chain information as the explicit path
> >>>>>information.
> >>>>>   This document describes how to leverage the MPLS-based source
> >>> routing
> >>>>>   mechanism as developed by the SPRING WG to realize the service
> path
> >>>>>   layer functionality of the service function chaining.
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> Please note that it may take a couple of minutes from the time of
> >>>>>submission until the htmlized version and diff are available at
> >>>>>tools.ietf.org.
> >>>>>
> >>>>> The IETF Secretariat
> >>>
> >>> _______________________________________________
> >>> sfc mailing list
> >>> sfc@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/sfc
> >
> >_______________________________________________
> >sfc mailing list
> >sfc@ietf.org
> >https://www.ietf.org/mailman/listinfo/sfc


From nobody Thu Mar  5 23:15:33 2015
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30D2D1ACCFC for <sfc@ietfa.amsl.com>; Thu,  5 Mar 2015 23:15:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 Nk49Y3xKP2L5 for <sfc@ietfa.amsl.com>; Thu,  5 Mar 2015 23:15:28 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2372B1ACCFB for <sfc@ietf.org>; Thu,  5 Mar 2015 23:15:27 -0800 (PST)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id 0169E324507; Fri,  6 Mar 2015 08:15:26 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.5]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id C90E14C0FB; Fri,  6 Mar 2015 08:15:25 +0100 (CET)
Received: from OPEXCLILM23.corporate.adroot.infra.ftgroup ([169.254.2.181]) by OPEXCLILH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0224.002; Fri, 6 Mar 2015 08:15:25 +0100
From: <mohamed.boucadair@orange.com>
To: Ron Parker <Ron_Parker@affirmednetworks.com>, "Paul Quinn (paulq)" <paulq@cisco.com>
Thread-Topic: [sfc] draft-quinn-sfc-nsh: version number
Thread-Index: AQHQVpZWlsbbenTwMkmQOaMIFOQDuZ0N+TeA///3w4CAARfY8A==
Date: Fri, 6 Mar 2015 07:15:25 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933004926879@OPEXCLILM23.corporate.adroot.infra.ftgroup>
References: <01f9e1a4e6514854a26556e4c6a3e36e@SEAEXCHMBX05.olympus.F5Net.com> <787AE7BB302AE849A7480A190F8B933004919B76@OPEXCLILM23.corporate.adroot.infra.ftgroup> <CDF2F015F4429F458815ED2A6C2B6B0B2E85379B@MBX021-W3-CA-2.exch021.domain.local> <787AE7BB302AE849A7480A190F8B93300491A1AF@OPEXCLILM23.corporate.adroot.infra.ftgroup> <CDF2F015F4429F458815ED2A6C2B6B0B2E8558D0@MBX021-W3-CA-2.exch021.domain.local> <787AE7BB302AE849A7480A190F8B93300491A1F7@OPEXCLILM23.corporate.adroot.infra.ftgroup> <08AFD2FB-AC81-479A-9098-0FFEDDBF0A58@cisco.com> <787AE7BB302AE849A7480A190F8B933004922B46@OPEXCLILM23.corporate.adroot.infra.ftgroup> <CDF2F015F4429F458815ED2A6C2B6B0B2E85A202@MBX021-W3-CA-2.exch021.domain.local>
In-Reply-To: <CDF2F015F4429F458815ED2A6C2B6B0B2E85A202@MBX021-W3-CA-2.exch021.domain.local>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.5]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B933004926879OPEXCLILM23corp_"
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.3.6.54820
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/P1Se6xSxbmNbBUNuKaSzYDu3a00>
Cc: Sunil Vallamkonda <sunilvk@f5.com>, "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] draft-quinn-sfc-nsh: version number
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 06 Mar 2015 07:15:32 -0000

--_000_787AE7BB302AE849A7480A190F8B933004926879OPEXCLILM23corp_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Ron,

Thank you for this clarification.


I would buy the argument if inserting some contexts was mandatory, but this=
 is not the case. Moreover, I don't understand from the draft what is the r=
ationale for classifying the context into these four categories. What is me=
ant by "platform-specific metadata" or "service platform specific"?

My personal point of view is that we need to choose. I'm personally for a m=
inimalist header. Leaving both induces more complexity.

FWIW, this thread http://www.ietf.org/mail-archive/web/sfc/current/msg03150=
.html can be used for MD type related discussions.

Cheers,
Med

De : Ron Parker [mailto:Ron_Parker@affirmednetworks.com]
Envoy=E9 : jeudi 5 mars 2015 15:21
=C0 : BOUCADAIR Mohamed IMT/OLN; Paul Quinn (paulq)
Cc : Sunil Vallamkonda; sfc@ietf.org
Objet : RE: [sfc] draft-quinn-sfc-nsh: version number

Med,

Albeit, from a co-author's perspective, the MD type, as I see it, is the cu=
rrent grand compromise, attempting to balance ease of parsing (MD type 1) a=
nd unconstrained flexibility (MD type 2).

   Ron



From: mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com> [ma=
ilto:mohamed.boucadair@orange.com]
Sent: Thursday, March 5, 2015 1:47 AM
To: Paul Quinn (paulq)
Cc: Ron Parker; Sunil Vallamkonda; sfc@ietf.org<mailto:sfc@ietf.org>
Subject: RE: [sfc] draft-quinn-sfc-nsh: version number

Hi Paul,

Glad to see that we are sharing the same objective to design simple things,=
 but the design should not cause another yet set of failure cases (which is=
 the case of the current spec: the non-support of the MD type will be a cau=
se of failure too).

I already provided a long message with my thoughts (http://www.ietf.org/mai=
l-archive/web/sfc/current/msg03175.html).

I can propose text, but we need to agree first. I'm still questioning the n=
eed to have the version field in addition to other fields such as MD type.

I hope to see more feedback from the WG participants other than the authors=
 of the draft so that I can adjust the proposed text.

Cheers,
Med

De : Paul Quinn (paulq) [mailto:paulq@cisco.com]
Envoy=E9 : mercredi 4 mars 2015 17:15
=C0 : BOUCADAIR Mohamed IMT/OLN
Cc : Ron Parker; Sunil Vallamkonda; sfc@ietf.org<mailto:sfc@ietf.org>
Objet : Re: [sfc] draft-quinn-sfc-nsh: version number


On Mar 4, 2015, at 11:09 AM, mohamed.boucadair@orange.com<mailto:mohamed.bo=
ucadair@orange.com> wrote:

Re-,

That would be a good start, but still not sufficient IMHO.

If no notification is sent back (which can be the case with the MAY languag=
e), the failure will be experienced till an action is done by the domain op=
erator. This is not desirable.

Having a more strong language for sending back the response (that needs to =
include at least the received packet with the unsupported version) will hav=
e the effect to resend the packet with an adequate version (if multiple ver=
sions are supported). The exact behavior when a version mismatch error is r=
eceived should be explicated in the document IMO.

Perhaps the best way forward: can you please suggest some text that we can =
all review?  I'm inclined to keep things simple (i.e. simple error message =
of sorts) but since you've given this a lot of thought, I'd love to see you=
r suggestions.



--_000_787AE7BB302AE849A7480A190F8B933004926879OPEXCLILM23corp_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Cambria;
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"Segoe UI";
	panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
h1
	{mso-style-priority:9;
	mso-style-link:"Titre 1 Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	font-weight:normal;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Texte brut Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"Pr=E9format=E9 HTML Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Texte de bulles Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.Titre1Car
	{mso-style-name:"Titre 1 Car";
	mso-style-priority:9;
	mso-style-link:"Titre 1";
	font-family:"Cambria","serif";
	color:#365F91;
	font-weight:bold;}
span.PrformatHTMLCar
	{mso-style-name:"Pr=E9format=E9 HTML Car";
	mso-style-priority:99;
	mso-style-link:"Pr=E9format=E9 HTML";
	font-family:Consolas;}
span.TextebrutCar
	{mso-style-name:"Texte brut Car";
	mso-style-priority:99;
	mso-style-link:"Texte brut";
	font-family:"Courier New";
	color:black;
	mso-fareast-language:EN-US;}
span.TextedebullesCar
	{mso-style-name:"Texte de bulles Car";
	mso-style-priority:99;
	mso-style-link:"Texte de bulles";
	font-family:"Tahoma","sans-serif";}
p.Heading1, li.Heading1, div.Heading1
	{mso-style-name:"Heading 1";
	mso-style-link:"Heading 1 Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.Heading1Char
	{mso-style-name:"Heading 1 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 1";
	font-family:"Times New Roman","serif";
	font-weight:bold;}
p.HTMLPreformatted, li.HTMLPreformatted, div.HTMLPreformatted
	{mso-style-name:"HTML Preformatted";
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
p.PlainText, li.PlainText, div.PlainText
	{mso-style-name:"Plain Text";
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
p.BalloonText, li.BalloonText, div.BalloonText
	{mso-style-name:"Balloon Text";
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Segoe UI","sans-serif";}
span.EmailStyle32
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle33
	{mso-style-type:personal;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;}
span.EmailStyle34
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle35
	{mso-style-type:personal;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;}
span.EmailStyle36
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle37
	{mso-style-type:personal;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;}
span.EmailStyle38
	{mso-style-type:personal;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;}
span.EmailStyle39
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle40
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"FR" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Hi Ron,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Thank you for this clarificatio=
n.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">I would buy the argument if inserting some contex=
ts was mandatory, but this is not the case. Moreover, I don&#8217;t underst=
and from the draft what is the rationale for classifying the context into t=
hese four categories. What is meant by &#8220;</span><span lang=3D"EN-US" s=
tyle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">platform-spec=
ific metadata</span><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-fam=
ily:&quot;Courier New&quot;;color:black">&#8221; or &#8220;</span><span lan=
g=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">=
service platform specific</span><span lang=3D"EN-US" style=3D"font-size:10.=
0pt;font-family:&quot;Courier New&quot;;color:black">&#8221;?<o:p></o:p></s=
pan></pre>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">My personal point of view is th=
at we need to choose. I&#8217;m personally for a minimalist header. Leaving=
 both induces more complexity.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">FWIW, this thread
<a href=3D"http://www.ietf.org/mail-archive/web/sfc/current/msg03150.html">=
http://www.ietf.org/mail-archive/web/sfc/current/msg03150.html</a> can be u=
sed for MD type related discussions.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Cheers,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Med<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">De&nbsp;:</span></b><span style=3D"fo=
nt-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Ron =
Parker [mailto:Ron_Parker@affirmednetworks.com]
<br>
<b>Envoy=E9&nbsp;:</b> jeudi 5 mars 2015 15:21<br>
<b>=C0&nbsp;:</b> BOUCADAIR Mohamed IMT/OLN; Paul Quinn (paulq)<br>
<b>Cc&nbsp;:</b> Sunil Vallamkonda; sfc@ietf.org<br>
<b>Objet&nbsp;:</b> RE: [sfc] draft-quinn-sfc-nsh: version number<o:p></o:p=
></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Med,<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Albeit,=
 from a co-author&#8217;s perspective, the MD type, as I see it, is the cur=
rent grand compromise, attempting to balance ease of parsing (MD type 1) an=
d unconstrained flexibility (MD type 2).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp; Ron<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><a name=3D"_MailEndCompose"></a><span lang=3D"EN-US"=
 style=3D"color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US">From:</span></b><span lang=
=3D"EN-US"> <a href=3D"mailto:mohamed.boucadair@orange.com">
mohamed.boucadair@orange.com</a> [<a href=3D"mailto:mohamed.boucadair@orang=
e.com">mailto:mohamed.boucadair@orange.com</a>]
<br>
<b>Sent:</b> Thursday, March 5, 2015 1:47 AM<br>
<b>To:</b> Paul Quinn (paulq)<br>
<b>Cc:</b> Ron Parker; Sunil Vallamkonda; <a href=3D"mailto:sfc@ietf.org">s=
fc@ietf.org</a><br>
<b>Subject:</b> RE: [sfc] draft-quinn-sfc-nsh: version number<o:p></o:p></s=
pan></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Hi Paul,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Glad to see that we are sharing=
 the same objective to design simple things, but the design should not caus=
e another yet set of failure cases (which is the
 case of the current spec: the non-support of the MD type will be a cause o=
f failure too).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">I already provided a long messa=
ge with my thoughts (<a href=3D"http://www.ietf.org/mail-archive/web/sfc/cu=
rrent/msg03175.html">http://www.ietf.org/mail-archive/web/sfc/current/msg03=
175.html</a>).
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">I can propose text, but we need=
 to agree first. I&#8217;m still questioning the need to have the version f=
ield in addition to other fields such as MD type.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">I hope to see more feedback fro=
m the WG participants other than the authors of the draft so that I can adj=
ust the proposed text.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Cheers,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Med<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">De&nbsp;:</span></b><span style=3D"fo=
nt-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Paul=
 Quinn (paulq) [<a href=3D"mailto:paulq@cisco.com">mailto:paulq@cisco.com</=
a>]
<br>
<b>Envoy=E9&nbsp;:</b> mercredi 4 mars 2015 17:15<br>
<b>=C0&nbsp;:</b> BOUCADAIR Mohamed IMT/OLN<br>
<b>Cc&nbsp;:</b> Ron Parker; Sunil Vallamkonda; <a href=3D"mailto:sfc@ietf.=
org">sfc@ietf.org</a><br>
<b>Objet&nbsp;:</b> Re: [sfc] draft-quinn-sfc-nsh: version number<o:p></o:p=
></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">On Mar 4, 2015, at 11:09 AM, <a href=3D"mailto:moham=
ed.boucadair@orange.com">
mohamed.boucadair@orange.com</a> wrote:<o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Re-,</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;">That would be a good start, but still not s=
ufficient IMHO.</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;">If no notification is sent back (which can =
be the case with the MAY language), the failure will be experienced till an=
 action is done by the domain operator. This is
 not desirable. </span><o:p></o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;">Having a more strong language for sending b=
ack the response (that needs to include at least the received packet with t=
he unsupported version) will have the effect to
 resend the packet with an adequate version (if multiple versions are suppo=
rted). The exact behavior when a version mismatch error is received should =
be explicated in the document IMO.
</span><o:p></o:p></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;">Perhaps the best way forward: can yo=
u please suggest some text that we can all review? &nbsp;I&#8217;m inclined=
 to keep things simple (i.e. simple error message of sorts) but since
 you&#8217;ve given this a lot of thought, I&#8217;d love to see your sugge=
stions.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_787AE7BB302AE849A7480A190F8B933004926879OPEXCLILM23corp_--


From nobody Thu Mar  5 23:28:37 2015
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90E831ACD05 for <sfc@ietfa.amsl.com>; Thu,  5 Mar 2015 23:28:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 HK9sHCm5HGUL for <sfc@ietfa.amsl.com>; Thu,  5 Mar 2015 23:28:25 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias243.francetelecom.com [80.12.204.243]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B352D1ACCFD for <sfc@ietf.org>; Thu,  5 Mar 2015 23:28:24 -0800 (PST)
Received: from omfeda05.si.francetelecom.fr (unknown [xx.xx.xx.198]) by omfeda09.si.francetelecom.fr (ESMTP service) with ESMTP id CFACEC07E0; Fri,  6 Mar 2015 08:28:22 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.16]) by omfeda05.si.francetelecom.fr (ESMTP service) with ESMTP id A5507180054; Fri,  6 Mar 2015 08:28:22 +0100 (CET)
Received: from OPEXCLILM23.corporate.adroot.infra.ftgroup ([169.254.2.181]) by OPEXCLILH05.corporate.adroot.infra.ftgroup ([10.114.31.16]) with mapi id 14.03.0224.002; Fri, 6 Mar 2015 08:28:22 +0100
From: <mohamed.boucadair@orange.com>
To: "Surendra Kumar (smkumar)" <smkumar@cisco.com>
Thread-Topic: [sfc] draft-quinn-sfc-nsh: version number
Thread-Index: AQHQV4FelsbbenTwMkmQOaMIFOQDuZ0PDf1w
Date: Fri, 6 Mar 2015 07:28:21 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933004926895@OPEXCLILM23.corporate.adroot.infra.ftgroup>
References: <D11DBC70.19374%smkumar@cisco.com>
In-Reply-To: <D11DBC70.19374%smkumar@cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.5]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B933004926895OPEXCLILM23corp_"
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.3.6.60618
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/iXbO00HM1xlf5RN_aWDG-NLJ69A>
Cc: Sunil Vallamkonda <sunilvk@f5.com>, Ron Parker <Ron_Parker@affirmednetworks.com>, "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] draft-quinn-sfc-nsh: version number
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 06 Mar 2015 07:28:35 -0000

--_000_787AE7BB302AE849A7480A190F8B933004926895OPEXCLILM23corp_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Surendra,

It seems we are putting a lot of requirements on the control plane while th=
ere is not yet such thing chartered to captured those.

BTW, the current spec already bumped up the version (hint "MD type") ;-)

Cheers,
Med

De : Surendra Kumar (smkumar) [mailto:smkumar@cisco.com]
Envoy=E9 : jeudi 5 mars 2015 21:17
=C0 : BOUCADAIR Mohamed IMT/OLN; Ron Parker; Sunil Vallamkonda
Cc : sfc@ietf.org
Objet : Re: [sfc] draft-quinn-sfc-nsh: version number



From: "mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>" <=
mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>>
Date: Wednesday, March 4, 2015 at 8:09 AM
To: Ron Parker <Ron_Parker@affirmednetworks.com<mailto:Ron_Parker@affirmedn=
etworks.com>>, Sunil Vallamkonda <sunilvk@f5.com<mailto:sunilvk@f5.com>>
Cc: "sfc@ietf.org<mailto:sfc@ietf.org>" <sfc@ietf.org<mailto:sfc@ietf.org>>
Subject: Re: [sfc] draft-quinn-sfc-nsh: version number

Re-,

That would be a good start, but still not sufficient IMHO.

If no notification is sent back (which can be the case with the MAY languag=
e), the failure will be experienced till an action is done by the domain op=
erator. This is not desirable.

Having a more strong language for sending back the response (that needs to =
include at least the received packet with the unsupported version) will hav=
e the effect to resend the packet with an adequate version (if multiple ver=
sions are supported). The exact behavior when a version mismatch error is r=
eceived should be explicated in the document IMO.
SK> Version incompatibility (with version numbers as opposed to flags) is a=
 transient issue when there exists a control-plane. It is very likely that =
there will exist SFs/SFFs/Classifiers which understand different versions o=
f the header and they must continue to inter-operate. The control plane mus=
t ensure a highest common version among the participants.

In the absence of such an over-arching control plane, there is a need to re=
solve the versions and this may or may not require data plane learning of t=
he versions based on how seamlessly the participants are required to be ins=
erted into the architecture. One could make a case either way but seems mor=
e appropriate to be left to the control plane, particularly given the exten=
sibility built into the header - hopefully it is some time before we have a=
 need to bump the version.

Surendra.

Cheers,
Med

De : Ron Parker [mailto:Ron_Parker@affirmednetworks.com]
Envoy=E9 : mercredi 4 mars 2015 16:50
=C0 : BOUCADAIR Mohamed IMT/OLN; Sunil Vallamkonda
Cc : sfc@ietf.org<mailto:sfc@ietf.org>
Objet : RE: Re: [sfc] draft-quinn-sfc-nsh: version number

Med,

I agree that we should add additional text around the expected behavior reg=
arding version incompatibility.   We could state that the SFF or SF perceiv=
ing this incompatibility MUST drop such a packet and MAY generate an OAM re=
sponse in the reverse direction, although the exact nature of that response=
 is outside the scope of the NSH draft.

   Ron





From: mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com> [ma=
ilto:mohamed.boucadair@orange.com]
Sent: Wednesday, March 4, 2015 10:43 AM
To: Ron Parker; Sunil Vallamkonda
Cc: sfc@ietf.org<mailto:sfc@ietf.org>
Subject: RE: Re: [sfc] draft-quinn-sfc-nsh: version number

Hi Ron,

If the version number is maintained, discussing the behavior of a node if i=
t supports several versions, if it does not support the version of a packet=
 it receives, etc. is not about OAM. This is part of the behavior that need=
s to be specified in the document.

Cheers,
Med


De : Ron Parker [mailto:Ron_Parker@affirmednetworks.com]
Envoy=E9 : mercredi 4 mars 2015 16:03
=C0 : BOUCADAIR Mohamed IMT/OLN; Sunil Vallamkonda
Cc : sfc@ietf.org<mailto:sfc@ietf.org>
Objet : RE: Re: [sfc] draft-quinn-sfc-nsh: version number

When we take up OAM, we could consider these ICMP-like behaviors - i.e., OA=
M packet containing "Version Incompatible" sent in the reverse direction on=
 the involved RSP.   But I'm not sure what should be discussed in this draf=
t, since OAM is explicitly out of scope.

   Ron



From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of mohamed.boucadair@oran=
ge.com<mailto:mohamed.boucadair@orange.com>
Sent: Wednesday, March 4, 2015 1:47 AM
To: Sunil Vallamkonda
Cc: sfc@ietf.org<mailto:sfc@ietf.org>
Subject: Re: [sfc] draft-quinn-sfc-nsh: version number

Hi Sunil,

There is no such notification in the current spec.

Below my thoughts about this point:

=3D=3D

(b) Suppose a node that supports only v1 receives a packet with header (v2)=
: If this node does not support a notification procedure to inform the sour=
ce that it does not support that header version, then FAILURES are introduc=
ed in the network. This is a degradation of the service compared to legacy =
scheme to structure services. This is not recommended, IMHO.



(c) If a notification is received from an element about its supported versi=
on: a node can use another version (the logic to select other version is an=
other point to discuss) for that communication, but what to do for the next=
 flows in the context of the same service chain or other chains that involv=
es these two nodes as adjacent elements in the same chain? Shouldn't these =
nodes cache the version to use for subsequent exchange to avoid receiving t=
he notification error each time? Wouldn't that complexity the behavior of t=
he SFC-aware elements?



(d) If a notification is received from an element about its supported versi=
on: As this may occurs in various segments of a given service chain, e.g., =
(A(v1), B(v1,v2), C(v1), D(v1,v2), E(v1)). Notifying the adjacent node each=
 time there is a version mismatch induce an extra delay, that may be not be=
 acceptable for every flow.
=3D=3D

Thank you.

Cheers,
Med


De : sfc [mailto:sfc-bounces@ietf.org] De la part de Sunil Vallamkonda
Envoy=E9 : mardi 3 mars 2015 20:43
=C0 : sfc@ietf.org<mailto:sfc@ietf.org>
Objet : Re: [sfc] draft-quinn-sfc-nsh: version number

Hi,

Just going through the thread on version number (jumping in mid-thread),

Apart from the version mismatched (unsupported) packet dropped and logged, =
is there a plan for a back off mechanism by SFF to notify sender and avoid =
being overwhelmed with such packets ?

Thank you,
Sunil.


Re: [sfc] draft-quinn-sfc-nsh: version number
________________________________

  *   From: "Paul Quinn (paulq)" <paulq at cisco.com<mailto:paulq@DOMAIN.HI=
DDEN>>
  *   To: "Joel M. Halpern" <jmh at joelhalpern.com<mailto:jmh@DOMAIN.HIDDE=
N>>
  *   Cc: "mohamed.boucadair at orange.com<mailto:mohamed.boucadair@DOMAIN.=
HIDDEN>" <mohamed.boucadair at orange.com<mailto:mohamed.boucadair@DOMAIN.H=
IDDEN>>, "sfc at ietf.org<mailto:sfc@DOMAIN.HIDDEN>" <sfc at ietf.org<mailt=
o:sfc@DOMAIN.HIDDEN>>
  *   Date: Mon, 2 Mar 2015 17:50:53 +0000
  *   In-reply-to: <54EF2C9A.3040008@joelhalpern.com<http://www.ietf.org/ma=
il-archive/web/sfc/current/msg03181.html>>
  *   References: <787AE7BB302AE849A7480A190F8B9330049140B4@OPEXCLILM23.cor=
porate.adroot.infra.ftgroup<mailto:787AE7BB302AE849A7480A190F8B9330049140B4=
@OPEXCLILM23.corporate.adroot.infra.ftgroup>> <54EDE5B7.6080102@joelhalpern=
.com<http://www.ietf.org/mail-archive/web/sfc/current/msg03151.html>> <787A=
E7BB302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.adroot.infra.ftg=
roup<mailto:787AE7BB302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.=
adroot.infra.ftgroup>> <54EF2C9A.3040008@joelhalpern.com<http://www.ietf.or=
g/mail-archive/web/sfc/current/msg03181.html>>
  *   List-id: Network Service Chaining <sfc.ietf.org>

________________________________

Hi,



Jumping in mid-thread.



Overall, I tend to agree with Joel.  Having an explicit version provides a =
simple way to handle dataplane format changes.  As Med points out, quickly =
correctly, IMHO, there are other way to signal changes via reserved bit.  I=
n practice though reserved bits are less useful since the convention is to =
ignore unknown bits, it makes using them for feature changes quite difficul=
t, which then brings up back to explicit versioning that cannot be ignored.



I think Joel's suggestion below makes perfect sense and should be added to =
the draft.



Paul





> On Feb 26, 2015, at 9:24 AM, Joel M. Halpern <jmh at joelhalpern.com> wro=
te:

>

> In one sense you are correct.  If you could count on everything being upg=
raded at once, sure you could just assume common interpretation.

> However, we have found over the years that such simultaneous upgrading ne=
ver works.  You need to be able to transition.

>

> I do agree that we should add text about what to do with version numbers =
that are not understood.  There are multiple choices that affect how we can=
 make changes.  My personal preference is:

>

> If an packet presumed to carry an NSH header is received at an SFF, and t=
he SFF does not understnad the version of the protocol as indicated in the =
base header, the packet MUST be discarded, and the event SHOULD be logged.

>

> This would allow an orderly transition, where devices can be upgraded to =
understand a new version, then generation of the new version header can be =
enabled.  If a configuration error is made, the packets will be dropped and=
 operators following good practices will get notifications.

>

> Yours,

> Joel

>

> On 2/26/15 2:16 AM, mohamed.boucadair at orange.com wrote:

>> Hi Joel,

>>

>> I fully agree with the extendibility of the header, but the question is =
why having a version number will be of help in the context of SFC? Second, =
having a version number without specifying the behavior when several versio=
ns are supported, when the version number is not supported by an SFC-aware =
element, etc. leaves open issues out of the spec.

>>

>> The other problem is that the current I-D includes several open doors le=
ft for extending the header:

>> * version

>> * reserved bits

>> * optional data

>>

>> This is too much for a header that is supposed to be compact and simple!

>>

>> There are other means to extend the header without signaling the version=
 in the packet. Having a distinct RFC number may be just fine in the contex=
t of an unidirectional stream such as SFC.

>>

>> Let us consider the situation where a version number is not explicitly s=
ignaled in the packet (but a new RFC updates the base SFC header). Several =
options can be considered, indeed (those are provided as examples for illus=
tration purposes):

>> * An operator can make sure that its SFC-enabled domain is configured in=
 a consistent manner to support one and only one version of the header. No =
interoperability issues is encountered in this case.

>> * An operator that wants to upgrade its SFC-enabled domain to support a =
new specification of the SFC header: An operator can decide to proceed to a=
 software/hardware updates but can maintain the old header in operation unt=
il all involved elements are upgraded to support the new version. Once the =
SFC-enabled domain is upgraded, then the new header can be enabled.

>>

>> Let's consider now that a version is signaled in the packet: to what ext=
ent signaling this information simplifies the SFC operations, and whether i=
t increases/decreases the serviceability of an SFC-enabled domain? Let's al=
so assess to what extent having the version number add more complexity in t=
he SFC header treatment when several versions are supported by a node/withi=
n an SFC enabled domain? How it helps interoperability? Some points for dis=
cussion are elaborated below:

>>

>> * If the SFC-enabled domain is configured to support the same version (w=
hich is likely): having the version number is not of any help.

>> * If the SFC-enabled domain involves some nodes that support version (v1=
) while others support (v2) (simple case): If these version are not backwar=
d compatible, this will lead to failures when two adjacent elements in a se=
rvice chain do not support the same version. The SFC system is broken. Havi=
ng the version number is not of any help in this case.

>> * If the SFC-enabled domain involves some nodes that support version (v1=
) while others support (v1 and v2):

>>

>> (a) The nodes that support both v1 and v2 should be instructed to decide=
 which version to be used. This can be either part of the specification or =
be driven by configuration. If a version number is included in the spec, I =
would expect to clarify the behavior in such case.

>>

>> (b) Suppose a node that supports only v1 receives a packet with header (=
v2): If this node does not support a notification procedure to inform the s=
ource that it does not support that header version, then FAILURES are intro=
duced in the network. This is a degradation of the service compared to lega=
cy scheme to structure services. This is not recommended, IMHO.

>>

>> (c) If a notification is received from an element about its supported ve=
rsion: a node can use another version (the logic to select other version is=
 another point to discuss) for that communication, but what to do for the n=
ext flows in the context of the same service chain or other chains that inv=
olves these two nodes as adjacent elements in the same chain? Shouldn't the=
se nodes cache the version to use for subsequent exchange to avoid receivin=
g the notification error each time? Wouldn't that complexity the behavior o=
f the SFC-aware elements?

>>

>> (d) If a notification is received from an element about its supported ve=
rsion: As this may occurs in various segments of a given service chain, e.g=
., (A(v1), B(v1,v2), C(v2), D(v1,v2), E(v1)). Notifying the adjacent node e=
ach time there is a version mismatch induce an extra delay, that may be not=
 be acceptable for every flow.

>>

>> I hope this clarifies my initial concern.

>>

>> Thank you.

>>

>> Cheers,

>> Med

>>

>>> -----Message d'origine-----

>>> De : Joel M. Halpern [mailto:jmh at joelhalpern.com]

>>> Envoy=E9 : mercredi 25 f=E9vrier 2015 16:10

>>> =C0 : BOUCADAIR Mohamed IMT/OLN; paulq at cisco.com

>>> Cc : sfc at ietf.org

>>> Objet : Re: [sfc] draft-quinn-sfc-nsh: version number

>>>

>>> I would really prefer to keep the version number.  Even though we have

>>> the MD-type identifier and for some MD we have the TLVs.

>>>

>>> The reason is that we may want to change the base header.  For example,

>>> suppose that the ciscussion about including a flow identifier in the

>>> base header had not come up now.  If it came up later, we would want to

>>> be able to have the discussion and make the choice, rather than being

>>> constrained by the lack of a version field.

>>>

>>> Yours,

>>> Joel

>>>

>>>

>>> On 2/25/15 10:03 AM, mohamed.boucadair at orange.com wrote:

>>>> Hi Paul, all,

>>>>

>>>> What is the purpose of having a version number in the header? Is there=
 a

>>>> kind of version negotiation that needs to be in place?

>>>>

>>>> I checked the I-D but failed to find text that explains the rationale,

>>>> the use of the such field and whether an error will be returned if the

>>>> version is not supported by the receiving node.

>>>>

>>>> Wouldn't be preferable to get rid of this field given that SFC header

>>>> can be extended using optional objects and consistent setup &

>>>> configuration within an SFC-enabled domain should be assumed?

>>>>

>>>> Thank you

>>>>

>>>> Cheers,

>>>>

>>>> Med

>>>>

>>>>

>>>>

>>>> _______________________________________________

>>>> sfc mailing list

>>>> sfc at ietf.org

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

>>>>

>>




--_000_787AE7BB302AE849A7480A190F8B933004926895OPEXCLILM23corp_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Cambria;
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"Segoe UI";
	panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
h1
	{mso-style-priority:9;
	mso-style-link:"Titre 1 Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	font-weight:normal;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Texte brut Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"Pr=E9format=E9 HTML Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Texte de bulles Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.Titre1Car
	{mso-style-name:"Titre 1 Car";
	mso-style-priority:9;
	mso-style-link:"Titre 1";
	font-family:"Cambria","serif";
	color:#365F91;
	font-weight:bold;}
span.PrformatHTMLCar
	{mso-style-name:"Pr=E9format=E9 HTML Car";
	mso-style-priority:99;
	mso-style-link:"Pr=E9format=E9 HTML";
	font-family:Consolas;}
span.TextebrutCar
	{mso-style-name:"Texte brut Car";
	mso-style-priority:99;
	mso-style-link:"Texte brut";
	font-family:"Courier New";
	color:black;
	mso-fareast-language:EN-US;}
span.TextedebullesCar
	{mso-style-name:"Texte de bulles Car";
	mso-style-priority:99;
	mso-style-link:"Texte de bulles";
	font-family:"Tahoma","sans-serif";}
span.Heading1Char
	{mso-style-name:"Heading 1 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 1";
	font-family:"Times New Roman","serif";
	font-weight:bold;}
p.Heading1, li.Heading1, div.Heading1
	{mso-style-name:"Heading 1";
	mso-style-link:"Heading 1 Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
p.HTMLPreformatted, li.HTMLPreformatted, div.HTMLPreformatted
	{mso-style-name:"HTML Preformatted";
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
p.PlainText, li.PlainText, div.PlainText
	{mso-style-name:"Plain Text";
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Segoe UI","sans-serif";}
p.BalloonText, li.BalloonText, div.BalloonText
	{mso-style-name:"Balloon Text";
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle32
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle33
	{mso-style-type:personal;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;}
span.EmailStyle34
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle35
	{mso-style-type:personal;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;}
span.EmailStyle36
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle37
	{mso-style-type:personal;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;}
span.EmailStyle39
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1094283961;
	mso-list-template-ids:-714036274;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1
	{mso-list-id:1529875700;
	mso-list-template-ids:1047569284;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"FR" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Hi Surendra,<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">It seems we are putting a lot o=
f requirements on the control plane while there is not yet such thing chart=
ered to captured those.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">BTW, the current spec already b=
umped up the version (hint &#8220;MD type&#8221;) ;-)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Cheers,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Med<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">De&nbsp;:</span></b><span style=3D"fo=
nt-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Sure=
ndra Kumar (smkumar) [mailto:smkumar@cisco.com]
<br>
<b>Envoy=E9&nbsp;:</b> jeudi 5 mars 2015 21:17<br>
<b>=C0&nbsp;:</b> BOUCADAIR Mohamed IMT/OLN; Ron Parker; Sunil Vallamkonda<=
br>
<b>Cc&nbsp;:</b> sfc@ietf.org<br>
<b>Objet&nbsp;:</b> Re: [sfc] draft-quinn-sfc-nsh: version number<o:p></o:p=
></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"color:black">From: </span></b><spa=
n style=3D"color:black">&quot;<a href=3D"mailto:mohamed.boucadair@orange.co=
m">mohamed.boucadair@orange.com</a>&quot; &lt;<a href=3D"mailto:mohamed.bou=
cadair@orange.com">mohamed.boucadair@orange.com</a>&gt;<br>
<b>Date: </b>Wednesday, March 4, 2015 at 8:09 AM<br>
<b>To: </b>Ron Parker &lt;<a href=3D"mailto:Ron_Parker@affirmednetworks.com=
">Ron_Parker@affirmednetworks.com</a>&gt;, Sunil Vallamkonda &lt;<a href=3D=
"mailto:sunilvk@f5.com">sunilvk@f5.com</a>&gt;<br>
<b>Cc: </b>&quot;<a href=3D"mailto:sfc@ietf.org">sfc@ietf.org</a>&quot; &lt=
;<a href=3D"mailto:sfc@ietf.org">sfc@ietf.org</a>&gt;<br>
<b>Subject: </b>Re: [sfc] draft-quinn-sfc-nsh: version number<o:p></o:p></s=
pan></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Re-,</span><span style=3D"color:black"><o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">That would be a good start, but=
 still not sufficient IMHO.</span><span style=3D"color:black"><o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">&nbsp;</span><span style=3D"col=
or:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">If no notification is sent back=
 (which can be the case with the MAY language), the failure will be experie=
nced till an action is done by the domain operator.
 This is not desirable. </span><span style=3D"color:black"><o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">&nbsp;</span><span style=3D"col=
or:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Having a more strong language f=
or sending back the response (that needs to include at least the received p=
acket with the unsupported version) will have the
 effect to resend the packet with an adequate version (if multiple versions=
 are supported). The exact behavior when a version mismatch error is receiv=
ed should be explicated in the document IMO.</span><span style=3D"color:bla=
ck"><o:p></o:p></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">SK&gt; =
Version incompatibility (with version numbers as opposed to flags) is a tra=
nsient issue when there exists a control-plane. It is very likely that ther=
e will exist SFs/SFFs/Classifiers which
 understand different versions of the header and they must continue to inte=
r-operate. The control plane must ensure a highest common version among the=
 participants.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">In the =
absence of such an over-arching control plane, there is a need to resolve t=
he versions and this may or may not require data plane learning of the vers=
ions based on how seamlessly the participants
 are required to be inserted into the architecture. One could make a case e=
ither way but seems more appropriate to be left to the control plane, parti=
cularly given the extensibility built into the header - hopefully it is som=
e time before we have a need to
 bump the version.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Surendr=
a.<o:p></o:p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">&nbsp;</span><span style=3D"col=
or:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Cheers,</span><span style=3D"co=
lor:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Med</span><span style=3D"color:=
black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">&nbsp;</span><span style=3D"col=
or:black"><o:p></o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;;color:black">De&nbsp;:</span></b><span=
 style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&=
quot;;color:black"> Ron Parker [<a href=3D"mailto:Ron_Parker@affirmednetwor=
ks.com">mailto:Ron_Parker@affirmednetworks.com</a>]
<br>
<b>Envoy=E9&nbsp;:</b> mercredi 4 mars 2015 16:50<br>
<b>=C0&nbsp;:</b> BOUCADAIR Mohamed IMT/OLN; Sunil Vallamkonda<br>
<b>Cc&nbsp;:</b> <a href=3D"mailto:sfc@ietf.org">sfc@ietf.org</a><br>
<b>Objet&nbsp;:</b> RE: Re: [sfc] draft-quinn-sfc-nsh: version number</span=
><span style=3D"color:black"><o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Med,</s=
pan><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">I agree=
 that we should add additional text around the expected behavior regarding =
version incompatibility.&nbsp;&nbsp; We could state that the SFF or SF perc=
eiving this incompatibility MUST drop such a packet
 and MAY generate an OAM response in the reverse direction, although the ex=
act nature of that response is outside the scope of the NSH draft.</span><s=
pan style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp; Ron</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><a name=3D"_MailEndCompose"></a><span lang=3D"EN-US"=
 style=3D"color:#1F497D">&nbsp;</span><span style=3D"color:black"><o:p></o:=
p></span></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"color:black">From:<=
/span></b><span lang=3D"EN-US" style=3D"color:black">
<a href=3D"mailto:mohamed.boucadair@orange.com">mohamed.boucadair@orange.co=
m</a> [<a href=3D"mailto:mohamed.boucadair@orange.com">mailto:mohamed.bouca=
dair@orange.com</a>]
<br>
<b>Sent:</b> Wednesday, March 4, 2015 10:43 AM<br>
<b>To:</b> Ron Parker; Sunil Vallamkonda<br>
<b>Cc:</b> <a href=3D"mailto:sfc@ietf.org">sfc@ietf.org</a><br>
<b>Subject:</b> RE: Re: [sfc] draft-quinn-sfc-nsh: version number</span><sp=
an style=3D"color:black"><o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black">&nbsp;</s=
pan><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Hi Ron,</span><span style=3D"color:black"><o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">If the version number is mainta=
ined, discussing the behavior of a node if it supports several versions, if=
 it does not support the version of a packet it
 receives, etc. is not about OAM. This is part of the behavior that needs t=
o be specified in the document.
</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">&nbsp;</span><span style=3D"col=
or:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Cheers,</span><span style=3D"co=
lor:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Med</span><span style=3D"color:=
black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">&nbsp;</span><span style=3D"col=
or:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">&nbsp;</span><span style=3D"col=
or:black"><o:p></o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;;color:black">De&nbsp;:</span></b><span=
 style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&=
quot;;color:black"> Ron Parker [<a href=3D"mailto:Ron_Parker@affirmednetwor=
ks.com">mailto:Ron_Parker@affirmednetworks.com</a>]
<br>
<b>Envoy=E9&nbsp;:</b> mercredi 4 mars 2015 16:03<br>
<b>=C0&nbsp;:</b> BOUCADAIR Mohamed IMT/OLN; Sunil Vallamkonda<br>
<b>Cc&nbsp;:</b> <a href=3D"mailto:sfc@ietf.org">sfc@ietf.org</a><br>
<b>Objet&nbsp;:</b> RE: Re: [sfc] draft-quinn-sfc-nsh: version number</span=
><span style=3D"color:black"><o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">When we=
 take up OAM, we could consider these ICMP-like behaviors &#8211; i.e., OAM=
 packet containing &#8220;Version Incompatible&#8221; sent in the reverse d=
irection on the involved RSP.&nbsp;&nbsp; But I&#8217;m not sure what shoul=
d
 be discussed in this draft, since OAM is explicitly out of scope.</span><s=
pan style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp; Ron</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"color:black">From:<=
/span></b><span lang=3D"EN-US" style=3D"color:black"> sfc [<a href=3D"mailt=
o:sfc-bounces@ietf.org">mailto:sfc-bounces@ietf.org</a>]
<b>On Behalf Of </b><a href=3D"mailto:mohamed.boucadair@orange.com">mohamed=
.boucadair@orange.com</a><br>
<b>Sent:</b> Wednesday, March 4, 2015 1:47 AM<br>
<b>To:</b> Sunil Vallamkonda<br>
<b>Cc:</b> <a href=3D"mailto:sfc@ietf.org">sfc@ietf.org</a><br>
<b>Subject:</b> Re: [sfc] draft-quinn-sfc-nsh: version number</span><span s=
tyle=3D"color:black"><o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black">&nbsp;</s=
pan><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Hi Sunil,</span><span style=3D"=
color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">&nbsp;</span><span style=3D"col=
or:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">There is no such notification i=
n the current spec.
</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">&nbsp;</span><span style=3D"col=
or:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Below my thoughts about this po=
int:</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">&nbsp;</span><span style=3D"col=
or:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">=3D=3D</span><span style=3D"col=
or:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Courier New&quot;;color:black">(b) Suppose a node that supp=
orts only v1 receives a packet with header (v2): If this node does not supp=
ort a notification procedure to inform the source
 that it does not support that header version, then FAILURES are introduced=
 in the network. This is a degradation of the service compared to legacy sc=
heme to structure services. This is not recommended, IMHO.</span><span styl=
e=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Courier New&quot;;color:black">&nbsp;</span><span style=3D"=
color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Courier New&quot;;color:black">(c) If a notification is rec=
eived from an element about its supported version: a node can use another v=
ersion (the logic to select other version is another
 point to discuss) for that communication, but what to do for the next flow=
s in the context of the same service chain or other chains that involves th=
ese two nodes as adjacent elements in the same chain? Shouldn't these nodes=
 cache the version to use for subsequent
 exchange to avoid receiving the notification error each time? Wouldn't tha=
t complexity the behavior of the SFC-aware elements?</span><span style=3D"c=
olor:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Courier New&quot;;color:black">&nbsp;</span><span style=3D"=
color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Courier New&quot;;color:black">(d) If a notification is rec=
eived from an element about its supported version: As this may occurs in va=
rious segments of a given service chain, e.g., (A(v1),
 B(v1,v2), C(v1), D(v1,v2), E(v1)). Notifying the adjacent node each time t=
here is a version mismatch induce an extra delay, that may be not be accept=
able for every flow.</span><span style=3D"color:black"><o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">=3D=3D</span><span style=3D"col=
or:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">&nbsp;</span><span style=3D"col=
or:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Thank you.</span><span style=3D=
"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">&nbsp;</span><span style=3D"col=
or:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Cheers,</span><span style=3D"co=
lor:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Med</span><span style=3D"color:=
black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">&nbsp;</span><span style=3D"col=
or:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">&nbsp;</span><span style=3D"col=
or:black"><o:p></o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;;color:black">De&nbsp;:</span></b><span=
 style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&=
quot;;color:black"> sfc [<a href=3D"mailto:sfc-bounces@ietf.org">mailto:sfc=
-bounces@ietf.org</a>]
<b>De la part de</b> Sunil Vallamkonda<br>
<b>Envoy=E9&nbsp;:</b> mardi 3 mars 2015 20:43<br>
<b>=C0&nbsp;:</b> <a href=3D"mailto:sfc@ietf.org">sfc@ietf.org</a><br>
<b>Objet&nbsp;:</b> Re: [sfc] draft-quinn-sfc-nsh: version number</span><sp=
an style=3D"color:black"><o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black">Hi,</span=
><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black">&nbsp;</s=
pan><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black">Just goin=
g through the thread on version number (jumping in mid-thread),</span><span=
 style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black">&nbsp;</s=
pan><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black">Apart fro=
m the version mismatched (unsupported) packet dropped and logged, is there =
a plan for a back off mechanism by SFF to notify sender and avoid being ove=
rwhelmed with such packets ?</span><span style=3D"color:black"><o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black">&nbsp;</s=
pan><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black">Thank you=
,</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black">Sunil.</s=
pan><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black">&nbsp;</s=
pan><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black">&nbsp;</s=
pan><span style=3D"color:black"><o:p></o:p></span></p>
<h1 style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang=
=3D"EN-US" style=3D"font-size:14.0pt;font-family:&quot;Times New Roman&quot=
;,&quot;serif&quot;;color:black">Re: [sfc] draft-quinn-sfc-nsh: version num=
ber</span><span style=3D"color:black"><o:p></o:p></span></h1>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 lang=3D"EN-US" style=3D"color:black">
<hr size=3D"2" width=3D"100%" align=3D"center">
</span></div>
<span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:black;mso-fareast-language:FR">
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"color:black;mso-margin-top-alt:auto;mso-ma=
rgin-bottom-alt:auto;mso-list:l0 level1 lfo3">
<em><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">=
From</span></em><span style=3D"mso-fareast-language:EN-US">: &quot;Paul Qui=
nn (paulq)&quot; &lt;<a href=3D"mailto:paulq@DOMAIN.HIDDEN">paulq at cisco.=
com</a>&gt;</span><span lang=3D"FR"><o:p></o:p></span></li><li class=3D"Mso=
Normal" style=3D"color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:=
auto;mso-list:l0 level1 lfo3">
<em><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">=
To</span></em><span style=3D"mso-fareast-language:EN-US">: &quot;Joel M. Ha=
lpern&quot; &lt;<a href=3D"mailto:jmh@DOMAIN.HIDDEN">jmh at joelhalpern.com=
</a>&gt;</span><span lang=3D"FR"><o:p></o:p></span></li><li class=3D"MsoNor=
mal" style=3D"color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:aut=
o;mso-list:l0 level1 lfo3">
<em><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">=
Cc</span></em><span style=3D"mso-fareast-language:EN-US">: &quot;<a href=3D=
"mailto:mohamed.boucadair@DOMAIN.HIDDEN">mohamed.boucadair at orange.com</a=
>&quot; &lt;<a href=3D"mailto:mohamed.boucadair@DOMAIN.HIDDEN">mohamed.bouc=
adair
 at orange.com</a>&gt;, &quot;<a href=3D"mailto:sfc@DOMAIN.HIDDEN">sfc at i=
etf.org</a>&quot; &lt;<a href=3D"mailto:sfc@DOMAIN.HIDDEN">sfc at ietf.org<=
/a>&gt;</span><span lang=3D"FR"><o:p></o:p></span></li><li class=3D"MsoNorm=
al" style=3D"color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto=
;mso-list:l0 level1 lfo3">
<em><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">=
Date</span></em><span style=3D"mso-fareast-language:EN-US">: Mon, 2 Mar 201=
5 17:50:53 &#43;0000</span><span lang=3D"FR"><o:p></o:p></span></li><li cla=
ss=3D"MsoNormal" style=3D"color:black;mso-margin-top-alt:auto;mso-margin-bo=
ttom-alt:auto;mso-list:l0 level1 lfo3">
<em><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">=
In-reply-to</span></em><span style=3D"mso-fareast-language:EN-US">: &lt;<a =
href=3D"http://www.ietf.org/mail-archive/web/sfc/current/msg03181.html">54E=
F2C9A.3040008@joelhalpern.com</a>&gt;</span><span lang=3D"FR"><o:p></o:p></=
span></li><li class=3D"MsoNormal" style=3D"color:black;mso-margin-top-alt:a=
uto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3">
<em><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">=
References</span></em><span style=3D"mso-fareast-language:EN-US">: &lt;<a h=
ref=3D"mailto:787AE7BB302AE849A7480A190F8B9330049140B4@OPEXCLILM23.corporat=
e.adroot.infra.ftgroup">787AE7BB302AE849A7480A190F8B9330049140B4@OPEXCLILM2=
3.corporate.adroot.infra.ftgroup</a>&gt;
 &lt;<a href=3D"http://www.ietf.org/mail-archive/web/sfc/current/msg03151.h=
tml">54EDE5B7.6080102@joelhalpern.com</a>&gt; &lt;<a href=3D"mailto:787AE7B=
B302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.adroot.infra.ftgrou=
p">787AE7BB302AE849A7480A190F8B9330049156A9@OPEXCLILM23.corporate.adroot.in=
fra.ftgroup</a>&gt;
 &lt;<a href=3D"http://www.ietf.org/mail-archive/web/sfc/current/msg03181.h=
tml">54EF2C9A.3040008@joelhalpern.com</a>&gt;</span><span lang=3D"FR"><o:p>=
</o:p></span></li><li class=3D"MsoNormal" style=3D"color:black;mso-margin-t=
op-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3">
<em><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">=
List-id</span></em><span style=3D"mso-fareast-language:EN-US">: Network Ser=
vice Chaining &lt;sfc.ietf.org&gt;</span><span lang=3D"FR"><o:p></o:p></spa=
n></li></ul>
</span>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 lang=3D"EN-US" style=3D"color:black">
<hr size=3D"2" width=3D"100%" align=3D"center">
</span></div>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">Hi,</span><span style=3D"color:black"><o:p></o:p>=
</span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o=
:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">Jumping in mid-thread.&nbsp; </span><span style=
=3D"color:black"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o=
:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">Overall, I tend to agree with Joel.&nbsp; Having =
an explicit version provides a simple way to handle dataplane format change=
s.&nbsp; As Med points out, quickly correctly, IMHO, there are other way to=
 signal changes via reserved bit.&nbsp; In practice though reserved bits ar=
e less useful since the convention is to ignore unknown bits, it makes usin=
g them for feature changes quite difficult, which then brings up back to ex=
plicit versioning that cannot be ignored.&nbsp; </span><span style=3D"color=
:black"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o=
:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">I think Joel&#8217;s suggestion below makes perfe=
ct sense and should be added to the draft.</span><span style=3D"color:black=
"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o=
:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">Paul</span><span style=3D"color:black"><o:p></o:p=
></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o=
:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o=
:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt; On Feb 26, 2015, at 9:24 AM, Joel M. Halpern=
 &lt;jmh at joelhalpern.com&gt; wrote:</span><span style=3D"color:black"><o=
:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt; </span><span style=3D"color:black"><o:p></o:=
p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt; In one sense you are correct.&nbsp; If you c=
ould count on everything being upgraded at once, sure you could just assume=
 common interpretation.</span><span style=3D"color:black"><o:p></o:p></span=
></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt; However, we have found over the years that s=
uch simultaneous upgrading never works.&nbsp; You need to be able to transi=
tion.</span><span style=3D"color:black"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt; </span><span style=3D"color:black"><o:p></o:=
p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt; I do agree that we should add text about wha=
t to do with version numbers that are not understood.&nbsp; There are multi=
ple choices that affect how we can make changes.&nbsp; My personal preferen=
ce is:</span><span style=3D"color:black"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt; </span><span style=3D"color:black"><o:p></o:=
p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt; If an packet presumed to carry an NSH header=
 is received at an SFF, and the SFF does not understnad the version of the =
protocol as indicated in the base header, the packet MUST be discarded, and=
 the event SHOULD be logged.</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt; </span><span style=3D"color:black"><o:p></o:=
p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt; This would allow an orderly transition, wher=
e devices can be upgraded to understand a new version, then generation of t=
he new version header can be enabled.&nbsp; If a configuration error is mad=
e, the packets will be dropped and operators following good practices will =
get notifications.</span><span style=3D"color:black"><o:p></o:p></span></pr=
e>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt; </span><span style=3D"color:black"><o:p></o:=
p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt; Yours,</span><span style=3D"color:black"><o:=
p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt; Joel</span><span style=3D"color:black"><o:p>=
</o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt; </span><span style=3D"color:black"><o:p></o:=
p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt; On 2/26/15 2:16 AM, mohamed.boucadair at ora=
nge.com wrote:</span><span style=3D"color:black"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; Hi Joel,</span><span style=3D"color:blac=
k"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; </span><span style=3D"color:black"><o:p>=
</o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; I fully agree with the extendibility of =
the header, but the question is why having a version number will be of help=
 in the context of SFC? Second, having a version number without specifying =
the behavior when several versions are supported, when the version number i=
s not supported by an SFC-aware element, etc. leaves open issues out of the=
 spec.</span><span style=3D"color:black"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; </span><span style=3D"color:black"><o:p>=
</o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; The other problem is that the current I-=
D includes several open doors left for extending the header:</span><span st=
yle=3D"color:black"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; * version</span><span style=3D"color:bla=
ck"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; * reserved bits</span><span style=3D"col=
or:black"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; * optional data</span><span style=3D"col=
or:black"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; </span><span style=3D"color:black"><o:p>=
</o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; This is too much for a header that is su=
pposed to be compact and simple!</span><span style=3D"color:black"><o:p></o=
:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; </span><span style=3D"color:black"><o:p>=
</o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; There are other means to extend the head=
er without signaling the version in the packet. Having a distinct RFC numbe=
r may be just fine in the context of an unidirectional stream such as SFC.<=
/span><span style=3D"color:black"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; </span><span style=3D"color:black"><o:p>=
</o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; Let us consider the situation where a ve=
rsion number is not explicitly signaled in the packet (but a new RFC update=
s the base SFC header). Several options can be considered, indeed (those ar=
e provided as examples for illustration purposes):</span><span style=3D"col=
or:black"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; * An operator can make sure that its SFC=
-enabled domain is configured in a consistent manner to support one and onl=
y one version of the header. No interoperability issues is encountered in t=
his case.</span><span style=3D"color:black"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; * An operator that wants to upgrade its =
SFC-enabled domain to support a new specification of the SFC header: An ope=
rator can decide to proceed to a software/hardware updates but can maintain=
 the old header in operation until all involved elements are upgraded to su=
pport the new version. Once the SFC-enabled domain is upgraded, then the ne=
w header can be enabled.</span><span style=3D"color:black"><o:p></o:p></spa=
n></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; </span><span style=3D"color:black"><o:p>=
</o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; Let's consider now that a version is sig=
naled in the packet: to what extent signaling this information simplifies t=
he SFC operations, and whether it increases/decreases the serviceability of=
 an SFC-enabled domain? Let's also assess to what extent having the version=
 number add more complexity in the SFC header treatment when several versio=
ns are supported by a node/within an SFC enabled domain? How it helps inter=
operability? Some points for discussion are elaborated below:</span><span s=
tyle=3D"color:black"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; </span><span style=3D"color:black"><o:p>=
</o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; * If the SFC-enabled domain is configure=
d to support the same version (which is likely): having the version number =
is not of any help.</span><span style=3D"color:black"><o:p></o:p></span></p=
re>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; * If the SFC-enabled domain involves som=
e nodes that support version (v1) while others support (v2) (simple case): =
If these version are not backward compatible, this will lead to failures wh=
en two adjacent elements in a service chain do not support the same version=
. The SFC system is broken. Having the version number is not of any help in=
 this case.</span><span style=3D"color:black"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; * If the SFC-enabled domain involves som=
e nodes that support version (v1) while others support (v1 and v2):</span><=
span style=3D"color:black"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; </span><span style=3D"color:black"><o:p>=
</o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; (a) The nodes that support both v1 and v=
2 should be instructed to decide which version to be used. This can be eith=
er part of the specification or be driven by configuration. If a version nu=
mber is included in the spec, I would expect to clarify the behavior in suc=
h case.</span><span style=3D"color:black"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; </span><span style=3D"color:black"><o:p>=
</o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; (b) Suppose a node that supports only v1=
 receives a packet with header (v2): If this node does not support a notifi=
cation procedure to inform the source that it does not support that header =
version, then FAILURES are introduced in the network. This is a degradation=
 of the service compared to legacy scheme to structure services. This is no=
t recommended, IMHO.</span><span style=3D"color:black"><o:p></o:p></span></=
pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; </span><span style=3D"color:black"><o:p>=
</o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; (c) If a notification is received from a=
n element about its supported version: a node can use another version (the =
logic to select other version is another point to discuss) for that communi=
cation, but what to do for the next flows in the context of the same servic=
e chain or other chains that involves these two nodes as adjacent elements =
in the same chain? Shouldn't these nodes cache the version to use for subse=
quent exchange to avoid receiving the notification error each time? Wouldn'=
t that complexity the behavior of the SFC-aware elements?</span><span style=
=3D"color:black"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; </span><span style=3D"color:black"><o:p>=
</o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; (d) If a notification is received from a=
n element about its supported version: As this may occurs in various segmen=
ts of a given service chain, e.g., (A(v1), B(v1,v2), C(v2), D(v1,v2), E(v1)=
). Notifying the adjacent node each time there is a version mismatch induce=
 an extra delay, that may be not be acceptable for every flow.</span><span =
style=3D"color:black"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; </span><span style=3D"color:black"><o:p>=
</o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; I hope this clarifies my initial concern=
.</span><span style=3D"color:black"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; </span><span style=3D"color:black"><o:p>=
</o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; Thank you.</span><span style=3D"color:bl=
ack"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; </span><span style=3D"color:black"><o:p>=
</o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; Cheers,</span><span style=3D"color:black=
"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; Med</span><span style=3D"color:black"><o=
:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; </span><span style=3D"color:black"><o:p>=
</o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt; -----Message d'origine-----</span><s=
pan style=3D"color:black"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt; De : Joel M. Halpern [<a href=3D"mai=
lto:jmh">mailto:jmh</a> at joelhalpern.com]</span><span style=3D"color:blac=
k"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt; Envoy=E9 : mercredi 25 f=E9vrier 201=
5 16:10</span><span style=3D"color:black"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt; =C0 : BOUCADAIR Mohamed IMT/OLN; pau=
lq at cisco.com</span><span style=3D"color:black"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt; Cc : sfc at ietf.org</span><span sty=
le=3D"color:black"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt; Objet : Re: [sfc] draft-quinn-sfc-ns=
h: version number</span><span style=3D"color:black"><o:p></o:p></span></pre=
>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt; </span><span style=3D"color:black"><=
o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt; I would really prefer to keep the ve=
rsion number.&nbsp; Even though we have</span><span style=3D"color:black"><=
o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt; the MD-type identifier and for some =
MD we have the TLVs.</span><span style=3D"color:black"><o:p></o:p></span></=
pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt; </span><span style=3D"color:black"><=
o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt; The reason is that we may want to ch=
ange the base header.&nbsp; For example,</span><span style=3D"color:black">=
<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt; suppose that the ciscussion about in=
cluding a flow identifier in the</span><span style=3D"color:black"><o:p></o=
:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt; base header had not come up now.&nbs=
p; If it came up later, we would want to</span><span style=3D"color:black">=
<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt; be able to have the discussion and m=
ake the choice, rather than being</span><span style=3D"color:black"><o:p></=
o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt; constrained by the lack of a version=
 field.</span><span style=3D"color:black"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt; </span><span style=3D"color:black"><=
o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt; Yours,</span><span style=3D"color:bl=
ack"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt; Joel</span><span style=3D"color:blac=
k"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt; </span><span style=3D"color:black"><=
o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt; </span><span style=3D"color:black"><=
o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt; On 2/25/15 10:03 AM, mohamed.boucada=
ir at orange.com wrote:</span><span style=3D"color:black"><o:p></o:p></span=
></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt;&gt; Hi Paul, all,</span><span style=
=3D"color:black"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt;&gt; </span><span style=3D"color:blac=
k"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt;&gt; What is the purpose of having a =
version number in the header? Is there a</span><span style=3D"color:black">=
<o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt;&gt; kind of version negotiation that=
 needs to be in place?</span><span style=3D"color:black"><o:p></o:p></span>=
</pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt;&gt; </span><span style=3D"color:blac=
k"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt;&gt; I checked the I-D but failed to =
find text that explains the rationale,</span><span style=3D"color:black"><o=
:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt;&gt; the use of the such field and wh=
ether an error will be returned if the</span><span style=3D"color:black"><o=
:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt;&gt; version is not supported by the =
receiving node.</span><span style=3D"color:black"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt;&gt; </span><span style=3D"color:blac=
k"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt;&gt; Wouldn't be preferable to get ri=
d of this field given that SFC header</span><span style=3D"color:black"><o:=
p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt;&gt; can be extended using optional o=
bjects and consistent setup &amp;</span><span style=3D"color:black"><o:p></=
o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt;&gt; configuration within an SFC-enab=
led domain should be assumed?</span><span style=3D"color:black"><o:p></o:p>=
</span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt;&gt; </span><span style=3D"color:blac=
k"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt;&gt; Thank you</span><span style=3D"c=
olor:black"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt;&gt; </span><span style=3D"color:blac=
k"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt;&gt; Cheers,</span><span style=3D"col=
or:black"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt;&gt; </span><span style=3D"color:blac=
k"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt;&gt; Med</span><span style=3D"color:b=
lack"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt;&gt; </span><span style=3D"color:blac=
k"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt;&gt; </span><span style=3D"color:blac=
k"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt;&gt; </span><span style=3D"color:blac=
k"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt;&gt; ________________________________=
_______________</span><span style=3D"color:black"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt;&gt; sfc mailing list</span><span sty=
le=3D"color:black"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt;&gt; sfc at ietf.org</span><span styl=
e=3D"color:black"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/=
mailman/listinfo/sfc">https://www.ietf.org/mailman/listinfo/sfc</a></span><=
span style=3D"color:black"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt;&gt;&gt; </span><span style=3D"color:blac=
k"><o:p></o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&gt;&gt; </span><span style=3D"color:black"><o:p>=
</o:p></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o=
:p></span></pre>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black">&nbsp;</s=
pan><span style=3D"color:black"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_787AE7BB302AE849A7480A190F8B933004926895OPEXCLILM23corp_--


From nobody Fri Mar  6 02:44:11 2015
Return-Path: <nick.heatley@ee.co.uk>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75B7B1A1BF3; Fri,  6 Mar 2015 02:44:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] autolearn=ham
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 IMsfi3qi24lL; Fri,  6 Mar 2015 02:44:08 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.146]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3AA8F1A1BB1; Fri,  6 Mar 2015 02:44:08 -0800 (PST)
Received: from [85.158.136.3] by server-10.bemta-5.messagelabs.com id 04/34-02756-6F489F45; Fri, 06 Mar 2015 10:44:06 +0000
X-Env-Sender: nick.heatley@ee.co.uk
X-Msg-Ref: server-14.tower-123.messagelabs.com!1425638646!37675470!1
X-Originating-IP: [149.254.241.76]
X-StarScan-Received: 
X-StarScan-Version: 6.13.4; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 7718 invoked from network); 6 Mar 2015 10:44:06 -0000
Received: from unknown (HELO smtpml01.ee.co.uk) (149.254.241.76) by server-14.tower-123.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP;  6 Mar 2015 10:44:06 -0000
Received: from EEUKWV0940.EEAD.EEINT.CO.UK (Not Verified[10.246.209.217]) by smtpml01.ee.co.uk with MailMarshal (v7, 2, 3, 6978) id <B54f984f00000>; Fri, 06 Mar 2015 10:44:00 +0000
Received: from UK31S005EXS02.EEAD.EEINT.CO.UK (Not Verified[10.246.208.27]) by EEUKWV0940.EEAD.EEINT.CO.UK with MailMarshal (v7, 2, 3, 6978) id <B54f984f50004>; Fri, 06 Mar 2015 10:44:05 +0000
Received: from UK30S005EXS06.EEAD.EEINT.CO.UK ([fe80::314c:b96c:4a9a:8a79]) by UK31S005EXS02.EEAD.EEINT.CO.UK ([2002:1ef6:d01b::1ef6:d01b]) with mapi id 14.03.0195.001; Fri, 6 Mar 2015 10:44:05 +0000
From: "Heatley, Nick" <nick.heatley@ee.co.uk>
To: "spring@ietf.org" <spring@ietf.org>
Thread-Topic: [spring] I-D Action: draft-ietf-spring-ipv6-use-cases-04.txt - path-cache-reflector?
Thread-Index: AdBX93lqJn3yJ92vTo+izeN21OjuUw==
Date: Fri, 6 Mar 2015 10:44:05 +0000
Message-ID: <6536E263028723489CCD5B6821D4B21303E0F350@UK30S005EXS06.EEAD.EEINT.CO.UK>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.246.208.5]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/39ysULK2Xm0nk0Q-bjPf-Tei0ik>
Cc: "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] [spring] I-D Action: draft-ietf-spring-ipv6-use-cases-04.txt - path-cache-reflector?
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 06 Mar 2015 10:44:10 -0000

SGkgYXV0aG9ycywgdGhpcyBkcmFmdCBpcyB2ZXJ5IGludGVyZXN0aW5nLCB0aGFuayB5b3UuDQoN
CkNvbnNpZGVyIGEgbW9iaWxlIG9wZXJhdG9yIHBlcnNwZWN0aXZlLCBJIHdhcyBpbnRlcmVzdGVk
IGluIHRoZSBjb21tZW50IHdpdGhpbiB0aGUgZHJhZnQgcmVnYXJkaW5nIG1ha2luZyBhIHNvdXJj
ZSBwYXRoIGRlY2lzaW9uIHdpdGhvdXQgcmVxdWlyaW5nIGZ1bGwgRFBJLg0KQ291bGQgdGhlcmUg
YmUgc3VjaCBhIHRoaW5nIGFzIGEgYm9yZGVyICJwYXRoLWNhY2hlLXJlZmxlY3RvciIgZnVuY3Rp
b24/DQpUaGUgZWdyZXNzIG5vZGUsIGluIGFkZGl0aW9uIHRvIGNsZWFuaW5nIHVwIHRoZSBoZWFk
ZXIsIGNvdWxkIHBlcmZvcm0gYWRkaXRpb25hbCBmdW5jdGlvbnM6IFRoZSBwYXRoIGlzIGR5bmFt
aWNhbGx5IGNhY2hlZCBmb3IgYSBzaG9ydCB3aGlsZSAocG90ZW50aWFsbHkgYWxzbyBOU0gpLCBh
bmQgdXNpbmcgYSBtb3JlIHNpbXBsZSBTUEksIHRoZSByZXR1cm4gdHJhZmZpYyBjb3VsZCBiZSBy
ZWZsZWN0ZWQgZG93biBhIHN5bW1ldHJpYyBwYXRoLCBieSByZXZlcnNpbmcgdGhlIHNlZ21lbnRz
Pw0KRm9yIG1lLCB0aGUgZ29hbCB3b3VsZCBiZSB0byB1c2UgU1BJIGZvciBpbmdyZXNzIG9mIHJl
dHVybiB0cmFmZmljIGFuZCBzaW1wbGVyIHByb2Nlc3NlcyBhdCB0aGUgYm9yZGVyIG5vZGUsIHJh
dGhlciB0aGFuIHJlc29ydGluZyB0byBEUEkgYW5kICJmdWxsIHNlcnZpY2UgYXdhcmVuZXNzIiB0
byBjbGFzc2lmeSBpbmNvbWluZyB0cmFmZmljLCB3aGVuIGNyZWF0aW5nIGEgc3ltbWV0cmljIHJl
dHVybiBwYXRoLiBDb3VsZCB0aGlzIGJlIGFjaGlldmVkPyBUaGlzIHdvdWxkIGJlIGFuIGludGVy
ZXN0aW5nIHNjZW5hcmlvIG9yIHVzZSBjYXNlOyBhcyBmYXIgYXMgSSBjYW4gdGVsbCBpdCBpcyBu
b3Qgc3RyaWN0bHkgYXZhaWxhYmxlIGluIGFuIE1QTFMgZW52aXJvbm1lbnQuDQoNClBlcmhhcHMg
dGhpcyBoYXMgYWxyZWFkeSBiZWVuIGRpc2N1c3NlZCBpbiBzYXkgU0ZDLCBJIGRvbid0IGtub3cu
IFBlcmhhcHMgdGhlcmUgYXJlIGlzc3VlcyBoZXJlPw0KSSBhbSBvbmx5IGp1c3QgZGlzY292ZXJp
bmcgdGhlc2UgZHJhZnRzLCBzbyBwbGVhc2UgYmUgZ2VudGxlLg0KUmVnYXJkcywNCk5pY2sgDQoN
Cg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IHNwcmluZyBbbWFpbHRvOnNwcmlu
Zy1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgaW50ZXJuZXQtZHJhZnRzQGlldGYub3Jn
DQpTZW50OiAwNiBNYXJjaCAyMDE1IDA5OjI3DQpUbzogaS1kLWFubm91bmNlQGlldGYub3JnDQpD
Yzogc3ByaW5nQGlldGYub3JnDQpTdWJqZWN0OiBbc3ByaW5nXSBJLUQgQWN0aW9uOiBkcmFmdC1p
ZXRmLXNwcmluZy1pcHY2LXVzZS1jYXNlcy0wNC50eHQNCg0KDQpBIE5ldyBJbnRlcm5ldC1EcmFm
dCBpcyBhdmFpbGFibGUgZnJvbSB0aGUgb24tbGluZSBJbnRlcm5ldC1EcmFmdHMgZGlyZWN0b3Jp
ZXMuDQogVGhpcyBkcmFmdCBpcyBhIHdvcmsgaXRlbSBvZiB0aGUgU291cmNlIFBhY2tldCBSb3V0
aW5nIGluIE5ldHdvcmtpbmcgV29ya2luZyBHcm91cCBvZiB0aGUgSUVURi4NCg0KICAgICAgICBU
aXRsZSAgICAgICAgICAgOiBJUHY2IFNQUklORyBVc2UgQ2FzZXMNCiAgICAgICAgQXV0aG9ycyAg
ICAgICAgIDogSm9obiBCcnpvem93c2tpDQogICAgICAgICAgICAgICAgICAgICAgICAgIEpvaG4g
TGVkZHkNCiAgICAgICAgICAgICAgICAgICAgICAgICAgSWRhIExldW5nDQogICAgICAgICAgICAg
ICAgICAgICAgICAgIFN0ZWZhbm8gUHJldmlkaQ0KICAgICAgICAgICAgICAgICAgICAgICAgICBN
YXJrIFRvd25zbGV5DQogICAgICAgICAgICAgICAgICAgICAgICAgIENocmlzdGlhbiBNYXJ0aW4N
CiAgICAgICAgICAgICAgICAgICAgICAgICAgQ2xhcmVuY2UgRmlsc2ZpbHMNCiAgICAgICAgICAg
ICAgICAgICAgICAgICAgUm9iZXJ0YSBNYWdsaW9uZQ0KCUZpbGVuYW1lICAgICAgICA6IGRyYWZ0
LWlldGYtc3ByaW5nLWlwdjYtdXNlLWNhc2VzLTA0LnR4dA0KCVBhZ2VzICAgICAgICAgICA6IDEz
DQoJRGF0ZSAgICAgICAgICAgIDogMjAxNS0wMy0wNg0KDQpBYnN0cmFjdDoNCiAgIFNvdXJjZSBQ
YWNrZXQgUm91dGluZyBpbiBOZXR3b3JraW5nIChTUFJJTkcpIGFyY2hpdGVjdHVyZSBsZXZlcmFn
ZXMNCiAgIHRoZSBzb3VyY2Ugcm91dGluZyBwYXJhZGlnbS4gIEEgbm9kZSBzdGVlcnMgYSBwYWNr
ZXQgdGhyb3VnaCBhDQogICBjb250cm9sbGVkIHNldCBvZiBpbnN0cnVjdGlvbnMsIGNhbGxlZCBz
ZWdtZW50cywgYnkgcHJlcGVuZGluZyB0aGUNCiAgIHBhY2tldCB3aXRoIFNQUklORyBoZWFkZXIu
ICBBIHNlZ21lbnQgY2FuIHJlcHJlc2VudCBhbnkgaW5zdHJ1Y3Rpb24sDQogICB0b3BvbG9naWNh
bCBvciBzZXJ2aWNlLWJhc2VkLiAgQSBzZWdtZW50IGNhbiBoYXZlIGEgbG9jYWwgc2VtYW50aWMg
dG8NCiAgIHRoZSBTUFJJTkcgbm9kZSBvciBnbG9iYWwgd2l0aGluIHRoZSBTUFJJTkcgZG9tYWlu
LiAgU1BSSU5HIGFsbG93cyB0bw0KICAgZW5mb3JjZSBhIGZsb3cgdGhyb3VnaCBhbnkgdG9wb2xv
Z2ljYWwgcGF0aCBhbmQgc2VydmljZSBjaGFpbiB3aGlsZQ0KICAgbWFpbnRhaW5pbmcgcGVyLWZs
b3cgc3RhdGUgb25seSBhdCB0aGUgaW5ncmVzcyBub2RlIHRvIHRoZSBTUFJJTkcNCiAgIGRvbWFp
bi4NCg0KICAgVGhlIG9iamVjdGl2ZSBvZiB0aGlzIGRvY3VtZW50IGlzIHRvIGlsbHVzdHJhdGUg
c29tZSB1c2UgY2FzZXMgdGhhdA0KICAgbmVlZCB0byBiZSB0YWtlbiBpbnRvIGFjY291bnQgYnkg
dGhlIFNvdXJjZSBQYWNrZXQgUm91dGluZyBpbg0KICAgTmV0d29ya2luZyAoU1BSSU5HKSBhcmNo
aXRlY3R1cmUuDQoNCg0KVGhlIElFVEYgZGF0YXRyYWNrZXIgc3RhdHVzIHBhZ2UgZm9yIHRoaXMg
ZHJhZnQgaXM6DQpodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLXNw
cmluZy1pcHY2LXVzZS1jYXNlcy8NCg0KVGhlcmUncyBhbHNvIGEgaHRtbGl6ZWQgdmVyc2lvbiBh
dmFpbGFibGUgYXQ6DQpodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLXNwcmlu
Zy1pcHY2LXVzZS1jYXNlcy0wNA0KDQpBIGRpZmYgZnJvbSB0aGUgcHJldmlvdXMgdmVyc2lvbiBp
cyBhdmFpbGFibGUgYXQ6DQpodHRwOi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJsMj1kcmFmdC1p
ZXRmLXNwcmluZy1pcHY2LXVzZS1jYXNlcy0wNA0KDQoNClBsZWFzZSBub3RlIHRoYXQgaXQgbWF5
IHRha2UgYSBjb3VwbGUgb2YgbWludXRlcyBmcm9tIHRoZSB0aW1lIG9mIHN1Ym1pc3Npb24gdW50
aWwgdGhlIGh0bWxpemVkIHZlcnNpb24gYW5kIGRpZmYgYXJlIGF2YWlsYWJsZSBhdCB0b29scy5p
ZXRmLm9yZy4NCg0KSW50ZXJuZXQtRHJhZnRzIGFyZSBhbHNvIGF2YWlsYWJsZSBieSBhbm9ueW1v
dXMgRlRQIGF0Og0KZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy8NCg0KX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCnNwcmluZyBtYWlsaW5n
IGxpc3QNCnNwcmluZ0BpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby9zcHJpbmcNCg0KTk9USUNFIEFORCBESVNDTEFJTUVSDQpUaGlzIGUtbWFpbCAoaW5jbHVk
aW5nIGFueSBhdHRhY2htZW50cykgaXMgaW50ZW5kZWQgZm9yIHRoZSBhYm92ZS1uYW1lZCBwZXJz
b24ocykuICBJZiB5b3UgYXJlIG5vdCB0aGUgaW50ZW5kZWQgcmVjaXBpZW50LCBub3RpZnkgdGhl
IHNlbmRlciBpbW1lZGlhdGVseSwgZGVsZXRlIHRoaXMgZW1haWwgZnJvbSB5b3VyIHN5c3RlbSBh
bmQgZG8gbm90IGRpc2Nsb3NlIG9yIHVzZSBmb3IgYW55IHB1cnBvc2UuICANCiANCldlIG1heSBt
b25pdG9yIGFsbCBpbmNvbWluZyBhbmQgb3V0Z29pbmcgZW1haWxzIGluIGxpbmUgd2l0aCBjdXJy
ZW50IGxlZ2lzbGF0aW9uLiBXZSBoYXZlIHRha2VuIHN0ZXBzIHRvIGVuc3VyZSB0aGF0IHRoaXMg
ZW1haWwgYW5kIGF0dGFjaG1lbnRzIGFyZSBmcmVlIGZyb20gYW55IHZpcnVzLCBidXQgaXQgcmVt
YWlucyB5b3VyIHJlc3BvbnNpYmlsaXR5IHRvIGVuc3VyZSB0aGF0IHZpcnVzZXMgZG8gbm90IGFk
dmVyc2VseSBhZmZlY3QgeW91LiANCg0KRUUgTGltaXRlZA0KUmVnaXN0ZXJlZCBpbiBFbmdsYW5k
IGFuZCBXYWxlcw0KQ29tcGFueSBSZWdpc3RlcmVkIE51bWJlcjogMDIzODIxNjENClJlZ2lzdGVy
ZWQgT2ZmaWNlIEFkZHJlc3M6IFRyaWRlbnQgUGxhY2UsIE1vc3F1aXRvIFdheSwgSGF0ZmllbGQs
IEhlcnRmb3Jkc2hpcmUsIEFMMTAgOUJXLg0K


From nobody Fri Mar  6 03:32:46 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2AEE1ACD7F; Fri,  6 Mar 2015 03:32:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 FSbj81npBFef; Fri,  6 Mar 2015 03:32:41 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BE9E81A00CC; Fri,  6 Mar 2015 03:32:41 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.12.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150306113241.5391.54328.idtracker@ietfa.amsl.com>
Date: Fri, 06 Mar 2015 03:32:41 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/h3nqG34mpN9wCCcW5DdZJbZ5ivs>
Cc: sfc@ietf.org
Subject: [sfc] I-D Action: draft-ietf-sfc-architecture-06.txt
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 06 Mar 2015 11:32:43 -0000

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           : Service Function Chaining (SFC) Architecture
        Authors         : Joel Halpern
                          Carlos Pignataro
	Filename        : draft-ietf-sfc-architecture-06.txt
	Pages           : 28
	Date            : 2015-03-06

Abstract:
   This document describes an architecture for the specification,
   creation, and ongoing maintenance of Service Function Chains (SFC) in
   a network.  It includes architectural concepts, principles, and
   components used in the construction of composite services through
   deployment of SFCs, with a focus on those to be standardized in the
   IETF.  This document does not propose solutions, protocols, or
   extensions to existing protocols.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-sfc-architecture/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-sfc-architecture-06

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-sfc-architecture-06


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Fri Mar  6 03:45:45 2015
Return-Path: <sprevidi@cisco.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7943A1ACD8B; Fri,  6 Mar 2015 03:45:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 rWs4IBruvRk6; Fri,  6 Mar 2015 03:45:42 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A8B41ACD8A; Fri,  6 Mar 2015 03:45:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5366; q=dns/txt; s=iport; t=1425642342; x=1426851942; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=y6Xn81rU/RurcWxqToy2uCllCSG76/ayJo4IJF52iUw=; b=BQCnCDAWVimLlniQthLaRq9CIlOv0djA2MILOB0AyMIP8z0QTPhaTvlv Y2s29Kufcclgf82aP6g8GuH7EwHsMx+LSynnsmdS+94crpckTl+PooUod XbNN8rX6K5UBGzI4uyH9G1BzRxvQniWjNwi0EPObDWL6j+IBhtNohkEl5 Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DJBgAZk/lU/5FdJa1cgwZSVQUEvzWCLAqFJ0kCgT1NAQEBAQEBfIQPAQEBAwEBAQE3NAsFBwQCAQgRAQMBAQEVCQkHJwsUAwYIAQEEDgUJiB4ICAXPMgEBAQEBAQEBAQEBAQEBAQEBAQEBAReLF4QMCgcBHTMHBgSDDYEUBZAHg2ODb4F7gRoRKIJti22DQiOCMoE8b4ECCRcifwEBAQ
X-IronPort-AV: E=Sophos;i="5.11,352,1422921600"; d="scan'208";a="401410426"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by rcdn-iport-5.cisco.com with ESMTP; 06 Mar 2015 11:45:41 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id t26BjftL007662 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 6 Mar 2015 11:45:41 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.159]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.03.0195.001; Fri, 6 Mar 2015 05:45:41 -0600
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: "Heatley, Nick" <nick.heatley@ee.co.uk>
Thread-Topic: [sfc] [spring] I-D Action: draft-ietf-spring-ipv6-use-cases-04.txt - path-cache-reflector?
Thread-Index: AdBX93lqJn3yJ92vTo+izeN21OjuUwAPeEqA
Date: Fri, 6 Mar 2015 11:45:41 +0000
Message-ID: <1972E2D2-7807-49F3-AD49-EF744DA9B7A0@cisco.com>
References: <6536E263028723489CCD5B6821D4B21303E0F350@UK30S005EXS06.EEAD.EEINT.CO.UK>
In-Reply-To: <6536E263028723489CCD5B6821D4B21303E0F350@UK30S005EXS06.EEAD.EEINT.CO.UK>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.61.222.242]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <9B9147CD45F2974BBA8716D4ADD8A418@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/MdaWTPXuc74FosBqMMePaLIp_wM>
Cc: "spring@ietf.org" <spring@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] [spring] I-D Action: draft-ietf-spring-ipv6-use-cases-04.txt - path-cache-reflector?
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 06 Mar 2015 11:45:44 -0000

On Mar 6, 2015, at 11:44 AM, "Heatley, Nick" <nick.heatley@ee.co.uk> wrote:
> Hi authors, this draft is very interesting, thank you.
>=20
> Consider a mobile operator perspective, I was interested in the comment w=
ithin the draft regarding making a source path decision without requiring f=
ull DPI.
> Could there be such a thing as a border "path-cache-reflector" function?
> The egress node, in addition to cleaning up the header, could perform add=
itional functions: The path is dynamically cached for a short while (potent=
ially also NSH), and using a more simple SPI, the return traffic could be r=
eflected down a symmetric path, by reversing the segments?


well, for sure there's nothing that prevents an implementation from doing s=
o. This specific point (reversing the segment list) has ben mentioned alrea=
dy a couple of times.=20

segment routing for v6 dataplane has the nice property of preserving the se=
gment list so it makes you scenario doable.


> For me, the goal would be to use SPI for ingress of return traffic and si=
mpler processes at the border node, rather than resorting to DPI and "full =
service awareness" to classify incoming traffic, when creating a symmetric =
return path. Could this be achieved? This would be an interesting scenario =
or use case; as far as I can tell it is not strictly available in an MPLS e=
nvironment.


it is possible but it would require some state to be kept if the node rever=
sing the segment list is not the destination of the packet. IOW if the reve=
rsing has to happen outside the service/application context.=20


> Perhaps this has already been discussed in say SFC, I don't know. Perhaps=
 there are issues here?
> I am only just discovering these drafts, so please be gentle.


too late... you're in the dark side now... ;-)

s.


> Regards,
> Nick=20
>=20
>=20
> -----Original Message-----
> From: spring [mailto:spring-bounces@ietf.org] On Behalf Of internet-draft=
s@ietf.org
> Sent: 06 March 2015 09:27
> To: i-d-announce@ietf.org
> Cc: spring@ietf.org
> Subject: [spring] I-D Action: draft-ietf-spring-ipv6-use-cases-04.txt
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
> This draft is a work item of the Source Packet Routing in Networking Work=
ing Group of the IETF.
>=20
>        Title           : IPv6 SPRING Use Cases
>        Authors         : John Brzozowski
>                          John Leddy
>                          Ida Leung
>                          Stefano Previdi
>                          Mark Townsley
>                          Christian Martin
>                          Clarence Filsfils
>                          Roberta Maglione
> 	Filename        : draft-ietf-spring-ipv6-use-cases-04.txt
> 	Pages           : 13
> 	Date            : 2015-03-06
>=20
> Abstract:
>   Source Packet Routing in Networking (SPRING) architecture leverages
>   the source routing paradigm.  A node steers a packet through a
>   controlled set of instructions, called segments, by prepending the
>   packet with SPRING header.  A segment can represent any instruction,
>   topological or service-based.  A segment can have a local semantic to
>   the SPRING node or global within the SPRING domain.  SPRING allows to
>   enforce a flow through any topological path and service chain while
>   maintaining per-flow state only at the ingress node to the SPRING
>   domain.
>=20
>   The objective of this document is to illustrate some use cases that
>   need to be taken into account by the Source Packet Routing in
>   Networking (SPRING) architecture.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-spring-ipv6-use-cases/
>=20
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-spring-ipv6-use-cases-04
>=20
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-spring-ipv6-use-cases-04
>=20
>=20
> Please note that it may take a couple of minutes from the time of submiss=
ion until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>=20
> NOTICE AND DISCLAIMER
> This e-mail (including any attachments) is intended for the above-named p=
erson(s).  If you are not the intended recipient, notify the sender immedia=
tely, delete this email from your system and do not disclose or use for any=
 purpose. =20
>=20
> We may monitor all incoming and outgoing emails in line with current legi=
slation. We have taken steps to ensure that this email and attachments are =
free from any virus, but it remains your responsibility to ensure that viru=
ses do not adversely affect you.=20
>=20
> EE Limited
> Registered in England and Wales
> Company Registered Number: 02382161
> Registered Office Address: Trident Place, Mosquito Way, Hatfield, Hertfor=
dshire, AL10 9BW.
> _______________________________________________
> sfc mailing list
> sfc@ietf.org
> https://www.ietf.org/mailman/listinfo/sfc


From nobody Fri Mar  6 07:54:03 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5E6A1ACED1; Fri,  6 Mar 2015 07:54:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 fAzwLLQYCJdR; Fri,  6 Mar 2015 07:54:00 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CF8231ACEDA; Fri,  6 Mar 2015 07:53:58 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.12.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150306155358.20292.61156.idtracker@ietfa.amsl.com>
Date: Fri, 06 Mar 2015 07:53:58 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/8bbmWLUkfJ53uXqJKwnRhx3J0fs>
Cc: sfc@ietf.org
Subject: [sfc] I-D Action: draft-ietf-sfc-architecture-07.txt
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 06 Mar 2015 15:54:02 -0000

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           : Service Function Chaining (SFC) Architecture
        Authors         : Joel Halpern
                          Carlos Pignataro
	Filename        : draft-ietf-sfc-architecture-07.txt
	Pages           : 28
	Date            : 2015-03-06

Abstract:
   This document describes an architecture for the specification,
   creation, and ongoing maintenance of Service Function Chains (SFC) in
   a network.  It includes architectural concepts, principles, and
   components used in the construction of composite services through
   deployment of SFCs, with a focus on those to be standardized in the
   IETF.  This document does not propose solutions, protocols, or
   extensions to existing protocols.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-sfc-architecture/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-sfc-architecture-07

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-sfc-architecture-07


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Fri Mar  6 15:48:50 2015
Return-Path: <linda.dunbar@huawei.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DA211A870D for <sfc@ietfa.amsl.com>; Fri,  6 Mar 2015 15:48:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 b-QYekTe7uMj for <sfc@ietfa.amsl.com>; Fri,  6 Mar 2015 15:48:48 -0800 (PST)
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 840EC1A1C06 for <sfc@ietf.org>; Fri,  6 Mar 2015 15:48:47 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BPY99854; Fri, 06 Mar 2015 23:48:45 +0000 (GMT)
Received: from DFWEML704-CHM.china.huawei.com (10.193.5.141) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 6 Mar 2015 23:48:45 +0000
Received: from DFWEML701-CHM.china.huawei.com ([10.193.5.50]) by dfweml704-chm ([10.193.5.141]) with mapi id 14.03.0158.001; Fri, 6 Mar 2015 15:48:41 -0800
From: Linda Dunbar <linda.dunbar@huawei.com>
To: "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: New Version Notification for draft-dunbar-sfc-path-control-01.txt
Thread-Index: AQHQWGegjwdzu6A4P0SimP9Os9x5o50QHotg
Date: Fri, 6 Mar 2015 23:48:40 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F645EEA52E@dfweml701-chm>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.192.11.206]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/wvyzCiuv_6UoWCeVs1_ynFTrV6k>
Subject: [sfc] FW: New Version Notification for draft-dunbar-sfc-path-control-01.txt
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 06 Mar 2015 23:48:49 -0000

VGhvdWdoIHdlIGRpZG4ndCBnZXQgY2hhbmNlIHRvIHByZXNlbnQgdGhpcyBTZXJ2aWNlIEZ1bmN0
aW9uIFBhdGggQ29udHJvbCBtZXRob2QgYXQgdGhlIGxhc3QgU0ZDIEZhY2UgdG8gRmFjZSBzZXNz
aW9uLCB3ZSBoYWQgc29tZSBvZmZsaW5lIGRpc2N1c3Npb24gd2l0aCBzZXZlcmFsIHBlb3BsZS4N
Cg0KV2UgdXBkYXRlZCB0aGUgZHJhZnQgdG8gYWRkcmVzcyB0aGUgY29tbWVudHMgYW5kIHN1Z2dl
c3Rpb25zIHNvIGZhci4gDQoNCkFwcHJlY2lhdGUgbW9yZSBjb21tZW50cyBhbmQgc3VnZ2VzdGlv
bi4gSG9wZSBTRkMgV0cgc2Vzc2lvbiBpbiBEYWxsYXMgd2lsbCBhbGxvY2F0ZSBzb21lIHRpbWUg
Zm9yIHRoZSBTRkMgY29udHJvbCBwbGFuZS4gDQoNCkxpbmRhIA0KDQotLS0tLU9yaWdpbmFsIE1l
c3NhZ2UtLS0tLQ0KRnJvbTogaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnIFttYWlsdG86aW50ZXJu
ZXQtZHJhZnRzQGlldGYub3JnXSANClNlbnQ6IEZyaWRheSwgTWFyY2ggMDYsIDIwMTUgNTo0NSBQ
TQ0KVG86IEFuZHJldyBHLiBNYWxpczsgTGluZGEgRHVuYmFyOyBBbmRyZXcgRy4gTWFsaXM7IExp
bmRhIER1bmJhcg0KU3ViamVjdDogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC1k
dW5iYXItc2ZjLXBhdGgtY29udHJvbC0wMS50eHQNCg0KDQpBIG5ldyB2ZXJzaW9uIG9mIEktRCwg
ZHJhZnQtZHVuYmFyLXNmYy1wYXRoLWNvbnRyb2wtMDEudHh0DQpoYXMgYmVlbiBzdWNjZXNzZnVs
bHkgc3VibWl0dGVkIGJ5IExpbmRhIER1bmJhciBhbmQgcG9zdGVkIHRvIHRoZSBJRVRGIHJlcG9z
aXRvcnkuDQoNCk5hbWU6CQlkcmFmdC1kdW5iYXItc2ZjLXBhdGgtY29udHJvbA0KUmV2aXNpb246
CTAxDQpUaXRsZToJCUZyYW1ld29yayBmb3IgU2VydmljZSBGdW5jdGlvbiBQYXRoIENvbnRyb2wN
CkRvY3VtZW50IGRhdGU6CTIwMTUtMDMtMDYNCkdyb3VwOgkJSW5kaXZpZHVhbCBTdWJtaXNzaW9u
DQpQYWdlczoJCTE3DQpVUkw6ICAgICAgICAgICAgaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5l
dC1kcmFmdHMvZHJhZnQtZHVuYmFyLXNmYy1wYXRoLWNvbnRyb2wtMDEudHh0DQpTdGF0dXM6ICAg
ICAgICAgaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtZHVuYmFyLXNmYy1w
YXRoLWNvbnRyb2wvDQpIdG1saXplZDogICAgICAgaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwv
ZHJhZnQtZHVuYmFyLXNmYy1wYXRoLWNvbnRyb2wtMDENCkRpZmY6ICAgICAgICAgICBodHRwOi8v
d3d3LmlldGYub3JnL3JmY2RpZmY/dXJsMj1kcmFmdC1kdW5iYXItc2ZjLXBhdGgtY29udHJvbC0w
MQ0KDQpBYnN0cmFjdDoNCiAgIFRoaXMgZHJhZnQgZGVzY3JpYmVzIHRoZSBmcmFtZXdvcmsgb2Yg
U2VydmljZSBGdW5jdGlvbiBQYXRoDQogICBDb250cm9sIHdoZW4gc29tZSBzZXJ2aWNlIGZ1bmN0
aW9ucyBvbiB0aGUgcGF0aCBmYWlsIG9yIG5lZWQgdG8gYmUNCiAgIHJlcGxhY2VkLg0KDQogICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgDQoNCg0KUGxlYXNlIG5vdGUgdGhhdCBpdCBtYXkgdGFrZSBh
IGNvdXBsZSBvZiBtaW51dGVzIGZyb20gdGhlIHRpbWUgb2Ygc3VibWlzc2lvbiB1bnRpbCB0aGUg
aHRtbGl6ZWQgdmVyc2lvbiBhbmQgZGlmZiBhcmUgYXZhaWxhYmxlIGF0IHRvb2xzLmlldGYub3Jn
Lg0KDQpUaGUgSUVURiBTZWNyZXRhcmlhdA0KDQo=


From nobody Sat Mar  7 00:06:42 2015
Return-Path: <davidme@marvell.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B3F01A8A39 for <sfc@ietfa.amsl.com>; Sat,  7 Mar 2015 00:06:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.266
X-Spam-Level: 
X-Spam-Status: No, score=-2.266 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 lsbCOMYvRYH6 for <sfc@ietfa.amsl.com>; Sat,  7 Mar 2015 00:06:38 -0800 (PST)
Received: from mx0b-0016f401.pphosted.com (mx0b-0016f401.pphosted.com [67.231.156.173]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA1151A8A3A for <sfc@ietf.org>; Sat,  7 Mar 2015 00:06:37 -0800 (PST)
Received: from pps.filterd (m0045851.ppops.net [127.0.0.1]) by mx0b-0016f401.pphosted.com (8.14.5/8.14.5) with SMTP id t27854TY019483 for <sfc@ietf.org>; Sat, 7 Mar 2015 00:06:37 -0800
Received: from sc-owa03.marvell.com ([199.233.58.149]) by mx0b-0016f401.pphosted.com with ESMTP id 1sy8u6kj1t-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <sfc@ietf.org>; Sat, 07 Mar 2015 00:06:36 -0800
Received: from IL-EXCH03.marvell.com (10.5.102.220) by SC-OWA03.marvell.com (10.93.76.24) with Microsoft SMTP Server (TLS) id 8.3.327.1; Sat, 7 Mar 2015 00:06:35 -0800
Received: from IL-EXCH03.marvell.com (10.5.102.220) by IL-EXCH03.marvell.com (10.5.102.220) with Microsoft SMTP Server (TLS) id 15.0.1044.25; Sat, 7 Mar 2015 10:06:32 +0200
Received: from IL-EXCH03.marvell.com ([fe80::1d75:e674:6bb0:e7ee]) by IL-EXCH03.marvell.com ([fe80::1d75:e674:6bb0:e7ee%20]) with mapi id 15.00.1044.021; Sat, 7 Mar 2015 10:06:32 +0200
From: David Melman <davidme@marvell.com>
To: "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: [sfc] WG call for adoption of draft-quinn-sfc-nsh
Thread-Index: AdBYrKUtmIFos39RStS2QvvE5cnbKQ==
Date: Sat, 7 Mar 2015 08:06:31 +0000
Message-ID: <8fd266c366864bee82ecc9f9328da4a3@IL-EXCH03.marvell.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [199.203.130.14]
Content-Type: multipart/alternative; boundary="_000_8fd266c366864bee82ecc9f9328da4a3ILEXCH03marvellcom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.13.68, 1.0.33,  0.0.0000 definitions=2015-03-06_07:2015-03-06,2015-03-06,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1503070090
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/GB1d4yjHQk9jrP0Ql3g95gV4_qo>
Subject: [sfc]  WG call for adoption of draft-quinn-sfc-nsh
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sat, 07 Mar 2015 08:06:40 -0000

--_000_8fd266c366864bee82ecc9f9328da4a3ILEXCH03marvellcom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Support draft-quinn-sfc-nsh as co-author.

David Melman

________________________________

  *   From: "Jim Guichard (jguichar)" <jguichar at cisco.com<mailto:jguicha=
r@DOMAIN.HIDDEN>>
  *   To: "sfc at ietf.org<mailto:sfc@DOMAIN.HIDDEN>" <sfc at ietf.org<mail=
to:sfc@DOMAIN.HIDDEN>>
  *   Date: Thu, 26 Feb 2015 12:47:03 +0000
  *   List-id: Network Service Chaining <sfc.ietf.org>

________________________________
Greetings WG:

The document draft-quinn-sfc-nsh-07 (https://datatracker.ietf.org/doc/draft=
-quinn-sfc-nsh/) has recently been reissued. The authors of draft-zhang-sfc=
-sch-03 (http://datatracker.ietf.org/doc/draft-zhang-sfc-sch/) have joined =
the NSH document so that the WG can focus on a single encapsulation documen=
t going forward. This new version of NSH includes an open items section bas=
ed on discussion between co-authors and members of the list. The WG will wo=
rk through this list (and any other issues that need to be added) over the =
next weeks. We appreciate and recognize the hard work of both the NSH and S=
CH authors in pushing the SFC encapsulation work forward.

With that said, the chairs are calling for WG adoption of draft-quinn-sfc-n=
sh-07 as a WG document. The call for adoption will run for 2 weeks ending 3=
/12/2015.

Please note that this is a call for adoption, and not a last call for conte=
nt of the document. Adopting a WG document simply means that the WG will fo=
cus its efforts on that particular draft going forward, and use that docume=
nt for resolving open issues and documenting the WG's decisions.

Please indicate whether you support adoption for not, and if not why. Issue=
s you have with the current document itself can also be raised, but they sh=
ould be raised in the context of what should be changed in the document goi=
ng forward, rather than a pre-condition for adoption.

Finally, now is also a good time to poll for knowledge of any IPR that appl=
ies to this draft, in line with the IPR disclosure obligations for WG parti=
cipants (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are l=
isted as a document author please respond to this email (to the chairs) whe=
ther or not you are aware of any relevant IPR.

Jim & Thomas

________________________________


--_000_8fd266c366864bee82ecc9f9328da4a3ILEXCH03marvellcom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
h1
	{mso-style-priority:9;
	mso-style-link:"Heading 1 Char";
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:24.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.Heading1Char
	{mso-style-name:"Heading 1 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 1";
	font-family:"Times New Roman","serif";
	font-weight:bold;}
span.apple-converted-space
	{mso-style-name:apple-converted-space;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1820729794;
	mso-list-template-ids:-1979972074;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Support draft-quinn-sfc-nsh as co-author.<o:p></o:p>=
</p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">David Melman<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"100%" noshade=3D"" style=3D"color:black" align=3D"c=
enter">
</div>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"color:black;mso-margin-top-alt:auto;mso-ma=
rgin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<em><span style=3D"font-size:13.5pt;font-family:&quot;Calibri&quot;,&quot;s=
ans-serif&quot;">From</span></em><span style=3D"font-size:13.5pt">: &quot;J=
im Guichard (jguichar)&quot; &lt;<a href=3D"mailto:jguichar@DOMAIN.HIDDEN">=
jguichar at cisco.com</a>&gt;<o:p></o:p></span></li><li class=3D"MsoNormal"=
 style=3D"color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;ms=
o-list:l0 level1 lfo1">
<em><span style=3D"font-size:13.5pt;font-family:&quot;Calibri&quot;,&quot;s=
ans-serif&quot;">To</span></em><span style=3D"font-size:13.5pt">: &quot;<a =
href=3D"mailto:sfc@DOMAIN.HIDDEN">sfc at ietf.org</a>&quot; &lt;<a href=3D"=
mailto:sfc@DOMAIN.HIDDEN">sfc at ietf.org</a>&gt;<o:p></o:p></span></li><li=
 class=3D"MsoNormal" style=3D"color:black;mso-margin-top-alt:auto;mso-margi=
n-bottom-alt:auto;mso-list:l0 level1 lfo1">
<em><span style=3D"font-size:13.5pt;font-family:&quot;Calibri&quot;,&quot;s=
ans-serif&quot;">Date</span></em><span style=3D"font-size:13.5pt">: Thu, 26=
 Feb 2015 12:47:03 &#43;0000<o:p></o:p></span></li><li class=3D"MsoNormal" =
style=3D"color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso=
-list:l0 level1 lfo1">
<em><span style=3D"font-size:13.5pt;font-family:&quot;Calibri&quot;,&quot;s=
ans-serif&quot;">List-id</span></em><span style=3D"font-size:13.5pt">: Netw=
ork Service Chaining &lt;sfc.ietf.org&gt;<o:p></o:p></span></li></ul>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"100%" noshade=3D"" style=3D"color:black" align=3D"c=
enter">
</div>
<table class=3D"MsoNormalTable" border=3D"0" cellpadding=3D"0" width=3D"100=
%" style=3D"width:100.0%;orphans: auto;text-align:start;widows: auto;-webki=
t-text-stroke-width: 0px;word-spacing:0px">
<tbody>
<tr>
<td style=3D"padding:.75pt .75pt .75pt .75pt">
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt;font-family:Consolas;=
color:black">Greetings WG:</span><span style=3D"font-size:13.5pt;color:blac=
k"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:13.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt;font-family:Consolas;=
color:black">The document draft-quinn-sfc-nsh-07 (<a href=3D"https://datatr=
acker.ietf.org/doc/draft-quinn-sfc-nsh">https://datatracker.ietf.org/doc/dr=
aft-quinn-sfc-nsh</a>/) has recently been
 reissued. The authors of draft-zhang-sfc-sch-03 (<a href=3D"http://datatra=
cker.ietf.org/doc/draft-zhang-sfc-sch">http://datatracker.ietf.org/doc/draf=
t-zhang-sfc-sch</a>/) have joined the NSH document so that the WG can focus=
 on a single encapsulation document
 going forward. This new version of NSH includes an<span class=3D"apple-con=
verted-space">&nbsp;</span><b>open items<span class=3D"apple-converted-spac=
e">&nbsp;</span></b>section based on discussion between co-authors and memb=
ers of the list. The WG will work through this
 list (and any other issues that need to be added) over the next weeks. We =
appreciate and recognize the hard work of both the NSH and SCH authors in p=
ushing the SFC encapsulation work forward.</span><span style=3D"font-size:1=
3.5pt;color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:13.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt;font-family:Consolas;=
color:black">With that said, the chairs are calling for WG adoption of draf=
t-quinn-sfc-nsh-07 as a WG document. The call for adoption will run for 2 w=
eeks ending 3/12/2015.</span><span style=3D"font-size:13.5pt;color:black"><=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:13.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt;font-family:Consolas;=
color:black">Please note that this is a call for adoption, and not a last c=
all for content of the document. Adopting a WG document simply means that t=
he WG will focus its efforts on that
 particular draft going forward, and use that document for resolving open i=
ssues and documenting the WG&#8217;s decisions.</span><span style=3D"font-s=
ize:13.5pt;color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:13.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt;font-family:Consolas;=
color:black">Please indicate whether you support adoption for not, and if n=
ot why. Issues you have with the current document itself can also be raised=
, but they should be raised in the context
 of what should be changed in the document going forward, rather than a pre=
-condition for adoption.&nbsp;</span><span style=3D"font-size:13.5pt;color:=
black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:13.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt;font-family:Consolas;=
color:black">Finally, now is also a good time to poll for knowledge of any =
IPR that applies to this draft, in line with the IPR disclosure obligations=
 for WG participants (see RFCs 3979,
 4879, 3669 and 5378 for more details). If you are listed as a document aut=
hor please respond to this email (to the chairs) whether or not you are awa=
re of any relevant IPR.</span><span style=3D"font-size:13.5pt;color:black">=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:13.5pt;font-family:Consolas=
;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt;font-family:Consolas;=
color:black">Jim &amp; Thomas</span><span style=3D"font-size:13.5pt;font-fa=
mily:Consolas;color:black"><o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"100%" noshade=3D"" style=3D"color:black" align=3D"c=
enter">
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_8fd266c366864bee82ecc9f9328da4a3ILEXCH03marvellcom_--


From nobody Sun Mar  8 19:43:25 2015
Return-Path: <fuqiao1@outlook.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 937451A017C for <sfc@ietfa.amsl.com>; Sun,  8 Mar 2015 19:43:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.35
X-Spam-Level: 
X-Spam-Status: No, score=-1.35 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=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 4llA0dlYSx85 for <sfc@ietfa.amsl.com>; Sun,  8 Mar 2015 19:43:20 -0700 (PDT)
Received: from SNT004-OMC2S24.hotmail.com (snt004-omc2s24.hotmail.com [65.55.90.99]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D4D3A1A03A9 for <sfc@ietf.org>; Sun,  8 Mar 2015 19:43:17 -0700 (PDT)
Received: from SNT146-DS24 ([65.55.90.71]) by SNT004-OMC2S24.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751);  Sun, 8 Mar 2015 19:43:16 -0700
X-TMN: [kkSxL72H14Hvxb0I5N4N5Wg2y1RcRDWGDABcj8g/jQM=]
X-Originating-Email: [fuqiao1@outlook.com]
Message-ID: <SNT146-DS2473AA961E67F8A68BA9F0E81B0@phx.gbl>
From: Qiao Fu <fuqiao1@outlook.com>
To: <sfc@ietf.org>
Date: Mon, 9 Mar 2015 10:43:16 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AdBaEKGLwOFrfBNLRO21H9GoHORD5AAARRcA
Content-Language: zh-cn
X-OriginalArrivalTime: 09 Mar 2015 02:43:16.0873 (UTC) FILETIME=[CBCAEF90:01D05A12]
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/Ew-5PpRZOSeeuDCOOK68TFJ7Wfc>
Cc: 'weiqiang cheng' <chengweiqiang@chinamobile.com>, 'Hui Deng' <denghui@chinamobile.com>
Subject: [sfc] =?utf-8?b?6L2s5Y+ROiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9y?= =?utf-8?q?_draft-fu-sfc-transport-network-usecase-00=2Etxt?=
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 09 Mar 2015 02:43:22 -0000

Hi, all. A new draft about sfc usecase in the transport network is =
proposed as follows. This draft discusses about the architecture of the =
Virtual CPE usecase in the transport network, and can be easily extended =
to other sfc usecases. Possible extension of sfc classifier is also =
discussed to adapt the MPLS-TP packet in the transport network.
Your comments and suggestions will be more than welcome. Thank you!


-----=E9=82=AE=E4=BB=B6=E5=8E=9F=E4=BB=B6-----
=E5=8F=91=E4=BB=B6=E4=BA=BA: internet-drafts@ietf.org =
[mailto:internet-drafts@ietf.org]=20
=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2015=E5=B9=B43=E6=9C=889=E6=97=A5 =
10:28
=E6=94=B6=E4=BB=B6=E4=BA=BA: Qiao Fu; Qiao Fu; Weiqiang Cheng; Hui Deng; =
Weiqiang Cheng; Hui Deng
=E4=B8=BB=E9=A2=98: New Version Notification for =
draft-fu-sfc-transport-network-usecase-00.txt


A new version of I-D, draft-fu-sfc-transport-network-usecase-00.txt
has been successfully submitted by Qiao Fu and posted to the
IETF repository.

Name:		draft-fu-sfc-transport-network-usecase
Revision:	00
Title:		Usecase of SFC for VCPE in the transport network
Document date:	2015-03-05
Group:		Individual Submission
Pages:		7
URL:            =
http://www.ietf.org/internet-drafts/draft-fu-sfc-transport-network-usecas=
e-00.txt
Status:         =
https://datatracker.ietf.org/doc/draft-fu-sfc-transport-network-usecase/
Htmlized:       =
http://tools.ietf.org/html/draft-fu-sfc-transport-network-usecase-00


Abstract:
   This document proposes a usecase of Service Function Chaining(SFC) to
   realize Virtual Customer Premises Equipment (VCPE) in the transport
   network.  In this document, the concept of VCPE is introduced into
   the transport network to provide value-added services for the
   enterprise customers.  The SFC is used to realize the VCPE and chains
   different services according to the requirement of the customers.
   Such architecture can provide value-added and self-defined services
   to the customers.  In the meantime, SDN controller is utilized in the
   usecase to direct certain traffic flows to the VCPE.  This usecase
   provides a practical mechanism to offer value-added and self-defined
   services in the transport network without complicating the CPE
   devices or increase OPEX and CAPEX cost.

                                                                         =
        =20


Please note that it may take a couple of minutes from the time of =
submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat



From nobody Sun Mar  8 20:03:22 2015
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 138F41A0104; Sun,  8 Mar 2015 20:03:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 XNZzlVxvxGSO; Sun,  8 Mar 2015 20:03:17 -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 807D51A00ED; Sun,  8 Mar 2015 20:03:16 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BQA26455; Mon, 09 Mar 2015 03:03:14 +0000 (GMT)
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 9 Mar 2015 03:03:12 +0000
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.115]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.03.0158.001; Mon, 9 Mar 2015 11:03:00 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Xuxiaohu <xuxiaohu@huawei.com>, "Jim Guichard (jguichar)" <jguichar@cisco.com>, Ron Parker <Ron_Parker@affirmednetworks.com>
Thread-Topic: [sfc] New Version Notification for draft-xu-sfc-using-mpls-spring-02.txt
Thread-Index: AQHQV1aYsfxG7/vV/kuy6NqPt9ZGW50On1JwgATWzpA=
Date: Mon, 9 Mar 2015 03:03:00 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831127C@NKGEML512-MBS.china.huawei.com>
References: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0830F7C0@NKGEML512-MBS.china.huawei.com> <CDF2F015F4429F458815ED2A6C2B6B0B2E855978@MBX021-W3-CA-2.exch021.domain.local> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0830FC8E@NKGEML512-MBS.china.huawei.com> <34ECE28B-F7AB-4FB9-9CE1-06289FB739B4@affirmednetworks.com> <D11DD3D6.BD0C%jguichar@cisco.com> 
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.99.55]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/DYZZXiFXngdWITz-oXHq4STRn6Y>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "<spring@ietf.org>" <spring@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] New Version Notification for draft-xu-sfc-using-mpls-spring-02.txt
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 09 Mar 2015 03:03:20 -0000

Hi Jim,

I have remove those options which may cause changes to the MPLS architectur=
e in the latest version (http://tools.ietf.org/html/draft-xu-sfc-using-mpls=
-spring-03).=20

Best regards,
Xiaohu

> -----Original Message-----
> From: Xuxiaohu
> Sent: Friday, March 06, 2015 8:49 AM
> To: 'Jim Guichard (jguichar)'; Ron Parker
> Cc: mpls@ietf.org; <spring@ietf.org>; sfc@ietf.org
> Subject: RE: [sfc] New Version Notification for
> draft-xu-sfc-using-mpls-spring-02.txt
>=20
> Hi Jim,
>=20
> Understood.
>=20
> Best regards,
> Xiaohu
>=20
> > -----Original Message-----
> > From: Jim Guichard (jguichar) [mailto:jguichar@cisco.com]
> > Sent: Thursday, March 05, 2015 11:11 PM
> > To: Ron Parker; Xuxiaohu
> > Cc: mpls@ietf.org; <spring@ietf.org>; sfc@ietf.org
> > Subject: Re: [sfc] New Version Notification for
> > draft-xu-sfc-using-mpls-spring-02.txt
> >
> > Hi Xiaohu,
> >
> > Thomas and I read your latest draft and believe that you will need to
> > take it to the MPLS WG as a first step. There are a number of things
> > within the document that may require changes to the base MPLS
> > architecture and the SFC WG is not the right community to address
> > those. Given this we will not be able to consider this document in the
> > SFC WG without agreement from the broader MPLS community.
> >
> > Regards,
> >
> > Jim & Thomas
> >
> >
> > On 3/4/15, 9:20 PM, "Ron Parker" <Ron_Parker@affirmednetworks.com>
> > wrote:
> >
> > >I think it needs to be there between SFF's, too.  In the case where
> > >there is no metadata, you could argue that the data in NSH and the
> > >label stack are redundantly saying the same thing, but an
> > >optimization along these lines would not be justified, IMO.
> > >
> > >   Ron
> > >
> > >
> > >> On Mar 4, 2015, at 8:58 PM, Xuxiaohu <xuxiaohu@huawei.com> wrote:
> > >>
> > >> Hi Ron,
> > >>
> > >> Thanks a lot for your insightful comments and suggestions. By the
> > >>way, in the case where there is no need to deliver metadata, does it
> > >>mean the NSH just only needs to be contained the packets exchanged
> > >>between SFFs and SFs? In other words, the NSH is used as a way for
> > >>the SFF to retrieve the label stack which has been stripped by that S=
FF
> before.
> > >>
> > >> Best regards,
> > >> Xiaohu
> > >>
> > >>> -----Original Message-----
> > >>> From: Ron Parker [mailto:Ron_Parker@affirmednetworks.com]
> > >>> Sent: Thursday, March 05, 2015 12:41 AM
> > >>> To: Xuxiaohu; sfc@ietf.org; <spring@ietf.org>; mpls@ietf.org
> > >>> Subject: RE: [sfc] New Version Notification for
> > >>> draft-xu-sfc-using-mpls-spring-02.txt
> > >>>
> > >>> Xiaohu,
> > >>>
> > >>> I read your latest draft and I do see the elegance of describing a
> > >>>sequence of
> > >>> must-visit nodes as a stack of MPLS labels.   And I see that you've
> > >>>addressed
> > >>> the transport-independence requirement by stating that the MPLS
> > >>>frames could
> > >>> be carried within IP tunnels (i.e., MPLS in UDP, etc.).    But, I h=
ave
> > >>>a couple of
> > >>> issues that I suggest be addressed.
> > >>>
> > >>> First, the text is written as if the NSH header is optional and
> > >>>present only if
> > >>> metadata is required.    The SFC architecture is such that the NSH =
is
> > >>> mandatory.   I think this issue can be combined with the second iss=
ue
> > >>>that I'll
> > >>> raise below.
> > >>>
> > >>> Second, the notion is that the SFF's strip the label stack and
> > >>>then restore the
> > >>> label stack.    And since the text states that even when NSH is
> > >>>present, the SFP
> > >>> ID is not used, the only remaining basis to do this is flow
> > >>>learning in the SFF.
> > >>> While I think there are many reasons that may cause SFF's to
> > >>>utilize flow  learning advantageously, it should not be a
> > >>>fundamental necessity to realize an
> > >>> SFF, IMO.   But even if the SFF is a flow learner, this is still
> > >>>inadequate since the
> > >>> SF may change the 5-tuple (e.g., NAT) or may launch internally
> > >>>generated flows
> > >>> (e.g., HTTP proxy).   Both cases could not be satisfied by flow
> > >>>learning.
> > >>>
> > >>> What I suggest, instead, is a tighter coupling between the NSH
> > >>>header and the
> > >>> MPLS label stack.   That there be a 1:1 equivalency between {SFP ID=
,
> > >>>SFP hop
> > >>> index} and the label stack.   Thus, when the SFC-aware SF returns a
> > >>>packet to
> > >>> the SFF, the {SFP ID, SFP hop index} contained in the NSH be used
> > >>>to push the
> > >>> appropriate label stack onto the packet.    I believe this would br=
ing
> > >>>the
> > >>> approach into conformance with the SFC architectural requirements
> > >>>(mandatory NSH, transport independence) and would solve the
> > >>>problems with  flow learning identified above.
> > >>>
> > >>>   Ron
> > >>>
> > >>>
> > >>>
> > >>> -----Original Message-----
> > >>> From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of Xuxiaohu
> > >>> Sent: Tuesday, March 3, 2015 11:10 PM
> > >>> To: Xuxiaohu; sfc@ietf.org; <spring@ietf.org>; mpls@ietf.org
> > >>> Subject: Re: [sfc] New Version Notification for
> > >>> draft-xu-sfc-using-mpls-spring-02.txt
> > >>>
> > >>> The rationales for leveraging the MPLS-SPRING mechanism to realize
> > >>>the service  path layer functionality of the service function
> > >>>chaining are as
> > >>>follows:
> > >>>
> > >>> 1) eliminate the SFC/SFP states on SFFs. This follows the same
> > >>>logic as  MPLS-SPRING and BIER.
> > >>> 2) utilize the existing encapsulation (e.g., the MPLS-SPRING) to a
> > >>>maximum  extent. This follows the Transport Derived SFF concept as
> > >>>described in Section
> > >>> 4.3.1 of draft-ietf-sfc-architecture. Meanwhile, this is aligned
> > >>>with the current  SFC charter, e.g., "...The working group will
> > >>>consider using an existing  encapsulation (with extensions as
> > >>>appropriate) if a suitable candidate is found..."
> > >>> 3) seamlessly support the SFC in a multi-tenant environment (e.g.,
> > >>>MPLS VPN).
> > >>> For example, the MPLS VPN packet (containing metadata) could be
> > >>>further  imposed with a label stack which indicates an SFC or SFP
> > >>>associated with that  packet. SFFs receiving the above packet would
> > >>>strip the whole label stack and  then send the payload of the MPLS
> > >>>packet (with metadata) to the corresponding  SFs which are
> > >>>tenant-aware and therefore easily could determine the tenant
> > >>>profile according to the tenant info contained in the metadata
> > >>>(a.k.a., the NSH).
> > >>>
> > >>> Best regards,
> > >>> Xiaohu
> > >>>
> > >>>
> > >>>> -----Original Message-----
> > >>>> From: Xuxiaohu
> > >>>> Sent: Wednesday, March 04, 2015 11:31 AM
> > >>>> To: sfc@ietf.org; '<spring@ietf.org>'; mpls@ietf.org
> > >>>> Subject: FW: New Version Notification for
> > >>>> draft-xu-sfc-using-mpls-spring-02.txt
> > >>>>
> > >>>> Hi all,
> > >>>>
> > >>>> This document describes how to leverage the MPLS-based source
> > >>>> routing (i.e.,
> > >>>> MPLS-SPRING) mechanism as developed by the SPRING WG to realize
> > >>>> the service path layer functionality of the service function chain=
ing.
> > >>>> In addition, this document also describes how to carry metadata
> > >>>> in an MPLS packet by using the NSH as a metadata container.
> > >>>>
> > >>>> Any comments are suggestions are welcome.
> > >>>>
> > >>>> Best regards,
> > >>>> Xiaohu
> > >>>>
> > >>>>> -----Original Message-----
> > >>>>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> > >>>>> Sent: Wednesday, March 04, 2015 11:24 AM
> > >>>>> To: Lizhenbin; Luis M. Contreras; Xuxiaohu; Himanshu C. Shah;
> > >>>>> Xuxiaohu; Himanshu Shah; Luis M. Contreras; Lizhenbin
> > >>>>> Subject: New Version Notification for
> > >>>>> draft-xu-sfc-using-mpls-spring-02.txt
> > >>>>>
> > >>>>>
> > >>>>> A new version of I-D, draft-xu-sfc-using-mpls-spring-02.txt
> > >>>>> has been successfully submitted by Xiaohu Xu and posted to the
> > >>>>> IETF
> > >>>> repository.
> > >>>>>
> > >>>>> Name:        draft-xu-sfc-using-mpls-spring
> > >>>>> Revision:    02
> > >>>>> Title:        Service Function Chaining Using MPLS-SPRING
> > >>>>> Document date:    2015-03-03
> > >>>>> Group:        Individual Submission
> > >>>>> Pages:        8
> > >>>>> URL:
> > >>>>>
> > >>>>>http://www.ietf.org/internet-drafts/draft-xu-sfc-using-mpls-spring=
-02.
> > >>>>> txt
> > >>>>> Status:
> > >>>>> https://datatracker.ietf.org/doc/draft-xu-sfc-using-mpls-spring/
> > >>>>> Htmlized:
> > >>> http://tools.ietf.org/html/draft-xu-sfc-using-mpls-spring-02
> > >>>>> Diff:
> > >>>>> http://www.ietf.org/rfcdiff?url2=3Ddraft-xu-sfc-using-mpls-spring=
-
> > >>>>> 02
> > >>>>>
> > >>>>> Abstract:
> > >>>>>   Source Packet Routing in Networking (SPRING) WG specifies a
> special
> > >>>>>   source routing mechanism.  Such source routing mechanism can be
> > >>>>>   leveraged to realize the service path layer functionality of th=
e
> > >>>>>   service function chaining (i.e, steering traffic through a
> > >>>>>particular
> > >>>>>   service function path) by encoding the service function path or=
 the
> > >>>>>   service function chain information as the explicit path
> > >>>>>information.
> > >>>>>   This document describes how to leverage the MPLS-based source
> > >>> routing
> > >>>>>   mechanism as developed by the SPRING WG to realize the service
> > path
> > >>>>>   layer functionality of the service function chaining.
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> Please note that it may take a couple of minutes from the time
> > >>>>>of submission until the htmlized version and diff are available
> > >>>>>at tools.ietf.org.
> > >>>>>
> > >>>>> The IETF Secretariat
> > >>>
> > >>> _______________________________________________
> > >>> sfc mailing list
> > >>> sfc@ietf.org
> > >>> https://www.ietf.org/mailman/listinfo/sfc
> > >
> > >_______________________________________________
> > >sfc mailing list
> > >sfc@ietf.org
> > >https://www.ietf.org/mailman/listinfo/sfc


From nobody Sun Mar  8 20:58:51 2015
Return-Path: <weixinpeng@huawei.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 687F01A1AA6 for <sfc@ietfa.amsl.com>; Sun,  8 Mar 2015 20:58:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 lg2aQWMcR6-n for <sfc@ietfa.amsl.com>; Sun,  8 Mar 2015 20:58:46 -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 7A6AE1A1AA0 for <sfc@ietf.org>; Sun,  8 Mar 2015 20:58:45 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml404-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BQA29680; Mon, 09 Mar 2015 03:58:43 +0000 (GMT)
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 9 Mar 2015 03:58:42 +0000
Received: from NKGEML507-MBX.china.huawei.com ([169.254.5.160]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.03.0158.001; Mon, 9 Mar 2015 11:58:32 +0800
From: "Weixinpeng (Jackie)" <weixinpeng@huawei.com>
To: "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: WG call for adoption of draft-quinn-sfc-nsh
Thread-Index: AQHQUcJRZDObBxbiIUWmIP9lX1xWp50ThVrQ
Date: Mon, 9 Mar 2015 03:58:31 +0000
Message-ID: <C5C3BB522B1DDF478AA09545169155B46E321AC5@nkgeml507-mbx.china.huawei.com>
References: <D1147FF5.844D%jguichar@cisco.com>
In-Reply-To: <D1147FF5.844D%jguichar@cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.76.176]
Content-Type: multipart/alternative; boundary="_000_C5C3BB522B1DDF478AA09545169155B46E321AC5nkgeml507mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/jt392Hv_jWe9VvWwpfHgjBFXhQQ>
Cc: "Xiongchunshan \(Sam\)" <sam.xiongchunshan@huawei.com>, "Jim Guichard \(jguichar\)" <jguichar@cisco.com>, "paulq@cisco.com" <paulq@cisco.com>
Subject: Re: [sfc] WG call for adoption of draft-quinn-sfc-nsh
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 09 Mar 2015 03:58:49 -0000

--_000_C5C3BB522B1DDF478AA09545169155B46E321AC5nkgeml507mbxchi_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,
It is would be great to have merged document to speed up the process of SFC=
 Header definition, and I agree that the WG use the joint document as the
basis for further work. But for the document, there are some of my comments=
.

1. As said in the document, 'C' bit is defined in NSH base header as an ind=
ication for the existence of critical metadata. But I don't think this bit =
is necessary: from my perspective, when receiving a
NSH encapsulated packet, the service function checks all the metadata to ge=
t what it needs, and it can learn about whether the metadata is critical fr=
om 'C' bit within
the TLV Type field. No matter whether a critical metadata exists, the servi=
ce function will check all the metadata.
2. The document defines "MD-Type=3D0x01", which contains metadata in NSH, a=
s mandatory and "MD-Type=3D0x02", which means metadata in NSH is optional, =
as optional. What I think is that metadata in
NSH should be optional, because metadata is not used in every case.
3. The draft defines a new list of "Next Protocol" values, such as 0x1 for =
IPv4, 0x2 for IPv6, 0x3 for Ethernet. But I think it's better to use the Pr=
otocol Number values that have been defined by IETF for consistence and no =
need to define
a list of new ones.

Regards,
-Xinpeng

From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of Jim Guichard (jguichar=
)
Sent: Thursday, February 26, 2015 8:47 PM
To: sfc@ietf.org
Subject: [sfc] WG call for adoption of draft-quinn-sfc-nsh

Greetings WG:

The document draft-quinn-sfc-nsh-07 (https://datatracker.ietf.org/doc/draft=
-quinn-sfc-nsh/) has recently been reissued. The authors of draft-zhang-sfc=
-sch-03 (http://datatracker.ietf.org/doc/draft-zhang-sfc-sch/) have joined =
the NSH document so that the WG can focus on a single encapsulation documen=
t going forward. This new version of NSH includes an open items section bas=
ed on discussion between co-authors and members of the list. The WG will wo=
rk through this list (and any other issues that need to be added) over the =
next weeks. We appreciate and recognize the hard work of both the NSH and S=
CH authors in pushing the SFC encapsulation work forward.

With that said, the chairs are calling for WG adoption of draft-quinn-sfc-n=
sh-07 as a WG document. The call for adoption will run for 2 weeks ending 3=
/12/2015.

Please note that this is a call for adoption, and not a last call for conte=
nt of the document. Adopting a WG document simply means that the WG will fo=
cus its efforts on that particular draft going forward, and use that docume=
nt for resolving open issues and documenting the WG's decisions.

Please indicate whether you support adoption for not, and if not why. Issue=
s you have with the current document itself can also be raised, but they sh=
ould be raised in the context of what should be changed in the document goi=
ng forward, rather than a pre-condition for adoption.

Finally, now is also a good time to poll for knowledge of any IPR that appl=
ies to this draft, in line with the IPR disclosure obligations for WG parti=
cipants (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are l=
isted as a document author please respond to this email (to the chairs) whe=
ther or not you are aware of any relevant IPR.

Jim & Thomas

--_000_C5C3BB522B1DDF478AA09545169155B46E321AC5nkgeml507mbxchi_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"ZH-CN" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi,<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">It is woul=
d be great to have merged document to speed up the process of SFC Header de=
finition, and I agree that the WG use the joint document as
 the <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">basis for =
further work. But for the document, there are some of my comments.<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">1. As said=
 in the document, &#8216;C&#8217; bit is defined in NSH base header as an i=
ndication for the existence of critical metadata. But I don&#8217;t think t=
his
 bit is necessary: from my perspective, when receiving a<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">NSH encaps=
ulated packet, the service function checks all the metadata to get what it =
needs, and it can learn about whether the metadata is critical
 from &#8216;C&#8217; bit within<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">the TLV Ty=
pe field. No matter whether a critical metadata exists, the service functio=
n will check all the metadata.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">2. The doc=
ument defines &#8220;MD-Type=3D0x01&#8221;, which contains metadata in NSH,=
 as mandatory and &#8220;MD-Type=3D0x02&#8221;, which means metadata in NSH=
 is optional,
 as optional. What I think is that metadata in<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">NSH should=
 be optional, because metadata is not used in every case.<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">3. The dra=
ft defines a new list of &#8220;Next Protocol&#8221; values, such as 0x1 fo=
r IPv4, 0x2 for IPv6, 0x3 for Ethernet. But I think it&#8217;s better to us=
e
 the Protocol Number values that have been defined by IETF for consistence =
and no need to define<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-indent:5.25pt"><span lang=3D"EN-US" st=
yle=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:#1F497D">a list of new ones.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Regards,<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">-Xinpeng<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> sfc [mailto:sfc-bounces@ietf.org]
<b>On Behalf Of </b>Jim Guichard (jguichar)<br>
<b>Sent:</b> Thursday, February 26, 2015 8:47 PM<br>
<b>To:</b> sfc@ietf.org<br>
<b>Subject:</b> [sfc] WG call for adoption of draft-quinn-sfc-nsh<o:p></o:p=
></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.0pt;font-f=
amily:Consolas;color:black">Greetings WG:</span><span lang=3D"EN-US" style=
=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black"><o:p>&nbs=
p;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.0pt;font-f=
amily:Consolas;color:black">The document draft-quinn-sfc-nsh-07 (<a href=3D=
"https://datatracker.ietf.org/doc/draft-quinn-sfc-nsh">https://datatracker.=
ietf.org/doc/draft-quinn-sfc-nsh</a>/) has
 recently been reissued. The authors of draft-zhang-sfc-sch-03 (<a href=3D"=
http://datatracker.ietf.org/doc/draft-zhang-sfc-sch">http://datatracker.iet=
f.org/doc/draft-zhang-sfc-sch</a>/) have joined the NSH document so that th=
e WG can focus on a single encapsulation
 document going forward. This new version of NSH includes an <b>open items =
</b>section based on discussion between co-authors and members of the list.=
 The WG will work through this list (and any other issues that need to be a=
dded) over the next weeks. We appreciate
 and recognize the hard work of both the NSH and SCH authors in pushing the=
 SFC encapsulation work forward.</span><span lang=3D"EN-US" style=3D"color:=
black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black"><o:p>&nbs=
p;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.0pt;font-f=
amily:Consolas;color:black">With that said, the chairs are calling for WG a=
doption of draft-quinn-sfc-nsh-07 as a WG document. The call for adoption w=
ill run for 2 weeks ending 3/12/2015.</span><span lang=3D"EN-US" style=3D"c=
olor:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black"><o:p>&nbs=
p;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.0pt;font-f=
amily:Consolas">Please note that this is a call for adoption, and not a las=
t call for content of the document. Adopting a WG document simply means tha=
t the WG will focus its efforts on that
 particular draft going forward, and use that document for resolving open i=
ssues and documenting the WG&#8217;s decisions.</span><span lang=3D"EN-US">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.0pt;font-f=
amily:Consolas">Please indicate whether you support adoption for not, and i=
f not why. Issues you have with the current document itself can also be rai=
sed, but they should be raised in the
 context of what should be changed in the document going forward, rather th=
an a pre-condition for adoption.&nbsp;</span><span lang=3D"EN-US"><o:p></o:=
p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.0pt;font-f=
amily:Consolas">Finally, now is also a good time to poll for knowledge of a=
ny IPR that applies to this draft, in line with the IPR disclosure obligati=
ons for WG participants (see RFCs 3979,
 4879, 3669 and 5378 for more details). If you are listed as a document aut=
hor please respond to this email (to the chairs) whether or not you are awa=
re of any relevant IPR.</span><span lang=3D"EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:13.5pt;font-=
family:Consolas;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.0pt;font-f=
amily:Consolas;color:black">Jim &amp; Thomas</span><span lang=3D"EN-US" sty=
le=3D"font-family:Consolas;color:black"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_C5C3BB522B1DDF478AA09545169155B46E321AC5nkgeml507mbxchi_--


From nobody Mon Mar  9 01:37:30 2015
Return-Path: <bill.wu@huawei.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E24FA1A86F1 for <sfc@ietfa.amsl.com>; Mon,  9 Mar 2015 01:37:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.422
X-Spam-Level: 
X-Spam-Status: No, score=-1.422 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CN_BODY_35=0.339, 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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hBW2eS6KuAxG for <sfc@ietfa.amsl.com>; Mon,  9 Mar 2015 01:37:26 -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 B30721A1EFE for <sfc@ietf.org>; Mon,  9 Mar 2015 01:37:25 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BQA51398; Mon, 09 Mar 2015 08:37:24 +0000 (GMT)
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 9 Mar 2015 08:37:23 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.146]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.03.0158.001; Mon, 9 Mar 2015 16:37:19 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: I-D Action: draft-ww-sfc-control-plane-04.txt
Thread-Index: AQHQWhc+atDw777+106H/CgInGTKt50T0VMA
Date: Mon, 9 Mar 2015 08:37:19 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA846DF4FE@nkgeml501-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.138.41.180]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/F4Pti5wwBPraIZLbHD3XwiWQfRE>
Subject: Re: [sfc] I-D Action: draft-ww-sfc-control-plane-04.txt
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 09 Mar 2015 08:37:29 -0000

SGk6DQpIZXJlIGlzIHRoZSB1cGRhdGUgb2YgZHJhZnQtd3ctc2ZjLWNvbnRyb2wtcGxhbmUgd2hp
Y2ggbWVyZ2VzIGRyYWZ0LWxlZS1zZmMtZHluYW1pYy0NCkluc3RhbnRpYXRpb24gYmFzZWQgb24g
c29tZSBkaXNjdXNzaW9uIHdpdGggYXV0aG9ycyBvZiBib3RoIGRyYWZ0cy4NCmh0dHA6Ly90b29s
cy5pZXRmLm9yZy9odG1sL2RyYWZ0LXd3LXNmYy1jb250cm9sLXBsYW5lLTA0DQoNClRoYW5rcyBT
ZXVuZ2lrIGZvciB0aGUgcHJvcG9zZWQgY2hhbmdlcy4gVGhhbmtzIFJvbiBQYXJrZXIgZm9yIHlv
dXIgaW50ZXJlc3RzIGluIGNvbnRyaWJ1dGluZyByZXNpbGllbmNlIGFzcGVjdC4NClRoZSBwcm9w
b3NlZCBjaGFuZ2VzIGluY2x1ZGU6DQotIHNlY3Rpb24gNDogYWRkaW5nIFNGUCBhZGp1c3RtZW50
IGZ1bmN0aW9uIGZvciBTRkMgTWFwcGluZyBhbmQgRm9yd2FyZGluZyBDb250cm9sDQotIHNlY3Rp
b24gNC4yLCA0LjQ6IGFkZCBkZXNjcmlwdGlvbnMgZm9yIFNGUCBhZGp1c3RtZW50DQotIHNlY3Rp
b24gNS40OiBuZXcgc2VjdGlvbiBpbnNlcnRlZDogIlNlcnZpY2UgRnVuY3Rpb24gUGF0aCBBZGp1
c3RtZW50Ig0KDQpUaGUgZGlmZiBpczoNCmh0dHA6Ly93d3cuaWV0Zi5vcmcvcmZjZGlmZj91cmwy
PWRyYWZ0LXd3LXNmYy1jb250cm9sLXBsYW5lLTA0DQoNClNvbWUgdGVybWlub2xvZ2llcyBpbmNv
bnNpc3RlbmN5IHdpbGwgYmUgZml4ZWQgbGF0ZXIuDQoNCi1RaW4NCi0tLS0t08q8/tStvP4tLS0t
LQ0Kt6K8/sjLOiBJLUQtQW5ub3VuY2UgW21haWx0bzppLWQtYW5ub3VuY2UtYm91bmNlc0BpZXRm
Lm9yZ10gtPqx7SBpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmcNCreiy83KsbzkOiAyMDE1xOoz1MI5
yNUgMTE6MTUNCsrVvP7IyzogaS1kLWFubm91bmNlQGlldGYub3JnDQrW98ziOiBJLUQgQWN0aW9u
OiBkcmFmdC13dy1zZmMtY29udHJvbC1wbGFuZS0wNC50eHQNCg0KDQpBIE5ldyBJbnRlcm5ldC1E
cmFmdCBpcyBhdmFpbGFibGUgZnJvbSB0aGUgb24tbGluZSBJbnRlcm5ldC1EcmFmdHMgZGlyZWN0
b3JpZXMuDQoNCg0KICAgICAgICBUaXRsZSAgICAgICAgICAgOiBTZXJ2aWNlIEZ1bmN0aW9uIENo
YWluaW5nIChTRkMpIENvbnRyb2wgUGxhbmUgQWNoaXRlY3R1cmUNCiAgICAgICAgQXV0aG9ycyAg
ICAgICAgIDogSG9uZ3l1IExpDQogICAgICAgICAgICAgICAgICAgICAgICAgIFFpbiBXdQ0KICAg
ICAgICAgICAgICAgICAgICAgICAgICBNb2hhbWVkIEJvdWNhZGFpcg0KICAgICAgICAgICAgICAg
ICAgICAgICAgICBDaHJpc3RpYW4gSmFjcXVlbmV0DQogICAgICAgICAgICAgICAgICAgICAgICAg
IFdhbHRlciBIYWVmZm5lcg0KICAgICAgICAgICAgICAgICAgICAgICAgICBTZXVuZ2lrIExlZQ0K
ICAgICAgICAgICAgICAgICAgICAgICAgICBSb24gUGFya2VyDQoJRmlsZW5hbWUgICAgICAgIDog
ZHJhZnQtd3ctc2ZjLWNvbnRyb2wtcGxhbmUtMDQudHh0DQoJUGFnZXMgICAgICAgICAgIDogMjAN
CglEYXRlICAgICAgICAgICAgOiAyMDE1LTAzLTA4DQoNCkFic3RyYWN0Og0KICAgVGhpcyBkb2N1
bWVudCBkZWZpbmVzIHRoZSBjb250cm9sIHBsYW5lIGFyY2hpdGVjdHVyZSB3aGljaCBpbmNsdWRl
DQogICBjb250cm9sIHBsYW5lIGNvbXBvbmVudHMgYW5kIGludGVyZmFjZSBiZXR3ZWVuIGNvbnRy
b2wgcGxhbmUNCiAgIGNvbXBvbmVudCBhbmQgZGF0YSBwbGFuZSBjb21wb25lbnQuICBUaGlzIGRv
Y3VtZW50IGZ1cnRoZXIgZGVzY3JpYmVzDQogICBob3cgU2VydmljZSBGdW5jdGlvbnMgQ2hhaW5z
IGFyZSBzdHJ1Y3R1cmVkIGFuZCBob3cgU2VydmljZSBGdW5jdGlvbg0KICAgQ2hhaW5pbmcgcGF0
aCBpcyBwcm92aXNpb25lZCBhbmQgc2V0dXAuDQoNCg0KVGhlIElFVEYgZGF0YXRyYWNrZXIgc3Rh
dHVzIHBhZ2UgZm9yIHRoaXMgZHJhZnQgaXM6DQpodHRwczovL2RhdGF0cmFja2VyLmlldGYub3Jn
L2RvYy9kcmFmdC13dy1zZmMtY29udHJvbC1wbGFuZS8NCg0KVGhlcmUncyBhbHNvIGEgaHRtbGl6
ZWQgdmVyc2lvbiBhdmFpbGFibGUgYXQ6DQpodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFm
dC13dy1zZmMtY29udHJvbC1wbGFuZS0wNA0KDQpBIGRpZmYgZnJvbSB0aGUgcHJldmlvdXMgdmVy
c2lvbiBpcyBhdmFpbGFibGUgYXQ6DQpodHRwOi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJsMj1k
cmFmdC13dy1zZmMtY29udHJvbC1wbGFuZS0wNA0KDQoNClBsZWFzZSBub3RlIHRoYXQgaXQgbWF5
IHRha2UgYSBjb3VwbGUgb2YgbWludXRlcyBmcm9tIHRoZSB0aW1lIG9mIHN1Ym1pc3Npb24gdW50
aWwgdGhlIGh0bWxpemVkIHZlcnNpb24gYW5kIGRpZmYgYXJlIGF2YWlsYWJsZSBhdCB0b29scy5p
ZXRmLm9yZy4NCg0KSW50ZXJuZXQtRHJhZnRzIGFyZSBhbHNvIGF2YWlsYWJsZSBieSBhbm9ueW1v
dXMgRlRQIGF0Og0KZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy8NCg0KX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkktRC1Bbm5vdW5jZSBt
YWlsaW5nIGxpc3QNCkktRC1Bbm5vdW5jZUBpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcv
bWFpbG1hbi9saXN0aW5mby9pLWQtYW5ub3VuY2UNCkludGVybmV0LURyYWZ0IGRpcmVjdG9yaWVz
OiBodHRwOi8vd3d3LmlldGYub3JnL3NoYWRvdy5odG1sIG9yIGZ0cDovL2Z0cC5pZXRmLm9yZy9p
ZXRmLzFzaGFkb3ctc2l0ZXMudHh0DQo=


From gurong_cmcc@outlook.com  Mon Mar  9 05:53:30 2015
Return-Path: <gurong_cmcc@outlook.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38A4A1A88B9 for <sfc@ietfa.amsl.com>; Mon,  9 Mar 2015 05:53:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.601
X-Spam-Level: *
X-Spam-Status: No, score=1.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=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 WtQimxIl-yzy for <sfc@ietfa.amsl.com>; Mon,  9 Mar 2015 05:53:28 -0700 (PDT)
Received: from SNT004-OMC2S44.hotmail.com (snt004-omc2s44.hotmail.com [65.54.61.95]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6890A1A885E for <sfc@ietf.org>; Mon,  9 Mar 2015 05:53:26 -0700 (PDT)
Received: from SNT148-W94 ([65.55.90.71]) by SNT004-OMC2S44.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751);  Mon, 9 Mar 2015 05:53:25 -0700
X-TMN: [DctuB7hkEfjjqnNGBst8UKbU9zKH1RocS7alPBRcBh8=]
X-Originating-Email: [gurong_cmcc@outlook.com]
Message-ID: <SNT148-W94A00ABF37203919D83F0A8B1B0@phx.gbl>
Content-Type: multipart/alternative; boundary="_53d4e6e8-a2ea-4e19-b406-9c8a498963f1_"
From: =?gb2312?B?ucvI1g==?= <gurong_cmcc@outlook.com>
To: "sfc@ietf.org" <sfc@ietf.org>, =?gb2312?B?ucvI1g==?= <gurong_cmcc@outlook.com>
Date: Mon, 9 Mar 2015 12:53:25 +0000
Importance: Normal
In-Reply-To: <20150309031308.2665.2383.idtracker@ietfa.amsl.com>
References: <20150309031308.2665.2383.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
X-OriginalArrivalTime: 09 Mar 2015 12:53:25.0818 (UTC) FILETIME=[086CA1A0:01D05A68]
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/VyWIlLd_a1uEIwuo3_qTCUalux4>
Subject: [sfc] FW: solicit comments for draft-gu-sfc-extend-architecture-00.txt
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 09 Mar 2015 12:55:56 -0000

--_53d4e6e8-a2ea-4e19-b406-9c8a498963f1_
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64

CgoKCgogSGksIGRlYXIgYWxsLiANCldlIGhhdmUganVzdCBzdWJtaXR0ZWQgYSBuZXcgZHJhZnQg
YWJvdXQgdGhlIHNlcnZpY2UgZnVuY3Rpb24gY2hhaW4gZXh0ZW5kIGFyY2hpdGVjdHVyZS4gImRy
YWZ0LWd1LXNmYy1leHRlbmQtYXJjaGl0ZWN0dXJlIi4NCiANClRoaXMgZHJhZnQgaW50cm9kdWNl
cyBhbiBleHRlbmRlZCBhcmNoaXRlY3R1cmUgaW4gc2VydmljZSBmdW50aW9uIGNoYWluIGluY2x1
ZGluZyB0aGUgYXBwbGljYXRpb25zIHRvIHRlbmFudHMsIFNETiBjb250cm9sbGVyLCBuZXR3b3Jr
IGZ1bmN0aW9uIHZpcnR1YWxpemVkIG1hbmFnZXIgYW5kIHRoZSBzZXJ2aWNlIGZ1bmN0aW9uIG5v
ZGUgaW4gb3JkZXIgdG8gcHJvdmlkZSBhdXRvLWRlcGxveW1lbnQgc2VsZi1zZXJ2aWNlLg0KIA0K
CgoKCkFueSBjb21tZW50cywgc3VnZ2VzdGlvbnMgYW5kIGRpc2N1c3Npb25zIGFyZSB3YXJtbHkg
d2VsY29tZWQuIApUaGFuayB5b3UuCiAKQmVzdCByZWdhcmRzIGZyb20gUm9uZyBHdS5ndXJvbmdf
Y21jY0BjaGluYW1vYmlsZS5jb20NCg0KIAo+IEZyb206IGludGVybmV0LWRyYWZ0c0BpZXRmLm9y
Zw0KPiBUbzogZ3Vyb25nX2NtY2NAb3V0bG9vay5jb207IGxpY2hlbnlqQGNoaW5hbW9iaWxlLmNv
bTsgbGljaGVueWpAY2hpbmFtb2JpbGUuY29tOyBndXJvbmdfY21jY0BvdXRsb29rLmNvbQ0KPiBT
dWJqZWN0OiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9yIGRyYWZ0LWd1LXNmYy1leHRlbmQt
YXJjaGl0ZWN0dXJlLTAwLnR4dA0KPiBEYXRlOiBTdW4sIDggTWFyIDIwMTUgMjA6MTM6MDggLTA3
MDANCj4gDQo+IA0KPiBBIG5ldyB2ZXJzaW9uIG9mIEktRCwgZHJhZnQtZ3Utc2ZjLWV4dGVuZC1h
cmNoaXRlY3R1cmUtMDAudHh0DQo+IGhhcyBiZWVuIHN1Y2Nlc3NmdWxseSBzdWJtaXR0ZWQgYnkg
Um9uZyBHdSBhbmQgcG9zdGVkIHRvIHRoZQ0KPiBJRVRGIHJlcG9zaXRvcnkuDQo+IA0KPiBOYW1l
OiBkcmFmdC1ndS1zZmMtZXh0ZW5kLWFyY2hpdGVjdHVyZQ0KPiBSZXZpc2lvbjogMDANCj4gVGl0
bGU6IFNlcnZpY2UgRnVuY3Rpb24gQ2hhaW4gRXh0ZW5zaW9uIEFyY2hpdGVjdHVyZQ0KPiBEb2N1
bWVudCBkYXRlOiAyMDE1LTAzLTA4DQo+IEdyb3VwOiBJbmRpdmlkdWFsIFN1Ym1pc3Npb24NCj4g
UGFnZXM6IDYNCj4gVVJMOiBodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFm
dC1ndS1zZmMtZXh0ZW5kLWFyY2hpdGVjdHVyZS0wMC50eHQNCj4gU3RhdHVzOiBodHRwczovL2Rh
dGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1ndS1zZmMtZXh0ZW5kLWFyY2hpdGVjdHVyZS8N
Cj4gSHRtbGl6ZWQ6IGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWd1LXNmYy1leHRl
bmQtYXJjaGl0ZWN0dXJlLTAwDQo+IA0KPiANCj4gQWJzdHJhY3Q6DQo+IEFuIGV4dGVuZGVkIGFy
Y2hpdGVjdHVyZSBpbiBzZXJ2aWNlIGZ1bmN0aW9uIGNoYWluIGlzIHByb3ZpZGVkDQo+IGluY2x1
ZGluZyB0aGUgYXBwbGljYXRpb25zIHRvIHRlbmFudHMsIFNETiBjb250cm9sbGVyLCBuZXR3b3Jr
DQo+IGZ1bmN0aW9uIHZpcnR1YWxpemVkIG1hbmFnZXIgKE5GVk0pIGFuZCB0aGUgc2VydmljZSBm
dW5jdGlvbiBub2RlLg0KPiBBdXRvLWRlcGxveWVkIHNlbGYtc2VydmljZSBpcyBwcm92aWRlZCBi
eSB0aGUgb3JjaGVzdHJhdGlvbiBvZiBTRE4NCj4gY29udHJvbGxlciBhbmQgTkZWIG1hbmFnZXIu
IEJlc2lkZXMsIGZ1bmRhbWVudGFsIGNvbmZpZ3VyYXRpb25zIGFuZA0KPiB0aGUgcmVhbGl6YXRp
b25zIG9mIHRoZSBzZXJ2aWNlIGZ1bmN0aW9uIGNoYWluaW5nIGFyZSBpbnRyb2R1Y2VkIHdpdGgN
Cj4gcmVxdWlyZW1lbnRzIHJhaXNlZC4gQmVuZWZpdHRpbmcgZnJvbSB0aGUgTmV0d29yayBmdW5j
dGlvbg0KPiB2aXJ0dWFsaXphdGlvbiAoTkZWKSBhbmQgY2xvdWQgdGVjaG5vbG9naWVzLCBTRkMg
aW4gdmlydHVhbCBuZXR3b3Jrcw0KPiBjYW4gYnJpbmcgY29udmVuaWVudCBhbmQgZWxhc3RpYyBu
ZXR3b3JrIHRvIHRoZSBjdXN0b21lcnMgd2l0aA0KPiBjZW50cmFsIG1hbmFnZW1lbnQgdG8gdGhl
IG9wZXJhdG9ycy4NCj4gDQo+IA0KPiANCj4gDQo+IFBsZWFzZSBub3RlIHRoYXQgaXQgbWF5IHRh
a2UgYSBjb3VwbGUgb2YgbWludXRlcyBmcm9tIHRoZSB0aW1lIG9mIHN1Ym1pc3Npb24NCj4gdW50
aWwgdGhlIGh0bWxpemVkIHZlcnNpb24gYW5kIGRpZmYgYXJlIGF2YWlsYWJsZSBhdCB0b29scy5p
ZXRmLm9yZy4NCj4gDQo+IFRoZSBJRVRGIFNlY3JldGFyaWF0DQo+IA0KCiAJCSAJICAgCQkgIA==

--_53d4e6e8-a2ea-4e19-b406-9c8a498963f1_
Content-Type: text/html; charset="gb2312"
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjwvaGVhZD4NCjxib2R5IGNsYXNzPSdobW1lc3NhZ2UnPjxkaXYgZGly
PSdsdHInPgoKPHN0eWxlPjwhLS0KLmhtbWVzc2FnZSBQCnsKbWFyZ2luOjBweDsKcGFkZGluZzow
cHgKfQpib2R5LmhtbWVzc2FnZQp7CmZvbnQtc2l6ZTogMTJwdDsKZm9udC1mYW1pbHk6zqLI7dHF
utoKfQotLT48L3N0eWxlPgo8ZGl2IGRpcj0ibHRyIj48ZGl2IGNsYXNzPSJjLVJlYWRNZXNzYWdl
UGFydEJvZHkiIGpxdWVyeTE3MjA5MTM4NTczMDI4MjMwOTk0PSIxODkiIF9qc3ZibmQ9IiZhbXA7
OTI4Ij4KPGRpdiBjbGFzcz0iQ2xlYXJCb3RoIj4KPGRpdiBzdHlsZT0iRElTUExBWTogbm9uZSI+
Jm5ic3A7PC9kaXY+SGksJm5ic3A7ZGVhciBhbGwuIDxicj5XZSBoYXZlIGp1c3Qgc3VibWl0dGVk
IGEgbmV3IGRyYWZ0IGFib3V0IHRoZSBzZXJ2aWNlIGZ1bmN0aW9uIGNoYWluIGV4dGVuZCBhcmNo
aXRlY3R1cmUuICJkcmFmdC1ndS1zZmMtZXh0ZW5kLWFyY2hpdGVjdHVyZSIuPGJyPiZuYnNwOzxi
cj5UaGlzIGRyYWZ0IGludHJvZHVjZXMgYW4gZXh0ZW5kZWQgYXJjaGl0ZWN0dXJlIGluIHNlcnZp
Y2UgZnVudGlvbiBjaGFpbiBpbmNsdWRpbmcgdGhlIGFwcGxpY2F0aW9ucyB0byB0ZW5hbnRzLCBT
RE4gY29udHJvbGxlciwgbmV0d29yayBmdW5jdGlvbiB2aXJ0dWFsaXplZCBtYW5hZ2VyIGFuZCB0
aGUgc2VydmljZSBmdW5jdGlvbiBub2RlIGluIG9yZGVyIHRvIHByb3ZpZGUgYXV0by1kZXBsb3lt
ZW50IHNlbGYtc2VydmljZS48YnI+Jm5ic3A7PGJyPjwvZGl2Pgo8ZGl2IGNsYXNzPSJyZWFkTXNn
Qm9keSI+CjxkaXYgaWQ9ImJvZHlyZWFkTWVzc2FnZVBhcnRCb2R5Q29udHJvbDEyM2YiIGNsYXNz
PSJFeHRlcm5hbENsYXNzIE1zZ0JvZHlDb250YWluZXIiIF9qc3ZibmQ9IiZhbXA7OTI5Ij4KPGRp
diBkaXI9Imx0ciI+CjxwIHN0eWxlPSJURVhULUFMSUdOOiBsZWZ0OyBNQVJHSU46IDBjbSAwY20g
MHB0IiBjbGFzcz0iZWN4TXNvTm9ybWFsIiBhbGlnbj0ibGVmdCI+PHNwYW4gbGFuZz0iRU4tVVMi
PkFueSBjb21tZW50cywgc3VnZ2VzdGlvbnMgYW5kIGRpc2N1c3Npb25zIGFyZSB3YXJtbHkgd2Vs
Y29tZWQuIDwvc3Bhbj48L3A+CjxwIHN0eWxlPSJNQVJHSU46IDBjbSAwY20gMHB0IiBjbGFzcz0i
ZWN4TXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+VGhhbmsgeW91Ljwvc3Bhbj48L3A+
CjxwIHN0eWxlPSJNQVJHSU46IDBjbSAwY20gMHB0IiBjbGFzcz0iZWN4TXNvUGxhaW5UZXh0Ij48
c3BhbiBsYW5nPSJFTi1VUyI+Jm5ic3A7PC9zcGFuPjwvcD4KPHAgc3R5bGU9Ik1BUkdJTjogMGNt
IDBjbSAwcHQiIGNsYXNzPSJlY3hNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj5CZXN0
IHJlZ2FyZHMgZnJvbSBSb25nIEd1Ljwvc3Bhbj48L3A+PGEgaHJlZj0ibWFpbHRvOmd1cm9uZ19j
bWNjQGNoaW5hbW9iaWxlLmNvbSI+PGZvbnQgY29sb3I9IiMwMDY4Y2YiPmd1cm9uZ19jbWNjQGNo
aW5hbW9iaWxlLmNvbTwvZm9udD48L2E+PGJyPjxicj4mbmJzcDs8L2Rpdj48L2Rpdj48L2Rpdj48
L2Rpdj4KPGRpdj4mZ3Q7IEZyb206IGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZzxicj4mZ3Q7IFRv
OiBndXJvbmdfY21jY0BvdXRsb29rLmNvbTsgbGljaGVueWpAY2hpbmFtb2JpbGUuY29tOyBsaWNo
ZW55akBjaGluYW1vYmlsZS5jb207IGd1cm9uZ19jbWNjQG91dGxvb2suY29tPGJyPiZndDsgU3Vi
amVjdDogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC1ndS1zZmMtZXh0ZW5kLWFy
Y2hpdGVjdHVyZS0wMC50eHQ8YnI+Jmd0OyBEYXRlOiBTdW4sIDggTWFyIDIwMTUgMjA6MTM6MDgg
LTA3MDA8YnI+Jmd0OyA8YnI+Jmd0OyA8YnI+Jmd0OyBBIG5ldyB2ZXJzaW9uIG9mIEktRCwgZHJh
ZnQtZ3Utc2ZjLWV4dGVuZC1hcmNoaXRlY3R1cmUtMDAudHh0PGJyPiZndDsgaGFzIGJlZW4gc3Vj
Y2Vzc2Z1bGx5IHN1Ym1pdHRlZCBieSBSb25nIEd1IGFuZCBwb3N0ZWQgdG8gdGhlPGJyPiZndDsg
SUVURiByZXBvc2l0b3J5Ljxicj4mZ3Q7IDxicj4mZ3Q7IE5hbWU6IGRyYWZ0LWd1LXNmYy1leHRl
bmQtYXJjaGl0ZWN0dXJlPGJyPiZndDsgUmV2aXNpb246IDAwPGJyPiZndDsgVGl0bGU6IFNlcnZp
Y2UgRnVuY3Rpb24gQ2hhaW4gRXh0ZW5zaW9uIEFyY2hpdGVjdHVyZTxicj4mZ3Q7IERvY3VtZW50
IGRhdGU6IDIwMTUtMDMtMDg8YnI+Jmd0OyBHcm91cDogSW5kaXZpZHVhbCBTdWJtaXNzaW9uPGJy
PiZndDsgUGFnZXM6IDY8YnI+Jmd0OyBVUkw6IGh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQt
ZHJhZnRzL2RyYWZ0LWd1LXNmYy1leHRlbmQtYXJjaGl0ZWN0dXJlLTAwLnR4dDxicj4mZ3Q7IFN0
YXR1czogaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtZ3Utc2ZjLWV4dGVu
ZC1hcmNoaXRlY3R1cmUvPGJyPiZndDsgSHRtbGl6ZWQ6IGh0dHA6Ly90b29scy5pZXRmLm9yZy9o
dG1sL2RyYWZ0LWd1LXNmYy1leHRlbmQtYXJjaGl0ZWN0dXJlLTAwPGJyPiZndDsgPGJyPiZndDsg
PGJyPiZndDsgQWJzdHJhY3Q6PGJyPiZndDsgQW4gZXh0ZW5kZWQgYXJjaGl0ZWN0dXJlIGluIHNl
cnZpY2UgZnVuY3Rpb24gY2hhaW4gaXMgcHJvdmlkZWQ8YnI+Jmd0OyBpbmNsdWRpbmcgdGhlIGFw
cGxpY2F0aW9ucyB0byB0ZW5hbnRzLCBTRE4gY29udHJvbGxlciwgbmV0d29yazxicj4mZ3Q7IGZ1
bmN0aW9uIHZpcnR1YWxpemVkIG1hbmFnZXIgKE5GVk0pIGFuZCB0aGUgc2VydmljZSBmdW5jdGlv
biBub2RlLjxicj4mZ3Q7IEF1dG8tZGVwbG95ZWQgc2VsZi1zZXJ2aWNlIGlzIHByb3ZpZGVkIGJ5
IHRoZSBvcmNoZXN0cmF0aW9uIG9mIFNETjxicj4mZ3Q7IGNvbnRyb2xsZXIgYW5kIE5GViBtYW5h
Z2VyLiBCZXNpZGVzLCBmdW5kYW1lbnRhbCBjb25maWd1cmF0aW9ucyBhbmQ8YnI+Jmd0OyB0aGUg
cmVhbGl6YXRpb25zIG9mIHRoZSBzZXJ2aWNlIGZ1bmN0aW9uIGNoYWluaW5nIGFyZSBpbnRyb2R1
Y2VkIHdpdGg8YnI+Jmd0OyByZXF1aXJlbWVudHMgcmFpc2VkLiBCZW5lZml0dGluZyBmcm9tIHRo
ZSBOZXR3b3JrIGZ1bmN0aW9uPGJyPiZndDsgdmlydHVhbGl6YXRpb24gKE5GVikgYW5kIGNsb3Vk
IHRlY2hub2xvZ2llcywgU0ZDIGluIHZpcnR1YWwgbmV0d29ya3M8YnI+Jmd0OyBjYW4gYnJpbmcg
Y29udmVuaWVudCBhbmQgZWxhc3RpYyBuZXR3b3JrIHRvIHRoZSBjdXN0b21lcnMgd2l0aDxicj4m
Z3Q7IGNlbnRyYWwgbWFuYWdlbWVudCB0byB0aGUgb3BlcmF0b3JzLjxicj4mZ3Q7IDxicj4mZ3Q7
IDxicj4mZ3Q7IDxicj4mZ3Q7IDxicj4mZ3Q7IFBsZWFzZSBub3RlIHRoYXQgaXQgbWF5IHRha2Ug
YSBjb3VwbGUgb2YgbWludXRlcyBmcm9tIHRoZSB0aW1lIG9mIHN1Ym1pc3Npb248YnI+Jmd0OyB1
bnRpbCB0aGUgaHRtbGl6ZWQgdmVyc2lvbiBhbmQgZGlmZiBhcmUgYXZhaWxhYmxlIGF0IHRvb2xz
LmlldGYub3JnLjxicj4mZ3Q7IDxicj4mZ3Q7IFRoZSBJRVRGIFNlY3JldGFyaWF0PGJyPiZndDsg
PGJyPjwvZGl2PjwvZGl2PgogCQkgCSAgIAkJICA8L2Rpdj48L2JvZHk+DQo8L2h0bWw+

--_53d4e6e8-a2ea-4e19-b406-9c8a498963f1_--


From nobody Mon Mar  9 15:53:27 2015
Return-Path: <nordmark@acm.org>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B3941ACDF1 for <sfc@ietfa.amsl.com>; Mon,  9 Mar 2015 15:53:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=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 CmDzqTHpweRX for <sfc@ietfa.amsl.com>; Mon,  9 Mar 2015 15:53:20 -0700 (PDT)
Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C3CC81ACDFB for <sfc@ietf.org>; Mon,  9 Mar 2015 15:53:18 -0700 (PDT)
Received: from [172.22.227.238] ([162.210.130.3]) (authenticated bits=0) by d.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id t29MrHeg004858 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 9 Mar 2015 15:53:17 -0700
Message-ID: <54FE245C.2060405@acm.org>
Date: Mon, 09 Mar 2015 15:53:16 -0700
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: "sfc@ietf.org" <sfc@ietf.org>
References: <20150309225145.1246.42035.idtracker@ietfa.amsl.com>
In-Reply-To: <20150309225145.1246.42035.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20150309225145.1246.42035.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Sonic-CAuth: UmFuZG9tSVazMOWQ21jR9Na65LE1LU4P5vFRXJYPqUkSUEjGhjcCs5ENEuIHdNkeYIstNplNlZqv86W9y6+ZF3Xl0fJ9/ws/
X-Sonic-ID: C;PhkbE6/G5BGScr5YxQPdhw== M;bMg4E6/G5BGScr5YxQPdhw==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/K_DNP7zwqNpe3VtXU_CIgXq62a8>
Subject: [sfc] Fwd: New Version Notification for draft-rtg-dt-encap-01.txt
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 09 Mar 2015 22:53:22 -0000

-------- Forwarded Message --------
Subject: 	New Version Notification for draft-rtg-dt-encap-01.txt
Date: 	Mon, 09 Mar 2015 15:51:45 -0700
From: 	internet-drafts@ietf.org
To: 	Jon Hudson <jon.hudson@gmail.com>, Tom Herbert 
<therbert@google.com>, Lawrence Kreeger <kreeger@cisco.com>, Patricia 
Thaler <pthaler@broadcom.com>, Patricia Thaler <pthaler@broadcom.com>, 
Jon Hudson <jon.hudson@gmail.com>, Albert Tian 
<albert.tian@ericsson.com>, Jesse Gross <jgross@vmware.com>, Albert Tian 
<albert.tian@ericsson.com>, Pankaj Garg <pankajg@microsoft.com>, Pankaj 
Garg <pankajg@microsoft.com>, Tom Herbert <therbert@google.com>, Jesse 
Gross <jgross@vmware.com>, Erik Nordmark <nordmark@arista.com>, Lawrence 
Kreeger <kreeger@cisco.com>, Erik Nordmark <nordmark@arista.com>



A new version of I-D, draft-rtg-dt-encap-01.txt
has been successfully submitted by Erik Nordmark and posted to the
IETF repository.

Name:		draft-rtg-dt-encap
Revision:	01
Title:		Encapsulation Considerations
Document date:	2015-03-09
Group:		Individual Submission
Pages:		37
URL:            http://www.ietf.org/internet-drafts/draft-rtg-dt-encap-01.txt
Status:         https://datatracker.ietf.org/doc/draft-rtg-dt-encap/
Htmlized:       http://tools.ietf.org/html/draft-rtg-dt-encap-01
Diff:           http://www.ietf.org/rfcdiff?url2=draft-rtg-dt-encap-01

Abstract:
    The IETF Routing Area director has chartered a design team to look at
    common issues for the different data plane encapsulations being
    discussed in the NVO3 and SFC working groups and also in the BIER
    BoF, and also to look at the relationship between such encapsulations
    in the case that they might be used at the same time.  The purpose of
    this design team is to discover, discuss and document considerations
    across the different encapsulations in the different WGs/BoFs so that
    we can reduce the number of wheels that need to be reinvented in the
    future.

                                                                                   


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat




From nobody Tue Mar 10 02:00:36 2015
Return-Path: <sevil.mehraghdam@uni-paderborn.de>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D47911A1AA9 for <sfc@ietfa.amsl.com>; Tue, 10 Mar 2015 02:00:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.86
X-Spam-Level: 
X-Spam-Status: No, score=-3.86 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 LmghC3RbInY6 for <sfc@ietfa.amsl.com>; Tue, 10 Mar 2015 02:00:32 -0700 (PDT)
Received: from mail.uni-paderborn.de (mail.uni-paderborn.de [131.234.142.9]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76CC61A6F03 for <sfc@ietf.org>; Tue, 10 Mar 2015 02:00:32 -0700 (PDT)
Message-ID: <54FEB2AC.8030608@uni-paderborn.de>
Date: Tue, 10 Mar 2015 10:00:28 +0100
From: Sevil Mehraghdam <sevil.mehraghdam@uni-paderborn.de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: repenno@cisco.com, sfc@ietf.org
References: <20150228002942.13121.52348.idtracker@ietfa.amsl.com> <D1164C15.B974%repenno@cisco.com>
In-Reply-To: <D1164C15.B974%repenno@cisco.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-IMT-Spam-Score: 0.0 ()
X-PMX-Version: 6.2.0.2453472, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.3.10.84818
X-IMT-Authenticated-Sender: uid=sevilmeh,ou=People,o=upb,c=de
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/nlfczRCdVLZjCSp5blTEZCF5NPQ>
Subject: [sfc] YANG data model for complex service structures (Re: FW: New Version Notification for draft-penno-sfc-yang-11.txt)
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 10 Mar 2015 09:00:35 -0000

Hello,

we have been working on a formal specification model for complex service 
structures besides a simple chain of totally ordered service functions, 
i.e., partially ordered sets that can be chained in different ways, 
branches, full meshes, etc.

We have developed a context-free grammar for the abstract specification 
of these structures. For a more concrete model that can include other 
attributes of a service together with the "structure", we have ideas for 
integrating our description model into the the latest draft of the Yang 
data model for SFC. You can find our paper (currently under review) with 
more details on this in:

http://arxiv.org/abs/1503.02442

We would very much appreciate your comments and suggestions.

Best regards,
Sevil





On 02/28/2015 01:30 AM, Reinaldo Penno (repenno) wrote:
>
> On 2/27/15, 4:29 PM, "internet-drafts@ietf.org" <internet-drafts@ietf.org>
> wrote:
>
>> A new version of I-D, draft-penno-sfc-yang-11.txt
>> has been successfully submitted by Reinaldo Penno and posted to the
>> IETF repository.
>>
>> Name:		draft-penno-sfc-yang
>> Revision:	11
>> Title:		Yang Data Model for Service Function Chaining
>> Document date:	2015-02-27
>> Group:		Individual Submission
>> Pages:		56
>> URL:
>> http://www.ietf.org/internet-drafts/draft-penno-sfc-yang-11.txt
>> Status:         https://datatracker.ietf.org/doc/draft-penno-sfc-yang/
>> Htmlized:       http://tools.ietf.org/html/draft-penno-sfc-yang-11
>> Diff:           http://www.ietf.org/rfcdiff?url2=draft-penno-sfc-yang-11
>>
>> Abstract:
>>    This document defines a YANG data model that can be used to configure
>>    and manage Service Function Chains.
>>
>>
>>                   
>>         
>>
>>
>> Please note that it may take a couple of minutes from the time of
>> submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> The IETF Secretariat
>>
> _______________________________________________
> sfc mailing list
> sfc@ietf.org
> https://www.ietf.org/mailman/listinfo/sfc

-- 
Sevil Mehraghdam
University of Paderborn
Computer Networks group – http://wwwcs.upb.de/cs/ag-karl
Tel.: +49 5251 / 601755
Room: O3.161


From nobody Tue Mar 10 05:31:04 2015
Return-Path: <janl@tail-f.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04FF91ACDF5 for <sfc@ietfa.amsl.com>; Tue, 10 Mar 2015 05:31:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 EHWIlfUpHEgc for <sfc@ietfa.amsl.com>; Tue, 10 Mar 2015 05:30:56 -0700 (PDT)
Received: from mail.tail-f.com (mail.tail-f.com [83.241.162.140]) by ietfa.amsl.com (Postfix) with ESMTP id 924541ACE1E for <sfc@ietf.org>; Tue, 10 Mar 2015 05:30:53 -0700 (PDT)
Received: from [10.148.226.151] (unknown [10.148.226.151]) by mail.tail-f.com (Postfix) with ESMTPSA id C5A411280A11; Tue, 10 Mar 2015 13:30:52 +0100 (CET)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_8A1DE4FA-CCE5-4779-956A-6018E869F59E"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5b5
From: Jan Lindblad <janl@tail-f.com>
In-Reply-To: <D1164C15.B974%repenno@cisco.com>
Date: Tue, 10 Mar 2015 13:29:52 +0100
Message-Id: <51A6EA76-E4A3-460D-9319-8369FA064FCB@tail-f.com>
References: <20150228002942.13121.52348.idtracker@ietfa.amsl.com> <D1164C15.B974%repenno@cisco.com>
To: "Reinaldo Penno (repenno)" <repenno@cisco.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/53Ac2WMMNmFENwbCJW6omja8hl0>
Cc: "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] New Version Notification for draft-penno-sfc-yang-11.txt
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 10 Mar 2015 12:31:04 -0000

--Apple-Mail=_8A1DE4FA-CCE5-4779-956A-6018E869F59E
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_FA954CA9-8317-4EBC-81EA-45B9F0D8B7F1"


--Apple-Mail=_FA954CA9-8317-4EBC-81EA-45B9F0D8B7F1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Reinaldo,

I haven=E2=80=99t seen a lot of review comments on the =
service-function.yang family of modules, so I decided to go through it. =
I=E2=80=99m a "YANG Doctor", so I understand YANG, but I haven=E2=80=99t =
followed the discussion on the list closely.

> On 28 feb 2015, at 01:30, Reinaldo Penno (repenno) <repenno@cisco.com> =
wrote:
...
>> A new version of I-D, draft-penno-sfc-yang-11.txt
>> has been successfully submitted by Reinaldo Penno and posted to the
>> IETF repository.
>>=20
>> Name:		draft-penno-sfc-yang
>> Revision:	11
>> Title:		Yang Data Model for Service Function Chaining
>> Document date:	2015-02-27
>> Group:		Individual Submission
>> Pages:		56
>> URL:
>> http://www.ietf.org/internet-drafts/draft-penno-sfc-yang-11.txt =
<http://www.ietf.org/internet-drafts/draft-penno-sfc-yang-11.txt>

First, I should say I find this document nicely arranged and highly =
readable. Considering that this is an initial review of 50+ pages worth =
of YANG models, I think the number of comments I have is surprisingly =
low. Comments here are more or less in document order.


service-function.yang:
- What is the purpose with rpc put-service-function, rpc =
read-service-function, rpc delete-service-function? If only to =
manipulate the configuration with no specific side effects, they are not =
required. The management protocols (NETCONF, RESTCONF, =E2=80=A6) all =
have built-in mechanisms for creating, reading, deleting etc the =
configuration modeled in the YANG model. I would suggest to remove the =
rpcs.
- The rpc delete-all-service-function may have a slight value, but =
it=E2=80=99s actually very easy to delete all instances with the =
built-in operations in NETCONF, RESTCONF etc.
- leaf request_reclassification, I suggest renaming to =
request-reclassification, in order to follow IETF naming conventions
- list sf-data-plane-locator, I suggest renaming to data-plane-locator, =
in order to follow IETF naming conventions. There is no value in keeping =
prefixes like =E2=80=9Csf-=E2=80=9C indicating the location of the =
object, since that is evident from the object path anyhow.
- leaf service-function-forwarder is of type string. I=E2=80=99m not =
sure I understand what the valid values would be for this string. Is =
this actually a reference? Is there reason to add a few words to the =
description field, or should we perhaps model this differently?
- As mentioned above the rpcs may not be necessary at all, but if any =
rpcs are included, they would often have an output clause, to report =
some sort of status


service-function-type.yang:
- list sft-service-function-name, suggest removing =E2=80=9Csft-=E2=80=9C =
prefix
- leaf name, are these the SF instances? Perhaps clarify the description =
with a few words.


service-function-chain.yang:
- rpc instantiate-service-function-chain, does this modify the =
configuration, or just the operational state?
- rpc put-service-function-chains appears to be unnecessary. Suggest =
removing or explaining the side effects it implements in the =
description.
- list sfc-service-function is ordered by user, but also has a leaf =
order. How do these relate? Lists ordered by user would normally not =
have any leafs suggesting sorting order.


service-function-path.yang:
- leaf classifier is a string. What string values can it take?
- leaf symmetric-classifier is a string. What string values can it take?
- list service-path-hop is ordered by user, but has a key hop-number =
which seems to be the natural sorting key. Remove order-by user?
- leaf service-index, I don=E2=80=99t understand the description. Does =
the description relate to the configuration or to the SFF wire =
operation?
- leaf service-chain-name is a string, should this be a reference?


service-function-forwarder.yang:
- leaf service-node is a string, should this be a reference?
- list sff-data-plane-locator, suggest removing =E2=80=9Csff-=E2=80=9C =
prefix
- container sff-sf-data-plane-locator, suggest removing =E2=80=9Csff-sf-=E2=
=80=9C prefix
- list sff-interfaces, suggest removing =E2=80=9Csff-=E2=80=9C prefix


service-funciton-forwarder-ova.yang:
(no comments)


service-locator.yang:
(no comments)


rendered-service-path.yang:
- list rendered-service-path, leaf name is a string. Should this be a =
reference?
- leaf parent-service-function-path is a string. Should this be a =
reference?
- list rendered-service-path-hop is a config false list keyed by a =
naturally sequenced key hop-number, yet it is marked as order-by user. =
Remove?
- leaf service-chain-name is a string. Should this be a reference?
- rpc delete-rendered-path, will this change the configuration, or just =
op state?
- rpc create-rendered-path, will this change the configuration, or just =
op state?


service-function-classifier.yang:
- the tree diagram is wrong (copy paste problem?)
- leaf bridge is a string. Should this be a reference?
- leaf interface is a string. Should this be a reference?
- leaf access-list is a string. What is the format?
- leaf rendered-service-path is a string. Should this be a reference?
- list scl-service-function-forwarder, suggest removing =E2=80=9Cscl-=E2=80=
=9C prefix


service-function-description-monitor-report.yang:
- config false statement appears to be missing
- rpc get-SF-description, suggest removing. This information can be =
retrieved without any rpc definition.
- rpc get-SF-monitoring-info, suggest removing. This information can be =
retrieved without any rpc definition.


service-function-description-monitor.yang:
(no comments)


/Jan Lindblad


--Apple-Mail=_FA954CA9-8317-4EBC-81EA-45B9F0D8B7F1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">Hi Reinaldo,<div class=3D""><br class=3D""></div><div =
class=3D"">I haven=E2=80=99t seen a lot of review comments on the =
service-function.yang family of modules, so I decided to go through it. =
I=E2=80=99m a "YANG Doctor", so I understand YANG, but I haven=E2=80=99t =
followed the discussion on the list closely.</div><div class=3D""><br =
class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D"">On =
28 feb 2015, at 01:30, Reinaldo Penno (repenno) &lt;<a =
href=3D"mailto:repenno@cisco.com" class=3D"">repenno@cisco.com</a>&gt; =
wrote:</div></blockquote>...<br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><blockquote type=3D"cite" class=3D"">A new =
version of I-D, draft-penno-sfc-yang-11.txt<br class=3D"">has been =
successfully submitted by Reinaldo Penno and posted to the<br =
class=3D"">IETF repository.<br class=3D""><br class=3D"">Name:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>draft-penno-sfc-yang<br class=3D"">Revision:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>11<br =
class=3D"">Title:<span class=3D"Apple-tab-span" style=3D"white-space:pre">=
	</span><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>Yang Data Model for Service Function Chaining<br =
class=3D"">Document date:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>2015-02-27<br =
class=3D"">Group:<span class=3D"Apple-tab-span" style=3D"white-space:pre">=
	</span><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>Individual Submission<br class=3D"">Pages:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>56<br =
class=3D"">URL: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br =
class=3D""><a =
href=3D"http://www.ietf.org/internet-drafts/draft-penno-sfc-yang-11.txt" =
class=3D"">http://www.ietf.org/internet-drafts/draft-penno-sfc-yang-11.txt=
</a><br class=3D""></blockquote></div></blockquote><br =
class=3D""></div><div>First, I should say I find this document nicely =
arranged and highly readable. Considering that this is an initial review =
of 50+ pages worth of YANG models, I think the number of comments I have =
is surprisingly low. Comments here are more or less in document =
order.</div><div><br class=3D""></div><div><br =
class=3D""></div><div>service-function.yang:</div><div>- What is the =
purpose with rpc put-service-function, rpc read-service-function, rpc =
delete-service-function? If only to manipulate the configuration with no =
specific side effects, they are not required. The management protocols =
(NETCONF, RESTCONF, =E2=80=A6) all have built-in mechanisms for =
creating, reading, deleting etc the configuration modeled in the YANG =
model. I would suggest to remove the rpcs.</div><div>- The rpc =
delete-all-service-function may have a slight value, but it=E2=80=99s =
actually very easy to delete all instances with the built-in operations =
in NETCONF, RESTCONF etc.</div><div>- leaf request_reclassification, I =
suggest renaming to request-reclassification, in order to follow IETF =
naming conventions</div><div>- list sf-data-plane-locator, I suggest =
renaming to data-plane-locator, in order to follow IETF naming =
conventions. There is no value in keeping prefixes like =E2=80=9Csf-=E2=80=
=9C indicating the location of the object, since that is evident from =
the object path anyhow.</div><div>- leaf service-function-forwarder is =
of type string. I=E2=80=99m not sure I understand what the valid values =
would be for this string. Is this actually a reference? Is there reason =
to add a few words to the description field, or should we perhaps model =
this differently?</div><div>- As mentioned above the rpcs may not be =
necessary at all, but if any rpcs are included, they would often have an =
output clause, to report some sort of status</div><div><br =
class=3D""></div><div><br =
class=3D""></div><div>service-function-type.yang:</div><div>- list =
sft-service-function-name, suggest removing =E2=80=9Csft-=E2=80=9C =
prefix</div><div>- leaf name, are these the SF instances? Perhaps =
clarify the description with a few words.</div><div><br =
class=3D""></div><div><br =
class=3D""></div><div>service-function-chain.yang:</div><div>- rpc =
instantiate-service-function-chain, does this modify the configuration, =
or just the operational state?</div><div>- rpc =
put-service-function-chains appears to be unnecessary. Suggest removing =
or explaining the side effects it implements in the =
description.</div><div>- list sfc-service-function is ordered by user, =
but also has a leaf order. How do these relate? Lists ordered by user =
would normally not have any leafs suggesting sorting =
order.</div><div><br class=3D""></div><div><br =
class=3D""></div><div>service-function-path.yang:</div><div>- leaf =
classifier is a string. What string values can it take?</div><div>- leaf =
symmetric-classifier is a string. What string values can it =
take?</div><div>- list service-path-hop is ordered by user, but has a =
key hop-number which seems to be the natural sorting key. Remove =
order-by user?</div><div>- leaf service-index, I don=E2=80=99t =
understand the description. Does the description relate to the =
configuration or to the SFF wire operation?</div><div>- leaf =
service-chain-name is a string, should this be a =
reference?</div><div><br class=3D""></div><div><br =
class=3D""></div><div>service-function-forwarder.yang:</div><div>- leaf =
service-node is a string, should this be a reference?</div><div>- list =
sff-data-plane-locator, suggest removing =E2=80=9Csff-=E2=80=9C =
prefix</div><div>- container sff-sf-data-plane-locator, suggest removing =
=E2=80=9Csff-sf-=E2=80=9C prefix</div><div>- list sff-interfaces, =
suggest removing =E2=80=9Csff-=E2=80=9C prefix</div><div><br =
class=3D""></div><div><br =
class=3D""></div><div>service-funciton-forwarder-ova.yang:</div><div>(no =
comments)</div><div><br class=3D""></div><div><br =
class=3D""></div><div>service-locator.yang:</div><div><div>(no =
comments)</div><div class=3D""><br class=3D""></div></div><div><br =
class=3D""></div><div>rendered-service-path.yang:</div><div>- list =
rendered-service-path, leaf name is a string. Should this be a =
reference?</div></div><div>- leaf parent-service-function-path is a =
string. Should this be a reference?</div><div>- list =
rendered-service-path-hop is a config false list keyed by a naturally =
sequenced key hop-number, yet it is marked as order-by user. =
Remove?</div><div>- leaf service-chain-name is a string. Should this be =
a reference?</div><div>- rpc delete-rendered-path, will this change the =
configuration, or just op state?</div><div>- rpc create-rendered-path, =
will this change the configuration, or just op state?</div><div><div =
class=3D""><br class=3D""></div></div><div><br =
class=3D""></div><div>service-function-classifier.yang:</div><div>- the =
tree diagram is wrong (copy paste problem?)</div><div>- leaf bridge is a =
string. Should this be a reference?</div><div>- leaf interface is a =
string. Should this be a reference?</div><div>- leaf access-list is a =
string. What is the format?</div><div>- leaf rendered-service-path is a =
string. Should this be a reference?</div><div>- list =
scl-service-function-forwarder, suggest removing =E2=80=9Cscl-=E2=80=9C =
prefix</div><div><br class=3D""></div><div><br =
class=3D""></div><div>service-function-description-monitor-report.yang:</d=
iv><div>- config false statement appears to be missing</div><div>- rpc =
get-SF-description, suggest removing. This information can be retrieved =
without any rpc definition.</div><div>- rpc get-SF-monitoring-info, =
suggest removing. This information can be retrieved without any rpc =
definition.</div><div><br class=3D""></div><div><br =
class=3D""></div><div>service-function-description-monitor.yang:</div><div=
><div>(no comments)</div><div class=3D""><br class=3D""></div><div =
class=3D""><br class=3D""></div><div class=3D"">/Jan Lindblad</div><div =
class=3D""><br class=3D""></div></div></body></html>=

--Apple-Mail=_FA954CA9-8317-4EBC-81EA-45B9F0D8B7F1--

--Apple-Mail=_8A1DE4FA-CCE5-4779-956A-6018E869F59E
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJU/uPAAAoJEBSCnbqufIis1tYH/1QwRGM5D9g5pFyVZYNK01rV
4hubnHGU1VmCG4FA0cG0oPG6R3CQhufvwgzSwY8wbpVMRK3PYwVEPinnOeUFHUwu
Syj7n01neimiKGwx3oOog59VLrLklNbcnI7GQykNZON1tdG1H0LjVZA4N1T0QxN5
/DXBT85vVlvFhJoBuv6hfXrX/3bvAckBvSSEMfSx8DM1LZrIQszdRvpF9vJnOaec
4QdjiaxOJZ3M6Yh+0bEKe8GVA0ExF6gDcUQXTMZ6XZSQjAO/o6gnEEQjdcPyXS2H
Ih13vkxmExqGyMTdCZI4rNZp+XZ7DQepDn1YOAPak4+HeuARwpd+JrnSYj3gGhU=
=UBuj
-----END PGP SIGNATURE-----

--Apple-Mail=_8A1DE4FA-CCE5-4779-956A-6018E869F59E--


From nobody Tue Mar 10 08:51:57 2015
Return-Path: <repenno@cisco.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65D371A06FD for <sfc@ietfa.amsl.com>; Tue, 10 Mar 2015 08:51:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 7_zlBVvz0ZF9 for <sfc@ietfa.amsl.com>; Tue, 10 Mar 2015 08:51:50 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B28C31A0027 for <sfc@ietf.org>; Tue, 10 Mar 2015 08:51:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=16541; q=dns/txt; s=iport; t=1426002712; x=1427212312; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=/6RxTMbi5czyyHzeo+/eTyl2pDYCCgTNVxuNiyigqN0=; b=BxuKKJX20k+dlWxEeddXrTPMYPcq4C0FAidugcG9ihV/DgjnC9PGJmeX P+hxeCCZ8ez5ze7blJ5F3n6knfa4D4tAbaClopwyM8D4Kr8Od9Swm9JyD I8UMq73fFyHOsYgihMofi8+BZiPkmIMwJ0oDlJ+TDi6PD2kYMhlcGyG9p k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AOBQAMEv9U/5NdJa1cgkNDUloEwyaFcAKBMU0BAQEBAQF8hA8BAQEEdwIQAgEIEQECAQIoBzIUAwYIAgQOBQmIJg3EAwEBAQEBBQEBAQEBAQEBGosXhF0RB4QtBYV6ihWFfoNVgRqFfIkcg0Ijg25vAYFDfwEBAQ
X-IronPort-AV: E=Sophos;i="5.11,375,1422921600";  d="scan'208,217";a="402399209"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by rcdn-iport-5.cisco.com with ESMTP; 10 Mar 2015 15:51:51 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id t2AFpn2p022815 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 10 Mar 2015 15:51:49 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.150]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.03.0195.001; Tue, 10 Mar 2015 10:51:49 -0500
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: Jan Lindblad <janl@tail-f.com>
Thread-Topic: [sfc] New Version Notification for draft-penno-sfc-yang-11.txt
Thread-Index: AQHQUu2n/C7BQSx4dkuqNnWQvAX+JZ0FFDKAgBD1lAD//8MSgA==
Date: Tue, 10 Mar 2015 15:51:48 +0000
Message-ID: <D12460CB.C68D%repenno@cisco.com>
References: <20150228002942.13121.52348.idtracker@ietfa.amsl.com> <D1164C15.B974%repenno@cisco.com> <51A6EA76-E4A3-460D-9319-8369FA064FCB@tail-f.com>
In-Reply-To: <51A6EA76-E4A3-460D-9319-8369FA064FCB@tail-f.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.7.141117
x-originating-ip: [10.24.101.5]
Content-Type: multipart/alternative; boundary="_000_D12460CBC68Drepennociscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/HKDnNei-m8lxHir-RZlqwXWZ1Co>
Cc: "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] New Version Notification for draft-penno-sfc-yang-11.txt
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 10 Mar 2015 15:51:55 -0000

--_000_D12460CBC68Drepennociscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Thanks Jan, I will go though your comments and provide detailed answers.

In the newsiest version (13) I added a section explaining the overall archi=
tecture of the Yang models that might help readers.

Thanks,

Reinaldo

From: Jan Lindblad <janl@tail-f.com<mailto:janl@tail-f.com>>
Date: Tuesday, March 10, 2015 at 5:29 AM
To: Reinaldo Penno <repenno@cisco.com<mailto:repenno@cisco.com>>
Cc: "sfc@ietf.org<mailto:sfc@ietf.org>" <sfc@ietf.org<mailto:sfc@ietf.org>>
Subject: Re: [sfc] New Version Notification for draft-penno-sfc-yang-11.txt

Hi Reinaldo,

I haven=92t seen a lot of review comments on the service-function.yang fami=
ly of modules, so I decided to go through it. I=92m a "YANG Doctor", so I u=
nderstand YANG, but I haven=92t followed the discussion on the list closely=
.

On 28 feb 2015, at 01:30, Reinaldo Penno (repenno) <repenno@cisco.com<mailt=
o:repenno@cisco.com>> wrote:
...
A new version of I-D, draft-penno-sfc-yang-11.txt
has been successfully submitted by Reinaldo Penno and posted to the
IETF repository.

Name: draft-penno-sfc-yang
Revision: 11
Title: Yang Data Model for Service Function Chaining
Document date: 2015-02-27
Group: Individual Submission
Pages: 56
URL:
http://www.ietf.org/internet-drafts/draft-penno-sfc-yang-11.txt

First, I should say I find this document nicely arranged and highly readabl=
e. Considering that this is an initial review of 50+ pages worth of YANG mo=
dels, I think the number of comments I have is surprisingly low. Comments h=
ere are more or less in document order.


service-function.yang:
- What is the purpose with rpc put-service-function, rpc read-service-funct=
ion, rpc delete-service-function? If only to manipulate the configuration w=
ith no specific side effects, they are not required. The management protoco=
ls (NETCONF, RESTCONF, =85) all have built-in mechanisms for creating, read=
ing, deleting etc the configuration modeled in the YANG model. I would sugg=
est to remove the rpcs.
- The rpc delete-all-service-function may have a slight value, but it=92s a=
ctually very easy to delete all instances with the built-in operations in N=
ETCONF, RESTCONF etc.
- leaf request_reclassification, I suggest renaming to request-reclassifica=
tion, in order to follow IETF naming conventions
- list sf-data-plane-locator, I suggest renaming to data-plane-locator, in =
order to follow IETF naming conventions. There is no value in keeping prefi=
xes like =93sf-=93 indicating the location of the object, since that is evi=
dent from the object path anyhow.
- leaf service-function-forwarder is of type string. I=92m not sure I under=
stand what the valid values would be for this string. Is this actually a re=
ference? Is there reason to add a few words to the description field, or sh=
ould we perhaps model this differently?
- As mentioned above the rpcs may not be necessary at all, but if any rpcs =
are included, they would often have an output clause, to report some sort o=
f status


service-function-type.yang:
- list sft-service-function-name, suggest removing =93sft-=93 prefix
- leaf name, are these the SF instances? Perhaps clarify the description wi=
th a few words.


service-function-chain.yang:
- rpc instantiate-service-function-chain, does this modify the configuratio=
n, or just the operational state?
- rpc put-service-function-chains appears to be unnecessary. Suggest removi=
ng or explaining the side effects it implements in the description.
- list sfc-service-function is ordered by user, but also has a leaf order. =
How do these relate? Lists ordered by user would normally not have any leaf=
s suggesting sorting order.


service-function-path.yang:
- leaf classifier is a string. What string values can it take?
- leaf symmetric-classifier is a string. What string values can it take?
- list service-path-hop is ordered by user, but has a key hop-number which =
seems to be the natural sorting key. Remove order-by user?
- leaf service-index, I don=92t understand the description. Does the descri=
ption relate to the configuration or to the SFF wire operation?
- leaf service-chain-name is a string, should this be a reference?


service-function-forwarder.yang:
- leaf service-node is a string, should this be a reference?
- list sff-data-plane-locator, suggest removing =93sff-=93 prefix
- container sff-sf-data-plane-locator, suggest removing =93sff-sf-=93 prefi=
x
- list sff-interfaces, suggest removing =93sff-=93 prefix


service-funciton-forwarder-ova.yang:
(no comments)


service-locator.yang:
(no comments)


rendered-service-path.yang:
- list rendered-service-path, leaf name is a string. Should this be a refer=
ence?
- leaf parent-service-function-path is a string. Should this be a reference=
?
- list rendered-service-path-hop is a config false list keyed by a naturall=
y sequenced key hop-number, yet it is marked as order-by user. Remove?
- leaf service-chain-name is a string. Should this be a reference?
- rpc delete-rendered-path, will this change the configuration, or just op =
state?
- rpc create-rendered-path, will this change the configuration, or just op =
state?


service-function-classifier.yang:
- the tree diagram is wrong (copy paste problem?)
- leaf bridge is a string. Should this be a reference?
- leaf interface is a string. Should this be a reference?
- leaf access-list is a string. What is the format?
- leaf rendered-service-path is a string. Should this be a reference?
- list scl-service-function-forwarder, suggest removing =93scl-=93 prefix


service-function-description-monitor-report.yang:
- config false statement appears to be missing
- rpc get-SF-description, suggest removing. This information can be retriev=
ed without any rpc definition.
- rpc get-SF-monitoring-info, suggest removing. This information can be ret=
rieved without any rpc definition.


service-function-description-monitor.yang:
(no comments)


/Jan Lindblad


--_000_D12460CBC68Drepennociscocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <81450F7C0B992048A83D5EB865F0CE24@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>Thanks Jan, I will go though your comments and provide detailed answer=
s.&nbsp;</div>
<div><br>
</div>
<div>In the newsiest version (13) I added a section explaining the overall =
architecture of the Yang models that might help readers.</div>
<div><br>
</div>
<div>Thanks,</div>
<div><br>
</div>
<div>Reinaldo</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>Jan Lindblad &lt;<a href=3D"m=
ailto:janl@tail-f.com">janl@tail-f.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Tuesday, March 10, 2015 at 5:=
29 AM<br>
<span style=3D"font-weight:bold">To: </span>Reinaldo Penno &lt;<a href=3D"m=
ailto:repenno@cisco.com">repenno@cisco.com</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>&quot;<a href=3D"mailto:sfc@iet=
f.org">sfc@ietf.org</a>&quot; &lt;<a href=3D"mailto:sfc@ietf.org">sfc@ietf.=
org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Re: [sfc] New Version Noti=
fication for draft-penno-sfc-yang-11.txt<br>
</div>
<div><br>
</div>
<div>
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space;" class=3D"">
Hi Reinaldo,
<div class=3D""><br class=3D"">
</div>
<div class=3D"">I haven=92t seen a lot of review comments on the service-fu=
nction.yang family of modules, so I decided to go through it. I=92m a &quot=
;YANG Doctor&quot;, so I understand YANG, but I haven=92t followed the disc=
ussion on the list closely.</div>
<div class=3D""><br class=3D"">
<div>
<blockquote type=3D"cite" class=3D"">
<div class=3D"">On 28 feb 2015, at 01:30, Reinaldo Penno (repenno) &lt;<a h=
ref=3D"mailto:repenno@cisco.com" class=3D"">repenno@cisco.com</a>&gt; wrote=
:</div>
</blockquote>
...<br class=3D"">
<blockquote type=3D"cite" class=3D"">
<div class=3D"">
<blockquote type=3D"cite" class=3D"">A new version of I-D, draft-penno-sfc-=
yang-11.txt<br class=3D"">
has been successfully submitted by Reinaldo Penno and posted to the<br clas=
s=3D"">
IETF repository.<br class=3D"">
<br class=3D"">
Name:<span class=3D"Apple-tab-span" style=3D"white-space:pre"> </span><span=
 class=3D"Apple-tab-span" style=3D"white-space:pre"></span>draft-penno-sfc-=
yang<br class=3D"">
Revision:<span class=3D"Apple-tab-span" style=3D"white-space:pre"> </span>1=
1<br class=3D"">
Title:<span class=3D"Apple-tab-span" style=3D"white-space:pre"> </span><spa=
n class=3D"Apple-tab-span" style=3D"white-space:pre"></span>Yang Data Model=
 for Service Function Chaining<br class=3D"">
Document date:<span class=3D"Apple-tab-span" style=3D"white-space:pre"> </s=
pan>2015-02-27<br class=3D"">
Group:<span class=3D"Apple-tab-span" style=3D"white-space:pre"> </span><spa=
n class=3D"Apple-tab-span" style=3D"white-space:pre"></span>Individual Subm=
ission<br class=3D"">
Pages:<span class=3D"Apple-tab-span" style=3D"white-space:pre"> </span><spa=
n class=3D"Apple-tab-span" style=3D"white-space:pre"></span>56<br class=3D"=
">
URL: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br =
class=3D"">
<a href=3D"http://www.ietf.org/internet-drafts/draft-penno-sfc-yang-11.txt"=
 class=3D"">http://www.ietf.org/internet-drafts/draft-penno-sfc-yang-11.txt=
</a><br class=3D"">
</blockquote>
</div>
</blockquote>
<br class=3D"">
</div>
<div>First, I should say I find this document nicely arranged and highly re=
adable. Considering that this is an initial review of 50&#43; pages worth o=
f YANG models, I think the number of comments I have is surprisingly low. C=
omments here are more or less in document
 order.</div>
<div><br class=3D"">
</div>
<div><br class=3D"">
</div>
<div>service-function.yang:</div>
<div>- What is the purpose with rpc put-service-function, rpc read-service-=
function, rpc delete-service-function? If only to manipulate the configurat=
ion with no specific side effects, they are not required. The management pr=
otocols (NETCONF, RESTCONF, =85) all
 have built-in mechanisms for creating, reading, deleting etc the configura=
tion modeled in the YANG model. I would suggest to remove the rpcs.</div>
<div>- The rpc delete-all-service-function may have a slight value, but it=
=92s actually very easy to delete all instances with the built-in operation=
s in NETCONF, RESTCONF etc.</div>
<div>- leaf request_reclassification, I suggest renaming to request-reclass=
ification, in order to follow IETF naming conventions</div>
<div>- list sf-data-plane-locator, I suggest renaming to data-plane-locator=
, in order to follow IETF naming conventions. There is no value in keeping =
prefixes like =93sf-=93 indicating the location of the object, since that i=
s evident from the object path anyhow.</div>
<div>- leaf service-function-forwarder is of type string. I=92m not sure I =
understand what the valid values would be for this string. Is this actually=
 a reference? Is there reason to add a few words to the description field, =
or should we perhaps model this differently?</div>
<div>- As mentioned above the rpcs may not be necessary at all, but if any =
rpcs are included, they would often have an output clause, to report some s=
ort of status</div>
<div><br class=3D"">
</div>
<div><br class=3D"">
</div>
<div>service-function-type.yang:</div>
<div>- list sft-service-function-name, suggest removing =93sft-=93 prefix</=
div>
<div>- leaf name, are these the SF instances? Perhaps clarify the descripti=
on with a few words.</div>
<div><br class=3D"">
</div>
<div><br class=3D"">
</div>
<div>service-function-chain.yang:</div>
<div>- rpc instantiate-service-function-chain, does this modify the configu=
ration, or just the operational state?</div>
<div>- rpc put-service-function-chains appears to be unnecessary. Suggest r=
emoving or explaining the side effects it implements in the description.</d=
iv>
<div>- list sfc-service-function is ordered by user, but also has a leaf or=
der. How do these relate? Lists ordered by user would normally not have any=
 leafs suggesting sorting order.</div>
<div><br class=3D"">
</div>
<div><br class=3D"">
</div>
<div>service-function-path.yang:</div>
<div>- leaf classifier is a string. What string values can it take?</div>
<div>- leaf symmetric-classifier is a string. What string values can it tak=
e?</div>
<div>- list service-path-hop is ordered by user, but has a key hop-number w=
hich seems to be the natural sorting key. Remove order-by user?</div>
<div>- leaf service-index, I don=92t understand the description. Does the d=
escription relate to the configuration or to the SFF wire operation?</div>
<div>- leaf service-chain-name is a string, should this be a reference?</di=
v>
<div><br class=3D"">
</div>
<div><br class=3D"">
</div>
<div>service-function-forwarder.yang:</div>
<div>- leaf service-node is a string, should this be a reference?</div>
<div>- list sff-data-plane-locator, suggest removing =93sff-=93 prefix</div=
>
<div>- container sff-sf-data-plane-locator, suggest removing =93sff-sf-=93 =
prefix</div>
<div>- list sff-interfaces, suggest removing =93sff-=93 prefix</div>
<div><br class=3D"">
</div>
<div><br class=3D"">
</div>
<div>service-funciton-forwarder-ova.yang:</div>
<div>(no comments)</div>
<div><br class=3D"">
</div>
<div><br class=3D"">
</div>
<div>service-locator.yang:</div>
<div>
<div>(no comments)</div>
<div class=3D""><br class=3D"">
</div>
</div>
<div><br class=3D"">
</div>
<div>rendered-service-path.yang:</div>
<div>- list rendered-service-path, leaf name is a string. Should this be a =
reference?</div>
</div>
<div>- leaf parent-service-function-path is a string. Should this be a refe=
rence?</div>
<div>- list rendered-service-path-hop is a config false list keyed by a nat=
urally sequenced key hop-number, yet it is marked as order-by user. Remove?=
</div>
<div>- leaf service-chain-name is a string. Should this be a reference?</di=
v>
<div>- rpc delete-rendered-path, will this change the configuration, or jus=
t op state?</div>
<div>- rpc create-rendered-path, will this change the configuration, or jus=
t op state?</div>
<div>
<div class=3D""><br class=3D"">
</div>
</div>
<div><br class=3D"">
</div>
<div>service-function-classifier.yang:</div>
<div>- the tree diagram is wrong (copy paste problem?)</div>
<div>- leaf bridge is a string. Should this be a reference?</div>
<div>- leaf interface is a string. Should this be a reference?</div>
<div>- leaf access-list is a string. What is the format?</div>
<div>- leaf rendered-service-path is a string. Should this be a reference?<=
/div>
<div>- list scl-service-function-forwarder, suggest removing =93scl-=93 pre=
fix</div>
<div><br class=3D"">
</div>
<div><br class=3D"">
</div>
<div>service-function-description-monitor-report.yang:</div>
<div>- config false statement appears to be missing</div>
<div>- rpc get-SF-description, suggest removing. This information can be re=
trieved without any rpc definition.</div>
<div>- rpc get-SF-monitoring-info, suggest removing. This information can b=
e retrieved without any rpc definition.</div>
<div><br class=3D"">
</div>
<div><br class=3D"">
</div>
<div>service-function-description-monitor.yang:</div>
<div>
<div>(no comments)</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">/Jan Lindblad</div>
<div class=3D""><br class=3D"">
</div>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_D12460CBC68Drepennociscocom_--


From nobody Tue Mar 10 19:29:14 2015
Return-Path: <bill.wu@huawei.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EA141A8899; Tue, 10 Mar 2015 19:29:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 pNoyxYqq0eeJ; Tue, 10 Mar 2015 19:29:11 -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 191C51A90DB; Tue, 10 Mar 2015 19:29:10 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BQC42460; Wed, 11 Mar 2015 02:29:09 +0000 (GMT)
Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 11 Mar 2015 02:24:59 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.146]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.03.0158.001; Wed, 11 Mar 2015 10:24:54 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "sfc@ietf.org" <sfc@ietf.org>, "pce@ietf.org" <pce@ietf.org>
Thread-Topic: New Version Notification for draft-wu-pce-traffic-steering-sfc-06.txt
Thread-Index: AQHQVuqm/XFwxvn6l0KO6yTJFND6T50WlH5A
Date: Wed, 11 Mar 2015 02:24:54 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA846E08F0@nkgeml501-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.138.41.180]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/5q_WGLpaO-lOFcTQqBKfXdW4F8w>
Subject: Re: [sfc] New Version Notification for draft-wu-pce-traffic-steering-sfc-06.txt
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 11 Mar 2015 02:29:13 -0000

SGksIGZvbGtzOg0KSGVyZSBpcyB0aGUgdXBkYXRlIHRvIGRyYWZ0LXd1LXBjZS10cmFmZmljLXN0
ZWVyaW5nLXNmYy0wNiBiYXNlZCBvbiByZWxldmFudCBkaXNjdXNzaW9uIHJlZ2FyZGluZyBTdXBw
b3J0IG9mIFNGIFNwaXJhbHMgb24gdGhlIFNGQyBsaXN0Lg0KaHR0cDovL3d3dy5pZXRmLm9yZy9p
bnRlcm5ldC1kcmFmdHMvZHJhZnQtd3UtcGNlLXRyYWZmaWMtc3RlZXJpbmctc2ZjLTA2LnR4dA0K
V2UgY2FuIHNlZSBTRlAgSWRlbnRpZmllciBpcyByZXF1aXJlZCBieSBib3RoIFNGRiBhbmQgQ2xh
c3NpZmllci4NCg0KSW4gdGhpcyB1cGRhdGUsIHdlIGdpdmUgdGhlIFNGUCBJZGVudGlmaWVyIGZv
cm1hdCBhbmQgDQpkZWZpbmUgb3BlcmF0aW9uIG9mIFNGUCBJZGVudGlmaWVyIHdoaWNoIGlzIHRv
IGdldCBpbiBsaW5lIHdpdGggDQpkcmFmdC1xdWlubi1zZmMtbnNoIGFuZCBkcmFmdC1pZXRmLXNm
Yy1hcmNoaXRlY3R1cmUuDQpUaGUgZGlmZiBpczoNCmh0dHA6Ly93d3cuaWV0Zi5vcmcvcmZjZGlm
Zj91cmwyPWRyYWZ0LXd1LXBjZS10cmFmZmljLXN0ZWVyaW5nLXNmYy0wNg0KDQpZb3VyIGNvbW1l
bnRzIGFuZCBzdWdnZXN0aW9ucyBhcmUgd2VsY29tZSENCg0KUmVnYXJkcyENCi1RaW4NCi0tLS0t
6YKu5Lu25Y6f5Lu2LS0tLS0NCuWPkeS7tuS6ujogaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnIFtt
YWlsdG86aW50ZXJuZXQtZHJhZnRzQGlldGYub3JnXSANCuWPkemAgeaXtumXtDogMjAxNeW5tDPm
nIg15pelIDEwOjE4DQrmlLbku7bkuro6IFFpbiBXdTsgUWluIFd1OyBKZWZmIFRhbnRzdXJhOyBE
aHJ1diBEaG9keTsgQ2hyaXN0aWFuIEphY3F1ZW5ldDsgRGhydXYgRGhvZHk7IE1vaGFtZWQgQm91
Y2FkYWlyOyBDaHJpc3RpYW4gSmFjcXVlbmV0OyBKZWZmIFRhbnRzdXJhOyBNb2hhbWVkIEJvdWNh
ZGFpcg0K5Li76aKYOiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9yIGRyYWZ0LXd1LXBjZS10
cmFmZmljLXN0ZWVyaW5nLXNmYy0wNi50eHQNCg0KDQpBIG5ldyB2ZXJzaW9uIG9mIEktRCwgZHJh
ZnQtd3UtcGNlLXRyYWZmaWMtc3RlZXJpbmctc2ZjLTA2LnR4dA0KaGFzIGJlZW4gc3VjY2Vzc2Z1
bGx5IHN1Ym1pdHRlZCBieSBRaW4gV3UgYW5kIHBvc3RlZCB0byB0aGUgSUVURiByZXBvc2l0b3J5
Lg0KDQpOYW1lOgkJZHJhZnQtd3UtcGNlLXRyYWZmaWMtc3RlZXJpbmctc2ZjDQpSZXZpc2lvbjoJ
MDYNClRpdGxlOgkJUENFUCBFeHRlbnNpb25zIGZvciB0cmFmZmljIHN0ZWVyaW5nIHN1cHBvcnQg
aW4gU2VydmljZSBGdW5jdGlvbiBDaGFpbmluZw0KRG9jdW1lbnQgZGF0ZToJMjAxNS0wMy0wNA0K
R3JvdXA6CQlJbmRpdmlkdWFsIFN1Ym1pc3Npb24NClBhZ2VzOgkJMTANClVSTDogICAgICAgICAg
ICBodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC13dS1wY2UtdHJhZmZp
Yy1zdGVlcmluZy1zZmMtMDYudHh0DQpTdGF0dXM6ICAgICAgICAgaHR0cHM6Ly9kYXRhdHJhY2tl
ci5pZXRmLm9yZy9kb2MvZHJhZnQtd3UtcGNlLXRyYWZmaWMtc3RlZXJpbmctc2ZjLw0KSHRtbGl6
ZWQ6ICAgICAgIGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LXd1LXBjZS10cmFmZmlj
LXN0ZWVyaW5nLXNmYy0wNg0KRGlmZjogICAgICAgICAgIGh0dHA6Ly93d3cuaWV0Zi5vcmcvcmZj
ZGlmZj91cmwyPWRyYWZ0LXd1LXBjZS10cmFmZmljLXN0ZWVyaW5nLXNmYy0wNg0KDQpBYnN0cmFj
dDoNCiAgIFRoaXMgZG9jdW1lbnQgcHJvdmlkZXMgYW4gb3ZlcnZpZXcgb2YgdGhlIHVzYWdlIG9m
IFBhdGggQ29tcHV0YXRpb24NCiAgIEVsZW1lbnQgKFBDRSkgd2l0aCBTZXJ2aWNlIEZ1bmN0aW9u
IENoYWluaW5nIChTRkMpOyB3aGljaCBpcw0KICAgZGVzY3JpYmVkIGFzIHRoZSBkZWZpbml0aW9u
IGFuZCBpbnN0YW50aWF0aW9uIG9mIGFuIG9yZGVyZWQgc2V0IG9mDQogICBzdWNoIHNlcnZpY2Ug
ZnVuY3Rpb25zIChzdWNoIGFzIGZpcmV3YWxscywgbG9hZCBiYWxhbmNlcnMpLCBhbmQgdGhlDQog
ICBzdWJzZXF1ZW50ICJzdGVlcmluZyIgb2YgdHJhZmZpYyBmbG93cyB0aHJvdWdoIHRob3NlIHNl
cnZpY2UNCiAgIGZ1bmN0aW9ucy4NCg0KICAgVGhpcyBkb2N1bWVudCBzcGVjaWZpZXMgZXh0ZW5z
aW9ucyB0byB0aGUgUGF0aCBDb21wdXRhdGlvbiBFbGVtZW50DQogICBQcm90b2NvbCAoUENFUCkg
dGhhdCBhbGxvdyBhIHN0YXRlZnVsIFBDRSB0byBjb21wdXRlIGFuZCBpbnN0YW50aWF0ZQ0KICAg
U2VydmljZSBGdW5jdGlvbiBQYXRocyAoU0ZQKS4NCg0KICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
IA0KDQoNClBsZWFzZSBub3RlIHRoYXQgaXQgbWF5IHRha2UgYSBjb3VwbGUgb2YgbWludXRlcyBm
cm9tIHRoZSB0aW1lIG9mIHN1Ym1pc3Npb24gdW50aWwgdGhlIGh0bWxpemVkIHZlcnNpb24gYW5k
IGRpZmYgYXJlIGF2YWlsYWJsZSBhdCB0b29scy5pZXRmLm9yZy4NCg0KVGhlIElFVEYgU2VjcmV0
YXJpYXQNCg0K


From nobody Thu Mar 12 12:29:37 2015
Return-Path: <linda.dunbar@huawei.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C48D21A0107 for <sfc@ietfa.amsl.com>; Thu, 12 Mar 2015 12:29:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 PYlc8nR1l68G for <sfc@ietfa.amsl.com>; Thu, 12 Mar 2015 12:29: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 203601A000B for <sfc@ietf.org>; Thu, 12 Mar 2015 12:29:32 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml403-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BTO74224; Thu, 12 Mar 2015 19:29:31 +0000 (GMT)
Received: from DFWEML702-CHM.china.huawei.com (10.193.5.72) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 12 Mar 2015 19:29:30 +0000
Received: from DFWEML701-CHM.china.huawei.com ([10.193.5.50]) by dfweml702-chm ([10.193.5.72]) with mapi id 14.03.0158.001; Thu, 12 Mar 2015 12:29:23 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: Thomas Narten <narten@us.ibm.com>, "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: [sfc] Call for Dallas SFC Agenda Topics
Thread-Index: AQHQVRxSzjAjQoBjrEOiNH0pLo0i2J0ZQpew
Date: Thu, 12 Mar 2015 19:29:24 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F645EEDEEE@dfweml701-chm>
References: <m3lhjfp69j.wl-narten@us.ibm.com>
In-Reply-To: <m3lhjfp69j.wl-narten@us.ibm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.154.126]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/KerwRvsvm2m96tjyx3a9iELvK0c>
Subject: Re: [sfc] Call for Dallas SFC Agenda Topics
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 12 Mar 2015 19:29:35 -0000

VGhvbWFzIGFuZCBKaW0sIA0KDQpUaGVyZSBhcmUgc2V2ZXJhbCBkcmFmdHMgb24gdGhlIFNGQyBD
b250cm9sIFBsYW5lOg0KDQotICBkcmFmdC13dy1zZmMtY29udHJvbC1wbGFuZS0wNA0KLSAgZHJh
ZnQta2FuZy1zZmMtZmFpbG92ZXItMDEgIA0KLSAgZHJhZnQtZHVuYmFyLXNmYy1wYXRoLWNvbnRy
b2wtMDENCi0gIGRyYWZ0LWt1bWFyLXNmYy1vZmZsb2Fkcy0wMA0KDQpUaGVyZSBhcmUgbWFueSB3
YXlzIHRvIGNvbnRyb2wgdGhlIHNlcnZpY2UgZnVuY3Rpb24gcGF0aCBhbmQgaG93IHRoZSBTRkMg
cGF0aCBiZWluZyBhbHRlcmVkIGR5bmFtaWNhbGx5LiANCmRyYWZ0LWt1bWFyLXNmYy1vZmZsb2Fk
cy0wMCAgIGRlc2NyaWJlcyBvbmUgd2F5IG9mIFNGQyBwYXRoIGJlaW5nIGFsdGVyZWQgKGkuZS4g
c29tZSBTRiBiZWluZyByZW1vdmVkIGZyb20gdGhlIHBhdGgpIGFzIHRoZSByZXN1bHQgb2Ygb3Ro
ZXIgc2VydmljZSBmdW5jdGlvbnMnIGV4ZWN1dGlvbiBzdGF0dXMuIA0KVGhlIFNGQyBwYXRoIGNh
biBhbHNvIGJlIGR5bmFtaWNhbGx5IGNoYW5nZWQgYnkgTmV0d29yayBDb250cm9sbGVyIHRyaWdn
ZXJlZCBieSBvdGhlciBldmVudHMuIA0KDQpJTUhPLCB0aGUgU0ZDIGNvbnRyb2wgcGxhbmUgc2hv
dWxkIGJlIGRpc2N1c3NlZCBieSB0aGUgV0cgYmVmb3JlIGp1bXBpbmcgaW50byBvbmUgc3BlY2lm
aWMgYXBwcm9hY2guIA0KDQpDYW4gd2UgaGF2ZSBhIHNsb3QgdG8gZGlzY3VzcyB0aGUgU0ZDIGNv
bnRyb2wgcGxhbmUgYXQgdGhpcyBTRkMgbWVldGluZz8gDQoNCg0KTGluZGENCi0tLS0tT3JpZ2lu
YWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBzZmMgW21haWx0bzpzZmMtYm91bmNlc0BpZXRmLm9yZ10g
T24gQmVoYWxmIE9mIFRob21hcyBOYXJ0ZW4NClNlbnQ6IE1vbmRheSwgTWFyY2ggMDIsIDIwMTUg
MTowOCBQTQ0KVG86IHNmY0BpZXRmLm9yZw0KU3ViamVjdDogW3NmY10gQ2FsbCBmb3IgRGFsbGFz
IFNGQyBBZ2VuZGEgVG9waWNzDQoNCkdyZWV0aW5ncyBXRzoNCg0KT3VyIG1lZXRpbmcgYXQgdGhl
IHVwY29taW5nIERhbGxhcyB2ZW51ZSBpcyBmYXN0IGFwcHJvYWNoaW5nLiAgQXMgYWx3YXlzLCB0
aGUgZ29hbCBvZiB0aGUgbWVldGluZyB3aWxsIGJlIHRvIG1ha2UgdGhlIGJlc3QgdXNlIG9mIGxp
bWl0ZWQgZmFjZS10by1mYWNlIHRpbWUuDQoNCkFzIHdlIGJ1aWxkIHRoZSBtZWV0aW5nIGFnZW5k
YSB3ZSB3ZWxjb21lIHJlcXVlc3RzIGZvciBhZ2VuZGEgdGltZS4gQXMgYWx3YXlzLCB0aGUgZ29h
bCBvZiBhIG1lZXRpbmcgc2xvdCBpcyB0byBiZXN0IGZ1cnRoZXIgdGhlIHdvcmsgb2YgdGhlIFdH
LCBhbmQgdGhhdCBnZW5lcmFsbHkgbWVhbnMgZm9jdXNzaW5nIG9uIGtleSBjaGFydGVyIGRlbGl2
ZXJhYmxlcyBhbmQgdG9waWNzIHdpdGggaW1wb3J0YW50IG9wZW4gaXNzdWVzIHRvIHJlc29sdmUu
IEluIHRoZSBjYXNlIG9mIGluZGl2aWR1YWwgSURzLCB0aGUgZ29hbCBpc27ulZogbmVjZXNzYXJp
bHkgdG8gcHJlc2VudCB3aGF0IGlzIGluIHRoZSBkcmFmdCBidXQgcmF0aGVyIHRvIGhlbHAgdGhl
IFdHIGRlY2lkZSB3aGF0IHRvIGRvIHdpdGggdGhlIElELiBXaXRoIHRoYXQgaW4gbWluZCwgd2hl
biBtYWtpbmcgYW4gYWdlbmRhIHJlcXVlc3QgcGxlYXNlIGNvbnNpZGVyIHdoYXQgeW91IHRoaW5r
IHRoZSBXRyBzaG91bGQgZG8gd2l0aCBpdHMgY29udGVudC4gRm9yDQpleGFtcGxlOg0KDQogICog
RG9lcyB0aGUgZG9jdW1lbnQgaGF2ZSB1c2VmdWwgY29udGVudCB0aGF0IHNob3VsZCBiZSBtb3Zl
ZCBpbnRvIGFub3RoZXIgV0cNCiAgICBkb2N1bWVudCBvciBwcm9ncmVzcyBvbiBpdO6VmSBvd24g
bWVyaXQNCiAgKiBEb2VzIHRoZSBjb250ZW50IGhhdmUgYSBnb29kIGJhc2lzIGZvciBvbmUgb2Yg
dGhlIFdHIGRvY3VtZW50cyBwZXIgdGhlDQogICAgY2hhcnRlciAoaW4gb3JkZXIgZm9yIHRoYXQg
dG8gaGFwcGVuIHRoZSBkb2N1bWVudCBuZWVkcyB0byBiZSB0aGUgbW9zdA0KICAgIGFwcHJvcHJp
YXRlIG91dCBvZiB0aGUgY29sbGVjdGlvbiBvZiByZWxhdGVkIGRvY3VtZW50cykNCiAgKiBTaG91
bGQgdGhlIGRvY3VtZW50IGNvbnRlbnQgYmUgbWVyZ2VkIHdpdGggb25lIG9yIG1vcmUgb3RoZXIg
ZG9jdW1lbnRzLCBzbw0KICAgIHRoYXQgYSBjb21iaW5lZCBkb2N1bWVudCBjb3VsZCBiZWNvbWUg
YSBXRyBkb2N1bWVudA0KDQpKaW0gJiBUaG9tYXMNCg0KDQpfX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fXw0Kc2ZjIG1haWxpbmcgbGlzdA0Kc2ZjQGlldGYub3Jn
DQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NmYw0K


From nobody Fri Mar 13 05:58:34 2015
Return-Path: <wangh13@mails.tsinghua.edu.cn>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9644F1A008F for <sfc@ietfa.amsl.com>; Fri, 13 Mar 2015 05:55:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 EPt3hLfAH_5M for <sfc@ietfa.amsl.com>; Fri, 13 Mar 2015 05:55:45 -0700 (PDT)
Received: from tsinghua.edu.cn (smtp07.tsinghua.edu.cn [166.111.204.36]) by ietfa.amsl.com (Postfix) with ESMTP id 37EA91A0086 for <sfc@ietf.org>; Fri, 13 Mar 2015 05:55:45 -0700 (PDT)
Received: from Hao (unknown [166.111.68.231]) by app6 (Coremail) with SMTP id D8xvpgCXUzBJ3gJVlp8HAA--.12208S3; Fri, 13 Mar 2015 20:55:39 +0800 (CST)
Date: Fri, 13 Mar 2015 20:54:47 +0800
From: "Hao Wang" <wangh13@mails.tsinghua.edu.cn>
To: "sfc" <sfc@ietf.org>
X-Mailer: NetEase Flash Mail 2.4.0.11
X-Priority: 3 (Normal)
MIME-Version: 1.0
Message-ID: <5502DE15.5040900@mails.tsinghua.edu.cn>
Content-Type: multipart/alternative; boundary="====003__MESSAGE__ID__54yg6f6h6y456345===="
X-CM-TRANSID: D8xvpgCXUzBJ3gJVlp8HAA--.12208S3
X-Coremail-Antispam: 1UD129KBjDUn29KB7ZKAUJUUUUU529EdanIXcx71UUUUU7v73 VFW2AGmfu7bjvjm3AaLaJ3UjIYCTnIWjp_UUUYA7k0a2IF6F4UM7kC6x804xWl14x267AK xVWUJVW8JwAFc2x0x2IEx4CE42xK8VAvwI8IcIk0rVWrJVCq3wAFIxvE14AKwVWUJVWUGw A2ocxC64kIII0Yj41l84ACjcxK6xIIjxv20xvE14v26F1j6w1UM28EF7xvwVC0I7IYx2IY 6xkF7I0E14v26F4j6r4UJwA2z4x0Y4vEx4A2jsIE14v26rxl6s0DM28EF7xvwVC2z280aV CY1x0267AKxVW0oVCq3wAac4AC62xK8xCEY4vEwIxC4wAS0I0E0xvYzxvE52x082IY62kv 0487Mc02F40Eb7x2x7xS6r1j6r4UMc02F40E57IF67AEF4xIwI1l5I8CrVAKz4kIr2xC04 v26r4j6ryUMc02F40E42I26xC2a48xMcIj6xIIjxv20xvE14v26r1j6r18McIj6I8E87Iv 67AKxVWUJVW8JwAm72CE4IkC6x0Yz7v_Jr0_Gr1lF7xvr2IYc2Ij64vIr41lFcxC0VAYjx AxZF0Ew4CEw7xC0wCY02Avz4vE14v_Xr1l42xK82IYc2Ij64vIr41lx2IqxVAqx4xG67AK xVWUGVWUWwC20s026x8GjcxK67AKxVWUGVWUWwC2zVAF1VAY17CE14v26r1j6r15MIIYrx kI7VAKI48JMIIF0xvE2Ix0cI8IcVAFwI0_Jr0_JF4lIxAIcVC0I7IYx2IY6xkF7I0E14v2 6r1j6r4UMIIF0xvE42xK8VAvwI8IcIk0rVWrZr1j6s0DMIIF0xvEx4A2jsIE14v26r1j6r 4UMIIF0xvEx4A2jsIEc7CjxVAFwI0_Jr0_GrUvcSsGvfC2KfnxnUUI43ZEXa7xUUei-UUU UUU==
X-CM-SenderInfo: pzdqwxyrt6zthlovh3pvlqwxlxdovvfxof0/
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/Slgt_LMi-RcGx3qWabHvdbltTBM>
X-Mailman-Approved-At: Fri, 13 Mar 2015 05:58:33 -0700
Subject: Re: [sfc] New Version Notification for draft-wu-pce-traffic-steering-sfc-06.txt
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 13 Mar 2015 12:55:47 -0000

--====003__MESSAGE__ID__54yg6f6h6y456345====
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGk6DQogIEkgaGF2ZSByZWFkIHRoaXMgZHJhZnQgYW5kIHRoaW5rIGl0J3MgdXNlZnVsIGZvciB0
aGlzIFBDRVAgZXh0ZW5zaW9ucywgd2hpY2ggY2FuIGFsbG93IHN0YXRlZnVsIFBDRSB0byBjb21w
dXRlIGFuZCBpbnN0YW50aWF0ZSBTRlAuDQogIFNldmVyYWwgY29tbWV0cyBiZWxvdzoNCiAgMS4g
SG93IGFib3V0IG11bHRpLVNGUCBpbnN0YW50aWF0ZSBtYWludGFpbmFuY2UsIGNhbiB0aGlzIHN0
YXRlZnVsIFBDRSBiZSBoYW5kbGVk77yfDQogIDIuIEFzIGZpZ3VyZSAxIHNob3csIHdoYXQncyB0
aGUgcmVsYXRpb25zaGlwIGJldHdlZW4gU0ZDIGNvbnRyb2wgcGxhbmUgYW5kIHN0YXRlZnVsIFBD
RSBQb2xpY3nvvJ8NCiAgMy4gSXMgdGhlcmUgYW55IHdheSB0byBtYW5hZ2Ugb3IgY29uZmlndWUg
dGhlIHByb2Nlc3Mgb2YgaW5zdGFudGlhdGlvbiBvZiBTRlA/DQoNCkJlc3QgUmVnYXJkcywNCkhh
bw0KDQoyMDE1LTAzLTEzDQoNCg0KSGFv

--====003__MESSAGE__ID__54yg6f6h6y456345====
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0
Zi04IiBodHRwLWVxdWl2PWNvbnRlbnQtdHlwZT4NCjxTVFlMRSB0eXBlPXRleHQvY3NzPgpCTE9D
S1FVT1RFe21hcmdpbi1Ub3A6IDBweDsgbWFyZ2luLUJvdHRvbTogMHB4OyBtYXJnaW4tTGVmdDog
MmVtfQ0KPC9TVFlMRT4NCg0KPE1FVEEgbmFtZT1HRU5FUkFUT1IgY29udGVudD0iTVNIVE1MIDEx
LjAwLjk2MDAuMTc2OTAiPjwhLS0gZmxhc2htYWlsIHN0eWxlIGJlZ2luIC0tPg0KPFNUWUxFIHR5
cGU9dGV4dC9jc3M+CmJvZHkge2JvcmRlci13aWR0aDowO21hcmdpbjowfQppbWcge2JvcmRlcjow
O21hcmdpbjowO3BhZGRpbmc6MH0KPC9TVFlMRT4NCjxCQVNFIHRhcmdldD1fYmxhbms+PCEtLSBm
bGFzaG1haWwgc3R5bGUgZW5kIC0tPjwvSEVBRD4NCjxCT0RZIA0Kc3R5bGU9IkJPUkRFUi1MRUZU
LVdJRFRIOiAwcHg7IEZPTlQtU0laRTogMTAuNXB0OyBGT05ULUZBTUlMWTog5b6u6L2v6ZuF6buR
OyBCT1JERVItUklHSFQtV0lEVEg6IDBweDsgQk9SREVSLUJPVFRPTS1XSURUSDogMHB4OyBDT0xP
UjogIzAwMDAwMDsgTUFSR0lOOiAxMnB4OyBMSU5FLUhFSUdIVDogMS41OyBCT1JERVItVE9QLVdJ
RFRIOiAwcHgiIA0KbWFyZ2lud2lkdGg9IjAiIG1hcmdpbmhlaWdodD0iMCI+PFNUQVRJT05FUlk+
DQo8RElWIHN0eWxlPSJGT05ULUZBTUlMWTogQ291cmllciBOZXciPkhpOjwvRElWPg0KPERJViBz
dHlsZT0iRk9OVC1GQU1JTFk6IENvdXJpZXIgTmV3Ij4mbmJzcDsmbmJzcDtJIGhhdmUgcmVhZCB0
aGlzIGRyYWZ0IGFuZCANCnRoaW5rIGl0J3MgdXNlZnVsIGZvciB0aGlzIFBDRVAgZXh0ZW5zaW9u
cywgd2hpY2ggY2FuIGFsbG93Jm5ic3A7c3RhdGVmdWwgUENFIHRvIA0KY29tcHV0ZSBhbmQgaW5z
dGFudGlhdGUgU0ZQLjwvRElWPg0KPERJViBzdHlsZT0iRk9OVC1GQU1JTFk6IENvdXJpZXIgTmV3
Ij4mbmJzcDsmbmJzcDtTZXZlcmFsIGNvbW1ldHMgYmVsb3c6PC9ESVY+DQo8RElWIHN0eWxlPSJG
T05ULUZBTUlMWTogQ291cmllciBOZXciPiZuYnNwOyZuYnNwOzEuIEhvdyBhYm91dCBtdWx0aS1T
RlAgDQppbnN0YW50aWF0ZSBtYWludGFpbmFuY2UsIGNhbiB0aGlzIHN0YXRlZnVsIFBDRSBiZSBo
YW5kbGVk77yfPC9ESVY+DQo8RElWIHN0eWxlPSJGT05ULUZBTUlMWTogQ291cmllciBOZXciPiZu
YnNwOyZuYnNwOzIuIEFzIGZpZ3VyZSAxIHNob3csIHdoYXQncyANCnRoZSByZWxhdGlvbnNoaXAg
YmV0d2VlbiBTRkMgY29udHJvbCBwbGFuZSBhbmQgc3RhdGVmdWwgUENFIFBvbGljee+8nzwvRElW
Pg0KPERJViBzdHlsZT0iRk9OVC1GQU1JTFk6IENvdXJpZXIgTmV3Ij4mbmJzcDsmbmJzcDszLiBJ
cyB0aGVyZSBhbnkgd2F5IHRvIG1hbmFnZSANCm9yIGNvbmZpZ3VlIHRoZSBwcm9jZXNzIG9mIGlu
c3RhbnRpYXRpb24gb2YgU0ZQPzwvRElWPg0KPERJViBzdHlsZT0iRk9OVC1GQU1JTFk6IENvdXJp
ZXIgTmV3Ij4mbmJzcDs8L0RJVj4NCjxESVYgc3R5bGU9IkZPTlQtRkFNSUxZOiBDb3VyaWVyIE5l
dyI+QmVzdCBSZWdhcmRzLDwvRElWPg0KPERJViBzdHlsZT0iRk9OVC1GQU1JTFk6IENvdXJpZXIg
TmV3Ij5IYW88L0RJVj4NCjxESVYgc3R5bGU9IkZPTlQtRkFNSUxZOiBDb3VyaWVyIE5ldyI+Jm5i
c3A7PC9ESVY+DQo8RElWIHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IEZPTlQtRkFNSUxZOiBWZXJk
YW5hOyBDT0xPUjogI2MwYzBjMCI+DQo8RElWIGFsaWduPWxlZnQ+MjAxNS0wMy0xMzwvRElWPg0K
PEhSIGlkPVNpZ25OYW1lSFIgDQpzdHlsZT0iQk9SREVSLVRPUDogI2MwYzBjMCAxcHggc29saWQ7
IEhFSUdIVDogMXB4OyBCT1JERVItUklHSFQ6IDBweDsgV0lEVEg6IDEyMnB4OyBCT1JERVItQk9U
VE9NOiAwcHg7IEJPUkRFUi1MRUZUOiAwcHgiIA0KYWxpZ249bGVmdD4NCjxTUEFOIGlkPV9GbGFz
aFNpZ25OYW1lPkhhbzwvU1BBTj48L0RJVj48L1NUQVRJT05FUlk+PC9CT0RZPjwvSFRNTD4=

--====003__MESSAGE__ID__54yg6f6h6y456345====--



From nobody Fri Mar 13 06:06:41 2015
Return-Path: <wangh13@mails.tsinghua.edu.cn>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D2D61A1A8B for <sfc@ietfa.amsl.com>; Fri, 13 Mar 2015 06:06:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 Mrfrx38Jq22u for <sfc@ietfa.amsl.com>; Fri, 13 Mar 2015 06:06:38 -0700 (PDT)
Received: from tsinghua.edu.cn (smtp06.tsinghua.edu.cn [166.111.204.35]) by ietfa.amsl.com (Postfix) with ESMTP id 0AC461A1A83 for <sfc@ietf.org>; Fri, 13 Mar 2015 06:06:37 -0700 (PDT)
Received: from Hao (unknown [166.111.68.231]) by app1 (Coremail) with SMTP id CsxvpgCHsEHa4AJVip8JAA--.15901S3; Fri, 13 Mar 2015 21:06:35 +0800 (CST)
Date: Fri, 13 Mar 2015 21:05:44 +0800
From: "Hao Wang" <wangh13@mails.tsinghua.edu.cn>
To: "sfc" <sfc@ietf.org>
X-Mailer: NetEase Flash Mail 2.4.0.11
X-Priority: 3 (Normal)
MIME-Version: 1.0
Message-ID: <5502E0A7.5050906@mails.tsinghua.edu.cn>
Content-Type: multipart/alternative; boundary="====003__MESSAGE__ID__54yg6f6h6y456345===="
X-CM-TRANSID: CsxvpgCHsEHa4AJVip8JAA--.15901S3
X-Coremail-Antispam: 1UD129KBjDUn29KB7ZKAUJUUUUU529EdanIXcx71UUUUU7v73 VFW2AGmfu7bjvjm3AaLaJ3UjIYCTnIWjp_UUUYZ7k0a2IF6F4UM7kC6x804xWl14x267AK xVWUJVW8JwAFc2x0x2IEx4CE42xK8VAvwI8IcIk0rVWrJVCq3wAFIxvE14AKwVWUJVWUGw A2ocxC64kIII0Yj41l84ACjcxK6xIIjxv20xvE14v26w1j6s0DM28EF7xvwVC0I7IYx2IY 6xkF7I0E14v26r4UJVWxJr1l84ACjcxK6I8E87Iv67AKxVW0oVCq3wA2z4x0Y4vEx4A2js IEc7CjxVAFwI0_GcCE3s1lnxkEFVAIw20F6cxK64vIFxWle2I262IYc4CY6c8Ij28IcVAa Y2xG8wAqx4xG67k08I80eVWUJVW8JwAqx4xG6c804VAFz4xC04v7Mc02F40Ew4AK048IF2 xKxVW8JVW5JwAqx4xG6xAIxVCFxsxG0wAv7VC0I7IYx2IY67AKxVWUGVWUXwAv7VC2z280 aVAFwI0_Jr0_Gr1lOx8S6xCaFVCjc4AY6r1j6r4UM4x0Y48IcxkI7VAKI48JM4xvF2IEb7 IF0Fy264kE64k0F24lc2xSY4AK67AK6ry8MxAIw28IcxkI7VAKI48JMI8I3I0E5I8CrVAF wI0_JrI_JrWlx2IqxVCjr7xvwVAFwI0_JrI_JrWlx4CE17CEb7AF67AKxVWUJVWUXwCIc4 0Y0x0EwIxGrwCI42IY6xIIjxv20xvE14v26r1j6r1xMIIF0xvE2Ix0cI8IcVCY1x0267AK xVWUJVW8JwCI42IY6xAIw20EY4v20xvaj40_Wr1j6rW3Jr1lIxAIcVC2z280aVAFwI0_Jr 0_Gr1lIxAIcVC2z280aVCY1x0267AKxVWUJVW8JbIYCTnIWIevJa73UjIFyTuYvj7UU6Zr UUUUU
X-CM-SenderInfo: pzdqwxyrt6zthlovh3pvlqwxlxdovvfxof0/
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/OypNICaawDCLxV25ZR5_cwT0jtU>
Subject: Re: [sfc] New Version Notification for draft-wu-pce-traffic-steering-sfc-06.txt
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 13 Mar 2015 13:06:40 -0000

--====003__MESSAGE__ID__54yg6f6h6y456345====
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGk6DQogIEkgaGF2ZSByZWFkIHRoaXMgZHJhZnQgYW5kIHRoaW5rIGl0J3MgdXNlZnVsIGZvciB0
aGlzIFBDRVAgZXh0ZW5zaW9ucywgd2hpY2ggY2FuIGFsbG93IHN0YXRlZnVsIFBDRSB0byBjb21w
dXRlIGFuZCBpbnN0YW50aWF0ZSBTRlAuDQogIFNldmVyYWwgY29tbWV0cyBiZWxvdzoNCiAgMS4g
SG93IGFib3V0IG11bHRpLVNGUCBpbnN0YW50aWF0ZSBtYWludGFpbmFuY2UsIGNhbiB0aGlzIHN0
YXRlZnVsIFBDRSBiZSBoYW5kbGVk77yfDQogIDIuIEFzIGZpZ3VyZSAxIHNob3csIHdoYXQncyB0
aGUgcmVsYXRpb25zaGlwIGJldHdlZW4gU0ZDIGNvbnRyb2wgcGxhbmUgYW5kIHN0YXRlZnVsIFBD
RSBQb2xpY3nvvJ8NCiAgMy4gSXMgdGhlcmUgYW55IHdheSB0byBtYW5hZ2Ugb3IgY29uZmlndWUg
dGhlIHByb2Nlc3Mgb2YgaW5zdGFudGlhdGlvbiBvZiBTRlA/DQoNCkJlc3QgUmVnYXJkcywNCkhh
bw0KDQoyMDE1LTAzLTEzDQoNCg0KSGFv

--====003__MESSAGE__ID__54yg6f6h6y456345====
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0
Zi04IiBodHRwLWVxdWl2PWNvbnRlbnQtdHlwZT4NCjxTVFlMRSB0eXBlPXRleHQvY3NzPgpCTE9D
S1FVT1RFe21hcmdpbi1Ub3A6IDBweDsgbWFyZ2luLUJvdHRvbTogMHB4OyBtYXJnaW4tTGVmdDog
MmVtfQ0KPC9TVFlMRT4NCg0KPE1FVEEgbmFtZT1HRU5FUkFUT1IgY29udGVudD0iTVNIVE1MIDEx
LjAwLjk2MDAuMTc2OTAiPjwhLS0gZmxhc2htYWlsIHN0eWxlIGJlZ2luIC0tPg0KPFNUWUxFIHR5
cGU9dGV4dC9jc3M+CmJvZHkge2JvcmRlci13aWR0aDowO21hcmdpbjowfQppbWcge2JvcmRlcjow
O21hcmdpbjowO3BhZGRpbmc6MH0KPC9TVFlMRT4NCjxCQVNFIHRhcmdldD1fYmxhbms+PCEtLSBm
bGFzaG1haWwgc3R5bGUgZW5kIC0tPjwvSEVBRD4NCjxCT0RZIA0Kc3R5bGU9IkJPUkRFUi1MRUZU
LVdJRFRIOiAwcHg7IEZPTlQtU0laRTogMTAuNXB0OyBGT05ULUZBTUlMWTog5b6u6L2v6ZuF6buR
OyBCT1JERVItUklHSFQtV0lEVEg6IDBweDsgQk9SREVSLUJPVFRPTS1XSURUSDogMHB4OyBDT0xP
UjogIzAwMDAwMDsgTUFSR0lOOiAxMnB4OyBMSU5FLUhFSUdIVDogMS41OyBCT1JERVItVE9QLVdJ
RFRIOiAwcHgiIA0KbWFyZ2luaGVpZ2h0PSIwIiBtYXJnaW53aWR0aD0iMCI+PFNUQVRJT05FUlk+
DQo8RElWIHN0eWxlPSJGT05ULUZBTUlMWTogQ291cmllciBOZXciPkhpOjwvRElWPg0KPERJViBz
dHlsZT0iRk9OVC1GQU1JTFk6IENvdXJpZXIgTmV3Ij4mbmJzcDsmbmJzcDtJIGhhdmUgcmVhZCB0
aGlzIGRyYWZ0IGFuZCANCnRoaW5rIGl0J3MgdXNlZnVsIGZvciB0aGlzIFBDRVAgZXh0ZW5zaW9u
cywgd2hpY2ggY2FuIGFsbG93Jm5ic3A7c3RhdGVmdWwgUENFIHRvIA0KY29tcHV0ZSBhbmQgaW5z
dGFudGlhdGUgU0ZQLjwvRElWPg0KPERJViBzdHlsZT0iRk9OVC1GQU1JTFk6IENvdXJpZXIgTmV3
Ij4mbmJzcDsmbmJzcDtTZXZlcmFsIGNvbW1ldHMgYmVsb3c6PC9ESVY+DQo8RElWIHN0eWxlPSJG
T05ULUZBTUlMWTogQ291cmllciBOZXciPiZuYnNwOyZuYnNwOzEuIEhvdyBhYm91dCBtdWx0aS1T
RlAgDQppbnN0YW50aWF0ZSBtYWludGFpbmFuY2UsIGNhbiB0aGlzIHN0YXRlZnVsIFBDRSBiZSBo
YW5kbGVk77yfPC9ESVY+DQo8RElWIHN0eWxlPSJGT05ULUZBTUlMWTogQ291cmllciBOZXciPiZu
YnNwOyZuYnNwOzIuIEFzIGZpZ3VyZSAxIHNob3csIHdoYXQncyANCnRoZSByZWxhdGlvbnNoaXAg
YmV0d2VlbiBTRkMgY29udHJvbCBwbGFuZSBhbmQgc3RhdGVmdWwgUENFIFBvbGljee+8nzwvRElW
Pg0KPERJViBzdHlsZT0iRk9OVC1GQU1JTFk6IENvdXJpZXIgTmV3Ij4mbmJzcDsmbmJzcDszLiBJ
cyB0aGVyZSBhbnkgd2F5IHRvIG1hbmFnZSANCm9yIGNvbmZpZ3VlIHRoZSBwcm9jZXNzIG9mIGlu
c3RhbnRpYXRpb24gb2YgU0ZQPzwvRElWPg0KPERJViBzdHlsZT0iRk9OVC1GQU1JTFk6IENvdXJp
ZXIgTmV3Ij4mbmJzcDs8L0RJVj4NCjxESVYgc3R5bGU9IkZPTlQtRkFNSUxZOiBDb3VyaWVyIE5l
dyI+QmVzdCBSZWdhcmRzLDwvRElWPg0KPERJViBzdHlsZT0iRk9OVC1GQU1JTFk6IENvdXJpZXIg
TmV3Ij5IYW88L0RJVj4NCjxESVYgc3R5bGU9IkZPTlQtRkFNSUxZOiBDb3VyaWVyIE5ldyI+Jm5i
c3A7PC9ESVY+DQo8RElWIHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IEZPTlQtRkFNSUxZOiBWZXJk
YW5hOyBDT0xPUjogI2MwYzBjMCI+DQo8RElWIGFsaWduPWxlZnQ+MjAxNS0wMy0xMzwvRElWPg0K
PEhSIGlkPVNpZ25OYW1lSFIgDQpzdHlsZT0iQk9SREVSLVRPUDogI2MwYzBjMCAxcHggc29saWQ7
IEhFSUdIVDogMXB4OyBCT1JERVItUklHSFQ6IDBweDsgV0lEVEg6IDEyMnB4OyBCT1JERVItQk9U
VE9NOiAwcHg7IEJPUkRFUi1MRUZUOiAwcHgiIA0KYWxpZ249bGVmdD4NCjxTUEFOIGlkPV9GbGFz
aFNpZ25OYW1lPkhhbzwvU1BBTj48L0RJVj48L1NUQVRJT05FUlk+PC9CT0RZPjwvSFRNTD4=

--====003__MESSAGE__ID__54yg6f6h6y456345====--



From nobody Fri Mar 13 06:23:45 2015
Return-Path: <RNATALE@mitre.org>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E23A51A1BE4 for <sfc@ietfa.amsl.com>; Fri, 13 Mar 2015 06:23:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 4BmPbrdn6bRo for <sfc@ietfa.amsl.com>; Fri, 13 Mar 2015 06:23:41 -0700 (PDT)
Received: from smtpvbsrv1.mitre.org (smtpvbsrv1.mitre.org [198.49.146.234]) by ietfa.amsl.com (Postfix) with ESMTP id BBE531A1B96 for <sfc@ietf.org>; Fri, 13 Mar 2015 06:23:41 -0700 (PDT)
Received: from smtpvbsrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id F3C3A3AE012; Fri, 13 Mar 2015 09:23:40 -0400 (EDT)
Received: from IMCCAS04.MITRE.ORG (imccas04.mitre.org [129.83.29.81]) by smtpvbsrv1.mitre.org (Postfix) with ESMTP id 9159E332048; Fri, 13 Mar 2015 09:23:40 -0400 (EDT)
Received: from imshyb02.MITRE.ORG (129.83.29.3) by IMCCAS04.MITRE.ORG (129.83.29.81) with Microsoft SMTP Server (TLS) id 14.3.224.2; Fri, 13 Mar 2015 09:23:40 -0400
Received: from imshyb01.MITRE.ORG (129.83.29.2) by imshyb02.MITRE.ORG (129.83.29.3) with Microsoft SMTP Server (TLS) id 15.0.1044.25; Fri, 13 Mar 2015 09:23:40 -0400
Received: from na01-bn1-obe.outbound.protection.outlook.com (10.140.19.249) by imshyb01.MITRE.ORG (129.83.29.2) with Microsoft SMTP Server (TLS) id 15.0.1044.25 via Frontend Transport; Fri, 13 Mar 2015 09:23:39 -0400
Received: from BY1PR09MB0440.namprd09.prod.outlook.com (25.160.109.22) by BY1PR09MB0437.namprd09.prod.outlook.com (25.160.109.19) with Microsoft SMTP Server (TLS) id 15.1.112.19; Fri, 13 Mar 2015 13:23:38 +0000
Received: from BY1PR09MB0440.namprd09.prod.outlook.com ([25.160.109.22]) by BY1PR09MB0440.namprd09.prod.outlook.com ([25.160.109.22]) with mapi id 15.01.0112.000; Fri, 13 Mar 2015 13:23:38 +0000
From: "Natale, Bob" <RNATALE@mitre.org>
To: Linda Dunbar <linda.dunbar@huawei.com>, Thomas Narten <narten@us.ibm.com>
Thread-Topic: [sfc] Call for Dallas SFC Agenda Topics
Thread-Index: AQHQVRxSzjAjQoBjrEOiNH0pLo0i2J0ZQpewgAEx3FA=
Date: Fri, 13 Mar 2015 13:23:37 +0000
Message-ID: <BY1PR09MB0440257FF0549A9E0902E312A8070@BY1PR09MB0440.namprd09.prod.outlook.com>
References: <m3lhjfp69j.wl-narten@us.ibm.com> <4A95BA014132FF49AE685FAB4B9F17F645EEDEEE@dfweml701-chm>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F645EEDEEE@dfweml701-chm>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.80.55.88]
authentication-results: huawei.com; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BY1PR09MB0437;
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10009020)(6009001)(13464003)(377454003)(22804002)(76104003)(74316001)(87936001)(2656002)(54356999)(50986999)(76176999)(62966003)(77156002)(76576001)(99286002)(86362001)(106116001)(46102003)(92566002)(102836002)(2900100001)(15975445007)(2950100001)(19580395003)(19580405001)(66066001)(33656002)(122556002)(40100003)(7059030); DIR:OUT; SFP:1101; SCL:1; SRVR:BY1PR09MB0437; H:BY1PR09MB0440.namprd09.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
x-microsoft-antispam-prvs: <BY1PR09MB0437CF342F4C1EF84A1ECA17A8070@BY1PR09MB0437.namprd09.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5002009)(5005006); SRVR:BY1PR09MB0437; BCL:0; PCL:0; RULEID:;  SRVR:BY1PR09MB0437; 
x-forefront-prvs: 05143A8241
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Mar 2015 13:23:37.7774 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: c620dc48-1d50-4952-8b39-df4d54d74d82
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY1PR09MB0437
X-OriginatorOrg: mitre.org
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/jjXBrJckWYRfk9GY9LVcLsNdc0Y>
Cc: "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] Call for Dallas SFC Agenda Topics
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 13 Mar 2015 13:23:44 -0000

PiBJTUhPLCB0aGUgU0ZDIGNvbnRyb2wgcGxhbmUgc2hvdWxkIGJlIGRpc2N1c3NlZCBieSB0aGUg
V0cgYmVmb3JlIGp1bXBpbmcgaW50byBvbmUgc3BlY2lmaWMgYXBwcm9hY2guIA0KDQpTdHJvbmcg
KzEgZnJvbSBtZSBvbiB0aGF0IHBvaW50IC4uLiB3aGljaCBJIGZpbmQgYW5hbG9nb3VzIHRvIEpv
aG4gU3RyYXNzbmVyJ3MgYXR0ZW1wdHMgdG8gZW5zdXJlIHRoYXQgd2UgdW5kZXJzdGFuZCB0aGUg
Z2VuZXJhbCBmb3JtIG9mIGluLXNjb3BlIHBvbGljaWVzLCBpbnRlcmZhY2VzLCBkYXRhIG1vZGVs
cywgZXRjLiwgYmVmb3JlIGNyZWF0aW5nIHNwZWNpZmljIGluc3RhbmNlcyBvZiB0aGVtIC4uLiBz
dWNoIHVuZGVyc3RhbmRpbmcgY2FuIGJlIGRvbmUgYXQgYW4gb3V0bGluZSBsZXZlbCBpbiBtYW55
IGNhc2VzLCBidXQgcmVhbGx5IHNob3VsZCBiZSBkb25lIHVwLWZyb250IChJTUhPKS4NCg0KPiBD
YW4gd2UgaGF2ZSBhIHNsb3QgdG8gZGlzY3VzcyB0aGUgU0ZDIGNvbnRyb2wgcGxhbmUgYXQgdGhp
cyBTRkMgbWVldGluZz8NCg0KSSBwcmVzdW1lIHdlJ3JlIG5vdCBwcm9wb3NpbmcgYSBkaXN0aW5j
dCBjb250cm9sIHBsYW5lIGZvciBTRkMgYW5kIHRoYXQgdGhlIHdvcmRpbmcgdGhlcmUgc2hvdWxk
IGJlIHNvbWV0aGluZyBsaWtlOiAiLi4uIGEgc2xvdCB0byBkaXNjdXNzIHRoZSBpbnRlcmZhY2Uo
cykgYmV0d2VlbiBTRkMvU0ZQICBhbmQgdGhlIGNvbnRyb2wgcGxhbmUuIg0KDQpSZWdhcmRsZXNz
IG9mIG15IHN1Z2dlc3Rpb25zLCBJIGhvcGUgdGhlIGdyb3VwIGhhcyBhIGhpZ2hseSBwcm9kdWN0
aXZlIHNldCBvZiBtZWV0aW5ncyBpbiBEYWxsYXMgKGFuZCByZWdyZXRzIHRoYXQgSSBjYW5ub3Qg
bWFrZSB0aGUgdHJpcCkgLi4uIGFzIEkgc2VlIGl0LCBTRkMgaXMgdGhlIGxpbmNocGluIGJldHdl
ZW4gTkZWIGFuZCBTRE4gdG8gYWNoaWV2ZSB0aGUgYnVzaW5lc3MvbWlzc2lvbiBiZW5lZml0cyBv
ZiBOZXR3b3JrIFNlcnZpY2VzIFZpcnR1YWxpemF0aW9uIGdvaW5nIGZvcndhcmQuDQoNCkF2YW50
aSwNCkJvYk4NCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IHNmYyBbbWFpbHRv
OnNmYy1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgTGluZGEgRHVuYmFyDQpTZW50OiBU
aHVyc2RheSwgTWFyY2ggMTIsIDIwMTUgMzoyOSBQTQ0KVG86IFRob21hcyBOYXJ0ZW47IHNmY0Bp
ZXRmLm9yZw0KU3ViamVjdDogUmU6IFtzZmNdIENhbGwgZm9yIERhbGxhcyBTRkMgQWdlbmRhIFRv
cGljcw0KDQpUaG9tYXMgYW5kIEppbSwgDQoNClRoZXJlIGFyZSBzZXZlcmFsIGRyYWZ0cyBvbiB0
aGUgU0ZDIENvbnRyb2wgUGxhbmU6DQoNCi0gIGRyYWZ0LXd3LXNmYy1jb250cm9sLXBsYW5lLTA0
DQotICBkcmFmdC1rYW5nLXNmYy1mYWlsb3Zlci0wMSAgDQotICBkcmFmdC1kdW5iYXItc2ZjLXBh
dGgtY29udHJvbC0wMQ0KLSAgZHJhZnQta3VtYXItc2ZjLW9mZmxvYWRzLTAwDQoNClRoZXJlIGFy
ZSBtYW55IHdheXMgdG8gY29udHJvbCB0aGUgc2VydmljZSBmdW5jdGlvbiBwYXRoIGFuZCBob3cg
dGhlIFNGQyBwYXRoIGJlaW5nIGFsdGVyZWQgZHluYW1pY2FsbHkuIA0KZHJhZnQta3VtYXItc2Zj
LW9mZmxvYWRzLTAwICAgZGVzY3JpYmVzIG9uZSB3YXkgb2YgU0ZDIHBhdGggYmVpbmcgYWx0ZXJl
ZCAoaS5lLiBzb21lIFNGIGJlaW5nIHJlbW92ZWQgZnJvbSB0aGUgcGF0aCkgYXMgdGhlIHJlc3Vs
dCBvZiBvdGhlciBzZXJ2aWNlIGZ1bmN0aW9ucycgZXhlY3V0aW9uIHN0YXR1cy4gDQpUaGUgU0ZD
IHBhdGggY2FuIGFsc28gYmUgZHluYW1pY2FsbHkgY2hhbmdlZCBieSBOZXR3b3JrIENvbnRyb2xs
ZXIgdHJpZ2dlcmVkIGJ5IG90aGVyIGV2ZW50cy4gDQoNCklNSE8sIHRoZSBTRkMgY29udHJvbCBw
bGFuZSBzaG91bGQgYmUgZGlzY3Vzc2VkIGJ5IHRoZSBXRyBiZWZvcmUganVtcGluZyBpbnRvIG9u
ZSBzcGVjaWZpYyBhcHByb2FjaC4gDQoNCkNhbiB3ZSBoYXZlIGEgc2xvdCB0byBkaXNjdXNzIHRo
ZSBTRkMgY29udHJvbCBwbGFuZSBhdCB0aGlzIFNGQyBtZWV0aW5nPyANCg0KDQpMaW5kYQ0KLS0t
LS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IHNmYyBbbWFpbHRvOnNmYy1ib3VuY2VzQGll
dGYub3JnXSBPbiBCZWhhbGYgT2YgVGhvbWFzIE5hcnRlbg0KU2VudDogTW9uZGF5LCBNYXJjaCAw
MiwgMjAxNSAxOjA4IFBNDQpUbzogc2ZjQGlldGYub3JnDQpTdWJqZWN0OiBbc2ZjXSBDYWxsIGZv
ciBEYWxsYXMgU0ZDIEFnZW5kYSBUb3BpY3MNCg0KR3JlZXRpbmdzIFdHOg0KDQpPdXIgbWVldGlu
ZyBhdCB0aGUgdXBjb21pbmcgRGFsbGFzIHZlbnVlIGlzIGZhc3QgYXBwcm9hY2hpbmcuICBBcyBh
bHdheXMsIHRoZSBnb2FsIG9mIHRoZSBtZWV0aW5nIHdpbGwgYmUgdG8gbWFrZSB0aGUgYmVzdCB1
c2Ugb2YgbGltaXRlZCBmYWNlLXRvLWZhY2UgdGltZS4NCg0KQXMgd2UgYnVpbGQgdGhlIG1lZXRp
bmcgYWdlbmRhIHdlIHdlbGNvbWUgcmVxdWVzdHMgZm9yIGFnZW5kYSB0aW1lLiBBcyBhbHdheXMs
IHRoZSBnb2FsIG9mIGEgbWVldGluZyBzbG90IGlzIHRvIGJlc3QgZnVydGhlciB0aGUgd29yayBv
ZiB0aGUgV0csIGFuZCB0aGF0IGdlbmVyYWxseSBtZWFucyBmb2N1c3Npbmcgb24ga2V5IGNoYXJ0
ZXIgZGVsaXZlcmFibGVzIGFuZCB0b3BpY3Mgd2l0aCBpbXBvcnRhbnQgb3BlbiBpc3N1ZXMgdG8g
cmVzb2x2ZS4gSW4gdGhlIGNhc2Ugb2YgaW5kaXZpZHVhbCBJRHMsIHRoZSBnb2FsIGlzbu6VmiBu
ZWNlc3NhcmlseSB0byBwcmVzZW50IHdoYXQgaXMgaW4gdGhlIGRyYWZ0IGJ1dCByYXRoZXIgdG8g
aGVscCB0aGUgV0cgZGVjaWRlIHdoYXQgdG8gZG8gd2l0aCB0aGUgSUQuIFdpdGggdGhhdCBpbiBt
aW5kLCB3aGVuIG1ha2luZyBhbiBhZ2VuZGEgcmVxdWVzdCBwbGVhc2UgY29uc2lkZXIgd2hhdCB5
b3UgdGhpbmsgdGhlIFdHIHNob3VsZCBkbyB3aXRoIGl0cyBjb250ZW50LiBGb3INCmV4YW1wbGU6
DQoNCiAgKiBEb2VzIHRoZSBkb2N1bWVudCBoYXZlIHVzZWZ1bCBjb250ZW50IHRoYXQgc2hvdWxk
IGJlIG1vdmVkIGludG8gYW5vdGhlciBXRw0KICAgIGRvY3VtZW50IG9yIHByb2dyZXNzIG9uIGl0
7pWZIG93biBtZXJpdA0KICAqIERvZXMgdGhlIGNvbnRlbnQgaGF2ZSBhIGdvb2QgYmFzaXMgZm9y
IG9uZSBvZiB0aGUgV0cgZG9jdW1lbnRzIHBlciB0aGUNCiAgICBjaGFydGVyIChpbiBvcmRlciBm
b3IgdGhhdCB0byBoYXBwZW4gdGhlIGRvY3VtZW50IG5lZWRzIHRvIGJlIHRoZSBtb3N0DQogICAg
YXBwcm9wcmlhdGUgb3V0IG9mIHRoZSBjb2xsZWN0aW9uIG9mIHJlbGF0ZWQgZG9jdW1lbnRzKQ0K
ICAqIFNob3VsZCB0aGUgZG9jdW1lbnQgY29udGVudCBiZSBtZXJnZWQgd2l0aCBvbmUgb3IgbW9y
ZSBvdGhlciBkb2N1bWVudHMsIHNvDQogICAgdGhhdCBhIGNvbWJpbmVkIGRvY3VtZW50IGNvdWxk
IGJlY29tZSBhIFdHIGRvY3VtZW50DQoNCkppbSAmIFRob21hcw0KDQoNCl9fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpzZmMgbWFpbGluZyBsaXN0DQpzZmNA
aWV0Zi5vcmcNCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vc2ZjDQpfX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0Kc2ZjIG1haWxpbmcg
bGlzdA0Kc2ZjQGlldGYub3JnDQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZv
L3NmYw0K


From nobody Sun Mar 15 19:37:12 2015
Return-Path: <bill.wu@huawei.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F19CD1A1DBD; Sun, 15 Mar 2015 19:37:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 7qgSG9hYyJUy; Sun, 15 Mar 2015 19:37:08 -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 3BE651A1C00; Sun, 15 Mar 2015 19:37:07 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BTR21203; Mon, 16 Mar 2015 02:37:05 +0000 (GMT)
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 16 Mar 2015 02:37:04 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.244]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.03.0158.001; Mon, 16 Mar 2015 10:36:57 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Hao Wang <wangh13@mails.tsinghua.edu.cn>, sfc <sfc@ietf.org>, "pce@ietf.org" <pce@ietf.org>
Thread-Topic: [sfc] New Version Notification for draft-wu-pce-traffic-steering-sfc-06.txt
Thread-Index: AQHQXY5qmW+qqfnN4E6JrNshfZYx8p0eY0yQ
Date: Mon, 16 Mar 2015 02:36:56 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA846F54E4@nkgeml501-mbs.china.huawei.com>
References: <5502E0A7.5050906@mails.tsinghua.edu.cn>
In-Reply-To: <5502E0A7.5050906@mails.tsinghua.edu.cn>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.138.41.180]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA846F54E4nkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/AOTMfLLN7PLkSEKsujcO4B8HlEQ>
Subject: Re: [sfc] New Version Notification for draft-wu-pce-traffic-steering-sfc-06.txt
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 16 Mar 2015 02:37:10 -0000

--_000_B8F9A780D330094D99AF023C5877DABA846F54E4nkgeml501mbschi_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGksIEhhbzoNClRoYW5rcyBmb3IgeW91ciBpbnRlcmVzdHMgYW5kIHZhbHVhYmxlIGNtbWVudHMu
IFNlZSBteSByZXBseSBpbmxpbmUgYmVsb3cuDQotUWluDQrlj5Hku7bkuro6IHNmYyBbbWFpbHRv
OnNmYy1ib3VuY2VzQGlldGYub3JnXSDku6PooaggSGFvIFdhbmcNCuWPkemAgeaXtumXtDogMjAx
NeW5tDPmnIgxM+aXpSAyMTowNg0K5pS25Lu25Lq6OiBzZmMNCuS4u+mimDogUmU6IFtzZmNdIE5l
dyBWZXJzaW9uIE5vdGlmaWNhdGlvbiBmb3IgZHJhZnQtd3UtcGNlLXRyYWZmaWMtc3RlZXJpbmct
c2ZjLTA2LnR4dA0KSGk6DQogIEkgaGF2ZSByZWFkIHRoaXMgZHJhZnQgYW5kIHRoaW5rIGl0J3Mg
dXNlZnVsIGZvciB0aGlzIFBDRVAgZXh0ZW5zaW9ucywgd2hpY2ggY2FuIGFsbG93IHN0YXRlZnVs
IFBDRSB0byBjb21wdXRlIGFuZCBpbnN0YW50aWF0ZSBTRlAuDQogIFNldmVyYWwgY29tbWV0cyBi
ZWxvdzoNCg0KMS4gIEhvdyBhYm91dCBtdWx0aS1TRlAgaW5zdGFudGlhdGUgbWFpbnRhaW5hbmNl
LCBjYW4gdGhpcyBzdGF0ZWZ1bCBQQ0UgYmUgaGFuZGxlZO+8nw0KW1Fpbl06IEdvb2QgcXVlc3Rp
b24sIHRoZSBzaW1wbHkgc29sdXRpb24gaXMgdG8gY2FycnkgbXVsdGlwbGUgU0ZQIElkZW50aWZp
ZXIgVExWcyB0byBpbmRpY2F0ZSBtdWx0aS1TRlAgaW5zdGFudGlhdGUgZnJvbSBzdGF0ZWZ1bCBQ
Q0Ugc2VydmVyLg0KSWYgd2UgbG9vayBmb3IgbW9yZSBnZW5lcmljIHdheSBmb3IgbXVsdGktU0ZQ
IGhhbmRsaW5nLCB3ZSBtYXkgcmVmZXJlbmNlIGRyYWZ0LWRob2R5LXBjZS1hc3NvY2lhdGlvbi1h
dHRyLTAxDQpodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaWQvZHJhZnQtZGhvZHktcGNlLWFzc29jaWF0
aW9uLWF0dHItMDEudHh0DQphbmQgZGVmaW5lIGdlbmVyaWMgZ3JvdXAgaWQgdG8gZG8gdGhpcy4N
Cg0KMi4gIEFzIGZpZ3VyZSAxIHNob3csIHdoYXQncyB0aGUgcmVsYXRpb25zaGlwIGJldHdlZW4g
U0ZDIGNvbnRyb2wgcGxhbmUgYW5kIHN0YXRlZnVsIFBDRSBQb2xpY3nvvJ8NCltRaW5dOiBTRkMg
Y29udHJvbCBwbGFuZSBpcyBtb3JlIGFib3V0IHBvbGljeSBkcml2ZW4sIEluIGVhY2ggaW50ZXJh
Y3Rpb24gYmV0d2VlbiBTRkMgY29udHJvbCBwbGFuZSBhbmQgU0ZDIGRhdGEgcGxhbmUsDQpQb2xp
Y3kgd2lsbCBiZSBpbnN0YWxsZWQgb3IgcG9wdWxhdGVkIGF0IGRhdGEgcGxhbmUgbm9kZS4gRm9y
IGV4YW1wbGUsIGVhY2ggaW50ZXJhY3Rpb24gYmV0d2VlbiBQQ0Ugc2VydmVyIGFuZCBTRkMgQ2xh
c3NpZmllcg0KV2lsbCBsZWFkIHRvIGNsYXNzaWZpY2F0aW9uIHJ1bGVzIGJlaW5nIGluc3RhbGxl
ZCB3aGljaCBlbmFibGUgU0ZQIHNlbGVjdGlvbiBmb3IgdGhlIHRyYWZmaWMsIGVhY2ggaW50ZXJh
Y3Rpb24gYmV0d2VlbiBTRkMgY29udHJvbGxlciBhbmQgU0ZDIGRhdGEgcGxhbmUgbm9kZShlLmcu
LCBTRkYpIHdpbGwgbGVhZCB0byBmb3J3YXJkaW5nIHBvbGljeSBiZWluZyBwb3B1bGF0ZWQgYXQg
dGhlIGNvcnJlc3BvbmRpbmcgbm9kZXMuDQoNCjMuICBJcyB0aGVyZSBhbnkgd2F5IHRvIG1hbmFn
ZSBvciBjb25maWd1ZSB0aGUgcHJvY2VzcyBvZiBpbnN0YW50aWF0aW9uIG9mIFNGUD8NCltRaW5d
OiBUaGlzIGlzIHdoYXQgd2UgdHJ5IHRvIHNvbHZlIGluIHRoaXMgZHJhZnQgYW5kIHByb3Bvc2Vz
IGEgd2F5IHRvIG1hbmFnZSBvciBjb25maWd1cmUgb2YgU0ZQIGluc3RhbnRpYXRpb24gcHJvY2Vz
cy4NClRoZSBiYXNpYyBpZGVhIGlzIHRvIHVzZSBQQ0UgaW5pdGlhdGVkIG1lY2hhbmlzbSBwcm9w
b3NlZCBpbiBkcmFmdC1pZXRmLXBjZS1wY2UtaW5pdGlhdGVkLWxzcC0wMiBhbmQgY29tYmluZSB3
aXRoIFNGUCBJZGVudGlmaWVyIFRMViBwcm9wb3NlZCBpbiB0aGlzIGRyYWZ0IHRvIHByb3ZpZGUg
U0ZQIGluc3RhbnRpYXRpb24gbWFuYWdlbWVudC4NCg0KQmVzdCBSZWdhcmRzLA0KSGFvDQoNCjIw
MTUtMDMtMTMNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpIYW8NCg==

--_000_B8F9A780D330094D99AF023C5877DABA846F54E4nkgeml501mbschi_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTIgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPGJhc2Ug
dGFyZ2V0PSJfYmxhbmsiPjwhLS1baWYgIW1zb10+PHN0eWxlPnZcOioge2JlaGF2aW9yOnVybCgj
ZGVmYXVsdCNWTUwpO30NCm9cOioge2JlaGF2aW9yOnVybCgjZGVmYXVsdCNWTUwpO30NCndcOiog
e2JlaGF2aW9yOnVybCgjZGVmYXVsdCNWTUwpO30NCi5zaGFwZSB7YmVoYXZpb3I6dXJsKCNkZWZh
dWx0I1ZNTCk7fQ0KPC9zdHlsZT48IVtlbmRpZl0tLT48c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZp
bml0aW9ucyAqLw0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTrlrovkvZM7DQoJcGFub3NlLTE6
MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJDYW1icmlh
IE1hdGgiOw0KCXBhbm9zZS0xOjIgNCA1IDMgNSA0IDYgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtm
b250LWZhbWlseTpDYWxpYnJpOw0KCXBhbm9zZS0xOjIgMTUgNSAyIDIgMiA0IDMgMiA0O30NCkBm
b250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IlxA5a6L5L2TIjsNCglwYW5vc2UtMToyIDEgNiAwIDMg
MSAxIDEgMSAxO30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6VmVyZGFuYTsNCglwYW5vc2Ut
MToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OuW+rui9
r+mbhem7kTsNCglwYW5vc2UtMToyIDExIDUgMyAyIDIgNCAyIDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OiJcQOW+rui9r+mbhem7kSI7DQoJcGFub3NlLTE6MiAxMSA1IDMgMiAyIDQg
MiAyIDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3Jt
YWwsIGRpdi5Nc29Ob3JtYWwNCgl7bXNvLW1hcmdpbi10b3AtYWx0OmF1dG87DQoJbWFyZ2luLXJp
Z2h0OjBjbTsNCgltc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzsNCgltYXJnaW4tbGVmdDowY207
DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseTrlrovkvZM7DQoJbXNvLWJlbGlldmUt
bm9ybWFsLWxlZnQ6eWVzO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxl
LXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9
DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9y
aXR5Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnAu
TXNvTGlzdFBhcmFncmFwaCwgbGkuTXNvTGlzdFBhcmFncmFwaCwgZGl2Lk1zb0xpc3RQYXJhZ3Jh
cGgNCgl7bXNvLXN0eWxlLXByaW9yaXR5OjM0Ow0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRvOw0K
CW1hcmdpbi1yaWdodDowY207DQoJbXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFyZ2lu
LWxlZnQ6MGNtOw0KCXRleHQtaW5kZW50OjIxLjBwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZv
bnQtZmFtaWx5OuWui+S9kzt9DQpzcGFuLkVtYWlsU3R5bGUxNw0KCXttc28tc3R5bGUtdHlwZTpw
ZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiOw0KCWNv
bG9yOiMxRjQ5N0Q7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9u
bHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo2MTIu
MHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA5MC4wcHQgNzIuMHB0IDkwLjBwdDt9DQpkaXYu
V29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi8qIExpc3QgRGVmaW5pdGlvbnMg
Ki8NCkBsaXN0IGwwDQoJe21zby1saXN0LWlkOjExOTM4MzU5NTk7DQoJbXNvLWxpc3QtdHlwZTpo
eWJyaWQ7DQoJbXNvLWxpc3QtdGVtcGxhdGUtaWRzOi0xNTAxNjQ1NjA2IDEwNzk2NTczNjIgNjc2
OTg3MTMgNjc2OTg3MTUgNjc2OTg3MDMgNjc2OTg3MTMgNjc2OTg3MTUgNjc2OTg3MDMgNjc2OTg3
MTMgNjc2OTg3MTU7fQ0KQGxpc3QgbDA6bGV2ZWwxDQoJe21zby1sZXZlbC10YWItc3RvcDpub25l
Ow0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgltYXJnaW4tbGVmdDozMC4wcHQ7
DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDt9DQotLT48L3N0eWxlPjwhW2lmIG1zbyA5XT48c3R5bGU+
cC5Nc29Ob3JtYWwNCgl7bWFyZ2luLWxlZnQ6OS4wcHQ7fQ0KPC9zdHlsZT48IVtlbmRpZl0+PCEt
LVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlk
bWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+
DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0
YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxi
b2R5IGxhbmc9IlpILUNOIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIiBzdHlsZT0ibWFyZ2lu
LWxlZnQ6OS4wcHQ7bWFyZ2luLXRvcDo5LjBwdDttYXJnaW4tcmlnaHQ6OS4wcHQ7bWFyZ2luLWJv
dHRvbTo5LjBwdCI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0
OTdEIj5IaSwgSGFvOjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+
VGhhbmtzIGZvciB5b3VyIGludGVyZXN0cyBhbmQgdmFsdWFibGUgY21tZW50cy4gU2VlIG15IHJl
cGx5IGlubGluZSBiZWxvdy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5
N0QiPi1RaW48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVy
Om5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGNtIDBj
bSAwY20iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbjowY207bWFyZ2luLWJv
dHRvbTouMDAwMXB0Ij48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdCI+5Y+R5Lu25Lq6
PHNwYW4gbGFuZz0iRU4tVVMiPjo8L3NwYW4+PC9zcGFuPjwvYj48c3BhbiBsYW5nPSJFTi1VUyIg
c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQiPiBzZmMgW21haWx0bzpzZmMtYm91bmNlc0BpZXRmLm9y
Z10NCjwvc3Bhbj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdCI+5Luj6KGoIDwvc3Bh
bj48L2I+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0Ij5IYW8gV2Fu
Zzxicj4NCjwvc3Bhbj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdCI+5Y+R6YCB5pe2
6Ze0PHNwYW4gbGFuZz0iRU4tVVMiPjo8L3NwYW4+PC9zcGFuPjwvYj48c3BhbiBsYW5nPSJFTi1V
UyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQiPiAyMDE1PC9zcGFuPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTAuMHB0Ij7lubQ8c3BhbiBsYW5nPSJFTi1VUyI+Mzwvc3Bhbj7mnIg8c3BhbiBsYW5n
PSJFTi1VUyI+MTM8L3NwYW4+5pelPHNwYW4gbGFuZz0iRU4tVVMiPiAyMTowNjxicj4NCjwvc3Bh
bj48Yj7mlLbku7bkuro8c3BhbiBsYW5nPSJFTi1VUyI+Ojwvc3Bhbj48L2I+PHNwYW4gbGFuZz0i
RU4tVVMiPiBzZmM8YnI+DQo8L3NwYW4+PGI+5Li76aKYPHNwYW4gbGFuZz0iRU4tVVMiPjo8L3Nw
YW4+PC9iPjxzcGFuIGxhbmc9IkVOLVVTIj4gUmU6IFtzZmNdIE5ldyBWZXJzaW9uIE5vdGlmaWNh
dGlvbiBmb3IgZHJhZnQtd3UtcGNlLXRyYWZmaWMtc3RlZXJpbmctc2ZjLTA2LnR4dDxvOnA+PC9v
OnA+PC9zcGFuPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSJtYXJnaW46MGNtO21hcmdpbi1ib3R0b206LjAwMDFwdCI+PHNwYW4g
bGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nv
dXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5IaTo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luOjBjbTttYXJn
aW4tYm90dG9tOi4wMDAxcHQiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEw
LjVwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+Jm5i
c3A7Jm5ic3A7SSBoYXZlIHJlYWQgdGhpcyBkcmFmdCBhbmQgdGhpbmsgaXQncyB1c2VmdWwgZm9y
IHRoaXMgUENFUCBleHRlbnNpb25zLCB3aGljaCBjYW4gYWxsb3cmbmJzcDtzdGF0ZWZ1bCBQQ0Ug
dG8gY29tcHV0ZQ0KIGFuZCBpbnN0YW50aWF0ZSBTRlAuPG86cD48L286cD48L3NwYW4+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbjowY207bWFy
Z2luLWJvdHRvbTouMDAwMXB0Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZTox
MC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPiZu
YnNwOyZuYnNwO1NldmVyYWwgY29tbWV0cyBiZWxvdzo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTGlzdFBhcmFncmFwaCIgc3R5bGU9Im1zby1tYXJn
aW4tdG9wLWFsdDo5LjBwdDttYXJnaW4tcmlnaHQ6OS4wcHQ7bWFyZ2luLWJvdHRvbTo5LjBwdDtt
YXJnaW4tbGVmdDozMC4wcHQ7dGV4dC1pbmRlbnQ6LTE4LjBwdDttc28tbGlzdDpsMCBsZXZlbDEg
bGZvMSI+DQo8IVtpZiAhc3VwcG9ydExpc3RzXT48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZv
bnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6
YmxhY2siPjxzcGFuIHN0eWxlPSJtc28tbGlzdDpJZ25vcmUiPjEuPHNwYW4gc3R5bGU9ImZvbnQ6
Ny4wcHQgJnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij4mbmJzcDsNCjwvc3Bhbj48L3NwYW4+
PC9zcGFuPjwhW2VuZGlmXT48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPkhvdyBh
Ym91dCBtdWx0aS1TRlAgaW5zdGFudGlhdGUgbWFpbnRhaW5hbmNlLCBjYW4gdGhpcyBzdGF0ZWZ1
bCBQQ0UgYmUgaGFuZGxlZDwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250
LWZhbWlseTomcXVvdDvlvq7ova/pm4Xpu5EmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztj
b2xvcjpibGFjayI+77yfPC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXpl
OjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1t
YXJnaW4tdG9wLWFsdDo5LjBwdDttYXJnaW4tcmlnaHQ6MTguMHB0O21hcmdpbi1ib3R0b206OS4w
cHQ7bWFyZ2luLWxlZnQ6OS4wcHQiPg0KPHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNp
emU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOiMxRjQ5
N0QiPltRaW5dOiBHb29kIHF1ZXN0aW9uLCB0aGUgc2ltcGx5IHNvbHV0aW9uIGlzIHRvIGNhcnJ5
IG11bHRpcGxlIFNGUCBJZGVudGlmaWVyIFRMVnMgdG8gaW5kaWNhdGUgbXVsdGktU0ZQIGluc3Rh
bnRpYXRlIGZyb20gc3RhdGVmdWwgUENFIHNlcnZlci48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OjkuMHB0O21hcmdp
bi1yaWdodDoxOC4wcHQ7bWFyZ2luLWJvdHRvbTo5LjBwdDttYXJnaW4tbGVmdDo5LjBwdCI+DQo8
c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6IzFGNDk3RCI+SWYgd2UgbG9vayBmb3IgbW9yZSBn
ZW5lcmljIHdheSBmb3IgbXVsdGktU0ZQIGhhbmRsaW5nLCB3ZSBtYXkgcmVmZXJlbmNlIGRyYWZ0
LWRob2R5LXBjZS1hc3NvY2lhdGlvbi1hdHRyLTAxPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDo5LjBwdDttYXJnaW4t
cmlnaHQ6MTguMHB0O21hcmdpbi1ib3R0b206OS4wcHQ7bWFyZ2luLWxlZnQ6OS4wcHQiPg0KPHNw
YW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxhIGhyZWY9Imh0dHA6Ly90b29scy5p
ZXRmLm9yZy9pZC9kcmFmdC1kaG9keS1wY2UtYXNzb2NpYXRpb24tYXR0ci0wMS50eHQiPmh0dHA6
Ly90b29scy5pZXRmLm9yZy9pZC9kcmFmdC1kaG9keS1wY2UtYXNzb2NpYXRpb24tYXR0ci0wMS50
eHQ8L2E+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1zby1tYXJnaW4tdG9wLWFsdDo5LjBwdDttYXJnaW4tcmlnaHQ6MTguMHB0O21hcmdpbi1ib3R0
b206OS4wcHQ7bWFyZ2luLWxlZnQ6OS4wcHQiPg0KPHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJm
b250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9y
OiMxRjQ5N0QiPmFuZCBkZWZpbmUgZ2VuZXJpYyBncm91cCBpZCB0byBkbyB0aGlzLjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29MaXN0UGFyYWdyYXBo
IiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OjkuMHB0O21hcmdpbi1yaWdodDo5LjBwdDttYXJn
aW4tYm90dG9tOjkuMHB0O21hcmdpbi1sZWZ0OjMwLjBwdDt0ZXh0LWluZGVudDotMTguMHB0O21z
by1saXN0OmwwIGxldmVsMSBsZm8xIj4NCjwhW2lmICFzdXBwb3J0TGlzdHNdPjxzcGFuIGxhbmc9
IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVy
IE5ldyZxdW90Oztjb2xvcjpibGFjayI+PHNwYW4gc3R5bGU9Im1zby1saXN0Oklnbm9yZSI+Mi48
c3BhbiBzdHlsZT0iZm9udDo3LjBwdCAmcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDsiPiZuYnNw
Ow0KPC9zcGFuPjwvc3Bhbj48L3NwYW4+PCFbZW5kaWZdPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHls
ZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztj
b2xvcjpibGFjayI+QXMgZmlndXJlIDEgc2hvdywgd2hhdCdzIHRoZSByZWxhdGlvbnNoaXAgYmV0
d2VlbiBTRkMgY29udHJvbCBwbGFuZSBhbmQgc3RhdGVmdWwgUENFIFBvbGljeTwvc3Bhbj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDvlvq7ova/pm4Xpu5Em
cXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjpibGFjayI+77yfPC9zcGFuPjxzcGFu
IGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtD
b3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDo5LjBwdDttYXJnaW4t
cmlnaHQ6MTguMHB0O21hcmdpbi1ib3R0b206OS4wcHQ7bWFyZ2luLWxlZnQ6OS4wcHQiPg0KPHNw
YW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPltRaW5dOiBTRkMgY29udHJvbCBwbGFu
ZSBpcyBtb3JlIGFib3V0IHBvbGljeSBkcml2ZW4sIEluIGVhY2ggaW50ZXJhY3Rpb24gYmV0d2Vl
biBTRkMgY29udHJvbCBwbGFuZSBhbmQgU0ZDIGRhdGEgcGxhbmUsPG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDo5LjBw
dDttYXJnaW4tcmlnaHQ6MTguMHB0O21hcmdpbi1ib3R0b206OS4wcHQ7bWFyZ2luLWxlZnQ6OS4w
cHQiPg0KPHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPlBvbGljeSB3aWxsIGJl
IGluc3RhbGxlZCBvciBwb3B1bGF0ZWQgYXQgZGF0YSBwbGFuZSBub2RlLiBGb3IgZXhhbXBsZSwg
ZWFjaCBpbnRlcmFjdGlvbiBiZXR3ZWVuIFBDRSBzZXJ2ZXIgYW5kIFNGQyBDbGFzc2lmaWVyPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJn
aW4tdG9wLWFsdDo5LjBwdDttYXJnaW4tcmlnaHQ6MTguMHB0O21hcmdpbi1ib3R0b206OS4wcHQ7
bWFyZ2luLWxlZnQ6OS4wcHQiPg0KPHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6
MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOiMxRjQ5N0Qi
PldpbGwgbGVhZCB0byBjbGFzc2lmaWNhdGlvbiBydWxlcyBiZWluZyBpbnN0YWxsZWQgd2hpY2gg
ZW5hYmxlIFNGUCBzZWxlY3Rpb24gZm9yIHRoZSB0cmFmZmljLCBlYWNoIGludGVyYWN0aW9uIGJl
dHdlZW4gU0ZDIGNvbnRyb2xsZXIgYW5kIFNGQyBkYXRhIHBsYW5lIG5vZGUoZS5nLiwgU0ZGKSB3
aWxsDQogbGVhZCB0byBmb3J3YXJkaW5nIHBvbGljeSBiZWluZyBwb3B1bGF0ZWQgYXQgdGhlIGNv
cnJlc3BvbmRpbmcgbm9kZXMuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb0xpc3RQYXJhZ3JhcGgiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6OS4w
cHQ7bWFyZ2luLXJpZ2h0OjkuMHB0O21hcmdpbi1ib3R0b206OS4wcHQ7bWFyZ2luLWxlZnQ6MzAu
MHB0O3RleHQtaW5kZW50Oi0xOC4wcHQ7bXNvLWxpc3Q6bDAgbGV2ZWwxIGxmbzEiPg0KPCFbaWYg
IXN1cHBvcnRMaXN0c10+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj48c3BhbiBz
dHlsZT0ibXNvLWxpc3Q6SWdub3JlIj4zLjxzcGFuIHN0eWxlPSJmb250OjcuMHB0ICZxdW90O1Rp
bWVzIE5ldyBSb21hbiZxdW90OyI+Jm5ic3A7DQo8L3NwYW4+PC9zcGFuPjwvc3Bhbj48IVtlbmRp
Zl0+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5JcyB0aGVyZSBhbnkgd2F5IHRv
IG1hbmFnZSBvciBjb25maWd1ZSB0aGUgcHJvY2VzcyBvZiBpbnN0YW50aWF0aW9uIG9mIFNGUD88
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1h
cmdpbi10b3AtYWx0OjkuMHB0O21hcmdpbi1yaWdodDoxOC4wcHQ7bWFyZ2luLWJvdHRvbTo5LjBw
dDttYXJnaW4tbGVmdDo5LjBwdCI+DQo8c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6
ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6IzFGNDk3
RCI+W1Fpbl06IFRoaXMgaXMgd2hhdCB3ZSB0cnkgdG8gc29sdmUgaW4gdGhpcyBkcmFmdCBhbmQg
cHJvcG9zZXMgYSB3YXkgdG8gbWFuYWdlIG9yIGNvbmZpZ3VyZSBvZiBTRlAgaW5zdGFudGlhdGlv
biBwcm9jZXNzLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6OS4wcHQ7bWFyZ2luLXJpZ2h0OjE4LjBwdDttYXJnaW4t
Ym90dG9tOjkuMHB0O21hcmdpbi1sZWZ0OjkuMHB0Ij4NCjxzcGFuIGxhbmc9IkVOLVVTIiBzdHls
ZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztj
b2xvcjojMUY0OTdEIj5UaGUgYmFzaWMgaWRlYSBpcyB0byB1c2UgUENFIGluaXRpYXRlZCBtZWNo
YW5pc20gcHJvcG9zZWQgaW4gZHJhZnQtaWV0Zi1wY2UtcGNlLWluaXRpYXRlZC1sc3AtMDIgYW5k
IGNvbWJpbmUgd2l0aCBTRlAgSWRlbnRpZmllciBUTFYgcHJvcG9zZWQgaW4gdGhpcyBkcmFmdCB0
byBwcm92aWRlIFNGUCBpbnN0YW50aWF0aW9uDQogbWFuYWdlbWVudC48bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2lu
OjBjbTttYXJnaW4tYm90dG9tOi4wMDAxcHQiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9u
dC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpi
bGFjayI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbjowY207bWFyZ2luLWJvdHRvbTouMDAwMXB0Ij48
c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPkJlc3QgUmVnYXJkcyw8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0i
bWFyZ2luOjBjbTttYXJnaW4tYm90dG9tOi4wMDAxcHQiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHls
ZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztj
b2xvcjpibGFjayI+SGFvPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbjowY207bWFyZ2luLWJvdHRvbTouMDAwMXB0
Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPiZuYnNwOzxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJn
aW46MGNtO21hcmdpbi1ib3R0b206LjAwMDFwdCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJm
b250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssJnF1b3Q7c2Fu
cy1zZXJpZiZxdW90Oztjb2xvcjpzaWx2ZXIiPjIwMTUtMDMtMTM8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8ZGl2IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW46MGNtO21hcmdpbi1ib3R0
b206LjAwMDFwdCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xv
cjpzaWx2ZXIiPg0KPGhyIHNpemU9IjEiIHdpZHRoPSIxMjIiIHN0eWxlPSJ3aWR0aDo5MS41cHQi
IGFsaWduPSJsZWZ0Ij4NCjwvc3Bhbj48L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtYXJnaW46MGNtO21hcmdpbi1ib3R0b206LjAwMDFwdCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0
eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssJnF1
b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjpzaWx2ZXIiPkhhbzxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_B8F9A780D330094D99AF023C5877DABA846F54E4nkgeml501mbschi_--


From nobody Mon Mar 16 23:30:52 2015
Return-Path: <bill.wu@huawei.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AB2F1A0099; Mon, 16 Mar 2015 23:30:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.76
X-Spam-Level: 
X-Spam-Status: No, score=-1.76 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nYp0Re-FDzIk; Mon, 16 Mar 2015 23:30:43 -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 A74431A005F; Mon, 16 Mar 2015 23:30:42 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BTS54126; Tue, 17 Mar 2015 06:30:40 +0000 (GMT)
Received: from NKGEML406-HUB.china.huawei.com (10.98.56.37) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 17 Mar 2015 06:30:39 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.244]) by nkgeml406-hub.china.huawei.com ([10.98.56.37]) with mapi id 14.03.0158.001; Tue, 17 Mar 2015 14:30:32 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "pce@ietf.org" <pce@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: Comments on draft-wu-pce-traffic-steering-sfc
Thread-Index: AdBgLHAKHYWbkiyCTs+0vjFBI7EDVQANba3gAAZWuIA=
Date: Tue, 17 Mar 2015 06:30:31 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA84704C98@nkgeml501-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.138.41.180]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA84704C98nkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/enghvNixtGixPZHKwGobCtjpiyQ>
Subject: Re: [sfc] Comments on draft-wu-pce-traffic-steering-sfc
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 17 Mar 2015 06:30:45 -0000

--_000_B8F9A780D330094D99AF023C5877DABA84704C98nkgeml501mbschi_
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64

RllJLg0KDQq3orz+yMs6IFFpbiBXdQ0Kt6LLzcqxvOQ6IDIwMTXE6jPUwjE3yNUgMTI6MDENCsrV
vP7IyzogJ1JvbiBQYXJrZXInDQqzrcvNOiBEaHJ1diBEaG9keQ0K1vfM4jogUkU6IENvbW1lbnRz
IG9uIGRyYWZ0LXd1LXBjZS10cmFmZmljLXN0ZWVyaW5nLXNmYw0KDQpIaSwgUm9uOg0KVGhhbmtz
IGZvciB5b3VyIHZhbHVhYmxlIGNvbW1lbnRzLiBTZWUgbXkgcmVwbHkgaW5saW5lLg0KDQotUWlu
DQq3orz+yMs6IFJvbiBQYXJrZXIgW21haWx0bzpSb25fUGFya2VyQGFmZmlybWVkbmV0d29ya3Mu
Y29tXQ0Kt6LLzcqxvOQ6IDIwMTXE6jPUwjE3yNUgNTozMg0KytW8/sjLOiBRaW4gV3UNCtb3zOI6
IENvbW1lbnRzIG9uIGRyYWZ0LXd1LXBjZS10cmFmZmljLXN0ZWVyaW5nLXNmYw0KDQpJbiBzZWN0
aW9uIDUuMi4xLCB0aGUgZm9ybWF0IGluY3VkZXMgdGhlIFNGUCBJRCBhbmQgdGhlIFNlcnZpY2Ug
SW5kZXguICAgQnV0IHRoaXMgaXMgYSBtZXNzYWdlIGZyb20gUENFIHRvIFBDQyAocHJlc3VtYWJs
eSB0aGUgY2xhc3NpZmllcikuDQoNCltRaW5dOkNvcnJlY3QuDQoNCldoYXQgZG9lcyB0aGUgaW5k
ZXggbWVhbiBpbiB0aGF0IGNvbnRleHQ/DQoNCltRaW5dOiBUaGUgaW5kZXggaXMgdXNlZCB0byBj
b3VudCB0aGUgbnVtYmVyIG9mIHNlcnZpY2UgcHJvdmlkZWQgYnkgc2VydmljZSBmdW5jdGlvbiBj
aGFpbiwgV2hlbiBpdCBpcyBjYXJyaWVkIGluIHRoZSBTRkMgZW5jYXBzdWxhdGlvbiwgaXQgY2Fu
IGZ1cnRoZXIgYmUgdXNlZCBieSBTRkYgdG8gcHJvdmlkZSBsb2NhdGlvbiB3aXRoaW4gdGhlIHNl
cnZpY2UgcGF0aC4gV2Ugd2lsbCBhZGQgc29tZSB0ZXh0IHRvIGNsYXJpZnkgdGhpcyBpbiB0aGUg
bmV4dCB1cGRhdGUuDQoNCg0KQWxzbywgY291bGQgeW91IGRlZmluZSBvciBnaXZlIG1vcmUgYmFj
a2dyb3VuZCBvbiChsFBMU1AtSUShsSBpbiB0aGUgU1BJIGRlZmluaXRpb24/DQoNCltRaW5dOk9r
YXksIGhvdyBhYm91dCBhZGQgdGhlIGZvbGxvd2luZyB0ZXh0IHVuZGVyIHRoZSBMU1AgT2JqZWN0
IGZvcm1hdCBpbiB0aGUgZHJhZnQ6DQqhsA0KVGhlIFBMU1AtSUQgaXMgYSBQQ0VQLXNwZWNpZmlj
IGlkZW50aWZpZXIgZm9yIHRoZSBMU1AuIEl0IGlzIHNldCB0byBhDQogICB2YWx1ZSB0aGF0IGlz
IGNvbnN0YW50IGZvciB0aGUgbGlmZXRpbWUgb2YgdGhlIFBDRVAgc2Vzc2lvbi4gQSBQQ0MNCiAg
IGNyZWF0ZXMgYSB1bmlxdWUgUExTUC1JRCBmb3IgZWFjaCBMU1AgYW5kIHdpbGwgYWR2ZXJ0aXNl
IHRoZSBzYW1lIFBMU1AtSUQNCiAgIG9uIGFsbCBQQ0VQIHNlc3Npb25zIGl0IG1haW50YWlucyBh
dCBhIGdpdmVuIHRpbWVzLiBUaGUNCiAgIHZhbHVlcyBvZiAwIGFuZCAweEZGRkZGIGFyZSByZXNl
cnZlZC4NCqGxDQpJcyB0aGUgUENDIGV4cGVjdGVkIHRvIKGwa25vd6GxIGEgcHJpb3JpIHRoZSBm
dWxsIHNlcXVlbmNlIG9mIFNGRqGvcyBhbmQgU0ZJoa9zIGFzc29jaWF0ZWQgdG8gYSBTZXJ2aWNl
IFBhdGggSUQ/ICAgIE9yIHNob3VsZCB0aGF0IGJlIGNvbnZleWVkIGluIHRoZSBtZXNzYWdlIGJl
dHdlZW4gUENFIGFuZCBQQ0MgZHluYW1pY2FsbHk/DQoNCg0KW1Fpbl06IEluIGNhc2UgU0ZDIGZv
cndhcmRpbmcgaXMgZnVsbHkgZGlzdHJpYnV0ZWQsIFBDRSBvbmx5IG5lZWRzIHRvIGNvbXB1dGUg
dGhlIGZ1bGwgc2VxdWVuY2Ugb2YgU0ZGIGNvcnJlc3BvbmRpbmcgdG8gU0ZQIElEIGJhc2VkIG9u
IHRoZSBzb3VyY2UgYWRkcmVzcyBhbmQgZGVzdGluYXRpb24gYWRkcmVzcyBzcGVjaWZpZWQgaW4g
dGhlIEVORC0gUE9JTlRTIG9iamVjdCBvZiBQQ0UgbWVzc2FnZS4gVGhlIGZ1bGwgc2VxdWVuY2Ug
b2YgU0ZGIGNhbiBiZSBjYXJyaWVkIHVzaW5nIEV4cGxpY2l0IFJvdXRlIE9iamVjdC4NCg0KVGhl
IGNsYXNzaWZpZXIgb25seSBuZWVkcyB0byBrbm93IGhvdyB0byBtYXAgdHJhZmZpYyB0byB0aGUg
c3BlY2lmaWMgU0ZQLg0KZnVsbCBzZXF1ZW5jZSBvZiBTRkmhr3MgYXNzb2NpYXRlZCB0byBhIFNl
cnZpY2UgUGF0aCBJRCBzZWVtcyBub3QgbmVlZGVkIGZvciB0aGUgY2FzZSB3aGVuIFNGQyBmb3J3
YXJkaW5nIGlzIGZ1bGx5IGRpc3RyaWJ1dGVkLg0KDQpJZiBQQ0MgaXMgZXhwZWN0ZWQgdG8gobBr
bm93obEgYSBwcmlvcmkgdGhlIGZ1bGwgc2VxdWVuY2Ugb2YgU0ZJoa9zIGFzc29jaWF0ZWQgdG8g
YSBTZXJ2aWNlIFBhdGggSUQsIFBDQyBjYW4gdXNlIHNlZ21lbnQgcm91dGluZyBhcHByb2FjaCBw
cm9wb3NlZCBpbiBkcmFmdC1kdy1wY2Utc2VydmljZS1zZWdtZW50LXJvdXRpbmc8aHR0cDovL3Rv
b2xzLmlldGYub3JnL2lkL2RyYWZ0LWR3LXBjZS1zZXJ2aWNlLXNlZ21lbnQtcm91dGluZy0wMS50
eHQ+IGFuZCAgZHJhZnQtaWV0Zi1wY2Utc2VnbWVudC1yb3V0aW5nPGh0dHA6Ly90b29scy5pZXRm
Lm9yZy93Zy9wY2UvZHJhZnQtaWV0Zi1wY2Utc2VnbWVudC1yb3V0aW5nLz4gdG8gZGV0ZXJtaW5l
IGEgZXhwbGljaXQgcGF0aCB0cmF2ZXJzaW5nIGJ5IFNGIGZvciB0aGUgdHJhZmZpYy4gWWVzLCBm
dWxsIHNlcXVlbmNlIG9mIFNGSSBjYW4gYmUgY29udmV5ZWQgaW4gdGhlIG1lc3NhZ2UgYmV0d2Vl
biBQQ0UgYW5kIFBDQy4NCkFsdGVybmF0aXZlbHksIFBDQyBhcyBjbGFzc2lmaWVyIGNhbiBpbnRl
cmFjdCB3aXRoIFNGQyBjb250cm9sbGVyIHRvIGdldCBmdWxsIHNlcXVlbmNlIG9mIFNGSaGvcy4N
Cg0KSXMgdGhlIFBDQyBleHBlY3RlZCB0byBjb25jcmV0ZWx5IHNlbGVjdCB0aGUgUlNQIElEIChp
LmUuLCB3aGljaCBTRkmhr3MgZXhhY3RseSkgYW5kIGlmIHNvLCBob3cgZG9lcyB0aGF0IGZhY3Rv
ciBpbnRvIHRoZSBhcHByb2FjaD8NCg0KW1Fpbl06IElmIFBDQyBpcyBleHBlY3RlZCB0byBjb25j
cmV0ZWx5IHNlbGVjdCB0aGUgUmVuZGVyZWQgU2VydmljZSBmdW5jdGlvbiBQYXRoLCBJIHRoaW5r
IHdlIGNhbiByZWx5IG9uIHNlcnZpY2Ugc2VnbWVudCBhcHByb2FjaCBwcm9wb3NlZCBpbiBkcmFm
dC1kdy1wY2Utc2VydmljZS1zZWdtZW50LXJvdXRpbmc8aHR0cDovL3Rvb2xzLmlldGYub3JnL2lk
L2RyYWZ0LWR3LXBjZS1zZXJ2aWNlLXNlZ21lbnQtcm91dGluZy0wMS50eHQ+IGNvbWJpbmluZyB3
aXRoIHRoZSBtZWNoYW5pc20gcHJvcG9zZWQgaW4gZHJhZnQtd3UtcGNlLXRyYWZmaWMtc3RlZXJp
bmctc2ZjIGFuZCBzZWdtZW50IHJvdXRpbmcgYXBwcm9hY2ggZGVmaW5lZCBpbiBkcmFmdC1pZXRm
LXBjZS1zZWdtZW50LXJvdXRpbmc8aHR0cDovL3Rvb2xzLmlldGYub3JnL3dnL3BjZS9kcmFmdC1p
ZXRmLXBjZS1zZWdtZW50LXJvdXRpbmcvPi4NCg0KVGhhbmtzLg0KDQogICAgUm9uDQoNCg0KDQo=

--_000_B8F9A780D330094D99AF023C5877DABA84704C98nkgeml501mbschi_
Content-Type: text/html; charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dgb2312">
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:=CB=CE=CC=E5;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@=CB=CE=CC=E5";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML =D4=A4=C9=E8=B8=F1=CA=BD Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:=CB=CE=CC=E5;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"=C5=FA=D7=A2=BF=F2=CE=C4=B1=BE Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:9.0pt;
	font-family:"Calibri","sans-serif";}
span.HTMLChar
	{mso-style-name:"HTML =D4=A4=C9=E8=B8=F1=CA=BD Char";
	mso-style-priority:99;
	mso-style-link:"HTML =D4=A4=C9=E8=B8=F1=CA=BD";
	font-family:=CB=CE=CC=E5;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.h31
	{mso-style-name:h31;
	font-family:"Courier New";
	font-weight:bold;}
span.Char
	{mso-style-name:"=C5=FA=D7=A2=BF=F2=CE=C4=B1=BE Char";
	mso-style-priority:99;
	mso-style-link:=C5=FA=D7=A2=BF=F2=CE=C4=B1=BE;
	font-family:"Calibri","sans-serif";}
span.EmailStyle24
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"ZH-CN" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D">FYI.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:=CB=
=CE=CC=E5">=B7=A2=BC=FE=C8=CB<span lang=3D"EN-US">:</span></span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:=CB=CE=CC=E5"> Qin Wu
<br>
</span><b><span style=3D"font-size:10.0pt;font-family:=CB=CE=CC=E5">=B7=A2=
=CB=CD=CA=B1=BC=E4<span lang=3D"EN-US">:</span></span></b><span lang=3D"EN-=
US" style=3D"font-size:10.0pt;font-family:=CB=CE=CC=E5"> 2015</span><span s=
tyle=3D"font-size:10.0pt;font-family:=CB=CE=CC=E5">=C4=EA<span lang=3D"EN-U=
S">3</span>=D4=C2<span lang=3D"EN-US">17</span>=C8=D5<span lang=3D"EN-US">
 12:01<br>
</span><b>=CA=D5=BC=FE=C8=CB<span lang=3D"EN-US">:</span></b><span lang=3D"=
EN-US"> 'Ron Parker'<br>
</span><b>=B3=AD=CB=CD<span lang=3D"EN-US">:</span></b><span lang=3D"EN-US"=
> Dhruv Dhody<br>
</span><b>=D6=F7=CC=E2<span lang=3D"EN-US">:</span></b><span lang=3D"EN-US"=
> RE: Comments on draft-wu-pce-traffic-steering-sfc<o:p></o:p></span></span=
></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D">Hi, Ron:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D">Thanks for your valuable comments. See my reply inline.<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D">-Qin<o:p></o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:=CB=
=CE=CC=E5">=B7=A2=BC=FE=C8=CB<span lang=3D"EN-US">:</span></span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:=CB=CE=CC=E5"> Ron Par=
ker [<a href=3D"mailto:Ron_Parker@affirmednetworks.com">mailto:Ron_Parker@a=
ffirmednetworks.com</a>]
<br>
</span><b><span style=3D"font-size:10.0pt;font-family:=CB=CE=CC=E5">=B7=A2=
=CB=CD=CA=B1=BC=E4<span lang=3D"EN-US">:</span></span></b><span lang=3D"EN-=
US" style=3D"font-size:10.0pt;font-family:=CB=CE=CC=E5"> 2015</span><span s=
tyle=3D"font-size:10.0pt;font-family:=CB=CE=CC=E5">=C4=EA<span lang=3D"EN-U=
S">3</span>=D4=C2<span lang=3D"EN-US">17</span>=C8=D5<span lang=3D"EN-US">
 5:32<br>
</span><b>=CA=D5=BC=FE=C8=CB<span lang=3D"EN-US">:</span></b><span lang=3D"=
EN-US"> Qin Wu<br>
</span><b>=D6=F7=CC=E2<span lang=3D"EN-US">:</span></b><span lang=3D"EN-US"=
> Comments on draft-wu-pce-traffic-steering-sfc<o:p></o:p></span></span></p=
>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">In section 5.2.1, the format in=
cudes the SFP ID and the Service Index.&nbsp;&nbsp; But this is a message f=
rom PCE to PCC (presumably the classifier).&nbsp;&nbsp;
<span style=3D"color:#1F497D"><o:p></o:p></span></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D">[Qin]:Correct.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">What does the index mean in tha=
t context?&nbsp;&nbsp;
<span style=3D"color:#1F497D"><o:p></o:p></span></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D">[Qin]: The index is used to count the number of service provided =
by service function chain, When it is carried in the SFC encapsulation, it =
can further be used by SFF to provide
 location within the service path.</span><span lang=3D"EN-US" style=3D"font=
-size:10.5pt;color:#1F497D"> We will add some text to clarify this in the n=
ext update.</span><span lang=3D"EN-US" style=3D"font-size:10.5pt;color:#1F4=
97D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Also, could you define or give =
more background on =A1=B0PLSP-ID=A1=B1 in the SPI definition?<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D">[Qin]:Okay, how about add the following text under the LSP Object=
 format in the draft:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D">=A1=B0<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-indent:18.0pt"><span lang=3D"EN-US" st=
yle=3D"font-size:12.0pt;font-family:=CB=CE=CC=E5">The PLSP-ID is a PCEP-spe=
cific identifier for the LSP. It is set to a<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:12.0pt;font-=
family:=CB=CE=CC=E5">&nbsp;&nbsp; value that is constant for the lifetime o=
f the PCEP session.</span><span lang=3D"EN-US">
</span><span lang=3D"EN-US" style=3D"font-size:12.0pt;font-family:=CB=CE=CC=
=E5">A PCC<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:12.0pt;font-=
family:=CB=CE=CC=E5">&nbsp;&nbsp; creates a unique PLSP-ID for each LSP and=
 will advertise the same PLSP-ID<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:12.0pt;font-=
family:=CB=CE=CC=E5">&nbsp;&nbsp; on all PCEP sessions it maintains at a gi=
ven times.</span><span lang=3D"EN-US">
</span><span lang=3D"EN-US" style=3D"font-size:12.0pt;font-family:=CB=CE=CC=
=E5">The<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:12.0pt;font-=
family:=CB=CE=CC=E5">&nbsp;&nbsp; values of 0 and 0xFFFFF are reserved.<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D">=A1=B1<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Is the PCC expected to =A1=B0kn=
ow=A1=B1 a priori the full sequence of SFF=A1=AFs and SFI=A1=AFs associated=
 to a Service Path ID?&nbsp;&nbsp;&nbsp; Or should that be conveyed in the =
message between PCE and PCC dynamically?&nbsp;&nbsp;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<pre style=3D"page-break-before:always"><span lang=3D"EN-US" style=3D"font-=
size:10.5pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1=
F497D">[Qin]: In case SFC forwarding is fully distributed, PCE only needs t=
o compute the full sequence of SFF corresponding to SFP ID based on the sou=
rce address and destination address specified in the END- POINTS object of =
PCE message. The full sequence of SFF can be carried using Explicit Route O=
bject.<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span lang=3D"EN-US" style=3D"font-=
size:10.5pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1=
F497D">The classifier only needs to know how to map traffic to the specific=
 SFP.<o:p></o:p></span></pre>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D">full sequence of SFI=A1=AFs associated to a Service Path ID seems=
 not needed for the case when SFC forwarding is fully distributed.<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D">If PCC is expected to =A1=B0know=A1=B1 a priori the full sequence=
 of SFI=A1=AFs associated to a Service Path ID, PCC can use segment routing=
 approach proposed in
<a href=3D"http://tools.ietf.org/id/draft-dw-pce-service-segment-routing-01=
.txt"><span style=3D"color:#1F497D;text-decoration:none">draft-dw-pce-servi=
ce-segment-routing</span></a> and&nbsp;
<a href=3D"http://tools.ietf.org/wg/pce/draft-ietf-pce-segment-routing/"><s=
pan style=3D"color:#1F497D;text-decoration:none">draft-ietf-pce-segment-rou=
ting</span></a> to determine a explicit path traversing by SF for the traff=
ic. Yes, full sequence of SFI can be
 conveyed in the message between PCE and PCC.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D">Alternatively, PCC as classifier can interact with SFC controller=
 to get full sequence of SFI=A1=AFs.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Is the PCC expected to concrete=
ly select the RSP ID (i.e., which SFI=A1=AFs exactly) and if so, how does t=
hat factor into the approach?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D">[Qin]: If PCC is expected to concretely select the Rendered Servi=
ce function Path, I think we can rely on service segment approach proposed =
in
<a href=3D"http://tools.ietf.org/id/draft-dw-pce-service-segment-routing-01=
.txt"><span style=3D"color:#1F497D;text-decoration:none">draft-dw-pce-servi=
ce-segment-routing</span></a> combining with the mechanism proposed in draf=
t-wu-pce-traffic-steering-sfc and segment
 routing approach defined in <a href=3D"http://tools.ietf.org/wg/pce/draft-=
ietf-pce-segment-routing/">
<span style=3D"color:#1F497D;text-decoration:none">draft-ietf-pce-segment-r=
outing</span></a>.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Thanks.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp; Ron<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--_000_B8F9A780D330094D99AF023C5877DABA84704C98nkgeml501mbschi_--


From nobody Tue Mar 17 03:49:36 2015
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EE511A0263; Tue, 17 Mar 2015 03:49:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.422
X-Spam-Level: 
X-Spam-Status: No, score=-1.422 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CN_BODY_35=0.339, 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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TojQWykVO_HJ; Tue, 17 Mar 2015 03:49:28 -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 E65621A0235; Tue, 17 Mar 2015 03:49:27 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml403-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BTT14245; Tue, 17 Mar 2015 10:49:26 +0000 (GMT)
Received: from NKGEML410-HUB.china.huawei.com (10.98.56.41) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 17 Mar 2015 10:49:25 +0000
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.209]) by nkgeml410-hub.china.huawei.com ([10.98.56.41]) with mapi id 14.03.0158.001; Tue, 17 Mar 2015 18:49:21 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: "stbryant@cisco.com" <stbryant@cisco.com>, Eric C Rosen <erosen@juniper.net>, BIER <bier@ietf.org>
Thread-Topic: [Bier] Encapsulation first nibble
Thread-Index: AQHQXcZrqojq7Dn2dkqRctiyZ05xTp0aTR0AgAY0PqA=
Date: Tue, 17 Mar 2015 10:49:21 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CB77@NKGEML512-MBS.china.huawei.com>
References: <55033E87.3030305@juniper.net> <5503403E.4050304@cisco.com>
In-Reply-To: <5503403E.4050304@cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.99.17]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/aw8b-eRXmsvGniNyZVOHHrqMLO0>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] [Bier] Encapsulation first nibble
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 17 Mar 2015 10:49:30 -0000

SSBiZWxpZXZlIHRoaXMgc2hvdWxkIGJlIGFwcGxpY2FibGUgdG8gdGhlIE5TSCBhcyB3ZWxsIChp
LmUuLCBzZXQgdGhlIG5pYmJsZSB0byB6ZXJvKSBpZiBpdCdzIGFzc3VtZWQgdGhhdCB0aGUgTlNI
IGNvdWxkIGJlIGVuY2Fwc3VsYXRlZCB3aXRoaW4gYW4gTVBMUyBwYWNrZXQuIA0KDQpCZXN0IHJl
Z2FyZHMsDQpYaWFvaHUNCg0KLS0tLS3Tyrz+1K28/i0tLS0tDQq3orz+yMs6IEJJRVIgW21haWx0
bzpiaWVyLWJvdW5jZXNAaWV0Zi5vcmddILT6se0gU3Rld2FydCBCcnlhbnQNCreiy83KsbzkOiAy
MDE1xOoz1MIxNMjVIDM6NTQNCsrVvP7IyzogRXJpYyBDIFJvc2VuOyBCSUVSDQrW98ziOiBSZTog
W0JpZXJdIEVuY2Fwc3VsYXRpb24gZmlyc3QgbmliYmxlDQoNCk9uIDEzLzAzLzIwMTUgMTk6NDYs
IEVyaWMgQyBSb3NlbiB3cm90ZToNCj4gSGVyZSdzIGEgc21hbGwgaXNzdWUgZm9yIHRoZSBXRyB0
byBjb25zaWRlci4NCj4NCj4gVGhlIG1wbHMtYmllci1lbmNhcHN1bGF0aW9uIGRyYWZ0IHNwZWNp
ZmllcyB0aGF0IHRoZSBmaXJzdCBuaWJibGUgb2YgDQo+IHRoZSBlbmNhcHN1bGF0aW9uIGlzIHRv
IGJlIGEgQklFUiBlbmNhcHMgdmVyc2lvbiBudW1iZXIsIGluaXRpYWxseSAwLg0KPiBUaGUgdmFs
dWVzIDQgYW5kIDYgYXJlIGV4Y2x1ZGVkIGZyb20gdGhlICJ2ZXJzaW9uIG51bWJlciIgc3BhY2Us
IGFzIA0KPiB0aGVyZSBhcmUgdmFyaW91cyBoZXVyaXN0aWMgcHJvY2VkdXJlcyBkZXBsb3llZCB0
aGF0IGludGVycHJldCB0aG9zZSANCj4gdmFsdWVzIG9mIHRoZSBmaXJzdCBuaWJibGUgZm9sbG93
aW5nIHRoZSBNUExTIGxhYmVsIHN0YWNrIGFzIA0KPiBpZGVudGlmeWluZyB0aGUgcGF5bG9hZCB0
byBiZSBhbiBJUCBwYWNrZXQuDQo+DQo+IEhvd2V2ZXIsIHRoZXJlIGFyZSBhbHNvIHZhcmlvdXMg
ZGVwbG95ZWQgaGV1cmlzdGljcyB0aGF0IG1heSBpbnRlcnByZXQgDQo+IHRoZSB2YWx1ZXMgMCBh
bmQgMSBhcyBpZGVudGlmeWluZyBhIHBzZXVkb3dpcmUgcGF5bG9hZCwgZWl0aGVyIGRhdGEgb3Ig
DQo+IE9BTS4NCj4NCj4gVGhpcyByYWlzZXMgdGhlIGlzc3VlIG9mIHdoZXRoZXIgd2UgbWlnaHQg
YmUgYmV0dGVyIG9mZiBzZXR0aW5nIHRoaXMgDQo+IG5pYmJsZSB0byBhIGZpeGVkIHZhbHVlLCBy
YXRoZXIgdGhhbiB0cnlpbmcgdG8gdXNlIGl0IGFzIGEgdmVyc2lvbiANCj4gbnVtYmVyLiAgSWYg
d2UgcmVhbGx5IG5lZWQgYSB2ZXJzaW9uIG51bWJlciBpbiB0aGUgZW5jYXBzLCBwZXJoYXBzIGl0
IA0KPiBzaG91bGQgYmUgc29tZXBsYWNlIHdoZXJlIGl0IGRlZmluaXRlbHkgd29uJ3QgaW1wYWN0
IGFueSBleGlzdGluZw0KPiBoZXVyaXN0aWNzLiAgIFRoZSBzYWZlc3QgdmFsdWUgZm9yIHRoZSBm
aXJzdCBuaWJibGUgbWlnaHQgYmUgb25lIG9mIA0KPiB0aGUgdmFsdWVzIDUtOSwgd2hpY2ggYXJl
IGFscmVhZHkgYXNzaWduZWQgYXMgSVAgVmVyc2lvbiBOdW1iZXJzLCBidXQgDQo+IGFyZSBhc3Np
Z25lZCB0byB0aGluZ3MgdGhhdCAoSSB0aGluaykgZG9uJ3QgYWN0dWFsbHkgZXhpc3QuDQo+DQo+
DQo+DQo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+
IEJJRVIgbWFpbGluZyBsaXN0DQo+IEJJRVJAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5v
cmcvbWFpbG1hbi9saXN0aW5mby9iaWVyDQo+DQoNCkkgYWdyZWUgd2l0aCBFcmljIG9uIHRoaXMu
DQoNCkkgd291bGQgc2V0IHRoZSBuaWJibGUgdG8gemVybyB3aGljaCB0ZWxscyBhbnkgcGFyc2Vy
IHRoYXQgdGhlIHBheWxvYWQgaXMgb25seSB1bmRlcnN0YW5kYWJsZSBvbmx5IGJ5IGEgbm9kZSB0
aGF0IGtub3dzIHRoZSBhY3Rpb25zIHJlcXVpcmVkIGJ5IHRoZSBCT1MgbGFiZWwuDQoNCkkgdGhp
bmsgdGhlIEFDSCBSRkMgc2F5cyBzb21ldGhpbmcgbGlrZSB0aGUgYWJvdmUsIGJ1dCB3b3VsZCBo
YXZlIHRvIGdvIGZpbmQgdGhlIHNwZWNpZmljIHRleHQuDQoNCi0gU3Rld2FydA0KDQpfX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KQklFUiBtYWlsaW5nIGxp
c3QNCkJJRVJAaWV0Zi5vcmcNCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8v
Ymllcg0K


From nobody Tue Mar 17 04:17:25 2015
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F41851A0266; Tue, 17 Mar 2015 04:17:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.422
X-Spam-Level: 
X-Spam-Status: No, score=-1.422 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CN_BODY_35=0.339, 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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id prel964jWphW; Tue, 17 Mar 2015 04:17:19 -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 43FD51A0358; Tue, 17 Mar 2015 04:17:18 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BTT17404; Tue, 17 Mar 2015 11:17:16 +0000 (GMT)
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 17 Mar 2015 11:17:15 +0000
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.209]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.03.0158.001; Tue, 17 Mar 2015 19:17:04 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Xuxiaohu <xuxiaohu@huawei.com>, "stbryant@cisco.com" <stbryant@cisco.com>,  Eric C Rosen <erosen@juniper.net>, BIER <bier@ietf.org>
Thread-Topic: [Bier] Encapsulation first nibble
Thread-Index: AQHQXcZrqojq7Dn2dkqRctiyZ05xTp0aTR0AgAY0PqCAAAkpwA==
Date: Tue, 17 Mar 2015 11:17:04 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CBB2@NKGEML512-MBS.china.huawei.com>
References: <55033E87.3030305@juniper.net> <5503403E.4050304@cisco.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CB77@NKGEML512-MBS.china.huawei.com>
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CB77@NKGEML512-MBS.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.99.17]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/8TaAUwBY-TRe-XlAsyG3dqv6OF4>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] [Bier] Encapsulation first nibble
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 17 Mar 2015 11:17:21 -0000

QW5vdGhlciB3YXkgaXMgdG8gYWRkIGEgcHJvdG9jb2wgaWRlbnRpZmllciBmaWVsZCBhZnRlciB0
aGUgYm90dG9tIG9mIHRoZSBsYWJlbCBzdGFjayAoaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1s
L2RyYWZ0LXh1LW1wbHMtcGF5bG9hZC1wcm90b2NvbC1pZGVudGlmaWVyLTAwKS4gSW4gdGhpcyB3
YXksIHdlIHdvdWxkIG5vdCBiZSBib3RoZXJlZCBhYm91dCB0aGUgbmliYmxlIGlzc3VlIGFueW1v
cmUgd2hlbiBwcm9wb3NpbmcgYW55IG5ldyBlbmNhcHN1bGF0aW9uIGhlYWRlciB3aGljaCBtYXkg
YmUgZW5jYXBzdWxhdGVkIHdpdGhpbiBhbiBNUExTIHBhY2tldC4NCg0KQmVzdCByZWdhcmRzLA0K
WGlhb2h1DQoNCi0tLS0t08q8/tStvP4tLS0tLQ0Kt6K8/sjLOiBtcGxzIFttYWlsdG86bXBscy1i
b3VuY2VzQGlldGYub3JnXSC0+rHtIFh1eGlhb2h1DQq3osvNyrG85DogMjAxNcTqM9TCMTfI1SAx
ODo0OQ0KytW8/sjLOiBzdGJyeWFudEBjaXNjby5jb207IEVyaWMgQyBSb3NlbjsgQklFUg0Ks63L
zTogbXBsc0BpZXRmLm9yZzsgc2ZjQGlldGYub3JnDQrW98ziOiBSZTogW21wbHNdIFtCaWVyXSBF
bmNhcHN1bGF0aW9uIGZpcnN0IG5pYmJsZQ0KDQpJIGJlbGlldmUgdGhpcyBzaG91bGQgYmUgYXBw
bGljYWJsZSB0byB0aGUgTlNIIGFzIHdlbGwgKGkuZS4sIHNldCB0aGUgbmliYmxlIHRvIHplcm8p
IGlmIGl0J3MgYXNzdW1lZCB0aGF0IHRoZSBOU0ggY291bGQgYmUgZW5jYXBzdWxhdGVkIHdpdGhp
biBhbiBNUExTIHBhY2tldC4gDQoNCkJlc3QgcmVnYXJkcywNClhpYW9odQ0KDQotLS0tLdPKvP7U
rbz+LS0tLS0NCreivP7IyzogQklFUiBbbWFpbHRvOmJpZXItYm91bmNlc0BpZXRmLm9yZ10gtPqx
7SBTdGV3YXJ0IEJyeWFudA0Kt6LLzcqxvOQ6IDIwMTXE6jPUwjE0yNUgMzo1NA0KytW8/sjLOiBF
cmljIEMgUm9zZW47IEJJRVINCtb3zOI6IFJlOiBbQmllcl0gRW5jYXBzdWxhdGlvbiBmaXJzdCBu
aWJibGUNCg0KT24gMTMvMDMvMjAxNSAxOTo0NiwgRXJpYyBDIFJvc2VuIHdyb3RlOg0KPiBIZXJl
J3MgYSBzbWFsbCBpc3N1ZSBmb3IgdGhlIFdHIHRvIGNvbnNpZGVyLg0KPg0KPiBUaGUgbXBscy1i
aWVyLWVuY2Fwc3VsYXRpb24gZHJhZnQgc3BlY2lmaWVzIHRoYXQgdGhlIGZpcnN0IG5pYmJsZSBv
ZiANCj4gdGhlIGVuY2Fwc3VsYXRpb24gaXMgdG8gYmUgYSBCSUVSIGVuY2FwcyB2ZXJzaW9uIG51
bWJlciwgaW5pdGlhbGx5IDAuDQo+IFRoZSB2YWx1ZXMgNCBhbmQgNiBhcmUgZXhjbHVkZWQgZnJv
bSB0aGUgInZlcnNpb24gbnVtYmVyIiBzcGFjZSwgYXMgDQo+IHRoZXJlIGFyZSB2YXJpb3VzIGhl
dXJpc3RpYyBwcm9jZWR1cmVzIGRlcGxveWVkIHRoYXQgaW50ZXJwcmV0IHRob3NlIA0KPiB2YWx1
ZXMgb2YgdGhlIGZpcnN0IG5pYmJsZSBmb2xsb3dpbmcgdGhlIE1QTFMgbGFiZWwgc3RhY2sgYXMg
DQo+IGlkZW50aWZ5aW5nIHRoZSBwYXlsb2FkIHRvIGJlIGFuIElQIHBhY2tldC4NCj4NCj4gSG93
ZXZlciwgdGhlcmUgYXJlIGFsc28gdmFyaW91cyBkZXBsb3llZCBoZXVyaXN0aWNzIHRoYXQgbWF5
IGludGVycHJldCANCj4gdGhlIHZhbHVlcyAwIGFuZCAxIGFzIGlkZW50aWZ5aW5nIGEgcHNldWRv
d2lyZSBwYXlsb2FkLCBlaXRoZXIgZGF0YSBvciANCj4gT0FNLg0KPg0KPiBUaGlzIHJhaXNlcyB0
aGUgaXNzdWUgb2Ygd2hldGhlciB3ZSBtaWdodCBiZSBiZXR0ZXIgb2ZmIHNldHRpbmcgdGhpcyAN
Cj4gbmliYmxlIHRvIGEgZml4ZWQgdmFsdWUsIHJhdGhlciB0aGFuIHRyeWluZyB0byB1c2UgaXQg
YXMgYSB2ZXJzaW9uIA0KPiBudW1iZXIuICBJZiB3ZSByZWFsbHkgbmVlZCBhIHZlcnNpb24gbnVt
YmVyIGluIHRoZSBlbmNhcHMsIHBlcmhhcHMgaXQgDQo+IHNob3VsZCBiZSBzb21lcGxhY2Ugd2hl
cmUgaXQgZGVmaW5pdGVseSB3b24ndCBpbXBhY3QgYW55IGV4aXN0aW5nDQo+IGhldXJpc3RpY3Mu
ICAgVGhlIHNhZmVzdCB2YWx1ZSBmb3IgdGhlIGZpcnN0IG5pYmJsZSBtaWdodCBiZSBvbmUgb2Yg
DQo+IHRoZSB2YWx1ZXMgNS05LCB3aGljaCBhcmUgYWxyZWFkeSBhc3NpZ25lZCBhcyBJUCBWZXJz
aW9uIE51bWJlcnMsIGJ1dCANCj4gYXJlIGFzc2lnbmVkIHRvIHRoaW5ncyB0aGF0IChJIHRoaW5r
KSBkb24ndCBhY3R1YWxseSBleGlzdC4NCj4NCj4NCj4NCj4gX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gQklFUiBtYWlsaW5nIGxpc3QNCj4gQklFUkBp
ZXRmLm9yZw0KPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2JpZXINCj4N
Cg0KSSBhZ3JlZSB3aXRoIEVyaWMgb24gdGhpcy4NCg0KSSB3b3VsZCBzZXQgdGhlIG5pYmJsZSB0
byB6ZXJvIHdoaWNoIHRlbGxzIGFueSBwYXJzZXIgdGhhdCB0aGUgcGF5bG9hZCBpcyBvbmx5IHVu
ZGVyc3RhbmRhYmxlIG9ubHkgYnkgYSBub2RlIHRoYXQga25vd3MgdGhlIGFjdGlvbnMgcmVxdWly
ZWQgYnkgdGhlIEJPUyBsYWJlbC4NCg0KSSB0aGluayB0aGUgQUNIIFJGQyBzYXlzIHNvbWV0aGlu
ZyBsaWtlIHRoZSBhYm92ZSwgYnV0IHdvdWxkIGhhdmUgdG8gZ28gZmluZCB0aGUgc3BlY2lmaWMg
dGV4dC4NCg0KLSBTdGV3YXJ0DQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fDQpCSUVSIG1haWxpbmcgbGlzdA0KQklFUkBpZXRmLm9yZw0KaHR0cHM6Ly93
d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9iaWVyDQpfX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fXw0KbXBscyBtYWlsaW5nIGxpc3QNCm1wbHNAaWV0Zi5v
cmcNCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbXBscw0K


From nobody Tue Mar 17 10:11:36 2015
Return-Path: <erosen@juniper.net>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FA541A87AF; Tue, 17 Mar 2015 10:11:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 wua7SFxeSoVL; Tue, 17 Mar 2015 10:11:31 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0778.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:778]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5AEC91A1B43; Tue, 17 Mar 2015 10:11:31 -0700 (PDT)
Received: from [172.29.32.200] (66.129.241.13) by BY1PR0501MB1093.namprd05.prod.outlook.com (25.160.103.139) with Microsoft SMTP Server (TLS) id 15.1.112.19; Tue, 17 Mar 2015 17:11:12 +0000
Message-ID: <55086028.1070004@juniper.net>
Date: Tue, 17 Mar 2015 13:11:04 -0400
From: Eric C Rosen <erosen@juniper.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Xuxiaohu <xuxiaohu@huawei.com>, "stbryant@cisco.com" <stbryant@cisco.com>,  BIER <bier@ietf.org>
References: <55033E87.3030305@juniper.net> <5503403E.4050304@cisco.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CB77@NKGEML512-MBS.china.huawei.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CBB2@NKGEML512-MBS.china.huawei.com>
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CBB2@NKGEML512-MBS.china.huawei.com>
Content-Type: text/plain; charset="gbk"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [66.129.241.13]
X-ClientProxiedBy: BLUPR07CA0053.namprd07.prod.outlook.com (10.255.223.166) To BY1PR0501MB1093.namprd05.prod.outlook.com (25.160.103.139)
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BY1PR0501MB1093;
X-Forefront-Antispam-Report: BMV:1; SFV:NSPM; SFS:(10019020)(6049001)(6009001)(24454002)(377454003)(479174004)(46102003)(42186005)(86362001)(23696002)(117636001)(59896002)(93886004)(122386002)(92566002)(19580395003)(83506001)(77096005)(2950100001)(62966003)(77156002)(15975445007)(87976001)(65806001)(36756003)(54356999)(50986999)(50466002)(65956001)(65816999)(40100003)(76176999)(87266999)(2501003)(66066001)(47776003)(64126003)(62816006); DIR:OUT; SFP:1102; SCL:1; SRVR:BY1PR0501MB1093; H:[172.29.32.200]; FPR:; SPF:None; MLV:sfv; LANG:en; 
X-Microsoft-Antispam-PRVS: <BY1PR0501MB109315BD28DD82AC0A0E8894D4030@BY1PR0501MB1093.namprd05.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(5002010)(5005006); SRVR:BY1PR0501MB1093; BCL:0; PCL:0; RULEID:; SRVR:BY1PR0501MB1093; 
X-Forefront-PRVS: 0518EEFB48
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 17 Mar 2015 17:11:12.6020 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY1PR0501MB1093
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/VwUZlDOLhst1kHTa4QrRANRvsmU>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>, erosen@juniper.net
Subject: Re: [sfc] [Bier] Encapsulation first nibble
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 17 Mar 2015 17:11:33 -0000

On 3/17/2015 7:17 AM, Xuxiaohu wrote:
> Another way is to add a protocol identifier field after the bottom of
> the label stack
> (https://tools.ietf.org/html/draft-xu-mpls-payload-protocol-identifier-00).
> In this way, we would not be bothered about the nibble issue anymore
> when proposing any new encapsulation header which may be encapsulated
> within an MPLS packet.

When a BIER packet is traveling from BFIR to BFER via a sequence of 
directly connected BFRs, each BFR already knows, via the bottom label, 
that the packet is a BIER packet.  The nibble issue really only matters 
when a BIER packet is traveling through a non-BIER tunnel.

When a BIER packet is traveling through a non-BIER tunnel, some of the 
transit routers may be routers that are running older software.  They 
will base their ECMP treatment of the packet on the first nibble.  A 
protocol identifier field won't help, because these old routers won't 
understand it.  For newer routers, I think the proper direction is to 
use the MPLS entropy label, rather than to have each router compute the 
entropy based on an analysis of the next encapsulation header.

So I don't think BIER justifies the use of a new MPLS special purpose 
payload-protocol-identifier label.

There is one case though in which it could potentially be useful to 
enable the transit routers of a unicast MPLS tunnel to determine that a 
particular packet has a BIER payload.  Suppose thtat the MPLS TTL of the 
unicast tunnel expires while the packet is still in the tunnel.  It 
might be useful for the transit router to generate an ICMP response to 
the TTL expiration, and for this ICMP response to be BIER-aware. 
However, this is only likely to happen in a traceroute-like application, 
and I don't think that is sufficient justification for having all BIER 
packets carry the two or three extra label stack entries it would take 
to provide the special purpose payload-protocol-identifier label.  On 
the other hand, a nibble value specific to BIER might be useful, as it 
provides the same information without requiring additional overhead.


From nobody Tue Mar 17 10:38:06 2015
Return-Path: <antoni.przygienda@ericsson.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 902491A87B1; Tue, 17 Mar 2015 10:15:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 AJxE2RlsQV0N; Tue, 17 Mar 2015 10:15:38 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 094BA1A87AF; Tue, 17 Mar 2015 10:15:37 -0700 (PDT)
X-AuditID: c6180641-f790b6d000004359-2e-5507ffaa13a8
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id AE.2E.17241.AAFF7055; Tue, 17 Mar 2015 11:19:22 +0100 (CET)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.03.0210.002; Tue, 17 Mar 2015 13:15:31 -0400
From: Antoni Przygienda <antoni.przygienda@ericsson.com>
To: Xuxiaohu <xuxiaohu@huawei.com>, "stbryant@cisco.com" <stbryant@cisco.com>,  Eric C Rosen <erosen@juniper.net>, BIER <bier@ietf.org>
Thread-Topic: [Bier] Encapsulation first nibble
Thread-Index: AQHQXcZr1RiePFKtRU2KrQ7DzVhUo50bFkcAgAWxRoCAAAe/AIAAHlkA
Date: Tue, 17 Mar 2015 17:15:31 +0000
Message-ID: <2E4BB27CAB87BF43B4207C0E55860F1827D3C5@eusaamb103.ericsson.se>
References: <55033E87.3030305@juniper.net> <5503403E.4050304@cisco.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CB77@NKGEML512-MBS.china.huawei.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CBB2@NKGEML512-MBS.china.huawei.com>
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CBB2@NKGEML512-MBS.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.9]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrPLMWRmVeSWpSXmKPExsUyuXRPuO6q/+yhBtdPKFgsnbGHyWLdhg/M FreWrmS1ePJgK7vFuadzGC22nl/F6MDmMeX3RlaPliNvWT2WLPnJ5HG96Sp7AEsUl01Kak5m WWqRvl0CV8aOlZtZCzazVZzu2cvawNjB2sXIySEhYCKx5dxBJghbTOLCvfVsXYxcHEICRxgl Li2fzArhLGeUOHv/KVgVm4CFxOVvT5lBEiICHYwSSxZsAhvFLOAk0bD8MiOILSygJ3F+y2M2 EFtEQF9i+flrQDUcQLabxMmXASBhFgFVidkXn4O18gp4S5y8eY8FxBYSuM8o8e2NCojNKRAm cW3KPbC9jEDXfT+1hglilbjErSfzoa4WkFiy5zwzhC0q8fLxP6jPFCX29U9nh6jXkViw+xMb hK0tsWzha2aIvYISJ2c+YZnAKDYLydhZSFpmIWmZhaRlASPLKkaO0uLUstx0I8NNjMAYOybB 5riDccEny0OMAhyMSjy8BhrsoUKsiWXFlbmHGKU5WJTEecuuHAwREkhPLEnNTk0tSC2KLyrN SS0+xMjEwSnVwNh+/u+dSJcnBqp7Ug1Pp+zsV2tPyxZjYNm+c1nir5llJ331NJL6mbcyvYlp 22VuPX9u4obZJbqG4X45tqzPnZOMa1hz0n5dzPk7Vfl8gLHtnidMc986hCqLZTEfEBA4N0Xi 27Zl+bpJLOuPbEkKjj/U9Hpiy80T9/R6m+IPved0LO3blPSnXYmlOCPRUIu5qDgRAEt35GqS AgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/0OJzDV_giehGAt5S56skidNhuco>
X-Mailman-Approved-At: Tue, 17 Mar 2015 10:38:04 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] [Bier] Encapsulation first nibble
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 17 Mar 2015 17:15:39 -0000

Not being much of an encapsulation, data plane guy myself, I wonder a tad h=
ow hacky those 'heuristics' are.  Last label indicates clearly a BIER heade=
r is following. For the LSRs that do not support BIER and do not parse the =
BIER encaps there is no reason to look 'behind the label'.  Multiple sub-do=
mains allow for clean separation of traffic with different properties if ne=
eded and with that there is even less reason for some kind of 'heuristic' D=
PI

Now, given some 'heuristics' are in place no matter what value we put into =
the nibble, sooner or later we'll collide with it no matter what value we p=
ick since such 'heuristics' basically try to parse bits without understandi=
ng their context and with that can easily mistake an 'eye' for an 'I' or an=
 'aye'.=20

--- tony=20




From nobody Tue Mar 17 10:38:07 2015
Return-Path: <zzhang@juniper.net>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 663C11A87EF; Tue, 17 Mar 2015 10:36:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 vCuCcA_5rJ5L; Tue, 17 Mar 2015 10:35:58 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0777.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:777]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA21F1A87EB; Tue, 17 Mar 2015 10:35:57 -0700 (PDT)
Received: from BY2PR05MB079.namprd05.prod.outlook.com (10.242.38.16) by DM2PR0501MB1104.namprd05.prod.outlook.com (25.160.245.140) with Microsoft SMTP Server (TLS) id 15.1.106.15; Tue, 17 Mar 2015 17:35:41 +0000
Received: from BY2PR05MB079.namprd05.prod.outlook.com ([169.254.8.136]) by BY2PR05MB079.namprd05.prod.outlook.com ([169.254.8.136]) with mapi id 15.01.0106.007; Tue, 17 Mar 2015 17:35:40 +0000
From: "Zhaohui (Jeffrey) Zhang" <zzhang@juniper.net>
To: Antoni Przygienda <antoni.przygienda@ericsson.com>, Xuxiaohu <xuxiaohu@huawei.com>, "stbryant@cisco.com" <stbryant@cisco.com>, Eric Rosen <erosen@juniper.net>, BIER <bier@ietf.org>
Thread-Topic: [Bier] Encapsulation first nibble
Thread-Index: AQHQXcZsT/NTuReqcUafEPAn7P7Hmp0a0zkAgAWxRoCAAAe/AIAAZCaAgAABcAA=
Date: Tue, 17 Mar 2015 17:35:40 +0000
Message-ID: <BY2PR05MB079ACD3AE28CC48B48C789ED4030@BY2PR05MB079.namprd05.prod.outlook.com>
References: <55033E87.3030305@juniper.net> <5503403E.4050304@cisco.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CB77@NKGEML512-MBS.china.huawei.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CBB2@NKGEML512-MBS.china.huawei.com> <2E4BB27CAB87BF43B4207C0E55860F1827D3C5@eusaamb103.ericsson.se>
In-Reply-To: <2E4BB27CAB87BF43B4207C0E55860F1827D3C5@eusaamb103.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.10]
authentication-results: ericsson.com; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR0501MB1104;
x-microsoft-antispam-prvs: <DM2PR0501MB11049A0179253EB2CA95578CD4030@DM2PR0501MB1104.namprd05.prod.outlook.com>
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(377454003)(51704005)(13464003)(102836002)(122556002)(2950100001)(106116001)(2900100001)(99286002)(76576001)(62966003)(15975445007)(77156002)(93886004)(86362001)(40100003)(66066001)(92566002)(54356999)(76176999)(46102003)(33656002)(19580395003)(19580405001)(2656002)(74316001)(50986999)(2501003)(87936001); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR0501MB1104; H:BY2PR05MB079.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(5002010); SRVR:DM2PR0501MB1104; BCL:0; PCL:0; RULEID:; SRVR:DM2PR0501MB1104; 
x-forefront-prvs: 0518EEFB48
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Mar 2015 17:35:40.1862 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0501MB1104
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/vOHiaQ5eVod8Sdgo_A13pK9EsK0>
X-Mailman-Approved-At: Tue, 17 Mar 2015 10:38:04 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] [Bier] Encapsulation first nibble
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 17 Mar 2015 17:36:00 -0000

Today those "heuristics" are typically used in very specific deployments wh=
ere an operator knows well what kind of traffic is going through their MPLS=
 infrastructure.

As Eric mentioned in the other message, a nibble value specific to BIER mig=
ht be useful for other purpose than ECMP entropy, and if such a value is st=
andardized (like value 0 and 1 that are reserved for PWs), then it helps re=
duce the clashing with random/hacky heuristics usages.

Jeffrey

> -----Original Message-----
> From: BIER [mailto:bier-bounces@ietf.org] On Behalf Of Antoni Przygienda
> Sent: Tuesday, March 17, 2015 1:16 PM
> To: Xuxiaohu; stbryant@cisco.com; Eric Rosen; BIER
> Cc: mpls@ietf.org; sfc@ietf.org
> Subject: Re: [Bier] Encapsulation first nibble
>=20
> Not being much of an encapsulation, data plane guy myself, I wonder a tad
> how hacky those 'heuristics' are.  Last label indicates clearly a BIER
> header is following. For the LSRs that do not support BIER and do not
> parse the BIER encaps there is no reason to look 'behind the label'.
> Multiple sub-domains allow for clean separation of traffic with different
> properties if needed and with that there is even less reason for some kin=
d
> of 'heuristic' DPI
>=20
> Now, given some 'heuristics' are in place no matter what value we put int=
o
> the nibble, sooner or later we'll collide with it no matter what value we
> pick since such 'heuristics' basically try to parse bits without
> understanding their context and with that can easily mistake an 'eye' for
> an 'I' or an 'aye'.
>=20
> --- tony
>=20
>=20
>=20
> _______________________________________________
> BIER mailing list
> BIER@ietf.org
> https://www.ietf.org/mailman/listinfo/bier


From nobody Tue Mar 17 10:42:08 2015
Return-Path: <antoni.przygienda@ericsson.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEDCF1A882A; Tue, 17 Mar 2015 10:38:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 dEd_kA3DMJZt; Tue, 17 Mar 2015 10:38:30 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2456D1A87F2; Tue, 17 Mar 2015 10:38:30 -0700 (PDT)
X-AuditID: c6180641-f790b6d000004359-b8-5508050a07d4
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id C7.BF.17241.A0508055; Tue, 17 Mar 2015 11:42:19 +0100 (CET)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.03.0210.002; Tue, 17 Mar 2015 13:38:28 -0400
From: Antoni Przygienda <antoni.przygienda@ericsson.com>
To: "Zhaohui (Jeffrey) Zhang" <zzhang@juniper.net>, Xuxiaohu <xuxiaohu@huawei.com>, "stbryant@cisco.com" <stbryant@cisco.com>, Eric Rosen <erosen@juniper.net>, BIER <bier@ietf.org>
Thread-Topic: [Bier] Encapsulation first nibble
Thread-Index: AQHQXcZr1RiePFKtRU2KrQ7DzVhUo50bFkcAgAWxRoCAAAe/AIAAHlkAgABLbgD//7070A==
Date: Tue, 17 Mar 2015 17:38:28 +0000
Message-ID: <2E4BB27CAB87BF43B4207C0E55860F1827D438@eusaamb103.ericsson.se>
References: <55033E87.3030305@juniper.net> <5503403E.4050304@cisco.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CB77@NKGEML512-MBS.china.huawei.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CBB2@NKGEML512-MBS.china.huawei.com> <2E4BB27CAB87BF43B4207C0E55860F1827D3C5@eusaamb103.ericsson.se> <BY2PR05MB079ACD3AE28CC48B48C789ED4030@BY2PR05MB079.namprd05.prod.outlook.com>
In-Reply-To: <BY2PR05MB079ACD3AE28CC48B48C789ED4030@BY2PR05MB079.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.9]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmphkeLIzCtJLcpLzFFi42KZXLonXJeblSPUYN90foulM/YwWazb8IHZ 4tbSlawWTx5sZbc493QOo8XW86sYLY5cbGRxYPeY8nsjq0fLkbesHkuW/GTyuN50lT2AJYrL JiU1J7MstUjfLoErY/vTA6wFm9kr7s7YydjA+J+1i5GTQ0LAROLn34NsELaYxIV764FsLg4h gSOMEkfnXYFyljNKTF5wgxGkik3AQuLyt6fMIAkRgR2MEu/PrmUHSTALOEk0LL8MViQsoCdx fstjsLEiAvoSy89fY4WwwyS+XrwIVMPBwSKgKtGwSwMkzCvgLfFr7jSoZZ+YJK5dO8kGUsMp EC3RcjYSpIYR6Lrvp9YwQawSl7j1ZD4TxNUCEkv2nGeGsEUlXj7+B/WZosS+/ulQp+lILNj9 iQ3C1pZYtvA1M8ReQYmTM5+wTGAUm4Vk7CwkLbOQtMxC0rKAkWUVI0dpcWpZbrqR4SZGYLQd k2Bz3MG44JPlIUYBDkYlHl4DDfZQIdbEsuLK3EOM0hwsSuK8ZVcOhggJpCeWpGanphakFsUX leakFh9iZOLglGpgDDRSPb1iX/nu+mC+fQqbPFN0OTkClDRnSlyw51u3TbDirprP1yentrJN 2uo36ZNg0jHmDF5zhrX/u84J1Yc/il57s3cHq8cKTm4+w9RDzmdfuxedTI5ktg1NNtUwr3t3 PPWI5p1J3LcjpVh82c8vla48uefrRbMLr14I3J63cukBTzde6YZPSizFGYmGWsxFxYkAJF0u ppcCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/bY8YZI_d5gGej5kGN8ThVwOdXw0>
X-Mailman-Approved-At: Tue, 17 Mar 2015 10:42:06 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] [Bier] Encapsulation first nibble
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 17 Mar 2015 17:38:32 -0000

Ok, point taken (as are the ECMP/ICMP things that Eric mentioned). I'll wat=
ch from the bleachers the data plane fireworks then  ;-)=20

--- tony=20

> -----Original Message-----
> From: Zhaohui (Jeffrey) Zhang [mailto:zzhang@juniper.net]
> Sent: Tuesday, March 17, 2015 10:36 AM
> To: Antoni Przygienda; Xuxiaohu; stbryant@cisco.com; Eric Rosen; BIER
> Cc: mpls@ietf.org; sfc@ietf.org
> Subject: RE: [Bier] Encapsulation first nibble
>=20
> Today those "heuristics" are typically used in very specific deployments =
where an
> operator knows well what kind of traffic is going through their MPLS
> infrastructure.
>=20
> As Eric mentioned in the other message, a nibble value specific to BIER m=
ight be
> useful for other purpose than ECMP entropy, and if such a value is standa=
rdized
> (like value 0 and 1 that are reserved for PWs), then it helps reduce the =
clashing
> with random/hacky heuristics usages.
>=20


From nobody Tue Mar 17 10:45:42 2015
Return-Path: <gregory.mirsky@ericsson.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE9471A8828; Tue, 17 Mar 2015 10:45:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.201
X-Spam-Level: 
X-Spam-Status: No, score=-104.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 fsrgUYJDDiCR; Tue, 17 Mar 2015 10:45:37 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 225FE1A00F4; Tue, 17 Mar 2015 10:45:37 -0700 (PDT)
X-AuditID: c618062d-f79686d0000030a8-01-550812dfb6f3
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id C1.BE.12456.FD218055; Tue, 17 Mar 2015 12:41:19 +0100 (CET)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.03.0210.002; Tue, 17 Mar 2015 13:45:35 -0400
From: Gregory Mirsky <gregory.mirsky@ericsson.com>
To: Antoni Przygienda <antoni.przygienda@ericsson.com>, Xuxiaohu <xuxiaohu@huawei.com>, "stbryant@cisco.com" <stbryant@cisco.com>, "Eric C Rosen" <erosen@juniper.net>, BIER <bier@ietf.org>
Thread-Topic: [Bier] Encapsulation first nibble
Thread-Index: AQHQXcZrqojq7Dn2dkqRctiyZ05xTp0aTR0AgAY0PqCAAAkpwIAAqO6A///CXeA=
Date: Tue, 17 Mar 2015 17:45:35 +0000
Message-ID: <7347100B5761DC41A166AC17F22DF1121B92F9DC@eusaamb103.ericsson.se>
References: <55033E87.3030305@juniper.net> <5503403E.4050304@cisco.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CB77@NKGEML512-MBS.china.huawei.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CBB2@NKGEML512-MBS.china.huawei.com> <2E4BB27CAB87BF43B4207C0E55860F1827D3C5@eusaamb103.ericsson.se>
In-Reply-To: <2E4BB27CAB87BF43B4207C0E55860F1827D3C5@eusaamb103.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.10]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpgkeLIzCtJLcpLzFFi42KZXLonQfe+EEeowb1/ehZLZ+xhsli34QOz xa2lK1ktnjzYym5x7ukcRout51cxOrB5TPm9kdWj5chbVo8lS34yeVxvusoewBLFZZOSmpNZ llqkb5fAlXHy6BaWgt98Fben/GBrYJzC08XIySEhYCLxa+0SJghbTOLCvfVsXYxcHEICRxgl Tu76zw7hLGeUuDTxPAtIFZuAkcSLjT1gCRGBA4wSnUcegyWYBZwkGpZfZgSxhQX0JM5vecwG YosI6EssP3+NFcL2k3jQdhGsnkVAVeLPkj9Agzg4eAV8JbqOV0IsW8gk8Wn7ObAaTgEfief9 x8BsRqDzvp9awwSxS1zi1pP5UGcLSCzZc54ZwhaVePn4HyuErSQxaek5Voh6HYkFuz+xQdja EssWvgar5xUQlDg58wnLBEaxWUjGzkLSMgtJyywkLQsYWVYxcpQWp5blphsZbGIERtkxCTbd HYx7XloeYhTgYFTi4TXQYA8VYk0sK67MPcQozcGiJM676MHBECGB9MSS1OzU1ILUovii0pzU 4kOMTBycUg2MbdxapbyZO84WLDxWfm+z1pZokfuWX6sVGYQ+b775MVanYdePnQxbOr5LZyic 0tiQ9tf25j6R5ayK2uzCNcV/fvr8UO35vvjxx7mnnzxoSbp5odPN8EmqxAbmkon3FNlOW66b r2xfW/vm1F1GGWXtG6tfJbu2Nt5n/tB4RYw5g7M7dqqOc+B/JZbijERDLeai4kQAxZFq9JMC AAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/bIN2PwwBPar5wikfEc10u9ZsqQs>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] [Bier] Encapsulation first nibble
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 17 Mar 2015 17:45:39 -0000

Hi Tony,
as Eric pointed, the potential problem is with non-BIER LSRs and all BIER L=
SRs do interpret BIER application label. Thus non-BIER transit LSR may look=
 past the label stack to balance flows across available ECMP. And if the ve=
ry first nibble is 0x04 or 0x06 (which may happen for Destination MAC as di=
scussed in EVPN scenarios), the LSR will interpret the packet as IPv4 or IP=
v6 respectively and thus potentially cause out-of-order packets within the =
same flow resulting from the hashing on something which is not IP 5 tuple.
Another possible solution, IMHO, may be use of PWMCW as discussed in Sectio=
n Frame Ordering RFC 7432.

	Regards,
		Greg

-----Original Message-----
From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Antoni Przygienda
Sent: Tuesday, March 17, 2015 10:16 AM
To: Xuxiaohu; stbryant@cisco.com; Eric C Rosen; BIER
Cc: mpls@ietf.org; sfc@ietf.org
Subject: Re: [mpls] [Bier] Encapsulation first nibble

Not being much of an encapsulation, data plane guy myself, I wonder a tad h=
ow hacky those 'heuristics' are.  Last label indicates clearly a BIER heade=
r is following. For the LSRs that do not support BIER and do not parse the =
BIER encaps there is no reason to look 'behind the label'.  Multiple sub-do=
mains allow for clean separation of traffic with different properties if ne=
eded and with that there is even less reason for some kind of 'heuristic' D=
PI

Now, given some 'heuristics' are in place no matter what value we put into =
the nibble, sooner or later we'll collide with it no matter what value we p=
ick since such 'heuristics' basically try to parse bits without understandi=
ng their context and with that can easily mistake an 'eye' for an 'I' or an=
 'aye'.=20

--- tony=20



_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From nobody Tue Mar 17 14:44:19 2015
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83DD11A8903; Tue, 17 Mar 2015 14:44:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.422
X-Spam-Level: 
X-Spam-Status: No, score=-1.422 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CN_BODY_35=0.339, 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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UHvIYe9W9ZZ1; Tue, 17 Mar 2015 14:44:13 -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 487541A1B6B; Tue, 17 Mar 2015 14:44:12 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BTT69516; Tue, 17 Mar 2015 21:44:10 +0000 (GMT)
Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 17 Mar 2015 21:44:09 +0000
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.209]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.03.0158.001; Wed, 18 Mar 2015 05:44:04 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Eric C Rosen <erosen@juniper.net>, "stbryant@cisco.com" <stbryant@cisco.com>, BIER <bier@ietf.org>
Thread-Topic: [Bier] Encapsulation first nibble
Thread-Index: AQHQXcZrqojq7Dn2dkqRctiyZ05xTp0aTR0AgAY0PqCAAAkpwP//3oUAgADIuWA=
Date: Tue, 17 Mar 2015 21:44:03 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CCD2@NKGEML512-MBS.china.huawei.com>
References: <55033E87.3030305@juniper.net> <5503403E.4050304@cisco.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CB77@NKGEML512-MBS.china.huawei.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CBB2@NKGEML512-MBS.china.huawei.com> <55086028.1070004@juniper.net>
In-Reply-To: <55086028.1070004@juniper.net>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.74.115]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/gtzNqG5NBy_4m3mps7z1sSM5q-c>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] [Bier] Encapsulation first nibble
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 17 Mar 2015 21:44:15 -0000

SGkgRXJpYywNCg0KVGhhbmtzIGEgbG90IGZvciB5b3VyIHJlc3BvbnNlLiBQbGVhc2Ugc2VlIG15
IHJlc3BvbnNlIGlubGluZS4NCg0KPiAtLS0tLdPKvP7Urbz+LS0tLS0NCj4gt6K8/sjLOiBFcmlj
IEMgUm9zZW4gW21haWx0bzplcm9zZW5AanVuaXBlci5uZXRdDQo+ILeiy83KsbzkOiAyMDE1xOoz
1MIxOMjVIDE6MTENCj4gytW8/sjLOiBYdXhpYW9odTsgc3RicnlhbnRAY2lzY28uY29tOyBCSUVS
DQo+ILOty806IGVyb3NlbkBqdW5pcGVyLm5ldDsgbXBsc0BpZXRmLm9yZzsgc2ZjQGlldGYub3Jn
DQo+INb3zOI6IFJlOiBbQmllcl0gRW5jYXBzdWxhdGlvbiBmaXJzdCBuaWJibGUNCj4gDQo+IE9u
IDMvMTcvMjAxNSA3OjE3IEFNLCBYdXhpYW9odSB3cm90ZToNCj4gPiBBbm90aGVyIHdheSBpcyB0
byBhZGQgYSBwcm90b2NvbCBpZGVudGlmaWVyIGZpZWxkIGFmdGVyIHRoZSBib3R0b20gb2YNCj4g
PiB0aGUgbGFiZWwgc3RhY2sNCj4gPiAoaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0
LXh1LW1wbHMtcGF5bG9hZC1wcm90b2NvbC1pZGVudGlmaWVyLTAwKS4NCj4gPiBJbiB0aGlzIHdh
eSwgd2Ugd291bGQgbm90IGJlIGJvdGhlcmVkIGFib3V0IHRoZSBuaWJibGUgaXNzdWUgYW55bW9y
ZQ0KPiA+IHdoZW4gcHJvcG9zaW5nIGFueSBuZXcgZW5jYXBzdWxhdGlvbiBoZWFkZXIgd2hpY2gg
bWF5IGJlIGVuY2Fwc3VsYXRlZA0KPiA+IHdpdGhpbiBhbiBNUExTIHBhY2tldC4NCj4gDQo+IFdo
ZW4gYSBCSUVSIHBhY2tldCBpcyB0cmF2ZWxpbmcgZnJvbSBCRklSIHRvIEJGRVIgdmlhIGEgc2Vx
dWVuY2Ugb2YgZGlyZWN0bHkNCj4gY29ubmVjdGVkIEJGUnMsIGVhY2ggQkZSIGFscmVhZHkga25v
d3MsIHZpYSB0aGUgYm90dG9tIGxhYmVsLCB0aGF0IHRoZSBwYWNrZXQNCj4gaXMgYSBCSUVSIHBh
Y2tldC4gIFRoZSBuaWJibGUgaXNzdWUgcmVhbGx5IG9ubHkgbWF0dGVycyB3aGVuIGEgQklFUiBw
YWNrZXQgaXMNCj4gdHJhdmVsaW5nIHRocm91Z2ggYSBub24tQklFUiB0dW5uZWwuDQoNCj4gV2hl
biBhIEJJRVIgcGFja2V0IGlzIHRyYXZlbGluZyB0aHJvdWdoIGEgbm9uLUJJRVIgdHVubmVsLCBz
b21lIG9mIHRoZSB0cmFuc2l0DQo+IHJvdXRlcnMgbWF5IGJlIHJvdXRlcnMgdGhhdCBhcmUgcnVu
bmluZyBvbGRlciBzb2Z0d2FyZS4gIFRoZXkgd2lsbCBiYXNlIHRoZWlyDQo+IEVDTVAgdHJlYXRt
ZW50IG9mIHRoZSBwYWNrZXQgb24gdGhlIGZpcnN0IG5pYmJsZS4gIEEgcHJvdG9jb2wgaWRlbnRp
ZmllciBmaWVsZA0KPiB3b24ndCBoZWxwLCBiZWNhdXNlIHRoZXNlIG9sZCByb3V0ZXJzIHdvbid0
IHVuZGVyc3RhbmQgaXQuICBGb3IgbmV3ZXIgcm91dGVycywNCg0KU2luY2UgdGhlIG5pYmJsZSBp
bW1lZGlhdGVseSBhZnRlciB0aGUgUHJvdG9jb2wgSWRlbnRpZmllciBMYWJlbCAoUElMKSB3aGlj
aCBpcyBhdCB0aGUgYm90dG9tIG9mIHRoZSBsYWJlbCBzdGFjayBpcyBzZXQgdG8gemVybywgdGhv
c2Ugb2xkIHJvdXRlcnMgd291bGQgbm90IGludGVycHJldGVkIHRob3NlIHBhY2tldHMgY29udGFp
bmluZyBhIHByb3RvY29sIGlkIGZpZWxkIGFzIElQIHBhY2tldHMuIE9mIGNvdXJzZSwgaWYgdGhl
IE1QTFMgcGF5bG9hZCBpcyBhbiBJUCBwYWNrZXQsIGl0IGNvdWxkIGJlIGVuY2Fwc3VsYXRlZCBh
cyBiZWZvcmUgKGkuZS4sIHcvbyB0aGUgcHJvdG9jb2wgaWQgZmllbGQpIC4gSW4gb3RoZXIgd29y
ZHMsIHRoZSBwcm90b2NvbCBpZCBmaWVsZCBjb3VsZCBiZSBhcHBsaWNhYmxlIHRvIG5ldyBwYXls
b2FkIHR5cGVzIHRpbGwgdGhvc2Ugb2xkIHJvdXRlcnMgaGF2ZSBkaXNhcHBlYXJlZCBmcm9tIHRo
ZSBuZXR3b3JrLg0KDQo+IEkgdGhpbmsgdGhlIHByb3BlciBkaXJlY3Rpb24gaXMgdG8gdXNlIHRo
ZSBNUExTIGVudHJvcHkgbGFiZWwsIHJhdGhlciB0aGFuIHRvDQo+IGhhdmUgZWFjaCByb3V0ZXIg
Y29tcHV0ZSB0aGUgZW50cm9weSBiYXNlZCBvbiBhbiBhbmFseXNpcyBvZiB0aGUgbmV4dA0KPiBl
bmNhcHN1bGF0aW9uIGhlYWRlci4NCj4gDQo+IFNvIEkgZG9uJ3QgdGhpbmsgQklFUiBqdXN0aWZp
ZXMgdGhlIHVzZSBvZiBhIG5ldyBNUExTIHNwZWNpYWwgcHVycG9zZQ0KPiBwYXlsb2FkLXByb3Rv
Y29sLWlkZW50aWZpZXIgbGFiZWwuDQoNClRoZSByZWFzb24gdGhhdCBJIG1lbnRpb25lZCB0aGF0
IGFwcHJvYWNoIGlzOiBmb3Igd2hhdGV2ZXIgbmV3IGVuY2Fwc3VsYXRpb24gaGVhZGVyIChlLmcu
LCBCSUVSLCBOU0gsLi4uKSwgYXMgbG9uZyBhcyBpdCBoYXMgdGhlIHBvc3NpYmlsaXR5IG9mIGJl
aW5nIGVuY2Fwc3VsYXRlZCB3aXRoaW4gYW4gTVBMUyBwYWNrZXQsIHdlIHdvdWxkIGhhdmUgdG8g
YWRkcmVzcyB0aGUgbmliYmxlIGlzc3VlIHdoZW4gZGVzaWduaW5nIHRoYXQgbmV3IGVuY2Fwc3Vs
YXRpb24gaGVhZGVyLiBJIHdvbmRlciB3aHkgbm90IHRoZSBNUExTIGl0c2VsZiBmaXhlcyBpdHMg
b3duIGRyYXdiYWNrIChpLmUuLCB0aGUgbGFjayBvZiB0aGUgcHJvdG9jb2wgZmllbGQpIHNvIGFz
IHRvIGVsaW1pbmF0ZSBzdWNoIGJvdGhlciBmb3JldmVyLiBJbiBhZGRpdGlvbiwgaXQgY291bGQg
ZnVydGhlciBlbGltaW5hdGUgdGhlIG5lZWQgZm9yIGFsbG9jYXRpbmcgYW5kIGFkdmVydGlzaW5n
IGxhYmVscyBmb3IgaW5kaWNhdGluZyB0aGVzZSBuZXcgTVBMUyBwYXlsb2FkIHR5cGVzLiBGb3Ig
ZXhhbXBsZSwgYXNzdW1lIHRoZSBOU0ggaXMgdG8gYmUgZW5jYXBzdWxhdGVkIHdpdGhpbiBhbiBN
UExTIHBhY2tldCwgdGhlIGVncmVzcyB3b3VsZCBoYXZlIHRvIGFsbG9jYXRlIGFuZCBhZHZlcnRp
c2UgYW4gYXBwbGljYXRpb24gbGFiZWwgZm9yIHRoZSBOU0gtZW5jYXBzdWxhdGVkIHBhY2tldCwg
anVzdCBhcyB3aGF0IHRoZSBNUExTLUJJRVIgbGFiZWwgZG9lcy4gT2YgY291cnNlLCB0aGUgTVBM
Uy1CSUVSIGxhYmVsIGNvdWxkIGJlIHVzZWQgdG8gZXh0cmFjdCBvdGhlciBCSUVSIHJlbGF0ZWQg
aW5mbyBiZXNpZGVzIHRoZSBwYXlsb2FkIHR5cGUgaW5mby4NCg0KQmVzdCByZWdhcmRzLA0KWGlh
b2h1DQoNCj4gVGhlcmUgaXMgb25lIGNhc2UgdGhvdWdoIGluIHdoaWNoIGl0IGNvdWxkIHBvdGVu
dGlhbGx5IGJlIHVzZWZ1bCB0byBlbmFibGUgdGhlDQo+IHRyYW5zaXQgcm91dGVycyBvZiBhIHVu
aWNhc3QgTVBMUyB0dW5uZWwgdG8gZGV0ZXJtaW5lIHRoYXQgYSBwYXJ0aWN1bGFyIHBhY2tldA0K
PiBoYXMgYSBCSUVSIHBheWxvYWQuICBTdXBwb3NlIHRodGF0IHRoZSBNUExTIFRUTCBvZiB0aGUg
dW5pY2FzdCB0dW5uZWwgZXhwaXJlcw0KPiB3aGlsZSB0aGUgcGFja2V0IGlzIHN0aWxsIGluIHRo
ZSB0dW5uZWwuICBJdCBtaWdodCBiZSB1c2VmdWwgZm9yIHRoZSB0cmFuc2l0IHJvdXRlcg0KPiB0
byBnZW5lcmF0ZSBhbiBJQ01QIHJlc3BvbnNlIHRvIHRoZSBUVEwgZXhwaXJhdGlvbiwgYW5kIGZv
ciB0aGlzIElDTVANCj4gcmVzcG9uc2UgdG8gYmUgQklFUi1hd2FyZS4NCj4gSG93ZXZlciwgdGhp
cyBpcyBvbmx5IGxpa2VseSB0byBoYXBwZW4gaW4gYSB0cmFjZXJvdXRlLWxpa2UgYXBwbGljYXRp
b24sIGFuZCBJIGRvbid0DQo+IHRoaW5rIHRoYXQgaXMgc3VmZmljaWVudCBqdXN0aWZpY2F0aW9u
IGZvciBoYXZpbmcgYWxsIEJJRVIgcGFja2V0cyBjYXJyeSB0aGUgdHdvIG9yDQo+IHRocmVlIGV4
dHJhIGxhYmVsIHN0YWNrIGVudHJpZXMgaXQgd291bGQgdGFrZSB0byBwcm92aWRlIHRoZSBzcGVj
aWFsIHB1cnBvc2UNCj4gcGF5bG9hZC1wcm90b2NvbC1pZGVudGlmaWVyIGxhYmVsLiAgT24gdGhl
IG90aGVyIGhhbmQsIGEgbmliYmxlIHZhbHVlIHNwZWNpZmljIHRvDQo+IEJJRVIgbWlnaHQgYmUg
dXNlZnVsLCBhcyBpdCBwcm92aWRlcyB0aGUgc2FtZSBpbmZvcm1hdGlvbiB3aXRob3V0IHJlcXVp
cmluZw0KPiBhZGRpdGlvbmFsIG92ZXJoZWFkLg0KDQo=


From nobody Tue Mar 17 14:51:38 2015
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DAD81A8913; Tue, 17 Mar 2015 14:51:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.078
X-Spam-Level: **
X-Spam-Status: No, score=2.078 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339, MIME_8BIT_HEADER=0.3, 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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mnzciB377abU; Tue, 17 Mar 2015 14:51: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 502661A890F; Tue, 17 Mar 2015 14:51:32 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BQI95861; Tue, 17 Mar 2015 21:51:30 +0000 (GMT)
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 17 Mar 2015 21:51:29 +0000
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.209]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.03.0158.001; Wed, 18 Mar 2015 05:51:22 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: "Zhaohui (Jeffrey) Zhang" <zzhang@juniper.net>, Antoni Przygienda <antoni.przygienda@ericsson.com>, "stbryant@cisco.com" <stbryant@cisco.com>, Eric Rosen <erosen@juniper.net>, BIER <bier@ietf.org>
Thread-Topic: [Bier] Encapsulation first nibble
Thread-Index: AQHQXcZrqojq7Dn2dkqRctiyZ05xTp0aTR0AgAY0PqCAAAkpwP//38SAgAAFoQCAAM2HIA==
Date: Tue, 17 Mar 2015 21:51:21 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CCE9@NKGEML512-MBS.china.huawei.com>
References: <55033E87.3030305@juniper.net> <5503403E.4050304@cisco.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CB77@NKGEML512-MBS.china.huawei.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CBB2@NKGEML512-MBS.china.huawei.com> <2E4BB27CAB87BF43B4207C0E55860F1827D3C5@eusaamb103.ericsson.se> <BY2PR05MB079ACD3AE28CC48B48C789ED4030@BY2PR05MB079.namprd05.prod.outlook.com>
In-Reply-To: <BY2PR05MB079ACD3AE28CC48B48C789ED4030@BY2PR05MB079.namprd05.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.74.115]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/Q1W2xabqD1rZY7YQfQAYfUEWimc>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>
Subject: [sfc] =?gb2312?b?tPC4tDogW0JpZXJdIEVuY2Fwc3VsYXRpb24gZmlyc3Qgbmli?= =?gb2312?b?Ymxl?=
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 17 Mar 2015 21:51:34 -0000

SGkgSmVmZnJleSwNCg0KPiAtLS0tLdPKvP7Urbz+LS0tLS0NCj4gt6K8/sjLOiBaaGFvaHVpIChK
ZWZmcmV5KSBaaGFuZyBbbWFpbHRvOnp6aGFuZ0BqdW5pcGVyLm5ldF0NCj4gt6LLzcqxvOQ6IDIw
MTXE6jPUwjE4yNUgMTozNg0KPiDK1bz+yMs6IEFudG9uaSBQcnp5Z2llbmRhOyBYdXhpYW9odTsg
c3RicnlhbnRAY2lzY28uY29tOyBFcmljIFJvc2VuOyBCSUVSDQo+ILOty806IG1wbHNAaWV0Zi5v
cmc7IHNmY0BpZXRmLm9yZw0KPiDW98ziOiBSRTogW0JpZXJdIEVuY2Fwc3VsYXRpb24gZmlyc3Qg
bmliYmxlDQo+IA0KPiBUb2RheSB0aG9zZSAiaGV1cmlzdGljcyIgYXJlIHR5cGljYWxseSB1c2Vk
IGluIHZlcnkgc3BlY2lmaWMgZGVwbG95bWVudHMgd2hlcmUNCj4gYW4gb3BlcmF0b3Iga25vd3Mg
d2VsbCB3aGF0IGtpbmQgb2YgdHJhZmZpYyBpcyBnb2luZyB0aHJvdWdoIHRoZWlyIE1QTFMNCj4g
aW5mcmFzdHJ1Y3R1cmUuDQo+IA0KPiBBcyBFcmljIG1lbnRpb25lZCBpbiB0aGUgb3RoZXIgbWVz
c2FnZSwgYSBuaWJibGUgdmFsdWUgc3BlY2lmaWMgdG8gQklFUiBtaWdodA0KPiBiZSB1c2VmdWwg
Zm9yIG90aGVyIHB1cnBvc2UgdGhhbiBFQ01QIGVudHJvcHksIGFuZCBpZiBzdWNoIGEgdmFsdWUg
aXMNCj4gc3RhbmRhcmRpemVkIChsaWtlIHZhbHVlIDAgYW5kIDEgdGhhdCBhcmUgcmVzZXJ2ZWQg
Zm9yIFBXcyksIHRoZW4gaXQgaGVscHMgcmVkdWNlDQo+IHRoZSBjbGFzaGluZyB3aXRoIHJhbmRv
bS9oYWNreSBoZXVyaXN0aWNzIHVzYWdlcy4NCg0KRm9sbG93aW5nIHN1Y2ggbG9naWMgKGkuZS4s
IGFzc2lnbiBhIG5pYmJsZSB2YWx1ZSBzcGVjaWZpYyB0byB0aGUgbmV3IGVuY2Fwc3VsYXRpb24g
aGVhZGVyKSwgd2Ugd291bGQgaGF2ZSB0byBjb25zaWRlciBob3cgbWFueSBhdmFpbGFibGUgbmli
YmxlIHZhbHVlcyBhcmUgdGhlcmUgd2hpY2ggY2FuIGJlIHVzZWQgZm9yIGZ1dHVyZSBlbmNhcHN1
bGF0aW9uIGhlYWRlcnMgaW4gdGhlIHNhbWUgd2F5Lg0KDQpCZXN0IHJlZ2FyZHMsDQpYaWFvaHUN
Cg0KPiBKZWZmcmV5DQo+IA0KPiA+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+ID4gRnJv
bTogQklFUiBbbWFpbHRvOmJpZXItYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIEFudG9u
aQ0KPiA+IFByenlnaWVuZGENCj4gPiBTZW50OiBUdWVzZGF5LCBNYXJjaCAxNywgMjAxNSAxOjE2
IFBNDQo+ID4gVG86IFh1eGlhb2h1OyBzdGJyeWFudEBjaXNjby5jb207IEVyaWMgUm9zZW47IEJJ
RVINCj4gPiBDYzogbXBsc0BpZXRmLm9yZzsgc2ZjQGlldGYub3JnDQo+ID4gU3ViamVjdDogUmU6
IFtCaWVyXSBFbmNhcHN1bGF0aW9uIGZpcnN0IG5pYmJsZQ0KPiA+DQo+ID4gTm90IGJlaW5nIG11
Y2ggb2YgYW4gZW5jYXBzdWxhdGlvbiwgZGF0YSBwbGFuZSBndXkgbXlzZWxmLCBJIHdvbmRlciBh
DQo+ID4gdGFkIGhvdyBoYWNreSB0aG9zZSAnaGV1cmlzdGljcycgYXJlLiAgTGFzdCBsYWJlbCBp
bmRpY2F0ZXMgY2xlYXJseSBhDQo+ID4gQklFUiBoZWFkZXIgaXMgZm9sbG93aW5nLiBGb3IgdGhl
IExTUnMgdGhhdCBkbyBub3Qgc3VwcG9ydCBCSUVSIGFuZCBkbw0KPiA+IG5vdCBwYXJzZSB0aGUg
QklFUiBlbmNhcHMgdGhlcmUgaXMgbm8gcmVhc29uIHRvIGxvb2sgJ2JlaGluZCB0aGUgbGFiZWwn
Lg0KPiA+IE11bHRpcGxlIHN1Yi1kb21haW5zIGFsbG93IGZvciBjbGVhbiBzZXBhcmF0aW9uIG9m
IHRyYWZmaWMgd2l0aA0KPiA+IGRpZmZlcmVudCBwcm9wZXJ0aWVzIGlmIG5lZWRlZCBhbmQgd2l0
aCB0aGF0IHRoZXJlIGlzIGV2ZW4gbGVzcyByZWFzb24NCj4gPiBmb3Igc29tZSBraW5kIG9mICdo
ZXVyaXN0aWMnIERQSQ0KPiA+DQo+ID4gTm93LCBnaXZlbiBzb21lICdoZXVyaXN0aWNzJyBhcmUg
aW4gcGxhY2Ugbm8gbWF0dGVyIHdoYXQgdmFsdWUgd2UgcHV0DQo+ID4gaW50byB0aGUgbmliYmxl
LCBzb29uZXIgb3IgbGF0ZXIgd2UnbGwgY29sbGlkZSB3aXRoIGl0IG5vIG1hdHRlciB3aGF0DQo+
ID4gdmFsdWUgd2UgcGljayBzaW5jZSBzdWNoICdoZXVyaXN0aWNzJyBiYXNpY2FsbHkgdHJ5IHRv
IHBhcnNlIGJpdHMNCj4gPiB3aXRob3V0IHVuZGVyc3RhbmRpbmcgdGhlaXIgY29udGV4dCBhbmQg
d2l0aCB0aGF0IGNhbiBlYXNpbHkgbWlzdGFrZQ0KPiA+IGFuICdleWUnIGZvciBhbiAnSScgb3Ig
YW4gJ2F5ZScuDQo+ID4NCj4gPiAtLS0gdG9ueQ0KPiA+DQo+ID4NCj4gPg0KPiA+IF9fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+ID4gQklFUiBtYWlsaW5n
IGxpc3QNCj4gPiBCSUVSQGlldGYub3JnDQo+ID4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby9iaWVyDQo=


From nobody Wed Mar 18 07:01:13 2015
Return-Path: <zzhang@juniper.net>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A96EA1A01EC; Wed, 18 Mar 2015 06:52:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 R1DrSGpHGGlH; Wed, 18 Mar 2015 06:52:50 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0787.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::787]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A928A1A019B; Wed, 18 Mar 2015 06:52:49 -0700 (PDT)
Received: from BY2PR05MB079.namprd05.prod.outlook.com (10.242.38.16) by CY1PR0501MB1098.namprd05.prod.outlook.com (25.160.144.140) with Microsoft SMTP Server (TLS) id 15.1.112.16; Wed, 18 Mar 2015 13:52:31 +0000
Received: from BY2PR05MB079.namprd05.prod.outlook.com ([169.254.8.136]) by BY2PR05MB079.namprd05.prod.outlook.com ([169.254.8.136]) with mapi id 15.01.0106.007; Wed, 18 Mar 2015 13:52:30 +0000
From: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>
To: Xuxiaohu <xuxiaohu@huawei.com>, Antoni Przygienda <antoni.przygienda@ericsson.com>, "stbryant@cisco.com" <stbryant@cisco.com>, Eric Rosen <erosen@juniper.net>, BIER <bier@ietf.org>, IJsbrand Wijnands <ice@cisco.com>
Thread-Topic: [Bier] Encapsulation first nibble
Thread-Index: AQHQXcZsT/NTuReqcUafEPAn7P7Hmp0a0zkAgAWxRoCAAAe/AIAAZCaAgAABcACAAEuhgIABB5lw
Date: Wed, 18 Mar 2015 13:52:30 +0000
Message-ID: <BY2PR05MB07904EDBB62DAF1E826E107D4000@BY2PR05MB079.namprd05.prod.outlook.com>
References: <55033E87.3030305@juniper.net> <5503403E.4050304@cisco.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CB77@NKGEML512-MBS.china.huawei.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CBB2@NKGEML512-MBS.china.huawei.com> <2E4BB27CAB87BF43B4207C0E55860F1827D3C5@eusaamb103.ericsson.se> <BY2PR05MB079ACD3AE28CC48B48C789ED4030@BY2PR05MB079.namprd05.prod.outlook.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CCE9@NKGEML512-MBS.china.huawei.com>
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CCE9@NKGEML512-MBS.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.10]
authentication-results: huawei.com; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CY1PR0501MB1098;
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(51704005)(33656002)(122556002)(40100003)(2501003)(106116001)(99286002)(92566002)(77156002)(62966003)(76576001)(102836002)(93886004)(2950100001)(74316001)(66066001)(76176999)(50986999)(54356999)(2656002)(87936001)(46102003)(86362001); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR0501MB1098; H:BY2PR05MB079.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
x-microsoft-antispam-prvs: <CY1PR0501MB1098F891BFBE4DCC64CD630BD4000@CY1PR0501MB1098.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5002010)(5005006); SRVR:CY1PR0501MB1098; BCL:0; PCL:0; RULEID:; SRVR:CY1PR0501MB1098; 
x-forefront-prvs: 051900244E
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Mar 2015 13:52:30.2639 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0501MB1098
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/pOm8s8gjjpnzEI_YJUVvHVs_7Jg>
X-Mailman-Approved-At: Wed, 18 Mar 2015 07:01:11 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] [Bier] Encapsulation first nibble
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 18 Mar 2015 13:52:51 -0000

Xiaohu,

> Following such logic (i.e., assign a nibble value specific to the new
> encapsulation header), we would have to consider how many available nibbl=
e
> values are there which can be used for future encapsulation headers in th=
e
> same way.

There are still quite a few values left; defining a new encapsulation is no=
t lightly taken; adding a new IP version is not lightly taken either. Besid=
es, there is this "reserved value 15" idea from Ice.

Coupled with the reasons that Eric gave:

> I think the proper direction is to use the MPLS entropy label, rather tha=
n to
> have each router compute the entropy based on an analysis of the next
> encapsulation header.
>=20
> So I don't think BIER justifies the use of a new MPLS special purpose
> payload-protocol-identifier label.

I would think the encap-specific nibble is quite reasonable, and better tha=
n a special purpose label.

Jeffrey


From nobody Wed Mar 18 07:20:38 2015
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61C691A03E3; Wed, 18 Mar 2015 07:20:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.422
X-Spam-Level: 
X-Spam-Status: No, score=-1.422 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CN_BODY_35=0.339, 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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id odteG29gNIjm; Wed, 18 Mar 2015 07:20:21 -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 E3B251A03FF; Wed, 18 Mar 2015 07:20:17 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BTU56820; Wed, 18 Mar 2015 14:20:16 +0000 (GMT)
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 18 Mar 2015 14:20:15 +0000
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.209]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.03.0158.001; Wed, 18 Mar 2015 22:20:11 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>, Antoni Przygienda <antoni.przygienda@ericsson.com>, "stbryant@cisco.com" <stbryant@cisco.com>, Eric Rosen <erosen@juniper.net>, BIER <bier@ietf.org>, IJsbrand Wijnands <ice@cisco.com>
Thread-Topic: [Bier] Encapsulation first nibble
Thread-Index: AQHQXcZrqojq7Dn2dkqRctiyZ05xTp0aTR0AgAY0PqCAAAkpwP//38SAgAAFoQCAAM2HIIAAhnQAgACMeVA=
Date: Wed, 18 Mar 2015 14:20:10 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CEFD@NKGEML512-MBS.china.huawei.com>
References: <55033E87.3030305@juniper.net> <5503403E.4050304@cisco.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CB77@NKGEML512-MBS.china.huawei.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CBB2@NKGEML512-MBS.china.huawei.com> <2E4BB27CAB87BF43B4207C0E55860F1827D3C5@eusaamb103.ericsson.se> <BY2PR05MB079ACD3AE28CC48B48C789ED4030@BY2PR05MB079.namprd05.prod.outlook.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CCE9@NKGEML512-MBS.china.huawei.com> <BY2PR05MB07904EDBB62DAF1E826E107D4000@BY2PR05MB079.namprd05.prod.outlook.com>
In-Reply-To: <BY2PR05MB07904EDBB62DAF1E826E107D4000@BY2PR05MB079.namprd05.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.117.70]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/CifTSRxNEKbB9s6pLGjTCc5qW7M>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] [Bier] Encapsulation first nibble
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 18 Mar 2015 14:20:23 -0000

SGkgSmVmZnJleSwNCg0KPiAtLS0tLdPKvP7Urbz+LS0tLS0NCj4gt6K8/sjLOiBKZWZmcmV5ICha
aGFvaHVpKSBaaGFuZyBbbWFpbHRvOnp6aGFuZ0BqdW5pcGVyLm5ldF0NCj4gt6LLzcqxvOQ6IDIw
MTXE6jPUwjE4yNUgMjE6NTMNCj4gytW8/sjLOiBYdXhpYW9odTsgQW50b25pIFByenlnaWVuZGE7
IHN0YnJ5YW50QGNpc2NvLmNvbTsgRXJpYyBSb3NlbjsgQklFUjsNCj4gSUpzYnJhbmQgV2lqbmFu
ZHMNCj4gs63LzTogbXBsc0BpZXRmLm9yZzsgc2ZjQGlldGYub3JnDQo+INb3zOI6IFJFOiBbQmll
cl0gRW5jYXBzdWxhdGlvbiBmaXJzdCBuaWJibGUNCj4gDQo+IFhpYW9odSwNCj4gDQo+ID4gRm9s
bG93aW5nIHN1Y2ggbG9naWMgKGkuZS4sIGFzc2lnbiBhIG5pYmJsZSB2YWx1ZSBzcGVjaWZpYyB0
byB0aGUgbmV3DQo+ID4gZW5jYXBzdWxhdGlvbiBoZWFkZXIpLCB3ZSB3b3VsZCBoYXZlIHRvIGNv
bnNpZGVyIGhvdyBtYW55IGF2YWlsYWJsZQ0KPiA+IG5pYmJsZSB2YWx1ZXMgYXJlIHRoZXJlIHdo
aWNoIGNhbiBiZSB1c2VkIGZvciBmdXR1cmUgZW5jYXBzdWxhdGlvbg0KPiA+IGhlYWRlcnMgaW4g
dGhlIHNhbWUgd2F5Lg0KPiANCj4gVGhlcmUgYXJlIHN0aWxsIHF1aXRlIGEgZmV3IHZhbHVlcyBs
ZWZ0OyBkZWZpbmluZyBhIG5ldyBlbmNhcHN1bGF0aW9uIGlzIG5vdCBsaWdodGx5DQo+IHRha2Vu
OyBhZGRpbmcgYSBuZXcgSVAgdmVyc2lvbiBpcyBub3QgbGlnaHRseSB0YWtlbiBlaXRoZXIuIEJl
c2lkZXMsIHRoZXJlIGlzIHRoaXMNCj4gInJlc2VydmVkIHZhbHVlIDE1IiBpZGVhIGZyb20gSWNl
Lg0KDQpTaW5jZSB0aGUgY29udHJvbCB3b3JkIGlzIG9wdGlvbmFsIHdoZW4gdHJhbnNwb3J0aW5n
IEV0aGVybmV0IG92ZXIgTVBMUywgSSB3b25kZXIgd2hldGhlciB0aGUgaWRlYSBvZiByZXNlcnZp
bmcgdGhlIGZpcnN0IG5pYmJsZSB2YWx1ZSBvZiAxNSBpcyBmZWFzaWJsZSBpbiBwcmFjdGljZS4N
Cg0KPiBDb3VwbGVkIHdpdGggdGhlIHJlYXNvbnMgdGhhdCBFcmljIGdhdmU6DQo+IA0KPiA+IEkg
dGhpbmsgdGhlIHByb3BlciBkaXJlY3Rpb24gaXMgdG8gdXNlIHRoZSBNUExTIGVudHJvcHkgbGFi
ZWwsIHJhdGhlcg0KPiA+IHRoYW4gdG8gaGF2ZSBlYWNoIHJvdXRlciBjb21wdXRlIHRoZSBlbnRy
b3B5IGJhc2VkIG9uIGFuIGFuYWx5c2lzIG9mDQo+ID4gdGhlIG5leHQgZW5jYXBzdWxhdGlvbiBo
ZWFkZXIuDQo+ID4NCj4gPiBTbyBJIGRvbid0IHRoaW5rIEJJRVIganVzdGlmaWVzIHRoZSB1c2Ug
b2YgYSBuZXcgTVBMUyBzcGVjaWFsIHB1cnBvc2UNCj4gPiBwYXlsb2FkLXByb3RvY29sLWlkZW50
aWZpZXIgbGFiZWwuDQo+IA0KPiBJIHdvdWxkIHRoaW5rIHRoZSBlbmNhcC1zcGVjaWZpYyBuaWJi
bGUgaXMgcXVpdGUgcmVhc29uYWJsZSwgYW5kIGJldHRlciB0aGFuIGENCj4gc3BlY2lhbCBwdXJw
b3NlIGxhYmVsLg0KDQpEdWUgdG8gdGhlIHNhbWUgcmVhc29uIGFzIG1lbnRpb25lZCBhYm92ZSwg
SSB3b25kZXIgd2hldGhlciBpdCdzIGZlYXNpYmxlIHRvIHJlc2VydmUgYSBjZXJ0YWluIGZpcnN0
IG5pYmJsZSB2YWx1ZSBhcyBhbiBlbmNhcC1zcGVjaWZpYyBuaWJibGUgaW4gcHJhY3RpY2UuDQoN
CkJlc3QgcmVnYXJkcywNClhpYW9odQ0KDQo+IEplZmZyZXkNCg==


From nobody Wed Mar 18 07:57:05 2015
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C3131A1A13; Wed, 18 Mar 2015 07:56:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.078
X-Spam-Level: **
X-Spam-Status: No, score=2.078 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339, MIME_8BIT_HEADER=0.3, 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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y6-J3sUcMaLw; Wed, 18 Mar 2015 07:56:57 -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 8201A1A1A0B; Wed, 18 Mar 2015 07:56:56 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BQJ83520; Wed, 18 Mar 2015 14:56:54 +0000 (GMT)
Received: from NKGEML403-HUB.china.huawei.com (10.98.56.34) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 18 Mar 2015 14:56:52 +0000
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.209]) by nkgeml403-hub.china.huawei.com ([10.98.56.34]) with mapi id 14.03.0158.001; Wed, 18 Mar 2015 22:56:40 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Xuxiaohu <xuxiaohu@huawei.com>, "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>, Antoni Przygienda <antoni.przygienda@ericsson.com>, "stbryant@cisco.com" <stbryant@cisco.com>, Eric Rosen <erosen@juniper.net>, BIER <bier@ietf.org>, IJsbrand Wijnands <ice@cisco.com>
Thread-Topic: [Bier] Encapsulation first nibble
Thread-Index: AQHQXcZrqojq7Dn2dkqRctiyZ05xTp0aTR0AgAY0PqCAAAkpwP//38SAgAAFoQCAAM2HIIAAhnQAgACMeVCAAAkmcA==
Date: Wed, 18 Mar 2015 14:56:39 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CF22@NKGEML512-MBS.china.huawei.com>
References: <55033E87.3030305@juniper.net> <5503403E.4050304@cisco.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CB77@NKGEML512-MBS.china.huawei.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CBB2@NKGEML512-MBS.china.huawei.com> <2E4BB27CAB87BF43B4207C0E55860F1827D3C5@eusaamb103.ericsson.se> <BY2PR05MB079ACD3AE28CC48B48C789ED4030@BY2PR05MB079.namprd05.prod.outlook.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CCE9@NKGEML512-MBS.china.huawei.com> <BY2PR05MB07904EDBB62DAF1E826E107D4000@BY2PR05MB079.namprd05.prod.outlook.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CEFD@NKGEML512-MBS.china.huawei.com>
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CEFD@NKGEML512-MBS.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.117.70]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/F4IxjBUlMNYIEqZxqFMYNIliUvs>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>
Subject: [sfc] =?gb2312?b?tPC4tDogW0JpZXJdIEVuY2Fwc3VsYXRpb24gZmlyc3Qgbmli?= =?gb2312?b?Ymxl?=
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 18 Mar 2015 14:56:59 -0000

DQoNCj4gLS0tLS3Tyrz+1K28/i0tLS0tDQo+ILeivP7IyzogbXBscyBbbWFpbHRvOm1wbHMtYm91
bmNlc0BpZXRmLm9yZ10gtPqx7SBYdXhpYW9odQ0KPiC3osvNyrG85DogMjAxNcTqM9TCMTjI1SAy
MjoyMA0KPiDK1bz+yMs6IEplZmZyZXkgKFpoYW9odWkpIFpoYW5nOyBBbnRvbmkgUHJ6eWdpZW5k
YTsgc3RicnlhbnRAY2lzY28uY29tOyBFcmljDQo+IFJvc2VuOyBCSUVSOyBJSnNicmFuZCBXaWpu
YW5kcw0KPiCzrcvNOiBtcGxzQGlldGYub3JnOyBzZmNAaWV0Zi5vcmcNCj4g1vfM4jogUmU6IFtt
cGxzXSBbQmllcl0gRW5jYXBzdWxhdGlvbiBmaXJzdCBuaWJibGUNCj4gDQo+IEhpIEplZmZyZXks
DQo+IA0KPiA+IC0tLS0t08q8/tStvP4tLS0tLQ0KPiA+ILeivP7IyzogSmVmZnJleSAoWmhhb2h1
aSkgWmhhbmcgW21haWx0bzp6emhhbmdAanVuaXBlci5uZXRdDQo+ID4gt6LLzcqxvOQ6IDIwMTXE
6jPUwjE4yNUgMjE6NTMNCj4gPiDK1bz+yMs6IFh1eGlhb2h1OyBBbnRvbmkgUHJ6eWdpZW5kYTsg
c3RicnlhbnRAY2lzY28uY29tOyBFcmljIFJvc2VuOw0KPiA+IEJJRVI7IElKc2JyYW5kIFdpam5h
bmRzDQo+ID4gs63LzTogbXBsc0BpZXRmLm9yZzsgc2ZjQGlldGYub3JnDQo+ID4g1vfM4jogUkU6
IFtCaWVyXSBFbmNhcHN1bGF0aW9uIGZpcnN0IG5pYmJsZQ0KPiA+DQo+ID4gWGlhb2h1LA0KPiA+
DQo+ID4gPiBGb2xsb3dpbmcgc3VjaCBsb2dpYyAoaS5lLiwgYXNzaWduIGEgbmliYmxlIHZhbHVl
IHNwZWNpZmljIHRvIHRoZQ0KPiA+ID4gbmV3IGVuY2Fwc3VsYXRpb24gaGVhZGVyKSwgd2Ugd291
bGQgaGF2ZSB0byBjb25zaWRlciBob3cgbWFueQ0KPiA+ID4gYXZhaWxhYmxlIG5pYmJsZSB2YWx1
ZXMgYXJlIHRoZXJlIHdoaWNoIGNhbiBiZSB1c2VkIGZvciBmdXR1cmUNCj4gPiA+IGVuY2Fwc3Vs
YXRpb24gaGVhZGVycyBpbiB0aGUgc2FtZSB3YXkuDQo+ID4NCj4gPiBUaGVyZSBhcmUgc3RpbGwg
cXVpdGUgYSBmZXcgdmFsdWVzIGxlZnQ7IGRlZmluaW5nIGEgbmV3IGVuY2Fwc3VsYXRpb24NCj4g
PiBpcyBub3QgbGlnaHRseSB0YWtlbjsgYWRkaW5nIGEgbmV3IElQIHZlcnNpb24gaXMgbm90IGxp
Z2h0bHkgdGFrZW4NCj4gPiBlaXRoZXIuIEJlc2lkZXMsIHRoZXJlIGlzIHRoaXMgInJlc2VydmVk
IHZhbHVlIDE1IiBpZGVhIGZyb20gSWNlLg0KPiANCj4gU2luY2UgdGhlIGNvbnRyb2wgd29yZCBp
cyBvcHRpb25hbCB3aGVuIHRyYW5zcG9ydGluZyBFdGhlcm5ldCBvdmVyIE1QTFMsIEkNCj4gd29u
ZGVyIHdoZXRoZXIgdGhlIGlkZWEgb2YgcmVzZXJ2aW5nIHRoZSBmaXJzdCBuaWJibGUgdmFsdWUg
b2YgMTUgaXMgZmVhc2libGUgaW4NCj4gcHJhY3RpY2UuDQo+IA0KPiA+IENvdXBsZWQgd2l0aCB0
aGUgcmVhc29ucyB0aGF0IEVyaWMgZ2F2ZToNCj4gPg0KPiA+ID4gSSB0aGluayB0aGUgcHJvcGVy
IGRpcmVjdGlvbiBpcyB0byB1c2UgdGhlIE1QTFMgZW50cm9weSBsYWJlbCwNCj4gPiA+IHJhdGhl
ciB0aGFuIHRvIGhhdmUgZWFjaCByb3V0ZXIgY29tcHV0ZSB0aGUgZW50cm9weSBiYXNlZCBvbiBh
bg0KPiA+ID4gYW5hbHlzaXMgb2YgdGhlIG5leHQgZW5jYXBzdWxhdGlvbiBoZWFkZXIuDQo+ID4g
Pg0KPiA+ID4gU28gSSBkb24ndCB0aGluayBCSUVSIGp1c3RpZmllcyB0aGUgdXNlIG9mIGEgbmV3
IE1QTFMgc3BlY2lhbA0KPiA+ID4gcHVycG9zZSBwYXlsb2FkLXByb3RvY29sLWlkZW50aWZpZXIg
bGFiZWwuDQo+ID4NCj4gPiBJIHdvdWxkIHRoaW5rIHRoZSBlbmNhcC1zcGVjaWZpYyBuaWJibGUg
aXMgcXVpdGUgcmVhc29uYWJsZSwgYW5kDQo+ID4gYmV0dGVyIHRoYW4gYSBzcGVjaWFsIHB1cnBv
c2UgbGFiZWwuDQo+IA0KPiBEdWUgdG8gdGhlIHNhbWUgcmVhc29uIGFzIG1lbnRpb25lZCBhYm92
ZSwgSSB3b25kZXIgd2hldGhlciBpdCdzIGZlYXNpYmxlIHRvDQo+IHJlc2VydmUgYSBjZXJ0YWlu
IGZpcnN0IG5pYmJsZSB2YWx1ZSBhcyBhbiBlbmNhcC1zcGVjaWZpYyBuaWJibGUgaW4gcHJhY3Rp
Y2UuDQoNCk1vcmUgc3BlY2lmaWNhbGx5LCBzaW5jZSBpdCBhbGxvd3MgdGhlIEV0aGVybmV0IGZy
YW1lcyB0byBiZSB0cmFuc3BvcnRlZCBvdmVyIE1QTFMgbmV0d29ya3Mgdy9vIGNvbnRyb2wgd29y
ZCwgYW55IHBvc3NpYmxlIHZhbHVlIG9mIHRoZSBmaXJzdCBuaWJibGUgbWF5IGhhdmUgYmVlbiB1
c2VkLiBPZiBjb3Vyc2UsIGlmIHRoZSBmaXJzdCBuaWJibGUgaXMgaW1tZWRpYXRlbHkgYWZ0ZXIg
YSBjZXJ0YWluIFNQTCBvciBFU1BMLCBpdCBiZWNvbWVzIHBvc3NpYmxlIHRvIHJlc2VydmUgYSBj
ZXJ0YWluIHZhbHVlIG9mIHRoYXQgbmliYmxlIGFzIGEgZ2l2ZW4gZW5jYXBzdWxhdGlvbiBoZWFk
ZXIgKHNlZSBodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtZ3VpY2hhcmQtc2ZjLW1l
dGFkYXRhLWhlYWRlci0wMCNwYWdlLTQpLiBIb3dldmVyLCBpbiB0aGlzIGNhc2UgKGkuZS4sIGFu
IFNQTCBvciBFU1BMIGlzIHVzZWQpLCBpdCBzZWVtcyBtb3JlIHN0cmFpZ2h0Zm9yd2FyZCB0byBh
ZGQgYSBwcm90byBmaWVsZCBhZnRlciB0aGUgZmlyc3QgbmliYmxlLCByYXRoZXIgdGhhbiB1c2lu
ZyB0aGUgZmlyc3QgbmliYmxlIGl0c2VsZiBhcyBhIHBvb3ItbWFuJ3MgcHJvdG8gZmllbGQuDQoN
Cj4gQmVzdCByZWdhcmRzLA0KPiBYaWFvaHUNCj4gDQo+ID4gSmVmZnJleQ0KPiBfX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBtcGxzIG1haWxpbmcgbGlz
dA0KPiBtcGxzQGlldGYub3JnDQo+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGlu
Zm8vbXBscw0K


From nobody Wed Mar 18 18:51:30 2015
Return-Path: <ibagdona.ietf@gmail.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6ED011A7D83; Wed, 18 Mar 2015 18:51:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 pI1bF-vJ616d; Wed, 18 Mar 2015 18:51:24 -0700 (PDT)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90BCA1A702E; Wed, 18 Mar 2015 18:51:24 -0700 (PDT)
Received: by wifj2 with SMTP id j2so55526740wif.1; Wed, 18 Mar 2015 18:51:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=ToDwbz0AjYZtl2HE+C0xwyTaOQYyXD3HRrOpFGpirEk=; b=Z5gJdw+SaHaa0nYxKmqK2GRtYiK1yVrQ7wQBPh2fXaA9WhmRbj0QPHpOZSEVhRxvza rnG3uvGKU/8BHwkOfAB7TcOAahy8yAN2K1YVlVy/IP9VBSTI85lVtTORph3pwRIAHw/6 8Y5iHfee4aDs1irUFufd/DUdBsDWtYRNAi1JcTCFkiPXGLbxWWIcm2Vztf+7+xkD67+F lbbC99X0EfpzZiCO5/bAQoHB+VptwzYJh3vZTT9tgAMZSNXHP8HMtjzjKRpevWPry2f1 F8oL6JkAwEfK8MDOVMTLMY6rFFDyoljH9XOcBE2WjNI24BYN94VbyZYJ8KYEJbQ8iMWx T9Bw==
X-Received: by 10.194.75.168 with SMTP id d8mr149713355wjw.87.1426729883426; Wed, 18 Mar 2015 18:51:23 -0700 (PDT)
Received: from [192.168.101.5] (host86-143-211-157.range86-143.btcentralplus.com. [86.143.211.157]) by mx.google.com with ESMTPSA id m4sm26744504wjb.25.2015.03.18.18.51.21 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 18 Mar 2015 18:51:22 -0700 (PDT)
Message-ID: <550A2B98.4010409@gmail.com>
Date: Thu, 19 Mar 2015 01:51:20 +0000
From: Ignas Bagdonas <ibagdona.ietf@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Xuxiaohu <xuxiaohu@huawei.com>,  "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>, Antoni Przygienda <antoni.przygienda@ericsson.com>,  "stbryant@cisco.com" <stbryant@cisco.com>, Eric Rosen <erosen@juniper.net>, BIER <bier@ietf.org>,  IJsbrand Wijnands <ice@cisco.com>
References: <55033E87.3030305@juniper.net> <5503403E.4050304@cisco.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CB77@NKGEML512-MBS.china.huawei.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CBB2@NKGEML512-MBS.china.huawei.com> <2E4BB27CAB87BF43B4207C0E55860F1827D3C5@eusaamb103.ericsson.se> <BY2PR05MB079ACD3AE28CC48B48C789ED4030@BY2PR05MB079.namprd05.prod.outlook.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CCE9@NKGEML512-MBS.china.huawei.com> <BY2PR05MB07904EDBB62DAF1E826E107D4000@BY2PR05MB079.namprd05.prod.outlook.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CEFD@NKGEML512-MBS.china.huawei.com>
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CEFD@NKGEML512-MBS.china.huawei.com>
Content-Type: text/plain; charset=gbk; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/JdYLMp8xsVMHsYjgKZhky6C2WoI>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] [Bier] Encapsulation first nibble
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 19 Mar 2015 01:51:26 -0000

Hi,

 > Since the control word is optional when transporting Ethernet over 
MPLS, I wonder whether the idea of reserving the first nibble value of 
15 is feasible in practice.

Not using a control word for ethernet PW is painful from operational 
perspective. Many deployed platforms will look past the labels without 
much context and if they happen to find 4 or 6 there, the behavior will 
range from blindly believing that it is in fact IPv4 or IPv6 packet to 
trying to validate certain fields or even checksums. Control word helps 
here, and if both sides have support, it should be used.

Ignas


From nobody Thu Mar 19 00:41:17 2015
Return-Path: <stbryant@cisco.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C857B1A8762; Thu, 19 Mar 2015 00:41:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 FbOLYqY5W8tL; Thu, 19 Mar 2015 00:41:11 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3CEE41A1B57; Thu, 19 Mar 2015 00:41:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1621; q=dns/txt; s=iport; t=1426750871; x=1427960471; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=9ztbs+LNwbJ/HUn2pqLLWGEkjB7FPgRMEz4ohL/JFIs=; b=IqjSYhzDMFFK86VLgUVEzx1ux8SaL4QgLiF81bn+HP5gq+78nxX1IxMN iGlybXGztK8M2tqRHPpKcSEnMP3m9cN9Is46cF7n0IHjivTBZZiL/9wOj PuXKsDg82jrfwZyWfoqcF0DeVxufHChlUuiIH/2w8Rzq9vjosghXUM5xB s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BTCgDofApV/5NdJa1cgwaBLLQWj0SILwKBR0wBAQEBAQF9hA8BAQEDATo/BQsCAQgOCh4QIRElAgQOBYgbAwkIyBkNhTABAQEBAQEBAQEBAQEBAQEBAQEBARiLF4JEgXozB4MXgRYFjjuCDoghgUyOAoYmIoNub4EEJIEbAQEB
X-IronPort-AV: E=Sophos;i="5.11,428,1422921600"; d="scan'208";a="404839026"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by rcdn-iport-7.cisco.com with ESMTP; 19 Mar 2015 07:41:09 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id t2J7f9lG024555 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 19 Mar 2015 07:41:09 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.114]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.03.0195.001; Thu, 19 Mar 2015 02:41:09 -0500
From: "Stewart Bryant (stbryant)" <stbryant@cisco.com>
To: Ignas Bagdonas <ibagdona.ietf@gmail.com>
Thread-Topic: [Bier] Encapsulation first nibble
Thread-Index: AQHQYec1U0ed6cLwWkSulZECuVCa0p0jbFFW
Date: Thu, 19 Mar 2015 07:41:08 +0000
Message-ID: <95467337-1826-4C9E-888A-ABABE872CD56@cisco.com>
References: <55033E87.3030305@juniper.net> <5503403E.4050304@cisco.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CB77@NKGEML512-MBS.china.huawei.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CBB2@NKGEML512-MBS.china.huawei.com> <2E4BB27CAB87BF43B4207C0E55860F1827D3C5@eusaamb103.ericsson.se> <BY2PR05MB079ACD3AE28CC48B48C789ED4030@BY2PR05MB079.namprd05.prod.outlook.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CCE9@NKGEML512-MBS.china.huawei.com> <BY2PR05MB07904EDBB62DAF1E826E107D4000@BY2PR05MB079.namprd05.prod.outlook.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CEFD@NKGEML512-MBS.china.huawei.com>, <550A2B98.4010409@gmail.com>
In-Reply-To: <550A2B98.4010409@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/jvBqQOlsn1BUVmx_mixieOHepM0>
Cc: "mpls@ietf.org" <mpls@ietf.org>, BIER <bier@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>, Antoni Przygienda <antoni.przygienda@ericsson.com>, "IJsbrand Wijnands \(iwijnand\)" <ice@cisco.com>, "Jeffrey \(Zhaohui\) Zhang" <zzhang@juniper.net>, Xuxiaohu <xuxiaohu@huawei.com>, Eric Rosen <erosen@juniper.net>
Subject: Re: [sfc] [Bier] Encapsulation first nibble
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 19 Mar 2015 07:41:16 -0000

That is correct.

PWE3 took over the design after draft-martini had been widely adopted and d=
eployed, otherwise PWs may well have been exclusively CW. The wide deployme=
nt of Ethernet PW without the CW means that PW OAM is more complicated than=
 it would otherwise be - see the latest vcxo over GAL draft from PALS. It w=
as asserted in the early days that there would not be a problem because the=
re would never be an ethernet address issued that alias with the IPv4 first=
 nibble. Well guess what happened? Yes they were and yes there was!

There is another way forward, require the inclusion of the ELI and exclusiv=
e use of ELI enabled LSPs, but in that case the packet size would go up by =
more than needed to fix BIER and the operational complexity would be signif=
icant, thus the cure would be worse than the disease.

Stewart=20

Sent from my iPad

> On 19 Mar 2015, at 01:51, Ignas Bagdonas <ibagdona.ietf@gmail.com> wrote:
>=20
>=20
> Hi,
>=20
> > Since the control word is optional when transporting Ethernet over MPLS=
, I wonder whether the idea of reserving the first nibble value of 15 is fe=
asible in practice.
>=20
> Not using a control word for ethernet PW is painful from operational pers=
pective. Many deployed platforms will look past the labels without much con=
text and if they happen to find 4 or 6 there, the behavior will range from =
blindly believing that it is in fact IPv4 or IPv6 packet to trying to valid=
ate certain fields or even checksums. Control word helps here, and if both =
sides have support, it should be used.
>=20
> Ignas
>=20


From nobody Thu Mar 19 03:57:51 2015
Return-Path: <stbryant@cisco.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAEF11A8974; Thu, 19 Mar 2015 03:57:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 w8Ga2GGGclTt; Thu, 19 Mar 2015 03:57:49 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C3171A883A; Thu, 19 Mar 2015 03:57:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=217; q=dns/txt; s=iport; t=1426762669; x=1427972269; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=0D7ULytw52vE8Rsw1bDbn9cB9GRuRcLLj/L+ojSfCKA=; b=L0aKJxaNdx3h0/oEEbdvuC2ElOAIa3HxMtI/SWrSp0kCoozuJjYzKnyg mX+BcBvA5GhnpztaVG2wk+MduMhgy8JM5ge4rfqTMso5EbZQX4pQChHxj e1ANAYVinmuPscz1Cn5yHIMKQOMAeKBAhOXTozTWgXFbo2x0NIKA4GmGi M=;
X-IronPort-AV: E=Sophos;i="5.11,429,1422921600"; d="scan'208";a="410305594"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP; 19 Mar 2015 10:57:46 +0000
Received: from [64.103.108.142] (dhcp-bdlk10-data-vlan301-64-103-108-142.cisco.com [64.103.108.142]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t2JAvkBn021392; Thu, 19 Mar 2015 10:57:46 GMT
Message-ID: <550AABAC.9020008@cisco.com>
Date: Thu, 19 Mar 2015 10:57:48 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Ignas Bagdonas <ibagdona.ietf@gmail.com>
References: <55033E87.3030305@juniper.net> <5503403E.4050304@cisco.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CB77@NKGEML512-MBS.china.huawei.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CBB2@NKGEML512-MBS.china.huawei.com> <2E4BB27CAB87BF43B4207C0E55860F1827D3C5@eusaamb103.ericsson.se> <BY2PR05MB079ACD3AE28CC48B48C789ED4030@BY2PR05MB079.namprd05.prod.outlook.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CCE9@NKGEML512-MBS.china.huawei.com> <BY2PR05MB07904EDBB62DAF1E826E107D4000@BY2PR05MB079.namprd05.prod.outlook.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CEFD@NKGEML512-MBS.china.huawei.com>, <550A2B98.4010409@gmail.com> <95467337-1826-4C9E-888A-ABABE872CD56@cisco.com>
In-Reply-To: <95467337-1826-4C9E-888A-ABABE872CD56@cisco.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/WxuFWhvdCsRpUJwNfdY1mFRy2_k>
Cc: "mpls@ietf.org" <mpls@ietf.org>, BIER <bier@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>, Antoni Przygienda <antoni.przygienda@ericsson.com>, "IJsbrand Wijnands \(iwijnand\)" <ice@cisco.com>, "Jeffrey \(Zhaohui\) Zhang" <zzhang@juniper.net>, Xuxiaohu <xuxiaohu@huawei.com>, Eric Rosen <erosen@juniper.net>
Subject: Re: [sfc] [Bier] Encapsulation first nibble
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 19 Mar 2015 10:57:50 -0000

Re-my last email.

Aren't learning spell correctors annoying!  VCXO was supposed to be
VCCV.  Clearly my iPad feels itself to be more closely affiliated to my
radio interests than my PW interests :(

- Stewart



From nobody Thu Mar 19 05:29:16 2015
Return-Path: <ju1738@att.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D39A41A8987; Thu, 19 Mar 2015 04:21:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 yhd9inf1ZYAm; Thu, 19 Mar 2015 04:21:44 -0700 (PDT)
Received: from nbfkord-smmo07.seg.att.com (nbfkord-smmo07.seg.att.com [209.65.160.93]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CD361A897D; Thu, 19 Mar 2015 04:21:44 -0700 (PDT)
Received: from unknown [144.160.229.24] (EHLO alpi155.enaf.aldc.att.com) by nbfkord-smmo07.seg.att.com(mxl_mta-7.2.4-5) with ESMTP id 841ba055.2ac71be52940.712039.00-2473.2004047.nbfkord-smmo07.seg.att.com (envelope-from <ju1738@att.com>);  Thu, 19 Mar 2015 11:21:44 +0000 (UTC)
X-MXL-Hash: 550ab14865649ad0-25ceca41a2027a8f4c88a27a64d1e2baa5193bc1
Received: from unknown [144.160.229.24] (EHLO alpi155.enaf.aldc.att.com) by nbfkord-smmo07.seg.att.com(mxl_mta-7.2.4-5) over TLS secured channel with ESMTP id 131ba055.0.711937.00-2355.2003718.nbfkord-smmo07.seg.att.com (envelope-from <ju1738@att.com>);  Thu, 19 Mar 2015 11:21:21 +0000 (UTC)
X-MXL-Hash: 550ab13135a93a18-f507932942442f3dd0501fe25118d8c3b55b5ef3
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id t2JBLK7s017741; Thu, 19 Mar 2015 07:21:20 -0400
Received: from mlpi408.sfdc.sbc.com (mlpi408.sfdc.sbc.com [130.9.128.240]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id t2JBLC77017631 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 19 Mar 2015 07:21:17 -0400
Received: from MISOUT7MSGHUBAB.ITServices.sbc.com (MISOUT7MSGHUBAB.itservices.sbc.com [130.9.129.146]) by mlpi408.sfdc.sbc.com (RSA Interceptor); Thu, 19 Mar 2015 11:20:53 GMT
Received: from MISOUT7MSGUSRCD.ITServices.sbc.com ([169.254.4.34]) by MISOUT7MSGHUBAB.ITServices.sbc.com ([130.9.129.146]) with mapi id 14.03.0224.002; Thu, 19 Mar 2015 07:20:53 -0400
From: "UTTARO, JAMES" <ju1738@att.com>
To: "'Stewart Bryant (stbryant)'" <stbryant@cisco.com>, "'Ignas Bagdonas'" <ibagdona.ietf@gmail.com>
Thread-Topic: [Bier] Encapsulation first nibble
Thread-Index: AQHQYhgcaT61EyeEBUKVRfvUSw0LlZ0jqlJw
Date: Thu, 19 Mar 2015 11:20:53 +0000
Message-ID: <B17A6910EEDD1F45980687268941550F06E220BE@MISOUT7MSGUSRCD.ITServices.sbc.com>
References: <55033E87.3030305@juniper.net> <5503403E.4050304@cisco.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CB77@NKGEML512-MBS.china.huawei.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CBB2@NKGEML512-MBS.china.huawei.com> <2E4BB27CAB87BF43B4207C0E55860F1827D3C5@eusaamb103.ericsson.se> <BY2PR05MB079ACD3AE28CC48B48C789ED4030@BY2PR05MB079.namprd05.prod.outlook.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CCE9@NKGEML512-MBS.china.huawei.com> <BY2PR05MB07904EDBB62DAF1E826E107D4000@BY2PR05MB079.namprd05.prod.outlook.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831CEFD@NKGEML512-MBS.china.huawei.com>, <550A2B98.4010409@gmail.com> <95467337-1826-4C9E-888A-ABABE872CD56@cisco.com>
In-Reply-To: <95467337-1826-4C9E-888A-ABABE872CD56@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.70.46.160]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-AnalysisOut: [v=2.0 cv=VY5AyiV9 c=1 sm=1 a=dhB6nF3YHL5t/Ixux6cINA==:17 a]
X-AnalysisOut: [=-vCCya6ofXAA:10 a=BLceEmwcHowA:10 a=kj9zAlcOel0A:10 a=zQP]
X-AnalysisOut: [7CpKOAAAA:8 a=XIqpo32RAAAA:8 a=emO1SXQWCLwA:10 a=48vgC7mUA]
X-AnalysisOut: [AAA:8 a=pGLkceISAAAA:8 a=DoV0cjcpzXQ8FZWdvQMA:9 a=CjuIK1q_]
X-AnalysisOut: [8ugA:10 a=4xa8uTXoekMmPyhK:21 a=OMQviz-YQPlPQJv3:21]
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2014051901)]
X-MAIL-FROM: <ju1738@att.com>
X-SOURCE-IP: [144.160.229.24]
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/VwVFDKrhh-1AzQ4uwM56RehBCVs>
X-Mailman-Approved-At: Thu, 19 Mar 2015 05:29:15 -0700
Cc: "'mpls@ietf.org'" <mpls@ietf.org>, 'BIER' <bier@ietf.org>, "'sfc@ietf.org'" <sfc@ietf.org>, 'Antoni Przygienda' <antoni.przygienda@ericsson.com>, "'IJsbrand Wijnands \(iwijnand\)'" <ice@cisco.com>, "'Jeffrey \(Zhaohui\) Zhang'" <zzhang@juniper.net>, 'Xuxiaohu' <xuxiaohu@huawei.com>, 'Eric Rosen' <erosen@juniper.net>
Subject: Re: [sfc] [Bier] Encapsulation first nibble
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 19 Mar 2015 11:21:49 -0000

Not really following this thread closely but from my point of view the ELI =
solution creates addl issues when one wants to use network elements that ar=
e label challenged in terms of pop/push/swap and label stack size.=20

Jim Uttaro

-----Original Message-----
From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of Stewart Bryant (stbrya=
nt)
Sent: Thursday, March 19, 2015 3:41 AM
To: Ignas Bagdonas
Cc: mpls@ietf.org; BIER; sfc@ietf.org; Antoni Przygienda; IJsbrand Wijnands=
 (iwijnand); Jeffrey (Zhaohui) Zhang; Xuxiaohu; Eric Rosen
Subject: Re: [sfc] [Bier] Encapsulation first nibble

That is correct.

PWE3 took over the design after draft-martini had been widely adopted and d=
eployed, otherwise PWs may well have been exclusively CW. The wide deployme=
nt of Ethernet PW without the CW means that PW OAM is more complicated than=
 it would otherwise be - see the latest vcxo over GAL draft from PALS. It w=
as asserted in the early days that there would not be a problem because the=
re would never be an ethernet address issued that alias with the IPv4 first=
 nibble. Well guess what happened? Yes they were and yes there was!

There is another way forward, require the inclusion of the ELI and exclusiv=
e use of ELI enabled LSPs, but in that case the packet size would go up by =
more than needed to fix BIER and the operational complexity would be signif=
icant, thus the cure would be worse than the disease.

Stewart=20

Sent from my iPad

> On 19 Mar 2015, at 01:51, Ignas Bagdonas <ibagdona.ietf@gmail.com> wrote:
>=20
>=20
> Hi,
>=20
> > Since the control word is optional when transporting Ethernet over MPLS=
, I wonder whether the idea of reserving the first nibble value of 15 is fe=
asible in practice.
>=20
> Not using a control word for ethernet PW is painful from operational pers=
pective. Many deployed platforms will look past the labels without much con=
text and if they happen to find 4 or 6 there, the behavior will range from =
blindly believing that it is in fact IPv4 or IPv6 packet to trying to valid=
ate certain fields or even checksums. Control word helps here, and if both =
sides have support, it should be used.
>=20
> Ignas
>=20

_______________________________________________
sfc mailing list
sfc@ietf.org
https://www.ietf.org/mailman/listinfo/sfc


From nobody Sat Mar 21 10:33:45 2015
Return-Path: <jguichar@cisco.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50E1C1A9168 for <sfc@ietfa.amsl.com>; Sat, 21 Mar 2015 10:33:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 bx7qzuTadGdL for <sfc@ietfa.amsl.com>; Sat, 21 Mar 2015 10:33:42 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B6681A90D2 for <sfc@ietf.org>; Sat, 21 Mar 2015 10:33:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=207; q=dns/txt; s=iport; t=1426959222; x=1428168822; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=I4ZKkaStazZBC8arJ3mLttTUq6m6BIa16lyBTUVeqs4=; b=KpHL9A5N22PMwyFIML04Rm2eahP3VOTWrTuk+ZikEj8aPBB6rWcTd5ur s8OWiKGUHU+KZpptH4kKIGZzst9nsIhjeIMqYd118M7I7BSxXhgKNq1gd ouvbrc0blHcsmYV3HxSlACdIdyYn6llkMqxDUcgMB6rFKFeUpMzaUysbW 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AFBQB1qg1V/4QNJK1cgwbOC4EyTAEBAQEBAX2EGzpRAT5CJgEEiEKhBKk/AQEBAQYBAQEBAQEBARqTNIEWBZBPiW6BG4MwjBiDRyKDboMyAQEB
X-IronPort-AV: E=Sophos;i="5.11,443,1422921600"; d="scan'208";a="134207327"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by alln-iport-4.cisco.com with ESMTP; 21 Mar 2015 17:33:41 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id t2LHXf7T014309 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <sfc@ietf.org>; Sat, 21 Mar 2015 17:33:41 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.225]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.03.0195.001; Sat, 21 Mar 2015 12:33:41 -0500
From: "Jim Guichard (jguichar)" <jguichar@cisco.com>
To: sfc <sfc@ietf.org>
Thread-Topic: SFC meeting slides
Thread-Index: AdBj/Sv+o7RTRuSFSsOjjSeSaDUt7w==
Date: Sat, 21 Mar 2015 17:33:41 +0000
Message-ID: <9D86ACA2-4A9D-406B-BAA2-7F3E5844CB87@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-ID: <9ED6D76BC2BC55469B2751ED64F0A600@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/9U9w3RhJxKv2SCQoyE2XqxYb5nI>
Subject: [sfc] SFC meeting slides
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sat, 21 Mar 2015 17:33:43 -0000

Greetings WG,

For those with presentation slots for our upcoming meeting please send your=
 presentations to me asap so that I can upload them to the proceedings page=
.

Jim

Sent from my iPhone=


From nobody Mon Mar 23 14:05:09 2015
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7CFD1A1ADA for <sfc@ietfa.amsl.com>; Mon, 23 Mar 2015 14:05:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.19
X-Spam-Level: 
X-Spam-Status: No, score=-3.19 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 pfqwICcMFCnM for <sfc@ietfa.amsl.com>; Mon, 23 Mar 2015 14:05:05 -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 9EB9C1A1AA9 for <sfc@ietf.org>; Mon, 23 Mar 2015 14:05:04 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BUA97586; Mon, 23 Mar 2015 21:05:03 +0000 (GMT)
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 23 Mar 2015 21:05:02 +0000
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.209]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.03.0158.001; Tue, 24 Mar 2015 05:04:55 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
CC: "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: Re: [sfc] New Version Notification for draft-xu-sfc-using-mpls-spring-02.txt
Thread-Index: AdBlrZ0+2xprrtZJRtC8gF9gPKT9CQ==
Date: Mon, 23 Mar 2015 21:04:55 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831E2F7@NKGEML512-MBS.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.144.217]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/EOorLc6AJqvAWLSBIZ4KGrxZ2_w>
Subject: Re: [sfc] New Version Notification for draft-xu-sfc-using-mpls-spring-02.txt
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 23 Mar 2015 21:05:07 -0000

Hi SFC co-chairs,

I have remove those options (i.e., encoding SFC using a label stack consist=
 of global labels and inserting a protocol field after the label stack for =
MPLS payload indication) which would cause changes to the MPLS architecture=
 in the latest version (http://tools.ietf.org/html/draft-xu-sfc-using-mpls-=
spring-03).=20

Therefore, we co-authors think it's now becoming suitable for the SFC WG to=
 reconsider this simplified MPLS-SPRING-based SFC solution which doesn't re=
quire any change to the MPLS base architecture.

Best regards,
Xiaohu

> -----Original Message-----
> From: Xuxiaohu
> Sent: Friday, March 06, 2015 8:49 AM
> To: 'Jim Guichard (jguichar)'; Ron Parker
> Cc: mpls at ietf.org; <spring at ietf.org>; sfc at ietf.org
> Subject: RE: [sfc] New Version Notification for
> draft-xu-sfc-using-mpls-spring-02.txt
>=20
> Hi Jim,
>=20
> Understood.
>=20
> Best regards,
> Xiaohu
>=20
> > -----Original Message-----
> > From: Jim Guichard (jguichar) [mailto:jguichar at cisco.com]
> > Sent: Thursday, March 05, 2015 11:11 PM
> > To: Ron Parker; Xuxiaohu
> > Cc: mpls at ietf.org; <spring at ietf.org>; sfc at ietf.org
> > Subject: Re: [sfc] New Version Notification for
> > draft-xu-sfc-using-mpls-spring-02.txt
> >
> > Hi Xiaohu,
> >
> > Thomas and I read your latest draft and believe that you will need to
> > take it to the MPLS WG as a first step. There are a number of things
> > within the document that may require changes to the base MPLS
> > architecture and the SFC WG is not the right community to address
> > those. Given this we will not be able to consider this document in the
> > SFC WG without agreement from the broader MPLS community.
> >
> > Regards,
> >
> > Jim & Thomas


From nobody Mon Mar 23 14:08:39 2015
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D8471B2A64; Mon, 23 Mar 2015 14:08:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 wice8fcABdpq; Mon, 23 Mar 2015 14:08:35 -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 D855E1B2A5D; Mon, 23 Mar 2015 14:08:34 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BQP87843; Mon, 23 Mar 2015 21:08:33 +0000 (GMT)
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 23 Mar 2015 21:08:33 +0000
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.209]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.03.0158.001; Tue, 24 Mar 2015 05:08:27 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: request to reconsider the new version of draft-xu-sfc-using-mpls-spring
Thread-Index: AdBlrhuBfuzgVbaLRIaHXE2MjsyRxQ==
Date: Mon, 23 Mar 2015 21:08:26 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0831E312@NKGEML512-MBS.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.144.217]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/xfYhQ5VrJHpz4kvdPU1DREVQUIs>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "spring@ietf.org" <spring@ietf.org>
Subject: [sfc] request to reconsider the new version of draft-xu-sfc-using-mpls-spring
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 23 Mar 2015 21:08:38 -0000

Hi SFC co-chairs,

I have remove those options (i.e., encoding SFC using a label stack consist=
 of global labels and inserting a protocol field after the label stack for =
MPLS payload indication) which would cause changes to the MPLS architecture=
 in the latest version (http://tools.ietf.org/html/draft-xu-sfc-using-mpls-=
spring-03).=20

Therefore, we co-authors think it's now becoming suitable for the SFC WG to=
 reconsider this simplified MPLS-SPRING-based SFC solution which doesn't re=
quire any change to the MPLS base architecture.

Best regards,
Xiaohu

> -----Original Message-----
> From: Xuxiaohu
> Sent: Friday, March 06, 2015 8:49 AM
> To: 'Jim Guichard (jguichar)'; Ron Parker
> Cc: mpls at ietf.org; <spring at ietf.org>; sfc at ietf.org
> Subject: RE: [sfc] New Version Notification for=20
> draft-xu-sfc-using-mpls-spring-02.txt
>=20
> Hi Jim,
>=20
> Understood.
>=20
> Best regards,
> Xiaohu
>=20
> > -----Original Message-----
> > From: Jim Guichard (jguichar) [mailto:jguichar at cisco.com]
> > Sent: Thursday, March 05, 2015 11:11 PM
> > To: Ron Parker; Xuxiaohu
> > Cc: mpls at ietf.org; <spring at ietf.org>; sfc at ietf.org
> > Subject: Re: [sfc] New Version Notification for=20
> > draft-xu-sfc-using-mpls-spring-02.txt
> >
> > Hi Xiaohu,
> >
> > Thomas and I read your latest draft and believe that you will need=20
> > to take it to the MPLS WG as a first step. There are a number of=20
> > things within the document that may require changes to the base MPLS=20
> > architecture and the SFC WG is not the right community to address=20
> > those. Given this we will not be able to consider this document in=20
> > the SFC WG without agreement from the broader MPLS community.
> >
> > Regards,
> >
> > Jim & Thomas


From nobody Mon Mar 23 16:06:02 2015
Return-Path: <repenno@cisco.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 053D41A0A85 for <sfc@ietfa.amsl.com>; Mon, 23 Mar 2015 16:06:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 SyQgqkOsESi0 for <sfc@ietfa.amsl.com>; Mon, 23 Mar 2015 16:05:58 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 768621A00FE for <sfc@ietf.org>; Mon, 23 Mar 2015 16:05:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1162; q=dns/txt; s=iport; t=1427151959; x=1428361559; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=mQK3iqOcENnS2h4dNBuT5EJnbUPHdv/mJZWg2E/jsLg=; b=Zb2VnxaC/CoSGptKhRu6KcIOE0muTg9q4vcKLSqZxifuj0xiALMhoraq GwGuXaDnnDwU55xsI1AK5Jh9tPnnu8kztsCuhQRdiFIv02h966p/BVMpK VyHf5+RO2OX5TxJifIlPSCBEPkM0XtFQvLiJ9x/o9BF9U0ZGGfSytNpwR 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0A4BQAtnBBV/4UNJK1cgwZSVQUExk+HJUwBAQEBAQF9hBs6UQE+QicEEwmIJggFnnqpXgELAR+USgWOQYIOg2+Ff4EbOoJ2j18ig25vAYFDfwEBAQ
X-IronPort-AV: E=Sophos;i="5.11,455,1422921600"; d="scan'208";a="134740223"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by alln-iport-6.cisco.com with ESMTP; 23 Mar 2015 23:05:57 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id t2NN5vNd012549 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <sfc@ietf.org>; Mon, 23 Mar 2015 23:05:57 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.114]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.03.0195.001; Mon, 23 Mar 2015 18:05:57 -0500
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: SFC Traceroute
Thread-Index: AQHQZb3rjJcOOUoim0SjDGde3At9bw==
Date: Mon, 23 Mar 2015 23:05:56 +0000
Message-ID: <D136064A.DB64%repenno@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.8.150116
x-originating-ip: [10.24.66.142]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3B5B49291067A04D8567650D5406C563@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/GRcxyf32zW6wB1-4AcYkLlN5HiA>
Subject: [sfc] SFC Traceroute
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 23 Mar 2015 23:06:02 -0000

New version of SFC Traceroute.

Thanks to those in the hackathon that tested it.


On 3/23/15, 6:03 PM, "internet-drafts@ietf.org" <internet-drafts@ietf.org>
wrote:

>
>A new version of I-D, draft-penno-sfc-trace-02.txt
>has been successfully submitted by Reinaldo Penno and posted to the
>IETF repository.
>
>Name:		draft-penno-sfc-trace
>Revision:	02
>Title:		Services Function Chaining Traceroute
>Document date:	2015-03-23
>Group:		Individual Submission
>Pages:		9
>URL:           =20
>http://www.ietf.org/internet-drafts/draft-penno-sfc-trace-02.txt
>Status:         https://datatracker.ietf.org/doc/draft-penno-sfc-trace/
>Htmlized:       http://tools.ietf.org/html/draft-penno-sfc-trace-02
>Diff:           http://www.ietf.org/rfcdiff?url2=3Ddraft-penno-sfc-trace-0=
2
>
>Abstract:
>   This document defines a protocol that checks the liveness and report
>   the service-hops of a service path. .
>
>
>                 =20
>       =20
>
>
>Please note that it may take a couple of minutes from the time of
>submission
>until the htmlized version and diff are available at tools.ietf.org.
>
>The IETF Secretariat
>


From nobody Tue Mar 24 06:27:25 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED9491A1A68; Tue, 24 Mar 2015 06:27:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 Qk5GCMXNjREn; Tue, 24 Mar 2015 06:27:20 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C4A3C1A1AB3; Tue, 24 Mar 2015 06:27:20 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.12.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150324132720.32029.55600.idtracker@ietfa.amsl.com>
Date: Tue, 24 Mar 2015 06:27:20 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/YvINy-ZoOKiY_q9D6kLo2lxZ-7c>
Cc: sfc@ietf.org
Subject: [sfc] I-D Action: draft-ietf-sfc-nsh-00.txt
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 24 Mar 2015 13:27:22 -0000

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-00.txt
	Pages           : 42
	Date            : 2015-03-24

Abstract:
   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.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-sfc-nsh/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-sfc-nsh-00


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Mar 24 08:02:24 2015
Return-Path: <sunilvk@f5.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E2581A87A7 for <sfc@ietfa.amsl.com>; Tue, 24 Mar 2015 08:02:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.01
X-Spam-Level: 
X-Spam-Status: No, score=-7.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 W3nlJcbHbhIN for <sfc@ietfa.amsl.com>; Tue, 24 Mar 2015 08:02:17 -0700 (PDT)
Received: from mail.f5.com (mail.f5.com [208.85.209.139]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BFE061A8792 for <sfc@ietf.org>; Tue, 24 Mar 2015 08:02:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=f5.com; i=@f5.com; q=dns/txt; s=seattle; t=1427209338; x=1458745338; h=from:to:subject:date:message-id:mime-version; bh=d8e0FJTyIIA/BR1Z0P7/VTQRqrg0XPO16Ekm8WUleUs=; b=BJgbh5zM63d2saxglbwyD2rAxgk4IRU0DhQpy6rdWlcv1b0xSbqAtsa1 94vX8C5a5p6Rrgfgdt7lCSfvCf4cTIZpJAwEpnbFI9jZBxBRjlllOOJaQ 34whb/K/Aq377S4hz+u34XjSaa+Yx+l9vvFqAiwwQaMjx3ArwS5iCDWDz U=;
X-IronPort-AV: E=Sophos;i="5.11,458,1422921600";  d="scan'208,217";a="154641332"
X-IPAS-Result: A2CpBACEexFV/+sKqMBcgkOBFV7GJxYFAYgFAQEBAQEBfYQbLV4BgQAmAQQb0SMskksMQYEzBY5CoCmEEIIzfwEBAQ
Received: from oracle-apps.f5net.com (HELO exchmail.f5net.com) ([192.168.10.235]) by mail.f5.com with ESMTP/TLS/AES256-SHA; 24 Mar 2015 15:02:17 +0000
Received: from SEAEXCHMBX03.olympus.F5Net.com (192.168.15.225) by seaexchmbx02.olympus.F5Net.com (192.168.15.224) with Microsoft SMTP Server (TLS) id 15.0.1044.25; Tue, 24 Mar 2015 08:02:16 -0700
Received: from SEAEXCHMBX03.olympus.F5Net.com ([fe80::f95f:ea5d:773b:29b8]) by seaexchmbx03.olympus.F5Net.com ([fe80::f95f:ea5d:773b:29b8%13]) with mapi id 15.00.1044.021; Tue, 24 Mar 2015 08:02:16 -0700
From: Sunil Vallamkonda <sunilvk@f5.com>
To: "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: [sfc] draft-quinn-sfc-nsh: path and metada
Thread-Index: AdBlH/QL90lIwWLyRSqu27N/Eeb3aQ==
Date: Tue, 24 Mar 2015 15:02:16 +0000
Message-ID: <87ad6e6e75df4f1e9d61ce9c024b491a@seaexchmbx03.olympus.F5Net.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.168.15.239]
Content-Type: multipart/alternative; boundary="_000_87ad6e6e75df4f1e9d61ce9c024b491aseaexchmbx03olympusF5Ne_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/khnreAeOm3POfVKAtsAAPoD2RRs>
Subject: [sfc]  draft-quinn-sfc-nsh: path and metada
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 24 Mar 2015 15:02:22 -0000

--_000_87ad6e6e75df4f1e9d61ce9c024b491aseaexchmbx03olympusF5Ne_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Paul,

Re: draft-quinn-sfc-nsh-07

(a)  Sec. 3.5.1 Optional Variable Length Metadata: I propose the Type field=
 to contain flags to indicate if a particular TLV metadata can be: [DD] do =
not discard, [DO] do not overwrite, for downstream nodes in a chain.

(b)  The Sec. 3.3 Service Path Header - SPI: identifies service path. Simil=
arly to include a reverse-path-id for the MDType cases would enable nodes t=
o make decision and monitor, as necessary.


Thank you,
Sunil.


--_000_87ad6e6e75df4f1e9d61ce9c024b491aseaexchmbx03olympusF5Ne_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.EmailStyle20
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1888562775;
	mso-list-type:hybrid;
	mso-list-template-ids:1616420938 -131936428 67698713 67698715 67698703 676=
98713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-number-format:alpha-lower;
	mso-level-text:"\(%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:13.5pt;font-family:&quot;Ti=
mes New Roman&quot;,serif;color:black">Hi Paul,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:13.5pt;font-family:&quot;Ti=
mes New Roman&quot;,serif;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:13.5pt;font-family:&quot;Ti=
mes New Roman&quot;,serif;color:black">Re:
</span><span style=3D"font-size:13.5pt;font-family:&quot;Times New Roman&qu=
ot;,serif">draft-quinn-sfc-nsh-07<span style=3D"color:black"><o:p></o:p></s=
pan></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"font-size:13.5pt;font-family:&q=
uot;Times New Roman&quot;,serif;color:black"><span style=3D"mso-list:Ignore=
">(a)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;
</span></span></span><![endif]><span style=3D"font-size:13.5pt;font-family:=
&quot;Times New Roman&quot;,serif;color:black">Sec. 3.5.1 Optional Variable=
 Length Metadata: I propose the Type field to contain flags to indicate if =
a particular TLV metadata can be: [DD] do not
 discard, [DO] do not overwrite, for downstream nodes in a chain.&nbsp; <o:=
p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"font-size:13.5pt;font-family:&q=
uot;Times New Roman&quot;,serif;color:black"><span style=3D"mso-list:Ignore=
">(b)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;
</span></span></span><![endif]><span style=3D"font-size:13.5pt;font-family:=
&quot;Times New Roman&quot;,serif;color:black">The Sec. 3.3 Service Path He=
ader &#8211; SPI: identifies service path. Similarly to include a reverse-p=
ath-id for the MDType cases would enable nodes to
 make decision and monitor, as necessary.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:13.5pt;font-family:&quot;Ti=
mes New Roman&quot;,serif;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:13.5pt;font-family:&quot;Ti=
mes New Roman&quot;,serif;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:13.5pt;font-family:&quot;Ti=
mes New Roman&quot;,serif;color:black">Thank you,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:13.5pt;font-family:&quot;Ti=
mes New Roman&quot;,serif;color:black">Sunil.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
</div>
</body>
</html>

--_000_87ad6e6e75df4f1e9d61ce9c024b491aseaexchmbx03olympusF5Ne_--


From nobody Tue Mar 24 21:41:30 2015
Return-Path: <nordmark@acm.org>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74EC31ACD97; Tue, 24 Mar 2015 21:41:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=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 Tt7B_bgnJYCA; Tue, 24 Mar 2015 21:41:27 -0700 (PDT)
Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 767531ACD8A; Tue, 24 Mar 2015 21:41:27 -0700 (PDT)
Received: from [31.133.137.136] (dhcp-8988.meeting.ietf.org [31.133.137.136]) (authenticated bits=0) by d.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id t2P4fM9G013233 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 24 Mar 2015 21:41:23 -0700
Message-ID: <55123C72.202@acm.org>
Date: Tue, 24 Mar 2015 23:41:22 -0500
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: "sfc@ietf.org" <sfc@ietf.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Sonic-CAuth: UmFuZG9tSVbfkJ4JkImp9+qTqQike3y/TIiXYHwbHAmh2t/OIXymgvyog/pE09doKd1jfuqH1VqQe6mziE1hatA6MyvaIPy7HRBX9BUp1h0=
X-Sonic-ID: C;+C/6L6nS5BGEAqSqki+G8Q== M;OJKTMKnS5BGEAqSqki+G8Q==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/NHBfRiZF1tDGhZZWJdsR3wgEMJM>
Cc: "rtg-dt-encap-considerations@ietf.org" <Rtg-dt-encap-considerations@ietf.org>
Subject: [sfc] Encapsulation considerations
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 25 Mar 2015 04:41:28 -0000

I don't know to what extent folks are paying attention to RTGWG but I 
presented the report from the encapsulation design team this afternoon.
The draft is
http://datatracker.ietf.org/doc/draft-rtg-dt-encap/
and the slides are at
http://www.ietf.org/proceedings/92/slides/slides-92-rtgwg-8.pdf

There is probably things in there to consider for SFC, and things that 
can be reused to make it easier to move SFC forward.

Sorry for not sending things out to the WG earlier.
    Erik


From nobody Wed Mar 25 08:43:23 2015
Return-Path: <linda.dunbar@huawei.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 932B51B2A65 for <sfc@ietfa.amsl.com>; Wed, 25 Mar 2015 08:43:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 LQb8sgD3H380 for <sfc@ietfa.amsl.com>; Wed, 25 Mar 2015 08:43:20 -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 3986C1B2A64 for <sfc@ietf.org>; Wed, 25 Mar 2015 08:43:19 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BQR87511; Wed, 25 Mar 2015 15:43:17 +0000 (GMT)
Received: from DFWEML706-CHM.china.huawei.com (10.193.5.225) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 25 Mar 2015 15:43:16 +0000
Received: from DFWEML701-CHM.china.huawei.com ([10.193.5.50]) by dfweml706-chm ([10.193.5.225]) with mapi id 14.03.0158.001; Wed, 25 Mar 2015 08:43:06 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: Minutes of the SFC Control Plane side meeting
Thread-Index: AdBnEmej7LVv2yT0R/Sh7vzFd2K1FA==
Date: Wed, 25 Mar 2015 15:43:06 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F657BFB6DD@dfweml701-chm>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.145.153]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F657BFB6DDdfweml701chm_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/N9a_RMqc3wJ7XnTR25KRUAvCWZA>
Cc: "'Jim Guichard \(jguichar\)'" <jguichar@cisco.com>, Thomas Narten <tnarten@us.ibm.com>
Subject: [sfc] Minutes of the SFC Control Plane side meeting
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 25 Mar 2015 15:43:22 -0000

--_000_4A95BA014132FF49AE685FAB4B9F17F657BFB6DDdfweml701chm_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Minutes of the SFC Control Plane side meeting
March 25, 8am-9am

Participants:
Joel Halpern, Jim Guichard, Paul Quinn, Andy Malis, Walter Haeffner, Mohame=
d Boucadair, Qin Wu, James Huang, Seungik Lee, and Linda Dunbar


Agreed:
SFC WG needs to document the overall interfaces for controlling service fun=
ction path.
Agreed the following interfaces for control plane.


SFC  Control Plane  Architecture

                         +-------------+
                         | SF Client   |
                         +------+------+
                                | M1: interface to clients
+--------------------------------------------------------------------+
|SFC Management, compute, and control  components                    |
|                                                                    |     =
                                                               +---------+-=
-------------------------+------------------------------++
          C1                         |C2                            |F2
   +------|--------------------------|---------------------------+  |
   |      |                          |                           |  |
   |      |              +-----------+-------------+             |  |
   |      |              |           |             |             |  |
   | +----+--- --+       |           |             |             |  |
   | |   SFC     |     +----+      +-|--+        +----+          |  |
   | |Classifier |---->|SFF |----->|SFF |------->|SFF |          |  |
   | |   Node    |<----|    |<-----|    |<-------|    |          |  |
   | +-----------+     +----+      +----+        +----+          |  |
   |                     |           |              |            |  |
   |                     |        -------           |            |  |
   |                     |       |       |     +-----------+ F1  |  |
   |                     V     +----+ +----+   | SF  Proxy |-----+  |
   |                           | SF | |SF  |   +-----------+     |  |
   |                           +-+--+ +-+--+                     |  |
   |                             |F     |F                       |  |
   |  SFC Data Plane Components  +------+------------------------+--+
   |                                                             |
   |-------------------------------------------------------------+


The SFC control plane architecture will specify the interfaces for

-          Classifier

-          SFF

-          Service functions (and SF proxy)
And will specify the content to be exchanged over each interface for contro=
lling Service Function Path establishment and alternation due to SFC policy=
 change or SF/network failures.

We are looking for comments from the community with regard to this proposed=
 SFC control plane architecture.

Agreed that IETF 93 Prague meeting will allocate a dedicated slot for contr=
ol plane discussion.

Cheers,

Linda Dunbar

--_000_4A95BA014132FF49AE685FAB4B9F17F657BFB6DDdfweml701chm_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1315455673;
	mso-list-type:hybrid;
	mso-list-template-ids:843604710 565462096 67698691 67698693 67698689 67698=
691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.75in;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:SimSun;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><u><spa=
n style=3D"font-size:12.0pt;color:black">Minutes of the SFC Control Plane s=
ide meeting<o:p></o:p></span></u></p>
<p class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span s=
tyle=3D"font-size:12.0pt;color:black">March 25, 8am-9am<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;color:black">Partici=
pants: <o:p>
</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
12.0pt;color:black">Joel Halpern, Jim Guichard, Paul Quinn, Andy Malis, Wal=
ter Haeffner, Mohamed Boucadair, Qin Wu, James Huang, Seungik Lee, and Lind=
a Dunbar<o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><u><span style=3D"font-size:12.0pt;color:black"><=
o:p><span style=3D"text-decoration:none">&nbsp;</span></o:p></span></u></b>=
</p>
<p class=3D"MsoNormal"><b><u><span style=3D"font-size:12.0pt;color:black"><=
o:p><span style=3D"text-decoration:none">&nbsp;</span></o:p></span></u></b>=
</p>
<p class=3D"MsoNormal"><b><u><span style=3D"font-size:12.0pt;color:black">A=
greed: <o:p>
</o:p></span></u></b></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
12.0pt;color:black">SFC WG needs to document the overall interfaces for con=
trolling service function path.
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
12.0pt;color:black">Agreed the following interfaces for control plane.
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.25in"><span style=3D"color:bla=
ck"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.25in"><span style=3D"color:bla=
ck"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.25in"><span style=3D"font-size=
:10.0pt;font-family:&quot;Courier New&quot;">SFC&nbsp; Control Plane&nbsp; =
Architecture
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
10.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in;page-break-after:avoid"><s=
pan style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;--------=
-----&#43;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in;page-break-after:avoid"><s=
pan style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;| SF Cli=
ent&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in;page-break-after:avoid"><s=
pan style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;------&#=
43;------&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in;page-break-after:avoid"><s=
pan style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:#1F=
497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|
</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;"=
>M1: interface to clients</span><span style=3D"font-size:10.0pt;font-family=
:&quot;Courier New&quot;;color:#1F497D">
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;">&#43;--------------------=
------------------------------------------------&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;">|SFC Management, compute,=
 and control&nbsp; components&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;">|&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;---------&#43;-----------------------=
---&#43;------------------------------&#43;&#43;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |C2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |F2<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; &#43;------|=
--------------------------|---------------------------&#43;&nbsp; |
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;|&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; &#43;-----------&#43;-------------&#43;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; |<o:p=
></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; |&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; | &#43;----&=
#43;--- --&#43;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; | |&nbsp;&nb=
sp; SFC&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp; &#43;----&#43;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;-|--&#43;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; &#43;----&#43;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; |&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; | |Classifie=
r |----&gt;|SFF |-----&gt;|SFF |-------&gt;|SFF |&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; | |&nbsp;&nb=
sp; Node&nbsp;&nbsp;&nbsp; |&lt;----|&nbsp;&nbsp;&nbsp; |&lt;-----|&nbsp;&n=
bsp;&nbsp; |&lt;-------|&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; | &#43;-----=
------&#43;&nbsp;&nbsp;&nbsp;&nbsp; &#43;----&#43;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; &#43;----&#43;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;----&#4=
3;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; |<o:p></o:=
p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; |&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; -------&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; |<=
o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp; &#43;--------=
---&#43; F1&nbsp; |&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; V&nbsp;&nbsp;&nbsp;&nbsp; &#43;----&#43;=
 &#43;----&#43;&nbsp;&nbsp; | SF&nbsp; Proxy |-----&#43;&nbsp; |&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;|&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 | SF | |SF&nbsp; |&nbsp;&nbsp; &#43;-----------&#43;&nbsp;&nbsp;&nbsp;&nbs=
p; |&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43=
;-&#43;--&#43; &#43;-&#43;--&#43;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; |&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; |F&nbsp;&nbsp;&nbsp;&nbsp; |F&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; |&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |&nbsp; SFC =
Data Plane Components&nbsp; &#43;------&#43;------------------------&#43;--=
&#43;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;|&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; |-----------=
--------------------------------------------------&#43;<o:p></o:p></span></=
p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"color:#1F4=
97D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"color:#1F4=
97D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
12.0pt;color:black">The SFC control plane architecture will specify the int=
erfaces for
<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in;text-indent:-.25in=
;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style=3D"font-size:12.0pt;color:black"><span sty=
le=3D"mso-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quo=
t;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:12.0pt;color:black"=
>Classifier<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in;text-indent:-.25in=
;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style=3D"font-size:12.0pt;color:black"><span sty=
le=3D"mso-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quo=
t;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:12.0pt;color:black"=
>SFF<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in;text-indent:-.25in=
;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style=3D"font-size:12.0pt;color:black"><span sty=
le=3D"mso-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quo=
t;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:12.0pt;color:black"=
>Service functions (and SF proxy)<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
12.0pt;color:black">And will specify the content to be exchanged over each =
interface for controlling Service Function Path establishment and alternati=
on due to SFC policy change or SF/network
 failures.&nbsp; <o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"color:#1F4=
97D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">We are looking for =
comments from the community with regard to this proposed SFC control plane =
architecture.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">Agreed that IETF 93=
 Prague meeting will allocate a dedicated slot for control plane discussion=
.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">Cheers, <o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">Linda Dunbar<o:p></=
o:p></span></p>
</div>
</body>
</html>

--_000_4A95BA014132FF49AE685FAB4B9F17F657BFB6DDdfweml701chm_--


From nobody Thu Mar 26 12:31:15 2015
Return-Path: <jiangyuanlong@huawei.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE3D51B2B38 for <sfc@ietfa.amsl.com>; Thu, 26 Mar 2015 12:31:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 AMhxRQP2gj-6 for <sfc@ietfa.amsl.com>; Thu, 26 Mar 2015 12:31:11 -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 696C91B2DA4 for <sfc@ietf.org>; Thu, 26 Mar 2015 12:31:06 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml403-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BQT09040; Thu, 26 Mar 2015 19:31:04 +0000 (GMT)
Received: from SZXEMA412-HUB.china.huawei.com (10.82.72.71) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 26 Mar 2015 19:31:04 +0000
Received: from SZXEMA506-MBS.china.huawei.com ([169.254.4.68]) by SZXEMA412-HUB.china.huawei.com ([10.82.72.71]) with mapi id 14.03.0158.001; Fri, 27 Mar 2015 03:30:53 +0800
From: Jiangyuanlong <jiangyuanlong@huawei.com>
To: "Reinaldo Penno (repenno)" <repenno@cisco.com>, "draft-penno-sfc-trace@tools.ietf.org" <draft-penno-sfc-trace@tools.ietf.org>
Thread-Topic: SFC Traceroute
Thread-Index: AQHQZb3rjJcOOUoim0SjDGde3At9b50vJ6Hw
Date: Thu, 26 Mar 2015 19:30:53 +0000
Message-ID: <3B0A1BED22CAD649A1B3E97BE5DDD68B5A8C472E@szxema506-mbs.china.huawei.com>
References: <D136064A.DB64%repenno@cisco.com>
In-Reply-To: <D136064A.DB64%repenno@cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.46.100.52]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/FmLI-TCBtEkCfqzxOfCBTmLn2M0>
Cc: Zhen Cao <zehn.cao@gmail.com>, "draft-jxc-sfc-fm@tools.ietf.org" <draft-jxc-sfc-fm@tools.ietf.org>, "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [sfc] SFC Traceroute
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 26 Mar 2015 19:31:13 -0000

Hi authors,

SFC Tracing is quite an important topic if SFC is to be deployed with any m=
onitoring capability. So we are glad to see more interests in this field.

Some issues in this I-D:
1. No discussion or references are given with regard to SFC tracing require=
ments.=20
2. There are some inconsistencies between the texts regarding Service Funct=
ion Forwarder Behavior in Section 5 and the ODL trace implementation as des=
cribed in Section 6. For example, "Address of Reporting SFF" is reported in=
 the implementation, but when and how this address is carried in the trace =
report is not mentioned in the document.

We happened to have posted draft-jxc-sfc-fm almost a year ago, and describe=
d a mechanism similar to the ODL trace implementation in Section 3.2 "SFC R=
oute Tracing" of draft-jxc-sfc-fm, that is, both SFs and SFFs are recorded =
in a trace reply message.=20

Maybe we can work together to move it forward.

Thanks,
Yuanlong

-----Original Message-----
From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of Reinaldo Penno (repenn=
o)
Sent: Tuesday, March 24, 2015 7:06 AM
To: sfc@ietf.org
Subject: [sfc] SFC Traceroute

New version of SFC Traceroute.

Thanks to those in the hackathon that tested it.


On 3/23/15, 6:03 PM, "internet-drafts@ietf.org" <internet-drafts@ietf.org>
wrote:

>
>A new version of I-D, draft-penno-sfc-trace-02.txt has been=20
>successfully submitted by Reinaldo Penno and posted to the IETF=20
>repository.
>
>Name:		draft-penno-sfc-trace
>Revision:	02
>Title:		Services Function Chaining Traceroute
>Document date:	2015-03-23
>Group:		Individual Submission
>Pages:		9
>URL:           =20
>http://www.ietf.org/internet-drafts/draft-penno-sfc-trace-02.txt
>Status:         https://datatracker.ietf.org/doc/draft-penno-sfc-trace/
>Htmlized:       http://tools.ietf.org/html/draft-penno-sfc-trace-02
>Diff:           http://www.ietf.org/rfcdiff?url2=3Ddraft-penno-sfc-trace-0=
2
>
>Abstract:
>   This document defines a protocol that checks the liveness and report
>   the service-hops of a service path. .
>
>
>                 =20
>       =20
>
>
>Please note that it may take a couple of minutes from the time of=20
>submission until the htmlized version and diff are available at=20
>tools.ietf.org.
>
>The IETF Secretariat
>

_______________________________________________
sfc mailing list
sfc@ietf.org
https://www.ietf.org/mailman/listinfo/sfc


From nobody Sat Mar 28 18:18:37 2015
Return-Path: <jguichar@cisco.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39DF21A911A for <sfc@ietfa.amsl.com>; Sat, 28 Mar 2015 18:18:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.611
X-Spam-Level: 
X-Spam-Status: No, score=-12.611 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 6Q91NnIcEXpw for <sfc@ietfa.amsl.com>; Sat, 28 Mar 2015 18:18:34 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13AB81A9116 for <sfc@ietf.org>; Sat, 28 Mar 2015 18:18:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=28134; q=dns/txt; s=iport; t=1427591914; x=1428801514; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=pZSThrNf0OAiKGsN0kYK/vMbVURtIpufCOaIHaKM8CE=; b=BowD1xgs+zRIh9/ZfPnedpZrv3+sna5XAsRLx58jXsCnpyVnBM5imI6D 2zpALoxA7ZPl5bsRZ7AYLMLvG3dJhmtOAC2BseJ10h2J49nMKF32Fkwsf C09z6nIOiga6pylrqOFArhOabJmvR/UsHcUKyXI21RgsfDP2P+F/kgiV+ s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BVBQCqaeJU/4ENJK1bgkNDUloEyC0CgRhDAQEBAQEBfIQMAQEBBCcGTBACAQgRAQIBAiEBBgcyFAMGCAEBBAENBRSIGc41AQEBAQEBAQEBAQEBAQEBAQEBAQEBF4sMhFwRBgGEKgWFWoleiTeTDSKCAhyBUG+BRH8BAQE
X-IronPort-AV: E=Sophos;i="5.11,486,1422921600";  d="scan'208,217";a="407205302"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-8.cisco.com with ESMTP; 29 Mar 2015 01:18:33 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id t2T1IXWf024066 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 29 Mar 2015 01:18:33 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.104]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.03.0195.001; Sat, 28 Mar 2015 20:18:32 -0500
From: "Jim Guichard (jguichar)" <jguichar@cisco.com>
To: Linda Dunbar <linda.dunbar@huawei.com>, "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: Minutes of the SFC Control Plane side meeting
Thread-Index: AdBnEmej7LVv2yT0R/Sh7vzFd2K1FACtD4sA
Date: Sun, 29 Mar 2015 01:18:32 +0000
Message-ID: <D13CCA0B.DA29%jguichar@cisco.com>
References: <4A95BA014132FF49AE685FAB4B9F17F657BFB6DD@dfweml701-chm>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F657BFB6DD@dfweml701-chm>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.7.141117
x-originating-ip: [10.98.43.184]
Content-Type: multipart/alternative; boundary="_000_D13CCA0BDA29jguicharciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sfc/OAv1pMgXXhK66K-hTEbPMH6KXRE>
Cc: Thomas Narten <tnarten@us.ibm.com>
Subject: Re: [sfc] Minutes of the SFC Control Plane side meeting
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sun, 29 Mar 2015 01:18:36 -0000

--_000_D13CCA0BDA29jguicharciscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi Linda,

Thank you for these minutes. However, a couple of clarification.

  1.  We agreed that our charter calls for "Informational document defining=
 the control plane requirements for conveying information between control o=
r management elements and SFC implementation points=94. This means we need =
to work on the requirements for any interfaces and not work on the interfac=
es themselves.
  2.  We agreed to document what information might need to be exchanged but=
 did not agree to actually define specific content.

Jim

From: Linda Dunbar <linda.dunbar@huawei.com<mailto:linda.dunbar@huawei.com>=
>
Date: Wednesday, March 25, 2015 at 11:43 AM
To: "sfc@ietf.org<mailto:sfc@ietf.org>" <sfc@ietf.org<mailto:sfc@ietf.org>>
Cc: Jim Guichard <jguichar@cisco.com<mailto:jguichar@cisco.com>>, Thomas Na=
rten <tnarten@us.ibm.com<mailto:tnarten@us.ibm.com>>
Subject: Minutes of the SFC Control Plane side meeting

Minutes of the SFC Control Plane side meeting
March 25, 8am-9am

Participants:
Joel Halpern, Jim Guichard, Paul Quinn, Andy Malis, Walter Haeffner, Mohame=
d Boucadair, Qin Wu, James Huang, Seungik Lee, and Linda Dunbar


Agreed:
SFC WG needs to document the overall interfaces for controlling service fun=
ction path.
Agreed the following interfaces for control plane.


SFC  Control Plane  Architecture

                         +-------------+
                         | SF Client   |
                         +------+------+
                                | M1: interface to clients
+--------------------------------------------------------------------+
|SFC Management, compute, and control  components                    |
|                                                                    |     =
                                                               +---------+-=
-------------------------+------------------------------++
          C1                         |C2                            |F2
   +------|--------------------------|---------------------------+  |
   |      |                          |                           |  |
   |      |              +-----------+-------------+             |  |
   |      |              |           |             |             |  |
   | +----+--- --+       |           |             |             |  |
   | |   SFC     |     +----+      +-|--+        +----+          |  |
   | |Classifier |---->|SFF |----->|SFF |------->|SFF |          |  |
   | |   Node    |<----|    |<-----|    |<-------|    |          |  |
   | +-----------+     +----+      +----+        +----+          |  |
   |                     |           |              |            |  |
   |                     |        -------           |            |  |
   |                     |       |       |     +-----------+ F1  |  |
   |                     V     +----+ +----+   | SF  Proxy |-----+  |
   |                           | SF | |SF  |   +-----------+     |  |
   |                           +-+--+ +-+--+                     |  |
   |                             |F     |F                       |  |
   |  SFC Data Plane Components  +------+------------------------+--+
   |                                                             |
   |-------------------------------------------------------------+


The SFC control plane architecture will specify the interfaces for

-          Classifier

-          SFF

-          Service functions (and SF proxy)
And will specify the content to be exchanged over each interface for contro=
lling Service Function Path establishment and alternation due to SFC policy=
 change or SF/network failures.

We are looking for comments from the community with regard to this proposed=
 SFC control plane architecture.

Agreed that IETF 93 Prague meeting will allocate a dedicated slot for contr=
ol plane discussion.

Cheers,

Linda Dunbar

--_000_D13CCA0BDA29jguicharciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <330193E8B336D54DBC678A37FD001FDB@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;">
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
Hi Linda,</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
Thank you for these minutes. However, a couple of clarification.</div>
<ol>
<li><font face=3D"Calibri,sans-serif">We agreed that our charter calls for =
&quot;</font><span style=3D"widows: 1;"><font face=3D"arial,helvetica,clean=
,sans-serif"><span style=3D"font-size: 13px; line-height: 17.7811088562012p=
x;">Informational document defining the control
 plane requirements for conveying information between control or management=
 elements and SFC implementation points</span><span style=3D"font-size: 13p=
x; line-height: 17px;">=94</span><span style=3D"font-size: 13px; line-heigh=
t: 17.7811088562012px;">. This means we
 need to work on the requirements for any interfaces and not work on the in=
terfaces themselves.</span></font></span></li><li><span style=3D"widows: 1;=
"><font face=3D"arial,helvetica,clean,sans-serif"><span style=3D"font-size:=
 13px; line-height: 17.7811088562012px;">We agreed to document what informa=
tion might need to be exchanged but did not agree to actually define specif=
ic content.</span></font></span></li></ol>
<div><span style=3D"color: rgb(0, 0, 0); font-family: arial, helvetica, cle=
an, sans-serif; font-size: 13px; font-style: normal; font-weight: normal; t=
ext-decoration: none;"><br>
</span></div>
<div><span style=3D"color: rgb(0, 0, 0); font-family: arial, helvetica, cle=
an, sans-serif; font-size: 13px; font-style: normal; font-weight: normal; t=
ext-decoration: none;">Jim</span></div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0); font-family=
: Calibri, sans-serif; font-size: 14px;">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>Linda Dunbar &lt;<a href=3D"m=
ailto:linda.dunbar@huawei.com">linda.dunbar@huawei.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Wednesday, March 25, 2015 at =
11:43 AM<br>
<span style=3D"font-weight:bold">To: </span>&quot;<a href=3D"mailto:sfc@iet=
f.org">sfc@ietf.org</a>&quot; &lt;<a href=3D"mailto:sfc@ietf.org">sfc@ietf.=
org</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>Jim Guichard &lt;<a href=3D"mai=
lto:jguichar@cisco.com">jguichar@cisco.com</a>&gt;, Thomas Narten &lt;<a hr=
ef=3D"mailto:tnarten@us.ibm.com">tnarten@us.ibm.com</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Minutes of the SFC Control=
 Plane side meeting<br>
</div>
<div><br>
</div>
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1315455673;
	mso-list-type:hybrid;
	mso-list-template-ids:843604710 565462096 67698691 67698693 67698689 67698=
691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.75in;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:SimSun;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><u><spa=
n style=3D"font-size:12.0pt;color:black">Minutes of the SFC Control Plane s=
ide meeting<o:p></o:p></span></u></p>
<p class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span s=
tyle=3D"font-size:12.0pt;color:black">March 25, 8am-9am<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;color:black">Partici=
pants: <o:p>
</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
12.0pt;color:black">Joel Halpern, Jim Guichard, Paul Quinn, Andy Malis, Wal=
ter Haeffner, Mohamed Boucadair, Qin Wu, James Huang, Seungik Lee, and Lind=
a Dunbar<o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><u><span style=3D"font-size:12.0pt;color:black"><=
o:p><span style=3D"text-decoration:none">&nbsp;</span></o:p></span></u></b>=
</p>
<p class=3D"MsoNormal"><b><u><span style=3D"font-size:12.0pt;color:black"><=
o:p><span style=3D"text-decoration:none">&nbsp;</span></o:p></span></u></b>=
</p>
<p class=3D"MsoNormal"><b><u><span style=3D"font-size:12.0pt;color:black">A=
greed: <o:p>
</o:p></span></u></b></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
12.0pt;color:black">SFC WG needs to document the overall interfaces for con=
trolling service function path.
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
12.0pt;color:black">Agreed the following interfaces for control plane.
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.25in"><span style=3D"color:bla=
ck"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.25in"><span style=3D"color:bla=
ck"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.25in"><span style=3D"font-size=
: 10pt; font-family: 'Courier New';">SFC&nbsp; Control Plane&nbsp; Architec=
ture
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
 10pt; font-family: 'Courier New';"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in;page-break-after:avoid"><s=
pan style=3D"font-size: 10pt; font-family: 'Courier New';">&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;-------------&#4=
3;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in;page-break-after:avoid"><s=
pan style=3D"font-size: 10pt; font-family: 'Courier New';">&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;| SF Client&nbsp=
;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in;page-break-after:avoid"><s=
pan style=3D"font-size: 10pt; font-family: 'Courier New';">&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;------&#43;-----=
-&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in;page-break-after:avoid"><s=
pan style=3D"font-size: 10pt; font-family: 'Courier New'; color: rgb(31, 73=
, 125);">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|
</span><span style=3D"font-size: 10pt; font-family: 'Courier New';">M1: int=
erface to clients</span><span style=3D"font-size: 10pt; font-family: 'Couri=
er New'; color: rgb(31, 73, 125);"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size: 10pt; font-family: 'Courier New';">&#43;----------------------------=
----------------------------------------&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size: 10pt; font-family: 'Courier New';">|SFC Management, compute, and con=
trol&nbsp; components&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<o:p></o:p></=
span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size: 10pt; font-family: 'Courier New';">|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; &#43;---------&#43;--------------------------&#43;=
------------------------------&#43;&#43;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size: 10pt; font-family: 'Courier New';">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;C1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; |C2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |F2<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size: 10pt; font-family: 'Courier New';">&nbsp;&nbsp; &#43;------|--------=
------------------|---------------------------&#43;&nbsp; |
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size: 10pt; font-family: 'Courier New';">&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size: 10pt; font-family: 'Courier New';">&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; &#43;-----------&#43;-------------&#43;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; |<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size: 10pt; font-family: 'Courier New';">&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; |&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size: 10pt; font-family: 'Courier New';">&nbsp;&nbsp; | &#43;----&#43;--- =
--&#43;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size: 10pt; font-family: 'Courier New';">&nbsp;&nbsp; | |&nbsp;&nbsp; SFC&=
nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp; &#43;----&#43;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; &#43;-|--&#43;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; &#43;----&#43;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nb=
sp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size: 10pt; font-family: 'Courier New';">&nbsp;&nbsp; | |Classifier |----&=
gt;|SFF |-----&gt;|SFF |-------&gt;|SFF |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; |&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size: 10pt; font-family: 'Courier New';">&nbsp;&nbsp; | |&nbsp;&nbsp; Node=
&nbsp;&nbsp;&nbsp; |&lt;----|&nbsp;&nbsp;&nbsp; |&lt;-----|&nbsp;&nbsp;&nbs=
p; |&lt;-------|&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; |&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size: 10pt; font-family: 'Courier New';">&nbsp;&nbsp; | &#43;-----------&#=
43;&nbsp;&nbsp;&nbsp;&nbsp; &#43;----&#43;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#=
43;----&#43;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;----&#43;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; |<o:p></o:p></span=
></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size: 10pt; font-family: 'Courier New';">&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp; |&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size: 10pt; font-family: 'Courier New';">&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ----=
---&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; |<o:p></o:=
p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size: 10pt; font-family: 'Courier New';">&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp; &#43;-----------&#43;=
 F1&nbsp; |&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size: 10pt; font-family: 'Courier New';">&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; V&nbsp;&nbsp;&nbsp;&nbsp; &#43;----&#43; &#43;--=
--&#43;&nbsp;&nbsp; | SF&nbsp; Proxy |-----&#43;&nbsp; |&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size: 10pt; font-family: 'Courier New';">&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | SF | =
|SF&nbsp; |&nbsp;&nbsp; &#43;-----------&#43;&nbsp;&nbsp;&nbsp;&nbsp; |&nbs=
p; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size: 10pt; font-family: 'Courier New';">&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;-&#43;-=
-&#43; &#43;-&#43;--&#43;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nb=
sp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size: 10pt; font-family: 'Courier New';">&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|F&nbsp;&nbsp;&nbsp;&nbsp; |F&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp; |&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size: 10pt; font-family: 'Courier New';">&nbsp;&nbsp; |&nbsp; SFC Data Pla=
ne Components&nbsp; &#43;------&#43;------------------------&#43;--&#43;&nb=
sp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size: 10pt; font-family: 'Courier New';">&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-after:avoid"><span style=3D"font=
-size: 10pt; font-family: 'Courier New';">&nbsp;&nbsp; |-------------------=
------------------------------------------&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"color:#1F4=
97D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"color:#1F4=
97D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
12.0pt;color:black">The SFC control plane architecture will specify the int=
erfaces for
<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in;text-indent:-.25in=
;mso-list:l0 level1 lfo1">
<!--[if !supportLists]--><span style=3D"font-size:12.0pt;color:black"><span=
 style=3D"mso-list:Ignore">-<span style=3D"font-style: normal; font-variant=
: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-fa=
mily: 'Times New Roman';">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
</span></span></span><!--[endif]--><span style=3D"font-size:12.0pt;color:bl=
ack">Classifier<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in;text-indent:-.25in=
;mso-list:l0 level1 lfo1">
<!--[if !supportLists]--><span style=3D"font-size:12.0pt;color:black"><span=
 style=3D"mso-list:Ignore">-<span style=3D"font-style: normal; font-variant=
: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-fa=
mily: 'Times New Roman';">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
</span></span></span><!--[endif]--><span style=3D"font-size:12.0pt;color:bl=
ack">SFF<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.75in;text-indent:-.25in=
;mso-list:l0 level1 lfo1">
<!--[if !supportLists]--><span style=3D"font-size:12.0pt;color:black"><span=
 style=3D"mso-list:Ignore">-<span style=3D"font-style: normal; font-variant=
: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-fa=
mily: 'Times New Roman';">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
</span></span></span><!--[endif]--><span style=3D"font-size:12.0pt;color:bl=
ack">Service functions (and SF proxy)<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
12.0pt;color:black">And will specify the content to be exchanged over each =
interface for controlling Service Function Path establishment and alternati=
on due to SFC policy change or SF/network
 failures.&nbsp; <o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"color:#1F4=
97D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">We are looking for =
comments from the community with regard to this proposed SFC control plane =
architecture.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">Agreed that IETF 93=
 Prague meeting will allocate a dedicated slot for control plane discussion=
.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">Cheers, <o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">Linda Dunbar<o:p></=
o:p></span></p>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_D13CCA0BDA29jguicharciscocom_--

