Anne van Kesteren | 8 Oct 11:44
Favicon
Gravatar

Provisional registration of Access Control for Cross-Site Requests headers

Hi,

Here is the registration template (inlined) for headers the W3C Web  
Applications WG would like to provisionally register. (Previously the W3C  
Web Application Formats WG worked on this draft.)

Since last time the header names have changed and some headers have been  
removed and added, but the overall idea is still the same.

===
Header field names:
Access-Control-Allow-Origin (response header)
Access-Control-Max-Age (response header)
Access-Control-Allow-Credentials (response header)
Access-Control-Allow-Methods (response header)
Access-Control-Allow-Headers (response header)
Origin (request header)
Access-Control-Request-Method (request header)
Access-Control-Request-Headers (request header)

Applicable protocol:
http

Status:
provisional

Author/Change controller:
W3C Web Applications Working Group
http://www.w3.org/2008/webapps/

(Continue reading)

Julian Reschke | 25 Sep 12:12

Re: Method-Check-Max-Age

AvK wrote back in January:

 > Based on feedback we renamed Method-Check-Expires to
 > Method-Check-Max-Age and instead of an HTTP-date it now takes
 > delta-seconds (RFC 2616).
 >
 >   http://dev.w3.org/2006/waf/access-control/
 >
 >
 > Can I simply e-mail IANA with this update or shall we go for
 > another two weeks review here? I'm good either way :-)

