The engineers who implemented MIPv6 and there are a few and in the MIPv6 working group are same engineers that do ND in most cases today. The issue is not one of expertise. This is MIPv6 work not IPv6 work.
/jim [Honor, Commitment, Integrity] > -----Original Message----- > From: Pekka Savola [mailto:[EMAIL PROTECTED]] > Sent: Monday, November 18, 2002 8:41 PM > To: [EMAIL PROTECTED] > Subject: MIPv6 and ND value changes > > > Hello, > > FWIW, I fully support Thomas Narten on his view that MIPv6 > should not be > making all of these assumptions to e.g. Neighbor Discovery > timer values. > > These should be in a separate document, either: > - by mobileip, reviewed by ipv6 wg > - by ipv6 wg > (- waiting for the ND spec revising is probably not an option) > > Such a document could be quite short, and probably could be > pushed quick > through the IETF process. > > -- > Pekka Savola "Tell me of difficulties surmounted, > Netcore Oy not those you stumble over and fall" > Systems. Networks. Security. -- Robert Jordan: A Crown of Swords > > -------------------------------------------------------------------- > 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] > -------------------------------------------------------------------- > -------------------------------------------------------------------- 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] --------------------------------------------------------------------
