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

[Randall Gellens <[e-mail]>]

At 9:54 AM -0400 9/22/16, Mark Baker wrote:

>  Sec 4.2 of RFC 6838 describes the role of the period in subtypes;
>
>  "Characters before first dot always specify a facet name"
>
>   -- https://tools.ietf.org/html/rfc6838#section-4.2
>
>  If you want to register in the standards tree, you'll need to do
>  something like change the period to something else, e.g. hyphens.
>  Alternately, you could just slap "vnd." on the front.

Oops.  I should have known this, but didn't.  I'm sorry.  The problem 
in fixing this is that the current two drafts, which register the 
three new subtypes, are adding on to RFC 7852 
(https://tools.ietf.org/html/rfc7852), which registered the following 
MIME types:

	application/EmergencyCallData.ProviderInfo+xml
	application/EmergencyCallData.ServiceInfo+xml
	application/EmergencyCallData.DeviceInfo+xml
	application/EmergencyCallData.SubscriberInfo+xml
	application/EmergencyCallData.Comment+xml

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?

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
You can only protect your liberties in this world by protecting the
other man's freedom.  You can only be free if I am free.
    --Clarence Darrow