From yakov@shaftek.org Mon Dec 3 19:34:54 2012 Return-Path: X-Original-To: media-types@ietfa.amsl.com Delivered-To: media-types@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D927921E803F for ; Mon, 3 Dec 2012 19:34:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.977 X-Spam-Level: X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 RfUywzHtTwbl for ; Mon, 3 Dec 2012 19:34:54 -0800 (PST) Received: from pechora3.lax.icann.org (unknown [IPv6:2620:0:2d0:201::1:73]) by ietfa.amsl.com (Postfix) with ESMTP id 5B31421E8039 for ; Mon, 3 Dec 2012 19:34:54 -0800 (PST) Received: from mail-vc0-f169.google.com (mail-vc0-f169.google.com [209.85.220.169]) by pechora3.lax.icann.org (8.13.8/8.13.8) with ESMTP id qB43YXEC031200 for ; Tue, 4 Dec 2012 03:34:53 GMT Received: by mail-vc0-f169.google.com with SMTP id gb23so2425353vcb.28 for ; Mon, 03 Dec 2012 19:34:32 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:from:date:message-id:subject:to :content-type:x-gm-message-state; bh=z3bL6rDa+4n7gTFBb/g0JZftJWgCYAjLjoLDwxpqp6M=; b=CekBiDftfHOh2oNyZ1Z4OGekNqCFYO8TnUD1MvnA47BoM4fnvX3IT9sBCvXJ7W/kQg mbJx4D2HOJWbvcbLwC+OOg+MCqZr9JJWWLjjdi32k5n7ONsUAa8u06HWPJ6evbRjcTv1 CU7bNT/Z5FZcWb6nrhUE+jqYnwpg35pVS+tb7u7akgEOsbqUWsnXIvkFHfxPSP0J+Lyt e5oYlz2T51TvvLAaaNG1ZvvO+MkuY4F+Yo2Qebimy3aljQvoG+ZNl5Dup+Iu3bjQHvA9 aQzyF8Vi0PHFyasXa67MhqfnNmF1GBqW8pWs+bdYcoE/4fMqKREDd36JzxVh9gD21DRY 9isg== Received: by 10.52.26.115 with SMTP id k19mr9137177vdg.67.1354591741929; Mon, 03 Dec 2012 19:29:01 -0800 (PST) MIME-Version: 1.0 Received: by 10.220.149.143 with HTTP; Mon, 3 Dec 2012 19:28:31 -0800 (PST) X-Originating-IP: [98.140.248.199] From: Yakov Shafranovich Date: Mon, 3 Dec 2012 22:28:31 -0500 Message-ID: To: media-types@iana.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQl0mW0o6yWH9GQCmG5qllYfASWeiMUdtwawJFksx0I1qqDvEsqifoxzD67qWnLqk4FwM1zy X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora3.lax.icann.org [192.0.33.73]); Tue, 04 Dec 2012 03:34:54 +0000 (UTC) Subject: [media-types] Updated media registration request: application/sql X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Dec 2012 03:34:55 -0000 I updated the relevant draft here: http://www.ietf.org/id/draft-shafranovich-mime-sql-02.txt Diff of changes here: http://www.ietf.org/rfcdiff?url2=draft-shafranovich-mime-sql-02 Here is the media registration template, I added more information on encoding: 2. Media Type Registration Application This section provides the media type registration application which will be submitted to IANA after IESG approval of this document. Type name: application Subtype name: sql Required parameters: N/A Optional parameters: "charset" - indicates the character set to be used. When not specified, US-ASCII should be assumed. Implementators should note that as per section 4.2.4, part 2 of [ISO.9075.2011], all SQL implementations are required to support US-ASCII, ISO-8859-1, UTF-8, UTF-16 and UTF-32 encodings. Those should be the only valid values for the charset parameter unless some other agreement exists between the parties. When using [Unicode], the [ISO.9075.2011] standard dictates a preference of UTF-8 over UTF-16, and UTF-16 over UTF-32. Encoding considerations:charset When no character set is specified via the "charset" parameter or US-ASCII is specified, 7bit encoding is used. When other character sets are used, 8bit or binary encoding may be required. Security considerations: Being that SQL is a full fledged programming language and may include embedded source code for other programming languages, it may be used to transfer malware, viruses and other malicious payloads. Implementors and users are encouraged only to exchange SQL files among trusted parties and utilize all available security measures such as restricted access, virus scanners, etc. to minimize risk. Interoperability considerations: While a single standard exists ([ISO.9075.2011]), vendor implementations of the standard vary significantly. Implementors and users should make sure that the exchanged SQL files match to the specific database/tool and version that they are using. Published specification: The most recent specification of SQL is available in [ISO.9075.2011]. Applications that use this media type: Databases and related tools Additional information: Magic number(s): N/A File extension(s): sql Macintosh File Type Code(s): TEXT Person & email address to contact for further information: Yakov Shafranovich Intended usage: COMMON Restrictions on usage: N/A Author/Change controller: IESG From shida@ntt-at.com Tue Dec 4 23:22:28 2012 Return-Path: X-Original-To: media-types@ietfa.amsl.com Delivered-To: media-types@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE5A521F8C6A for ; Tue, 4 Dec 2012 23:22:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -97.511 X-Spam-Level: X-Spam-Status: No, score=-97.511 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FRT_BELOW2=2.154, IP_NOT_FRIENDLY=0.334, 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 1W00y6ZALtsj for ; Tue, 4 Dec 2012 23:22:28 -0800 (PST) Received: from pechora5.dc.icann.org (pechora5.icann.org [IPv6:2620:0:2830:201::1:71]) by ietfa.amsl.com (Postfix) with ESMTP id 51ADA21F8C69 for ; Tue, 4 Dec 2012 23:22:28 -0800 (PST) Received: from gator465.hostgator.com (gator465.hostgator.com [69.56.174.130]) by pechora5.dc.icann.org (8.13.8/8.13.8) with ESMTP id qB57M6du002431 for ; Wed, 5 Dec 2012 07:22:27 GMT Received: from [125.193.49.76] (port=54470 helo=[192.168.11.3]) by gator465.hostgator.com with esmtpa (Exim 4.80) (envelope-from ) id 1Tg7jR-0004aL-W5 for media-types@iana.org; Tue, 04 Dec 2012 23:41:18 -0600 From: Shida Schubert Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Wed, 5 Dec 2012 14:41:16 +0900 Message-Id: <05DA5F2F-D32B-4A57-9DAA-97995A8C30AD@ntt-at.com> To: media-types@iana.org Mime-Version: 1.0 (Apple Message framework v1283) X-Mailer: Apple Mail (2.1283) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - gator465.hostgator.com X-AntiAbuse: Original Domain - iana.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ntt-at.com X-BWhitelist: yes X-Source: X-Source-Args: X-Source-Dir: X-Source-Sender: ([192.168.11.3]) [125.193.49.76]:54470 X-Source-Auth: shida.schubert+tingle.jp X-Email-Count: 2 X-Source-Cap: c3NoaWRhO3NzaGlkYTtnYXRvcjQ2NS5ob3N0Z2F0b3IuY29t X-Greylist: Delayed for 01:40:47 by milter-greylist-4.0 (pechora5.dc.icann.org [192.0.46.71]); Wed, 05 Dec 2012 07:22:27 +0000 (UTC) Subject: [media-types] MIME Type registration X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Dec 2012 07:22:29 -0000 Hi there; I would like to register (in the standards tree) a new MIME type that = has been defined in BLISS working group in RAI. The specification which = defines this MIME type is: http://tools.ietf.org/wg/bliss/draft-ietf-bliss-call-completion/ Section 12.2 has the MIME type registration information, and is = extracted bellow for your consideration/review. Please let me know if additional information or questions you may have. Thank you & Regars, Shida Schubert (BLISS chair) ************** MIME registration information ************** MIME media type name: application MIME subtype name: call-completion Required parameters: none. Optional parameters: none. Encoding considerations: Consists of lines of UTF-8-encoded characters, ended with CR-LF Security considerations: There are no security considerations internal to the media type. Its typical usage involves the security considerations described in RFC XXXX (Note for RFC Editor: Please fill in XXXX with the RFC number of this specification). Interoperability considerations: See RFC XXXX (Note for RFC Editor: Please fill in XXXX with the RFC number of this specification). Published specification: RFC XXXX (Note for RFC Editor: Please fill in XXXX with the RFC number of this specification) Applications that use this media type: the implementations of the call-completion features of the Session Initiation Protocol Additional information: Magic number(s): none File extension(s): not expected to be stored in files Macintosh file type code(s): not expected to be stored in files Person & email address to contact for further information: Martin Huelsemann, martin.huelsemann@telekom.de Intended usage: LIMITED USE Restrictions on usage: none Author/Change controller: the IETF From henke@henke37.cjb.net Sun Dec 9 07:20:08 2012 Return-Path: X-Original-To: media-types@ietfa.amsl.com Delivered-To: media-types@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B30D021F893C for ; Sun, 9 Dec 2012 07:20:07 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.998 X-Spam-Level: X-Spam-Status: No, score=-0.998 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HS_INDEX_PARAM=0.001, 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 jQ7pHsusL08m for ; Sun, 9 Dec 2012 07:20:06 -0800 (PST) Received: from pechora5.dc.icann.org (pechora5.icann.org [IPv6:2620:0:2830:201::1:71]) by ietfa.amsl.com (Postfix) with ESMTP id C600821F88BE for ; Sun, 9 Dec 2012 07:20:06 -0800 (PST) Received: from smtp-out11.han.skanova.net (smtp-out11.han.skanova.net [195.67.226.200]) by pechora5.dc.icann.org (8.13.8/8.13.8) with ESMTP id qB9FJj3l004926 for ; Sun, 9 Dec 2012 15:20:05 GMT Received: from [127.0.0.1] (90.230.202.243) by smtp-out11.han.skanova.net (8.5.133) (authenticated as u57601879) id 508F280700FE10E0 for media-types@iana.org; Sun, 9 Dec 2012 15:58:58 +0100 Message-ID: <50C4A72E.5000408@henke37.cjb.net> Date: Sun, 09 Dec 2012 15:58:54 +0100 From: Henrik Andersson User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20100101 Firefox/17.0 SeaMonkey/2.14.1 MIME-Version: 1.0 To: media-types@iana.org X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Greylist: Delayed for 00:20:45 by milter-greylist-4.0 (pechora5.dc.icann.org [192.0.46.71]); Sun, 09 Dec 2012 15:20:05 +0000 (UTC) X-Mailman-Approved-At: Sun, 09 Dec 2012 08:51:31 -0800 Subject: [media-types] A bunch of Valve types X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Dec 2012 15:23:31 -0000 Hi! First time poster, no time lurker here. I have been working on writing up some registrations for the types that the Source game engine, by Valve, uses. I would like some comments on what I have so far. Apologies in advance for not being in text/plain and for not quite following the standard headings. I will of course address those issues when I get to submitting the document for real. http://www.mediafire.com/view/?66n42xa3fpge47b I am mainly concerned about the top level types used for the various formats. Did I make the correct calls? Ps. I could not find any list registration instructions anywhere online. Please give me the stock reply. From dean.willis@softarmor.com Sun Dec 9 09:05:30 2012 Return-Path: X-Original-To: media-types@ietfa.amsl.com Delivered-To: media-types@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22FF221F8BF3 for ; Sun, 9 Dec 2012 09:05:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.196 X-Spam-Level: X-Spam-Status: No, score=-103.196 tagged_above=-999 required=5 tests=[AWL=0.402, BAYES_00=-2.599, HS_INDEX_PARAM=0.001, RCVD_IN_DNSWL_LOW=-1, 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 BAtIzlfrI0Ah for ; Sun, 9 Dec 2012 09:05:29 -0800 (PST) Received: from pechora8.dc.icann.org (unknown [IPv6:2620:0:2830:201::1:74]) by ietfa.amsl.com (Postfix) with ESMTP id A7D8021F85E7 for ; Sun, 9 Dec 2012 09:05:28 -0800 (PST) Received: from mail-ye0-f169.google.com (mail-ye0-f169.google.com [209.85.213.169]) by pechora8.dc.icann.org (8.13.8/8.13.8) with ESMTP id qB9H56p0023391 for ; Sun, 9 Dec 2012 17:05:27 GMT Received: by mail-ye0-f169.google.com with SMTP id l13so361866yen.28 for ; Sun, 09 Dec 2012 09:05:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=softarmor.com; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=tqprK0PNjnRYP37g6FEmuJ+3qUHDnGr+iBUanqZqkc0=; b=DBVaz0Z17Q/U1RR2THHHtuF9wsIBHaTkcNRnTrPY/wO2QYW+bgtE8qvRG5cdTdTKj6 4Ky9/3fC2NWAnZsfL17szoS9fUnGqFR+lF9rh056bYx7rNcGzOmnafxL7K1rgSFAg8az GrjFLLlkpZfj1Uown8YnLmWIGgtDDcxRL4les= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=tqprK0PNjnRYP37g6FEmuJ+3qUHDnGr+iBUanqZqkc0=; b=T0gJh948LWnCYoC8sS5lV84UX5y4xWm1R5v4xByo1jQrZNK78FOqnzpKksE6rQHHzP ASFQYvY70BGe6vMV+NKfJA0+l87L4VSt9bYIpGxHcTSBCspe/XqW+71FUddaSFOSw6tZ Q/dEzYKTn+DJACczS1DVA0nNV+1hajL+ALWXCYtROqpZMBCF3KYtf/tIYmAZjb6IroId LI5N7ORqu4RMVEcybFn/lyFtzvbwV3f8s0wqJNqZHq89SLECc7iPg11MOAZZdQI9uuw4 Bxx+Ki/CYuspCGCi551hQpPClRWMTb0LSJ9OCq8ys+t4MoTt0ORejGtWsk/C+Q5NnGI7 1o6g== Received: by 10.101.41.12 with SMTP id t12mr4970443anj.88.1355072706726; Sun, 09 Dec 2012 09:05:06 -0800 (PST) Received: from [192.168.2.114] (cpe-72-181-157-19.tx.res.rr.com. [72.181.157.19]) by mx.google.com with ESMTPS id e24sm22562183yhh.4.2012.12.09.09.05.05 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 09 Dec 2012 09:05:06 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) From: Dean Willis In-Reply-To: <50C4A72E.5000408@henke37.cjb.net> Date: Sun, 9 Dec 2012 11:05:07 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: References: <50C4A72E.5000408@henke37.cjb.net> To: Henrik Andersson X-Mailer: Apple Mail (2.1499) X-Gm-Message-State: ALoCoQmweX2zvK/WwDWEsLX8CUoWtF4sepZcUE1+8NaBV2AK9KaSQ6nprMisrnKUG3lwAKuIThnY X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.2.3 (pechora8.dc.icann.org [192.0.46.74]); Sun, 09 Dec 2012 17:05:27 +0000 (UTC) Cc: media-types@iana.org Subject: Re: [media-types] A bunch of Valve types X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Dec 2012 17:05:30 -0000 I confess to not having read through entirely, but I must ask: Why do these types need to be registered? Are they being sent as payload = in SMTP, HTTP, SIP or something such that a receiving end needs to treat = them based on the MIME-type encoding? Or are they, like the VMF format, = only used on a local filesystem by specialized tools? On Dec 9, 2012, at 8:58 AM, Henrik Andersson = wrote: > Hi! First time poster, no time lurker here. >=20 > I have been working on writing up some registrations for the types = that > the Source game engine, by Valve, uses. I would like some comments on > what I have so far. >=20 > Apologies in advance for not being in text/plain and for not quite > following the standard headings. I will of course address those issues > when I get to submitting the document for real. >=20 > http://www.mediafire.com/view/?66n42xa3fpge47b >=20 > I am mainly concerned about the top level types used for the various > formats. Did I make the correct calls? >=20 > Ps. I could not find any list registration instructions anywhere = online. > Please give me the stock reply. > _______________________________________________ > media-types mailing list > media-types@ietf.org > https://www.ietf.org/mailman/listinfo/media-types From henke@henke37.cjb.net Sun Dec 9 10:41:03 2012 Return-Path: X-Original-To: media-types@ietfa.amsl.com Delivered-To: media-types@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74D8C21F8CBE for ; Sun, 9 Dec 2012 10:41:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.949 X-Spam-Level: X-Spam-Status: No, score=-2.949 tagged_above=-999 required=5 tests=[AWL=0.650, 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 SCNYIxcrMMN1 for ; Sun, 9 Dec 2012 10:41:02 -0800 (PST) Received: from pechora8.dc.icann.org (unknown [IPv6:2620:0:2830:201::1:74]) by ietfa.amsl.com (Postfix) with ESMTP id AAF2721F88BE for ; Sun, 9 Dec 2012 10:41:02 -0800 (PST) Received: from smtp-out21.han.skanova.net (smtp-out21.han.skanova.net [195.67.226.208]) by pechora8.dc.icann.org (8.13.8/8.13.8) with ESMTP id qB9IefD4026926 for ; Sun, 9 Dec 2012 18:41:01 GMT Received: from [127.0.0.1] (90.230.202.243) by smtp-out21.han.skanova.net (8.5.133) (authenticated as u57601879) id 50B6243300448B97; Sun, 9 Dec 2012 19:20:15 +0100 Message-ID: <50C4D65C.8060709@henke37.cjb.net> Date: Sun, 09 Dec 2012 19:20:12 +0100 From: Henrik Andersson User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20100101 Firefox/17.0 SeaMonkey/2.14.1 MIME-Version: 1.0 To: Dean Willis References: <50C4A72E.5000408@henke37.cjb.net> In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Delayed for 00:20:22 by milter-greylist-4.2.3 (pechora8.dc.icann.org [192.0.46.74]); Sun, 09 Dec 2012 18:41:02 +0000 (UTC) X-Mailman-Approved-At: Sun, 09 Dec 2012 10:49:21 -0800 Cc: media-types@iana.org Subject: Re: [media-types] A bunch of Valve types X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Dec 2012 18:41:03 -0000 BSP files are regularly sent over HTTP as both manual map installs as well as automatic download in game. Some servers have custom content in the form of models, materials and textures. This is automatically downloaded over HTTP on connect. And BSP files often store models, textures, materials as well as other files that the map uses in the embedded zip file. In fact, all maps with built cubemaps (which are required for people to not laugh at you as a map maker) will at minimum include the cubemap textures and materials. A few of the file formats are unlikely to be sent at all, but I figured that I might as well cover all of them in one go. Dean Willis skriver: > > I confess to not having read through entirely, but I must ask: > > Why do these types need to be registered? Are they being sent as payload in SMTP, HTTP, SIP or something such that a receiving end needs to treat them based on the MIME-type encoding? Or are they, like the VMF format, only used on a local filesystem by specialized tools? > From ned.freed@mrochek.com Sun Dec 9 10:57:09 2012 Return-Path: X-Original-To: media-types@ietfa.amsl.com Delivered-To: media-types@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7342F21F8CBD for ; Sun, 9 Dec 2012 10:57:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.386 X-Spam-Level: X-Spam-Status: No, score=-1.386 tagged_above=-999 required=5 tests=[AWL=-1.201, BAYES_40=-0.185] 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 X1IgDU3cWQ8y for ; Sun, 9 Dec 2012 10:57:08 -0800 (PST) Received: from pechora8.dc.icann.org (unknown [IPv6:2620:0:2830:201::1:74]) by ietfa.amsl.com (Postfix) with ESMTP id 7F36F21F8CB1 for ; Sun, 9 Dec 2012 10:57:08 -0800 (PST) Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by pechora8.dc.icann.org (8.13.8/8.13.8) with ESMTP id qB9IujLn027547 for ; Sun, 9 Dec 2012 18:57:07 GMT Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01ONKWW218NK002XJU@mauve.mrochek.com> for media-types@iana.org; Sun, 9 Dec 2012 10:51:31 -0800 (PST) Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01ONJKIFWMHS00008S@mauve.mrochek.com>; Sun, 9 Dec 2012 10:51:29 -0800 (PST) Message-id: <01ONKWW0T5FC00008S@mauve.mrochek.com> Date: Sun, 09 Dec 2012 10:50:00 -0800 (PST) From: Ned Freed In-reply-to: "Your message dated Sun, 09 Dec 2012 11:05:07 -0600" MIME-version: 1.0 Content-type: TEXT/PLAIN References: <50C4A72E.5000408@henke37.cjb.net> To: Dean Willis X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.2.3 (pechora8.dc.icann.org [192.0.46.74]); Sun, 09 Dec 2012 18:57:07 +0000 (UTC) Cc: Henrik Andersson , media-types@iana.org Subject: Re: [media-types] A bunch of Valve types X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Dec 2012 18:57:09 -0000 > I confess to not having read through entirely, but I must ask: > Why do these types need to be registered? Are they being sent as payload in > SMTP, HTTP, SIP or something such that a receiving end needs to treat them > based on the MIME-type encoding? Or are they, like the VMF format, only used on > a local filesystem by specialized tools? One of the very first uses of media types was for file system typing, independent of any protocol use. Use in a protocol is not now and never has been a criteria for defining a type. Ned From dean.willis@softarmor.com Sun Dec 9 21:20:03 2012 Return-Path: X-Original-To: media-types@ietfa.amsl.com Delivered-To: media-types@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87F0721F8DBA for ; Sun, 9 Dec 2012 21:20:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.976 X-Spam-Level: X-Spam-Status: No, score=-102.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, 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 bEyWPBO1XtHA for ; Sun, 9 Dec 2012 21:20:01 -0800 (PST) Received: from pechora4.lax.icann.org (pechora4.icann.org [IPv6:2620:0:2d0:201::1:74]) by ietfa.amsl.com (Postfix) with ESMTP id 6284B21F8DFD for ; Sun, 9 Dec 2012 21:19:52 -0800 (PST) Received: from mail-vc0-f169.google.com (mail-vc0-f169.google.com [209.85.220.169]) by pechora4.lax.icann.org (8.13.8/8.13.8) with ESMTP id qBA5JPJ0022301 for ; Mon, 10 Dec 2012 05:19:45 GMT Received: by mail-vc0-f169.google.com with SMTP id gb23so1962650vcb.28 for ; Sun, 09 Dec 2012 21:19:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=softarmor.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=4bj+mz33dJWF6VR9gm4wWsPu1WsVtveoFkyimextZq0=; b=LyxzUQM4L35TML3oUp8nlSFz7EVrZSfvAktBsYsposWRb+CUbGQv2tjQnqVa0qXRPF +lgLtH4ys0XHiyote15kwiFmNoEJQbzAzBqLuA3p+C1JRPSKpOaVfLFwzCdjripX5pVD cVnBzGXCGMZue7DJBL6eoOataMyjNYa8DyBKI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=4bj+mz33dJWF6VR9gm4wWsPu1WsVtveoFkyimextZq0=; b=o/z1PdVpI4HEq2rhWb4e8octoO9XKti0PH5uHfHFO0jI4vQfR8wSu9gQvQeND8pnlx 1GKPjnbDcCn+jpXRE36scMxR278G8Jm11/zeZf6nyLVc38Yeh33o/IhRGWr5mOPkk+U5 9t67OQmBHtwInXA4nXD3N90BqHMx0s1M9cJIRryOFGl/oEXtwQD7vUBzJqz7EaA4zrdc 1K2f6oMAwyly/63l2GgmNnljrB6wQ1APG3FNuK2mEUQCVyYc7RZRt1vGth9B7vHu3IwC 65vpqeBBBqwHh/sbvE8sqKHBVCDhDPmC5WZTjL/IQXh9TfzQF3yKCaEC0VQ7FodfBTm2 Pj2g== MIME-Version: 1.0 Received: by 10.52.98.36 with SMTP id ef4mr7256285vdb.104.1355116764999; Sun, 09 Dec 2012 21:19:24 -0800 (PST) Received: by 10.58.1.66 with HTTP; Sun, 9 Dec 2012 21:19:24 -0800 (PST) Received: by 10.58.1.66 with HTTP; Sun, 9 Dec 2012 21:19:24 -0800 (PST) In-Reply-To: <01ONKWW0T5FC00008S@mauve.mrochek.com> References: <50C4A72E.5000408@henke37.cjb.net> <01ONKWW0T5FC00008S@mauve.mrochek.com> Date: Sun, 9 Dec 2012 23:19:24 -0600 Message-ID: From: Dean Willis To: Ned Freed Content-Type: multipart/alternative; boundary=20cf307f343468306204d078b533 X-Gm-Message-State: ALoCoQngEsmLREyj8UZj6yzbFdakQDOAm8DL08sg45j75zWxeBz3pXAfbrZt/TEdCc+pvicXYs/y X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora4.lax.icann.org [192.0.33.74]); Mon, 10 Dec 2012 05:19:45 +0000 (UTC) Cc: media-types@iana.org, Henrik Andersson Subject: Re: [media-types] A bunch of Valve types X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Dec 2012 05:20:03 -0000 --20cf307f343468306204d078b533 Content-Type: text/plain; charset=ISO-8859-1 True, but I'd say that the vast majority of file types for local storage have not been registered as MIME types, because they just haven't needed to be. As far as I know, the only times I bothered were when I was doing something that needed to be transported in a type-aware fashion OK n some sort of encapsulating protocol. Hence, I was idly curious as to what was driving the request. Wouldn't it be cool if Steam were actually using the MIME types and appropriate content-dispositions for things like delivery of updates? On Dec 9, 2012 12:56 PM, "Ned Freed" wrote: > > > I confess to not having read through entirely, but I must ask: > > > Why do these types need to be registered? Are they being sent as payload > in > > SMTP, HTTP, SIP or something such that a receiving end needs to treat > them > > based on the MIME-type encoding? Or are they, like the VMF format, only > used on > > a local filesystem by specialized tools? > > One of the very first uses of media types was for file system typing, > independent of any protocol use. > > Use in a protocol is not now and never has been a criteria for defining > a type. > > Ned > --20cf307f343468306204d078b533 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

