From IP1394@mailbag.cps.intel.com  Mon Jun  5 02:11:05 2000
Received: from mailbag.cps.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26364
	for <ip1394-archive@LISTS.IETF.ORG>; Mon, 5 Jun 2000 02:11:04 -0400 (EDT)
Received: from mailbag.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24 22:10:56 iwep Exp iwep $) with ESMTP id WAA28621;
	Sun, 4 Jun 2000 22:29:55 -0700 (PDT)
Received: from MAILBAG.INTEL.COM by MAILBAG.INTEL.COM (LISTSERV-TCP/IP release
          1.8d) with spool id 228693 for IP1394@MAILBAG.INTEL.COM; Sun, 4 Jun
          2000 22:29:53 -0700
Received: from mail.visualcities.com (MAIL.VISUALCITIES.COM [208.197.229.7]) by
          mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24
          22:10:56 iwep Exp iwep $) with SMTP id WAA28573 for
          <ip1394@mailbag.intel.com>; Sun, 4 Jun 2000 22:19:52 -0700 (PDT)
Received: from mail.visualcities.com ([])by NT_VCM_SERVER(MailMax 3.033) with
          ESMTP id 1890805 for loseweightfast@visualcities.com; Mon, 05 Jun
          2000 01:17:42 -0400 EDT
Message-ID:  <200006050519.WAA28573@mailbag.cps.intel.com>
Date:         Sun, 4 Jun 2000 22:19:52 -0700
Reply-To: loseweightfast@VISUALCITIES.COM
Sender: IETF IP over 1394 Working Group <IP1394@mailbag.cps.intel.com>
From: loseweightfast@VISUALCITIES.COM
Subject:      FREE SAMPLE!  Look and feel great!  100% Guarantee!
To: IP1394@mailbag.cps.intel.com

    ,

100% Money Back Guarantee and FREE SAMPLES!!!

http://www.aaadiet.com

"I Lost 40 Pounds in 2 Months!  So can YOU!!!"


1-800-701-THIN (8446)


FREE SAMPLES HAVE BEEN ARRANGED FOR YOU!!!


Come and see what 30 Million have and are using to Look And Feel GREAT!!!



We Specialize in Weight Loss, Weight Gain and in the Finest Nutrition, Health and Fitness, Beauty and Personal Care in the WORLD.  Now in 47 Countries!

http://www.aaadiet.com





________________________________________________________
This Message was Sent To You BY REQUEST.  IF you wish to be removed from all future mailings, please reply with the subject "Remove" and this software will automatically block you
from all future mailings.  INCLUDING OUR FREE OFFERS AND SWEEPSTAKES!!!


From IP1394@mailbag.cps.intel.com  Thu Jun  8 13:23:29 2000
Received: from mailbag.cps.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12517
	for <ip1394-archive@LISTS.IETF.ORG>; Thu, 8 Jun 2000 13:23:29 -0400 (EDT)
Received: from mailbag.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24 22:10:56 iwep Exp iwep $) with ESMTP id JAA28914;
	Thu, 8 Jun 2000 09:39:43 -0700 (PDT)
Received: from MAILBAG.INTEL.COM by MAILBAG.INTEL.COM (LISTSERV-TCP/IP release
          1.8d) with spool id 231936 for IP1394@MAILBAG.INTEL.COM; Thu, 8 Jun
          2000 09:39:41 -0700
Received: from mta5.rcsntx.swbell.net (mta5.rcsntx.swbell.net [151.164.30.29])
          by mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24
          22:10:56 iwep Exp iwep $) with ESMTP id JAA28808 for
          <ip1394@mailbag.intel.com>; Thu, 8 Jun 2000 09:29:39 -0700 (PDT)
Received: from zainprov ([207.193.24.81]) by mta5.rcsntx.swbell.net (Sun
          Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with SMTP id
          <0FVU00D84F8Y39@mta5.rcsntx.swbell.net> for ip1394@mailbag.intel.com;
          Thu,  8 Jun 2000 11:05:28 -0500 (CDT)
Date-warning: Date header was inserted by mta5.rcsntx.swbell.net
MIME-version: 1.0
Content-type: text/plain; charset=unknown-8bit
Message-ID:  <0FVU00DQ4FD239@mta5.rcsntx.swbell.net>
Date:         Thu, 8 Jun 2000 11:05:28 -0500
Reply-To: zainprov@SWBELL.NET
Sender: IETF IP over 1394 Working Group <IP1394@mailbag.cps.intel.com>
From: zainprov@SWBELL.NET
Subject:      Shocking LOSE 10-100lbs. DESTINY
To: IP1394@mailbag.cps.intel.com

Hello From Destiny,

You will LOOSE 20-100 pounds easy!
Do to Such a high demand for Destiny, we are able
To Dramatically reduce our price for the entire System!
You will LOVE our incredible offer on this
Scientific Breakthrough in Weight Loss.
Now with a 105% Money Back Guarantee!
LOOK! http://home.swbell.net/zainprov/destiny.htm



We hope things are going well for you.  Good luck, God Bless, and
HAVE A GREAT DAY!



Either you are someone else subscribed to our list.  To be removed
Simply reply with a blank email.

Thank you,

Sherry Wilson


From IP1394@mailbag.cps.intel.com  Tue Jun 13 09:10:21 2000
Received: from mailbag.cps.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06551
	for <ip1394-archive@LISTS.IETF.ORG>; Tue, 13 Jun 2000 09:10:21 -0400 (EDT)
Received: from mailbag.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24 22:10:56 iwep Exp iwep $) with ESMTP id FAA00345;
	Tue, 13 Jun 2000 05:20:58 -0700 (PDT)
Received: from MAILBAG.INTEL.COM by MAILBAG.INTEL.COM (LISTSERV-TCP/IP release
          1.8d) with spool id 231333 for IP1394@MAILBAG.INTEL.COM; Tue, 13 Jun
          2000 05:20:56 -0700
Received: from jarramas.karlskrona.se ([195.84.83.57]) by mailbag.cps.intel.com
          (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24 22:10:56 iwep Exp iwep $)
          with ESMTP id FAA00233 for <ip1394@mailbag.intel.com>; Tue, 13 Jun
          2000 05:10:54 -0700 (PDT)
Received: from host (ip148.providence11.ri.pub-ip.psi.net [38.26.242.148]) by
          jarramas.karlskrona.se (8.8.8/8.8.8) with ESMTP id OAA11044; Tue, 13
          Jun 2000 14:05:47 +0200
X-Mailer: Microsoft Outlook Express 4.72.1712.3
X-MimeOLE: Produced By Microsoft MimeOLE V(null).1712.3
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by mailbag.cps.intel.com id
                      FAA00234
Message-ID:  <200006131205.OAA11044@jarramas.karlskrona.se>
Date:         Tue, 13 Jun 2000 07:01:08 -0500
Reply-To: Owen Reed <25mmt@SAFE-MAIL.NET>
Sender: IETF IP over 1394 Working Group <IP1394@mailbag.cps.intel.com>
From: Owen Reed <25mmt@SAFE-MAIL.NET>
Subject:      Your business depends on it #1E89
Comments: To: trust29d@jarramas.karlskrona.se
To: IP1394@mailbag.cps.intel.com
Content-Transfer-Encoding: 8bit

Email marketing is starting to boom and
you're probably wondering how you can
capitalize on this phenomenal advertising
method. Well..here is your chance!

As e-commerce grows, you need to stay
on top of your competition and keep up with
the technology.

GENIUS MARKETING STRATEGIES CAN HELP!

We can target a market that will advertise
your business effectively. NATIONWIDE OR
LOCAL TARGETING IS AVAILABLE!

You've probably seen millions of email addresses
on CD's for $50 or lots of companies offering
deals that seem too good to be true...
Well, they are!

We are professional email marketers who
take pride in our excellent customer service.

RATED #1 EMAIL MARKETERS IN
ENTREPRENEUR MAGAZINE

Get a head start on your competition today
with FREE ADVERTISING CONSULTING from
Genius Marketing Strategies.

Please Call 401-433-5811


We accept:
VISA, MASTER CARD, AND AMERICAN EXPRESS
OR CHECK BY FAX OR PHONE.


***********************************************************
Since you have received this message you have either responded
to one of our offers in the past or your address has been
registered with us. If you wish to be removed please reply to:
mailto:merch345@yahoo.com?subject=remove
************************************************************


From IP1394@mailbag.cps.intel.com  Tue Jun 13 15:43:07 2000
Received: from mailbag.cps.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20289
	for <ip1394-archive@LISTS.IETF.ORG>; Tue, 13 Jun 2000 15:43:06 -0400 (EDT)
Received: from mailbag.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24 22:10:56 iwep Exp iwep $) with ESMTP id MAA05177;
	Tue, 13 Jun 2000 12:01:29 -0700 (PDT)
Received: from MAILBAG.INTEL.COM by MAILBAG.INTEL.COM (LISTSERV-TCP/IP release
          1.8d) with spool id 232003 for IP1394@MAILBAG.INTEL.COM; Tue, 13 Jun
          2000 12:01:27 -0700
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by
          mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24
          22:10:56 iwep Exp iwep $) with ESMTP id LAA05101 for
          <ip1394@mailbag.cps.intel.com>; Tue, 13 Jun 2000 11:51:26 -0700 (PDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu
          (8.9.3/8.9.3) with ESMTP id LAA14978; Tue, 13 Jun 2000 11:49:03 -0700
          (PDT)
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Message-ID:  <200006131849.LAA14978@boreas.isi.edu>
Date:         Tue, 13 Jun 2000 11:49:03 -0700
Reply-To: RFC Editor <rfc-ed@ISI.EDU>
Sender: IETF IP over 1394 Working Group <IP1394@mailbag.cps.intel.com>
Comments:     RFC822 error: <W> Incorrect or incomplete address field found and
              ignored.
From: RFC Editor <rfc-ed@ISI.EDU>
Subject:      RFC 2855 on DHCP for IEEE 1394
Comments: cc: ip1394@mailbag.cps.intel.com
To: IP1394@mailbag.cps.intel.com

--NextPart


A new Request for Comments is now available in online RFC libraries.


        RFC 2855

        Title:      DHCP for IEEE 1394
        Author(s):  K. Fujisawa
        Status:     Standards Track
        Date:       June 2000
        Mailbox:    fujisawa@sm.sony.co.jp
        Pages:      5
        Characters: 8070
        Updates/Obsoletes/SeeAlso: None

        I-D Tag:    draft-ietf-ip1394-dhcp-04.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2855.txt


IEEE Std 1394-1995 is a standard for a High Performance Serial Bus.
Since 1394 uses a different link-layer addressing method than
conventional IEEE802/Ethernet, the usage of some fields must be
clarified to achieve interoperability.  This memo describes the 1394
specific usage of some fields of DHCP messages.

This document is a product of the IP Over IEEE 1394 Working Group of
the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type:  Message/External-body;
        access-type="mail-server";
        server="RFC-INFO@RFC-EDITOR.ORG"

Content-Type: text/plain
Content-ID: <000613114642.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc2855

--OtherAccess
Content-Type:   Message/External-body;
        name="rfc2855.txt";
        site="ftp.isi.edu";
        access-type="anon-ftp";
        directory="in-notes"

Content-Type: text/plain
Content-ID: <000613114642.RFC@RFC-EDITOR.ORG>

--OtherAccess--
--NextPart--


From IP1394@mailbag.cps.intel.com  Mon Jun 19 18:19:27 2000
Received: from mailbag.cps.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24553
	for <ip1394-archive@LISTS.IETF.ORG>; Mon, 19 Jun 2000 18:19:27 -0400 (EDT)
Received: from mailbag.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24 22:10:56 iwep Exp iwep $) with ESMTP id OAA04179;
	Mon, 19 Jun 2000 14:36:38 -0700 (PDT)
