Nsis_Imp February 2005

nsis_imp@informatik.uni-goettingen.de

7 participants
21 discussions

web page recent changes
by Bernd Schloer 04 Mar '05

04 Mar '05

Also this mail might be lost: Hi list, please note the button 'recent changes' http://cleo-project.org/browse/recent_changes.html on cleo-project.org. This is a good entry to the web page as you see here what's going on and where progress was made. bye, Bernd

6 19

Re: [Nsis_imp] FW: [NSIS] I-D ACTION:draft-ietf-nsis-ntlp-05.txt
by Xiaoming Fu 25 Feb '05

25 Feb '05

Elwyn, Which do you think is better: a 05- or 04-conformant impl for this ietf? does this change much to interop? Xiaoming Elwyn davies wrote: > Hi. > > The new version of the GIMPS specification was published yesterday. > > There are some minor changes which affect what CLEO is doing at present: > - NTLP common header: Now contains a message type field in some of the > reserved bits together with a bit saying which source address is being used > (data sender or GIMPS hop). This is an improvement ... it makes message > parsing much easier as you don't need to work out what sort of message it is > from heuristics. > - Clears up a possible misunderstanding on my part regarding the CONFIRM > message. I thought this was sent on the new MA as the first message when it > was set up. This is not so... it is only sent on the MA if we are reusing > an existing MA (which means the RESPONSE message arrives on the MA). In the > case of a new MA, the CONFIRM message is sent in Dmode so that responders > that are postponing setting up MRS for as long as possible need only set it > up once the CONFIRM arrives. This affects Bernd primarily ... some details > in the FSM. > > I haven't had chance to do a really detailed read through, but these were > the headlines that I spotted on first pass (it is 92 pages now!). > > Regards, > Elwyn > > -----Original Message----- > From: nsis-bounces(a)ietf.org [mailto:nsis-bounces@ietf.org] On Behalf Of > Internet-Drafts(a)ietf.org > Sent: 23 February 2005 20:54 > To: i-d-announce(a)ietf.org > Cc: nsis(a)ietf.org > Subject: [NSIS] I-D ACTION:draft-ietf-nsis-ntlp-05.txt > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Next Steps in Signaling Working Group of > the IETF. > > Title : GIMPS: General Internet Messaging Protocol for > Signaling > Author(s) : H. Schulzrinne, R. Hancock > Filename : draft-ietf-nsis-ntlp-05.txt > Pages : 92 > Date : 2005-2-23 > > This document specifies protocol stacks for the routing and transport > of per-flow signaling messages along the path taken by that flow > through the network. The design uses existing transport and security > protocols under a common messaging layer, the General Internet > Messaging Protocol for Signaling (GIMPS), which provides a universal > service for diverse signaling applications. GIMPS does not handle > signaling application state itself, but manages its own internal > state and the configuration of the underlying transport and security > protocols to enable the transfer of messages in both directions along > the flow path. The combination of GIMPS and the lower layer > transport and security protocols provides a solution for the base > protocol component of the "Next Steps in Signaling" framework. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-nsis-ntlp-05.txt > > To remove yourself from the I-D Announcement list, send a message to > i-d-announce-request(a)ietf.org with the word unsubscribe in the body of the > message. > You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce > to change your subscription settings. > > > Internet-Drafts are also available by anonymous FTP. Login with the username > "anonymous" and a password of your e-mail address. After logging in, > type "cd internet-drafts" and then > "get draft-ietf-nsis-ntlp-05.txt". > > A list of Internet-Drafts directories can be found in > http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > Internet-Drafts can also be obtained by e-mail. > > Send a message to: > mailserv(a)ietf.org. > In the body type: > "FILE /internet-drafts/draft-ietf-nsis-ntlp-05.txt". > > NOTE: The mail server at ietf.org can return the document in > MIME-encoded form by using the "mpack" utility. To use this > feature, insert the command "ENCODING mime" before the "FILE" > command. To decode the response(s), you will need "munpack" or > a MIME-compliant mail reader. Different MIME-compliant mail readers > exhibit different behavior, especially when dealing with > "multipart" MIME messages (i.e. documents which have been split > up into multiple messages), so check your local documentation on > how to manipulate these messages. > > > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. > > > ------------------------------------------------------------------------ > > _______________________________________________ > nsis mailing list > nsis(a)ietf.org > https://www1.ietf.org/mailman/listinfo/nsis > > > ------------------------------------------------------------------------ > > _______________________________________________ > Nsis_imp mailing list > Nsis_imp(a)informatik.uni-goettingen.de > https://user.informatik.uni-goettingen.de/mailman/listinfo/nsis_imp

2 1

FW: [NSIS] I-D ACTION:draft-ietf-nsis-ntlp-05.txt
by Elwyn davies 25 Feb '05

25 Feb '05

