In section 5.7 we have:
 
5.7.  Connection Data ("c=")

      c=<nettype> <addrtype> <connection-address>

each of the components between the brackets is mandatory
 
"c=IN IP4 " is not allowed but "c=IN IP4 0.0.0.0" would be ok.
 
Regards,
Attila
 
 
 
________________________________

From: Vishwas Bharadwaj [mailto:[EMAIL PROTECTED] 
Sent: 18 June 2008 15:18
To: Attila Sipos
Cc: [email protected]
Subject: Re: [Sip-implementors] SIP message with SDP content with
differentscenarios of connection field.


Thanks attila, Where can i find more specifics of it being an error
mentioned.. i mean is it in any of the RFC.

RFC 4566(SDP) mentions


"In general, the "o=" field serves as a globally unique identifier for

   this version of this session description, and the subfields excepting
   the version taken together identify the session irrespective of any
   modifications."


I was jez wondering if connection field can still exist without an IP
Address, as the Origin field is mandatory and serves as a global
identifier for the session. though i cant really think of a Use case
currently :(....... 

br,
Vish


  



On Wed, Jun 18, 2008 at 7:24 PM, Attila Sipos
<[EMAIL PROTECTED]> wrote:



        it's an error.  (it is not valid SDP)
        



        -----Original Message-----
        From: [EMAIL PROTECTED]
        [mailto:[EMAIL PROTECTED] On
Behalf Of
        Vishwas Bharadwaj
        Sent: 18 June 2008 14:50
        To: [email protected]
        Subject: [Sip-implementors] SIP message with SDP content with
        differentscenarios of connection field.
        
        Hi all,
        
        Can a SDP content have a Connection field without an IP
address.... to
        be more precise...
        Case 1: "c=IN IP4 192.168.1.2 " (Normal scenarion) Case 2: "c=IN
IP4 "
        (No  I P address is mentioned)
        
        Shud an SDP Parser Raise an Error on Case 2 or shud it parse the
Message
        and pass on to stack as an Valid SDP Content.
        
        Please correct me if there'z any info i have wrongly
interpreted....
        
        best regards,
        Vishwas
        
        _______________________________________________
        Sip-implementors mailing list
        [email protected]
        
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
        


_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to