[rtcweb] URIs for rtcweb "calls"

Ted Hardie <ted.ietf@gmail.com> Fri, 12 August 2011 17:46 UTC

Return-Path: <ted.ietf@gmail.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 2D8C211E808C for <rtcweb@ietfa.amsl.com>; Fri, 12 Aug 2011 10:46:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 ZLdZQvqhcYEN for <rtcweb@ietfa.amsl.com>; Fri, 12 Aug 2011 10:46:52 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by ietfa.amsl.com (Postfix) with ESMTP id 9441611E808B for <rtcweb@ietf.org>; Fri, 12 Aug 2011 10:46:52 -0700 (PDT)
Received: by qyk35 with SMTP id 35so1894190qyk.10 for <rtcweb@ietf.org>; Fri, 12 Aug 2011 10:47:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=Tr9HORnD77ZtJw6gEmZaM33tgF6rZImjAgokZuJ1asE=; b=CQo6oxhBM7CQUH8h/k/DKKfKWVvMokWfySJ0LDTtupNAwwjDpPwWjDdVPl6zvzppOt xrYn288LKRv8xS8KQBiMtM56sljW02S137Fvfjn7CEBDEtELCQoRDfVOMUuFxin3Eyl3 /Ede01cpX+szFK6eNLbpWUgPu8tBjcsIeXNnA=
MIME-Version: 1.0
Received: by 10.229.131.159 with SMTP id x31mr830419qcs.193.1313171250067; Fri, 12 Aug 2011 10:47:30 -0700 (PDT)
Received: by 10.229.249.201 with HTTP; Fri, 12 Aug 2011 10:47:30 -0700 (PDT)
Date: Fri, 12 Aug 2011 10:47:30 -0700
Message-ID: <CA+9kkMBFwX9KiPDGwOZaANJuMO6J_wh06CPt+9+=y6iJL-hzXA@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: rtcweb@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [rtcweb] URIs for rtcweb "calls"
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: Fri, 12 Aug 2011 17:46:53 -0000

In one of the use cases we've discussed, there is an advertisement
placed on a page with something like "click here to chat with someone
now".  In some of the discussion in Quebec city, we circled around the
question of who did the job of connecting the user when there was a
click.  In a side discussion on that topic, Cullen, ekr, and I talked
about possibly making that explicit by using a uri structured along
these lines:

scheme: (e.g. rtw)
authority: the entity which will act as the signaling service for
setting up the session.
path-component-1: the entity to which you will be connected
path-component-2: a token used in the media path to assure you that
media is coming from someone with access to the uri

rtw://outsourced-video.example.com/custchat.carmaker.example;token=2342342433

I don't want to delve into the UI aspects of this too much, but the
presumption I was working under was that if someone clicked on such a
link, it would open a new context (e.g. new browser window), and start
a session. path-component one could be something meaningful only
within a specific context:

rtw://dating-site.example/prospective13344;token=444322111

Alternatively, it could be also meaningful in an external security
context, possibly because custchat.carmaker.example will appear in a
certificate in a known place during the media exchange.  It could also
be a reference to something like a presentity, where the presence
infrastructure provides an out-of-band mechanism for confirming
identity.

Do others think defining something like this would be useful?

If so, would the authority section be a host pointer or an xmpp-style service?
Does the format of path-compenent-1 need to be fixed, or can it be
service-dependent?
Would a token be a pawn-ticket style URI, or would the whole URI be
something that could be bookmarked and re-used?

regards,

Ted