Hi. The new version of the GIMPS specification was published yesterday. There are some minor changes which affect what CLEO is doing at present: - NTLP common header: Now contains a message type field in some of the reserved bits together with a bit saying which source address is being used (data sender or GIMPS hop). This is an improvement ... it makes message parsing much easier as you don't need to work out what sort of message it is from heuristics. - Clears up a possible misunderstanding on my part regarding the CONFIRM message. I thought this was sent on the new MA as the first message when it was set up. This is not so... it is only sent on the MA if we are reusing an existing MA (which means the RESPONSE message arrives on the MA). In the case of a new MA, the CONFIRM message is sent in Dmode so that responders that are postponing setting up MRS for as long as possible need only set it up once the CONFIRM arrives. This affects Bernd primarily ... some details in the FSM. I haven't had chance to do a really detailed read through, but these were the headlines that I spotted on first pass (it is 92 pages now!). Regards, Elwyn -----Original Message----- From: nsis-bounces(a)ietf.org [mailto:nsis-bounces@ietf.org] On Behalf Of Internet-Drafts(a)ietf.org Sent: 23 February 2005 20:54 To: i-d-announce(a)ietf.org Cc: nsis(a)ietf.org Subject: [NSIS] I-D ACTION:draft-ietf-nsis-ntlp-05.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Next Steps in Signaling Working Group of the IETF. Title : GIMPS: General Internet Messaging Protocol for Signaling Author(s) : H. Schulzrinne, R. Hancock Filename : draft-ietf-nsis-ntlp-05.txt Pages : 92 Date : 2005-2-23 This document specifies protocol stacks for the routing and transport of per-flow signaling messages along the path taken by that flow through the network. The design uses existing transport and security protocols under a common messaging layer, the General Internet Messaging Protocol for Signaling (GIMPS), which provides a universal service for diverse signaling applications. GIMPS does not handle signaling application state itself, but manages its own internal state and the configuration of the underlying transport and security protocols to enable the transfer of messages in both directions along the flow path. The combination of GIMPS and the lower layer transport and security protocols provides a solution for the base protocol component of the "Next Steps in Signaling" framework. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-nsis-ntlp-05.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request(a)ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-nsis-ntlp-05.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv(a)ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-nsis-ntlp-05.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. ENCODING mime FILE /internet-drafts/draft-ietf-nsis-ntlp-05.txt

1 0

GIMPS_FSM
by Bernd Schloer 24 Feb '05

24 Feb '05