Received: from MAILBAG.INTEL.COM by MAILBAG.INTEL.COM (LISTSERV-TCP/IP release
          1.8d) with spool id 234220 for IP1394@MAILBAG.INTEL.COM; Mon, 19 Jun
          2000 14:36:36 -0700
Received: from orsmsx28.jf.intel.com (orsmsx28.jf.intel.com [192.168.65.28]) by
          mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24
          22:10:56 iwep Exp iwep $) with ESMTP id OAA04172 for
          <ip1394@mailbag.intel.com>; Mon, 19 Jun 2000 14:36:35 -0700 (PDT)
Received: by orsmsx28.jf.intel.com with Internet Mail Service (5.5.2448.0) id
          <M6LLX77Z>; Mon, 19 Jun 2000 14:34:15 -0700
X-Mailer: Internet Mail Service (5.5.2448.0)
Message-ID:  <4148FEAAD879D311AC5700A0C969E8904F2A4A@orsmsx35.jf.intel.com>
Date:         Mon, 19 Jun 2000 14:34:12 -0700
Reply-To: "Hattig, Myron" <myron.hattig@INTEL.COM>
Sender: IETF IP over 1394 Working Group <IP1394@mailbag.cps.intel.com>
From: "Hattig, Myron" <myron.hattig@INTEL.COM>
Subject:      IP/1394 WG close
To: IP1394@mailbag.cps.intel.com

Congratulations to everyone for their hardwork for completing RFC 2734 IPv4
over 1394 and the recently announced RFC 2855 that defines DHCP extensions
for 1394.

Special thanks to Peter Johansson and Kenji Fujisawa for their beginning-to-end
effort that started a little more than three years. Both Peter and Kenji
consistently acted as accurate technical references to help the group move
forward. Also, special thanks to the developers at Sony, Intel, Microsoft,
NEC, Intoto, and HCL for their outstanding implementations during the
interoperability tests.

So what does it mean that the IP/1394 WG is closing?

Well, those interested in continuing on IPv6 over 1394 or IP over 1394 isoch
streams should consult with Thomas Narten and Erik Nordmark, the Area
Directors for IP/1934 WG, to request a BOF or to publish informational RFCs.
The current drafts on these topics will be removed from the IETF pages as
they expire.

Our web page, http://www.ietf.org/html.charters/ip1394-charter.html, will
be going away in a matter of days.

This list will remain active for as long as it remains useful; however,
this email is the first useful message posted on this list in months. I
suspect this list will be gone by the end of the summer.

It's been a pleasure working with and meeting everyone.

Best regards,

Myron Hattig
WG Co-Chair


From IP1394@mailbag.cps.intel.com  Mon Jun 19 23:26:54 2000
Received: from mailbag.cps.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29732
	for <ip1394-archive@LISTS.IETF.ORG>; Mon, 19 Jun 2000 23:26:53 -0400 (EDT)
Received: from mailbag.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24 22:10:56 iwep Exp iwep $) with ESMTP id TAA07154;
	Mon, 19 Jun 2000 19:45:38 -0700 (PDT)
Received: from MAILBAG.INTEL.COM by MAILBAG.INTEL.COM (LISTSERV-TCP/IP release
          1.8d) with spool id 234412 for IP1394@MAILBAG.INTEL.COM; Mon, 19 Jun
          2000 19:45:37 -0700
Received: from agni.wipinfo.soft.net (agni.wipinfo.soft.net [164.164.6.20]) by
          mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24
          22:10:56 iwep Exp iwep $) with ESMTP id TAA07101 for
          <IP1394@mailbag.cps.intel.com>; Mon, 19 Jun 2000 19:35:32 -0700 (PDT)
Received: from vayu.wipinfo.soft.net (vayu [192.168.200.170]) by
          agni.wipinfo.soft.net (8.9.3/8.9.3) with ESMTP id HAA02897 for
          <IP1394@mailbag.cps.intel.com>; Tue, 20 Jun 2000 07:59:35 +0500 (GMT)
Received: from ozone.mail.wipro.com (ozone [192.168.151.18]) by
          vayu.wipinfo.soft.net (8.9.3/8.9.3) with ESMTP id IAA13594 for
          <IP1394@mailbag.cps.intel.com>; Tue, 20 Jun 2000 08:01:55 +0500 (GMT)
Received: from gnraj ([192.168.151.7]) by ozone.mail.wipro.com (Netscape
          Messaging Server 3.6)  with SMTP id AAA6303; Tue, 20 Jun 2000
          08:05:28 +0530
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Message-ID:  <NDBBLNNGMCKNAMJCHDHKIEKLIGAA.g.nagaraj@wipro.com>
Date:         Tue, 20 Jun 2000 08:22:18 +0530
Reply-To: g.nagaraj@wipro.com
Sender: IETF IP over 1394 Working Group <IP1394@mailbag.cps.intel.com>
From: "G. Nagaraj" <g.nagaraj@wipro.com>
Subject:      Re: IP/1394 WG close
Comments: To: "Hattig, Myron" <myron.hattig@INTEL.COM>,
          IP1394@mailbag.cps.intel.com
To: IP1394@mailbag.cps.intel.com
In-Reply-To:  <4148FEAAD879D311AC5700A0C969E8904F2A4A@orsmsx35.jf.intel.com>
Content-Transfer-Encoding: 7bit

Thank you very much Myron for the great work in getting such good RFCs.

I would like to add EnThink also to the list of successful Interoperability
Testers (March).

I hope the IPv6 over 1394 will start before the closure of WG or it might
open a new WG. Let us wait and see if any positive responses are there.

Thanks again.

Regards,

G. Nagaraj

-----Original Message-----
From: IETF IP over 1394 Working Group
[mailto:IP1394@mailbag.cps.intel.com]On Behalf Of Hattig, Myron
Sent: Tuesday, June 20, 2000 3:04 AM
To: IP1394@mailbag.cps.intel.com
Subject: IP/1394 WG close


Congratulations to everyone for their hardwork for completing RFC 2734 IPv4
over 1394 and the recently announced RFC 2855 that defines DHCP extensions
for 1394.

Special thanks to Peter Johansson and Kenji Fujisawa for their
beginning-to-end
effort that started a little more than three years. Both Peter and Kenji
consistently acted as accurate technical references to help the group move
forward. Also, special thanks to the developers at Sony, Intel, Microsoft,
NEC, Intoto, and HCL for their outstanding implementations during the
interoperability tests.

So what does it mean that the IP/1394 WG is closing?

Well, those interested in continuing on IPv6 over 1394 or IP over 1394 isoch
streams should consult with Thomas Narten and Erik Nordmark, the Area
Directors for IP/1934 WG, to request a BOF or to publish informational RFCs.
The current drafts on these topics will be removed from the IETF pages as
they expire.

Our web page, http://www.ietf.org/html.charters/ip1394-charter.html, will
be going away in a matter of days.

This list will remain active for as long as it remains useful; however,
this email is the first useful message posted on this list in months. I
suspect this list will be gone by the end of the summer.

It's been a pleasure working with and meeting everyone.

Best regards,

Myron Hattig
WG Co-Chair


From IP1394@mailbag.cps.intel.com  Thu Jun 22 08:50:47 2000
Received: from mailbag.cps.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03264
	for <ip1394-archive@LISTS.IETF.ORG>; Thu, 22 Jun 2000 08:50:46 -0400 (EDT)
Received: from mailbag.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24 22:10:56 iwep Exp iwep $) with ESMTP id FAA14559;
	Thu, 22 Jun 2000 05:09:13 -0700 (PDT)
Received: from MAILBAG.INTEL.COM by MAILBAG.INTEL.COM (LISTSERV-TCP/IP release
          1.8d) with spool id 233190 for IP1394@MAILBAG.INTEL.COM; Thu, 22 Jun
          2000 05:09:11 -0700
Received: from hygro.adsl.duke.edu (hygro.adsl.duke.edu [152.16.64.159]) by
          mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24
          22:10:56 iwep Exp iwep $) with ESMTP id FAA14552 for
          <IP1394@mailbag.cps.intel.com>; Thu, 22 Jun 2000 05:09:10 -0700 (PDT)
Received: from hygro.adsl.duke.edu (IDENT:narten@localhost.localdomain
          [127.0.0.1]) by hygro.adsl.duke.edu (8.9.3/8.9.3) with ESMTP id
          IAA01668; Thu, 22 Jun 2000 08:06:42 -0400
Message-ID:  <200006221206.IAA01668@hygro.adsl.duke.edu>
Date:         Thu, 22 Jun 2000 08:06:42 -0400
Reply-To: Thomas Narten <narten@RALEIGH.IBM.COM>
Sender: IETF IP over 1394 Working Group <IP1394@mailbag.cps.intel.com>
From: Thomas Narten <narten@RALEIGH.IBM.COM>
Subject:      Re: IP/1394 WG close
Comments: To: g.nagaraj@wipro.com
Comments: cc: Steve Deering <deering@cisco.com>,
          Bob Hinden <hinden@iprg.nokia.com>,
          IP1394@mailbag.cps.intel.com, fujisawa@sm.sony.co.jp
To: IP1394@mailbag.cps.intel.com
In-Reply-To:  Message from "G. Nagaraj" <g.nagaraj@wipro.com> of "Tue, 20 Jun
              2000 08:22:18 +0530."
              <NDBBLNNGMCKNAMJCHDHKIEKLIGAA.g.nagaraj@wipro.com>

"G. Nagaraj" <g.nagaraj@wipro.com> writes:

> Thank you very much Myron for the great work in getting such good RFCs.

> I would like to add EnThink also to the list of successful Interoperability
> Testers (March).

> I hope the IPv6 over 1394 will start before the closure of WG or it might
> open a new WG. Let us wait and see if any positive responses are there.

Do you (or anyone else for that matter) have interest in working on
such a document? And do you have a sense for how *soon* an IPv6 over
1394 document will be needed?

Context: I think a lot of folks would like to see such a document, but
when the mailing list was asked in the past, there was a conspicuous
lack of volunteers to come forward to do the work. :-) Perhaps that
has changed, now that the 1394 over IPv4 work is done.

I would certainly be interested in seeing a critical mass of people (2
or 3 might even be enough) commit to tackling this problem.

Note also that there is an (old) expired ID on the topic
(draft-fujisawa-ip1394-ipv6-03.txt). I have no idea of how out of date
it is relative to the work that has been done for IPv4 over 1394. It
expired over a year ago.

Thomas


