Hi Thomas, On Sep 27, 2012, at 14:31, Thomas Narten <[email protected]> wrote:
> One of the things I've been meaning to clarify here is what is the > defintion of a CUG? > > In offlist discussions I've had, I've come to the conclusion that a > CUG is the same thing as a VN. That is, it's a set of machine that are > administratively placed into a group and are allowed to communicate > with each other, but not with others outside of that CUG. > > Correct? Almost. Entities inside a CUG may communicate to entities outside through a policy specified by the appropriate administrator. the default policy is as you say: no communication. > And, RFC 4364 says: Essentially, RFC 4364 defined an L3 CUG, and the EVPN draft an L2 CUG. Kireeti >> Suppose it is desired to create a fully meshed closed user group, >> i.e., a set of sites where each can send traffic directly to the >> other, but traffic cannot be sent to or received from other sites. >> Then each site is associated with a VRF, a single Route Target >> attribute is chosen, that Route Target is assigned to each VRF as >> both the Import Target and the Export Target, and that Route Target >> is not assigned to any other VRFs as either the Import Target or the >> Export Target. > > Is there another (different?) definition of CUG? > > Thomas > > _______________________________________________ > nvo3 mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/nvo3 _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
