From iesg-secretary@ietf.org Thu Jan 2 07:18:34 2014 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6BFC1ADEBA; Thu, 2 Jan 2014 07:18:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham 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 peXXkXAjnWnr; Thu, 2 Jan 2014 07:18:33 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 09C8C1AE593; Thu, 2 Jan 2014 07:18:29 -0800 (PST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 4.90 Auto-Submitted: auto-generated Precedence: bulk Sender: Message-ID: <20140102151829.2998.88454.idtracker@ietfa.amsl.com> Date: Thu, 02 Jan 2014 07:18:29 -0800 Cc: avt@ietf.org Subject: [AVTCORE] Last Call: (RTP Clock Source Signalling) to Proposed Standard X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.15 Reply-To: ietf@ietf.org List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jan 2014 15:18:34 -0000 The IESG has received a request from the Audio/Video Transport Core Maintenance WG (avtcore) to consider the following document: - 'RTP Clock Source Signalling' as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2014-01-16. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract NTP format timestamps are used by several RTP protocols for synchronisation and statistical measurements. This memo specifies SDP signalling identifying timestamp reference clock sources and SDP signalling identifying the media clock sources in a multimedia session. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-avtcore-clksrc/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-avtcore-clksrc/ballot/ No IPR declarations have been submitted directly on this I-D. From internet-drafts@ietf.org Sun Jan 12 20:22:55 2014 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1E241AE027; Sun, 12 Jan 2014 20:22:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham 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 RnCESrqwLw42; Sun, 12 Jan 2014 20:22:54 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CD821A1EF9; Sun, 12 Jan 2014 20:22:54 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.90.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140113042254.26923.14319.idtracker@ietfa.amsl.com> Date: Sun, 12 Jan 2014 20:22:54 -0800 Cc: avt@ietf.org Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-leap-second-08.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.15 List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jan 2014 04:22:56 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Audio/Video Transport Core Maintenance Wo= rking Group of the IETF. Title : RTP and Leap Seconds Authors : Kevin Gross Ray van Brandenburg Filename : draft-ietf-avtcore-leap-second-08.txt Pages : 9 Date : 2014-01-12 Abstract: This document discusses issues that arise when RTP sessions span Coordinated Universal Time (UTC) leap seconds. It updates RFC 3550 to describe how RTP senders and receivers should behave in the presence of leap seconds. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-avtcore-leap-second/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-avtcore-leap-second-08 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-avtcore-leap-second-08 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From internet-drafts@ietf.org Mon Jan 13 08:41:20 2014 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B9101ADFD6; Mon, 13 Jan 2014 08:41:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham 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 uO8aLnOeWjiy; Mon, 13 Jan 2014 08:41:18 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B02331ADFD4; Mon, 13 Jan 2014 08:41:18 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.90.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140113164118.5750.33306.idtracker@ietfa.amsl.com> Date: Mon, 13 Jan 2014 08:41:18 -0800 Cc: avt@ietf.org Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-circuit-breakers-04.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.15 List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jan 2014 16:41:20 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Audio/Video Transport Core Maintenance Wo= rking Group of the IETF. Title : Multimedia Congestion Control: Circuit Breakers f= or Unicast RTP Sessions Authors : Colin Perkins Varun Singh Filename : draft-ietf-avtcore-rtp-circuit-breakers-04.txt Pages : 17 Date : 2014-01-13 Abstract: The Real-time Transport Protocol (RTP) is widely used in telephony, video conferencing, and telepresence applications. Such applications are often run on best-effort UDP/IP networks. If congestion control is not implemented in the applications, then network congestion will deteriorate the user's multimedia experience. This document does not propose a congestion control algorithm; instead, it defines a minimal set of RTP "circuit-breakers". Circuit-breakers are conditions under which an RTP sender needs to stop transmitting media data in order to protect the network from excessive congestion. It is expected that, in the absence of severe congestion, all RTP applications running on best-effort IP networks will be able to run without triggering these circuit breakers. Any future RTP congestion control specification will be expected to operate within the constraints defined by these circuit breakers. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-circuit-breakers/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-avtcore-rtp-circuit-breakers-04 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-avtcore-rtp-circuit-breakers-= 04 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From csp@csperkins.org Mon Jan 13 08:47:37 2014 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB6B11ADFD6 for ; Mon, 13 Jan 2014 08:47:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham 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 nNN-GweRxr0F for ; Mon, 13 Jan 2014 08:47:35 -0800 (PST) Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) by ietfa.amsl.com (Postfix) with ESMTP id C67091ADFD4 for ; Mon, 13 Jan 2014 08:47:35 -0800 (PST) Received: from [130.209.247.112] (port=64933 helo=mangole.dcs.gla.ac.uk) by balrog.mythic-beasts.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1W2kfY-0002RS-Q8 for avt@ietf.org; Mon, 13 Jan 2014 16:47:23 +0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) From: Colin Perkins In-Reply-To: <20140113164118.5750.33306.idtracker@ietfa.amsl.com> Date: Mon, 13 Jan 2014 16:47:19 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: <4917CBC7-20E1-495C-8A4E-0E67E6745A13@csperkins.org> References: <20140113164118.5750.33306.idtracker@ietfa.amsl.com> To: "avt@ietf.org WG" X-Mailer: Apple Mail (2.1827) X-BlackCat-Spam-Score: -28 X-Mythic-Debug: Threshold = On = Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-circuit-breakers-04.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jan 2014 16:47:38 -0000 This is a keep-alive version, to prevent the draft expiring. The only = changes are to update the references to catch-up with recently published = RFCs. Colin On 13 Jan 2014, at 16:41, Internet-Drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts = directories. > This draft is a work item of the Audio/Video Transport Core = Maintenance Working Group of the IETF. >=20 > Title : Multimedia Congestion Control: Circuit = Breakers for Unicast RTP Sessions > Authors : Colin Perkins > Varun Singh > Filename : draft-ietf-avtcore-rtp-circuit-breakers-04.txt > Pages : 17 > Date : 2014-01-13 >=20 > Abstract: > The Real-time Transport Protocol (RTP) is widely used in telephony, > video conferencing, and telepresence applications. Such = applications > are often run on best-effort UDP/IP networks. If congestion control > is not implemented in the applications, then network congestion will > deteriorate the user's multimedia experience. This document does = not > propose a congestion control algorithm; instead, it defines a = minimal > set of RTP "circuit-breakers". Circuit-breakers are conditions = under > which an RTP sender needs to stop transmitting media data in order = to > protect the network from excessive congestion. It is expected that, > in the absence of severe congestion, all RTP applications running on > best-effort IP networks will be able to run without triggering these > circuit breakers. Any future RTP congestion control specification > will be expected to operate within the constraints defined by these > circuit breakers. >=20 >=20 > The IETF datatracker status page for this draft is: > = https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-circuit-breakers/ >=20 > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-avtcore-rtp-circuit-breakers-04 >=20 > A diff from the previous version is available at: > = http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-avtcore-rtp-circuit-breakers= -04 >=20 >=20 > Please note that it may take a couple of minutes from the time of = submission > until the htmlized version and diff are available at tools.ietf.org. >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 > _______________________________________________ > Audio/Video Transport Core Maintenance > avt@ietf.org > https://www.ietf.org/mailman/listinfo/avt --=20 Colin Perkins http://csperkins.org/ From internet-drafts@ietf.org Mon Jan 13 09:54:38 2014 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C46931ADF92; Mon, 13 Jan 2014 09:54:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham 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 WNsoJqlG8DAF; Mon, 13 Jan 2014 09:54:37 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 617E51ADF7F; Mon, 13 Jan 2014 09:54:37 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.90.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140113175437.9471.79343.idtracker@ietfa.amsl.com> Date: Mon, 13 Jan 2014 09:54:37 -0800 Cc: avt@ietf.org Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-multi-media-rtp-session-04.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.15 List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jan 2014 17:54:39 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Audio/Video Transport Core Maintenance Wo= rking Group of the IETF. Title : Sending Multiple Types of Media in a Single RTP S= ession Authors : Magnus Westerlund Colin Perkins Jonathan Lennox Filename : draft-ietf-avtcore-multi-media-rtp-session-04.txt Pages : 18 Date : 2014-01-13 Abstract: This document specifies how an RTP session can contain media streams with media from multiple media types such as audio, video, and text. This has been restricted by the RTP Specification, and thus this document updates RFC 3550 and RFC 3551 to enable this behaviour for applications that satisfy the applicability for using multiple media types in a single RTP session. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-avtcore-multi-media-rtp-session/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-avtcore-multi-media-rtp-session-04 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-avtcore-multi-media-rtp-sessi= on-04 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From internet-drafts@ietf.org Mon Jan 13 10:02:09 2014 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FD3D1ADFD7; Mon, 13 Jan 2014 10:02:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham 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 BOLPiaoue1he; Mon, 13 Jan 2014 10:02:08 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EF1A51ADF7F; Mon, 13 Jan 2014 10:02:07 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.90.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140113180207.8450.43448.idtracker@ietfa.amsl.com> Date: Mon, 13 Jan 2014 10:02:07 -0800 Cc: avt@ietf.org Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-multiplex-guidelines-02.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.15 List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jan 2014 18:02:09 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Audio/Video Transport Core Maintenance Wo= rking Group of the IETF. Title : Guidelines for using the Multiplexing Features of= RTP to Support Multiple Media Streams Authors : Magnus Westerlund Bo Burman Colin Perkins Harald Tveit Alvestrand Filename : draft-ietf-avtcore-multiplex-guidelines-02.txt Pages : 46 Date : 2014-01-13 Abstract: The Real-time Transport Protocol (RTP) is a flexible protocol that can be used in a wide range of applications, networks, and system topologies. That flexibility makes for wide applicability, but can complicate the application design process. One particular design question that has received much attention is how to support multiple media streams in RTP. This memo discusses the available options and design trade-offs, and provides guidelines on how to use the multiplexing features of RTP to support multiple media streams. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-avtcore-multiplex-guidelines/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-avtcore-multiplex-guidelines-02 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-avtcore-multiplex-guidelines-= 02 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From internet-drafts@ietf.org Mon Jan 13 10:09:17 2014 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F00C1ADF8F; Mon, 13 Jan 2014 10:09:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham 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 Fsf8n7KCfPRh; Mon, 13 Jan 2014 10:09:15 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8324F1ADFA0; Mon, 13 Jan 2014 10:09:15 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.90.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140113180915.8450.71784.idtracker@ietfa.amsl.com> Date: Mon, 13 Jan 2014 10:09:15 -0800 Cc: avt@ietf.org Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-multi-stream-02.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.15 List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jan 2014 18:09:17 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Audio/Video Transport Core Maintenance Wo= rking Group of the IETF. Title : Sending Multiple Media Streams in a Single RTP Se= ssion Authors : Jonathan Lennox Magnus Westerlund Qin Wu Colin Perkins Filename : draft-ietf-avtcore-rtp-multi-stream-02.txt Pages : 15 Date : 2014-01-13 Abstract: This document expands and clarifies the behavior of the Real-Time Transport Protocol (RTP) endpoints when they are sending multiple media streams in a single RTP session. In particular, issues involving RTP Control Protocol (RTCP) messages are described. This document updates RFC 3550 in regards to handling of multiple SSRCs per endpoint in RTP sessions. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-multi-stream/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-avtcore-rtp-multi-stream-02 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-avtcore-rtp-multi-stream-02 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From internet-drafts@ietf.org Mon Jan 13 10:14:00 2014 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AE471AE098; Mon, 13 Jan 2014 10:14:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham 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 mP7iLtgSb6KY; Mon, 13 Jan 2014 10:13:58 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 85CA81ADF89; Mon, 13 Jan 2014 10:13:58 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.90.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140113181358.17095.77601.idtracker@ietfa.amsl.com> Date: Mon, 13 Jan 2014 10:13:58 -0800 Cc: avt@ietf.org Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-multi-stream-optimisation-01.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.15 List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jan 2014 18:14:00 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Audio/Video Transport Core Maintenance Wo= rking Group of the IETF. Title : Sending Multiple Media Streams in a Single RTP Se= ssion: Grouping RTCP Reception Statistics and Other Feedback Authors : Jonathan Lennox Magnus Westerlund Qin Wu Colin Perkins Filename : draft-ietf-avtcore-rtp-multi-stream-optimisation-01.txt Pages : 10 Date : 2014-01-13 Abstract: RTP allows multiple media streams to be sent in a single session, but requires each Synchronisation Source (SSRC) to send RTCP reception quality reports for every other SSRC visible in the session. This causes the number of RTCP reception reports to grow with the number of SSRCs, rather than the number of endpoints. In many cases most of these RTCP reception reports are unnecessary, since all SSRCs of an endpoint are co-located and see the same reception quality. This memo defines a Reporting Group extension to RTCP to reduce the reporting overhead in such scenarios. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-multi-stream-optimi= sation/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-avtcore-rtp-multi-stream-optimisation= -01 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-avtcore-rtp-multi-stream-opti= misation-01 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From csp@csperkins.org Mon Jan 13 10:17:29 2014 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12B441ADF7F for ; Mon, 13 Jan 2014 10:17:29 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham 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 3Wi4R13rGAN8 for ; Mon, 13 Jan 2014 10:17:26 -0800 (PST) Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) by ietfa.amsl.com (Postfix) with ESMTP id A2F071ADF65 for ; Mon, 13 Jan 2014 10:17:26 -0800 (PST) Received: from [130.209.247.112] (port=49590 helo=mangole.dcs.gla.ac.uk) by balrog.mythic-beasts.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1W2m4Y-00061P-6F for avt@ietf.org; Mon, 13 Jan 2014 18:17:15 +0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) From: Colin Perkins In-Reply-To: <20140113175437.9471.79343.idtracker@ietfa.amsl.com> Date: Mon, 13 Jan 2014 18:17:13 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: <8BBCD8A9-A6E9-4488-AA52-ED4D0AAA4054@csperkins.org> References: <20140113175437.9471.79343.idtracker@ietfa.amsl.com> To: "avt@ietf.org WG" X-Mailer: Apple Mail (2.1827) X-BlackCat-Spam-Score: -28 X-Mythic-Debug: Threshold = On = Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-multi-media-rtp-session-04.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jan 2014 18:17:29 -0000 This is a keep-alive version; no content changes. Colin On 13 Jan 2014, at 17:54, Internet-Drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts = directories. > This draft is a work item of the Audio/Video Transport Core = Maintenance Working Group of the IETF. >=20 > Title : Sending Multiple Types of Media in a Single = RTP Session > Authors : Magnus Westerlund > Colin Perkins > Jonathan Lennox > Filename : = draft-ietf-avtcore-multi-media-rtp-session-04.txt > Pages : 18 > Date : 2014-01-13 >=20 > Abstract: > This document specifies how an RTP session can contain media streams > with media from multiple media types such as audio, video, and text. > This has been restricted by the RTP Specification, and thus this > document updates RFC 3550 and RFC 3551 to enable this behaviour for > applications that satisfy the applicability for using multiple media > types in a single RTP session. >=20 >=20 > The IETF datatracker status page for this draft is: > = https://datatracker.ietf.org/doc/draft-ietf-avtcore-multi-media-rtp-sessio= n/ >=20 > There's also a htmlized version available at: > = http://tools.ietf.org/html/draft-ietf-avtcore-multi-media-rtp-session-04 >=20 > A diff from the previous version is available at: > = http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-avtcore-multi-media-rtp-sess= ion-04 >=20 >=20 > Please note that it may take a couple of minutes from the time of = submission > until the htmlized version and diff are available at tools.ietf.org. >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 > _______________________________________________ > Audio/Video Transport Core Maintenance > avt@ietf.org > https://www.ietf.org/mailman/listinfo/avt --=20 Colin Perkins http://csperkins.org/ From csp@csperkins.org Mon Jan 13 10:17:43 2014 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67C1D1ADF93 for ; Mon, 13 Jan 2014 10:17:43 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham 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 beLoE0MKCDpc for ; Mon, 13 Jan 2014 10:17:41 -0800 (PST) Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) by ietfa.amsl.com (Postfix) with ESMTP id 262391ADF9A for ; Mon, 13 Jan 2014 10:17:40 -0800 (PST) Received: from [130.209.247.112] (port=49590 helo=mangole.dcs.gla.ac.uk) by balrog.mythic-beasts.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1W2m4l-00061P-Hh for avt@ietf.org; Mon, 13 Jan 2014 18:17:28 +0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) From: Colin Perkins In-Reply-To: <20140113180207.8450.43448.idtracker@ietfa.amsl.com> Date: Mon, 13 Jan 2014 18:17:27 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: <425ED618-1F75-4C92-AA4B-456CD498A185@csperkins.org> References: <20140113180207.8450.43448.idtracker@ietfa.amsl.com> To: "avt@ietf.org WG" X-Mailer: Apple Mail (2.1827) X-BlackCat-Spam-Score: -28 X-Mythic-Debug: Threshold = On = Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-multiplex-guidelines-02.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jan 2014 18:17:43 -0000 This is a keep-alive version; no content changes. Colin On 13 Jan 2014, at 18:02, Internet-Drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts = directories. > This draft is a work item of the Audio/Video Transport Core = Maintenance Working Group of the IETF. >=20 > Title : Guidelines for using the Multiplexing = Features of RTP to Support Multiple Media Streams > Authors : Magnus Westerlund > Bo Burman > Colin Perkins > Harald Tveit Alvestrand > Filename : draft-ietf-avtcore-multiplex-guidelines-02.txt > Pages : 46 > Date : 2014-01-13 >=20 > Abstract: > The Real-time Transport Protocol (RTP) is a flexible protocol that > can be used in a wide range of applications, networks, and system > topologies. That flexibility makes for wide applicability, but can > complicate the application design process. One particular design > question that has received much attention is how to support multiple > media streams in RTP. This memo discusses the available options and > design trade-offs, and provides guidelines on how to use the > multiplexing features of RTP to support multiple media streams. >=20 >=20 > The IETF datatracker status page for this draft is: > = https://datatracker.ietf.org/doc/draft-ietf-avtcore-multiplex-guidelines/ >=20 > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-avtcore-multiplex-guidelines-02 >=20 > A diff from the previous version is available at: > = http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-avtcore-multiplex-guidelines= -02 >=20 >=20 > Please note that it may take a couple of minutes from the time of = submission > until the htmlized version and diff are available at tools.ietf.org. >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 > _______________________________________________ > Audio/Video Transport Core Maintenance > avt@ietf.org > https://www.ietf.org/mailman/listinfo/avt --=20 Colin Perkins http://csperkins.org/ From csp@csperkins.org Mon Jan 13 10:17:56 2014 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC4B71AE1AB for ; Mon, 13 Jan 2014 10:17:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham 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 KW0ZQlFH_bdC for ; Mon, 13 Jan 2014 10:17:55 -0800 (PST) Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) by ietfa.amsl.com (Postfix) with ESMTP id B7AE61AE1B0 for ; Mon, 13 Jan 2014 10:17:54 -0800 (PST) Received: from [130.209.247.112] (port=49590 helo=mangole.dcs.gla.ac.uk) by balrog.mythic-beasts.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1W2m4z-00061P-V9 for avt@ietf.org; Mon, 13 Jan 2014 18:17:43 +0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) From: Colin Perkins In-Reply-To: <20140113180915.8450.71784.idtracker@ietfa.amsl.com> Date: Mon, 13 Jan 2014 18:17:41 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: <3F162CBD-FAAF-4755-A1C5-2FA5F8695779@csperkins.org> References: <20140113180915.8450.71784.idtracker@ietfa.amsl.com> To: "avt@ietf.org WG" X-Mailer: Apple Mail (2.1827) X-BlackCat-Spam-Score: -28 X-Mythic-Debug: Threshold = On = Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-multi-stream-02.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jan 2014 18:17:57 -0000 This is a keep-alive version; no content changes. Colin On 13 Jan 2014, at 18:09, Internet-Drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts = directories. > This draft is a work item of the Audio/Video Transport Core = Maintenance Working Group of the IETF. >=20 > Title : Sending Multiple Media Streams in a Single = RTP Session > Authors : Jonathan Lennox > Magnus Westerlund > Qin Wu > Colin Perkins > Filename : draft-ietf-avtcore-rtp-multi-stream-02.txt > Pages : 15 > Date : 2014-01-13 >=20 > Abstract: > This document expands and clarifies the behavior of the Real-Time > Transport Protocol (RTP) endpoints when they are sending multiple > media streams in a single RTP session. In particular, issues > involving RTP Control Protocol (RTCP) messages are described. >=20 > This document updates RFC 3550 in regards to handling of multiple > SSRCs per endpoint in RTP sessions. >=20 >=20 > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-multi-stream/ >=20 > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-avtcore-rtp-multi-stream-02 >=20 > A diff from the previous version is available at: > = http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-avtcore-rtp-multi-stream-02 >=20 >=20 > Please note that it may take a couple of minutes from the time of = submission > until the htmlized version and diff are available at tools.ietf.org. >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 > _______________________________________________ > Audio/Video Transport Core Maintenance > avt@ietf.org > https://www.ietf.org/mailman/listinfo/avt --=20 Colin Perkins http://csperkins.org/ From csp@csperkins.org Mon Jan 13 10:18:10 2014 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B3811AE196 for ; Mon, 13 Jan 2014 10:18:10 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham 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 zzE5hxd5nCmM for ; Mon, 13 Jan 2014 10:18:08 -0800 (PST) Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) by ietfa.amsl.com (Postfix) with ESMTP id 10EDD1AE174 for ; Mon, 13 Jan 2014 10:18:07 -0800 (PST) Received: from [130.209.247.112] (port=49590 helo=mangole.dcs.gla.ac.uk) by balrog.mythic-beasts.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1W2m5D-00061P-7e for avt@ietf.org; Mon, 13 Jan 2014 18:17:55 +0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) From: Colin Perkins In-Reply-To: <20140113181358.17095.77601.idtracker@ietfa.amsl.com> Date: Mon, 13 Jan 2014 18:17:54 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: <4D2E9E70-DD17-47B1-88C6-101B434FA127@csperkins.org> References: <20140113181358.17095.77601.idtracker@ietfa.amsl.com> To: "avt@ietf.org WG" X-Mailer: Apple Mail (2.1827) X-BlackCat-Spam-Score: -28 X-Mythic-Debug: Threshold = On = Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-multi-stream-optimisation-01.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jan 2014 18:18:10 -0000 This is a keep-alive version; no content changes. Colin On 13 Jan 2014, at 18:13, Internet-Drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts = directories. > This draft is a work item of the Audio/Video Transport Core = Maintenance Working Group of the IETF. >=20 > Title : Sending Multiple Media Streams in a Single = RTP Session: Grouping RTCP Reception Statistics and Other Feedback > Authors : Jonathan Lennox > Magnus Westerlund > Qin Wu > Colin Perkins > Filename : = draft-ietf-avtcore-rtp-multi-stream-optimisation-01.txt > Pages : 10 > Date : 2014-01-13 >=20 > Abstract: > RTP allows multiple media streams to be sent in a single session, = but > requires each Synchronisation Source (SSRC) to send RTCP reception > quality reports for every other SSRC visible in the session. This > causes the number of RTCP reception reports to grow with the number > of SSRCs, rather than the number of endpoints. In many cases most = of > these RTCP reception reports are unnecessary, since all SSRCs of an > endpoint are co-located and see the same reception quality. This > memo defines a Reporting Group extension to RTCP to reduce the > reporting overhead in such scenarios. >=20 >=20 > The IETF datatracker status page for this draft is: > = https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-multi-stream-optim= isation/ >=20 > There's also a htmlized version available at: > = http://tools.ietf.org/html/draft-ietf-avtcore-rtp-multi-stream-optimisatio= n-01 >=20 > A diff from the previous version is available at: > = http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-avtcore-rtp-multi-stream-opt= imisation-01 >=20 >=20 > Please note that it may take a couple of minutes from the time of = submission > until the htmlized version and diff are available at tools.ietf.org. >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 > _______________________________________________ > Audio/Video Transport Core Maintenance > avt@ietf.org > https://www.ietf.org/mailman/listinfo/avt --=20 Colin Perkins http://csperkins.org/ From adam@nostrum.com Tue Jan 14 12:06:48 2014 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AECE1AE1B0 for ; Tue, 14 Jan 2014 12:06:48 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.035 X-Spam-Level: X-Spam-Status: No, score=-1.035 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001] autolearn=no 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 291PtVgaRYDM for ; Tue, 14 Jan 2014 12:06:47 -0800 (PST) Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 289041AE1A5 for ; Tue, 14 Jan 2014 12:06:47 -0800 (PST) Received: from orochi-2.roach.at (99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s0EK6N8A077025 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 14 Jan 2014 14:06:24 -0600 (CST) (envelope-from adam@nostrum.com) Message-ID: <52D598BA.6050201@nostrum.com> Date: Tue, 14 Jan 2014 14:06:18 -0600 From: Adam Roach User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Colin Perkins , Roni Even References: <20130830162909.20422.68365.idtracker@ietfa.amsl.com> <008201cea59e$aa9fd3a0$ffdf7ae0$@gmail.com> <5EAB5396-57ED-4B29-9FEF-0CAF92F27052@csperkins.org> <015a01cea7d3$62c3cbe0$284b63a0$@gmail.com> <5C7CBAD2-4340-4A7B-8D55-8E56AB2DE07E@csperkins.org> <031001cea92f$df4ff780$9defe680$@gmail.com> In-Reply-To: Content-Type: multipart/alternative; boundary="------------010607060304070309040209" Received-SPF: pass (shaman.nostrum.com: 99.152.145.110 is authenticated by a trusted mechanism) Cc: "rai-ads@tools.ietf.org" , avt@ietf.org Subject: Re: [AVTCORE] New Version Notification for draft-wu-avtcore-dynamic-pt-usage-00.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jan 2014 20:06:48 -0000 This is a multi-part message in MIME format. --------------010607060304070309040209 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 9/4/13 17:13, Colin Perkins wrote: > I really don't think you need a new draft to update this table. There > is an existing RFC that reserves those payload types; just ask IANA to > make the correction to the registry. I agree. I think this is a simple administrative action to update the registry to match the facts on the ground as documented by the already-published RFC 5761. I think that either the AVT chairs or the RAI ADs would be well within process to ask the IANA to fix the registry to match currently published RFCs; we do stuff like this all the time when oversights in registries are spotted. If we want to also publish a PT guidance document, great. I think that would be useful, too. But we don't need to predicate fixing the registry to match the already-published RFCs on having that document finished. /a --------------010607060304070309040209 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit
On 9/4/13 17:13, Colin Perkins wrote:
I really don't think you need a new draft to update this table. There is an existing RFC that reserves those payload types; just ask IANA to make the correction to the registry.

I agree. I think this is a simple administrative action to update the registry to match the facts on the ground as documented by the already-published RFC 5761. I think that either the AVT chairs or the RAI ADs would be well within process to ask the IANA to fix the registry to match currently published RFCs; we do stuff like this all the time when oversights in registries are spotted.

If we want to also publish a PT guidance document, great. I think that would be useful, too. But we don't need to predicate fixing the registry to match the already-published RFCs on having that document finished.

/a
--------------010607060304070309040209-- From internet-drafts@ietf.org Wed Jan 15 01:04:49 2014 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 656B81AE31A; Wed, 15 Jan 2014 01:04:49 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham 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 R3dXxR_id4DI; Wed, 15 Jan 2014 01:04:47 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DC9121AE02E; Wed, 15 Jan 2014 01:04:47 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.90.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140115090447.23945.3740.idtracker@ietfa.amsl.com> Date: Wed, 15 Jan 2014 01:04:47 -0800 Cc: avt@ietf.org Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-security-options-10.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.15 List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jan 2014 09:04:49 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Audio/Video Transport Core Maintenance Wo= rking Group of the IETF. Title : Options for Securing RTP Sessions Authors : Magnus Westerlund Colin Perkins Filename : draft-ietf-avtcore-rtp-security-options-10.txt Pages : 35 Date : 2014-01-15 Abstract: The Real-time Transport Protocol (RTP) is used in a large number of different application domains and environments. This heterogeneity implies that different security mechanisms are needed to provide services such as confidentiality, integrity and source authentication of RTP/RTCP packets suitable for the various environments. The range of solutions makes it difficult for RTP-based application developers to pick the most suitable mechanism. This document provides an overview of a number of security solutions for RTP, and gives guidance for developers on how to choose the appropriate security mechanism. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-security-options/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-avtcore-rtp-security-options-10 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-avtcore-rtp-security-options-= 10 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From magnus.westerlund@ericsson.com Wed Jan 15 01:12:31 2014 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B4E01AE221 for ; Wed, 15 Jan 2014 01:12:31 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham 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 gI-9uoefWfLg for ; Wed, 15 Jan 2014 01:12:29 -0800 (PST) Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id C72F71AE304 for ; Wed, 15 Jan 2014 01:12:28 -0800 (PST) X-AuditID: c1b4fb38-b7f2c8e000006d25-3b-52d650f06e0c Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id 45.73.27941.0F056D25; Wed, 15 Jan 2014 10:12:16 +0100 (CET) Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.77) with Microsoft SMTP Server id 14.2.347.0; Wed, 15 Jan 2014 10:12:16 +0100 Message-ID: <52D650E3.7010107@ericsson.com> Date: Wed, 15 Jan 2014 10:12:03 +0100 From: Magnus Westerlund User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: References: <20140115090447.23945.3740.idtracker@ietfa.amsl.com> In-Reply-To: <20140115090447.23945.3740.idtracker@ietfa.amsl.com> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrFJMWRmVeSWpSXmKPExsUyM+Jvje6HgGtBBqeuqVu87FnJ7sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujDPHO5kK5olX7Llxia2Bca9QFyMnh4SAicSK+ctZIGwxiQv3 1rN1MXJxCAkcYZT409kG5SxnlJg38RE7SBWvgLbExoMrWEFsFgFViY8Pt7CB2GwCFhI3fzSC 2aICwRK3pj2AqheUODnzCdgGEQEhien9E5hAbGEBd4klB3+DxYUEHCTebljK3MXIwcEp4Cgx 76AGiCkhIC7R0xgEUsEsoCcx5WoLI4QtL9G8dTYzRKe2RENTB+sERsFZSJbNQtIyC0nLAkbm VYwcxanFSbnpRgabGIHhd3DLb4sdjJf/2hxilOZgURLn/fjWOUhIID2xJDU7NbUgtSi+qDQn tfgQIxMHp1QDY07njw/yWisdZgTv2X1FrtPfca79q7+dM+wSmbZOerBAkWvRZY/GdPMJLf83 JF5/uG1ydW0dq5biNvFrDe+Xr4jwyIl7tdy5Y9LvveyTGNZ/VVjyNX2TgepeycQbE8KtJhjf +F26sXoXS5+QZcaa168kz3/ctkTR+ETk2cST/zyK/b8trudZWKHEUpyRaKjFXFScCABCXrJg DQIAAA== Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-security-options-10.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jan 2014 09:12:31 -0000 WG, The document didn't get any discusses when going through IESG approval, but we got some comments that we liked to address, thus this update that changes some wording etc. See diff link below. Please provide quick feedback on these changes if any, as I expect it to be approved soon. Cheers Magnus On 2014-01-15 10:04, internet-drafts@ietf.org wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Audio/Video Transport Core Maintenance Working Group of the IETF. > > Title : Options for Securing RTP Sessions > Authors : Magnus Westerlund > Colin Perkins > Filename : draft-ietf-avtcore-rtp-security-options-10.txt > Pages : 35 > Date : 2014-01-15 > > Abstract: > The Real-time Transport Protocol (RTP) is used in a large number of > different application domains and environments. This heterogeneity > implies that different security mechanisms are needed to provide > services such as confidentiality, integrity and source authentication > of RTP/RTCP packets suitable for the various environments. The range > of solutions makes it difficult for RTP-based application developers > to pick the most suitable mechanism. This document provides an > overview of a number of security solutions for RTP, and gives > guidance for developers on how to choose the appropriate security > mechanism. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-security-options/ > > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-avtcore-rtp-security-options-10 > > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=draft-ietf-avtcore-rtp-security-options-10 > > > Please note that it may take a couple of minutes from the time of submission > until the htmlized version and diff are available at tools.ietf.org. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > I-D-Announce mailing list > I-D-Announce@ietf.org > https://www.ietf.org/mailman/listinfo/i-d-announce > Internet-Draft directories: http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > -- Magnus Westerlund ---------------------------------------------------------------------- Services, Media and Network features, Ericsson Research EAB/TXM ---------------------------------------------------------------------- Ericsson AB | Phone +46 10 7148287 Färögatan 6 | Mobile +46 73 0949079 SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com ---------------------------------------------------------------------- From internet-drafts@ietf.org Thu Jan 16 02:12:45 2014 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D551C1AE308; Thu, 16 Jan 2014 02:12:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham 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 JpMRdvkJdxVk; Thu, 16 Jan 2014 02:12:44 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D5281AE058; Thu, 16 Jan 2014 02:12:44 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.90.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140116101244.29407.82035.idtracker@ietfa.amsl.com> Date: Thu, 16 Jan 2014 02:12:44 -0800 Cc: avt@ietf.org Subject: [AVTCORE] I-D Action: draft-ietf-avt-srtp-not-mandatory-15.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.15 List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jan 2014 10:12:46 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Audio/Video Transport Core Maintenance Wo= rking Group of the IETF. Title : Securing the RTP Protocol Framework: Why RTP Does= Not Mandate a Single Media Security Solution Authors : Colin Perkins Magnus Westerlund Filename : draft-ietf-avt-srtp-not-mandatory-15.txt Pages : 10 Date : 2014-01-16 Abstract: This memo discusses the problem of securing real-time multimedia sessions, and explains why the Real-time Transport Protocol (RTP), and the associated RTP Control Protocol (RTCP), do not mandate a single media security mechanism. This is relevant for designers and reviewers of future RTP extensions, to ensure that appropriate security mechanisms are mandated, and that any such mechanisms are specified in a manner that conforms with the RTP architecture. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-avt-srtp-not-mandatory/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-avt-srtp-not-mandatory-15 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-avt-srtp-not-mandatory-15 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From internet-drafts@ietf.org Thu Jan 16 02:19:46 2014 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 992221AE31F; Thu, 16 Jan 2014 02:19:46 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham 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 njIuXl0Tk0Lw; Thu, 16 Jan 2014 02:19:45 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DFC51AE314; Thu, 16 Jan 2014 02:19:45 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.90.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140116101945.25114.11696.idtracker@ietfa.amsl.com> Date: Thu, 16 Jan 2014 02:19:45 -0800 Cc: avt@ietf.org Subject: [AVTCORE] I-D Action: draft-ietf-avt-srtp-not-mandatory-16.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.15 List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jan 2014 10:19:46 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Audio/Video Transport Core Maintenance Wo= rking Group of the IETF. Title : Securing the RTP Protocol Framework: Why RTP Does= Not Mandate a Single Media Security Solution Authors : Colin Perkins Magnus Westerlund Filename : draft-ietf-avt-srtp-not-mandatory-16.txt Pages : 10 Date : 2014-01-16 Abstract: This memo discusses the problem of securing real-time multimedia sessions, and explains why the Real-time Transport Protocol (RTP), and the associated RTP Control Protocol (RTCP), do not mandate a single media security mechanism. This is relevant for designers and reviewers of future RTP extensions, to ensure that appropriate security mechanisms are mandated, and that any such mechanisms are specified in a manner that conforms with the RTP architecture. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-avt-srtp-not-mandatory/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-avt-srtp-not-mandatory-16 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-avt-srtp-not-mandatory-16 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From magnus.westerlund@ericsson.com Thu Jan 16 02:29:41 2014 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 152771AE203 for ; Thu, 16 Jan 2014 02:29:41 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.24 X-Spam-Level: X-Spam-Status: No, score=-1.24 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] autolearn=no 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 Fcj-LJkCOVFN for ; Thu, 16 Jan 2014 02:29:39 -0800 (PST) Received: from sessmg20.mgmt.ericsson.se (sessmg20.ericsson.net [193.180.251.50]) by ietfa.amsl.com (Postfix) with ESMTP id E28761AE1F9 for ; Thu, 16 Jan 2014 02:29:38 -0800 (PST) X-AuditID: c1b4fb32-b7f2b8e0000073bf-f9-52d7b485a677 Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg20.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 06.21.29631.584B7D25; Thu, 16 Jan 2014 11:29:26 +0100 (CET) To: undisclosed-recipients:; Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.41) with Microsoft SMTP Server id 14.2.347.0; Thu, 16 Jan 2014 11:29:25 +0100 Message-ID: <52D7B476.9070501@ericsson.com> Date: Thu, 16 Jan 2014 11:29:10 +0100 From: Magnus Westerlund User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 CC: References: <20140116101945.25114.11696.idtracker@ietfa.amsl.com> In-Reply-To: <20140116101945.25114.11696.idtracker@ietfa.amsl.com> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprBLMWRmVeSWpSXmKPExsUyM+JvjW7blutBBit7mCxe9qxkd2D0WLLk J1MAYxSXTUpqTmZZapG+XQJXxto3GxgL5opXvL31j7mBcZVQFyMnh4SAicSvtZuZIWwxiQv3 1rN1MXJxCAmcYJQ4tWIKWEJEQEZi7uzHrBCJ5YwSs461giV4BbQlHl5+wgJiswioSiybdIgd xGYTsJC4+aORDcQWFQiWuDXtATtEvaDEyZkQ9cwCQhKn53xjBbGFBbwlHs9vAKsXEnCUaLj6 FyzOKeAkcfXMJqBeDqDrxCV6GoMgWvUkplxtYYSw5SWat85mhmjVlmho6mCdwCg0C8m2WUha ZiFpWcDIvIpRsji1uDg33chALzc9t0QvtSgzubg4P0+vOHUTIzB0D275bbSD8eQe+0OM0hws SuK811lrgoQE0hNLUrNTUwtSi+KLSnNSiw8xMnFwSjUwlvEu8z3CKq14s73FsHxDDeMa0UMF Cy6mhR6XCNpyRDRYovI0G8fiy2L3axI/FL2d5bZ265y6bK4VjEHXDpzOPtNXdtlpMUtHz1aT E89SDsd9eSM0QUfA2lO5XrrsgVKjdLv303j2o626p+6n7QwVTg571TzZTbpyotOlQ8ZsAtxB pTq3mWYpsRRnJBpqMRcVJwIAJ5c6eSsCAAA= Subject: Re: [AVTCORE] I-D Action: draft-ietf-avt-srtp-not-mandatory-16.txt X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jan 2014 10:29:41 -0000 WG, (as author) We have now updated this document to resolve both Benoit's discuss and the comments we received from IESG. The discuss fix is all making it clearer the purpose of the document in the introduction. A bit of editorial in the abstract and in one of the section title was also done. The other significant change is in Section 5, where one sentence was removed and another written. Please review the diff. Sorry for the two versions, missed that the latest proposed change hadn't been added to the source .xml file. Cheers Magnus On 2014-01-16 11:19, internet-drafts@ietf.org wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Audio/Video Transport Core Maintenance Working Group of the IETF. > > Title : Securing the RTP Protocol Framework: Why RTP Does Not Mandate a Single Media Security Solution > Authors : Colin Perkins > Magnus Westerlund > Filename : draft-ietf-avt-srtp-not-mandatory-16.txt > Pages : 10 > Date : 2014-01-16 > > Abstract: > This memo discusses the problem of securing real-time multimedia > sessions, and explains why the Real-time Transport Protocol (RTP), > and the associated RTP Control Protocol (RTCP), do not mandate a > single media security mechanism. This is relevant for designers and > reviewers of future RTP extensions, to ensure that appropriate > security mechanisms are mandated, and that any such mechanisms are > specified in a manner that conforms with the RTP architecture. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-avt-srtp-not-mandatory/ > > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-avt-srtp-not-mandatory-16 > > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=draft-ietf-avt-srtp-not-mandatory-16 > > > Please note that it may take a couple of minutes from the time of submission > until the htmlized version and diff are available at tools.ietf.org. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > Audio/Video Transport Core Maintenance > avt@ietf.org > https://www.ietf.org/mailman/listinfo/avt > > -- Magnus Westerlund ---------------------------------------------------------------------- Services, Media and Network features, Ericsson Research EAB/TXM ---------------------------------------------------------------------- Ericsson AB | Phone +46 10 7148287 Färögatan 6 | Mobile +46 73 0949079 SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com ---------------------------------------------------------------------- From magnus.westerlund@ericsson.com Thu Jan 23 07:19:05 2014 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3AAA1A001E for ; Thu, 23 Jan 2014 07:19:05 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham 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 4_DknMFSGgXh for ; Thu, 23 Jan 2014 07:19:04 -0800 (PST) Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id 8C1F71A0006 for ; Thu, 23 Jan 2014 07:19:03 -0800 (PST) X-AuditID: c1b4fb38-b7f418e000001099-49-52e132e511cf Received: from ESESSHC005.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id 58.6F.04249.5E231E25; Thu, 23 Jan 2014 16:19:02 +0100 (CET) Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.35) with Microsoft SMTP Server id 14.2.347.0; Thu, 23 Jan 2014 16:19:01 +0100 Message-ID: <52E132E5.40207@ericsson.com> Date: Thu, 23 Jan 2014 16:19:01 +0100 From: Magnus Westerlund User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: IETF AVTCore WG X-Enigmail-Version: 1.6 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrMJMWRmVeSWpSXmKPExsUyM+Jvje4zo4dBBmcmC1q87FnJ7sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujHld7xkLOuQr/r+6xNLAOFGyi5GTQ0LARGLZk3ZGCFtM4sK9 9WxdjFwcQgJHGCUmnGpjgXCWM0q8f98GVsUroClxaNchMJtFQFXi/eLpbCA2m4CFxM0fjWC2 qECwxK1pD9gh6gUlTs58wgJiiwgoSeyYtI0ZxBYGqv+15CpQnANos7hET2MQSJhZQE9iytUW RghbXqJ562ywciEBbYmGpg7WCYz8s5BMnYWkZRaSlgWMzKsYOYpTi5Ny040MNjECA+rglt8W Oxgv/7U5xCjNwaIkzvvxrXOQkEB6YklqdmpqQWpRfFFpTmrxIUYmDk6pBsaAM47cSxy/T5Tb MfXE28AlIs9yA3f4Tr0Xb2xTuc3IPqC4Y/dJnhpjDQPW91ESPBdb1fyYPpW62R9nPSZyUjq5 XDB6QoJKuIRST6TdzAIZ5+DEeBWtR4t/X4lui1CxOC0pzHKbVUDmOJ/QbO/zOfwb+JU8q2e1 /DeR3LDeJ26ZmUv8IRkJJZbijERDLeai4kQA/eZYm/YBAAA= Subject: [AVTCORE] IANAs payload type number registry and RFC 5761 X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jan 2014 15:19:05 -0000 WG, (As Chair) I started writing on a email to IANA regarding our discussion and the need to update the registry: http://www.iana.org/assignments/rtp-parameters/rtp-parameters.xhtml#rtp-parameters-1 After having reviewed RFC 3551, RFC 5761, the registry and the email discuss and do question the recommendation the discussion and https://datatracker.ietf.org/doc/draft-wu-avtcore-dynamic-pt-usage/ have on this topic. My understanding of Dale's original message to this list and the reason for raising this issue is that people look at this table to determine how to handle dynamic PT assignments. This is a closed registry and has therefore not been updated. Also the relevant information around how to chose dynamic payload type ranges are present now in two documents. Namely RFC 3551, Section 3: This profile reserves payload type numbers in the range 96-127 exclusively for dynamic assignment. Applications SHOULD first use values in this range for dynamic payload types. Those applications which need to define more than 32 dynamic payload types MAY bind codes below 96, in which case it is RECOMMENDED that unassigned payload type numbers be used first. However, the statically assigned payload types are default bindings and MAY be dynamically bound to new encodings if needed. Redefining payload types below 96 may cause incorrect operation if an attempt is made to join a session without obtaining session description information that defines the dynamic payload types. This is further expanded on given that one is using RTP/RTCP multiplexing by RFC 5761 that adds the additional rules and clarification in Section 4: Given these constraints, it is RECOMMENDED to follow the guidelines in the RTP/AVP profile [7] for the choice of RTP payload type values, with the additional restriction that payload type values in the range 64-95 MUST NOT be used. Specifically, dynamic RTP payload types SHOULD be chosen in the range 96-127 where possible. Values below 64 MAY be used if that is insufficient, in which case it is RECOMMENDED that payload type numbers that are not statically assigned by [7] be used first. Thus, if this is the main reason why people want to update the registry I would recommend that we propose to IANA to update the registries note, that is not particular helpful at this point. I believe a good note for this registry would contain three things. 1. That the registry is closed, see RFC 3551, no additional registrations will be done. The payload types that have a static mapping are the below ones (0-34). 2. The "Reserved for RTCP conflict avoidance" in this table is not up to date. Instead http://www.iana.org/assignments/rtp-parameters/rtp-parameters.xhtml#rtp-parameters-4 provides the list of the RTCP types that has actually been registered. Subtract 128 from the RTCP Packet Type value to find the corresponding PT value with collision risk. For further information see RFC 3551 and RFC 5761. 3. If you seek guidance on which PT values to use for assigning dynamic payload types, then that is present in RFC 3551 (Section 3) and RFC 5761 (Section 4). I think such a note update will continue to be more relevant that a current patch to the reserved range. It also avoids the complexities that the dynamic payload type assignment rules are different between users of RFC 5761 and those who don't. Comments Magnus Westerlund ---------------------------------------------------------------------- Services, Media and Network features, Ericsson Research EAB/TXM ---------------------------------------------------------------------- Ericsson AB | Phone +46 10 7148287 Färögatan 6 | Mobile +46 73 0949079 SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com ---------------------------------------------------------------------- From worley@shell01.TheWorld.com Thu Jan 23 08:54:13 2014 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A56B1A0090 for ; Thu, 23 Jan 2014 08:54:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.601 X-Spam-Level: X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham 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 kPRMV6w2pQ-2 for ; Thu, 23 Jan 2014 08:54:10 -0800 (PST) Received: from TheWorld.com (pcls6.std.com [192.74.137.146]) by ietfa.amsl.com (Postfix) with ESMTP id 140E91A0095 for ; Thu, 23 Jan 2014 08:54:08 -0800 (PST) Received: from shell.TheWorld.com (root@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id s0NGrxCh002318; Thu, 23 Jan 2014 11:54:02 -0500 Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id s0NGnNZs3433431; Thu, 23 Jan 2014 11:49:23 -0500 (EST) Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id s0NGnMKU3433184; Thu, 23 Jan 2014 11:49:22 -0500 (EST) Date: Thu, 23 Jan 2014 11:49:22 -0500 (EST) Message-Id: <201401231649.s0NGnMKU3433184@shell01.TheWorld.com> From: worley@ariadne.com (Dale R. Worley) Sender: worley@ariadne.com (Dale R. Worley) To: Magnus Westerlund In-reply-to: <52E132E5.40207@ericsson.com> (magnus.westerlund@ericsson.com) References: <52E132E5.40207@ericsson.com> Cc: avt@ietf.org Subject: Re: [AVTCORE] IANAs payload type number registry and RFC 5761 X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jan 2014 16:54:13 -0000 > From: Magnus Westerlund > I believe a good note for this registry would contain three things. > [etc.] A note containing all of this information would satisfy my concerns. Dale From iesg-secretary@ietf.org Thu Jan 23 09:05:37 2014 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B61821A006C; Thu, 23 Jan 2014 09:05:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham 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 bLs1eSASCPOL; Thu, 23 Jan 2014 09:05:36 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 12A241A00BC; Thu, 23 Jan 2014 09:05:34 -0800 (PST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 4.90.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140123170534.22572.31466.idtracker@ietfa.amsl.com> Date: Thu, 23 Jan 2014 09:05:34 -0800 Cc: avtcore chair , avtcore mailing list , RFC Editor Subject: [AVTCORE] Protocol Action: 'RTP and Leap Seconds' to Proposed Standard (draft-ietf-avtcore-leap-second-08.txt) X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.15 List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jan 2014 17:05:38 -0000 The IESG has approved the following document: - 'RTP and Leap Seconds' (draft-ietf-avtcore-leap-second-08.txt) as Proposed Standard This document is the product of the Audio/Video Transport Core Maintenance Working Group. The IESG contact persons are Richard Barnes and Gonzalo Camarillo. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-avtcore-leap-second/ Technical Summary This document discusses issues that arise when RTP sessions span Coordinated Universal Time (UTC) leap seconds. It updates RFC 3550 to describe how RTP senders and receivers should behave in the presence of leap seconds. Working Group Summary There has solid consensus in the AVTCORE WG to do this work. The WG process has been making good progress with a reasonable amount of persons involved in reviewing and commenting on the document. Document Quality There has been several reviewers that combined make the Shepherd convinced that this document has no substantiative issues. First Colin Perkins has reviewed the RTP/RTCP recommendations. Then Art Allison and John Fletcher has reviewed and commented on the time and clock aspects of this document. The shepherd is not yet aware of any implementation of this specification. Personnel Magnus Westerlund is the Document Shepherd and Richard Barnes the responsible AD. From iesg-secretary@ietf.org Thu Jan 23 09:12:35 2014 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4346F1A0103; Thu, 23 Jan 2014 09:12:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham 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 zUW9zYDHjN32; Thu, 23 Jan 2014 09:12:32 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 072D31A00F4; Thu, 23 Jan 2014 09:12:30 -0800 (PST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 4.90.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140123171230.28712.46658.idtracker@ietfa.amsl.com> Date: Thu, 23 Jan 2014 09:12:30 -0800 Cc: avtcore chair , avtcore mailing list , RFC Editor Subject: [AVTCORE] Document Action: 'Securing the RTP Protocol Framework: Why RTP Does Not Mandate a Single Media Security Solution' to Informational RFC (draft-ietf-avt-srtp-not-mandatory-16.txt) X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.15 List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jan 2014 17:12:35 -0000 The IESG has approved the following document: - 'Securing the RTP Protocol Framework: Why RTP Does Not Mandate a Single Media Security Solution' (draft-ietf-avt-srtp-not-mandatory-16.txt) as Informational RFC This document is the product of the Audio/Video Transport Core Maintenance Working Group. The IESG contact persons are Richard Barnes and Gonzalo Camarillo. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-avt-srtp-not-mandatory/ Technical Summary This memo discusses the problem of securing real-time multimedia sessions, and explains why the Real-time Transport Protocol (RTP), and the associated RTP Control Protocol (RTCP), do not mandate a single media security mechanism. Guidelines for designers and reviewers of future RTP extensions are provided, to ensure that appropriate security mechanisms are mandated, and that any such mechanisms are specified in a manner that conforms with the RTP architecture. Working Group Summary This document was already in IESG review and there were concerns from the Security area suggesting that there will be also a document describing the security options. It came back to the AVTcore WG and there is also the security option document that complements this document. It was reviewed by the WG members and the WG security experts and there are no issues from the WG that is worth noting. Document Quality This document is an informational document and I would like to mention that Dan Wing and Alan Johnston did a review and made helpful comments that helped with the quality of the document. There are of course implementations of the media security solutions including SRTP with SDES and DTLS SRTO but this document is only explain why we do not mandate a single solution. Personnel Document Shepherd is Roni Even and the responsible AD is Richard Barnes. From iesg-secretary@ietf.org Thu Jan 23 09:15:28 2014 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADD9F1A0041; Thu, 23 Jan 2014 09:15:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham 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 MPtbn_wGarpB; Thu, 23 Jan 2014 09:15:27 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 204011A00A1; Thu, 23 Jan 2014 09:15:25 -0800 (PST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 4.90.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140123171525.9658.72023.idtracker@ietfa.amsl.com> Date: Thu, 23 Jan 2014 09:15:25 -0800 Cc: avtcore chair , avtcore mailing list , RFC Editor Subject: [AVTCORE] Document Action: 'Options for Securing RTP Sessions' to Informational RFC (draft-ietf-avtcore-rtp-security-options-10.txt) X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.15 List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jan 2014 17:15:29 -0000 The IESG has approved the following document: - 'Options for Securing RTP Sessions' (draft-ietf-avtcore-rtp-security-options-10.txt) as Informational RFC This document is the product of the Audio/Video Transport Core Maintenance Working Group. The IESG contact persons are Richard Barnes and Gonzalo Camarillo. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-security-options/ Technical Summary The Real-time Transport Protocol (RTP) is used in a large number of different application domains and environments. This heterogeneity implies that different security mechanisms are needed to provide services such as confidentiality, integrity and source authentication of RTP/RTCP packets suitable for the various environments. The range of solutions makes it difficult for RTP-based application developers to pick the most suitable mechanism. This document provides an overview of a number of security solutions for RTP, and gives guidance for developers on how to choose the appropriate security mechanism. Working Group Summary This document complements draft-ietf-avt-srtp-not-mandatory providing information about security options. It was reviewed by the WG members and the WG security experts and there are no issues from the WG that is worth noting. Document Quality This document is an overview document and I would like to mention that Dan Wing and Alan Johnston did a review and made helpful comments that helped with the quality of the document. Personnel Document Shepherd is Roni Even and the responsible AD is Richard Barnes. From adam@nostrum.com Thu Jan 23 12:22:18 2014 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 469181A00CC for ; Thu, 23 Jan 2014 12:22:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.036 X-Spam-Level: X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] autolearn=no 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 ynR2AAgFP-B7 for ; Thu, 23 Jan 2014 12:22:17 -0800 (PST) Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id A73C21A0049 for ; Thu, 23 Jan 2014 12:22:17 -0800 (PST) Received: from orochi-2.roach.at (99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s0NKM9CT069787 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 23 Jan 2014 14:22:10 -0600 (CST) (envelope-from adam@nostrum.com) Message-ID: <52E179EC.8000105@nostrum.com> Date: Thu, 23 Jan 2014 14:22:04 -0600 From: Adam Roach User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: "Dale R. Worley" , Magnus Westerlund References: <52E132E5.40207@ericsson.com> <201401231649.s0NGnMKU3433184@shell01.TheWorld.com> In-Reply-To: <201401231649.s0NGnMKU3433184@shell01.TheWorld.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Received-SPF: pass (shaman.nostrum.com: 99.152.145.110 is authenticated by a trusted mechanism) Cc: avt@ietf.org Subject: Re: [AVTCORE] IANAs payload type number registry and RFC 5761 X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jan 2014 20:22:18 -0000 On 1/23/14 10:49, Dale R. Worley wrote: >> From: Magnus Westerlund >> I believe a good note for this registry would contain three things. >> [etc.] > A note containing all of this information would satisfy my concerns. > It's not my preferred solution, but I can live with this as well. /a From magnus.westerlund@ericsson.com Fri Jan 24 04:07:10 2014 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB1A91A02D1 for ; Fri, 24 Jan 2014 04:07:10 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.851 X-Spam-Level: X-Spam-Status: No, score=-3.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham 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 Rbqs3gigCa0K for ; Fri, 24 Jan 2014 04:07:09 -0800 (PST) Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 812911A02D0 for ; Fri, 24 Jan 2014 04:07:08 -0800 (PST) X-AuditID: c1b4fb25-b7f038e000005d01-3f-52e2576ae5a4 Received: from ESESSHC010.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 7B.A0.23809.A6752E25; Fri, 24 Jan 2014 13:07:06 +0100 (CET) Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.50) with Microsoft SMTP Server id 14.2.347.0; Fri, 24 Jan 2014 13:07:06 +0100 Message-ID: <52E25769.5030605@ericsson.com> Date: Fri, 24 Jan 2014 13:07:05 +0100 From: Magnus Westerlund User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Adam Roach , "Dale R. Worley" References: <52E132E5.40207@ericsson.com> <201401231649.s0NGnMKU3433184@shell01.TheWorld.com> <52E179EC.8000105@nostrum.com> In-Reply-To: <52E179EC.8000105@nostrum.com> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprBLMWRmVeSWpSXmKPExsUyM+JvjW5W+KMgg6PbTC32/F3EbvGyZyWQ OFHmwOwxef9XZo8lS34yecza+YQlgDmKyyYlNSezLLVI3y6BK2PqsuOsBUv5K5q2f2VvYFzE 08XIySEhYCJxovU5K4QtJnHh3nq2LkYuDiGBQ4wS06eeY4JwljNKLJv3ig2kildAW+LSx20s IDaLgKrE12XrwGw2AQuJmz8awWpEBYIlbk17wA5RLyhxcuYTsBoRAQ+Jef97wWxmASGJ03O+ gW0WFnCTWLr4O1ivkECNxJprVxi7GDk4OIF2ffqjAGJKCIhL9DQGQXRqSrRu/80OYctLNG+d zQzRqS3R0NTBOoFRaBaSxbOQtMxC0rKAkXkVI3tuYmZOernRJkZg6B7c8lt1B+OdcyKHGKU5 WJTEeT+8dQ4SEkhPLEnNTk0tSC2KLyrNSS0+xMjEwSnVwLjbzUVKi9+1an/aKZUWmwUiJU+n ey9v6FTP89b9dObg5qTAQl7Ppyy3m+SdN5fsyrhRkmcaW6JscOXtm88XwjqLPYO2brJ8t0Vn wYmvXU8VxG1bhaxMuzy2vBa5Uidzc7E3s0vFSo0jDy+uXPkjLZZzDSvjtWk+7pM+iPDqM+hZ G2m8+f9WX4mlOCPRUIu5qDgRADDczGwrAgAA Cc: avt@ietf.org Subject: Re: [AVTCORE] IANAs payload type number registry and RFC 5761 X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jan 2014 12:07:11 -0000 On 2014-01-23 21:22, Adam Roach wrote: > On 1/23/14 10:49, Dale R. Worley wrote: >>> From: Magnus Westerlund >>> I believe a good note for this registry would contain three things. >>> [etc.] >> A note containing all of this information would satisfy my concerns. >> > > It's not my preferred solution, but I can live with this as well. > What would your preferred solution be? To update the registry? I am personally hesitant to do that for the following reasons: 1. It is a closed registry 2. The registries purpose was to capture which static assignments that had been made. 3. The dynamic payload type recommendations are done in RFC 3551. 4. If one is using the RTP/RTCP multiplexing of RFC 5761 that applies also, but we do have different set of rules depending on if one is using RFC5761 or not. That is difficult to capture in a static table. 5. The RTCP reservations are done in a different table, including an indication of what the primary and secondary ranges for assignment are. 6. The PT's, i.e. lower 7 bits of the packets types that would collides with is a ever changing. So updating it today doesn't help, if we are going to use it in this way would need to continue to ensure that all new RTCP packet types that goes into the RTCP Packet type registry also get a line in the Payload type registry. These are the reasons why I think a note being a better solution. Cheers Magnus Westerlund ---------------------------------------------------------------------- Services, Media and Network features, Ericsson Research EAB/TXM ---------------------------------------------------------------------- Ericsson AB | Phone +46 10 7148287 Färögatan 6 | Mobile +46 73 0949079 SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com ---------------------------------------------------------------------- From aidan.williams@audinate.com Tue Jan 28 16:20:03 2014 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E66181A0467 for ; Tue, 28 Jan 2014 16:20:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.436 X-Spam-Level: X-Spam-Status: No, score=-2.436 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham 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 AiaQGyIuNQ7k for ; Tue, 28 Jan 2014 16:20:01 -0800 (PST) Received: from zimbra8.audinate.com (sydney.audinate.com [150.101.200.21]) by ietfa.amsl.com (Postfix) with ESMTP id 87ED31A043A for ; Tue, 28 Jan 2014 16:20:01 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zimbra8.audinate.com (Postfix) with ESMTP id 19B2A343BB3; Wed, 29 Jan 2014 11:19:58 +1100 (EST) Received: from zimbra8.audinate.com ([127.0.0.1]) by localhost (zimbra8.audinate.com [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id ghdiOLpGmJcC; Wed, 29 Jan 2014 11:19:57 +1100 (EST) Received: from localhost (localhost [127.0.0.1]) by zimbra8.audinate.com (Postfix) with ESMTP id ECC57343BAE; Wed, 29 Jan 2014 11:19:56 +1100 (EST) X-Virus-Scanned: amavisd-new at audinate.com Received: from zimbra8.audinate.com ([127.0.0.1]) by localhost (zimbra8.audinate.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id JQDaByk0mxKz; Wed, 29 Jan 2014 11:19:56 +1100 (EST) Received: from zimbra8.audinate.com (zimbra8.audinate.com [10.12.0.4]) by zimbra8.audinate.com (Postfix) with ESMTP id D1A16343BA9; Wed, 29 Jan 2014 11:19:56 +1100 (EST) Date: Wed, 29 Jan 2014 11:19:56 +1100 (EST) From: Aidan Williams To: Richard Barnes Message-ID: <134045964.59704.1390954796756.JavaMail.zimbra@audinate.com> In-Reply-To: References: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_59703_260793013.1390954796755" X-Mailer: Zimbra 8.0.6_GA_5922 (ZimbraWebClient - FF26 (Mac)/8.0.6_GA_5922) Thread-Topic: AD review: draft-ietf-avtcore-clksrc-09 Thread-Index: wkzY8AZpfPMItOp29AexvYG0fg6PZA== Cc: "avt@ietf.org WG" Subject: Re: [AVTCORE] AD review: draft-ietf-avtcore-clksrc-09 X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jan 2014 00:20:04 -0000 ------=_Part_59703_260793013.1390954796755 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hi Richard, Thanks for the review. Responses are inline below... ----- Original Message ----- | From: "Richard Barnes" | To: "avt@ietf.org WG" | Sent: Sunday, 29 December, 2013 12:25:39 PM | Subject: [AVTCORE] AD review: draft-ietf-avtcore-clksrc-09 | I have reviewed this document in preparation for IETF LC. Overall, it reads | quite well. Thanks! I have requested a LC. | A couple of comments that you can consider with LC comments: | -- It seems like a reader familiar with | draft-ietf-avtext-rtp-grouping-taxonomy might be surprised by these terms. | Given that that document is still in development, I don't expect you to be | able to use the terms there. However, it might be helpful to add a note | saying that you are not attempting to align with their terminology. It is great that there is a document attempting to define terminology clearly (it would have been awesome to have it for this draft!), but I'm not sure how to go about addressing your comment since we probably don't want to refer to the above draft explicitly. At present, there is a positive statement: "here are the definitions". Can you say a bit more about what you would like to see? | -- GLONASS? Happy to add this. | -- Behavior with traceable clocks seems underspecified to me. Section 4.7 | should say explicitly that traceable clocks are marked with the ":traceable" | suffix or the "/traceable/" identifier. With regard to NTP/PTP servers, how | does the user of the clock know that the server is traceable? Is this | indicated in-band to those protocols? Would it not be useful to be able to | indicate that those servers provide traceable time? Marking a clock as traceable allows additional information (e.g. IP addresses, PTP master identifiers and the like) to be omitted from the SDP since any traceable clock available at the answerer is considered to be an appropriate timestamp reference clock. For example, an offerer could could specify ts-refclk:ntp=/traceable/ and the answerer could use GPS as a reference clock since GPS is a source of traceable time. Would some additional sentences such as these address your comment? regards aidan ____ :wq! | --Richard | _______________________________________________ | Audio/Video Transport Core Maintenance | avt@ietf.org | https://www.ietf.org/mailman/listinfo/avt ------=_Part_59703_260793013.1390954796755 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hi Richard,

