Re: [AVTCORE] draft-ietf-avtcore-multiplex-guidelines references

Colin Perkins <csp@csperkins.org> Wed, 29 March 2017 17:28 UTC

Return-Path: <csp@csperkins.org>
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 578C71294CD for <avt@ietfa.amsl.com>; Wed, 29 Mar 2017 10:28:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 6ksGNYcnC184 for <avt@ietfa.amsl.com>; Wed, 29 Mar 2017 10:28:13 -0700 (PDT)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 303F212944F for <avt@ietf.org>; Wed, 29 Mar 2017 10:28:13 -0700 (PDT)
Received: from [130.209.157.46] (port=9468 helo=glaroam2-177-18.wireless.gla.ac.uk) by balrog.mythic-beasts.com with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from <csp@csperkins.org>) id 1ctHOD-00047z-Se; Wed, 29 Mar 2017 18:28:11 +0100
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <950741FF-FD4D-447D-B778-C950D144DD90@csperkins.org>
Date: Wed, 29 Mar 2017 18:28:08 +0100
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, IETF AVTCore WG <avt@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F41087F4-5D8A-4427-A77A-911ABA7D4672@csperkins.org>
References: <8d59d8b8-2694-be24-8cf3-18fed901a9ae@ericsson.com> <950741FF-FD4D-447D-B778-C950D144DD90@csperkins.org>
To: Colin Perkins <csp@csperkins.org>
X-Mailer: Apple Mail (2.3273)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: State = no_sa; Score =
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/NZzhx4ehZiCFgmz8yBh47omeKBw>
Subject: Re: [AVTCORE] draft-ietf-avtcore-multiplex-guidelines references
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 29 Mar 2017 17:28:15 -0000

> On 29 Mar 2017, at 18:22, Colin Perkins <csp@csperkins.org> wrote:
> 
> Magnus,
> 
> For both draft-ietf-avtcore-multi-media-rtp-session and draft-ietf-rtcweb-rtp-usage, I see be problem removing the reference to multiplexing guidelines in
“no problem”
> AUTH48.
> 
> Colin
> 
> 
> 
>> On 28 Mar 2017, at 15:41, Magnus Westerlund <magnus.westerlund@ericsson.com> wrote:
>> 
>> Hi,
>> 
>> In today's discussion of draft-ietf-avtcore-multiplex-guidelines and what references this document, I have included the sentences which references it below.
>> 
>> They are all of the type: For more information on this topic see this doc.
>> 
>> So this is part of the considerations if we can drop the milestone.
>> 
>> draft-ietf-avtcore-multi-media-rtp-session:
>> 
>> Section 4:
>> 
>>     Further
>>     guidance on how to provide differential treatment for some media
>>     is given in [I-D.ietf-avtcore-multiplex-guidelines] and [RFC7657].
>> 
>> Section 5.3:
>> 
>>  For additional arguments why RTP
>>  payload type based multiplexing of multiple media sources doesn't
>>  work, see [I-D.ietf-avtcore-multiplex-guidelines].
>> 
>> 
>> draft-ietf-mmusic-sdp-simulcast:
>> 
>> Section 8:
>> 
>>  RTP multiplexing alternatives can be found in
>>  Guidelines for Multiplexing in RTP
>>  [I-D.ietf-avtcore-multiplex-guidelines].  Discussion and
>>  clarification on how to handle multiple streams in an RTP session can
>>  be found in [RFC8108].
>> 
>> 
>> draft-ietf-payload-rtp-howto:
>> Section 3.3:
>> 
>>  For more discussion and consideration of how and when to use the
>>  different RTP multiplexing points see
>>  [I-D.ietf-avtcore-multiplex-guidelines].
>> 
>> The above I have proposed to remove in AUTH48.
>> 
>> draft-ietf-rtcweb-rtp-usage:
>> 
>> Section 4.4:
>> 
>>  Further discussion about the suitability of different RTP session
>>  structures and multiplexing methods to different scenarios can be
>>  found in [I-D.ietf-avtcore-multiplex-guidelines].
>> 
>> Cheers
>> 
>> Magnus Westerlund
>> 
>> ----------------------------------------------------------------------
>> Media Technologies, Ericsson Research
>> ----------------------------------------------------------------------
>> Ericsson AB                 | Phone  +46 10 7148287
>> Färögatan 6                 | Mobile +46 73 0949079
>> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>> ----------------------------------------------------------------------
>> 
>> _______________________________________________
>> Audio/Video Transport Core Maintenance
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
> 
> 
> 
> -- 
> Colin Perkins
> https://csperkins.org/
> 
> 
> 
> 
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt



-- 
Colin Perkins
https://csperkins.org/