sync with reality.
- getipnodeby{name,addr} is now non-issue as RFC2553bis will be dropping it
- if_detach is mostly done
- add some items
This commit is contained in:
itojun
parent
aba424872a
commit
7604e315fb
|
|
@ -1,5 +1,5 @@
|
|||
KAME/NetBSD integration TODOs
|
||||
$NetBSD: TODO,v 1.10 2000/02/03 19:29:20 itojun Exp $
|
||||
$NetBSD: TODO,v 1.11 2000/02/05 18:05:33 itojun Exp $
|
||||
Jun-ichiro itojun Hagino <itojun@itojun.org>
|
||||
|
||||
|
||||
|
|
@ -37,7 +37,7 @@ can easily exceed MHLEN. Remember, IPv6 header itself already occupies 40
|
|||
bytes)
|
||||
|
||||
KAME team is doing experiments with m_pulldown(). will migrate to m_pulldown()
|
||||
after stabilization.
|
||||
after stabilization. working nicely but need more tests and code reviews.
|
||||
|
||||
* ipsec socket pointer
|
||||
|
||||
|
|
@ -58,9 +58,8 @@ is local to IPv6 code so it should be M_PROTO0 or something like that.
|
|||
Others (IPsec items) are used across IPv4 and IPv6 so they cannot be in
|
||||
M_PROTO0 kind of thing.
|
||||
|
||||
When we switch to m->m_pkthdr.aux, we don't need those flags in m->m_flags.
|
||||
|
||||
* if_detach improvement
|
||||
When we switch to full m->m_pkthdr.aux support, we don't need IPsec related
|
||||
flags in m->m_flags.
|
||||
|
||||
* use of xx_control() from kernel
|
||||
|
||||
|
|
@ -70,20 +69,24 @@ cause various problems, like M_WAIT/NOWAIT issue, spl issue and others.
|
|||
we need to clean it up. The right thing to happen is to split those
|
||||
necessary functions into (1) called-from-userland function, (2) called-from-
|
||||
interrupt function, and (3) common backend which shares as much code as
|
||||
possible.
|
||||
possible. in6_prefix.c is the offending portion.
|
||||
|
||||
* more LP64 friendliness
|
||||
* more LP64 friendliness checking
|
||||
|
||||
* scoped address printing
|
||||
|
||||
KAME implements extended format for link-local address printing, like
|
||||
"fe80::1@lo0". After long debate, IETF ipngwg will pick "lo0%fe80::1" as
|
||||
standard one (picked "%" for avoiding conflict with "user@host" notation).
|
||||
We'll need to update the support before the release.
|
||||
|
||||
|
||||
USERLAND
|
||||
========
|
||||
* various routing daemons
|
||||
* pim6dd/pim6sd licensing
|
||||
|
||||
KAME codebase includes several routing daemons, like route6d or bgpd (which
|
||||
does RIPng and BGP4+, respectively). Should we put these into
|
||||
/usr/src/usr.sbin, or should we treat those as third-party code (pkgsrc)?
|
||||
|
||||
pim6dd/pim6sd license issue should be clarified.
|
||||
pim6dd/pim6sd license issue should be clarified, just like we need
|
||||
clarification for mroute6d.
|
||||
|
||||
* IPv6-support in resolvers and libraries
|
||||
|
||||
|
|
@ -93,9 +96,6 @@ future bind8 code, so we may have to merge future bind8 carefully.
|
|||
|
||||
At this moment IPv6 support in lib/libc/net/* is implemented in very
|
||||
conservative way so that it will not break existing codebase.
|
||||
To be RFC2553 compilient, we need to supply getipnodeby{name,addr}.
|
||||
However, it needs a total rewrite of gethostby{name,addr}.
|
||||
It will make future upgrade to bind8x really harder.
|
||||
|
||||
* -DINET6, -DIPSEC
|
||||
|
||||
|
|
@ -109,15 +109,6 @@ and there's no global option for enabling/disabling userland IPv6/IPsec
|
|||
support. Since we ship single binary tree we want to ship them enabled
|
||||
by default.
|
||||
|
||||
* if index
|
||||
|
||||
Should we hide if index (s6_addr[2-3] in in6_addr) from the user, on "ifconfig"
|
||||
or "netstat -in"? Those numbers are just for kernel internal
|
||||
and should never be used from standard userland applications.
|
||||
(see 1.3 in sys/netinet6/IMPLEMENTATION)
|
||||
|
||||
We start hiding it by using getnameinfo(NI_WITHSCOPEID).
|
||||
|
||||
* more IPv6 support
|
||||
|
||||
X11, NFS, RPC, whatever.
|
||||
|
|
|
|||
Loading…
Reference in New Issue