Re: question on draft-lfblb-draft.txt?

I have removed the diagam below.  It ended up so wide that I could 
not get a good view of it.

I am pretty sure that you are asking what the relationship is between 
the port LFB and various forms of processing such as layer 2 
validation, layer 3 validation, forwarding lookup, etc.

The general guideline is that processing that is logically distinct 
should be in different LFBs.  Thus L3 validation L3 Next Hop 
selection, and Next hop application are ll proposed in the library to 
be separate LFBs.
The Port LFB should only include functionality that is closely 
coupled to the media.  So I have suggested that media decapsulation 
(or encapsulation) goes in the Port (or Generic Connectivity) 
LFB.  Media errors are also counted in that LFB.

However, that decomposition is just a suggestion.  The working group 
has not adopted the library draft.  Other folks haven't started 
writing class definitions for the draft.  If there is a different 
decomposition that helps us represent the range of implementations of 
routers and other packet processing devices, I am open to hearing it.

Yours,
Joel M. Halpern

At 01:11 AM 9/22/2006, Jia Fenggen wrote:
>Still another question about port LFB,in convention router,packet 
>processing on interface always be divided into to stages:ingress and 
>egress processing,ingress handles things like L2 decap,Forwarding 
>table lookup and then send the packets to fabric which will deliver 
>it to egress side for queuing and scheduling for sending out to 
>media.This two stage may reside in an interface processing card in 
>modern routers.My question is the Port LFB reside and fuctions in 
>such model.As model pictures:
...
>what's relationship between Ingress\Egress in the above draw and the 
>Port LFB?Should we give an example LFB topology which use the Port 
>LFB,in part to satify the ForCES Requriment and in another aspect 
>make the reader known more of the model? Yours,Fenggen