Register Node specific MIME types

I would like to register a few new MIMEs under the Node Foundation's authority in the IANA Registry . This would allow some better interop and disambiguation with various APIs using MIME types or overlap with ESM and CJS module systems.

In particular I would like to register:

text/vnd.node.js
- Will request an exception be made as to match WHATWG Script MIME Default otherwise we can use application/.

Security Considerations: ... TODO ...
File Extensions: .js
Change Controller: Node Foundation

application/vnd.node.node

Security Considerations: Used as a container format to execute code directly on the host within the Node Process. All permissions of the host process will be granted to the code within the resource.
File Extensions: .node
Change Controller: Node Foundation

+1 on this.

What do you intend to put for the contact information for the registration? I would propose that the TSC, in general, be listed as the authority for the registrations.

I'm fine w/ whatever, "Node Foundation TSC"?

Works for me

…

On Thu, Sep 28, 2017 at 16:12 Bradley Meck ***@***.***> wrote: I'm fine w/ whatever, "Node Foundation TSC"? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#371 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAa2eRYdXQD3XK4Bv3NsHOufeqyhFx4Fks5snAusgaJpZM4PnY-_> .

Is it "Node Foundation" or "Node.js Foundation"?

Node.js Foundation

…

On Thu, Sep 28, 2017 at 16:29 Timothy Gu ***@***.***> wrote: Is it "Node Foundation" or "Node.js Foundation"? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#371 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAa2eWygz-aAXpsaUTVbL6gilJ0RO9fOks5snA-4gaJpZM4PnY-_> .

+1 from me

draft just needs contact name + email I think.

Type Name: text
Subtype Name: vnd.node.js
Require Parameters: none
Optional Parameters: none
Encoding Considerations: 8 bit text, utf8
Security Considerations:

  The resource is given access to all of Node.js's module system.
  This includes code execution, filesystem access, and network access.
  Ensuring security is left up to the host running the resource.

Interoperability Considerations:

  The registration occupies the same file extension as other media types.
  The media type of the file extension should be considered ambiguous if the intended execution environment is unknown.

Published Specification: https://nodejs.org/api/modules.html
Application Usage:

  Node.js CommonJS execution environments
  Node.js CommonJS package managers
  Node.js CommonJS module tools

Fragment Identifier Considerations: none
Restrictions on Usage: none
Provisional Registrations: none
Additional Information:

  Deprecated alias names for this type: none
  Magic number(s): none
  File extension(s): .js
  Macintosh File Type Code(s): TEXT
  Object Identifier(s) or OID(s): none

Intended Usage: Common
Other Information & Comments:

  See also text/javascript which also occupies the same file extension.
  See the CommonJS specification for Module which Node.js is a variant of.
  This usage of the .js file extension is extremely prolific on the public `npm` registry ( https://www.npmjs.com/ ) with millions of downloads of packages a day.
  If text type name is not appropriate, application works as well. text is slightly preferred since https://html.spec.whatwg.org/multipage/scripting.html#prepare-a-script used text/javascript instead of application/javascript.

Contact Person: Node.js Technical Steering Committee
Contact Email Address: tsc@iojs.org
Author/Change Controller: Node.js Technical Steering Committee

Type Name: application
Subtype Name: vnd.node.node
Require Parameters: none
Optional Parameters: none
Encoding Considerations: binary
Security Considerations:

  The resource is given access to arbitrary code execution on the host.
  Ensuring security is left up to the host running the resource.

Interoperability Considerations:

  This format is not safe to transfer between different architectures or operating environments.

Published Specification: https://nodejs.org/api/addons.html
Application Usage:

  Node.js execution environments
  Node.js package managers
  Node.js module tools

Fragment Identifier Considerations: none
Restrictions on Usage: none
Provisional Registrations: none
Additional Information:

  Deprecated alias names for this type: none
  Magic number(s): none
  File extension(s): .node
  Macintosh File Type Code(s): BINA
  Object Identifier(s) or OID(s): none

Intended Usage: Common
Other Information & Comments:

Contact Person: Node.js Technical Steering Committee
Contact Email Address: tsc@iojs.org
Author/Change Controller: Node.js Technical Steering Committee

For Contact Person, I would just say "Node.js Technical Steering Committee"
and tsc@iojs.org as the contact email.

@mhdawson

This usage of the .js file extension is extremely prolific on the public npm registry ( https://www.npmjs.com/ ) with millions of downloads of package a day.

packages

These look good to me otherwise. I'd say the contact email should be the tsc email, and if we cannot put the TSC as the "contact person" I suggest we put the chair, @mhdawson.

@mhdawson

Given that registrations are long lived and the chair can change year to year, it's not a great idea to list @mhdawson. The tsc email should be just fine

I am reading 6 +1s, at 11 I think we are ok to start submission it looks like (TSC currently has 21 members)? Or is there a simpler way to determine if it is something that is ok to start?

Generally we go for consensus seeking if there isn't an explicit vote called. So if there are no objections I think it is safe to move forward +1 from me We can also bring this up at next week's tsc meeting if you would prefer an explicit majority

…

On Oct 3, 2017 7:22 AM, "Bradley Meck" ***@***.***> wrote: I am reading 6 +1s, at 11 I think we are ok to start submission it looks like (TSC currently has 21 members)? Or is there a simpler way to determine if it is something that is ok to start? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#371 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAecV9T0IUv8DvS5VFmdgazBbGBqNZWoks5sokL5gaJpZM4PnY-_> .

SGTM

@MylesBorins

@MylesBorins I'm fine w/ consensus since it will still take a bit of time to land in IANA

Yes, with very few exceptions, we only vote when consensus-seeking fails. If this has been open for many days, has multiple approvals, and has no objections, then you can move forward with it.

@jasnell

@jasnell what do you think about doing the registration with tsc@nodejs.org which just points to tsc@iojs.org since that is the official domain of the project it will look a little more legit, IMHO.

The vnd.node.node request has been denied since it does not have a consistent content body type. It varies per platform with .so, .dll, and .dylib formats.

+1

@MylesBorins

@MylesBorins in the last TSC meeting we were not sure what the question was for the TSC. Can you add some context.

SGTM

This has been sent of w/ TSC as the organization per todays meeting.

Should we remove the tsc-agenda label at this time?

@Trott

@Trott yes

Done. https://www.iana.org/assignments/media-types/application/node

Navigation Menu

Repository navigation

Register Node specific MIME types #371

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Register Node specific MIME types #371

Description

Activity

jasnell commented on Sep 28, 2017

bmeck commented on Sep 28, 2017

jasnell commented on Sep 28, 2017

TimothyGu commented on Sep 28, 2017

jasnell commented on Sep 28, 2017

mhdawson commented on Sep 29, 2017

bmeck commented on Sep 29, 2017

jasnell commented on Sep 29, 2017

Fishrock123 commented on Oct 2, 2017

jasnell commented on Oct 2, 2017

bmeck commented on Oct 3, 2017

MylesBorins commented on Oct 3, 2017

mcollina commented on Oct 3, 2017

bmeck commented on Oct 3, 2017

Trott commented on Oct 4, 2017

mrhinkle commented on Nov 2, 2017

bmeck commented on Nov 6, 2017

fhinkel commented on Nov 15, 2017

mhdawson commented on Nov 22, 2017

joyeecheung commented on Nov 22, 2017

bmeck commented on Nov 29, 2017

Trott commented on Nov 30, 2017

bmeck commented on Nov 30, 2017

bmeck commented on Dec 12, 2017

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions