On Mon, 23 Jun 2014, Fernando Gont wrote:
> On 06/20/2014 12:13 PM, Eric Vyncke (evyncke) wrote:
> > - 3.5 I do not like the idea that error messages should not be generated
> > when destination is a multicast...
>
> That's in the specs already (RFC4443) -- the only thing that I had
> proposed to change at the time was the response to unsupported options
> of type 10xxxxxx.
>
> > We need at least packet too big as well
> > as parameter problem if we still dream about mcasted IPv6 video streaming
>
> That would go against RFC4443.
That's not what I read. Section 2.4(e) says:
(e) An ICMPv6 error message MUST NOT be originated as a result of
receiving the following:
(e.1) An ICMPv6 error message.
(e.2) An ICMPv6 redirect message [IPv6-DISC].
(e.3) A packet destined to an IPv6 multicast address. (There are
two exceptions to this rule: (1) the Packet Too Big Message
(Section 3.2) to allow Path MTU discovery to work for IPv6
multicast, and (2) the Parameter Problem Message, Code 2
(Section 3.4) reporting an unrecognized IPv6 option (see
Section 4.2 of [IPv6]) that has the Option Type highest-
order two bits set to 10).
Seems like PTB is always allowed/required.
//cmh
_______________________________________________
OPSEC mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/opsec
