idnits 2.17.1 draft-omar-ipmix-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 62 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 2 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** There are 2 instances of too long lines in the document, the longest one being 4 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 20, 2020) is 1283 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) == Unused Reference: 'RFC2119' is defined on line 90, but no explicit reference was found in the text == Unused Reference: 'RFC8174' is defined on line 99, but no explicit reference was found in the text == Unused Reference: 'RFC0791' is defined on line 105, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2401 (Obsoleted by RFC 4301) Summary: 3 errors (**), 0 flaws (~~), 6 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Engineering Task Force Khaled Omar 2 Internet-Draft The Road 3 Intended status: Standards Track October 20, 2020 4 Expires: April 20, 2021 6 Internet Protocol Mixture (IPmix) Specification 7 draft-omar-ipmix-02 9 Abstract 11 This document specifies the Internet Protocol Mixture (IPmix). a 12 solution that allows IPv4-only hosts to communicate with IPv6-only 13 hosts and vice versa. 15 Status of This Memo 17 This Internet-Draft is submitted in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF). Note that other groups may also distribute 22 working documents as Internet-Drafts. The list of current Internet- 23 Drafts is at https://datatracker.ietf.org/drafts/current/. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 This Internet-Draft will expire on April 20, 2021. 32 Copyright Notice 34 Copyright (c) 2020 IETF Trust and the persons identified as the 35 document authors. All rights reserved. 37 This document is subject to BCP 78 and the IETF Trust's Legal 38 Provisions Relating to IETF Documents 39 (https://trustee.ietf.org/license-info) in effect on the date of 40 publication of this document. Please review these documents 41 carefully, as they describe your rights and restrictions with respect 42 to this document. Code Components extracted from this document must 43 include Simplified BSD License text as described in Section 4.e of 44 the Trust Legal Provisions and are provided without warranty as 45 described in the Simplified BSD License. 47 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 50 2. Notational Conventions and Terminology . . . . . . . . . . . 3 51 3. Internet Protocol Mixture (IPmix) . . . . . . . . . . . . . . 3 52 4. The Four Types of Communication . . . . . . . . . . . . . . . 4 53 4.1. IPmix: IPv6 Host to IPv4 Host . . . . . . . . . . . . . . 4 54 4.2. IPmix: IPv4 Host to IPv6 Host . . . . . . . . . . . . . . 5 55 4.3. IPmix: IPv6 Host to IPv6 Host . . . . . . . . . . . . . . 6 56 4.4. IPmix: IPv4 Host to IPv4 Host . . . . . . . . . . . . . . 7 57 5. Advantages of IPmix . . . . . . . . . . . . . . . . . . . . . 8 58 6. IPmix with DNS . . . . . . . . . . . . . . . . . . . . . . . 8 59 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 60 8. Security Considerations . . . . . . . . . . . . . . . . . . . 9 61 9. Acknowledgements . .. . . . . . . . . . . . . . . . . . . . . 9 62 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 63 10.1. Normative References . . . . . . . . . . . . . . . . . . 9 64 10.2. Informative References . . . . . . . . . . . . . . . . . 9 65 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 9 67 This contribution has been withdrawn. 69 7. IANA Considerations 71 TBC. 73 8. Security Considerations 75 The security features of IPmix are described in the Security 76 Architecture for the Internet Protocol [RFC2401]. 78 9. Acknowledgements 80 The author would like to thank S. Krishnan, W. Haddad, L. 81 Howard,C. Huitema, T. Manderson, JC. Zuniga, J. Touch, A. 82 Sullivan, , K. Thomann, S. Bortzmeyer, J. Linkova, R. Bonica, 83 F.Baker and T. Herbert for the useful inputs and discussions about 84 IPmix. 86 10. References 88 10.1. Normative References 90 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 91 Requirement Levels", BCP 14, RFC 2119, 92 DOI 10.17487/RFC2119, March 1997, 93 . 95 [RFC2401] Kent, S. and R. Atkinson, "Security Architecture for the 96 Internet Protocol", RFC 2401, DOI 10.17487/RFC2401, 97 November 1998, . 99 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 100 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 101 May 2017, . 103 10.2. Informative References 105 [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, 106 DOI 10.17487/RFC0791, September 1981, 107 . 109 Author's Address 111 Khaled Omar 112 The Road 113 6th of October City, 114 Giza 115 Egypt 117 Phone: 2 01003620284 118 Email: eng.khaled.omar@hotmail.com