The design of IS-IS messages using the TLV structure is that it has better scalability. To add new features, you only need to add a new TLV, and there is no need to change the overall structure of…

Question

Options

• ATRUE
• BFALSE

• A
  76% (13)
• B
  24% (4)

Explanation

A (TRUE) is correct because IS-IS uses a Type-Length-Value (TLV) encoding scheme, where each field in a message is self-describing: the Type identifies what kind of data follows, the Length specifies how many bytes, and the Value holds the actual data. This modular design means new capabilities (like IPv6 support, traffic engineering extensions, or segment routing) can be introduced by defining new TLV types without restructuring existing message formats - older routers simply skip TLVs they don't recognize.

B (FALSE) is a distractor because it incorrectly implies TLVs constrain scalability or require structural changes for new features, which is the opposite of reality - TLV extensibility is precisely why IS-IS has been able to evolve significantly since its original specification without breaking backward compatibility.

Memory tip: Think of TLVs like USB ports - you can plug in new devices (features) without redesigning the computer (the message structure). "Add a port, not a motherboard."

No community discussion yet for this question.