Hi, Ron,
The "*Acceptable Uses*" section reminded me of BCP 189 / RFC 7279 : An
Acceptable Use Policy for New ICMP Types and Codes.
Looks like RFC 7279 ought to be cited.
Where the document says:
*Extensibility: Some ICMP messages are extensible {{RFC4443}}.*
I wonder if RFC 4884 is actually a more effective reference. I'd add at
this point a citation to RFC 4884.
In "*Translation Considerations*"
I think key-most considerations are in
https://datatracker.ietf.org/doc/rfc5508/ and
https://datatracker.ietf.org/doc/rfc7915/
Thanks,
Carlos.
On Wed, May 22, 2024 at 6:50 PM Ron Bonica <rbonica=
[email protected]> wrote:
> Folks,
>
> Over the years, I have written several forwarding plane documents that
> mention ICMP. During the review of these documents, people have raised
> issues of the like the following:
>
>
> - shouldn't we mention that ICMP message delivery is not reliable?
> - shouldn't we mention that ICMP messages are rate limited?
> - How is the ICMP message processed at its destination?
>
>
> In each of these documents, I have added an ICMP considerations section to
> address these issues. Rather than repeating that text in every document we
> write in the future, I have abstracted it into a separate document.
>
> If anyone would like to contribute to this document, it can be found at
> https://github.com/ronbonica/ICMP
>
> Please send a private email if you are interested in contributing to the
> document.
>
>
> Ron
>
> <https://github.com/ronbonica/ICMP>
> GitHub - ronbonica/ICMP: ICMP Inherited Wisdom Draft
> <https://github.com/ronbonica/ICMP>
> ICMP Inherited Wisdom Draft. Contribute to ronbonica/ICMP development by
> creating an account on GitHub.
> github.com
>
>
>
> Juniper Business Use Only
> _______________________________________________
> Int-area mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>
_______________________________________________
Int-area mailing list -- [email protected]
To unsubscribe send an email to [email protected]
