The MPLS WG Archive

["Metz, E.T." <E.T.Metz@kpn.com>]

This is indeed a bit confusing. 

As far as I understand (Kireeti: correct me if I'm wrong here) the
parameters are actually *configured* on the PE. However, the CE should know
about this. In particular the CE configuration should reflect the same logic
that is applied by the PE in mapping CE-to-CE circuits to eachother. This is
the algorithm described in Section 4.3.1. When CE and PE configuration are
not aligned on this point, the CE may expect to connect to one site on a
particular circuit, while the PE actually connects it to another one.

I think the text should say that the parameters are configured on the PE,
and that the CE should know about this / reflect this in it's configuration.
Currently, it is described in the exact opposite way. Also it makes less
sense to configure it on the CE since there is no interaction between PE and
CE to exchange this information.

cheers,
	Eduard


Metz, E.T. writes:

 > it is the pe that is configured with the parameters you mention, not
 > the ce.

that is not what the i-d says:

4.2.1. CE Configuration

   Each CE that belongs to a VPN is given a "CE ID".  CE IDs must be
   unique in the context of a VPN.  We assume that the CE ID for CE-k is
   k.  Each CE is also configured with a maximum number of CEs that it
   can connect to; this is the CE's "range".

   Each CE is configured to communicate with its corresponding PE with
   the set of DLCIs given above; for example, CE0 is configured with
   DLCIs 100 through 109.  OSPF is configured to run over each DLCI. 

-- juha