IPv6IMP List Request (DO NOT RESPOND TO THIS MAIL)

bound@zk3.dec.com Tue, 09 May 1995 02:42 UTC

Errors-To: droms@zk3.dec.com
Message-Id: <9505081615.AA20193@xirtlu.zk3.dec.com>
To: ipng@sunroof.eng.sun.com, addrconf@cisco.com, host-conf@sol, sdrp@catarina.usc.edu, ietf-rip@xylogics.com, namedroppers@internic.net, bgp@ans.net, ospf@gated.cornell.edu, ipsec-request@ans.net
Cc: bound@zk3.dec.com
Subject: IPv6IMP List Request (DO NOT RESPOND TO THIS MAIL)
Date: Mon, 08 May 95 12:15:06 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: bound@zk3.dec.com

Please do not send me further requests to get on the IPv6 implementors
list.  Send them to:

   ipv6imp-request@munnari.oz.au

thanks
/jim 

Return-Path: owner-IPv6Imp@munnari.OZ.AU
Received: from decvax.zk3.dec.com by alpha.zk3.dec.com; (5.65/1.1.8.2/15Sep94-0303PM)
	id AA07691; Mon, 1 May 1995 15:35:27 -0400
Received: from murtoa.cs.mu.OZ.AU by decvax.dec.com (5.65/DEC-ULTRIX-8/19/92)
	id AA17128; Mon, 1 May 1995 15:35:22 -0400
Received: from mailing-list by murtoa.cs.mu.OZ.AU (8.6.9/1.0)
	id FAA14715; Tue, 2 May 1995 05:28:00 +1000
Received: from munnari.oz.au by murtoa.cs.mu.OZ.AU (8.6.9/1.0) with SMTP
	id FAA14695; Tue, 2 May 1995 05:18:32 +1000
Precedence: list
From: bound@zk3.dec.com
Received: from inet-gw-3.pa.dec.com by munnari.oz.au with SMTP (5.83--+1.3.1+0.50)
	id AA01404; Tue, 2 May 1995 05:18:14 +1000 (from bound@zk3.dec.com)
Received: from xirtlu.zk3.dec.com by inet-gw-3.pa.dec.com (5.65/24Feb95)
	id AA16732; Mon, 1 May 95 12:12:02 -0700
Received: by xirtlu.zk3.dec.com; id AA10889; Mon, 1 May 1995 15:11:53 -0400
Message-Id: <9505011911.AA10889@xirtlu.zk3.dec.com>
To: IPv6Imp@munnari.OZ.AU
Subject: [IPv6Imp] Purpose of IPv6 Implementors List  
Date: Mon, 01 May 95 15:11:47 -0400
X-Mts: smtp

Hi,

The purpose of the IPv6 Implementors list is to provide a forum to
discuss IPv6 implementations, develop testing scripts and plans, and to
determine future dates for IPv6 interoperability testing events.  It is
not the purpose of this list to discuss any proposed changes to any of
the IPv6 draft standards or to-be developed IETF draft standards.  If we
find that there is a "potential" error in a particular draft standard during 
the course of an implementors discussion the person whom uncovered a potential
error should send that directly to the IETF WG mail list.

I apologize for not getting this genric announcment out quicker, but I
have not been around for a few days and just got back.  I will have a
template of the test scenarios for discussion and review early next week.

I want to thank Robert Elz for setting up this list for us and really
appreciated the help.

take care,
/jim