Re: [MMUSIC] Fwd: New Version Notification for draft-abhishek-mmusic-overlay-grouping-00.txt

Rohit Abhishek <rabhishek@rabhishek.com> Mon, 02 November 2020 16:18 UTC

Return-Path: <rabhishek@rabhishek.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A7203A0AE3 for <mmusic@ietfa.amsl.com>; Mon, 2 Nov 2020 08:18:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rabhishek.com
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 agxM0ezqruD8 for <mmusic@ietfa.amsl.com>; Mon, 2 Nov 2020 08:18:12 -0800 (PST)
Received: from mail-qv1-xf33.google.com (mail-qv1-xf33.google.com [IPv6:2607:f8b0:4864:20::f33]) (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 B56FB3A0982 for <mmusic@ietf.org>; Mon, 2 Nov 2020 08:18:12 -0800 (PST)
Received: by mail-qv1-xf33.google.com with SMTP id t20so6346002qvv.8 for <mmusic@ietf.org>; Mon, 02 Nov 2020 08:18:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rabhishek.com; s=google; h=from:to:subject:thread-topic:thread-index:date:message-id :references:in-reply-to:accept-language:content-language :mime-version; bh=muYS77BeaPWM1/ixzW5jggNLxINWHze8E7QmsK3+BcY=; b=iQJtAstQe9xXKbtBytl5mt09YfyUf9NKEE6IK+l8enDQrx9hYyRTnLW2qtb/hGbpLD 6+0mSwkuVi5pIqgNUuPAbqCKi43wUCGBC0s7oNcdhgh15gbOhuwqt4TlpmyjSPMZS75N mMQESdcMNP0hqNcQIFrWEHnvrqaE8vLFZGscB6i9ISq8VkNwiWV0fr+px8UhUX1XTZwr +XygRqKR3axaUTxCYPtPzz2RIpyhE97PfRN8DQIhB7GRP820n/68L6dUrbEksFMdrsB7 ufOhRh39rktfLAqlHwiG5LPgeks8ukbFB+t0F3vLt90E9aNBq6IMPxeB7P6dC+Uy+9WO VW2g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:thread-topic:thread-index:date :message-id:references:in-reply-to:accept-language:content-language :mime-version; bh=muYS77BeaPWM1/ixzW5jggNLxINWHze8E7QmsK3+BcY=; b=O1J6eh0vl2OPP175ATiOEpCzSIFbC+tYeGMTr5GbhhVth7ekh1OwV39buVZOlZOqOX E7chk7UwlCpLncIRSJUsvgdEEuLvBL5FZydzxigdk+70cnLAq26GeDWFJZKgEOfzmqAL OMX9hAn7yKTgm4hCUdqc7E6UB8K392HHdlnVBkziVSkQOozSp3rlbwgCZjD9hRYzp6Xo oTK/X5mfSpbtnTWCKM8gxJIWPY2S3z6cJ/Jb66t8XrR0lCp9io5s/j+qefSWYqQ6LdZx T+AdxPAPmiJsY5IGti9DzOFY3X2Sv8ANzkzVQq4i1Go96Z0MdVUQ067+2oiRW4vvyCiW wKFw==
X-Gm-Message-State: AOAM530B+GiZ+pSpXYOizZLPsQEeOLkysHUgS0tj+tYT8RvF+3tkelwC eIyOJaHTlgTpPyvHmDKGSSsIow==
X-Google-Smtp-Source: ABdhPJwR2mVvScpHQngmoPhurRN2ajpNO0Rx8VN73UIQikZs6gq46SPTiSgILJ5DPHyGl8/0vEsX0A==
X-Received: by 2002:a05:6214:1341:: with SMTP id b1mr18117216qvw.54.1604333891636; Mon, 02 Nov 2020 08:18:11 -0800 (PST)
Received: from BLAPR07MB7572.namprd07.prod.outlook.com ([2603:1036:302:5027::5]) by smtp.gmail.com with ESMTPSA id 67sm8112899qkd.14.2020.11.02.08.18.10 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 02 Nov 2020 08:18:10 -0800 (PST)
From: Rohit Abhishek <rabhishek@rabhishek.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Fwd: New Version Notification for draft-abhishek-mmusic-overlay-grouping-00.txt
Thread-Index: ATUzMTA5XOKQvhBnm/+YIzsfjz0d1EFiQmllwOqQDACABmMCOw==
X-MS-Exchange-MessageSentRepresentingType: 1
Date: Mon, 02 Nov 2020 16:18:09 +0000
Message-ID: <BLAPR07MB757280ABF64D0C4A7A1CE197F3100@BLAPR07MB7572.namprd07.prod.outlook.com>
References: <160383579701.1505.5863140495031626135@ietfa.amsl.com> <CAPoeGLXGue9fVB0rOM8i0vM2GFH7GBTb0i2QPzNbsUx_gVXNXA@mail.gmail.com> <AM0PR07MB386056222151187D9614FBE993140@AM0PR07MB3860.eurprd07.prod.outlook.com>
In-Reply-To: <AM0PR07MB386056222151187D9614FBE993140@AM0PR07MB3860.eurprd07.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-Exchange-Organization-SCL: -1
X-MS-TNEF-Correlator:
X-MS-Exchange-Organization-RecordReviewCfmType: 0
Content-Type: multipart/alternative; boundary="_000_BLAPR07MB757280ABF64D0C4A7A1CE197F3100BLAPR07MB7572namp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/OiJqJMxjJgaEZuj7wi9hUmk3lPY>
Subject: Re: [MMUSIC] Fwd: New Version Notification for draft-abhishek-mmusic-overlay-grouping-00.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Nov 2020 16:18:15 -0000

Hi Christer,

Thanks for reading the draft and your reviews. I really appreciate your feedback. The questions here suggest more explanatory text about motivation is needed. I will address these in the next version.

From: Christer Holmberg <christer.holmberg@ericsson.com>
Date: Thursday, October 29, 2020 at 7:46 AM
To: Rohit Abhishek <rabhishek@rabhishek.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: RE: [MMUSIC] Fwd: New Version Notification for draft-abhishek-mmusic-overlay-grouping-00.txt

Hi Rohit,

A few initial questions for clarifications:
RA: The assumption here is for an immersive telepresence session, one immersive video will be transmitted, whereas other streams will be transmitted as overlays. For ex, consider 10 people in a conference call; a user may stream an immersive video from one user, whereas 2D videos as overlays from other 8 participants (plus additional streams if any participant shares any additional media) . The total overlay streams may vary, for example, a session with a large number of audiences.

Q1:                      The draft references the telepresence use-case spec (RFC7205), but there is no text on why the actual CLUE mechanism isn’t feasible for what you want to do.
RA: I had referred to RFC7205 for definition purposes. CLUE enables interoperability between telepresence systems by exchanging information about the systems’ characteristics. Here, the cameras and screens may be arranged to provide a panoramic view of the remote room.  However, overlays were not considered in the CLUE mechanism.

Q2:                      It is unclear why you need to group the overlay streams together. If you only want to indicate that a stream is for overlay you can e.g., use an SDP attribute for that. You don’t need grouping.
RA: Of course, when a single or relatively fewer overlays are transmitted, grouping won’t be needed. However, when relatively larger numbers of users are in a session, it may be more favorable to use a grouping framework than using SDP attribute for each stream.

Q3:                      The draft talks about the overlay streams being associated with “immersive video”. But, there is no text about how this immersive video stream is represented, and how the overlay streams are associated with that immersive video stream.
RA: Thanks for the suggestion. I will update this in the next version

Q4:                      I assume the overlay streams can be multiplexed using the BUNDLE mechanism?
RA: There maybe multiple RTP sessions whose streams may have to be grouped. Using BUNDLE mechanism will only allow to group media streams within a single RTP session.  However, multiple media streams from various endpoints may be multiplexed into a single RTP session but would require RTP-level middle boxes. These middle boxes may add delay if a large number of streams are to be multiplexed, which even if very less, may not be favorable for telepresence sessions.


Best Regards,
Rohit



Regards,

Christer

From: mmusic <mmusic-bounces@ietf.org> On Behalf Of Rohit Abhishek
Sent: keskiviikko 28. lokakuuta 2020 0.23
To: mmusic@ietf.org
Subject: [MMUSIC] Fwd: New Version Notification for draft-abhishek-mmusic-overlay-grouping-00.txt


Dear All,



I am currently working on an SDP extension facilitating overlays for immersive telepresence.

An individual draft has been posted at

https://www.ietf.org/archive/id/draft-abhishek-mmusic-overlay-grouping-00.txt



Comments are welcome





Best Regards,

Rohit

---------- Forwarded message ---------
From: <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>>
Date: Tue, Oct 27, 2020 at 2:56 PM
Subject: New Version Notification for draft-abhishek-mmusic-overlay-grouping-00.txt
To: Rohit Abhishek <rabhishek@rabhishek.com<mailto:rabhishek@rabhishek.com>>



A new version of I-D, draft-abhishek-mmusic-overlay-grouping-00.txt
has been successfully submitted by Rohit Abhishek and posted to the
IETF repository.

Name:           draft-abhishek-mmusic-overlay-grouping
Revision:       00
Title:          SDP Overlay Grouping framework for immersive telepresence media streams
Document date:  2020-10-27
Group:          Individual Submission
Pages:          8
URL:            https://www.ietf.org/archive/id/draft-abhishek-mmusic-overlay-grouping-00.txt
Status:         https://datatracker.ietf.org/doc/draft-abhishek-mmusic-overlay-grouping/
Htmlized:       https://datatracker.ietf.org/doc/html/draft-abhishek-mmusic-overlay-grouping
Htmlized:       https://tools.ietf.org/html/draft-abhishek-mmusic-overlay-grouping-00


Abstract:
   This document defines semantics that allow for signalling a new SDP
   group "OL" for overlays in an immersive telepresence session.  The
   "OL" attribute can be used by the application to relate all the
   overlay media streams enabling them to be added as overlay on top of
   the immersive video.  The overlay grouping semantics is required, if
   the media data is seperate and transported via different protocols.




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<http://tools.ietf.org>.

The IETF Secretariat