Re: [rtcweb] Alexey Melnikov's No Objection on draft-ietf-rtcweb-alpn-03: (with COMMENT)
Martin Thomson <martin.thomson@gmail.com> Thu, 28 April 2016 23:51 UTC
Return-Path: <martin.thomson@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 A0A6512B041; Thu, 28 Apr 2016 16:51:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x5tXYJiQWXui; Thu, 28 Apr 2016 16:51:21 -0700 (PDT)
Received: from mail-ig0-x231.google.com (mail-ig0-x231.google.com [IPv6:2607:f8b0:4001:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D355212B071; Thu, 28 Apr 2016 16:51:20 -0700 (PDT)
Received: by mail-ig0-x231.google.com with SMTP id u10so7508861igr.1; Thu, 28 Apr 2016 16:51:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=ubf4HUXyJ/yve9PWJTvYCILAdAVmhWtDdpnoHTw8PYs=; b=XgA8fhXkRZ3v1zTiQOlfieZ9RwCGWqjtVaSrbL5tQ7S9cd9+/qsr7qTFV57TQycsPH OARU9Ssa9wDRvwqtb05AcS5y2ncR6k4PELY4NBRf8jP1lo9IIdCPMU2z2mMRRz4kClUp uChrC/+n8dYHiev7o8hKDoYixqgSj6Fhtw3hOfyZESGpoMVakI04yZotgGTe+t6Napga i1wnX0gQdcO43KF9rMrOsK5drl5O0l6Nha+10AZfghEg7bZ1BbSzhD0rn99982kQxJh/ YQonrxpuH++28e27T4Gg0vleIxXUcx7Q7ldVhuFMwqUse+u7303QUU9OQSCMyDQ7H3Eu 6YUw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=ubf4HUXyJ/yve9PWJTvYCILAdAVmhWtDdpnoHTw8PYs=; b=F3dwq287tpoYUPKQ1Yb1TLWg9IAaowtvKo0gX28bVdt+JeVWSECTE1FaJRx1ucr2+e uUc48AP8LsG4mERJLLxgnu43LYCq0KumnotF1Lm4jwu/6WFz5fOHW5b6WZHVCoeC1WaD 44us+nezHFB8egBcaaGzjeHVtdicAhn3/w3M4Efzd+ViEkvU70IU8BlDVunPCgfbIIgO e4+yNnfStt1aLRN+49YT7avm3GA5mi7axuT6a84AOmw31RnXrx71dZDTytizWfap1O5q aqx4tQdXDuV1EaxyZK2kusudijtPtkRQFrQ2IX4L7bcYISs9vrC5s8h5fgNEFJe2G3M0 C8fg==
X-Gm-Message-State: AOPr4FVeHKQqwF6RLk0xAOmAm+gYH6iq0juloXBP6NRCTdcW1kRiZwfkLH33iW1rAiPgESsR1fBDiV1AnQv7xg==
MIME-Version: 1.0
X-Received: by 10.50.101.169 with SMTP id fh9mr772657igb.58.1461887480247; Thu, 28 Apr 2016 16:51:20 -0700 (PDT)
Received: by 10.36.43.82 with HTTP; Thu, 28 Apr 2016 16:51:20 -0700 (PDT)
In-Reply-To: <20160428160109.27729.26050.idtracker@ietfa.amsl.com>
References: <20160428160109.27729.26050.idtracker@ietfa.amsl.com>
Date: Fri, 29 Apr 2016 09:51:20 +1000
Message-ID: <CABkgnnVMu0_hXChcAk54AzEnE70PmAe45cBtsevv7TuD+iKnTA@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Alexey Melnikov <aamelnikov@fastmail.fm>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/a7LvEU-CqGdWiavuxknhsI6GtLQ>
Cc: draft-ietf-rtcweb-alpn@ietf.org, Sean Turner <turners@ieca.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>, The IESG <iesg@ietf.org>, rtcweb-chairs@ietf.org
Subject: Re: [rtcweb] Alexey Melnikov's No Objection on draft-ietf-rtcweb-alpn-03: (with COMMENT)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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, 28 Apr 2016 23:51:22 -0000
On 29 April 2016 at 02:01, Alexey Melnikov <aamelnikov@fastmail.fm> wrote: > Please excuse my ignorance (pointers would be appreciated, if this is > explained elsewhere): do RTP intermediary need to be updated to > understand this spec? No. Mostly. RTP intermediaries can choose to implement this spec as an endpoint, but there is typically no benefit from doing so. RTP intermediaries don't usually have a strong distinction between "the thing that does (S)RTP" and "the thing that controls signaling" and so don't gain much by isolating media from the latter.
- [rtcweb] Alexey Melnikov's No Objection on draft-… Alexey Melnikov
- Re: [rtcweb] Alexey Melnikov's No Objection on dr… Martin Thomson
- Re: [rtcweb] Alexey Melnikov's No Objection on dr… Alexey Melnikov
- Re: [rtcweb] Alexey Melnikov's No Objection on dr… Martin Thomson