Re: [rtcweb] Why SDP answer needs and ack … was Re: SDP Offer/Answer draft-jennings-rtcweb-signaling

Randell Jesup <randell-ietf@jesup.org> Thu, 20 October 2011 03:12 UTC

Return-Path: <randell-ietf@jesup.org>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF71811E80B6 for <rtcweb@ietfa.amsl.com>; Wed, 19 Oct 2011 20:12:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.389
X-Spam-Level:
X-Spam-Status: No, score=-2.389 tagged_above=-999 required=5 tests=[AWL=-0.090, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4riGxTHn1STA for <rtcweb@ietfa.amsl.com>; Wed, 19 Oct 2011 20:12:40 -0700 (PDT)
Received: from r2-chicago.webserversystems.com (r2-chicago.webserversystems.com [173.236.101.58]) by ietfa.amsl.com (Postfix) with ESMTP id 68CDC11E80B2 for <rtcweb@ietf.org>; Wed, 19 Oct 2011 20:12:40 -0700 (PDT)
Received: from pool-173-49-141-165.phlapa.fios.verizon.net ([173.49.141.165] helo=[192.168.1.12]) by r2-chicago.webserversystems.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <randell-ietf@jesup.org>) id 1RGj3f-0007OC-L4 for rtcweb@ietf.org; Wed, 19 Oct 2011 22:12:39 -0500
Message-ID: <4E9F908B.9060703@jesup.org>
Date: Wed, 19 Oct 2011 23:07:55 -0400
From: Randell Jesup <randell-ietf@jesup.org>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <15B0E3AD-3086-499A-8E79-7AE58B3376C4@cisco.com> <CALiegf=EXfNAfRDGiohz3aSqmZzsDDXbE=DRNX0gZTXz7x4+Yg@mail.gmail.com> <DA064BE5-9C95-4B87-B1D9-CD3FD1E0810D@cisco.com> <CALiegfn_DDxKwbq1gTeyDo+t=+oEyAy6eUS3sJ36Tbyo_Ffnww@mail.gmail.com> <05C007AF-7462-4A08-894D-9D4DD0569105@cisco.com>
In-Reply-To: <05C007AF-7462-4A08-894D-9D4DD0569105@cisco.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - r2-chicago.webserversystems.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jesup.org
X-Source:
X-Source-Args:
X-Source-Dir:
Subject: Re: [rtcweb] =?windows-1252?q?Why_SDP_answer_needs_and_ack_=85_was_Re?= =?windows-1252?q?=3A__SDP_Offer/Answer_draft-jennings-rtcweb-signaling?=
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Oct 2011 03:12:41 -0000

On 10/19/2011 8:43 PM, Cullen Jennings wrote:
>
> I guess the question I am thinking about is how important is this use case. I'm a bit of
 > the fence on the topic.  The primary use of INVITE with no offer is 
when doing a gateway
 > to some forms of  H.323. It seem the odds of a gateway from RTCWeb to 
SIP to H323 is
 > pretty low so I have not been thinking about how to deal with
 > INVITE with no
 > offer much.  I should think about it more but too few hours in the 
day :-)

The primary use of bare INVITE in SIP I've seen is for an SBC to force a 
renegotiation by the two sides:

A                        SBC                        B
| <-------------------- media --------------------> |
| <--- INVITE w/o SDP --- |                         |
| ----- 200 OK w/OFFER -> |                         |
|                         | ------ INVITE w/OFFER-> |
|                         | <--- 200 OK w/ANSWER -- |
| <---- ACK w/ANSWER ---- |                         |
|                         | -------- ACK ---------> |
| <--------------------- media -------------------> |

This can let the SBC modify things in the process (like move media
relaying to a new IP/port, change hold state), and other 3PCC things.


-- 
Randell Jesup
randell-ietf@jesup.org