Re: [rtcweb] SIP Glare - Re: Minimal SDP negotiation mechanism

Matthew Kaufman <matthew.kaufman@skype.net> Thu, 22 September 2011 19:57 UTC

Return-Path: <matthew.kaufman@skype.net>
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 7C09C1F0C46 for <rtcweb@ietfa.amsl.com>; Thu, 22 Sep 2011 12:57:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.713
X-Spam-Level:
X-Spam-Status: No, score=-5.713 tagged_above=-999 required=5 tests=[AWL=0.886, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 ZFK2Q0AvrL0K for <rtcweb@ietfa.amsl.com>; Thu, 22 Sep 2011 12:57:29 -0700 (PDT)
Received: from mx.skype.net (mx.skype.net [78.141.177.88]) by ietfa.amsl.com (Postfix) with ESMTP id D0CCD1F0C3C for <rtcweb@ietf.org>; Thu, 22 Sep 2011 12:57:28 -0700 (PDT)
Received: from mx.skype.net (localhost [127.0.0.1]) by mx.skype.net (Postfix) with ESMTP id 4DA03170E; Thu, 22 Sep 2011 21:59:59 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=skype.net; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=mx; bh=PEA2ObTBPpjNSN A+gOJrnxlpPoM=; b=ugI/+XX5j3wiNmvULG7xgh45tOrAKttiTmdYfJvefNLh6U mWssiay39gZc0dGgJz17V6sKlq+ZdpQOaYCKGnh3QEWB0SbqvpMjJTakl+iEgCjb 7iNo3rtDTD9GMHa8H6Pda73ZWi2fNU/FLQ7JRCYQwaa2dOLPKfnqFXqG4maJU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=skype.net; h=message-id:date:from :mime-version:to:cc:subject:references:in-reply-to:content-type: content-transfer-encoding; q=dns; s=mx; b=gwG6023K00hahzcA30rws2 WkJEzpDGNIpBEVsE14vA8KqGWd3Fc7yBD//4Cfga1jCLA60pjnSMRnypBo1nRKMW rC2UOL/ERUKl8qZ2biKe0Uqksq/CKu7DMF08mC/Cv6qIuAKdyktoVYDMkF7YZS0t 6CEjL/6ImHebT56kn+Mas=
Received: from zimbra.skype.net (zimbra.skype.net [78.141.177.82]) by mx.skype.net (Postfix) with ESMTP id 4C0427F6; Thu, 22 Sep 2011 21:59:59 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by zimbra.skype.net (Postfix) with ESMTP id 271B01678D03; Thu, 22 Sep 2011 21:59:59 +0200 (CEST)
X-Virus-Scanned: amavisd-new at lu2-zimbra.skype.net
Received: from zimbra.skype.net ([127.0.0.1]) by localhost (zimbra.skype.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Whesn3S0XGUr; Thu, 22 Sep 2011 21:59:58 +0200 (CEST)
Received: from Matthew-Kaufman-Air.local (50-0-2-20.static.sonic.net [50.0.2.20]) by zimbra.skype.net (Postfix) with ESMTPSA id EC10F1678D02; Thu, 22 Sep 2011 21:59:57 +0200 (CEST)
Message-ID: <4E7B93C3.1090101@skype.net>
Date: Thu, 22 Sep 2011 13:00:03 -0700
From: Matthew Kaufman <matthew.kaufman@skype.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0.2) Gecko/20110902 Thunderbird/6.0.2
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
References: <4E777500.5030201@alvestrand.no> <4E78940C.4040405@ericsson.com> <ED2DB00E-A64B-405F-96AC-2269258F6FFC@cisco.com> <4E799ECC.8030306@ericsson.com> <DB6B2796-9762-47CA-9A45-62476146DF04@cisco.com> <57CCCB06-F4C3-4E23-AF09-B7B5285C5FAE@phonefromhere.com> <F7758EE8-9D36-4999-86E4-21DB1E6F217D@cisco.com> <4E7B8D9D.8060303@skype.net> <46B4E074-69C8-4B25-8348-F6951FF9725F@cisco.com>
In-Reply-To: <46B4E074-69C8-4B25-8348-F6951FF9725F@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] SIP Glare - Re: Minimal SDP negotiation mechanism
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, 22 Sep 2011 19:57:29 -0000

On 9/22/11 12:53 PM, Cullen Jennings wrote:
> Could you'd like to elaborate on how it works when one of the sides is an SIP endpoint, or we the two endpoint are at different domains that are federated?

The server uses its knowledge of the web browser capabilities to 
generate an SDP offer and/or reply with an SDP answer as appropriate and 
then requests that the browser begin sending and/or prepare for 
receiving media as appropriate.

This is exactly the same answer as "how does it work when you have an 
MGCP (or Skinny) device and you want to talk to a SIP endpoint or the 
other endpoint is at the far side of a SIP trunk"

Matthew Kaufman