Re: [rtcweb] Payload Types assignments was Re: SV: [mmusic] WGLC of draft-ietf-rtcweb-use-cases-and-requirements-11

Martin Thomson <> Fri, 11 October 2013 11:32 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DA6CF21E80F3 for <>; Fri, 11 Oct 2013 04:32:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id UL5Hh2Qidgel for <>; Fri, 11 Oct 2013 04:32:00 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:400c:c05::232]) by (Postfix) with ESMTP id 3259D21E80EB for <>; Fri, 11 Oct 2013 04:32:00 -0700 (PDT)
Received: by with SMTP id hn3so900406wib.17 for <>; Fri, 11 Oct 2013 04:31:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=VSPN0XNFNVfiqzA3IOlDwC+4R1o2wLlC1ipwCq2+UPs=; b=nFtYh5bpp4g6PaMOx2Nttwte5o3IS2lRUq4Zd3uAkRi9EkxZ/XTj9EOpr0+m1YjAAd +ygrn1Lf0/q21OUuqJ5BJO5HsqRiAwK5ftdy/CBUH/2ccsfjhz5ZmlRvRi3/N6uKvlH9 h5i9RSILR9ryB/4tktcu7YR7InwyqawjpE5CD9QVP86Fs1vYlkCj4EEKpV7Wen2eq+hh ewPzX4NIfeQrG+Rale4pUe7b8tn50e4XIF7ixdaZ2khLbHTtpp/6IDfnkSj4obvOACMS zC1bRbBtUv3tlHb1JznmBKaU2Z/u/sgkj/5Yh7fnR/SQynCSuNRmlXNrOGDmypa7HQf+ fitA==
MIME-Version: 1.0
X-Received: by with SMTP id mb17mr2822454wic.64.1381491119264; Fri, 11 Oct 2013 04:31:59 -0700 (PDT)
Received: by with HTTP; Fri, 11 Oct 2013 04:31:59 -0700 (PDT)
In-Reply-To: <>
References: <> <> <> <> <> <> <AAE428925197FE46A5F94ED6643478FEAD1BDC6F0B@HE111644.EMEA1.CDS.T-INTERNAL.COM> <> <AAE428925197FE46A5F94ED6643478FEAD1BDC7177@HE111644.EMEA1.CDS.T-INTERNAL.COM> <>
Date: Fri, 11 Oct 2013 04:31:59 -0700
Message-ID: <>
From: Martin Thomson <>
To: Harald Alvestrand <>
Content-Type: text/plain; charset="UTF-8"
Cc: "" <>
Subject: Re: [rtcweb] Payload Types assignments was Re: SV: [mmusic] WGLC of draft-ietf-rtcweb-use-cases-and-requirements-11
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 11 Oct 2013 11:32:01 -0000

On 11 October 2013 04:05, Harald Alvestrand <> wrote:
> This topic may have solutions that aren't being pursued in the RTCWEB WG.
> In particular:
> describes a proposal for how to find objects on the local net (currently:
> announced via upnp and zeroconf), and
> describes a proposal for getting some information about how you're connected
> to the network.

Those solutions may not be appropriate for use in web browsers, in
much the same way that the "raw sockets" API is not.

> Getting that information may be out of scope for WEBRTC or RTCWEB.
> Putting that information to use once we have it may be in scope.

I find it more appropriate to say first that the problem is in scope,
then to look for solutions that you don't have to build yourself.  It
seems that if you want to be able to do priority marking, then a way
of discovering what markings do what is entirely in scope.

This is, of course, another case where the delineation of
responsibilities is required.  The W3C group you chair might decide to
use the discovery API, but there may be a need to assess the discovery
mechanisms here.

Other items on the list - a reasonable set of questions - seemed like
even larger problems.  If we're talking about a generic way to
advertise packet prioritization capabilities in a network, plus ways
to manage access to those features, that's a non-trivial enterprise.