Re: [rtcweb] Current state of signaling discussion

Cullen Jennings <fluffy@cisco.com> Tue, 18 October 2011 23:35 UTC

Return-Path: <fluffy@cisco.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 C9D4421F85AE for <rtcweb@ietfa.amsl.com>; Tue, 18 Oct 2011 16:35:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.549
X-Spam-Level:
X-Spam-Status: No, score=-106.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 yvTXPKZOsvqM for <rtcweb@ietfa.amsl.com>; Tue, 18 Oct 2011 16:35:41 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 2884B21F841D for <rtcweb@ietf.org>; Tue, 18 Oct 2011 16:35:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=996; q=dns/txt; s=iport; t=1318980941; x=1320190541; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=mW+01sv0LUA+IFUtZ5Ehto0VzkIf/zXwvF7vgiblbO0=; b=I1Fd7Yv+IODAcHHFKMoteBQkOwzXsRyyZrcOSLbIjdr/z+p9Oawu55pZ j3vlsAkmlbwoGmIziMSespFIFXKtgIQAMGg2U1MCZk9FExBMJegdbB3zY ucYPT01PMA/TFD3v8OoMApoXvzD0rSj+P/J3txXAqKS31vS+jYsTLyCsP 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAMYMnk6rRDoJ/2dsb2JhbAA7CahwgQWBbgEBAQMBEgEnPwULCw44VwY1h16XbAGePYRtgk1hBIgCi3uRdg
X-IronPort-AV: E=Sophos;i="4.69,368,1315180800"; d="scan'208";a="8447737"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-1.cisco.com with ESMTP; 18 Oct 2011 23:35:40 +0000
Received: from dhcp-171-70-217-213.cisco.com (dhcp-171-70-217-213.cisco.com [171.70.217.213]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p9INZe3m021246; Tue, 18 Oct 2011 23:35:40 GMT
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <F89E752A-820B-4C41-BE14-15B358BFA267@acmepacket.com>
Date: Tue, 18 Oct 2011 16:35:39 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <3710890A-04D8-4050-A090-FE93DCD073FD@cisco.com>
References: <4E9D773A.4010705@ericsson.com> <E7E0C331-9943-444F-9D42-782DAD6A7FF3@acmepacket.com> <CABcZeBP0v=q7sH4G4Ehvx7x5b_tyoukS1N0EOm1Ji8URNOeDUw@mail.gmail.com> <F89E752A-820B-4C41-BE14-15B358BFA267@acmepacket.com>
To: Hadriel Kaplan <HKaplan@acmepacket.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>, "rtcweb-chairs@tools.ietf.org" <rtcweb-chairs@tools.ietf.org>
Subject: Re: [rtcweb] Current state of signaling discussion
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: Tue, 18 Oct 2011 23:35:41 -0000

On Oct 18, 2011, at 14:05 , Hadriel Kaplan wrote:

> BUT, for an actual session protocol to work for even a gaming app, you need to do the following:
> 1) determine a target for the ROAP message (ie, who's this OFFER going to in the end?)
> 2) define how that target identity is conveyed (ie, how does the web server know which browser to give this ROAP OFFER to?)
> 3) define a source identity model, possibly with authentication (ie, who are you?)
> 4) define how the source identity is conveyed (ie, how does the server/far-end-browser know who's calling?)
> 5) define a end-of-session indication
> 6) define a keep-alive mechanism, for when the far end goes away silently and (5) doesn't apply

I've thought a bunch about this - In addition to those, I think we need a way to cache state, sort of like cookie or something. That gets passed back at the right time. That type of thing makes it much easier for the web-service to keep track of things.