Subject: RE: [Sip] outbound-06: Question on TCP demultiplexing STUN and SIPtraffic

From: "Attila Sipos" <[email-masked]>
Date: Fri, 24 Nov 2006 12:30:11 -0000

1. (obvious but) only look STUN response for it
   when you've sent a STUN request.

2. There is a STUN magic cookie
   (not in RFC3489 but in http://www.heise.de/netze/rfc/drafts/draft-ietf-behave-rfc3489bis-05.shtml)

3. There is your transaction ID.

Regards,

Attila

>> -----Original Message-----
>> From: Vavilapalli Srikanth-A19563 [mailto:[email-masked]]
>> Sent: 24 November 2006 12:14
>> To: SIP WG
>> Cc: Cullen Jennings; Rohan Mahy
>> Subject: [Sip] outbound-06: Question on TCP demultiplexing STUN and
>> SIPtraffic
>> 
>> 
>> Hi
>> 
>> Section 8 of the draft says: For TCP or TLS over TCP flows, 
>> determining
>> if the first octet of the next message in a stream is SIP or STUN is
>> still straightforward.  As with any stream-based protocol,
>> implementations need to be prepared to receive STUN messages 
>> which cross
>> a stream buffer boundary, and SIP and STUN messages which 
>> share the same
>> stream buffer.
>> 
>> Can anyone please elaborate more on demultiplexing of SIP and STUN
>> message in case of TCP? If the STUN message is in middle of the read
>> buffer, how can we demux these packets?
>> 
>> Regards
>> Srikanth
>> 
>> 
>> _______________________________________________
>> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
>> This list is for NEW development of the core SIP Protocol
>> Use [email-masked] for questions on current sip
>> Use [email-masked] for new developments on the application of sip
>> 

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [email-masked] for questions on current sip
Use [email-masked] for new developments on the application of sip