[media-types] Re: [IANA #1448627] expert review for dr aft-pantos-content-steering-03 (vendor tree, conflict review )
"Murray S. Kucherawy" <[email protected]> Tue, 14 Apr 2026 09:41:38 -0700
| Newsgroups | gmane.ietf.types |
|---|---|
| Message-ID | <CAL0qLwYLK_Aq0e2XqO53J3j1RZJTXNXMQjiiK00x9UJnG6vt0w@mail.gmail.com> |
Some minor feedback, approved otherwise. -MSK On Thu, Apr 9, 2026 at 11:31 PM David Dong via RT < [email protected]> wrote: > Hi Murray, > > Following up on this vendor-tree conflict review request (#1 of 2). > > This is now on the 4/16 telechat. > > Thank you. > > Best regards, > > David Dong > IANA Services Sr. Specialist > > On Wed Apr 01 23:11:47 2026, amanda.baber wrote: > > Hi Murray, > > > > Sending a reminder for this vendor-tree conflict review request. #1 of 2. > > > > thanks, > > Amanda > > > > On Thu Mar 26 21:38:43 2026, amanda.baber wrote: > > > Hi Murray, > > > > > > I'm sending you a request to review a vendor-tree media type for a > > > conflict review listed as "for action" on next week's telechat. This > > > is the first of two conflict review requests. The other is modifying a > > > vendor-tree type registered by RFC 8216. > > > > > > I apologize for sending these so close to the telechat. I didn't check > > > these for actions when they came in last week. > > > > > > Should the change controller be Apple rather than an Apple employee? > > > > > > thanks, > > > Amanda > > > > > > ===== > > > > > > From https://datatracker.ietf.org/doc/html/draft-pantos-content- > > > steering-03: > > > > > > Type name: application > > > > > > Subtype name: vnd.apple.steering-list > > > > > > Required parameters: none > This should be "N/A"; see RFC 6868 Section 5.6. > > > Optional parameters: none > Same. > > > Encoding considerations: encoded as JSON (UTF-8), which is 8-bit > > > text. This media type may require encoding on transports not capable > > > of handling 8-bit text. See Section 4 for more information. > I think all you need here is "binary"; see RFC 6838 Section 4.8. > > > Security considerations: See Section 12. > > > > > > Compression: this media type does not employ compression. > This isn't part of the template. > > > Interoperability considerations: There are no byte-ordering issues > > > since files are 8-bit text. Applications could encounter > > > unrecognized keys, which SHOULD be ignored. > > > > > > Published specification: see Section 4. > > > > > > Applications that use this media type: streaming media content > > > delivery protocols such as HLS and DASH, including media servers and > > > media players. > > > > > > Fragment identifier considerations: no Fragment Identifiers are > > > defined for this media type. > > > > > > Query parameter considerations: this specification does not define > > > any query parameters, however any CDP using Content Steering may > > > define query parameters. (See Section 6.) > > > > > > Additional information: > > > > > > Deprecated alias names for this type: none > This should probably also be "N/A". > > > Magic number(s): none > > > File extension(s): .json (see Section 4) > > > Macintosh file type code(s): none > > > > > > Person & email address to contact for further information: Dimitri > > > Podborski, dpodborski AT apple.com. > > > > > > Intended usage: LIMITED USE > > > > > > Restrictions on usage: none > > > > > > Author: Roger Pantos > > > > > > Change Controller: Dimitri Podborski > _______________________________________________ media-types mailing list -- [email protected] To unsubscribe send an email to [email protected]