On Mon, Jun 03, 2002 at 02:37:28PM +0900, JINMEI Tatuya / ?$B?@L@C#:H?(B wrote: > > In summary: > > - if we're going to make something mandatory for all IPv6 nodes, it > must be discussed in the ipv6 wg. > - (IMO) we cannot go with the MUST, considering the current situation > and some possible scenarios in the future. We should delay the > decision, or should go with a SHOULD or a MAY. > - it does not make sense just to say "the route optimization is > mandatory." we should be more specific.
My take is that this should be a SHOULD. I actually think that it depends upon the type of device, and how it is expected to be used. So I'd say in general, RO is not generally needed when a router (non mobile router) is the CN, for some really minimal implementation (i.e. IP stack in a fridge, light switch etc) there's no need whatsoever, but for other general nodes - my computers, mobile phone etc, then RO should be implemented. Given that and a differentiation on device basis, I say: for routers => SHOULD for minimal nodes => MAY for other nodes => MUST As to what's being done; as others have pointed out there is already shipping code which doesn't implement RO (as defined in draft-17) thus we already effectivly have a MAY situation. After glancing through draft-17 recently I decided that (for a router) one didn't need to bother with implementing RO initially (if ever). That was based upon the assumption that traffic directed to/from the router itself would generally (or almost always) be from within the organisation owning the router, and as such dog leg forwarding would be uncommon. Obviously ICMPs generated by the router are a possible exception. Hence the view that we could leave implementing RO for CN functionality within a router until some later stage, i.e. ship product without it (as happens now) and then implement the functionality within some later release of software. Now if this was a router that was also acting as a HA, the analysis would be somewhat different. DF -------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to [EMAIL PROTECTED] --------------------------------------------------------------------