Hi, in the .txt file you can see the output of the testfile gimps_states.cpp (tables and simulated connection-setup -> connection-teardown -> connection-setup for both Initiator and Responder). You have a better look at the tables in the source itself. Files are accessible here: http://cleo-project.org/filebase/gimps_fsm.zip or via CVS. ToDo: put Event-Triggers into Parser-Source and complete pseudo-code functions which are called by the FSM. bye, Bernd 00, State:00, IDLE_RESPONDER , Event:00, EV_SENDMESSAGE_NSLP_API_CALL_DMODE_DOWNSTREAM_RESPONDER , Routine:0x8053260 01, State:00, IDLE_RESPONDER , Event:01, EV_SENDMESSAGE_NSLP_API_CALL_CMODE_DOWNSTREAM_RESPONDER , Routine:0x8053220 02, State:00, IDLE_RESPONDER , Event:02, EV_SET_STATE_LIFETIME_NSLP_API_CALL_RESPONDER , Routine:0x80532a0 03, State:00, IDLE_RESPONDER , Event:03, EV_ADJACENCY_RESPONSE_TIMER_TIMEOUT_RESPONDER , Routine:0x80534b0 04, State:00, IDLE_RESPONDER , Event:04, EV_NETWORK_RECEIVE_DMODE_UPSTREAM_CONTROL_MESSAGE_RECEIVED_GIMPS_RESPONSE_RESPONDER , Routine:0x8053190 05, State:00, IDLE_RESPONDER , Event:05, EV_NETWORK_RECEIVE_CMODE_UPSTREAM_CONTROL_MESSAGE_RECEIVED_GIMPS_RESPONSE_RESPONDER , Routine:0x8053190 06, State:00, IDLE_RESPONDER , Event:06, EV_NETWORK_RECEIVE_DMODE_UPSTREAM_DATA_MESSAGE_RECEIVED_RESPONDER , Routine:0x8053190 07, State:00, IDLE_RESPONDER , Event:07, EV_NETWORK_RECEIVE_CMODE_UPSTREAM_DATA_MESSAGE_RECEIVED_RESPONDER , Routine:0x8053190 08, State:00, IDLE_RESPONDER , Event:08, EV_DOWNSTREAM_REFRESH_TIMER_TIMEOUT_RESPONDER , Routine:0x8053190 09, State:01, WAIT_RESPONSE_1_RESPONDER , Event:00, EV_SENDMESSAGE_NSLP_API_CALL_DMODE_DOWNSTREAM_RESPONDER , Routine:0x8053190 10, State:01, WAIT_RESPONSE_1_RESPONDER , Event:01, EV_SENDMESSAGE_NSLP_API_CALL_CMODE_DOWNSTREAM_RESPONDER , Routine:0x8053190 11, State:01, WAIT_RESPONSE_1_RESPONDER , Event:02, EV_SET_STATE_LIFETIME_NSLP_API_CALL_RESPONDER , Routine:0x80532a0 12, State:01, WAIT_RESPONSE_1_RESPONDER , Event:03, EV_ADJACENCY_RESPONSE_TIMER_TIMEOUT_RESPONDER , Routine:0x80534b0 13, State:01, WAIT_RESPONSE_1_RESPONDER , Event:04, EV_NETWORK_RECEIVE_DMODE_UPSTREAM_CONTROL_MESSAGE_RECEIVED_GIMPS_RESPONSE_RESPONDER , Routine:0x8053320 14, State:01, WAIT_RESPONSE_1_RESPONDER , Event:05, EV_NETWORK_RECEIVE_CMODE_UPSTREAM_CONTROL_MESSAGE_RECEIVED_GIMPS_RESPONSE_RESPONDER , Routine:0x80532e0 15, State:01, WAIT_RESPONSE_1_RESPONDER , Event:06, EV_NETWORK_RECEIVE_DMODE_UPSTREAM_DATA_MESSAGE_RECEIVED_RESPONDER , Routine:0x8053190 16, State:01, WAIT_RESPONSE_1_RESPONDER , Event:07, EV_NETWORK_RECEIVE_CMODE_UPSTREAM_DATA_MESSAGE_RECEIVED_RESPONDER , Routine:0x8053190 17, State:01, WAIT_RESPONSE_1_RESPONDER , Event:08, EV_DOWNSTREAM_REFRESH_TIMER_TIMEOUT_RESPONDER , Routine:0x8053190 18, State:02, WAIT_RESPONSE_2_RESPONDER , Event:00, EV_SENDMESSAGE_NSLP_API_CALL_DMODE_DOWNSTREAM_RESPONDER , Routine:0x8053190 19, State:02, WAIT_RESPONSE_2_RESPONDER , Event:01, EV_SENDMESSAGE_NSLP_API_CALL_CMODE_DOWNSTREAM_RESPONDER , Routine:0x8053190 20, State:02, WAIT_RESPONSE_2_RESPONDER , Event:02, EV_SET_STATE_LIFETIME_NSLP_API_CALL_RESPONDER , Routine:0x80532a0 21, State:02, WAIT_RESPONSE_2_RESPONDER , Event:03, EV_ADJACENCY_RESPONSE_TIMER_TIMEOUT_RESPONDER , Routine:0x80534b0 22, State:02, WAIT_RESPONSE_2_RESPONDER , Event:04, EV_NETWORK_RECEIVE_DMODE_UPSTREAM_CONTROL_MESSAGE_RECEIVED_GIMPS_RESPONSE_RESPONDER , Routine:0x8053360 23, State:02, WAIT_RESPONSE_2_RESPONDER , Event:05, EV_NETWORK_RECEIVE_CMODE_UPSTREAM_CONTROL_MESSAGE_RECEIVED_GIMPS_RESPONSE_RESPONDER , Routine:0x8053190 24, State:02, WAIT_RESPONSE_2_RESPONDER , Event:06, EV_NETWORK_RECEIVE_DMODE_UPSTREAM_DATA_MESSAGE_RECEIVED_RESPONDER , Routine:0x8053190 25, State:02, WAIT_RESPONSE_2_RESPONDER , Event:07, EV_NETWORK_RECEIVE_CMODE_UPSTREAM_DATA_MESSAGE_RECEIVED_RESPONDER , Routine:0x8053190 26, State:02, WAIT_RESPONSE_2_RESPONDER , Event:08, EV_DOWNSTREAM_REFRESH_TIMER_TIMEOUT_RESPONDER , Routine:0x8053190 27, State:03, ESTABLISHED_DOWNSTREAM_MRS_MA_RESPONDER, Event:00, EV_SENDMESSAGE_NSLP_API_CALL_DMODE_DOWNSTREAM_RESPONDER , Routine:0x8053190 28, State:03, ESTABLISHED_DOWNSTREAM_MRS_MA_RESPONDER, Event:01, EV_SENDMESSAGE_NSLP_API_CALL_CMODE_DOWNSTREAM_RESPONDER , Routine:0x80533d0 29, State:03, ESTABLISHED_DOWNSTREAM_MRS_MA_RESPONDER, Event:02, EV_SET_STATE_LIFETIME_NSLP_API_CALL_RESPONDER , Routine:0x80532a0 30, State:03, ESTABLISHED_DOWNSTREAM_MRS_MA_RESPONDER, Event:03, EV_ADJACENCY_RESPONSE_TIMER_TIMEOUT_RESPONDER , Routine:0x80534b0 31, State:03, ESTABLISHED_DOWNSTREAM_MRS_MA_RESPONDER, Event:04, EV_NETWORK_RECEIVE_DMODE_UPSTREAM_CONTROL_MESSAGE_RECEIVED_GIMPS_RESPONSE_RESPONDER , Routine:0x8053430 32, State:03, ESTABLISHED_DOWNSTREAM_MRS_MA_RESPONDER, Event:05, EV_NETWORK_RECEIVE_CMODE_UPSTREAM_CONTROL_MESSAGE_RECEIVED_GIMPS_RESPONSE_RESPONDER , Routine:0x80533f0 33, State:03, ESTABLISHED_DOWNSTREAM_MRS_MA_RESPONDER, Event:06, EV_NETWORK_RECEIVE_DMODE_UPSTREAM_DATA_MESSAGE_RECEIVED_RESPONDER , Routine:0x8053190 34, State:03, ESTABLISHED_DOWNSTREAM_MRS_MA_RESPONDER, Event:07, EV_NETWORK_RECEIVE_CMODE_UPSTREAM_DATA_MESSAGE_RECEIVED_RESPONDER , Routine:0x8053410 35, State:03, ESTABLISHED_DOWNSTREAM_MRS_MA_RESPONDER, Event:08, EV_DOWNSTREAM_REFRESH_TIMER_TIMEOUT_RESPONDER , Routine:0x8053190 36, State:04, ESTABLISHED_DOWNSTREAM_MRS_RESPONDER , Event:00, EV_SENDMESSAGE_NSLP_API_CALL_DMODE_DOWNSTREAM_RESPONDER , Routine:0x8053190 37, State:04, ESTABLISHED_DOWNSTREAM_MRS_RESPONDER , Event:01, EV_SENDMESSAGE_NSLP_API_CALL_CMODE_DOWNSTREAM_RESPONDER , Routine:0x8053190 38, State:04, ESTABLISHED_DOWNSTREAM_MRS_RESPONDER , Event:02, EV_SET_STATE_LIFETIME_NSLP_API_CALL_RESPONDER , Routine:0x80532a0 39, State:04, ESTABLISHED_DOWNSTREAM_MRS_RESPONDER , Event:03, EV_ADJACENCY_RESPONSE_TIMER_TIMEOUT_RESPONDER , Routine:0x80534b0 40, State:04, ESTABLISHED_DOWNSTREAM_MRS_RESPONDER , Event:04, EV_NETWORK_RECEIVE_DMODE_UPSTREAM_CONTROL_MESSAGE_RECEIVED_GIMPS_RESPONSE_RESPONDER , Routine:0x8053430 41, State:04, ESTABLISHED_DOWNSTREAM_MRS_RESPONDER , Event:05, EV_NETWORK_RECEIVE_CMODE_UPSTREAM_CONTROL_MESSAGE_RECEIVED_GIMPS_RESPONSE_RESPONDER , Routine:0x8053190 42, State:04, ESTABLISHED_DOWNSTREAM_MRS_RESPONDER , Event:06, EV_NETWORK_RECEIVE_DMODE_UPSTREAM_DATA_MESSAGE_RECEIVED_RESPONDER , Routine:0x8053450 43, State:04, ESTABLISHED_DOWNSTREAM_MRS_RESPONDER , Event:07, EV_NETWORK_RECEIVE_CMODE_UPSTREAM_DATA_MESSAGE_RECEIVED_RESPONDER , Routine:0x8053190 44, State:04, ESTABLISHED_DOWNSTREAM_MRS_RESPONDER , Event:08, EV_DOWNSTREAM_REFRESH_TIMER_TIMEOUT_RESPONDER , Routine:0x80534f0 00, State:00, IDLE_INITIATOR , Event:00, EV_SENDMESSAGE_NSLP_API_CALL_DMODE_UPSTREAM_INITIATOR , Routine:0x8053190 01, State:00, IDLE_INITIATOR , Event:01, EV_SENDMESSAGE_NSLP_API_CALL_CMODE_UPSTREAM_INITIATOR , Routine:0x8053190 02, State:00, IDLE_INITIATOR , Event:02, EV_SET_STATE_LIFETIME_NSLP_API_CALL_INITIATOR , Routine:0x8053570 03, State:00, IDLE_INITIATOR , Event:03, EV_ADJACENCY_RESPONSE_TIMER_TIMEOUT_INITIATOR , Routine:0x8053710 04, State:00, IDLE_INITIATOR , Event:04, EV_NETWORK_RECEIVE_DMODE_DOWNSTREAM_CONTROL_MESSAGE_RECEIVED_GIMPS_QUERY_INITIATOR , Routine:0x8053530 05, State:00, IDLE_INITIATOR , Event:05, EV_NETWORK_RECEIVE_DMODE_DOWNSTREAM_CONTROL_MESSAGE_RECEIVED_GIMPS_CONFIRM_INITIATOR, Routine:0x8053190 06, State:00, IDLE_INITIATOR , Event:06, EV_NETWORK_RECEIVE_CMODE_DOWNSTREAM_CONTROL_MESSAGE_RECEIVED_GIMPS_QUERY_INITIATOR , Routine:0x8053190 07, State:00, IDLE_INITIATOR , Event:07, EV_NETWORK_RECEIVE_CMODE_DOWNSTREAM_CONTROL_MESSAGE_RECEIVED_GIMPS_CONFIRM_INITIATOR, Routine:0x8053190 08, State:00, IDLE_INITIATOR , Event:08, EV_NETWORK_RECEIVE_DMODE_DOWNSTREAM_DATA_MESSAGE_RECEIVED_INITIATOR , Routine:0x8053190 09, State:00, IDLE_INITIATOR , Event:09, EV_NETWORK_RECEIVE_CMODE_DOWNSTREAM_DATA_MESSAGE_RECEIVED_INITIATOR , Routine:0x8053190 10, State:00, IDLE_INITIATOR , Event:10, EV_UPSTREAM_REFRESH_TIMER_TIMEOUT_INITIATOR , Routine:0x8053190 11, State:01, WAIT_CONFIRM_INITIATOR , Event:00, EV_SENDMESSAGE_NSLP_API_CALL_DMODE_UPSTREAM_INITIATOR , Routine:0x8053190 12, State:01, WAIT_CONFIRM_INITIATOR , Event:01, EV_SENDMESSAGE_NSLP_API_CALL_CMODE_UPSTREAM_INITIATOR , Routine:0x8053190 13, State:01, WAIT_CONFIRM_INITIATOR , Event:02, EV_SET_STATE_LIFETIME_NSLP_API_CALL_INITIATOR , Routine:0x8053570 14, State:01, WAIT_CONFIRM_INITIATOR , Event:03, EV_ADJACENCY_RESPONSE_TIMER_TIMEOUT_INITIATOR , Routine:0x8053710 15, State:01, WAIT_CONFIRM_INITIATOR , Event:04, EV_NETWORK_RECEIVE_DMODE_DOWNSTREAM_CONTROL_MESSAGE_RECEIVED_GIMPS_QUERY_INITIATOR , Routine:0x8053190 16, State:01, WAIT_CONFIRM_INITIATOR , Event:05, EV_NETWORK_RECEIVE_DMODE_DOWNSTREAM_CONTROL_MESSAGE_RECEIVED_GIMPS_CONFIRM_INITIATOR, Routine:0x80535f0 17, State:01, WAIT_CONFIRM_INITIATOR , Event:06, EV_NETWORK_RECEIVE_CMODE_DOWNSTREAM_CONTROL_MESSAGE_RECEIVED_GIMPS_QUERY_INITIATOR , Routine:0x8053190 18, State:01, WAIT_CONFIRM_INITIATOR , Event:07, EV_NETWORK_RECEIVE_CMODE_DOWNSTREAM_CONTROL_MESSAGE_RECEIVED_GIMPS_CONFIRM_INITIATOR, Routine:0x80535b0 19, State:01, WAIT_CONFIRM_INITIATOR , Event:08, EV_NETWORK_RECEIVE_DMODE_DOWNSTREAM_DATA_MESSAGE_RECEIVED_INITIATOR , Routine:0x8053190 20, State:01, WAIT_CONFIRM_INITIATOR , Event:09, EV_NETWORK_RECEIVE_CMODE_DOWNSTREAM_DATA_MESSAGE_RECEIVED_INITIATOR , Routine:0x8053190 21, State:01, WAIT_CONFIRM_INITIATOR , Event:10, EV_UPSTREAM_REFRESH_TIMER_TIMEOUT_INITIATOR , Routine:0x8053190 22, State:02, ESTABLISHED_DOWNSTREAM_MRS_MA_INITIATOR, Event:00, EV_SENDMESSAGE_NSLP_API_CALL_DMODE_UPSTREAM_INITIATOR , Routine:0x80536f0 23, State:02, ESTABLISHED_DOWNSTREAM_MRS_MA_INITIATOR, Event:01, EV_SENDMESSAGE_NSLP_API_CALL_CMODE_UPSTREAM_INITIATOR , Routine:0x8053630 24, State:02, ESTABLISHED_DOWNSTREAM_MRS_MA_INITIATOR, Event:02, EV_SET_STATE_LIFETIME_NSLP_API_CALL_INITIATOR , Routine:0x8053570 25, State:02, ESTABLISHED_DOWNSTREAM_MRS_MA_INITIATOR, Event:03, EV_ADJACENCY_RESPONSE_TIMER_TIMEOUT_INITIATOR , Routine:0x8053710 26, State:02, ESTABLISHED_DOWNSTREAM_MRS_MA_INITIATOR, Event:04, EV_NETWORK_RECEIVE_DMODE_DOWNSTREAM_CONTROL_MESSAGE_RECEIVED_GIMPS_QUERY_INITIATOR , Routine:0x8053190 27, State:02, ESTABLISHED_DOWNSTREAM_MRS_MA_INITIATOR, Event:05, EV_NETWORK_RECEIVE_DMODE_DOWNSTREAM_CONTROL_MESSAGE_RECEIVED_GIMPS_CONFIRM_INITIATOR, Routine:0x8053190 28, State:02, ESTABLISHED_DOWNSTREAM_MRS_MA_INITIATOR, Event:06, EV_NETWORK_RECEIVE_CMODE_DOWNSTREAM_CONTROL_MESSAGE_RECEIVED_GIMPS_QUERY_INITIATOR , Routine:0x8053190 29, State:02, ESTABLISHED_DOWNSTREAM_MRS_MA_INITIATOR, Event:07, EV_NETWORK_RECEIVE_CMODE_DOWNSTREAM_CONTROL_MESSAGE_RECEIVED_GIMPS_CONFIRM_INITIATOR, Routine:0x8053190 30, State:02, ESTABLISHED_DOWNSTREAM_MRS_MA_INITIATOR, Event:08, EV_NETWORK_RECEIVE_DMODE_DOWNSTREAM_DATA_MESSAGE_RECEIVED_INITIATOR , Routine:0x8053190 31, State:02, ESTABLISHED_DOWNSTREAM_MRS_MA_INITIATOR, Event:09, EV_NETWORK_RECEIVE_CMODE_DOWNSTREAM_DATA_MESSAGE_RECEIVED_INITIATOR , Routine:0x8053650 32, State:02, ESTABLISHED_DOWNSTREAM_MRS_MA_INITIATOR, Event:10, EV_UPSTREAM_REFRESH_TIMER_TIMEOUT_INITIATOR , Routine:0x8053190 33, State:03, ESTABLISHED_DOWNSTREAM_MRS_INITIATOR , Event:00, EV_SENDMESSAGE_NSLP_API_CALL_DMODE_UPSTREAM_INITIATOR , Routine:0x80536f0 34, State:03, ESTABLISHED_DOWNSTREAM_MRS_INITIATOR , Event:01, EV_SENDMESSAGE_NSLP_API_CALL_CMODE_UPSTREAM_INITIATOR , Routine:0x8053190 35, State:03, ESTABLISHED_DOWNSTREAM_MRS_INITIATOR , Event:02, EV_SET_STATE_LIFETIME_NSLP_API_CALL_INITIATOR , Routine:0x8053570 36, State:03, ESTABLISHED_DOWNSTREAM_MRS_INITIATOR , Event:03, EV_ADJACENCY_RESPONSE_TIMER_TIMEOUT_INITIATOR , Routine:0x8053710 37, State:03, ESTABLISHED_DOWNSTREAM_MRS_INITIATOR , Event:04, EV_NETWORK_RECEIVE_DMODE_DOWNSTREAM_CONTROL_MESSAGE_RECEIVED_GIMPS_QUERY_INITIATOR , Routine:0x80536d0 38, State:03, ESTABLISHED_DOWNSTREAM_MRS_INITIATOR , Event:05, EV_NETWORK_RECEIVE_DMODE_DOWNSTREAM_CONTROL_MESSAGE_RECEIVED_GIMPS_CONFIRM_INITIATOR, Routine:0x8053190 39, State:03, ESTABLISHED_DOWNSTREAM_MRS_INITIATOR , Event:06, EV_NETWORK_RECEIVE_CMODE_DOWNSTREAM_CONTROL_MESSAGE_RECEIVED_GIMPS_QUERY_INITIATOR , Routine:0x8053190 40, State:03, ESTABLISHED_DOWNSTREAM_MRS_INITIATOR , Event:07, EV_NETWORK_RECEIVE_CMODE_DOWNSTREAM_CONTROL_MESSAGE_RECEIVED_GIMPS_CONFIRM_INITIATOR, Routine:0x8053190 41, State:03, ESTABLISHED_DOWNSTREAM_MRS_INITIATOR , Event:08, EV_NETWORK_RECEIVE_DMODE_DOWNSTREAM_DATA_MESSAGE_RECEIVED_INITIATOR , Routine:0x8053670 42, State:03, ESTABLISHED_DOWNSTREAM_MRS_INITIATOR , Event:09, EV_NETWORK_RECEIVE_CMODE_DOWNSTREAM_DATA_MESSAGE_RECEIVED_INITIATOR , Routine:0x8053190 43, State:03, ESTABLISHED_DOWNSTREAM_MRS_INITIATOR , Event:10, EV_UPSTREAM_REFRESH_TIMER_TIMEOUT_INITIATOR , Routine:0x8053690 FsmInitTimer : 0x8063c74, 2000ms FsmInitTimer : 0x8063cb0, 2000ms State : IDLE_RESPONDER Event : EV_SENDMESSAGE_NSLP_API_CALL_CMODE_DOWNSTREAM_RESPONDER Timer : 0x8063c74 Routine : 0x8053220 Idle__Wait_Response_1_Responder ChangeState : WAIT_RESPONSE_1_RESPONDER State : WAIT_RESPONSE_1_RESPONDER Event : EV_NETWORK_RECEIVE_CMODE_UPSTREAM_CONTROL_MESSAGE_RECEIVED_GIMPS_RESPONSE_RESPONDER Timer : 0x8063c74 Routine : 0x80532e0 Wait_Response_1__Established_Downstream_MRS_MA_Cmode_Responder ChangeState : ESTABLISHED_DOWNSTREAM_MRS_MA_RESPONDER State : ESTABLISHED_DOWNSTREAM_MRS_MA_RESPONDER Event : EV_NETWORK_RECEIVE_CMODE_UPSTREAM_DATA_MESSAGE_RECEIVED_RESPONDER Timer : 0x8063c74 Routine : 0x8053410 Receive_Upstream_Data_Message_Cmode_Responder State : ESTABLISHED_DOWNSTREAM_MRS_MA_RESPONDER Event : EV_SET_STATE_LIFETIME_NSLP_API_CALL_RESPONDER Timer : 0x8063c74 Routine : 0x80532a0 Set_State_Lifetime_Responder ChangeState : IDLE_RESPONDER ------------------------------------------------------------------------------------------------ State : IDLE_RESPONDER Event : EV_SENDMESSAGE_NSLP_API_CALL_CMODE_DOWNSTREAM_RESPONDER Timer : 0x8063c74 Routine : 0x8053220 Idle__Wait_Response_1_Responder ChangeState : WAIT_RESPONSE_1_RESPONDER State : WAIT_RESPONSE_1_RESPONDER Event : EV_NETWORK_RECEIVE_CMODE_UPSTREAM_CONTROL_MESSAGE_RECEIVED_GIMPS_RESPONSE_RESPONDER Timer : 0x8063c74 Routine : 0x80532e0 Wait_Response_1__Established_Downstream_MRS_MA_Cmode_Responder ChangeState : ESTABLISHED_DOWNSTREAM_MRS_MA_RESPONDER State : ESTABLISHED_DOWNSTREAM_MRS_MA_RESPONDER Event : EV_NETWORK_RECEIVE_CMODE_UPSTREAM_DATA_MESSAGE_RECEIVED_RESPONDER Timer : 0x8063c74 Routine : 0x8053410 Receive_Upstream_Data_Message_Cmode_Responder ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ State : IDLE_INITIATOR Event : EV_NETWORK_RECEIVE_DMODE_DOWNSTREAM_CONTROL_MESSAGE_RECEIVED_GIMPS_QUERY_INITIATOR Timer : 0x8063cb0 Routine : 0x8053530 Idle__Wait_Confirm_Initiator ChangeState : WAIT_CONFIRM_INITIATOR State : WAIT_CONFIRM_INITIATOR Event : EV_NETWORK_RECEIVE_CMODE_DOWNSTREAM_CONTROL_MESSAGE_RECEIVED_GIMPS_CONFIRM_INITIATOR Timer : 0x8063cb0 Routine : 0x80535b0 Wait_Confirm__Established_Upstream_MRS_MA_Initiator ChangeState : ESTABLISHED_DOWNSTREAM_MRS_MA_INITIATOR State : ESTABLISHED_DOWNSTREAM_MRS_MA_INITIATOR Event : EV_NETWORK_RECEIVE_CMODE_DOWNSTREAM_DATA_MESSAGE_RECEIVED_INITIATOR Timer : 0x8063cb0 Routine : 0x8053650 Receive_Downstream_Message_Cmode_Initiator State : ESTABLISHED_DOWNSTREAM_MRS_MA_INITIATOR Event : EV_SENDMESSAGE_NSLP_API_CALL_CMODE_UPSTREAM_INITIATOR Timer : 0x8063cb0 Routine : 0x8053630 Receive_Upstream_SendMessage_Cmode_Events_Initiator State : ESTABLISHED_DOWNSTREAM_MRS_MA_INITIATOR Event : EV_SET_STATE_LIFETIME_NSLP_API_CALL_INITIATOR Timer : 0x8063cb0 Routine : 0x8053570 Set_State_Lifetime_Initiator ChangeState : IDLE_INITIATOR ------------------------------------------------------------------------------------------------ State : IDLE_INITIATOR Event : EV_NETWORK_RECEIVE_DMODE_DOWNSTREAM_CONTROL_MESSAGE_RECEIVED_GIMPS_QUERY_INITIATOR Timer : 0x8063cb0 Routine : 0x8053530 Idle__Wait_Confirm_Initiator ChangeState : WAIT_CONFIRM_INITIATOR State : WAIT_CONFIRM_INITIATOR Event : EV_NETWORK_RECEIVE_CMODE_DOWNSTREAM_CONTROL_MESSAGE_RECEIVED_GIMPS_CONFIRM_INITIATOR Timer : 0x8063cb0 Routine : 0x80535b0 Wait_Confirm__Established_Upstream_MRS_MA_Initiator ChangeState : ESTABLISHED_DOWNSTREAM_MRS_MA_INITIATOR State : ESTABLISHED_DOWNSTREAM_MRS_MA_INITIATOR Event : EV_NETWORK_RECEIVE_CMODE_DOWNSTREAM_DATA_MESSAGE_RECEIVED_INITIATOR Timer : 0x8063cb0 Routine : 0x8053650 Receive_Downstream_Message_Cmode_Initiator State : ESTABLISHED_DOWNSTREAM_MRS_MA_INITIATOR Event : EV_SENDMESSAGE_NSLP_API_CALL_CMODE_UPSTREAM_INITIATOR Timer : 0x8063cb0 Routine : 0x8053630 Receive_Upstream_SendMessage_Cmode_Events_Initiator FsmExpireTimer : 0x8063c74. Setting Event: EV_DOWNSTREAM_REFRESH_TIMER_TIMEOUT_RESPONDER State : ESTABLISHED_DOWNSTREAM_MRS_MA_RESPONDER Event : EV_DOWNSTREAM_REFRESH_TIMER_TIMEOUT_RESPONDER Timer : 0x8063c74 Routine : 0x8053190 Error - The Event EV_DOWNSTREAM_REFRESH_TIMER_TIMEOUT_RESPONDER is not defined in ESTABLISHED_DOWNSTREAM_MRS_MA_RESPONDER FsmExpireTimer : 0x8063cb0. Setting Event: EV_UPSTREAM_REFRESH_TIMER_TIMEOUT_INITIATOR State : ESTABLISHED_DOWNSTREAM_MRS_MA_INITIATOR Event : EV_UPSTREAM_REFRESH_TIMER_TIMEOUT_INITIATOR Timer : 0x8063cb0 Routine : 0x8053190 Error - The Event EV_UPSTREAM_REFRESH_TIMER_TIMEOUT_INITIATOR is not defined in ESTABLISHED_DOWNSTREAM_MRS_MA_INITIATOR no timers pending. exiting...

