idnits 2.17.1 draft-ietf-ipngwg-ethernet-ntwrks-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-18) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard == It seems as if not all pages are separated by form feeds - found 0 form feeds but 4 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (February 26, 1996) is 10279 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 1884 (ref. 'AARCH') (Obsoleted by RFC 2373) == Outdated reference: A later version (-06) exists of draft-ietf-ipngwg-discovery-05 ** Obsolete normative reference: RFC 1883 (ref. 'IPV6') (Obsoleted by RFC 2460) Summary: 11 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Engineering Task Force Matt Crawford 2 INTERNET-DRAFT Fermilab 3 February 26, 1996 5 A Method for the Transmission of IPv6 Packets over Ethernet Networks 7 Status of this Memo 9 This document is an Internet Draft. Internet Drafts are working 10 documents of the Internet Engineering Task Force (IETF), its Areas, 11 and its Working Groups. Note that other groups may also distribute 12 working documents as Internet Drafts. 14 Internet Drafts are draft documents valid for a maximum of six 15 months. Internet Drafts may be updated, replaced, or obsoleted by 16 other documents at any time. It is not appropriate to use Internet 17 Drafts as reference material or to cite them other than as a "working 18 draft" or "work in progress." 20 To learn the current status of any Internet-Draft, please check the 21 ``1id-abstracts.txt'' listing contained in the Internet Drafts Shadow 22 Directories on ds.internic.net (US East Coast), nic.nordu.net 23 (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific 24 Rim). 26 Distribution of this memo is unlimited. 28 Introduction 30 This memo specifies the frame format for transmission of IPv6 [IPV6] 31 packets and the method of forming IPv6 link-local addresses on 32 Ethernet networks. It also specifies the content of the 33 Source/Target Link-layer Address option used the the Router 34 Solicitation, Router Advertisement, Neighbor Solicitation, and 35 Neighbor Advertisement messages described in [DISC], when those 36 messages are transmitted on an Ethernet. 38 Maximum Transmission Unit 40 The default MTU size for IPv6 packets on an Ethernet is 1500 octets. 41 This size may be reduced by a Router Advertisement [DISC] containing 42 an MTU option which specifies a smaller MTU, or by manual 43 configuration of each node. If a Router Advertisement is received 45 =0C 46 INTERNET-DRAFT Transmission of IPv6 Packets Over Ethernet 1996-02-26 48 with an MTU option specifying an MTU larger than 1500, or larger than 49 a manually configured value less than 1500, that MTU option must be 50 ignored. 52 Frame Format 54 IPv6 packets are transmitted in standard Ethernet frames. The 55 ethernet header contains the Destination and Source ethernet 56 addresses and the ethernet type code, which must contain the value 57 86DD hexadecimal. The data field contains the IPv6 header followed 58 immediately by the payload, and possibly padding octets to meet the 59 minimum frame size for Ethernet. 61 +-------+-------+-------+-------+-------+-------+ ^ 62 | Destination Ethernet address | | 63 +-------+-------+-------+-------+-------+-------+ ethernet 64 | Source Ethernet address | header 65 +-------+-------+-------+-------+-------+-------+ | 66 | 86 DD | v 67 +-------+-------+-------+-------+-------+------+------+ 68 | IPv6 header and payload ... / 69 +-------+-------+-------+-------+-------+------+------+ 71 Stateless Autoconfiguration and Link-Local Addresses 73 The address token [CONF] for an Ethernet interface is the interface's 74 built-in 48-bit IEEE 802 address, in canonical bit order and with the 75 octets in the same order in which they would appear in the header of 76 an ethernet frame. (The individual/group bit is in the first octet 77 and the OUI is in the first three octets.) A different MAC address 78 set manually or by software should not be used as the address token. 80 An IPv6 address prefix used for stateless autoconfiguration of an 81 ethernet interface must be 80 bits in length. 83 The IPv6 Link-local address [AARCH] for an Ethernet interface is 84 formed by appending the interface's IEEE 802 address to the 80-bit 85 prefix FE80::. 87 +-------+-------+-------+-------+-------+-------+------+------+ 88 | FE 80 00 00 00 00 00 00 | 89 +-------+-------+-------+-------+-------+-------+------+------+ 90 | 00 00 | Ethernet Address | 91 +-------+-------+-------+-------+-------+-------+------+------+ 93 =0C 94 INTERNET-DRAFT Transmission of IPv6 Packets Over Ethernet 1996-02-26 96 Address Mapping -- Unicast 98 The procedure for mapping IPv6 addresses into Ethernet link-layer 99 addresses is described in [DISC]. The Source/Target Link-layer 100 Address option has the following form when the link layer is 101 Ethernet. 103 +-------+-------+-------+-------+-------+-------+-------+-------+ 104 | Type |Length | Ethernet Address | 105 +-------+-------+-------+-------+-------+-------+-------+-------+ 107 Option fields: 109 Type 1 for Source Link-layer address. 110 2 for Target Link-layer address. 112 Length 1 (in units of 8 octets). 114 Ethernet Address 115 The 48 bit Ethernet IEEE 802 address, in canonical bit 116 order. This is the address the interface currently responds 117 to, and may be different from the built-in address used as 118 the address token. 120 Address Mapping -- Multicast 122 An IPv6 packet with a multicast destination address DST is 123 transmitted to the Ethernet multicast address whose first two octets 124 are the value 3333 hexadecimal and whose last four octets are the 125 last four octets of DST, ordered from more to least significant. 127 +-------+-------+-------+-------+-------+-------+ 128 | 33 | 33 | DST13 | DST14 | DST15 | DST16 | 129 +-------+-------+-------+-------+-------+-------+ 131 Security Considerations 133 Security considerations are not addressed in this memo. 135 =0C 136 INTERNET-DRAFT Transmission of IPv6 Packets Over Ethernet 1996-02-26 138 References 140 [AARCH] R. Hinden, S. Deering, IP Version 6 Addressing Architecture. 141 RFC1884. 143 [CONF] S. Thomson, IPv6 Stateless Address Autoconfiguration. Currently 144 draft-ietf-addrconf-ipv6-auto-07.txt. 146 [DISC] T. Narten, E. Nordmark, W. A. Simpson, Neighbor Discovery for IP 147 Version 6 (IPv6). Currently draft-ietf-ipngwg-discovery-05.txt. 149 [IPV6] S. Deering, R. Hinden, Internet Protocol, Version 6 (IPv6) 150 Specification. RFC1883. 152 Author's Address 154 Matt Crawford 155 Fermilab MS 368 156 PO Box 500 157 Batavia, IL 60510 158 USA 160 Phone: +1 708 840-3461 162 EMail: crawdad@fnal.gov