>>>>> On Thu, 8 Nov 2001 14:29:04 +0100 (CET),
>>>>> Erik Nordmark <[EMAIL PROTECTED]> said:
>> > Thanks for the quick replies. I have one more question - this time about
>> > the setsockopt portion for TCP in 2292bis.
>>
>> > If an application does a setsockopt IPV6_PKTINFO on a TCP socket, is the
>> > setting of the source address restricted only to an unconnected socket?
>> > What should the behavior be once a connection is established? Since we
>> > cannot change the local IPv6 address during a connection, I am guessing
>> > return an error of some sort.
>>
>> Good point. Actually, I was thinking about the issue, too, and I'm
>> going to clarify this so that issuing IPV6_PKTINFO setsockopt on a TCP
>> socket will fail.
> Being able to use IPV6_PKTOPTIONS for TCP to e.g. set the outbound interface
^^^^^^^^^^^^^^^should be IPV6_PKTINFO
> when using a global address seems consistent with the intent of the option
> and the way it is used with UDP.
Ah, yes...though I don't see practical usage for the TCP case, I don't
see the strong reason to prohibit it either. So a reasonable
clarification would be:
for a TCP socket,
- the address part should be ignored (or must be "::")
- the interface index part will be used as the outgoing interface
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]
--------------------------------------------------------------------