1 0

The Parser HowTo
by Bernd Schloer 23 Feb '05

23 Feb '05

Hi, here's a brief description of the parser. Thanks Youssef. Hi Bernd, Let's suppose we are in the socket handling part of the code. We have just read the beginning of a new gimps message. We now know how long is the message (the length of the entire gimps message is simply a field in the header of the gimps message). Let's say the message (header included) is n bytes long. We allocate enough memory: char * stream = new char[n]; or char * stream = malloc(n); We then read the message from the socket and put it in stream. The help of our parser is only needed now. A gimps message has to be allocated: GimpsMessage *gimps_message = new GimpsMessage(); Then a simple call to the GimpsMessage::parse method parses the entire message (including the objects it contains): gimps_message->parse(stream); That is all. We tried to do some tests, but our parser (even if it should have been a really simple piece of code) still has to be thoroughly tested. I hope this helps. Again, don't hesitate if you need anything. Youssef.

1 0

[Fwd: [NSIS_FSM] a "tutorial" to NSIS/GIMPS]
by Xiaoming Fu 19 Feb '05

19 Feb '05

sorry to all@cleo: was sent to a wrong list -------- Original Message -------- Subject: [NSIS_FSM] a "tutorial" to NSIS/GIMPS Date: Tue, 25 Jan 2005 17:34:34 +0100 From: Xiaoming Fu <fu(a)cs.uni-goettingen.de> Reply-To: NSIS FSM discussion mailing list <nsis_fsm(a)informatik.uni-goettingen.de> To: NSIS FSM discussion mailing list <nsis_fsm(a)informatik.uni-goettingen.de> Hi all, Please find attached a "tutorial" I made for the convenience of NSIS newbies in the cleo team to understand a bit about GIMPS basic operation and its background. Note this is only meant for CLEO, not elsewhere: please keep it confidentially! HT/CA/Tseno/SW: you may point out any incorrect or better info to me (and certainly we can update it). If you have any questions to the information (esp. "routine"), feel free to ask us. BTW - I am away this Thursday and Friday again Xiaoming _______________________________________________ Nsis_fsm mailing list Nsis_fsm(a)informatik.uni-goettingen.de http://user.informatik.uni-goettingen.de/mailman/listinfo/nsis_fsm