From IP1394@mailbag.cps.intel.com  Thu Jun 22 23:52:23 2000
Received: from mailbag.cps.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA21536
	for <ip1394-archive@LISTS.IETF.ORG>; Thu, 22 Jun 2000 23:52:23 -0400 (EDT)
Received: from mailbag.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24 22:10:56 iwep Exp iwep $) with ESMTP id TAA24564;
	Thu, 22 Jun 2000 19:58:32 -0700 (PDT)
Received: from MAILBAG.INTEL.COM by MAILBAG.INTEL.COM (LISTSERV-TCP/IP release
          1.8d) with spool id 234346 for IP1394@MAILBAG.INTEL.COM; Thu, 22 Jun
          2000 19:58:31 -0700
Received: from agni.wipinfo.soft.net (agni.wipinfo.soft.net [164.164.6.20]) by
          mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24
          22:10:56 iwep Exp iwep $) with ESMTP id TAA24557 for
          <IP1394@mailbag.cps.intel.com>; Thu, 22 Jun 2000 19:58:18 -0700 (PDT)
Received: from vayu.wipinfo.soft.net (vayu [192.168.200.170]) by
          agni.wipinfo.soft.net (8.9.3/8.9.3) with ESMTP id IAA20609 for
          <IP1394@mailbag.cps.intel.com>; Fri, 23 Jun 2000 08:22:09 +0500 (GMT)
Received: from ozone.mail.wipro.com (ozone [192.168.151.18]) by
          vayu.wipinfo.soft.net (8.9.3/8.9.3) with ESMTP id IAA04231 for
          <IP1394@mailbag.cps.intel.com>; Fri, 23 Jun 2000 08:24:31 +0500 (GMT)
Received: from gnraj ([192.168.151.7]) by ozone.mail.wipro.com (Netscape
          Messaging Server 3.6)  with SMTP id AAA1D3D; Fri, 23 Jun 2000
          08:28:06 +0530
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Message-ID:  <NDBBLNNGMCKNAMJCHDHKCENIIGAA.g.nagaraj@wipro.com>
Date:         Fri, 23 Jun 2000 08:32:56 +0530
Reply-To: g.nagaraj@wipro.com
Sender: IETF IP over 1394 Working Group <IP1394@mailbag.cps.intel.com>
From: "G. Nagaraj" <g.nagaraj@wipro.com>
Subject:      Re: IP/1394 WG close
Comments: To: Thomas Narten <narten@raleigh.ibm.com>
Comments: cc: Steve Deering <deering@cisco.com>,
          Bob Hinden <hinden@iprg.nokia.com>,
          IP1394@mailbag.cps.intel.com, fujisawa@sm.sony.co.jp
To: IP1394@mailbag.cps.intel.com
In-Reply-To:  <200006221206.IAA01668@hygro.adsl.duke.edu>
Content-Transfer-Encoding: 7bit

I do have interest in working on such a document. But I am not sure how
helpful will I be as I haven't studied IPv6 fully. I can complete my study
of IPv6 and start my contribution to the IPv6 over 1394 document. And I
don't see any problem other than taking permission from my employer.

Now, regarding how soon such a document will be needed, I don't have an
idea. The question comes back to the number of implementations of IPv6 over
Ethernet. As the Internet is still on IPv4 (as far as I know), the drive for
IPv6 is not so heavy. I don't see even Microsoft / Linux / any other OS with
IPv6 support right now for Ethernet. So the question of *soon* is very
difficult to answer.

Might be by the time we complete the IPv6 over 1394 document, which I expect
will take at least a year, I expect the IPv6 to be in almost all the
platforms by at least in 1.5 years.

-Nagaraj

-----Original Message-----
From: Thomas Narten [mailto:narten@raleigh.ibm.com]
Sent: Thursday, June 22, 2000 5:37 PM
To: g.nagaraj@wipro.com
Cc: Steve Deering; Bob Hinden; IP1394@mailbag.cps.intel.com;
fujisawa@sm.sony.co.jp
Subject: Re: IP/1394 WG close


"G. Nagaraj" <g.nagaraj@wipro.com> writes:

> Thank you very much Myron for the great work in getting such good RFCs.

> I would like to add EnThink also to the list of successful
Interoperability
> Testers (March).

> I hope the IPv6 over 1394 will start before the closure of WG or it might
> open a new WG. Let us wait and see if any positive responses are there.

Do you (or anyone else for that matter) have interest in working on
such a document? And do you have a sense for how *soon* an IPv6 over
1394 document will be needed?

Context: I think a lot of folks would like to see such a document, but
when the mailing list was asked in the past, there was a conspicuous
lack of volunteers to come forward to do the work. :-) Perhaps that
has changed, now that the 1394 over IPv4 work is done.

I would certainly be interested in seeing a critical mass of people (2
or 3 might even be enough) commit to tackling this problem.

Note also that there is an (old) expired ID on the topic
(draft-fujisawa-ip1394-ipv6-03.txt). I have no idea of how out of date
it is relative to the work that has been done for IPv4 over 1394. It
expired over a year ago.

Thomas


From IP1394@mailbag.cps.intel.com  Fri Jun 23 00:16:03 2000
Received: from mailbag.cps.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA21705
	for <ip1394-archive@LISTS.IETF.ORG>; Fri, 23 Jun 2000 00:16:03 -0400 (EDT)
Received: from mailbag.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24 22:10:56 iwep Exp iwep $) with ESMTP id UAA24790;
	Thu, 22 Jun 2000 20:27:43 -0700 (PDT)
Received: from MAILBAG.INTEL.COM by MAILBAG.INTEL.COM (LISTSERV-TCP/IP release
          1.8d) with spool id 234365 for IP1394@MAILBAG.INTEL.COM; Thu, 22 Jun
          2000 20:27:41 -0700
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
          by mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24
          22:10:56 iwep Exp iwep $) with ESMTP id UAA24740 for
          <IP1394@mailbag.cps.intel.com>; Thu, 22 Jun 2000 20:17:40 -0700 (PDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
          by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id UAA26051;
          Thu, 22 Jun 2000 20:14:09 -0700 (PDT)
Received: (from root@localhost) by darkstar.iprg.nokia.com
          (8.9.3/8.9.3-VIRSCAN) id UAA01317; Thu, 22 Jun 2000 20:14:05 -0700
X-Virus-Scanned:  Thu, 22 Jun 2000 20:14:05 -0700 Nokia Silicon Valley Email
                  Exploit Scanner
Received: from <hinden@iprg.nokia.com> (ihinden-3.iprg.nokia.com
          [205.226.22.76]) by darkstar.iprg.nokia.com  SMTP/WTS (12.69)
          xma000731; Thu, 22 Jun 00 20:13:57 -0700
X-Sender: hinden@mailhost.iprg.nokia.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
References: <200006221206.IAA01668@hygro.adsl.duke.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Message-ID:  <4.3.2.7.2.20000622200848.0251ee78@mailhost.iprg.nokia.com>
Date:         Thu, 22 Jun 2000 20:11:54 -0700
Reply-To: Bob Hinden <hinden@IPRG.NOKIA.COM>
Sender: IETF IP over 1394 Working Group <IP1394@mailbag.cps.intel.com>
From: Bob Hinden <hinden@IPRG.NOKIA.COM>
Subject:      Re: IP/1394 WG close
Comments: To: g.nagaraj@wipro.com
Comments: cc: Thomas Narten <narten@raleigh.ibm.com>,
          Steve Deering <deering@cisco.com>,
          IP1394@mailbag.cps.intel.com, fujisawa@sm.sony.co.jp
To: IP1394@mailbag.cps.intel.com
In-Reply-To:  <NDBBLNNGMCKNAMJCHDHKCENIIGAA.g.nagaraj@wipro.com>

Nagaraj,

>Now, regarding how soon such a document will be needed, I don't have an
>idea. The question comes back to the number of implementations of IPv6 over
>Ethernet. As the Internet is still on IPv4 (as far as I know), the drive for
>IPv6 is not so heavy. I don't see even Microsoft / Linux / any other OS with
>IPv6 support right now for Ethernet. So the question of *soon* is very
>difficult to answer.

You can find a list of IPv6 implementations at

   http://playground.sun.com/ipng

Look on the implementations page.  There are IPv6 implementations listed
for all of the OS's you cite and I am pretty sure they all support IPv6
over Ethernet.

Bob


From IP1394@mailbag.cps.intel.com  Fri Jun 23 00:16:27 2000
Received: from mailbag.cps.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA21716
	for <ip1394-archive@LISTS.IETF.ORG>; Fri, 23 Jun 2000 00:16:27 -0400 (EDT)
Received: from mailbag.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24 22:10:56 iwep Exp iwep $) with ESMTP id UAA24776;
	Thu, 22 Jun 2000 20:26:10 -0700 (PDT)
Received: from MAILBAG.INTEL.COM by MAILBAG.INTEL.COM (LISTSERV-TCP/IP release
          1.8d) with spool id 234368 for IP1394@MAILBAG.INTEL.COM; Thu, 22 Jun
          2000 20:26:08 -0700
Received: from agni.wipinfo.soft.net (agni.wipinfo.soft.net [164.164.6.20]) by
          mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24
          22:10:56 iwep Exp iwep $) with ESMTP id UAA24769 for
          <IP1394@mailbag.cps.intel.com>; Thu, 22 Jun 2000 20:25:50 -0700 (PDT)
Received: from vayu.wipinfo.soft.net (vayu [192.168.200.170]) by
          agni.wipinfo.soft.net (8.9.3/8.9.3) with ESMTP id IAA22059 for
          <IP1394@mailbag.cps.intel.com>; Fri, 23 Jun 2000 08:49:44 +0500 (GMT)
Received: from ozone.mail.wipro.com (ozone [192.168.151.18]) by
          vayu.wipinfo.soft.net (8.9.3/8.9.3) with ESMTP id IAA06298 for
          <IP1394@mailbag.cps.intel.com>; Fri, 23 Jun 2000 08:52:06 +0500 (GMT)
Received: from gnraj ([192.168.151.7]) by ozone.mail.wipro.com (Netscape
          Messaging Server 3.6)  with SMTP id AAA2196; Fri, 23 Jun 2000
          08:55:40 +0530
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Message-ID:  <NDBBLNNGMCKNAMJCHDHKKENIIGAA.g.nagaraj@wipro.com>
Date:         Fri, 23 Jun 2000 09:00:31 +0530
Reply-To: g.nagaraj@wipro.com
Sender: IETF IP over 1394 Working Group <IP1394@mailbag.cps.intel.com>
From: "G. Nagaraj" <g.nagaraj@wipro.com>
Subject:      Re: IP/1394 WG close
Comments: To: Bob Hinden <hinden@iprg.nokia.com>
Comments: cc: Thomas Narten <narten@raleigh.ibm.com>,
          Steve Deering <deering@cisco.com>,
          IP1394@mailbag.cps.intel.com, fujisawa@sm.sony.co.jp
To: IP1394@mailbag.cps.intel.com
In-Reply-To:  <4.3.2.7.2.20000622200848.0251ee78@mailhost.iprg.nokia.com>
Content-Transfer-Encoding: 7bit

Thanks Bob,

