> -Original Message-
> From: =JeffH [mailto:jeff.hod...@kingsmountain.com]
> Sent: Friday, May 04, 2012 9:06 AM
> To: Murray S. Kucherawy
> Cc: IETF WebSec WG
> Subject: Re: [websec] new rev: draft-ietf-websec-strict-transport-sec-07
>
> yes, as well as Section 2 o
Nevermind all of that. It looks like that's covered in RFC2616 Section 4.2.
-MSK
___
websec mailing list
websec@ietf.org
https://www.ietf.org/mailman/listinfo/websec
> -Original Message-
> From: websec-boun...@ietf.org [mailto:websec-boun...@ietf.org] On Behalf Of
> =JeffH
> Sent: Wednesday, May 02, 2012 1:39 PM
> To: IETF WebSec WG
> Subject: [websec] new rev: draft-ietf-websec-strict-transport-sec-07
>
> New rev:
> https://tools.ietf.org/html/draft-
> -Original Message-
> From: Julian Reschke [mailto:julian.resc...@gmx.de]
> Sent: Tuesday, May 01, 2012 12:54 PM
> To: Murray S. Kucherawy
> Cc: apps-disc...@ietf.org; websec@ietf.org;
> draft-ietf-websec-strict-transport-...@tools.ietf.org
> Subject: Re: [websec] Ap
> -Original Message-
> From: Julian Reschke [mailto:julian.resc...@gmx.de]
> Sent: Tuesday, May 01, 2012 1:11 AM
> To: Murray S. Kucherawy
> Cc: apps-disc...@ietf.org; websec@ietf.org;
> draft-ietf-websec-strict-transport-...@tools.ietf.org
> Subject: Re: [websec] Ap
> -Original Message-
> From: Julian Reschke [mailto:julian.resc...@gmx.de]
> Sent: Monday, April 30, 2012 10:03 AM
> To: Murray S. Kucherawy
> Cc: apps-disc...@ietf.org; websec@ietf.org;
> draft-ietf-websec-strict-transport-...@tools.ietf.org
> Subject: Re: [webs
: HTTP Strict Transport Security (HSTS)
Reviewer: Murray S. Kucherawy
Review Date: April 28, 2012
IETF Last Call Date: n/a
IESG Telechat Date: n/a
Summary: This draft is almost ready for publication as a Standards Track RFC,
but has a few issues that should be fixed before publication.
Reviewer
> -Original Message-
> From: Yoav Nir [mailto:y...@checkpoint.com]
> Sent: Monday, December 12, 2011 11:25 AM
> To: Murray S. Kucherawy
> Cc: websec@ietf.org
> Subject: Re: [websec] Same Origins and email
>
> > What about something like Outlook or alpine, where
> -Original Message-
> From: Adam Barth [mailto:i...@adambarth.com]
> Sent: Monday, December 12, 2011 11:35 AM
> To: Yoav Nir
> Cc: Murray S. Kucherawy; websec@ietf.org
> Subject: Re: [websec] Same Origins and email
>
> The questions you're asking don&#x
> -Original Message-
> From: Adam Barth [mailto:i...@adambarth.com]
> Sent: Monday, December 12, 2011 11:09 AM
> To: Murray S. Kucherawy
> Cc: websec@ietf.org
> Subject: Re: [websec] Same Origins and email
>
> That depends on the MUA. In Gmail, for exampl
Hi all, long-time lurker, first-time poster.
I don't work in the web browser business so much as I do the messaging
anti-abuse business. But this stuff has gotten my attention. Now that RFC6454
is published, I have a few questions about its possible application in my
context.
My first questio
11 matches
Mail list logo
