[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [RRG] Six/One: A (Different) Solution for Routing and Addressing in IPv6



Tony,

On 2007-07-14 00:54, Tony Li wrote:

One more general comment. I just re-read the shim6 protocol for WG
Last Call, and was struck by how much detail had to be added to the
basic version from three years ago, to cover all sorts of corner
cases that have been discovered. I am absolutely certain the same
would be true of Six/One. However, shim6 is in need of a clean
solution to the "shim6 proxy" problem, and there is a lot of
commonality in the detailed issues for shim6 and Six/One. I think
there may be an opportunity for using the Six/One approach to fill
the shim6 proxy gap, by means of the very useful 'bunch' concept, and
get the best of both worlds.

Yes, Six/One can be used in proxy mode.

The disadvantage of running Six/One in proxy mode compared to normal
host-based operation of Six/One is that, in proxy mode, a host (be it at
Six/One level or at application level) loses the ability to choose a
particular provider for its packets.


Many folks would consider that a benefit. Hosts within an enterprise need to be managed in a scalable manner, which effectively necessitates the proxy approach. This is the same driver that makes proxy mode for shim6 a pragmatic necessity. Along with that proxy mode, it would seem that this would relieve the burden on the host of learning and retaining all of the addresses in its bunch. This would actually simplify deployment.

The alternative approach is that the necessary policy and preference
table is automatically distributed to all hosts in the site from
a central point; that would of course require overhead in every host
(but RFC 3484 already assumes such overhead).

There's at least one proposed mechanism for this:
draft-fujisaki-dhc-addr-select-opt-04

   This document describes a new DHCPv6 option for distributing default
   address selection policy information defined in RFC3484 to a client.
   With this option, site administrators can distribute address
   selection policy to control the node's address selection behavior.

       Brian

--
to unsubscribe send a message to rrg-request@psg.com with the
word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/rrg/> & ftp://psg.com/pub/lists/rrg