I now know that the support is there. But I haven't seen a way of defining
an IPv6 address in Microsoft Windows Operating systems. If there is a
special way of doing it than from the normal network configurations, which I
am not aware of, then it is OK.

With all these OSs already supporting, then the expectation of the Internet
moving to IPv6 is not so far. Am I right? If the internet moves towards
IPv6, then I think the demand for IPv6 over 1394 is very high.

- Nagaraj

-----Original Message-----
From: Bob Hinden [mailto:hinden@iprg.nokia.com]
Sent: Friday, June 23, 2000 8:42 AM
To: g.nagaraj@wipro.com
Cc: Thomas Narten; Steve Deering; Bob Hinden;
IP1394@mailbag.cps.intel.com; fujisawa@sm.sony.co.jp
Subject: RE: IP/1394 WG close


Nagaraj,

>Now, regarding how soon such a document will be needed, I don't have an
>idea. The question comes back to the number of implementations of IPv6 over
>Ethernet. As the Internet is still on IPv4 (as far as I know), the drive
for
>IPv6 is not so heavy. I don't see even Microsoft / Linux / any other OS
with
>IPv6 support right now for Ethernet. So the question of *soon* is very
>difficult to answer.

You can find a list of IPv6 implementations at

   http://playground.sun.com/ipng

Look on the implementations page.  There are IPv6 implementations listed
for all of the OS's you cite and I am pretty sure they all support IPv6
over Ethernet.

Bob


From IP1394@mailbag.cps.intel.com  Fri Jun 23 14:17:13 2000
Received: from mailbag.cps.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16666
	for <ip1394-archive@LISTS.IETF.ORG>; Fri, 23 Jun 2000 14:17:13 -0400 (EDT)
Received: from mailbag.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24 22:10:56 iwep Exp iwep $) with ESMTP id KAA02147;
	Fri, 23 Jun 2000 10:31:57 -0700 (PDT)
Received: from MAILBAG.INTEL.COM by MAILBAG.INTEL.COM (LISTSERV-TCP/IP release
          1.8d) with spool id 233394 for IP1394@MAILBAG.INTEL.COM; Fri, 23 Jun
          2000 10:31:55 -0700
Received: from dfssl.exchange.microsoft.com (dfssl.exchange.microsoft.com
          [131.107.88.59]) by mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v
          1.6 1998/11/24 22:10:56 iwep Exp iwep $) with ESMTP id KAA02140 for
          <IP1394@MAILBAG.INTEL.COM>; Fri, 23 Jun 2000 10:31:54 -0700 (PDT)
Received: by DFSSL.dns.microsoft.com with Internet Mail Service (5.5.2652.35)
          id <NNNG8NT8>; Fri, 23 Jun 2000 10:21:38 -0700
X-Mailer: Internet Mail Service (5.5.2652.35)
Message-ID:  <078292D50C98D2118D090008C7E9C6A60ABE33D6@STAY.platinum.corp.microsoft.com>
Date:         Fri, 23 Jun 2000 10:22:28 -0700
Reply-To: Larry Cleeton <lcleeton@EXCHANGE.MICROSOFT.COM>
Sender: IETF IP over 1394 Working Group <IP1394@mailbag.cps.intel.com>
From: Larry Cleeton <lcleeton@EXCHANGE.MICROSOFT.COM>
Subject:      Re: IP/1394 WG close
Comments: To: Thomas Narten <narten@RALEIGH.IBM.COM>
To: IP1394@mailbag.cps.intel.com

Thomas and all,

Microsoft does have an interest in moving IP/1394 forward onto IPv6.  We
have a publicly available preview of an IPv6 implementation that works on
Windows 2000.  IPv6 is very important to Microsoft and to the Internet
community at large and you can expect to see increasing effort on our part
to deploy production quality IPv6. Our IP/1394 implementation for IPv4 is
part of our new consumer version of Windows called Windows Me (Millennium
Edition) that will be available at retail on Sept 14th.  It is our intention
to support IP/1394 on all our future releases of consumer products and our
enterprise and professional workstation products.

I am willing to commit resources to work on an IPv6 over 1394 document.

Larry Cleeton
Program Manager
Microsoft Corporation


-----Original Message-----
From: Thomas Narten [mailto:narten@RALEIGH.IBM.COM]
Sent: Thursday, June 22, 2000 5:07 AM
To: IP1394@MAILBAG.INTEL.COM
Subject: Re: IP/1394 WG close


"G. Nagaraj" <g.nagaraj@wipro.com> writes:

> Thank you very much Myron for the great work in getting such good RFCs.

> I would like to add EnThink also to the list of successful
Interoperability
> Testers (March).

> I hope the IPv6 over 1394 will start before the closure of WG or it might
> open a new WG. Let us wait and see if any positive responses are there.

Do you (or anyone else for that matter) have interest in working on
such a document? And do you have a sense for how *soon* an IPv6 over
1394 document will be needed?

Context: I think a lot of folks would like to see such a document, but
when the mailing list was asked in the past, there was a conspicuous
lack of volunteers to come forward to do the work. :-) Perhaps that
has changed, now that the 1394 over IPv4 work is done.

I would certainly be interested in seeing a critical mass of people (2
or 3 might even be enough) commit to tackling this problem.

Note also that there is an (old) expired ID on the topic
(draft-fujisawa-ip1394-ipv6-03.txt). I have no idea of how out of date
it is relative to the work that has been done for IPv4 over 1394. It
expired over a year ago.

Thomas


From IP1394@mailbag.cps.intel.com  Mon Jun 26 13:51:28 2000
Received: from mailbag.cps.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12068
	for <ip1394-archive@LISTS.IETF.ORG>; Mon, 26 Jun 2000 13:51:27 -0400 (EDT)
Received: from mailbag.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24 22:10:56 iwep Exp iwep $) with ESMTP id KAA03073;
	Mon, 26 Jun 2000 10:11:10 -0700 (PDT)
Received: from MAILBAG.INTEL.COM by MAILBAG.INTEL.COM (LISTSERV-TCP/IP release
          1.8d) with spool id 233560 for IP1394@MAILBAG.INTEL.COM; Mon, 26 Jun
          2000 10:11:09 -0700
Received: from fmsmsx27.FM.INTEL.COM (fmsmsx27.fm.intel.com [132.233.42.27]) by
          mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24
          22:10:56 iwep Exp iwep $) with ESMTP id KAA03066 for
          <ip1394@mailbag.intel.com>; Mon, 26 Jun 2000 10:11:06 -0700 (PDT)
Received: by fmsmsx27.fm.intel.com with Internet Mail Service (5.5.2650.21) id
          <N32L7N30>; Mon, 26 Jun 2000 10:08:44 -0700
X-Mailer: Internet Mail Service (5.5.2650.21)
Message-ID:  <4148FEAAD879D311AC5700A0C969E8904F2A94@orsmsx35.jf.intel.com>
Date:         Mon, 26 Jun 2000 10:08:41 -0700
Reply-To: "Hattig, Myron" <myron.hattig@INTEL.COM>
Sender: IETF IP over 1394 Working Group <IP1394@mailbag.cps.intel.com>
From: "Hattig, Myron" <myron.hattig@INTEL.COM>
Subject:      Interop Event  Report
To: IP1394@mailbag.cps.intel.com

Below is the report garneted by Larry Cleeton, Microsoft host of interop
event.
Thanks for hosting and the trip report, Larry!!!  In addition there are a
few
follow-up questions about MCAP implementations. The report and the questions
are
important for advancing RFC 2734 from Draft Standard to Proposed Standard.
Participants, please read the report for accuracy and answer the MCAP
questions.

----------------------------------------------------------------------------
Report:
An IP/1394 interoperability test event was held on March 16th and 17th, 2000
at the Microsoft Redmond campus.

Attendees:

Microsoft, Sony, NEC, Enthink, Zayante
Two key contributors to the IP/1394 effort were also present: Myron Hattig
and Peter Johansonn.

Tested Scenarios:

* Basic connectivity among IP/1394 peers: static ip; pings; large pings.
* Home: Internet access and private network access via VPN using Windows
  Millennium Edition ICS (NAT).
* Office: Interconnectivity (file transfer) and corpnet access (via VPN)
  using Windows 2000 server with NAT and DHCP.
* Multicast: Multicast connectivity using default broadcast channel, as well
  as passive and active MCAP.

Implementations tested:

* Three separately developed Windows implementations.
* Two separately developed VxWorks implementations
* One FreeBSD implementation.

Issues Discovered:

Some interoperability issues with DHCP need to be investigated further.

----------------------------------------------------------------------------
MCAP questions:
These questions are for those that implemented MCAP for the last interop
test.
If you want details of your implementation to remain secret, respond to me
personally and I'll repost to the reflector without identifying the
implementation. Here are the questions:

What parts of MCAP spec did you implement? What parts were successfully
tested? If not successful, what was the source of the problem? the spec
or the implementation?
1) channel mapping owner
2) mcast source but not channel mapping owner
3) mcast receiver
4) changing mapping ownership during the last 30 seconds of ownership

What other cases are important?

-myron


From IP1394@mailbag.cps.intel.com  Mon Jun 26 15:15:46 2000
Received: from mailbag.cps.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14124
	for <ip1394-archive@LISTS.IETF.ORG>; Mon, 26 Jun 2000 15:15:45 -0400 (EDT)
Received: from mailbag.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24 22:10:56 iwep Exp iwep $) with ESMTP id LAA04371;
	Mon, 26 Jun 2000 11:33:47 -0700 (PDT)
Received: from MAILBAG.INTEL.COM by MAILBAG.INTEL.COM (LISTSERV-TCP/IP release
          1.8d) with spool id 233712 for IP1394@MAILBAG.INTEL.COM; Mon, 26 Jun
          2000 11:33:45 -0700
Received: from mta5.snfc21.pbi.net ([206.13.28.241]) by mailbag.cps.intel.com
          (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24 22:10:56 iwep Exp iwep $)
          with ESMTP id LAA04126 for <IP1394@Mailbag.Intel.com>; Mon, 26 Jun
          2000 11:23:44 -0700 (PDT)
Received: from SERVER.PacBell.net ([63.199.7.253]) by mta5.snfc21.pbi.net (Sun
          Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id
          <0FWR004GPX5M9C@mta5.snfc21.pbi.net> for IP1394@Mailbag.Intel.com;
          Mon, 26 Jun 2000 11:10:35 -0700 (PDT)
X-Sender: Celeborn@PacBell.net
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Content-type: text/plain; charset="us-ascii"; format=flowed
Message-ID:  <4.3.2.7.2.20000626110435.00b81b00@PacBell.net>
Date:         Mon, 26 Jun 2000 11:05:02 -0700
Reply-To: Peter Johansson <PJohansson@ACM.ORG>
Sender: IETF IP over 1394 Working Group <IP1394@mailbag.cps.intel.com>
From: Peter Johansson <PJohansson@ACM.ORG>
Subject:      Next Interop Event
To: IP1394@mailbag.cps.intel.com

I think there is a need for another interoperability event, this time to be
focused upon DHCP and MCAP issues.

Such an event probably needs some advance planning on what is to be tested
and the test matrix we intend to use. Of course, as all past coordinators
can attest, it also needs significant logistical support.

What if we defer the question of when and where (for the time being) and
focus on the following:

1) Is there a perceived need for another event? Who would likely participate?

