Re: Let's look at it from an IETF newbie's perspective... Re: IPv4 Outage Planned for IETF 71 Plenary

Matt Mathis <mathis@psc.edu> Wed, 19 December 2007 19:37 UTC

Return-path: <ietf-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J54jg-0004nu-Ec; Wed, 19 Dec 2007 14:37:44 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J54jd-0004kD-Sv; Wed, 19 Dec 2007 14:37:41 -0500
Received: from mailer1.psc.edu ([2001:5e8:1:3a::64]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J54jb-0005VY-NP; Wed, 19 Dec 2007 14:37:41 -0500
Received: from tesla.psc.edu (tesla.psc.edu [128.182.58.233]) by mailer1.psc.edu (8.14.2/8.13.3) with ESMTP id lBJJbd2a020802 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 19 Dec 2007 14:37:39 -0500 (EST)
Received: from localhost.psc.edu (localhost.psc.edu [127.0.0.1]) by tesla.psc.edu (8.13.1/8.13.1) with ESMTP id lBJJbdCm010011; Wed, 19 Dec 2007 14:37:39 -0500
Date: Wed, 19 Dec 2007 14:37:39 -0500
From: Matt Mathis <mathis@psc.edu>
To: ietf@ietf.org
In-Reply-To: <407E0B9D-CFC6-4763-A6B3-9559EAF518EC@multicasttech.com>
Message-ID: <Pine.LNX.4.64.0712191430050.9776@tesla.psc.edu>
References: <C38EED7A.1B20DA%jordi.palet@consulintel.es> <407E0B9D-CFC6-4763-A6B3-9559EAF518EC@multicasttech.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: iaoc@ietf.org, iesg@ietf.org
Subject: Re: Let's look at it from an IETF newbie's perspective... Re: IPv4 Outage Planned for IETF 71 Plenary
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org

> Why not do this for the entire meeting ? In fact, why not do it for the 
> entire meeting even if there isn't a plenary outage ?

Good idea!, except perhaps 71 is too soon.  How about the plenary
outage as planed for 71, and the entire IETF after that?

(Perhaps support IPv4 in the terminal room only, for individuals who don't 
have enough leverage to move their home institutions.)

The point is not to cause people to debug during the IETF, but to cause 
people to notice deployment problems and to have them fixed by the following
IETF.

Thanks,
--MM--



_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf