From: Yoav Nir <ynir@checkpoint.com>
To: IETF WebSec WG <websec@ietf.org>
Thread-Topic: WGLC for X-Frame-Options
Thread-Index: Ac2xb0zTHb33hMtRQwuRaMJzUgzEDQQv02sA
Date: Wed, 14 Nov 2012 08:09:29 +0000
Message-ID: <4613980CFC78314ABFD7F85CC3027721015E74@IL-EX10.ad.checkpoint.com>
References: <D418C856-1FA9-4FA3-805D-6A44042B5A36@checkpoint.com>
In-Reply-To: <D418C856-1FA9-4FA3-805D-6A44042B5A36@checkpoint.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F402EF8D1AE1B74A993B1C42AA7278F0@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [websec] WGLC for X-Frame-Options
Precedence: list

Reminder: WGLC ends this Friday. Please send in your reviews.

On Oct 24, 2012, at 12:39 AM, Yoav Nir wrote:

> Hi all
>=20
> This is to initiate WGLC for the X-Frame-Options draft (not to be confuse=
d with the Frame-Options draft).
>=20
> Please go to http://tools.ietf.org/html/draft-ietf-websec-x-frame-options=
-01, read the draft and send comments.
>=20
> As usual, we would very much like to hear comments about clarity, thoroug=
hness and applicability. Since this draft documents existing behavior, rath=
er than prescribing future behavior, we would especially like to hear from =
people familiar with current implementations that support the X-Frame-Optio=
n header about whether the draft accurately describes the behavior of those=
 implementations.
>=20
> WGLC is usually for two weeks. However, the following two weeks include a=
n IETF meeting, so I am extending this period to a little over three weeks.=
 WGLC will end on Friday, November 16th. Please send your comments early, s=
o that we might use our session in Atlanta to discuss issues that come up.
>=20
> Yoav