-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add 15-nov-2017 minutes #420
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔥
meetings/2017-11-15.md
Outdated
|
||
Q: Can the Foundation be used as the contact? | ||
|
||
Jasnell: tl/dr; version: Mime types can be registered Standards track or Vendor track as described here: https://tools.ietf.org/html/rfc4288#section-3.1. Vendor track is for commercial products, Standards track is for stuff that is of “general”interest. The IESG/IETF may be viewing this in the latter case -- in general, they prefer things *not* to be vendor track as much as possible. The concern is that Standards track takes longer and requires an RFC to be published, which any one of us could write up. It doesn’t require Board action to push through, so we should get Bradley’s reasoning for why he’d like to see that. Also, fwiw, I’ve written many RFC’s to this point and I’m quite familiar with the process so can help push this forward. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing space between "general"
and interest
.
One lowercase vendor track
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
No description provided.