[OCCAID] Proposal for EINTAP

[Neil]

> Of course OCCAID won't advertise your prefix if it is smaller than /32.
> This is common knowledge. If you were to sit back and think of what SJC
> was offering, you would understand. OCCAID would accept your /48-/64 
> address space from whomever/whatever and it would be present in the
> OCCAID iBGP. You would receive full bgp routes from OCCAID which would
> allow you to route engineer your traffic potentially out via OCCAID. 
> Since uRPF is not yet an issue with IPv6 you could send bits from say,
> your HE.net /48 to OCCAID and out via their peers/transits. Of course
> the return path for anyone not a downstream of AS30071 would be HE.net's 
> /32 announcement.


to date, occaidv6 does not run with strict uRPF on ipv6 networking. and we
do not plan to implement strict uRPF since it breaks 95% of all downstream
networks.

the only router that has uRPF enabled is cr1.sjc1 in san jose where we have
global crossing transit dropping in. and that is LOOSE uRPF, not strict.
so it doesn't drop packets unless sourced from a route that doesn't exist
at all in DFZ, or the route is blackholed.

plz to note the LRPF_INET6 flag, thank you.

occaid at cr1.sjc1.us> ifconfig ge-0/0/0.7
ge-0/0/0.7: flags=18843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LRPF_INET6> mtu 1500
        inet6 fe80::202:b3ff:feca:90bd%ge-0/0/0.7 prefixlen 64 scopeid 0x1 
        inet6 3ffe:401d:ff:10c5::3549 prefixlen 64
        ether 00:02:b3:ca:90:bd
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
        vlan: 7 parent interface: ge-0/0/0
 
occaid at cr1.sjc1.us>

but then again, since occaid has layer 10 problems, i am not credible.
oh well, NANOG friends used to say "its just IRC" ;-) or was it that 
TCAM is for layer 2 mac addresses? last i recall there was difference
between binary CAM and ternary CAM but anyways.. good night folks

	-ndf