Re: [AVTCORE] Moving draft-ietf-avtcore-multiplex-guidelines along
Barry Leiba <barryleiba@computer.org> Fri, 14 February 2020 04:41 UTC
Return-Path: <barryleiba@gmail.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 4C5F612004D; Thu, 13 Feb 2020 20:41:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level:
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 m5sMCvNSlAvp; Thu, 13 Feb 2020 20:41:45 -0800 (PST)
Received: from mail-io1-f47.google.com (mail-io1-f47.google.com [209.85.166.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D7C78120044; Thu, 13 Feb 2020 20:41:41 -0800 (PST)
Received: by mail-io1-f47.google.com with SMTP id z8so9193801ioh.0; Thu, 13 Feb 2020 20:41:41 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=q9lCEbDWnCFXJSQtOyW5v2ko3NTqs51LVgL84gFFSy0=; b=jkd1cxp2/0XCekFZdTgZ7Pr9VRPOyszN/D/QWOo/rE/eNeerCM1OK2CKEBiAt2Yerr T+KHEE31WCF5P8FA4oc/74OCQgpqjsBMNgRazdLppSEN+EJZ1WgaRXqm33WxBVX1d+qM FaJ0ETCj2jW+jjXjsvyL420eeZAKwCMYHSCY+YSerIzbm+hvVGxCRrAUMf0rnSPtM+2a x4jrsgFXQGubU9ehXSCzm9FoDXKZ+Deua8LpcWZd0DarYACCdOY5z7nWVdYNJ6Kpf69y hW6D332P1FZtKeK2N/QkNroVhI/JoHCwmJ3X0Br1VoAYUGGK84UWLQbuMtKFSKH58d78 /UzQ==
X-Gm-Message-State: APjAAAWzHrAKPW2wbNFSfmtcUphJohZVNhZ7hH/P1hPn2x9rn6UpvjjC v4lB3u+LHmd8vogTtwJ1w53Y5+PhSMxcu4vLA9c=
X-Google-Smtp-Source: APXvYqx+/NhUP3YO9OnH3WNWfk64Iqt0/xY6PO1Dljbvc0CFLJSfxQ8wK01Gjjsk1/BXZEBcq1jpOoWFoBIEXws36lI=
X-Received: by 2002:a5d:9a85:: with SMTP id c5mr818100iom.266.1581655300867; Thu, 13 Feb 2020 20:41:40 -0800 (PST)
MIME-Version: 1.0
References: <CALaySJ+FVGYTStOVYjarR_UtPG5Ksm8hKDD2DdXQLYgQO3zRrg@mail.gmail.com> <DB7PR07MB5736513571AA3CFD7E16574795B00@DB7PR07MB5736.eurprd07.prod.outlook.com> <CALaySJ+xsk-CVmvbwcNP31J8kLsQd4hLfQh1OT-gDBhzsqCaAA@mail.gmail.com> <HE1PR0701MB2697A398E78C5C636B42C49B954F0@HE1PR0701MB2697.eurprd07.prod.outlook.com> <CALaySJKMzcsAU4d6sr5Fdk-Z_OSK=MyHd9no13bnawKzfZKC6Q@mail.gmail.com> <HE1PR07MB32596CC0FC216BA57A273DB98D420@HE1PR07MB3259.eurprd07.prod.outlook.com>
In-Reply-To: <HE1PR07MB32596CC0FC216BA57A273DB98D420@HE1PR07MB3259.eurprd07.prod.outlook.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Fri, 14 Feb 2020 04:41:30 +0000
Message-ID: <CALaySJJ+7AVLbTEFPg-kBiw-tjck_UekVWDcFn9-6-84XHqYcw@mail.gmail.com>
To: Bo Burman <bo.burman@ericsson.com>
Cc: Bernard Aboba <bernard.aboba@gmail.com>, Magnus Westerlund <magnus.westerlund@ericsson.com>, "avt@ietf.org" <avt@ietf.org>, "draft-ietf-avtcore-multiplex-guidelines.all@ietf.org" <draft-ietf-avtcore-multiplex-guidelines.all@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005d8b50059e81d29e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/EYV6gBpMuFe8e0ZJhqZ4RpDforA>
Subject: Re: [AVTCORE] Moving draft-ietf-avtcore-multiplex-guidelines along
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 14 Feb 2020 04:41:46 -0000
Hi... any progress on this? Barry On Tue, Dec 3, 2019 at 7:03 AM Bo Burman <bo.burman@ericsson.com> wrote: > Hi, > > I've started a (so far author-internal) draft -10 that tries to address > most > of Bernard's comments; in progress. > > I however didn't yet do a total re-haul to consider if use of MID/RID/RRID > is > sufficiently covered and described throughout the document. Help on > identifying potentially impacted text would be greatly appreciated, from > my > co-authors as well as from the list. > > Regarding Bernard's comment to section 5.2: > > > 3. For applications with dynamic usage of RTP streams, i.e. > > frequently added and removed, having much of the state associated > > with the RTP session rather than per individual SSRC can avoid > > the need for in-session signalling of meta-information about each > > SSRC. > > > > [BA] Not sure I grasp your point here. If there are multiple SSRCs in > the > > same RTP session, avoiding the need for in-session signaling typically > > requires: > > > > a. A mechanism for handling "unsignaled streams" (e.g. an Unhandled RTP > > event as in ORTC), OR > > > > b. Support for MID to allow routing to the correct RTP receiver without > > in-session signaling of the SSRC. > > Firstly, I think the original text in bullet 3 doesn't consider use of > bundle > or MID but rather assumes the pre-bundle type of RTP session. Adding use > of > MID would be part of an RTP session state (e.g. mapping SSRC to an media > source, which would also map to an m= line if SDP is used) that doesn't > require in-session signaling. That would correspond to your alternative b. > > Secondly, there could still be "unsignaled streams" handling, either > within > (using same) MID or when not using MID in the RTP session, where other RTP > session information can be used to allow proper handling of dynamically > occuring RTP streams, such as e.g. RTCP SDES CNAME to identify RTP streams > sent from the same endpoint (but not necessarily the same media source). > What > type of RTP session information that is needed for proper RTP stream > handling > depends on, I must assume, application-dependent requirements. That would > correspond to your alternative a. > > Bernard, you indicate "a OR b" above; should they be seen as mutually > exclusive or could they both apply in the way I indicate? Would adding a > clarification along the lines above address your concern? > > Cheers, > /Bo > > > -----Original Message----- > > From: Barry Leiba <barryleiba@computer.org> > > Sent: den 20 november 2019 07:22 > > To: Magnus Westerlund <magnus.westerlund@ericsson.com> > > Cc: draft-ietf-avtcore-multiplex-guidelines.all@ietf.org; avt@ietf.org > > Subject: Re: Moving draft-ietf-avtcore-multiplex-guidelines along > > > > Thanks; I'd love to move it forward. > > > > b > > > > On Wed, Nov 20, 2019 at 2:20 PM Magnus Westerlund > > <magnus.westerlund@ericsson.com> wrote: > > > > > > Hi Barry, > > > > > > Sorry, this has failed to get the necessary author time to take care > > > of the comments. Will try to get it done soonish. > > > > > > Cheers > > > > > > Magnus Westerlund > > > > > > >
- [AVTCORE] Moving draft-ietf-avtcore-multiplex-gui… Barry Leiba
- Re: [AVTCORE] Moving draft-ietf-avtcore-multiplex… Magnus Westerlund
- Re: [AVTCORE] Moving draft-ietf-avtcore-multiplex… Barry Leiba
- Re: [AVTCORE] Moving draft-ietf-avtcore-multiplex… Magnus Westerlund
- Re: [AVTCORE] Moving draft-ietf-avtcore-multiplex… Barry Leiba
- Re: [AVTCORE] Moving draft-ietf-avtcore-multiplex… Bo Burman
- Re: [AVTCORE] Moving draft-ietf-avtcore-multiplex… Bernard Aboba
- Re: [AVTCORE] Moving draft-ietf-avtcore-multiplex… Barry Leiba
- Re: [AVTCORE] Moving draft-ietf-avtcore-multiplex… Magnus Westerlund
- Re: [AVTCORE] Moving draft-ietf-avtcore-multiplex… Magnus Westerlund
- Re: [AVTCORE] Moving draft-ietf-avtcore-multiplex… Barry Leiba
- Re: [AVTCORE] Moving draft-ietf-avtcore-multiplex… Bernard Aboba
- Re: [AVTCORE] Moving draft-ietf-avtcore-multiplex… Barry Leiba
- Re: [AVTCORE] Moving draft-ietf-avtcore-multiplex… Colin Perkins
- Re: [AVTCORE] Moving draft-ietf-avtcore-multiplex… Roni Even (A)
- Re: [AVTCORE] Moving draft-ietf-avtcore-multiplex… Magnus Westerlund
- Re: [AVTCORE] Moving draft-ietf-avtcore-multiplex… Colin Perkins
- Re: [AVTCORE] Moving draft-ietf-avtcore-multiplex… Magnus Westerlund