Th= anks for the review.  Responses are inline below...

=

From: "Richard Barnes" <rlb@ipv.sx>
<= b>To: "avt@ietf.org WG" <avt@ietf.org>
Sent: Sunday, 29= December, 2013 12:25:39 PM
Subject: [AVTCORE] AD review: draft-i= etf-avtcore-clksrc-09

I have reviewed this document in preparation for IETF LC.&= nbsp; Overall, it reads quite well.  Thanks!   I have reques= ted a LC.

A couple of comments that you can conside= r with LC comments:

-- It seems like a reader familiar with dr= aft-ietf-avtext-rtp-grouping-taxonomy might be surprised by these terms.&nb= sp; Given that that document is still in development, I don't expect you to= be able to use the terms there.  However, it might be helpful to add = a note saying that you are not attempting to align with their terminology.<= br>
It is great that t= here is a document attempting to define terminology clearly (it would have = been awesome to have it for this draft!), but I'm not sure how to go about = addressing your comment since we probably don't want to refer to the above = draft explicitly.  At present, there is a positive statement: "here ar= e the definitions".  Can you say a bit more about what you would like = to see?

-- GLONASS?
=
Happy to add this.

=
-- Behavior with traceable clocks= seems underspecified to me.  Section 4.7 should say explicitly that t= raceable clocks are marked with the ":traceable" suffix or the "/traceable/= " identifier.  With regard to NTP/PTP servers, how does the user of th= e clock know that the server is traceable?  Is this indicated in-band = to those protocols?  Would it not be useful to be able to indicate tha= t those servers provide traceable time? 
<= /div>
Marking a clock as traceable allows additional= information (e.g. IP addresses, PTP master identifiers and the like) to be= omitted from the SDP since any traceable clock available at the answerer i= s considered to be an appropriate timestamp reference clock.  For exam= ple, an offerer could could specify ts-refclk:ntp=3D/traceable/ and the ans= werer could use GPS as a reference clock since GPS is a source of traceable= time.

