Return-Path: <hayabusagsm@gmail.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
 by ietfa.amsl.com (Postfix) with ESMTP id B2CAF120019
 for <spring@ietfa.amsl.com>; Sat, 14 Dec 2019 23:06:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 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, HTML_MESSAGE=0.001,
 RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001,
 URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key)
 header.d=gmail.com
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 tUFJFbRDPD0z for <spring@ietfa.amsl.com>;
 Sat, 14 Dec 2019 23:06:45 -0800 (PST)
Received: from mail-il1-x132.google.com (mail-il1-x132.google.com
 [IPv6:2607:f8b0:4864:20::132])
 (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 1EC4F120005
 for <spring@ietf.org>; Sat, 14 Dec 2019 23:06:45 -0800 (PST)
Received: by mail-il1-x132.google.com with SMTP id p8so2877940iln.12
 for <spring@ietf.org>; Sat, 14 Dec 2019 23:06:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; 
 h=mime-version:references:in-reply-to:from:date:message-id:subject:to
 :cc; bh=RLX+XUWi2asMXB+yAOVBH0z6ywZFc36ZOA3taHD94js=;
 b=TnoN/Rz3+Fmr5ZjuQbLxqpWbyJNM8/qmpgIEAI53/EANujmNf23UlW6wVND5GjQqxM
 4TKcQ9Un20dPZB48doZJrMPzyh5NDpbUb7hEJie9mISJNm6LMaQr25MLdjnzAWQkj6eL
 5nPp+06GBPqQV8VFzVdjT4MdhffB+FGHBIHeEQwwIPT797CoR7g4DAeiO6ixHjVSLIf/
 a8A6c5t75YW5RSaXqL4zQv5M6F5lyCSr/O0/UcFKi2Xi8hwD87nSvkZvRqGIVKEfy8ml
 UazwgnJyIxXS9n16fSOVUrqCJHPTbWfU+xXiW39QWPYLNOYaDwQn6gp+3s6RnZ5auYWp
 EXiw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to:cc;
 bh=RLX+XUWi2asMXB+yAOVBH0z6ywZFc36ZOA3taHD94js=;
 b=nvAJdwmH6Ee89u3QrzS/GnoH/Bv9y+DlfNFwUm3Zu4IHrZUuZVB/AdGM2v/BHjzKHG
 I2iABw+RS/3K8SeI2LsjjaRCZDt2MBpsGduxGAbVN9IPvBnm0mxjyvPb5dxq90UbzS+j
 h69B5hgK5zo3VZi/34d24GNfKYCCuvfLbmz0yPvJAZ69K7Qz7dtV8jFlA2z/kXCL2Hwt
 1DOUJOmfX0/YBSQu9dxzT4xrE+tgMB8nZR3ERPMr8BgGc/H138P+Da7+a6Ap3fnmwmPi
 QmptidyFb7Un0Mq3GL3YR1NkjMknnbSkfFIH3eu+UgcRVN6SCV/L0bJWVF5tlyJ9dyMt
 M4SQ==
X-Gm-Message-State: APjAAAUzqs7M2Jx9me0QfnmFBTYgV7J6sLBq9AoZwLQyGCpkf/8VvbgH
 ZTOQq4wPPBffIEqKyEnFx1WJbtO7K0JIM+uny8w=
X-Google-Smtp-Source: APXvYqyfxHMDV0NgdNeiBUVB+l3hRtn7cSxj6a9zThrLrwjhIg526CcMAB7rcvc5wmm7d4vmqKFyOKOh8G+Kv1mE9Gc=
X-Received: by 2002:a92:350d:: with SMTP id c13mr7616794ila.205.1576393604229; 
 Sat, 14 Dec 2019 23:06:44 -0800 (PST)
MIME-Version: 1.0
References: <8532651c71c94715abfa96990aec3854@nokia-sbell.com>
In-Reply-To: <8532651c71c94715abfa96990aec3854@nokia-sbell.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Sun, 15 Dec 2019 02:06:33 -0500
Message-ID: <CABNhwV1FpyLFcZicFBxjE74WGUhAzkwFgzrn7_jLxm5OTO0XgQ@mail.gmail.com>
To: "Wang, Weibin (NSB - CN/Shanghai)" <weibin.wang@nokia-sbell.com>
Cc: "Pablo Camarillo (pcamaril)" <pcamaril@cisco.com>,
 "spring@ietf.org" <spring@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ce7d3f0599b8bcf8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/qiAeE_xuJA7CObaybi83XqecXao>
Subject: Re: [spring] USD/USP question in
 draft-ietf-spring-srv6-network-programming-06.txt
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>,
 <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>,
 <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Dec 2019 07:06:48 -0000

--000000000000ce7d3f0599b8bcf8
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Wang

I have a question regarding the PSP, USP and USD sections I pasted below.

I just sent an email to Spring WG related to PSP and technically why that
is necessary as that is a legacy concept that has parity to MPLS but is not
used today due to QOS issues.  Please see that email related to that topic.


In the PSP section can If we have to keep PSP can we add verbiage that
states that PSP removal of the SRH header occurs on the Penultimate egress
P node.

In the USP section can we also add that all remaining SRH present in the
packet are popped on the egress PE ultimate node.

In looking at these 3 SID functions the PSP and USP pop the EH and the USP
removes the 6in6 encapsulation so that the other end.x dt4 dt6 etc can pop
the services L3vpn headers.

Why can=E2=80=99t the USD 6in6 encapsulation removal be done on with the US=
P SID?

Why does the USP and USD SID have to be separate?

4.16.1 <https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programm=
ing-05#section-4.16.1>.
PSP: Penultimate Segment Pop of the SRH

   The SRH processing of the End, End.X and End.T behaviors are
   modified: after the instruction "S14.  Update IPv6 DA with Segment
   List[Segments Left]" is executed, the following instructions must be
   executed as well:

   S14.1.   If (updated SL =3D=3D 0) {
   S14.2.      Pop the SRH
   S14.3.   }
4.16.2 <https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programm=
ing-05#section-4.16.2>.
USP: Ultimate Segment Pop of the SRH

   The SRH processing of the End, End.X and End.T behaviors are
   modified: the instructions S02-S04 are substituted by the following
   ones:

   S02.   If (Segments Left =3D=3D 0) {
   S03.       Pop the SRH
   S04.   }

4.16.3 <https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programm=
ing-05#section-4.16.3>.
USD: Ultimate Segment Decapsulation


   The SRH processing of the End, End.X and End.T behaviors are
   modified: the instructions S02-S04 are substituted by the following
   ones:

   S02.   If (Segments Left =3D=3D 0) {
   S03.      Skip the SRH processing and proceed to the next header
   S04.   }


   Further on, the Upper-layer header processing of the End, End.X and
   End.T behaviors are modified as follows:



Kind regards,


Gyan


On Sat, Dec 14, 2019 at 9:08 PM Wang, Weibin (NSB - CN/Shanghai) <
weibin.wang@nokia-sbell.com> wrote:

> Hi Pablo:
>
>
>
> After the 2 context assumption in previous version of this draft,  =E2=80=
=9Cwe
> assume that there is no other extension header than the SRH.=E2=80=9D  an=
d  =E2=80=9CWe
> assume
>
>    that the SRH may be present multiple times inside each packet=E2=80=9D=
, are
> removed in this last draft, I feel a bit confusion on USD SID, as well as
> combination of USD & USP.
>
>
>
> First, within the content of this last draft, the word =E2=80=9CFurther o=
n=E2=80=9D marked
> red in the following pseudocode in section =E2=80=9C4.16.3=E2=80=9D is ha=
rd to understand
> if the packet being processed has other EH embed between SRH and
> Upper-layer header, such as AH or other EH, then the processing control o=
f
> this packet will be passed to normal IPv6 module from current SRH
> processing module in SR-Node, so my question is : Can its control after
> completing AH processing (for example)  be back to SRH module (or call it
> pseudocode module) to proceed the next header like =E2=80=9Cupper-lay hea=
der type
> =3D=3D41 or 4=E2=80=9D.
>
> Or, if not, Did you created a new EH processing protocol stack instance i=
n
> parallel to normal IPv6 module within the scope of SRH processing in
> SR-node.
>
>
>
> 4.16.3.  USD: Ultimate Segment Decapsulation
>
>
>
> S02.   If (Segments Left =3D=3D 0) {
>
>    S03.      Skip the SRH processing and proceed to the next header
>
>    S04.   }
>
>
>
> Further on, the Upper-layer header processing of the End, End.X and
>
>    End.T behaviors are modified as follows:
>
>
>
>    End:
>
>    S01. If (Upper-layer Header type =3D=3D 41 || 4) {
>
>    S02.    Remove the outer IPv6 Header with all its extension headers
>
>    S03.    Submit the packet to the egress IP FIB lookup and
>
>               transmission to the new destination
>
>    S04. } Else {
>
>    S05.    Send an ICMP Parameter Problem message to the Source Address
>
>               Code 4 (SR Upper-layer Header Error),
>
>               Pointer set to the offset of the upper-layer header.
>
>               Interrupt packet processing and discard the packet.
>
>
>
>    S06. }
>
>
>
> From my understanding, the all processing action about specific SID must
> be completed successively. That is to say, upon USD, the upper-layer head=
er
> (type 41 or 4) must be followed the SRH header being processed currently,
> or second SRH following the same rule (of course, the draft not consideri=
ng
> 2 or more successive SRHs).
>
>
>
> Second, the mixed SIDs function with combination of USD and USP (even
> PSP&USD&USP), I think, it is easy to understand when the two assumption
> above exist, but now I think it isn=E2=80=99t clear if you only provide t=
he
> following sentence in this draft, i.e.  =E2=80=9Cif =E2=80=A6 else=E2=80=
=A6=E2=80=9D statement:
>
> =E2=80=9CAn implementation that supports the USD flavor in conjunction wi=
th
>
>    the USP flavor MAY optimize the packet processing by first looking
>
>    whether the conditions for the USD flavor are met, in which case it
>
>    can proceed with USD processing else do USP processing.=E2=80=9D
>
> This confusion is also described in my another mail. Of course, if the
> first question is addressed then this confusion does not exist.
>
>
>
> By the way, is it really no different in text description before and afte=
r
> the two context assumption above removed?
>
>
>
>
>
> *Cheers !*
>
>
>
> *WANG Weibin*
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>
--=20

Gyan S. Mishra

IT Network Engineering & Technology

Verizon Communications Inc. (VZ)

13101 Columbia Pike FDC1 3rd Floor

Silver Spring, MD 20904

United States

Phone: 301 502-1347

Email: gyan.s.mishra@verizon.com

www.linkedin.com/in/networking-technologies-consultant

--000000000000ce7d3f0599b8bcf8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div><div style=3D"color:rgb(49,49,49);word-spacing:1px" dir=3D"auto"><div =
dir=3D"auto" style=3D"font-size:1rem">Hi Wang</div></div><div dir=3D"auto" =
style=3D"color:rgb(49,49,49);word-spacing:1px"><br></div><div dir=3D"auto" =
style=3D"font-size:1rem;color:rgb(49,49,49);word-spacing:1px">I have a ques=
tion regarding the PSP, USP and USD sections I pasted below.</div><div dir=
=3D"auto" style=3D"color:rgb(49,49,49);word-spacing:1px"><br></div><div dir=
=3D"auto" style=3D"font-size:1rem;color:rgb(49,49,49);word-spacing:1px">I j=
ust sent an email to Spring WG related to PSP and technically why that is n=
ecessary as that is a legacy concept that has parity to MPLS but is not use=
d today due to QOS issues.=C2=A0 Please see that email related to that topi=
c.</div><div dir=3D"auto" style=3D"color:rgb(49,49,49);word-spacing:1px"><b=
r></div><div dir=3D"auto" style=3D"color:rgb(49,49,49);word-spacing:1px"><b=
r></div><div dir=3D"auto" style=3D"font-size:1rem;color:rgb(49,49,49);word-=
spacing:1px">In the PSP section can If we have to keep PSP can we add verbi=
age that states that PSP removal of the SRH header occurs on the Penultimat=
e egress P node.</div><div dir=3D"auto" style=3D"color:rgb(49,49,49);word-s=
pacing:1px"><br></div><div dir=3D"auto" style=3D"font-size:1rem;color:rgb(4=
9,49,49);word-spacing:1px">In the USP section can we also add that all rema=
ining SRH present in the packet are popped on the egress PE ultimate node.<=
/div><div dir=3D"auto" style=3D"color:rgb(49,49,49);word-spacing:1px"><br><=
/div><div dir=3D"auto" style=3D"font-size:1rem;color:rgb(49,49,49);word-spa=
cing:1px">In looking at these 3 SID functions the PSP and USP pop the EH an=
d the USP removes the 6in6 encapsulation so that the other end.x dt4 dt6 et=
c can pop the services L3vpn headers.</div><div dir=3D"auto" style=3D"color=
:rgb(49,49,49);word-spacing:1px"><br></div><div dir=3D"auto" style=3D"font-=
size:1rem;color:rgb(49,49,49);word-spacing:1px">Why can=E2=80=99t the USD 6=
in6 encapsulation removal be done on with the USP SID?</div><div dir=3D"aut=
o" style=3D"color:rgb(49,49,49);word-spacing:1px"><br></div><div dir=3D"aut=
o" style=3D"font-size:1rem;color:rgb(49,49,49);word-spacing:1px">Why does t=
he USP and USD SID have to be separate?</div><div dir=3D"auto" style=3D"col=
or:rgb(49,49,49);word-spacing:1px"><br></div><div dir=3D"auto" style=3D"col=
or:rgb(49,49,49);word-spacing:1px"><pre style=3D"white-space:pre-wrap;font-=
size:1rem;margin-top:0px;margin-bottom:0px;break-before:page"><span style=
=3D"font-size:1em;font-weight:bold"><h4 style=3D"display:inline;font-size:1=
rem"><a name=3D"m_-7527854924089525293_section-4.16.1" href=3D"https://tool=
s.ietf.org/html/draft-ietf-spring-srv6-network-programming-05#section-4.16.=
1" target=3D"_blank" style=3D"color:black;text-decoration:none;font-size:1r=
em">4.16.1</a>.  PSP: Penultimate Segment Pop of the SRH</h4></span>

   The SRH processing of the End, End.X and End.T behaviors are
   modified: after the instruction &quot;S14.  Update IPv6 DA with Segment
   List[Segments Left]&quot; is executed, the following instructions must b=
e
   executed as well:

   S14.1.   If (updated SL =3D=3D 0) {
   S14.2.      Pop the SRH
   S14.3.   }

<span style=3D"font-size:1em;font-weight:bold"><h4 style=3D"display:inline;=
font-size:1rem"><a name=3D"m_-7527854924089525293_section-4.16.2" href=3D"h=
ttps://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-05#se=
ction-4.16.2" target=3D"_blank" style=3D"color:black;text-decoration:none;f=
ont-size:1rem">4.16.2</a>.  USP: Ultimate Segment Pop of the SRH</h4></span=
>

   The SRH processing of the End, End.X and End.T behaviors are
   modified: the instructions S02-S04 are substituted by the following
   ones:

   S02.   If (Segments Left =3D=3D 0) {
   S03.       Pop the SRH
   S04.   }

<div class=3D"quoted-text" style=3D"color:rgb(117,117,117)"><span style=3D"=
font-size:1em;font-weight:bold"><h4 style=3D"display:inline;font-size:1rem"=
><a name=3D"m_-7527854924089525293_section-4.16.3" href=3D"https://tools.ie=
tf.org/html/draft-ietf-spring-srv6-network-programming-05#section-4.16.3" t=
arget=3D"_blank" style=3D"color:black;text-decoration:none;font-size:1rem">=
4.16.3</a>.  USD: Ultimate Segment Decapsulation</h4></span></div>

   The SRH processing of the End, End.X and End.T behaviors are
   modified: the instructions S02-S04 are substituted by the following
   ones:

   S02.   If (Segments Left =3D=3D 0) {
   S03.      Skip the SRH processing and proceed to the next header
   S04.   }


   Further on, the Upper-layer header processing of the End, End.X and
   End.T behaviors are modified as follows:</pre><pre style=3D"white-space:=
pre-wrap;font-size:1rem;margin-top:0px;margin-bottom:0px;break-before:page"=
><br></pre><pre style=3D"white-space:pre-wrap;font-size:1rem;margin-top:0px=
;margin-bottom:0px;break-before:page"><br></pre><pre style=3D"white-space:p=
re-wrap;font-size:1rem;margin-top:0px;margin-bottom:0px;break-before:page">=
Kind regards,</pre><pre style=3D"white-space:pre-wrap;font-size:1rem;margin=
-top:0px;margin-bottom:0px;break-before:page"><br></pre><pre style=3D"white=
-space:pre-wrap;font-size:1rem;margin-top:0px;margin-bottom:0px;break-befor=
e:page">Gyan</pre></div></div><div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Sat, Dec 14, 2019 at 9:08 PM Wang, Weibin =
(NSB - CN/Shanghai) &lt;<a href=3D"mailto:weibin.wang@nokia-sbell.com">weib=
in.wang@nokia-sbell.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex">





<div lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div>
<p class=3D"MsoNormal">Hi Pablo:<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal" style=3D"word-break:break-all">After the 2 context a=
ssumption in previous version of this draft, =C2=A0=E2=80=9C<span style=3D"=
font-size:10.5pt;font-family:&quot;Courier New&quot;;color:black;background=
:#fffdf5">we assume that there is no other extension header than
 the SRH.</span>=E2=80=9D =C2=A0and =C2=A0=E2=80=9C<span style=3D"font-size=
:10.5pt;font-family:&quot;Courier New&quot;;color:black;background:#fffdf5"=
>We assume<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"word-break:break-all"><span style=3D"font-s=
ize:10.5pt;font-family:&quot;Courier New&quot;;color:black;background:#fffd=
f5">=C2=A0=C2=A0 that the SRH may be present multiple times inside each pac=
ket</span>=E2=80=9D, are removed in this last draft, I feel a bit
 confusion on USD SID, as well as combination of USD &amp; USP.<u></u><u></=
u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">First, within the content of this last draft, the wo=
rd =E2=80=9CFurther on=E2=80=9D marked red in the following pseudocode in s=
ection =E2=80=9C4.16.3=E2=80=9D is hard to understand if the packet being p=
rocessed has other EH embed between SRH and Upper-layer header, such
 as AH or other EH, then the processing control of this packet will be pass=
ed to normal IPv6 module from current SRH processing module in SR-Node, so =
my question is : Can its control after completing AH processing (for exampl=
e) =C2=A0be back to SRH module (or call
 it pseudocode module) to proceed the next header like =E2=80=9Cupper-lay h=
eader type =3D=3D41 or 4=E2=80=9D.<u></u><u></u></p>
<p class=3D"MsoNormal">Or, if not, Did you created a new EH processing prot=
ocol stack instance in parallel to normal IPv6 module within the scope of S=
RH processing in SR-node.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Co=
urier New&quot;;color:black;background:#fffdf5">4.16.3.=C2=A0 USD: Ultimate=
 Segment Decapsulation</span><u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"word-break:break-all"><span style=3D"font-s=
ize:10.5pt;font-family:&quot;Courier New&quot;;color:black;background:#fffd=
f5"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal" style=3D"word-break:break-all"><span style=3D"font-s=
ize:10.5pt;font-family:&quot;Courier New&quot;;color:black;background:#fffd=
f5">S02.=C2=A0=C2=A0 If (Segments Left =3D=3D 0) {<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"word-break:break-all"><span style=3D"font-s=
ize:10.5pt;font-family:&quot;Courier New&quot;;color:black;background:#fffd=
f5">=C2=A0=C2=A0 S03.=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Skip the SRH processing=
 and proceed to the next header<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Co=
urier New&quot;;color:black;background:#fffdf5">=C2=A0=C2=A0 S04.=C2=A0=C2=
=A0 }</span><u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal" style=3D"word-break:break-all"><span style=3D"font-s=
ize:10.5pt;font-family:&quot;Courier New&quot;;color:red;background:#fffdf5=
">Further on,
</span><span style=3D"font-size:10.5pt;font-family:&quot;Courier New&quot;;=
color:black;background:#fffdf5">the Upper-layer header processing of the En=
d, End.X and<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"word-break:break-all"><span style=3D"font-s=
ize:10.5pt;font-family:&quot;Courier New&quot;;color:black;background:#fffd=
f5">=C2=A0=C2=A0 End.T behaviors are modified as follows:<u></u><u></u></sp=
an></p>
<p class=3D"MsoNormal" style=3D"word-break:break-all"><span style=3D"font-s=
ize:10.5pt;font-family:&quot;Courier New&quot;;color:black;background:#fffd=
f5"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal" style=3D"word-break:break-all"><span style=3D"font-s=
ize:10.5pt;font-family:&quot;Courier New&quot;;color:black;background:#fffd=
f5">=C2=A0=C2=A0 End:<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"word-break:break-all"><span style=3D"font-s=
ize:10.5pt;font-family:&quot;Courier New&quot;;color:black;background:#fffd=
f5">=C2=A0=C2=A0 S01. If (Upper-layer Header type =3D=3D 41 || 4) {<u></u><=
u></u></span></p>
<p class=3D"MsoNormal" style=3D"word-break:break-all"><span style=3D"font-s=
ize:10.5pt;font-family:&quot;Courier New&quot;;color:black;background:#fffd=
f5">=C2=A0=C2=A0 S02.=C2=A0=C2=A0=C2=A0 Remove the outer IPv6 Header with a=
ll its extension headers<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"word-break:break-all"><span style=3D"font-s=
ize:10.5pt;font-family:&quot;Courier New&quot;;color:black;background:#fffd=
f5">=C2=A0=C2=A0 S03.=C2=A0=C2=A0=C2=A0 Submit the packet to the egress IP =
FIB lookup and<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"word-break:break-all"><span style=3D"font-s=
ize:10.5pt;font-family:&quot;Courier New&quot;;color:black;background:#fffd=
f5">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 transmission to the new destination<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"word-break:break-all"><span style=3D"font-s=
ize:10.5pt;font-family:&quot;Courier New&quot;;color:black;background:#fffd=
f5">=C2=A0=C2=A0 S04. } Else {<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"word-break:break-all"><span style=3D"font-s=
ize:10.5pt;font-family:&quot;Courier New&quot;;color:black;background:#fffd=
f5">=C2=A0=C2=A0 S05.=C2=A0=C2=A0=C2=A0 Send an ICMP Parameter Problem mess=
age to the Source Address<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"word-break:break-all"><span style=3D"font-s=
ize:10.5pt;font-family:&quot;Courier New&quot;;color:black;background:#fffd=
f5">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 Code 4 (SR Upper-layer Header Error),<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"word-break:break-all"><span style=3D"font-s=
ize:10.5pt;font-family:&quot;Courier New&quot;;color:black;background:#fffd=
f5">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 Pointer set to the offset of the upper-layer header.<u></u><u></u=
></span></p>
<p class=3D"MsoNormal" style=3D"word-break:break-all"><span style=3D"font-s=
ize:10.5pt;font-family:&quot;Courier New&quot;;color:black;background:#fffd=
f5">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 Interrupt packet processing and discard the packet.<u></u><u></u>=
</span></p>
<p class=3D"MsoNormal" style=3D"word-break:break-all"><span style=3D"font-s=
ize:10.5pt;font-family:&quot;Courier New&quot;;color:black;background:#fffd=
f5"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Co=
urier New&quot;;color:black;background:#fffdf5">=C2=A0=C2=A0 S06. }</span><=
u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">From my understanding, the all processing action abo=
ut specific SID must be completed successively. That is to say, upon USD, t=
he upper-layer header (type 41 or 4) must be followed the SRH header being =
processed currently, or second SRH
 following the same rule (of course, the draft not considering 2 or more su=
ccessive SRHs).
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Second, the mixed SIDs function with combination of =
USD and USP (even PSP&amp;USD&amp;USP), I think, it is easy to understand w=
hen the two assumption above exist, but now I think it isn=E2=80=99t clear =
if you only provide the following sentence in this
 draft, i.e. =C2=A0=E2=80=9Cif =E2=80=A6 else=E2=80=A6=E2=80=9D statement:<=
