From ietf-message-headers-bounces@ietf.org Thu Sep 27 08:06:18 2007
Return-path: <ietf-message-headers-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ias89-0005UP-WB; Thu, 27 Sep 2007 08:06:10 -0400
Received: from ietf-message-headers by megatron.ietf.org with local (Exim 4.43)
	id 1Ias89-0005UG-Cz
	for ietf-message-headers-confirm+ok@megatron.ietf.org;
	Thu, 27 Sep 2007 08:06:09 -0400
Received: from ietf-message-headers by megatron.ietf.org with local (Exim 4.43)
	id 1Ias89-0005TM-0Z
	for ietf-message-headers@lists.ietf.org; Thu, 27 Sep 2007 08:06:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IarwG-0003Fh-A2
	for ietf-message-headers@lists.ietf.org; Thu, 27 Sep 2007 07:53:52 -0400
Received: from sam.opera.com ([213.236.208.81])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Iarw9-0003Yr-Tn
	for ietf-message-headers@lists.ietf.org; Thu, 27 Sep 2007 07:53:52 -0400
Received: from annevk-t60.oslo.opera.com (c5144430c.cable.wanadoo.nl
	[81.68.67.12]) (authenticated bits=0)
	by sam.opera.com (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	l8RBrcXW008155
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT)
	for <ietf-message-headers@lists.ietf.org>; Thu, 27 Sep 2007 11:53:39 GMT
Date: Thu, 27 Sep 2007 13:53:40 +0200
To: ietf-message-headers@lists.ietf.org
From: "Anne van Kesteren" <annevk@opera.com>
Organization: Opera Software ASA
Content-Type: multipart/mixed; boundary=----------78YV1ita77pK5c7z83nEm3
MIME-Version: 1.0
Message-ID: <op.tza9zqen64w2qv@annevk-t60.oslo.opera.com>
User-Agent: Opera Mail/9.21 (Linux)
X-Virus-Scanned: ClamAV 0.91.1/4411/Wed Sep 26 21:43:35 2007 on sam.opera.com
X-Virus-Status: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
X-TMDA-Confirmed: Thu, 27 Sep 2007 08:06:08 -0400
Cc: 
Subject: [Ietf-message-headers] HTTP header registration question
X-BeenThere: ietf-message-headers@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Discussion list for header fields used in Internet messaging
	applications." <ietf-message-headers.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-message-headers>, 
	<mailto:ietf-message-headers-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-message-headers@ietf.org>
List-Help: <mailto:ietf-message-headers-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-message-headers>, 
	<mailto:ietf-message-headers-request@ietf.org?subject=subscribe>
Errors-To: ietf-message-headers-bounces@ietf.org

------------78YV1ita77pK5c7z83nEm3
Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8
Content-Transfer-Encoding: 7bit

Hi,

For a W3C specification "Enabling Read Access for Web Resources" the W3C  
WAF WG would like to register three HTTP headers: Access-Control,  
If-Method-Allowed, and Referer-Root (sic). Can I do that as attached or is  
it preferable to have three separate templates? Also, does the  
specification itself need to include anything that points back to the  
header registry, does it need to include the template, etc.? This did not  
became clear from reading RFC 	3864. Thanks for the information!

Kind regards,


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
------------78YV1ita77pK5c7z83nEm3
Content-Disposition: attachment; filename=header-field-registration.txt
Content-Type: text/plain; name=header-field-registration.txt
Content-Transfer-Encoding: 7bit

Header field names:
   Access-Control
   If-Method-Allowed
   Referer-Root (sic)

Applicable protocol:
   http

Status:
   standard

Author/Change controller:
   W3C

Specification documents:
   http://www.w3.org/TR/access-control/ (Working Draft)
   http://dev.w3.org/2006/waf/access-control/Overview.html (Editor draft)

Related information:
   The editor draft currently includes all headers. The working draft has
   not yet been republished to reflect this.


------------78YV1ita77pK5c7z83nEm3
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Ietf-message-headers mailing list
Ietf-message-headers@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-message-headers

------------78YV1ita77pK5c7z83nEm3--







From ietf-message-headers-bounces@ietf.org Thu Sep 27 18:38:44 2007
Return-path: <ietf-message-headers-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ib20A-0006Ng-T7; Thu, 27 Sep 2007 18:38:34 -0400
Received: from ietf-message-headers by megatron.ietf.org with local (Exim 4.43)
	id 1Ib209-0006Ew-EM
	for ietf-message-headers-confirm+ok@megatron.ietf.org;
	Thu, 27 Sep 2007 18:38:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ib209-0005zk-2q
	for ietf-message-headers@lists.ietf.org; Thu, 27 Sep 2007 18:38:33 -0400
Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ib1zy-0004MT-S6
	for ietf-message-headers@lists.ietf.org; Thu, 27 Sep 2007 18:38:29 -0400
Received: from list by ciao.gmane.org with local (Exim 4.43)
	id 1Ib1zc-0007Ij-6D
	for ietf-message-headers@lists.ietf.org; Thu, 27 Sep 2007 22:38:00 +0000
Received: from 1cust133.tnt2.hbg2.deu.da.uu.net ([149.225.12.133])
	by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00 for <ietf-message-headers@lists.ietf.org>;
	Thu, 27 Sep 2007 22:38:00 +0000
Received: from nobody by 1cust133.tnt2.hbg2.deu.da.uu.net with local (Gmexim
	0.1 (Debian)) id 1AlnuQ-0007hv-00
	for <ietf-message-headers@lists.ietf.org>;
	Thu, 27 Sep 2007 22:38:00 +0000
X-Injected-Via-Gmane: http://gmane.org/
To: ietf-message-headers@lists.ietf.org
From: "Frank Ellermann" <nobody@xyzzy.claranet.de>
Date: Fri, 28 Sep 2007 00:37:35 +0200
Organization: http://purl.net/xyzzy
Lines: 39
Message-ID: <fdhbc1$s2n$1@sea.gmane.org>
References: <op.tza9zqen64w2qv@annevk-t60.oslo.opera.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Complaints-To: usenet@sea.gmane.org
X-Gmane-NNTP-Posting-Host: 1cust133.tnt2.hbg2.deu.da.uu.net
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1807
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1896
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: 
Subject: [Ietf-message-headers] Re: HTTP header registration question
X-BeenThere: ietf-message-headers@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Discussion list for header fields used in Internet messaging
	applications." <ietf-message-headers.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-message-headers>, 
	<mailto:ietf-message-headers-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-message-headers@ietf.org>
List-Help: <mailto:ietf-message-headers-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-message-headers>, 
	<mailto:ietf-message-headers-request@ietf.org?subject=subscribe>
Errors-To: ietf-message-headers-bounces@ietf.org

Anne van Kesteren wrote:
 =20
> three HTTP headers: Access-Control, If-Method-Allowed, and=20
> Referer-Root (sic). Can I do that as attached or is it=20
> preferable to have three separate templates?

The given specification apparently only covers Access-Control
in an "Editor Draft".  Do you plan to add the other two later
in your draft ?

Maybe use three separate templates for the submission to IANA,
after the two weeks review here, less chances that something
goes wrong. =20

For status: standard you have to wait until the specification
actually is a W3C standard.  You could use status: provisional
before, and later send an update to IANA when it's a standard.

> Also, does the specification itself need to include anything
> that points back to the header registry

No.

> does it need to include the template, etc.?

Of course it can, but that's more interesting for IETF RFCs:

IANA has a seat in the IESG, and can so check what they're
supposed to do before an IETF RFC is approved by the IESG.

BTW, your draft uses the ugly RFC 2616 "LWS" construct.
Maybe check with the 2616bis folks what they intend to do
with "LWS".  The 2616bis list is ietf-http-wg @ w3.org=20

 Frank=20

(I like your text/xml flame, Olivier hit me with it on the
 validator list ;-)




_______________________________________________
Ietf-message-headers mailing list
Ietf-message-headers@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-message-headers



From ietf-message-headers-bounces@ietf.org Fri Sep 28 05:59:26 2007
Return-path: <ietf-message-headers-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IbCct-0006HC-Gs; Fri, 28 Sep 2007 05:59:15 -0400
Received: from ietf-message-headers by megatron.ietf.org with local (Exim 4.43)
	id 1IbCcs-0006Gr-IV
	for ietf-message-headers-confirm+ok@megatron.ietf.org;
	Fri, 28 Sep 2007 05:59:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IbCcs-0006GX-8b
	for ietf-message-headers@lists.ietf.org; Fri, 28 Sep 2007 05:59:14 -0400
Received: from sam.opera.com ([213.236.208.81])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IbCcl-00039N-TY
	for ietf-message-headers@lists.ietf.org; Fri, 28 Sep 2007 05:59:14 -0400
Received: from annevk-t60.oslo.opera.com (c5144430c.cable.wanadoo.nl
	[81.68.67.12]) (authenticated bits=0)
	by sam.opera.com (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	l8S9wtCj005744
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT)
	for <ietf-message-headers@lists.ietf.org>; Fri, 28 Sep 2007 09:58:56 GMT
