[pim] Re: Roman Danyliw's Discuss on draft-ietf-pim-zeroco nf-mcast-addr-alloc-ps-08: (with DISCUSS and COMMENT)

Hi Roman,

Did the below understanding provide the context you were looking for?

G/

-----Original Message-----
From: Gunter van de Velde (Nokia) <[email protected]> 
Sent: Wednesday, November 19, 2025 7:08 PM
To: Roman Danyliw <[email protected]>; The IESG <[email protected]>
Cc: [email protected]; [email protected]; [email protected]; [email protected]
Subject: RE: Roman Danyliw's Discuss on draft-ietf-pim-zeroconf-mcast-addr-alloc-ps-08: (with DISCUSS and COMMENT)

Hi Roman,

Thanks for the assessment and your observations. 

Not all deliverables in PIM, and neither in most other RTG WGs, have milestones attached. It would potentially cause chairs to perpetually update milestones as things progress. Only the big ticket items have milestones. 

When looking at the charter there is item 7 that covers this deliverable:

7) Develop multicast group address allocation protocols.

It seems pretty normal for a protocol wg to publish requirements...which are protocol enabling and not directly message exchange protocols. This draft provides context for protocol drafts which are being brewed.

Hope this provides you the context you were looking for?
Be well,
G/

-----Original Message-----
From: Roman Danyliw via Datatracker <[email protected]> 
Sent: Wednesday, November 19, 2025 2:01 PM
To: The IESG <[email protected]>
Cc: [email protected]; [email protected]; [email protected]; [email protected]
Subject: Roman Danyliw's Discuss on draft-ietf-pim-zeroconf-mcast-addr-alloc-ps-08: (with DISCUSS and COMMENT)


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.



Roman Danyliw has entered the following ballot position for
draft-ietf-pim-zeroconf-mcast-addr-alloc-ps-08: 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/about/groups/iesg/statements/handling-ballot-positions/
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-pim-zeroconf-mcast-addr-alloc-ps/



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

For the PIM WG chairs and responsible AD: this document appears to describe both current deployment issues (Section 2) and requirement/considerations (Section 3, and 5).  However, these topics do not appear to be in scope of
08-02 (https://datatracker.ietf.org/doc/charter-ietf-pim/08-02/) (or 09,
https://datatracker.ietf.org/doc/charter-ietf-pim/09/) of the charter.  The closest related text is "Create multicast protocol design experience documents".  Perhaps deployment issues could be considered "protocol design experience", but requirements don't seem to be fit.

I'll note that this document was adopted in Sept-2023 when the -08 charter
(https://datatracker.ietf.org/doc/charter-ietf-pim/08/) from 2015 scoped the WG.  It also didn't have producing informational requirements/problem statement documents in scope.

Thank you for your attention to detail on milestones.  I also observe there are no milestones covering this document which would indicate an approved scope when the WG was rechartered.


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

Thank you to Joel Halpern for the GENART review, and the revisions to the document by the WG are appreciated.



_______________________________________________
pim mailing list -- [email protected]
To unsubscribe send an email to [email protected]