Return-Path: <robert@raszuk.net>
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 7F88E1201E4
 for <spring@ietfa.amsl.com>; Mon, 16 Dec 2019 02:45:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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_NONE=-0.0001,
 SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key)
 header.d=raszuk.net
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 sUBsXhamNYXi for <spring@ietfa.amsl.com>;
 Mon, 16 Dec 2019 02:45:42 -0800 (PST)
Received: from mail-qk1-x72e.google.com (mail-qk1-x72e.google.com
 [IPv6:2607:f8b0:4864:20::72e])
 (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 236A6120220
 for <spring@ietf.org>; Mon, 16 Dec 2019 02:45:42 -0800 (PST)
Received: by mail-qk1-x72e.google.com with SMTP id c17so4001143qkg.7
 for <spring@ietf.org>; Mon, 16 Dec 2019 02:45:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; 
 h=mime-version:references:in-reply-to:from:date:message-id:subject:to
 :cc; bh=cBLdhCnUmGS8iWHlgwyHGHKnQN6r54VQvfnxjzp9D0Y=;
 b=I5psOgM7IfcMx5pa1KJLvWdAgvl+UXcU80I6Gp5VY1sw7g+hewzbngdj8w/iGdj2X+
 bKo206G2pY9TfT/kL15L6vPjTMAXjSPwmIKQDyW2tTDHbcNWlscAuTpaTUw5hubiES18
 HXy0SXvFIDVNWd1DZYR7PCeWNsjakOrRBXNqZ4Gj3hr9MXS2lizQKI+DT7iAjOUCHfMk
 9k5JQqiVgEcSVc4PVSuIZxP2irEDUbxRaIvcTOAjju8k/E2rUoFJqYr1RR/7IFHCfquK
 5rBtXZ5S98++8qnNY2I/90IIIf+FA4lk9PLyfLb4C5E6uJpat644dSzdAynKecxpTKWF
 yjlg==
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=cBLdhCnUmGS8iWHlgwyHGHKnQN6r54VQvfnxjzp9D0Y=;
 b=tkEg7G+T8p5NykLMVlFBUxLmkbk1p6rKFyVnAgCMXWMHyW1gkbddeA8ehXtnOLoI2b
 5vyKdqXbLElfH90ZqKV7z4wNZ4c3vvizpQhR5kp2uIaRow0KuVLqWnSLQE5UyunZ/pt2
 m+xvhqE3GYW09pTfkFTmBoaBgnJ6DUd9/UlxSAfz+4GqBCDIWbUqiYBcXtK0OS4QRnJm
 gT8aGm3qUNNnSSfwXMrm/ILbbTATkxmMLPZkvwNWsVQ5qj2WknXR1ES+CHNeO7ciLj5J
 r6p6Kr/YSSZA7f2PXXeZ2iNsq96dpTZ+T9++077Ubz48nEvzoA9XHJ3HEthV5HHKMAo1
 oF2Q==
X-Gm-Message-State: APjAAAVvflZ5ayNt+PBd60VN3+nrlkdlccfKlGKeSLAQ1Q48SoAWcSA9
 OtddGTAmsqSzxvLPiowrJo3d9LA0wx2RDdDeqbq/sA==
X-Google-Smtp-Source: APXvYqxdMv2ibGQGGlbDgPvmHsw4wIIoYd1QOmx3ztNLtgs7WciTMofugvzYpZVcOhzuHlcS83LhLp6ug65Gidu24ag=
X-Received: by 2002:a37:6087:: with SMTP id
 u129mr25820678qkb.219.1576493141037; 
 Mon, 16 Dec 2019 02:45:41 -0800 (PST)
MIME-Version: 1.0
References: <157645488473.11514.14849824578103099190@ietfa.amsl.com>
 <CAO42Z2xC4_QJ4h62bC1+pdkBY4LMEkKq0zXkAxxh=RMt8GEgPw@mail.gmail.com>
 <MWHPR11MB1600AD626D8C052175C518ABC1510@MWHPR11MB1600.namprd11.prod.outlook.com>
 <CAO42Z2whbJva6OYAJ2R7iq+4t87JWF5q63LJSnVRw22TqMPfSQ@mail.gmail.com>
 <MWHPR11MB16008E8034DE223FC784171EC1510@MWHPR11MB1600.namprd11.prod.outlook.com>
In-Reply-To: <MWHPR11MB16008E8034DE223FC784171EC1510@MWHPR11MB1600.namprd11.prod.outlook.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Mon, 16 Dec 2019 11:45:31 +0100
Message-ID: <CAOj+MMHpszR6URujmsFKTmS9DiMXtWpMUMAr=EeouLDOebXq5Q@mail.gmail.com>
To: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
Cc: Mark Smith <markzzzsmith@gmail.com>, SPRING WG <spring@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a9bda90599cfe94a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/eDPeIwxJX_FNkjApCQ_r2VaghY8>
Subject: Re: [spring] I-D Action:
 draft-ietf-spring-segment-routing-policy-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: Mon, 16 Dec 2019 10:45:46 -0000

--000000000000a9bda90599cfe94a
Content-Type: text/plain; charset="UTF-8"

Hi Ketan,

I think Mark is right here.

I went through this document again and it seems that it defines endpoint to
be used as either "address" or "prefix". See there is nothing wrong with
using prefix ... but "address" is normally referred to what is in the
packet.

Moreover your examples of default routes specify special prefixes of
0.0.0.0 not addresses.

Honestly if you re-define all endpoint use as prefix you will nicely cover
over all of your cases. Even more ... you will also nicely cover SR anycast
case. So my suggestion would be to encode endpoint as prefix+mask in all
cases here.

Thx,
R.





On Mon, Dec 16, 2019 at 11:07 AM Ketan Talaulikar (ketant) <ketant@cisco.com>
wrote:

> Hi Mark,
>
>
>
> Could you share references which says it is illegal to refer to 0.0.0.0 or
> :: as IP addresses?
>
>
>
> Many (if not most) implementations use these representations of IP
> addresses when provisioning a default static route and there is nothing
> wrong with doing so.
>
>
>
> The link you shared previously that indicated an issue because someone was
> using these zero addresses as destination IP in the packets. That would be
> an incorrect analogy since there is no such proposal in this document.
>
>
>
> Thanks,
>
> Ketan
>
>
>
> *From:* Mark Smith <markzzzsmith@gmail.com>
> *Sent:* 16 December 2019 12:27
> *To:* Ketan Talaulikar (ketant) <ketant@cisco.com>
> *Cc:* SPRING WG <spring@ietf.org>; i-d-announce@ietf.org
> *Subject:* Re: [spring] I-D Action:
> draft-ietf-spring-segment-routing-policy-06.txt
>
>
>
>
>
> On Mon, 16 Dec 2019, 16:43 Ketan Talaulikar (ketant), <ketant@cisco.com>
> wrote:
>
> Hi Mark,
>
> The draft talks about "destination of the policy" as in the tail-end node
> of the SR Policy. It does not talk about the destination IP address in the
> packet.
>
> You can consider this as a "default policy" on similar lines as a default
> route.
>
> Please see the section below which will cover one of the use-cases for
> steering over such SR policies to the null endpoint.
>
> https://tools.ietf.org/html/draft-ietf-spring-segment-routing-policy-06#section-8.8.1
>
> Hope that clarifies.
>
>
>
>
>
> I don't think it does.
>
>
>
> If this text is true - "The endpoint
>
>    is specified as an IPv4 or IPv6 address" - then those are illegal IPv4
> and IPv6 addresses.
>
>
>
> If these are not being used as IPv4 or IPv6 addresses, then they cannot be
> referred to as IPv4 or IPv6 addresses. It is confusing and inaccurate if
> they are.
>
>
>
>
> Thanks,
> Ketan
>
> -----Original Message-----
> From: spring <spring-bounces@ietf.org> On Behalf Of Mark Smith
> Sent: 16 December 2019 06:36
> To: SPRING WG <spring@ietf.org>
> Cc: i-d-announce@ietf.org
> Subject: Re: [spring] I-D Action:
> draft-ietf-spring-segment-routing-policy-06.txt
>
> "The endpoint indicates the destination of the policy.  The endpoint
>    is specified as an IPv4 or IPv6 address and is expected to be unique
>    in the domain.  In a specific case (refer to Section 8.8.1), the
>    endpoint can be the null address (0.0.0.0 for IPv4, ::0 for IPv6)."
>
> Per Internet Standard 3 / RFC 1122, 0.0.0.0 is an illegal IPv4 destination
> address.*
>
> Per RFC 4291, ::0 is an illegal IPv6 destination address.
>
>
> Regards,
> Mark.
>
>
> *People doing tricky things with 0.0.0.0 has cost me and a past employer 2
> weeks of needless troubleshooting, delaying a product/service launch.
>
> http://lists.ausnog.net/pipermail/ausnog/2017-July/039402.html
>
>
> On Mon, 16 Dec 2019 at 11:08, <internet-drafts@ietf.org> wrote:
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> > This draft is a work item of the Source Packet Routing in Networking WG
> of the IETF.
> >
> >         Title           : Segment Routing Policy Architecture
> >         Authors         : Clarence Filsfils
> >                           Siva Sivabalan
> >                           Daniel Voyer
> >                           Alex Bogdanov
> >                           Paul Mattes
> >         Filename        : draft-ietf-spring-segment-routing-policy-06.txt
> >         Pages           : 35
> >         Date            : 2019-12-15
> >
> > Abstract:
> >    Segment Routing (SR) allows a headend node to steer a packet flow
> >    along any path.  Intermediate per-flow states are eliminated thanks
> >    to source routing.  The headend node steers a flow into an SR Policy.
> >    The header of a packet steered in an SR Policy is augmented with an
> >    ordered list of segments associated with that SR Policy.  This
> >    document details the concepts of SR Policy and steering into an SR
> >    Policy.
> >
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-spring-segment-routing-pol
> > icy/
> >
> > There are also htmlized versions available at:
> > https://tools.ietf.org/html/draft-ietf-spring-segment-routing-policy-0
> > 6
> > https://datatracker.ietf.org/doc/html/draft-ietf-spring-segment-routin
> > g-policy-06
> >
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=draft-ietf-spring-segment-routing-po
> > licy-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/
> >
> > _______________________________________________
> > spring mailing list
> > spring@ietf.org
> > https://www.ietf.org/mailman/listinfo/spring
>
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>

--000000000000a9bda90599cfe94a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Ketan,<div><br></div><div>I think Mark is right here.=
=C2=A0</div><div><br></div><div>I went through this document again and it s=
eems that it defines endpoint to be used as either &quot;address&quot; or &=
quot;prefix&quot;. See there is nothing wrong with using prefix ... but &qu=
ot;address&quot; is normally referred to what is in the packet.=C2=A0</div>=
<div><br></div><div>Moreover your examples of default routes specify specia=
l prefixes of 0.0.0.0 not addresses.=C2=A0</div><div><br></div><div>Honestl=
y if you re-define all endpoint use as prefix you will nicely cover over al=
l of your cases. Even more ... you will also nicely cover SR anycast case. =
So my suggestion would be to encode endpoint as prefix+mask in all cases he=
re.=C2=A0</div><div><br></div><div>Thx,<br>R.</div><div><br></div><div><br>=
</div><div><br></div><div><br></div></div><br><div class=3D"gmail_quote"><d=
iv dir=3D"ltr" class=3D"gmail_attr">On Mon, Dec 16, 2019 at 11:07 AM Ketan =
Talaulikar (ketant) &lt;<a href=3D"mailto:ketant@cisco.com">ketant@cisco.co=
m</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"=
>





<div lang=3D"EN-IN">
<div class=3D"gmail-m_7798682907829229927WordSection1">
<p class=3D"MsoNormal"><span>Hi Mark,<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span>Could you share references which says it is il=
legal to refer to 0.0.0.0 or :: as IP addresses?<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span>Many (if not most) implementations use these r=
epresentations of IP addresses when provisioning a default static route and=
 there is nothing wrong with doing so.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span>The link you shared previously that indicated =
an issue because someone was using these zero addresses as destination IP i=
n the packets. That would be an incorrect analogy since there is no such pr=
oposal
 in this document.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span>Thanks,<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span>Ketan<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US">From:</span></b><span lang=
=3D"EN-US"> Mark Smith &lt;<a href=3D"mailto:markzzzsmith@gmail.com" target=
=3D"_blank">markzzzsmith@gmail.com</a>&gt;
<br>
<b>Sent:</b> 16 December 2019 12:27<br>
<b>To:</b> Ketan Talaulikar (ketant) &lt;<a href=3D"mailto:ketant@cisco.com=
" target=3D"_blank">ketant@cisco.com</a>&gt;<br>
<b>Cc:</b> SPRING WG &lt;<a href=3D"mailto:spring@ietf.org" target=3D"_blan=
k">spring@ietf.org</a>&gt;; <a href=3D"mailto:i-d-announce@ietf.org" target=
=3D"_blank">i-d-announce@ietf.org</a><br>
<b>Subject:</b> Re: [spring] I-D Action: draft-ietf-spring-segment-routing-=
policy-06.txt<u></u><u></u></span></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12pt"><u></u>=C2=A0<u></u></p=
>
<div>
<div>
<p class=3D"MsoNormal">On Mon, 16 Dec 2019, 16:43 Ketan Talaulikar (ketant)=
, &lt;<a href=3D"mailto:ketant@cisco.com" target=3D"_blank">ketant@cisco.co=
m</a>&gt; wrote:<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin-left:4=
.8pt;margin-right:0cm">
<p class=3D"MsoNormal">Hi Mark,<br>
<br>
The draft talks about &quot;destination of the policy&quot; as in the tail-=
end node of the SR Policy. It does not talk about the destination IP addres=
s in the packet.<br>
<br>
You can consider this as a &quot;default policy&quot; on similar lines as a=
 default route.<br>
<br>
Please see the section below which will cover one of the use-cases for stee=
ring over such SR policies to the null endpoint.<br>
<a href=3D"https://tools.ietf.org/html/draft-ietf-spring-segment-routing-po=
licy-06#section-8.8.1" target=3D"_blank">https://tools.ietf.org/html/draft-=
ietf-spring-segment-routing-policy-06#section-8.8.1</a><br>
<br>
Hope that clarifies.<u></u><u></u></p>
</blockquote>
</div>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I don&#39;t think it does.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">If this text is true - &quot;<span style=3D"font-fam=
ily:Arial,sans-serif">The endpoint</span><u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-family:Arial,sans-serif">=C2=A0 =
=C2=A0is specified as an IPv4 or IPv6 address&quot; - then those are illega=
l IPv4 and IPv6 addresses.</span><u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:Arial,sans-serif">If thes=
e are not being used as IPv4 or IPv6 addresses, then they cannot be referre=
d to as IPv4 or IPv6 addresses. It is confusing and inaccurate if they are.=
</span><u></u><u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin-left:4=
.8pt;margin-right:0cm">
<p class=3D"MsoNormal"><br>
Thanks,<br>
Ketan<br>
<br>
-----Original Message-----<br>
From: spring &lt;<a href=3D"mailto:spring-bounces@ietf.org" target=3D"_blan=
k">spring-bounces@ietf.org</a>&gt; On Behalf Of Mark Smith<br>
Sent: 16 December 2019 06:36<br>
To: SPRING WG &lt;<a href=3D"mailto:spring@ietf.org" target=3D"_blank">spri=
ng@ietf.org</a>&gt;<br>
Cc: <a href=3D"mailto:i-d-announce@ietf.org" target=3D"_blank">i-d-announce=
@ietf.org</a><br>
Subject: Re: [spring] I-D Action: draft-ietf-spring-segment-routing-policy-=
06.txt<br>
<br>
&quot;The endpoint indicates the destination of the policy.=C2=A0 The endpo=
int<br>
=C2=A0 =C2=A0is specified as an IPv4 or IPv6 address and is expected to be =
unique<br>
=C2=A0 =C2=A0in the domain.=C2=A0 In a specific case (refer to Section 8.8.=
1), the<br>
=C2=A0 =C2=A0endpoint can be the null address (0.0.0.0 for IPv4, ::0 for IP=
v6).&quot;<br>
<br>
Per Internet Standard 3 / RFC 1122, 0.0.0.0 is an illegal IPv4 destination =
address.*<br>
<br>
Per RFC 4291, ::0 is an illegal IPv6 destination address.<br>
<br>
<br>
Regards,<br>
Mark.<br>
<br>
<br>
*People doing tricky things with 0.0.0.0 has cost me and a past employer 2 =
weeks of needless troubleshooting, delaying a product/service launch.<br>
<br>
<a href=3D"http://lists.ausnog.net/pipermail/ausnog/2017-July/039402.html" =
target=3D"_blank">http://lists.ausnog.net/pipermail/ausnog/2017-July/039402=
.html</a><br>
<br>
<br>
On Mon, 16 Dec 2019 at 11:08, &lt;<a href=3D"mailto:internet-drafts@ietf.or=
g" target=3D"_blank">internet-drafts@ietf.org</a>&gt; wrote:<br>
&gt;<br>
&gt;<br>
&gt; A New Internet-Draft is available from the on-line Internet-Drafts dir=
ectories.<br>
&gt; This draft is a work item of the Source Packet Routing in Networking W=
G of the IETF.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0: Segment Routing Policy Architecture<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0: Clarence Filsfils<br>
&gt;=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 =C2=A0Siva Sivabalan<br>
&gt;=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 =C2=A0Daniel Voyer<br>
&gt;=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 =C2=A0Alex Bogdanov<br>
&gt;=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 =C2=A0Paul Mattes<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 draft-ietf-spring-segment-routing-policy-06.txt<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0: 35<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 : 2019-12-15<br>
&gt;<br>
&gt; Abstract:<br>
&gt;=C2=A0 =C2=A0 Segment Routing (SR) allows a headend node to steer a pac=
ket flow<br>
&gt;=C2=A0 =C2=A0 along any path.=C2=A0 Intermediate per-flow states are el=
iminated thanks<br>
&gt;=C2=A0 =C2=A0 to source routing.=C2=A0 The headend node steers a flow i=
nto an SR Policy.<br>
&gt;=C2=A0 =C2=A0 The header of a packet steered in an SR Policy is augment=
ed with an<br>
&gt;=C2=A0 =C2=A0 ordered list of segments associated with that SR Policy.=
=C2=A0 This<br>
&gt;=C2=A0 =C2=A0 document details the concepts of SR Policy and steering i=
nto an SR<br>
&gt;=C2=A0 =C2=A0 Policy.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; The IETF datatracker status page for this draft is:<br>
&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-spring-segment-=
routing-pol" target=3D"_blank">
https://datatracker.ietf.org/doc/draft-ietf-spring-segment-routing-pol</a><=
br>
&gt; icy/<br>
&gt;<br>
&gt; There are also htmlized versions available at:<br>
&gt; <a href=3D"https://tools.ietf.org/html/draft-ietf-spring-segment-routi=
ng-policy-0" target=3D"_blank">
https://tools.ietf.org/html/draft-ietf-spring-segment-routing-policy-0</a><=
br>
&gt; 6<br>
&gt; <a href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-spring-seg=
ment-routin" target=3D"_blank">
https://datatracker.ietf.org/doc/html/draft-ietf-spring-segment-routin</a><=
br>
&gt; g-policy-06<br>
&gt;<br>
&gt; A diff from the previous version is available at:<br>
&gt; <a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-spring-segme=
nt-routing-po" target=3D"_blank">
https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-spring-segment-routing-po</a=
><br>
&gt; licy-06<br>
&gt;<br>
&gt;<br>
&gt; Please note that it may take a couple of minutes from the time of <br>
&gt; submission until the htmlized version and diff are available at <a hre=
f=3D"http://tools.ietf.org" target=3D"_blank">
tools.ietf.org</a>.<br>
&gt;<br>
&gt; Internet-Drafts are also available by anonymous FTP at:<br>
&gt; <a href=3D"ftp://ftp.ietf.org/internet-drafts/" target=3D"_blank">ftp:=
//ftp.ietf.org/internet-drafts/</a><br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; spring mailing list<br>
&gt; <a href=3D"mailto:spring@ietf.org" target=3D"_blank">spring@ietf.org</=
a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/spring" target=3D"_bl=
ank">https://www.ietf.org/mailman/listinfo/spring</a><br>
<br>
_______________________________________________<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" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/spring</a><u></u><u></u></p>
</blockquote>
</div>
</div>
</div>
</div>
</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>

--000000000000a9bda90599cfe94a--

