Re: Validation of Packet Too Big Payload using Echo Request

Hi Shawn,

If you are referring to the IPv6 Ready Logo Core Test Specification for
this, we have a possible problem for this validation test case for devices
that don't track ICMPv6 connections.

*"Possible Problems: * If the device under test does not support tracking
connections for ICMPv6 this test case may be omitted."

If you have other questions about IPv6 Ready please feel free to take this
to the info@ipv6ready.org.

~Tim

On Tue, Jul 28, 2020 at 7:48 AM Shawn Zhang <yuanshan_zhang=
40apple.com@dmarc.ietf.org> wrote:

> Hi Ole,
>
> I am reviving this thread.
>
> >> Frankly, I think for compliance this should be treated as a *SHOULD*
> and not as a MUST.
>
> > Yes, I think that's a correct interpretation.
> > That's what 8201 says too. "Nodes should appropriately validate..."
>
> Since RFC8201 says “SHOULD” instead of “MUST”, should this test be removed
> from the compliance test as it is not a mandatory behavior?
>
> IMHO, since the smallest packet size is capped at 1280, it won't cause too
> much risk  even if we don't verify it using Echo Request here.
>
> Bests,
> Shawn
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>