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

Marshall Eubanks <tme@multicasttech.com> Thu, 03 January 2008 15:18 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 1JARpw-0003Hd-63; Thu, 03 Jan 2008 10:18:24 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JARpu-000318-0T; Thu, 03 Jan 2008 10:18:22 -0500
Received: from lennon.multicasttech.com ([63.105.122.7] helo=multicasttech.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JARpt-0000zy-Mc; Thu, 03 Jan 2008 10:18:21 -0500
Received: from [63.105.122.7] (account marshall_eubanks HELO [IPv6:::1]) by multicasttech.com (CommuniGate Pro SMTP 3.4.8) with ESMTP-TLS id 10044098; Thu, 03 Jan 2008 10:18:21 -0500
In-Reply-To: <Pine.LNX.4.64.0712191430050.9776@tesla.psc.edu>
References: <C38EED7A.1B20DA%jordi.palet@consulintel.es> <407E0B9D-CFC6-4763-A6B3-9559EAF518EC@multicasttech.com> <Pine.LNX.4.64.0712191430050.9776@tesla.psc.edu>
Mime-Version: 1.0 (Apple Message framework v753)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <CE2BDD7C-B6A3-41C8-A53A-320C9A8E00F4@multicasttech.com>
Content-Transfer-Encoding: 7bit
From: Marshall Eubanks <tme@multicasttech.com>
Date: Thu, 03 Jan 2008 10:18:12 -0500
To: Matt Mathis <mathis@psc.edu>
X-Mailer: Apple Mail (2.753)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: iaoc@ietf.org, ietf@ietf.org, iesg@ietf.org
Subject: Re: [IAOC] 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

On Dec 19, 2007, at 2:37 PM, Matt Mathis wrote:

>> 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?
>

I actually had in mind a parallel network, offering only IPv6, but  
with v4 still available on the original network, at least in the  
beginning.

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

I suspect that there are enough good engineers at the plenary to  
route around any artificial restrictions. For example, those with  
Macs and EVD0 cards could easily set up wired or wireless LANs  
offering v4...
>

>
> 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.
>

So would it be OK if I set up a high bandwidth multicast HD video  
stream from the plenary ? The IETF used to be
a great tool to help debug multicast problems...

> Thanks,
> --MM--
>

Regards
Marshall

>
>
> _______________________________________________
> IAOC mailing list
> IAOC@ietf.org
> https://www1.ietf.org/mailman/listinfo/iaoc


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