draft-ietf-ipv6-default-addr-select-08.txt mentions two per-connection
configuration switches for source address selection. One is for home
vs care-of addresses, and the other is for temporary vs public
addresses.
The value of the switches may affect destination address selection,
because it depends on the expected source address corresponding to
each candidate of destination address.
I have a feeling that the current draft is not very clear about the
dependency. For example, Section 8 (Implementation Considerations)
indicates that the destination address selection algorithm can be
implemented inside getaddrinfo(). However, the library function
does not always know the value of per-connection switches in advance.
An application may even not open a socket for the actual connection
when calling getaddrinfo().
This may rather be an implementation issue, so I don't think we need a
major revise of the draft just due to this. But I also think it would
be good to add some note about the dependency in Section 8 before
publishing the 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]
--------------------------------------------------------------------
