[pim] Re: [IANA #1446138] Early review: draft-ietf-p im-rfc8059-9798bis-00 (IETF 125)
"Vengada Prasad Govindan \(venggovi\)" <[email protected]> Sat, 14 Mar 2026 15:16:41 +0000
| Newsgroups | gmane.ietf.pim |
|---|---|
| Message-ID | <DM8PR11MB56224F0655EC2F8024C34684CD42A@DM8PR11MB5622.namprd11.prod.outlook.com> |
Hello Amanda/ IANA, First my thanks for your detailed note, please see inline responses with GVP1>. I have attached the diff for your review. Please let me know if further changes are required Thanks Prasad ________________________________ From: Amanda Baber via RT <[email protected]> Sent: Thursday, March 12, 2026 6:42 AM Cc: [email protected] <[email protected]>; [email protected] <[email protected]> Subject: [pim] [IANA #1446138] Early review: draft-ietf-pim-rfc8059-9798bis-00 (IETF 125) Dear Authors, Before the IETF meeting, we check working group agendas for documents with IANA-related issues. We have notes about this document: https://datatracker.ietf.org/doc/html/draft-ietf-pim-rfc8059-9798bis-00 I see that the IANA Considerations section from RFC 8059 has been carried over here. I just want to confirm that it’s correct for this document to serve as the new reference for the RFC 8059 registry and registrations. From what we’ve seen, this generally happens when a document is obsoleted, but not necessarily when it’s just being updated. I have no insight into this case, though. GVP1> Since the bis document is in Standards track and the two prior documents (RFC8059 & 9798 were experimental) I think the bis should obsolete the old ones. I will change the headers of the bis to reflect this. Thanks for pointing this out. Hence as a corollary, the IANA code points should be now owned by the bis (new RFC). What I would say is that it’s confusing to read that “IANA is asked to assign” values that we’ve already assigned. It would be better to say that IANA is asked to update the references for the following registrations and registry created by RFC 8059 to point to this document, and update the language in the next two paragraphs to indicate that these actions are complete. GVP1> I will change the language to note that IANA is requested to update the reference of the code points. There's a discussion of "bis" document language in draft-ietf-ianabis-rfc8126bis-01, Section 8 that might be useful here. The reference to “Two new PIM Join/Prune attribute types” (carried over from RFC 8059) is also a little confusing in that the registry the assignments come from is called “PIM Join Attribute Types,” not “PIM Join/Prune Attribute Types.” The fact that the next paragraph creates a “PIM Join/Prune Transport Types” registry makes it sound like the “Prune” in “Join/Prune attribute types” could have been a copy/paste error. This is something we should've caught before 8059 was published. GVP1> I will do s/PIM Join/ Prune Attribute types/ PIM Join attribute types. If you have any questions, just let us know. If you'd like to talk in person, you can find us next to the RFC Editor's table from Monday through Thursday. You can also request another review at any time by contacting us at [email protected]. For more information about IANA Considerations section requirements, please see https://www.iana.org/help/protocol-registration Best regards, Amanda Baber IANA _______________________________________________ pim mailing list -- [email protected] To unsubscribe send an email to [email protected] _______________________________________________ pim mailing list -- [email protected] To unsubscribe send an email to [email protected]
draft-ietf-pim-rfc8059-9798bis-01.diff.html
(text/html, 41.1 KB)
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Diff: draft-ietf-pim-rfc8059-9798bis-01.txt - draft-ietf-pim-rfc8059-9798bis-00.txt</title>
<style>
body {font-family: monospace}
table {
border-spacing: 0;
}
td {
padding: 0;
white-space: pre;
vertical-align: top;
font-size: 0.86em;
}
th {
padding: 0;
text-align: center;
}
.left { background-color: #EEE; }
.right { background-color: #FFF; }
.lblock { background-color: #BFB; }
.rblock { background-color: #FF8; }
.delete { background-color: #ACF; }
.insert { background-color: #8FF; }
.change { background-color: gray; }
.header { background-color: orange; }
.w-delete {
color: #F00;
text-decoration: line-through;
}
.w-insert {
color: #008000;
font-weight: bold;
}
</style>
</head>
<body>
<table>
<tbody>
<tr>
<td> </td>
<th class="header" scope="col">draft-ietf-pim-rfc8059-9798bis-01.txt</th>
<td> </td>
<th class="header" scope="col">draft-ietf-pim-rfc8059-9798bis-00.txt</th>
</tr>
<tr>
<td> </td>
<td class="left">
</td>
<td> </td>
<td class="right">
</td>
</tr>
<tr>
<td> </td>
<td class="left">
</td>
<td> </td>
<td class="right">
</td>
</tr>
<tr>
<td> </td>
<td class="left">
</td>
<td> </td>
<td class="right">
</td>
</tr>
<tr>
<td> </td>
<td class="left">
</td>
<td> </td>
<td class="right">
</td>
</tr>
<tr>
<td> </td>
<td class="left">Internet Engineering Task Force V. Govindan
</td>
<td> </td>
<td class="right">Internet Engineering Task Force V. Govindan
</td>
</tr>
<tr>
<td> </td>
<td class="left">Internet-Draft S. Venaas
</td>
<td> </td>
<td class="right">Internet-Draft S. Venaas
</td>
</tr>
<tr>
<td> </td>
<td class="lblock"><span class="delete">Obsole</span>tes: 8059, 9798 (if approved) Cisco
</td>
<td> </td>
<td class="rblock"><span class="insert">Upda</span>tes: 8059, 9798 (if approved) <span class="insert"> </span>Cisco
</td>
</tr>
<tr>
<td> </td>
<td class="lblock">Intended status: Standards Track <span class="delete"> 1</span>4 <span class="delete">M</span>ar<span class="delete">ch</span> 2026
</td>
<td> </td>
<td class="rblock">Intended status: Standards Track 4 <span class="insert">Janu</span>ar<span class="insert">y</span> 2026
</td>
</tr>
<tr>
<td> </td>
<td class="lblock"><span class="delete">Expires: 15 September 2026
</span></td>
<td> </td>
<td class="rblock"><span class="insert">Expires: 8 July 2026
</span></td>
</tr>
<tr>
<td> </td>
<td class="left">
</td>
<td> </td>
<td class="right">
</td>
</tr>
<tr>
<td> </td>
<td class="left">
</td>
<td> </td>
<td class="right">
</td>
</tr>
<tr>
<td> </td>
<td class="left"> PIM Join Attributes for Locator/ID Separation Protocol (LISP)
</td>
<td> </td>
<td class="right"> PIM Join Attributes for Locator/ID Separation Protocol (LISP)
</td>
</tr>
<tr>
<td> </td>
<td class="left"> Environments
</td>
<td> </td>
<td class="right"> Environments
</td>
</tr>
<tr>
<td> </td>
<td class="lblock"> draft-ietf-pim-rfc8059-9798bis-0<span class="delete">1</span>
</td>
<td> </td>
<td class="rblock"> draft-ietf-pim-rfc8059-9798bis-0<span class="insert">0</span>
</td>
</tr>
<tr>
<td> </td>
<td class="left">
</td>
<td> </td>
<td class="right">
</td>
</tr>
<tr>
<td> </td>
<td class="left">Abstract
</td>
<td> </td>
<td class="right">Abstract
</td>
</tr>
<tr>
<td> </td>
<td class="left">
</td>
<td> </td>
<td class="right">
</td>
</tr>
<tr>
<td> </td>
<td class="left"> This document defines two PIM Join/Prune attributes that support the
</td>
<td> </td>
<td class="right"> This document defines two PIM Join/Prune attributes that support the
</td>
</tr>
<tr>
<td> </td>
<td class="left"> construction of multicast distribution trees where the root and
</td>
<td> </td>
<td class="right"> construction of multicast distribution trees where the root and
</td>
</tr>
<tr>
<td> </td>
<td class="left"> receivers are located in different Locator/ID Separation Protocol
</td>
<td> </td>
<td class="right"> receivers are located in different Locator/ID Separation Protocol
</td>
</tr>
<tr>
<td> </td>
<td class="left"> (LISP) sites. These attributes allow the receiver site to select
</td>
<td> </td>
<td class="right"> (LISP) sites. These attributes allow the receiver site to select
</td>
</tr>
<tr>
<td> </td>
<td class="left"> between unicast and multicast underlying transport, to convey the
</td>
<td> </td>
<td class="right"> between unicast and multicast underlying transport, to convey the
</td>
</tr>
<tr>
<td> </td>
<td class="left"> </td>
<td> </td>
<td class="right"> </td>
</tr>
<tr id="context-0">
<td></td>
<th class="change" scope="col">
<a href="#context-0">
<small>Skipping</small>
</a>
</th>
<td></td>
<th class="change" scope="col">
<a href="#context-0">
<small>Skipping</small>
</a>
</th>
</tr>
<tr>
<td> </td>
<td class="left"> working documents as Internet-Drafts. The list of current Internet-
</td>
<td> </td>
<td class="right"> working documents as Internet-Drafts. The list of current Internet-
</td>
</tr>
<tr>
<td> </td>
<td class="left"> Drafts is at https://datatracker.ietf.org/drafts/current/.
</td>
<td> </td>
<td class="right"> Drafts is at https://datatracker.ietf.org/drafts/current/.
</td>
</tr>
<tr>
<td> </td>
<td class="left">
</td>
<td> </td>
<td class="right">
</td>
</tr>
<tr>
<td> </td>
<td class="left"> Internet-Drafts are draft documents valid for a maximum of six months
</td>
<td> </td>
<td class="right"> Internet-Drafts are draft documents valid for a maximum of six months
</td>
</tr>
<tr>
<td> </td>
<td class="left"> and may be updated, replaced, or obsoleted by other documents at any
</td>
<td> </td>
<td class="right"> and may be updated, replaced, or obsoleted by other documents at any
</td>
</tr>
<tr>
<td> </td>
<td class="left"> time. It is inappropriate to use Internet-Drafts as reference
</td>
<td> </td>
<td class="right"> time. It is inappropriate to use Internet-Drafts as reference
</td>
</tr>
<tr>
<td> </td>
<td class="left"> material or to cite them other than as "work in progress."
</td>
<td> </td>
<td class="right"> material or to cite them other than as "work in progress."
</td>
</tr>
<tr>
<td> </td>
<td class="left">
</td>
<td> </td>
<td class="right">
</td>
</tr>
<tr>
<td> </td>
<td class="lblock"> This Internet-Draft will expire on <span class="delete">15 September</span> 2026.
</td>
<td> </td>
<td class="rblock"> This Internet-Draft will expire on <span class="insert">8 July</span> 2026.
</td>
</tr>
<tr>
<td> </td>
<td class="left">
</td>
<td> </td>
<td class="right">
</td>
</tr>
<tr>
<td> </td>
<td class="left">Copyright Notice
</td>
<td> </td>
<td class="right">Copyright Notice
</td>
</tr>
<tr>
<td> </td>
<td class="left">
</td>
<td> </td>
<td class="right">
</td>
</tr>
<tr>
<td> </td>
<td class="left"> Copyright (c) 2026 IETF Trust and the persons identified as the
</td>
<td> </td>
<td class="right"> Copyright (c) 2026 IETF Trust and the persons identified as the
</td>
</tr>
<tr>
<td> </td>
<td class="left"> document authors. All rights reserved.
</td>
<td> </td>
<td class="right"> document authors. All rights reserved.
</td>
</tr>
<tr>
<td> </td>
<td class="left">
</td>
<td> </td>
<td class="right">
</td>
</tr>
<tr>
<td> </td>
<td class="left"> This document is subject to BCP 78 and the IETF Trust's Legal
</td>
<td> </td>
<td class="right"> This document is subject to BCP 78 and the IETF Trust's Legal
</td>
</tr>
<tr>
<td> </td>
<td class="left"> Provisions Relating to IETF Documents (https://trustee.ietf.org/
</td>
<td> </td>
<td class="right"> Provisions Relating to IETF Documents (https://trustee.ietf.org/
</td>
</tr>
<tr>
<td> </td>
<td class="left"> </td>
<td> </td>
<td class="right"> </td>
</tr>
<tr id="context-1">
<td></td>
<th class="change" scope="col">
<a href="#context-1">
<small>Skipping</small>
</a>
</th>
<td></td>
<th class="change" scope="col">
<a href="#context-1">
<small>Skipping</small>
</a>
</th>
</tr>
<tr>
<td> </td>
<td class="left"> 4.2.1. Multicast Address Range constraints: . . . . . . . . 6
</td>
<td> </td>
<td class="right"> 4.2.1. Multicast Address Range constraints: . . . . . . . . 6
</td>
</tr>
<tr>
<td> </td>
<td class="left"> 4.3. Receiver RLOC Attribute format . . . . . . . . . . . . . 7
</td>
<td> </td>
<td class="right"> 4.3. Receiver RLOC Attribute format . . . . . . . . . . . . . 7
</td>
</tr>
<tr>
<td> </td>
<td class="left"> 4.4. Using the Receiver RLOC Attribute . . . . . . . . . . . . 8
</td>
<td> </td>
<td class="right"> 4.4. Using the Receiver RLOC Attribute . . . . . . . . . . . . 8
</td>
</tr>
<tr>
<td> </td>
<td class="left"> 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9
</td>
<td> </td>
<td class="right"> 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9
</td>
</tr>
<tr>
<td> </td>
<td class="left"> 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
</td>
<td> </td>
<td class="right"> 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
</td>
</tr>
<tr>
<td> </td>
<td class="left"> 7. Security Considerations . . . . . . . . . . . . . . . . . . . 9
</td>
<td> </td>
<td class="right"> 7. Security Considerations . . . . . . . . . . . . . . . . . . . 9
</td>
</tr>
<tr>
<td> </td>
<td class="left"> 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 10
</td>
<td> </td>
<td class="right"> 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 10
</td>
</tr>
<tr>
<td> </td>
<td class="left"> 9. Normative References . . . . . . . . . . . . . . . . . . . . 10
</td>
<td> </td>
<td class="right"> 9. Normative References . . . . . . . . . . . . . . . . . . . . 10
</td>
</tr>
<tr>
<td> </td>
<td class="lblock"> Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 1<span class="delete">1</span>
</td>
<td> </td>
<td class="rblock"> Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 1<span class="insert">2</span>
</td>
</tr>
<tr>
<td> </td>
<td class="left">
</td>
<td> </td>
<td class="right">
</td>
</tr>
<tr>
<td> </td>
<td class="left">1. Introduction
</td>
<td> </td>
<td class="right">1. Introduction
</td>
</tr>
<tr>
<td> </td>
<td class="left">
</td>
<td> </td>
<td class="right">
</td>
</tr>
<tr>
<td> </td>
<td class="left"> The construction of multicast distribution trees where the root and
</td>
<td> </td>
<td class="right"> The construction of multicast distribution trees where the root and
</td>
</tr>
<tr>
<td> </td>
<td class="left"> receivers are located in different LISP sites [RFC9300] is defined in
</td>
<td> </td>
<td class="right"> receivers are located in different LISP sites [RFC9300] is defined in
</td>
</tr>
<tr>
<td> </td>
<td class="left"> [I-D.ietf-lisp-rfc6831bis]. Creation of (root-EID,G) state in the
</td>
<td> </td>
<td class="right"> [I-D.ietf-lisp-rfc6831bis]. Creation of (root-EID,G) state in the
</td>
</tr>
<tr>
<td> </td>
<td class="left"> root site requires that unicast LISP-encapsulated Join/Prune messages
</td>
<td> </td>
<td class="right"> root site requires that unicast LISP-encapsulated Join/Prune messages
</td>
</tr>
<tr>
<td> </td>
<td class="left"> be sent from an ETR on the receiver site to an ITR on the root site.
</td>
<td> </td>
<td class="right"> be sent from an ETR on the receiver site to an ITR on the root site.
</td>
</tr>
<tr>
<td> </td>
<td class="left"> </td>
<td> </td>
<td class="right"> </td>
</tr>
<tr id="context-2">
<td></td>
<th class="change" scope="col">
<a href="#context-2">
<small>Skipping</small>
</a>
</th>
<td></td>
<th class="change" scope="col">
<a href="#context-2">
<small>Skipping</small>
</a>
</th>
</tr>
<tr>
<td> </td>
<td class="left">
</td>
<td> </td>
<td class="right">
</td>
</tr>
<tr>
<td> </td>
<td class="left">
</td>
<td> </td>
<td class="right">
</td>
</tr>
<tr>
<td> </td>
<td class="left">5. Acknowledgements
</td>
<td> </td>
<td class="right">5. Acknowledgements
</td>
</tr>
<tr>
<td> </td>
<td class="left">
</td>
<td> </td>
<td class="right">
</td>
</tr>
<tr>
<td> </td>
<td class="left"> TBD
</td>
<td> </td>
<td class="right"> TBD
</td>
</tr>
<tr>
<td> </td>
<td class="left">
</td>
<td> </td>
<td class="right">
</td>
</tr>
<tr>
<td> </td>
<td class="left">6. IANA Considerations
</td>
<td> </td>
<td class="right">6. IANA Considerations
</td>
</tr>
<tr>
<td> </td>
<td class="left">
</td>
<td> </td>
<td class="right">
</td>
</tr>
<tr>
<td> </td>
<td class="lblock"> Following the guidelines of [RFC8126], IANA is asked to u<span class="delete">pdat</span>e<span class="delete"> the</span>
</td>
<td> </td>
<td class="rblock"> Following the guidelines of [RFC8126], IANA is asked to <span class="insert">assign val</span>ue<span class="insert">s</span>
</td>
</tr>
<tr>
<td> </td>
<td class="lblock"><span class="delete"> references for the following registrations as follows:
</span></td>
<td> </td>
<td class="rblock"><span class="insert"> as follows:
</span></td>
</tr>
<tr>
<td> </td>
<td class="left">
</td>
<td> </td>
<td class="right">
</td>
</tr>
<tr>
<td> </td>
<td class="lblock"><span class="delete"> Two PIM Join attribute types need to be updated: value 5 for the
</span></td>
<td> </td>
<td class="rblock"><span class="insert"> Two new PIM Join/Prune attribute types have been requested: value 5
</span></td>
</tr>
<tr>
<td> </td>
<td class="lblock"> Transport Attribute and value 6 for the Receiver RLOC<span class="delete"> Attribute</span>
</td>
<td> </td>
<td class="rblock"> <span class="insert"> for the</span> Transport Attribute and value 6 for the Receiver RLOC
</td>
</tr>
<tr>
<td> </td>
<td class="lblock"><span class="delete"> earlier allocated through [RFC8059] and [RFC9798] are to be updated
</span></td>
<td> </td>
<td class="rblock"><span class="insert"> Attribute[RFC8059] and [RFC9798].
</span></td>
</tr>
<tr>
<td> </td>
<td class="lblock"><span class="delete"> to be owned by this document.
</span></td>
<td> </td>
<td class="rblock"></td>
</tr>
<tr>
<td> </td>
<td class="left">
</td>
<td> </td>
<td class="right">
</td>
</tr>
<tr>
<td> </td>
<td class="lblock"> The "PIM Join/Prune Transport Types" registry e<span class="delete">xis</span>t<span class="delete">s</span> for<span class="delete"> the Join/</span>
</td>
<td> </td>
<td class="rblock"> The "PIM Join/Prune Transport Types" registry <span class="insert">has b</span>e<span class="insert">en crea</span>t<span class="insert">ed</span> for
</td>
</tr>
<tr>
<td> </td>
<td class="lblock"> Prune Transport attribute. The registration policy is IETF<span class="delete"> Review</span>
</td>
<td> </td>
<td class="rblock"> <span class="insert">the Join/</span>Prune Transport attribute. The registration policy is IETF
</td>
</tr>
<tr>
<td> </td>
<td class="lblock"> [RFC5226], and the values are in the range 0-255. This<span class="delete"> document</span>
</td>
<td> </td>
<td class="rblock"> <span class="insert"> Review</span> [RFC5226], and the values are in the range 0-255. This
</td>
</tr>
<tr>
<td> </td>
<td class="lblock"><span class="delete"> should be the updated reference for value 0 for multicast and value 1
</span></td>
<td> </td>
<td class="rblock"><span class="insert"> document requests value 0 for multicast and value 1 for unicast
</span></td>
</tr>
<tr>
<td> </td>
<td class="lblock"><span class="delete"> for unicast. These values were earlier owned by [RFC8059] and
</span></td>
<td> </td>
<td class="rblock"><span class="insert"> [RFC8059] and [RFC9798].
</span></td>
</tr>
<tr>
<td> </td>
<td class="lblock"><span class="delete"> [RFC9798].
</span></td>
<td> </td>
<td class="rblock"></td>
</tr>
<tr>
<td> </td>
<td class="left">
</td>
<td> </td>
<td class="right">
</td>
</tr>
<tr>
<td> </td>
<td class="left">7. Security Considerations
</td>
<td> </td>
<td class="right">7. Security Considerations
</td>
</tr>
<tr>
<td> </td>
<td class="left">
</td>
<td> </td>
<td class="right">
</td>
</tr>
<tr>
<td> </td>
<td class="left"> Security of Join/Prune attributes is only guaranteed by the security
</td>
<td> </td>
<td class="right"> Security of Join/Prune attributes is only guaranteed by the security
</td>
</tr>
<tr>
<td> </td>
<td class="left"> of the PIM packet. The attributes specified herein do not enhance or
</td>
<td> </td>
<td class="right"> of the PIM packet. The attributes specified herein do not enhance or
</td>
</tr>
<tr>
<td> </td>
<td class="left"> diminish the privacy or authenticity of a Join/Prune message. A site
</td>
<td> </td>
<td class="right"> diminish the privacy or authenticity of a Join/Prune message. A site
</td>
</tr>
<tr>
<td> </td>
<td class="left"> that legitimately or maliciously sends and delivers a Join/Prune
</td>
<td> </td>
<td class="right"> that legitimately or maliciously sends and delivers a Join/Prune
</td>
</tr>
<tr>
<td> </td>
<td class="left"> message to another site will equally be able to append these and any
</td>
<td> </td>
<td class="right"> message to another site will equally be able to append these and any
</td>
</tr>
<tr>
<td> </td>
<td class="left"> </td>
<td> </td>
<td class="right"> </td>
</tr>
<tr id="context-3">
<td></td>
<th class="change" scope="col">
<a href="#context-3">
<small>Skipping</small>
</a>
</th>
<td></td>
<th class="change" scope="col">
<a href="#context-3">
<small>Skipping</small>
</a>
</th>
</tr>
<tr>
<td> </td>
<td class="left"> considerations for Join/Prune attributes.
</td>
<td> </td>
<td class="right"> considerations for Join/Prune attributes.
</td>
</tr>
<tr>
<td> </td>
<td class="left">
</td>
<td> </td>
<td class="right">
</td>
</tr>
<tr>
<td> </td>
<td class="left"> An attack vector arises where an attacker sends numerous PIM Join
</td>
<td> </td>
<td class="right"> An attack vector arises where an attacker sends numerous PIM Join
</td>
</tr>
<tr>
<td> </td>
<td class="left"> messages with different group addresses. This could interfere with
</td>
<td> </td>
<td class="right"> messages with different group addresses. This could interfere with
</td>
</tr>
<tr>
<td> </td>
<td class="left"> legitimate multicast traffic if the group addresses overlap.
</td>
<td> </td>
<td class="right"> legitimate multicast traffic if the group addresses overlap.
</td>
</tr>
<tr>
<td> </td>
<td class="left"> Additionally, resource exhaustion may occur if replication is
</td>
<td> </td>
<td class="right"> Additionally, resource exhaustion may occur if replication is
</td>
</tr>
<tr>
<td> </td>
<td class="left"> requested for a large number of groups, potentially resulting in
</td>
<td> </td>
<td class="right"> requested for a large number of groups, potentially resulting in
</td>
</tr>
<tr>
<td> </td>
<td class="left"> significant resource consumption.
</td>
<td> </td>
<td class="right"> significant resource consumption.
</td>
</tr>
<tr>
<td> </td>
<td class="lblock"></td>
<td> </td>
<td class="rblock"></td>
</tr>
<tr>
<td> </td>
<td class="left"> To mitigate these risks, PIM authentication mechanisms RFC 5796
</td>
<td> </td>
<td class="right"> To mitigate these risks, PIM authentication mechanisms RFC 5796
</td>
</tr>
<tr>
<td> </td>
<td class="left"> [RFC5796] could be employed to validate join requests. Furthermore,
</td>
<td> </td>
<td class="right"> [RFC5796] could be employed to validate join requests. Furthermore,
</td>
</tr>
<tr>
<td> </td>
<td class="left"> implementations may consider explicit tracking mechanisms to manage
</td>
<td> </td>
<td class="right"> implementations may consider explicit tracking mechanisms to manage
</td>
</tr>
<tr>
<td> </td>
<td class="left"> joins more effectively. Configurable controls could be introduced,
</td>
<td> </td>
<td class="right"> joins more effectively. Configurable controls could be introduced,
</td>
</tr>
<tr>
<td> </td>
<td class="left"> allowing for a maximum permissible number of groups for each ETR RLOC
</td>
<td> </td>
<td class="right"> allowing for a maximum permissible number of groups for each ETR RLOC
</td>
</tr>
<tr>
<td> </td>
<td class="left"> used as the source of overlay joins. These controls would limit the
</td>
<td> </td>
<td class="right"> used as the source of overlay joins. These controls would limit the
</td>
</tr>
<tr>
<td> </td>
<td class="left"> impact of such attacks and ensure that resource allocation is managed
</td>
<td> </td>
<td class="right"> impact of such attacks and ensure that resource allocation is managed
</td>
</tr>
<tr>
<td> </td>
<td class="left"> appropriately.
</td>
<td> </td>
<td class="right"> appropriately.
</td>
</tr>
<tr>
<td> </td>
<td class="left"> </td>
<td> </td>
<td class="right"> </td>
</tr>
<tr id="context-4">
<td></td>
<th class="change" scope="col">
<a href="#context-4">
<small>Skipping</small>
</a>
</th>
<td></td>
<th class="change" scope="col">
<a href="#context-4">
<small>Skipping</small>
</a>
</th>
</tr>
<tr>
<td> </td>
<td class="left">
</td>
<td> </td>
<td class="right">
</td>
</tr>
<tr>
<td> </td>
<td class="left">
</td>
<td> </td>
<td class="right">
</td>
</tr>
<tr>
<td> </td>
<td class="left">9. Normative References
</td>
<td> </td>
<td class="right">9. Normative References
</td>
</tr>
<tr>
<td> </td>
<td class="left">
</td>
<td> </td>
<td class="right">
</td>
</tr>
<tr>
<td> </td>
<td class="left"> [I-D.ietf-lisp-rfc6831bis]
</td>
<td> </td>
<td class="right"> [I-D.ietf-lisp-rfc6831bis]
</td>
</tr>
<tr>
<td> </td>
<td class="left"> Farinacci, D., Meyer, D., Zwiebel, J., Venaas, S., and V.
</td>
<td> </td>
<td class="right"> Farinacci, D., Meyer, D., Zwiebel, J., Venaas, S., and V.
</td>
</tr>
<tr>
<td> </td>
<td class="left"> P. Govindan, "The Locator/ID Separation Protocol (LISP)
</td>
<td> </td>
<td class="right"> P. Govindan, "The Locator/ID Separation Protocol (LISP)
</td>
</tr>
<tr>
<td> </td>
<td class="left"> for Multicast Environments", Work in Progress, Internet-
</td>
<td> </td>
<td class="right"> for Multicast Environments", Work in Progress, Internet-
</td>
</tr>
<tr>
<td> </td>
<td class="lblock"> Draft, draft-ietf-lisp-rfc6831bis-0<span class="delete">6</span>, <span class="delete">22 Janua</span>r<span class="delete">y</span> 202<span class="delete">6</span>,
</td>
<td> </td>
<td class="rblock"> Draft, draft-ietf-lisp-rfc6831bis-0<span class="insert">5</span>, <span class="insert">18 Novembe</span>r 202<span class="insert">5</span>,
</td>
</tr>
<tr>
<td> </td>
<td class="left"> <https://datatracker.ietf.org/doc/html/draft-ietf-lisp-
</td>
<td> </td>
<td class="right"> <https://datatracker.ietf.org/doc/html/draft-ietf-lisp-
</td>
</tr>
<tr>
<td> </td>
<td class="lblock"> rfc6831bis-0<span class="delete">6</span>>.
</td>
<td> </td>
<td class="rblock"> rfc6831bis-0<span class="insert">5</span>>.
</td>
</tr>
<tr>
<td> </td>
<td class="left">
</td>
<td> </td>
<td class="right">
</td>
</tr>
<tr>
<td> </td>
<td class="left"> [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
</td>
<td> </td>
<td class="right"> [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
</td>
</tr>
<tr>
<td> </td>
<td class="left"> Requirement Levels", BCP 14, RFC 2119,
</td>
<td> </td>
<td class="right"> Requirement Levels", BCP 14, RFC 2119,
</td>
</tr>
<tr>
<td> </td>
<td class="left"> DOI 10.17487/RFC2119, March 1997,
</td>
<td> </td>
<td class="right"> DOI 10.17487/RFC2119, March 1997,
</td>
</tr>
<tr>
<td> </td>
<td class="left"> <https://www.rfc-editor.org/info/rfc2119>.
</td>
<td> </td>
<td class="right"> <https://www.rfc-editor.org/info/rfc2119>.
</td>
</tr>
<tr>
<td> </td>
<td class="left">
</td>
<td> </td>
<td class="right">
</td>
</tr>
<tr>
<td> </td>
<td class="left"> [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
</td>
<td> </td>
<td class="right"> [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
</td>
</tr>
<tr>
<td> </td>
<td class="left"> IANA Considerations Section in RFCs", RFC 5226,
</td>
<td> </td>
<td class="right"> IANA Considerations Section in RFCs", RFC 5226,
</td>
</tr>
<tr>
<td> </td>
<td class="left"> DOI 10.17487/RFC5226, May 2008,
</td>
<td> </td>
<td class="right"> DOI 10.17487/RFC5226, May 2008,
</td>
</tr>
<tr>
<td> </td>
<td class="left"> <https://www.rfc-editor.org/info/rfc5226>.
</td>
<td> </td>
<td class="right"> <https://www.rfc-editor.org/info/rfc5226>.
</td>
</tr>
<tr>
<td> </td>
<td class="lblock"></td>
<td> </td>
<td class="rblock"></td>
</tr>
<tr>
<td> </td>
<td class="left"> [RFC5384] Boers, A., Wijnands, I., and E. Rosen, "The Protocol
</td>
<td> </td>
<td class="right"> [RFC5384] Boers, A., Wijnands, I., and E. Rosen, "The Protocol
</td>
</tr>
<tr>
<td> </td>
<td class="left"> Independent Multicast (PIM) Join Attribute Format",
</td>
<td> </td>
<td class="right"> Independent Multicast (PIM) Join Attribute Format",
</td>
</tr>
<tr>
<td> </td>
<td class="left"> RFC 5384, DOI 10.17487/RFC5384, November 2008,
</td>
<td> </td>
<td class="right"> RFC 5384, DOI 10.17487/RFC5384, November 2008,
</td>
</tr>
<tr>
<td> </td>
<td class="left"> <https://www.rfc-editor.org/info/rfc5384>.
</td>
<td> </td>
<td class="right"> <https://www.rfc-editor.org/info/rfc5384>.
</td>
</tr>
<tr>
<td> </td>
<td class="lblock"></td>
<td> </td>
<td class="rblock"></td>
</tr>
<tr>
<td> </td>
<td class="left"> [RFC5796] Atwood, W., Islam, S., and M. Siami, "Authentication and
</td>
<td> </td>
<td class="right"> [RFC5796] Atwood, W., Islam, S., and M. Siami, "Authentication and
</td>
</tr>
<tr>
<td> </td>
<td class="left"> Confidentiality in Protocol Independent Multicast Sparse
</td>
<td> </td>
<td class="right"> Confidentiality in Protocol Independent Multicast Sparse
</td>
</tr>
<tr>
<td> </td>
<td class="left"> Mode (PIM-SM) Link-Local Messages", RFC 5796,
</td>
<td> </td>
<td class="right"> Mode (PIM-SM) Link-Local Messages", RFC 5796,
</td>
</tr>
<tr>
<td> </td>
<td class="left"> DOI 10.17487/RFC5796, March 2010,
</td>
<td> </td>
<td class="right"> DOI 10.17487/RFC5796, March 2010,
</td>
</tr>
<tr>
<td> </td>
<td class="left"> <https://www.rfc-editor.org/info/rfc5796>.
</td>
<td> </td>
<td class="right"> <https://www.rfc-editor.org/info/rfc5796>.
</td>
</tr>
<tr>
<td> </td>
<td class="left">
</td>
<td> </td>
<td class="right">
</td>
</tr>
<tr>
<td> </td>
<td class="left"> [RFC7761] Fenner, B., Handley, M., Holbrook, H., Kouvelas, I.,
</td>
<td> </td>
<td class="right"> [RFC7761] Fenner, B., Handley, M., Holbrook, H., Kouvelas, I.,
</td>
</tr>
<tr>
<td> </td>
<td class="left"> Parekh, R., Zhang, Z., and L. Zheng, "Protocol Independent
</td>
<td> </td>
<td class="right"> Parekh, R., Zhang, Z., and L. Zheng, "Protocol Independent
</td>
</tr>
<tr>
<td> </td>
<td class="left"> </td>
<td> </td>
<td class="right"> </td>
</tr>
<tr id="context-5">
<td></td>
<th class="change" scope="col">
<a href="#context-5">
<small>Skipping</small>
</a>
</th>
<td></td>
<th class="change" scope="col">
<a href="#context-5">
<small>Skipping</small>
</a>
</th>
</tr>
<tr>
<td> </td>
<td class="left"> Cabellos, Ed., "The Locator/ID Separation Protocol
</td>
<td> </td>
<td class="right"> Cabellos, Ed., "The Locator/ID Separation Protocol
</td>
</tr>
<tr>
<td> </td>
<td class="left"> (LISP)", RFC 9300, DOI 10.17487/RFC9300, October 2022,
</td>
<td> </td>
<td class="right"> (LISP)", RFC 9300, DOI 10.17487/RFC9300, October 2022,
</td>
</tr>
<tr>
<td> </td>
<td class="left"> <https://www.rfc-editor.org/info/rfc9300>.
</td>
<td> </td>
<td class="right"> <https://www.rfc-editor.org/info/rfc9300>.
</td>
</tr>
<tr>
<td> </td>
<td class="left">
</td>
<td> </td>
<td class="right">
</td>
</tr>
<tr>
<td> </td>
<td class="left"> [RFC9301] Farinacci, D., Maino, F., Fuller, V., and A. Cabellos,
</td>
<td> </td>
<td class="right"> [RFC9301] Farinacci, D., Maino, F., Fuller, V., and A. Cabellos,
</td>
</tr>
<tr>
<td> </td>
<td class="left"> Ed., "Locator/ID Separation Protocol (LISP) Control
</td>
<td> </td>
<td class="right"> Ed., "Locator/ID Separation Protocol (LISP) Control
</td>
</tr>
<tr>
<td> </td>
<td class="left"> Plane", RFC 9301, DOI 10.17487/RFC9301, October 2022,
</td>
<td> </td>
<td class="right"> Plane", RFC 9301, DOI 10.17487/RFC9301, October 2022,
</td>
</tr>
<tr>
<td> </td>
<td class="left"> <https://www.rfc-editor.org/info/rfc9301>.
</td>
<td> </td>
<td class="right"> <https://www.rfc-editor.org/info/rfc9301>.
</td>
</tr>
<tr>
<td> </td>
<td class="lblock"></td>
<td> </td>
<td class="rblock"></td>
</tr>
<tr>
<td> </td>
<td class="left"> [RFC9798] Govindan, V. and S. Venaas, "PIM Join/Prune Attributes for
</td>
<td> </td>
<td class="right"> [RFC9798] Govindan, V. and S. Venaas, "PIM Join/Prune Attributes for
</td>
</tr>
<tr>
<td> </td>
<td class="left"> Locator/ID Separation Protocol (LISP) Environments Using
</td>
<td> </td>
<td class="right"> Locator/ID Separation Protocol (LISP) Environments Using
</td>
</tr>
<tr>
<td> </td>
<td class="left"> Underlay Multicast", RFC 9798, DOI 10.17487/RFC9798, June
</td>
<td> </td>
<td class="right"> Underlay Multicast", RFC 9798, DOI 10.17487/RFC9798, June
</td>
</tr>
<tr>
<td> </td>
<td class="left"> 2025, <https://www.rfc-editor.org/info/rfc9798>.
</td>
<td> </td>
<td class="right"> 2025, <https://www.rfc-editor.org/info/rfc9798>.
</td>
</tr>
<tr>
<td> </td>
<td class="left">
</td>
<td> </td>
<td class="right">
</td>
</tr>
<tr>
<td> </td>
<td class="left">Authors' Addresses
</td>
<td> </td>
<td class="right">Authors' Addresses
</td>
</tr>
<tr>
<td> </td>
<td class="lblock"></td>
<td> </td>
<td class="rblock"></td>
</tr>
<tr>
<td> </td>
<td class="left"> Vengada Prasad Govindan
</td>
<td> </td>
<td class="right"> Vengada Prasad Govindan
</td>
</tr>
<tr>
<td> </td>
<td class="left"> Cisco
</td>
<td> </td>
<td class="right"> Cisco
</td>
</tr>
<tr>
<td> </td>
<td class="left"> Email: [email protected]
</td>
<td> </td>
<td class="right"> Email: [email protected]
</td>
</tr>
<tr>
<td> </td>
<td class="left">
</td>
<td> </td>
<td class="right">
</td>
</tr>
<tr>
<td> </td>
<td class="left">
</td>
<td> </td>
<td class="right">
</td>
</tr>
<tr>
<td> </td>
<td class="left"> Stig Venaas
</td>
<td> </td>
<td class="right"> Stig Venaas
</td>
</tr>
<tr>
<td> </td>
<td class="left"> Cisco
</td>
<td> </td>
<td class="right"> Cisco
</td>
</tr>
<tr>
<td> </td>
<td class="left"> Email: [email protected]
</td>
<td> </td>
<td class="right"> Email: [email protected]
</td>
</tr>
</tbody>
</table></body>
</html>