Would some additional sentences such as= these address your comment?

regards
=
        aidan
____
:wq!

--Richard

__________= _____________________________________
Audio/Video Transport Core Mainten= ance
avt@ietf.org
https://www.ietf.org/mailman/listinfo/avt

------=_Part_59703_260793013.1390954796755-- From christer.holmberg@ericsson.com Wed Jan 29 04:27:14 2014 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 108B01A0360 for ; Wed, 29 Jan 2014 04:27:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.239 X-Spam-Level: X-Spam-Status: No, score=-1.239 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no 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 MR3Xs63hWf-H for ; Wed, 29 Jan 2014 04:27:13 -0800 (PST) Received: from sessmg20.mgmt.ericsson.se (sessmg20.ericsson.net [193.180.251.50]) by ietfa.amsl.com (Postfix) with ESMTP id 76DF71A04D0 for ; Wed, 29 Jan 2014 04:27:12 -0800 (PST) X-AuditID: c1b4fb32-b7f4c8e0000012f5-3a-52e8f39c4b7e Received: from ESESSHC006.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg20.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 92.60.04853.C93F8E25; Wed, 29 Jan 2014 13:27:08 +0100 (CET) Received: from ESESSMB209.ericsson.se ([169.254.9.99]) by ESESSHC006.ericsson.se ([153.88.183.36]) with mapi id 14.02.0387.000; Wed, 29 Jan 2014 13:27:07 +0100 From: Christer Holmberg To: "avt@ietf.org" Thread-Topic: STRAW WG document review request: draft-ietf-straw-b2bua-rtcp-00 Thread-Index: Ac8c7RjSMbYBmdnLQ9mQTmK4kQtrcg== Date: Wed, 29 Jan 2014 12:27:06 +0000 Message-ID: <7594FB04B1934943A5C02806D1A2204B1D14960D@ESESSMB209.ericsson.se> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [153.88.183.147] Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D14960DESESSMB209erics_" MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrKLMWRmVeSWpSXmKPExsUyM+Jvje6czy+CDE5/srZ42bOS3YHRY8mS n0wBjFFcNimpOZllqUX6dglcGf0zLjMVNMlVfJg/k72B8ZRUFyMnh4SAicTq3vnsELaYxIV7 69m6GLk4hAROMEps330JylnMKDG55wZjFyMHB5uAhUT3P22QBhEBRYnWa58ZQWxhAU+JY2u/ skDEAyT2/JnEBmHrSfR+2w9mswioSpy63MwEYvMK+Er8mb8EzGYEWvz91Bowm1lAXOLWk/lM EAcJSCzZc54ZwhaVePn4HyvICRICShLTtqaBmMwC+RL/7sRATBSUODnzCcsERqFZSAbNQqia haQKokRHYsHuT2wQtrbEsoWvmWHsMwceMyGLL2BkX8UoWZxaXJybbmSgl5ueW6KXWpSZXFyc n6dXnLqJERgVB7f8NtrBeHKP/SFGaQ4WJXHe66w1QUIC6YklqdmpqQWpRfFFpTmpxYcYmTg4 pRoY67uF9/z69uhsu9e8TZcuPdh2tL6GKfqdZ4lfZNCu01M3pLE9k9rvl7bKcMfRr54HDWUY HleWTba90L7KT9pI/PzWM9PrTBf0GLo5Nkp6/X73q/d3ddui078FGXl6BRfPfWKoZtumo8N4 LOcb58aZsrzX+/e1lzQ80l9wuMHz4nsHvXc66W2+SizFGYmGWsxFxYkAHYZ571gCAAA= Subject: [AVTCORE] STRAW WG document review request: draft-ietf-straw-b2bua-rtcp-00 X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jan 2014 12:27:14 -0000 --_000_7594FB04B1934943A5C02806D1A2204B1D14960DESESSMB209erics_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, In the STRAW WG we are working on the following document: http://tools.ietf.org/html/draft-ietf-straw-b2bua-rtcp-00 The STRAW WG chairs think it would be very useful, and we would deeply appr= eciate, if some people from the AVTCORE community would have some time and = interest in reviewing and providing comments on the document (on the STRAW = list). Please let me know if you are willing to do such review :) Thanks! Regards, Christer STRAW WG co-chair --_000_7594FB04B1934943A5C02806D1A2204B1D14960DESESSMB209erics_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

 