True, but I'd say that the vast majority of file types f= or local storage have not been registered as MIME types, because they just = haven't needed to be. As far as I know, the only times I bothered were = when I was doing something that needed to be transported in a type-aware fa= shion OK n some sort of encapsulating protocol. Hence, I was idly curious a= s to what was driving the request. Wouldn't it be cool if Steam were ac= tually using the MIME types and appropriate content-dispositions for things= like delivery of updates?

On Dec 9, 2012 12:56 PM, "Ned Freed" &= lt;ned.freed@mrochek.com> w= rote:

> I confess to not having read through entirely, but I must ask:

> Why do these types need to be registered? Are they being sent as paylo= ad in
> SMTP, HTTP, SIP or something such that a receiving end needs to treat = them
> based on the MIME-type encoding? Or are they, like the VMF format, onl= y used on
> a local filesystem by specialized tools?

One of the very first uses of media types was for file system typing,
independent of any protocol use.

Use in a protocol is not now and never has been a criteria for defining
a type.

=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Ned
--20cf307f343468306204d078b533-- From duerst@it.aoyama.ac.jp Tue Dec 11 01:40:25 2012 Return-Path: X-Original-To: media-types@ietfa.amsl.com Delivered-To: media-types@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AE5B21F8716 for ; Tue, 11 Dec 2012 01:40:25 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -99.088 X-Spam-Level: X-Spam-Status: No, score=-99.088 tagged_above=-999 required=5 tests=[AWL=-1.713, BAYES_40=-0.185, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, HS_INDEX_PARAM=0.001, 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 gclek3h0suHj for ; Tue, 11 Dec 2012 01:40:24 -0800 (PST) Received: from pechora8.dc.icann.org (unknown [IPv6:2620:0:2830:201::1:74]) by ietfa.amsl.com (Postfix) with ESMTP id BC63021F8578 for ; Tue, 11 Dec 2012 01:40:23 -0800 (PST) Received: from acspool01.acbb.aoyama.ac.jp (acspool01.acbb.aoyama.ac.jp [133.2.20.162]) by pechora8.dc.icann.org (8.13.8/8.13.8) with ESMTP id qBB9e21G010131 for ; Tue, 11 Dec 2012 09:40:22 GMT Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by acspool01.acbb.aoyama.ac.jp (secret/secret) with ESMTP id qBB9H00f015532 for ; Tue, 11 Dec 2012 18:17:00 +0900 Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id qBB9DgQE031741 for ; Tue, 11 Dec 2012 18:13:42 +0900 Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 2473_ff73_0f1ea10a_4373_11e2_b28f_001d096c5782; Tue, 11 Dec 2012 18:13:42 +0900 Received: from [IPv6:::1] ([133.2.210.1]:60961) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id for from ; Tue, 11 Dec 2012 18:13:42 +0900 Message-ID: <50C6F944.7050603@it.aoyama.ac.jp> Date: Tue, 11 Dec 2012 18:13:40 +0900 From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= 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: Henrik Andersson References: <50C4A72E.5000408@henke37.cjb.net> In-Reply-To: <50C4A72E.5000408@henke37.cjb.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Delayed for 00:21:33 by milter-greylist-4.2.3 (pechora8.dc.icann.org [192.0.46.74]); Tue, 11 Dec 2012 09:40:23 +0000 (UTC) Cc: media-types@iana.org Subject: Re: [media-types] A bunch of Valve types X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Dec 2012 09:40:25 -0000 Hello Henrik, On 2012/12/09 23:58, Henrik Andersson wrote: > Hi! First time poster, no time lurker here. > > I have been working on writing up some registrations for the types that > the Source game engine, by Valve, uses. I would like some comments on > what I have so far. > > Apologies in advance for not being in text/plain and for not quite > following the standard headings. I will of course address those issues > when I get to submitting the document for real. > > http://www.mediafire.com/view/?66n42xa3fpge47b The chance to get feedback is much higher if you send the actual registration templates here. If you have many, maybe you can start with a typical one, and then move to bulk later. > I am mainly concerned about the top level types used for the various > formats. Did I make the correct calls? > > Ps. I could not find any list registration instructions anywhere online. > Please give me the stock reply. List-Subscribe: , > _______________________________________________ > media-types mailing list > media-types@ietf.org > https://www.ietf.org/mailman/listinfo/media-types > From ron.even.tlv@gmail.com Wed Dec 12 22:49:07 2012 Return-Path: X-Original-To: media-types@ietfa.amsl.com Delivered-To: media-types@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD7C821F8A9A for ; Wed, 12 Dec 2012 22:49:07 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.598 X-Spam-Level: X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 4LYna7x1jbT6 for ; Wed, 12 Dec 2012 22:49:07 -0800 (PST) Received: from pechora3.lax.icann.org (unknown [IPv6:2620:0:2d0:201::1:73]) by ietfa.amsl.com (Postfix) with ESMTP id 52F2721F8A77 for ; Wed, 12 Dec 2012 22:49:07 -0800 (PST) Received: from mail-ee0-f41.google.com (mail-ee0-f41.google.com [74.125.83.41]) by pechora3.lax.icann.org (8.13.8/8.13.8) with ESMTP id qBD6mk7H008853 for ; Thu, 13 Dec 2012 06:49:06 GMT Received: by mail-ee0-f41.google.com with SMTP id d41so1010329eek.28 for ; Wed, 12 Dec 2012 22:48:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; bh=ExPNAHEX2p7TriHovksjgCejADadICksLAsLhsV6mZs=; b=wDUSyyGG+luYrjjBIhitlHlLRCkLI/UD9VrZoB7IHV/I9wCc4Z2BoOrOFcXTGNSL4Z YqE+y+T9k6webjIjjESLxeFnsbci+awaam/yy69T0QF5ZpeTcedKzTW1uoYXwYCYQkzR vjI8IQ5fS885PFansqlWdPQIA9PU9u+1AicCWmXsg0hKHokICT/hyN07yMpKDK4yqBWp eAlGpNS6AGtZp0Vv/egRdZp+cg2JkZEtivX873ozTZS4IMc9JiZYeWmaU50AASC7qCdh RxMXJOnHIO6QQmKpKrmnCNPOqa0YIDenci67FGe3o04girwsygxSn1cl42rZZoAHP75n 8OKQ== Received: by 10.14.178.196 with SMTP id f44mr2469140eem.14.1355381325806; Wed, 12 Dec 2012 22:48:45 -0800 (PST) Received: from RoniE (bzq-79-176-185-176.red.bezeqint.net. [79.176.185.176]) by mx.google.com with ESMTPS id 6sm1161378eea.3.2012.12.12.22.48.43 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 12 Dec 2012 22:48:44 -0800 (PST) From: "Roni Even" To: Date: Thu, 13 Dec 2012 08:45:57 +0200 Message-ID: <005701cdd8fd$83ade6b0$8b09b410$@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0058_01CDD90E.4737C820" X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac3Y/VDIdS/QicjiQxCmDifr23qBVw== Content-Language: en-us X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora3.lax.icann.org [192.0.33.73]); Thu, 13 Dec 2012 06:49:07 +0000 (UTC) Cc: draft-ietf-avt-rtp-isac@tools.ietf.org, payload@ietf.org Subject: [media-types] registration of iSac media subtype X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Dec 2012 06:49:08 -0000 This is a multipart message in MIME format. ------=_NextPart_000_0058_01CDD90E.4737C820 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi, The iSac draft is currently in WGLC in the Payload WG http://tools.ietf.org/html/draft-ietf-avt-rtp-isac-02 the media type registration is in section 4 and also included below. Please review the registration. Thanks Roni Even Payload WG co-chair Media type name: audio Media subtype: isac Required parameters: None Optional parameters: * ibitrate: The parameter indicates the upper bound of the initial target bit rate the device would like to receive. For channel-adaptive mode, the target bit rate may vary with time; for channel-independent mode, the target bit rate will remain at that level unless instructed otherwise. An acceptable value for ibitrate is in the range of 20000 to 32000 (bits per second). * maxbitrate: The parameter indicates the maximum bit rate the endpoint expects to receive. The recipient of this parameter SHOULD NOT transmit at a higher bit rate. Encoding considerations: This media format is framed and binary. Security considerations: See Section 6 Interoperability considerations: None Published specification: RFC XXXX Applications which use this media type: This media type is suitable for use in numerous applications needing to transport encoded voice or other audio. Some examples include Voice over IP, Streaming Media, Voice Messaging, and Conferencing. Additional information: None Intended usage: COMMON Other Information/General Comment: iSAC is a proprietary speech and audio codec owned by Google. The codec operates on 30 or 60 ms speech frames at a sampling rate clock of 16 kHz or 32 kHz. Person to contact for further information: Tina le Grand [tlegrand@google.com] Restrictions on usage: This media type depends on RTP framing, and hence is only defined for transfer via RTP [2]. Transport within other framing protocols is not defined at this time. Change controller: IETF Audio/Video Transport working group delegated from the IESG. Note to the RFC Editor / IANA: Please replace "RFC XXXX" above with the number of this RFC when published, and remove this note. ------=_NextPart_000_0058_01CDD90E.4737C820 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

The iSac draft = is currently in WGLC in the Payload WG http://too= ls.ietf.org/html/draft-ietf-avt-rtp-isac-02

the media type registration is in section 4 and also = included below.

Please review the = registration.

 

Thanks

Roni Even =

Payload WG co-chair

 

   =

Media type name:   = audio

 

   Media subtype:   = isac

 

   Required parameters:  = None

 

   Optional parameters:

 

      *  ibitrate: The = parameter indicates the upper bound of the

         = initial target bit rate the device would like to receive.  = For

         = channel-adaptive mode, the target bit rate may vary with = time;

         for = channel-independent mode, the target bit rate will = remain

         at = that level unless instructed otherwise.  An acceptable = value

         for = ibitrate is in the range of 20000 to 32000 (bits per

         = second).

 

      *  maxbitrate: The = parameter indicates the maximum bit rate the

         = endpoint expects to receive.  The recipient of this = parameter

         = SHOULD NOT transmit at a higher bit rate.

 

   = Encoding considerations:

      This media format is = framed and binary.

 

   = Security considerations:  See Section 6

 

  =  Interoperability considerations:  None

 

   = Published specification:  RFC XXXX

 

   = Applications which use this media type:

      This media type is = suitable for use in numerous applications

      needing to transport = encoded voice or other audio.  Some examples

      include Voice over IP, = Streaming Media, Voice Messaging, and

      = Conferencing.

 

   Additional information:  = None

 

   Intended usage:  = COMMON

 

   Other Information/General = Comment:

      iSAC is a proprietary = speech and audio codec owned by Google.  The

      codec operates on 30 or = 60 ms speech frames at a sampling rate

      clock of 16 kHz or 32 = kHz.

 

   Person to contact for further = information:

      Tina le Grand = [tlegrand@google.com]

 

   = Restrictions on usage:

      This media type depends = on RTP framing, and hence is only defined

      for transfer via RTP = [2].  Transport within other framing

      protocols is not = defined at this time.

 

   = Change controller:

      IETF Audio/Video = Transport working group delegated from the IESG.

 

   = Note to the RFC Editor / IANA: Please replace "RFC XXXX" above = with

   the number of this = RFC when published, and remove this = note.

------=_NextPart_000_0058_01CDD90E.4737C820--