2) What are the test scenarios, DHCP and MCAP, for which we should prepare?

3) Is a possible outcome of the cumulative experience from these events a
compliance specification and/or tests? Has the IETF created such ancillary
documents and tests in the past?

Regards,

Peter Johansson

Congruent Software, Inc.
98 Colorado Avenue
Berkeley, CA  94707

(510) 527-3926
(510) 527-3856 FAX

PJohansson@ACM.org


From IP1394@mailbag.cps.intel.com  Tue Jun 27 07:46:30 2000
Received: from mailbag.cps.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08185
	for <ip1394-archive@LISTS.IETF.ORG>; Tue, 27 Jun 2000 07:46:29 -0400 (EDT)
Received: from mailbag.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24 22:10:56 iwep Exp iwep $) with ESMTP id EAA14180;
	Tue, 27 Jun 2000 04:03:16 -0700 (PDT)
Received: from MAILBAG.INTEL.COM by MAILBAG.INTEL.COM (LISTSERV-TCP/IP release
          1.8d) with spool id 233063 for IP1394@MAILBAG.INTEL.COM; Tue, 27 Jun
          2000 04:03:14 -0700
Received: from hygro.adsl.duke.edu (hygro.adsl.duke.edu [152.16.64.159]) by
          mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24
          22:10:56 iwep Exp iwep $) with ESMTP id EAA14173 for
          <IP1394@mailbag.cps.intel.com>; Tue, 27 Jun 2000 04:03:13 -0700 (PDT)
Received: from hygro.adsl.duke.edu (IDENT:narten@localhost.localdomain
          [127.0.0.1]) by hygro.adsl.duke.edu (8.9.3/8.9.3) with ESMTP id
          HAA01344; Tue, 27 Jun 2000 07:00:29 -0400
Message-ID:  <200006271100.HAA01344@hygro.adsl.duke.edu>
Date:         Tue, 27 Jun 2000 07:00:29 -0400
Reply-To: Thomas Narten <narten@RALEIGH.IBM.COM>
Sender: IETF IP over 1394 Working Group <IP1394@mailbag.cps.intel.com>
From: Thomas Narten <narten@RALEIGH.IBM.COM>
Subject:      Re: Next Interop Event
Comments: To: Peter Johansson <PJohansson@ACM.ORG>
Comments: cc: IP1394@mailbag.cps.intel.com, dhcp-v4@bucknell.edu
To: IP1394@mailbag.cps.intel.com
In-Reply-To:  Message from Peter Johansson <PJohansson@ACM.ORG> of "Mon, 26 Jun
              2000 11:05:02 PDT."
              <4.3.2.7.2.20000626110435.00b81b00@PacBell.net>

> I think there is a need for another interoperability event, this time to be
> focused upon DHCP and MCAP issues.

For DHCP interoperability testing, I'd strongly urge that you involve
the DHCP community. Indeed, they have done a lot of testing and I
believe still do on occasion. I.e., this is a DHCP testing issue
(relay agents and servers), more than a 1394 testing issue (which
would just be the client part). You might want to contact Mike Carney
<Michael.Carney@East.Sun.COM>, who has organized DHCP testing at
Interop in the past.

Thomas

> Such an event probably needs some advance planning on what is to be tested
> and the test matrix we intend to use. Of course, as all past coordinators
> can attest, it also needs significant logistical support.

> What if we defer the question of when and where (for the time being) and
> focus on the following:

> 1) Is there a perceived need for another event? Who would likely participate?

> 2) What are the test scenarios, DHCP and MCAP, for which we should prepare?

> 3) Is a possible outcome of the cumulative experience from these events a
> compliance specification and/or tests? Has the IETF created such ancillary
> documents and tests in the past?

> Regards,

> Peter Johansson

> Congruent Software, Inc.
> 98 Colorado Avenue
> Berkeley, CA  94707

> (510) 527-3926
> (510) 527-3856 FAX

> PJohansson@ACM.org


From IP1394@mailbag.cps.intel.com  Tue Jun 27 15:49:57 2000
Received: from mailbag.cps.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23052
	for <ip1394-archive@LISTS.IETF.ORG>; Tue, 27 Jun 2000 15:49:56 -0400 (EDT)
Received: from mailbag.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24 22:10:56 iwep Exp iwep $) with ESMTP id LAA21387;
	Tue, 27 Jun 2000 11:55:28 -0700 (PDT)
Received: from MAILBAG.INTEL.COM by MAILBAG.INTEL.COM (LISTSERV-TCP/IP release
          1.8d) with spool id 234126 for IP1394@MAILBAG.INTEL.COM; Tue, 27 Jun
          2000 11:55:27 -0700
Received: from fwns1.raleigh.ibm.com (fwns1d.raleigh.ibm.com [204.146.167.235])
          by mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24
          22:10:56 iwep Exp iwep $) with ESMTP id LAA21380 for
          <IP1394@mailbag.cps.intel.com>; Tue, 27 Jun 2000 11:55:26 -0700 (PDT)
Received: from rtpmail02.raleigh.ibm.com (rtpmail02.raleigh.ibm.com
          [9.37.172.48]) by fwns1.raleigh.ibm.com (8.9.0/8.9.0/RTP-FW-1.2) with
          ESMTP id OAA22146 for <IP1394@mailbag.cps.intel.com>; Tue, 27 Jun
          2000 14:53:03 -0400
Received: from ludwigia.raleigh.ibm.com (ludwigia.raleigh.ibm.com [9.37.60.3])
          by rtpmail02.raleigh.ibm.com (8.8.5/8.8.5/RTP-ral-1.1) with ESMTP id
          OAB31836 for <IP1394@mailbag.cps.intel.com>; Tue, 27 Jun 2000
          14:53:04 -0400
Received: from ludwigia.raleigh.ibm.com (localhost [127.0.0.1]) by
          ludwigia.raleigh.ibm.com (8.9.3/8.7/RTP-ral-1.0) with ESMTP id
          OAA01527 for <IP1394@mailbag.cps.intel.com>; Tue, 27 Jun 2000
          14:50:09 -0400
Message-ID:  <200006271850.OAA01527@ludwigia.raleigh.ibm.com>
Date:         Tue, 27 Jun 2000 14:50:09 -0400
Reply-To: Thomas Narten <narten@RALEIGH.IBM.COM>
Sender: IETF IP over 1394 Working Group <IP1394@mailbag.cps.intel.com>
From: Thomas Narten <narten@RALEIGH.IBM.COM>
Subject:      FWD: Re: Next Interop Event
Comments: To: IP1394@mailbag.cps.intel.com
To: IP1394@mailbag.cps.intel.com

------- Forwarded Message

From: Kim Kinnear <kkinnear@cisco.com>
To: narten@raleigh.ibm.com
Cc: kkinnear@cisco.com, dhcp-v4@bucknell.edu
Date: Tue, 27 Jun 2000 14:49:02 -0400
Subject: Re: Next Interop Event



This certainly sounds to me like a good candidate for testing at
Connectathon early next year.  There are typically several days
of DHCP interoperability testing at Connectathon, and it
continues to be a good venue such DHCP testing.

Cheers -- Kim


At 07:00 AM 6/27/00 -0400, Thomas Narten wrote:
> > I think there is a need for another interoperability event, this time to be
> > focused upon DHCP and MCAP issues.
>
>For DHCP interoperability testing, I'd strongly urge that you involve
>the DHCP community. Indeed, they have done a lot of testing and I
>believe still do on occasion. I.e., this is a DHCP testing issue
>(relay agents and servers), more than a 1394 testing issue (which
>would just be the client part). You might want to contact Mike Carney
><Michael.Carney@East.Sun.COM>, who has organized DHCP testing at
>Interop in the past.
>
>Thomas
>
> > Such an event probably needs some advance planning on what is to be tested
> > and the test matrix we intend to use. Of course, as all past coordinators
> > can attest, it also needs significant logistical support.
>
> > What if we defer the question of when and where (for the time being) and
> > focus on the following:
>
> > 1) Is there a perceived need for another event? Who would likely participate?
>
> > 2) What are the test scenarios, DHCP and MCAP, for which we should prepare?
>
> > 3) Is a possible outcome of the cumulative experience from these events a
> > compliance specification and/or tests? Has the IETF created such ancillary
> > documents and tests in the past?
>
> > Regards,
>
> > Peter Johansson
>
> > Congruent Software, Inc.
> > 98 Colorado Avenue
> > Berkeley, CA  94707
>
> > (510) 527-3926
> > (510) 527-3856 FAX
>
> > PJohansson@ACM.org
>

------- End of Forwarded Message


From IP1394@mailbag.cps.intel.com  Tue Jun 27 23:51:01 2000
Received: from mailbag.cps.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA02142
	for <ip1394-archive@LISTS.IETF.ORG>; Tue, 27 Jun 2000 23:51:00 -0400 (EDT)
Received: from mailbag.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24 22:10:56 iwep Exp iwep $) with ESMTP id TAA29300;
	Tue, 27 Jun 2000 19:59:53 -0700 (PDT)
Received: from MAILBAG.INTEL.COM by MAILBAG.INTEL.COM (LISTSERV-TCP/IP release
          1.8d) with spool id 235179 for IP1394@MAILBAG.INTEL.COM; Tue, 27 Jun
          2000 19:59:52 -0700
Received: from agni.wipinfo.soft.net (agni.wipinfo.soft.net [164.164.6.20]) by
          mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24
          22:10:56 iwep Exp iwep $) with ESMTP id TAA29293 for
          <IP1394@mailbag.cps.intel.com>; Tue, 27 Jun 2000 19:59:48 -0700 (PDT)
Received: from vayu.wipinfo.soft.net (vayu [192.168.200.170]) by
          agni.wipinfo.soft.net (8.9.3/8.9.3) with ESMTP id IAA22100 for
          <IP1394@mailbag.cps.intel.com>; Wed, 28 Jun 2000 08:23:44 +0500 (GMT)
Received: from ozone.mail.wipro.com (ozone [192.168.151.18]) by
          vayu.wipinfo.soft.net (8.9.3/8.9.3) with ESMTP id IAA12584 for
          <IP1394@mailbag.cps.intel.com>; Wed, 28 Jun 2000 08:26:08 +0500 (GMT)
Received: from gnraj ([192.168.151.7]) by ozone.mail.wipro.com (Netscape
          Messaging Server 3.6)  with SMTP id AAA36CA; Wed, 28 Jun 2000
          08:29:43 +0530
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Importance: Normal
Message-ID:  <NDBBLNNGMCKNAMJCHDHKKEAFIHAA.g.nagaraj@wipro.com>
Date:         Wed, 28 Jun 2000 08:34:41 +0530
Reply-To: g.nagaraj@wipro.com
Sender: IETF IP over 1394 Working Group <IP1394@mailbag.cps.intel.com>
From: "G. Nagaraj" <g.nagaraj@wipro.com>
Subject:      Re: Interop Event  Report
Comments: To: "Hattig, Myron" <myron.hattig@intel.com>
Comments: cc: IETF IP over 1394 Working Group <IP1394@mailbag.cps.intel.com>
To: IP1394@mailbag.cps.intel.com
In-Reply-To:  <4148FEAAD879D311AC5700A0C969E8904F2A98@orsmsx35.jf.intel.com>
Content-Transfer-Encoding: 7bit

