Re: [TLS] who do I poke to fix the URLs in the header?

Stephen Farrell <stephen.farrell@cs.tcd.ie> Thu, 30 April 2015 08:06 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7FA71ACEF0 for <tls@ietfa.amsl.com>; Thu, 30 Apr 2015 01:06:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 tvqRSurn_hjE for <tls@ietfa.amsl.com>; Thu, 30 Apr 2015 01:06:33 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2ED8F1ACEEE for <tls@ietf.org>; Thu, 30 Apr 2015 01:06:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 046AFBE3E; Thu, 30 Apr 2015 09:06:32 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eSIZuqG6XuPE; Thu, 30 Apr 2015 09:06:30 +0100 (IST)
Received: from [10.87.48.73] (unknown [86.46.18.22]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 6742FBE2F; Thu, 30 Apr 2015 09:06:30 +0100 (IST)
Message-ID: <5541E286.2090001@cs.tcd.ie>
Date: Thu, 30 Apr 2015 09:06:30 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Dave Garrett <davemgarrett@gmail.com>, tls@ietf.org
References: <201504292035.21721.davemgarrett@gmail.com>
In-Reply-To: <201504292035.21721.davemgarrett@gmail.com>
OpenPGP: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/tls/mnr6hiSGsFIMsvEeU69g4ykEdCY>
Subject: Re: [TLS] who do I poke to fix the URLs in the header?
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Apr 2015 08:06:34 -0000

Hi Dave,

That brings in a bunch of things including tools, boilerplate
issues and policy stuff ("do we want an https-everything like
thing for the IETF?"). Good questions to ask though so I'll put
that on the IESG's agenda for some meetings we're having next
week. Please hassle me in 2-3 weeks if you don't hear something
back.

Cheers,
S.

On 30/04/15 01:35, Dave Garrett wrote:
> https://tlswg.github.io/tls13-spec/
> https://tools.ietf.org/html/draft-ietf-tls-tls13-05
> 
> Where does the "Status of This Memo" and "Copyright Notice" text get pulled from? There seems to be some black magic involved in the build process, and I don't see where that text lives. I'd like to request the two URLs be updated, but I don't know where to ask.
> 
> status has:
> http://datatracker.ietf.org/drafts/current/
> which redirects to:
> http://datatracker.ietf.org/doc/active/
> which does support TLS, and should be:
> https://datatracker.ietf.org/doc/active/
> 
> copyright has:
> http://trustee.ietf.org/license-info
> which redirects to:
> http://trustee.ietf.org/trust-legal-provisions.html
> which does support TLS, and should be:
> https://trustee.ietf.org/trust-legal-provisions.html
> the initial URL also supports TLS, so this works:
> https://trustee.ietf.org/license-info
> however that redirects to HTTP, not HTTPS (...sigh)
> 
> So, yeah... I'd like the new TLS spec to actually attempt to use TLS in its URLs, where possible. To do this needs:
> 1) Update those two URLs in the template for these sections to use the HTTPS equivalent (in the case of "status", also change "current" to "active").
> 2) Get someone to fix the redirects on trustee.ietf.org to redirect to HTTPS, at minimum when already coming from HTTPS.
> 
> Actually using TLS by default might also be a plan...
> 
> As to other URLs in the document, I added a couple 's'es in my minor fixes branch/PR. There are additional domains that do support HTTPS, technically, but they get cert errors... because of course they do.
> 
> The RFC references have an odd inconsistency here. In the numbered working group drafts, they properly generate with HTTPS links:
> https://tools.ietf.org/html/draft-ietf-tls-tls13-05#section-13.1
> However, in the editor's copy (draft-ietf-tls-tls13-latest), they generate with HTTP links:
> https://tlswg.github.io/tls13-spec/#rfc.references.1
> 
> That needs fixing if just for consistency.
> 
> Also, tools.ietf.org should of course be using HTTPS by default, but it's not.
> 
> 
> Dave
> 
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
> 
>