[MMUSIC] M-lines: Wikifying it

Harald Alvestrand <harald@alvestrand.no> Wed, 28 November 2012 14:50 UTC

Return-Path: <harald@alvestrand.no>
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 0054B21F887A for <mmusic@ietfa.amsl.com>; Wed, 28 Nov 2012 06:50:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.598
X-Spam-Level:
X-Spam-Status: No, score=-110.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, 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 LhQdRVTWVnis for <mmusic@ietfa.amsl.com>; Wed, 28 Nov 2012 06:50:56 -0800 (PST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 8E2A021F859D for <mmusic@ietf.org>; Wed, 28 Nov 2012 06:50:55 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 1DDC039E1C2 for <mmusic@ietf.org>; Wed, 28 Nov 2012 15:50:54 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5kmbCWc-VMSM for <mmusic@ietf.org>; Wed, 28 Nov 2012 15:50:52 +0100 (CET)
Received: from [192.168.1.107] (unknown [188.113.88.47]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 985E039E056 for <mmusic@ietf.org>; Wed, 28 Nov 2012 15:50:52 +0100 (CET)
Message-ID: <50B624CC.4010501@alvestrand.no>
Date: Wed, 28 Nov 2012 15:50:52 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: mmusic <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="------------000407040007040107030804"
Subject: [MMUSIC] M-lines: Wikifying it
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 28 Nov 2012 14:50:58 -0000

Perhaps we can do some real work rather than just disagreeing on principles.

Perhaps the most contentious issue now is "what should an M-line be".
As far as I can tell, M-lines and their parameters describe 3 things:

- Properties of the transport flow / RTP session (Transport, or T for short)
- Properties that make sense to apply to an individual media stream, and 
may need to be different for different media streams in the same 
combined RTP session (Flow, or F for short)
- Properties that make sense to apply to all streams of a given type 
(Media, or M for short)

The properties that can be represented in M-lines are found in two IANA 
registries, both on
http://www.iana.org/assignments/sdp-parameters/sdp-parameters.xml:

- att-field (both session and media level)
- att-field (media level only)

I make it 179 entries in these categories, combined.

I see the same kind of work being necessary no matter which way we go:

- If we go with M-lines describing a whole RTP session (the MMT 
proposal), each property of the "F" class that we stil need needs to be 
copied onto a property in the "att-field (source level)" registry.

- If we go with M-lines describing groups of media streams, degenerating 
to a single media stream in the case of using "a=inactive" for stream 
muting (the BUNDLE and TOGETHER proposals), each property of the "T" 
class needs to be described as "MUST have consistent values for all the 
combined M-lines", "MUST be taken only from the first M-line in the 
bundle argument", or "must get special treatment".

- In both cases, the "M"-class lines don't need any special treatment. 
They just need to be present in all the M-lines where they're relevant.

I've created a spreadsheet here:

https://docs.google.com/spreadsheet/ccc?key=0Av-aF69sk5C6dDhPblpRV2pkbXVGNV9lUFI3cHlIRFE

with 2 extra columns: "Class" (M, F or T) and "Importance" (1 for 
"necessary" and 0 for "will never matter").

Anyone should be able to write it.
If a few of us do a quick job of markup on it, I think we should be able 
to have a more realistic assessment in a few days.

I've started, but much of this is unknown to me. Can others help?

                       Harald