In the STRAW WG we are working on the following docu= ment:

 

http://tools.ietf.org/html/draft-ietf-straw-b2bua-rtcp-00=

 

The STRAW WG chairs think it would be very useful, a= nd we would deeply appreciate, if some people from the AVTCORE community wo= uld have some time and interest in reviewing and providing comments on the = document (on the STRAW list).

 

Please let me know if you are willing to do such rev= iew :)

 

Thanks!

 

Regards,

 

Christer

STRAW WG co-chair

--_000_7594FB04B1934943A5C02806D1A2204B1D14960DESESSMB209erics_-- From sang.zhuo@zte.com.cn Wed Jan 29 18:00:45 2014 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 968CE1A041D for ; Wed, 29 Jan 2014 18:00:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -97.285 X-Spam-Level: X-Spam-Status: No, score=-97.285 tagged_above=-999 required=5 tests=[BAYES_50=0.8, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.535, USER_IN_WHITELIST=-100] autolearn=ham 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 1InMRwbiAFD1 for ; Wed, 29 Jan 2014 18:00:42 -0800 (PST) Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id 993931A0357 for ; Wed, 29 Jan 2014 18:00:42 -0800 (PST) Received: from zte.com.cn (unknown [192.168.168.119]) by Websense Email Security Gateway with ESMTP id 08963123D515 for ; Thu, 30 Jan 2014 10:00:31 +0800 (CST) Received: from mse02.zte.com.cn (unknown [10.30.3.21]) by Websense Email Security Gateway with ESMTPS id 8C3711F826B for ; Thu, 30 Jan 2014 10:00:29 +0800 (CST) Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id s0U20Upi003422 for ; Thu, 30 Jan 2014 10:00:30 +0800 (GMT-8) (envelope-from sang.zhuo@zte.com.cn) Auto-Submitted: auto-generated From: sang.zhuo@zte.com.cn To: avt@ietf.org Message-ID: Date: Thu, 30 Jan 2014 10:00:38 +0800 X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2014-01-30 10:00:13 MIME-Version: 1.0 Content-type: text/plain; charset=GB2312 Content-transfer-encoding: base64 X-MAIL: mse02.zte.com.cn s0U20Upi003422 Subject: [AVTCORE] Santino Sang is out of office X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2014 02:00:45 -0000 DQrO0r2rtNMgMjAxNC8wMS8yOSC/qsq8wOu/qrDsuavK0qOstb0gMjAxNC8wMi8wNyDKsbe1u9ih ow0KDQpJIGFtIG91dCBvZiB0aGUgb2ZmaWNlIHVudGlsIDZ0aCBGZWIgMjAxNC5FbWFpbHMgcmVw bHkgd291bGQgYmUgZGVsYXksIGFueSB1cmdlbnQgaXNzdWUgeW91IGNhbiByZWFjaCBtZSBieSBj ZWxscGhvbmU6MDA4NiAxMzQyNTE3NzU1Nw0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NClpURSBJbmZvcm1hdGlvbiBTZWN1cml0eSBOb3Rp Y2U6IFRoZSBpbmZvcm1hdGlvbiBjb250YWluZWQgaW4gdGhpcyBtYWlsIChhbmQgYW55IGF0dGFj aG1lbnQgdHJhbnNtaXR0ZWQgaGVyZXdpdGgpIGlzIHByaXZpbGVnZWQgYW5kIGNvbmZpZGVudGlh bCBhbmQgaXMgaW50ZW5kZWQgZm9yIHRoZSBleGNsdXNpdmUgdXNlIG9mIHRoZSBhZGRyZXNzZWUo cykuICBJZiB5b3UgYXJlIG5vdCBhbiBpbnRlbmRlZCByZWNpcGllbnQsIGFueSBkaXNjbG9zdXJl LCByZXByb2R1Y3Rpb24sIGRpc3RyaWJ1dGlvbiBvciBvdGhlciBkaXNzZW1pbmF0aW9uIG9yIHVz ZSBvZiB0aGUgaW5mb3JtYXRpb24gY29udGFpbmVkIGlzIHN0cmljdGx5IHByb2hpYml0ZWQuICBJ ZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIG1haWwgaW4gZXJyb3IsIHBsZWFzZSBkZWxldGUgaXQg YW5kIG5vdGlmeSB1cyBpbW1lZGlhdGVseS4NCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQpaVEUgSW5mb3JtYXRpb24gU2VjdXJpdHkgTm90 aWNlOiBUaGUgaW5mb3JtYXRpb24gY29udGFpbmVkIGluIHRoaXMgbWFpbCAoYW5kIGFueSBhdHRh Y2htZW50IHRyYW5zbWl0dGVkIGhlcmV3aXRoKSBpcyBwcml2aWxlZ2VkIGFuZCBjb25maWRlbnRp YWwgYW5kIGlzIGludGVuZGVkIGZvciB0aGUgZXhjbHVzaXZlIHVzZSBvZiB0aGUgYWRkcmVzc2Vl KHMpLiAgSWYgeW91IGFyZSBub3QgYW4gaW50ZW5kZWQgcmVjaXBpZW50LCBhbnkgZGlzY2xvc3Vy ZSwgcmVwcm9kdWN0aW9uLCBkaXN0cmlidXRpb24gb3Igb3RoZXIgZGlzc2VtaW5hdGlvbiBvciB1 c2Ugb2YgdGhlIGluZm9ybWF0aW9uIGNvbnRhaW5lZCBpcyBzdHJpY3RseSBwcm9oaWJpdGVkLiAg SWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBtYWlsIGluIGVycm9yLCBwbGVhc2UgZGVsZXRlIGl0 IGFuZCBub3RpZnkgdXMgaW1tZWRpYXRlbHkuDQo= From keith.drage@alcatel-lucent.com Wed Jan 29 16:41:24 2014 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BE771A0435 for ; Wed, 29 Jan 2014 16:41:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.9 X-Spam-Level: X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham 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 EajF14CPbKNs for ; Wed, 29 Jan 2014 16:41:23 -0800 (PST) Received: from hoemail1.alcatel.com (hoemail1.alcatel.com [192.160.6.148]) by ietfa.amsl.com (Postfix) with ESMTP id 511D51A042F for ; Wed, 29 Jan 2014 16:41:23 -0800 (PST) Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by hoemail1.alcatel.com (8.13.8/IER-o) with ESMTP id s0U0fIYp016014 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Wed, 29 Jan 2014 18:41:20 -0600 (CST) Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id s0U0fIVE008296 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Thu, 30 Jan 2014 01:41:18 +0100 Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.26]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.02.0247.003; Thu, 30 Jan 2014 01:41:18 +0100 From: "DRAGE, Keith (Keith)" To: "avtcore@ietf.org" , "mmusic@ietf.org" , "rtcweb@ietf.org" , "clue@ietf.org" Thread-Topic: draft-ietf-avtext-rtp-grouping-taxonomy-00 Thread-Index: Ac8dU7miUI8F3eIfTMKku34324AzNA== Date: Thu, 30 Jan 2014 00:41:17 +0000 Message-ID: <949EF20990823C4C85C18D59AA11AD8B125741@FR712WXCHMBA11.zeu.alcatel-lucent.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [135.239.27.38] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Mailman-Approved-At: Thu, 30 Jan 2014 08:01:44 -0800 Subject: [AVTCORE] draft-ietf-avtext-rtp-grouping-taxonomy-00 X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2014 00:41:24 -0000 To all potential users of the taxonomy document in other working groups. We could do with a few people reading the above draft and identifying omiss= ions, open issues, or corrections, so the editors can get a new version out= prior to the AVTEXT meeting in London. https://datatracker.ietf.org/doc/draft-ietf-avtext-rtp-grouping-taxonomy/ In particular, those of you who have drafts that might use some of this ter= minology. Please respond to the avtext list. Regards Keith AVTEXT WG cochair. From georgehanes@hushmail.com Thu Jan 30 14:04:51 2014 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D53721A0489 for ; Thu, 30 Jan 2014 14:04:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.323 X-Spam-Level: X-Spam-Status: No, score=-2.323 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RP_MATCHES_RCVD=-0.535, SPF_HELO_NEUTRAL=0.112, SPF_PASS=-0.001] autolearn=ham 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 x8nJU5FS0CpQ for ; Thu, 30 Jan 2014 14:04:50 -0800 (PST) Received: from smtp3.hushmail.com (smtp3a.hushmail.com [65.39.178.201]) by ietfa.amsl.com (Postfix) with ESMTP id 9CCDB1A04B2 for ; Thu, 30 Jan 2014 14:04:50 -0800 (PST) Received: from smtp3.hushmail.com (smtp3a.hushmail.com [65.39.178.201]) by smtp3.hushmail.com (Postfix) with SMTP id 645C6E03B6 for ; Thu, 30 Jan 2014 22:04:32 +0000 (UTC) Received: from smtp.hushmail.com (w8.hushmail.com [65.39.178.52]) by smtp3.hushmail.com (Postfix) with ESMTP for ; Thu, 30 Jan 2014 22:04:32 +0000 (UTC) Received: by smtp.hushmail.com (Postfix, from userid 99) id 4F0CD6018A; Thu, 30 Jan 2014 22:04:32 +0000 (UTC) MIME-Version: 1.0 Date: Thu, 30 Jan 2014 17:04:32 -0500 To: avt@ietf.org From: georgehanes@hushmail.com Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="UTF-8" Message-Id: <20140130220432.4F0CD6018A@smtp.hushmail.com> Subject: [AVTCORE] Be cautious of this computer science conference X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2014 22:11:15 -0000 Be cautious of this computer science conference If you have any thought of attending the world’s biggest f-a-k-e conference in computer science http://www.world-academy-of-science.org you should visit any websites below https://sites.google.com/site/worlddump1 or https://sites.google.com/site/dumpconf https://sites.google.com/site/moneycomp1 https://sites.google.com/site/worlddump4 The organizer of this conference is H-amid A-rabnia http://www.cs.uga.edu/~hra a professor from University of Georgia, Athens, US. He already earned millions of dollars from the registration fee. He recently started a new conference CSCI due to his hunger for money http://www.americancse.org He did not reveal the reviews and reviewers' information for all the papers he received, despite repeated requests and challenges. The reason for his failure is there are no reviews and reviewers and he just cheated the research community for more than a decade by announcing that each draft paper is reviewed by two experts. We challenge him to publish these details at the conference website. Where are your experts? Where are your reviews? Soon he comes up with a story announcing that he lost all the information having reviews and reviewers because of computer crash or theft. DBLP stopped indexing these conferences since 2011 and displayed an explicit message; "The DBLP Advisory Board decided to discontinue indexing of this conference series". Visit http://www.informatik.uni-trier.de/~ley/db/conf/biocomp/index.html as a sample. He was forced to remove his name, the university of Georgia name, and university of Georgia email address from the conference’s contact page because the University has banned him from doing that. Do not spoil your resume by publishing in this conference. Apologies for posting to multiple mailing lists. Spreading the news is the only way to stop this conference from harming innocent researchers. Respectfully, Many researchers cheated by these conferences From rlb@ipv.sx Thu Jan 30 16:05:03 2014 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3F341A0526 for ; Thu, 30 Jan 2014 16:05:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.977 X-Spam-Level: X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham 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 ynWiqLL8N6iq for ; Thu, 30 Jan 2014 16:05:01 -0800 (PST) Received: from mail-oa0-f42.google.com (mail-oa0-f42.google.com [209.85.219.42]) by ietfa.amsl.com (Postfix) with ESMTP id 565C11A0521 for ; Thu, 30 Jan 2014 16:04:57 -0800 (PST) Received: by mail-oa0-f42.google.com with SMTP id i7so4531914oag.1 for ; Thu, 30 Jan 2014 16:04:53 -0800 (PST) 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:content-type; bh=2XwltR93uO7ZxlTPA9jr6/jCrvO26FObI6IRQa2wbCQ=; b=R+nKy63DGav+7vo40cRukRZrq8rUh60J5Encyt+s2rzrFg8edU1CByK9T3VOGBbz4d 004cxuhvPMm0wTE7W/bc5QYgCU8YPIBZ/sJeVZl5t5PtfEUp2dn+I46g74/eEffuvZXc JbDDOGheKSNnTkHaTzztz9r2Usk+hysXZhoyJML0D/CqokYCVV6eJ5KQFcl9+P0UqoY8 QR5EGM1664o+/XgCQu1tQ2I/+VwNCRA/KpT3AYd3Ww1jcV5bTRsUCJbc4mgleS9Z2dAh tO/4BpIvXatXkhooDoTp7htkNS8uYErYG7BwrNpml0oabk2fwku4ZA4b22g4L99k6nlk MIMw== X-Gm-Message-State: ALoCoQnvV74mwIeVq7AIfkVW5WeEaRZIF5+6mwG2uxQjTvTSpFxJ7RQvQAGUUp0ECMoqfj65xuVn MIME-Version: 1.0 X-Received: by 10.182.29.98 with SMTP id j2mr13822306obh.30.1391126693800; Thu, 30 Jan 2014 16:04:53 -0800 (PST) Received: by 10.60.69.102 with HTTP; Thu, 30 Jan 2014 16:04:53 -0800 (PST) In-Reply-To: <134045964.59704.1390954796756.JavaMail.zimbra@audinate.com> References: <134045964.59704.1390954796756.JavaMail.zimbra@audinate.com> Date: Thu, 30 Jan 2014 16:04:53 -0800 Message-ID: From: Richard Barnes To: Aidan Williams Content-Type: multipart/alternative; boundary=001a11c2c4846c10f104f138ec21 Cc: "avt@ietf.org WG" Subject: Re: [AVTCORE] AD review: draft-ietf-avtcore-clksrc-09 X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Jan 2014 00:05:04 -0000 --001a11c2c4846c10f104f138ec21 Content-Type: text/plain; charset=ISO-8859-1 Hey Aidan, Would you like to go ahead and revise the document before it goes to the IESG for evaluation? Or we can handle these with any IESG comments. --Richard On Tue, Jan 28, 2014 at 4:19 PM, Aidan Williams wrote: > Hi Richard, > > Thanks for the review. Responses are inline below... > > > ------------------------------ > > *From: *"Richard Barnes" > *To: *"avt@ietf.org WG" > *Sent: *Sunday, 29 December, 2013 12:25:39 PM > *Subject: *[AVTCORE] AD review: draft-ietf-avtcore-clksrc-09 > > > I have reviewed this document in preparation for IETF LC. Overall, it > reads quite well. Thanks! I have requested a LC. > > A couple of comments that you can consider with LC comments: > > -- It seems like a reader familiar with > draft-ietf-avtext-rtp-grouping-taxonomy might be surprised by these terms. > Given that that document is still in development, I don't expect you to be > able to use the terms there. However, it might be helpful to add a note > saying that you are not attempting to align with their terminology. > > It is great that there is a document attempting to define terminology > clearly (it would have been awesome to have it for this draft!), but I'm > not sure how to go about addressing your comment since we probably don't > want to refer to the above draft explicitly. At present, there is a > positive statement: "here are the definitions". Can you say a bit more > about what you would like to see? > > -- GLONASS? > > Happy to add this. > > -- Behavior with traceable clocks seems underspecified to me. Section 4.7 > should say explicitly that traceable clocks are marked with the > ":traceable" suffix or the "/traceable/" identifier. With regard to > NTP/PTP servers, how does the user of the clock know that the server is > traceable? Is this indicated in-band to those protocols? Would it not be > useful to be able to indicate that those servers provide traceable time? > > Marking a clock as traceable allows additional information (e.g. IP > addresses, PTP master identifiers and the like) to be omitted from the SDP > since any traceable clock available at the answerer is considered to be an > appropriate timestamp reference clock. For example, an offerer could could > specify ts-refclk:ntp=/traceable/ and the answerer could use GPS as a > reference clock since GPS is a source of traceable time. > > Would some additional sentences such as these address your comment? > > regards > aidan > ____ > :wq! > > --Richard > > _______________________________________________ > Audio/Video Transport Core Maintenance > avt@ietf.org > https://www.ietf.org/mailman/listinfo/avt > > > --001a11c2c4846c10f104f138ec21 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hey Aidan,

