HAO SHOULD be implemented. MUST is a stretch and I always thought so since draft 1. The security argument is irrelevant to being a MUST or SHOULD if I deployed MIPv6 I would not use RR or any IPsec there are many ways to secure the mobile nodes and CNs and I agree with Vijays point on this just not the MUST.
That being said anyone who would not want to implement mobile HAO is not in tune with the market at all. But thats not the IETFs job to keep them in tune. /jim > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, July 17, 2002 8:41 PM > To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; > [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: RE: [mobile-ip] Re: HAO and BE processing will be mandated > > > Hi Hesham, > > > > > => Exactly, IMHO the support for HAO is tied to > > > > RO support which is a SHOULD anyway, so the HAO > > > > should follow that. > > > > > > Logically, you are inconsistant. > > > > > > As an example, RO is a should, protecting RO is a MUST. > > > > => Huh? > > > > Protecting it is a must for those who support it! > > But supporting it is a should. > > We're dangerously on the edge of a rathole. > > Debates on support / implement / use of various functions is something > to often causes pointless discussions. > > The question more is, what do general implementations need to > implement. > In my opinion, general often equals robust. SHOULD does not mean > optional, it means you do it unless you have good reason not to do it. > I think the burden of proof, then, would be the endpoint > which does not > implement a certain feature. > > I think that since HAO is used for security reasons, it may > have a strong > need to be a must than other functionality. Just my opinion. > > John > > -------------------------------------------------------------------- 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] --------------------------------------------------------------------