2 4

[Nsis_imp]GIPMS state machine confusing issues
by Tseno Tsenov 17 Feb '05

17 Feb '05

Hi all, I found out that there are some points in the gimps FSM that are confusing. It is especially visible in the gimps-intermediate node. The FSM states represent the states of the upstream/downstream peers states in the MRS table. Since the peer states have separate timers for refresh and lifetime I though it is a good point to explicitly assign then to different FSM states. So, for the intermediate node we have: ----------------------- Established Upstream MRS: MRS is established with state info about the upstream peer. Established Upstream and Downstream MRS: MRS is established with state info about the upstream peer and no state info about the downstream peer.This is similar to "Upstream MRS" but the GIMPS node should take care of the refreshment of the MRS. Established Upstream MRS+MA: MRS is established with state info about the upstream peer/pointer to MA/. Established Upstream MRS+MA and Downstream MRS: MRS is established with state info about the upstream peer/pointer to MA/ and no state info about the downstream peer.This is similar to "Upstream MRS+MA" but the GIMPS node should take care of the refreshment of the MRS. Established Upstream MRS+MA and Downstream MRS+MA: MRS is established with state info about the upstream peer/pointer to MA/ and with state info about the downstream peer/pointer to MA/.The GIMPS node should take care of the refreshment of the MRS. --------------------- Elwyn, is this the problem that you mentioned about your interpretation and this FSM? Do you find this notation suitalbe or too confusing? Greetings, Tseno_

