IETF Logo Mail Archive

Re: [netmod] HTTP: or HTTPS:

Ladislav Lhotka <lhotka@nic.cz> Wed, 31 July 2019 12:08 UTC

Return-Path: <lhotka@nic.cz>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07ADA120153 for <netmod@ietfa.amsl.com>; Wed, 31 Jul 2019 05:08:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.998
X-Spam-Level:
X-Spam-Status: No, score=-6.998 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_HI=-5, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
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 YPxNCuVXQoyS for <netmod@ietfa.amsl.com>; Wed, 31 Jul 2019 05:07:58 -0700 (PDT)
Received: from mail.nic.cz (mail.nic.cz [217.31.204.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE1CF1200F6 for <netmod@ietf.org>; Wed, 31 Jul 2019 05:07:58 -0700 (PDT)
Received: from birdie (unknown [IPv6:2001:1488:fffe:6:a88f:7eff:fed2:45f8]) by mail.nic.cz (Postfix) with ESMTPSA id 7787F13FD6D; Wed, 31 Jul 2019 14:07:56 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1564574876; bh=/+5U8YX5G82RvFsyirsvtbP3o2hhw9Vt17Hqy+mU+5Q=; h=From:To:Date; b=P1bhZa5HPWFNZBa5xqLi2QGVmq1fEZaCtPHv6/kInAgdXT7oamIbwVp6S5tWxPn4K jLjhNYiVrnWfLEiPmnP8UiA2pOslOBabF1wlzvW1ckwwwJMGmbb98U6GL3Bbfg+ZrH 4ALeyWjFnxcAzaie23A1g2HH9iKAN817GV56pzYA=
Message-ID: <a001a0d8cb4b02570ee2b9a71875bbdb0179c5af.camel@nic.cz>
From: Ladislav Lhotka <lhotka@nic.cz>
To: tom petch <ietfc@btconnect.com>, "Acee Lindem (acee)" <acee@cisco.com>, "netmod@ietf.org" <netmod@ietf.org>
Date: Wed, 31 Jul 2019 14:07:56 +0200
In-Reply-To: <076b01d54795$c593e1c0$4001a8c0@gateway.2wire.net>
References: <2dcd4d92-1436-4b9a-050f-ec36053ffa8a@bogus.com> <06ee01d5478f$0f827140$4001a8c0@gateway.2wire.net> <92dc3ca86f4850afe600ddc6874046505a1d8d7a.camel@nic.cz> <B050CCEE-1346-436D-8D11-36BA4D2758EA@cisco.com> <076b01d54795$c593e1c0$4001a8c0@gateway.2wire.net>
Organization: CZ.NIC
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.32.4
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: clamav-milter 0.100.3 at mail.nic.cz
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/0oeIZueTFEcwm0k8X7L_RKYWFZk>
Subject: Re: [netmod] HTTP: or HTTPS:
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Jul 2019 12:08:01 -0000

On Wed, 2019-07-31 at 11:48 +0000, tom petch wrote:
> ----- Original Message -----
> From: "Acee Lindem (acee)" <acee@cisco.com>
> Sent: Wednesday, July 31, 2019 12:11 PM
> 
> > On 7/31/19, 7:09 AM, "netmod on behalf of Ladislav Lhotka"
> <netmod-bounces@ietf.org on behalf of lhotka@nic.cz> wrote:
> >     On Wed, 2019-07-31 at 11:00 +0000, tom petch wrote:
> >     > YANG modules contain several URL - e.g. for the Working Group,
> Legal
> >     > provisions, RFC - for which some authors use http:, some use
> https: and
> >     > some use a mixture.
> >     >
> >     > Should we be recommending the use of https: in all cases?
> > 
> >     Yes, given that the http: URLs now return 404.
> 
> I find that my http: usually get silently converted to https: rather

Oh yes, sorry, my fault, I blindly used the URL from Appendix B that of course
doesn't work either way :-)

http://datatracker.ietf.org/wg/your-wg-name/

Lada

> than
> giving me a 404 but I agree that using https: native is better.  In
> passing, the recently IESG-approved
> draft-ietf-teas-yang-te-topo
> has http: as does (pro parte)
> draft-ietf-ospf-yang
> 
> Interestingly, RFC8407 Appendix A gets it right while Appendix B gets it
> wrong.
> 
> Tom Petch
> 
> 
> > Agreed. Perhaps, there should be an errata on the RFC 8407 template.
> > 
> > https://tools.ietf.org/html/rfc8407#appendix-B
> > 
> > Thanks,
> > Acee
> > 
> >     Lada
> > 
> >     >
> >     > Tom Petch
> >     >
> >     > _______________________________________________
> >     > netmod mailing list
> >     > netmod@ietf.org
> >     > https://www.ietf.org/mailman/listinfo/netmod
> >     --
> >     Ladislav Lhotka
> >     Head, CZ.NIC Labs
> >     PGP Key ID: 0xB8F92B08A9F76C67
> > 
> >     _______________________________________________
> >     netmod mailing list
> >     netmod@ietf.org
> >     https://www.ietf.org/mailman/listinfo/netmod
> > 
> > 
> > _______________________________________________
> > netmod mailing list
> > netmod@ietf.org
> > https://www.ietf.org/mailman/listinfo/netmod
> > 
-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67

v2.23.0 | Report a Bug | By Email