[Rmt] FLUTE SDP specification

Jani Peltotalo <jani.peltotalo@tut.fi> Wed, 23 June 2010 17:29 UTC

Return-Path: <jani.peltotalo@tut.fi>
X-Original-To: rmt@core3.amsl.com
Delivered-To: rmt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DCC0F3A6842 for <rmt@core3.amsl.com>; Wed, 23 Jun 2010 10:29:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kHwc7jJou+2A for <rmt@core3.amsl.com>; Wed, 23 Jun 2010 10:29:52 -0700 (PDT)
Received: from mail-gw2.cc.tut.fi (mail-gw2.cc.tut.fi [130.230.160.16]) by core3.amsl.com (Postfix) with ESMTP id 6DFE73A6857 for <rmt@ietf.org>; Wed, 23 Jun 2010 10:29:51 -0700 (PDT)
X-AuditID: 82e6a010-b7c01ae0000009dc-17-4c22449685d2
Received: from mail.cc.tut.fi (mail.cc.tut.fi [130.230.1.120]) by mail-gw2.cc.tut.fi (Symantec Brightmail Gateway) with SMTP id 4E.84.02524.694422C4; Wed, 23 Jun 2010 20:29:58 +0300 (EEST)
Received: from [130.230.52.111] (wireless7.atm.tut.fi [130.230.52.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.cc.tut.fi (Postfix) with ESMTP id 29C2BA4157 for <rmt@ietf.org>; Wed, 23 Jun 2010 20:29:58 +0300 (EEST)
Message-ID: <4C22448F.3050704@tut.fi>
Date: Wed, 23 Jun 2010 20:29:51 +0300
From: Jani Peltotalo <jani.peltotalo@tut.fi>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.1.10) Gecko/20100512 Lightning/1.0b1 Thunderbird/3.0.5
MIME-Version: 1.0
To: rmt@ietf.org
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Subject: [Rmt] FLUTE SDP specification
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rmt>, <mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rmt>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmt>, <mailto:rmt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jun 2010 17:29:53 -0000

Dear RMTers,

We are currently updating the FLUTE SDP specification and at this point
we need to clarify three issues:

1. Our understanding is that ALC, LCT and FLUTE sessions must
originate from a single sender and therefore from a single IP address.
There is some confusing text of discussing ASM/SSM models in the ALC,
LCT and FLUTE specifications. It is our understanding that ASM/SSM
discussion only relates to IP level routing and (e.g., IGMP) joining of
IP multicast groups. Does anyone disagree with this? (And more
critically is anyone aware of implementation that is incompatible with
our understanding.)

2. FLUTE SDP defines the Composite Session token so that multiple FLUTE
sessions can be described in a single SDP object/instance/file (for
efficiency and encapsulation). To enable this the 05-version of the
specification promotes one media (channel) to be the Primary Media where
things like source IP address are defined for all media / channel for a
single FLUTE session. The specification currently says: "The first media
line declared for a Composite Session group is the Primary Media.".
However, we propose to change this to: "The first (leftmost) mid value
declared for a Composite Session group is the Primary Media.". This
should make reading and writing the SDP simpler and less prone to
errors. Because of the convention of declaring the group's mid values in
the same order as the media lines we anticipate no compatibility
breakages. Does anyone disagree with this?

3. ALC, LCT and FLUTE specify: "Each TSI MUST uniquely identify a
FLUTE session for a given source IP address during the time that the
session is active and also for a large time before and after the active
session time.". In SDP, the t-field is mandatory and this field is used
to specify precise time. We would like to fully specify what is meant by
large time. We propose 60 minutes. We will also clarify the best
practise use of SDP session times (especially with unbounded and
permanent sessions) in MMUSIC working group. Will this make anyone happy
on unhappy?

BR,

Jani Peltotalo