---------------------
PatchSet 6405 
Date: 2007/12/19 02:47:39
Author: amosjeffries
Branch: squid3-ipv6
Tag: (none) 
Log:
Update NOTES-IPv6

Members: 
	NOTES-IPv6:1.1.2.81->1.1.2.82 

Index: squid3/NOTES-IPv6
===================================================================
RCS file: /cvsroot/squid-sf//squid3/Attic/NOTES-IPv6,v
retrieving revision 1.1.2.81
retrieving revision 1.1.2.82
diff -u -r1.1.2.81 -r1.1.2.82
--- squid3/NOTES-IPv6	18 Dec 2007 22:40:49 -0000	1.1.2.81
+++ squid3/NOTES-IPv6	19 Dec 2007 02:47:39 -0000	1.1.2.82
@@ -1,25 +1,12 @@
-$Id: NOTES-IPv6,v 1.1.2.81 2007/12/18 22:40:49 amosjeffries Exp $
+$Id: NOTES-IPv6,v 1.1.2.82 2007/12/19 02:47:39 amosjeffries Exp $
 
 NP: Any problems with this version of squid please contact
 	squid3@treenet.co.nz for assistance.
 
-NP: Cache transition from older squid to IPv6 has not been tested.
-	Any volunteers welcome. For the rest cache_dir's should be
-	built from an empty state in the usual manner.
-
 
 CURRENTLY KNOWN ISSUES:
 
 
-PROBLEM: Sockets created with IPv6 family gives "92 Protocol not supported" errors
-	for getsockopt in clientNatLookup via netfilter.
-	This occurs regardless of the actual source and destination IP types.
-	ie IPv4-client to IPv4-server REDIRECT'd to squid on [::]:81
-NP: iptables <= 1.3.8 tested bad.
-SOLUTION: iptables/netfilter crew working on IPv6 support. Try again in a few months.
-WORKAROUND: squid will explicitly force an IPv4 listening address for transparent ports.
-
-
 PROBLEM: Another intermittent failure:
 NP: This one appears to be static and only occuring during destruction of IPA.
 	have reduced the assert to a debugs and printf(stderr) WARNING.
@@ -27,7 +14,7 @@
 NP2: found a few spots doing memset where they should not. Probably more coming.
 NP3: Sometime during July these have stopped for me.
 NP4: spoke too soon, as soon as I needed to set debug_options ALL,9 back they come :-(
-NP5: OK, killed the IPA type tracker which was supposed to keep track fof content type
+NP5: OK, killed the IPA type tracker which was supposed to keep track of content type
 	it was not strictly necessary and was usually causing these failures.
 	IPAddress is now much more friendly after garbage and peoples over/underflow writes.
 	These will now occur as invalid addresses instead of segfault.
@@ -68,6 +55,7 @@
 
 4.6	Write a Neighbour-Discovery auto-configuration component.
 	- DHCPv6?
+	- SRV auto-discovery?
 	- broad/multi-cast ICP?
 	- link/site-local broadcast (custom protocol)?