idnits 2.17.1 draft-durand-ipv6prefix-00.txt: ** The Abstract section seems to be numbered 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-20) 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 -- however, there's a paragraph with a matching beginning. Boilerplate error? ** 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 Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction 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 "Author's Address" (or "Authors' Addresses") section title is misspelled. -- 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.) -- Couldn't find a document date in the document -- date freshness check skipped. 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 (Obsoleted by RFC 2373) Summary: 11 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Engineering Task Force Alain Durand Jean-Luc Richier 2 INTERNET-DRAFT IMAG 3 Expire in six months November, 1996 5 IPv6 network prefix notation 7 9 1. Status 11 This document is an Internet-Draft. Internet-Drafts are working 12 documents of the Internet Engineering Task Force (IETF), its 13 areas, and its working groups. Note that other groups may also 14 distribute working documents as Internet-Drafts. 16 Internet-Drafts are draft documents valid for a maximum of six 17 months and may be updated, replaced, or obsoleted by other 18 documents at any time. It is inappropriate to use Internet- 19 Drafts as reference material or to cite them other than as 20 ``work in progress.'' 22 To learn the current status of any Internet-Draft, please check 23 the ``1id-abstracts.txt'' listing contained in the Internet- 24 Drafts Shadow Directories on ftp.is.co.za (Africa), 25 nic.nordu.net (Europe), munnari.oz.au (Pacific Rim), 26 ds.internic.net (US East Coast), or ftp.isi.edu (US West Coast). 28 2. Abstract 30 This memo propose a text representation of IPv6 network prefixes. 32 3. Motivation 34 RFC 1884 propose a text representation of IPv6 addresses. 35 IPv6 addresses consist of a network prefix and a local identifier. 37 Routing registry tables use network prefixes. Prefix lengths are 38 important informations for routing algorithms. A compact 39 notation to represent both informations is needed. 41 DRAFT IPv6 network prefix notation November 1996 43 4. Notation 45 An IPv6 address is a string of 128 bits that can be represented 46 per [RFC1884] by a string of hex digits separated by ":". 47 This address is composed by two substrings, the network prefix and 48 the local identifier. The boundary between those two substrings 49 is characterized by an integer, the prefix length plen, in the 50 interval [0 - 128]. 52 The proposed method to represent the network prefix is to 53 complement the prefix plen bit string by (128 - plen) bits 54 set to zero. This will make an IPv6 address. Then we represent 55 this address using [RFC1884] to obtain an hex string. The trailing 56 zeros are represented by "::". Eventually, we concatenate the 57 symbol "/" followed by the decimal notation of plen. 59 5. Examples 61 ::/96 IPv6 prefix for IPv4 compatible addresses 62 fe80::/10 link local prefix 63 5f06:b500::/32 site prefix 64 5f06:b500:8158:1a00::/80 local area network prefix 66 6. Security considerations 68 Security issues are not discussed in this memo. 70 7. References 72 [RFC1884] Hinden, R., and S. Deering, "IP Version 6 Addressing 73 Architecture", RFC 1884, December 1995. 75 8. Author address 77 Alain Durand & Jean-Luc Richier 78 Institut d'Informatique et de Mathematiques Appliquees de Grenoble 79 (IMAG), BP 53 38041 Grenoble CEDEX 9 FRANCE 81 Phone : +33 4 76 63 57 03 82 Fax : +33 4 76 51 49 64 83 E-Mail: Alain.Durand@imag.fr Jean-Luc Richier@imag.fr