During the LDP session establishment process, the active party will first send Initialization information to negotiate parameters. If the passive party does not accept the negotiation parameters…

Question

Options

• AInitialization Message
• BHello Message
• CKeepalive Message
• DError Notification Message

• A
  5% (2)
• B
  12% (5)
• C
  2% (1)
• D
  80% (33)

Explanation

In LDP (Label Distribution Protocol) session establishment, after the active party sends an Initialization message to propose session parameters (keepalive timer, max PDU size, etc.), the passive party must either accept or reject those parameters. If it cannot accept them, RFC 5036 specifies that it sends an Error Notification Message indicating the specific problem (e.g., "Session Parameters Not Acceptable") and then closes the TCP connection - making D correct.

Why the distractors are wrong:

• A (Initialization Message): This is what the active party sends to propose parameters, not what the passive party sends to reject them.
• B (Hello Message): Hello messages belong to the Discovery phase (sent via UDP before any TCP session exists) - they play no role in parameter rejection.
• C (Keepalive Message): Keepalives are sent only after both sides successfully agree on parameters, to maintain an already-established session.

Memory tip: Think of the flow as a job offer negotiation - Hello is the introduction, Initialization is the offer, Keepalive is the signed contract check-in, and an Error Notification is the rejection letter you send when the terms are unacceptable.

No community discussion yet for this question.