Leslie Daigle wrote:
>
> I posted this a few days ago -- before, I think, people had
> a chance to get subscribed. So, let me re-post it for
> further discussion...
And I've been carrying the attached minor comment around for two weeks...
...
>
> 3.2. Addressing Requirements of Enterprises
...
> Some enterprises have addressing requirements caused by the need to set
> up inter-enterprise Virtual Private Networks (VPNs). Also, at some
> point in their existence most enterprises undergo some form of merger or
> acquisition, and discover that they need to merge internal networks. In
> both these circumstances there is a requirement to avoid the need to
> renumber or to suffer from ambiguous addressing resulting from the
> merger of two private address spaces.
I think this misses another related requirement that may become very
significant, in a future consisting of virtual organizations and on-demand
computing environments. It may often be required for a set of enterprises
to create a short-term "closed user group" of hosts that need transparent
(firewall-free) interconnection for a period of time; this is like a dynamic
merger followed some time later by a demerger. This is more demanding on the
addressing (and routing) architecture than relatively static VPNs or one-time
events like mergers.
Brian
_______________________________________________
Saad mailing list
Saad@ietf.org
https://www1.ietf.org/mailman/listinfo/saad
