RE: RFC 2460 issue
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: RFC 2460 issue
It is perfectly valid to originate packets with Hop Count set to zero. Such
packets, if received, must not be forwarded. However they should be accepted
by a receiving node to which these packets are sent to.
Dimitry
> -----Original Message-----
> From: Fred Templin [mailto:ftemplin@iprg.nokia.com]
> Sent: Tuesday, October 28, 2003 2:35 PM
> To: Alain Durand
> Cc: ipv6@ietf.org
> Subject: Re: RFC 2460 issue
>
>
> Don't know about the sending host, but perhaps the next forwarding
> hop should send an ICMPv6 parameter problem message (RFC 2463,
> section 3.4) if it gets a packet with Hop Count = 0?
>
> Trouble is, the original source of the IPv6 packet might be different
> than the previous hop which made the mistake forwarding the packet
> with Hop Count = 0. So, the ICMPv6 parameter problem message
> might be of little value to the original source.
>
> Fred
> ftemplin@iprg.nokia.com
>
>
> Alain Durand wrote:
>
> > I had this question yesterday and I couldn't find an answer
> in RFC2460:
> >
> > Is it valid for a host to send a packet with Hop Count set to zero?
> >
> > - Alain.
> >
> >
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
>
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.