The MPLS WG Archive[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] ce range in l2 mpls vpns
this may have been discussed already, but why does draft-kompella-mpls-l2vpn-01.txt require that the ce is configured with the ce id, the ce's range and all labels in that range? why can't the ce dynamically add a new neighbor when it learns about a new label via lmi, ilmi, or a corresponding mpls protocol? i'm asking this because the proposed practice would be a step backwards from how people have been running atm or fr vpns for years using cisco cpe routers, where the only thing i need to configure is the (sub)interface and an ip address. here is a frame relay example: interface Serial <number> ip address <address> <mask> encapsulation frame-relay IETF ip ospf network point-to-multipoint and here is an atm example: vc-class atm broadcast broadcast interface ATM <number> atm pvc 2 0 16 ilmi atm ilmi-pvc-discovery subinterface interface ATM <number>/<number> multipoint ip address address mask ip ospf network point-to-multipoint class-int broadcast dlcis or atm vcs of the other sites are learned dynamically via lmi or ilmi. as you see in above, the cpe doesn't even need to be configured with its own ce id. -- juha |
|