
Return-Path: <presnick@qualcomm.com>
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 05E9711E80AE; Sun, 26 Jun 2011 20:41:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.855
X-Spam-Level: 
X-Spam-Status: No, score=-103.855 tagged_above=-999 required=5 tests=[AWL=1.256, BAYES_05=-1.11, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8avJVp7NPQM5; Sun, 26 Jun 2011 20:41:36 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 4C4F511E80A8; Sun, 26 Jun 2011 20:41:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1309146096; x=1340682096; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; z=Message-ID:=20<4E07FBEA.4090402@qualcomm.com>|Date:=20Su n,=2026=20Jun=202011=2022:41:30=20-0500|From:=20Pete=20Re snick=20<presnick@qualcomm.com>|User-Agent:=20Mozilla/5.0 =20(Macintosh=3B=20U=3B=20Intel=20Mac=20OS=20X=2010.6=3B =20en-US=3B=20rv:1.9.1.9)=20Gecko/20100630=20Eudora/3.0.4 |MIME-Version:=201.0|To:=20Julian=20Reschke=20<julian.res chke@gmx.de>|CC:=20Mykyta=20Yevstifeyev=20<evnikita2@gmai l.com>,=20<ietf-types@ietf.org>,=0D=0A=09Apps-discuss=20l ist=20<apps-discuss@ietf.org>,=0D=0A=09<public-html-comme nts-request@w3.org>|Subject:=20Re:=20[apps-discuss]=20HTM L5=20and=20RFC=202854|References:=20<4E04C38A.6090505@gma il.com>=20<4E05AFF0.9080705@gmx.de>=09<4E05C3A1.9080002@g mail.com>=20<4E05C490.8090702@gmx.de>|In-Reply-To:=20<4E0 5C490.8090702@gmx.de>|Content-Type:=20text/plain=3B=20cha rset=3D"ISO-8859-1"=3B=20format=3Dflowed |Content-Transfer-Encoding:=207bit|X-Originating-IP:=20[1 72.30.39.5]; bh=LjjgVqH1hrOHjp8p9Gb3br8yNOF67uDYwwxjEnzgo5Y=; b=liP1rZOTNcrt2y7A2dKUiAFG4DgG12Jbi0yjzrFUltklTCKsLfvcgYI0 rnK2nZpQr0WdrAuLBUj+SGQiLmrPqBClZzw03aUjHU+WOSenaZNjmaWeS 911tV8swrD4/3OSuAjXEA3h7t3vbX9f1wOMESKBNwJibKDRBo6Im0Fcby c=;
X-IronPort-AV: E=McAfee;i="5400,1158,6389"; a="100200211"
Received: from ironmsg02-r.qualcomm.com ([172.30.46.16]) by wolverine01.qualcomm.com with ESMTP; 26 Jun 2011 20:41:34 -0700
X-IronPort-AV: E=Sophos;i="4.65,429,1304319600"; d="scan'208";a="149896101"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by ironmsg02-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 26 Jun 2011 20:41:34 -0700
Received: from Macintosh-4.local (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.1.270.1; Sun, 26 Jun 2011 20:41:34 -0700
Message-ID: <4E07FBEA.4090402@qualcomm.com>
Date: Sun, 26 Jun 2011 22:41:30 -0500
From: Pete Resnick <presnick@qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
References: <4E04C38A.6090505@gmail.com> <4E05AFF0.9080705@gmx.de>	<4E05C3A1.9080002@gmail.com> <4E05C490.8090702@gmx.de>
In-Reply-To: <4E05C490.8090702@gmx.de>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: Mykyta Yevstifeyev <evnikita2@gmail.com>, public-html-comments-request@w3.org, Apps-discuss list <apps-discuss@ietf.org>, ietf-types@ietf.org
Subject: Re: [ietf-types] [apps-discuss] HTML5 and RFC 2854
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jun 2011 03:41:37 -0000

On 6/25/11 6:20 AM, Julian Reschke wrote:
> On 2011-06-25 13:16, Mykyta Yevstifeyev wrote:
>> Currently copying this to ietf-types@ietf.org . I personally think HTML5
>> should be backwards-compatible with previous version as well as the
>> media type defined for that version. So, first what should be done is
> > ...
>
> But it isn't. It forbids certain things that were allowed before and 
> which are in use.
>
> I believe that in this case, a single level of indirection, like the 
> one we have in RFC 2854, is the right thing.

I agree. HTML defines, internal to the document, the version of HTML it 
is using, often in a DOCTYPE directive. 2854 points to authoritative 
documents for the different versions of HTML and thereby defines the 
MIME type. It seems perfectly reasonable for a new IETF document to 
update (or obsolete) 2854 giving pointers to HTML5 *and all of the prior 
versions of HTML* that might be found in a text/html MIME body.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102


Return-Path: <julian.reschke@gmx.de>
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 EF6A211E8070 for <ietf-types@ietfa.amsl.com>; Sat, 25 Jun 2011 04:21:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.651
X-Spam-Level: 
X-Spam-Status: No, score=-103.651 tagged_above=-999 required=5 tests=[AWL=-1.052, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zEIY2HV-DGia for <ietf-types@ietfa.amsl.com>; Sat, 25 Jun 2011 04:21:06 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 2451E11E807B for <ietf-types@ietf.org>; Sat, 25 Jun 2011 04:21:05 -0700 (PDT)
Received: (qmail invoked by alias); 25 Jun 2011 11:21:03 -0000
Received: from p508FBF56.dip.t-dialin.net (EHLO [192.168.178.36]) [80.143.191.86] by mail.gmx.net (mp047) with SMTP; 25 Jun 2011 13:21:03 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18ff3xFSvAfjyBuM3I+WoScQtTPr74QKIacFoWJUo uy7DdbBVwOuo+2
Message-ID: <4E05C490.8090702@gmx.de>
Date: Sat, 25 Jun 2011 13:20:48 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
References: <4E04C38A.6090505@gmail.com> <4E05AFF0.9080705@gmx.de> <4E05C3A1.9080002@gmail.com>
In-Reply-To: <4E05C3A1.9080002@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: ietf-types@ietf.org, Apps-discuss list <apps-discuss@ietf.org>, public-html-comments-request@w3.org
Subject: Re: [ietf-types] [apps-discuss] HTML5 and RFC 2854
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Jun 2011 11:21:07 -0000

On 2011-06-25 13:16, Mykyta Yevstifeyev wrote:
> Currently copying this to ietf-types@ietf.org . I personally think HTML5
> should be backwards-compatible with previous version as well as the
> media type defined for that version. So, first what should be done is
 > ...

But it isn't. It forbids certain things that were allowed before and 
which are in use.

I believe that in this case, a single level of indirection, like the one 
we have in RFC 2854, is the right thing.

Best regards, Julian


Return-Path: <evnikita2@gmail.com>
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 16E24228006; Sat, 25 Jun 2011 04:16:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.472
X-Spam-Level: 
X-Spam-Status: No, score=-3.472 tagged_above=-999 required=5 tests=[AWL=0.127,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CU8MJqfQfgL5; Sat, 25 Jun 2011 04:16:07 -0700 (PDT)
Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by ietfa.amsl.com (Postfix) with ESMTP id 1433C228005; Sat, 25 Jun 2011 04:16:06 -0700 (PDT)
Received: by fxe4 with SMTP id 4so916178fxe.27 for <multiple recipients>; Sat, 25 Jun 2011 04:16:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=8n5LXtUencGcqFfHcL4/1l8t1tah0X/DYYEm+VKultA=; b=u7clKSfkETAsrkWieK1Falb8ODY8VoUa42h/yjVK7nXQ0wExiea79E02xXlE34OxD4 rmxE5qW21ASRcK6z9BveNfN94n/Q7gg4IYHWtOkYF1YgzB3yqDhPzTZ/GPpY27gH5vZu LhOf/Viik4Bwionv6JRa5AAoOMlkTbNpWK6pQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=uxDLrurymtWQtiGIpox0Tne59T2KYRRWNT/49TnEqpC6mvnEYrNoWFfofe74qDopII 9LkqZj6kRhhFhtR66I/Tg8vuZeuSDFM7WDlSjYNeJfqz6nG/u/FYeMKMTOC0yk6S09c7 eaBjEfRPvb+PpWVzGI1m23YY7o075TtmScL3I=
Received: by 10.223.20.210 with SMTP id g18mr6024401fab.30.1309000566038; Sat, 25 Jun 2011 04:16:06 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id e16sm2204488fak.41.2011.06.25.04.16.04 (version=SSLv3 cipher=OTHER); Sat, 25 Jun 2011 04:16:04 -0700 (PDT)
Message-ID: <4E05C3A1.9080002@gmail.com>
Date: Sat, 25 Jun 2011 14:16:49 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
References: <4E04C38A.6090505@gmail.com> <4E05AFF0.9080705@gmx.de>
In-Reply-To: <4E05AFF0.9080705@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Sat, 25 Jun 2011 09:56:50 -0700
Cc: ietf-types@ietf.org, Apps-discuss list <apps-discuss@ietf.org>, public-html-comments-request@w3.org
Subject: Re: [ietf-types] [apps-discuss] HTML5 and RFC 2854
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Jun 2011 11:16:09 -0000

25.06.2011 12:52, Julian Reschke wrote:
> On 2011-06-24 19:04, Mykyta Yevstifeyev wrote:
>> Hello all,
>>
>> Cross-posting this to Apps-discuss and html-comments lists. The proposed
>> HTML5 specification (http://dev.w3.org/html5/spec/), which is currently
>> in Last Call, in its Section 12.1 updates the registration of text/html
>> media type. I should note that we have RFC 2854
>> (http://tools.ietf.org/html/rfc2854) which also specifies this media
>> type. Therefore the question is what should be done with this RFC.
>> Should it be retired upon approval of HTML5? Or something else?
>>
>> Mykyta Yevstifeyev
>
> HTML5 currently tries to obsolete RFC 2854; I believe this is a problem.
>
> From <http://tools.ietf.org/html/rfc4288#section-9>:
>
>    Changes should be requested only when there are serious omissions or
>    errors in the published specification.  When review is required, a
>    change request may be denied if it renders entities that were valid
>    under the previous definition invalid under the new definition.
>
> Note the second sentence; many currently valid HTML4 documents aren't 
> valid HTML5 documents anymore. Thus, a document updating the media 
> type registration for text/html will need to continue to allow 
> HTML4.01 documents as well.
Currently copying this to ietf-types@ietf.org .  I personally think 
HTML5 should be backwards-compatible with previous version as well as 
the media type defined for that version.  So, first what should be done 
is identification whether there are some issue which make create 
confusion with the aforementioned regulations of RFC 4288.  Next, if it 
doesn't, IANA should update registration of this media type with 
reference to HTML5, not RFC 2854.  RFC 2854 itself should then be moved 
to Historic in order to represent it isn't an authoritative definition 
any more.  This won't create confusion with different definitions of the 
media type.

Just my opinion.

Mykyta Yevstifeyev
>
> See related HTML WG issue: <http://www.w3.org/html/wg/tracker/issues/53>
>
> Best regards, Julian
>



Return-Path: <stbryant@cisco.com>
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 EEF5F11E814A; Mon, 20 Jun 2011 03:47:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.524
X-Spam-Level: 
X-Spam-Status: No, score=-110.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5gdYW1bcRelE; Mon, 20 Jun 2011 03:47:54 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id C5A9C11E80C6; Mon, 20 Jun 2011 03:47:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=3137; q=dns/txt; s=iport; t=1308566874; x=1309776474; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=ARfRdzAoUMDao3XeCulLZjq0fdX3Mz+1f+UG+LoLk9c=; b=XCxIeOgBx19LZVaZvjCDc2ggqvYqqgfcB8OMo643zU2KktNfcZldBo7K iCavW9wdkkmFFs9SGq3iRff4BNhZr2xG4/dhL6O6678/0jRZXfUZ07dh7 9yn8LUhvFMH4FIpUwOJL894fBJkAAE2LF/2+bH2O+cpb6JZ9J87YnJ+X8 o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAJ8k/02Q/khN/2dsb2JhbABTplt3qiaDDw8BmimGKgSRXpAC
X-IronPort-AV: E=Sophos;i="4.65,392,1304294400"; d="scan'208";a="94858305"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-1.cisco.com with ESMTP; 20 Jun 2011 10:47:51 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p5KAlcQE023293; Mon, 20 Jun 2011 10:47:46 GMT
Received: from stbryant-mac2.local (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id p5KAlbP8012298; Mon, 20 Jun 2011 11:47:37 +0100 (BST)
Message-ID: <4DFF2579.2080009@cisco.com>
Date: Mon, 20 Jun 2011 11:48:25 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: Paul Libbrecht <paul@hoplahup.net>
References: <4DFB534C.6010606@cisco.com> <CC4AD4E4-95E1-4B0B-BED5-5916A7D1FFB3@hoplahup.net>
In-Reply-To: <CC4AD4E4-95E1-4B0B-BED5-5916A7D1FFB3@hoplahup.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: draft-ietf-sidr-repos-struct@tools.ietf.org, "iesg@ietf.org" <iesg@ietf.org>, ietf-types@ietf.org
Subject: Re: [ietf-types] Review requested for draft-ietf-sidr-repos-struct
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jun 2011 10:47:55 -0000

Hi Paul

Thank you for the suggestion.

RTG will follow IETF best practice on this and to that end
I will take the advice of my IESG colleges who are have
more experience with ietf-types.

- Stewart


On 18/06/2011 21:37, Paul Libbrecht wrote:
> Stewart,
>
> would you consider adding information in this registration request about names of the clipboard flavors?
> My modest experience has shown me that importing files with certificates is rather a painful approach but drag-and-dropping or copy-and-pasting them worked much better.
>
> If you agree, I would suggest a Windows Flavor Name (e.g. "RPKI Manifest") and Macintosh Uniform Type Identifier (e.g. "public.rpki.manifest").
>
> paul
>
>
> Le 17 juin 2011 à 15:14, Stewart Bryant a écrit :
>
>> draft-ietf-sidr-repos-struct
>>
>> https://datatracker.ietf.org/doc/draft-ietf-sidr-repos-struct/
>>
>> Makes the following types request.
>>
>> Review comments by 1 July would be appreciated.
>>
>> Many thanks
>>
>> - Stewart
>>
>>
>>
>> 7.1.1.  application/rpki-manifest
>>
>>    MIME media type name:  application
>>    MIME subtype name:  rpki-manifest
>>    Required parameters:  None
>>    Optional parameters:  None
>>    Encoding considerations:  binary
>>    Security considerations:  Carries a RPKI Manifest
>>       [I-D.ietf-sidr-rpki-manifests].
>>    Interoperability considerations:  None
>>    Published specification:  This document
>>    Applications which use this media type:  Any MIME-complaint transport
>>    Additional information:
>>       Magic number(s):  None
>>       File extension(s):  .mft
>>       Macintosh File Type Code(s):
>>    Person&   email address to contact for further information:  Geoff
>>       Huston<gih@apnic.net>
>>    Intended usage:  COMMON
>>    Author/Change controller:  Geoff Huston<gih@apnic.net>
>>
>> 7.1.2.  application/rpki-roa
>>
>>    MIME media type name:  application>
>>    MIME subtype name:  rpki-roa
>>    Required parameters:  None
>>    Optional parameters:  None
>>    Encoding considerations:  binary
>>    Security considerations:  Carries a RPKI ROA
>>       [I-D.ietf-sidr-roa-format]
>>    Interoperability considerations:  None
>>
>> Huston, et al.          Expires December 10, 2011              [Page 12]
>> Internet-Draft        ResCert Repository Structure             June 2011
>>
>>    Published specification:  This document
>>    Applications which use this media type:  Any MIME-complaint transport
>>    Additional information:
>>       Magic number(s):  None
>>       File extension(s):  .roa
>>       Macintosh File Type Code(s):
>>    Person&   email address to contact for further information:  Geoff
>>       Huston<gih@apnic.net>
>>    Intended usage:  COMMON
>>    Author/Change controller:  Geoff Huston<gih@apnic.net>
>>
>> _______________________________________________
>> ietf-types mailing list
>> ietf-types@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf-types
>


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html




Return-Path: <duerst@it.aoyama.ac.jp>
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 E816211E813A for <ietf-types@ietfa.amsl.com>; Sun, 19 Jun 2011 20:41:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.74
X-Spam-Level: 
X-Spam-Status: No, score=-99.74 tagged_above=-999 required=5 tests=[AWL=-0.550, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_48=0.6, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6g85UgQoz+e1 for <ietf-types@ietfa.amsl.com>; Sun, 19 Jun 2011 20:41:27 -0700 (PDT)
Received: from acintmta02.acbb.aoyama.ac.jp (acintmta02.acbb.aoyama.ac.jp [133.2.20.34]) by ietfa.amsl.com (Postfix) with ESMTP id 269C811E809D for <ietf-types@ietf.org>; Sun, 19 Jun 2011 20:41:26 -0700 (PDT)
Received: from acmse02.acbb.aoyama.ac.jp ([133.2.20.226]) by acintmta02.acbb.aoyama.ac.jp (secret/secret) with SMTP id p5K3fF8h002704 for <ietf-types@ietf.org>; Mon, 20 Jun 2011 12:41:15 +0900
Received: from (unknown [133.2.206.133]) by acmse02.acbb.aoyama.ac.jp with smtp id 33bb_161c_267402c4_9aef_11e0_83e8_001d0969ab06; Mon, 20 Jun 2011 12:41:15 +0900
Received: from [IPv6:::1] ([133.2.210.5]:46934) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S151F985> for <ietf-types@ietf.org> from <duerst@it.aoyama.ac.jp>;  Mon, 20 Jun 2011 12:41:10 +0900
Message-ID: <4DFEC14A.3000800@it.aoyama.ac.jp>
Date: Mon, 20 Jun 2011 12:40:58 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: "Eric Prud'hommeaux" <eric@w3.org>
References: <4DFB534C.6010606@cisco.com> <h1lmv69gdsu8s921nrr1mmvfcn65aoum3f@hive.bjoern.hoehrmann.de> <4DFB6A27.2010500@stpeter.im> <918593622.20110617170001@w3.org> <4DFC3BA6.6080407@it.aoyama.ac.jp> <20110618155402.GA21479@w3.org>
In-Reply-To: <20110618155402.GA21479@w3.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, ietf-types@ietf.org
Subject: Re: [ietf-types] are http://tools.ietf.org/html/*.html appropriate for scholarly reference?
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jun 2011 03:41:28 -0000

Hello Eric,

On 2011/06/19 0:54, Eric Prud'hommeaux wrote:
> * "Martin J. DÃ¼rst"<duerst@it.aoyama.ac.jp>  [2011-06-18 14:46+0900]

>> If you look at the 'right' copy online, e.g.
>> http://tools.ietf.org/html/rfc2048, then it actually gets updated
>> :-). So one way to help with this is to use the 'right' reference
>> where possible (e.g. in the W3C), and to push this kind of format
>> (or a similar one) from the IETF and the RFC Editor.
>
> If that is indeed the 'right' reference, I'd certainly prefer to reference the HTML, with anchors and all that web-y stuff, over http://www.ietf.org/rfc/rfc*.txt. Iirc, the /html/ dir started sort of unofficially, with a few RFCs offered as an aid to a growingly hypertext web. The decades have past and no doubt social contracts have changed; is there enough of a guarantee of stability that ISO, OASIS, W3C, journals etc. can reference the HTML versions?

In my understanding, the "official" answer to this question would still 
be: The *right* reference is referencing the RFC as such, without any 
link, the same way it would have been done pre-Web.

Of course, that's not very user-friendly these days, so that's why many 
formats add a link. Once you do that, you have to balance 
user-friendliness and stability yourself. Also, the more you use links 
to a particular location, the more you create social pressure to not 
change that. And in the end, if the link ever goes away, people will 
still know how to search for the RFC anyway. The rest is your choice.

Regards,   Martin.


Return-Path: <paul@hoplahup.net>
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 3859F21F85A4 for <ietf-types@ietfa.amsl.com>; Sat, 18 Jun 2011 13:38:21 -0700 (PDT)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5uiE4tJPPntt for <ietf-types@ietfa.amsl.com>; Sat, 18 Jun 2011 13:38:20 -0700 (PDT)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by ietfa.amsl.com (Postfix) with ESMTP id 77B3121F85A0 for <ietf-types@ietf.org>; Sat, 18 Jun 2011 13:38:20 -0700 (PDT)
Received: from [192.168.178.137] (srbk-4db7f99e.pool.mediaWays.net [77.183.249.158]) by mrelayeu.kundenserver.de (node=mreu0) with ESMTP (Nemesis) id 0Lxbn5-1PSMpT3nx5-016luG; Sat, 18 Jun 2011 22:37:57 +0200
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: Paul Libbrecht <paul@hoplahup.net>
In-Reply-To: <4DFB534C.6010606@cisco.com>
Date: Sat, 18 Jun 2011 22:37:56 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <CC4AD4E4-95E1-4B0B-BED5-5916A7D1FFB3@hoplahup.net>
References: <4DFB534C.6010606@cisco.com>
To: stbryant@cisco.com
X-Mailer: Apple Mail (2.1084)
X-Provags-ID: V02:K0:DihT0zpcmyAOKpPDLBbutVQmynCf7PR4V9JK1p4FIZr 69VYvPmp3gJ0ilLtid+nJIrKt+MCuIwlPHAhDBKCIzsFABYdBv K7QSAJvgyg9rjgelrb4RHtZCcfcMFqkcG8qJUPBvgoPyGCtMIV XYlZM0Ff39t+eJESuHyAsJDUIxFTWsM9fkJy6u40DouL+X7DL3 jlUtNCrnXhTt6w86fVPNwVNPlGLIcLbWqcgIbZqHFM=
Cc: draft-ietf-sidr-repos-struct@tools.ietf.org, ietf-types@ietf.org
Subject: Re: [ietf-types] Review requested for draft-ietf-sidr-repos-struct
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Jun 2011 20:38:21 -0000

Stewart,

would you consider adding information in this registration request about =
names of the clipboard flavors?
My modest experience has shown me that importing files with certificates =
is rather a painful approach but drag-and-dropping or copy-and-pasting =
them worked much better.

If you agree, I would suggest a Windows Flavor Name (e.g. "RPKI =
Manifest") and Macintosh Uniform Type Identifier (e.g. =
"public.rpki.manifest").

paul


Le 17 juin 2011 =E0 15:14, Stewart Bryant a =E9crit :

>=20
> draft-ietf-sidr-repos-struct
>=20
> https://datatracker.ietf.org/doc/draft-ietf-sidr-repos-struct/
>=20
> Makes the following types request.
>=20
> Review comments by 1 July would be appreciated.
>=20
> Many thanks
>=20
> - Stewart
>=20
>=20
>=20
> 7.1.1.  application/rpki-manifest
>=20
>   MIME media type name:  application
>   MIME subtype name:  rpki-manifest
>   Required parameters:  None
>   Optional parameters:  None
>   Encoding considerations:  binary
>   Security considerations:  Carries a RPKI Manifest
>      [I-D.ietf-sidr-rpki-manifests].
>   Interoperability considerations:  None
>   Published specification:  This document
>   Applications which use this media type:  Any MIME-complaint =
transport
>   Additional information:
>      Magic number(s):  None
>      File extension(s):  .mft
>      Macintosh File Type Code(s):
>   Person&  email address to contact for further information:  Geoff
>      Huston<gih@apnic.net>
>   Intended usage:  COMMON
>   Author/Change controller:  Geoff Huston<gih@apnic.net>
>=20
> 7.1.2.  application/rpki-roa
>=20
>   MIME media type name:  application>
>   MIME subtype name:  rpki-roa
>   Required parameters:  None
>   Optional parameters:  None
>   Encoding considerations:  binary
>   Security considerations:  Carries a RPKI ROA
>      [I-D.ietf-sidr-roa-format]
>   Interoperability considerations:  None
>=20
> Huston, et al.          Expires December 10, 2011              [Page =
12]
> Internet-Draft        ResCert Repository Structure             June =
2011
>=20
>   Published specification:  This document
>   Applications which use this media type:  Any MIME-complaint =
transport
>   Additional information:
>      Magic number(s):  None
>      File extension(s):  .roa
>      Macintosh File Type Code(s):
>   Person&  email address to contact for further information:  Geoff
>      Huston<gih@apnic.net>
>   Intended usage:  COMMON
>   Author/Change controller:  Geoff Huston<gih@apnic.net>
>=20
> _______________________________________________
> ietf-types mailing list
> ietf-types@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-types



Return-Path: <ericw3c@gmail.com>
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 71E4211E81B4 for <ietf-types@ietfa.amsl.com>; Sat, 18 Jun 2011 08:54:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level: 
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S1TZJpVmBkBg for <ietf-types@ietfa.amsl.com>; Sat, 18 Jun 2011 08:54:06 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id BF03411E81AA for <ietf-types@ietf.org>; Sat, 18 Jun 2011 08:54:06 -0700 (PDT)
Received: by vws12 with SMTP id 12so3251164vws.31 for <ietf-types@ietf.org>; Sat, 18 Jun 2011 08:54:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:date:from:to:cc:subject:message-id :references:mime-version:content-type:content-disposition :content-transfer-encoding:in-reply-to:organization:user-agent; bh=FNIWC0DT9JF7y9QkDWQxjklGwNsVP44+/cOvnBQNC6Q=; b=UYfzrNgVdzNgADrq2BnlwBqWTFvAyfl87tqE3W20/fzUDxQ4Z4rDT8ISf6bqdXaToW SZTfuqcf2emxuv+R+zDf7nR+VSofZwtT/whPUlxhCloMm3z1aSxlk3kZnYlco9kSROkb k6mGhr46IEZ/EJnfNiAvujpKbpUXL8vt1pST4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:content-transfer-encoding :in-reply-to:organization:user-agent; b=ck3vqy7bysHU+R6n1uASRDQUUbeoU4Adm4YMps1bfvhgaQ7B0QVV2C0e/iYDkFsNx4 8ot4lnj8bBgDeg4zF2bg9O+huqiIlIXKnvCCwT3U8/XcLToIEw/DDBjQ5mJUhFTnCOoP ngiZE/b+8B+4CtwhzfKG6LCzWVJoyYvLTGc2w=
Received: by 10.52.180.133 with SMTP id do5mr1523315vdc.307.1308412446153; Sat, 18 Jun 2011 08:54:06 -0700 (PDT)
Received: from w3.org (c-24-218-124-254.hsd1.ma.comcast.net [24.218.124.254]) by mx.google.com with ESMTPS id q1sm1256650vdt.23.2011.06.18.08.54.05 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 18 Jun 2011 08:54:05 -0700 (PDT)
Sender: "Eric Prud'hommeaux" <ericw3c@gmail.com>
Date: Sat, 18 Jun 2011 11:54:04 -0400
From: Eric Prud'hommeaux <eric@w3.org>
To: =?utf-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Message-ID: <20110618155402.GA21479@w3.org>
References: <4DFB534C.6010606@cisco.com> <h1lmv69gdsu8s921nrr1mmvfcn65aoum3f@hive.bjoern.hoehrmann.de> <4DFB6A27.2010500@stpeter.im> <918593622.20110617170001@w3.org> <4DFC3BA6.6080407@it.aoyama.ac.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <4DFC3BA6.6080407@it.aoyama.ac.jp>
Organization: World Wide Web Consortium (W3C) - http://www.w3.org/
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, ietf-types@ietf.org
Subject: [ietf-types] are http://tools.ietf.org/html/*.html appropriate for scholarly reference?
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Jun 2011 15:54:07 -0000

* "Martin J. DÃ¼rst" <duerst@it.aoyama.ac.jp> [2011-06-18 14:46+0900]
> On 2011/06/18 0:00, Chris Lilley wrote:
> 
> >People reading RFC 2048 think they know
> >a) which template to use
> 
> >Also, I assume its a policy decision that RFCs once published are never updated to say that they are obsoleted; but perhapsit is time to review that decision? I imagine most people consult an online copy nowadays rather than taking out a dusty pile of lineprinter paper to read.
> 
> If you look at the 'right' copy online, e.g.
> http://tools.ietf.org/html/rfc2048, then it actually gets updated
> :-). So one way to help with this is to use the 'right' reference
> where possible (e.g. in the W3C), and to push this kind of format
> (or a similar one) from the IETF and the RFC Editor.

If that is indeed the 'right' reference, I'd certainly prefer to reference the HTML, with anchors and all that web-y stuff, over http://www.ietf.org/rfc/rfc*.txt. Iirc, the /html/ dir started sort of unofficially, with a few RFCs offered as an aid to a growingly hypertext web. The decades have past and no doubt social contracts have changed; is there enough of a guarantee of stability that ISO, OASIS, W3C, journals etc. can reference the HTML versions?

> Regards,   Martin.
> _______________________________________________
> ietf-types mailing list
> ietf-types@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-types

-- 
-ericP


Return-Path: <julian.reschke@gmx.de>
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 BD51B11E80A1 for <ietf-types@ietfa.amsl.com>; Sat, 18 Jun 2011 01:10:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.572
X-Spam-Level: 
X-Spam-Status: No, score=-102.572 tagged_above=-999 required=5 tests=[AWL=0.027, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WoMpz55a1Xv4 for <ietf-types@ietfa.amsl.com>; Sat, 18 Jun 2011 01:10:46 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 0222E11E8082 for <ietf-types@ietf.org>; Sat, 18 Jun 2011 01:10:40 -0700 (PDT)
Received: (qmail invoked by alias); 18 Jun 2011 08:10:26 -0000
Received: from p508FC09F.dip.t-dialin.net (EHLO [192.168.178.36]) [80.143.192.159] by mail.gmx.net (mp065) with SMTP; 18 Jun 2011 10:10:26 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+744oRefG7v/GdZaT3GQq3EyR8QQULcjubJdTCQ5 kTe3qEFPxBjEai
Message-ID: <4DFC5D68.4040806@gmx.de>
Date: Sat, 18 Jun 2011 10:10:16 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: Chris Lilley <chris@w3.org>
References: <4DFB534C.6010606@cisco.com>	<h1lmv69gdsu8s921nrr1mmvfcn65aoum3f@hive.bjoern.hoehrmann.de>	<4DFB6A27.2010500@stpeter.im> <918593622.20110617170001@w3.org>
In-Reply-To: <918593622.20110617170001@w3.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, ietf-types@ietf.org
Subject: Re: [ietf-types] outdated template
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Jun 2011 08:10:46 -0000

On 2011-06-17 17:00, Chris Lilley wrote:
> On Friday, June 17, 2011, 4:52:23 PM, Peter wrote:
>
> PSA>  On 6/17/11 7:22 AM, Bjoern Hoehrmann wrote:
>>> * Stewart Bryant wrote:
>>>> 7.1.1.  application/rpki-manifest
>
>>>>     MIME media type name:  application
>>>>     MIME subtype name:  rpki-manifest
>
>>> This uses an outdated template, the current template is in RFC 4288.
>
> PSA>  Bjoern, I notice that many of your reviews start with "this uses an
> PSA>  outdated template". Do we need to update pointers somewhere so that
> PSA>  people know which template to use?
>
> People reading RFC 4288  know
> a) which template to use
> b) that it obsoletes RFC 2048
>
> People reading RFC 2048 think they know
> a) which template to use
>
> and they know that it obsoletes some older RFCs but don't know (from reading the text) that it is obsoleted by RFC 4288.
>
> I have seen a checker for documents, to make sure the referenced RFCs are up to date; is there a tool (that doesn't start with a document), to see if a single RFC is the latest?
> ...

Nowadays there's a status page at rfc-editor.org, for instance:

   http://www.rfc-editor.org/info/rfc2048

And yes, this link appears in the new RFCs as well; but as you have 
observed this doesn't help with old ones.

And, as Martin pointed out, the HTMLized versions on tools.ietf.org are 
very useful. Use them whenever you can (despite they are not the 
"canonical" versions).

Best regards, Julian


Return-Path: <duerst@it.aoyama.ac.jp>
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 D94CD21F84FA for <ietf-types@ietfa.amsl.com>; Fri, 17 Jun 2011 22:46:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.123
X-Spam-Level: 
X-Spam-Status: No, score=-100.123 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zl4DZFBPFQEX for <ietf-types@ietfa.amsl.com>; Fri, 17 Jun 2011 22:46:48 -0700 (PDT)
Received: from acintmta01.acbb.aoyama.ac.jp (acintmta01.acbb.aoyama.ac.jp [133.2.20.33]) by ietfa.amsl.com (Postfix) with ESMTP id E37D521F84F9 for <ietf-types@ietf.org>; Fri, 17 Jun 2011 22:46:46 -0700 (PDT)
Received: from acmse01.acbb.aoyama.ac.jp ([133.2.20.226]) by acintmta01.acbb.aoyama.ac.jp (secret/secret) with SMTP id p5I5kaa2012193 for <ietf-types@ietf.org>; Sat, 18 Jun 2011 14:46:37 +0900
Received: from (unknown [133.2.206.133]) by acmse01.acbb.aoyama.ac.jp with smtp id 1efa_26c3_5479b9e8_996e_11e0_ab05_001d096c5b62; Sat, 18 Jun 2011 14:46:36 +0900
Received: from [IPv6:::1] ([133.2.210.5]:34187) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S151E9F4> for <ietf-types@ietf.org> from <duerst@it.aoyama.ac.jp>;  Sat, 18 Jun 2011 14:46:33 +0900
Message-ID: <4DFC3BA6.6080407@it.aoyama.ac.jp>
Date: Sat, 18 Jun 2011 14:46:14 +0900
From: =?ISO-8859-1?Q?=22Martin_J=2E_D=FCrst=22?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Chris Lilley <chris@w3.org>
References: <4DFB534C.6010606@cisco.com>	<h1lmv69gdsu8s921nrr1mmvfcn65aoum3f@hive.bjoern.hoehrmann.de>	<4DFB6A27.2010500@stpeter.im> <918593622.20110617170001@w3.org>
In-Reply-To: <918593622.20110617170001@w3.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, ietf-types@ietf.org
Subject: Re: [ietf-types] outdated template
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Jun 2011 05:46:49 -0000

On 2011/06/18 0:00, Chris Lilley wrote:

> People reading RFC 2048 think they know
> a) which template to use

> Also, I assume its a policy decision that RFCs once published are never updated to say that they are obsoleted; but perhapsit is time to review that decision? I imagine most people consult an online copy nowadays rather than taking out a dusty pile of lineprinter paper to read.

If you look at the 'right' copy online, e.g. 
http://tools.ietf.org/html/rfc2048, then it actually gets updated :-). 
So one way to help with this is to use the 'right' reference where 
possible (e.g. in the W3C), and to push this kind of format (or a 
similar one) from the IETF and the RFC Editor.

Regards,   Martin.


Return-Path: <stpeter@stpeter.im>
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 4EC6111E8179 for <ietf-types@ietfa.amsl.com>; Fri, 17 Jun 2011 08:07:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.517
X-Spam-Level: 
X-Spam-Status: No, score=-102.517 tagged_above=-999 required=5 tests=[AWL=0.082, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I9w7PJ56Jznn for <ietf-types@ietfa.amsl.com>; Fri, 17 Jun 2011 08:07:46 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 728B011E809C for <ietf-types@ietf.org>; Fri, 17 Jun 2011 08:07:46 -0700 (PDT)
Received: from dhcp-64-101-72-207.cisco.com (dhcp-64-101-72-207.cisco.com [64.101.72.207]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 5B72E400A5; Fri, 17 Jun 2011 09:08:13 -0600 (MDT)
Message-ID: <4DFB6DBF.7030503@stpeter.im>
Date: Fri, 17 Jun 2011 09:07:43 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Chris Lilley <chris@w3.org>
References: <4DFB534C.6010606@cisco.com> <h1lmv69gdsu8s921nrr1mmvfcn65aoum3f@hive.bjoern.hoehrmann.de> <4DFB6A27.2010500@stpeter.im> <918593622.20110617170001@w3.org>
In-Reply-To: <918593622.20110617170001@w3.org>
X-Enigmail-Version: 1.1.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms030104080205050903090606"
Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, ietf-types@ietf.org
Subject: Re: [ietf-types] outdated template
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jun 2011 15:07:48 -0000

This is a cryptographically signed message in MIME format.

--------------ms030104080205050903090606
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 6/17/11 9:00 AM, Chris Lilley wrote:
> On Friday, June 17, 2011, 4:52:23 PM, Peter wrote:
>=20
> PSA> On 6/17/11 7:22 AM, Bjoern Hoehrmann wrote:
>>> * Stewart Bryant wrote:
>>>> 7.1.1.  application/rpki-manifest
>=20
>>>> MIME media type name:  application MIME subtype name:
>>>> rpki-manifest
>=20
>>> This uses an outdated template, the current template is in RFC
>>> 4288.
>=20
> PSA> Bjoern, I notice that many of your reviews start with "this uses
> an PSA> outdated template". Do we need to update pointers somewhere
> so that PSA> people know which template to use?
>=20
> People reading RFC 4288  know a) which template to use b) that it
> obsoletes RFC 2048
>=20
> People reading RFC 2048 think they know a) which template to use
>=20
> and they know that it obsoletes some older RFCs but don't know (from
> reading the text) that it is obsoleted by RFC 4288.

People reading http://tools.ietf.org/html/rfc2048 know that it's been
obsoleted, but the plain text versions don't have the forward link.

Peter

--=20
Peter Saint-Andre
https://stpeter.im/




--------------ms030104080205050903090606
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIITzjCC
BjQwggQcoAMCAQICASMwDQYJKoZIhvcNAQELBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoT
DVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3
MTAyNDIxMDMzM1oXDTE3MTAyNDIxMDMzM1owgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALmjSW4SPiDKlAinvVeL
ZOVfItiuP1aRHL530E7QUc9icCwL33+PH+Js1HAh8CgWFl34sOxx1FJyS/C4VLPRsqDfP72j
tzCVUAL0DAxZ7wgzQvFz7x61jGxfhYhqYb1+PPOLkYBbkRIrPMg3dLEdKmXIYJYXDH+mB/V/
jLo73/Kb7h/rNoNg/oHHSv5Jolyvp5IY2btfcTBfW/telEFj5rDTX2juTvZ3Qhf3XQX5ca3Q
7A10zrUV/cWJOJ7F5RltbEIaboZmX5JBUb3FhUiAdBotehAX6DbDOuYoJtVxmGof6GuVGcPo
98K4TJf8FHo+UA9EOVDp/W7fCqKT4sXk/XkCAwEAAaOCAa0wggGpMA8GA1UdEwEB/wQFMAMB
Af8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBR7iZySlyShhEcCy3T8LvSs3DLl8zAfBgNV
HSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH
MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20v
c2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQELBQADggIBAGpd
SbdLFMhirxK37V4gE00+uW74UdAXtDgQI3AsRZWtaRtKHgAxFBSteqz4kDkeAjH/1b+K8tQR
6cxSI2nho7qOaPW/UpzOfSS/MeKK/9vfM2lfs+uItXH7LWtvS9wD1erfH1a+BXHCrCp4LA1l
fADDhRIiGTSS3i0Zu5xV3INNRHrCCCl6patltQ8RZTqzDMri7ombgIxjN51Zo7xV77EZcThV
0GA8iIN+7T53uHhUJpjfLIztHs/69OclRvHux9hCflfOm7GY5Sc4nqjfES+5XPArGGWiQSEk
ez37QfXqsxO3oCHK4b3DFZysG4uyOuC/WL80ab3muQ3tgwjBhq0D3JZN5kvu5gSuNZPa1WrV
hEgXkd6C7s5stqB6/htVpshG08jRz9DEutGM9oKQ1ncTivbfPNx7pILoHWvvT7N5i/puVoNu
bPUmLXh/2wA6wzAzuuoONiIL14Xpw6jLSnqpaLWElo2yTIFZ/CU/nCvvpW1Dj1457P3Ci9bD
0RPkWSR+CuucpgxrEmaw4UOLxflzuYYaq1RJwygOO5K0s2bAWOcXpgteyUOnQ3d/EjJAWRri
2v0ubiq+4H3KUOMlbznlPAY/1T8YyyJPM88+Ueahe/AW1zoUwZayNcTnuM7cq6yBV8Wr3GOI
LFXhtT0UVuJLChPMJKVKVsa7qNorlLkMMIIGxzCCBa+gAwIBAgICAIswDQYJKoZIhvcNAQEF
BQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJT
ZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBD
bGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTAeFw0xMDEwMTQwMTM2MzRa
Fw0xMjEwMTQxMjAxMDdaMIHAMSAwHgYDVQQNExcyNzQ1ODEtOU5YMDRxeExEYjBvNDY5VDEL
MAkGA1UEBhMCVVMxETAPBgNVBAgTCENvbG9yYWRvMQ8wDQYDVQQHEwZEZW52ZXIxLDAqBgNV
BAsTI1N0YXJ0Q29tIFRydXN0ZWQgQ2VydGlmaWNhdGUgTWVtYmVyMRowGAYDVQQDExFQZXRl
ciBTYWludC1BbmRyZTEhMB8GCSqGSIb3DQEJARYSc3RwZXRlckBzdHBldGVyLmltMIIBIjAN
BgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuERvnrkpQTx9wbJfgxbNKEYvt0IilecZRUM6
wrbCzIUPCocuYhaAJcQoqIyHaKybPQ7f+DIGIAolAa3dHnNdlsXP2smTft/ZNpj10PIG5bil
NAqLUYwmLJaEaqY7BMW8423U3blW43/luLJk/Pq4OsWcw7AK3LeVh1U/HOgqhin26N3h72X1
nbLEpZFrgcp8egmWtXLCbLBDMqUK3j6wjLldni79muzYEVqU0A5GqSeb8Wc4kIx8VI5yL24J
KzinG2iVRP5ZDEbOZETzBXJabUsV56XSxqPG9DK6ke+ybCiL/wKV1HFqdtFB1y25lfvHgOP2
gyEApBKEDNjgLmKyyQIDAQABo4IC+zCCAvcwCQYDVR0TBAIwADALBgNVHQ8EBAMCBLAwHQYD
VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBS2EW2iNB+g0EibKJLBdv8I
eLovVDAfBgNVHSMEGDAWgBR7iZySlyShhEcCy3T8LvSs3DLl8zAdBgNVHREEFjAUgRJzdHBl
dGVyQHN0cGV0ZXIuaW0wggFCBgNVHSAEggE5MIIBNTCCATEGCysGAQQBgbU3AQICMIIBIDAu
BggrBgEFBQcCARYiaHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjA0BggrBgEF
BQcCARYoaHR0cDovL3d3dy5zdGFydHNzbC5jb20vaW50ZXJtZWRpYXRlLnBkZjCBtwYIKwYB
BQUHAgIwgaowFBYNU3RhcnRDb20gTHRkLjADAgEBGoGRTGltaXRlZCBMaWFiaWxpdHksIHNl
ZSBzZWN0aW9uICpMZWdhbCBMaW1pdGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENlcnRpZmlj
YXRpb24gQXV0aG9yaXR5IFBvbGljeSBhdmFpbGFibGUgYXQgaHR0cDovL3d3dy5zdGFydHNz
bC5jb20vcG9saWN5LnBkZjBjBgNVHR8EXDBaMCugKaAnhiVodHRwOi8vd3d3LnN0YXJ0c3Ns
LmNvbS9jcnR1My1jcmwuY3JsMCugKaAnhiVodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9jcnR1
My1jcmwuY3JsMIGOBggrBgEFBQcBAQSBgTB/MDkGCCsGAQUFBzABhi1odHRwOi8vb2NzcC5z
dGFydHNzbC5jb20vc3ViL2NsYXNzMy9jbGllbnQvY2EwQgYIKwYBBQUHMAKGNmh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2NlcnRzL3N1Yi5jbGFzczMuY2xpZW50LmNhLmNydDAjBgNVHRIE
HDAahhhodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS8wDQYJKoZIhvcNAQEFBQADggEBADVtbXJG
tKAr55xc/OUM546gXUybI72Bank0w739Mv+9BBNtq9rMEvCnLmSKhBi76c1mdXh6zXs8RQDo
6nR/aPabE3llF2T4z80smi9jfnl3y9dpu9TcgDoqDLZ7a2lBlW656XAAQzHjvLp2MC7/mxlg
PYH2axa+q40mAYM20GbNsAEGbWQT1IqIh0BcLLsgbaMJHbyG/57zd9JLyMX3Vry1L1fJRQr3
GeLxMV5RtxN+mBgxrwFz/cOc09COiFExlsHgekpB5O43gqsAU16MXypyoSt4MrSfKTMHIGx6
2RF/M6vqUlvhi28gk2ZUvQ/+OX5+gjcZyooEzAAn4RuOKNswggbHMIIFr6ADAgECAgIAizAN
BgkqhkiG9w0BAQUFADCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4x
KzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMT
L1N0YXJ0Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBMB4XDTEw
MTAxNDAxMzYzNFoXDTEyMTAxNDEyMDEwN1owgcAxIDAeBgNVBA0TFzI3NDU4MS05TlgwNHF4
TERiMG80NjlUMQswCQYDVQQGEwJVUzERMA8GA1UECBMIQ29sb3JhZG8xDzANBgNVBAcTBkRl
bnZlcjEsMCoGA1UECxMjU3RhcnRDb20gVHJ1c3RlZCBDZXJ0aWZpY2F0ZSBNZW1iZXIxGjAY
BgNVBAMTEVBldGVyIFNhaW50LUFuZHJlMSEwHwYJKoZIhvcNAQkBFhJzdHBldGVyQHN0cGV0
ZXIuaW0wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC4RG+euSlBPH3Bsl+DFs0o
Ri+3QiKV5xlFQzrCtsLMhQ8Khy5iFoAlxCiojIdorJs9Dt/4MgYgCiUBrd0ec12Wxc/ayZN+
39k2mPXQ8gbluKU0CotRjCYsloRqpjsExbzjbdTduVbjf+W4smT8+rg6xZzDsArct5WHVT8c
6CqGKfbo3eHvZfWdssSlkWuBynx6CZa1csJssEMypQrePrCMuV2eLv2a7NgRWpTQDkapJ5vx
ZziQjHxUjnIvbgkrOKcbaJVE/lkMRs5kRPMFclptSxXnpdLGo8b0MrqR77JsKIv/ApXUcWp2
0UHXLbmV+8eA4/aDIQCkEoQM2OAuYrLJAgMBAAGjggL7MIIC9zAJBgNVHRMEAjAAMAsGA1Ud
DwQEAwIEsDAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFLYRbaI0
H6DQSJsoksF2/wh4ui9UMB8GA1UdIwQYMBaAFHuJnJKXJKGERwLLdPwu9KzcMuXzMB0GA1Ud
EQQWMBSBEnN0cGV0ZXJAc3RwZXRlci5pbTCCAUIGA1UdIASCATkwggE1MIIBMQYLKwYBBAGB
tTcBAgIwggEgMC4GCCsGAQUFBwIBFiJodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3ku
cGRmMDQGCCsGAQUFBwIBFihodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9pbnRlcm1lZGlhdGUu
cGRmMIG3BggrBgEFBQcCAjCBqjAUFg1TdGFydENvbSBMdGQuMAMCAQEagZFMaW1pdGVkIExp
YWJpbGl0eSwgc2VlIHNlY3Rpb24gKkxlZ2FsIExpbWl0YXRpb25zKiBvZiB0aGUgU3RhcnRD
b20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgUG9saWN5IGF2YWlsYWJsZSBhdCBodHRwOi8v
d3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3kucGRmMGMGA1UdHwRcMFowK6ApoCeGJWh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2NydHUzLWNybC5jcmwwK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRz
c2wuY29tL2NydHUzLWNybC5jcmwwgY4GCCsGAQUFBwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0
dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3MzL2NsaWVudC9jYTBCBggrBgEFBQcw
AoY2aHR0cDovL3d3dy5zdGFydHNzbC5jb20vY2VydHMvc3ViLmNsYXNzMy5jbGllbnQuY2Eu
Y3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzANBgkqhkiG9w0BAQUF
AAOCAQEANW1tcka0oCvnnFz85QznjqBdTJsjvYFqeTTDvf0y/70EE22r2swS8KcuZIqEGLvp
zWZ1eHrNezxFAOjqdH9o9psTeWUXZPjPzSyaL2N+eXfL12m71NyAOioMtntraUGVbrnpcABD
MeO8unYwLv+bGWA9gfZrFr6rjSYBgzbQZs2wAQZtZBPUioiHQFwsuyBtowkdvIb/nvN30kvI
xfdWvLUvV8lFCvcZ4vExXlG3E36YGDGvAXP9w5zT0I6IUTGWweB6SkHk7jeCqwBTXoxfKnKh
K3gytJ8pMwcgbHrZEX8zq+pSW+GLbyCTZlS9D/45fn6CNxnKigTMACfhG44o2zGCA80wggPJ
AgEBMIGTMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UE
CxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRD
b20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMAkGBSsOAwIa
BQCgggIOMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDYx
NzE1MDc0M1owIwYJKoZIhvcNAQkEMRYEFNbzwyGQWeptHlpK62VGhi787O8OMF8GCSqGSIb3
DQEJDzFSMFAwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggq
hkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBpAYJKwYBBAGCNxAEMYGWMIGT
MIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2Vj
dXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xh
c3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMIGmBgsqhkiG9w0BCRAC
CzGBlqCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNV
BAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0
Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgIAizANBgkqhkiG
9w0BAQEFAASCAQCRfN1dvepMjb4QEgzex5hC2TF9+hVyblAaZe5dwLMVbWTlHFvKTNAi+nMT
7QPjaDNYgBWBTYnhLpBgWz9O+HT1TDkWQ/r8Svs4DHZzmSOj6HzJ66t01fSuSJJ61BnxFs4y
Pvs516BIrB0g6dddkrr3lgSeTB87sjyYQbneCTp+j58qp9wH4iTo0zQtyWNPwz/Oyn/cfRLw
h1ybOBEWlUR9UZsmca4HZPafk2S3CRnZZAueYbqBc5dM8knnaiV53haxlDkMurYE2PkRbMTH
cFCFktAMZnUpga7x8rqYjdaHocQB+AiXNAc3x+BNuQLwxl1LB7ySSTmbOUK++ihAkBvjAAAA
AAAA
--------------ms030104080205050903090606--


Return-Path: <chris@w3.org>
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 E99C311E819D for <ietf-types@ietfa.amsl.com>; Fri, 17 Jun 2011 08:04:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EBJV0QOxUw0p for <ietf-types@ietfa.amsl.com>; Fri, 17 Jun 2011 08:04:30 -0700 (PDT)
Received: from jay.w3.org (ssh.w3.org [128.30.52.60]) by ietfa.amsl.com (Postfix) with ESMTP id 49D0111E8129 for <ietf-types@ietf.org>; Fri, 17 Jun 2011 08:04:30 -0700 (PDT)
Received: from localhost ([127.0.0.1]) by jay.w3.org with esmtpa (Exim 4.69) (envelope-from <chris@w3.org>) id 1QXaaw-0002mE-Ng; Fri, 17 Jun 2011 11:04:26 -0400
Date: Fri, 17 Jun 2011 17:00:01 +0200
From: Chris Lilley <chris@w3.org>
X-Mailer: The Bat! (v3.95.6) Home
Organization: W3C
X-Priority: 3 (Normal)
Message-ID: <918593622.20110617170001@w3.org>
To: Peter Saint-Andre <stpeter@stpeter.im>
In-Reply-To: <4DFB6A27.2010500@stpeter.im>
References: <4DFB534C.6010606@cisco.com> <h1lmv69gdsu8s921nrr1mmvfcn65aoum3f@hive.bjoern.hoehrmann.de> <4DFB6A27.2010500@stpeter.im>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, ietf-types@ietf.org
Subject: Re: [ietf-types] outdated template (was: Re: Review requested for draft-ietf-sidr-repos-struct)
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Chris Lilley <chris@w3.org>
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jun 2011 15:04:31 -0000

On Friday, June 17, 2011, 4:52:23 PM, Peter wrote:

PSA> On 6/17/11 7:22 AM, Bjoern Hoehrmann wrote:
>> * Stewart Bryant wrote:
>>> 7.1.1.  application/rpki-manifest

>>>    MIME media type name:  application
>>>    MIME subtype name:  rpki-manifest

>> This uses an outdated template, the current template is in RFC 4288.

PSA> Bjoern, I notice that many of your reviews start with "this uses an
PSA> outdated template". Do we need to update pointers somewhere so that
PSA> people know which template to use?

People reading RFC 4288  know
a) which template to use
b) that it obsoletes RFC 2048

