Internet-Draft Abbreviated Title July 2023
Kadavill Expires 7 January 2024 [Page]
Workgroup:
Internet Engineering Task Force
Internet-Draft:
draft-rfcxml-general-ipv11-standard-00
Published:
Intended Status:
Standards Track
Expires:
Author:
K. Kadavill, Ed.

Internet Protocol version 11

Abstract

Standard for IPv11 address format and routing theory

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on 7 January 2024.

Table of Contents

1. Introduction

IPv6 has been routing packets by forwarding packets to gateways after gateways until it reaches its destination network . BGP Networks seem to be working on a bus or Ring topology network. This happened because IPv6 addresses were bland and had no networking information in them. We plan to right these wrongs with IPv11. A 128 bit address with 24 bit chunks ancestors and host. Since 24 chunks means just 16,777,216 clients per child network or hosts so they are easy to manage.

1.1. Requirements Language

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.

2. IPv11

The Internet Protocol Version 11

2.1. Address Format

The format for an IPv11 address starts with an Octet and its value is a constant hexadecimal number 0x0B which tells the device that it is an IPv11 IP address. The next 24 bits is the first ancestor of the ip address.If any ancestor is 0x000000 it means there is no network assigned to this part of the network address. The next 24 bits are its child network of the client address.The next child (network network )is 24 bits and so on until the last 24 bits. The host ip address is always the last 24 bits of the IP address .IPv11 IP address is of the format: 0BXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXHH:HHHH.

Table 1
IP Address
Host Part of address 0BXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXHH:HHHH
Parent network address, network address and child network address of host 0BPP:PPPP:NNNN:NNCC:CCCC:XXXX:XXXX:XXXX
Parent network address, network address and child network address of host 0BXX:XXXX:PPPP:PPNN:NNNN:CCCC:CCXX:XXXX

2.2. IPv11 Assignment

IP addresses are assigned sequentially to network AA(autonomous authorities) starting at the first address from the last 24bit child network i.e. the first network address is 0B::100:0000.

Table 2
IP Address
First network to assign 0B::100:0000
Last network to assign 0BEF:FFFF:FFFF:FFFF:FFFF:FFFF:FF00:0000

2.3. Broadcast address

Any network can be broadcasted to by filling in the ancestor part of the address and masking the rest part of the networks (and host address) with the value F . This will send data to child network AAs (or host). An example of a broadcast address is 0BXX:XXXX:FFFF:FFFF::FFFF:FFFF:FFFF:FFFF this will broadcast to next 16,777,216 child networks of OBXX:XXXX:: network

Table 3
IP Address
Broadcast address of first network 0B::1FF:FFFF
Broadcast address of last network 0BEF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF

2.4. Routing

Routing is accomplished by first finding how many 24 bits match in the source and the destination IP address. Then querying child AA’s for the next 24 bit address.this process is repeated for every network. Each AA’s network tables contain all known immediate children (a max of 16777216) the best route to the next child network in the path. Routes can be optimized later by lookin for shortcut pathways to networks on route to the destination. This can be accomplished by looking for matching sibling gateways to child networks in the pathway to the destination

3. IANA Considerations

This memo includes no request to IANA.

4. Security Considerations

This document should not affect the security of the Internet.

5. References

5.1. Normative References

[RFC2119]
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.
[RFC8174]
Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <https://www.rfc-editor.org/info/rfc8174>.

5.2. Informative References

[Wikipedia]
Wikipedia, "Wikipedia", , <https://www.wikipedia.org/>.

Author's Address

Kiran Kadavill (editor)
#34, Goshree Garden,Arattuvazhi Road
Njarakkal 682505
KERALA 682505
India