Re: Question about the need for a Router Alert Option (RFC 2711) within a Hop-By-Hop Option Extension Header (RFC 2460) ...

2005-11-02 Thread Elwyn Davies
The router alert option has a rather more drastic effect than simply having a h-b-h extension header. The intention of the h-b-h header (as has been discussed recently in connection with a proposed QoS related option) is that h-b-h options should, by default, not need to be diverted to the

RE: Question about the need for a Router Alert Option (RFC 2711) within a Hop-By-Hop Option Extension Header (RFC 2460) ...

2005-11-02 Thread John Spence
Excellent. Thanks for the insight. One comment - you did mention an empty h-b-h header. I would not expect to see an empty one - right - only if I have options would I attach the extension header to carry them. Spence -Original Message- From: Elwyn Davies [mailto:[EMAIL PROTECTED]

Re: Question about the need for a Router Alert Option (RFC 2711)within a Hop-By-Hop Option Extension Header (RFC 2460) ...

2005-11-02 Thread Fred Baker
I would reword that slightly. Melinda Shoer has been known to suggest that RSVP might be used as a firewall traversal mechanism, implying that a NAT/Firewall might be interested in the protocol even though it is middleware more than router. It does mean, however, if you receive this

Question about the need for a Router Alert Option (RFC 2711) within a Hop-By-Hop Option Extension Header (RFC 2460) ...

2005-11-01 Thread John Spence
Hello; If the H-B-H extension header means "all intermediate nodes must look in here for options to process", why is the "Router Alert" option needed? As I read the text of the two RFCs, the Router Alert Option is redundant - just including a H-B-H header means "intermediate nodes must

Re: Question about the need for a Router Alert Option (RFC 2711) within a Hop-By-Hop Option Extension Header (RFC 2460) ...

2005-11-01 Thread Fred Baker
one of them sounds like it is redundant. I think the Router Alert predated the HBH header...On Nov 1, 2005, at 6:04 PM, John Spence wrote: Hello;   If the H-B-H extension header means "all intermediate nodes must look in here for options to process", why is the "Router Alert" option needed?  As I

Re: Question about the need for a Router Alert Option (RFC 2711) within a Hop-By-Hop Option Extension Header (RFC 2460) ...

2005-11-01 Thread vijay gill
Fred Baker wrote: one of them sounds like it is redundant. I think the Router Alert predated the HBH header... On Nov 1, 2005, at 6:04 PM, John Spence wrote: Hello; If the H-B-H extension header means all intermediate nodes must look in here for options to process, why is the Router Alert

RE: Question about the need for a Router Alert Option (RFC 2711) within a Hop-By-Hop Option Extension Header (RFC 2460) ...

2005-11-01 Thread John Spence
Sorry - that fired too fast. RFC 2711 also references RFC 2460, so it was built for the H-B-H extension header. Also, if you look at RFC 3810 (MLDv2), it also references the Router Alert Option and says: All MLDv2 messages described in this document MUST be sent with a link-local IPv6 Source

Re: Question about the need for a Router Alert Option (RFC 2711) within a Hop-By-Hop Option Extension Header (RFC 2460) ...

2005-11-01 Thread Fred Baker
more like something you turn on - by configuring the protocol that uses it. On Nov 1, 2005, at 7:01 PM, vijay gill wrote: Fred Baker wrote: one of them sounds like it is redundant. I think the Router Alert predated the HBH header... On Nov 1, 2005, at 6:04 PM, John Spence wrote: Hello;