[Gen-art] Gen-ART LC review of draft-ietf-mmusic-sdp-mux-attributes-13

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Mon, 08 August 2016 16:01 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 31DF812D0AC for <gen-art@ietfa.amsl.com>; Mon, 8 Aug 2016 09:01:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.166
X-Spam-Status: No, score=-8.166 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.247] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id fMtPB9Ev0p96 for <gen-art@ietfa.amsl.com>; Mon, 8 Aug 2016 09:01:38 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A4AE12B01B for <gen-art@ietf.org>; Mon, 8 Aug 2016 09:01:38 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.28,490,1464667200"; d="scan'208,217";a="186993728"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([]) by co300216-co-outbound.net.avaya.com with ESMTP; 08 Aug 2016 12:01:35 -0400
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC02.global.avaya.com) ([]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/AES256-SHA; 08 Aug 2016 12:01:34 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC02.global.avaya.com ([]) with mapi id 14.03.0294.000; Mon, 8 Aug 2016 18:01:33 +0200
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: General Area Review Team <gen-art@ietf.org>
Thread-Topic: Gen-ART LC review of draft-ietf-mmusic-sdp-mux-attributes-13
Thread-Index: AdHxjh6Ih2VdKT4hSpGkdjOAj1xYSg==
Date: Mon, 08 Aug 2016 16:01:33 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA752668EC@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA752668ECAZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/VhLd1aw_ihcs7smzeoNa2N42LBc>
Cc: "draft-ietf-mmusic-sdp-mux-attributes.all@tools.ietf.org" <draft-ietf-mmusic-sdp-mux-attributes.all@tools.ietf.org>
Subject: [Gen-art] Gen-ART LC review of draft-ietf-mmusic-sdp-mux-attributes-13
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2016 16:01:40 -0000

I am the assigned Gen-ART reviewer for this draft. The General Area Review Team (Gen-ART) reviews all IETF documents being processed by the IESG for the IETF Chair.  Please treat these comments just like any other last call comments.

For more information, please see the FAQ at


Document: draft-ietf-mmusic-sdp-mux-attributes-13

Reviewer: Dan Romascanu

Review Date: 8/8/16

IETF LC End Date: 8/10/16

IESG Telechat date: not known


Ready with issues.

Major issues:

1.       My understanding is that this document undertakes the task of analyzing the multiplexing characteristics of the SDP attributes and classifying them based on this analysis. It also adds one new 'Multiplexing Category' registry, a 'Mux Category' column and new attributes to a number of SDP sub-registries. What is not clear to me is what is the process by which new attribute values are to be added. The sub-registries in 15.2.x - can new values be added? Or new  sub-registries created because of the need to support a new protocol that defined SDP attributes? What is the policy and the registration process? I hope that my question makes sense, in case it does not, please explain why.

Minor issues:

1.       The use of B - 'Both' terminology used to indicate that an attribute is specified S - Session Level and M - Medial Level (e.g. in Section 5) may be confusing, as there is a third possible level SR - Source Level. Actually S + M would probably be more clear.

2.       Section 5.54 includes a note referring to the TBD content. 'As per section 9.1 of [I-D.ietf-mmusic-sdp-bundle-negotiation],  there exists no publicly available specification that defines procedures for multiplexing/demultiplexing fax protocols flows over a single 5-tuple.  Once such a specification is available, the multiplexing category assignments for the attributes in this section could be revisited.' Assuming the missing specification will be publicly available sometime in the future - how will this information be added? Revise this RFC? The question applies to other TBD marked in the 'Mux Category' column of the tables in Section 5 (in 5.42, 5.44, ...)

Nits/editorial comments:

1.       In the table at 5.6 - repetition 'section Section'