Re: [Slim] IETF last call for draft-ietf-slim-negotiating-human-language (Issue 8, section 6, IANA registrations)

Gunnar Hellström <gunnar.hellstrom@omnitor.se> Wed, 15 February 2017 12:33 UTC

Return-Path: <gunnar.hellstrom@omnitor.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DD2E1295C9 for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2017 04:33:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o86nGSetMCjR for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2017 04:33:03 -0800 (PST)
Received: from bin-vsp-out-03.atm.binero.net (bin-mail-out-05.binero.net [195.74.38.228]) (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 82191127735 for <ietf@ietf.org>; Wed, 15 Feb 2017 04:33:03 -0800 (PST)
X-Halon-ID: e2eb9301-f37a-11e6-9c99-0050569116f7
Authorized-sender: gunnar.hellstrom@omnitor.se
Received: from [192.168.2.136] (unknown [83.209.158.27]) by bin-vsp-out-03.atm.binero.net (Halon Mail Gateway) with ESMTPSA; Wed, 15 Feb 2017 13:32:57 +0100 (CET)
Subject: Re: [Slim] IETF last call for draft-ietf-slim-negotiating-human-language (Issue 8, section 6, IANA registrations)
To: ietf@ietf.org, "slim@ietf.org" <slim@ietf.org>
References: <20170213161000.665a7a7059d7ee80bb4d670165c8327d.917539e857.wbe@email0 3.godaddy.com> <ddc5af1d-f084-f57e-d6c9-5963e4fe98d3@omnitor.se> <4c4ef65a-a907-cf5e-4b2c-835fb55d0146@omnitor.se> <p06240603d4c8f105055e@[99.111.97.136]> <434a4f06-f034-46ca-9df7-f59059e67e41@alumni.stanford.edu> <843f0cc1-2686-162d-25dc-0075847579bc@omnitor.se> <p06240609d4c937dc9ff8@[99.111.97.136]> <84760193-19e6-1f53-43cc-32b0493a1844@alumni.stanford.edu> <p0624060dd4c9523fcf2a@[99.111.97.136]> <4f1f3a72-d8a9-4f41-4133-0e6d54aadec8@omnitor.se>
From: Gunnar Hellström <gunnar.hellstrom@omnitor.se>
Message-ID: <a5ce4d13-309c-0bef-4b23-b44bb7c07c1b@omnitor.se>
Date: Wed, 15 Feb 2017 13:32:56 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <4f1f3a72-d8a9-4f41-4133-0e6d54aadec8@omnitor.se>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Dv7vXr39boq0X2r3r1Icsqj5K-A>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 12:33:05 -0000

in issue 8, I propose:

(Look in the edited draft -06g that I attached some days ago for how the 
proposal appears in the text )


------------------------------------------------------------------------------------------------------------ 


8. Include more fields for attribute registration from 4566bis

Section 6 has the form for attribute registration by IANA. There are a 
couple of fields missing that will be important for use of the 
specification in the WebRTC environment.  Include these fields if that 
is allowable according to current IANA procedures and if that does not 
delay the publication of this draft. These fields are needed for use of 
text media in WebRTC.

Change:

In two locations from:
     "Usage Level:  media"

to:

     "Usage Level:  media, dcsa(subprotocol)"

Insert in two locations in the registration forms:
"Mux Category: NORMAL"
---------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------

I checked in current IANA registrations, and found that all SDP 
attribute registrations now include the "Mux Category".

So, I assume that we are obliged to do so also and hope that we can 
agree on that.
As far as I understand the logic, we should specify NORMAL.

I saw no trace yet of registrations of  "Usage Level: dcsa(subprotocol)"

I would like to get advice from someone with insight in the SDP 
attribute registration and the status of the dsca(subprotocol) value on 
how we should proceed in order to get the dsca(subprotocol)  included in 
a smooth way without causing exessive delay.


Regards
Gunnar