If headers that we previously registered aren't needed anymore, then 
yes, you should tell IANA about it so that the registry can be cleaned 
up (<http://tools.ietf.org/html/rfc3864#section-4.5>).

BR, Julian

Confirm: ietf-message-headers <at> ietf.org:E1K3a4SMN-TQ:cmkjCsL44v9hyZDv4PIeZCd9nXbcItp3bfb3kQ


Confirmation of list posting -- confirmation ID: E1K3a4SMN-TQ

The ietf.org mailing-list server has received a list posting from 
gim-ietf-message-headers <at> m.gmane.org to ietf-message-headers <at> ietf.org with the subject 
'Re: For review: Original-Recipient'

As the sender address isn't subscribed to the list, and has not been
confirmed earlier, we have to request a confirmation of the address.
To confirm the address, send a message to ietf-message-headers <at> ietf.org,
with the same subject line as this message.

(Simply sending a 'reply' to this message should work from most email
interfaces, since that usually leaves the subject line in the right
form.  The reply's additional "Re:" is ok.)

If you do not wish your posting to the list to go through, simply
disregard this message.  Questions to postmaster <at> ietf.org.

Pete Resnick | 10 Jul 02:34

Auto-Submitted

Header field name: Auto-Submitted
Applicable protocol: mail
Status: standard
Author/Change controller: IETF
Specification document: RFC 3834

Will send to IANA in 2 weeks barring objections.

pr
--

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

For review: Original-Recipient

Test mail - please ignore if it turns out to be a dupe.

The From: address is "unidirectional" (sent from a Webmail
interface where I can't set a working Reply-To address, sorry).

http://gmane.org/list-address.php?group=gmane.ietf.message-headers
shows still the old @lists.ietf address, and the claranet.de Webmail tells
me that this doesn't work, therefore I test now the new @ietf address.
----------------------------------------------------------------------------------

Hi,

when draft-eai-dsn got its number it is time to add
Original-Recipient to the registry.  Bruce has this
in draft-lilly-legacy-fields-00, but his I-D didn't
move for three years.  The Original-Recipient is not
really a "legacy" field, it is only "unregistered".

 Frank
-----------------------------------------------------
PERMANENT MESSAGE HEADER FIELD REGISTRATION TEMPLATE:

Header field name:         Original-Recipient
Applicable protocol:       mail
Status:                    standard
Author/Change controller:  IETF
Specification document(s): RFC 3798, draft-ietf-eai-dsn
Related information:
  Also used in Delivery Status Notification (DSN) per-recipient fields
  (RFC 3464) in a message/delivery-status part.  Compare RFC 2156 for
(Continue reading)

Anne van Kesteren | 27 Jan 01:36
Favicon
Gravatar

Method-Check-Max-Age

Hi,

Based on feedback we renamed Method-Check-Expires to Method-Check-Max-Age  
and instead of an HTTP-date it now takes delta-seconds (RFC 2616).

   http://dev.w3.org/2006/waf/access-control/

Can I simply e-mail IANA with this update or shall we go for another two  
weeks review here? I'm good either way :-)

By the way, thanks for the help before in getting the headers  
provisionally registered, all worked out:

   http://iana.org/assignments/message-headers/prov-headers.html

Kind regards,

--

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

Peter Saint-Andre | 6 Nov 16:40

[Fwd: I-D Action:draft-saintandre-header-pres-00.txt]

FYI

-------- Original Message --------
To: i-d-announce <at> ietf.org
From: Internet-Drafts <at> ietf.org
Date: Mon, 05 Nov 2007 22:00:02 -0500
Subject: I-D Action:draft-saintandre-header-pres-00.txt

A New Internet-Draft is available from the on-line Internet-Drafts
directories.

	Title           : The Presence-ID Header Field
	Author(s)       : P. Saint-Andre
	Filename        : draft-saintandre-header-pres-00.txt
	Pages           : 7
	Date            : 2007-11-05

This document defines a header field that enables the author of an
email message to include a Presence URI in the message header block
for the purpose of associating the author with an address that
provides information about network availability, also known as
"presence".

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-saintandre-header-pres-00.txt

Attachment (smime.p7s): application/x-pkcs7-signature, 7338 bytes
FYI
(Continue reading)

Peter Saint-Andre | 6 Nov 16:40

[Fwd: I-D Action:draft-saintandre-header-im-00.txt]

FYI

-------- Original Message --------
To: i-d-announce <at> ietf.org
From: Internet-Drafts <at> ietf.org
Date: Mon, 05 Nov 2007 22:00:02 -0500
Subject: I-D Action:draft-saintandre-header-im-00.txt

A New Internet-Draft is available from the on-line Internet-Drafts
directories.

	Title           : The IM-ID Header Field
	Author(s)       : P. Saint-Andre
	Filename        : draft-saintandre-header-im-00.txt
	Pages           : 7
	Date            : 2007-11-05

This document defines a header field that enables the author of an
email message to include an Instant Messaging (IM) URI in the message
header block for the purpose of associating the author with an
instant messaging address.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-saintandre-header-im-00.txt

Attachment (smime.p7s): application/x-pkcs7-signature, 7338 bytes
FYI

(Continue reading)

Anne van Kesteren | 4 Oct 11:31
Favicon
Gravatar

If-Method-Allowed renamed to Method-Check

Hi,

Because If-Method-Allowed didn't share the semantics of other If-* headers  
it seemed better to rename it. Should the review period be extended by  
another two weeks for this header?

Kind regards,

--

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

Anne van Kesteren | 27 Sep 13:50
Favicon
Gravatar

HTTP header registration question

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/>
Header field names:
   Access-Control
   If-Method-Allowed
   Referer-Root (sic)

Applicable protocol:
   http

Status:
   standard

Author/Change controller:
   W3C
(Continue reading)

Peter Saint-Andre | 7 Jun 20:52

draft-saintandre-jabberid

We have previously discussed draft-saintandre-jabberid on this list. The
latest version is -05:

http://www.ietf.org/internet-drafts/draft-saintandre-jabberid-05.txt

As far as I know, I have corrected the errors in RFC 4622 (on which the
I-D depends) in draft-saintandre-rfc4622bis. Assuming that rfc4622bis 
is accurate (if not it will be corrected per discussion on the URI and
URI-Review lists), I would like to know if anyone on this list has
further feedback on draft-saintandre-jabberid. If not, I will complete
another reading of the I-D and then request a standards action from the 
appropriate AD.

Thanks!

Peter

--

-- 
Peter Saint-Andre
XMPP Standards Foundation
http://www.xmpp.org/xsf/people/stpeter.shtml


Gmane