Would you like to go ahead a= nd revise the document before it goes to the IESG for evaluation? =A0Or we = can handle these with any IESG comments.

--Richard=


On Tue,= Jan 28, 2014 at 4:19 PM, Aidan Williams <aidan.williams@audinat= e.com> wrote:
Hi Richard,

Thanks for the review.=A0 Responses are inline below...

<= /div>

From: "Richard Barnes" <rlb@ipv.sx>
To: &q= uot;avt@ietf.org WG&q= uot; <avt@ietf.org= >
Sent: Sunday, 29 December, 2013 12:25:39 PM
Subject: [AVTC= ORE] AD review: draft-ietf-avtcore-clksrc-09


=
I have reviewed t= his document in preparation for IETF LC.=A0 Overall, it reads quite well.= =A0 Thanks!=A0=A0 I have requested a LC.

A couple of comments that you can consider with LC com= ments:

-- It seems like a reader familiar with draft-ietf-avte= xt-rtp-grouping-taxonomy might be surprised by these terms.=A0 Given that t= hat document is still in development, I don't expect you to be able to = use the terms there.=A0 However, it might be helpful to add a note saying t= hat you are not attempting to align with their terminology.
It is great tha= t there is a document attempting to define terminology clearly (it would ha= ve been awesome to have it for this draft!), but I'm not sure how to go= about addressing your comment since we probably don't want to refer to= the above draft explicitly.=A0 At present, there is a positive statement: = "here are the definitions".=A0 Can you say a bit more about what = you would like to see?

