>>>>> On Sun, 1 Jun 2003 10:00:14 -0400 (EDT)
>>>>> [EMAIL PROTECTED](Robert Watson) said:
> | | | | The FreeBSD KAME |
> | | | | IPv6 code is now |
> | | | | substantially dated |
> | | | | with respect to the |
> | KAME | | | KAME vendor source. |
> | Synchronization | -- | -- | The FreeBSD Project |
> | | | | needs to take |
> | | | | initiative in |
> | | | | driving the merge |
> | | | | of new bug fixes, |
> | | | | features, et al. |
I discussed this issued within KAME.
Here's our rough plan about this synchronization.
If you have some opinion, please let me know.
When I've finished each merge, I'll ask you how to proceed.
- sync per feature; don't do a complete sync with the KAME-snap:
Since some of the KAME-specific features are still under
standardization or immature, it's dangerous to sync without
much consideration.
- items to be merged
Here's the candidate items to be merged.
5.2-RELEASE
- IPv6 Advanced API (RFC3542 = written as
'RFC2292bis' in source code)
Binary compatibility to RFC2292 is
provided.
- Source Address Selection (RFC3484)
It involves too many unessential changes.
(e.g. NDP data structure change, use struct
sockaddr_in6 instead of struct in6_addr).
So if time does not permit, I'll shift it
to the future release.
5.x-RELEASE
- IGMPv3 (RFC3478 and draft-ietf-magma-msf-api-04.txt)
seems almost okay in terms of standardization,
but has less priority.
So if time permits, I'll shift it to
5.2-RELEASE.
- Mobile IPv6 Corresponding Node (draft-ietf-mobileip-ipv6-22.txt)
waiting for becoming an RFC
- items not to be merged
The following items are not merged for the time being, because
of their immaturity, wating for standardization, etc.
MLDv2
mDNS
Scoped routing
VRRPv6
Mobile-IPv6 Home-Agent and Mobile-Node
Router Selection
ISATAP
DNS server discovery
DHCPv6
SCTP
_______________________________________________
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
