Subject: [Sip] Help: "About multiple early-session sdp body in a request"

From: [email-masked]
Date: Wed, 13 Dec 2006 11:13:48 +0800

Dear Sip Group,

     There encounters some questions when I read RFC 3959 and RFC 3960 
which refer to the Early-Session , that is
 
       1. "Is it available to include multiple early-session sdp body in a 
request?"

    for example:
        Content-Type: multipart/mixed; boundary="boundary1"
        Content-Length: 401

        --boundary1
           Content-Type: application/sdp
           Content-Disposition: early-session

           v=0
           o=Bob 2890844725 2890844725 IN IP4 host1.example.org
           s=
           c=IN IP4 192.0.2.2
           t=0 0
           m=audio 30000 RTP/AVP 0

       --boundary1
          Content-Type: application/sdp
          Content-Disposition: early-session

          v=0
          o=Bob 2890844714 2890844714 IN IP4 host2.example.org
          s=
          c=IN IP4 192.0.2.3
          t=0 0
          m=audio 30002 RTP/AVP 0

       --boundary1--

     2. "How can a UAS decide to handle a early-session sdp ,and not to 
handle other early-session sdps when     UAS receive a request with 
multiple early-session sdps?"

    This question arises from the following scene:
    Before A and B establish communication，
    (1) AS-1 wants to send media to B 
    (2) AS-2 wants to send media to A

    To reach the goal , some principles should obey:
    (1)precondtion defined in RFC 3312
    (2)Early-Session defined in RFC 3959, RFC 3960

    The red circles mark special processing.

--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.
_______________________________________________
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