Hi. FYI. Per Gavin’s shepherd feedback, submitted this request to media-ty...@ietf.org<mailto:media-ty...@ietf.org> for a review of the new geofeed media type.
Thanks, Jasdip From: Jasdip Singh <jasd...@arin.net> Date: Wednesday, October 23, 2024 at 10:27 AM To: media-ty...@ietf.org <media-ty...@ietf.org> Cc: Tom Harrison <t...@apnic.net>, Gavin Brown <gavin.br...@icann.org> Subject: [media-types] Geofeed media type Hi. This is a request for the review of a new media type “application/geofeed+csv” from the RDAP Geofeed draft [1]. 6.3. <https://www.ietf.org/archive/id/draft-ietf-regext-rdap-geofeed-08.html#section-6.3> Media Types Registry<https://www.ietf.org/archive/id/draft-ietf-regext-rdap-geofeed-08.html#name-media-types-registry> IANA is requested to register the following value in the Media Types Registry at [MEDIA-TYPES<https://www.ietf.org/archive/id/draft-ietf-regext-rdap-geofeed-08.html#MEDIA-TYPES>]: · Type name: application · Subtype name: geofeed+csv · Required parameters: N/A · Optional parameters: N/A · Encoding considerations: See Section 2<https://rfc-editor.org/rfc/rfc9632#section-2> of [RFC9632<https://www.ietf.org/archive/id/draft-ietf-regext-rdap-geofeed-08.html#RFC9632>]. · Security considerations: See Section 5<https://www.ietf.org/archive/id/draft-ietf-regext-rdap-geofeed-08.html#security_considerations> of this document [1]. · Interoperability considerations: There are no known interoperability problems regarding this media format. · Published specification: This document [1]. · Applications that use this media type: Implementations of the Registration Data Access Protocol (RDAP) Extension for Geofeed Data. Furthermore, any application that processes the CSV geofeed data. · Additional information: This media type is a product of the IETF REGEXT Working Group. The REGEXT charter, information on the REGEXT mailing list, and other documents produced by the REGEXT Working Group can be found at [REGEXT<https://www.ietf.org/archive/id/draft-ietf-regext-rdap-geofeed-08.html#REGEXT>]. · Person & email address to contact for further information: IETF, i...@ietf.org · Intended usage: COMMON · Restrictions on usage: None · Authors: Tom Harrison, Jasdip Singh · Change controller: IETF · Provisional Registration: No 6.4. <https://www.ietf.org/archive/id/draft-ietf-regext-rdap-geofeed-08.html#section-6.4> Structured Syntax Suffixes Registry<https://www.ietf.org/archive/id/draft-ietf-regext-rdap-geofeed-08.html#name-structured-syntax-suffixes-> IANA is requested to register the following value in the Structured Syntax Suffixes Registry at [STRUCTURED-SYNTAX-SUFFIXES<https://www.ietf.org/archive/id/draft-ietf-regext-rdap-geofeed-08.html#STRUCTURED-SYNTAX-SUFFIXES>]: · Name: Comma-Separated Values (CSV) · +suffix: +csv · References: [RFC4180<https://www.ietf.org/archive/id/draft-ietf-regext-rdap-geofeed-08.html#RFC4180>], [RFC7111<https://www.ietf.org/archive/id/draft-ietf-regext-rdap-geofeed-08.html#RFC7111>] · Encoding Considerations: Same as "text/csv". · Interoperability Considerations: Same as "text/csv". · Fragment Identifier Considerations: The syntax and semantics of fragment identifiers specified for +csv SHOULD be as specified for "text/csv". The syntax and semantics for fragment identifiers for a specific "xxx/yyy+csv" SHOULD be processed as follows: For cases defined in +csv, where the fragment identifier resolves per the +csv rules, then as specified in +csv. For cases defined in +csv, where the fragment identifier does not resolve per the +csv rules, then as specified in "xxx/yyy+csv". For cases not defined in +csv, then as specified in "xxx/yyy+csv". · Security Considerations: Same as "text/csv". · Contact: IETF, i...@ietf.org [1] https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-geofeed/ Thanks, Tom Harrison and Jasdip Singh
_______________________________________________ media-types mailing list -- media-ty...@ietf.org To unsubscribe send an email to media-types-le...@ietf.org
_______________________________________________ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
