The MPLS WG Archive[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] [mpls] Question regarding LDP session setup
Hi,
The relation between TCP connection and session is one to one. and in your case there should be only 1 session. So there should be only 1 tcp connect. If there are multiple links between 2 routers and using different transport address we should have some method to process this case. But unfortunately this is not clearly specified by RFC3036.
Maybe the transport address should be same if mutiple links exist. This can avoid much trouble and this can be done by the limitation of configuration.
Or just accept the first hello adjacency for the session if the second hello adjacency has different transport address. Only in case the transport address are same for multiple adjacencies the session will be maintained by these multiple adjacencies.
Cheers,
Yu Yi
-----Original Message-----
From: Kishore Tiruveedhula [mailto:tiruveedhula@avici.com]
Sent: 2006Äê9ÔÂ29ÈÕ 10:04 PM
To: Bob Thomas
Cc: Fantolino Luca; mpls@lists.ietf.org
Subject: RE: [mpls] Question regarding LDP session setup
Hi Bob,
If the transport addresses are same, then active router can attempt single TCP connection, agree with Pranjal.
If the transport addresses differ, then RFC3036 is not clear which one to pick for TCP connection or attempt multiple TCP connections.
And there is one more problem that both routers may become Active or both may become passive if both links advertises the different transport addresses in such way that first adjacency transport address is higher and second transport address is lower.
Thanks,
Kishore
-----Original Message-----
From: Dutta, Pranjal [mailto:pdutta@riverstonenet.com]
Sent: Thursday, September 28, 2006 11:26 PM
To: Bob Thomas; Kishore Tiruveedhula
Cc: Fantolino Luca; mpls@lists.ietf.org
Subject: RE: [mpls] Question regarding LDP session setup
Hi Bob,
It is well understood that the passive router has to close the second or subsequent TCP connection requests for the same LDP session.
But
If the passive router advertises one LDPID (single label space) from it then I don't see any reason for the active one to trigger up multiple TCP connections. The active router has to initiate only one TCP connection for remote LDPID, although multiple hello adjacencies may exist for the same LDPID.
Thanks,
Pranjal
-----Original Message-----
From: Bob Thomas [mailto:rhthomas@cisco.com]
Sent: Friday, 29 September, 2006 4:10 AM
To: Kishore Tiruveedhula
Cc: Fantolino Luca; mpls@lists.ietf.org
Subject: Re: [mpls] Question regarding LDP session setup
Hi Kishore,
> Subject: RE: [mpls] Question regarding LDP session setup
> Date: Thu, 28 Sep 2006 11:49:22 -0400
> Cc: mpls@lists.ietf.org
>
> Luca,
> Yes. I expect single TCP connection.
RFC3036 is silent on this point.
RFC3036 specifies a single session between the 2 routers in this situation but places no limit on the number of connections the active router may attempt to open in order to establish the single session.
This leaves the router playing the passive role with the job of selecting one connection for the session and closing the other(s).
Bob
> Thanks,
> Kishore
>
>
> -----Original Message-----
> From: Fantolino Luca [mailto:luca.fantolino@telecomitalia.it]
> Sent: Thursday, September 28, 2006 10:18 AM
> To: Kishore Tiruveedhula
> Cc: mpls@lists.ietf.org; Tempia Bonda Alberto
> Subject: RE: [mpls] Question regarding LDP session setup
>
>
> Thanks for your reply.
>
> I verified again the content of the LDP messages: both report the same
=
> LDP ID (the loopback address) and same Label Space ID (0).
>
> In this case I understand you expect a single TCP connection be
created.
>
> bye
> Luca
>
> -----Original Message-----
> From: Kishore Tiruveedhula [mailto:tiruveedhula@avici.com]=20
> Sent: mercoled=EC 27 settembre 2006 18:42
> To: Tempia Bonda Alberto; mpls@lists.ietf.org
> Cc: Fantolino Luca
> Subject: RE: [mpls] Question regarding LDP session setup
>
> If the both links uses the same local LDP ID (LSR Id:label space id),
=
> then
> it should create single LDP session (single TCP connection).
>
> I guess your case might be something like below:
>
> If Router A (assuming passive) LDP ID on link1 is Ra:La1, on link2 is
=
> Ra:La2
> and
> Router B (assuming Active) LDP ID on both links is same Rb:Lb.
>
>
> Router A link1 (LDP ID is Ra:La1) <--> Router B link1 (LDP ID is
Rb:Lb)
> Router A link2 (LDP ID is Ra:La2) <--> Router B link2 (LDP ID is
Rb:Lb)
>
>
> In this case, Router B opens two TCP connections and Router B accepts
=
> both
> connections,
> but it may be accepted the TCP connections
> link1 of Router A to link2 of Router B and
> link2 of Router A to link1 of Router B.
>
> In this case, the session initialization fails when it verifies the
> Initialization message with its Hello adjacency ( by using Receiver
LDP
> Identifier in CommonSession Parameter TLV).
>
>
> Thanks,
> Kishore
>
> -----Original Message-----
> From: Tempia Bonda Alberto
[mailto:alberto.tempiabonda@telecomitalia.it]
> Sent: Wednesday, September 27, 2006 11:21 AM
> To: mpls@lists.ietf.org
> Cc: Fantolino Luca
> Subject: [mpls] Question regarding LDP session setup
>
>
> Hello,
>
> I have a question about LDP session establishment between two LSRs
> connected by multiple links.
> A problem has occurred in the network during LDP session set up
between
> two routers linked by two Ethernet LANs. Below I describe the
behavior.
>
> 1. Router A sends a LDP HELLO message on each Ethernet link at the
same
> time; the two messages are identical, including the router ID and the
> source IP address (IP address assigned to an internal interface).
>
> 2. Router B tries to open two TCP connections with router A on port
> 646: it sends two TCP SYN packets (using two different local ports).
>
> 3. Router A accepts both connections (TCP SYN ACK) and router B
> completes the TCP connections set up (TCP ACK): two TCP connections
are
> now available for LDP message exchange.
>
> 4. Router B (active role) sends two copies of the same LDP
> INITIALIZATION message to router A through the two TCP connections.
>
> 5. Router A sends a LDP INITIALIZATION message on the first TCP
> connection and clears the second TCP connection (TCP FIN).
>
> 6. Router A sends a LDP NOTIFICATION message with E-bit set and then
> resets the second TCP connection.
>
> What happens is that two TCP connections are created and Router B
tries
> to open two separate LDP sessions. It tries to open a second LDP
session
> when the first one is not yet established with the result that router
A
> closes both TCP connections and no LDP session is set up.
>
> It is not clear to me whether this behavior is correct according to
RFC
> 3036. In particular, is it correct that two TCP sessions are created
and
> a router tries to open two LDP sessions (it sends two LDP
INITIALIZATION
> messages) with the same peer?
>
> Thanks,
> Alberto and Luca
> --------------------------------------------------------------------
>
> CONFIDENTIALITY NOTICE
>
> This message and its attachments are addressed solely to the persons =
> above and may contain confidential information. If you have received
> the = message in error, be informed that any use of the content hereof
> is
prohibited.
> Please return it immediately to the sender and delete the message. =
> Should you have any questions, please contact us by replying to
> webmaster@telecomitalia.it.
>
> Thank you
>
> www.telecomitalia.it
>
> --------------------------------------------------------------------
>
>
> _______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/mpls
>
>
> --------------------------------------------------------------------
>
> CONFIDENTIALITY NOTICE
>
> This message and its attachments are addressed solely to the persons =
> above and may contain confidential information. If you have received
the =
> message in error, be informed that any use of the content hereof is =
> prohibited. Please return it immediately to the sender and delete the
=
> message. Should you have any questions, please contact us by replying
to =
> webmaster@telecomitalia.it.
>
> Thank you
>
> www.telecomitalia.it
>
> --------------------------------------------------------------------
> =20
>
> _______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/mpls
>
_______________________________________________
mpls mailing list
mpls@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls
_______________________________________________
mpls mailing list
mpls@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls
_______________________________________________
mpls mailing list
mpls@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls
|
|