idnits 2.17.1 draft-goswami-ipv6-discovery-link-option-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? == There is 1 instance of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 158 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations 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. ** There are 5 instances of too long lines in the document, the longest one being 10 characters in excess of 72. ** There is 1 instance of lines with control characters in the document. ** The abstract seems to contain references ([IPv6ND]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 48 has weird spacing: '...Options for N...' == Line 68 has weird spacing: '... 1/8 th octet...' -- 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 (Dec 21, 2001) is 8156 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) == Missing Reference: 'RFC 2119' is mentioned on line 32, but not defined == Missing Reference: 'IPv6ND' is mentioned on line 36, but not defined == Missing Reference: 'IPv6-ETHER' is mentioned on line 78, but not defined == Unused Reference: 'RFC2119' is defined on line 128, but no explicit reference was found in the text == Unused Reference: 'IANA-ALLOCATION' is defined on line 131, but no explicit reference was found in the text == Unused Reference: 'IEEE-EUI64' is defined on line 134, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2461 (ref. 'IPV6ND') (Obsoleted by RFC 4861) -- Possible downref: Non-RFC (?) normative reference: ref. 'IANA-ALLOCATION' -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE-EUI64' Summary: 9 errors (**), 0 flaws (~~), 11 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT Link-Layer Option Extension S. Goswami 3 Expires June 21, 2002 Self Inc 4 Dec 21, 2001 6 IPv6 Neighbor Discovery Link-Layer Option Extension 7 9 Status of this Memo 11 This document is an Internet-Draft and is in full conformance with all 12 provisions of Section 10 of RFC2026. 14 Internet-Drafts are working documents of the Internet Engineering Task 15 Force (IETF), its areas, and its working groups. Note that other groups 16 may also distribute working documents as Internet-Drafts. 18 Internet-Drafts are draft documents valid for a maximum of six months 19 and may be updated, replaced, or obsoleted by other documents at any 20 time. It is inappropriate to use Internet- Drafts as reference material 21 or to cite them other than as "work in progress." 23 The list of current Internet-Drafts can be accessed at 24 http://www.ietf.org/ietf/1id-abstracts.txt 26 The list of Internet-Draft Shadow Directories can be accessed at 27 http://www.ietf.org/shadow.html. 29 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 30 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 31 document are to be interpreted as described in RFC 2119 [RFC 2119]. 33 Abstract 35 This document describes changes to the Source/Target Link-layer Address 36 option in IPv6 Neighbor Discovery Protocol [IPv6ND] to support addresses 37 of any liength. 39 1. Overview and Rationale 41 The IPv6 Neighbor Disocvery Protocol uses Link-Layer addresses in option. 42 The option as it stands can only support link layer addresses of 6 + 8*n 43 octets, where n is natural number (i.e 0,1,2,3, ...). This precludes the 44 support for link layer addresses of arbitrary length that may need to 45 be supported in the future. One example of such an address is IEEE-EUI64 46 which is a 8 octet address. 48 2. Additional Requirements for Link-Layer Options for Neighbor Dicovery 50 This document adds two more option types to be used with Neighbor Discovery. 51 The 53 4.6.1. Source/Target Any Length Link-layer Address 55 0 1 2 3 56 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 57 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 58 | Type | Length | Link-Layer Address ... 59 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 61 Fields: 63 Type 64 11 for Source Any Length Link-layer Address 65 12 for Target Any Length Link-layer Address 67 Length The length of the option (including the type and 68 length fields) in units of 1/8 th octets. Forexample, 69 the length for IEEE 802 addresses is 1 [IPv6- 70 ETHER]. 72 Link-Layer Address 73 The variable length link-layer address. 74 The content and format of this field (including 75 byte and bit ordering) is expected to be specified 76 in specific documents that describe how IPv6 77 operates over different link layers. For instance, 78 [IPv6-ETHER]. 80 Description 81 The Source Link-Layer Address option contains the 82 link-layer address of the sender of the packet. It 83 is used in the Neighbor Solicitation, Router 84 Solicitation, and Router Advertisement packets. 86 The Target Link-Layer Address option contains the 87 link-layer address of the target. It is used in 88 Neighbor Advertisement and Redirect packets. 90 These options MUST be silently ignored for other 91 Neighbor Discovery messages. 93 2.2 Router Solicitation Message 95 In addition to the options mentioned in [IPV6ND], the Source Any Length 96 Link-layer Address can be used. 98 2.3 Router Advertisement Message 100 In addition to the options mentioned in [IPV6ND], the Source Any Length 101 Link-layer Address can be used. 103 2.4 Neighbor Solicitation Message 105 In addition to the options mentioned in [IPV6ND], the Source Any Length 106 Link-layer Address can be used. 108 2.5 Neighbor Advertisement Message 110 In addition to the options mentioned in [IPV6ND], the Target Any Length 111 Link-layer Address can be used. 113 2.6 Redirect Message Format 115 In addition to the options mentioned in [IPV6ND], the Target Any Length 116 Link-layer Address can be used. 118 4. Acknowledgments 120 The authors would like to thank Vince Laviano, Nidhi Bhaskar, and Steve 121 Deering and for their input and careful review. 123 5. References 125 [IPV6ND] Narten, T, et. al., "Neighbor Discovery for IP Version 6 126 (IPv6)", RFC 2461, December 1998. 128 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 129 Requirement Levels," RFC 2119, March 1997. 131 [IANA-ALLOCATION] Internet Assigned Numbers Authority, 132 http://www.isi.edu/in-notes/iana/assignments/multicast-addresses. 134 [IEEE-EUI64] GUIDELINES FOR 64-BIT GLOBAL IDENTIFIER (EUI-64�) 135 REGISTRATION AUTHORITY, http://standards.ieee.org/regauth/oui/tutorials/EUI64.html 137 6. Author's Address 139 Dr. Subrata Goswami 140 Self Inc. 141 Newark, CA 94560 142 sgoswami@umich.edu 144 This document expires June 21, 2002.