[mpls-linux-general] Re: LDP Qn
Status: Beta
Brought to you by:
jleu
From: James R. L. <jl...@mi...> - 2001-05-16 13:00:23
|
(could you please use the mpl...@li... list) On Wed, May 16, 2001 at 01:04:37AM -0700, yt...@12... wrote: > Hi all, > I have a Qn in LDP. When LDP receives label mapping message from its adjacent peer, is it required to install the label in FTN table eventhough its not ingress?. How u define Ingress?. The one which generates label request message is the Ingress. Am i right?. Each LSR needs decieds whether it will be ingress for a particular FEC. The rules that it uses for this will change based on policies created by the administrator of the network. For example, in the core of your network you may not want to be ingress for ANY FECs, but at the edge you want to be ingress for every FEC. This is normally controlled through access-lists route-maps or policy statments. > In MPLS linux LDP code, during label mapping message the function "ldp_policy_ingress_check" is invoked. If u walk through this function it is just returns TRUE. Thats all. If one want to install label always in FTN table why it need to call this func?. Pls let me know. Remeber that ldp-portable is meant to be run on other environments then the linux-port. For example the zebra-port may add access-list processing to ldp_policy_ingress_check(). The linux-port is only an example of how to implement a porting layer. Jim -- James R. Leu |