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

Hadriel Kaplan <HKaplan@acmepacket.com> Thu, 20 October 2011 03:30 UTC

Return-Path: <HKaplan@acmepacket.com>
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 4EDF621F84CF for <rtcweb@ietfa.amsl.com>; Wed, 19 Oct 2011 20:30:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.329
X-Spam-Level:
X-Spam-Status: No, score=-2.329 tagged_above=-999 required=5 tests=[AWL=-0.030, 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 m-qF2B-5LFgt for <rtcweb@ietfa.amsl.com>; Wed, 19 Oct 2011 20:30:51 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by ietfa.amsl.com (Postfix) with ESMTP id C3BF321F84CE for <rtcweb@ietf.org>; Wed, 19 Oct 2011 20:30:51 -0700 (PDT)
Received: from MAIL2.acmepacket.com (10.0.0.22) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 19 Oct 2011 23:30:50 -0400
Received: from MAIL1.acmepacket.com ([169.254.1.230]) by Mail2.acmepacket.com ([169.254.2.157]) with mapi id 14.01.0270.001; Wed, 19 Oct 2011 23:30:51 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Cullen Jennings <fluffy@cisco.com>
Thread-Topic: [rtcweb] Why SDP answer needs and ack … was Re: SDP Offer/Answer draft-jennings-rtcweb-signaling
Thread-Index: AQHMjtipQ13+gx0IuEeO9cXwfJxoKA==
Date: Thu, 20 Oct 2011 03:30:49 +0000
Message-ID: <3D0CC711-6A0D-40CC-84AD-9F15B49BCCC1@acmepacket.com>
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>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [216.41.24.34]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <554D81AE2BCE344299E1A94C25C9C907@acmepacket.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
Cc: Jonathan Rosenberg <jonathan.rosenberg@skype.net>, "<rtcweb@ietf.org>" <rtcweb@ietf.org>, "<public-webrtc@w3.org>" <public-webrtc@w3.org>
Subject: Re: [rtcweb] Why SDP answer needs and ack … was Re: 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:30:52 -0000

On Oct 19, 2011, at 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 :-) 

Ummm... you do realize the number one generator of offerless INVITEs by a fairly wide margin is a popular product made by a company on Tasman Drive in San Jose, with a domain name like the one in your email address, right?  
:)

Or at least it was the last time I checked the Billboard charts for Top-10 offerless INVITE generators.

-hadriel