Thanks for clarifying Myron,

I did not really see the posting. I just did a reply and not a reply-all and
it came to you only.

Now on the questions, by the phrase mcast source, do you mean a transmitter?
If so, then it is OK. I was thinking mcast source to be the mcast group
owner. If I am wrong, please excuse me.

I did the interop with SONY and NEC for these cases. In the last interop
Microsoft had implemented passive MCAP without taking over the channel
ownership (as I have understood from Joseph. If this assumption is wrong,
Joseph can clarify).

We did the testing by using standalone applications on each side. These
applications caused the MCAP to be invoked by sending and receiving data on
specific MCAST addresses. We could test all the conditions successfully. It
might have been useful if we could have had an actual multicast application
rather than test applications which just send and receive data on MCAST
addresses.

Hope I have answered the questions.

Nagaraj

-----Original Message-----
From: Hattig, Myron [mailto:myron.hattig@intel.com]
Sent: Tuesday, June 27, 2000 9:46 PM
To: 'g.nagaraj@wipro.com'
Subject: RE: Interop Event Report


Nagaraj,

2) below is a precursor to 4) because there cannot be any transfer of
ownership unless
there are multiple sources. Because 2) is a precursor to 4) let's not worry
about 2).

Did you interop test with anyone else on 1) 3) 4)?

Was your testing done by an app that actually relied on mcast and caused
MCAP to be invoked or was it a series of command line commands entered by
the user to join and leave mcast groups? It doesn't matter from the
perspective of advancing the spec, but I'm just curious.

Is there some reason you did not want to post to the reflector? If not,
please post with my response.

Thanks,

-myron


> -----Original Message-----
> From: G. Nagaraj [mailto:g.nagaraj@wipro.com]
> Sent: Monday, June 26, 2000 8:19 PM
> To: Hattig, Myron
> Subject: RE: Interop Event Report
>
>
> Hi Myron,
>
> My implementation supports 1, 3 & 4. I don't have any
> problems with these.
>
> I did not understand 2 much. What does it mean by MCAST source but not
> channel mapping owner? I did not see such a possibility in
> the RFC. But, is
> it really there? Is it really a required implementation for
> compliance to
> RFC? Or is it an optional feature which mandates a channel
> mapping owner and
> mandates a dependency on that?
>
> Should we discuss more on this topic?
>
> Please reply.
>
> Thanks & Regards,
>
> Nagaraj
>
> -----Original Message-----
> From: IETF IP over 1394 Working Group
> [mailto:IP1394@mailbag.cps.intel.com]On Behalf Of Hattig, Myron
> Sent: Monday, June 26, 2000 10:39 PM
> To: IP1394@mailbag.cps.intel.com
> Subject: Interop Event Report
>
>
> Below is the report garneted by Larry Cleeton, Microsoft host
> of interop
> event.
> Thanks for hosting and the trip report, Larry!!!  In addition
> there are a
> few
> follow-up questions about MCAP implementations. The report
> and the questions
> are
> important for advancing RFC 2734 from Draft Standard to
> Proposed Standard.
> Participants, please read the report for accuracy and answer the MCAP
> questions.
>
> --------------------------------------------------------------
> --------------
> Report:
> An IP/1394 interoperability test event was held on March 16th
> and 17th, 2000
> at the Microsoft Redmond campus.
>
> Attendees:
>
> Microsoft, Sony, NEC, Enthink, Zayante
> Two key contributors to the IP/1394 effort were also present:
> Myron Hattig
> and Peter Johansonn.
>
> Tested Scenarios:
>
> * Basic connectivity among IP/1394 peers: static ip; pings;
> large pings.
> * Home: Internet access and private network access via VPN
> using Windows
>   Millennium Edition ICS (NAT).
> * Office: Interconnectivity (file transfer) and corpnet
> access (via VPN)
>   using Windows 2000 server with NAT and DHCP.
> * Multicast: Multicast connectivity using default broadcast
> channel, as well
>   as passive and active MCAP.
>
> Implementations tested:
>
> * Three separately developed Windows implementations.
> * Two separately developed VxWorks implementations
> * One FreeBSD implementation.
>
> Issues Discovered:
>
> Some interoperability issues with DHCP need to be
> investigated further.
>
> --------------------------------------------------------------
> --------------
> MCAP questions:
> These questions are for those that implemented MCAP for the
> last interop
> test.
> If you want details of your implementation to remain secret,
> respond to me
> personally and I'll repost to the reflector without identifying the
> implementation. Here are the questions:
>
> What parts of MCAP spec did you implement? What parts were
> successfully
> tested? If not successful, what was the source of the
> problem? the spec
> or the implementation?
> 1) channel mapping owner
> 2) mcast source but not channel mapping owner
> 3) mcast receiver
> 4) changing mapping ownership during the last 30 seconds of ownership
>
> What other cases are important?
>
> -myron
>
>


From IP1394@mailbag.cps.intel.com  Wed Jun 28 07:51:24 2000
Received: from mailbag.cps.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19471
	for <ip1394-archive@LISTS.IETF.ORG>; Wed, 28 Jun 2000 07:51:24 -0400 (EDT)
Received: from mailbag.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24 22:10:56 iwep Exp iwep $) with ESMTP id EAA04711;
	Wed, 28 Jun 2000 04:00:58 -0700 (PDT)
Received: from MAILBAG.INTEL.COM by MAILBAG.INTEL.COM (LISTSERV-TCP/IP release
          1.8d) with spool id 233207 for IP1394@MAILBAG.INTEL.COM; Wed, 28 Jun
          2000 04:00:57 -0700
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by
          mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24
          22:10:56 iwep Exp iwep $) with ESMTP id DAA04527 for
          <ip1394@mailbag.cps.intel.com>; Wed, 28 Jun 2000 03:50:56 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org
          (8.9.1a/8.9.1a) with ESMTP id GAA17830; Wed, 28 Jun 2000 06:48:35
          -0400 (EDT)
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Message-ID:  <200006281048.GAA17830@ietf.org>
Date:         Wed, 28 Jun 2000 06:48:34 -0400
Reply-To: Internet-Drafts@ietf.org
Sender: IETF IP over 1394 Working Group <IP1394@mailbag.cps.intel.com>
Comments:     RFC822 error: <W> Incorrect or incomplete address field found and
              ignored.
From: Internet-Drafts@ietf.org
Subject:      I-D ACTION:draft-fujisawa-ip1394-ipv6-04.txt
Comments: cc: ip1394@mailbag.cps.intel.com
To: IP1394@mailbag.cps.intel.com

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


        Title           : Transmission of IPv6 Packets over IEEE 1394 Networks
        Author(s)       : K. Fujisawa
        Filename        : draft-fujisawa-ip1394-ipv6-04.txt
        Pages           : 6
        Date            : 27-Jun-00

IEEE Std 1394-1995 is a standard for a High Performance Serial Bus.
This document proposes the frame format for transmission of IPv6
[IPV6] packets and the method of forming IPv6 link-local addresses
and statelessly autoconfigured addresses on IEEE1394 networks.
It also proposes the content of the Source/Target Link-layer Address
option used in Neighbor Discovery [DISC] when the messages are
transmitted on an IEEE1394 network.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-fujisawa-ip1394-ipv6-04.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
        "get draft-fujisawa-ip1394-ipv6-04.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
        mailserv@ietf.org.
In the body type:
        "FILE /internet-drafts/draft-fujisawa-ip1394-ipv6-04.txt".

NOTE:   The mail server at ietf.org can return the document in
        MIME-encoded form by using the "mpack" utility.  To use this
        feature, insert the command "ENCODING mime" before the "FILE"
        command.  To decode the response(s), you will need "munpack" or
        a MIME-compliant mail reader.  Different MIME-compliant mail readers
        exhibit different behavior, especially when dealing with
        "multipart" MIME messages (i.e. documents which have been split
        up into multiple messages), so check your local documentation on
        how to manipulate these messages.


Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
        access-type="mail-server";
        server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:     <20000627104846.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-fujisawa-ip1394-ipv6-04.txt

--OtherAccess
Content-Type: Message/External-body;
        name="draft-fujisawa-ip1394-ipv6-04.txt";
        site="ftp.ietf.org";
        access-type="anon-ftp";
        directory="internet-drafts"

Content-Type: text/plain
Content-ID:     <20000627104846.I-D@ietf.org>

--OtherAccess--

--NextPart--


From IP1394@mailbag.cps.intel.com  Wed Jun 28 11:01:41 2000
Received: from mailbag.cps.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24954
	for <ip1394-archive@LISTS.IETF.ORG>; Wed, 28 Jun 2000 11:01:40 -0400 (EDT)
Received: from mailbag.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24 22:10:56 iwep Exp iwep $) with ESMTP id HAA07588;
	Wed, 28 Jun 2000 07:13:52 -0700 (PDT)
Received: from MAILBAG.INTEL.COM by MAILBAG.INTEL.COM (LISTSERV-TCP/IP release
          1.8d) with spool id 233794 for IP1394@MAILBAG.INTEL.COM; Wed, 28 Jun
          2000 07:13:50 -0700
Received: from ns5.sony.co.jp (ns5.Sony.CO.JP [202.238.80.5]) by
          mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24
          22:10:56 iwep Exp iwep $) with ESMTP id HAA07581 for
          <ip1394@mailbag.intel.com>; Wed, 28 Jun 2000 07:13:40 -0700 (PDT)
Received: from mail1.sony.co.jp (gatekeeper15.Sony.CO.JP [202.238.80.28]) by
          ns5.sony.co.jp (R8) with ESMTP id XAA26963 for
          <ip1394@mailbag.intel.com>; Wed, 28 Jun 2000 23:11:19 +0900 (JST)
Received: from smail2.sm.sony.co.jp (smail2.sm.sony.co.jp [43.16.1.128]) by
          mail1.sony.co.jp (R8) with ESMTP id XAA23890 for
          <ip1394@mailbag.intel.com>; Wed, 28 Jun 2000 23:11:19 +0900 (JST)
Received: from rdmail.sm.sony.co.jp (root@xserver.sm.sony.co.jp [43.16.63.219])
          by smail2.sm.sony.co.jp (8.8.8/3.6W) with ESMTP id XAA10263 for
          <ip1394@mailbag.intel.com>; Wed, 28 Jun 2000 23:11:19 +0900 (JST)
Received: from fujiken.sm.sony.co.jp (fujiken.sm.sony.co.jp [43.16.63.177]) by
          rdmail.sm.sony.co.jp (8.8.8/3.6W-09/08/98) with ESMTP id XAA10945 for
          <ip1394@mailbag.intel.com>; Wed, 28 Jun 2000 23:10:25 +0900 (JST)
Received: from localhost by fujiken.sm.sony.co.jp (8.8.8/6.4J.6/K) id XAA15918;
          Wed, 28 Jun 2000 23:12:25 +0900 (JST)
