RE: [Sip] Doubts in SIP/SDP

"Francois Audet" <audet@nortelnetworks.com> Fri, 10 December 2004 03:13 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14440 for <sip-web-archive@ietf.org>; Thu, 9 Dec 2004 22:13:21 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcbKl-0001Qi-Sc for sip-web-archive@ietf.org; Thu, 09 Dec 2004 22:20:44 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ccb75-0007Rf-FY; Thu, 09 Dec 2004 22:06:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ccb39-0006NU-N1 for sip@megatron.ietf.org; Thu, 09 Dec 2004 22:02:31 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13647 for <sip@ietf.org>; Thu, 9 Dec 2004 22:02:30 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcbAD-0001Fl-22 for sip@ietf.org; Thu, 09 Dec 2004 22:09:52 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25]) by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id iBA31RD24822; Thu, 9 Dec 2004 22:01:27 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19) id <YFGT3VQL>; Thu, 9 Dec 2004 22:01:28 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF012851E7@zrc2hxm0.corp.nortel.com>
From: Francois Audet <audet@nortelnetworks.com>
To: 'Dean Willis' <dean.willis@softarmor.com>, 'Anil Bollineni' <ABollineni@juniper.net>
Subject: RE: [Sip] Doubts in SIP/SDP
Date: Thu, 09 Dec 2004 22:01:10 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 27ec2ff0f5c3b18b49c722f4f1748838
Cc: "'sip@ietf.org'" <sip@ietf.org>, "'sip-implementors@cs.columbia.edu'" <sip-implementors@cs.columbia.edu>
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1946463459=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 343d06d914165ffd9d590a64755216ca

Of course with forking, this gets really interesting.

> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of Dean Willis
> Sent: Thursday, December 09, 2004 14:31
> To: Anil Bollineni
> Cc: sip@ietf.org; sip-implementors@cs.columbia.edu
> Subject: Re: [Sip] Doubts in SIP/SDP
> 
> 
> 
> BTW, this is a lovely "sip-implementors" list question.
> 
> Answers herein are my opinion, and may not mesh with some 
> particularly 
> strict interpretations. On the other hand, one can refer to 
> the Postel 
> axiom "be liberal with what you accept" (or however he said 
> that . . .)
> 
> More detailed procedures are available in 
> draft-ietf-sipping-early-media-02.txt, which I believe has been 
> approved by the IESG and is in the RFC Editor queue.
> 
> On Dec 7, 2004, at 6:10 PM, Anil Bollineni wrote:
> 
> > Hi,
> >   Thanks for the response. I have a basic question, considering 3
> > views.
> >
> > 1. Suppose terminating endpoint does not support 183, and sends the 
> > early media for IVR, should  UAC, play the media treated as 
> if early 
> > media.
> >
> 
> yes.
> 
> > 2. Any case the terminating endpoint must support 183 and send the
> > media
> > after it sends. The 100rel is optional, in this case the 
> sequence of 
> > 183
> > and early media is not guaranteed. Should UAC prepare media 
> > irrespective
> > of call progress message?
> >
> 
> The UAC should play any media it receives that is consistent with the 
> SDP it offered in the INVITE.
> 
> The exception to this case is described in the early media draft:
> 
>          Note that, in some situations, the UAC does need to receive
>          the answer before being able to play any media. UAs in such
>          a situation (e.g., QoS, media authorization or media
>          encryption is required) use preconditions to avoid media
>          clipping.
> 
> The use of preconditions is discussed in RFC 3312.
> 
> > 3. In case of 100Rel calling UA requires the option 100rel, should
> > terminating endpoint MUST send always after PRACK is received?
> >
> 
> That's debatable. One might be inclined to suspect that the 
> calling UA 
> has issues with "really early media" in this case, and the UAS SHOULD 
> hold off until receiving the PRACK. I don't know that MUST 
> applies, as 
> one can reasonably expect that SOME UASs might not delay, so the 
> calling UA MUST be prepared to deal with the consequences of a called 
> UA that responds with media before sending an SDP answer.
> 
> 
> 
> > Specifically, if we want deploy a firewall between originating and
> > terminating endpoints, should we allow early media after 
> INVITE without
> > 183 is being seen?
> >
> 
> yes.
> 
> 
> --
> Dean
> 
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org 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 sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip