Re: [media-types] Review request for application/emergencyCallData.eCall.MSD+per

Randall Gellens <rg+ietf@randy.pensive.org> Wed, 28 September 2016 15:16 UTC

Return-Path: <rg+ietf@randy.pensive.org>
X-Original-To: media-types@ietfa.amsl.com
Delivered-To: media-types@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB32B12B04F for <media-types@ietfa.amsl.com>; Wed, 28 Sep 2016 08:16:17 -0700 (PDT)
X-Quarantine-ID: <ScPuQrXFmQMN>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001] autolearn=unavailable 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 ScPuQrXFmQMN for <media-types@ietfa.amsl.com>; Wed, 28 Sep 2016 08:16:16 -0700 (PDT)
Received: from pechora1.lax.icann.org (pechora1.icann.org [IPv6:2620:0:2d0:201::1:71]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C282812B18E for <media-types@ietf.org>; Wed, 28 Sep 2016 08:16:16 -0700 (PDT)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by pechora1.lax.icann.org (8.13.8/8.13.8) with ESMTP id u8SFFuV0017799 for <media-types@iana.org>; Wed, 28 Sep 2016 15:16:16 GMT
Received: from [192.168.1.2] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Wed, 28 Sep 2016 08:15:56 -0700
Mime-Version: 1.0
Message-Id: <p06240603d4118e1ada5a@[192.168.1.2]>
In-Reply-To: <01Q5H5GL1BUC00005M@mauve.mrochek.com>
References: <p06240604d408c444a602@99.111.97.136> <CALcoZiqzEVL=R_Yt_v=Yb5Jsq90UrYmZph-DdgUPg8V_tp+iLw@mail.gmail.com> <p0624060ad409bf5d8041@99.111.97.136> <p06240601d40f4d71cf0a@99.111.97.136> <CALcoZioe5NW56ZRiZ+irc=E=X3BSrOxXq=0v_Q0Y1b+_ze0Znw@mail.gmail.com> <01Q5FW9PDQ3W00005M@mauve.mrochek.com> <p06240605d410dbe81638@[99.111.97.136]> <01Q5GOYB35LG00005M@mauve.mrochek.com> <p06240601d41186590928@[192.168.1.2]> <01Q5H5GL1BUC00005M@mauve.mrochek.com>
X-Mailer: Eudora for Mac OS X
Date: Wed, 28 Sep 2016 08:15:52 -0700
To: Ned Freed <ned.freed@mrochek.com>, Randall Gellens <rg+ietf@randy.pensive.org>
From: Randall Gellens <rg+ietf@randy.pensive.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora1.lax.icann.org [192.0.33.71]); Wed, 28 Sep 2016 15:16:16 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/Qke8pO7LlY7vthTMcbOX4Dmf5Bg>
Cc: Mark Baker <distobj@acm.org>, Randall Gellens <rg+ietf@randy.pensive.org>, Ned Freed <ned.freed@mrochek.com>, ecrit-chairs@ietf.org, Brian Rosen <Brian.Rosen@neustar.biz>, Hannes Tschofenig <hannes.tschofenig@gmx.net>, media-types@iana.org
Subject: Re: [media-types] Review request for application/emergencyCallData.eCall.MSD+per
X-BeenThere: media-types@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." <media-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/media-types>, <mailto:media-types-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/media-types/>
List-Post: <mailto:media-types@ietf.org>
List-Help: <mailto:media-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/media-types>, <mailto:media-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Sep 2016 15:16:18 -0000

At 7:48 AM -0700 9/28/16, Ned Freed wrote:

>  What you need to do is specify essentially what
>  the tree is for, who gets to use it, and so on. The same way that RFC 6838
>  specifies what the trees it defines are for and who gets to use them.
>
>  I know very little about these types generally, but given the name
>  I'm guessing that the rules associated with personal tree would not
>  be appropriate... Some variation of the rules associated with the standards
>  (unfaceted) tree would seem to make sense, but as I note above, you
>  need to decide who gets to use the tree, and the rule for the existing
>  standards tree (standards organizations recognized as such by the IESG)
>  may or may not be what you want.

Thanks very much for the clarification.  Probably the rule for the 
existing standards tree would make sense, perhaps with the addition 
of the IETF and an additional restriction that the standards body 
must be doing emergency services work.

Could this be added to one of the two current drafts that seek to 
register new application/EmergencyCallData.* types or would this need 
to be a new standalone draft?  Would the draft need to update RFC 
6838?

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Miners Refuse to Work after Death
--Newspaper headline