On May 28, 2011, at 3:16 AM, Bjoern Hoehrmann wrote: > * Cullen Jennings wrote: > > To: [email protected] > > > > Subject: Registration of media type application/p2p-overlay+xml > > There is no reason to include this part in the specification.
fixed - thanks > > > Type name: application > > > > Subtype name: p2p-overlay+xml > > > > Required parameters: none > > > > Optional parameters: none > > Why are you using the +xml convention but do not specify the type in a > manner consistent with application/xml? I may have missed what part of 3023 part we violate but I read it and could not see anything. Clearly the desire was to support UTF-8 which we do. > Without a very good reason I'd > think you should either add the "charset" parameter We are mandating UTF-8 as the charset which gives us the benefits would hope. We don't want to have multiple charsets supported as we have noted this reduces interoperability when some implementations don't bother to implement charsets other than UTF-8. It's arbitrary choice that increases what you need to implement and test, reduces interoperability, and provides not benefits to the end user beyond what they get with UTF-8. > or drop the "+xml". It is xml so it seems like it is useful to use the +xml convention so that systems that process that can use it. > > > Encoding considerations: Must be binary encoded. The contents MUST > > be valid XML compliant with the relax NG grammar specified in RFC- > > AAAA and use the UTF-8[RFC3629] character encoding. > > This should either just say "binary" or just reference RFC 3023 as RFC > 3023 suggests. Ok - removed this and moved it to additional info as it seems like useful information. > > > Interoperability considerations: Same as application/xml as defined > > in [RFC3023]. > > If there are no known interoperability issues beyond those of the type > application/xml, that is what you should say; the considerations here > are certainly not the same. > -- > Björn Höhrmann · mailto:[email protected] · http://bjoern.hoehrmann.de > Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de > 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ > _______________________________________________ P2PSIP mailing list [email protected] https://www.ietf.org/mailman/listinfo/p2psip