Date: Fri, 28 Sep 2007 11:58:54 +0200
To: ietf-message-headers@lists.ietf.org
Subject: Re: [Ietf-message-headers] Re: HTTP header registration question
From: "Anne van Kesteren" <annevk@opera.com>
Organization: Opera Software ASA
Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8
MIME-Version: 1.0
References: <op.tza9zqen64w2qv@annevk-t60.oslo.opera.com>
	<fdhbc1$s2n$1@sea.gmane.org>
Content-Transfer-Encoding: 7bit
Message-ID: <op.tzczcggc64w2qv@annevk-t60.oslo.opera.com>
In-Reply-To: <fdhbc1$s2n$1@sea.gmane.org>
User-Agent: Opera Mail/9.21 (Linux)
X-Virus-Scanned: ClamAV 0.91.1/4419/Fri Sep 28 07:36:28 2007 on sam.opera.com
X-Virus-Status: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: 
X-BeenThere: ietf-message-headers@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Discussion list for header fields used in Internet messaging
	applications." <ietf-message-headers.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-message-headers>, 
	<mailto:ietf-message-headers-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-message-headers@ietf.org>
List-Help: <mailto:ietf-message-headers-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-message-headers>, 
	<mailto:ietf-message-headers-request@ietf.org?subject=subscribe>
Errors-To: ietf-message-headers-bounces@ietf.org

On Fri, 28 Sep 2007 00:37:35 +0200, Frank Ellermann  
<nobody@xyzzy.claranet.de> wrote:
> Anne van Kesteren wrote:
>
>> three HTTP headers: Access-Control, If-Method-Allowed, and
>> Referer-Root (sic). Can I do that as attached or is it
>> preferable to have three separate templates?
>
> The given specification apparently only covers Access-Control
> in an "Editor Draft".  Do you plan to add the other two later
> in your draft ?

The other two are both mentioned and it's defined what they are to  
contain. (They are request headers.) Maybe they should have syntax  
definitions as well just to make it complete.


> BTW, your draft uses the ugly RFC 2616 "LWS" construct.
> Maybe check with the 2616bis folks what they intend to do
> with "LWS".  The 2616bis list is ietf-http-wg @ w3.org

Once they publish something new, the specification can be revised I  
suppose.


> (I like your text/xml flame, Olivier hit me with it on the
>  validator list ;-)

More recently I've become of the opinion that a much more pragmatic  
solution would be to simply treat text/xml identical to application/xml as  
all browsers already do.


(I'll use "provisional" by the way, thanks.)


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>


_______________________________________________
Ietf-message-headers mailing list
Ietf-message-headers@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-message-headers



From ietf-message-headers-bounces@ietf.org Fri Sep 28 06:57:24 2007
Return-path: <ietf-message-headers-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IbDWo-0003u5-U8; Fri, 28 Sep 2007 06:57:02 -0400
Received: from ietf-message-headers by megatron.ietf.org with local (Exim 4.43)
	id 1IbDWn-0003sK-Kg
	for ietf-message-headers-confirm+ok@megatron.ietf.org;
	Fri, 28 Sep 2007 06:57:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IbDWn-0003nH-BD
	for ietf-message-headers@lists.ietf.org; Fri, 28 Sep 2007 06:57:01 -0400
Received: from scmailgw1.scop.aoyama.ac.jp ([133.2.251.194])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IbDWc-0004VW-Qu
	for ietf-message-headers@lists.ietf.org; Fri, 28 Sep 2007 06:56:57 -0400
Received: from scmse1.scbb.aoyama.ac.jp (scmse1 [133.2.253.16])
	by scmailgw1.scop.aoyama.ac.jp (secret/secret) with SMTP id
	l8SAtuwR013461 for <ietf-message-headers@lists.ietf.org>;
	Fri, 28 Sep 2007 19:56:00 +0900 (JST)
Received: from (133.2.206.133) by scmse1.scbb.aoyama.ac.jp via smtp
	id 19b3_63efed3a_6db1_11dc_9d3b_0014221fa3c9;
	Fri, 28 Sep 2007 19:55:56 +0900
X-AuthUser: duerst@it.aoyama.ac.jp
Received: from Tanzawa.it.aoyama.ac.jp ([133.2.210.1]:53348)
	by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server]
	id <S15A0B0> for <ietf-message-headers@lists.ietf.org> from
	<duerst@it.aoyama.ac.jp>; Fri, 28 Sep 2007 19:52:39 +0900
