Hi all!
Thank you for your answer, it has proven most helpful. However, I have a new problem: how can I use GIST with RMD-QoS-NSLP in a stateless domain. I mean: 1. between Ingress and Egress stateful edge nodes, normal qos-nslp operation is sufficient with the following: - signaling messages sent between edge nodes over TCP (but intra-domain stateless nodes are not processing these edge2edge messages)
2. for the intra-domain nodes: - signaling is sent over UDP (and edge nodes are also processing these intra-domain messages)
I believe TCP/UDP choice can be solved with the reliable flag of the SendMessage API call, but I only have ideas regarding the local message processing or no-processing in the stateless intra-domain nodes.
I read in the drafts I shall use the RAO value/NSLP-ID to determine what message shall be passed on without processing, and what shall be passed up to the QoS-NSLP for processing. ( Shall I solve this by checking the NSLP-ID value at every node when receiving message from GIST to decide to process/pass on? )
Could you specify how can I achieve this? Is there an option in either the SendMessage/RecvMessage API call, or the mri to indicate this to GIST? Perhaps it is not a GIST-relevant question, but can I configure a linux-box to only handle packets with a specified RAO value? (The one I hope I can force GIST to use).
Thank you for your help,
Ferenc Pintér