[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Distributing site-wide RFC 3484 policy
Le 07-07-23 à 13:56, Brian E Carpenter a écrit :
As I said at the mike today, I really think we can't avoid
such a mechanism.
I agree with Brian. There must be a way for enterprises to push a
RFC3484 policy to its nodes.
I went into this discussion with a large enterprise customer who
wanted to carefully control how v6 will be deployed in an incremental
way. some of the enterprise sites would be v6 ready, others will be
v6 enabled but not so ready, etc... therefore, pushing different
RFC3484 policies depending on the sites is very useful in this
context. Policy #1 could be the default policy(prefer v6), policy #2
would be prefer ipv4. It is also pretty useful when nodes are mobile
and move from sites to sites and then get the site network rfc3484
policy while attaching to the network.
It will also help applications developers since we are seeing
applications developers forcing v4 to prefer v6, disabling v6, etc...
if rfc3484 policy can be pushed to nodes, then these changes to
applications would be less useful, since the enterprise network
manager would be able to tell the nodes, (and then the applications)
what are the best version of IP to use on the attached network.
There *will* be sites running multiple prefixes
(those too small to insist on PI space, but big enough to
need multiple ISPs).
IPv6 book: Migrating to IPv6, Wiley, 2006, http://www.ipv6book.ca