> >> 3)The adjacency formation logic discussed in Section 2 isn’t directly >> relevant >> to calculating a flooding topology. There are existing implementations which >> use the techniques you define as a means of reducing redundant flooding >> associated with adjacency bringup when there are parallel links between two >> nodes. Note this can be (and is) done without requiring protocol >> extensions/specification i.e., a node can do this today without introducing >> any interoperability issues. So while this is definitely a good idea, it >> isn’t >> directly related to the work on flooding topologies and I think is better >> removed from the draft. > > Okay -- it seems like this technique is not documented anyplace, and could be > used for all adjacencies.
I’m going to risk disagreeing with Les again and suggest that this should be documented. It need not be in this draft, but it is useful to have in an RFC somewhere. Tony _______________________________________________ Lsr mailing list [email protected] https://www.ietf.org/mailman/listinfo/lsr
