
From stpeter@stpeter.im  Mon Aug  8 12:28:29 2011
Return-Path: <stpeter@stpeter.im>
X-Original-To: w3c-policy@ietfa.amsl.com
Delivered-To: w3c-policy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1A8511E8082 for <w3c-policy@ietfa.amsl.com>; Mon,  8 Aug 2011 12:28:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.643
X-Spam-Level: 
X-Spam-Status: No, score=-102.643 tagged_above=-999 required=5 tests=[AWL=-0.044, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nawOQYSkxeEr for <w3c-policy@ietfa.amsl.com>; Mon,  8 Aug 2011 12:28:29 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 18F3C11E807F for <w3c-policy@apps.ietf.org>; Mon,  8 Aug 2011 12:28:29 -0700 (PDT)
Received: from dhcp-64-101-72-239.cisco.com (unknown [64.101.72.239]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id E3990413D9; Mon,  8 Aug 2011 13:30:29 -0600 (MDT)
Message-ID: <4E4038F5.7030705@stpeter.im>
Date: Mon, 08 Aug 2011 13:28:53 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Kazuyuki Ashimura <ashimura@w3.org>
Subject: Re: Requesting IESG Approval for the Media Type application/inkml+xml
References: <1308663218.27118.6.camel@chacal> <4E2081BC.9040304@stpeter.im> <4E3F1818.3070201@w3.org>
In-Reply-To: <4E3F1818.3070201@w3.org>
X-Enigmail-Version: 1.2
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Philippe Le Hegaret <plh@w3.org>, w3c-policy@apps.ietf.org, iesg <iesg@ietf.org>
X-BeenThere: w3c-policy@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Administration of the W3C/IETF liaison <w3c-policy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/w3c-policy>, <mailto:w3c-policy-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/w3c-policy>
List-Post: <mailto:w3c-policy@ietf.org>
List-Help: <mailto:w3c-policy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/w3c-policy>, <mailto:w3c-policy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2011 19:28:29 -0000

Thank you for the clarification!

On 8/7/11 4:56 PM, Kazuyuki Ashimura wrote:
> Dear Peter Saint-Andre,
> 
> I am very sorry for my late response.  It was vacation season and took
> a bit longer to check with the specification editors.
>  
> I have checked with the editors and clarified the following:
> 
> - The editor inadvertently used "instructions" here, but their actual
>   intention was simply that "InkML elements may include arbitrary
>   URIs".
> 
> - So we have to change the wording in the specification from
>   "instructions" to "elements" to clarify that InkML agents are not
>   language processors and arbitrary URI's will not be dereferenced.
> 
> I hope the above clarification works.
> 
> Thanks,
> 
> Kazuyuki
>  
> 
> On 07/16/2011 03:06 AM, Peter Saint-Andre wrote:
>> Hi Philippe,
>>
>> The security considerations portion of the media type registration
>> states that "several InkML instructions may cause arbitrary URIs to be
>> dereferenced". However, there are no examples of such URIs in the body
>> of the specification, nor is there a list of the instructions that might
>> cause this behavior (does this apply to all attributes with a datatype
>> of "anyUri"?). These small clarifications would be helpful.
>>
>> Peter
>>
>> On 6/21/11 7:33 AM, Philippe Le Hegaret wrote:
>>> Dear IESG participants,
>>>
>>> This message is to request approval for the registration of the media
>>> type:
>>>   application/inkml+xml
>>>   D.1 Registration of MIME media type application/inkml+xml
>>>   http://www.w3.org/TR/2011/PR-InkML-20110510/#media-type-registration
>>>
>>> This message follows the procedure described in the Media Type
>>> Specifications and Registration Procedures, section 5.2, "IESG
>>> Approval" [1]. The proposed media types were sent for preliminary
>>> community review on January 28, 2008:
>>>   http://www.alvestrand.no/pipermail/ietf-types/2008-January/001989.html
>>>
>>> No comments were received.
>>>
>>> We believe the media type is now ready for IESG approval.
>>>
>>> Thank you,
>>>
>>> Philippe
>>>
>>> [1] http://www.ietf.org/rfc/rfc4288.txt
>>>
>>
> 


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



From stpeter@stpeter.im  Tue Aug  9 13:35:55 2011
Return-Path: <stpeter@stpeter.im>
X-Original-To: w3c-policy@ietfa.amsl.com
Delivered-To: w3c-policy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 864A711E80F0 for <w3c-policy@ietfa.amsl.com>; Tue,  9 Aug 2011 13:35:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.639
X-Spam-Level: 
X-Spam-Status: No, score=-102.639 tagged_above=-999 required=5 tests=[AWL=-0.040, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id shzp1YYwn3fw for <w3c-policy@ietfa.amsl.com>; Tue,  9 Aug 2011 13:35:55 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 5783111E80E6 for <w3c-policy@apps.ietf.org>; Tue,  9 Aug 2011 13:35:55 -0700 (PDT)
Received: from dhcp-64-101-72-239.cisco.com (unknown [64.101.72.239]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 7811F413D9; Tue,  9 Aug 2011 14:30:37 -0600 (MDT)
Message-ID: <4E41988B.7090504@stpeter.im>
Date: Tue, 09 Aug 2011 14:28:59 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Kazuyuki Ashimura <ashimura@w3.org>
Subject: Re: Requesting IESG Approval for the Media Type application/inkml+xml
References: <1308663218.27118.6.camel@chacal> <4E2081BC.9040304@stpeter.im> <4E3F1818.3070201@w3.org> <4E4038F5.7030705@stpeter.im> <4E403A7B.8060805@w3.org>
In-Reply-To: <4E403A7B.8060805@w3.org>
X-Enigmail-Version: 1.2
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Philippe Le Hegaret <plh@w3.org>, w3c-policy@apps.ietf.org, iesg <iesg@ietf.org>
X-BeenThere: w3c-policy@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Administration of the W3C/IETF liaison <w3c-policy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/w3c-policy>, <mailto:w3c-policy-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/w3c-policy>
List-Post: <mailto:w3c-policy@ietf.org>
List-Help: <mailto:w3c-policy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/w3c-policy>, <mailto:w3c-policy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2011 20:35:55 -0000

I have asked the IANA to modify the registration request as follows:

OLD:
   Several InkML instructions may cause arbitrary URIs to be
   dereferenced.  In this case, the security issues of [RFC3986],
   section 7, should be considered.

NEW:
   InkML elements may include arbitrary URIs.  Therefore the
   security issues of [RFC3986], section 7, should be considered.

Please let me know if that is incorrect.

Peter

On 8/8/11 1:35 PM, Kazuyuki Ashimura wrote:
> Thank YOU so much for your prompt response, Peter!
> 
> Kazuyuki
> 
> 
> On 08/09/2011 04:28 AM, Peter Saint-Andre wrote:
>> Thank you for the clarification!
>>
>> On 8/7/11 4:56 PM, Kazuyuki Ashimura wrote:
>>> Dear Peter Saint-Andre,
>>>
>>> I am very sorry for my late response.  It was vacation season and took
>>> a bit longer to check with the specification editors.
>>>
>>> I have checked with the editors and clarified the following:
>>>
>>> - The editor inadvertently used "instructions" here, but their actual
>>>    intention was simply that "InkML elements may include arbitrary
>>>    URIs".
>>>
>>> - So we have to change the wording in the specification from
>>>    "instructions" to "elements" to clarify that InkML agents are not
>>>    language processors and arbitrary URI's will not be dereferenced.
>>>
>>> I hope the above clarification works.
>>>
>>> Thanks,
>>>
>>> Kazuyuki
>>>
>>>
>>> On 07/16/2011 03:06 AM, Peter Saint-Andre wrote:
>>>> Hi Philippe,
>>>>
>>>> The security considerations portion of the media type registration
>>>> states that "several InkML instructions may cause arbitrary URIs to be
>>>> dereferenced". However, there are no examples of such URIs in the body
>>>> of the specification, nor is there a list of the instructions that
>>>> might
>>>> cause this behavior (does this apply to all attributes with a datatype
>>>> of "anyUri"?). These small clarifications would be helpful.
>>>>
>>>> Peter
>>>>
>>>> On 6/21/11 7:33 AM, Philippe Le Hegaret wrote:
>>>>> Dear IESG participants,
>>>>>
>>>>> This message is to request approval for the registration of the media
>>>>> type:
>>>>>    application/inkml+xml
>>>>>    D.1 Registration of MIME media type application/inkml+xml
>>>>>   
>>>>> http://www.w3.org/TR/2011/PR-InkML-20110510/#media-type-registration
>>>>>
>>>>> This message follows the procedure described in the Media Type
>>>>> Specifications and Registration Procedures, section 5.2, "IESG
>>>>> Approval" [1]. The proposed media types were sent for preliminary
>>>>> community review on January 28, 2008:
>>>>>   
>>>>> http://www.alvestrand.no/pipermail/ietf-types/2008-January/001989.html
>>>>>
>>>>> No comments were received.
>>>>>
>>>>> We believe the media type is now ready for IESG approval.
>>>>>
>>>>> Thank you,
>>>>>
>>>>> Philippe
>>>>>
>>>>> [1] http://www.ietf.org/rfc/rfc4288.txt
>>>>>
>>>>
