OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

camp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [camp] Media type for CAMP SPF protocol


Robin,

Thanks for your prompt response on this matter.
The TC hasn't decided on whether to register a new media type yet.
If/when the TC decides, I'll let you know.
We would certainly appreciate your/OASIS staff's help in this matter if/when we decide to register a new media-type.

Thanks.

--Anish

On 6/16/16 10:50 AM, Robin Cover wrote:
Hello Anish and TC Members,

I noted the thread on new media/mime types (possibly) to be associated
with CAMP SPF protocol.

https://lists.oasis-open.org/archives/camp/201606/msg00011.html

Our coordination with IANA/ICANN (etc) on registration of new media
types (also: ports, headers, protocol names...) requires that OASIS
Staff help manage the correspondence and then file the registration
application.

So please let me know if you decide to proceed with a TC decision to
request new media/mime types.  I can open a TC Admin JIRA ticket for
tracking if and when that happens.

It will be OK for you all to send mail communications to the relevant
IETF list for preliminary discussion there. The registration application
itself needs to be made by OASIS Staff on behalf of OASIS as the owner,
maintainer, and change controller.

Thanks!

- Robin Cover




On Thu, Jun 16, 2016 at 12:09 PM, Anish Karmarkar
<anish.karmarkar@oracle.com <mailto:anish.karmarkar@oracle.com>> wrote:

    I had an AI to investigate whether CAMP's SPF protocol should use
    application/json media type or create a new one using the +json suffix.

    Since the SPF protocol will introduce new semantics to the returned
    JSON messages (as SCIM does) it makes sense to use
    application/camp+json (or similar) media type. These media types are
    required to conform to application/json media type and therefore can
    be displayed as such by tools like browsers. This is exactly the
    reason why SCIM uses it. Furthermore, JSON Patch that we already use
    in CAMP also uses application/jason-patch+json media type. This is
    similar to how the +xml structured media type is used.

    For more details see:
    1) IETF RFC 6838 Media Type Specifications and Registration
    Procedures https://tools.ietf.org/html/rfc6838
    2) IETF RFC 6839 Additional Media Type Structured Syntax Suffixes
    https://tools.ietf.org/html/rfc6839

    --Anish

    ---------------------------------------------------------------------
    To unsubscribe from this mail list, you must leave the OASIS TC that
    generates this mail.  Follow this link to all your TCs in OASIS at:
    https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php




--
Robin Cover
OASIS, Director of Information Services
Editor, Cover Pages and XML Daily Newslink
Email: robin@oasis-open.org <mailto:robin@oasis-open.org>
Staff bio: http://www.oasis-open.org/people/staff/robin-cover
Cover Pages: http://xml.coverpages.org/
Newsletter: http://xml.coverpages.org/newsletterArchive.html
Tel: +1 972-296-1783


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]