Message-Id: <6.0.0.20.2.20070928194301.0383ab30@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Version 6J
Date: Fri, 28 Sep 2007 19:52:45 +0900
To: "Anne van Kesteren" <annevk@opera.com>, ietf-message-headers@lists.ietf.org
From: Martin Duerst <duerst@it.aoyama.ac.jp>
Subject: Re: [Ietf-message-headers] HTTP header registration question
In-Reply-To: <op.tza9zqen64w2qv@annevk-t60.oslo.opera.com>
References: <op.tza9zqen64w2qv@annevk-t60.oslo.opera.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: 
X-BeenThere: ietf-message-headers@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Discussion list for header fields used in Internet messaging
	applications." <ietf-message-headers.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-message-headers>, 
	<mailto:ietf-message-headers-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-message-headers@ietf.org>
List-Help: <mailto:ietf-message-headers-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-message-headers>, 
	<mailto:ietf-message-headers-request@ietf.org?subject=subscribe>
Errors-To: ietf-message-headers-bounces@ietf.org

Hello Anne,

I have some comments about the document at
http://dev.w3.org/2006/waf/access-control/Overview.html.

First, the title is not easy to understand for people who
aren't totally immersed in the Ajax business. Most Web
Resources are, almost by definition, read accessible.

I'd suggest a title like "Enabling Cross-Domain Read
Access for Web Resources".

I don't understand the sentence:
>>>>
XML resources may include an <?access-control?> processing instruction within the XML Prolog to indicate in cases where the access control read policy applies from which domains they can be fetched. [XML]
>>>>

First, the [XML] reference at the end looks totally out of context.
I know that some style guides say that references should be at the
end of a sentence, but this one is really unreadable. More important,
"in cases where" doesn't make sense.

The only way for me to understand this sentence is that the PI is
interpreted on the server side, before the document is (or actually
is not) sent, but experience with in-document information for server
side has been detrimental (nobody wants to take that performance hit),
so I highly advise against this. If the PI is supposed to apply
client-side, the the above sentence needs heavy rewriting.
Checking whether a document can be downloaded once it's already
downloaded is of course nonsense.

Another point that I don't understand is that the TO-ASCII algorithm
of RFC 3490 is mentioned several times, but the syntax only allows
RFC 3986 URIs or RFC 1034 labels. TO-ASCII only makes sense if you
start with an Unicode string, but RFC 3986 and RFC 1034 are pure
ASCII already. I think it would be good to allow IDNs, but you actually
have to say so.

Regards,    Martin.

At 20:53 07/09/27, Anne van Kesteren wrote:
>Hi,
>
>For a W3C specification "Enabling Read Access for Web Resources" the W3C  
>WAF WG would like to register three HTTP headers: Access-Control,  
>If-Method-Allowed, and Referer-Root (sic). Can I do that as attached or is  
>it preferable to have three separate templates? Also, does the  
>specification itself need to include anything that points back to the  
>header registry, does it need to include the template, etc.? This did not  
>became clear from reading RFC  3864. Thanks for the information!
>
>Kind regards,
>
>
>-- 
>Anne van Kesteren
><http://annevankesteren.nl/>
><http://www.opera.com/>
>
>
>_______________________________________________
>Ietf-message-headers mailing list
>Ietf-message-headers@ietf.org
>https://www1.ietf.org/mailman/listinfo/ietf-message-headers


#-#-#  Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
#-#-#  http://www.sw.it.aoyama.ac.jp       mailto:duerst@it.aoyama.ac.jp     



_______________________________________________
Ietf-message-headers mailing list
Ietf-message-headers@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-message-headers



From ietf-message-headers-bounces@ietf.org Fri Sep 28 07:16:16 2007
Return-path: <ietf-message-headers-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IbDpB-0003Sg-1m; Fri, 28 Sep 2007 07:16:01 -0400
Received: from ietf-message-headers by megatron.ietf.org with local (Exim 4.43)
	id 1IbDp9-0003Pa-B7
	for ietf-message-headers-confirm+ok@megatron.ietf.org;
	Fri, 28 Sep 2007 07:15:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IbDp9-0003LN-0P
	for ietf-message-headers@lists.ietf.org; Fri, 28 Sep 2007 07:15:59 -0400
Received: from sam.opera.com ([213.236.208.81])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IbDow-0004zc-FU
	for ietf-message-headers@lists.ietf.org; Fri, 28 Sep 2007 07:15:53 -0400
