Re: Model: Configured Neighbor Table

hi,joel:
   As is saying:It is intended to allow an FE to be configured with 
information about neighbor FEs.The configured neighbor table is used to 
configure static FE 
topologys,and because CE could get the specified address info about the 
neighbors from LFB such as port LFB,so I think we could just reserved two 
field Neighborid and Neighbor interface and let CE get other info by 
itself,what do you think?
Yours,Fenggen
>From: "Joel M. Halpern" <[email protected]>
>Reply-To: "Joel M. Halpern" <[email protected]>
>To: [email protected]
>Subject: Model: Configured Neighbor Table
>Date: Thu, 28 Sep 2006 10:57:29 -0400
>
>--- original note:
>The configured neighbor table (section 5.3.4) is probably wrong.  
>This table is NOT intended to represent information from discovery 
>protocols.  It is intended to allow an FE to be configured with 
>information about neighbor FEs.
>
>[Prejudicial aside: I have argued on the list that this is not 
>necessary.  I lost the argument, so I can not simply remove the 
>section.]
>
>I need some input on what to put here.
>
>Yours,
>Joel M. Halpern
>---
>
>I had two people suggest removing this.  (I would count as three.)
>Failing removing, one of the people observed that the CE presumably 
>has IP and MAC address infromation from the identifier FE and FE 
>Interface.  Therefore, the suggestion was to remove those fields.
>One person asked to keep those fields.
>
>In the absence of any better discussion, I am removing the fields.  
>I agree that they are redundant, and I have to do something.

_________________________________________________________________
涓虹杩琛浜ゆ锛璇蜂娇 MSN Messenger:  http://messenger.msn.com/cn