Return-Path: <gregimirsky@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 E73A112008A
 for <spring@ietfa.amsl.com>; Sun, 26 Jan 2020 21:35:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.987
X-Spam-Level: 
X-Spam-Status: No, score=-1.987 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,
 T_KAM_HTML_FONT_INVALID=0.01, 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 j7R_kCQaRE1X for <spring@ietfa.amsl.com>;
 Sun, 26 Jan 2020 21:35:45 -0800 (PST)
Received: from mail-lj1-x236.google.com (mail-lj1-x236.google.com
 [IPv6:2a00:1450:4864:20::236])
 (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 58A96120103
 for <spring@ietf.org>; Sun, 26 Jan 2020 21:35:44 -0800 (PST)
Received: by mail-lj1-x236.google.com with SMTP id y6so9324201lji.0
 for <spring@ietf.org>; Sun, 26 Jan 2020 21:35: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=4iERLfLM72EXUWBDVyf/qnIOyFm7SCuJ6Wvt7s1+8hY=;
 b=MnBUssd0oYKX0dEPKKyxkwcEH/3lzL4e9waxKbfTD/1nURowNZiRz/h6r+QIFp19jt
 OhDWl3dHeDxiB1NtHEeSpstL6KE9EKK/IFPdCViQKHnpLq0Tx3O7ipOwTDqTNCoGbobB
 x4VMFf8Ze2zV+Nw1BYIwsE5v341sr9zeRgeuoVxCtfdam5YelB5lZTyo0muvYXohakwW
 IzFssqhRgkQKIBQpeHB/XD2lSZAvl8DEmaCHKbGxSnvrz2YaZzaoaZdVmgn/FTwHq2OY
 fd1IoY6wLiw6C5Bfsj3el9BjIgBllluPtt6JXlx/21NCp8okwwWN65dBDU9pkVy/RnTS
 f4ng==
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=4iERLfLM72EXUWBDVyf/qnIOyFm7SCuJ6Wvt7s1+8hY=;
 b=qlJK7s+GMTOPmZT4wk9M+Bt2UP9ksb1YF8MY63oKKCiKhf8Dpm4w8ZNppQbDCpGIKU
 kqNYwxw1SpGN3Ow4zB23Ypvpcl/YpxA77DtsApRhhix3rI/l2r72D/Vt3EFjJBzGLatR
 5JTdy9skPGx0agzbQss7/jQB1XJ3P0Jw8yZynkqmqBDAUA25OZn8z5WyiX30uAtxKqxo
 uhY/gp0G2NzBOAgwCM+S9QTNdfZuMbgNP5Wn5RjSmyUDAnEWWf/rVd+iRwYebEEQWzsn
 f1QIhYu3+lRDOttyQxd3CC2rSsfPZJ5vm40YObxaekAwde9mIbygP0jly8tb7NcnzRuS
 UKtQ==
X-Gm-Message-State: APjAAAU2pPq67hrUCtpq3K2+4AAm1RCffVlOcBzhWkBVzpfZDuvxX4MN
 0SIv/uhXpf9ILj3Pn1YXQhn8N+fe4kc5uqsLLJW6n8Du
X-Google-Smtp-Source: APXvYqzX+PpSXfTcrQFf5H1+RMDAueOV+0tVG7RUXWteq3/4DP/rYDbmJk9gdZ/hcNfBzKeqUEjF/tJzqX/JuwaT9cw=
X-Received: by 2002:a2e:88c4:: with SMTP id a4mr9461943ljk.174.1580103342394; 
 Sun, 26 Jan 2020 21:35:42 -0800 (PST)
MIME-Version: 1.0
References: <17421_1575566127_5DE93B2F_17421_93_1_53C29892C857584299CBF5D05346208A48D1A3DA@OPEXCAUBM43.corporate.adroot.infra.ftgroup>
 <CA+RyBmWQOgVmekANMLXVQeeBy9MK72Y653u0vpiW_GboqyDNUQ@mail.gmail.com>
 <238769EE-8272-420D-A2A4-BFECCE6E09AC@cisco.com>
 <CA+RyBmVkPK6Zv05vmmfHahXPJRRJ2SbWFuKTDTjBvvNFJWxqpw@mail.gmail.com>
 <70A6F938-29B0-473E-8559-7E20C7E992BD@cisco.com>
 <CA+RyBmVbYObSvcf9frfr8LBhKU5cmJ99o8mNJr_=CvH_z7j6Gw@mail.gmail.com>
 <5BF8B291-479F-400C-A551-8EF76F8F8090@cisco.com>
In-Reply-To: <5BF8B291-479F-400C-A551-8EF76F8F8090@cisco.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Sun, 26 Jan 2020 21:35:30 -0800
Message-ID: <CA+RyBmU_PgWpFo+KmS4=jAmAGKwSqavBYys_WbaKrEkbvsu9mg@mail.gmail.com>
To: "Pablo Camarillo (pcamaril)" <pcamaril@cisco.com>
Cc: "spring@ietf.org" <spring@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006e9240059d187aa8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/QH2TcECpC0Yd2tFraTflIncqiz8>
Subject: Re: [spring] WGLC - draft-ietf-spring-srv6-network-programming
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, 27 Jan 2020 05:35:49 -0000

--0000000000006e9240059d187aa8
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Pablo,
thank you for your thoughtful consideration of my comments. Please find my
new notes in-line below tagged GIM>>.

Regards,
Greg

On Tue, Jan 21, 2020 at 11:08 PM Pablo Camarillo (pcamaril) <
pcamaril@cisco.com> wrote:

> Hi Greg,
>
>
>
> Inline.
>
>
>
> Thanks,
>
> Pablo.
>
>
>
> *From: *Greg Mirsky <gregimirsky@gmail.com>
> *Date: *Sunday, 19 January 2020 at 20:28
> *To: *"Pablo Camarillo (pcamaril)" <pcamaril@cisco.com>
> *Cc: *"spring@ietf.org" <spring@ietf.org>
> *Subject: *Re: WGLC - draft-ietf-spring-srv6-network-programming
>
>
>
> Hi Pablo,
>
> thank you for sharing your opinion. I understand that you believe that
> draft-ietf-6man-spring-srv6-oam will not change and will be published wit=
h
> defining the O-flag as
>
>       O-flag: OAM flag.  When set, it indicates that this packet is an
>       operations and management (OAM) packet.
>
> I, on the other hand, am much less certain that that draft and SRv6 OAM,
> in general, require the special flag in SRH. I believe that progressing
> the draft-ietf-spring-srv6-network-programming with the current text and
> the informative reference increases the likelihood that an Errata must be
> filed one the SRv6 OAM draft is published.
>
>
>
> PC:
>
> I believe that we can trim the text in section 6.3 to avoid mentioning th=
e
> O-bit without reducing the overall quality of the document.
>
> <old>
>
>    [I-D.ietf-6man-spring-srv6-oam] defines OAM behaviors for SRv6.  This
>
>    includes the definition of the SRH Flag 'O-bit', as well as
>
>    additional SR Endpoint behaviors for OAM purposes.
>
> </old>
>
> <new>
>
>    [I-D.ietf-6man-spring-srv6-oam] defines OAM behaviors for SRv6.  This
>
>    includes the definition of additional SR Endpoint behaviors for OAM
> purposes.
>
> </new>
>
> Do you agree with this change?
>
GIM>> I agree that the new text is more clear and less dependent on the
discussion of I-D.ietf-6man-spring-srv6-oam. Though the "OAM behaviors for
SRv6" that are introduced in the draft, i.e., "punt the packet" and "punt
the packet with a timestamp", are being discussed and may change as the
result of the discussion by 6man WG. Hence I think that it be better to not
to reference   I-D.ietf-6man-spring-srv6-oam altogether.

>
>
> And as we're discussing a sub-section in the Operation section, I've got
> few questions on counters, hope you don't mind:
>
> =C2=B7         As this is part of the operational considerations, should =
there
> be any recommendation on the length of the counters?
>
> PC: Counter length is implementation dependent. The capabilities of
> different platforms have significant hairpin as to make any recommendatio=
n
> irrelevant.
>
> =C2=B7         Also, the usual drawback of detailed statistics to charact=
erize
> a flow is scaling. Any consideration and recommendation on that?
>
> PC: There is no per-flow statistics. It is a counter per SRv6 SID. An SRv=
6
> SID is shared among different flows. No per-flow scaling is required.
>
> =C2=B7         And last. I didn't find any of these counters being discus=
sed
> in draft-ietf-6man-spring-srv6-oam. Perhaps you can help me with a
> reference to the SRv6 document that uses them.
>
> PC: The counters are required by the controller. Its usage is out of the
> scope of this document.
>
GIM>> I think that if SRv6 OAM was part of the network programming draft,
then defining these counters, that are, in my understanding, an integral
part of SRv6 OAM, logical, in the right place. But since SRv6 OAM is
discussed in the draft of its own, I suggest considering moving Section 6.1
Counters to I-D.ietf-6man-spring-srv6-oam.

Regards,
>
> Greg
>
>
>
>
>
> On Mon, Jan 13, 2020 at 10:23 AM Pablo Camarillo (pcamaril) <
> pcamaril@cisco.com> wrote:
>
> Hi Greg,
>
>
>
> Inline.
>
>
>
> Thank you,
>
> Pablo.
>
>
>
> *From: *Greg Mirsky <gregimirsky@gmail.com>
> *Date: *Sunday, 12 January 2020 at 04:01
> *To: *=E2=80=9CPablo Camarillo (pcamaril)=E2=80=9D <pcamaril@cisco.com>
> *Cc: *=E2=80=9Cspring@ietf.org=E2=80=9D <spring@ietf.org>
> *Subject: *Re: WGLC =E2=80=93 draft-ietf-spring-srv6-network-programming
>
>
>
> Hi Pablo,
>
> thank you for your expedient response. Please find my new notes under
> GIM>> tag below in-line.
>
>
>
> Regards,
>
> Greg
>
>
>
> On Fri, Jan 10, 2020 at 1:09 PM Pablo Camarillo (pcamaril) <
> pcamaril@cisco.com> wrote:
>
> Hi Greg,
>
>
>
> Inline.
>
>
>
> Thanks,
>
> Pablo.
>
>
>
> *From: *Greg Mirsky <gregimirsky@gmail.com>
> *Date: *Tuesday, 7 January 2020 at 21:01
> *To: *Bruno Decraene <bruno.decraene@orange.com>
> *Cc: *SPRING WG List <spring@ietf.org>, =E2=80=9C6man@ietf.org=E2=80=9D <=
6man@ietf.org>,
> draft-ietf-spring-srv6-network-programming <
> draft-ietf-spring-srv6-network-programming@ietf.org>
> *Subject: *Re: WGLC =E2=80=93 draft-ietf-spring-srv6-network-programming
> *Resent from: *<alias-bounces@ietf.org>
> *Resent to: *<cf@cisco.com>, <pcamaril@cisco.com>, <john@leddy.net>, <
> daniel.voyer@bell.ca>, <satoru.matsushima@g.softbank.co.jp>, <
> lizhenbin@huawei.com>
> *Resent date: *Tuesday, 7 January 2020 at 21:01
>
>
>
> Dear Authors, WG Chairs, et al.,
>
> I hope I=E2=80=99m not too late with my comments and questions on the doc=
ument.
> Please kindly consider them as WG LC comments:
>
> =C2=B7         I have a question regarding the following pseudo-code:
>
>   S08.   Max_LE =3D (Hdr Ext Len / 2) =E2=80=93 1
>
>   S09.   If ((Last Entry > max_LE) or (Segments Left > (Last Entry+1)) {
>
>   S10.      Send an ICMP Parameter Problem to the Source Address,
>
>                Code 0 (Erroneous header field encountered),
>
>                Pointer set to the Segments Left field.
>
>                Interrupt packet processing and discard the packet.
>
>   S11.   }
>
>
>
> According to RFC 8200, Hdr Ext Len is the length of the extension header
> in 8-octet units, not including the first 8 octets. Thus, as I understand=
,
> max_LE is the length in 8-octet units of half of the extension header les=
s
> one. On the other hand, Last Entry and Segments Left are indices. Hence m=
y
> question, What is being compared in line S09 ( Last Entry > max_LE)? Leng=
th
> and index? If the goal is to use Hdr Ext Len to calculate the number of
> entries in the header, then what assumption is used in S08? Is it that th=
e
> entry=E2=80=99s length is always and only 128 bits, i.e. 16 octets? I bel=
ieve that
> using such an assumption is too narrowing and limiting to SRH.
>
>
>
> PC: This has already been discussed with Adrian. Please check this thread=
:
> https://mailarchive.ietf.org/arch/msg/spring/IOA_4nlNPacD2v7Jue2dkGeOABk
>
> GIM>> Thank you for the reference. In some aspects, part of my statement
> is repeating your answer to Adrain. The only length on an element in SRH
> considered is 128 bits, the length of IPv6 address. I think that your
> explanation of how you have arrived at th following formula
>
>     S08.   Max_LE =3D (Hdr Ext Len / 2) =E2=80=93 1
>
>  will benefit the document.
>
> My question to you and SPRING WG goes beyond this scenario. Considering
> presented in Singapore Unified Identifier proposals (
> draft-mirsky-6man-unified-id-sr
> <https://datatracker.ietf.org/doc/draft-mirsky-6man-unified-id-sr/> and
> draft-wmsaxw-6man-usid-id-use
> <https://datatracker.ietf.org/doc/draft-gmsm-bess-evpn-bfd/?include_text=
=3D1>),
> I believe other scenarios of using SRH, with elements of length other tha=
n
> 128 bits should be accommodated, e.g., 32 bits-long elements.
>
> i.
>
>
>
> PC: It is up to the draft-mirsky authors to standardize in their draft th=
e
> changes to the SRH processing. As per today the draft-mirsky proposal is
> still an individual document.
>
>
>
> =C2=B7         Another question is to Section 6.3. What value do you see =
in
> this section? I've noticed that draft-ietf-6man-spring-srv6-oam is in the
> Informational References section. I agree with that for the first sentenc=
e
> in the section. But I believe that the second sentence that refers to the
> new O-bit and OAM behaviors defined in  draft-ietf-6man-spring-srv6-oam
> requires it to be moved into the Normative References section. Unless
> you'll decide to remove the section altogether.
>
> PC: The O-bit and OAM behaviors described in
> draft-ietf-6man-spring-srv6-oam are not required to understand or impleme=
nt
> the technology described in draft-ietf-spring-srv6-network-programming.
> However, they are relevant as to provide additional information to the
> reader. Why would it be a normative reference?
>
> GIM>> Ali and I are discussing several aspects of
> draft-ietf-6man-spring-srv6-oam. For example, the O-bit is applicable to
> any OAM operation or to some part of them. Note that OAM apparatus usuall=
y
> considered to include Fault Management and Performance Monitoring
> protocols. Both may operate as proactive or on-demand. Is the O-bit
> applicable to all OAM methods? Then, Fault Management OAM supports
> Continuity Check, Connectivity Verification and, for some networks,
> Automatic Protection Coordination. How O-bit is used in these methods? No=
w,
> to the Performance Monitoring OAM. I think that the O-bit can be only use=
d
> in dual-ended one-way PM OAM. How O-bit may be used in single-ended two-w=
ay
> PM OAM? Can the O-bit support the Loss Measurement? As you may see, there
> are many questions to discuss and clarify in the document. I can imagine
> that the result of our work on draft-ietf-6man-spring-srv6-oam may be
> somewhat different from its current form. How to ensure synchronization
> between SRv6 programming and OAM specifications?
>
>
>
> PC: The current reference in draft-ietf-spring-srv6-network-programming
> does not explain particular mechanisms of draft-ietf-6man-spring-srv6-oam=
.
> It only says that draft-ietf-6man-spring-srv6-oam defines OAM mechanisms
> for SRv6 as well as the O-bit. This is flexible enough as to be correct
> regardless of the changes that you make during the WGLC to
> draft-ietf-6man-spring-srv6-oam.
>
>
>
> Regards,
>
> Greg
>
>
>
> On Thu, Dec 5, 2019 at 9:15 AM <bruno.decraene@orange.com> wrote:
>
> Hello SPRING,
>
>
>
> This email starts a two weeks Working Group Last Call on draft-ietf-sprin=
g-srv6-network-programming [1].
>
>
>
> Please read this document if you haven't read the most recent version, an=
d send your comments to the SPRING WG list, no later than December 20.
>
>
>
> You may copy the 6MAN WG for IPv6 related comment, but consider not dupli=
cating emails on the 6MAN mailing list for the comments which are only spri=
ng specifics.
>
>
>
> If you are raising a point which you expect will be specifically debated =
on the mailing list, consider using a specific email/thread for this point.
>
> This may help avoiding that the thread become specific to this point and =
that other points get forgotten (or that the thread get converted into para=
llel independent discussions)
>
>
>
> Thank you,
>
> Bruno
>
>
>
> [1] https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programmin=
g-05
>
>
>
>
>
> _________________________________________________________________________=
________________________________________________
>
>
>
> Ce message et ses pieces jointes peuvent contenir des informations confid=
entielles ou privilegiees et ne doivent donc
>
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez re=
cu ce message par erreur, veuillez le signaler
>
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages =
electroniques etant susceptibles d'alteration,
>
> Orange decline toute responsabilite si ce message a ete altere, deforme o=
u falsifie. Merci.
>
>
>
> This message and its attachments may contain confidential or privileged i=
nformation that may be protected by law;
>
> they should not be distributed, used or copied without authorisation.
>
> If you have received this email in error, please notify the sender and de=
lete this message and its attachments.
>
> As emails may be altered, Orange is not liable for messages that have bee=
n modified, changed or falsified.
>
> Thank you.
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>

--0000000000006e9240059d187aa8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Hi Pablo,<div>thank you for your thoughtf=
ul consideration of my comments. Please find my new notes in-line below tag=
ged GIM&gt;&gt;.</div><div><br></div><div>Regards,</div><div>Greg</div></di=
v><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On T=
ue, Jan 21, 2020 at 11:08 PM Pablo Camarillo (pcamaril) &lt;<a href=3D"mail=
to:pcamaril@cisco.com">pcamaril@cisco.com</a>&gt; wrote:<br></div><blockquo=
te 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-ES">
<div class=3D"gmail-m_4709508110174724463WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hi Greg,<u></u><u></u></span></=
p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Inline.<u></u><u></u></span></p=
>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Thanks,<u></u><u></u></span></p=
>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Pablo.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span><u></u>=C2=A0<u></u></span></p>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(181,196,223);padding:3pt 0cm 0cm">
<p class=3D"MsoNormal" style=3D"margin-left:36pt"><b><span style=3D"font-si=
ze:12pt;color:black">From:
</span></b><span style=3D"font-size:12pt;color:black">Greg Mirsky &lt;<a hr=
ef=3D"mailto:gregimirsky@gmail.com" target=3D"_blank">gregimirsky@gmail.com=
</a>&gt;<br>
<b>Date: </b>Sunday, 19 January 2020 at 20:28<br>
<b>To: </b>&quot;Pablo Camarillo (pcamaril)&quot; &lt;<a href=3D"mailto:pca=
maril@cisco.com" target=3D"_blank">pcamaril@cisco.com</a>&gt;<br>
<b>Cc: </b>&quot;<a href=3D"mailto:spring@ietf.org" target=3D"_blank">sprin=
g@ietf.org</a>&quot; &lt;<a href=3D"mailto:spring@ietf.org" target=3D"_blan=
k">spring@ietf.org</a>&gt;<br>
<b>Subject: </b>Re: WGLC - draft-ietf-spring-srv6-network-programming<u></u=
><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt"><u></u>=C2=A0<u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">Hi Pablo,<u></u><u></u></=
p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">thank you for sharing you=
r opinion. I understand that you believe=C2=A0that draft-ietf-6man-spring-s=
rv6-oam will not change and will be published with defining the O-flag as=
=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">=C2=A0 =C2=A0 =C2=A0 O-fl=
ag: OAM flag.=C2=A0 When set, it indicates that this packet is an<br>
=C2=A0 =C2=A0 =C2=A0 operations and management (OAM) packet.<u></u><u></u><=
/p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">I, on the other hand, am =
much less certain that that draft and SRv6 OAM, in general, require the spe=
cial flag in SRH. I believe that progressing the=C2=A0draft-ietf-spring-srv=
6-network-programming with the current
 text and the informative reference increases the=C2=A0likelihood=C2=A0that=
 an Errata must be filed one the SRv6 OAM draft is published.<u></u><u></u>=
</p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">PC: <u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">I believe that we can trim the =
text in section 6.3 to avoid mentioning the O-bit without reducing the over=
all quality of the document.
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&lt;old&gt;<u></u><u></u></span=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;Cour=
ier New&quot;;color:black">=C2=A0=C2=A0 [<a name=3D"m_4709508110174724463_r=
ef-I-D.ietf-6man-spring-srv6-oam">I-D.ietf-6man-spring-srv6-oam</a>] define=
s OAM behaviors for SRv6.=C2=A0 This<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;Cour=
ier New&quot;;color:black">=C2=A0=C2=A0 includes the definition of the SRH =
Flag &#39;O-bit&#39;, as well as<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;Cour=
ier New&quot;;color:black">=C2=A0=C2=A0 additional SR Endpoint behaviors fo=
r OAM purposes.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&lt;/old&gt;<u></u><u></u></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&lt;new&gt;<u></u><u></u></span=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;Cour=
ier New&quot;;color:black">=C2=A0=C2=A0 [I-D.ietf-6man-spring-srv6-oam] def=
ines OAM behaviors for SRv6.=C2=A0 This<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;Cour=
ier New&quot;;color:black">=C2=A0=C2=A0 includes the definition of
</span><span lang=3D"EN-US" style=3D"font-size:10pt;font-family:&quot;Couri=
er New&quot;;color:black">a</span><span style=3D"font-size:10pt;font-family=
:&quot;Courier New&quot;;color:black">dditional SR Endpoint behaviors for O=
AM purposes.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&lt;/new&gt;<u></u><u></u></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Do you agree with this change?<=
/span></p></div></div></div></div></blockquote><div>GIM&gt;&gt; I agree tha=
t the new text is more clear and less dependent on the discussion of=C2=A0I=
-D.ietf-6man-spring-srv6-oam. Though the &quot;OAM behaviors for SRv6&quot;=
 that are introduced in the draft, i.e., &quot;punt the packet&quot; and &q=
uot;punt the packet with a timestamp&quot;, are being discussed and may cha=
nge as the result of the discussion by 6man WG. Hence I think that it be be=
tter to not to reference=C2=A0

=C2=A0I-D.ietf-6man-spring-srv6-oam altogether.</div><blockquote class=3D"g=
mail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204=
,204,204);padding-left:1ex"><div lang=3D"en-ES"><div class=3D"gmail-m_47095=
08110174724463WordSection1"><div><div><p class=3D"MsoNormal"><span lang=3D"=
EN-US"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">And as we&#39;re discussi=
ng a sub-section in the Operation section, I&#39;ve got few questions on co=
unters, hope you don&#39;t mind:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:72pt">
<u></u><span style=3D"font-size:10pt;font-family:Symbol"><span>=C2=B7<span =
style=3D"font:7pt &quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0
</span></span></span><u></u><span dir=3D"LTR"></span>As this is part of the=
 operational considerations, should there be any recommendation on the leng=
th of the counters?<u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">PC: Counter length is implement=
ation dependent. The capabilities of different platforms have significant h=
airpin as to make any recommendation irrelevant.<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:72pt">
<u></u><span style=3D"font-size:10pt;font-family:Symbol"><span>=C2=B7<span =
style=3D"font:7pt &quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0
</span></span></span><u></u><span dir=3D"LTR"></span>Also, the usual drawba=
ck of detailed statistics to characterize a flow is scaling. Any considerat=
ion and recommendation on that?<u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">PC: There is no per-flow statis=
tics. It is a counter per SRv6 SID. An SRv6 SID is shared among different f=
lows. No per-flow scaling is required.
<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:72pt">
<u></u><span style=3D"font-size:10pt;font-family:Symbol"><span>=C2=B7<span =
style=3D"font:7pt &quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0
</span></span></span><u></u><span dir=3D"LTR"></span>And last. I didn&#39;t=
 find any of these counters being discussed in=C2=A0draft-ietf-6man-spring-=
srv6-oam. Perhaps you can help me with a reference to the SRv6 document tha=
t uses them.<u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">PC: The counters are required b=
y the controller. Its usage is out of the scope of this document.</span></p=
></div></div></div></div></blockquote><div>GIM&gt;&gt; I think that if SRv6=
 OAM was part of the network programming draft, then defining these counter=
s, that are, in my understanding, an integral part of SRv6 OAM, logical, in=
 the right place. But since SRv6 OAM is discussed in the draft of its own, =
I suggest considering moving Section 6.1 Counters to I-D.ietf-6man-spring-s=
rv6-oam.</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex"><div lang=3D"en-ES"><div class=3D"gmail-m_4709508110174724463WordSectio=
n1"><div><div><p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u><u></u></s=
pan></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">Regards,<u></u><u></u></p=
>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">Greg<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt"><u></u>=C2=A0<u></u></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">On Mon, Jan 13, 2020 at 1=
0:23 AM Pablo Camarillo (pcamaril) &lt;<a href=3D"mailto:pcamaril@cisco.com=
" target=3D"_blank">pcamaril@cisco.com</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:5pt 0c=
m 5pt 4.8pt">
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">
<span lang=3D"EN-GB">Hi Greg,</span><span lang=3D"EN-US"><u></u><u></u></sp=
an></p>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">
<span lang=3D"EN-GB">=C2=A0</span><span lang=3D"EN-US"><u></u><u></u></span=
></p>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">
<span lang=3D"EN-GB">Inline.</span><span lang=3D"EN-US"><u></u><u></u></spa=
n></p>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">
<span lang=3D"EN-GB">=C2=A0</span><span lang=3D"EN-US"><u></u><u></u></span=
></p>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">
<span lang=3D"EN-GB">Thank you,</span><span lang=3D"EN-US"><u></u><u></u></=
span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">
<span lang=3D"EN-GB">Pablo.</span><span lang=3D"EN-US"><u></u><u></u></span=
></p>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">
<span lang=3D"EN-GB">=C2=A0</span><span lang=3D"EN-US"><u></u><u></u></span=
></p>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(181,196,223);padding:3pt 0cm 0cm">
<p class=3D"MsoNormal" style=3D"margin-left:72pt">
<b><span lang=3D"EN-US" style=3D"font-size:12pt;color:black">From: </span><=
/b><span lang=3D"EN-US" style=3D"font-size:12pt;color:black">Greg Mirsky &l=
t;</span><a href=3D"mailto:gregimirsky@gmail.com" target=3D"_blank"><span l=
ang=3D"EN-US" style=3D"font-size:12pt">gregimirsky@gmail.com</span></a><spa=
n lang=3D"EN-US" style=3D"font-size:12pt;color:black">&gt;<br>
<b>Date: </b>Sunday, 12 January 2020 at 04:01<br>
<b>To: </b></span><span lang=3D"EN-US" style=3D"font-size:12pt">=E2=80=9C<s=
pan style=3D"color:black">Pablo Camarillo (pcamaril)</span>=E2=80=9D<span s=
tyle=3D"color:black"> &lt;</span></span><a href=3D"mailto:pcamaril@cisco.co=
m" target=3D"_blank"><span lang=3D"EN-US" style=3D"font-size:12pt">pcamaril=
@cisco.com</span></a><span lang=3D"EN-US" style=3D"font-size:12pt;color:bla=
ck">&gt;<br>
<b>Cc: </b></span><span lang=3D"EN-US" style=3D"font-size:12pt">=E2=80=9C</=
span><a href=3D"mailto:spring@ietf.org" target=3D"_blank"><span lang=3D"EN-=
US" style=3D"font-size:12pt">spring@ietf.org</span></a><span lang=3D"EN-US"=
 style=3D"font-size:12pt">=E2=80=9D<span style=3D"color:black">
 &lt;</span></span><a href=3D"mailto:spring@ietf.org" target=3D"_blank"><sp=
an lang=3D"EN-US" style=3D"font-size:12pt">spring@ietf.org</span></a><span =
lang=3D"EN-US" style=3D"font-size:12pt;color:black">&gt;<br>
<b>Subject: </b>Re: WGLC </span><span lang=3D"EN-US" style=3D"font-size:12p=
t">=E2=80=93<span style=3D"color:black"> draft-ietf-spring-srv6-network-pro=
gramming</span></span><span lang=3D"EN-US"><u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:72pt">
<span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:72pt">
<span lang=3D"EN-US">Hi Pablo, <u></u><u></u></span></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:72pt">
<span lang=3D"EN-US">thank you for your expedient response. Please find my =
new notes under GIM&gt;&gt; tag below in-line.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:72pt">
<span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:72pt">
<span lang=3D"EN-US">Regards,<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:72pt">
<span lang=3D"EN-US">Greg<u></u><u></u></span></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:72pt">
<span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:72pt">
<span lang=3D"EN-US">On Fri, Jan 10, 2020 at 1:09 PM Pablo Camarillo (pcama=
ril) &lt;</span><a href=3D"mailto:pcamaril@cisco.com" target=3D"_blank"><sp=
an lang=3D"EN-US">pcamaril@cisco.com</span></a><span lang=3D"EN-US">&gt; wr=
ote:<u></u><u></u></span></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:5pt 0c=
m 5pt 4.8pt">
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:72pt">
<span lang=3D"EN-GB">Hi Greg,</span><span lang=3D"EN-US"><u></u><u></u></sp=
an></p>
<p class=3D"MsoNormal" style=3D"margin-left:72pt">
<span lang=3D"EN-GB">=C2=A0</span><span lang=3D"EN-US"><u></u><u></u></span=
></p>
<p class=3D"MsoNormal" style=3D"margin-left:72pt">
<span lang=3D"EN-GB">Inline.</span><span lang=3D"EN-US"><u></u><u></u></spa=
n></p>
<p class=3D"MsoNormal" style=3D"margin-left:72pt">
<span lang=3D"EN-GB">=C2=A0</span><span lang=3D"EN-US"><u></u><u></u></span=
></p>
<p class=3D"MsoNormal" style=3D"margin-left:72pt">
<span lang=3D"EN-GB">Thanks,</span><span lang=3D"EN-US"><u></u><u></u></spa=
n></p>
<p class=3D"MsoNormal" style=3D"margin-left:72pt">
<span lang=3D"EN-GB">Pablo.</span><span lang=3D"EN-US"><u></u><u></u></span=
></p>
<p class=3D"MsoNormal" style=3D"margin-left:72pt">
<span lang=3D"EN-GB">=C2=A0</span><span lang=3D"EN-US"><u></u><u></u></span=
></p>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(181,196,223);padding:3pt 0cm 0cm">
<p class=3D"MsoNormal" style=3D"margin-left:108pt">
<b><span lang=3D"EN-US" style=3D"font-size:12pt;color:black">From: </span><=
/b><span lang=3D"EN-US" style=3D"font-size:12pt;color:black">Greg Mirsky &l=
t;</span><a href=3D"mailto:gregimirsky@gmail.com" target=3D"_blank"><span l=
ang=3D"EN-US" style=3D"font-size:12pt">gregimirsky@gmail.com</span></a><spa=
n lang=3D"EN-US" style=3D"font-size:12pt;color:black">&gt;<br>
<b>Date: </b>Tuesday, 7 January 2020 at 21:01<br>
<b>To: </b>Bruno Decraene &lt;</span><a href=3D"mailto:bruno.decraene@orang=
e.com" target=3D"_blank"><span lang=3D"EN-US" style=3D"font-size:12pt">brun=
o.decraene@orange.com</span></a><span lang=3D"EN-US" style=3D"font-size:12p=
t;color:black">&gt;<br>
<b>Cc: </b>SPRING WG List &lt;</span><a href=3D"mailto:spring@ietf.org" tar=
get=3D"_blank"><span lang=3D"EN-US" style=3D"font-size:12pt">spring@ietf.or=
g</span></a><span lang=3D"EN-US" style=3D"font-size:12pt;color:black">&gt;,
</span><span lang=3D"EN-US" style=3D"font-size:12pt">=E2=80=9C</span><a hre=
f=3D"mailto:6man@ietf.org" target=3D"_blank"><span lang=3D"EN-US" style=3D"=
font-size:12pt">6man@ietf.org</span></a><span lang=3D"EN-US" style=3D"font-=
size:12pt">=E2=80=9D<span style=3D"color:black"> &lt;</span></span><a href=
=3D"mailto:6man@ietf.org" target=3D"_blank"><span lang=3D"EN-US" style=3D"f=
ont-size:12pt">6man@ietf.org</span></a><span lang=3D"EN-US" style=3D"font-s=
ize:12pt;color:black">&gt;,
 draft-ietf-spring-srv6-network-programming &lt;</span><a href=3D"mailto:dr=
aft-ietf-spring-srv6-network-programming@ietf.org" target=3D"_blank"><span =
lang=3D"EN-US" style=3D"font-size:12pt">draft-ietf-spring-srv6-network-prog=
ramming@ietf.org</span></a><span lang=3D"EN-US" style=3D"font-size:12pt;col=
or:black">&gt;<br>
<b>Subject: </b>Re: WGLC </span><span lang=3D"EN-US" style=3D"font-size:12p=
t">=E2=80=93<span style=3D"color:black"> draft-ietf-spring-srv6-network-pro=
gramming<br>
<b>Resent from: </b>&lt;</span></span><a href=3D"mailto:alias-bounces@ietf.=
org" target=3D"_blank"><span lang=3D"EN-US" style=3D"font-size:12pt">alias-=
bounces@ietf.org</span></a><span lang=3D"EN-US" style=3D"font-size:12pt;col=
or:black">&gt;<br>
<b>Resent to: </b>&lt;</span><a href=3D"mailto:cf@cisco.com" target=3D"_bla=
nk"><span lang=3D"EN-US" style=3D"font-size:12pt">cf@cisco.com</span></a><s=
pan lang=3D"EN-US" style=3D"font-size:12pt;color:black">&gt;, &lt;</span><a=
 href=3D"mailto:pcamaril@cisco.com" target=3D"_blank"><span lang=3D"EN-US" =
style=3D"font-size:12pt">pcamaril@cisco.com</span></a><span lang=3D"EN-US" =
style=3D"font-size:12pt;color:black">&gt;,
 &lt;</span><a href=3D"mailto:john@leddy.net" target=3D"_blank"><span lang=
=3D"EN-US" style=3D"font-size:12pt">john@leddy.net</span></a><span lang=3D"=
EN-US" style=3D"font-size:12pt;color:black">&gt;, &lt;</span><a href=3D"mai=
lto:daniel.voyer@bell.ca" target=3D"_blank"><span lang=3D"EN-US" style=3D"f=
ont-size:12pt">daniel.voyer@bell.ca</span></a><span lang=3D"EN-US" style=3D=
"font-size:12pt;color:black">&gt;,
 &lt;</span><a href=3D"mailto:satoru.matsushima@g.softbank.co.jp" target=3D=
"_blank"><span lang=3D"EN-US" style=3D"font-size:12pt">satoru.matsushima@g.=
softbank.co.jp</span></a><span lang=3D"EN-US" style=3D"font-size:12pt;color=
:black">&gt;, &lt;</span><a href=3D"mailto:lizhenbin@huawei.com" target=3D"=
_blank"><span lang=3D"EN-US" style=3D"font-size:12pt">lizhenbin@huawei.com<=
/span></a><span lang=3D"EN-US" style=3D"font-size:12pt;color:black">&gt;<br=
>
<b>Resent date: </b>Tuesday, 7 January 2020 at 21:01</span><span lang=3D"EN=
-US"><u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:108pt">
<span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:108pt">
<span lang=3D"EN-US">Dear Authors, WG Chairs, et al., <u></u><u></u></span>=
</p>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:108pt">
<span lang=3D"EN-US">I hope I=E2=80=99m not too late with my comments and q=
uestions on the document. Please kindly consider them as WG LC comments:<u>=
</u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:144pt">
<span lang=3D"EN-US" style=3D"font-size:10pt;font-family:Symbol">=C2=B7</sp=
an><span lang=3D"EN-US" style=3D"font-size:7pt;font-family:&quot;Times New =
Roman&quot;,serif">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span><span lang=3D"EN-US">I have a question regarding the following pseud=
o-code:<u></u><u></u></span></p>
</div>
<blockquote style=3D"margin:5pt 0cm 5pt 30pt">
<div>
<p class=3D"MsoNormal" style=3D"margin-left:108pt">
<span lang=3D"EN-US">=C2=A0 S08. =C2=A0 Max_LE =3D (Hdr Ext Len / 2) =E2=80=
=93 1<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:108pt">
<span lang=3D"EN-US">=C2=A0 S09. =C2=A0 If ((Last Entry &gt; max_LE) or (Se=
gments Left &gt; (Last Entry+1)) {<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:108pt">
<span lang=3D"EN-US">=C2=A0 S10. =C2=A0 =C2=A0 =C2=A0Send an ICMP Parameter=
 Problem to the Source Address,<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:108pt">
<span lang=3D"EN-US">=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0Code 0 (Erroneous header field encountered),<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:108pt">
<span lang=3D"EN-US">=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0Pointer set to the Segments Left field.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:108pt">
<span lang=3D"EN-US">=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0Interrupt packet processing and discard the packet.<u></u><u></u></span>=
</p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:108pt">
<span lang=3D"EN-US">=C2=A0 S11. =C2=A0 }<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:108pt">
<span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:108pt">
<span lang=3D"EN-US">According to RFC 8200, Hdr Ext Len is the length of th=
e extension header in 8-octet units, not including the first 8 octets. Thus=
, as I understand, max_LE is the length in 8-octet units of half of the ext=
ension header less one. On the other
 hand, Last Entry and Segments Left are indices. Hence my question, What is=
 being compared in line S09 ( Last Entry &gt; max_LE)? Length and index? If=
 the goal is to use Hdr Ext Len to calculate the number of entries in the h=
eader, then what assumption is used
 in S08? Is it that the entry=E2=80=99s length is always and only 128 bits,=
 i.e. 16 octets? I believe that using such an assumption is too narrowing a=
nd limiting to SRH.<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:72pt">
<span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:72pt">
<span lang=3D"EN-US">PC: This has already been discussed with Adrian. Pleas=
e check this thread:
</span><a href=3D"https://mailarchive.ietf.org/arch/msg/spring/IOA_4nlNPacD=
2v7Jue2dkGeOABk" target=3D"_blank"><span lang=3D"EN-US" style=3D"color:wind=
owtext;text-decoration:none">https://mailarchive.ietf.org/arch/msg/spring/I=
OA_4nlNPacD2v7Jue2dkGeOABk</span></a><span lang=3D"EN-US"><u></u><u></u></s=
pan></p>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:72pt">
<span lang=3D"EN-US">GIM&gt;&gt; Thank you for the reference. In some aspec=
ts, part of my statement is repeating your answer to Adrain. The only lengt=
h on an element in SRH considered is 128 bits, the length of IPv6 address. =
I think that your explanation of how you
 have arrived at th following formula<u></u><u></u></span></p>
</div>
</div>
<blockquote style=3D"margin:5pt 0cm 5pt 30pt">
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:72pt">
<span lang=3D"EN-US">=C2=A0 =C2=A0 S08. =C2=A0 Max_LE =3D (Hdr Ext Len / 2)=
 =E2=80=93 1=C2=A0 =C2=A0=C2=A0<u></u><u></u></span></p>
</div>
</div>
</blockquote>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:72pt">
<span lang=3D"EN-US">=C2=A0will benefit the document.=C2=A0<u></u><u></u></=
span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:72pt">
<span lang=3D"EN-US">My question to you and SPRING WG goes beyond this scen=
ario. Considering presented in Singapore Unified Identifier proposals (</sp=
an><a href=3D"https://datatracker.ietf.org/doc/draft-mirsky-6man-unified-id=
-sr/" target=3D"_blank"><span lang=3D"EN-US">draft-mirsky-6man-unified-id-s=
r</span></a><span lang=3D"EN-US">=C2=A0and=C2=A0</span><a href=3D"https://d=
atatracker.ietf.org/doc/draft-gmsm-bess-evpn-bfd/?include_text=3D1" target=
=3D"_blank"><span lang=3D"EN-US">draft-wmsaxw-6man-usid-id-use</span></a><s=
pan lang=3D"EN-US">),
 I believe other scenarios of using SRH, with elements of length other than=
 128 bits should be accommodated, e.g., 32 bits-long elements.<u></u><u></u=
></span></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:72pt">
<span lang=3D"EN-US">i.<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:72pt">
<span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">
<span lang=3D"EN-US">PC: It is up to the draft-mirsky authors to standardiz=
e in their draft the changes to the SRH processing. As per today the draft-=
mirsky proposal is still an individual document.<u></u><u></u></span></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:5pt 0c=
m 5pt 4.8pt">
<div>
<div>
<div>
<blockquote style=3D"margin:5pt 0cm 5pt 30pt">
<div>
<p class=3D"MsoNormal" style=3D"margin-left:72pt">
<span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
</div>
</blockquote>
<p class=3D"MsoNormal" style=3D"margin-left:144pt">
<span lang=3D"EN-US" style=3D"font-size:10pt;font-family:Symbol">=C2=B7</sp=
an><span lang=3D"EN-US" style=3D"font-size:7pt;font-family:&quot;Times New =
Roman&quot;,serif">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span><span lang=3D"EN-US">Another question is to Section 6.3. What value =
do you see in this section? I&#39;ve noticed that draft-ietf-6man-spring-sr=
v6-oam is in the Informational References section. I agree with that for th=
e first sentence in the section. But I
 believe that the second sentence that refers to the new O-bit and OAM beha=
viors defined in=C2=A0 draft-ietf-6man-spring-srv6-oam requires it to be mo=
ved into the Normative References section. Unless you&#39;ll decide to remo=
ve the section altogether.<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:72pt">
<span lang=3D"EN-US">PC: The O-bit and OAM behaviors described in draft-iet=
f-6man-spring-srv6-oam are not required to understand or implement the tech=
nology described in draft-ietf-spring-srv6-network-programming. However, th=
ey are relevant as to provide additional
 information to the reader. Why would it be a normative reference?<u></u><u=
></u></span></p>
</div>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:72pt">
<span lang=3D"EN-US">GIM&gt;&gt; Ali and I are discussing several aspects o=
f draft-ietf-6man-spring-srv6-oam. For example, the O-bit is applicable to =
any OAM operation or to some part of them. Note that OAM apparatus usually =
considered to include Fault Management and
 Performance Monitoring protocols. Both may operate as proactive or on-dema=
nd. Is the O-bit applicable to all OAM methods? Then, Fault Management OAM =
supports Continuity Check, Connectivity Verification and, for some networks=
, Automatic Protection Coordination.
 How O-bit is used in these methods? Now, to the Performance Monitoring OAM=
. I think that the O-bit can be only used in dual-ended one-way PM OAM. How=
 O-bit may be used in single-ended two-way PM OAM? Can the O-bit support th=
e Loss Measurement? As you may see,
 there are many questions to discuss and clarify in the document. I can ima=
gine that the result of our work on draft-ietf-6man-spring-srv6-oam may be =
somewhat different from its current form. How to ensure synchronization bet=
ween SRv6 programming and OAM specifications?<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">
<span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">
<span lang=3D"EN-US">PC: The current reference in draft-ietf-spring-srv6-ne=
twork-programming does not explain particular mechanisms of draft-ietf-6man=
-spring-srv6-oam. It only says that draft-ietf-6man-spring-srv6-oam defines=
 OAM mechanisms for SRv6 as well as
 the O-bit. This is flexible enough as to be correct regardless of the chan=
ges that you make during the WGLC to draft-ietf-6man-spring-srv6-oam.<u></u=
><u></u></span></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:5pt 0c=
m 5pt 4.8pt">
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:108pt">
<span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:108pt">
<span lang=3D"EN-US">Regards,<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:108pt">
<span lang=3D"EN-US">Greg<u></u><u></u></span></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:108pt">
<span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:108pt">
<span lang=3D"EN-US">On Thu, Dec 5, 2019 at 9:15 AM &lt;</span><a href=3D"m=
ailto:bruno.decraene@orange.com" target=3D"_blank"><span lang=3D"EN-US">bru=
no.decraene@orange.com</span></a><span lang=3D"EN-US">&gt; wrote:<u></u><u>=
</u></span></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:5pt 0c=
m 5pt 4.8pt">
<div>
<div>
<pre style=3D"margin-left:108pt"><span lang=3D"EN-US">Hello SPRING,<u></u><=
u></u></span></pre>
<pre style=3D"margin-left:108pt"><span lang=3D"EN-US">=C2=A0<u></u><u></u><=
/span></pre>
<pre style=3D"margin-left:108pt"><span lang=3D"EN-US">This email starts a t=
wo weeks Working Group Last Call on draft-ietf-spring-srv6-network-programm=
ing [1].<u></u><u></u></span></pre>
<pre style=3D"margin-left:108pt"><span lang=3D"EN-US">=C2=A0<u></u><u></u><=
/span></pre>
<pre style=3D"margin-left:108pt"><span lang=3D"EN-US">Please read this docu=
ment if you haven&#39;t read the most recent version, and send your comment=
s to the SPRING WG list, no later than December 20.<u></u><u></u></span></p=
re>
<pre style=3D"margin-left:108pt"><span lang=3D"EN-US">=C2=A0<u></u><u></u><=
/span></pre>
<pre style=3D"margin-left:108pt"><span lang=3D"EN-US">You may copy the 6MAN=
 WG for IPv6 related comment, but consider not duplicating emails on the 6M=
AN mailing list for the comments which are only spring specifics.<u></u><u>=
</u></span></pre>
<pre style=3D"margin-left:108pt"><span lang=3D"EN-US">=C2=A0<u></u><u></u><=
/span></pre>
<pre style=3D"margin-left:108pt"><span lang=3D"EN-US">If you are raising a =
point which you expect will be specifically debated on the mailing list, co=
nsider using a specific email/thread for this point.<u></u><u></u></span></=
pre>
<pre style=3D"margin-left:108pt"><span lang=3D"EN-US">This may help avoidin=
g that the thread become specific to this point and that other points get f=
orgotten (or that the thread get converted into parallel independent discus=
sions)<u></u><u></u></span></pre>
<pre style=3D"margin-left:108pt"><span lang=3D"EN-US">=C2=A0<u></u><u></u><=
/span></pre>
<pre style=3D"margin-left:108pt"><span lang=3D"EN-US">Thank you,<u></u><u><=
/u></span></pre>
<pre style=3D"margin-left:108pt"><span lang=3D"EN-US">Bruno<u></u><u></u></=
span></pre>
<pre style=3D"margin-left:108pt"><span lang=3D"EN-US">=C2=A0<u></u><u></u><=
/span></pre>
<pre style=3D"margin-left:108pt"><span lang=3D"EN-US">[1] </span><a href=3D=
"https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-05"=
 target=3D"_blank"><span lang=3D"EN-US">https://tools.ietf.org/html/draft-i=
etf-spring-srv6-network-programming-05</span></a><span lang=3D"EN-US"><u></=
u><u></u></span></pre>
<pre style=3D"margin-left:108pt"><span lang=3D"EN-US">=C2=A0<u></u><u></u><=
/span></pre>
<p class=3D"MsoNormal" style=3D"margin-left:108pt">
<span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
</div>
<pre style=3D"margin-left:108pt"><span lang=3D"FR">________________________=
___________________________________________________________________________=
______________________</span><span lang=3D"EN-US"><u></u><u></u></span></pr=
e>
<pre style=3D"margin-left:108pt"><span lang=3D"FR">=C2=A0</span><span lang=
=3D"EN-US"><u></u><u></u></span></pre>
<pre style=3D"margin-left:108pt"><span lang=3D"FR">Ce message et ses pieces=
 jointes peuvent contenir des informations confidentielles ou privilegiees =
et ne doivent donc</span><span lang=3D"EN-US"><u></u><u></u></span></pre>
<pre style=3D"margin-left:108pt"><span lang=3D"FR">pas etre diffuses, explo=
ites ou copies sans autorisation. Si vous avez recu ce message par erreur, =
veuillez le signaler</span><span lang=3D"ES"><u></u><u></u></span></pre>
<pre style=3D"margin-left:108pt"><span lang=3D"FR">a l&#39;expediteur et le=
 detruire ainsi que les pieces jointes. Les messages electroniques etant su=
sceptibles d&#39;alteration,<u></u><u></u></span></pre>
<pre style=3D"margin-left:108pt"><span lang=3D"FR">Orange decline toute res=
ponsabilite si ce message a ete altere, deforme ou falsifie. Merci.<u></u><=
u></u></span></pre>
<pre style=3D"margin-left:108pt"><span lang=3D"FR">=C2=A0<u></u><u></u></sp=
an></pre>
<pre style=3D"margin-left:108pt"><span lang=3D"FR">This message and its att=
achments may contain confidential or privileged information that may be pro=
tected by law;</span><span lang=3D"EN-US"><u></u><u></u></span></pre>
<pre style=3D"margin-left:108pt"><span lang=3D"FR">they should not be distr=
ibuted, used or copied without authorisation.</span><span lang=3D"EN-US"><u=
></u><u></u></span></pre>
<pre style=3D"margin-left:108pt"><span lang=3D"FR">If you have received thi=
s email in error, please notify the sender and delete this message and its =
attachments.</span><span lang=3D"EN-US"><u></u><u></u></span></pre>
<pre style=3D"margin-left:108pt"><span lang=3D"FR">As emails may be altered=
, Orange is not liable for messages that have been modified, changed or fal=
sified.</span><span lang=3D"EN-US"><u></u><u></u></span></pre>
<pre style=3D"margin-left:108pt"><span lang=3D"FR">Thank you.</span><span l=
ang=3D"EN-US"><u></u><u></u></span></pre>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:108pt">
<span lang=3D"EN-US">------------------------------------------------------=
--------------<br>
IETF IPv6 working group mailing list<br>
</span><a href=3D"mailto:ipv6@ietf.org" target=3D"_blank"><span lang=3D"EN-=
US">ipv6@ietf.org</span></a><span lang=3D"EN-US"><br>
Administrative Requests: </span><a href=3D"https://www.ietf.org/mailman/lis=
tinfo/ipv6" target=3D"_blank"><span lang=3D"EN-US">https://www.ietf.org/mai=
lman/listinfo/ipv6</span></a><span lang=3D"EN-US"><br>
--------------------------------------------------------------------<u></u>=
<u></u></span></p>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>

</blockquote></div></div>

--0000000000006e9240059d187aa8--

