[MMUSIC] Status of "Hitchhiker's Guide to SDP"

Bert Greevenbosch <Bert.Greevenbosch@huawei.com> Thu, 05 July 2012 06:26 UTC

Return-Path: <Bert.Greevenbosch@huawei.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 C612211E80A3 for <mmusic@ietfa.amsl.com>; Wed, 4 Jul 2012 23:26:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hq56EASU9xvr for <mmusic@ietfa.amsl.com>; Wed, 4 Jul 2012 23:26:06 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 1E69711E8079 for <mmusic@ietf.org>; Wed, 4 Jul 2012 23:26:06 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AHL29689; Thu, 05 Jul 2012 02:26:18 -0400 (EDT)
Received: from DFWEML407-HUB.china.huawei.com (10.193.5.132) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 4 Jul 2012 23:25:58 -0700
Received: from SZXEML419-HUB.china.huawei.com (10.82.67.158) by dfweml407-hub.china.huawei.com (10.193.5.132) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 4 Jul 2012 23:26:03 -0700
Received: from SZXEML509-MBS.china.huawei.com ([10.82.67.53]) by szxeml419-hub.china.huawei.com ([10.82.67.158]) with mapi id 14.01.0323.003; Thu, 5 Jul 2012 14:25:54 +0800
From: Bert Greevenbosch <Bert.Greevenbosch@huawei.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Status of "Hitchhiker's Guide to SDP"
Thread-Index: Ac1adwdyKake702nQZeBSXLg/TheQw==
Date: Thu, 05 Jul 2012 06:25:53 +0000
Message-ID: <46A1DF3F04371240B504290A071B4DB629054D47@szxeml509-mbs>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.70.110.143]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [MMUSIC] Status of "Hitchhiker's Guide to SDP"
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: Thu, 05 Jul 2012 06:26:06 -0000

Hello all,

I have just uploaded a new version of the "Hitchhiker's Guide to SDP" draft:
http://datatracker.ietf.org/doc/draft-greevenbosch-mmusic-hitchhikersguide-sdp/

The main work done was identifying the drafts related to SDP, SIP, Megaco and RTSP. Gonzalo Salguiero and Yue Peiyu (Roy) have helped in this. In addition, I have copied some text from the original "Hitchhiker's Guide to SDP" (RFC 5411).

This is the current state of the work. However, we have some doubts about if this approach is the right one, especially as the document would become very similar to RFC 5411.

So we would like to ask feedback from the group on the approach.

We are considering the following options:

(1) Maintain the same style as RFC5411, including SIP. This would mean copy & paste from RFC 5411, or even start with RFC 5411 and expand it. The draft would become RFC5411bis.

(2) Start completely from scratch, and use a different format from RFC 5411. The new guide could be "textbook style", giving a prosaic description of SDP, its different components and working areas, and in the process references to the related RFCs. Notice that this is distinctively different from RFC 5411, as the new document will not be a categorised list of SDP related RFCs with short descriptions.

(3) Reference RFC 5411, and include only new descriptions. This would keep the document concise, but the reader has to read both the new draft and RFC 5411 to get the complete picture. The advantage is, that we could focus on what was done after RFC 5411, giving an insight in the latest developments.
 
(4) Reconsider the scope of the document, i.e. inclusion of SIP or not.

What would be the groups preference?

Best regards,
Bert