-- GLONASS?
Happy to add this.

-- Behavior with traceable clocks= seems underspecified to me.=A0 Section 4.7 should say explicitly that trac= eable clocks are marked with the ":traceable" suffix or the "= ;/traceable/" identifier.=A0 With regard to NTP/PTP servers, how does = the user of the clock know that the server is traceable?=A0 Is this indicat= ed in-band to those protocols?=A0 Would it not be useful to be able to indi= cate that those servers provide traceable time?=A0
Marking a clock= as traceable allows additional information (e.g. IP addresses, PTP master = identifiers and the like) to be omitted from the SDP since any traceable cl= ock available at the answerer is considered to be an appropriate timestamp = reference clock.=A0 For example, an offerer could could specify ts-refclk:n= tp=3D/traceable/ and the answerer could use GPS as a reference clock since = GPS is a source of traceable time.

Would some additional sentences such as these add= ress your comment?

regards
=A0= =A0=A0=A0=A0=A0=A0 aidan
____
:wq!

--Richard

_______________________________________________
Audio/Video Tr= ansport Core Maintenance
avt@ietf.org
https://www.ietf.org/mailman/listinfo/avt


--001a11c2c4846c10f104f138ec21-- From aidan.williams@audinate.com Thu Jan 30 20:34:53 2014 Return-Path: X-Original-To: avt@ietfa.amsl.com Delivered-To: avt@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 793381A0541 for ; Thu, 30 Jan 2014 20:34:53 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.436 X-Spam-Level: X-Spam-Status: No, score=-2.436 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham 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 Q_f_4HU0rDub for ; Thu, 30 Jan 2014 20:34:51 -0800 (PST) Received: from zimbra8.audinate.com (sydney.audinate.com [150.101.200.21]) by ietfa.amsl.com (Postfix) with ESMTP id AC0771A0540 for ; Thu, 30 Jan 2014 20:34:50 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zimbra8.audinate.com (Postfix) with ESMTP id 971063AC318; Fri, 31 Jan 2014 15:34:46 +1100 (EST) Received: from zimbra8.audinate.com ([127.0.0.1]) by localhost (zimbra8.audinate.com [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id 4ifjMmrlNPmL; Fri, 31 Jan 2014 15:34:45 +1100 (EST) Received: from localhost (localhost [127.0.0.1]) by zimbra8.audinate.com (Postfix) with ESMTP id 49FEF3AC30E; Fri, 31 Jan 2014 15:34:45 +1100 (EST) X-Virus-Scanned: amavisd-new at audinate.com Received: from zimbra8.audinate.com ([127.0.0.1]) by localhost (zimbra8.audinate.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id W24DEwISfxCE; Fri, 31 Jan 2014 15:34:45 +1100 (EST) Received: from zimbra8.audinate.com (zimbra8.audinate.com [10.12.0.4]) by zimbra8.audinate.com (Postfix) with ESMTP id 1FA2B3AC309; Fri, 31 Jan 2014 15:34:45 +1100 (EST) Date: Fri, 31 Jan 2014 15:34:44 +1100 (EST) From: Aidan Williams To: Richard Barnes Message-ID: <330007132.150230.1391142884977.JavaMail.zimbra@audinate.com> In-Reply-To: References: <134045964.59704.1390954796756.JavaMail.zimbra@audinate.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_150229_1781688700.1391142884975" X-Mailer: Zimbra 8.0.6_GA_5922 (ZimbraWebClient - FF26 (Mac)/8.0.6_GA_5922) Thread-Topic: AD review: draft-ietf-avtcore-clksrc-09 Thread-Index: VOZpfEeZWKQ9CtnMigvf0lNSLjybQg== Cc: "avt@ietf.org WG" Subject: Re: [AVTCORE] AD review: draft-ietf-avtcore-clksrc-09 X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Jan 2014 04:34:53 -0000 ------=_Part_150229_1781688700.1391142884975 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hi Richard, I'm flexible, but I'd prefer to do another revision that addresses all comments in one batch. The other comments I have received so far are editorial in nature, so proceeding to IESG review seems appropriate. - aidan ----- Original Message ----- | From: "Richard Barnes" | To: "Aidan Williams" | Cc: "avt@ietf.org WG" | Sent: Friday, 31 January, 2014 11:04:53 AM | Subject: Re: [AVTCORE] AD review: draft-ietf-avtcore-clksrc-09 | Hey Aidan, | Would you like to go ahead and revise the document before it goes to the IESG | for evaluation? Or we can handle these with any IESG comments. | --Richard | On Tue, Jan 28, 2014 at 4:19 PM, Aidan Williams < aidan.williams@audinate.com | > wrote: | | Hi Richard, | | | Thanks for the review. Responses are inline below... | | | | From: "Richard Barnes" | | | | | | To: " avt@ietf.org WG" < avt@ietf.org > | | | | | | Sent: Sunday, 29 December, 2013 12:25:39 PM | | | | | | Subject: [AVTCORE] AD review: draft-ietf-avtcore-clksrc-09 | | | | | | I have reviewed this document in preparation for IETF LC. Overall, it | | | reads | | | quite well. Thanks! I have requested a LC. | | | | | | A couple of comments that you can consider with LC comments: | | | | | | -- It seems like a reader familiar with | | | draft-ietf-avtext-rtp-grouping-taxonomy might be surprised by these | | | terms. | | | Given that that document is still in development, I don't expect you to | | | be | | | able to use the terms there. However, it might be helpful to add a note | | | saying that you are not attempting to align with their terminology. | | | | | It is great that there is a document attempting to define terminology | | clearly | | (it would have been awesome to have it for this draft!), but I'm not sure | | how to go about addressing your comment since we probably don't want to | | refer to the above draft explicitly. At present, there is a positive | | statement: "here are the definitions". Can you say a bit more about what | | you | | would like to see? | | | | -- GLONASS? | | | | | Happy to add this. | | | | -- Behavior with traceable clocks seems underspecified to me. Section 4.7 | | | should say explicitly that traceable clocks are marked with the | | | ":traceable" | | | suffix or the "/traceable/" identifier. With regard to NTP/PTP servers, | | | how | | | does the user of the clock know that the server is traceable? Is this | | | indicated in-band to those protocols? Would it not be useful to be able | | | to | | | indicate that those servers provide traceable time? | | | | | Marking a clock as traceable allows additional information (e.g. IP | | addresses, PTP master identifiers and the like) to be omitted from the SDP | | since any traceable clock available at the answerer is considered to be an | | appropriate timestamp reference clock. For example, an offerer could could | | specify ts-refclk:ntp=/traceable/ and the answerer could use GPS as a | | reference clock since GPS is a source of traceable time. | | | Would some additional sentences such as these address your comment? | | | regards | | | aidan | | | ____ | | | :wq! | | | | --Richard | | | | | | _______________________________________________ | | | | | | Audio/Video Transport Core Maintenance | | | | | | avt@ietf.org | | | | | | https://www.ietf.org/mailman/listinfo/avt | | | ------=_Part_150229_1781688700.1391142884975 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hi Richard,

I'= m flexible, but I'd prefer to do another revision that addresses all commen= ts in one batch.

The other comments I have receive= d so far are editorial in nature, so proceeding to IESG review seems approp= riate.

- aidan

From: "Richard Barnes" <rlb@ipv.sx>
To: "Aida= n Williams" <aidan.williams@audinate.com>
Cc: "avt@ietf.org= WG" <avt@ietf.org>
Sent: Friday, 31 January, 2014 11:04:53= AM
Subject: Re: [AVTCORE] AD review: draft-ietf-avtcore-clksrc-0= 9

Hey Aidan,

Would yo= u like to go ahead and revise the document before it goes to the IESG for e= valuation?  Or we can handle these with any IESG comments.
<= br>
--Richard


=
On Tue, Jan 28, 2014 at 4:19 PM, Aidan Wil= liams <aida= n.williams@audinate.com> wrote:
Hi Richard,

Thanks = for the review.  Responses are inline below...


From: "Richard B= arnes" <rlb@ipv.sx>
To: "avt@ietf.org WG" = <avt@ietf.org>
Sent: Sunday, 29 December,= 2013 12:25:39 PM
Subject: [AVTCORE] AD review: draft-ietf-avtcor= e-clksrc-09


=
I have reviewed this document in preparation for I= ETF LC.  Overall, it reads quite well.  Thanks!   I hav= e requested a LC.

A couple of comments that you can= consider with LC comments:

-- It seems like a read= er familiar with draft-ietf-avtext-rtp-grouping-taxonomy might be surprised= by these terms.  Given that that document is still in development, I = don't expect you to be able to use the terms there.  However, it might= be helpful to add a note saying that you are not attempting to align with = their terminology.
It is great that there is a document attempting to define terminolog= y clearly (it would have been awesome to have it for this draft!), but I'm = not sure how to go about addressing your comment since we probably don't wa= nt to refer to the above draft explicitly.  At present, there is a pos= itive statement: "here are the definitions".  Can you say a bit more a= bout what you would like to see?

-- GLONASS?
<= /div>
Happy to add this.
=

-- Behavior with traceable clocks seems u= nderspecified to me.  Section 4.7 should say explicitly that traceable= clocks are marked with the ":traceable" suffix or the "/traceable/" identi= fier.  With regard to NTP/PTP servers, how does the user of the clock = know that the server is traceable?  Is this indicated in-band to those= protocols?  Would it not be useful to be able to indicate that those = servers provide traceable time? 
Marking a clock as traceable allows additional i= nformation (e.g. IP addresses, PTP master identifiers and the like) to be o= mitted from the SDP since any traceable clock available at the answerer is = considered to be an appropriate timestamp reference clock.  For exampl= e, an offerer could could specify ts-refclk:ntp=3D/traceable/ and the answe= rer could use GPS as a reference clock since GPS is a source of traceable t= ime.

Would some additional sentences such as t= hese address your comment?

regards
        aidan
____
<= /div>
:wq!

--Richard

_______________________________________= ________
Audio/Video Transport Core Maintenance
avt@ietf= .org
https:= //www.ietf.org/mailman/listinfo/avt



------=_Part_150229_1781688700.1391142884975--