Re: [address-policy-wg] Re: Re: 200 customer requirements for IPv6

[Geoff Huston gih@localhost]

At 01:20 AM 19/01/2006, Daniel Roesen wrote:
> On Mon, Jan 16, 2006 at 05:46:22PM +0100, Per Heldal wrote:
> > * The current policy will work just fine combined with a
> > production-quality shim6 implementation, complete with full support for
> > traffic-engineering and load-balancing from all vendors.
>
> Sorry, but please inform yourself about the technical details of shim6
> first. There is no provision for traffic engineering in shim6 as we
> know, use and need it today.
You are referring to various forms of routing table abuse of course.

>  As a completely host-centric thing this
> ain't doable anyway, as a host has no faint clue about how the network
> is interconnected with others.
And yet once you draw further away from the host you run into the issues
that we all know and love with NATS and other forms of packet header
rewriting at a distance. So as a completely network-centric thing the problem
you run into very quickly is how to distinguish assistance from attack.
The network has no clue about intentions and all you achieve is a lowered
attack threshold. Very useful indeed.


>  And the idea of retrofitting such stuff
> into shim6 outright scares me (and many others). Let the network do it's
> job.
Depends on your architectural vision - if the network's job is simple
lossy connectionless packet forwarding along paths identified by working
scaleable routing protocols, then precisely how does TE and other forms
of architecture and routing abuse fit into this "job"? :-)

> > I believe that still is a few years down the road.
>
> No, it's not even on shim6' radar.
Sorry, but please inform yourself about the details of shim6's agenda first.

It is on the radar, and if you wish to contribute then put fingers to the
keyboard and send in a draft as to _how_ it could be done.

> shim6 is not the droid we're looking for. And we don't even need Obi-Wan
> to make us believe that.
Usual response: propose an approach, gather interest, call a BOF, formulate
a plan, adopt a charter and get to work.

Geoff