Hi Herbie,

>What about taking advantage of the ICMP error mechanism?

As the draft says, ICMP error messages already include the header and
payload of the original "offending" packet, including for example the
Time Exceeded messages in Traceroute.
The Loopback exchange is similar to Echo, except that the reply
includes the header and payload of the Request, which is similar in
that context to error messages.

Cheers,
Tal.

On Wed, Jun 7, 2023 at 3:20 PM Robinson, Herbie
<[email protected]> wrote:
>
> What about taking advantage of the ICMP error mechanism?
>
> >From Phone
> ________________________________
> From: Int-area <[email protected]> on behalf of Florian Obser 
> <[email protected]>
> Sent: Wednesday, June 7, 2023 8:15:21 AM
> To: Luigi IANNONE <[email protected]>
> Cc: [email protected] <[email protected]>; [email protected] <[email protected]>
> Subject: [EXTERNAL] Re: [Int-area] [IPv6] New Draft - ICMPv6 Loopback
>
> [EXTERNAL SENDER: This email originated from outside of Stratus Technologies. 
> Do not click links or open attachments unless you recognize the sender and 
> know the content is safe.]
>
> On 2023-06-07 11:42 UTC, Luigi IANNONE 
> <[email protected]> wrote:
> > For FreeBSD it looks like code MUST be 0 or the packet is dropped:
> >
>
> this is coming from KAME so everything that derives from there has
> this. E.g. it's also present in OpenBSD & NetBSD.
>
> > (file netinet6/icmp6.c line 550: 
> > http://fxr.watson.org/fxr/source/netinet6/icmp6.c#L550)
> >
> >
> > case ICMP6_ECHO_REQUEST:
> > icmp6_ifstat_inc(ifp, ifs6_in_echo);
> > if (code != 0)
> > goto badcode;
> >
> >
> > Ciao
> >
> > L.
>
> --
> In my defence, I have been left unsupervised.
>
> _______________________________________________
> Int-area mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/int-area
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> [email protected]
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

_______________________________________________
Int-area mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/int-area

Reply via email to