IETF Logo Mail Archive

Re: [websec] Regarding RFC 6797

Anne van Kesteren <annevk@annevk.nl> Tue, 08 May 2018 07:48 UTC

Return-Path: <annevk@annevk.nl>
X-Original-To: websec@ietfa.amsl.com
Delivered-To: websec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16BB61271FD for <websec@ietfa.amsl.com>; Tue, 8 May 2018 00:48:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.019
X-Spam-Level:
X-Spam-Status: No, score=-2.019 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=annevk.nl
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6hHj2DemwR4R for <websec@ietfa.amsl.com>; Tue, 8 May 2018 00:48:01 -0700 (PDT)
Received: from homiemail-a2.g.dreamhost.com (homie.mail.dreamhost.com [208.97.132.208]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5DC0D1270B4 for <websec@ietf.org>; Tue, 8 May 2018 00:48:01 -0700 (PDT)
Received: from homiemail-a2.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a2.g.dreamhost.com (Postfix) with ESMTP id 76F29280072 for <websec@ietf.org>; Tue, 8 May 2018 00:48:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=annevk.nl; h=mime-version :in-reply-to:references:from:date:message-id:subject:to:cc: content-type; s=annevk.nl; bh=IRMq4Ob3xu7OUk0zX+ki8q5Lj7E=; b=Z0 woMs8Dm5A/SxN5WemuFXLPEikhm1nrHkpiDfmhZ8rqGve5/Nc/deGlW4jRJS/6vD 6kE4/pqxG6uwS4A8hr1AZ71znan3Z9t1SGYo6emO5YoYorIjf1hJzlGjOBxnaSuo Kk1rU25+1TE76vmDIhvmxIKroQVfQouvZb3qFjRBw=
Received: from mail-wm0-f41.google.com (mail-wm0-f41.google.com [74.125.82.41]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: annevk@annevk.nl) by homiemail-a2.g.dreamhost.com (Postfix) with ESMTPSA id 50C59280062 for <websec@ietf.org>; Tue, 8 May 2018 00:48:00 -0700 (PDT)
Received: by mail-wm0-f41.google.com with SMTP id t11so17214091wmt.0 for <websec@ietf.org>; Tue, 08 May 2018 00:48:00 -0700 (PDT)
X-Gm-Message-State: ALQs6tARaazzOhkPTs3WcPGPcMPSISQrWB4UJ705bGcntfbMCoAvnBt8 DsVT/kXXQ65cY5VRZf7UKxWugAQ6Op5Ukz7TSg==
X-Google-Smtp-Source: AB8JxZpQb6iVQR5pA9WFy9QGB6TSOlfrTbtA2esD1DifVrlC+HbwBbThsOpJPUYQuqfViVEHj6at2Heipw+UUl9QKjQ=
X-Received: by 2002:a50:ee15:: with SMTP id g21-v6mr47762328eds.269.1525765678738; Tue, 08 May 2018 00:47:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.80.138.2 with HTTP; Tue, 8 May 2018 00:47:57 -0700 (PDT)
In-Reply-To: <960CE667-98A4-48A9-9E7E-B32E3405A961@gmail.com>
References: <CWXP265MB03125F1F074DBA2FDA1E1D2BB1860@CWXP265MB0312.GBRP265.PROD.OUTLOOK.COM> <960CE667-98A4-48A9-9E7E-B32E3405A961@gmail.com>
From: Anne van Kesteren <annevk@annevk.nl>
Date: Tue, 08 May 2018 09:47:57 +0200
X-Gmail-Original-Message-ID: <CADnb78jDEfAwoeObF62SmdaxpF2FrYF2TQZGnESE+1kZEU=xNA@mail.gmail.com>
Message-ID: <CADnb78jDEfAwoeObF62SmdaxpF2FrYF2TQZGnESE+1kZEU=xNA@mail.gmail.com>
To: Yoav Nir <ynir.ietf@gmail.com>
Cc: Robert Linder <Robert.Vuj.Linder@outlook.com>, "websec@ietf.org" <websec@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/websec/UIy3uGIbgS1JfzDCpNLqSY1aqig>
Subject: Re: [websec] Regarding RFC 6797
X-BeenThere: websec@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Web Application Security Minus Authentication and Transport <websec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/websec>, <mailto:websec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/websec/>
List-Post: <mailto:websec@ietf.org>
List-Help: <mailto:websec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/websec>, <mailto:websec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 May 2018 07:48:03 -0000

On Mon, May 7, 2018 at 9:54 PM, Yoav Nir <ynir.ietf@gmail.com> wrote:
> Immutable meaning that the HSTS header is permanent and can never be
> removed?  So if a user agent has seen an immutable HSTS header once, that
> site has to be (valid) HTTPS-only forever?
>
> Interesting idea.

FWIW, if anything, it should be about standardizing
https://hstspreload.org/. That's already the widely adopted practice
to mostly-immutable HSTS. (Not quite sure truly-immutable is feasible,
other than using a TLD that has HSTS as policy. And even then TLDs get
reassigned or disappear at times...)


-- 
https://annevankesteren.nl/

v2.23.0 | Report a Bug | By Email