Received: from annevk-t60.oslo.opera.com (c5144430c.cable.wanadoo.nl
	[81.68.67.12]) (authenticated bits=0)
	by sam.opera.com (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	l8SBFMYm008466
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Fri, 28 Sep 2007 11:15:23 GMT
Date: Fri, 28 Sep 2007 13:15:22 +0200
To: "Martin Duerst" <duerst@it.aoyama.ac.jp>,
	ietf-message-headers@lists.ietf.org
Subject: Re: [Ietf-message-headers] HTTP header registration question
From: "Anne van Kesteren" <annevk@opera.com>
Organization: Opera Software ASA
Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8
MIME-Version: 1.0
References: <op.tza9zqen64w2qv@annevk-t60.oslo.opera.com>
	<6.0.0.20.2.20070928194301.0383ab30@localhost>
Content-Transfer-Encoding: 7bit
Message-ID: <op.tzc2vw0i64w2qv@annevk-t60.oslo.opera.com>
In-Reply-To: <6.0.0.20.2.20070928194301.0383ab30@localhost>
User-Agent: Opera Mail/9.21 (Linux)
X-Virus-Scanned: ClamAV 0.91.1/4419/Fri Sep 28 07:36:28 2007 on sam.opera.com
X-Virus-Status: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: 
X-BeenThere: ietf-message-headers@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Discussion list for header fields used in Internet messaging
	applications." <ietf-message-headers.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-message-headers>, 
	<mailto:ietf-message-headers-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-message-headers@ietf.org>
List-Help: <mailto:ietf-message-headers-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-message-headers>, 
	<mailto:ietf-message-headers-request@ietf.org?subject=subscribe>
Errors-To: ietf-message-headers-bounces@ietf.org

On Fri, 28 Sep 2007 12:52:45 +0200, Martin Duerst <duerst@it.aoyama.ac.jp>  
wrote:
> I have some comments about the document at
> http://dev.w3.org/2006/waf/access-control/Overview.html.
>
> First, the title is not easy to understand for people who
> aren't totally immersed in the Ajax business. Most Web
> Resources are, almost by definition, read accessible.
>
> I'd suggest a title like "Enabling Cross-Domain Read
> Access for Web Resources".

I think this would cause conflicts for people who want to use it in other  
contexts, but I personally agree with this. Maybe raise this on  
public-appformats@w3.org so other people can give input?


> I don't understand the sentence:
>>>>>
> XML resources may include an <?access-control?> processing instruction  
> within the XML Prolog to indicate in cases where the access control read  
> policy applies from which domains they can be fetched. [XML]
>>>>>
>
> First, the [XML] reference at the end looks totally out of context.
> I know that some style guides say that references should be at the
> end of a sentence, but this one is really unreadable. More important,
> "in cases where" doesn't make sense.

That should be replaced with "if" probably. And some punctation around it.  
I just made that change.


> The only way for me to understand this sentence is that the PI is
> interpreted on the server side, before the document is (or actually
> is not) sent, but experience with in-document information for server
> side has been detrimental (nobody wants to take that performance hit),
> so I highly advise against this. If the PI is supposed to apply
> client-side, the the above sentence needs heavy rewriting.
> Checking whether a document can be downloaded once it's already
> downloaded is of course nonsense.

Good point. Replaced "they can be fetched" with "their content can be  
accessed".


> Another point that I don't understand is that the TO-ASCII algorithm
> of RFC 3490 is mentioned several times, but the syntax only allows
> RFC 3986 URIs or RFC 1034 labels. TO-ASCII only makes sense if you
> start with an Unicode string, but RFC 3986 and RFC 1034 are pure
> ASCII already. I think it would be good to allow IDNs, but you actually
> have to say so.

I couldn't find definitions of "subdomain" and "label" elsewhere. And it  
seems that RFC 1034 doesn't actually restrict IDN usage, but I could be  
mistaken. If you have suggestions on how to improve this they are most  
welcome (on any list).


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>


_______________________________________________
Ietf-message-headers mailing list
Ietf-message-headers@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-message-headers



From ietf-message-headers-bounces@ietf.org Fri Sep 28 11:01:25 2007
Return-path: <ietf-message-headers-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IbHL9-0003Ty-5i; Fri, 28 Sep 2007 11:01:15 -0400
Received: from ietf-message-headers by megatron.ietf.org with local (Exim 4.43)
	id 1IbHL7-0003P5-PW
	for ietf-message-headers-confirm+ok@megatron.ietf.org;
	Fri, 28 Sep 2007 11:01:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IbHL7-0003Km-F8
	for ietf-message-headers@lists.ietf.org; Fri, 28 Sep 2007 11:01:13 -0400
Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IbHKw-00028O-8F
	for ietf-message-headers@lists.ietf.org; Fri, 28 Sep 2007 11:01:08 -0400
Received: from list by ciao.gmane.org with local (Exim 4.43)
	id 1IbHKX-0008Ub-Ei
	for ietf-message-headers@lists.ietf.org; Fri, 28 Sep 2007 15:00:37 +0000
Received: from 1cust91.tnt1.hbg2.deu.da.uu.net ([149.225.10.91])
	by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00 for <ietf-message-headers@lists.ietf.org>;
	Fri, 28 Sep 2007 15:00:37 +0000
Received: from nobody by 1cust91.tnt1.hbg2.deu.da.uu.net with local (Gmexim
	0.1 (Debian)) id 1AlnuQ-0007hv-00
	for <ietf-message-headers@lists.ietf.org>;
	Fri, 28 Sep 2007 15:00:37 +0000
X-Injected-Via-Gmane: http://gmane.org/
To: ietf-message-headers@lists.ietf.org
From: "Frank Ellermann" <nobody@xyzzy.claranet.de>
Date: Fri, 28 Sep 2007 17:00:01 +0200
Organization: http://purl.net/xyzzy
Lines: 10
Message-ID: <fdj4u5$q45$1@sea.gmane.org>
References: <op.tza9zqen64w2qv@annevk-t60.oslo.opera.com><6.0.0.20.2.20070928194301.0383ab30@localhost>
	<op.tzc2vw0i64w2qv@annevk-t60.oslo.opera.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Complaints-To: usenet@sea.gmane.org
X-Gmane-NNTP-Posting-Host: 1cust91.tnt1.hbg2.deu.da.uu.net
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1807
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1896
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Cc: 
Subject: [Ietf-message-headers] Re: HTTP header registration question
X-BeenThere: ietf-message-headers@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Discussion list for header fields used in Internet messaging
	applications." <ietf-message-headers.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-message-headers>, 
	<mailto:ietf-message-headers-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-message-headers@ietf.org>
List-Help: <mailto:ietf-message-headers-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-message-headers>, 
	<mailto:ietf-message-headers-request@ietf.org?subject=subscribe>
Errors-To: ietf-message-headers-bounces@ietf.org

Anne van Kesteren wrote:

> I couldn't find definitions of "subdomain" and "label" elsewhere.

http://tools.ietf.org/html/rfc3696 (+ errata) is a nice intro, what
you want are "LDH" (letter-digit-hyphen) labels permitted in "host"
names, not labels containing arbitrary octets.

 Frank
 



_______________________________________________
Ietf-message-headers mailing list
Ietf-message-headers@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-message-headers



From ietf-message-headers-bounces@ietf.org Sat Sep 29 05:59:28 2007
Return-path: <ietf-message-headers-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IbZ6C-0002bh-Ae; Sat, 29 Sep 2007 05:59:00 -0400
Received: from ietf-message-headers by megatron.ietf.org with local (Exim 4.43)
	id 1IbZ6B-0002bc-56
	for ietf-message-headers-confirm+ok@megatron.ietf.org;
	Sat, 29 Sep 2007 05:58:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IbZ6A-0002ac-Ru
	for ietf-message-headers@lists.ietf.org; Sat, 29 Sep 2007 05:58:58 -0400
Received: from sam.opera.com ([213.236.208.81])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IbZ5u-0005IG-Gz
	for ietf-message-headers@lists.ietf.org; Sat, 29 Sep 2007 05:58:48 -0400
Received: from annevk-t60.oslo.opera.com (c5144430c.cable.wanadoo.nl
	[81.68.67.12]) (authenticated bits=0)
	by sam.opera.com (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
	l8T9wP2O001946
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT)
	for <ietf-message-headers@lists.ietf.org>; Sat, 29 Sep 2007 09:58:26 GMT
Date: Sat, 29 Sep 2007 11:58:25 +0200
To: ietf-message-headers@lists.ietf.org
Subject: Re: [Ietf-message-headers] Re: HTTP header registration question
From: "Anne van Kesteren" <annevk@opera.com>
Organization: Opera Software ASA
Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8
MIME-Version: 1.0
References: <op.tza9zqen64w2qv@annevk-t60.oslo.opera.com>
	<6.0.0.20.2.20070928194301.0383ab30@localhost>
	<op.tzc2vw0i64w2qv@annevk-t60.oslo.opera.com>
	<fdj4u5$q45$1@sea.gmane.org>
Content-Transfer-Encoding: 7bit
Message-ID: <op.tzetzn2l64w2qv@annevk-t60.oslo.opera.com>
In-Reply-To: <fdj4u5$q45$1@sea.gmane.org>
User-Agent: Opera Mail/9.21 (Linux)
X-Virus-Scanned: ClamAV 0.91.1/4429/Sat Sep 29 06:49:25 2007 on sam.opera.com
X-Virus-Status: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: 
X-BeenThere: ietf-message-headers@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Discussion list for header fields used in Internet messaging
	applications." <ietf-message-headers.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-message-headers>, 
	<mailto:ietf-message-headers-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-message-headers@ietf.org>
List-Help: <mailto:ietf-message-headers-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-message-headers>, 
	<mailto:ietf-message-headers-request@ietf.org?subject=subscribe>
Errors-To: ietf-message-headers-bounces@ietf.org

On Fri, 28 Sep 2007 17:00:01 +0200, Frank Ellermann  
<nobody@xyzzy.claranet.de> wrote:
> Anne van Kesteren wrote:
>
>> I couldn't find definitions of "subdomain" and "label" elsewhere.
>
> http://tools.ietf.org/html/rfc3696 (+ errata) is a nice intro, what
> you want are "LDH" (letter-digit-hyphen) labels permitted in "host"
> names, not labels containing arbitrary octets.

I'm not sure that RFC helps as it's informational only. Would using  
ireg-name be appropriate? (We do not want to allow IP addresses for now.)


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>


_______________________________________________
Ietf-message-headers mailing list
Ietf-message-headers@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-message-headers



From ietf-message-headers-bounces@ietf.org Sat Sep 29 06:34:14 2007
Return-path: <ietf-message-headers-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IbZdz-0004gu-8w; Sat, 29 Sep 2007 06:33:55 -0400
Received: from ietf-message-headers by megatron.ietf.org with local (Exim 4.43)
	id 1IbZdx-0004gH-Pb
	for ietf-message-headers-confirm+ok@megatron.ietf.org;
	Sat, 29 Sep 2007 06:33:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IbZdx-0004dH-Fm
	for ietf-message-headers@lists.ietf.org; Sat, 29 Sep 2007 06:33:53 -0400
Received: from scmailgw2.scop.aoyama.ac.jp ([133.2.251.195])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IbZdk-0006Ic-Kg
	for ietf-message-headers@lists.ietf.org; Sat, 29 Sep 2007 06:33:47 -0400
Received: from scmse2.scbb.aoyama.ac.jp (scmse2 [133.2.253.17])
	by scmailgw2.scop.aoyama.ac.jp (secret/secret) with SMTP id
	l8TAWkCS008091 for <ietf-message-headers@lists.ietf.org>;
	Sat, 29 Sep 2007 19:32:50 +0900 (JST)
Received: from (133.2.206.133) by scmse2.scbb.aoyama.ac.jp via smtp
	id 634a_5161391e_6e77_11dc_9a69_0014221f2a2d;
	Sat, 29 Sep 2007 19:32:45 +0900
X-AuthUser: duerst@it.aoyama.ac.jp
Received: from Tanzawa.it.aoyama.ac.jp ([133.2.210.1]:57087)
	by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server]
	id <S15BDF9> for <ietf-message-headers@lists.ietf.org> from
	<duerst@it.aoyama.ac.jp>; Sat, 29 Sep 2007 19:29:27 +0900
