Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 13 Apr 2007 02:14:03 +0900
From:      JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@isl.rdc.toshiba.co.jp>
To:        Andrew McDonald <andrew@mcdonald.org.uk>
Cc:        freebsd-net@freebsd.org
Subject:   Re: IPv6 Router Alert breaks forwarding
Message-ID:  <m1y7kxms6c.wl%jinmei@isl.rdc.toshiba.co.jp>
In-Reply-To: <20070405152547.GC6798@mcdonald.org.uk>
References:  <20070404211815.GA6798@mcdonald.org.uk> <m1d52jpd5c.wl%jinmei@isl.rdc.toshiba.co.jp> <20070405081639.GB6798@mcdonald.org.uk> <m11wiyq5q5.wl%jinmei@isl.rdc.toshiba.co.jp> <20070405152547.GC6798@mcdonald.org.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
At Thu, 5 Apr 2007 16:25:47 +0100,
Andrew McDonald <andrew@mcdonald.org.uk> wrote:

> > The behavior looks reasonable, but I'd code it more explicitly with
> > some comments so that the intent is clear and others can correctly
> > modify it for future extensions.  A possible patch to implement it is
> > pasted below.  One thing I'm not really sure is whether someone is
> > using (or has used) other predefined alert values:
> > 
> >          1        Datagram contains RSVP message.
> >          2        Datagram contains an Active Networks message.
> > 
> > (I guess you're now going to use values 3-35 per RFC3175).
> > 
> > If there is a user, we need to be careful not to break compatibility.
> 
> That patch looks good to me.
> 
> I think RSVP is the only other potential current user (and most likely
> without RFC3175 support). There appears to be some basic support for
> IPv6 in the ISI RSVPd implementation (untouched since 1999), but from a
> quick look at the code it is not clear whether they actually use the
> IPv6 router alert anyway. It predates RFC3175. If you want to be very
> conservative in changing behaviour you might want to include RSVP, but
> it seems unlikely that anyone is using it.
> 
> The only reference I know of for the Active Networks use is a published
> paper (and the reference in RFC2711). I don't know of any running code.

Okay, if no one else objects to it, I'll commit the change.

Thanks,

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m1y7kxms6c.wl%jinmei>