[spring] Fwd: Re: FW: Re: SPRING SRComp design list

"Joel M. Halpern" <jmh@joelhalpern.com> Tue, 11 August 2020 22:15 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 3E67D3A0C77 for <spring@ietfa.amsl.com>; Tue, 11 Aug 2020 15:15:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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=joelhalpern.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 8370pskcjndG for <spring@ietfa.amsl.com>; Tue, 11 Aug 2020 15:15:24 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net []) (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 1A9843A0B41 for <spring@ietf.org>; Tue, 11 Aug 2020 15:15:23 -0700 (PDT)
Received: from localhost (localhost []) by maila2.tigertech.net (Postfix) with ESMTP id 4BR6bH6Fz2z6G9pQ for <spring@ietf.org>; Tue, 11 Aug 2020 15:15:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1597184123; bh=h02T+2n9p2YEFisOq6F+SIrNv+pU5NsMc5iYq7Ze6B4=; h=Subject:References:To:From:Date:In-Reply-To:From; b=fgXdDYc4zB12UzBFT5lcaoTNAibSZzs1+Pdkoh9I6A4/2f6H5Z6rXgyLuIhiJ11WG fm+63scG+BOINqqj7tDIr9GBh3eg+9mw83NiQoq2KbGdObo3mOStlU6JbYMWIclENy u2Fp9ScLOTDVHmVHWmaCcWFccfvBssSaF6C62nXY=
X-Quarantine-ID: <UFipvVQx4lfo>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [] (209-255-163-147.ip.mcleodusa.net []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 4BR6bH3Glvz6G83f for <spring@ietf.org>; Tue, 11 Aug 2020 15:15:23 -0700 (PDT)
References: <2eb45d68-8699-fe5c-c6a7-181fe9ef628e@nokia.com>
To: "spring@ietf.org" <spring@ietf.org>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
X-Forwarded-Message-Id: <2eb45d68-8699-fe5c-c6a7-181fe9ef628e@nokia.com>
Message-ID: <343da401-57f8-a550-339e-a24c6583f875@joelhalpern.com>
Date: Tue, 11 Aug 2020 18:15:21 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <2eb45d68-8699-fe5c-c6a7-181fe9ef628e@nokia.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/ccXPAnJ6oMseLB-zm8OQxvyn5QY>
Subject: [spring] Fwd: Re: FW: Re: SPRING SRComp design list
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Aug 2020 22:15:25 -0000

The tools team found a fixed the problem that was preventing us from 
making the SRComp archives public.  They are now public.

Thanks to all involved.

-------- Forwarded Message --------
Subject: Re: FW: Re: SPRING SRComp design list
Date: Tue, 11 Aug 2020 23:59:41 +0200
From: Martin Vigoureux <martin.vigoureux@nokia.com>
To: Joel Halpern Direct <jmh.direct@joelhalpern.com>

the archives are now public. please make sure every one is aware. past 
messages are also public.

Le 2020-08-11 à 23:48, Martin Vigoureux a écrit :
> seems there is an underlying tools issue somewhere. tools team will look 
> into that