Return-Path: X-Original-To: ietf-types@ietfa.amsl.com Delivered-To: ietf-types@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F308421F84EC for ; Sun, 22 Jan 2012 05:16:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.14 X-Spam-Level: X-Spam-Status: No, score=-1.14 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4yKlWq+dNvnQ for ; Sun, 22 Jan 2012 05:16:34 -0800 (PST) Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id D38B921F84D7 for ; Sun, 22 Jan 2012 05:16:33 -0800 (PST) Received: by werp11 with SMTP id p11so1830402wer.31 for ; Sun, 22 Jan 2012 05:16:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:to:subject:date:message-id:user-agent:mime-version :content-type; bh=pWoYrGY48+haFVm6XnZ398hsY6UUknXigZUGsdTdQLM=; b=SCACq3DgDUbVXJUrUOPJA+EXWsRupCXajnQ6ZgonTU0l/XmwQT/qtnmMvwlXwxi844 ozv99uw8QQVKW2ON/bihMGPmCuZJqw5iTwZN68e3nz91gUQRCOe9HAOFnDepMw4R/xss 3XvmIg/5JX+u1Io8lwioRItQ0Mq7z27U43B3o= Received: by 10.216.134.71 with SMTP id r49mr2055645wei.49.1327238193089; Sun, 22 Jan 2012 05:16:33 -0800 (PST) Received: from localhost (lie.newton.cam.ac.uk. [131.111.145.118]) by mx.google.com with ESMTPS id n5sm11232798wiw.7.2012.01.22.05.16.31 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 22 Jan 2012 05:16:32 -0800 (PST) From: Jesse Alama To: ietf-types@ietf.org Date: Sun, 22 Jan 2012 13:16:30 +0000 Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.92 (darwin) MIME-Version: 1.0 Content-Type: text/plain Subject: [ietf-types] request for review: text/mizar X-BeenThere: ietf-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Media \(MIME\) type review" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jan 2012 13:16:36 -0000 (Reposted to ietf-types@ietf.org rather than ietf-types@alvestrand.no, to which it was [wrongly] initially submitted, and thus my have hampered discussion about the proposed MIME type. What follows is the result of completing the form at http://www.iana.org/cgi-bin/mediatypes.pl .) ====================================================================== Name : Jesse Alama Email : j.alama at fct.unl.pt MIME media type name : text MIME subtype name : Standards Tree -mizar Required parameters : none Optional parameters : none Encoding considerations : 7bit Security considerations : none Interoperability considerations : Published specification : A. Grabowski, A. Kornilowicz, and A. Naumowicz, "Mizar in a Nutshell", Journal of Formalized Reasoning 3(2), 2010, pp. 153--245. Applications which use this media : The mizar suite of tools Additional information : 1. Magic number(s) : none 2. File extension(s) : .miz 3. Macintosh file type code : none 4. Object Identifiers: none Window clipboard flavor: "Mizar" Macintosh Uniform Type Identifier: "org.mizar" conforms to "public.text" The mizar language is a language for formalized mathematical documents. Authors use this language to express definitions of mathematical concepts, and express and proof formal mathematical statements. The language has been developed since the 1970s and today is used in teaching logic and mathematics in various high school and university settings. The library of mathematical knowledge formalized in the mizar language, the Mizar Mathematical Library, consists (at the time of application) of more than 1100 "articles" which, like an ordinary mathematical article in a journal, are coherent presentations and developments of mathematics. Person to contact for further information : 1. Name : Jesse Alama 2. Email : j.alama at fct.unl.pt Intended usage : Common This media type is intended to be used by text editors and affiliated programs that read text (e.g., web browsers). Author/Change controller : Adam Naumowicz Association of Mizar Users sum at mizar.uwb.edu.pl -- Jesse Alama http://centria.di.fct.unl.pt/~alama/ Return-Path: X-Original-To: ietf-types@ietfa.amsl.com Delivered-To: ietf-types@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6579521F84F7 for ; Fri, 20 Jan 2012 15:41:43 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.263 X-Spam-Level: X-Spam-Status: No, score=-3.263 tagged_above=-999 required=5 tests=[AWL=-0.664, BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WUfCqckdtlwx for ; Fri, 20 Jan 2012 15:41:41 -0800 (PST) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 2A55D21F84F1 for ; Fri, 20 Jan 2012 15:41:40 -0800 (PST) Received: (qmail invoked by alias); 20 Jan 2012 23:41:39 -0000 Received: from dslb-094-223-223-057.pools.arcor-ip.net (EHLO HIVE) [94.223.223.57] by mail.gmx.net (mp071) with SMTP; 21 Jan 2012 00:41:39 +0100 X-Authenticated: #723575 X-Provags-ID: V01U2FsdGVkX1+h0yADbpGhDx7hvLtJALORRI3+KD+Dbc3BK9RBzF AS5Q4Z65Ow8oTF From: Bjoern Hoehrmann To: "Worley, Dale R (Dale)" Date: Sat, 21 Jan 2012 00:41:52 +0100 Message-ID: References: , In-Reply-To: X-Mailer: Forte Agent 3.3/32.846 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Y-GMX-Trusted: 0 Cc: Lorenzo Miniero , Chris Boulton , Eric Burger , "ietf-types@ietf.org" Subject: Re: [ietf-types] Registration of application/mrb-publish+xml and application/mrb-consumer+xml X-BeenThere: ietf-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Media \(MIME\) type review" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jan 2012 23:41:43 -0000 * Worley, Dale R (Dale) wrote: >We will work on updating the I-D based on your comments. But there is >a difficulty with this item: "Media Resource Broker" is the term used >by the various vendors of MRB devices. And this I-D is one of a very >few IETF documents that describes MRB functionality. Unfortunately, >there is no larger, better-known class that contains MRB. > >Perhaps we could at least warn the reader that the RFC is the only >generic description of MRB: > > Applications which use this media type: This document type has been > used to support a Media Resource Broker (MRB) entity. MRB is > described in RFCXXXX. [[NOTE TO RFC-EDITOR/IANA: Please replace > XXXX with the RFC number of this specification.]] Regard the comment as an editorial nit that does not really have to be addressed. My problem is that I do not know "Media Resource Broker" in the way I know "video conferencing system", "photo editor", or "real- time chat application". Something about the problem it solves (random example, "Informs SIP applications of available communication options") or the enviroment it is used in (random example, "real-time telephony applications") would be nice, but if there is any trouble coming up with text for that, don't bother trying as far as I am concerned. -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · 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/ Return-Path: X-Original-To: ietf-types@ietfa.amsl.com Delivered-To: ietf-types@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2888421F86C4 for ; Fri, 20 Jan 2012 15:24:52 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.631 X-Spam-Level: X-Spam-Status: No, score=-102.631 tagged_above=-999 required=5 tests=[AWL=-0.032, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id je8nYa5GZXf0 for ; Fri, 20 Jan 2012 15:24:51 -0800 (PST) Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 964A221F86C2 for ; Fri, 20 Jan 2012 15:24:51 -0800 (PST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av8EAAn2GU/GmAcF/2dsb2JhbABDrgqBBYFyAQEBAQIBEig/BQsCAQgNAQchEDIlAQEEDgUIGodanR+bQItDYwSIPJJUjHI X-IronPort-AV: E=Sophos;i="4.71,545,1320642000"; d="scan'208";a="227850557" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 20 Jan 2012 18:24:50 -0500 Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by co300216-co-erhwest-out.avaya.com with ESMTP; 20 Jan 2012 18:19:56 -0500 Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.137]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Fri, 20 Jan 2012 18:24:49 -0500 From: "Worley, Dale R (Dale)" To: Bjoern Hoehrmann Date: Fri, 20 Jan 2012 18:24:48 -0500 Thread-Topic: [ietf-types] Registration of application/mrb-publish+xml and application/mrb-consumer+xml Thread-Index: AczXlkLVHPRtFsJRQhGBzHYKZF20WQAM292Q Message-ID: References: , In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: Lorenzo Miniero , Chris Boulton , Eric Burger , "ietf-types@ietf.org" Subject: Re: [ietf-types] Registration of application/mrb-publish+xml and application/mrb-consumer+xml X-BeenThere: ietf-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Media \(MIME\) type review" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jan 2012 23:24:52 -0000 > From: Bjoern Hoehrmann [derhoermi@gmx.net] >=20 > > Published specification: Section 10 of RFCXXXX [[NOTE TO RFC- > > EDITOR/IANA: Please replace XXXX with the RFC number of this > > specification.]]. > > > > Applications which use this media type: This document type has been > > used to support a Media Resource Broker (MRB) entity. >=20 > I suppose this might be okay in the context of the document, in general > it should give people like "oh, this is for document management" or "oh, > yet enother 3d modeling format". We will work on updating the I-D based on your comments. But there is a difficulty with this item: "Media Resource Broker" is the term used by the various vendors of MRB devices. And this I-D is one of a very few IETF documents that describes MRB functionality. Unfortunately, there is no larger, better-known class that contains MRB. Perhaps we could at least warn the reader that the RFC is the only generic description of MRB: Applications which use this media type: This document type has been used to support a Media Resource Broker (MRB) entity. MRB is described in RFCXXXX. [[NOTE TO RFC-EDITOR/IANA: Please replace XXXX with the RFC number of this specification.]] Dale Return-Path: X-Original-To: ietf-types@ietfa.amsl.com Delivered-To: ietf-types@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2030821F863C for ; Fri, 20 Jan 2012 09:09:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.293 X-Spam-Level: X-Spam-Status: No, score=-3.293 tagged_above=-999 required=5 tests=[AWL=-0.694, BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5cW72PFLIEwr for ; Fri, 20 Jan 2012 09:09:21 -0800 (PST) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id C7C9D21F85E5 for ; Fri, 20 Jan 2012 09:09:20 -0800 (PST) Received: (qmail invoked by alias); 20 Jan 2012 17:09:17 -0000 Received: from dslb-094-223-223-057.pools.arcor-ip.net (EHLO HIVE) [94.223.223.57] by mail.gmx.net (mp031) with SMTP; 20 Jan 2012 18:09:17 +0100 X-Authenticated: #723575 X-Provags-ID: V01U2FsdGVkX1+5QCxcgOS55BCiPME/DlQ9COdWqF12H+U8wbSrsF Rg2bQXPsrl96Dw From: Bjoern Hoehrmann To: "Worley, Dale R (Dale)" Date: Fri, 20 Jan 2012 18:09:29 +0100 Message-ID: References: In-Reply-To: X-Mailer: Forte Agent 3.3/32.846 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Y-GMX-Trusted: 0 Cc: Lorenzo Miniero , Chris Boulton , Eric Burger , "ietf-types@ietf.org" Subject: Re: [ietf-types] Registration of application/mrb-publish+xml and application/mrb-consumer+xml X-BeenThere: ietf-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Media \(MIME\) type review" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jan 2012 17:09:22 -0000 * Worley, Dale R (Dale) wrote: >13.2. application/mrb-publish+xml MIME Type > > MIME media type name: application > > MIME subtype name: mrb-publish+xml This is using an outdated template, the current one in RFC 4288 changes the names of some fields and organizes some other fields differently. > Mandatory parameters: none > > Optional parameters: Same as charset parameter of application/xml > as specified in RFC 3023 [RFC3023]. > > Encoding considerations: Same as encoding considerations of > application/xml as specified in RFC 3023 [RFC3023]. > > Security considerations: See Section 10 of RFC 3023 [RFC3023] and > Section 12 of RFCXXXX [[NOTE TO RFC-EDITOR/IANA: Please replace > XXXX with the RFC number of this specification.]]. > > Interoperability considerations: none. > > Published specification: Section 10 of RFCXXXX [[NOTE TO RFC- > EDITOR/IANA: Please replace XXXX with the RFC number of this > specification.]]. > > Applications which use this media type: This document type has been > used to support a Media Resource Broker (MRB) entity. I suppose this might be okay in the context of the document, in general it should give people like "oh, this is for document management" or "oh, yet enother 3d modeling format". > Additional Information: > > Magic Number: None > > File Extension: .xdf I note that you propose the same file name extension for both types. Do make sure that's not a copy and paste error. > Macintosh file type code: "TEXT" > > Personal and email address for further information: Chris Boulton, > chris@ns-technologies.com The typical rendering is `Chris Boulton `. >13.3. application/mrb-consumer+xml MIME Type (Same comments as above). -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · 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/ Return-Path: X-Original-To: ietf-types@ietfa.amsl.com Delivered-To: ietf-types@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AF9721F8603 for ; Thu, 19 Jan 2012 22:09:41 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.15 X-Spam-Level: X-Spam-Status: No, score=-5.15 tagged_above=-999 required=5 tests=[AWL=-4.000, BAYES_00=-2.599, MSGID_MULTIPLE_AT=1.449] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LQVVwgf+XUc6 for ; Thu, 19 Jan 2012 22:09:41 -0800 (PST) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id A327521F85FD for ; Thu, 19 Jan 2012 22:09:40 -0800 (PST) Received: (qmail invoked by alias); 20 Jan 2012 06:09:37 -0000 Received: from d175-38-188-181.per801.wa.optusnet.com.au (EHLO Vostro3500) [175.38.188.181] by mail.gmx.net (mp024) with SMTP; 20 Jan 2012 07:09:37 +0100 X-Authenticated: #419883 X-Provags-ID: V01U2FsdGVkX1+WXNxbNASW9GxRC054ICRI38qgZ89X42W44ACDAe 81rlJ6CaJe+87l From: "Markus Lanthaler" To: Date: Fri, 20 Jan 2012 14:09:32 +0800 Message-ID: <00c101ccd73a$16370000$42a50000$@lanthaler@gmx.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AczXOhNqpn6gONsnQ0q9tee1tGs6Nw== Content-Language: de X-Y-GMX-Trusted: 0 Subject: [ietf-types] Best practice for new MIME type: application/frame-ld+json X-BeenThere: ietf-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Media \(MIME\) type review" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jan 2012 06:15:07 -0000 Hello, We are currently working on an effort to standardize a way to describe linked data in JSON. Consequently we plan to register a media type application/ld+json (ld stands for linked data). We now came across the need for another media type to label framing documents, i.e., again a JSON document but with a completely different structure than a JSON-LD document. The media type we came up with so far was application/frame-ld+json but some people argued that we should follow this "+" pattern and call it application/frame+ld+json instead. >From talking with people from the HTTP WG this seems to be discouraged ([1], [2]). Bjoern Hoehrmann suggested to go with application/ld-frame+json as that "would be more in keeping with the terminology" and suggested to take the discussion over to this mailing list. I would love to hear you opinion on this. [1] http://lists.w3.org/Archives/Public/ietf-http-wg/2012JanMar/0088.html [2] http://lists.w3.org/Archives/Public/ietf-http-wg/2012JanMar/0089.html Thanks, Markus Return-Path: X-Original-To: ietf-types@ietfa.amsl.com Delivered-To: ietf-types@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC1A221F86B1 for ; Thu, 19 Jan 2012 13:33:21 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.638 X-Spam-Level: X-Spam-Status: No, score=-102.638 tagged_above=-999 required=5 tests=[AWL=-0.039, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id suM8js9c8Wnp for ; Thu, 19 Jan 2012 13:33:21 -0800 (PST) Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 507D621F8568 for ; Thu, 19 Jan 2012 13:33:21 -0800 (PST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av4EAOGLGE+HCzI1/2dsb2JhbABErHeBAIEFgXkSKD8SARUpQicEDgUIGodinUWbR4kKCAIDAQQPAgUFDAIJCQQBDgIBAUQKCRAGAQIBAQgBAQEBAoMFgzljBIg7klOMcQ X-IronPort-AV: E=Sophos;i="4.71,538,1320642000"; d="scan'208";a="227665660" Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 19 Jan 2012 16:33:17 -0500 Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 19 Jan 2012 16:19:48 -0500 Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.137]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Thu, 19 Jan 2012 16:33:16 -0500 From: "Worley, Dale R (Dale)" To: "ietf-types@ietf.org" Date: Thu, 19 Jan 2012 16:32:04 -0500 Thread-Topic: Registration of application/mrb-publish+xml and application/mrb-consumer+xml Thread-Index: AQHM1vH0llJHpD7qGEaR1vU2r3ZbGQ== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Mailman-Approved-At: Fri, 20 Jan 2012 08:35:55 -0800 Cc: Lorenzo Miniero , Chris Boulton , Eric Burger Subject: [ietf-types] Registration of application/mrb-publish+xml and application/mrb-consumer+xml X-BeenThere: ietf-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Media \(MIME\) type review" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Jan 2012 21:33:22 -0000 draft-ietf-mediactrl-mrb-12 will shortly be undergoing WGLC in the MEDIACTRL WG. In it, there are two new type registrations. The registrations are in sections 13.1 and 13.2 of http://tools.ietf.org/id/draft-ietf-mediactrl-mrb-12.txt, which are also copied below. Your comments are appreciated. Thanks, Dale Worley (MEDIACTRL WG co-chair) ---------------------------------------------------------------------- 13.2. application/mrb-publish+xml MIME Type MIME media type name: application MIME subtype name: mrb-publish+xml Mandatory parameters: none Optional parameters: Same as charset parameter of application/xml as specified in RFC 3023 [RFC3023]. Encoding considerations: Same as encoding considerations of application/xml as specified in RFC 3023 [RFC3023]. Security considerations: See Section 10 of RFC 3023 [RFC3023] and Section 12 of RFCXXXX [[NOTE TO RFC-EDITOR/IANA: Please replace XXXX with the RFC number of this specification.]]. Interoperability considerations: none. Published specification: Section 10 of RFCXXXX [[NOTE TO RFC- EDITOR/IANA: Please replace XXXX with the RFC number of this specification.]]. Applications which use this media type: This document type has been used to support a Media Resource Broker (MRB) entity. Additional Information: Magic Number: None File Extension: .xdf Macintosh file type code: "TEXT" Personal and email address for further information: Chris Boulton, chris@ns-technologies.com Intended usage: COMMON Author/Change controller: The IETF. 13.3. application/mrb-consumer+xml MIME Type MIME media type name: application MIME subtype name: mrb-consumer+xml Mandatory parameters: none Optional parameters: Same as charset parameter of application/xml as specified in RFC 3023 [RFC3023]. Encoding considerations: Same as encoding considerations of application/xml as specified in RFC 3023 [RFC3023]. Security considerations: See Section 10 of RFC 3023 [RFC3023] and Section 12 of RFCXXXX [[NOTE TO RFC-EDITOR/IANA: Please replace XXXX with the RFC number of this specification.]]. Interoperability considerations: none. Published specification: Section 11 of RFCXXXX [[NOTE TO RFC- EDITOR/IANA: Please replace XXXX with the RFC number of this specification.]]. Applications which use this media type: This document type has been used to support a Media Resource Broker (MRB) entity. Additional Information: Magic Number: None File Extension: .xdf Macintosh file type code: "TEXT" Personal and email address for further information: Chris Boulton, chris@ns-technologies.com Intended usage: COMMON Author/Change controller: The IETF. ---------------------------------------------------------------------- [END] Return-Path: X-Original-To: ietf-types@ietfa.amsl.com Delivered-To: ietf-types@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B663121F8699 for ; Tue, 17 Jan 2012 08:42:52 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m4MQfDxSEq+u for ; Tue, 17 Jan 2012 08:42:52 -0800 (PST) Received: from pechora6.dc.icann.org (unknown [IPv6:2620:0:2830:201::1:72]) by ietfa.amsl.com (Postfix) with ESMTP id 9D48521F85C6 for ; Tue, 17 Jan 2012 08:42:51 -0800 (PST) Received: from imail1.partech.com (imail1b.partech.com [192.133.62.25]) by pechora6.dc.icann.org (8.13.8/8.13.8) with ESMTP id q0HGgUnd014689 for ; Tue, 17 Jan 2012 11:42:51 -0500 Received: from eclipse.partech.com (eclipse.partech.com [172.16.8.4]) by imail1.partech.com (8.13.1/8.12.11) with ESMTP id q0HGJiq6003301; Tue, 17 Jan 2012 11:19:44 -0500 Received: from beasley.parcorp.local (beasley.partech.com [172.16.16.70]) by eclipse.partech.com (8.12.9/8.12.9) with ESMTP id q0HGJebM008503; Tue, 17 Jan 2012 11:19:41 -0500 (EST) Received: from [192.168.248.11] ([192.168.248.11]) by beasley.parcorp.local with Microsoft SMTPSVC(6.0.3790.4675); Tue, 17 Jan 2012 11:19:41 -0500 Message-ID: <4F159F7F.5000706@partech.com> Date: Tue, 17 Jan 2012 11:19:11 -0500 From: Jeff Downs User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: derhoermi@gmx.net References: In-Reply-To: X-Forwarded-Message-Id: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-OriginalArrivalTime: 17 Jan 2012 16:19:41.0504 (UTC) FILETIME=[D1193400:01CCD533] X-Greylist: Delayed for 00:22:40 by milter-greylist-4.2.3 (pechora6.dc.icann.org [192.0.46.72]); Tue, 17 Jan 2012 11:42:51 -0500 (EST) X-Mailman-Approved-At: Wed, 18 Jan 2012 06:30:17 -0800 Cc: ietf-types@iana.org, abegen@cisco.com, payload@ietf.org Subject: Re: [ietf-types] Registration of application/smpte336m X-BeenThere: ietf-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Media \(MIME\) type review" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jan 2012 16:42:52 -0000 The encoding considerations text of "binary and framed" in the proposed registration of application/smpte336m (as part of draft-ietf-payload-rtp-klv-02) comes literally out of the template in draft-ietf-payload-rtp-howto-01. The format is, indeed, binary (not textual). I reviewed RFC 3555 and the usage of "binary" vs. "framed" isn't very clear to me, but as I read it the difference is whether or not the payload data can exist "standalone" without the frame headers/transport data. SMPTE 336M data can indeed exist outside such framing and be reasonably interpreted (without the notion of data timing), though this certainly does not fall within the scope of the I-D submitted by myself (rather it is the core of the SMPTE 336M specification itself). I am more than happy to defer to the expertise of others; if dropping binary is the right thing to do here I am completely ok with that change. Please include me directly on any follow-ups. Jeff Downs PAR Government Systems -----Original Message----- From: Bjoern Hoehrmann [mailto:derhoermi@gmx.net] Sent: Friday, January 13, 2012 10:46 AM To: Ali C. Begen (abegen) Cc: ietf-types@iana.org; payload@ietf.org Subject: Re: [ietf-types] Registration of application/smpte336m * Ali C. Begen (abegen) wrote: >6.1. Media Type Definition > > Type name: application > > Subtype name: smpte336m > > Required parameters: > > rate: RTP timestamp clock rate. Typically chosen based on > sampling rate of metadata being transmitted, but other rates > can be specified. > > Optional parameters: None > > Encoding considerations: This media type is framed and binary; see > Section 4.8 of [RFC4288]. Why does this include "binary"? -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · 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/ Return-Path: X-Original-To: ietf-types@ietfa.amsl.com Delivered-To: ietf-types@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AF8521F858D for ; Fri, 13 Jan 2012 07:46:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.305 X-Spam-Level: X-Spam-Status: No, score=-2.305 tagged_above=-999 required=5 tests=[AWL=0.294, BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nt+g4avAJOTB for ; Fri, 13 Jan 2012 07:46:20 -0800 (PST) Received: from pechora1.lax.icann.org (unknown [IPv6:2620:0:2d0:201::1:71]) by ietfa.amsl.com (Postfix) with ESMTP id 6191321F8581 for ; Fri, 13 Jan 2012 07:46:20 -0800 (PST) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by pechora1.lax.icann.org (8.13.8/8.13.8) with SMTP id q0DFjxag015560 for ; Fri, 13 Jan 2012 07:46:19 -0800 Received: (qmail invoked by alias); 13 Jan 2012 15:45:57 -0000 Received: from dslb-094-223-152-203.pools.arcor-ip.net (EHLO HIVE) [94.223.152.203] by mail.gmx.net (mp070) with SMTP; 13 Jan 2012 16:45:57 +0100 X-Authenticated: #723575 X-Provags-ID: V01U2FsdGVkX1/v+mQd2Njv7uQlYaE18nLcza3J5EdW23yd4uwRdj S+1+D/REz3H02G From: Bjoern Hoehrmann To: "Ali C. Begen (abegen)" Date: Fri, 13 Jan 2012 16:46:02 +0100 Message-ID: References: <04CAD96D4C5A3D48B1919248A8FE0D5410B0A017@xmb-sjc-215.amer.cisco.com> In-Reply-To: <04CAD96D4C5A3D48B1919248A8FE0D5410B0A017@xmb-sjc-215.amer.cisco.com> X-Mailer: Forte Agent 3.3/32.846 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Y-GMX-Trusted: 0 X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora1.lax.icann.org [192.0.33.71]); Fri, 13 Jan 2012 15:46:20 +0000 (UTC) Cc: ietf-types@iana.org, payload@ietf.org Subject: Re: [ietf-types] Registration of application/smpte336m X-BeenThere: ietf-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Media \(MIME\) type review" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2012 15:46:20 -0000 * Ali C. Begen (abegen) wrote: >6.1. Media Type Definition > > Type name: application > > Subtype name: smpte336m > > Required parameters: > > rate: RTP timestamp clock rate. Typically chosen based on > sampling rate of metadata being transmitted, but other rates > can be specified. > > Optional parameters: None > > Encoding considerations: This media type is framed and binary; see > Section 4.8 of [RFC4288]. Why does this include "binary"? -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · 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/ Return-Path: X-Original-To: ietf-types@ietfa.amsl.com Delivered-To: ietf-types@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD65221F874A for ; Wed, 11 Jan 2012 11:22:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.274 X-Spam-Level: X-Spam-Status: No, score=-7.274 tagged_above=-999 required=5 tests=[AWL=-0.675, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LHL3jecYRtc9 for ; Wed, 11 Jan 2012 11:22:39 -0800 (PST) Received: from pechora3.lax.icann.org (unknown [IPv6:2620:0:2d0:201::1:73]) by ietfa.amsl.com (Postfix) with ESMTP id 4C3B311E8094 for ; Wed, 11 Jan 2012 11:22:35 -0800 (PST) Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by pechora3.lax.icann.org (8.13.8/8.13.8) with ESMTP id q0BJME1c004260 for ; Wed, 11 Jan 2012 19:22:35 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=abegen@cisco.com; l=2153; q=dns/txt; s=iport; t=1326309755; x=1327519355; h=mime-version:content-transfer-encoding:subject:date: message-id:from:to:cc; bh=rTlqZIZbUHPTWO5xDrh6McBgHhQMteuHkFCQ4Z8jn8I=; b=mJNmIZBFblV4Cxodj+fNOblUHB0PVAKvgwEL/Wqu7KYGlwPg1OeWzBXJ kVMH9NnlpL8tUFwmfDciK910eO9Rmn+yGFrp0rXvlxqke07sntzIMih0c BH8XeyvnyOmInyZZBYmzdZ33NDZDywL3hKhxrfuVHtsjOKyfDzmEjw5yI 4=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av0EAA3hDU+rRDoI/2dsb2JhbABDrQaBBYF0AQQSAR1JEgEqBhgHIDcBBAoJCBqHYJkFAZ5NiQGCOWMEiAczl0iHZw X-IronPort-AV: E=Sophos;i="4.71,494,1320624000"; d="scan'208";a="24913694" Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-3.cisco.com with ESMTP; 11 Jan 2012 19:21:57 +0000 Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q0BJLvEv017689; Wed, 11 Jan 2012 19:21:57 GMT Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 11 Jan 2012 11:21:56 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Wed, 11 Jan 2012 11:21:50 -0800 Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D5410B0A017@xmb-sjc-215.amer.cisco.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Registration of application/smpte336m Thread-Index: AczQlkSJJSeJKPUKTyiakz3lL6NNNg== From: "Ali C. Begen (abegen)" To: X-OriginalArrivalTime: 11 Jan 2012 19:21:56.0923 (UTC) FILETIME=[48A338B0:01CCD096] X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora3.lax.icann.org [192.0.33.73]); Wed, 11 Jan 2012 19:22:35 +0000 (UTC) X-Mailman-Approved-At: Fri, 13 Jan 2012 07:29:28 -0800 Cc: payload@ietf.org Subject: [ietf-types] Registration of application/smpte336m X-BeenThere: ietf-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Media \(MIME\) type review" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2012 19:22:42 -0000 Hello, draft-ietf-payload-rtp-klv-02 has finished WGLC in the PAYLOAD WG. There = is one new registration in Section 6.1 of = http://datatracker.ietf.org/doc/draft-ietf-payload-rtp-klv/?include_text=3D= 1=20 The relevant text is copied below as well. Your comments are appreciated. Thanks.=20 -acbegen (PAYLOAD WG Co-chair) 6.1. Media Type Definition Type name: application Subtype name: smpte336m Required parameters: rate: RTP timestamp clock rate. Typically chosen based on sampling rate of metadata being transmitted, but other rates can be specified. Optional parameters: None Encoding considerations: This media type is framed and binary; see Section 4.8 of [RFC4288]. Security considerations: See Section 8 of RFCXXXX (note to RFC editor: please replace XXXX with the number assigned to this RFC). Interoperability considerations: Data items in smpte336m can be very diverse. Receivers might only be capable of interpreting a subset of the possible data items; unrecognized items are skipped. Agreement on data items to be used out of band, via application profile or similar, is typical. Published specification: RFCXXXX Applications that use this media type: Streaming of metadata associated with simultaneously streamed video and transmission of [SMPTE336M] based media formats (e.g. MXF [SMPTE377M]). Additional Information: none Person & email address to contact for further information: J. Downs ; IETF Payload Working Group Intended usage: COMMON Restrictions on usage: This media type depends on RTP framing, and hence is only defined for transfer via RTP ([RFC3550]). Transport within other framing protocols is not defined at this time. Author: J. Downs J. Arbeiter Change controller: IETF Payload working group delegated from the IESG. Return-Path: X-Original-To: ietf-types@ietfa.amsl.com Delivered-To: ietf-types@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6EF221F886F for ; Wed, 11 Jan 2012 09:02:07 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.679 X-Spam-Level: X-Spam-Status: No, score=-103.679 tagged_above=-999 required=5 tests=[AWL=-1.080, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DlyAV4EM0K2E for ; Wed, 11 Jan 2012 09:02:07 -0800 (PST) Received: from pechora6.dc.icann.org (unknown [IPv6:2620:0:2830:201::1:72]) by ietfa.amsl.com (Postfix) with ESMTP id 2563421F8873 for ; Wed, 11 Jan 2012 09:02:06 -0800 (PST) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by pechora6.dc.icann.org (8.13.8/8.13.8) with SMTP id q0BH1h5B004985 for ; Wed, 11 Jan 2012 12:02:04 -0500 Received: (qmail invoked by alias); 11 Jan 2012 17:01:41 -0000 Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp026) with SMTP; 11 Jan 2012 18:01:41 +0100 X-Authenticated: #1915285 X-Provags-ID: V01U2FsdGVkX180QskPmCY0HgYoGqhh59bRpuGK0JxynhNKc0/BDf Xgi2Q5TsVAFzNX Message-ID: <4F0DC06F.4040302@gmx.de> Date: Wed, 11 Jan 2012 18:01:35 +0100 From: Julian Reschke User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: Jan Algermissen References: <61DA936B-79AE-480E-B77A-2415DC18DB08@nordsc.com> <4F0D4A94.407@gmx.de> <4F0D5A60.10806@gmx.de> <859C71A7-C655-4612-A004-E4BC10546BC9@nordsc.com> In-Reply-To: <859C71A7-C655-4612-A004-E4BC10546BC9@nordsc.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.2.3 (pechora6.dc.icann.org [192.0.46.72]); Wed, 11 Jan 2012 12:02:04 -0500 (EST) Cc: ietf-types@iana.org, Carl Reed Subject: Re: [ietf-types] Request for review application/gml+xml X-BeenThere: ietf-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Media \(MIME\) type review" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2012 17:02:07 -0000 On 2012-01-11 17:50, Jan Algermissen wrote: > > On Jan 11, 2012, at 10:46 AM, Julian Reschke wrote: > >> On 2012-01-11 10:22, Jan Algermissen wrote: >>> >>> On Jan 11, 2012, at 9:38 AM, Julian Reschke wrote: >>> >>>> On 2012-01-11 08:05, Jan Algermissen wrote: >>>>> Carl, >>>>> >>>>> On Jan 11, 2012, at 2:54 AM, Carl Reed wrote: >>>>> >>>>>> "version": If provided, this parameter indicates the GML version >>>>>> used in the GML document. Only the major and the first minor >>>>>> version number are provided, e.g. "3.2". >>>>>> >>>>>> The value may be provided with or without quotes. i.e., >>>>>> application/gml+xml; version=3.1 shall be treated as identical to >>>>>> application/gml+xml; version="3.1". >>>>>> >>>>>> In cases where elements from multiple GML versions are used, >>>>>> the parameter shall indicate the highest GML version used in the >>>>>> document. >>>>>> >>>>>> The parameter can be used to provide protocol-specific operations, >>>>>> such as version-based content negotiation in HTTP >>>>> >>>>> I cannot find the reference just now, but if I am not seriously wrong, media type parameters are not taken into account by HTTP conneg. (How could they, given that their meaning is defined by the media type itself except for q and charset et al. >>>>> ... >>>> >>>> Why would that be a problem? >>> >>> I think that the correct way of implementing conneg is to strip all media type specific parameters before matching (otherwise the code would need to be aware of the media type specific parameters). >> >> But that's not what is specified in HTTP. > > Can you point me to that part of the spec? I saw the 'format' example in your reference to media type ranges, but I cannot (personally) read that the way you seem to do. > >> >>> The proposed text above suggests that the version parameter would be recognized by such implementations - which it would not. I.e. >>> >>> Accept: application/gml+xml; version=3.1 >>> >>> would maybe yield >>> >>> Content-Type: application/gml+xml; version=1.2 >> >> I think that would be a bug according to the HTTP spec. > > Doh, I am shocked - if you are right then I have lived with a very clouded spot of HTTP in my brain for years. > > So you are saying, if there are parameters (besides q) that do not *exactly* match conneg should say 'Not Acceptable'? Well, it's all advisory; so there is wiggle room. > IOW, this would also not be correct: > > Accept: application/gml+xml; version=3.1 > > Content-Type: application/gml+xml; version=3.5 > > And also this would be incorrect: > > Accept: application/atom+xml;type=entry > > Content-Type: application/atom+xml > > Or am I misunderstanding you? No, that's my understanding. But of course I may be wrong; I assume this is a feature that hasn't been used a lot yet. Best regards, Julian Return-Path: X-Original-To: ietf-types@ietfa.amsl.com Delivered-To: ietf-types@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D95A821F8613 for ; Wed, 11 Jan 2012 08:51:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.733 X-Spam-Level: X-Spam-Status: No, score=-0.733 tagged_above=-999 required=5 tests=[AWL=-1.517, BAYES_40=-0.185, HELO_EQ_DE=0.35, RCVD_IN_SORBS_WEB=0.619] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RXofjcEAY477 for ; Wed, 11 Jan 2012 08:51:20 -0800 (PST) Received: from pechora6.dc.icann.org (unknown [IPv6:2620:0:2830:201::1:72]) by ietfa.amsl.com (Postfix) with ESMTP id 742A721F860D for ; Wed, 11 Jan 2012 08:51:19 -0800 (PST) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by pechora6.dc.icann.org (8.13.8/8.13.8) with ESMTP id q0BGowKI004350 for ; Wed, 11 Jan 2012 11:51:18 -0500 Received: from [10.34.240.205] (tmo-111-77.customers.d1-online.com [80.187.111.77]) by mrelayeu.kundenserver.de (node=mreu2) with ESMTP (Nemesis) id 0MYrDT-1SG71V34d9-00VXzk; Wed, 11 Jan 2012 17:50:55 +0100 Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Jan Algermissen In-Reply-To: <4F0D5A60.10806@gmx.de> Date: Wed, 11 Jan 2012 17:50:48 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <859C71A7-C655-4612-A004-E4BC10546BC9@nordsc.com> References: <61DA936B-79AE-480E-B77A-2415DC18DB08@nordsc.com> <4F0D4A94.407@gmx.de> <4F0D5A60.10806@gmx.de> To: Julian Reschke X-Mailer: Apple Mail (2.1084) X-Provags-ID: V02:K0:kwad+9Zrk2bO3BmilPXkZx/cL+B28PEPbh1OMIKMk2z PIi4LdfPWHklVsML+0m1iYeVY1vq8qasuWy5mbOOtGxxiDvblk vuHW93zoUsmcWAg2hsTRrXhUFc6pX3rJEoLm36h44LHjdI/iYj VbcN1itwOsHBthSLLYuLbISyuA0NMkEy7PZ0zthY1hPBPXOvaL Qi7/936FC0qW//jyX2hIOMyi0nb4+9mvlKkx6IU1cYNdRlb6Ms 9FaIK2LMJDpeYImTdb27NiAZ/uTNwjEkYtWMaReHDuh+LeYJdP tKMxozTTQ2N5jkhVWhv/li5Q9aYw5ttDrzyyo/abDo+t9pL2SJ 5+xOX/xls/V97W6FTEcjWyLcd1/wFXRNxrWj+RQdVXZfD1vDhI 6dFCj46fCXy0w== X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.2.3 (pechora6.dc.icann.org [192.0.46.72]); Wed, 11 Jan 2012 11:51:18 -0500 (EST) Cc: ietf-types@iana.org, Carl Reed Subject: Re: [ietf-types] Request for review application/gml+xml X-BeenThere: ietf-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Media \(MIME\) type review" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2012 16:51:25 -0000 On Jan 11, 2012, at 10:46 AM, Julian Reschke wrote: > On 2012-01-11 10:22, Jan Algermissen wrote: >>=20 >> On Jan 11, 2012, at 9:38 AM, Julian Reschke wrote: >>=20 >>> On 2012-01-11 08:05, Jan Algermissen wrote: >>>> Carl, >>>>=20 >>>> On Jan 11, 2012, at 2:54 AM, Carl Reed wrote: >>>>=20 >>>>> "version": If provided, this parameter indicates the GML version >>>>> used in the GML document. Only the major and the first minor >>>>> version number are provided, e.g. "3.2". >>>>>=20 >>>>> The value may be provided with or without quotes. i.e., >>>>> application/gml+xml; version=3D3.1 shall be treated as = identical to >>>>> application/gml+xml; version=3D"3.1". >>>>>=20 >>>>> In cases where elements from multiple GML versions are used, >>>>> the parameter shall indicate the highest GML version used in = the >>>>> document. >>>>>=20 >>>>> The parameter can be used to provide protocol-specific = operations, >>>>> such as version-based content negotiation in HTTP >>>>=20 >>>> I cannot find the reference just now, but if I am not seriously = wrong, media type parameters are not taken into account by HTTP conneg. = (How could they, given that their meaning is defined by the media type = itself except for q and charset et al. >>>> ... >>>=20 >>> Why would that be a problem? >>=20 >> I think that the correct way of implementing conneg is to strip all = media type specific parameters before matching (otherwise the code would = need to be aware of the media type specific parameters). >=20 > But that's not what is specified in HTTP. Can you point me to that part of the spec? I saw the 'format' example in = your reference to media type ranges, but I cannot (personally) read that = the way you seem to do. >=20 >> The proposed text above suggests that the version parameter would be = recognized by such implementations - which it would not. I.e. >>=20 >> Accept: application/gml+xml; version=3D3.1 >>=20 >> would maybe yield >>=20 >> Content-Type: application/gml+xml; version=3D1.2 >=20 > I think that would be a bug according to the HTTP spec. Doh, I am shocked - if you are right then I have lived with a very = clouded spot of HTTP in my brain for years. So you are saying, if there are parameters (besides q) that do not = *exactly* match conneg should say 'Not Acceptable'? IOW, this would also not be correct: Accept: application/gml+xml; version=3D3.1 Content-Type: application/gml+xml; version=3D3.5 And also this would be incorrect: Accept: application/atom+xml;type=3Dentry Content-Type: application/atom+xml Or am I misunderstanding you? Jan >=20 >> ... >=20 > Best regards, Julian Return-Path: X-Original-To: ietf-types@ietfa.amsl.com Delivered-To: ietf-types@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8708F21F8675 for ; Wed, 11 Jan 2012 04:35:33 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.278 X-Spam-Level: X-Spam-Status: No, score=-2.278 tagged_above=-999 required=5 tests=[AWL=0.321, BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sz-GGLPQVqAK for ; Wed, 11 Jan 2012 04:35:33 -0800 (PST) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 742DE21F8671 for ; Wed, 11 Jan 2012 04:35:32 -0800 (PST) Received: (qmail invoked by alias); 11 Jan 2012 12:35:28 -0000 Received: from dslb-094-223-194-051.pools.arcor-ip.net (EHLO HIVE) [94.223.194.51] by mail.gmx.net (mp014) with SMTP; 11 Jan 2012 13:35:28 +0100 X-Authenticated: #723575 X-Provags-ID: V01U2FsdGVkX1/kEBtsL93k+C0bq6leLn6SQbG5ZNr/CQ+7GodBJN tLESYs0oN2w0ov From: Bjoern Hoehrmann To: Hannes Tschofenig Date: Wed, 11 Jan 2012 13:35:28 +0100 Message-ID: References: <831E75A2-96FD-44AF-84F2-206D7D0040A5@gmx.net> In-Reply-To: <831E75A2-96FD-44AF-84F2-206D7D0040A5@gmx.net> X-Mailer: Forte Agent 3.3/32.846 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Y-GMX-Trusted: 0 Cc: ECRIT Org , ietf-types@ietf.org Subject: Re: [ietf-types] Request for review of Media Type 'application/lostsync+xml' X-BeenThere: ietf-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Media \(MIME\) type review" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2012 12:35:33 -0000 * Hannes Tschofenig wrote: >thank you for your review. I have updated the draft based on your comments. >Here is the new draft: http://www.ietf.org/id/draft-ietf-ecrit-lost-sync-14.txt RFC 3023 section 7.1 starts out: Registrations for new XML-based media types under top-level types other than "text" SHOULD, in specifying the charset parameter and encoding considerations, define them as: "Same as [charset parameter / encoding considerations] of application/xml as specified in RFC 3023." So, instead of "Indicates the character encoding of enclosed XML." you should have "Same as the charset parameter of application/xml as ..."; same for the encoding considerations. -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · 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/ Return-Path: X-Original-To: ietf-types@ietfa.amsl.com Delivered-To: ietf-types@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE1E721F879B for ; Wed, 11 Jan 2012 02:13:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.383 X-Spam-Level: X-Spam-Status: No, score=-103.383 tagged_above=-999 required=5 tests=[AWL=-0.784, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yObF0G64kcuS for ; Wed, 11 Jan 2012 02:13:14 -0800 (PST) Received: from pechora5.dc.icann.org (pechora5.icann.org [IPv6:2620:0:2830:201::1:71]) by ietfa.amsl.com (Postfix) with ESMTP id EF12821F879A for ; Wed, 11 Jan 2012 02:13:13 -0800 (PST) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by pechora5.dc.icann.org (8.13.8/8.13.8) with SMTP id q0BACq8I007103 for ; Wed, 11 Jan 2012 02:13:13 -0800 Received: (qmail invoked by alias); 11 Jan 2012 09:46:10 -0000 Received: from p3EE27860.dip.t-dialin.net (EHLO [192.168.178.36]) [62.226.120.96] by mail.gmx.net (mp007) with SMTP; 11 Jan 2012 10:46:10 +0100 X-Authenticated: #1915285 X-Provags-ID: V01U2FsdGVkX1+v51pAKQeve3/zGSmJDWlIfEwcXxFob1zpGeSG18 UbkwohHLvod1LI Message-ID: <4F0D5A60.10806@gmx.de> Date: Wed, 11 Jan 2012 10:46:08 +0100 From: Julian Reschke User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: Jan Algermissen References: <61DA936B-79AE-480E-B77A-2415DC18DB08@nordsc.com> <4F0D4A94.407@gmx.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-Greylist: Delayed for 00:26:39 by milter-greylist-4.0 (pechora5.dc.icann.org [192.0.46.71]); Wed, 11 Jan 2012 02:13:13 -0800 (PST) Cc: ietf-types@iana.org, Carl Reed Subject: Re: [ietf-types] Request for review application/gml+xml X-BeenThere: ietf-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Media \(MIME\) type review" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2012 10:13:14 -0000 On 2012-01-11 10:22, Jan Algermissen wrote: > > On Jan 11, 2012, at 9:38 AM, Julian Reschke wrote: > >> On 2012-01-11 08:05, Jan Algermissen wrote: >>> Carl, >>> >>> On Jan 11, 2012, at 2:54 AM, Carl Reed wrote: >>> >>>> "version": If provided, this parameter indicates the GML version >>>> used in the GML document. Only the major and the first minor >>>> version number are provided, e.g. "3.2". >>>> >>>> The value may be provided with or without quotes. i.e., >>>> application/gml+xml; version=3.1 shall be treated as identical to >>>> application/gml+xml; version="3.1". >>>> >>>> In cases where elements from multiple GML versions are used, >>>> the parameter shall indicate the highest GML version used in the >>>> document. >>>> >>>> The parameter can be used to provide protocol-specific operations, >>>> such as version-based content negotiation in HTTP >>> >>> I cannot find the reference just now, but if I am not seriously wrong, media type parameters are not taken into account by HTTP conneg. (How could they, given that their meaning is defined by the media type itself except for q and charset et al. >>> ... >> >> Why would that be a problem? > > I think that the correct way of implementing conneg is to strip all media type specific parameters before matching (otherwise the code would need to be aware of the media type specific parameters). But that's not what is specified in HTTP. > The proposed text above suggests that the version parameter would be recognized by such implementations - which it would not. I.e. > > Accept: application/gml+xml; version=3.1 > > would maybe yield > > Content-Type: application/gml+xml; version=1.2 I think that would be a bug according to the HTTP spec. > ... Best regards, Julian Return-Path: X-Original-To: ietf-types@ietfa.amsl.com Delivered-To: ietf-types@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47CE021F8799 for ; Wed, 11 Jan 2012 01:30:10 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.228 X-Spam-Level: X-Spam-Status: No, score=-102.228 tagged_above=-999 required=5 tests=[AWL=-0.229, BAYES_00=-2.599, J_CHICKENPOX_83=0.6, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m3YkAA6J8OJ2 for ; Wed, 11 Jan 2012 01:30:09 -0800 (PST) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id A8DDD21F8795 for ; Wed, 11 Jan 2012 01:30:08 -0800 (PST) Received: (qmail invoked by alias); 11 Jan 2012 09:30:06 -0000 Received: from a88-115-216-191.elisa-laajakaista.fi (EHLO [192.168.100.109]) [88.115.216.191] by mail.gmx.net (mp013) with SMTP; 11 Jan 2012 10:30:06 +0100 X-Authenticated: #29516787 X-Provags-ID: V01U2FsdGVkX180rmlUlW00omKbRon9DqzorC5H4IvWFLVm8QTCIR dCdg2C/mOhtSKk Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=iso-8859-1 From: Hannes Tschofenig In-Reply-To: Date: Wed, 11 Jan 2012 11:30:04 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <831E75A2-96FD-44AF-84F2-206D7D0040A5@gmx.net> References: To: Bjoern Hoehrmann X-Mailer: Apple Mail (2.1084) X-Y-GMX-Trusted: 0 X-Mailman-Approved-At: Fri, 13 Jan 2012 07:29:28 -0800 Cc: Hannes Tschofenig , ECRIT Org , ietf-types@ietf.org Subject: Re: [ietf-types] Request for review of Media Type 'application/lostsync+xml' X-BeenThere: ietf-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Media \(MIME\) type review" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2012 09:30:10 -0000 Hi Bjoern,=20 thank you for your review. I have updated the draft based on your = comments.=20 Here is the new draft: = http://www.ietf.org/id/draft-ietf-ecrit-lost-sync-14.txt Ciao Hannes On Sep 18, 2011, at 10:29 PM, Bjoern Hoehrmann wrote: > * Hannes Tschofenig wrote: >> MIME media type name: application >>=20 >>=20 >> MIME subtype name: lostsync+xml >=20 > This is based on an outdated version of the template, the current one = is > in RFC 4288; some of the fields are named and organized differently. >=20 >> Optional parameters: charset >>=20 >> Indicates the character encoding of enclosed XML. >>=20 >>=20 >> Encoding considerations: Uses XML, which can employ 8-bit >> characters, depending on the character encoding used. See RFC >> 3023 [RFC3023], Section 3.2. >=20 > RFC 3023 should be referenced as specified in RFC 3023 section 7.1. >=20 >> Additional information: >>=20 >> Magic Number: None >>=20 >>=20 >> File Extension: .lostsyncxml >>=20 >>=20 >> Macintosh file type code: 'TEXT' >>=20 >>=20 >> Personal and email address for further information: Hannes >> Tschofenig, Hannes.Tschofenig@nsn.com >=20 > (The rendering "Name " is more often used for this.) > --=20 > Bj=F6rn H=F6hrmann =B7 mailto:bjoern@hoehrmann.de =B7 = http://bjoern.hoehrmann.de > Am Badedeich 7 =B7 Telefon: +49(0)160/4415681 =B7 = http://www.bjoernsworld.de > 25899 Dageb=FCll =B7 PGP Pub. KeyID: 0xA4357E78 =B7 = http://www.websitedev.de/=20 Return-Path: X-Original-To: ietf-types@ietfa.amsl.com Delivered-To: ietf-types@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0785A21F8605 for ; Wed, 11 Jan 2012 01:23:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.249 X-Spam-Level: X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IafQgdi5KziW for ; Wed, 11 Jan 2012 01:23:16 -0800 (PST) Received: from pechora4.lax.icann.org (pechora4.icann.org [IPv6:2620:0:2d0:201::1:74]) by ietfa.amsl.com (Postfix) with ESMTP id 5D38421F85F2 for ; Wed, 11 Jan 2012 01:23:16 -0800 (PST) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.10]) by pechora4.lax.icann.org (8.13.8/8.13.8) with ESMTP id q0B9MtYh023775 for ; Wed, 11 Jan 2012 09:23:15 GMT Received: from [10.163.29.200] (tmo-110-8.customers.d1-online.com [80.187.110.8]) by mrelayeu.kundenserver.de (node=mreu1) with ESMTP (Nemesis) id 0MAASz-1RrHEo2mpV-00Bsda; Wed, 11 Jan 2012 10:22:52 +0100 Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Jan Algermissen In-Reply-To: <4F0D4A94.407@gmx.de> Date: Wed, 11 Jan 2012 10:22:48 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <61DA936B-79AE-480E-B77A-2415DC18DB08@nordsc.com> <4F0D4A94.407@gmx.de> To: Julian Reschke X-Mailer: Apple Mail (2.1084) X-Provags-ID: V02:K0:pjb/JqEb17SAPfaigCD0OKfoql3vHXRx43uUUFHgPGQ v46ynK3AA2YURXcLL2zutbnQ8L9GZSAjxr8DB/Tr9u6+u+RVm+ NjHlLNsn6rOmhrmkDOLemvbo/l1AqVJ1NL1SOOWoU1ho19dknC YRYTyPY+tqdiXIuEKSJURN7VDm98ZKmVXj38U9zyCVDdkbJCRl 7S8XLV3E+DykVv+vl9iEc+GGq/dKJXZ0FKosiFw47AOLq5Lds3 2AaHa3USIOj1PBUp6uGzTtckpIg3Q/sCUo+li8jnuAfmlYpOrF uz3dmTrW7SRfhht1M3sEQLiIjqKrXoXJxdnaIDtSoIsKAloc0F r9dfTmsh0sASDfXzshaMdOjM4t2my4Uwkx3BWwvrJy4HEQYIqr dRu+jn7gC+vYw== X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora4.lax.icann.org [192.0.33.74]); Wed, 11 Jan 2012 09:23:15 +0000 (UTC) Cc: ietf-types@iana.org, Carl Reed Subject: Re: [ietf-types] Request for review application/gml+xml X-BeenThere: ietf-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Media \(MIME\) type review" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2012 09:23:17 -0000 On Jan 11, 2012, at 9:38 AM, Julian Reschke wrote: > On 2012-01-11 08:05, Jan Algermissen wrote: >> Carl, >>=20 >> On Jan 11, 2012, at 2:54 AM, Carl Reed wrote: >>=20 >>> "version": If provided, this parameter indicates the GML version >>> used in the GML document. Only the major and the first minor >>> version number are provided, e.g. "3.2". >>>=20 >>> The value may be provided with or without quotes. i.e., >>> application/gml+xml; version=3D3.1 shall be treated as identical = to >>> application/gml+xml; version=3D"3.1". >>>=20 >>> In cases where elements from multiple GML versions are used, >>> the parameter shall indicate the highest GML version used in the >>> document. >>>=20 >>> The parameter can be used to provide protocol-specific = operations, >>> such as version-based content negotiation in HTTP >>=20 >> I cannot find the reference just now, but if I am not seriously = wrong, media type parameters are not taken into account by HTTP conneg. = (How could they, given that their meaning is defined by the media type = itself except for q and charset et al. >> ... >=20 > Why would that be a problem? I think that the correct way of implementing conneg is to strip all = media type specific parameters before matching (otherwise the code would = need to be aware of the media type specific parameters). The proposed text above suggests that the version parameter would be = recognized by such implementations - which it would not. I.e.=20 Accept: application/gml+xml; version=3D3.1 would maybe yield Content-Type: application/gml+xml; version=3D1.2 Or is the intention, that after 'initial standard HTTP conneg' there = would be a check for the version parameter in the resource = implementation to 'tune' the response entity accordingly? Sorry if I am confusing this somehow. Jan >=20 > See >=20 > = >=20 > Best regards, Julian > _______________________________________________ > ietf-types mailing list > ietf-types@ietf.org > https://www.ietf.org/mailman/listinfo/ietf-types Return-Path: X-Original-To: ietf-types@ietfa.amsl.com Delivered-To: ietf-types@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38ADC21F8852 for ; Wed, 11 Jan 2012 01:05:50 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.412 X-Spam-Level: X-Spam-Status: No, score=-103.412 tagged_above=-999 required=5 tests=[AWL=-0.813, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SplSwBGHvJLZ for ; Wed, 11 Jan 2012 01:05:49 -0800 (PST) Received: from pechora6.dc.icann.org (unknown [IPv6:2620:0:2830:201::1:72]) by ietfa.amsl.com (Postfix) with ESMTP id 40B0121F8543 for ; Wed, 11 Jan 2012 01:05:48 -0800 (PST) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by pechora6.dc.icann.org (8.13.8/8.13.8) with SMTP id q0B95RDG010864 for ; Wed, 11 Jan 2012 04:05:48 -0500 Received: (qmail invoked by alias); 11 Jan 2012 08:38:46 -0000 Received: from p3EE27860.dip.t-dialin.net (EHLO [192.168.178.36]) [62.226.120.96] by mail.gmx.net (mp068) with SMTP; 11 Jan 2012 09:38:46 +0100 X-Authenticated: #1915285 X-Provags-ID: V01U2FsdGVkX19uZWg27QtuuQO836Lrk9DBbRrTxbyxKYgUyrT2hK pfxeMm0ZMhvFL8 Message-ID: <4F0D4A94.407@gmx.de> Date: Wed, 11 Jan 2012 09:38:44 +0100 From: Julian Reschke User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: Jan Algermissen References: <61DA936B-79AE-480E-B77A-2415DC18DB08@nordsc.com> In-Reply-To: <61DA936B-79AE-480E-B77A-2415DC18DB08@nordsc.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-Greylist: Delayed for 00:26:39 by milter-greylist-4.2.3 (pechora6.dc.icann.org [192.0.46.72]); Wed, 11 Jan 2012 04:05:48 -0500 (EST) Cc: ietf-types@iana.org, Carl Reed Subject: Re: [ietf-types] Request for review application/gml+xml X-BeenThere: ietf-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Media \(MIME\) type review" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2012 09:05:50 -0000 On 2012-01-11 08:05, Jan Algermissen wrote: > Carl, > > On Jan 11, 2012, at 2:54 AM, Carl Reed wrote: > >> "version": If provided, this parameter indicates the GML version >> used in the GML document. Only the major and the first minor >> version number are provided, e.g. "3.2". >> >> The value may be provided with or without quotes. i.e., >> application/gml+xml; version=3.1 shall be treated as identical to >> application/gml+xml; version="3.1". >> >> In cases where elements from multiple GML versions are used, >> the parameter shall indicate the highest GML version used in the >> document. >> >> The parameter can be used to provide protocol-specific operations, >> such as version-based content negotiation in HTTP > > I cannot find the reference just now, but if I am not seriously wrong, media type parameters are not taken into account by HTTP conneg. (How could they, given that their meaning is defined by the media type itself except for q and charset et al. > ... Why would that be a problem? See Best regards, Julian Return-Path: X-Original-To: ietf-types@ietfa.amsl.com Delivered-To: ietf-types@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC09221F8846 for ; Tue, 10 Jan 2012 23:37:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.351 X-Spam-Level: X-Spam-Status: No, score=0.351 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_DE=0.35] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rZbHokcdIE-0 for ; Tue, 10 Jan 2012 23:37:56 -0800 (PST) Received: from pechora1.lax.icann.org (unknown [IPv6:2620:0:2d0:201::1:71]) by ietfa.amsl.com (Postfix) with ESMTP id 8BE4321F8843 for ; Tue, 10 Jan 2012 23:37:52 -0800 (PST) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by pechora1.lax.icann.org (8.13.8/8.13.8) with ESMTP id q0B7bVq0011662 for ; Tue, 10 Jan 2012 23:37:51 -0800 Received: from [192.168.2.107] (p548F9FA8.dip.t-dialin.net [84.143.159.168]) by mrelayeu.kundenserver.de (node=mreu3) with ESMTP (Nemesis) id 0MNAPk-1Rn3XF47o0-006ckw; Wed, 11 Jan 2012 08:37:30 +0100 Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Jan Algermissen X-Priority: 3 In-Reply-To: Date: Wed, 11 Jan 2012 08:05:28 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <61DA936B-79AE-480E-B77A-2415DC18DB08@nordsc.com> References: To: "Carl Reed" X-Mailer: Apple Mail (2.1084) X-Provags-ID: V02:K0:5yDO/Fdc6KTiyvvYptkihsbvKsSEIu2zrO1oWRXgb9L o3I2mD+wF7AWLWYAF0tVeI/Z9HTDPdrKoQ3Im4pr7l5VjeQFGZ HSK69c1H+5sbMwTZ2a+Gga/l9EcKyvmeJlKjS6JYjODJR45BAH 41XIq9vc3XVEjVuPuUNZ/JWwT91I+NctT1VOPZcpl4RMeCjhwr AvpovvAZcWDKB4aMsB9tYWIga3VuyZCkzwCcuYK/Fv11B7WPR6 17/lUMAejxyCidZsYXDRDwKySLOGeMsJ4FdrnD5z/RY/AJfhaX gEcM/rEAtBQ/nfUEJR7E6LcbLDK+puJGOM6jXwn+usz5yfp/qt 9HEpEmKIZbqTUk2bVk6SghggHXeeUurseFhr0z7lmrxLRyM0j4 Nct0//Mwfc9lw== X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora1.lax.icann.org [192.0.33.71]); Wed, 11 Jan 2012 07:37:52 +0000 (UTC) Cc: ietf-types@iana.org Subject: Re: [ietf-types] Request for review application/gml+xml X-BeenThere: ietf-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Media \(MIME\) type review" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2012 07:37:56 -0000 Carl, On Jan 11, 2012, at 2:54 AM, Carl Reed wrote: > "version": If provided, this parameter indicates the GML version > used in the GML document. Only the major and the first minor > version number are provided, e.g. "3.2". > =20 > The value may be provided with or without quotes. i.e., > application/gml+xml; version=3D3.1 shall be treated as identical to > application/gml+xml; version=3D"3.1". > =20 > In cases where elements from multiple GML versions are used, > the parameter shall indicate the highest GML version used in the > document. > =20 > The parameter can be used to provide protocol-specific operations, > such as version-based content negotiation in HTTP I cannot find the reference just now, but if I am not seriously wrong, = media type parameters are not taken into account by HTTP conneg. (How = could they, given that their meaning is defined by the media type itself = except for q and charset et al. Jan > or in the OGC > Web Feature Service. Return-Path: X-Original-To: ietf-types@ietfa.amsl.com Delivered-To: ietf-types@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88B1E21F8493 for ; Tue, 10 Jan 2012 18:26:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.668 X-Spam-Level: X-Spam-Status: No, score=0.668 tagged_above=-999 required=5 tests=[AWL=-0.856, BAYES_50=0.001, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z8NQE7v5RDbA for ; Tue, 10 Jan 2012 18:26:02 -0800 (PST) Received: from pechora2.lax.icann.org (pechora2.icann.org [IPv6:2620:0:2d0:201::1:72]) by ietfa.amsl.com (Postfix) with ESMTP id 81FD421F8492 for ; Tue, 10 Jan 2012 18:26:02 -0800 (PST) Received: from mail.opengeospatial.org (scale.ogcinc.net [66.244.86.102]) by pechora2.lax.icann.org (8.13.8/8.13.8) with ESMTP id q0B2PfT4030247 for ; Wed, 11 Jan 2012 02:26:01 GMT Received: from localhost (localhost [127.0.0.1]) by mail.opengeospatial.org (Postfix) with ESMTP id DC3BC5A2E3 for ; Tue, 10 Jan 2012 21:07:59 -0500 (EST) X-Virus-Scanned: Debian amavisd-new at mail.ogcinc.net Received: from mail.opengeospatial.org ([127.0.0.1]) by localhost (mail.opengeospatial.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jeOsXcwi0NWL for ; Tue, 10 Jan 2012 21:07:59 -0500 (EST) Received: from OfficeHP (c-98-245-174-99.hsd1.co.comcast.net [98.245.174.99]) by mail.opengeospatial.org (Postfix) with ESMTPSA id 049EB5A2DF for ; Tue, 10 Jan 2012 21:07:58 -0500 (EST) Message-ID: From: "Carl Reed" To: Date: Tue, 10 Jan 2012 18:54:09 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0312_01CCCFC9.3C9F49F0" X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 15.4.3538.513 X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3538.513 X-Greylist: Delayed for 00:17:40 by milter-greylist-4.0 (pechora2.lax.icann.org [192.0.33.72]); Wed, 11 Jan 2012 02:26:02 +0000 (UTC) Subject: [ietf-types] Request for review application/gml+xml X-BeenThere: ietf-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Media \(MIME\) type review" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2012 02:26:03 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_0312_01CCCFC9.3C9F49F0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable The OGC is requesting review of a proposed GML MIME type. Below is the = application formatted using the registration form. Thank you for your time and consideration. Carl Reed, PhD CTO OGC Type name: Application Subtype name: Standards Tree gml+xml Required parameters: None Optional parameters: "charset" The charset parameter of application/gml+xml is=20 handled in the same fashion as for application/xml, as specified in Section 3.2 of [RFC3023] =20 "version": If provided, this parameter indicates the GML version used in the GML document. Only the major and the first minor version number are provided, e.g. "3.2".=20 The value may be provided with or without quotes. i.e.,=20 application/gml+xml; version=3D3.1 shall be treated as identical to application/gml+xml; version=3D"3.1". In cases where elements from multiple GML versions are used,=20 the parameter shall indicate the highest GML version used in the document. The parameter can be used to provide protocol-specific operations, such as version-based content negotiation in HTTP or in the OGC=20 Web Feature Service. Encoding considerations: As per Section 3.2 of [RFC3023] Security considerations: The OGC Geography Markup Language (GML) is a generic format for exchanging geographic information, but application designers must not assume that it provides generic protection against security threats. RFC 3023, section 10, discusses security concerns for generic XML, which are also applicable to GML. Xlink references in GML documents may cause arbitrary URIs to be dereferenced. In this case, the security issues of RFC 3986, section 7, should be considered. Interoperability considerations: Different versions of GML specify different XML Schema documents used for the validation of GML documents. Starting with version 3.2, the GML version information is represented in the namespace. As applications may only support a subset of all published GML versions, the use of the version parameter is recommended. Published specification : GML (Geography Markup Language) is an international standard adopted by both the Open Geospatial Consortium (OGC) and International Organization for Standardization (ISO). The latest version at the time of this writing is 3.2.1 which is published by ISO as ISO 19136:2007. The standard can be accessed freely online at http://www.opengeospatial.org/standards/gml. The OGC GML MIME specification has also been approved by the OGC Membership and is published here: http://portal.opengeospatial.org/files/?artifact_id=3D37743 Applications which use this media type: GML is a generic device-, platform-, and vendor-neutral XML grammar and is supported by a range of applications creating, providing access to and processing geographic information. The use of GML is in use internationally with hundreds of deployed applications able to create and ingest GML payloads, including all of the major GIS vendors, many database providers, earth browzer applications, and so forth. Additional information: 1. Magic number(s): None. Although no byte sequences can be counted on to consistently identify GML documents, GML documents will have the sequence http://www.opengis.net/gml as part of a namespace declaration to identify the GML namespace. This will usually be towards the top of the document. 2. File extension(s): .xml or .gml 3. Macintosh file type code: TEXT 4. Object Identifiers: None The OGC is an international voluntary consensus standards organization focused on defining and maintaining standards that enable interoperability for using geospatial content and services in any application that requires the use of geospatial content or services. The OGC website is www.opengeospatial.org. Person & email address to contact for further information: Name : Clemens Portele Address:Interactive Instruments, Bonn, Germany Email : portele@interactive-instruments.de Intended usage: Common Restrictions on usage: None Author/Change controller: The GML standard is a work product of the Open Geospatial Consortium (OGC). The OGC and the GML Standards Working Group have change control over the GML standard. MIME types for use in OGC standards and formats are defined by the OGC Members and discussed and approved by the OGC Naming Authority (OGC-NA). The function and role of the OGC-NA is described in RFC 5165 and in the OGC Policies and Procedures here: http://portal.opengeospatial.org/files/?artifact_id=3D23325 Carl Reed, PhD CTO and Executive Director Standards Program Open Geospatial Consortium www.opengeospatial.org The OGC: Making Location Count! --------------------- This communication, including attachments, is for the exclusive use of = addressee and may contain proprietary, confidential or privileged = information. If you are not the intended recipient, any use, copying, = disclosure, dissemination or distribution is strictly prohibited. If you = are not the intended recipient, please notify the sender immediately by = return email and delete this communication and destroy all copies. "The important thing is not to stop questioning." -- Albert Einstein=20 "Security is mostly a superstition. It does not exist in nature. Life is = either a daring adventure or nothing." -- Helen Keller ------=_NextPart_000_0312_01CCCFC9.3C9F49F0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
The OGC is requesting review of a proposed GML MIME type. Below is = the=20 application formatted using the registration form.
 
Thank you for your time and consideration.
 
Carl Reed, PhD
CTO
OGC
 
Type name: Application
 
Subtype name: Standards Tree gml+xml
 
Required parameters:  None
 
Optional parameters:
   "charset" The charset parameter of application/gml+xml = is=20
   handled in the same fashion as for application/xml, as = specified
   in Section 3.2 of [RFC3023]
  
   "version": If provided, this parameter indicates the = GML=20 version
   used in the GML document. Only the major and the first = minor
   version number are provided, e.g. "3.2".
 
   The value may be provided with or without quotes. = i.e.,
   application/gml+xml; version=3D3.1 shall be treated as = identical=20 to
   application/gml+xml; version=3D"3.1".
 
   In cases where elements from multiple GML versions are = used,=20
   the parameter shall indicate the highest GML version = used in=20 the
   document.
 
   The parameter can be used to provide protocol-specific = operations,
   such as version-based content negotiation in HTTP or = in the=20 OGC
   Web Feature Service.
 
Encoding considerations: As per Section 3.2 of [RFC3023]
 
Security considerations:
   The OGC Geography Markup Language (GML) is a generic = format=20 for
   exchanging geographic information, but application = designers=20 must
   not assume that it provides generic protection against = security
   threats.  RFC 3023, section 10, discusses = security=20 concerns for
   generic XML, which are also applicable to GML.
 
   Xlink references in GML documents may cause arbitrary = URIs to=20 be
   dereferenced. In this case, the security issues of RFC = 3986,
   section 7, should be considered.
 
Interoperability considerations:
   Different versions of GML specify different XML Schema = documents used
   for the validation of GML documents. Starting with = version=20 3.2, the
   GML version information is represented in the = namespace.=20 As
   applications may only support a subset of all = published=20 GML
   versions, the use of the version parameter is=20 recommended.
 
Published specification :
   GML (Geography Markup Language) is an international=20 standard
   adopted by both the Open Geospatial Consortium (OGC) = and
   International Organization for Standardization (ISO). = The=20 latest
   version at the time of this writing is 3.2.1 which is=20 published by
   ISO as ISO 19136:2007. The standard can be accessed = freely=20 online at
   http://www.opengeosp= atial.org/standards/gml.
 
   The OGC GML MIME specification has also been approved = by the=20 OGC
   Membership and is published here:
   http= ://portal.opengeospatial.org/files/?artifact_id=3D37743
 
Applications which use this media type:
   GML is a generic device-, platform-, and = vendor-neutral=20 XML
   grammar and is supported by a range of applications=20 creating,
   providing access to and processing geographic = information. The=20 use
   of GML is in use internationally with hundreds of=20 deployed
   applications able to create and ingest GML payloads, = including=20 all
   of the major GIS vendors, many database providers, = earth=20 browzer
   applications, and so forth.
 
Additional information:
 
1. Magic number(s):    None. Although no byte = sequences can=20 be
    counted on to consistently identify GML = documents,=20 GML
    documents will have the sequence http://www.opengis.net/gml
    as part of a namespace declaration to identify = the=20 GML
    namespace. This will usually be towards the top = of the=20 document.
2. File extension(s): .xml or .gml
3. Macintosh file type code: TEXT
4. Object Identifiers: None
 
    The OGC is an international voluntary consensus=20 standards
    organization focused on defining and maintaining = standards that
    enable interoperability for using geospatial = content and=20 services
    in any application that requires the use of = geospatial=20 content or
    services. The OGC website is=20 www.opengeospatial.org.
 
Person & email address to contact for further = information:
 
    Name : Clemens Portele
    Address:Interactive Instruments, Bonn, = Germany
    Email : portele@interactive-instruments.de
 
Intended usage: Common
 
Restrictions on usage:
    None
 
Author/Change controller:
    The GML standard is a work product of the Open=20 Geospatial
    Consortium (OGC). The OGC and the GML Standards=20 Working
    Group have change control over the GML = standard.
 
    MIME types for use in OGC standards and formats = are=20 defined
    by the OGC Members and discussed and approved by = the=20 OGC
    Naming Authority (OGC-NA). The function and role = of the=20 OGC-NA
    is described in RFC 5165 and in the OGC Policies = and=20 Procedures
    here: http= ://portal.opengeospatial.org/files/?artifact_id=3D23325
 
Carl=20 Reed, PhD
CTO and Executive Director Standards Program
Open = Geospatial=20 Consortium
www.opengeospatial.org

The OGC: Making Location=20 Count!

---------------------

This communication, including = attachments, is for the exclusive use of addressee and may contain = proprietary,=20 confidential or privileged information. If you are not the intended = recipient,=20 any use, copying, disclosure, dissemination or distribution is strictly=20 prohibited. If you are not the intended recipient, please notify the = sender=20 immediately by return email and delete this communication and destroy = all=20 copies.

"The important thing is not to stop questioning." -- = Albert=20 Einstein
"Security is mostly a superstition. It does not exist in = nature.=20 Life is either a daring adventure or nothing." -- Helen Keller=20
------=_NextPart_000_0312_01CCCFC9.3C9F49F0--