[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: protocol standards that use formal specification of behavior?

Dear Eric,


An example of a standard for the formal description of protocols is
LOTOS.  The ISO standard
MailScanner has detected a possible fraud attempt from "calendar.elex.be" claiming to be http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=16258
is an expensive document, but on the web a huge amount of literature can be
found.

If this is not what you or Alan Grover are looking for, please let me know.

With best regards,

Raymond
 
PS.
 
Personnally I find CSP a bit too primitive to describe protocols as one needs to expres everything in low level channel communication and at least two processes. I am still looking for a tool or way that takes a whole protocol (like expressed in a MSC) as a single interaction between concurrent entities.
 
Eric

 

----------------------  FROM : --------------------------
   Eric.Verhulst@xxxxxxxxxxxxxxxxxxxxxx
   Skype me at: ericverhulstskype
   Mob. +32 477 608339
   Systematic Systems Development Methodologies
   Trustworthy Embedded Components
   http://www.OpenLicenseSociety.org
-----------------------------------------------------------
" "Concept" is a vague concept", L. Wittgenstein

 

From: owner-occam-com@xxxxxxxxxx [mailto:owner-occam-com@xxxxxxxxxx] On Behalf Of Alan Grover
Sent: Wednesday, January 24, 2007 1:16 AM
To: occam-com@xxxxxxxxxx; java-threads@xxxxxxxxxx
Subject: Re: protocol standards that use formal specification of behavior?

Thanks for all the comments so far! 

I'm working on SAE AS-4, the migration of JAUS (jauswg.org) to SAE.  It is basically an application level message passing standard that has suffered from a lack of networking/protocol experience.  To date it is mostly a message format standard, but they understand the benefits of adding a formal description of behavior, and that is currently work in progress.  It is an xml-based specification, currently called the Jaus Services Interface Definition Language (JSIDL), although the name has been a moving target.

The current draft has a behavior specification based on the State Machine Compiler, and it is pretty weak (it essentially ignores concurrency within a service; somebody decided simple state machines were best because 'people are familiar with them').

A colleague of mine is set to propose something based on BPEL/BPMN but adapted to our needs.

I've offered to provide a CSP-based behavior schema, and it would be helpful to be able to point out examples of similar directions in other protocols.  Application-level SOA type protocols would be ideal, but anything in the network protocol area is helpful, especially if it became a published standard.

Alan