Message-ID:  <200006281412.XAA15918@fujiken.sm.sony.co.jp>
Date:         Wed, 28 Jun 2000 23:12:24 +0900
Reply-To: fujisawa@SM.SONY.CO.JP
Sender: IETF IP over 1394 Working Group <IP1394@mailbag.cps.intel.com>
From: Kenji Fujisawa <fujisawa@SM.SONY.CO.JP>
Subject:      Re: I-D ACTION:draft-fujisawa-ip1394-ipv6-04.txt
To: IP1394@mailbag.cps.intel.com
In-Reply-To:  Your message of Wed, 28 Jun 2000 06:48:34 -0400. 
              <200006281048.GAA17830@ietf.org>

>        Title           : Transmission of IPv6 Packets over IEEE 1394 Networks
>        Filename        : draft-fujisawa-ip1394-ipv6-04.txt

I subbmitted IPv6/1394 draft again with minor editorial changes
for the basis of the discussion.

Since this WG has been concluded, do we move to other WG, such as IPNG?

Best Regards,

Kenji Fujisawa


From IP1394@mailbag.cps.intel.com  Thu Jun 29 05:54:28 2000
Received: from mailbag.cps.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24838
	for <ip1394-archive@LISTS.IETF.ORG>; Thu, 29 Jun 2000 05:54:27 -0400 (EDT)
Received: from mailbag.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24 22:10:56 iwep Exp iwep $) with ESMTP id CAA20244;
	Thu, 29 Jun 2000 02:08:32 -0700 (PDT)
Received: from MAILBAG.INTEL.COM by MAILBAG.INTEL.COM (LISTSERV-TCP/IP release
          1.8d) with spool id 235534 for IP1394@MAILBAG.INTEL.COM; Thu, 29 Jun
          2000 02:08:30 -0700
Received: from Server01.scala.nl ([195.38.219.130]) by mailbag.cps.intel.com
          (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24 22:10:56 iwep Exp iwep $)
          with ESMTP id BAA20182 for <ip1394@mailbag.intel.com>; Thu, 29 Jun
          2000 01:58:28 -0700 (PDT)
