Re: [mpls] Doubts in RFC 5036

["Anup Kumar Vasudevan (anuvasud)" <anuvasud at cisco.com>]

Hi

 

My attempt at explaining -

 

1. We use the LDP keep alive message to setup the session. When we get the session init message we reply with a keep alive message. The keep alive timer is only used to maintain the TCP session. We do not need to use the TCP keep alive messages for LDP. Using TCP keep alives will probably result in unnecessary n/w traffic. The LSR's can recevie any LDP message in order to keep the session alive (keep alive timer from expiring). If LSR's dont have any info to exchange a keep alive message is used.

 

2. When LSR's exchange hello's they will be able to setup adjacencies. With the Adjacency configured the session setup can be done. In case the session params do not match the session setup wiill fail but the adjacency will remain until timer expiry. I think this is for trouble shooting purposes. Atleast thats what i have used it for. o/w we cannot distinguish between a failed adjaceny setup and a failed session setup.

 

Thanks and Regards

Anup Vasudevan

---

From: mpls-bounces at ietf.org [mailto:mpls-bounces at ietf.org] On Behalf Of priyanka gupta
Sent: Monday, April 14, 2008 7:51 PM
To: mpls at ietf.org
Subject: [mpls] Doubts in RFC 5036

Hi all,

 

I was analysising the LDP RFC and wasnot able to get the reason for few events declared.

 

1)Need of keep aive timer over TCP session.Cannt the TCP keep alive is enough to maintain teh integrity of session?

 

2) In RFC it is written deletion of adjacency will delete the session.Refer section 2.5.5.but vise versa is not clear.

    Will session deletion also deletes the adjacency?As per my understanding whats the need of maintaining adjacency when session establishment parameter are failed in negotiation.

 

 

regards,

Priyanka

---

Unlimited freedom, unlimited storage. Get 
it now
_______________________________________________
mpls mailing list
mpls at ietf.org
https://www.ietf.org/mailman/listinfo/mpls