IETF Logo Mail Archive

Re: [rtcweb] Last call redux: draft-ietf-rtcweb-rtp-usage-26

Alissa Cooper <alissa@cooperw.in> Thu, 14 April 2016 16:42 UTC

Return-Path: <alissa@cooperw.in>
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 AC7A112E69D for <rtcweb@ietfa.amsl.com>; Thu, 14 Apr 2016 09:42:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level:
X-Spam-Status: No, score=-2.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cooperw.in header.b=IVc3gMzS; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=ibVuimsW
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 kVzc-sPTosuA for <rtcweb@ietfa.amsl.com>; Thu, 14 Apr 2016 09:42:57 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B01E612E69A for <rtcweb@ietf.org>; Thu, 14 Apr 2016 09:42:57 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 1F0CD20801 for <rtcweb@ietf.org>; Thu, 14 Apr 2016 12:42:56 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Thu, 14 Apr 2016 12:42:56 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=E2LZIwx15zIqIFljbZrXGmaVUP8=; b=IVc3gM zSJ2Q2ps+7QUIRJpRc9QbCUdWUwSY5RfbmyWWrouiiXwJz2bJ5Ox+MJ/IyXz+mdj lY2a0O706JCbDOl1c3TC9FXvkAQDsFmmYbebl9T8wAAti1sXnxBOaeKIjgz8bNZP ALDKFLOjN1k36lryI2B0ALBPVOwvWwi63bUwk=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=E2LZIwx15zIqIFl jbZrXGmaVUP8=; b=ibVuimsWYLRJuujarUGc427p/hD8e/hkoyF3KlXpVKmUEfy mD+n+JbI4GMDHgoTAGULGIQSKvS5W4Z5tAVZ6pdd9itRlsp6CKmjOWbyzbqsPY3H okmPgZCa8UNW399OjdmMh58Iv0GFJ0JwpPQqngO66ds5BHUdn4ePNkMdkiYw=
X-Sasl-enc: iJiRfKg+XljPM1R/Qxq2W3Kdx0wSYyPVkj2p8RopES2h 1460652175
Received: from dhcp-171-68-21-99.cisco.com (dhcp-171-68-21-99.cisco.com [171.68.21.99]) by mail.messagingengine.com (Postfix) with ESMTPA id 91BAB680250; Thu, 14 Apr 2016 12:42:55 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <4F3B615A-A77A-434E-B3A9-DDABE8994373@cooperw.in>
Date: Thu, 14 Apr 2016 09:42:54 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <D38D1C32-F465-47EB-8FBC-69B294AAB324@cooperw.in>
References: <4F3B615A-A77A-434E-B3A9-DDABE8994373@cooperw.in>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.3112)
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/wvBFPY9PsHvRhs0Ma1dErZQMROw>
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Last call redux: draft-ietf-rtcweb-rtp-usage-26
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, 14 Apr 2016 16:43:00 -0000

No comments were received, so this document will revert to the RFC Editor.

> On Mar 23, 2016, at 1:44 PM, Alissa Cooper <alissa@cooperw.in> wrote:
> 
> draft-ietf-rtcweb-rtp-usage-25 was approved for publication in July 2015 and is in the RFC Editor's queue. Subsequently, the RTCWEB WG identified a change that needed to be made in Section 4.5 related to multiplexing RTP and RTCP. The change is reflected in draft-ietf-rtcweb-rtp-usage-26 and copied below.
> 
> The IESG will not revisit its decision to approve this document for publication unless it receives feedback from the community indicating a need to do so. Please send substantive comments to the ietf@ietf.org mailing list by 2016-04-13. Exceptionally, comments may be sent to iesg@ietf.org instead.
> 
> The change is:
> 
> OLD:
> 
> If SDP is used for signalling, this
> negotiation MUST use the attributes defined in [RFC5761].  For
> backwards compatibility, implementations are also REQUIRED to support
> RTP and RTCP sent on separate transport-layer flows.
> 
> NEW:
> 
> If SDP is used for signalling, this
> negotiation MUST use the mechanism defined in [RFC5761].
> Implementations can also support sending RTP and RTCP on separate
> transport-layer flows, but this is OPTIONAL to implement.  If an
> implementation does not support RTP and RTCP sent on separate
> transport-layer flows, it MUST indicate that using the mechanism
> defined in [I-D.ietf-mmusic-mux-exclusive].
> 
> The document is available at https://datatracker.ietf.org/doc/draft-ietf-rtcweb-rtp-usage/
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email