1 0

[Fwd: [Nsis-imp] GIMPS assigned numbers]
by Xiaoming Fu 16 Feb '05

16 Feb '05

fyi btw- please subscribe to the following list if you have not yet done so: https://www1.ietf.org/mailman/listinfo/nsis-imp https://www1.ietf.org/mailman/listinfo/nsis -------- Original Message -------- Subject: [Nsis-imp] GIMPS assigned numbers Date: Wed, 16 Feb 2005 18:25:27 -0000 From: McDonald, Andrew <andrew.mcdonald(a)roke.co.uk> To: nsis-imp(a)ietf.org Hi all, In advance of any interop testing, it seems sensible to make sure we're all using the same set of numbers for object types, etc. So, here are those that we currently use in our implementation, and propose we use for any packets we exchange in Minneapolis. TLV Types ========= T_MRI_TLV = 0 T_SESSION_TLV = 1 T_NODEADDR_TLV = 2 T_STACK_TLV = 3 T_QCOOKIE_TLV = 4 T_RCOOKIE_TLV = 5 T_LIFE_TLV = 6 T_NAT_TLV = 7 T_NSLP_DATA_TLV = 8 Stack Proposal Protocol Numbers =============================== TCP = 1 TLS = 2 Other Constants =============== GIMPS_PORT = 4 RAO_NUMBER = 0 GIMPS_VERSION = 1 RTG_METHOD_PATH_COUPLED = 0 best regards, Andrew _______________________________________________ NSIS-imp mailing list NSIS-imp(a)lists.ietf.org https://www1.ietf.org/mailman/listinfo/nsis-imp

