[media-types] Vendor-Specific Media Type: PagerDuty

Ken Kwan <kkwan@pagerduty.com> Wed, 24 June 2015 19:42 UTC

MIME-Version: 1.0
From: Ken Kwan <kkwan@pagerduty.com>
Date: Wed, 24 Jun 2015 19:41:30 +0000
Message-ID: <CAG7QND_YLLDY5Y0oV=TU95bDoRCvxf6NMeSEuw-LMFB=6KLBBw@mail.gmail.com>
To: ietf-types@iana.org
Content-Type: multipart/alternative; boundary="001a11c2e33e1c9a98051948b206"
Archived-At: <http://mailarchive.ietf.org/arch/msg/media-types/In9CkAsoube0pwh4Ylm_8i2sQ2k>
Subject: [media-types] Vendor-Specific Media Type: PagerDuty
Precedence: list

Hello,

PagerDuty would like to register a vendor-specific media type. As per
https://tools.ietf.org/html/rfc4288#section-3.2:
*"While public exposure and review of media types to be registered in the
vendor tree is not required, using the ietf-types@iana.org
<ietf-types@iana.org> mailing list for review is strongly encouraged to
improve the quality of those specifications."*

Please let me know if there should be any modifications before directly
submitting to IANA.

Thanks,
Kenneth Kwan


Name: *Kenneth Kwan*
Email: *kkwan@pagerduty.com <kkwan@pagerduty.com>*

   1. Media Type Name: *application*
   2. Subtype name: Vendor Tree - *vnd.pagerduty+json*
   3. Required parameters: *None*
   4. Optional parameters: *version=[version string, e.g. “1.0”]*
   5. Encoding considerations: *7 bit text*
   6. Security considerations: *the security issues associated with this
   type have not been assessed*
   7. Interoperability considerations: *None*
   8. Published specification: *None*
   9. Applications which use this media type: *PagerDuty API
   (developer.pagerduty.com <http://developer.pagerduty.com>)*
   10. Fragment identifier considerations: *None*
   11. Restrictions on usage: *None*
   12. Provisional registration? (standards tree only): *N/A*
   13. Additional information: *N/A*
   1. Deprecated alias names for this type: *N/A*
      2. Magic number(s): *N/A*
      3. File extension(s): *N/A*
      4. Macintosh File Type Code(s): *N/A*
      5. Object Identifier(s) or OID(s): *N/A*
   14. Intended usage: *(Common) Used by clients to indicate that the
   request is in PagerDuty's API-specified format and is expecting a formatted
   response as per the API definition (as described at
   https://developer.pagerduty.com <https://developer.pagerduty.com/>).*
   15. Other Information/General Comment (optional): *N/A*
   16. Person to contact for further information
   1. Name: *Steve Rice*
      2. E-mail: *developers@pagerduty.com <developers@pagerduty.com>*
      3. Author/Change controller: *Steve Rice, developers@pagerduty.com
      <developers@pagerduty.com>*

[media-types] Vendor-Specific Media Type: PagerDu… Ken Kwan