On Tue, 27 Apr 2004 09:13:55 -0700,
Alain Durand [EMAIL PROTECTED] said:
The facts are:
1. there is code that sets the MO bits. (router implementations)
2. there are at least two implementations that read and
act on the O
bit. These two implementations both invoke stateless DHCPv6 as
The facts are:
1. there is code that sets the MO bits. (router implementations)
2. there are at least two implementations that read and
act on the O
bit. These two implementations both invoke stateless DHCPv6 as
the action.
= So based on
On Tue, 27 Apr 2004 04:50:00 -0400,
Soliman Hesham [EMAIL PROTECTED] said:
1. there is code that sets the MO bits. (router implementations)
2. there are at least two implementations that read and
act on the O
bit. These two implementations both invoke stateless DHCPv6 as
the action.
=
On Tue, 27 Apr 2004, JINMEI Tatuya / [ISO-2022-JP] [EMAIL PROTECTED]@C#:H wrote:
In any event, I'd first like to clarify the general point before going
to each detail to avoid further confusion. The question is:
We do not have an implementation on some part of RFC2462. Can we
still
Hi Ralph,
I also agree that we should be more precise in our acceptance of
implemented and interoperable. I fear that the current practice can be
(and has been) applied selectively to allow advancement of some standards
while holding back others.
I'm not sure that your point above is
On Apr 27, 2004, at 1:50 AM, Soliman Hesham wrote:
The facts are:
1. there is code that sets the MO bits. (router implementations)
2. there are at least two implementations that read and
act on the O
bit. These two implementations both invoke stateless DHCPv6 as
the action.
= So
John - I should have been more careful in my use of we, which I had
intended to mean the IETF as a whole. I agree that the issue of
implemented and interoperable is not within the IPv6 WG's scope. It
wouldn't hurt for the WG to be aware of the potential issues and come to an
explciit decision
Subject: Re: whether we need the M flag ??
On Apr 27, 2004, at 1:50 AM, Soliman Hesham wrote:
The facts are:
1. there is code that sets the MO bits. (router
implementations)
2. there are at least two implementations that read and
act on the O
bit
