Re: IETF chair's blog
Marc Petit-Huguenin <petithug@acm.org> Mon, 25 February 2013 23:28 UTC
Return-Path: <petithug@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27B7D21F948D for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 15:28:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.561
X-Spam-Level:
X-Spam-Status: No, score=-102.561 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xwbUgNEet7PS for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 15:28:44 -0800 (PST)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id 79ACD21E8128 for <ietf@ietf.org>; Mon, 25 Feb 2013 15:28:38 -0800 (PST)
Received: from [IPv6:2601:9:4b80:32:69cb:6b3f:dfaa:1476] (unknown [IPv6:2601:9:4b80:32:69cb:6b3f:dfaa:1476]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 6397A20515; Mon, 25 Feb 2013 23:28:37 +0000 (UTC)
Message-ID: <512BF3A7.3020903@acm.org>
Date: Mon, 25 Feb 2013 15:28:39 -0800
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130116 Icedove/10.0.12
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: IETF chair's blog
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org> <51298B1E.60007@lacnic.net> <512A5A10.4090406@acm.org> <8A832DDC-1D5E-4C1B-87BB-36A384937480@lacnic.net> <512B0A2D.3050102@acm.org> <512B0B20.2000403@lacnic.net> <512B0C7E.5010900@250bpm.com> <512B0E64.2030101@acm.org> <96CB57D2-68EA-4AC5-92AD-90CEA37E2A93@lurchi.franken.de> <512B827F.4060406@acm.org> <m2r4k4c82l.wl%randy@psg.com>
In-Reply-To: <m2r4k4c82l.wl%randy@psg.com>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2013 23:28:45 -0000
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 02/25/2013 03:00 PM, Randy Bush wrote: >> For me the most important point is that it is managed on IETF (or IETF's >> contractor) servers. > > as no private data are involved, i am curious why? > Because public does not mean unlimited availability. Let's say that the IETF decides to use a collaboration tool hosted by a service run by an external company. The data is public (although it can be stored in a proprietary format) so anybody can consult it. But suddenly the service is bankrupted/become collateral damage when servers are seized/has its certificates expiring/etc... Unless someone did some preventive data liberation, the data is no longer available, at least until whatever caused the problem is solved. - -- Marc Petit-Huguenin Email: marc@petit-huguenin.org Blog: http://blog.marc.petit-huguenin.org Profile: http://www.linkedin.com/in/petithug -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJRK/OkAAoJECnERZXWan7EP/gQAK+bhwya94XYiAXwvwlR5bTX ejSRx7Z8OhE25ggkNOBmY/zaRNyfmFSxmPGlEMWrMjDd/3n761NjyOHnHksNyqT4 WVUbPwIy0fFKPwVsWp6YzrmrmuFkwL3NOGjgBRXQuO1N0dLj42yk1NbSrqxfSzXx wiUCu+U3ucCD7F5aNg3tZh+6BNMCbFjjk9KKrylxfRtg0x1lJjNuPkXUhIsyQLer fwqeRAzZhFBT5xo1Nr0lijb6Eu1rYZjaMESQTPs8IquDI0FLrxLvwyiO7wCK7s5Y b21qN+/yZaxxqgbv3om0gRwWx7r2MZshZD5TXGE7XiUfiTHkp7tgP/ymnh9U2t39 JcnXocng470JfewJk1+zBzrfriTGSpaSK0RpDRd+Ft/KLT4J5iBoD2/5AR3PCWwM nHiab1UqdKEsyMuNEEPSA7xaM0N401IRVePaVv7Woo7YtbrEKmXCwwqQERy2hgqJ W4RSIg8BrI1FTztkRFWrvYZYhU7nIiQY9lxBW7Un84aWeS78TS6ePPfDmVPjPk2e GAV9DQw6yf21hdiHwP0slHeKrcSYA/sNu1vq7f8j1+ympJrqvA6b7/kZzCRx8YNI NYYgEvp4Z8ISCzyIOr16L6M7zs0yAwDHRxCU22tjMIq3GH33nKWpDjIw/RU9sekX /1LePxXi9Xs+mZLAa0KO =7oou -----END PGP SIGNATURE-----
- IETF chair's blog IETF Chair
- Re: IETF chair's blog Hector Santos
- Re: IETF chair's blog Alejandro Acosta
- Re: IETF chair's blog DM Abreu
- Re: IETF chair's blog Arturo Servin
- Re: IETF chair's blog Marc Petit-Huguenin
- Re: IETF chair's blog Arturo Servin
- Re: IETF chair's blog Brian Trammell
- Re: IETF chair's blog Marc Petit-Huguenin
- Re: IETF chair's blog Arturo Servin
- Re: IETF chair's blog Arturo Servin
- Re: IETF chair's blog Martin Sustrik
- Re: IETF chair's blog Fred Baker (fred)
- Re: IETF chair's blog Marc Petit-Huguenin
- Re: IETF chair's blog Brian E Carpenter
- Re: IETF chair's blog Arturo Servin
- Re: IETF chair's blog Michael Tuexen
- Re: IETF chair's blog Simon Pietro Romano
- Re: IETF chair's blog Brian E Carpenter
- Re: IETF chair's blog Marc Petit-Huguenin
- Re: IETF chair's blog Alejandro Acosta
- Re: IETF chair's blog Dale R. Worley
- Re: IETF chair's blog jari.arkko
- Vendor standardization (was: IETF chair's blog) SM
- Re: IETF chair's blog Simon Pietro Romano
- Re: IETF chair's blog Carsten Bormann
- Re: IETF chair's blog Hector Santos
- Re: IETF chair's blog Randy Bush
- Re: IETF chair's blog Marc Petit-Huguenin
- Re: IETF chair's blog Randy Bush
- Re: IETF chair's blog Arturo Servin
- Re: IETF chair's blog falsehood911
- Re: IETF chair's blog Carlos M. Martinez
- Meetecho archive down? / Availability of collabor… Simon Leinen
- Re: Meetecho archive down? / Availability of coll… Simon Pietro Romano
- Re: Meetecho archive down? / Availability of coll… Simon Leinen
- Re: Meetecho archive down? / Availability of coll… Simon Pietro Romano