1 0

Idea for draft about implementation of a ping client
by Ingo Juchem 14 Feb '05

14 Feb '05

Hallo all, I was thinking of an idea how to test the cleo-projects' implementation of GIMPS and as Bernd asked for a ping client.... Attached you see an alpha version of the draft (which is my first one,btw and wouldn't have been possible without Xiaomings and Sebastians help so please bare with me). Any comments and suggestions are highly appreciated! Please criticise as much as possible ;P However, there are several points that need to be addressed: 1. This draft will not be published without your approval. At the moment there only exists an intention to publish it. 2. This idea needs support through an implementation of the Ping Client so we need to confirm somebody does that (Bernd, Sebastian, me?) 3. Maybe this rather simple approach does not fulfill cleos requirement of a diagnostic tool, so if it's not useful we can just drop it 4. Is this a good way for testing after all? Is it really needed at all? What could be added? So please feel free to add anything you might think could be useful! Regards, Ingo

3 2

[Fwd: New Internet draft on "Ping test tool for GIMPS"]
by Ingo Juchem 14 Feb '05

14 Feb '05

Hi everybody, Xiaoming has shortly reviewed it and then I submitted the doc as a draft to IETF. Thanks for your attention and comments ! Regards, Ingo -------- Original Message -------- Subject: New Internet draft on "Ping test tool for GIMPS" Date: Mon, 14 Feb 2005 15:00:00 +0100 From: Ingo Juchem <ijuchem(a)cs.uni-goettingen.de> To: internet-drafts(a)ietf.org Dear Internet-draft editor, We would like to submit the initial version of an Internet Draft "A stateless Ping Client for simple tests of GIMPS implementations", which is related to the work in the NSIS WG. Please find the Internet draft in the attachment, or the following URL: http://user.informatik.uni-goettingen.de/~ijuchem/draft-juchem-nsis-ping-to… Title: A stateless Ping Client for simple tests of GIMPS implementations Abstract: When implementing signaling protocols such as CASP or GIMPS, implementers need a way to test the functionality and measure the performance of their own implementations. In this document, we try to provide a sketch for such a testing tool, a simple, stateless Ping Client, which works similar to ICMP Ping messages. This tool is able to traverse a path from a source to a destination along signaling- aware network nodes and collect various data that could be useful for identifying each node it is passing. Authors: Ingo Juchem, Sebastian Willert and Xiaoming Fu Best regards, Ingo Juchem

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Nsis_Imp February 2005