u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"word-break:break-all">=E2=80=9C<span style=
=3D"font-size:10.5pt;font-family:&quot;Courier New&quot;;color:black;backgr=
ound:#fffdf5">An implementation that supports the USD flavor in conjunction=
 with<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"word-break:break-all"><span style=3D"font-s=
ize:10.5pt;font-family:&quot;Courier New&quot;;color:black;background:#fffd=
f5">=C2=A0=C2=A0 the USP flavor MAY optimize the packet processing by first=
 looking<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"word-break:break-all"><span style=3D"font-s=
ize:10.5pt;font-family:&quot;Courier New&quot;;color:black;background:#fffd=
f5">=C2=A0=C2=A0 whether the conditions for the USD flavor are met, in whic=
h case it<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Co=
urier New&quot;;color:black;background:#fffdf5">=C2=A0=C2=A0 can proceed wi=
th USD processing else do USP processing.</span>=E2=80=9D<u></u><u></u></p>
<p class=3D"MsoNormal">This confusion is also described in my another mail.=
 Of course, if the first question is addressed then this confusion does not=
 exist.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">By the way, is it really no different in text descri=
ption before and after the two context assumption above removed?<u></u><u><=
/u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal" style=3D"text-align:justify;text-justify:inter-ideog=
raph"><i><span style=3D"font-size:10.5pt;font-family:&quot;Times New Roman&=
quot;,serif">Cheers !<u></u><u></u></span></i></p>
<p class=3D"MsoNormal" style=3D"text-align:justify;text-justify:inter-ideog=
raph"><b><span style=3D"font-size:10.5pt;font-family:&quot;Times New Roman&=
quot;,serif"><u></u>=C2=A0<u></u></span></b></p>
<p class=3D"MsoNormal" style=3D"text-align:justify;text-justify:inter-ideog=
raph"><b><span style=3D"font-size:10.5pt;font-family:&quot;Times New Roman&=
quot;,serif">WANG Weibin<u></u><u></u></span></b></p>
</div>
</div>