Message-Id: <6.0.0.20.2.20070929192836.0bb84270@localhost>
X-Sender: duerst@localhost
X-Mailer: QUALCOMM Windows Eudora Version 6J
Date: Sat, 29 Sep 2007 19:31:54 +0900
To: "Anne van Kesteren" <annevk@opera.com>, ietf-message-headers@lists.ietf.org
From: Martin Duerst <duerst@it.aoyama.ac.jp>
Subject: Re: [Ietf-message-headers] Re: HTTP header registration
  question
In-Reply-To: <op.tzetzn2l64w2qv@annevk-t60.oslo.opera.com>
References: <op.tza9zqen64w2qv@annevk-t60.oslo.opera.com>
	<6.0.0.20.2.20070928194301.0383ab30@localhost>
	<op.tzc2vw0i64w2qv@annevk-t60.oslo.opera.com>
	<fdj4u5$q45$1@sea.gmane.org>
	<op.tzetzn2l64w2qv@annevk-t60.oslo.opera.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: 
X-BeenThere: ietf-message-headers@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Discussion list for header fields used in Internet messaging
	applications." <ietf-message-headers.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-message-headers>, 
	<mailto:ietf-message-headers-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-message-headers@ietf.org>
List-Help: <mailto:ietf-message-headers-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-message-headers>, 
	<mailto:ietf-message-headers-request@ietf.org?subject=subscribe>
