Re: [Rfc-markdown] Is xml2rfc.tools.ietf.org down? Can't reach it from IETF 103 network

Dan York <york@isoc.org> Sun, 04 November 2018 13:48 UTC

Return-Path: <york@isoc.org>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A68A21200D7 for <rfc-markdown@ietfa.amsl.com>; Sun, 4 Nov 2018 05:48:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isoc.org
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 R7NVatLh-xQ1 for <rfc-markdown@ietfa.amsl.com>; Sun, 4 Nov 2018 05:48:36 -0800 (PST)
Received: from NAM04-SN1-obe.outbound.protection.outlook.com (mail-eopbgr700078.outbound.protection.outlook.com [40.107.70.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 58F46120072 for <rfc-markdown@ietf.org>; Sun, 4 Nov 2018 05:48:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isoc.org; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=f2VIfsczf95ybWkxt7uc8XMspThIJsBCL+PNQazAoXo=; b=ZD7cQszJVRwVdiYd62iWDMGP7IwX7Q5sX5A1LdOfg+IID38UekPyyZ89bUVlgJSBjqkHNkXe4SA5aYWOz8PSibTUdhJGgejgKiJFLGb7SJKW12L/lo3q2/XEq1+yfeu3H5AMFyDT2e1+qQQswr7vsUEzgcpJKm5C1O/OCkVEPms=
Received: from BN3PR0601MB1314.namprd06.prod.outlook.com (10.161.210.139) by BN3PR0601MB1026.namprd06.prod.outlook.com (10.160.154.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1294.20; Sun, 4 Nov 2018 13:48:34 +0000
Received: from BN3PR0601MB1314.namprd06.prod.outlook.com ([fe80::6ddc:e11:56b8:b6ba]) by BN3PR0601MB1314.namprd06.prod.outlook.com ([fe80::6ddc:e11:56b8:b6ba%9]) with mapi id 15.20.1273.033; Sun, 4 Nov 2018 13:48:34 +0000
From: Dan York <york@isoc.org>
To: Carsten Bormann <cabo@tzi.org>
CC: "Rfc-markdown@ietf.org" <rfc-markdown@ietf.org>
Thread-Topic: [Rfc-markdown] Is xml2rfc.tools.ietf.org down? Can't reach it from IETF 103 network
Thread-Index: AQHUdDL/1H7gmnc4sEKLaptIDCUUKKU/heGAgAAb3gA=
Date: Sun, 4 Nov 2018 13:48:33 +0000
Message-ID: <FE6DD41B-7DFB-4DE7-A885-B9FCBE2F7D77@isoc.org>
References: <DE6C909E-D327-4931-B876-B51E9E454557@isoc.org> <68CDC4C6-9576-441C-BB51-7D664F668B89@tzi.org> <6495EB78-B3F1-454F-965C-008F790A6D20@tzi.org>
In-Reply-To: <6495EB78-B3F1-454F-965C-008F790A6D20@tzi.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [2001:67c:1232:144:8587:b960:9782:4d9d]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN3PR0601MB1026; 6:GGkxxsSXrZaag98mIWa+WGN6F+ZmclWsDb/AEa3KLoOTZJaBMX+et3UObBpTI+z4jSW2du/Xe9T2AXFxPdL8zfFN3dZt4sJDucpM36zxQJWHoxwcMvFEullxjhyXEmb/4HUo0tSdDnugKqA9EeIXRraOew/IzqayeaEFsTJNhfuPl5Ct1gZS5I5mVpdgcKtAPWqd339Yy3ML+mODOIFgssiVNvZYyX9OYrHLcCrIK4nHJ9YOKCF+IOGjMxdZ+QfIFQyYUrhIuS6HSBeXke/aeCc/E0gx6QL5+uWrhHDLy17kKlCv1XMjSGv6i8/dK7N/LOz5xfpAMkQmlhBzMPYtDonRAvAuDXIUTmLH3nXUk5aYo6T4nQSKbovqpPNr29RRMzSN7eH1SoPGYd9w/RC21qDxr/6iZJTg0Nz6QSyqP4VLpwzVGPWzM3XTITST5NIJFA9WmBUVp6oNL37H5SoVxg==; 5:W7t9qsl+aA8/SoJROm9O2KcFn+uLa2jaJek/+/nPswWf9JUvidTCCNu4Z/wv1iWawunrf3/718eW+khzWzUspzUZeajAuW56ghQ1wWZVbtGPORQsIM1F8C9OA5fVsUQneGTZSrKxucTHcT0m1/uaBdAfgwmmKfwp/I1XJ2ivOlE=; 7:tYMKDyPNlW24s5NBT631oD+BoDRNA5dUzNWo2Y6xeMFt/ZLg98XC+OZZH9NfBuyocTEiHzcymIMkH+ndNNI3J+LsWyo5jM8wDeles8Mlnq4dIYstmn4BHpDaucr/W993QoLGNdlvpuNwWDy2cy51wg==
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: a99ee996-1383-425f-a258-08d6425c36a5
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(2017052603328)(7153060)(49563074)(7193020); SRVR:BN3PR0601MB1026;
x-ms-traffictypediagnostic: BN3PR0601MB1026:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=york@isoc.org;
x-microsoft-antispam-prvs: <BN3PR0601MB1026BD2B745133DA321734DCB7C90@BN3PR0601MB1026.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(31418570063057);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(102415395)(6040522)(2401047)(5005006)(8121501046)(3231382)(944501410)(4983020)(4982022)(52105095)(93006095)(93001095)(10201501046)(3002001)(148016)(149066)(150057)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(20161123562045)(20161123564045)(20161123560045)(201708071742011)(7699051)(76991095); SRVR:BN3PR0601MB1026; BCL:0; PCL:0; RULEID:; SRVR:BN3PR0601MB1026;
x-forefront-prvs: 084674B2CF
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39830400003)(346002)(376002)(136003)(366004)(396003)(189003)(199004)(46003)(2900100001)(53936002)(11346002)(6246003)(53376002)(6306002)(6916009)(83716004)(86362001)(229853002)(6436002)(446003)(966005)(25786009)(1720100001)(6486002)(99286004)(71190400001)(97736004)(14454004)(486006)(71200400001)(478600001)(82746002)(81156014)(81166006)(8676002)(8936002)(2616005)(102836004)(105586002)(33656002)(106356001)(2906002)(14444005)(256004)(36756003)(99936001)(4326008)(186003)(76176011)(68736007)(5660300001)(6512007)(316002)(53546011)(6506007)(476003)(7736002)(305945005)(6116002)(18886065003); DIR:OUT; SFP:1101; SCL:1; SRVR:BN3PR0601MB1026; H:BN3PR0601MB1314.namprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: isoc.org does not designate permitted sender hosts)
x-microsoft-antispam-message-info: g7hmi/uiu0mG78eummNFvYZRujvSbNezkhY3ymC4ynGaVvVSY/p1A2SAsrO/Qbni8Z2syCPrIP41CXn9mo7Hewjm9mL5o6VGB+jydg2MurTQjexMuXW537vnyqNrRKj5z5Pr5LnQ1blEV2DefREgRN9nPXQlB6vAgf8xEXRmopUCa3FOYTZxUufma4MkPhTW9P/K04iZzCKyXDPFULe3RLimR9QMKg0mDmMDxBzLz9mC7/d7QSkLDrVgoeSzsAyKhPLIukiqmqjAOmB5OmRQ9DnesrpsFLtIqt7xqGLTRyDU+4cZcI/Ghe9ePAIFXB24QX1G/c/WJmhclLFxhfW6dZKxEL1gCClU2AOP0owZaGA=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/signed; boundary="Apple-Mail=_CE1CEB60-579F-40FC-B7B5-AF054A539835"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-OriginatorOrg: isoc.org
X-MS-Exchange-CrossTenant-Network-Message-Id: a99ee996-1383-425f-a258-08d6425c36a5
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Nov 2018 13:48:33.9652 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 89f84dfb-7285-4810-bc4d-8b9b5794554f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0601MB1026
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/459wVG_dNwoHWeM3PJOWov6fjaM>
Subject: Re: [Rfc-markdown] Is xml2rfc.tools.ietf.org down? Can't reach it from IETF 103 network
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Nov 2018 13:48:39 -0000

Carsten,

> On Nov 4, 2018, at 7:08 PM, Carsten Bormann <cabo@tzi.org> wrote:
> 
> Henrik just told me this now works again

And I can confirm that it work. Thanks for letting me know.

> (at least if you fix the double dot :-)

Ha!  I'm not quite sure how that got in there, since the text only has one dot. And I scrolled back up the shell history and don't see a double dot anywhere... so I must have somehow copied/pasted that incorrectly.

Thanks,
Dan

--
Dan York
Director, Content & Web Strategy, Internet Society
york@isoc.org   +1-802-735-1624 
Jabber: york@jabber.isoc.org  Skype: danyork   http://twitter.com/danyork

http://www.internetsociety.org/