The one advantage that I can see is the ability to represent a standardized serial format for sip messages so as to enable pattern matching on partially formatted sip messages. The sip protocol call flow can be represented by a causally ordered sequence of such partially specified messages and from that a correctness checker can be generated. I had got started along those lines but got diverted.

For example,

<SIPREQUEST
   method = INVITE
  >
  <REQUEST_URI
         userName = *
    >
    <ADDRESS
         hostName = "*.nist.gov"
     />
  </REQUEST_URI>
</SIPREQUEST>

Would match any sip request that had a method of INVITE originating from nist.gov domain.

This can be used to encode call flows. Here is a paper along those lines - http://www-x.antd.nist.gov/proj/iptel/papers/whitepaper.pdf


Hope this helps.


Regards

Ranga.

Ivan Smolcic wrote:

Has there been any work done with encoding SIP messages with XML? If there has, please tell me where I can find out more about it.
What are the advantages of encoding SIP messages with XML instead of plain text?


_________________________________________________________________
STOP MORE SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail


_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors


--
M. Ranganathan


Advanced Networking Technologies Divsion,
National Institute of Standards and Technology (NIST),
100 Bureau Drive, Stop 8920, Gaithersburg, MD 20899. tel:301 975 3664 , fax:301 590 0932 http://w3.antd.nist.gov/
Advanced Networking Technologies For the People!




_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

Reply via email to