> ?? with RFC2292 IPv6 raw socket, this is not possible.
> (if you pass IPv6 header to the userland, that is not RFC2292
> conformant)
... promts me to make a query concerning dual IPv4/IPv6 stacks: has
anyone given any thoughts about mapping IPv4 into RFC2292 (+bis)?
One should be able to write new applications using this API alone
(also for IPv4 connections), without any concern about IPv4 or IPv6
(where it is not explicitly required)?
For example, some UDP based services (IKE for example), need to know
the actual destination address that was used in the incoming UDP
packet. In IPv4, the only way to get this was to enable raw mode and
dig it out from the packet. I guess for this special need, the packet
information of RFC2292bis should work for both IPv4 and IPv6?
..which gets me back to original query: wouldn't the source address
packet information contain the care-address in the described scenario?
--
Markku Savela ([EMAIL PROTECTED]), Technical Research Centre of Finland
Multimedia Systems, P.O.Box 1203,FIN-02044 VTT,http://www.vtt.fi/tte/staff/msa/
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
