[OPS-AREA]Re: Proposals for ICMP Extensions: Operational M otivations & Rationale
"Joe Clarke \(jclarke\)" <[email protected]> Fri, 24 Jul 2026 12:50:44 +0000
| Newsgroups | gmane.ietf.ops,gmane.ietf.opsawg,gmane.ietf.int |
|---|---|
| Message-ID | <CH2PR11MB886739ED59953775D9620729B8CF2@CH2PR11MB8867.namprd11.prod.outlook.com> |
--===============4069890536822798328== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_CH2PR11MB886739ED59953775D9620729B8CF2CH2PR11MB8867namp_" --_000_CH2PR11MB886739ED59953775D9620729B8CF2CH2PR11MB8867namp_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable If we=92re going to do this in opsawg, I can create a repo for us in our or= g and push the current text there. Just throwing this in as a thought as i IIRC did not note this at the mic; I coarsely see two groups in here; What I think might be a good thing is clarifying the creation of state (specific to ICMP/ICMPv6) via ICMP/ICMPv6 messages and/or state dependence. That will entail some security considerations tied to that. [JMC] Not just state. Some of those drafts expose access to management dat= a that has traditionally been protected behind some form of credential. Ex= posing it to =93anyone=94 with no real accountability definitely raises the= ir own security considerations. Joe --_000_CH2PR11MB886739ED59953775D9620729B8CF2CH2PR11MB8867namp_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1= 252"> </head> <body> <div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se= rif; font-size: 12pt; color: rgb(0, 0, 0);"> If we=92re going to do this in opsawg, I can create a repo for us in our or= g and push the current text there.<span style=3D"font-size: 11pt;"><br> <br> Just throwing this in as a thought as i IIRC did not note this at the<br> mic; I coarsely see two groups in here; What I think might be a good<br> thing is clarifying the creation of state (specific to ICMP/ICMPv6) via<br> ICMP/ICMPv6 messages and/or state dependence. That will entail some<br> security considerations tied to that.</span></div> <div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-se= rif; font-size: 11pt; color: rgb(0, 0, 0);"> <br> </div> <div style=3D"direction: ltr;"><span style=3D"font-size: 11pt;">[JMC] Not j= ust state. Some of those drafts expose access to management data that= has traditionally been protected behind some form of credential. Exp= osing it to </span><span style=3D"font-size: 14.666667px;">=93</span><span style=3D"fon= t-size: 11pt;">anyone</span><span style=3D"font-size: 14.666667px;">=94</sp= an><span style=3D"font-size: 11pt;"> with no real accountability defin= itely raises their own security considerations.</span></div> <div style=3D"direction: ltr; font-size: 14.666667px;"><br> </div> <div style=3D"direction: ltr;"><span style=3D"font-size: 14.666667px;">Joe<= br> </span><br> <br> </div> </body> </html> --_000_CH2PR11MB886739ED59953775D9620729B8CF2CH2PR11MB8867namp_-- --===============4069890536822798328== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KT1BTLUFSRUEg bWFpbGluZyBsaXN0IC0tIG9wcy1hcmVhQGlldGYub3JnClRvIHVuc3Vic2NyaWJlIHNlbmQgYW4g ZW1haWwgdG8gb3BzLWFyZWEtbGVhdmVAaWV0Zi5vcmcK --===============4069890536822798328==--