IETF Logo Mail Archive

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

Mark Baker <distobj@acm.org> Tue, 27 September 2016 15:35 UTC

Return-Path: <mark@coactus.com>
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 3A13512B243 for <media-types@ietfa.amsl.com>; Tue, 27 Sep 2016 08:35:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_HELO_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=coactus-com.20150623.gappssmtp.com
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 Tw1xkY9Mu1j0 for <media-types@ietfa.amsl.com>; Tue, 27 Sep 2016 08:35:37 -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 75C4312B228 for <media-types@ietf.org>; Tue, 27 Sep 2016 08:35:37 -0700 (PDT)
Received: from mail-ua0-x233.google.com (mail-ua0-x233.google.com [IPv6:2607:f8b0:400c:c08::233]) by pechora1.lax.icann.org (8.13.8/8.13.8) with ESMTP id u8RFZGKn019506 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <media-types@iana.org>; Tue, 27 Sep 2016 15:35:37 GMT
Received: by mail-ua0-x233.google.com with SMTP id i25so14131560uab.0 for <media-types@iana.org>; Tue, 27 Sep 2016 08:35:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=coactus-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=Z4qamTunJCTX+IHFiYaD1mLdm0IcrBNpWUC86IwGFjI=; b=KOctnWBNxUdIzJplS8B0iLKQ+pNhXIgqId2baHDwMNUBoK4pUGFjx3qBWkL9ozSqNr eei9W4ERtcA9GVvC0OSyUKVaCHTx+z9Fjlfp4uGCCDmK4I2jwqNeswPhF+Miwt4DASkK uRHnzIzZQvbQJ5qlqPMuvx4jX1T0ZxHpVsAdVWGHL4veM6YUkq2JmbEhQZCGf8ctekeG +vzpJyzW3ucoAD8RhY//JkXKkjkhMvzEX4LM/LeVS3nitmw8huB01idZmTNZS8FG1pUV 2+2S50W26JQJLwAw5lKCcAdGRgfF3zA5EaDMgqKDMtncCV2odM6TBF0eXRj3mm5kP828 VjEg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=Z4qamTunJCTX+IHFiYaD1mLdm0IcrBNpWUC86IwGFjI=; b=FA4/5Tvr7gWrnDQg61u0E9zO3+nSdbF7kJjS9WG+FxNEqs6ZdLPmTDD8kjLp1C5Jc2 WAwG11b1aihgZQrlDwcs7czqJ/o5PrDA8yn72tteoL+OPLBgJV2OjiPJ4ojUZAgP+hiE bvHg9MOimBpgZG72BkU1H5RQJ3dykZYYGkY9VTmD/KT09qUh1s2s3h4yD+7vS0XbyjjB h1PQH9tvjgvk2DuQrppS9VSIDjTiJoUsM1IQkxPLx0HJBnkKDSitYaKYHxf4JfZ7MeCj 854AHZx8BIsK0uA5TJnGrEAG2m2K/1t/7mCukwiq0NC/jpReoq9Q/KxFf9fP4/Wf3oCt EeyA==
X-Gm-Message-State: AA6/9RnaHjwZpDwG2F4GnG0sZM4L9Vj7927IqY3K+3D6mCkZ8XDAcnZzaeSbfLIKylGDoTNSJ8UjH6NGQTf1vA==
X-Received: by 10.159.33.198 with SMTP id 64mr1936280uac.79.1474990516204; Tue, 27 Sep 2016 08:35:16 -0700 (PDT)
MIME-Version: 1.0
Sender: mark@coactus.com
Received: by 10.103.111.193 with HTTP; Tue, 27 Sep 2016 08:35:15 -0700 (PDT)
X-Originating-IP: [142.162.2.229]
In-Reply-To: <p06240601d40f4d71cf0a@99.111.97.136>
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>
From: Mark Baker <distobj@acm.org>
Date: Tue, 27 Sep 2016 13:05:15 -0230
X-Google-Sender-Auth: QJmNrIFrUnVPp4PcZXqHF3aKqFg
Message-ID: <CALcoZioe5NW56ZRiZ+irc=E=X3BSrOxXq=0v_Q0Y1b+_ze0Znw@mail.gmail.com>
To: Randall Gellens <rg+ietf@randy.pensive.org>
Content-Type: text/plain; charset="UTF-8"
X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora1.lax.icann.org [IPv6:2620:0:2d0:201::1:71]); Tue, 27 Sep 2016 15:35:37 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/vxaLBoWEwl3Wa2em4xSrfghzU9c>
Cc: Brian Rosen <Brian.Rosen@neustar.biz>, Hannes Tschofenig <hannes.tschofenig@gmx.net>, Ned Freed <ned.freed@mrochek.com>, media-types@iana.org, ecrit-chairs@ietf.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: Tue, 27 Sep 2016 15:35:39 -0000

On Mon, Sep 26, 2016 at 8:14 PM, Randall Gellens
<rg+ietf@randy.pensive.org> wrote:
> At 10:11 AM -0700 9/22/16, Randall Gellens wrote:
>>  These have been registered by IANA (e.g.,
>> https://www.iana.org/assignments/media-types/application/EmergencyCallData.ProviderInfo+xml),
>> are referenced in several NENA documents, and I belive there are
>> implementations.
>>
>>  We want the three new subtypes to follow the same pattern, which is that
>> 'EmergencyCallData' is a parent and the various subtypes are children within
>> that.
>>
>>  So, given this, how do we proceed?
>
>
> I have a proposed solutions:
>
> We treat "EmergencyCallData" as a parallel to a facet, since it serves an
> analogous purpose: it establishes a naming subspace that has a particular
> meaning.

Yes, but it's meaning along an orthogonal axis.

It's surprising IANA would register those types without expert review.
I'll leave the larger process implications to somebody else to worry
about, but as a media type reviewer, I'm not too concerned as I've yet
to see a MIME/media-type library that consults or exposes the facet
(versus the suffix, which is commonly exposed).

But if these types are indeed in use in the wild, I would think we
have little option but to grandfather them in.

Mark.

v2.23.0 | Report a Bug | By Email