On Aug 30, 2015, at 11:54 PM, Mingui Zhang <zhangmingui@xxxxxxxxxx> wrote: > Hi Russ, > > >> >> (3) In Section 11, we learn that the VLAN membership of all the RBridge ports >> in an LAALP MUST be the same. Any inconsistencies in VLAN membership >> may result in packet loss or non-shortest paths. >> Is there anything that can be added to the Security Considerations that can >> help avoid these inconsistencies? >> > > [MZ] The LAALP is REQUIED to keep the consistence. That is to say, if the consistence cannot be maintained, it is not qualified as a LAALP. What TRILL switches can do is that ports connected to inconsistent LAALPs MUST be disabled. This requirement can be added. > I just replied to Russ’s message before I read your response. The draft language is just as Russ said. It is important that the VLAN membership of all the RBridge ports in an LAALP MUST be the same. Any inconsistencies in VLAN membership may result in packet loss or non-shortest paths. Following this, there is a paragraph fully describing an inconsistent configuration. If it is not possible for inconsistencies to occur, then why are you mentioning them? Why give an explicit example of an inconsistent VLAN configuration? You say "if the consistence cannot be maintained, it is not qualified as a LAALP”. But the example shows a configuration case where inconsistency happens. Does that mean it is not an LAALP? Does the spec for LAALP ensure consistency (and if so, why mention inconsistencies and provide examples)? Does anything in TRILL detect the absence of consistency? —Sandy
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail