>>>>> On Wed, 24 Jul 2002 10:37:28 +0900 (JST),
>>>>> Keiichi SHIMA <[EMAIL PROTECTED]> said:
>> thanks Phil. this approach sounds good.
> I agree, too.
I basically agree, too. A few points:
>> When MIP sends the spec up to the IESG for approval, we'll let the NG
>> working
>> group know the summary of the requirements that the MIP working group has
>> recommended.
The ipv6 wg members will check the next draft and will make comments
on it when it is out , not only at the point of the IESG approval.
The ipv6 wg members will also make comments at the mip wg last call
(since the last call will be announced to the members as well), and at
the IETF last call, especially if they have objections to the draft.
> Thoughout the discussion, it seems to me that the IPv6 WG will not
> accept the mip6 draft if the HAO/BE requirements are MUST. Even if we
> leave them with MUST (of course we can, the decision can be done in
> the mip WG inside), I think that the IESG never pass it. This creates
> another delay for the standard process of the mip6.
I'm not sure if this is really the case (because we cannot tell all
about the future), but I'm 99% sure that many ipv6 wg members will
make objections to the MUST. And, the objections will surely
introduce additional delay to standardize mip6. (I'm not talking
about my own position about the MUST vs SHOULD, but talking about a
story that will be very likely to happen, by observing the discussions
so far.)
So, I hope the next draft will consider the various tradeoffs among
ideal solutions to MNs, effects to CNs (both existing and future
ones), and the standardization/deployment schedule.
Again, I agree the ball is now in the mip wg and we should wait for
the next draft.
JINMEI, Tatuya
Communication Platform Lab.
Corporate R&D Center, Toshiba Corp.
[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]
--------------------------------------------------------------------