People reading RFC 2048 think they know
a) which template to use

and they know that it obsoletes some older RFCs but don't know (from reading the text) that it is obsoleted by RFC 4288.

I have seen a checker for documents, to make sure the referenced RFCs are up to date; is there a tool (that doesn't start with a document), to see if a single RFC is the latest?

Also, I assume its a policy decision that RFCs once published are never updated to say that they are obsoleted; but perhapsit is time to review that decision? I imagine most people consult an online copy nowadays rather than taking out a dusty pile of lineprinter paper to read.


-- 
 Chris Lilley   Technical Director, Interaction Domain                 
 W3C Graphics Activity Lead, Fonts Activity Lead
 Co-Chair, W3C Hypertext CG
 Member, CSS, WebFonts, SVG Working Groups



Return-Path: <stpeter@stpeter.im>
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 5D21A11E818F for <ietf-types@ietfa.amsl.com>; Fri, 17 Jun 2011 07:52:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.509
X-Spam-Level: 
X-Spam-Status: No, score=-102.509 tagged_above=-999 required=5 tests=[AWL=0.090, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vBqRqYnRBgKF for <ietf-types@ietfa.amsl.com>; Fri, 17 Jun 2011 07:52:28 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id AACD511E8179 for <ietf-types@ietf.org>; Fri, 17 Jun 2011 07:52:25 -0700 (PDT)
Received: from dhcp-64-101-72-207.cisco.com (dhcp-64-101-72-207.cisco.com [64.101.72.207]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 9476D400A5; Fri, 17 Jun 2011 08:52:52 -0600 (MDT)
Message-ID: <4DFB6A27.2010500@stpeter.im>
Date: Fri, 17 Jun 2011 08:52:23 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Bjoern Hoehrmann <derhoermi@gmx.net>
References: <4DFB534C.6010606@cisco.com> <h1lmv69gdsu8s921nrr1mmvfcn65aoum3f@hive.bjoern.hoehrmann.de>
In-Reply-To: <h1lmv69gdsu8s921nrr1mmvfcn65aoum3f@hive.bjoern.hoehrmann.de>
X-Enigmail-Version: 1.1.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms050701020602040503040303"
Cc: ietf-types@ietf.org
Subject: [ietf-types] outdated template (was: Re: Review requested for draft-ietf-sidr-repos-struct)
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jun 2011 14:52:34 -0000

This is a cryptographically signed message in MIME format.

--------------ms050701020602040503040303
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 6/17/11 7:22 AM, Bjoern Hoehrmann wrote:
> * Stewart Bryant wrote:
>> 7.1.1.  application/rpki-manifest
>>
>>    MIME media type name:  application
>>    MIME subtype name:  rpki-manifest
>=20
> This uses an outdated template, the current template is in RFC 4288.

Bjoern, I notice that many of your reviews start with "this uses an
outdated template". Do we need to update pointers somewhere so that
people know which template to use?

Peter

--=20
Peter Saint-Andre
https://stpeter.im/




--------------ms050701020602040503040303
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIITzjCC
BjQwggQcoAMCAQICASMwDQYJKoZIhvcNAQELBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoT
DVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3
MTAyNDIxMDMzM1oXDTE3MTAyNDIxMDMzM1owgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALmjSW4SPiDKlAinvVeL
ZOVfItiuP1aRHL530E7QUc9icCwL33+PH+Js1HAh8CgWFl34sOxx1FJyS/C4VLPRsqDfP72j
tzCVUAL0DAxZ7wgzQvFz7x61jGxfhYhqYb1+PPOLkYBbkRIrPMg3dLEdKmXIYJYXDH+mB/V/
jLo73/Kb7h/rNoNg/oHHSv5Jolyvp5IY2btfcTBfW/telEFj5rDTX2juTvZ3Qhf3XQX5ca3Q
7A10zrUV/cWJOJ7F5RltbEIaboZmX5JBUb3FhUiAdBotehAX6DbDOuYoJtVxmGof6GuVGcPo
98K4TJf8FHo+UA9EOVDp/W7fCqKT4sXk/XkCAwEAAaOCAa0wggGpMA8GA1UdEwEB/wQFMAMB
Af8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBR7iZySlyShhEcCy3T8LvSs3DLl8zAfBgNV
HSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH
MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20v
c2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQELBQADggIBAGpd
SbdLFMhirxK37V4gE00+uW74UdAXtDgQI3AsRZWtaRtKHgAxFBSteqz4kDkeAjH/1b+K8tQR
6cxSI2nho7qOaPW/UpzOfSS/MeKK/9vfM2lfs+uItXH7LWtvS9wD1erfH1a+BXHCrCp4LA1l
fADDhRIiGTSS3i0Zu5xV3INNRHrCCCl6patltQ8RZTqzDMri7ombgIxjN51Zo7xV77EZcThV
0GA8iIN+7T53uHhUJpjfLIztHs/69OclRvHux9hCflfOm7GY5Sc4nqjfES+5XPArGGWiQSEk
ez37QfXqsxO3oCHK4b3DFZysG4uyOuC/WL80ab3muQ3tgwjBhq0D3JZN5kvu5gSuNZPa1WrV
hEgXkd6C7s5stqB6/htVpshG08jRz9DEutGM9oKQ1ncTivbfPNx7pILoHWvvT7N5i/puVoNu
bPUmLXh/2wA6wzAzuuoONiIL14Xpw6jLSnqpaLWElo2yTIFZ/CU/nCvvpW1Dj1457P3Ci9bD
0RPkWSR+CuucpgxrEmaw4UOLxflzuYYaq1RJwygOO5K0s2bAWOcXpgteyUOnQ3d/EjJAWRri
2v0ubiq+4H3KUOMlbznlPAY/1T8YyyJPM88+Ueahe/AW1zoUwZayNcTnuM7cq6yBV8Wr3GOI
LFXhtT0UVuJLChPMJKVKVsa7qNorlLkMMIIGxzCCBa+gAwIBAgICAIswDQYJKoZIhvcNAQEF
BQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJT
ZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBD
bGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTAeFw0xMDEwMTQwMTM2MzRa
Fw0xMjEwMTQxMjAxMDdaMIHAMSAwHgYDVQQNExcyNzQ1ODEtOU5YMDRxeExEYjBvNDY5VDEL
MAkGA1UEBhMCVVMxETAPBgNVBAgTCENvbG9yYWRvMQ8wDQYDVQQHEwZEZW52ZXIxLDAqBgNV
BAsTI1N0YXJ0Q29tIFRydXN0ZWQgQ2VydGlmaWNhdGUgTWVtYmVyMRowGAYDVQQDExFQZXRl
ciBTYWludC1BbmRyZTEhMB8GCSqGSIb3DQEJARYSc3RwZXRlckBzdHBldGVyLmltMIIBIjAN
BgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuERvnrkpQTx9wbJfgxbNKEYvt0IilecZRUM6
wrbCzIUPCocuYhaAJcQoqIyHaKybPQ7f+DIGIAolAa3dHnNdlsXP2smTft/ZNpj10PIG5bil
NAqLUYwmLJaEaqY7BMW8423U3blW43/luLJk/Pq4OsWcw7AK3LeVh1U/HOgqhin26N3h72X1
nbLEpZFrgcp8egmWtXLCbLBDMqUK3j6wjLldni79muzYEVqU0A5GqSeb8Wc4kIx8VI5yL24J
KzinG2iVRP5ZDEbOZETzBXJabUsV56XSxqPG9DK6ke+ybCiL/wKV1HFqdtFB1y25lfvHgOP2
gyEApBKEDNjgLmKyyQIDAQABo4IC+zCCAvcwCQYDVR0TBAIwADALBgNVHQ8EBAMCBLAwHQYD
VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBS2EW2iNB+g0EibKJLBdv8I
eLovVDAfBgNVHSMEGDAWgBR7iZySlyShhEcCy3T8LvSs3DLl8zAdBgNVHREEFjAUgRJzdHBl
dGVyQHN0cGV0ZXIuaW0wggFCBgNVHSAEggE5MIIBNTCCATEGCysGAQQBgbU3AQICMIIBIDAu
BggrBgEFBQcCARYiaHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjA0BggrBgEF
BQcCARYoaHR0cDovL3d3dy5zdGFydHNzbC5jb20vaW50ZXJtZWRpYXRlLnBkZjCBtwYIKwYB
BQUHAgIwgaowFBYNU3RhcnRDb20gTHRkLjADAgEBGoGRTGltaXRlZCBMaWFiaWxpdHksIHNl
ZSBzZWN0aW9uICpMZWdhbCBMaW1pdGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENlcnRpZmlj
YXRpb24gQXV0aG9yaXR5IFBvbGljeSBhdmFpbGFibGUgYXQgaHR0cDovL3d3dy5zdGFydHNz
bC5jb20vcG9saWN5LnBkZjBjBgNVHR8EXDBaMCugKaAnhiVodHRwOi8vd3d3LnN0YXJ0c3Ns
LmNvbS9jcnR1My1jcmwuY3JsMCugKaAnhiVodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9jcnR1
My1jcmwuY3JsMIGOBggrBgEFBQcBAQSBgTB/MDkGCCsGAQUFBzABhi1odHRwOi8vb2NzcC5z
dGFydHNzbC5jb20vc3ViL2NsYXNzMy9jbGllbnQvY2EwQgYIKwYBBQUHMAKGNmh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2NlcnRzL3N1Yi5jbGFzczMuY2xpZW50LmNhLmNydDAjBgNVHRIE
HDAahhhodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS8wDQYJKoZIhvcNAQEFBQADggEBADVtbXJG
tKAr55xc/OUM546gXUybI72Bank0w739Mv+9BBNtq9rMEvCnLmSKhBi76c1mdXh6zXs8RQDo
6nR/aPabE3llF2T4z80smi9jfnl3y9dpu9TcgDoqDLZ7a2lBlW656XAAQzHjvLp2MC7/mxlg
PYH2axa+q40mAYM20GbNsAEGbWQT1IqIh0BcLLsgbaMJHbyG/57zd9JLyMX3Vry1L1fJRQr3
GeLxMV5RtxN+mBgxrwFz/cOc09COiFExlsHgekpB5O43gqsAU16MXypyoSt4MrSfKTMHIGx6
2RF/M6vqUlvhi28gk2ZUvQ/+OX5+gjcZyooEzAAn4RuOKNswggbHMIIFr6ADAgECAgIAizAN
BgkqhkiG9w0BAQUFADCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4x
KzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMT
L1N0YXJ0Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBMB4XDTEw
MTAxNDAxMzYzNFoXDTEyMTAxNDEyMDEwN1owgcAxIDAeBgNVBA0TFzI3NDU4MS05TlgwNHF4
TERiMG80NjlUMQswCQYDVQQGEwJVUzERMA8GA1UECBMIQ29sb3JhZG8xDzANBgNVBAcTBkRl
bnZlcjEsMCoGA1UECxMjU3RhcnRDb20gVHJ1c3RlZCBDZXJ0aWZpY2F0ZSBNZW1iZXIxGjAY
BgNVBAMTEVBldGVyIFNhaW50LUFuZHJlMSEwHwYJKoZIhvcNAQkBFhJzdHBldGVyQHN0cGV0
ZXIuaW0wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC4RG+euSlBPH3Bsl+DFs0o
Ri+3QiKV5xlFQzrCtsLMhQ8Khy5iFoAlxCiojIdorJs9Dt/4MgYgCiUBrd0ec12Wxc/ayZN+
39k2mPXQ8gbluKU0CotRjCYsloRqpjsExbzjbdTduVbjf+W4smT8+rg6xZzDsArct5WHVT8c
6CqGKfbo3eHvZfWdssSlkWuBynx6CZa1csJssEMypQrePrCMuV2eLv2a7NgRWpTQDkapJ5vx
ZziQjHxUjnIvbgkrOKcbaJVE/lkMRs5kRPMFclptSxXnpdLGo8b0MrqR77JsKIv/ApXUcWp2
0UHXLbmV+8eA4/aDIQCkEoQM2OAuYrLJAgMBAAGjggL7MIIC9zAJBgNVHRMEAjAAMAsGA1Ud
DwQEAwIEsDAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFLYRbaI0
H6DQSJsoksF2/wh4ui9UMB8GA1UdIwQYMBaAFHuJnJKXJKGERwLLdPwu9KzcMuXzMB0GA1Ud
EQQWMBSBEnN0cGV0ZXJAc3RwZXRlci5pbTCCAUIGA1UdIASCATkwggE1MIIBMQYLKwYBBAGB
tTcBAgIwggEgMC4GCCsGAQUFBwIBFiJodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3ku
cGRmMDQGCCsGAQUFBwIBFihodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9pbnRlcm1lZGlhdGUu
cGRmMIG3BggrBgEFBQcCAjCBqjAUFg1TdGFydENvbSBMdGQuMAMCAQEagZFMaW1pdGVkIExp
YWJpbGl0eSwgc2VlIHNlY3Rpb24gKkxlZ2FsIExpbWl0YXRpb25zKiBvZiB0aGUgU3RhcnRD
b20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgUG9saWN5IGF2YWlsYWJsZSBhdCBodHRwOi8v
d3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3kucGRmMGMGA1UdHwRcMFowK6ApoCeGJWh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2NydHUzLWNybC5jcmwwK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRz
c2wuY29tL2NydHUzLWNybC5jcmwwgY4GCCsGAQUFBwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0
dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3MzL2NsaWVudC9jYTBCBggrBgEFBQcw
AoY2aHR0cDovL3d3dy5zdGFydHNzbC5jb20vY2VydHMvc3ViLmNsYXNzMy5jbGllbnQuY2Eu
Y3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzANBgkqhkiG9w0BAQUF
AAOCAQEANW1tcka0oCvnnFz85QznjqBdTJsjvYFqeTTDvf0y/70EE22r2swS8KcuZIqEGLvp
zWZ1eHrNezxFAOjqdH9o9psTeWUXZPjPzSyaL2N+eXfL12m71NyAOioMtntraUGVbrnpcABD
MeO8unYwLv+bGWA9gfZrFr6rjSYBgzbQZs2wAQZtZBPUioiHQFwsuyBtowkdvIb/nvN30kvI
xfdWvLUvV8lFCvcZ4vExXlG3E36YGDGvAXP9w5zT0I6IUTGWweB6SkHk7jeCqwBTXoxfKnKh
K3gytJ8pMwcgbHrZEX8zq+pSW+GLbyCTZlS9D/45fn6CNxnKigTMACfhG44o2zGCA80wggPJ
AgEBMIGTMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UE
CxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRD
b20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMAkGBSsOAwIa
BQCgggIOMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDYx
NzE0NTIyM1owIwYJKoZIhvcNAQkEMRYEFD+djl48ucxioOgxYzG5fF+qc2D+MF8GCSqGSIb3
DQEJDzFSMFAwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggq
hkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBpAYJKwYBBAGCNxAEMYGWMIGT
MIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2Vj
dXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xh
c3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMIGmBgsqhkiG9w0BCRAC
CzGBlqCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNV
BAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0
Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgIAizANBgkqhkiG
9w0BAQEFAASCAQB5UQUaV52rL9Kjp9+dHTudTkzcVk0i2DeIDnzlM9lQHmnSU4J6kJr5bXOp
kPFXSPLw6GbM48WVVa8/xb0s7L12UX/WGDK71Lsjx0aKvjTwtuOSfVekRgIb/99BGwYNLtIh
PHJ9pMyMXVvL1yogik7GxTUzoHcMrg4ucosu2xKdpRBt0EQPDvFgHbGKdk3L9nGcHPpFrBXZ
8HJ0/jcnrhNXDgxMENThYWbnJnfyGIJn9oEybimC3AiWMT/TUIAjVvkSsxee5lHj5838oukI
uUR55FJHstvN++Y/WLmKoRcFcIkGA++xl8wQJNjp9CHrGMQo72tgG6zwzulV5XMHz1prAAAA
AAAA
--------------ms050701020602040503040303--


Return-Path: <derhoermi@gmx.net>
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 3AD9911E8088 for <ietf-types@ietfa.amsl.com>; Fri, 17 Jun 2011 06:21:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.407
X-Spam-Level: 
X-Spam-Status: No, score=-2.407 tagged_above=-999 required=5 tests=[AWL=0.192,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6RVVT9M5DF4U for <ietf-types@ietfa.amsl.com>; Fri, 17 Jun 2011 06:21:50 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id D095D11E8070 for <ietf-types@ietf.org>; Fri, 17 Jun 2011 06:21:49 -0700 (PDT)
Received: (qmail invoked by alias); 17 Jun 2011 13:21:47 -0000
Received: from dslb-094-222-153-106.pools.arcor-ip.net (EHLO HIVE) [94.222.153.106] by mail.gmx.net (mp056) with SMTP; 17 Jun 2011 15:21:47 +0200
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX1/S9k4KBsbSUmLhE/bA5aMVhRM8ONZ80Ygb7qw0go HVhDbI2gaSqEFM
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: stbryant@cisco.com
Date: Fri, 17 Jun 2011 15:22:01 +0200
Message-ID: <h1lmv69gdsu8s921nrr1mmvfcn65aoum3f@hive.bjoern.hoehrmann.de>
References: <4DFB534C.6010606@cisco.com>
In-Reply-To: <4DFB534C.6010606@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
Cc: draft-ietf-sidr-repos-struct@tools.ietf.org, ietf-types@ietf.org
Subject: Re: [ietf-types] Review requested for draft-ietf-sidr-repos-struct
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jun 2011 13:21:51 -0000

* Stewart Bryant wrote:
>7.1.1.  application/rpki-manifest
>
>    MIME media type name:  application
>    MIME subtype name:  rpki-manifest

This uses an outdated template, the current template is in RFC 4288.

>    Required parameters:  None
>    Optional parameters:  None
>    Encoding considerations:  binary
>    Security considerations:  Carries a RPKI Manifest
>       [I-D.ietf-sidr-rpki-manifests].

This should perhaps reference the Security Considerations of that
document then.

>    Interoperability considerations:  None
>    Published specification:  This document
>    Applications which use this media type:  Any MIME-complaint transport

This should say something more like "3D Modeling Software".

(Same comments apply to the other type.)
-- 
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: <stbryant@cisco.com>
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 7643411E8088 for <ietf-types@ietfa.amsl.com>; Fri, 17 Jun 2011 06:14:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.486
X-Spam-Level: 
X-Spam-Status: No, score=-110.486 tagged_above=-999 required=5 tests=[AWL=0.113, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VJu0-oqyca+N for <ietf-types@ietfa.amsl.com>; Fri, 17 Jun 2011 06:14:16 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 7D26511E8070 for <ietf-types@ietf.org>; Fri, 17 Jun 2011 06:14:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=1950; q=dns/txt; s=iport; t=1308316456; x=1309526056; h=message-id:date:from:reply-to:mime-version:to:cc:subject: content-transfer-encoding; bh=iwSoud91Q/Kho1v1FVIMwjDXsmut3OYgkWdhg2izZOE=; b=dDQ6c3AlDFChmznqlOiechYxP6q9Xy9xDnq++kohpuDIXdf+itwKaylP +qlp8mFjKJNGPTTwgJHmcHXqNt8rKV1FqxgwLyIhjChKEZr1ktBCrQ2q2 NkglsSjwQCSncOA/1+7DnD6w63k3JxqzrWZwL9x0THBzInM5knO6VK5tv M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AoEIAAJS+02Q/khR/2dsb2JhbABSmCaOSHepWIMPDwGafoYnBJFej34
X-IronPort-AV: E=Sophos;i="4.65,381,1304294400"; d="scan'208";a="94538042"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-1.cisco.com with ESMTP; 17 Jun 2011 13:14:09 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p5HDE9f7001803; Fri, 17 Jun 2011 13:14:09 GMT
Received: from stbryant-mac2.local (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id p5HDE8QS028227; Fri, 17 Jun 2011 14:14:09 +0100 (BST)
Message-ID: <4DFB534C.6010606@cisco.com>
Date: Fri, 17 Jun 2011 14:14:52 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: ietf-types@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-sidr-repos-struct@tools.ietf.org
Subject: [ietf-types] Review requested for draft-ietf-sidr-repos-struct
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jun 2011 13:14:17 -0000

draft-ietf-sidr-repos-struct

https://datatracker.ietf.org/doc/draft-ietf-sidr-repos-struct/

Makes the following types request.

Review comments by 1 July would be appreciated.

Many thanks

- Stewart



7.1.1.  application/rpki-manifest

    MIME media type name:  application
    MIME subtype name:  rpki-manifest
    Required parameters:  None
    Optional parameters:  None
    Encoding considerations:  binary
    Security considerations:  Carries a RPKI Manifest
       [I-D.ietf-sidr-rpki-manifests].
    Interoperability considerations:  None
    Published specification:  This document
    Applications which use this media type:  Any MIME-complaint transport
    Additional information:
       Magic number(s):  None
       File extension(s):  .mft
       Macintosh File Type Code(s):
    Person&  email address to contact for further information:  Geoff
       Huston<gih@apnic.net>
    Intended usage:  COMMON
    Author/Change controller:  Geoff Huston<gih@apnic.net>

7.1.2.  application/rpki-roa

    MIME media type name:  application>
    MIME subtype name:  rpki-roa
    Required parameters:  None
    Optional parameters:  None
    Encoding considerations:  binary
    Security considerations:  Carries a RPKI ROA
       [I-D.ietf-sidr-roa-format]
    Interoperability considerations:  None

Huston, et al.          Expires December 10, 2011              [Page 12]
Internet-Draft        ResCert Repository Structure             June 2011

    Published specification:  This document
    Applications which use this media type:  Any MIME-complaint transport
    Additional information:
       Magic number(s):  None
       File extension(s):  .roa
       Macintosh File Type Code(s):
    Person&  email address to contact for further information:  Geoff
       Huston<gih@apnic.net>
    Intended usage:  COMMON
    Author/Change controller:  Geoff Huston<gih@apnic.net>



Return-Path: <mdirector@iptc.org>
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 5F37F11E80CB for <ietf-types@ietfa.amsl.com>; Fri, 17 Jun 2011 05:06:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.187
X-Spam-Level: 
X-Spam-Status: No, score=-0.187 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RuwB1TSNtuv8 for <ietf-types@ietfa.amsl.com>; Fri, 17 Jun 2011 05:06:15 -0700 (PDT)
Received: from pechora5.dc.icann.org (pechora5.icann.org [IPv6:2620:0:2830:201::1:71]) by ietfa.amsl.com (Postfix) with ESMTP id F2B3711E808B for <ietf-types@ietf.org>; Fri, 17 Jun 2011 05:06:13 -0700 (PDT)
Received: from mail.iptc.org (srvhost34.serverhosting.apa.net [194.232.153.97]) by pechora5.dc.icann.org (8.13.8/8.13.8) with ESMTP id p5HC5qKH026540 for <ietf-types@iana.org>; Fri, 17 Jun 2011 05:06:12 -0700
Received: from NITFIX7 (unknown [83.64.11.70]) (Authenticated sender: mdirector) by mail.iptc.org (Postfix) with ESMTP id E158C1EFAB8 for <ietf-types@iana.org>; Fri, 17 Jun 2011 13:39:10 +0200 (CEST)
From: "Michael Steidl \(IPTC\)" <mdirector@iptc.org>
To: <ietf-types@iana.org>
Date: Fri, 17 Jun 2011 13:39:07 +0200
Organization: IPTC
Message-ID: <008201cc2ce3$2abfc130$803f4390$@org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0083_01CC2CF3.EE489130"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acws4yqgnBzGHAtTTCCxUIRnRSF7GQ==
Content-Language: de-at
X-Greylist: Delayed for 00:26:39 by milter-greylist-4.0 (pechora5.dc.icann.org [192.0.46.71]); Fri, 17 Jun 2011 05:06:13 -0700 (PDT)
Subject: [ietf-types] Updating registration of application/vnd.iptc.g2.planningitem+xml
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jun 2011 12:06:16 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0083_01CC2CF3.EE489130
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Upon request a Windows Clipboard Flavor Name and a Macintosh Uniform =
Type Identifier have been added.

=20

This is the updated application:

=20

Media Type Name: application

=20

Subtype name: vnd.iptc.g2.planningitem+xml

=20

Required parameters: none

=20

Optional parameters: charset

identical to the charset parameter on application/xml as described

in RFC 3023 [RFC3023] section 3.2

=20

Encoding considerations: Identical to those of application/xml as

described in RFC 3023, section 3.2

=20

Security considerations: In regards to general XML Security issues,

identical to those of "application/xml" as described in RFC3023,

section 10. Beyond these general XML Security issues, the media

type does not contain active or executable content. The information

contained in the media type does not require privacy or integrity

services, however the media type does support the use of the XML

syntax and processing rules for creating and representing digital

signatures as described by RFC3275.

=20

Interoperability considerations:

=20

Published specification:

=20

for NewsML-G2 version 2.7 specifications and EventsML-G2 version 1.6 =
specifications

=20

http://www.iptc.org/std/NAR/1.8/specification/NAR_1.8-spec-PlanningItem-C=
ore.xsd

=20

Or

=20

http://www.iptc.org/std/NAR/1.8/specification/NAR_1.8-spec-PlanningItem-P=
ower.xsd

=20

Applications which use this media type: none

=20

Additional information:

=20

Magic number(s): none

=20

File extension(s): .xml

=20

Macintosh File Type Code(s): Identical to those of

"application/xml" as described in RFC3023, "TEXT"

=20

Windows Clipboard Flavor Name: "IPTC PlanningItem XML"

=20

Macintosh Uniform Type Identifier: org.iptc.planningitem conforms to =
public.xml

=20

Object Identifier(s) or OID(s):

It must be possible to positively identify an Item as it moves

through the news workflow, and is transferred from place to place

and from system to system. An Item therefore gets a globally

unique identifier (guid), which is a persistent, universally unique

identifier, and a version which is incremented when the content of

the Item is updated. The first version is numbered 1: if the version

is not explicitly set, this value must be assumed by the recipient of

the Item. The guid is required to be in the form of a IRI. Any IRI

capable of acting as a globally unique identifier is accepted; the

IPTC provides a standard for this purpose in the form of an IETF RFC

[RFC-3085].

=20

Intended usage:

=20

A Planning Item conveys information for the editorial staff of

media companies about the planned coverage of events or topics=20

by a news provider.

Typically a Planning Item holds details like the headline,

keywords and the time of release for a set of planned News Items,

Concept Items or Package items. Further a Planning Item

may provide a list of already delivered Items.

=20

Other Information/General Comment: none

=20

Person to contact for further information:

Name: Michael Steidl

E-mail: mdirector@iptc.org

=20

Author/Change controller:

Name: Michael Steidl

E-mail: mdirector@iptc.org

=20

=20

=20

Michael Steidl

Managing Director of the IPTC [mdirector@iptc.org]

International Press Telecommunications Council=20
Web:  <http://www.iptc.org/> www.iptc.org - on Twitter  =
<http://www.twitter.com/IPTC> @IPTC

Business office address:=20

20 Garrick Street, London WC2E 9BT, United Kingdom

Registered in England, company no 101096

=20


------=_NextPart_000_0083_01CC2CF3.EE489130
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 12 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.E-MailFormatvorlage17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DDE-AT link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>U=
pon request a Windows Clipboard Flavor Name and a Macintosh Uniform Type =
Identifier have been added.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><=
o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>T=
his is the updated application:<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><=
o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>M=
edia Type Name: application<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><=
o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>S=
ubtype name: vnd.iptc.g2.planningitem+xml<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><=
o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>R=
equired parameters: none<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><=
o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>O=
ptional parameters: charset<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>i=
dentical to the charset parameter on application/xml as =
described<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>i=
n RFC 3023 [RFC3023] section 3.2<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><=
o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>E=
ncoding considerations: Identical to those of application/xml =
as<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>d=
escribed in RFC 3023, section 3.2<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><=
o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>S=
ecurity considerations: In regards to general XML Security =
issues,<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>i=
dentical to those of &quot;application/xml&quot; as described in =
RFC3023,<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>s=
ection 10. Beyond these general XML Security issues, the =
media<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>t=
ype does not contain active or executable content. The =
information<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>c=
ontained in the media type does not require privacy or =
integrity<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>s=
ervices, however the media type does support the use of the =
XML<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>s=
yntax and processing rules for creating and representing =
digital<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>s=
ignatures as described by RFC3275.<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><=
o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>I=
nteroperability considerations:<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><=
o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>P=
ublished specification:<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><=
o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>f=
or NewsML-G2 version 2.7 specifications and EventsML-G2 version 1.6 =
specifications<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><=
o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>h=
ttp://www.iptc.org/std/NAR/1.8/specification/NAR_1.8-spec-PlanningItem-Co=
re.xsd<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><=
o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>O=
r<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><=
o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>h=
ttp://www.iptc.org/std/NAR/1.8/specification/NAR_1.8-spec-PlanningItem-Po=
wer.xsd<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><=
o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>A=
pplications which use this media type: none<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><=
o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>A=
dditional information:<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><=
o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>M=
agic number(s): none<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><=
o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>F=
ile extension(s): .xml<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><=
o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>M=
acintosh File Type Code(s): Identical to those =
of<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>&=
quot;application/xml&quot; as described in RFC3023, =
&quot;TEXT&quot;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><=
o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>W=
indows Clipboard Flavor Name: &quot;IPTC PlanningItem =
XML&quot;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><=
o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>M=
acintosh Uniform Type Identifier: org.iptc.planningitem conforms to =
public.xml<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><=
o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>O=
bject Identifier(s) or OID(s):<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>I=
t must be possible to positively identify an Item as it =
moves<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>t=
hrough the news workflow, and is transferred from place to =
place<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>a=
nd from system to system. An Item therefore gets a =
globally<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>u=
nique identifier (guid), which is a persistent, universally =
unique<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>i=
dentifier, and a version which is incremented when the content =
of<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>t=
he Item is updated. The first version is numbered 1: if the =
version<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>i=
s not explicitly set, this value must be assumed by the recipient =
of<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>t=
he Item. The guid is required to be in the form of a IRI. Any =
IRI<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>c=
apable of acting as a globally unique identifier is accepted; =
the<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>I=
PTC provides a standard for this purpose in the form of an IETF =
RFC<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>[=
RFC-3085].<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><=
o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>I=
ntended usage:<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><=
o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>A=
 Planning Item conveys information for the editorial staff =
of<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>m=
edia companies about the planned coverage of events or topics =
<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>b=
y a news provider.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>T=
ypically a Planning Item holds details like the =
headline,<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>k=
eywords and the time of release for a set of planned News =
Items,<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>C=
oncept Items or Package items. Further a Planning =
Item<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>m=
ay provide a list of already delivered Items.<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><=
o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>O=
ther Information/General Comment: none<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><=
o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>P=
erson to contact for further information:<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>N=
ame: Michael Steidl<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>E=
-mail: mdirector@iptc.org<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><=
o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>A=
uthor/Change controller:<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>N=
ame: Michael Steidl<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>E=
-mail: mdirector@iptc.org<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><=
o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><b><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'=
>Michael Steidl<o:p></o:p></span></b></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'=
>Managing Director of the IPTC =
[mdirector@iptc.org]<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'=
>International Press Telecommunications Council <br>Web: </span><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'=
><a href=3D"http://www.iptc.org/"><span lang=3DEN-GB =
style=3D'color:#1F497D'>www.iptc.org</span></a></span><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'=
> <span lang=3DEN-GB>- on Twitter </span></span><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'=
><a href=3D"http://www.twitter.com/IPTC"><span lang=3DEN-GB =
style=3D'color:#1F497D'>@IPTC</span></a></span><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'=
><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'=
>Business office address: <o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'=
>20 Garrick Street, London WC2E 9BT, United =
Kingdom<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'=
>Registered in England, company no 101096<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
lang=3DEN-GB><o:p>&nbsp;</o:p></span></p></div></body></html>
------=_NextPart_000_0083_01CC2CF3.EE489130--




Return-Path: <julian.reschke@gmx.de>
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 CF92811E80D2 for <ietf-types@ietfa.amsl.com>; Thu, 16 Jun 2011 06:23:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.438
X-Spam-Level: 
X-Spam-Status: No, score=-103.438 tagged_above=-999 required=5 tests=[AWL=-0.839, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q+jrBY4N+AHq for <ietf-types@ietfa.amsl.com>; Thu, 16 Jun 2011 06:23:58 -0700 (PDT)
Received: from pechora1.lax.icann.org (pechora1.icann.org [208.77.188.36]) by ietfa.amsl.com (Postfix) with ESMTP id 3C29B11E8071 for <ietf-types@ietf.org>; Thu, 16 Jun 2011 06:23:57 -0700 (PDT)
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 p5GDNLTw004898 for <ietf-types@iana.org>; Thu, 16 Jun 2011 06:23:42 -0700
Received: (qmail invoked by alias); 16 Jun 2011 13:23:19 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp008) with SMTP; 16 Jun 2011 15:23:19 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+5b044kve5u9JXcl/QHSojFJkBwNnAmLE6ZVnVm9 ZGWEToWZQAwpzo
Message-ID: <4DFA03BC.4000002@gmx.de>
Date: Thu, 16 Jun 2011 15:23:08 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: Bjoern Hoehrmann <derhoermi@gmx.net>
References: <surev6hio3morol2u6431pf6m413ntcl4g@hive.bjoern.hoehrmann.de>
In-Reply-To: <surev6hio3morol2u6431pf6m413ntcl4g@hive.bjoern.hoehrmann.de>
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.0 (pechora1.lax.icann.org [208.77.188.36]); Thu, 16 Jun 2011 06:23:42 -0700 (PDT)
Cc: ietf-types@iana.org
Subject: Re: [ietf-types] Comments on draft-melnikov-mime-default-charset-00.txt
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jun 2011 13:23:59 -0000

On 2011-06-14 17:18, Bjoern Hoehrmann wrote:
> Hi,
>
>    On http://www.ietf.org/id/draft-melnikov-mime-default-charset-00.txt
>
> The first paragraph is horrible. It fails to properly separate the RFC
> 2046 context from the RFC 2616 context, and instead makes encoding de-
> tection a property of the media type independently of context. That is

I think mentioning both here makes sense as RFC 2616 overrides the 
default set in 2046 (when used over HTTP).

> not how media types are used, it is common for instance to use them in
> contexts where a character encoding is not used at all, for instance,
> in a XHTML document with
>
>    <style type='text/css'>
>      ...
>    </style>
> ...

That's a good point. The same applies to <script> in (X)HTML, and AFAIR 
<atom:content>.

We should describe this use case somewhere, and point out that in cases 
like these, the charset parameter doesn't make sense.

Does this belong into *this* document, though?

 > ...

Best regards, Julian


Return-Path: <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
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 7647611E81C7 for <ietf-types@ietfa.amsl.com>; Wed, 15 Jun 2011 15:41:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, FROM_LOCAL_NOVOWEL=0.5, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9R70CWFHXmjC for <ietf-types@ietfa.amsl.com>; Wed, 15 Jun 2011 15:41:31 -0700 (PDT)
Received: from pechora8.dc.icann.org (pechora8.icann.org [192.0.46.74]) by ietfa.amsl.com (Postfix) with ESMTP id AD61611E81C8 for <ietf-types@ietf.org>; Wed, 15 Jun 2011 15:41:30 -0700 (PDT)
Received: from mail-pv0-f169.google.com (mail-pv0-f169.google.com [74.125.83.169]) by pechora8.dc.icann.org (8.13.8/8.13.8) with ESMTP id p5FMeq1f017088 for <ietf-types@iana.org>; Wed, 15 Jun 2011 18:41:13 -0400
Received: by pvc12 with SMTP id 12so745569pvc.28 for <ietf-types@iana.org>; Wed, 15 Jun 2011 15:40:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=vKv8ONosEQ0hY31QN5dfgH05aOEAMot7A5xwHNLdFZo=; b=LptD8PQGdvfxMkhkM/HyOAEaOOP1k66Gl3IjU7ZcpljNNgXuwf0VV/dv7Uyaw5xj04 eoq7BhEIQkLI1mMhYmy8RY4tl9qmYqFxdDPqM6unt0vMYXXuFxbGKVQqZ6xU1u8w69kl ixphzJEzIrIP9UF0DmVID5kUp85P3y3Zkc1Jc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=M2AKJrAUOtyg9yh3wYvDRdLbxW6pGuDuQuq9qL5d8jpRCw54kGgRdWOj6w/wRB1whj VilelMvw/3YXBZKpyMtYEhy/3jXTae7S258TjUP1K6gHlbQL1ykKeSoZaQngfc/vJHLB MwTjZCEii0xKSPmEyDW6WYsZ7MYa/ceV87zaU=
Received: by 10.142.242.12 with SMTP id p12mr39893wfh.346.1308177652100; Wed, 15 Jun 2011 15:40:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.143.34.19 with HTTP; Wed, 15 Jun 2011 15:40:32 -0700 (PDT)
In-Reply-To: <l19iv6h399raafe50rkntrts2og71lfmoe@hive.bjoern.hoehrmann.de>
References: <surev6hio3morol2u6431pf6m413ntcl4g@hive.bjoern.hoehrmann.de> <BANLkTi=__wEZpOCBg24EzF=AhXEw7sJOJg@mail.gmail.com> <l19iv6h399raafe50rkntrts2og71lfmoe@hive.bjoern.hoehrmann.de>
From: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
Date: Thu, 16 Jun 2011 00:40:32 +0200
Message-ID: <BANLkTikTBA6dQ99wXD+dKTwTchGKnOOaew@mail.gmail.com>
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.2.3 (pechora8.dc.icann.org [192.0.46.74]); Wed, 15 Jun 2011 18:41:13 -0400 (EDT)
Cc: ietf-types@iana.org
Subject: Re: [ietf-types] Comments on draft-melnikov-mime-default-charset-00.txt
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jun 2011 22:41:31 -0000

On 15 June 2011 23:44, Bjoern Hoehrmann wrote:

> My point was that the context where the media type label
> and the content occur in is important. RFC 2616 did
> not "change the default", it spelled out rules for HTTP
> messages, which is a different context than what
> RFC 2046 was about.

IBTD, RFC 2616 has a reference to RFC 2046, and I think
that should be a "normative reference" in a modern RFC.

And unlike the old "HTML i18n" RFC the HTTP RFC already
knew BCP 18 (listed in the references).  In other words,
it ignored MIME *and* the IETF charset policy for its
own purposes (= compatibilty with existing software at
the time of its publication).

[...]
> Right now the model is that higher level information
> overrides lower-level information, so the server
> administrator wins over the content maintainer. That's
> a bad model as information about encodings, media
> types, is not stored in typical file systems, and
> cannot be conveyed through some protocols, so explicit
> out of band configuration is required, but that's what
> we have got at the moment. That's not likely to change
> for old protocols.

Yes, that's what I meant.  The most specific info should
win, not the most general (server) info.  If exactly the
same resource is also available by FTP it could be valid
for FTP, and invalid for HTTP.  That is not only "bad",
it is plain wrong:  Hopefully HTTPbis fixes this, or at
least documents the fact of its own "unusabilty" for many
users unable to configure Web servers of a third party,
i.e., their Web hoster.

> I am saying that the draft maybe should specify "don't
> know" as that reflects reality fairly well.

Well, the MIME default is a last resort for "dunno", one
step before you are forced to sniff and guess.  Charset
sniffing does not work well for UTF-8 vs. ASCII-based
SBCS, if non-ASCII bytes occur too late in text/plain.

> I do understand that people think, and quite rightly
> so, that you "need" to know the encoding, but that does
> not mean the protocols must specify an answer even if
> that does not correspond to reality.

And that is the problem that has to be fixed for HTTPbis.
If the solution is "don't talk about it, use a normative
reference to MIME, and decree that the old ISO-8859-1
default turned out to be a bad idea" I'd like it better
than what we have now in RFC 2616.

Sadly this business also affects AUTH DIGEST, and it was
one of several reasons why SASL DIGEST was obsoleted.

The HTTP DIGEST RFC inherited the obscure HTTP default
charset.  From there this beast spread out, AUTH DIGEST
(ignoring the now potentially obsolete SASL DIGEST) is
used in other protocols, I vaguely recall "SIPPING".

> RFC 3023 specifies that text/xml "is" US-ASCII even
> though RFC 2616 says it "is" ISO-8859-1, that is
> probably what you mean here.

Yes, when a text/xml resource clearly states that it is
UTF-8 it shouldn't be rejected as invalid by validators
only because a server or browser transmitted the file
as text/plain.

This mess was caused by not strictly following MIME in
other RFCs.  Nothing is wrong with MIME -- other RFCs
trying to outsmart MIME failed miserably, and caused
unnecessary pains for many authors trying to create
"valid" documents.

-Frank


Return-Path: <derhoermi@gmx.net>
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 8431311E81AF for <ietf-types@ietfa.amsl.com>; Wed, 15 Jun 2011 14:44:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.369
X-Spam-Level: 
X-Spam-Status: No, score=-2.369 tagged_above=-999 required=5 tests=[AWL=0.230,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vUYQ2IFZfdeU for <ietf-types@ietfa.amsl.com>; Wed, 15 Jun 2011 14:44:46 -0700 (PDT)
Received: from pechora1.lax.icann.org (pechora1.icann.org [208.77.188.36]) by ietfa.amsl.com (Postfix) with ESMTP id 69C2C11E81AE for <ietf-types@ietf.org>; Wed, 15 Jun 2011 14:44:46 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by pechora1.lax.icann.org (8.13.8/8.13.8) with SMTP id p5FLiAQv019935 for <ietf-types@iana.org>; Wed, 15 Jun 2011 14:44:30 -0700
Received: (qmail invoked by alias); 15 Jun 2011 21:44:07 -0000
Received: from dslb-094-222-153-106.pools.arcor-ip.net (EHLO HIVE) [94.222.153.106] by mail.gmx.net (mp063) with SMTP; 15 Jun 2011 23:44:07 +0200
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX1/WVUp18tTWnQCs4ZkCN4M5uFtBChSXWJ+F3kNmGM W2lTYSrIc4E7M/
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
Date: Wed, 15 Jun 2011 23:44:19 +0200
Message-ID: <l19iv6h399raafe50rkntrts2og71lfmoe@hive.bjoern.hoehrmann.de>
References: <surev6hio3morol2u6431pf6m413ntcl4g@hive.bjoern.hoehrmann.de> <BANLkTi=__wEZpOCBg24EzF=AhXEw7sJOJg@mail.gmail.com>
In-Reply-To: <BANLkTi=__wEZpOCBg24EzF=AhXEw7sJOJg@mail.gmail.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 [208.77.188.36]); Wed, 15 Jun 2011 14:44:31 -0700 (PDT)
Cc: ietf-types@iana.org
Subject: Re: [ietf-types] Comments on draft-melnikov-mime-default-charset-00.txt
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jun 2011 21:44:47 -0000

* Frank Ellermann wrote:
>Sorry, you lost me here, inline CSS as in your example uses
>the document charset, doesn't it?  You can certainly have
>non-ASCII in CSS comments or in, say, CSS "content" values.
>
>For external CSS files the charset can be specified inline
>with, e.g., @charset "us-ascii"; (begin of file).  Please
>correct me if I'm wrong, my CSS knowledge is very limited.
>
>I'd be surprised if the charset for inline CSS could be
>different from the document charset -- if that's what you
>are talking about it's IMO obvious, but maybe the new I-D
>should mention the issue of "an immutable per document
>default for inline text/css or text/javascript".

Your understanding above is correct. My point was that the context where
the media type label and the content occur in is important. RFC 2616 did
not "change the default", it spelled out rules for HTTP messages, which
is a different context than what RFC 2046 was about.

>Sounds good.  Hopefully inline definitions maintained by
>the authors of resources can overrule whatever server
>admins configure, unlike server admins the authors should
>know which charset they use.

(I am not sure what you are saying here. Right now the model is that
higher level information overrides lower-level information, so the
server administrator wins over the content maintainer. That's a bad
model as information about encodings, media types, is not stored in
typical file systems, and cannot be conveyed through some protocols,
so explicit out of band configuration is required, but that's what we
have got at the moment. That's not likely to change for old protocols.)

>> for text/plain, and for many other subtypes, if there is
>> no charset parameter, then you don't know what encoding
>> it is in.
>
>Of course you know this, because MIME specifies US-ASCII.

I am saying that the draft maybe should specify "don't know" as that
reflects reality fairly well. I do understand that people think, and
quite rightly so, that you "need" to know the encoding, but that does
not mean the protocols must specify an answer even if that does not
correspond to reality.

>Other text/* types I'm aware of (text/xml, text/html,
>text/css) permit this to some degree -- but there was
>something special with text/xml, I forgot the details;
>was it perhaps "text/xml MUST be US-ASCII"?

RFC 3023 specifies that text/xml "is" US-ASCII even though RFC 2616
says it "is" ISO-8859-1, that is probably what you mean here.
-- 
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: <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
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 7FEF411E8192 for <ietf-types@ietfa.amsl.com>; Wed, 15 Jun 2011 14:28:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, FROM_LOCAL_NOVOWEL=0.5, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tw84d1kUHrg3 for <ietf-types@ietfa.amsl.com>; Wed, 15 Jun 2011 14:28:49 -0700 (PDT)
Received: from pechora3.lax.icann.org (pechora3.icann.org [208.77.188.38]) by ietfa.amsl.com (Postfix) with ESMTP id EF1CE11E8189 for <ietf-types@ietf.org>; Wed, 15 Jun 2011 14:28:42 -0700 (PDT)
Received: from mail-pz0-f41.google.com (mail-pz0-f41.google.com [209.85.210.41]) by pechora3.lax.icann.org (8.13.8/8.13.8) with ESMTP id p5FLS7rQ029349 for <ietf-types@iana.org>; Wed, 15 Jun 2011 14:28:27 -0700
Received: by pzk4 with SMTP id 4so668973pzk.28 for <ietf-types@iana.org>; Wed, 15 Jun 2011 14:28:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=OWIEcW4n8Z45ukk4nzXQy/xEjDYD7TGw9ujnHbjVn3I=; b=proxKVxWP2MNXAT88B6S5uYbuLwZCErVMXD5Zunp+1vBKx6QDcM7+jSQxteXdZr4VB vtj732y16hOmJhba1bRefIFflr5re6TgJPw7TMNMA36d2bUU5vCqnYP6Tv+86230lOyH L1/xuIRgITgB0DzxaJTjSoGmFCrh5u3AH/WWU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=XpZpO0KLMccD5vqj7O15EKFWaE191K9otwyejJR+oW0OAk6kMmx1q3qJT6Ix/TXh/n WXhrTxuoro4t+JotD/fxEuPl+DUmVk8InGiEUVWjGp5RpjvTijtgS8tkAj5WiT6bAqpm 1E9FJhkVJMhYSekWiCKGL+HECXXqflSWN2BTM=
Received: by 10.142.161.19 with SMTP id j19mr44017wfe.175.1308173287140; Wed, 15 Jun 2011 14:28:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.143.34.19 with HTTP; Wed, 15 Jun 2011 14:27:47 -0700 (PDT)
In-Reply-To: <surev6hio3morol2u6431pf6m413ntcl4g@hive.bjoern.hoehrmann.de>
References: <surev6hio3morol2u6431pf6m413ntcl4g@hive.bjoern.hoehrmann.de>
From: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
Date: Wed, 15 Jun 2011 23:27:47 +0200
Message-ID: <BANLkTi=__wEZpOCBg24EzF=AhXEw7sJOJg@mail.gmail.com>
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora3.lax.icann.org [208.77.188.38]); Wed, 15 Jun 2011 14:28:27 -0700 (PDT)
Cc: ietf-types@iana.org
Subject: Re: [ietf-types] Comments on draft-melnikov-mime-default-charset-00.txt
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jun 2011 21:28:49 -0000

On 14 June 2011 17:18, Bjoern Hoehrmann wrote:

> it is common for instance to use them in contexts where a
> character encoding is not used at all, for instance, in a
> XHTML document with

> =A0<style type=3D'text/css'>
> =A0 =A0...
> =A0</style>

> there is no value used for the absent charset parameter,
> it's a notion that does not make sense in the context.

Sorry, you lost me here, inline CSS as in your example uses
the document charset, doesn't it?  You can certainly have
non-ASCII in CSS comments or in, say, CSS "content" values.

For external CSS files the charset can be specified inline
with, e.g., @charset "us-ascii"; (begin of file).  Please
correct me if I'm wrong, my CSS knowledge is very limited.

I'd be surprised if the charset for inline CSS could be
different from the document charset -- if that's what you
are talking about it's IMO obvious, but maybe the new I-D
should mention the issue of "an immutable per document
default for inline text/css or text/javascript".

> a protocol similar to HTTP where all text/* is transported
> UTF-16 encoded which would result in a similar situation.

Now I'm confused, the HTTP default is ISO-8859-1, and that
is precisely what has to be fixed a.s.a.p.  As far as I'm
concerned US-ASCII also for HTTP is a solution; the HTML5
proposal "interpret ISO-8859-1 as windows-1252" is an odd
hack, but better than nothing; and more radical "let's just
say UTF-8 and be done with it" ideas didn't make it on the
HTTPbis list three years ago.

Are you talking about a hypothetical protocol with its own
UTF-16 default for text/*?  I'm not aware of any protocol
violating MIME for its purposes, only HTTP has this issue,
and the draft apparently tries to fix this.

> The default of US-ASCII is for the text/plain type.

No, already answered by Julian.  As you said RFC 2046 is
not a new RFC, and it should be updated to use the new
ABNF STD when the message format and SMTP RFCs are finally
full Internet standards (insert "errata exist" blurb here).

But just because the MIME RFC is old doesn't mean that it
is wrong, a compliment I would not extend to HTTP.  Maybe
the draft should get an i18n section as mandated by the
IETF charset policy, and explain why UTF-8 is *not* the
default for historical reasons (and practical reasons
wrt to old mail software not "yet" supporting 8BITMIME).

> "This memo changes RFC 2046 by defining and clarifying
>  rules how to determine the character encoding of
>  resources labeled with a text subtype."

Sounds good.  Hopefully inline definitions maintained by
the authors of resources can overrule whatever server
admins configure, unlike server admins the authors should
know which charset they use.

> for text/plain, and for many other subtypes, if there is
> no charset parameter, then you don't know what encoding
> it is in.

Of course you know this, because MIME specifies US-ASCII.

It could end up as UNKNOWN-8BIT (registered by IANA) if
the US-ASCII theory fails miserably, but that is another
story.  The text/plain case is a special case, because
there is no standard way to note the document charset
within the document -- or rather, I'm not aware of any
standard apart from Unicode "BOM" signatures, or the old
and forgotten ISO charset escape-sequences.

Other text/* types I'm aware of (text/xml, text/html,
text/css) permit this to some degree -- but there was
something special with text/xml, I forgot the details;
was it perhaps "text/xml MUST be US-ASCII"?

-Frank


Return-Path: <julian.reschke@gmx.de>
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 D5DDF11E8143 for <ietf-types@ietfa.amsl.com>; Tue, 14 Jun 2011 15:42:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NIgBEBKyV2zk for <ietf-types@ietfa.amsl.com>; Tue, 14 Jun 2011 15:42:31 -0700 (PDT)
Received: from pechora4.lax.icann.org (pechora4.icann.org [IPv6:2620:0:2d0:1::39]) by ietfa.amsl.com (Postfix) with ESMTP id 928A611E811E for <ietf-types@ietf.org>; Tue, 14 Jun 2011 15:42:27 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by pechora4.lax.icann.org (8.13.8/8.13.8) with SMTP id p5EMg5qT020729 for <ietf-types@iana.org>; Tue, 14 Jun 2011 15:42:25 -0700
Received: (qmail invoked by alias); 14 Jun 2011 22:15:24 -0000
Received: from xdsl-87-78-102-6.netcologne.de (EHLO [192.168.1.207]) [87.78.102.6] by mail.gmx.net (mp006) with SMTP; 15 Jun 2011 00:15:24 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19269gei9B28zYrWoCHI7t5dcFBQHWBJcRzDlMgY1 pL5g6dMLoXtwhy
Message-ID: <4DF7DD7C.80805@gmx.de>
Date: Wed, 15 Jun 2011 00:15:24 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: Bjoern Hoehrmann <derhoermi@gmx.net>
References: <surev6hio3morol2u6431pf6m413ntcl4g@hive.bjoern.hoehrmann.de> <4DF7D9F9.1020402@gmx.de> <qrmfv61ie0ifl52tb5v3osm7e366j6bq9p@hive.bjoern.hoehrmann.de>
In-Reply-To: <qrmfv61ie0ifl52tb5v3osm7e366j6bq9p@hive.bjoern.hoehrmann.de>
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.0 (pechora4.lax.icann.org [208.77.188.39]); Tue, 14 Jun 2011 15:42:26 -0700 (PDT)
Cc: ietf-types@iana.org
Subject: Re: [ietf-types] Comments on draft-melnikov-mime-default-charset-00.txt
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jun 2011 22:42:32 -0000

On 2011-06-15 00:13, Bjoern Hoehrmann wrote:
> * Julian Reschke wrote:
>> On 2011-06-14 17:18, Bjoern Hoehrmann wrote:
>>> ...
>>> There is also confusion about what RFC 2046 specifies. The default of
>>> US-ASCII is for the text/plain type. While there are suggestions that it
>>> ...
>>
>> No, it *really* applies to text/*.
>>
>> See
>> <http://greenbytes.de/tech/webdav/rfc2046.html#rfc.section.4.1.2.p.18>
>> -- that's in the section 4.1.2 (Charset Parameter), not in 4.1.3 (Plain
>> Subtype).
>
> It's easy to get caught up on archaeological details like this, here I
> might argue that this is for the Content-Type header in "Internet mail",
> but as I noted, I do not think it's valuable to overanalyze what some
> specification may have meant to specify 15 years ago. As I understand
> it, the idea of the draft is come up with something coherent to replace
> what's in there. I would prefer to keep the draft and the discussion as
> close as possible to "This whole charset, content-type, mail vs http,
> stuff sucks, but we are fixing this now saying X".

I'm not disagreeing.

On the other hand, it's necessary that we agree on what needs to be 
fixed; and this certainly is something that does not to be fixed...

Best regards, Julian


Return-Path: <derhoermi@gmx.net>
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 019CE11E8144 for <ietf-types@ietfa.amsl.com>; Tue, 14 Jun 2011 15:41:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.312
X-Spam-Level: 
X-Spam-Status: No, score=-2.312 tagged_above=-999 required=5 tests=[AWL=0.288,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9rJaCrIReZsP for <ietf-types@ietfa.amsl.com>; Tue, 14 Jun 2011 15:41:07 -0700 (PDT)
Received: from pechora8.dc.icann.org (pechora8.icann.org [192.0.46.74]) by ietfa.amsl.com (Postfix) with ESMTP id CE87711E8143 for <ietf-types@ietf.org>; Tue, 14 Jun 2011 15:41:06 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by pechora8.dc.icann.org (8.13.8/8.13.8) with SMTP id p5EMeTmm020113 for <ietf-types@iana.org>; Tue, 14 Jun 2011 18:40:49 -0400
Received: (qmail invoked by alias); 14 Jun 2011 22:13:46 -0000
Received: from dslb-094-222-153-106.pools.arcor-ip.net (EHLO HIVE) [94.222.153.106] by mail.gmx.net (mp026) with SMTP; 15 Jun 2011 00:13:46 +0200
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX19U7z9AQZNUw1ZCp2GXP1mauo3Wu8resQOYWngoW4 zPI1qkSqhgtrVx
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Julian Reschke <julian.reschke@gmx.de>
Date: Wed, 15 Jun 2011 00:13:58 +0200
Message-ID: <qrmfv61ie0ifl52tb5v3osm7e366j6bq9p@hive.bjoern.hoehrmann.de>
References: <surev6hio3morol2u6431pf6m413ntcl4g@hive.bjoern.hoehrmann.de> <4DF7D9F9.1020402@gmx.de>
In-Reply-To: <4DF7D9F9.1020402@gmx.de>
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: Delayed for 00:26:40 by milter-greylist-4.2.3 (pechora8.dc.icann.org [192.0.46.74]); Tue, 14 Jun 2011 18:40:50 -0400 (EDT)
Cc: ietf-types@iana.org
Subject: Re: [ietf-types] Comments on draft-melnikov-mime-default-charset-00.txt
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jun 2011 22:41:08 -0000

* Julian Reschke wrote:
>On 2011-06-14 17:18, Bjoern Hoehrmann wrote:
>> ...
>> There is also confusion about what RFC 2046 specifies. The default of
>> US-ASCII is for the text/plain type. While there are suggestions that it
>> ...
>
>No, it *really* applies to text/*.
>
>See 
><http://greenbytes.de/tech/webdav/rfc2046.html#rfc.section.4.1.2.p.18> 
>-- that's in the section 4.1.2 (Charset Parameter), not in 4.1.3 (Plain 
>Subtype).

It's easy to get caught up on archaeological details like this, here I
might argue that this is for the Content-Type header in "Internet mail",
but as I noted, I do not think it's valuable to overanalyze what some
specification may have meant to specify 15 years ago. As I understand
it, the idea of the draft is come up with something coherent to replace
what's in there. I would prefer to keep the draft and the discussion as
close as possible to "This whole charset, content-type, mail vs http,
stuff sucks, but we are fixing this now saying X".
-- 
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: <julian.reschke@gmx.de>
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 D266F11E8086 for <ietf-types@ietfa.amsl.com>; Tue, 14 Jun 2011 15:01:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n4ntBCucNE-8 for <ietf-types@ietfa.amsl.com>; Tue, 14 Jun 2011 15:01:03 -0700 (PDT)
Received: from pechora8.dc.icann.org (pechora8.icann.org [192.0.46.74]) by ietfa.amsl.com (Postfix) with ESMTP id B36B611E8078 for <ietf-types@ietf.org>; Tue, 14 Jun 2011 15:01:03 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by pechora8.dc.icann.org (8.13.8/8.13.8) with SMTP id p5EM0RMQ018720 for <ietf-types@iana.org>; Tue, 14 Jun 2011 18:00:47 -0400
Received: (qmail invoked by alias); 14 Jun 2011 22:00:25 -0000
Received: from xdsl-87-78-102-6.netcologne.de (EHLO [192.168.1.207]) [87.78.102.6] by mail.gmx.net (mp011) with SMTP; 15 Jun 2011 00:00:25 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/p2XRo7CDpud7G/eI/IZDUFKvN/Hur3b7dlsMZ7X +Cfb5i3Rgb29WM
Message-ID: <4DF7D9F9.1020402@gmx.de>
Date: Wed, 15 Jun 2011 00:00:25 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: Bjoern Hoehrmann <derhoermi@gmx.net>
References: <surev6hio3morol2u6431pf6m413ntcl4g@hive.bjoern.hoehrmann.de>
In-Reply-To: <surev6hio3morol2u6431pf6m413ntcl4g@hive.bjoern.hoehrmann.de>
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 (pechora8.dc.icann.org [192.0.46.74]); Tue, 14 Jun 2011 18:00:48 -0400 (EDT)
Cc: ietf-types@iana.org
Subject: Re: [ietf-types] Comments on draft-melnikov-mime-default-charset-00.txt
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jun 2011 22:01:04 -0000

On 2011-06-14 17:18, Bjoern Hoehrmann wrote:
> ...
> There is also confusion about what RFC 2046 specifies. The default of
> US-ASCII is for the text/plain type. While there are suggestions that it
> ...

No, it *really* applies to text/*.

See 
<http://greenbytes.de/tech/webdav/rfc2046.html#rfc.section.4.1.2.p.18> 
-- that's in the section 4.1.2 (Charset Parameter), not in 4.1.3 (Plain 
Subtype).

Best regards, Julian


Return-Path: <derhoermi@gmx.net>
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 1A0AF1F0C36 for <ietf-types@ietfa.amsl.com>; Tue, 14 Jun 2011 08:18:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.216
X-Spam-Level: 
X-Spam-Status: No, score=-2.216 tagged_above=-999 required=5 tests=[AWL=0.383,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U-4oJCgxOZor for <ietf-types@ietfa.amsl.com>; Tue, 14 Jun 2011 08:18:44 -0700 (PDT)
Received: from pechora6.dc.icann.org (pechora6.icann.org [192.0.46.72]) by ietfa.amsl.com (Postfix) with ESMTP id A73811F0C34 for <ietf-types@ietf.org>; Tue, 14 Jun 2011 08:18:44 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by pechora6.dc.icann.org (8.13.8/8.13.8) with SMTP id p5EFI8FA008262 for <ietf-types@iana.org>; Tue, 14 Jun 2011 11:18:28 -0400
Received: (qmail invoked by alias); 14 Jun 2011 15:18:06 -0000
Received: from dslb-094-222-153-106.pools.arcor-ip.net (EHLO HIVE) [94.222.153.106] by mail.gmx.net (mp051) with SMTP; 14 Jun 2011 17:18:06 +0200
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX1/IgSsK5WHI6cDDmK7KkQNwkSbVGgvTCssb5Fx/iE 6dD82h9JHxzzOT
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: ietf-types@iana.org
Date: Tue, 14 Jun 2011 17:18:17 +0200
Message-ID: <surev6hio3morol2u6431pf6m413ntcl4g@hive.bjoern.hoehrmann.de>
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.2.3 (pechora6.dc.icann.org [192.0.46.72]); Tue, 14 Jun 2011 11:18:29 -0400 (EDT)
Subject: [ietf-types] Comments on draft-melnikov-mime-default-charset-00.txt
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jun 2011 15:18:46 -0000

Hi,

  On http://www.ietf.org/id/draft-melnikov-mime-default-charset-00.txt

The first paragraph is horrible. It fails to properly separate the RFC
2046 context from the RFC 2616 context, and instead makes encoding de-
tection a property of the media type independently of context. That is
not how media types are used, it is common for instance to use them in
contexts where a character encoding is not used at all, for instance,
in a XHTML document with

  <style type='text/css'>
    ...
  </style>

there is no value used for the absent charset parameter, it's a notion
that does not make sense in the context. Similarily, I might make a
protocol similar to HTTP where all text/* is transported UTF-16 encoded
which would result in a similar situation. Even if that protocol had a
Content-Type header and allowed media type parameters, the charset para-
meter would have no influence on the bytes-to-text mapping.

There is also confusion about what RFC 2046 specifies. The default of
US-ASCII is for the text/plain type. While there are suggestions that it
"kinda" applies to other sub-types, for instance, like when handling an
unrecognized subtype, it should be handled like "plain", the language in
RFC 2046 leaves room for much interpretation and running code often does
not follow a particular interpretation like the one in the draft.

I think this should all be something more like "This memo changes RFC
2046 by defining and clarifying rules how to determine the character
encoding of resources labeled with a text subtype." and then say little
about the various sources of disputes and confusion.

In section 3 the notion that you always get to know the encoding, as is
implied by, for instance, "i.e. the charset information is transport
inside the payload", does not reflect current practise. Look, for text/
plain, and for many other subtypes, if there is no charset parameter,
then you don't know what encoding it is in. Maybe there are internal
markers, maybe there are not. Some formats do not even care, it's common
for "source code" for instance to just care about some special bytes and
ignore or pass verbatim the rest; some allow to mix encodings.

It seems to me the rules should rather be something like:

  1. If there is a higher-level protocol with rules, those rules win.

  2. If there is a charset parameter but it's malformed: out of scope.

  3. If there is a properly formed charset parameter, that wins. That
     wins even if the encoding is unsupported and there are other hints
     inside the document. That wins for all text subtypes, always.

  4. Otherwise it's type-specific and if the type specification does
     not define how you determine the encoding in this case, you don't
     know what the encoding is. For text/plain in particular, you do
     not know, it's not US-ASCII, you don't know.

I don't see why you would not define it this way, it sets expectations
reasonably well while also being relatively simple. There is no utility
for instance in having some text types that do not use the charset pa-
rameter at this level. You may very well have a format that just says it
is always UTF-8, but when you add charset=iso-8859-1 then some will take
the charset parameter as authoriative, possibly due to text/plain de-
faulting, so you get confusion and security vulnerabilities.

What should happen in a case like that is that the receiving software
recognizes the presence of a charset parameter with an encoding that is
not expected, like in the example, as indicating corruption and maybe a
deliberate attack against the system and respond as appropriate. It's a
bad idea to simply ignore the charset parameter and essentially hope the
other components of the system handle the situation safely even as they
are updated and replaced over time.

Leaving the US-ASCII default as-is seems rather silly even, there is so
much non-ASCII text/plain content without a proper label out there, it's
without informational value to say the default is US-ASCII beyond saying
not including a charset parameter is probably a bad idea (but plenty of
people do it anyway).

regards,
-- 
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: <creed@opengeospatial.org>
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 0052EE07F5 for <ietf-types@ietfa.amsl.com>; Fri,  3 Jun 2011 15:28:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.116
X-Spam-Level: 
X-Spam-Status: No, score=-1.116 tagged_above=-999 required=5 tests=[AWL=-0.640, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_NET=0.311, J_CHICKENPOX_33=0.6, J_CHICKENPOX_63=0.6, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4ai9PmHAIBPc for <ietf-types@ietfa.amsl.com>; Fri,  3 Jun 2011 15:28:11 -0700 (PDT)
Received: from pechora4.lax.icann.org (pechora4.icann.org [IPv6:2620:0:2d0:1::39]) by ietfa.amsl.com (Postfix) with ESMTP id 10F4DE07F2 for <ietf-types@ietf.org>; Fri,  3 Jun 2011 15:28:09 -0700 (PDT)
Received: from mail.opengeospatial.org (scale.ogcinc.net [66.244.86.102]) by pechora4.lax.icann.org (8.13.8/8.13.8) with ESMTP id p53MRm00024138 for <ietf-types@iana.org>; Fri, 3 Jun 2011 15:28:08 -0700
Received: from localhost (localhost [127.0.0.1]) by mail.opengeospatial.org (Postfix) with ESMTP id B91F95A1C3; Fri,  3 Jun 2011 18:27:47 -0400 (EDT)
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 FsrBouoaV12I; Fri,  3 Jun 2011 18:27:47 -0400 (EDT)
Received: from CarlandSusieOf (c-98-245-174-99.hsd1.co.comcast.net [98.245.174.99]) by mail.opengeospatial.org (Postfix) with ESMTPSA id 6E75F5A1B3; Fri,  3 Jun 2011 18:27:46 -0400 (EDT)
Message-ID: <DCDA958C2A964D17A7C2F6E533753B1E@CarlandSusieOf>
From: "Carl Reed" <creed@opengeospatial.org>
To: "Paul Libbrecht" <paul@hoplahup.net>
References: <ACC2090E6F07476697E38D8E8067677A@CarlandSusieOf> <4c1du6tbs0ec7kc8kig2m9qbfufq217o79@hive.bjoern.hoehrmann.de> <554582F1EE504437ABA16C499D64DF0D@CarlandSusieOf> <0C273449-27D3-4898-A1C0-B910B3FE0107@hoplahup.net>
In-Reply-To: <0C273449-27D3-4898-A1C0-B910B3FE0107@hoplahup.net>
Date: Fri, 3 Jun 2011 16:27:43 -0600
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Windows Mail 6.0.6000.16480
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6000.16669
X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora4.lax.icann.org [208.77.188.39]); Fri, 03 Jun 2011 15:28:09 -0700 (PDT)
Cc: ietf-types@iana.org, Bjoern Hoehrmann <derhoermi@gmx.net>
Subject: Re: [ietf-types] Registration of media type gml+xml (by the Open Geospatial Consortium)
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jun 2011 22:28:12 -0000

Paul -

Thanks for the feedback. Let be pass on your suggestion to the OGC GML 
community.

Regards

Carl

----- Original Message ----- 
From: "Paul Libbrecht" <paul@hoplahup.net>
To: "Carl Reed" <creed@opengeospatial.org>
Cc: "Bjoern Hoehrmann" <derhoermi@gmx.net>; <ietf-types@iana.org>
Sent: Friday, June 03, 2011 4:26 PM
Subject: Re: [ietf-types] Registration of media type gml+xml (by the Open 
Geospatial Consortium)


Carl,

Could I suggest that the additional information section is enriched with 
recommended flavor names for the Windows and MacOSX operating systems?

At first glance, I would suggest the following:
- Windows Clipboard Name: OGC GML
- Macintosh Universal Type Identifier code: public.gml conforming to 
public.xml

This way, interoperability can be done at the clipboard. Do I mistake or the 
clipboard sounds to be a fairly good place to put, say, a location or route 
you have selected and copied in one application and want to paste into 
another?

thanks in advance

Paul


Le 3 juin 2011 à 23:47, Carl Reed a écrit :

> Bjoern and the ietf-types list -
>
> I have coordinated with Clemens Portele on a revision to the contents of 
> the submission. Please find below my signature a revision to the 
> registration request for a media type gml+xml (by the Open Geospatial 
> Consortium)
>
> I also checked to make sure that we are using the correct template as 
> specified in RFC 4288. I will update the version as uploaded to 
> datatracker.
>
> Regards
>
> Carl Reed, PhD
> CTO
> Open Geospatial Consortium
>
>
> Type name: Application
>
> Subtype name: Standards Tree gml+xml
>
> Required parameters:  None
>
> Optional parameters:
>  "charset" The charset parameter of application/gml+xml is
>  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 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 or in the 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 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=37743
>
> 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=23325
>
>
>
>
> ----- Original Message ----- From: "Bjoern Hoehrmann" <derhoermi@gmx.net>
> To: "Carl Reed" <creed@opengeospatial.org>
> Cc: <ietf-types@iana.org>
> Sent: Wednesday, June 01, 2011 12:34 PM
> Subject: Re: [ietf-types] Registration of media type -gml+xml (by the Open 
> Geospatial Consortium)
>
>
>> * Carl Reed wrote:
>>> MIME media type name: Application
>>
>> This seems to be using an outdated template. The current template is in
>> RFC 4288, there are some minor differences like this field name. New re-
>> gistrations should follow the most recent template.
>>
>>> MIME subtype name:    Standards Tree -gml+xml
>>
>> The value should be "gml+xml" if this' to register application/gml+xml.
>>
>>> Optional parameters:
>>>
>>>  "charset" The charset parameter of application/gml+xml is
>>>  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
>>>  version used in the GML document. Only the major and
>>>  the first minor version number are provided, e.g. "3.2".
>>
>> (I think this is insufficient, for instance, it is not clear whether
>> you can use version=3.2 and also version="3.2" but many registrations
>> have this problem.)
>> -- 
>> 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/
>
> _______________________________________________
> ietf-types mailing list
> ietf-types@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-types




Return-Path: <paul@hoplahup.net>
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 D56DCE07F5 for <ietf-types@ietfa.amsl.com>; Fri,  3 Jun 2011 15:26:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.049
X-Spam-Level: 
X-Spam-Status: No, score=-1.049 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, J_CHICKENPOX_33=0.6, J_CHICKENPOX_63=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uqfRDhJb9cqM for <ietf-types@ietfa.amsl.com>; Fri,  3 Jun 2011 15:26:32 -0700 (PDT)
Received: from pechora7.dc.icann.org (pechora7.icann.org [IPv6:2620:0:2830:201::1:73]) by ietfa.amsl.com (Postfix) with ESMTP id 6F2ADE07F2 for <ietf-types@ietf.org>; Fri,  3 Jun 2011 15:26:32 -0700 (PDT)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by pechora7.dc.icann.org (8.13.8/8.13.8) with ESMTP id p53MQBqr028597 for <ietf-types@iana.org>; Fri, 3 Jun 2011 18:26:31 -0400
Received: from [192.168.178.137] (srbk-4d0b920f.pool.mediaWays.net [77.11.146.15]) by mrelayeu.kundenserver.de (node=mrbap4) with ESMTP (Nemesis) id 0MRljF-1Pzhyi1Z3h-00SvhA; Sat, 04 Jun 2011 00:26:09 +0200
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset=iso-8859-1
From: Paul Libbrecht <paul@hoplahup.net>
X-Priority: 3
In-Reply-To: <554582F1EE504437ABA16C499D64DF0D@CarlandSusieOf>
Date: Sat, 4 Jun 2011 00:26:08 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <0C273449-27D3-4898-A1C0-B910B3FE0107@hoplahup.net>
References: <ACC2090E6F07476697E38D8E8067677A@CarlandSusieOf> <4c1du6tbs0ec7kc8kig2m9qbfufq217o79@hive.bjoern.hoehrmann.de> <554582F1EE504437ABA16C499D64DF0D@CarlandSusieOf>
To: Carl Reed <creed@opengeospatial.org>
X-Mailer: Apple Mail (2.1078)
X-Provags-ID: V02:K0:TyV4ZqfOVIChEMaz+KoQU/HpMjCpf+syl13913V1Kwi bCctwPbk2iOP2n6X3wg4Y//YOdT9Pk16slm1jh9G6NZR85/20L zrpcXXWOcmYWa00Een3nIh/K5laLbN1t23GIooVw4d07L2cS4X xZ+NfHHXNlSSniiX+oxgLCIx3li4VR3AoF1SUfvQ7prvJmiPS0 dwLfFRvo+WBim9py8h6NvJ/psZ7QqyGwJt69xCz3iU=
X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.2.3 (pechora7.dc.icann.org [192.0.46.73]); Fri, 03 Jun 2011 18:26:31 -0400 (EDT)
Cc: ietf-types@iana.org, Bjoern Hoehrmann <derhoermi@gmx.net>
Subject: Re: [ietf-types] Registration of media type gml+xml (by the Open Geospatial Consortium)
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jun 2011 22:26:34 -0000

Carl,

Could I suggest that the additional information section is enriched with =
recommended flavor names for the Windows and MacOSX operating systems?

At first glance, I would suggest the following:
- Windows Clipboard Name: OGC GML
- Macintosh Universal Type Identifier code: public.gml conforming to =
public.xml

This way, interoperability can be done at the clipboard. Do I mistake or =
the clipboard sounds to be a fairly good place to put, say, a location =
or route you have selected and copied in one application and want to =
paste into another?

thanks in advance

Paul


Le 3 juin 2011 =E0 23:47, Carl Reed a =E9crit :

> Bjoern and the ietf-types list -
>=20
> I have coordinated with Clemens Portele on a revision to the contents =
of the submission. Please find below my signature a revision to the =
registration request for a media type gml+xml (by the Open Geospatial =
Consortium)
>=20
> I also checked to make sure that we are using the correct template as =
specified in RFC 4288. I will update the version as uploaded to =
datatracker.
>=20
> Regards
>=20
> Carl Reed, PhD
> CTO
> Open Geospatial Consortium
>=20
>=20
> Type name: Application
>=20
> Subtype name: Standards Tree gml+xml
>=20
> Required parameters:  None
>=20
> Optional parameters:
>  "charset" The charset parameter of application/gml+xml is
>  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.,
>  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 or in the OGC
>  Web Feature Service.
>=20
> Encoding considerations: As per Section 3.2 of [RFC3023]
>=20
> 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.
>=20
>  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.
>=20
> 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.
>=20
> 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.
>=20
>  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
>=20
> 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.
>=20
> Additional information:
>=20
> 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
>=20
>   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.
>=20
> Person & email address to contact for further information:
>=20
>   Name : Clemens Portele
>   Address:Interactive Instruments, Bonn, Germany
>   Email : portele@interactive-instruments.de
>=20
> Intended usage: Common
>=20
> Restrictions on usage:
>   None
>=20
> 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.
>=20
>   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
>=20
>=20
>=20
>=20
> ----- Original Message ----- From: "Bjoern Hoehrmann" =
<derhoermi@gmx.net>
> To: "Carl Reed" <creed@opengeospatial.org>
> Cc: <ietf-types@iana.org>
> Sent: Wednesday, June 01, 2011 12:34 PM
> Subject: Re: [ietf-types] Registration of media type -gml+xml (by the =
Open Geospatial Consortium)
>=20
>=20
>> * Carl Reed wrote:
>>> MIME media type name: Application
>>=20
>> This seems to be using an outdated template. The current template is =
in
>> RFC 4288, there are some minor differences like this field name. New =
re-
>> gistrations should follow the most recent template.
>>=20
>>> MIME subtype name:    Standards Tree -gml+xml
>>=20
>> The value should be "gml+xml" if this' to register =
application/gml+xml.
>>=20
>>> Optional parameters:
>>>=20
>>>  "charset" The charset parameter of application/gml+xml is
>>>  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
>>>  version used in the GML document. Only the major and
>>>  the first minor version number are provided, e.g. "3.2".
>>=20
>> (I think this is insufficient, for instance, it is not clear whether
>> you can use version=3D3.2 and also version=3D"3.2" but many =
registrations
>> have this problem.)
>> --=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
> _______________________________________________
> ietf-types mailing list
> ietf-types@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-types



Return-Path: <creed@opengeospatial.org>
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 1C160E0772 for <ietf-types@ietfa.amsl.com>; Fri,  3 Jun 2011 15:14:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.53
X-Spam-Level: 
X-Spam-Status: No, score=-1.53 tagged_above=-999 required=5 tests=[AWL=-0.454,  BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_NET=0.311,  J_CHICKENPOX_33=0.6, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w+SVEdBhJxYT for <ietf-types@ietfa.amsl.com>; Fri,  3 Jun 2011 15:14:18 -0700 (PDT)
Received: from pechora5.dc.icann.org (pechora5.icann.org [IPv6:2620:0:2830:201::1:71]) by ietfa.amsl.com (Postfix) with ESMTP id 771FCE07F2 for <ietf-types@ietf.org>; Fri,  3 Jun 2011 15:14:17 -0700 (PDT)
Received: from mail.opengeospatial.org (scale.ogcinc.net [66.244.86.102]) by pechora5.dc.icann.org (8.13.8/8.13.8) with ESMTP id p53MDupw009217 for <ietf-types@iana.org>; Fri, 3 Jun 2011 15:14:16 -0700
Received: from localhost (localhost [127.0.0.1]) by mail.opengeospatial.org (Postfix) with ESMTP id A6F225A1CA; Fri,  3 Jun 2011 18:13:55 -0400 (EDT)
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 VoesR+6ltmvq; Fri,  3 Jun 2011 18:13:54 -0400 (EDT)
Received: from CarlandSusieOf (c-98-245-174-99.hsd1.co.comcast.net [98.245.174.99]) by mail.opengeospatial.org (Postfix) with ESMTPSA id BCA055A1C3; Fri,  3 Jun 2011 18:13:54 -0400 (EDT)
Message-ID: <554582F1EE504437ABA16C499D64DF0D@CarlandSusieOf>
From: "Carl Reed" <creed@opengeospatial.org>
To: "Bjoern Hoehrmann" <derhoermi@gmx.net>
References: <ACC2090E6F07476697E38D8E8067677A@CarlandSusieOf> <4c1du6tbs0ec7kc8kig2m9qbfufq217o79@hive.bjoern.hoehrmann.de>
In-Reply-To: <4c1du6tbs0ec7kc8kig2m9qbfufq217o79@hive.bjoern.hoehrmann.de>
Date: Fri, 3 Jun 2011 15:47:55 -0600
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Windows Mail 6.0.6000.16480
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6000.16669
X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora5.dc.icann.org [192.0.46.71]); Fri, 03 Jun 2011 15:14:16 -0700 (PDT)
Cc: ietf-types@iana.org
Subject: Re: [ietf-types] Registration of media type gml+xml (by the Open Geospatial Consortium)
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jun 2011 22:14:19 -0000

Bjoern and the ietf-types list -

I have coordinated with Clemens Portele on a revision to the contents of the 
submission. Please find below my signature a revision to the registration 
request for a media type gml+xml (by the Open Geospatial Consortium)

I also checked to make sure that we are using the correct template as 
specified in RFC 4288. I will update the version as uploaded to datatracker.

Regards

Carl Reed, PhD
CTO
Open Geospatial Consortium


Type name: Application

Subtype name: Standards Tree gml+xml

Required parameters:  None

Optional parameters:
   "charset" The charset parameter of application/gml+xml is
   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 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 or in the 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 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=37743

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=23325




----- Original Message ----- 
From: "Bjoern Hoehrmann" <derhoermi@gmx.net>
To: "Carl Reed" <creed@opengeospatial.org>
Cc: <ietf-types@iana.org>
Sent: Wednesday, June 01, 2011 12:34 PM
Subject: Re: [ietf-types] Registration of media type -gml+xml (by the Open 
Geospatial Consortium)


>* Carl Reed wrote:
>>MIME media type name: Application
>
> This seems to be using an outdated template. The current template is in
> RFC 4288, there are some minor differences like this field name. New re-
> gistrations should follow the most recent template.
>
>>MIME subtype name:    Standards Tree -gml+xml
>
> The value should be "gml+xml" if this' to register application/gml+xml.
>
>>Optional parameters:
>>
>>   "charset" The charset parameter of application/gml+xml is
>>   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
>>   version used in the GML document. Only the major and
>>   the first minor version number are provided, e.g. "3.2".
>
> (I think this is insufficient, for instance, it is not clear whether
> you can use version=3.2 and also version="3.2" but many registrations
> have this problem.)
> -- 
> 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: <derhoermi@gmx.net>
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 3408A130052 for <ietf-types@ietfa.amsl.com>; Wed,  1 Jun 2011 11:35:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.128
X-Spam-Level: 
X-Spam-Status: No, score=-3.128 tagged_above=-999 required=5 tests=[AWL=-0.529, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gVStKmVzqtkj for <ietf-types@ietfa.amsl.com>; Wed,  1 Jun 2011 11:35:09 -0700 (PDT)
Received: from pechora1.lax.icann.org (pechora1.icann.org [208.77.188.36]) by ietfa.amsl.com (Postfix) with ESMTP id E6AB7130047 for <ietf-types@ietf.org>; Wed,  1 Jun 2011 11:35:08 -0700 (PDT)
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 p51IYWOk014384 for <ietf-types@iana.org>; Wed, 1 Jun 2011 11:34:53 -0700
Received: (qmail invoked by alias); 01 Jun 2011 18:34:30 -0000
Received: from dslb-094-223-193-161.pools.arcor-ip.net (EHLO HIVE) [94.223.193.161] by mail.gmx.net (mp008) with SMTP; 01 Jun 2011 20:34:30 +0200
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX1/uRfk8DbTujf0Woq/WBJE5PmyBOFLMe3oax4S1/i by7hNg23OlX2PQ
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: "Carl Reed" <creed@opengeospatial.org>
Date: Wed, 01 Jun 2011 20:34:38 +0200
Message-ID: <4c1du6tbs0ec7kc8kig2m9qbfufq217o79@hive.bjoern.hoehrmann.de>
References: <ACC2090E6F07476697E38D8E8067677A@CarlandSusieOf>
In-Reply-To: <ACC2090E6F07476697E38D8E8067677A@CarlandSusieOf>
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 [208.77.188.36]); Wed, 01 Jun 2011 11:34:53 -0700 (PDT)
Cc: ietf-types@iana.org
Subject: Re: [ietf-types] Registration of media type -gml+xml (by the Open Geospatial Consortium)
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jun 2011 18:35:10 -0000

* Carl Reed wrote:
>MIME media type name: Application

This seems to be using an outdated template. The current template is in
RFC 4288, there are some minor differences like this field name. New re-
gistrations should follow the most recent template.

>MIME subtype name:    Standards Tree -gml+xml

The value should be "gml+xml" if this' to register application/gml+xml.

>Optional parameters:
>
>   "charset" The charset parameter of application/gml+xml is 
>   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 
>   version used in the GML document. Only the major and 
>   the first minor version number are provided, e.g. "3.2".

(I think this is insufficient, for instance, it is not clear whether
you can use version=3.2 and also version="3.2" but many registrations
have this problem.)
-- 
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: <creed@opengeospatial.org>
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 AAE0AE06BB for <ietf-types@ietfa.amsl.com>; Wed,  1 Jun 2011 09:51:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.137
X-Spam-Level: 
X-Spam-Status: No, score=-2.137 tagged_above=-999 required=5 tests=[AWL=0.461,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ekkLTyrsVLcP for <ietf-types@ietfa.amsl.com>; Wed,  1 Jun 2011 09:51:45 -0700 (PDT)
Received: from pechora1.lax.icann.org (pechora1.icann.org [208.77.188.36]) by ietfa.amsl.com (Postfix) with ESMTP id 61DABE067E for <ietf-types@ietf.org>; Wed,  1 Jun 2011 09:51:45 -0700 (PDT)
Received: from mail.opengeospatial.org (scale.ogcinc.net [66.244.86.102]) by pechora1.lax.icann.org (8.13.8/8.13.8) with ESMTP id p51Gp9Ha015830 for <ietf-types@iana.org>; Wed, 1 Jun 2011 09:51:29 -0700
Received: from localhost (localhost [127.0.0.1]) by mail.opengeospatial.org (Postfix) with ESMTP id 6C3BB5A0FE for <ietf-types@iana.org>; Wed,  1 Jun 2011 12:26:29 -0400 (EDT)
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 SKo5RdpqU-gT for <ietf-types@iana.org>; Wed,  1 Jun 2011 12:26:28 -0400 (EDT)
Received: from CarlandSusieOf (c-98-245-174-99.hsd1.co.comcast.net [98.245.174.99]) by mail.opengeospatial.org (Postfix) with ESMTPSA id 299395A0FC for <ietf-types@iana.org>; Wed,  1 Jun 2011 12:26:28 -0400 (EDT)
Message-ID: <ACC2090E6F07476697E38D8E8067677A@CarlandSusieOf>
From: "Carl Reed" <creed@opengeospatial.org>
To: <ietf-types@iana.org>
Date: Wed, 1 Jun 2011 10:25:17 -0600
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0343_01CC2046.33DB9590"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Windows Mail 6.0.6000.16480
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6000.16669
X-Greylist: Delayed for 00:24:38 by milter-greylist-4.0 (pechora1.lax.icann.org [208.77.188.36]); Wed, 01 Jun 2011 09:51:30 -0700 (PDT)
X-Mailman-Approved-At: Wed, 01 Jun 2011 10:22:52 -0700
Subject: [ietf-types] Registration of media type -gml+xml (by the Open Geospatial Consortium)
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jun 2011 16:51:46 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0343_01CC2046.33DB9590
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

To whom it may concern -

The OGC is an international standards organization focused on encoding =
and interface standards for use in the geospatial and locations services =
domains. One of out most widely implemented standards is the Geography =
Markup Language (GML). Recently, the GML implementation community has =
identifed the need for a GML MIME type. Below my signature is the =
information on the GML MIME type for your review and consideration. The =
long version of this document may be found at: =
http://www.ietf.org/internet-drafts/draft-portele-ogc-gml-mime-01.txt

Thank you for your time and consideration.

Regards

Carl Reed, PhD
CTO and Executive Director Specification Program
Open Geospatial Consortium
www.opengeospatial.org

Name: Carl Reed

=20

Email: creed@opengeospatial.org

=20

MIME media type name: Application

=20

MIME subtype name:    Standards Tree -gml+xml

=20

Required parameters:  None

=20

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=20

   the first minor version number are provided, e.g. "3.2".

=20

Encoding considerations: As per Section 3.2 of [RFC3023]

=20

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.

=20

   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.

=20

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.

=20

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 online at

   http://www.opengeospatial.org/standards/gml.

=20

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

=20

Applications which use this media:

   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.

=20

Additional information:

=20

 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

=20

    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.

=20

 Person to contact for further information :

=20

    Name : Clemens Portele

    Address:Interactive Instruments, Bonn, Germany

    Email : portele@interactive-instruments.de

=20

 Intended usage: Common

=20

 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.

=20

      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 Specification 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_0343_01CC2046.33DB9590
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.6000.17037" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>To whom it may concern -</DIV>
<DIV>&nbsp;</DIV>
<DIV>The OGC is an international standards organization focused on =
encoding and=20
interface standards for use in the geospatial and locations services =
domains.=20
One of out most widely implemented standards is the Geography Markup =
Language=20
(GML). Recently, the GML implementation community has identifed the need =
for a=20
GML MIME type. Below my signature is the information on the GML MIME =
type for=20
your review and consideration. The long version of this document may be =
found=20
at: <A=20
href=3D"http://www.ietf.org/internet-drafts/draft-portele-ogc-gml-mime-01=
.txt">http://www.ietf.org/internet-drafts/draft-portele-ogc-gml-mime-01.t=
xt</A><BR></DIV>
<DIV>Thank you for your time and consideration.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Regards</DIV>
<DIV>&nbsp;</DIV>
<DIV>
<DIV>Carl Reed, PhD<BR>CTO and Executive Director Specification =
Program<BR>Open=20
Geospatial Consortium<BR><A=20
href=3D"http://www.opengeospatial.org/">www.opengeospatial.org</A></DIV><=
/DIV>
<DIV>&nbsp;</DIV>
<DIV>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt; mso-outline-level: =
1"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New">Name: Carl Reed<?xml:namespace prefix =3D o ns =3D=20
"urn:schemas-microsoft-com:office:office" =
/><o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: =
yes">&nbsp;</SPAN><o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt; mso-outline-level: =
1"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New">Email:=20
creed@opengeospatial.org<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New">&nbsp;<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt; mso-outline-level: =
1"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New">MIME media type name:=20
Application<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New">&nbsp;<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt; mso-outline-level: =
1"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New">MIME subtype name:<SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp; </SPAN>Standards Tree=20
-gml+xml<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New">&nbsp;<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt; mso-outline-level: =
1"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New">Required parameters:<SPAN style=3D"mso-spacerun: =
yes">&nbsp;=20
</SPAN>None<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New">&nbsp;<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New">Optional =
parameters:<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp; =
</SPAN>=93charset=94=20
The charset parameter of application/gml+xml is=20
<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp; =
</SPAN>handled=20
in the same fashion as for application/xml, as=20
specified<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp; =
</SPAN>in=20
Section 3.2 of [RFC3023]<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp;=20
</SPAN>"version": If provided, this parameter indicates the GML=20
<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp; =
</SPAN>version=20
used in the GML document. Only the major and=20
<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp; =
</SPAN>the first=20
minor version number are provided, e.g.=20
"3.2".<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: =
yes">&nbsp;</SPAN><o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt; mso-outline-level: =
1"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New">Encoding considerations: As per Section 3.2 of=20
[RFC3023]<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: =
yes">&nbsp;</SPAN><o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New">Security =
considerations:<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp; =
</SPAN>The OGC=20
Geography Markup Language (GML) is a generic format=20
for<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp;=20
</SPAN>exchanging geographic information, but application designers=20
must<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp; =
</SPAN>not=20
assume that it provides generic protection against=20
security<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp;=20
</SPAN>threats.<SPAN style=3D"mso-spacerun: yes">&nbsp; </SPAN>RFC 3023, =
section=20
10, discusses security concerns for<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp; =
</SPAN>generic=20
XML, which are also applicable to =
GML.<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: =
yes">&nbsp;</SPAN><o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp; =
</SPAN>Xlink=20
references in GML documents may cause arbitrary URIs to=20
be<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp;=20
</SPAN>dereferenced. In this case, the security issues of RFC=20
3986,<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp; =
</SPAN>section=20
7, should be considered.<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: =
yes">&nbsp;</SPAN><o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New">Interoperability=20
considerations:<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp; =
</SPAN>Different=20
versions of GML specify different XML Schema documents=20
used<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp; =
</SPAN>for the=20
validation of GML documents. Starting with version 3.2,=20
the<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp; =
</SPAN>GML=20
version information is represented in the namespace.=20
As<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp;=20
</SPAN>applications may only support a subset of all published=20
GML<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp; =
</SPAN>versions,=20
the use of the version parameter is=20
recommended.<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: =
yes">&nbsp;</SPAN><o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New">Published specification =
:<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp; =
</SPAN>GML=20
(Geography Markup Language) is an international=20
standard<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp; =
</SPAN>adopted=20
by both the Open Geospatial Consortium (OGC)=20
and<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp;=20
</SPAN>International Organization for Standardization (ISO). The=20
latest<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: =
yes">&nbsp;</SPAN><SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>version at the time of this =
writing is=20
3.2.1 which is published by<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp; =
</SPAN>ISO as=20
ISO 19136:2007. The standard can be accessed online=20
at<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp;=20
</SPAN>http://www.opengeospatial.org/standards/gml.<o:p></o:p></FONT></FO=
NT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: =
yes">&nbsp;</SPAN><o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt; mso-outline-level: =
1"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New">The OGC GML MIME specification has also been =
approved by the=20
OGC<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp; =
</SPAN><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;</SPAN>Membership and is published=20
here:<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp;=20
</SPAN>http://portal.opengeospatial.org/files/?artifact_id=3D37743<o:p></=
o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: =
yes">&nbsp;</SPAN><o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New">Applications which use this=20
media:<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp; =
</SPAN>GML is a=20
generic device-, platform-, and vendor-neutral=20
XML<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp; =
</SPAN>grammar=20
and is supported by a range of applications=20
creating,<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp; =
</SPAN>providing=20
access to and processing geographic information. The=20
use<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp; =
</SPAN>of GML is=20
in use internationally with hundreds of=20
deployed<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp;=20
</SPAN>applications able to create and ingest GML payloads, including=20
all<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp; =
</SPAN>of the=20
major GIS vendors, many database providers, earth=20
browzer<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;&nbsp;=20
</SPAN>applications, and so forth.<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: =
yes">&nbsp;</SPAN><o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New">Additional =
information:<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: =
yes">&nbsp;</SPAN><o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT =
size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-fareast-font-family: 'MS =
Mincho'"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;</SPAN>1. Magic number(s):<SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp; </SPAN>None. =
</SPAN>Although no=20
byte sequences can be<o:p></o:p></FONT></FONT></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-bidi-font-size: 12.0pt"><FONT size=3D2><FONT =
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp; </SPAN>counted on to =
consistently=20
identify GML documents, GML<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT =
size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;=20
</SPAN>documents will have the sequence=20
http://www.opengis.net/gml<o:p></o:p></FONT></FONT></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT =
size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp; </SPAN>as=20
part of a namespace declaration to identify the =
GML<o:p></o:p></FONT></FONT></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><FONT =
size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;=20
</SPAN>namespace. This will usually be towards the top of the =
document.<SPAN=20
style=3D"mso-fareast-font-family: 'MS =
Mincho'"><o:p></o:p></SPAN></FONT></FONT></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;</SPAN>2. =
File=20
extension(s): .xml or .gml<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;</SPAN>3. =
Macintosh=20
file type code: TEXT<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: yes">&nbsp;</SPAN>4. =
Object=20
Identifiers: None<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: =
yes">&nbsp;</SPAN><o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp; </SPAN>The=20
OGC is an international voluntary consensus=20
standards<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;=20
</SPAN>organization focused on defining and maintaining standards=20
that<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;=20
</SPAN>enable interoperability for using geospatial content and=20
services<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp; </SPAN>in=20
any application that requires the use of geospatial content=20
or<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;=20
</SPAN>services. The OGC website is=20
www.opengeospatial.org.<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: =
yes">&nbsp;</SPAN><o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: =
yes">&nbsp;</SPAN>Person to=20
contact for further information :<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: =
yes">&nbsp;</SPAN><o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt; mso-outline-level: =
1"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;=20
</SPAN>Name : Clemens Portele<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;=20
</SPAN>Address:Interactive Instruments, Bonn,=20
Germany<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;=20
</SPAN>Email :=20
portele@interactive-instruments.de<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: =
yes">&nbsp;</SPAN><o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt; mso-outline-level: =
1"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: =
yes">&nbsp;</SPAN>Intended usage:=20
Common<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: =
yes">&nbsp;</SPAN><o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN style=3D"mso-spacerun: =
yes">&nbsp;</SPAN>Author/Change=20
controller:<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>The =
GML standard=20
is a work product of the Open =
Geospatial<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</SPAN>Consortium=20
(OGC). The OGC and the GML Standards =
Working<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>Group =
have=20
change control over the GML =
standard.<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New">&nbsp;<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>MIME =
types for=20
use in OGC standards and formats are =
defined<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>by the =
OGC=20
Members and discussed and approved by the=20
OGC<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>Naming =
Authority=20
(OGC-NA). The function and role of the=20
OGC-NA<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>is =
described in=20
RFC 5165 and in the OGC Policies and=20
Procedures<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoPlainText style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"mso-fareast-font-family: 'MS Mincho'"><FONT size=3D2><FONT=20
face=3D"Courier New"><SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>here: =
<A=20
href=3D"http://portal.opengeospatial.org/files/?artifact_id=3D23325">http=
://portal.opengeospatial.org/files/?artifact_id=3D23325</A><o:p></o:p></F=
ONT></FONT></SPAN></P></DIV>
<DIV>&nbsp;</DIV>
<DIV>Carl Reed, PhD<BR>CTO and Executive Director Specification =
Program<BR>Open=20
Geospatial Consortium<BR><A=20
href=3D"http://www.opengeospatial.org">www.opengeospatial.org</A></DIV>
<DIV>&nbsp;</DIV>
<DIV>The OGC: Making Location Count!</DIV>
<DIV>&nbsp;</DIV>
<DIV>---------------------</DIV>
<DIV>&nbsp;</DIV>
<DIV>This communication, including attachments, is for the exclusive use =
of=20
addressee and may contain proprietary, confidential or privileged =
information.=20
If you are not the intended recipient, any use, copying, disclosure,=20
dissemination or distribution is strictly prohibited. If you are not the =

intended recipient, please notify the sender&nbsp; immediately by return =
email=20
and delete this communication and destroy all copies.</DIV>
<DIV>&nbsp;</DIV>
<DIV>"The important thing is not to stop questioning." -- Albert =
Einstein=20
<BR>"Security is mostly a superstition. It does not exist in nature. =
Life is=20
either a daring adventure or nothing." -- Helen Keller =
</DIV></BODY></HTML>

------=_NextPart_000_0343_01CC2046.33DB9590--


