[Pce] Re: WG Last Call for draft-ietf-pce-sr-p2mp-policy-19 (Ends 2026-08-04)
Dhruv Dhody <dd@dhruvdhody.com> Wed, 16 September 2026 09:10 UTC
Received: from mail-oo2-x0d.google.com (mail-oo2-x0d.google.com [IPv6:2607:f8b0:4864:31::d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mx.ietf.org (Postfix) with ESMTPS id 88A8C44 for <pce@ietf.org>; Wed, 16 Sep 2026 09:10:59 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=dhruvdhody-com.20251104.gappssmtp.com header.s=20251104 header.b=Hcc8oJdU; arc=pass ("google.com:s=arc-20260327:i=1"); dmarc=none; spf=none (mx.ietf.org: domain of dd@dhruvdhody.com has no SPF policy when checking 2607:f8b0:4864:31::d) smtp.mailfrom=dd@dhruvdhody.com
Received: by mail-oo2-x0d.google.com with SMTP id 46e09a7af769-80552a37b55so83625a34.3 for <pce@ietf.org>; Wed, 16 Sep 2026 02:10:59 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1789549859; cv=none; d=google.com; s=arc-20260327; b=l1WcDwrLwAggvW2cPYTt8RJxwXl/KIDPVGtLbhjJ2I7BpjFaMsyytxHVpq2rcpCPHl tHADsjyPK7GkW7LvM+PBIC2HNsjuBZAVe7d4q5D6yvY0TsaUqfBkNLArZWdUnCtzM+vb 6/fO5DLJpmjdoSoyVFgDer1Uz7qbGFPkqhEqpfz/DmjO/WDWFA4W0txkGV3HlBRaZoNH EMDWHNf2f/mi1gbPRAXz6uGyszIDKqWLt/xcbHnZJ3rkNWjhKrSTM5csL2PfSs8k4YSx eq1QHoLXlih3eYpRYaCSlnVMFD8gK+OXKXiWtdAGReckuSptX1nPzyUgszF+jDLvK/Zh T5rg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20260327; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:dkim-signature; bh=Cbn8b4aoweF4W9eVCthRW/0Bqn8O77G8YYN4ar5JlRo=; fh=c5mqb+y+4jCTbO982pMUog04tSqkEWtd+293X6SWVEk=; b=VIgtCJztqxCIz0QZtsaLTb6J5I6MfrWTHXRMFdVHHM8/aV+3nh3bnuZpnOFSwYKiRi 9H484Yknh55DrtySLyELjHRNk4mWr5ESZczNglmO/YwJCmYb/KhOANrE8bVVoAlZ63nY da68HD3I5VDxnDqJ2OiEewtjrWCOOCAzU50xAiIzlYCSPoog2DBgnFVOiYgu7JKopa8P HLgTBPsX11bd2BQALdYBpuOG+MU2PPLXWrO+qabYYHiy1XSjz4L133wywxE8vhwFIsZn 7q7m02cByOAW+PEGdY1AInzBPqdHvWxgITcZgUaa6EzpFiBfyUNfN5abKyiW9DA3Xfah EnDQ==; darn=ietf.org
ARC-Authentication-Results: i=1; mx.google.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dhruvdhody-com.20251104.gappssmtp.com; s=20251104; t=1789549859; x=1790154659; darn=ietf.org; h=content-type:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:from:to:cc:subject:date:message-id:reply-to :content-type; bh=Cbn8b4aoweF4W9eVCthRW/0Bqn8O77G8YYN4ar5JlRo=; b=Hcc8oJdUThjOsdFXuy7Cm5MRCcuepJ2j13aOzfrJCnWxKIK6CqstW4/12JM+CvDvbB BxMOkr8yH+oD06kAJQaJHooQAalv1EtMTTyybgMpTcauU+ozWLt5u9RF8PKIcdlxj8gW UorXiB2tu/lLD4b5voKiqyJ0IdPbCuar/xgrjGxyetFhcKWRCUoDEgBfsQb66qAaATmQ AZll8k07DUWP7viwpY33KkmxNShDCDJ0Xp2GiqLreLdnVvGX4im64LD8bFKLrFWRa2G4 tisBKP8EsN57ewJyCOsgFwz1EQVTbcsq0M6EsW9oaDnZ3CSWCIz5qM/ZtxGIxs4YDEda DQ+Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1789549859; x=1790154659; h=content-type:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:x-gm-gg:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to:content-type; bh=Cbn8b4aoweF4W9eVCthRW/0Bqn8O77G8YYN4ar5JlRo=; b=Xj2nyAdPyDaIIc8nD2CNj5PotYfxsOeU2tf877/WfCmDxDSM+hqoiQpnsxc97JnhBM I+eHiIRNc3XDHqkJOuh4F4oD3IzpqH6V/foPfef6N/zRDeJzTdiTeAY8NGmLCSW4cNU0 1V5z+SplK6p1jxLmNQzE415l3lHgl8pKot/KevO6juZBDY731QHDaBPlAGikcVLMwpxk Y5C7YTSSW7jxs2uVZHhdivPYueu5ec6FGDMqnRjE7K2uYEH7Oie+ZYtOmxP/Omg8+lSw idAefDhLG34gDbBa3g4Qer3WYzJ/JOqY+TQCJDvUbTpZhox9G3wY+KY80q8iK3plgn/z twZA==
X-Forwarded-Encrypted: i=1; AKwUvBzDgrGPKgCHluOpHq9nsaHuUffmgIb2XXS4CdSTlziY5weVKfT3HTQqead7NhsYjs7flEA=@ietf.org
X-Gm-Message-State: AFuF++mesmJvyRDn8RDaI+Le1rWZwU4LGb/8HMWAIrnIfgtPXJ93h5al u0/RgzYdmxvseQ1ipeLkEWyf8bolGH1PwDQIrcCFf8hu2zCx3bKD7FdfEXm/XJl0oFAzeSUjxIc XNVpzDI6hOqtjudkhrB/s1/EqYjHWwNF24t/sLa7HBg==
X-Gm-Gg: AYBFou3NMTv8VPEjPeSHA6MJHkeJuFyT6Ubi/J+fiPEjw0RszxQrCuXzTgUHBR58vDf ypMvCuqNVgoRgf77wOoDDRob71XVyE7CfZ/CVOD6BHQWoNsOpH6xKFHyDOQQvh2oQIpAcY33rXG uJVl8FO1amzFR56IQiJQClly1I0FgrSEURshuOvK2CB9KDac3zd/lNgYcrM/xLsNl/ezqFA51oS Q0qM8Xn9/VALpqpF85f5asZrZ9vTUYJi+9VUbKRufFmMWQkLwHo+AtDrBG7LwYM/Vj4a4QpI2ZN N5yJX5C5FN8UOGu3/2UO4KKmRhFZkpP28cWCglkHVgY933AWkm7Qk2ZXjPxPGG75QJMa7NCYZqZ M3vdOIPusRy3VyTTVy4ILCklCtFq+pNrDJQ8SrTtSfFVdlOD+NOGElm4p/AcuYJUCmtl7J6NfgF eeMW4SW71ofhbrviV+qzEmGK2PBD2bI52WrhJ0kau/mCgpob274xNTifcc996xRU0a6XvvuG2f1 An2oTNFuDMRYNjXjLZqFgQYgfmV0QPwU/J56S3SviyJuwsYWmY3+4GZr0paL8ukU00853BI1Ub6 fCjdWWu3LMKjN8ujFHBamf71o6XJuUJftxyWJ2zd/r9/CzGepMheGVq0AuM1oGtXflMnd5v8ZN4 vFmOHJFc=
X-Received: by 2002:a05:6830:4488:b0:7e6:6ced:992f with SMTP id 46e09a7af769-80b2ec5cbc7mr2230227a34.2.1789549858144; Wed, 16 Sep 2026 02:10:58 -0700 (PDT)
MIME-Version: 1.0
References: <178341908550.413483.15283611983977799329@dt-datatracker-57b5d8f849-zrqfx> <CAP7zK5Y-nh5VDOFcZ3UHJ-DFdDGtjBp5Z4N7M5Hzh2f=N2i3tw@mail.gmail.com> <IA0PR11MB779285FF742DFF5B6901BF73D0AF2@IA0PR11MB7792.namprd11.prod.outlook.com> <CH0PR08MB732227B05A757220303339B091A82@CH0PR08MB7322.namprd08.prod.outlook.com> <IA0PR11MB77923E9232D657E432AFE8E4D0B12@IA0PR11MB7792.namprd11.prod.outlook.com> <CH0PR08MB732273B1F726B6EC58A9900D91B02@CH0PR08MB7322.namprd08.prod.outlook.com> <IA0PR11MB77920FA0E7E08123322B9B37D0B02@IA0PR11MB7792.namprd11.prod.outlook.com> <CH0PR08MB73225DD31634288DA9FC8F7991BB2@CH0PR08MB7322.namprd08.prod.outlook.com> <IA0PR11MB7792ED0E9284EF42FD14FEE7D0B92@IA0PR11MB7792.namprd11.prod.outlook.com>
In-Reply-To: <IA0PR11MB7792ED0E9284EF42FD14FEE7D0B92@IA0PR11MB7792.namprd11.prod.outlook.com>
From: Dhruv Dhody <dd@dhruvdhody.com>
Date: Wed, 16 Sep 2026 14:40:21 +0530
X-Gm-Features: AcwNN1VthrBGuo3541awyPk9NHNkxkDcOzf1X-fCIILWKxTC6kUSqeAhEbwVErQ
Message-ID: <CAP7zK5ZhY8hdDR4FrpyyrpWXsY-CW4LuK6HTML0CmD2ejWTZKA@mail.gmail.com>
To: "Samuel Sidor (ssidor)" <ssidor@cisco.com>
Content-Type: multipart/alternative; boundary="0000000000009a50b2065b960bbb"
X-Spamd-Bar: /
Message-ID-Hash: FF3GTCTW6ISFOSJYK5J7VM5BEFVYSYWT
X-Message-ID-Hash: FF3GTCTW6ISFOSJYK5J7VM5BEFVYSYWT
X-MailFrom: dd@dhruvdhody.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-pce.ietf.org-0; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "draft-ietf-pce-sr-p2mp-policy@ietf.org" <draft-ietf-pce-sr-p2mp-policy@ietf.org>, "Andrew Stone (Nokia)" <andrew.stone@nokia.com>, "pce-chairs@ietf.org" <pce-chairs@ietf.org>, "pce@ietf.org" <pce@ietf.org>
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [Pce] Re: WG Last Call for draft-ietf-pce-sr-p2mp-policy-19 (Ends 2026-08-04)
List-Id: Path Computation Element <pce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/Ce1WtGnbUokWHNJiK0SYiP32HhQ>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Owner: <mailto:pce-owner@ietf.org>
List-Post: <mailto:pce@ietf.org>
List-Subscribe: <mailto:pce-join@ietf.org>
List-Unsubscribe: <mailto:pce-leave@ietf.org>
Hi Hooman,
I agree with what Samuel says. But also I would ask you to not combine
these in a single PCEP message.
This design was a deliberate decision in RFC 9050: each PCEP message must
relate only to "LSP" or "central control" (CCI) and not both!
<PCE-initiated-lsp-request> ::=
(<PCE-initiated-lsp-instantiation>|
<PCE-initiated-lsp-deletion>|
<PCE-initiated-lsp-central-control>)
<state-report> ::= (<lsp-state-report>|
<central-control-report>)
https://www.rfc-editor.org/info/rfc9050/#section-6
The RBNF would be unnecessarily complicated otherwise, and sending two
distinct PCEP messages is much cleaner.
Thanks!
Dhruv (as a WG participant)
On Wed, Sep 16, 2026 at 1:01 PM Samuel Sidor (ssidor) <ssidor@cisco.com>
wrote:
> Hi Hooman,
>
> I would say that dedicated RBNF is better - it could even be single RBNF
> describing combined case with text clarifying which objects are
> required/optional for each case (section 4.4.2 vs section 4.4.3 vs
> combined).
>
> The current version of the draft is just saying that those can be
> combined, but it is not specifying order of those objects. Also I believe
> that RBNF is normative, but current statement which is trying to allow
> combination is not.
>
> It is also a bit unclear to me, whether combination is allowed in
> PCInitiate, PCUpd or both since section 5.6 is talking about PCUpd, title
> of A.2 is talking about CP initialization (Examples in appendix B just
> show example with separate PCInitiate and PCUpd)
>
> Thanks,
> Samuel
>
> *From: *Hooman Bidgoli (Nokia) <hooman.bidgoli@nokia.com>
> *Date: *Monday, 14 September 2026 at 06:45
> *To: *Samuel Sidor (ssidor) <ssidor@cisco.com>;
> draft-ietf-pce-sr-p2mp-policy@ietf.org <
> draft-ietf-pce-sr-p2mp-policy@ietf.org>
> *Cc: *Andrew Stone (Nokia) <andrew.stone@nokia.com>; pce-chairs@ietf.org <
> pce-chairs@ietf.org>; Dhruv Dhody <dd@dhruvdhody.com>; pce@ietf.org <
> pce@ietf.org>
> *Subject: *RE: [Pce] Re: WG Last Call for
> draft-ietf-pce-sr-p2mp-policy-19 (Ends 2026-08-04)
>
> Hi Samuel
>
>
>
> As per A.2 text, it is showing the example that the p2mp policy and
> replication segment is downloaded in the same message
>
>
>
> As per section 5.6
>
>
>
> As it was noted previously, for the Root the SR P2MP Policy and the
> Replication Segment is downloaded via the same PCUpd message.
>
>
>
> Perhaps we can make this more clear.
>
>
>
> But basically on the root we can send a p2mp policy initiation and its
> replication segment with in the same message.
>
>
>
> So the question is do we need a new RBNF to display this case or just a
> paragraph explaining this is sufficient?
>
>
>
> Thanks
>
> Hooman
>
>
>
>
>
> *From:* Samuel Sidor (ssidor) <ssidor@cisco.com>
> *Sent:* Wednesday, September 9, 2026 8:19 AM
> *To:* Hooman Bidgoli (Nokia) <hooman.bidgoli@nokia.com>;
> draft-ietf-pce-sr-p2mp-policy@ietf.org
> *Cc:* Andrew Stone (Nokia) <andrew.stone@nokia.com>; pce-chairs@ietf.org;
> Dhruv Dhody <dd@dhruvdhody.com>; pce@ietf.org
> *Subject:* Re: [Pce] Re: WG Last Call for
> draft-ietf-pce-sr-p2mp-policy-19 (Ends 2026-08-04)
>
>
>
>
>
> *CAUTION:* This is an external email. Please be very careful when
> clicking links or opening attachments. See the URL nok.it/ext for
> additional information.
>
>
>
> Hi Hooman,
>
>
>
> Thanks for addressing those comments quickly.
>
>
>
> For RBNF coverage for A.2 example - here is what I can see in A.2 - single
> PCEP message with:
>
>
>
> SRP+LSP+ASSOCIATION+P2MP-ENDPOINT+CCI+PATH-ATTRIB+ERO1+PATH-ATTRIB+ERO2
>
>
>
> (I assume that it is PCInitiate since whole section is talking about
> candidate-path instantiation, but same applies even if it is PCUpd).
>
>
>
> 4.4.2 defines:
>
>
>
> <PCE-initiated-lsp-instantiation> ::= <SRP>
>
> <LSP>
>
> ([<END-POINTS>]
>
> <ERO>|<sr-p2mp>)
>
> [<association-list>]
>
> [<attribute-list>]
>
>
>
> Where “<sr-p2mp>::=<END-POINTS>”, so in reality:
>
>
>
> <PCE-initiated-lsp-instantiation> ::= <SRP>
>
> <LSP>
>
> ([<END-POINTS>]
>
> <ERO>|<END-POINTS>)
>
> [<association-list>]
>
> [<attribute-list>]
>
> Where I assume that “<attribute-list>” is the one defined in RFC5440 (but
> it would be good to state that explicitly in the draft as well):
>
> <attribute-list> ::= [<LSPA>]
>
> [<BANDWIDTH>]
>
> [<metric-list>]
>
> [<IRO>]
>
>
>
> So CCI is not allowed at all (CCI is not part of attribute-list). Note
> that this RBNF is not even allowing multiple pairs of PATH-ATTRIB+ERO/paths
> (which are used in the example).
>
>
>
> 4.4.3 defines:
>
>
>
> <PCE-initiated-lsp-central-control> ::= <SRP>
>
> <LSP>
>
> (<cci-list>|
>
> (<FEC>
>
> <CCI>)|
>
> (<CCI>
>
> <intended-path-multipath>))
>
>
>
> Which does not allow ASSOCIATION and END-POINTS objects at all.
>
>
>
> So overall, none of those RBNFs defined is allowing message used in A.2
> example. But feel free to correct me if I’m missing anything.
>
>
>
> One more issue introduced in version 21 - in the examples the
> SR‑P2MP‑INSTANCE‑ID TLV is shown with Type=17, which is the
> SYMBOLIC‑PATH‑NAME type:
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> | Type=*17* | Length=<var> |
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> | symbolic path name |
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> | Type=*17* | Length |
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> | Root = A |
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> ...
>
>
>
> Same is repeated in multiple examples - so TLV type is set to 17 (which is
> supposed to be used for symbolic name), but it is used for
> SR‑P2MP‑INSTANCE‑ID TLV.
>
>
>
> Regards,
>
> Samuel
>
>
>
> *From: *Hooman Bidgoli (Nokia) <*hooman.bidgoli@nokia.com*
> <hooman.bidgoli@nokia.com>>
> *Date: *Wednesday, 9 September 2026 at 04:42
> *To: *Samuel Sidor (ssidor) <*ssidor@cisco.com* <ssidor@cisco.com>>;
> *draft-ietf-pce-sr-p2mp-policy@ietf.org*
> <draft-ietf-pce-sr-p2mp-policy@ietf.org> <
> *draft-ietf-pce-sr-p2mp-policy@ietf.org*
> <draft-ietf-pce-sr-p2mp-policy@ietf.org>>
> *Cc: *Andrew Stone (Nokia) <*andrew.stone@nokia.com*
> <andrew.stone@nokia.com>>; *pce-chairs@ietf.org* <pce-chairs@ietf.org> <
> *pce-chairs@ietf.org* <pce-chairs@ietf.org>>; Dhruv Dhody <
> *dd@dhruvdhody.com* <dd@dhruvdhody.com>>; *pce@ietf.org* <pce@ietf.org> <
> *pce@ietf.org* <pce@ietf.org>>
> *Subject: *RE: [Pce] Re: WG Last Call for
> draft-ietf-pce-sr-p2mp-policy-19 (Ends 2026-08-04)
>
> Hi Samuel
>
>
>
> Thanks again for the comments
>
>
>
> Inline, I uploaded version 21 for now to address some of the comments.
>
>
>
> Thanks
>
> Hooman
>
>
>
> *From:* Samuel Sidor (ssidor) <*ssidor@cisco.com* <ssidor@cisco.com>>
> *Sent:* Tuesday, September 8, 2026 10:00 AM
> *To:* Hooman Bidgoli (Nokia) <*hooman.bidgoli@nokia.com*
> <hooman.bidgoli@nokia.com>>; *draft-ietf-pce-sr-p2mp-policy@ietf.org*
> <draft-ietf-pce-sr-p2mp-policy@ietf.org>
> *Cc:* Andrew Stone (Nokia) <*andrew.stone@nokia.com*
> <andrew.stone@nokia.com>>; *pce-chairs@ietf.org* <pce-chairs@ietf.org>;
> Dhruv Dhody <*dd@dhruvdhody.com* <dd@dhruvdhody.com>>; *pce@ietf.org*
> <pce@ietf.org>
> *Subject:* Re: [Pce] Re: WG Last Call for
> draft-ietf-pce-sr-p2mp-policy-19 (Ends 2026-08-04)
>
>
>
>
>
> *CAUTION:* This is an external email. Please be very careful when
> clicking links or opening attachments. See the URL nok.it/ext for
> additional information.
>
>
>
> Hi Hooman,
>
>
>
> Thanks a lot for handling those comments.
>
>
>
> A few more minor comments on the updated version (sorry for not finding
> those sooner as only some of them were introduced in latest version):
>
>
>
> 1. There is a stale PCEP error‑value defined in Section 6.5 - "1: SR
> P2MP incompatible leaf types" - which does not seem to be used anywhere.
>
> HB> yah good catch.
>
>
>
> 2. Sections 4.4.2 and 4.4.3 describe the RBNF for
> PCInitiate/PCUpd/PCRpt. Each allows a specific set of objects to be
> combined, but the A.2 example mixes both types together, which is not
> explicitly allowed by either RBNF. Do we need combined normative text or an
> RBNF production allowing such a combination (e.g., to specify the ordering
> of the objects when combined)?
>
>
>
> HB> sorry I don’t understand this comment, if you are running a LLM it
> might be confused by the format. A.2 matches the RBNF.
>
>
>
> 3. Some object names use underscores that don't match the original
> (registered) names, e.g., MULTIPATH_BACKUP vs. MULTIPATH-BACKUP (and
> PATH_ATTRIB, CPATH_ID in Figure 3).
>
>
>
> HB> thanks fixed those.
>
>
>
> 4. In Appendix B, I see "N=1" - is this the same as my earlier comment
> about the "N flag in the LSP object," or is it a different N flag from
> another object?
>
>
>
> HB> yes it is the same removed it.
>
>
>
> 5. "TBD" is used for some code points where the actual value is
> already allocated - e.g., "PST = TBD" in the examples, even though PST is
> supposed to always be 1 (per Section 5.2). It would help to scan the whole
> document for "TBD"; most should be replaceable now.
>
>
>
> HB> need to look into this in detail, might take a little while.
>
>
>
> 6. The association name differs across sections: "P2MP SR Policy
> Association" (5.3), "SR P2MP Policy Association Type" (5.5.1), and "SR P2MP
> Policy Association" (6.1). Shouldn't all three be aligned, since they refer
> to the same association type 9 (code point)?
>
> HB> corrected.
>
>
>
> 7. In Section 5.8 - "A series of 4‑octet identifiers that reference
> the Path ID field (see *Section 4.2*)." Is this really meant to
> reference Section 4.2 ("Overview of SR P2MP Policy Objects")?
>
>
>
> HB> Thanks copy paste issue when I ported this section from other draft.
>
>
>
> 8. In Section 4.2.1 - "This Object is a new object based on the *LSP
> ID Object* defined …". I assume this refers to the LSP object, not an
> "LSP ID object." Also, that section isn't introducing a new PCEP object;
> it's really just specifying what to fill into the existing LSP object and
> the new SR‑P2MP‑INSTANCE‑ID TLV.
>
>
>
> HB> yes, the original sentence was “identified on the root via the P2MP
> LSP Object which is a variant of the LSP Object…” That said Dhruv points
> out that there should be a use of “variant” .
>
> HB> I still think this should read “identified on the root via the P2MP
> LSP Object which is a *new* variant of the LSP Object…” I am going to
> change it to this.
>
>
>
> 9. draft-ietf-pce-pcep-extension-pce-controller-sr - shouldn't this be
> a normative reference, since the draft relies on the CCI object‑type/flags
> introduced there?
>
>
>
> HB> true thanks.
>
>
>
> 10. The name of Section 9.1, "Operation Consideration," should be
> "Operational Considerations."
>
>
>
> HB> AI changed this 😃 so now I change it back.
>
>
>
> 11. In Section 5.3 - "…SHOULD not be set…" → "SHOULD NOT be set."
>
>
>
> HB> thanks
>
>
>
> 12. In Section A.2 - "wraps all the Path Attribute messages and their
> corresponding EROs." I assume this refers to the PATH‑ATTRIB object, not a
> message.
>
> HB> yes thanks
>
>
>
> There are also a number of formatting issues, and uppercase/lowercase
> usage is inconsistent in a few places.
>
>
>
> Regards,
>
> Samuel
>
>
>
> *From: *Hooman Bidgoli (Nokia) <*hooman.bidgoli@nokia.com*
> <hooman.bidgoli@nokia.com>>
> *Date: *Wednesday, 2 September 2026 at 01:30
> *To: *Samuel Sidor (ssidor) <*ssidor@cisco.com* <ssidor@cisco.com>>;
> *draft-ietf-pce-sr-p2mp-policy@ietf.org*
> <draft-ietf-pce-sr-p2mp-policy@ietf.org> <
> *draft-ietf-pce-sr-p2mp-policy@ietf.org*
> <draft-ietf-pce-sr-p2mp-policy@ietf.org>>
> *Cc: *Andrew Stone (Nokia) <*andrew.stone@nokia.com*
> <andrew.stone@nokia.com>>; *pce-chairs@ietf.org* <pce-chairs@ietf.org> <
> *pce-chairs@ietf.org* <pce-chairs@ietf.org>>; Dhruv Dhody <
> *dd@dhruvdhody.com* <dd@dhruvdhody.com>>; *pce@ietf.org* <pce@ietf.org> <
> *pce@ietf.org* <pce@ietf.org>>
> *Subject: *RE: [Pce] Re: WG Last Call for
> draft-ietf-pce-sr-p2mp-policy-19 (Ends 2026-08-04)
>
> Hi Samuel
>
>
>
> Much appreciated your detail review! We addressed most of your comments
> and will upload in the next version. Next version should be available
> sometime next week.
>
>
>
> Inline
>
>
>
> Regards
>
> Hooman
>
>
>
> *From:* Samuel Sidor (ssidor) <*ssidor@cisco.com* <ssidor@cisco.com>>
> *Sent:* Tuesday, August 25, 2026 7:08 AM
> *To:* *draft-ietf-pce-sr-p2mp-policy@ietf.org*
> <draft-ietf-pce-sr-p2mp-policy@ietf.org>
> *Cc:* Andrew Stone (Nokia) <*andrew.stone@nokia.com*
> <andrew.stone@nokia.com>>; *pce-chairs@ietf.org* <pce-chairs@ietf.org>;
> Dhruv Dhody <*dd@dhruvdhody.com* <dd@dhruvdhody.com>>; *pce@ietf.org*
> <pce@ietf.org>
> *Subject:* Re: [Pce] Re: WG Last Call for
> draft-ietf-pce-sr-p2mp-policy-19 (Ends 2026-08-04)
>
>
>
>
>
> *CAUTION:* This is an external email. Please be very careful when
> clicking links or opening attachments. See the URL nok.it/ext for
> additional information.
>
>
>
> Hi authors of draft-ietf-pce-sr-p2mp-policy,
>
>
>
> Sorry for delayed response, I support WGLC of this document, but it would
> be good to fix a few things (ignore if any of them was reported already by
> other reviewers) in the draft:
>
>
>
> 1. *Instance ID assignment*
>
> It seems to be a bit unclear about who is assigning instance ID. E.g.
> section 4.2.1 is saying “Instance-ID: serves as the PTI identifier and is
> assigned *by the PCE*” (same seems to be indicated in multiple sections),
> but 4.3.2.2 is saying “Instance-ID: value MUST be set to zero. *The PCC* generates
> the PTI's Instance-ID of the CP.”. I assume that it is just typo.
>
>
>
> HB> thanks you fixed section 4.3.2.2
>
>
>
> 2. *Instance ID length*
>
> The diagrams showing SR-P2MP-INSTACE-ID-TLV in section 5.6.1 are using
> Instance-ID with *16 bits* length, but text is saying: “Instance-ID :
> Identifier of PTI, Contains *32 Bit* instance ID”. Note that also
> appendix is showing instance-ID with 32bits.
>
>
>
> HB> changed to 16 bit
>
>
>
> 3. *SR-P2MP-POLICY-CAPABILITY TLV Reserved field handling*
>
> Add statement clarifying how “Reserved” space is supposed to be handled,
> e.g. “Reserved: 16 bits, MUST be set to 0 on transmission and ignored on
> receipt”. Also TLV type is marked as TBD, but IANA section was already
> updated with allocated type for that TLV, so “Type=TBD” can be updated as
> well (same applies to multiple diagrams).
>
>
>
> HB> changed thanks
>
>
>
> 4. *Strange “**SR P2MP incompatible leaf types**” error*
>
> In section 5.1, there is last paragraph talking about PCEP peer checking
> whether leaf-types are acceptable, but capability TLV does not have any
> information about supported leaf types. It contains only number of
> supported instances and replications. If it is still applicable and not
> just some outdated text, it would be good to add details.
>
>
>
> HB> removed you are right.
>
>
>
> 5. *Not matching error type*
>
> In section 4.3.1, the text is saying “The PCInitiate message sent to the
> root MUST set the *Tree-ID to 0*. If not the PCC must send a PCEP Error
> message (PCErr) with Error-Type = X2 (SR P2MP Policy General Error) and
> Error value = 1 (PCInit Invalid *Root-ID*).” So error is indicating that
> Root-ID was incorrect, but in reality Tree-ID was incorrectly. Wouldn’t it
> be better to have dedicated error value for that? It seems to be a bit
> misleading.
>
>
>
> HB> thanks good catch
>
>
>
> 6. *Missing association object error*
>
> When association object is missing, then error “Error-Type = X2 (SR P2MP
> Policy General Error) and Error value = 4 (*Invalid Instance-ID*)” is
> used. Is that really intentional? It seems to be re-used for unrelated
> purpose.
>
>
>
> HB> ok thanks cleaned the errors now create a new error for missing
> association object
>
>
>
> 7. *Node role TLV which was not defined*
>
> In Appendix ("SR P2MP Policy Candidate Path Init” part), there is TLV with
> “Type=Node Role” used, but I don’t see any such TLV defined anywhere. Was
> this really replaced by “role” field from CCI object? Note there is also
> another instance, but with TLV type specified as TBD:
>
> | Type=TBD | Length=4 |
> |Role = ingress | Reserved |
>
>
>
> HB> ok thanks
>
>
>
>
>
> 8. *Referenced PCE CC capability Sub TLV which is not used*
>
> In section 4.1, description of RFC9050 is talking about "A new PCE CC
> Capability sub Tlv is introduced to indicated the support to handle PCE CC
> based label download for SR P2MP.”, but how that is relevant to this
> draft? I don’t see that new sub TLV used anywhere.
>
>
>
> HB> you are correct removed.
>
>
>
> 9. *Terminology for node role*
>
> Section 5.7.2 introduced enumeration with role types, where type 1 is
> “Head”, but even text of that section is calling it already also “ingress”,
> which is then repeated in Appendix as “Role = ingress”. Also then text of
> the document is something referring to same node as a “Root”. It would be
> good to make it consistent.
>
>
>
> HB> thanks we changed it to ingress
>
>
>
> 10. *PCC with local optimization support only*
>
> Section 4.3.5 is describing that PCE can detect that PCC is not capable of
> global optimization and it is indirectly referring to field "Number of
> Instances" from "SR-P2MP-POLICY-CAPABILITY” TLV. It would be good to have
> some normative text explaining that if “Number of Instances” is 1, then PCE
> MUST not use global optimization and also what PCC is supposed to do if it
> advertised that it does not support multiple instances, but it still
> received second instance as well. Also there is no text saying what PCE is
> supposed to set to that value SR-P2MP-POLICY-CAPABILITY TLV (e.g. MUST be
> set to 0 by PCE and ignored by PCC). Also please define scope of “Number
> of instances” (per CP, per tree,…).
>
>
>
> HB> great catch added the following to section 4.3.4
>
> When a PCC Open Message indicates support for only one instance of PTI,
> then the PCE MUST NOT include the PCC as part of global optimization
> procedures.
>
>
>
>
>
> 11. *Error handling for MUST statements*
>
> There are multiple MUST statements, e.g. section 5.5.1.1, which is saying
> that "Extended Association ID TLV" MUST be included, but there is no
> behavior defined for what MUST happen if it was not included.
>
>
>
> HB> thanks added a new error Missing Extended Association ID
>
>
>
> 12. *Outdated reference to section 8.1*
>
> In section 4.4.1, there is a statement “described further in section
> 5.5.2 and with an example in section 8.1”, but section 8.1 is
> implementation section pointing to Cisco implementation, so I assume that
> is outdated.
>
>
>
> HB> changed to Appendix A thanks!
>
>
>
> 13. *N flag in LSP object*
>
> Examples in appendix are using LSP object flags “A:1,D:1,N:1”, where N
> flag was introduced in RFC8623 (which is not mentioned anywhere in
> references), that RFC introduced multiple MUST requirements if that flag is
> set, e.g. “The S2LS object MUST be carried in a PCRpt message along with
> the END‑POINTS object when an N (P2MP) flag is set” or "If the N bit is
> set … but the P2MP‑LSP‑IDENTIFIER TLV is absent, the PCE MUST respond with
> … error‑value 14 … and close the PCEP session.”. Is that flag supposed to
> be used? Is that clarified anywhere in this draft (besides examples)?
>
>
>
> HB> removed the N flags.
>
>
>
> 14. *A lot of typos in the document,* e.g.
>
>
> - Section-title typos: "SR-P2MP-INSTACE-ID-TLV" (many times),
> "Replicatoin Segment Instantiation", "local optimizatoin", "PCEP
> Prodecures", "Operatoin Consideration".
> - "Multipath weight TLV … SHOULD be ignored when revived" → "received".
> - "trigger a local optimization … and triger" → "trigger".
> - Incomplete sentence in "Operatoin Consideration": "Otherwise the PCE
> control needs to be able to The operation consideration of P2MP policy…"
> - “artwork” word in section 4.4.3
> - Some typos in authors metadata, e.g. initials for Daniel is “V.”,
> but should be “D.”, full name for Rishabh is fullname=“Rishabh" only
> - Terminology inconsistent: "P2MP END POINT OBJECT" vs
> "P2MP-END-POINTS Object"; "Head" vs "Root" vs "ingress"; "LSP-ID" vs
> "Instance-ID"
> - ...
>
>
>
> HB> thanks going through the doc to address some of these.
>
>
>
> Thanks a lot,
>
> Samuel
>
>
>
> *From: *Dhruv Dhody <*dd@dhruvdhody.com* <dd@dhruvdhody.com>>
> *Date: *Sunday, 9 August 2026 at 19:05
> *To: **pce@ietf.org* <pce@ietf.org> <*pce@ietf.org* <pce@ietf.org>>
> *Cc: **andrew.stone@nokia.com* <andrew.stone@nokia.com> <
> *andrew.stone@nokia.com* <andrew.stone@nokia.com>>;
> *draft-ietf-pce-sr-p2mp-policy@ietf.org*
> <draft-ietf-pce-sr-p2mp-policy@ietf.org> <
> *draft-ietf-pce-sr-p2mp-policy@ietf.org*
> <draft-ietf-pce-sr-p2mp-policy@ietf.org>>; *pce-chairs@ietf.org*
> <pce-chairs@ietf.org> <*pce-chairs@ietf.org* <pce-chairs@ietf.org>>
> *Subject: *[Pce] Re: WG Last Call for draft-ietf-pce-sr-p2mp-policy-19
> (Ends 2026-08-04)
>
> Hi WG,
>
>
>
> To accommodate the Aug break, we are extending the WGLC till 24th Aug.
> Please use this opportunity to be explicit during WGLC if you wish this I-D
> to be published as an RFC!
>
>
>
> Thanks!
>
> Dhruv
>
>
>
> On Tue, Jul 7, 2026 at 3:41 PM Dhruv Dhody via Datatracker <
> *noreply@ietf.org* <noreply@ietf.org>> wrote:
>
> This message starts a WG Last Call for: draft-ietf-pce-sr-p2mp-policy-19
>
> This Working Group Last Call ends on 2026-08-04 (intentionally longer to
> accommodate IETF126 and travels)
>
> Abstract:
> Segment Routing (SR) Point-to-Multipoint (P2MP) Policies are a set of
> policies that enable architecture for P2MP service delivery. This
> document specifies extensions to the Path Computation Element
> Communication Protocol (PCEP) that allow a stateful PCE to compute
> and initiate P2MP paths for SR-MPLS from a Root to a set of Leaf
> nodes.
>
> Please indicate your support or concern for this draft on the mailing
> list. If you are opposed to the progression of the draft to RFC, please
> articulate your concern. If you support it, please indicate that you have
> read the latest version and that it is ready for publication in your
> opinion. As always, review comments and nits are most welcome.
>
> A general reminder to the WG to be more vocal during the
> last-call/adoption.
>
> Thanks,
> Dhruv & Julien
>
> The IETF datatracker status page for this Internet-Draft is:
> *https://datatracker.ietf.org/doc/draft-ietf-pce-sr-p2mp-policy/*
> <https://datatracker.ietf.org/doc/draft-ietf-pce-sr-p2mp-policy/>
>
> There is also an HTMLized version available at:
> *https://datatracker.ietf.org/doc/html/draft-ietf-pce-sr-p2mp-policy-19*
> <https://datatracker.ietf.org/doc/html/draft-ietf-pce-sr-p2mp-policy-19>
>
> A diff from the previous version is available at:
>
> *https://author-tools.ietf.org/iddiff?url2=draft-ietf-pce-sr-p2mp-policy-19*
> <https://author-tools.ietf.org/iddiff?url2=draft-ietf-pce-sr-p2mp-policy-19>
>
>
- [Pce] WG Last Call for draft-ietf-pce-sr-p2mp-pol… Dhruv Dhody via Datatracker
- [Pce] Re: WG Last Call for draft-ietf-pce-sr-p2mp… Rishabh Parekh
- [Pce] WG Last Call for draft-ietf-pce-sr-p2mp-pol… Susan Hares
- [Pce] Re: WG Last Call for draft-ietf-pce-sr-p2mp… Dhruv Dhody
- [Pce] Re: [**EXTERNAL**] Re: WG Last Call for dra… Sivabalan, Siva
- [Pce] Re: WG Last Call for draft-ietf-pce-sr-p2mp… Hooman Bidgoli (Nokia)
- [Pce] Re: WG Last Call for draft-ietf-pce-sr-p2mp… Anuj Budhiraja (abudhira)
- [Pce] Re: WG Last Call for draft-ietf-pce-sr-p2mp… Samuel Sidor (ssidor)
- [Pce] Re: WG Last Call for draft-ietf-pce-sr-p2mp… Hooman Bidgoli (Nokia)
- [Pce] Re: WG Last Call for draft-ietf-pce-sr-p2mp… Samuel Sidor (ssidor)
- [Pce] Re: WG Last Call for draft-ietf-pce-sr-p2mp… Hooman Bidgoli (Nokia)
- [Pce] Re: WG Last Call for draft-ietf-pce-sr-p2mp… Samuel Sidor (ssidor)
- [Pce] Re: WG Last Call for draft-ietf-pce-sr-p2mp… Hooman Bidgoli (Nokia)
- [Pce] Re: WG Last Call for draft-ietf-pce-sr-p2mp… Samuel Sidor (ssidor)
- [Pce] Re: WG Last Call for draft-ietf-pce-sr-p2mp… Dhruv Dhody
- [Pce] Re: [**EXTERNAL**] Re: Re: WG Last Call for…
- [Pce] Re: WG Last Call for draft-ietf-pce-sr-p2mp… Hooman Bidgoli (Nokia)
- [Pce] Re: WG Last Call for draft-ietf-pce-sr-p2mp… Dhruv Dhody
- [Pce] Re: WG Last Call for draft-ietf-pce-sr-p2mp… Hooman Bidgoli (Nokia)
- [Pce] Re: WG Last Call for draft-ietf-pce-sr-p2mp… Dhruv Dhody
- [Pce] Re: WG Last Call for draft-ietf-pce-sr-p2mp… Hooman Bidgoli (Nokia)
- [Pce] Re: WG Last Call for draft-ietf-pce-sr-p2mp… Adrian Farrel
- [Pce] Re: WG Last Call for draft-ietf-pce-sr-p2mp… Hooman Bidgoli (Nokia)
- [Pce] Re: WG Last Call for draft-ietf-pce-sr-p2mp… Dhruv Dhody
- [Pce] Re: WG Last Call for draft-ietf-pce-sr-p2mp… Diego Achaval (Nokia)
- [Pce] Re: WG Last Call for draft-ietf-pce-sr-p2mp… Mike Koldychev
- [Pce] Re: WG Last Call for draft-ietf-pce-sr-p2mp… Hooman Bidgoli (Nokia)
- [Pce] Re: WG Last Call for draft-ietf-pce-sr-p2mp… Stig Venaas