3 Apr 2005 07:46
Re: I-D ACTION:draft-ietf-isis-wg-multi-topology-09.txt
Naiming Shen <naiming <at> cisco.com>
2005-04-03 05:46:09 GMT
2005-04-03 05:46:09 GMT
Dave & Chris, Can you issue a LC on the draft? Just want to add here the reasons of the change in the latest version I mentioned below: on a LAN, if an interface is configured of running ISIS level-1-2, there is a possibility that the MT set in L1 IIH is different from the MT set in L2 IIH, thus it's possible to have two routers on the LAN form different MT set of adjacency between the L1 and L2. For example, R1 advertises MT a and MT b in both L1 and L2 IIHs, but R2 advertises MT a in L1 IIHs, MT a and MT b in L2 IIHs. It forms a L1/L2 boundary for MT b, but not for MT a. From spec point of view, this is nothing wrong. Since each MT carries it's own ATT bit and each MT calculates it's own routes, there is no need to make the L1/L2 alignment for all the MTs. Thus we removed the sentence "boundaries between levels will be the same for all MTs." in the latest version of the draft. Thanks to Les who raised this issue. Although I don't see any reason to make the boundaries differently for the MTs, as far as I know of, none of the current implementations allows users configuring MT set differently for the two levels. But it's an implementation and configuration choice. thanks. - Naiming(Continue reading)
RSS Feed