Hello,
This is all a matter of being consistent with the Advanced IPv6 API, and
with the established practice in POSIX world. Pretty much every
setsockopt uses int, unless it has very peculiar reason not to do so.
Using something else will only confuse people, and add a (minor) extra
imple
On Friday 20 October 2006 14:48, you wrote:
> Hello again,
Hi,
> For consistency with the current getaddrinfo and
> setsockopt usage, I think the preference flags ought
> to be an "int" rather than an "uin32_t",
What should we be consistent with? I don't understand
how that would be more
Hi Vlad,
On Wednesday 25 October 2006 18:22, Vlad Yasevich
wrote:
> > So, yes, there is a reason to prefer a configured
> > address over a stateless autoconf one. Same
> > argument applies with DHCPv6 configured addresses.
>
> [...]
>
> Also, this preference really depends on the usage
> case
A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the IP Version 6 Working Group Working Group of
the IETF.
Title : Neighbor Discovery for IP version 6 (IPv6)
Author(s) : T. Narten, et al.
Filename
Vlad Yasevich writes:
> Also, this preference really depends on the usage cases. I can see
> scenarios, where I would rather use autoconfigured address over the DHCP
> or manually assigned one.
Can you describe these?
> The concern I have is someone else may find the above preference backwards
>
Durand, Alain wrote:
>
> Yes, they do, especially when different types of addreses
> are configured on the same Interface/prefix.
> For example, you can have a host with mannually configured
> address 2001:db8:1:1::1 and a stateless autoconf address
> within the same prefix: 2001:db8:1:1::
> -Original Message-
> From: Vlad Yasevich [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 25, 2006 10:07 AM
> To: James Carlson
> Cc: ipv6@ietf.org
> Subject: Re: address selection and DHCPv6
> Why do you want to distinguish between DHCP, manual, and
> autoconfigured addresses?
Vlad Yasevich writes:
> Why do you want to distinguish between DHCP, manual, and autoconfigured
> addresses?
In some deployments, DHCP-derived and manually configured addresses
may have attributes that statelessly autoconfigured addresses do not,
such as useful DNS entries. Stateless autoconfigur
James Carlson wrote:
> I've done quite a bit of searching over the archives and over various
> web resources, but I haven't seen this issue addressed directly.
> Apologies if I've just missed it.
>
> RFC 3484 ("Default Address Selection for Internet Protocol version 6
> (IPv6)") section 5 gives a