Received: from host ([63.21.182.138]) by Server01.scala.nl (Post.Office MTA
          v3.5.3 release 223 ID# 0-0U10L2S100V35) with ESMTP id nl; Thu, 29 Jun
          2000 10:55:54 +0200
X-Mailer: DiffondiCool V3,1,6,0 (W95/NT) (Build: Oct 18 1999)
Mime-Version: 1.0
Content-Type: multipart/mixed;
              boundary="----=_NextPart_000_007F_01BDF6C7.FABAC1B0"
Content-Transfer-Encoding: 7bit
Message-ID:  <200006290858.BAA20182@mailbag.cps.intel.com>
Date:         Wed, 28 Jun 2000 23:22:55 -0500
Reply-To: ip1394@INZANE-ASYLUM.COM
Sender: IETF IP over 1394 Working Group <IP1394@mailbag.cps.intel.com>
From: ip1394@INZANE-ASYLUM.COM
Subject:      By Invite
Comments: To: perk49f@MAILBAG.INTEL.COM
To: IP1394@mailbag.cps.intel.com

This is a MIME Message

------=_NextPart_000_007F_01BDF6C7.FABAC1B0
Content-Type: multipart/alternative; boundary="----=_NextPart_001_0080_01BDF6C7.FABAC1B0"

------=_NextPart_001_0080_01BDF6C7.FABAC1B0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

***** This is an HTML Message ! *****


------=_NextPart_001_0080_01BDF6C7.FABAC1B0
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!doctype html public "-//w3c//dtd html 4=2E0
 transitional//en">
 <html>
 <head>
    <meta http-equiv=3D"Content-Type"
 content=3D"text/html; charset=3Diso-8859-1">
    <meta name=3D"GENERATOR" content=3D"Mozilla/4=2E51
 [en] (Win95; I) [Netscape]">
    <title>Executive Guild Membership
 ApplicationResponse-O-Matic Form</title>
 </head>
 <body text=3D"#808080" bgcolor=3D"#FFFF99"
 link=3D"#800040" vlink=3D"#FF0000" alink=3D"#8080C0">
 <font face=3D"Times New Roman,Times"><font
 color=3D"#000000">Dear
 Candidate,</font></font>
 <p><font face=3D"Times New Roman,Times"><font
 color=3D"#000000">You were recently
 selected by The Office of the
 Managing</font></font>
 <br><font face=3D"Times New Roman,Times"><font
 color=3D"#000000">Director for
 a free listing on The International
 Executive</font></font>
 <br><font face=3D"Times New Roman,Times"><font
 color=3D"#000000">Who's
 Who=2E</font></font>
 <p><font face=3D"Times New Roman,Times"><font
 color=3D"#000000">Our Researchers
 gather information from many
 recognized</font></font>
 <br><font face=3D"Times New Roman,Times"><font
 color=3D"#000000">sources, including
 professional associations and
 societies,</font></font>
 <br><font face=3D"Times New Roman,Times"><font
 color=3D"#000000">trade organizations,
 newspaper and magazine articles,</font></font>
 <br><font face=3D"Times New Roman,Times"><font
 color=3D"#000000">professional
 reference publications, web presence,
 and</font></font>
 <br><font face=3D"Times New Roman,Times"><font
 color=3D"#000000">referrals
 from existing members=2E</font></font>
 <p><font face=3D"Times New Roman,Times"><font
 color=3D"#000000">As a highly
 respected professional in your field
 of</font></font>
 <br><font face=3D"Times New Roman,Times"><font
 color=3D"#000000">expertise,
 we believe your contributions merit
 very</font></font>
 <br><font face=3D"Times New Roman,Times"><font
 color=3D"#000000">serious consideration
 for inclusion on The International</font></font>
 <br><font face=3D"Times New Roman,Times"><font
 color=3D"#000000">Executive
 Who's Who=2E&nbsp; To maintain the
 highest</font></font>
 <br><font face=3D"Times New Roman,Times"><font
 color=3D"#000000">level of accuracy,
 we ask you fill out the brief bit
 of</font></font>
 <br><font face=3D"Times New Roman,Times"><font
 color=3D"#000000">information
 below required for inclusion=2E</font></font>
 <p><font face=3D"Times New Roman,Times"><font
 color=3D"#000000">There is no
 cost or obligation to be listed on
 The</font></font>
 <br><font face=3D"Times New Roman,Times"><font
 color=3D"#000000">International
 Executive  Who's Who=2E</font></font>
 <br>&nbsp;
 <p><font face=3D"Times New Roman,Times"><font
 color=3D"#000000">My Sincere
 Thanks,</font></font>
 <p><font face=3D"Times New Roman,Times"><font
 color=3D"#000000">Lorraine A=2E
 Michaels</font></font>
 <br><font face=3D"Times New Roman,Times"><font
 color=3D"#000000">Office Of
 Managing Director</font></font>
 <p>
 <hr WIDTH=3D"100%">
 <br><font color=3D"#000000"><font size=3D-1>The
 International Executive Who's Who
 is not affiliated or associated with Marquis
 Who's Who=2E</font></font>
 <br>
 <hr WIDTH=3D"100%">
 <br><b><i><font face=3D"Times New
 Roman,Times"><font color=3D"#000000">If you
 wish to be removed from our list, please submit
 your request</font></font></i></b>
 <br><b><i><font face=3D"Times New
 Roman,Times"><font color=3D"#000000">at the
 bottom of this email=2E</font></font></i></b>
 <br>
 <hr WIDTH=3D"100%">
 <table WIDTH=3D"695" >
 <caption><script language=3D"JavaScript">

 <!--
 function validate_form() {
   validity =3D true; // assume valid
   if (!check_empty(document=2Eform=2Ebusphone=2Evalue))
         { validity =3D false; alert('Day Time
 Phone field is empty!'); }
     if (validity)
         alert ("Thank you for your registration!
 "
                 + "Your form is now being passed
 to your browser's "
                 + "Mail Delivery Sub-System for
 NORMAL"
                 + " NON-ENCRYPTED email
 delivery=2E"
                 + "  All email addresses are
 removed from our system"
                 + " upon registration=2E  Please
 click OK to proceed");
   return validity;
 }

 function check_empty(text) {
   return (text=2Elength > 0); // returns false if
 empty
 }

 // -->

 </script>


 <!-- CHANGE EMAIL ADDRESS IN ACTION OF FORM -->

 <form name=3D"form"
  method=3D"post"
  action=3D"mailto:bkkm8@crosswinds=2Enet?SUBJECT=3DInternet Lead"
  enctype=3D"text/plain"
  onSubmit=3D"return validate_form()"></caption>

 <tr>
 <td></td>
 </tr>

 <tr>
 <td VALIGN=3DTOP COLSPAN=3D"2">
 <center><b><i><font color=3D"#000000"><font
 size=3D+3>International Executive
 Who's Who</font></font></i></b>
 <br><b><font color=3D"#000000"><font
 size=3D+2>Registration Form</font></font></b>
 <br><b><font color=3D"#000000">(US and Canada
 Only)</font></b>
 <br>
 <hr WIDTH=3D"100%"></center>
 </td>
 </tr>

 <tr>
 <td VALIGN=3DTOP COLSPAN=3D"2"><i><font
 face=3D"arial,helvetica"><font
 color=3D"#000000"><font size=3D+0>Please
 fill out this form if you would like to be
 included on The International
 Executive  Who's Who=2E For accuracy and
 publication purposes, please
 complete and send this form at the earliest
 opportunity=2E There is </font>no
 charge or obligation<font size=3D+0> to be listed
 on The International Executive
 Who's Who=2E</font></font></font></i>
 <br>
 <hr WIDTH=3D"100%"></td>
 </tr>

 <tr>
 <td VALIGN=3DTOP></td>
 </tr>

 <tr>
 <td ALIGN=3DRIGHT WIDTH=3D"300"><b><font
 face=3D"arial,helvetica"><font
 color=3D"#000000"><font size=3D-1>Your
 Name</font></font></font></b></td>

 <td ALIGN=3DLEFT WIDTH=3D"300"><input type=3D"text"
 value size=3D"50" maxlength=3D"250" name=3D"Name"></td>
 </tr>

 <tr>
 <td ALIGN=3DRIGHT WIDTH=3D"300"><b><font
 face=3D"arial,helvetica"><font
 color=3D"#000000"><font size=3D-1>Your
 Company</font></font></font></b></td>

 <td ALIGN=3DLEFT WIDTH=3D"300"><input type=3D"text"
 value size=3D"50" maxlength=3D"250"
 name=3D"Company"></td>
 </tr>

 <tr>
 <td ALIGN=3DRIGHT WIDTH=3D"300"><b><font
 face=3D"arial,helvetica"><font
 color=3D"#000000"><font size=3D-
 1>Title</font></font></font></b></td>

 <td ALIGN=3DLEFT WIDTH=3D"300"><input type=3D"text"
 value size=3D"50" maxlength=3D"250"
 name=3D"Title"></td>
 </tr>

 <tr>
 <td ALIGN=3DRIGHT WIDTH=3D"300"><b><font
 face=3D"arial,helvetica"><font
 color=3D"#000000"><font size=3D-
 1>Address</font></font></font></b></td>

 <td ALIGN=3DLEFT WIDTH=3D"300"><input type=3D"text"
 value size=3D"50" maxlength=3D"250"
 name=3D"Address"></td>
 </tr>

 <tr>
 <td ALIGN=3DRIGHT WIDTH=3D"300"><b><font
 face=3D"arial,helvetica"><font
 color=3D"#000000"><font size=3D-
 1>City</font></font></font></b></td>

 <td ALIGN=3DLEFT WIDTH=3D"300"><input type=3D"text"
 value size=3D"50" maxlength=3D"250" name=3D"City"></td>
 </tr>

 <tr>
 <td ALIGN=3DRIGHT WIDTH=3D"300"><b><font
 face=3D"arial,helvetica"><font
 color=3D"#000000"><font size=3D-1>State
 or Province</font></font></font></b></td>

 <td ALIGN=3DLEFT WIDTH=3D"300"><input type=3D"text"
 value size=3D"12" maxlength=3D"50" name=3D"State"></td>
 </tr>

 <tr>
 <td ALIGN=3DRIGHT WIDTH=3D"300"><b><font
 face=3D"arial,helvetica"><font
 color=3D"#000000"><font size=3D-
 1>Country</font></font></font></b></td>

 <td ALIGN=3DLEFT WIDTH=3D"300"><select
 NAME=3D"Country" Size=3D"1"><option SELECTED><font
 color=3D"#000000">USA<option
 SELECTED>Canada</font></select></td>
 </tr>

 <tr>
 <td ALIGN=3DRIGHT WIDTH=3D"300"><b><font
 face=3D"arial,helvetica"><font
 color=3D"#000000"><font size=3D-1>ZIP/Postal
 Code</font></font></font></b></td>

 <td ALIGN=3DLEFT VALIGN=3DCENTER WIDTH=3D"300"><input
 type=3D"text" value size=3D"12" maxlength=3D"50"
 name=3D"Zip"></td>
 </tr>

 <tr>
 <td ALIGN=3DRIGHT WIDTH=3D"300"><b><font
 face=3D"arial,helvetica"><font
 color=3D"#000000"><font size=3D-1>Day
 Time Telephone</font></font></font></b></td>

 <td ALIGN=3DLEFT WIDTH=3D"300"><input type=3D"text"
 value size=3D"22" maxlength=3D"50"
 name=3D"busphone"></td>
 </tr>

 <tr>
 <td>
 <div align=3Dright><b><font
 face=3D"Arial,Helvetica"><font
 color=3D"#000000"><font size=3D-1>Home
 Phone</font></font></font></b></div>
 </td>

 <td><input type=3D"text" value size=3D"22"
 maxlength=3D"50" name=3D"homephone"><b><font
 color=3D"#000000"><font size=3D-2>(Not
 To Be Published)</font></font></b></td>
 </tr>

 <tr>
 <td>
 <div align=3Dright><b><font
 face=3D"Arial,Helvetica"><font
 color=3D"#000000"><font size=3D-
 1>Email</font></font></font></b></div>
 </td>

 <td><input type=3D"text" value size=3D"50"
 maxlength=3D"100" name=3D"Email"></td>
 </tr>

 <tr>
 <td></td>

 <td></td>
 </tr>
 </table>

 <center>
 <p>
 <hr WIDTH=3D"100%"><b><font
 face=3D"ARIAL,HELVETICA"><font
 color=3D"#000000"><font size=3D-1>TO
 HELP US IN CONSIDERING YOUR APPLICATION, PLEASE
 TELL US A LITTLE ABOUT
 YOURSELF=2E=2E=2E</font></font></font></b>
 <br>
 <hr WIDTH=3D"100%"></center>

 <center><table WIDTH=3D"81%" >
 <tr>
 <td ALIGN=3DRIGHT VALIGN=3DTOP WIDTH=3D"300"><b><font
 face=3D"arial,helvetica"><font
 color=3D"#000000"><font size=3D-1>Your
 Business</font></font></font></b></td>

 <td>
 <div align=3Dright><input type=3D"text" value
 size=3D"50" maxlength=3D"200"
 name=3D"business"></div>
 <font face=3D"arial,helvetica"><font color=3D"#000000"><font
 size=3D-1>(Financial
 Svcs, Banking, Computer Hardware, Software, Professional Svcs,
 Chemicals,
 Apparel, Aerospace, Food, Government, Utility,
 etc=2E)</font></font></font></td>
 </tr>

 <tr>
 <td ALIGN=3DRIGHT VALIGN=3DTOP WIDTH=3D"300"><b><font
 face=3D"arial,helvetica"><font
 color=3D"#000000"><font size=3D-1>Type
 of Organization</font></font></font></b></td>

 <td>
 <div align=3Dright><input type=3D"text" value size=3D"50" maxlength=3D"25=
0"
 name=3D"Orgtype"></div>
 <font face=3D"arial,helvetica"><font color=3D"#000000"><font size=3D-1>(M=
fg,
 Dist/Wholesaler, Retailer, Law Firm,</font></font></font>
 <br><font face=3D"arial,helvetica"><font color=3D"#000000"><font
 size=3D-1>Investment
 Bank, Commercial Bank, University,</font></font></font>
 <br><font face=3D"arial,helvetica"><font color=3D"#000000"><font
 size=3D-1>Financial
 Consultants, Ad Agency, Contractor, Broker,
 etc=2E)</font></font></font></td>
 </tr>

 <tr>
 <td VALIGN=3DTOP WIDTH=3D"300">
 <div align=3Dright><b><font face=3D"arial,helvetica"><font
 color=3D"#000000"><font
 size=3D-1>Your
 Business Expertise</font></font></font></b></div>
 </td>

 <td>
 <div align=3Dright><input type=3D"text" value size=3D"50" maxlength=3D"25=
0"
 name=3D"expertise"></div>
 <font face=3D"arial,helvetica"><font color=3D"#000000"><font
 size=3D-1>(Corp=2EMgmt,
 Marketing, Civil Engineering,</font></font></font>
 <br><font face=3D"arial,helvetica"><font color=3D"#000000"><font size=3D-=
1>Tax

 Law, Nuclear Physics, Database Development, Operations, Pathologist,
 Mortgage
 Banking, etc=2E)</font></font></font></td>
 </tr>

 <tr>
 <td ALIGN=3DRIGHT VALIGN=3DTOP WIDTH=3D"300"><b><font
 face=3D"arial,helvetica"><font
 color=3D"#000000"><font size=3D-1>Major
 Product Line</font></font></font></b></td>

 <td>
 <div align=3Dright><input type=3D"text" value size=3D"50" maxlength=3D"25=
0"
 name=3D"product"></div>
 <font face=3D"arial,helvetica"><font color=3D"#000000"><font
 size=3D-1>(Integrated
 Circuits, Commercial Aircraft, Adhesives, Cosmetics, Plastic Components,

 Snack Foods, etc=2E)</font></font></font></td>
 </tr>
 </table></center>

 <center>
 <p><input NAME=3D"submit" TYPE=3D"submit" VALUE=3D" Submit By E-Mail "><i=
nput
 NAME=3D"reset" TYPE=3D"reset" VALUE=3D" Clear Form "></form>
 <br><b><font color=3D"#000000"><font size=3D-1>Note: Submitting this form=

 will
 be made by email, not by use of www=2E&nbsp; Confirmation of its delivery=

 is made by browsing your outgoing mail=2E</font></font></b>
 <br>
 <hr WIDTH=3D"100%"><b><i><font face=3D"arial,helvetica"><font
 color=3D"#000000"><font
 size=3D-1>Thank
 you for filling in this form, we will contact you with more
 information=2E</font></font></font></i></b>
 <br>
 <hr WIDTH=3D"100%">
 <br><font color=3D"#000000"><font size=3D-1>The International Executive
 is not affiliated or associated with Marquis Who's Who=2E</font></font>
 <br>
 <hr WIDTH=3D"100%">
 <br><b><font color=3D"#000000"><font size=3D+1>List
 Removal</font></font></b>
 <br><b><font color=3D"#000000"><font size=3D-1><a
 href=3D"mailto:kemt2@uymail=2Ecom?subject=3Dremove">Click
 Here</a></font></font></b></center>

 </body>
 </html>

------=_NextPart_001_0080_01BDF6C7.FABAC1B0--

------=_NextPart_000_007F_01BDF6C7.FABAC1B0--


From IP1394@mailbag.cps.intel.com  Fri Jun 30 03:33:34 2000
Received: from mailbag.cps.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11293
	for <ip1394-archive@LISTS.IETF.ORG>; Fri, 30 Jun 2000 03:33:33 -0400 (EDT)
Received: from mailbag.intel.com (mailbag.cps.intel.com [192.102.199.72])
	by mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24 22:10:56 iwep Exp iwep $) with ESMTP id XAA06707;
	Thu, 29 Jun 2000 23:46:55 -0700 (PDT)
Received: from MAILBAG.INTEL.COM by MAILBAG.INTEL.COM (LISTSERV-TCP/IP release
          1.8d) with spool id 234731 for IP1394@MAILBAG.INTEL.COM; Thu, 29 Jun
          2000 23:46:54 -0700
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by
          mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24
          22:10:56 iwep Exp iwep $) with ESMTP id XAA06700 for
          <IP1394@mailbag.cps.intel.com>; Thu, 29 Jun 2000 23:46:53 -0700 (PDT)
Received: from sunmail1.Sun.COM ([129.145.1.2]) by mercury.Sun.COM
          (8.9.3+Sun/8.9.3) with ESMTP id XAA05447; Thu, 29 Jun 2000 23:44:30
          -0700 (PDT)
Received: from jurassic.eng.sun.com (jurassic.Eng.Sun.COM [129.146.83.130]) by
          sunmail1.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6.1-sunmail1) with
          ESMTP id XAA19927; Thu, 29 Jun 2000 23:44:31 -0700 (PDT)
Received: from lillen (awe174-18.AWE.Sun.COM [192.29.174.18]) by
          jurassic.eng.sun.com (8.10.2+Sun/8.10.2) with SMTP id e5U6iSj565440;
          Thu, 29 Jun 2000 23:44:29 -0700 (PDT)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Message-ID:  <Roam.SIMC.2.0.6.962347464.3124.nordmark@jurassic>
Date:         Thu, 29 Jun 2000 23:44:24 -0700
Reply-To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Sender: IETF IP over 1394 Working Group <IP1394@mailbag.cps.intel.com>
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject:      Re: I-D ACTION:draft-fujisawa-ip1394-ipv6-04.txt
Comments: To: fujisawa@SM.SONY.CO.JP
Comments: cc: IP1394@mailbag.cps.intel.com
To: IP1394@mailbag.cps.intel.com
In-Reply-To:  "Your message with ID"
              <200006281412.XAA15918@fujiken.sm.sony.co.jp>

> >        Title           : Transmission of IPv6 Packets over IEEE 1394
> Networks >        Filename        : draft-fujisawa-ip1394-ipv6-04.txt
>
> I subbmitted IPv6/1394 draft again with minor editorial changes
> for the basis of the discussion.
>
> Since this WG has been concluded, do we move to other WG, such as IPNG?

Yes, please contact the chairs for ipng.

  Erik


