[prev in list] [next in list] [prev in thread] [next in thread] 

List:       zebra
Subject:    [zebra 8634] Re: OSPF daemon API
From:       Ralph Keller <keller () arl ! wustl ! edu>
Date:       2001-05-31 15:08:59
[Download RAW message or body]

Dongmei,

> Your design is very impressive. I have a few questions:
> (1) API may want to retrieve all the LSAs with certain type from the link state database, do
> you think it might help if you define one function lsa_request_func(lsa_type).

There needs to be a function that retrieves all LSAs of a given type to synchronize the client
with the LSDB content. So far this has not been specified.

> (2) When API is brought up, should it ask for the non_self_generated opaque lsas
> of its own type from OSPFD? I mean for those already saved in the database.

Yes all LSAs (self-originated and LSAs from other routers) need to be retrieved.

> (3) Your message format for OSPFD and API comunication includes command field and data field.
> I am wondering how would you tell the end of one mssage if
> you have multiple messages in the buffer and have no knowledge about the length of each
> message.

Well the client knows the type of the message and then reads as many bytes as this message
contains. There might be a length field for the opaque data but not for the complete LSA.

- Ralph

[prev in list] [next in list] [prev in thread] [next in thread]