Re: [core] Comments on draft-ietf-core-echo-request-tag-02

Carsten Bormann <cabo@tzi.org> Mon, 22 October 2018 11:56 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 660B8129AB8; Mon, 22 Oct 2018 04:56:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
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 Ep6TaxHnH11E; Mon, 22 Oct 2018 04:56:00 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 63D39128CF3; Mon, 22 Oct 2018 04:56:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost2.informatik.uni-bremen.de [134.102.200.7]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id w9MBtFXZ001523; Mon, 22 Oct 2018 13:55:20 +0200 (CEST)
Received: from [192.168.217.102] (p54A6CA9F.dip0.t-ipconnect.de [84.166.202.159]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 42dw1t6HRGz1Bqf; Mon, 22 Oct 2018 13:55:14 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <049375ED-A806-4969-8403-8DB18317021F@ericsson.com>
Date: Mon, 22 Oct 2018 13:55:14 +0200
Cc: Jim Schaad <ietf@augustcellars.com>, "core-chairs@ietf.org" <core-chairs@ietf.org>, "draft-ietf-core-echo-request-tag@ietf.org" <draft-ietf-core-echo-request-tag@ietf.org>, "core@ietf.org" <core@ietf.org>
X-Mao-Original-Outgoing-Id: 561902112.1695319-e9b8c12a016684b597a97f9e9a0b95eb
Content-Transfer-Encoding: quoted-printable
Message-Id: <B50307B6-64C9-4092-B0FA-DCD4FF277690@tzi.org>
References: <00fa01d461b0$2a314f40$7e93edc0$@augustcellars.com> <20181017141813.GA4084@hephaistos.amsuess.com> <E207969D-C945-4E7A-94E7-C3F08EC46882@ericsson.com> <005d01d46736$8025e8d0$8071ba70$@augustcellars.com> <049375ED-A806-4969-8403-8DB18317021F@ericsson.com>
To: Göran Selander <goran.selander@ericsson.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/kRV0K1NkrMj1Lzoo7HW5a9Yd1pA>
Subject: Re: [core] Comments on draft-ietf-core-echo-request-tag-02
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2018 11:56:02 -0000

On Oct 19, 2018, at 17:43, Göran Selander <goran.selander@ericsson.com> wrote:
> 
> Please note that the "Editor's copy" does not build to the latest version (perhaps someone with admin rights could look at this __) so look at the .md file instead.
> https://github.com/core-wg/echo-request-tag

I don’t know why, but this repo doesn’t seem to be set up for automatic builds.

You can always build manually by saying

	make ghpages

(Note that there also was a partial github outage [1] since yesterday evening, which may influence whether you can see that something has happened.  This was supposed to be fixed about now, but I haven’t seen the “all clear” yet.)

Grüße, Carsten

[1]: https://blog.github.com/2018-10-21-october21-incident-report/