[AVTCORE] Holding draft-ietf-avtcore-rtp-multi-stream in Auth48 waiting for references
Magnus Westerlund <magnus.westerlund@ericsson.com> Thu, 31 March 2016 07:02 UTC
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id 10CB512D851
for <avt@ietfa.amsl.com>; Thu, 31 Mar 2016 00:02:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01,
RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001]
autolearn=ham autolearn_force=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 PKRogtNAVgdZ for <avt@ietfa.amsl.com>;
Thu, 31 Mar 2016 00:02:53 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 234B712D821
for <avt@ietf.org>; Thu, 31 Mar 2016 00:02:52 -0700 (PDT)
X-AuditID: c1b4fb25-f79f86d00000400a-29-56fccb9b19b6
Received: from ESESSHC009.ericsson.se (Unknown_Domain [153.88.183.45])
by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id
61.D9.16394.B9BCCF65; Thu, 31 Mar 2016 09:02:51 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com
(153.88.183.47) with Microsoft SMTP Server id 14.3.248.2; Thu, 31 Mar 2016
09:02:50 +0200
To: IETF AVTCore WG <avt@ietf.org>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <56FCCB9A.8050401@ericsson.com>
Date: Thu, 31 Mar 2016 09:02:50 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
Thunderbird/38.6.0
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrPLMWRmVeSWpSXmKPExsUyM2K7ru7s03/CDM58kLJ42bOS3WJ+52l2
iyctP5gdmD2WLPnJ5LFj8wNWj1k7n7AEMEdx2aSk5mSWpRbp2yVwZbR17WEueC5QcX3+fcYG
xie8XYycHBICJhIrf85gg7DFJC7cWw9kc3EICRxhlHh86gkzhLOcUWLCwX3MIFUiAkoSOyZt
A7I5OJgFvCWmTY0ECbMJWEjc/NEINkhYIFzi+MZWVhCbV0BbYt+s2ewg5SwCqhLrvueChEUF
YiSOvzvHCFEiKHFy5hMWiIn2Eg+2loGEmQXkJZq3zgZbKgQ0paGpg3UCI/8sJB2zEDpmIelY
wMi8ilG0OLU4KTfdyFgvtSgzubg4P08vL7VkEyMwGA9u+a26g/HyG8dDjAIcjEo8vAta/oQJ
sSaWFVfmHmKU4GBWEuF9dgwoxJuSWFmVWpQfX1Sak1p8iFGag0VJnJf10+UwIYH0xJLU7NTU
gtQimCwTB6dUA2Ptu+7Hp7NynrIcmsfEdJilqfj+1KTbs5OWfI+sZUzQbP7TOUWjvZLn0OfZ
RzX+GHzOKmpr0ZqjLpbzpXPz4pzHIRu3TVRu49O7kqh779OlJdzGX3lkFz39+ClnVzDH+a0T
+vK3mfzR0dRZmH/vW93D5YXf7zafvVb8knnakZ/Gz5qkPzkzZexTYinOSDTUYi4qTgQAucnY
zEICAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/XyjmZxiTyBh0oq-BjUqha0hFOzg>
Subject: [AVTCORE] Holding draft-ietf-avtcore-rtp-multi-stream in Auth48
waiting for references
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>,
<mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>,
<mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2016 07:02:55 -0000
WG, This is written as one of the authors of draft-ietf-avtcore-rtp-multi-stream. We are currently in AUTH48 and are mostly done with our reviews. However, we have come to the conclusion that we have a number of important informational references in this document to its sibling documents. These documents are: draft-ietf-avtcore-rtp-multi-stream-optimisation: The optimization for reporting when having multiple SSRCs per endpoint. We think this is the most important reference as it is so closely tied. draft-ietf-avtcore-multi-media-rtp-session is one of the motivating usages for why this clarification is needed. Thus good to get a proper reference to its RFC rather than a draft name. draft-ietf-mmusic-sdp-bundle-negotiation is much less important from this document context, however it is anyway a normative reference for draft-ietf-avtcore-rtp-multi-stream-optimisation and will thus be available if we wait for the optimization one. We authors think it would be really good to have these reference as RFCs rather than drafts. Thus our proposal is to actually hold the publication of this document until the time all three of the above can be published. Thus our question to the WG is two fold. Are there anyone that will have a significant issue with holding the publication of this document until the above documents are available? Considering that the AVTCORE ones already are in the RFC-editor queue, the blocking document that we need to wait for is draft-ietf-mmusic-sdp-bundle-negotiation. The second question is if people agree with us that it would be good to hold the publication? 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 ----------------------------------------------------------------------
- [AVTCORE] Holding draft-ietf-avtcore-rtp-multi-st… Magnus Westerlund