Errors-To: ietf-message-headers-bounces@ietf.org

At 18:58 07/09/29, Anne van Kesteren wrote:
>On Fri, 28 Sep 2007 17:00:01 +0200, Frank Ellermann  
><nobody@xyzzy.claranet.de> wrote:
>> Anne van Kesteren wrote:
>>
>>> I couldn't find definitions of "subdomain" and "label" elsewhere.
>>
>> http://tools.ietf.org/html/rfc3696 (+ errata) is a nice intro, what
>> you want are "LDH" (letter-digit-hyphen) labels permitted in "host"
>> names, not labels containing arbitrary octets.
>
>I'm not sure that RFC helps as it's informational only. Would using  
>ireg-name be appropriate? (We do not want to allow IP addresses for now.)

ireg-name doesn't cut up the name into labels, because it is intended
(similar to reg-name in RFC 3986) to cover other registries than just
the DNS, if and when these would be used in new schemes.

I suggest that you look at the IDNA RFCs if you want to get a definition
of a label including non-ASCII characters. IDNA definitely deals with
individual labels, because that's where punicode and the xn-- prefix
and all that stuff happen.

Regards,    Martin.s



#-#-#  Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
#-#-#  http://www.sw.it.aoyama.ac.jp       mailto:duerst@it.aoyama.ac.jp     



