Hi All, ( 1 ) Please refer section 4.1.6.3. of RFC 4235, which states the following about the Session Description Element:
" It has a single attribute, "type", which indicates the MIME media type of the session description. To avoid repeating session description information in each request, the subscriber can assume that the session description is the same as in previous notifications if no session description element is present in the corresponding local or remote element. " We have the following query w.r.to the above description: The session is established through SDP offer/answer and the MIME media type of the session description would be "application". Further, this MIME media type will NOT change, by further offer/answer procedures due to Re-Invite and Update. Hence, when and how is this MIME media type expected to change ? ( 2 ) Section :3.7.2. of RFC 4235 : Applying the State Machine (last paragraph) states : " The notifier SHOULD generate a NOTIFY request on any change in the characteristics associated with the dialog. Since these include Contact URIs, Contact parameters, and session descriptions, receipt of re-INVITEs and UPDATE requests [3] that modify this information MAY trigger notifications. " If the MIME media type of the session description could be changed by re-INVITEs and UPDATEs, could receipt of RPR also change this and trigger notifications ? thanks in advance, regards, rhari ! *********************** FSS-Unclassified *********************** "DISCLAIMER: This message is proprietary to Flextronics Software Systems (FSS) and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. FSS accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus." _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
