Re: [splices] FW: New Version Notification for draft-loreto-splices-disaggregated-media-02.txt

"Worley, Dale R (Dale)" <dworley@avaya.com> Thu, 07 July 2011 18:56 UTC

Return-Path: <dworley@avaya.com>
X-Original-To: splices@ietfa.amsl.com
Delivered-To: splices@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E71C01F0CAF for <splices@ietfa.amsl.com>; Thu, 7 Jul 2011 11:56:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.501
X-Spam-Level:
X-Spam-Status: No, score=-103.501 tagged_above=-999 required=5 tests=[AWL=0.098, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sIIT62ovVJ0e for <splices@ietfa.amsl.com>; Thu, 7 Jul 2011 11:56:00 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 69B4D1F0CAE for <splices@ietf.org>; Thu, 7 Jul 2011 11:56:00 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAGgAFk7GmAcF/2dsb2JhbABTpzZ3sCMCmx6GOASXYYtC
X-IronPort-AV: E=Sophos;i="4.65,494,1304308800"; d="scan'208";a="289392646"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 07 Jul 2011 14:55:59 -0400
Received: from unknown (HELO DC-US1HCEX4.global.avaya.com) ([135.11.52.35]) by co300216-co-erhwest-out.avaya.com with ESMTP; 07 Jul 2011 14:54:43 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.172]) by DC-US1HCEX4.global.avaya.com ([135.11.52.35]) with mapi; Thu, 7 Jul 2011 14:55:59 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Salvatore Loreto <salvatore.loreto@ericsson.com>
Date: Thu, 07 Jul 2011 14:56:00 -0400
Thread-Topic: [splices] FW: New Version Notification for draft-loreto-splices-disaggregated-media-02.txt
Thread-Index: Acw8v5R5jk7sM3ZLTjS2H6Zlgg1brgAFxEUy
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222B1F574C@DC-US1MBEX4.global.avaya.com>
References: <6369CB70BFD88942B9705AC1E639A33822CE7CF83F@DC-US1MBEX4.global.avaya.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F573A@DC-US1MBEX4.global.avaya.com>, <4E14B1ED.6070900@ericsson.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F573B@DC-US1MBEX4.global.avaya.com>, <4E15D911.2050402@ericsson.com>
In-Reply-To: <4E15D911.2050402@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "splices@ietf.org" <splices@ietf.org>
Subject: Re: [splices] FW: New Version Notification for draft-loreto-splices-disaggregated-media-02.txt
X-BeenThere: splices@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Loosely-coupled SIP Devices \(splices\) working group discussion list" <splices.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/splices>, <mailto:splices-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/splices>
List-Post: <mailto:splices@ietf.org>
List-Help: <mailto:splices-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/splices>, <mailto:splices-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jul 2011 18:56:01 -0000

________________________________________
From: Salvatore Loreto [salvatore.loreto@ericsson.com]

what you show in the below diagrams are media streams not dialog, isn't it?

if so, the "near-end managed" is not really clear to me:
what the UA, the one managing all of its UAs, is supposed to do with the
media streams
that passes trough it?
________________________________________

The drawings are taken from your draft, and yes, they aren't truly parallel to each other.

In the "near-end managed" version, called "Centralized scenario" in fig. 2, the
bundles of lines represent SIP dialogs, the individual lines are the media streams
as represented in the SDP carries in the dialogs.  In that sense, all 4 streams go
"though" the two coordinating UAs, in that those UAs pass through the SDP lines
that describe them.  Of course, the media packets themselves go directly from one
endpoint UA to another.

In the "far-end managed" version, called "distributed scenario" near fig. 9, there
are two groups of UAs, and there are 4 SIP dialogs between them, each dialog responsible
for one of the 4 media streams.  So the lines represent SIP dialogs as well as media streams.

The overall idea though, is that disaggregation (or aggregation, if you want to describe it)
is being done at both ends; both Alice and Bob have multiple UA devices they wish to operate
as if they were single UAs.

Having a mechanism that works in this situation should be a requirement, IMO.

Dale