Re: [Ecrit] draft-ietf-ecrit-ecall-16.txt and draft-ietf-ecrit-car-crash-15.txt

Randall Gellens <rg+ietf@randy.pensive.org> Sun, 16 October 2016 16:21 UTC

Return-Path: <rg+ietf@randy.pensive.org>
X-Original-To: ecrit@ietfa.amsl.com
Delivered-To: ecrit@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BED2D129463 for <ecrit@ietfa.amsl.com>; Sun, 16 Oct 2016 09:21:10 -0700 (PDT)
X-Quarantine-ID: <g0w5Tt618ZBS>
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: -2.331
X-Spam-Level:
X-Spam-Status: No, score=-2.331 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.431] 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 g0w5Tt618ZBS for <ecrit@ietfa.amsl.com>; Sun, 16 Oct 2016 09:21:08 -0700 (PDT)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id 9DCF8129447 for <ecrit@ietf.org>; Sun, 16 Oct 2016 09:21:08 -0700 (PDT)
Received: from [99.111.97.136] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Sun, 16 Oct 2016 09:21:07 -0700
Mime-Version: 1.0
Message-Id: <p06240600d429550f0d72@[99.111.97.136]>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4BD8FC66@ESESSMB209.ericsson.se>
References: <147646451751.18604.4638966497289572815.idtracker@ietfa.amsl.com> <147646453871.18548.7812739569679702499.idtracker@ietfa.amsl.com> <p06240604d426c0923f32@99.111.97.136> <CAJD5LR32EJp9Li2oGOdWE6T5xpTo2Mvtv=8nBn6GSHEVzCtX4A@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B4BD8FC66@ESESSMB209.ericsson.se>
X-Mailer: Eudora for Mac OS X
Date: Sun, 16 Oct 2016 09:21:05 -0700
To: Christer Holmberg <christer.holmberg@ericsson.com>, Az Mankin <azmankin@gmail.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>
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
Archived-At: <https://mailarchive.ietf.org/arch/msg/ecrit/b-oi4i2OfWYcGPppl8IaaLrdzFs>
Cc: "ecrit@ietf.org" <ecrit@ietf.org>
Subject: Re: [Ecrit] draft-ietf-ecrit-ecall-16.txt and draft-ietf-ecrit-car-crash-15.txt
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ecrit/>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Oct 2016 16:21:11 -0000

Hi Christer,

In rereading RFC 6086 and RFC 5621, I don't see any clear statement 
that the Content-Disposition of a top-level multipart within an INFO 
request should be Info-Package.  RFC 6086 says Content-Disposition is 
optional at the top level of a SIP message, and the examples in RFC 
6086 sometimes show no Content-Disposition at the top level.  Upon 
careful rereading, my interpretation is that the innermost multipart 
that contains only body parts associated with the INFO package 
perhaps should have a Content-Disposition of Info-Package.  If there 
is only one multipart, then the innermost is also the top level.

Therefore, I propose to add the following text:

    The innermost multipart that contains only body parts associated with
    the INFO package SHOULD have a Content-Disposition value of Info-
    Package (if there is only one multipart, then the innermost is also
    the top level).

And add the C-D header to the examples.

--Randy

At 4:56 PM +0000 10/15/16, Christer Holmberg wrote:

>  Hi,
>
>  We need to solve the Content-Disposition issue first. If the issue 
> is unclear, perhaps it's not enough to cover it in the example - 
> perhaps we need some normative clarification text too.
>
>  Regards,
>
>  Christer
>
>  From: Ecrit [mailto:ecrit-bounces@ietf.org] On Behalf Of Az Mankin
>  Sent: 15 October 2016 18:24
>  To: Randy Gellens <rg+ietf@randy.pensive.org>
>  Cc: ecrit@ietf.org
>  Subject: Re: [Ecrit] draft-ietf-ecrit-ecall-16.txt and 
> draft-ietf-ecrit-car-crash-15.txt
>
>  I'll request IETF LC first thing on Tuesday. Working on the 
> write-up and will share it tonight.
>  Thank you, WG and Randy
>
>  On Oct 14, 2016 12:06, "Randall Gellens" 
> <<mailto:rg%2Bietf@randy.pensive.org>rg+ietf@randy.pensive.org> 
> wrote:
>
>  Hi everyone,
>
>  These versions address all comments received, with the exception of 
> the Content-Disposition issue Christer raised.
>
>  --Randall
>
>  At 10:01 AM -0700 10/14/16, <mailto:internet-drafts@ietf.org> 
> internet-drafts@ietf.org wrote:
>
>   A New Internet-Draft is available from the on-line Internet-Drafts 
> directories.
>   This draft is a work item of the Emergency Context Resolution with 
> Internet Technologies of the IETF.
>
>           Title           : Next-Generation Pan-European eCall
>           Authors         : Randall Gellens
>                             Hannes Tschofenig
>          Filename        : draft-ietf-ecrit-ecall-16.txt
>          Pages           : 44
>          Date            : 2016-10-14
>
>   Abstract:
>      This document describes how to use IP-based emergency services
>      mechanisms to support the next generation of the pan European in-
>      vehicle emergency call service defined under the eSafety initiative
>      of the European Commission (generally referred to as "eCall"). eCall
>      is a standardized and mandated system for a special form of emergency
>      calls placed by vehicles, providing real-time communications and an
>      integrated set of related data.
>
>      This document also registers MIME Content Types and an Emergency Call
>      Additional Data Block for the eCall vehicle data and metadata/control
>      data, and an INFO package to enable carrying this data in INFO
>      requests.
>
>
>   The IETF datatracker status page for this draft is:
> 
> <https://datatracker.ietf.org/doc/draft-ietf-ecrit-ecall/>https://datatracker.ietf.org/doc/draft-ietf-ecrit-ecall/
>
>   There's also a htmlized version available at:
> 
> <https://tools.ietf.org/html/draft-ietf-ecrit-ecall-16>https://tools.ietf.org/html/draft-ietf-ecrit-ecall-16
>
>   A diff from the previous version is available at:
> 
> <https://www.ietf.org/rfcdiff?url2=draft-ietf-ecrit-ecall-16>https://www.ietf.org/rfcdiff?url2=draft-ietf-ecrit-ecall-16
>
>
>   Please note that it may take a couple of minutes from the time of submission
>   until the htmlized version and diff are available at 
> <http://tools.ietf.org> tools.ietf.org.
>
>   Internet-Drafts are also available by anonymous FTP at:
>   <ftp://ftp.ietf.org/internet-drafts/>ftp://ftp.ietf.org/internet-drafts/
>
>   _______________________________________________
>   Ecrit mailing list
>   <mailto:Ecrit@ietf.org>Ecrit@ietf.org
> 
> <https://www.ietf.org/mailman/listinfo/ecrit>https://www.ietf.org/mailman/listinfo/ecrit
>
>
>  At 10:02 AM -0700 10/14/16, <mailto:internet-drafts@ietf.org> 
> internet-drafts@ietf.org wrote:
>
>   A New Internet-Draft is available from the on-line Internet-Drafts 
> directories.
>   This draft is a work item of the Emergency Context Resolution with 
> Internet Technologies of the IETF.
>
>           Title           : Next-Generation Vehicle-Initiated Emergency Calls
>           Authors         : Randall Gellens
>                             Brian Rosen
>                             Hannes Tschofenig
>          Filename        : draft-ietf-ecrit-car-crash-15.txt
>          Pages           : 43
>          Date            : 2016-10-14
>
>   Abstract:
>      This document describes how to use IP-based emergency services
>      mechanisms to support the next generation of emergency calls placed
>      by vehicles (automatically in the event of a crash or serious
>      incident, or manually invoked by a vehicle occupant) and conveying
>      vehicle, sensor, and location data related to the crash or incident.
>      Such calls are often referred to as "Automatic Crash Notification"
>      (ACN), or "Advanced Automatic Crash Notification" (AACN), even in the
>      case of manual trigger.  The "Advanced" qualifier refers to the
>      ability to carry a richer set of data.
>
>      This document also registers a MIME Content Type and Emergency Call
>      Additional Data Block for the vehicle, sensor, and location data
>      (often referred to as "crash data" even though there is not
>      necessarily a crash) and an INFO package to enable carrying this and
>      related data in INFO requests.  An external specification for the
>      data format, contents, and structure are referenced in this document.
>
>      This document reuses the technical aspects of next-generation pan-
>      European eCall (a mandated and standardized system for emergency
>      calls by in-vehicle systems within Europe and other regions).
>      However, this document specifies a different set of vehicle (crash)
>      data, specifically, the Vehicle Emergency Data Set (VEDS) rather than
>      the eCall Minimum Set of Data (MSD).  This document is an extension
>      of the eCall document, with the primary differences being that this
>      document makes the MSD data set optional and VEDS mandatory, and adds
>      attribute values to the metadata/control object to permit greater
>      functionality.  This document registers a new INFO package (identical
>      to that registered for eCall but with the addition of the VEDS MIME
>      type).  This document also describes legacy (circuit-switched) ACN
>      systems and their migration to next-generation emergency calling, to
>      provide background information and context.
>
>
>   The IETF datatracker status page for this draft is:
> 
> <https://datatracker.ietf.org/doc/draft-ietf-ecrit-car-crash/>https://datatracker.ietf.org/doc/draft-ietf-ecrit-car-crash/
>
>   There's also a htmlized version available at:
> 
> <https://tools.ietf.org/html/draft-ietf-ecrit-car-crash-15>https://tools.ietf.org/html/draft-ietf-ecrit-car-crash-15
>
>   A diff from the previous version is available at:
> 
> <https://www.ietf.org/rfcdiff?url2=draft-ietf-ecrit-car-crash-15>https://www.ietf.org/rfcdiff?url2=draft-ietf-ecrit-car-crash-15
>
>
>   Please note that it may take a couple of minutes from the time of submission
>   until the htmlized version and diff are available at 
> <http://tools.ietf.org> tools.ietf.org.
>
>   Internet-Drafts are also available by anonymous FTP at:
>   <ftp://ftp.ietf.org/internet-drafts/>ftp://ftp.ietf.org/internet-drafts/
>
>   _______________________________________________
>   Ecrit mailing list
>   <mailto:Ecrit@ietf.org>Ecrit@ietf.org
> 
> <https://www.ietf.org/mailman/listinfo/ecrit>https://www.ietf.org/mailman/listinfo/ecrit
>
>
>  _______________________________________________
>  Ecrit mailing list
>  <mailto:Ecrit@ietf.org>Ecrit@ietf.org
> 
> <https://www.ietf.org/mailman/listinfo/ecrit>https://www.ietf.org/mailman/listinfo/ecrit


-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
One of the greatest labor saving inventions of today is tomorrow.  -
                                               --Vincent T. Foss