
From nobody Sun Sep  1 06:09:59 2019
Return-Path: <chengweiqiang@chinamobile.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD13A120024; Sun,  1 Sep 2019 06:09:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eDYAt2dkkCng; Sun,  1 Sep 2019 06:09:54 -0700 (PDT)
Received: from cmccmta1.chinamobile.com (cmccmta1.chinamobile.com [221.176.66.79]) by ietfa.amsl.com (Postfix) with ESMTP id CB99C12000F; Sun,  1 Sep 2019 06:09:49 -0700 (PDT)
Received: from spf.mail.chinamobile.com (unknown[172.16.121.7]) by rmmx-syy-dmz-app04-12004 (RichMail) with SMTP id 2ee45d6bc30c709-20c23; Sun, 01 Sep 2019 21:09:35 +0800 (CST)
X-RM-TRANSID: 2ee45d6bc30c709-20c23
X-RM-TagInfo: emlType=0                                       
X-RM-SPAM-FLAG: 00000000
Received: from cmcc (unknown[111.32.143.119]) by rmsmtp-syy-appsvr04-12004 (RichMail) with SMTP id 2ee45d6bc30e9b4-4c485; Sun, 01 Sep 2019 21:09:35 +0800 (CST)
X-RM-TRANSID: 2ee45d6bc30e9b4-4c485
From: "Weiqiang Cheng" <chengweiqiang@chinamobile.com>
To: "'Dhruv Dhody'" <dhruv.ietf@gmail.com>, <pce@ietf.org>
Cc: "'pce-chairs'" <pce-chairs@ietf.org>
References: <CAB75xn44Q8Y_eeGDfV+ecojJt0gKd9zHU4B7V0Xn_PYneCQAeg@mail.gmail.com>
In-Reply-To: <CAB75xn44Q8Y_eeGDfV+ecojJt0gKd9zHU4B7V0Xn_PYneCQAeg@mail.gmail.com>
Date: Sun, 1 Sep 2019 21:09:34 +0800
Message-ID: <001c01d560c6$80bd7a30$82386e90$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AdVXfwyHtDl5QTKWSKy5ndCvD+ZQ/QJRx1hw
Content-Language: zh-cn
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/f00Cj0F-v6_1l7EHdHGibHyzkaw>
Subject: [Pce] =?gb2312?b?tPC4tDogIFdHIGFkb3B0aW9uIHBvbGwgZm9yIGRyYWZ0?= =?gb2312?b?LXNpdmFiYWxhbi1wY2UtYmluZGluZy1sYWJlbC1zaWQtMDc=?=
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Sep 2019 13:09:58 -0000

I support the adoption of this draft.

B.R.
Weiqiang Cheng

-----=D3=CA=BC=FE=D4=AD=BC=FE-----
=B7=A2=BC=FE=C8=CB: Pce [mailto:pce-bounces@ietf.org] =B4=FA=B1=ED Dhruv =
Dhody
=B7=A2=CB=CD=CA=B1=BC=E4: 2019=C4=EA8=D4=C221=C8=D5 01:45
=CA=D5=BC=FE=C8=CB: pce@ietf.org
=B3=AD=CB=CD: pce-chairs
=D6=F7=CC=E2: [Pce] WG adoption poll for =
draft-sivabalan-pce-binding-label-sid-07

Hi WG,

This email begins the WG adoption poll for
draft-sivabalan-pce-binding-label-sid-07 [1].

Should this draft be adopted by the PCE WG? Please state your reasons - =
Why
/
Why not? What needs to be fixed before or after adoption? Are you =
willing to
work on this draft? Review comments should be posted to the list.

One of the chairs did a pre-adoption review [2] and authors posted a new
revision. Note that there are known implementations.

This adoption poll will end on 6th September 2019.

Thanks!
Dhruv (for the chairs)


[1] https://tools.ietf.org/html/draft-sivabalan-pce-binding-label-sid-07
[2] =
https://mailarchive.ietf.org/arch/msg/pce/oaBIRA9FnNsV6-JrKKRCdwtLysk

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




From nobody Sun Sep  1 10:48:40 2019
Return-Path: <mahend.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 682901200B4; Sun,  1 Sep 2019 10:48:38 -0700 (PDT)
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 HWrEb2YQmO6y; Sun,  1 Sep 2019 10:48:36 -0700 (PDT)
Received: from mail-ot1-x32d.google.com (mail-ot1-x32d.google.com [IPv6:2607:f8b0:4864:20::32d]) (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 5005E12007C; Sun,  1 Sep 2019 10:48:36 -0700 (PDT)
Received: by mail-ot1-x32d.google.com with SMTP id r20so11610811ota.5; Sun, 01 Sep 2019 10:48:36 -0700 (PDT)
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=fm0R0KHLnfH3IqPS18WcKWYjDDbQbt69I4jiL+B6nh0=; b=RPpncDCsxdVFO77okE7gdlprSfxuzNUCS5hKyT2Aa2Hca+ij1WJ+l/pWjE01aa6NvC 7voQ6DkWfsKuGttX4pOHmKmP9JhqEdlbdIaEaxjSt83UGlaxRkbjc8IRizcqQpsKoj4/ eOMpVMP2bsnCX4kRQ4w+y34S80SMIaf0RvD5ofcadX8IDINOBrt1L34Hm3Mb4daZG61f IFMxzonHKnLYNAkZlf62QJlZg3wKPbocAHhXzPsGGG2Gle9VDYNcwwg/EepO9RPXgrhv 4qgfKcUjNu5A9DXt6Xn20/oWEr9kDrkALZYIpJfSVjOhdpgZZJJGOeMKQz9JfoNX7P+q YCOg==
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=fm0R0KHLnfH3IqPS18WcKWYjDDbQbt69I4jiL+B6nh0=; b=QZStOhAYs3QtcXQdHdvH7ru0g7YdtJ7+ztPcftkPkhBAQfokTICr9wH6Z4JSO9dkAO p4D7EgFzJIP+/XNtHH5aRs0OmsxeHHF0nw2+NAyGsFHKz4RkDk3n/ajgyOyBFyGE+BxR 3b82KEC6Hq5wDdkSniHQ9gEACBFYUI+oOPs7FiD4h31Omrt7kTjwJB3P9xmc9MOqnUWi NFtZGvy1MM95SXF9geDAvPgivLX9qpwdy7e1YufFLmtJjg9ubr1C7/uwGlXuVg2Soy7X XkCSHKbkEAkGG/o6VYPb39D3zPm1a9xJ95BkdZWOmpqUc4zdloW9O3UvVZNSANyz6vBa OfGA==
X-Gm-Message-State: APjAAAVIF7J/CjJpLyV0prX3MlJ5bFzN/pctwcxTWTSIR1M9hP8B1gUE 6WuYhCuTiczJj52bUYf5sFPJFBUk0T67RPDMjRg=
X-Google-Smtp-Source: APXvYqzlc2jKJYTOvVKEN2ez3cf4Ou3lTdfgD8zzYmN5CU3+NNdPVly6j10Fk6CqGKDs0TMYfgRyjjgAfT8UGeZdwCU=
X-Received: by 2002:a9d:1289:: with SMTP id g9mr19669854otg.287.1567360115721;  Sun, 01 Sep 2019 10:48:35 -0700 (PDT)
MIME-Version: 1.0
References: <CAB75xn44Q8Y_eeGDfV+ecojJt0gKd9zHU4B7V0Xn_PYneCQAeg@mail.gmail.com>
In-Reply-To: <CAB75xn44Q8Y_eeGDfV+ecojJt0gKd9zHU4B7V0Xn_PYneCQAeg@mail.gmail.com>
From: Mahend Negi <mahend.ietf@gmail.com>
Date: Sun, 1 Sep 2019 23:18:24 +0530
Message-ID: <CAM5Nu_wA6JFYWxFddgLgQ6Su9_+8aP0ZA40Ehy4Pn3Sxmw6cbA@mail.gmail.com>
To: Dhruv Dhody <dhruv.ietf@gmail.com>
Cc: pce@ietf.org, pce-chairs <pce-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000eecb34059181765c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/oiEe5TNylndtTbbO1rkaJVcsbRI>
Subject: Re: [Pce] WG adoption poll for draft-sivabalan-pce-binding-label-sid-07
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Sep 2019 17:48:39 -0000

--000000000000eecb34059181765c
Content-Type: text/plain; charset="UTF-8"

Yes/Support.

Thanks,
Mahendra


On Tue, Aug 20, 2019 at 11:15 PM Dhruv Dhody <dhruv.ietf@gmail.com> wrote:

> Hi WG,
>
> This email begins the WG adoption poll for
> draft-sivabalan-pce-binding-label-sid-07 [1].
>
> Should this draft be adopted by the PCE WG? Please state your reasons -
> Why /
> Why not? What needs to be fixed before or after adoption? Are you willing
> to
> work on this draft? Review comments should be posted to the list.
>
> One of the chairs did a pre-adoption review [2] and authors posted a new
> revision. Note that there are known implementations.
>
> This adoption poll will end on 6th September 2019.
>
> Thanks!
> Dhruv (for the chairs)
>
>
> [1] https://tools.ietf.org/html/draft-sivabalan-pce-binding-label-sid-07
> [2] https://mailarchive.ietf.org/arch/msg/pce/oaBIRA9FnNsV6-JrKKRCdwtLysk
>
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce
>

--000000000000eecb34059181765c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Yes/Support.<br></div><div><br></div><div>Thanks,</di=
v><div>Mahendra<br></div><br></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Tue, Aug 20, 2019 at 11:15 PM Dhruv Dhody =
&lt;<a href=3D"mailto:dhruv.ietf@gmail.com" target=3D"_blank">dhruv.ietf@gm=
ail.com</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-lef=
t:1ex">Hi WG,<br>
<br>
This email begins the WG adoption poll for<br>
draft-sivabalan-pce-binding-label-sid-07 [1].<br>
<br>
Should this draft be adopted by the PCE WG? Please state your reasons - Why=
 /<br>
Why not? What needs to be fixed before or after adoption? Are you willing t=
o<br>
work on this draft? Review comments should be posted to the list.<br>
<br>
One of the chairs did a pre-adoption review [2] and authors posted a new<br=
>
revision. Note that there are known implementations.<br>
<br>
This adoption poll will end on 6th September 2019.<br>
<br>
Thanks!<br>
Dhruv (for the chairs)<br>
<br>
<br>
[1] <a href=3D"https://tools.ietf.org/html/draft-sivabalan-pce-binding-labe=
l-sid-07" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/=
draft-sivabalan-pce-binding-label-sid-07</a><br>
[2] <a href=3D"https://mailarchive.ietf.org/arch/msg/pce/oaBIRA9FnNsV6-JrKK=
RCdwtLysk" rel=3D"noreferrer" target=3D"_blank">https://mailarchive.ietf.or=
g/arch/msg/pce/oaBIRA9FnNsV6-JrKKRCdwtLysk</a><br>
<br>
_______________________________________________<br>
Pce mailing list<br>
<a href=3D"mailto:Pce@ietf.org" target=3D"_blank">Pce@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/pce" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/pce</a><br>
</blockquote></div>

--000000000000eecb34059181765c--


From nobody Sun Sep  1 11:04:13 2019
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 53491120099; Sun,  1 Sep 2019 11:04:05 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: pce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.100.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: pce@ietf.org
Message-ID: <156736104527.16990.7508505565687302370@ietfa.amsl.com>
Date: Sun, 01 Sep 2019 11:04:05 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/SNFSM8GsAezpbAlmaX3Zsw_rqHM>
Subject: [Pce] I-D Action: draft-ietf-pce-stateful-path-protection-10.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Sep 2019 18:04:05 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Path Computation Element WG of the IETF.

        Title           : PCEP Extensions for Associating Working and Protection LSPs with Stateful PCE
        Authors         : Hariharan Ananthakrishnan
                          Siva Sivabalan
                          Colby Barth
                          Ina Minei
                          Mahendra Singh Negi
	Filename        : draft-ietf-pce-stateful-path-protection-10.txt
	Pages           : 16
	Date            : 2019-09-01

Abstract:
   An active stateful Path Computation Element (PCE) is capable of
   computing as well as controlling via Path Computation Element
   Communication Protocol (PCEP) Multiprotocol Label Switching Traffic
   Engineering Label Switched Paths (MPLS LSP).  Furthermore, it is also
   possible for an active stateful PCE to create, maintain, and delete
   LSPs.  This document defines the PCEP extension to associate two or
   more LSPs to provide end-to-end path protection.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-path-protection/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-pce-stateful-path-protection-10
https://datatracker.ietf.org/doc/html/draft-ietf-pce-stateful-path-protection-10

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-pce-stateful-path-protection-10


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Mon Sep  2 01:50:18 2019
Return-Path: <wangaijun@tsinghua.org.cn>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59BB512011D; Mon,  2 Sep 2019 01:50:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6sk8MsaXUC_N; Mon,  2 Sep 2019 01:50:13 -0700 (PDT)
Received: from m176115.mail.qiye.163.com (m176115.mail.qiye.163.com [59.111.176.115]) by ietfa.amsl.com (Postfix) with ESMTP id 9854F120118; Mon,  2 Sep 2019 01:50:12 -0700 (PDT)
Received: from WangajPC (unknown [219.142.69.77]) by m176115.mail.qiye.163.com (Hmail) with ESMTPA id 9B52B6627B0; Mon,  2 Sep 2019 16:50:05 +0800 (CST)
From: "Aijun Wang" <wangaijun@tsinghua.org.cn>
To: "'Dhruv Dhody'" <dhruv.ietf@gmail.com>, <pce@ietf.org>
Cc: "'pce-chairs'" <pce-chairs@ietf.org>
References: <CAB75xn44Q8Y_eeGDfV+ecojJt0gKd9zHU4B7V0Xn_PYneCQAeg@mail.gmail.com>
In-Reply-To: <CAB75xn44Q8Y_eeGDfV+ecojJt0gKd9zHU4B7V0Xn_PYneCQAeg@mail.gmail.com>
Date: Mon, 2 Sep 2019 16:50:06 +0800
Message-ID: <014901d5616b$6b906dc0$42b14940$@org.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AdVXfw+CfKqeBlUsQKWQmLYTKeoM2gJ6/oxg
Content-Language: zh-cn
X-HM-Spam-Status: e1kfGhgUHx5ZQUtXWQgYFAkeWUFZVktVSEpCQkJCTE5PT0lDQ01PWVdZKF lBSkxLS0o3V1ktWUFJV1kJDhceCFlBWTU0KTY6NyQpLjc#WQY+
X-HM-Sender-Digest: e1kMHhlZQR0aFwgeV1kSHx4VD1lBWUc6NSI6CBw4MTlLIyI#E00VShxP PBwaFANVSlVKTk1MT0pPSUpLQkhOVTMWGhIXVQwaFRwaEhEOFTsPCBIVHBMOGlUUCRxVGBVFWVdZ EgtZQVlJSkJVSk9JVU1CVUxMWVdZCAFZQUlMS0g3Bg++
X-HM-Tid: 0a6cf12abd279373kuws9b52b6627b0
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/8hYst-WyWEO-brgIXJO38VdQXpg>
Subject: [Pce] =?gb2312?b?tPC4tDogIFdHIGFkb3B0aW9uIHBvbGwgZm9yIGRyYWZ0?= =?gb2312?b?LXNpdmFiYWxhbi1wY2UtYmluZGluZy1sYWJlbC1zaWQtMDc=?=
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Sep 2019 08:50:16 -0000

Yes/Support.

I think such mechanism is necessary for the interoperation of SR and
RSVP-TE, and can overcome some shortcomings of SR technology.

Aijun Wang.

-----=D3=CA=BC=FE=D4=AD=BC=FE-----
=B7=A2=BC=FE=C8=CB: pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] =
=B4=FA=B1=ED Dhruv Dhody
=B7=A2=CB=CD=CA=B1=BC=E4: 2019=C4=EA8=D4=C221=C8=D5 1:45
=CA=D5=BC=FE=C8=CB: pce@ietf.org
=B3=AD=CB=CD: pce-chairs
=D6=F7=CC=E2: [Pce] WG adoption poll for =
draft-sivabalan-pce-binding-label-sid-07

Hi WG,

This email begins the WG adoption poll for
draft-sivabalan-pce-binding-label-sid-07 [1].

Should this draft be adopted by the PCE WG? Please state your reasons - =
Why
/ Why not? What needs to be fixed before or after adoption? Are you =
willing
to work on this draft? Review comments should be posted to the list.

One of the chairs did a pre-adoption review [2] and authors posted a new
revision. Note that there are known implementations.

This adoption poll will end on 6th September 2019.

Thanks!
Dhruv (for the chairs)


[1] https://tools.ietf.org/html/draft-sivabalan-pce-binding-label-sid-07
[2] =
https://mailarchive.ietf.org/arch/msg/pce/oaBIRA9FnNsV6-JrKKRCdwtLysk

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


From nobody Tue Sep  3 00:00:34 2019
Return-Path: <dhruv.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2845E12021D; Tue,  3 Sep 2019 00:00:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.998
X-Spam-Level: 
X-Spam-Status: No, score=-0.998 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, FREEMAIL_REPLY=1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 Y3Y6CjEPBcB4; Tue,  3 Sep 2019 00:00:25 -0700 (PDT)
Received: from mail-io1-xd35.google.com (mail-io1-xd35.google.com [IPv6:2607:f8b0:4864:20::d35]) (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 7A53C1201E4; Tue,  3 Sep 2019 00:00:25 -0700 (PDT)
Received: by mail-io1-xd35.google.com with SMTP id x4so33415670iog.13; Tue, 03 Sep 2019 00:00:25 -0700 (PDT)
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:content-transfer-encoding; bh=1xf+v81TeaD+Gg+FFVOjhg/jc2Y9NaL1OCMxJJPcNEU=; b=WM/XLBX6X6wS+c+ZkS+to3Ms/nJgw9fp1Q9xYxG0Xt/uGrmoc/QJd7yGilLXJOfq8t R7Zh+BaNk7tLbj9eQ+dqzZNHZ51PB5XWR+kO3X12VMMN7hSHWM+uf+cB9CKWlA+T8/Tl nPbyr/BuIdpVItdNHLNBfGPgj+CKz/5neT/9iOlnqib/3E1C9C6xvSv6djkZw061R4w+ q1JDmX22jOyF+gDWxC2u1ub0ZX1XSfv3k3BHFXznyj16QcdI+yt35dFZ+sJmEBkPJkKB yFuoOnYczI03TRHzGlnl4685pt7XCunjOPT53CHjdbQnPk0TyOt2ycBDIBRzv8A8TUQR pq8Q==
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:content-transfer-encoding; bh=1xf+v81TeaD+Gg+FFVOjhg/jc2Y9NaL1OCMxJJPcNEU=; b=MYL3L9VJD97tmTUs7x3CeI05jZDUH7d527wxiooyUCFATtCNJVeEbSaub4GoRJ4Mpf r7Q7175T8wm42dLTnbgnlB2Go/D65Ov25hHt7v+n9/RivmCLKLD9zy8Ux3RKYpCLCWkm 5oGluhcc4IU2dczZmI3bDj+n3M+z45/3MH2Hon1ZTZ+3XaHHfzBkSNmyd8aUW2J5As1s WgnvOS17DaFieyJj9ovpzAYEVso+tKPfknAr/gHxJnm/T2uKXK2D4Ozv22kTm1sthwLU Qhcwqh2mJXHBFnsyLDngFSG4og1tpTwT4bC+QoLgoIB7gcI29sPMj/MJevcNW4B3qxtl mPwg==
X-Gm-Message-State: APjAAAUDBy0MSC5aEP/4j4WIbBMpIwTZVlEnIKaZ4Abvp4JJq2OuAqxt xvbGhXcq+VVzn3YSHtpu6RvbfLwsMwXfQ8X5spw=
X-Google-Smtp-Source: APXvYqysMBsdei7s5RQyY2/2aTSFS8DO8OVAlYakAStEjFB5NFfzycuJtjEvLLGGlx8w+VCEXsdXmlje4ovItoICqF4=
X-Received: by 2002:a6b:c38f:: with SMTP id t137mr3920168iof.137.1567494024497;  Tue, 03 Sep 2019 00:00:24 -0700 (PDT)
MIME-Version: 1.0
References: <CAF4+nEENTRBsZzvwPtSfTjBS+msotyqtSXmogn97Z_fa8aNWLw@mail.gmail.com>
In-Reply-To: <CAF4+nEENTRBsZzvwPtSfTjBS+msotyqtSXmogn97Z_fa8aNWLw@mail.gmail.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Tue, 3 Sep 2019 12:29:48 +0530
Message-ID: <CAB75xn5S7jmS_f5jz=kxBWHQM6AK29a0O7vkFQ-=w=oSBxXzpw@mail.gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Cc: "iesg@ietf.org" <iesg@ietf.org>, draft-ietf-pce-stateful-path-protection.all@ietf.org,  secdir <secdir@ietf.org>, pce@ietf.org, Mahend Negi <mahend.ietf@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/Vsi6hgAXzlxg5baezEyWVLzPscI>
Subject: Re: [Pce] SECDIR review of draft-ietf-pce-stateful-path-protection
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Sep 2019 07:00:27 -0000

Hi Donald,

Thanks for your review.

On Thu, Aug 29, 2019 at 8:21 PM Donald Eastlake <d3e3e3@gmail.com> wrote:
>
> I have reviewed this document as part of the Security Directorate's ongoi=
ng effort to review all IETF documents being processed by the IESG.  Docume=
nt editors and WG chairs should treat these comments just like any other la=
st call comments.
>
> The summary of the review is Almost Ready.
>
> This document specifies an extension to the stateful Path Computation Ele=
ment Communication Protocol to associate two or more Label Switched Paths f=
or the purpose of setting up path protection.
>
> This is not at all my area of expertise. The Security Considerations sect=
ion primarily refers to the Security Considerations in existing RFCs and on=
e draft, draft-ietf-pce-association-group (which is already in the RFC Edit=
or queue). I think these references are pretty thorough and provide good se=
curity coverage and advice with one possible exception. Given that this doc=
ument specifies a new facility, it seems likely that a few narrow sentences=
 would be in order about the damage an adversary could cause by specificall=
y monkeying with that new facility.
>

I see that authors have posted a new revision (-10) that has this sentence =
-

   Adding a spurious protection LSP
   to the Path Protection Association group could give false sense of
   network reliability, which leads to issues when the working LSP is
   down and the protection LSP fails as well.

https://tools.ietf.org/html/draft-ietf-pce-stateful-path-protection-10#sect=
ion-7

Does this work for you?

Thanks!
Dhruv


> Tiny nits:
> In abstract and other places when referring to what this standards track =
draft does: "describes" -> "specifies" or "defines"
> Draft references draft-ietf-pce-association-diversity-08 when latest vers=
ion is -09
>
> Thanks,
> Donald
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  1424 Pro Shop Court, Davenport, FL 33896 USA
>  d3e3e3@gmail.com


From nobody Tue Sep  3 06:17:32 2019
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CEB0120052; Tue,  3 Sep 2019 06:17:30 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: pce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.100.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: pce@ietf.org
Message-ID: <156751665049.9694.10777362163608844974@ietfa.amsl.com>
Date: Tue, 03 Sep 2019 06:17:30 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/jbAYD_SiYb9bhdOKcGJHib_2kU0>
Subject: [Pce] I-D Action: draft-ietf-pce-stateful-hpce-12.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Sep 2019 13:17:31 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Path Computation Element WG of the IETF.

        Title           : Hierarchical Stateful Path Computation Element (PCE).
        Authors         : Dhruv Dhody
                          Young Lee
                          Daniele Ceccarelli
                          Jongyoon Shin
                          Daniel King
	Filename        : draft-ietf-pce-stateful-hpce-12.txt
	Pages           : 23
	Date            : 2019-09-03

Abstract:
   A Stateful Path Computation Element (PCE) maintains information on
   the current network state, including: computed Label Switched Path
   (LSPs), reserved resources within the network, and pending path
   computation requests. This information may then be considered when
   computing new traffic engineered LSPs, and for associated and
   dependent LSPs, received from Path Computation Clients (PCCs). The
   Path computation response from a PCE is helpful for the PCC to
   gracefully establish the computed LSP.

   The Hierarchical Path Computation Element (H-PCE) architecture,
   provides an architecture to allow the optimum sequence of
   inter-connected domains to be selected, and network policy to be
   applied if applicable, via the use of a hierarchical relationship
   between PCEs.

   Combining the capabilities of Stateful PCE and the Hierarchical PCE
   would be advantageous. This document describes general considerations
   and use cases for the deployment of Stateful, and not Stateless, PCEs
   using the Hierarchical PCE architecture.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-hpce/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-pce-stateful-hpce-12
https://datatracker.ietf.org/doc/html/draft-ietf-pce-stateful-hpce-12

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-pce-stateful-hpce-12


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Sep  3 11:17:13 2019
Return-Path: <d3e3e3@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D088212023E; Tue,  3 Sep 2019 11:17:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.747
X-Spam-Level: 
X-Spam-Status: No, score=-1.747 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, 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=no 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 c6pBnF08Nm-e; Tue,  3 Sep 2019 11:17:03 -0700 (PDT)
Received: from mail-io1-xd30.google.com (mail-io1-xd30.google.com [IPv6:2607:f8b0:4864:20::d30]) (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 1BBC712013D; Tue,  3 Sep 2019 11:17:03 -0700 (PDT)
Received: by mail-io1-xd30.google.com with SMTP id u185so34279841iod.10; Tue, 03 Sep 2019 11:17:03 -0700 (PDT)
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=uGCAiz4TAWOhAFpH19Kj+PJYDPle7to29PcMTBcRwPI=; b=hrn5Lx0SPMm8wHNNVoVnF78CTWLXuzCcEBHF3q2XH26Xm247EQtR05GR9/uG5EVEXp /WMeA67y1ARnvmpCGAuQaW6SJAc3SkjBPAgPXdix5dJuLFHy24qEhj8rDkYddyF7iZuH S6VrZ/2eOuZjv9+OiQFh0+WgVoUnMDU/cJ6EPzT7Ij59w1HhKvOS2YVqu4yE1BdwyUAd WtUxTJzXUPPd2y0tAR6IB1WLOh6r4BmyvYiXZ87W4Rhk25LxksMGvBH08hj3zQ/1J6T/ IW27S1rdnV7bhlpqGWEOiQtoPUO8zff8neN9ScvoVux64vbPOAeoyuhx1E+wS7PQcew7 Pf4Q==
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=uGCAiz4TAWOhAFpH19Kj+PJYDPle7to29PcMTBcRwPI=; b=s3z+RfssC1Xd2YdoTk5ZDoIDkkiesGXRiV6au5QipZy7wJOOfeLnWfkauHY9axqaYl LHC1/eH6XVDF5Tn63W9yprl7idS+sdy17Kz8lp3N6VVDME58nb4Zbo4W+kH2PsrAEPEy xHqO/IbC8yBNszxp31f7ZrKXfMr9medm3mbLPBaf1PZuCD6yVD3nZnIWovtOIwfUrfeN zPZS5yHY77JKDdAap2APTO/ntpc9aBPt6FIKsQBlOl0Ct8C07wGnxiMEXZ0WMJT3pS7l ZXbJ3jjEchR4n2wYXh9KIN0T2xoqAWFpgpzI0iOhe2oQN/DuuByD//bRRXg0l13d3ADe I9iA==
X-Gm-Message-State: APjAAAUvxdQeFTb9GxWr3YnUF+JZ/3ZCEcpYDjAfx9a902Sp7vY5bk1L DODbT234Up1IU0JzS3NQOGul708uMu0XOiS2cLM=
X-Google-Smtp-Source: APXvYqxh3bUaom6Nno9TddRePgOw4JS0A5j1dCDWp11mYW2mJi9YJfVsfl1EFIQToUx9XS2zOZ/cfJhA8+ShaavWN0U=
X-Received: by 2002:a6b:6a15:: with SMTP id x21mr22248735iog.40.1567534622252;  Tue, 03 Sep 2019 11:17:02 -0700 (PDT)
MIME-Version: 1.0
References: <CAF4+nEENTRBsZzvwPtSfTjBS+msotyqtSXmogn97Z_fa8aNWLw@mail.gmail.com> <CAB75xn5S7jmS_f5jz=kxBWHQM6AK29a0O7vkFQ-=w=oSBxXzpw@mail.gmail.com>
In-Reply-To: <CAB75xn5S7jmS_f5jz=kxBWHQM6AK29a0O7vkFQ-=w=oSBxXzpw@mail.gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 3 Sep 2019 14:16:51 -0400
Message-ID: <CAF4+nEEwuMq8-JPgyEAPKdpUV2TJh-t0iRrAeVmQiNJkCArfPQ@mail.gmail.com>
To: Dhruv Dhody <dhruv.ietf@gmail.com>
Cc: "iesg@ietf.org" <iesg@ietf.org>, draft-ietf-pce-stateful-path-protection.all@ietf.org,  secdir <secdir@ietf.org>, pce@ietf.org, Mahend Negi <mahend.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000005525570591aa18e9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/w2aQN7TPs3DhENvqe2wTklJZC7s>
Subject: Re: [Pce] SECDIR review of draft-ietf-pce-stateful-path-protection
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Sep 2019 18:17:05 -0000

--0000000000005525570591aa18e9
Content-Type: text/plain; charset="UTF-8"

Hi,

That change looks good to me.

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 1424 Pro Shop Court, Davenport, FL 33896 USA
 d3e3e3@gmail.com


On Tue, Sep 3, 2019 at 3:00 AM Dhruv Dhody <dhruv.ietf@gmail.com> wrote:

> Hi Donald,
>
> Thanks for your review.
>
> On Thu, Aug 29, 2019 at 8:21 PM Donald Eastlake <d3e3e3@gmail.com> wrote:
> >
> > I have reviewed this document as part of the Security Directorate's
> ongoing effort to review all IETF documents being processed by the IESG.
> Document editors and WG chairs should treat these comments just like any
> other last call comments.
> >
> > The summary of the review is Almost Ready.
> >
> > This document specifies an extension to the stateful Path Computation
> Element Communication Protocol to associate two or more Label Switched
> Paths for the purpose of setting up path protection.
> >
> > This is not at all my area of expertise. The Security Considerations
> section primarily refers to the Security Considerations in existing RFCs
> and one draft, draft-ietf-pce-association-group (which is already in the
> RFC Editor queue). I think these references are pretty thorough and provide
> good security coverage and advice with one possible exception. Given that
> this document specifies a new facility, it seems likely that a few narrow
> sentences would be in order about the damage an adversary could cause by
> specifically monkeying with that new facility.
> >
>
> I see that authors have posted a new revision (-10) that has this sentence
> -
>
>    Adding a spurious protection LSP
>    to the Path Protection Association group could give false sense of
>    network reliability, which leads to issues when the working LSP is
>    down and the protection LSP fails as well.
>
>
> https://tools.ietf.org/html/draft-ietf-pce-stateful-path-protection-10#section-7
>
> Does this work for you?
>
> Thanks!
> Dhruv
>
>
> > Tiny nits:
> > In abstract and other places when referring to what this standards track
> draft does: "describes" -> "specifies" or "defines"
> > Draft references draft-ietf-pce-association-diversity-08 when latest
> version is -09
> >
> > Thanks,
> > Donald
> > ===============================
> >  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
> >  1424 Pro Shop Court, Davenport, FL 33896 USA
> >  d3e3e3@gmail.com
>

--0000000000005525570591aa18e9
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div><br></div><div>That change looks good to me.</div>=
<div><br clear=3D"all"><div><div dir=3D"ltr" class=3D"gmail_signature" data=
-smartmail=3D"gmail_signature">Thanks,<br>Donald<br>=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br=
>=C2=A0Donald E. Eastlake 3rd =C2=A0 +1-508-333-2270 (cell)<br>=C2=A01424 P=
ro Shop Court, Davenport, FL 33896 USA<br>=C2=A0<a href=3D"mailto:d3e3e3@gm=
ail.com" target=3D"_blank">d3e3e3@gmail.com</a></div></div><br></div></div>=
<br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue=
, Sep 3, 2019 at 3:00 AM Dhruv Dhody &lt;<a href=3D"mailto:dhruv.ietf@gmail=
.com">dhruv.ietf@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gma=
il_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,2=
04,204);padding-left:1ex">Hi Donald,<br>
<br>
Thanks for your review.<br>
<br>
On Thu, Aug 29, 2019 at 8:21 PM Donald Eastlake &lt;<a href=3D"mailto:d3e3e=
3@gmail.com" target=3D"_blank">d3e3e3@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt; I have reviewed this document as part of the Security Directorate&#39;=
s ongoing effort to review all IETF documents being processed by the IESG.=
=C2=A0 Document editors and WG chairs should treat these comments just like=
 any other last call comments.<br>
&gt;<br>
&gt; The summary of the review is Almost Ready.<br>
&gt;<br>
&gt; This document specifies an extension to the stateful Path Computation =
Element Communication Protocol to associate two or more Label Switched Path=
s for the purpose of setting up path protection.<br>
&gt;<br>
&gt; This is not at all my area of expertise. The Security Considerations s=
ection primarily refers to the Security Considerations in existing RFCs and=
 one draft, draft-ietf-pce-association-group (which is already in the RFC E=
ditor queue). I think these references are pretty thorough and provide good=
 security coverage and advice with one possible exception. Given that this =
document specifies a new facility, it seems likely that a few narrow senten=
ces would be in order about the damage an adversary could cause by specific=
ally monkeying with that new facility.<br>
&gt;<br>
<br>
I see that authors have posted a new revision (-10) that has this sentence =
-<br>
<br>
=C2=A0 =C2=A0Adding a spurious protection LSP<br>
=C2=A0 =C2=A0to the Path Protection Association group could give false sens=
e of<br>
=C2=A0 =C2=A0network reliability, which leads to issues when the working LS=
P is<br>
=C2=A0 =C2=A0down and the protection LSP fails as well.<br>
<br>
<a href=3D"https://tools.ietf.org/html/draft-ietf-pce-stateful-path-protect=
ion-10#section-7" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.o=
rg/html/draft-ietf-pce-stateful-path-protection-10#section-7</a><br>
<br>
Does this work for you?<br>
<br>
Thanks!<br>
Dhruv<br>
<br>
<br>
&gt; Tiny nits:<br>
&gt; In abstract and other places when referring to what this standards tra=
ck draft does: &quot;describes&quot; -&gt; &quot;specifies&quot; or &quot;d=
efines&quot;<br>
&gt; Draft references draft-ietf-pce-association-diversity-08 when latest v=
ersion is -09<br>
&gt;<br>
&gt; Thanks,<br>
&gt; Donald<br>
&gt; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D<br>
&gt;=C2=A0 Donald E. Eastlake 3rd=C2=A0 =C2=A0+1-508-333-2270 (cell)<br>
&gt;=C2=A0 1424 Pro Shop Court, Davenport, FL 33896 USA<br>
&gt;=C2=A0 <a href=3D"mailto:d3e3e3@gmail.com" target=3D"_blank">d3e3e3@gma=
il.com</a><br>
</blockquote></div>

--0000000000005525570591aa18e9--


From nobody Wed Sep  4 01:37:01 2019
Return-Path: <Jonathan.Hardwick@metaswitch.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 074E412020A; Wed,  4 Sep 2019 01:36:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=metaswitch.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 IEOlBZ1AHSxh; Wed,  4 Sep 2019 01:36:52 -0700 (PDT)
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (mail-eopbgr780109.outbound.protection.outlook.com [40.107.78.109]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 103B91201CE; Wed,  4 Sep 2019 01:36:51 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=hoQUnEOLgr2dBcRvpJf9+NKb0pDawEk5x0kY3up5SJzheO1s+y13givBwQOco/NIDVE4OePArhnST3sw+srJD4yK0/A3orCKA7yA1lK86FOJM5UyfUOYgkgIJGFG85y3GpDdp+jwmQ5sDjjcbDcHQbxb2WnlVyEm/xKpHn9z0VGeGVOpxa/4j/h0KGR8I5veZ2pU/v8PTXP7MZ+s6nVhF/jvw4szEutd3HfyHnOIxVpkdFFilmCFbGhxRtHfop9Ht7I8+Dfik6mjkB3JlRRUW1gbpzYxDbN7VOuBiyVt8MYZTAizmz0GRjjHjeEgguo3QB36ifEOmjqufnp/WvlSzQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=7sA8JDxp8rTcMsV5ukWH9vt+Rqg5SdUXQTT8as0k3/8=; b=YEPeG2tW4pfli+1rmDJyjsbIPY6UWS+jYvximHFZt0yVqy5h5JeW5GvE0zwaoFEhACwyKn140SFP/iqKhgOC634OHeMede7J3lEnhQzi1SmaZ6eYyVYouLtJ1KlC0fxjbFsL33V/xUL4tdLhEfzmQZiuw2ONCYNfKz6VVYBVY/eUKXAtnZZRRwlkdFr9IAkr2V6CePYRbTjhOX4uU1vd4v7sq876mTMvV2zGWA29j/Da8oxtO0JVAjE/bhBRTyGeIrnR3xHoH2i6xomxvtUa3ZbVSTmYgBwn3a8zjRQh1fa2q4ztjf8VPcojNbMXbb9eGrhYbRmAdntbWRfv9HP6Ew==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=metaswitch.com; dmarc=pass action=none header.from=metaswitch.com; dkim=pass header.d=metaswitch.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=metaswitch.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=7sA8JDxp8rTcMsV5ukWH9vt+Rqg5SdUXQTT8as0k3/8=; b=j6ttWawk/hdMzlpb3/9MtqE2qhYFyInd77DG1KvXPARVVLtsHp6bCM/uPs8OZ2LgCiP4UniWztP4dGi+sT2PxhZUwXtQoqlsKt6ciGzeVzMifx8Rt4Qsud+IKb05yMQO7Aygr322QGsjmSbZtKyIFHM6kJHI9foeRXTYlX8WCWs=
Received: from BL0PR02MB4868.namprd02.prod.outlook.com (20.177.144.87) by BL0PR02MB4516.namprd02.prod.outlook.com (10.167.180.95) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2199.20; Wed, 4 Sep 2019 08:36:50 +0000
Received: from BL0PR02MB4868.namprd02.prod.outlook.com ([fe80::e812:c885:c3a1:457b]) by BL0PR02MB4868.namprd02.prod.outlook.com ([fe80::e812:c885:c3a1:457b%5]) with mapi id 15.20.2220.022; Wed, 4 Sep 2019 08:36:50 +0000
From: Jonathan Hardwick <Jonathan.Hardwick@metaswitch.com>
To: Dhruv Dhody <dhruv.ietf@gmail.com>, "pce@ietf.org" <pce@ietf.org>
CC: pce-chairs <pce-chairs@ietf.org>
Thread-Topic: [Pce] WG adoption poll for draft-sivabalan-pce-binding-label-sid-07
Thread-Index: AQHVV38OtysJ8aJYD027+bhg2X6BpacbR2aA
Date: Wed, 4 Sep 2019 08:36:49 +0000
Message-ID: <BL0PR02MB486820EE831D61892FE8212B84B80@BL0PR02MB4868.namprd02.prod.outlook.com>
References: <CAB75xn44Q8Y_eeGDfV+ecojJt0gKd9zHU4B7V0Xn_PYneCQAeg@mail.gmail.com>
In-Reply-To: <CAB75xn44Q8Y_eeGDfV+ecojJt0gKd9zHU4B7V0Xn_PYneCQAeg@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ts-tracking-id: 54aeed9f-d750-4c2f-b008-80e4d3310769.0
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Jonathan.Hardwick@metaswitch.com; 
x-originating-ip: [86.136.127.59]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 85362b7c-8900-471e-9f1e-08d7311307ce
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600166)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:BL0PR02MB4516; 
x-ms-traffictypediagnostic: BL0PR02MB4516:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <BL0PR02MB4516389C59E0CF475EB7887784B80@BL0PR02MB4516.namprd02.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0150F3F97D
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(346002)(376002)(396003)(366004)(136003)(39850400004)(199004)(189003)(13464003)(26005)(53546011)(186003)(3846002)(6116002)(7736002)(102836004)(316002)(76176011)(7696005)(86362001)(99286004)(9686003)(2501003)(66066001)(110136005)(478600001)(8936002)(66446008)(74316002)(229853002)(64756008)(25786009)(966005)(6506007)(8676002)(14454004)(256004)(14444005)(81156014)(71200400001)(55016002)(305945005)(6306002)(66476007)(66946007)(66556008)(76116006)(52536014)(5660300002)(486006)(11346002)(446003)(476003)(2906002)(6246003)(4326008)(71190400001)(33656002)(6436002)(53936002)(81166006); DIR:OUT; SFP:1102; SCL:1; SRVR:BL0PR02MB4516; H:BL0PR02MB4868.namprd02.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: metaswitch.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: KWM93m3XSJlzXkWXcQjv9LS+P0ExIWEMa7JMN4sfaa23eyoYcwwJ5JWmRy/Bb+6I9prILSfgh5rQe2Hb5lf0XcmKlkjsgWpCKwrb6t++65l8zo2b9p2I3B5lIa4MGpCP0VmNbgNZtp3HG/jhGsM1WE8+UJ9l0c3hWgFVWnmk7HG+z9B1MHG393mf0xufXjUEPTDJ87hGnBM0Sod2Y19AjnKJa0l+aMUl0Q4G6ETtfhTVj6KnKLLgXiWR4ORSFh6IlYMjPjin2lZp1WnuVMjxWCqYqs0bPrQ/1AYcwnN8oivHUBwpetc7ZmXZ9XX8A4hrOqiKBmAZGhV8pKiKlBPtx1gJ5XqGtdSWvrvTcq1X9oaW8mX4UG94SoHaCsL9InVEaN8xn0Spcp7KYK4jvz40+mtHnRtmKXP5GlwEQa13Hs8=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: metaswitch.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 85362b7c-8900-471e-9f1e-08d7311307ce
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Sep 2019 08:36:49.9976 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 9d9e56eb-f613-4ddb-b27b-bfcdf14b2cdb
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: zqYZPfWYSMbqqB90fps8UrR3YiK4m9+usKmTwxsvWjvkrOr5BT4G5CWhMBJRI8+Hxvf3+Cs6mB++GF3ZrXSVCA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL0PR02MB4516
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/u8vOJjIgyRICZ_bxZ4X-t_zvqO8>
Subject: Re: [Pce] WG adoption poll for draft-sivabalan-pce-binding-label-sid-07
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Sep 2019 08:37:00 -0000

I support adoption of this draft (as co-author).
The binding label provides a mechanism for interworking between separate MP=
LS switching domains, which is an important consideration as SR is rolled o=
ut.  Extending PCEP with this capability is a logical and necessary step.

Cheers
Jon

-----Original Message-----
From: Pce <pce-bounces@ietf.org> On Behalf Of Dhruv Dhody
Sent: 20 August 2019 18:45
To: pce@ietf.org
Cc: pce-chairs <pce-chairs@ietf.org>
Subject: [Pce] WG adoption poll for draft-sivabalan-pce-binding-label-sid-0=
7

NOTE: Message is from an external sender

Hi WG,

This email begins the WG adoption poll for
draft-sivabalan-pce-binding-label-sid-07 [1].

Should this draft be adopted by the PCE WG? Please state your reasons - Why=
 / Why not? What needs to be fixed before or after adoption? Are you willin=
g to work on this draft? Review comments should be posted to the list.

One of the chairs did a pre-adoption review [2] and authors posted a new re=
vision. Note that there are known implementations.

This adoption poll will end on 6th September 2019.

Thanks!
Dhruv (for the chairs)


[1] https://tools.ietf.org/html/draft-sivabalan-pce-binding-label-sid-07
[2] https://mailarchive.ietf.org/arch/msg/pce/oaBIRA9FnNsV6-JrKKRCdwtLysk

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


From nobody Fri Sep  6 01:07:31 2019
Return-Path: <session-request@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CEAA12007C; Fri,  6 Sep 2019 01:07:29 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Meeting Session Request Tool <session-request@ietf.org>
To: <session-request@ietf.org>
Cc: dhruv.ietf@gmail.com, pce@ietf.org, db3546@att.com, pce-chairs@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.100.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <156775724917.22005.11296780458514657671.idtracker@ietfa.amsl.com>
Date: Fri, 06 Sep 2019 01:07:29 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/U3bjbpHBJDKBKJF1oQsLQjvkdIo>
Subject: [Pce] pce - New Meeting Session Request for IETF 106
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Sep 2019 08:07:30 -0000

A new meeting session request has just been submitted by Dhruv Dhody, a Chair of the pce working group.


---------------------------------------------------------
Working Group Name: Path Computation Element
Area Name: Routing Area
Session Requester: Dhruv Dhody

Number of Sessions: 1
Length of Session(s):  2 Hours
Number of Attendees: 75
Conflicts to Avoid: 
 Chair Conflict: spring teas ccamp
 Technology Overlap: bier panrg
 Key Participant Conflict: mpls rift rtgwg detnet idr lsr sfc pals opsawg bess netconf netmod 6man


People who must be present:
  Deborah Brungard
  Julien Meuric
  Dhruv Dhody
  Hariharan Ananthakrishnan

Resources Requested:

Special Requests:
  Do not schedule against RTG area BOF (if any)
---------------------------------------------------------


From nobody Fri Sep  6 02:47:04 2019
Return-Path: <dhruv.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DE96120098; Fri,  6 Sep 2019 02:46:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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, 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 Iq_nl4atM4kk; Fri,  6 Sep 2019 02:46:45 -0700 (PDT)
Received: from mail-io1-xd29.google.com (mail-io1-xd29.google.com [IPv6:2607:f8b0:4864:20::d29]) (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 6312612008F; Fri,  6 Sep 2019 02:46:45 -0700 (PDT)
Received: by mail-io1-xd29.google.com with SMTP id u185so11292255iod.10; Fri, 06 Sep 2019 02:46:45 -0700 (PDT)
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=a3LUXK9qProq5M7gDK2RmXnz25rvUwDAKlGLc+NyhVo=; b=GdObEomjJYwwBYSd3TR5r+GlRbtwElPpQunoEuQuWX6IyMcKBWZ4rIMrAnd+dumkWc 5QexZvS9u55W/YVGO9HUB1eB0JQbU9aRMban+95iZGVA71Hg9BHbgVlOFLWfFLg4gLcR Ehb5f3aYpkhTEWjNlQLVczWog5ifaGXGEiEMRDfmoKqdJWgVk9+oUjslAWNxc0XqiCuY EhJLwzu9jdiMliD6HHWhBGXsd5LKCzPzvxFqmUbuz34+qKCqNT2adGJwzXpFWp6YzUlt iMdctQIXIrCwDyPpLaEuFeKL3FeG7r6MdksSfyZ6FUkikNuoTBWWtAJeFQnPONl7ffON rfVg==
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=a3LUXK9qProq5M7gDK2RmXnz25rvUwDAKlGLc+NyhVo=; b=OxaCD8I/2blBSFtOiHKiphQ+TGYUs9ShHsPTl4OFYqe8mJvRa+85W1NhTX/+tQOMYg SPQ7xIRaufTFBuXZRB7uZXKpYvM0izLVi1E0BZWdsJMUAoIHpqX3Csu6LGJJk1lxUl0I 0i0xlswJ/hPl07HKb9rTpUTwhvuwDef3Ng4x6GyxM4C3YWr1xBW6g7ohhqZMZA4ZJ30z B4+7PIe5tB6rwHtVGmW22ZR4eDjN18D3oIq+YpJi8NOkVWEzRTzj/d6iOp306aY51nmg 17ZCRaVSeGldqyfX3bKqoNSRoA52MuupnXsPvtugDCuxmOzx2G+QQb+rAVLPWGPescDj RRRg==
X-Gm-Message-State: APjAAAWWLvIDlolfHx81uJ48Wsw3fBJv4/GyCriNW196WiwASGyWfZpt psmaJ0s8e0xzQNvtyAZNUNdK6bHlZzI5buJtnBI=
X-Google-Smtp-Source: APXvYqx1zaGFKaAAbzMQYvAfs0j/eiZRuH2rQ627+DllEbf2/jowqzSnQdoJNFA5qdvJwgNtbLFrkRBuDO0JdyTZgiQ=
X-Received: by 2002:a5e:c301:: with SMTP id a1mr9580189iok.1.1567763204542; Fri, 06 Sep 2019 02:46:44 -0700 (PDT)
MIME-Version: 1.0
References: <156682165261.25516.1887489813169802107@ietfa.amsl.com>
In-Reply-To: <156682165261.25516.1887489813169802107@ietfa.amsl.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Fri, 6 Sep 2019 15:16:08 +0530
Message-ID: <CAB75xn4=Q5gw1Z1fcYTDgwd5BD7S+=Qsa1pt1QfjGc8nLzUhYA@mail.gmail.com>
To: Francesca Palombini <francesca.palombini@ericsson.com>
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-pce-lsp-control-request.all@ietf.org,  pce@ietf.org, "ietf@ietf.org Discussion" <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/gWNzcELjactebIOBmDZQtqFwp2A>
Subject: Re: [Pce] Genart last call review of draft-ietf-pce-lsp-control-request-08
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Sep 2019 09:46:47 -0000

Hi Francesca,

Thanks for your review. Few thoughts...

On Mon, Aug 26, 2019 at 5:44 PM Francesca Palombini via Datatracker
<noreply@ietf.org> wrote:
>
> Reviewer: Francesca Palombini
> Review result: Ready with Issues
>
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>
> For more information, please see the FAQ at
>
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>
> Document: draft-ietf-pce-lsp-control-request-08
> Reviewer: Francesca Palombini
> Review Date: 2019-08-26
> IETF LC End Date: 2019-08-28
> IESG Telechat date: Not scheduled for a telechat
>
> Summary: This draft is almost ready for publication, but has minor issues/open
> points that should be fixed before publication.
>
> Major issues: N/A
>
> Minor issues / questions:
>
> * Section 3: At the end of season 3, you indicate that this new flag has no
> meaning in PCRpt and PCInitiate messages. RFC8231 defines that the SRP Object
> MAY be carried in PCErr as well, shouldn't there be such requirements (MUST be
> set to 0, MUST be ignored on reception) for PCErr?
>

I agree. I suggest to make this generic, something like - "The C Flag
has no meaning in other PCEP messages that carry SRP object and the
flag MUST be set to 0 on transmission and MUST be ignored on receipt."

> * In the following text (Section 4): "The PCE SHOULD NOT
>    send control request for LSP which is already delegated to the PCE,
>    i.e. if the D Flag is set in the PCUpd message, then C Flag SHOULD
>    NOT be set." Why is there a SHOULD NOT instead of MUST NOT? In which
>    situation could it be acceptable or useful to request control for a
>    delegated LSP?
>

It wont be useful, but if received it would be silently ignored. It
does not rise up to a high level of error and I suspect that is why
authors used SHOULD.

> Nits/editorial comments:
>

Thanks for these, just one comment ...

> * Terminology should also include a sentence about the reader being familiar
> with at least RFC8231.
>
> * Terminology could also include what SRP stand for.
>
> * Section 3. When introducing SRP, it would have been helpful to the reader to
> reference section 7.2 of RFC8231.
>
> * Section 3. "PCE sets the C Flag to 1 to indicate that, it wishes" -- remove
> ","
>
> * Section 3. "MUST be ignored on receipt" -- "MUST be ignored on reception"
>

I have noticed 'on receipt' in many of our documents. We should leave
this one for the RFC-EDITOR maybe...

> * Section 4. When introducing the D flag, it would have been helpful to the
> reader to reference section 7.3 of RFC8231.
>
> * Section 4. "Note that, the PCUpd message with C Flag set is received" --
> "Note that, if the PCUpd message with C Flag set is received"
>
> (Please keep my address in the To: field if you want to make sure I see any
> response to this thread)
>
> Thanks,
> Francesca
>

Thanks again for your review.

Regards,
Dhruv


From nobody Fri Sep  6 07:41:36 2019
Return-Path: <hari@netflix.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8584120C3C for <pce@ietfa.amsl.com>; Fri,  6 Sep 2019 07:41:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIMWL_WL_HIGH=-0.001, 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 (1024-bit key) header.d=netflix.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 EUS-GzRr5_j1 for <pce@ietfa.amsl.com>; Fri,  6 Sep 2019 07:41:31 -0700 (PDT)
Received: from mail-vk1-xa35.google.com (mail-vk1-xa35.google.com [IPv6:2607:f8b0:4864:20::a35]) (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 4680F120B8A for <pce@ietf.org>; Fri,  6 Sep 2019 07:41:16 -0700 (PDT)
Received: by mail-vk1-xa35.google.com with SMTP id d126so1327793vkf.7 for <pce@ietf.org>; Fri, 06 Sep 2019 07:41:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netflix.com; s=google;  h=mime-version:from:date:message-id:subject:to:cc; bh=ml4aQFCkam1JvyywuZb3XEjxRy+nPIzCa8iFY4T3hfI=; b=hgxiimwkqD1qos1WFOFVP6dTyhQhctlQz6T0+lorzetcUZJ9+MFOPiGDsVoWcnEGTt rSumFpvjzefrIdToON6ylMwJnbwa/w8yrEm8CucAKMr1yPUo9vdvfgR8k5wgMSwXI06k ixTbKe/1dgOreWILADU+0/nbggCt8W1OjXInQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=ml4aQFCkam1JvyywuZb3XEjxRy+nPIzCa8iFY4T3hfI=; b=hniFV7+9w44R11yDYX0a9CYPe48iY6AIq47tXynE5vC/gOUxRN2b/Ze5ortfRTup8K gi7m9WNCgsUPUelo/723eY6/zr2LBC0uInH0iqBganUKfznS+aX8uoWRhF4uwvi7F0bv KqtIUL1toLPOl5VwOK+vu30PHpDbugKJg7FHV0Sr5A5rVsv3HjPalm0xE8LRHmoHT5w3 9KXKsow+woxwyQybUBD+mPFohfbKsPPPyvX6FDs2ZuwaH12JA615PaY66GY+JhwPwYoV nDE2txOCTh91W3OKVKEcpoiqdVP3Ops9VUxwkjujlK6921e+B4INqO5d2w+grLBVe+bx 3IqQ==
X-Gm-Message-State: APjAAAV8T7pBwRCbCqjAtArMHceMjR7vE8apmfPpRwzeYAjsQGTCD7WS SaxBrtVWAYIxBv/8yTDOFCi0idIIQQrhYuQeWj4rXay5YS/ouw==
X-Google-Smtp-Source: APXvYqx9N96kjL6kvFZMWv+swzSftSb05HCVcBMiIvkXY0hxGGCLy6Q1GANUdSWbZ/KRuYGnLkYnC+uHIpv1NOPjUd8=
X-Received: by 2002:ac5:c659:: with SMTP id j25mr30439vkl.30.1567780875112; Fri, 06 Sep 2019 07:41:15 -0700 (PDT)
MIME-Version: 1.0
From: Hariharan Ananthakrishnan <hari@netflix.com>
Date: Fri, 6 Sep 2019 07:41:04 -0700
Message-ID: <CAL70W4oEprCSQxEVAL-4DLRBnPQvsim6BdEr5nGaEdyStw=MYg@mail.gmail.com>
To: Farrel Adrian <adrian@olddog.co.uk>
Cc: pce@ietf.org
Content-Type: multipart/alternative; boundary="00000000000025bff70591e36e62"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/IzcP6cf8MdPB42oEThQzB3eg6to>
Subject: [Pce] IPR Poll on draft-farrel-pce-stateful-flags-01
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Sep 2019 14:41:34 -0000

--00000000000025bff70591e36e62
Content-Type: text/plain; charset="UTF-8"

Hi Authors,

In preparation for Working Group last call on this draft, I'd like all
authors and contributors to confirm on the list that they are in compliance
with IETF IPR rules.

Please respond (copying the mailing list) to say one of:

I am not aware of any IPR applicable to this draft that should be disclosed
in accordance with IETF IPR rules.

I am aware of IPR applicable to this draft, and it has already been
disclosed to the IETF.

I am aware of IPR applicable to this draft, but that has not yet been
disclosed to the IETF. I will work to ensure that it will be disclosed in a
timely manner.

Thanks,
- Hari

--00000000000025bff70591e36e62
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:verdana,=
sans-serif;font-size:small"><pre class=3D"gmail-m_-1415996240095654116gmail=
-m_-3549781874373280381gmail-m_5789933747195254190gmail-wordwrap" style=3D"=
white-space:pre-wrap;box-sizing:border-box;margin-top:0px;margin-bottom:1re=
m;overflow:auto;color:rgb(33,37,41);word-break:normal;padding:0px"><font fa=
ce=3D"verdana, sans-serif">Hi Authors,

In preparation for Working Group last call on this draft, I&#39;d like all
authors and contributors to confirm on the list that they are in compliance
with IETF <span class=3D"gmail-il">IPR</span> rules.

Please respond (copying the mailing list) to say one of:

I am not aware of any <span class=3D"gmail-il">IPR</span> applicable to thi=
s draft that should be disclosed
in accordance with IETF <span class=3D"gmail-il">IPR</span> rules.

I am aware of <span class=3D"gmail-il">IPR</span> applicable to this draft,=
 and it has already been
disclosed to the IETF.

I am aware of <span class=3D"gmail-il">IPR</span> applicable to this draft,=
 but that has not yet been
disclosed to the IETF. I will work to ensure that it will be disclosed in a
timely manner.

Thanks,
- Hari</font></pre></div></div>

--00000000000025bff70591e36e62--


From nobody Fri Sep  6 10:58:03 2019
Return-Path: <dhruv.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FCA8120867 for <pce@ietfa.amsl.com>; Fri,  6 Sep 2019 10:58:01 -0700 (PDT)
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, FREEMAIL_FROM=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=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 t_slC8rn_JfI for <pce@ietfa.amsl.com>; Fri,  6 Sep 2019 10:57:59 -0700 (PDT)
Received: from mail-io1-xd2f.google.com (mail-io1-xd2f.google.com [IPv6:2607:f8b0:4864:20::d2f]) (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 AD75F120809 for <pce@ietf.org>; Fri,  6 Sep 2019 10:57:59 -0700 (PDT)
Received: by mail-io1-xd2f.google.com with SMTP id s21so14722751ioa.1 for <pce@ietf.org>; Fri, 06 Sep 2019 10:57:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=ARn63arcN4EOL70aTM1RuNtiCem2MOfiL7AxFO1S5QU=; b=X+PUmZlVTqjZ5NhkgwkhjUlSuhJmlRtOeh2D+V2dFWCLFRD4vpvHMf9yyh3Lp4Oy/r U/LMgkUNAvJXC575BHi67a1G6p0oABDyvocaq2Cdp+zw3incQu4L+WYZtmswfNptnSCg qhdra3OBxi5Q5omf2OPlClO7HI6L8magQp4QAzWywXfNiHqQBZ19xO3h9tXmcBor68Ch CdI//OJlNnsAD4wnOZhKPsJ6OYu4lmrlRrGnRHR5nAqwq+qJWD1sVYedonldRSACefRa X1g3j2gMAWb1mC7PSB6lhLYBzmeJnh4g/dw1ls77fSNCHFIXlW/q/oQXLHJ6F8CIOnL8 LfqQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=ARn63arcN4EOL70aTM1RuNtiCem2MOfiL7AxFO1S5QU=; b=rN6TfDHDR0HJ2v+WxPLUHSjx4X5G3sv/XNnGzfeUYJMfcFmLzdo6eGFyFlYbYk5qqw t9QWixLVt8FAdlv87FKpxyTwhnQJHxGDBQYLT6TfjuPqvMhcyR6tJiMu8cTpjLC0bfE3 Fgy94CR9qV536Icx9xQiUZhuH5Zr/PMzACcNK/nwecUSlhVKt9dXFWIlQ45gFq8B3Cp6 LQXWVQ2b/EIs/19tcU6NSkkRpjIeAp2U1l9i4krvsLqXB3ZlaZvXM+frLsBDJ+3tbnKr Ip/hKyDm03q+XEkBVkCDa20iCCROCwSpdDwPGLL9B5pm/SyfwyPoM4BeeKBq0NUR3a3S gZ2Q==
X-Gm-Message-State: APjAAAU6qXcaZtNh5R18g+uE69MaNs1FPWFTuZjh7GXtwdz0TWYHdJ4+ Ao1wVLfNARUQLjel0iEoz1XyHi5QKHyvLqL7MTWUXpgn
X-Google-Smtp-Source: APXvYqzN7iJ9pKfOaFujEhzQJZHR42zl05C38fE5LHDloRnYhMCNZs8F1WeGE9beTcgjMJHBo3INqAMM8hvba0MRNWE=
X-Received: by 2002:a5e:c301:: with SMTP id a1mr11912931iok.1.1567792678639; Fri, 06 Sep 2019 10:57:58 -0700 (PDT)
MIME-Version: 1.0
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Fri, 6 Sep 2019 23:27:22 +0530
Message-ID: <CAB75xn6OACdFe0w1paSYTSWAKB_dGJE443uOC02KuyZYGY1tqg@mail.gmail.com>
To: pce@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/YYPmfpqYYO36ypY7etzIHH79i7s>
Subject: [Pce] WG adoption of draft-sivabalan-pce-binding-label-sid-07
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Sep 2019 17:58:01 -0000

Hi WG,

Thanks to all who responded to the adoption poll. We have support to adopt this
as a WG item. Please continue to provide your comments as document moves through
the WG process.

Authors, please post a -00 version 'draft-ietf-pce-binding-label-sid-00' with
only the name and date change, and be sure to set the "replaces" at submission.

Have a good weekend!

Thanks!
PCE Chairs


From nobody Fri Sep  6 11:08:14 2019
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 518871209BE; Fri,  6 Sep 2019 11:08:06 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: pce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.100.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: pce@ietf.org
Message-ID: <156779328625.21968.11597268810494570125@ietfa.amsl.com>
Date: Fri, 06 Sep 2019 11:08:06 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/TFdhw0_i6MWuI2Vh_0fXLUhBbrk>
Subject: [Pce] I-D Action: draft-ietf-pce-binding-label-sid-00.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Sep 2019 18:08:07 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Path Computation Element WG of the IETF.

        Title           : Carrying Binding Label/Segment-ID in PCE-based Networks.
        Authors         : Siva Sivabalan
                          Clarence Filsfils
                          Jeff Tantsura
                          Jonathan Hardwick
                          Stefano Previdi
                          Cheng Li
	Filename        : draft-ietf-pce-binding-label-sid-00.txt
	Pages           : 16
	Date            : 2019-09-06

Abstract:
   In order to provide greater scalability, network opacity, and service
   independence, SR utilizes a Binding Segment Identifier (BSID).  It is
   possible to associate a BSID to RSVP-TE signaled Traffic Engineering
   Label Switching Path or binding Segment-ID (SID) to Segment Routed
   (SR) Traffic Engineering path.  Such a binding label/SID can be used
   by an upstream node for steering traffic into the appropriate TE path
   to enforce SR policies.  This document proposes an approach for
   reporting binding label/SID to Path Computation Element (PCE) for
   supporting PCE-based Traffic Engineering policies.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pce-binding-label-sid/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-pce-binding-label-sid-00
https://datatracker.ietf.org/doc/html/draft-ietf-pce-binding-label-sid-00


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Fri Sep  6 14:17:13 2019
Return-Path: <adrian@olddog.co.uk>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E7B4120DE8 for <pce@ietfa.amsl.com>; Fri,  6 Sep 2019 14:17:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.596
X-Spam-Level: 
X-Spam-Status: No, score=-2.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nooUCAwJI6oZ for <pce@ietfa.amsl.com>; Fri,  6 Sep 2019 14:17:08 -0700 (PDT)
Received: from mta6.iomartmail.com (mta6.iomartmail.com [62.128.193.156]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7BEC120DE6 for <pce@ietf.org>; Fri,  6 Sep 2019 14:17:07 -0700 (PDT)
Received: from vs2.iomartmail.com (vs2.iomartmail.com [10.12.10.123]) by mta6.iomartmail.com (8.14.4/8.14.4) with ESMTP id x86LH62u019013; Fri, 6 Sep 2019 22:17:06 +0100
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id C6A95220D7; Fri,  6 Sep 2019 22:17:05 +0100 (BST)
Received: from asmtp3.iomartmail.com (unknown [10.12.10.224]) by vs2.iomartmail.com (Postfix) with ESMTPS id B1131220D6; Fri,  6 Sep 2019 22:17:05 +0100 (BST)
Received: from LAPTOPK7AS653V (216.126.159.143.dyn.plus.net [143.159.126.216]) (authenticated bits=0) by asmtp3.iomartmail.com (8.14.4/8.14.4) with ESMTP id x86LH4sb022089 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 6 Sep 2019 22:17:04 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Hariharan Ananthakrishnan'" <hari@netflix.com>
Cc: <pce@ietf.org>
References: <CAL70W4oEprCSQxEVAL-4DLRBnPQvsim6BdEr5nGaEdyStw=MYg@mail.gmail.com>
In-Reply-To: <CAL70W4oEprCSQxEVAL-4DLRBnPQvsim6BdEr5nGaEdyStw=MYg@mail.gmail.com>
Date: Fri, 6 Sep 2019 22:17:03 +0100
Organization: Old Dog Consulting
Message-ID: <040101d564f8$6e76e3d0$4b64ab70$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0402_01D56500.D03CAB60"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQGNZUSDC4l1+Ck6BHo9tLf7FPGpgaevJjIQ
Content-Language: en-gb
X-Originating-IP: 143.159.126.216
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-24894.003
X-TM-AS-Result: No--18.826-10.0-31-10
X-imss-scan-details: No--18.826-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-24894.003
X-TMASE-Result: 10--18.825900-10.000000
X-TMASE-MatchedRID: gzVbiXtWD9vxIbpQ8BhdbGzBijri5+RVpQH4ogtVQP0Lz9ysPCD6mAFL dQ5v4HNoIUHhOFoozeBkKeQ9nAfTujlJNbG98kTYhL9NX2TqmkAeRZr2cxRELsLRRNKa+dDo+on o1l23mLX3Wuu4o+UjZ/0Cg5RA61r8qSSr/I1wc/pQ+S0N05fR+0upr1fvkyppc2WeU/GRHcDv/7 2zC4hJFUtt4xcKCO29ftblt3CCdbwVlVZBrluia980oP25F8xpcQ43DruBJVxKddiF2Wo8eXI0S qyXZvY+i99Im41M3+vFYZvLkeDp4CxLt17m0r0BMTTrAcDX5/5hS5mf1VdlYbmN/B2gLs6O3c00 lAOLPF4igAsGa3qgmnc1ZaiuhQystDyv3gNOnrciPTMUjkOgksC2kM0wuzzWmCNknSXswf8SkGd mQt+XWY8lwu8j52eI++QVMrHdsxsHot1G7FlH2+QYBHVKqgDUfS0Ip2eEHnyvXSmSdlcYmsnjLT A/UDoASlnU38LCY8vQqQhSw0x2VOJGF26G8SWypfzLa08EuFBTO2MjZ/11rEeVhJizhwS+PzSTa K43NPX1qRMQ/zL+rVGUsNMK829j
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/Z3wLbt6GCzYGDX7Fk8TLo5Ipn0o>
Subject: Re: [Pce] IPR Poll on draft-farrel-pce-stateful-flags-01
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Sep 2019 21:17:10 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0402_01D56500.D03CAB60
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: 7bit

Hi Hari,

 

I am not aware of any IPR applicable to this draft that should be disclosed
in accordance with IETF IPR rules.

 

Thanks,

Adrian

 

From: Hariharan Ananthakrishnan <hari@netflix.com> 
Sent: 06 September 2019 15:41
To: Farrel Adrian <adrian@olddog.co.uk>
Cc: pce@ietf.org
Subject: IPR Poll on draft-farrel-pce-stateful-flags-01

 

Hi Authors,
 
In preparation for Working Group last call on this draft, I'd like all
authors and contributors to confirm on the list that they are in compliance
with IETF IPR rules.
 
Please respond (copying the mailing list) to say one of:
 
I am not aware of any IPR applicable to this draft that should be disclosed
in accordance with IETF IPR rules.
 
I am aware of IPR applicable to this draft, and it has already been
disclosed to the IETF.
 
I am aware of IPR applicable to this draft, but that has not yet been
disclosed to the IETF. I will work to ensure that it will be disclosed in a
timely manner.
 
Thanks,
- Hari

------=_NextPart_000_0402_01D56500.D03CAB60
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 15 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	mso-fareast-language:EN-GB;}
span.gmail-il
	{mso-style-name:gmail-il;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-GB =
link=3D"#0563C1" vlink=3D"#954F72"><div class=3DWordSection1><p =
class=3DMsoNormal><span style=3D'mso-fareast-language:EN-US'>Hi =
Hari,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><pre><sp=
an style=3D'font-family:"Verdana",sans-serif;color:#212529'>I am not =
aware of any <span class=3Dgmail-il>IPR</span> applicable to this draft =
that should be disclosed<o:p></o:p></span></pre><pre><span =
style=3D'font-family:"Verdana",sans-serif;color:#212529'>in accordance =
with IETF <span class=3Dgmail-il>IPR</span> =
rules.<o:p></o:p></span></pre><p class=3DMsoNormal><span =
style=3D'mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'mso-fareast-language:EN-US'>Thanks,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'mso-fareast-language:EN-US'>Adrian<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><b><span lang=3DEN-US>From:</span></b><span =
lang=3DEN-US> Hariharan Ananthakrishnan &lt;hari@netflix.com&gt; =
<br><b>Sent:</b> 06 September 2019 15:41<br><b>To:</b> Farrel Adrian =
&lt;adrian@olddog.co.uk&gt;<br><b>Cc:</b> =
pce@ietf.org<br><b>Subject:</b> IPR Poll on =
draft-farrel-pce-stateful-flags-01<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><pre><span =
style=3D'font-family:"Verdana",sans-serif;color:#212529'>Hi =
Authors,<o:p></o:p></span></pre><pre><span =
style=3D'font-family:"Verdana",sans-serif;color:#212529'><o:p>&nbsp;</o:p=
></span></pre><pre><span =
style=3D'font-family:"Verdana",sans-serif;color:#212529'>In preparation =
for Working Group last call on this draft, I'd like =
all<o:p></o:p></span></pre><pre><span =
style=3D'font-family:"Verdana",sans-serif;color:#212529'>authors and =
contributors to confirm on the list that they are in =
compliance<o:p></o:p></span></pre><pre><span =
style=3D'font-family:"Verdana",sans-serif;color:#212529'>with IETF <span =
class=3Dgmail-il>IPR</span> rules.<o:p></o:p></span></pre><pre><span =
style=3D'font-family:"Verdana",sans-serif;color:#212529'><o:p>&nbsp;</o:p=
></span></pre><pre><span =
style=3D'font-family:"Verdana",sans-serif;color:#212529'>Please respond =
(copying the mailing list) to say one =
of:<o:p></o:p></span></pre><pre><span =
style=3D'font-family:"Verdana",sans-serif;color:#212529'><o:p>&nbsp;</o:p=
></span></pre><pre><span =
style=3D'font-family:"Verdana",sans-serif;color:#212529'>I am not aware =
of any <span class=3Dgmail-il>IPR</span> applicable to this draft that =
should be disclosed<o:p></o:p></span></pre><pre><span =
style=3D'font-family:"Verdana",sans-serif;color:#212529'>in accordance =
with IETF <span class=3Dgmail-il>IPR</span> =
rules.<o:p></o:p></span></pre><pre><span =
style=3D'font-family:"Verdana",sans-serif;color:#212529'><o:p>&nbsp;</o:p=
></span></pre><pre><span =
style=3D'font-family:"Verdana",sans-serif;color:#212529'>I am aware of =
<span class=3Dgmail-il>IPR</span> applicable to this draft, and it has =
already been<o:p></o:p></span></pre><pre><span =
style=3D'font-family:"Verdana",sans-serif;color:#212529'>disclosed to =
the IETF.<o:p></o:p></span></pre><pre><span =
style=3D'font-family:"Verdana",sans-serif;color:#212529'><o:p>&nbsp;</o:p=
></span></pre><pre><span =
style=3D'font-family:"Verdana",sans-serif;color:#212529'>I am aware of =
<span class=3Dgmail-il>IPR</span> applicable to this draft, but that has =
not yet been<o:p></o:p></span></pre><pre><span =
style=3D'font-family:"Verdana",sans-serif;color:#212529'>disclosed to =
the IETF. I will work to ensure that it will be disclosed in =
a<o:p></o:p></span></pre><pre><span =
style=3D'font-family:"Verdana",sans-serif;color:#212529'>timely =
manner.<o:p></o:p></span></pre><pre><span =
style=3D'font-family:"Verdana",sans-serif;color:#212529'><o:p>&nbsp;</o:p=
></span></pre><pre><span =
style=3D'font-family:"Verdana",sans-serif;color:#212529'>Thanks,<o:p></o:=
p></span></pre><pre><span =
style=3D'font-family:"Verdana",sans-serif;color:#212529'>- =
Hari</span><span =
style=3D'color:#212529'><o:p></o:p></span></pre></div></div></div></body>=
</html>
------=_NextPart_000_0402_01D56500.D03CAB60--


From nobody Mon Sep  9 04:05:59 2019
Return-Path: <dhruv.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4ACDD120047; Mon,  9 Sep 2019 04:05:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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, 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 h7AsDAN4Ue6V; Mon,  9 Sep 2019 04:05:56 -0700 (PDT)
Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com [IPv6:2607:f8b0:4864:20::d2b]) (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 557AF120044; Mon,  9 Sep 2019 04:05:56 -0700 (PDT)
Received: by mail-io1-xd2b.google.com with SMTP id k5so2324402iol.5; Mon, 09 Sep 2019 04:05:56 -0700 (PDT)
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=NhM9yKIuOOBc+bT/4jBT95ih0Twsmo2f5afDwFN700I=; b=lE1MTA9lLO8AHdvU6J2xinDTR4TTjUVle3M3wIzvmv4uN12qvrc3QYH7xuoAe7ls85 Aib5Ft1nsnZmtK8LIkTokrw+Z5BSwZ8lPJiGP294AdHLBBBFsWClwFKbxuwRxdtUL4QM caLQQ5kuNy3n4nvXf6e6EVhHgC0QuvC9lNW364lv7OqzU8o7AH/RgZxLzhcTgiyJSIQ5 8I+hlYnrRF8g3YyrDPOUTB9NXxwyCNBeegMSzYdHBbIarmvzMW7KmudE7i9s79F+sAtW 5/mPL3mhKDO4GAFwPGAsNYyi9QTcXXEggTAMOpy+6Kno54bBubjzJAIPM7Nw4z8L0KRx C1JA==
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=NhM9yKIuOOBc+bT/4jBT95ih0Twsmo2f5afDwFN700I=; b=O7zMKfUJVMnpXeazNuT4KV6nQk3X95ax5MCp3TOPkGgdjjMaY7OHEPPMbzQVvy8rDz DvxM5GV7Lq/XvjjS6tnTT8ZSGIaLjo47TA2fKZJYbWNu6sWcNAcuVA63N7uweCShoexu gAUv++gCLWd76fWYutqNpWVm7k3CIC3mvD2WcLPBjzzSQ/1liAjoFOh4HZEZjbb/MvXD ZIzwWAH1fnTDXTJv0I8pzE4UEL/nHmg2qFgSsQQnxmvSOB5LUOpXJ/3UNYfZhU8hjIct l5U8xppaG8iiFcaPzulzXupXbKciHGNW7pUza8txCUboIsVpb7GPZK8TynZGnpysfBx1 XAcg==
X-Gm-Message-State: APjAAAV71p+lpU77xA0zMd8u4Qc+HdDq8WRqO0bO0VwFqhreVllGdfkc sJZWXz4yyyntne3nz6ztevG5ojjFqGndeSARmhELuFCy
X-Google-Smtp-Source: APXvYqzazNN8sXkON8FiPYoQXURTzxf5MXvCwnjpEcpvngIyj6Xb+KhDKwMmsXbf7kHv6WtpFvyhEr0/tNyvPL628t0=
X-Received: by 2002:a6b:b78b:: with SMTP id h133mr8987230iof.276.1568027155233;  Mon, 09 Sep 2019 04:05:55 -0700 (PDT)
MIME-Version: 1.0
References: <CAB75xn6YcL4wXggWTBhfwOp_go32XaHFjaV+oEV-hdE7XjFuyw@mail.gmail.com>
In-Reply-To: <CAB75xn6YcL4wXggWTBhfwOp_go32XaHFjaV+oEV-hdE7XjFuyw@mail.gmail.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Mon, 9 Sep 2019 16:35:18 +0530
Message-ID: <CAB75xn6cFH-zYKkh-SzBRrpoT0j=cpbGa=mNfZCKBpCi5+UPmQ@mail.gmail.com>
To: pce@ietf.org
Cc: pce-chairs <pce-chairs@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/FOiXt_A9Wy1lgKJgTsM9hGNFyM0>
Subject: Re: [Pce] WG LC for draft-farrel-pce-stateful-flags-01
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Sep 2019 11:05:58 -0000

Hi WG,

We have only one response so far. This is a focused small document, with
just 1-2 pages of the main content that updates a problem that was found
in RFC 8231. This might seem trivial but it is important as a WG that we
fix issues in our published RFCs and make it easier for later work and
implementations.

Please read and comment, if you feel the document should not be published,
please state your reason. We urge you to be vocal on the list either way,
you have another week as WG LC closes on 16th Sept.

Thanks!
PCE Chairs

On Fri, Aug 30, 2019 at 11:43 PM Dhruv Dhody <dhruv.ietf@gmail.com> wrote:
>
> Hi WG,
>
> This email starts a 'working group last call' for
> draft-farrel-pce-stateful-flags-01 [1]. This I-D is focused and has an
> uncontroversial fix to RFC 8231, we are moving it directly to WGLC. See [2]
> for context.
>
> Please indicate your support or concern for this draft.
>
> If you are opposed to the progression of the draft, please articulate your
> concern.
>
> If you support, please indicate that you have read the latest version and
> it is ready for publication.
>
> As always, review comments and nits are most welcome.
>
> The WG LC will end on 16th September 2019.
>
> Thanks,
> PCE Chairs
>
> [1] https://datatracker.ietf.org/doc/draft-farrel-pce-stateful-flags/
> [2] https://mailarchive.ietf.org/arch/msg/pce/tTkJKO34xTD0CY48IJCk5FjmiJ4


From nobody Mon Sep  9 09:48:19 2019
Return-Path: <noreply@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 83A5C12007A; Mon,  9 Sep 2019 09:48:09 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?q?Mirja_K=C3=BChlewind_via_Datatracker?= <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-pce-stateful-pce-auto-bandwidth@ietf.org, Adrian Farrel <adrian@olddog.co.uk>, pce-chairs@ietf.org, adrian@olddog.co.uk,  pce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.101.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: =?utf-8?q?Mirja_K=C3=BChlewind?= <ietf@kuehlewind.net>
Message-ID: <156804768952.28211.12510339549643163890.idtracker@ietfa.amsl.com>
Date: Mon, 09 Sep 2019 09:48:09 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/OYbKG107ZjTCL1cqjThzUJDZ__8>
Subject: [Pce] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft-i?= =?utf-8?q?etf-pce-stateful-pce-auto-bandwidth-11=3A_=28with_COMMENT=29?=
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Sep 2019 16:48:10 -0000

Mirja Kühlewind has entered the following ballot position for
draft-ietf-pce-stateful-pce-auto-bandwidth-11: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-pce-auto-bandwidth/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks for quickly addressing the TSV-ART review (and thanks to David for this
very clear and well explained review)! I would have preferred to actually see a
normative requirement as original proposed by David ("sample interval SHOULD
NOT be less than 1 minute") in section 5.2.1. Also I would have expected the
proposed new text to show up somewhere in section 4 (maybe even as a new
subsection).



From nobody Mon Sep  9 10:11:28 2019
Return-Path: <noreply@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EC97120812; Mon,  9 Sep 2019 10:11:26 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: David Black via Datatracker <noreply@ietf.org>
To: <tsv-art@ietf.org>
Cc: pce@ietf.org, ietf@ietf.org, draft-ietf-pce-stateful-pce-auto-bandwidth.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.101.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: David Black <david.black@dell.com>
Message-ID: <156804908638.28121.16243368719278250439@ietfa.amsl.com>
Date: Mon, 09 Sep 2019 10:11:26 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/_7BZvshQ8SpOSbyBtg3pk_RbmnY>
Subject: [Pce] Tsvart telechat review of draft-ietf-pce-stateful-pce-auto-bandwidth-11
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Sep 2019 17:11:27 -0000

Reviewer: David Black
Review result: Ready with Nits

This document has been reviewed as part of the transport area review team's
ongoing effort to review key IETF documents. These comments were written
primarily for the transport area directors, but are copied to the document's
authors and WG to allow them to address any issues raised and also to the IETF
discussion list for information.

When done at the time of IETF Last Call, the authors should consider this
review as part of the last-call comments they receive. Please always CC
tsv-art@ietf.org if you reply to or forward this review.

The -11 version of this draft contains a new paragraph of text in Section 6.6
that warns operators about the timing interaction possibility with transport
protocols raised in the review of the -10 version.  That paragraph also
provides an implicit suggestion on what to do (just use the 5 minute default
time period between samples).

Nit in that new paragraph: "(5 minute)" -> "(5 minutes)"
This nit can be left to the RFC Editor to correct.


From nobody Tue Sep 10 00:52:32 2019
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D80B6120045; Tue, 10 Sep 2019 00:52:23 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: pce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.101.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: pce@ietf.org
Message-ID: <156810194380.27638.13900608157360187972@ietfa.amsl.com>
Date: Tue, 10 Sep 2019 00:52:23 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/vDD9GgvZKCpiLuTiZbk4ux3Ycwc>
Subject: [Pce] I-D Action: draft-ietf-pce-flexible-grid-02.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Sep 2019 07:52:24 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Path Computation Element WG of the IETF.

        Title           : PCEP Extension for Flexible Grid Networks
        Authors         : Young Lee
                          Haomian Zheng
                          Ramon Casellas
                          Ricard Vilalta
                          Daniele Ceccarelli
                          Francesco Lazzeri
	Filename        : draft-ietf-pce-flexible-grid-02.txt
	Pages           : 19
	Date            : 2019-09-10

Abstract:
   This document provides the Path Computation Element Communication
   Protocol (PCEP) extensions for the support of Routing and Spectrum
   Assignment (RSA) in Flexible Grid networks.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pce-flexible-grid/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-pce-flexible-grid-02
https://datatracker.ietf.org/doc/html/draft-ietf-pce-flexible-grid-02

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-pce-flexible-grid-02


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Sep 11 00:41:34 2019
Return-Path: <Jonathan.Hardwick@metaswitch.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59D13120814; Wed, 11 Sep 2019 00:41:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=metaswitch.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 BFDXqZwuRgKm; Wed, 11 Sep 2019 00:41:30 -0700 (PDT)
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (mail-eopbgr740102.outbound.protection.outlook.com [40.107.74.102]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1714D12009C; Wed, 11 Sep 2019 00:41:29 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=HjwNzJzSZXoWJMa99MZ5kq0Kf0ytteS7GInoZw2BP7DKb2H/jFBB1zKXz08/ZTaD5dFuHh5y4I4kO1mPxWP46r1i4MawaAHQ64cEgxhaMYgrdzMv4hZQvyHdUEMsE19v05LkvVyQDkBRTGF1GHTqmIhoji8CEgAY2gug6blt7Sd3ToV4aQEmE3htyAneA5QFBZOnFFE0UYuijKAkQDrFqmdCbSjRh+KxSz7Gmcn0HVzgSG7xx3kg79p0/OYjStuMPyWOBf/rfEsdcLm8Q7+mOEy0zkNQF/xPaP9heR9hfryy7d0NjVrGxQ1RlcHfSNIS2aC6ZUklaBvaK5VitRWfgQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=7IbxDRmaxGLfbVY4cWn7FnhlZBBb2IjDodYty0JRlAY=; b=LPS8qptOaHX4K9kSmjbC0benaU/xUDaR1ZV6hbhu5HYyYKoGcnKbnkFeWTgWdN5fCk9l+IlgaS5SpVzdxPk4DlvGCiOciNf6Hemiv6zZK29uQ6LN8Y1stv0jqDkFHHR/VtRdBGfc6vinkS+J6/kbllCMcvw2U82kxCuK6PEQ4wPDqpF/Wu3UQq6NdAVOup2FHOF91cHoFHJCdLynZ80A837wI6pDvOcKGa92PjX/tvYBEIODUWMnV1L/GHIwBlh3EIuOw55mEQ1xKrACn3pkPHzWu8zavV+Jc9E6qy07fDOjCysuO13ZhFkJ0t1lO4LOZ999m171O0gWubibxnSmqw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=metaswitch.com; dmarc=pass action=none header.from=metaswitch.com; dkim=pass header.d=metaswitch.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=metaswitch.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=7IbxDRmaxGLfbVY4cWn7FnhlZBBb2IjDodYty0JRlAY=; b=XDjHK0wPbHC3w0lpaGU1OKJ70foGCWkFX5pwt4Rbje2UD2Z0b39gSci62YiF7qhFwREXHKCcXGbj0FA+zrvndRLRYQbM+RdUlkZ0wm7+kBXtdA/p7qZyisbv3AcheN0gQ0oVHSrugKUmBu6CG4OISRp5YszxVym9NAqnufRDuIY=
Received: from BL0PR02MB4868.namprd02.prod.outlook.com (20.177.144.87) by BL0PR02MB4339.namprd02.prod.outlook.com (10.167.180.159) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2220.20; Wed, 11 Sep 2019 07:41:27 +0000
Received: from BL0PR02MB4868.namprd02.prod.outlook.com ([fe80::b990:d862:9222:4d1d]) by BL0PR02MB4868.namprd02.prod.outlook.com ([fe80::b990:d862:9222:4d1d%4]) with mapi id 15.20.2241.018; Wed, 11 Sep 2019 07:41:27 +0000
From: Jonathan Hardwick <Jonathan.Hardwick@metaswitch.com>
To: Dhruv Dhody <dhruv.ietf@gmail.com>, "pce@ietf.org" <pce@ietf.org>
CC: pce-chairs <pce-chairs@ietf.org>
Thread-Topic: [Pce] WG LC for draft-farrel-pce-stateful-flags-01
Thread-Index: AQHVZv6Tj6NRquSpTkijBX4HqQpSxacmGlVg
Date: Wed, 11 Sep 2019 07:41:27 +0000
Message-ID: <BL0PR02MB4868EAFE6120EAF3EDFDE8D084B10@BL0PR02MB4868.namprd02.prod.outlook.com>
References: <CAB75xn6YcL4wXggWTBhfwOp_go32XaHFjaV+oEV-hdE7XjFuyw@mail.gmail.com> <CAB75xn6cFH-zYKkh-SzBRrpoT0j=cpbGa=mNfZCKBpCi5+UPmQ@mail.gmail.com>
In-Reply-To: <CAB75xn6cFH-zYKkh-SzBRrpoT0j=cpbGa=mNfZCKBpCi5+UPmQ@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ts-tracking-id: d2c26a65-1f26-43b5-8e42-4bcc6b855bd1.0
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Jonathan.Hardwick@metaswitch.com; 
x-originating-ip: [192.91.191.162]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: d46d21eb-3a99-42d3-9c2b-08d7368b7457
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600166)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:BL0PR02MB4339; 
x-ms-traffictypediagnostic: BL0PR02MB4339:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <BL0PR02MB4339C01A08993FE09C34AF4184B10@BL0PR02MB4339.namprd02.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0157DEB61B
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(346002)(39860400002)(396003)(366004)(376002)(199004)(189003)(13464003)(9686003)(6306002)(55016002)(53936002)(5660300002)(71200400001)(8676002)(71190400001)(25786009)(6436002)(4326008)(52536014)(186003)(64756008)(66946007)(53546011)(6506007)(7696005)(26005)(486006)(102836004)(66446008)(6116002)(3846002)(2906002)(66476007)(76176011)(446003)(66556008)(76116006)(11346002)(476003)(8936002)(14454004)(7736002)(478600001)(966005)(81156014)(81166006)(256004)(14444005)(86362001)(316002)(229853002)(66066001)(6246003)(99286004)(74316002)(305945005)(110136005)(33656002)(2501003); DIR:OUT; SFP:1102; SCL:1; SRVR:BL0PR02MB4339; H:BL0PR02MB4868.namprd02.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: metaswitch.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: zXD8bbjN5hXoqDlloMJIk06EJjuvvTF8VUy9+Jbb/FM3aMXmmUlGYjBL6NqXddkPTKXTqzwRMCY34PdOX7T2rkg+enhkOXww969bnH1RT17jQZuoEIYHFBBSYIznJa3Gak0dd6ZGJ6pIhmDakg15AkrMurrzsDdxoqkHGUuYZKBbc4XNgmzii5DmxpgW7Y+/Te0TVdKHxCOcwrXDdP3UftTg9E8GWZL5iuGXdgSfD5d0421EObo515vo1NlUeWIuHWowy8odBEKYe+LYKrfMfUMV/6Krn90KWiXOnjCVeAPvpEfQ87ncmdS0NgfjrAtf/jsAjB0bIkwp927KjhjY9b/aYIpyzweV9wBkn0AMrocOK1LzgMgKMR7HZs49xT5KjZypRk1MPTXU4CIQI41TPVVdg9SSmdTCKSNrz0715+g=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: metaswitch.com
X-MS-Exchange-CrossTenant-Network-Message-Id: d46d21eb-3a99-42d3-9c2b-08d7368b7457
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Sep 2019 07:41:27.4558 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 9d9e56eb-f613-4ddb-b27b-bfcdf14b2cdb
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: x8xi+Q7IfVJU0Ui+mmb0I7O35mVJ5qRLs3+uY65EtwKiyp0QiLZiWT/c5IYDy1o19oTel3M2wwNsbANsYeeorg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL0PR02MB4339
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/Qw2E88bMJVRgJ9trka3GP6Q0UFw>
Subject: Re: [Pce] WG LC for draft-farrel-pce-stateful-flags-01
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Sep 2019 07:41:33 -0000

I have read the document. It's straightforward and clear. I think it's read=
y to be published.
Cheers
Jon

-----Original Message-----
From: Pce <pce-bounces@ietf.org> On Behalf Of Dhruv Dhody
Sent: 09 September 2019 12:05
To: pce@ietf.org
Cc: pce-chairs <pce-chairs@ietf.org>
Subject: Re: [Pce] WG LC for draft-farrel-pce-stateful-flags-01

NOTE: Message is from an external sender

Hi WG,

We have only one response so far. This is a focused small document, with ju=
st 1-2 pages of the main content that updates a problem that was found in R=
FC 8231. This might seem trivial but it is important as a WG that we fix is=
sues in our published RFCs and make it easier for later work and implementa=
tions.

Please read and comment, if you feel the document should not be published, =
please state your reason. We urge you to be vocal on the list either way, y=
ou have another week as WG LC closes on 16th Sept.

Thanks!
PCE Chairs

On Fri, Aug 30, 2019 at 11:43 PM Dhruv Dhody <dhruv.ietf@gmail.com> wrote:
>
> Hi WG,
>
> This email starts a 'working group last call' for
> draft-farrel-pce-stateful-flags-01 [1]. This I-D is focused and has an=20
> uncontroversial fix to RFC 8231, we are moving it directly to WGLC.=20
> See [2] for context.
>
> Please indicate your support or concern for this draft.
>
> If you are opposed to the progression of the draft, please articulate=20
> your concern.
>
> If you support, please indicate that you have read the latest version=20
> and it is ready for publication.
>
> As always, review comments and nits are most welcome.
>
> The WG LC will end on 16th September 2019.
>
> Thanks,
> PCE Chairs
>
> [1] https://datatracker.ietf.org/doc/draft-farrel-pce-stateful-flags/
> [2]=20
> https://mailarchive.ietf.org/arch/msg/pce/tTkJKO34xTD0CY48IJCk5FjmiJ4

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


From nobody Wed Sep 11 10:28:54 2019
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FC71120B90; Wed, 11 Sep 2019 10:28:40 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: pce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.101.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: pce@ietf.org
Message-ID: <156822292047.13210.9262804420560092507@ietfa.amsl.com>
Date: Wed, 11 Sep 2019 10:28:40 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/NdXoiJhFLmAtayhxb1i6pw1mQ3E>
Subject: [Pce] I-D Action: draft-ietf-pce-stateful-hpce-13.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Sep 2019 17:28:47 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Path Computation Element WG of the IETF.

        Title           : Hierarchical Stateful Path Computation Element (PCE).
        Authors         : Dhruv Dhody
                          Young Lee
                          Daniele Ceccarelli
                          Jongyoon Shin
                          Daniel King
	Filename        : draft-ietf-pce-stateful-hpce-13.txt
	Pages           : 23
	Date            : 2019-09-11

Abstract:
   A Stateful Path Computation Element (PCE) maintains information on
   the current network state, including: computed Label Switched Path
   (LSPs), reserved resources within the network, and pending path
   computation requests. This information may then be considered when
   computing new traffic engineered LSPs, and for associated and
   dependent LSPs, received from Path Computation Clients (PCCs). The
   Path computation response from a PCE is helpful for the PCC to
   gracefully establish the computed LSP.

   The Hierarchical Path Computation Element (H-PCE) architecture,
   provides an architecture to allow the optimum sequence of
   inter-connected domains to be selected, and network policy to be
   applied if applicable, via the use of a hierarchical relationship
   between PCEs.

   Combining the capabilities of Stateful PCE and the Hierarchical PCE
   would be advantageous. This document describes general considerations
   and use cases for the deployment of Stateful, and not Stateless, PCEs
   using the Hierarchical PCE architecture.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-hpce/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-pce-stateful-hpce-13
https://datatracker.ietf.org/doc/html/draft-ietf-pce-stateful-hpce-13

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-pce-stateful-hpce-13


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Sep 11 13:14:21 2019
Return-Path: <db3546@att.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0688120227; Wed, 11 Sep 2019 13:14:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ww0i_-h8nrFY; Wed, 11 Sep 2019 13:14:17 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6370C1201CE; Wed, 11 Sep 2019 13:14:17 -0700 (PDT)
Received: from pps.filterd (m0049297.ppops.net [127.0.0.1]) by m0049297.ppops.net-00191d01. (8.16.0.27/8.16.0.27) with SMTP id x8BK2Y38037839; Wed, 11 Sep 2019 16:14:15 -0400
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0049297.ppops.net-00191d01. with ESMTP id 2uy6q6ss6s-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 11 Sep 2019 16:14:10 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id x8BKDnel025984; Wed, 11 Sep 2019 16:13:49 -0400
Received: from zlp27129.vci.att.com (zlp27129.vci.att.com [135.66.87.42]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id x8BKDlxF025925 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 11 Sep 2019 16:13:47 -0400
Received: from zlp27129.vci.att.com (zlp27129.vci.att.com [127.0.0.1]) by zlp27129.vci.att.com (Service) with ESMTP id 08DCA40392B7; Wed, 11 Sep 2019 20:13:47 +0000 (GMT)
Received: from MISOUT7MSGHUBAC.ITServices.sbc.com (unknown [130.9.129.147]) by zlp27129.vci.att.com (Service) with ESMTPS id D5AAB4039199; Wed, 11 Sep 2019 20:13:46 +0000 (GMT)
Received: from MISOUT7MSGUSRDE.ITServices.sbc.com ([169.254.5.220]) by MISOUT7MSGHUBAC.ITServices.sbc.com ([130.9.129.147]) with mapi id 14.03.0468.000; Wed, 11 Sep 2019 16:13:46 -0400
From: "BRUNGARD, DEBORAH A" <db3546@att.com>
To: "pce@ietf.org" <pce@ietf.org>
CC: pce-chairs <pce-chairs@ietf.org>
Thread-Topic: Adrian stepping down as PCE co-chair
Thread-Index: AdVo28vCYIoHnaEsTjSAQbDA3xY4EA==
Date: Wed, 11 Sep 2019 20:13:46 +0000
Message-ID: <F64C10EAA68C8044B33656FA214632C8A3A1FDCF@MISOUT7MSGUSRDE.ITServices.sbc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.10.219.64]
Content-Type: multipart/alternative; boundary="_000_F64C10EAA68C8044B33656FA214632C8A3A1FDCFMISOUT7MSGUSRDE_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-09-11_08:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=609 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1906280000 definitions=main-1909110180
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/CMdFGg_Ttggr63pDpDjH5uP0h-o>
Subject: [Pce] Adrian stepping down as PCE co-chair
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Sep 2019 20:14:19 -0000

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

Hi,

As we noted earlier, Adrian stepped in to help us with the PCE document que=
ue and help bring Dhruv on as a new chair. He has done a fantastic job and =
Dhruv and Julien are now ready to go forward.

We very much appreciate his support and thank him for all his help!

Deborah


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">As we noted earlier, Adrian stepped in to help us wi=
th the PCE document queue and help bring Dhruv on as a new chair. He has do=
ne a fantastic job and Dhruv and Julien are now ready to go forward.<o:p></=
o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">We very much appreciate his support and thank him fo=
r all his help!<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Deborah<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_F64C10EAA68C8044B33656FA214632C8A3A1FDCFMISOUT7MSGUSRDE_--


From nobody Wed Sep 11 13:56:42 2019
Return-Path: <jefftant.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B536120803; Wed, 11 Sep 2019 13:56:40 -0700 (PDT)
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 OqMsI6F9aYQ6; Wed, 11 Sep 2019 13:56:38 -0700 (PDT)
Received: from mail-pl1-x62e.google.com (mail-pl1-x62e.google.com [IPv6:2607:f8b0:4864:20::62e]) (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 1028B120289; Wed, 11 Sep 2019 13:56:37 -0700 (PDT)
Received: by mail-pl1-x62e.google.com with SMTP id p9so5986111plk.5; Wed, 11 Sep 2019 13:56:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version; bh=8xdtQi5R11sbRbKuKjZPoMemCJsprB6ZxfWvrE3CnMs=; b=Q28eQkv1FT5uIkWiZrl9dzSVNJ+sdDQ4irTmzNc3R1vgW96/3bgbiFJsVI8yFMW33x b0uc/NNRO/BR2S2XMWLySpVxwZu4I1eaFpaSzrm5p61reT5vaAOGmV0hEB1CzjWlfZN9 JSHjxdUXAFNx5nGKW0vz8Pc5bOXPOqWuBEgoP5yoBttye2JkPBz4rGvat+mqg2GDwOp0 g/NUorxH7eD8xQzjhYeF3kCJGHszlzkbk/3Vc6DFdJJGgWheqpcVvbgIT69qMu5LRcjt kgiGR637fozAkmH/XBxShECMUDGvtRKKFwTqr6dsW6tHbWcDpvug7q0kgJxboca75jEI X3ag==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:message-id:in-reply-to :references:subject:mime-version; bh=8xdtQi5R11sbRbKuKjZPoMemCJsprB6ZxfWvrE3CnMs=; b=SPqrJqQxG8/3gbowCvOv9vRBbIQCZr6i9MO6A5Hzf5p+g7/kHymk55Qb2fjRLa+xNU WcZgSOWJkgTbTwkptxLhOeALCJU4HeHcuYmjvrQnT3W0CFXzs6CkI8s72rtLJrp7BUT7 DFoAd3147BC5ySYR6eoeLQzfA4IgsGE2VlgdkD8TLhfoSkaV3aReZ+QAEoWPUWZee6Cw iagKNFm7CAzsgXK7jluRwtFzO9XBbeggi6mdILWRIvrwEi/BtghFSH8anR4HIWWZnmdg wtLxiL3uDI3I1Of6PiJ9f69DrzCKK/rS7B43r6ZU/j1H6oKkTrE92IryIna+LN5ES2Lv ifxQ==
X-Gm-Message-State: APjAAAVNTxVCF8RqD6SyxpThYKn6CiSu3j+Z0HfOBW8qFlQ3J6+Xll5C ZudG4TZcPtRLR9cVRtuCJPb+kLfD
X-Google-Smtp-Source: APXvYqyJo5GXKWsZA5H4ka+Gpm/daatkfaF4VSXRbO1YY0grWMhhn8g1WIaHU4OxCJDeJCRLV8ZDLQ==
X-Received: by 2002:a17:902:850c:: with SMTP id bj12mr39805461plb.68.1568235397053;  Wed, 11 Sep 2019 13:56:37 -0700 (PDT)
Received: from [10.5.5.194] ([50.235.77.202]) by smtp.gmail.com with ESMTPSA id s97sm3571012pjc.4.2019.09.11.13.56.35 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 11 Sep 2019 13:56:36 -0700 (PDT)
Date: Wed, 11 Sep 2019 13:56:25 -0700
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: "=?utf-8?Q?pce=40ietf.org?=" <pce@ietf.org>,  =?utf-8?Q?BRUNGARD=2C_DEBORAH_A?= <db3546@att.com>
Cc: pce-chairs <pce-chairs@ietf.org>
Message-ID: <c393b4fe-b540-4972-a553-64f0beff9e6a@Spark>
In-Reply-To: <F64C10EAA68C8044B33656FA214632C8A3A1FDCF@MISOUT7MSGUSRDE.ITServices.sbc.com>
References: <F64C10EAA68C8044B33656FA214632C8A3A1FDCF@MISOUT7MSGUSRDE.ITServices.sbc.com>
X-Readdle-Message-ID: c393b4fe-b540-4972-a553-64f0beff9e6a@Spark
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="5d795f81_216231b_5a8b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/2lNZm2o27fboZlSI4e4PMcfd76E>
Subject: Re: [Pce] Adrian stepping down as PCE co-chair
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Sep 2019 20:56:40 -0000

--5d795f81_216231b_5a8b
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Thanks Adrian!

Cheers,
Jeff
On Sep 11, 2019, 1:14 PM -0700, BRUNGARD, DEBORAH A <db3546@att.com>, wrote:
> Hi,
>
> As we noted earlier, Adrian stepped in to help us with the PCE document queue and help bring Dhruv on as a new chair. He has done a fantastic job and Dhruv and Julien are now ready to go forward.
>
> We very much appreciate his support and thank him for all his help!
>
> Deborah
>
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce

--5d795f81_216231b_5a8b
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<html xmlns=3D=22http://www.w3.org/1999/xhtml=22>
<head>
<title></title>
</head>
<body>
<div name=3D=22messageBodySection=22>
<div dir=3D=22auto=22>Thanks Adrian=21</div>
</div>
<div name=3D=22messageSignatureSection=22><br />
<div class=3D=22match=46ont=22>Cheers,
<div>Jeff</div>
</div>
</div>
<div name=3D=22messageReplySection=22>On Sep 11, 2019, 1:14 PM -0700, BRU=
NGARD, DEBORAH A &lt;db3546=40att.com&gt;, wrote:<br />
<blockquote type=3D=22cite=22 class=3D=22spark=5Fquote=22 style=3D=22marg=
in: 5px 5px; padding-left: 10px; border-left: thin solid =231abc9c;=22>
<div class=3D=22WordSection1=22>
<p class=3D=22MsoNormal=22>Hi,</p>
<p class=3D=22MsoNormal=22>&=23160;</p>
<p class=3D=22MsoNormal=22>As we noted earlier, Adrian stepped in to help=
 us with the PCE document queue and help bring Dhruv on as a new chair. H=
e has done a fantastic job and Dhruv and Julien are now ready to go forwa=
rd.</p>
<p class=3D=22MsoNormal=22>&=23160;</p>
<p class=3D=22MsoNormal=22>We very much appreciate his support and thank =
him for all his help=21</p>
<p class=3D=22MsoNormal=22>&=23160;</p>
<p class=3D=22MsoNormal=22>Deborah</p>
<p class=3D=22MsoNormal=22>&=23160;</p>
</div>
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F<br />
Pce mailing list<br />
Pce=40ietf.org<br />
https://www.ietf.org/mailman/listinfo/pce<br /></blockquote>
</div>
</body>
</html>

--5d795f81_216231b_5a8b--


From nobody Wed Sep 11 16:54:04 2019
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 45E5B12001A; Wed, 11 Sep 2019 16:53:55 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: pce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.101.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: pce@ietf.org
Message-ID: <156824603520.13418.11886889569473957883@ietfa.amsl.com>
Date: Wed, 11 Sep 2019 16:53:55 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/Y65x8hkfKuRBkfOCB8aq1I-Iq6Y>
Subject: [Pce] I-D Action: draft-ietf-pce-association-bidir-04.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Sep 2019 23:53:56 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Path Computation Element WG of the IETF.

        Title           : PCEP Extensions for Associated Bidirectional Label Switched Paths (LSPs)
        Authors         : Rakesh Gandhi
                          Colby Barth
                          Bin Wen
	Filename        : draft-ietf-pce-association-bidir-04.txt
	Pages           : 19
	Date            : 2019-09-11

Abstract:
   The Path Computation Element Communication Protocol (PCEP) provides
   mechanisms for Path Computation Elements (PCEs) to perform path
   computations in response to Path Computation Clients (PCCs) requests.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pce-association-bidir/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-pce-association-bidir-04
https://datatracker.ietf.org/doc/html/draft-ietf-pce-association-bidir-04

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-pce-association-bidir-04


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Sep 11 18:42:39 2019
Return-Path: <chengli13@huawei.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52AC7120C94; Wed, 11 Sep 2019 18:42:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yFwySkATT3zI; Wed, 11 Sep 2019 18:42:28 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91E50120858; Wed, 11 Sep 2019 18:42:28 -0700 (PDT)
Received: from LHREML714-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 50510DA26A61DF160F0C; Thu, 12 Sep 2019 02:42:26 +0100 (IST)
Received: from lhreml702-chm.china.huawei.com (10.201.108.51) by LHREML714-CAH.china.huawei.com (10.201.108.37) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 12 Sep 2019 02:42:26 +0100
Received: from lhreml702-chm.china.huawei.com (10.201.108.51) by lhreml702-chm.china.huawei.com (10.201.108.51) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Thu, 12 Sep 2019 02:42:25 +0100
Received: from DGGEML405-HUB.china.huawei.com (10.3.17.49) by lhreml702-chm.china.huawei.com (10.201.108.51) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1713.5 via Frontend Transport; Thu, 12 Sep 2019 02:42:25 +0100
Received: from DGGEML529-MBX.china.huawei.com ([169.254.6.58]) by dggeml405-hub.china.huawei.com ([10.3.17.49]) with mapi id 14.03.0439.000; Thu, 12 Sep 2019 09:42:18 +0800
From: "Chengli (Cheng Li)" <chengli13@huawei.com>
To: "BRUNGARD, DEBORAH A" <db3546@att.com>, "pce@ietf.org" <pce@ietf.org>
CC: pce-chairs <pce-chairs@ietf.org>
Thread-Topic: Adrian stepping down as PCE co-chair
Thread-Index: AdVo28vCYIoHnaEsTjSAQbDA3xY4EAALyhZA
Date: Thu, 12 Sep 2019 01:42:18 +0000
Message-ID: <C7C2E1C43D652C4E9E49FE7517C236CB026D72EE@dggeml529-mbx.china.huawei.com>
References: <F64C10EAA68C8044B33656FA214632C8A3A1FDCF@MISOUT7MSGUSRDE.ITServices.sbc.com>
In-Reply-To: <F64C10EAA68C8044B33656FA214632C8A3A1FDCF@MISOUT7MSGUSRDE.ITServices.sbc.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.130.185.75]
Content-Type: multipart/alternative; boundary="_000_C7C2E1C43D652C4E9E49FE7517C236CB026D72EEdggeml529mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/8hZNDQrATmRI6YPtKMMdl6ALc9U>
Subject: Re: [Pce] Adrian stepping down as PCE co-chair
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Sep 2019 01:42:37 -0000

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

Many thanks to Adrian!

Best,
Cheng


From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of BRUNGARD, DEBORAH A
Sent: Thursday, September 12, 2019 4:14 AM
To: pce@ietf.org
Cc: pce-chairs <pce-chairs@ietf.org>
Subject: [Pce] Adrian stepping down as PCE co-chair

Hi,

As we noted earlier, Adrian stepped in to help us with the PCE document que=
ue and help bring Dhruv on as a new chair. He has done a fantastic job and =
Dhruv and Julien are now ready to go forward.

We very much appreciate his support and thank him for all his help!

Deborah


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Many thanks to Adrian!=
 <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Best,<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Cheng<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b>From:</b> Pce [mailto:pce-bounces@ietf.org] <b>On=
 Behalf Of
</b>BRUNGARD, DEBORAH A<br>
<b>Sent:</b> Thursday, September 12, 2019 4:14 AM<br>
<b>To:</b> pce@ietf.org<br>
<b>Cc:</b> pce-chairs &lt;pce-chairs@ietf.org&gt;<br>
<b>Subject:</b> [Pce] Adrian stepping down as PCE co-chair<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">As we noted earlier, Adrian stepped in to help us wi=
th the PCE document queue and help bring Dhruv on as a new chair. He has do=
ne a fantastic job and Dhruv and Julien are now ready to go forward.<o:p></=
o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">We very much appreciate his support and thank him fo=
r all his help!<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Deborah<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_C7C2E1C43D652C4E9E49FE7517C236CB026D72EEdggeml529mbxchi_--


From nobody Wed Sep 11 19:53:30 2019
Return-Path: <zhenghaomian@huawei.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9C1E12025D; Wed, 11 Sep 2019 19:53:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gWV_OHnfLp3w; Wed, 11 Sep 2019 19:53:26 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A97B1200E0; Wed, 11 Sep 2019 19:53:26 -0700 (PDT)
Received: from LHREML713-CAH.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 47631E6C796018BD1C37; Thu, 12 Sep 2019 03:53:24 +0100 (IST)
Received: from DGGEML421-HUB.china.huawei.com (10.1.199.38) by LHREML713-CAH.china.huawei.com (10.201.108.36) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 12 Sep 2019 03:53:23 +0100
Received: from DGGEML511-MBX.china.huawei.com ([169.254.1.20]) by dggeml421-hub.china.huawei.com ([10.1.199.38]) with mapi id 14.03.0439.000; Thu, 12 Sep 2019 10:53:16 +0800
From: Zhenghaomian <zhenghaomian@huawei.com>
To: "BRUNGARD, DEBORAH A" <db3546@att.com>, "pce@ietf.org" <pce@ietf.org>
CC: pce-chairs <pce-chairs@ietf.org>
Thread-Topic: Adrian stepping down as PCE co-chair
Thread-Index: AdVo28vCYIoHnaEsTjSAQbDA3xY4EAAOL+gg
Date: Thu, 12 Sep 2019 02:53:17 +0000
Message-ID: <E0C26CAA2504C84093A49B2CAC3261A43B86C89C@dggeml511-mbx.china.huawei.com>
References: <F64C10EAA68C8044B33656FA214632C8A3A1FDCF@MISOUT7MSGUSRDE.ITServices.sbc.com>
In-Reply-To: <F64C10EAA68C8044B33656FA214632C8A3A1FDCF@MISOUT7MSGUSRDE.ITServices.sbc.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.24.178.201]
Content-Type: multipart/alternative; boundary="_000_E0C26CAA2504C84093A49B2CAC3261A43B86C89Cdggeml511mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/lVKpm87l6bVk6IsrBYKU-xdeYTw>
Subject: [Pce] =?gb2312?b?tPC4tDogQWRyaWFuIHN0ZXBwaW5nIGRvd24gYXMgUENF?= =?gb2312?b?IGNvLWNoYWly?=
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Sep 2019 02:53:29 -0000

--_000_E0C26CAA2504C84093A49B2CAC3261A43B86C89Cdggeml511mbxchi_
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64

QmlnIGFwcGxhdXNlIEFkcmlhbn4NCg0KVGhhbmsgeW91Lg0KDQpCZXN0IHdpc2hlcywNCkhhb21p
YW4NCg0Kt6K8/sjLOiBQY2UgW21haWx0bzpwY2UtYm91bmNlc0BpZXRmLm9yZ10gtPqx7SBCUlVO
R0FSRCwgREVCT1JBSCBBDQq3osvNyrG85DogMjAxOcTqOdTCMTLI1SA0OjE0DQrK1bz+yMs6IHBj
ZUBpZXRmLm9yZw0Ks63LzTogcGNlLWNoYWlycyA8cGNlLWNoYWlyc0BpZXRmLm9yZz4NCtb3zOI6
IFtQY2VdIEFkcmlhbiBzdGVwcGluZyBkb3duIGFzIFBDRSBjby1jaGFpcg0KDQpIaSwNCg0KQXMg
d2Ugbm90ZWQgZWFybGllciwgQWRyaWFuIHN0ZXBwZWQgaW4gdG8gaGVscCB1cyB3aXRoIHRoZSBQ
Q0UgZG9jdW1lbnQgcXVldWUgYW5kIGhlbHAgYnJpbmcgRGhydXYgb24gYXMgYSBuZXcgY2hhaXIu
IEhlIGhhcyBkb25lIGEgZmFudGFzdGljIGpvYiBhbmQgRGhydXYgYW5kIEp1bGllbiBhcmUgbm93
IHJlYWR5IHRvIGdvIGZvcndhcmQuDQoNCldlIHZlcnkgbXVjaCBhcHByZWNpYXRlIGhpcyBzdXBw
b3J0IGFuZCB0aGFuayBoaW0gZm9yIGFsbCBoaXMgaGVscCENCg0KRGVib3JhaA0KDQo=

--_000_E0C26CAA2504C84093A49B2CAC3261A43B86C89Cdggeml511mbxchi_
Content-Type: text/html; charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dgb2312">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:=CB=CE=CC=E5;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:=CE=A2=C8=ED=D1=C5=BA=DA;
	panose-1:2 11 5 3 2 2 4 2 2 4;}
@font-face
	{font-family:"\@=CE=A2=C8=ED=D1=C5=BA=DA";
	panose-1:2 11 5 3 2 2 4 2 2 4;}
@font-face
	{font-family:"\@=CB=CE=CC=E5";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"ZH-CN" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D">Big applause Adrian~
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D">Thank you.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"text-align:justify;text-justify:inter-ideog=
raph"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color:#1F497D">Best wi=
shes,<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-align:justify;text-justify:inter-ideog=
raph"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color:#1F497D">Haomian=
<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-family:&quot;=CE=A2=C8=ED=D1=
=C5=BA=DA&quot;,sans-serif">=B7=A2=BC=FE=C8=CB<span lang=3D"EN-US">:</span>=
</span></b><span lang=3D"EN-US" style=3D"font-family:&quot;=CE=A2=C8=ED=D1=
=C5=BA=DA&quot;,sans-serif"> Pce [mailto:pce-bounces@ietf.org]
</span><b><span style=3D"font-family:&quot;=CE=A2=C8=ED=D1=C5=BA=DA&quot;,s=
ans-serif">=B4=FA=B1=ED </span></b><span lang=3D"EN-US" style=3D"font-famil=
y:&quot;=CE=A2=C8=ED=D1=C5=BA=DA&quot;,sans-serif">BRUNGARD, DEBORAH A<br>
</span><b><span style=3D"font-family:&quot;=CE=A2=C8=ED=D1=C5=BA=DA&quot;,s=
ans-serif">=B7=A2=CB=CD=CA=B1=BC=E4<span lang=3D"EN-US">:</span></span></b>=
<span lang=3D"EN-US" style=3D"font-family:&quot;=CE=A2=C8=ED=D1=C5=BA=DA&qu=
ot;,sans-serif"> 2019</span><span style=3D"font-family:&quot;=CE=A2=C8=ED=
=D1=C5=BA=DA&quot;,sans-serif">=C4=EA<span lang=3D"EN-US">9</span>=D4=C2<sp=
an lang=3D"EN-US">12</span>=C8=D5<span lang=3D"EN-US">
 4:14<br>
</span><b>=CA=D5=BC=FE=C8=CB<span lang=3D"EN-US">:</span></b><span lang=3D"=
EN-US"> pce@ietf.org<br>
</span><b>=B3=AD=CB=CD<span lang=3D"EN-US">:</span></b><span lang=3D"EN-US"=
> pce-chairs &lt;pce-chairs@ietf.org&gt;<br>
</span><b>=D6=F7=CC=E2<span lang=3D"EN-US">:</span></b><span lang=3D"EN-US"=
> [Pce] Adrian stepping down as PCE co-chair<o:p></o:p></span></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hi,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">As we noted earlier, Adrian ste=
pped in to help us with the PCE document queue and help bring Dhruv on as a=
 new chair. He has done a fantastic job and Dhruv and Julien are now ready =
to go forward.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">We very much appreciate his sup=
port and thank him for all his help!<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Deborah<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--_000_E0C26CAA2504C84093A49B2CAC3261A43B86C89Cdggeml511mbxchi_--


From nobody Wed Sep 11 23:40:45 2019
Return-Path: <xiong.quan@zte.com.cn>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30DCC1200C3; Wed, 11 Sep 2019 23:40:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level: 
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WjKrLPrM6Sbu; Wed, 11 Sep 2019 23:40:41 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.217.80.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5FC4120020; Wed, 11 Sep 2019 23:40:40 -0700 (PDT)
Received: from mxct.zte.com.cn (unknown [192.168.164.217]) by Forcepoint Email with ESMTPS id 36F1EAACDD194EC781EE; Thu, 12 Sep 2019 14:40:39 +0800 (CST)
Received: from mse-fl2.zte.com.cn (unknown [10.30.14.239]) by Forcepoint Email with ESMTPS id 2CBF074CEE2B1ADF6439; Thu, 12 Sep 2019 14:40:39 +0800 (CST)
Received: from njxapp05.zte.com.cn ([10.41.132.204]) by mse-fl2.zte.com.cn with SMTP id x8C6eOcu043511; Thu, 12 Sep 2019 14:40:24 +0800 (GMT-8) (envelope-from xiong.quan@zte.com.cn)
Received: from mapi (njxapp05[null]) by mapi (Zmail) with MAPI id mid201; Thu, 12 Sep 2019 14:40:23 +0800 (CST)
Date: Thu, 12 Sep 2019 14:40:23 +0800 (CST)
X-Zmail-TransId: 2afd5d79e857ac8ba351
X-Mailer: Zmail v1.0
Message-ID: <201909121440233240278@zte.com.cn>
Mime-Version: 1.0
From: <xiong.quan@zte.com.cn>
To: <pce@ietf.org>, <db3546@att.com>
Cc: <pce-chairs@ietf.org>
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn x8C6eOcu043511
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/QwPXKBOHfiGG8ovQmumwaPWxeE0>
Subject: Re: [Pce] =?utf-8?q?Adrian_stepping_down_as_PCE_co-chair?=
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Sep 2019 06:40:43 -0000

--=====_001_next=====
Content-Type: multipart/related;
	boundary="=====_002_next====="


--=====_002_next=====
Content-Type: multipart/alternative;
	boundary="=====_003_next====="


--=====_003_next=====
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: base64

VGhhbmtzIGZvciB0aGUgaGFyZCB3b3JrIHRvIEFkcmlhbiEgSXQgaXMgdmVyeSBhcHByZWNpYXRl
ZCENCg0KDQoNCg0KDQoNCg0KQmVzdCB3aXNoZXMsDQoNClF1YW4NCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoiQlJVTkdBUkQsIERFQk9SQUggQSIgPGRiMzU0NkBhdHQuY29tPiBXZWQsIDExIFNlcHRl
bWJlciAyMDE5IDIwOjE0IFVUQ1Nob3cgaGVhZGVyDQoNCg0KSGksCgpBcyB3ZSBub3RlZCBlYXJs
aWVyLCBBZHJpYW4gc3RlcHBlZCBpbiB0byBoZWxwIHVzIHdpdGggdGhlIFBDRSBkb2N1bWVudCBx
dWV1ZSBhbmQgaGVscCBicmluZyBEaHJ1diBvbiBhcyBhIG5ldyBjaGFpci4gSGUgaGFzIGRvbmUg
YSBmYW50YXN0aWMgam9iIGFuZCBEaHJ1diBhbmQgSnVsaWVuIGFyZSBub3cgcmVhZHkgdG8gZ28g
Zm9yd2FyZC4KCldlIHZlcnkgbXVjaCBhcHByZWNpYXRlIGhpcyBzdXBwb3J0IGFuZCB0aGFuayBo
aW0gZm9yIGFsbCBoaXMgaGVscCEKCkRlYm9yYWg=


--=====_003_next=====
Content-Type: text/html ;
	charset="UTF-8"
Content-Transfer-Encoding: base64

PGRpdiBjbGFzcz0iemNvbnRlbnRSb3ciPjxwPjxicj48L3A+PHA+VGhhbmtzIGZvciB0aGUgaGFy
ZCB3b3JrJm5ic3A7dG8gQWRyaWFuISBJdCBpcyB2ZXJ5Jm5ic3A7YXBwcmVjaWF0ZWQhPC9wPjxw
Pjxicj48L3A+PHA+PGJyPjwvcD48cD5CZXN0IHdpc2hlcyw8L3A+PHA+UXVhbjwvcD48cD48YnI+
PC9wPjxwPjxicj48L3A+PHA+PGJyPjwvcD48cCBpZD0ibXNnLWluZm8iIGNsYXNzPSJtc2ctaGVh
ZGVyIiBzdHlsZT0iYm94LXNpemluZzogYm9yZGVyLWJveDsgbWFyZ2luLXRvcDogMHB4OyBtYXJn
aW4tYm90dG9tOiAyMHB4OyBjb2xvcjogcmdiKDEyOCwgMTI4LCAxMjgpOyBmb250LWZhbWlseTog
LWFwcGxlLXN5c3RlbSwgQmxpbmtNYWNTeXN0ZW1Gb250LCAnU2Vnb2UgVUknLCBSb2JvdG8sICdI
ZWx2ZXRpY2EgTmV1ZScsIEFyaWFsLCBzYW5zLXNlcmlmLCAnQXBwbGUgQ29sb3IgRW1vamknLCAn
U2Vnb2UgVUkgRW1vamknLCAnU2Vnb2UgVUkgU3ltYm9sJywgJ05vdG8gQ29sb3IgRW1vamknOyBm
b250LXZhcmlhbnQtbGlnYXR1cmVzOiBub3JtYWw7IG9ycGhhbnM6IDI7IHdoaXRlLXNwYWNlOiBu
b3JtYWw7IHdpZG93czogMjsgYmFja2dyb3VuZC1jb2xvcjogcmdiKDI1NSwgMjU1LCAyNTUpOyI+
PHNwYW4gaWQ9Im1zZy1mcm9tIiBjbGFzcz0icGlwZSIgc3R5bGU9ImJveC1zaXppbmc6IGJvcmRl
ci1ib3g7Ij4iQlJVTkdBUkQsIERFQk9SQUggQSIgJmx0O2RiMzU0NkBhdHQuY29tJmd0Ozwvc3Bh
bj4mbmJzcDs8c3BhbiBpZD0ibXNnLWRhdGUiIGNsYXNzPSJwaXBlIiBzdHlsZT0iYm94LXNpemlu
ZzogYm9yZGVyLWJveDsiPldlZCwgMTEgU2VwdGVtYmVyIDIwMTkgMjA6MTQgVVRDPC9zcGFuPjxh
IGlkPSJ0b2dnbGUtbXNnLWhlYWRlciIgY2xhc3M9InRvZ2dsZSIgaHJlZj0iaHR0cHM6Ly9tYWls
YXJjaGl2ZS5pZXRmLm9yZy9hcmNoL2Jyb3dzZS9wY2UvP2didD0xJmFtcDtpbmRleD1sVktwbTg3
bDZiVms2SXNyQllLVS14ZGVZVHcjIiBzdHlsZT0iYm94LXNpemluZzogYm9yZGVyLWJveDsgY29s
b3I6IHJnYig1MSwgMTIyLCAxODMpOyB0ZXh0LWRlY29yYXRpb246IG5vbmU7IGJhY2tncm91bmQt
Y29sb3I6IHRyYW5zcGFyZW50OyI+U2hvdyBoZWFkZXI8L2E+PC9wPjxkaXYgY2xhc3M9Im1zZy1w
YXlsb2FkIiBzdHlsZT0iYm94LXNpemluZzogYm9yZGVyLWJveDsgY29sb3I6IHJnYigzMywgMzcs
IDQxKTsgZm9udC1mYW1pbHk6IC1hcHBsZS1zeXN0ZW0sIEJsaW5rTWFjU3lzdGVtRm9udCwgJ1Nl
Z29lIFVJJywgUm9ib3RvLCAnSGVsdmV0aWNhIE5ldWUnLCBBcmlhbCwgc2Fucy1zZXJpZiwgJ0Fw
cGxlIENvbG9yIEVtb2ppJywgJ1NlZ29lIFVJIEVtb2ppJywgJ1NlZ29lIFVJIFN5bWJvbCcsICdO
b3RvIENvbG9yIEVtb2ppJzsgZm9udC12YXJpYW50LWxpZ2F0dXJlczogbm9ybWFsOyBvcnBoYW5z
OiAyOyB3aGl0ZS1zcGFjZTogbm9ybWFsOyB3aWRvd3M6IDI7IGJhY2tncm91bmQtY29sb3I6IHJn
YigyNTUsIDI1NSwgMjU1KTsiPjxwcmUgY2xhc3M9IndvcmR3cmFwIiBzdHlsZT0iYm94LXNpemlu
ZzogYm9yZGVyLWJveDsgZm9udC1mYW1pbHk6IFNGTW9uby1SZWd1bGFyLCBNZW5sbywgTW9uYWNv
LCBDb25zb2xhcywgJ0xpYmVyYXRpb24gTW9ubycsICdDb3VyaWVyIE5ldycsIG1vbm9zcGFjZTsg
Zm9udC1zaXplOiAxMi4yNXB4OyBtYXJnaW4tdG9wOiAwcHg7IG1hcmdpbi1ib3R0b206IDFyZW07
IG92ZXJmbG93OiBhdXRvOyB3aGl0ZS1zcGFjZTogcHJlLXdyYXA7IG92ZXJmbG93LXdyYXA6IG5v
cm1hbDsgd29yZC1icmVhazogbm9ybWFsOyBwYWRkaW5nOiAwcHg7Ij5IaSwKCkFzIHdlIG5vdGVk
IGVhcmxpZXIsIEFkcmlhbiBzdGVwcGVkIGluIHRvIGhlbHAgdXMgd2l0aCB0aGUgUENFIGRvY3Vt
ZW50IHF1ZXVlIGFuZCBoZWxwIGJyaW5nIERocnV2IG9uIGFzIGEgbmV3IGNoYWlyLiBIZSBoYXMg
ZG9uZSBhIGZhbnRhc3RpYyBqb2IgYW5kIERocnV2IGFuZCBKdWxpZW4gYXJlIG5vdyByZWFkeSB0
byBnbyBmb3J3YXJkLgoKV2UgdmVyeSBtdWNoIGFwcHJlY2lhdGUgaGlzIHN1cHBvcnQgYW5kIHRo
YW5rIGhpbSBmb3IgYWxsIGhpcyBoZWxwIQoKRGVib3JhaDwvcHJlPjwvZGl2PjxwPjxicj48L3A+
PC9kaXY+


--=====_003_next=====--

--=====_002_next=====--

--=====_001_next=====--


From nobody Thu Sep 12 00:47:07 2019
Return-Path: <jie.dong@huawei.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A13AF120C6F; Thu, 12 Sep 2019 00:46:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HHsxk3LJ8aDI; Thu, 12 Sep 2019 00:46:53 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6CDD91208A1; Thu, 12 Sep 2019 00:46:53 -0700 (PDT)
Received: from lhreml702-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id E83948AC788C128B4A5D; Thu, 12 Sep 2019 08:46:50 +0100 (IST)
Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by lhreml702-cah.china.huawei.com (10.201.108.43) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 12 Sep 2019 08:46:50 +0100
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml414-hub.china.huawei.com ([10.98.56.75]) with mapi id 14.03.0439.000; Thu, 12 Sep 2019 15:46:45 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: "BRUNGARD, DEBORAH A" <db3546@att.com>, "pce@ietf.org" <pce@ietf.org>
CC: pce-chairs <pce-chairs@ietf.org>
Thread-Topic: Adrian stepping down as PCE co-chair
Thread-Index: AdVo28vCYIoHnaEsTjSAQbDA3xY4EAAYllIg
Date: Thu, 12 Sep 2019 07:46:45 +0000
Message-ID: <76CD132C3ADEF848BD84D028D243C927CD155EFB@NKGEML515-MBX.china.huawei.com>
References: <F64C10EAA68C8044B33656FA214632C8A3A1FDCF@MISOUT7MSGUSRDE.ITServices.sbc.com>
In-Reply-To: <F64C10EAA68C8044B33656FA214632C8A3A1FDCF@MISOUT7MSGUSRDE.ITServices.sbc.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.130.151.75]
Content-Type: multipart/alternative; boundary="_000_76CD132C3ADEF848BD84D028D243C927CD155EFBNKGEML515MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/oq_s8WzC2vFOKic5q57VHm2asoE>
Subject: Re: [Pce] Adrian stepping down as PCE co-chair
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Sep 2019 07:47:02 -0000

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

Many thanks, Adrian!

-Jie

From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of BRUNGARD, DEBORAH A
Sent: Thursday, September 12, 2019 4:14 AM
To: pce@ietf.org
Cc: pce-chairs <pce-chairs@ietf.org>
Subject: [Pce] Adrian stepping down as PCE co-chair

Hi,

As we noted earlier, Adrian stepped in to help us with the PCE document que=
ue and help bring Dhruv on as a new chair. He has done a fantastic job and =
Dhruv and Julien are now ready to go forward.

We very much appreciate his support and thank him for all his help!

Deborah


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"ZH-CN" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D">Many thanks, Adrian!<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D">-Jie<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US">From:</span></b><span lang=
=3D"EN-US"> Pce [mailto:pce-bounces@ietf.org]
<b>On Behalf Of </b>BRUNGARD, DEBORAH A<br>
<b>Sent:</b> Thursday, September 12, 2019 4:14 AM<br>
<b>To:</b> pce@ietf.org<br>
<b>Cc:</b> pce-chairs &lt;pce-chairs@ietf.org&gt;<br>
<b>Subject:</b> [Pce] Adrian stepping down as PCE co-chair<o:p></o:p></span=
></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hi,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">As we noted earlier, Adrian ste=
pped in to help us with the PCE document queue and help bring Dhruv on as a=
 new chair. He has done a fantastic job and Dhruv and Julien are now ready =
to go forward.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">We very much appreciate his sup=
port and thank him for all his help!<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Deborah<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
</div>
</body>
</html>

--_000_76CD132C3ADEF848BD84D028D243C927CD155EFBNKGEML515MBXchi_--


From nobody Thu Sep 12 01:00:21 2019
Return-Path: <khasanov.boris@huawei.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F412812083E; Thu, 12 Sep 2019 01:00:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CcKOj1CeLrQ8; Thu, 12 Sep 2019 01:00:17 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27AA312010C; Thu, 12 Sep 2019 01:00:17 -0700 (PDT)
Received: from lhreml707-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 77CBB2E703E53DC5C377; Thu, 12 Sep 2019 09:00:15 +0100 (IST)
Received: from LHREML505-MBS.china.huawei.com ([169.254.1.193]) by lhreml707-cah.china.huawei.com ([10.201.108.48]) with mapi id 14.03.0415.000;  Thu, 12 Sep 2019 09:00:11 +0100
From: Khasanov Boris <khasanov.boris@huawei.com>
To: "BRUNGARD, DEBORAH A" <db3546@att.com>, "pce@ietf.org" <pce@ietf.org>
CC: pce-chairs <pce-chairs@ietf.org>
Thread-Topic: Adrian stepping down as PCE co-chair
Thread-Index: AdVo28vCYIoHnaEsTjSAQbDA3xY4EAAY+33w
Date: Thu, 12 Sep 2019 08:00:10 +0000
Message-ID: <C7794D4A32C7D046B93DBCF0FA202C182E8397E3@lhreml505-mbs.china.huawei.com>
References: <F64C10EAA68C8044B33656FA214632C8A3A1FDCF@MISOUT7MSGUSRDE.ITServices.sbc.com>
In-Reply-To: <F64C10EAA68C8044B33656FA214632C8A3A1FDCF@MISOUT7MSGUSRDE.ITServices.sbc.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.198.105.92]
Content-Type: multipart/alternative; boundary="_000_C7794D4A32C7D046B93DBCF0FA202C182E8397E3lhreml505mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/regO1UqV5QXWCdn0bd7XotkJs6o>
Subject: Re: [Pce] Adrian stepping down as PCE co-chair
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Sep 2019 08:00:19 -0000

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

Thanks a lot Adrian for all your great work and efforts!

SY,
Boris

From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of BRUNGARD, DEBORAH A
Sent: Wednesday, September 11, 2019 11:14 PM
To: pce@ietf.org
Cc: pce-chairs <pce-chairs@ietf.org>
Subject: [Pce] Adrian stepping down as PCE co-chair

Hi,

As we noted earlier, Adrian stepped in to help us with the PCE document que=
ue and help bring Dhruv on as a new chair. He has done a fantastic job and =
Dhruv and Julien are now ready to go forward.

We very much appreciate his support and thank him for all his help!

Deborah


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks a lot Adrian fo=
r all your great work and efforts!<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">SY,<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Boris<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Pce [mailto:pce-bounces@ietf.org] <b>On=
 Behalf Of
</b>BRUNGARD, DEBORAH A<br>
<b>Sent:</b> Wednesday, September 11, 2019 11:14 PM<br>
<b>To:</b> pce@ietf.org<br>
<b>Cc:</b> pce-chairs &lt;pce-chairs@ietf.org&gt;<br>
<b>Subject:</b> [Pce] Adrian stepping down as PCE co-chair<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">As we noted earlier, Adrian stepped in to help us wi=
th the PCE document queue and help bring Dhruv on as a new chair. He has do=
ne a fantastic job and Dhruv and Julien are now ready to go forward.<o:p></=
o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">We very much appreciate his support and thank him fo=
r all his help!<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Deborah<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_C7794D4A32C7D046B93DBCF0FA202C182E8397E3lhreml505mbschi_--


From nobody Thu Sep 12 01:10:52 2019
Return-Path: <xiechf@chinatelecom.cn>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE3AB1200B9; Thu, 12 Sep 2019 01:10:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kdwslN4r86E6; Thu, 12 Sep 2019 01:10:48 -0700 (PDT)
Received: from chinatelecom.cn (prt-mail.chinatelecom.cn [42.123.76.228]) by ietfa.amsl.com (Postfix) with ESMTP id 4F0DE12089F; Thu, 12 Sep 2019 01:10:48 -0700 (PDT)
HMM_SOURCE_IP: 172.18.0.92:59140.1108012457
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_TYPE: SMTP
Received: from clientip-219.142.69.76?logid-0D7FCBD573EF4A8E87ED858BE19742E2 (unknown [172.18.0.92]) by chinatelecom.cn (HERMES) with SMTP id 4A2BA2800CF; Thu, 12 Sep 2019 16:10:43 +0800 (CST)
X-189-SAVE-TO-SEND: 66040161@chinatelecom.cn
Received: from  ([172.18.0.92]) by App0021 with ESMTP id 0D7FCBD573EF4A8E87ED858BE19742E2 for db3546@att.com;  Thu Sep 12 16:10:45 2019
X-Transaction-ID: 0D7FCBD573EF4A8E87ED858BE19742E2
X-filter-score: filter<0>
X-Real-From: xiechf@chinatelecom.cn
X-Receive-IP: 172.18.0.92
X-MEDUSA-Status: 0
Date: Thu, 12 Sep 2019 16:10:42 +0800
From: "xiechf@chinatelecom.cn" <xiechf@chinatelecom.cn>
To: =?ISO-8859-1?B?QlJVTkdBUkQsIERFQk9SQUggQQ==?= <db3546@att.com>,  "pce@ietf.org" <pce@ietf.org>
Cc: pce-chairs <pce-chairs@ietf.org>
References: <F64C10EAA68C8044B33656FA214632C8A3A1FDCF@MISOUT7MSGUSRDE.ITServices.sbc.com>, <C7794D4A32C7D046B93DBCF0FA202C182E8397E3@lhreml505-mbs.china.huawei.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7, 2, 8, 379[cn]
Mime-Version: 1.0
Message-ID: <2019091216104208805327@chinatelecom.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart547440808108_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/J7v_EcV-jIO84Q0mn-LTzWDaT0M>
Subject: Re: [Pce] Adrian stepping down as PCE co-chair
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Sep 2019 08:10:51 -0000

This is a multi-part message in MIME format.

------=_001_NextPart547440808108_=----
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: base64

TWFueSB0aGFua3MgdG8gQWRyaWFuIGZvciB5b3VyIGdyZWF0IHdvcmsgYW5kIGtpbmRuZXNzLg0K
DQpDaG9uZ2ZlbmcgDQogDQpGcm9tOiBLaGFzYW5vdiBCb3Jpcw0KRGF0ZTogMjAxOS0wOS0xMiAx
NjowMA0KVG86IEJSVU5HQVJELCBERUJPUkFIIEE7IHBjZUBpZXRmLm9yZw0KQ0M6IHBjZS1jaGFp
cnMNClN1YmplY3Q6IFJlOiBbUGNlXSBBZHJpYW4gc3RlcHBpbmcgZG93biBhcyBQQ0UgY28tY2hh
aXINClRoYW5rcyBhIGxvdCBBZHJpYW4gZm9yIGFsbCB5b3VyIGdyZWF0IHdvcmsgYW5kIGVmZm9y
dHMhDQogDQpTWSwNCkJvcmlzDQogDQpGcm9tOiBQY2UgW21haWx0bzpwY2UtYm91bmNlc0BpZXRm
Lm9yZ10gT24gQmVoYWxmIE9mIEJSVU5HQVJELCBERUJPUkFIIEENClNlbnQ6IFdlZG5lc2RheSwg
U2VwdGVtYmVyIDExLCAyMDE5IDExOjE0IFBNDQpUbzogcGNlQGlldGYub3JnDQpDYzogcGNlLWNo
YWlycyA8cGNlLWNoYWlyc0BpZXRmLm9yZz4NClN1YmplY3Q6IFtQY2VdIEFkcmlhbiBzdGVwcGlu
ZyBkb3duIGFzIFBDRSBjby1jaGFpcg0KIA0KSGksDQogDQpBcyB3ZSBub3RlZCBlYXJsaWVyLCBB
ZHJpYW4gc3RlcHBlZCBpbiB0byBoZWxwIHVzIHdpdGggdGhlIFBDRSBkb2N1bWVudCBxdWV1ZSBh
bmQgaGVscCBicmluZyBEaHJ1diBvbiBhcyBhIG5ldyBjaGFpci4gSGUgaGFzIGRvbmUgYSBmYW50
YXN0aWMgam9iIGFuZCBEaHJ1diBhbmQgSnVsaWVuIGFyZSBub3cgcmVhZHkgdG8gZ28gZm9yd2Fy
ZC4NCiANCldlIHZlcnkgbXVjaCBhcHByZWNpYXRlIGhpcyBzdXBwb3J0IGFuZCB0aGFuayBoaW0g
Zm9yIGFsbCBoaXMgaGVscCENCiANCkRlYm9yYWgNCiANCg==

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

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charse=
t=3DISO-8859-1"><style>body { line-height: 1.5; }blockquote { margin-top: =
0px; margin-bottom: 0px; margin-left: 0.5em; }p { margin-top: 0px; margin-=
bottom: 0px; }div.foxdiv20190912160844894234 { }body { font-size: 10.5pt; =
font-family: 'Microsoft YaHei UI'; color: rgb(0, 0, 0); line-height: 1.5; =
}</style></head><body>=0A<!--[if gte mso 9]><xml>=0A<o:shapedefaults v:ext=
=3D"edit" spidmax=3D"1026" ></o:shapedefaults>=0A</xml><![endif]--><!--[if=
 gte mso 9]><xml>=0A<o:shapelayout v:ext=3D"edit">=0A<o:idmap v:ext=3D"edi=
t" data=3D"1" ></o:idmap>=0A</o:shapelayout></xml><![endif]-->=0A<div><spa=
n></span>Many thanks to Adrian for your great work and kindness.</div><div=
><br></div><div>Chongfeng&nbsp;</div>=0A<blockquote style=3D"margin-top: 0=
px; margin-bottom: 0px; margin-left: 0.5em;"><div>&nbsp;</div><div style=
=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">=
<div style=3D"PADDING-RIGHT: 8px; PADDING-LEFT: 8px; FONT-SIZE: 12px;FONT-=
FAMILY:tahoma;COLOR:#000000; BACKGROUND: #efefef; PADDING-BOTTOM: 8px; PAD=
DING-TOP: 8px"><div><b>From:</b>&nbsp;<a href=3D"mailto:khasanov.boris@hua=
wei.com" style=3D"color: rgb(5, 99, 193); text-decoration: underline;">Kha=
sanov Boris</a></div><div><b>Date:</b>&nbsp;2019-09-12&nbsp;16:00</div><di=
v><b>To:</b>&nbsp;<a href=3D"mailto:db3546@att.com" style=3D"color: rgb(5,=
 99, 193); text-decoration: underline;">BRUNGARD, DEBORAH A</a>; <a href=
=3D"mailto:pce@ietf.org" style=3D"color: rgb(5, 99, 193); text-decoration:=
 underline;">pce@ietf.org</a></div><div><b>CC:</b>&nbsp;<a href=3D"mailto:=
pce-chairs@ietf.org" style=3D"color: rgb(5, 99, 193); text-decoration: und=
erline;">pce-chairs</a></div><div><b>Subject:</b>&nbsp;Re: [Pce] Adrian st=
epping down as PCE co-chair</div></div></div><div><div class=3D"FoxDiv2019=
0912160844894234">=0A<!--[if gte mso 9]><xml>=0A<o:shapedefaults v:ext=3D"=
edit" spidmax=3D"1026" ></o:shapedefaults>=0A</xml><![endif]--><!--[if gte=
 mso 9]><xml>=0A<o:shapelayout v:ext=3D"edit">=0A<o:idmap v:ext=3D"edit" d=
ata=3D"1" ></o:idmap>=0A</o:shapelayout></xml><![endif]-->=0A<div class=3D=
"WordSection1" style=3D"page: WordSection1;">=0A<p class=3D"MsoNormal" sty=
le=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, san=
s-serif;"><span style=3D"color:#1F497D">Thanks a lot Adrian for all your g=
reat work and efforts!<o:p></o:p></span></p>=0A<p class=3D"MsoNormal" styl=
e=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans=
-serif;"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></span></p>=0A<p c=
lass=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; fon=
t-family: Calibri, sans-serif;"><span style=3D"color:#1F497D">SY,<o:p></o:=
p></span></p>=0A<p class=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span style=3D"color:#=
1F497D">Boris<o:p></o:p></span></p>=0A<p class=3D"MsoNormal" style=3D"marg=
in: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">=
<span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></span></p>=0A<div>=0A<div =
style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in =
0in">=0A<p class=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-siz=
e: 11pt; font-family: Calibri, sans-serif;"><b>From:</b> Pce [mailto:pce-b=
ounces@ietf.org] <b>On Behalf Of=0A</b>BRUNGARD, DEBORAH A<br>=0A<b>Sent:<=
/b> Wednesday, September 11, 2019 11:14 PM<br>=0A<b>To:</b> pce@ietf.org<b=
r>=0A<b>Cc:</b> pce-chairs &lt;pce-chairs@ietf.org&gt;<br>=0A<b>Subject:</=
b> [Pce] Adrian stepping down as PCE co-chair<o:p></o:p></p>=0A</div>=0A</=
div>=0A<p class=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-size=
: 11pt; font-family: Calibri, sans-serif;"><o:p>&nbsp;</o:p></p>=0A<p clas=
s=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-f=
amily: Calibri, sans-serif;">Hi,<o:p></o:p></p>=0A<p class=3D"MsoNormal" s=
tyle=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, s=
ans-serif;"><o:p>&nbsp;</o:p></p>=0A<p class=3D"MsoNormal" style=3D"margin=
: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">As=
 we noted earlier, Adrian stepped in to help us with the PCE document queu=
e and help bring Dhruv on as a new chair. He has done a fantastic job and =
Dhruv and Julien are now ready to go forward.<o:p></o:p></p>=0A<p class=3D=
"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-famil=
y: Calibri, sans-serif;"><o:p>&nbsp;</o:p></p>=0A<p class=3D"MsoNormal" st=
yle=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sa=
ns-serif;">We very much appreciate his support and thank him for all his h=
elp!<o:p></o:p></p>=0A<p class=3D"MsoNormal" style=3D"margin: 0in 0in 0.00=
01pt; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p>&nbsp;</o:p=
></p>=0A<p class=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-siz=
e: 11pt; font-family: Calibri, sans-serif;">Deborah<o:p></o:p></p>=0A<p cl=
ass=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font=
-family: Calibri, sans-serif;"><o:p>&nbsp;</o:p></p>=0A</div>=0A</div></di=
v></blockquote>=0A</body></html>
------=_001_NextPart547440808108_=------


From nobody Thu Sep 12 04:32:32 2019
Return-Path: <chengli13@huawei.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F018B1200EB; Thu, 12 Sep 2019 04:32:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LtrO9WHkZxJd; Thu, 12 Sep 2019 04:32:28 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B5ED1200CD; Thu, 12 Sep 2019 04:32:28 -0700 (PDT)
Received: from lhreml709-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id DEC1A24BB72FBFDB26A4; Thu, 12 Sep 2019 12:32:25 +0100 (IST)
Received: from DGGEML424-HUB.china.huawei.com (10.1.199.41) by lhreml709-cah.china.huawei.com (10.201.108.32) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 12 Sep 2019 12:32:25 +0100
Received: from DGGEML529-MBX.china.huawei.com ([169.254.6.58]) by dggeml424-hub.china.huawei.com ([10.1.199.41]) with mapi id 14.03.0439.000; Thu, 12 Sep 2019 19:32:21 +0800
From: "Chengli (Cheng Li)" <chengli13@huawei.com>
To: Jonathan Hardwick <Jonathan.Hardwick=40metaswitch.com@dmarc.ietf.org>, Dhruv Dhody <dhruv.ietf@gmail.com>, pce <pce@ietf.org>
CC: pce-chairs <pce-chairs@ietf.org>
Thread-Topic: [Pce] WG LC for draft-farrel-pce-stateful-flags-01
Thread-Index: AQHVaV2+ZsTGnkTw6UGIBAIldt0Y1g==
Date: Thu, 12 Sep 2019 11:32:22 +0000
Message-ID: <C7C2E1C43D652C4E9E49FE7517C236CB026D9BE8@dggeml529-mbx.china.huawei.com>
References: <CAB75xn6YcL4wXggWTBhfwOp_go32XaHFjaV+oEV-hdE7XjFuyw@mail.gmail.com> <CAB75xn6cFH-zYKkh-SzBRrpoT0j=cpbGa=mNfZCKBpCi5+UPmQ@mail.gmail.com>, <BL0PR02MB4868EAFE6120EAF3EDFDE8D084B10@BL0PR02MB4868.namprd02.prod.outlook.com>
In-Reply-To: <BL0PR02MB4868EAFE6120EAF3EDFDE8D084B10@BL0PR02MB4868.namprd02.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_C7C2E1C43D652C4E9E49FE7517C236CB026D9BE8dggeml529mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/wTQUxLOF8fo-XW9-Ax6eARv6mHQ>
Subject: Re: [Pce] WG LC for draft-farrel-pce-stateful-flags-01
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Sep 2019 11:32:30 -0000

--_000_C7C2E1C43D652C4E9E49FE7517C236CB026D9BE8dggeml529mbxchi_
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable

+1. A simple, straightforward and useful document.

Support to be published.

Thanks,
Cheng




________________________________
=1B$BM{Dh=1B(B Cheng Li
Email: chengli13@huawei.com<mailto:chengli13@huawei.com>



From: Jonathan Hardwick<Jonathan.Hardwick=3D40metaswitch.com@dmarc.ietf.org=
<mailto:Jonathan.Hardwick=3D40metaswitch.com@dmarc.ietf.org>>
To: Dhruv Dhody<dhruv.ietf@gmail.com<mailto:dhruv.ietf@gmail.com>>;pce<pce@=
ietf.org<mailto:pce@ietf.org>>
Cc: pce-chairs<pce-chairs@ietf.org<mailto:pce-chairs@ietf.org>>
Subject: Re: [Pce] WG LC for draft-farrel-pce-stateful-flags-01
Time: 2019-09-11 15:42:03

I have read the document. It's straightforward and clear. I think it's read=
y to be published.
Cheers
Jon

-----Original Message-----
From: Pce <pce-bounces@ietf.org> On Behalf Of Dhruv Dhody
Sent: 09 September 2019 12:05
To: pce@ietf.org
Cc: pce-chairs <pce-chairs@ietf.org>
Subject: Re: [Pce] WG LC for draft-farrel-pce-stateful-flags-01

NOTE: Message is from an external sender

Hi WG,

We have only one response so far. This is a focused small document, with ju=
st 1-2 pages of the main content that updates a problem that was found in R=
FC 8231. This might seem trivial but it is important as a WG that we fix is=
sues in our published RFCs and make it easier for later work and implementa=
tions.

Please read and comment, if you feel the document should not be published, =
please state your reason. We urge you to be vocal on the list either way, y=
ou have another week as WG LC closes on 16th Sept.

Thanks!
PCE Chairs

On Fri, Aug 30, 2019 at 11:43 PM Dhruv Dhody <dhruv.ietf@gmail.com> wrote:
>
> Hi WG,
>
> This email starts a 'working group last call' for
> draft-farrel-pce-stateful-flags-01 [1]. This I-D is focused and has an
> uncontroversial fix to RFC 8231, we are moving it directly to WGLC.
> See [2] for context.
>
> Please indicate your support or concern for this draft.
>
> If you are opposed to the progression of the draft, please articulate
> your concern.
>
> If you support, please indicate that you have read the latest version
> and it is ready for publication.
>
> As always, review comments and nits are most welcome.
>
> The WG LC will end on 16th September 2019.
>
> Thanks,
> PCE Chairs
>
> [1] https://datatracker.ietf.org/doc/draft-farrel-pce-stateful-flags/
> [2]
> https://mailarchive.ietf.org/arch/msg/pce/tTkJKO34xTD0CY48IJCk5FjmiJ4

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

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

--_000_C7C2E1C43D652C4E9E49FE7517C236CB026D9BE8dggeml529mbxchi_
Content-Type: text/html; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-2022-=
jp">
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; pad=
ding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div style=3D"font-family:Calibri,Helvetica!important">&#43;1. A simple, st=
raightforward and useful document.<br>
<br>
Support to be published.<br>
<br>
Thanks,<br>
Cheng<br>
<br>
<br>
<br>
<br>
<hr style=3D"border-top:dotted 1px">
=1B$BM{Dh=1B(B Cheng Li<br>
Email: <a href=3D"mailto:chengli13@huawei.com">chengli13@huawei.com</a><br>
<br>
<br>
<br>
</div>
<div name=3D"x_AnyOffice-Background-Image" style=3D"border-top:1px solid #B=
5C4DF; padding:8px">
<div><b>From: </b>Jonathan Hardwick&lt;<a href=3D"mailto:Jonathan.Hardwick=
=3D40metaswitch.com@dmarc.ietf.org">Jonathan.Hardwick=3D40metaswitch.com@dm=
arc.ietf.org</a>&gt;</div>
<div><b>To: </b>Dhruv Dhody&lt;<a href=3D"mailto:dhruv.ietf@gmail.com">dhru=
v.ietf@gmail.com</a>&gt;;pce&lt;<a href=3D"mailto:pce@ietf.org">pce@ietf.or=
g</a>&gt;</div>
<div><b>Cc: </b>pce-chairs&lt;<a href=3D"mailto:pce-chairs@ietf.org">pce-ch=
airs@ietf.org</a>&gt;</div>
<div><b>Subject: </b>Re: [Pce] WG LC for draft-farrel-pce-stateful-flags-01=
</div>
<div><b>Time: </b>2019-09-11 15:42:03</div>
<br>
</div>
</div>
<font size=3D"2"><span style=3D"font-size:10pt;">
<div class=3D"PlainText">I have read the document. It's straightforward and=
 clear. I think it's ready to be published.<br>
Cheers<br>
Jon<br>
<br>
-----Original Message-----<br>
From: Pce &lt;pce-bounces@ietf.org&gt; On Behalf Of Dhruv Dhody<br>
Sent: 09 September 2019 12:05<br>
To: pce@ietf.org<br>
Cc: pce-chairs &lt;pce-chairs@ietf.org&gt;<br>
Subject: Re: [Pce] WG LC for draft-farrel-pce-stateful-flags-01<br>
<br>
NOTE: Message is from an external sender<br>
<br>
Hi WG,<br>
<br>
We have only one response so far. This is a focused small document, with ju=
st 1-2 pages of the main content that updates a problem that was found in R=
FC 8231. This might seem trivial but it is important as a WG that we fix is=
sues in our published RFCs and make
 it easier for later work and implementations.<br>
<br>
Please read and comment, if you feel the document should not be published, =
please state your reason. We urge you to be vocal on the list either way, y=
ou have another week as WG LC closes on 16th Sept.<br>
<br>
Thanks!<br>
PCE Chairs<br>
<br>
On Fri, Aug 30, 2019 at 11:43 PM Dhruv Dhody &lt;dhruv.ietf@gmail.com&gt; w=
rote:<br>
&gt;<br>
&gt; Hi WG,<br>
&gt;<br>
&gt; This email starts a 'working group last call' for<br>
&gt; draft-farrel-pce-stateful-flags-01 [1]. This I-D is focused and has an=
 <br>
&gt; uncontroversial fix to RFC 8231, we are moving it directly to WGLC. <b=
r>
&gt; See [2] for context.<br>
&gt;<br>
&gt; Please indicate your support or concern for this draft.<br>
&gt;<br>
&gt; If you are opposed to the progression of the draft, please articulate =
<br>
&gt; your concern.<br>
&gt;<br>
&gt; If you support, please indicate that you have read the latest version =
<br>
&gt; and it is ready for publication.<br>
&gt;<br>
&gt; As always, review comments and nits are most welcome.<br>
&gt;<br>
&gt; The WG LC will end on 16th September 2019.<br>
&gt;<br>
&gt; Thanks,<br>
&gt; PCE Chairs<br>
&gt;<br>
&gt; [1] <a href=3D"https://datatracker.ietf.org/doc/draft-farrel-pce-state=
ful-flags/">
https://datatracker.ietf.org/doc/draft-farrel-pce-stateful-flags/</a><br>
&gt; [2] <br>
&gt; <a href=3D"https://mailarchive.ietf.org/arch/msg/pce/tTkJKO34xTD0CY48I=
JCk5FjmiJ4">
https://mailarchive.ietf.org/arch/msg/pce/tTkJKO34xTD0CY48IJCk5FjmiJ4</a><b=
r>
<br>
_______________________________________________<br>
Pce mailing list<br>
Pce@ietf.org<br>
<a href=3D"https://www.ietf.org/mailman/listinfo/pce">https://www.ietf.org/=
mailman/listinfo/pce</a><br>
<br>
_______________________________________________<br>
Pce mailing list<br>
Pce@ietf.org<br>
<a href=3D"https://www.ietf.org/mailman/listinfo/pce">https://www.ietf.org/=
mailman/listinfo/pce</a><br>
</div>
</span></font>
</body>
</html>

--_000_C7C2E1C43D652C4E9E49FE7517C236CB026D9BE8dggeml529mbxchi_--


From nobody Thu Sep 12 05:52:11 2019
Return-Path: <sergio.belotti@nokia.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91802120052; Thu, 12 Sep 2019 05:52:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.onmicrosoft.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 ISfKHnJ-zcK4; Thu, 12 Sep 2019 05:52:07 -0700 (PDT)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-eopbgr150121.outbound.protection.outlook.com [40.107.15.121]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 312AC12006D; Thu, 12 Sep 2019 05:52:07 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=iBr+vin7GnGNvNdylwUy6GrgqHGWX3UcSOtJaUN3z7VvTjQ9JcbFaRHoQcuphPVp7yo106CO+KjIDzhG3HlkEQZbNWJ/tY5YI1QgpORZltF1/ulrQMdxUwzu8JwgRNgEQJfOm6BZiw8I8ODyWTpBGhGrxfTDZ9AzNhnTCLTccGkuFrJsjqHABfnVMdJciyfMDQF9iE3oVsEsjqv3ScqfygCAz9TM/bzIEqhtxttuawPvEr4Pj1tMEcgV2LnWJCbpXeY+ZvhBarGh0fqX4X+j/wM3jukyF47MQ7eJc6MGnkk79zer/bDvevv82jWbICnlsvpNYXY3tB8A4g7DoXIfXg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=d2RcZ0VXgr3GbDZ4t1ivZebBPpoLMvwyG3RaBtKI6IY=; b=OEOWsjrnhwbOYt8C5ZDNZ1rXzdRv6nyRQEE1nW1uKiI/Ivrtgk4CxQ37Ni/e11PDIYn0kI+kYYP05uld4ZPjzNPEUNDQWof49Wjf+K0CJ001imfu8QLNKqy0qHK9tpySlp3mtuNh0K5nJGf3Kb25PIrxdxFN+ExDOjObloheMFhlL+GjPLTVZjUUP1OktcInPlpoMCH2U4b00rZ53CLztf+4DcqEMAdskX2O3X4IYpYJwV75S5bn80OPZ9iU9qWpLKPSnG70/krihIVQDx7DIt4287PZ08wihNg/lXLbGtGzG8cimqDF3p5kwXzafAsIeyJXQdXv5LAxbXzjrpX0Sg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nokia.com; dmarc=pass action=none header.from=nokia.com; dkim=pass header.d=nokia.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com;  s=selector1-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=d2RcZ0VXgr3GbDZ4t1ivZebBPpoLMvwyG3RaBtKI6IY=; b=S9sCfpN7IXphB3C+6ud2ZokfihTelazKW7NPlFFi4Ye/AP94LmJ885iOStGVmV9aILEEHKy01yACT5havPWrPVelwEgpnoTGhnbJk6MUkvDd7XYQcId5IvWRPjHNyL7p8hvpbZw6ErsoKbWWYQZORlWL3pZjnfNLjYaXEBnF56M=
Received: from AM0PR07MB5121.eurprd07.prod.outlook.com (20.178.19.26) by AM0PR07MB4628.eurprd07.prod.outlook.com (52.135.150.31) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2263.6; Thu, 12 Sep 2019 12:52:05 +0000
Received: from AM0PR07MB5121.eurprd07.prod.outlook.com ([fe80::cd89:db8:8be8:6f5b]) by AM0PR07MB5121.eurprd07.prod.outlook.com ([fe80::cd89:db8:8be8:6f5b%6]) with mapi id 15.20.2284.009; Thu, 12 Sep 2019 12:52:05 +0000
From: "Belotti, Sergio (Nokia - IT/Vimercate)" <sergio.belotti@nokia.com>
To: "BRUNGARD, DEBORAH A" <db3546@att.com>, "pce@ietf.org" <pce@ietf.org>
CC: pce-chairs <pce-chairs@ietf.org>
Thread-Topic: Adrian stepping down as PCE co-chair
Thread-Index: AdVo28vCYIoHnaEsTjSAQbDA3xY4EAAjPjBg
Date: Thu, 12 Sep 2019 12:52:04 +0000
Message-ID: <AM0PR07MB512166FD6089D8393827A24991B00@AM0PR07MB5121.eurprd07.prod.outlook.com>
References: <F64C10EAA68C8044B33656FA214632C8A3A1FDCF@MISOUT7MSGUSRDE.ITServices.sbc.com>
In-Reply-To: <F64C10EAA68C8044B33656FA214632C8A3A1FDCF@MISOUT7MSGUSRDE.ITServices.sbc.com>
Accept-Language: it-IT, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=sergio.belotti@nokia.com; 
x-originating-ip: [79.31.140.11]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 85a43aeb-0da4-4c8a-e9dd-08d73780037c
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600166)(711020)(4605104)(1401327)(4618075)(2017052603328)(7193020); SRVR:AM0PR07MB4628; 
x-ms-traffictypediagnostic: AM0PR07MB4628:
x-microsoft-antispam-prvs: <AM0PR07MB4628DFBE0CFD9E357C34FD9C91B00@AM0PR07MB4628.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:6790;
x-forefront-prvs: 01583E185C
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(39860400002)(366004)(136003)(396003)(376002)(346002)(199004)(189003)(33656002)(76176011)(14454004)(66066001)(5660300002)(9686003)(6246003)(478600001)(7696005)(4326008)(53936002)(229853002)(52536014)(25786009)(2501003)(316002)(110136005)(4744005)(99286004)(446003)(66556008)(790700001)(6116002)(3846002)(66476007)(53546011)(6306002)(64756008)(76116006)(186003)(66946007)(71200400001)(66446008)(86362001)(6506007)(71190400001)(26005)(6436002)(102836004)(11346002)(55016002)(476003)(486006)(8936002)(2906002)(74316002)(8676002)(81166006)(81156014)(7736002)(54896002)(256004); DIR:OUT; SFP:1102; SCL:1; SRVR:AM0PR07MB4628; H:AM0PR07MB5121.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: nokia.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: MTohILGdlDySuABEufEDT07XY3/270FKnt/TYEUHIxGQ8VVBnm+2HTiuPKsg9AwsztM2gT5/kg0swbI35fikCaSVToee4Xlbn7ggSQL24NswInvOzs0lBmz8hcpwkgJjigSWH0p87SnO8gJfDPt+vX2cONbz/vio/OFcyGBp3yAXS1fL1MII85sCFXDvM2/QI+EOQqkQI1U9V5bb6/qSM+zH8/ppvJVUjaTazCym19wyHsLHrGU1FeLPiBH9Bf1fVTv2WB7lHzIbPlnKpYR9a5Qa5gmERMWQD0VAhhX9pGXatJk3ksl9xM1DGZsGwEeu3Q04UwYpQno9hHm/8TweXWN/UAPXMAgWi2S731zjqW1FEplThP/HVKPFStkd5xPmmH1y6xfDUYUEUz2wx0qPGZzizVG4ipsc43to+qvnNG0=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_AM0PR07MB512166FD6089D8393827A24991B00AM0PR07MB5121eurp_"
MIME-Version: 1.0
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 85a43aeb-0da4-4c8a-e9dd-08d73780037c
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Sep 2019 12:52:04.9554 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: eZr3E6PaxGpI+p96V6ZVOryRLe4VGy6moCK15CGBTrrH2qF7q87pTpwvRslvXVVogeSi6fCYBeYBxDrxKlDBK2l98xigedOP2mHJ3RRTq38=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR07MB4628
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/mDzUOhM6cih-RoBR8O47Et162HI>
Subject: Re: [Pce] Adrian stepping down as PCE co-chair
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Sep 2019 12:52:10 -0000

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

Thanks Adrian !

Cheers
SErgio

From: Pce <pce-bounces@ietf.org> On Behalf Of BRUNGARD, DEBORAH A
Sent: Wednesday, September 11, 2019 10:14 PM
To: pce@ietf.org
Cc: pce-chairs <pce-chairs@ietf.org>
Subject: [Pce] Adrian stepping down as PCE co-chair

Hi,

As we noted earlier, Adrian stepped in to help us with the PCE document que=
ue and help bring Dhruv on as a new chair. He has done a fantastic job and =
Dhruv and Julien are now ready to go forward.

We very much appreciate his support and thank him for all his help!

Deborah


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Thanks Adrian !<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Cheers<o:p></o:p></p>
<p class=3D"MsoNormal">SErgio<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b>From:</b> Pce &lt;pce-bounces@ietf.org&gt; <b>On =
Behalf Of </b>
BRUNGARD, DEBORAH A<br>
<b>Sent:</b> Wednesday, September 11, 2019 10:14 PM<br>
<b>To:</b> pce@ietf.org<br>
<b>Cc:</b> pce-chairs &lt;pce-chairs@ietf.org&gt;<br>
<b>Subject:</b> [Pce] Adrian stepping down as PCE co-chair<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">As we noted earlier, Adrian stepped in to help us wi=
th the PCE document queue and help bring Dhruv on as a new chair. He has do=
ne a fantastic job and Dhruv and Julien are now ready to go forward.<o:p></=
o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">We very much appreciate his support and thank him fo=
r all his help!<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Deborah<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_AM0PR07MB512166FD6089D8393827A24991B00AM0PR07MB5121eurp_--


From nobody Thu Sep 12 05:54:29 2019
Return-Path: <tsaad.net@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6B37120052; Thu, 12 Sep 2019 05:54:26 -0700 (PDT)
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 Gl-bOor5zraW; Thu, 12 Sep 2019 05:54:24 -0700 (PDT)
Received: from mail-io1-xd2d.google.com (mail-io1-xd2d.google.com [IPv6:2607:f8b0:4864:20::d2d]) (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 8FC6D120041; Thu, 12 Sep 2019 05:54:24 -0700 (PDT)
Received: by mail-io1-xd2d.google.com with SMTP id b136so54247135iof.3; Thu, 12 Sep 2019 05:54:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:cc:subject:thread-topic:thread-index:date:message-id :references:in-reply-to:accept-language:content-language :mime-version; bh=ouFeekRl+fpJTBYrAYXa+ynteSAc3TlJKdXv+0XnvYU=; b=JnrJQxC/rCTZ8UvEXmQ10knEQyfv7K7Vga/eLoSacygwRpMoFVR0rMspMfTCFxQuGl k98er2b/BjYaENyqFYyZEmoGU0F99KFrnvNQFyUrgdGD0JI5bobjRgPcWJwfCoysDNCK sdJkz9iQfPvc+4pLPzptP8yQQi7RI7NngLad/Jddh4k/3+t6EGUtOmAcyqLpPnMkoxom Q5UbrfIurtuSYcvW0gbQ9IimVNRFgKqdxAZTI9QEnHGjrgXVARllOkk/Nv4g/w4KmCC8 jVBn7lyaD9+jjdoAGpD3Wfs7AuXH7ZBMArSnwXaiv+YRksrN7W+o4LcCvKZPH+w2GjWv k9Vw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:thread-topic:thread-index :date:message-id:references:in-reply-to:accept-language :content-language:mime-version; bh=ouFeekRl+fpJTBYrAYXa+ynteSAc3TlJKdXv+0XnvYU=; b=r/FL4gfG9Yy3Fwv2qoGzrz4BMJ/GJMWDObl9Ll3XxSV4MEVBgYBxbnFMooe+GNjdSH VdyG9+Eroonq1gbtuDYZ5L0r7kelDSxcYzF4UbeakkicJKsKPcWGl584wxwz/ubcuaez pK40wumxYVCY/j5XHQ8tWMHyQiOxKR2uMcwJ6zj6CHImueyZt8zlPg/a4YXjaH/Gax9A j4+FnoZq9NEy91qA+J4//JNaPAuBzTdPDlnu9XtdYPCdO8eLB4XqOuOGjKl1bznzzVHk G5Qjgs4tfRULSzzwFYzeck0xods0TXL7CL8QdWW8uXLJYglaNdFmF+7eKO0LYrtA7i1h BRyw==
X-Gm-Message-State: APjAAAW19Np3fHx839eCWhXSS84Djrvh4dj4efi9m5UCvG6/pAIyeC3q U+ZedKQ0zHkkkcoupciicyo=
X-Google-Smtp-Source: APXvYqxttCySlLG+7wEAuFwYYLMS/0J4+CnNCZjzPxTpNEu/Qd6S6y0WIL7uY9Hz8txjStGlAuutQA==
X-Received: by 2002:a6b:4a11:: with SMTP id w17mr4127542iob.21.1568292863871;  Thu, 12 Sep 2019 05:54:23 -0700 (PDT)
Received: from BYAPR19MB3415.namprd19.prod.outlook.com ([2603:1036:307:293b::5]) by smtp.gmail.com with ESMTPSA id c21sm9954673iot.15.2019.09.12.05.54.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 Sep 2019 05:54:23 -0700 (PDT)
From: Tarek Saad <tsaad.net@gmail.com>
To: "BRUNGARD, DEBORAH A" <db3546@att.com>, "pce@ietf.org" <pce@ietf.org>
CC: pce-chairs <pce-chairs@ietf.org>
Thread-Topic: [Pce] Adrian stepping down as PCE co-chair
Thread-Index: AUY4QTRBNxg0MkwgOnYLjLlKtgmtpp5iT/zY
X-MS-Exchange-MessageSentRepresentingType: 1
Date: Thu, 12 Sep 2019 12:54:22 +0000
Message-ID: <BYAPR19MB34157638D7C50FD358FD426DFCB00@BYAPR19MB3415.namprd19.prod.outlook.com>
References: <F64C10EAA68C8044B33656FA214632C8A3A1FDCF@MISOUT7MSGUSRDE.ITServices.sbc.com>
In-Reply-To: <F64C10EAA68C8044B33656FA214632C8A3A1FDCF@MISOUT7MSGUSRDE.ITServices.sbc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-Exchange-Organization-SCL: -1
X-MS-TNEF-Correlator: 
X-MS-Exchange-Organization-RecordReviewCfmType: 0
Content-Type: multipart/alternative; boundary="_000_BYAPR19MB34157638D7C50FD358FD426DFCB00BYAPR19MB3415namp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/c8twrHXRUEf9sC4K9fsV6tp0_P4>
Subject: Re: [Pce] Adrian stepping down as PCE co-chair
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Sep 2019 12:54:27 -0000

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

Many thanks Adrian.

Regards,
Tarek

From: Pce <pce-bounces@ietf.org> on behalf of "BRUNGARD, DEBORAH A" <db3546=
@att.com>
Date: Wednesday, September 11, 2019 at 4:14 PM
To: "pce@ietf.org" <pce@ietf.org>
Cc: pce-chairs <pce-chairs@ietf.org>
Subject: [Pce] Adrian stepping down as PCE co-chair

Hi,

As we noted earlier, Adrian stepped in to help us with the PCE document que=
ue and help bring Dhruv on as a new chair. He has done a fantastic job and =
Dhruv and Julien are now ready to go forward.

We very much appreciate his support and thank him for all his help!

Deborah


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

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc=
hemas-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/of=
fice/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"Times New Roman \(Body CS\)";
	panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.emailstyle17
	{mso-style-name:emailstyle17;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style>
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">Many thanks Adrian.=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">Regards,<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">Tarek<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><b><span style=3D"font-si=
ze:12.0pt;color:black">From:
</span></b><span style=3D"font-size:12.0pt;color:black">Pce &lt;pce-bounces=
@ietf.org&gt; on behalf of &quot;BRUNGARD, DEBORAH A&quot; &lt;db3546@att.c=
om&gt;<br>
<b>Date: </b>Wednesday, September 11, 2019 at 4:14 PM<br>
<b>To: </b>&quot;pce@ietf.org&quot; &lt;pce@ietf.org&gt;<br>
<b>Cc: </b>pce-chairs &lt;pce-chairs@ietf.org&gt;<br>
<b>Subject: </b>[Pce] Adrian stepping down as PCE co-chair<o:p></o:p></span=
></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">As we noted earlier, Adri=
an stepped in to help us with the PCE document queue and help bring Dhruv o=
n as a new chair. He has done a fantastic job and Dhruv and Julien are now =
ready to go forward.<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">We very much appreciate h=
is support and thank him for all his help!<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">Deborah<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">&nbsp;<o:p></o:p></p>
</div>
</div>
</body>
</html>

--_000_BYAPR19MB34157638D7C50FD358FD426DFCB00BYAPR19MB3415namp_--


From nobody Fri Sep 13 00:00:56 2019
Return-Path: <francesca.palombini@ericsson.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB4181200BA; Fri, 13 Sep 2019 00:00:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 TnuUH4MWoO3l; Fri, 13 Sep 2019 00:00:38 -0700 (PDT)
Received: from EUR04-VI1-obe.outbound.protection.outlook.com (mail-eopbgr80079.outbound.protection.outlook.com [40.107.8.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A344912004D; Fri, 13 Sep 2019 00:00:37 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Fl7gO5yX7XdOHVFu+mTw72VWioo1p6ZVfYpeGhjmGSy01oaN4e9lwv3mgetorM3pgw8nKW6WVVcbkNLXAVa2kWiRDImb0IWvMGathnrwv3dBjBs+wIFsjBtN6d2kxDuivyed8AkaBcqymSrXWl80U13uwHM/RSP+A5RbsPzfuili1BU9KdeUU0eCPIMpthqZWLWZZdNcK3zUd1bQw4/cAz9OCYkJ4s3M/Mm3r2PsPykP1g12Crw88ks1wCY4HCRF4SVvfdHPpLtZ42rvsnhPAQ1wr5kaBNZUNP5oB+6IGyBit+eX0JZgY1wkUoT66JkzgGEFVaChjrANt4LtReYVAg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=/IYKYJlihEdgnZd1gI2RMQXrs/Q/FYnQiTCAPndHRwk=; b=Sv8H6DHWBL5wkYZyNG3QTKgQ2VquxNEEAMlFUqBhtM5+IObWkovUR3j/w4YfAsXJLN0W+dD5VDFfkS+y4LfE4XofYCggCWYf2OyOI5wWNNqCrqYrGs9N7taXMdJTz/Iw2Ok8EUmXAPpSFqkdacwOIShduE8d7QcZOn7xs3EZOUE1it9CGXKV2npl3/0s5BjBPeMv7K1WngiQlc9y2XjSgglhLmAEu6vUiY6lUTk8KKIUX8S50tvc2dB/DHpJBG6a/ltivYj/MZsh07A6v4n1Fu/uT5D7CITIa/+U8vT3eO3s/D/g4cd/MQX5r5Fpf78lcV0X2787xzW20kfdMWW/yA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=/IYKYJlihEdgnZd1gI2RMQXrs/Q/FYnQiTCAPndHRwk=; b=kFZHvRmnN15US06gA18RFZeBrpQMWTMHig5H4L9No4EDz2evJNjjRWKJe40EJOX7zdGw/Ksh26K4C3YigTidwnZQNfTEd63ZcdptesKXskntiSCNm5aXyH9wCS8YxwWZpxI1bYlqway3PBBu5f1F0YvNQuUwQfInmZKaE+iIRaY=
Received: from HE1PR0701MB2746.eurprd07.prod.outlook.com (10.168.185.17) by HE1PR0701MB2362.eurprd07.prod.outlook.com (10.168.126.149) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2263.10; Fri, 13 Sep 2019 07:00:35 +0000
Received: from HE1PR0701MB2746.eurprd07.prod.outlook.com ([fe80::69ac:4f28:cd6a:6302]) by HE1PR0701MB2746.eurprd07.prod.outlook.com ([fe80::69ac:4f28:cd6a:6302%11]) with mapi id 15.20.2263.016; Fri, 13 Sep 2019 07:00:35 +0000
From: Francesca Palombini <francesca.palombini@ericsson.com>
To: Dhruv Dhody <dhruv.ietf@gmail.com>
CC: General Area Review Team <gen-art@ietf.org>, "draft-ietf-pce-lsp-control-request.all@ietf.org" <draft-ietf-pce-lsp-control-request.all@ietf.org>, "pce@ietf.org" <pce@ietf.org>, "ietf@ietf.org Discussion" <ietf@ietf.org>
Thread-Topic: Genart last call review of draft-ietf-pce-lsp-control-request-08
Thread-Index: AQHVZJgCPIMQGKtzVUGn3Sf9A9xxvqcpWjcA
Date: Fri, 13 Sep 2019 07:00:34 +0000
Message-ID: <45C6E308-79BC-4427-A61C-590D03E7572B@ericsson.com>
References: <156682165261.25516.1887489813169802107@ietfa.amsl.com> <CAB75xn4=Q5gw1Z1fcYTDgwd5BD7S+=Qsa1pt1QfjGc8nLzUhYA@mail.gmail.com>
In-Reply-To: <CAB75xn4=Q5gw1Z1fcYTDgwd5BD7S+=Qsa1pt1QfjGc8nLzUhYA@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=francesca.palombini@ericsson.com; 
x-originating-ip: [158.174.219.143]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: bf3c4bfd-5ada-4116-173b-08d738181358
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600166)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:HE1PR0701MB2362; 
x-ms-traffictypediagnostic: HE1PR0701MB2362:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <HE1PR0701MB236233E9A2DDE5CE6FD759F598B30@HE1PR0701MB2362.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0159AC2B97
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(396003)(346002)(376002)(39860400002)(136003)(366004)(189003)(199004)(51914003)(6506007)(71200400001)(71190400001)(53546011)(14454004)(8676002)(7736002)(66066001)(486006)(2906002)(446003)(102836004)(26005)(478600001)(11346002)(186003)(14444005)(256004)(86362001)(66946007)(81166006)(81156014)(316002)(305945005)(76116006)(6116002)(36756003)(4326008)(53936002)(99286004)(25786009)(8936002)(54906003)(6916009)(64756008)(66556008)(66446008)(66476007)(5660300002)(6512007)(6306002)(44832011)(2616005)(476003)(33656002)(6436002)(76176011)(6246003)(3846002)(6486002)(229853002); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR0701MB2362; H:HE1PR0701MB2746.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: ix05MP8ox0Wc2HXmrLlrWVZMgKMxR3GQ+LgB2crCV1+dMFlMLQHOnVwULFRIqfJB4E0tgzaRvpGMKW3d8G2a6nQkHpAdB30CaBAgMLKQFiTsebk7upNyEvUcZoVonZ/xzaKe+i2yfrhIHEfEouim+6l4TvkxWBaoPhj2B6zFphUeL+OHMXQ6GbQo9iq4SL9TeyK5D3yo+jXYLCD76AU0QlCbX9geyIzpQKNaQXlw+QRWrd7K/YPcU/teIuEt1PFyab5ej20lAlYDOJ6F9aBI96Z/jLUCgHCZlDrH0Ql6bU7D2LjClzKHGvqTlkzxLLOdysRDsMG/B7c7XKyyh60322HtGf2iWA2/FYf8vGrVA1HNCIgNOzeMKEZC+quSVBWaqev7OtfNVgM3mgde4cgBLDNynowEr9qa3Fe/pyxnP1c=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <09B820FEE1A509459D39372D35E33FED@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: bf3c4bfd-5ada-4116-173b-08d738181358
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Sep 2019 07:00:35.0135 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: ZHHTBimi90+IJAdOJ18WHKp/LKkxK9g29RH3wpiHLwEDUNSi3QZtBocOMmCwgQytSv0vbypJLzEWNP0ZOMaZIWQibaeHQqCWpFY2jqil5lGNFYJ5piLtDToHFdZTcqZY
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0701MB2362
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/vr5PWfCrEyTlyOHFROZ4trZUf9A>
Subject: Re: [Pce] Genart last call review of draft-ietf-pce-lsp-control-request-08
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Sep 2019 07:00:42 -0000

SGkgRGhydXYsDQoNClllcywgdGhhdCBsb29rcyBnb29kIHRvIG1lLCBJIGFncmVlIHdpdGggdGhl
IGNoYW5nZXMgYW5kIEknbSBmaW5lIHdpdGggbGV0dGluZyB0aGUgUkZDIGVkaXRvciBmaWd1cmUg
dGhlIGxhc3Qgbml0IG91dC4gVGhhbmtzIQ0KDQpGcmFuY2VzY2ENCg0K77u/T24gMDYvMDkvMjAx
OSwgMTE6NDYsICJEaHJ1diBEaG9keSIgPGRocnV2LmlldGZAZ21haWwuY29tPiB3cm90ZToNCg0K
ICAgIEhpIEZyYW5jZXNjYSwNCiAgICANCiAgICBUaGFua3MgZm9yIHlvdXIgcmV2aWV3LiBGZXcg
dGhvdWdodHMuLi4NCiAgICANCiAgICBPbiBNb24sIEF1ZyAyNiwgMjAxOSBhdCA1OjQ0IFBNIEZy
YW5jZXNjYSBQYWxvbWJpbmkgdmlhIERhdGF0cmFja2VyDQogICAgPG5vcmVwbHlAaWV0Zi5vcmc+
IHdyb3RlOg0KICAgID4NCiAgICA+IFJldmlld2VyOiBGcmFuY2VzY2EgUGFsb21iaW5pDQogICAg
PiBSZXZpZXcgcmVzdWx0OiBSZWFkeSB3aXRoIElzc3Vlcw0KICAgID4NCiAgICA+IEkgYW0gdGhl
IGFzc2lnbmVkIEdlbi1BUlQgcmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIFRoZSBHZW5lcmFsIEFy
ZWENCiAgICA+IFJldmlldyBUZWFtIChHZW4tQVJUKSByZXZpZXdzIGFsbCBJRVRGIGRvY3VtZW50
cyBiZWluZyBwcm9jZXNzZWQNCiAgICA+IGJ5IHRoZSBJRVNHIGZvciB0aGUgSUVURiBDaGFpci4g
IFBsZWFzZSB0cmVhdCB0aGVzZSBjb21tZW50cyBqdXN0DQogICAgPiBsaWtlIGFueSBvdGhlciBs
YXN0IGNhbGwgY29tbWVudHMuDQogICAgPg0KICAgID4gRm9yIG1vcmUgaW5mb3JtYXRpb24sIHBs
ZWFzZSBzZWUgdGhlIEZBUSBhdA0KICAgID4NCiAgICA+IDxodHRwczovL3RyYWMuaWV0Zi5vcmcv
dHJhYy9nZW4vd2lraS9HZW5BcnRmYXE+Lg0KICAgID4NCiAgICA+IERvY3VtZW50OiBkcmFmdC1p
ZXRmLXBjZS1sc3AtY29udHJvbC1yZXF1ZXN0LTA4DQogICAgPiBSZXZpZXdlcjogRnJhbmNlc2Nh
IFBhbG9tYmluaQ0KICAgID4gUmV2aWV3IERhdGU6IDIwMTktMDgtMjYNCiAgICA+IElFVEYgTEMg
RW5kIERhdGU6IDIwMTktMDgtMjgNCiAgICA+IElFU0cgVGVsZWNoYXQgZGF0ZTogTm90IHNjaGVk
dWxlZCBmb3IgYSB0ZWxlY2hhdA0KICAgID4NCiAgICA+IFN1bW1hcnk6IFRoaXMgZHJhZnQgaXMg
YWxtb3N0IHJlYWR5IGZvciBwdWJsaWNhdGlvbiwgYnV0IGhhcyBtaW5vciBpc3N1ZXMvb3Blbg0K
ICAgID4gcG9pbnRzIHRoYXQgc2hvdWxkIGJlIGZpeGVkIGJlZm9yZSBwdWJsaWNhdGlvbi4NCiAg
ICA+DQogICAgPiBNYWpvciBpc3N1ZXM6IE4vQQ0KICAgID4NCiAgICA+IE1pbm9yIGlzc3VlcyAv
IHF1ZXN0aW9uczoNCiAgICA+DQogICAgPiAqIFNlY3Rpb24gMzogQXQgdGhlIGVuZCBvZiBzZWFz
b24gMywgeW91IGluZGljYXRlIHRoYXQgdGhpcyBuZXcgZmxhZyBoYXMgbm8NCiAgICA+IG1lYW5p
bmcgaW4gUENScHQgYW5kIFBDSW5pdGlhdGUgbWVzc2FnZXMuIFJGQzgyMzEgZGVmaW5lcyB0aGF0
IHRoZSBTUlAgT2JqZWN0DQogICAgPiBNQVkgYmUgY2FycmllZCBpbiBQQ0VyciBhcyB3ZWxsLCBz
aG91bGRuJ3QgdGhlcmUgYmUgc3VjaCByZXF1aXJlbWVudHMgKE1VU1QgYmUNCiAgICA+IHNldCB0
byAwLCBNVVNUIGJlIGlnbm9yZWQgb24gcmVjZXB0aW9uKSBmb3IgUENFcnI/DQogICAgPg0KICAg
IA0KICAgIEkgYWdyZWUuIEkgc3VnZ2VzdCB0byBtYWtlIHRoaXMgZ2VuZXJpYywgc29tZXRoaW5n
IGxpa2UgLSAiVGhlIEMgRmxhZw0KICAgIGhhcyBubyBtZWFuaW5nIGluIG90aGVyIFBDRVAgbWVz
c2FnZXMgdGhhdCBjYXJyeSBTUlAgb2JqZWN0IGFuZCB0aGUNCiAgICBmbGFnIE1VU1QgYmUgc2V0
IHRvIDAgb24gdHJhbnNtaXNzaW9uIGFuZCBNVVNUIGJlIGlnbm9yZWQgb24gcmVjZWlwdC4iDQog
ICAgDQogICAgPiAqIEluIHRoZSBmb2xsb3dpbmcgdGV4dCAoU2VjdGlvbiA0KTogIlRoZSBQQ0Ug
U0hPVUxEIE5PVA0KICAgID4gICAgc2VuZCBjb250cm9sIHJlcXVlc3QgZm9yIExTUCB3aGljaCBp
cyBhbHJlYWR5IGRlbGVnYXRlZCB0byB0aGUgUENFLA0KICAgID4gICAgaS5lLiBpZiB0aGUgRCBG
bGFnIGlzIHNldCBpbiB0aGUgUENVcGQgbWVzc2FnZSwgdGhlbiBDIEZsYWcgU0hPVUxEDQogICAg
PiAgICBOT1QgYmUgc2V0LiIgV2h5IGlzIHRoZXJlIGEgU0hPVUxEIE5PVCBpbnN0ZWFkIG9mIE1V
U1QgTk9UPyBJbiB3aGljaA0KICAgID4gICAgc2l0dWF0aW9uIGNvdWxkIGl0IGJlIGFjY2VwdGFi
bGUgb3IgdXNlZnVsIHRvIHJlcXVlc3QgY29udHJvbCBmb3IgYQ0KICAgID4gICAgZGVsZWdhdGVk
IExTUD8NCiAgICA+DQogICAgDQogICAgSXQgd29udCBiZSB1c2VmdWwsIGJ1dCBpZiByZWNlaXZl
ZCBpdCB3b3VsZCBiZSBzaWxlbnRseSBpZ25vcmVkLiBJdA0KICAgIGRvZXMgbm90IHJpc2UgdXAg
dG8gYSBoaWdoIGxldmVsIG9mIGVycm9yIGFuZCBJIHN1c3BlY3QgdGhhdCBpcyB3aHkNCiAgICBh
dXRob3JzIHVzZWQgU0hPVUxELg0KICAgIA0KICAgID4gTml0cy9lZGl0b3JpYWwgY29tbWVudHM6
DQogICAgPg0KICAgIA0KICAgIFRoYW5rcyBmb3IgdGhlc2UsIGp1c3Qgb25lIGNvbW1lbnQgLi4u
DQogICAgDQogICAgPiAqIFRlcm1pbm9sb2d5IHNob3VsZCBhbHNvIGluY2x1ZGUgYSBzZW50ZW5j
ZSBhYm91dCB0aGUgcmVhZGVyIGJlaW5nIGZhbWlsaWFyDQogICAgPiB3aXRoIGF0IGxlYXN0IFJG
QzgyMzEuDQogICAgPg0KICAgID4gKiBUZXJtaW5vbG9neSBjb3VsZCBhbHNvIGluY2x1ZGUgd2hh
dCBTUlAgc3RhbmQgZm9yLg0KICAgID4NCiAgICA+ICogU2VjdGlvbiAzLiBXaGVuIGludHJvZHVj
aW5nIFNSUCwgaXQgd291bGQgaGF2ZSBiZWVuIGhlbHBmdWwgdG8gdGhlIHJlYWRlciB0bw0KICAg
ID4gcmVmZXJlbmNlIHNlY3Rpb24gNy4yIG9mIFJGQzgyMzEuDQogICAgPg0KICAgID4gKiBTZWN0
aW9uIDMuICJQQ0Ugc2V0cyB0aGUgQyBGbGFnIHRvIDEgdG8gaW5kaWNhdGUgdGhhdCwgaXQgd2lz
aGVzIiAtLSByZW1vdmUNCiAgICA+ICIsIg0KICAgID4NCiAgICA+ICogU2VjdGlvbiAzLiAiTVVT
VCBiZSBpZ25vcmVkIG9uIHJlY2VpcHQiIC0tICJNVVNUIGJlIGlnbm9yZWQgb24gcmVjZXB0aW9u
Ig0KICAgID4NCiAgICANCiAgICBJIGhhdmUgbm90aWNlZCAnb24gcmVjZWlwdCcgaW4gbWFueSBv
ZiBvdXIgZG9jdW1lbnRzLiBXZSBzaG91bGQgbGVhdmUNCiAgICB0aGlzIG9uZSBmb3IgdGhlIFJG
Qy1FRElUT1IgbWF5YmUuLi4NCiAgICANCiAgICA+ICogU2VjdGlvbiA0LiBXaGVuIGludHJvZHVj
aW5nIHRoZSBEIGZsYWcsIGl0IHdvdWxkIGhhdmUgYmVlbiBoZWxwZnVsIHRvIHRoZQ0KICAgID4g
cmVhZGVyIHRvIHJlZmVyZW5jZSBzZWN0aW9uIDcuMyBvZiBSRkM4MjMxLg0KICAgID4NCiAgICA+
ICogU2VjdGlvbiA0LiAiTm90ZSB0aGF0LCB0aGUgUENVcGQgbWVzc2FnZSB3aXRoIEMgRmxhZyBz
ZXQgaXMgcmVjZWl2ZWQiIC0tDQogICAgPiAiTm90ZSB0aGF0LCBpZiB0aGUgUENVcGQgbWVzc2Fn
ZSB3aXRoIEMgRmxhZyBzZXQgaXMgcmVjZWl2ZWQiDQogICAgPg0KICAgID4gKFBsZWFzZSBrZWVw
IG15IGFkZHJlc3MgaW4gdGhlIFRvOiBmaWVsZCBpZiB5b3Ugd2FudCB0byBtYWtlIHN1cmUgSSBz
ZWUgYW55DQogICAgPiByZXNwb25zZSB0byB0aGlzIHRocmVhZCkNCiAgICA+DQogICAgPiBUaGFu
a3MsDQogICAgPiBGcmFuY2VzY2ENCiAgICA+DQogICAgDQogICAgVGhhbmtzIGFnYWluIGZvciB5
b3VyIHJldmlldy4NCiAgICANCiAgICBSZWdhcmRzLA0KICAgIERocnV2DQogICAgDQoNCg==


From nobody Fri Sep 13 02:13:55 2019
Return-Path: <dhruv.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50E1E120233; Fri, 13 Sep 2019 02:13:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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, 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 bA1Gf8L6lZJp; Fri, 13 Sep 2019 02:13:52 -0700 (PDT)
Received: from mail-io1-xd2e.google.com (mail-io1-xd2e.google.com [IPv6:2607:f8b0:4864:20::d2e]) (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 E544B1200B9; Fri, 13 Sep 2019 02:13:51 -0700 (PDT)
Received: by mail-io1-xd2e.google.com with SMTP id j4so61506548iog.11; Fri, 13 Sep 2019 02:13:51 -0700 (PDT)
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:content-transfer-encoding; bh=jCyDBLQwhKhjMIGjeBtG7vBR2GaC8wAFRylbo+mf2qk=; b=g+DAw4jgh8FjoOdeLeTqSi5r29NflRyPhzT+LKK/SI/jZ6Um7cJtlGJhlDLWWwsgbU URKKp2GoDPnH7+Kx8QL6dCuojbAnouYysAaEwYq0B4+ZNQIDNkc1SUv2pSFSso7oUir9 A1cJYo7wR/19JoN7Mx863ejuDA75n0VoZplVJxWb3LJZ5uWVqbHU8L54ZyVVsg6Xtxdw SHP9qNrlL+xqnIdV3hk7/CrcatEV/uXlFpwMb3i+/m+1GB4rjrF66I4KDQs1shlstrCY DRb8PRWlzjfrNfga3HLUxSWjIpeQgHdpXgSb2AbrycJ8kcR5VdCuf7Qx/QPztOkP+Xvn IPRw==
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:content-transfer-encoding; bh=jCyDBLQwhKhjMIGjeBtG7vBR2GaC8wAFRylbo+mf2qk=; b=YQyy5A1k608xb1jbO9PAeU2ilGwL6iZf3jaMDM7GPd8LV6gxS7McIAVLewttfDJRyw V5Wkh+Fnw5CMuRAZuMeASvRia+UBUeylQk7eHvR7bqMdLCs4rqrrYSYDvZzbQEFeqID1 AoZM0BncNiejTvk46gZMmmPSJIQoRqxDZfpdMAv+SIhbIfpxy0tFF/E2azfI69YAXH73 B8TnYCl6zZoojODEa/GGtyhwaI+BR6adu1TFJiJmgffP7hUgdDOOzsVaOsDLyCN55Il2 E374ZJTbfB8KCsT/ikUxGIHHX+YMr78WpYGRnEje0pEKOxxFy4fV43IE5GkvJ5VtkDdD i5IQ==
X-Gm-Message-State: APjAAAVr6uRvs3blfbpiZIChIvirKOzbnR/BanzPV7jFV/Dwcvz3SNkn zdguxGR9dGTqSNSVj/F+5ZMtu0YHRGCe0NE+10o=
X-Google-Smtp-Source: APXvYqw+2+tAVnr2h7s0BpDnb8B3knnwZfYBvsVfMtNddIi4w9dCZREAALHng+zpW9xHpQ822AIeCjcm5q8f4krp7ZI=
X-Received: by 2002:a6b:6f0c:: with SMTP id k12mr10451236ioc.1.1568366030934;  Fri, 13 Sep 2019 02:13:50 -0700 (PDT)
MIME-Version: 1.0
References: <156804768952.28211.12510339549643163890.idtracker@ietfa.amsl.com>
In-Reply-To: <156804768952.28211.12510339549643163890.idtracker@ietfa.amsl.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Fri, 13 Sep 2019 14:43:14 +0530
Message-ID: <CAB75xn62+7eJ62j5NizG=Jcmbpoj3JvDbkS_QyLNj8QbzBp86w@mail.gmail.com>
To: =?UTF-8?Q?Mirja_K=C3=BChlewind?= <ietf@kuehlewind.net>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pce-stateful-pce-auto-bandwidth@ietf.org,  Adrian Farrel <adrian@olddog.co.uk>, pce-chairs <pce-chairs@ietf.org>, pce@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/zArGEsaBl26cYpavJixt5P-nZ3U>
Subject: Re: [Pce]  =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft-i?= =?utf-8?q?etf-pce-stateful-pce-auto-bandwidth-11=3A_=28with_COMMENT=29?=
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Sep 2019 09:13:54 -0000

Hi Mirja,

On Mon, Sep 9, 2019 at 10:18 PM Mirja K=C3=BChlewind via Datatracker
<noreply@ietf.org> wrote:
>
> Mirja K=C3=BChlewind has entered the following ballot position for
> draft-ietf-pce-stateful-pce-auto-bandwidth-11: No Objection
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Thanks for quickly addressing the TSV-ART review (and thanks to David for=
 this
> very clear and well explained review)! I would have preferred to actually=
 see a
> normative requirement as original proposed by David ("sample interval SHO=
ULD
> NOT be less than 1 minute") in section 5.2.1. Also I would have expected =
the
> proposed new text to show up somewhere in section 4 (maybe even as a new
> subsection).
>
>

Thanks for your review, as well as to David for TSV-ART review.

Regarding normative - as there could be different transport protocol
(with different congestion techniques), I feel providing a clear
warning to the reader about changing the default is better than using
1 min. I thought in some scenario the issue could be seen even if set
to 2 mins! And with the help of David we have consensuses on the
current text.

I have added text in section 4 and 5.2.1, with reference to section
6.6 in the working copy.

Diff: https://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=3Ddraft-ietf-p=
ce-stateful-pce-auto-bandwidth-11&url2=3Dhttps://raw.githubusercontent.com/=
dhruvdhody/ietf/master/draft-ietf-pce-stateful-pce-auto-bandwidth-12.txt

Thanks!
Dhruv


From nobody Fri Sep 13 04:35:39 2019
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 61845120046; Fri, 13 Sep 2019 04:35:30 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: pce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.101.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: pce@ietf.org
Message-ID: <156837453030.31946.1839178312362431398@ietfa.amsl.com>
Date: Fri, 13 Sep 2019 04:35:30 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/jvAcPESH2udOSTHHLEcoAo93yMs>
Subject: [Pce] I-D Action: draft-ietf-pce-lsp-control-request-09.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Sep 2019 11:35:31 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Path Computation Element WG of the IETF.

        Title           : Ability for a Stateful Path Computation Element (PCE) to request and obtain control of a Label Switched Path (LSP)
        Authors         : Aswatnarayan Raghuram
                          Al Goddard
                          Jay Karthik
                          Siva Sivabalan
                          Mahendra Singh Negi
	Filename        : draft-ietf-pce-lsp-control-request-09.txt
	Pages           : 12
	Date            : 2019-09-13

Abstract:
   A Stateful Path Computation Element (PCE) retains information about
   the placement of Multiprotocol Label Switching (MPLS) Traffic
   Engineering Label Switched Paths (TE LSPs).  When a PCE has stateful
   control over LSPs it may send indications to LSP head-ends to modify
   the attributes (especially the paths) of the LSPs.  A Path
   Computation Client (PCC) has set up LSPs under local configuration
   may delegate control of those LSPs to a stateful PCE.

   There are use-cases in which a stateful PCE may wish to obtain
   control of locally configured LSPs of which it is aware but that have
   not been delegated to the PCE.

   This document describes an extension to the Path Computation Element
   communication Protocol (PCEP) to enable a PCE to make such requests.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pce-lsp-control-request/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-pce-lsp-control-request-09
https://datatracker.ietf.org/doc/html/draft-ietf-pce-lsp-control-request-09

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-pce-lsp-control-request-09


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Sat Sep 14 12:28:56 2019
Return-Path: <noreply@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CA4112001E; Sat, 14 Sep 2019 12:28:47 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Barry Leiba via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-pce-stateful-hpce@ietf.org, Adrian Farrel <adrian@olddog.co.uk>, pce-chairs@ietf.org, adrian@olddog.co.uk, pce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.101.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Barry Leiba <barryleiba@computer.org>
Message-ID: <156848932743.2904.14662217533512732107.idtracker@ietfa.amsl.com>
Date: Sat, 14 Sep 2019 12:28:47 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/642eR3iGJ6OM6Qi2aYs6Pa40shM>
Subject: [Pce] Barry Leiba's No Objection on draft-ietf-pce-stateful-hpce-13: (with COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Sep 2019 19:28:48 -0000

Barry Leiba has entered the following ballot position for
draft-ietf-pce-stateful-hpce-13: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-hpce/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks for this document.  I have only editorial suggestions (albeit, a lot of
them).  There's no need to reply in any detail; just please consider adopting
these suggestions.  Thanks.

— Abstract —

   computing new traffic engineered LSPs, and for associated and

Need a hyphen in “traffic-engineered”.

— Section 1.1 —

   This document presents general considerations for stateful PCEs, and
   not Stateless PCEs, in the hierarchical PCE architecture.  In
   particular, the behavior changes and additions to the existing
   stateful PCE mechanisms (including PCE-initiated LSP setup and active
   PCE usage) in the context of networks using the H-PCE architecture.

The second “sentence” is not a complete sentence.  One way to fix that is by
changing “In particular,” to “It focuses on”.

   stitching Per Domain LSPs.

Throughout, “Per-Domain” needs a hyphen.

— Section 1.2 —

In the title, “Use Cases” should *not* be hyphenated (it’s a noun, and not
being used as a modifier).  There’s also an instance of this in Section 3.

   As per [RFC6805], in the hierarchical PCE architecture, a P-PCE

The second comma doesn’t belong.

   It could also be a change in topology at the P-PCE
   such as inter-domain link status change.

You could take that extra comma and put it here, after “P-PCE”.

   Additionally a per-domain stitched LSP

And then make a copy of that comma and put it after “Additionally”.

   setup, whereas Section 3.3.1 describe the per-domain stitching.

“describes”

— Section 1.2.1 —

   support the function of multi domain coordination via hierarchy,

Hyphenate “multi-domain”, or make it one word (“multidomain”).

   Virtual Network (VN) requirements before requesting for the VN to be
   provisioned.

That sounds odd using “for” and “to be”.  It should be “…requesting that the VN
be provisioned.”

   P-PCE and C-PCEs. When the CNC requests for VN provisioning, the MDSC

Remove “for”.

   decompose this request into multiple inter-domain LSP provisioning

“decomposes”

— Section 1.2.2 —

   In case of a stateful P-PCE, the stateful P-PCE has to be aware of

You don’t have to say “stateful P-PCE” twice.  You can either remove the word
“stateful” the second time, or (better, I think) simply remove the first clause
and say, “A stateful P-PCE has to…”

   For example, a domain diverse path from another LSP.

That’s not a sentence; please make it one or merge it into an adjacent sentence
(I can’t figure out the right way to do that from the text you have).

   The other LSP could be
   an associated LSP (such as protection) or an unrelated LSP whose

I don’t understand the use of “protection” here; can you clarify?

— Section 1.2.3 —

   Similarly, a P-PCE could also request for delegation if it needs to

Remove “for”.

— Section 3 —

   All PCE types herein (i.e., EC-EP or EP-EC) are assumed to

It should be “and”, not “or”, and I suggest removing the “i.e.” and just saying
“(EC-EP and EP-EC)”.

   A number of interactions are expected in the Hierarchical Stateful
   PCE architecture, these include:

This is called a “comma splice”.  Make it a period instead (and have “These”
start a new sentence).  Alternatively, change “these include” to “including”.

   Note that this hierarchy is recursive and thus a Label Switching
   Router (LSR), as a PCC could delegate the control to a PCE, which may
   delegate to its parent, which may further delegate it to its parent
   (if it exist or needed). Similarly update operations could also be
   applied recursively.

This has a number of problems, so let me just fix it here:

NEW
   Note that this hierarchy is recursive, so a Label Switching Router
   (LSR), as a PCC, could delegate control to a PCE, which may in turn
   delegate to its parent, which may further delegate to its parent
   (if it exists). Similarly, update operations can also be applied
   recursively.
END

   an Open message indicates the support for stateful H-PCE operations
   as described in this document.

Remove “as”.

   procedures to minimise computational loops.

“minimize” — if you use British spelling you need to be consistent about it,
and you’re otherwise using American spelling throughout the document.

— Section 3.1 —

   It then sends computation requests to the C-
   PCEs responsible for each of the domains on the candidate domain

I think it’s better not to allow “C-PCE” (and other such terms) to be
hyphen-split across lines.

   A local policy at
   C-PCE may dictate which LSPs to be reported to the P-PCE.

“to be” is not right here.  I’d make it “are” (or “should be”).

   State synchronization mechanism as described in [RFC8231] and
   [RFC8232] are applicable

“mechanisms”

   We use the sample hierarchical domain topology example from [RFC6805]

I’d remove “sample”, because “example” covers it.  Or remove “example”… either
way.

   following additional steps are added for stateful PCE to be executed
   at the end:

Comma after “PCE”, please.

— Section 3.2 —

   As per [RFC8051], Delegation is an operation to grant a PCE,
   temporary rights

Remove the comma after “PCE”.

   The C-PCE may further choose to delegate to P-PCE based
   on a local policy.

To any P-PCE?  Or “to its P-PCE”?

   The PCRpt message with "D" (delegate) flag is
   sent from C-PCE to P-PCE.

‘with the “D” (delegate) flag’ (add ‘the’)

   For LSP delegated to the P-PCE via the child PCE,
   the P-PCE can use the same PCUpd message to request change to the C-
   PCE (the Ingress domain PCE), the PCE further propagates the update
   request to the PCC.

Again, multiple issues:

NEW
   For an LSP delegated to a P-PCE via the child PCE, the P-PCE
   can use the same PCUpd message to request a change to the C-PCE
   (the Ingress domain PCE).  The PCE further propagates the update
   request to the PCC.
END

— Section 3.3 —

   In case of inter-domain LSP in
   Hierarchical PCE architecture, the initiation operations can be
   carried out at the P-PCE.  In which case after P-PCE finishes the E2E
   path computation, it can send the PCInitiate message to the C-PCE

There are articles missing here.  I think it should be “an inter-domain LSP”
and “after the P-PCE finishes”.

   The following steps are performed, for PCE initiated operations,

Remove the first comma and hyphenate “PCE-initiated”.

— Section 3.3.1 —

   operation is possible, where multiple intra-domain LSPs are initiated
   in each domain which are further stitched to form an E2E LSP.

Needs a comma after “each domain”.

   The following steps are performed, for the Per Domain stitched LSP

Remove the comma.

   Note that each per-domain LSP can be setup in parallel.

“set up”, two words.

— Section 5.1 —

   If a parent PCE receives report from an unauthorized child

“a report”

   All mechanism as described in
   [RFC8231] and [RFC8281] continue to apply.

“mechanisms”

— Section 5.2 —

   The PCEP YANG module
   [I-D.ietf-pce-pcep-yang] may be extended to include details for
   stateful H-PCE deployment and operation, exact attributes to be
   modeled is out of scope for this document.

Who will (or may) extend it, and when might that happen?
And change the comma to a period and capitalize “Exact” (another comma splice).

— Section 6.3 —

   Along with the confidentiality during path
   computation, the child PCE could also conceal the path information, a
   C-PCE may replace a path segment with a path-key [RFC5520],
   effectively hiding the content of a segment of a path.

Combination of problems:

NEW
   Along with maintaining confidentiality during path
   computation, the child PCE could also conceal the path information.
   A C-PCE may replace a path segment with a path-key [RFC5520],
   effectively hiding the content of a segment of a path.
END



From nobody Sat Sep 14 14:53:22 2019
Return-Path: <noreply@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CC6C01200E9; Sat, 14 Sep 2019 14:53:13 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Barry Leiba via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-pce-stateful-path-protection@ietf.org, Julien Meuric <julien.meuric@orange.com>, pce-chairs@ietf.org, julien.meuric@orange.com, pce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.101.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Barry Leiba <barryleiba@computer.org>
Message-ID: <156849799383.3020.16398829686379997035.idtracker@ietfa.amsl.com>
Date: Sat, 14 Sep 2019 14:53:13 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/b6xLkNFgBSmaO27qyK8m_QtrS3I>
Subject: [Pce] Barry Leiba's No Objection on draft-ietf-pce-stateful-path-protection-10: (with COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Sep 2019 21:53:14 -0000

Barry Leiba has entered the following ballot position for
draft-ietf-pce-stateful-path-protection-10: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-path-protection/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks for this document.  I have only editorial suggestions.  There's no need
to reply in any detail; just please consider adopting these suggestions. 
Thanks.

— Abstract —

   Multiprotocol Label Switching Traffic
   Engineering Label Switched Paths (MPLS LSP)

Shouldn’t that be “(MPLS-TE LSPs)”?

— Section 1 —

   [RFC5440] describes PCEP for communication between a Path Computation
   Client (PCC) and a PCE or between a pair of PCEs as per [RFC4655].  A
   PCE computes paths for MPLS-TE LSPs based on various constraints and
   optimization criteria.

Even though you expanded some of these acronyms in the Abstract, they have to
be expanded again in the Introduction, because the Abstract and the document
itself each has to stand separately.

That said, “MPLS-TE” and “PCE” are in the RFC Editor’s list of common acronyms
that don’t need expansion, so you can expand them or not, as you please.  But
“PCEP” and “LSP” do need expansion here.

You should also be consistent in using “MPLS-TE” (with the hyphen), so please
check the instances of “MPLS TE” without the hyphen, and change them.  The RFC
Editor will flag this anyway, and it saves time during final editing and AUTH48
if you fix it now.

   It includes
   mechanisms to effect LSP state synchronization between PCCs and PCEs,
   delegation of control of LSPs to PCEs, and PCE control of timing and
   sequence of path computations within and across PCEP sessions and
   focuses on a model where LSPs are configured on the PCC and control
   over them is delegated to the PCE.

This is a really long sentence, and can do with being split in two.  I suggest
changing “sessions and” to “sessions.  Stateful PCE”.

   Furthermore, a mechanism to
   dynamically instantiate LSPs on a PCC based on the requests from a
   stateful PCE or a controller using stateful PCE, is specified in
   [RFC8281].

This reads oddly in passive voice, and you have a clear subject to use.  So I
suggest:

NEW
   Furthermore, [RFC8281] specifies a mechanism to
   dynamically instantiate LSPs on a PCC based on the requests from a
   stateful PCE or a controller using stateful PCE.
END

      computes the path for the protection LSP and update the PCC with

“updates”

   Note that protection LSP can be established (signaled) prior to the
   failure (in which case the LSP is said to be in standby mode
   [RFC4427] or a Primary LSP [RFC4872]) or post failure of the
   corresponding working LSP according to the operator choice/policy
   (known as secondary LSP [RFC4872]).

“a protection LSP”

I suggest changing “post failure” to “after failure”, as it reads better.

I’m not sure about the antecedent to “according to the operator choice/policy”.
 I think you mean that the establishment can be prior to failure or after
failure, according to operator choice or policy, is that right?  In that case,
the sentence isn’t worded well.  May I suggest this?:

NEW
   Note that a protection LSP can be established (signaled) before
   the failure (in which case the LSP is said to be in standby mode
   [RFC4427] or a Primary LSP [RFC4872]) or after failure of the
   corresponding working LSP (known as secondary LSP [RFC4872]).
   Whether to establish it before or after failure is according
   to operator choice or policy.
END

   [I-D.ietf-pce-association-group] introduces a generic mechanism to
   create a grouping of LSPs which can then be used to define
   associations between a set of LSPs that is equally applicable to
   stateful PCE (active and passive modes) and stateless PCE.

When I first read this I thought “that is equally applicable” applied to the
set of LSPs.  I think you mean it to apply to the generic mechanism — that is,
the generic mechanism is equally applicable.  Assuming that’s right (note
inserted comma and split sentences):

NEW
   [I-D.ietf-pce-association-group] introduces a generic mechanism to
   create a grouping of LSPs, which can then be used to define
   associations between a set of LSPs.  The mechanism is equally
   applicable to stateful PCE (active and passive modes) and stateless
   PCE.
END

— Section 3.2 —

      Protecting (P): 1 bit - This bit is as defined in Section 14.1 of
      [RFC4872] to indicate if the LSP is working or protection LSP.

At a minimum, make it “a working or protection LSP” (add the article).
Better still, “a working (0) or protection (1) LSP.”  I know it says that in
RFC 4872, but I think it makes sense to include that here.

      Secondary (S): 1 bit - This bit is as defined in Section 14.1 of
      [RFC4872] to indicate if the LSP is primary or secondary LSP.  The
      S flag is ignored if the P flag is not set.

Similarly, add the article “a”, and also consider “a primary (0) or secondary
(1) LSP.”

   If the TLV is missing, it is considered that the LSP is the working
   LSP (i.e. as if P bit is unset).

Is this really “the working LSP”, or should it be “a working LSP”?

— Section 4 —

   An LSP is associated with other LSPs with which they interact by
   adding them to a common association group via the ASSOCIATION object.

The number disagreement here is confusing, so I’m not sure what you mean to
say.  I think you mean that the other LSPs are added to the group, in which
case change “they interact” to “it interacts”.

— Section 4.2 —

   A PCC can associate a set of LSPs under its control for path
   protection purpose.

“purposes”

   PCC reports the change in association to PCE(s) via Path Computation
   Report (PCRpt) message.

Either “a Path Computation Report (PCRpt) message” or “Path Computation Report
(PCRpt) messages”.

   It is expected that both working and protection LSP are delegated

“LSPs”

— Section 4.5 —

   When the protection type is set to 1+1 or 1:N with N=1, there MUST be
…
   When the protection type is set to 1:N with N>1, there MUST be

This is a style thing, so take it or leave it as you please — it’s not wrong
the way it’s written.  It’s just that the “1:N with N=1” and “1:N with N>1”
distinction isn’t necessary, and I think it’s distracting and invites
uncertainty.  If you just made these like this:

NEW
   When the protection type is set to 1+1, there MUST be
…
   When the protection type is set to 1:N, there MUST be
END

…it would be equally correct, but also simpler and, I think, less likely to be
confusing.

— Section 5 —

   association of one LSP to another LSP across different RSVP - Traffic
   Engineering (RSVP-TE) sessions

Is it typical to have that hyphen there in the first line?  Isn’t it more
typical to write “RSVP Traffic Engineering (RSVP-TE)” without the extra hyphen?

   The information in the PPAG TLV in PCEP as received from the
   PCE, is used to trigger

Remove the comma.



From nobody Sat Sep 14 22:00:42 2019
Return-Path: <dhruv.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A7D31200B8; Sat, 14 Sep 2019 22:00:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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, 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 PYyWhvkCVtyR; Sat, 14 Sep 2019 22:00:29 -0700 (PDT)
Received: from mail-io1-xd2a.google.com (mail-io1-xd2a.google.com [IPv6:2607:f8b0:4864:20::d2a]) (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 A3F36120048; Sat, 14 Sep 2019 22:00:29 -0700 (PDT)
Received: by mail-io1-xd2a.google.com with SMTP id r26so71265848ioh.8; Sat, 14 Sep 2019 22:00:29 -0700 (PDT)
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:content-transfer-encoding; bh=dmleub1J4fVUvNmzB3InUWouigBUCsT6MRcyJ3zDLzI=; b=Mc0Mr8/ldSAJCr/rw2ALSSwEHh1gyVRPiLXRM5QyZJy3aH5JLVHrfqEjshgyBfjFjZ sQeBAktnHidpfqxP6P9OQXeCtSJxRaHoXvQf6DHFE9I1qaE7RNLUDoxjuh5HOiUnZJPD BrJA6cZB2WqYOzxCEZTMiQeh+rhN0ZTd2W26up+jFvxdah1FHiIwj30TvdwhNTfJCYRh D6nbTqVF2nmz811oBdZ8RZliKcyk9BhM+HWREV8GlWKNnyzEISnQO1g7khgdO6S5ibm0 5lQSAzUJdT2tzLI5rnhVu/cSPZNKYfX6gTZxXAHhu4ODvB/q1Bn6SKb91gA2XG1WQrCP nKMw==
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:content-transfer-encoding; bh=dmleub1J4fVUvNmzB3InUWouigBUCsT6MRcyJ3zDLzI=; b=PmS/ap6HQmGcVMVyu2P5gSQx8ioounSmXRClI6eO+cIU5FT66zi95isP7LwwENtdta UD/I+H1tzbb0q8WlCvG4C4XkItVUFLRpZbyOHF0nAVqCQIt3/9KSnkKTZmMTpdZzuxGE 9bKx3EJFHXvHRh1tF/yCPNpgxpI2LVz8XWRrRpRcBK35VGGqSNXyzHpu8JZYG+LIoA2T rB+KJR9bRHjp7TgNAQJ/Oq3aOenpV9n15xi+L/Mf8aiI7SiGJEK3ro/TInM7o/RNg1nW QXFIJJl+yMUSEln6IPwKG0vxiQVQ2Xb2jhblRGkD3PMI2UlYE8PVZhDk3lIJCv3NvkhG ZXLA==
X-Gm-Message-State: APjAAAXtEM5ZNCot5W+7xowVcv3QDILpi45wCHJ3pJ3SsYWyh8So2WFW UNu1jbMRhrepkHVHhYuhXDHBuVPVxsHfnKZrfqbQGQZj
X-Google-Smtp-Source: APXvYqxtlrSJdU84PjPxbrc7nAZZC4S+go8J+gUzhSIYaQ/RUm6MGY1jVkOFKRAVPAPVvVxubC2xn2YcK0Fpa8S0/MY=
X-Received: by 2002:a02:1ac5:: with SMTP id 188mr8113045jai.71.1568523628471;  Sat, 14 Sep 2019 22:00:28 -0700 (PDT)
MIME-Version: 1.0
References: <156848932743.2904.14662217533512732107.idtracker@ietfa.amsl.com>
In-Reply-To: <156848932743.2904.14662217533512732107.idtracker@ietfa.amsl.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Sun, 15 Sep 2019 10:29:51 +0530
Message-ID: <CAB75xn5FSnCq4XF+n0HH_MLH9sjSGiH1_=N2xaZqLfzqbLUk4g@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pce-stateful-hpce@ietf.org,  Adrian Farrel <adrian@olddog.co.uk>, pce-chairs <pce-chairs@ietf.org>, pce@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/fbGOIW6JcsRoj7oAqV7P-N_1fLk>
Subject: Re: [Pce] Barry Leiba's No Objection on draft-ietf-pce-stateful-hpce-13: (with COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Sep 2019 05:00:33 -0000

Hi Barry,

Thanks for your detailed review. The working copy is updated with your
suggestions.

Diff: https://tools.ietf.org/rfcdiff?url1=3Ddraft-ietf-pce-stateful-hpce-13=
&url2=3Dhttps://raw.githubusercontent.com/dhruvdhody/ietf/master/draft-ietf=
-pce-stateful-hpce-14.txt

Thanks!
Dhruv

On Sun, Sep 15, 2019 at 12:58 AM Barry Leiba via Datatracker
<noreply@ietf.org> wrote:
>
> Barry Leiba has entered the following ballot position for
> draft-ietf-pce-stateful-hpce-13: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-hpce/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Thanks for this document.  I have only editorial suggestions (albeit, a l=
ot of
> them).  There's no need to reply in any detail; just please consider adop=
ting
> these suggestions.  Thanks.
>
> =E2=80=94 Abstract =E2=80=94
>
>    computing new traffic engineered LSPs, and for associated and
>
> Need a hyphen in =E2=80=9Ctraffic-engineered=E2=80=9D.
>
> =E2=80=94 Section 1.1 =E2=80=94
>
>    This document presents general considerations for stateful PCEs, and
>    not Stateless PCEs, in the hierarchical PCE architecture.  In
>    particular, the behavior changes and additions to the existing
>    stateful PCE mechanisms (including PCE-initiated LSP setup and active
>    PCE usage) in the context of networks using the H-PCE architecture.
>
> The second =E2=80=9Csentence=E2=80=9D is not a complete sentence.  One wa=
y to fix that is by
> changing =E2=80=9CIn particular,=E2=80=9D to =E2=80=9CIt focuses on=E2=80=
=9D.
>
>    stitching Per Domain LSPs.
>
> Throughout, =E2=80=9CPer-Domain=E2=80=9D needs a hyphen.
>
> =E2=80=94 Section 1.2 =E2=80=94
>
> In the title, =E2=80=9CUse Cases=E2=80=9D should *not* be hyphenated (it=
=E2=80=99s a noun, and not
> being used as a modifier).  There=E2=80=99s also an instance of this in S=
ection 3.
>
>    As per [RFC6805], in the hierarchical PCE architecture, a P-PCE
>
> The second comma doesn=E2=80=99t belong.
>
>    It could also be a change in topology at the P-PCE
>    such as inter-domain link status change.
>
> You could take that extra comma and put it here, after =E2=80=9CP-PCE=E2=
=80=9D.
>
>    Additionally a per-domain stitched LSP
>
> And then make a copy of that comma and put it after =E2=80=9CAdditionally=
=E2=80=9D.
>
>    setup, whereas Section 3.3.1 describe the per-domain stitching.
>
> =E2=80=9Cdescribes=E2=80=9D
>
> =E2=80=94 Section 1.2.1 =E2=80=94
>
>    support the function of multi domain coordination via hierarchy,
>
> Hyphenate =E2=80=9Cmulti-domain=E2=80=9D, or make it one word (=E2=80=9Cm=
ultidomain=E2=80=9D).
>
>    Virtual Network (VN) requirements before requesting for the VN to be
>    provisioned.
>
> That sounds odd using =E2=80=9Cfor=E2=80=9D and =E2=80=9Cto be=E2=80=9D. =
 It should be =E2=80=9C=E2=80=A6requesting that the VN
> be provisioned.=E2=80=9D
>
>    P-PCE and C-PCEs. When the CNC requests for VN provisioning, the MDSC
>
> Remove =E2=80=9Cfor=E2=80=9D.
>
>    decompose this request into multiple inter-domain LSP provisioning
>
> =E2=80=9Cdecomposes=E2=80=9D
>
> =E2=80=94 Section 1.2.2 =E2=80=94
>
>    In case of a stateful P-PCE, the stateful P-PCE has to be aware of
>
> You don=E2=80=99t have to say =E2=80=9Cstateful P-PCE=E2=80=9D twice.  Yo=
u can either remove the word
> =E2=80=9Cstateful=E2=80=9D the second time, or (better, I think) simply r=
emove the first clause
> and say, =E2=80=9CA stateful P-PCE has to=E2=80=A6=E2=80=9D
>
>    For example, a domain diverse path from another LSP.
>
> That=E2=80=99s not a sentence; please make it one or merge it into an adj=
acent sentence
> (I can=E2=80=99t figure out the right way to do that from the text you ha=
ve).
>
>    The other LSP could be
>    an associated LSP (such as protection) or an unrelated LSP whose
>
> I don=E2=80=99t understand the use of =E2=80=9Cprotection=E2=80=9D here; =
can you clarify?
>
> =E2=80=94 Section 1.2.3 =E2=80=94
>
>    Similarly, a P-PCE could also request for delegation if it needs to
>
> Remove =E2=80=9Cfor=E2=80=9D.
>
> =E2=80=94 Section 3 =E2=80=94
>
>    All PCE types herein (i.e., EC-EP or EP-EC) are assumed to
>
> It should be =E2=80=9Cand=E2=80=9D, not =E2=80=9Cor=E2=80=9D, and I sugge=
st removing the =E2=80=9Ci.e.=E2=80=9D and just saying
> =E2=80=9C(EC-EP and EP-EC)=E2=80=9D.
>
>    A number of interactions are expected in the Hierarchical Stateful
>    PCE architecture, these include:
>
> This is called a =E2=80=9Ccomma splice=E2=80=9D.  Make it a period instea=
d (and have =E2=80=9CThese=E2=80=9D
> start a new sentence).  Alternatively, change =E2=80=9Cthese include=E2=
=80=9D to =E2=80=9Cincluding=E2=80=9D.
>
>    Note that this hierarchy is recursive and thus a Label Switching
>    Router (LSR), as a PCC could delegate the control to a PCE, which may
>    delegate to its parent, which may further delegate it to its parent
>    (if it exist or needed). Similarly update operations could also be
>    applied recursively.
>
> This has a number of problems, so let me just fix it here:
>
> NEW
>    Note that this hierarchy is recursive, so a Label Switching Router
>    (LSR), as a PCC, could delegate control to a PCE, which may in turn
>    delegate to its parent, which may further delegate to its parent
>    (if it exists). Similarly, update operations can also be applied
>    recursively.
> END
>
>    an Open message indicates the support for stateful H-PCE operations
>    as described in this document.
>
> Remove =E2=80=9Cas=E2=80=9D.
>
>    procedures to minimise computational loops.
>
> =E2=80=9Cminimize=E2=80=9D =E2=80=94 if you use British spelling you need=
 to be consistent about it,
> and you=E2=80=99re otherwise using American spelling throughout the docum=
ent.
>
> =E2=80=94 Section 3.1 =E2=80=94
>
>    It then sends computation requests to the C-
>    PCEs responsible for each of the domains on the candidate domain
>
> I think it=E2=80=99s better not to allow =E2=80=9CC-PCE=E2=80=9D (and oth=
er such terms) to be
> hyphen-split across lines.
>
>    A local policy at
>    C-PCE may dictate which LSPs to be reported to the P-PCE.
>
> =E2=80=9Cto be=E2=80=9D is not right here.  I=E2=80=99d make it =E2=80=9C=
are=E2=80=9D (or =E2=80=9Cshould be=E2=80=9D).
>
>    State synchronization mechanism as described in [RFC8231] and
>    [RFC8232] are applicable
>
> =E2=80=9Cmechanisms=E2=80=9D
>
>    We use the sample hierarchical domain topology example from [RFC6805]
>
> I=E2=80=99d remove =E2=80=9Csample=E2=80=9D, because =E2=80=9Cexample=E2=
=80=9D covers it.  Or remove =E2=80=9Cexample=E2=80=9D=E2=80=A6 either
> way.
>
>    following additional steps are added for stateful PCE to be executed
>    at the end:
>
> Comma after =E2=80=9CPCE=E2=80=9D, please.
>
> =E2=80=94 Section 3.2 =E2=80=94
>
>    As per [RFC8051], Delegation is an operation to grant a PCE,
>    temporary rights
>
> Remove the comma after =E2=80=9CPCE=E2=80=9D.
>
>    The C-PCE may further choose to delegate to P-PCE based
>    on a local policy.
>
> To any P-PCE?  Or =E2=80=9Cto its P-PCE=E2=80=9D?
>
>    The PCRpt message with "D" (delegate) flag is
>    sent from C-PCE to P-PCE.
>
> =E2=80=98with the =E2=80=9CD=E2=80=9D (delegate) flag=E2=80=99 (add =E2=
=80=98the=E2=80=99)
>
>    For LSP delegated to the P-PCE via the child PCE,
>    the P-PCE can use the same PCUpd message to request change to the C-
>    PCE (the Ingress domain PCE), the PCE further propagates the update
>    request to the PCC.
>
> Again, multiple issues:
>
> NEW
>    For an LSP delegated to a P-PCE via the child PCE, the P-PCE
>    can use the same PCUpd message to request a change to the C-PCE
>    (the Ingress domain PCE).  The PCE further propagates the update
>    request to the PCC.
> END
>
> =E2=80=94 Section 3.3 =E2=80=94
>
>    In case of inter-domain LSP in
>    Hierarchical PCE architecture, the initiation operations can be
>    carried out at the P-PCE.  In which case after P-PCE finishes the E2E
>    path computation, it can send the PCInitiate message to the C-PCE
>
> There are articles missing here.  I think it should be =E2=80=9Can inter-=
domain LSP=E2=80=9D
> and =E2=80=9Cafter the P-PCE finishes=E2=80=9D.
>
>    The following steps are performed, for PCE initiated operations,
>
> Remove the first comma and hyphenate =E2=80=9CPCE-initiated=E2=80=9D.
>
> =E2=80=94 Section 3.3.1 =E2=80=94
>
>    operation is possible, where multiple intra-domain LSPs are initiated
>    in each domain which are further stitched to form an E2E LSP.
>
> Needs a comma after =E2=80=9Ceach domain=E2=80=9D.
>
>    The following steps are performed, for the Per Domain stitched LSP
>
> Remove the comma.
>
>    Note that each per-domain LSP can be setup in parallel.
>
> =E2=80=9Cset up=E2=80=9D, two words.
>
> =E2=80=94 Section 5.1 =E2=80=94
>
>    If a parent PCE receives report from an unauthorized child
>
> =E2=80=9Ca report=E2=80=9D
>
>    All mechanism as described in
>    [RFC8231] and [RFC8281] continue to apply.
>
> =E2=80=9Cmechanisms=E2=80=9D
>
> =E2=80=94 Section 5.2 =E2=80=94
>
>    The PCEP YANG module
>    [I-D.ietf-pce-pcep-yang] may be extended to include details for
>    stateful H-PCE deployment and operation, exact attributes to be
>    modeled is out of scope for this document.
>
> Who will (or may) extend it, and when might that happen?
> And change the comma to a period and capitalize =E2=80=9CExact=E2=80=9D (=
another comma splice).
>
> =E2=80=94 Section 6.3 =E2=80=94
>
>    Along with the confidentiality during path
>    computation, the child PCE could also conceal the path information, a
>    C-PCE may replace a path segment with a path-key [RFC5520],
>    effectively hiding the content of a segment of a path.
>
> Combination of problems:
>
> NEW
>    Along with maintaining confidentiality during path
>    computation, the child PCE could also conceal the path information.
>    A C-PCE may replace a path segment with a path-key [RFC5520],
>    effectively hiding the content of a segment of a path.
> END
>
>


From nobody Sat Sep 14 22:21:49 2019
Return-Path: <zhenghaomian@huawei.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C17E1200EC; Sat, 14 Sep 2019 22:21:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.631
X-Spam-Level: 
X-Spam-Status: No, score=-3.631 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, INVALID_MSGID=0.568, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EWTW_Tp0o_Xx; Sat, 14 Sep 2019 22:21:45 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99B03120048; Sat, 14 Sep 2019 22:21:45 -0700 (PDT)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id DB0F0FE7A71DC139D287; Sun, 15 Sep 2019 06:21:42 +0100 (IST)
Received: from DGGEML401-HUB.china.huawei.com (10.3.17.32) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.408.0; Sun, 15 Sep 2019 06:21:41 +0100
Received: from DGGEML511-MBX.china.huawei.com ([169.254.1.20]) by DGGEML401-HUB.china.huawei.com ([fe80::89ed:853e:30a9:2a79%31]) with mapi id 14.03.0439.000; Sun, 15 Sep 2019 13:21:34 +0800
From: Zhenghaomian <zhenghaomian@huawei.com>
To: Dhruv Dhody <dhruv.ietf@gmail.com>, pce <pce@ietf.org>
CC: pce-chairs <pce-chairs@ietf.org>
Thread-Topic: [Pce] WG LC for draft-farrel-pce-stateful-flags-01
Thread-Index: AQHVX17ThzZBq3yDakOMnM/OoYvsyKcsTCPk
Date: Sun, 15 Sep 2019 05:21:34 +0000
Message-ID: 5171A061-D94D-41DB-AA94-D6D5AE4809C2
References: <CAB75xn6YcL4wXggWTBhfwOp_go32XaHFjaV+oEV-hdE7XjFuyw@mail.gmail.com>
In-Reply-To: <CAB75xn6YcL4wXggWTBhfwOp_go32XaHFjaV+oEV-hdE7XjFuyw@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_5171A061D94D41DBAA94D6D5AE4809C2_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/x1aCEFmaE1UXbtNp1yqETy9-S5g>
Subject: Re: [Pce] WG LC for draft-farrel-pce-stateful-flags-01
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Sep 2019 05:21:48 -0000

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

DQpEZWFyIFdHLA0KDQpJIGhhdmUgcmVhZCB0aGlzIGRvY3VtZW50IGFuZCBiZWxpZXZlIGl0IGlz
IGhlbHBmdWwgdG8gaGF2ZSBhIHF1aWNrIHB1YmxpY2F0aW9uLg0KDQpUaGlzIGlzIGEgc21hbGwg
ZHJhZnQgd2l0aCB2ZXJ5IGZvY3VzZWQgcHJvYmxlbSBzdGF0ZW1lbnQgb24gUENFUCBmbGFnIHBy
b2Nlc3NpbmcgYW5kIGFsc28gY2xlYXIgdGFyZ2V0IGRvY3VtZW50cyB0byBiZSB1cGRhdGVkLiBX
aXRoIHRoZSBncm93aW5nIG51bWJlciBvZiBmbGFncyBpbiBQQ0VQIGl0IHdvdWxkIGJlIGhlbHBm
dWwgdG8gZ3VpZGUgdGhlIGltcGxlbWVudGF0aW9uIG9uIGEgc3RhbmRhcmQgd2F5IHRvIHByb2Nl
c3MgdW5rbm93biBmbGFncy4NCg0KTXkgMiBjZW50cywNCkhhb21pYW4NCg0KDQotLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0K6YOR5aW95qOJIFpoZW5n
IEhhb21pYW4NCk1vYmlsZTogKzg2LTEzMDY2OTc1MjA2PHRlbDorODYtMTMwNjY5NzUyMDY+DQpF
bWFpbDogemhlbmdoYW9taWFuQGh1YXdlaS5jb208bWFpbHRvOnpoZW5naGFvbWlhbkBodWF3ZWku
Y29tPg0K5Y+R5Lu25Lq677yaRGhydXYgRGhvZHkgPGRocnV2LmlldGZAZ21haWwuY29tPg0K5pS2
5Lu25Lq677yacGNlIDxwY2VAaWV0Zi5vcmc+DQrmioTigIPpgIHvvJpwY2UtY2hhaXJzIDxwY2Ut
Y2hhaXJzQGlldGYub3JnPg0K5pe24oCD6Ze077yaMjAxOS0wOC0zMSAwMjoxNDo1Ng0K5Li76aKY
W1BjZV0gV0cgTEMgZm9yIGRyYWZ0LWZhcnJlbC1wY2Utc3RhdGVmdWwtZmxhZ3MtMDENCg0KSGkg
V0csDQoNClRoaXMgZW1haWwgc3RhcnRzIGEgJ3dvcmtpbmcgZ3JvdXAgbGFzdCBjYWxsJyBmb3IN
CmRyYWZ0LWZhcnJlbC1wY2Utc3RhdGVmdWwtZmxhZ3MtMDEgWzFdLiBUaGlzIEktRCBpcyBmb2N1
c2VkIGFuZCBoYXMgYW4NCnVuY29udHJvdmVyc2lhbCBmaXggdG8gUkZDIDgyMzEsIHdlIGFyZSBt
b3ZpbmcgaXQgZGlyZWN0bHkgdG8gV0dMQy4gU2VlIFsyXQ0KZm9yIGNvbnRleHQuDQoNClBsZWFz
ZSBpbmRpY2F0ZSB5b3VyIHN1cHBvcnQgb3IgY29uY2VybiBmb3IgdGhpcyBkcmFmdC4NCg0KSWYg
eW91IGFyZSBvcHBvc2VkIHRvIHRoZSBwcm9ncmVzc2lvbiBvZiB0aGUgZHJhZnQsIHBsZWFzZSBh
cnRpY3VsYXRlIHlvdXINCmNvbmNlcm4uDQoNCklmIHlvdSBzdXBwb3J0LCBwbGVhc2UgaW5kaWNh
dGUgdGhhdCB5b3UgaGF2ZSByZWFkIHRoZSBsYXRlc3QgdmVyc2lvbiBhbmQNCml0IGlzIHJlYWR5
IGZvciBwdWJsaWNhdGlvbi4NCg0KQXMgYWx3YXlzLCByZXZpZXcgY29tbWVudHMgYW5kIG5pdHMg
YXJlIG1vc3Qgd2VsY29tZS4NCg0KVGhlIFdHIExDIHdpbGwgZW5kIG9uIDE2dGggU2VwdGVtYmVy
IDIwMTkuDQoNClRoYW5rcywNClBDRSBDaGFpcnMNCg0KWzFdIGh0dHBzOi8vZGF0YXRyYWNrZXIu
aWV0Zi5vcmcvZG9jL2RyYWZ0LWZhcnJlbC1wY2Utc3RhdGVmdWwtZmxhZ3MvDQpbMl0gaHR0cHM6
Ly9tYWlsYXJjaGl2ZS5pZXRmLm9yZy9hcmNoL21zZy9wY2UvdFRrSktPMzR4VEQwQ1k0OElKQ2s1
RmptaUo0DQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
DQpQY2UgbWFpbGluZyBsaXN0DQpQY2VAaWV0Zi5vcmcNCmh0dHBzOi8vd3d3LmlldGYub3JnL21h
aWxtYW4vbGlzdGluZm8vcGNlDQo=

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

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRvciIgY29udGVu
dD0iTWljcm9zb2Z0IEV4Y2hhbmdlIFNlcnZlciI+DQo8IS0tIGNvbnZlcnRlZCBmcm9tIHRleHQg
LS0+PHN0eWxlPjwhLS0gLkVtYWlsUXVvdGUgeyBtYXJnaW4tbGVmdDogMXB0OyBwYWRkaW5nLWxl
ZnQ6IDRwdDsgYm9yZGVyLWxlZnQ6ICM4MDAwMDAgMnB4IHNvbGlkOyB9IC0tPjwvc3R5bGU+DQo8
L2hlYWQ+DQo8Ym9keT4NCjxzdHlsZSB0eXBlPSJ0ZXh0L2NzcyI+DQo8IS0tDQotLT4NCjwvc3R5
bGU+DQo8ZGl2Pg0KPGRpdj48YnI+DQpEZWFyIFdHLDxicj4NCjxicj4NCkkgaGF2ZSByZWFkIHRo
aXMgZG9jdW1lbnQgYW5kIGJlbGlldmUgaXQgaXMgaGVscGZ1bCB0byBoYXZlIGEgcXVpY2sgcHVi
bGljYXRpb24uPGJyPg0KPGJyPg0KVGhpcyBpcyBhIHNtYWxsIGRyYWZ0IHdpdGggdmVyeSBmb2N1
c2VkIHByb2JsZW0gc3RhdGVtZW50IG9uIFBDRVAgZmxhZyBwcm9jZXNzaW5nIGFuZCBhbHNvIGNs
ZWFyIHRhcmdldCBkb2N1bWVudHMgdG8gYmUgdXBkYXRlZC4gV2l0aCB0aGUgZ3Jvd2luZyBudW1i
ZXIgb2YgZmxhZ3MgaW4gUENFUCBpdCB3b3VsZCBiZSBoZWxwZnVsIHRvIGd1aWRlIHRoZSBpbXBs
ZW1lbnRhdGlvbiBvbiBhIHN0YW5kYXJkIHdheSB0byBwcm9jZXNzIHVua25vd24gZmxhZ3MuPGJy
Pg0KPGJyPg0KTXkgMiBjZW50cyw8YnI+DQpIYW9taWFuPGJyPg0KPGJyPg0KPGJyPg0KPC9kaXY+
DQo8ZGl2PjwvZGl2Pg0KPGRpdj4tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLTxicj4NCumDkeWlveajiSBaaGVuZyBIYW9taWFuPGJyPg0KTW9iaWxlOiA8
YSBocmVmPSJ0ZWw6JiM0Mzs4Ni0xMzA2Njk3NTIwNiI+JiM0Mzs4Ni0xMzA2Njk3NTIwNjwvYT48
YnI+DQpFbWFpbDogPGEgaHJlZj0ibWFpbHRvOnpoZW5naGFvbWlhbkBodWF3ZWkuY29tIj56aGVu
Z2hhb21pYW5AaHVhd2VpLmNvbTwvYT48L2Rpdj4NCjxkaXYgbmFtZT0ieF9BbnlPZmZpY2UtQmFj
a2dyb3VuZC1JbWFnZSIgc3R5bGU9ImJvcmRlci10b3A6MXB4IHNvbGlkICNCNUM0REY7IHBhZGRp
bmc6OHB4Ij4NCjxkaXYgc3R5bGU9IndvcmQtYnJlYWs6YnJlYWstYWxsIj48Yj7lj5Hku7bkurrv
vJo8L2I+RGhydXYgRGhvZHkgJmx0O2RocnV2LmlldGZAZ21haWwuY29tJmd0OzwvZGl2Pg0KPGRp
diBzdHlsZT0id29yZC1icmVhazpicmVhay1hbGwiPjxiPuaUtuS7tuS6uu+8mjwvYj5wY2UgJmx0
O3BjZUBpZXRmLm9yZyZndDs8L2Rpdj4NCjxkaXYgc3R5bGU9IndvcmQtYnJlYWs6YnJlYWstYWxs
Ij48Yj7mioTigIPpgIHvvJo8L2I+cGNlLWNoYWlycyAmbHQ7cGNlLWNoYWlyc0BpZXRmLm9yZyZn
dDs8L2Rpdj4NCjxkaXYgc3R5bGU9IndvcmQtYnJlYWs6YnJlYWstYWxsIj48Yj7ml7bigIPpl7Tv
vJo8L2I+MjAxOS0wOC0zMSAwMjoxNDo1NjwvZGl2Pg0KPGRpdiBzdHlsZT0id29yZC1icmVhazpi
cmVhay1hbGwiPjxiPuS4u+mimDwvYj5bUGNlXSBXRyBMQyBmb3IgZHJhZnQtZmFycmVsLXBjZS1z
dGF0ZWZ1bC1mbGFncy0wMTwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+
DQo8Zm9udCBzaXplPSIyIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwcHQ7Ij4NCjxkaXYgY2xh
c3M9IlBsYWluVGV4dCI+SGkgV0csPGJyPg0KPGJyPg0KVGhpcyBlbWFpbCBzdGFydHMgYSAnd29y
a2luZyBncm91cCBsYXN0IGNhbGwnIGZvcjxicj4NCmRyYWZ0LWZhcnJlbC1wY2Utc3RhdGVmdWwt
ZmxhZ3MtMDEgWzFdLiBUaGlzIEktRCBpcyBmb2N1c2VkIGFuZCBoYXMgYW48YnI+DQp1bmNvbnRy
b3ZlcnNpYWwgZml4IHRvIFJGQyA4MjMxLCB3ZSBhcmUgbW92aW5nIGl0IGRpcmVjdGx5IHRvIFdH
TEMuIFNlZSBbMl08YnI+DQpmb3IgY29udGV4dC48YnI+DQo8YnI+DQpQbGVhc2UgaW5kaWNhdGUg
eW91ciBzdXBwb3J0IG9yIGNvbmNlcm4gZm9yIHRoaXMgZHJhZnQuPGJyPg0KPGJyPg0KSWYgeW91
IGFyZSBvcHBvc2VkIHRvIHRoZSBwcm9ncmVzc2lvbiBvZiB0aGUgZHJhZnQsIHBsZWFzZSBhcnRp
Y3VsYXRlIHlvdXI8YnI+DQpjb25jZXJuLjxicj4NCjxicj4NCklmIHlvdSBzdXBwb3J0LCBwbGVh
c2UgaW5kaWNhdGUgdGhhdCB5b3UgaGF2ZSByZWFkIHRoZSBsYXRlc3QgdmVyc2lvbiBhbmQ8YnI+
DQppdCBpcyByZWFkeSBmb3IgcHVibGljYXRpb24uPGJyPg0KPGJyPg0KQXMgYWx3YXlzLCByZXZp
ZXcgY29tbWVudHMgYW5kIG5pdHMgYXJlIG1vc3Qgd2VsY29tZS48YnI+DQo8YnI+DQpUaGUgV0cg
TEMgd2lsbCBlbmQgb24gMTZ0aCBTZXB0ZW1iZXIgMjAxOS48YnI+DQo8YnI+DQpUaGFua3MsPGJy
Pg0KUENFIENoYWlyczxicj4NCjxicj4NClsxXSA8YSBocmVmPSJodHRwczovL2RhdGF0cmFja2Vy
LmlldGYub3JnL2RvYy9kcmFmdC1mYXJyZWwtcGNlLXN0YXRlZnVsLWZsYWdzLyI+aHR0cHM6Ly9k
YXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtZmFycmVsLXBjZS1zdGF0ZWZ1bC1mbGFncy88
L2E+PGJyPg0KWzJdIDxhIGhyZWY9Imh0dHBzOi8vbWFpbGFyY2hpdmUuaWV0Zi5vcmcvYXJjaC9t
c2cvcGNlL3RUa0pLTzM0eFREMENZNDhJSkNrNUZqbWlKNCI+DQpodHRwczovL21haWxhcmNoaXZl
LmlldGYub3JnL2FyY2gvbXNnL3BjZS90VGtKS08zNHhURDBDWTQ4SUpDazVGam1pSjQ8L2E+PGJy
Pg0KPGJyPg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188
YnI+DQpQY2UgbWFpbGluZyBsaXN0PGJyPg0KUGNlQGlldGYub3JnPGJyPg0KPGEgaHJlZj0iaHR0
cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9wY2UiPmh0dHBzOi8vd3d3LmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vcGNlPC9hPjxicj4NCjwvZGl2Pg0KPC9zcGFuPjwvZm9udD4N
CjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_5171A061D94D41DBAA94D6D5AE4809C2_--


From nobody Sun Sep 15 00:41:24 2019
Return-Path: <khasanov.boris@huawei.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 067E3120013; Sun, 15 Sep 2019 00:41:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jP0OXFd8XGMe; Sun, 15 Sep 2019 00:41:18 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C22FB120019; Sun, 15 Sep 2019 00:41:18 -0700 (PDT)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id AD46F860E323FD4DF96E; Sun, 15 Sep 2019 08:41:16 +0100 (IST)
Received: from LHREML505-MBS.china.huawei.com ([169.254.1.193]) by lhreml704-cah.china.huawei.com ([10.201.108.45]) with mapi id 14.03.0415.000;  Sun, 15 Sep 2019 08:41:11 +0100
From: Khasanov Boris <khasanov.boris@huawei.com>
To: Dhruv Dhody <dhruv.ietf@gmail.com>, "pce@ietf.org" <pce@ietf.org>
CC: pce-chairs <pce-chairs@ietf.org>
Thread-Topic: [Pce] WG LC for draft-farrel-pce-stateful-flags-01
Thread-Index: AQHVX17SrmPyz7rzZEqN2l1daOivb6cscUOA
Date: Sun, 15 Sep 2019 07:41:11 +0000
Message-ID: <C7794D4A32C7D046B93DBCF0FA202C182E839BB4@lhreml505-mbs.china.huawei.com>
References: <CAB75xn6YcL4wXggWTBhfwOp_go32XaHFjaV+oEV-hdE7XjFuyw@mail.gmail.com>
In-Reply-To: <CAB75xn6YcL4wXggWTBhfwOp_go32XaHFjaV+oEV-hdE7XjFuyw@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.160.92]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/4CcBBnoGNuZn399iBwTW6PQxto0>
Subject: Re: [Pce] WG LC for draft-farrel-pce-stateful-flags-01
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Sep 2019 07:41:22 -0000

Hi all,

I have read  draft-farrel-pce-stateful-flags-01 and think it is ready for p=
ublication.
As it was mentioned, it is small but important since it closes possible int=
eroperability issues of handling PCEP flags in SRP  object between differen=
t implementations.

SY,
Boris=20


-----Original Message-----
From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of Dhruv Dhody
Sent: Friday, August 30, 2019 9:14 PM
To: pce@ietf.org
Cc: pce-chairs <pce-chairs@ietf.org>
Subject: [Pce] WG LC for draft-farrel-pce-stateful-flags-01

Hi WG,

This email starts a 'working group last call' for
draft-farrel-pce-stateful-flags-01 [1]. This I-D is focused and has an unco=
ntroversial fix to RFC 8231, we are moving it directly to WGLC. See [2] for=
 context.

Please indicate your support or concern for this draft.

If you are opposed to the progression of the draft, please articulate your =
concern.

If you support, please indicate that you have read the latest version and i=
t is ready for publication.

As always, review comments and nits are most welcome.

The WG LC will end on 16th September 2019.

Thanks,
PCE Chairs

[1] https://datatracker.ietf.org/doc/draft-farrel-pce-stateful-flags/
[2] https://mailarchive.ietf.org/arch/msg/pce/tTkJKO34xTD0CY48IJCk5FjmiJ4

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


From nobody Sun Sep 15 05:42:37 2019
Return-Path: <barryleiba@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 916811200E0; Sun, 15 Sep 2019 05:42:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.922
X-Spam-Level: 
X-Spam-Status: No, score=-1.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.026, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WZ0aTyFWIDux; Sun, 15 Sep 2019 05:42:25 -0700 (PDT)
Received: from mail-io1-f67.google.com (mail-io1-f67.google.com [209.85.166.67]) (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 73DAA120046; Sun, 15 Sep 2019 05:42:25 -0700 (PDT)
Received: by mail-io1-f67.google.com with SMTP id d17so50678943ios.13; Sun, 15 Sep 2019 05:42:25 -0700 (PDT)
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:content-transfer-encoding; bh=+Lt0pMQUXOONS1Yow+E0kdflHmguTmXbN3/p0wB+JPM=; b=QGNflEOv40lrPvxDuxc9MeUNGK1rc6oD1bAVxXufo95gWzHSUBBRyBClm9ObOUW/A7 pdedb6V7kHrwmeLAmZucfvlXW58U/QUFIhgXnvwBSJ9H8ueuJudpLpVRaD2K2PlnA4Nq 24uCpa4yyEGKgdBpDFNg3iCO/Ndq/9TaVg/UW/+ZvwCAM0uymc8wiCb7JUJHxbIsRyQs Km7Ao+xcSjADJ691RyU4hluVtyWK/JRUDwKaMo+DC+LnGZ2iErIdUlcNneB5fTgxQfFf xxsANXfywUIRI34gPpEwermp7q282OUznfnCxCqXHkYcB1PRhdzoiyOrlXozFDpANKAa ZfAQ==
X-Gm-Message-State: APjAAAWbZAGgtibaE1pXwsAGkUJ7dmdV+W4vTFVogVJ3X4W9fxCuuPEe QWG8vQCVZfdTODQ3EyVaprcxtb7NjkW5LHHtsA0=
X-Google-Smtp-Source: APXvYqz7xcmdfmm+m/zeUl5jbG5JqGjJ4pRZfQ97W9/ncrgk1J8ANOR3zp6C/tNEUX6wpSPw+1GsTL2lTAOK0pOkVMo=
X-Received: by 2002:a5d:9714:: with SMTP id h20mr9334552iol.294.1568551344417;  Sun, 15 Sep 2019 05:42:24 -0700 (PDT)
MIME-Version: 1.0
References: <156848932743.2904.14662217533512732107.idtracker@ietfa.amsl.com> <CAB75xn5FSnCq4XF+n0HH_MLH9sjSGiH1_=N2xaZqLfzqbLUk4g@mail.gmail.com>
In-Reply-To: <CAB75xn5FSnCq4XF+n0HH_MLH9sjSGiH1_=N2xaZqLfzqbLUk4g@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Sun, 15 Sep 2019 08:42:12 -0400
Message-ID: <CALaySJLbXbguNcCWG0RarF=xWpF3JNVkggtite3bgn7Axm+bEw@mail.gmail.com>
To: Dhruv Dhody <dhruv.ietf@gmail.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pce-stateful-hpce@ietf.org,  Adrian Farrel <adrian@olddog.co.uk>, pce-chairs <pce-chairs@ietf.org>, pce@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/vc_QKDYHVEqzSn1059s5V5qMnII>
Subject: Re: [Pce] Barry Leiba's No Objection on draft-ietf-pce-stateful-hpce-13: (with COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Sep 2019 12:42:29 -0000

Great!  Thank you, Dhruv.

Barry

On Sun, Sep 15, 2019 at 1:00 AM Dhruv Dhody <dhruv.ietf@gmail.com> wrote:
>
> Hi Barry,
>
> Thanks for your detailed review. The working copy is updated with your
> suggestions.
>
> Diff: https://tools.ietf.org/rfcdiff?url1=3Ddraft-ietf-pce-stateful-hpce-=
13&url2=3Dhttps://raw.githubusercontent.com/dhruvdhody/ietf/master/draft-ie=
tf-pce-stateful-hpce-14.txt
>
> Thanks!
> Dhruv
>
> On Sun, Sep 15, 2019 at 12:58 AM Barry Leiba via Datatracker
> <noreply@ietf.org> wrote:
> >
> > Barry Leiba has entered the following ballot position for
> > draft-ietf-pce-stateful-hpce-13: No Objection
> >
> > When responding, please keep the subject line intact and reply to all
> > email addresses included in the To and CC lines. (Feel free to cut this
> > introductory paragraph, however.)
> >
> >
> > Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.ht=
ml
> > for more information about IESG DISCUSS and COMMENT positions.
> >
> >
> > The document, along with other ballot positions, can be found here:
> > https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-hpce/
> >
> >
> >
> > ----------------------------------------------------------------------
> > COMMENT:
> > ----------------------------------------------------------------------
> >
> > Thanks for this document.  I have only editorial suggestions (albeit, a=
 lot of
> > them).  There's no need to reply in any detail; just please consider ad=
opting
> > these suggestions.  Thanks.
> >
> > =E2=80=94 Abstract =E2=80=94
> >
> >    computing new traffic engineered LSPs, and for associated and
> >
> > Need a hyphen in =E2=80=9Ctraffic-engineered=E2=80=9D.
> >
> > =E2=80=94 Section 1.1 =E2=80=94
> >
> >    This document presents general considerations for stateful PCEs, and
> >    not Stateless PCEs, in the hierarchical PCE architecture.  In
> >    particular, the behavior changes and additions to the existing
> >    stateful PCE mechanisms (including PCE-initiated LSP setup and activ=
e
> >    PCE usage) in the context of networks using the H-PCE architecture.
> >
> > The second =E2=80=9Csentence=E2=80=9D is not a complete sentence.  One =
way to fix that is by
> > changing =E2=80=9CIn particular,=E2=80=9D to =E2=80=9CIt focuses on=E2=
=80=9D.
> >
> >    stitching Per Domain LSPs.
> >
> > Throughout, =E2=80=9CPer-Domain=E2=80=9D needs a hyphen.
> >
> > =E2=80=94 Section 1.2 =E2=80=94
> >
> > In the title, =E2=80=9CUse Cases=E2=80=9D should *not* be hyphenated (i=
t=E2=80=99s a noun, and not
> > being used as a modifier).  There=E2=80=99s also an instance of this in=
 Section 3.
> >
> >    As per [RFC6805], in the hierarchical PCE architecture, a P-PCE
> >
> > The second comma doesn=E2=80=99t belong.
> >
> >    It could also be a change in topology at the P-PCE
> >    such as inter-domain link status change.
> >
> > You could take that extra comma and put it here, after =E2=80=9CP-PCE=
=E2=80=9D.
> >
> >    Additionally a per-domain stitched LSP
> >
> > And then make a copy of that comma and put it after =E2=80=9CAdditional=
ly=E2=80=9D.
> >
> >    setup, whereas Section 3.3.1 describe the per-domain stitching.
> >
> > =E2=80=9Cdescribes=E2=80=9D
> >
> > =E2=80=94 Section 1.2.1 =E2=80=94
> >
> >    support the function of multi domain coordination via hierarchy,
> >
> > Hyphenate =E2=80=9Cmulti-domain=E2=80=9D, or make it one word (=E2=80=
=9Cmultidomain=E2=80=9D).
> >
> >    Virtual Network (VN) requirements before requesting for the VN to be
> >    provisioned.
> >
> > That sounds odd using =E2=80=9Cfor=E2=80=9D and =E2=80=9Cto be=E2=80=9D=
.  It should be =E2=80=9C=E2=80=A6requesting that the VN
> > be provisioned.=E2=80=9D
> >
> >    P-PCE and C-PCEs. When the CNC requests for VN provisioning, the MDS=
C
> >
> > Remove =E2=80=9Cfor=E2=80=9D.
> >
> >    decompose this request into multiple inter-domain LSP provisioning
> >
> > =E2=80=9Cdecomposes=E2=80=9D
> >
> > =E2=80=94 Section 1.2.2 =E2=80=94
> >
> >    In case of a stateful P-PCE, the stateful P-PCE has to be aware of
> >
> > You don=E2=80=99t have to say =E2=80=9Cstateful P-PCE=E2=80=9D twice.  =
You can either remove the word
> > =E2=80=9Cstateful=E2=80=9D the second time, or (better, I think) simply=
 remove the first clause
> > and say, =E2=80=9CA stateful P-PCE has to=E2=80=A6=E2=80=9D
> >
> >    For example, a domain diverse path from another LSP.
> >
> > That=E2=80=99s not a sentence; please make it one or merge it into an a=
djacent sentence
> > (I can=E2=80=99t figure out the right way to do that from the text you =
have).
> >
> >    The other LSP could be
> >    an associated LSP (such as protection) or an unrelated LSP whose
> >
> > I don=E2=80=99t understand the use of =E2=80=9Cprotection=E2=80=9D here=
; can you clarify?
> >
> > =E2=80=94 Section 1.2.3 =E2=80=94
> >
> >    Similarly, a P-PCE could also request for delegation if it needs to
> >
> > Remove =E2=80=9Cfor=E2=80=9D.
> >
> > =E2=80=94 Section 3 =E2=80=94
> >
> >    All PCE types herein (i.e., EC-EP or EP-EC) are assumed to
> >
> > It should be =E2=80=9Cand=E2=80=9D, not =E2=80=9Cor=E2=80=9D, and I sug=
gest removing the =E2=80=9Ci.e.=E2=80=9D and just saying
> > =E2=80=9C(EC-EP and EP-EC)=E2=80=9D.
> >
> >    A number of interactions are expected in the Hierarchical Stateful
> >    PCE architecture, these include:
> >
> > This is called a =E2=80=9Ccomma splice=E2=80=9D.  Make it a period inst=
ead (and have =E2=80=9CThese=E2=80=9D
> > start a new sentence).  Alternatively, change =E2=80=9Cthese include=E2=
=80=9D to =E2=80=9Cincluding=E2=80=9D.
> >
> >    Note that this hierarchy is recursive and thus a Label Switching
> >    Router (LSR), as a PCC could delegate the control to a PCE, which ma=
y
> >    delegate to its parent, which may further delegate it to its parent
> >    (if it exist or needed). Similarly update operations could also be
> >    applied recursively.
> >
> > This has a number of problems, so let me just fix it here:
> >
> > NEW
> >    Note that this hierarchy is recursive, so a Label Switching Router
> >    (LSR), as a PCC, could delegate control to a PCE, which may in turn
> >    delegate to its parent, which may further delegate to its parent
> >    (if it exists). Similarly, update operations can also be applied
> >    recursively.
> > END
> >
> >    an Open message indicates the support for stateful H-PCE operations
> >    as described in this document.
> >
> > Remove =E2=80=9Cas=E2=80=9D.
> >
> >    procedures to minimise computational loops.
> >
> > =E2=80=9Cminimize=E2=80=9D =E2=80=94 if you use British spelling you ne=
ed to be consistent about it,
> > and you=E2=80=99re otherwise using American spelling throughout the doc=
ument.
> >
> > =E2=80=94 Section 3.1 =E2=80=94
> >
> >    It then sends computation requests to the C-
> >    PCEs responsible for each of the domains on the candidate domain
> >
> > I think it=E2=80=99s better not to allow =E2=80=9CC-PCE=E2=80=9D (and o=
ther such terms) to be
> > hyphen-split across lines.
> >
> >    A local policy at
> >    C-PCE may dictate which LSPs to be reported to the P-PCE.
> >
> > =E2=80=9Cto be=E2=80=9D is not right here.  I=E2=80=99d make it =E2=80=
=9Care=E2=80=9D (or =E2=80=9Cshould be=E2=80=9D).
> >
> >    State synchronization mechanism as described in [RFC8231] and
> >    [RFC8232] are applicable
> >
> > =E2=80=9Cmechanisms=E2=80=9D
> >
> >    We use the sample hierarchical domain topology example from [RFC6805=
]
> >
> > I=E2=80=99d remove =E2=80=9Csample=E2=80=9D, because =E2=80=9Cexample=
=E2=80=9D covers it.  Or remove =E2=80=9Cexample=E2=80=9D=E2=80=A6 either
> > way.
> >
> >    following additional steps are added for stateful PCE to be executed
> >    at the end:
> >
> > Comma after =E2=80=9CPCE=E2=80=9D, please.
> >
> > =E2=80=94 Section 3.2 =E2=80=94
> >
> >    As per [RFC8051], Delegation is an operation to grant a PCE,
> >    temporary rights
> >
> > Remove the comma after =E2=80=9CPCE=E2=80=9D.
> >
> >    The C-PCE may further choose to delegate to P-PCE based
> >    on a local policy.
> >
> > To any P-PCE?  Or =E2=80=9Cto its P-PCE=E2=80=9D?
> >
> >    The PCRpt message with "D" (delegate) flag is
> >    sent from C-PCE to P-PCE.
> >
> > =E2=80=98with the =E2=80=9CD=E2=80=9D (delegate) flag=E2=80=99 (add =E2=
=80=98the=E2=80=99)
> >
> >    For LSP delegated to the P-PCE via the child PCE,
> >    the P-PCE can use the same PCUpd message to request change to the C-
> >    PCE (the Ingress domain PCE), the PCE further propagates the update
> >    request to the PCC.
> >
> > Again, multiple issues:
> >
> > NEW
> >    For an LSP delegated to a P-PCE via the child PCE, the P-PCE
> >    can use the same PCUpd message to request a change to the C-PCE
> >    (the Ingress domain PCE).  The PCE further propagates the update
> >    request to the PCC.
> > END
> >
> > =E2=80=94 Section 3.3 =E2=80=94
> >
> >    In case of inter-domain LSP in
> >    Hierarchical PCE architecture, the initiation operations can be
> >    carried out at the P-PCE.  In which case after P-PCE finishes the E2=
E
> >    path computation, it can send the PCInitiate message to the C-PCE
> >
> > There are articles missing here.  I think it should be =E2=80=9Can inte=
r-domain LSP=E2=80=9D
> > and =E2=80=9Cafter the P-PCE finishes=E2=80=9D.
> >
> >    The following steps are performed, for PCE initiated operations,
> >
> > Remove the first comma and hyphenate =E2=80=9CPCE-initiated=E2=80=9D.
> >
> > =E2=80=94 Section 3.3.1 =E2=80=94
> >
> >    operation is possible, where multiple intra-domain LSPs are initiate=
d
> >    in each domain which are further stitched to form an E2E LSP.
> >
> > Needs a comma after =E2=80=9Ceach domain=E2=80=9D.
> >
> >    The following steps are performed, for the Per Domain stitched LSP
> >
> > Remove the comma.
> >
> >    Note that each per-domain LSP can be setup in parallel.
> >
> > =E2=80=9Cset up=E2=80=9D, two words.
> >
> > =E2=80=94 Section 5.1 =E2=80=94
> >
> >    If a parent PCE receives report from an unauthorized child
> >
> > =E2=80=9Ca report=E2=80=9D
> >
> >    All mechanism as described in
> >    [RFC8231] and [RFC8281] continue to apply.
> >
> > =E2=80=9Cmechanisms=E2=80=9D
> >
> > =E2=80=94 Section 5.2 =E2=80=94
> >
> >    The PCEP YANG module
> >    [I-D.ietf-pce-pcep-yang] may be extended to include details for
> >    stateful H-PCE deployment and operation, exact attributes to be
> >    modeled is out of scope for this document.
> >
> > Who will (or may) extend it, and when might that happen?
> > And change the comma to a period and capitalize =E2=80=9CExact=E2=80=9D=
 (another comma splice).
> >
> > =E2=80=94 Section 6.3 =E2=80=94
> >
> >    Along with the confidentiality during path
> >    computation, the child PCE could also conceal the path information, =
a
> >    C-PCE may replace a path segment with a path-key [RFC5520],
> >    effectively hiding the content of a segment of a path.
> >
> > Combination of problems:
> >
> > NEW
> >    Along with maintaining confidentiality during path
> >    computation, the child PCE could also conceal the path information.
> >    A C-PCE may replace a path segment with a path-key [RFC5520],
> >    effectively hiding the content of a segment of a path.
> > END
> >
> >


From nobody Mon Sep 16 01:42:32 2019
Return-Path: <xiong.quan@zte.com.cn>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BF1712002E; Mon, 16 Sep 2019 01:42:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.58
X-Spam-Level: 
X-Spam-Status: No, score=-2.58 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6IEa3lNbDV7u; Mon, 16 Sep 2019 01:42:28 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.217.80.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 952FE12003F; Mon, 16 Sep 2019 01:42:28 -0700 (PDT)
Received: from mxct.zte.com.cn (unknown [192.168.164.217]) by Forcepoint Email with ESMTPS id 7F7499747E0E7AAC4D96; Mon, 16 Sep 2019 16:42:26 +0800 (CST)
Received: from mse-fl2.zte.com.cn (unknown [10.30.14.239]) by Forcepoint Email with ESMTPS id 5E10DC0CE415935C5DF4; Mon, 16 Sep 2019 16:42:26 +0800 (CST)
Received: from njxapp05.zte.com.cn ([10.41.132.204]) by mse-fl2.zte.com.cn with SMTP id x8G8gA13077894; Mon, 16 Sep 2019 16:42:10 +0800 (GMT-8) (envelope-from xiong.quan@zte.com.cn)
Received: from mapi (njxapp05[null]) by mapi (Zmail) with MAPI id mid201; Mon, 16 Sep 2019 16:42:10 +0800 (CST)
Date: Mon, 16 Sep 2019 16:42:10 +0800 (CST)
X-Zmail-TransId: 2afd5d7f4ae2eeccff67
X-Mailer: Zmail v1.0
Message-ID: <201909161642099990442@zte.com.cn>
Mime-Version: 1.0
From: <xiong.quan@zte.com.cn>
To: <pce@ietf.org>
Cc: <pce-chairs@ietf.org>
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn x8G8gA13077894
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/Mdkt9knRNZOjHNZCTSKUwPIRmIM>
Subject: [Pce] =?utf-8?q?Comments_about_the_LSP_Object_Flag_field?=
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Sep 2019 08:42:31 -0000

--=====_001_next=====
Content-Type: multipart/related;
	boundary="=====_002_next====="


--=====_002_next=====
Content-Type: multipart/alternative;
	boundary="=====_003_next====="


--=====_003_next=====
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: base64

SGkgYWxsLA0KDQoNCg0KDQpBcyBkZWZpbmVkIGluIFtSRkM4MjMxXSwgdGhlIGxlbmd0aCBvZiBM
U1AgT2JqZWN0IEZsYWcgZmllbGQgaXMgMTIgYml0cyBhbmQgaXQgZGVmaW5lZCB0aGUgdmFsdWUg
ZnJvbSBiaXQgNSB0byBiaXQgMTEuICANCg0KVGhlIGJpdHMgZnJvbSAxIHRvIDMgYXJlIGRlZmlu
ZWQgaW4gW1JGQzg2MjNdIGFuZCB0aGUgYml0IHZhbHVlIDQgaXMgdXNlZCBpbiBbUkZDODI4MV0u
IFNvIGFsbCBiaXRzIG9mIHRoZSBmbGFnIGhhcyBiZWVuIG9jY3VwaWVkIGFzIHRoZSBmb2xsb3dp
bmcgc2hvd24uDQoNCg0KDQoNCg0KDQoNCg0KDQpJIG5vdGljZWQgbWFueSBvdGhlciBkcmFmdHMg
aGF2ZSBleHRlbmRlZCB0aGUgZmxhZywgZm9yIGV4YW1wbGUsIGRyYWZ0LWxpLXBjZS1zci1wYXRo
LXNlZ21lbnQgZGVmaW5lZCBhIG5ldyBQIGJpdC4NCg0KQnV0IG5vIHVudXNlZCBiaXQgY2FuIGJl
IGFzc2lnbmVkIGZvciBpdC4gU28gSSBwcm9wb2VzZSAgYSBuZXcgTFNQLUVYVEVOREVELUZMQUcg
VExWIGZvciBMU1Agb2JqZWN0IHRvIGV4dGVuZCB0aGUNCg0KIGxlbmd0aCBvZiB0aGUgZmxhZyBh
cyB0aGUgZm9sbG93aW5nIHNob3duLg0KDQogICAgICAgIDAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgMSAgICAgICAgICAgICAgICAgICAgICAgICAgICAyICAgICAgICAgICAgICAgICAgICAg
ICAgICAgMw0KDQogICAgICAgIDAgMSAyIDMgNCA1IDYgNyA4IDkgMCAxIDIgMyA0IDUgNiA3IDgg
OSAwIDEgMiAzIDQgNSA2IDcgOCA5IDAgMQ0KDQogICAgICAgKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSsNCg0KICAgICAgIHwg
ICAgICAgICAgICAgICAgICAgIFR5cGU9VEJEICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAg
ICAgIExlbmd0aCAgICAgICAgICAgICAgICAgICB8DQoNCiAgICAgICArLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKw0KDQogICAg
ICAgfCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIEV4dGVuZGVkIEZsYWcgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwNCg0KICAgICAgICstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
DQoNCg0KDQoNCldoYXQgaXMgeXB1ciBvcG5pb24/IERvIHlvdSBoYXZlIG90aGVyIHN1Z2dlc3Rp
b25zPw0KDQoNCg0KDQoNClRoYW5rcywNCg0KUXVhbg==


--=====_003_next=====
Content-Type: text/html ;
	charset="UTF-8"
Content-Transfer-Encoding: base64

PGRpdiBjbGFzcz0iemNvbnRlbnRSb3ciPjxkaXY+PGRpdiBjbGFzcz0iemNvbnRlbnRSb3ciPjxk
aXYgY2xhc3M9Inpjb250ZW50Um93Ij48cD48YnI+PC9wPjxwPkhpIGFsbCw8L3A+PHA+PGJyPjwv
cD48cD5BcyBkZWZpbmVkIGluIFtSRkM4MjMxXSwgdGhlIGxlbmd0aCBvZiBMU1AgT2JqZWN0IEZs
YWcgZmllbGQgaXMgMTIgYml0cyBhbmQgaXQgZGVmaW5lZCB0aGUgdmFsdWUgZnJvbSBiaXQgNSB0
byBiaXQgMTEuICZuYnNwOzwvcD48cD5UaGUgYml0cyBmcm9tIDEgdG8gMyBhcmUgZGVmaW5lZCBp
biBbUkZDODYyM10gYW5kIHRoZSBiaXQgdmFsdWUgNCBpcyB1c2VkIGluIFtSRkM4MjgxXS4gU28g
YWxsIGJpdHMgb2YgdGhlIGZsYWcgaGFzIGJlZW4gb2NjdXBpZWQmbmJzcDthcyB0aGUgZm9sbG93
aW5nIHNob3duLjwvcD48cD48YnI+PC9wPjxwPjxpbWcgc3JjPSJjaWQ6MDBjOTAwMDAxZjYxNjM0
ZTM5ZDE0NjcxMDAwMDEiIHN0eWxlPSJ3aGl0ZS1zcGFjZTogbm9ybWFsOyI+PC9wPjxwPjxicj48
L3A+PHA+SSBub3RpY2VkIG1hbnkgb3RoZXIgZHJhZnRzIGhhdmUgZXh0ZW5kZWQgdGhlIGZsYWcs
IGZvciBleGFtcGxlLCBkcmFmdC1saS1wY2Utc3ItcGF0aC1zZWdtZW50IGRlZmluZWQgYSBuZXcg
UCBiaXQuPC9wPjxwPkJ1dCBubyB1bnVzZWQgYml0IGNhbiBiZSBhc3NpZ25lZCBmb3IgaXQuIFNv
IEkgcHJvcG9lc2UgJm5ic3A7YSBuZXcgTFNQLUVYVEVOREVELUZMQUcgVExWIGZvciBMU1Agb2Jq
ZWN0IHRvIGV4dGVuZCB0aGU8L3A+PHA+Jm5ic3A7bGVuZ3RoIG9mIHRoZSBmbGFnIGFzIHRoZSBm
b2xsb3dpbmcgc2hvd24uPC9wPjxwPiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAwICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsxICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsyICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAz
PC9wPjxwPiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAwIDEgMiAzIDQgNSA2IDcgOCA5IDAg
MSAyIDMgNCA1IDYgNyA4IDkgMCAxIDIgMyA0IDUgNiA3IDggOSAwIDE8L3A+PHA+Jm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSs8L3A+PHA+Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i
c3A7fCAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDtUeXBlPVRCRCAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyB8ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO0xlbmd0aCAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyB8PC9wPjxwPiZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOystKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rPC9wPjxwPiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
O3wgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDtFeHRlbmRlZCBGbGFnICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgfDwv
cD48cD4mbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsrLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKzwvcD48cD48YnI+PC9wPjxw
PldoYXQgaXMgeXB1ciBvcG5pb24/IERvIHlvdSBoYXZlIG90aGVyIHN1Z2dlc3Rpb25zPzxicj48
L3A+PHA+PGJyPjwvcD48cD5UaGFua3MsPC9wPjxwPlF1YW48L3A+PHA+PGJyPjwvcD48L2Rpdj48
L2Rpdj48L2Rpdj48L2Rpdj4=


--=====_003_next=====--

--=====_002_next=====
Content-Type: image/other;
	 name="=?UTF-8?B?YmxvYi5wbmc=?="
Content-Disposition: inline;
	filename="=?UTF-8?B?YmxvYi5wbmc=?="
Content-Transfer-Encoding: base64
Content-ID: <00c900001f61634e39d1467100001>

iVBORw0KGgoAAAANSUhEUgAAAR0AAADSCAYAAAB3oxSuAAAgAElEQVR4Ae19z4/bRrbuJ8fxZBAM
JsEAfhLgaehvMLKgdlp5aWoxC2rnRXDR1wjuYlbS/AFDrmbxEPg1HrLwjlxc4LaMBzzAK+3EReC/
QfAYkGDgTpzJ5MUz+cGHU8UqFkskJbVEUt19GmiQrB+nTn1FHtU5ZH3VSZIkAf8xAowAI9AQAnca
aoebYQQYAUZAIMBGh28ERoARaBQBNjqNws2NMQKMABsdvgcYAUagUQTuVrX23+/+WZXNeYwAI8AI
lCLwu09+VZhXaXT+33dvCytxIiPACDAC2xD43Se/LyzC7lUhLJzICDACdSHARqcuZFkuI8AIFCJQ
6V4V1kgTXz07wygoKPHoS3z91WPcF1mv8OxshCCXVlDHSvrLX/5ipVRf/vGPf6wuUJJb3IdH+PLr
r/BYdqCkZn3JUqcDdHj7Ap9/9gVeTi7x+unDWhRtanxqUT4VWjz2APa6V9P7W8ic4PL1U9SDeJ1I
ZLKbGtcrGx2pqvVwvHqGs9EX+OzZg/Ibnh6K/3yAr7Y8ELsakn2ByiBWZ/k+iJvxszO8uXyNLSoq
Aa0fXz37HG/+0KyhbG586oQ3P/ZI798/vXDw1Q6/Om9fPAP97k6u0b2yDc0mxvVAo2N14aGDCYDg
1Ru8xUPcx0M8ff0aT1Ux41dYJVUdqwzKruBUyS/Ke/j0EpNghODZC/xBz9iKStaT9vDpa7zWgG1v
Q8+M/pCWvf8YX71+vL3iEUq0MT5HULtchLp/X8R4+1jN1suL39Scusf1uDGdV7Gw/I8eO4Z7dYaz
z1/gLV7hGU37aaSCEc7OnuHVllErMyxl6VvE7Zj9EA5Zzpdv8EbVIGN5doaz9P+ZqbiVJ/uqKgKw
843KZDDOzj7Hs2efC9mfv3gLlfZCvDik6Tvh9wzPPlftfw6ZR6I/T13cl/jiszNQfd3eRjub9UlL
kkH9evbC6KMYL6MPJadl41CWXiLmtJOt8VOwEm6ffSHuZgSjM5ypDJot6XslGyvqpBpbc7yz9HR8
TOxV289e4EXB+Evg0ntEtWnWx1ujnqHjFsTLxq8sfYu4jewDjY682TXIFOR59CX+XDg1fYinX3+J
R6QCxRt29H/tjtrXGz06WsIrvKEHnwZexUhev8bXXz5CMFI301u8+NMXeElxgNev8fpyArz8An/K
rEKursgPRtI4aD1f4tWDP+P169flU/qXr/Dgz6/x+vXX+PIRYS4N9v3HX4GaBMhNKK6vZ0JfU33S
H8JAqWdEqRG8eYCv0v5RH/7TNKyqUMHRHg/7uqDK6SbZP5oVY0/Y071Af+ReifiZcM8CPPrya4H1
5SQbq6zT+fHOj88lJi8pPGGBH7zBg69e47V4fl7iCz04RsyU7j/K1/XJ4HyGL15SrCnN27j3Mq3s
M3sc7Wu7/D7XBxodebPTzSz+Vad3mMXso6TqsDruU/fQsm/jF2J2NnFkiPC+8xiP8BIvYuMbJhro
s8/x4sHTnPGw6+JhPl/q9giPnS1R60ePIYvch/OYbvQAsXVfFvfzFWIRdHiqA+P3Hz+VLrAlQPfv
geznK2Fxi6XaqWpc1NHOP93rzR9NMhgqnmOPX+HYG517JcDOxvOhmDLbY5XlA+n46PFNZ9lBnPcC
Jo4MUN9/II8ifEFTJ8uzEK51agDfxnhBEzFd1wHdOi/JdTR0rjpV46mOVWX3yTvQ6FhN3X+Mp+KX
N50lWNmHXFLHq3zNQ2QX132IB4YtEFNomsKmLuLLN+R83cdj2WHyx8QMQrgqqUF484ZG/REePChu
4Sqp9/cxCm/f5G9es0F145ppB5w3Pz4HKKurqh/NS2GIKfmhOehpueKx10Ksk+w+OEtf72414OJH
S7pXsspuz8/bN/JGK9JZKyVCGSSbZj1W2EAXKj+pY1yPa3TKdT84RxkcdTxYYKkA9evzAKatEFNo
NaOjo3q1lc5eaKYnXR0KWUn358EDmpW8hLBPpe3tl7HTjaZEql9GdW0eHz5I425m4tXP1bio49Ul
tVHzIZ6mg6fGztSidOzNQvpcGbJ09l/lNqs6yj3X99dubyJ3+gESoYxMl13DGko1NZ7qqNIPOR7Z
6KgHVrkDlmpVD4FV1Ly0O2xfm2UPPdevQZ/KtxdySg0EqTuiA6/iR0YFeilQDjx8SjEXmtxIg2XX
VUFeEfDdR1EdY3mLWM6ZkXp7kIatTJiarj8zgs/pa14loKzqHun2eNjXe4hqr+jDp+mPRoBRGlOx
xy8/9puqSncqc71V4FiF+ApqpC8tXkB66/n7abO8lZK+bctcprQ+6X9fulNQrpoOSu/kl4uG7HG0
ry1tdr488JW5nEp+kWtugsvSV83qIRjhLKBfhO0WvayjlH4cX9Pug/yl0rFw8pO/Bj7/jHSWHSW/
X0506JOAS+BshM/OFAoUuEtftxbUFUF0LTwHXPnFoy/xID6jZtKgcfYRmnwwvhCu3Rf0q6ZenafS
6BX8Jc4w+uwMUkOrf+Wt7pRT//jspMZRCunPJYIRnjn0nVbV2Bc0SbNecTt8BnU7TC6r7/HN8al6
fuw2C+4/mjWls/DH8sbFKLtxdZ4tyb6uc1w7VXSlf/3rX21dGrnex6DsU7YR5Y/aiPF2otSQH7XB
nYTtg/k+ZXdqnAvVhsA+Y7VL2d//vnjB54Ezndr633DQuL5+3FTJdNPx381DoIlxPcmZzs0byqv2
6DRnOlftDde7XQiUzXTY6Nyu+4B7ywg0hkCZ0al0r/7r//zfxhTkhhgBRuBmIfAf//5vhR2qnOkU
1uBERoARYAQOQODI3+kcoAlXZQQYgVuBABudWzHM3ElG4HQQaMHorBGNOuh01H+AuCU84qCDTrDZ
+joaFaY3ouY6wqjTPCat9rkRYLmRU0GgMpBci5Lxc4wRYpV46AKgB38QDJFMnFqau3ZCux4ueXf5
azdsrPDuCDQ+04nnU7jeUBgcUtN5EsKNl1jvrjOXZAQYgWuMQMNGZ41lDDh9muMYf7MllsblSZ2m
7k5ELpdyCXMuWYxApYvjCJG2oJYradYTcpWL2aF1efLPdq/iwGg3Eq6pKkuzxFEUGe2bbQMoa0O0
ZOodYH5SoLMyNxmBho1OAZTdPhzEWOoHtaBM60lTRLhAkiRIViHc6SA1EmRUBojDlcxLVgjdGcbP
pQVZR+cYO4ssLzbqnY/hLBItMx4UxHHIaAxihCtZbtWPMJ7lwZiNlxiSXkmChT/D+DxKZ40xgp7d
hjJKlt6rPiJbcL4ZvmIEjoZA+0bnaF2pU5ALb5jOzrpDeK5qqwvvMsGlp2ZuXQyzTFloGqQzH1nW
DF1Ng9RAiDjOBHZUaz2PMPMnUOK73gS+alod/aGu5wyN3HiOqRviiRLa9XARAtF8DazniGY+Jplg
TIyqSjQfGYE6EGjf6KyXiOHA9rjq6Kwts9/X1sPOsq6r9RNvflIXq2fMGLreJVYhMO4pN0rNNMgA
rRBijJ5yzUZqhmI1nbvsw1bZ7fdzJdTFmvzYmSG/0wHpNlsWO7K7Y6Fa4CMjcDUEGjY6XfQdILZ9
KbeP4kfnap06tNZyOUPZw5yXLeMiveUkdaESrMK8ISPDI9yyDfdHznxk3gL+bIzzLBiUb+aqVy69
JUxdOHU0p1pXlcv1GIEDEGjY6ADkAsyiuX5bFT8fY+b09dusA/qyd9Xu0DPiM2n1OMBgarhTVVLF
LM1FqHyYdYRzY6ZjfwckZhOir9JYqYAwIGcwdoBd6qfcM4oLn2/EdMrUE67YbIw0vERRZRGEHpFh
Ey7iFAOtQIznht5lMjmdETgGAs1/p+MM4c8G6HXGqf4+FokKPByjS3vIoFjKChiR+6OruQhXlzqO
opOLTkScJEKv14HoDc0sFj5mgzniiQNnskI46qGjhWd9nazCfLv+AgIGM6BO+i2W6Cj5figC1cUO
kq2gA7sNN1zp+BO5d9C6+QhphrabYLshvmYE9kKAF3zuBVfbhWmGFKC/q1FsW11unxEoQKBx96pA
B04qQ0B8o2O8Sqc3Ui0F3ctU5HRGYF8EeKazL2INlxfLRKaq0T1cP1WFj4zAiSHARufEBoTVYQRu
OgKVgeT/fvfPm95/7h8jwAjUhMDvPvlVoWSe6RTCwomMACNQFwIcSK4LWZbLCDAChQiw0SmEhRMZ
AUagLgRaNTr0ZkZ/FFtXDyvkii+G1dqn3FGtkZIkY5rSwixTpLhFJdFpgQGworutZhHW4mvoVrVQ
jRuUI2Icv0fQ+Qadgv/cMK+/w6igTKfzzqAzIWa6b/OyRt/pL/C1BtG7rIydb7VTqUPwvRIpjmtT
budbzcqp7/Wd1vjlRB79ojWjQyAM9Kvgo/drd4H0JbBal6SP1hfJG2UW8DW9RdoUfVPTi+ClNBRC
5gIYdNo1rLsDUW9JZ2Kuxq+3rV2l+0QtYqxF8xefIkmM/8UdTAfZgyvldhCujDKi/Cf6C3bx0A+A
hSFn4fyEnmlY4m/Riz7AKi2z8n5GTxuP7xH0fsFE1V/dRTxQRo3yfoKj9bwHf/ovjKL3UjWSO+7o
tldhgkHaLuGfLE6DSqAFoyPXHQ1iH35+beSu98oJlHPwJHQxnSvmrRiB4L2xjJUzEQOtKSxOQHNW
YQ8EnF8hdH+BHuZtVdff4XwMhKvfaroRquJM7sGf/aTXwa2XCeDc0esNu/0OEP8iZkPr6EdM3TvZ
Aujub3CZKKP2sTBGmZ38GE/CDmbLn6Vmzm+RJFnb3eEHcGe/nNzqlhaMDjCkX5jLJxmw2wbzBPNp
Jbr+E9w1HhTljk6nE7HWLALR2JT96anvxqzIcAPItTPn2TSzGkWIiFw+dfsou1BWSVmpD7UxQhCk
zIiqDfE1tJKduZtUx2yDdMi6Vq4v1THdq1IZBbqa9cowrCf9Z5jDvLWN5S+YuR8U3Ad5Y2EaGZJp
GqHlMoHrfagN0tY2KwrEz3/CzL+bM4AVxRvLasHoOHBaWt9ZiOp0oB9a9fDmHu6iSusIwRTwh7Ij
grumdKU8rSCfoYTGhp5gDKa0EFROf6cGg2Ac9DaYB3O6zcZYDlNWQZp5DTqYm9eKJIz6MBsj6qcM
h6sQ8cA0JDNMY0/SYNDPqMVYmCwcjHvpcgzSN84oMxZORslRzpSYB5H4h2wZPdN4Gf0il2A2Ps/H
TPLiarsSsw7cQTrMaTsJxr18/EfZadN4VCpFM5LJL+il8aFzfIRk8jGA94LOF/gZ0ShrQ8nflPk9
no8T+EOqa/ylMaHBtIPwiZVnFGvrtAWj01ZXS9rdiNfk/XxRyzZMPTGHRjbNLZG9QzIR1UOx/5E7
ligGwRjzqUGbgS68C6JKnevgIODrB6JLREUb16YCNlPgTLIIpkVMsnybsRDOBAt/mrkZBmXGRqym
gilRNrXGPJrBn8jdQCjNmRCfkDkbzPolZopmN2o8nw6yB52CynKYM3dFNr0Z09n3PhBxn/ldHT+6
wHt0dEyHfh9+BC5U3OgeoGM6+c7Hwb8w9e9t3ofCJfsUyeoDRD0VD8rXbfOKjc4u6BuGScbijAcY
gHjgS3e0WGI5cyEI/qy3W+oXrJAwbBdGRZv8zL42+1aVRw++Qd0oXEfL0FLQX5CvqTjVQLleWaC8
nCnRVMTAw0w2z7foahY95nkWSL4naWH9D3WAeJd2bLepuM57zKP87ETEXqY/Ilp/JEju3PAjo92P
MfQTRPM0WJwKJcM1iO9iJWZIxS2h+yE8d7NuSenGktno7Am14MhxpxiY7kBV3MaM9wgu5IzJT/1C
FlKIHpuwft8dNwxDq97uaS5oMSMz3bpsJXw5U6ICeou7qYq1evwYk9VduOaboV30ce7Cn/1cEL97
L9wl/ZapQlafgsq5P+lyOf2PdGocfCPffl3+ZqfYj1lXC2nxhI3O3uCnbk6OXtTBRMQ9zDiJiLii
M5jmXAm7OUGmrlwmMRNSMhwMaXcHTf23RnQ+xky5YragrddTBIoOVcSkytkRxV5k2k0iwRnToeCD
NgyumOWlMxMRHFbTNwAZU6KpnCSvN9/oxcEAU7ckEG9WbfK8+xtc0Juh8fs94kn0Nok4sfOv2ePg
B4xndzDxyHB8hKHXQbw0Zi5GAJpmPRj/03ChKZit4krSeIkZTpHBoe+DzFfz6x8R6bpNglfdVuWC
z+qqNySX3IiC74XoGw41E9noqWIMHPcQ9NNy9Ou/igQboOJEpBgLBYgr4+bOBKtwJAjaqR1i91Ob
NGwwD9Lso1SpDS3zCW4Ib6lYDLdQZNiMhRQtUng4l1gsOwbzI8maiF/cbgVToqkMzYZyMohx8TKL
8Zhl2zzveh8hjH4QRqRvvIqu0qnrfYKkLz8O1OXcu1gl2ayEykwCih/9IItQvjIiFI9ZyY8Q5ftR
iiF9Iu8hYUSoyk8iCJ2TT/Wd32LlvTPyjLq6cPsnvOCz/TGoXwN6DR30T/LBrr/zRS3Qq/0elpOK
H5aiatc97UTuA57pXPcbifU/GIFf//obvDe8nYMFnqCA9foT/I8T0YuNzokMBKvRPAL0XdOUXNYf
Kh3g5hWroUWKt3UpjOCGNUjfTyS7V/vhxaUZAUbgQAQqZzrMHHggulydEbjFCDBz4C0efO46I3BK
CPB3Oqc0GqwLI3ALEGCjcwsGmbvICJwSAi0YHfl1q17RbXzd2jQwOXqFbayATSvXQnuER3s0Ek12
2KDgEF9QM3Ngk+gTa16Df6skdJG44SptU17T565t/C18JG21XVt/V2Hiwk00xFUN7VO2Ss61y5P3
XXbb/SPx8bcku047tHiXAO8SfXeu/p64+KYS21X4Tb5OkiQL/28J3L8n6q5PSK5xLer4/0gbJV3K
2rT1lNdu+IOsa+kr5BrtJAs/gRtmerQ0bg3PdLrwLk3ayi68iU/Llw0iqEZtLjfGCJQjwMyB5dgc
kNOw0TlA0xaqkrsRBIEk+VJuIH1KbrpiKl3oZ7qOAaJolLH9Ub1dmf5IVq4dtQiUMqRrEEQRRloP
tco7RtAbY4YZxj1Vx9SJ6CiMdKus7V7l3E+znwV9uZluGTMH1vHYtWx01oiCKUwCqTo6WSnT4o3J
028C0ymRbBO9qoeuzai3CuFqQisyBgPEoWLn6yMaG5SmpITBiLeqYvqz2zGZ+9LOTCPgQhDJrxAS
1YaITTiYkE5QCzotnRIqq1au22XzKF0Xdr+81se9YubA4+KppLVqdAS9JUJcqGXVSqsmjzZvjL3a
2aSSEHw4Bvl6dwhPkcuv54hmBrlX1wN5jvm/jBGviulvK3Mffc3uDVMuFUkVkW9HXW26s0OtsCpT
dDxddr8ibY+VxsyBx0KyWk57RicO0Bs7WNgPebW+jedusvoZbz46PdiTGVNBwSdjJtiMePZ1WraS
uS8tYzL9mU0UnQsOnNQV61UprCufLrufVrGGE2YOrAHUApGtGB3xEIi9gRQfcIFmp5gk4iySEkGy
6ZG7UpOi9gwsMQPwu7Yp4zm9JXEvZ0x/22tfB3a/7b24eglmDrw6dttrNm50KDgpZjiagHy7kqdS
Quz64IZ4ki5KFu6hCtsIVyvPzne+06xis3dVzH2bpStSBM+yQe6+jrCbTteE3a+i6wdnMXPgwRCW
CWjY6NAOB6TKVOx8mb0FUm9fytQ8jfSud4EQY8HyR7qf4wJE1C433aP4yQLOmNj5Ouj0lvCuOg0S
zH207YsiPxfTwnImQxMeYfzo7VUHwdLDhaDPTOWcAxdSYUmHaZZV+wamsgS7n5P1VWwZc+KusAnD
Mc4Fc6BLW87k6UerZAvmQLGza7azhKAXNZgHBXPg8odsW+HgjsUceMfY5vhH9NXmfYo5cCaZA/U2
yIqiVDAH/qy3tun0foan6lYp3XAeU1vUCLh45d5fQROa19gWi94HAYrLMXPgPogds2wltcUxG7r5
sih+Ys5I5KzOWXRvfteveQ+ZObDZAWSjczS8aUcIHx1io0tlEsn65c0npTsagk0LYubAphGX7bF7
1Q7u3CojcGsRqJzpMHPgrb0vuOOMwMEIMHPgwRCyAEaAETgGAg2/Mj+GyiyDEWAErjMCbHSu8+ix
7ozANUSgBaNjrl3qZNQPLYCXo27QNBEdGNtxA2J/cfWRXl5fe1/vXBfSelqWLUe1Z1JG5ATwRX0I
GPcgMwfWB3OJ5MaNThz0MHYW6VqgFcJ40C5Fpr3GaRUiHuQ5Z5yFXLeUJAv4U1vfCOfasiiU14jO
idfG/iPKCSVLHhf01e9GfbseX9eBAO3Pbu4Nny34/BRJ8imSxR1MB/bXyLQ/eJpPZcT/J3r/+XX0
DvJzLZX3KRbOT+ipr4apI/G36EUfYJXWX3k/oxd8n3bxewS9XzBRsld3EQ/eIVpTNuX9BGehZN+D
P/0XRlG6PSnJHXewUHLDBIO0XWeSIKGv0U/gr3GjIzo/UR+vyDU+s+XyBKBIVUiXBkRzGmUHk8Tc
79rBk9BFTl/HgxfP5bIC1Yv4OcaOj12G2BmKdRT5+koOH9tFgJkDa8G/caOT70WM5+MZ/KEyQvnc
63HVR9+ZYm6sXYrnU/jD4fVQn7WsQICZAyvAuXJWa0ZHcrwMMDVWbV+5F8esSLOUmQtvWLR8odhI
0mxFLvokRWj5Q0bWVa2aZE6ESRRWXYFzG0SAmQPrAbs1o0OrmInjZeVF6LUZTLXpSgcxwpXBDmjg
HgcDTP3F5mpvZwh/mrpY8RzTUiMiV39nq+vT+JZ2N43G+LRxBJg5sBnIWzM6qnvdoQd3FkGEUFRi
k0c7kJwUGxyamQl6h0ID4WDoSxdLulZl7uJmINkMZDbZbW5rE4EskHxPxuP8D3WAeLP0Zkq33wHi
X7bsbPIe8yiBP/xYC+gOP4A7/RHR+iP0HcANPzLa/RhDP0E0T4PFaS0KWAvKjEkmRwtUJ90P4bmb
dVV2W8fWjY7suIN+kTfTFipWu4J4LPKwquCTkS5WsIdrZTXClyeEADMH1jkYjRsdeoDN7UokCfkQ
ZXODOju/Xbb8nmMnAivhYk0xLeE93t4WlzgpBJg5sLbhaNzoOJMVvChl1+t00KMZRKHLUlufdxcs
dniQW8f01Md8dCyMQZGLZe7SsHszXPI0EWDmwHrGhakt6sGVpZ40Aswc2GY0o5La4qTvG1aOETgS
AswceCQgdxTDRmdHoLjYzUOAmQPbGVN2r9rBnVtlBG4tApUzHWYOvLX3BXecETgYAWYOPBhCFsAI
MALHQKDxV+bHUJplMAKMwPVFgI3O9R071pwRuJYItGt0BJte21sKGyxy6QeAzKl1Le/lPZQ2xvwE
mQPjINuSuNNRBF5Z93L5mvwryxdn8bfoGHmaJbPww1arbs2XLRqdMna9mnucE0+7cvYQeauUyTBB
IpgDLcrSXJ3DLsTgs1U7DMQj1T5F5kC9kFOz/yG3l7rIx72UsfBTLGAwBypcyOAMflFX4nirmQM1
EsRbAxeuTmj+RFFV5PYa73q4CF1Mg2jLauHm9eUWG0agBebArvcJksvfQH0x3PU+hI8ES0FXCiyX
Cdz+BxqIfr+D2fJnfS1mQYMEvt/Raad20tJMJ0ZA235feC3iscYyRiFroeD6USvKyQUcBQhGkpxd
TVL0dLVgLZYkKNskcxf0GLTnMHH4KEEWYbtKbhEYbloj0DxzoG665MQ2MrYRwpBmQZ/gSb9EwAkk
t2J01lGAOHzS8sryJZYzF/1dBmc2RZy6YLQ2VXPrJAXk6nGA3tjBIs0TZNjTQBBrkzET3NjE4SMW
ucYIemNo4vccKfwJ3B23XIXmmQM3ARc6uB9AEVnSTGjV/xGdjoz7zIef4tL7SFd0nAp+HV2q3ZPm
jc46wnnk4cJTE8h2AditdZO+dI15NIM/8fQU2JnQLhEpc6AzQZJMMoNKlBdljRDLoEnXKlw7QJLC
l1Xi9LoQOBXmQN2/9Xc4HwPhReZukft0jo90TGc4/ybbDUJXPO2Txo1O/HwMx3hg24Onj747w24b
UZgkYzRDIg/JcJ86A0wRa7+beJIDTYVBecV/a/LvZmOYtBm98Sy/20RxVU6tAYH2mQPNTqntZrLt
bWgLmvm0A29ozGyGdzAb//Na7SbSsNEh0nLjge3R3lBTDDpqnykT9LrP5fY3GaG60V4coNOpfpUv
3nwoF0ocJc2pjOcE6Ov9rRblMx1q0g2xysnJ78VkaMWnjSHQHnOg6OL6O4w6/wIWn27ycTeGQX0N
NWx05D5SRMgu/lchXPhYlPAS19dtKbnrTTY3z6PA7mAKtzTmJPe+yr3dMozUkqZB/kRz3Io3ZCUd
Ee3Pxniut6+R34+YzIolVTm5bgRaYg6kjfg66YZ6m9x2ki/ZnJ2vlwng383c+bpxOYL8ho3OETQ+
qggygnkmw04a2M29RrfaFAFh2plTuVD0Ji6N48j4zgBqx4f5cIXQnek4jdxcb5CyDzqYpN8FyfLy
m6Gqti1V+LJGBNpgDozn8vsaO76k3mo6k1+jb3w82Ft+iKSKnL1GfK4qmqktrooc17vGCDBzYJuv
cSqpLa7xXcWqMwI7I8DMgTtDdZSCbHSOAiMLuY4IMHNgO6PG7lU7uHOrjMCtRaBypsPMgbf2vuCO
MwIHI8DMgQdDyAIYAUbgGAjc8lfmx4CQZTACjMA+CLDR2QctLssIMAIHI1Cj0THY2dRHdOoLpw21
zbVK5pqm6qUIG2KumJCjqejk91q/osjjVGuEWVGOU+nQUE8EvYfiF8qPVdXX04Rraf6V+ka6HmPJ
jHFvio5/jyBdta1Wb6tjDhexPMFk9VPnFrsffVVsyht9t8HNRGRcuoyVn2MG3GAOzOs6it4X32sn
zBxIyxFq+lskPvxkcSXpqyR0kbjh6kq1d68k24FvapmmuWFSd+tFei6IsSmnT1GpY6bJ/pY3Sflu
IodCls3GhcYYSVld6ktWtkLnVZi4UG1UlKMsKnvw2Nh9/kfi42+b/Vi8S4B32T28+nvi4psUi2I9
V+E3+TpJkiz8vyVw/57dTyTXuBZ1/H8IgXndoVQAABP6SURBVOLcztM6/JCE7t8SN/whbbxK778l
SGVqTRd+goOx09KufFLfTGe9ROz2sQtdjW2q19E5xghrp78Q7TiK20Zp0YV3uUIIc02UyruFR2J4
dNRaMsImQbZMw8HQB2JFa9cEPF0PE6ehsTk55sCP4F2a/Dm0Fovwz2Y7t5s5cLnEzOlrzpnd78cY
z8d5vprd6+5TMuXFGToFlawV6LSgcxQhCjLXLz/tjjBSLmQnz69MLkYQ0Kr1TrreCoBYIJrJItnE
RrnBLGi7IOI6q2fqIF2ZyKDUyLshcvV7VlczFxb03kyK59NCdkVRZh0hmJpcQ2ZNdT43dDLcZd03
SWQ2wwzjXqpzRT9Jar/vopAdQDV5tOPpMQfmurb+DoFFdXGrmQOJK8bNPVzGDZdDLn9BrII5Yqt8
9hGvqpkDu32HfkIyX3w2RtRPCdxzDH/b2f+mU1oQmiAhClR6oAYxQkV9QSvt05Xmm8yCZneL2skb
uNl4iWG6gn/hzzA+T+MwFWyGZgub50RFUsyuKOJgRE1irKjfrE90QZGm+ViFMQYbuxHIRa/Elh2u
iB5EEvbn2RTz90536MFVpGlFjR4p7RSZA1XXxIym9xNm/oea0YDybjVzIFE8zOBlXDGrPoKNG05B
qI5y9uF6wyvMkJSMuo4+JortkKb4frpyfBf2P3+YUQ90PVyaVB7dIbxd2OkL27F+8Y12xGp2BcU+
bIaqDh3JRYZJYJZlit0FkgQLGHzPWbY+c8ML/VBIKo8I85RkXBcqONHUIQIvg4lRlzVJ03TiQSf2
yu4esfatfpuNnZDeQbj6VDP3Jcn+nDciiDy/q2Vc4H1uuxjdiQLmQJXnTKQOtBuEudWMyj/lY20x
HXFTKnJzQqDbhzOTN1x+qm/+isnZh6cIYWtFrpo5ULD6me5hSXxqF/Y/d4OI2Xh70ulhPNve0Q19
CqpstmMWMt86lbMZmjV2OZdUHSlV6y4VtpbJYmqaOsT+saJ7aauc/QucPnPgZp+c4R1g+hMzB25C
o1Lkr6bYbUEReZl8wvRrXvLLqiQc72jFbXKCC+I9syWWuTLGxT7sf8Ll7GE5SYnMEuLbMWSVnG64
eyXlipL3ZjMsElKVVmKQq6pU58mAtSR7W8CfjXEeGdMjMQOrlnBY7jVjDnTvXOmFzWEYXb12TTMd
+Uue+0aDDIox/S9SWfyabylTVO+qaV3vAmFsuweke0+8PXuS+zmdIlA3vhFA3Zf9T/TRIGMXb9B2
mOmACN5NlkEiuKeAe2EgPI/IPmyGuZpiRmG6MXJccwHs+RRV7vBs/Fz/CgsWRdfTOxvk2tIXckaW
tUEzUsDp2wwwxW6fFnPoyUkyB75HNPoGGTYAkX653ocnGI4oH4CajI6cIntRTzPodYI+Vpv8iznN
xMORS6n7Qv6iiriEfvuU7vhpuoakhhvCW6b96UXwRNCTMvZj/xOGDhnr4DkuxLY06m1MnlnQ7L/V
TspwuAVSIWAbm6HZSv6cXomb5PWE1wIwSOkHWBiv0PO16coN+5in2A7iECsbVyok4lr09ooC41Y/
yf10Fjmu4PU8wqyBH6fTYw6kV+b3gIH6KPEbDHAvtwXN5gicXgpTW+wyJuQSkdEsemB2qX+dy1Df
58N0n65T6IiciZJ7uovBLdb4GDKKJZ906oncx5XUFicNICvXDALOE4TBOaK13O2imUYrWlnPEdGH
oznXt6L8DlnMHLgDSEcswkbniGDeTFFdeBceRucRhq3P9OgbngjexeVRYhjMHNjOHcvuVTu4c6uM
wK1FoHKmw8yBt/a+4I4zAgcjwMyBB0PIAhgBRuAYCNT0yvwYqrEMRoARuIkIsNG5iaPKfWIEThiB
VoxObu2Vva6mDbBSKoXcF9QlegjdzU9CS8ptJNM3Erv0VVM+bEioL6GNNuvrzQ6S5ZfVgm5EjGWe
jU8z+nXyX/+CmQN3wHZ7keaNDtEsRNnq85UXoXeVh3h733YuQV+4wveBaJ5RWexce8eCtNJ7l1fO
pauqrXaEochz5lglKi8FNYXCfdc2KyVev0x/keQ+eswWfKaryBd3MB18q5dxyB5urjJPkk/0Snqx
glzsbZ+tRF84P6FnUpLG36IXfYBVIsusvJ/RC74X4qn+IL6b5YXAuKd0oGUQ/0Ic/jpdoX4PzviH
3LIIIYSoSgdyT3Q1KmIB9sJXl60eGzc69mrpQxYyHgc5Ig0DvCdDOObapuMIZynXGQFmDqxl9Bo3
OraRsY1QLb2sEip4amgRoqTeVGugsiomJUSAeZaBTbY+ounIl49VedO9Ss9NJkLt2lmujpiRqHVh
2j3bZNujcjZDYc6NJRnpzIbSB1MA03Sxq9GmkKOVJuXJFclmVMX6qE7etCMzB9Yxoo0bHZCbMVlC
caXQgsfk6otoDsaE6DjVKmnnSWgx0tEDN0AcKsbAPiKL/CZj6yOKiikGnXnK3iev9cp0W9PZGMth
Sm+x8DEb01IDq1AcQCySVGyAjqJ4kIsiM7Y9WS/HUFjBFljFUEgYxIHa+YFsDi07kCvDhbGiRZuG
Pm27xhZiR71k5sCjwqmFNW50xK8vLSBMb9wLnOtfYK1VUyeCosJkBCQWP5PCYo5oZuYTY6ClnF7t
3AUxnMK+topnlz40KwXRVmQZ+TPD5SO/PCNFzxcTV7ptWvw+QWJyFVW1YYqiFd/I2P3i52M4Ew9d
pBxD4lxWkKvXj0ngZSrS/DkzBzaDecNGZ5McS/LdBpu/8g30X1AkgGYnirBcsvjNKgLKRApu/tls
ffa1WTZ3vgvxFRmOhQ9aIyTetFik7zl5RCOxwVBounq7sgV24U0cRIJTlDiSlXEkVkfyyDJdOh2S
afLt2Bpdr+sskHxP/ghY/MPbetPtd4D4ly0vI95jHiXwhx9rcd3hB3CnP1rPwPcIej/BWWRBal3B
OGHmQAOM0z9NDSC9wdAshgkSQZSe/dK33g8xY5E6rkIX04FJ71qunYznBJoUPUkW5bMpW4wzhEPk
WwXEa+KNj4mXyfdsy7m218wcWOfQNTzTkRShuX2SaKuarWxyNUBA+zkhRJ4dkAilJOn6+HmckktN
MVCvliG3x6lBm0KRwnDo4DHRTDs0ndmJmvLKbIFCEwqqTzGgXSs0QA6ekNEz4z0UEO/sZgQLO3jK
icwcWNvoNGx06Jm+xEQx8Ik3Ku2QY5kBZBvdjGxcMiAKSlPhgs3R34XQ2BZ4xWsR8HUylsEOGYEL
iq/YbHubDWxjCyxnKJSyRFDd+jHY1Ie21inaqWFTn+uYwsyB9YwaU1vUgytLPWkEmDnQZpxucrgq
qS2aVITbYgTaQoCZA5tFno1Os3hzayeEADMHtjMY7F61gzu3ygjcWgQqZzrMHHhr7wvuOCNwMALM
HHgwhCyAEWAEjoFA46/Mj6E0y2AEGIHriwAbnes7dqw5I3AtEWjF6OToEfTXvs3jl9NDr7/KKCCa
14hbbAYBZg5sBufiVho3OoIeAYtsvdNwDs0lU6xjvam+oYtYU7SAPx1ssrHVqwVLbwEBZg5sAXQA
DRudzVXmoJXRFau6m4clXWM0zzFZNa8Gt9g+AswcWMsYNGx0SvowW2JZktVGslgsaTYsmPUySofM
I5TT9CCKMFLuGS3QNMsbCzZJZM6l03kkJ2Pnk00TLUW2mLK4nqkknx8fAWYOPD6mjc905CpzkxKU
SKJmp8TJIoi9iIuLGLnoT1KDOooCYxUiHuQNxDQCLpRrNhujd56/pgXr9CdcS5t5TxgeyWEjVrbL
ooBBK1FYL7N8qgYfj4wAMwceGdBUXOMzna53gWzVdgfz4R48L3VgQDzBapZCx94YCFfQDKqCQ9mg
wOh6uAjJI8y4RRXdKdAHcXzZ11LtEua9WcrdQ8x+U8XCt0YUKFqJknq6bB2g3E6ZzBzYzLg3bnQA
oovIiLMm/SViOOi3tezVCCTLHToMelKanSxjgGYvhmHqjWeYLTOH0LGUt6/lUBLznitCWMVDS7Gk
GCKUZPASAzefsa8Yj+ZTmTmwGcxbMDpWxwSJ127EVFbNo186k5RcXcda0ibcjIxcswzqqdCuatAs
aAbDVm1UJOpWIkWPaR8ubyh5c9JSt4OxbwOSlhKYObBO4Bs3OoINz4hHEJmWb5B919nZ7bK78C5C
uDO16wKRjk3gG+TockuWzhVe86fxLIN5Lw4GmJpEWYIUfYzB2MHEU1O/W8bYt32QminBzIG14dy4
0bFjOkHfiJ/U1s09BIuYjYvZuJd+qyO3e4k1IXkPkbeq3pWhpDmbeU9sL5Pb9ZMCyr6xo4QUZNfr
iB0kby5jXwl8jSczc2A9kDO1RT24stSTRoCZA9U8uo1hqqS2aEMhbpMRaBoBZg5sFnE2Os3iza2d
EALMHNjOYLB71Q7u3CojcGsRqJzpMHPgrb0vuOOMwMEIMHPgwRCyAEaAETgGAo2/Mj+G0iyDEWAE
ri8CbHSu79ix5ozAtUSgWaNDe18bXyNLxIjCIaON6NhLEGqGVXwhbbZv6Cfz8ivKpTop85wom+pv
1DPLbCSL/b/b62/NcF4T8en40biLAfoeQecbdAr+c+O3/g6jgjKdzjtE2fpfIP42L2v0HcxsAmkd
vcvKWPlxYOpiyUZe11H0vhhz0iH4XudpapSGny+tgHHSnNGhh20wNZqWp+sowFQvulwhRLYEYaPw
kRPIqPQiDytBS0GLUFdyBXx6p4kvgf0ZcpQT4oY5xxghVub6q2mQv/EKdBVGTHxNnC14XdBe5Sdw
IxSoe+OTmDmwnSFuxOgIKzuI4fuu1UubSVAuAzBXcFsVjnpJZF0ZDQWJTtdeGbQRzpMQrklfuo5w
TuwXF15uQabrAuPzaOMXTSus6q3yyxecycJa26Vr8EnbCDBzYC0j0IjRwZB4iC/xpG/3oYTuIV6W
P7y2iAOvZ+PnyBGTdj1cJoZhSNdiTdOFmkQ6hvACej1m2r4zkQtDz3PzbEM5sZrew3Dj+3MHkyTJ
+HuMKnzaNgLMHFjHCDRidBxHsfDt0IV+H25D9KWaykLHdIriN7TS/EK6faMRBtM8307WIweThY8N
I5YWELw8Tj83O8rq8tkpIsDMgfWMSiNGpx7VjyHVIBRbhXAxw7jXwWYwW7pdmM3gL4xZkK2CM8HC
n2KQiz7ahfj6VBFg5sBmRub0jE5bpF7CrUqQkPHJ8eekA9Htw0EV858stxED0tUdoEG3sZnb52a1
wsyBzYxny0anhE2vETeEXnUXuFNEpGXHu/cZCx0Dep7f4YI4kBUfck6efH3b6t5fOX34AmDmwDrv
gpaNjr07BBGST+HSXli1/zkY0uvwXrbNi2gyfo7xzIfeDOIKesgY0BTTmVmZGACx0V4c9ER7GVOg
WYfPW0OAmQNrg75lowMQLzC9kpY7MvTE9y8X9quhmrrvTBKswhgDHUimj8X6WJlvr67UdsoAaNWl
736SBXLtCfbAg9uzGuLLoyDAzIFHgXFDCFNbbEDCCTcfAWYO3Phyo8FBr6S2aFAPbooRaA0BZg5s
Fno2Os3iza2dEALMHNjOYLB71Q7u3CojcGsRqJzpMHPgrb0vuOOMwMEIMHPgwRCyAEaAETgGAq2/
Mj9GJ1gGI8AIXB8E2Ohcn7FiTRmBG4FAw0aHvo8oWHpAUBayCtaLsWZTMz8OLFoaUaqGXMLA6ztL
ATrRDDlu4oNUMXh5Nj6TQTA3tswceJTxbNDoyA+yxrmlAWkfSlgFj9LDbUI0a2HK5rdwMO6VGMZt
smrKF4yDzC54dHSZOfDokO4ksBmjs44w6vQwdnz4llrlrIJWwaYuBT3FJkVpU81zOyeEADMH1jIY
zRgd9DFZJUgmw81OlLIKbhZtKsUZ+nkaCmE0MzL13JQ7p5Qxbdek31kBSfQu5YyiyFrlbhHUKzcv
DtCj6eHM5FKubidrkc8OQ4CZAw/Dr7h2M0an68ApWeyxF6tgcR+On5pjL4wR9MZwFqn7tQoRD4rd
L7Fi3CFq1ozkXVNWCOPhYJGSwE+WY2Q09WREBojDVVbXTWdbzgSr0AXcEKtLyctc2c7x0bi1Epk5
sJ6hb8bo1KN7M1LjOaZuiCeKcVXw5QDR3N5UJMZ86iLMCsK7CKmg4HuO51O44RMoMYLsS/dAMhhe
6tX1kvJDZ+dOqtvJFeWLvRBg5sC94LpyYTY6RdAZ7IWC25hcG+MNF7k7GztWrJeIFd2pKtsbY1bG
9yyYCPONm+6XcKny2fJq33aKZHBaIQLMHFgIy9ET2egUQEqzEpjsheTa6L2xUjfL3PNKy3ARUuwq
V7aCU1nXk/Gc3nKi6wqXSufbJ1dtx5bD18UIMHNgMS7HSWWjY+MYBxgYblLXk1vLPNf71Mggro7V
qPpdDxNrYz7zVTcFp82dIuJgkMV0xOzFcM3EHllF3xbQ1lzV7Sh1+HggAswceCCA5dXZ6GjWwvTt
lNiB89LY18rBRASP1durHiJvhSz+koErtrSJFQtiR+4emgZ/IQLCGUth0A+zzwfSOJHYiYJcs3Pg
YuED6aZ/gl1RuHiSWrWynUwdPjsQAWYOPBDAkupMbVECTO3J9Bq+t8SEqUprh3qzAZqt9rCc3LJN
DsVX/339FnQTl2ZSKqktmlHhdrRCrpbYNz2d+aznEWauh4vb0f2T7iUzBzY7PGx0GsJb7BAR9dDr
jNMWfSyS/H7oDanCzaQIMHNgO7cCu1ft4M6tMgK3FoHKmc7//F//+9YCwx1nBBiBwxD4j3//t0IB
PNMphIUTGQFGoC4E+JV5XciyXEaAEShEgI1OISycyAgwAnUhwEanLmRZLiPACBQiwEanEBZOZAQY
gboQYKNTF7IslxFgBAoR+P8E9f9idw9CCQAAAABJRU5ErkJggg==


--=====_002_next=====--

--=====_001_next=====--


From nobody Mon Sep 16 02:37:16 2019
Return-Path: <dhruv.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6943C120810; Mon, 16 Sep 2019 02:37:14 -0700 (PDT)
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, FREEMAIL_FROM=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=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 vCUGJGtkhzPq; Mon, 16 Sep 2019 02:37:12 -0700 (PDT)
Received: from mail-io1-xd35.google.com (mail-io1-xd35.google.com [IPv6:2607:f8b0:4864:20::d35]) (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 B1CF8120019; Mon, 16 Sep 2019 02:37:12 -0700 (PDT)
Received: by mail-io1-xd35.google.com with SMTP id r26so76935569ioh.8; Mon, 16 Sep 2019 02:37:12 -0700 (PDT)
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=N3rMwk0zXUUZyJtV3fb0tCSlXgb1lDKppYWmQi0HUTc=; b=M4dHSQeFgKoZmYyGXZ0mN6OCLfmX+JpSMxXsKzJEKTCFlMPSrjkB4/H6pf53gfiK0M zQ/LHIhXotZR1G5vfY1Q7yopI0GfdILtZqX2LeRF7GtaeuobryFxaQt+TDUlm4L9uLyH RuNZoYkT9ws1CDPdjRawCe6UGM+mej2zkdCnkzbhFcPY9C/2ypiY9DWrkP+we3Nw97ec auSdMvEL6/vTIXWCbT+2BYDT3nC0iBLzAW9zBTRNtrhkZ8g1AfwpwfzpAqQd9+yIo8N5 yG41Pimdx3Kp5x9VicNJIwwVC8bgXhQQ7g3FcHR2cP79a7Xo8v3gTTRQ4zrjHeqGRPEZ fgGQ==
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=N3rMwk0zXUUZyJtV3fb0tCSlXgb1lDKppYWmQi0HUTc=; b=Fje3Ypm1TPnafzzhu+/C/MIvxpVQmhfQLN2hapsKa5yJP9d24g2TRnHzVy8LgM3clp 5Il+LNfOHqNt4JopmpJOqLTc096DDE1LBFggnmZQLw1f0S7f6WjQyYXxZbsutvu2bYsa A5aIiuydABGq5PD9SflfXOnt11CnBdaMod4JeYzJEFDNEtvEbAw+rctfTAgharXhFXHr QoW9Mhvwvher3ksTAmUeK0o0AMWrjc88N55nbH7VgOTb+hVVFOB7h+TMuvgtUWUO5ypg HGAWwgWvenePbbpFcrxp/YSDiz5xPwSvyHPJlw4HF0oN9j02sfnRlvvpVHDaRwBjb4VA w4bA==
X-Gm-Message-State: APjAAAV2dYwTq4WuReMnPhaJiG9IC1U8ofo8v5+XcDlWyEWViie+gDEj n/c1v9U9RqIrDgrcultUYHZFjRshAalVLqSEz4s=
X-Google-Smtp-Source: APXvYqxPJYtYSVW6l+AukhkWvZ+V9+pYLhNYiwBIQdsI2twxtYgsOjFY4DQvOqgfPYcqWfNs//3Xjmm13iMWmfzIWh8=
X-Received: by 2002:a6b:c38f:: with SMTP id t137mr15951781iof.137.1568626631726;  Mon, 16 Sep 2019 02:37:11 -0700 (PDT)
MIME-Version: 1.0
References: <201909161642099990442@zte.com.cn>
In-Reply-To: <201909161642099990442@zte.com.cn>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Mon, 16 Sep 2019 15:06:35 +0530
Message-ID: <CAB75xn5oNhRTvJTApZUfQeSb=n=W2bbOXqRfuV5oJeiGb9pu8A@mail.gmail.com>
To: xiong.quan@zte.com.cn
Cc: pce@ietf.org, pce-chairs <pce-chairs@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/QVomd2NJyRn842ZwKLdescQZsPA>
Subject: Re: [Pce] Comments about the LSP Object Flag field
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Sep 2019 09:37:15 -0000

Hi Quan,

Thanks for bringing this up.

Hi WG,

I see these options -

1) Leave the last bit in flag field in LSP object as unassigned and
all future allocations in 'LSP-EXTENDED-FLAG TLV'.
2) Mark the last bit as Extended (X) which directs the implementation
to parse the 'LSP-EXTENDED-FLAG TLV'. And all future allocations in
'LSP-EXTENDED-FLAG TLV'.
3) Allocate the last flag in LSP object to the first request and any
other future allocations in 'LSP-EXTENDED-FLAG TLV'.

Thoughts?

The 'LSP-EXTENDED-FLAG TLV' and the associated registry can be created
in an independent document or the first document that is progressed in
the WG that requires the flag.

Thanks!
Dhruv


On Mon, Sep 16, 2019 at 2:12 PM <xiong.quan@zte.com.cn> wrote:
>
>
> Hi all,
>
>
> As defined in [RFC8231], the length of LSP Object Flag field is 12 bits and it defined the value from bit 5 to bit 11.
>
> The bits from 1 to 3 are defined in [RFC8623] and the bit value 4 is used in [RFC8281]. So all bits of the flag has been occupied as the following shown.
>
>
>
> I noticed many other drafts have extended the flag, for example, draft-li-pce-sr-path-segment defined a new P bit.
>

I think the path segment is the only one


> But no unused bit can be assigned for it. So I propoese  a new LSP-EXTENDED-FLAG TLV for LSP object to extend the
>
>  length of the flag as the following shown.
>
>         0                            1                            2                           3
>
>         0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>        |                    Type=TBD             |                    Length                   |
>
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>        |                                    Extended Flag                                         |
>
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>
> What is ypur opnion? Do you have other suggestions?
>
>
> Thanks,
>
> Quan
>
>


From nobody Mon Sep 16 04:18:58 2019
Return-Path: <dhruv.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 547A4120834; Mon, 16 Sep 2019 04:18:47 -0700 (PDT)
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, FREEMAIL_FROM=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=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 9rADYsgGkwAZ; Mon, 16 Sep 2019 04:18:45 -0700 (PDT)
Received: from mail-io1-xd32.google.com (mail-io1-xd32.google.com [IPv6:2607:f8b0:4864:20::d32]) (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 D6DFA120019; Mon, 16 Sep 2019 04:18:44 -0700 (PDT)
Received: by mail-io1-xd32.google.com with SMTP id h144so77608098iof.7; Mon, 16 Sep 2019 04:18:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to:cc :content-transfer-encoding; bh=mz7w4BEMvy8p+PNBOGM3jjO7Z9lMrTCbOyyKfBperQQ=; b=AmgE/Q5IesWgChHOKTqFZ00fNGOoxyXm6vRdlDG1L4d3Vm6iehoasBuWP3scLkh20r YzDBKBM5Th0mL9Q9s8Ficz84+6SjCVdC4rI0kxJHcwqhTikLPCmUZOphJmojDFhVP+or tg1T3k2H0pIqvRWijCyefRiv9OOvzxNwanOtLMeMjlsBX0Q5p2W0R3uXCBEGg791W7m3 +e6JKeU6q56NsXIzzql2k1DveS/XP5I/YTkli+3LuapergE1NUKu0di+FPK6/uYuzX52 kChzncOOs6zmF4O+rBXoOv8zr385J5z/7SzMg/3NF/DPhDICKJHq3HhPrtJdxT3td/75 dHAQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc :content-transfer-encoding; bh=mz7w4BEMvy8p+PNBOGM3jjO7Z9lMrTCbOyyKfBperQQ=; b=Vq14yn++Kj3CpEBsHYuTeCoZJXW4moR5TiNQcZKfZ019A9cTyl6jHai8m7aTYoLfcN tlAnkTMcV3xUhHBnZ/+lKiV/dmA6S+/n7Aju/2RcrYnM/aQMS1hOXiyT8h4qhrNBmqef 8zNUrRkmsN2UpoYlry/K9IZ6TpbPmt2U9ym8li3KHKmovQIxkDwepfNoCJ2rPNmXrdUV OjPrf1o7oWa5pN0pN8N927xuFXE25thOGSNx4DN7Dwv+cvceQo6sx1g6BaOwpEMiqAYw jHxgjX/4L4KMIV3YkBv1GdSKlXLMCeoowTs3UFVT6rl+m4dC9vWoMs2tCbOutJqWDTjn 5lUQ==
X-Gm-Message-State: APjAAAXKFPCRZBILrzCYBeOGZAw6Bw2pCZGg0i/4maanX803JLk/YwuN 0CYSwETUQH+nGP70k3Kmh4mQd590oI+7N9+/SoM=
X-Google-Smtp-Source: APXvYqxzJ+KWmPo0S9y5EMEEL1ijr4ZyHqEC5x04kBmBvtQ9C2sWGHUIjYMWJKD9ZCW9/QjSzrz9H0+f6UMiS1ag55w=
X-Received: by 2002:a02:1ac5:: with SMTP id 188mr14535551jai.71.1568632723878;  Mon, 16 Sep 2019 04:18:43 -0700 (PDT)
MIME-Version: 1.0
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Mon, 16 Sep 2019 16:48:07 +0530
Message-ID: <CAB75xn5CPpoo=SWGfiDS+jQQ0pr1Z7HeHKjx9prGzb6tH9YxbQ@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>, pce@ietf.org
Cc: The IESG <iesg@ietf.org>, pce-chairs <pce-chairs@ietf.org>,  Farrel Adrian <adrian@olddog.co.uk>, draft-ietf-pce-stateful-pce-auto-bandwidth@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/YxO8HZTG8xIkK3R4nQJJToVUEZs>
Subject: [Pce] **Barry Leiba's DISCUSS on draft-ietf-pce-stateful-pce-auto-bandwidth**
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Sep 2019 11:18:48 -0000

Hi Barry, WG,

I saw the DISCUSS [1] in the datatracker but for some reason the email
never landed in my inbox or the list [2]. I am manually posting it
here -

=3D=3D=3D=3D

Discuss (2019-09-16)

Thanks for another clear document.  There are some "SHOULD" key words
in one section that I would like to discuss, and that I think we ought
to be able to resolve without much difficulty:

=E2=80=94 Section 5.7 =E2=80=94

There are various =E2=80=9CSHOULD=E2=80=9Ds in this section, and I have the=
 same
comment about all of them: BCP 14 says, about =E2=80=9CSHOULD=E2=80=9D, tha=
t =E2=80=9Cthere
may exist valid reasons in particular circumstances to ignore a
particular item, but the full implications must be understood and
carefully weighed before choosing a different course.=E2=80=9D  I see no
guidance here to help the reader understand what such circumstances
and implications are, so I can=E2=80=99t see how an implementer can evaluat=
e
the situation.  Can you provide any help here?

=3D=3D=3D=3D

Comment (2019-09-16)

Again, these are purely editorial comments, which need no detailed
response; please just consider them.

=E2=80=94 Section 1 =E2=80=94

   Over time, based on the varying traffic pattern, an LSP established
   with a certain bandwidth may require to adjust the bandwidth reserved
   in the network dynamically.

=E2=80=9Cmay require adjustment of the bandwidth=E2=80=9D

   This is similar to
   the Passive stateful PCE model, while the Passive stateful PCE uses
   path request/reply mechanism, the Active stateful PCE uses
   report/update mechanism.

NEW
   This is similar to
   the Passive stateful PCE model: while the Passive stateful PCE uses
   a path request/reply mechanism, the Active stateful PCE uses a
   report/update mechanism.
END

   This document defines the PCEP extensions needed to support Auto-
   Bandwidth feature in a Active stateful PCE model

NEW
   This document defines the PCEP extensions needed to support an Auto-
   Bandwidth feature in an Active stateful PCE model
END

=E2=80=94 Section 2.3 =E2=80=94

      This value indicates how many times
      consecutively, the percentage or absolute difference

Add a comma after =E2=80=9Ctimes=E2=80=9D.

=E2=80=94 Section 3 =E2=80=94

   The PCEP speaker supporting this document must have a mechanism

=E2=80=9CA PCEP speaker=E2=80=9D.

   o  It is required to identify and inform the PCC, which LSPs are
      enabled with Auto-Bandwidth feature.  Not all LSPs in some
      deployments would like their bandwidth to be dependent on the
      real-time bandwidth usage but be constant as set by the operator.

NEW
   o  It is necessary to identify and inform the PCC which LSPs have
      the Auto-Bandwidth feature enabled.  In some deployments, not
      all LSPs would like their bandwidth to be dependent on the
      real-time bandwidth usage, but would rather be constant as set
      by the operator.
END

=E2=80=94 Section 4.1 =E2=80=94

   The initial LSP bandwidth can be set to an arbitrary value (including
   zero), in practice, it can be operator expected value based on design
   and planning.

NEW
   The initial LSP bandwidth can be set to an arbitrary value (including
   zero).  In practice, it can be set to an expected value based on design
   and planning.
END

=E2=80=94 Section 4.2 =E2=80=94

   When the Auto-Bandwidth feature is enabled, the measured traffic rate
   is periodically sampled at each Sample-Interval (which can be
   configured by an operator and the default value as 5 minutes) by the
   PCC, when the PCC is the head-end node of the LSP.  The traffic rate
   samples are accumulated over the Adjustment-Interval period (in the
   Up or Down direction) (which can be configured by an operator and the
   default value as 24 hours).

NEW
   When the Auto-Bandwidth feature is enabled, the measured traffic rate
   is periodically sampled at each Sample-Interval by the PCC, when the
   PCC is the head-end node of the LSP.  The sample interval can be
   configured by an operator, with a default value of 5 minutes.

   The traffic rate samples are accumulated over the Adjustment-Interval
   period (in the Up or Down direction).  The period can be configured by
   an operator, with a default value of 24 hours.
END

   The PCC, in-charge of calculating the
   bandwidth to be adjusted, can decide to adjust the bandwidth

Remove both commas.

   Only if the difference between the
   current bandwidth demand (MaxAvgBw) and the current bandwidth
   reservation is greater than or equal to the Adjustment-Threshold
   (percentage or absolute value) (which can be configured by an
   operator and the default as 5 percentage), the LSP bandwidth is
   adjusted (upsized) to the current bandwidth demand (MaxAvgBw).

I=E2=80=99m sorry: I can=E2=80=99t made any sense out of this text and, thu=
s, can=E2=80=99t
suggest a fix.  Please try rephrasing this.  When you do, please make
it more than one sentence, and please avoid consecutive parenthesized
phrases, which are awkward.

   However, longer
   adjustment-interval can result in an undesirable effect

=E2=80=9Ca longer=E2=80=9D

   To avoid this, the
   Auto-Bandwidth feature may pre-maturely expire the adjustment-
   interval and adjust the LSP bandwidth

=E2=80=9Cprematurely=E2=80=9D, with no hyphen.
=E2=80=9Cadjustment interval=E2=80=9D, with no hyphen.

=E2=80=94 Section 5.1 =E2=80=94

   o  The PCEP speaker that does not recognize the extensions defined in

=E2=80=9CA PCEP speaker=E2=80=9D

   o  If the PCEP speaker that supports the extensions defined in this

=E2=80=9CIf a PCEP speaker supports=E2=80=9D

=E2=80=94 Section 5.2 =E2=80=94

   Future specification can define additional sub-TLVs.

=E2=80=9Cspecifications=E2=80=9D

   If sub-TLVs are not present, the
   default values as specified in this document are used or otherwise
   based on the local policy are assumed.

I can=E2=80=99t make sense of that sentence; please re-phrase it.

=E2=80=94 Section 5.2.3.2 =E2=80=94

   o  Reserved: SHOULD be set to zero on transmission and MUST be
      ignored on receipt.

Why is this =E2=80=9CSHOULD=E2=80=9D, when other reserved values have been =
=E2=80=9CMUST=E2=80=9D?

(Same comment in 5.2.3.4, 5.2.5.1, 5.2.5.2, 5.2.5.3, and 5.2.5.4.)

=3D=3D=3D=3D

[1] https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-pce-auto-bandw=
idth/ballot/
[2] https://mailarchive.ietf.org/arch/browse/pce/


From nobody Mon Sep 16 04:21:28 2019
Return-Path: <dhruv.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC44E120834; Mon, 16 Sep 2019 04:21:26 -0700 (PDT)
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, FREEMAIL_FROM=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=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 kj9C2VUcS2j9; Mon, 16 Sep 2019 04:21:24 -0700 (PDT)
Received: from mail-io1-xd42.google.com (mail-io1-xd42.google.com [IPv6:2607:f8b0:4864:20::d42]) (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 1D77F120019; Mon, 16 Sep 2019 04:21:24 -0700 (PDT)
Received: by mail-io1-xd42.google.com with SMTP id q10so5865731iop.2; Mon, 16 Sep 2019 04:21:24 -0700 (PDT)
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:content-transfer-encoding; bh=YmKnli5cssOLP4ZkSPw81CwzMxwNMxzWbksAtfFsiEA=; b=UA5BP932yxFlxDENKpFnbHbcN45+JueNrX+RdyKxKYR8/19xw6Pyct8XRS8Z8578Wv Jr58oOou/S3BxJQXT2rSsbQdy+GNajrrlY3H2h/ZsivVd5H/RtOw9H6Hop1V/B1zqJkw f6HhGY6noCQG53ihVGvAfuwLMZoiIP1uGNWgwgXw2fLgmHmNgXiGWvITFFe2JXiGvYyr MBZt26GOiDC/Fh9tqnFLq63ERwmZQhts8ucmVI4jv9qC+EENdPRhjdEWyF5g2PNnk3rz EVncjMdSZCONVU8mkQQgh+cokPt0SbkM6q8LhYw3NmusSd8sTOIy0lBUuv806x1Utmvo tT6Q==
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:content-transfer-encoding; bh=YmKnli5cssOLP4ZkSPw81CwzMxwNMxzWbksAtfFsiEA=; b=YFakiCwwmbkwAU9xuKE2HlS0fN2qlt6KnOhbP3eUTEtTSxdyPOgQsep3SS0y/BtSw4 AxMbY0+iICx4quMH/8GqkdyeQrff+itmlqrImmr92Zrzy4ZQdbuGMeIiGz/Js3Rsa9fU M1fMxNd3D2M2P4No+kumhOelVkHTwsh4c6LE3nIGM/zOdl05GvjrS+CadvRw1cjpLD9E wjV78TvfurO2TnTDxXA9erihU1rUcOzdk60lRVRoCjvNLVkRAkAmFGvUjXnV+eW0ydGs HTwT3EuPb2iSi2dgem9Z+LLzoj5EiLP4qf2Q92qHF06WMJypjYKfa11c8e5uPngl3Fd6 fwfw==
X-Gm-Message-State: APjAAAUCiEEw5Pkx2yxUzjJkdF3gf7PzM13BjyALsM5OCNGuX+8LJ/eb kWoHQcN3bhknYXvULN5Ssjh8f7YBe4fSCLi7AGbDMQGu
X-Google-Smtp-Source: APXvYqxN0vVu8wp35vxtagaQ6t23Q9KvV0dUSRQxMiV0BIfCnR5mvv2lRj+fHwGL5cgPiCtFtkWL7iIlalBFdEFsKDY=
X-Received: by 2002:a05:6638:3:: with SMTP id z3mr6662242jao.54.1568632883184;  Mon, 16 Sep 2019 04:21:23 -0700 (PDT)
MIME-Version: 1.0
References: <CAB75xn5CPpoo=SWGfiDS+jQQ0pr1Z7HeHKjx9prGzb6tH9YxbQ@mail.gmail.com>
In-Reply-To: <CAB75xn5CPpoo=SWGfiDS+jQQ0pr1Z7HeHKjx9prGzb6tH9YxbQ@mail.gmail.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Mon, 16 Sep 2019 16:50:46 +0530
Message-ID: <CAB75xn6jiNGePOAat_ET-JsPsvuouo8d651GrdjswPjC7OYPWQ@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>, pce@ietf.org
Cc: The IESG <iesg@ietf.org>, pce-chairs <pce-chairs@ietf.org>,  Farrel Adrian <adrian@olddog.co.uk>, draft-ietf-pce-stateful-pce-auto-bandwidth@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/izl_c-zDCX_0fKrPIxCnPVRMydI>
Subject: Re: [Pce] **Barry Leiba's DISCUSS on draft-ietf-pce-stateful-pce-auto-bandwidth**
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Sep 2019 11:21:27 -0000

Hi again!

On Mon, Sep 16, 2019 at 4:48 PM Dhruv Dhody <dhruv.ietf@gmail.com> wrote:
>
> Hi Barry, WG,
>
> I saw the DISCUSS [1] in the datatracker but for some reason the email
> never landed in my inbox or the list [2]. I am manually posting it
> here -
>
> =3D=3D=3D=3D
>
> Discuss (2019-09-16)
>
> Thanks for another clear document.  There are some "SHOULD" key words
> in one section that I would like to discuss, and that I think we ought
> to be able to resolve without much difficulty:
>
> =E2=80=94 Section 5.7 =E2=80=94
>
> There are various =E2=80=9CSHOULD=E2=80=9Ds in this section, and I have t=
he same
> comment about all of them: BCP 14 says, about =E2=80=9CSHOULD=E2=80=9D, t=
hat =E2=80=9Cthere
> may exist valid reasons in particular circumstances to ignore a
> particular item, but the full implications must be understood and
> carefully weighed before choosing a different course.=E2=80=9D  I see no
> guidance here to help the reader understand what such circumstances
> and implications are, so I can=E2=80=99t see how an implementer can evalu=
ate
> the situation.  Can you provide any help here?
>
> =3D=3D=3D=3D
>

I checked the base RFC for PCEP - RFC 5440 where notifications are
first defined. They do not use MUST for sending notification in the
PCE overload case [1].

Leaving that aside, in case of auto-bandwidth feature, this
notification is important for scaling. I am inclined to change it to
MUST as suggested.

Co-authors, WG, please speak up if you disagree!!

I have incorporated all other comments in the working copy.

Diff: https://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=3Ddraft-ietf-p=
ce-stateful-pce-auto-bandwidth-11&url2=3Dhttps://raw.githubusercontent.com/=
dhruvdhody/ietf/master/draft-ietf-pce-stateful-pce-auto-bandwidth-12.txt

Thanks!
Dhruv

[1] https://tools.ietf.org/html/rfc5440#section-7.14

> Comment (2019-09-16)
>
> Again, these are purely editorial comments, which need no detailed
> response; please just consider them.
>
> =E2=80=94 Section 1 =E2=80=94
>
>    Over time, based on the varying traffic pattern, an LSP established
>    with a certain bandwidth may require to adjust the bandwidth reserved
>    in the network dynamically.
>
> =E2=80=9Cmay require adjustment of the bandwidth=E2=80=9D
>
>    This is similar to
>    the Passive stateful PCE model, while the Passive stateful PCE uses
>    path request/reply mechanism, the Active stateful PCE uses
>    report/update mechanism.
>
> NEW
>    This is similar to
>    the Passive stateful PCE model: while the Passive stateful PCE uses
>    a path request/reply mechanism, the Active stateful PCE uses a
>    report/update mechanism.
> END
>
>    This document defines the PCEP extensions needed to support Auto-
>    Bandwidth feature in a Active stateful PCE model
>
> NEW
>    This document defines the PCEP extensions needed to support an Auto-
>    Bandwidth feature in an Active stateful PCE model
> END
>
> =E2=80=94 Section 2.3 =E2=80=94
>
>       This value indicates how many times
>       consecutively, the percentage or absolute difference
>
> Add a comma after =E2=80=9Ctimes=E2=80=9D.
>
> =E2=80=94 Section 3 =E2=80=94
>
>    The PCEP speaker supporting this document must have a mechanism
>
> =E2=80=9CA PCEP speaker=E2=80=9D.
>
>    o  It is required to identify and inform the PCC, which LSPs are
>       enabled with Auto-Bandwidth feature.  Not all LSPs in some
>       deployments would like their bandwidth to be dependent on the
>       real-time bandwidth usage but be constant as set by the operator.
>
> NEW
>    o  It is necessary to identify and inform the PCC which LSPs have
>       the Auto-Bandwidth feature enabled.  In some deployments, not
>       all LSPs would like their bandwidth to be dependent on the
>       real-time bandwidth usage, but would rather be constant as set
>       by the operator.
> END
>
> =E2=80=94 Section 4.1 =E2=80=94
>
>    The initial LSP bandwidth can be set to an arbitrary value (including
>    zero), in practice, it can be operator expected value based on design
>    and planning.
>
> NEW
>    The initial LSP bandwidth can be set to an arbitrary value (including
>    zero).  In practice, it can be set to an expected value based on desig=
n
>    and planning.
> END
>
> =E2=80=94 Section 4.2 =E2=80=94
>
>    When the Auto-Bandwidth feature is enabled, the measured traffic rate
>    is periodically sampled at each Sample-Interval (which can be
>    configured by an operator and the default value as 5 minutes) by the
>    PCC, when the PCC is the head-end node of the LSP.  The traffic rate
>    samples are accumulated over the Adjustment-Interval period (in the
>    Up or Down direction) (which can be configured by an operator and the
>    default value as 24 hours).
>
> NEW
>    When the Auto-Bandwidth feature is enabled, the measured traffic rate
>    is periodically sampled at each Sample-Interval by the PCC, when the
>    PCC is the head-end node of the LSP.  The sample interval can be
>    configured by an operator, with a default value of 5 minutes.
>
>    The traffic rate samples are accumulated over the Adjustment-Interval
>    period (in the Up or Down direction).  The period can be configured by
>    an operator, with a default value of 24 hours.
> END
>
>    The PCC, in-charge of calculating the
>    bandwidth to be adjusted, can decide to adjust the bandwidth
>
> Remove both commas.
>
>    Only if the difference between the
>    current bandwidth demand (MaxAvgBw) and the current bandwidth
>    reservation is greater than or equal to the Adjustment-Threshold
>    (percentage or absolute value) (which can be configured by an
>    operator and the default as 5 percentage), the LSP bandwidth is
>    adjusted (upsized) to the current bandwidth demand (MaxAvgBw).
>
> I=E2=80=99m sorry: I can=E2=80=99t made any sense out of this text and, t=
hus, can=E2=80=99t
> suggest a fix.  Please try rephrasing this.  When you do, please make
> it more than one sentence, and please avoid consecutive parenthesized
> phrases, which are awkward.
>
>    However, longer
>    adjustment-interval can result in an undesirable effect
>
> =E2=80=9Ca longer=E2=80=9D
>
>    To avoid this, the
>    Auto-Bandwidth feature may pre-maturely expire the adjustment-
>    interval and adjust the LSP bandwidth
>
> =E2=80=9Cprematurely=E2=80=9D, with no hyphen.
> =E2=80=9Cadjustment interval=E2=80=9D, with no hyphen.
>
> =E2=80=94 Section 5.1 =E2=80=94
>
>    o  The PCEP speaker that does not recognize the extensions defined in
>
> =E2=80=9CA PCEP speaker=E2=80=9D
>
>    o  If the PCEP speaker that supports the extensions defined in this
>
> =E2=80=9CIf a PCEP speaker supports=E2=80=9D
>
> =E2=80=94 Section 5.2 =E2=80=94
>
>    Future specification can define additional sub-TLVs.
>
> =E2=80=9Cspecifications=E2=80=9D
>
>    If sub-TLVs are not present, the
>    default values as specified in this document are used or otherwise
>    based on the local policy are assumed.
>
> I can=E2=80=99t make sense of that sentence; please re-phrase it.
>
> =E2=80=94 Section 5.2.3.2 =E2=80=94
>
>    o  Reserved: SHOULD be set to zero on transmission and MUST be
>       ignored on receipt.
>
> Why is this =E2=80=9CSHOULD=E2=80=9D, when other reserved values have bee=
n =E2=80=9CMUST=E2=80=9D?
>
> (Same comment in 5.2.3.4, 5.2.5.1, 5.2.5.2, 5.2.5.3, and 5.2.5.4.)
>
> =3D=3D=3D=3D
>
> [1] https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-pce-auto-ban=
dwidth/ballot/
> [2] https://mailarchive.ietf.org/arch/browse/pce/


From nobody Mon Sep 16 04:33:48 2019
Return-Path: <adrian@olddog.co.uk>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4EBB120838; Mon, 16 Sep 2019 04:33:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SzLmTo25n8jP; Mon, 16 Sep 2019 04:33:38 -0700 (PDT)
Received: from mta5.iomartmail.com (mta5.iomartmail.com [62.128.193.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91355120019; Mon, 16 Sep 2019 04:33:36 -0700 (PDT)
Received: from vs3.iomartmail.com (vs3.iomartmail.com [10.12.10.124]) by mta5.iomartmail.com (8.14.4/8.14.4) with ESMTP id x8GBWe8G025498; Mon, 16 Sep 2019 12:33:31 +0100
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id C569F22032; Mon, 16 Sep 2019 12:33:30 +0100 (BST)
Received: from asmtp2.iomartmail.com (unknown [10.12.10.249]) by vs3.iomartmail.com (Postfix) with ESMTPS id AF30D2203D; Mon, 16 Sep 2019 12:33:30 +0100 (BST)
Received: from LAPTOPK7AS653V ([87.112.72.158]) (authenticated bits=0) by asmtp2.iomartmail.com (8.14.4/8.14.4) with ESMTP id x8GBXSfU015860 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 16 Sep 2019 12:33:29 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Dhruv Dhody'" <dhruv.ietf@gmail.com>, "'Barry Leiba'" <barryleiba@computer.org>, <pce@ietf.org>
Cc: "'The IESG'" <iesg@ietf.org>, "'pce-chairs'" <pce-chairs@ietf.org>, <draft-ietf-pce-stateful-pce-auto-bandwidth@ietf.org>
References: <CAB75xn5CPpoo=SWGfiDS+jQQ0pr1Z7HeHKjx9prGzb6tH9YxbQ@mail.gmail.com> <CAB75xn6jiNGePOAat_ET-JsPsvuouo8d651GrdjswPjC7OYPWQ@mail.gmail.com>
In-Reply-To: <CAB75xn6jiNGePOAat_ET-JsPsvuouo8d651GrdjswPjC7OYPWQ@mail.gmail.com>
Date: Mon, 16 Sep 2019 12:33:28 +0100
Organization: Old Dog Consulting
Message-ID: <016c01d56c82$903a3620$b0aea260$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQLaJY984CkYp6/h4if5RMNX+4ERwAL9TlnepQzNGiA=
Content-Language: en-gb
X-Originating-IP: 87.112.72.158
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-24914.005
X-TM-AS-Result: No--23.161-10.0-31-10
X-imss-scan-details: No--23.161-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-24914.005
X-TMASE-Result: 10--23.161000-10.000000
X-TMASE-MatchedRID: IeZYkn8zfFq9GVQT/CmkaHFPUrVDm6jthlL5/PVMMhIHdnpVZivvnLCb bOwPG3Amh4QrtA0MYnIUJHq3EzYoRx8tmNEYF19BN19PjPJahlJR3sGN+j7mNN+gRbw3K+dvmwO HFxYq8mfV7VjYFubQMFEaFUDrmPqnPWKLA6/g//vx5KZMlKYS/Q73P4/aDCIFG1VFRGOlP68F/2 gAm/rnq+DYvGkwxz0/arhRRWLyWzEhOgSF6241nbqImyaR0axZ4NNiN6MhlPAK5I+5JVbn7jO+P BlvZU7YAOB9g4xdOhlLSashyfR4h1/JJvf1ahcWLCDCajDZWp1aEfFgComdj5DgR3nlxgB6NmGS wj6QJy+tuxo618zL1cPvxoWsx4RiXhIgqyFXxJe9uqvNJ0+KqilayzmQ9QV0jklQr1R1iSf68RI XoGEMjGZANw4i2FngSdlhYkWanzmMQmg2+WN4OzKVTrGMDe/Di8J8z2fwGac3xO2R3boBWH8N94 053/fN9blF8FoSg7i8J639iEjfqHcxza41jj1KECZm53NHwzVUIaneDj+GOz8fBHJpFUzVsyWAN +6yISLICH7stvZ9Dl6X+V0hPL5ko6RGjAPtMXuqDSBu0tUhr7vGYJkNeu61Ocom8XH3/7JoZEsK cpKKle8BsGvUbOXx9mUl/pj0E70CWAJNioDShW6HurDH4PpPowhSWTqHYRigipjx+cBzOc7ixSB r9wsbdpGsTq/ormLZE+mt+xTnl3bXMG2FSiQ12Hlwa3CYC+SPzv8sr7ayo4H7rHelmEu3L+QPwy flusyL+skqd2bd776UFwxM7gqvNtywwIf5ksWeAiCmPx4NwFkMvWAuahr8m5N2YHMD0b8MyrfP9 j+C1d934/rDAK3zUc1+O1X9AzE=
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/LAmGnFHVJs8CauzVRim4qmjYPMw>
Subject: Re: [Pce] **Barry Leiba's DISCUSS on draft-ietf-pce-stateful-pce-auto-bandwidth**
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Sep 2019 11:33:41 -0000

Top post, historic view.

IIRC the reason for not requiring a Notification in the case of overload =
was that the process of sending a Notification might contribute to the =
overload. And, furthermore, that there might be an attack that leverages =
the need to send a Notification to perpetuate the overload.

I take no position on this: just reporting what is in my memory.

Best,
Adrian

-----Original Message-----
From: Dhruv Dhody <dhruv.ietf@gmail.com>=20
Sent: 16 September 2019 12:21
To: Barry Leiba <barryleiba@computer.org>; pce@ietf.org
Cc: The IESG <iesg@ietf.org>; pce-chairs <pce-chairs@ietf.org>; Farrel =
Adrian <adrian@olddog.co.uk>; =
draft-ietf-pce-stateful-pce-auto-bandwidth@ietf.org
Subject: Re: **Barry Leiba's DISCUSS on =
draft-ietf-pce-stateful-pce-auto-bandwidth**

Hi again!

On Mon, Sep 16, 2019 at 4:48 PM Dhruv Dhody <dhruv.ietf@gmail.com> =
wrote:
>
> Hi Barry, WG,
>
> I saw the DISCUSS [1] in the datatracker but for some reason the email
> never landed in my inbox or the list [2]. I am manually posting it
> here -
>
> =3D=3D=3D=3D
>
> Discuss (2019-09-16)
>
> Thanks for another clear document.  There are some "SHOULD" key words
> in one section that I would like to discuss, and that I think we ought
> to be able to resolve without much difficulty:
>
> =E2=80=94 Section 5.7 =E2=80=94
>
> There are various =E2=80=9CSHOULD=E2=80=9Ds in this section, and I =
have the same
> comment about all of them: BCP 14 says, about =
=E2=80=9CSHOULD=E2=80=9D, that =E2=80=9Cthere
> may exist valid reasons in particular circumstances to ignore a
> particular item, but the full implications must be understood and
> carefully weighed before choosing a different course.=E2=80=9D  I see =
no
> guidance here to help the reader understand what such circumstances
> and implications are, so I can=E2=80=99t see how an implementer can =
evaluate
> the situation.  Can you provide any help here?
>
> =3D=3D=3D=3D
>

I checked the base RFC for PCEP - RFC 5440 where notifications are
first defined. They do not use MUST for sending notification in the
PCE overload case [1].

Leaving that aside, in case of auto-bandwidth feature, this
notification is important for scaling. I am inclined to change it to
MUST as suggested.

Co-authors, WG, please speak up if you disagree!!

I have incorporated all other comments in the working copy.

Diff: =
https://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=3Ddraft-ietf-pce-s=
tateful-pce-auto-bandwidth-11&url2=3Dhttps://raw.githubusercontent.com/dh=
ruvdhody/ietf/master/draft-ietf-pce-stateful-pce-auto-bandwidth-12.txt

Thanks!
Dhruv

[1] https://tools.ietf.org/html/rfc5440#section-7.14

> Comment (2019-09-16)
>
> Again, these are purely editorial comments, which need no detailed
> response; please just consider them.
>
> =E2=80=94 Section 1 =E2=80=94
>
>    Over time, based on the varying traffic pattern, an LSP established
>    with a certain bandwidth may require to adjust the bandwidth =
reserved
>    in the network dynamically.
>
> =E2=80=9Cmay require adjustment of the bandwidth=E2=80=9D
>
>    This is similar to
>    the Passive stateful PCE model, while the Passive stateful PCE uses
>    path request/reply mechanism, the Active stateful PCE uses
>    report/update mechanism.
>
> NEW
>    This is similar to
>    the Passive stateful PCE model: while the Passive stateful PCE uses
>    a path request/reply mechanism, the Active stateful PCE uses a
>    report/update mechanism.
> END
>
>    This document defines the PCEP extensions needed to support Auto-
>    Bandwidth feature in a Active stateful PCE model
>
> NEW
>    This document defines the PCEP extensions needed to support an =
Auto-
>    Bandwidth feature in an Active stateful PCE model
> END
>
> =E2=80=94 Section 2.3 =E2=80=94
>
>       This value indicates how many times
>       consecutively, the percentage or absolute difference
>
> Add a comma after =E2=80=9Ctimes=E2=80=9D.
>
> =E2=80=94 Section 3 =E2=80=94
>
>    The PCEP speaker supporting this document must have a mechanism
>
> =E2=80=9CA PCEP speaker=E2=80=9D.
>
>    o  It is required to identify and inform the PCC, which LSPs are
>       enabled with Auto-Bandwidth feature.  Not all LSPs in some
>       deployments would like their bandwidth to be dependent on the
>       real-time bandwidth usage but be constant as set by the =
operator.
>
> NEW
>    o  It is necessary to identify and inform the PCC which LSPs have
>       the Auto-Bandwidth feature enabled.  In some deployments, not
>       all LSPs would like their bandwidth to be dependent on the
>       real-time bandwidth usage, but would rather be constant as set
>       by the operator.
> END
>
> =E2=80=94 Section 4.1 =E2=80=94
>
>    The initial LSP bandwidth can be set to an arbitrary value =
(including
>    zero), in practice, it can be operator expected value based on =
design
>    and planning.
>
> NEW
>    The initial LSP bandwidth can be set to an arbitrary value =
(including
>    zero).  In practice, it can be set to an expected value based on =
design
>    and planning.
> END
>
> =E2=80=94 Section 4.2 =E2=80=94
>
>    When the Auto-Bandwidth feature is enabled, the measured traffic =
rate
>    is periodically sampled at each Sample-Interval (which can be
>    configured by an operator and the default value as 5 minutes) by =
the
>    PCC, when the PCC is the head-end node of the LSP.  The traffic =
rate
>    samples are accumulated over the Adjustment-Interval period (in the
>    Up or Down direction) (which can be configured by an operator and =
the
>    default value as 24 hours).
>
> NEW
>    When the Auto-Bandwidth feature is enabled, the measured traffic =
rate
>    is periodically sampled at each Sample-Interval by the PCC, when =
the
>    PCC is the head-end node of the LSP.  The sample interval can be
>    configured by an operator, with a default value of 5 minutes.
>
>    The traffic rate samples are accumulated over the =
Adjustment-Interval
>    period (in the Up or Down direction).  The period can be configured =
by
>    an operator, with a default value of 24 hours.
> END
>
>    The PCC, in-charge of calculating the
>    bandwidth to be adjusted, can decide to adjust the bandwidth
>
> Remove both commas.
>
>    Only if the difference between the
>    current bandwidth demand (MaxAvgBw) and the current bandwidth
>    reservation is greater than or equal to the Adjustment-Threshold
>    (percentage or absolute value) (which can be configured by an
>    operator and the default as 5 percentage), the LSP bandwidth is
>    adjusted (upsized) to the current bandwidth demand (MaxAvgBw).
>
> I=E2=80=99m sorry: I can=E2=80=99t made any sense out of this text =
and, thus, can=E2=80=99t
> suggest a fix.  Please try rephrasing this.  When you do, please make
> it more than one sentence, and please avoid consecutive parenthesized
> phrases, which are awkward.
>
>    However, longer
>    adjustment-interval can result in an undesirable effect
>
> =E2=80=9Ca longer=E2=80=9D
>
>    To avoid this, the
>    Auto-Bandwidth feature may pre-maturely expire the adjustment-
>    interval and adjust the LSP bandwidth
>
> =E2=80=9Cprematurely=E2=80=9D, with no hyphen.
> =E2=80=9Cadjustment interval=E2=80=9D, with no hyphen.
>
> =E2=80=94 Section 5.1 =E2=80=94
>
>    o  The PCEP speaker that does not recognize the extensions defined =
in
>
> =E2=80=9CA PCEP speaker=E2=80=9D
>
>    o  If the PCEP speaker that supports the extensions defined in this
>
> =E2=80=9CIf a PCEP speaker supports=E2=80=9D
>
> =E2=80=94 Section 5.2 =E2=80=94
>
>    Future specification can define additional sub-TLVs.
>
> =E2=80=9Cspecifications=E2=80=9D
>
>    If sub-TLVs are not present, the
>    default values as specified in this document are used or otherwise
>    based on the local policy are assumed.
>
> I can=E2=80=99t make sense of that sentence; please re-phrase it.
>
> =E2=80=94 Section 5.2.3.2 =E2=80=94
>
>    o  Reserved: SHOULD be set to zero on transmission and MUST be
>       ignored on receipt.
>
> Why is this =E2=80=9CSHOULD=E2=80=9D, when other reserved values have =
been =E2=80=9CMUST=E2=80=9D?
>
> (Same comment in 5.2.3.4, 5.2.5.1, 5.2.5.2, 5.2.5.3, and 5.2.5.4.)
>
> =3D=3D=3D=3D
>
> [1] =
https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-pce-auto-bandwid=
th/ballot/
> [2] https://mailarchive.ietf.org/arch/browse/pce/


From nobody Mon Sep 16 06:27:34 2019
Return-Path: <lizhenbin@huawei.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7570B12006A; Mon, 16 Sep 2019 06:27:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sxeis5qHde-F; Mon, 16 Sep 2019 06:27:30 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75B7F120046; Mon, 16 Sep 2019 06:27:30 -0700 (PDT)
Received: from LHREML712-CAH.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 8356F9473F273B7445CF; Mon, 16 Sep 2019 14:27:28 +0100 (IST)
Received: from lhreml723-chm.china.huawei.com (10.201.108.74) by LHREML712-CAH.china.huawei.com (10.201.108.35) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 16 Sep 2019 14:27:20 +0100
Received: from lhreml723-chm.china.huawei.com (10.201.108.74) by lhreml723-chm.china.huawei.com (10.201.108.74) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Mon, 16 Sep 2019 14:27:21 +0100
Received: from DGGEMM422-HUB.china.huawei.com (10.1.198.39) by lhreml723-chm.china.huawei.com (10.201.108.74) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1713.5 via Frontend Transport; Mon, 16 Sep 2019 14:27:20 +0100
Received: from DGGEMM532-MBX.china.huawei.com ([169.254.7.237]) by dggemm422-hub.china.huawei.com ([10.1.198.39]) with mapi id 14.03.0439.000; Mon, 16 Sep 2019 21:25:57 +0800
From: Lizhenbin <lizhenbin@huawei.com>
To: "pce@ietf.org" <pce@ietf.org>
CC: pce-chairs <pce-chairs@ietf.org>
Thread-Topic: Adrian stepping down as PCE co-chair
Thread-Index: AdVo28vCYIoHnaEsTjSAQbDA3xY4EADti0Mg
Date: Mon, 16 Sep 2019 13:25:57 +0000
Message-ID: <5A5B4DE12C0DAC44AF501CD9A2B01A8D934AFD42@DGGEMM532-MBX.china.huawei.com>
References: <F64C10EAA68C8044B33656FA214632C8A3A1FDCF@MISOUT7MSGUSRDE.ITServices.sbc.com>
In-Reply-To: <F64C10EAA68C8044B33656FA214632C8A3A1FDCF@MISOUT7MSGUSRDE.ITServices.sbc.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.206.84]
Content-Type: multipart/alternative; boundary="_000_5A5B4DE12C0DAC44AF501CD9A2B01A8D934AFD42DGGEMM532MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/pWRe-36zF529btZIXR-r8TQ1mlM>
Subject: Re: [Pce] Adrian stepping down as PCE co-chair
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Sep 2019 13:27:33 -0000

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

Many thanks to Adrian. Thanks for your effort to guarantee the smooth trans=
ition.

Best Regards,
Zhenbin (Robin)



From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of BRUNGARD, DEBORAH A
Sent: Thursday, September 12, 2019 4:14 AM
To: pce@ietf.org
Cc: pce-chairs <pce-chairs@ietf.org>
Subject: [Pce] Adrian stepping down as PCE co-chair

Hi,

As we noted earlier, Adrian stepped in to help us with the PCE document que=
ue and help bring Dhruv on as a new chair. He has done a fantastic job and =
Dhruv and Julien are now ready to go forward.

We very much appreciate his support and thank him for all his help!

Deborah


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"ZH-CN" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D">Many thanks to Adrian. Thanks for your effort to guarantee the sm=
ooth transition.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D">Best Regards,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D">Zhenbin (Robin)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US">From:</span></b><span lang=
=3D"EN-US"> Pce [mailto:pce-bounces@ietf.org]
<b>On Behalf Of </b>BRUNGARD, DEBORAH A<br>
<b>Sent:</b> Thursday, September 12, 2019 4:14 AM<br>
<b>To:</b> pce@ietf.org<br>
<b>Cc:</b> pce-chairs &lt;pce-chairs@ietf.org&gt;<br>
<b>Subject:</b> [Pce] Adrian stepping down as PCE co-chair<o:p></o:p></span=
></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hi,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">As we noted earlier, Adrian ste=
pped in to help us with the PCE document queue and help bring Dhruv on as a=
 new chair. He has done a fantastic job and Dhruv and Julien are now ready =
to go forward.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">We very much appreciate his sup=
port and thank him for all his help!<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Deborah<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--_000_5A5B4DE12C0DAC44AF501CD9A2B01A8D934AFD42DGGEMM532MBXchi_--


From nobody Mon Sep 16 08:30:30 2019
Return-Path: <rgandhi.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7B8E12084E; Mon, 16 Sep 2019 08:30:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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] 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 MSqNhE46kxme; Mon, 16 Sep 2019 08:30:11 -0700 (PDT)
Received: from mail-lj1-x22b.google.com (mail-lj1-x22b.google.com [IPv6:2a00:1450:4864:20::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 53F66120895; Mon, 16 Sep 2019 08:30:11 -0700 (PDT)
Received: by mail-lj1-x22b.google.com with SMTP id d5so320873lja.10; Mon, 16 Sep 2019 08:30:11 -0700 (PDT)
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=z1RIHUegn/TPAEF52AtpK18jCxF7tnb5MwEogmA1+lM=; b=dFYB2PzGWLJJXNB6QLx3K/4qkspJRarEB+CnuZk4Pv8U2UCh6SKHnt6zqXCIMRet1Y KSViEFm6aBQclPk1CYUhuMUnKAI9/JAaI3rhkrhqMZoo80tAaSupS8d7ijDVudZvxv3u J2Rv1FT8ppd7OMJ9KnM7sIakLbp8Rt7bVgWxX7WEIDi8PSBp/ULbFtwHnIuOtzuwvzGT HEdzJTFWKUr2fuPej8+RfbAJnfumdTgxq+V3ZU9RpbyZpm32lnM0LqI2SLrZoHkSpSqN rTYP/0XMxsPN1zsgiuEc8+63vbYFMRF98XcVJkOuiB75v0PqSa/n4G0BFV36CnvIMZWy gVvg==
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=z1RIHUegn/TPAEF52AtpK18jCxF7tnb5MwEogmA1+lM=; b=IRN8/kcdDZlTgmXlw9lDlzeJCC3M4rzoqGuppTMp/i0/CyM8VgYxkiHAxKKptVuMtK T/jY+Y0hIrBCHc4wIuyakOHs+/q8comZ5KvWSH/EBjn8Be9g95K5f8osveF6peLecFz6 +XYfMF+eqFKdsCKNgrQY8Q9Jq8Q/ebI9b9Wb30AElzaALVkzwxBYyKO7iMFrgGAFZ4G0 jrdk+zFOtFCDC0NIbmpnKLdaxT1qf7eWwbXoNhtoHArCKseiU1w66IDqXi/B4gKc4WwJ CBT5sOv/inWTvLBjD7eqys2HeUuxhWhjMy7Si3BKmnoGllQtM7qTwS1SRoaAXI0ljhGF aeUQ==
X-Gm-Message-State: APjAAAWMFUY28pvBA3RpHquFOplFw6jgcfBSo7gAZGYMN/u0szTvZvPg smdlpVCle4Y4p5k5TOlxrElLWbuaPoH/VF99hw==
X-Google-Smtp-Source: APXvYqzkMHF/WO746Ixu0SWjLzw6WY04PzFkkMRcD+uV72XUTC6abUM/zRKUCrzfOcdt33p68NFOu+oOhzvisaCrXOw=
X-Received: by 2002:a2e:3c14:: with SMTP id j20mr140170lja.84.1568647808518; Mon, 16 Sep 2019 08:30:08 -0700 (PDT)
MIME-Version: 1.0
References: <CAB75xn5CPpoo=SWGfiDS+jQQ0pr1Z7HeHKjx9prGzb6tH9YxbQ@mail.gmail.com> <CAB75xn6jiNGePOAat_ET-JsPsvuouo8d651GrdjswPjC7OYPWQ@mail.gmail.com> <016c01d56c82$903a3620$b0aea260$@olddog.co.uk>
In-Reply-To: <016c01d56c82$903a3620$b0aea260$@olddog.co.uk>
From: Rakesh Gandhi <rgandhi.ietf@gmail.com>
Date: Mon, 16 Sep 2019 11:29:57 -0400
Message-ID: <CAMZsk6ehuyri9aPNNA19unOy9yoOj_i7fob9bRN0EYZWK41bpw@mail.gmail.com>
To: Farrel Adrian <adrian@olddog.co.uk>
Cc: Dhruv Dhody <dhruv.ietf@gmail.com>, Barry Leiba <barryleiba@computer.org>,  pce@ietf.org,  draft-ietf-pce-stateful-pce-auto-bandwidth@ietf.org, The IESG <iesg@ietf.org>,  pce-chairs <pce-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000678da40592ad478e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/3NtH-QDGqD7X2QDZoNDl6fnNZBY>
Subject: Re: [Pce] **Barry Leiba's DISCUSS on draft-ietf-pce-stateful-pce-auto-bandwidth**
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Sep 2019 15:30:17 -0000

--000000000000678da40592ad478e
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Dhruv,
If the node is overloaded, it may not be able to send the notification, may
be too busy completing the work. "SHOULD" seems reasonable for this
notification as well.

Thanks Adrian for your view.

Thanks,
Rakesh


On Mon, Sep 16, 2019 at 7:33 AM Adrian Farrel <adrian@olddog.co.uk> wrote:

> Top post, historic view.
>
> IIRC the reason for not requiring a Notification in the case of overload
> was that the process of sending a Notification might contribute to the
> overload. And, furthermore, that there might be an attack that leverages
> the need to send a Notification to perpetuate the overload.
>
> I take no position on this: just reporting what is in my memory.
>
> Best,
> Adrian
>
> -----Original Message-----
> From: Dhruv Dhody <dhruv.ietf@gmail.com>
> Sent: 16 September 2019 12:21
> To: Barry Leiba <barryleiba@computer.org>; pce@ietf.org
> Cc: The IESG <iesg@ietf.org>; pce-chairs <pce-chairs@ietf.org>; Farrel
> Adrian <adrian@olddog.co.uk>;
> draft-ietf-pce-stateful-pce-auto-bandwidth@ietf.org
> Subject: Re: **Barry Leiba's DISCUSS on
> draft-ietf-pce-stateful-pce-auto-bandwidth**
>
> Hi again!
>
> On Mon, Sep 16, 2019 at 4:48 PM Dhruv Dhody <dhruv.ietf@gmail.com> wrote:
> >
> > Hi Barry, WG,
> >
> > I saw the DISCUSS [1] in the datatracker but for some reason the email
> > never landed in my inbox or the list [2]. I am manually posting it
> > here -
> >
> > =3D=3D=3D=3D
> >
> > Discuss (2019-09-16)
> >
> > Thanks for another clear document.  There are some "SHOULD" key words
> > in one section that I would like to discuss, and that I think we ought
> > to be able to resolve without much difficulty:
> >
> > =E2=80=94 Section 5.7 =E2=80=94
> >
> > There are various =E2=80=9CSHOULD=E2=80=9Ds in this section, and I have=
 the same
> > comment about all of them: BCP 14 says, about =E2=80=9CSHOULD=E2=80=9D,=
 that =E2=80=9Cthere
> > may exist valid reasons in particular circumstances to ignore a
> > particular item, but the full implications must be understood and
> > carefully weighed before choosing a different course.=E2=80=9D  I see n=
o
> > guidance here to help the reader understand what such circumstances
> > and implications are, so I can=E2=80=99t see how an implementer can eva=
luate
> > the situation.  Can you provide any help here?
> >
> > =3D=3D=3D=3D
> >
>
> I checked the base RFC for PCEP - RFC 5440 where notifications are
> first defined. They do not use MUST for sending notification in the
> PCE overload case [1].
>
> Leaving that aside, in case of auto-bandwidth feature, this
> notification is important for scaling. I am inclined to change it to
> MUST as suggested.
>
> Co-authors, WG, please speak up if you disagree!!
>
> I have incorporated all other comments in the working copy.
>
> Diff:
> https://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=3Ddraft-ietf-pce-s=
tateful-pce-auto-bandwidth-11&url2=3Dhttps://raw.githubusercontent.com/dhru=
vdhody/ietf/master/draft-ietf-pce-stateful-pce-auto-bandwidth-12.txt
>
> Thanks!
> Dhruv
>
> [1] https://tools.ietf.org/html/rfc5440#section-7.14
>
> > Comment (2019-09-16)
> >
> > Again, these are purely editorial comments, which need no detailed
> > response; please just consider them.
> >
> > =E2=80=94 Section 1 =E2=80=94
> >
> >    Over time, based on the varying traffic pattern, an LSP established
> >    with a certain bandwidth may require to adjust the bandwidth reserve=
d
> >    in the network dynamically.
> >
> > =E2=80=9Cmay require adjustment of the bandwidth=E2=80=9D
> >
> >    This is similar to
> >    the Passive stateful PCE model, while the Passive stateful PCE uses
> >    path request/reply mechanism, the Active stateful PCE uses
> >    report/update mechanism.
> >
> > NEW
> >    This is similar to
> >    the Passive stateful PCE model: while the Passive stateful PCE uses
> >    a path request/reply mechanism, the Active stateful PCE uses a
> >    report/update mechanism.
> > END
> >
> >    This document defines the PCEP extensions needed to support Auto-
> >    Bandwidth feature in a Active stateful PCE model
> >
> > NEW
> >    This document defines the PCEP extensions needed to support an Auto-
> >    Bandwidth feature in an Active stateful PCE model
> > END
> >
> > =E2=80=94 Section 2.3 =E2=80=94
> >
> >       This value indicates how many times
> >       consecutively, the percentage or absolute difference
> >
> > Add a comma after =E2=80=9Ctimes=E2=80=9D.
> >
> > =E2=80=94 Section 3 =E2=80=94
> >
> >    The PCEP speaker supporting this document must have a mechanism
> >
> > =E2=80=9CA PCEP speaker=E2=80=9D.
> >
> >    o  It is required to identify and inform the PCC, which LSPs are
> >       enabled with Auto-Bandwidth feature.  Not all LSPs in some
> >       deployments would like their bandwidth to be dependent on the
> >       real-time bandwidth usage but be constant as set by the operator.
> >
> > NEW
> >    o  It is necessary to identify and inform the PCC which LSPs have
> >       the Auto-Bandwidth feature enabled.  In some deployments, not
> >       all LSPs would like their bandwidth to be dependent on the
> >       real-time bandwidth usage, but would rather be constant as set
> >       by the operator.
> > END
> >
> > =E2=80=94 Section 4.1 =E2=80=94
> >
> >    The initial LSP bandwidth can be set to an arbitrary value (includin=
g
> >    zero), in practice, it can be operator expected value based on desig=
n
> >    and planning.
> >
> > NEW
> >    The initial LSP bandwidth can be set to an arbitrary value (includin=
g
> >    zero).  In practice, it can be set to an expected value based on
> design
> >    and planning.
> > END
> >
> > =E2=80=94 Section 4.2 =E2=80=94
> >
> >    When the Auto-Bandwidth feature is enabled, the measured traffic rat=
e
> >    is periodically sampled at each Sample-Interval (which can be
> >    configured by an operator and the default value as 5 minutes) by the
> >    PCC, when the PCC is the head-end node of the LSP.  The traffic rate
> >    samples are accumulated over the Adjustment-Interval period (in the
> >    Up or Down direction) (which can be configured by an operator and th=
e
> >    default value as 24 hours).
> >
> > NEW
> >    When the Auto-Bandwidth feature is enabled, the measured traffic rat=
e
> >    is periodically sampled at each Sample-Interval by the PCC, when the
> >    PCC is the head-end node of the LSP.  The sample interval can be
> >    configured by an operator, with a default value of 5 minutes.
> >
> >    The traffic rate samples are accumulated over the Adjustment-Interva=
l
> >    period (in the Up or Down direction).  The period can be configured =
by
> >    an operator, with a default value of 24 hours.
> > END
> >
> >    The PCC, in-charge of calculating the
> >    bandwidth to be adjusted, can decide to adjust the bandwidth
> >
> > Remove both commas.
> >
> >    Only if the difference between the
> >    current bandwidth demand (MaxAvgBw) and the current bandwidth
> >    reservation is greater than or equal to the Adjustment-Threshold
> >    (percentage or absolute value) (which can be configured by an
> >    operator and the default as 5 percentage), the LSP bandwidth is
> >    adjusted (upsized) to the current bandwidth demand (MaxAvgBw).
> >
> > I=E2=80=99m sorry: I can=E2=80=99t made any sense out of this text and,=
 thus, can=E2=80=99t
> > suggest a fix.  Please try rephrasing this.  When you do, please make
> > it more than one sentence, and please avoid consecutive parenthesized
> > phrases, which are awkward.
> >
> >    However, longer
> >    adjustment-interval can result in an undesirable effect
> >
> > =E2=80=9Ca longer=E2=80=9D
> >
> >    To avoid this, the
> >    Auto-Bandwidth feature may pre-maturely expire the adjustment-
> >    interval and adjust the LSP bandwidth
> >
> > =E2=80=9Cprematurely=E2=80=9D, with no hyphen.
> > =E2=80=9Cadjustment interval=E2=80=9D, with no hyphen.
> >
> > =E2=80=94 Section 5.1 =E2=80=94
> >
> >    o  The PCEP speaker that does not recognize the extensions defined i=
n
> >
> > =E2=80=9CA PCEP speaker=E2=80=9D
> >
> >    o  If the PCEP speaker that supports the extensions defined in this
> >
> > =E2=80=9CIf a PCEP speaker supports=E2=80=9D
> >
> > =E2=80=94 Section 5.2 =E2=80=94
> >
> >    Future specification can define additional sub-TLVs.
> >
> > =E2=80=9Cspecifications=E2=80=9D
> >
> >    If sub-TLVs are not present, the
> >    default values as specified in this document are used or otherwise
> >    based on the local policy are assumed.
> >
> > I can=E2=80=99t make sense of that sentence; please re-phrase it.
> >
> > =E2=80=94 Section 5.2.3.2 =E2=80=94
> >
> >    o  Reserved: SHOULD be set to zero on transmission and MUST be
> >       ignored on receipt.
> >
> > Why is this =E2=80=9CSHOULD=E2=80=9D, when other reserved values have b=
een =E2=80=9CMUST=E2=80=9D?
> >
> > (Same comment in 5.2.3.4, 5.2.5.1, 5.2.5.2, 5.2.5.3, and 5.2.5.4.)
> >
> > =3D=3D=3D=3D
> >
> > [1]
> https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-pce-auto-bandwid=
th/ballot/
> > [2] https://mailarchive.ietf.org/arch/browse/pce/
>
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce
>

--000000000000678da40592ad478e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi Dhruv,</div><div>If the node is overloaded, it may=
 not be able to send the notification, may be too busy completing the work.=
 &quot;SHOULD&quot; seems reasonable for this notification as well.</div><d=
iv><br></div><div>Thanks Adrian for your view.</div><div><br></div><div>Tha=
nks,</div><div>Rakesh</div><div><br></div></div><br><div class=3D"gmail_quo=
te"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Sep 16, 2019 at 7:33 AM A=
drian Farrel &lt;<a href=3D"mailto:adrian@olddog.co.uk">adrian@olddog.co.uk=
</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">=
Top post, historic view.<br>
<br>
IIRC the reason for not requiring a Notification in the case of overload wa=
s that the process of sending a Notification might contribute to the overlo=
ad. And, furthermore, that there might be an attack that leverages the need=
 to send a Notification to perpetuate the overload.<br>
<br>
I take no position on this: just reporting what is in my memory.<br>
<br>
Best,<br>
Adrian<br>
<br>
-----Original Message-----<br>
From: Dhruv Dhody &lt;<a href=3D"mailto:dhruv.ietf@gmail.com" target=3D"_bl=
ank">dhruv.ietf@gmail.com</a>&gt; <br>
Sent: 16 September 2019 12:21<br>
To: Barry Leiba &lt;<a href=3D"mailto:barryleiba@computer.org" target=3D"_b=
lank">barryleiba@computer.org</a>&gt;; <a href=3D"mailto:pce@ietf.org" targ=
et=3D"_blank">pce@ietf.org</a><br>
Cc: The IESG &lt;<a href=3D"mailto:iesg@ietf.org" target=3D"_blank">iesg@ie=
tf.org</a>&gt;; pce-chairs &lt;<a href=3D"mailto:pce-chairs@ietf.org" targe=
t=3D"_blank">pce-chairs@ietf.org</a>&gt;; Farrel Adrian &lt;<a href=3D"mail=
to:adrian@olddog.co.uk" target=3D"_blank">adrian@olddog.co.uk</a>&gt;; <a h=
ref=3D"mailto:draft-ietf-pce-stateful-pce-auto-bandwidth@ietf.org" target=
=3D"_blank">draft-ietf-pce-stateful-pce-auto-bandwidth@ietf.org</a><br>
Subject: Re: **Barry Leiba&#39;s DISCUSS on draft-ietf-pce-stateful-pce-aut=
o-bandwidth**<br>
<br>
Hi again!<br>
<br>
On Mon, Sep 16, 2019 at 4:48 PM Dhruv Dhody &lt;<a href=3D"mailto:dhruv.iet=
f@gmail.com" target=3D"_blank">dhruv.ietf@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Hi Barry, WG,<br>
&gt;<br>
&gt; I saw the DISCUSS [1] in the datatracker but for some reason the email=
<br>
&gt; never landed in my inbox or the list [2]. I am manually posting it<br>
&gt; here -<br>
&gt;<br>
&gt; =3D=3D=3D=3D<br>
&gt;<br>
&gt; Discuss (2019-09-16)<br>
&gt;<br>
&gt; Thanks for another clear document.=C2=A0 There are some &quot;SHOULD&q=
uot; key words<br>
&gt; in one section that I would like to discuss, and that I think we ought=
<br>
&gt; to be able to resolve without much difficulty:<br>
&gt;<br>
&gt; =E2=80=94 Section 5.7 =E2=80=94<br>
&gt;<br>
&gt; There are various =E2=80=9CSHOULD=E2=80=9Ds in this section, and I hav=
e the same<br>
&gt; comment about all of them: BCP 14 says, about =E2=80=9CSHOULD=E2=80=9D=
, that =E2=80=9Cthere<br>
&gt; may exist valid reasons in particular circumstances to ignore a<br>
&gt; particular item, but the full implications must be understood and<br>
&gt; carefully weighed before choosing a different course.=E2=80=9D=C2=A0 I=
 see no<br>
&gt; guidance here to help the reader understand what such circumstances<br=
>
&gt; and implications are, so I can=E2=80=99t see how an implementer can ev=
aluate<br>
&gt; the situation.=C2=A0 Can you provide any help here?<br>
&gt;<br>
&gt; =3D=3D=3D=3D<br>
&gt;<br>
<br>
I checked the base RFC for PCEP - RFC 5440 where notifications are<br>
first defined. They do not use MUST for sending notification in the<br>
PCE overload case [1].<br>
<br>
Leaving that aside, in case of auto-bandwidth feature, this<br>
notification is important for scaling. I am inclined to change it to<br>
MUST as suggested.<br>
<br>
Co-authors, WG, please speak up if you disagree!!<br>
<br>
I have incorporated all other comments in the working copy.<br>
<br>
Diff: <a href=3D"https://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=3Dd=
raft-ietf-pce-stateful-pce-auto-bandwidth-11&amp;url2=3Dhttps://raw.githubu=
sercontent.com/dhruvdhody/ietf/master/draft-ietf-pce-stateful-pce-auto-band=
width-12.txt" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/t=
ools/rfcdiff/rfcdiff.pyht?url1=3Ddraft-ietf-pce-stateful-pce-auto-bandwidth=
-11&amp;url2=3Dhttps://raw.githubusercontent.com/dhruvdhody/ietf/master/dra=
ft-ietf-pce-stateful-pce-auto-bandwidth-12.txt</a><br>
<br>
Thanks!<br>
Dhruv<br>
<br>
[1] <a href=3D"https://tools.ietf.org/html/rfc5440#section-7.14" rel=3D"nor=
eferrer" target=3D"_blank">https://tools.ietf.org/html/rfc5440#section-7.14=
</a><br>
<br>
&gt; Comment (2019-09-16)<br>
&gt;<br>
&gt; Again, these are purely editorial comments, which need no detailed<br>
&gt; response; please just consider them.<br>
&gt;<br>
&gt; =E2=80=94 Section 1 =E2=80=94<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 Over time, based on the varying traffic pattern, an LSP e=
stablished<br>
&gt;=C2=A0 =C2=A0 with a certain bandwidth may require to adjust the bandwi=
dth reserved<br>
&gt;=C2=A0 =C2=A0 in the network dynamically.<br>
&gt;<br>
&gt; =E2=80=9Cmay require adjustment of the bandwidth=E2=80=9D<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 This is similar to<br>
&gt;=C2=A0 =C2=A0 the Passive stateful PCE model, while the Passive statefu=
l PCE uses<br>
&gt;=C2=A0 =C2=A0 path request/reply mechanism, the Active stateful PCE use=
s<br>
&gt;=C2=A0 =C2=A0 report/update mechanism.<br>
&gt;<br>
&gt; NEW<br>
&gt;=C2=A0 =C2=A0 This is similar to<br>
&gt;=C2=A0 =C2=A0 the Passive stateful PCE model: while the Passive statefu=
l PCE uses<br>
&gt;=C2=A0 =C2=A0 a path request/reply mechanism, the Active stateful PCE u=
ses a<br>
&gt;=C2=A0 =C2=A0 report/update mechanism.<br>
&gt; END<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 This document defines the PCEP extensions needed to suppo=
rt Auto-<br>
&gt;=C2=A0 =C2=A0 Bandwidth feature in a Active stateful PCE model<br>
&gt;<br>
&gt; NEW<br>
&gt;=C2=A0 =C2=A0 This document defines the PCEP extensions needed to suppo=
rt an Auto-<br>
&gt;=C2=A0 =C2=A0 Bandwidth feature in an Active stateful PCE model<br>
&gt; END<br>
&gt;<br>
&gt; =E2=80=94 Section 2.3 =E2=80=94<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0This value indicates how many times<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0consecutively, the percentage or absolute di=
fference<br>
&gt;<br>
&gt; Add a comma after =E2=80=9Ctimes=E2=80=9D.<br>
&gt;<br>
&gt; =E2=80=94 Section 3 =E2=80=94<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 The PCEP speaker supporting this document must have a mec=
hanism<br>
&gt;<br>
&gt; =E2=80=9CA PCEP speaker=E2=80=9D.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 o=C2=A0 It is required to identify and inform the PCC, wh=
ich LSPs are<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0enabled with Auto-Bandwidth feature.=C2=A0 N=
ot all LSPs in some<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0deployments would like their bandwidth to be=
 dependent on the<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0real-time bandwidth usage but be constant as=
 set by the operator.<br>
&gt;<br>
&gt; NEW<br>
&gt;=C2=A0 =C2=A0 o=C2=A0 It is necessary to identify and inform the PCC wh=
ich LSPs have<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0the Auto-Bandwidth feature enabled.=C2=A0 In=
 some deployments, not<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0all LSPs would like their bandwidth to be de=
pendent on the<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0real-time bandwidth usage, but would rather =
be constant as set<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0by the operator.<br>
&gt; END<br>
&gt;<br>
&gt; =E2=80=94 Section 4.1 =E2=80=94<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 The initial LSP bandwidth can be set to an arbitrary valu=
e (including<br>
&gt;=C2=A0 =C2=A0 zero), in practice, it can be operator expected value bas=
ed on design<br>
&gt;=C2=A0 =C2=A0 and planning.<br>
&gt;<br>
&gt; NEW<br>
&gt;=C2=A0 =C2=A0 The initial LSP bandwidth can be set to an arbitrary valu=
e (including<br>
&gt;=C2=A0 =C2=A0 zero).=C2=A0 In practice, it can be set to an expected va=
lue based on design<br>
&gt;=C2=A0 =C2=A0 and planning.<br>
&gt; END<br>
&gt;<br>
&gt; =E2=80=94 Section 4.2 =E2=80=94<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 When the Auto-Bandwidth feature is enabled, the measured =
traffic rate<br>
&gt;=C2=A0 =C2=A0 is periodically sampled at each Sample-Interval (which ca=
n be<br>
&gt;=C2=A0 =C2=A0 configured by an operator and the default value as 5 minu=
tes) by the<br>
&gt;=C2=A0 =C2=A0 PCC, when the PCC is the head-end node of the LSP.=C2=A0 =
The traffic rate<br>
&gt;=C2=A0 =C2=A0 samples are accumulated over the Adjustment-Interval peri=
od (in the<br>
&gt;=C2=A0 =C2=A0 Up or Down direction) (which can be configured by an oper=
ator and the<br>
&gt;=C2=A0 =C2=A0 default value as 24 hours).<br>
&gt;<br>
&gt; NEW<br>
&gt;=C2=A0 =C2=A0 When the Auto-Bandwidth feature is enabled, the measured =
traffic rate<br>
&gt;=C2=A0 =C2=A0 is periodically sampled at each Sample-Interval by the PC=
C, when the<br>
&gt;=C2=A0 =C2=A0 PCC is the head-end node of the LSP.=C2=A0 The sample int=
erval can be<br>
&gt;=C2=A0 =C2=A0 configured by an operator, with a default value of 5 minu=
tes.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 The traffic rate samples are accumulated over the Adjustm=
ent-Interval<br>
&gt;=C2=A0 =C2=A0 period (in the Up or Down direction).=C2=A0 The period ca=
n be configured by<br>
&gt;=C2=A0 =C2=A0 an operator, with a default value of 24 hours.<br>
&gt; END<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 The PCC, in-charge of calculating the<br>
&gt;=C2=A0 =C2=A0 bandwidth to be adjusted, can decide to adjust the bandwi=
dth<br>
&gt;<br>
&gt; Remove both commas.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 Only if the difference between the<br>
&gt;=C2=A0 =C2=A0 current bandwidth demand (MaxAvgBw) and the current bandw=
idth<br>
&gt;=C2=A0 =C2=A0 reservation is greater than or equal to the Adjustment-Th=
reshold<br>
&gt;=C2=A0 =C2=A0 (percentage or absolute value) (which can be configured b=
y an<br>
&gt;=C2=A0 =C2=A0 operator and the default as 5 percentage), the LSP bandwi=
dth is<br>
&gt;=C2=A0 =C2=A0 adjusted (upsized) to the current bandwidth demand (MaxAv=
gBw).<br>
&gt;<br>
&gt; I=E2=80=99m sorry: I can=E2=80=99t made any sense out of this text and=
, thus, can=E2=80=99t<br>
&gt; suggest a fix.=C2=A0 Please try rephrasing this.=C2=A0 When you do, pl=
ease make<br>
&gt; it more than one sentence, and please avoid consecutive parenthesized<=
br>
&gt; phrases, which are awkward.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 However, longer<br>
&gt;=C2=A0 =C2=A0 adjustment-interval can result in an undesirable effect<b=
r>
&gt;<br>
&gt; =E2=80=9Ca longer=E2=80=9D<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 To avoid this, the<br>
&gt;=C2=A0 =C2=A0 Auto-Bandwidth feature may pre-maturely expire the adjust=
ment-<br>
&gt;=C2=A0 =C2=A0 interval and adjust the LSP bandwidth<br>
&gt;<br>
&gt; =E2=80=9Cprematurely=E2=80=9D, with no hyphen.<br>
&gt; =E2=80=9Cadjustment interval=E2=80=9D, with no hyphen.<br>
&gt;<br>
&gt; =E2=80=94 Section 5.1 =E2=80=94<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 o=C2=A0 The PCEP speaker that does not recognize the exte=
nsions defined in<br>
&gt;<br>
&gt; =E2=80=9CA PCEP speaker=E2=80=9D<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 o=C2=A0 If the PCEP speaker that supports the extensions =
defined in this<br>
&gt;<br>
&gt; =E2=80=9CIf a PCEP speaker supports=E2=80=9D<br>
&gt;<br>
&gt; =E2=80=94 Section 5.2 =E2=80=94<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 Future specification can define additional sub-TLVs.<br>
&gt;<br>
&gt; =E2=80=9Cspecifications=E2=80=9D<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 If sub-TLVs are not present, the<br>
&gt;=C2=A0 =C2=A0 default values as specified in this document are used or =
otherwise<br>
&gt;=C2=A0 =C2=A0 based on the local policy are assumed.<br>
&gt;<br>
&gt; I can=E2=80=99t make sense of that sentence; please re-phrase it.<br>
&gt;<br>
&gt; =E2=80=94 Section 5.2.3.2 =E2=80=94<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 o=C2=A0 Reserved: SHOULD be set to zero on transmission a=
nd MUST be<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0ignored on receipt.<br>
&gt;<br>
&gt; Why is this =E2=80=9CSHOULD=E2=80=9D, when other reserved values have =
been =E2=80=9CMUST=E2=80=9D?<br>
&gt;<br>
&gt; (Same comment in 5.2.3.4, 5.2.5.1, 5.2.5.2, 5.2.5.3, and 5.2.5.4.)<br>
&gt;<br>
&gt; =3D=3D=3D=3D<br>
&gt;<br>
&gt; [1] <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-pce-statefu=
l-pce-auto-bandwidth/ballot/" rel=3D"noreferrer" target=3D"_blank">https://=
datatracker.ietf.org/doc/draft-ietf-pce-stateful-pce-auto-bandwidth/ballot/=
</a><br>
&gt; [2] <a href=3D"https://mailarchive.ietf.org/arch/browse/pce/" rel=3D"n=
oreferrer" target=3D"_blank">https://mailarchive.ietf.org/arch/browse/pce/<=
/a><br>
<br>
_______________________________________________<br>
Pce mailing list<br>
<a href=3D"mailto:Pce@ietf.org" target=3D"_blank">Pce@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/pce" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/pce</a><br>
</blockquote></div>

--000000000000678da40592ad478e--


From nobody Mon Sep 16 09:00:43 2019
Return-Path: <barryleiba@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 321971208C9; Mon, 16 Sep 2019 09:00:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.923
X-Spam-Level: 
X-Spam-Status: No, score=-1.923 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.026, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KXJKPaK946YV; Mon, 16 Sep 2019 09:00:17 -0700 (PDT)
Received: from mail-io1-f41.google.com (mail-io1-f41.google.com [209.85.166.41]) (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 5FEEF120889; Mon, 16 Sep 2019 09:00:17 -0700 (PDT)
Received: by mail-io1-f41.google.com with SMTP id q1so331801ion.1; Mon, 16 Sep 2019 09:00:17 -0700 (PDT)
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:content-transfer-encoding; bh=0Roo/PreTycSJKmkDM4Ajn5W5xd/QHeysxDM17kF1Mc=; b=L83p4FqZ2BHxZVGSdOn/eXXgyaCA3nRcGDIqMgOpQXbQeUFmJj3aJ7vZ72BUHSIExU mJ0nqaLkGm0CeEeFrc6pNaDRbAwY3IwSHcxFc8VqQhTFvzinZehcJqpbgKRuCsu+i5FC xQgjv7TokA0co0zH/UbdBHE3xJbbmsnkF82YFdS1fujAQNhvYjaIpfCgUDODosYbOwgy PdU51yRSdR908lJKRaRRxFMriTqi9xc5HFEplAFMnG0FdIf9H6gRkN8GiKLKhS6/eynT mMdJl1DU/hykiWI2VpSOfQjnSUZowrEBcxS+jOJqGcr0wHFZ3S2BBN53OUWJJf4iTrKb pj3g==
X-Gm-Message-State: APjAAAXCPIPsOt7sYRjT1oFmiJ1xp9het8QxrFJFJxL+SHC0fgegL2md eiIHI/EY8kiSbLtKL+jubrfw8aEtXdJdFLy5JBN5zw==
X-Google-Smtp-Source: APXvYqwpSOelqdvdA+TeMJbXvTdHENJ2XSCxOkMiVM+u8OGmRQzfDTyfU4DPmOzYIA7V7EKnnrOVHBt9UoM17N79UjM=
X-Received: by 2002:a6b:1787:: with SMTP id 129mr193417iox.140.1568649616325;  Mon, 16 Sep 2019 09:00:16 -0700 (PDT)
MIME-Version: 1.0
References: <CAB75xn5CPpoo=SWGfiDS+jQQ0pr1Z7HeHKjx9prGzb6tH9YxbQ@mail.gmail.com> <CAB75xn6jiNGePOAat_ET-JsPsvuouo8d651GrdjswPjC7OYPWQ@mail.gmail.com>
In-Reply-To: <CAB75xn6jiNGePOAat_ET-JsPsvuouo8d651GrdjswPjC7OYPWQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Mon, 16 Sep 2019 09:00:05 -0700
Message-ID: <CALaySJJ2dkCLm9zdfRFYzU5QRve41UhoX9RYPxvkvpeZJnByZg@mail.gmail.com>
To: Dhruv Dhody <dhruv.ietf@gmail.com>
Cc: pce@ietf.org, The IESG <iesg@ietf.org>, pce-chairs <pce-chairs@ietf.org>,  Farrel Adrian <adrian@olddog.co.uk>, draft-ietf-pce-stateful-pce-auto-bandwidth@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/7pTFx0UX2-HKikAodV8Kz_iQE4o>
Subject: Re: [Pce] **Barry Leiba's DISCUSS on draft-ietf-pce-stateful-pce-auto-bandwidth**
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Sep 2019 16:00:31 -0000

Thanks for the reply, Dhruv.

To be clear, I am NOT suggesting changing it to MUST (though that
could be a perfectly good outcome of the discussion).  I am suggesting
that if it remains as SHOULD, there has to be some explanation of what
the constraints are and what interoperability or security issues could
arise if an implementation doesn't do it that way.

Barry

On Mon, Sep 16, 2019 at 4:21 AM Dhruv Dhody <dhruv.ietf@gmail.com> wrote:
>
> Hi again!
>
> On Mon, Sep 16, 2019 at 4:48 PM Dhruv Dhody <dhruv.ietf@gmail.com> wrote:
> >
> > Hi Barry, WG,
> >
> > I saw the DISCUSS [1] in the datatracker but for some reason the email
> > never landed in my inbox or the list [2]. I am manually posting it
> > here -
> >
> > =3D=3D=3D=3D
> >
> > Discuss (2019-09-16)
> >
> > Thanks for another clear document.  There are some "SHOULD" key words
> > in one section that I would like to discuss, and that I think we ought
> > to be able to resolve without much difficulty:
> >
> > =E2=80=94 Section 5.7 =E2=80=94
> >
> > There are various =E2=80=9CSHOULD=E2=80=9Ds in this section, and I have=
 the same
> > comment about all of them: BCP 14 says, about =E2=80=9CSHOULD=E2=80=9D,=
 that =E2=80=9Cthere
> > may exist valid reasons in particular circumstances to ignore a
> > particular item, but the full implications must be understood and
> > carefully weighed before choosing a different course.=E2=80=9D  I see n=
o
> > guidance here to help the reader understand what such circumstances
> > and implications are, so I can=E2=80=99t see how an implementer can eva=
luate
> > the situation.  Can you provide any help here?
> >
> > =3D=3D=3D=3D
> >
>
> I checked the base RFC for PCEP - RFC 5440 where notifications are
> first defined. They do not use MUST for sending notification in the
> PCE overload case [1].
>
> Leaving that aside, in case of auto-bandwidth feature, this
> notification is important for scaling. I am inclined to change it to
> MUST as suggested.
>
> Co-authors, WG, please speak up if you disagree!!
>
> I have incorporated all other comments in the working copy.
>
> Diff: https://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=3Ddraft-ietf=
-pce-stateful-pce-auto-bandwidth-11&url2=3Dhttps://raw.githubusercontent.co=
m/dhruvdhody/ietf/master/draft-ietf-pce-stateful-pce-auto-bandwidth-12.txt
>
> Thanks!
> Dhruv
>
> [1] https://tools.ietf.org/html/rfc5440#section-7.14
>
> > Comment (2019-09-16)
> >
> > Again, these are purely editorial comments, which need no detailed
> > response; please just consider them.
> >
> > =E2=80=94 Section 1 =E2=80=94
> >
> >    Over time, based on the varying traffic pattern, an LSP established
> >    with a certain bandwidth may require to adjust the bandwidth reserve=
d
> >    in the network dynamically.
> >
> > =E2=80=9Cmay require adjustment of the bandwidth=E2=80=9D
> >
> >    This is similar to
> >    the Passive stateful PCE model, while the Passive stateful PCE uses
> >    path request/reply mechanism, the Active stateful PCE uses
> >    report/update mechanism.
> >
> > NEW
> >    This is similar to
> >    the Passive stateful PCE model: while the Passive stateful PCE uses
> >    a path request/reply mechanism, the Active stateful PCE uses a
> >    report/update mechanism.
> > END
> >
> >    This document defines the PCEP extensions needed to support Auto-
> >    Bandwidth feature in a Active stateful PCE model
> >
> > NEW
> >    This document defines the PCEP extensions needed to support an Auto-
> >    Bandwidth feature in an Active stateful PCE model
> > END
> >
> > =E2=80=94 Section 2.3 =E2=80=94
> >
> >       This value indicates how many times
> >       consecutively, the percentage or absolute difference
> >
> > Add a comma after =E2=80=9Ctimes=E2=80=9D.
> >
> > =E2=80=94 Section 3 =E2=80=94
> >
> >    The PCEP speaker supporting this document must have a mechanism
> >
> > =E2=80=9CA PCEP speaker=E2=80=9D.
> >
> >    o  It is required to identify and inform the PCC, which LSPs are
> >       enabled with Auto-Bandwidth feature.  Not all LSPs in some
> >       deployments would like their bandwidth to be dependent on the
> >       real-time bandwidth usage but be constant as set by the operator.
> >
> > NEW
> >    o  It is necessary to identify and inform the PCC which LSPs have
> >       the Auto-Bandwidth feature enabled.  In some deployments, not
> >       all LSPs would like their bandwidth to be dependent on the
> >       real-time bandwidth usage, but would rather be constant as set
> >       by the operator.
> > END
> >
> > =E2=80=94 Section 4.1 =E2=80=94
> >
> >    The initial LSP bandwidth can be set to an arbitrary value (includin=
g
> >    zero), in practice, it can be operator expected value based on desig=
n
> >    and planning.
> >
> > NEW
> >    The initial LSP bandwidth can be set to an arbitrary value (includin=
g
> >    zero).  In practice, it can be set to an expected value based on des=
ign
> >    and planning.
> > END
> >
> > =E2=80=94 Section 4.2 =E2=80=94
> >
> >    When the Auto-Bandwidth feature is enabled, the measured traffic rat=
e
> >    is periodically sampled at each Sample-Interval (which can be
> >    configured by an operator and the default value as 5 minutes) by the
> >    PCC, when the PCC is the head-end node of the LSP.  The traffic rate
> >    samples are accumulated over the Adjustment-Interval period (in the
> >    Up or Down direction) (which can be configured by an operator and th=
e
> >    default value as 24 hours).
> >
> > NEW
> >    When the Auto-Bandwidth feature is enabled, the measured traffic rat=
e
> >    is periodically sampled at each Sample-Interval by the PCC, when the
> >    PCC is the head-end node of the LSP.  The sample interval can be
> >    configured by an operator, with a default value of 5 minutes.
> >
> >    The traffic rate samples are accumulated over the Adjustment-Interva=
l
> >    period (in the Up or Down direction).  The period can be configured =
by
> >    an operator, with a default value of 24 hours.
> > END
> >
> >    The PCC, in-charge of calculating the
> >    bandwidth to be adjusted, can decide to adjust the bandwidth
> >
> > Remove both commas.
> >
> >    Only if the difference between the
> >    current bandwidth demand (MaxAvgBw) and the current bandwidth
> >    reservation is greater than or equal to the Adjustment-Threshold
> >    (percentage or absolute value) (which can be configured by an
> >    operator and the default as 5 percentage), the LSP bandwidth is
> >    adjusted (upsized) to the current bandwidth demand (MaxAvgBw).
> >
> > I=E2=80=99m sorry: I can=E2=80=99t made any sense out of this text and,=
 thus, can=E2=80=99t
> > suggest a fix.  Please try rephrasing this.  When you do, please make
> > it more than one sentence, and please avoid consecutive parenthesized
> > phrases, which are awkward.
> >
> >    However, longer
> >    adjustment-interval can result in an undesirable effect
> >
> > =E2=80=9Ca longer=E2=80=9D
> >
> >    To avoid this, the
> >    Auto-Bandwidth feature may pre-maturely expire the adjustment-
> >    interval and adjust the LSP bandwidth
> >
> > =E2=80=9Cprematurely=E2=80=9D, with no hyphen.
> > =E2=80=9Cadjustment interval=E2=80=9D, with no hyphen.
> >
> > =E2=80=94 Section 5.1 =E2=80=94
> >
> >    o  The PCEP speaker that does not recognize the extensions defined i=
n
> >
> > =E2=80=9CA PCEP speaker=E2=80=9D
> >
> >    o  If the PCEP speaker that supports the extensions defined in this
> >
> > =E2=80=9CIf a PCEP speaker supports=E2=80=9D
> >
> > =E2=80=94 Section 5.2 =E2=80=94
> >
> >    Future specification can define additional sub-TLVs.
> >
> > =E2=80=9Cspecifications=E2=80=9D
> >
> >    If sub-TLVs are not present, the
> >    default values as specified in this document are used or otherwise
> >    based on the local policy are assumed.
> >
> > I can=E2=80=99t make sense of that sentence; please re-phrase it.
> >
> > =E2=80=94 Section 5.2.3.2 =E2=80=94
> >
> >    o  Reserved: SHOULD be set to zero on transmission and MUST be
> >       ignored on receipt.
> >
> > Why is this =E2=80=9CSHOULD=E2=80=9D, when other reserved values have b=
een =E2=80=9CMUST=E2=80=9D?
> >
> > (Same comment in 5.2.3.4, 5.2.5.1, 5.2.5.2, 5.2.5.3, and 5.2.5.4.)
> >
> > =3D=3D=3D=3D
> >
> > [1] https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-pce-auto-b=
andwidth/ballot/
> > [2] https://mailarchive.ietf.org/arch/browse/pce/


From nobody Mon Sep 16 09:16:23 2019
Return-Path: <adrian@olddog.co.uk>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D19E912004F; Mon, 16 Sep 2019 09:16:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qXUsHLOwaLYh; Mon, 16 Sep 2019 09:16:19 -0700 (PDT)
Received: from mta5.iomartmail.com (mta5.iomartmail.com [62.128.193.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5B6C120026; Mon, 16 Sep 2019 09:16:18 -0700 (PDT)
Received: from vs3.iomartmail.com (vs3.iomartmail.com [10.12.10.124]) by mta5.iomartmail.com (8.14.4/8.14.4) with ESMTP id x8GGGEin014223; Mon, 16 Sep 2019 17:16:15 +0100
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 169FA22032; Mon, 16 Sep 2019 17:16:15 +0100 (BST)
Received: from asmtp1.iomartmail.com (unknown [10.12.10.248]) by vs3.iomartmail.com (Postfix) with ESMTPS id F258622042; Mon, 16 Sep 2019 17:16:14 +0100 (BST)
Received: from LAPTOPK7AS653V ([87.112.72.158]) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.4/8.14.4) with ESMTP id x8GGGBF9013296 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 16 Sep 2019 17:16:13 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Barry Leiba'" <barryleiba@computer.org>, "'Dhruv Dhody'" <dhruv.ietf@gmail.com>
Cc: <pce@ietf.org>, "'The IESG'" <iesg@ietf.org>, "'pce-chairs'" <pce-chairs@ietf.org>, <draft-ietf-pce-stateful-pce-auto-bandwidth@ietf.org>
References: <CAB75xn5CPpoo=SWGfiDS+jQQ0pr1Z7HeHKjx9prGzb6tH9YxbQ@mail.gmail.com> <CAB75xn6jiNGePOAat_ET-JsPsvuouo8d651GrdjswPjC7OYPWQ@mail.gmail.com> <CALaySJJ2dkCLm9zdfRFYzU5QRve41UhoX9RYPxvkvpeZJnByZg@mail.gmail.com>
In-Reply-To: <CALaySJJ2dkCLm9zdfRFYzU5QRve41UhoX9RYPxvkvpeZJnByZg@mail.gmail.com>
Date: Mon, 16 Sep 2019 17:16:10 +0100
Organization: Old Dog Consulting
Message-ID: <024101d56caa$0f14f710$2d3ee530$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQLaJY984CkYp6/h4if5RMNX+4ERwAL9TlneAh10iSKk/DHiMA==
Content-Language: en-gb
X-Originating-IP: 87.112.72.158
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-24916.000
X-TM-AS-Result: No--31.369-10.0-31-10
X-imss-scan-details: No--31.369-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-24916.000
X-TMASE-Result: 10--31.369300-10.000000
X-TMASE-MatchedRID: IeZYkn8zfFq9GVQT/CmkaHFPUrVDm6jtjHhXj1NLbjBayaoU89Fh9s9H W53QBL0AVs85UhK71rjB/g189dtqj5BKcAbnxjMCqjZ865FPtprBnL3AaGm9o5l6cEz4nsnl8gv cSKVCSkIkR3pgFbBMgIfv9hpetzms7K35r0y1/571WO1NzV/CYKrhQu91zwNn5DJ1FS+XdBPWNt V1ifHVhsBhyl4WRusrbDlVQvRsKTtoWWTS0CIqzjdfT4zyWoZSlJ6XrUTdEpEoWk+HrvUAIE5VH uLzyf0qF3uQYtPkNr5zluLdPk1n7T1iiwOv4P/78eSmTJSmEv1+Mk6ACsw4JhtVRURjpT+vqM7v 6KBNGANq6b3UW5godg96yZo+kNGOOXyRIvc0XEMiMpIfyuUBOyIk3dpe5X+hmEmkgQDHT/xe/RS +vWeoFzjpLDVWoC1BH5ED9mQDsMjPIXC61GJeS6roPbyANljgPJb7oABYhT9J/DW2nb8DkZbPBs aBVobl/nw40ETKsm1OK+rVow/DPtF+3yx4SzgcfjUCBXbhed99iuvWn3J8KrytS1u1Z7z6l9Mup 5cLtswduR3Zh+ac91wpiL8fYl2ZayXayD84kueFTLRMAFrHXG+BW75YgTMbEd+K6O5Nt53E4EXr t01+HcA01iXVdUbitvifC4MzRj2/C8Xh7eU7wyTc3NdTt+Z6TJYvCNRUoW6E2ut4EHvMmYE/vIN hyffjQTiBk5oGzQos4iOZjuRh1nKQyUwGFiMJ7LuOEAY9BqSCF6GkB9h+D5GhAvBSa2i/C2AcMd uALVImLrQLVUxjyhn1Zh5h4gk/HnGJ65Z1kWSeAiCmPx4NwFkMvWAuahr8m5N2YHMD0b8MyrfP9 j+C1d934/rDAK3zUc1+O1X9AzE=
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/BmueiiE6xWcC53R96LBoCi-TIjM>
Subject: Re: [Pce] **Barry Leiba's DISCUSS on draft-ietf-pce-stateful-pce-auto-bandwidth**
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Sep 2019 16:16:22 -0000

Yes, that's a reasonable request.

Should send a Notification.
If congested or would only serve to increase overload, May choose to not =
send a Notification.
Not sending a Notification could result in foo
A PCC experiencing foo should to bar.
Note that when a PCE serves very many PCCs, congestion may arise without =
any one PCC becoming aware of multiple unserved messages, in which case =
something.

Adrian

-----Original Message-----
From: Barry Leiba <barryleiba@computer.org>=20
Sent: 16 September 2019 17:00
To: Dhruv Dhody <dhruv.ietf@gmail.com>
Cc: pce@ietf.org; The IESG <iesg@ietf.org>; pce-chairs =
<pce-chairs@ietf.org>; Farrel Adrian <adrian@olddog.co.uk>; =
draft-ietf-pce-stateful-pce-auto-bandwidth@ietf.org
Subject: Re: **Barry Leiba's DISCUSS on =
draft-ietf-pce-stateful-pce-auto-bandwidth**

Thanks for the reply, Dhruv.

To be clear, I am NOT suggesting changing it to MUST (though that
could be a perfectly good outcome of the discussion).  I am suggesting
that if it remains as SHOULD, there has to be some explanation of what
the constraints are and what interoperability or security issues could
arise if an implementation doesn't do it that way.

Barry

On Mon, Sep 16, 2019 at 4:21 AM Dhruv Dhody <dhruv.ietf@gmail.com> =
wrote:
>
> Hi again!
>
> On Mon, Sep 16, 2019 at 4:48 PM Dhruv Dhody <dhruv.ietf@gmail.com> =
wrote:
> >
> > Hi Barry, WG,
> >
> > I saw the DISCUSS [1] in the datatracker but for some reason the =
email
> > never landed in my inbox or the list [2]. I am manually posting it
> > here -
> >
> > =3D=3D=3D=3D
> >
> > Discuss (2019-09-16)
> >
> > Thanks for another clear document.  There are some "SHOULD" key =
words
> > in one section that I would like to discuss, and that I think we =
ought
> > to be able to resolve without much difficulty:
> >
> > =E2=80=94 Section 5.7 =E2=80=94
> >
> > There are various =E2=80=9CSHOULD=E2=80=9Ds in this section, and I =
have the same
> > comment about all of them: BCP 14 says, about =
=E2=80=9CSHOULD=E2=80=9D, that =E2=80=9Cthere
> > may exist valid reasons in particular circumstances to ignore a
> > particular item, but the full implications must be understood and
> > carefully weighed before choosing a different course.=E2=80=9D  I =
see no
> > guidance here to help the reader understand what such circumstances
> > and implications are, so I can=E2=80=99t see how an implementer can =
evaluate
> > the situation.  Can you provide any help here?
> >
> > =3D=3D=3D=3D
> >
>
> I checked the base RFC for PCEP - RFC 5440 where notifications are
> first defined. They do not use MUST for sending notification in the
> PCE overload case [1].
>
> Leaving that aside, in case of auto-bandwidth feature, this
> notification is important for scaling. I am inclined to change it to
> MUST as suggested.
>
> Co-authors, WG, please speak up if you disagree!!
>
> I have incorporated all other comments in the working copy.
>
> Diff: =
https://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=3Ddraft-ietf-pce-s=
tateful-pce-auto-bandwidth-11&url2=3Dhttps://raw.githubusercontent.com/dh=
ruvdhody/ietf/master/draft-ietf-pce-stateful-pce-auto-bandwidth-12.txt
>
> Thanks!
> Dhruv
>
> [1] https://tools.ietf.org/html/rfc5440#section-7.14
>
> > Comment (2019-09-16)
> >
> > Again, these are purely editorial comments, which need no detailed
> > response; please just consider them.
> >
> > =E2=80=94 Section 1 =E2=80=94
> >
> >    Over time, based on the varying traffic pattern, an LSP =
established
> >    with a certain bandwidth may require to adjust the bandwidth =
reserved
> >    in the network dynamically.
> >
> > =E2=80=9Cmay require adjustment of the bandwidth=E2=80=9D
> >
> >    This is similar to
> >    the Passive stateful PCE model, while the Passive stateful PCE =
uses
> >    path request/reply mechanism, the Active stateful PCE uses
> >    report/update mechanism.
> >
> > NEW
> >    This is similar to
> >    the Passive stateful PCE model: while the Passive stateful PCE =
uses
> >    a path request/reply mechanism, the Active stateful PCE uses a
> >    report/update mechanism.
> > END
> >
> >    This document defines the PCEP extensions needed to support Auto-
> >    Bandwidth feature in a Active stateful PCE model
> >
> > NEW
> >    This document defines the PCEP extensions needed to support an =
Auto-
> >    Bandwidth feature in an Active stateful PCE model
> > END
> >
> > =E2=80=94 Section 2.3 =E2=80=94
> >
> >       This value indicates how many times
> >       consecutively, the percentage or absolute difference
> >
> > Add a comma after =E2=80=9Ctimes=E2=80=9D.
> >
> > =E2=80=94 Section 3 =E2=80=94
> >
> >    The PCEP speaker supporting this document must have a mechanism
> >
> > =E2=80=9CA PCEP speaker=E2=80=9D.
> >
> >    o  It is required to identify and inform the PCC, which LSPs are
> >       enabled with Auto-Bandwidth feature.  Not all LSPs in some
> >       deployments would like their bandwidth to be dependent on the
> >       real-time bandwidth usage but be constant as set by the =
operator.
> >
> > NEW
> >    o  It is necessary to identify and inform the PCC which LSPs have
> >       the Auto-Bandwidth feature enabled.  In some deployments, not
> >       all LSPs would like their bandwidth to be dependent on the
> >       real-time bandwidth usage, but would rather be constant as set
> >       by the operator.
> > END
> >
> > =E2=80=94 Section 4.1 =E2=80=94
> >
> >    The initial LSP bandwidth can be set to an arbitrary value =
(including
> >    zero), in practice, it can be operator expected value based on =
design
> >    and planning.
> >
> > NEW
> >    The initial LSP bandwidth can be set to an arbitrary value =
(including
> >    zero).  In practice, it can be set to an expected value based on =
design
> >    and planning.
> > END
> >
> > =E2=80=94 Section 4.2 =E2=80=94
> >
> >    When the Auto-Bandwidth feature is enabled, the measured traffic =
rate
> >    is periodically sampled at each Sample-Interval (which can be
> >    configured by an operator and the default value as 5 minutes) by =
the
> >    PCC, when the PCC is the head-end node of the LSP.  The traffic =
rate
> >    samples are accumulated over the Adjustment-Interval period (in =
the
> >    Up or Down direction) (which can be configured by an operator and =
the
> >    default value as 24 hours).
> >
> > NEW
> >    When the Auto-Bandwidth feature is enabled, the measured traffic =
rate
> >    is periodically sampled at each Sample-Interval by the PCC, when =
the
> >    PCC is the head-end node of the LSP.  The sample interval can be
> >    configured by an operator, with a default value of 5 minutes.
> >
> >    The traffic rate samples are accumulated over the =
Adjustment-Interval
> >    period (in the Up or Down direction).  The period can be =
configured by
> >    an operator, with a default value of 24 hours.
> > END
> >
> >    The PCC, in-charge of calculating the
> >    bandwidth to be adjusted, can decide to adjust the bandwidth
> >
> > Remove both commas.
> >
> >    Only if the difference between the
> >    current bandwidth demand (MaxAvgBw) and the current bandwidth
> >    reservation is greater than or equal to the Adjustment-Threshold
> >    (percentage or absolute value) (which can be configured by an
> >    operator and the default as 5 percentage), the LSP bandwidth is
> >    adjusted (upsized) to the current bandwidth demand (MaxAvgBw).
> >
> > I=E2=80=99m sorry: I can=E2=80=99t made any sense out of this text =
and, thus, can=E2=80=99t
> > suggest a fix.  Please try rephrasing this.  When you do, please =
make
> > it more than one sentence, and please avoid consecutive =
parenthesized
> > phrases, which are awkward.
> >
> >    However, longer
> >    adjustment-interval can result in an undesirable effect
> >
> > =E2=80=9Ca longer=E2=80=9D
> >
> >    To avoid this, the
> >    Auto-Bandwidth feature may pre-maturely expire the adjustment-
> >    interval and adjust the LSP bandwidth
> >
> > =E2=80=9Cprematurely=E2=80=9D, with no hyphen.
> > =E2=80=9Cadjustment interval=E2=80=9D, with no hyphen.
> >
> > =E2=80=94 Section 5.1 =E2=80=94
> >
> >    o  The PCEP speaker that does not recognize the extensions =
defined in
> >
> > =E2=80=9CA PCEP speaker=E2=80=9D
> >
> >    o  If the PCEP speaker that supports the extensions defined in =
this
> >
> > =E2=80=9CIf a PCEP speaker supports=E2=80=9D
> >
> > =E2=80=94 Section 5.2 =E2=80=94
> >
> >    Future specification can define additional sub-TLVs.
> >
> > =E2=80=9Cspecifications=E2=80=9D
> >
> >    If sub-TLVs are not present, the
> >    default values as specified in this document are used or =
otherwise
> >    based on the local policy are assumed.
> >
> > I can=E2=80=99t make sense of that sentence; please re-phrase it.
> >
> > =E2=80=94 Section 5.2.3.2 =E2=80=94
> >
> >    o  Reserved: SHOULD be set to zero on transmission and MUST be
> >       ignored on receipt.
> >
> > Why is this =E2=80=9CSHOULD=E2=80=9D, when other reserved values =
have been =E2=80=9CMUST=E2=80=9D?
> >
> > (Same comment in 5.2.3.4, 5.2.5.1, 5.2.5.2, 5.2.5.3, and 5.2.5.4.)
> >
> > =3D=3D=3D=3D
> >
> > [1] =
https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-pce-auto-bandwid=
th/ballot/
> > [2] https://mailarchive.ietf.org/arch/browse/pce/


From nobody Mon Sep 16 20:53:13 2019
Return-Path: <dhruv.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 752D3120144 for <pce@ietfa.amsl.com>; Mon, 16 Sep 2019 20:53:11 -0700 (PDT)
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, FREEMAIL_FROM=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=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 EIIifeVHJwHz for <pce@ietfa.amsl.com>; Mon, 16 Sep 2019 20:53:09 -0700 (PDT)
Received: from mail-io1-xd29.google.com (mail-io1-xd29.google.com [IPv6:2607:f8b0:4864:20::d29]) (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 D1B3D1200FB for <pce@ietf.org>; Mon, 16 Sep 2019 20:53:09 -0700 (PDT)
Received: by mail-io1-xd29.google.com with SMTP id r26so4182241ioh.8 for <pce@ietf.org>; Mon, 16 Sep 2019 20:53:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=1riALQ4rgPo3d+pJCsVOMHln1+1UT7AGhOwxKQsvwLg=; b=cXba1CEaEXKsduY6Ej5orwW06zz8+iBHPJItCJ4/JaEdfj+joyrvbexI1Lai4mkUzA KR5XDfDfCI7dhSLKv8I6W14ryANiDQe96sp8TPH6e15zq/pW3y/kAETHMeuR7icEWkRt e/S6tw+XQya74R89makiEHV7sLXQRIWMYB54kweAhFePgn5N7+PniACPXtL8dvlICahI ZzPKjCjGKRkI3+wudiiDgEggSgwp8fMKZQKMSIG2OqTLcQFIPLisvge2Z1OFvD9vIdjV mO+j4Wp+Cvu87Ksitp4llkU6qEyTtuk4+5kTor0qUiAuR0U8NlZo2GWOOkvoVOYZABhh x90Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=1riALQ4rgPo3d+pJCsVOMHln1+1UT7AGhOwxKQsvwLg=; b=a8G4Y8Hi7vcHt8eJio1JOLN9Cc7jgl22N+xK9EXskuVpR4hn9KtSUUVK2rk4ghzJf6 u8jdzQRmxhIGr71PCzYZB+EwksJj3PpYnf4sML/jcEmSzSfNcI913ZOZLiBVpBHUmLnv CguagugWjr8ivx1f5nH+RT2gQONrSF1EAZKxy88qNx8rrWH746aAB1O4XwCw1crVB6Hr C1iYhZ59XyWmb5WGjw3ad+9SjQy1/eCqMz53M8KATbIGU0o2lZtqVCLlSSPGhl2cRY83 DiQ2j2Hv+A0EuH6Thc/WSZ9nHb/2d8VtdDbbr/J8MESgTFPftDrJTNdHTBz3qwcTWz5e fHZA==
X-Gm-Message-State: APjAAAXb/zQHOTkvBcbQ8hrNkZtiMmlZGE71cwL+6X1epNX3D7e1UG8s WM7OFidDJxkn/4hFlu4/eHnpTNOpBgwYzxPUe0Rj4+Lh
X-Google-Smtp-Source: APXvYqwzK0iS//QREUoqmW4Wu4Zw8raHke944QEI9sVVjBQj1kZFrtiSpYsBhT7ucrgs4s1Sxwxpo/whBdFTdo4n+iM=
X-Received: by 2002:a5e:d502:: with SMTP id e2mr590723iom.279.1568692388748; Mon, 16 Sep 2019 20:53:08 -0700 (PDT)
MIME-Version: 1.0
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Tue, 17 Sep 2019 09:22:32 +0530
Message-ID: <CAB75xn7kUgm=+TCveuo=ubNUbws8QBMiqoUenLWe5wOneqGTNA@mail.gmail.com>
To: pce@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/zIJWttMXcZDcWOtHUOx2YEQ3fLg>
Subject: [Pce] WG LC ends for draft-farrel-pce-stateful-flags-01
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Sep 2019 03:53:12 -0000

Hi WG,

The WG LC has ended. The last call response for this draft was not
overwhelming, but there were no objections and some support on the
list. Thanks to everyone who responded. Since this seems to be focused
and uncontroversial work, we believe we can move this forward in the
publication process.

Thanks to Hari for agreeing to be the document shepherd.

Thanks!
PCE Chairs


From nobody Mon Sep 16 22:30:08 2019
Return-Path: <dhruv.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D8D8120145; Mon, 16 Sep 2019 22:29:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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, 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 qC5OPtDd_8c0; Mon, 16 Sep 2019 22:29:54 -0700 (PDT)
Received: from mail-io1-xd36.google.com (mail-io1-xd36.google.com [IPv6:2607:f8b0:4864:20::d36]) (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 BCBD21200A4; Mon, 16 Sep 2019 22:29:54 -0700 (PDT)
Received: by mail-io1-xd36.google.com with SMTP id d17so4494441ios.13; Mon, 16 Sep 2019 22:29:54 -0700 (PDT)
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:content-transfer-encoding; bh=FaEpfgAOIOC2EJpdoLGuQwgqyz0KLLJVIaOnksQuaQg=; b=IqD2ayJ3FvaLfFeOAnn5ic66n1Anl4JROyeeZ5USkJWzYsJwrGeQ9ymaNhwlMXLJcL hw6rvKE2ZiD1mp6yQhEgK1KLMvtVud4VTa9AdlmbhlS6lFUk3vSuchixFRT7atx5uawG zNTJvAMQBGYqICrqKeGVSCbABuKuSqPOAx/sN69GjpGk6L0BbZIpKz4TyBr/T0EHe2EA j6bTFx6ZCBAlLjTESY7LaT72lEUtpUcfhcI6fUUOH8PG+sWW5mXLHzeTaAwsCduRISah zQoaImdFptuBzoodVk1vXgP2hNLUl4oPHkBLh3LTN9b1Sj0+dermkK0FWSPpCUtyWJW2 /5zg==
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:content-transfer-encoding; bh=FaEpfgAOIOC2EJpdoLGuQwgqyz0KLLJVIaOnksQuaQg=; b=BGqwXQLeMY0K+O1lPBJ5yLvtmMciogE3rL2x1F1Z++fHrzuMlwx1vuiezFWMpXtTfb izzhZwJcPqTDUrHJNaEmDP7QCxfghdtJSHjZ5awLclufF/tpfnzCI7XMmlYYMC0v3ZK9 ZOErmOHiLaXucAP3tABGFuckfn/dHdhWwNLpZ0KR6K5LYgUHcdZm34mcMOezs5TI/M1s Pc/H92FGpuxWOCEoFKrdDSR6bxDTqkg1POEBUhETpeR8yfRu92pWiEjUA7a2d07Vxfco afQQ3TFrhZAF3Xr59q8GVVP3anM5TRMPXcDx0xwMGc4zzQ+hhmJ5j8DwdYUPnVDHO8qG 1AEQ==
X-Gm-Message-State: APjAAAUfMyryuRrmg/CvHhoHZgojbXPYMiITX0dwyLY7rpsUSAFLhaLP q/Y3R11hkH/KMtKMF1E1GJrbpXbwXPZ8CLtPCrE=
X-Google-Smtp-Source: APXvYqyjKT+L/wXDwE0DJxnVb7XPAfAJRcf+06tU8CSUTeoMnHLX3XWiucfaYz33lXwsacX3YZb0QtQqKoOZeDb26vw=
X-Received: by 2002:a5e:df04:: with SMTP id f4mr1788979ioq.192.1568698193745;  Mon, 16 Sep 2019 22:29:53 -0700 (PDT)
MIME-Version: 1.0
References: <CAB75xn5CPpoo=SWGfiDS+jQQ0pr1Z7HeHKjx9prGzb6tH9YxbQ@mail.gmail.com> <CAB75xn6jiNGePOAat_ET-JsPsvuouo8d651GrdjswPjC7OYPWQ@mail.gmail.com> <CALaySJJ2dkCLm9zdfRFYzU5QRve41UhoX9RYPxvkvpeZJnByZg@mail.gmail.com> <024101d56caa$0f14f710$2d3ee530$@olddog.co.uk>
In-Reply-To: <024101d56caa$0f14f710$2d3ee530$@olddog.co.uk>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Tue, 17 Sep 2019 10:59:17 +0530
Message-ID: <CAB75xn4UCEXLuw-E10i=cYpphhReYwhHBGPzR=qGyiSQVstoOg@mail.gmail.com>
To: Farrel Adrian <adrian@olddog.co.uk>
Cc: Barry Leiba <barryleiba@computer.org>, pce@ietf.org, The IESG <iesg@ietf.org>, pce-chairs <pce-chairs@ietf.org>, draft-ietf-pce-stateful-pce-auto-bandwidth@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/GTtYhcQw5hrZ7W63uGcOxUd0ZbU>
Subject: Re: [Pce] **Barry Leiba's DISCUSS on draft-ietf-pce-stateful-pce-auto-bandwidth**
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Sep 2019 05:29:57 -0000

Hi All,

Thanks for the discussion. I have updated text based on Adrian's suggestion=
.

See diff - https://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=3Ddraft-i=
etf-pce-stateful-pce-auto-bandwidth-11&url2=3Dhttps://raw.githubusercontent=
.com/dhruvdhody/ietf/master/draft-ietf-pce-stateful-pce-auto-bandwidth-12.t=
xt

Skip to Section 5.7 to see related changes.

Let me know if any further changes are needed.

Thanks!
Dhruv

On Mon, Sep 16, 2019 at 9:46 PM Adrian Farrel <adrian@olddog.co.uk> wrote:
>
> Yes, that's a reasonable request.
>
> Should send a Notification.
> If congested or would only serve to increase overload, May choose to not =
send a Notification.
> Not sending a Notification could result in foo
> A PCC experiencing foo should to bar.
> Note that when a PCE serves very many PCCs, congestion may arise without =
any one PCC becoming aware of multiple unserved messages, in which case som=
ething.
>
> Adrian
>
> -----Original Message-----
> From: Barry Leiba <barryleiba@computer.org>
> Sent: 16 September 2019 17:00
> To: Dhruv Dhody <dhruv.ietf@gmail.com>
> Cc: pce@ietf.org; The IESG <iesg@ietf.org>; pce-chairs <pce-chairs@ietf.o=
rg>; Farrel Adrian <adrian@olddog.co.uk>; draft-ietf-pce-stateful-pce-auto-=
bandwidth@ietf.org
> Subject: Re: **Barry Leiba's DISCUSS on draft-ietf-pce-stateful-pce-auto-=
bandwidth**
>
> Thanks for the reply, Dhruv.
>
> To be clear, I am NOT suggesting changing it to MUST (though that
> could be a perfectly good outcome of the discussion).  I am suggesting
> that if it remains as SHOULD, there has to be some explanation of what
> the constraints are and what interoperability or security issues could
> arise if an implementation doesn't do it that way.
>
> Barry
>
> On Mon, Sep 16, 2019 at 4:21 AM Dhruv Dhody <dhruv.ietf@gmail.com> wrote:
> >
> > Hi again!
> >
> > On Mon, Sep 16, 2019 at 4:48 PM Dhruv Dhody <dhruv.ietf@gmail.com> wrot=
e:
> > >
> > > Hi Barry, WG,
> > >
> > > I saw the DISCUSS [1] in the datatracker but for some reason the emai=
l
> > > never landed in my inbox or the list [2]. I am manually posting it
> > > here -
> > >
> > > =3D=3D=3D=3D
> > >
> > > Discuss (2019-09-16)
> > >
> > > Thanks for another clear document.  There are some "SHOULD" key words
> > > in one section that I would like to discuss, and that I think we ough=
t
> > > to be able to resolve without much difficulty:
> > >
> > > =E2=80=94 Section 5.7 =E2=80=94
> > >
> > > There are various =E2=80=9CSHOULD=E2=80=9Ds in this section, and I ha=
ve the same
> > > comment about all of them: BCP 14 says, about =E2=80=9CSHOULD=E2=80=
=9D, that =E2=80=9Cthere
> > > may exist valid reasons in particular circumstances to ignore a
> > > particular item, but the full implications must be understood and
> > > carefully weighed before choosing a different course.=E2=80=9D  I see=
 no
> > > guidance here to help the reader understand what such circumstances
> > > and implications are, so I can=E2=80=99t see how an implementer can e=
valuate
> > > the situation.  Can you provide any help here?
> > >
> > > =3D=3D=3D=3D
> > >
> >
> > I checked the base RFC for PCEP - RFC 5440 where notifications are
> > first defined. They do not use MUST for sending notification in the
> > PCE overload case [1].
> >
> > Leaving that aside, in case of auto-bandwidth feature, this
> > notification is important for scaling. I am inclined to change it to
> > MUST as suggested.
> >
> > Co-authors, WG, please speak up if you disagree!!
> >
> > I have incorporated all other comments in the working copy.
> >
> > Diff: https://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=3Ddraft-ie=
tf-pce-stateful-pce-auto-bandwidth-11&url2=3Dhttps://raw.githubusercontent.=
com/dhruvdhody/ietf/master/draft-ietf-pce-stateful-pce-auto-bandwidth-12.tx=
t
> >
> > Thanks!
> > Dhruv
> >
> > [1] https://tools.ietf.org/html/rfc5440#section-7.14
> >
> > > Comment (2019-09-16)
> > >
> > > Again, these are purely editorial comments, which need no detailed
> > > response; please just consider them.
> > >
> > > =E2=80=94 Section 1 =E2=80=94
> > >
> > >    Over time, based on the varying traffic pattern, an LSP establishe=
d
> > >    with a certain bandwidth may require to adjust the bandwidth reser=
ved
> > >    in the network dynamically.
> > >
> > > =E2=80=9Cmay require adjustment of the bandwidth=E2=80=9D
> > >
> > >    This is similar to
> > >    the Passive stateful PCE model, while the Passive stateful PCE use=
s
> > >    path request/reply mechanism, the Active stateful PCE uses
> > >    report/update mechanism.
> > >
> > > NEW
> > >    This is similar to
> > >    the Passive stateful PCE model: while the Passive stateful PCE use=
s
> > >    a path request/reply mechanism, the Active stateful PCE uses a
> > >    report/update mechanism.
> > > END
> > >
> > >    This document defines the PCEP extensions needed to support Auto-
> > >    Bandwidth feature in a Active stateful PCE model
> > >
> > > NEW
> > >    This document defines the PCEP extensions needed to support an Aut=
o-
> > >    Bandwidth feature in an Active stateful PCE model
> > > END
> > >
> > > =E2=80=94 Section 2.3 =E2=80=94
> > >
> > >       This value indicates how many times
> > >       consecutively, the percentage or absolute difference
> > >
> > > Add a comma after =E2=80=9Ctimes=E2=80=9D.
> > >
> > > =E2=80=94 Section 3 =E2=80=94
> > >
> > >    The PCEP speaker supporting this document must have a mechanism
> > >
> > > =E2=80=9CA PCEP speaker=E2=80=9D.
> > >
> > >    o  It is required to identify and inform the PCC, which LSPs are
> > >       enabled with Auto-Bandwidth feature.  Not all LSPs in some
> > >       deployments would like their bandwidth to be dependent on the
> > >       real-time bandwidth usage but be constant as set by the operato=
r.
> > >
> > > NEW
> > >    o  It is necessary to identify and inform the PCC which LSPs have
> > >       the Auto-Bandwidth feature enabled.  In some deployments, not
> > >       all LSPs would like their bandwidth to be dependent on the
> > >       real-time bandwidth usage, but would rather be constant as set
> > >       by the operator.
> > > END
> > >
> > > =E2=80=94 Section 4.1 =E2=80=94
> > >
> > >    The initial LSP bandwidth can be set to an arbitrary value (includ=
ing
> > >    zero), in practice, it can be operator expected value based on des=
ign
> > >    and planning.
> > >
> > > NEW
> > >    The initial LSP bandwidth can be set to an arbitrary value (includ=
ing
> > >    zero).  In practice, it can be set to an expected value based on d=
esign
> > >    and planning.
> > > END
> > >
> > > =E2=80=94 Section 4.2 =E2=80=94
> > >
> > >    When the Auto-Bandwidth feature is enabled, the measured traffic r=
ate
> > >    is periodically sampled at each Sample-Interval (which can be
> > >    configured by an operator and the default value as 5 minutes) by t=
he
> > >    PCC, when the PCC is the head-end node of the LSP.  The traffic ra=
te
> > >    samples are accumulated over the Adjustment-Interval period (in th=
e
> > >    Up or Down direction) (which can be configured by an operator and =
the
> > >    default value as 24 hours).
> > >
> > > NEW
> > >    When the Auto-Bandwidth feature is enabled, the measured traffic r=
ate
> > >    is periodically sampled at each Sample-Interval by the PCC, when t=
he
> > >    PCC is the head-end node of the LSP.  The sample interval can be
> > >    configured by an operator, with a default value of 5 minutes.
> > >
> > >    The traffic rate samples are accumulated over the Adjustment-Inter=
val
> > >    period (in the Up or Down direction).  The period can be configure=
d by
> > >    an operator, with a default value of 24 hours.
> > > END
> > >
> > >    The PCC, in-charge of calculating the
> > >    bandwidth to be adjusted, can decide to adjust the bandwidth
> > >
> > > Remove both commas.
> > >
> > >    Only if the difference between the
> > >    current bandwidth demand (MaxAvgBw) and the current bandwidth
> > >    reservation is greater than or equal to the Adjustment-Threshold
> > >    (percentage or absolute value) (which can be configured by an
> > >    operator and the default as 5 percentage), the LSP bandwidth is
> > >    adjusted (upsized) to the current bandwidth demand (MaxAvgBw).
> > >
> > > I=E2=80=99m sorry: I can=E2=80=99t made any sense out of this text an=
d, thus, can=E2=80=99t
> > > suggest a fix.  Please try rephrasing this.  When you do, please make
> > > it more than one sentence, and please avoid consecutive parenthesized
> > > phrases, which are awkward.
> > >
> > >    However, longer
> > >    adjustment-interval can result in an undesirable effect
> > >
> > > =E2=80=9Ca longer=E2=80=9D
> > >
> > >    To avoid this, the
> > >    Auto-Bandwidth feature may pre-maturely expire the adjustment-
> > >    interval and adjust the LSP bandwidth
> > >
> > > =E2=80=9Cprematurely=E2=80=9D, with no hyphen.
> > > =E2=80=9Cadjustment interval=E2=80=9D, with no hyphen.
> > >
> > > =E2=80=94 Section 5.1 =E2=80=94
> > >
> > >    o  The PCEP speaker that does not recognize the extensions defined=
 in
> > >
> > > =E2=80=9CA PCEP speaker=E2=80=9D
> > >
> > >    o  If the PCEP speaker that supports the extensions defined in thi=
s
> > >
> > > =E2=80=9CIf a PCEP speaker supports=E2=80=9D
> > >
> > > =E2=80=94 Section 5.2 =E2=80=94
> > >
> > >    Future specification can define additional sub-TLVs.
> > >
> > > =E2=80=9Cspecifications=E2=80=9D
> > >
> > >    If sub-TLVs are not present, the
> > >    default values as specified in this document are used or otherwise
> > >    based on the local policy are assumed.
> > >
> > > I can=E2=80=99t make sense of that sentence; please re-phrase it.
> > >
> > > =E2=80=94 Section 5.2.3.2 =E2=80=94
> > >
> > >    o  Reserved: SHOULD be set to zero on transmission and MUST be
> > >       ignored on receipt.
> > >
> > > Why is this =E2=80=9CSHOULD=E2=80=9D, when other reserved values have=
 been =E2=80=9CMUST=E2=80=9D?
> > >
> > > (Same comment in 5.2.3.4, 5.2.5.1, 5.2.5.2, 5.2.5.3, and 5.2.5.4.)
> > >
> > > =3D=3D=3D=3D
> > >
> > > [1] https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-pce-auto=
-bandwidth/ballot/
> > > [2] https://mailarchive.ietf.org/arch/browse/pce/
>


From nobody Mon Sep 16 23:01:04 2019
Return-Path: <barryleiba@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5692C120145; Mon, 16 Sep 2019 23:01:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.922
X-Spam-Level: 
X-Spam-Status: No, score=-1.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.026, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AkF0RiMpF5k0; Mon, 16 Sep 2019 23:01:01 -0700 (PDT)
Received: from mail-io1-f41.google.com (mail-io1-f41.google.com [209.85.166.41]) (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 5B5CD1200E9; Mon, 16 Sep 2019 23:01:01 -0700 (PDT)
Received: by mail-io1-f41.google.com with SMTP id j4so4666619iog.11; Mon, 16 Sep 2019 23:01:01 -0700 (PDT)
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=ZXp9epogMi5ZROUu7r1fLy0HdhGEnJgYf5tUhePS4Ac=; b=YatQYHaREllVFlvPVQf6TrpzLQ5qj2+MGdl1bZ2hJn9ijDFWiDKB6FrVIp1zZAldOq jOQpMreqWIWEwGbz0mE36eAPqtANGZawuLTpMX3Sg0IkkRhLCBHzQysB/bWW5ztS+DP3 aT0u/zx+t2F+lcuw6UZwjtMeZGRtm0ZhfBI2DGNqJjLQu8MAPeySszmj2Z8icXiSw1Qx aNwsfDTbZ/5IAXEXUvoDzzt/V5zPA4MNhFOgySUzM6U/S1ny1iKhTeLUJO7gTU+TECGt 6sDwMyE3haajvkZn5l0zXg46KO45iXXMcZkjzMKRE3SxflDzImzIGtDveqowCR+FQgto ZrQg==
X-Gm-Message-State: APjAAAWIhxGApcgB2RvcrTRnCCUhg4URTA9BmuerOPTZXVQd1/uwF9XU dqUZd1JXfFbxg81SIt3+jqPABllFWVKFvFkCaVQ=
X-Google-Smtp-Source: APXvYqzy3yK63/W2jkmyZfPHWGrd+vH1A0HCisecvOaFW3sblEDfuNoqeW6xqoplHSySsEOJ7oTyPhphq+CYRHGiw9o=
X-Received: by 2002:a02:b882:: with SMTP id p2mr1197530jam.16.1568700060334; Mon, 16 Sep 2019 23:01:00 -0700 (PDT)
MIME-Version: 1.0
References: <CAB75xn5CPpoo=SWGfiDS+jQQ0pr1Z7HeHKjx9prGzb6tH9YxbQ@mail.gmail.com> <CAB75xn6jiNGePOAat_ET-JsPsvuouo8d651GrdjswPjC7OYPWQ@mail.gmail.com> <CALaySJJ2dkCLm9zdfRFYzU5QRve41UhoX9RYPxvkvpeZJnByZg@mail.gmail.com> <024101d56caa$0f14f710$2d3ee530$@olddog.co.uk> <CAB75xn4UCEXLuw-E10i=cYpphhReYwhHBGPzR=qGyiSQVstoOg@mail.gmail.com>
In-Reply-To: <CAB75xn4UCEXLuw-E10i=cYpphhReYwhHBGPzR=qGyiSQVstoOg@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Mon, 16 Sep 2019 23:00:48 -0700
Message-ID: <CALaySJLq88EYZ21tq9PdnTbwA_MG52GOyxOEkEMGQJEUbHbgsA@mail.gmail.com>
To: Dhruv Dhody <dhruv.ietf@gmail.com>
Cc: Farrel Adrian <adrian@olddog.co.uk>, pce@ietf.org, The IESG <iesg@ietf.org>, pce-chairs <pce-chairs@ietf.org>, draft-ietf-pce-stateful-pce-auto-bandwidth@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/5xg6YndQsAqVOWJjrOTb3oLIq2g>
Subject: Re: [Pce] **Barry Leiba's DISCUSS on draft-ietf-pce-stateful-pce-auto-bandwidth**
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Sep 2019 06:01:03 -0000

> Thanks for the discussion. I have updated text based on Adrian's suggestion.
>
> See diff - https://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=draft-ietf-pce-stateful-pce-auto-bandwidth-11&url2=https://raw.githubusercontent.com/dhruvdhody/ietf/master/draft-ietf-pce-stateful-pce-auto-bandwidth-12.txt

This looks good to me, and seems a clear explanation.  I'll go clear
my DISCUSS.  Thanks for making the changes, and thanks, Adrian and
Rakesh, for weighing in on the discussion.

Barry


From nobody Tue Sep 17 02:46:37 2019
Return-Path: <noreply@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BFA82120013; Tue, 17 Sep 2019 02:46:28 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Martin Vigoureux via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-pce-stateful-hpce@ietf.org, Adrian Farrel <adrian@olddog.co.uk>, pce-chairs@ietf.org, adrian@olddog.co.uk, pce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.101.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Martin Vigoureux <martin.vigoureux@nokia.com>
Message-ID: <156871358878.17495.3532142129372536142.idtracker@ietfa.amsl.com>
Date: Tue, 17 Sep 2019 02:46:28 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/exQ--No_VTXt3bAzOretkjSuVfo>
Subject: [Pce] Martin Vigoureux's No Objection on draft-ietf-pce-stateful-hpce-13: (with COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Sep 2019 09:46:29 -0000

Martin Vigoureux has entered the following ballot position for
draft-ietf-pce-stateful-hpce-13: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-hpce/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Hi,

thank you for this document. I only have nit type comments:

s/hierarchy of stateful PCEs play a crucial role/hierarchy of stateful PCEs plays a crucial role/

   The ability to compute shortest constrained TE LSPs
not sure what you mean by "shortest constrained"

s/the MDSC decompose/the MDSC decomposes/

   Different signaling methods for inter-domain RSVP-TE signaling
s/methods/options/

s/the PCE further propagates/the C-PCE further propagates/



From nobody Tue Sep 17 03:12:56 2019
Return-Path: <dhruv.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58D3D12080F; Tue, 17 Sep 2019 03:12:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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, 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 jXzS8P52MQqF; Tue, 17 Sep 2019 03:12:46 -0700 (PDT)
Received: from mail-io1-xd35.google.com (mail-io1-xd35.google.com [IPv6:2607:f8b0:4864:20::d35]) (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 5376412080A; Tue, 17 Sep 2019 03:12:46 -0700 (PDT)
Received: by mail-io1-xd35.google.com with SMTP id a1so6218429ioc.6; Tue, 17 Sep 2019 03:12:46 -0700 (PDT)
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=8CWnIW342MYBBErQgKraTufyMv+QlXIdQrdo6j1q71g=; b=OehJ8aAVkRe5r/nPrSmsgPl3PqZ1P/Pq6RramATHaiLJV/DpZyZ2crOfSU1BuEOC7b 8mhsscQResWG8O0UypKWIwk17RFYX494BQFZledWMNvb9baFVSA1I91fgA+CwykAyU9D 5+6T4RvqdGIbJ97QxSNQ9JINxHuzyA/IGapwuKbWG19afLTibzX7biPpeSDtKtfz+wZy Nt/NogdKe538C90cSZT91KjQW5ImS/0mbwRtultZEqvifSN9YSp6a6AJ6NmrD/Wp07/2 Ly4fZZUcH9LmGqi8BQoNGJ9Pa0wySGd+7mziNjafRFLO0p1e84InkwOK7dmk5b0TAR30 cMyw==
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=8CWnIW342MYBBErQgKraTufyMv+QlXIdQrdo6j1q71g=; b=kMXXsss+ao3xK419OWIeuHMerIaBNFBuYaXNWDStVTOmnI59pkAU1GTMLxPkxFyZSn K9ee08gbChAAnfcAXeEESZlXBD+pzJAK0+ytLXu//pQYXOw5OzJ9u06bfnKuC/dEbS4A zFmhO36QLQWCLrdRSry8FoOzMJ/dF0cZW5xLuPYa7XBYNGqQ0teXA5G+FoodYpB8Or1B GQiREo0cWlOAqaZRpA7kY9imaWcKQu/UvT13WdCOzPvxZtFWdLQc6ar1UXhadOEOj5Hc I4IG/D8c31HdJiu1t0zU4F1axH3K9RAynvzg0Ob5i06kgp+C8kaTSEKmyw4ThtwxWTB6 jElQ==
X-Gm-Message-State: APjAAAWBlCzw6p0Qp+tk6+uhWoMFty9TKWLV6KEfUH3Yo/KVELNY7VUN q1kWH+AzjZN4ZGq1Wwy1+LMRFzcnSON1Ln/jCTHCifwY
X-Google-Smtp-Source: APXvYqyvuSUya7lMXRt9KF1vX9ExQFfJFJqRAKbnVKLSx0JGYhtwrAPsNEpC9KLTPZRVUX1/d+sZOLJO/Tb8/4bBDGs=
X-Received: by 2002:a6b:c38f:: with SMTP id t137mr2928585iof.137.1568715165384;  Tue, 17 Sep 2019 03:12:45 -0700 (PDT)
MIME-Version: 1.0
References: <156871358878.17495.3532142129372536142.idtracker@ietfa.amsl.com>
In-Reply-To: <156871358878.17495.3532142129372536142.idtracker@ietfa.amsl.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Tue, 17 Sep 2019 15:42:08 +0530
Message-ID: <CAB75xn7SpJ4d4TwjOvSJqY-S8W4_gAbXyXuh99krXhzpxVY+Ug@mail.gmail.com>
To: Martin Vigoureux <martin.vigoureux@nokia.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pce-stateful-hpce@ietf.org,  Adrian Farrel <adrian@olddog.co.uk>, pce-chairs <pce-chairs@ietf.org>, pce@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/MTZNDTldEuz-WbSa29VY6ckiIGI>
Subject: Re: [Pce] Martin Vigoureux's No Objection on draft-ietf-pce-stateful-hpce-13: (with COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Sep 2019 10:12:48 -0000

Hi Martin,

Thanks for the nits. I incorporated them in the working copy.

Thanks!
Dhruv

Commit: https://github.com/dhruvdhody/ietf/commit/4fa5e2f64a050fcc42bcfaf85c492b8dd5b4e863

Diff: https://tools.ietf.org/rfcdiff?url1=draft-ietf-pce-stateful-hpce-13&url2=https://raw.githubusercontent.com/dhruvdhody/ietf/master/draft-ietf-pce-stateful-hpce-14.txt

On Tue, Sep 17, 2019 at 3:16 PM Martin Vigoureux via Datatracker
<noreply@ietf.org> wrote:
>
> Martin Vigoureux has entered the following ballot position for
> draft-ietf-pce-stateful-hpce-13: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-hpce/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Hi,
>
> thank you for this document. I only have nit type comments:
>
> s/hierarchy of stateful PCEs play a crucial role/hierarchy of stateful PCEs plays a crucial role/
>
>    The ability to compute shortest constrained TE LSPs
> not sure what you mean by "shortest constrained"
>
> s/the MDSC decompose/the MDSC decomposes/
>
>    Different signaling methods for inter-domain RSVP-TE signaling
> s/methods/options/
>
> s/the PCE further propagates/the C-PCE further propagates/
>
>


From nobody Tue Sep 17 10:48:56 2019
Return-Path: <mahend.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 355EE1209BD; Tue, 17 Sep 2019 10:48:45 -0700 (PDT)
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_HTML_ATTACH=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 8kYGD52tIyOY; Tue, 17 Sep 2019 10:48:39 -0700 (PDT)
Received: from mail-ot1-x329.google.com (mail-ot1-x329.google.com [IPv6:2607:f8b0:4864:20::329]) (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 CD0D0120990; Tue, 17 Sep 2019 10:48:35 -0700 (PDT)
Received: by mail-ot1-x329.google.com with SMTP id g25so3897248otl.0; Tue, 17 Sep 2019 10:48:35 -0700 (PDT)
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=TuYIbnJ1Ehi5aX8eDHZaWCrhY9yojAqEOPFY5Ul7SVc=; b=p9Afr3Hl9PFmBzX+75xRvH18tF+3GVodROEVYxFVDK5gI/sNw56bjDKg7IykK1X4gA B+E7CwLbDgu7N5qwh+MHfTnuU4IiBadavrljwMdT12n5VVa2pDFCT9R8z+ZABYHgrKN4 Uy7lRYFxkTMncXfYwjxC+aY8wSYbnnnWJfgLWDyt/6+hbZQTQ3yRudqUdXdVx1o9WHPT 0ZsoOZCfRiYOoZU5EvPVNZMJzGUeSAk83NxtL0dVXI2KRrCx0SmeTpXQOTcgaJo8Rmh8 BAWIDpbSgN2TMsS6BxinP4zaYssRvNdxoJrz+Oc3SvTWHSNBZmtxUzwuG0gn2gYgBpdo nGiA==
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=TuYIbnJ1Ehi5aX8eDHZaWCrhY9yojAqEOPFY5Ul7SVc=; b=LtME4Xc7Gw1YvvytCKK6cWVONN0N0fxeQX682B1HjQy5f3xBdL6Kepe/jPBY2qOsSd YYmp4G2/2LonoXQ5Vqpyw39+AxwV/iqs8NGmSrr9F0dL0hFz+K2l0wDlchRkf9mn/DZ6 4yGe/VBa5UzawuvQU92G7rhDhGHpVU0LUZY8pRobJmnip15S7sGGxmfsMI9PbcZk5JY3 HydzbN7ctEQpzUzSopaeiSxoLo9timVc2yeWoVC11xm9pQQS5Nc25NhCh6aklNPMCu1M exakOa+p1ZaGjpFdIbMnAYRrZHXXvgfi5F0R9eJgRDWls7kCXnAdwr5vUVv8KcKY5o4e 1y9Q==
X-Gm-Message-State: APjAAAUSjyCPPUK9Q/zxQICnaY2jvPq5Kb6ab+xXOuY5c0xGaPnylJci 34+R5CeO8LgpR0xqesM/ahAfIhlHFEe1b/4dd6E=
X-Google-Smtp-Source: APXvYqxnpFC97+Qoeu1BxkHsoc+Vh6MuhQBb2WIBex21AcoFvZPzxh/aakEoJPJVi04nzvvaNJUSU3OlycDA63seiYI=
X-Received: by 2002:a9d:1e83:: with SMTP id n3mr21474otn.287.1568742514985; Tue, 17 Sep 2019 10:48:34 -0700 (PDT)
MIME-Version: 1.0
References: <156849799383.3020.16398829686379997035.idtracker@ietfa.amsl.com>
In-Reply-To: <156849799383.3020.16398829686379997035.idtracker@ietfa.amsl.com>
From: Mahend Negi <mahend.ietf@gmail.com>
Date: Tue, 17 Sep 2019 23:18:22 +0530
Message-ID: <CAM5Nu_zFe31wbGORGvYffxdGQtfMA+_U-twdRGndbUDObHfG9g@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pce-stateful-path-protection@ietf.org, Julien Meuric <julien.meuric@orange.com>, pce-chairs <pce-chairs@ietf.org>, pce@ietf.org
Content-Type: multipart/mixed; boundary="00000000000059ff940592c3549d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/rlUqtQ-MOCIXV_Tft-XCO3FxeKk>
Subject: Re: [Pce] Barry Leiba's No Objection on draft-ietf-pce-stateful-path-protection-10: (with COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Sep 2019 17:48:46 -0000

--00000000000059ff940592c3549d
Content-Type: multipart/alternative; boundary="00000000000059ff900592c3549b"

--00000000000059ff900592c3549b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Barry,

Many thanks for your review. Comments are incorporated in the working copy
(diff attached).

For this one comment ->
=3D=3D=3D
=E2=80=94 Section 4.5 =E2=80=94

   When the protection type is set to 1+1 or 1:N with N=3D1, there MUST be
=E2=80=A6
   When the protection type is set to 1:N with N>1, there MUST be

This is a style thing, so take it or leave it as you please =E2=80=94 it=E2=
=80=99s not wrong
the way it=E2=80=99s written.  It=E2=80=99s just that the =E2=80=9C1:N with=
 N=3D1=E2=80=9D and =E2=80=9C1:N with N>1=E2=80=9D
distinction isn=E2=80=99t necessary, and I think it=E2=80=99s distracting a=
nd invites
uncertainty.  If you just made these like this:

NEW
   When the protection type is set to 1+1, there MUST be
=E2=80=A6
   When the protection type is set to 1:N, there MUST be
END

=E2=80=A6it would be equally correct, but also simpler and, I think, less l=
ikely to
be
confusing.
=3D=3D=3D

The first sentence is for the case 1+1 and 1:1. Since RFC 4872 does
not define an explicit state 1:1, it define 1:N only this wording was
chosen. I have made this change "When the protection type is set to
1+1 or 1:1 (1:N with N=3D1)...".


Thanks,
Mahendra

On Sun, Sep 15, 2019 at 3:23 AM Barry Leiba via Datatracker <
noreply@ietf.org> wrote:

> Barry Leiba has entered the following ballot position for
> draft-ietf-pce-stateful-path-protection-10: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-path-protection/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Thanks for this document.  I have only editorial suggestions.  There's no
> need
> to reply in any detail; just please consider adopting these suggestions.
> Thanks.
>
> =E2=80=94 Abstract =E2=80=94
>
>    Multiprotocol Label Switching Traffic
>    Engineering Label Switched Paths (MPLS LSP)
>
> Shouldn=E2=80=99t that be =E2=80=9C(MPLS-TE LSPs)=E2=80=9D?
>
> =E2=80=94 Section 1 =E2=80=94
>
>    [RFC5440] describes PCEP for communication between a Path Computation
>    Client (PCC) and a PCE or between a pair of PCEs as per [RFC4655].  A
>    PCE computes paths for MPLS-TE LSPs based on various constraints and
>    optimization criteria.
>
> Even though you expanded some of these acronyms in the Abstract, they hav=
e
> to
> be expanded again in the Introduction, because the Abstract and the
> document
> itself each has to stand separately.
>
> That said, =E2=80=9CMPLS-TE=E2=80=9D and =E2=80=9CPCE=E2=80=9D are in the=
 RFC Editor=E2=80=99s list of common
> acronyms
> that don=E2=80=99t need expansion, so you can expand them or not, as you =
please.
> But
> =E2=80=9CPCEP=E2=80=9D and =E2=80=9CLSP=E2=80=9D do need expansion here.
>
> You should also be consistent in using =E2=80=9CMPLS-TE=E2=80=9D (with th=
e hyphen), so
> please
> check the instances of =E2=80=9CMPLS TE=E2=80=9D without the hyphen, and =
change them.  The
> RFC
> Editor will flag this anyway, and it saves time during final editing and
> AUTH48
> if you fix it now.
>
>    It includes
>    mechanisms to effect LSP state synchronization between PCCs and PCEs,
>    delegation of control of LSPs to PCEs, and PCE control of timing and
>    sequence of path computations within and across PCEP sessions and
>    focuses on a model where LSPs are configured on the PCC and control
>    over them is delegated to the PCE.
>
> This is a really long sentence, and can do with being split in two.  I
> suggest
> changing =E2=80=9Csessions and=E2=80=9D to =E2=80=9Csessions.  Stateful P=
CE=E2=80=9D.
>
>    Furthermore, a mechanism to
>    dynamically instantiate LSPs on a PCC based on the requests from a
>    stateful PCE or a controller using stateful PCE, is specified in
>    [RFC8281].
>
> This reads oddly in passive voice, and you have a clear subject to use.
> So I
> suggest:
>
> NEW
>    Furthermore, [RFC8281] specifies a mechanism to
>    dynamically instantiate LSPs on a PCC based on the requests from a
>    stateful PCE or a controller using stateful PCE.
> END
>
>       computes the path for the protection LSP and update the PCC with
>
> =E2=80=9Cupdates=E2=80=9D
>
>    Note that protection LSP can be established (signaled) prior to the
>    failure (in which case the LSP is said to be in standby mode
>    [RFC4427] or a Primary LSP [RFC4872]) or post failure of the
>    corresponding working LSP according to the operator choice/policy
>    (known as secondary LSP [RFC4872]).
>
> =E2=80=9Ca protection LSP=E2=80=9D
>
> I suggest changing =E2=80=9Cpost failure=E2=80=9D to =E2=80=9Cafter failu=
re=E2=80=9D, as it reads better.
>
> I=E2=80=99m not sure about the antecedent to =E2=80=9Caccording to the op=
erator
> choice/policy=E2=80=9D.
>  I think you mean that the establishment can be prior to failure or after
> failure, according to operator choice or policy, is that right?  In that
> case,
> the sentence isn=E2=80=99t worded well.  May I suggest this?:
>
> NEW
>    Note that a protection LSP can be established (signaled) before
>    the failure (in which case the LSP is said to be in standby mode
>    [RFC4427] or a Primary LSP [RFC4872]) or after failure of the
>    corresponding working LSP (known as secondary LSP [RFC4872]).
>    Whether to establish it before or after failure is according
>    to operator choice or policy.
> END
>
>    [I-D.ietf-pce-association-group] introduces a generic mechanism to
>    create a grouping of LSPs which can then be used to define
>    associations between a set of LSPs that is equally applicable to
>    stateful PCE (active and passive modes) and stateless PCE.
>
> When I first read this I thought =E2=80=9Cthat is equally applicable=E2=
=80=9D applied to
> the
> set of LSPs.  I think you mean it to apply to the generic mechanism =E2=
=80=94 that
> is,
> the generic mechanism is equally applicable.  Assuming that=E2=80=99s rig=
ht (note
> inserted comma and split sentences):
>
> NEW
>    [I-D.ietf-pce-association-group] introduces a generic mechanism to
>    create a grouping of LSPs, which can then be used to define
>    associations between a set of LSPs.  The mechanism is equally
>    applicable to stateful PCE (active and passive modes) and stateless
>    PCE.
> END
>
> =E2=80=94 Section 3.2 =E2=80=94
>
>       Protecting (P): 1 bit - This bit is as defined in Section 14.1 of
>       [RFC4872] to indicate if the LSP is working or protection LSP.
>
> At a minimum, make it =E2=80=9Ca working or protection LSP=E2=80=9D (add =
the article).
> Better still, =E2=80=9Ca working (0) or protection (1) LSP.=E2=80=9D  I k=
now it says that
> in
> RFC 4872, but I think it makes sense to include that here.
>
>       Secondary (S): 1 bit - This bit is as defined in Section 14.1 of
>       [RFC4872] to indicate if the LSP is primary or secondary LSP.  The
>       S flag is ignored if the P flag is not set.
>
> Similarly, add the article =E2=80=9Ca=E2=80=9D, and also consider =E2=80=
=9Ca primary (0) or
> secondary
> (1) LSP.=E2=80=9D
>
>    If the TLV is missing, it is considered that the LSP is the working
>    LSP (i.e. as if P bit is unset).
>
> Is this really =E2=80=9Cthe working LSP=E2=80=9D, or should it be =E2=80=
=9Ca working LSP=E2=80=9D?
>
> =E2=80=94 Section 4 =E2=80=94
>
>    An LSP is associated with other LSPs with which they interact by
>    adding them to a common association group via the ASSOCIATION object.
>
> The number disagreement here is confusing, so I=E2=80=99m not sure what y=
ou mean to
> say.  I think you mean that the other LSPs are added to the group, in whi=
ch
> case change =E2=80=9Cthey interact=E2=80=9D to =E2=80=9Cit interacts=E2=
=80=9D.
>
> =E2=80=94 Section 4.2 =E2=80=94
>
>    A PCC can associate a set of LSPs under its control for path
>    protection purpose.
>
> =E2=80=9Cpurposes=E2=80=9D
>
>    PCC reports the change in association to PCE(s) via Path Computation
>    Report (PCRpt) message.
>
> Either =E2=80=9Ca Path Computation Report (PCRpt) message=E2=80=9D or =E2=
=80=9CPath Computation
> Report
> (PCRpt) messages=E2=80=9D.
>
>    It is expected that both working and protection LSP are delegated
>
> =E2=80=9CLSPs=E2=80=9D
>
> =E2=80=94 Section 4.5 =E2=80=94
>
>    When the protection type is set to 1+1 or 1:N with N=3D1, there MUST b=
e
> =E2=80=A6
>    When the protection type is set to 1:N with N>1, there MUST be
>
> This is a style thing, so take it or leave it as you please =E2=80=94 it=
=E2=80=99s not
> wrong
> the way it=E2=80=99s written.  It=E2=80=99s just that the =E2=80=9C1:N wi=
th N=3D1=E2=80=9D and =E2=80=9C1:N with N>1=E2=80=9D
> distinction isn=E2=80=99t necessary, and I think it=E2=80=99s distracting=
 and invites
> uncertainty.  If you just made these like this:
>
> NEW
>    When the protection type is set to 1+1, there MUST be
> =E2=80=A6
>    When the protection type is set to 1:N, there MUST be
> END
>
> =E2=80=A6it would be equally correct, but also simpler and, I think, less=
 likely
> to be
> confusing.
>
> =E2=80=94 Section 5 =E2=80=94
>
>    association of one LSP to another LSP across different RSVP - Traffic
>    Engineering (RSVP-TE) sessions
>
> Is it typical to have that hyphen there in the first line?  Isn=E2=80=99t=
 it more
> typical to write =E2=80=9CRSVP Traffic Engineering (RSVP-TE)=E2=80=9D wit=
hout the extra
> hyphen?
>
>    The information in the PPAG TLV in PCEP as received from the
>    PCE, is used to trigger
>
> Remove the comma.
>
>
>

--00000000000059ff900592c3549b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi Barry,</div><div><br></div><div>Many thanks for yo=
ur review. Comments are incorporated in the working copy (diff attached).</=
div><div><br></div><div>For this one comment -&gt;</div><div>=3D=3D=3D<br>=
=E2=80=94 Section 4.5 =E2=80=94<br><br>=C2=A0 =C2=A0When the protection typ=
e is set to 1+1 or 1:N with N=3D1, there MUST be<br>=E2=80=A6<br>=C2=A0 =C2=
=A0When the protection type is set to 1:N with N&gt;1, there MUST be<br><br=
>This is a style thing, so take it or leave it as you please =E2=80=94 it=
=E2=80=99s not wrong<br>the way it=E2=80=99s written.=C2=A0 It=E2=80=99s ju=
st that the =E2=80=9C1:N with N=3D1=E2=80=9D and =E2=80=9C1:N with N&gt;1=
=E2=80=9D<br>distinction isn=E2=80=99t necessary, and I think it=E2=80=99s =
distracting and invites<br>uncertainty.=C2=A0 If you just made these like t=
his:<br><br>NEW<br>=C2=A0 =C2=A0When the protection type is set to 1+1, the=
re MUST be<br>=E2=80=A6<br>=C2=A0 =C2=A0When the protection type is set to =
1:N, there MUST be<br>END<br><br>=E2=80=A6it would be equally correct, but =
also simpler and, I think, less likely to be<br>confusing.<br>=3D=3D=3D<br>=
<br>The first sentence is for the case 1+1 and 1:1. Since RFC 4872 does<br>=
not define an explicit state 1:1, it define 1:N only this wording was<br>ch=
osen. I have made this change &quot;When the protection type is set to<br>1=
+1 or 1:1 (1:N with N=3D1)...&quot;.</div><div><br></div><div><br></div><di=
v>Thanks,</div><div>Mahendra</div></div><br><div class=3D"gmail_quote"><div=
 dir=3D"ltr" class=3D"gmail_attr">On Sun, Sep 15, 2019 at 3:23 AM Barry Lei=
ba via Datatracker &lt;<a href=3D"mailto:noreply@ietf.org">noreply@ietf.org=
</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">=
Barry Leiba has entered the following ballot position for<br>
draft-ietf-pce-stateful-path-protection-10: No Objection<br>
<br>
When responding, please keep the subject line intact and reply to all<br>
email addresses included in the To and CC lines. (Feel free to cut this<br>
introductory paragraph, however.)<br>
<br>
<br>
Please refer to <a href=3D"https://www.ietf.org/iesg/statement/discuss-crit=
eria.html" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/iesg/s=
tatement/discuss-criteria.html</a><br>
for more information about IESG DISCUSS and COMMENT positions.<br>
<br>
<br>
The document, along with other ballot positions, can be found here:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-path-pr=
otection/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.or=
g/doc/draft-ietf-pce-stateful-path-protection/</a><br>
<br>
<br>
<br>
----------------------------------------------------------------------<br>
COMMENT:<br>
----------------------------------------------------------------------<br>
<br>
Thanks for this document.=C2=A0 I have only editorial suggestions.=C2=A0 Th=
ere&#39;s no need<br>
to reply in any detail; just please consider adopting these suggestions. <b=
r>
Thanks.<br>
<br>
=E2=80=94 Abstract =E2=80=94<br>
<br>
=C2=A0 =C2=A0Multiprotocol Label Switching Traffic<br>
=C2=A0 =C2=A0Engineering Label Switched Paths (MPLS LSP)<br>
<br>
Shouldn=E2=80=99t that be =E2=80=9C(MPLS-TE LSPs)=E2=80=9D?<br>
<br>
=E2=80=94 Section 1 =E2=80=94<br>
<br>
=C2=A0 =C2=A0[RFC5440] describes PCEP for communication between a Path Comp=
utation<br>
=C2=A0 =C2=A0Client (PCC) and a PCE or between a pair of PCEs as per [RFC46=
55].=C2=A0 A<br>
=C2=A0 =C2=A0PCE computes paths for MPLS-TE LSPs based on various constrain=
ts and<br>
=C2=A0 =C2=A0optimization criteria.<br>
<br>
Even though you expanded some of these acronyms in the Abstract, they have =
to<br>
be expanded again in the Introduction, because the Abstract and the documen=
t<br>
itself each has to stand separately.<br>
<br>
That said, =E2=80=9CMPLS-TE=E2=80=9D and =E2=80=9CPCE=E2=80=9D are in the R=
FC Editor=E2=80=99s list of common acronyms<br>
that don=E2=80=99t need expansion, so you can expand them or not, as you pl=
ease.=C2=A0 But<br>
=E2=80=9CPCEP=E2=80=9D and =E2=80=9CLSP=E2=80=9D do need expansion here.<br=
>
<br>
You should also be consistent in using =E2=80=9CMPLS-TE=E2=80=9D (with the =
hyphen), so please<br>
check the instances of =E2=80=9CMPLS TE=E2=80=9D without the hyphen, and ch=
ange them.=C2=A0 The RFC<br>
Editor will flag this anyway, and it saves time during final editing and AU=
TH48<br>
if you fix it now.<br>
<br>
=C2=A0 =C2=A0It includes<br>
=C2=A0 =C2=A0mechanisms to effect LSP state synchronization between PCCs an=
d PCEs,<br>
=C2=A0 =C2=A0delegation of control of LSPs to PCEs, and PCE control of timi=
ng and<br>
=C2=A0 =C2=A0sequence of path computations within and across PCEP sessions =
and<br>
=C2=A0 =C2=A0focuses on a model where LSPs are configured on the PCC and co=
ntrol<br>
=C2=A0 =C2=A0over them is delegated to the PCE.<br>
<br>
This is a really long sentence, and can do with being split in two.=C2=A0 I=
 suggest<br>
changing =E2=80=9Csessions and=E2=80=9D to =E2=80=9Csessions.=C2=A0 Statefu=
l PCE=E2=80=9D.<br>
<br>
=C2=A0 =C2=A0Furthermore, a mechanism to<br>
=C2=A0 =C2=A0dynamically instantiate LSPs on a PCC based on the requests fr=
om a<br>
=C2=A0 =C2=A0stateful PCE or a controller using stateful PCE, is specified =
in<br>
=C2=A0 =C2=A0[RFC8281].<br>
<br>
This reads oddly in passive voice, and you have a clear subject to use.=C2=
=A0 So I<br>
suggest:<br>
<br>
NEW<br>
=C2=A0 =C2=A0Furthermore, [RFC8281] specifies a mechanism to<br>
=C2=A0 =C2=A0dynamically instantiate LSPs on a PCC based on the requests fr=
om a<br>
=C2=A0 =C2=A0stateful PCE or a controller using stateful PCE.<br>
END<br>
<br>
=C2=A0 =C2=A0 =C2=A0 computes the path for the protection LSP and update th=
e PCC with<br>
<br>
=E2=80=9Cupdates=E2=80=9D<br>
<br>
=C2=A0 =C2=A0Note that protection LSP can be established (signaled) prior t=
o the<br>
=C2=A0 =C2=A0failure (in which case the LSP is said to be in standby mode<b=
r>
=C2=A0 =C2=A0[RFC4427] or a Primary LSP [RFC4872]) or post failure of the<b=
r>
=C2=A0 =C2=A0corresponding working LSP according to the operator choice/pol=
icy<br>
=C2=A0 =C2=A0(known as secondary LSP [RFC4872]).<br>
<br>
=E2=80=9Ca protection LSP=E2=80=9D<br>
<br>
I suggest changing =E2=80=9Cpost failure=E2=80=9D to =E2=80=9Cafter failure=
=E2=80=9D, as it reads better.<br>
<br>
I=E2=80=99m not sure about the antecedent to =E2=80=9Caccording to the oper=
ator choice/policy=E2=80=9D.<br>
=C2=A0I think you mean that the establishment can be prior to failure or af=
ter<br>
failure, according to operator choice or policy, is that right?=C2=A0 In th=
at case,<br>
the sentence isn=E2=80=99t worded well.=C2=A0 May I suggest this?:<br>
<br>
NEW<br>
=C2=A0 =C2=A0Note that a protection LSP can be established (signaled) befor=
e<br>
=C2=A0 =C2=A0the failure (in which case the LSP is said to be in standby mo=
de<br>
=C2=A0 =C2=A0[RFC4427] or a Primary LSP [RFC4872]) or after failure of the<=
br>
=C2=A0 =C2=A0corresponding working LSP (known as secondary LSP [RFC4872]).<=
br>
=C2=A0 =C2=A0Whether to establish it before or after failure is according<b=
r>
=C2=A0 =C2=A0to operator choice or policy.<br>
END<br>
<br>
=C2=A0 =C2=A0[I-D.ietf-pce-association-group] introduces a generic mechanis=
m to<br>
=C2=A0 =C2=A0create a grouping of LSPs which can then be used to define<br>
=C2=A0 =C2=A0associations between a set of LSPs that is equally applicable =
to<br>
=C2=A0 =C2=A0stateful PCE (active and passive modes) and stateless PCE.<br>
<br>
When I first read this I thought =E2=80=9Cthat is equally applicable=E2=80=
=9D applied to the<br>
set of LSPs.=C2=A0 I think you mean it to apply to the generic mechanism =
=E2=80=94 that is,<br>
the generic mechanism is equally applicable.=C2=A0 Assuming that=E2=80=99s =
right (note<br>
inserted comma and split sentences):<br>
<br>
NEW<br>
=C2=A0 =C2=A0[I-D.ietf-pce-association-group] introduces a generic mechanis=
m to<br>
=C2=A0 =C2=A0create a grouping of LSPs, which can then be used to define<br=
>
=C2=A0 =C2=A0associations between a set of LSPs.=C2=A0 The mechanism is equ=
ally<br>
=C2=A0 =C2=A0applicable to stateful PCE (active and passive modes) and stat=
eless<br>
=C2=A0 =C2=A0PCE.<br>
END<br>
<br>
=E2=80=94 Section 3.2 =E2=80=94<br>
<br>
=C2=A0 =C2=A0 =C2=A0 Protecting (P): 1 bit - This bit is as defined in Sect=
ion 14.1 of<br>
=C2=A0 =C2=A0 =C2=A0 [RFC4872] to indicate if the LSP is working or protect=
ion LSP.<br>
<br>
At a minimum, make it =E2=80=9Ca working or protection LSP=E2=80=9D (add th=
e article).<br>
Better still, =E2=80=9Ca working (0) or protection (1) LSP.=E2=80=9D=C2=A0 =
I know it says that in<br>
RFC 4872, but I think it makes sense to include that here.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 Secondary (S): 1 bit - This bit is as defined in Secti=
on 14.1 of<br>
=C2=A0 =C2=A0 =C2=A0 [RFC4872] to indicate if the LSP is primary or seconda=
ry LSP.=C2=A0 The<br>
=C2=A0 =C2=A0 =C2=A0 S flag is ignored if the P flag is not set.<br>
<br>
Similarly, add the article =E2=80=9Ca=E2=80=9D, and also consider =E2=80=9C=
a primary (0) or secondary<br>
(1) LSP.=E2=80=9D<br>
<br>
=C2=A0 =C2=A0If the TLV is missing, it is considered that the LSP is the wo=
rking<br>
=C2=A0 =C2=A0LSP (i.e. as if P bit is unset).<br>
<br>
Is this really =E2=80=9Cthe working LSP=E2=80=9D, or should it be =E2=80=9C=
a working LSP=E2=80=9D?<br>
<br>
=E2=80=94 Section 4 =E2=80=94<br>
<br>
=C2=A0 =C2=A0An LSP is associated with other LSPs with which they interact =
by<br>
=C2=A0 =C2=A0adding them to a common association group via the ASSOCIATION =
object.<br>
<br>
The number disagreement here is confusing, so I=E2=80=99m not sure what you=
 mean to<br>
say.=C2=A0 I think you mean that the other LSPs are added to the group, in =
which<br>
case change =E2=80=9Cthey interact=E2=80=9D to =E2=80=9Cit interacts=E2=80=
=9D.<br>
<br>
=E2=80=94 Section 4.2 =E2=80=94<br>
<br>
=C2=A0 =C2=A0A PCC can associate a set of LSPs under its control for path<b=
r>
=C2=A0 =C2=A0protection purpose.<br>
<br>
=E2=80=9Cpurposes=E2=80=9D<br>
<br>
=C2=A0 =C2=A0PCC reports the change in association to PCE(s) via Path Compu=
tation<br>
=C2=A0 =C2=A0Report (PCRpt) message.<br>
<br>
Either =E2=80=9Ca Path Computation Report (PCRpt) message=E2=80=9D or =E2=
=80=9CPath Computation Report<br>
(PCRpt) messages=E2=80=9D.<br>
<br>
=C2=A0 =C2=A0It is expected that both working and protection LSP are delega=
ted<br>
<br>
=E2=80=9CLSPs=E2=80=9D<br>
<br>
=E2=80=94 Section 4.5 =E2=80=94<br>
<br>
=C2=A0 =C2=A0When the protection type is set to 1+1 or 1:N with N=3D1, ther=
e MUST be<br>
=E2=80=A6<br>
=C2=A0 =C2=A0When the protection type is set to 1:N with N&gt;1, there MUST=
 be<br>
<br>
This is a style thing, so take it or leave it as you please =E2=80=94 it=E2=
=80=99s not wrong<br>
the way it=E2=80=99s written.=C2=A0 It=E2=80=99s just that the =E2=80=9C1:N=
 with N=3D1=E2=80=9D and =E2=80=9C1:N with N&gt;1=E2=80=9D<br>
distinction isn=E2=80=99t necessary, and I think it=E2=80=99s distracting a=
nd invites<br>
uncertainty.=C2=A0 If you just made these like this:<br>
<br>
NEW<br>
=C2=A0 =C2=A0When the protection type is set to 1+1, there MUST be<br>
=E2=80=A6<br>
=C2=A0 =C2=A0When the protection type is set to 1:N, there MUST be<br>
END<br>
<br>
=E2=80=A6it would be equally correct, but also simpler and, I think, less l=
ikely to be<br>
confusing.<br>
<br>
=E2=80=94 Section 5 =E2=80=94<br>
<br>
=C2=A0 =C2=A0association of one LSP to another LSP across different RSVP - =
Traffic<br>
=C2=A0 =C2=A0Engineering (RSVP-TE) sessions<br>
<br>
Is it typical to have that hyphen there in the first line?=C2=A0 Isn=E2=80=
=99t it more<br>
typical to write =E2=80=9CRSVP Traffic Engineering (RSVP-TE)=E2=80=9D witho=
ut the extra hyphen?<br>
<br>
=C2=A0 =C2=A0The information in the PPAG TLV in PCEP as received from the<b=
r>
=C2=A0 =C2=A0PCE, is used to trigger<br>
<br>
Remove the comma.<br>
<br>
<br>
</blockquote></div>

--00000000000059ff900592c3549b--

--00000000000059ff940592c3549d
Content-Type: text/html; charset="UTF-8"; 
 name="Diff: draft-ietf-pce-stateful-path-protection-10.txt -
 draft-ietf-pce-stateful-path-protection-11.txt.html"
Content-Disposition: attachment; 
 filename="Diff: draft-ietf-pce-stateful-path-protection-10.txt -
 draft-ietf-pce-stateful-path-protection-11.txt.html"
Content-Transfer-Encoding: base64
Content-ID: <f_k0o4rv6q0>
X-Attachment-Id: f_k0o4rv6q0

PCFET0NUWVBFIGh0bWwgUFVCTElDICItLy9XM0MvL0RURCBYSFRNTCAxLjAgVHJhbnNpdGlvbmFs
Ly9FTiIgImh0dHA6Ly93d3cudzMub3JnL1RSL3hodG1sMS9EVEQveGh0bWwxLXRyYW5zaXRpb25h
bC5kdGQiPgo8IS0tIEdlbmVyYXRlZCBieSByZmNkaWZmIDEuNDc6IHJmY2RpZmYgIC0tPgo8IS0t
IDwhRE9DVFlQRSBodG1sIFBVQkxJQyAiLS8vVzNDLy9EVEQgSFRNTCA0LjAxIFRyYW5zaXRpb25h
bCIgPiAtLT4KPCEtLSBTeXN0ZW06IExpbnV4IGRlY2hhdW5hYyAzLjIuMC02LWFtZDY0ICMxIFNN
UCBEZWJpYW4gMy4yLjEwMi0xIHg4Nl82NCBHTlUvTGludXggLS0+CjwhLS0gVXNpbmcgYXdrOiAv
dXNyL2Jpbi9nYXdrOiBHTlUgQXdrIDQuMS4xLCBBUEk6IDEuMSAoR05VIE1QRlIgMy4xLjMsIEdO
VSBNUCA2LjAuMCkgLS0+CjwhLS0gVXNpbmcgZGlmZjogL3Vzci9iaW4vZGlmZjogZGlmZiAoR05V
IGRpZmZ1dGlscykgMy4zIC0tPgo8IS0tIFVzaW5nIHdkaWZmOiAvdXNyL2Jpbi93ZGlmZjogd2Rp
ZmYgKEdOVSB3ZGlmZikgMS4yLjIgLS0+CjxodG1sIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8x
OTk5L3hodG1sIj48aGVhZD4gCiAgPG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250
ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9VVRGLTgiPiAKICA8bWV0YSBodHRwLWVxdWl2PSJDb250
ZW50LVN0eWxlLVR5cGUiIGNvbnRlbnQ9InRleHQvY3NzIj4gCiAgPHRpdGxlPkRpZmY6IGRyYWZ0
LWlldGYtcGNlLXN0YXRlZnVsLXBhdGgtcHJvdGVjdGlvbi0xMC50eHQgLSBkcmFmdC1pZXRmLXBj
ZS1zdGF0ZWZ1bC1wYXRoLXByb3RlY3Rpb24tMTEudHh0PC90aXRsZT4gCiAgPHN0eWxlIHR5cGU9
InRleHQvY3NzIj4gCiAgICBib2R5ICAgIHsgbWFyZ2luOiAwLjRleDsgbWFyZ2luLXJpZ2h0OiBh
dXRvOyB9IAogICAgdHIgICAgICB7IH0gCiAgICB0ZCAgICAgIHsgd2hpdGUtc3BhY2U6IHByZTsg
Zm9udC1mYW1pbHk6IG1vbm9zcGFjZTsgdmVydGljYWwtYWxpZ246IHRvcDsgZm9udC1zaXplOiAw
Ljg2ZW07fSAKICAgIHRoICAgICAgeyBmb250LXNpemU6IDAuODZlbTsgfSAKICAgIC5zbWFsbCAg
eyBmb250LXNpemU6IDAuNmVtOyBmb250LXN0eWxlOiBpdGFsaWM7IGZvbnQtZmFtaWx5OiBWZXJk
YW5hLCBIZWx2ZXRpY2EsIHNhbnMtc2VyaWY7IH0gCiAgICAubGVmdCAgIHsgYmFja2dyb3VuZC1j
b2xvcjogI0VFRTsgfSAKICAgIC5yaWdodCAgeyBiYWNrZ3JvdW5kLWNvbG9yOiAjRkZGOyB9IAog
ICAgLmRpZmYgICB7IGJhY2tncm91bmQtY29sb3I6ICNDQ0Y7IH0gCiAgICAubGJsb2NrIHsgYmFj
a2dyb3VuZC1jb2xvcjogI0JGQjsgfSAKICAgIC5yYmxvY2sgeyBiYWNrZ3JvdW5kLWNvbG9yOiAj
RkY4OyB9IAogICAgLmluc2VydCB7IGJhY2tncm91bmQtY29sb3I6ICM4RkY7IH0gCiAgICAuZGVs
ZXRlIHsgYmFja2dyb3VuZC1jb2xvcjogI0FDRjsgfSAKICAgIC52b2lkICAgeyBiYWNrZ3JvdW5k
LWNvbG9yOiAjRkZCOyB9IAogICAgLmNvbnQgICB7IGJhY2tncm91bmQtY29sb3I6ICNFRUU7IH0g
CiAgICAubGluZWJyIHsgYmFja2dyb3VuZC1jb2xvcjogI0FBQTsgfSAKICAgIC5saW5lbm8geyBj
b2xvcjogcmVkOyBiYWNrZ3JvdW5kLWNvbG9yOiAjRkZGOyBmb250LXNpemU6IDAuN2VtOyB0ZXh0
LWFsaWduOiByaWdodDsgcGFkZGluZzogMCAycHg7IH0gCiAgICAuZWxpcHNpc3sgYmFja2dyb3Vu
ZC1jb2xvcjogI0FBQTsgfSAKICAgIC5sZWZ0IC5jb250IHsgYmFja2dyb3VuZC1jb2xvcjogI0RE
RDsgfSAKICAgIC5yaWdodCAuY29udCB7IGJhY2tncm91bmQtY29sb3I6ICNFRUU7IH0gCiAgICAu
bGJsb2NrIC5jb250IHsgYmFja2dyb3VuZC1jb2xvcjogIzlEOTsgfSAKICAgIC5yYmxvY2sgLmNv
bnQgeyBiYWNrZ3JvdW5kLWNvbG9yOiAjREQ2OyB9IAogICAgLmluc2VydCAuY29udCB7IGJhY2tn
cm91bmQtY29sb3I6ICMwREQ7IH0gCiAgICAuZGVsZXRlIC5jb250IHsgYmFja2dyb3VuZC1jb2xv
cjogIzhBRDsgfSAKICAgIC5zdGF0cywgLnN0YXRzIHRkLCAuc3RhdHMgdGggeyBiYWNrZ3JvdW5k
LWNvbG9yOiAjRUVFOyBwYWRkaW5nOiAycHggMDsgfSAKICAgIHNwYW4uaGlkZSB7IGRpc3BsYXk6
IG5vbmU7IGNvbG9yOiAjYWFhO30gICAgYTpob3ZlciBzcGFuIHsgZGlzcGxheTogaW5saW5lOyB9
ICAgIHRyLmNoYW5nZSB7IGJhY2tncm91bmQtY29sb3I6IGdyYXk7IH0gCiAgICB0ci5jaGFuZ2Ug
YSB7IHRleHQtZGVjb3JhdGlvbjogbm9uZTsgY29sb3I6IGJsYWNrIH0gCiAgPC9zdHlsZT4gCiAg
ICAgPHNjcmlwdD4KdmFyIGNodW5rX2luZGV4ID0gMDsKdmFyIG9sZF9jaHVuayA9IG51bGw7Cgpm
dW5jdGlvbiBmb3JtYXRfY2h1bmsoaW5kZXgpIHsKICAgIHZhciBwcmVmaXggPSAiZGlmZiI7CiAg
ICB2YXIgc3RyID0gaW5kZXgudG9TdHJpbmcoKTsKICAgIGZvciAoeD0wOyB4PCg0LXN0ci5sZW5n
dGgpOyArK3gpIHsKICAgICAgICBwcmVmaXgrPScwJzsKICAgIH0KICAgIHJldHVybiBwcmVmaXgg
KyBzdHI7Cn0KCmZ1bmN0aW9uIGZpbmRfY2h1bmsobil7CiAgICByZXR1cm4gZG9jdW1lbnQucXVl
cnlTZWxlY3RvcigndHJbaWQkPSInICsgbiArICciXScpOwp9CgpmdW5jdGlvbiBjaGFuZ2VfY2h1
bmsob2Zmc2V0KSB7CiAgICB2YXIgaW5kZXggPSBjaHVua19pbmRleCArIG9mZnNldDsKICAgIHZh
ciBuZXdfc3RyOwogICAgdmFyIG5ld19jaHVuazsKCiAgICBuZXdfc3RyID0gZm9ybWF0X2NodW5r
KGluZGV4KTsKICAgIG5ld19jaHVuayA9IGZpbmRfY2h1bmsobmV3X3N0cik7CiAgICBpZiAoIW5l
d19jaHVuaykgewogICAgICAgIHJldHVybjsKICAgIH0KICAgIGlmIChvbGRfY2h1bmspIHsKICAg
ICAgICBvbGRfY2h1bmsuc3R5bGUub3V0bGluZSA9ICIiOwogICAgfQogICAgb2xkX2NodW5rID0g
bmV3X2NodW5rOwogICAgb2xkX2NodW5rLnN0eWxlLm91dGxpbmUgPSAiMXB4IHNvbGlkIHJlZCI7
CiAgICB3aW5kb3cubG9jYXRpb24ucmVwbGFjZSgiIyIgKyBuZXdfc3RyKQogICAgd2luZG93LnNj
cm9sbEJ5KDAsLTEwMCk7CiAgICBjaHVua19pbmRleCA9IGluZGV4Owp9Cgpkb2N1bWVudC5vbmtl
eWRvd24gPSBmdW5jdGlvbihlKSB7CiAgICBzd2l0Y2ggKGUua2V5Q29kZSkgewogICAgY2FzZSA3
ODoKICAgICAgICBjaGFuZ2VfY2h1bmsoMSk7CiAgICAgICAgYnJlYWs7CiAgICBjYXNlIDgwOgog
ICAgICAgIGNoYW5nZV9jaHVuaygtMSk7CiAgICAgICAgYnJlYWs7CiAgICB9Cn07CiAgIDwvc2Ny
aXB0PiAKPC9oZWFkPiAKPGJvZHk+IAogIDx0YWJsZSBjZWxsc3BhY2luZz0iMCIgY2VsbHBhZGRp
bmc9IjAiIGJvcmRlcj0iMCI+IAogIDx0Ym9keT48dHIgaWQ9InBhcnQtMSIgYmdjb2xvcj0ib3Jh
bmdlIj48dGg+PC90aD48dGg+PGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy9yZmNkaWZm
P3VybDI9ZHJhZnQtaWV0Zi1wY2Utc3RhdGVmdWwtcGF0aC1wcm90ZWN0aW9uLTEwLnR4dCIgc3R5
bGU9ImNvbG9yOiMwMDg7IHRleHQtZGVjb3JhdGlvbjpub25lOyI+Jmx0OzwvYT4mbmJzcDs8YSBo
cmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1wY2Utc3RhdGVmdWwt
cGF0aC1wcm90ZWN0aW9uLTEwLnR4dCIgc3R5bGU9ImNvbG9yOiMwMDgiPmRyYWZ0LWlldGYtcGNl
LXN0YXRlZnVsLXBhdGgtcHJvdGVjdGlvbi0xMC50eHQ8L2E+Jm5ic3A7PC90aD48dGg+IDwvdGg+
PHRoPiZuYnNwOzxhIGhyZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRm
LXBjZS1zdGF0ZWZ1bC1wYXRoLXByb3RlY3Rpb24tMTEudHh0IiBzdHlsZT0iY29sb3I6IzAwOCI+
ZHJhZnQtaWV0Zi1wY2Utc3RhdGVmdWwtcGF0aC1wcm90ZWN0aW9uLTExLnR4dDwvYT4mbmJzcDs8
YSBocmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL3JmY2RpZmY/dXJsMT1kcmFmdC1pZXRmLXBj
ZS1zdGF0ZWZ1bC1wYXRoLXByb3RlY3Rpb24tMTEudHh0IiBzdHlsZT0iY29sb3I6IzAwODsgdGV4
dC1kZWNvcmF0aW9uOm5vbmU7Ij4mZ3Q7PC9hPjwvdGg+PHRoPjwvdGg+PC90cj4gCiAgICAgIDx0
cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+UENFIFdvcmtp
bmcgR3JvdXAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgSC4gQW5hbnRoYWty
aXNobmFuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+UENFIFdvcmtpbmcgR3JvdXAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgSC4gQW5hbnRoYWtyaXNobmFuPC90
ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij5JbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIE5ldGZsaXg8L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij5JbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgIE5ldGZsaXg8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPkludGVuZGVkIHN0YXR1czogU3RhbmRhcmRzIFRyYWNrICAgICAgICAgICAgICAgICAgICAg
ICAgICAgIFMuIFNpdmFiYWxhbjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPkludGVu
ZGVkIHN0YXR1czogU3RhbmRhcmRzIFRyYWNrICAgICAgICAgICAgICAgICAgICAgICAgICAgIFMu
IFNpdmFiYWxhbjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGlk
PSJkaWZmMDAwMSI+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj5FeHBpcmVzOiBNYXJjaCA8c3BhbiBjbGFzcz0iZGVsZXRl
Ij4zLCAyMDIwIDwvc3Bhbj4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgIENpc2NvPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPkV4cGlyZXM6IE1hcmNo
IDxzcGFuIGNsYXNzPSJpbnNlcnQiPjE5LCAyMDIwPC9zcGFuPiAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgQ2lzY288L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
PjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICBDLiBCYXJ0aDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBD
LiBCYXJ0aDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBKdW5pcGVyIE5ldHdvcmtzPC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICBKdW5pcGVyIE5ldHdvcmtzPC90ZD48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRk
IGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgSS4gTWluZWk8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgSS4gTWluZWk8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBHb29n
bGUsIEluYzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBHb29nbGUsIEluYzwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBNLiBOZWdpPC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICBNLiBOZWdpPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
IEh1YXdlaSBUZWNobm9sb2dpZXM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIEh1YXdlaSBU
ZWNobm9sb2dpZXM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBp
ZD0iZGlmZjAwMDIiPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+ICAgQXVndXN0IDMxPC9z
cGFuPiwgMjAxOTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICA8c3BhbiBjbGFzcz0iaW5z
ZXJ0Ij5TZXB0ZW1iZXIgMTY8L3NwYW4+LCAyMDE5PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPiAgICBQQ0VQIEV4dGVuc2lvbnMgZm9yIEFzc29jaWF0aW5nIFdvcmtpbmcgYW5kIFBy
b3RlY3Rpb24gTFNQcyB3aXRoPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgIFBD
RVAgRXh0ZW5zaW9ucyBmb3IgQXNzb2NpYXRpbmcgV29ya2luZyBhbmQgUHJvdGVjdGlvbiBMU1Bz
IHdpdGg8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgIFN0YXRlZnVsIFBDRTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgIFN0YXRlZnVsIFBDRTwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGlkPSJkaWZmMDAwMyI+PHRkPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICAgICAg
ICAgICAgICBkcmFmdC1pZXRmLXBjZS1zdGF0ZWZ1bC1wYXRoLXByb3RlY3Rpb24tMTxzcGFuIGNs
YXNzPSJkZWxldGUiPjA8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAg
ICAgICAgICAgICAgIGRyYWZ0LWlldGYtcGNlLXN0YXRlZnVsLXBhdGgtcHJvdGVjdGlvbi0xPHNw
YW4gY2xhc3M9Imluc2VydCI+MTwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVm
dCI+QWJzdHJhY3Q8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij5BYnN0cmFjdDwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBBbiBhY3RpdmUgc3RhdGVmdWwgUGF0aCBD
b21wdXRhdGlvbiBFbGVtZW50IChQQ0UpIGlzIGNhcGFibGUgb2Y8L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJpZ2h0Ij4gICBBbiBhY3RpdmUgc3RhdGVmdWwgUGF0aCBDb21wdXRhdGlvbiBFbGVt
ZW50IChQQ0UpIGlzIGNhcGFibGUgb2Y8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGNv
bXB1dGluZyBhcyB3ZWxsIGFzIGNvbnRyb2xsaW5nIHZpYSBQYXRoIENvbXB1dGF0aW9uIEVsZW1l
bnQ8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBjb21wdXRpbmcgYXMgd2VsbCBh
cyBjb250cm9sbGluZyB2aWEgUGF0aCBDb21wdXRhdGlvbiBFbGVtZW50PC90ZD48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRk
IGNsYXNzPSJsZWZ0Ij4gICBDb21tdW5pY2F0aW9uIFByb3RvY29sIChQQ0VQKSBNdWx0aXByb3Rv
Y29sIExhYmVsIFN3aXRjaGluZyBUcmFmZmljPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdo
dCI+ICAgQ29tbXVuaWNhdGlvbiBQcm90b2NvbCAoUENFUCkgTXVsdGlwcm90b2NvbCBMYWJlbCBT
d2l0Y2hpbmcgVHJhZmZpYzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyIGlkPSJkaWZmMDAwNCI+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICBFbmdpbmVlcmluZyBMYWJlbCBTd2l0Y2hl
ZCBQYXRocyA8c3BhbiBjbGFzcz0iZGVsZXRlIj4oTVBMUyBMU1ApLjwvc3Bhbj4gIEZ1cnRoZXJt
b3JlLCBpdCBpcyBhbHNvPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIEVuZ2lu
ZWVyaW5nIDxzcGFuIGNsYXNzPSJpbnNlcnQiPihNUExTLVRFKTwvc3Bhbj4gTGFiZWwgU3dpdGNo
ZWQgUGF0aHMgPHNwYW4gY2xhc3M9Imluc2VydCI+KExTUHMpLjwvc3Bhbj4gIEZ1cnRoZXJtb3Jl
LCBpdDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICBwb3NzaWJsZSBmb3IgYW4gYWN0
aXZlIHN0YXRlZnVsIFBDRSB0byBjcmVhdGUsIG1haW50YWluLCBhbmQgZGVsZXRlPC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIGlzIGFsc28gcG9zc2libGUgZm9yIGFuIGFjdGl2
ZSBzdGF0ZWZ1bCBQQ0UgdG8gY3JlYXRlLCBtYWludGFpbiwgYW5kPC90ZD48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsYmxvY2siPiAgIExTUHMuICBUaGlzIGRvY3VtZW50IGRlZmluZXMgdGhlIFBDRVAgZXh0
ZW5zaW9uIHRvIGFzc29jaWF0ZSB0d28gb3I8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9j
ayI+ICAgZGVsZXRlIExTUHMuICBUaGlzIGRvY3VtZW50IGRlZmluZXMgdGhlIFBDRVAgZXh0ZW5z
aW9uIHRvIGFzc29jaWF0ZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICBtb3JlIExT
UHMgdG8gcHJvdmlkZSBlbmQtdG8tZW5kIHBhdGggcHJvdGVjdGlvbi48L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJibG9jayI+ICAgdHdvIG9yIG1vcmUgTFNQcyB0byBwcm92aWRlIGVuZC10by1l
bmQgcGF0aCBwcm90ZWN0aW9uLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij5TdGF0
dXMgb2YgVGhpcyBNZW1vPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+U3RhdHVzIG9m
IFRoaXMgTWVtbzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBUaGlzIEludGVy
bmV0LURyYWZ0IGlzIHN1Ym1pdHRlZCBpbiBmdWxsIGNvbmZvcm1hbmNlIHdpdGggdGhlPC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgVGhpcyBJbnRlcm5ldC1EcmFmdCBpcyBzdWJt
aXR0ZWQgaW4gZnVsbCBjb25mb3JtYW5jZSB3aXRoIHRoZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0i
bGVmdCI+ICAgcHJvdmlzaW9ucyBvZiBCQ1AgNzggYW5kIEJDUCA3OS48L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij4gICBwcm92aXNpb25zIG9mIEJDUCA3OCBhbmQgQkNQIDc5LjwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBJbnRlcm5ldC1EcmFmdHMgYXJlIHdvcmtp
bmcgZG9jdW1lbnRzIG9mIHRoZSBJbnRlcm5ldCBFbmdpbmVlcmluZzwvdGQ+PHRkPiA8L3RkPjx0
ZCBjbGFzcz0icmlnaHQiPiAgIEludGVybmV0LURyYWZ0cyBhcmUgd29ya2luZyBkb2N1bWVudHMg
b2YgdGhlIEludGVybmV0IEVuZ2luZWVyaW5nPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4g
ICBUYXNrIEZvcmNlIChJRVRGKS4gIE5vdGUgdGhhdCBvdGhlciBncm91cHMgbWF5IGFsc28gZGlz
dHJpYnV0ZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFRhc2sgRm9yY2UgKElF
VEYpLiAgTm90ZSB0aGF0IG90aGVyIGdyb3VwcyBtYXkgYWxzbyBkaXN0cmlidXRlPC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICB3b3JraW5nIGRvY3VtZW50cyBhcyBJbnRlcm5ldC1EcmFm
dHMuICBUaGUgbGlzdCBvZiBjdXJyZW50IEludGVybmV0LTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPiAgIHdvcmtpbmcgZG9jdW1lbnRzIGFzIEludGVybmV0LURyYWZ0cy4gIFRoZSBs
aXN0IG9mIGN1cnJlbnQgSW50ZXJuZXQtPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBE
cmFmdHMgaXMgYXQgaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kcmFmdHMvY3VycmVudC8u
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgRHJhZnRzIGlzIGF0IGh0dHBzOi8v
ZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZHJhZnRzL2N1cnJlbnQvLjwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFz
cz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRk
IGNsYXNzPSJsZWZ0Ij4gICBJbnRlcm5ldC1EcmFmdHMgYXJlIGRyYWZ0IGRvY3VtZW50cyB2YWxp
ZCBmb3IgYSBtYXhpbXVtIG9mIHNpeCBtb250aHM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij4gICBJbnRlcm5ldC1EcmFmdHMgYXJlIGRyYWZ0IGRvY3VtZW50cyB2YWxpZCBmb3IgYSBt
YXhpbXVtIG9mIHNpeCBtb250aHM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGFuZCBt
YXkgYmUgdXBkYXRlZCwgcmVwbGFjZWQsIG9yIG9ic29sZXRlZCBieSBvdGhlciBkb2N1bWVudHMg
YXQgYW55PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgYW5kIG1heSBiZSB1cGRh
dGVkLCByZXBsYWNlZCwgb3Igb2Jzb2xldGVkIGJ5IG90aGVyIGRvY3VtZW50cyBhdCBhbnk8L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIHRpbWUuICBJdCBpcyBpbmFwcHJvcHJpYXRlIHRv
IHVzZSBJbnRlcm5ldC1EcmFmdHMgYXMgcmVmZXJlbmNlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+ICAgdGltZS4gIEl0IGlzIGluYXBwcm9wcmlhdGUgdG8gdXNlIEludGVybmV0LURy
YWZ0cyBhcyByZWZlcmVuY2U8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIG1hdGVyaWFs
IG9yIHRvIGNpdGUgdGhlbSBvdGhlciB0aGFuIGFzICJ3b3JrIGluIHByb2dyZXNzLiI8L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBtYXRlcmlhbCBvciB0byBjaXRlIHRoZW0gb3Ro
ZXIgdGhhbiBhcyAid29yayBpbiBwcm9ncmVzcy4iPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlmZjAwMDUiPjx0ZD48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgVGhpcyBJ
bnRlcm5ldC1EcmFmdCB3aWxsIGV4cGlyZSBvbiBNYXJjaCA8c3BhbiBjbGFzcz0iZGVsZXRlIj4z
PC9zcGFuPiwgMjAyMC48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgVGhpcyBJ
bnRlcm5ldC1EcmFmdCB3aWxsIGV4cGlyZSBvbiBNYXJjaCA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij4x
OTwvc3Bhbj4sIDIwMjAuPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPkNvcHlyaWdo
dCBOb3RpY2U8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij5Db3B5cmlnaHQgTm90aWNl
PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIENvcHlyaWdodCAoYykgMjAxOSBJ
RVRGIFRydXN0IGFuZCB0aGUgcGVyc29ucyBpZGVudGlmaWVkIGFzIHRoZTwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmlnaHQiPiAgIENvcHlyaWdodCAoYykgMjAxOSBJRVRGIFRydXN0IGFuZCB0
aGUgcGVyc29ucyBpZGVudGlmaWVkIGFzIHRoZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
ICAgZG9jdW1lbnQgYXV0aG9ycy4gIEFsbCByaWdodHMgcmVzZXJ2ZWQuPC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyaWdodCI+ICAgZG9jdW1lbnQgYXV0aG9ycy4gIEFsbCByaWdodHMgcmVzZXJ2
ZWQuPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFRoaXMgZG9jdW1lbnQgaXMg
c3ViamVjdCB0byBCQ1AgNzggYW5kIHRoZSBJRVRGIFRydXN0J3MgTGVnYWw8L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBUaGlzIGRvY3VtZW50IGlzIHN1YmplY3QgdG8gQkNQIDc4
IGFuZCB0aGUgSUVURiBUcnVzdCdzIExlZ2FsPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4g
ICBQcm92aXNpb25zIFJlbGF0aW5nIHRvIElFVEYgRG9jdW1lbnRzPC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+ICAgUHJvdmlzaW9ucyBSZWxhdGluZyB0byBJRVRGIERvY3VtZW50czwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgKGh0dHBzOi8vdHJ1c3RlZS5pZXRmLm9yZy9s
aWNlbnNlLWluZm8pIGluIGVmZmVjdCBvbiB0aGUgZGF0ZSBvZjwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPiAgIChodHRwczovL3RydXN0ZWUuaWV0Zi5vcmcvbGljZW5zZS1pbmZvKSBp
biBlZmZlY3Qgb24gdGhlIGRhdGUgb2Y8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIHB1
YmxpY2F0aW9uIG9mIHRoaXMgZG9jdW1lbnQuICBQbGVhc2UgcmV2aWV3IHRoZXNlIGRvY3VtZW50
czwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIHB1YmxpY2F0aW9uIG9mIHRoaXMg
ZG9jdW1lbnQuICBQbGVhc2UgcmV2aWV3IHRoZXNlIGRvY3VtZW50czwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9InBhcnQtMiIgY2xhc3M9ImNoYW5n
ZSI+PHRkPjwvdGQ+PHRoPjxzbWFsbD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8L3NtYWxsPjxhIGhy
ZWY9IiNwYXJ0LTIiPjxlbT4gcGFnZSAyLCBsaW5lIDI4PHNwYW4gY2xhc3M9ImhpZGUiPiDCtjwv
c3Bhbj48L2VtPjwvYT48L3RoPjx0aD4gPC90aD48dGg+PHNtYWxsPnNraXBwaW5nIHRvIGNoYW5n
ZSBhdDwvc21hbGw+PGEgaHJlZj0iI3BhcnQtMiI+PGVtPiBwYWdlIDIsIGxpbmUgMjg8c3BhbiBj
bGFzcz0iaGlkZSI+IMK2PC9zcGFuPjwvZW0+PC9hPjwvdGg+PHRkPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgZGVzY3JpYmVk
IGluIHRoZSBTaW1wbGlmaWVkIEJTRCBMaWNlbnNlLjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmlnaHQiPiAgIGRlc2NyaWJlZCBpbiB0aGUgU2ltcGxpZmllZCBCU0QgTGljZW5zZS48L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+VGFibGUgb2YgQ29udGVudHM8L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij5UYWJsZSBvZiBDb250ZW50czwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFz
cz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRk
IGNsYXNzPSJsZWZ0Ij4gICAxLiAgSW50cm9kdWN0aW9uICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgIDM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij4gICAxLiAgSW50cm9kdWN0aW9uICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAgIDM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgMS4x
LiAgUmVxdWlyZW1lbnRzIExhbmd1YWdlIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuICAgNDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgMS4xLiAgUmVxdWly
ZW1lbnRzIExhbmd1YWdlIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgNDwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgMi4gIFRlcm1pbm9sb2d5IC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gICA0PC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyaWdodCI+ICAgMi4gIFRlcm1pbm9sb2d5IC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gICA0PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij4gICAzLiAgUENFUCBFeHRlbnNpb25zIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAgIDU8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAz
LiAgUENFUCBFeHRlbnNpb25zIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAgIDU8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgMy4xLiAgUGF0aCBQ
cm90ZWN0aW9uIEFzc29jaWF0aW9uIFR5cGUgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgNTwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgMy4xLiAgUGF0aCBQcm90ZWN0aW9u
IEFzc29jaWF0aW9uIFR5cGUgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgNTwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAzLjIuICBQYXRoIFByb3RlY3Rpb24gQXNzb2NpYXRpb24g
VExWIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gICA1PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+ICAgICAzLjIuICBQYXRoIFByb3RlY3Rpb24gQXNzb2NpYXRpb24gVExWIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gICA1PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHIgaWQ9ImRpZmYwMDA2Ij48dGQ+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIDQuICBPcGVyYXRpb24gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgPHNwYW4g
Y2xhc3M9ImRlbGV0ZSI+Njwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+
ICAgNC4gIE9wZXJhdGlvbiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gICA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij43PC9zcGFuPjwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+ICAgICA0LjEuICBTdGF0ZSBTeW5jaHJvbml6YXRpb24gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gICA3PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+ICAgICA0LjEuICBTdGF0ZSBTeW5jaHJvbml6YXRpb24gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gICA3PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgIDQu
Mi4gIFBDQy1Jbml0aWF0ZWQgTFNQcyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAgIDc8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgIDQuMi4gIFBDQy1J
bml0aWF0ZWQgTFNQcyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgIDc8
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgNC4zLiAgUENFLUluaXRpYXRlZCBMU1Bz
ICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgNzwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgNC4zLiAgUENFLUluaXRpYXRlZCBMU1BzICAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgNzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0i
bGVmdCI+ICAgICA0LjQuICBTZXNzaW9uIFRlcm1pbmF0aW9uIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gICA3PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAg
ICA0LjQuICBTZXNzaW9uIFRlcm1pbmF0aW9uIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gICA3PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgIDQuNS4gIEVycm9y
IEhhbmRsaW5nICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgIDg8
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgIDQuNS4gIEVycm9yIEhhbmRsaW5n
ICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgIDg8L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPiAgIDUuICBPdGhlciBDb25zaWRlcmF0aW9ucyAgLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgOTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPiAgIDUuICBPdGhlciBDb25zaWRlcmF0aW9ucyAgLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgOTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAg
Ni4gIElBTkEgQ29uc2lkZXJhdGlvbnMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gICA5PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgNi4gIElBTkEg
Q29uc2lkZXJhdGlvbnMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
ICA5PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgIDYuMS4gIEFzc29jaWF0aW9uIFR5
cGUgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgIDk8L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgIDYuMS4gIEFzc29jaWF0aW9uIFR5cGUgIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgIDk8L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xh
c3M9ImxlZnQiPiAgICAgNi4yLiAgUFBBRyBUTFYgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuICAxMDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PiAgICAgNi4yLiAgUFBBRyBUTFYgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuICAxMDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyIGlkPSJkaWZmMDAwNyI+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICAgIDYuMy4gIFBDRVAgRXJyb3JzIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMTxzcGFuIGNsYXNzPSJk
ZWxldGUiPjA8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgICAgNi4z
LiAgUENFUCBFcnJvcnMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuICAxPHNwYW4gY2xhc3M9Imluc2VydCI+MTwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPiAgIDcuICBTZWN1cml0eSBDb25zaWRlcmF0aW9ucyAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuICAxMTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAg
IDcuICBTZWN1cml0eSBDb25zaWRlcmF0aW9ucyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuICAxMTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgOC4gIE1hbmFnZWFi
aWxpdHkgQ29uc2lkZXJhdGlvbnMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDEx
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgOC4gIE1hbmFnZWFiaWxpdHkgQ29u
c2lkZXJhdGlvbnMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDExPC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgIDguMS4gIENvbnRyb2wgb2YgRnVuY3Rpb24gYW5kIFBv
bGljeSAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMTE8L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij4gICAgIDguMS4gIENvbnRyb2wgb2YgRnVuY3Rpb24gYW5kIFBvbGljeSAgLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMTE8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAg
ICAgOC4yLiAgSW5mb3JtYXRpb24gYW5kIERhdGEgTW9kZWxzIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuICAxMTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgOC4yLiAg
SW5mb3JtYXRpb24gYW5kIERhdGEgTW9kZWxzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
ICAxMTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGlkPSJkaWZm
MDAwOCI+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGJsb2NrIj4gICAgIDguMy4gIExpdmVuZXNzIERldGVjdGlvbiBhbmQgTW9uaXRv
cmluZyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMTxzcGFuIGNsYXNzPSJkZWxldGUiPjE8L3Nw
YW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgICAgOC4zLiAgTGl2ZW5lc3Mg
RGV0ZWN0aW9uIGFuZCBNb25pdG9yaW5nIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAxPHNwYW4g
Y2xhc3M9Imluc2VydCI+Mjwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAg
OC40LiAgVmVyaWZ5IENvcnJlY3QgT3BlcmF0aW9ucyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuICAxMjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgOC40LiAgVmVy
aWZ5IENvcnJlY3QgT3BlcmF0aW9ucyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAx
MjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICA4LjUuICBSZXF1aXJlbWVudHMgT24g
T3RoZXIgUHJvdG9jb2xzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDEyPC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICA4LjUuICBSZXF1aXJlbWVudHMgT24gT3RoZXIgUHJv
dG9jb2xzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDEyPC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij4gICAgIDguNi4gIEltcGFjdCBPbiBOZXR3b3JrIE9wZXJhdGlvbnMgIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAgMTI8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4g
ICAgIDguNi4gIEltcGFjdCBPbiBOZXR3b3JrIE9wZXJhdGlvbnMgIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAgMTI8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0
cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIDkuICBBY2tub3ds
ZWRnbWVudHMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAx
MjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIDkuICBBY2tub3dsZWRnbWVudHMg
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAxMjwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgMTAuIFJlZmVyZW5jZXMgIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDEyPC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyaWdodCI+ICAgMTAuIFJlZmVyZW5jZXMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDEyPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4g
ICAgIDEwLjEuICBOb3JtYXRpdmUgUmVmZXJlbmNlcyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAgMTI8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgIDEwLjEu
ICBOb3JtYXRpdmUgUmVmZXJlbmNlcyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAgMTI8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlm
ZjAwMDkiPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxibG9jayI+ICAgICAxMC4yLiAgSW5mb3JtYXRpdmUgUmVmZXJlbmNlcyAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDE8c3BhbiBjbGFzcz0iZGVsZXRlIj4zPC9z
cGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICAgIDEwLjIuICBJbmZvcm1h
dGl2ZSBSZWZlcmVuY2VzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMTxzcGFu
IGNsYXNzPSJpbnNlcnQiPjQ8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBB
cHBlbmRpeCBBLiAgQ29udHJpYnV0b3IgQWRkcmVzc2VzICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAgMTU8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBBcHBlbmRpeCBB
LiAgQ29udHJpYnV0b3IgQWRkcmVzc2VzICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAg
MTU8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIEF1dGhvcnMnIEFkZHJlc3NlcyAgLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAxNTwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIEF1dGhvcnMnIEFkZHJlc3NlcyAgLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAxNTwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFz
cz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRk
IGNsYXNzPSJsZWZ0Ij4xLiAgSW50cm9kdWN0aW9uPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+MS4gIEludHJvZHVjdGlvbjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHIgaWQ9ImRpZmYwMDEwIj48dGQ+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIFtSRkM1NDQwXSBkZXNj
cmliZXMgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+UENFUDwvc3Bhbj4gZm9yIGNvbW11bmljYXRpb24g
YmV0d2VlbiBhIFBhdGggQ29tcHV0YXRpb248L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9j
ayI+ICAgW1JGQzU0NDBdIGRlc2NyaWJlcyA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij5QYXRoIENvbXB1
dGF0aW9uIEVsZW1lbnQgQ29tbXVuaWNhdGlvbiBQcm90b2NvbDwvc3Bhbj48L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxibG9jayI+ICAgQ2xpZW50IChQQ0MpIGFuZCBhIFBDRSBvciBiZXR3ZWVuIGEg
cGFpciBvZiBQQ0VzIGFzIHBlciBbUkZDNDY1NV0uICBBPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyYmxvY2siPiAgIGZvciBjb21tdW5pY2F0aW9uIGJldHdlZW4gYSBQYXRoIENvbXB1dGF0aW9u
IENsaWVudCAoUENDKSBhbmQgYSBQQ0U8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAg
UENFIGNvbXB1dGVzIHBhdGhzIGZvciBNUExTLVRFIDxzcGFuIGNsYXNzPSJkZWxldGUiPkxTUHM8
L3NwYW4+IGJhc2VkIG9uIHZhcmlvdXMgY29uc3RyYWludHMgYW5kPC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyYmxvY2siPiAgIG9yIGJldHdlZW4gYSBwYWlyIG9mIFBDRXMgYXMgcGVyIFtSRkM0
NjU1XS4gIEEgUENFIGNvbXB1dGVzIHBhdGhzIGZvcjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJs
b2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgTVBMUy1URSA8c3BhbiBj
bGFzcz0iaW5zZXJ0Ij5MYWJlbCBTd2l0Y2hlZCBQYXRocyAoTFNQcyk8L3NwYW4+IGJhc2VkIG9u
IHZhcmlvdXMgY29uc3RyYWludHMgYW5kPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBv
cHRpbWl6YXRpb24gY3JpdGVyaWEuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAg
b3B0aW1pemF0aW9uIGNyaXRlcmlhLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4g
ICBTdGF0ZWZ1bCBQQ0UgW1JGQzgyMzFdIHNwZWNpZmllcyBhIHNldCBvZiBleHRlbnNpb25zIHRv
IFBDRVAgdG88L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBTdGF0ZWZ1bCBQQ0Ug
W1JGQzgyMzFdIHNwZWNpZmllcyBhIHNldCBvZiBleHRlbnNpb25zIHRvIFBDRVAgdG88L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlmZjAwMTEiPjx0ZD48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9Imxi
bG9jayI+ICAgZW5hYmxlIHN0YXRlZnVsIGNvbnRyb2wgb2YgcGF0aHMgc3VjaCBhcyBNUExTPHNw
YW4gY2xhc3M9ImRlbGV0ZSI+IDwvc3Bhbj5URSBMU1BzIGJldHdlZW4gYW5kPC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIGVuYWJsZSBzdGF0ZWZ1bCBjb250cm9sIG9mIHBhdGhz
IHN1Y2ggYXMgTVBMUzxzcGFuIGNsYXNzPSJpbnNlcnQiPi08L3NwYW4+VEUgTFNQcyBiZXR3ZWVu
IGFuZDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgYWNyb3NzIFBDRVAgc2Vzc2lvbnMg
aW4gY29tcGxpYW5jZSB3aXRoIFtSRkM0NjU3XS4gIEl0IGluY2x1ZGVzPC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyaWdodCI+ICAgYWNyb3NzIFBDRVAgc2Vzc2lvbnMgaW4gY29tcGxpYW5jZSB3
aXRoIFtSRkM0NjU3XS4gIEl0IGluY2x1ZGVzPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4g
ICBtZWNoYW5pc21zIHRvIGVmZmVjdCBMU1Agc3RhdGUgc3luY2hyb25pemF0aW9uIGJldHdlZW4g
UENDcyBhbmQgUENFcyw8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBtZWNoYW5p
c21zIHRvIGVmZmVjdCBMU1Agc3RhdGUgc3luY2hyb25pemF0aW9uIGJldHdlZW4gUENDcyBhbmQg
UENFcyw8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGRlbGVnYXRpb24gb2YgY29udHJv
bCBvZiBMU1BzIHRvIFBDRXMsIGFuZCBQQ0UgY29udHJvbCBvZiB0aW1pbmcgYW5kPC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgZGVsZWdhdGlvbiBvZiBjb250cm9sIG9mIExTUHMg
dG8gUENFcywgYW5kIFBDRSBjb250cm9sIG9mIHRpbWluZyBhbmQ8L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlmZjAwMTIiPjx0ZD48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgc2Vx
dWVuY2Ugb2YgcGF0aCBjb21wdXRhdGlvbnMgd2l0aGluIGFuZCBhY3Jvc3MgUENFUCA8c3BhbiBj
bGFzcz0iZGVsZXRlIj5zZXNzaW9ucyBhbmQ8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyYmxvY2siPiAgIHNlcXVlbmNlIG9mIHBhdGggY29tcHV0YXRpb25zIHdpdGhpbiBhbmQgYWNy
b3NzIFBDRVAgPHNwYW4gY2xhc3M9Imluc2VydCI+c2Vzc2lvbnMuICBUaGU8L3NwYW4+PC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjxzcGFuIGNsYXNzPSJkZWxldGUiPiAgIGZvY3VzZXM8
L3NwYW4+IG9uIGEgbW9kZWwgd2hlcmUgTFNQcyBhcmUgY29uZmlndXJlZCBvbiB0aGUgUENDIGFu
ZCBjb250cm9sPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJp
bnNlcnQiPiAgIGZvY3VzIGlzPC9zcGFuPiBvbiBhIG1vZGVsIHdoZXJlIExTUHMgYXJlIGNvbmZp
Z3VyZWQgb24gdGhlIFBDQyBhbmQgY29udHJvbDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2Nr
Ij4gICBvdmVyIHRoZW0gaXMgZGVsZWdhdGVkIHRvIHRoZSBQQ0UuICBGdXJ0aGVybW9yZSwgYSBt
ZWNoYW5pc20gdG88L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgb3ZlciB0aGVt
IGlzIGRlbGVnYXRlZCB0byB0aGUgPHNwYW4gY2xhc3M9Imluc2VydCI+U3RhdGVmdWw8L3NwYW4+
IFBDRS4gIEZ1cnRoZXJtb3JlLCA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij5bUkZDODI4MV08L3NwYW4+
PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIGR5bmFtaWNhbGx5IGluc3RhbnRpYXRl
IExTUHMgb24gYSBQQ0MgYmFzZWQgb24gdGhlIHJlcXVlc3RzIGZyb20gYTwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmJsb2NrIj48c3BhbiBjbGFzcz0iaW5zZXJ0Ij4gICBzcGVjaWZpZXM8L3Nw
YW4+IGEgbWVjaGFuaXNtIHRvIGR5bmFtaWNhbGx5IGluc3RhbnRpYXRlIExTUHMgb24gYSBQQ0Mg
YmFzZWQ8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgc3RhdGVmdWwgUENFIG9yIGEg
Y29udHJvbGxlciB1c2luZyBzdGF0ZWZ1bCA8c3BhbiBjbGFzcz0iZGVsZXRlIj5QQ0UsIGlzIHNw
ZWNpZmllZCBpbjwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgb24g
dGhlIHJlcXVlc3RzIGZyb20gYSBzdGF0ZWZ1bCBQQ0Ugb3IgYSBjb250cm9sbGVyIHVzaW5nIHN0
YXRlZnVsPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjxzcGFuIGNsYXNzPSJkZWxldGUi
PiAgIFtSRkM4MjgxXS48L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAg
IDxzcGFuIGNsYXNzPSJpbnNlcnQiPlBDRS48L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xh
c3M9ImxlZnQiPiAgIFBhdGggcHJvdGVjdGlvbiBbUkZDNDQyN10gcmVmZXJzIHRvIGEgcGFyYWRp
Z20gaW4gd2hpY2ggdGhlIHdvcmtpbmc8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4g
ICBQYXRoIHByb3RlY3Rpb24gW1JGQzQ0MjddIHJlZmVycyB0byBhIHBhcmFkaWdtIGluIHdoaWNo
IHRoZSB3b3JraW5nPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBMU1AgaXMgcHJvdGVj
dGVkIGJ5IG9uZSBvciBtb3JlIHByb3RlY3Rpb24gTFNQKHMpLiAgV2hlbiB0aGUgd29ya2luZzwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIExTUCBpcyBwcm90ZWN0ZWQgYnkgb25l
IG9yIG1vcmUgcHJvdGVjdGlvbiBMU1AocykuICBXaGVuIHRoZSB3b3JraW5nPC90ZD48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij4gICBMU1AgZmFpbHMsIHByb3RlY3Rpb24gTFNQKHMpIGlzL2FyZSBh
Y3RpdmF0ZWQuICBXaGVuIHRoZSB3b3JraW5nIExTUHM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJpZ2h0Ij4gICBMU1AgZmFpbHMsIHByb3RlY3Rpb24gTFNQKHMpIGlzL2FyZSBhY3RpdmF0ZWQu
ICBXaGVuIHRoZSB3b3JraW5nIExTUHM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGFy
ZSBjb21wdXRlZCBhbmQgY29udHJvbGxlZCBieSB0aGUgUENFLCB0aGVyZSBpcyBiZW5lZml0IGlu
IGEgbW9kZSBvZjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIGFyZSBjb21wdXRl
ZCBhbmQgY29udHJvbGxlZCBieSB0aGUgUENFLCB0aGVyZSBpcyBiZW5lZml0IGluIGEgbW9kZSBv
ZjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgb3BlcmF0aW9uIHdoZXJlIHByb3RlY3Rp
b24gTFNQcyBhcmUgYXMgd2VsbC4gIFtSRkM4MDUxXSBkZXNjcmliZXM8L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij4gICBvcGVyYXRpb24gd2hlcmUgcHJvdGVjdGlvbiBMU1BzIGFyZSBh
cyB3ZWxsLiAgW1JGQzgwNTFdIGRlc2NyaWJlczwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
ICAgYXBwbGljYWJpbGl0eSBvZiBwYXRoIHByb3RlY3Rpb24gaW4gUENFIGRlcGxveW1lbnRzLjwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIGFwcGxpY2FiaWxpdHkgb2YgcGF0aCBw
cm90ZWN0aW9uIGluIFBDRSBkZXBsb3ltZW50cy48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
PjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0i
bGVmdCI+ICAgVGhpcyBkb2N1bWVudCBzcGVjaWZpZXMgYSBzdGF0ZWZ1bCBQQ0VQIGV4dGVuc2lv
biB0byBhc3NvY2lhdGUgdHdvIG9yPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAg
VGhpcyBkb2N1bWVudCBzcGVjaWZpZXMgYSBzdGF0ZWZ1bCBQQ0VQIGV4dGVuc2lvbiB0byBhc3Nv
Y2lhdGUgdHdvIG9yPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBtb3JlIExTUHMgZm9y
IHRoZSBwdXJwb3NlIG9mIHNldHRpbmcgdXAgcGF0aCBwcm90ZWN0aW9uLiAgVGhlPC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgbW9yZSBMU1BzIGZvciB0aGUgcHVycG9zZSBvZiBz
ZXR0aW5nIHVwIHBhdGggcHJvdGVjdGlvbi4gIFRoZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVm
dCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9InBhcnQtMyIgY2xhc3M9ImNoYW5nZSI+PHRkPjwv
dGQ+PHRoPjxzbWFsbD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8L3NtYWxsPjxhIGhyZWY9IiNwYXJ0
LTMiPjxlbT4gcGFnZSAzLCBsaW5lIDQ1PHNwYW4gY2xhc3M9ImhpZGUiPiDCtjwvc3Bhbj48L2Vt
PjwvYT48L3RoPjx0aD4gPC90aD48dGg+PHNtYWxsPnNraXBwaW5nIHRvIGNoYW5nZSBhdDwvc21h
bGw+PGEgaHJlZj0iI3BhcnQtMyI+PGVtPiBwYWdlIDMsIGxpbmUgNDY8c3BhbiBjbGFzcz0iaGlk
ZSI+IMK2PC9zcGFuPjwvZW0+PC9hPjwvdGg+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgbyAgQSBQQ0MgaW5pdGlhdGVz
IGEgcHJvdGVjdGlvbiBMU1AgYW5kIHJldGFpbnMgdGhlIGNvbnRyb2wgb2YgdGhlPC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgbyAgQSBQQ0MgaW5pdGlhdGVzIGEgcHJvdGVjdGlv
biBMU1AgYW5kIHJldGFpbnMgdGhlIGNvbnRyb2wgb2YgdGhlPC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij4gICAgICBMU1AuICBUaGUgUENDIGNvbXB1dGVzIHRoZSBwYXRoIGl0c2VsZiBvciBt
YWtlcyBhIHJlcXVlc3QgZm9yIHBhdGg8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4g
ICAgICBMU1AuICBUaGUgUENDIGNvbXB1dGVzIHRoZSBwYXRoIGl0c2VsZiBvciBtYWtlcyBhIHJl
cXVlc3QgZm9yIHBhdGg8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0
cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgIGNvbXB1dGF0
aW9uIHRvIGEgUENFLiAgQWZ0ZXIgdGhlIHBhdGggc2V0dXAsIGl0IHJlcG9ydHMgdGhlPC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgY29tcHV0YXRpb24gdG8gYSBQQ0UuICBB
ZnRlciB0aGUgcGF0aCBzZXR1cCwgaXQgcmVwb3J0cyB0aGU8L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPiAgICAgIGluZm9ybWF0aW9uIGFuZCBzdGF0ZSBvZiB0aGUgcGF0aCB0byB0aGUgUENF
LiAgVGhpcyBpbmNsdWRlcyB0aGU8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAg
ICBpbmZvcm1hdGlvbiBhbmQgc3RhdGUgb2YgdGhlIHBhdGggdG8gdGhlIFBDRS4gIFRoaXMgaW5j
bHVkZXMgdGhlPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICBhc3NvY2lhdGlvbiBn
cm91cCBpZGVudGlmeWluZyB0aGUgd29ya2luZyBhbmQgcHJvdGVjdGlvbiBMU1BzLjwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgIGFzc29jaWF0aW9uIGdyb3VwIGlkZW50aWZ5
aW5nIHRoZSB3b3JraW5nIGFuZCBwcm90ZWN0aW9uIExTUHMuPC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij4gICAgICBUaGlzIGlzIHRoZSBwYXNzaXZlIHN0YXRlZnVsIG1vZGUgW1JGQzgwNTFd
LjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgIFRoaXMgaXMgdGhlIHBhc3Np
dmUgc3RhdGVmdWwgbW9kZSBbUkZDODA1MV0uPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPiAgIG8gIEEgUENDIGluaXRpYXRlcyBhIHByb3RlY3Rpb24gTFNQIGFuZCBkZWxlZ2F0ZXMg
dGhlIGNvbnRyb2wgb2YgdGhlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgbyAg
QSBQQ0MgaW5pdGlhdGVzIGEgcHJvdGVjdGlvbiBMU1AgYW5kIGRlbGVnYXRlcyB0aGUgY29udHJv
bCBvZiB0aGU8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgIExTUCB0byBhIHN0YXRl
ZnVsIFBDRS4gIER1cmluZyBkZWxlZ2F0aW9uIHRoZSBhc3NvY2lhdGlvbiBncm91cDwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgIExTUCB0byBhIHN0YXRlZnVsIFBDRS4gIER1
cmluZyBkZWxlZ2F0aW9uIHRoZSBhc3NvY2lhdGlvbiBncm91cDwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFz
cz0ibGVmdCI+ICAgICAgaWRlbnRpZnlpbmcgdGhlIHdvcmtpbmcgYW5kIHByb3RlY3Rpb24gTFNQ
cyBpcyBpbmNsdWRlZC4gIFRoZSBQQ0U8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4g
ICAgICBpZGVudGlmeWluZyB0aGUgd29ya2luZyBhbmQgcHJvdGVjdGlvbiBMU1BzIGlzIGluY2x1
ZGVkLiAgVGhlIFBDRTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
IGlkPSJkaWZmMDAxMyI+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICAgICBjb21wdXRlcyB0aGUgcGF0aCBmb3IgdGhl
IHByb3RlY3Rpb24gTFNQIGFuZCB1cGRhdGUgdGhlIFBDQyB3aXRoPC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyYmxvY2siPiAgICAgIGNvbXB1dGVzIHRoZSBwYXRoIGZvciB0aGUgcHJvdGVjdGlv
biBMU1AgYW5kIHVwZGF0ZTxzcGFuIGNsYXNzPSJpbnNlcnQiPnM8L3NwYW4+IHRoZSBQQ0Mgd2l0
aDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgdGhlIGluZm9ybWF0aW9uIGFib3V0
IHRoZSBwYXRoIGFzIGxvbmcgYXMgaXQgY29udHJvbHMgdGhlIExTUC48L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij4gICAgICB0aGUgaW5mb3JtYXRpb24gYWJvdXQgdGhlIHBhdGggYXMg
bG9uZyBhcyBpdCBjb250cm9scyB0aGUgTFNQLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
ICAgICAgVGhpcyBpcyB0aGUgYWN0aXZlIHN0YXRlZnVsIG1vZGUgW1JGQzgwNTFdLjwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgIFRoaXMgaXMgdGhlIGFjdGl2ZSBzdGF0ZWZ1
bCBtb2RlIFtSRkM4MDUxXS48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgbyAg
QSBwcm90ZWN0aW9uIExTUCBjb3VsZCBiZSBpbml0aWF0ZWQgYnkgYSBzdGF0ZWZ1bCBQQ0UsIHdo
aWNoPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgbyAgQSBwcm90ZWN0aW9uIExT
UCBjb3VsZCBiZSBpbml0aWF0ZWQgYnkgYSBzdGF0ZWZ1bCBQQ0UsIHdoaWNoPC90ZD48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICByZXRhaW5zIHRoZSBjb250cm9sIG9mIHRoZSBMU1AuICBU
aGUgUENFIGlzIHJlc3BvbnNpYmxlIGZvcjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PiAgICAgIHJldGFpbnMgdGhlIGNvbnRyb2wgb2YgdGhlIExTUC4gIFRoZSBQQ0UgaXMgcmVzcG9u
c2libGUgZm9yPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICBjb21wdXRpbmcgdGhl
IHBhdGggb2YgdGhlIExTUCBhbmQgdXBkYXRpbmcgdG8gdGhlIFBDQyB3aXRoIHRoZTwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgIGNvbXB1dGluZyB0aGUgcGF0aCBvZiB0aGUg
TFNQIGFuZCB1cGRhdGluZyB0byB0aGUgUENDIHdpdGggdGhlPC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij4gICAgICBpbmZvcm1hdGlvbiBhYm91dCB0aGUgcGF0aC4gIFRoaXMgaXMgdGhlIFBD
RS1Jbml0aWF0ZWQgbW9kZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgIGlu
Zm9ybWF0aW9uIGFib3V0IHRoZSBwYXRoLiAgVGhpcyBpcyB0aGUgUENFLUluaXRpYXRlZCBtb2Rl
PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICBbUkZDODI4MV0uPC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgW1JGQzgyODFdLjwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFz
cz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9ImRpZmYwMDE0Ij48dGQ+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAg
IE5vdGUgdGhhdCA8c3BhbiBjbGFzcz0iZGVsZXRlIj5wcm90ZWN0aW9uIExTUCBjYW4gYmUgZXN0
YWJsaXNoZWQgKHNpZ25hbGVkKSBwcmlvciB0bzwvc3Bhbj4gdGhlPC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyYmxvY2siPiAgIE5vdGUgdGhhdCA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij5hIHByb3Rl
Y3Rpb24gTFNQIGNhbiBiZSBlc3RhYmxpc2hlZCAoc2lnbmFsZWQpIGJlZm9yZTwvc3Bhbj4gdGhl
PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBmYWlsdXJlIChpbiB3aGljaCBjYXNlIHRo
ZSBMU1AgaXMgc2FpZCB0byBiZSBpbiBzdGFuZGJ5IG1vZGU8L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij4gICBmYWlsdXJlIChpbiB3aGljaCBjYXNlIHRoZSBMU1AgaXMgc2FpZCB0byBi
ZSBpbiBzdGFuZGJ5IG1vZGU8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0ciBpZD0iZGlmZjAwMTUiPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgW1JGQzQ0MjddIG9yIGEgUHJpbWFyeSBM
U1AgW1JGQzQ4NzJdKSBvciA8c3BhbiBjbGFzcz0iZGVsZXRlIj5wb3N0PC9zcGFuPiBmYWlsdXJl
IG9mIHRoZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICBbUkZDNDQyN10gb3Ig
YSBQcmltYXJ5IExTUCBbUkZDNDg3Ml0pIG9yIDxzcGFuIGNsYXNzPSJpbnNlcnQiPmFmdGVyPC9z
cGFuPiBmYWlsdXJlIG9mIHRoZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICBjb3Jy
ZXNwb25kaW5nIHdvcmtpbmcgTFNQIDxzcGFuIGNsYXNzPSJkZWxldGUiPmFjY29yZGluZyB0byB0
aGUgb3BlcmF0b3IgY2hvaWNlL3BvbGljeTwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJibG9jayI+ICAgY29ycmVzcG9uZGluZyB3b3JraW5nIExTUCAoa25vd24gYXMgPHNwYW4gY2xh
c3M9Imluc2VydCI+YTwvc3Bhbj4gc2Vjb25kYXJ5IExTUCBbUkZDNDg3Ml0pLjwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGJsb2NrIj4gICAoa25vd24gYXMgc2Vjb25kYXJ5IExTUCBbUkZDNDg3Ml0p
LjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICA8c3BhbiBjbGFzcz0iaW5zZXJ0
Ij5XaGV0aGVyIHRvIGVzdGFibGlzaCBpdCBiZWZvcmUgb3IgYWZ0ZXIgZmFpbHVyZSBpcyBhY2Nv
cmRpbmcgdG88L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48c3BhbiBjbGFzcz0iaW5zZXJ0Ij4gICBvcGVyYXRvciBj
aG9pY2Ugb3IgcG9saWN5Ljwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
ICAgW0ktRC5pZXRmLXBjZS1hc3NvY2lhdGlvbi1ncm91cF0gaW50cm9kdWNlcyBhIGdlbmVyaWMg
bWVjaGFuaXNtIHRvPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgW0ktRC5pZXRm
LXBjZS1hc3NvY2lhdGlvbi1ncm91cF0gaW50cm9kdWNlcyBhIGdlbmVyaWMgbWVjaGFuaXNtIHRv
PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9ImRpZmYwMDE2
Ij48dGQ+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsYmxvY2siPiAgIGNyZWF0ZSBhIGdyb3VwaW5nIG9mIDxzcGFuIGNsYXNzPSJkZWxldGUi
PkxTUHM8L3NwYW4+IHdoaWNoIGNhbiB0aGVuIGJlIHVzZWQgdG8gZGVmaW5lPC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIGNyZWF0ZSBhIGdyb3VwaW5nIG9mIDxzcGFuIGNsYXNz
PSJpbnNlcnQiPkxTUHMsPC9zcGFuPiB3aGljaCBjYW4gdGhlbiBiZSB1c2VkIHRvIGRlZmluZTwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICBhc3NvY2lhdGlvbnMgYmV0d2VlbiBhIHNl
dCBvZiA8c3BhbiBjbGFzcz0iZGVsZXRlIj5MU1BzIHRoYXQ8L3NwYW4+IGlzIGVxdWFsbHkgYXBw
bGljYWJsZSB0bzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICBhc3NvY2lhdGlv
bnMgYmV0d2VlbiBhIHNldCBvZiA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij5MU1BzLiAgVGhlIG1lY2hh
bmlzbTwvc3Bhbj4gaXMgZXF1YWxseTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICBz
dGF0ZWZ1bCBQQ0UgKGFjdGl2ZSBhbmQgcGFzc2l2ZSBtb2RlcykgYW5kIHN0YXRlbGVzcyBQQ0Uu
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIGFwcGxpY2FibGUgdG8gc3RhdGVm
dWwgUENFIChhY3RpdmUgYW5kIHBhc3NpdmUgbW9kZXMpIGFuZCBzdGF0ZWxlc3M8L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAg
IFBDRS48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgVGhpcyBkb2N1bWVudCBz
cGVjaWZpZXMgYSBQQ0VQIGV4dGVuc2lvbiB0byBhc3NvY2lhdGUgb25lIHdvcmtpbmcgTFNQPC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgVGhpcyBkb2N1bWVudCBzcGVjaWZpZXMg
YSBQQ0VQIGV4dGVuc2lvbiB0byBhc3NvY2lhdGUgb25lIHdvcmtpbmcgTFNQPC90ZD48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij4gICB3aXRoIG9uZSBvciBtb3JlIHByb3RlY3Rpb24gTFNQcyB1c2lu
ZyB0aGUgZ2VuZXJpYyBhc3NvY2lhdGlvbjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PiAgIHdpdGggb25lIG9yIG1vcmUgcHJvdGVjdGlvbiBMU1BzIHVzaW5nIHRoZSBnZW5lcmljIGFz
c29jaWF0aW9uPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBtZWNoYW5pc20uPC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgbWVjaGFuaXNtLjwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij4gICBUaGlzIGRvY3VtZW50IGRlc2NyaWJlcyBhIFBDRVAgZXh0ZW5z
aW9uIHRvIGFzc29jaWF0ZSBwcm90ZWN0aW9uIExTUHM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJpZ2h0Ij4gICBUaGlzIGRvY3VtZW50IGRlc2NyaWJlcyBhIFBDRVAgZXh0ZW5zaW9uIHRvIGFz
c29jaWF0ZSBwcm90ZWN0aW9uIExTUHM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGJ5
IGNyZWF0aW5nIFBhdGggUHJvdGVjdGlvbiBBc3NvY2lhdGlvbiBHcm91cCAoUFBBRykgYW5kIGVu
Y29kaW5nPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgYnkgY3JlYXRpbmcgUGF0
aCBQcm90ZWN0aW9uIEFzc29jaWF0aW9uIEdyb3VwIChQUEFHKSBhbmQgZW5jb2Rpbmc8L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIHRoaXMgYXNzb2NpYXRpb24gaW4gUENFUCBtZXNzYWdl
cyBmb3Igc3RhdGVmdWwgUENFUCBzZXNzaW9ucy48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij4gICB0aGlzIGFzc29jaWF0aW9uIGluIFBDRVAgbWVzc2FnZXMgZm9yIHN0YXRlZnVsIFBD
RVAgc2Vzc2lvbnMuPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjEuMS4gIFJlcXVp
cmVtZW50cyBMYW5ndWFnZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjEuMS4gIFJl
cXVpcmVtZW50cyBMYW5ndWFnZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHIgaWQ9InBhcnQtNCIgY2xhc3M9ImNoYW5nZSI+PHRkPjwvdGQ+PHRoPjxzbWFs
bD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8L3NtYWxsPjxhIGhyZWY9IiNwYXJ0LTQiPjxlbT4gcGFn
ZSA2LCBsaW5lIDMxPHNwYW4gY2xhc3M9ImhpZGUiPiDCtjwvc3Bhbj48L2VtPjwvYT48L3RoPjx0
aD4gPC90aD48dGg+PHNtYWxsPnNraXBwaW5nIHRvIGNoYW5nZSBhdDwvc21hbGw+PGEgaHJlZj0i
I3BhcnQtNCI+PGVtPiBwYWdlIDYsIGxpbmUgMzM8c3BhbiBjbGFzcz0iaGlkZSI+IMK2PC9zcGFu
PjwvZW0+PC9hPjwvdGg+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICArLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKzwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPiAgICAgKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSs8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAg
ICAgfCAgIFBUICAgICAgfCAgICAgICAgICAgICAgIFVuYXNzaWduZWQgRmxhZ3MgICAgICAgICAg
ICAgICAgfFN8UHw8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgIHwgICBQVCAg
ICAgIHwgICAgICAgICAgICAgICBVbmFzc2lnbmVkIEZsYWdzICAgICAgICAgICAgICAgIHxTfFB8
PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rPC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyaWdodCI+ICAgICArLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVm
dCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij4gICAgICAgICAgICAgRmlndXJlIDE6IFBhdGggUHJvdGVjdGlvbiBBc3NvY2lhdGlv
biBUTFYgZm9ybWF0PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAg
IEZpZ3VyZSAxOiBQYXRoIFByb3RlY3Rpb24gQXNzb2NpYXRpb24gVExWIGZvcm1hdDwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90
ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBQYXRoIFByb3RlY3Rpb24gQXNzb2NpYXRpb24g
RmxhZ3MgKDMyIGJpdHMpIC0gVGhlIGZvbGxvd2luZyBmbGFncyBhcmU8L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij4gICBQYXRoIFByb3RlY3Rpb24gQXNzb2NpYXRpb24gRmxhZ3MgKDMy
IGJpdHMpIC0gVGhlIGZvbGxvd2luZyBmbGFncyBhcmU8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPiAgIGN1cnJlbnRseSBkZWZpbmVkIC08L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij4gICBjdXJyZW50bHkgZGVmaW5lZCAtPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
PjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PiAgICAgIFByb3RlY3RpbmcgKFApOiAxIGJpdCAtIFRoaXMgYml0IGlzIGFzIGRlZmluZWQgaW4g
U2VjdGlvbiAxNC4xIG9mPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgUHJv
dGVjdGluZyAoUCk6IDEgYml0IC0gVGhpcyBiaXQgaXMgYXMgZGVmaW5lZCBpbiBTZWN0aW9uIDE0
LjEgb2Y8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlm
ZjAwMTciPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxibG9jayI+ICAgICAgW1JGQzQ4NzJdIHRvIGluZGljYXRlIGlmIHRoZSBMU1Ag
aXMgd29ya2luZyBvciBwcm90ZWN0aW9uIExTUC48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJi
bG9jayI+ICAgICAgW1JGQzQ4NzJdIHRvIGluZGljYXRlIGlmIHRoZSBMU1AgaXMgPHNwYW4gY2xh
c3M9Imluc2VydCI+YTwvc3Bhbj4gd29ya2luZyA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij4oMCk8L3Nw
YW4+IG9yIHByb3RlY3Rpb248L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgICAgIDxzcGFuIGNsYXNzPSJpbnNlcnQiPigxKTwv
c3Bhbj4gTFNQLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICBTZWNvbmRh
cnkgKFMpOiAxIGJpdCAtIFRoaXMgYml0IGlzIGFzIGRlZmluZWQgaW4gU2VjdGlvbiAxNC4xIG9m
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgU2Vjb25kYXJ5IChTKTogMSBi
aXQgLSBUaGlzIGJpdCBpcyBhcyBkZWZpbmVkIGluIFNlY3Rpb24gMTQuMSBvZjwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGlkPSJkaWZmMDAxOCI+PHRkPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2Nr
Ij4gICAgICBbUkZDNDg3Ml0gdG8gaW5kaWNhdGUgaWYgdGhlIExTUCBpcyBwcmltYXJ5IG9yIHNl
Y29uZGFyeSBMU1AuICBUaGU8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgICAg
W1JGQzQ4NzJdIHRvIGluZGljYXRlIGlmIHRoZSBMU1AgaXMgPHNwYW4gY2xhc3M9Imluc2VydCI+
YTwvc3Bhbj4gcHJpbWFyeSA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij4oMCk8L3NwYW4+IG9yIHNlY29u
ZGFyeSA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij4oMSk8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsYmxvY2siPiAgICAgIFMgZmxhZyBpcyBpZ25vcmVkIGlmIHRoZSBQIGZsYWcgaXMgbm90IHNl
dC48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgICAgTFNQLiAgVGhlIFMgZmxh
ZyBpcyBpZ25vcmVkIGlmIHRoZSBQIGZsYWcgaXMgbm90IHNldC48L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xh
c3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+ICAgICAgUHJvdGVjdGlvbiBUeXBlIChQVCk6IDYgYml0cyAtIFRoaXMg
ZmllbGQgaXMgYXMgZGVmaW5lZCBpbjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAg
ICAgIFByb3RlY3Rpb24gVHlwZSAoUFQpOiA2IGJpdHMgLSBUaGlzIGZpZWxkIGlzIGFzIGRlZmlu
ZWQgaW48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgIFNlY3Rpb24gMTQuMSBvZiBb
UkZDNDg3Ml0gdG8gaW5kaWNhdGUgdGhlIExTUCBwcm90ZWN0aW9uIHR5cGUgaW48L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICBTZWN0aW9uIDE0LjEgb2YgW1JGQzQ4NzJdIHRv
IGluZGljYXRlIHRoZSBMU1AgcHJvdGVjdGlvbiB0eXBlIGluPC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij4gICAgICB1c2UuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAg
dXNlLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICBVbmFzc2lnbmVkIGJp
dHMgYXJlIGNvbnNpZGVyZWQgcmVzZXJ2ZWQuICBUaGV5IE1VU1QgYmUgc2V0IHRvIDAgb248L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICBVbmFzc2lnbmVkIGJpdHMgYXJlIGNv
bnNpZGVyZWQgcmVzZXJ2ZWQuICBUaGV5IE1VU1QgYmUgc2V0IHRvIDAgb248L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxlZnQiPiAgICAgIHRyYW5zbWlzc2lvbiBhbmQgTVVTVCBiZSBpZ25vcmVkIG9u
IHJlY2VpcHQuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgdHJhbnNtaXNz
aW9uIGFuZCBNVVNUIGJlIGlnbm9yZWQgb24gcmVjZWlwdC48L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGlkPSJkaWZmMDAxOSI+PHRkPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICBJ
ZiB0aGUgVExWIGlzIG1pc3NpbmcsIGl0IGlzIGNvbnNpZGVyZWQgdGhhdCB0aGUgTFNQIGlzIDxz
cGFuIGNsYXNzPSJkZWxldGUiPnRoZTwvc3Bhbj4gd29ya2luZzwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmJsb2NrIj4gICBJZiB0aGUgVExWIGlzIG1pc3NpbmcsIGl0IGlzIGNvbnNpZGVyZWQg
dGhhdCB0aGUgTFNQIGlzIDxzcGFuIGNsYXNzPSJpbnNlcnQiPmE8L3NwYW4+IHdvcmtpbmcgTFNQ
PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIExTUCAoaS5lLiBhcyBpZiBQIGJpdCBp
cyB1bnNldCkuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIChpLmUuIGFzIGlm
IDxzcGFuIGNsYXNzPSJpbnNlcnQiPnRoZTwvc3Bhbj4gUCBiaXQgaXMgdW5zZXQpLjwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90
ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij40LiAgT3BlcmF0aW9uPC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+NC4gIE9wZXJhdGlvbjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHIgaWQ9ImRpZmYwMDIwIj48dGQ+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIEFuIExTUCBp
cyBhc3NvY2lhdGVkIHdpdGggb3RoZXIgTFNQcyB3aXRoIHdoaWNoIDxzcGFuIGNsYXNzPSJkZWxl
dGUiPnRoZXkgaW50ZXJhY3Q8L3NwYW4+IGJ5PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxv
Y2siPiAgIEFuIExTUCBpcyBhc3NvY2lhdGVkIHdpdGggb3RoZXIgTFNQcyB3aXRoIHdoaWNoIDxz
cGFuIGNsYXNzPSJpbnNlcnQiPml0IGludGVyYWN0czwvc3Bhbj4gYnk8L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQg
Y2xhc3M9ImxlZnQiPiAgIGFkZGluZyB0aGVtIHRvIGEgY29tbW9uIGFzc29jaWF0aW9uIGdyb3Vw
IHZpYSB0aGUgQVNTT0NJQVRJT04gb2JqZWN0LjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPiAgIGFkZGluZyB0aGVtIHRvIGEgY29tbW9uIGFzc29jaWF0aW9uIGdyb3VwIHZpYSB0aGUg
QVNTT0NJQVRJT04gb2JqZWN0LjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAg
ICAgPHRyIGlkPSJkaWZmMDAyMSI+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48c3BhbiBjbGFzcz0iZGVsZXRlIj4gICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgPC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIEFsbCBwcm9jZWR1cmVzIGFuZCBlcnJvci1oYW5k
bGluZyBmb3IgdGhlIEFTU09DSUFUSU9OIG9iamVjdCBpcyBhczwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPiAgIEFsbCBwcm9jZWR1cmVzIGFuZCBlcnJvci1oYW5kbGluZyBmb3IgdGhl
IEFTU09DSUFUSU9OIG9iamVjdCBpcyBhczwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAg
cGVyIFtJLUQuaWV0Zi1wY2UtYXNzb2NpYXRpb24tZ3JvdXBdLjwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPiAgIHBlciBbSS1ELmlldGYtcGNlLWFzc29jaWF0aW9uLWdyb3VwXS48L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+NC4xLiAgU3RhdGUgU3luY2hyb25pemF0aW9u
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+NC4xLiAgU3RhdGUgU3luY2hyb25pemF0
aW9uPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIER1cmluZyBzdGF0ZSBzeW5j
aHJvbml6YXRpb24sIGEgUENDIHJlcG9ydHMgYWxsIHRoZSBleGlzdGluZyBMU1A8L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBEdXJpbmcgc3RhdGUgc3luY2hyb25pemF0aW9uLCBh
IFBDQyByZXBvcnRzIGFsbCB0aGUgZXhpc3RpbmcgTFNQPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij4gICBzdGF0ZXMgYXMgZGVzY3JpYmVkIGluIFtSRkM4MjMxXS4gIFRoZSBhc3NvY2lhdGlv
biBncm91cCBtZW1iZXJzaGlwPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgc3Rh
dGVzIGFzIGRlc2NyaWJlZCBpbiBbUkZDODIzMV0uICBUaGUgYXNzb2NpYXRpb24gZ3JvdXAgbWVt
YmVyc2hpcDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgcGVydGFpbmluZyB0byBhbiBM
U1AgaXMgYWxzbyByZXBvcnRlZCBhcyBwZXI8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij4gICBwZXJ0YWluaW5nIHRvIGFuIExTUCBpcyBhbHNvIHJlcG9ydGVkIGFzIHBlcjwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgW0ktRC5pZXRmLXBjZS1hc3NvY2lhdGlvbi1ncm91cF0u
ICBUaGlzIGluY2x1ZGVzIFBQQUdzLjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAg
IFtJLUQuaWV0Zi1wY2UtYXNzb2NpYXRpb24tZ3JvdXBdLiAgVGhpcyBpbmNsdWRlcyBQUEFHcy48
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9
InBhcnQtNSIgY2xhc3M9ImNoYW5nZSI+PHRkPjwvdGQ+PHRoPjxzbWFsbD5za2lwcGluZyB0byBj
aGFuZ2UgYXQ8L3NtYWxsPjxhIGhyZWY9IiNwYXJ0LTUiPjxlbT4gcGFnZSA3LCBsaW5lIDE4PHNw
YW4gY2xhc3M9ImhpZGUiPiDCtjwvc3Bhbj48L2VtPjwvYT48L3RoPjx0aD4gPC90aD48dGg+PHNt
YWxsPnNraXBwaW5nIHRvIGNoYW5nZSBhdDwvc21hbGw+PGEgaHJlZj0iI3BhcnQtNSI+PGVtPiBw
YWdlIDcsIGxpbmUgMjI8c3BhbiBjbGFzcz0iaGlkZSI+IMK2PC9zcGFuPjwvZW0+PC9hPjwvdGg+
PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFz
cz0ibGVmdCI+NC4xLiAgU3RhdGUgU3luY2hyb25pemF0aW9uPC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyaWdodCI+NC4xLiAgU3RhdGUgU3luY2hyb25pemF0aW9uPC90ZD48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxlZnQiPiAgIER1cmluZyBzdGF0ZSBzeW5jaHJvbml6YXRpb24sIGEgUENDIHJl
cG9ydHMgYWxsIHRoZSBleGlzdGluZyBMU1A8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij4gICBEdXJpbmcgc3RhdGUgc3luY2hyb25pemF0aW9uLCBhIFBDQyByZXBvcnRzIGFsbCB0aGUg
ZXhpc3RpbmcgTFNQPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBzdGF0ZXMgYXMgZGVz
Y3JpYmVkIGluIFtSRkM4MjMxXS4gIFRoZSBhc3NvY2lhdGlvbiBncm91cCBtZW1iZXJzaGlwPC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgc3RhdGVzIGFzIGRlc2NyaWJlZCBpbiBb
UkZDODIzMV0uICBUaGUgYXNzb2NpYXRpb24gZ3JvdXAgbWVtYmVyc2hpcDwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+ICAgcGVydGFpbmluZyB0byBhbiBMU1AgaXMgYWxzbyByZXBvcnRlZCBh
cyBwZXI8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBwZXJ0YWluaW5nIHRvIGFu
IExTUCBpcyBhbHNvIHJlcG9ydGVkIGFzIHBlcjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
ICAgW0ktRC5pZXRmLXBjZS1hc3NvY2lhdGlvbi1ncm91cF0uICBUaGlzIGluY2x1ZGVzIFBQQUdz
LjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFtJLUQuaWV0Zi1wY2UtYXNzb2Np
YXRpb24tZ3JvdXBdLiAgVGhpcyBpbmNsdWRlcyBQUEFHcy48L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGVmdCI+NC4yLiAgUENDLUluaXRpYXRlZCBMU1BzPC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyaWdodCI+NC4yLiAgUENDLUluaXRpYXRlZCBMU1BzPC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQg
Y2xhc3M9ImxlZnQiPiAgIEEgUENDIGNhbiBhc3NvY2lhdGUgYSBzZXQgb2YgTFNQcyB1bmRlciBp
dHMgY29udHJvbCBmb3IgcGF0aDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIEEg
UENDIGNhbiBhc3NvY2lhdGUgYSBzZXQgb2YgTFNQcyB1bmRlciBpdHMgY29udHJvbCBmb3IgcGF0
aDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGlkPSJkaWZmMDAy
MiI+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGJsb2NrIj4gICBwcm90ZWN0aW9uIHB1cnBvc2UuICBTaW1pbGFybHksIHRoZSBQQ0Mg
Y2FuIHJlbW92ZSBvbmUgb3IgbW9yZSBMU1BzPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxv
Y2siPiAgIHByb3RlY3Rpb24gcHVycG9zZTxzcGFuIGNsYXNzPSJpbnNlcnQiPnM8L3NwYW4+LiAg
U2ltaWxhcmx5LCB0aGUgUENDIGNhbiByZW1vdmUgb25lIG9yIG1vcmUgTFNQczwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+ICAgdW5kZXIgaXRzIGNvbnRyb2wgZnJvbSB0aGUgY29ycmVzcG9u
ZGluZyBQUEFHLiAgSW4gYm90aCBjYXNlcywgdGhlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+ICAgdW5kZXIgaXRzIGNvbnRyb2wgZnJvbSB0aGUgY29ycmVzcG9uZGluZyBQUEFHLiAg
SW4gYm90aCBjYXNlcywgdGhlPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAg
ICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBQQ0MgcmVw
b3J0cyB0aGUgY2hhbmdlIGluIGFzc29jaWF0aW9uIHRvIFBDRShzKSB2aWEgUGF0aCBDb21wdXRh
dGlvbjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFBDQyByZXBvcnRzIHRoZSBj
aGFuZ2UgaW4gYXNzb2NpYXRpb24gdG8gUENFKHMpIHZpYSBQYXRoIENvbXB1dGF0aW9uPC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9ImRpZmYwMDIzIj48dGQ+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJs
YmxvY2siPiAgIFJlcG9ydCAoUENScHQpIG1lc3NhZ2UuICBBIFBDQyBjYW4gYWxzbyBkZWxlZ2F0
ZSB0aGUgd29ya2luZyBhbmQ8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgUmVw
b3J0IChQQ1JwdCkgbWVzc2FnZTxzcGFuIGNsYXNzPSJpbnNlcnQiPnM8L3NwYW4+LiAgQSBQQ0Mg
Y2FuIGFsc28gZGVsZWdhdGUgdGhlIHdvcmtpbmcgYW5kPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij4gICBwcm90ZWN0aW9uIExTUHMgdG8gYW4gYWN0aXZlIHN0YXRlZnVsIFBDRSwgd2hlcmUg
dGhlIFBDRSB3b3VsZDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIHByb3RlY3Rp
b24gTFNQcyB0byBhbiBhY3RpdmUgc3RhdGVmdWwgUENFLCB3aGVyZSB0aGUgUENFIHdvdWxkPC90
ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBjb250cm9sIHRoZSBMU1BzLiAgVGhlIHN0YXRl
ZnVsIFBDRSBjb3VsZCB1cGRhdGUgdGhlIHBhdGhzIGFuZDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPiAgIGNvbnRyb2wgdGhlIExTUHMuICBUaGUgc3RhdGVmdWwgUENFIGNvdWxkIHVw
ZGF0ZSB0aGUgcGF0aHMgYW5kPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAg
ICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBhdHRyaWJ1
dGVzIG9mIHRoZSBMU1BzIGluIHRoZSBhc3NvY2lhdGlvbiBncm91cCB2aWEgUGF0aCBDb21wdXRh
dGlvbjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIGF0dHJpYnV0ZXMgb2YgdGhl
IExTUHMgaW4gdGhlIGFzc29jaWF0aW9uIGdyb3VwIHZpYSBQYXRoIENvbXB1dGF0aW9uPC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBVcGRhdGUgKFBDVXBkKSBtZXNzYWdlLiAgQSBQQ0Ug
Y291bGQgYWxzbyB1cGRhdGUgdGhlIGFzc29jaWF0aW9uIHRvPC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyaWdodCI+ICAgVXBkYXRlIChQQ1VwZCkgbWVzc2FnZS4gIEEgUENFIGNvdWxkIGFsc28g
dXBkYXRlIHRoZSBhc3NvY2lhdGlvbiB0bzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAg
dGhlIFBDQyB2aWEgUENVcGQgbWVzc2FnZS4gIFRoZXNlIHByb2NlZHVyZXMgYXJlIGRlc2NyaWJl
ZCBpbjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIHRoZSBQQ0MgdmlhIFBDVXBk
IG1lc3NhZ2UuICBUaGVzZSBwcm9jZWR1cmVzIGFyZSBkZXNjcmliZWQgaW48L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxlZnQiPiAgIFtJLUQuaWV0Zi1wY2UtYXNzb2NpYXRpb24tZ3JvdXBdLjwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFtJLUQuaWV0Zi1wY2UtYXNzb2NpYXRpb24t
Z3JvdXBdLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHIg
aWQ9ImRpZmYwMDI0Ij48dGQ+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIEl0IGlzIGV4cGVjdGVkIHRoYXQgYm90aCB3b3Jr
aW5nIGFuZCBwcm90ZWN0aW9uIExTUCBhcmUgZGVsZWdhdGVkPC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyYmxvY2siPiAgIEl0IGlzIGV4cGVjdGVkIHRoYXQgYm90aCB3b3JraW5nIGFuZCBwcm90
ZWN0aW9uIExTUDxzcGFuIGNsYXNzPSJpbnNlcnQiPnM8L3NwYW4+IGFyZSBkZWxlZ2F0ZWQ8L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIHRvZ2V0aGVyIChhbmQgdG8gdGhlIHNhbWUgUENF
KSB0byBhdm9pZCBhbnkgcmFjZSBjb25kaXRpb25zLiAgUmVmZXI8L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJpZ2h0Ij4gICB0b2dldGhlciAoYW5kIHRvIHRoZSBzYW1lIFBDRSkgdG8gYXZvaWQg
YW55IHJhY2UgY29uZGl0aW9ucy4gIFJlZmVyPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4g
ICB0byBbSS1ELmxpdGtvd3NraS1wY2Utc3RhdGUtc3luY10gZm9yIHRoZSBwcm9ibGVtIGRlc2Ny
aXB0aW9uLjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIHRvIFtJLUQubGl0a293
c2tpLXBjZS1zdGF0ZS1zeW5jXSBmb3IgdGhlIHByb2JsZW0gZGVzY3JpcHRpb24uPC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjQuMy4gIFBDRS1Jbml0aWF0ZWQgTFNQczwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjQuMy4gIFBDRS1Jbml0aWF0ZWQgTFNQczwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90
ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBBIFBDRSBjYW4gY3JlYXRlL3VwZGF0ZSB3b3Jr
aW5nIGFuZCBwcm90ZWN0aW9uIExTUHMgaW5kZXBlbmRlbnRseS48L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJpZ2h0Ij4gICBBIFBDRSBjYW4gY3JlYXRlL3VwZGF0ZSB3b3JraW5nIGFuZCBwcm90
ZWN0aW9uIExTUHMgaW5kZXBlbmRlbnRseS48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAg
IEFzIHNwZWNpZmllZCBpbiBbSS1ELmlldGYtcGNlLWFzc29jaWF0aW9uLWdyb3VwXSwgQXNzb2Np
YXRpb24gR3JvdXBzPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgQXMgc3BlY2lm
aWVkIGluIFtJLUQuaWV0Zi1wY2UtYXNzb2NpYXRpb24tZ3JvdXBdLCBBc3NvY2lhdGlvbiBHcm91
cHM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGNhbiBiZSBjcmVhdGVkIGJ5IGJvdGgg
dGhlIFBDRSBhbmQgdGhlIFBDQy4gIEZ1cnRoZXIsIGEgUENFIGNhbjwvdGQ+PHRkPiA8L3RkPjx0
ZCBjbGFzcz0icmlnaHQiPiAgIGNhbiBiZSBjcmVhdGVkIGJ5IGJvdGggdGhlIFBDRSBhbmQgdGhl
IFBDQy4gIEZ1cnRoZXIsIGEgUENFIGNhbjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAg
cmVtb3ZlIGEgcHJvdGVjdGlvbiBMU1AgZnJvbSBhIFBQQUcgYXMgc3BlY2lmaWVkIGluPC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgcmVtb3ZlIGEgcHJvdGVjdGlvbiBMU1AgZnJv
bSBhIFBQQUcgYXMgc3BlY2lmaWVkIGluPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBb
SS1ELmlldGYtcGNlLWFzc29jaWF0aW9uLWdyb3VwXS4gIFRoZSBQQ0UgdXNlcyBQQ1VwZCBvciBQ
YXRoPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgW0ktRC5pZXRmLXBjZS1hc3Nv
Y2lhdGlvbi1ncm91cF0uICBUaGUgUENFIHVzZXMgUENVcGQgb3IgUGF0aDwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9InBhcnQtNiIgY2xhc3M9ImNo
YW5nZSI+PHRkPjwvdGQ+PHRoPjxzbWFsbD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8L3NtYWxsPjxh
IGhyZWY9IiNwYXJ0LTYiPjxlbT4gcGFnZSA4LCBsaW5lIDM5PHNwYW4gY2xhc3M9ImhpZGUiPiDC
tjwvc3Bhbj48L2VtPjwvYT48L3RoPjx0aD4gPC90aD48dGg+PHNtYWxsPnNraXBwaW5nIHRvIGNo
YW5nZSBhdDwvc21hbGw+PGEgaHJlZj0iI3BhcnQtNiI+PGVtPiBwYWdlIDgsIGxpbmUgNDI8c3Bh
biBjbGFzcz0iaGlkZSI+IMK2PC9zcGFuPjwvZW0+PC9hPjwvdGg+PHRkPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgdGhlIFBD
RVAgcGVlciBNVVNUIHNlbmQgUENFcnIgd2l0aCBFcnJvci1UeXBlIDI2IChBc3NvY2lhdGlvbiBF
cnJvcik8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICB0aGUgUENFUCBwZWVyIE1V
U1Qgc2VuZCBQQ0VyciB3aXRoIEVycm9yLVR5cGUgMjYgKEFzc29jaWF0aW9uIEVycm9yKTwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgW0ktRC5pZXRmLXBjZS1hc3NvY2lhdGlvbi1ncm91
cF0gYW5kIEVycm9yLVZhbHVlIFRCRDUgKFByb3RlY3Rpb248L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij4gICBbSS1ELmlldGYtcGNlLWFzc29jaWF0aW9uLWdyb3VwXSBhbmQgRXJyb3It
VmFsdWUgVEJENSAoUHJvdGVjdGlvbjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgdHlw
ZSBpcyBub3Qgc3VwcG9ydGVkKS48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICB0
eXBlIGlzIG5vdCBzdXBwb3J0ZWQpLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4g
ICBBIGdpdmVuIExTUCBNQVkgYmVsb25nIHRvIG1vcmUgdGhhbiBvbmUgUFBBRy4gIElmIHRoZXJl
IGlzIGEgY29uZmxpY3Q8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBBIGdpdmVu
IExTUCBNQVkgYmVsb25nIHRvIG1vcmUgdGhhbiBvbmUgUFBBRy4gIElmIHRoZXJlIGlzIGEgY29u
ZmxpY3Q8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGJldHdlZW4gYW55IG9mIHRoZSB0
d28gUFBBR3MsIHRoZSBQQ0VQIHBlZXIgTVVTVCBzZW5kIFBDRXJyIHdpdGg8L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBiZXR3ZWVuIGFueSBvZiB0aGUgdHdvIFBQQUdzLCB0aGUg
UENFUCBwZWVyIE1VU1Qgc2VuZCBQQ0VyciB3aXRoPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij4gICBFcnJvci1UeXBlIDI2IChBc3NvY2lhdGlvbiBFcnJvcikgW0ktRC5pZXRmLXBjZS1hc3Nv
Y2lhdGlvbi1ncm91cF08L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBFcnJvci1U
eXBlIDI2IChBc3NvY2lhdGlvbiBFcnJvcikgW0ktRC5pZXRmLXBjZS1hc3NvY2lhdGlvbi1ncm91
cF08L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGFuZCBFcnJvci1WYWx1ZSA2IChBc3Nv
Y2lhdGlvbiBpbmZvcm1hdGlvbiBtaXNtYXRjaCkgYXMgcGVyPC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyaWdodCI+ICAgYW5kIEVycm9yLVZhbHVlIDYgKEFzc29jaWF0aW9uIGluZm9ybWF0aW9u
IG1pc21hdGNoKSBhcyBwZXI8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFtJLUQuaWV0
Zi1wY2UtYXNzb2NpYXRpb24tZ3JvdXBdLjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PiAgIFtJLUQuaWV0Zi1wY2UtYXNzb2NpYXRpb24tZ3JvdXBdLjwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFz
cz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9ImRpZmYwMDI1Ij48dGQ+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAg
IFdoZW4gdGhlIHByb3RlY3Rpb24gdHlwZSBpcyBzZXQgdG8gMSsxIG9yIDxzcGFuIGNsYXNzPSJk
ZWxldGUiPjE6Tjwvc3Bhbj4gd2l0aCA8c3BhbiBjbGFzcz0iZGVsZXRlIj5OPTEsPC9zcGFuPiB0
aGVyZSBNVVNUIGJlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIFdoZW4gdGhl
IHByb3RlY3Rpb24gdHlwZSBpcyBzZXQgdG8gMSsxIG9yIDxzcGFuIGNsYXNzPSJpbnNlcnQiPjE6
MSAoMTpOPC9zcGFuPiB3aXRoIDxzcGFuIGNsYXNzPSJpbnNlcnQiPk49MSksPC9zcGFuPiB0aGVy
ZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICBvbmx5IG9uZSB3b3JraW5nIExTUCBh
bmQgb25lIHByb3RlY3Rpb24gTFNQIHdpdGhpbiBhIFBQQUcuICBJZiBhIFBDRVA8L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgTVVTVCBiZSBvbmx5IG9uZSB3b3JraW5nIExTUCBh
bmQgb25lIHByb3RlY3Rpb24gTFNQIHdpdGhpbiBhIFBQQUcuPC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsYmxvY2siPiAgIHNwZWFrZXIgYXR0ZW1wdHMgdG8gYWRkIGFub3RoZXIgd29ya2luZy9wcm90
ZWN0aW9uIExTUCwgdGhlIFBDRVAgcGVlcjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2Nr
Ij4gICBJZiBhIFBDRVAgc3BlYWtlciBhdHRlbXB0cyB0byBhZGQgYW5vdGhlciB3b3JraW5nL3By
b3RlY3Rpb24gTFNQLCB0aGU8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgTVVTVCBz
ZW5kIFBDRXJyIHdpdGggRXJyb3ItVHlwZSAyNiAoQXNzb2NpYXRpb24gRXJyb3IpPC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIFBDRVAgcGVlciBNVVNUIHNlbmQgUENFcnIgd2l0
aCBFcnJvci1UeXBlIDI2IChBc3NvY2lhdGlvbiBFcnJvcik8L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPiAgIFtJLUQuaWV0Zi1wY2UtYXNzb2NpYXRpb24tZ3JvdXBdIGFuZCBFcnJvci1WYWx1
ZSBUQkQ0IChBdHRlbXB0IHRvIGFkZDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAg
IFtJLUQuaWV0Zi1wY2UtYXNzb2NpYXRpb24tZ3JvdXBdIGFuZCBFcnJvci1WYWx1ZSBUQkQ0IChB
dHRlbXB0IHRvIGFkZDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgYW5vdGhlciB3b3Jr
aW5nL3Byb3RlY3Rpb24gTFNQIGZvciBQYXRoIFByb3RlY3Rpb24gQXNzb2NpYXRpb24pLjwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIGFub3RoZXIgd29ya2luZy9wcm90ZWN0aW9u
IExTUCBmb3IgUGF0aCBQcm90ZWN0aW9uIEFzc29jaWF0aW9uKS48L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xh
c3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+ICAgV2hlbiB0aGUgcHJvdGVjdGlvbiB0eXBlIGlzIHNldCB0byAxOk4g
d2l0aCBOJmd0OzEsIHRoZXJlIE1VU1QgYmUgb25seTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmlnaHQiPiAgIFdoZW4gdGhlIHByb3RlY3Rpb24gdHlwZSBpcyBzZXQgdG8gMTpOIHdpdGggTiZn
dDsxLCB0aGVyZSBNVVNUIGJlIG9ubHk8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIG9u
ZSB3b3JraW5nIExTUCBhbmQgbnVtYmVyIG9mIHByb3RlY3Rpb24gTFNQcyBNVVNUIE5PVCBiZSBt
b3JlIHRoYW4gTjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIG9uZSB3b3JraW5n
IExTUCBhbmQgbnVtYmVyIG9mIHByb3RlY3Rpb24gTFNQcyBNVVNUIE5PVCBiZSBtb3JlIHRoYW4g
TjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgd2l0aGluIGEgUFBBRy4gIElmIGEgUENF
UCBzcGVha2VyIGF0dGVtcHRzIHRvIGFkZCBhbm90aGVyIHdvcmtpbmcvPC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyaWdodCI+ICAgd2l0aGluIGEgUFBBRy4gIElmIGEgUENFUCBzcGVha2VyIGF0
dGVtcHRzIHRvIGFkZCBhbm90aGVyIHdvcmtpbmcvPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij4gICBwcm90ZWN0aW9uIExTUCwgdGhlIFBDRVAgcGVlciBNVVNUIHNlbmQgUENFcnIgd2l0aCBF
cnJvci1UeXBlIDI2PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgcHJvdGVjdGlv
biBMU1AsIHRoZSBQQ0VQIHBlZXIgTVVTVCBzZW5kIFBDRXJyIHdpdGggRXJyb3ItVHlwZSAyNjwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgKEFzc29jaWF0aW9uIEVycm9yKSBbSS1ELmll
dGYtcGNlLWFzc29jaWF0aW9uLWdyb3VwXSBhbmQgRXJyb3ItVmFsdWU8L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij4gICAoQXNzb2NpYXRpb24gRXJyb3IpIFtJLUQuaWV0Zi1wY2UtYXNz
b2NpYXRpb24tZ3JvdXBdIGFuZCBFcnJvci1WYWx1ZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVm
dCI+ICAgVEJENCAoQXR0ZW1wdCB0byBhZGQgYW5vdGhlciB3b3JraW5nL3Byb3RlY3Rpb24gTFNQ
IGZvciBQYXRoPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgVEJENCAoQXR0ZW1w
dCB0byBhZGQgYW5vdGhlciB3b3JraW5nL3Byb3RlY3Rpb24gTFNQIGZvciBQYXRoPC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBQcm90ZWN0aW9uIEFzc29jaWF0aW9uKS48L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBQcm90ZWN0aW9uIEFzc29jaWF0aW9uKS48L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGlkPSJwYXJ0LTciIGNs
YXNzPSJjaGFuZ2UiPjx0ZD48L3RkPjx0aD48c21hbGw+c2tpcHBpbmcgdG8gY2hhbmdlIGF0PC9z
bWFsbD48YSBocmVmPSIjcGFydC03Ij48ZW0+IHBhZ2UgOSwgbGluZSAyMTxzcGFuIGNsYXNzPSJo
aWRlIj4gwrY8L3NwYW4+PC9lbT48L2E+PC90aD48dGg+IDwvdGg+PHRoPjxzbWFsbD5za2lwcGlu
ZyB0byBjaGFuZ2UgYXQ8L3NtYWxsPjxhIGhyZWY9IiNwYXJ0LTciPjxlbT4gcGFnZSA5LCBsaW5l
IDI1PHNwYW4gY2xhc3M9ImhpZGUiPiDCtjwvc3Bhbj48L2VtPjwvYT48L3RoPjx0ZD48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAg
IChlLmcuLCBub2RlLCBTUkxHIGRpc2pvaW50KS4gIFRoaXMgZW5zdXJlcyB0aGF0IGEgc2luZ2xl
IGZhaWx1cmUgd2lsbDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIChlLmcuLCBu
b2RlLCBTUkxHIGRpc2pvaW50KS4gIFRoaXMgZW5zdXJlcyB0aGF0IGEgc2luZ2xlIGZhaWx1cmUg
d2lsbDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgbm90IGFmZmVjdCBib3RoIHRoZSB3
b3JraW5nIGFuZCBwcm90ZWN0aW9uIExTUHMuICBUaGUgZGlzam9pbnQ8L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij4gICBub3QgYWZmZWN0IGJvdGggdGhlIHdvcmtpbmcgYW5kIHByb3Rl
Y3Rpb24gTFNQcy4gIFRoZSBkaXNqb2ludDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAg
cmVxdWlyZW1lbnQgZm9yIGEgZ3JvdXAgb2YgTFNQcyBpcyBoYW5kbGVkIHZpYSBhbm90aGVyIEFz
c29jaWF0aW9uPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgcmVxdWlyZW1lbnQg
Zm9yIGEgZ3JvdXAgb2YgTFNQcyBpcyBoYW5kbGVkIHZpYSBhbm90aGVyIEFzc29jaWF0aW9uPC90
ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICB0eXBlIGNhbGxlZCAiRGlzam9pbnRuZXNzIEFz
c29jaWF0aW9uIiwgYXMgZGVzY3JpYmVkIGluPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdo
dCI+ICAgdHlwZSBjYWxsZWQgIkRpc2pvaW50bmVzcyBBc3NvY2lhdGlvbiIsIGFzIGRlc2NyaWJl
ZCBpbjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgW0ktRC5pZXRmLXBjZS1hc3NvY2lh
dGlvbi1kaXZlcnNpdHldLiAgVGhlIGRpdmVyc2l0eSByZXF1aXJlbWVudHMgZm9yPC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgW0ktRC5pZXRmLXBjZS1hc3NvY2lhdGlvbi1kaXZl
cnNpdHldLiAgVGhlIGRpdmVyc2l0eSByZXF1aXJlbWVudHMgZm9yPC90ZD48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsZWZ0Ij4gICB0aGUgcHJvdGVjdGlvbiBMU1AgYXJlIGFsc28gaGFuZGxlZCBieSBpbmNs
dWRpbmcgYm90aCBBU1NPQ0lBVElPTjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAg
IHRoZSBwcm90ZWN0aW9uIExTUCBhcmUgYWxzbyBoYW5kbGVkIGJ5IGluY2x1ZGluZyBib3RoIEFT
U09DSUFUSU9OPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBvYmplY3RzIGlkZW50aWZ5
aW5nIGJvdGggdGhlIHByb3RlY3Rpb24gYXNzb2NpYXRpb24gZ3JvdXAgYW5kIHRoZTwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIG9iamVjdHMgaWRlbnRpZnlpbmcgYm90aCB0aGUg
cHJvdGVjdGlvbiBhc3NvY2lhdGlvbiBncm91cCBhbmQgdGhlPC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij4gICBkaXNqb2ludCBhc3NvY2lhdGlvbiBncm91cCBmb3IgdGhlIGdyb3VwIG9mIExT
UHMuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgZGlzam9pbnQgYXNzb2NpYXRp
b24gZ3JvdXAgZm9yIHRoZSBncm91cCBvZiBMU1BzLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVm
dCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij4gICBbUkZDNDg3Ml0gaW50cm9kdWNlcyB0aGUgY29uY2VwdCBhbmQgbWVjaGFuaXNt
cyB0byBzdXBwb3J0IHRoZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFtSRkM0
ODcyXSBpbnRyb2R1Y2VzIHRoZSBjb25jZXB0IGFuZCBtZWNoYW5pc21zIHRvIHN1cHBvcnQgdGhl
PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9ImRpZmYwMDI2
Ij48dGQ+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsYmxvY2siPiAgIGFzc29jaWF0aW9uIG9mIG9uZSBMU1AgdG8gYW5vdGhlciBMU1AgYWNy
b3NzIGRpZmZlcmVudCBSU1ZQIDxzcGFuIGNsYXNzPSJkZWxldGUiPi0gPC9zcGFuPlRyYWZmaWM8
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgYXNzb2NpYXRpb24gb2Ygb25lIExT
UCB0byBhbm90aGVyIExTUCBhY3Jvc3MgZGlmZmVyZW50IFJTVlAgVHJhZmZpYzwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+ICAgRW5naW5lZXJpbmcgKFJTVlAtVEUpIHNlc3Npb25zIHVzaW5n
IEFTU09DSUFUSU9OIGFuZCBQUk9URUNUSU9OPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdo
dCI+ICAgRW5naW5lZXJpbmcgKFJTVlAtVEUpIHNlc3Npb25zIHVzaW5nIEFTU09DSUFUSU9OIGFu
ZCBQUk9URUNUSU9OPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBvYmplY3QuICBUaGUg
aW5mb3JtYXRpb24gaW4gdGhlIFBQQUcgVExWIGluIFBDRVAgYXMgcmVjZWl2ZWQgZnJvbSB0aGU8
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBvYmplY3QuICBUaGUgaW5mb3JtYXRp
b24gaW4gdGhlIFBQQUcgVExWIGluIFBDRVAgYXMgcmVjZWl2ZWQgZnJvbSB0aGU8L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlmZjAwMjciPjx0ZD48L3Rk
PjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9j
ayI+ICAgUENFPHNwYW4gY2xhc3M9ImRlbGV0ZSI+LDwvc3Bhbj4gaXMgdXNlZCB0byB0cmlnZ2Vy
IHRoZSBzaWduYWxsaW5nIG9mIHdvcmtpbmcgTFNQIGFuZCBwcm90ZWN0aW9uPC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIFBDRSBpcyB1c2VkIHRvIHRyaWdnZXIgdGhlIHNpZ25h
bGxpbmcgb2Ygd29ya2luZyBMU1AgYW5kIHByb3RlY3Rpb248L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPiAgIExTUCwgd2l0aCB0aGUgUGF0aCBQcm90ZWN0aW9uIEFzc29jaWF0aW9uIEZsYWdz
IG1hcHBlZCB0byB0aGU8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBMU1AsIHdp
dGggdGhlIFBhdGggUHJvdGVjdGlvbiBBc3NvY2lhdGlvbiBGbGFncyBtYXBwZWQgdG8gdGhlPC90
ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBjb3JyZXNwb25kaW5nIGZpZWxkcyBpbiB0aGUg
UFJPVEVDVElPTiBPYmplY3QgaW4gUlNWUC1URS48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij4gICBjb3JyZXNwb25kaW5nIGZpZWxkcyBpbiB0aGUgUFJPVEVDVElPTiBPYmplY3QgaW4g
UlNWUC1URS48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+Ni4gIElBTkEgQ29uc2lk
ZXJhdGlvbnM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij42LiAgSUFOQSBDb25zaWRl
cmF0aW9uczwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBbTm90ZSB0byBSRkMg
RWRpdG9yIGFuZCBJQU5BOiBTZWN0aW9ucyAzLjEsIDMuMiwgYW5kIDQuNSBjb250YWluPC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgW05vdGUgdG8gUkZDIEVkaXRvciBhbmQgSUFO
QTogU2VjdGlvbnMgMy4xLCAzLjIsIGFuZCA0LjUgY29udGFpbjwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFz
cz0ibGVmdCI+ICAgIlRCRDEiIHRocm91Z2ggIlRCRDUiIHRob3NlIHNob3VsZCBiZSByZXBsYWNl
ZCBieSB0aGUgdmFsdWVzIHRoYXQ8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAi
VEJEMSIgdGhyb3VnaCAiVEJENSIgdGhvc2Ugc2hvdWxkIGJlIHJlcGxhY2VkIGJ5IHRoZSB2YWx1
ZXMgdGhhdDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgSUFOQSBhc3NpZ25zLl08L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBJQU5BIGFzc2lnbnMuXTwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij42LjEuICBBc3NvY2lhdGlvbiBUeXBlPC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyaWdodCI+Ni4xLiAgQXNzb2NpYXRpb24gVHlwZTwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9InBhcnQtOCIgY2xhc3M9ImNo
YW5nZSI+PHRkPjwvdGQ+PHRoPjxzbWFsbD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8L3NtYWxsPjxh
IGhyZWY9IiNwYXJ0LTgiPjxlbT4gcGFnZSAxMiwgbGluZSAzMzxzcGFuIGNsYXNzPSJoaWRlIj4g
wrY8L3NwYW4+PC9lbT48L2E+PC90aD48dGg+IDwvdGg+PHRoPjxzbWFsbD5za2lwcGluZyB0byBj
aGFuZ2UgYXQ8L3NtYWxsPjxhIGhyZWY9IiNwYXJ0LTgiPjxlbT4gcGFnZSAxMiwgbGluZSA0MTxz
cGFuIGNsYXNzPSJoaWRlIj4gwrY8L3NwYW4+PC9lbT48L2E+PC90aD48dGQ+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAg
IFdlIHdvdWxkIGxpa2UgdG8gdGhhbmsgSmVmZiBUYW50c3VyYSwgWGlhbiBaaGFuZyBhbmQgR3Jl
ZyBNaXJza3kgZm9yPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgV2Ugd291bGQg
bGlrZSB0byB0aGFuayBKZWZmIFRhbnRzdXJhLCBYaWFuIFpoYW5nIGFuZCBHcmVnIE1pcnNreSBm
b3I8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIHRoZWlyIGNvbnRyaWJ1dGlvbnMgdG8g
dGhpcyBkb2N1bWVudC48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICB0aGVpciBj
b250cmlidXRpb25zIHRvIHRoaXMgZG9jdW1lbnQuPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPiAgIFRoYW5rcyB0byBJbmVzIFJvYmxlcyBmb3IgdGhlIFJUR0RJUiByZXZpZXcuPC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgVGhhbmtzIHRvIEluZXMgUm9ibGVzIGZv
ciB0aGUgUlRHRElSIHJldmlldy48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAg
VGhhbmtzIHRvIFBldGUgUmVzbmljayBmb3IgdGhlIEdFTkFSVCByZXZpZXcuPC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgVGhhbmtzIHRvIFBldGUgUmVzbmljayBmb3IgdGhlIEdF
TkFSVCByZXZpZXcuPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFRoYW5rcyB0
byBEb25hbGQgRWFzdGxha2UgZm9yIHRoZSBTRUNESVIgcmV2aWV3LjwvdGQ+PHRkPiA8L3RkPjx0
ZCBjbGFzcz0icmlnaHQiPiAgIFRoYW5rcyB0byBEb25hbGQgRWFzdGxha2UgZm9yIHRoZSBTRUNE
SVIgcmV2aWV3LjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8
dHIgaWQ9ImRpZmYwMDI4Ij48dGQ+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJs
b2NrIj4gICA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij5UaGFua3MgdG8gQmFycnkgTGVpYmEgZm9yIHRo
ZSBJRVNHIHJldmlldy48L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgPC90ZD48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij4xMC4gIFJlZmVyZW5jZXM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJpZ2h0Ij4xMC4gIFJlZmVyZW5jZXM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
MTAuMS4gIE5vcm1hdGl2ZSBSZWZlcmVuY2VzPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdo
dCI+MTAuMS4gIE5vcm1hdGl2ZSBSZWZlcmVuY2VzPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPiAgIFtSRkMyMTE5XSAgQnJhZG5lciwgUy4sICJLZXkgd29yZHMgZm9yIHVzZSBpbiBS
RkNzIHRvIEluZGljYXRlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgW1JGQzIx
MTldICBCcmFkbmVyLCBTLiwgIktleSB3b3JkcyBmb3IgdXNlIGluIFJGQ3MgdG8gSW5kaWNhdGU8
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgUmVxdWlyZW1lbnQgTGV2
ZWxzIiwgQkNQIDE0LCBSRkMgMjExOSw8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4g
ICAgICAgICAgICAgIFJlcXVpcmVtZW50IExldmVscyIsIEJDUCAxNCwgUkZDIDIxMTksPC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgIERPSSAxMC4xNzQ4Ny9SRkMyMTE5
LCBNYXJjaCAxOTk3LDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAg
ICAgRE9JIDEwLjE3NDg3L1JGQzIxMTksIE1hcmNoIDE5OTcsPC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij4gICAgICAgICAgICAgICZsdDtodHRwczovL3d3dy5yZmMtZWRpdG9yLm9yZy9pbmZv
L3JmYzIxMTkmZ3Q7LjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAg
ICAgJmx0O2h0dHBzOi8vd3d3LnJmYy1lZGl0b3Iub3JnL2luZm8vcmZjMjExOSZndDsuPC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFtSRkMzMjA5XSAgQXdkdWNoZSwgRC4sIEJl
cmdlciwgTC4sIEdhbiwgRC4sIExpLCBULiwgU3Jpbml2YXNhbiwgVi4sPC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyaWdodCI+ICAgW1JGQzMyMDldICBBd2R1Y2hlLCBELiwgQmVyZ2VyLCBMLiwg
R2FuLCBELiwgTGksIFQuLCBTcmluaXZhc2FuLCBWLiw8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGlkPSJwYXJ0LTkiIGNsYXNzPSJjaGFuZ2UiPjx0ZD48
L3RkPjx0aD48c21hbGw+c2tpcHBpbmcgdG8gY2hhbmdlIGF0PC9zbWFsbD48YSBocmVmPSIjcGFy
dC05Ij48ZW0+IHBhZ2UgMTQsIGxpbmUgNDM8c3BhbiBjbGFzcz0iaGlkZSI+IMK2PC9zcGFuPjwv
ZW0+PC9hPjwvdGg+PHRoPiA8L3RoPjx0aD48c21hbGw+c2tpcHBpbmcgdG8gY2hhbmdlIGF0PC9z
bWFsbD48YSBocmVmPSIjcGFydC05Ij48ZW0+IHBhZ2UgMTUsIGxpbmUgOTxzcGFuIGNsYXNzPSJo
aWRlIj4gwrY8L3NwYW4+PC9lbT48L2E+PC90aD48dGQ+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBbSS1ELmlldGYtcGNlLXBj
ZXAteWFuZ108L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBbSS1ELmlldGYtcGNl
LXBjZXAteWFuZ108L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgRGhv
ZHksIEQuLCBIYXJkd2ljaywgSi4sIEJlZXJhbSwgVi4sIGFuZCBKLiBUYW50c3VyYSwgIkE8L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgIERob2R5LCBELiwgSGFy
ZHdpY2ssIEouLCBCZWVyYW0sIFYuLCBhbmQgSi4gVGFudHN1cmEsICJBPC90ZD48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRk
IGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgIFlBTkcgRGF0YSBNb2RlbCBmb3IgUGF0aCBDb21w
dXRhdGlvbiBFbGVtZW50PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAg
ICAgICBZQU5HIERhdGEgTW9kZWwgZm9yIFBhdGggQ29tcHV0YXRpb24gRWxlbWVudDwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICBDb21tdW5pY2F0aW9ucyBQcm90b2Nv
bCAoUENFUCkiLCBkcmFmdC1pZXRmLXBjZS1wY2VwLTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmlnaHQiPiAgICAgICAgICAgICAgQ29tbXVuaWNhdGlvbnMgUHJvdG9jb2wgKFBDRVApIiwgZHJh
ZnQtaWV0Zi1wY2UtcGNlcC08L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAg
ICAgeWFuZy0xMiAod29yayBpbiBwcm9ncmVzcyksIEp1bHkgMjAxOS48L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgIHlhbmctMTIgKHdvcmsgaW4gcHJvZ3Jlc3Mp
LCBKdWx5IDIwMTkuPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFtJLUQuaWV0
Zi1wY2UtYXNzb2NpYXRpb24tZGl2ZXJzaXR5XTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPiAgIFtJLUQuaWV0Zi1wY2UtYXNzb2NpYXRpb24tZGl2ZXJzaXR5XTwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICBMaXRrb3dza2ksIFMuLCBTaXZhYmFsYW4sIFMu
LCBCYXJ0aCwgQy4sIGFuZCBNLiBOZWdpLDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PiAgICAgICAgICAgICAgTGl0a293c2tpLCBTLiwgU2l2YWJhbGFuLCBTLiwgQmFydGgsIEMuLCBh
bmQgTS4gTmVnaSw8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgIlBh
dGggQ29tcHV0YXRpb24gRWxlbWVudCBDb21tdW5pY2F0aW9uIFByb3RvY29sIChQQ0VQKTwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgIlBhdGggQ29tcHV0YXRp
b24gRWxlbWVudCBDb21tdW5pY2F0aW9uIFByb3RvY29sIChQQ0VQKTwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGVmdCI+ICAgICAgICAgICAgICBFeHRlbnNpb24gZm9yIExTUCBEaXZlcnNpdHkgQ29u
c3RyYWludCBTaWduYWxpbmciLCBkcmFmdC08L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij4gICAgICAgICAgICAgIEV4dGVuc2lvbiBmb3IgTFNQIERpdmVyc2l0eSBDb25zdHJhaW50IFNp
Z25hbGluZyIsIGRyYWZ0LTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyIGlkPSJkaWZmMDAyOSI+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICAgICAgICAgICAgIGlldGYtcGNlLWFzc29j
aWF0aW9uLWRpdmVyc2l0eS08c3BhbiBjbGFzcz0iZGVsZXRlIj4wOTwvc3Bhbj4gKHdvcmsgaW4g
cHJvZ3Jlc3MpLDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICAgICAgICAgICAg
IGlldGYtcGNlLWFzc29jaWF0aW9uLWRpdmVyc2l0eS08c3BhbiBjbGFzcz0iaW5zZXJ0Ij4xMDwv
c3Bhbj4gKHdvcmsgaW4gcHJvZ3Jlc3MpLDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAg
ICAgICAgICAgICBBdWd1c3QgMjAxOS48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4g
ICAgICAgICAgICAgIEF1Z3VzdCAyMDE5LjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij4gICBbSS1ELmlldGYtcGNlLXNlZ21lbnQtcm91dGluZ108L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij4gICBbSS1ELmlldGYtcGNlLXNlZ21lbnQtcm91dGluZ108L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgU2l2YWJhbGFuLCBTLiwgRmlsc2ZpbHMsIEMu
LCBUYW50c3VyYSwgSi4sIEhlbmRlcmlja3gsIFcuLDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmlnaHQiPiAgICAgICAgICAgICAgU2l2YWJhbGFuLCBTLiwgRmlsc2ZpbHMsIEMuLCBUYW50c3Vy
YSwgSi4sIEhlbmRlcmlja3gsIFcuLDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAg
ICAgICAgICBhbmQgSi4gSGFyZHdpY2ssICJQQ0VQIEV4dGVuc2lvbnMgZm9yIFNlZ21lbnQgUm91
dGluZyIsPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAgICBhbmQg
Si4gSGFyZHdpY2ssICJQQ0VQIEV4dGVuc2lvbnMgZm9yIFNlZ21lbnQgUm91dGluZyIsPC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgIGRyYWZ0LWlldGYtcGNlLXNlZ21l
bnQtcm91dGluZy0xNiAod29yayBpbiBwcm9ncmVzcyksPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+ICAgICAgICAgICAgICBkcmFmdC1pZXRmLXBjZS1zZWdtZW50LXJvdXRpbmctMTYg
KHdvcmsgaW4gcHJvZ3Jlc3MpLDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAg
ICAgICBNYXJjaCAyMDE5LjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAg
ICAgICAgTWFyY2ggMjAxOS48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgW0kt
RC5saXRrb3dza2ktcGNlLXN0YXRlLXN5bmNdPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdo
dCI+ICAgW0ktRC5saXRrb3dza2ktcGNlLXN0YXRlLXN5bmNdPC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij4gICAgICAgICAgICAgIExpdGtvd3NraSwgUy4sIFNpdmFiYWxhbiwgUy4sIExpLCBD
LiwgYW5kIEguIFpoZW5nLCAiSW50ZXI8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4g
ICAgICAgICAgICAgIExpdGtvd3NraSwgUy4sIFNpdmFiYWxhbiwgUy4sIExpLCBDLiwgYW5kIEgu
IFpoZW5nLCAiSW50ZXI8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CgogICAgIDx0
cj48dGQ+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPjwvdGQ+PHRkPjwvdGQ+PC90cj4KICAgICA8dHIgaWQ9ImVuZCIgYmdjb2xvcj0iZ3JheSI+
PHRoIGNvbHNwYW49IjUiIGFsaWduPSJjZW50ZXIiPiZuYnNwO0VuZCBvZiBjaGFuZ2VzLiAyOSBj
aGFuZ2UgYmxvY2tzLiZuYnNwOzwvdGg+PC90cj4KICAgICA8dHIgY2xhc3M9InN0YXRzIj48dGQ+
PC90ZD48dGg+PGk+NDcgbGluZXMgY2hhbmdlZCBvciBkZWxldGVkPC9pPjwvdGg+PHRoPjxpPiA8
L2k+PC90aD48dGg+PGk+NTIgbGluZXMgY2hhbmdlZCBvciBhZGRlZDwvaT48L3RoPjx0ZD48L3Rk
PjwvdHI+CiAgICAgPHRyPjx0ZCBjb2xzcGFuPSI1IiBjbGFzcz0ic21hbGwiIGFsaWduPSJjZW50
ZXIiPjxicj5UaGlzIGh0bWwgZGlmZiB3YXMgcHJvZHVjZWQgYnkgcmZjZGlmZiAxLjQ3LiBUaGUg
bGF0ZXN0IHZlcnNpb24gaXMgYXZhaWxhYmxlIGZyb20gPGEgaHJlZj0iaHR0cDovL3d3dy50b29s
cy5pZXRmLm9yZy90b29scy9yZmNkaWZmLyI+aHR0cDovL3Rvb2xzLmlldGYub3JnL3Rvb2xzL3Jm
Y2RpZmYvPC9hPiA8L3RkPjwvdHI+CiAgIDwvdGJvZHk+PC90YWJsZT4KICAgCiAgIAo8L2JvZHk+
PC9odG1sPg==
--00000000000059ff940592c3549d--


From nobody Tue Sep 17 10:53:21 2019
Return-Path: <barryleiba@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70353120A05; Tue, 17 Sep 2019 10:53:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.923
X-Spam-Level: 
X-Spam-Status: No, score=-1.923 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.026, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uBp_0dIHLRTj; Tue, 17 Sep 2019 10:53:12 -0700 (PDT)
Received: from mail-io1-f47.google.com (mail-io1-f47.google.com [209.85.166.47]) (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 C97871209CD; Tue, 17 Sep 2019 10:53:12 -0700 (PDT)
Received: by mail-io1-f47.google.com with SMTP id q1so9798214ion.1; Tue, 17 Sep 2019 10:53:12 -0700 (PDT)
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:content-transfer-encoding; bh=agAnK23cc4XJ/fLmgDTuJBhpap0+0jmR7uYj86pGf6Q=; b=PXuFr18KC0njDktI8733OiRXBW3NEzJxcD6FU89DzazmoPsFmDgOVjRt5H7/sOs8ws z4ts2yXwPYbnvuR8kYMj5OGa7BnOdPB/XnQR1t3OVPcJl8TmDWIPTWIC1k3l8fGAO/Md gltuK3LqPl+Z4OiW25RrGXgW3bMOPnPe1YjaCQf4Hdvk5ZR0k2sorosMwuU+54JqqQtG kaToQEty/HDa5Hl7YNcCedkwJdb9viAXio67CO28Voq4BqxtrRqnn3bL9m1/WHMyPBau MNL8NStqs7Qyn/tahRCxNhle0fwsmIHx6nIGCloqc3n71NQNfV1BZHOA6OKNqRb6hje6 gtOw==
X-Gm-Message-State: APjAAAVfzvASxsDB0VQB9D5awxu1s+9kiI2/cW0TQtTltzezDGfA6ntZ W3cSvRdHmA6GlgYtf9AE7BzPJdF6Dbh7gFFVlzs=
X-Google-Smtp-Source: APXvYqzIascZ4Iq9mIr5pJVDaIV8OVUY5iRay3nACBQsi4cKRXsyT7IBOpPLI+dsRyBjt/7BfwJFlN6ypIft2z+XIS4=
X-Received: by 2002:a5d:96c6:: with SMTP id r6mr5114855iol.266.1568742791740;  Tue, 17 Sep 2019 10:53:11 -0700 (PDT)
MIME-Version: 1.0
References: <156849799383.3020.16398829686379997035.idtracker@ietfa.amsl.com> <CAM5Nu_zFe31wbGORGvYffxdGQtfMA+_U-twdRGndbUDObHfG9g@mail.gmail.com>
In-Reply-To: <CAM5Nu_zFe31wbGORGvYffxdGQtfMA+_U-twdRGndbUDObHfG9g@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Tue, 17 Sep 2019 10:53:00 -0700
Message-ID: <CALaySJ+m5_DhXc0wRiFwskMrsCBCo_CMXvg0CSWkQX-5qXi8eg@mail.gmail.com>
To: Mahend Negi <mahend.ietf@gmail.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pce-stateful-path-protection@ietf.org, Julien Meuric <julien.meuric@orange.com>, pce-chairs <pce-chairs@ietf.org>, pce@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/0rOPNVVctX2Qii10gmRWbQ9EM3w>
Subject: Re: [Pce] Barry Leiba's No Objection on draft-ietf-pce-stateful-path-protection-10: (with COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Sep 2019 17:53:15 -0000

Hi, Mahend, and thanks for the response and for addressing my comments.

> For this one comment ->
> =3D=3D=3D
> =E2=80=94 Section 4.5 =E2=80=94
>
>    When the protection type is set to 1+1 or 1:N with N=3D1, there MUST b=
e
> =E2=80=A6
>    When the protection type is set to 1:N with N>1, there MUST be
>
> This is a style thing, so take it or leave it as you please =E2=80=94 it=
=E2=80=99s not wrong
> the way it=E2=80=99s written.  It=E2=80=99s just that the =E2=80=9C1:N wi=
th N=3D1=E2=80=9D and =E2=80=9C1:N with N>1=E2=80=9D
> distinction isn=E2=80=99t necessary, and I think it=E2=80=99s distracting=
 and invites
> uncertainty.  If you just made these like this:
>
> NEW
>    When the protection type is set to 1+1, there MUST be
> =E2=80=A6
>    When the protection type is set to 1:N, there MUST be
> END
>
> =E2=80=A6it would be equally correct, but also simpler and, I think, less=
 likely to be
> confusing.
> =3D=3D=3D
>
> The first sentence is for the case 1+1 and 1:1. Since RFC 4872 does
> not define an explicit state 1:1, it define 1:N only this wording was
> chosen. I have made this change "When the protection type is set to
> 1+1 or 1:1 (1:N with N=3D1)...".

I understand what the text says, but my comment is about why you are
calling out "1:N with N=3D1" separately.  What benefit does that have
for the text?  The regular "1:N" text works perfectly whether N=3D1 or
N>1, so why not just let that text serve for all cases of N?  Is there
a benefit that I'm not seeing to having N=3D1 as a separate case?

Barry


From nobody Tue Sep 17 12:34:44 2019
Return-Path: <noreply@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 66E761209AF; Tue, 17 Sep 2019 12:34:34 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Kaduk via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-pce-stateful-pce-auto-bandwidth@ietf.org, Adrian Farrel <adrian@olddog.co.uk>, pce-chairs@ietf.org, adrian@olddog.co.uk,  pce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.101.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Benjamin Kaduk <kaduk@mit.edu>
Message-ID: <156874887441.17499.7855633347557404477.idtracker@ietfa.amsl.com>
Date: Tue, 17 Sep 2019 12:34:34 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/VO-c5JHCwtQ-GIuEDA3K6Ku4Kgk>
Subject: [Pce] Benjamin Kaduk's Discuss on draft-ietf-pce-stateful-pce-auto-bandwidth-11: (with DISCUSS and COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Sep 2019 19:34:35 -0000

Benjamin Kaduk has entered the following ballot position for
draft-ietf-pce-stateful-pce-auto-bandwidth-11: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-pce-auto-bandwidth/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

This document seems generally useful, and thanks for it.  I think
there's a couple places where it's ambiguous or unclear, and hopefully
we can tighten up the language without needing extensive changes.

There may be an internal inconsistency in Section 2.3's definitions
relating the Overflow-Count and the Overflow-Threshold: the description
of Overflow-Count reads as if it is a reported quantity, but the
description of Overflow-Threshold implies that Overflow-Count is a
configured parameter.  (Similarly for the Underflow- variants.)
Specifically, the sentence "[t]his value indicates how many times
consecutively, the percentage or absolute difference between the current
MaxAvgBw and the current bandwidth reservation of the LSP is greater
than or equal to the Overflow-Threshold value" uses the descriptive
verb "is" as opposed to a conditional such as "needs to be [...] in
order to [...]".

Section 5.2.3.2 says:

   If the percentage difference between the current MaxAvgBw and the
   current bandwidth reservation is greater than or less than or equal
   to the threshold percentage, the LSP bandwidth is adjusted to the
   current bandwidth demand (MaxAvgBw) (as long as the difference in the
   bandwidth is at least or above the Minimum-Threshold).

As written ("greater than or less than or equal to"), this is always
true, which cannot be what was intended.  Probably we should reword to
just "greater than" and talk about the percentage absolute difference,
i.e., 100 * abs(MaxAvgBw - CurrentRes) / CurrentRes .


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

As a general note, I'm not sure the phrase "calculated bandwidth to be
adjusted" is a great fit for how it's currently being used.
Specifically, the "calculation" in question seems to just be taking the
maximum of a sliding window of per-timeslice average bandwidth values,
and this seems like a sufficiently small amount of computation that I'd
be comfortable describing it as a "measurement", for "measured bandwidth
as input to path calculation".  That is, this doesn't seem like it comes
close to the amount of computation involved in actually computing paths,
so I keep misreading what information is being sent where.

Section 1

   Over time, based on the varying traffic pattern, an LSP established
   with a certain bandwidth may require to adjust the bandwidth reserved
   in the network dynamically.  The head-end Label Switch Router (LSR)
   monitors the actual bandwidth demand of the established LSP and
   periodically computes new bandwidth.  The head-end LSR adjusts the
   bandwidth reservation of the LSP based on the computed bandwidth
   automatically.  This feature is commonly referred to as Auto-
   Bandwidth.  The Auto-Bandwidth feature is described in detail in
   Section 4 of this document.

>From just this text, I can't tell if this is describing the mechanisms of
this document or an existing Auto-Bandwidth feature that is related to
the mechanisms of this document.

   In the model considered in this document, the PCC (head-end of the
   LSP) collects the traffic rate samples flowing through the LSP and
   calculates the new adjusted bandwidth.  The PCC reports the
   calculated bandwidth to be adjusted to the PCE.  This is similar to
   the Passive stateful PCE model, while the Passive stateful PCE uses
   path request/reply mechanism, the Active stateful PCE uses
   report/update mechanism.  [...]

nit: I think the punctuation in this last sentence needs some tweaking,
as there looks to be a comma splice at present.
(It's also unclear how much we need to talk about Passive stateful PCE,
since just two paragraphs ago we say we focus on Active stateful PCE in
this document.)

   This document defines the PCEP extensions needed to support Auto-
   Bandwidth feature in a Active stateful PCE model where the LSP
   bandwidth to be adjusted is calculated on the PCC (head-end of the
   LSP). The use of PCE to calculate the bandwidth to be adjusted is out
   of scope of this document.

Maybe I'm just confused about active vs. passive in general, but I
thought that active stateful PCE involved the PCE "making the decisions"
with the PCC just providing input data.  But here we're saying that the
PCC is making the bandwidth decision, even though the rest of the LSP
computation remains on the PCE?  Or is "calculate the bandwidth to be
adjusted" referring to "evaluate the expression max_{time periods}(avg.
bandwidth per time period)" (as opposed to "compute the bandwidth
adjustment to make)?

Section 2.3

Are we assuming any relationship between the Up-Adjustment-Threshold and
the Overflow-Threshold?

      traffic demand.  If the percentage or absolute difference between
      the current MaxAvgBw and the current bandwidth reservation of the
      LSP is greater than or equal to the threshold value, the overflow
      condition is set to be met.  The LSP bandwidth is adjusted to the

nit: I think s/set to be met/said to be met/ ?  (this appears twice)

   Minimum-Threshold:  The increase or decrease of the LSP bandwidth
      should be at least or above the minimum-threshold represented as
      an absolute bandwidth value before the bandwidth adjustment for
      the LSP is made.  This threshold can be seen as a suppression
      threshold that is used along with a percentage threshold to avoid
      unnecessary auto-bandwidth adjustments and re-signaling of the LSP
      at low bandwidth values.

I can't tell from this text if this threshold is a (LSP) bandwidth
value/measurement or a bandwidth offset between configured and measured
values.  (The subsequent protocol element definitions are more clear
that it's the latter.)

Section 3

The column headings in Table 1 refer to who initiates the LSP in
question, right?

   The PCEP speaker supporting this document must have a mechanism to
   advertise the automatic bandwidth adjustment capability for both PCC-
   Initiated and PCE-Initiated LSPs.

Just checking on "must" vs. "MUST" here.

   o  It is required to identify and inform the PCC, which LSPs are
      enabled with Auto-Bandwidth feature.  Not all LSPs in some
      deployments would like their bandwidth to be dependent on the
      real-time bandwidth usage but be constant as set by the operator.

nit: I suggest NEW:

%  o  It is required to identify and inform the PCC which LSPs have
%     enabled the Auto-Bandwidth feature.  Not all LSPs in some
%     deployments would like their bandwidth to be dependent on the
%     real-time bandwidth usage; for some LSPs leaving the bandwidth
%     constant as set by the operator is preferred.

Section 4.2

   When the Auto-Bandwidth feature is enabled, the measured traffic rate
   is periodically sampled at each Sample-Interval (which can be
   configured by an operator and the default value as 5 minutes) by the
   PCC, when the PCC is the head-end node of the LSP.  The traffic rate

Do we cover what happens in the case when the PCC is not the head-end
node of the LSP?

Section 5.1

   o  The PCEP speaker that does not recognize the extensions defined in
      this document sends the PCErr message with error-type 2
      (capability not supported) as per Section 6.9 in [RFC5440].

This refers to when the actual new messages (e.g.,
AUTO-BANDWIDTH-ATTRIBUTES TLV) are being used, not merely advertising
the Auto-Bandwidth Capability TLV in the OPEN object, right?  That is,
this is descriptive language of what the core protocol spec mandates as
error handling in the presence of unrecognized input?

Section 5.1.1

nit: in the previous section we captialized this as "Auto-Bandwidth
Capability", but here (including the section heading) it is
"AUTO-BANDWIDTH-CAPABILITY".  Should they be consistent?

Section 5.2

   Future specification can define additional sub-TLVs.

I see that we see later that unrecognized sub-TLVs are ignored, but
would there be a case where we want to use a bit in the
AUTO-BANDWIDTH-CAPABILITY flags to negotiate support for a sub-TLV
(i.e., to confirm that the peer will understand it, instead of just
sending it and not knowing if it is understood)?

Section 5.2.1

It sounds like we should ignore values larger than 7 days as well
(rather than erroring out)?

Section 5.2.2, 5.2.3

I'd like to see a little bit more detail specified of the interaction
between (regular) Adjustment-{Interval,Threshold} and
Down-Adjustment-{Interval,Threshold}.  We do have this text about (e.g.)
"[t]he Adjustment-Interval sub-TLV specifies the time interval for both
upward and downward trend", which conveys the general intent, but I'm
not sure I have all the details about there being one default value,
that applies to both, and changes to the (regular) parameter continue to
apply to both, until an explicit Down- variant is seen, at which point
the control of the two parameters diverge permanently and they must
always be separately controlled.

Section 5.2.3.1

   o  Adjustment-Threshold: The absolute Adjustment-Threshold bandwidth
      value, encoded in IEEE floating point format (see

nit: I'd suggest that this is a bandwidth *difference* value (or offset),
pedantically speaking.  (The following paragraph is quite clear on the
actual usage, though, so this is nit-level.)  This comment applies to
basically all the threshold fields in the document, but I'll just make
it once, here.

Section 5.2.3.2

   o  Reserved: SHOULD be set to zero on transmission and MUST be
      ignored on receipt.

I think the formulation of "MUST be set to zero on transmission and
SHOULD be ignored on receipt" is more common.

   o  Percentage: The Adjustment-Threshold value (7 bits), encoded in
      percentage (an integer from 1 to 100).  The value 0 is considered
      to be invalid.  The default value is 5 percent.

I assume that the question of whether to allow sub-percentage
granularity came up, and don't want to revisit the WG's decision.  But
please confirm that it was discussed.

Also, are values over 100 also "invalid"?  What should the recipient do
upon receipt of an invalid value?

   If the percentage difference between the current MaxAvgBw and the
   current bandwidth reservation is greater than or less than or equal
   to the threshold percentage, the LSP bandwidth is adjusted to the
   current bandwidth demand (MaxAvgBw) (as long as the difference in the
   bandwidth is at least or above the Minimum-Threshold).

I'd suggest rewording to make the two criteria equal peers (e.g., "If X
and Y") rather than relegating the minimum-threshold to a parenthetical
that's easy to ignore.

Section 5.2.3.3

It would probably be good to reiterate here (and at other similar
locations) that this "is used to decide" only when there's a need for
different behavior in the upward and downard directions.

Also, nit-level, I think "overrides" is more appropriate than
"overwrites", since the non-Down- variant remains active for its
separate role.

Section 5.2.4.2

      per second.  The default maximum-bandwidth value is not set.

I guess effectively the default is FLOAT_MAX, inherited from RFC 5440.

Section 5.2.5.1

   o  Overflow-Threshold: The absolute Overflow-Threshold bandwidth
      value, encoded in IEEE floating point format (see
      [IEEE.754.1985]), expressed in bytes per second.  Refer to Section
      3.1.2 of [RFC3471] for a table of commonly used values.  If the
      increase of the current MaxAvgBw from the current bandwidth
      reservation is greater than or equal to the threshold value, the
      overflow condition is met.

nit: I'd suggest to s/increase/difference/, since (IIUC) the operation
here is "observed bandwidth remains above the (reservation plus)
threshold for <count> times", not "observed bandwidth increases in
successive reporting intervals".  This assumes that the
Adjustment-Interval is larger than <count> times the reporting interval,
of course.

Section 5.2.5.3

   o  Underflow-Threshold: The absolute Underflow-Threshold bandwidth
      value, encoded in IEEE floating point format (see
      [IEEE.754.1985]), expressed in bytes per second.  Refer to Section
      3.1.2 of [RFC3471] for a table of commonly used values.  If the
      decrease of the current MaxAvgBw from the current bandwidth
      reservation is greater than or equal to the threshold value, the
      underflow condition is met.

As above, I suggest s/decrease/difference/ (perhaps with an additional
indication that the magnitude of the difference is to be used, not the
signed difference).

Section 5.7

I'm not sure I understand why there's a need for an
auto-bandwidth-specific "overload" notification, as opposed to having
such messages suppressed as part of a more general overload condition.
But that doesn't mean there's not a need, of course, as I'm not very
familiar with this area!

Section 6.6

   An implementation MAY allow a limit to be placed on the rate of auto-
   bandwidth related messages sent by a PCEP speaker and received by a
   peer.  An implementation MAY also allow sending a notification when a
   PCEP speaker is overwhelmed or the rate of messages reach a
   threshold.

I don't want to revisit a WG consensus outcome, but I could see "SHOULD"
for "allow sending a notification", noting that it is "SHOULD allow
sending" and not "SHOULD send".

Section 7

   This document defines AUTO-BANDWIDTH-CAPABILITY TLV and AUTO-
   BANDWIDTH-ATTRIBUTES sub-TLVs which do not add any new security
   concerns beyond those already discussed in [RFC8231] and [RFC8281]

I'd suggest to qualify this as "do not add any substantial new security
concerns".  We did just in the previous section talk about how this
functionality could increase computational and operational load, which,
taken to an extreme, can affect availability and could be considered a
security consideration.

We could also perhaps give guidance about setting the min and max
bandwidth sub-TLVs to constrain automatic adjustment to be within a
known range and thus bound the extent of second-order effects on the
rest of the MPLS-TE domain.

Section 8.2

It might be good to say within what registry the sub-registry being
created is to be located.

Also, the last paragraph could perhaps be rephrased as "the initial
contents of the registry are empty, with all bits unassigned".

Section 9.2

I think that the RFC 7525 and 8253 references fall under the RECOMMENDED
guidance in Section 7, in which case per
https://www.ietf.org/about/groups/iesg/statements/normative-informative-references/
they should be classified as Normative references.  (It's probably also
good to cite RFC 7525 as BCP 195 and not just RFC 7525.)

The IEEE.754 reference is also normative since we use its wire encoding
(but it could practically be considered "well-known" at this point,
given its ubiquity).



From nobody Tue Sep 17 16:44:44 2019
Return-Path: <noreply@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DE0312018B; Tue, 17 Sep 2019 16:44:42 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Kaduk via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-pce-stateful-path-protection@ietf.org, Julien Meuric <julien.meuric@orange.com>, pce-chairs@ietf.org, julien.meuric@orange.com, pce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.101.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Benjamin Kaduk <kaduk@mit.edu>
Message-ID: <156876388231.17411.6094234033866939217.idtracker@ietfa.amsl.com>
Date: Tue, 17 Sep 2019 16:44:42 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/ETpG5Y6DkOCQ4pGr114bFd2aLRo>
Subject: [Pce] Benjamin Kaduk's Discuss on draft-ietf-pce-stateful-path-protection-10: (with DISCUSS and COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Sep 2019 23:44:42 -0000

Benjamin Kaduk has entered the following ballot position for
draft-ietf-pce-stateful-path-protection-10: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-path-protection/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

(1) draft-ietf-pce-association-group notes that "PCEP extensions that define
a new association type should clarify the relationship between the SVEC
object and the association type, if any".  Where do we do so for the
path protection association type?

(2) Section 3.2 says:

      Protection Type (PT): 6 bits - This field is as defined in
      Section 14.1 of [RFC4872] to indicate the LSP protection type in
      use.

There doesn't seem to be a registry created by RFC 4872 to track these
PT values, so I assume that the way to allocate a new value is
"standards-track RFC that Updates: RFC 4872".  Is that also the way to
allocate new PT values for PPAG usage?  How would someone updating RFC
4872 to allocate a new type know to consider/document whether it applies
for PPAG usage?

(3) In Section 4.3:

   A PCE can create/update working and protection LSPs independently.
   As specified in [I-D.ietf-pce-association-group], Association Groups
   can be created by both the PCE and the PCC.  Further, a PCE can

The requirement that source, destination, and tunnel ID of all LSPs
within a PPAG MUST be the same is new to this document, so I think we
need to specify error handling for when attempts to update LSPs
independently would violate that invariant (presumably in Section 4.5).

(4) In Section 6.3:

                                      IANA is requested to allocate new
   error values within the "PCEP-ERROR Object Error Types and Values"
   sub-registry of the PCEP Numbers registry, as follows:

The following table only lists Error-values.  What Error-type(s) should
they be associated with?

(5) We don't say which objects the PPAG TLV can appear in.  (Section 3.2
says "[t]he Path Protection Association TLV is an optional TLV for use
with the Path Protection Association Type", but it's hard to interpret
that as meaning "for use [only] with the ASSOCIATION object defined in
draft-ietf-pce-association-group", especially since there is a "path
protection association type" already (and it's a codepoint in the
"ASSOCIATION Type Field" registry).

(6) I'm not sure if a change to the document is needed here, but perhaps
some discussion is in order: we say that a given LSP can belong to more
than one PPAG, but only allow one PPAG TLV per [some context that
remains unclear; see (5)].  I don't have a good handle for whether these
two requirements are potentially in conflict: that is, whether a single
PPAG TLV would have to specify the flags that apply for both PPAGs that
a given LSP is a member of, or if the containing objects serve to scope
the PPAG TLV flags' interpretation.

(7) Do the Protection Type fields of the PPAG TLV in the various LSPs
that are members of the same PPAG need to match, in the same way that
the source/destination/tunnel-ID do?


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Section 1

   This document specifies a stateful PCEP extension to associate two or
   more LSPs for the purpose of setting up path protection.  The
   proposed extension covers the following scenarios:

nit: after publication, it doesn't really seem like a *proposed*
extension anymore.

Section 3.1

   LSPs are not associated by listing the other LSPs with which they
   interact, but rather by making them belong to an association group
   referred to as "Path Protection Association Group" (PPAG) in this
   document.  [...]

The first 2/3 of this sentence is a (true) generic statement about all
association groups, which exist outside of this document in a generic
fashion.  I strongly suggest rewording this to make clear that the PPAG
is the specific association (group) type used for this document's
functionality but that other association groups are possible.  The
current wording implies that the PPAG is the only association possible,
and it is just given a special name for this document's purposes.

   [I-D.ietf-pce-association-group] specifies the mechanism for the
   capability advertisement of the Association types supported by a PCEP
   speaker by defining a ASSOC-Type-List TLV to be carried within an
   OPEN object.  This capability exchange for the Association type
   described in this document (i.e.  Path Protection Association Type)
   MAY be done before using the policy association, i.e., the PCEP
   speaker MAY include the Path Protection Association Type (TBD1) in
   the ASSOC-Type-List TLV before using the PPAG in the PCEP messages.

Why is this only MAY and not MUST?

   This Association type is dynamic in nature and created by the PCC or

nit: is it the type that is dynamic or the associations of that type?

      Protecting (P): 1 bit - This bit is as defined in Section 14.1 of
      [RFC4872] to indicate if the LSP is working or protection LSP.

      Secondary (S): 1 bit - This bit is as defined in Section 14.1 of
      [RFC4872] to indicate if the LSP is primary or secondary LSP.  The
      S flag is ignored if the P flag is not set.

Just to check my understanding (no change expected to result): if P is
zero, the LSP is working, and thus we know that it's primary since it's
actively carrying traffic?

Section 3.2

nit(?) The section heading does not match the name of the TLV requested
in the IANA considerations, nor do we mention here that "PPAG TLV" is
synonymous with it.

   If the TLV is missing, it is considered that the LSP is the working
   LSP (i.e. as if P bit is unset).

Is this conditional on the LSP being part of a PPAG, or does it hold
generically as well?

Section 4.5

   As per the processing rules specified in section 5.4 of
   [I-D.ietf-pce-association-group], if a PCEP speaker does not support

There is no Section 5.4 in draft-ietf-pce-association-group-10;
presumably this was supposed to be Section 6.4?

   A given LSP MAY belong to more than one PPAG.  If there is a conflict

While I'm not arguing to remove this option, I'm also a bit confused at
how useful having a single LSP be in multiple PPAGs woud be, given the
need for source/destination/tunnel-ID to match.

   When the protection type is set to 1+1 or 1:N with N=1, there MUST be
   only one working LSP and one protection LSP within a PPAG.  If a PCEP
   speaker attempts to add another working/protection LSP, the PCEP peer
   MUST send PCErr with Error-Type 26 (Association Error)
   [I-D.ietf-pce-association-group] and Error-Value TBD4 (Attempt to add
   another working/protection LSP for Path Protection Association).

This seems to prevent a scenario where there's a need to change the
protection LSP and a desire to do so without removing the protected
nature of the working LSP.  Unless it's presumed that this could always
be done by updating the protection LSP and it would never be necessary
to create a new one?  (Similarly for 1:N, though maybe less severe.)

Section 5

   [RFC4872] introduces the concept and mechanisms to support the
   association of one LSP to another LSP across different RSVP - Traffic
   Engineering (RSVP-TE) sessions using ASSOCIATION and PROTECTION
   object.  The information in the PPAG TLV in PCEP as received from the
   PCE, is used to trigger the signalling of working LSP and protection
   LSP, with the Path Protection Association Flags mapped to the
   corresponding fields in the PROTECTION Object in RSVP-TE.

Just to check my understanding: this paragraph is saying that the
contents of the PPAG TLV received by the PCC is used as input to
populating the PROTECTION object that corresponds to the protection
group?

Section 10.2

I think RFCs 7525 and 8253 need to be normative (and please cite RFC
7525 as BCP 195).



From nobody Tue Sep 17 18:47:33 2019
Return-Path: <mahend.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAAA812012E; Tue, 17 Sep 2019 18:47:21 -0700 (PDT)
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 jgPUTJUPXU_Y; Tue, 17 Sep 2019 18:47:17 -0700 (PDT)
Received: from mail-oi1-x22b.google.com (mail-oi1-x22b.google.com [IPv6:2607:f8b0:4864:20::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C69212011E; Tue, 17 Sep 2019 18:47:17 -0700 (PDT)
Received: by mail-oi1-x22b.google.com with SMTP id o205so4582590oib.12; Tue, 17 Sep 2019 18:47:17 -0700 (PDT)
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=hRK67sFEI8y3RHWcE85tvXxfhGFSZ5auxVNuYD6EyIQ=; b=EOm3/1uMX/VcDyqNI1OJg5bisknuQ32z6EWpaWHiwjQsXaIedyt8Gxb/Jm+1ixjdQc IDTFZRtNDw+mCVzTZ0tnvNHMS1jQntoIdYvO/FRDzQSweb6DLbw5JUYcwxmT6jrbLzvF xgu5BBXtoVegDItlKjG4YqusijWaDvAZaCXeAlIHIBEc/ahVre7OfAy+f3tmmCjttiss /P4pA3BDCAsmInrtAT964MBA8sFU+V07g9BRBdoGy/W2h+3RXEv9bi/0A/hguncmy3Vu gLaLQwIc3zyCARE4C6jnej942ziKaOWE6Ym0/pO5ympzOIf9Cq1u4HSd43CRfjPNHzLm Icfw==
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=hRK67sFEI8y3RHWcE85tvXxfhGFSZ5auxVNuYD6EyIQ=; b=AoHdAkTGkWKD0LLDhDwTWiSKyT8M0MA6lfPoirrHTfahw6Hf1uu73habtABLoUvnBp oXxhihQAsZ4fKgSnS7xLmg/3YkyN07pAIskl9pmSRvi6KXeOdH6wjWly87vpU+nvYE5t +ppDO/1HdEln7OZbKn590MWgQsbxwVxbcBOA5sM4oBpxfKRkcXHYwOYC2RMg+AflVnmC 1jPoq8QDT4EBMpZTKbMUYO0WsBpnoGaWBwIvO9O5r4aP0QqkncnQsakzFYqNU2CsslDe MuS9Ev0biMuvHlJ9kioPR+TWt/i+3Gkum/PsZb0VV3H0kkDuFrN88AizpDP96eK/rrw4 6/JQ==
X-Gm-Message-State: APjAAAWz4g5vudUCTrJTpf1GWCmGINurp+pREmeKOiXkgeaJ/MFHZwgt dKnpj0LZvxIEnoNZhcRNiws5cMWdwei7mGwKcG8=
X-Google-Smtp-Source: APXvYqxLCXoviE31um1ZadFnbjjx1t60dFik+m0jUNrvXy4wQI//y3EwLP+iAbZVhMRHroME8GtUBLL+r5ZJU3RhNOU=
X-Received: by 2002:aca:578a:: with SMTP id l132mr720515oib.14.1568771236810;  Tue, 17 Sep 2019 18:47:16 -0700 (PDT)
MIME-Version: 1.0
References: <156849799383.3020.16398829686379997035.idtracker@ietfa.amsl.com> <CAM5Nu_zFe31wbGORGvYffxdGQtfMA+_U-twdRGndbUDObHfG9g@mail.gmail.com>
In-Reply-To: <CAM5Nu_zFe31wbGORGvYffxdGQtfMA+_U-twdRGndbUDObHfG9g@mail.gmail.com>
From: Mahend Negi <mahend.ietf@gmail.com>
Date: Wed, 18 Sep 2019 07:17:05 +0530
Message-ID: <CAM5Nu_xss5mDWdSFMSZeYTitScFSRwH-yQVA7NdjiGHpN5y2qA@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pce-stateful-path-protection@ietf.org, Julien Meuric <julien.meuric@orange.com>, pce-chairs <pce-chairs@ietf.org>, pce@ietf.org
Content-Type: multipart/alternative; boundary="0000000000004dd4010592ca0417"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/aMXfpfiVASWXUipT59OowyZCXGE>
Subject: Re: [Pce] Barry Leiba's No Objection on draft-ietf-pce-stateful-path-protection-10: (with COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Sep 2019 01:47:22 -0000

--0000000000004dd4010592ca0417
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Barry,

We mis-understood the last comment (section 4.5) and will updated as
suggested in the new version.

Thanks,
Mahendra


On Tue 17 Sep, 2019, 23:18 Mahend Negi, <mahend.ietf@gmail.com> wrote:

> Hi Barry,
>
> Many thanks for your review. Comments are incorporated in the working cop=
y
> (diff attached).
>
> For this one comment ->
> =3D=3D=3D
> =E2=80=94 Section 4.5 =E2=80=94
>
>    When the protection type is set to 1+1 or 1:N with N=3D1, there MUST b=
e
> =E2=80=A6
>    When the protection type is set to 1:N with N>1, there MUST be
>
> This is a style thing, so take it or leave it as you please =E2=80=94 it=
=E2=80=99s not
> wrong
> the way it=E2=80=99s written.  It=E2=80=99s just that the =E2=80=9C1:N wi=
th N=3D1=E2=80=9D and =E2=80=9C1:N with N>1=E2=80=9D
> distinction isn=E2=80=99t necessary, and I think it=E2=80=99s distracting=
 and invites
> uncertainty.  If you just made these like this:
>
> NEW
>    When the protection type is set to 1+1, there MUST be
> =E2=80=A6
>    When the protection type is set to 1:N, there MUST be
> END
>
> =E2=80=A6it would be equally correct, but also simpler and, I think, less=
 likely
> to be
> confusing.
> =3D=3D=3D
>
> The first sentence is for the case 1+1 and 1:1. Since RFC 4872 does
> not define an explicit state 1:1, it define 1:N only this wording was
> chosen. I have made this change "When the protection type is set to
> 1+1 or 1:1 (1:N with N=3D1)...".
>
>
> Thanks,
> Mahendra
>
> On Sun, Sep 15, 2019 at 3:23 AM Barry Leiba via Datatracker <
> noreply@ietf.org> wrote:
>
>> Barry Leiba has entered the following ballot position for
>> draft-ietf-pce-stateful-path-protection-10: No Objection
>>
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut this
>> introductory paragraph, however.)
>>
>>
>> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.htm=
l
>> for more information about IESG DISCUSS and COMMENT positions.
>>
>>
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-path-protection=
/
>>
>>
>>
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>>
>> Thanks for this document.  I have only editorial suggestions.  There's n=
o
>> need
>> to reply in any detail; just please consider adopting these suggestions.
>> Thanks.
>>
>> =E2=80=94 Abstract =E2=80=94
>>
>>    Multiprotocol Label Switching Traffic
>>    Engineering Label Switched Paths (MPLS LSP)
>>
>> Shouldn=E2=80=99t that be =E2=80=9C(MPLS-TE LSPs)=E2=80=9D?
>>
>> =E2=80=94 Section 1 =E2=80=94
>>
>>    [RFC5440] describes PCEP for communication between a Path Computation
>>    Client (PCC) and a PCE or between a pair of PCEs as per [RFC4655].  A
>>    PCE computes paths for MPLS-TE LSPs based on various constraints and
>>    optimization criteria.
>>
>> Even though you expanded some of these acronyms in the Abstract, they
>> have to
>> be expanded again in the Introduction, because the Abstract and the
>> document
>> itself each has to stand separately.
>>
>> That said, =E2=80=9CMPLS-TE=E2=80=9D and =E2=80=9CPCE=E2=80=9D are in th=
e RFC Editor=E2=80=99s list of common
>> acronyms
>> that don=E2=80=99t need expansion, so you can expand them or not, as you=
 please.
>> But
>> =E2=80=9CPCEP=E2=80=9D and =E2=80=9CLSP=E2=80=9D do need expansion here.
>>
>> You should also be consistent in using =E2=80=9CMPLS-TE=E2=80=9D (with t=
he hyphen), so
>> please
>> check the instances of =E2=80=9CMPLS TE=E2=80=9D without the hyphen, and=
 change them.
>> The RFC
>> Editor will flag this anyway, and it saves time during final editing and
>> AUTH48
>> if you fix it now.
>>
>>    It includes
>>    mechanisms to effect LSP state synchronization between PCCs and PCEs,
>>    delegation of control of LSPs to PCEs, and PCE control of timing and
>>    sequence of path computations within and across PCEP sessions and
>>    focuses on a model where LSPs are configured on the PCC and control
>>    over them is delegated to the PCE.
>>
>> This is a really long sentence, and can do with being split in two.  I
>> suggest
>> changing =E2=80=9Csessions and=E2=80=9D to =E2=80=9Csessions.  Stateful =
PCE=E2=80=9D.
>>
>>    Furthermore, a mechanism to
>>    dynamically instantiate LSPs on a PCC based on the requests from a
>>    stateful PCE or a controller using stateful PCE, is specified in
>>    [RFC8281].
>>
>> This reads oddly in passive voice, and you have a clear subject to use.
>> So I
>> suggest:
>>
>> NEW
>>    Furthermore, [RFC8281] specifies a mechanism to
>>    dynamically instantiate LSPs on a PCC based on the requests from a
>>    stateful PCE or a controller using stateful PCE.
>> END
>>
>>       computes the path for the protection LSP and update the PCC with
>>
>> =E2=80=9Cupdates=E2=80=9D
>>
>>    Note that protection LSP can be established (signaled) prior to the
>>    failure (in which case the LSP is said to be in standby mode
>>    [RFC4427] or a Primary LSP [RFC4872]) or post failure of the
>>    corresponding working LSP according to the operator choice/policy
>>    (known as secondary LSP [RFC4872]).
>>
>> =E2=80=9Ca protection LSP=E2=80=9D
>>
>> I suggest changing =E2=80=9Cpost failure=E2=80=9D to =E2=80=9Cafter fail=
ure=E2=80=9D, as it reads better.
>>
>> I=E2=80=99m not sure about the antecedent to =E2=80=9Caccording to the o=
perator
>> choice/policy=E2=80=9D.
>>  I think you mean that the establishment can be prior to failure or afte=
r
>> failure, according to operator choice or policy, is that right?  In that
>> case,
>> the sentence isn=E2=80=99t worded well.  May I suggest this?:
>>
>> NEW
>>    Note that a protection LSP can be established (signaled) before
>>    the failure (in which case the LSP is said to be in standby mode
>>    [RFC4427] or a Primary LSP [RFC4872]) or after failure of the
>>    corresponding working LSP (known as secondary LSP [RFC4872]).
>>    Whether to establish it before or after failure is according
>>    to operator choice or policy.
>> END
>>
>>    [I-D.ietf-pce-association-group] introduces a generic mechanism to
>>    create a grouping of LSPs which can then be used to define
>>    associations between a set of LSPs that is equally applicable to
>>    stateful PCE (active and passive modes) and stateless PCE.
>>
>> When I first read this I thought =E2=80=9Cthat is equally applicable=E2=
=80=9D applied to
>> the
>> set of LSPs.  I think you mean it to apply to the generic mechanism =E2=
=80=94
>> that is,
>> the generic mechanism is equally applicable.  Assuming that=E2=80=99s ri=
ght (note
>> inserted comma and split sentences):
>>
>> NEW
>>    [I-D.ietf-pce-association-group] introduces a generic mechanism to
>>    create a grouping of LSPs, which can then be used to define
>>    associations between a set of LSPs.  The mechanism is equally
>>    applicable to stateful PCE (active and passive modes) and stateless
>>    PCE.
>> END
>>
>> =E2=80=94 Section 3.2 =E2=80=94
>>
>>       Protecting (P): 1 bit - This bit is as defined in Section 14.1 of
>>       [RFC4872] to indicate if the LSP is working or protection LSP.
>>
>> At a minimum, make it =E2=80=9Ca working or protection LSP=E2=80=9D (add=
 the article).
>> Better still, =E2=80=9Ca working (0) or protection (1) LSP.=E2=80=9D  I =
know it says that
>> in
>> RFC 4872, but I think it makes sense to include that here.
>>
>>       Secondary (S): 1 bit - This bit is as defined in Section 14.1 of
>>       [RFC4872] to indicate if the LSP is primary or secondary LSP.  The
>>       S flag is ignored if the P flag is not set.
>>
>> Similarly, add the article =E2=80=9Ca=E2=80=9D, and also consider =E2=80=
=9Ca primary (0) or
>> secondary
>> (1) LSP.=E2=80=9D
>>
>>    If the TLV is missing, it is considered that the LSP is the working
>>    LSP (i.e. as if P bit is unset).
>>
>> Is this really =E2=80=9Cthe working LSP=E2=80=9D, or should it be =E2=80=
=9Ca working LSP=E2=80=9D?
>>
>> =E2=80=94 Section 4 =E2=80=94
>>
>>    An LSP is associated with other LSPs with which they interact by
>>    adding them to a common association group via the ASSOCIATION object.
>>
>> The number disagreement here is confusing, so I=E2=80=99m not sure what =
you mean
>> to
>> say.  I think you mean that the other LSPs are added to the group, in
>> which
>> case change =E2=80=9Cthey interact=E2=80=9D to =E2=80=9Cit interacts=E2=
=80=9D.
>>
>> =E2=80=94 Section 4.2 =E2=80=94
>>
>>    A PCC can associate a set of LSPs under its control for path
>>    protection purpose.
>>
>> =E2=80=9Cpurposes=E2=80=9D
>>
>>    PCC reports the change in association to PCE(s) via Path Computation
>>    Report (PCRpt) message.
>>
>> Either =E2=80=9Ca Path Computation Report (PCRpt) message=E2=80=9D or =
=E2=80=9CPath Computation
>> Report
>> (PCRpt) messages=E2=80=9D.
>>
>>    It is expected that both working and protection LSP are delegated
>>
>> =E2=80=9CLSPs=E2=80=9D
>>
>> =E2=80=94 Section 4.5 =E2=80=94
>>
>>    When the protection type is set to 1+1 or 1:N with N=3D1, there MUST =
be
>> =E2=80=A6
>>    When the protection type is set to 1:N with N>1, there MUST be
>>
>> This is a style thing, so take it or leave it as you please =E2=80=94 it=
=E2=80=99s not
>> wrong
>> the way it=E2=80=99s written.  It=E2=80=99s just that the =E2=80=9C1:N w=
ith N=3D1=E2=80=9D and =E2=80=9C1:N with
>> N>1=E2=80=9D
>> distinction isn=E2=80=99t necessary, and I think it=E2=80=99s distractin=
g and invites
>> uncertainty.  If you just made these like this:
>>
>> NEW
>>    When the protection type is set to 1+1, there MUST be
>> =E2=80=A6
>>    When the protection type is set to 1:N, there MUST be
>> END
>>
>> =E2=80=A6it would be equally correct, but also simpler and, I think, les=
s likely
>> to be
>> confusing.
>>
>> =E2=80=94 Section 5 =E2=80=94
>>
>>    association of one LSP to another LSP across different RSVP - Traffic
>>    Engineering (RSVP-TE) sessions
>>
>> Is it typical to have that hyphen there in the first line?  Isn=E2=80=99=
t it more
>> typical to write =E2=80=9CRSVP Traffic Engineering (RSVP-TE)=E2=80=9D wi=
thout the extra
>> hyphen?
>>
>>    The information in the PPAG TLV in PCEP as received from the
>>    PCE, is used to trigger
>>
>> Remove the comma.
>>
>>
>>

--0000000000004dd4010592ca0417
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div>Hi=C2=A0Barry,</div><div dir=3D"auto"><br></div><div=
 dir=3D"auto">We mis-understood the last comment (section 4.5) and will upd=
ated as suggested in the new version.</div><div dir=3D"auto"><br></div><div=
 dir=3D"auto">Thanks,</div><div dir=3D"auto">Mahendra</div><div dir=3D"auto=
"><br><br><div class=3D"gmail_quote" dir=3D"auto"><div dir=3D"ltr" class=3D=
"gmail_attr">On Tue 17 Sep, 2019, 23:18 Mahend Negi, &lt;<a href=3D"mailto:=
mahend.ietf@gmail.com">mahend.ietf@gmail.com</a>&gt; wrote:<br></div><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex"><div dir=3D"ltr"><div>Hi Barry,</div><div><br></di=
v><div>Many thanks for your review. Comments are incorporated in the workin=
g copy (diff attached).</div><div><br></div><div>For this one comment -&gt;=
</div><div>=3D=3D=3D<br>=E2=80=94 Section 4.5 =E2=80=94<br><br>=C2=A0 =C2=
=A0When the protection type is set to 1+1 or 1:N with N=3D1, there MUST be<=
br>=E2=80=A6<br>=C2=A0 =C2=A0When the protection type is set to 1:N with N&=
gt;1, there MUST be<br><br>This is a style thing, so take it or leave it as=
 you please =E2=80=94 it=E2=80=99s not wrong<br>the way it=E2=80=99s writte=
n.=C2=A0 It=E2=80=99s just that the =E2=80=9C1:N with N=3D1=E2=80=9D and =
=E2=80=9C1:N with N&gt;1=E2=80=9D<br>distinction isn=E2=80=99t necessary, a=
nd I think it=E2=80=99s distracting and invites<br>uncertainty.=C2=A0 If yo=
u just made these like this:<br><br>NEW<br>=C2=A0 =C2=A0When the protection=
 type is set to 1+1, there MUST be<br>=E2=80=A6<br>=C2=A0 =C2=A0When the pr=
otection type is set to 1:N, there MUST be<br>END<br><br>=E2=80=A6it would =
be equally correct, but also simpler and, I think, less likely to be<br>con=
fusing.<br>=3D=3D=3D<br><br>The first sentence is for the case 1+1 and 1:1.=
 Since RFC 4872 does<br>not define an explicit state 1:1, it define 1:N onl=
y this wording was<br>chosen. I have made this change &quot;When the protec=
tion type is set to<br>1+1 or 1:1 (1:N with N=3D1)...&quot;.</div><div><br>=
</div><div><br></div><div>Thanks,</div><div>Mahendra</div></div><br><div cl=
ass=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, Sep 15, 2=
019 at 3:23 AM Barry Leiba via Datatracker &lt;<a href=3D"mailto:noreply@ie=
tf.org" target=3D"_blank" rel=3D"noreferrer">noreply@ietf.org</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">Barry Leiba ha=
s entered the following ballot position for<br>
draft-ietf-pce-stateful-path-protection-10: No Objection<br>
<br>
When responding, please keep the subject line intact and reply to all<br>
email addresses included in the To and CC lines. (Feel free to cut this<br>
introductory paragraph, however.)<br>
<br>
<br>
Please refer to <a href=3D"https://www.ietf.org/iesg/statement/discuss-crit=
eria.html" rel=3D"noreferrer noreferrer" target=3D"_blank">https://www.ietf=
.org/iesg/statement/discuss-criteria.html</a><br>
for more information about IESG DISCUSS and COMMENT positions.<br>
<br>
<br>
The document, along with other ballot positions, can be found here:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-path-pr=
otection/" rel=3D"noreferrer noreferrer" target=3D"_blank">https://datatrac=
ker.ietf.org/doc/draft-ietf-pce-stateful-path-protection/</a><br>
<br>
<br>
<br>
----------------------------------------------------------------------<br>
COMMENT:<br>
----------------------------------------------------------------------<br>
<br>
Thanks for this document.=C2=A0 I have only editorial suggestions.=C2=A0 Th=
ere&#39;s no need<br>
to reply in any detail; just please consider adopting these suggestions. <b=
r>
Thanks.<br>
<br>
=E2=80=94 Abstract =E2=80=94<br>
<br>
=C2=A0 =C2=A0Multiprotocol Label Switching Traffic<br>
=C2=A0 =C2=A0Engineering Label Switched Paths (MPLS LSP)<br>
<br>
Shouldn=E2=80=99t that be =E2=80=9C(MPLS-TE LSPs)=E2=80=9D?<br>
<br>
=E2=80=94 Section 1 =E2=80=94<br>
<br>
=C2=A0 =C2=A0[RFC5440] describes PCEP for communication between a Path Comp=
utation<br>
=C2=A0 =C2=A0Client (PCC) and a PCE or between a pair of PCEs as per [RFC46=
55].=C2=A0 A<br>
=C2=A0 =C2=A0PCE computes paths for MPLS-TE LSPs based on various constrain=
ts and<br>
=C2=A0 =C2=A0optimization criteria.<br>
<br>
Even though you expanded some of these acronyms in the Abstract, they have =
to<br>
be expanded again in the Introduction, because the Abstract and the documen=
t<br>
itself each has to stand separately.<br>
<br>
That said, =E2=80=9CMPLS-TE=E2=80=9D and =E2=80=9CPCE=E2=80=9D are in the R=
FC Editor=E2=80=99s list of common acronyms<br>
that don=E2=80=99t need expansion, so you can expand them or not, as you pl=
ease.=C2=A0 But<br>
=E2=80=9CPCEP=E2=80=9D and =E2=80=9CLSP=E2=80=9D do need expansion here.<br=
>
<br>
You should also be consistent in using =E2=80=9CMPLS-TE=E2=80=9D (with the =
hyphen), so please<br>
check the instances of =E2=80=9CMPLS TE=E2=80=9D without the hyphen, and ch=
ange them.=C2=A0 The RFC<br>
Editor will flag this anyway, and it saves time during final editing and AU=
TH48<br>
if you fix it now.<br>
<br>
=C2=A0 =C2=A0It includes<br>
=C2=A0 =C2=A0mechanisms to effect LSP state synchronization between PCCs an=
d PCEs,<br>
=C2=A0 =C2=A0delegation of control of LSPs to PCEs, and PCE control of timi=
ng and<br>
=C2=A0 =C2=A0sequence of path computations within and across PCEP sessions =
and<br>
=C2=A0 =C2=A0focuses on a model where LSPs are configured on the PCC and co=
ntrol<br>
=C2=A0 =C2=A0over them is delegated to the PCE.<br>
<br>
This is a really long sentence, and can do with being split in two.=C2=A0 I=
 suggest<br>
changing =E2=80=9Csessions and=E2=80=9D to =E2=80=9Csessions.=C2=A0 Statefu=
l PCE=E2=80=9D.<br>
<br>
=C2=A0 =C2=A0Furthermore, a mechanism to<br>
=C2=A0 =C2=A0dynamically instantiate LSPs on a PCC based on the requests fr=
om a<br>
=C2=A0 =C2=A0stateful PCE or a controller using stateful PCE, is specified =
in<br>
=C2=A0 =C2=A0[RFC8281].<br>
<br>
This reads oddly in passive voice, and you have a clear subject to use.=C2=
=A0 So I<br>
suggest:<br>
<br>
NEW<br>
=C2=A0 =C2=A0Furthermore, [RFC8281] specifies a mechanism to<br>
=C2=A0 =C2=A0dynamically instantiate LSPs on a PCC based on the requests fr=
om a<br>
=C2=A0 =C2=A0stateful PCE or a controller using stateful PCE.<br>
END<br>
<br>
=C2=A0 =C2=A0 =C2=A0 computes the path for the protection LSP and update th=
e PCC with<br>
<br>
=E2=80=9Cupdates=E2=80=9D<br>
<br>
=C2=A0 =C2=A0Note that protection LSP can be established (signaled) prior t=
o the<br>
=C2=A0 =C2=A0failure (in which case the LSP is said to be in standby mode<b=
r>
=C2=A0 =C2=A0[RFC4427] or a Primary LSP [RFC4872]) or post failure of the<b=
r>
=C2=A0 =C2=A0corresponding working LSP according to the operator choice/pol=
icy<br>
=C2=A0 =C2=A0(known as secondary LSP [RFC4872]).<br>
<br>
=E2=80=9Ca protection LSP=E2=80=9D<br>
<br>
I suggest changing =E2=80=9Cpost failure=E2=80=9D to =E2=80=9Cafter failure=
=E2=80=9D, as it reads better.<br>
<br>
I=E2=80=99m not sure about the antecedent to =E2=80=9Caccording to the oper=
ator choice/policy=E2=80=9D.<br>
=C2=A0I think you mean that the establishment can be prior to failure or af=
ter<br>
failure, according to operator choice or policy, is that right?=C2=A0 In th=
at case,<br>
the sentence isn=E2=80=99t worded well.=C2=A0 May I suggest this?:<br>
<br>
NEW<br>
=C2=A0 =C2=A0Note that a protection LSP can be established (signaled) befor=
e<br>
=C2=A0 =C2=A0the failure (in which case the LSP is said to be in standby mo=
de<br>
=C2=A0 =C2=A0[RFC4427] or a Primary LSP [RFC4872]) or after failure of the<=
br>
=C2=A0 =C2=A0corresponding working LSP (known as secondary LSP [RFC4872]).<=
br>
=C2=A0 =C2=A0Whether to establish it before or after failure is according<b=
r>
=C2=A0 =C2=A0to operator choice or policy.<br>
END<br>
<br>
=C2=A0 =C2=A0[I-D.ietf-pce-association-group] introduces a generic mechanis=
m to<br>
=C2=A0 =C2=A0create a grouping of LSPs which can then be used to define<br>
=C2=A0 =C2=A0associations between a set of LSPs that is equally applicable =
to<br>
=C2=A0 =C2=A0stateful PCE (active and passive modes) and stateless PCE.<br>
<br>
When I first read this I thought =E2=80=9Cthat is equally applicable=E2=80=
=9D applied to the<br>
set of LSPs.=C2=A0 I think you mean it to apply to the generic mechanism =
=E2=80=94 that is,<br>
the generic mechanism is equally applicable.=C2=A0 Assuming that=E2=80=99s =
right (note<br>
inserted comma and split sentences):<br>
<br>
NEW<br>
=C2=A0 =C2=A0[I-D.ietf-pce-association-group] introduces a generic mechanis=
m to<br>
=C2=A0 =C2=A0create a grouping of LSPs, which can then be used to define<br=
>
=C2=A0 =C2=A0associations between a set of LSPs.=C2=A0 The mechanism is equ=
ally<br>
=C2=A0 =C2=A0applicable to stateful PCE (active and passive modes) and stat=
eless<br>
=C2=A0 =C2=A0PCE.<br>
END<br>
<br>
=E2=80=94 Section 3.2 =E2=80=94<br>
<br>
=C2=A0 =C2=A0 =C2=A0 Protecting (P): 1 bit - This bit is as defined in Sect=
ion 14.1 of<br>
=C2=A0 =C2=A0 =C2=A0 [RFC4872] to indicate if the LSP is working or protect=
ion LSP.<br>
<br>
At a minimum, make it =E2=80=9Ca working or protection LSP=E2=80=9D (add th=
e article).<br>
Better still, =E2=80=9Ca working (0) or protection (1) LSP.=E2=80=9D=C2=A0 =
I know it says that in<br>
RFC 4872, but I think it makes sense to include that here.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 Secondary (S): 1 bit - This bit is as defined in Secti=
on 14.1 of<br>
=C2=A0 =C2=A0 =C2=A0 [RFC4872] to indicate if the LSP is primary or seconda=
ry LSP.=C2=A0 The<br>
=C2=A0 =C2=A0 =C2=A0 S flag is ignored if the P flag is not set.<br>
<br>
Similarly, add the article =E2=80=9Ca=E2=80=9D, and also consider =E2=80=9C=
a primary (0) or secondary<br>
(1) LSP.=E2=80=9D<br>
<br>
=C2=A0 =C2=A0If the TLV is missing, it is considered that the LSP is the wo=
rking<br>
=C2=A0 =C2=A0LSP (i.e. as if P bit is unset).<br>
<br>
Is this really =E2=80=9Cthe working LSP=E2=80=9D, or should it be =E2=80=9C=
a working LSP=E2=80=9D?<br>
<br>
=E2=80=94 Section 4 =E2=80=94<br>
<br>
=C2=A0 =C2=A0An LSP is associated with other LSPs with which they interact =
by<br>
=C2=A0 =C2=A0adding them to a common association group via the ASSOCIATION =
object.<br>
<br>
The number disagreement here is confusing, so I=E2=80=99m not sure what you=
 mean to<br>
say.=C2=A0 I think you mean that the other LSPs are added to the group, in =
which<br>
case change =E2=80=9Cthey interact=E2=80=9D to =E2=80=9Cit interacts=E2=80=
=9D.<br>
<br>
=E2=80=94 Section 4.2 =E2=80=94<br>
<br>
=C2=A0 =C2=A0A PCC can associate a set of LSPs under its control for path<b=
r>
=C2=A0 =C2=A0protection purpose.<br>
<br>
=E2=80=9Cpurposes=E2=80=9D<br>
<br>
=C2=A0 =C2=A0PCC reports the change in association to PCE(s) via Path Compu=
tation<br>
=C2=A0 =C2=A0Report (PCRpt) message.<br>
<br>
Either =E2=80=9Ca Path Computation Report (PCRpt) message=E2=80=9D or =E2=
=80=9CPath Computation Report<br>
(PCRpt) messages=E2=80=9D.<br>
<br>
=C2=A0 =C2=A0It is expected that both working and protection LSP are delega=
ted<br>
<br>
=E2=80=9CLSPs=E2=80=9D<br>
<br>
=E2=80=94 Section 4.5 =E2=80=94<br>
<br>
=C2=A0 =C2=A0When the protection type is set to 1+1 or 1:N with N=3D1, ther=
e MUST be<br>
=E2=80=A6<br>
=C2=A0 =C2=A0When the protection type is set to 1:N with N&gt;1, there MUST=
 be<br>
<br>
This is a style thing, so take it or leave it as you please =E2=80=94 it=E2=
=80=99s not wrong<br>
the way it=E2=80=99s written.=C2=A0 It=E2=80=99s just that the =E2=80=9C1:N=
 with N=3D1=E2=80=9D and =E2=80=9C1:N with N&gt;1=E2=80=9D<br>
distinction isn=E2=80=99t necessary, and I think it=E2=80=99s distracting a=
nd invites<br>
uncertainty.=C2=A0 If you just made these like this:<br>
<br>
NEW<br>
=C2=A0 =C2=A0When the protection type is set to 1+1, there MUST be<br>
=E2=80=A6<br>
=C2=A0 =C2=A0When the protection type is set to 1:N, there MUST be<br>
END<br>
<br>
=E2=80=A6it would be equally correct, but also simpler and, I think, less l=
ikely to be<br>
confusing.<br>
<br>
=E2=80=94 Section 5 =E2=80=94<br>
<br>
=C2=A0 =C2=A0association of one LSP to another LSP across different RSVP - =
Traffic<br>
=C2=A0 =C2=A0Engineering (RSVP-TE) sessions<br>
<br>
Is it typical to have that hyphen there in the first line?=C2=A0 Isn=E2=80=
=99t it more<br>
typical to write =E2=80=9CRSVP Traffic Engineering (RSVP-TE)=E2=80=9D witho=
ut the extra hyphen?<br>
<br>
=C2=A0 =C2=A0The information in the PPAG TLV in PCEP as received from the<b=
r>
=C2=A0 =C2=A0PCE, is used to trigger<br>
<br>
Remove the comma.<br>
<br>
<br>
</blockquote></div>
</blockquote></div></div></div>

--0000000000004dd4010592ca0417--


From nobody Tue Sep 17 20:48:09 2019
Return-Path: <barryleiba@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C60B4120180; Tue, 17 Sep 2019 20:47:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.922
X-Spam-Level: 
X-Spam-Status: No, score=-1.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.026, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hlO9YRYgpOc8; Tue, 17 Sep 2019 20:47:57 -0700 (PDT)
Received: from mail-io1-f68.google.com (mail-io1-f68.google.com [209.85.166.68]) (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 7C7051200A3; Tue, 17 Sep 2019 20:47:57 -0700 (PDT)
Received: by mail-io1-f68.google.com with SMTP id r26so12781292ioh.8; Tue, 17 Sep 2019 20:47:57 -0700 (PDT)
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:content-transfer-encoding; bh=LhCgCA9tXqIprfK82oO6tGfHDdBAy+AMZ/gQCT+vuVE=; b=T1kLYUROS/sTo6GOEQ9eP9nnVURdi8wn9XaBEE+nJR7ylHtfTjZ4oEdYT7JbVdkMCB Xr2+fBoc+A+HJO3Aip0DO8s0fsBTsAfbmJReHD867BaVeNAABNHJ9h4T/X5pJAFN2tfG e9LD3bDjgxNTLfOVAxnBv3gu0hYtmUmTl90d2Dvu9IlfFGLClz3Cm/rXqszTPuzFsD0X OZtS8MNoJ25GX462FFsVWCNB8I//zPFanh3XNpGqmRB4piVmlRQXkW7xmq5+Y3PnGbrK EpaNnt+achizG6cFNFBMusVrBN4TGS1mBSx0LGNmejA7i6t5VBVOitw4IXM7pF6R7p1C ZdGA==
X-Gm-Message-State: APjAAAVYINXOmPo5DK81FGQITYMiQw61Alc2hsgAPDSf1gCbxFC/+wiY aR/MIS9+GJYgfUhSVwPxEr2L+a0LFcTxMBaptXA=
X-Google-Smtp-Source: APXvYqw6zrk3TXBPYK95Ew1Gn0Zo5zrY61Ec/uMmzUDkwU5u4fa+HQ0Yg/vSQxs5k+fywyqHU63c/1qrrQgKrusndhg=
X-Received: by 2002:a5d:96c6:: with SMTP id r6mr2893111iol.266.1568778476511;  Tue, 17 Sep 2019 20:47:56 -0700 (PDT)
MIME-Version: 1.0
References: <156849799383.3020.16398829686379997035.idtracker@ietfa.amsl.com> <CAM5Nu_zFe31wbGORGvYffxdGQtfMA+_U-twdRGndbUDObHfG9g@mail.gmail.com> <CAM5Nu_xss5mDWdSFMSZeYTitScFSRwH-yQVA7NdjiGHpN5y2qA@mail.gmail.com>
In-Reply-To: <CAM5Nu_xss5mDWdSFMSZeYTitScFSRwH-yQVA7NdjiGHpN5y2qA@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Tue, 17 Sep 2019 20:47:44 -0700
Message-ID: <CALaySJ+aBdjxLCsL+Mua63o2e2wtnLyxLFEgTVNq_Qox-XBqww@mail.gmail.com>
To: Mahend Negi <mahend.ietf@gmail.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pce-stateful-path-protection@ietf.org, Julien Meuric <julien.meuric@orange.com>, pce-chairs <pce-chairs@ietf.org>, pce@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/16HnoJVQ3sTzG6wIe1IXkPlJ7jk>
Subject: Re: [Pce] Barry Leiba's No Objection on draft-ietf-pce-stateful-path-protection-10: (with COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Sep 2019 03:48:00 -0000

Thanks!

b

On Tue, Sep 17, 2019 at 6:47 PM Mahend Negi <mahend.ietf@gmail.com> wrote:
>
> Hi Barry,
>
> We mis-understood the last comment (section 4.5) and will updated as sugg=
ested in the new version.
>
> Thanks,
> Mahendra
>
>
> On Tue 17 Sep, 2019, 23:18 Mahend Negi, <mahend.ietf@gmail.com> wrote:
>>
>> Hi Barry,
>>
>> Many thanks for your review. Comments are incorporated in the working co=
py (diff attached).
>>
>> For this one comment ->
>> =3D=3D=3D
>> =E2=80=94 Section 4.5 =E2=80=94
>>
>>    When the protection type is set to 1+1 or 1:N with N=3D1, there MUST =
be
>> =E2=80=A6
>>    When the protection type is set to 1:N with N>1, there MUST be
>>
>> This is a style thing, so take it or leave it as you please =E2=80=94 it=
=E2=80=99s not wrong
>> the way it=E2=80=99s written.  It=E2=80=99s just that the =E2=80=9C1:N w=
ith N=3D1=E2=80=9D and =E2=80=9C1:N with N>1=E2=80=9D
>> distinction isn=E2=80=99t necessary, and I think it=E2=80=99s distractin=
g and invites
>> uncertainty.  If you just made these like this:
>>
>> NEW
>>    When the protection type is set to 1+1, there MUST be
>> =E2=80=A6
>>    When the protection type is set to 1:N, there MUST be
>> END
>>
>> =E2=80=A6it would be equally correct, but also simpler and, I think, les=
s likely to be
>> confusing.
>> =3D=3D=3D
>>
>> The first sentence is for the case 1+1 and 1:1. Since RFC 4872 does
>> not define an explicit state 1:1, it define 1:N only this wording was
>> chosen. I have made this change "When the protection type is set to
>> 1+1 or 1:1 (1:N with N=3D1)...".
>>
>>
>> Thanks,
>> Mahendra
>>
>> On Sun, Sep 15, 2019 at 3:23 AM Barry Leiba via Datatracker <noreply@iet=
f.org> wrote:
>>>
>>> Barry Leiba has entered the following ballot position for
>>> draft-ietf-pce-stateful-path-protection-10: No Objection
>>>
>>> When responding, please keep the subject line intact and reply to all
>>> email addresses included in the To and CC lines. (Feel free to cut this
>>> introductory paragraph, however.)
>>>
>>>
>>> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.ht=
ml
>>> for more information about IESG DISCUSS and COMMENT positions.
>>>
>>>
>>> The document, along with other ballot positions, can be found here:
>>> https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-path-protectio=
n/
>>>
>>>
>>>
>>> ----------------------------------------------------------------------
>>> COMMENT:
>>> ----------------------------------------------------------------------
>>>
>>> Thanks for this document.  I have only editorial suggestions.  There's =
no need
>>> to reply in any detail; just please consider adopting these suggestions=
.
>>> Thanks.
>>>
>>> =E2=80=94 Abstract =E2=80=94
>>>
>>>    Multiprotocol Label Switching Traffic
>>>    Engineering Label Switched Paths (MPLS LSP)
>>>
>>> Shouldn=E2=80=99t that be =E2=80=9C(MPLS-TE LSPs)=E2=80=9D?
>>>
>>> =E2=80=94 Section 1 =E2=80=94
>>>
>>>    [RFC5440] describes PCEP for communication between a Path Computatio=
n
>>>    Client (PCC) and a PCE or between a pair of PCEs as per [RFC4655].  =
A
>>>    PCE computes paths for MPLS-TE LSPs based on various constraints and
>>>    optimization criteria.
>>>
>>> Even though you expanded some of these acronyms in the Abstract, they h=
ave to
>>> be expanded again in the Introduction, because the Abstract and the doc=
ument
>>> itself each has to stand separately.
>>>
>>> That said, =E2=80=9CMPLS-TE=E2=80=9D and =E2=80=9CPCE=E2=80=9D are in t=
he RFC Editor=E2=80=99s list of common acronyms
>>> that don=E2=80=99t need expansion, so you can expand them or not, as yo=
u please.  But
>>> =E2=80=9CPCEP=E2=80=9D and =E2=80=9CLSP=E2=80=9D do need expansion here=
.
>>>
>>> You should also be consistent in using =E2=80=9CMPLS-TE=E2=80=9D (with =
the hyphen), so please
>>> check the instances of =E2=80=9CMPLS TE=E2=80=9D without the hyphen, an=
d change them.  The RFC
>>> Editor will flag this anyway, and it saves time during final editing an=
d AUTH48
>>> if you fix it now.
>>>
>>>    It includes
>>>    mechanisms to effect LSP state synchronization between PCCs and PCEs=
,
>>>    delegation of control of LSPs to PCEs, and PCE control of timing and
>>>    sequence of path computations within and across PCEP sessions and
>>>    focuses on a model where LSPs are configured on the PCC and control
>>>    over them is delegated to the PCE.
>>>
>>> This is a really long sentence, and can do with being split in two.  I =
suggest
>>> changing =E2=80=9Csessions and=E2=80=9D to =E2=80=9Csessions.  Stateful=
 PCE=E2=80=9D.
>>>
>>>    Furthermore, a mechanism to
>>>    dynamically instantiate LSPs on a PCC based on the requests from a
>>>    stateful PCE or a controller using stateful PCE, is specified in
>>>    [RFC8281].
>>>
>>> This reads oddly in passive voice, and you have a clear subject to use.=
  So I
>>> suggest:
>>>
>>> NEW
>>>    Furthermore, [RFC8281] specifies a mechanism to
>>>    dynamically instantiate LSPs on a PCC based on the requests from a
>>>    stateful PCE or a controller using stateful PCE.
>>> END
>>>
>>>       computes the path for the protection LSP and update the PCC with
>>>
>>> =E2=80=9Cupdates=E2=80=9D
>>>
>>>    Note that protection LSP can be established (signaled) prior to the
>>>    failure (in which case the LSP is said to be in standby mode
>>>    [RFC4427] or a Primary LSP [RFC4872]) or post failure of the
>>>    corresponding working LSP according to the operator choice/policy
>>>    (known as secondary LSP [RFC4872]).
>>>
>>> =E2=80=9Ca protection LSP=E2=80=9D
>>>
>>> I suggest changing =E2=80=9Cpost failure=E2=80=9D to =E2=80=9Cafter fai=
lure=E2=80=9D, as it reads better.
>>>
>>> I=E2=80=99m not sure about the antecedent to =E2=80=9Caccording to the =
operator choice/policy=E2=80=9D.
>>>  I think you mean that the establishment can be prior to failure or aft=
er
>>> failure, according to operator choice or policy, is that right?  In tha=
t case,
>>> the sentence isn=E2=80=99t worded well.  May I suggest this?:
>>>
>>> NEW
>>>    Note that a protection LSP can be established (signaled) before
>>>    the failure (in which case the LSP is said to be in standby mode
>>>    [RFC4427] or a Primary LSP [RFC4872]) or after failure of the
>>>    corresponding working LSP (known as secondary LSP [RFC4872]).
>>>    Whether to establish it before or after failure is according
>>>    to operator choice or policy.
>>> END
>>>
>>>    [I-D.ietf-pce-association-group] introduces a generic mechanism to
>>>    create a grouping of LSPs which can then be used to define
>>>    associations between a set of LSPs that is equally applicable to
>>>    stateful PCE (active and passive modes) and stateless PCE.
>>>
>>> When I first read this I thought =E2=80=9Cthat is equally applicable=E2=
=80=9D applied to the
>>> set of LSPs.  I think you mean it to apply to the generic mechanism =E2=
=80=94 that is,
>>> the generic mechanism is equally applicable.  Assuming that=E2=80=99s r=
ight (note
>>> inserted comma and split sentences):
>>>
>>> NEW
>>>    [I-D.ietf-pce-association-group] introduces a generic mechanism to
>>>    create a grouping of LSPs, which can then be used to define
>>>    associations between a set of LSPs.  The mechanism is equally
>>>    applicable to stateful PCE (active and passive modes) and stateless
>>>    PCE.
>>> END
>>>
>>> =E2=80=94 Section 3.2 =E2=80=94
>>>
>>>       Protecting (P): 1 bit - This bit is as defined in Section 14.1 of
>>>       [RFC4872] to indicate if the LSP is working or protection LSP.
>>>
>>> At a minimum, make it =E2=80=9Ca working or protection LSP=E2=80=9D (ad=
d the article).
>>> Better still, =E2=80=9Ca working (0) or protection (1) LSP.=E2=80=9D  I=
 know it says that in
>>> RFC 4872, but I think it makes sense to include that here.
>>>
>>>       Secondary (S): 1 bit - This bit is as defined in Section 14.1 of
>>>       [RFC4872] to indicate if the LSP is primary or secondary LSP.  Th=
e
>>>       S flag is ignored if the P flag is not set.
>>>
>>> Similarly, add the article =E2=80=9Ca=E2=80=9D, and also consider =E2=
=80=9Ca primary (0) or secondary
>>> (1) LSP.=E2=80=9D
>>>
>>>    If the TLV is missing, it is considered that the LSP is the working
>>>    LSP (i.e. as if P bit is unset).
>>>
>>> Is this really =E2=80=9Cthe working LSP=E2=80=9D, or should it be =E2=
=80=9Ca working LSP=E2=80=9D?
>>>
>>> =E2=80=94 Section 4 =E2=80=94
>>>
>>>    An LSP is associated with other LSPs with which they interact by
>>>    adding them to a common association group via the ASSOCIATION object=
.
>>>
>>> The number disagreement here is confusing, so I=E2=80=99m not sure what=
 you mean to
>>> say.  I think you mean that the other LSPs are added to the group, in w=
hich
>>> case change =E2=80=9Cthey interact=E2=80=9D to =E2=80=9Cit interacts=E2=
=80=9D.
>>>
>>> =E2=80=94 Section 4.2 =E2=80=94
>>>
>>>    A PCC can associate a set of LSPs under its control for path
>>>    protection purpose.
>>>
>>> =E2=80=9Cpurposes=E2=80=9D
>>>
>>>    PCC reports the change in association to PCE(s) via Path Computation
>>>    Report (PCRpt) message.
>>>
>>> Either =E2=80=9Ca Path Computation Report (PCRpt) message=E2=80=9D or =
=E2=80=9CPath Computation Report
>>> (PCRpt) messages=E2=80=9D.
>>>
>>>    It is expected that both working and protection LSP are delegated
>>>
>>> =E2=80=9CLSPs=E2=80=9D
>>>
>>> =E2=80=94 Section 4.5 =E2=80=94
>>>
>>>    When the protection type is set to 1+1 or 1:N with N=3D1, there MUST=
 be
>>> =E2=80=A6
>>>    When the protection type is set to 1:N with N>1, there MUST be
>>>
>>> This is a style thing, so take it or leave it as you please =E2=80=94 i=
t=E2=80=99s not wrong
>>> the way it=E2=80=99s written.  It=E2=80=99s just that the =E2=80=9C1:N =
with N=3D1=E2=80=9D and =E2=80=9C1:N with N>1=E2=80=9D
>>> distinction isn=E2=80=99t necessary, and I think it=E2=80=99s distracti=
ng and invites
>>> uncertainty.  If you just made these like this:
>>>
>>> NEW
>>>    When the protection type is set to 1+1, there MUST be
>>> =E2=80=A6
>>>    When the protection type is set to 1:N, there MUST be
>>> END
>>>
>>> =E2=80=A6it would be equally correct, but also simpler and, I think, le=
ss likely to be
>>> confusing.
>>>
>>> =E2=80=94 Section 5 =E2=80=94
>>>
>>>    association of one LSP to another LSP across different RSVP - Traffi=
c
>>>    Engineering (RSVP-TE) sessions
>>>
>>> Is it typical to have that hyphen there in the first line?  Isn=E2=80=
=99t it more
>>> typical to write =E2=80=9CRSVP Traffic Engineering (RSVP-TE)=E2=80=9D w=
ithout the extra hyphen?
>>>
>>>    The information in the PPAG TLV in PCEP as received from the
>>>    PCE, is used to trigger
>>>
>>> Remove the comma.
>>>
>>>


From nobody Tue Sep 17 23:16:13 2019
Return-Path: <dhruv.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 046DE1200FB; Tue, 17 Sep 2019 23:16:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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, 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 vzi7WAnTZU_a; Tue, 17 Sep 2019 23:16:01 -0700 (PDT)
Received: from mail-io1-xd43.google.com (mail-io1-xd43.google.com [IPv6:2607:f8b0:4864:20::d43]) (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 B01701200A4; Tue, 17 Sep 2019 23:16:01 -0700 (PDT)
Received: by mail-io1-xd43.google.com with SMTP id q1so13522168ion.1; Tue, 17 Sep 2019 23:16:01 -0700 (PDT)
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=F+lmWelVYC6NxNmMt2pJxwmMpqSNqHEOnNms0yDSf1s=; b=WK5s0jJv5daNNolyAHSMctRR2GPtTspFoPvoJDtIRgTXV/CIWS0ewd9KhVUgkftnVk NE5RHDbD9DP7TYptWSHNZLxvo4H7Dtr6VHL0F/bUwXvAmHkJRbZuILimgKUSFTGGY4Um Ud6M5eYPCEbAEEaSTf6LRCNUT/mYMDgRB4hlx7e2JaTlyl1sc6KiseQCXgywBH/5ocUB a07ue6ykYMDH+WAxY0pSJVQkjEnlQOoAJ5gTCujUAZ09cCjtakUaXOU26FojXoeJZFYM GPo5uPx/RYrwRtsQYRk09RL/bx8nPHMMaudV2NIV6pfC+J9n5ePITIBjHtcUbHS88Pmc bDkA==
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=F+lmWelVYC6NxNmMt2pJxwmMpqSNqHEOnNms0yDSf1s=; b=p1IlSJNy4c36W3gZ0BiQeszM8owWPvFurfm8WJXdv9AxbUurvn8f2hmg/WU2ayknw6 X8aohjkEbv7fJZuRICJBMX3iDlP0xo7gePc2/0szJx9f/EyJn3iNV6CefSbvFQ4VXh+X yJKSwdZckRnZ9/U+6EmcpVQeEiVwmbR0uZDZ+mDAzT6ULdj/dEIzIoxRrG1tQFppPErq kE6kQQBeCNbvoFa4b+HgRvs6p/H9jAZofXvhlhAJ9Go7uoYAqNd33CVJL25gSyPAtW41 Zrnat/1pprDnMC1Pbdnsewei9QHo7s9775d0bVAczVOhI3F93G2AeRCmULhAlqcHAcDr dIxQ==
X-Gm-Message-State: APjAAAWwWQfLAR1myz1M2hdl4oXKWC4KDF30BrzsbRjuiSoeRQEYmSmU eB1fq2qgVuQNLFsM7k0KnPsDxajV5tPHmwosZx4=
X-Google-Smtp-Source: APXvYqx/iigI/wW8dblxXCNwZEh/XmlJbTUs1S1Ll5I6qZ+rOTEdBR4Z8C2VnlbB0tdFhW0Phcmv4jP5BEK5VDk849U=
X-Received: by 2002:a02:2302:: with SMTP id u2mr3176186jau.70.1568787360635; Tue, 17 Sep 2019 23:16:00 -0700 (PDT)
MIME-Version: 1.0
References: <156876388231.17411.6094234033866939217.idtracker@ietfa.amsl.com>
In-Reply-To: <156876388231.17411.6094234033866939217.idtracker@ietfa.amsl.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Wed, 18 Sep 2019 11:45:23 +0530
Message-ID: <CAB75xn4L2RE0vo44bt332kUL7Nh=LryKpJ3BSHRRnHggz8v3vQ@mail.gmail.com>
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pce-stateful-path-protection@ietf.org, Julien Meuric <julien.meuric@orange.com>, pce-chairs <pce-chairs@ietf.org>, pce@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/rrTWi_wtHplsCoRMyH_0lfJildE>
Subject: Re: [Pce] Benjamin Kaduk's Discuss on draft-ietf-pce-stateful-path-protection-10: (with DISCUSS and COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Sep 2019 06:16:05 -0000

Hi Ben,

Thanks for your review, let me start the discussion and the authors
can interject as needed.

On Wed, Sep 18, 2019 at 5:14 AM Benjamin Kaduk via Datatracker
<noreply@ietf.org> wrote:
>
> Benjamin Kaduk has entered the following ballot position for
> draft-ietf-pce-stateful-path-protection-10: Discuss
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-path-protection/
>
>
>
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
> (1) draft-ietf-pce-association-group notes that "PCEP extensions that define
> a new association type should clarify the relationship between the SVEC
> object and the association type, if any".  Where do we do so for the
> path protection association type?
>

This is discussed in
https://tools.ietf.org/html/draft-ietf-pce-association-diversity-10#section-5.3,
where it is more relevant. This draft includes the relationship with
diversity association in Section 5.

> (2) Section 3.2 says:
>
>       Protection Type (PT): 6 bits - This field is as defined in
>       Section 14.1 of [RFC4872] to indicate the LSP protection type in
>       use.
>
> There doesn't seem to be a registry created by RFC 4872 to track these
> PT values, so I assume that the way to allocate a new value is
> "standards-track RFC that Updates: RFC 4872".  Is that also the way to
> allocate new PT values for PPAG usage?  How would someone updating RFC
> 4872 to allocate a new type know to consider/document whether it applies
> for PPAG usage?
>

That's true. Maybe we can add this text - "Any type already defined or
that could be defined in the future for use in the RSVP-TE PROTECTION
object is acceptable in this TLV unless explicitly stated otherwise."

> (3) In Section 4.3:
>
>    A PCE can create/update working and protection LSPs independently.
>    As specified in [I-D.ietf-pce-association-group], Association Groups
>    can be created by both the PCE and the PCC.  Further, a PCE can
>
> The requirement that source, destination, and tunnel ID of all LSPs
> within a PPAG MUST be the same is new to this document, so I think we
> need to specify error handling for when attempts to update LSPs
> independently would violate that invariant (presumably in Section 4.5).
>

In the existing error case in Section 4.5 we could make it "add or update".

> (4) In Section 6.3:
>
>                                       IANA is requested to allocate new
>    error values within the "PCEP-ERROR Object Error Types and Values"
>    sub-registry of the PCEP Numbers registry, as follows:
>
> The following table only lists Error-values.  What Error-type(s) should
> they be associated with?
>

It is mentioned in the text, but worth making it explicit in the table as well.

> (5) We don't say which objects the PPAG TLV can appear in.  (Section 3.2
> says "[t]he Path Protection Association TLV is an optional TLV for use
> with the Path Protection Association Type", but it's hard to interpret
> that as meaning "for use [only] with the ASSOCIATION object defined in
> draft-ietf-pce-association-group", especially since there is a "path
> protection association type" already (and it's a codepoint in the
> "ASSOCIATION Type Field" registry).
>

We can update to - "The Path Protection Association TLV is an optional
TLV for use in the ASSOCIATION Object with the Path Protection
Association Type."

> (6) I'm not sure if a change to the document is needed here, but perhaps
> some discussion is in order: we say that a given LSP can belong to more
> than one PPAG, but only allow one PPAG TLV per [some context that
> remains unclear; see (5)].  I don't have a good handle for whether these
> two requirements are potentially in conflict: that is, whether a single
> PPAG TLV would have to specify the flags that apply for both PPAGs that
> a given LSP is a member of, or if the containing objects serve to scope
> the PPAG TLV flags' interpretation.
>

When a given LSP belong to more than one PPAG, we expect to have
multiple ASSOCIATION Object for each PPAG with each of them having a
single PPAG TLV.

> (7) Do the Protection Type fields of the PPAG TLV in the various LSPs
> that are members of the same PPAG need to match, in the same way that
> the source/destination/tunnel-ID do?
>

Yes. Authors should make that explicit.

>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Section 1
>
>    This document specifies a stateful PCEP extension to associate two or
>    more LSPs for the purpose of setting up path protection.  The
>    proposed extension covers the following scenarios:
>
> nit: after publication, it doesn't really seem like a *proposed*
> extension anymore.
>
> Section 3.1
>
>    LSPs are not associated by listing the other LSPs with which they
>    interact, but rather by making them belong to an association group
>    referred to as "Path Protection Association Group" (PPAG) in this
>    document.  [...]
>
> The first 2/3 of this sentence is a (true) generic statement about all
> association groups, which exist outside of this document in a generic
> fashion.  I strongly suggest rewording this to make clear that the PPAG
> is the specific association (group) type used for this document's
> functionality but that other association groups are possible.  The
> current wording implies that the PPAG is the only association possible,
> and it is just given a special name for this document's purposes.
>
>    [I-D.ietf-pce-association-group] specifies the mechanism for the
>    capability advertisement of the Association types supported by a PCEP
>    speaker by defining a ASSOC-Type-List TLV to be carried within an
>    OPEN object.  This capability exchange for the Association type
>    described in this document (i.e.  Path Protection Association Type)
>    MAY be done before using the policy association, i.e., the PCEP
>    speaker MAY include the Path Protection Association Type (TBD1) in
>    the ASSOC-Type-List TLV before using the PPAG in the PCEP messages.
>
> Why is this only MAY and not MUST?
>

In [I-D.ietf-pce-association-group] we explicitly did not mandate the
capability exchange for all association types and let each type decide
for itself. This association type fits into where the capability
exchange is optional. When the capability exchange was added in
[I-D.ietf-pce-association-group], there was a desire from the WG to
keep it optional for already defined/implemented protection
association type. Also this is a basic feature in path computation and
it is expected to be supported universally. In a corner case there is
an error handling for unknown/unsupported association-type to take
care of it.

>    This Association type is dynamic in nature and created by the PCC or
>
> nit: is it the type that is dynamic or the associations of that type?
>

It is the type. [I-D.ietf-pce-association-group] has dynamic or
operator-configured association, this one is dynamic.

>       Protecting (P): 1 bit - This bit is as defined in Section 14.1 of
>       [RFC4872] to indicate if the LSP is working or protection LSP.
>
>       Secondary (S): 1 bit - This bit is as defined in Section 14.1 of
>       [RFC4872] to indicate if the LSP is primary or secondary LSP.  The
>       S flag is ignored if the P flag is not set.
>
> Just to check my understanding (no change expected to result): if P is
> zero, the LSP is working, and thus we know that it's primary since it's
> actively carrying traffic?
>

Yes, Working LSPs are always primary.


> Section 3.2
>
> nit(?) The section heading does not match the name of the TLV requested
> in the IANA considerations, nor do we mention here that "PPAG TLV" is
> synonymous with it.
>
>    If the TLV is missing, it is considered that the LSP is the working
>    LSP (i.e. as if P bit is unset).
>
> Is this conditional on the LSP being part of a PPAG, or does it hold
> generically as well?
>

IMHO when part of a PPAG i.e. association object but no TLV.

> Section 4.5
>
>    As per the processing rules specified in section 5.4 of
>    [I-D.ietf-pce-association-group], if a PCEP speaker does not support
>
> There is no Section 5.4 in draft-ietf-pce-association-group-10;
> presumably this was supposed to be Section 6.4?
>
>    A given LSP MAY belong to more than one PPAG.  If there is a conflict
>
> While I'm not arguing to remove this option, I'm also a bit confused at
> how useful having a single LSP be in multiple PPAGs woud be, given the
> need for source/destination/tunnel-ID to match.
>

One working LSP could have multiple protection LSPs with each
belonging to a different association.

>    When the protection type is set to 1+1 or 1:N with N=1, there MUST be
>    only one working LSP and one protection LSP within a PPAG.  If a PCEP
>    speaker attempts to add another working/protection LSP, the PCEP peer
>    MUST send PCErr with Error-Type 26 (Association Error)
>    [I-D.ietf-pce-association-group] and Error-Value TBD4 (Attempt to add
>    another working/protection LSP for Path Protection Association).
>
> This seems to prevent a scenario where there's a need to change the
> protection LSP and a desire to do so without removing the protected
> nature of the working LSP.  Unless it's presumed that this could always
> be done by updating the protection LSP and it would never be necessary
> to create a new one?  (Similarly for 1:N, though maybe less severe.)
>

One can remove the protection LSP and keep the association intact. The
error will not be triggered.
Also, PCEP messages are per LSP, when the first LSP is reported with
association, it is bound to be the only LSP in the association.
So the error in this section are focused only when one adds "another".

Maybe we can add "..at maximum.." to make it clear?

> Section 5
>
>    [RFC4872] introduces the concept and mechanisms to support the
>    association of one LSP to another LSP across different RSVP - Traffic
>    Engineering (RSVP-TE) sessions using ASSOCIATION and PROTECTION
>    object.  The information in the PPAG TLV in PCEP as received from the
>    PCE, is used to trigger the signalling of working LSP and protection
>    LSP, with the Path Protection Association Flags mapped to the
>    corresponding fields in the PROTECTION Object in RSVP-TE.
>
> Just to check my understanding: this paragraph is saying that the
> contents of the PPAG TLV received by the PCC is used as input to
> populating the PROTECTION object that corresponds to the protection
> group?
>

Yes.

> Section 10.2
>
> I think RFCs 7525 and 8253 need to be normative (and please cite RFC
> 7525 as BCP 195).
>
>

Thanks!
Dhruv


From nobody Wed Sep 18 07:15:22 2019
Return-Path: <noreply@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E5D612011F; Wed, 18 Sep 2019 07:15:21 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Roman Danyliw via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-pce-stateful-hpce@ietf.org, Adrian Farrel <adrian@olddog.co.uk>, pce-chairs@ietf.org, adrian@olddog.co.uk, pce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.101.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Roman Danyliw <rdd@cert.org>
Message-ID: <156881612137.4479.15191325652251719065.idtracker@ietfa.amsl.com>
Date: Wed, 18 Sep 2019 07:15:21 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/v35iMJLmB4wpDL74EcXvQ--ksFk>
Subject: [Pce] Roman Danyliw's Discuss on draft-ietf-pce-stateful-hpce-13: (with DISCUSS and COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Sep 2019 14:15:21 -0000

Roman Danyliw has entered the following ballot position for
draft-ietf-pce-stateful-hpce-13: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-hpce/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

** Section 4.  Per “The security considerations listed in [RFC8231], [RFC6805]
and [RFC5440] apply to this document as well. As per [RFC6805], it is expected
that the parent PCE will require all child PCEs to use full security when
communicating with the parent.”, the references make sense, thanks for making
them.  My concern is in the definition of “use full security”.  I can see those
words come from RFC6805, however, I can't find where that set of practices is
defined.  Can this please be clarified.


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

** Section 4.  Per the recommendation to use TLS _or_ TCP-AO.
-- I take the point from the SECDIR (thanks Stephen Farrell) about the (lack
of) deployment of AO.  My caution would be that TLS and TCP-AO provide
different security mechanism and therefore imbue different security properties
and this should be noted. (i.e., this isn’t a choice between like options)

-- As an editorial nit, it would be worth saying that guidance for implementing
using TLS with PCEP can be found in RFC8232.

** Editorial Nits:
Title.  Is the period at the end of the title necessary?



From nobody Wed Sep 18 07:47:04 2019
Return-Path: <dhruv.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA60B120843; Wed, 18 Sep 2019 07:47:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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, 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 wVQgfEQrKAim; Wed, 18 Sep 2019 07:46:59 -0700 (PDT)
Received: from mail-io1-xd44.google.com (mail-io1-xd44.google.com [IPv6:2607:f8b0:4864:20::d44]) (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 D551812081E; Wed, 18 Sep 2019 07:46:58 -0700 (PDT)
Received: by mail-io1-xd44.google.com with SMTP id q10so16853442iop.2; Wed, 18 Sep 2019 07:46:58 -0700 (PDT)
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=IdBVLpo46mil3lvNMdYDrWEGO/8CoNZAOl36nvT7aoA=; b=Iog4AQFZjqJemWLzeLcqGAZ3sTZkQyz2JLMYjWArNH5GCVk9OISo0ACHnY9XsOPwUp K35KJJA+udOYJA1UY5EECpBZRZlNxRDtzp8SK/u1NeYtqrplnRVf/KDzezdD1mx4GnCc h3VEa4fATqT5krreelkdWQNP1Se8nEtXAJQcYKVM4wMZ+tDvfVpLpXAenOTZKtqwPAWn LqZd5/XhlHeREyk03rznczXsxYGVG6M3IOSl/jy1VfoYnHvKmmSpsZIhrqrgLbZ7oYij hIrDvMcfFTHzpJCRYq4qbYWa2ephz5CGnVRKSLpGMMRh/PzPljYxmXNT6+mNH4XnT7Ex G2Vg==
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=IdBVLpo46mil3lvNMdYDrWEGO/8CoNZAOl36nvT7aoA=; b=jYsYsjcxfJqCWLMchEE/8yGQaJOPFD9j6yh1KTqZ0E0LvqLJxqPUOIVwin1vHVT37u N6jvBmeZif7G2tzz1LCp+IVR4oJfJWaTRHCzdGczva3XhVg5Dxb4mWLR28pDTNV+1Lw7 8MEqVOm3KB+B1F43J2Bn7knagLRaEaScPy/4Rl52hwGh98sxmdSE8J481jqNki+iu/V0 wdOa2Hk/DY0PPBKOIJPltqgk4TJBf8UROfapvSfP32STKDwRFP9DJi1CvBC3/Xejhyh8 ezUet1lEHxfhctDjyOVIavmS/rR/kXGJdYU8LZz5BNpdsU6lGi7WXBzeaJ+aLxiBJJBG BCbQ==
X-Gm-Message-State: APjAAAVwjZ6xF1hexIpZjRwPM6ETYSXBeXvQmGU7htBVE5wN7gS1hwyV uij5ahsZwHIH/Js1lbyUzW/k4fE/bgrL+8h6Wak=
X-Google-Smtp-Source: APXvYqzKXBf3Mq/3k6IXGmRIDvcyeRMP6l/MBmkLD5ZOh4mNPKNfAeKF7u3gWjxVQbbLicutAuDNahju9ia31RQyrbc=
X-Received: by 2002:a05:6638:778:: with SMTP id y24mr5346970jad.122.1568818017711;  Wed, 18 Sep 2019 07:46:57 -0700 (PDT)
MIME-Version: 1.0
References: <156874887441.17499.7855633347557404477.idtracker@ietfa.amsl.com>
In-Reply-To: <156874887441.17499.7855633347557404477.idtracker@ietfa.amsl.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Wed, 18 Sep 2019 20:16:20 +0530
Message-ID: <CAB75xn5MUrTS43f5boMo4Kq7dfCo+YmLu1Qh_Qf-XN9hXLKsww@mail.gmail.com>
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pce-stateful-pce-auto-bandwidth@ietf.org,  Adrian Farrel <adrian@olddog.co.uk>, pce-chairs <pce-chairs@ietf.org>, pce@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/A_R-9FaJI83LAKoJTdRTW0JXOIQ>
Subject: Re: [Pce] Benjamin Kaduk's Discuss on draft-ietf-pce-stateful-pce-auto-bandwidth-11: (with DISCUSS and COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Sep 2019 14:47:03 -0000

Hi Ben,

Thanks for your review. Please see inline...

On Wed, Sep 18, 2019 at 1:04 AM Benjamin Kaduk via Datatracker
<noreply@ietf.org> wrote:
>
> Benjamin Kaduk has entered the following ballot position for
> draft-ietf-pce-stateful-pce-auto-bandwidth-11: Discuss
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-pce-auto-bandwidth/
>
>
>
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
> This document seems generally useful, and thanks for it.  I think
> there's a couple places where it's ambiguous or unclear, and hopefully
> we can tighten up the language without needing extensive changes.
>
> There may be an internal inconsistency in Section 2.3's definitions
> relating the Overflow-Count and the Overflow-Threshold: the description
> of Overflow-Count reads as if it is a reported quantity, but the
> description of Overflow-Threshold implies that Overflow-Count is a
> configured parameter.  (Similarly for the Underflow- variants.)
> Specifically, the sentence "[t]his value indicates how many times
> consecutively, the percentage or absolute difference between the current
> MaxAvgBw and the current bandwidth reservation of the LSP is greater
> than or equal to the Overflow-Threshold value" uses the descriptive
> verb "is" as opposed to a conditional such as "needs to be [...] in
> order to [...]".
>

Updated.

> Section 5.2.3.2 says:
>
>    If the percentage difference between the current MaxAvgBw and the
>    current bandwidth reservation is greater than or less than or equal
>    to the threshold percentage, the LSP bandwidth is adjusted to the
>    current bandwidth demand (MaxAvgBw) (as long as the difference in the
>    bandwidth is at least or above the Minimum-Threshold).
>
> As written ("greater than or less than or equal to"), this is always
> true, which cannot be what was intended.  Probably we should reword to
> just "greater than" and talk about the percentage absolute difference,
> i.e., 100 * abs(MaxAvgBw - CurrentRes) / CurrentRes .
>

Updated.

>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> As a general note, I'm not sure the phrase "calculated bandwidth to be
> adjusted" is a great fit for how it's currently being used.
> Specifically, the "calculation" in question seems to just be taking the
> maximum of a sliding window of per-timeslice average bandwidth values,
> and this seems like a sufficiently small amount of computation that I'd
> be comfortable describing it as a "measurement", for "measured bandwidth
> as input to path calculation".  That is, this doesn't seem like it comes
> close to the amount of computation involved in actually computing paths,
> so I keep misreading what information is being sent where.
>

In an earlier version there was a feature where the PCC could report
the measured value at each sample interval (it moved to another
document). IMHO for the clarity in the WG, it is still better to
differentiate between the raw measured value (telemetry) and the value
that is currently reported which is marked as "calculated".

> Section 1
>
>    Over time, based on the varying traffic pattern, an LSP established
>    with a certain bandwidth may require to adjust the bandwidth reserved
>    in the network dynamically.  The head-end Label Switch Router (LSR)
>    monitors the actual bandwidth demand of the established LSP and
>    periodically computes new bandwidth.  The head-end LSR adjusts the
>    bandwidth reservation of the LSP based on the computed bandwidth
>    automatically.  This feature is commonly referred to as Auto-
>    Bandwidth.  The Auto-Bandwidth feature is described in detail in
>    Section 4 of this document.
>
> >From just this text, I can't tell if this is describing the mechanisms of
> this document or an existing Auto-Bandwidth feature that is related to
> the mechanisms of this document.
>

The auto-bandwidth feature without PCE exists, where the ingress does
the measurement as well as path computation. This feature has been
implemented long back but was not part of any standard because it was
a local implementation at the ingress node and no protocol changes was
required. With the PCE things changed and here we are...

>    In the model considered in this document, the PCC (head-end of the
>    LSP) collects the traffic rate samples flowing through the LSP and
>    calculates the new adjusted bandwidth.  The PCC reports the
>    calculated bandwidth to be adjusted to the PCE.  This is similar to
>    the Passive stateful PCE model, while the Passive stateful PCE uses
>    path request/reply mechanism, the Active stateful PCE uses
>    report/update mechanism.  [...]
>
> nit: I think the punctuation in this last sentence needs some tweaking,
> as there looks to be a comma splice at present.
> (It's also unclear how much we need to talk about Passive stateful PCE,
> since just two paragraphs ago we say we focus on Active stateful PCE in
> this document.)
>

This was updated based on Barry's suggestion. It makes sense to
include a sentence here in Introduction to set the stage.

>    This document defines the PCEP extensions needed to support Auto-
>    Bandwidth feature in a Active stateful PCE model where the LSP
>    bandwidth to be adjusted is calculated on the PCC (head-end of the
>    LSP). The use of PCE to calculate the bandwidth to be adjusted is out
>    of scope of this document.
>
> Maybe I'm just confused about active vs. passive in general, but I
> thought that active stateful PCE involved the PCE "making the decisions"
> with the PCC just providing input data.  But here we're saying that the
> PCC is making the bandwidth decision, even though the rest of the LSP
> computation remains on the PCE?

Yes, this is correct. The calculated bandwidth is still an input for
PCE to make the path computation taking that as an input.

> Or is "calculate the bandwidth to be
> adjusted" referring to "evaluate the expression max_{time periods}(avg.
> bandwidth per time period)" (as opposed to "compute the bandwidth
> adjustment to make)?
>

It is the former.

> Section 2.3
>
> Are we assuming any relationship between the Up-Adjustment-Threshold and
> the Overflow-Threshold?
>

Yes, as mentioned here while describing Overflow-Threshold -

      The LSP bandwidth is adjusted to the
      current bandwidth demand bypassing the Up-Adjustment-Interval if
      the overflow condition is met consecutively for the Overflow-
      Count.


>       traffic demand.  If the percentage or absolute difference between
>       the current MaxAvgBw and the current bandwidth reservation of the
>       LSP is greater than or equal to the threshold value, the overflow
>       condition is set to be met.  The LSP bandwidth is adjusted to the
>
> nit: I think s/set to be met/said to be met/ ?  (this appears twice)
>

Ack

>    Minimum-Threshold:  The increase or decrease of the LSP bandwidth
>       should be at least or above the minimum-threshold represented as
>       an absolute bandwidth value before the bandwidth adjustment for
>       the LSP is made.  This threshold can be seen as a suppression
>       threshold that is used along with a percentage threshold to avoid
>       unnecessary auto-bandwidth adjustments and re-signaling of the LSP
>       at low bandwidth values.
>
> I can't tell from this text if this threshold is a (LSP) bandwidth
> value/measurement or a bandwidth offset between configured and measured
> values.  (The subsequent protocol element definitions are more clear
> that it's the latter.)
>

It is latter. Do you have a suggested change, I am not sure what change to make.

> Section 3
>
> The column headings in Table 1 refer to who initiates the LSP in
> question, right?
>

yes

>    The PCEP speaker supporting this document must have a mechanism to
>    advertise the automatic bandwidth adjustment capability for both PCC-
>    Initiated and PCE-Initiated LSPs.
>
> Just checking on "must" vs. "MUST" here.
>

The use of normative for requirements for the protocol extensions may
not be required. .

>    o  It is required to identify and inform the PCC, which LSPs are
>       enabled with Auto-Bandwidth feature.  Not all LSPs in some
>       deployments would like their bandwidth to be dependent on the
>       real-time bandwidth usage but be constant as set by the operator.
>
> nit: I suggest NEW:
>
> %  o  It is required to identify and inform the PCC which LSPs have
> %     enabled the Auto-Bandwidth feature.  Not all LSPs in some
> %     deployments would like their bandwidth to be dependent on the
> %     real-time bandwidth usage; for some LSPs leaving the bandwidth
> %     constant as set by the operator is preferred.
>

Ack

> Section 4.2
>
>    When the Auto-Bandwidth feature is enabled, the measured traffic rate
>    is periodically sampled at each Sample-Interval (which can be
>    configured by an operator and the default value as 5 minutes) by the
>    PCC, when the PCC is the head-end node of the LSP.  The traffic rate
>
> Do we cover what happens in the case when the PCC is not the head-end
> node of the LSP?
>

No.

> Section 5.1
>
>    o  The PCEP speaker that does not recognize the extensions defined in
>       this document sends the PCErr message with error-type 2
>       (capability not supported) as per Section 6.9 in [RFC5440].
>
> This refers to when the actual new messages (e.g.,
> AUTO-BANDWIDTH-ATTRIBUTES TLV) are being used, not merely advertising
> the Auto-Bandwidth Capability TLV in the OPEN object, right?  That is,
> this is descriptive language of what the core protocol spec mandates as
> error handling in the presence of unrecognized input?
>

This is a mistake, that error is only for unknown message. Will fix this.

> Section 5.1.1
>
> nit: in the previous section we captialized this as "Auto-Bandwidth
> Capability", but here (including the section heading) it is
> "AUTO-BANDWIDTH-CAPABILITY".  Should they be consistent?
>

Updated

> Section 5.2
>
>    Future specification can define additional sub-TLVs.
>
> I see that we see later that unrecognized sub-TLVs are ignored, but
> would there be a case where we want to use a bit in the
> AUTO-BANDWIDTH-CAPABILITY flags to negotiate support for a sub-TLV
> (i.e., to confirm that the peer will understand it, instead of just
> sending it and not knowing if it is understood)?
>

I guess a future extension that defines any new sub-TLV for
auto-bandwidth could take that approach.

> Section 5.2.1
>
> It sounds like we should ignore values larger than 7 days as well
> (rather than erroring out)?
>

Updated

> Section 5.2.2, 5.2.3
>
> I'd like to see a little bit more detail specified of the interaction
> between (regular) Adjustment-{Interval,Threshold} and
> Down-Adjustment-{Interval,Threshold}.  We do have this text about (e.g.)
> "[t]he Adjustment-Interval sub-TLV specifies the time interval for both
> upward and downward trend", which conveys the general intent, but I'm
> not sure I have all the details about there being one default value,
> that applies to both, and changes to the (regular) parameter continue to
> apply to both, until an explicit Down- variant is seen, at which point
> the control of the two parameters diverge permanently and they must
> always be separately controlled.
>

Updated

> Section 5.2.3.1
>
>    o  Adjustment-Threshold: The absolute Adjustment-Threshold bandwidth
>       value, encoded in IEEE floating point format (see
>
> nit: I'd suggest that this is a bandwidth *difference* value (or offset),
> pedantically speaking.  (The following paragraph is quite clear on the
> actual usage, though, so this is nit-level.)  This comment applies to
> basically all the threshold fields in the document, but I'll just make
> it once, here.
>

Updated

> Section 5.2.3.2
>
>    o  Reserved: SHOULD be set to zero on transmission and MUST be
>       ignored on receipt.
>
> I think the formulation of "MUST be set to zero on transmission and
> SHOULD be ignored on receipt" is more common.
>

Changed to MUST for both.

>    o  Percentage: The Adjustment-Threshold value (7 bits), encoded in
>       percentage (an integer from 1 to 100).  The value 0 is considered
>       to be invalid.  The default value is 5 percent.
>
> I assume that the question of whether to allow sub-percentage
> granularity came up, and don't want to revisit the WG's decision.  But
> please confirm that it was discussed.
>

I don't have a thread to point to where this was explicitly talked
about. But I believe we have WG consensuses for this.

> Also, are values over 100 also "invalid"?  What should the recipient do
> upon receipt of an invalid value?
>
>    If the percentage difference between the current MaxAvgBw and the
>    current bandwidth reservation is greater than or less than or equal
>    to the threshold percentage, the LSP bandwidth is adjusted to the
>    current bandwidth demand (MaxAvgBw) (as long as the difference in the
>    bandwidth is at least or above the Minimum-Threshold).
>
> I'd suggest rewording to make the two criteria equal peers (e.g., "If X
> and Y") rather than relegating the minimum-threshold to a parenthetical
> that's easy to ignore.
>

Ack

> Section 5.2.3.3
>
> It would probably be good to reiterate here (and at other similar
> locations) that this "is used to decide" only when there's a need for
> different behavior in the upward and downard directions.
>
> Also, nit-level, I think "overrides" is more appropriate than
> "overwrites", since the non-Down- variant remains active for its
> separate role.
>

Ack

> Section 5.2.4.2
>
>       per second.  The default maximum-bandwidth value is not set.
>
> I guess effectively the default is FLOAT_MAX, inherited from RFC 5440.
>

Yes

> Section 5.2.5.1
>
>    o  Overflow-Threshold: The absolute Overflow-Threshold bandwidth
>       value, encoded in IEEE floating point format (see
>       [IEEE.754.1985]), expressed in bytes per second.  Refer to Section
>       3.1.2 of [RFC3471] for a table of commonly used values.  If the
>       increase of the current MaxAvgBw from the current bandwidth
>       reservation is greater than or equal to the threshold value, the
>       overflow condition is met.
>
> nit: I'd suggest to s/increase/difference/, since (IIUC) the operation
> here is "observed bandwidth remains above the (reservation plus)
> threshold for <count> times", not "observed bandwidth increases in
> successive reporting intervals".  This assumes that the
> Adjustment-Interval is larger than <count> times the reporting interval,
> of course.
>

Updated

> Section 5.2.5.3
>
>    o  Underflow-Threshold: The absolute Underflow-Threshold bandwidth
>       value, encoded in IEEE floating point format (see
>       [IEEE.754.1985]), expressed in bytes per second.  Refer to Section
>       3.1.2 of [RFC3471] for a table of commonly used values.  If the
>       decrease of the current MaxAvgBw from the current bandwidth
>       reservation is greater than or equal to the threshold value, the
>       underflow condition is met.
>
> As above, I suggest s/decrease/difference/ (perhaps with an additional
> indication that the magnitude of the difference is to be used, not the
> signed difference).
>

Updated

> Section 5.7
>
> I'm not sure I understand why there's a need for an
> auto-bandwidth-specific "overload" notification, as opposed to having
> such messages suppressed as part of a more general overload condition.
> But that doesn't mean there's not a need, of course, as I'm not very
> familiar with this area!
>

The auto-bandwidth feature increases the rate of message exchange and
path computation. So in case of an overload because of auto-bandwidth
it would be good for a PCEP speaker to indicate that. Also the general
overload only worked in one direction 'PCE to PCC'. Here PCE could
send to many updates to PCC and making PCC to be overloaded as well.

> Section 6.6
>
>    An implementation MAY allow a limit to be placed on the rate of auto-
>    bandwidth related messages sent by a PCEP speaker and received by a
>    peer.  An implementation MAY also allow sending a notification when a
>    PCEP speaker is overwhelmed or the rate of messages reach a
>    threshold.
>
> I don't want to revisit a WG consensus outcome, but I could see "SHOULD"
> for "allow sending a notification", noting that it is "SHOULD allow
> sending" and not "SHOULD send".
>

Updated

> Section 7
>
>    This document defines AUTO-BANDWIDTH-CAPABILITY TLV and AUTO-
>    BANDWIDTH-ATTRIBUTES sub-TLVs which do not add any new security
>    concerns beyond those already discussed in [RFC8231] and [RFC8281]
>
> I'd suggest to qualify this as "do not add any substantial new security
> concerns".  We did just in the previous section talk about how this
> functionality could increase computational and operational load, which,
> taken to an extreme, can affect availability and could be considered a
> security consideration.
>
> We could also perhaps give guidance about setting the min and max
> bandwidth sub-TLVs to constrain automatic adjustment to be within a
> known range and thus bound the extent of second-order effects on the
> rest of the MPLS-TE domain.
>

Updated

> Section 8.2
>
> It might be good to say within what registry the sub-registry being
> created is to be located.
>
> Also, the last paragraph could perhaps be rephrased as "the initial
> contents of the registry are empty, with all bits unassigned".
>

Ack

> Section 9.2
>
> I think that the RFC 7525 and 8253 references fall under the RECOMMENDED
> guidance in Section 7, in which case per
> https://www.ietf.org/about/groups/iesg/statements/normative-informative-references/
> they should be classified as Normative references.  (It's probably also
> good to cite RFC 7525 as BCP 195 and not just RFC 7525.)
>
> The IEEE.754 reference is also normative since we use its wire encoding
> (but it could practically be considered "well-known" at this point,
> given its ubiquity).
>
>

Ack

Diff: https://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=draft-ietf-pce-stateful-pce-auto-bandwidth-11&url2=https://raw.githubusercontent.com/dhruvdhody/ietf/master/draft-ietf-pce-stateful-pce-auto-bandwidth-12.txt

Working Copy: https://raw.githubusercontent.com/dhruvdhody/ietf/master/draft-ietf-pce-stateful-pce-auto-bandwidth-12.txt

Thanks!
Dhruv


From nobody Wed Sep 18 10:29:41 2019
Return-Path: <alissa@cooperw.in>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72CFB12097D; Wed, 18 Sep 2019 10:29:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, 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=cooperw.in header.b=oKjD0ZdF; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=QOV3RNh1
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 i20m-4wgT4f1; Wed, 18 Sep 2019 10:29:23 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7BA5E1209D0; Wed, 18 Sep 2019 10:29:23 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 99DC021FC5; Wed, 18 Sep 2019 13:29:22 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Wed, 18 Sep 2019 13:29:22 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=1 G7gDaQr+d8KK2VSL9/Me5rZhmzFrUO9ktamEWZEI3c=; b=oKjD0ZdFivRpZnzGl up0dbiB52C2qd/S6BrzP/2IPyAGNa4OvnMgnBnKYVZAwqOTTaByaV1iNmDNdRkFI DSYqBecVywuE7TPg5N4RB6Obfi8FH3dB8lMxIGgfkEKXLw23aKftqzGLx2uUaKsy Av9jLSNHdIG1ryhABUv09kt6y6uIHeRJtuTihTH7LYdb9sTn3XZ+XsM57FpOeKGW aUS+xmlU/m35ql/XCqYX839ozIqHFHiaD3F9DMKFGhYH+BYvfE43WZueikb6w2rh FNIMLdslw/PQEMlRYaH/WMcUYl4ErPRlidnls0+6CwIakT1shLOqd1B1jGn39bqX 573pQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=1G7gDaQr+d8KK2VSL9/Me5rZhmzFrUO9ktamEWZEI 3c=; b=QOV3RNh1cJMuOXaxmy2juKsduql19KUQ+6flICjm+aDAe12tgxMH/+fu8 tIO0AJTjKMuXXJE/ofKURENTEvs5mJQUKjw99Rq1ZNoer4Ng5iiP6MHQ8RSSfCqj roBQ2HtwwdUgyGpN9ljnhLHIwxQTkjuzFrca1W4BbDYbAqOzd0+ephcKzZzh23LB WTV2337YKoqmgtmTaod6moyAIsA3HMDwzumUk8eV1MDyVYs0vHOEqiLhNCA3obAb sjMoskn4ebgnI6tUt1oJxlIdMg28/AqKCTe8PhzfxNGpAs+1VKyikjOfeMYCfZFt PBxfzUw2tYBo4EMo1vBGOWnHkHdXQ==
X-ME-Sender: <xms:cmmCXUSEHB5KLN8qHlpQq50tx1CUg_lIXTNocAzMVN4fYYMaj6nhKQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudekgdduudefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtjeenucfhrhhomheptehlihhs shgrucevohhophgvrhcuoegrlhhishhsrgestghoohhpvghrfidrihhnqeenucffohhmrg hinhepihgvthhfrdhorhhgnecukfhppedujeefrdefkedruddujedrleefnecurfgrrhgr mhepmhgrihhlfhhrohhmpegrlhhishhsrgestghoohhpvghrfidrihhnnecuvehluhhsth gvrhfuihiivgeptd
X-ME-Proxy: <xmx:cmmCXSPcU4tsNPSaUUIdlhEvAugV06QABCeI6iSbwNq431m3q95H2w> <xmx:cmmCXRmdo1UcMcM_ntA1-f3ZOvxcVbyZoTeKBjeUB8yB0tIGp1wV0g> <xmx:cmmCXUYpbE3NEMNNRlnZHyAiC32IRgTxhlxWn7fPLHk1rZYlUb1gVA> <xmx:cmmCXaMRhnRCTOz-ZeljwlBlDbXl3GyiyEhsEd9elmS4-AG_YWuZCA>
Received: from rtp-alcoop-nitro2.cisco.com (unknown [173.38.117.93]) by mail.messagingengine.com (Postfix) with ESMTPA id D4ECB80061; Wed, 18 Sep 2019 13:29:21 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <CAB75xn7o_sHjnHOutapz2JiHFwUxkoy0BPW=D00fsn2KQveD8A@mail.gmail.com>
Date: Wed, 18 Sep 2019 13:29:22 -0400
Cc: General Area Review Team <gen-art@ietf.org>, pce@ietf.org, "ietf@ietf.org Discussion" <ietf@ietf.org>, draft-ietf-pce-stateful-pce-auto-bandwidth.all@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <3EDFEFA2-EA36-4140-A76F-4B70BD4BB66C@cooperw.in>
References: <156695748522.22371.4307730844191565910@ietfa.amsl.com> <CAB75xn7o_sHjnHOutapz2JiHFwUxkoy0BPW=D00fsn2KQveD8A@mail.gmail.com>
To: Dhruv Dhody <dhruv.ietf@gmail.com>, Erik Kline <ek@google.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/ytblsimYETwJcPxkf9d7kVvITxU>
Subject: Re: [Pce] [Gen-art] Genart last call review of draft-ietf-pce-stateful-pce-auto-bandwidth-10
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Sep 2019 17:29:26 -0000

Erik, thanks for your review. Dhruv, thanks for addressing Erik=E2=80=99s =
comments. I entered a No Objection ballot.

Alissa


> On Aug 28, 2019, at 2:54 AM, Dhruv Dhody <dhruv.ietf@gmail.com> wrote:
>=20
> Hi Erik,
>=20
> Thank you for your review and suggestions. We will update in the next =
revision.
>=20
> Thanks!
> Dhruv
>=20
> On Wed, Aug 28, 2019 at 7:28 AM Erik Kline via Datatracker
> <noreply@ietf.org> wrote:
>>=20
>> Reviewer: Erik Kline
>> Review result: Ready with Nits
>>=20
>> I am the assigned Gen-ART reviewer for this draft. The General Area
>> Review Team (Gen-ART) reviews all IETF documents being processed
>> by the IESG for the IETF Chair.  Please treat these comments just
>> like any other last call comments.
>>=20
>> For more information, please see the FAQ at
>>=20
>> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>>=20
>> Document: draft-ietf-pce-stateful-pce-auto-bandwidth-10
>> Reviewer: Erik Kline
>> Review Date: 2019-08-27
>> IETF LC End Date: 2019-08-28
>> IESG Telechat date: Not scheduled for a telechat
>>=20
>> Summary:
>>=20
>> Gentle reminder for the authors to double-check all the lower case =
"should"s,
>> "required"s, and "must not"s (etc) to make sure it's not important =
that they be
>> capitalized (since the case-sensitive requirements text is =
referenced).
>>=20
>> Major issues:
>>=20
>> Minor issues:
>>=20
>> Nits/editorial comments:
>>=20
>> There are some periodic grammatical changes that I think would be =
nice, but I
>> assume that can get sorted out with the RFC editor.
>>=20
>> Two random things I'll note:
>>=20
>> Section 1> I can't find "Path Control Element" in RFC 5440. Should =
this be
>> "Path Computation Element"?
>>=20
>> Section 5.2>
>>    .  s/speaker wish to disable/speaker wishes to disable/
>>    .  s/of same type/of the same type/
>>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Wed Sep 18 10:38:58 2019
Return-Path: <noreply@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D167120AD4; Wed, 18 Sep 2019 10:38:56 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Roman Danyliw via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-pce-stateful-pce-auto-bandwidth@ietf.org, Adrian Farrel <adrian@olddog.co.uk>, pce-chairs@ietf.org, adrian@olddog.co.uk,  pce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.101.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Roman Danyliw <rdd@cert.org>
Message-ID: <156882833650.4553.15366878761681665492.idtracker@ietfa.amsl.com>
Date: Wed, 18 Sep 2019 10:38:56 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/Bb1YVGezbgclb18xUTS7p6Kpzt0>
Subject: [Pce] Roman Danyliw's No Objection on draft-ietf-pce-stateful-pce-auto-bandwidth-11: (with COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Sep 2019 17:38:57 -0000

Roman Danyliw has entered the following ballot position for
draft-ietf-pce-stateful-pce-auto-bandwidth-11: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-pce-auto-bandwidth/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

** I support Ben Kaduk’s DISCUSS position on the need for clarity in the
definition of Overflow-Count and Overflow-Threshold

** Section 5.2.x.  Error handling:
-- A number of the sub-TLVs define ranges smaller than would be possible given
the number of bit (e.g., 1..604800 in a 32-bit field; 1.100), how would an
error be signaled for values used outside that range?

-- For values that are [IEEE.754.1985]), how should negative value be processed?

** Nits:
-- Section 1.  Typo. s/a Active stateful/an Active stateful/

-- Section 5.2.2.2.  For consistency with the other sections s/1 to 604800/1 to
604800 (7 days)/

-- Section 6.6.  Typo. s/signalling/signaling/



From nobody Wed Sep 18 12:12:13 2019
Return-Path: <alissa@cooperw.in>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 487D5120128; Wed, 18 Sep 2019 12:12:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, 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=cooperw.in header.b=Ewxf2DTw; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=KpGUCJQz
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 xt0vsSiJ2WxH; Wed, 18 Sep 2019 12:12:01 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ABB5212012C; Wed, 18 Sep 2019 12:12:01 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id B8333213BD; Wed, 18 Sep 2019 15:12:00 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Wed, 18 Sep 2019 15:12:00 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=7 0rtMltCfj1jRyEZcdCkfepzK9Y6W8pYzF0Jn+GfG2Q=; b=Ewxf2DTweIhLlzsvk MkvgNpTu9e0JbP/tB0GehdbZkBhH+3HsodTFMP8xutPJEE3Ry6U4du3NPuuXaYBO liGBSlc7L6loc2Oz81dfwudNtakACOTQdHSmpgOtQrI6Ed1BkXuhbiwQ0HR1yjkX 11EtMYwh0za3Y+jAQX0nLww1RAd8H/uTFAJOk9LTUgmqxgCgJEA63VOuPt0xuxS5 AoxWuEk4jCcznlCVw5NzzdjLhEi0/X7xZQS2XzgczsAWUuqh3lg+s4U5JclSaZE9 OoU4SAuED09SCuz/62f8jOvs23tdTe9YZn5mphtuIUNk7uXl7OxeVhaSZvsM8AFv yodwA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=70rtMltCfj1jRyEZcdCkfepzK9Y6W8pYzF0Jn+GfG 2Q=; b=KpGUCJQz13rMWPEzB/1nCqgaNSwM4tklP8Ujm1in+fARzFaqynWW5g1+8 CoGrP8E+fUUDcoz/hI40LNBQ6MmeA1FdW8MXAGFStCOvMYO/t1LGZJs1zLjMU0Uz X4MDnz9bB+Dq8kD9NLbDS8pw1/95Eb0USFTPmM7uXAcCPN/n8/EkFI9gYTcNhLrY Y4ir5HXLlmPrQSxhFcMjlLte0pyp8o3i0rRUQ9eIWLSB4C0fv2wzdeZ1s3V+fF3e MIcBy3TbIKNBO92KenT24T3d9MJ0xYGwm/0tqt4dnhAOYAdUGv/DaWh3HtC+UTAD i43bXVkozx9WKaDRkM3ZoPcWE/qSA==
X-ME-Sender: <xms:gIGCXT08riDzRfNPSPKjBtRoltEr0O096iT7DFnSJyPFuK1ZiZk5AQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudekgddufeegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtvdenucfhrhhomheptehlihhs shgrucevohhophgvrhcuoegrlhhishhsrgestghoohhpvghrfidrihhnqeenucffohhmrg hinhepghhithhhuhgsuhhsvghrtghonhhtvghnthdrtghomhdpghhithhhuhgsrdgtohhm pdhivghtfhdrohhrghenucfkphepudejfedrfeekrdduudejrdelfeenucfrrghrrghmpe hmrghilhhfrhhomheprghlihhsshgrsegtohhophgvrhifrdhinhenucevlhhushhtvghr ufhiiigvpedt
X-ME-Proxy: <xmx:gIGCXSMFRiXVmXSXqmcGtkwN2qRhsdex_EZtQZLw9WnXKya2_aZBPA> <xmx:gIGCXbW25mS-kV6-MKpSYuMIqzufU-ox9DgEA8proGz-Rxu03onuWg> <xmx:gIGCXfYIBVDoyvNSsuLIeyEh2ZdRX8ELXTaRqHynVaUgrakUiEyr9Q> <xmx:gIGCXRriSMhKNcI-6HV5n5wfWetGmXm3X5c0m64UUspCnPud7q9PwQ>
Received: from rtp-alcoop-nitro2.cisco.com (unknown [173.38.117.93]) by mail.messagingengine.com (Postfix) with ESMTPA id C1FAE80064; Wed, 18 Sep 2019 15:11:59 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <904a88e9-440f-ba77-cab0-b06e071ec172@alum.mit.edu>
Date: Wed, 18 Sep 2019 15:11:57 -0400
Cc: Dhruv Dhody <dhruv.ietf@gmail.com>, General Area Review Team <gen-art@ietf.org>, pce@ietf.org, draft-ietf-pce-stateful-hpce.all@ietf.org, Daniel King <daniel@olddog.co.uk>
Content-Transfer-Encoding: quoted-printable
Message-Id: <14028402-EA9C-4C3F-8199-54D33893739C@cooperw.in>
References: <8bc6f14c-3c4b-9d00-e920-4bebf4c58f15@alum.mit.edu> <CAB75xn4APq=Cr3fSNz_W7C1zEd7bga3vMvK8=cKLivhPmVBCpg@mail.gmail.com> <904a88e9-440f-ba77-cab0-b06e071ec172@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/faNbSUlLoZUtoAfk-HzMc0ZT-sI>
Subject: Re: [Pce] [Gen-art] Gen-ART Last Call review of draft-ietf-pce-stateful-hpce-11
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Sep 2019 19:12:04 -0000

Paul, thanks for your review. Dhruv, thanks for the updates. I entered a =
No Objection ballot.

Alissa


> On Aug 21, 2019, at 1:12 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> =
wrote:
>=20
> Dhruv,
>=20
> Thanks for addressing my concerns.
>=20
> Regarding (C-E / E-C) and (EC-EP / EP-EC): I recognized that there was =
more to it, and that using "E" for P-PCE in this document would be =
problematic. I guess this is just a conflict between documents that has =
to be tolerated.
>=20
> And it hadn't dawned on me that the linking issues were artifacts of =
the automatic generation mechanism.
>=20
> 	Thanks,
> 	Paul
>=20
> On 8/21/19 7:26 AM, Dhruv Dhody wrote:
>> Hi Paul,
>> Thanks for your review, please see inline...
>> On Tue, Aug 20, 2019 at 9:58 PM Paul Kyzivat <pkyzivat@alum.mit.edu> =
wrote:
>>>=20
>>> I am the assigned Gen-ART reviewer for this draft. The General Area
>>> Review Team (Gen-ART) reviews all IETF documents being processed
>>> by the IESG for the IETF Chair.  Please treat these comments just
>>> like any other last call comments.
>>>=20
>>> For more information, please see the FAQ at
>>>=20
>>> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>>>=20
>>> Document: draft-ietf-pce-stateful-hpce-11
>>> Reviewer: Paul Kyzivat
>>> Review Date: 2019-08-20
>>> IETF LC End Date: 2019-08-28
>>> IESG Telechat date: ?
>>>=20
>>> Summary:
>>>=20
>>> This draft is basically ready for publication, but has nits that =
should
>>> be fixed before publication.
>>>=20
>>> Issues:
>>>=20
>>> Major: 0
>>> Minor: 0
>>> Nits:  7
>>>=20
>>> 1) NIT: No glossary
>>>=20
>>> Since I am not familiar with the subject domain, when I started =
reading
>>> this document I felt I was lost among the acronyms. While you are =
good
>>> at defining these at first use, I couldn't keep them all in mind as =
I
>>> read. I had to create my own glossary to support me while reading. I
>>> would really appreciate having a glossary in the document.
>>>=20
>> Added.
>>> 2) NIT: Inconsistent terminology
>>>=20
>>> In section 3 two pairs of terms are introduced: (C-E / E-C) and =
(EC-EP /
>>> EP-EC). IIUC in the first pair "E" stands for "PCE" while in the =
second
>>> pair "E" seems to stand for "Extended", while "P" stands for PCE. I
>>> found this very confusing. I think it would be better to allow "E" =
to
>>> mean the same thing in both pairs. Perhaps you could use "X" to =
stand
>>> for "eXtended". Then there would be clear parallels:
>>>=20
>>> C -> XC
>>> E -> XE
>>>=20
>>> Please consider doing something relieve the confusion.
>>>=20
>> The use of notation C-E and E-C is as per RFC 8231
>> https://tools.ietf.org/html/rfc8231#section-4 where PCC to PCE is
>> (C-E) and PCE to PCC is (E-C). In this document we wanted to =
represent
>> messages between C-PCE (child PCE) to P-PCE (parent PCE) and we used
>> EC-EP for it and the reverse EP-EC for P-PCE to C-PCE communication.
>> This was discussed during shepherd review as well (as we were using =
CE
>> and PE before but that was causing confusion because of the well =
known
>> meaning of those terms in routing).
>> I would like to keep the existing notations that has WG support.
>>> 3) NIT: Badly formed sentence
>>>=20
>>> I can't parse this sentence in section 3.1:
>>>=20
>>>     Procedures as described in [RFC6805] are applied and where the
>>>     ingress C-PCE (Child PCE), triggers a path computation request =
for
>>>     the LER in the domain where the LSP originates, sends a request =
to
>>>     the P-PCE.
>>>=20
>>> Can you rephrase it?
>>>=20
>> Updated.
>>> 4) NIT: Unclear text
>>>=20
>>> In section 3.1 are steps A/B/C/D to be added at the *end*, after =
step
>>> 11? It would help to be explicit.
>>>=20
>>> In step (C) of section 3.2, can you please be explicit about which =
node
>>> is to execute these elements? I think it is PCE5, but I'm not =
certain.
>>>=20
>> Updated.
>>> 5) NIT: Unlinked references
>>>=20
>>> Some RFC references (e.g. [RFC8051] and [RFC8231] in section 1.1, =
and
>>> [RFC8232] in section 3.1) are not linked in the HTML version. I =
suggest
>>> a global search for all such unlinked references in the source.
>>>=20
>> The HTML version of the draft is automatically generated from the =
text
>> version. The `rfcmarkup` is used to render the HTML of the I-D/sRFCs.
>> Specifically, rfcmarkup produces the final HTML using heuristics from
>> the source TXT and this is beyond the control of the authors.
>>> 6) NIT: Bad reference link
>>>=20
>>> In the following from section 3.1:
>>>=20
>>>     Steps 1 to 11 are exactly as described in section 4.6.2 =
(Hierarchical
>>>     PCE End-to-End Path Computation Procedure) of [RFC6805], the
>>>=20
>>> the "section 4.6.2" is linked to the non-existent section 4.6.2 of
>>> *this* document rather than RFC6805.
>>>=20
>>> A similar link to the same spot in section 3.2 is ok.
>>>=20
>> I arranged the words so that rfcmarkup works.
>>> 7) NIT: Outdated references:
>>>=20
>>> IdNits reports outdated references. I trust these will be updated in =
due
>>> course.
>>>=20
>> Updated.
>> Working Copy: =
https://github.com/dhruvdhody/ietf/blob/master/draft-ietf-pce-stateful-hpc=
e-12.txt
>> Diff: =
https://tools.ietf.org/rfcdiff?url1=3Ddraft-ietf-pce-stateful-hpce-11&url2=
=3Dhttps://raw.githubusercontent.com/dhruvdhody/ietf/master/draft-ietf-pce=
-stateful-hpce-12.txt
>> Thanks!
>> Dhruv
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Wed Sep 18 14:01:32 2019
Return-Path: <noreply@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 81026120052; Wed, 18 Sep 2019 14:01:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Roman Danyliw via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-pce-stateful-path-protection@ietf.org, Julien Meuric <julien.meuric@orange.com>, pce-chairs@ietf.org, julien.meuric@orange.com, pce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.101.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Roman Danyliw <rdd@cert.org>
Message-ID: <156884048251.4597.11655493158307521478.idtracker@ietfa.amsl.com>
Date: Wed, 18 Sep 2019 14:01:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/I469noEirAemyCbuwS7qOsYepm0>
Subject: [Pce] Roman Danyliw's No Objection on draft-ietf-pce-stateful-path-protection-10: (with COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Sep 2019 21:01:23 -0000

Roman Danyliw has entered the following ballot position for
draft-ietf-pce-stateful-path-protection-10: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-path-protection/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

** Section 3.2.  It took me a bit to understand that the Path Protection
Association TLV goes in an ASSOCIATION Object per Section 6 of
[I-D.ietf-pce-association-group].  On initial reading of “[t]he Path Protection
Association TLV is an optional TLV for use with the Path Protection Association
Type” this relationship wasn’t clear.  I’d recommend an editorial update to
make it clearer.  I believe this is related Ben Kaduk’s DISCUSS #5 (which I
support).

** Section 3.2  The protection type field specifies the protection type of the
LSP.  Section 1 notes that “one working LSP [can be associated with] one or
more protection LSPs using the generic association mechanism.”  Assuming a case
were multiple protection LSPs are specified, is it valid for the protections
type to be different?

** Section 4.5.  For clarity, I would recommend being precise with the exact
code point names when discussing conflicting combinations of protection types. 
For example, s/1+1 or 1:N/1+1 (i.e., protection type=0x08 or 0x10) or 1:N
(i.e., protection type = 0x04) with N=1 per <insert IANA registry name>/

Baring these combinations, are other any other remaining combinations of
protection types legal given different protection LSPs in the same PPAG (e.g.,
0x1 + 0x2)?

** Editorial Nits:
-- Section 1.  s/effect/affect/

-- Section 1.  Per “When the working LSPs are computed and controlled by the
PCE, there is benefit in a mode of operation where protection LSPs are as
well”, I couldn’t parse the second clause.



From nobody Wed Sep 18 14:09:47 2019
Return-Path: <noreply@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id ADFFB120046; Wed, 18 Sep 2019 14:09:45 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?q?=C3=89ric_Vyncke_via_Datatracker?= <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-pce-stateful-path-protection@ietf.org, Julien Meuric <julien.meuric@orange.com>, pce-chairs@ietf.org, julien.meuric@orange.com, pce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.101.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: =?utf-8?q?=C3=89ric_Vyncke?= <evyncke@cisco.com>
Message-ID: <156884098570.4585.6466973426120663299.idtracker@ietfa.amsl.com>
Date: Wed, 18 Sep 2019 14:09:45 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/zaIP9a8mxVB1dGa4IDrBcK_lpBs>
Subject: [Pce] =?utf-8?q?=C3=89ric_Vyncke=27s_No_Objection_on_draft-ietf-?= =?utf-8?q?pce-stateful-path-protection-10=3A_=28with_COMMENT=29?=
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Sep 2019 21:09:46 -0000

Éric Vyncke has entered the following ballot position for
draft-ietf-pce-stateful-path-protection-10: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-path-protection/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you for the work put into this document. I am trusting the routing AD for
their deep understanding of this document and their approval.

Nevertheless, I have 2 COMMENTs which are mere questions of mine.

Regards,

-éric

== COMMENTS ==

-- Section 3.2 --
C.1) Any reason to have a field named "unassigned flags" rather than
"reserved"? After all, those bits could be used later for something different
than flags. Also applicable to section 6.2.

C.2) is there any reason the "P", "S" and "PT" are described right to left ?



From nobody Wed Sep 18 15:09:52 2019
Return-Path: <noreply@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 550BF1200C7; Wed, 18 Sep 2019 15:09:50 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Kaduk via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-pce-stateful-hpce@ietf.org, Adrian Farrel <adrian@olddog.co.uk>, pce-chairs@ietf.org, adrian@olddog.co.uk, pce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.101.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Benjamin Kaduk <kaduk@mit.edu>
Message-ID: <156884459034.4565.10696493114905134845.idtracker@ietfa.amsl.com>
Date: Wed, 18 Sep 2019 15:09:50 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/wC03v7c_RlimoylNPVQNmhy8Awc>
Subject: [Pce] Benjamin Kaduk's Discuss on draft-ietf-pce-stateful-hpce-13: (with DISCUSS and COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Sep 2019 22:09:50 -0000

Benjamin Kaduk has entered the following ballot position for
draft-ietf-pce-stateful-hpce-13: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-hpce/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

I think this should be pretty easy to resolve, though I'm not sure what
the right way to do so it.

Section 3 says:

   [I-D.ietf-pce-hierarchy-extensions] defines the H-PCE Capability TLV
   that is used in the Open message to advertise the H-PCE capability.
   [RFC8231] defines the Stateful PCE Capability TLV used in the Open
   message to indicate stateful support.  The presence of both TLVs in
   an Open message indicates the support for stateful H-PCE operations
   as described in this document.

There is no normative reference relationship (in either direction)
between draft-ietf-pce-hierarchy-extension and this document; I think
that the use of the capability TLV to imply both sets of functionality
implies some sort of normative relationship; we wouldn't want version
skew between documents to induce breaking changes.  In particular, an
implementation that already supports RFC 8231 and is implementing the
hierarchy extensions would need to know to look at this document *and
implement it*, or would unknowingly be noncompliant with this document
and fail to interoperate with a peer that is compliant with this
document.


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Abstract

                         This information may then be considered when
   computing new traffic engineered LSPs, and for associated and
   dependent LSPs, received from Path Computation Clients (PCCs). [...]

nit: I'm not sure how to parse this sentence.  The best thing I can come
up with is that "when computing new traffic engineered LSPs" and "for
associated [...]" are two separate cases, which each could independently
consider the information in question.  The first one makes sense, but
for the second I'm left trying to parse "this information may then be
considered for associated and dependent LSPs, received from PCCs", and
it's not really clear what considering the PCE is going to do if it just
sits there with information from the LSP-DB and information from PCCs (and
not doing anything with the information).

   The Hierarchical Path Computation Element (H-PCE) architecture,
   provides an architecture to allow the optimum sequence of
   [...]

nit: no comma here.

Also, three paragraphs may be pushing the bounds of an abstract in RFC
style.

Section 1.1

   path based on the domain connectivity information.  A Child PCE
   (C-PCE) may be responsible for a single domain or multiple domains,
   it is used to compute the intra-domain path based on its domain
   topology information.

nit: comma splice

   This document presents general considerations for stateful PCEs, and
   not Stateless PCEs, in the hierarchical PCE architecture.  In
   particular, the behavior changes and additions to the existing
   stateful PCE mechanisms (including PCE-initiated LSP setup and active
   PCE usage) in the context of networks using the H-PCE architecture.

nit: should "active PCE usage" read "active stateful PCE usage"?

Section 1.2

   The inter-domain LSP could be set up using the end-to-end signaling
   as described in [RFC6805]. Additionally a per-domain stitched LSP

Should I be reading this "could be set up using" as "this document
describes how to set [the LSP] up using"?

Section 1.2.2

   Different signaling methods for inter-domain RSVP-TE signaling are
   identified in [RFC4726].  Contiguous LSPs are achieved using the

nit: are the two "signaling"s redundant?

   In case of a stateful P-PCE, the stateful P-PCE has to be aware of
   the inter-domain LSPs for it to consider them during path
   computation. For example, a domain diverse path from another LSP.

nit: this last sentence is a sentence fragment.

   In this document, for the Contiguous LSP, the above interactions are
   only between the ingress domain C-PCE and the P-PCE. The use of
   stateful operations for an inter-domain LSP between the
   transit/egress domain C-PCEs towards the P-PCE is out of scope of
   this document.

nit: I suggest rewording to avoid the ambiguity of "towards" as applying
to the inter-domain LSP vs. the use of stateful operations.

Section 3

   in the topology).  The P-PCE has no information about the content of
   the child domains.  Each child domain has at least one PCE capable of

nit: we could potentially reword this in light of the remarks made about
ACTN previously.

   computing paths across the domain.  These PCEs are known as C-PCEs
   and have a direct relationship with the P-PCE.  The P-PCE builds the

It might be good to forward-reference where we talk about this
relationship in more detail.  (And, er, have more detail about the
relationship than we currently do.)

   and have a direct relationship with the P-PCE.  The P-PCE builds the
   domain topology map either via direct configuration (allowing network
   policy to also be applied) or from learned information received from
   each C-PCE.

Policy cannot be applied to information learned at runtime?

   LSP State Report (EC-EP):  a child stateful PCE sends an LSP state
      report to a Parent Stateful PCE whenever the state of a LSP
      changes.

With respect to "whenever the state of a LSP changes", is there a
possibility of a state-change that is visible to the C-PCE but does not
affect anything that the P-PCE knows about?  Is the state report still
expected to be generated in such cases?

   object to identify the Ingress (PCC). The PLSP-ID used in the
   forwarded PCRpt by the C-PCE to P-PCE is same as the original one
   used by the PCC.

I couldn't quickly find an authoritative definition of what the PLSP-ID
is; I see some discussion in RFC 8231 for the LSP Object, but am not
sure if there is prior usage.

Section 3.1

   paths.  Each C-PCE computes a set of candidate path segments across
   its domain and sends the results to the P-PCE. The P-PCE uses this
   information to select path segments and concatenate them to derive
   the optimal end-to-end inter-domain path.  The end-to-end path is
   then sent to the C-PCE that received the initial path request, and
   this C-PCE passes the path on to the PCC that issued the original
   request.

This is basically the same language as in RFC 6805, so I don't really
expect changing it to be the right thing to do, but I'm confused about
how the P-PCE is getting "candidate" segments from the C-PCEs but only
has to tell the head-end which path got picked.  Are the other C-PCEs
supposed to find out which of the candidates got used somehow?

Section 3.2

   a PCUpd message.  For LSP delegated to the P-PCE via the child PCE,
   the P-PCE can use the same PCUpd message to request change to the C-
   PCE (the Ingress domain PCE), the PCE further propagates the update
   request to the PCC.

nit: comma splice

Section 4

I expect this to not be the case, but just to check: is there a
possibility for differing levels of authorization for different PCCs,
e.g., where PCC A is allowed to request LSPs within the domain and to
any other domain, but PCC B is not allowed to request LSPs to/through a
subset of domain peers, and PCC C is only allowed to request LSPs within
the local domain?

As Roman mentions, we don't have a picture of what "full security" means
for child/parent communications.

   Thus it is RECOMMENDED to secure the PCEP session (between the P-PCE
   and the C-PCE) using either Transport Layer Security (TLS) [RFC8253]
   per the recommendations and best current practices in [RFC7525] or
   TCP Authentication Option (TCP-AO) [RFC5925].

It's not entirely clear to me that we need to call out TCP-AO here.
Partially since, as Stephen noted in the secdir review, it doesn't seem
to be implemented/deployed much, but also since RFC 8231 does call out
that it recommends TLS for confidentiality protection, which TCP-AO does
not provide.  There don't seem to be specific threats enumerated there
that the confidentiality protects against, so I am not making a strong
recommendation to remove TCP-AO from this text, but I'd like to better
understand why it was added.

   In case of TLS, due care needs to be taken while exposing the
   parameters of the X.509 certificate, such as subjectAltName:otherName
   which is set to Speaker Entity Identifier [RFC8232] as per [RFC8253],
   to ensure uniqueness and avoid any mismatch.

I'm not entirely sure which "mismatch" we would be concerned about.
And just to check: there aren't expected to be any privacy-like
considerations for exposing the speaker entity identifier to a peer in a
different domain, right?

Section 5.7

I'm not sure how appropriate it is to fully delegate (e.g.) propagation
of errors to draft-ietf-pce-enhanced-errors (which is not even a
normative reference!) -- it seems important to describe some expectation
of the error handling either in this document or in a normative
reference thereof.

Section 9.2

I think RFCs 5925, 7525, and 8253 should be normative, and RFC 7525 can
be cited as BCP 195.



From nobody Thu Sep 19 13:21:38 2019
Return-Path: <kaduk@mit.edu>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0925120129; Thu, 19 Sep 2019 13:21:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9tEyr8520-ZV; Thu, 19 Sep 2019 13:21:11 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEC5712006A; Thu, 19 Sep 2019 13:21:10 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x8JKKj5t005187 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 19 Sep 2019 16:20:55 -0400
Date: Thu, 19 Sep 2019 15:20:44 -0500
From: Benjamin Kaduk <kaduk@mit.edu>
To: Dhruv Dhody <dhruv.ietf@gmail.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pce-stateful-pce-auto-bandwidth@ietf.org, Adrian Farrel <adrian@olddog.co.uk>, pce-chairs <pce-chairs@ietf.org>, pce@ietf.org
Message-ID: <20190919202036.GA48975@kduck.mit.edu>
References: <156874887441.17499.7855633347557404477.idtracker@ietfa.amsl.com> <CAB75xn5MUrTS43f5boMo4Kq7dfCo+YmLu1Qh_Qf-XN9hXLKsww@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAB75xn5MUrTS43f5boMo4Kq7dfCo+YmLu1Qh_Qf-XN9hXLKsww@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/TiqjwxGVa2hacY6t3m9QHiz3lqY>
Subject: Re: [Pce] Benjamin Kaduk's Discuss on draft-ietf-pce-stateful-pce-auto-bandwidth-11: (with DISCUSS and COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Sep 2019 20:21:15 -0000

Hi Dhruv,

On Wed, Sep 18, 2019 at 08:16:20PM +0530, Dhruv Dhody wrote:
> Hi Ben,
> 
> Thanks for your review. Please see inline...
> 
> On Wed, Sep 18, 2019 at 1:04 AM Benjamin Kaduk via Datatracker
> <noreply@ietf.org> wrote:
> >
> > Benjamin Kaduk has entered the following ballot position for
> > draft-ietf-pce-stateful-pce-auto-bandwidth-11: Discuss
> >
> > When responding, please keep the subject line intact and reply to all
> > email addresses included in the To and CC lines. (Feel free to cut this
> > introductory paragraph, however.)
> >
> >
> > Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> > for more information about IESG DISCUSS and COMMENT positions.
> >
> >
> > The document, along with other ballot positions, can be found here:
> > https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-pce-auto-bandwidth/
> >
> >
> >
> > ----------------------------------------------------------------------
> > DISCUSS:
> > ----------------------------------------------------------------------
> >
> > This document seems generally useful, and thanks for it.  I think
> > there's a couple places where it's ambiguous or unclear, and hopefully
> > we can tighten up the language without needing extensive changes.
> >
> > There may be an internal inconsistency in Section 2.3's definitions
> > relating the Overflow-Count and the Overflow-Threshold: the description
> > of Overflow-Count reads as if it is a reported quantity, but the
> > description of Overflow-Threshold implies that Overflow-Count is a
> > configured parameter.  (Similarly for the Underflow- variants.)
> > Specifically, the sentence "[t]his value indicates how many times
> > consecutively, the percentage or absolute difference between the current
> > MaxAvgBw and the current bandwidth reservation of the LSP is greater
> > than or equal to the Overflow-Threshold value" uses the descriptive
> > verb "is" as opposed to a conditional such as "needs to be [...] in
> > order to [...]".
> >
> 
> Updated.
> 
> > Section 5.2.3.2 says:
> >
> >    If the percentage difference between the current MaxAvgBw and the
> >    current bandwidth reservation is greater than or less than or equal
> >    to the threshold percentage, the LSP bandwidth is adjusted to the
> >    current bandwidth demand (MaxAvgBw) (as long as the difference in the
> >    bandwidth is at least or above the Minimum-Threshold).
> >
> > As written ("greater than or less than or equal to"), this is always
> > true, which cannot be what was intended.  Probably we should reword to
> > just "greater than" and talk about the percentage absolute difference,
> > i.e., 100 * abs(MaxAvgBw - CurrentRes) / CurrentRes .
> >
> 
> Updated.
> 
> >
> > ----------------------------------------------------------------------
> > COMMENT:
> > ----------------------------------------------------------------------
> >
> > As a general note, I'm not sure the phrase "calculated bandwidth to be
> > adjusted" is a great fit for how it's currently being used.
> > Specifically, the "calculation" in question seems to just be taking the
> > maximum of a sliding window of per-timeslice average bandwidth values,
> > and this seems like a sufficiently small amount of computation that I'd
> > be comfortable describing it as a "measurement", for "measured bandwidth
> > as input to path calculation".  That is, this doesn't seem like it comes
> > close to the amount of computation involved in actually computing paths,
> > so I keep misreading what information is being sent where.
> >
> 
> In an earlier version there was a feature where the PCC could report
> the measured value at each sample interval (it moved to another
> document). IMHO for the clarity in the WG, it is still better to
> differentiate between the raw measured value (telemetry) and the value
> that is currently reported which is marked as "calculated".

Ah, in that context it makes more sense to do it this way.  Perhaps an
informative reference to the other document/usage and note about the
terminology would help, though?

> > Section 1
> >
> >    Over time, based on the varying traffic pattern, an LSP established
> >    with a certain bandwidth may require to adjust the bandwidth reserved
> >    in the network dynamically.  The head-end Label Switch Router (LSR)
> >    monitors the actual bandwidth demand of the established LSP and
> >    periodically computes new bandwidth.  The head-end LSR adjusts the
> >    bandwidth reservation of the LSP based on the computed bandwidth
> >    automatically.  This feature is commonly referred to as Auto-
> >    Bandwidth.  The Auto-Bandwidth feature is described in detail in
> >    Section 4 of this document.
> >
> > >From just this text, I can't tell if this is describing the mechanisms of
> > this document or an existing Auto-Bandwidth feature that is related to
> > the mechanisms of this document.
> >
> 
> The auto-bandwidth feature without PCE exists, where the ingress does
> the measurement as well as path computation. This feature has been
> implemented long back but was not part of any standard because it was
> a local implementation at the ingress node and no protocol changes was
> required. With the PCE things changed and here we are...

Ah, I see.  Maybe "This feature, when available in the head-end LSR
implementation, is common referred to as [...]", then?

> >    In the model considered in this document, the PCC (head-end of the
> >    LSP) collects the traffic rate samples flowing through the LSP and
> >    calculates the new adjusted bandwidth.  The PCC reports the
> >    calculated bandwidth to be adjusted to the PCE.  This is similar to
> >    the Passive stateful PCE model, while the Passive stateful PCE uses
> >    path request/reply mechanism, the Active stateful PCE uses
> >    report/update mechanism.  [...]
> >
> > nit: I think the punctuation in this last sentence needs some tweaking,
> > as there looks to be a comma splice at present.
> > (It's also unclear how much we need to talk about Passive stateful PCE,
> > since just two paragraphs ago we say we focus on Active stateful PCE in
> > this document.)
> >
> 
> This was updated based on Barry's suggestion. It makes sense to
> include a sentence here in Introduction to set the stage.

Barry's text looks great, thanks.

> >    This document defines the PCEP extensions needed to support Auto-
> >    Bandwidth feature in a Active stateful PCE model where the LSP
> >    bandwidth to be adjusted is calculated on the PCC (head-end of the
> >    LSP). The use of PCE to calculate the bandwidth to be adjusted is out
> >    of scope of this document.
> >
> > Maybe I'm just confused about active vs. passive in general, but I
> > thought that active stateful PCE involved the PCE "making the decisions"
> > with the PCC just providing input data.  But here we're saying that the
> > PCC is making the bandwidth decision, even though the rest of the LSP
> > computation remains on the PCE?
> 
> Yes, this is correct. The calculated bandwidth is still an input for
> PCE to make the path computation taking that as an input.
> 
> > Or is "calculate the bandwidth to be
> > adjusted" referring to "evaluate the expression max_{time periods}(avg.
> > bandwidth per time period)" (as opposed to "compute the bandwidth
> > adjustment to make)?
> >
> 
> It is the former.
> 
> > Section 2.3
> >
> > Are we assuming any relationship between the Up-Adjustment-Threshold and
> > the Overflow-Threshold?
> >
> 
> Yes, as mentioned here while describing Overflow-Threshold -
> 
>       The LSP bandwidth is adjusted to the
>       current bandwidth demand bypassing the Up-Adjustment-Interval if
>       the overflow condition is met consecutively for the Overflow-
>       Count.

I was thinking more along the lines of if the Overflow-Threshold value was
going to be a larger number than the Up-Adjustment-Threshold.

> 
> >       traffic demand.  If the percentage or absolute difference between
> >       the current MaxAvgBw and the current bandwidth reservation of the
> >       LSP is greater than or equal to the threshold value, the overflow
> >       condition is set to be met.  The LSP bandwidth is adjusted to the
> >
> > nit: I think s/set to be met/said to be met/ ?  (this appears twice)
> >
> 
> Ack
> 
> >    Minimum-Threshold:  The increase or decrease of the LSP bandwidth
> >       should be at least or above the minimum-threshold represented as
> >       an absolute bandwidth value before the bandwidth adjustment for
> >       the LSP is made.  This threshold can be seen as a suppression
> >       threshold that is used along with a percentage threshold to avoid
> >       unnecessary auto-bandwidth adjustments and re-signaling of the LSP
> >       at low bandwidth values.
> >
> > I can't tell from this text if this threshold is a (LSP) bandwidth
> > value/measurement or a bandwidth offset between configured and measured
> > values.  (The subsequent protocol element definitions are more clear
> > that it's the latter.)
> >
> 
> It is latter. Do you have a suggested change, I am not sure what change to make.

How about:

   Minimum-Threshold:  When percentage-based thresholds are in use, they
      are accompanied by this minimum threshold, which is used to enforce
      that the magnitude of deviation of calculated LSP bandwidth from the
      reserved bandwidth exceeds a specific non-percentage-based criterion
      before any adjustments are made.  This serves to suppress unnecessary
      auto-bandwidth adjustments and re-signaling of the LSP at low
      bandwidth values.


> > Section 3
> >
> > The column headings in Table 1 refer to who initiates the LSP in
> > question, right?
> >
> 
> yes
> 
> >    The PCEP speaker supporting this document must have a mechanism to
> >    advertise the automatic bandwidth adjustment capability for both PCC-
> >    Initiated and PCE-Initiated LSPs.
> >
> > Just checking on "must" vs. "MUST" here.
> >
> 
> The use of normative for requirements for the protocol extensions may
> not be required. .
> 
> >    o  It is required to identify and inform the PCC, which LSPs are
> >       enabled with Auto-Bandwidth feature.  Not all LSPs in some
> >       deployments would like their bandwidth to be dependent on the
> >       real-time bandwidth usage but be constant as set by the operator.
> >
> > nit: I suggest NEW:
> >
> > %  o  It is required to identify and inform the PCC which LSPs have
> > %     enabled the Auto-Bandwidth feature.  Not all LSPs in some
> > %     deployments would like their bandwidth to be dependent on the
> > %     real-time bandwidth usage; for some LSPs leaving the bandwidth
> > %     constant as set by the operator is preferred.
> >
> 
> Ack
> 
> > Section 4.2
> >
> >    When the Auto-Bandwidth feature is enabled, the measured traffic rate
> >    is periodically sampled at each Sample-Interval (which can be
> >    configured by an operator and the default value as 5 minutes) by the
> >    PCC, when the PCC is the head-end node of the LSP.  The traffic rate
> >
> > Do we cover what happens in the case when the PCC is not the head-end
> > node of the LSP?
> >
> 
> No.

Should we document that somewhere?

> > Section 5.1
> >
> >    o  The PCEP speaker that does not recognize the extensions defined in
> >       this document sends the PCErr message with error-type 2
> >       (capability not supported) as per Section 6.9 in [RFC5440].
> >
> > This refers to when the actual new messages (e.g.,
> > AUTO-BANDWIDTH-ATTRIBUTES TLV) are being used, not merely advertising
> > the Auto-Bandwidth Capability TLV in the OPEN object, right?  That is,
> > this is descriptive language of what the core protocol spec mandates as
> > error handling in the presence of unrecognized input?
> >
> 
> This is a mistake, that error is only for unknown message. Will fix this.
> 
> > Section 5.1.1
> >
> > nit: in the previous section we captialized this as "Auto-Bandwidth
> > Capability", but here (including the section heading) it is
> > "AUTO-BANDWIDTH-CAPABILITY".  Should they be consistent?
> >
> 
> Updated
> 
> > Section 5.2
> >
> >    Future specification can define additional sub-TLVs.
> >
> > I see that we see later that unrecognized sub-TLVs are ignored, but
> > would there be a case where we want to use a bit in the
> > AUTO-BANDWIDTH-CAPABILITY flags to negotiate support for a sub-TLV
> > (i.e., to confirm that the peer will understand it, instead of just
> > sending it and not knowing if it is understood)?
> >
> 
> I guess a future extension that defines any new sub-TLV for
> auto-bandwidth could take that approach.
> 
> > Section 5.2.1
> >
> > It sounds like we should ignore values larger than 7 days as well
> > (rather than erroring out)?
> >
> 
> Updated
> 
> > Section 5.2.2, 5.2.3
> >
> > I'd like to see a little bit more detail specified of the interaction
> > between (regular) Adjustment-{Interval,Threshold} and
> > Down-Adjustment-{Interval,Threshold}.  We do have this text about (e.g.)
> > "[t]he Adjustment-Interval sub-TLV specifies the time interval for both
> > upward and downward trend", which conveys the general intent, but I'm
> > not sure I have all the details about there being one default value,
> > that applies to both, and changes to the (regular) parameter continue to
> > apply to both, until an explicit Down- variant is seen, at which point
> > the control of the two parameters diverge permanently and they must
> > always be separately controlled.
> >
> 
> Updated
> 
> > Section 5.2.3.1
> >
> >    o  Adjustment-Threshold: The absolute Adjustment-Threshold bandwidth
> >       value, encoded in IEEE floating point format (see
> >
> > nit: I'd suggest that this is a bandwidth *difference* value (or offset),
> > pedantically speaking.  (The following paragraph is quite clear on the
> > actual usage, though, so this is nit-level.)  This comment applies to
> > basically all the threshold fields in the document, but I'll just make
> > it once, here.
> >
> 
> Updated
> 
> > Section 5.2.3.2
> >
> >    o  Reserved: SHOULD be set to zero on transmission and MUST be
> >       ignored on receipt.
> >
> > I think the formulation of "MUST be set to zero on transmission and
> > SHOULD be ignored on receipt" is more common.
> >
> 
> Changed to MUST for both.
> 
> >    o  Percentage: The Adjustment-Threshold value (7 bits), encoded in
> >       percentage (an integer from 1 to 100).  The value 0 is considered
> >       to be invalid.  The default value is 5 percent.
> >
> > I assume that the question of whether to allow sub-percentage
> > granularity came up, and don't want to revisit the WG's decision.  But
> > please confirm that it was discussed.
> >
> 
> I don't have a thread to point to where this was explicitly talked
> about. But I believe we have WG consensuses for this.

That's good enough for me, thanks.

> > Also, are values over 100 also "invalid"?  What should the recipient do
> > upon receipt of an invalid value?
> >
> >    If the percentage difference between the current MaxAvgBw and the
> >    current bandwidth reservation is greater than or less than or equal
> >    to the threshold percentage, the LSP bandwidth is adjusted to the
> >    current bandwidth demand (MaxAvgBw) (as long as the difference in the
> >    bandwidth is at least or above the Minimum-Threshold).
> >
> > I'd suggest rewording to make the two criteria equal peers (e.g., "If X
> > and Y") rather than relegating the minimum-threshold to a parenthetical
> > that's easy to ignore.
> >
> 
> Ack
> 
> > Section 5.2.3.3
> >
> > It would probably be good to reiterate here (and at other similar
> > locations) that this "is used to decide" only when there's a need for
> > different behavior in the upward and downard directions.
> >
> > Also, nit-level, I think "overrides" is more appropriate than
> > "overwrites", since the non-Down- variant remains active for its
> > separate role.
> >
> 
> Ack
> 
> > Section 5.2.4.2
> >
> >       per second.  The default maximum-bandwidth value is not set.
> >
> > I guess effectively the default is FLOAT_MAX, inherited from RFC 5440.
> >
> 
> Yes
> 
> > Section 5.2.5.1
> >
> >    o  Overflow-Threshold: The absolute Overflow-Threshold bandwidth
> >       value, encoded in IEEE floating point format (see
> >       [IEEE.754.1985]), expressed in bytes per second.  Refer to Section
> >       3.1.2 of [RFC3471] for a table of commonly used values.  If the
> >       increase of the current MaxAvgBw from the current bandwidth
> >       reservation is greater than or equal to the threshold value, the
> >       overflow condition is met.
> >
> > nit: I'd suggest to s/increase/difference/, since (IIUC) the operation
> > here is "observed bandwidth remains above the (reservation plus)
> > threshold for <count> times", not "observed bandwidth increases in
> > successive reporting intervals".  This assumes that the
> > Adjustment-Interval is larger than <count> times the reporting interval,
> > of course.
> >
> 
> Updated
> 
> > Section 5.2.5.3
> >
> >    o  Underflow-Threshold: The absolute Underflow-Threshold bandwidth
> >       value, encoded in IEEE floating point format (see
> >       [IEEE.754.1985]), expressed in bytes per second.  Refer to Section
> >       3.1.2 of [RFC3471] for a table of commonly used values.  If the
> >       decrease of the current MaxAvgBw from the current bandwidth
> >       reservation is greater than or equal to the threshold value, the
> >       underflow condition is met.
> >
> > As above, I suggest s/decrease/difference/ (perhaps with an additional
> > indication that the magnitude of the difference is to be used, not the
> > signed difference).
> >
> 
> Updated
> 
> > Section 5.7
> >
> > I'm not sure I understand why there's a need for an
> > auto-bandwidth-specific "overload" notification, as opposed to having
> > such messages suppressed as part of a more general overload condition.
> > But that doesn't mean there's not a need, of course, as I'm not very
> > familiar with this area!
> >
> 
> The auto-bandwidth feature increases the rate of message exchange and
> path computation. So in case of an overload because of auto-bandwidth
> it would be good for a PCEP speaker to indicate that. Also the general
> overload only worked in one direction 'PCE to PCC'. Here PCE could
> send to many updates to PCC and making PCC to be overloaded as well.

Thanks for the explanation; I understand better now.

> > Section 6.6
> >
> >    An implementation MAY allow a limit to be placed on the rate of auto-
> >    bandwidth related messages sent by a PCEP speaker and received by a
> >    peer.  An implementation MAY also allow sending a notification when a
> >    PCEP speaker is overwhelmed or the rate of messages reach a
> >    threshold.
> >
> > I don't want to revisit a WG consensus outcome, but I could see "SHOULD"
> > for "allow sending a notification", noting that it is "SHOULD allow
> > sending" and not "SHOULD send".
> >
> 
> Updated
> 
> > Section 7
> >
> >    This document defines AUTO-BANDWIDTH-CAPABILITY TLV and AUTO-
> >    BANDWIDTH-ATTRIBUTES sub-TLVs which do not add any new security
> >    concerns beyond those already discussed in [RFC8231] and [RFC8281]
> >
> > I'd suggest to qualify this as "do not add any substantial new security
> > concerns".  We did just in the previous section talk about how this
> > functionality could increase computational and operational load, which,
> > taken to an extreme, can affect availability and could be considered a
> > security consideration.
> >
> > We could also perhaps give guidance about setting the min and max
> > bandwidth sub-TLVs to constrain automatic adjustment to be within a
> > known range and thus bound the extent of second-order effects on the
> > rest of the MPLS-TE domain.
> >
> 
> Updated
> 
> > Section 8.2
> >
> > It might be good to say within what registry the sub-registry being
> > created is to be located.
> >
> > Also, the last paragraph could perhaps be rephrased as "the initial
> > contents of the registry are empty, with all bits unassigned".
> >
> 
> Ack
> 
> > Section 9.2
> >
> > I think that the RFC 7525 and 8253 references fall under the RECOMMENDED
> > guidance in Section 7, in which case per
> > https://www.ietf.org/about/groups/iesg/statements/normative-informative-references/
> > they should be classified as Normative references.  (It's probably also
> > good to cite RFC 7525 as BCP 195 and not just RFC 7525.)
> >
> > The IEEE.754 reference is also normative since we use its wire encoding
> > (but it could practically be considered "well-known" at this point,
> > given its ubiquity).
> >
> >
> 
> Ack
> 
> Diff: https://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=draft-ietf-pce-stateful-pce-auto-bandwidth-11&url2=https://raw.githubusercontent.com/dhruvdhody/ietf/master/draft-ietf-pce-stateful-pce-auto-bandwidth-12.txt
> 
> Working Copy: https://raw.githubusercontent.com/dhruvdhody/ietf/master/draft-ietf-pce-stateful-pce-auto-bandwidth-12.txt

Thanks!

-Ben


From nobody Thu Sep 19 14:03:11 2019
Return-Path: <kaduk@mit.edu>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC1E8120152; Thu, 19 Sep 2019 14:03:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yVtSuP9l5nVy; Thu, 19 Sep 2019 14:03:00 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5B5A120129; Thu, 19 Sep 2019 14:02:59 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x8JL2iC8032375 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 19 Sep 2019 17:02:50 -0400
Date: Thu, 19 Sep 2019 16:02:43 -0500
From: Benjamin Kaduk <kaduk@mit.edu>
To: Dhruv Dhody <dhruv.ietf@gmail.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pce-stateful-path-protection@ietf.org, Julien Meuric <julien.meuric@orange.com>, pce-chairs <pce-chairs@ietf.org>, pce@ietf.org
Message-ID: <20190919210236.GB48975@kduck.mit.edu>
References: <156876388231.17411.6094234033866939217.idtracker@ietfa.amsl.com> <CAB75xn4L2RE0vo44bt332kUL7Nh=LryKpJ3BSHRRnHggz8v3vQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAB75xn4L2RE0vo44bt332kUL7Nh=LryKpJ3BSHRRnHggz8v3vQ@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/paJvzxkBhbvnh4Mo6PDOtni5x3U>
Subject: Re: [Pce] Benjamin Kaduk's Discuss on draft-ietf-pce-stateful-path-protection-10: (with DISCUSS and COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Sep 2019 21:03:03 -0000

Hi Dhruv,

On Wed, Sep 18, 2019 at 11:45:23AM +0530, Dhruv Dhody wrote:
> Hi Ben,
> 
> Thanks for your review, let me start the discussion and the authors
> can interject as needed.

Thanks; it's a great start.

> On Wed, Sep 18, 2019 at 5:14 AM Benjamin Kaduk via Datatracker
> <noreply@ietf.org> wrote:
> >
> > Benjamin Kaduk has entered the following ballot position for
> > draft-ietf-pce-stateful-path-protection-10: Discuss
> >
> > When responding, please keep the subject line intact and reply to all
> > email addresses included in the To and CC lines. (Feel free to cut this
> > introductory paragraph, however.)
> >
> >
> > Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> > for more information about IESG DISCUSS and COMMENT positions.
> >
> >
> > The document, along with other ballot positions, can be found here:
> > https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-path-protection/
> >
> >
> >
> > ----------------------------------------------------------------------
> > DISCUSS:
> > ----------------------------------------------------------------------
> >
> > (1) draft-ietf-pce-association-group notes that "PCEP extensions that define
> > a new association type should clarify the relationship between the SVEC
> > object and the association type, if any".  Where do we do so for the
> > path protection association type?
> >
> 
> This is discussed in
> https://tools.ietf.org/html/draft-ietf-pce-association-diversity-10#section-5.3,
> where it is more relevant. This draft includes the relationship with
> diversity association in Section 5.

A naive reading of the linked section would be that it applies only to the
"Disjointness Association Type" defined in that document.  I'm not in a
position to claim that the reasoning in that document does not apply to
this one, but I think we should make a more clear link between the Path
Protection ASsociation Type and the discussion in that document.

> > (2) Section 3.2 says:
> >
> >       Protection Type (PT): 6 bits - This field is as defined in
> >       Section 14.1 of [RFC4872] to indicate the LSP protection type in
> >       use.
> >
> > There doesn't seem to be a registry created by RFC 4872 to track these
> > PT values, so I assume that the way to allocate a new value is
> > "standards-track RFC that Updates: RFC 4872".  Is that also the way to
> > allocate new PT values for PPAG usage?  How would someone updating RFC
> > 4872 to allocate a new type know to consider/document whether it applies
> > for PPAG usage?
> >
> 
> That's true. Maybe we can add this text - "Any type already defined or
> that could be defined in the future for use in the RSVP-TE PROTECTION
> object is acceptable in this TLV unless explicitly stated otherwise."

To be honest, that's probably good enough in practice, since it seems
somewhat unlikely that the last bit is ever going to get allocated (though,
I guess technically the field could be converted to an integer instead of
flags).  I do still have to wonder how the reader would know *where* it
would be stated otherwise, and how the author of a document defining a new
type would know to consider our use case as well as the RFC 4872 use case.

> > (3) In Section 4.3:
> >
> >    A PCE can create/update working and protection LSPs independently.
> >    As specified in [I-D.ietf-pce-association-group], Association Groups
> >    can be created by both the PCE and the PCC.  Further, a PCE can
> >
> > The requirement that source, destination, and tunnel ID of all LSPs
> > within a PPAG MUST be the same is new to this document, so I think we
> > need to specify error handling for when attempts to update LSPs
> > independently would violate that invariant (presumably in Section 4.5).
> >
> 
> In the existing error case in Section 4.5 we could make it "add or update".

Wording it right might be a little finicky, but that's fine in general.

> > (4) In Section 6.3:
> >
> >                                       IANA is requested to allocate new
> >    error values within the "PCEP-ERROR Object Error Types and Values"
> >    sub-registry of the PCEP Numbers registry, as follows:
> >
> > The following table only lists Error-values.  What Error-type(s) should
> > they be associated with?
> >
> 
> It is mentioned in the text, but worth making it explicit in the table as well.
> 
> > (5) We don't say which objects the PPAG TLV can appear in.  (Section 3.2
> > says "[t]he Path Protection Association TLV is an optional TLV for use
> > with the Path Protection Association Type", but it's hard to interpret
> > that as meaning "for use [only] with the ASSOCIATION object defined in
> > draft-ietf-pce-association-group", especially since there is a "path
> > protection association type" already (and it's a codepoint in the
> > "ASSOCIATION Type Field" registry).
> >
> 
> We can update to - "The Path Protection Association TLV is an optional
> TLV for use in the ASSOCIATION Object with the Path Protection
> Association Type."

Thanks!

> > (6) I'm not sure if a change to the document is needed here, but perhaps
> > some discussion is in order: we say that a given LSP can belong to more
> > than one PPAG, but only allow one PPAG TLV per [some context that
> > remains unclear; see (5)].  I don't have a good handle for whether these
> > two requirements are potentially in conflict: that is, whether a single
> > PPAG TLV would have to specify the flags that apply for both PPAGs that
> > a given LSP is a member of, or if the containing objects serve to scope
> > the PPAG TLV flags' interpretation.
> >
> 
> When a given LSP belong to more than one PPAG, we expect to have
> multiple ASSOCIATION Object for each PPAG with each of them having a
> single PPAG TLV.

Sounds good, and quite natural given (5).

> > (7) Do the Protection Type fields of the PPAG TLV in the various LSPs
> > that are members of the same PPAG need to match, in the same way that
> > the source/destination/tunnel-ID do?
> >
> 
> Yes. Authors should make that explicit.

Thanks

> >
> > ----------------------------------------------------------------------
> > COMMENT:
> > ----------------------------------------------------------------------
> >
> > Section 1
> >
> >    This document specifies a stateful PCEP extension to associate two or
> >    more LSPs for the purpose of setting up path protection.  The
> >    proposed extension covers the following scenarios:
> >
> > nit: after publication, it doesn't really seem like a *proposed*
> > extension anymore.
> >
> > Section 3.1
> >
> >    LSPs are not associated by listing the other LSPs with which they
> >    interact, but rather by making them belong to an association group
> >    referred to as "Path Protection Association Group" (PPAG) in this
> >    document.  [...]
> >
> > The first 2/3 of this sentence is a (true) generic statement about all
> > association groups, which exist outside of this document in a generic
> > fashion.  I strongly suggest rewording this to make clear that the PPAG
> > is the specific association (group) type used for this document's
> > functionality but that other association groups are possible.  The
> > current wording implies that the PPAG is the only association possible,
> > and it is just given a special name for this document's purposes.
> >
> >    [I-D.ietf-pce-association-group] specifies the mechanism for the
> >    capability advertisement of the Association types supported by a PCEP
> >    speaker by defining a ASSOC-Type-List TLV to be carried within an
> >    OPEN object.  This capability exchange for the Association type
> >    described in this document (i.e.  Path Protection Association Type)
> >    MAY be done before using the policy association, i.e., the PCEP
> >    speaker MAY include the Path Protection Association Type (TBD1) in
> >    the ASSOC-Type-List TLV before using the PPAG in the PCEP messages.
> >
> > Why is this only MAY and not MUST?
> >
> 
> In [I-D.ietf-pce-association-group] we explicitly did not mandate the
> capability exchange for all association types and let each type decide
> for itself. This association type fits into where the capability
> exchange is optional. When the capability exchange was added in
> [I-D.ietf-pce-association-group], there was a desire from the WG to
> keep it optional for already defined/implemented protection
> association type. Also this is a basic feature in path computation and
> it is expected to be supported universally. In a corner case there is
> an error handling for unknown/unsupported association-type to take
> care of it.

Okay, thanks for giving me the backstory.

> >    This Association type is dynamic in nature and created by the PCC or
> >
> > nit: is it the type that is dynamic or the associations of that type?
> >
> 
> It is the type. [I-D.ietf-pce-association-group] has dynamic or
> operator-configured association, this one is dynamic.

Ah, of course, I had forgotten about that division of configuration.

> >       Protecting (P): 1 bit - This bit is as defined in Section 14.1 of
> >       [RFC4872] to indicate if the LSP is working or protection LSP.
> >
> >       Secondary (S): 1 bit - This bit is as defined in Section 14.1 of
> >       [RFC4872] to indicate if the LSP is primary or secondary LSP.  The
> >       S flag is ignored if the P flag is not set.
> >
> > Just to check my understanding (no change expected to result): if P is
> > zero, the LSP is working, and thus we know that it's primary since it's
> > actively carrying traffic?
> >
> 
> Yes, Working LSPs are always primary.
> 
> 
> > Section 3.2
> >
> > nit(?) The section heading does not match the name of the TLV requested
> > in the IANA considerations, nor do we mention here that "PPAG TLV" is
> > synonymous with it.
> >
> >    If the TLV is missing, it is considered that the LSP is the working
> >    LSP (i.e. as if P bit is unset).
> >
> > Is this conditional on the LSP being part of a PPAG, or does it hold
> > generically as well?
> >
> 
> IMHO when part of a PPAG i.e. association object but no TLV.

It may be worth making the text explicit about it.

> > Section 4.5
> >
> >    As per the processing rules specified in section 5.4 of
> >    [I-D.ietf-pce-association-group], if a PCEP speaker does not support
> >
> > There is no Section 5.4 in draft-ietf-pce-association-group-10;
> > presumably this was supposed to be Section 6.4?
> >
> >    A given LSP MAY belong to more than one PPAG.  If there is a conflict
> >
> > While I'm not arguing to remove this option, I'm also a bit confused at
> > how useful having a single LSP be in multiple PPAGs woud be, given the
> > need for source/destination/tunnel-ID to match.
> >
> 
> One working LSP could have multiple protection LSPs with each
> belonging to a different association.
> 
> >    When the protection type is set to 1+1 or 1:N with N=1, there MUST be
> >    only one working LSP and one protection LSP within a PPAG.  If a PCEP
> >    speaker attempts to add another working/protection LSP, the PCEP peer
> >    MUST send PCErr with Error-Type 26 (Association Error)
> >    [I-D.ietf-pce-association-group] and Error-Value TBD4 (Attempt to add
> >    another working/protection LSP for Path Protection Association).
> >
> > This seems to prevent a scenario where there's a need to change the
> > protection LSP and a desire to do so without removing the protected
> > nature of the working LSP.  Unless it's presumed that this could always
> > be done by updating the protection LSP and it would never be necessary
> > to create a new one?  (Similarly for 1:N, though maybe less severe.)
> >
> 
> One can remove the protection LSP and keep the association intact. The
> error will not be triggered.
> Also, PCEP messages are per LSP, when the first LSP is reported with
> association, it is bound to be the only LSP in the association.
> So the error in this section are focused only when one adds "another".

I don't think that the points you cover above are what I was concerned
about -- I was thinking more along the lines of a "make-before-break"
scheme for changing what LSP is the protection LSP for a given working LSP.
Maybe given the timescales involved it's not an issue in practice, though.

> Maybe we can add "..at maximum.." to make it clear?

(I don't think that's needed.)

Thanks!

-Ben

> > Section 5
> >
> >    [RFC4872] introduces the concept and mechanisms to support the
> >    association of one LSP to another LSP across different RSVP - Traffic
> >    Engineering (RSVP-TE) sessions using ASSOCIATION and PROTECTION
> >    object.  The information in the PPAG TLV in PCEP as received from the
> >    PCE, is used to trigger the signalling of working LSP and protection
> >    LSP, with the Path Protection Association Flags mapped to the
> >    corresponding fields in the PROTECTION Object in RSVP-TE.
> >
> > Just to check my understanding: this paragraph is saying that the
> > contents of the PPAG TLV received by the PCC is used as input to
> > populating the PROTECTION object that corresponds to the protection
> > group?
> >
> 
> Yes.
> 
> > Section 10.2
> >
> > I think RFCs 7525 and 8253 need to be normative (and please cite RFC
> > 7525 as BCP 195).
> >
> >
> 
> Thanks!
> Dhruv


From nobody Sun Sep 22 08:36:51 2019
Return-Path: <mahend.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64DF41200F1; Sun, 22 Sep 2019 08:36:42 -0700 (PDT)
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 if2RzYHEOjo9; Sun, 22 Sep 2019 08:36:36 -0700 (PDT)
Received: from mail-oi1-x244.google.com (mail-oi1-x244.google.com [IPv6:2607:f8b0:4864:20::244]) (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 37C881200F5; Sun, 22 Sep 2019 08:36:36 -0700 (PDT)
Received: by mail-oi1-x244.google.com with SMTP id m16so5607016oic.5; Sun, 22 Sep 2019 08:36:36 -0700 (PDT)
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=GVc+MA+r9lt/dhnZHwora+ux8DsKre9LUxorka1RXSY=; b=unT5qBztSKD94KirNihVkItozzyrjMgInLakl44eWj4MyGTemQkAvffVAbxS6EC/Fq PsT/lm1fpEokmdsqAo2nMtRMTD0s49T/Xe4dRg3JdJH5i0BiEGkdRMfkoMlXuU+XIiZG cXCkwvwb09qHv07ZeWZYd+L847/BzIJphdFGJbsg947qauUINU4hT62JRLvY2cL8V4A6 f+qTKIG/GVVGL+EvRUj2Bc6DgQioJRUr9Sz7bbmUWrusKyIlvHPJAVXQY2iQAK0Fn+jV 0+pcJZDyTTqSWpbYQJHPedOlxSfUz+f7ZYfgEWjx3C7nz47nB7ZqTDczAO/RYtWe3DH7 u/7g==
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=GVc+MA+r9lt/dhnZHwora+ux8DsKre9LUxorka1RXSY=; b=tm/BpZJihMXZTTI0ZBwLk8mv1H5ZXkVd5I9jBVoAbiBg5uq1l1n2f9OziOeI03zqXr zHB2wXt2y2lPZ/0vFmL91GYODCdLMcxklCEtO+6u4CW56zJHfYG4s0gZ2w9O6nRc+jLx 914hbvmnKCnHqL/mcZlpOuCw1xUZbemAy0Ze2aSumIaUA59fK75Xcutld9tIqb3m45eY xk/9svqGxdStfJIeqkUsfEKtnM44XbijHP8AqnygQ7f5xN12fYqzfKSwjdigv3vfoOXZ YfO4fDeFvVzFapF6lytGEdBLJMCwZ4SuzDKJRrstF/wxc+R8+NLZDJ3LhPcS2otI5PGk pW1g==
X-Gm-Message-State: APjAAAUDMBWH84uvwZ9ms+c7S3Fcd0/MigZSSOPok15x3RFkB1eNWT1I qBP+2v6xHKU3iH3ZyFEttPND5Md1Y4aw9I0+L8g=
X-Google-Smtp-Source: APXvYqy00mNFnt+7a1ritXrtOUsZlNJigpFZf0vWDppqrVf2JnFOQroajCddFbkupamdKcSVR9je7ERig5evoOuNpBo=
X-Received: by 2002:aca:4f55:: with SMTP id d82mr10108410oib.105.1569166595428;  Sun, 22 Sep 2019 08:36:35 -0700 (PDT)
MIME-Version: 1.0
References: <156876388231.17411.6094234033866939217.idtracker@ietfa.amsl.com> <CAB75xn4L2RE0vo44bt332kUL7Nh=LryKpJ3BSHRRnHggz8v3vQ@mail.gmail.com> <20190919210236.GB48975@kduck.mit.edu>
In-Reply-To: <20190919210236.GB48975@kduck.mit.edu>
From: Mahend Negi <mahend.ietf@gmail.com>
Date: Sun, 22 Sep 2019 21:06:24 +0530
Message-ID: <CAM5Nu_wQnQpkgK-X4=YZ9y2NHyNo3AdonsrGgxG32497TTy2Zg@mail.gmail.com>
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: Dhruv Dhody <dhruv.ietf@gmail.com>, The IESG <iesg@ietf.org>,  draft-ietf-pce-stateful-path-protection@ietf.org,  Julien Meuric <julien.meuric@orange.com>, pce-chairs <pce-chairs@ietf.org>, pce@ietf.org
Content-Type: multipart/alternative; boundary="0000000000008394da05932611bc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/nTzaRVZ0kDqy0jxr8_E5vYhGNo0>
Subject: Re: [Pce] Benjamin Kaduk's Discuss on draft-ietf-pce-stateful-path-protection-10: (with DISCUSS and COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Sep 2019 15:36:43 -0000

--0000000000008394da05932611bc
Content-Type: text/plain; charset="UTF-8"

Hi Ben/Dhruv,

Thanks for the review and clarification. Comments are incorporated in the
working copy (links below).

Working copy:
https://github.com/mahendnegi/ietf/blob/master/pce/path-protection/iesg/draft-ietf-pce-stateful-path-protection-11.txt
Diff:
https://github.com/mahendnegi/ietf/commit/c51efb2b025d545e066b9b13de6d84de48d1a03c

Please do share your opinion.

Thanks,
Mahendra


On Fri, Sep 20, 2019 at 2:33 AM Benjamin Kaduk <kaduk@mit.edu> wrote:

> Hi Dhruv,
>
> On Wed, Sep 18, 2019 at 11:45:23AM +0530, Dhruv Dhody wrote:
> > Hi Ben,
> >
> > Thanks for your review, let me start the discussion and the authors
> > can interject as needed.
>
> Thanks; it's a great start.
>
> > On Wed, Sep 18, 2019 at 5:14 AM Benjamin Kaduk via Datatracker
> > <noreply@ietf.org> wrote:
> > >
> > > Benjamin Kaduk has entered the following ballot position for
> > > draft-ietf-pce-stateful-path-protection-10: Discuss
> > >
> > > When responding, please keep the subject line intact and reply to all
> > > email addresses included in the To and CC lines. (Feel free to cut this
> > > introductory paragraph, however.)
> > >
> > >
> > > Please refer to
> https://www.ietf.org/iesg/statement/discuss-criteria.html
> > > for more information about IESG DISCUSS and COMMENT positions.
> > >
> > >
> > > The document, along with other ballot positions, can be found here:
> > >
> https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-path-protection/
> > >
> > >
> > >
> > > ----------------------------------------------------------------------
> > > DISCUSS:
> > > ----------------------------------------------------------------------
> > >
> > > (1) draft-ietf-pce-association-group notes that "PCEP extensions that
> define
> > > a new association type should clarify the relationship between the SVEC
> > > object and the association type, if any".  Where do we do so for the
> > > path protection association type?
> > >
> >
> > This is discussed in
> >
> https://tools.ietf.org/html/draft-ietf-pce-association-diversity-10#section-5.3
> ,
> > where it is more relevant. This draft includes the relationship with
> > diversity association in Section 5.
>
> A naive reading of the linked section would be that it applies only to the
> "Disjointness Association Type" defined in that document.  I'm not in a
> position to claim that the reasoning in that document does not apply to
> this one, but I think we should make a more clear link between the Path
> Protection ASsociation Type and the discussion in that document.
>
> > > (2) Section 3.2 says:
> > >
> > >       Protection Type (PT): 6 bits - This field is as defined in
> > >       Section 14.1 of [RFC4872] to indicate the LSP protection type in
> > >       use.
> > >
> > > There doesn't seem to be a registry created by RFC 4872 to track these
> > > PT values, so I assume that the way to allocate a new value is
> > > "standards-track RFC that Updates: RFC 4872".  Is that also the way to
> > > allocate new PT values for PPAG usage?  How would someone updating RFC
> > > 4872 to allocate a new type know to consider/document whether it
> applies
> > > for PPAG usage?
> > >
> >
> > That's true. Maybe we can add this text - "Any type already defined or
> > that could be defined in the future for use in the RSVP-TE PROTECTION
> > object is acceptable in this TLV unless explicitly stated otherwise."
>
> To be honest, that's probably good enough in practice, since it seems
> somewhat unlikely that the last bit is ever going to get allocated (though,
> I guess technically the field could be converted to an integer instead of
> flags).  I do still have to wonder how the reader would know *where* it
> would be stated otherwise, and how the author of a document defining a new
> type would know to consider our use case as well as the RFC 4872 use case.
>
> > > (3) In Section 4.3:
> > >
> > >    A PCE can create/update working and protection LSPs independently.
> > >    As specified in [I-D.ietf-pce-association-group], Association Groups
> > >    can be created by both the PCE and the PCC.  Further, a PCE can
> > >
> > > The requirement that source, destination, and tunnel ID of all LSPs
> > > within a PPAG MUST be the same is new to this document, so I think we
> > > need to specify error handling for when attempts to update LSPs
> > > independently would violate that invariant (presumably in Section 4.5).
> > >
> >
> > In the existing error case in Section 4.5 we could make it "add or
> update".
>
> Wording it right might be a little finicky, but that's fine in general.
>
> > > (4) In Section 6.3:
> > >
> > >                                       IANA is requested to allocate new
> > >    error values within the "PCEP-ERROR Object Error Types and Values"
> > >    sub-registry of the PCEP Numbers registry, as follows:
> > >
> > > The following table only lists Error-values.  What Error-type(s) should
> > > they be associated with?
> > >
> >
> > It is mentioned in the text, but worth making it explicit in the table
> as well.
> >
> > > (5) We don't say which objects the PPAG TLV can appear in.  (Section
> 3.2
> > > says "[t]he Path Protection Association TLV is an optional TLV for use
> > > with the Path Protection Association Type", but it's hard to interpret
> > > that as meaning "for use [only] with the ASSOCIATION object defined in
> > > draft-ietf-pce-association-group", especially since there is a "path
> > > protection association type" already (and it's a codepoint in the
> > > "ASSOCIATION Type Field" registry).
> > >
> >
> > We can update to - "The Path Protection Association TLV is an optional
> > TLV for use in the ASSOCIATION Object with the Path Protection
> > Association Type."
>
> Thanks!
>
> > > (6) I'm not sure if a change to the document is needed here, but
> perhaps
> > > some discussion is in order: we say that a given LSP can belong to more
> > > than one PPAG, but only allow one PPAG TLV per [some context that
> > > remains unclear; see (5)].  I don't have a good handle for whether
> these
> > > two requirements are potentially in conflict: that is, whether a single
> > > PPAG TLV would have to specify the flags that apply for both PPAGs that
> > > a given LSP is a member of, or if the containing objects serve to scope
> > > the PPAG TLV flags' interpretation.
> > >
> >
> > When a given LSP belong to more than one PPAG, we expect to have
> > multiple ASSOCIATION Object for each PPAG with each of them having a
> > single PPAG TLV.
>
> Sounds good, and quite natural given (5).
>
> > > (7) Do the Protection Type fields of the PPAG TLV in the various LSPs
> > > that are members of the same PPAG need to match, in the same way that
> > > the source/destination/tunnel-ID do?
> > >
> >
> > Yes. Authors should make that explicit.
>
> Thanks
>
> > >
> > > ----------------------------------------------------------------------
> > > COMMENT:
> > > ----------------------------------------------------------------------
> > >
> > > Section 1
> > >
> > >    This document specifies a stateful PCEP extension to associate two
> or
> > >    more LSPs for the purpose of setting up path protection.  The
> > >    proposed extension covers the following scenarios:
> > >
> > > nit: after publication, it doesn't really seem like a *proposed*
> > > extension anymore.
> > >
> > > Section 3.1
> > >
> > >    LSPs are not associated by listing the other LSPs with which they
> > >    interact, but rather by making them belong to an association group
> > >    referred to as "Path Protection Association Group" (PPAG) in this
> > >    document.  [...]
> > >
> > > The first 2/3 of this sentence is a (true) generic statement about all
> > > association groups, which exist outside of this document in a generic
> > > fashion.  I strongly suggest rewording this to make clear that the PPAG
> > > is the specific association (group) type used for this document's
> > > functionality but that other association groups are possible.  The
> > > current wording implies that the PPAG is the only association possible,
> > > and it is just given a special name for this document's purposes.
> > >
> > >    [I-D.ietf-pce-association-group] specifies the mechanism for the
> > >    capability advertisement of the Association types supported by a
> PCEP
> > >    speaker by defining a ASSOC-Type-List TLV to be carried within an
> > >    OPEN object.  This capability exchange for the Association type
> > >    described in this document (i.e.  Path Protection Association Type)
> > >    MAY be done before using the policy association, i.e., the PCEP
> > >    speaker MAY include the Path Protection Association Type (TBD1) in
> > >    the ASSOC-Type-List TLV before using the PPAG in the PCEP messages.
> > >
> > > Why is this only MAY and not MUST?
> > >
> >
> > In [I-D.ietf-pce-association-group] we explicitly did not mandate the
> > capability exchange for all association types and let each type decide
> > for itself. This association type fits into where the capability
> > exchange is optional. When the capability exchange was added in
> > [I-D.ietf-pce-association-group], there was a desire from the WG to
> > keep it optional for already defined/implemented protection
> > association type. Also this is a basic feature in path computation and
> > it is expected to be supported universally. In a corner case there is
> > an error handling for unknown/unsupported association-type to take
> > care of it.
>
> Okay, thanks for giving me the backstory.
>
> > >    This Association type is dynamic in nature and created by the PCC or
> > >
> > > nit: is it the type that is dynamic or the associations of that type?
> > >
> >
> > It is the type. [I-D.ietf-pce-association-group] has dynamic or
> > operator-configured association, this one is dynamic.
>
> Ah, of course, I had forgotten about that division of configuration.
>
> > >       Protecting (P): 1 bit - This bit is as defined in Section 14.1 of
> > >       [RFC4872] to indicate if the LSP is working or protection LSP.
> > >
> > >       Secondary (S): 1 bit - This bit is as defined in Section 14.1 of
> > >       [RFC4872] to indicate if the LSP is primary or secondary LSP.
> The
> > >       S flag is ignored if the P flag is not set.
> > >
> > > Just to check my understanding (no change expected to result): if P is
> > > zero, the LSP is working, and thus we know that it's primary since it's
> > > actively carrying traffic?
> > >
> >
> > Yes, Working LSPs are always primary.
> >
> >
> > > Section 3.2
> > >
> > > nit(?) The section heading does not match the name of the TLV requested
> > > in the IANA considerations, nor do we mention here that "PPAG TLV" is
> > > synonymous with it.
> > >
> > >    If the TLV is missing, it is considered that the LSP is the working
> > >    LSP (i.e. as if P bit is unset).
> > >
> > > Is this conditional on the LSP being part of a PPAG, or does it hold
> > > generically as well?
> > >
> >
> > IMHO when part of a PPAG i.e. association object but no TLV.
>
> It may be worth making the text explicit about it.
>
> > > Section 4.5
> > >
> > >    As per the processing rules specified in section 5.4 of
> > >    [I-D.ietf-pce-association-group], if a PCEP speaker does not support
> > >
> > > There is no Section 5.4 in draft-ietf-pce-association-group-10;
> > > presumably this was supposed to be Section 6.4?
> > >
> > >    A given LSP MAY belong to more than one PPAG.  If there is a
> conflict
> > >
> > > While I'm not arguing to remove this option, I'm also a bit confused at
> > > how useful having a single LSP be in multiple PPAGs woud be, given the
> > > need for source/destination/tunnel-ID to match.
> > >
> >
> > One working LSP could have multiple protection LSPs with each
> > belonging to a different association.
> >
> > >    When the protection type is set to 1+1 or 1:N with N=1, there MUST
> be
> > >    only one working LSP and one protection LSP within a PPAG.  If a
> PCEP
> > >    speaker attempts to add another working/protection LSP, the PCEP
> peer
> > >    MUST send PCErr with Error-Type 26 (Association Error)
> > >    [I-D.ietf-pce-association-group] and Error-Value TBD4 (Attempt to
> add
> > >    another working/protection LSP for Path Protection Association).
> > >
> > > This seems to prevent a scenario where there's a need to change the
> > > protection LSP and a desire to do so without removing the protected
> > > nature of the working LSP.  Unless it's presumed that this could always
> > > be done by updating the protection LSP and it would never be necessary
> > > to create a new one?  (Similarly for 1:N, though maybe less severe.)
> > >
> >
> > One can remove the protection LSP and keep the association intact. The
> > error will not be triggered.
> > Also, PCEP messages are per LSP, when the first LSP is reported with
> > association, it is bound to be the only LSP in the association.
> > So the error in this section are focused only when one adds "another".
>
> I don't think that the points you cover above are what I was concerned
> about -- I was thinking more along the lines of a "make-before-break"
> scheme for changing what LSP is the protection LSP for a given working LSP.
> Maybe given the timescales involved it's not an issue in practice, though.
>
> > Maybe we can add "..at maximum.." to make it clear?
>
> (I don't think that's needed.)
>
> Thanks!
>
> -Ben
>
> > > Section 5
> > >
> > >    [RFC4872] introduces the concept and mechanisms to support the
> > >    association of one LSP to another LSP across different RSVP -
> Traffic
> > >    Engineering (RSVP-TE) sessions using ASSOCIATION and PROTECTION
> > >    object.  The information in the PPAG TLV in PCEP as received from
> the
> > >    PCE, is used to trigger the signalling of working LSP and protection
> > >    LSP, with the Path Protection Association Flags mapped to the
> > >    corresponding fields in the PROTECTION Object in RSVP-TE.
> > >
> > > Just to check my understanding: this paragraph is saying that the
> > > contents of the PPAG TLV received by the PCC is used as input to
> > > populating the PROTECTION object that corresponds to the protection
> > > group?
> > >
> >
> > Yes.
> >
> > > Section 10.2
> > >
> > > I think RFCs 7525 and 8253 need to be normative (and please cite RFC
> > > 7525 as BCP 195).
> > >
> > >
> >
> > Thanks!
> > Dhruv
>

--0000000000008394da05932611bc
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi Ben/Dhruv,</div><div><br></div><div>Thanks for the=
 review and clarification. Comments are incorporated in the working copy (l=
inks below).</div><div><br></div><div>Working copy:</div><div><a href=3D"ht=
tps://github.com/mahendnegi/ietf/blob/master/pce/path-protection/iesg/draft=
-ietf-pce-stateful-path-protection-11.txt">https://github.com/mahendnegi/ie=
tf/blob/master/pce/path-protection/iesg/draft-ietf-pce-stateful-path-protec=
tion-11.txt</a></div><div><div>Diff: <br></div><div><a href=3D"https://gith=
ub.com/mahendnegi/ietf/commit/c51efb2b025d545e066b9b13de6d84de48d1a03c">htt=
ps://github.com/mahendnegi/ietf/commit/c51efb2b025d545e066b9b13de6d84de48d1=
a03c</a></div></div><div><br></div><div>Please do share your opinion.</div>=
<div><br></div><div>Thanks,</div><div>Mahendra</div><div></div><div><br></d=
iv></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_att=
r">On Fri, Sep 20, 2019 at 2:33 AM Benjamin Kaduk &lt;<a href=3D"mailto:kad=
uk@mit.edu">kaduk@mit.edu</a>&gt; wrote:<br></div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,20=
4,204);padding-left:1ex">Hi Dhruv,<br>
<br>
On Wed, Sep 18, 2019 at 11:45:23AM +0530, Dhruv Dhody wrote:<br>
&gt; Hi Ben,<br>
&gt; <br>
&gt; Thanks for your review, let me start the discussion and the authors<br=
>
&gt; can interject as needed.<br>
<br>
Thanks; it&#39;s a great start.<br>
<br>
&gt; On Wed, Sep 18, 2019 at 5:14 AM Benjamin Kaduk via Datatracker<br>
&gt; &lt;<a href=3D"mailto:noreply@ietf.org" target=3D"_blank">noreply@ietf=
.org</a>&gt; wrote:<br>
&gt; &gt;<br>
&gt; &gt; Benjamin Kaduk has entered the following ballot position for<br>
&gt; &gt; draft-ietf-pce-stateful-path-protection-10: Discuss<br>
&gt; &gt;<br>
&gt; &gt; When responding, please keep the subject line intact and reply to=
 all<br>
&gt; &gt; email addresses included in the To and CC lines. (Feel free to cu=
t this<br>
&gt; &gt; introductory paragraph, however.)<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; Please refer to <a href=3D"https://www.ietf.org/iesg/statement/di=
scuss-criteria.html" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.=
org/iesg/statement/discuss-criteria.html</a><br>
&gt; &gt; for more information about IESG DISCUSS and COMMENT positions.<br=
>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; The document, along with other ballot positions, can be found her=
e:<br>
&gt; &gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-pce-statef=
ul-path-protection/" rel=3D"noreferrer" target=3D"_blank">https://datatrack=
er.ietf.org/doc/draft-ietf-pce-stateful-path-protection/</a><br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; -----------------------------------------------------------------=
-----<br>
&gt; &gt; DISCUSS:<br>
&gt; &gt; -----------------------------------------------------------------=
-----<br>
&gt; &gt;<br>
&gt; &gt; (1) draft-ietf-pce-association-group notes that &quot;PCEP extens=
ions that define<br>
&gt; &gt; a new association type should clarify the relationship between th=
e SVEC<br>
&gt; &gt; object and the association type, if any&quot;.=C2=A0 Where do we =
do so for the<br>
&gt; &gt; path protection association type?<br>
&gt; &gt;<br>
&gt; <br>
&gt; This is discussed in<br>
&gt; <a href=3D"https://tools.ietf.org/html/draft-ietf-pce-association-dive=
rsity-10#section-5.3" rel=3D"noreferrer" target=3D"_blank">https://tools.ie=
tf.org/html/draft-ietf-pce-association-diversity-10#section-5.3</a>,<br>
&gt; where it is more relevant. This draft includes the relationship with<b=
r>
&gt; diversity association in Section 5.<br>
<br>
A naive reading of the linked section would be that it applies only to the<=
br>
&quot;Disjointness Association Type&quot; defined in that document.=C2=A0 I=
&#39;m not in a<br>
position to claim that the reasoning in that document does not apply to<br>
this one, but I think we should make a more clear link between the Path<br>
Protection ASsociation Type and the discussion in that document.<br>
<br>
&gt; &gt; (2) Section 3.2 says:<br>
&gt; &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Protection Type (PT): 6 bits - This fie=
ld is as defined in<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Section 14.1 of [RFC4872] to indicate t=
he LSP protection type in<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0use.<br>
&gt; &gt;<br>
&gt; &gt; There doesn&#39;t seem to be a registry created by RFC 4872 to tr=
ack these<br>
&gt; &gt; PT values, so I assume that the way to allocate a new value is<br=
>
&gt; &gt; &quot;standards-track RFC that Updates: RFC 4872&quot;.=C2=A0 Is =
that also the way to<br>
&gt; &gt; allocate new PT values for PPAG usage?=C2=A0 How would someone up=
dating RFC<br>
&gt; &gt; 4872 to allocate a new type know to consider/document whether it =
applies<br>
&gt; &gt; for PPAG usage?<br>
&gt; &gt;<br>
&gt; <br>
&gt; That&#39;s true. Maybe we can add this text - &quot;Any type already d=
efined or<br>
&gt; that could be defined in the future for use in the RSVP-TE PROTECTION<=
br>
&gt; object is acceptable in this TLV unless explicitly stated otherwise.&q=
uot;<br>
<br>
To be honest, that&#39;s probably good enough in practice, since it seems<b=
r>
somewhat unlikely that the last bit is ever going to get allocated (though,=
<br>
I guess technically the field could be converted to an integer instead of<b=
r>
flags).=C2=A0 I do still have to wonder how the reader would know *where* i=
t<br>
would be stated otherwise, and how the author of a document defining a new<=
br>
type would know to consider our use case as well as the RFC 4872 use case.<=
br>
<br>
&gt; &gt; (3) In Section 4.3:<br>
&gt; &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 A PCE can create/update working and protection LSPs =
independently.<br>
&gt; &gt;=C2=A0 =C2=A0 As specified in [I-D.ietf-pce-association-group], As=
sociation Groups<br>
&gt; &gt;=C2=A0 =C2=A0 can be created by both the PCE and the PCC.=C2=A0 Fu=
rther, a PCE can<br>
&gt; &gt;<br>
&gt; &gt; The requirement that source, destination, and tunnel ID of all LS=
Ps<br>
&gt; &gt; within a PPAG MUST be the same is new to this document, so I thin=
k we<br>
&gt; &gt; need to specify error handling for when attempts to update LSPs<b=
r>
&gt; &gt; independently would violate that invariant (presumably in Section=
 4.5).<br>
&gt; &gt;<br>
&gt; <br>
&gt; In the existing error case in Section 4.5 we could make it &quot;add o=
r update&quot;.<br>
<br>
Wording it right might be a little finicky, but that&#39;s fine in general.=
<br>
<br>
&gt; &gt; (4) In Section 6.3:<br>
&gt; &gt;<br>
&gt; &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=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0IA=
NA is requested to allocate new<br>
&gt; &gt;=C2=A0 =C2=A0 error values within the &quot;PCEP-ERROR Object Erro=
r Types and Values&quot;<br>
&gt; &gt;=C2=A0 =C2=A0 sub-registry of the PCEP Numbers registry, as follow=
s:<br>
&gt; &gt;<br>
&gt; &gt; The following table only lists Error-values.=C2=A0 What Error-typ=
e(s) should<br>
&gt; &gt; they be associated with?<br>
&gt; &gt;<br>
&gt; <br>
&gt; It is mentioned in the text, but worth making it explicit in the table=
 as well.<br>
&gt; <br>
&gt; &gt; (5) We don&#39;t say which objects the PPAG TLV can appear in.=C2=
=A0 (Section 3.2<br>
&gt; &gt; says &quot;[t]he Path Protection Association TLV is an optional T=
LV for use<br>
&gt; &gt; with the Path Protection Association Type&quot;, but it&#39;s har=
d to interpret<br>
&gt; &gt; that as meaning &quot;for use [only] with the ASSOCIATION object =
defined in<br>
&gt; &gt; draft-ietf-pce-association-group&quot;, especially since there is=
 a &quot;path<br>
&gt; &gt; protection association type&quot; already (and it&#39;s a codepoi=
nt in the<br>
&gt; &gt; &quot;ASSOCIATION Type Field&quot; registry).<br>
&gt; &gt;<br>
&gt; <br>
&gt; We can update to - &quot;The Path Protection Association TLV is an opt=
ional<br>
&gt; TLV for use in the ASSOCIATION Object with the Path Protection<br>
&gt; Association Type.&quot;<br>
<br>
Thanks!<br>
<br>
&gt; &gt; (6) I&#39;m not sure if a change to the document is needed here, =
but perhaps<br>
&gt; &gt; some discussion is in order: we say that a given LSP can belong t=
o more<br>
&gt; &gt; than one PPAG, but only allow one PPAG TLV per [some context that=
<br>
&gt; &gt; remains unclear; see (5)].=C2=A0 I don&#39;t have a good handle f=
or whether these<br>
&gt; &gt; two requirements are potentially in conflict: that is, whether a =
single<br>
&gt; &gt; PPAG TLV would have to specify the flags that apply for both PPAG=
s that<br>
&gt; &gt; a given LSP is a member of, or if the containing objects serve to=
 scope<br>
&gt; &gt; the PPAG TLV flags&#39; interpretation.<br>
&gt; &gt;<br>
&gt; <br>
&gt; When a given LSP belong to more than one PPAG, we expect to have<br>
&gt; multiple ASSOCIATION Object for each PPAG with each of them having a<b=
r>
&gt; single PPAG TLV.<br>
<br>
Sounds good, and quite natural given (5).<br>
<br>
&gt; &gt; (7) Do the Protection Type fields of the PPAG TLV in the various =
LSPs<br>
&gt; &gt; that are members of the same PPAG need to match, in the same way =
that<br>
&gt; &gt; the source/destination/tunnel-ID do?<br>
&gt; &gt;<br>
&gt; <br>
&gt; Yes. Authors should make that explicit.<br>
<br>
Thanks<br>
<br>
&gt; &gt;<br>
&gt; &gt; -----------------------------------------------------------------=
-----<br>
&gt; &gt; COMMENT:<br>
&gt; &gt; -----------------------------------------------------------------=
-----<br>
&gt; &gt;<br>
&gt; &gt; Section 1<br>
&gt; &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 This document specifies a stateful PCEP extension to=
 associate two or<br>
&gt; &gt;=C2=A0 =C2=A0 more LSPs for the purpose of setting up path protect=
ion.=C2=A0 The<br>
&gt; &gt;=C2=A0 =C2=A0 proposed extension covers the following scenarios:<b=
r>
&gt; &gt;<br>
&gt; &gt; nit: after publication, it doesn&#39;t really seem like a *propos=
ed*<br>
&gt; &gt; extension anymore.<br>
&gt; &gt;<br>
&gt; &gt; Section 3.1<br>
&gt; &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 LSPs are not associated by listing the other LSPs wi=
th which they<br>
&gt; &gt;=C2=A0 =C2=A0 interact, but rather by making them belong to an ass=
ociation group<br>
&gt; &gt;=C2=A0 =C2=A0 referred to as &quot;Path Protection Association Gro=
up&quot; (PPAG) in this<br>
&gt; &gt;=C2=A0 =C2=A0 document.=C2=A0 [...]<br>
&gt; &gt;<br>
&gt; &gt; The first 2/3 of this sentence is a (true) generic statement abou=
t all<br>
&gt; &gt; association groups, which exist outside of this document in a gen=
eric<br>
&gt; &gt; fashion.=C2=A0 I strongly suggest rewording this to make clear th=
at the PPAG<br>
&gt; &gt; is the specific association (group) type used for this document&#=
39;s<br>
&gt; &gt; functionality but that other association groups are possible.=C2=
=A0 The<br>
&gt; &gt; current wording implies that the PPAG is the only association pos=
sible,<br>
&gt; &gt; and it is just given a special name for this document&#39;s purpo=
ses.<br>
&gt; &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 [I-D.ietf-pce-association-group] specifies the mecha=
nism for the<br>
&gt; &gt;=C2=A0 =C2=A0 capability advertisement of the Association types su=
pported by a PCEP<br>
&gt; &gt;=C2=A0 =C2=A0 speaker by defining a ASSOC-Type-List TLV to be carr=
ied within an<br>
&gt; &gt;=C2=A0 =C2=A0 OPEN object.=C2=A0 This capability exchange for the =
Association type<br>
&gt; &gt;=C2=A0 =C2=A0 described in this document (i.e.=C2=A0 Path Protecti=
on Association Type)<br>
&gt; &gt;=C2=A0 =C2=A0 MAY be done before using the policy association, i.e=
., the PCEP<br>
&gt; &gt;=C2=A0 =C2=A0 speaker MAY include the Path Protection Association =
Type (TBD1) in<br>
&gt; &gt;=C2=A0 =C2=A0 the ASSOC-Type-List TLV before using the PPAG in the=
 PCEP messages.<br>
&gt; &gt;<br>
&gt; &gt; Why is this only MAY and not MUST?<br>
&gt; &gt;<br>
&gt; <br>
&gt; In [I-D.ietf-pce-association-group] we explicitly did not mandate the<=
br>
&gt; capability exchange for all association types and let each type decide=
<br>
&gt; for itself. This association type fits into where the capability<br>
&gt; exchange is optional. When the capability exchange was added in<br>
&gt; [I-D.ietf-pce-association-group], there was a desire from the WG to<br=
>
&gt; keep it optional for already defined/implemented protection<br>
&gt; association type. Also this is a basic feature in path computation and=
<br>
&gt; it is expected to be supported universally. In a corner case there is<=
br>
&gt; an error handling for unknown/unsupported association-type to take<br>
&gt; care of it.<br>
<br>
Okay, thanks for giving me the backstory.<br>
<br>
&gt; &gt;=C2=A0 =C2=A0 This Association type is dynamic in nature and creat=
ed by the PCC or<br>
&gt; &gt;<br>
&gt; &gt; nit: is it the type that is dynamic or the associations of that t=
ype?<br>
&gt; &gt;<br>
&gt; <br>
&gt; It is the type. [I-D.ietf-pce-association-group] has dynamic or<br>
&gt; operator-configured association, this one is dynamic.<br>
<br>
Ah, of course, I had forgotten about that division of configuration.<br>
<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Protecting (P): 1 bit - This bit is as =
defined in Section 14.1 of<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0[RFC4872] to indicate if the LSP is wor=
king or protection LSP.<br>
&gt; &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Secondary (S): 1 bit - This bit is as d=
efined in Section 14.1 of<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0[RFC4872] to indicate if the LSP is pri=
mary or secondary LSP.=C2=A0 The<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0S flag is ignored if the P flag is not =
set.<br>
&gt; &gt;<br>
&gt; &gt; Just to check my understanding (no change expected to result): if=
 P is<br>
&gt; &gt; zero, the LSP is working, and thus we know that it&#39;s primary =
since it&#39;s<br>
&gt; &gt; actively carrying traffic?<br>
&gt; &gt;<br>
&gt; <br>
&gt; Yes, Working LSPs are always primary.<br>
&gt; <br>
&gt; <br>
&gt; &gt; Section 3.2<br>
&gt; &gt;<br>
&gt; &gt; nit(?) The section heading does not match the name of the TLV req=
uested<br>
&gt; &gt; in the IANA considerations, nor do we mention here that &quot;PPA=
G TLV&quot; is<br>
&gt; &gt; synonymous with it.<br>
&gt; &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 If the TLV is missing, it is considered that the LSP=
 is the working<br>
&gt; &gt;=C2=A0 =C2=A0 LSP (i.e. as if P bit is unset).<br>
&gt; &gt;<br>
&gt; &gt; Is this conditional on the LSP being part of a PPAG, or does it h=
old<br>
&gt; &gt; generically as well?<br>
&gt; &gt;<br>
&gt; <br>
&gt; IMHO when part of a PPAG i.e. association object but no TLV.<br>
<br>
It may be worth making the text explicit about it.<br>
<br>
&gt; &gt; Section 4.5<br>
&gt; &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 As per the processing rules specified in section 5.4=
 of<br>
&gt; &gt;=C2=A0 =C2=A0 [I-D.ietf-pce-association-group], if a PCEP speaker =
does not support<br>
&gt; &gt;<br>
&gt; &gt; There is no Section 5.4 in draft-ietf-pce-association-group-10;<b=
r>
&gt; &gt; presumably this was supposed to be Section 6.4?<br>
&gt; &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 A given LSP MAY belong to more than one PPAG.=C2=A0 =
If there is a conflict<br>
&gt; &gt;<br>
&gt; &gt; While I&#39;m not arguing to remove this option, I&#39;m also a b=
it confused at<br>
&gt; &gt; how useful having a single LSP be in multiple PPAGs woud be, give=
n the<br>
&gt; &gt; need for source/destination/tunnel-ID to match.<br>
&gt; &gt;<br>
&gt; <br>
&gt; One working LSP could have multiple protection LSPs with each<br>
&gt; belonging to a different association.<br>
&gt; <br>
&gt; &gt;=C2=A0 =C2=A0 When the protection type is set to 1+1 or 1:N with N=
=3D1, there MUST be<br>
&gt; &gt;=C2=A0 =C2=A0 only one working LSP and one protection LSP within a=
 PPAG.=C2=A0 If a PCEP<br>
&gt; &gt;=C2=A0 =C2=A0 speaker attempts to add another working/protection L=
SP, the PCEP peer<br>
&gt; &gt;=C2=A0 =C2=A0 MUST send PCErr with Error-Type 26 (Association Erro=
r)<br>
&gt; &gt;=C2=A0 =C2=A0 [I-D.ietf-pce-association-group] and Error-Value TBD=
4 (Attempt to add<br>
&gt; &gt;=C2=A0 =C2=A0 another working/protection LSP for Path Protection A=
ssociation).<br>
&gt; &gt;<br>
&gt; &gt; This seems to prevent a scenario where there&#39;s a need to chan=
ge the<br>
&gt; &gt; protection LSP and a desire to do so without removing the protect=
ed<br>
&gt; &gt; nature of the working LSP.=C2=A0 Unless it&#39;s presumed that th=
is could always<br>
&gt; &gt; be done by updating the protection LSP and it would never be nece=
ssary<br>
&gt; &gt; to create a new one?=C2=A0 (Similarly for 1:N, though maybe less =
severe.)<br>
&gt; &gt;<br>
&gt; <br>
&gt; One can remove the protection LSP and keep the association intact. The=
<br>
&gt; error will not be triggered.<br>
&gt; Also, PCEP messages are per LSP, when the first LSP is reported with<b=
r>
&gt; association, it is bound to be the only LSP in the association.<br>
&gt; So the error in this section are focused only when one adds &quot;anot=
her&quot;.<br>
<br>
I don&#39;t think that the points you cover above are what I was concerned<=
br>
about -- I was thinking more along the lines of a &quot;make-before-break&q=
uot;<br>
scheme for changing what LSP is the protection LSP for a given working LSP.=
<br>
Maybe given the timescales involved it&#39;s not an issue in practice, thou=
gh.<br>
<br>
&gt; Maybe we can add &quot;..at maximum..&quot; to make it clear?<br>
<br>
(I don&#39;t think that&#39;s needed.)<br>
<br>
Thanks!<br>
<br>
-Ben<br>
<br>
&gt; &gt; Section 5<br>
&gt; &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 [RFC4872] introduces the concept and mechanisms to s=
upport the<br>
&gt; &gt;=C2=A0 =C2=A0 association of one LSP to another LSP across differe=
nt RSVP - Traffic<br>
&gt; &gt;=C2=A0 =C2=A0 Engineering (RSVP-TE) sessions using ASSOCIATION and=
 PROTECTION<br>
&gt; &gt;=C2=A0 =C2=A0 object.=C2=A0 The information in the PPAG TLV in PCE=
P as received from the<br>
&gt; &gt;=C2=A0 =C2=A0 PCE, is used to trigger the signalling of working LS=
P and protection<br>
&gt; &gt;=C2=A0 =C2=A0 LSP, with the Path Protection Association Flags mapp=
ed to the<br>
&gt; &gt;=C2=A0 =C2=A0 corresponding fields in the PROTECTION Object in RSV=
P-TE.<br>
&gt; &gt;<br>
&gt; &gt; Just to check my understanding: this paragraph is saying that the=
<br>
&gt; &gt; contents of the PPAG TLV received by the PCC is used as input to<=
br>
&gt; &gt; populating the PROTECTION object that corresponds to the protecti=
on<br>
&gt; &gt; group?<br>
&gt; &gt;<br>
&gt; <br>
&gt; Yes.<br>
&gt; <br>
&gt; &gt; Section 10.2<br>
&gt; &gt;<br>
&gt; &gt; I think RFCs 7525 and 8253 need to be normative (and please cite =
RFC<br>
&gt; &gt; 7525 as BCP 195).<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; <br>
&gt; Thanks!<br>
&gt; Dhruv<br>
</blockquote></div>

--0000000000008394da05932611bc--


From nobody Sun Sep 22 09:18:40 2019
Return-Path: <hari@netflix.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA6911200E7 for <pce@ietfa.amsl.com>; Sun, 22 Sep 2019 09:18:38 -0700 (PDT)
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, DKIMWL_WL_HIGH=-0.001, 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=netflix.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 dfDBchlC7uPg for <pce@ietfa.amsl.com>; Sun, 22 Sep 2019 09:18:37 -0700 (PDT)
Received: from mail-vs1-xe30.google.com (mail-vs1-xe30.google.com [IPv6:2607:f8b0:4864:20::e30]) (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 68D93120059 for <pce@ietf.org>; Sun, 22 Sep 2019 09:18:37 -0700 (PDT)
Received: by mail-vs1-xe30.google.com with SMTP id d3so7890914vsr.1 for <pce@ietf.org>; Sun, 22 Sep 2019 09:18:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netflix.com; s=google;  h=mime-version:from:date:message-id:subject:to:cc; bh=0rw22ZsBEI5MGu1hk+2w5NwQSDTEb41ulnI+g7q0Xh0=; b=N00x9uk5W01PjDF5KFR4KFglqAR1WHYqbOo5BYYvhdk+jKpa5ARtSsiuypOGY015vK Uv9kvmUlF6/iyE4exwQnVzBWHKWe4rd+pkOOiWcz0YEvA5Fyy7oOon51iUlzqGTRUsg+ zyMLe4jJIBTDwYOyCjqy3L3UBWKG/zsuardOg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=0rw22ZsBEI5MGu1hk+2w5NwQSDTEb41ulnI+g7q0Xh0=; b=dNDbLI77M6rugS/RSnVf8x53xoZtu1jBCLTJBYlJBdxODpeKj4UAqmG31cJoZadwHr RT4OFTQl4wnECaBSIg+qphGAOwpAsLjb1ZZ+yESdwMq6yegfriiW7fb8Y4k4Nw0Sri94 Ibuezwd2zQpIDFzo/RjW9HHkAjVOxhtktzL/T343s0E1efLwhXN50zwKXXsjdZlZbj3w +9fAxvfs1SycQlQdpXhyNOkQ6mIewyB3ZEGwKPt9f6X5nd2DZ3kTIXGcQ+8RHIFB4cKX yT8L+xi28RLbBPzYpbC6405TdtDNKhzHBiqygBsL+ab8UmbKjUbnGCZvfU7yOu8hgwG+ DFkg==
X-Gm-Message-State: APjAAAULiyHvXiNxdsPtvjEBIsCBnQB1hvjHsQNwGLJm2xjYih+/O/lI zOAFdevg2ux4uXwtVBNq5c+UoDAFH2AEeEcCp8eWVTkk9MU=
X-Google-Smtp-Source: APXvYqwUO/Sn/x+KKif7QyXZPdvElmq1GONAWg8izHAYkQXz6MwI94vd4eSwP8NKE5PmLvxrvMkCGOZkkR9pQgjRoqw=
X-Received: by 2002:a67:f9c3:: with SMTP id c3mr7509307vsq.64.1569169116285; Sun, 22 Sep 2019 09:18:36 -0700 (PDT)
MIME-Version: 1.0
From: Hariharan Ananthakrishnan <hari@netflix.com>
Date: Sun, 22 Sep 2019 09:18:25 -0700
Message-ID: <CAL70W4q1DJ3WsGyN+88sXkCU+VT0omn9u3vzQzB1_GmTc4AH3w@mail.gmail.com>
To: Farrel Adrian <adrian@olddog.co.uk>
Cc: pce@ietf.org
Content-Type: multipart/alternative; boundary="000000000000c51635059326a7c3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/gcaQavCnK-AlyHYHkcQyR_G-u7I>
Subject: [Pce] Shepherd Review of draft-farrel-pce-stateful-flags-01
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Sep 2019 16:18:39 -0000

--000000000000c51635059326a7c3
Content-Type: text/plain; charset="UTF-8"

Hi Adrian,

This document is well written and clear. Thanks for the update. Please find
below my comments on draft-farrel-pce-stateful-flags-01.

OLD:
8. IANA Considerations
This document makes no requests for IANA action

NEW:
The current IANA for this object has reference to "RFC8281" (
https://www.iana.org/assignments/pcep/pcep.xhtml#srp-object-flag-field)
Dont we want that refer to this new draft since we have updated the text ?

Thanks,
Hari

--000000000000c51635059326a7c3
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D""><font face=3D"verd=
ana, sans-serif" style=3D"">Hi Adrian,</font></div><div class=3D"gmail_defa=
ult" style=3D""><font face=3D"verdana, sans-serif"><br></font></div><div cl=
ass=3D"gmail_default" style=3D""><font face=3D"verdana, sans-serif">This do=
cument is well written and clear. Thanks for the update. Please find below =
my comments on=C2=A0draft-farrel-pce-stateful-flags-01.</font></div><div cl=
ass=3D"gmail_default" style=3D""><font face=3D"verdana, sans-serif"><br></f=
ont></div><div class=3D"gmail_default" style=3D""><font face=3D"verdana, sa=
ns-serif">OLD:</font></div><div class=3D"gmail_default" style=3D""><font fa=
ce=3D"verdana, sans-serif">8. IANA Considerations</font></div><div class=3D=
"gmail_default" style=3D""><font face=3D"verdana, sans-serif">This document=
 makes no requests for IANA action</font></div><div class=3D"gmail_default"=
 style=3D""><font face=3D"verdana, sans-serif"><br></font></div><div class=
=3D"gmail_default" style=3D""><font face=3D"verdana, sans-serif">NEW:</font=
></div><div class=3D"gmail_default" style=3D""><font face=3D"verdana, sans-=
serif">The current IANA for this object has reference to &quot;RFC8281&quot=
; (<a href=3D"https://www.iana.org/assignments/pcep/pcep.xhtml#srp-object-f=
lag-field" style=3D"">https://www.iana.org/assignments/pcep/pcep.xhtml#srp-=
object-flag-field</a>) Dont we want that refer to this new draft since we h=
ave updated the text ?</font></div><div class=3D"gmail_default" style=3D"">=
<font face=3D"verdana, sans-serif"><br></font></div><div class=3D"gmail_def=
ault" style=3D""><font face=3D"verdana, sans-serif">Thanks,</font></div><di=
v class=3D"gmail_default" style=3D""><font face=3D"verdana, sans-serif">Har=
i</font></div><div class=3D"gmail_default" style=3D""><font face=3D"verdana=
, sans-serif"><br></font></div><div class=3D"gmail_default" style=3D"font-f=
amily:verdana,sans-serif;font-size:small"><br></div></div>

--000000000000c51635059326a7c3--


From nobody Sun Sep 22 13:16:58 2019
Return-Path: <adrian@olddog.co.uk>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7840A12002E for <pce@ietfa.amsl.com>; Sun, 22 Sep 2019 13:16:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level: 
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NbGSbgJLUnom for <pce@ietfa.amsl.com>; Sun, 22 Sep 2019 13:16:55 -0700 (PDT)
Received: from mta8.iomartmail.com (mta8.iomartmail.com [62.128.193.158]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 498FC120024 for <pce@ietf.org>; Sun, 22 Sep 2019 13:16:55 -0700 (PDT)
Received: from vs1.iomartmail.com (vs1.iomartmail.com [10.12.10.121]) by mta8.iomartmail.com (8.14.4/8.14.4) with ESMTP id x8MKGrLP005789; Sun, 22 Sep 2019 21:16:53 +0100
Received: from vs1.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id B704B2203C; Sun, 22 Sep 2019 21:16:52 +0100 (BST)
Received: from asmtp2.iomartmail.com (unknown [10.12.10.249]) by vs1.iomartmail.com (Postfix) with ESMTPS id A24E92203A; Sun, 22 Sep 2019 21:16:52 +0100 (BST)
Received: from LAPTOPK7AS653V ([87.112.72.158]) (authenticated bits=0) by asmtp2.iomartmail.com (8.14.4/8.14.4) with ESMTP id x8MKGobx031637 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 22 Sep 2019 21:16:51 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Hariharan Ananthakrishnan'" <hari@netflix.com>
Cc: <pce@ietf.org>
References: <CAL70W4q1DJ3WsGyN+88sXkCU+VT0omn9u3vzQzB1_GmTc4AH3w@mail.gmail.com>
In-Reply-To: <CAL70W4q1DJ3WsGyN+88sXkCU+VT0omn9u3vzQzB1_GmTc4AH3w@mail.gmail.com>
Date: Sun, 22 Sep 2019 21:16:50 +0100
Organization: Old Dog Consulting
Message-ID: <037901d57182$abe9c890$03bd59b0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQDVPz5ZV7qb86ImGNLuJLFaUtsACqk4g45g
Content-Language: en-gb
X-Originating-IP: 87.112.72.158
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-24928.000
X-TM-AS-Result: No--8.272-10.0-31-10
X-imss-scan-details: No--8.272-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-24928.000
X-TMASE-Result: 10--8.271600-10.000000
X-TMASE-MatchedRID: HXSqh3WYKfuWfDtBOz4q23FPUrVDm6jtBhfhOps3jahXPwnnY5XL5FEt MRGFGDWD2tmoqiGUvaKmQiqBg0hpSG8Nr8jnZavLH9HlIp7fUBGu+ACrt1e+WqMVwpOQMj2MSeQ h3pm1dj45Rg1eyvWfXTgOA5268BU3N2GXzj6bC8JcrmR4Jr5uaAvxMaV6x4s8RjNrjV0arFLoFU 9MRXQZvXFKqE7VNqHUCCCt1s6uEATsAGjS6lxxKsK1Ib9JAALxKNlHmNt0jkqbKItl61J/yY3BZ j4qY5QbDMq3z/Y/gtV5zdAzex5xZokQ9TKobLo+CTyeS37lsYVwuCW4yLXaAa53mhMMi7Tbx6os yv7X5oKUTGVAhB5EbQ==
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/osqEawrdc0WHjjlugmYCiF1upb8>
Subject: Re: [Pce] Shepherd Review of draft-farrel-pce-stateful-flags-01
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Sep 2019 20:16:58 -0000

Hi,

I=E2=80=99m willing to be guided here.

I don=E2=80=99t think the new draft makes any changes to how a code =
point seen in in the wild should be interpreted.
And the =E2=80=9Cupdates=E2=80=9D relationship will be in place.

But if people think it is valuable we could have=E2=80=A6

IANA maintains a registry called the =E2=80=9CPath Computation Element =
Protocol (PCEP) Numbers=E2=80=9D registry with a subregistry called " =
SRP Object Flag Field". IANA is requested to update the Reference in =
that subregistry to include a reference to this document in addition to =
[RFC8281].

Best,
Adrian

> This document is well written and clear. Thanks for the update. Please =
find below
> my comments on draft-farrel-pce-stateful-flags-01.
>
> OLD:
> 8. IANA Considerations
> This document makes no requests for IANA action
>
> NEW:
> The current IANA for this object has reference to "RFC8281" =
(https://www.iana.org/
> assignments/pcep/pcep.xhtml#srp-object-flag-field) Dont we want that =
refer to this
> new draft since we have updated the text ?


From nobody Mon Sep 23 01:20:48 2019
Return-Path: <julien.meuric@orange.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42D32120128 for <pce@ietfa.amsl.com>; Mon, 23 Sep 2019 01:20:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.29
X-Spam-Level: 
X-Spam-Status: No, score=-0.29 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FORGED_MUA_MOZILLA=2.309, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kKfa25ImObKj for <pce@ietfa.amsl.com>; Mon, 23 Sep 2019 01:20:46 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F006F120121 for <pce@ietf.org>; Mon, 23 Sep 2019 01:20:45 -0700 (PDT)
Received: from opfedar00.francetelecom.fr (unknown [xx.xx.xx.11]) by opfedar22.francetelecom.fr (ESMTP service) with ESMTP id 46cHMJ5kcSz2yGt; Mon, 23 Sep 2019 10:20:44 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.57]) by opfedar00.francetelecom.fr (ESMTP service) with ESMTP id 46cHMJ4dbCzCqk4; Mon, 23 Sep 2019 10:20:44 +0200 (CEST)
Received: from [10.193.71.44] (10.114.13.247) by OPEXCAUBM6D.corporate.adroot.infra.ftgroup (10.114.13.57) with Microsoft SMTP Server (TLS) id 14.3.468.0; Mon, 23 Sep 2019 10:20:44 +0200
To: <adrian@olddog.co.uk>, 'Hariharan Ananthakrishnan' <hari@netflix.com>
CC: <pce@ietf.org>
References: <CAL70W4q1DJ3WsGyN+88sXkCU+VT0omn9u3vzQzB1_GmTc4AH3w@mail.gmail.com> <037901d57182$abe9c890$03bd59b0$@olddog.co.uk>
From: <julien.meuric@orange.com>
Organization: Orange
Message-ID: <26690_1569226844_5D88805C_26690_4_1_8e686ec4-f6dd-c80a-74dd-f1dbf60ea43d@orange.com>
Date: Mon, 23 Sep 2019 10:20:43 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <037901d57182$abe9c890$03bd59b0$@olddog.co.uk>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-Originating-IP: [10.114.13.247]
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/41CkO-orVOxd6Lj6e8AKHuMQbDQ>
Subject: Re: [Pce] Shepherd Review of draft-farrel-pce-stateful-flags-01
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Sep 2019 08:20:47 -0000

Hi,

IMHO, including the new reference in the registry could be valuable and
makes no harm. And now that the text is written, why leaving it out?

Thanks Hari and Adrian,

Julien


On 22/09/2019 22:16, Adrian Farrel wrote:
> Hi,
>
> I’m willing to be guided here.
>
> I don’t think the new draft makes any changes to how a code point seen in in the wild should be interpreted.
> And the “updates” relationship will be in place.
>
> But if people think it is valuable we could have…
>
> IANA maintains a registry called the “Path Computation Element Protocol (PCEP) Numbers” registry with a subregistry called " SRP Object Flag Field". IANA is requested to update the Reference in that subregistry to include a reference to this document in addition to [RFC8281].
>
> Best,
> Adrian
>
>> This document is well written and clear. Thanks for the update. Please find below
>> my comments on draft-farrel-pce-stateful-flags-01.
>>
>> OLD:
>> 8. IANA Considerations
>> This document makes no requests for IANA action
>>
>> NEW:
>> The current IANA for this object has reference to "RFC8281" (https://www.iana.org/
>> assignments/pcep/pcep.xhtml#srp-object-flag-field) Dont we want that refer to this
>> new draft since we have updated the text ?
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu 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 ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information 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 delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.


From nobody Mon Sep 23 03:41:38 2019
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A30E1207FF; Mon, 23 Sep 2019 03:41:36 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: pce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.102.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: pce@ietf.org
Message-ID: <156923529602.17153.16206115759250626103@ietfa.amsl.com>
Date: Mon, 23 Sep 2019 03:41:36 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/mqU7acijTXwS5QQmWTWAmHI6j_Y>
Subject: [Pce] I-D Action: draft-farrel-pce-stateful-flags-02.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Sep 2019 10:41:36 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Path Computation Element WG of the IETF.

        Title           : Updated Rules for Processing Stateful PCE Request Parameters Flags
        Author          : Adrian Farrel
	Filename        : draft-farrel-pce-stateful-flags-02.txt
	Pages           : 6
	Date            : 2019-09-23

Abstract:
   Extensions to the Path Computation Element communications Protocol
   (PCEP) to support stateful Path Computation Elements (PCEs) are
   defined in RFC 8231.  One of the extensions is the Stateful PCE
   Request Parameters (SRP) object.  That object includes a Flags field
   that is a set of 32 bit flags, and RFC 8281 defines an IANA registry
   for tracking assigned flags.  However, RFC 8231 does not explain how
   an implementation should set unassigned flags in transmitted
   messages, nor how an implementation should process unassigned,
   unknown, or unsupported flags in received messages.

   This document updates RFC 8231 by defining the correct behaviors.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-farrel-pce-stateful-flags/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-farrel-pce-stateful-flags-02
https://datatracker.ietf.org/doc/html/draft-farrel-pce-stateful-flags-02

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-farrel-pce-stateful-flags-02


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Mon Sep 23 03:45:03 2019
Return-Path: <adrian@olddog.co.uk>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3ABE9120807 for <pce@ietfa.amsl.com>; Mon, 23 Sep 2019 03:45:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bPUbdeqYO5Ju for <pce@ietfa.amsl.com>; Mon, 23 Sep 2019 03:44:59 -0700 (PDT)
Received: from mta7.iomartmail.com (mta7.iomartmail.com [62.128.193.157]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 15B0D1207FF for <pce@ietf.org>; Mon, 23 Sep 2019 03:44:58 -0700 (PDT)
Received: from vs2.iomartmail.com (vs2.iomartmail.com [10.12.10.123]) by mta7.iomartmail.com (8.14.4/8.14.4) with ESMTP id x8NAivYA018494 for <pce@ietf.org>; Mon, 23 Sep 2019 11:44:57 +0100
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 72A2F22042 for <pce@ietf.org>; Mon, 23 Sep 2019 11:44:56 +0100 (BST)
Received: from asmtp1.iomartmail.com (unknown [10.12.10.248]) by vs2.iomartmail.com (Postfix) with ESMTPS id 5DF7722048 for <pce@ietf.org>; Mon, 23 Sep 2019 11:44:56 +0100 (BST)
Received: from LAPTOPK7AS653V ([62.60.61.127]) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.4/8.14.4) with ESMTP id x8NAitL6028047 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <pce@ietf.org>; Mon, 23 Sep 2019 11:44:56 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <pce@ietf.org>
References: <156923529602.17153.16206115759250626103@ietfa.amsl.com>
In-Reply-To: <156923529602.17153.16206115759250626103@ietfa.amsl.com>
Date: Mon, 23 Sep 2019 11:44:55 +0100
Organization: Old Dog Consulting
Message-ID: <042701d571fb$f05d6440$d1182cc0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQJSoXD8jdeIF7eS8ljVXi+aftJBOKY+tK7Q
Content-Language: en-gb
X-Originating-IP: 62.60.61.127
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-24928.005
X-TM-AS-Result: No--16.263-10.0-31-10
X-imss-scan-details: No--16.263-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-24928.005
X-TMASE-Result: 10--16.262700-10.000000
X-TMASE-MatchedRID: vbSD0OnL8/Jor4mPA3EMtnFPUrVDm6jtWw/S0HB7eoMiXE6jAom+xeMC y75Xgp5qlbWusee2uNvvPv7ExP3sV2FSCbxk53PfDHEg6thbROwZskwWqoib3CjCkOoEU36vWmr Yr8SaWTVHSYz7tSK8Whf5Pn/5586ND2VuZEXfbiSqDSBu0tUhr8ZJvtGKTC9XckmGbcDQFh/zw9 wqo6kGZsXQ6cZhT4QYRdMpuWoOWqvsEz9ycWwbCn41AgV24Xnf9wXxnluKnXvSpzLct3VK/lcBf jjXtvYaMDydwFW0h0sAf/HImzvCGL8q1zjO7UWhFcK/QGNGRL2pXdWa4gU0S9rbWin3863fsmc+ HzD5HmiEijVvY3+ENOGzdbsR7OPYcydwnP3Uz7HH9K2ZqHQWln0tCKdnhB58vqq8s2MNhPDPPeN 6HN6d7OXcVWh4vfMcC24oEZ6SpSkgbhiVsIMQKxZ5+8y352uC
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/o8LJR0wlDYO7zuzqzQgNvDoLFTY>
Subject: Re: [Pce] I-D Action: draft-farrel-pce-stateful-flags-02.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Sep 2019 10:45:01 -0000

New revision to ask IANA to add this document as a reference in the
appropriate registry (as suggested by Hari).

-----Original Message-----
From: Pce <pce-bounces@ietf.org> On Behalf Of internet-drafts@ietf.org
Sent: 23 September 2019 11:42
To: i-d-announce@ietf.org
Cc: pce@ietf.org
Subject: [Pce] I-D Action: draft-farrel-pce-stateful-flags-02.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Path Computation Element WG of the IETF.

        Title           : Updated Rules for Processing Stateful PCE Request
Parameters Flags
        Author          : Adrian Farrel
	Filename        : draft-farrel-pce-stateful-flags-02.txt
	Pages           : 6
	Date            : 2019-09-23

Abstract:
   Extensions to the Path Computation Element communications Protocol
   (PCEP) to support stateful Path Computation Elements (PCEs) are
   defined in RFC 8231.  One of the extensions is the Stateful PCE
   Request Parameters (SRP) object.  That object includes a Flags field
   that is a set of 32 bit flags, and RFC 8281 defines an IANA registry
   for tracking assigned flags.  However, RFC 8231 does not explain how
   an implementation should set unassigned flags in transmitted
   messages, nor how an implementation should process unassigned,
   unknown, or unsupported flags in received messages.

   This document updates RFC 8231 by defining the correct behaviors.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-farrel-pce-stateful-flags/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-farrel-pce-stateful-flags-02
https://datatracker.ietf.org/doc/html/draft-farrel-pce-stateful-flags-02

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-farrel-pce-stateful-flags-02


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/

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


From nobody Mon Sep 23 08:04:18 2019
Return-Path: <noreply@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 75BF712082A; Mon, 23 Sep 2019 08:04:16 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Hariharan Ananthakrishnan via Datatracker <noreply@ietf.org>
To: <db3546@att.com>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.102.0
Auto-Submitted: auto-generated
Precedence: bulk
Cc: iesg-secretary@ietf.org, pce@ietf.org, Hariharan Ananthakrishnan <hari@netflix.com>, pce-chairs@ietf.org, hari@netflix.com
Message-ID: <156925105647.17213.8813968271367888385.idtracker@ietfa.amsl.com>
Date: Mon, 23 Sep 2019 08:04:16 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/Xpz-U8lmvIjmD91J0KsNje-Loy0>
Subject: [Pce] Publication has been requested for draft-farrel-pce-stateful-flags-02
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Sep 2019 15:04:17 -0000

Hariharan Ananthakrishnan has requested publication of draft-farrel-pce-stateful-flags-02 as Proposed Standard on behalf of the PCE working group.

Please verify the document's state at https://datatracker.ietf.org/doc/draft-farrel-pce-stateful-flags/


From nobody Mon Sep 23 17:48:24 2019
Return-Path: <kaduk@mit.edu>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9B4D12009C; Mon, 23 Sep 2019 17:48:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sK3JLTENQ4GR; Mon, 23 Sep 2019 17:48:11 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82DD6120045; Mon, 23 Sep 2019 17:48:11 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x8O0m5v3001276 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 23 Sep 2019 20:48:08 -0400
Date: Mon, 23 Sep 2019 17:48:05 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Mahend Negi <mahend.ietf@gmail.com>
Cc: Dhruv Dhody <dhruv.ietf@gmail.com>, The IESG <iesg@ietf.org>, draft-ietf-pce-stateful-path-protection@ietf.org, Julien Meuric <julien.meuric@orange.com>, pce-chairs <pce-chairs@ietf.org>, pce@ietf.org
Message-ID: <20190924004805.GA6424@kduck.mit.edu>
References: <156876388231.17411.6094234033866939217.idtracker@ietfa.amsl.com> <CAB75xn4L2RE0vo44bt332kUL7Nh=LryKpJ3BSHRRnHggz8v3vQ@mail.gmail.com> <20190919210236.GB48975@kduck.mit.edu> <CAM5Nu_wQnQpkgK-X4=YZ9y2NHyNo3AdonsrGgxG32497TTy2Zg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAM5Nu_wQnQpkgK-X4=YZ9y2NHyNo3AdonsrGgxG32497TTy2Zg@mail.gmail.com>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/-tDClYjA98U4tVTrMYhfz63s73k>
Subject: Re: [Pce] Benjamin Kaduk's Discuss on draft-ietf-pce-stateful-path-protection-10: (with DISCUSS and COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Sep 2019 00:48:15 -0000

Hi Mahendra,

Thanks for the links.  What's in the diff generally looks good; I think we
may still need to have a bit more discussion here about items (1) and (4)
(for the latter, I'm not sure if the plan is still to update the table to
list everything or just leave it to the body text).

Also, with respect to (7), I think there was at least one place in the text
where we mention that the source, destination, and tunnel ID must match
where we don't also mention the protection type matching.  Maybe it's
sufficiently less important that we don't need to mention it everywhere,
but I'll mention it just in case.

Thanks,

Ben

On Sun, Sep 22, 2019 at 09:06:24PM +0530, Mahend Negi wrote:
> Hi Ben/Dhruv,
> 
> Thanks for the review and clarification. Comments are incorporated in the
> working copy (links below).
> 
> Working copy:
> https://github.com/mahendnegi/ietf/blob/master/pce/path-protection/iesg/draft-ietf-pce-stateful-path-protection-11.txt
> Diff:
> https://github.com/mahendnegi/ietf/commit/c51efb2b025d545e066b9b13de6d84de48d1a03c
> 
> Please do share your opinion.
> 
> Thanks,
> Mahendra
> 
> 
> On Fri, Sep 20, 2019 at 2:33 AM Benjamin Kaduk <kaduk@mit.edu> wrote:
> 
> > Hi Dhruv,
> >
> > On Wed, Sep 18, 2019 at 11:45:23AM +0530, Dhruv Dhody wrote:
> > > Hi Ben,
> > >
> > > Thanks for your review, let me start the discussion and the authors
> > > can interject as needed.
> >
> > Thanks; it's a great start.
> >
> > > On Wed, Sep 18, 2019 at 5:14 AM Benjamin Kaduk via Datatracker
> > > <noreply@ietf.org> wrote:
> > > >
> > > > Benjamin Kaduk has entered the following ballot position for
> > > > draft-ietf-pce-stateful-path-protection-10: Discuss
> > > >
> > > > When responding, please keep the subject line intact and reply to all
> > > > email addresses included in the To and CC lines. (Feel free to cut this
> > > > introductory paragraph, however.)
> > > >
> > > >
> > > > Please refer to
> > https://www.ietf.org/iesg/statement/discuss-criteria.html
> > > > for more information about IESG DISCUSS and COMMENT positions.
> > > >
> > > >
> > > > The document, along with other ballot positions, can be found here:
> > > >
> > https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-path-protection/
> > > >
> > > >
> > > >
> > > > ----------------------------------------------------------------------
> > > > DISCUSS:
> > > > ----------------------------------------------------------------------
> > > >
> > > > (1) draft-ietf-pce-association-group notes that "PCEP extensions that
> > define
> > > > a new association type should clarify the relationship between the SVEC
> > > > object and the association type, if any".  Where do we do so for the
> > > > path protection association type?
> > > >
> > >
> > > This is discussed in
> > >
> > https://tools.ietf.org/html/draft-ietf-pce-association-diversity-10#section-5.3
> > ,
> > > where it is more relevant. This draft includes the relationship with
> > > diversity association in Section 5.
> >
> > A naive reading of the linked section would be that it applies only to the
> > "Disjointness Association Type" defined in that document.  I'm not in a
> > position to claim that the reasoning in that document does not apply to
> > this one, but I think we should make a more clear link between the Path
> > Protection ASsociation Type and the discussion in that document.
> >
> > > > (2) Section 3.2 says:
> > > >
> > > >       Protection Type (PT): 6 bits - This field is as defined in
> > > >       Section 14.1 of [RFC4872] to indicate the LSP protection type in
> > > >       use.
> > > >
> > > > There doesn't seem to be a registry created by RFC 4872 to track these
> > > > PT values, so I assume that the way to allocate a new value is
> > > > "standards-track RFC that Updates: RFC 4872".  Is that also the way to
> > > > allocate new PT values for PPAG usage?  How would someone updating RFC
> > > > 4872 to allocate a new type know to consider/document whether it
> > applies
> > > > for PPAG usage?
> > > >
> > >
> > > That's true. Maybe we can add this text - "Any type already defined or
> > > that could be defined in the future for use in the RSVP-TE PROTECTION
> > > object is acceptable in this TLV unless explicitly stated otherwise."
> >
> > To be honest, that's probably good enough in practice, since it seems
> > somewhat unlikely that the last bit is ever going to get allocated (though,
> > I guess technically the field could be converted to an integer instead of
> > flags).  I do still have to wonder how the reader would know *where* it
> > would be stated otherwise, and how the author of a document defining a new
> > type would know to consider our use case as well as the RFC 4872 use case.
> >
> > > > (3) In Section 4.3:
> > > >
> > > >    A PCE can create/update working and protection LSPs independently.
> > > >    As specified in [I-D.ietf-pce-association-group], Association Groups
> > > >    can be created by both the PCE and the PCC.  Further, a PCE can
> > > >
> > > > The requirement that source, destination, and tunnel ID of all LSPs
> > > > within a PPAG MUST be the same is new to this document, so I think we
> > > > need to specify error handling for when attempts to update LSPs
> > > > independently would violate that invariant (presumably in Section 4.5).
> > > >
> > >
> > > In the existing error case in Section 4.5 we could make it "add or
> > update".
> >
> > Wording it right might be a little finicky, but that's fine in general.
> >
> > > > (4) In Section 6.3:
> > > >
> > > >                                       IANA is requested to allocate new
> > > >    error values within the "PCEP-ERROR Object Error Types and Values"
> > > >    sub-registry of the PCEP Numbers registry, as follows:
> > > >
> > > > The following table only lists Error-values.  What Error-type(s) should
> > > > they be associated with?
> > > >
> > >
> > > It is mentioned in the text, but worth making it explicit in the table
> > as well.
> > >
> > > > (5) We don't say which objects the PPAG TLV can appear in.  (Section
> > 3.2
> > > > says "[t]he Path Protection Association TLV is an optional TLV for use
> > > > with the Path Protection Association Type", but it's hard to interpret
> > > > that as meaning "for use [only] with the ASSOCIATION object defined in
> > > > draft-ietf-pce-association-group", especially since there is a "path
> > > > protection association type" already (and it's a codepoint in the
> > > > "ASSOCIATION Type Field" registry).
> > > >
> > >
> > > We can update to - "The Path Protection Association TLV is an optional
> > > TLV for use in the ASSOCIATION Object with the Path Protection
> > > Association Type."
> >
> > Thanks!
> >
> > > > (6) I'm not sure if a change to the document is needed here, but
> > perhaps
> > > > some discussion is in order: we say that a given LSP can belong to more
> > > > than one PPAG, but only allow one PPAG TLV per [some context that
> > > > remains unclear; see (5)].  I don't have a good handle for whether
> > these
> > > > two requirements are potentially in conflict: that is, whether a single
> > > > PPAG TLV would have to specify the flags that apply for both PPAGs that
> > > > a given LSP is a member of, or if the containing objects serve to scope
> > > > the PPAG TLV flags' interpretation.
> > > >
> > >
> > > When a given LSP belong to more than one PPAG, we expect to have
> > > multiple ASSOCIATION Object for each PPAG with each of them having a
> > > single PPAG TLV.
> >
> > Sounds good, and quite natural given (5).
> >
> > > > (7) Do the Protection Type fields of the PPAG TLV in the various LSPs
> > > > that are members of the same PPAG need to match, in the same way that
> > > > the source/destination/tunnel-ID do?
> > > >
> > >
> > > Yes. Authors should make that explicit.
> >
> > Thanks
> >
> > > >
> > > > ----------------------------------------------------------------------
> > > > COMMENT:
> > > > ----------------------------------------------------------------------
> > > >
> > > > Section 1
> > > >
> > > >    This document specifies a stateful PCEP extension to associate two
> > or
> > > >    more LSPs for the purpose of setting up path protection.  The
> > > >    proposed extension covers the following scenarios:
> > > >
> > > > nit: after publication, it doesn't really seem like a *proposed*
> > > > extension anymore.
> > > >
> > > > Section 3.1
> > > >
> > > >    LSPs are not associated by listing the other LSPs with which they
> > > >    interact, but rather by making them belong to an association group
> > > >    referred to as "Path Protection Association Group" (PPAG) in this
> > > >    document.  [...]
> > > >
> > > > The first 2/3 of this sentence is a (true) generic statement about all
> > > > association groups, which exist outside of this document in a generic
> > > > fashion.  I strongly suggest rewording this to make clear that the PPAG
> > > > is the specific association (group) type used for this document's
> > > > functionality but that other association groups are possible.  The
> > > > current wording implies that the PPAG is the only association possible,
> > > > and it is just given a special name for this document's purposes.
> > > >
> > > >    [I-D.ietf-pce-association-group] specifies the mechanism for the
> > > >    capability advertisement of the Association types supported by a
> > PCEP
> > > >    speaker by defining a ASSOC-Type-List TLV to be carried within an
> > > >    OPEN object.  This capability exchange for the Association type
> > > >    described in this document (i.e.  Path Protection Association Type)
> > > >    MAY be done before using the policy association, i.e., the PCEP
> > > >    speaker MAY include the Path Protection Association Type (TBD1) in
> > > >    the ASSOC-Type-List TLV before using the PPAG in the PCEP messages.
> > > >
> > > > Why is this only MAY and not MUST?
> > > >
> > >
> > > In [I-D.ietf-pce-association-group] we explicitly did not mandate the
> > > capability exchange for all association types and let each type decide
> > > for itself. This association type fits into where the capability
> > > exchange is optional. When the capability exchange was added in
> > > [I-D.ietf-pce-association-group], there was a desire from the WG to
> > > keep it optional for already defined/implemented protection
> > > association type. Also this is a basic feature in path computation and
> > > it is expected to be supported universally. In a corner case there is
> > > an error handling for unknown/unsupported association-type to take
> > > care of it.
> >
> > Okay, thanks for giving me the backstory.
> >
> > > >    This Association type is dynamic in nature and created by the PCC or
> > > >
> > > > nit: is it the type that is dynamic or the associations of that type?
> > > >
> > >
> > > It is the type. [I-D.ietf-pce-association-group] has dynamic or
> > > operator-configured association, this one is dynamic.
> >
> > Ah, of course, I had forgotten about that division of configuration.
> >
> > > >       Protecting (P): 1 bit - This bit is as defined in Section 14.1 of
> > > >       [RFC4872] to indicate if the LSP is working or protection LSP.
> > > >
> > > >       Secondary (S): 1 bit - This bit is as defined in Section 14.1 of
> > > >       [RFC4872] to indicate if the LSP is primary or secondary LSP.
> > The
> > > >       S flag is ignored if the P flag is not set.
> > > >
> > > > Just to check my understanding (no change expected to result): if P is
> > > > zero, the LSP is working, and thus we know that it's primary since it's
> > > > actively carrying traffic?
> > > >
> > >
> > > Yes, Working LSPs are always primary.
> > >
> > >
> > > > Section 3.2
> > > >
> > > > nit(?) The section heading does not match the name of the TLV requested
> > > > in the IANA considerations, nor do we mention here that "PPAG TLV" is
> > > > synonymous with it.
> > > >
> > > >    If the TLV is missing, it is considered that the LSP is the working
> > > >    LSP (i.e. as if P bit is unset).
> > > >
> > > > Is this conditional on the LSP being part of a PPAG, or does it hold
> > > > generically as well?
> > > >
> > >
> > > IMHO when part of a PPAG i.e. association object but no TLV.
> >
> > It may be worth making the text explicit about it.
> >
> > > > Section 4.5
> > > >
> > > >    As per the processing rules specified in section 5.4 of
> > > >    [I-D.ietf-pce-association-group], if a PCEP speaker does not support
> > > >
> > > > There is no Section 5.4 in draft-ietf-pce-association-group-10;
> > > > presumably this was supposed to be Section 6.4?
> > > >
> > > >    A given LSP MAY belong to more than one PPAG.  If there is a
> > conflict
> > > >
> > > > While I'm not arguing to remove this option, I'm also a bit confused at
> > > > how useful having a single LSP be in multiple PPAGs woud be, given the
> > > > need for source/destination/tunnel-ID to match.
> > > >
> > >
> > > One working LSP could have multiple protection LSPs with each
> > > belonging to a different association.
> > >
> > > >    When the protection type is set to 1+1 or 1:N with N=1, there MUST
> > be
> > > >    only one working LSP and one protection LSP within a PPAG.  If a
> > PCEP
> > > >    speaker attempts to add another working/protection LSP, the PCEP
> > peer
> > > >    MUST send PCErr with Error-Type 26 (Association Error)
> > > >    [I-D.ietf-pce-association-group] and Error-Value TBD4 (Attempt to
> > add
> > > >    another working/protection LSP for Path Protection Association).
> > > >
> > > > This seems to prevent a scenario where there's a need to change the
> > > > protection LSP and a desire to do so without removing the protected
> > > > nature of the working LSP.  Unless it's presumed that this could always
> > > > be done by updating the protection LSP and it would never be necessary
> > > > to create a new one?  (Similarly for 1:N, though maybe less severe.)
> > > >
> > >
> > > One can remove the protection LSP and keep the association intact. The
> > > error will not be triggered.
> > > Also, PCEP messages are per LSP, when the first LSP is reported with
> > > association, it is bound to be the only LSP in the association.
> > > So the error in this section are focused only when one adds "another".
> >
> > I don't think that the points you cover above are what I was concerned
> > about -- I was thinking more along the lines of a "make-before-break"
> > scheme for changing what LSP is the protection LSP for a given working LSP.
> > Maybe given the timescales involved it's not an issue in practice, though.
> >
> > > Maybe we can add "..at maximum.." to make it clear?
> >
> > (I don't think that's needed.)
> >
> > Thanks!
> >
> > -Ben
> >
> > > > Section 5
> > > >
> > > >    [RFC4872] introduces the concept and mechanisms to support the
> > > >    association of one LSP to another LSP across different RSVP -
> > Traffic
> > > >    Engineering (RSVP-TE) sessions using ASSOCIATION and PROTECTION
> > > >    object.  The information in the PPAG TLV in PCEP as received from
> > the
> > > >    PCE, is used to trigger the signalling of working LSP and protection
> > > >    LSP, with the Path Protection Association Flags mapped to the
> > > >    corresponding fields in the PROTECTION Object in RSVP-TE.
> > > >
> > > > Just to check my understanding: this paragraph is saying that the
> > > > contents of the PPAG TLV received by the PCC is used as input to
> > > > populating the PROTECTION object that corresponds to the protection
> > > > group?
> > > >
> > >
> > > Yes.
> > >
> > > > Section 10.2
> > > >
> > > > I think RFCs 7525 and 8253 need to be normative (and please cite RFC
> > > > 7525 as BCP 195).
> > > >
> > > >
> > >
> > > Thanks!
> > > Dhruv
> >


From nobody Mon Sep 23 23:09:03 2019
Return-Path: <dhruv.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27AE8120119; Mon, 23 Sep 2019 23:08:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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, 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 oin9QCY6jIvE; Mon, 23 Sep 2019 23:08:52 -0700 (PDT)
Received: from mail-io1-xd2e.google.com (mail-io1-xd2e.google.com [IPv6:2607:f8b0:4864:20::d2e]) (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 EFC63120113; Mon, 23 Sep 2019 23:08:51 -0700 (PDT)
Received: by mail-io1-xd2e.google.com with SMTP id r26so1547749ioh.8; Mon, 23 Sep 2019 23:08:51 -0700 (PDT)
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=9lYJuNTwSjQ1pM9ytQX+gD1YNE8aozrr7n/yWGwZygE=; b=Snw37tlmhmRYtH8hGFxEucSCjC6aDxTZ4F8S0mUTCd8cDY05rN1AjOd2HZytbNsRHz mp+63b7h5g9u842nhTykqn9QNo8DDVSm+fbJXHqeeFwChqkoCbOUV0k5HpS92FwZ+uIa tm7jXfuap2VZGDw2AmEQHPJO47PItTfygbhWTtLfYus6wUJKGVSaydNUBK6QMNV8ZOfs aVCgX8cHwkzwgrrYvRA01N00JPZoTsZA+NXr3g5yZMXc69v+J37Kb9jhmiyRUzTDS27r cXZa3yPTpqsgDBI8gEGX/p7E8bcKkx5iHHTmvI/Xq85hN4O0ahGDaXBLR2Tm44Cb7rBF iTvw==
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=9lYJuNTwSjQ1pM9ytQX+gD1YNE8aozrr7n/yWGwZygE=; b=TkDQAheZX+/KgO1HXYH4IDD9Oj4O1Hpxz1uXgc/pawZmUwCGmHtk+LPFfdMXv9QHat clV9lPbhGWR9gUANyunLtDVq8n5pp5z0GxLE3e6MFYnoquwIYRa+pQnqrUPqSmhMCc6M SIkBha9t/EgGYsKMb8CkFYazVMgBwJKFqZJb4H3AAGnLDdMAxpLrQcgw8uvQvPypiqC2 BaUWfpEN6H3thdDuk/qIO3hfKbix7WE51nGcveHW2vUEu8LMIQjxL+wRs9svb5LGb5V3 q859FIgN6b+caDoH4HmvRrWR4c/1ndyDfWBLGajJE5xy4XF8gWUenNnJwCO7KwV3URg4 /1IQ==
X-Gm-Message-State: APjAAAX1I8fq3iIx9X8AN0kRGzZTCwRQwLkkefyuNt6c/xP2y/yS4CP+ eSoS0na0J6Ipxj9h2odk3A6NbGsUiJGUOMKN5Ag=
X-Google-Smtp-Source: APXvYqxgiFNz+THpz77wcfVDvnc3wckHNe3Car+m1GIfHwodNBkjb6ykup8xgqS0Bi/Tz+2GTKcguhYpZ2WTK/RyhFw=
X-Received: by 2002:a5e:da4d:: with SMTP id o13mr1586311iop.124.1569305330741;  Mon, 23 Sep 2019 23:08:50 -0700 (PDT)
MIME-Version: 1.0
References: <156876388231.17411.6094234033866939217.idtracker@ietfa.amsl.com> <CAB75xn4L2RE0vo44bt332kUL7Nh=LryKpJ3BSHRRnHggz8v3vQ@mail.gmail.com> <20190919210236.GB48975@kduck.mit.edu>
In-Reply-To: <20190919210236.GB48975@kduck.mit.edu>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Tue, 24 Sep 2019 11:38:13 +0530
Message-ID: <CAB75xn553Ft1i1zDnYqDgSZZf57eQF6Ej1FOpbqSWAuqgVPOxA@mail.gmail.com>
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pce-stateful-path-protection@ietf.org, Julien Meuric <julien.meuric@orange.com>, pce-chairs <pce-chairs@ietf.org>, pce@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/-P6RMHXnW6o7LKv-luJd85RYqSQ>
Subject: Re: [Pce] Benjamin Kaduk's Discuss on draft-ietf-pce-stateful-path-protection-10: (with DISCUSS and COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Sep 2019 06:08:56 -0000

Hi Ben,

Apologies for the delay. I am replying this email where we tackle
points that needed some more discussion.

On Fri, Sep 20, 2019 at 2:32 AM Benjamin Kaduk <kaduk@mit.edu> wrote:
>
> Hi Dhruv,
>
> On Wed, Sep 18, 2019 at 11:45:23AM +0530, Dhruv Dhody wrote:
> > Hi Ben,
> >
> > Thanks for your review, let me start the discussion and the authors
> > can interject as needed.
>
> Thanks; it's a great start.
>
> > On Wed, Sep 18, 2019 at 5:14 AM Benjamin Kaduk via Datatracker
> > <noreply@ietf.org> wrote:
> > >
> > > Benjamin Kaduk has entered the following ballot position for
> > > draft-ietf-pce-stateful-path-protection-10: Discuss
> > >
> > > When responding, please keep the subject line intact and reply to all
> > > email addresses included in the To and CC lines. (Feel free to cut this
> > > introductory paragraph, however.)
> > >
> > >
> > > Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> > > for more information about IESG DISCUSS and COMMENT positions.
> > >
> > >
> > > The document, along with other ballot positions, can be found here:
> > > https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-path-protection/
> > >
> > >
> > >
> > > ----------------------------------------------------------------------
> > > DISCUSS:
> > > ----------------------------------------------------------------------
> > >
> > > (1) draft-ietf-pce-association-group notes that "PCEP extensions that define
> > > a new association type should clarify the relationship between the SVEC
> > > object and the association type, if any".  Where do we do so for the
> > > path protection association type?
> > >
> >
> > This is discussed in
> > https://tools.ietf.org/html/draft-ietf-pce-association-diversity-10#section-5.3,
> > where it is more relevant. This draft includes the relationship with
> > diversity association in Section 5.
>
> A naive reading of the linked section would be that it applies only to the
> "Disjointness Association Type" defined in that document.  I'm not in a
> position to claim that the reasoning in that document does not apply to
> this one, but I think we should make a more clear link between the Path
> Protection ASsociation Type and the discussion in that document.
>

The direct relationship is between the 'Disjointness Association Type'
and SVEC. But it is natural to include both Protection association and
disjoint association together. If SVEC is also present the
relationship is as per the Section 5.3 of
[I-D.ietf-pce-association-diversity]. Suppose if only protection
association is present and SVEC object, there is no direct
relationship and both object would be processed.

I suggest we add this text to make sure reader is aware of SVEC - "The
relationship between the Synchronization VECtor (SVEC) object and the
Disjointness Association is described in section 5.3 of
[I-D.ietf-pce-association-diversity]."


> > > (2) Section 3.2 says:
> > >
> > >       Protection Type (PT): 6 bits - This field is as defined in
> > >       Section 14.1 of [RFC4872] to indicate the LSP protection type in
> > >       use.
> > >
> > > There doesn't seem to be a registry created by RFC 4872 to track these
> > > PT values, so I assume that the way to allocate a new value is
> > > "standards-track RFC that Updates: RFC 4872".  Is that also the way to
> > > allocate new PT values for PPAG usage?  How would someone updating RFC
> > > 4872 to allocate a new type know to consider/document whether it applies
> > > for PPAG usage?
> > >
> >
> > That's true. Maybe we can add this text - "Any type already defined or
> > that could be defined in the future for use in the RSVP-TE PROTECTION
> > object is acceptable in this TLV unless explicitly stated otherwise."
>
> To be honest, that's probably good enough in practice, since it seems
> somewhat unlikely that the last bit is ever going to get allocated (though,
> I guess technically the field could be converted to an integer instead of
> flags).  I do still have to wonder how the reader would know *where* it
> would be stated otherwise, and how the author of a document defining a new
> type would know to consider our use case as well as the RFC 4872 use case.
>

I guess such an update would happen in TEAS; and historically PCE and
TEAS work very closely, as well as share the same AD. I think we are
quite safe here.

In case you were wondering why flags - we chose PT as flags as per RFC
4872 where this is called "LSP (Protection Type) Flags".

> > > (3) In Section 4.3:
> > >
> > >    A PCE can create/update working and protection LSPs independently.
> > >    As specified in [I-D.ietf-pce-association-group], Association Groups
> > >    can be created by both the PCE and the PCC.  Further, a PCE can
> > >
> > > The requirement that source, destination, and tunnel ID of all LSPs
> > > within a PPAG MUST be the same is new to this document, so I think we
> > > need to specify error handling for when attempts to update LSPs
> > > independently would violate that invariant (presumably in Section 4.5).
> > >
> >
> > In the existing error case in Section 4.5 we could make it "add or update".
>
> Wording it right might be a little finicky, but that's fine in general.
>
> > > (4) In Section 6.3:
> > >
> > >                                       IANA is requested to allocate new
> > >    error values within the "PCEP-ERROR Object Error Types and Values"
> > >    sub-registry of the PCEP Numbers registry, as follows:
> > >
> > > The following table only lists Error-values.  What Error-type(s) should
> > > they be associated with?
> > >
> >
> > It is mentioned in the text, but worth making it explicit in the table as well.
> >

Lets update the table as well. Request authors to update.

> > > (5) We don't say which objects the PPAG TLV can appear in.  (Section 3.2
> > > says "[t]he Path Protection Association TLV is an optional TLV for use
> > > with the Path Protection Association Type", but it's hard to interpret
> > > that as meaning "for use [only] with the ASSOCIATION object defined in
> > > draft-ietf-pce-association-group", especially since there is a "path
> > > protection association type" already (and it's a codepoint in the
> > > "ASSOCIATION Type Field" registry).
> > >
> >
> > We can update to - "The Path Protection Association TLV is an optional
> > TLV for use in the ASSOCIATION Object with the Path Protection
> > Association Type."
>
> Thanks!
>
> > > (6) I'm not sure if a change to the document is needed here, but perhaps
> > > some discussion is in order: we say that a given LSP can belong to more
> > > than one PPAG, but only allow one PPAG TLV per [some context that
> > > remains unclear; see (5)].  I don't have a good handle for whether these
> > > two requirements are potentially in conflict: that is, whether a single
> > > PPAG TLV would have to specify the flags that apply for both PPAGs that
> > > a given LSP is a member of, or if the containing objects serve to scope
> > > the PPAG TLV flags' interpretation.
> > >
> >
> > When a given LSP belong to more than one PPAG, we expect to have
> > multiple ASSOCIATION Object for each PPAG with each of them having a
> > single PPAG TLV.
>
> Sounds good, and quite natural given (5).
>
> > > (7) Do the Protection Type fields of the PPAG TLV in the various LSPs
> > > that are members of the same PPAG need to match, in the same way that
> > > the source/destination/tunnel-ID do?
> > >
> >
> > Yes. Authors should make that explicit.
>

Sure. Request authors to add.

> Thanks
>
> > >
> > > ----------------------------------------------------------------------
> > > COMMENT:
> > > ----------------------------------------------------------------------
> > >
> > > Section 1
> > >
> > >    This document specifies a stateful PCEP extension to associate two or
> > >    more LSPs for the purpose of setting up path protection.  The
> > >    proposed extension covers the following scenarios:
> > >
> > > nit: after publication, it doesn't really seem like a *proposed*
> > > extension anymore.
> > >
> > > Section 3.1
> > >
> > >    LSPs are not associated by listing the other LSPs with which they
> > >    interact, but rather by making them belong to an association group
> > >    referred to as "Path Protection Association Group" (PPAG) in this
> > >    document.  [...]
> > >
> > > The first 2/3 of this sentence is a (true) generic statement about all
> > > association groups, which exist outside of this document in a generic
> > > fashion.  I strongly suggest rewording this to make clear that the PPAG
> > > is the specific association (group) type used for this document's
> > > functionality but that other association groups are possible.  The
> > > current wording implies that the PPAG is the only association possible,
> > > and it is just given a special name for this document's purposes.
> > >
> > >    [I-D.ietf-pce-association-group] specifies the mechanism for the
> > >    capability advertisement of the Association types supported by a PCEP
> > >    speaker by defining a ASSOC-Type-List TLV to be carried within an
> > >    OPEN object.  This capability exchange for the Association type
> > >    described in this document (i.e.  Path Protection Association Type)
> > >    MAY be done before using the policy association, i.e., the PCEP
> > >    speaker MAY include the Path Protection Association Type (TBD1) in
> > >    the ASSOC-Type-List TLV before using the PPAG in the PCEP messages.
> > >
> > > Why is this only MAY and not MUST?
> > >
> >
> > In [I-D.ietf-pce-association-group] we explicitly did not mandate the
> > capability exchange for all association types and let each type decide
> > for itself. This association type fits into where the capability
> > exchange is optional. When the capability exchange was added in
> > [I-D.ietf-pce-association-group], there was a desire from the WG to
> > keep it optional for already defined/implemented protection
> > association type. Also this is a basic feature in path computation and
> > it is expected to be supported universally. In a corner case there is
> > an error handling for unknown/unsupported association-type to take
> > care of it.
>
> Okay, thanks for giving me the backstory.
>
> > >    This Association type is dynamic in nature and created by the PCC or
> > >
> > > nit: is it the type that is dynamic or the associations of that type?
> > >
> >
> > It is the type. [I-D.ietf-pce-association-group] has dynamic or
> > operator-configured association, this one is dynamic.
>
> Ah, of course, I had forgotten about that division of configuration.
>
> > >       Protecting (P): 1 bit - This bit is as defined in Section 14.1 of
> > >       [RFC4872] to indicate if the LSP is working or protection LSP.
> > >
> > >       Secondary (S): 1 bit - This bit is as defined in Section 14.1 of
> > >       [RFC4872] to indicate if the LSP is primary or secondary LSP.  The
> > >       S flag is ignored if the P flag is not set.
> > >
> > > Just to check my understanding (no change expected to result): if P is
> > > zero, the LSP is working, and thus we know that it's primary since it's
> > > actively carrying traffic?
> > >
> >
> > Yes, Working LSPs are always primary.
> >
> >
> > > Section 3.2
> > >
> > > nit(?) The section heading does not match the name of the TLV requested
> > > in the IANA considerations, nor do we mention here that "PPAG TLV" is
> > > synonymous with it.
> > >
> > >    If the TLV is missing, it is considered that the LSP is the working
> > >    LSP (i.e. as if P bit is unset).
> > >
> > > Is this conditional on the LSP being part of a PPAG, or does it hold
> > > generically as well?
> > >
> >
> > IMHO when part of a PPAG i.e. association object but no TLV.
>
> It may be worth making the text explicit about it.
>
> > > Section 4.5
> > >
> > >    As per the processing rules specified in section 5.4 of
> > >    [I-D.ietf-pce-association-group], if a PCEP speaker does not support
> > >
> > > There is no Section 5.4 in draft-ietf-pce-association-group-10;
> > > presumably this was supposed to be Section 6.4?
> > >
> > >    A given LSP MAY belong to more than one PPAG.  If there is a conflict
> > >
> > > While I'm not arguing to remove this option, I'm also a bit confused at
> > > how useful having a single LSP be in multiple PPAGs woud be, given the
> > > need for source/destination/tunnel-ID to match.
> > >
> >
> > One working LSP could have multiple protection LSPs with each
> > belonging to a different association.
> >
> > >    When the protection type is set to 1+1 or 1:N with N=1, there MUST be
> > >    only one working LSP and one protection LSP within a PPAG.  If a PCEP
> > >    speaker attempts to add another working/protection LSP, the PCEP peer
> > >    MUST send PCErr with Error-Type 26 (Association Error)
> > >    [I-D.ietf-pce-association-group] and Error-Value TBD4 (Attempt to add
> > >    another working/protection LSP for Path Protection Association).
> > >
> > > This seems to prevent a scenario where there's a need to change the
> > > protection LSP and a desire to do so without removing the protected
> > > nature of the working LSP.  Unless it's presumed that this could always
> > > be done by updating the protection LSP and it would never be necessary
> > > to create a new one?  (Similarly for 1:N, though maybe less severe.)
> > >
> >
> > One can remove the protection LSP and keep the association intact. The
> > error will not be triggered.
> > Also, PCEP messages are per LSP, when the first LSP is reported with
> > association, it is bound to be the only LSP in the association.
> > So the error in this section are focused only when one adds "another".
>
> I don't think that the points you cover above are what I was concerned
> about -- I was thinking more along the lines of a "make-before-break"
> scheme for changing what LSP is the protection LSP for a given working LSP.
> Maybe given the timescales involved it's not an issue in practice, though.
>

Maybe worth adding some text here to be safe - "During the
make-before-break (MBB) procedure, two paths will briefly coexist. The
error handling related to number of LSPs allowed in a PPAG MUST NOT be
applied during MBB."

I hope this message clears all the remaining points.

Thanks!
Dhruv

> > Maybe we can add "..at maximum.." to make it clear?
>
> (I don't think that's needed.)
>
> Thanks!
>
> -Ben
>
> > > Section 5
> > >
> > >    [RFC4872] introduces the concept and mechanisms to support the
> > >    association of one LSP to another LSP across different RSVP - Traffic
> > >    Engineering (RSVP-TE) sessions using ASSOCIATION and PROTECTION
> > >    object.  The information in the PPAG TLV in PCEP as received from the
> > >    PCE, is used to trigger the signalling of working LSP and protection
> > >    LSP, with the Path Protection Association Flags mapped to the
> > >    corresponding fields in the PROTECTION Object in RSVP-TE.
> > >
> > > Just to check my understanding: this paragraph is saying that the
> > > contents of the PPAG TLV received by the PCC is used as input to
> > > populating the PROTECTION object that corresponds to the protection
> > > group?
> > >
> >
> > Yes.
> >
> > > Section 10.2
> > >
> > > I think RFCs 7525 and 8253 need to be normative (and please cite RFC
> > > 7525 as BCP 195).
> > >
> > >
> >
> > Thanks!
> > Dhruv


From nobody Mon Sep 23 23:09:30 2019
Return-Path: <dhruv.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 254AD120119; Mon, 23 Sep 2019 23:09:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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, 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 4R-zD4H9swyK; Mon, 23 Sep 2019 23:09:25 -0700 (PDT)
Received: from mail-io1-xd2e.google.com (mail-io1-xd2e.google.com [IPv6:2607:f8b0:4864:20::d2e]) (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 BFAB4120113; Mon, 23 Sep 2019 23:09:25 -0700 (PDT)
Received: by mail-io1-xd2e.google.com with SMTP id b19so1591320iob.4; Mon, 23 Sep 2019 23:09:25 -0700 (PDT)
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:content-transfer-encoding; bh=urqBtNrTxCGd07q6KjY+cV5PAO8JMeBVb/gwdWDpSUA=; b=sVKx8SmY/P6h4p0azyLtkrzfCDf8gHxnDp+M8JT3sokOJqvg2uxXL9eKTPvmsPOYfP TDTtrhHjikZCiclEtbmjKsExIGNUaKQ5OiDvgfrKRYiywA/FilDJNMPdTj+3GSxR6xaY 99c9Hbq3Ub5DzwZVzokM2rAwXuDmE+a0WcyYZDUGoq3lPQ0LEueN/CIBPTsQNxRx7wwX Q+UsiJ1xIR2wNlXMU23zc7YqLBbKn6fEhV3KYCsLKGO6eb5fKAvfMzL1KLvM1VPr0ka+ /iFu4WeL2b4e+NzgWpFpm3mF8clXz0ZnGFtEicxdPaCBtcv0tz6gbUeugVndpClF/xbe Gp/A==
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:content-transfer-encoding; bh=urqBtNrTxCGd07q6KjY+cV5PAO8JMeBVb/gwdWDpSUA=; b=DpnCchWQbUEcREVIstZ/jXOlydkKMf2QIfKgsPk9JQATNZF+BQZ6AVeHh15J4PH73Z mCLHKElL4Wh6JztAiAGv6eDa1B/oUmQ7sHOYIvpyeqCLvk9BPAV/ezaI5xi74HhNjZqn 43xuWjjiyUMcal7V52NhT7efeYNnCsmlRC3EPee+Wm5O9rsEQYH6CCefqCLl0PDLQE61 1ekHBVs1IgYte36vwTxIJlKtGake7v3St4SXLGGwf3b+owSW3aCQzmgS/zlJr7qcaqvX jdArZ97AIuYnDlt0JOsp6SdBSe6Uj+gVG/Q1+NxHb2DCrP5MKQeRnq9uegrDBz3NJPoC nw2g==
X-Gm-Message-State: APjAAAUF6PwgNSzVb8d6M/+/pCSz4Z1/M4z1EzPpgwfE/9bQmfictgrv U16SeR1fRlEQs/F/Zq3LKlKSRG4Re3vohv7K51945Q==
X-Google-Smtp-Source: APXvYqy406AEzDFEK2bxNEIO5wMI0KKZb5+tyeuTpQu+3kuX7baGTNRYG8mpZwzNacggXeOSbW8BEKqCma2NNpC8IgU=
X-Received: by 2002:a6b:c38f:: with SMTP id t137mr1726447iof.137.1569305364401;  Mon, 23 Sep 2019 23:09:24 -0700 (PDT)
MIME-Version: 1.0
References: <156884048251.4597.11655493158307521478.idtracker@ietfa.amsl.com>
In-Reply-To: <156884048251.4597.11655493158307521478.idtracker@ietfa.amsl.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Tue, 24 Sep 2019 11:38:48 +0530
Message-ID: <CAB75xn4ih=5h3ZSomt+kKBYzRZGCrMbXME3bQDC4Z9ud-7GNhg@mail.gmail.com>
To: Roman Danyliw <rdd@cert.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pce-stateful-path-protection@ietf.org, Julien Meuric <julien.meuric@orange.com>, pce-chairs <pce-chairs@ietf.org>, pce@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/H-IU3llq_HVXHH6yvbqgZIbng3c>
Subject: Re: [Pce] Roman Danyliw's No Objection on draft-ietf-pce-stateful-path-protection-10: (with COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Sep 2019 06:09:29 -0000

Hi Roman,

Thanks for your comments. Few thoughts...

On Thu, Sep 19, 2019 at 2:31 AM Roman Danyliw via Datatracker
<noreply@ietf.org> wrote:
>
> Roman Danyliw has entered the following ballot position for
> draft-ietf-pce-stateful-path-protection-10: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-path-protection/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> ** Section 3.2.  It took me a bit to understand that the Path Protection
> Association TLV goes in an ASSOCIATION Object per Section 6 of
> [I-D.ietf-pce-association-group].  On initial reading of =E2=80=9C[t]he P=
ath Protection
> Association TLV is an optional TLV for use with the Path Protection Assoc=
iation
> Type=E2=80=9D this relationship wasn=E2=80=99t clear.  I=E2=80=99d recomm=
end an editorial update to
> make it clearer.  I believe this is related Ben Kaduk=E2=80=99s DISCUSS #=
5 (which I
> support).
>

This is updated to "The Path Protection Association TLV is an optional
TLV for use in the ASSOCIATION Object with the Path Protection
Association Type."

> ** Section 3.2  The protection type field specifies the protection type o=
f the
> LSP.  Section 1 notes that =E2=80=9Cone working LSP [can be associated wi=
th] one or
> more protection LSPs using the generic association mechanism.=E2=80=9D  A=
ssuming a case
> were multiple protection LSPs are specified, is it valid for the protecti=
ons
> type to be different?
>

An explicit error text has been added to make sure LSPs within the
association group has the same Protection Type.

> ** Section 4.5.  For clarity, I would recommend being precise with the ex=
act
> code point names when discussing conflicting combinations of protection t=
ypes.
> For example, s/1+1 or 1:N/1+1 (i.e., protection type=3D0x08 or 0x10) or 1=
:N
> (i.e., protection type =3D 0x04) with N=3D1 per <insert IANA registry nam=
e>/
>

Based on Barry's comment this was simplified and now we have just two
case 1+1 and 1:N. The protection type values could be added in
brackets.

> Baring these combinations, are other any other remaining combinations of
> protection types legal given different protection LSPs in the same PPAG (=
e.g.,
> 0x1 + 0x2)?
>

As per RFC 4872, all "other" values are reserved.
As per Ben's comment, this was added - "Any type already defined or
that could be defined in the future for use in the RSVP-TE PROTECTION
object is acceptable in this TLV unless explicitly stated otherwise."

> ** Editorial Nits:
> -- Section 1.  s/effect/affect/
>
> -- Section 1.  Per =E2=80=9CWhen the working LSPs are computed and contro=
lled by the
> PCE, there is benefit in a mode of operation where protection LSPs are as
> well=E2=80=9D, I couldn=E2=80=99t parse the second clause.
>
>

Thanks!
Dhruv


From nobody Mon Sep 23 23:12:56 2019
Return-Path: <dhruv.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74BEF120115; Mon, 23 Sep 2019 23:12:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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, 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 U36zvAC7Px93; Mon, 23 Sep 2019 23:12:46 -0700 (PDT)
Received: from mail-io1-xd29.google.com (mail-io1-xd29.google.com [IPv6:2607:f8b0:4864:20::d29]) (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 3E9A7120113; Mon, 23 Sep 2019 23:12:46 -0700 (PDT)
Received: by mail-io1-xd29.google.com with SMTP id q1so1632516ion.1; Mon, 23 Sep 2019 23:12:46 -0700 (PDT)
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:content-transfer-encoding; bh=QKpqqddbJ5QucEgNpj5bhmYEbrX205v4SbdXrfiCxyo=; b=iQZJvbt32QvjLj9lunXwoP/mIHezX5dwp/16GBB+ephpUjac7FMDAxplkCYCDEv163 n75Q7PRPnkAJgHQWdw+g2z+YGeedbz8kHeh4swmhkHjWj6UmYuTmOX7kKnxDV2nr80Tr SFXF7CEPGRX7gCWoWBqCiJlnbXeDzZW+iricqLtICiCZspvKo6rpy20CyWe6T7xU6eud w2sW+A6O8Ukr+bpItjWDJwgTYA02P15xIBWfJ9cPiR8kZI7JZ+5my04fy5AeOxus8tz9 PVpwWULp2D3RhY14bXkefEHZpOGiG1tQopSVmMwTG2dezdKcyd9dytbcEkW1u3jEerli kpcg==
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:content-transfer-encoding; bh=QKpqqddbJ5QucEgNpj5bhmYEbrX205v4SbdXrfiCxyo=; b=KcQUojzP3SnUte0yX8MhIHWEB2XQ65auQzN0gF6oBlCCN0t4w92Ax3YUong/laIVmv cIEkWU2BiiBadjWtekbpkfsKfKzMSETGgg6d+EwyiMWh7KK9lynO70RFS0XAi/6QcAFm a6pfRqWbw0nvApQypU2M52UVpe0jkwDFkLixckclMQpCep25KO8ldaxA/VwqKz4TwWwO Nhg6AqR2CXn+PrlarhRLH6VmIeMqnGi/gBZha0l3X2uPXus14k+JYw2f9qIF3YrM0ITk QFDEf8lt5XGka4I6Os/UVbnjeGCvG6GUkPzMh5IqSIYBGucpn0Dx5Yo+YqBtCCHQl6O6 1s+A==
X-Gm-Message-State: APjAAAXMQFQZEAvtL+hPRnG/ptiYuWZLwaUkSjrBdQHh2i0kLLVDwZ/B UKW6Ec0mYc61SDTJY4dbxa/nwHv0ngSaSQQCh7U=
X-Google-Smtp-Source: APXvYqxR4WDN/jkmU50SrYO8ferh7Q2Jd7/2ZBsOtX4yDUCjNlW1Eo7E1aSAwkmQxH5P5VT+UB2oazpIwYNUYaFNNuc=
X-Received: by 2002:a5d:9dd4:: with SMTP id 20mr1514169ioo.1.1569305565453; Mon, 23 Sep 2019 23:12:45 -0700 (PDT)
MIME-Version: 1.0
References: <156884098570.4585.6466973426120663299.idtracker@ietfa.amsl.com>
In-Reply-To: <156884098570.4585.6466973426120663299.idtracker@ietfa.amsl.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Tue, 24 Sep 2019 11:42:09 +0530
Message-ID: <CAB75xn4=ptgPOOO1F=Mj5e924BqJvU5vPceadpqEN4ikuDxMJw@mail.gmail.com>
To: =?UTF-8?B?w4lyaWMgVnluY2tl?= <evyncke@cisco.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pce-stateful-path-protection@ietf.org, Julien Meuric <julien.meuric@orange.com>, pce-chairs <pce-chairs@ietf.org>, pce@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/9JFjF2HpW3EI9QDTZzw_3zmJO2A>
Subject: Re: [Pce]  =?utf-8?q?=C3=89ric_Vyncke=27s_No_Objection_on_draft-ietf-?= =?utf-8?q?pce-stateful-path-protection-10=3A_=28with_COMMENT=29?=
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Sep 2019 06:12:49 -0000

Hi Eric,

Thanks for your comments.

On Thu, Sep 19, 2019 at 2:39 AM =C3=89ric Vyncke via Datatracker
<noreply@ietf.org> wrote:
>
> =C3=89ric Vyncke has entered the following ballot position for
> draft-ietf-pce-stateful-path-protection-10: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-path-protection/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Thank you for the work put into this document. I am trusting the routing =
AD for
> their deep understanding of this document and their approval.
>
> Nevertheless, I have 2 COMMENTs which are mere questions of mine.
>
> Regards,
>
> -=C3=A9ric
>
> =3D=3D COMMENTS =3D=3D
>
> -- Section 3.2 --
> C.1) Any reason to have a field named "unassigned flags" rather than
> "reserved"? After all, those bits could be used later for something diffe=
rent
> than flags. Also applicable to section 6.2.
>

The encoding is to make the full 32 bits as a flag field called "Path
Protection Association Flags (32 bits)" with IANA registry for all 32
bits. RFC 4872 also considers "PT" as flags - "LSP (Protection Type)
Flags". We expect only flags (or fields represented as flags) in this
TLV in future. In case some other data needs to be encoded we expect
another TLV to be defined for it.

> C.2) is there any reason the "P", "S" and "PT" are described right to lef=
t ?
>
>

I guess because of the order of importance, we could check with RFC
editor later in case they have a concern.

Thanks!
Dhruv


From nobody Tue Sep 24 05:22:11 2019
Return-Path: <rdd@cert.org>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5793120096; Tue, 24 Sep 2019 05:22:02 -0700 (PDT)
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, 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 (1024-bit key) header.d=cert.org
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 o-xTl3CAEuL8; Tue, 24 Sep 2019 05:22:00 -0700 (PDT)
Received: from veto.sei.cmu.edu (veto.sei.cmu.edu [147.72.252.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61D72120233; Tue, 24 Sep 2019 05:22:00 -0700 (PDT)
Received: from delp.sei.cmu.edu (delp.sei.cmu.edu [10.64.21.31]) by veto.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id x8OCLuYH037781; Tue, 24 Sep 2019 08:21:56 -0400
DKIM-Filter: OpenDKIM Filter v2.11.0 veto.sei.cmu.edu x8OCLuYH037781
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1569327716; bh=2IA9wKNCsX2eIk66AKBB3D2C1C67z03XMB0aTQsyusw=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=EFSp+Se3KPjlkz4tkshxqW4CmsaYMqmdl3FnkxiGrfURcpcYfq9YOYl/OTB5p3XYK mPgqGdhUYsZuStgIo4+6VWa+kaZIcoJcHr431r5T+3S/zUpMOGuPJDH72cydWmBM/o 4LOPA3RPPKbhDM3L2l+mMOPV+lKbqPfFX3vIYNXM=
Received: from CASCADE.ad.sei.cmu.edu (cascade.ad.sei.cmu.edu [10.64.28.248]) by delp.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id x8OCLs1Q009597; Tue, 24 Sep 2019 08:21:54 -0400
Received: from MARATHON.ad.sei.cmu.edu ([10.64.28.250]) by CASCADE.ad.sei.cmu.edu ([10.64.28.248]) with mapi id 14.03.0468.000; Tue, 24 Sep 2019 08:21:54 -0400
From: Roman Danyliw <rdd@cert.org>
To: Dhruv Dhody <dhruv.ietf@gmail.com>
CC: The IESG <iesg@ietf.org>, "draft-ietf-pce-stateful-path-protection@ietf.org" <draft-ietf-pce-stateful-path-protection@ietf.org>, Julien Meuric <julien.meuric@orange.com>, pce-chairs <pce-chairs@ietf.org>, "pce@ietf.org" <pce@ietf.org>
Thread-Topic: Roman Danyliw's No Objection on draft-ietf-pce-stateful-path-protection-10: (with COMMENT)
Thread-Index: AQHVbmRDfvjd7IDUj0yUzcN1b5Ef+qc6o1QAgAAd98A=
Date: Tue, 24 Sep 2019 12:21:54 +0000
Message-ID: <359EC4B99E040048A7131E0F4E113AFC01B3464ED1@marathon>
References: <156884048251.4597.11655493158307521478.idtracker@ietfa.amsl.com> <CAB75xn4ih=5h3ZSomt+kKBYzRZGCrMbXME3bQDC4Z9ud-7GNhg@mail.gmail.com>
In-Reply-To: <CAB75xn4ih=5h3ZSomt+kKBYzRZGCrMbXME3bQDC4Z9ud-7GNhg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.64.22.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/RzNYMjg1J84dM_TCBMNEwSaXxfU>
Subject: Re: [Pce] Roman Danyliw's No Objection on draft-ietf-pce-stateful-path-protection-10: (with COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Sep 2019 12:22:03 -0000

SGkgRGhydXYhDQoNClRoYW5rcyBmb3IgdGhlc2UgcHJvcG9zZWQgZWRpdHMuICBUaGV5IGFkZHJl
c3MgbXkgY29tbWVudHMuDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTog
RGhydXYgRGhvZHkgW21haWx0bzpkaHJ1di5pZXRmQGdtYWlsLmNvbV0NCj4gU2VudDogVHVlc2Rh
eSwgU2VwdGVtYmVyIDI0LCAyMDE5IDI6MDkgQU0NCj4gVG86IFJvbWFuIERhbnlsaXcgPHJkZEBj
ZXJ0Lm9yZz4NCj4gQ2M6IFRoZSBJRVNHIDxpZXNnQGlldGYub3JnPjsgZHJhZnQtaWV0Zi1wY2Ut
c3RhdGVmdWwtcGF0aC0NCj4gcHJvdGVjdGlvbkBpZXRmLm9yZzsgSnVsaWVuIE1ldXJpYyA8anVs
aWVuLm1ldXJpY0BvcmFuZ2UuY29tPjsgcGNlLWNoYWlycw0KPiA8cGNlLWNoYWlyc0BpZXRmLm9y
Zz47IHBjZUBpZXRmLm9yZw0KPiBTdWJqZWN0OiBSZTogUm9tYW4gRGFueWxpdydzIE5vIE9iamVj
dGlvbiBvbiBkcmFmdC1pZXRmLXBjZS1zdGF0ZWZ1bC1wYXRoLQ0KPiBwcm90ZWN0aW9uLTEwOiAo
d2l0aCBDT01NRU5UKQ0KPiANCj4gSGkgUm9tYW4sDQo+IA0KPiBUaGFua3MgZm9yIHlvdXIgY29t
bWVudHMuIEZldyB0aG91Z2h0cy4uLg0KPiANCj4gT24gVGh1LCBTZXAgMTksIDIwMTkgYXQgMjoz
MSBBTSBSb21hbiBEYW55bGl3IHZpYSBEYXRhdHJhY2tlcg0KPiA8bm9yZXBseUBpZXRmLm9yZz4g
d3JvdGU6DQo+ID4NCj4gPiBSb21hbiBEYW55bGl3IGhhcyBlbnRlcmVkIHRoZSBmb2xsb3dpbmcg
YmFsbG90IHBvc2l0aW9uIGZvcg0KPiA+IGRyYWZ0LWlldGYtcGNlLXN0YXRlZnVsLXBhdGgtcHJv
dGVjdGlvbi0xMDogTm8gT2JqZWN0aW9uDQo+ID4NCj4gPiBXaGVuIHJlc3BvbmRpbmcsIHBsZWFz
ZSBrZWVwIHRoZSBzdWJqZWN0IGxpbmUgaW50YWN0IGFuZCByZXBseSB0byBhbGwNCj4gPiBlbWFp
bCBhZGRyZXNzZXMgaW5jbHVkZWQgaW4gdGhlIFRvIGFuZCBDQyBsaW5lcy4gKEZlZWwgZnJlZSB0
byBjdXQNCj4gPiB0aGlzIGludHJvZHVjdG9yeSBwYXJhZ3JhcGgsIGhvd2V2ZXIuKQ0KPiA+DQo+
ID4NCj4gPiBQbGVhc2UgcmVmZXIgdG8NCj4gPiBodHRwczovL3d3dy5pZXRmLm9yZy9pZXNnL3N0
YXRlbWVudC9kaXNjdXNzLWNyaXRlcmlhLmh0bWwNCj4gPiBmb3IgbW9yZSBpbmZvcm1hdGlvbiBh
Ym91dCBJRVNHIERJU0NVU1MgYW5kIENPTU1FTlQgcG9zaXRpb25zLg0KPiA+DQo+ID4NCj4gPiBU
aGUgZG9jdW1lbnQsIGFsb25nIHdpdGggb3RoZXIgYmFsbG90IHBvc2l0aW9ucywgY2FuIGJlIGZv
dW5kIGhlcmU6DQo+ID4gaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0
Zi1wY2Utc3RhdGVmdWwtcGF0aC1wcm90ZWN0aQ0KPiA+IG9uLw0KPiA+DQo+ID4NCj4gPg0KPiA+
IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0NCj4gPiBDT01NRU5UOg0KPiA+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4gPg0KPiA+
ICoqIFNlY3Rpb24gMy4yLiAgSXQgdG9vayBtZSBhIGJpdCB0byB1bmRlcnN0YW5kIHRoYXQgdGhl
IFBhdGgNCj4gPiBQcm90ZWN0aW9uIEFzc29jaWF0aW9uIFRMViBnb2VzIGluIGFuIEFTU09DSUFU
SU9OIE9iamVjdCBwZXIgU2VjdGlvbiA2DQo+ID4gb2YgW0ktRC5pZXRmLXBjZS1hc3NvY2lhdGlv
bi1ncm91cF0uICBPbiBpbml0aWFsIHJlYWRpbmcgb2Yg4oCcW3RdaGUNCj4gPiBQYXRoIFByb3Rl
Y3Rpb24gQXNzb2NpYXRpb24gVExWIGlzIGFuIG9wdGlvbmFsIFRMViBmb3IgdXNlIHdpdGggdGhl
DQo+ID4gUGF0aCBQcm90ZWN0aW9uIEFzc29jaWF0aW9uIFR5cGXigJ0gdGhpcyByZWxhdGlvbnNo
aXAgd2FzbuKAmXQgY2xlYXIuICBJ4oCZZA0KPiA+IHJlY29tbWVuZCBhbiBlZGl0b3JpYWwgdXBk
YXRlIHRvIG1ha2UgaXQgY2xlYXJlci4gIEkgYmVsaWV2ZSB0aGlzIGlzDQo+ID4gcmVsYXRlZCBC
ZW4gS2FkdWvigJlzIERJU0NVU1MgIzUgKHdoaWNoIEkgc3VwcG9ydCkuDQo+ID4NCj4gDQo+IFRo
aXMgaXMgdXBkYXRlZCB0byAiVGhlIFBhdGggUHJvdGVjdGlvbiBBc3NvY2lhdGlvbiBUTFYgaXMg
YW4gb3B0aW9uYWwgVExWDQo+IGZvciB1c2UgaW4gdGhlIEFTU09DSUFUSU9OIE9iamVjdCB3aXRo
IHRoZSBQYXRoIFByb3RlY3Rpb24gQXNzb2NpYXRpb24NCj4gVHlwZS4iDQoNClRoYW5rcy4gIFRo
YXQgaXMgbXVjaCBjbGVhcmVyLg0KDQo+ID4gKiogU2VjdGlvbiAzLjIgIFRoZSBwcm90ZWN0aW9u
IHR5cGUgZmllbGQgc3BlY2lmaWVzIHRoZSBwcm90ZWN0aW9uDQo+ID4gdHlwZSBvZiB0aGUgTFNQ
LiAgU2VjdGlvbiAxIG5vdGVzIHRoYXQg4oCcb25lIHdvcmtpbmcgTFNQIFtjYW4gYmUNCj4gPiBh
c3NvY2lhdGVkIHdpdGhdIG9uZSBvciBtb3JlIHByb3RlY3Rpb24gTFNQcyB1c2luZyB0aGUgZ2Vu
ZXJpYw0KPiA+IGFzc29jaWF0aW9uIG1lY2hhbmlzbS7igJ0gIEFzc3VtaW5nIGEgY2FzZSB3ZXJl
IG11bHRpcGxlIHByb3RlY3Rpb24gTFNQcw0KPiA+IGFyZSBzcGVjaWZpZWQsIGlzIGl0IHZhbGlk
IGZvciB0aGUgcHJvdGVjdGlvbnMgdHlwZSB0byBiZSBkaWZmZXJlbnQ/DQo+ID4NCj4gDQo+IEFu
IGV4cGxpY2l0IGVycm9yIHRleHQgaGFzIGJlZW4gYWRkZWQgdG8gbWFrZSBzdXJlIExTUHMgd2l0
aGluIHRoZQ0KPiBhc3NvY2lhdGlvbiBncm91cCBoYXMgdGhlIHNhbWUgUHJvdGVjdGlvbiBUeXBl
Lg0KDQo+ID4gKiogU2VjdGlvbiA0LjUuICBGb3IgY2xhcml0eSwgSSB3b3VsZCByZWNvbW1lbmQg
YmVpbmcgcHJlY2lzZSB3aXRoIHRoZQ0KPiA+IGV4YWN0IGNvZGUgcG9pbnQgbmFtZXMgd2hlbiBk
aXNjdXNzaW5nIGNvbmZsaWN0aW5nIGNvbWJpbmF0aW9ucyBvZg0KPiBwcm90ZWN0aW9uIHR5cGVz
Lg0KPiA+IEZvciBleGFtcGxlLCBzLzErMSBvciAxOk4vMSsxIChpLmUuLCBwcm90ZWN0aW9uIHR5
cGU9MHgwOCBvciAweDEwKSBvcg0KPiA+IDE6TiAoaS5lLiwgcHJvdGVjdGlvbiB0eXBlID0gMHgw
NCkgd2l0aCBOPTEgcGVyIDxpbnNlcnQgSUFOQSByZWdpc3RyeQ0KPiA+IG5hbWU+Lw0KPiA+DQo+
IA0KPiBCYXNlZCBvbiBCYXJyeSdzIGNvbW1lbnQgdGhpcyB3YXMgc2ltcGxpZmllZCBhbmQgbm93
IHdlIGhhdmUganVzdCB0d28NCj4gY2FzZSAxKzEgYW5kIDE6Ti4gVGhlIHByb3RlY3Rpb24gdHlw
ZSB2YWx1ZXMgY291bGQgYmUgYWRkZWQgaW4gYnJhY2tldHMuDQo+DQo+ID4gQmFyaW5nIHRoZXNl
IGNvbWJpbmF0aW9ucywgYXJlIG90aGVyIGFueSBvdGhlciByZW1haW5pbmcgY29tYmluYXRpb25z
DQo+ID4gb2YgcHJvdGVjdGlvbiB0eXBlcyBsZWdhbCBnaXZlbiBkaWZmZXJlbnQgcHJvdGVjdGlv
biBMU1BzIGluIHRoZSBzYW1lDQo+ID4gUFBBRyAoZS5nLiwNCj4gPiAweDEgKyAweDIpPw0KPiA+
DQo+IA0KPiBBcyBwZXIgUkZDIDQ4NzIsIGFsbCAib3RoZXIiIHZhbHVlcyBhcmUgcmVzZXJ2ZWQu
DQo+IEFzIHBlciBCZW4ncyBjb21tZW50LCB0aGlzIHdhcyBhZGRlZCAtICJBbnkgdHlwZSBhbHJl
YWR5IGRlZmluZWQgb3IgdGhhdA0KPiBjb3VsZCBiZSBkZWZpbmVkIGluIHRoZSBmdXR1cmUgZm9y
IHVzZSBpbiB0aGUgUlNWUC1URSBQUk9URUNUSU9OIG9iamVjdCBpcw0KPiBhY2NlcHRhYmxlIGlu
IHRoaXMgVExWIHVubGVzcyBleHBsaWNpdGx5IHN0YXRlZCBvdGhlcndpc2UuIg0KDQpUaGFua3Mu
ICBGb3IgYm90aCBvZiB0aGUgaXRlbXMgYWJvdmUsIHRoZSBwcm9wb3NlZCBhcHByb2FjaCBpcyBj
bGVhcmVyIGFuZCBhZGRyZXNzZXMgbXkgY29tbWVudC4NCg0KPiA+ICoqIEVkaXRvcmlhbCBOaXRz
Og0KPiA+IC0tIFNlY3Rpb24gMS4gIHMvZWZmZWN0L2FmZmVjdC8NCj4gPg0KPiA+IC0tIFNlY3Rp
b24gMS4gIFBlciDigJxXaGVuIHRoZSB3b3JraW5nIExTUHMgYXJlIGNvbXB1dGVkIGFuZCBjb250
cm9sbGVkDQo+ID4gYnkgdGhlIFBDRSwgdGhlcmUgaXMgYmVuZWZpdCBpbiBhIG1vZGUgb2Ygb3Bl
cmF0aW9uIHdoZXJlIHByb3RlY3Rpb24NCj4gPiBMU1BzIGFyZSBhcyB3ZWxs4oCdLCBJIGNvdWxk
buKAmXQgcGFyc2UgdGhlIHNlY29uZCBjbGF1c2UuDQo+ID4NCj4gPg0KDQpUaGFua3MsDQpSb21h
bg0KDQoNCj4gDQo+IFRoYW5rcyENCj4gRGhydXYNCg==


From nobody Tue Sep 24 07:06:34 2019
Return-Path: <dhruv.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F50B120854; Tue, 24 Sep 2019 07:06:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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, 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 jCPkzSkP2pJu; Tue, 24 Sep 2019 07:06:28 -0700 (PDT)
Received: from mail-io1-xd31.google.com (mail-io1-xd31.google.com [IPv6:2607:f8b0:4864:20::d31]) (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 E6682120845; Tue, 24 Sep 2019 07:06:27 -0700 (PDT)
Received: by mail-io1-xd31.google.com with SMTP id j4so4675854iog.11; Tue, 24 Sep 2019 07:06:27 -0700 (PDT)
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:content-transfer-encoding; bh=FPPWmV2FnXlpVVeDBR7vHj2wGvjoWsJn3Dk2adfN4Vs=; b=K5k/Js8z5/Pz5FP+/LNkMAmmaRP/Pe8f5z0isU6v7nZ/YJXDI7qQjBmkj0+wdjwysx vLiiIm3x36BBNeIOoTVwLr7UbAhYvJLVmBXaYcg6VG02OhxwmWuUT+nSBNCMgKyaCq4n ciRCCwROtLXYrpJmGEwRTKFs90Sv9MNCDzTevHwGzQQDF2qD7iF9LXIHQH6fk5eYC8Ir 2Iw68R23C5iMSChOj7ZRFxnkEKLtTPSmGWUHEtyZATgd5EGY+hMwTtuc2ybFLjfGf1wH Y36srP0njBnKwnuVzFEoBC/6dRQMtHpyhHqF3u9UNOq1AG12nhTdDaw6FMupZeT98C0H aehQ==
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:content-transfer-encoding; bh=FPPWmV2FnXlpVVeDBR7vHj2wGvjoWsJn3Dk2adfN4Vs=; b=T+vAmma8jauuIab2qJ7Snv+8JLuvpsPPBhwHrGZCfN3TINV7p88Afn8phZ4bBJyQ40 o+6KJsmETQ9nbQkZDZazQLDCzsq7tSxPgH3i3V1vToDiPWXMmOJ8JCgco9vgoklJJcAo Y25u9ykvf//IhiMwl6Gu3yO892KsOq1m/2J4IG+RQ93H2+I2oyolkeYSJY27+37/rW+7 N87xFf6auuXF2/vUOWPZwlyLJPMtd3+2LC/NO7Vtyjn4qk+2zXBCdDyEqPa7ULn6USXC tNJNTipE4YIKM09TCg8fsf6/jSwlC3rCHqqcg8QwFgXxRtWqq504K1U7DRaPhcaNqBG2 EBcA==
X-Gm-Message-State: APjAAAWtDFozGXeDTegHYCo4sYQ3N0rEScIg+ZNhHm1MiGkDcGyrN4IN Nvwdj28P2czd5Vk7HbQSXYEw0rZqLLmDOCx5yQU=
X-Google-Smtp-Source: APXvYqzfg5Sm7M+FLg0uK2zfc04/LIzI205F65zsZtuz1AT1yEFOeW4ZiN8+avUT9OAIG5Vr0zgnIMAyjVZuNZuG2kk=
X-Received: by 2002:a5d:9457:: with SMTP id x23mr3649555ior.14.1569333986942;  Tue, 24 Sep 2019 07:06:26 -0700 (PDT)
MIME-Version: 1.0
References: <156881612137.4479.15191325652251719065.idtracker@ietfa.amsl.com>
In-Reply-To: <156881612137.4479.15191325652251719065.idtracker@ietfa.amsl.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Tue, 24 Sep 2019 19:35:49 +0530
Message-ID: <CAB75xn7ffQRzKdiHf3U5asnFuOenBQoeHT-ER1Bdd=zeieiXtQ@mail.gmail.com>
To: Roman Danyliw <rdd@cert.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pce-stateful-hpce@ietf.org,  Adrian Farrel <adrian@olddog.co.uk>, pce-chairs <pce-chairs@ietf.org>, pce@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/zuNvwEEsu1CUtxqrvr0OryMTvt0>
Subject: Re: [Pce] Roman Danyliw's Discuss on draft-ietf-pce-stateful-hpce-13: (with DISCUSS and COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Sep 2019 14:06:33 -0000

Hi Roman,

Thanks for your review.

On Wed, Sep 18, 2019 at 7:45 PM Roman Danyliw via Datatracker
<noreply@ietf.org> wrote:
>
> Roman Danyliw has entered the following ballot position for
> draft-ietf-pce-stateful-hpce-13: Discuss
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-hpce/
>
>
>
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
> ** Section 4.  Per =E2=80=9CThe security considerations listed in [RFC823=
1], [RFC6805]
> and [RFC5440] apply to this document as well. As per [RFC6805], it is exp=
ected
> that the parent PCE will require all child PCEs to use full security when
> communicating with the parent.=E2=80=9D, the references make sense, thank=
s for making
> them.  My concern is in the definition of =E2=80=9Cuse full security=E2=
=80=9D.  I can see those
> words come from RFC6805, however, I can't find where that set of practice=
s is
> defined.  Can this please be clarified.
>

How about we update to "..full security (i.e. the highest security
mechanism available for PCEP)"?

>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> ** Section 4.  Per the recommendation to use TLS _or_ TCP-AO.
> -- I take the point from the SECDIR (thanks Stephen Farrell) about the (l=
ack
> of) deployment of AO.  My caution would be that TLS and TCP-AO provide
> different security mechanism and therefore imbue different security prope=
rties
> and this should be noted. (i.e., this isn=E2=80=99t a choice between like=
 options)
>

How about I make at "..and/or.."? RFC8253 encourages the use of TCP-AO
alongside TLS. This could do the trick of removing the sense of choice
without adding more text.

> -- As an editorial nit, it would be worth saying that guidance for implem=
enting
> using TLS with PCEP can be found in RFC8232.
>

You mean RFC 8253 right? Updated text -

   Thus it is RECOMMENDED to secure the PCEP session (between the P-PCE
   and the C-PCE) using Transport Layer Security (TLS) [RFC8446] (per
   the recommendations and best current practices in [RFC7525]) and/or
   TCP Authentication Option (TCP-AO) [RFC5925]. The guidance for
   implementing PCEP with TLS can be found in [RFC8253].

> ** Editorial Nits:
> Title.  Is the period at the end of the title necessary?
>
>

Removed.

Thanks!
Dhruv


From nobody Tue Sep 24 07:07:27 2019
Return-Path: <dhruv.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 968D11200EB; Tue, 24 Sep 2019 07:07:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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, 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 vdBzG0j9CbgP; Tue, 24 Sep 2019 07:07:23 -0700 (PDT)
Received: from mail-io1-xd36.google.com (mail-io1-xd36.google.com [IPv6:2607:f8b0:4864:20::d36]) (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 E92981200B3; Tue, 24 Sep 2019 07:07:22 -0700 (PDT)
Received: by mail-io1-xd36.google.com with SMTP id c6so4669704ioo.13; Tue, 24 Sep 2019 07:07:22 -0700 (PDT)
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=6mlkK2fiEn8ktcug0bF7iuIPLmflV3VXHcS9Jyp7bIc=; b=HX6X7WqpmaBdAZX9M33TXDt06+cIbBVq1QjvqfLM1yDHyJhfPxX2clsd4e7IrqufDd FxU+TZzzfJaAfQwla31Tp771/Adx6sFoKXnaEbMPPkgymR5j+Pmmd9qTo0AwCtvKD0Jw 8Rsb0khP53pstGKDb2sOaEkXck3v84d62wgMzJn8vDOjbvdccHSfHDUOU749UBdCWvW5 t2HotLXbMzFH+DyOiseTaZICGt2uvIVvrvrnUoR3sOeE1vAVXzP30uXb/gWeHGeWWq0D zLaX9k2pA7EJYX/uVf6hXzK6l/P2W7cX1+6gg7fFgNdm3vDjm3o5umn8gVHDuncUcswq W5aA==
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=6mlkK2fiEn8ktcug0bF7iuIPLmflV3VXHcS9Jyp7bIc=; b=kfq54q4J5as0kY52SAHg2Zq4T4Ua97oEtsptQ8XfofyymeGjOqHCtvgGsta1IMKos/ Qg1+d4abK69vpVJ/rxi0aeVTfzv4n9cAFswdDEa2dmzCVy3h5asSKOTxf0bbrWUZkA65 /t8PNHwgkWrcIYGhrLBoQEUAX2nj/MdUBbtOVJ/jhCeVn8g4ZpAO7EpQz4YIozVh8+b9 wjXYCHmDpIrNBzG9eGGD8GnNWuurPuZvrjzEoR7MeAXXTIuDu/OfMY/vIvwXS+aT7bfv Jis2wdimlmh0bsmld5QW4hczVcRSwlOoYng+wPxz3XBDQ+AvRG2TjkXWi/KZXmvQfvPv tLGA==
X-Gm-Message-State: APjAAAUQZt02wqpK51sleLN/RShi5leshbhx0qrMv0znC5wZwlrfbT8J pEjdr7kDJPaIXPq+mWdsCheE78ePVqKeHeC0VNlY7snJ
X-Google-Smtp-Source: APXvYqxZo/z22tiZ1lpSuAbo/M8Ha+302OFQjiCa6yzNfXCuPFofFjwFI1sh8sLU1VWvFa4KYDQHLI0PZEzDPEWP6hg=
X-Received: by 2002:a5d:9dd4:: with SMTP id 20mr3597119ioo.1.1569334041904; Tue, 24 Sep 2019 07:07:21 -0700 (PDT)
MIME-Version: 1.0
References: <156884459034.4565.10696493114905134845.idtracker@ietfa.amsl.com>
In-Reply-To: <156884459034.4565.10696493114905134845.idtracker@ietfa.amsl.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Tue, 24 Sep 2019 19:36:43 +0530
Message-ID: <CAB75xn5wp6EvhCVExn9sz4ipbxT+1GpPbW_fX8GOea6zh=tBpw@mail.gmail.com>
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pce-stateful-hpce@ietf.org,  Adrian Farrel <adrian@olddog.co.uk>, pce-chairs <pce-chairs@ietf.org>, pce@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/hopMsmu_xWOzdWJ01m97_dQl5gA>
Subject: Re: [Pce] Benjamin Kaduk's Discuss on draft-ietf-pce-stateful-hpce-13: (with DISCUSS and COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Sep 2019 14:07:26 -0000

Hi Ben,

Thanks for your review.

On Thu, Sep 19, 2019 at 3:39 AM Benjamin Kaduk via Datatracker
<noreply@ietf.org> wrote:
>
> Benjamin Kaduk has entered the following ballot position for
> draft-ietf-pce-stateful-hpce-13: Discuss
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-hpce/
>
>
>
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
> I think this should be pretty easy to resolve, though I'm not sure what
> the right way to do so it.
>
> Section 3 says:
>
>    [I-D.ietf-pce-hierarchy-extensions] defines the H-PCE Capability TLV
>    that is used in the Open message to advertise the H-PCE capability.
>    [RFC8231] defines the Stateful PCE Capability TLV used in the Open
>    message to indicate stateful support.  The presence of both TLVs in
>    an Open message indicates the support for stateful H-PCE operations
>    as described in this document.
>
> There is no normative reference relationship (in either direction)
> between draft-ietf-pce-hierarchy-extension and this document; I think
> that the use of the capability TLV to imply both sets of functionality
> implies some sort of normative relationship; we wouldn't want version
> skew between documents to induce breaking changes.  In particular, an
> implementation that already supports RFC 8231 and is implementing the
> hierarchy extensions would need to know to look at this document *and
> implement it*, or would unknowingly be noncompliant with this document
> and fail to interoperate with a peer that is compliant with this
> document.
>

How about we add normative text for this -

   [I-D.ietf-pce-hierarchy-extensions] defines the H-PCE Capability TLV
   that is used in the Open message to advertise the H-PCE capability.
   [RFC8231] defines the Stateful PCE Capability TLV used in the Open
   message to indicate stateful support. To indicates the support for
   stateful H-PCE operations described in this document, a PCEP speaker
   MUST include both TLVs in an Open message. It is RECOMMENDED that any
   implementation that supports stateful operations [RFC8231] and H-PCE
   [I-D.ietf-pce-hierarchy-extensions] would also implements the
   stateful H-PCE operations as described in this document.

This would be true in most deployments/implementations of C-PCE and
P-PCE that are also stateful!

>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Abstract
>
>                          This information may then be considered when
>    computing new traffic engineered LSPs, and for associated and
>    dependent LSPs, received from Path Computation Clients (PCCs). [...]
>
> nit: I'm not sure how to parse this sentence.  The best thing I can come
> up with is that "when computing new traffic engineered LSPs" and "for
> associated [...]" are two separate cases, which each could independently
> consider the information in question.  The first one makes sense, but
> for the second I'm left trying to parse "this information may then be
> considered for associated and dependent LSPs, received from PCCs", and
> it's not really clear what considering the PCE is going to do if it just
> sits there with information from the LSP-DB and information from PCCs (and
> not doing anything with the information).
>

Suggested update -

   A Stateful Path Computation Element (PCE) maintains information on
   the current network state received from the Path Computation Clients
   (PCCs), including: computed Label Switched Path (LSPs), reserved
   resources within the network, and pending path computation requests.
   This information may then be considered when computing path for a new
   traffic-engineered LSP or for any associated/dependent LSPs. The Path
   computation response from a PCE is helpful for the PCC to gracefully
   establish the computed LSP.


>    The Hierarchical Path Computation Element (H-PCE) architecture,
>    provides an architecture to allow the optimum sequence of
>    [...]
>
> nit: no comma here.
>
> Also, three paragraphs may be pushing the bounds of an abstract in RFC
> style.
>
> Section 1.1
>
>    path based on the domain connectivity information.  A Child PCE
>    (C-PCE) may be responsible for a single domain or multiple domains,
>    it is used to compute the intra-domain path based on its domain
>    topology information.
>
> nit: comma splice
>
>    This document presents general considerations for stateful PCEs, and
>    not Stateless PCEs, in the hierarchical PCE architecture.  In
>    particular, the behavior changes and additions to the existing
>    stateful PCE mechanisms (including PCE-initiated LSP setup and active
>    PCE usage) in the context of networks using the H-PCE architecture.
>
> nit: should "active PCE usage" read "active stateful PCE usage"?
>
> Section 1.2
>
>    The inter-domain LSP could be set up using the end-to-end signaling
>    as described in [RFC6805]. Additionally a per-domain stitched LSP
>
> Should I be reading this "could be set up using" as "this document
> describes how to set [the LSP] up using"?
>

Updated to -

   The end-to-end inter-domain path computation and setup is described
   in [RFC6805].

> Section 1.2.2
>
>    Different signaling methods for inter-domain RSVP-TE signaling are
>    identified in [RFC4726].  Contiguous LSPs are achieved using the
>
> nit: are the two "signaling"s redundant?
>
>    In case of a stateful P-PCE, the stateful P-PCE has to be aware of
>    the inter-domain LSPs for it to consider them during path
>    computation. For example, a domain diverse path from another LSP.
>
> nit: this last sentence is a sentence fragment.

Updated based on Barry's suggested text -

   A stateful P-PCE has to be aware of the inter-domain LSPs for it to
   consider them during path computation. For instance when a domain
   diverse path is required from another LSP, the P-PCE needs to be
   aware of the LSP.

>
>    In this document, for the Contiguous LSP, the above interactions are
>    only between the ingress domain C-PCE and the P-PCE. The use of
>    stateful operations for an inter-domain LSP between the
>    transit/egress domain C-PCEs towards the P-PCE is out of scope of
>    this document.
>
> nit: I suggest rewording to avoid the ambiguity of "towards" as applying
> to the inter-domain LSP vs. the use of stateful operations.
>

Changed to "and".

> Section 3
>
>    in the topology).  The P-PCE has no information about the content of
>    the child domains.  Each child domain has at least one PCE capable of
>
> nit: we could potentially reword this in light of the remarks made about
> ACTN previously.
>
>    computing paths across the domain.  These PCEs are known as C-PCEs
>    and have a direct relationship with the P-PCE.  The P-PCE builds the
>
> It might be good to forward-reference where we talk about this
> relationship in more detail.  (And, er, have more detail about the
> relationship than we currently do.)
>

This text is focused on what is described in RFC 6805, so added
reference to that.

>    and have a direct relationship with the P-PCE.  The P-PCE builds the
>    domain topology map either via direct configuration (allowing network
>    policy to also be applied) or from learned information received from
>    each C-PCE.
>
> Policy cannot be applied to information learned at runtime?
>

Updated

>    LSP State Report (EC-EP):  a child stateful PCE sends an LSP state
>       report to a Parent Stateful PCE whenever the state of a LSP
>       changes.
>
> With respect to "whenever the state of a LSP changes", is there a
> possibility of a state-change that is visible to the C-PCE but does not
> affect anything that the P-PCE knows about?  Is the state report still
> expected to be generated in such cases?
>

Yes / No
Updated text.

>    object to identify the Ingress (PCC). The PLSP-ID used in the
>    forwarded PCRpt by the C-PCE to P-PCE is same as the original one
>    used by the PCC.
>
> I couldn't quickly find an authoritative definition of what the PLSP-ID
> is; I see some discussion in RFC 8231 for the LSP Object, but am not
> sure if there is prior usage.
>

It is RFC 8231, added - PLSP-ID (PCEP-specific identifier for the LSP,
as per [RFC8231])

> Section 3.1
>
>    paths.  Each C-PCE computes a set of candidate path segments across
>    its domain and sends the results to the P-PCE. The P-PCE uses this
>    information to select path segments and concatenate them to derive
>    the optimal end-to-end inter-domain path.  The end-to-end path is
>    then sent to the C-PCE that received the initial path request, and
>    this C-PCE passes the path on to the PCC that issued the original
>    request.
>
> This is basically the same language as in RFC 6805, so I don't really
> expect changing it to be the right thing to do, but I'm confused about
> how the P-PCE is getting "candidate" segments from the C-PCEs but only
> has to tell the head-end which path got picked.  Are the other C-PCEs
> supposed to find out which of the candidates got used somehow?
>

The request to other C-PCEs is "stateless" in nature and thus once
they have computed path segments and provided the result to the P-PCE
they loose the state and dont care which candidate was picked.

> Section 3.2
>
>    a PCUpd message.  For LSP delegated to the P-PCE via the child PCE,
>    the P-PCE can use the same PCUpd message to request change to the C-
>    PCE (the Ingress domain PCE), the PCE further propagates the update
>    request to the PCC.
>
> nit: comma splice
>
> Section 4
>
> I expect this to not be the case, but just to check: is there a
> possibility for differing levels of authorization for different PCCs,
> e.g., where PCC A is allowed to request LSPs within the domain and to
> any other domain, but PCC B is not allowed to request LSPs to/through a
> subset of domain peers, and PCC C is only allowed to request LSPs within
> the local domain?
>

Yes, we do not have different levels of authorization.

> As Roman mentions, we don't have a picture of what "full security" means
> for child/parent communications.
>

How about we update to "..full security (i.e. the highest security
mechanism available for PCEP)"?

>
>    Thus it is RECOMMENDED to secure the PCEP session (between the P-PCE
>    and the C-PCE) using either Transport Layer Security (TLS) [RFC8253]
>    per the recommendations and best current practices in [RFC7525] or
>    TCP Authentication Option (TCP-AO) [RFC5925].
>
> It's not entirely clear to me that we need to call out TCP-AO here.
> Partially since, as Stephen noted in the secdir review, it doesn't seem
> to be implemented/deployed much, but also since RFC 8231 does call out
> that it recommends TLS for confidentiality protection, which TCP-AO does
> not provide.  There don't seem to be specific threats enumerated there
> that the confidentiality protects against, so I am not making a strong
> recommendation to remove TCP-AO from this text, but I'd like to better
> understand why it was added.
>

We decided to keep TCP-AO as it is still a good security feature even
though not implemented. At the same time it could be use alongside
TLS. The updated text as per Roman's comment -

   Thus it is RECOMMENDED to secure the PCEP session (between the P-PCE
   and the C-PCE) using Transport Layer Security (TLS) [RFC8446] (per
   the recommendations and best current practices in [RFC7525]) and/or
   TCP Authentication Option (TCP-AO) [RFC5925]. The guidance for
   implementing PCEP with TLS can be found in [RFC8253].

>    In case of TLS, due care needs to be taken while exposing the
>    parameters of the X.509 certificate, such as subjectAltName:otherName
>    which is set to Speaker Entity Identifier [RFC8232] as per [RFC8253],
>    to ensure uniqueness and avoid any mismatch.
>
> I'm not entirely sure which "mismatch" we would be concerned about.

We added this based on Stephen's comment to make sure that there is no
issue of conflict because of peer identification parameters exposed
via certificates. Maybe two peers using the same Speaker Entity
Identifier in the certificate. I think the TLS establishment would
fail but the advise still stands.

> And just to check: there aren't expected to be any privacy-like
> considerations for exposing the speaker entity identifier to a peer in a
> different domain, right?
>

Yes, IMHO this is fine.

> Section 5.7
>
> I'm not sure how appropriate it is to fully delegate (e.g.) propagation
> of errors to draft-ietf-pce-enhanced-errors (which is not even a
> normative reference!) -- it seems important to describe some expectation
> of the error handling either in this document or in a normative
> reference thereof.
>

Updated to -

   Apart from the basic error handling described in this document, an
   implementation could also use the enhanced error and notification
   mechanism for stateful H-PCE operations as per [I-D.ietf-pce-
   enhanced-errors]. Enhanced features such as error behavior
   propagation, notification and error criticality level, are further
   defined in [I-D.ietf-pce-enhanced-errors].

> Section 9.2
>
> I think RFCs 5925, 7525, and 8253 should be normative, and RFC 7525 can
> be cited as BCP 195.
>
>

Diff: https://tools.ietf.org/rfcdiff?url1=draft-ietf-pce-stateful-hpce-13&url2=https://raw.githubusercontent.com/dhruvdhody/ietf/master/draft-ietf-pce-stateful-hpce-14.txt

Thanks!
Dhruv


From nobody Wed Sep 25 01:27:37 2019
Return-Path: <dhruv.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56A79120122; Wed, 25 Sep 2019 01:27:27 -0700 (PDT)
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, FREEMAIL_FROM=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=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 RtuG9kZSJsE2; Wed, 25 Sep 2019 01:27:24 -0700 (PDT)
Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com [IPv6:2607:f8b0:4864:20::d2b]) (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 BA3FC12011B; Wed, 25 Sep 2019 01:27:24 -0700 (PDT)
Received: by mail-io1-xd2b.google.com with SMTP id r26so11549153ioh.8; Wed, 25 Sep 2019 01:27:24 -0700 (PDT)
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=rjYzGnExckWZIQdkXwfRNmmdf4SM/+aPi2jkgL4QAmU=; b=uWnRCp5DvTLVEX4JOr5xaQRBLCwrmonsgndl2c+01yO5cbvJvKQmKeHcCQi7e/fB2W xkRhpO0aiqYv3gKOBZQP2AiR3158t3gKB10Jwoaij6lOBeIlNY2trivS4IJDmZ32NjYA vsgMtBQ+lNj3KEcR17hsgwfSHQ6fJIxnRG8fElVzva6HcES7fYUZd2vpdRLHYKlu5ys1 MWVPDWv/zyCKhJzgBKthg2CYR1aPlJ1B8AgneA3102uE4rZMdESGQKOxEDpMFxwDOS7C c/iYUJoOnoz3P5yVagCH16cGsphkfpuTumwtFA/nNb7DizacJ7Gnv7//w9vi0J2HVLYN mxoA==
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=rjYzGnExckWZIQdkXwfRNmmdf4SM/+aPi2jkgL4QAmU=; b=BHiSUUpvZLoU6u4n2AZjy47HPBslFORrjH7c0Ls/gUNgqYTxy3wlrArKfPZi5haj9R G3w6LWheMxgmjQTat99VO7oD5saZCkK4Luk/F0es3vvhjdVX4AYNMirqFCe6ERGwccXX OTGdAQtdpSfkaa0rPKLFSgvh1tA1LUaXyyJQfndZ1p4uLjd74KSRJVryWy8052aJLPez pplao2S6kS37kSk7ZXIeoJrezw2JQsXxqQJ6W25dhvBYXNFDNuibTOxjh5CAotJWIWqk YJaEZp0ojqKwV1m1i3578I1DWN8gI/bY+SwKEodCuMsBVSaVTwkXTB2HcLmi3WeGgvKP EPdg==
X-Gm-Message-State: APjAAAVC1pmYvGQGTAgFRK85wBSfKq63KTvA6aVsoD4Bjt1x7cALTJL/ qouV3jEnVjNPWrRWkmRFh8Grc6b+VKxXZDAEoOM=
X-Google-Smtp-Source: APXvYqwg1yGBxZZ3bmgGLD5bVi5CuDAVE7tOp5T9bo6CkkF198yvy7Hm4MavtYviRYP6FYXqKXLP0E9qbJpOd3w3HP8=
X-Received: by 2002:a5e:d502:: with SMTP id e2mr6144486iom.279.1569400043776;  Wed, 25 Sep 2019 01:27:23 -0700 (PDT)
MIME-Version: 1.0
References: <156874887441.17499.7855633347557404477.idtracker@ietfa.amsl.com> <CAB75xn5MUrTS43f5boMo4Kq7dfCo+YmLu1Qh_Qf-XN9hXLKsww@mail.gmail.com> <20190919202036.GA48975@kduck.mit.edu>
In-Reply-To: <20190919202036.GA48975@kduck.mit.edu>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Wed, 25 Sep 2019 13:56:46 +0530
Message-ID: <CAB75xn69TNsthD=KpmLFzekZ7PjOnGaj5G_RvpqucKk06XGAOw@mail.gmail.com>
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pce-stateful-pce-auto-bandwidth@ietf.org,  Adrian Farrel <adrian@olddog.co.uk>, pce-chairs <pce-chairs@ietf.org>, pce@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/8f9hGu3y8OKGuGkKD22ttgedR3k>
Subject: Re: [Pce] Benjamin Kaduk's Discuss on draft-ietf-pce-stateful-pce-auto-bandwidth-11: (with DISCUSS and COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Sep 2019 08:27:28 -0000

Hi Ben,

Thanks for the discussion.

Snipping to open points..

> > >
> > > As a general note, I'm not sure the phrase "calculated bandwidth to be
> > > adjusted" is a great fit for how it's currently being used.
> > > Specifically, the "calculation" in question seems to just be taking the
> > > maximum of a sliding window of per-timeslice average bandwidth values,
> > > and this seems like a sufficiently small amount of computation that I'd
> > > be comfortable describing it as a "measurement", for "measured bandwidth
> > > as input to path calculation".  That is, this doesn't seem like it comes
> > > close to the amount of computation involved in actually computing paths,
> > > so I keep misreading what information is being sent where.
> > >
> >
> > In an earlier version there was a feature where the PCC could report
> > the measured value at each sample interval (it moved to another
> > document). IMHO for the clarity in the WG, it is still better to
> > differentiate between the raw measured value (telemetry) and the value
> > that is currently reported which is marked as "calculated".
>
> Ah, in that context it makes more sense to do it this way.  Perhaps an
> informative reference to the other document/usage and note about the
> terminology would help, though?
>

I have added - "Another approach would be to send the measured values
itself to the PCE, which is considered out of scope for this
document.". In terminology I highlighted 'measured' and 'calculated'
in the existing terms.

> > > Section 1
> > >
> > >    Over time, based on the varying traffic pattern, an LSP established
> > >    with a certain bandwidth may require to adjust the bandwidth reserved
> > >    in the network dynamically.  The head-end Label Switch Router (LSR)
> > >    monitors the actual bandwidth demand of the established LSP and
> > >    periodically computes new bandwidth.  The head-end LSR adjusts the
> > >    bandwidth reservation of the LSP based on the computed bandwidth
> > >    automatically.  This feature is commonly referred to as Auto-
> > >    Bandwidth.  The Auto-Bandwidth feature is described in detail in
> > >    Section 4 of this document.
> > >
> > > >From just this text, I can't tell if this is describing the mechanisms of
> > > this document or an existing Auto-Bandwidth feature that is related to
> > > the mechanisms of this document.
> > >
> >
> > The auto-bandwidth feature without PCE exists, where the ingress does
> > the measurement as well as path computation. This feature has been
> > implemented long back but was not part of any standard because it was
> > a local implementation at the ingress node and no protocol changes was
> > required. With the PCE things changed and here we are...
>
> Ah, I see.  Maybe "This feature, when available in the head-end LSR
> implementation, is common referred to as [...]", then?
>

Updated.


> > > Section 2.3
> > >
> > > Are we assuming any relationship between the Up-Adjustment-Threshold and
> > > the Overflow-Threshold?
> > >
> >
> > Yes, as mentioned here while describing Overflow-Threshold -
> >
> >       The LSP bandwidth is adjusted to the
> >       current bandwidth demand bypassing the Up-Adjustment-Interval if
> >       the overflow condition is met consecutively for the Overflow-
> >       Count.
>
> I was thinking more along the lines of if the Overflow-Threshold value was
> going to be a larger number than the Up-Adjustment-Threshold.
>

Yes, I have added this in terminology section.
Also added a note for operator to take care while setting this in section 6.1.

I prefer to keep this generic as there are multiple combinations of
formats to deal with.

> >
> > >       traffic demand.  If the percentage or absolute difference between
> > >       the current MaxAvgBw and the current bandwidth reservation of the
> > >       LSP is greater than or equal to the threshold value, the overflow
> > >       condition is set to be met.  The LSP bandwidth is adjusted to the
> > >
> > > nit: I think s/set to be met/said to be met/ ?  (this appears twice)
> > >
> >
> > Ack
> >
> > >    Minimum-Threshold:  The increase or decrease of the LSP bandwidth
> > >       should be at least or above the minimum-threshold represented as
> > >       an absolute bandwidth value before the bandwidth adjustment for
> > >       the LSP is made.  This threshold can be seen as a suppression
> > >       threshold that is used along with a percentage threshold to avoid
> > >       unnecessary auto-bandwidth adjustments and re-signaling of the LSP
> > >       at low bandwidth values.
> > >
> > > I can't tell from this text if this threshold is a (LSP) bandwidth
> > > value/measurement or a bandwidth offset between configured and measured
> > > values.  (The subsequent protocol element definitions are more clear
> > > that it's the latter.)
> > >
> >
> > It is latter. Do you have a suggested change, I am not sure what change to make.
>
> How about:
>
>    Minimum-Threshold:  When percentage-based thresholds are in use, they
>       are accompanied by this minimum threshold, which is used to enforce
>       that the magnitude of deviation of calculated LSP bandwidth from the
>       reserved bandwidth exceeds a specific non-percentage-based criterion
>       before any adjustments are made.  This serves to suppress unnecessary
>       auto-bandwidth adjustments and re-signaling of the LSP at low
>       bandwidth values.
>
>

Thanks for the text. Updated with minor changes.

> > > Section 4.2
> > >
> > >    When the Auto-Bandwidth feature is enabled, the measured traffic rate
> > >    is periodically sampled at each Sample-Interval (which can be
> > >    configured by an operator and the default value as 5 minutes) by the
> > >    PCC, when the PCC is the head-end node of the LSP.  The traffic rate
> > >
> > > Do we cover what happens in the case when the PCC is not the head-end
> > > node of the LSP?
> > >
> >
> > No.
>
> Should we document that somewhere?
>

Added.

Diff: https://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=draft-ietf-pce-stateful-pce-auto-bandwidth-11&url2=https://raw.githubusercontent.com/dhruvdhody/ietf/master/draft-ietf-pce-stateful-pce-auto-bandwidth-12.txt

Working Copy: https://raw.githubusercontent.com/dhruvdhody/ietf/master/draft-ietf-pce-stateful-pce-auto-bandwidth-12.txt

Thanks!
Dhruv


From nobody Wed Sep 25 01:28:22 2019
Return-Path: <dhruv.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2731120122; Wed, 25 Sep 2019 01:28:14 -0700 (PDT)
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, FREEMAIL_FROM=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=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 XBR1-F-Lqa2g; Wed, 25 Sep 2019 01:28:13 -0700 (PDT)
Received: from mail-io1-xd29.google.com (mail-io1-xd29.google.com [IPv6:2607:f8b0:4864:20::d29]) (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 06A5112011B; Wed, 25 Sep 2019 01:28:13 -0700 (PDT)
Received: by mail-io1-xd29.google.com with SMTP id h144so11574141iof.7; Wed, 25 Sep 2019 01:28:12 -0700 (PDT)
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:content-transfer-encoding; bh=M/0G22efe3zHuHuNaQnQMZOMdiTkHPE1l/XaLPOQ3E0=; b=YE1RlQHrt1rWdkTiOyA7rwG8m3hcpKuoRuXeQRRiuOaqzvul2r74A/MwW6WUbIkaUF 4KHfe2/ejcmOt8iJiz1NzQn+bS14IniBDcDfKxvy+jR8bD1mQ2aCIPMD4NvAXln5RCA5 OwE0fyuD7CQ8pzprBmMdhEXxEhdRQNPCkr3MouaKjpTOKiRTl8XwD6VcEa6DzwSC0JUc 5PdfD6IPrfTfKlZUD8JVDQTK0YckiNhS00lRJNA4bGuFOWL4Sv3bR35gJFkFK9ZIwsCG QdUCKycVaAPxUlAzbXjbXD20ba481mog4Oj9AAdnC7zq7wCS582XsMz2DqlA0Hyolv+b OqPQ==
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:content-transfer-encoding; bh=M/0G22efe3zHuHuNaQnQMZOMdiTkHPE1l/XaLPOQ3E0=; b=uGvMDAqHrTlbZszFCoMiF3s7s9zWYuZUuM64TjoQngRARd2gllIpiSt664iLro0h1p 5nNGbQ0t/bojUejet2QJPoo+S++MIaXSNQa6Jo89dckGiaA/ybdgzlqjaieF0B4kRp9D 0nkpK3a+LBY6JhodR4PsxVrPYhCqOsBhZ6wGJ4NgbtMnwmZzOIz/xzCs7flh3ZlM0Ech MJJMlXdyKCtS1Sv4DoT+b9/pHgTgwLERcNfA/tW2jFCjzw4K4+k8HfO/ZkJTbyowchdT lnpy6xvRdmKJeaRjGmmnEHki3RwO7zayW9vM/0NeRw4evkTjo1JXp69HJcuwdx2NM7fN pgmA==
X-Gm-Message-State: APjAAAWaDYW7OLI/XjH5bSn7ESS0mGMehPSDQMSXWlIFCypIFddxdZYO 1k9/JP2vE66c8g3V6kuxVueyyvwhEwAl7tHULLg=
X-Google-Smtp-Source: APXvYqwuRed1knRDjlfvcGLepPoeTiB3Xdq1FAIN3KoI5u/JMt2bOOtPaX0mMMYeBPSLMNcnGvg/hBjsfPvnSJPZ1+8=
X-Received: by 2002:a5d:9c4c:: with SMTP id 12mr8728236iof.276.1569400092202;  Wed, 25 Sep 2019 01:28:12 -0700 (PDT)
MIME-Version: 1.0
References: <156882833650.4553.15366878761681665492.idtracker@ietfa.amsl.com>
In-Reply-To: <156882833650.4553.15366878761681665492.idtracker@ietfa.amsl.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Wed, 25 Sep 2019 13:57:36 +0530
Message-ID: <CAB75xn79HoiABmaNQxyv7SrHo5rkvzSrkM1yTMLGtckuJiAwQQ@mail.gmail.com>
To: Roman Danyliw <rdd@cert.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pce-stateful-pce-auto-bandwidth@ietf.org,  Adrian Farrel <adrian@olddog.co.uk>, pce-chairs <pce-chairs@ietf.org>, pce@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/rlljrad5oxY6MjuhtZsfU5efgFo>
Subject: Re: [Pce] Roman Danyliw's No Objection on draft-ietf-pce-stateful-pce-auto-bandwidth-11: (with COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Sep 2019 08:28:15 -0000

Hi Roman,

On Wed, Sep 18, 2019 at 11:08 PM Roman Danyliw via Datatracker
<noreply@ietf.org> wrote:
>
> Roman Danyliw has entered the following ballot position for
> draft-ietf-pce-stateful-pce-auto-bandwidth-11: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-pce-auto-bandwid=
th/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> ** I support Ben Kaduk=E2=80=99s DISCUSS position on the need for clarity=
 in the
> definition of Overflow-Count and Overflow-Threshold
>

Updated.

> ** Section 5.2.x.  Error handling:
> -- A number of the sub-TLVs define ranges smaller than would be possible =
given
> the number of bit (e.g., 1..604800 in a 32-bit field; 1.100), how would a=
n
> error be signaled for values used outside that range?
>
> -- For values that are [IEEE.754.1985]), how should negative value be pro=
cessed?
>

I have added "In case of an invalid value, the Sub-TLV MUST be ignored
and the previous value is maintained." in sub-TLV to handle it for all
such cases. Also added a sentence in section 6.4 to log this event.

> ** Nits:
> -- Section 1.  Typo. s/a Active stateful/an Active stateful/
>
> -- Section 5.2.2.2.  For consistency with the other sections s/1 to 60480=
0/1 to
> 604800 (7 days)/
>
> -- Section 6.6.  Typo. s/signalling/signaling/
>
>

All nits are fixed.

Thank you for your review!

Dhruv


From nobody Wed Sep 25 09:21:04 2019
Return-Path: <julien.meuric@orange.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5738120817 for <pce@ietfa.amsl.com>; Wed, 25 Sep 2019 09:20:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.29
X-Spam-Level: 
X-Spam-Status: No, score=-0.29 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FORGED_MUA_MOZILLA=2.309, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zzR5V7Ezey5g for <pce@ietfa.amsl.com>; Wed, 25 Sep 2019 09:20:45 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A714120251 for <pce@ietf.org>; Wed, 25 Sep 2019 09:20:45 -0700 (PDT)
Received: from opfedar02.francetelecom.fr (unknown [xx.xx.xx.4]) by opfedar24.francetelecom.fr (ESMTP service) with ESMTP id 46djwC5Fgwz5wCK for <pce@ietf.org>; Wed, 25 Sep 2019 18:20:43 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.92]) by opfedar02.francetelecom.fr (ESMTP service) with ESMTP id 46djwC4WYNzCqkM for <pce@ietf.org>; Wed, 25 Sep 2019 18:20:43 +0200 (CEST)
Received: from [10.192.150.227] (10.114.13.247) by OPEXCAUBM34.corporate.adroot.infra.ftgroup (10.114.13.92) with Microsoft SMTP Server (TLS) id 14.3.468.0; Wed, 25 Sep 2019 18:20:43 +0200
From: <julien.meuric@orange.com>
Organization: Orange
To: "pce@ietf.org" <pce@ietf.org>
Message-ID: <29713_1569428443_5D8B93DB_29713_96_1_6698a3d9-4ace-57fd-3b7c-7be23f135631@orange.com>
Date: Wed, 25 Sep 2019 18:20:42 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-Originating-IP: [10.114.13.247]
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/kpZqPAUAauFFdhzrh-NHL48uVsQ>
Subject: [Pce] Adoption of draft-li-pce-sr-path-segment?
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Sep 2019 16:20:57 -0000

Hi PCE WG,

In our adoption poll queue, draft-li-pce-sr-path-segment has been there
for a little while, after it was discussed face to face. We would now
like you to voice your opinion on the list: do you think this I-D can be
the foundation for a PCE WG's work item?

Please send your feedback to the PCE mailing list, including any comment
you would like to share, especially if you think the WG should not adopt
it. This poll will end on October 9.

Thanks,

Dhruv & Julien


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu 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 ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information 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 delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.


From nobody Wed Sep 25 10:49:43 2019
Return-Path: <hari@netflix.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 745A1120839 for <pce@ietfa.amsl.com>; Wed, 25 Sep 2019 10:49:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIMWL_WL_HIGH=-0.001, 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 (1024-bit key) header.d=netflix.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 nCZOr6EEhxg7 for <pce@ietfa.amsl.com>; Wed, 25 Sep 2019 10:49:39 -0700 (PDT)
Received: from mail-vk1-xa33.google.com (mail-vk1-xa33.google.com [IPv6:2607:f8b0:4864:20::a33]) (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 9723F120831 for <pce@ietf.org>; Wed, 25 Sep 2019 10:49:39 -0700 (PDT)
Received: by mail-vk1-xa33.google.com with SMTP id w3so814558vkm.3 for <pce@ietf.org>; Wed, 25 Sep 2019 10:49:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netflix.com; s=google;  h=mime-version:from:date:message-id:subject:to:cc; bh=9kIT6P8dyndx3AJA/fqcnYDUWN5b8uRCV/jt3s8JnH0=; b=Ab9bV3u4TKBEfzXaMCg96vQgSTOspYJJJBjofb8UepFX2A8LIqUJ809EPjyz6TrUby hHdDxrXtoSVzhRGwv0S9uoAFdNLD16MHFzdAE7jeG4kp2huUvjaBux29cR1upbt0lxXq v+jzBr5o2p8usl4OTiqfu2oMHTULY9R/5HxHs=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=9kIT6P8dyndx3AJA/fqcnYDUWN5b8uRCV/jt3s8JnH0=; b=uUQCjTL6hJ2wQO0i4AvR9Tm4Fw8z0O7i89KgE7aerXwSZ0oCXNmXxdGjrHYRpaP85J 9cgXKPgQk92ElG1gnZTISXwBkQd2ROojEISL3Yk0KBS5N9xcbUKokYPKujj2zOSmZRGQ +8mnAzNykCtnGl6nJFERWAoRHcHPtrZlORfAnAq8j3Fxd4lzFVwR2X8/C7Pc5ujkNYUm wHxthKORdCLa8ht1bu588XRHP1/i1hJ9Aqfx3qJaWdv6FfKvstJ7IRrxjQdmgaUIABbo /MqDwzLViKE6V00EDiThLkXQlUOvdqMT23Qfg9hzi8Gcw/OGQmAsBmwcgvDcULURV3lz Sqtw==
X-Gm-Message-State: APjAAAVrErrz1xsDuYNFr5ns8jaeAQylg2ygaq66e0UBcJj1TjZOSm46 luomySndsMgLx0TfbUCe8S3o4DvUAQ6euFzanQ/0Zw==
X-Google-Smtp-Source: APXvYqwUzx2dVpk1hd9cVEiCbT1wd7shweSBW0Gl15Q+yYqPjVRWsWmIc++9NZzXunzotNJj2MKIwyGUQ/BO3wxl+hw=
X-Received: by 2002:a1f:38c6:: with SMTP id f189mr3199977vka.32.1569433778347;  Wed, 25 Sep 2019 10:49:38 -0700 (PDT)
MIME-Version: 1.0
From: Hariharan Ananthakrishnan <hari@netflix.com>
Date: Wed, 25 Sep 2019 10:49:28 -0700
Message-ID: <CAL70W4q8DctbRNTFMWzKELNZORgL5OuStFJgFOx1tw9tq3+jGA@mail.gmail.com>
To: chengli13@huawei.com, mach.chen@huawei.com, chengweiqiang@chinamobile.com,  jie.dong@huawei.com, lizhenbin@huawei.com, rgandhi@cisco.com,  xiong.quan@zte.com.cn
Cc: pce@ietf.org
Content-Type: multipart/alternative; boundary="000000000000db9c080593644656"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/o_9yv75Lk2a-nISTlyrFM-xGxdI>
Subject: [Pce] IPR Poll on draft-li-pce-sr-path-segment-08
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Sep 2019 17:49:42 -0000

--000000000000db9c080593644656
Content-Type: text/plain; charset="UTF-8"

Hi Authors,

In preparation for Working Group last call on this draft, I'd like all
authors and contributors to confirm on the list that they are in compliance
with IETF IPR rules.

Please respond (copying the mailing list) to say one of:

I am not aware of any IPR applicable to this draft that should be disclosed
in accordance with IETF IPR rules.

I am aware of IPR applicable to this draft, and it has already been
disclosed to the IETF.

I am aware of IPR applicable to this draft, but that has not yet been
disclosed to the IETF. I will work to ensure that it will be disclosed in a
timely manner.

Thanks,
- Hari

--000000000000db9c080593644656
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:verdana,=
sans-serif;font-size:small"><pre style=3D"white-space:pre-wrap;box-sizing:b=
order-box;margin-top:0px;margin-bottom:1rem;overflow:auto;color:rgb(33,37,4=
1);word-break:normal;padding:0px"><font face=3D"verdana, sans-serif">Hi Aut=
hors,

In preparation for Working Group last call on this draft, I&#39;d like all
authors and contributors to confirm on the list that they are in compliance
with IETF IPR rules.

Please respond (copying the mailing list) to say one of:

I am not aware of any IPR applicable to this draft that should be disclosed
in accordance with IETF IPR rules.

I am aware of IPR applicable to this draft, and it has already been
disclosed to the IETF.

I am aware of IPR applicable to this draft, but that has not yet been
disclosed to the IETF. I will work to ensure that it will be disclosed in a
timely manner.

Thanks,
- Hari</font></pre></div></div>

--000000000000db9c080593644656--


From nobody Wed Sep 25 14:17:58 2019
Return-Path: <kaduk@mit.edu>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E80112022C; Wed, 25 Sep 2019 14:17:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rknOfY7yvbYd; Wed, 25 Sep 2019 14:17:53 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 459F71200CC; Wed, 25 Sep 2019 14:17:53 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x8PLHj0g016995 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 25 Sep 2019 17:17:48 -0400
Date: Wed, 25 Sep 2019 14:17:45 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Dhruv Dhody <dhruv.ietf@gmail.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pce-stateful-path-protection@ietf.org, Julien Meuric <julien.meuric@orange.com>, pce-chairs <pce-chairs@ietf.org>, pce@ietf.org
Message-ID: <20190925211745.GN6424@kduck.mit.edu>
References: <156876388231.17411.6094234033866939217.idtracker@ietfa.amsl.com> <CAB75xn4L2RE0vo44bt332kUL7Nh=LryKpJ3BSHRRnHggz8v3vQ@mail.gmail.com> <20190919210236.GB48975@kduck.mit.edu> <CAB75xn553Ft1i1zDnYqDgSZZf57eQF6Ej1FOpbqSWAuqgVPOxA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAB75xn553Ft1i1zDnYqDgSZZf57eQF6Ej1FOpbqSWAuqgVPOxA@mail.gmail.com>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/wK-kCVsg3FgZrzUkSHOmxDTt-4E>
Subject: Re: [Pce] Benjamin Kaduk's Discuss on draft-ietf-pce-stateful-path-protection-10: (with DISCUSS and COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Sep 2019 21:17:56 -0000

On Tue, Sep 24, 2019 at 11:38:13AM +0530, Dhruv Dhody wrote:
> Hi Ben,
> 
> Apologies for the delay. I am replying this email where we tackle
> points that needed some more discussion.
> 
> On Fri, Sep 20, 2019 at 2:32 AM Benjamin Kaduk <kaduk@mit.edu> wrote:
> >
> > Hi Dhruv,
> >
> > On Wed, Sep 18, 2019 at 11:45:23AM +0530, Dhruv Dhody wrote:
> > > Hi Ben,
> > >
> > > Thanks for your review, let me start the discussion and the authors
> > > can interject as needed.
> >
> > Thanks; it's a great start.
> >
> > > On Wed, Sep 18, 2019 at 5:14 AM Benjamin Kaduk via Datatracker
> > > <noreply@ietf.org> wrote:
> > > >
> > > > Benjamin Kaduk has entered the following ballot position for
> > > > draft-ietf-pce-stateful-path-protection-10: Discuss
> > > >
> > > > When responding, please keep the subject line intact and reply to all
> > > > email addresses included in the To and CC lines. (Feel free to cut this
> > > > introductory paragraph, however.)
> > > >
> > > >
> > > > Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> > > > for more information about IESG DISCUSS and COMMENT positions.
> > > >
> > > >
> > > > The document, along with other ballot positions, can be found here:
> > > > https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-path-protection/
> > > >
> > > >
> > > >
> > > > ----------------------------------------------------------------------
> > > > DISCUSS:
> > > > ----------------------------------------------------------------------
> > > >
> > > > (1) draft-ietf-pce-association-group notes that "PCEP extensions that define
> > > > a new association type should clarify the relationship between the SVEC
> > > > object and the association type, if any".  Where do we do so for the
> > > > path protection association type?
> > > >
> > >
> > > This is discussed in
> > > https://tools.ietf.org/html/draft-ietf-pce-association-diversity-10#section-5.3,
> > > where it is more relevant. This draft includes the relationship with
> > > diversity association in Section 5.
> >
> > A naive reading of the linked section would be that it applies only to the
> > "Disjointness Association Type" defined in that document.  I'm not in a
> > position to claim that the reasoning in that document does not apply to
> > this one, but I think we should make a more clear link between the Path
> > Protection ASsociation Type and the discussion in that document.
> >
> 
> The direct relationship is between the 'Disjointness Association Type'
> and SVEC. But it is natural to include both Protection association and
> disjoint association together. If SVEC is also present the
> relationship is as per the Section 5.3 of
> [I-D.ietf-pce-association-diversity]. Suppose if only protection
> association is present and SVEC object, there is no direct
> relationship and both object would be processed.
> 
> I suggest we add this text to make sure reader is aware of SVEC - "The
> relationship between the Synchronization VECtor (SVEC) object and the
> Disjointness Association is described in section 5.3 of
> [I-D.ietf-pce-association-diversity]."

Thanks!

> 
> > > > (2) Section 3.2 says:
> > > >
> > > >       Protection Type (PT): 6 bits - This field is as defined in
> > > >       Section 14.1 of [RFC4872] to indicate the LSP protection type in
> > > >       use.
> > > >
> > > > There doesn't seem to be a registry created by RFC 4872 to track these
> > > > PT values, so I assume that the way to allocate a new value is
> > > > "standards-track RFC that Updates: RFC 4872".  Is that also the way to
> > > > allocate new PT values for PPAG usage?  How would someone updating RFC
> > > > 4872 to allocate a new type know to consider/document whether it applies
> > > > for PPAG usage?
> > > >
> > >
> > > That's true. Maybe we can add this text - "Any type already defined or
> > > that could be defined in the future for use in the RSVP-TE PROTECTION
> > > object is acceptable in this TLV unless explicitly stated otherwise."
> >
> > To be honest, that's probably good enough in practice, since it seems
> > somewhat unlikely that the last bit is ever going to get allocated (though,
> > I guess technically the field could be converted to an integer instead of
> > flags).  I do still have to wonder how the reader would know *where* it
> > would be stated otherwise, and how the author of a document defining a new
> > type would know to consider our use case as well as the RFC 4872 use case.
> >
> 
> I guess such an update would happen in TEAS; and historically PCE and
> TEAS work very closely, as well as share the same AD. I think we are
> quite safe here.
> 
> In case you were wondering why flags - we chose PT as flags as per RFC
> 4872 where this is called "LSP (Protection Type) Flags".
> 
> > > > (3) In Section 4.3:
> > > >
> > > >    A PCE can create/update working and protection LSPs independently.
> > > >    As specified in [I-D.ietf-pce-association-group], Association Groups
> > > >    can be created by both the PCE and the PCC.  Further, a PCE can
> > > >
> > > > The requirement that source, destination, and tunnel ID of all LSPs
> > > > within a PPAG MUST be the same is new to this document, so I think we
> > > > need to specify error handling for when attempts to update LSPs
> > > > independently would violate that invariant (presumably in Section 4.5).
> > > >
> > >
> > > In the existing error case in Section 4.5 we could make it "add or update".
> >
> > Wording it right might be a little finicky, but that's fine in general.
> >
> > > > (4) In Section 6.3:
> > > >
> > > >                                       IANA is requested to allocate new
> > > >    error values within the "PCEP-ERROR Object Error Types and Values"
> > > >    sub-registry of the PCEP Numbers registry, as follows:
> > > >
> > > > The following table only lists Error-values.  What Error-type(s) should
> > > > they be associated with?
> > > >
> > >
> > > It is mentioned in the text, but worth making it explicit in the table as well.
> > >
> 
> Lets update the table as well. Request authors to update.

Thanks!

> > > > (5) We don't say which objects the PPAG TLV can appear in.  (Section 3.2
> > > > says "[t]he Path Protection Association TLV is an optional TLV for use
> > > > with the Path Protection Association Type", but it's hard to interpret
> > > > that as meaning "for use [only] with the ASSOCIATION object defined in
> > > > draft-ietf-pce-association-group", especially since there is a "path
> > > > protection association type" already (and it's a codepoint in the
> > > > "ASSOCIATION Type Field" registry).
> > > >
> > >
> > > We can update to - "The Path Protection Association TLV is an optional
> > > TLV for use in the ASSOCIATION Object with the Path Protection
> > > Association Type."
> >
> > Thanks!
> >
> > > > (6) I'm not sure if a change to the document is needed here, but perhaps
> > > > some discussion is in order: we say that a given LSP can belong to more
> > > > than one PPAG, but only allow one PPAG TLV per [some context that
> > > > remains unclear; see (5)].  I don't have a good handle for whether these
> > > > two requirements are potentially in conflict: that is, whether a single
> > > > PPAG TLV would have to specify the flags that apply for both PPAGs that
> > > > a given LSP is a member of, or if the containing objects serve to scope
> > > > the PPAG TLV flags' interpretation.
> > > >
> > >
> > > When a given LSP belong to more than one PPAG, we expect to have
> > > multiple ASSOCIATION Object for each PPAG with each of them having a
> > > single PPAG TLV.
> >
> > Sounds good, and quite natural given (5).
> >
> > > > (7) Do the Protection Type fields of the PPAG TLV in the various LSPs
> > > > that are members of the same PPAG need to match, in the same way that
> > > > the source/destination/tunnel-ID do?
> > > >
> > >
> > > Yes. Authors should make that explicit.
> >
> 
> Sure. Request authors to add.

Thanks!

> > Thanks
> >
> > > >
> > > > ----------------------------------------------------------------------
> > > > COMMENT:
> > > > ----------------------------------------------------------------------
> > > >
> > > > Section 1
> > > >
> > > >    This document specifies a stateful PCEP extension to associate two or
> > > >    more LSPs for the purpose of setting up path protection.  The
> > > >    proposed extension covers the following scenarios:
> > > >
> > > > nit: after publication, it doesn't really seem like a *proposed*
> > > > extension anymore.
> > > >
> > > > Section 3.1
> > > >
> > > >    LSPs are not associated by listing the other LSPs with which they
> > > >    interact, but rather by making them belong to an association group
> > > >    referred to as "Path Protection Association Group" (PPAG) in this
> > > >    document.  [...]
> > > >
> > > > The first 2/3 of this sentence is a (true) generic statement about all
> > > > association groups, which exist outside of this document in a generic
> > > > fashion.  I strongly suggest rewording this to make clear that the PPAG
> > > > is the specific association (group) type used for this document's
> > > > functionality but that other association groups are possible.  The
> > > > current wording implies that the PPAG is the only association possible,
> > > > and it is just given a special name for this document's purposes.
> > > >
> > > >    [I-D.ietf-pce-association-group] specifies the mechanism for the
> > > >    capability advertisement of the Association types supported by a PCEP
> > > >    speaker by defining a ASSOC-Type-List TLV to be carried within an
> > > >    OPEN object.  This capability exchange for the Association type
> > > >    described in this document (i.e.  Path Protection Association Type)
> > > >    MAY be done before using the policy association, i.e., the PCEP
> > > >    speaker MAY include the Path Protection Association Type (TBD1) in
> > > >    the ASSOC-Type-List TLV before using the PPAG in the PCEP messages.
> > > >
> > > > Why is this only MAY and not MUST?
> > > >
> > >
> > > In [I-D.ietf-pce-association-group] we explicitly did not mandate the
> > > capability exchange for all association types and let each type decide
> > > for itself. This association type fits into where the capability
> > > exchange is optional. When the capability exchange was added in
> > > [I-D.ietf-pce-association-group], there was a desire from the WG to
> > > keep it optional for already defined/implemented protection
> > > association type. Also this is a basic feature in path computation and
> > > it is expected to be supported universally. In a corner case there is
> > > an error handling for unknown/unsupported association-type to take
> > > care of it.
> >
> > Okay, thanks for giving me the backstory.
> >
> > > >    This Association type is dynamic in nature and created by the PCC or
> > > >
> > > > nit: is it the type that is dynamic or the associations of that type?
> > > >
> > >
> > > It is the type. [I-D.ietf-pce-association-group] has dynamic or
> > > operator-configured association, this one is dynamic.
> >
> > Ah, of course, I had forgotten about that division of configuration.
> >
> > > >       Protecting (P): 1 bit - This bit is as defined in Section 14.1 of
> > > >       [RFC4872] to indicate if the LSP is working or protection LSP.
> > > >
> > > >       Secondary (S): 1 bit - This bit is as defined in Section 14.1 of
> > > >       [RFC4872] to indicate if the LSP is primary or secondary LSP.  The
> > > >       S flag is ignored if the P flag is not set.
> > > >
> > > > Just to check my understanding (no change expected to result): if P is
> > > > zero, the LSP is working, and thus we know that it's primary since it's
> > > > actively carrying traffic?
> > > >
> > >
> > > Yes, Working LSPs are always primary.
> > >
> > >
> > > > Section 3.2
> > > >
> > > > nit(?) The section heading does not match the name of the TLV requested
> > > > in the IANA considerations, nor do we mention here that "PPAG TLV" is
> > > > synonymous with it.
> > > >
> > > >    If the TLV is missing, it is considered that the LSP is the working
> > > >    LSP (i.e. as if P bit is unset).
> > > >
> > > > Is this conditional on the LSP being part of a PPAG, or does it hold
> > > > generically as well?
> > > >
> > >
> > > IMHO when part of a PPAG i.e. association object but no TLV.
> >
> > It may be worth making the text explicit about it.
> >
> > > > Section 4.5
> > > >
> > > >    As per the processing rules specified in section 5.4 of
> > > >    [I-D.ietf-pce-association-group], if a PCEP speaker does not support
> > > >
> > > > There is no Section 5.4 in draft-ietf-pce-association-group-10;
> > > > presumably this was supposed to be Section 6.4?
> > > >
> > > >    A given LSP MAY belong to more than one PPAG.  If there is a conflict
> > > >
> > > > While I'm not arguing to remove this option, I'm also a bit confused at
> > > > how useful having a single LSP be in multiple PPAGs woud be, given the
> > > > need for source/destination/tunnel-ID to match.
> > > >
> > >
> > > One working LSP could have multiple protection LSPs with each
> > > belonging to a different association.
> > >
> > > >    When the protection type is set to 1+1 or 1:N with N=1, there MUST be
> > > >    only one working LSP and one protection LSP within a PPAG.  If a PCEP
> > > >    speaker attempts to add another working/protection LSP, the PCEP peer
> > > >    MUST send PCErr with Error-Type 26 (Association Error)
> > > >    [I-D.ietf-pce-association-group] and Error-Value TBD4 (Attempt to add
> > > >    another working/protection LSP for Path Protection Association).
> > > >
> > > > This seems to prevent a scenario where there's a need to change the
> > > > protection LSP and a desire to do so without removing the protected
> > > > nature of the working LSP.  Unless it's presumed that this could always
> > > > be done by updating the protection LSP and it would never be necessary
> > > > to create a new one?  (Similarly for 1:N, though maybe less severe.)
> > > >
> > >
> > > One can remove the protection LSP and keep the association intact. The
> > > error will not be triggered.
> > > Also, PCEP messages are per LSP, when the first LSP is reported with
> > > association, it is bound to be the only LSP in the association.
> > > So the error in this section are focused only when one adds "another".
> >
> > I don't think that the points you cover above are what I was concerned
> > about -- I was thinking more along the lines of a "make-before-break"
> > scheme for changing what LSP is the protection LSP for a given working LSP.
> > Maybe given the timescales involved it's not an issue in practice, though.
> >
> 
> Maybe worth adding some text here to be safe - "During the
> make-before-break (MBB) procedure, two paths will briefly coexist. The
> error handling related to number of LSPs allowed in a PPAG MUST NOT be
> applied during MBB."
> 
> I hope this message clears all the remaining points.

I think it does; thanks again.

-Ben


From nobody Wed Sep 25 16:26:08 2019
Return-Path: <kaduk@mit.edu>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C270F12013C; Wed, 25 Sep 2019 16:25:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oPR15u6NsiqS; Wed, 25 Sep 2019 16:25:56 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5208D12002E; Wed, 25 Sep 2019 16:25:56 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x8PNPnJZ022683 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 25 Sep 2019 19:25:51 -0400
Date: Wed, 25 Sep 2019 16:25:48 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Dhruv Dhody <dhruv.ietf@gmail.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pce-stateful-hpce@ietf.org, Adrian Farrel <adrian@olddog.co.uk>, pce-chairs <pce-chairs@ietf.org>, pce@ietf.org
Message-ID: <20190925232548.GQ6424@kduck.mit.edu>
References: <156884459034.4565.10696493114905134845.idtracker@ietfa.amsl.com> <CAB75xn5wp6EvhCVExn9sz4ipbxT+1GpPbW_fX8GOea6zh=tBpw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAB75xn5wp6EvhCVExn9sz4ipbxT+1GpPbW_fX8GOea6zh=tBpw@mail.gmail.com>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/1-Y0JRAfrkSDsRELoCemNimmKRA>
Subject: Re: [Pce] Benjamin Kaduk's Discuss on draft-ietf-pce-stateful-hpce-13: (with DISCUSS and COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Sep 2019 23:26:00 -0000

Hi Dhruv,

On Tue, Sep 24, 2019 at 07:36:43PM +0530, Dhruv Dhody wrote:
> Hi Ben,
> 
> Thanks for your review.
> 
> On Thu, Sep 19, 2019 at 3:39 AM Benjamin Kaduk via Datatracker
> <noreply@ietf.org> wrote:
> >
> > Benjamin Kaduk has entered the following ballot position for
> > draft-ietf-pce-stateful-hpce-13: Discuss
> >
> > When responding, please keep the subject line intact and reply to all
> > email addresses included in the To and CC lines. (Feel free to cut this
> > introductory paragraph, however.)
> >
> >
> > Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> > for more information about IESG DISCUSS and COMMENT positions.
> >
> >
> > The document, along with other ballot positions, can be found here:
> > https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-hpce/
> >
> >
> >
> > ----------------------------------------------------------------------
> > DISCUSS:
> > ----------------------------------------------------------------------
> >
> > I think this should be pretty easy to resolve, though I'm not sure what
> > the right way to do so it.
> >
> > Section 3 says:
> >
> >    [I-D.ietf-pce-hierarchy-extensions] defines the H-PCE Capability TLV
> >    that is used in the Open message to advertise the H-PCE capability.
> >    [RFC8231] defines the Stateful PCE Capability TLV used in the Open
> >    message to indicate stateful support.  The presence of both TLVs in
> >    an Open message indicates the support for stateful H-PCE operations
> >    as described in this document.
> >
> > There is no normative reference relationship (in either direction)
> > between draft-ietf-pce-hierarchy-extension and this document; I think
> > that the use of the capability TLV to imply both sets of functionality
> > implies some sort of normative relationship; we wouldn't want version
> > skew between documents to induce breaking changes.  In particular, an
> > implementation that already supports RFC 8231 and is implementing the
> > hierarchy extensions would need to know to look at this document *and
> > implement it*, or would unknowingly be noncompliant with this document
> > and fail to interoperate with a peer that is compliant with this
> > document.
> >
> 
> How about we add normative text for this -
> 
>    [I-D.ietf-pce-hierarchy-extensions] defines the H-PCE Capability TLV
>    that is used in the Open message to advertise the H-PCE capability.
>    [RFC8231] defines the Stateful PCE Capability TLV used in the Open
>    message to indicate stateful support. To indicates the support for
>    stateful H-PCE operations described in this document, a PCEP speaker
>    MUST include both TLVs in an Open message. It is RECOMMENDED that any
>    implementation that supports stateful operations [RFC8231] and H-PCE
>    [I-D.ietf-pce-hierarchy-extensions] would also implements the
>    stateful H-PCE operations as described in this document.
> 
> This would be true in most deployments/implementations of C-PCE and
> P-PCE that are also stateful!

This does remove the problematic normative requirement on implementations
of other documents, but I'm not sure if it does what's needed for the
interactions across documents.  Specifically, what will happen if two peers
both support/advertise stateful PCE and H-PCE but only one implements
stateful HPCE?  Will there be a clean error handling at runtime and
degredation to one or the other, or will there be messy errors?  If the
latter, then I don't think we can just have a RECOMMENDED relationship.

> >
> > ----------------------------------------------------------------------
> > COMMENT:
> > ----------------------------------------------------------------------
> >
> > Abstract
> >
> >                          This information may then be considered when
> >    computing new traffic engineered LSPs, and for associated and
> >    dependent LSPs, received from Path Computation Clients (PCCs). [...]
> >
> > nit: I'm not sure how to parse this sentence.  The best thing I can come
> > up with is that "when computing new traffic engineered LSPs" and "for
> > associated [...]" are two separate cases, which each could independently
> > consider the information in question.  The first one makes sense, but
> > for the second I'm left trying to parse "this information may then be
> > considered for associated and dependent LSPs, received from PCCs", and
> > it's not really clear what considering the PCE is going to do if it just
> > sits there with information from the LSP-DB and information from PCCs (and
> > not doing anything with the information).
> >
> 
> Suggested update -
> 
>    A Stateful Path Computation Element (PCE) maintains information on
>    the current network state received from the Path Computation Clients
>    (PCCs), including: computed Label Switched Path (LSPs), reserved
>    resources within the network, and pending path computation requests.
>    This information may then be considered when computing path for a new
>    traffic-engineered LSP or for any associated/dependent LSPs. The Path
>    computation response from a PCE is helpful for the PCC to gracefully
>    establish the computed LSP.

Looks better, thanks (nit: add "the" for "when computing the path for a new")

> 
> >    The Hierarchical Path Computation Element (H-PCE) architecture,
> >    provides an architecture to allow the optimum sequence of
> >    [...]
> >
> > nit: no comma here.
> >
> > Also, three paragraphs may be pushing the bounds of an abstract in RFC
> > style.
> >
> > Section 1.1
> >
> >    path based on the domain connectivity information.  A Child PCE
> >    (C-PCE) may be responsible for a single domain or multiple domains,
> >    it is used to compute the intra-domain path based on its domain
> >    topology information.
> >
> > nit: comma splice
> >
> >    This document presents general considerations for stateful PCEs, and
> >    not Stateless PCEs, in the hierarchical PCE architecture.  In
> >    particular, the behavior changes and additions to the existing
> >    stateful PCE mechanisms (including PCE-initiated LSP setup and active
> >    PCE usage) in the context of networks using the H-PCE architecture.
> >
> > nit: should "active PCE usage" read "active stateful PCE usage"?
> >
> > Section 1.2
> >
> >    The inter-domain LSP could be set up using the end-to-end signaling
> >    as described in [RFC6805]. Additionally a per-domain stitched LSP
> >
> > Should I be reading this "could be set up using" as "this document
> > describes how to set [the LSP] up using"?
> >
> 
> Updated to -
> 
>    The end-to-end inter-domain path computation and setup is described
>    in [RFC6805].
> 
> > Section 1.2.2
> >
> >    Different signaling methods for inter-domain RSVP-TE signaling are
> >    identified in [RFC4726].  Contiguous LSPs are achieved using the
> >
> > nit: are the two "signaling"s redundant?
> >
> >    In case of a stateful P-PCE, the stateful P-PCE has to be aware of
> >    the inter-domain LSPs for it to consider them during path
> >    computation. For example, a domain diverse path from another LSP.
> >
> > nit: this last sentence is a sentence fragment.
> 
> Updated based on Barry's suggested text -
> 
>    A stateful P-PCE has to be aware of the inter-domain LSPs for it to
>    consider them during path computation. For instance when a domain
>    diverse path is required from another LSP, the P-PCE needs to be
>    aware of the LSP.
> 
> >
> >    In this document, for the Contiguous LSP, the above interactions are
> >    only between the ingress domain C-PCE and the P-PCE. The use of
> >    stateful operations for an inter-domain LSP between the
> >    transit/egress domain C-PCEs towards the P-PCE is out of scope of
> >    this document.
> >
> > nit: I suggest rewording to avoid the ambiguity of "towards" as applying
> > to the inter-domain LSP vs. the use of stateful operations.
> >
> 
> Changed to "and".
> 
> > Section 3
> >
> >    in the topology).  The P-PCE has no information about the content of
> >    the child domains.  Each child domain has at least one PCE capable of
> >
> > nit: we could potentially reword this in light of the remarks made about
> > ACTN previously.
> >
> >    computing paths across the domain.  These PCEs are known as C-PCEs
> >    and have a direct relationship with the P-PCE.  The P-PCE builds the
> >
> > It might be good to forward-reference where we talk about this
> > relationship in more detail.  (And, er, have more detail about the
> > relationship than we currently do.)
> >
> 
> This text is focused on what is described in RFC 6805, so added
> reference to that.
> 
> >    and have a direct relationship with the P-PCE.  The P-PCE builds the
> >    domain topology map either via direct configuration (allowing network
> >    policy to also be applied) or from learned information received from
> >    each C-PCE.
> >
> > Policy cannot be applied to information learned at runtime?
> >
> 
> Updated
> 
> >    LSP State Report (EC-EP):  a child stateful PCE sends an LSP state
> >       report to a Parent Stateful PCE whenever the state of a LSP
> >       changes.
> >
> > With respect to "whenever the state of a LSP changes", is there a
> > possibility of a state-change that is visible to the C-PCE but does not
> > affect anything that the P-PCE knows about?  Is the state report still
> > expected to be generated in such cases?
> >
> 
> Yes / No
> Updated text.
> 
> >    object to identify the Ingress (PCC). The PLSP-ID used in the
> >    forwarded PCRpt by the C-PCE to P-PCE is same as the original one
> >    used by the PCC.
> >
> > I couldn't quickly find an authoritative definition of what the PLSP-ID
> > is; I see some discussion in RFC 8231 for the LSP Object, but am not
> > sure if there is prior usage.
> >
> 
> It is RFC 8231, added - PLSP-ID (PCEP-specific identifier for the LSP,
> as per [RFC8231])
> 
> > Section 3.1
> >
> >    paths.  Each C-PCE computes a set of candidate path segments across
> >    its domain and sends the results to the P-PCE. The P-PCE uses this
> >    information to select path segments and concatenate them to derive
> >    the optimal end-to-end inter-domain path.  The end-to-end path is
> >    then sent to the C-PCE that received the initial path request, and
> >    this C-PCE passes the path on to the PCC that issued the original
> >    request.
> >
> > This is basically the same language as in RFC 6805, so I don't really
> > expect changing it to be the right thing to do, but I'm confused about
> > how the P-PCE is getting "candidate" segments from the C-PCEs but only
> > has to tell the head-end which path got picked.  Are the other C-PCEs
> > supposed to find out which of the candidates got used somehow?
> >
> 
> The request to other C-PCEs is "stateless" in nature and thus once
> they have computed path segments and provided the result to the P-PCE
> they loose the state and dont care which candidate was picked.

Ah, right, we did say that we are only stateful to the head-end C-PCE;
thanks for reminding me.

> > Section 3.2
> >
> >    a PCUpd message.  For LSP delegated to the P-PCE via the child PCE,
> >    the P-PCE can use the same PCUpd message to request change to the C-
> >    PCE (the Ingress domain PCE), the PCE further propagates the update
> >    request to the PCC.
> >
> > nit: comma splice
> >
> > Section 4
> >
> > I expect this to not be the case, but just to check: is there a
> > possibility for differing levels of authorization for different PCCs,
> > e.g., where PCC A is allowed to request LSPs within the domain and to
> > any other domain, but PCC B is not allowed to request LSPs to/through a
> > subset of domain peers, and PCC C is only allowed to request LSPs within
> > the local domain?
> >
> 
> Yes, we do not have different levels of authorization.
> 
> > As Roman mentions, we don't have a picture of what "full security" means
> > for child/parent communications.
> >
> 
> How about we update to "..full security (i.e. the highest security
> mechanism available for PCEP)"?

I'm not sure that we have defined an absolute ordering on PCEP security
mechanisms ... right now, I think this would mean TLS but we may not need
to prevent any future developments in the area.  I guess the right thing to
do here depends on how likely of a need there is for confidentiality
protection (and, relatedly, how widely implemented/deployed PCEPS is).

> >
> >    Thus it is RECOMMENDED to secure the PCEP session (between the P-PCE
> >    and the C-PCE) using either Transport Layer Security (TLS) [RFC8253]
> >    per the recommendations and best current practices in [RFC7525] or
> >    TCP Authentication Option (TCP-AO) [RFC5925].
> >
> > It's not entirely clear to me that we need to call out TCP-AO here.
> > Partially since, as Stephen noted in the secdir review, it doesn't seem
> > to be implemented/deployed much, but also since RFC 8231 does call out
> > that it recommends TLS for confidentiality protection, which TCP-AO does
> > not provide.  There don't seem to be specific threats enumerated there
> > that the confidentiality protects against, so I am not making a strong
> > recommendation to remove TCP-AO from this text, but I'd like to better
> > understand why it was added.
> >
> 
> We decided to keep TCP-AO as it is still a good security feature even
> though not implemented. At the same time it could be use alongside
> TLS. The updated text as per Roman's comment -
> 
>    Thus it is RECOMMENDED to secure the PCEP session (between the P-PCE
>    and the C-PCE) using Transport Layer Security (TLS) [RFC8446] (per
>    the recommendations and best current practices in [RFC7525]) and/or
>    TCP Authentication Option (TCP-AO) [RFC5925]. The guidance for
>    implementing PCEP with TLS can be found in [RFC8253].
> 
> >    In case of TLS, due care needs to be taken while exposing the
> >    parameters of the X.509 certificate, such as subjectAltName:otherName
> >    which is set to Speaker Entity Identifier [RFC8232] as per [RFC8253],
> >    to ensure uniqueness and avoid any mismatch.
> >
> > I'm not entirely sure which "mismatch" we would be concerned about.
> 
> We added this based on Stephen's comment to make sure that there is no
> issue of conflict because of peer identification parameters exposed
> via certificates. Maybe two peers using the same Speaker Entity
> Identifier in the certificate. I think the TLS establishment would
> fail but the advise still stands.
> 
> > And just to check: there aren't expected to be any privacy-like
> > considerations for exposing the speaker entity identifier to a peer in a
> > different domain, right?
> >
> 
> Yes, IMHO this is fine.
> 
> > Section 5.7
> >
> > I'm not sure how appropriate it is to fully delegate (e.g.) propagation
> > of errors to draft-ietf-pce-enhanced-errors (which is not even a
> > normative reference!) -- it seems important to describe some expectation
> > of the error handling either in this document or in a normative
> > reference thereof.
> >
> 
> Updated to -
> 
>    Apart from the basic error handling described in this document, an
>    implementation could also use the enhanced error and notification
>    mechanism for stateful H-PCE operations as per [I-D.ietf-pce-
>    enhanced-errors]. Enhanced features such as error behavior
>    propagation, notification and error criticality level, are further
>    defined in [I-D.ietf-pce-enhanced-errors].

Thanks for all the updates!

-Ben

> > Section 9.2
> >
> > I think RFCs 5925, 7525, and 8253 should be normative, and RFC 7525 can
> > be cited as BCP 195.
> >
> >
> 
> Diff: https://tools.ietf.org/rfcdiff?url1=draft-ietf-pce-stateful-hpce-13&url2=https://raw.githubusercontent.com/dhruvdhody/ietf/master/draft-ietf-pce-stateful-hpce-14.txt
> 
> Thanks!
> Dhruv


From nobody Wed Sep 25 18:49:56 2019
Return-Path: <chengli13@huawei.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26539120088 for <pce@ietfa.amsl.com>; Wed, 25 Sep 2019 18:49:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id koxdoW2l1Tmn for <pce@ietfa.amsl.com>; Wed, 25 Sep 2019 18:49:53 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B017D12001A for <pce@ietf.org>; Wed, 25 Sep 2019 18:49:52 -0700 (PDT)
Received: from lhreml701-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id A4658E0F83825960E8B7 for <pce@ietf.org>; Thu, 26 Sep 2019 02:49:50 +0100 (IST)
Received: from lhreml730-chm.china.huawei.com (10.201.108.81) by lhreml701-cah.china.huawei.com (10.201.108.42) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 26 Sep 2019 02:49:49 +0100
Received: from lhreml730-chm.china.huawei.com (10.201.108.81) by lhreml730-chm.china.huawei.com (10.201.108.81) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Thu, 26 Sep 2019 02:49:50 +0100
Received: from DGGEML402-HUB.china.huawei.com (10.3.17.38) by lhreml730-chm.china.huawei.com (10.201.108.81) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1713.5 via Frontend Transport; Thu, 26 Sep 2019 02:49:49 +0100
Received: from DGGEML529-MBX.china.huawei.com ([169.254.6.245]) by DGGEML402-HUB.china.huawei.com ([fe80::fca6:7568:4ee3:c776%31]) with mapi id 14.03.0439.000; Thu, 26 Sep 2019 09:49:38 +0800
From: "Chengli (Cheng Li)" <chengli13@huawei.com>
To: Hariharan Ananthakrishnan <hari@netflix.com>, Mach Chen <mach.chen@huawei.com>, "chengweiqiang@chinamobile.com" <chengweiqiang@chinamobile.com>, "Dongjie (Jimmy)" <jie.dong@huawei.com>, Lizhenbin <lizhenbin@huawei.com>, "rgandhi@cisco.com" <rgandhi@cisco.com>, "xiong.quan@zte.com.cn" <xiong.quan@zte.com.cn>
CC: "pce@ietf.org" <pce@ietf.org>
Thread-Topic: IPR Poll on draft-li-pce-sr-path-segment-08
Thread-Index: AQHVc8mflZA85oVTOkuR5uXcwgADxqc9MVRw
Date: Thu, 26 Sep 2019 01:49:37 +0000
Message-ID: <C7C2E1C43D652C4E9E49FE7517C236CB027030F6@dggeml529-mbx.china.huawei.com>
References: <CAL70W4q8DctbRNTFMWzKELNZORgL5OuStFJgFOx1tw9tq3+jGA@mail.gmail.com>
In-Reply-To: <CAL70W4q8DctbRNTFMWzKELNZORgL5OuStFJgFOx1tw9tq3+jGA@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.130.185.75]
Content-Type: multipart/alternative; boundary="_000_C7C2E1C43D652C4E9E49FE7517C236CB027030F6dggeml529mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/6FuNZwHgEutJceEpAhMkzjMl6n4>
Subject: Re: [Pce] IPR Poll on draft-li-pce-sr-path-segment-08
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Sep 2019 01:49:55 -0000

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

SGkgSGFyaSBhbmQgV0csDQoNCkkgYW0gbm90IGF3YXJlIG9mIGFueSBJUFIgYXBwbGljYWJsZSB0
byB0aGlzIGRyYWZ0IHRoYXQgc2hvdWxkIGJlIGRpc2Nsb3NlZA0KaW4gYWNjb3JkYW5jZSB3aXRo
IElFVEYgSVBSIHJ1bGVzLg0KDQpDaGVuZw0KDQoNCkZyb206IEhhcmloYXJhbiBBbmFudGhha3Jp
c2huYW4gW21haWx0bzpoYXJpQG5ldGZsaXguY29tXQ0KU2VudDogVGh1cnNkYXksIFNlcHRlbWJl
ciAyNiwgMjAxOSAxOjQ5IEFNDQpUbzogQ2hlbmdsaSAoQ2hlbmcgTGkpIDxjaGVuZ2xpMTNAaHVh
d2VpLmNvbT47IE1hY2ggQ2hlbiA8bWFjaC5jaGVuQGh1YXdlaS5jb20+OyBjaGVuZ3dlaXFpYW5n
QGNoaW5hbW9iaWxlLmNvbTsgRG9uZ2ppZSAoSmltbXkpIDxqaWUuZG9uZ0BodWF3ZWkuY29tPjsg
TGl6aGVuYmluIDxsaXpoZW5iaW5AaHVhd2VpLmNvbT47IHJnYW5kaGlAY2lzY28uY29tOyB4aW9u
Zy5xdWFuQHp0ZS5jb20uY24NCkNjOiBwY2VAaWV0Zi5vcmcNClN1YmplY3Q6IElQUiBQb2xsIG9u
IGRyYWZ0LWxpLXBjZS1zci1wYXRoLXNlZ21lbnQtMDgNCg0KDQpIaSBBdXRob3JzLA0KDQoNCg0K
SW4gcHJlcGFyYXRpb24gZm9yIFdvcmtpbmcgR3JvdXAgbGFzdCBjYWxsIG9uIHRoaXMgZHJhZnQs
IEknZCBsaWtlIGFsbA0KDQphdXRob3JzIGFuZCBjb250cmlidXRvcnMgdG8gY29uZmlybSBvbiB0
aGUgbGlzdCB0aGF0IHRoZXkgYXJlIGluIGNvbXBsaWFuY2UNCg0Kd2l0aCBJRVRGIElQUiBydWxl
cy4NCg0KDQoNClBsZWFzZSByZXNwb25kIChjb3B5aW5nIHRoZSBtYWlsaW5nIGxpc3QpIHRvIHNh
eSBvbmUgb2Y6DQoNCg0KDQpJIGFtIG5vdCBhd2FyZSBvZiBhbnkgSVBSIGFwcGxpY2FibGUgdG8g
dGhpcyBkcmFmdCB0aGF0IHNob3VsZCBiZSBkaXNjbG9zZWQNCg0KaW4gYWNjb3JkYW5jZSB3aXRo
IElFVEYgSVBSIHJ1bGVzLg0KDQoNCg0KSSBhbSBhd2FyZSBvZiBJUFIgYXBwbGljYWJsZSB0byB0
aGlzIGRyYWZ0LCBhbmQgaXQgaGFzIGFscmVhZHkgYmVlbg0KDQpkaXNjbG9zZWQgdG8gdGhlIElF
VEYuDQoNCg0KDQpJIGFtIGF3YXJlIG9mIElQUiBhcHBsaWNhYmxlIHRvIHRoaXMgZHJhZnQsIGJ1
dCB0aGF0IGhhcyBub3QgeWV0IGJlZW4NCg0KZGlzY2xvc2VkIHRvIHRoZSBJRVRGLiBJIHdpbGwg
d29yayB0byBlbnN1cmUgdGhhdCBpdCB3aWxsIGJlIGRpc2Nsb3NlZCBpbiBhDQoNCnRpbWVseSBt
YW5uZXIuDQoNCg0KDQpUaGFua3MsDQoNCi0gSGFyaQ0K

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6ZHQ9InV1aWQ6QzJGNDEwMTAtNjVC
My0xMWQxLUEyOUYtMDBBQTAwQzE0ODgyIiB4bWxuczptPSJodHRwOi8vc2NoZW1hcy5taWNyb3Nv
ZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy9UUi9S
RUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250
ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1ldGEgbmFtZT0iR2VuZXJhdG9yIiBj
b250ZW50PSJNaWNyb3NvZnQgV29yZCAxNSAoZmlsdGVyZWQgbWVkaXVtKSI+DQo8c3R5bGU+PCEt
LQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTrlrovk
vZM7DQoJcGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQpAZm9udC1mYWNlDQoJe2ZvbnQt
ZmFtaWx5OiJDYW1icmlhIE1hdGgiOw0KCXBhbm9zZS0xOjIgNCA1IDMgNSA0IDYgMyAyIDQ7fQ0K
QGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDYWxpYnJpOw0KCXBhbm9zZS0xOjIgMTUgNSAyIDIg
MiA0IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IlxA5a6L5L2TIjsNCglwYW5v
c2UtMToyIDEgNiAwIDMgMSAxIDEgMSAxO30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q29u
c29sYXM7DQoJcGFub3NlLTE6MiAxMSA2IDkgMiAyIDQgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtm
b250LWZhbWlseTpWZXJkYW5hOw0KCXBhbm9zZS0xOjIgMTEgNiA0IDMgNSA0IDQgMiA0O30NCi8q
IFN0eWxlIERlZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNv
Tm9ybWFsDQoJe21hcmdpbjowY207DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6
ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIsc2VyaWY7fQ0KYTpsaW5r
LCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6IzA1
NjNDMTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29I
eXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Izk1NEY3
MjsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnByZQ0KCXttc28tc3R5bGUtcHJpb3Jp
dHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IkhUTUwg6aKE6K6+5qC85byPIENoYXIiOw0KCW1hcmdp
bjowY207DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7DQoJZm9u
dC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQpzcGFuLkhUTUxDaGFyDQoJe21zby1zdHlsZS1uYW1l
OiJIVE1MIOmihOiuvuagvOW8jyBDaGFyIjsNCgltc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNv
LXN0eWxlLWxpbms6IkhUTUwg6aKE6K6+5qC85byPIjsNCglmb250LWZhbWlseTpDb25zb2xhczt9
DQpzcGFuLkVtYWlsU3R5bGUxOQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglm
b250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjojMUY0OTdEO30NCi5Nc29D
aHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtZmFtaWx5OiJD
YWxpYnJpIixzYW5zLXNlcmlmO30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjYxMi4wcHQg
NzkyLjBwdDsNCgltYXJnaW46NzIuMHB0IDkwLjBwdCA3Mi4wcHQgOTAuMHB0O30NCmRpdi5Xb3Jk
U2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBt
c28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYi
IC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBl
bGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0K
PC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0i
RU4tVVMiIGxpbms9IiMwNTYzQzEiIHZsaW5rPSIjOTU0RjcyIj4NCjxkaXYgY2xhc3M9IldvcmRT
ZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFG
NDk3RCI+SGkgSGFyaSBhbmQgV0csPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjoj
MUY0OTdEIj5JIGFtIG5vdCBhd2FyZSBvZiBhbnkgSVBSIGFwcGxpY2FibGUgdG8gdGhpcyBkcmFm
dCB0aGF0IHNob3VsZCBiZSBkaXNjbG9zZWQ8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+aW4gYWNjb3JkYW5j
ZSB3aXRoIElFVEYgSVBSIHJ1bGVzLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6
IzFGNDk3RCI+Q2hlbmc8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Qi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssc2Fucy1zZXJpZiI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+IEhhcmloYXJh
biBBbmFudGhha3Jpc2huYW4gW21haWx0bzpoYXJpQG5ldGZsaXguY29tXQ0KPGJyPg0KPGI+U2Vu
dDo8L2I+IFRodXJzZGF5LCBTZXB0ZW1iZXIgMjYsIDIwMTkgMTo0OSBBTTxicj4NCjxiPlRvOjwv
Yj4gQ2hlbmdsaSAoQ2hlbmcgTGkpICZsdDtjaGVuZ2xpMTNAaHVhd2VpLmNvbSZndDs7IE1hY2gg
Q2hlbiAmbHQ7bWFjaC5jaGVuQGh1YXdlaS5jb20mZ3Q7OyBjaGVuZ3dlaXFpYW5nQGNoaW5hbW9i
aWxlLmNvbTsgRG9uZ2ppZSAoSmltbXkpICZsdDtqaWUuZG9uZ0BodWF3ZWkuY29tJmd0OzsgTGl6
aGVuYmluICZsdDtsaXpoZW5iaW5AaHVhd2VpLmNvbSZndDs7IHJnYW5kaGlAY2lzY28uY29tOyB4
aW9uZy5xdWFuQHp0ZS5jb20uY248YnI+DQo8Yj5DYzo8L2I+IHBjZUBpZXRmLm9yZzxicj4NCjxi
PlN1YmplY3Q6PC9iPiBJUFIgUG9sbCBvbiBkcmFmdC1saS1wY2Utc3ItcGF0aC1zZWdtZW50LTA4
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8
L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwcmU+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZx
dW90O1ZlcmRhbmEmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMjEyNTI5Ij5IaSBBdXRob3JzLDxv
OnA+PC9vOnA+PC9zcGFuPjwvcHJlPg0KPHByZT48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1
b3Q7VmVyZGFuYSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMyMTI1MjkiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcHJlPg0KPHByZT48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7VmVy
ZGFuYSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMyMTI1MjkiPkluIHByZXBhcmF0aW9uIGZvciBX
b3JraW5nIEdyb3VwIGxhc3QgY2FsbCBvbiB0aGlzIGRyYWZ0LCBJJ2QgbGlrZSBhbGw8bzpwPjwv
bzpwPjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1Zl
cmRhbmEmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMjEyNTI5Ij5hdXRob3JzIGFuZCBjb250cmli
dXRvcnMgdG8gY29uZmlybSBvbiB0aGUgbGlzdCB0aGF0IHRoZXkgYXJlIGluIGNvbXBsaWFuY2U8
bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZx
dW90O1ZlcmRhbmEmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMjEyNTI5Ij53aXRoIElFVEYgSVBS
IHJ1bGVzLjxvOnA+PC9vOnA+PC9zcGFuPjwvcHJlPg0KPHByZT48c3BhbiBzdHlsZT0iZm9udC1m
YW1pbHk6JnF1b3Q7VmVyZGFuYSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMyMTI1MjkiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcHJlPg0KPHByZT48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6
JnF1b3Q7VmVyZGFuYSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMyMTI1MjkiPlBsZWFzZSByZXNw
b25kIChjb3B5aW5nIHRoZSBtYWlsaW5nIGxpc3QpIHRvIHNheSBvbmUgb2Y6PG86cD48L286cD48
L3NwYW4+PC9wcmU+DQo8cHJlPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtWZXJkYW5h
JnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzIxMjUyOSI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wcmU+DQo8cHJlPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7
LHNhbnMtc2VyaWY7Y29sb3I6IzIxMjUyOSI+SSBhbSBub3QgYXdhcmUgb2YgYW55IElQUiBhcHBs
aWNhYmxlIHRvIHRoaXMgZHJhZnQgdGhhdCBzaG91bGQgYmUgZGlzY2xvc2VkPG86cD48L286cD48
L3NwYW4+PC9wcmU+DQo8cHJlPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtWZXJkYW5h
JnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzIxMjUyOSI+aW4gYWNjb3JkYW5jZSB3aXRoIElFVEYg
SVBSIHJ1bGVzLjxvOnA+PC9vOnA+PC9zcGFuPjwvcHJlPg0KPHByZT48c3BhbiBzdHlsZT0iZm9u
dC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMyMTI1MjkiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcHJlPg0KPHByZT48c3BhbiBzdHlsZT0iZm9udC1mYW1p
bHk6JnF1b3Q7VmVyZGFuYSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMyMTI1MjkiPkkgYW0gYXdh
cmUgb2YgSVBSIGFwcGxpY2FibGUgdG8gdGhpcyBkcmFmdCwgYW5kIGl0IGhhcyBhbHJlYWR5IGJl
ZW48bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5
OiZxdW90O1ZlcmRhbmEmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMjEyNTI5Ij5kaXNjbG9zZWQg
dG8gdGhlIElFVEYuPG86cD48L286cD48L3NwYW4+PC9wcmU+DQo8cHJlPjxzcGFuIHN0eWxlPSJm
b250LWZhbWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzIxMjUyOSI+
PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wcmU+DQo8cHJlPjxzcGFuIHN0eWxlPSJmb250LWZh
bWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzIxMjUyOSI+SSBhbSBh
d2FyZSBvZiBJUFIgYXBwbGljYWJsZSB0byB0aGlzIGRyYWZ0LCBidXQgdGhhdCBoYXMgbm90IHll
dCBiZWVuPG86cD48L286cD48L3NwYW4+PC9wcmU+DQo8cHJlPjxzcGFuIHN0eWxlPSJmb250LWZh
bWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzIxMjUyOSI+ZGlzY2xv
c2VkIHRvIHRoZSBJRVRGLiBJIHdpbGwgd29yayB0byBlbnN1cmUgdGhhdCBpdCB3aWxsIGJlIGRp
c2Nsb3NlZCBpbiBhPG86cD48L286cD48L3NwYW4+PC9wcmU+DQo8cHJlPjxzcGFuIHN0eWxlPSJm
b250LWZhbWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzIxMjUyOSI+
dGltZWx5IG1hbm5lci48bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4gc3R5bGU9
ImZvbnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMjEyNTI5
Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4gc3R5bGU9ImZvbnQt
ZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMjEyNTI5Ij5UaGFu
a3MsPG86cD48L286cD48L3NwYW4+PC9wcmU+DQo8cHJlPjxzcGFuIHN0eWxlPSJmb250LWZhbWls
eTomcXVvdDtWZXJkYW5hJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzIxMjUyOSI+LSBIYXJpPC9z
cGFuPjxzcGFuIHN0eWxlPSJjb2xvcjojMjEyNTI5Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT4N
CjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_C7C2E1C43D652C4E9E49FE7517C236CB027030F6dggeml529mbxchi_--


From nobody Wed Sep 25 19:07:33 2019
Return-Path: <chengweiqiang@chinamobile.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84699120170 for <pce@ietfa.amsl.com>; Wed, 25 Sep 2019 19:07:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G9j-VY79fdOa for <pce@ietfa.amsl.com>; Wed, 25 Sep 2019 19:07:28 -0700 (PDT)
Received: from cmccmta1.chinamobile.com (cmccmta1.chinamobile.com [221.176.66.79]) by ietfa.amsl.com (Postfix) with ESMTP id 06E90120088 for <pce@ietf.org>; Wed, 25 Sep 2019 19:07:27 -0700 (PDT)
Received: from spf.mail.chinamobile.com (unknown[172.16.121.3]) by rmmx-syy-dmz-app03-12003 (RichMail) with SMTP id 2ee35d8c1d5110e-1cc9f; Thu, 26 Sep 2019 10:07:14 +0800 (CST)
X-RM-TRANSID: 2ee35d8c1d5110e-1cc9f
X-RM-TagInfo: emlType=0                                       
X-RM-SPAM-FLAG: 00000000
Received: from cmcc (unknown[10.2.51.55]) by rmsmtp-syy-appsvr02-12002 (RichMail) with SMTP id 2ee25d8c1d50e78-33026; Thu, 26 Sep 2019 10:07:13 +0800 (CST)
X-RM-TRANSID: 2ee25d8c1d50e78-33026
From: "Weiqiang Cheng" <chengweiqiang@chinamobile.com>
To: "'Chengli \(Cheng Li\)'" <chengli13@huawei.com>, "'Hariharan Ananthakrishnan'" <hari@netflix.com>, "'Mach Chen'" <mach.chen@huawei.com>, "'Dongjie \(Jimmy\)'" <jie.dong@huawei.com>, "'Lizhenbin'" <lizhenbin@huawei.com>, <rgandhi@cisco.com>, <xiong.quan@zte.com.cn>
Cc: <pce@ietf.org>
References: <CAL70W4q8DctbRNTFMWzKELNZORgL5OuStFJgFOx1tw9tq3+jGA@mail.gmail.com> <C7C2E1C43D652C4E9E49FE7517C236CB027030F6@dggeml529-mbx.china.huawei.com>
In-Reply-To: <C7C2E1C43D652C4E9E49FE7517C236CB027030F6@dggeml529-mbx.china.huawei.com>
Date: Thu, 26 Sep 2019 10:07:11 +0800
Message-ID: <022001d5740f$1c5658d0$55030a70$@com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0221_01D57452.2A7998D0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQHVc8mflZA85oVTOkuR5uXcwgADxqc9MVRwgAAE8wA=
Content-Language: zh-cn
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/oWq04kfZA2uH2O4f_qjiC1VtqtA>
Subject: [Pce] =?utf-8?b?562U5aSNOiBJUFIgUG9sbCBvbiBkcmFmdC1saS1wY2Utc3It?= =?utf-8?q?path-segment-08?=
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Sep 2019 02:07:32 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0221_01D57452.2A7998D0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hi,

I am not aware of any IPR applicable to the draft.

=20

B.R.

Weiqiang Cheng

=20

=E5=8F=91=E4=BB=B6=E4=BA=BA: Chengli (Cheng Li) =
[mailto:chengli13@huawei.com]=20
=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2019=E5=B9=B49=E6=9C=8826=E6=97=A5 =
09:50
=E6=94=B6=E4=BB=B6=E4=BA=BA: Hariharan Ananthakrishnan; Mach Chen; =
chengweiqiang@chinamobile.com; Dongjie (Jimmy); Lizhenbin; =
rgandhi@cisco.com; xiong.quan@zte.com.cn
=E6=8A=84=E9=80=81: pce@ietf.org
=E4=B8=BB=E9=A2=98: RE: IPR Poll on draft-li-pce-sr-path-segment-08

=20

Hi Hari and WG,

=20

I am not aware of any IPR applicable to this draft that should be =
disclosed

in accordance with IETF IPR rules.

=20

Cheng

=20

=20

From: Hariharan Ananthakrishnan [mailto:hari@netflix.com]=20
Sent: Thursday, September 26, 2019 1:49 AM
To: Chengli (Cheng Li) <chengli13@huawei.com>; Mach Chen =
<mach.chen@huawei.com>; chengweiqiang@chinamobile.com; Dongjie (Jimmy) =
<jie.dong@huawei.com>; Lizhenbin <lizhenbin@huawei.com>; =
rgandhi@cisco.com; xiong.quan@zte.com.cn
Cc: pce@ietf.org
Subject: IPR Poll on draft-li-pce-sr-path-segment-08

=20

Hi Authors,
=20
In preparation for Working Group last call on this draft, I'd like all
authors and contributors to confirm on the list that they are in =
compliance
with IETF IPR rules.
=20
Please respond (copying the mailing list) to say one of:
=20
I am not aware of any IPR applicable to this draft that should be =
disclosed
in accordance with IETF IPR rules.
=20
I am aware of IPR applicable to this draft, and it has already been
disclosed to the IETF.
=20
I am aware of IPR applicable to this draft, but that has not yet been
disclosed to the IETF. I will work to ensure that it will be disclosed =
in a
timely manner.
=20
Thanks,
- Hari

------=_NextPart_000_0221_01D57452.2A7998D0
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 12 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:=E5=AE=8B=E4=BD=93;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@=E5=AE=8B=E4=BD=93";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML =E9=A2=84=E8=AE=BE=E6=A0=BC=E5=BC=8F Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.HTMLChar
	{mso-style-name:"HTML =E9=A2=84=E8=AE=BE=E6=A0=BC=E5=BC=8F Char";
	mso-style-priority:99;
	mso-style-link:"HTML =E9=A2=84=E8=AE=BE=E6=A0=BC=E5=BC=8F";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DZH-CN =
link=3D"#0563C1" vlink=3D"#954F72"><div class=3DWordSection1><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Hi,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I am not aware of any IPR applicable to the =
draft.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>B.R.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Weiqiang Cheng<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:=E5=AE=8B=E4=BD=93'>=E5=8F=91=E4=BB=
=B6=E4=BA=BA<span lang=3DEN-US>:</span></span></b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:=E5=AE=8B=E4=BD=93'> Chengli =
(Cheng Li) [mailto:chengli13@huawei.com] <br></span><b><span =
style=3D'font-size:10.0pt;font-family:=E5=AE=8B=E4=BD=93'>=E5=8F=91=E9=80=
=81=E6=97=B6=E9=97=B4<span lang=3DEN-US>:</span></span></b><span =
lang=3DEN-US style=3D'font-size:10.0pt;font-family:=E5=AE=8B=E4=BD=93'> =
2019</span><span =
style=3D'font-size:10.0pt;font-family:=E5=AE=8B=E4=BD=93'>=E5=B9=B4<span =
lang=3DEN-US>9</span>=E6=9C=88<span lang=3DEN-US>26</span>=E6=97=A5<span =
lang=3DEN-US> 09:50<br></span><b>=E6=94=B6=E4=BB=B6=E4=BA=BA<span =
lang=3DEN-US>:</span></b><span lang=3DEN-US> Hariharan Ananthakrishnan; =
Mach Chen; chengweiqiang@chinamobile.com; Dongjie (Jimmy); Lizhenbin; =
rgandhi@cisco.com; =
xiong.quan@zte.com.cn<br></span><b>=E6=8A=84=E9=80=81<span =
lang=3DEN-US>:</span></b><span lang=3DEN-US> =
pce@ietf.org<br></span><b>=E4=B8=BB=E9=A2=98<span =
lang=3DEN-US>:</span></b><span lang=3DEN-US> RE: IPR Poll on =
draft-li-pce-sr-path-segment-08<o:p></o:p></span></span></p></div></div><=
p class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Hi Hari and WG,<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I am not aware of any IPR applicable to this draft that should be =
disclosed<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>in accordance with IETF IPR rules.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Cheng<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><b><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>From:</span=
></b><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'> Hariharan =
Ananthakrishnan [mailto:hari@netflix.com] <br><b>Sent:</b> Thursday, =
September 26, 2019 1:49 AM<br><b>To:</b> Chengli (Cheng Li) =
&lt;chengli13@huawei.com&gt;; Mach Chen &lt;mach.chen@huawei.com&gt;; =
chengweiqiang@chinamobile.com; Dongjie (Jimmy) =
&lt;jie.dong@huawei.com&gt;; Lizhenbin &lt;lizhenbin@huawei.com&gt;; =
rgandhi@cisco.com; xiong.quan@zte.com.cn<br><b>Cc:</b> =
pce@ietf.org<br><b>Subject:</b> IPR Poll on =
draft-li-pce-sr-path-segment-08<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><div><div><pre><span =
lang=3DEN-US =
style=3D'font-family:"Verdana","sans-serif";color:#212529'>Hi =
Authors,<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'font-family:"Verdana","sans-serif";color:#212529'><o:p>&nbsp;</o=
:p></span></pre><pre><span lang=3DEN-US =
style=3D'font-family:"Verdana","sans-serif";color:#212529'>In =
preparation for Working Group last call on this draft, I'd like =
all<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'font-family:"Verdana","sans-serif";color:#212529'>authors and =
contributors to confirm on the list that they are in =
compliance<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'font-family:"Verdana","sans-serif";color:#212529'>with IETF IPR =
rules.<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'font-family:"Verdana","sans-serif";color:#212529'><o:p>&nbsp;</o=
:p></span></pre><pre><span lang=3DEN-US =
style=3D'font-family:"Verdana","sans-serif";color:#212529'>Please =
respond (copying the mailing list) to say one =
of:<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'font-family:"Verdana","sans-serif";color:#212529'><o:p>&nbsp;</o=
:p></span></pre><pre><span lang=3DEN-US =
style=3D'font-family:"Verdana","sans-serif";color:#212529'>I am not =
aware of any IPR applicable to this draft that should be =
disclosed<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'font-family:"Verdana","sans-serif";color:#212529'>in accordance =
with IETF IPR rules.<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'font-family:"Verdana","sans-serif";color:#212529'><o:p>&nbsp;</o=
:p></span></pre><pre><span lang=3DEN-US =
style=3D'font-family:"Verdana","sans-serif";color:#212529'>I am aware of =
IPR applicable to this draft, and it has already =
been<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'font-family:"Verdana","sans-serif";color:#212529'>disclosed to =
the IETF.<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'font-family:"Verdana","sans-serif";color:#212529'><o:p>&nbsp;</o=
:p></span></pre><pre><span lang=3DEN-US =
style=3D'font-family:"Verdana","sans-serif";color:#212529'>I am aware of =
IPR applicable to this draft, but that has not yet =
been<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'font-family:"Verdana","sans-serif";color:#212529'>disclosed to =
the IETF. I will work to ensure that it will be disclosed in =
a<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'font-family:"Verdana","sans-serif";color:#212529'>timely =
manner.<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'font-family:"Verdana","sans-serif";color:#212529'><o:p>&nbsp;</o=
:p></span></pre><pre><span lang=3DEN-US =
style=3D'font-family:"Verdana","sans-serif";color:#212529'>Thanks,<o:p></=
o:p></span></pre><pre><span lang=3DEN-US =
style=3D'font-family:"Verdana","sans-serif";color:#212529'>- =
Hari</span><span lang=3DEN-US =
style=3D'color:#212529'><o:p></o:p></span></pre></div></div></div></body>=
</html>
------=_NextPart_000_0221_01D57452.2A7998D0--




From nobody Wed Sep 25 19:42:53 2019
Return-Path: <xiong.quan@zte.com.cn>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8B20120110 for <pce@ietfa.amsl.com>; Wed, 25 Sep 2019 19:42:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level: 
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QEdwkEpDZ5Fc for <pce@ietfa.amsl.com>; Wed, 25 Sep 2019 19:42:48 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.217.80.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29BAA120033 for <pce@ietf.org>; Wed, 25 Sep 2019 19:42:47 -0700 (PDT)
Received: from mxct.zte.com.cn (unknown [192.168.164.217]) by Forcepoint Email with ESMTPS id 66F3D1DB47B35F08A668 for <pce@ietf.org>; Thu, 26 Sep 2019 10:42:45 +0800 (CST)
Received: from mse-fl1.zte.com.cn (unknown [10.30.14.238]) by Forcepoint Email with ESMTPS id 2310E1549918963F1922; Thu, 26 Sep 2019 10:35:04 +0800 (CST)
Received: from njxapp02.zte.com.cn ([10.41.132.201]) by mse-fl1.zte.com.cn with SMTP id x8Q2Xc9B047752; Thu, 26 Sep 2019 10:33:38 +0800 (GMT-8) (envelope-from xiong.quan@zte.com.cn)
Received: from mapi (njxapp05[null]) by mapi (Zmail) with MAPI id mid201; Thu, 26 Sep 2019 10:33:37 +0800 (CST)
Date: Thu, 26 Sep 2019 10:33:37 +0800 (CST)
X-Zmail-TransId: 2afd5d8c23815e28c1c3
X-Mailer: Zmail v1.0
Message-ID: <201909261033378021824@zte.com.cn>
In-Reply-To: <CAL70W4q8DctbRNTFMWzKELNZORgL5OuStFJgFOx1tw9tq3+jGA@mail.gmail.com>
References: CAL70W4q8DctbRNTFMWzKELNZORgL5OuStFJgFOx1tw9tq3+jGA@mail.gmail.com
Mime-Version: 1.0
From: <xiong.quan@zte.com.cn>
To: <hari@netflix.com>
Cc: <chengli13@huawei.com>, <mach.chen@huawei.com>, <chengweiqiang@chinamobile.com>, <jie.dong@huawei.com>, <lizhenbin@huawei.com>, <rgandhi@cisco.com>, <pce@ietf.org>
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl1.zte.com.cn x8Q2Xc9B047752
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/epIYjwIP-hu_IOmS5erXOkRzmi8>
Subject: [Pce] =?utf-8?b?562U5aSNOiBJUFIgUG9sbCBvbiBkcmFmdC1saS1wY2Utc3It?= =?utf-8?q?path-segment-08?=
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Sep 2019 02:42:51 -0000

--=====_001_next=====
Content-Type: multipart/related;
	boundary="=====_002_next====="


--=====_002_next=====
Content-Type: multipart/alternative;
	boundary="=====_003_next====="


--=====_003_next=====
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: base64

SGkgSGFyaSBhbmQgV0csDQoNCg0KIA0KDQoNCkkgYW0gbm90IGF3YXJlIG9mIGFueSBJUFIgYXBw
bGljYWJsZSB0byB0aGlzIGRyYWZ0IHRoYXQgc2hvdWxkIGJlIGRpc2Nsb3NlZCBpbiBhY2NvcmRh
bmNlIHdpdGggSUVURiBJUFIgcnVsZXMuDQoNCg0KIA0KDQoNClF1YW4NCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQrljp/lp4vpgq7ku7YNCg0KDQoNCuWPkeS7tuS6uu+8mkhhcmloYXJhbkFuYW50aGFr
cmlzaG5hbiA8aGFyaUBuZXRmbGl4LmNvbT4NCuaUtuS7tuS6uu+8mmNoZW5nbGkxM0BodWF3ZWku
Y29tIDxjaGVuZ2xpMTNAaHVhd2VpLmNvbT47bWFjaC5jaGVuQGh1YXdlaS5jb20gPG1hY2guY2hl
bkBodWF3ZWkuY29tPjtjaGVuZ3dlaXFpYW5nQGNoaW5hbW9iaWxlLmNvbSA8Y2hlbmd3ZWlxaWFu
Z0BjaGluYW1vYmlsZS5jb20+O2ppZS5kb25nQGh1YXdlaS5jb20gPGppZS5kb25nQGh1YXdlaS5j
b20+O2xpemhlbmJpbkBodWF3ZWkuY29tIDxsaXpoZW5iaW5AaHVhd2VpLmNvbT47cmdhbmRoaUBj
aXNjby5jb20gPHJnYW5kaGlAY2lzY28uY29tPjvnhorms4kwMDA5MTA2NTsNCuaKhOmAgeS6uu+8
mnBjZUBpZXRmLm9yZyA8cGNlQGlldGYub3JnPjsNCuaXpSDmnJ8g77yaMjAxOeW5tDA55pyIMjbm
l6UgMDI6MDQNCuS4uyDpopgg77yaSVBSIFBvbGwgb24gZHJhZnQtbGktcGNlLXNyLXBhdGgtc2Vn
bWVudC0wOA0KDQoNCg0KDQpIaSBBdXRob3JzLAoKSW4gcHJlcGFyYXRpb24gZm9yIFdvcmtpbmcg
R3JvdXAgbGFzdCBjYWxsIG9uIHRoaXMgZHJhZnQsIEknZCBsaWtlIGFsbAphdXRob3JzIGFuZCBj
b250cmlidXRvcnMgdG8gY29uZmlybSBvbiB0aGUgbGlzdCB0aGF0IHRoZXkgYXJlIGluIGNvbXBs
aWFuY2UKd2l0aCBJRVRGIElQUiBydWxlcy4KClBsZWFzZSByZXNwb25kIChjb3B5aW5nIHRoZSBt
YWlsaW5nIGxpc3QpIHRvIHNheSBvbmUgb2Y6CgpJIGFtIG5vdCBhd2FyZSBvZiBhbnkgSVBSIGFw
cGxpY2FibGUgdG8gdGhpcyBkcmFmdCB0aGF0IHNob3VsZCBiZSBkaXNjbG9zZWQKaW4gYWNjb3Jk
YW5jZSB3aXRoIElFVEYgSVBSIHJ1bGVzLgoKSSBhbSBhd2FyZSBvZiBJUFIgYXBwbGljYWJsZSB0
byB0aGlzIGRyYWZ0LCBhbmQgaXQgaGFzIGFscmVhZHkgYmVlbgpkaXNjbG9zZWQgdG8gdGhlIElF
VEYuCgpJIGFtIGF3YXJlIG9mIElQUiBhcHBsaWNhYmxlIHRvIHRoaXMgZHJhZnQsIGJ1dCB0aGF0
IGhhcyBub3QgeWV0IGJlZW4KZGlzY2xvc2VkIHRvIHRoZSBJRVRGLiBJIHdpbGwgd29yayB0byBl
bnN1cmUgdGhhdCBpdCB3aWxsIGJlIGRpc2Nsb3NlZCBpbiBhCnRpbWVseSBtYW5uZXIuCgpUaGFu
a3MsCi0gSGFyaQ==


--=====_003_next=====
Content-Type: text/html ;
	charset="UTF-8"
Content-Transfer-Encoding: base64

PGRpdiBjbGFzcz0iemNvbnRlbnRSb3ciPjxwIHN0eWxlPSJmb250LXNpemU6MTRweDtmb250LWZh
bWlseTphcmlhbDsiPjxicj48L3A+PHAgc3R5bGU9ImJveC1zaXppbmc6IGJvcmRlci1ib3g7d2hp
dGUtc3BhY2U6IG5vcm1hbDttaW4taGVpZ2h0OiAxNHB4O2ZvbnQtc2l6ZTogMTZweDtmb250LWZh
bWlseTogJ1RpbWVzIE5ldyBSb21hbicsIHNlcmlmO291dGxpbmU6IDBweCAhaW1wb3J0YW50O2Jh
Y2tncm91bmQtY29sb3I6IHJnYigyNTUsIDI1NSwgMjU1KSI+PHNwYW4gc3R5bGU9ImJveC1zaXpp
bmc6IGJvcmRlci1ib3g7Zm9udC1zaXplOiAyMHB4O2ZvbnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5z
LXNlcmlmO2NvbG9yOiByZ2IoMzEsIDczLCAxMjUpO291dGxpbmU6IDBweCAhaW1wb3J0YW50Ij5I
aSBIYXJpIGFuZCBXRyw8L3NwYW4+PC9wPjxwIHN0eWxlPSJib3gtc2l6aW5nOiBib3JkZXItYm94
O3doaXRlLXNwYWNlOiBub3JtYWw7bWluLWhlaWdodDogMTRweDtmb250LXNpemU6IDE2cHg7Zm9u
dC1mYW1pbHk6ICdUaW1lcyBOZXcgUm9tYW4nLCBzZXJpZjtvdXRsaW5lOiAwcHggIWltcG9ydGFu
dDtiYWNrZ3JvdW5kLWNvbG9yOiByZ2IoMjU1LCAyNTUsIDI1NSkiPjxzcGFuIHN0eWxlPSJib3gt
c2l6aW5nOiBib3JkZXItYm94O2ZvbnQtc2l6ZTogMjBweDtmb250LWZhbWlseTogQ2FsaWJyaSwg
c2Fucy1zZXJpZjtjb2xvcjogcmdiKDMxLCA3MywgMTI1KTtvdXRsaW5lOiAwcHggIWltcG9ydGFu
dCI+Jm5ic3A7PC9zcGFuPjwvcD48cCBzdHlsZT0iYm94LXNpemluZzogYm9yZGVyLWJveDt3aGl0
ZS1zcGFjZTogbm9ybWFsO21pbi1oZWlnaHQ6IDE0cHg7Zm9udC1zaXplOiAxNnB4O2ZvbnQtZmFt
aWx5OiAnVGltZXMgTmV3IFJvbWFuJywgc2VyaWY7b3V0bGluZTogMHB4ICFpbXBvcnRhbnQ7YmFj
a2dyb3VuZC1jb2xvcjogcmdiKDI1NSwgMjU1LCAyNTUpIj48c3BhbiBzdHlsZT0iYm94LXNpemlu
ZzogYm9yZGVyLWJveDtmb250LXNpemU6IDIwcHg7Zm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMt
c2VyaWY7Y29sb3I6IHJnYigzMSwgNzMsIDEyNSk7b3V0bGluZTogMHB4ICFpbXBvcnRhbnQiPkkg
YW0gbm90IGF3YXJlIG9mIGFueSBJUFIgYXBwbGljYWJsZSB0byB0aGlzIGRyYWZ0IHRoYXQgc2hv
dWxkIGJlIGRpc2Nsb3NlZCZuYnNwOzwvc3Bhbj48c3BhbiBzdHlsZT0iY29sb3I6IHJnYigzMSwg
NzMsIDEyNSk7IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5zLXNlcmlmOyBmb250LXNpemU6IDIw
cHg7Ij5pbiBhY2NvcmRhbmNlIHdpdGggSUVURiBJUFIgcnVsZXMuPC9zcGFuPjwvcD48cCBzdHls
ZT0iYm94LXNpemluZzogYm9yZGVyLWJveDt3aGl0ZS1zcGFjZTogbm9ybWFsO21pbi1oZWlnaHQ6
IDE0cHg7Zm9udC1zaXplOiAxNnB4O2ZvbnQtZmFtaWx5OiAnVGltZXMgTmV3IFJvbWFuJywgc2Vy
aWY7b3V0bGluZTogMHB4ICFpbXBvcnRhbnQ7YmFja2dyb3VuZC1jb2xvcjogcmdiKDI1NSwgMjU1
LCAyNTUpIj48c3BhbiBzdHlsZT0iYm94LXNpemluZzogYm9yZGVyLWJveDtmb250LXNpemU6IDIw
cHg7Zm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7Y29sb3I6IHJnYigzMSwgNzMsIDEy
NSk7b3V0bGluZTogMHB4ICFpbXBvcnRhbnQiPiZuYnNwOzwvc3Bhbj48L3A+PHAgc3R5bGU9ImJv
eC1zaXppbmc6IGJvcmRlci1ib3g7IHdoaXRlLXNwYWNlOiBub3JtYWw7IG1pbi1oZWlnaHQ6IDE0
cHg7IG91dGxpbmU6IDBweCAhaW1wb3J0YW50OyBiYWNrZ3JvdW5kLWNvbG9yOiByZ2IoMjU1LCAy
NTUsIDI1NSk7Ij48Zm9udCBjb2xvcj0iIzFmNDk3ZCIgZmFjZT0iQ2FsaWJyaSwgc2Fucy1zZXJp
ZiI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTogMjBweDsgbGluZS1oZWlnaHQ6IDMwcHg7Ij5RdWFu
PC9zcGFuPjwvZm9udD48L3A+PHAgc3R5bGU9Im1hcmdpbi10b3A6IDBweDsgbWFyZ2luLWJvdHRv
bTogMHB4OyBsaW5lLWhlaWdodDogMjBweDsiPjxicj48L3A+PHAgc3R5bGU9ImZvbnQtc2l6ZTox
NHB4O2ZvbnQtZmFtaWx5OmFyaWFsOyI+PGJyPjwvcD48ZGl2PjxkaXYgY2xhc3M9InpoaXN0b3J5
Um93IiBzdHlsZT0iZGlzcGxheTpibG9jayI+PGRpdiBjbGFzcz0iemhpc3RvcnlEZXMiIHN0eWxl
PSJ3aWR0aDogMTAwJTsgaGVpZ2h0OiAyOHB4OyBsaW5lLWhlaWdodDogMjhweDsgYmFja2dyb3Vu
ZC1jb2xvcjogI0UwRTVFOTsgY29sb3I6ICMxMzg4RkY7IHRleHQtYWxpZ246IGNlbnRlcjsiIGxh
bmd1YWdlLWRhdGE9Ikhpc3RvcnlPcmdUeHQiPuWOn+Wni+mCruS7tjwvZGl2PjxkaXYgaWQ9Inp3
cml0ZUhpc3RvcnlDb250YWluZXIiPjxkaXYgY2xhc3M9ImNvbnRyb2wtZ3JvdXAgemhpc3RvcnlQ
YW5lbCI+PGRpdiBjbGFzcz0iemhpc3RvcnlIZWFkZXIiIHN0eWxlPSJwYWRkaW5nOiA4cHg7IGJh
Y2tncm91bmQtY29sb3I6ICNGNUY2Rjg7Ij48ZGl2PjxzdHJvbmcgbGFuZ3VhZ2UtZGF0YT0iSGlz
dG9yeVNlbmRlclR4dCI+5Y+R5Lu25Lq677yaPC9zdHJvbmc+PHNwYW4gY2xhc3M9InpyZWFkVXNl
ck5hbWUiPkhhcmloYXJhbkFuYW50aGFrcmlzaG5hbiAmbHQ7aGFyaUBuZXRmbGl4LmNvbSZndDs8
L3NwYW4+PC9kaXY+PGRpdj48c3Ryb25nIGxhbmd1YWdlLWRhdGE9Ikhpc3RvcnlUT1R4dCI+5pS2
5Lu25Lq677yaPC9zdHJvbmc+PHNwYW4gY2xhc3M9InpyZWFkVXNlck5hbWUiIHN0eWxlPSJkaXNw
bGF5OiBpbmxpbmU7Ij5jaGVuZ2xpMTNAaHVhd2VpLmNvbSAmbHQ7Y2hlbmdsaTEzQGh1YXdlaS5j
b20mZ3Q7Ozwvc3Bhbj48c3BhbiBjbGFzcz0ienJlYWRVc2VyTmFtZSIgc3R5bGU9ImRpc3BsYXk6
IGlubGluZTsiPm1hY2guY2hlbkBodWF3ZWkuY29tICZsdDttYWNoLmNoZW5AaHVhd2VpLmNvbSZn
dDs7PC9zcGFuPjxzcGFuIGNsYXNzPSJ6cmVhZFVzZXJOYW1lIiBzdHlsZT0iZGlzcGxheTogaW5s
aW5lOyI+Y2hlbmd3ZWlxaWFuZ0BjaGluYW1vYmlsZS5jb20gJmx0O2NoZW5nd2VpcWlhbmdAY2hp
bmFtb2JpbGUuY29tJmd0Ozs8L3NwYW4+PHNwYW4gY2xhc3M9InpyZWFkVXNlck5hbWUiIHN0eWxl
PSJkaXNwbGF5OiBpbmxpbmU7Ij5qaWUuZG9uZ0BodWF3ZWkuY29tICZsdDtqaWUuZG9uZ0BodWF3
ZWkuY29tJmd0Ozs8L3NwYW4+PHNwYW4gY2xhc3M9InpyZWFkVXNlck5hbWUiIHN0eWxlPSJkaXNw
bGF5OiBpbmxpbmU7Ij5saXpoZW5iaW5AaHVhd2VpLmNvbSAmbHQ7bGl6aGVuYmluQGh1YXdlaS5j
b20mZ3Q7Ozwvc3Bhbj48c3BhbiBjbGFzcz0ienJlYWRVc2VyTmFtZSIgc3R5bGU9ImRpc3BsYXk6
IGlubGluZTsiPnJnYW5kaGlAY2lzY28uY29tICZsdDtyZ2FuZGhpQGNpc2NvLmNvbSZndDs7PC9z
cGFuPjxzcGFuIGNsYXNzPSJ6cmVhZFVzZXJOYW1lIiBzdHlsZT0iZGlzcGxheTogaW5saW5lOyI+
54aK5rOJMDAwOTEwNjU7PC9zcGFuPjwvZGl2PjxkaXY+PHN0cm9uZyBsYW5ndWFnZS1kYXRhPSJI
aXN0b3J5Q0NUeHQiPuaKhOmAgeS6uu+8mjwvc3Ryb25nPjxzcGFuIGNsYXNzPSJ6cmVhZFVzZXJO
YW1lIiBzdHlsZT0iZGlzcGxheTogaW5saW5lOyI+cGNlQGlldGYub3JnICZsdDtwY2VAaWV0Zi5v
cmcmZ3Q7Ozwvc3Bhbj48L2Rpdj48ZGl2PjxzdHJvbmcgbGFuZ3VhZ2UtZGF0YT0iSGlzdG9yeURh
dGVUeHQiPuaXpSDmnJ8g77yaPC9zdHJvbmc+PHNwYW4gY2xhc3M9IiI+MjAxOeW5tDA55pyIMjbm
l6UgMDI6MDQ8L3NwYW4+PC9kaXY+PGRpdj48c3Ryb25nIGxhbmd1YWdlLWRhdGE9Ikhpc3RvcnlT
dWJqZWN0VHh0Ij7kuLsg6aKYIO+8mjwvc3Ryb25nPjxzcGFuIGNsYXNzPSJ6cmVhZFRpdGxlIj48
c3Ryb25nPklQUiBQb2xsIG9uIGRyYWZ0LWxpLXBjZS1zci1wYXRoLXNlZ21lbnQtMDg8L3N0cm9u
Zz48L3NwYW4+PC9kaXY+PC9kaXY+PGRpdiBjbGFzcz0iemhpc3RvcnlDb250ZW50Ij48ZGl2Pjxk
aXYgZGlyPSJsdHIiPjxkaXYgY2xhc3M9ImdtYWlsX2RlZmF1bHQiIHN0eWxlPSJmb250LWZhbWls
eTp2ZXJkYW5hLHNhbnMtc2VyaWY7Zm9udC1zaXplOnNtYWxsIj48cHJlIHN0eWxlPSJ3aGl0ZS1z
cGFjZTpwcmUtd3JhcDtib3gtc2l6aW5nOmJvcmRlci1ib3g7bWFyZ2luLXRvcDowcHg7bWFyZ2lu
LWJvdHRvbToxcmVtO292ZXJmbG93OmF1dG87Y29sb3I6cmdiKDMzLDM3LDQxKTt3b3JkLWJyZWFr
Om5vcm1hbDtwYWRkaW5nOjBweCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OnZlcmRhbmEsIHNh
bnMtc2VyaWYiPkhpIEF1dGhvcnMsCgpJbiBwcmVwYXJhdGlvbiBmb3IgV29ya2luZyBHcm91cCBs
YXN0IGNhbGwgb24gdGhpcyBkcmFmdCwgSSdkIGxpa2UgYWxsCmF1dGhvcnMgYW5kIGNvbnRyaWJ1
dG9ycyB0byBjb25maXJtIG9uIHRoZSBsaXN0IHRoYXQgdGhleSBhcmUgaW4gY29tcGxpYW5jZQp3
aXRoIElFVEYgSVBSIHJ1bGVzLgoKUGxlYXNlIHJlc3BvbmQgKGNvcHlpbmcgdGhlIG1haWxpbmcg
bGlzdCkgdG8gc2F5IG9uZSBvZjoKCkkgYW0gbm90IGF3YXJlIG9mIGFueSBJUFIgYXBwbGljYWJs
ZSB0byB0aGlzIGRyYWZ0IHRoYXQgc2hvdWxkIGJlIGRpc2Nsb3NlZAppbiBhY2NvcmRhbmNlIHdp
dGggSUVURiBJUFIgcnVsZXMuCgpJIGFtIGF3YXJlIG9mIElQUiBhcHBsaWNhYmxlIHRvIHRoaXMg
ZHJhZnQsIGFuZCBpdCBoYXMgYWxyZWFkeSBiZWVuCmRpc2Nsb3NlZCB0byB0aGUgSUVURi4KCkkg
YW0gYXdhcmUgb2YgSVBSIGFwcGxpY2FibGUgdG8gdGhpcyBkcmFmdCwgYnV0IHRoYXQgaGFzIG5v
dCB5ZXQgYmVlbgpkaXNjbG9zZWQgdG8gdGhlIElFVEYuIEkgd2lsbCB3b3JrIHRvIGVuc3VyZSB0
aGF0IGl0IHdpbGwgYmUgZGlzY2xvc2VkIGluIGEKdGltZWx5IG1hbm5lci4KClRoYW5rcywKLSBI
YXJpPC9zcGFuPjwvcHJlPjwvZGl2PjwvZGl2PjwvZGl2PjwvZGl2PjwvZGl2PjwvZGl2PjwvZGl2
PjwvZGl2PjxwPjxicj48L3A+PC9kaXY+


--=====_003_next=====--

--=====_002_next=====--

--=====_001_next=====--


From nobody Wed Sep 25 19:49:13 2019
Return-Path: <kaduk@mit.edu>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BCBC120807; Wed, 25 Sep 2019 19:49:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a-4UW_AaXjkY; Wed, 25 Sep 2019 19:49:08 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E1601200EF; Wed, 25 Sep 2019 19:49:08 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x8Q2n2ed013684 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 25 Sep 2019 22:49:05 -0400
Date: Wed, 25 Sep 2019 19:49:02 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Dhruv Dhody <dhruv.ietf@gmail.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pce-stateful-pce-auto-bandwidth@ietf.org, Adrian Farrel <adrian@olddog.co.uk>, pce-chairs <pce-chairs@ietf.org>, pce@ietf.org
Message-ID: <20190926024902.GV6424@kduck.mit.edu>
References: <156874887441.17499.7855633347557404477.idtracker@ietfa.amsl.com> <CAB75xn5MUrTS43f5boMo4Kq7dfCo+YmLu1Qh_Qf-XN9hXLKsww@mail.gmail.com> <20190919202036.GA48975@kduck.mit.edu> <CAB75xn69TNsthD=KpmLFzekZ7PjOnGaj5G_RvpqucKk06XGAOw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAB75xn69TNsthD=KpmLFzekZ7PjOnGaj5G_RvpqucKk06XGAOw@mail.gmail.com>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/NIjDxC5AyjPgrYkgMSLrrPXIkQg>
Subject: Re: [Pce] Benjamin Kaduk's Discuss on draft-ietf-pce-stateful-pce-auto-bandwidth-11: (with DISCUSS and COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Sep 2019 02:49:11 -0000

On Wed, Sep 25, 2019 at 01:56:46PM +0530, Dhruv Dhody wrote:
> Hi Ben,
> 
> Thanks for the discussion.
> 
> Snipping to open points..
> 
> > > >
> > > > As a general note, I'm not sure the phrase "calculated bandwidth to be
> > > > adjusted" is a great fit for how it's currently being used.
> > > > Specifically, the "calculation" in question seems to just be taking the
> > > > maximum of a sliding window of per-timeslice average bandwidth values,
> > > > and this seems like a sufficiently small amount of computation that I'd
> > > > be comfortable describing it as a "measurement", for "measured bandwidth
> > > > as input to path calculation".  That is, this doesn't seem like it comes
> > > > close to the amount of computation involved in actually computing paths,
> > > > so I keep misreading what information is being sent where.
> > > >
> > >
> > > In an earlier version there was a feature where the PCC could report
> > > the measured value at each sample interval (it moved to another
> > > document). IMHO for the clarity in the WG, it is still better to
> > > differentiate between the raw measured value (telemetry) and the value
> > > that is currently reported which is marked as "calculated".
> >
> > Ah, in that context it makes more sense to do it this way.  Perhaps an
> > informative reference to the other document/usage and note about the
> > terminology would help, though?
> >
> 
> I have added - "Another approach would be to send the measured values
> itself to the PCE, which is considered out of scope for this
> document.". In terminology I highlighted 'measured' and 'calculated'
> in the existing terms.

Great, that should be enough to get the reader started for the specific
meanings.

> > > > Section 1
> > > >
> > > >    Over time, based on the varying traffic pattern, an LSP established
> > > >    with a certain bandwidth may require to adjust the bandwidth reserved
> > > >    in the network dynamically.  The head-end Label Switch Router (LSR)
> > > >    monitors the actual bandwidth demand of the established LSP and
> > > >    periodically computes new bandwidth.  The head-end LSR adjusts the
> > > >    bandwidth reservation of the LSP based on the computed bandwidth
> > > >    automatically.  This feature is commonly referred to as Auto-
> > > >    Bandwidth.  The Auto-Bandwidth feature is described in detail in
> > > >    Section 4 of this document.
> > > >
> > > > >From just this text, I can't tell if this is describing the mechanisms of
> > > > this document or an existing Auto-Bandwidth feature that is related to
> > > > the mechanisms of this document.
> > > >
> > >
> > > The auto-bandwidth feature without PCE exists, where the ingress does
> > > the measurement as well as path computation. This feature has been
> > > implemented long back but was not part of any standard because it was
> > > a local implementation at the ingress node and no protocol changes was
> > > required. With the PCE things changed and here we are...
> >
> > Ah, I see.  Maybe "This feature, when available in the head-end LSR
> > implementation, is common referred to as [...]", then?
> >
> 
> Updated.
> 
> 
> > > > Section 2.3
> > > >
> > > > Are we assuming any relationship between the Up-Adjustment-Threshold and
> > > > the Overflow-Threshold?
> > > >
> > >
> > > Yes, as mentioned here while describing Overflow-Threshold -
> > >
> > >       The LSP bandwidth is adjusted to the
> > >       current bandwidth demand bypassing the Up-Adjustment-Interval if
> > >       the overflow condition is met consecutively for the Overflow-
> > >       Count.
> >
> > I was thinking more along the lines of if the Overflow-Threshold value was
> > going to be a larger number than the Up-Adjustment-Threshold.
> >
> 
> Yes, I have added this in terminology section.
> Also added a note for operator to take care while setting this in section 6.1.
> 
> I prefer to keep this generic as there are multiple combinations of
> formats to deal with.

Understood.

The updates all look good; thanks!

-Ben

> > >
> > > >       traffic demand.  If the percentage or absolute difference between
> > > >       the current MaxAvgBw and the current bandwidth reservation of the
> > > >       LSP is greater than or equal to the threshold value, the overflow
> > > >       condition is set to be met.  The LSP bandwidth is adjusted to the
> > > >
> > > > nit: I think s/set to be met/said to be met/ ?  (this appears twice)
> > > >
> > >
> > > Ack
> > >
> > > >    Minimum-Threshold:  The increase or decrease of the LSP bandwidth
> > > >       should be at least or above the minimum-threshold represented as
> > > >       an absolute bandwidth value before the bandwidth adjustment for
> > > >       the LSP is made.  This threshold can be seen as a suppression
> > > >       threshold that is used along with a percentage threshold to avoid
> > > >       unnecessary auto-bandwidth adjustments and re-signaling of the LSP
> > > >       at low bandwidth values.
> > > >
> > > > I can't tell from this text if this threshold is a (LSP) bandwidth
> > > > value/measurement or a bandwidth offset between configured and measured
> > > > values.  (The subsequent protocol element definitions are more clear
> > > > that it's the latter.)
> > > >
> > >
> > > It is latter. Do you have a suggested change, I am not sure what change to make.
> >
> > How about:
> >
> >    Minimum-Threshold:  When percentage-based thresholds are in use, they
> >       are accompanied by this minimum threshold, which is used to enforce
> >       that the magnitude of deviation of calculated LSP bandwidth from the
> >       reserved bandwidth exceeds a specific non-percentage-based criterion
> >       before any adjustments are made.  This serves to suppress unnecessary
> >       auto-bandwidth adjustments and re-signaling of the LSP at low
> >       bandwidth values.
> >
> >
> 
> Thanks for the text. Updated with minor changes.
> 
> > > > Section 4.2
> > > >
> > > >    When the Auto-Bandwidth feature is enabled, the measured traffic rate
> > > >    is periodically sampled at each Sample-Interval (which can be
> > > >    configured by an operator and the default value as 5 minutes) by the
> > > >    PCC, when the PCC is the head-end node of the LSP.  The traffic rate
> > > >
> > > > Do we cover what happens in the case when the PCC is not the head-end
> > > > node of the LSP?
> > > >
> > >
> > > No.
> >
> > Should we document that somewhere?
> >
> 
> Added.
> 
> Diff: https://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=draft-ietf-pce-stateful-pce-auto-bandwidth-11&url2=https://raw.githubusercontent.com/dhruvdhody/ietf/master/draft-ietf-pce-stateful-pce-auto-bandwidth-12.txt
> 
> Working Copy: https://raw.githubusercontent.com/dhruvdhody/ietf/master/draft-ietf-pce-stateful-pce-auto-bandwidth-12.txt
> 
> Thanks!
> Dhruv


From nobody Wed Sep 25 20:08:42 2019
Return-Path: <mach.chen@huawei.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F3E21200EF for <pce@ietfa.amsl.com>; Wed, 25 Sep 2019 20:08:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LVSxrO5fvwWL for <pce@ietfa.amsl.com>; Wed, 25 Sep 2019 20:08:37 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3BB531200D5 for <pce@ietf.org>; Wed, 25 Sep 2019 20:08:37 -0700 (PDT)
Received: from lhreml705-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id BB01416DD497E1C9C2B0 for <pce@ietf.org>; Thu, 26 Sep 2019 04:08:34 +0100 (IST)
Received: from lhreml719-chm.china.huawei.com (10.201.108.70) by lhreml705-cah.china.huawei.com (10.201.108.46) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 26 Sep 2019 04:08:34 +0100
Received: from lhreml719-chm.china.huawei.com (10.201.108.70) by lhreml719-chm.china.huawei.com (10.201.108.70) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Thu, 26 Sep 2019 04:08:34 +0100
Received: from DGGEML403-HUB.china.huawei.com (10.3.17.33) by lhreml719-chm.china.huawei.com (10.201.108.70) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1713.5 via Frontend Transport; Thu, 26 Sep 2019 04:08:34 +0100
Received: from DGGEML510-MBX.china.huawei.com ([169.254.2.152]) by DGGEML403-HUB.china.huawei.com ([fe80::74d9:c659:fbec:21fa%31]) with mapi id 14.03.0439.000; Thu, 26 Sep 2019 11:08:23 +0800
From: Mach Chen <mach.chen@huawei.com>
To: Hariharan Ananthakrishnan <hari@netflix.com>, "Chengli (Cheng Li)" <chengli13@huawei.com>, "chengweiqiang@chinamobile.com" <chengweiqiang@chinamobile.com>, "Dongjie (Jimmy)" <jie.dong@huawei.com>, Lizhenbin <lizhenbin@huawei.com>, "rgandhi@cisco.com" <rgandhi@cisco.com>, "xiong.quan@zte.com.cn" <xiong.quan@zte.com.cn>
CC: "pce@ietf.org" <pce@ietf.org>
Thread-Topic: IPR Poll on draft-li-pce-sr-path-segment-08
Thread-Index: AQHVc8mdEMPBaJOws02e5QW/CLh4W6c9R1VA
Date: Thu, 26 Sep 2019 03:08:22 +0000
Message-ID: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE292CCD23F@dggeml510-mbx.china.huawei.com>
References: <CAL70W4q8DctbRNTFMWzKELNZORgL5OuStFJgFOx1tw9tq3+jGA@mail.gmail.com>
In-Reply-To: <CAL70W4q8DctbRNTFMWzKELNZORgL5OuStFJgFOx1tw9tq3+jGA@mail.gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.194.201]
Content-Type: multipart/alternative; boundary="_000_F73A3CB31E8BE34FA1BBE3C8F0CB2AE292CCD23Fdggeml510mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/RWnUQPQjen_4osgCUjr3S8VD8sM>
Subject: Re: [Pce] IPR Poll on draft-li-pce-sr-path-segment-08
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Sep 2019 03:08:40 -0000

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

SGksDQoNCg0KSSBhbSBub3QgYXdhcmUgb2YgYW55IElQUiBhcHBsaWNhYmxlIHRvIHRoaXMgZHJh
ZnQgdGhhdCBzaG91bGQgYmUgZGlzY2xvc2VkIGluIGFjY29yZGFuY2Ugd2l0aCBJRVRGIElQUiBy
dWxlcy4NCg0KDQoNCkJlc3QgcmVnYXJkcywNCg0KTWFjaA0KDQoNCkZyb206IEhhcmloYXJhbiBB
bmFudGhha3Jpc2huYW4gW21haWx0bzpoYXJpQG5ldGZsaXguY29tXQ0KU2VudDogVGh1cnNkYXks
IFNlcHRlbWJlciAyNiwgMjAxOSAxOjQ5IEFNDQpUbzogQ2hlbmdsaSAoQ2hlbmcgTGkpIDxjaGVu
Z2xpMTNAaHVhd2VpLmNvbT47IE1hY2ggQ2hlbiA8bWFjaC5jaGVuQGh1YXdlaS5jb20+OyBjaGVu
Z3dlaXFpYW5nQGNoaW5hbW9iaWxlLmNvbTsgRG9uZ2ppZSAoSmltbXkpIDxqaWUuZG9uZ0BodWF3
ZWkuY29tPjsgTGl6aGVuYmluIDxsaXpoZW5iaW5AaHVhd2VpLmNvbT47IHJnYW5kaGlAY2lzY28u
Y29tOyB4aW9uZy5xdWFuQHp0ZS5jb20uY24NCkNjOiBwY2VAaWV0Zi5vcmcNClN1YmplY3Q6IElQ
UiBQb2xsIG9uIGRyYWZ0LWxpLXBjZS1zci1wYXRoLXNlZ21lbnQtMDgNCg0KDQpIaSBBdXRob3Jz
LA0KDQoNCg0KSW4gcHJlcGFyYXRpb24gZm9yIFdvcmtpbmcgR3JvdXAgbGFzdCBjYWxsIG9uIHRo
aXMgZHJhZnQsIEknZCBsaWtlIGFsbA0KDQphdXRob3JzIGFuZCBjb250cmlidXRvcnMgdG8gY29u
ZmlybSBvbiB0aGUgbGlzdCB0aGF0IHRoZXkgYXJlIGluIGNvbXBsaWFuY2UNCg0Kd2l0aCBJRVRG
IElQUiBydWxlcy4NCg0KDQoNClBsZWFzZSByZXNwb25kIChjb3B5aW5nIHRoZSBtYWlsaW5nIGxp
c3QpIHRvIHNheSBvbmUgb2Y6DQoNCg0KDQpJIGFtIG5vdCBhd2FyZSBvZiBhbnkgSVBSIGFwcGxp
Y2FibGUgdG8gdGhpcyBkcmFmdCB0aGF0IHNob3VsZCBiZSBkaXNjbG9zZWQNCg0KaW4gYWNjb3Jk
YW5jZSB3aXRoIElFVEYgSVBSIHJ1bGVzLg0KDQoNCg0KSSBhbSBhd2FyZSBvZiBJUFIgYXBwbGlj
YWJsZSB0byB0aGlzIGRyYWZ0LCBhbmQgaXQgaGFzIGFscmVhZHkgYmVlbg0KDQpkaXNjbG9zZWQg
dG8gdGhlIElFVEYuDQoNCg0KDQpJIGFtIGF3YXJlIG9mIElQUiBhcHBsaWNhYmxlIHRvIHRoaXMg
ZHJhZnQsIGJ1dCB0aGF0IGhhcyBub3QgeWV0IGJlZW4NCg0KZGlzY2xvc2VkIHRvIHRoZSBJRVRG
LiBJIHdpbGwgd29yayB0byBlbnN1cmUgdGhhdCBpdCB3aWxsIGJlIGRpc2Nsb3NlZCBpbiBhDQoN
CnRpbWVseSBtYW5uZXIuDQoNCg0KDQpUaGFua3MsDQoNCi0gSGFyaQ0K

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
5a6L5L2TOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtm
b250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0
O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUg
MiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJcQOWui+S9kyI7DQoJ
cGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5
OkNvbnNvbGFzOw0KCXBhbm9zZS0xOjIgMTEgNiA5IDIgMiA0IDMgMiA0O30NCkBmb250LWZhY2UN
Cgl7Zm9udC1mYW1pbHk6VmVyZGFuYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9
DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2
Lk1zb05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250
LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLHNlcmlmO30NCmE6
bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9y
OiMwNTYzQzE7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4u
TXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOiM5
NTRGNzI7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwcmUNCgl7bXNvLXN0eWxlLXBy
aW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJIVE1MIOmihOiuvuagvOW8jyBDaGFyIjsNCglt
YXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTAuMHB0Ow0K
CWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0Kc3Bhbi5IVE1MQ2hhcg0KCXttc28tc3R5bGUt
bmFtZToiSFRNTCDpooTorr7moLzlvI8gQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0K
CW1zby1zdHlsZS1saW5rOiJIVE1MIOmihOiuvuagvOW8jyI7DQoJZm9udC1mYW1pbHk6Q29uc29s
YXM7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTkNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7
DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6IzFGNDk3RDt9DQou
TXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LWZhbWls
eToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo2MTIu
MHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA5MC4wcHQgNzIuMHB0IDkwLjBwdDt9DQpkaXYu
V29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBn
dGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIx
MDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpz
aGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIg
Lz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxh
bmc9IkVOLVVTIiBsaW5rPSIjMDU2M0MxIiB2bGluaz0iIzk1NEY3MiI+DQo8ZGl2IGNsYXNzPSJX
b3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGZvbnQgc2l6ZT0iMiIgY29sb3I9
IiMxZjQ5N2QiIGZhY2U9IkNhbGlicmkiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj5I
aSw8bzpwPjwvbzpwPjwvc3Bhbj48L2ZvbnQ+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGZv
bnQgc2l6ZT0iMiIgY29sb3I9IiMxZjQ5N2QiIGZhY2U9IkNhbGlicmkiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJp
Zjtjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L2ZvbnQ+PC9wPg0KPHBy
ZT48Zm9udCBzaXplPSIyIiBjb2xvcj0iIzFmNDk3ZCIgZmFjZT0iQ2FsaWJyaSI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5z
LXNlcmlmO2NvbG9yOiMxRjQ5N0QiPkkgYW0gbm90IGF3YXJlIG9mIGFueSBJUFIgYXBwbGljYWJs
ZSB0byB0aGlzIGRyYWZ0IHRoYXQgc2hvdWxkIGJlIGRpc2Nsb3NlZCBpbiBhY2NvcmRhbmNlIHdp
dGggSUVURiBJUFIgcnVsZXMuPG86cD48L286cD48L3NwYW4+PC9mb250PjwvcHJlPg0KPHByZT48
Zm9udCBzaXplPSIyIiBjb2xvcj0iIzFmNDk3ZCIgZmFjZT0iQ2FsaWJyaSI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNl
cmlmO2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvZm9udD48L3ByZT4N
CjxwcmU+PGZvbnQgc2l6ZT0iMiIgY29sb3I9IiMxZjQ5N2QiIGZhY2U9IkNhbGlicmkiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
c2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj5CZXN0IHJlZ2FyZHMsPG86cD48L286cD48L3NwYW4+
PC9mb250PjwvcHJlPg0KPHByZT48Zm9udCBzaXplPSIyIiBjb2xvcj0iIzFmNDk3ZCIgZmFjZT0i
Q2FsaWJyaSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPk1hY2g8bzpwPjwvbzpwPjwv
c3Bhbj48L2ZvbnQ+PC9wcmU+DQo8cHJlPjxmb250IHNpemU9IjIiIGNvbG9yPSIjMWY0OTdkIiBm
YWNlPSJDYWxpYnJpIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8
L286cD48L3NwYW4+PC9mb250PjwvcHJlPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVy
LWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDQuMHB0Ij4NCjxkaXY+
DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNFMUUxRTEgMS4wcHQ7
cGFkZGluZzozLjBwdCAwY20gMGNtIDBjbSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48Zm9u
dCBzaXplPSIyIiBmYWNlPSJDYWxpYnJpIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtm
b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Zm9udC13ZWlnaHQ6Ym9s
ZCI+RnJvbTo8L3NwYW4+PC9mb250PjwvYj48Zm9udCBzaXplPSIyIiBmYWNlPSJDYWxpYnJpIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1
b3Q7LHNhbnMtc2VyaWYiPiBIYXJpaGFyYW4NCiBBbmFudGhha3Jpc2huYW4gW21haWx0bzpoYXJp
QG5ldGZsaXguY29tXSA8YnI+DQo8Yj48c3BhbiBzdHlsZT0iZm9udC13ZWlnaHQ6Ym9sZCI+U2Vu
dDo8L3NwYW4+PC9iPiBUaHVyc2RheSwgU2VwdGVtYmVyIDI2LCAyMDE5IDE6NDkgQU08YnI+DQo8
Yj48c3BhbiBzdHlsZT0iZm9udC13ZWlnaHQ6Ym9sZCI+VG86PC9zcGFuPjwvYj4gQ2hlbmdsaSAo
Q2hlbmcgTGkpICZsdDtjaGVuZ2xpMTNAaHVhd2VpLmNvbSZndDs7IE1hY2ggQ2hlbiAmbHQ7bWFj
aC5jaGVuQGh1YXdlaS5jb20mZ3Q7OyBjaGVuZ3dlaXFpYW5nQGNoaW5hbW9iaWxlLmNvbTsgRG9u
Z2ppZSAoSmltbXkpICZsdDtqaWUuZG9uZ0BodWF3ZWkuY29tJmd0OzsgTGl6aGVuYmluICZsdDts
aXpoZW5iaW5AaHVhd2VpLmNvbSZndDs7IHJnYW5kaGlAY2lzY28uY29tOyB4aW9uZy5xdWFuQHp0
ZS5jb20uY248YnI+DQo8Yj48c3BhbiBzdHlsZT0iZm9udC13ZWlnaHQ6Ym9sZCI+Q2M6PC9zcGFu
PjwvYj4gcGNlQGlldGYub3JnPGJyPg0KPGI+PHNwYW4gc3R5bGU9ImZvbnQtd2VpZ2h0OmJvbGQi
PlN1YmplY3Q6PC9zcGFuPjwvYj4gSVBSIFBvbGwgb24gZHJhZnQtbGktcGNlLXNyLXBhdGgtc2Vn
bWVudC0wODxvOnA+PC9vOnA+PC9zcGFuPjwvZm9udD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PGZvbnQgc2l6ZT0iMyIgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9m
b250PjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHByZT48Zm9udCBzaXplPSIyIiBjb2xvcj0iIzIxMjUy
OSIgZmFjZT0iVmVyZGFuYSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7VmVyZGFuYSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMyMTI1MjkiPkhpIEF1dGhv
cnMsPG86cD48L286cD48L3NwYW4+PC9mb250PjwvcHJlPg0KPHByZT48Zm9udCBzaXplPSIyIiBj
b2xvcj0iIzIxMjUyOSIgZmFjZT0iVmVyZGFuYSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMyMTI1
MjkiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvZm9udD48L3ByZT4NCjxwcmU+PGZvbnQgc2l6
ZT0iMiIgY29sb3I9IiMyMTI1MjkiIGZhY2U9IlZlcmRhbmEiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssc2Fucy1zZXJpZjtjb2xv
cjojMjEyNTI5Ij5JbiBwcmVwYXJhdGlvbiBmb3IgV29ya2luZyBHcm91cCBsYXN0IGNhbGwgb24g
dGhpcyBkcmFmdCwgSSdkIGxpa2UgYWxsPG86cD48L286cD48L3NwYW4+PC9mb250PjwvcHJlPg0K
PHByZT48Zm9udCBzaXplPSIyIiBjb2xvcj0iIzIxMjUyOSIgZmFjZT0iVmVyZGFuYSI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZxdW90Oyxz
YW5zLXNlcmlmO2NvbG9yOiMyMTI1MjkiPmF1dGhvcnMgYW5kIGNvbnRyaWJ1dG9ycyB0byBjb25m
aXJtIG9uIHRoZSBsaXN0IHRoYXQgdGhleSBhcmUgaW4gY29tcGxpYW5jZTxvOnA+PC9vOnA+PC9z
cGFuPjwvZm9udD48L3ByZT4NCjxwcmU+PGZvbnQgc2l6ZT0iMiIgY29sb3I9IiMyMTI1MjkiIGZh
Y2U9IlZlcmRhbmEiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O1ZlcmRhbmEmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMjEyNTI5Ij53aXRoIElFVEYgSVBS
IHJ1bGVzLjxvOnA+PC9vOnA+PC9zcGFuPjwvZm9udD48L3ByZT4NCjxwcmU+PGZvbnQgc2l6ZT0i
MiIgY29sb3I9IiMyMTI1MjkiIGZhY2U9IlZlcmRhbmEiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjoj
MjEyNTI5Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L2ZvbnQ+PC9wcmU+DQo8cHJlPjxmb250
IHNpemU9IjIiIGNvbG9yPSIjMjEyNTI5IiBmYWNlPSJWZXJkYW5hIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7LHNhbnMtc2VyaWY7
Y29sb3I6IzIxMjUyOSI+UGxlYXNlIHJlc3BvbmQgKGNvcHlpbmcgdGhlIG1haWxpbmcgbGlzdCkg
dG8gc2F5IG9uZSBvZjo8bzpwPjwvbzpwPjwvc3Bhbj48L2ZvbnQ+PC9wcmU+DQo8cHJlPjxmb250
IHNpemU9IjIiIGNvbG9yPSIjMjEyNTI5IiBmYWNlPSJWZXJkYW5hIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7LHNhbnMtc2VyaWY7
Y29sb3I6IzIxMjUyOSI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9mb250PjwvcHJlPg0KPHBy
ZT48Zm9udCBzaXplPSIyIiBjb2xvcj0iIzIxMjUyOSIgZmFjZT0iVmVyZGFuYSI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZxdW90OyxzYW5z
LXNlcmlmO2NvbG9yOiMyMTI1MjkiPkkgYW0gbm90IGF3YXJlIG9mIGFueSBJUFIgYXBwbGljYWJs
ZSB0byB0aGlzIGRyYWZ0IHRoYXQgc2hvdWxkIGJlIGRpc2Nsb3NlZDxvOnA+PC9vOnA+PC9zcGFu
PjwvZm9udD48L3ByZT4NCjxwcmU+PGZvbnQgc2l6ZT0iMiIgY29sb3I9IiMyMTI1MjkiIGZhY2U9
IlZlcmRhbmEiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O1ZlcmRhbmEmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMjEyNTI5Ij5pbiBhY2NvcmRhbmNlIHdp
dGggSUVURiBJUFIgcnVsZXMuPG86cD48L286cD48L3NwYW4+PC9mb250PjwvcHJlPg0KPHByZT48
Zm9udCBzaXplPSIyIiBjb2xvcj0iIzIxMjUyOSIgZmFjZT0iVmVyZGFuYSI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZxdW90OyxzYW5zLXNl
cmlmO2NvbG9yOiMyMTI1MjkiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvZm9udD48L3ByZT4N
CjxwcmU+PGZvbnQgc2l6ZT0iMiIgY29sb3I9IiMyMTI1MjkiIGZhY2U9IlZlcmRhbmEiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDss
c2Fucy1zZXJpZjtjb2xvcjojMjEyNTI5Ij5JIGFtIGF3YXJlIG9mIElQUiBhcHBsaWNhYmxlIHRv
IHRoaXMgZHJhZnQsIGFuZCBpdCBoYXMgYWxyZWFkeSBiZWVuPG86cD48L286cD48L3NwYW4+PC9m
b250PjwvcHJlPg0KPHByZT48Zm9udCBzaXplPSIyIiBjb2xvcj0iIzIxMjUyOSIgZmFjZT0iVmVy
ZGFuYSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VmVy
ZGFuYSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMyMTI1MjkiPmRpc2Nsb3NlZCB0byB0aGUgSUVU
Ri48bzpwPjwvbzpwPjwvc3Bhbj48L2ZvbnQ+PC9wcmU+DQo8cHJlPjxmb250IHNpemU9IjIiIGNv
bG9yPSIjMjEyNTI5IiBmYWNlPSJWZXJkYW5hIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBw
dDtmb250LWZhbWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzIxMjUy
OSI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9mb250PjwvcHJlPg0KPHByZT48Zm9udCBzaXpl
PSIyIiBjb2xvcj0iIzIxMjUyOSIgZmFjZT0iVmVyZGFuYSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZxdW90OyxzYW5zLXNlcmlmO2NvbG9y
OiMyMTI1MjkiPkkgYW0gYXdhcmUgb2YgSVBSIGFwcGxpY2FibGUgdG8gdGhpcyBkcmFmdCwgYnV0
IHRoYXQgaGFzIG5vdCB5ZXQgYmVlbjxvOnA+PC9vOnA+PC9zcGFuPjwvZm9udD48L3ByZT4NCjxw
cmU+PGZvbnQgc2l6ZT0iMiIgY29sb3I9IiMyMTI1MjkiIGZhY2U9IlZlcmRhbmEiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssc2Fu
cy1zZXJpZjtjb2xvcjojMjEyNTI5Ij5kaXNjbG9zZWQgdG8gdGhlIElFVEYuIEkgd2lsbCB3b3Jr
IHRvIGVuc3VyZSB0aGF0IGl0IHdpbGwgYmUgZGlzY2xvc2VkIGluIGE8bzpwPjwvbzpwPjwvc3Bh
bj48L2ZvbnQ+PC9wcmU+DQo8cHJlPjxmb250IHNpemU9IjIiIGNvbG9yPSIjMjEyNTI5IiBmYWNl
PSJWZXJkYW5hIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVv
dDtWZXJkYW5hJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzIxMjUyOSI+dGltZWx5IG1hbm5lci48
bzpwPjwvbzpwPjwvc3Bhbj48L2ZvbnQ+PC9wcmU+DQo8cHJlPjxmb250IHNpemU9IjIiIGNvbG9y
PSIjMjEyNTI5IiBmYWNlPSJWZXJkYW5hIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtm
b250LWZhbWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzIxMjUyOSI+
PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9mb250PjwvcHJlPg0KPHByZT48Zm9udCBzaXplPSIy
IiBjb2xvcj0iIzIxMjUyOSIgZmFjZT0iVmVyZGFuYSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMy
MTI1MjkiPlRoYW5rcyw8bzpwPjwvbzpwPjwvc3Bhbj48L2ZvbnQ+PC9wcmU+DQo8cHJlPjxmb250
IHNpemU9IjIiIGNvbG9yPSIjMjEyNTI5IiBmYWNlPSJWZXJkYW5hIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7LHNhbnMtc2VyaWY7
Y29sb3I6IzIxMjUyOSI+LSBIYXJpPC9zcGFuPjwvZm9udD48Zm9udCBjb2xvcj0iIzIxMjUyOSI+
PHNwYW4gc3R5bGU9ImNvbG9yOiMyMTI1MjkiPjxvOnA+PC9vOnA+PC9zcGFuPjwvZm9udD48L3By
ZT4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_F73A3CB31E8BE34FA1BBE3C8F0CB2AE292CCD23Fdggeml510mbxchi_--


From nobody Wed Sep 25 20:39:32 2019
Return-Path: <chengli13@huawei.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23A281200EF for <pce@ietfa.amsl.com>; Wed, 25 Sep 2019 20:39:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RAXhGwaoGR0B for <pce@ietfa.amsl.com>; Wed, 25 Sep 2019 20:39:29 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E6B2D1200DF for <pce@ietf.org>; Wed, 25 Sep 2019 20:39:28 -0700 (PDT)
Received: from lhreml707-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 9F65171A1D3CC1E56A7A for <pce@ietf.org>; Thu, 26 Sep 2019 04:39:26 +0100 (IST)
Received: from DGGEML424-HUB.china.huawei.com (10.1.199.41) by lhreml707-cah.china.huawei.com (10.201.108.48) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 26 Sep 2019 04:39:25 +0100
Received: from DGGEML529-MBX.china.huawei.com ([169.254.6.245]) by dggeml424-hub.china.huawei.com ([10.1.199.41]) with mapi id 14.03.0439.000; Thu, 26 Sep 2019 11:39:16 +0800
From: "Chengli (Cheng Li)" <chengli13@huawei.com>
To: "julien.meuric@orange.com" <julien.meuric@orange.com>, "pce@ietf.org" <pce@ietf.org>
Thread-Topic: [Pce] Adoption of draft-li-pce-sr-path-segment?
Thread-Index: AQHVc71hnVttO3U2WUCcBILB4fFRoKc9T24w
Date: Thu, 26 Sep 2019 03:39:16 +0000
Message-ID: <C7C2E1C43D652C4E9E49FE7517C236CB0270318E@dggeml529-mbx.china.huawei.com>
References: <29713_1569428443_5D8B93DB_29713_96_1_6698a3d9-4ace-57fd-3b7c-7be23f135631@orange.com>
In-Reply-To: <29713_1569428443_5D8B93DB_29713_96_1_6698a3d9-4ace-57fd-3b7c-7be23f135631@orange.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.130.185.75]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/TOmXmvR0vX6ap09PY2DYqJFE2vA>
Subject: Re: [Pce] Adoption of draft-li-pce-sr-path-segment?
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Sep 2019 03:39:31 -0000

Hi WG,

Support as a co-author since the text of this draft is mature and ready for=
 WG adoption.

This document is being implemented by Huawei Product, and it will be used i=
n CMCC's SPN in the future.=20

Many thanks,
Cheng



-----Original Message-----
From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of julien.meuric@orange.c=
om
Sent: Thursday, September 26, 2019 12:21 AM
To: pce@ietf.org
Subject: [Pce] Adoption of draft-li-pce-sr-path-segment?

Hi PCE WG,

In our adoption poll queue, draft-li-pce-sr-path-segment has been there for=
 a little while, after it was discussed face to face. We would now like you=
 to voice your opinion on the list: do you think this I-D can be the founda=
tion for a PCE WG's work item?

Please send your feedback to the PCE mailing list, including any comment yo=
u would like to share, especially if you think the WG should not adopt it. =
This poll will end on October 9.

Thanks,

Dhruv & Julien


___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou =
copies sans autorisation. Si vous avez recu ce message par erreur, veuillez=
 le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Le=
s messages electroniques etant susceptibles d'alteration, Orange decline to=
ute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation 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 dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.

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


From nobody Wed Sep 25 20:43:44 2019
Return-Path: <lizhenbin@huawei.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11F47120271 for <pce@ietfa.amsl.com>; Wed, 25 Sep 2019 20:43:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DWN3T7AgZRbM for <pce@ietfa.amsl.com>; Wed, 25 Sep 2019 20:43:40 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DB93120170 for <pce@ietf.org>; Wed, 25 Sep 2019 20:43:40 -0700 (PDT)
Received: from lhreml703-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 66DB7553A64AA5B93575 for <pce@ietf.org>; Thu, 26 Sep 2019 04:43:38 +0100 (IST)
Received: from lhreml709-chm.china.huawei.com (10.201.108.58) by lhreml703-cah.china.huawei.com (10.201.108.44) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 26 Sep 2019 04:43:38 +0100
Received: from lhreml709-chm.china.huawei.com (10.201.108.58) by lhreml709-chm.china.huawei.com (10.201.108.58) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Thu, 26 Sep 2019 04:43:37 +0100
Received: from DGGEMM405-HUB.china.huawei.com (10.3.20.213) by lhreml709-chm.china.huawei.com (10.201.108.58) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1713.5 via Frontend Transport; Thu, 26 Sep 2019 04:43:37 +0100
Received: from DGGEMM532-MBX.china.huawei.com ([169.254.7.3]) by DGGEMM405-HUB.china.huawei.com ([10.3.20.213]) with mapi id 14.03.0439.000; Thu, 26 Sep 2019 11:43:28 +0800
From: Lizhenbin <lizhenbin@huawei.com>
To: 'Hariharan Ananthakrishnan' <hari@netflix.com>, Mach Chen <mach.chen@huawei.com>, "Dongjie (Jimmy)" <jie.dong@huawei.com>, "rgandhi@cisco.com" <rgandhi@cisco.com>, "xiong.quan@zte.com.cn" <xiong.quan@zte.com.cn>
CC: "pce@ietf.org" <pce@ietf.org>, Weiqiang Cheng <chengweiqiang@chinamobile.com>, "Chengli (Cheng Li)" <chengli13@huawei.com>
Thread-Topic: IPR Poll on draft-li-pce-sr-path-segment-08
Thread-Index: AQHVc8mfMY5vTNngPUSRu4nOKQ/2Rqc8q56AgAAE6YCAAKDE0A==
Date: Thu, 26 Sep 2019 03:43:28 +0000
Message-ID: <5A5B4DE12C0DAC44AF501CD9A2B01A8D934D2B77@DGGEMM532-MBX.china.huawei.com>
References: <CAL70W4q8DctbRNTFMWzKELNZORgL5OuStFJgFOx1tw9tq3+jGA@mail.gmail.com> <C7C2E1C43D652C4E9E49FE7517C236CB027030F6@dggeml529-mbx.china.huawei.com> <022001d5740f$1c5658d0$55030a70$@com>
In-Reply-To: <022001d5740f$1c5658d0$55030a70$@com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.206.84]
Content-Type: multipart/alternative; boundary="_000_5A5B4DE12C0DAC44AF501CD9A2B01A8D934D2B77DGGEMM532MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/5pDhdk86BudSkUDZhK_0qpC4abk>
Subject: Re: [Pce] IPR Poll on draft-li-pce-sr-path-segment-08
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Sep 2019 03:43:43 -0000

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

SGkgSGFyaSBhbmQgV0csDQoNCkkgYW0gbm90IGF3YXJlIG9mIGFueSBJUFIgYXBwbGljYWJsZSB0
byB0aGlzIGRyYWZ0IHRoYXQgc2hvdWxkIGJlIGRpc2Nsb3NlZA0KaW4gYWNjb3JkYW5jZSB3aXRo
IElFVEYgSVBSIHJ1bGVzLg0KDQpCZXN0IFJlZ2FyZHMsDQpaaGVuYmluIChSb2JpbikNCg0KDQoN
Cg0KRnJvbTogV2VpcWlhbmcgQ2hlbmcgW21haWx0bzpjaGVuZ3dlaXFpYW5nQGNoaW5hbW9iaWxl
LmNvbV0NClNlbnQ6IFRodXJzZGF5LCBTZXB0ZW1iZXIgMjYsIDIwMTkgMTA6MDcgQU0NClRvOiBD
aGVuZ2xpIChDaGVuZyBMaSkgPGNoZW5nbGkxM0BodWF3ZWkuY29tPjsgJ0hhcmloYXJhbiBBbmFu
dGhha3Jpc2huYW4nIDxoYXJpQG5ldGZsaXguY29tPjsgTWFjaCBDaGVuIDxtYWNoLmNoZW5AaHVh
d2VpLmNvbT47IERvbmdqaWUgKEppbW15KSA8amllLmRvbmdAaHVhd2VpLmNvbT47IExpemhlbmJp
biA8bGl6aGVuYmluQGh1YXdlaS5jb20+OyByZ2FuZGhpQGNpc2NvLmNvbTsgeGlvbmcucXVhbkB6
dGUuY29tLmNuDQpDYzogcGNlQGlldGYub3JnDQpTdWJqZWN0OiDnrZTlpI06IElQUiBQb2xsIG9u
IGRyYWZ0LWxpLXBjZS1zci1wYXRoLXNlZ21lbnQtMDgNCg0KSGksDQpJIGFtIG5vdCBhd2FyZSBv
ZiBhbnkgSVBSIGFwcGxpY2FibGUgdG8gdGhlIGRyYWZ0Lg0KDQpCLlIuDQpXZWlxaWFuZyBDaGVu
Zw0KDQrlj5Hku7bkuro6IENoZW5nbGkgKENoZW5nIExpKSBbbWFpbHRvOmNoZW5nbGkxM0BodWF3
ZWkuY29tXQ0K5Y+R6YCB5pe26Ze0OiAyMDE55bm0OeaciDI25pelIDA5OjUwDQrmlLbku7bkuro6
IEhhcmloYXJhbiBBbmFudGhha3Jpc2huYW47IE1hY2ggQ2hlbjsgY2hlbmd3ZWlxaWFuZ0BjaGlu
YW1vYmlsZS5jb208bWFpbHRvOmNoZW5nd2VpcWlhbmdAY2hpbmFtb2JpbGUuY29tPjsgRG9uZ2pp
ZSAoSmltbXkpOyBMaXpoZW5iaW47IHJnYW5kaGlAY2lzY28uY29tPG1haWx0bzpyZ2FuZGhpQGNp
c2NvLmNvbT47IHhpb25nLnF1YW5AenRlLmNvbS5jbjxtYWlsdG86eGlvbmcucXVhbkB6dGUuY29t
LmNuPg0K5oqE6YCBOiBwY2VAaWV0Zi5vcmc8bWFpbHRvOnBjZUBpZXRmLm9yZz4NCuS4u+mimDog
UkU6IElQUiBQb2xsIG9uIGRyYWZ0LWxpLXBjZS1zci1wYXRoLXNlZ21lbnQtMDgNCg0KSGkgSGFy
aSBhbmQgV0csDQoNCkkgYW0gbm90IGF3YXJlIG9mIGFueSBJUFIgYXBwbGljYWJsZSB0byB0aGlz
IGRyYWZ0IHRoYXQgc2hvdWxkIGJlIGRpc2Nsb3NlZA0KaW4gYWNjb3JkYW5jZSB3aXRoIElFVEYg
SVBSIHJ1bGVzLg0KDQpDaGVuZw0KDQoNCkZyb206IEhhcmloYXJhbiBBbmFudGhha3Jpc2huYW4g
W21haWx0bzpoYXJpQG5ldGZsaXguY29tXQ0KU2VudDogVGh1cnNkYXksIFNlcHRlbWJlciAyNiwg
MjAxOSAxOjQ5IEFNDQpUbzogQ2hlbmdsaSAoQ2hlbmcgTGkpIDxjaGVuZ2xpMTNAaHVhd2VpLmNv
bTxtYWlsdG86Y2hlbmdsaTEzQGh1YXdlaS5jb20+PjsgTWFjaCBDaGVuIDxtYWNoLmNoZW5AaHVh
d2VpLmNvbTxtYWlsdG86bWFjaC5jaGVuQGh1YXdlaS5jb20+PjsgY2hlbmd3ZWlxaWFuZ0BjaGlu
YW1vYmlsZS5jb208bWFpbHRvOmNoZW5nd2VpcWlhbmdAY2hpbmFtb2JpbGUuY29tPjsgRG9uZ2pp
ZSAoSmltbXkpIDxqaWUuZG9uZ0BodWF3ZWkuY29tPG1haWx0bzpqaWUuZG9uZ0BodWF3ZWkuY29t
Pj47IExpemhlbmJpbiA8bGl6aGVuYmluQGh1YXdlaS5jb208bWFpbHRvOmxpemhlbmJpbkBodWF3
ZWkuY29tPj47IHJnYW5kaGlAY2lzY28uY29tPG1haWx0bzpyZ2FuZGhpQGNpc2NvLmNvbT47IHhp
b25nLnF1YW5AenRlLmNvbS5jbjxtYWlsdG86eGlvbmcucXVhbkB6dGUuY29tLmNuPg0KQ2M6IHBj
ZUBpZXRmLm9yZzxtYWlsdG86cGNlQGlldGYub3JnPg0KU3ViamVjdDogSVBSIFBvbGwgb24gZHJh
ZnQtbGktcGNlLXNyLXBhdGgtc2VnbWVudC0wOA0KDQoNCkhpIEF1dGhvcnMsDQoNCg0KDQpJbiBw
cmVwYXJhdGlvbiBmb3IgV29ya2luZyBHcm91cCBsYXN0IGNhbGwgb24gdGhpcyBkcmFmdCwgSSdk
IGxpa2UgYWxsDQoNCmF1dGhvcnMgYW5kIGNvbnRyaWJ1dG9ycyB0byBjb25maXJtIG9uIHRoZSBs
aXN0IHRoYXQgdGhleSBhcmUgaW4gY29tcGxpYW5jZQ0KDQp3aXRoIElFVEYgSVBSIHJ1bGVzLg0K
DQoNCg0KUGxlYXNlIHJlc3BvbmQgKGNvcHlpbmcgdGhlIG1haWxpbmcgbGlzdCkgdG8gc2F5IG9u
ZSBvZjoNCg0KDQoNCkkgYW0gbm90IGF3YXJlIG9mIGFueSBJUFIgYXBwbGljYWJsZSB0byB0aGlz
IGRyYWZ0IHRoYXQgc2hvdWxkIGJlIGRpc2Nsb3NlZA0KDQppbiBhY2NvcmRhbmNlIHdpdGggSUVU
RiBJUFIgcnVsZXMuDQoNCg0KDQpJIGFtIGF3YXJlIG9mIElQUiBhcHBsaWNhYmxlIHRvIHRoaXMg
ZHJhZnQsIGFuZCBpdCBoYXMgYWxyZWFkeSBiZWVuDQoNCmRpc2Nsb3NlZCB0byB0aGUgSUVURi4N
Cg0KDQoNCkkgYW0gYXdhcmUgb2YgSVBSIGFwcGxpY2FibGUgdG8gdGhpcyBkcmFmdCwgYnV0IHRo
YXQgaGFzIG5vdCB5ZXQgYmVlbg0KDQpkaXNjbG9zZWQgdG8gdGhlIElFVEYuIEkgd2lsbCB3b3Jr
IHRvIGVuc3VyZSB0aGF0IGl0IHdpbGwgYmUgZGlzY2xvc2VkIGluIGENCg0KdGltZWx5IG1hbm5l
ci4NCg0KDQoNClRoYW5rcywNCg0KLSBIYXJpDQo=

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
5a6L5L2TOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtm
b250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0
O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUg
MiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJcQOWui+S9kyI7DQoJ
cGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5
OkNvbnNvbGFzOw0KCXBhbm9zZS0xOjIgMTEgNiA5IDIgMiA0IDMgMiA0O30NCkBmb250LWZhY2UN
Cgl7Zm9udC1mYW1pbHk6VmVyZGFuYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9
DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2
Lk1zb05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250
LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLHNlcmlmO30NCmE6
bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9y
OiMwNTYzQzE7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4u
TXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOiM5
NTRGNzI7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwcmUNCgl7bXNvLXN0eWxlLXBy
aW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJIVE1MIOmihOiuvuagvOW8jyBDaGFyIjsNCglt
YXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTAuMHB0Ow0K
CWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0Kc3Bhbi5IVE1MQ2hhcg0KCXttc28tc3R5bGUt
bmFtZToiSFRNTCDpooTorr7moLzlvI8gQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0K
CW1zby1zdHlsZS1saW5rOiJIVE1MIOmihOiuvuagvOW8jyI7DQoJZm9udC1mYW1pbHk6Q29uc29s
YXM7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTkNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJZm9u
dC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6IzFGNDk3RDt9DQpzcGFuLkVt
YWlsU3R5bGUyMA0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglmb250LWZhbWlseToiQ2Fs
aWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjojMUY0OTdEO30NCnNwYW4uRW1haWxTdHlsZTIxDQoJ
e21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixz
YW5zLXNlcmlmOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxl
LXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlv
bjENCgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA5MC4wcHQgNzIuMHB0
IDkwLjBwdDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwv
c3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJl
ZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNv
IDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0i
ZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwv
aGVhZD4NCjxib2R5IGxhbmc9IlpILUNOIiBsaW5rPSIjMDU2M0MxIiB2bGluaz0iIzk1NEY3MiI+
DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
bGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nh
bGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj5IaSBIYXJpIGFuZCBXRyw8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1V
UyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6
IzFGNDk3RCI+SSBhbSBub3QgYXdhcmUgb2YgYW55IElQUiBhcHBsaWNhYmxlIHRvIHRoaXMgZHJh
ZnQgdGhhdCBzaG91bGQgYmUgZGlzY2xvc2VkPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdE
Ij5pbiBhY2NvcmRhbmNlIHdpdGggSUVURiBJUFIgcnVsZXMuPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xv
cjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPkJlc3QgUmVn
YXJkcyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBs
YW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPlpoZW5iaW4gKFJvYmluKTxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVT
IiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6
MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjoj
MUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVT
IiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0K
PGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0UxRTFFMSAx
LjBwdDtwYWRkaW5nOjMuMHB0IDBjbSAwY20gMGNtIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxi
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPkZyb206PC9zcGFuPjwvYj48c3BhbiBsYW5n
PSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJy
aSZxdW90OyxzYW5zLXNlcmlmIj4gV2VpcWlhbmcgQ2hlbmcgW21haWx0bzpjaGVuZ3dlaXFpYW5n
QGNoaW5hbW9iaWxlLmNvbV0NCjxicj4NCjxiPlNlbnQ6PC9iPiBUaHVyc2RheSwgU2VwdGVtYmVy
IDI2LCAyMDE5IDEwOjA3IEFNPGJyPg0KPGI+VG86PC9iPiBDaGVuZ2xpIChDaGVuZyBMaSkgJmx0
O2NoZW5nbGkxM0BodWF3ZWkuY29tJmd0OzsgJ0hhcmloYXJhbiBBbmFudGhha3Jpc2huYW4nICZs
dDtoYXJpQG5ldGZsaXguY29tJmd0OzsgTWFjaCBDaGVuICZsdDttYWNoLmNoZW5AaHVhd2VpLmNv
bSZndDs7IERvbmdqaWUgKEppbW15KSAmbHQ7amllLmRvbmdAaHVhd2VpLmNvbSZndDs7IExpemhl
bmJpbiAmbHQ7bGl6aGVuYmluQGh1YXdlaS5jb20mZ3Q7OyByZ2FuZGhpQGNpc2NvLmNvbTsgeGlv
bmcucXVhbkB6dGUuY29tLmNuPGJyPg0KPGI+Q2M6PC9iPiBwY2VAaWV0Zi5vcmc8YnI+DQo8Yj5T
dWJqZWN0OjwvYj4gPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OuWui+S9kyI+562U5aSNPC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1z
aXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPjog
SVBSIFBvbGwgb24gZHJhZnQtbGktcGNlLXNyLXBhdGgtc2VnbWVudC0wODxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5n
PSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj5IaSw8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIg
c3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90Oyxz
YW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPkkgYW0gbm90IGF3YXJlIG9mIGFueSBJUFIgYXBwbGlj
YWJsZSB0byB0aGUgZHJhZnQuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJF
Ti1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPkIuUi48bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6
ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9y
OiMxRjQ5N0QiPldlaXFpYW5nIENoZW5nPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj48
bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5v
bmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGNtIDBjbSAw
Y20iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4w
cHQ7Zm9udC1mYW1pbHk65a6L5L2TIj7lj5Hku7bkuro8c3BhbiBsYW5nPSJFTi1VUyI+Ojwvc3Bh
bj48L3NwYW4+PC9iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtm
b250LWZhbWlseTrlrovkvZMiPiBDaGVuZ2xpIChDaGVuZyBMaSkgWzxhIGhyZWY9Im1haWx0bzpj
aGVuZ2xpMTNAaHVhd2VpLmNvbSI+bWFpbHRvOmNoZW5nbGkxM0BodWF3ZWkuY29tPC9hPl0NCjxi
cj4NCjwvc3Bhbj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTrl
rovkvZMiPuWPkemAgeaXtumXtDxzcGFuIGxhbmc9IkVOLVVTIj46PC9zcGFuPjwvc3Bhbj48L2I+
PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OuWu
i+S9kyI+IDIwMTk8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1p
bHk65a6L5L2TIj7lubQ8c3BhbiBsYW5nPSJFTi1VUyI+OTwvc3Bhbj7mnIg8c3BhbiBsYW5nPSJF
Ti1VUyI+MjY8L3NwYW4+5pelPHNwYW4gbGFuZz0iRU4tVVMiPg0KIDA5OjUwPGJyPg0KPC9zcGFu
PjxiPuaUtuS7tuS6ujxzcGFuIGxhbmc9IkVOLVVTIj46PC9zcGFuPjwvYj48c3BhbiBsYW5nPSJF
Ti1VUyI+IEhhcmloYXJhbiBBbmFudGhha3Jpc2huYW47IE1hY2ggQ2hlbjsNCjxhIGhyZWY9Im1h
aWx0bzpjaGVuZ3dlaXFpYW5nQGNoaW5hbW9iaWxlLmNvbSI+Y2hlbmd3ZWlxaWFuZ0BjaGluYW1v
YmlsZS5jb208L2E+OyBEb25namllIChKaW1teSk7IExpemhlbmJpbjsNCjxhIGhyZWY9Im1haWx0
bzpyZ2FuZGhpQGNpc2NvLmNvbSI+cmdhbmRoaUBjaXNjby5jb208L2E+OyA8YSBocmVmPSJtYWls
dG86eGlvbmcucXVhbkB6dGUuY29tLmNuIj4NCnhpb25nLnF1YW5AenRlLmNvbS5jbjwvYT48YnI+
DQo8L3NwYW4+PGI+5oqE6YCBPHNwYW4gbGFuZz0iRU4tVVMiPjo8L3NwYW4+PC9iPjxzcGFuIGxh
bmc9IkVOLVVTIj4gPGEgaHJlZj0ibWFpbHRvOnBjZUBpZXRmLm9yZyI+DQpwY2VAaWV0Zi5vcmc8
L2E+PGJyPg0KPC9zcGFuPjxiPuS4u+mimDxzcGFuIGxhbmc9IkVOLVVTIj46PC9zcGFuPjwvYj48
c3BhbiBsYW5nPSJFTi1VUyI+IFJFOiBJUFIgUG9sbCBvbiBkcmFmdC1saS1wY2Utc3ItcGF0aC1z
ZWdtZW50LTA4PG86cD48L286cD48L3NwYW4+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1z
ZXJpZjtjb2xvcjojMUY0OTdEIj5IaSBIYXJpIGFuZCBXRyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6
ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9y
OiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls
eTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+SSBhbSBub3Qg
YXdhcmUgb2YgYW55IElQUiBhcHBsaWNhYmxlIHRvIHRoaXMgZHJhZnQgdGhhdCBzaG91bGQgYmUg
ZGlzY2xvc2VkPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj5pbiBhY2NvcmRhbmNlIHdp
dGggSUVURiBJUFIgcnVsZXMuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJF
Ti1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPkNoZW5nPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xv
cjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIGxhbmc9
IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LHNhbnMtc2VyaWYiPkZyb206PC9zcGFuPjwvYj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5
bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5z
LXNlcmlmIj4gSGFyaWhhcmFuIEFuYW50aGFrcmlzaG5hbiBbPGEgaHJlZj0ibWFpbHRvOmhhcmlA
bmV0ZmxpeC5jb20iPm1haWx0bzpoYXJpQG5ldGZsaXguY29tPC9hPl0NCjxicj4NCjxiPlNlbnQ6
PC9iPiBUaHVyc2RheSwgU2VwdGVtYmVyIDI2LCAyMDE5IDE6NDkgQU08YnI+DQo8Yj5Ubzo8L2I+
IENoZW5nbGkgKENoZW5nIExpKSAmbHQ7PGEgaHJlZj0ibWFpbHRvOmNoZW5nbGkxM0BodWF3ZWku
Y29tIj5jaGVuZ2xpMTNAaHVhd2VpLmNvbTwvYT4mZ3Q7OyBNYWNoIENoZW4gJmx0OzxhIGhyZWY9
Im1haWx0bzptYWNoLmNoZW5AaHVhd2VpLmNvbSI+bWFjaC5jaGVuQGh1YXdlaS5jb208L2E+Jmd0
OzsNCjxhIGhyZWY9Im1haWx0bzpjaGVuZ3dlaXFpYW5nQGNoaW5hbW9iaWxlLmNvbSI+Y2hlbmd3
ZWlxaWFuZ0BjaGluYW1vYmlsZS5jb208L2E+OyBEb25namllIChKaW1teSkgJmx0OzxhIGhyZWY9
Im1haWx0bzpqaWUuZG9uZ0BodWF3ZWkuY29tIj5qaWUuZG9uZ0BodWF3ZWkuY29tPC9hPiZndDs7
IExpemhlbmJpbiAmbHQ7PGEgaHJlZj0ibWFpbHRvOmxpemhlbmJpbkBodWF3ZWkuY29tIj5saXpo
ZW5iaW5AaHVhd2VpLmNvbTwvYT4mZ3Q7Ow0KPGEgaHJlZj0ibWFpbHRvOnJnYW5kaGlAY2lzY28u
Y29tIj5yZ2FuZGhpQGNpc2NvLmNvbTwvYT47IDxhIGhyZWY9Im1haWx0bzp4aW9uZy5xdWFuQHp0
ZS5jb20uY24iPg0KeGlvbmcucXVhbkB6dGUuY29tLmNuPC9hPjxicj4NCjxiPkNjOjwvYj4gPGEg
aHJlZj0ibWFpbHRvOnBjZUBpZXRmLm9yZyI+cGNlQGlldGYub3JnPC9hPjxicj4NCjxiPlN1Ympl
Y3Q6PC9iPiBJUFIgUG9sbCBvbiBkcmFmdC1saS1wY2Utc3ItcGF0aC1zZWdtZW50LTA4PG86cD48
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHByZT48c3BhbiBs
YW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssc2Fucy1z
ZXJpZjtjb2xvcjojMjEyNTI5Ij5IaSBBdXRob3JzLDxvOnA+PC9vOnA+PC9zcGFuPjwvcHJlPg0K
PHByZT48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEm
cXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMjEyNTI5Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3ByZT4NCjxwcmU+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtW
ZXJkYW5hJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzIxMjUyOSI+SW4gcHJlcGFyYXRpb24gZm9y
IFdvcmtpbmcgR3JvdXAgbGFzdCBjYWxsIG9uIHRoaXMgZHJhZnQsIEknZCBsaWtlIGFsbDxvOnA+
PC9vOnA+PC9zcGFuPjwvcHJlPg0KPHByZT48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQt
ZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMjEyNTI5Ij5hdXRo
b3JzIGFuZCBjb250cmlidXRvcnMgdG8gY29uZmlybSBvbiB0aGUgbGlzdCB0aGF0IHRoZXkgYXJl
IGluIGNvbXBsaWFuY2U8bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4gbGFuZz0i
RU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7LHNhbnMtc2VyaWY7
Y29sb3I6IzIxMjUyOSI+d2l0aCBJRVRGIElQUiBydWxlcy48bzpwPjwvbzpwPjwvc3Bhbj48L3By
ZT4NCjxwcmU+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtWZXJk
YW5hJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzIxMjUyOSI+PG86cD4mbmJzcDs8L286cD48L3Nw
YW4+PC9wcmU+DQo8cHJlPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1
b3Q7VmVyZGFuYSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMyMTI1MjkiPlBsZWFzZSByZXNwb25k
IChjb3B5aW5nIHRoZSBtYWlsaW5nIGxpc3QpIHRvIHNheSBvbmUgb2Y6PG86cD48L286cD48L3Nw
YW4+PC9wcmU+DQo8cHJlPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1
b3Q7VmVyZGFuYSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMyMTI1MjkiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcHJlPg0KPHByZT48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtZmFt
aWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMjEyNTI5Ij5JIGFtIG5v
dCBhd2FyZSBvZiBhbnkgSVBSIGFwcGxpY2FibGUgdG8gdGhpcyBkcmFmdCB0aGF0IHNob3VsZCBi
ZSBkaXNjbG9zZWQ8bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7LHNhbnMtc2VyaWY7Y29s
b3I6IzIxMjUyOSI+aW4gYWNjb3JkYW5jZSB3aXRoIElFVEYgSVBSIHJ1bGVzLjxvOnA+PC9vOnA+
PC9zcGFuPjwvcHJlPg0KPHByZT48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtZmFtaWx5
OiZxdW90O1ZlcmRhbmEmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMjEyNTI5Ij48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250
LWZhbWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzIxMjUyOSI+SSBh
bSBhd2FyZSBvZiBJUFIgYXBwbGljYWJsZSB0byB0aGlzIGRyYWZ0LCBhbmQgaXQgaGFzIGFscmVh
ZHkgYmVlbjxvOnA+PC9vOnA+PC9zcGFuPjwvcHJlPg0KPHByZT48c3BhbiBsYW5nPSJFTi1VUyIg
c3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjoj
MjEyNTI5Ij5kaXNjbG9zZWQgdG8gdGhlIElFVEYuPG86cD48L286cD48L3NwYW4+PC9wcmU+DQo8
cHJlPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZx
dW90OyxzYW5zLXNlcmlmO2NvbG9yOiMyMTI1MjkiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cHJlPg0KPHByZT48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1Zl
cmRhbmEmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMjEyNTI5Ij5JIGFtIGF3YXJlIG9mIElQUiBh
cHBsaWNhYmxlIHRvIHRoaXMgZHJhZnQsIGJ1dCB0aGF0IGhhcyBub3QgeWV0IGJlZW48bzpwPjwv
bzpwPjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZh
bWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzIxMjUyOSI+ZGlzY2xv
c2VkIHRvIHRoZSBJRVRGLiBJIHdpbGwgd29yayB0byBlbnN1cmUgdGhhdCBpdCB3aWxsIGJlIGRp
c2Nsb3NlZCBpbiBhPG86cD48L286cD48L3NwYW4+PC9wcmU+DQo8cHJlPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZxdW90OyxzYW5zLXNlcmlmO2Nv
bG9yOiMyMTI1MjkiPnRpbWVseSBtYW5uZXIuPG86cD48L286cD48L3NwYW4+PC9wcmU+DQo8cHJl
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZxdW90
OyxzYW5zLXNlcmlmO2NvbG9yOiMyMTI1MjkiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcHJl
Pg0KPHByZT48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1ZlcmRh
bmEmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMjEyNTI5Ij5UaGFua3MsPG86cD48L286cD48L3Nw
YW4+PC9wcmU+DQo8cHJlPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1
b3Q7VmVyZGFuYSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMyMTI1MjkiPi0gSGFyaTwvc3Bhbj48
c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOiMyMTI1MjkiPjxvOnA+PC9vOnA+PC9zcGFu
PjwvcHJlPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_5A5B4DE12C0DAC44AF501CD9A2B01A8D934D2B77DGGEMM532MBXchi_--


From nobody Wed Sep 25 20:47:25 2019
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 572371200B9; Wed, 25 Sep 2019 20:47:16 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: pce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.102.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: pce@ietf.org
Message-ID: <156946963626.29050.9369423667001464533@ietfa.amsl.com>
Date: Wed, 25 Sep 2019 20:47:16 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/QFjsXZWZYSXV1XeKwDW2xteO3yI>
Subject: [Pce] I-D Action: draft-ietf-pce-stateful-path-protection-11.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Sep 2019 03:47:17 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Path Computation Element WG of the IETF.

        Title           : PCEP Extensions for Associating Working and Protection LSPs with Stateful PCE
        Authors         : Hariharan Ananthakrishnan
                          Siva Sivabalan
                          Colby Barth
                          Ina Minei
                          Mahendra Singh Negi
	Filename        : draft-ietf-pce-stateful-path-protection-11.txt
	Pages           : 17
	Date            : 2019-09-25

Abstract:
   An active stateful Path Computation Element (PCE) is capable of
   computing as well as controlling via Path Computation Element
   Communication Protocol (PCEP) Multiprotocol Label Switching Traffic
   Engineering (MPLS-TE) Label Switched Paths (LSPs).  Furthermore, it
   is also possible for an active stateful PCE to create, maintain, and
   delete LSPs.  This document defines the PCEP extension to associate
   two or more LSPs to provide end-to-end path protection.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-path-protection/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-pce-stateful-path-protection-11
https://datatracker.ietf.org/doc/html/draft-ietf-pce-stateful-path-protection-11

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-pce-stateful-path-protection-11


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Sep 25 20:53:43 2019
Return-Path: <internet-drafts@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6139F1200DF; Wed, 25 Sep 2019 20:53:35 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: pce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.102.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: pce@ietf.org
Message-ID: <156947001534.29038.3394197904018962381@ietfa.amsl.com>
Date: Wed, 25 Sep 2019 20:53:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/9N0n4mEF28LkMVYyhSX8lRRc8zQ>
Subject: [Pce] I-D Action: draft-ietf-pce-stateful-pce-auto-bandwidth-12.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Sep 2019 03:53:35 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Path Computation Element WG of the IETF.

        Title           : PCEP Extensions for MPLS-TE LSP Automatic Bandwidth Adjustment with Stateful PCE
        Authors         : Dhruv Dhody
                          Rakesh Gandhi
                          Udayasree Palle
                          Ravi Singh
                          Luyuan Fang
	Filename        : draft-ietf-pce-stateful-pce-auto-bandwidth-12.txt
	Pages           : 34
	Date            : 2019-09-25

Abstract:
   The Path Computation Element Communication Protocol (PCEP) provides
   mechanisms for Path Computation Elements (PCEs) to perform path
   computations in response to Path Computation Clients (PCCs) requests.
   The Stateful PCE extensions allow stateful control of Multi-Protocol
   Label Switching (MPLS) Traffic Engineering Label Switched Paths (TE
   LSPs) using PCEP.

   The automatic bandwidth feature allows automatic and dynamic
   adjustment of the TE LSP bandwidth reservation based on the volume of
   traffic flowing through the LSP.  This document describes PCEP
   extensions for automatic bandwidth adjustment when employing an
   Active Stateful PCE for both PCE-Initiated and PCC-Initiated LSPs.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-pce-auto-bandwidth/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-pce-stateful-pce-auto-bandwidth-12
https://datatracker.ietf.org/doc/html/draft-ietf-pce-stateful-pce-auto-bandwidth-12

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-pce-stateful-pce-auto-bandwidth-12


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Sep 25 21:01:46 2019
Return-Path: <lizhenbin@huawei.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B685120170 for <pce@ietfa.amsl.com>; Wed, 25 Sep 2019 21:01:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MoMcPUWVxo2V for <pce@ietfa.amsl.com>; Wed, 25 Sep 2019 21:01:42 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E00AE120271 for <pce@ietf.org>; Wed, 25 Sep 2019 21:01:41 -0700 (PDT)
Received: from LHREML712-CAH.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 05B858974AAAEB599CE6 for <pce@ietf.org>; Thu, 26 Sep 2019 05:01:39 +0100 (IST)
Received: from lhreml716-chm.china.huawei.com (10.201.108.67) by LHREML712-CAH.china.huawei.com (10.201.108.35) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 26 Sep 2019 05:01:09 +0100
Received: from lhreml716-chm.china.huawei.com (10.201.108.67) by lhreml716-chm.china.huawei.com (10.201.108.67) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Thu, 26 Sep 2019 05:01:08 +0100
Received: from DGGEMM404-HUB.china.huawei.com (10.3.20.212) by lhreml716-chm.china.huawei.com (10.201.108.67) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1713.5 via Frontend Transport; Thu, 26 Sep 2019 05:01:08 +0100
Received: from DGGEMM532-MBX.china.huawei.com ([169.254.7.3]) by DGGEMM404-HUB.china.huawei.com ([10.3.20.212]) with mapi id 14.03.0439.000; Thu, 26 Sep 2019 12:01:01 +0800
From: Lizhenbin <lizhenbin@huawei.com>
To: "julien.meuric@orange.com" <julien.meuric@orange.com>, "pce@ietf.org" <pce@ietf.org>
Thread-Topic: [Pce] Adoption of draft-li-pce-sr-path-segment?
Thread-Index: AQHVc71hUq31PGIHsUm2OFMsI8oI76c8yloAgACLGRA=
Date: Thu, 26 Sep 2019 04:01:02 +0000
Message-ID: <5A5B4DE12C0DAC44AF501CD9A2B01A8D934D2BBD@DGGEMM532-MBX.china.huawei.com>
References: <29713_1569428443_5D8B93DB_29713_96_1_6698a3d9-4ace-57fd-3b7c-7be23f135631@orange.com> <C7C2E1C43D652C4E9E49FE7517C236CB0270318E@dggeml529-mbx.china.huawei.com>
In-Reply-To: <C7C2E1C43D652C4E9E49FE7517C236CB0270318E@dggeml529-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.206.84]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/FDC6XWVgWhHDxVGPIlTQS6sr4uc>
Subject: Re: [Pce] Adoption of draft-li-pce-sr-path-segment?
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Sep 2019 04:01:44 -0000

Hi WG,

Support as the co-author. Path Segment is the base for many usecases based =
on SR such as OAM, bi-directional, etc. It has been well accepted.=20
PCE extensions will facilitate the deployment of Path Segment and the draft=
 is ready.


Best Regards,
Zhenbin (Robin)





-----Original Message-----
From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of julien.meuric@orange.c=
om
Sent: Thursday, September 26, 2019 12:21 AM
To: pce@ietf.org
Subject: [Pce] Adoption of draft-li-pce-sr-path-segment?

Hi PCE WG,

In our adoption poll queue, draft-li-pce-sr-path-segment has been there for=
 a little while, after it was discussed face to face. We would now like you=
 to voice your opinion on the list: do you think this I-D can be the founda=
tion for a PCE WG's work item?

Please send your feedback to the PCE mailing list, including any comment yo=
u would like to share, especially if you think the WG should not adopt it. =
This poll will end on October 9.

Thanks,

Dhruv & Julien


___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou =
copies sans autorisation. Si vous avez recu ce message par erreur, veuillez=
 le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Le=
s messages electroniques etant susceptibles d'alteration, Orange decline to=
ute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation 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 dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.

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


From nobody Wed Sep 25 23:26:23 2019
Return-Path: <noreply@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 17920120045; Wed, 25 Sep 2019 23:26:15 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Barry Leiba via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-pce-lsp-control-request@ietf.org, Hariharan Ananthakrishnan <hari@netflix.com>, pce-chairs@ietf.org, hari@netflix.com, pce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.102.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Barry Leiba <barryleiba@computer.org>
Message-ID: <156947917508.29034.2649004397929023444.idtracker@ietfa.amsl.com>
Date: Wed, 25 Sep 2019 23:26:15 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/_WqHzBshQst_15dBlVNCIcBtFmE>
Subject: [Pce] Barry Leiba's No Objection on draft-ietf-pce-lsp-control-request-09: (with COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Sep 2019 06:26:15 -0000

Barry Leiba has entered the following ballot position for
draft-ietf-pce-lsp-control-request-09: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-pce-lsp-control-request/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I have only some editorial comments.  There’s no need to respond, but please
consider these comments, as I think they’ll help make the document clearer. 
Particularly note the first comment for Section 3.

— Abstract —

   This document describes an extension to the Path Computation Element
   communication Protocol (PCEP) to enable a PCE to make such requests.

It’s a small thing, but no requests have been mentioned that could match “such
requests”.  But “control” has been discussed, so  I think you need to say it
this way:

NEW
   This document describes an extension to the Path Computation Element
   communication Protocol (PCEP) to enable a PCE to make requests for
   such control.
END

— Section 1 —

   In case of virtualized PCEs (vPCE) running as virtual network
   function (VNF), as the computation load in the network increases

“Running as virtual network function” sounds like it’s missing something. 
Maybe “running in VNF mode,” or some such?

   The PCEs could use proprietary algorithm to decide which LSPs
   to be assigned to the new vPCE.

Either “a proprietary algorithm” or “proprietary algorithms”.

   Thus having a mechanism for the PCE
   to request control of some LSPs is needed.

You need a comma after “Thus”.

   This specification provides a simple extension, by using this a PCE
   can request control

Comma splice.  The easiest fix is to change the “,” to a “:”.  Or else split it
into two sentences at the comma.

— Section 3 —
This section refers to the new flag as the “LSP-Control Request Flag”.  The
IANA Considerations section (7.1) just calls it “LSP-Control”.  Probably
Section 7.1 should call it “LSP-Control Request”, and this section should refer
to “TBD” so that th RFC Editor will insert the bit number that IANA assigns.

   The Stateful PCE Request Parameters (SRP) object is defined in
   Section 7.2 of [RFC8231], it includes a Flags field.

Comma splice.  Change “it” to “and” to fix it.

   The C Flag has no meaning in other PCEP messages that
   carry SRP object

Either “an SRP object” or “SRP objects”.

— Section 4 —

   The D Flag and C
   Flag are mutually exclusive in PCUpd message.  The PCE SHOULD NOT
   send control request for LSP which is already delegated to the PCE,
   i.e. if the D Flag is set in the PCUpd message, then C Flag SHOULD
   NOT be set.

I’m confused: “mutually exclusive” means that they can’t both be set.  So why
SHOULD NOT and not MUST NOT?  (You’re also missing a few articles here: ”a
PCUpd message”, “a control request”, “an LSP”, and “the C Flag”.

   It should be noted that a legacy implementation of PCC, that does not
   support this extension would trigger the error condition as specified
   in [RFC8231] (a PCErr with Error-type=19 (Invalid Operation) and
   error-value 1 (Attempted LSP Update Request for a non-delegated LSP))
   as the D Flag would be unset in this update request.

Please move the comma that’s after “PCC” and place it instead before “as the D
Flag”.

   It also specifies how a
   PCE MAY obtain control over an orphaned LSP that was PCE-initiated.

This should be “may”, not a BCP 14 key word.



From nobody Wed Sep 25 23:42:45 2019
Return-Path: <dhruv.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6129C12080F; Wed, 25 Sep 2019 23:42:36 -0700 (PDT)
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, FREEMAIL_FROM=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=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 sd4FZcshXV-5; Wed, 25 Sep 2019 23:42:34 -0700 (PDT)
Received: from mail-io1-xd2d.google.com (mail-io1-xd2d.google.com [IPv6:2607:f8b0:4864:20::d2d]) (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 3965B1200F6; Wed, 25 Sep 2019 23:42:34 -0700 (PDT)
Received: by mail-io1-xd2d.google.com with SMTP id a1so3613773ioc.6; Wed, 25 Sep 2019 23:42:34 -0700 (PDT)
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=2uKoV7tyICeQJrtitD1fXshnYyreBh92p3Q4gAXvfgk=; b=VT52U6JEezB13nXP8n4/yATw1UxE5Wy1OKNQH+H7uB/whuBHQaenqCVBe98I/AfvRg 1sdFlDFd2otkyc4lvbXBfMkzvceaduP9keeftGQvJvuub1QqllHsfUn/YkpkOOcKmfvZ 2WHKD8M4aNCcV0w5+iaOQnoYqrr7Fajw8F3NasXFyq0AvQYr6EsE4aqt9XAbrhhX5TI6 20RR9lB3ck9Y0e7blVT/x0qQIqmy6Rwit/94Ku6w3ZjZY3cx0j6Kbtr5uMfm4nrblAMO 0cWpc8xxqX3+4/CZ4e0cFdoLHBdTQ6c2336NcsoXu4Ol0Q/KGqcUCTQx6546F/9lNEMp CVkw==
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=2uKoV7tyICeQJrtitD1fXshnYyreBh92p3Q4gAXvfgk=; b=kkcHzpzL4CvjAj1zZHhKJiYZ2MNk9Ji4WoajSzxt3gLjojjI35jGplA7t0lKl7Orly TTRlsxJ9vWbKvdBygQ543jAWzhKVA8b45MXFkip50vpYy0oT9JnnM0CGZcVLU6JiXO4r g+7NfHtMftta+SNbFK1fdTs33b6eULVFbO6S1VIrzgftVUUqu6JWQNWGjNg0BbuJzmAR /qSrdOVjEI9ar2wTxHGumbvmUzLcb/trno9t0ehF+sgHjHWjUe+I6wa2gvmGHYUCgExI AbW0MURj2wETjODlEVBVuq6ihhd9R9c5Op0pUHY/apVN9xNQkNTkE/yYc4k+MELfCQhM NW5w==
X-Gm-Message-State: APjAAAWkIM7FbMEIpl39WX/ewELVVSRFQouGFqdRzfHBCgIgQrkf5Sqr xhA4JFOa/4Gx8NU9dNpwVzHdXfo2EY2wOWei3Hg=
X-Google-Smtp-Source: APXvYqzz1QCXnUost4GjcZ1jb3F9xEQJHELEFb/2CLGOrbG0HAVFa3wGrq7yXwhgP6Te8+T0GOV4JVEwYWzDskJHnco=
X-Received: by 2002:a5e:d502:: with SMTP id e2mr1978340iom.279.1569480153150;  Wed, 25 Sep 2019 23:42:33 -0700 (PDT)
MIME-Version: 1.0
References: <156884459034.4565.10696493114905134845.idtracker@ietfa.amsl.com> <CAB75xn5wp6EvhCVExn9sz4ipbxT+1GpPbW_fX8GOea6zh=tBpw@mail.gmail.com> <20190925232548.GQ6424@kduck.mit.edu>
In-Reply-To: <20190925232548.GQ6424@kduck.mit.edu>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Thu, 26 Sep 2019 12:11:56 +0530
Message-ID: <CAB75xn7XA4+b3+65SK8PhKUfQNX_Z3FRUOs+8u3Ekmv1XvXdYA@mail.gmail.com>
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pce-stateful-hpce@ietf.org,  Adrian Farrel <adrian@olddog.co.uk>, pce-chairs <pce-chairs@ietf.org>, pce@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/q05i0SflNwqVeMllpmWA8gKh99Y>
Subject: Re: [Pce] Benjamin Kaduk's Discuss on draft-ietf-pce-stateful-hpce-13: (with DISCUSS and COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Sep 2019 06:42:37 -0000

Hi Ben,

Snipping to the final discuss that is still open -


> > > ----------------------------------------------------------------------
> > > DISCUSS:
> > > ----------------------------------------------------------------------
> > >
> > > I think this should be pretty easy to resolve, though I'm not sure what
> > > the right way to do so it.
> > >
> > > Section 3 says:
> > >
> > >    [I-D.ietf-pce-hierarchy-extensions] defines the H-PCE Capability TLV
> > >    that is used in the Open message to advertise the H-PCE capability.
> > >    [RFC8231] defines the Stateful PCE Capability TLV used in the Open
> > >    message to indicate stateful support.  The presence of both TLVs in
> > >    an Open message indicates the support for stateful H-PCE operations
> > >    as described in this document.
> > >
> > > There is no normative reference relationship (in either direction)
> > > between draft-ietf-pce-hierarchy-extension and this document; I think
> > > that the use of the capability TLV to imply both sets of functionality
> > > implies some sort of normative relationship; we wouldn't want version
> > > skew between documents to induce breaking changes.  In particular, an
> > > implementation that already supports RFC 8231 and is implementing the
> > > hierarchy extensions would need to know to look at this document *and
> > > implement it*, or would unknowingly be noncompliant with this document
> > > and fail to interoperate with a peer that is compliant with this
> > > document.
> > >
> >
> > How about we add normative text for this -
> >
> >    [I-D.ietf-pce-hierarchy-extensions] defines the H-PCE Capability TLV
> >    that is used in the Open message to advertise the H-PCE capability.
> >    [RFC8231] defines the Stateful PCE Capability TLV used in the Open
> >    message to indicate stateful support. To indicates the support for
> >    stateful H-PCE operations described in this document, a PCEP speaker
> >    MUST include both TLVs in an Open message. It is RECOMMENDED that any
> >    implementation that supports stateful operations [RFC8231] and H-PCE
> >    [I-D.ietf-pce-hierarchy-extensions] would also implements the
> >    stateful H-PCE operations as described in this document.
> >
> > This would be true in most deployments/implementations of C-PCE and
> > P-PCE that are also stateful!
>
> This does remove the problematic normative requirement on implementations
> of other documents, but I'm not sure if it does what's needed for the
> interactions across documents.  Specifically, what will happen if two peers
> both support/advertise stateful PCE and H-PCE but only one implements
> stateful HPCE? Will there be a clean error handling at runtime and
> degredation to one or the other, or will there be messy errors?  If the
> latter, then I don't think we can just have a RECOMMENDED relationship.
>

The assumption was that any implementation that claims to support
stateful and H-PCE on a particular session would also support Stateful
H-PCE and this document just describes the interaction between these
two features as an informational document.

But, lets take a case where PCC and P-PCE support stateful H-PCE but
the C-PCE does not. PCC would send stateful message to C-PCE and C-PCE
would not further propagate them.

I further did a mental exercise for PCC -> C-PCE -> P-PCE and assumed
all support stateful and H-PCE extension but what happens when any
PCEP speaker does not support stateful H-PCE but the peer assumes that
it does. On further PCEP message exchange, the messages may not get
further propagated and thus at worse would not lead to the stateful
H-PCE based 'parent' control of the LSP. This is something any peer
should be prepared for anyways.

The "clean" solution would be to add a new flag; but then we also need
to move this a standards track and loose the claim that this is just a
combination of existing protocol extensions.

Thanks!
Dhruv


From nobody Thu Sep 26 00:39:44 2019
Return-Path: <adrian@olddog.co.uk>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9989E120816; Thu, 26 Sep 2019 00:39:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sCs7Wb4rPPzJ; Thu, 26 Sep 2019 00:39:39 -0700 (PDT)
Received: from mta8.iomartmail.com (mta8.iomartmail.com [62.128.193.158]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D10812084B; Thu, 26 Sep 2019 00:39:36 -0700 (PDT)
Received: from vs1.iomartmail.com (vs1.iomartmail.com [10.12.10.121]) by mta8.iomartmail.com (8.14.4/8.14.4) with ESMTP id x8Q7dXw3012803; Thu, 26 Sep 2019 08:39:34 +0100
Received: from vs1.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 839B02203B; Thu, 26 Sep 2019 08:39:33 +0100 (BST)
Received: from asmtp1.iomartmail.com (unknown [10.12.10.248]) by vs1.iomartmail.com (Postfix) with ESMTPS id 6E9632203A; Thu, 26 Sep 2019 08:39:33 +0100 (BST)
Received: from LAPTOPK7AS653V ([87.112.72.158]) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.4/8.14.4) with ESMTP id x8Q7dSVx022810 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 26 Sep 2019 08:39:32 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <draft-zhang-pce-resource-sharing@ietf.org>
Cc: <pce@ietf.org>
Date: Thu, 26 Sep 2019 08:39:24 +0100
Organization: Old Dog Consulting
Message-ID: <00bc01d5743d$89693c20$9c3bb460$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdV0PBwa8hOvLNhiTAKngPKw4ETJNg==
Content-Language: en-gb
X-Originating-IP: 87.112.72.158
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-24934.005
X-TM-AS-Result: No--18.786-10.0-31-10
X-imss-scan-details: No--18.786-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-24934.005
X-TMASE-Result: 10--18.785500-10.000000
X-TMASE-MatchedRID: SZwsnQS1TAc/9d9Rtcc0Q6JVTu7sjgg1lFGUu7DBzhhtHpq0YbBRi2eG LC9y2ysxOHQMPkdZKVOJQE6dtGxyOUyO27FZOPGv7LuOEAY9BqT27Syjew41+LKeTtOdjMy61IT 6ihIyptbD+zC17DiLSqoqVJT6t2qTChTObk4Cb7/jxJDUku2PNhZSD+Gbjz3I7649n0TgA4k9Mh AW8ZTOY/F4AdJnW02pyhxVty87JW1zt4swJJfEYQPZZctd3P4BEDnDEqNPduqZfDRE1uqSgtWZD ZFp9sK+XZ9uwiJ9BzHiVHZUU4QDnpmvObnpEDjcFEiDvEGKJxbJ5SXtoJPLyDi//dZ3YI25tdBA /Ye69J0XxDANc7MuDgG+x76r1ZOgvUDyWU5LV4OdonALKgiNvKwmLjb7urxINadzXMzmvfo/sJJ rvRfE1Gitp0rwRDpPWYQ/NVzpo5Bo/KGUV8ExqIvNlIrJDKnMunSyiaV8TbP78VtsEK4eICyW7M C1GOnhzFzAoAIAqP6+ScOGRvQ7A8TGhdajQJfFgLf5GeDY2qMOZNXmvnJaen8ozV5Wwb505sZTw YHfBM7aaz6XaPMQyiifxa8hl4apkbfFSBkmVVc05OiRm60IbgeCHewokHM/pUhsal26H0dRLTER hRg1g2re8N4zYSDbg25QWLQyM7uZRBKsj/jrq8y6PPK75b2BPJb7oABYhT+fcVJ8cL8ZO3/WDu2 EM8cZB5lYfN/XeVp5xMgAEHdrO09OXLef1sAMM8XTtgUzttOaIhErJt0dLAbYcy9YQl6ebxTyq4 Bg+pCh9bMmqe83MQdiJPnMXEw20yMP1QZOu5KeAiCmPx4NwLTrdaH1ZWqCii7lXaIcF/Ww7M6dy uYKg/cUt5lc1lLgtT4piLWpY7p+3BndfXUhXQ==
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/kH9gKq-t-CZB-QrkBMet-tf2NHM>
Subject: [Pce] Review of draft-zhang-pce-resource-sharing-10
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Sep 2019 07:39:43 -0000

Hi,

Now I'm no longer one of the PCE chairs, I have a little more time for
reviewing works in progress.

This document popped up as a candidate because it has been around for a
long time and is now on its eleventh version. (It's also not too long,
which makes it attractive.)

I hope these comments are useful.

Best,
Adrian

===

Title

OLD
    Extensions to Path Computation Element Protocol (PCEP) to Support
                Resource Sharing-based Path Computation
NEW
  Extensions to the Path Computation Element Protocol (PCEP) to Support
                Resource Sharing-based Path Computation
END

---

Boilerplate

You should reorganise the header sections to match with the current
best practice. That it:

Title
File name
Abstract
Status of this memo
Copyright
Table of contents

The requirements language should be moved to Section 1.1 or Section 2
where you should use the latest form of words...

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

That also gives you an additional Normative reference for 8174.

---

Optional plurals. In English you do not need say things like "use common
piece(s)". You can use the unequivocal plural and it is understood that
it is optional. So you should say "use common pieces".

Please s/(s)/s/ throughout the document.

---

In the Abstract you have a use of "PCEP" before the expansion of the
term.

---

The last words of the Abstract are:
   which is a special case in the association path computation.

This is slightly confusing because you haven't established what
"association path computation" is. I suggest you might change the
Abstract to read something like:

   Resource sharing in a network means two or more Label Switched Paths
   (LSPs) use common piece(s) of resource along their paths. This can
   help save network resource and is useful in scenarios such as LSP
   recovery or when two LSPs do not need to be active at the same time.
   A Path Computation Element (PCE) is responsible for path computation
   with such requirement.

   Existing extensions to the Path Computation Element Protocol (PCEP)
   allow one path computation request for an LSP to be associated with
   other (existing) LSPs through the use of the PCEP Association Object.

   The resource-sharing-based path computation
   with better efficiency can be achieved together with the association
   object in PCEP.

   This document extends PCEP to support resource sharing-based path
   computation as another use of the Association Object.

---

Section 1

OLD
   provides an alternative way for providing
NEW
   is a way to provide
END

Since "passive" and "active" have not yet been mentioned...
OLD
   Unless specified, this
   document assumes a PCE mentioned is a stateful PCE (either passive
   or active).
NEW
   Unless specified, this
   document assumes a PCE mentioned is a stateful PCE.
END

---

Global search and replace "a LSP" to "an LSP"

---

In Section 1 you have:

   Furthermore, if there is resource sharing between new LSP and
   existing LSP, the two LSPs cannot exist simultaneously, the new LSP
   will replace the existing LSP(s).

I know why you say this, because (obviously) you can't double-book
resources. But I think that you can relax the requirement here especially
for the case of protection and restoration. All you actually need is
that both LSPs can't be active (i.e., carry traffic) at the same time.

Actually, a little while later you talk about make-before-break where
(obviously) both LSPs can exist at the same time.

Of course, this is not a concern for the PCE, just for the LSP head-end,
so perhaps it isn't a requirement to state here. Maybe just state it as
an observation in this paragraph.

But you will need to clean up the hole text, I think. For example, a
little later you have:
   However, these objects
   are used to describe the relationship with two simultaneous LSPs,
   instead of a new one and an old one, which is different with the
   object proposed in this draft.
...and you say that like only one of the two LSPs will exist at any
time, but (again) that is not consistent with MBB or other forms of
protection. So this could be clarified to mean "used to carry traffic".

---

In Section 1

   but also the same slice of bandwidth in TDM networks.

While true, this appears to be limiting to TDM where, I think, you
intend the document to apply to any technology. So how about:

   but also the same slice of bandwidth in the network.

---

Throughout the document, where you have written "this draft" say "this
document" to future-proof yourself against becoming an RFC.

Similarly s/proposed/defined/

---

Section 1

   As mentioned in [RFC8231], the PLSP-ID is unique during a PCEP
   session between PCC and PCE. Such identification is helpful in
   supporting the above resource sharing requirement for
   standardization of stateful PCEs.  With a unique identifier, the
   configuration of PCCs is greatly simplified. Instead of determining
   all the resources to be shared, the PCC could request resource
   sharing directly from PCE.

This might be better as...

   As mentioned in [RFC8231], the PLSP-ID provides a unique identifier
   for an LSP during a PCEP session between PCC and PCE. Such
   identification is helpful in supporting the resource sharing
   requirement for stateful PCEs because it greatly simplifies the
   operation of a PCC. Instead of the PCC determining all the resources
   to be shared, the PCC can request that the PCE share the resources of
   a specific LSP: the stateful PCE is able to determine those resources
   itself.

---

Section 1

   In a multi-layer network, Label Switched Paths (LSPs) in a lower

No need to expand "LSP" a second time, here.

---

There is some misalignment of the sides of the stateful PCE in Figure 1

---

Section 2.1

   If resources are shared
   between the old and new LSPs, there will be some 'interruption' when
   the traffic is switched from the old LSP to the new LSP.

and later

   On the other hand, in some scenarios there are different policies,
   for example the LSP should be restored without any interruption with
   best effort.

Well, didn't link N2-N3 just fail? So the interruption is probably
already quite significant.

You do go on to say
   An example can be found in Fig. 1 without failure on
   N2-N3 link, instead, an online re-optimization is needed for the
   working LSP (N1-N2-N3) from the stateful PCE.

So I think you need to sort out two cases:
1. Repair after failure
2. Re-routing for optimization (or other reasons)

For these, you may want to explain the benefits of shared resources:
- may not be enough resource in the network to set up the 2nd LSP
- may want to keep the 2nd LSP on the shortest path and might not be
  enough resources to do that
- may want to reduce network programming time
- may have some resource continuity (such as lambda) constraints
But also the drawbacks:
- switch-over in MBB may take longer because multiple nodes have to
  act to effect the switch
- switch-over coordination may be harder because switching nodes are
  remote from the LSP end-points

Your example LSP1 and LSP2 do highlight this successfully.

---

I wonder whether Section 2.1 should also include notifying the PCE of
which resources to avoid. That would certainly include the failed link
(I am not sure that we can assume that the PCE has learned about the
failure [through the IGP] as fast as the PCC learned about it through
fault notification or signalling), but it might also include non-failed
in case of rerouting [such as before planned maintenance]).

---

The top of LSR H5 has become detached in Figure 2

---

The diagonals in Figure 3 are hard on the eye. Can you use single lines?

Maybe...

                         +----------------------+
                         |        P-PCE         |
                         +----------+-----------+
                        /           |            \
                       /            |             \
                      /             |              \
                     /              |               \
                    /               |                \
                   /                |                 \
           +------+             +---+---+              +------+
           |C-PCE1|             |C-PCE2 |              |C-PCE3|
           +------+             +-------+              +------+

     ______________       ______________________      ______________
    /               \    /                      \    /              \
   | +---+     +---+ |  |  +---+   +---+   +---+ |  | +---+    +---+ |
   | | A +-----+ B +-+--+--+ D +---+ E +---+ H +-+--+-+ J +----+ L | |
   | +---+     +---+ |  |  +---+   +---+   +---+ |  | +---+    +-+-+ |
   |      \          |  |         /             \|  |           /    |
   |       \         |  |        /               +  |          /     |
   |        \        |  |       /                |\ |         /      |
   |         \ +---+ |  |  +---+                 | \|    +---+       |
   |          \| C +-+--+--+ G |                 |  +----| K |       |
   |           +---+ |  |  +---+                 |  |    +---+       |
    \_______________/    \______________________/    \______________/


---

In 3.1 you have:

   A sharing group should have multiple LSPs. The number of LSPs and
   the criteria for how LSPs share among each other are implementation
   dependent. Local path computation policies apply to different PCE
   and PCC, some examples can be found in section 2.

I wonder whether "implementation dependent" might be better as
"dependent on local policy".

---

Section 3.2 has:

   The PCEP Resource Sharing group MUST carry the following TLV. It MAY
   be carried within a PCReq message from the network element (or other
   PCCs) so as to indicate the desired resource sharing requirements to
   be applied by the stateful PCE during path computation.

It feels like a contradiction between the "MUST" and the "MAY".

---

The figure in 3.2 seems to have surplus blank lines inserted.

---

Section 3.2

Flags L, N, and B all say that the PCE "should prioritise" something.
That is OK, but what happens if more than one bit is set? How are the
prioritisations prioritised?

---

Section 3.3

     - If the Resource Sharing TLV is unknown/unsupported, the PCE will
     follow procedures defined in [RFC5440].  That is, the PCE sends a
     PCErr message with error type 3 or 4 (Unknown / Not supported
     object) and error value 1 or 2 (unknown / unsupported object class
     / object type), and the related path computation request is
     discarded.

     - If Resource Sharing TLV are unknown/unsupported and the P bit is
     set, the PCE MUST send a PCErr message with error type 3 or 4
     (Unknown / Not supported object) and error value 4
     (Unrecognized/Unsupported parameter), and the related path
     computation request MUST be discarded as defined in [RFC5440].

Now I'm confused! Is this a TLV or an Object? And how are these two
paragraphs compatible? (I think it is a TLV.)

---

Section 3.3

     - If the resource sharing TLV is extracted correctly, the PCE MUST
     apply the requested resource sharing requirement.

Yes, OK. Except that you have said this is subject to local policy which
could (of course) mean that no sharing is done or even attempted.

---

Section 3.3

Can you expand RSO on first use.

---

According to WG policy, you'll need to include an "Implementation
Status" section. Put it in now, even if you only say that you are not
aware of any implementations at the moment.

---

I'd love to see a Manageability Considerations section. It isn't
compulsory, but it has become normal for the PCE WG. And you have
some management things to talk about as you mention policies, and
also as you have to coordinate alerts/fault reports from the network.

You also have "The RSO flags may be locally configured..."

---

Section 5.1 uses "TBA" but the txt uses "TBD" Please align these.

---

Section 5.1 needs a little more detail to correctly direct IANA to the
registry. You need some text such as...

   IANA maintains a registry called the "Path Computation Element
   Protocol (PCEP) Numbers" registry with a subregistry called the
   "Association Type Field" subregistry.  IANA is requested to make
   an assignment from that subregistry as follows:

   Type |   Name               | Reference
   -----+----------------------+---------------
   TBD1 | Sharing Association  | [this.I-D]

---

The heading of Section 5.2 has become indented

---

Section 5.2

This section seems a bit jumbled. Have a look at Section 7.2 of
draft-ietf-pce-association-diversity.

You have numbered the bits from 0 as the right-hand bit, but the figure
in section 3.2 has them numbered in the opposite way. You need to be
consistent or include an explanation. Again, modeling on draft-ietf-pce-
association-diversity might help.

---

It would be helpful if you included the filename in the reference
[H-PCE].  I think this is draft-ietf-pce-stateful-hpce.

---

The Contributors section is hiding inside the Authors' Addresses and I
missed it. I think that is just an indentation problem.


From nobody Thu Sep 26 09:47:20 2019
Return-Path: <rgandhi@cisco.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CFF612009E for <pce@ietfa.amsl.com>; Thu, 26 Sep 2019 09:47:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level: 
X-Spam-Status: No, score=-14.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=ktBlkZg7; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=L+gtruSH
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 zArTqueT4Ro9 for <pce@ietfa.amsl.com>; Thu, 26 Sep 2019 09:47:17 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99184120019 for <pce@ietf.org>; Thu, 26 Sep 2019 09:47:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10885; q=dns/txt; s=iport; t=1569516437; x=1570726037; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=zNLowfqb3MZ6cGmLECtBD/KdpJOEZlJjv7iGSt3L3zA=; b=ktBlkZg7U99l3Oi5E5HZO7kDICoqskO0859P9JHKNmmWy8mxsWTjjK2n 0agqjwDe6ptZM74Y+BKUSAHRsIBYtON2cRwL2x97NjlgtZJctmN5xLiM2 yS+/1Dj0VfI7kopd1KHRxm0gDQtx24OM1XcfnvsXA2xf2KZYLzs8Eq6uD 4=;
IronPort-PHdr: =?us-ascii?q?9a23=3A17bZZBWy+QzbzrCUVkHbBa03QoHV8LGuZFwc94?= =?us-ascii?q?YnhrRSc6+q45XlOgnF6O5wiEPSA92J8OpK3uzRta2oGXcN55qMqjgjSNRNTF?= =?us-ascii?q?dE7KdehAk8GIiAAEz/IuTtankgE81EWF9k13q6KkNSXs35Yg6arw=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ALAABW64xd/40NJK1mGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQwBAQEBAQGBVAMBAQEBAQsBgRsvUANtViAECyoKhBiDRwOKeYJckxe?= =?us-ascii?q?EX4EugSQDVAkBAQEMAQEtAgEBhEACF4MaIzUIDgIDCQEBBAEBAQIBBQRthS0?= =?us-ascii?q?MhUsBAQEEEhEdAQEsCwEPAgEIDgMDAQIrAgICMB0IAgQBDQUigwABgR1NAx0?= =?us-ascii?q?BAqQ8AoE4iGFzgTKCfQEBBYEGAQGEABiCFwmBNAGMCxiBQD+BOB+CTD6EZIJ?= =?us-ascii?q?rMoImj1yFLIkojmkKgiKVCxuCN4dMjzGNNQtglVKDSwIEAgQFAg4BAQWBVAE?= =?us-ascii?q?1gVhwFTsqAYJBUBAUgU6DcoocATZ0gSmMRQGBIgEB?=
X-IronPort-AV: E=Sophos;i="5.64,552,1559520000";  d="scan'208,217";a="345875233"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 26 Sep 2019 16:46:53 +0000
Received: from XCH-RCD-015.cisco.com (xch-rcd-015.cisco.com [173.37.102.25]) by alln-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id x8QGkrJY000319 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 26 Sep 2019 16:46:53 GMT
Received: from xhs-aln-001.cisco.com (173.37.135.118) by XCH-RCD-015.cisco.com (173.37.102.25) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 26 Sep 2019 11:46:53 -0500
Received: from xhs-aln-003.cisco.com (173.37.135.120) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 26 Sep 2019 11:46:51 -0500
Received: from NAM05-BY2-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 26 Sep 2019 11:46:51 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=D3U9XfrRUthEo4OMjUBB0fzJkO+PIpvogLL4wIUYzailjEgtGHUkbrOD3GxHbgFsCOdG4HLUXDfXCqlGAIfLghdzUZ7XcHSFN4GB40mAiaMUCKwalPnXZPBYUNta561HBfV1RJnieZgzBoiqaeyJ7rq/sOqFE8Z61l9JS4iGKnAogHmFHTuoeC2WECAuDrbWQtJyQ9wi3aSi221MNT43F0N+iB9kSJoITjQiCEh5IVxSVBoWPnW9XujnS2ZfekhissjYfgW1T4o53xPrn0X0p4N4tVKoOLtUylvqE3ivITmyjuQS9WySyjmzJC7TYSL4aHrDvudbDovQKcqTq/FSHw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=zNLowfqb3MZ6cGmLECtBD/KdpJOEZlJjv7iGSt3L3zA=; b=A8yATSAsNglUzhkV2ifYXocyA3VTgMs60b94VEsrJ4wsJuHTeuCovn+pAJ/CvOiwJ2twS79QnFSmpm+6vJMEpotNJlIn1zzsg2/aXOrqHPM+qikWTQTBtS2i/fLfLXwjc5F5gPaNI9p65RekWphW9jzGKdWT2MWpOCYs1msvhMwD9SUz2cJsA9Yo8iv2F9SBf5AlWSuCADdXui3+HB/SBonX7dDIoPlKZLsbwKYkwrW5Eq+j4czZLCzopzCUA6A+aGpV7BvZAYMRISYjLvfACA4uqAjeRs9wT58ezMFb4Wnh7SX3RK4X7yXjrKDpBv+4NVhtz16AjIczdMY01Ocbnw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com;  s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=zNLowfqb3MZ6cGmLECtBD/KdpJOEZlJjv7iGSt3L3zA=; b=L+gtruSHxc09Q7vfffmXcM2ZpYMpBFgUz4jX3ymz4nriafuGVuINCIKSXgfBIYu8DK41w5livLmep5pZ/nDqrtmD+oaWayPWgPMO7IF97VxF1WkWj9levNcvvAAEFV7mpOZOzIYLnFcbpa+jutPBu4kSsMBISpP7biaxG+TxToU=
Received: from BYAPR11MB3061.namprd11.prod.outlook.com (20.177.224.85) by BYAPR11MB3191.namprd11.prod.outlook.com (20.177.127.88) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2284.25; Thu, 26 Sep 2019 16:46:50 +0000
Received: from BYAPR11MB3061.namprd11.prod.outlook.com ([fe80::b185:1dbd:6e0f:27ef]) by BYAPR11MB3061.namprd11.prod.outlook.com ([fe80::b185:1dbd:6e0f:27ef%6]) with mapi id 15.20.2284.023; Thu, 26 Sep 2019 16:46:49 +0000
From: "Rakesh Gandhi (rgandhi)" <rgandhi@cisco.com>
To: Hariharan Ananthakrishnan <hari@netflix.com>, "chengli13@huawei.com" <chengli13@huawei.com>, "mach.chen@huawei.com" <mach.chen@huawei.com>, "chengweiqiang@chinamobile.com" <chengweiqiang@chinamobile.com>, "jie.dong@huawei.com" <jie.dong@huawei.com>, "lizhenbin@huawei.com" <lizhenbin@huawei.com>, "xiong.quan@zte.com.cn" <xiong.quan@zte.com.cn>
CC: "pce@ietf.org" <pce@ietf.org>
Thread-Topic: IPR Poll on draft-li-pce-sr-path-segment-08
Thread-Index: AQHVc8mgMc+bWrNH3UaBaLb6ZZu/mac9tw0A
Date: Thu, 26 Sep 2019 16:46:49 +0000
Message-ID: <A8968932-342C-47A0-97D3-F2881791BFBE@cisco.com>
References: <CAL70W4q8DctbRNTFMWzKELNZORgL5OuStFJgFOx1tw9tq3+jGA@mail.gmail.com>
In-Reply-To: <CAL70W4q8DctbRNTFMWzKELNZORgL5OuStFJgFOx1tw9tq3+jGA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.10.d.190811
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rgandhi@cisco.com; 
x-originating-ip: [128.107.241.171]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 28253959-dad3-48bc-5fe0-08d742a1204c
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600167)(711020)(4605104)(1401327)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:BYAPR11MB3191; 
x-ms-traffictypediagnostic: BYAPR11MB3191:
x-microsoft-antispam-prvs: <BYAPR11MB31916F051C2395F042E236DEBF860@BYAPR11MB3191.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 0172F0EF77
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(346002)(39860400002)(396003)(376002)(366004)(189003)(199004)(66946007)(64756008)(66556008)(66446008)(66476007)(5660300002)(6506007)(53546011)(76116006)(478600001)(186003)(58126008)(6512007)(54896002)(6246003)(229853002)(6436002)(316002)(102836004)(25786009)(36756003)(71200400001)(71190400001)(86362001)(6486002)(66066001)(2201001)(6306002)(26005)(446003)(476003)(486006)(33656002)(2616005)(11346002)(99286004)(110136005)(14454004)(4326008)(9326002)(8936002)(8676002)(3846002)(81156014)(81166006)(6116002)(14444005)(256004)(7736002)(2906002)(76176011)(2501003); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB3191; H:BYAPR11MB3061.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: clmJ+9KzV8V2r00NviZj6YUJ0fa6tbH6VBGzqpnzBkaC5RdYGShQ4ooPIDQwq7sThtr1PQBnlW5jkoUUivhZlnRvV1a8tYLDlbAEPkoZgISzhKIRf3/LxDuddAdSoyViKUL+RFPuWloOW1MIy/NG2seMdZfZ56LcQT1UZx8lpkktbwDn5HRa5VdetUKTc8UOU79hIFUQWwY5q4FQWuvmuWeCivuNLFidPOBqLe3Mlpjb2IrcP06eK/pIGunTL4ydILG8YV7LwU4KPfwGnAKNu2E9GtqxROukP6o+3mUFZcxFxPaZu6fBe8/shoZtR4al7T/EDOH6DY2trr027+bQifYaqT9sAmDydv4JD0mZRdE74i8Z03VZ+fRskG9BRh3kcMAUzyEnXhpBGl1aniIOs5xHpsZj7CsgIcYpOp5g+bk=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_A8968932342C47A097D3F2881791BFBEciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 28253959-dad3-48bc-5fe0-08d742a1204c
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Sep 2019 16:46:49.4439 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Bfnm6N9qPd/oY3tSZPq2nf46iFFHgbmchv1jbJykRRjCwwQOHRbmOJw9fonuLQzW6YtCXHzHwl+MSI9h1nVd6A==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB3191
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.25, xch-rcd-015.cisco.com
X-Outbound-Node: alln-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/eSJBhr6r219_cpO1m4vRZrJTYjE>
Subject: Re: [Pce] IPR Poll on draft-li-pce-sr-path-segment-08
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Sep 2019 16:47:19 -0000

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

SGkgSGFyaSwNCkkgYW0gbm90IGF3YXJlIG9mIGFueSBJUFIgYXBwbGljYWJsZSB0byB0aGlzIGRy
YWZ0IHRoYXQgc2hvdWxkIGJlIGRpc2Nsb3NlZCBpbiBhY2NvcmRhbmNlIHdpdGggSUVURiBJUFIg
cnVsZXMuDQoNClRoYW5rcywNClJha2VzaA0KDQoNCkZyb206IEhhcmloYXJhbiBBbmFudGhha3Jp
c2huYW4gPGhhcmlAbmV0ZmxpeC5jb20+DQpEYXRlOiBXZWRuZXNkYXksIFNlcHRlbWJlciAyNSwg
MjAxOSBhdCAxMDo0OSBBTQ0KVG86ICJjaGVuZ2xpMTNAaHVhd2VpLmNvbSIgPGNoZW5nbGkxM0Bo
dWF3ZWkuY29tPiwgIm1hY2guY2hlbkBodWF3ZWkuY29tIiA8bWFjaC5jaGVuQGh1YXdlaS5jb20+
LCAiY2hlbmd3ZWlxaWFuZ0BjaGluYW1vYmlsZS5jb20iIDxjaGVuZ3dlaXFpYW5nQGNoaW5hbW9i
aWxlLmNvbT4sICJqaWUuZG9uZ0BodWF3ZWkuY29tIiA8amllLmRvbmdAaHVhd2VpLmNvbT4sICJs
aXpoZW5iaW5AaHVhd2VpLmNvbSIgPGxpemhlbmJpbkBodWF3ZWkuY29tPiwgIj1TTVRQOnJnYW5k
aGlAY2lzY28uIGNvbSIgPHJnYW5kaGlAY2lzY28uY29tPiwgInhpb25nLnF1YW5AenRlLmNvbS5j
biIgPHhpb25nLnF1YW5AenRlLmNvbS5jbj4NCkNjOiAicGNlQGlldGYub3JnIiA8cGNlQGlldGYu
b3JnPg0KU3ViamVjdDogSVBSIFBvbGwgb24gZHJhZnQtbGktcGNlLXNyLXBhdGgtc2VnbWVudC0w
OA0KDQoNCkhpIEF1dGhvcnMsDQoNCg0KDQpJbiBwcmVwYXJhdGlvbiBmb3IgV29ya2luZyBHcm91
cCBsYXN0IGNhbGwgb24gdGhpcyBkcmFmdCwgSSdkIGxpa2UgYWxsDQoNCmF1dGhvcnMgYW5kIGNv
bnRyaWJ1dG9ycyB0byBjb25maXJtIG9uIHRoZSBsaXN0IHRoYXQgdGhleSBhcmUgaW4gY29tcGxp
YW5jZQ0KDQp3aXRoIElFVEYgSVBSIHJ1bGVzLg0KDQoNCg0KUGxlYXNlIHJlc3BvbmQgKGNvcHlp
bmcgdGhlIG1haWxpbmcgbGlzdCkgdG8gc2F5IG9uZSBvZjoNCg0KDQoNCkkgYW0gbm90IGF3YXJl
IG9mIGFueSBJUFIgYXBwbGljYWJsZSB0byB0aGlzIGRyYWZ0IHRoYXQgc2hvdWxkIGJlIGRpc2Ns
b3NlZA0KDQppbiBhY2NvcmRhbmNlIHdpdGggSUVURiBJUFIgcnVsZXMuDQoNCg0KDQpJIGFtIGF3
YXJlIG9mIElQUiBhcHBsaWNhYmxlIHRvIHRoaXMgZHJhZnQsIGFuZCBpdCBoYXMgYWxyZWFkeSBi
ZWVuDQoNCmRpc2Nsb3NlZCB0byB0aGUgSUVURi4NCg0KDQoNCkkgYW0gYXdhcmUgb2YgSVBSIGFw
cGxpY2FibGUgdG8gdGhpcyBkcmFmdCwgYnV0IHRoYXQgaGFzIG5vdCB5ZXQgYmVlbg0KDQpkaXNj
bG9zZWQgdG8gdGhlIElFVEYuIEkgd2lsbCB3b3JrIHRvIGVuc3VyZSB0aGF0IGl0IHdpbGwgYmUg
ZGlzY2xvc2VkIGluIGENCg0KdGltZWx5IG1hbm5lci4NCg0KDQoNClRoYW5rcywNCg0KLSBIYXJp
DQo=

--_000_A8968932342C47A097D3F2881791BFBEciscocom_
Content-Type: text/html; charset="utf-8"
Content-ID: <2A02832CA293A4429D9E297B0712D3C8@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxNSAoZmlsdGVyZWQg
bWVkaXVtKSI+DQo8c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFj
ZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2
IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToy
IDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OlZlcmRhbmE7
DQoJcGFub3NlLTE6MiAxMSA2IDQgMyA1IDQgNCAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZh
bWlseTpDb25zb2xhczsNCglwYW5vc2UtMToyIDExIDYgOSAyIDIgNCAzIDIgNDt9DQovKiBTdHls
ZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1h
bA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEu
MHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5N
c29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOiMwNTYzQzE7DQoJ
dGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5r
Rm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOiM5NTRGNzI7DQoJdGV4
dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwcmUNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0K
CW1zby1zdHlsZS1saW5rOiJIVE1MIFByZWZvcm1hdHRlZCBDaGFyIjsNCgltYXJnaW46MGNtOw0K
CW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5
OiJDb3VyaWVyIE5ldyI7fQ0KcC5tc29ub3JtYWwwLCBsaS5tc29ub3JtYWwwLCBkaXYubXNvbm9y
bWFsMA0KCXttc28tc3R5bGUtbmFtZTptc29ub3JtYWw7DQoJbXNvLW1hcmdpbi10b3AtYWx0OmF1
dG87DQoJbWFyZ2luLXJpZ2h0OjBjbTsNCgltc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzsNCglt
YXJnaW4tbGVmdDowY207DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJy
aSIsc2Fucy1zZXJpZjt9DQpzcGFuLkhUTUxQcmVmb3JtYXR0ZWRDaGFyDQoJe21zby1zdHlsZS1u
YW1lOiJIVE1MIFByZWZvcm1hdHRlZCBDaGFyIjsNCgltc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJ
bXNvLXN0eWxlLWxpbms6IkhUTUwgUHJlZm9ybWF0dGVkIjsNCglmb250LWZhbWlseToiQ29uc29s
YXMiLHNlcmlmO30NCnNwYW4uRW1haWxTdHlsZTIwDQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFs
LXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOndpbmRv
d3RleHQ7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJ
Zm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo2MTIuMHB0IDc5
Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA3Mi4wcHQgNzIuMHB0IDcyLjBwdDt9DQpkaXYuV29yZFNl
Y3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+DQo8L2hlYWQ+DQo8Ym9k
eSBsYW5nPSJFTi1DQSIgbGluaz0iIzA1NjNDMSIgdmxpbms9IiM5NTRGNzIiPg0KPGRpdiBjbGFz
cz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkhpIEhhcmksPG86cD48L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JIGFtIG5vdCBhd2FyZSBvZiBhbnkgSVBSIGFw
cGxpY2FibGUgdG8gdGhpcyBkcmFmdCB0aGF0IHNob3VsZCBiZSBkaXNjbG9zZWQgaW4gYWNjb3Jk
YW5jZSB3aXRoIElFVEYgSVBSIHJ1bGVzLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGFua3Ms
PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5SYWtlc2g8bzpwPjwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9u
ZTtib3JkZXItdG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwY20gMGNtIDBj
bSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBw
dDtjb2xvcjpibGFjayI+RnJvbTogPC9zcGFuPjwvYj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEy
LjBwdDtjb2xvcjpibGFjayI+SGFyaWhhcmFuIEFuYW50aGFrcmlzaG5hbiAmbHQ7aGFyaUBuZXRm
bGl4LmNvbSZndDs8YnI+DQo8Yj5EYXRlOiA8L2I+V2VkbmVzZGF5LCBTZXB0ZW1iZXIgMjUsIDIw
MTkgYXQgMTA6NDkgQU08YnI+DQo8Yj5UbzogPC9iPiZxdW90O2NoZW5nbGkxM0BodWF3ZWkuY29t
JnF1b3Q7ICZsdDtjaGVuZ2xpMTNAaHVhd2VpLmNvbSZndDssICZxdW90O21hY2guY2hlbkBodWF3
ZWkuY29tJnF1b3Q7ICZsdDttYWNoLmNoZW5AaHVhd2VpLmNvbSZndDssICZxdW90O2NoZW5nd2Vp
cWlhbmdAY2hpbmFtb2JpbGUuY29tJnF1b3Q7ICZsdDtjaGVuZ3dlaXFpYW5nQGNoaW5hbW9iaWxl
LmNvbSZndDssICZxdW90O2ppZS5kb25nQGh1YXdlaS5jb20mcXVvdDsgJmx0O2ppZS5kb25nQGh1
YXdlaS5jb20mZ3Q7LCAmcXVvdDtsaXpoZW5iaW5AaHVhd2VpLmNvbSZxdW90OyAmbHQ7bGl6aGVu
YmluQGh1YXdlaS5jb20mZ3Q7LA0KICZxdW90Oz1TTVRQOnJnYW5kaGlAY2lzY28uIGNvbSZxdW90
OyAmbHQ7cmdhbmRoaUBjaXNjby5jb20mZ3Q7LCAmcXVvdDt4aW9uZy5xdWFuQHp0ZS5jb20uY24m
cXVvdDsgJmx0O3hpb25nLnF1YW5AenRlLmNvbS5jbiZndDs8YnI+DQo8Yj5DYzogPC9iPiZxdW90
O3BjZUBpZXRmLm9yZyZxdW90OyAmbHQ7cGNlQGlldGYub3JnJmd0Ozxicj4NCjxiPlN1YmplY3Q6
IDwvYj5JUFIgUG9sbCBvbiBkcmFmdC1saS1wY2Utc3ItcGF0aC1zZWdtZW50LTA4PG86cD48L286
cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4m
bmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPHByZSBzdHlsZT0id2hpdGUt
c3BhY2U6cHJlLXdyYXA7Ym94LXNpemluZzpib3JkZXItYm94O21hcmdpbi1ib3R0b206MXJlbTtv
dmVyZmxvdzphdXRvIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZxdW90
OyxzYW5zLXNlcmlmO2NvbG9yOiMyMTI1MjkiPkhpIEF1dGhvcnMsPG86cD48L286cD48L3NwYW4+
PC9wcmU+DQo8cHJlPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7
LHNhbnMtc2VyaWY7Y29sb3I6IzIxMjUyOSI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wcmU+
DQo8cHJlPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7LHNhbnMt
c2VyaWY7Y29sb3I6IzIxMjUyOSI+SW4gcHJlcGFyYXRpb24gZm9yIFdvcmtpbmcgR3JvdXAgbGFz
dCBjYWxsIG9uIHRoaXMgZHJhZnQsIEknZCBsaWtlIGFsbDxvOnA+PC9vOnA+PC9zcGFuPjwvcHJl
Pg0KPHByZT48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZxdW90OyxzYW5z
LXNlcmlmO2NvbG9yOiMyMTI1MjkiPmF1dGhvcnMgYW5kIGNvbnRyaWJ1dG9ycyB0byBjb25maXJt
IG9uIHRoZSBsaXN0IHRoYXQgdGhleSBhcmUgaW4gY29tcGxpYW5jZTxvOnA+PC9vOnA+PC9zcGFu
PjwvcHJlPg0KPHByZT48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZxdW90
OyxzYW5zLXNlcmlmO2NvbG9yOiMyMTI1MjkiPndpdGggSUVURiBJUFIgcnVsZXMuPG86cD48L286
cD48L3NwYW4+PC9wcmU+DQo8cHJlPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtWZXJk
YW5hJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzIxMjUyOSI+PG86cD4mbmJzcDs8L286cD48L3Nw
YW4+PC9wcmU+DQo8cHJlPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtWZXJkYW5hJnF1
b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzIxMjUyOSI+UGxlYXNlIHJlc3BvbmQgKGNvcHlpbmcgdGhl
IG1haWxpbmcgbGlzdCkgdG8gc2F5IG9uZSBvZjo8bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT4NCjxw
cmU+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssc2Fucy1zZXJp
Zjtjb2xvcjojMjEyNTI5Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNw
YW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssc2Fucy1zZXJpZjtjb2xv
cjojMjEyNTI5Ij5JIGFtIG5vdCBhd2FyZSBvZiBhbnkgSVBSIGFwcGxpY2FibGUgdG8gdGhpcyBk
cmFmdCB0aGF0IHNob3VsZCBiZSBkaXNjbG9zZWQ8bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT4NCjxw
cmU+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssc2Fucy1zZXJp
Zjtjb2xvcjojMjEyNTI5Ij5pbiBhY2NvcmRhbmNlIHdpdGggSUVURiBJUFIgcnVsZXMuPG86cD48
L286cD48L3NwYW4+PC9wcmU+DQo8cHJlPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtW
ZXJkYW5hJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzIxMjUyOSI+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wcmU+DQo8cHJlPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtWZXJkYW5h
JnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzIxMjUyOSI+SSBhbSBhd2FyZSBvZiBJUFIgYXBwbGlj
YWJsZSB0byB0aGlzIGRyYWZ0LCBhbmQgaXQgaGFzIGFscmVhZHkgYmVlbjxvOnA+PC9vOnA+PC9z
cGFuPjwvcHJlPg0KPHByZT48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZx
dW90OyxzYW5zLXNlcmlmO2NvbG9yOiMyMTI1MjkiPmRpc2Nsb3NlZCB0byB0aGUgSUVURi48bzpw
PjwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90
O1ZlcmRhbmEmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMjEyNTI5Ij48bzpwPiZuYnNwOzwvbzpw
Pjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1ZlcmRh
bmEmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMjEyNTI5Ij5JIGFtIGF3YXJlIG9mIElQUiBhcHBs
aWNhYmxlIHRvIHRoaXMgZHJhZnQsIGJ1dCB0aGF0IGhhcyBub3QgeWV0IGJlZW48bzpwPjwvbzpw
Pjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1ZlcmRh
bmEmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMjEyNTI5Ij5kaXNjbG9zZWQgdG8gdGhlIElFVEYu
IEkgd2lsbCB3b3JrIHRvIGVuc3VyZSB0aGF0IGl0IHdpbGwgYmUgZGlzY2xvc2VkIGluIGE8bzpw
PjwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90
O1ZlcmRhbmEmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMjEyNTI5Ij50aW1lbHkgbWFubmVyLjxv
OnA+PC9vOnA+PC9zcGFuPjwvcHJlPg0KPHByZT48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1
b3Q7VmVyZGFuYSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMyMTI1MjkiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcHJlPg0KPHByZT48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7VmVy
ZGFuYSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMyMTI1MjkiPlRoYW5rcyw8bzpwPjwvbzpwPjwv
c3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEm
cXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMjEyNTI5Ij4tIEhhcmk8L3NwYW4+PHNwYW4gc3R5bGU9
ImNvbG9yOiMyMTI1MjkiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcHJlPg0KPC9kaXY+DQo8L2Rpdj4N
CjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_A8968932342C47A097D3F2881791BFBEciscocom_--


From nobody Thu Sep 26 15:19:35 2019
Return-Path: <noreply@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7636C1201E5; Thu, 26 Sep 2019 15:19:25 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Kaduk via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-pce-stateful-pce-auto-bandwidth@ietf.org, Adrian Farrel <adrian@olddog.co.uk>, pce-chairs@ietf.org, adrian@olddog.co.uk,  pce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.103.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Benjamin Kaduk <kaduk@mit.edu>
Message-ID: <156953636547.10255.16246235690355501607.idtracker@ietfa.amsl.com>
Date: Thu, 26 Sep 2019 15:19:25 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/C6K-Iwhnb4RBUfsjbpYA6kmicO8>
Subject: [Pce] Benjamin Kaduk's No Objection on draft-ietf-pce-stateful-pce-auto-bandwidth-12: (with COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Sep 2019 22:19:26 -0000

Benjamin Kaduk has entered the following ballot position for
draft-ietf-pce-stateful-pce-auto-bandwidth-12: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-pce-auto-bandwidth/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks you for addressing my Discuss (and Comment) points!



From nobody Thu Sep 26 17:51:41 2019
Return-Path: <noreply@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 511DD1200E0; Thu, 26 Sep 2019 17:51:40 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Kaduk via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-pce-stateful-path-protection@ietf.org, Julien Meuric <julien.meuric@orange.com>, pce-chairs@ietf.org, julien.meuric@orange.com, pce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.103.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Benjamin Kaduk <kaduk@mit.edu>
Message-ID: <156954550032.31974.14332314099334010194.idtracker@ietfa.amsl.com>
Date: Thu, 26 Sep 2019 17:51:40 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/GBB9P0iijJsJBH9kEbD1omSDMNU>
Subject: [Pce] Benjamin Kaduk's No Objection on draft-ietf-pce-stateful-path-protection-11: (with COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Sep 2019 00:51:40 -0000

Benjamin Kaduk has entered the following ballot position for
draft-ietf-pce-stateful-path-protection-11: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-path-protection/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you for addressing my Discuss (and Comment) points!



From nobody Thu Sep 26 23:39:18 2019
Return-Path: <zhenghaomian@huawei.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E6A71200B4; Thu, 26 Sep 2019 23:39:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SevLZlCN8p70; Thu, 26 Sep 2019 23:39:14 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B22D6120086; Thu, 26 Sep 2019 23:39:13 -0700 (PDT)
Received: from lhreml702-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 0037CFB37A2D24552B92; Fri, 27 Sep 2019 07:39:09 +0100 (IST)
Received: from lhreml722-chm.china.huawei.com (10.201.108.73) by lhreml702-cah.china.huawei.com (10.201.108.43) with Microsoft SMTP Server (TLS) id 14.3.408.0; Fri, 27 Sep 2019 07:39:09 +0100
Received: from lhreml722-chm.china.huawei.com (10.201.108.73) by lhreml722-chm.china.huawei.com (10.201.108.73) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Fri, 27 Sep 2019 07:39:09 +0100
Received: from DGGEML421-HUB.china.huawei.com (10.1.199.38) by lhreml722-chm.china.huawei.com (10.201.108.73) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1713.5 via Frontend Transport; Fri, 27 Sep 2019 07:39:08 +0100
Received: from DGGEML511-MBX.china.huawei.com ([169.254.1.20]) by dggeml421-hub.china.huawei.com ([10.1.199.38]) with mapi id 14.03.0439.000; Fri, 27 Sep 2019 14:39:02 +0800
From: Zhenghaomian <zhenghaomian@huawei.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "draft-zhang-pce-resource-sharing@ietf.org" <draft-zhang-pce-resource-sharing@ietf.org>
CC: "pce@ietf.org" <pce@ietf.org>
Thread-Topic: Review of draft-zhang-pce-resource-sharing-10
Thread-Index: AdV0PBwa8hOvLNhiTAKngPKw4ETJNgAwhMcQ
Date: Fri, 27 Sep 2019 06:39:01 +0000
Message-ID: <E0C26CAA2504C84093A49B2CAC3261A43B8800B6@dggeml511-mbx.china.huawei.com>
References: <00bc01d5743d$89693c20$9c3bb460$@olddog.co.uk>
In-Reply-To: <00bc01d5743d$89693c20$9c3bb460$@olddog.co.uk>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.24.179.251]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/GavRXKZfYsbpEJNyL69x3KGgoLA>
Subject: [Pce] =?gb2312?b?tPC4tDogUmV2aWV3IG9mIGRyYWZ0LXpoYW5nLXBjZS1y?= =?gb2312?b?ZXNvdXJjZS1zaGFyaW5nLTEw?=
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Sep 2019 06:39:16 -0000

SGksIEFkcmlhbiwgDQoNClRoYW5rIHlvdSBmb3IgdGhlIGhlbHAgYW5kIGNvbW1lbnRzLCB3ZSB3
aWxsIGFkZHJlc3MgYW5kIHVwZGF0ZSBpbiB0aGUgbmV4dCB2ZXJzaW9uLiANCg0KQmVzdCB3aXNo
ZXMsDQpIYW9taWFuDQoNCi0tLS0t08q8/tStvP4tLS0tLQ0Kt6K8/sjLOiBBZHJpYW4gRmFycmVs
IFttYWlsdG86YWRyaWFuQG9sZGRvZy5jby51a10gDQq3osvNyrG85DogMjAxOcTqOdTCMjbI1SAx
NTozOQ0KytW8/sjLOiBkcmFmdC16aGFuZy1wY2UtcmVzb3VyY2Utc2hhcmluZ0BpZXRmLm9yZw0K
s63LzTogcGNlQGlldGYub3JnDQrW98ziOiBSZXZpZXcgb2YgZHJhZnQtemhhbmctcGNlLXJlc291
cmNlLXNoYXJpbmctMTANCg0KSGksDQoNCk5vdyBJJ20gbm8gbG9uZ2VyIG9uZSBvZiB0aGUgUENF
IGNoYWlycywgSSBoYXZlIGEgbGl0dGxlIG1vcmUgdGltZSBmb3IgcmV2aWV3aW5nIHdvcmtzIGlu
IHByb2dyZXNzLg0KDQpUaGlzIGRvY3VtZW50IHBvcHBlZCB1cCBhcyBhIGNhbmRpZGF0ZSBiZWNh
dXNlIGl0IGhhcyBiZWVuIGFyb3VuZCBmb3IgYSBsb25nIHRpbWUgYW5kIGlzIG5vdyBvbiBpdHMg
ZWxldmVudGggdmVyc2lvbi4gKEl0J3MgYWxzbyBub3QgdG9vIGxvbmcsIHdoaWNoIG1ha2VzIGl0
IGF0dHJhY3RpdmUuKQ0KDQpJIGhvcGUgdGhlc2UgY29tbWVudHMgYXJlIHVzZWZ1bC4NCg0KQmVz
dCwNCkFkcmlhbg0KDQo9PT0NCg0KVGl0bGUNCg0KT0xEDQogICAgRXh0ZW5zaW9ucyB0byBQYXRo
IENvbXB1dGF0aW9uIEVsZW1lbnQgUHJvdG9jb2wgKFBDRVApIHRvIFN1cHBvcnQNCiAgICAgICAg
ICAgICAgICBSZXNvdXJjZSBTaGFyaW5nLWJhc2VkIFBhdGggQ29tcHV0YXRpb24gTkVXDQogIEV4
dGVuc2lvbnMgdG8gdGhlIFBhdGggQ29tcHV0YXRpb24gRWxlbWVudCBQcm90b2NvbCAoUENFUCkg
dG8gU3VwcG9ydA0KICAgICAgICAgICAgICAgIFJlc291cmNlIFNoYXJpbmctYmFzZWQgUGF0aCBD
b21wdXRhdGlvbiBFTkQNCg0KLS0tDQoNCkJvaWxlcnBsYXRlDQoNCllvdSBzaG91bGQgcmVvcmdh
bmlzZSB0aGUgaGVhZGVyIHNlY3Rpb25zIHRvIG1hdGNoIHdpdGggdGhlIGN1cnJlbnQgYmVzdCBw
cmFjdGljZS4gVGhhdCBpdDoNCg0KVGl0bGUNCkZpbGUgbmFtZQ0KQWJzdHJhY3QNClN0YXR1cyBv
ZiB0aGlzIG1lbW8NCkNvcHlyaWdodA0KVGFibGUgb2YgY29udGVudHMNCg0KVGhlIHJlcXVpcmVt
ZW50cyBsYW5ndWFnZSBzaG91bGQgYmUgbW92ZWQgdG8gU2VjdGlvbiAxLjEgb3IgU2VjdGlvbiAy
IHdoZXJlIHlvdSBzaG91bGQgdXNlIHRoZSBsYXRlc3QgZm9ybSBvZiB3b3Jkcy4uLg0KDQogICBU
aGUga2V5IHdvcmRzICJNVVNUIiwgIk1VU1QgTk9UIiwgIlJFUVVJUkVEIiwgIlNIQUxMIiwgIlNI
QUxMIE5PVCIsDQogICAiU0hPVUxEIiwgIlNIT1VMRCBOT1QiLCAiUkVDT01NRU5ERUQiLCAiTk9U
IFJFQ09NTUVOREVEIiwgIk1BWSIsIGFuZA0KICAgIk9QVElPTkFMIiBpbiB0aGlzIGRvY3VtZW50
IGFyZSB0byBiZSBpbnRlcnByZXRlZCBhcyBkZXNjcmliZWQgaW4gQkNQDQogICAxNCBbUkZDMjEx
OV0gW1JGQzgxNzRdIHdoZW4sIGFuZCBvbmx5IHdoZW4sIHRoZXkgYXBwZWFyIGluIGFsbA0KICAg
Y2FwaXRhbHMsIGFzIHNob3duIGhlcmUuDQoNClRoYXQgYWxzbyBnaXZlcyB5b3UgYW4gYWRkaXRp
b25hbCBOb3JtYXRpdmUgcmVmZXJlbmNlIGZvciA4MTc0Lg0KDQotLS0NCg0KT3B0aW9uYWwgcGx1
cmFscy4gSW4gRW5nbGlzaCB5b3UgZG8gbm90IG5lZWQgc2F5IHRoaW5ncyBsaWtlICJ1c2UgY29t
bW9uIHBpZWNlKHMpIi4gWW91IGNhbiB1c2UgdGhlIHVuZXF1aXZvY2FsIHBsdXJhbCBhbmQgaXQg
aXMgdW5kZXJzdG9vZCB0aGF0IGl0IGlzIG9wdGlvbmFsLiBTbyB5b3Ugc2hvdWxkIHNheSAidXNl
IGNvbW1vbiBwaWVjZXMiLg0KDQpQbGVhc2Ugcy8ocykvcy8gdGhyb3VnaG91dCB0aGUgZG9jdW1l
bnQuDQoNCi0tLQ0KDQpJbiB0aGUgQWJzdHJhY3QgeW91IGhhdmUgYSB1c2Ugb2YgIlBDRVAiIGJl
Zm9yZSB0aGUgZXhwYW5zaW9uIG9mIHRoZSB0ZXJtLg0KDQotLS0NCg0KVGhlIGxhc3Qgd29yZHMg
b2YgdGhlIEFic3RyYWN0IGFyZToNCiAgIHdoaWNoIGlzIGEgc3BlY2lhbCBjYXNlIGluIHRoZSBh
c3NvY2lhdGlvbiBwYXRoIGNvbXB1dGF0aW9uLg0KDQpUaGlzIGlzIHNsaWdodGx5IGNvbmZ1c2lu
ZyBiZWNhdXNlIHlvdSBoYXZlbid0IGVzdGFibGlzaGVkIHdoYXQgImFzc29jaWF0aW9uIHBhdGgg
Y29tcHV0YXRpb24iIGlzLiBJIHN1Z2dlc3QgeW91IG1pZ2h0IGNoYW5nZSB0aGUgQWJzdHJhY3Qg
dG8gcmVhZCBzb21ldGhpbmcgbGlrZToNCg0KICAgUmVzb3VyY2Ugc2hhcmluZyBpbiBhIG5ldHdv
cmsgbWVhbnMgdHdvIG9yIG1vcmUgTGFiZWwgU3dpdGNoZWQgUGF0aHMNCiAgIChMU1BzKSB1c2Ug
Y29tbW9uIHBpZWNlKHMpIG9mIHJlc291cmNlIGFsb25nIHRoZWlyIHBhdGhzLiBUaGlzIGNhbg0K
ICAgaGVscCBzYXZlIG5ldHdvcmsgcmVzb3VyY2UgYW5kIGlzIHVzZWZ1bCBpbiBzY2VuYXJpb3Mg
c3VjaCBhcyBMU1ANCiAgIHJlY292ZXJ5IG9yIHdoZW4gdHdvIExTUHMgZG8gbm90IG5lZWQgdG8g
YmUgYWN0aXZlIGF0IHRoZSBzYW1lIHRpbWUuDQogICBBIFBhdGggQ29tcHV0YXRpb24gRWxlbWVu
dCAoUENFKSBpcyByZXNwb25zaWJsZSBmb3IgcGF0aCBjb21wdXRhdGlvbg0KICAgd2l0aCBzdWNo
IHJlcXVpcmVtZW50Lg0KDQogICBFeGlzdGluZyBleHRlbnNpb25zIHRvIHRoZSBQYXRoIENvbXB1
dGF0aW9uIEVsZW1lbnQgUHJvdG9jb2wgKFBDRVApDQogICBhbGxvdyBvbmUgcGF0aCBjb21wdXRh
dGlvbiByZXF1ZXN0IGZvciBhbiBMU1AgdG8gYmUgYXNzb2NpYXRlZCB3aXRoDQogICBvdGhlciAo
ZXhpc3RpbmcpIExTUHMgdGhyb3VnaCB0aGUgdXNlIG9mIHRoZSBQQ0VQIEFzc29jaWF0aW9uIE9i
amVjdC4NCg0KICAgVGhlIHJlc291cmNlLXNoYXJpbmctYmFzZWQgcGF0aCBjb21wdXRhdGlvbg0K
ICAgd2l0aCBiZXR0ZXIgZWZmaWNpZW5jeSBjYW4gYmUgYWNoaWV2ZWQgdG9nZXRoZXIgd2l0aCB0
aGUgYXNzb2NpYXRpb24NCiAgIG9iamVjdCBpbiBQQ0VQLg0KDQogICBUaGlzIGRvY3VtZW50IGV4
dGVuZHMgUENFUCB0byBzdXBwb3J0IHJlc291cmNlIHNoYXJpbmctYmFzZWQgcGF0aA0KICAgY29t
cHV0YXRpb24gYXMgYW5vdGhlciB1c2Ugb2YgdGhlIEFzc29jaWF0aW9uIE9iamVjdC4NCg0KLS0t
DQoNClNlY3Rpb24gMQ0KDQpPTEQNCiAgIHByb3ZpZGVzIGFuIGFsdGVybmF0aXZlIHdheSBmb3Ig
cHJvdmlkaW5nIE5FVw0KICAgaXMgYSB3YXkgdG8gcHJvdmlkZQ0KRU5EDQoNClNpbmNlICJwYXNz
aXZlIiBhbmQgImFjdGl2ZSIgaGF2ZSBub3QgeWV0IGJlZW4gbWVudGlvbmVkLi4uDQpPTEQNCiAg
IFVubGVzcyBzcGVjaWZpZWQsIHRoaXMNCiAgIGRvY3VtZW50IGFzc3VtZXMgYSBQQ0UgbWVudGlv
bmVkIGlzIGEgc3RhdGVmdWwgUENFIChlaXRoZXIgcGFzc2l2ZQ0KICAgb3IgYWN0aXZlKS4NCk5F
Vw0KICAgVW5sZXNzIHNwZWNpZmllZCwgdGhpcw0KICAgZG9jdW1lbnQgYXNzdW1lcyBhIFBDRSBt
ZW50aW9uZWQgaXMgYSBzdGF0ZWZ1bCBQQ0UuDQpFTkQNCg0KLS0tDQoNCkdsb2JhbCBzZWFyY2gg
YW5kIHJlcGxhY2UgImEgTFNQIiB0byAiYW4gTFNQIg0KDQotLS0NCg0KSW4gU2VjdGlvbiAxIHlv
dSBoYXZlOg0KDQogICBGdXJ0aGVybW9yZSwgaWYgdGhlcmUgaXMgcmVzb3VyY2Ugc2hhcmluZyBi
ZXR3ZWVuIG5ldyBMU1AgYW5kDQogICBleGlzdGluZyBMU1AsIHRoZSB0d28gTFNQcyBjYW5ub3Qg
ZXhpc3Qgc2ltdWx0YW5lb3VzbHksIHRoZSBuZXcgTFNQDQogICB3aWxsIHJlcGxhY2UgdGhlIGV4
aXN0aW5nIExTUChzKS4NCg0KSSBrbm93IHdoeSB5b3Ugc2F5IHRoaXMsIGJlY2F1c2UgKG9idmlv
dXNseSkgeW91IGNhbid0IGRvdWJsZS1ib29rIHJlc291cmNlcy4gQnV0IEkgdGhpbmsgdGhhdCB5
b3UgY2FuIHJlbGF4IHRoZSByZXF1aXJlbWVudCBoZXJlIGVzcGVjaWFsbHkgZm9yIHRoZSBjYXNl
IG9mIHByb3RlY3Rpb24gYW5kIHJlc3RvcmF0aW9uLiBBbGwgeW91IGFjdHVhbGx5IG5lZWQgaXMg
dGhhdCBib3RoIExTUHMgY2FuJ3QgYmUgYWN0aXZlIChpLmUuLCBjYXJyeSB0cmFmZmljKSBhdCB0
aGUgc2FtZSB0aW1lLg0KDQpBY3R1YWxseSwgYSBsaXR0bGUgd2hpbGUgbGF0ZXIgeW91IHRhbGsg
YWJvdXQgbWFrZS1iZWZvcmUtYnJlYWsgd2hlcmUNCihvYnZpb3VzbHkpIGJvdGggTFNQcyBjYW4g
ZXhpc3QgYXQgdGhlIHNhbWUgdGltZS4NCg0KT2YgY291cnNlLCB0aGlzIGlzIG5vdCBhIGNvbmNl
cm4gZm9yIHRoZSBQQ0UsIGp1c3QgZm9yIHRoZSBMU1AgaGVhZC1lbmQsIHNvIHBlcmhhcHMgaXQg
aXNuJ3QgYSByZXF1aXJlbWVudCB0byBzdGF0ZSBoZXJlLiBNYXliZSBqdXN0IHN0YXRlIGl0IGFz
IGFuIG9ic2VydmF0aW9uIGluIHRoaXMgcGFyYWdyYXBoLg0KDQpCdXQgeW91IHdpbGwgbmVlZCB0
byBjbGVhbiB1cCB0aGUgaG9sZSB0ZXh0LCBJIHRoaW5rLiBGb3IgZXhhbXBsZSwgYSBsaXR0bGUg
bGF0ZXIgeW91IGhhdmU6DQogICBIb3dldmVyLCB0aGVzZSBvYmplY3RzDQogICBhcmUgdXNlZCB0
byBkZXNjcmliZSB0aGUgcmVsYXRpb25zaGlwIHdpdGggdHdvIHNpbXVsdGFuZW91cyBMU1BzLA0K
ICAgaW5zdGVhZCBvZiBhIG5ldyBvbmUgYW5kIGFuIG9sZCBvbmUsIHdoaWNoIGlzIGRpZmZlcmVu
dCB3aXRoIHRoZQ0KICAgb2JqZWN0IHByb3Bvc2VkIGluIHRoaXMgZHJhZnQuDQouLi5hbmQgeW91
IHNheSB0aGF0IGxpa2Ugb25seSBvbmUgb2YgdGhlIHR3byBMU1BzIHdpbGwgZXhpc3QgYXQgYW55
IHRpbWUsIGJ1dCAoYWdhaW4pIHRoYXQgaXMgbm90IGNvbnNpc3RlbnQgd2l0aCBNQkIgb3Igb3Ro
ZXIgZm9ybXMgb2YgcHJvdGVjdGlvbi4gU28gdGhpcyBjb3VsZCBiZSBjbGFyaWZpZWQgdG8gbWVh
biAidXNlZCB0byBjYXJyeSB0cmFmZmljIi4NCg0KLS0tDQoNCkluIFNlY3Rpb24gMQ0KDQogICBi
dXQgYWxzbyB0aGUgc2FtZSBzbGljZSBvZiBiYW5kd2lkdGggaW4gVERNIG5ldHdvcmtzLg0KDQpX
aGlsZSB0cnVlLCB0aGlzIGFwcGVhcnMgdG8gYmUgbGltaXRpbmcgdG8gVERNIHdoZXJlLCBJIHRo
aW5rLCB5b3UgaW50ZW5kIHRoZSBkb2N1bWVudCB0byBhcHBseSB0byBhbnkgdGVjaG5vbG9neS4g
U28gaG93IGFib3V0Og0KDQogICBidXQgYWxzbyB0aGUgc2FtZSBzbGljZSBvZiBiYW5kd2lkdGgg
aW4gdGhlIG5ldHdvcmsuDQoNCi0tLQ0KDQpUaHJvdWdob3V0IHRoZSBkb2N1bWVudCwgd2hlcmUg
eW91IGhhdmUgd3JpdHRlbiAidGhpcyBkcmFmdCIgc2F5ICJ0aGlzIGRvY3VtZW50IiB0byBmdXR1
cmUtcHJvb2YgeW91cnNlbGYgYWdhaW5zdCBiZWNvbWluZyBhbiBSRkMuDQoNClNpbWlsYXJseSBz
L3Byb3Bvc2VkL2RlZmluZWQvDQoNCi0tLQ0KDQpTZWN0aW9uIDENCg0KICAgQXMgbWVudGlvbmVk
IGluIFtSRkM4MjMxXSwgdGhlIFBMU1AtSUQgaXMgdW5pcXVlIGR1cmluZyBhIFBDRVANCiAgIHNl
c3Npb24gYmV0d2VlbiBQQ0MgYW5kIFBDRS4gU3VjaCBpZGVudGlmaWNhdGlvbiBpcyBoZWxwZnVs
IGluDQogICBzdXBwb3J0aW5nIHRoZSBhYm92ZSByZXNvdXJjZSBzaGFyaW5nIHJlcXVpcmVtZW50
IGZvcg0KICAgc3RhbmRhcmRpemF0aW9uIG9mIHN0YXRlZnVsIFBDRXMuICBXaXRoIGEgdW5pcXVl
IGlkZW50aWZpZXIsIHRoZQ0KICAgY29uZmlndXJhdGlvbiBvZiBQQ0NzIGlzIGdyZWF0bHkgc2lt
cGxpZmllZC4gSW5zdGVhZCBvZiBkZXRlcm1pbmluZw0KICAgYWxsIHRoZSByZXNvdXJjZXMgdG8g
YmUgc2hhcmVkLCB0aGUgUENDIGNvdWxkIHJlcXVlc3QgcmVzb3VyY2UNCiAgIHNoYXJpbmcgZGly
ZWN0bHkgZnJvbSBQQ0UuDQoNClRoaXMgbWlnaHQgYmUgYmV0dGVyIGFzLi4uDQoNCiAgIEFzIG1l
bnRpb25lZCBpbiBbUkZDODIzMV0sIHRoZSBQTFNQLUlEIHByb3ZpZGVzIGEgdW5pcXVlIGlkZW50
aWZpZXINCiAgIGZvciBhbiBMU1AgZHVyaW5nIGEgUENFUCBzZXNzaW9uIGJldHdlZW4gUENDIGFu
ZCBQQ0UuIFN1Y2gNCiAgIGlkZW50aWZpY2F0aW9uIGlzIGhlbHBmdWwgaW4gc3VwcG9ydGluZyB0
aGUgcmVzb3VyY2Ugc2hhcmluZw0KICAgcmVxdWlyZW1lbnQgZm9yIHN0YXRlZnVsIFBDRXMgYmVj
YXVzZSBpdCBncmVhdGx5IHNpbXBsaWZpZXMgdGhlDQogICBvcGVyYXRpb24gb2YgYSBQQ0MuIElu
c3RlYWQgb2YgdGhlIFBDQyBkZXRlcm1pbmluZyBhbGwgdGhlIHJlc291cmNlcw0KICAgdG8gYmUg
c2hhcmVkLCB0aGUgUENDIGNhbiByZXF1ZXN0IHRoYXQgdGhlIFBDRSBzaGFyZSB0aGUgcmVzb3Vy
Y2VzIG9mDQogICBhIHNwZWNpZmljIExTUDogdGhlIHN0YXRlZnVsIFBDRSBpcyBhYmxlIHRvIGRl
dGVybWluZSB0aG9zZSByZXNvdXJjZXMNCiAgIGl0c2VsZi4NCg0KLS0tDQoNClNlY3Rpb24gMQ0K
DQogICBJbiBhIG11bHRpLWxheWVyIG5ldHdvcmssIExhYmVsIFN3aXRjaGVkIFBhdGhzIChMU1Bz
KSBpbiBhIGxvd2VyDQoNCk5vIG5lZWQgdG8gZXhwYW5kICJMU1AiIGEgc2Vjb25kIHRpbWUsIGhl
cmUuDQoNCi0tLQ0KDQpUaGVyZSBpcyBzb21lIG1pc2FsaWdubWVudCBvZiB0aGUgc2lkZXMgb2Yg
dGhlIHN0YXRlZnVsIFBDRSBpbiBGaWd1cmUgMQ0KDQotLS0NCg0KU2VjdGlvbiAyLjENCg0KICAg
SWYgcmVzb3VyY2VzIGFyZSBzaGFyZWQNCiAgIGJldHdlZW4gdGhlIG9sZCBhbmQgbmV3IExTUHMs
IHRoZXJlIHdpbGwgYmUgc29tZSAnaW50ZXJydXB0aW9uJyB3aGVuDQogICB0aGUgdHJhZmZpYyBp
cyBzd2l0Y2hlZCBmcm9tIHRoZSBvbGQgTFNQIHRvIHRoZSBuZXcgTFNQLg0KDQphbmQgbGF0ZXIN
Cg0KICAgT24gdGhlIG90aGVyIGhhbmQsIGluIHNvbWUgc2NlbmFyaW9zIHRoZXJlIGFyZSBkaWZm
ZXJlbnQgcG9saWNpZXMsDQogICBmb3IgZXhhbXBsZSB0aGUgTFNQIHNob3VsZCBiZSByZXN0b3Jl
ZCB3aXRob3V0IGFueSBpbnRlcnJ1cHRpb24gd2l0aA0KICAgYmVzdCBlZmZvcnQuDQoNCldlbGws
IGRpZG4ndCBsaW5rIE4yLU4zIGp1c3QgZmFpbD8gU28gdGhlIGludGVycnVwdGlvbiBpcyBwcm9i
YWJseSBhbHJlYWR5IHF1aXRlIHNpZ25pZmljYW50Lg0KDQpZb3UgZG8gZ28gb24gdG8gc2F5DQog
ICBBbiBleGFtcGxlIGNhbiBiZSBmb3VuZCBpbiBGaWcuIDEgd2l0aG91dCBmYWlsdXJlIG9uDQog
ICBOMi1OMyBsaW5rLCBpbnN0ZWFkLCBhbiBvbmxpbmUgcmUtb3B0aW1pemF0aW9uIGlzIG5lZWRl
ZCBmb3IgdGhlDQogICB3b3JraW5nIExTUCAoTjEtTjItTjMpIGZyb20gdGhlIHN0YXRlZnVsIFBD
RS4NCg0KU28gSSB0aGluayB5b3UgbmVlZCB0byBzb3J0IG91dCB0d28gY2FzZXM6DQoxLiBSZXBh
aXIgYWZ0ZXIgZmFpbHVyZQ0KMi4gUmUtcm91dGluZyBmb3Igb3B0aW1pemF0aW9uIChvciBvdGhl
ciByZWFzb25zKQ0KDQpGb3IgdGhlc2UsIHlvdSBtYXkgd2FudCB0byBleHBsYWluIHRoZSBiZW5l
Zml0cyBvZiBzaGFyZWQgcmVzb3VyY2VzOg0KLSBtYXkgbm90IGJlIGVub3VnaCByZXNvdXJjZSBp
biB0aGUgbmV0d29yayB0byBzZXQgdXAgdGhlIDJuZCBMU1ANCi0gbWF5IHdhbnQgdG8ga2VlcCB0
aGUgMm5kIExTUCBvbiB0aGUgc2hvcnRlc3QgcGF0aCBhbmQgbWlnaHQgbm90IGJlDQogIGVub3Vn
aCByZXNvdXJjZXMgdG8gZG8gdGhhdA0KLSBtYXkgd2FudCB0byByZWR1Y2UgbmV0d29yayBwcm9n
cmFtbWluZyB0aW1lDQotIG1heSBoYXZlIHNvbWUgcmVzb3VyY2UgY29udGludWl0eSAoc3VjaCBh
cyBsYW1iZGEpIGNvbnN0cmFpbnRzIEJ1dCBhbHNvIHRoZSBkcmF3YmFja3M6DQotIHN3aXRjaC1v
dmVyIGluIE1CQiBtYXkgdGFrZSBsb25nZXIgYmVjYXVzZSBtdWx0aXBsZSBub2RlcyBoYXZlIHRv
DQogIGFjdCB0byBlZmZlY3QgdGhlIHN3aXRjaA0KLSBzd2l0Y2gtb3ZlciBjb29yZGluYXRpb24g
bWF5IGJlIGhhcmRlciBiZWNhdXNlIHN3aXRjaGluZyBub2RlcyBhcmUNCiAgcmVtb3RlIGZyb20g
dGhlIExTUCBlbmQtcG9pbnRzDQoNCllvdXIgZXhhbXBsZSBMU1AxIGFuZCBMU1AyIGRvIGhpZ2hs
aWdodCB0aGlzIHN1Y2Nlc3NmdWxseS4NCg0KLS0tDQoNCkkgd29uZGVyIHdoZXRoZXIgU2VjdGlv
biAyLjEgc2hvdWxkIGFsc28gaW5jbHVkZSBub3RpZnlpbmcgdGhlIFBDRSBvZiB3aGljaCByZXNv
dXJjZXMgdG8gYXZvaWQuIFRoYXQgd291bGQgY2VydGFpbmx5IGluY2x1ZGUgdGhlIGZhaWxlZCBs
aW5rIChJIGFtIG5vdCBzdXJlIHRoYXQgd2UgY2FuIGFzc3VtZSB0aGF0IHRoZSBQQ0UgaGFzIGxl
YXJuZWQgYWJvdXQgdGhlIGZhaWx1cmUgW3Rocm91Z2ggdGhlIElHUF0gYXMgZmFzdCBhcyB0aGUg
UENDIGxlYXJuZWQgYWJvdXQgaXQgdGhyb3VnaCBmYXVsdCBub3RpZmljYXRpb24gb3Igc2lnbmFs
bGluZyksIGJ1dCBpdCBtaWdodCBhbHNvIGluY2x1ZGUgbm9uLWZhaWxlZCBpbiBjYXNlIG9mIHJl
cm91dGluZyBbc3VjaCBhcyBiZWZvcmUgcGxhbm5lZCBtYWludGVuYW5jZV0pLg0KDQotLS0NCg0K
VGhlIHRvcCBvZiBMU1IgSDUgaGFzIGJlY29tZSBkZXRhY2hlZCBpbiBGaWd1cmUgMg0KDQotLS0N
Cg0KVGhlIGRpYWdvbmFscyBpbiBGaWd1cmUgMyBhcmUgaGFyZCBvbiB0aGUgZXllLiBDYW4geW91
IHVzZSBzaW5nbGUgbGluZXM/DQoNCk1heWJlLi4uDQoNCiAgICAgICAgICAgICAgICAgICAgICAg
ICArLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSsNCiAgICAgICAgICAgICAgICAgICAgICAgICB8ICAg
ICAgICBQLVBDRSAgICAgICAgIHwNCiAgICAgICAgICAgICAgICAgICAgICAgICArLS0tLS0tLS0t
LSstLS0tLS0tLS0tLSsNCiAgICAgICAgICAgICAgICAgICAgICAgIC8gICAgICAgICAgIHwgICAg
ICAgICAgICBcDQogICAgICAgICAgICAgICAgICAgICAgIC8gICAgICAgICAgICB8ICAgICAgICAg
ICAgIFwNCiAgICAgICAgICAgICAgICAgICAgICAvICAgICAgICAgICAgIHwgICAgICAgICAgICAg
IFwNCiAgICAgICAgICAgICAgICAgICAgIC8gICAgICAgICAgICAgIHwgICAgICAgICAgICAgICBc
DQogICAgICAgICAgICAgICAgICAgIC8gICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgIFwN
CiAgICAgICAgICAgICAgICAgICAvICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgIFwN
CiAgICAgICAgICAgKy0tLS0tLSsgICAgICAgICAgICAgKy0tLSstLS0rICAgICAgICAgICAgICAr
LS0tLS0tKw0KICAgICAgICAgICB8Qy1QQ0UxfCAgICAgICAgICAgICB8Qy1QQ0UyIHwgICAgICAg
ICAgICAgIHxDLVBDRTN8DQogICAgICAgICAgICstLS0tLS0rICAgICAgICAgICAgICstLS0tLS0t
KyAgICAgICAgICAgICAgKy0tLS0tLSsNCg0KICAgICBfX19fX19fX19fX19fXyAgICAgICBfX19f
X19fX19fX19fX19fX19fX19fICAgICAgX19fX19fX19fX19fX18NCiAgICAvICAgICAgICAgICAg
ICAgXCAgICAvICAgICAgICAgICAgICAgICAgICAgIFwgICAgLyAgICAgICAgICAgICAgXA0KICAg
fCArLS0tKyAgICAgKy0tLSsgfCAgfCAgKy0tLSsgICArLS0tKyAgICstLS0rIHwgIHwgKy0tLSsg
ICAgKy0tLSsgfA0KICAgfCB8IEEgKy0tLS0tKyBCICstKy0tKy0tKyBEICstLS0rIEUgKy0tLSsg
SCArLSstLSstKyBKICstLS0tKyBMIHwgfA0KICAgfCArLS0tKyAgICAgKy0tLSsgfCAgfCAgKy0t
LSsgICArLS0tKyAgICstLS0rIHwgIHwgKy0tLSsgICAgKy0rLSsgfA0KICAgfCAgICAgIFwgICAg
ICAgICAgfCAgfCAgICAgICAgIC8gICAgICAgICAgICAgXHwgIHwgICAgICAgICAgIC8gICAgfA0K
ICAgfCAgICAgICBcICAgICAgICAgfCAgfCAgICAgICAgLyAgICAgICAgICAgICAgICsgIHwgICAg
ICAgICAgLyAgICAgfA0KICAgfCAgICAgICAgXCAgICAgICAgfCAgfCAgICAgICAvICAgICAgICAg
ICAgICAgIHxcIHwgICAgICAgICAvICAgICAgfA0KICAgfCAgICAgICAgIFwgKy0tLSsgfCAgfCAg
Ky0tLSsgICAgICAgICAgICAgICAgIHwgXHwgICAgKy0tLSsgICAgICAgfA0KICAgfCAgICAgICAg
ICBcfCBDICstKy0tKy0tKyBHIHwgICAgICAgICAgICAgICAgIHwgICstLS0tfCBLIHwgICAgICAg
fA0KICAgfCAgICAgICAgICAgKy0tLSsgfCAgfCAgKy0tLSsgICAgICAgICAgICAgICAgIHwgIHwg
ICAgKy0tLSsgICAgICAgfA0KICAgIFxfX19fX19fX19fX19fX18vICAgIFxfX19fX19fX19fX19f
X19fX19fX19fLyAgICBcX19fX19fX19fX19fX18vDQoNCg0KLS0tDQoNCkluIDMuMSB5b3UgaGF2
ZToNCg0KICAgQSBzaGFyaW5nIGdyb3VwIHNob3VsZCBoYXZlIG11bHRpcGxlIExTUHMuIFRoZSBu
dW1iZXIgb2YgTFNQcyBhbmQNCiAgIHRoZSBjcml0ZXJpYSBmb3IgaG93IExTUHMgc2hhcmUgYW1v
bmcgZWFjaCBvdGhlciBhcmUgaW1wbGVtZW50YXRpb24NCiAgIGRlcGVuZGVudC4gTG9jYWwgcGF0
aCBjb21wdXRhdGlvbiBwb2xpY2llcyBhcHBseSB0byBkaWZmZXJlbnQgUENFDQogICBhbmQgUEND
LCBzb21lIGV4YW1wbGVzIGNhbiBiZSBmb3VuZCBpbiBzZWN0aW9uIDIuDQoNCkkgd29uZGVyIHdo
ZXRoZXIgImltcGxlbWVudGF0aW9uIGRlcGVuZGVudCIgbWlnaHQgYmUgYmV0dGVyIGFzICJkZXBl
bmRlbnQgb24gbG9jYWwgcG9saWN5Ii4NCg0KLS0tDQoNClNlY3Rpb24gMy4yIGhhczoNCg0KICAg
VGhlIFBDRVAgUmVzb3VyY2UgU2hhcmluZyBncm91cCBNVVNUIGNhcnJ5IHRoZSBmb2xsb3dpbmcg
VExWLiBJdCBNQVkNCiAgIGJlIGNhcnJpZWQgd2l0aGluIGEgUENSZXEgbWVzc2FnZSBmcm9tIHRo
ZSBuZXR3b3JrIGVsZW1lbnQgKG9yIG90aGVyDQogICBQQ0NzKSBzbyBhcyB0byBpbmRpY2F0ZSB0
aGUgZGVzaXJlZCByZXNvdXJjZSBzaGFyaW5nIHJlcXVpcmVtZW50cyB0bw0KICAgYmUgYXBwbGll
ZCBieSB0aGUgc3RhdGVmdWwgUENFIGR1cmluZyBwYXRoIGNvbXB1dGF0aW9uLg0KDQpJdCBmZWVs
cyBsaWtlIGEgY29udHJhZGljdGlvbiBiZXR3ZWVuIHRoZSAiTVVTVCIgYW5kIHRoZSAiTUFZIi4N
Cg0KLS0tDQoNClRoZSBmaWd1cmUgaW4gMy4yIHNlZW1zIHRvIGhhdmUgc3VycGx1cyBibGFuayBs
aW5lcyBpbnNlcnRlZC4NCg0KLS0tDQoNClNlY3Rpb24gMy4yDQoNCkZsYWdzIEwsIE4sIGFuZCBC
IGFsbCBzYXkgdGhhdCB0aGUgUENFICJzaG91bGQgcHJpb3JpdGlzZSIgc29tZXRoaW5nLg0KVGhh
dCBpcyBPSywgYnV0IHdoYXQgaGFwcGVucyBpZiBtb3JlIHRoYW4gb25lIGJpdCBpcyBzZXQ/IEhv
dyBhcmUgdGhlIHByaW9yaXRpc2F0aW9ucyBwcmlvcml0aXNlZD8NCg0KLS0tDQoNClNlY3Rpb24g
My4zDQoNCiAgICAgLSBJZiB0aGUgUmVzb3VyY2UgU2hhcmluZyBUTFYgaXMgdW5rbm93bi91bnN1
cHBvcnRlZCwgdGhlIFBDRSB3aWxsDQogICAgIGZvbGxvdyBwcm9jZWR1cmVzIGRlZmluZWQgaW4g
W1JGQzU0NDBdLiAgVGhhdCBpcywgdGhlIFBDRSBzZW5kcyBhDQogICAgIFBDRXJyIG1lc3NhZ2Ug
d2l0aCBlcnJvciB0eXBlIDMgb3IgNCAoVW5rbm93biAvIE5vdCBzdXBwb3J0ZWQNCiAgICAgb2Jq
ZWN0KSBhbmQgZXJyb3IgdmFsdWUgMSBvciAyICh1bmtub3duIC8gdW5zdXBwb3J0ZWQgb2JqZWN0
IGNsYXNzDQogICAgIC8gb2JqZWN0IHR5cGUpLCBhbmQgdGhlIHJlbGF0ZWQgcGF0aCBjb21wdXRh
dGlvbiByZXF1ZXN0IGlzDQogICAgIGRpc2NhcmRlZC4NCg0KICAgICAtIElmIFJlc291cmNlIFNo
YXJpbmcgVExWIGFyZSB1bmtub3duL3Vuc3VwcG9ydGVkIGFuZCB0aGUgUCBiaXQgaXMNCiAgICAg
c2V0LCB0aGUgUENFIE1VU1Qgc2VuZCBhIFBDRXJyIG1lc3NhZ2Ugd2l0aCBlcnJvciB0eXBlIDMg
b3IgNA0KICAgICAoVW5rbm93biAvIE5vdCBzdXBwb3J0ZWQgb2JqZWN0KSBhbmQgZXJyb3IgdmFs
dWUgNA0KICAgICAoVW5yZWNvZ25pemVkL1Vuc3VwcG9ydGVkIHBhcmFtZXRlciksIGFuZCB0aGUg
cmVsYXRlZCBwYXRoDQogICAgIGNvbXB1dGF0aW9uIHJlcXVlc3QgTVVTVCBiZSBkaXNjYXJkZWQg
YXMgZGVmaW5lZCBpbiBbUkZDNTQ0MF0uDQoNCk5vdyBJJ20gY29uZnVzZWQhIElzIHRoaXMgYSBU
TFYgb3IgYW4gT2JqZWN0PyBBbmQgaG93IGFyZSB0aGVzZSB0d28gcGFyYWdyYXBocyBjb21wYXRp
YmxlPyAoSSB0aGluayBpdCBpcyBhIFRMVi4pDQoNCi0tLQ0KDQpTZWN0aW9uIDMuMw0KDQogICAg
IC0gSWYgdGhlIHJlc291cmNlIHNoYXJpbmcgVExWIGlzIGV4dHJhY3RlZCBjb3JyZWN0bHksIHRo
ZSBQQ0UgTVVTVA0KICAgICBhcHBseSB0aGUgcmVxdWVzdGVkIHJlc291cmNlIHNoYXJpbmcgcmVx
dWlyZW1lbnQuDQoNClllcywgT0suIEV4Y2VwdCB0aGF0IHlvdSBoYXZlIHNhaWQgdGhpcyBpcyBz
dWJqZWN0IHRvIGxvY2FsIHBvbGljeSB3aGljaCBjb3VsZCAob2YgY291cnNlKSBtZWFuIHRoYXQg
bm8gc2hhcmluZyBpcyBkb25lIG9yIGV2ZW4gYXR0ZW1wdGVkLg0KDQotLS0NCg0KU2VjdGlvbiAz
LjMNCg0KQ2FuIHlvdSBleHBhbmQgUlNPIG9uIGZpcnN0IHVzZS4NCg0KLS0tDQoNCkFjY29yZGlu
ZyB0byBXRyBwb2xpY3ksIHlvdSdsbCBuZWVkIHRvIGluY2x1ZGUgYW4gIkltcGxlbWVudGF0aW9u
IFN0YXR1cyIgc2VjdGlvbi4gUHV0IGl0IGluIG5vdywgZXZlbiBpZiB5b3Ugb25seSBzYXkgdGhh
dCB5b3UgYXJlIG5vdCBhd2FyZSBvZiBhbnkgaW1wbGVtZW50YXRpb25zIGF0IHRoZSBtb21lbnQu
DQoNCi0tLQ0KDQpJJ2QgbG92ZSB0byBzZWUgYSBNYW5hZ2VhYmlsaXR5IENvbnNpZGVyYXRpb25z
IHNlY3Rpb24uIEl0IGlzbid0IGNvbXB1bHNvcnksIGJ1dCBpdCBoYXMgYmVjb21lIG5vcm1hbCBm
b3IgdGhlIFBDRSBXRy4gQW5kIHlvdSBoYXZlIHNvbWUgbWFuYWdlbWVudCB0aGluZ3MgdG8gdGFs
ayBhYm91dCBhcyB5b3UgbWVudGlvbiBwb2xpY2llcywgYW5kIGFsc28gYXMgeW91IGhhdmUgdG8g
Y29vcmRpbmF0ZSBhbGVydHMvZmF1bHQgcmVwb3J0cyBmcm9tIHRoZSBuZXR3b3JrLg0KDQpZb3Ug
YWxzbyBoYXZlICJUaGUgUlNPIGZsYWdzIG1heSBiZSBsb2NhbGx5IGNvbmZpZ3VyZWQuLi4iDQoN
Ci0tLQ0KDQpTZWN0aW9uIDUuMSB1c2VzICJUQkEiIGJ1dCB0aGUgdHh0IHVzZXMgIlRCRCIgUGxl
YXNlIGFsaWduIHRoZXNlLg0KDQotLS0NCg0KU2VjdGlvbiA1LjEgbmVlZHMgYSBsaXR0bGUgbW9y
ZSBkZXRhaWwgdG8gY29ycmVjdGx5IGRpcmVjdCBJQU5BIHRvIHRoZSByZWdpc3RyeS4gWW91IG5l
ZWQgc29tZSB0ZXh0IHN1Y2ggYXMuLi4NCg0KICAgSUFOQSBtYWludGFpbnMgYSByZWdpc3RyeSBj
YWxsZWQgdGhlICJQYXRoIENvbXB1dGF0aW9uIEVsZW1lbnQNCiAgIFByb3RvY29sIChQQ0VQKSBO
dW1iZXJzIiByZWdpc3RyeSB3aXRoIGEgc3VicmVnaXN0cnkgY2FsbGVkIHRoZQ0KICAgIkFzc29j
aWF0aW9uIFR5cGUgRmllbGQiIHN1YnJlZ2lzdHJ5LiAgSUFOQSBpcyByZXF1ZXN0ZWQgdG8gbWFr
ZQ0KICAgYW4gYXNzaWdubWVudCBmcm9tIHRoYXQgc3VicmVnaXN0cnkgYXMgZm9sbG93czoNCg0K
ICAgVHlwZSB8ICAgTmFtZSAgICAgICAgICAgICAgIHwgUmVmZXJlbmNlDQogICAtLS0tLSstLS0t
LS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0tLQ0KICAgVEJEMSB8IFNoYXJpbmcgQXNz
b2NpYXRpb24gIHwgW3RoaXMuSS1EXQ0KDQotLS0NCg0KVGhlIGhlYWRpbmcgb2YgU2VjdGlvbiA1
LjIgaGFzIGJlY29tZSBpbmRlbnRlZA0KDQotLS0NCg0KU2VjdGlvbiA1LjINCg0KVGhpcyBzZWN0
aW9uIHNlZW1zIGEgYml0IGp1bWJsZWQuIEhhdmUgYSBsb29rIGF0IFNlY3Rpb24gNy4yIG9mIGRy
YWZ0LWlldGYtcGNlLWFzc29jaWF0aW9uLWRpdmVyc2l0eS4NCg0KWW91IGhhdmUgbnVtYmVyZWQg
dGhlIGJpdHMgZnJvbSAwIGFzIHRoZSByaWdodC1oYW5kIGJpdCwgYnV0IHRoZSBmaWd1cmUgaW4g
c2VjdGlvbiAzLjIgaGFzIHRoZW0gbnVtYmVyZWQgaW4gdGhlIG9wcG9zaXRlIHdheS4gWW91IG5l
ZWQgdG8gYmUgY29uc2lzdGVudCBvciBpbmNsdWRlIGFuIGV4cGxhbmF0aW9uLiBBZ2FpbiwgbW9k
ZWxpbmcgb24gZHJhZnQtaWV0Zi1wY2UtIGFzc29jaWF0aW9uLWRpdmVyc2l0eSBtaWdodCBoZWxw
Lg0KDQotLS0NCg0KSXQgd291bGQgYmUgaGVscGZ1bCBpZiB5b3UgaW5jbHVkZWQgdGhlIGZpbGVu
YW1lIGluIHRoZSByZWZlcmVuY2UgW0gtUENFXS4gIEkgdGhpbmsgdGhpcyBpcyBkcmFmdC1pZXRm
LXBjZS1zdGF0ZWZ1bC1ocGNlLg0KDQotLS0NCg0KVGhlIENvbnRyaWJ1dG9ycyBzZWN0aW9uIGlz
IGhpZGluZyBpbnNpZGUgdGhlIEF1dGhvcnMnIEFkZHJlc3NlcyBhbmQgSSBtaXNzZWQgaXQuIEkg
dGhpbmsgdGhhdCBpcyBqdXN0IGFuIGluZGVudGF0aW9uIHByb2JsZW0uDQoNCg==


From nobody Fri Sep 27 01:27:36 2019
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CC091120800; Fri, 27 Sep 2019 01:27:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
To: <pce@ietf.org>, <pce-chairs@ietf.org>, <draft-li-pce-sr-path-segment@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.103.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <156957284282.12324.3302328973044803638.idtracker@ietfa.amsl.com>
Date: Fri, 27 Sep 2019 01:27:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/5TU44NGFtztH8VlxquzudVj23jQ>
Subject: [Pce] The PCE WG has placed draft-li-pce-sr-path-segment in state "Call For Adoption By WG Issued"
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Sep 2019 08:27:35 -0000

The PCE WG has placed draft-li-pce-sr-path-segment in state
Call For Adoption By WG Issued (entered by Julien Meuric)

The document is available at
https://datatracker.ietf.org/doc/draft-li-pce-sr-path-segment/


From nobody Fri Sep 27 03:08:45 2019
Return-Path: <noreply@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 44597120113; Fri, 27 Sep 2019 03:08:36 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Alvaro Retana via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-pce-lsp-control-request@ietf.org, Hariharan Ananthakrishnan <hari@netflix.com>, pce-chairs@ietf.org, pce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.103.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Alvaro Retana <aretana.ietf@gmail.com>
Message-ID: <156957891627.12410.17887218088455702680.idtracker@ietfa.amsl.com>
Date: Fri, 27 Sep 2019 03:08:36 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/VCaz5dScPhTe3fGdoNKGfaqNUmM>
Subject: [Pce] Alvaro Retana's No Objection on draft-ietf-pce-lsp-control-request-09: (with COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Sep 2019 10:08:37 -0000

Alvaro Retana has entered the following ballot position for
draft-ietf-pce-lsp-control-request-09: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-pce-lsp-control-request/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I have a substantive comment and then some nits/editorial notes.

(1) It seems to me that any PCE can request control of an LSP.  Even if the
sessions are authenticated and encrypted, how does the PCC determine if it's ok
for the requesting PCE to ask for control?  §8.1 says that an "implementation
SHOULD allow the operator to configure the policy based on which it honors the
request to control the LSPs".  If the implementation doesn't allow the
configuration of policy, then it is possible for a rogue PCE to ask for control
of an LSP, and for the PCC to grant it.  Why is the ability to configure this
policy not REQUIRED?  I believe this case should be explicitly called out as a
vulnerability.

(2) Abstract: s/A Path Computation Client (PCC) has set up LSPs/A Path
Computation Client (PCC) that has set up LSPs

(3) §1: s/which PCE to delegate the orphaned LSP/which PCE to delegate the
orphaned LSP to

(4) §1: s/a simple extension, by using this a PCE can/a simple extension, by
using it a PCE can

(5) In §3 the new C Flag is called the "LSP-Control Request Flag", but §7.1
only uses "LSP-Control".  Please be consistent; the more descriptive name is
probably better.



From nobody Fri Sep 27 11:33:26 2019
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BF49120AC1; Fri, 27 Sep 2019 11:33:00 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.103.0
Auto-Submitted: auto-generated
Precedence: bulk
Cc: The IESG <iesg@ietf.org>, db3546@att.com, Adrian Farrel <adrian@olddog.co.uk>, pce@ietf.org, pce-chairs@ietf.org, adrian@olddog.co.uk, draft-ietf-pce-stateful-pce-auto-bandwidth@ietf.org, rfc-editor@rfc-editor.org
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Message-ID: <156960918016.12440.198211388270262809.idtracker@ietfa.amsl.com>
Date: Fri, 27 Sep 2019 11:33:00 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/Q6aaeqvQxXTSHTSRgpZp48rtKOQ>
Subject: [Pce] Protocol Action: 'PCEP Extensions for MPLS-TE LSP Automatic Bandwidth Adjustment with Stateful PCE' to Proposed Standard (draft-ietf-pce-stateful-pce-auto-bandwidth-12.txt)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Sep 2019 18:33:09 -0000

The IESG has approved the following document:
- 'PCEP Extensions for MPLS-TE LSP Automatic Bandwidth Adjustment with
   Stateful PCE'
  (draft-ietf-pce-stateful-pce-auto-bandwidth-12.txt) as Proposed Standard

This document is the product of the Path Computation Element Working Group.

The IESG contact persons are Alvaro Retana, Martin Vigoureux and Deborah
Brungard.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-pce-auto-bandwidth/





Technical Summary

The Path Computation Element Communication Protocol (PCEP) provides
mechanisms for Path Computation Elements (PCEs) to perform path
computations in response to Path Computation Clients (PCCs) requests.
The Stateful PCE extensions allow stateful control of Multi-Protocol
Label Switching (MPLS) Traffic Engineering Label Switched Paths (TE
LSPs) using PCEP.

The automatic bandwidth feature allows automatic and dynamic
adjustment of the TE LSP bandwidth reservation based on the volume of
traffic flowing through the LSP.  This document describes PCEP
extensions for automatic bandwidth adjustment when employing an
Active Stateful PCE for both PCE-Initiated and PCC-Initiated LSPs.

Working Group Summary

There was nothing unusual in the working group processing of this document.

Before the document was adopted there were concerns regarding scaling and scope of the work.
The version of this I-D that was adopted handled these and had broad support from the WG at
the time of adoption and later during WGLC. There is consensus in the WG to publish this work. 

Document Quality

The authors report "a few" implementations supporting this feature. Some, they say,
are more complete than others.

A few people in the working group performed substantial reviews, but most of the
working group was quiet. During working group last call a good number of people
reported that they had read the document and supported publication.


Personnel

   Who is the Document Shepherd for this document?  Adrian Farrel
   Who is the Responsible Area Director?  Deborah Brungard


From nobody Fri Sep 27 18:29:09 2019
Return-Path: <zhuangshunwan@huawei.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F21F812006B for <pce@ietfa.amsl.com>; Fri, 27 Sep 2019 18:29:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sm1UtkmLViKH for <pce@ietfa.amsl.com>; Fri, 27 Sep 2019 18:29:05 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A47AB120026 for <pce@ietf.org>; Fri, 27 Sep 2019 18:29:05 -0700 (PDT)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 61523678F43D342E95FE for <pce@ietf.org>; Sat, 28 Sep 2019 02:29:03 +0100 (IST)
Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.408.0; Sat, 28 Sep 2019 02:29:03 +0100
Received: from NKGEML515-MBS.china.huawei.com ([169.254.5.62]) by nkgeml414-hub.china.huawei.com ([10.98.56.75]) with mapi id 14.03.0439.000; Sat, 28 Sep 2019 09:28:52 +0800
From: Zhuangshunwan <zhuangshunwan@huawei.com>
To: "julien.meuric@orange.com" <julien.meuric@orange.com>, "pce@ietf.org" <pce@ietf.org>
Thread-Topic: [Pce] Adoption of draft-li-pce-sr-path-segment?
Thread-Index: AQHVc71hanmlIHGCx06kvbHPvCsQq6dAT8hQ
Date: Sat, 28 Sep 2019 01:28:51 +0000
Message-ID: <19AB2A007F56DB4E8257F949A2FB9858E5CF71A7@NKGEML515-MBS.china.huawei.com>
References: <29713_1569428443_5D8B93DB_29713_96_1_6698a3d9-4ace-57fd-3b7c-7be23f135631@orange.com>
In-Reply-To: <29713_1569428443_5D8B93DB_29713_96_1_6698a3d9-4ace-57fd-3b7c-7be23f135631@orange.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.130.202.166]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/GBYItjtLVsEbVWDItw4rLjGgpnk>
Subject: Re: [Pce] Adoption of draft-li-pce-sr-path-segment?
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Sep 2019 01:29:08 -0000

Hi WG,

I support the adoption of this draft.

Best Regards,
Shunwan

-----Original Message-----
From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of julien.meuric@orange.c=
om
Sent: Thursday, September 26, 2019 12:21 AM
To: pce@ietf.org
Subject: [Pce] Adoption of draft-li-pce-sr-path-segment?

Hi PCE WG,

In our adoption poll queue, draft-li-pce-sr-path-segment has been there for=
 a little while, after it was discussed face to face. We would now like you=
 to voice your opinion on the list: do you think this I-D can be the founda=
tion for a PCE WG's work item?

Please send your feedback to the PCE mailing list, including any comment yo=
u would like to share, especially if you think the WG should not adopt it. =
This poll will end on October 9.

Thanks,

Dhruv & Julien


___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou =
copies sans autorisation. Si vous avez recu ce message par erreur, veuillez=
 le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Le=
s messages electroniques etant susceptibles d'alteration, Orange decline to=
ute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation 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 dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.

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


From nobody Sat Sep 28 08:52:56 2019
Return-Path: <jie.dong@huawei.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4917312004D for <pce@ietfa.amsl.com>; Sat, 28 Sep 2019 08:52:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bUj96-FC2BKB for <pce@ietfa.amsl.com>; Sat, 28 Sep 2019 08:52:49 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F349120047 for <pce@ietf.org>; Sat, 28 Sep 2019 08:52:49 -0700 (PDT)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 6B68DCF766E6C0DFAD91 for <pce@ietf.org>; Sat, 28 Sep 2019 16:52:46 +0100 (IST)
Received: from lhreml717-chm.china.huawei.com (10.201.108.68) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.408.0; Sat, 28 Sep 2019 16:52:46 +0100
Received: from lhreml717-chm.china.huawei.com (10.201.108.68) by lhreml717-chm.china.huawei.com (10.201.108.68) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Sat, 28 Sep 2019 16:52:46 +0100
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml717-chm.china.huawei.com (10.201.108.68) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1713.5 via Frontend Transport; Sat, 28 Sep 2019 16:52:45 +0100
Received: from NKGEML515-MBS.china.huawei.com ([169.254.5.62]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0439.000; Sat, 28 Sep 2019 23:52:35 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: Hariharan Ananthakrishnan <hari@netflix.com>, "Chengli (Cheng Li)" <chengli13@huawei.com>, Mach Chen <mach.chen@huawei.com>, "chengweiqiang@chinamobile.com" <chengweiqiang@chinamobile.com>, Lizhenbin <lizhenbin@huawei.com>, "rgandhi@cisco.com" <rgandhi@cisco.com>, "xiong.quan@zte.com.cn" <xiong.quan@zte.com.cn>
CC: "pce@ietf.org" <pce@ietf.org>
Thread-Topic: IPR Poll on draft-li-pce-sr-path-segment-08
Thread-Index: AQHVc8mcKYIEXiJ12UCTZryP/F6KFKdBQZbQ
Date: Sat, 28 Sep 2019 15:52:34 +0000
Message-ID: <76CD132C3ADEF848BD84D028D243C927CD1F5697@NKGEML515-MBS.china.huawei.com>
References: <CAL70W4q8DctbRNTFMWzKELNZORgL5OuStFJgFOx1tw9tq3+jGA@mail.gmail.com>
In-Reply-To: <CAL70W4q8DctbRNTFMWzKELNZORgL5OuStFJgFOx1tw9tq3+jGA@mail.gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.45.50.62]
Content-Type: multipart/alternative; boundary="_000_76CD132C3ADEF848BD84D028D243C927CD1F5697NKGEML515MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/lDI2gtbQ2Rjscae4fMx9GZAklEg>
Subject: Re: [Pce] IPR Poll on draft-li-pce-sr-path-segment-08
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Sep 2019 15:52:52 -0000

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

SGkgSGFyaSBhbmQgV0csDQoNCkkgYW0gbm90IGF3YXJlIG9mIGFueSBJUFIgYXBwbGljYWJsZSB0
byB0aGlzIGRyYWZ0IHRoYXQgc2hvdWxkIGJlIGRpc2Nsb3NlZCBpbiBhY2NvcmRhbmNlIHdpdGgg
SUVURiBJUFIgcnVsZXMuDQoNCkJlc3QgcmVnYXJkcywNCkppZQ0KDQpGcm9tOiBIYXJpaGFyYW4g
QW5hbnRoYWtyaXNobmFuIFttYWlsdG86aGFyaUBuZXRmbGl4LmNvbV0NClNlbnQ6IFRodXJzZGF5
LCBTZXB0ZW1iZXIgMjYsIDIwMTkgMTo0OSBBTQ0KVG86IENoZW5nbGkgKENoZW5nIExpKSA8Y2hl
bmdsaTEzQGh1YXdlaS5jb20+OyBNYWNoIENoZW4gPG1hY2guY2hlbkBodWF3ZWkuY29tPjsgY2hl
bmd3ZWlxaWFuZ0BjaGluYW1vYmlsZS5jb207IERvbmdqaWUgKEppbW15KSA8amllLmRvbmdAaHVh
d2VpLmNvbT47IExpemhlbmJpbiA8bGl6aGVuYmluQGh1YXdlaS5jb20+OyByZ2FuZGhpQGNpc2Nv
LmNvbTsgeGlvbmcucXVhbkB6dGUuY29tLmNuDQpDYzogcGNlQGlldGYub3JnDQpTdWJqZWN0OiBJ
UFIgUG9sbCBvbiBkcmFmdC1saS1wY2Utc3ItcGF0aC1zZWdtZW50LTA4DQoNCg0KSGkgQXV0aG9y
cywNCg0KDQoNCkluIHByZXBhcmF0aW9uIGZvciBXb3JraW5nIEdyb3VwIGxhc3QgY2FsbCBvbiB0
aGlzIGRyYWZ0LCBJJ2QgbGlrZSBhbGwNCg0KYXV0aG9ycyBhbmQgY29udHJpYnV0b3JzIHRvIGNv
bmZpcm0gb24gdGhlIGxpc3QgdGhhdCB0aGV5IGFyZSBpbiBjb21wbGlhbmNlDQoNCndpdGggSUVU
RiBJUFIgcnVsZXMuDQoNCg0KDQpQbGVhc2UgcmVzcG9uZCAoY29weWluZyB0aGUgbWFpbGluZyBs
aXN0KSB0byBzYXkgb25lIG9mOg0KDQoNCg0KSSBhbSBub3QgYXdhcmUgb2YgYW55IElQUiBhcHBs
aWNhYmxlIHRvIHRoaXMgZHJhZnQgdGhhdCBzaG91bGQgYmUgZGlzY2xvc2VkDQoNCmluIGFjY29y
ZGFuY2Ugd2l0aCBJRVRGIElQUiBydWxlcy4NCg0KDQoNCkkgYW0gYXdhcmUgb2YgSVBSIGFwcGxp
Y2FibGUgdG8gdGhpcyBkcmFmdCwgYW5kIGl0IGhhcyBhbHJlYWR5IGJlZW4NCg0KZGlzY2xvc2Vk
IHRvIHRoZSBJRVRGLg0KDQoNCg0KSSBhbSBhd2FyZSBvZiBJUFIgYXBwbGljYWJsZSB0byB0aGlz
IGRyYWZ0LCBidXQgdGhhdCBoYXMgbm90IHlldCBiZWVuDQoNCmRpc2Nsb3NlZCB0byB0aGUgSUVU
Ri4gSSB3aWxsIHdvcmsgdG8gZW5zdXJlIHRoYXQgaXQgd2lsbCBiZSBkaXNjbG9zZWQgaW4gYQ0K
DQp0aW1lbHkgbWFubmVyLg0KDQoNCg0KVGhhbmtzLA0KDQotIEhhcmkNCg==

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
5a6L5L2TOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtm
b250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0
O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUg
MiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJcQOWui+S9kyI7DQoJ
cGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5
OlZlcmRhbmE7DQoJcGFub3NlLTE6MiAxMSA2IDQgMyA1IDQgNCAyIDQ7fQ0KLyogU3R5bGUgRGVm
aW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7
bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjEyLjBwdDsN
Cglmb250LWZhbWlseTrlrovkvZM7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28t
c3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6IzA1NjNDMTsNCgl0ZXh0LWRlY29yYXRpb246dW5k
ZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5
bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Izk1NEY3MjsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJs
aW5lO30NCnByZQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IkhU
TUwg6aKE6K6+5qC85byPIENoYXIiOw0KCW1hcmdpbjowY207DQoJbWFyZ2luLWJvdHRvbTouMDAw
MXB0Ow0KCWZvbnQtc2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk65a6L5L2TO30NCnNwYW4uSFRN
TENoYXINCgl7bXNvLXN0eWxlLW5hbWU6IkhUTUwg6aKE6K6+5qC85byPIENoYXIiOw0KCW1zby1z
dHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiSFRNTCDpooTorr7moLzlvI8iOw0K
CWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTkNCgl7bXNvLXN0
eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2Vy
aWY7DQoJY29sb3I6IzFGNDk3RDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpl
eHBvcnQtb25seTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQpAcGFnZSBX
b3JkU2VjdGlvbjENCgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA5MC4w
cHQgNzIuMHB0IDkwLjBwdDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24x
O30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRz
IHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtp
ZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1h
cCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRp
Zl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IlpILUNOIiBsaW5rPSIjMDU2M0MxIiB2bGluaz0i
Izk1NEY3MiI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj5IaSBIYXJpIGFu
ZCBXRyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBs
YW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0i
Zm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2Vy
aWY7Y29sb3I6IzFGNDk3RCI+SSBhbSBub3QgYXdhcmUgb2YgYW55IElQUiBhcHBsaWNhYmxlIHRv
IHRoaXMgZHJhZnQgdGhhdCBzaG91bGQgYmUgZGlzY2xvc2VkIGluIGFjY29yZGFuY2Ugd2l0aCBJ
RVRGIElQUiBydWxlcy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVT
IiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+QmVzdCByZWdhcmRzLDxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9u
dC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7
Y29sb3I6IzFGNDk3RCI+SmllPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVm
dDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQiPg0KPGRpdj4NCjxk
aXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0UxRTFFMSAxLjBwdDtwYWRk
aW5nOjMuMHB0IDBjbSAwY20gMGNtIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIGxh
bmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxp
YnJpJnF1b3Q7LHNhbnMtc2VyaWYiPkZyb206PC9zcGFuPjwvYj48c3BhbiBsYW5nPSJFTi1VUyIg
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90Oyxz
YW5zLXNlcmlmIj4gSGFyaWhhcmFuIEFuYW50aGFrcmlzaG5hbiBbbWFpbHRvOmhhcmlAbmV0Zmxp
eC5jb21dDQo8YnI+DQo8Yj5TZW50OjwvYj4gVGh1cnNkYXksIFNlcHRlbWJlciAyNiwgMjAxOSAx
OjQ5IEFNPGJyPg0KPGI+VG86PC9iPiBDaGVuZ2xpIChDaGVuZyBMaSkgJmx0O2NoZW5nbGkxM0Bo
dWF3ZWkuY29tJmd0OzsgTWFjaCBDaGVuICZsdDttYWNoLmNoZW5AaHVhd2VpLmNvbSZndDs7IGNo
ZW5nd2VpcWlhbmdAY2hpbmFtb2JpbGUuY29tOyBEb25namllIChKaW1teSkgJmx0O2ppZS5kb25n
QGh1YXdlaS5jb20mZ3Q7OyBMaXpoZW5iaW4gJmx0O2xpemhlbmJpbkBodWF3ZWkuY29tJmd0Ozsg
cmdhbmRoaUBjaXNjby5jb207IHhpb25nLnF1YW5AenRlLmNvbS5jbjxicj4NCjxiPkNjOjwvYj4g
cGNlQGlldGYub3JnPGJyPg0KPGI+U3ViamVjdDo8L2I+IElQUiBQb2xsIG9uIGRyYWZ0LWxpLXBj
ZS1zci1wYXRoLXNlZ21lbnQtMDg8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHByZT48c3BhbiBsYW5nPSJFTi1VUyIgc3R5
bGU9ImZvbnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMjEy
NTI5Ij5IaSBBdXRob3JzLDxvOnA+PC9vOnA+PC9zcGFuPjwvcHJlPg0KPHByZT48c3BhbiBsYW5n
PSJFTi1VUyIgc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssc2Fucy1zZXJp
Zjtjb2xvcjojMjEyNTI5Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNw
YW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7LHNh
bnMtc2VyaWY7Y29sb3I6IzIxMjUyOSI+SW4gcHJlcGFyYXRpb24gZm9yIFdvcmtpbmcgR3JvdXAg
bGFzdCBjYWxsIG9uIHRoaXMgZHJhZnQsIEknZCBsaWtlIGFsbDxvOnA+PC9vOnA+PC9zcGFuPjwv
cHJlPg0KPHByZT48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1Zl
cmRhbmEmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMjEyNTI5Ij5hdXRob3JzIGFuZCBjb250cmli
dXRvcnMgdG8gY29uZmlybSBvbiB0aGUgbGlzdCB0aGF0IHRoZXkgYXJlIGluIGNvbXBsaWFuY2U8
bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJm
b250LWZhbWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzIxMjUyOSI+
d2l0aCBJRVRGIElQUiBydWxlcy48bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4g
bGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7LHNhbnMt
c2VyaWY7Y29sb3I6IzIxMjUyOSI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wcmU+DQo8cHJl
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZxdW90
OyxzYW5zLXNlcmlmO2NvbG9yOiMyMTI1MjkiPlBsZWFzZSByZXNwb25kIChjb3B5aW5nIHRoZSBt
YWlsaW5nIGxpc3QpIHRvIHNheSBvbmUgb2Y6PG86cD48L286cD48L3NwYW4+PC9wcmU+DQo8cHJl
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZxdW90
OyxzYW5zLXNlcmlmO2NvbG9yOiMyMTI1MjkiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcHJl
Pg0KPHByZT48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1ZlcmRh
bmEmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMjEyNTI5Ij5JIGFtIG5vdCBhd2FyZSBvZiBhbnkg
SVBSIGFwcGxpY2FibGUgdG8gdGhpcyBkcmFmdCB0aGF0IHNob3VsZCBiZSBkaXNjbG9zZWQ8bzpw
PjwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250
LWZhbWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzIxMjUyOSI+aW4g
YWNjb3JkYW5jZSB3aXRoIElFVEYgSVBSIHJ1bGVzLjxvOnA+PC9vOnA+PC9zcGFuPjwvcHJlPg0K
PHByZT48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEm
cXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMjEyNTI5Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3ByZT4NCjxwcmU+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtW
ZXJkYW5hJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzIxMjUyOSI+SSBhbSBhd2FyZSBvZiBJUFIg
YXBwbGljYWJsZSB0byB0aGlzIGRyYWZ0LCBhbmQgaXQgaGFzIGFscmVhZHkgYmVlbjxvOnA+PC9v
OnA+PC9zcGFuPjwvcHJlPg0KPHByZT48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtZmFt
aWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMjEyNTI5Ij5kaXNjbG9z
ZWQgdG8gdGhlIElFVEYuPG86cD48L286cD48L3NwYW4+PC9wcmU+DQo8cHJlPjxzcGFuIGxhbmc9
IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZxdW90OyxzYW5zLXNlcmlm
O2NvbG9yOiMyMTI1MjkiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcHJlPg0KPHByZT48c3Bh
biBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssc2Fu
cy1zZXJpZjtjb2xvcjojMjEyNTI5Ij5JIGFtIGF3YXJlIG9mIElQUiBhcHBsaWNhYmxlIHRvIHRo
aXMgZHJhZnQsIGJ1dCB0aGF0IGhhcyBub3QgeWV0IGJlZW48bzpwPjwvbzpwPjwvc3Bhbj48L3By
ZT4NCjxwcmU+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtWZXJk
YW5hJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzIxMjUyOSI+ZGlzY2xvc2VkIHRvIHRoZSBJRVRG
LiBJIHdpbGwgd29yayB0byBlbnN1cmUgdGhhdCBpdCB3aWxsIGJlIGRpc2Nsb3NlZCBpbiBhPG86
cD48L286cD48L3NwYW4+PC9wcmU+DQo8cHJlPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9u
dC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMyMTI1MjkiPnRp
bWVseSBtYW5uZXIuPG86cD48L286cD48L3NwYW4+PC9wcmU+DQo8cHJlPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZxdW90OyxzYW5zLXNlcmlmO2Nv
bG9yOiMyMTI1MjkiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcHJlPg0KPHByZT48c3BhbiBs
YW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssc2Fucy1z
ZXJpZjtjb2xvcjojMjEyNTI5Ij5UaGFua3MsPG86cD48L286cD48L3NwYW4+PC9wcmU+DQo8cHJl
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZxdW90
OyxzYW5zLXNlcmlmO2NvbG9yOiMyMTI1MjkiPi0gSGFyaTwvc3Bhbj48c3BhbiBsYW5nPSJFTi1V
UyIgc3R5bGU9ImNvbG9yOiMyMTI1MjkiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcHJlPg0KPC9kaXY+
DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_76CD132C3ADEF848BD84D028D243C927CD1F5697NKGEML515MBSchi_--


From nobody Mon Sep 30 02:47:12 2019
Return-Path: <noreply@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C2F61201B7; Mon, 30 Sep 2019 02:46:58 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Francesca Palombini via Datatracker <noreply@ietf.org>
To: <gen-art@ietf.org>
Cc: draft-ietf-pce-lsp-control-request.all@ietf.org, pce@ietf.org, ietf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.103.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Francesca Palombini <francesca.palombini@ericsson.com>
Message-ID: <156983681789.492.9278022227990286693@ietfa.amsl.com>
Date: Mon, 30 Sep 2019 02:46:58 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/J4LGVStxk2PEaoO42Fpi7B9UQC4>
Subject: [Pce] Genart telechat review of draft-ietf-pce-lsp-control-request-09
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Sep 2019 09:46:58 -0000

Reviewer: Francesca Palombini
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-pce-lsp-control-request-09
Reviewer: Francesca Palombini
Review Date: 2019-09-30
IETF LC End Date: None
IESG Telechat date: 2019-10-03

Summary: This draft is ready for publication as a Standards Track RFC

Major issues: N/A

Minor issues: N/A

Nits/editorial comments: N/A

Thanks for addressing all my comments for v-08!


From nobody Mon Sep 30 02:53:03 2019
Return-Path: <noreply@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C5D80120142; Mon, 30 Sep 2019 02:53:01 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Martin Vigoureux via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-pce-lsp-control-request@ietf.org, Hariharan Ananthakrishnan <hari@netflix.com>, pce-chairs@ietf.org, hari@netflix.com, pce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.103.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Martin Vigoureux <martin.vigoureux@nokia.com>
Message-ID: <156983718180.546.10162334928586461765.idtracker@ietfa.amsl.com>
Date: Mon, 30 Sep 2019 02:53:01 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/6cf-dS39T5Kqu_Ux33iyuPqkPXw>
Subject: [Pce] Martin Vigoureux's No Objection on draft-ietf-pce-lsp-control-request-09: (with COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Sep 2019 09:53:02 -0000

Martin Vigoureux has entered the following ballot position for
draft-ietf-pce-lsp-control-request-09: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-pce-lsp-control-request/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Hi,

thank you for this document.
This document indicates:
"...MUST NOT trigger the error condition for unknown PLSP-ID in an LSP update
request as per [RFC8231] ...". "...MUST NOT trigger the error handling as
specified in [RFC8231] ...".

Yet, it also says:
The procedures for granting and relinquishing control of the LSPs are specified
in accordance with the specification [RFC8231].

So
1/ it seems to me that the latter sentence, considering the first two, is not
strictly correct. 2/ the rationale is well described, so I'm fine with not
respecting the original rules of 8231, but then I wonder if this document
shouldn't update 8231.



From nobody Mon Sep 30 04:29:03 2019
Return-Path: <dhruv.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBCF112022C; Mon, 30 Sep 2019 04:28:52 -0700 (PDT)
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, FREEMAIL_FROM=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=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 SsMWwjdDlsxV; Mon, 30 Sep 2019 04:28:51 -0700 (PDT)
Received: from mail-io1-xd2f.google.com (mail-io1-xd2f.google.com [IPv6:2607:f8b0:4864:20::d2f]) (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 E0C2E120227; Mon, 30 Sep 2019 04:28:50 -0700 (PDT)
Received: by mail-io1-xd2f.google.com with SMTP id b19so9198700iob.4; Mon, 30 Sep 2019 04:28:50 -0700 (PDT)
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=u0hL0tQAXZflckLy9pNMSdkAttvZrsk+y0KE17CMEF4=; b=uHxJGIkE0LEz9zwMYvHBkiFsZmnhkKHRY76aVqcQUE5MJHslSDKgbxJO+qHThfF8OR w1YT+KPIIN8/jJWG3ljESODOJkg9u6ichGfDkeD8xrRG1B26OGEys4EyNQeRdqbpLvh3 FV7So4q+Z35mvyvngJDQwsFu00nlNww4u87eQ3Y9IpvHWPccy5uemJ50dtfYn8kdpJgp mjj5Z+GMYRiYO+d7gLunDdnJ2djsRfACFFaw3UJiQ+PgO1s50i5zeh19n1NZaGFKL/QT cMxVUYCuGGMFQFNYNOnA8Dqn4885QvkwcXacrDk+Rz+mArmBw/sZPsIE+vxcydJUkwRU 32aQ==
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=u0hL0tQAXZflckLy9pNMSdkAttvZrsk+y0KE17CMEF4=; b=qsmQmWDOjiN8adqj2ErGHtzVM6v4uLWx94exeOH2l1oFO6lO9iTN7Ku/Twxb3A+uji oPPIz1bk8b9RCkfczazm2SexGFUGtzGUDy/E2yuyeTJXGBgf6t4+Fdo/Os2o68uSc7mK 7PW6Wd41NSjNrix4yMBn5MCJujmVOolP8nn6UQXoJ1yvDD6LAxRvBCPOD9EGAipBLirK K7YoMRfHCcg6dR5cC8JFtNPPffxTxza+OrEgPQi/di/6C/CFaPVXu2cK4QI2w8P6jPRu iF45ArCYFzUj6h1XJSKVmvbezVnQQ13G2H72AK/wJkr9ZsZW9awu4oB1TJTgDQA1BgAF ic/A==
X-Gm-Message-State: APjAAAX6lSWGeKkQeUk+9J4kM0LWs3Un6wthlEDRjhji0QxZunDZCQrV pP+o4B2f4UgkXwOZp8viCLHhgoxSHwsOQHp7ek0=
X-Google-Smtp-Source: APXvYqxaQJCe/KCSEozjV1txubRRwNHQX9pJJCOchadrTZPuBEepEg4N3wH8A25jB1VUH46xahzDADdzcoAzO7JZVT0=
X-Received: by 2002:a5d:9457:: with SMTP id x23mr4701312ior.14.1569842929914;  Mon, 30 Sep 2019 04:28:49 -0700 (PDT)
MIME-Version: 1.0
References: <156983718180.546.10162334928586461765.idtracker@ietfa.amsl.com>
In-Reply-To: <156983718180.546.10162334928586461765.idtracker@ietfa.amsl.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Mon, 30 Sep 2019 16:58:13 +0530
Message-ID: <CAB75xn7y2CrmW9ApEuRbjZD2P1b-A=xktr-hHZp-H1x-f1ggAA@mail.gmail.com>
To: Martin Vigoureux <martin.vigoureux@nokia.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pce-lsp-control-request@ietf.org,  Hariharan Ananthakrishnan <hari@netflix.com>, pce-chairs <pce-chairs@ietf.org>, pce@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/bjAD_SygV3mkl74KYoxSrCanuJY>
Subject: Re: [Pce] Martin Vigoureux's No Objection on draft-ietf-pce-lsp-control-request-09: (with COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Sep 2019 11:28:53 -0000

Hi Martin,

Thanks for your review, request authors to chime in as needed.

On Mon, Sep 30, 2019 at 3:23 PM Martin Vigoureux via Datatracker
<noreply@ietf.org> wrote:
>
> Martin Vigoureux has entered the following ballot position for
> draft-ietf-pce-lsp-control-request-09: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-pce-lsp-control-request/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Hi,
>
> thank you for this document.
> This document indicates:
> "...MUST NOT trigger the error condition for unknown PLSP-ID in an LSP update
> request as per [RFC8231] ...". "...MUST NOT trigger the error handling as
> specified in [RFC8231] ...".
>
> Yet, it also says:
> The procedures for granting and relinquishing control of the LSPs are specified
> in accordance with the specification [RFC8231].
>

Maybe we can add - "...unless explicitly set aside in this document."

> So
> 1/ it seems to me that the latter sentence, considering the first two, is not
> strictly correct. 2/ the rationale is well described, so I'm fine with not
> respecting the original rules of 8231, but then I wonder if this document
> shouldn't update 8231.
>
>

I am not sure if this rises to the level of "update" (as I understand
it and not taking the ongoing discussion on the topic); to me it is a
normal extension of a protocol 'business as usual'!

I think maybe it is time for some AD guidance on this :)

Thanks!
Dhruv


From nobody Mon Sep 30 04:29:31 2019
Return-Path: <dhruv.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C962C120227; Mon, 30 Sep 2019 04:29:21 -0700 (PDT)
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, FREEMAIL_FROM=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=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 SGbRdCR0RmcA; Mon, 30 Sep 2019 04:29:19 -0700 (PDT)
Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com [IPv6:2607:f8b0:4864:20::d2b]) (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 D084F12021D; Mon, 30 Sep 2019 04:29:19 -0700 (PDT)
Received: by mail-io1-xd2b.google.com with SMTP id v2so37184164iob.10; Mon, 30 Sep 2019 04:29:19 -0700 (PDT)
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:content-transfer-encoding; bh=b7NKr6WQbFTBM60WAI26th4y45jHQvo5LqcztiOk6EE=; b=ZEqUUOsPFPQ9WxnKdcvKwHbReJxzngW0FkjaiJWFUHWzpYSrOT6YUGAca5j1IZPRTH vebRTDpP35wgQOeFkeyJRQ30NiyBObkmkVr1kk0YrFRlvTeZizVOWZbp+VV4I2M+NXDL wMGZ2RRpUgqWfOUi0D4S4cIBlG6A0CFHMjOY0UNATbMPeRrzou39Xdyh9UyQxSLwL5jc OoU9WjXe6d8dJWMXHGF2qzGvsLKEecnnlcBJ3swfvr2alkJaMo0TuX/QxKIVj1hwd5zg Q7ishyWI0QgiAd2sasKrrAGg9jqXSMM+Jwqp1egIVM4e5w//jHVb/lTHnQKNnh+Mekat Te6w==
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:content-transfer-encoding; bh=b7NKr6WQbFTBM60WAI26th4y45jHQvo5LqcztiOk6EE=; b=LwJxUbctdoIN34e/NcTjklJAM6GMxfMhlQMqSgl5/jauJ5PaFBbQ6XcJhSt0yjn025 zJOvkMAFdpIA1tZYBezWPg/kRw4IPCOoOek4+EeWA2S3h/y0wIryJdY+fG/UbXTdbub1 u/q5d1jeCZj+SxyjksEeTHFb0z6V4Ccgy5TuxEh0eEAwRarTcMhLeUL5JowNKqPHXCm8 DjlKwjGBONFmyZSqw1RIJJPwaTowy2T2W6REDSykvHavVu2cY0TJNETrYx3ZtwIYjuF6 oJE8sgNRemYG1mr/TED20srRHAXE2prEM7712T/nl2uBsBdRo6PPqg7Yz3DF2zp3e6yW aimQ==
X-Gm-Message-State: APjAAAWu7bAoCK+IJgHeoKa/RmuZhTK/ouZPR7vvjUijmWQ6uB8bzuEu oNfhFZeEUFoXIaIvAvmCmYpQ+6s6NEd3gx25zgU=
X-Google-Smtp-Source: APXvYqzdwoj5l0ufJKl+9MLw03YCmS1HYZeAlbn6CWHrs5NjovrjjEFeV3b7Ngj/pRKL2thq/bX31yvesyZKRO9nOPY=
X-Received: by 2002:a5d:9dd4:: with SMTP id 20mr20752656ioo.1.1569842958984; Mon, 30 Sep 2019 04:29:18 -0700 (PDT)
MIME-Version: 1.0
References: <156957891627.12410.17887218088455702680.idtracker@ietfa.amsl.com>
In-Reply-To: <156957891627.12410.17887218088455702680.idtracker@ietfa.amsl.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Mon, 30 Sep 2019 16:58:42 +0530
Message-ID: <CAB75xn6kg9TkxV=S=o7BXDVQ5GpLkU1g+zG4XFwrGn9JkQ9RrQ@mail.gmail.com>
To: Alvaro Retana <aretana.ietf@gmail.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pce-lsp-control-request@ietf.org,  Hariharan Ananthakrishnan <hari@netflix.com>, pce-chairs <pce-chairs@ietf.org>, pce@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/5sJI3JY0TmotsVTKErsQ1azmp7E>
Subject: Re: [Pce] Alvaro Retana's No Objection on draft-ietf-pce-lsp-control-request-09: (with COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Sep 2019 11:29:22 -0000

Hi Alvaro,

Let me take a stab at this. Authors can join in -

On Fri, Sep 27, 2019 at 3:38 PM Alvaro Retana via Datatracker
<noreply@ietf.org> wrote:
>
> Alvaro Retana has entered the following ballot position for
> draft-ietf-pce-lsp-control-request-09: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-pce-lsp-control-request/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> I have a substantive comment and then some nits/editorial notes.
>
> (1) It seems to me that any PCE can request control of an LSP.  Even if t=
he
> sessions are authenticated and encrypted, how does the PCC determine if i=
t's ok
> for the requesting PCE to ask for control?  =C2=A78.1 says that an "imple=
mentation
> SHOULD allow the operator to configure the policy based on which it honor=
s the
> request to control the LSPs".  If the implementation doesn't allow the
> configuration of policy, then it is possible for a rogue PCE to ask for c=
ontrol
> of an LSP, and for the PCC to grant it.  Why is the ability to configure =
this
> policy not REQUIRED?  I believe this case should be explicitly called out=
 as a
> vulnerability.
>

Thanks for pointing this out. Since RFC 8231 uses SHOULD wrt policy, I
would consider not changing that. We can highlight that the PCC is the
ultimate arbiter on if the delegation should be made and to which PCE.
Even after delegation, the PCC can take back control anytime. But at
the same time blindly accepting control request could be a problem!

I propose this text in Security section -

   A PCC is the ultimate arbiter of delegation.  As per [RFC8231], a
   local policy at PCC is used to influence the delegation.  A PCC can
   also revoke the delegation at any time.  A PCC MUST NOT blindly trust
   the control requests and SHOULD take local policy and other factors
   into consideration before honoring the request.

> (2) Abstract: s/A Path Computation Client (PCC) has set up LSPs/A Path
> Computation Client (PCC) that has set up LSPs
>
> (3) =C2=A71: s/which PCE to delegate the orphaned LSP/which PCE to delega=
te the
> orphaned LSP to
>
> (4) =C2=A71: s/a simple extension, by using this a PCE can/a simple exten=
sion, by
> using it a PCE can
>
> (5) In =C2=A73 the new C Flag is called the "LSP-Control Request Flag", b=
ut =C2=A77.1
> only uses "LSP-Control".  Please be consistent; the more descriptive name=
 is
> probably better.
>
>

These all looks like reasonable requests, authors - please update!

Thanks!
Dhruv


From nobody Mon Sep 30 04:29:59 2019
Return-Path: <dhruv.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6AD4120227; Mon, 30 Sep 2019 04:29:58 -0700 (PDT)
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, FREEMAIL_FROM=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=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 hg1NoI8gnJA3; Mon, 30 Sep 2019 04:29:57 -0700 (PDT)
Received: from mail-io1-xd35.google.com (mail-io1-xd35.google.com [IPv6:2607:f8b0:4864:20::d35]) (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 E7CCB12021D; Mon, 30 Sep 2019 04:29:56 -0700 (PDT)
Received: by mail-io1-xd35.google.com with SMTP id a1so37309813ioc.6; Mon, 30 Sep 2019 04:29:56 -0700 (PDT)
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:content-transfer-encoding; bh=B496awp7uhA7dzFvZcbWcP0+7imwqavxLfRZ2e9aLhQ=; b=Q5seJJU0vSqh9ju1yW7gMDbnGSR/9Lnoe5xR2XmUNlKhY+zQr2+hQDj9suMUKJEc6k XYDm0HCmLVYT0z8ukadlT3XoIz3rnoAy9qM9RUR0Wmj+aiBq8WWVYMG0qrXspT8EHoGi m5yFwZ5LHTT4R5mCCMaGJs2UzXVXTbCyP3sNRe2AtVhCJpTSbucDu3CK3GqFNz/I4hQ8 0jMjqi3TkStwM1aSJlvRRAv+B7pwhpS4E5RhkfrbGDpzbGIHjIy6oruz+NO8Rck1mPjQ nQ63m/+8rFZioJJHn0zebz9u1JENKUy7nb5NyhVP0W2mhWliuezLcFth5sZCUIKT00XB 5aFg==
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:content-transfer-encoding; bh=B496awp7uhA7dzFvZcbWcP0+7imwqavxLfRZ2e9aLhQ=; b=gudZpWU5WNV9z/C6+b4P8mK53mIbzk2b0DSAc2Y4/XcyansLvKJKlwq7Me5Vbv6qm8 jAXjYSm0gJQXU0zH2tvUevOScbpek7nvmvMoBm0SKn6JdTR41AZb1TfXYKQkuHj2GWbz WC+50tkVJv+WULxgD7uBiFebhADjH71XTvWtKjmMXMNaWwdvkcN/gb+tU3IFfwkMcewg GEkb2uiuVPJfaAJMrcVos3t1eiQUZxqSvbBllAAU21U8LZImwSL6yMnWnudXqWQNrByA L31s2U/1IsVqAA9DhAGLFxMX8dHvUySBHTrvf/lIbvCjj35UUvFE5IB8yyjND6F+PnV6 t1ig==
X-Gm-Message-State: APjAAAXwMDXcXEaZzz5EME/2j+D5dWMdauB0IJH1AIYTS/s2XBE411tm FPIcZHdgFMFFzSDdH7I8qJnKXbH0DqNh9DyUP4Q=
X-Google-Smtp-Source: APXvYqxE0khtc7O6YbwstqUW1c5TxopiTkuY8vuuYgDBds/q26gWqdcvm5V9WcmuxTcJCLi2LgUv3CDRMkoLE/Xv3jQ=
X-Received: by 2002:a05:6638:3:: with SMTP id z3mr13692857jao.54.1569842996108;  Mon, 30 Sep 2019 04:29:56 -0700 (PDT)
MIME-Version: 1.0
References: <156947917508.29034.2649004397929023444.idtracker@ietfa.amsl.com>
In-Reply-To: <156947917508.29034.2649004397929023444.idtracker@ietfa.amsl.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Mon, 30 Sep 2019 16:59:19 +0530
Message-ID: <CAB75xn4dFO1QRb1zmDiUitHYjtqfce+DscBbVSMbi7YF=Ac9EA@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pce-lsp-control-request@ietf.org,  Hariharan Ananthakrishnan <hari@netflix.com>, pce-chairs <pce-chairs@ietf.org>, pce@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/rYrQ_yNW6xBcmULDqT53wp9F1nI>
Subject: Re: [Pce] Barry Leiba's No Objection on draft-ietf-pce-lsp-control-request-09: (with COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Sep 2019 11:29:59 -0000

Hi Barry,

Thanks for your review. Snipping to just one point -

> =E2=80=94 Section 4 =E2=80=94
>
>    The D Flag and C
>    Flag are mutually exclusive in PCUpd message.  The PCE SHOULD NOT
>    send control request for LSP which is already delegated to the PCE,
>    i.e. if the D Flag is set in the PCUpd message, then C Flag SHOULD
>    NOT be set.
>
> I=E2=80=99m confused: =E2=80=9Cmutually exclusive=E2=80=9D means that the=
y can=E2=80=99t both be set.  So why
> SHOULD NOT and not MUST NOT?  (You=E2=80=99re also missing a few articles=
 here: =E2=80=9Da
> PCUpd message=E2=80=9D, =E2=80=9Ca control request=E2=80=9D, =E2=80=9Can =
LSP=E2=80=9D, and =E2=80=9Cthe C Flag=E2=80=9D.
>

I think the reason for SHOULD NOT was because when a PCC receives this
- it would simply ignore it!
This did not rise to the level of error usual for MUST NOT!

If you feel that the above isn't a good enough reason, changing would
not cause any harm either.

Thanks!
Dhruv


From nobody Mon Sep 30 07:09:59 2019
Return-Path: <barryleiba@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BEC91200CC; Mon, 30 Sep 2019 07:09:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.478
X-Spam-Level: 
X-Spam-Status: No, score=-1.478 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.172, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4g4mon46ma2u; Mon, 30 Sep 2019 07:09:51 -0700 (PDT)
Received: from mail-io1-f50.google.com (mail-io1-f50.google.com [209.85.166.50]) (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 5A2D01200BA; Mon, 30 Sep 2019 07:09:51 -0700 (PDT)
Received: by mail-io1-f50.google.com with SMTP id q10so38733714iop.2; Mon, 30 Sep 2019 07:09:51 -0700 (PDT)
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:content-transfer-encoding; bh=B+5XP2xCzYRcwgZ1T2gZzpEbXZ0uSbkIhnBjDq7uDPM=; b=AOjJfkUWA08FutPag9JPiaE3CuBjopXNwbHUpeAQogVv5b8om2+4gE54Q/xE/mPE7b tRd3NuKQQQ7DLyjl8rf6uyIa3P6Q31erUj+fQdY6klVD5jFrGttUW+VnJZ6/yp1FScjZ zRYT+EpnZTpxsypjeervs7ZIKnEpbdU0F7RBynh4tYBHFjF7MgebmPe6nmoYiRQB3FBV BsUv7oInqwSxX3SZLGtdSbCrvlg+X83DBlz3Bc1hN58BADxzmYby3bCaHoTOp1TsVqgr PThUFrkjml+AMoxZdQHLwhU0bl4wriqNM1rSkOWpyAUSYszzjMxnSvXLRPnOc8SaOWVm tC4g==
X-Gm-Message-State: APjAAAVYFsTDQtyK/2ei2PNXdRuV4fRHGK13bc/IcrcgfhnvHzzrIycJ bmsZ4z74Ingm0ol37uNmvrWbIAqXc8zIQAreUrw=
X-Google-Smtp-Source: APXvYqxKuS+L6njGpvky7kG3uneATapichKPu5BGR12C2R3NJCzS4JdGNreS+xzgnRdsrRTFnis57C1NcvbSz6lX1zI=
X-Received: by 2002:a02:1c02:: with SMTP id c2mr19575320jac.118.1569852590359;  Mon, 30 Sep 2019 07:09:50 -0700 (PDT)
MIME-Version: 1.0
References: <156947917508.29034.2649004397929023444.idtracker@ietfa.amsl.com> <CAB75xn4dFO1QRb1zmDiUitHYjtqfce+DscBbVSMbi7YF=Ac9EA@mail.gmail.com>
In-Reply-To: <CAB75xn4dFO1QRb1zmDiUitHYjtqfce+DscBbVSMbi7YF=Ac9EA@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Mon, 30 Sep 2019 10:09:39 -0400
Message-ID: <CALaySJJFsf=due-W3ynnsV0hBfAWNLsRW_x_tw_iZeo86cxdJg@mail.gmail.com>
To: Dhruv Dhody <dhruv.ietf@gmail.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pce-lsp-control-request@ietf.org,  Hariharan Ananthakrishnan <hari@netflix.com>, pce-chairs <pce-chairs@ietf.org>, pce@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/8AYMDFyTbuErjAGlg9XF7YrIh_g>
Subject: Re: [Pce] Barry Leiba's No Objection on draft-ietf-pce-lsp-control-request-09: (with COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Sep 2019 14:09:52 -0000

> > =E2=80=94 Section 4 =E2=80=94
> >
> >    The D Flag and C
> >    Flag are mutually exclusive in PCUpd message.  The PCE SHOULD NOT
> >    send control request for LSP which is already delegated to the PCE,
> >    i.e. if the D Flag is set in the PCUpd message, then C Flag SHOULD
> >    NOT be set.
> >
> > I=E2=80=99m confused: =E2=80=9Cmutually exclusive=E2=80=9D means that t=
hey can=E2=80=99t both be set.  So why
> > SHOULD NOT and not MUST NOT?  (You=E2=80=99re also missing a few articl=
es here: =E2=80=9Da
> > PCUpd message=E2=80=9D, =E2=80=9Ca control request=E2=80=9D, =E2=80=9Ca=
n LSP=E2=80=9D, and =E2=80=9Cthe C Flag=E2=80=9D.
> >
>
> I think the reason for SHOULD NOT was because when a PCC receives this
> - it would simply ignore it!
> This did not rise to the level of error usual for MUST NOT!
>
> If you feel that the above isn't a good enough reason, changing would
> not cause any harm either.

If the working group thinks that SHOULD NOT is right, it should stay
that way -- I just questioned the combination of "mutually exclusive"
and "SHOULD NOT".  So here are my thoughts:

1. If there is no reason they should ever be set together, then it
should be MUST NOT.

2. If there might be a reason to set them together -- it's difficult
to meet the conditions in some way, or whatever -- then SHOULD NOT is
OK.

3. If you keep it as SHOULD NOT, I think you should change the
"mutually exclusive" sentence to be less strong.

It sounds to me like MUST NOT is the right thing here -- that there's
never a reason to set them both together, and that it doesn't make
sense in the protocol to have them both set.  So even though the
receiver can ignore the situation, MUST NOT still applies.

Barry


From nobody Mon Sep 30 10:49:13 2019
Return-Path: <noreply@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 52E2112002F; Mon, 30 Sep 2019 10:49:04 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Kaduk via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-pce-lsp-control-request@ietf.org, Hariharan Ananthakrishnan <hari@netflix.com>, pce-chairs@ietf.org, hari@netflix.com, pce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.103.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Benjamin Kaduk <kaduk@mit.edu>
Message-ID: <156986574432.578.10826380036165341647.idtracker@ietfa.amsl.com>
Date: Mon, 30 Sep 2019 10:49:04 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/-GQ3JVDDC5oGGzZM3vJWxBY25ag>
Subject: [Pce] Benjamin Kaduk's Discuss on draft-ietf-pce-lsp-control-request-09: (with DISCUSS and COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Sep 2019 17:49:05 -0000

Benjamin Kaduk has entered the following ballot position for
draft-ietf-pce-lsp-control-request-09: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-pce-lsp-control-request/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

This may just be a philosophical discussion, but if RFC 8231 marks the
PLSP-ID value of 0 as "reserved" and we are making use of the extension
point, do we need to have an Updates: relationship with 8231?  This
seems particularly poigniant given that we have to explicitly override
the RFC 8231 error handling, with some text in the second paragraph of
Section 4.

What kind of feature negotiation is available to check support prior to
using this flag?  After all, if the peer does not implement this
document it will not implement the override of 8231 error handling and
will respond with errors when the D flag is set (or the PLSP-ID of 0
used).  If we have to just "try it and fall back to not using it if we
get errors", that has some associated security considerations as well.

What can we say about authorization policy on the PCC?  Alvaro touched
on this in his Comment, but I think it's important enough to be
Discuss-level.  Since this policy is the key factor to the security
posture of this extension, not only does it seem like there MUST be the
ability to configure the policy, but it also seems like we should be
able to give some guidance on typical use cases (where the authors
believe the security properties to be reasonable).  Other use cases
might require an additional level of analysis by those proposing to
deploy the solution.


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Section 1

               It includes mechanisms to effect LSP state
   synchronization between Path Computation Clients (PCCs) and PCEs,
   delegation of control of LSPs to PCE, and PCE control of timing and
   sequence of path computations within and across PCEP sessions.  [...]

nit: assuming this is grouped as "it includes mechanisms to: (1) effect
LSP state synchronization [...], (2) delegation of control [...], and
(3) PCE control of timing and sequence [...]", the verb tenses need to
be changed so that they match up.

   For Redundant Stateful PCEs (section 5.7.4. of [RFC8231]), during a
   PCE failure, one of the redundant PCE could request to take control
   over an LSP.  The redundant PCEs may use a local policy or a

Just to check: this request is only possible with the mechanism defined
in this document, and is not possible with just the previous
technologies?  I might suggest to s/could/might want to/ to make it more
clear that this is motivating the rest of the document.

   In case of virtualized PCEs (vPCE) running as virtual network
   function (VNF), as the computation load in the network increases, a

nit: singular/plural mismatch "PCEs"/VNF

   can be used in conjunction to [RFC8231].  Ultimately, it is the PCC
   that decides which PCE to delegate the orphaned LSP.

nit: either "to which to delegate the orphaned LSP" or "to delegate the
orphaned LSP to".

Section 3

   A new flag, the "LSP-Control Request Flag" (C), is introduced in the
   SRP object.  On a PCUpd message, a PCE sets the C Flag to 1 to
   indicate that it wishes to gain control of LSPs.  The LSPs are
   identified by the LSP object.  A PLSP-ID of value other than 0 and
   0xFFFFF is used to identify the LSP for which the PCE requests
   control.  The PLSP-ID value of 0 indicates that the PCE is requesting
   control of all LSPs originating from the PCC that it wishes to
   delegate.  [...]

nit: I suggest s/identified by the LSP object/identified by the PLSP-ID
in the LSP object following the SRP object/.

   delegate.  The C Flag has no meaning in other PCEP messages that
   carry SRP object and the flag MUST be set to 0 on transmission and
   MUST be ignored on receipt.

nit: I suggest s/object/objects/ and s/and the/and for which the/

Section 4

   If a PCE wishes to gain control over an LSP, it sends a PCUpd message
   with C Flag set to 1 in SRP object.  The LSP for which the PCE
   requests control is identified by the PLSP-ID.  The PLSP-ID of 0

nit: as above, I suggest s/identified by the PLSP-ID/identified by the
PLSP-ID in the associated LSP object/

   timer.  A PCE ignores the C Flag on the PCRpt message.  Note that, if

nit: I think this is now redundant with the text added in respone to
the genart review ("The C Flag has no meaning in other PCEP messages
that carry SRP object and the flag MUST be set to 0 on transmission and
MUST be ignored on receipt").

   It should be noted that a legacy implementation of PCC, that does not
   support this extension would trigger the error condition as specified
   in [RFC8231] (a PCErr with Error-type=19 (Invalid Operation) and
   error-value 1 (Attempted LSP Update Request for a non-delegated LSP))
I don't understand this sentence -- what does "as the D Flag would be
unset" mean?  Does it just mean that the PCC treats it as unset because
it has no code to handle the D flag at all?

Section 6

Please cite RFC 7525 as BCP 195.



From nobody Mon Sep 30 13:45:43 2019
Return-Path: <db3546@att.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AB8B120143; Mon, 30 Sep 2019 13:45:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UcVnwFqihn3c; Mon, 30 Sep 2019 13:45:23 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A11E12008C; Mon, 30 Sep 2019 13:45:23 -0700 (PDT)
Received: from pps.filterd (m0083689.ppops.net [127.0.0.1]) by m0083689.ppops.net-00191d01. (8.16.0.42/8.16.0.42) with SMTP id x8UKeMSm011526; Mon, 30 Sep 2019 16:45:19 -0400
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0083689.ppops.net-00191d01. with ESMTP id 2vbr39hcd4-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 30 Sep 2019 16:45:16 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id x8UKjCo6018872; Mon, 30 Sep 2019 16:45:14 -0400
Received: from zlp27127.vci.att.com (zlp27127.vci.att.com [135.66.87.31]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id x8UKj6aT018636 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 30 Sep 2019 16:45:06 -0400
Received: from zlp27127.vci.att.com (zlp27127.vci.att.com [127.0.0.1]) by zlp27127.vci.att.com (Service) with ESMTP id B47BD4009E94; Mon, 30 Sep 2019 20:45:06 +0000 (GMT)
Received: from MISOUT7MSGHUBAD.ITServices.sbc.com (unknown [130.9.129.148]) by zlp27127.vci.att.com (Service) with ESMTPS id 9EB3E4009E8E; Mon, 30 Sep 2019 20:45:06 +0000 (GMT)
Received: from MISOUT7MSGUSRDE.ITServices.sbc.com ([169.254.5.151]) by MISOUT7MSGHUBAD.ITServices.sbc.com ([130.9.129.148]) with mapi id 14.03.0468.000; Mon, 30 Sep 2019 16:45:06 -0400
From: "BRUNGARD, DEBORAH A" <db3546@att.com>
To: Dhruv Dhody <dhruv.ietf@gmail.com>, Martin Vigoureux <martin.vigoureux@nokia.com>
CC: pce-chairs <pce-chairs@ietf.org>, "pce@ietf.org" <pce@ietf.org>, The IESG <iesg@ietf.org>, "draft-ietf-pce-lsp-control-request@ietf.org" <draft-ietf-pce-lsp-control-request@ietf.org>, Hariharan Ananthakrishnan <hari@netflix.com>
Thread-Topic: Martin Vigoureux's No Objection on draft-ietf-pce-lsp-control-request-09: (with COMMENT)
Thread-Index: AQHVd4JEhvkCSsjTpUO5HkMCNB1mjKdErbWg
Date: Mon, 30 Sep 2019 20:45:05 +0000
Message-ID: <F64C10EAA68C8044B33656FA214632C8A3A5B672@MISOUT7MSGUSRDE.ITServices.sbc.com>
References: <156983718180.546.10162334928586461765.idtracker@ietfa.amsl.com> <CAB75xn7y2CrmW9ApEuRbjZD2P1b-A=xktr-hHZp-H1x-f1ggAA@mail.gmail.com>
In-Reply-To: <CAB75xn7y2CrmW9ApEuRbjZD2P1b-A=xktr-hHZp-H1x-f1ggAA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.70.213.70]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-09-30_11:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1908290000 definitions=main-1909300177
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/jmn15X5VaFh6Zn1AMuaaKWnPbJ4>
Subject: Re: [Pce] Martin Vigoureux's No Objection on draft-ietf-pce-lsp-control-request-09: (with COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Sep 2019 20:45:26 -0000

SGksDQoNClJGQzgyMzEgaW1wbGVtZW50YXRpb25zIGRvIG5vdCBuZWVkIHRvIGJlIGF3YXJlIG9m
IHRoaXMgUkZDJ3MgY2FwYWJpbGl0eS4gT25seSBmb3IgdGhvc2Ugd2FudGluZyB0byBzdXBwb3J0
IHRoaXMgbmV3IGNhcGFiaWxpdHksIHRoZXkgd2lsbCBmb2xsb3cgdGhpcyBSRkMuDQoNCkFzIHRo
ZSBjYXBhYmlsaXR5IGlzIG9wdGlvbmFsIC0gbm90IHJlcXVpcmVkIGZvciBSRkM4MjMxIGltcGxl
bWVudGF0aW9ucyAtIHRvIG1lIHRoYXQncyBhbiAiZXh0ZW5zaW9uIiwgbm90IGFuICJ1cGRhdGUi
Lg0KDQpUaGFua3MhDQpEZWJvcmFoDQoNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZy
b206IGllc2cgPGllc2ctYm91bmNlc0BpZXRmLm9yZz4gT24gQmVoYWxmIE9mIERocnV2IERob2R5
DQpTZW50OiBNb25kYXksIFNlcHRlbWJlciAzMCwgMjAxOSA3OjI4IEFNDQpUbzogTWFydGluIFZp
Z291cmV1eCA8bWFydGluLnZpZ291cmV1eEBub2tpYS5jb20+DQpDYzogcGNlLWNoYWlycyA8cGNl
LWNoYWlyc0BpZXRmLm9yZz47IHBjZUBpZXRmLm9yZzsgVGhlIElFU0cgPGllc2dAaWV0Zi5vcmc+
OyBkcmFmdC1pZXRmLXBjZS1sc3AtY29udHJvbC1yZXF1ZXN0QGlldGYub3JnOyBIYXJpaGFyYW4g
QW5hbnRoYWtyaXNobmFuIDxoYXJpQG5ldGZsaXguY29tPg0KU3ViamVjdDogUmU6IE1hcnRpbiBW
aWdvdXJldXgncyBObyBPYmplY3Rpb24gb24gZHJhZnQtaWV0Zi1wY2UtbHNwLWNvbnRyb2wtcmVx
dWVzdC0wOTogKHdpdGggQ09NTUVOVCkNCg0KSGkgTWFydGluLA0KDQpUaGFua3MgZm9yIHlvdXIg
cmV2aWV3LCByZXF1ZXN0IGF1dGhvcnMgdG8gY2hpbWUgaW4gYXMgbmVlZGVkLg0KDQpPbiBNb24s
IFNlcCAzMCwgMjAxOSBhdCAzOjIzIFBNIE1hcnRpbiBWaWdvdXJldXggdmlhIERhdGF0cmFja2Vy
IDxub3JlcGx5QGlldGYub3JnPiB3cm90ZToNCj4NCj4gTWFydGluIFZpZ291cmV1eCBoYXMgZW50
ZXJlZCB0aGUgZm9sbG93aW5nIGJhbGxvdCBwb3NpdGlvbiBmb3INCj4gZHJhZnQtaWV0Zi1wY2Ut
bHNwLWNvbnRyb2wtcmVxdWVzdC0wOTogTm8gT2JqZWN0aW9uDQo+DQo+IFdoZW4gcmVzcG9uZGlu
ZywgcGxlYXNlIGtlZXAgdGhlIHN1YmplY3QgbGluZSBpbnRhY3QgYW5kIHJlcGx5IHRvIGFsbCAN
Cj4gZW1haWwgYWRkcmVzc2VzIGluY2x1ZGVkIGluIHRoZSBUbyBhbmQgQ0MgbGluZXMuIChGZWVs
IGZyZWUgdG8gY3V0IA0KPiB0aGlzIGludHJvZHVjdG9yeSBwYXJhZ3JhcGgsIGhvd2V2ZXIuKQ0K
Pg0KPg0KPiBQbGVhc2UgcmVmZXIgdG8gDQo+IGh0dHBzOi8vdXJsZGVmZW5zZS5wcm9vZnBvaW50
LmNvbS92Mi91cmw/dT1odHRwcy0zQV9fd3d3LmlldGYub3JnX2llc2cNCj4gX3N0YXRlbWVudF9k
aXNjdXNzLTJEY3JpdGVyaWEuaHRtbCZkPUR3SUJhUSZjPUxGWVotbzlfSFVNZU1UU1FpY3ZqSWcm
cg0KPiA9NlVoR3BXOWx3aTlkTTdqWWx4WEQ4dyZtPUtUbGdRQzFUNXlWamp1eWtodDRyX3RiOVo4
S21vbGZadmpibnJkclRsdEUmDQo+IHM9LWxXRUIyNW4zZm1GQ0swWERsc0xFNWFEX28yVE9aZ2NW
QkF3ekJzRVlEayZlPQ0KPiBmb3IgbW9yZSBpbmZvcm1hdGlvbiBhYm91dCBJRVNHIERJU0NVU1Mg
YW5kIENPTU1FTlQgcG9zaXRpb25zLg0KPg0KPg0KPiBUaGUgZG9jdW1lbnQsIGFsb25nIHdpdGgg
b3RoZXIgYmFsbG90IHBvc2l0aW9ucywgY2FuIGJlIGZvdW5kIGhlcmU6DQo+IGh0dHBzOi8vdXJs
ZGVmZW5zZS5wcm9vZnBvaW50LmNvbS92Mi91cmw/dT1odHRwcy0zQV9fZGF0YXRyYWNrZXIuaWV0
Zi4NCj4gb3JnX2RvY19kcmFmdC0yRGlldGYtMkRwY2UtMkRsc3AtMkRjb250cm9sLTJEcmVxdWVz
dF8mZD1Ed0lCYVEmYz1MRllaLQ0KPiBvOV9IVU1lTVRTUWljdmpJZyZyPTZVaEdwVzlsd2k5ZE03
allseFhEOHcmbT1LVGxnUUMxVDV5VmpqdXlraHQ0cl90YjlaDQo+IDhLbW9sZlp2amJucmRyVGx0
RSZzPWJLMVZvUXJVM2xfRUNndmpBVkJIa1MyaW9hbnNTSnMwREUwYnk1Zm8zYmcmZT0NCj4NCj4N
Cj4NCj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLQ0KPiBDT01NRU5UOg0KPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+DQo+IEhp
LA0KPg0KPiB0aGFuayB5b3UgZm9yIHRoaXMgZG9jdW1lbnQuDQo+IFRoaXMgZG9jdW1lbnQgaW5k
aWNhdGVzOg0KPiAiLi4uTVVTVCBOT1QgdHJpZ2dlciB0aGUgZXJyb3IgY29uZGl0aW9uIGZvciB1
bmtub3duIFBMU1AtSUQgaW4gYW4gTFNQIA0KPiB1cGRhdGUgcmVxdWVzdCBhcyBwZXIgW1JGQzgy
MzFdIC4uLiIuICIuLi5NVVNUIE5PVCB0cmlnZ2VyIHRoZSBlcnJvciANCj4gaGFuZGxpbmcgYXMg
c3BlY2lmaWVkIGluIFtSRkM4MjMxXSAuLi4iLg0KPg0KPiBZZXQsIGl0IGFsc28gc2F5czoNCj4g
VGhlIHByb2NlZHVyZXMgZm9yIGdyYW50aW5nIGFuZCByZWxpbnF1aXNoaW5nIGNvbnRyb2wgb2Yg
dGhlIExTUHMgYXJlIA0KPiBzcGVjaWZpZWQgaW4gYWNjb3JkYW5jZSB3aXRoIHRoZSBzcGVjaWZp
Y2F0aW9uIFtSRkM4MjMxXS4NCj4NCg0KTWF5YmUgd2UgY2FuIGFkZCAtICIuLi51bmxlc3MgZXhw
bGljaXRseSBzZXQgYXNpZGUgaW4gdGhpcyBkb2N1bWVudC4iDQoNCj4gU28NCj4gMS8gaXQgc2Vl
bXMgdG8gbWUgdGhhdCB0aGUgbGF0dGVyIHNlbnRlbmNlLCBjb25zaWRlcmluZyB0aGUgZmlyc3Qg
dHdvLCANCj4gaXMgbm90IHN0cmljdGx5IGNvcnJlY3QuIDIvIHRoZSByYXRpb25hbGUgaXMgd2Vs
bCBkZXNjcmliZWQsIHNvIEknbSANCj4gZmluZSB3aXRoIG5vdCByZXNwZWN0aW5nIHRoZSBvcmln
aW5hbCBydWxlcyBvZiA4MjMxLCBidXQgdGhlbiBJIHdvbmRlciANCj4gaWYgdGhpcyBkb2N1bWVu
dCBzaG91bGRuJ3QgdXBkYXRlIDgyMzEuDQo+DQo+DQoNCkkgYW0gbm90IHN1cmUgaWYgdGhpcyBy
aXNlcyB0byB0aGUgbGV2ZWwgb2YgInVwZGF0ZSIgKGFzIEkgdW5kZXJzdGFuZCBpdCBhbmQgbm90
IHRha2luZyB0aGUgb25nb2luZyBkaXNjdXNzaW9uIG9uIHRoZSB0b3BpYyk7IHRvIG1lIGl0IGlz
IGEgbm9ybWFsIGV4dGVuc2lvbiBvZiBhIHByb3RvY29sICdidXNpbmVzcyBhcyB1c3VhbCchDQoN
CkkgdGhpbmsgbWF5YmUgaXQgaXMgdGltZSBmb3Igc29tZSBBRCBndWlkYW5jZSBvbiB0aGlzIDop
DQoNClRoYW5rcyENCkRocnV2DQoNCg==

