[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Interoperability Testing at IETF Meetings
Dear IESG Members:
At Harald's request, I have added the topic of "Interoperability Testing at
IETF Meetings" to the agenda for the September 18, 2003 IESG telechat under
"Management Issues." As background material for the discussion, I am
forwarding five e-mail messages (or excerpts thereof) that the Secretariat
has received on this topic. For your convenience, this material will also
be included in the telechat package. If the Secretariat receives
additional messages prior to the telechat, then I will forward them to you
and add them to the telechat package as well.
Regards,
Barbara
------------------------------------------------------------
Message #1 From Michael Richardson (in its entirety)
Subject: [57crew] IETF anchored interop testing
Date: Monday 28 July 2003 11:53
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
To: ietf-secretariat@ietf.org, Brett Thorson <bthorson@ietf.org>
Cc: hugh@xisp.net, martin.steimerling@ccrle.nec.de, Edward Lewis
<edlewis@arin.net>, Bill Manning <bmanning@ISI.EDU>, paul.hoffman@vpnc.org,
57crew@ietf.org, Sabine.Beauvois@etsi.org, Andrew McGregor
<andrew@indranet.co.nz>
-----BEGIN PGP SIGNED MESSAGE-----
Hi,
various WGs have attempted to organize interop/plug testing either before or
after IETF sessions. Sometimes during. I am aware of IPsec, HIP, DNSSEC, and
DHCPv6 tests that have occured or been attempted in the past year.
I wanted to arrange a manner in which we might organize this kind of thing
in a more organized, less ad-hoc manner. I wanted to propose that a mailing
list be set up that included someone from the secretariat, as well as
interested parties.
Primarily, I am interesting in reducing the lead time for getting things
organized - in great part so that the cost to the participants of attending
such a plugtest is reduced into the noise level compared to IETF itself.
If we can do this @ietf.org, that would be great. If not, let me know,
and I will create a list elsewhere.
I will save conversation about my thoughts about logistics for the list
itself.
------------------------------------------------------------
Message #2 From Bill Manning (excerpt)
(NOTE: In his message, Bill forwarded Message #1 from Michael Richardson,
and added one sentence. The excerpt contains the additional sentence.)
Envelope-to: bfuller@foretec.com
From: Bill Manning <bmanning@ISI.EDU>
Subject: Re: IETF anchored interop testing
To: mcr@sandelman.ottawa.on.ca (Michael Richardson)
Date: Thu, 4 Sep 2003 02:59:28 -0700 (PDT)
Cc: ietf-secretariat@ietf.org, bthorson@ietf.org, hugh@xisp.net,
martin.steimerling@ccrle.nec.de, edlewis@arin.net, bmanning@ISI.EDU,
paul.hoffman@vpnc.org, 57crew@ietf.org, Sabine.Beauvois@etsi.org,
andrew@indranet.co.nz, bmanning@ep.net
X-Mailer: ELM [version 2.4ME+ PL39 (25)]
There are some rumblings of doing another series of
testing in Korea prior to the IETF next spring.
--bill
------------------------------------------------------------
Message #3 From Kevin Almeroth (in its entirety, but without headers)
(NOTE: This message was forwarded to me by Brett Thorson who originally
received it. Kevin Almeroth is the head of the multicast group at the
University of Oregon that provides multicast support at the IETF meetings.)
On Tue, 26 Aug 2003, Kevin C. Almeroth wrote:
Brett, don't know if I have the right email for Jim, but I think I do. Okay...
So, we are planning a pretty interesting/aggressive project for the Minn
IETF and we wanted to get your feedback.
First, the "we" is me, Elizabeth Belding-Royer (a faculty member here who
is active with Charlie Perkins in the Ad hoc area), and our usual group of
students.
Second, we are building (soon to be "have built") a plug-in that allows a
laptop to run in true ad hoc mode. The idea is to use other such laptops to
build a "real" ad hoc network. My personal idea is to be able to use these
ad hoc nodes to extend connectivity into the upper floors of the hotel. A
better idea would be if there is an area that could use wireless access,
but for some reason (money, AP access, etc.) there won't be. Based on what
ya'll know about the layout, do you have any idea on whether Minn will have
this?
Third, we want to conduct a parallel experiment to start doing a better job
tracking and collecting stats about what is happening on the wireless
network. I wanted to do this in Vienna but the goobers couldn't figure out
how to do what I wanted. Basically, I'd like to periodically dump a variety
of SNMP data from the APs. The problems in Vienna seemed to be that they'd
already configured the APs to ONLY listen to one address and they'd also
configured them to ONLY do fault alarms... So, anyway we can set up to
collect decent information?
Thanks for your support. :-)
-Kevin
------------------------------------------------------------
Message #4 From Michael Richardson (almost in its entirety...extraneous
sentence omitted)
(NOTE: Brett sent Michael Richardson and Kevin Almeroth a note asking for
more details about their testing plans for Minneapolis. He cc'd the
mailing list for his IETF "meeting crew" on the note. Message #4 is
Michael Richardson's response to Brett's note.)
Subject: Re: Testing at the IETF
Date: Tuesday 09 September 2003 15:20
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
To: Brett Thorson <bthorson@foretec.com>
Cc: "Kevin C. Almeroth" <almeroth@cs.ucsb.edu>
>>>>> "Brett" == Brett Thorson <bthorson@foretec.com> writes:
Brett> Hi there Michael & Kevin.
Brett> It has come to my attention that both of you would like to do some
Brett> testing at the IETF meetings (and from what I understand, at the
Brett> Minneapolis IETF meeting). The Acting IETF Director has discussed
Brett> this idea with Harald (The IETF Chair) and he would like me to
Brett> collect from you a description of what you will be testing /
Brett> providing, and your goals.
I am not specifically interesting in doing it *at* IETF, but rather
immediately preceeding - Friday/Saturday.
My impression from being involved with network setup is that it is much
easier to be the guinea pigs as the network goes up, rather than try and
get the network to remain up after Friday.
And in general, I was hoping that this could become a tradition rather
than just an incidental occurance.
Brett> If you could get this to me by 1300 Eastern Time Thursday
Brett> 2003/11/09, I can then submit it for the weekly discussion.
The protocols that I have in mind are:
IPsec IKEv2
DNSSEC
I can not be certain at this time that there is sufficient interest in
either of them at this time, but I will attempt to determine this by
Thursday.
------------------------------------------------------------
Message #5 From Michael Richardson (in its entirety)
(NOTE: Chris Liljenstolpe, who is on the mailing list for Brett's "meeting
crew," responded to Brett's note with a question, and Michael Richardson
responded to Chris. Message #5 is Michael's response to Chris's question.)
Subject: Re: [58crew] Testing at the IETF
Date: Tuesday 09 September 2003 15:29
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
To: Chris Liljenstolpe <cds@io.com>
Cc: Brett Thorson <bthorson@foretec.com>, "Kevin C. Almeroth"
<almeroth@cs.ucsb.edu>
>>>>> "Chris" == Chris Liljenstolpe <cds@io.com> writes:
Chris> What kind of testing?
I can't speak for Kevin, since I don't know what he is after.
In general, what we are looking for is a tradition of having some
room(s) with a network drop that becomes live on the IETF network earlier,
ideally Friday morning. With real IPv4 and IPv6 space alive.
Pretty much anyone who wants to do testing winds up needing some amount
of Internet, but we one 9 of reliability is probably enough.
What? DNSSEC, IPsec is what I do.
I think most groups could easily deal with bring hubs/switches, etc. We
would not bring wireless if asked not to.
------------------------------------------------
Barbara B. Fuller
Acting Executive Director
Internet Engineering Task Force
Natick, Massachusetts Office:
Phone: +1-508-650-4020
Fax: +1-508-650-4639
Reston, Virginia Office:
Phone: +1-703-620-9053
Fax: +1-703-620-9071