prag 1103 | 4 Apr 09:46 2012
Picon

What is the correct approach to parser MSRP messages.

Hello Group,

I hope it's ok to ask an implementation related query in this mailing group.

UA1 is sending 200ok followed by success report, one after the other using two different tcp send calls,
however towards UA2 both 200ok and success report are read jointly in a single read to buffer.

Is this an expected behavior. if yes, what is the best approach to parse the messages
 
Thanks & Regards.
_______________________________________________
Simple mailing list
Simple <at> ietf.org
https://www.ietf.org/mailman/listinfo/simple
Iñaki Baz Castillo | 5 Apr 11:43 2012
Picon

Re: What is the correct approach to parser MSRP messages.

2012/4/4 prag 1103 <prag1103 <at> gmail.com>:
> I hope it's ok to ask an implementation related query in this mailing group.
>
> UA1 is sending 200ok followed by success report, one after the other using
> two different tcp send calls,
> however towards UA2 both 200ok and success report are read jointly in a
> single read to buffer.
>
> Is this an expected behavior. if yes, what is the best approach to parse the
> messages

Anyone. TCP is not a message boundary transport protocol (as UDP or
SCTP are) so you must *never* rely on receiving a complete/single
application level message in a TCP packet. You could receive a TCP
packet with an incomplete application message so you must wait for a
new TCP packet containing the rest.

That is TCP. Regards.

PS: However this question fits better in sip-implementor maillist.

--

-- 
Iñaki Baz Castillo
<ibc <at> aliax.net>
_______________________________________________
Simple mailing list
Simple <at> ietf.org
https://www.ietf.org/mailman/listinfo/simple
internet-drafts | 17 Apr 12:24 2012
Picon

I-D Action: draft-ietf-simple-msrp-cema-04.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item
of the SIP for Instant Messaging and Presence Leveraging Extensions Working Group of the IETF.

	Title           : Connection Establishment for Media Anchoring (CEMA) for the Message Session Relay Protocol (MSRP)
	Author(s)       : Christer Holmberg
                          Staffan Blau
                          Eric Burger
	Filename        : draft-ietf-simple-msrp-cema-04.txt
	Pages           : 21
	Date            : 2012-04-17

   This document defines a Message Session Relay Protocol (MSRP)
   extension, Connection Establishment for Media Anchoring (CEMA).
   Support of the extension is optional.  The extension allows
   middleboxes to anchor the MSRP connection, without the need for
   middleboxes to modify the MSRP messages, and thus also enables a
   secure end-to-end MSRP communication in networks where such
   middleboxes are deployed.  The document also defines a Session
   Description Protocol (SDP) attribute, 'msrp-cema', that MSRP
   endpoints use to indicate support of the CEMA extension.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-simple-msrp-cema-04.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-simple-msrp-cema-04.txt

internet-drafts | 18 Apr 22:13 2012
Picon

I-D Action: draft-ietf-simple-simple-07.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item
of the SIP for Instant Messaging and Presence Leveraging Extensions Working Group of the IETF.

	Title           : SIMPLE made Simple: An Overview of the IETF Specifications for Instant Messaging and Presence
using the Session Initiation Protocol (SIP)
	Author(s)       : Jonathan Rosenberg
	Filename        : draft-ietf-simple-simple-07.txt
	Pages           : 15
	Date            : 2012-04-18

   The IETF has produced many specifications related to Presence and
   Instant Messaging with the Session Initiation Protocol (SIP).
   Collectively, these specifications are known as SIMPLE - SIP for
   Instant Messaging and Presence Leveraging Extensions.  This document
   serves as a guide to the SIMPLE suite of specifications.  It breaks
   them up into categories and explains what each is for and how they
   relate to each other.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-simple-simple-07.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-simple-simple-07.txt

Gmane