_______________________________________________<br>
spring mailing list<br>
<a href=3D"mailto:spring@ietf.org" target=3D"_blank">spring@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/spring" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/spring</a><br>
</blockquote></div></div>-- <br><div dir=3D"ltr" class=3D"gmail_signature" =
data-smartmail=3D"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><=
div dir=3D"ltr"><div><p class=3D"MsoNormal"><span style=3D"font-family:Cali=
bri,sans-serif;color:rgb(80,0,80);background-image:initial;background-posit=
ion:initial;background-repeat:initial">Gyan S. Mishra</span><span style=3D"=
color:rgb(80,0,80);background-image:initial;background-position:initial;bac=
kground-repeat:initial"><span></span></span></p><p class=3D"MsoNormal"><spa=
n style=3D"font-family:Calibri,sans-serif;color:rgb(80,0,80);background-ima=
ge:initial;background-position:initial;background-repeat:initial">IT Networ=
k Engineering &amp;
Technology=C2=A0</span><span style=3D"color:rgb(80,0,80);background-image:i=
nitial;background-position:initial;background-repeat:initial"><span></span>=
</span></p><p class=3D"MsoNormal"><span style=3D"font-family:Calibri,sans-s=
erif;color:rgb(80,0,80);background-image:initial;background-position:initia=
l;background-repeat:initial">Verizon
Communications=C2=A0Inc. (VZ)</span><span style=3D"color:rgb(80,0,80);backg=
round-image:initial;background-position:initial;background-repeat:initial">=
<span></span></span></p><p class=3D"MsoNormal"><span style=3D"font-family:C=
alibri,sans-serif;color:rgb(80,0,80);background-image:initial;background-po=
sition:initial;background-repeat:initial">13101 Columbia Pike FDC1 3rd
Floor</span><span style=3D"color:rgb(80,0,80);background-image:initial;back=
ground-position:initial;background-repeat:initial"><span></span></span></p>=
<p class=3D"MsoNormal"><span style=3D"font-family:Calibri,sans-serif;color:=
rgb(80,0,80);background-image:initial;background-position:initial;backgroun=
d-repeat:initial">Silver Spring, MD 20904</span><span style=3D"color:rgb(80=
,0,80);background-image:initial;background-position:initial;background-repe=
at:initial"><span></span></span></p><p class=3D"MsoNormal"><span style=3D"f=
ont-family:Calibri,sans-serif;color:rgb(80,0,80);background-image:initial;b=
ackground-position:initial;background-repeat:initial">United States</span><=
span style=3D"color:rgb(80,0,80);background-image:initial;background-positi=
on:initial;background-repeat:initial"><span></span></span></p><p class=3D"M=
soNormal" style=3D"background-image:initial;background-position:initial;bac=
kground-repeat:initial"><span style=3D"font-family:Calibri,sans-serif;color=
:rgb(80,0,80)">Phone:=C2=A0301 502-1347</span><span></span></p><p class=3D"=
MsoNormal" style=3D"background-image:initial;background-position:initial;ba=
ckground-repeat:initial"><span style=3D"font-family:Calibri,sans-serif;colo=
r:rgb(80,0,80)">Email:=C2=A0<a href=3D"mailto:gyan.s.mishra@verizon.com" ta=
rget=3D"_blank"><span style=3D"color:rgb(17,85,204)">gyan.s.mishra@verizon.=
com</span></a></span><span></span></p><p class=3D"MsoNormal" style=3D"margi=
n:0in 0in 0.0001pt;background-image:initial;background-position:initial;bac=
kground-repeat:initial;font-size:12pt;font-family:&quot;Times New Roman&quo=
t;,serif">















</p><p class=3D"MsoNormal" style=3D"background-image:initial;background-pos=
ition:initial;background-repeat:initial"><span><span style=3D"font-family:&=
quot;Segoe UI&quot;,sans-serif;color:black;border:1pt none windowtext;paddi=
ng:0in;background-image:initial;background-position:initial;background-repe=
at:initial"><a href=3D"http://www.linkedin.com/in/networking-technologies-c=
onsultant" target=3D"_blank">www.linkedin.com/in/networking-technologies-co=
nsultant</a></span></span><span><span style=3D"font-family:&quot;Segoe UI&q=
uot;,sans-serif;border:1pt none windowtext;padding:0in;background-image:ini=
tial;background-position:initial;background-repeat:initial"><span></span></=
span></span></p></div><div><br></div></div></div></div></div></div>

--000000000000ce7d3f0599b8bcf8--