_______________________________________________
Ietf-message-headers mailing list
Ietf-message-headers@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-message-headers



From ietf-message-headers-bounces@ietf.org Sat Sep 29 06:50:45 2007
Return-path: <ietf-message-headers-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IbZuC-0002J9-DI; Sat, 29 Sep 2007 06:50:40 -0400
Received: from ietf-message-headers by megatron.ietf.org with local (Exim 4.43)
	id 1IbZuB-0002Iy-B9
	for ietf-message-headers-confirm+ok@megatron.ietf.org;
	Sat, 29 Sep 2007 06:50:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IbZuB-0002I5-1R
	for ietf-message-headers@lists.ietf.org; Sat, 29 Sep 2007 06:50:39 -0400
Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IbZu1-0006mO-Ou
	for ietf-message-headers@lists.ietf.org; Sat, 29 Sep 2007 06:50:35 -0400
Received: from list by ciao.gmane.org with local (Exim 4.43)
	id 1IbZtc-0007W2-RA
	for ietf-message-headers@lists.ietf.org; Sat, 29 Sep 2007 10:50:04 +0000
Received: from 1cust117.tnt1.hbg2.deu.da.uu.net ([149.225.10.117])
	by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00 for <ietf-message-headers@lists.ietf.org>;
	Sat, 29 Sep 2007 10:50:04 +0000
Received: from nobody by 1cust117.tnt1.hbg2.deu.da.uu.net with local (Gmexim
	0.1 (Debian)) id 1AlnuQ-0007hv-00
	for <ietf-message-headers@lists.ietf.org>;
	Sat, 29 Sep 2007 10:50:04 +0000
X-Injected-Via-Gmane: http://gmane.org/
To: ietf-message-headers@lists.ietf.org
From: "Frank Ellermann" <nobody@xyzzy.claranet.de>
Date: Sat, 29 Sep 2007 12:49:17 +0200
Organization: http://purl.net/xyzzy
Lines: 17
Message-ID: <fdlak2$dd7$1@sea.gmane.org>
References: <op.tza9zqen64w2qv@annevk-t60.oslo.opera.com><6.0.0.20.2.20070928194301.0383ab30@localhost><op.tzc2vw0i64w2qv@annevk-t60.oslo.opera.com><fdj4u5$q45$1@sea.gmane.org>
	<op.tzetzn2l64w2qv@annevk-t60.oslo.opera.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Complaints-To: usenet@sea.gmane.org
X-Gmane-NNTP-Posting-Host: 1cust117.tnt1.hbg2.deu.da.uu.net
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1807
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1896
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: 
Subject: [Ietf-message-headers] Re: HTTP header registration question
X-BeenThere: ietf-message-headers@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Discussion list for header fields used in Internet messaging
	applications." <ietf-message-headers.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-message-headers>, 
	<mailto:ietf-message-headers-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-message-headers@ietf.org>
List-Help: <mailto:ietf-message-headers-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-message-headers>, 
	<mailto:ietf-message-headers-request@ietf.org?subject=subscribe>
Errors-To: ietf-message-headers-bounces@ietf.org

Anne van Kesteren wrote:
=20
> Would using ireg-name be appropriate?

If you'd want IRIs excluding domain-literals.

But your draft is about HTTP, isn't it ?
For HTTP you need URIs, or RFC 3986 reg-name,
not RFC 3987 ireg-name. =20

An HTTP header uses Latin-1.  You could say
that clients are supposed to translate an
ireg-name into a reg-name as explained in
RFC 3987 3.1, that would be IDNA punycode,
not simply percent-encoded UTF-8.

 Frank



_______________________________________________
Ietf-message-headers mailing list
Ietf-message-headers@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-message-headers



