RFC 3146 on IPv6 Packets over IEEE 1394 Networks
RFC Editor <rfc-ed@ISI.EDU> Fri, 26 October 2001 00:18 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02857; Thu, 25 Oct 2001 20:18:13 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id UAA07110 for ietf-123-outbound.10@ietf.org; Thu, 25 Oct 2001 20:15:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id UAA07084 for <all-ietf@loki.ietf.org>; Thu, 25 Oct 2001 20:09:19 -0400 (EDT)
Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02706 for <all-ietf@ietf.org>; Thu, 25 Oct 2001 20:09:14 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id f9Q09HH16854; Thu, 25 Oct 2001 17:09:17 -0700 (PDT)
Message-Id: <200110260009.f9Q09HH16854@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3146 on IPv6 Packets over IEEE 1394 Networks
Cc: rfc-ed@ISI.EDU, ipng@sunroof.eng.sun.com
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 25 Oct 2001 17:09:17 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 3146 Title: Transmission of IPv6 Packets over IEEE 1394 Networks Author(s): K. Fujisawa, A. Onoe Status: Standards Track Date: October 2001 Mailbox: fujisawa@sm.sony.co.jp, onoe@sm.sony.co.jp Pages: 8 Characters: 16513 SeeAlso/Updates/Obsoletes: None I-D Tag: draft-ietf-ipngwg-1394-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3146.txt This document describes the frame format for transmission of IPv6 packets and the method of forming IPv6 link-local addresses and statelessly autoconfigured addresses on IEEE1394 networks. This document is the product of the IPNG 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.