[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
IPv6 routing /48s
- Subject: IPv6 routing /48s
- From: Mark_Andrews at isc.org (Mark Andrews)
- Date: Wed, 26 Nov 2008 12:00:49 +1100
- In-reply-to: Your message of "Wed, 26 Nov 2008 11:55:02 +1100."
Mark Andrews writes:
>
> In message <20081126002425.GO78345 at burnout.tpb.net>, Niels Bakker writes:
> > * alh-ietf at tndh.net (Tony Hain) [Wed 26 Nov 2008, 01:03 CET]:
> > > In any case, content providers can avoid the confusion if they simply put
> u
> > p
> > > a local 6to4 router alongside their 2001:: prefix, and populate DNS with
> > > both. Longest match will cause 2001:: connected systems to chose that dst
> ,
> > > while 6to4 connected systems will chose 2002:: as the dst. There is no ne
> ed
> >
> > Huh? Longest match done by web browsers and other applications? Since
> > when?
>
> FreeBSD 6 has is as part of the standard getaddrinfo() implementation.
>
> % grep -r in6_addrpolicy /usr/src/lib/libc
> /usr/src/lib/libc/net/getaddrinfo.c: struct in6_addrpolicy pc_policy;
> /usr/src/lib/libc/net/getaddrinfo.c: struct in6_addrpolicy *pol, *ep;
> /usr/src/lib/libc/net/getaddrinfo.c: ep = (struct in6_addrpolicy *)(buf +
> l);
> /usr/src/lib/libc/net/getaddrinfo.c: for (pol = (struct in6_addrpolicy *)b
> uf; pol + 1 <= ep; pol++) {
> /usr/src/lib/libc/net/getaddrinfo.c: struct in6_addrpolicy *pol;
> /usr/src/lib/libc/net/name6.c: struct in6_addrpolicy pc_policy;
> /usr/src/lib/libc/net/name6.c: struct in6_addrpolicy *pol, *ep;
> /usr/src/lib/libc/net/name6.c: ep = (struct in6_addrpolicy *)(buf + l);
> /usr/src/lib/libc/net/name6.c: for (pol = (struct in6_addrpolicy *)buf; pol
> + 1 <= ep; pol++) {
> /usr/src/lib/libc/net/name6.c: struct in6_addrpolicy *pol;
> %
And it was added on 30-Oct-03 according to CVS.
Mark
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews at isc.org