Internet Draft E. Terrell Category: Proposed Standard ETT-R&D Publications Expires: January 27th, 2008 July 2007 The IPtX Domain Name Service Specification; IPtX-MX DNS 'draft-terrell-iptx-mx-dns-specification-03' Status of this Memo Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. 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 document may not be modified, and derivative works of it may not be created, except to publish it as an RFC and to translate it into languages other than English." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Intellectual Property Rights (IPR) Statement By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Requirements Terminology The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this document, are to be interpreted as described in [RFC-2119]. Conventions Please note, the mathematical operators that cannot be represented in the 'txt' file format, which represent; the '^' Carrot sign for Super-Script, and the 'v' sign is used for Sub-Script(or Nested). This Internet-Draft will expire on January 27th, 2008. E Terrell Internet Draft [Page 1] The IPtX-MX Domain Name Service Specification January 27th, 2008 Abstract This document defines the IPtX Specification for the 'Domain Name Service' (IPtX / IPtX-MX DNS), and eliminates the possibility of an Addressing 'Conflict', or a Mathematical Addressing Error in the IPtX Address Space when using Multiple IPtX Addressing Formats. In other words, the IPtX / IPtX-MX IP Addressing format on the "Back-End", or "Backbone", obtains its uniqueness through the use and / or difference defined by the accuracy of the 'Exponential Decimal String'. However, this uniqueness, if not clarified, would not be discernable on the "Front-End", because the IPtX IP Addressing Specification 'Allows' only a '48' Bit-Mapped IP Address, or 2 Octets and 4 '10 Bit-Quadrants', and up to 60 Bits for every IP Addressing Format greater than IPt1. That is, on the "Front-End", if there is No distinction, because every Addressing Format in the IPtX Specification, when Resolved, is Equal, there will ultimately be Address Conflicts within the Addressing Scheme. Nevertheless, this clarification, when used in conjunction with the IPtX 32 / 64 Bit Header, allows the simultaneous use of (2E24) 16,777,216 different IPtX / IPtX-MX IP Addressing Specifications; the Concurrent use of the IPtX / IPtX-MX IP Addressing Specifications 'IPt1' thru 'IPt16,777,216'. E Terrell Internet Draft [Page 2] The IPtX-MX Domain Name Service Specification January 27th, 2008 Table of Contents Abstract Introduction IANA Considerations I. IPtX / IPtX-MX DNS 'Scaled Spanning Tree' database II. IPtX 32 / 64 Bit Header Design Specification - 'Variable IP Addressing Format Range Bit-Mapped Capacity' - e.g.; IPt1 thru IPtX III. IPtX 32 / 64 Bit - DNS Header, DNS Query, DNS Resource Record, TCP Header, TCP Pseudo Header, UDP Header, and UDP Pseudo Header, Design Specification(s) - Security Considerations IANA Isolation and Privatization Options References Work(s) in Progress Normative References Informative References E Terrell Internet Draft [Page 3] The IPtX-MX Domain Name Service Specification January 27th, 2008 Introduction The profoundness of the 'IPtX Specification' is that, it represents and defines a Real Conundrum. In other words, IP Addressing in the IPtX Specification, is a Mathematical Enigma that begs the question; 'How much does anyone really know about the Human Neuronic Processes? Or more specifically; 'Does anyone truly understand the Communication Process of the Neuron (perhaps, Macro and Quantum Levels), to actually develop a 'True Artificial Intelligence'? In which case, it should be understood; Today's Computers cannot discern the 'Identity', or 'Equality', between any two or more IP Addresses having Numerical Values that actually define the same IP Address in the IPtX Specification - e.g.; 213 = 00E0000.0000... ~ 2 E 7 . 73 11010101 11 11001010 111 . 1001001 Bit-Mapped Length = 110101011111001001 ~ 18 Bits 213 = 00E0000.0000... ~ 2 E 7 . 735 11010101 11 11001010 111 . 1011011111 Bit-Mapped Length = 110101011111011011111 ~ 21 Bits The distinction between the Binary Numerals is defined by the Accuracy of the 'Exponential Decimal String', which represents a Unique Binary Sequence from the Binary Set, {0,1}. However, while this clearly defines a valid conclusion, it is sustained only on the "Back-End". In other words, when converting the Binary Sequence into the Integer representing the IP Address, an additional Tag, which identifies (equaling the 'CIDR Network Descriptor') the Bit-Mapped Length of the Addressing Format being used is necessary when making a distinction - where; E Terrell Internet Draft [Page 4] The IPtX-MX Domain Name Service Specification January 27th, 2008 11111111 : 11 11111111 Variable Bit Length . Variable Bit Length = 0000 : 2 E 0000 . 0000... 2E0000 . 0000... = XXX:XXX:XXX.XXX.XXX.XXX -/+ /0000:00 = IPtX IP Address And given that the Display of the 'CIDR Network Descriptor' is replaced with the Display of the Name of the Addressing Format identifying the Bit-Mapped Length of the IPtX Addressing Format being used; -/+ /0000:00 = IPtX = {IPt1, IPt2, ... IPt100, ... IPtX} The User sees the Binary Conversion of '2E0000 . 0000...' only as the Integer which represents the IPtX IP Address - In other words, using the IPtX / IPtX-MX DNS 'IP Addressing Format Tag', which distinguishes the Addressing Specification using an 'A' to represent the number of 32 Bit Groupings the Addressing Format contains, prevents 'Front-End' Address Resolution Conflicts. - As given by; E Terrell Internet Draft [Page 5] The IPtX-MX Domain Name Service Specification January 27th, 2008 XXX:XXX:XXX.XXX.XXX.XXX /XA - Or - XXX:XXX:XXX.XXX.XXX.XXX /IPtX IPtX = {IPt1, IPt2, ... IPt100, ... IPtX} = /XA Note: Where X = {Any Integer}, and A = {One 4 Octet Group} 213:112:238.009.112.001 /XA, or 213:112:238.009.112.001 /IPtX and the 'Preferred', since ; XA = 16 Bits, /XA = 16 Bits = 2EX; An 'IPtX / IPtX-MX DNS Tag' 2EX; 3 Bit = Exponent = 2^3, 3 Bit Decimal String = 2^3 2EX = 2E8.8; 2E8.8 = The Number of ('A') Octet Groupings (Yielding a 8 Bit Number with a 8 Bit Decimal String Accuracy) Or [/X < / = 2^24 : A = Class ID - ('ID' = A, B, C, D, or E)] = /XA 3 State CIDR Network Descriptor 8 - 16 Bit - Switch {'0','+','-', '/'} [Where '0' means "No Sign" or '/'] \ / \ / THE END-NODE OR FRONT-END | | Network IP | | 8 - 16 Bits | Address | | | 8 (10 Bit > IPt1) | ~ 40 Bits Or | | | ZONE IP ADDRESS | 4-8 Bit Octets | | | 8 - 16 Bits \ |/ \ / \| | | | '2EX' = [ XXX : XXX : 999 . 999 . 999 . 999 '?' / X A ] ~ 104 Bits \ / | \ 8 (10 Bit > IPt1) - IP AREA CODE ADDRESS / | \ / / \ \ 16 thru 48 Bits - 'IPtX / IPtX-MX DNS Tag' E Terrell Internet Draft [Page 6] The IPtX-MX Domain Name Service Specification January 27th, 2008 Note: If - (Perfix x Zone IP x IP Area Code) = 2^24; (Network IP Address) ~ 2^40; (IPtX-MX DNS Tag) = 2^48; And - 104 Bit-Mapped Length = (2^16) x ((2^40) x (2^48) = 2EX Then - (2^24) x (2^40) x (2^48) = 0000:2EX0000.0000... = IPt1 = [2^24 = Unused Bits] x (2^24) x (2^40) x (2^48) = 2^136 [2^24 = Unused Bits = Back-End ISP ID = Internet Service Provider 'ID'] [X > / = 1 and < / = 2E24 : A = Class ID] = /XA 'IPtX / IPtX-MX IP Addressing DNS Tag' Given that; if the DNS Tag, in essence, represents a Function 'Call' that determines the IPtX Addressing Format being used, then it (the DNS Tag) must also determine the accuracy of the Exponential Decimal String - as given by; 0000:2E0000.0000... - 'DNS Tag' = /XA 0000:2E'0000.0000... - 'DNS Tag' = /XA' Clearly then, any translation and / or distinction available to the user, must also be defined within the code of the Operating System, and in particular, defined within the code of the 'Domain Name Service' for the IPtX / IPtX-MX DNS Specification. E Terrell Internet Draft [Page 7] The IPtX-MX Domain Name Service Specification January 27th, 2008 IANA Consideration I. IPtX / IPtX-MX DNS 'Scaled Spanning Tree' database IPtX Global Root / | | | | \ / / | | \ \ / / | | \ \ / / | | \ \ / | | | | \ NA SA EU AF AU OS 'GLOBAL ROOT' - 'PREFIX' Scaled Range = '1 - 256 = '0000:' |-------------------------------------------------------------------| | | | | | | | | | | | | | | | | | | | | 001 002 003 004 005 006 007 008 009 010 011...125...207... 242... 256 Global Root IPtX-MX IP Address 0000:2E0000.0000... = 0000:0E0 = 0000:E - 'NA' - GOLBAL ROOT 'PREFIX' ; '0000:' / | \ / | \ / | \ / | \ CANADA MEXICO UNITED STATES 'ZONE IP ROOT' - Scaled Range for every GR 'PREFIX' = '1 - 256' |-------------------------------------------------------------------| | | | | | | | | | | | | | | | | | | | | 001 002 003 004 005 006 007 008 009 010 011...125...207... 242... 256 Continent Country/State City/Town User.Friendly.Name ccTLD +---------+-------------+--------------+-----------------+----------+ | Prefix :| Zone IP : |IP Area Code :| IPtX IP Address | /XXXX:XX | +- 0000: -+-- XXX : ---+---- XXX : --+ XXX.XXX.XXX.XXX +----------+ E Terrell Internet Draft [Page 8] The IPtX-MX Domain Name Service Specification January 27th, 2008 UNITED STATES - 'ZONE IP ROOT' / \ / \ 'IP AREA CODE' DISTRIBUTION - Scaled Range Per Zone IP = '1 - 256' / \ / \ |-------------------------------------------------------------------| | | | | | | | | | | | | | | | | | | | | 001 002 003 004 005 006 007 008 009 010 011...125...207... 242... 256 .Record (Tag) Continent Country/State City/Town User.Friendly.Name ccTLD +---------+-------------+--------------+-----------------+----------+ | Prefix :| Zone IP : |IP Area Code :| IPtX IP Address | /XXXX:XX | +- 0000 -+--- XXX ---+---- XXX ---+ XXX XXX XXX XXX +--- /X A -+ IPtX-MX IP Address Distribution per IP Area Code ~ 2E40 |-------------------------------------------------------------------| | | | | | | | | | | | | | | | | | | | | 001 002 003 004 005 006 007 008 009 010 011...125...207... 242... 256 ^ | /|\ / | \ / | \ / | \ /| | |\ / | | | \ / | | | \ / | | | \ / | | | \ Class Class Class Class Class A B C D E \ \ | / / \ -/+ /XXXX:XX / "IPtX Default 'Network Domain Name Address' Design Specification" Zone IP IP Area Code IP Address ccTLD (Tag) |-----XXX:-----|-------XXX:-------|----------------------|-------------| Country/State: City/Town/Village: User.Friendly.Name .Record Name | V Country/Province City/Town/Village User.Friendly.Name Record Name |-----XXX:-----|-------XXX:-------|--- XXX XXX XXX XXX ---|+/-/0000:00 | E Terrell Internet Draft [Page 9] The IPtX-MX Domain Name Service Specification January 27th, 2008 Default IPtX Specification 'Network Domain Name Specification' Continent Country/State City/Town User.Friendly.Name ccTLD +---------+-------------+--------------+-----------------+----------+ | Prefix :| Zone IP : |IP Area Code :| IPtX IP Address | /XXXX:XX | +- 0000 -+--- XXX ---+---- XXX ---+ XXX XXX XXX XXX +--- /X A -+ |-------------------------------------------------------------------| | | | | | | | | | | | | | | | | | | | | 001 002 003 004 005 006 007 008 009 010 011...125...207... 242... 256 ^ | /|\ / | \ / | \ / | \ /| | |\ / | | | \ / | | | \ / | | | \ / | | | \ Class Class Class Class Class A B C D E ^ | | / \ / / \ \ / / / \ \ \ / / / | \ \ \ / / / | \ \ \ / / / | \ \ \ / / / | \ \ \ / / / | \ \ \ / / \ | / \ \ .com .edu .gov .int .mil .net .org E Terrell Internet Draft [Page 10] The IPtX-MX Domain Name Service Specification January 27th, 2008 NOTE: Logical Argument supporting the introduction of the CLASS System Specification - defining the IP Area Code Sector(s); 1) Backward Compatibility with the IPv4 Addressing Specification 2) A IPtX / IPtX-MX DNS IP Addressing Tag used to distinguish between 2 or more different IPtX / IPtX-MX Addressing formats Furthermore, because the IPtX Specification Counts Sequentially, even with the inclusion of the 'CLASS ID', the IPtX Specification remains CIDR Compliant. In other words, because it Counts Sequentially, on the 'Back-End', everything is either a Large or a Small Binary Number; there are No Classes on the 'Backbone'. However, the actual benefit gained by using the CLASS System, is the Expansion of the IP Address Pool for the IPtX / IPtX-MX Specification, which defines the simultaneous use of Multiple IPtX IP Addressing Formats - As viewed from the 'Front-End', e.g., every 'IP Area Code Address' can be Divided into an Infinite Number of Sectors defined by up to 26 CLASS ID categories, which represents an Individual IPtX / IPtX-MX IP Addressing Specification; a distinct IPtX / IPtX-MX Addressing Format. {See pages 4 thru 7}; Recall that the IPtX-MX DNS IP Addressing Tag - '+/- /XA', defines; X = Any Integer, and A = One 4 Octet Group Where; A = Class A, Class B, Class C, ..., Class Z - And every CLASS ID represents ONE 4 OCTET GROUP; - As in; /XA, /XB, /XC, /XD, ..., /XZ. In other words, the 'CLASS ID' Designation allows the creation of a Rectangular Array, representing the Expansion Capabilities of the IPtX / IPtX-MX Addressing Specification - as given below; Consistent Rows representing an Identical IPtX Addressing Format IPt1 = X = 1 Class A, Class B, Class C, ..., Class Z = /1 Class ID IPt2 = X = 2 Class A, Class B, Class C, ..., Class Z = /2 Class ID IPt3 = X = 3 Class A, Class B, Class C, ..., Class Z = /3 Class ID IPt4 = X = 4 Class A, Class B, Class C, ..., Class Z = /4 Class ID IPt5 = X = 5 Class A, Class B, Class C, ..., Class Z = /5 Class ID : : : : : : : : : : : : : : : : : : : : : : : : IPtX = X = Infinity Class A, Class B, ..., Class Z = /Infinity Class ID E Terrell Internet Draft [Page 11] The IPtX-MX Domain Name Service Specification January 27th, 2008 [The Number of IPtX IP Addressing Formats that can be used Simultaneous, is Specified by the Range Limits of the Default Source and Destination Address Fields in the '32 / 64' Bit IPtX Header - See page 15. e.g.; Currently, using IPt1, the maximum number of IPtX Addressing Formats (Values for 'X', the 32 Bit incremental progression defining a different IPtX Addressing Format) defined by the IPtX-MX DNS Tag, is equal to 2E24 (2^24 or 'IPt16,777,216'); which means, 16,777,216 different IPtX Addressing Formats can be used Simultaneously.] -- OR -- Staggered Rows representing different IPtX Addressing Format IPt1 = Class A, IPt2 = Class B, IPt3 = Class C, IPt6 = Class D, ... etc. The Expansion the CLASS ID System clearly provides, since every Column is defined by an Alpha Character following an Alphabet Sequence, defines a 'Rectangular Array' having; 26 Columns The Number of ROWS however, is defined by the Limits of the IPtX IP Address Bit-Mapped Length specified in the IPtX 'Header'. Furthermore, it should be understood, when analyzing the IPtX 32 / 64 Bit Header Specification (see page 15), only the Bit-Map of the Integer representing the Bit-Mapped Length for the Binary Numeral defining the Exponent and Exponential Decimal String, for every IP Address, is specified in the IPtX Header. In other words, the Exponent and the Exponential Decimal String defined in IPtX 32 / 64 Bit Header and the IPtX IP Addressing Specification is a Variable, which represents a Nested Exponential Base 2 Operation defining only the Bit-Map Length for the Exponent and the Exponential Decimal String. And more importantly, because the Exponent and the Exponential Decimal String defines a Binary Numeral instead of an Integer, the Number of IPtX Addressing Formats that can be used Concurrently and Handled by the IPtX Header increases astronomically. - as given by the examples below, we have; E Terrell Internet Draft [Page 12] The IPtX-MX Domain Name Service Specification January 27th, 2008 Example 1.a e.g. - If 0000:2E0000.0000... = 0000:2E78.32 Bits - where 2E78.32 = 78 Bit Exponent = 2^78, and a 32 Bit Exponential Decimal String = 2^32; - converts to the respective Integer(s) given by; a) 78 Bit Exponent = 2^78 = 302,231,454,903,657,293,676,544 b) 32 Bit Exponential Decimal String = 2^32 = 4,294,967,296 In which case, only the Bit-Map of 2^78, representing the Exponent, and the Bit-Map of 2^32 (defining the Bit-Mapped of the Result from a Base 2 Exponential Operation), defining the Exponential Decimal String, as in 2E78.32, are defined by the Bit-Mapped Address Fields in the IPtX 'Header' (see page 15). Or, as given by the second example; Example 2.a where, e.g. - If 0000:2E0000.0000... = 2E198.868003799... Bits - where 2E78.32 = 198 Bit Exponent = 2^198, and the 868003799... Bit Exponential Decimal String ~ 2^30; - converts to the respective Integer(s) given by; a) 198 Bit Exponent = 2^198 2^198 = 11000110 b) 868003799... Bit Exponential Decimal String ~ 2^30 2^30 ~ 868003799... = 110011101111001010111111010111 - And 2E198.868003799... = 733,220,031,361,163,229,807,327, 628,901,324,958,746,998,773,250, 008,505,586,546 = 60 Digit Integer In any case, once again, only the Bit-Map of 198, representing the Exponent, and the Bit-Map of '868003799...', defining the Exponential Decimal String, as in 2E198.868003799..., are defined by the Bit-Mapped Address Fields in the IPtX 'Header'. In other words, the Mathematical Operations involving the Masking and Un-Masking procedures, which resolves the Integer representing an IPtX / IPtX-MX IP Address from the Conversion of the Binary Bit-Mapped Transmission, are function(s) that are Hardware Specific - See TCP/IP and OSI Model(s). Hence, the size specification for the measurement of the Length of the Bit-Mapped IP Address Field(s) for the IPtX Header, represents a Nested Exponential Operation – as given by; E Terrell Internet Draft [Page 13] The IPtX-MX Domain Name Service Specification January 27th, 2008 Example 3.a SOURCE & DESTINATION ADDRESS Field(s) = 2E 14 / 46 Bits = 2E 11111111111111 Bits = 14 Bits = 14 Bits = 2^14 = 16,384 Bit Exponent = 2E 1111111111111111111111111111111111111111111111 = 46 Bits = 46 Bits = 2^46 = 70,368,744,177,664 Bit Exponent In other words, the Bit-Mapped Displacement defining the Length of the 'SOURCE & DESTINATION ADDRESS' Field(s) in the IPtX Header, just as with any IPtX-MX IP Addressing Format, as noted in Example 1.a, represents the Mathematical equation involving a NESTED Exponential Base 2 Operation. That is, given that the Exponent actually equals the Binary Conversion for the Integer equaling the Result from an Exponential Base 2 Operation. Then Example(s) '1.a' and '3.a' must represent the Bit-Map of the Binary Numeral defining the Integer (or Irrational Number) representing the Exponent and the Exponential Decimal String. While in Example 2.a, the Integer (or Irrational Number) representing the Exponent and the Exponential Decimal String, defines the Bit-Map Displacement or Binary Conversion of the Result from the Exponential Base 2 Operation. (Please Note: The use of Separate Fields to define the Exponent and the Exponential Decimal String in the IPtX Header is Preferred, because this method increases the size of the IP Address Pool for the IPtX / IPtX-MX Specification and the accuracy Exponential Decimal String.) E Terrell Internet Draft [Page 14] The IPtX-MX Domain Name Service Specification January 27th, 2008 II. IPtX 32 / 64 Bit Header Design Specification - 'Variable IP Addressing Format Range Bit-Mapped Capacity' - e.g.; IPt1 thru IPtX The current IP Bit-Mapped Transmission of an IP Address, is nothing more than the 'End or Station' Node Software Translation of a Binary Numerical Conversion. Clearly, utilizing the same principles and continuing the exploitation of the 'DCE Unit'. The Compression Range of a 22 to 54 Bit-Mapped IPtX IP Addressing Format, can be reduced to the Bit-Mapped Length of a 32 or 64 Bit Header. IPtX 32 / 64 Bit Header 0 1 2 3 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 2 / 32 Bit Header Scale / / / 0 2 4 6 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2 4 / 64 Bit Header Scale / / / IPtX 32 / 64 Bit Header Information Fields / / / / |IPtX | IHL | TOS & NEXT HEADER | TL & DIRECTION BIT | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | ID & SECURITY BIT |FLA| FRAG OFFSET |:IP PBX Send*|/XXXX:XX | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | TTL-HOP LIMIT | PROTOCOL*|:IP PBX Recv*| CHK SUM | ConfCall*| |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | Prefix | SOURCE ADDRESS Exponent = 2E 14 / 46 Bits | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | SOURCE ADDRESS Exponential Decimal String = 2E 22 / 54 Bits | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | Prefix |DESTINATION ADDRESS Exponent = 2E 14 / 46 Bits| |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| |DESTINATION ADDRESS Exponential Decimal String = 2E22/54 Bits| |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | 2E10.12 Bits = Options = 2E24.30 Bits | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | 2E10.12 Bits = DATA = 2E24.30 Bits | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| |-------------------------------------------------------------| Note*:The Option for Different Field Definition(s) is Available. E Terrell Internet Draft [Page 15] The IPtX-MX Domain Name Service Specification January 27th, 2008 INTERNET PROTOCOL tX (32 / 64 Bit) ADDRESS SPACE IPtX / IPtX-MX IP Address ' 0000:2E0000.0000... ' | 8 Bits | 8/10 Bits | 8/10 Bits | ~ 40 Bits 16-48 Bits +---------+-----------+--------------+-----------------+----------+ | Prefix :| Zone IP : |IP Area Code :| IPtX IP Address |?/XXXX:XX | +- 0000 -+-- XXX --+---- XXX ---+ XXX XXX XXX XXX + '+/-/XA' + CIDR IP IPtX Network Distribution Prefix Zone IP Area Code IP Address Descriptor Purpose Date -------+---------+----------+-----------------+--------+---------+----- None | None | None | 000.000.000.000 | None | None | 7/07 001 | 001-256:| All: | XXX.XXX.XXX.XXX | All | NA | 7/07 002 | 001-256:| All: | XXX.XXX.XXX.XXX | All | SA | 7/07 003 | 001-256:| All: | XXX.XXX.XXX.XXX | All | EU | 7/07 004 | 001-256:| All: | XXX.XXX.XXX.XXX | All | OS | 7/07 005 | 001-256:| All: | XXX.XXX.XXX.XXX | All | AU | 7/07 006 | 001-256:| All: | XXX.XXX.XXX.XXX | All | AF | 7/07 007-256| 001-256:| All: | XXX.XXX.XXX.XXX | All | IANA/RSV| 7/07 001-256| 001-256:| All: | - -.XXX.XXX.XXX | All* |IANA/TELe| 7/07 None | None | None | 127.000.000.000 | None | LoopBack| 7/07 001-256| 001-256:| All: |1/- -.- -.YYY.000| All |IANA/Emer| 7/07 SA = South America, NA = North America, EU = European Union, AU = African Union, AF = Asian Federation, OS = Oceania States Note: For IPtX-MX IP Addressing Specifications > IPt1; the Zone IP and IP Area Code Divisions = '1 - 999'; resulting in a 60 Bit Users IPtX / IPtX-MX IP Address: "999: 999: 999.999.999.999 '+/- /XA' = 2EX". IANA EMERGENCY BROADCAST IP ADDRESS 001-256| 001-256:| All: | - -.- -. e .911 | All |IANA/Emer| 7/07 Note: In addition to Character usage, Numerical Values can be used to allow the remaining IP Addresses in IANA EMERGENCY Section, to create a 'Network AnyCast/BroadCast Address Pool'. And more importantly, these are not Radio 'Broadcast Frequency Channel(s)' [See - 'Work(s) in Progress' [12]. E Terrell Internet Draft [Page 16] The IPtX-MX Domain Name Service Specification January 27th, 2008 IPtX / IPtX-MX IP Address ' 0000:2E'0000.0000... ' | 8 Bits | 8/10 Bits | 8/10 Bits | ~ 40 Bits 16-48 Bits +---------+-----------+--------------+-----------------+----------+ | Prefix :| Zone IP : |IP Area Code :| IPtX IP Address |?/XXXX:XX | +- 0000 -+-- XXX --+---- XXX ---+ XXX XXX XXX XXX + '+/-/XA' + CIDR IP IPtX Network Distribution Prefix Zone IP Area Code IP Address Descriptor Purpose Date -------+---------+---------+-----------------+--------+---------+----- None | None | None |1/000,000,000,000| None | None | 7/07 001 | 001-256:| All: |1/XXX.XXX.XXX.XXX| All | NA | 7/07 002 | 001-256:| All: |1/XXX.XXX.XXX.XXX| All | SA | 7/07 003 | 001-256:| All: |1/XXX.XXX.XXX.XXX| All | EU | 7/07 004 | 001-256:| All: |1/XXX.XXX.XXX.XXX| All | OS | 7/07 005 | 001-256:| All: |1/XXX.XXX.XXX.XXX| All | AU | 7/07 006 | 001-256:| All: |1/XXX.XXX.XXX.XXX| All | AF | 7/07 007-256| 001-256:| All: |1/XXX.XXX.XXX.XXX| All | IANA/RSV| 7/07 001-256| 001-256:| All: |1/- -.XXX.XXX.XXX| All* |IANA/TELe| 7/07 None | None | None | 127.000.000.000 | None | LoopBack| 7/07 001-256| 001-256:| All: |1/- -.- -.YYY.000| All |IANA/Emer| 7/07 SA = South America, NA = North America, EU = European Union, AU = African Union, AF = Asian Federation, OS = Oceania States Note: For IPtX-MX IP Addressing Specifications > IPt1; the Zone IP and IP Area Code Divisions = '1 - 999'; resulting in a 60 Bit Users IPtX / IPtX-MX IP Address: "999: 999: 999.999.999.999 '+/- /XA' = 2EX". E Terrell Internet Draft [Page 17] The IPtX-MX Domain Name Service Specification January 27th, 2008 III. IPtX 32 / 64 Bit - DNS Header, DNS Query, DNS Resource Record, TCP Header, TCP Pseudo Header, UDP Header, and UDP Pseudo Header, Design Specification(s) - CHANGES: IPtX DNS Services 32 / 64 Bit Header DNS Header for IPtx | DNS Query for IPtX | DNS RR Record for IPtX ------------------------|----------------------|-----------------------| Identification = | Type = 2E18.20 Bits | Type = 2E18.20 Bits 2E15.25 Bits | | Opcode = 4 Bits | Class = 16 Bits | Class = 16 Bits | | Rcode = 4 Bits | Length Rdata = | TTL = Variable to | 2E12.20 Bits | 2E22.40 Bits ------------------------|----------------------|-----------------------| | TQuestions = 2E12.20 Bits | 4 New "TYPE" Categories | TAnswers RR = 2E12.20 Bits |1. TYPE 43 = 'RNN' | = "Reverse Network Domain Name" | Title: IN-ADDR.APARA NAME TAuthority RR = 2E12.20 Bits | = IN-ADDR.RNN | |2. TYPE 44 = 'RNN-PTR' | = "Reverse Network Domain TAdditional RR = 2E12.20 Bits| Name-Domain Name Pointer" | CIDRNetDes = XXXX:XX | /XXXX:XX = 8 Bits | 2 New IPtX DNS Tag(s) Specifications | |3. TYPE 45 = XA = "IPtX DNS Address Tag" | Where X = Integer Variable >/= 1 | - e.g. IPt1 = A, IPt2 = AA = 2A, | IPt3 = AAA = 3A, IPt4 = AAAA = 4A, etc | |4. TYPE 46 = XA' = "IPtX DNS Address Tag" -----------------------------|-----------------------------------------| Note: Approximating the Number of Digits representing the Integer from a Binary Conversion, or the Bit-Mapped Displacement / Length of an Integer, is more accurately defined as; Bit-Map Length / 3 ~ Number of Digits e.g.; 2E30 = 2^30 = 1073741824 Bit Length ~ 357,913,941 Digit Number E Terrell Internet Draft [Page 18] The IPtX-MX Domain Name Service Specification January 27th, 2008 DNS Header 64 Bit IPtX 0 2 4 6 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2 4 | Identification-XXXX:XX |QR|Opcode|AA|TC|RD|RA|Z|AD|CD|Rcode | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | Total Questions = 2E10.12 Bits = Total Answer RRs | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | Total Authority RRs = 2E10.12 Bits = Total Additional RRs | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | Questions | | = 2E24.30 Bits | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | Answer RRs | | = 2E24.30 Bits | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | Authority RRs | | = 2E24.30 Bits | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | Additional RRs | | = 2E24.30 Bits | |-------------------------------------------------------------| DNS Header 32 Bit IPtX 0 1 2 3 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 2 | Identification-XXXX:XX |QR|Opcode|AA|TC|RD|RA|Z|AD|CD|Rcode | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | Total Questions | Total Answer RRs | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | Total Authority RRs | Total Additional RRs | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | Questions | | = 2E10.12 Bits | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | Answer RRs | | = 2E10.12 Bits | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | Authority RRs | | = 2E10.12 Bits | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | Additional RRs | | = 2E10.12 Bits | |-------------------------------------------------------------| E Terrell Internet Draft [Page 19] The IPtX-MX Domain Name Service Specification January 27th, 2008 IPtX DNS Query 32 / 64 Bit 0 1 2 3 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 2 / 32 Bit Header Scale / / / 0 2 4 6 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2 4 / 64 Bit Header Scale / / / | 2E10.12 Bits = Query Name = 2E24.30 Bits | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | ::: | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | ::: | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | Type | Class | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | 2E10.12 Bits Or 2E24.30 Bits | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | ::: | |-------------------------------------------------------------| E Terrell Internet Draft [Page 20] The IPtX-MX Domain Name Service Specification January 27th, 2008 DNS Resource Record for IPtX 0 1 2 3 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 2 / 32 Bit Header Scale / / / 0 2 4 6 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2 4 / 64 Bit Header Scale / / / | 2E10.12 Bits = Name = 2E24.30 Bits | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | ::: | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | ::: | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | Type | Class | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | 2E10.12 Bits = TTL = 2E24.30 Bits | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | Length Rdata | Rdata ::: | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | ::: | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | 2E10.12 Bits Or 2E24.30 Bits | |-------------------------------------------------------------| Note: There is room for improvement, i.e. TTL = 2E24.30... Bits! This is clearly Ridiculous... However, this represents Backwards Compatibility at its Best. At least now, Networking the Moon, or perhaps Mars, seems plausible. Nevertheless, the difference between the Fields defining the Headers for the 'Binary' IPtX-MX IP Addressing Specification, which pertains specifically to IP Addressing, only involves the Mathematics associated with Changing the Exponential Operator, E, to E'. However, it also necessitates the specification defining the use of a "T" for 'TELe' and an 'M' for Mobile, as the Operational Function(s) defined 'by / in' the CIDR Network Descriptor for Transmission and Front-End' Address Resolution. In which case, 'X' becomes; 'X = T (TELe)', or 'X = M (Mobile)', in '/XA', which respectively represents the '/TA', and '/MA' IPtX-MX DNS Tags for use in Telephony and Mobile Transmissions. E Terrell Internet Draft [Page 21] The IPtX-MX Domain Name Service Specification January 27th, 2008 IPtX 32 / 64 Bit TCP Header 0 1 2 3 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 2 / 32 Bit Header Scale / / / 0 2 4 6 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2 4 / 64 Bit Header Scale / / / / IPtX 32 / 64 Bit Header Information Fields / / / | Source Port = 16 Bits | Destination Port = 16 Bits | / / |Source Port = 2E10.12 Bits | Destination Port = 2E10.12 Bits | / / |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | 2E10.12 Bits = Sequence Number = 2E24.30 Bits | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | 2E10.12 Bits = Acknowledgment Number = 2E24.30 Bits | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| |DataOffset 4Bit|Resrvd|ECN|Control Bits6|Window 48Bit HEX No.| |+ + + + +2 + + + + + + + + + + + + + + 3 + + + + 24 + + + + | |16 = Checksum = 2E10.12 Bits|16 = Urgent Pointer = 2E10.12Bit| |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | Options and padding | | 2E10.12 Bits Or 2E24.30 Bits | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | Data | | 2E10.12 Bits Or 2E24.30 Bits | |-------------------------------------------------------------| E Terrell Internet Draft [Page 22] The IPtX-MX Domain Name Service Specification January 27th, 2008 IPtX 32 / 64 Bit TCP Pseudo Header 0 1 2 3 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 2 / 32 Bit Header Scale / / / 0 2 4 6 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2 4 / 64 Bit Header Scale / / / | 2E10.12 Bits = Source IPtX address = 2E24.30 Bits | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | 2E10.12 Bits = Destination IPtX address = 2E10.12 Bits | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | 0 |Protocol = 8 / 16 Bits |Total length = 16 / 2E10.12 Bits | |-------------------------------------------------------------| UDP header for IPtX 0 1 2 3 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 2 / 32 Bit Header Scale / / / 0 2 4 6 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0 2 4 / 64 Bit Header Scale / / / / IPtX 32 / 64 Bit Header Information Fields / / / | Source Port = 16 Bits | Destination Port = 16 Bits | / / |Source Port = 2E10.12 Bits | Destination Port = 2E10.12 Bits | / / |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | 16 = Length = 2E10.12 Bits | 16 = Checksum = 2E10.12 Bits | |+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| | Data | | ::: | | 2E10.12 Bits Or 2E24.30 Bits | |-------------------------------------------------------------| E Terrell Internet Draft [Page 23] The IPtX-MX Domain Name Service Specification January 27th, 2008 Security Considerations - IANA Isolation and Privatization Options - There are many instances, not only for Businesses, Governments, and the Military, but ordinary Citizens also require a Secure Networking and Telephony Environment - However, while there are a number of methods employed today, which addresses these concerns, the IPtX Specification provides IANA with additional tools to make these environments even more secure - e.g.; I. IANA/Telephony* - IPtX / IPtX-MX DNS Tag "/TA" 'Depending upon whether or not the Telephony Address Pool is Shared by every IPtX Addressing Format' Provides every IPtX Addressing Format with Enhanced Isolation when using the IPtX / IPtX-MX DNS Tag "/TA" Specification II. ISP - "Backbone ID" Enhanced Security for 'All IPtX Addressing Formats' III. Users - "Backbone Account Number ID" - Enhanced Privatization Enhanced Security for 'All IPtX Addressing Formats' beyond the IPt1 Specification - an Address Bit-Mapped Length assigned by IANA, with respect to the IPtX Addressing Format being used. IV. Network - "Backbone Account Number ID" - Privatization Enhanced Security for 'All IPtX Addressing Formats' beyond the IPt1 Specification - an Address Bit-Mapped Length assigned by IANA, with respect to the IPtX Addressing Format being used, Isolates the 'Network' sharing a Common Backbone. V. IANA/EMERGENCY - "BROADCAST" - Isolation and Privatization Defined by / in the 'CIDR Network Descriptor Specification' VI. Options for the "IPtX-MX '0000:2E'0000.0000...' Address Band" If a 'Binary IP Addressing Protocol Specification' is unnecessary, then the more suitable application for the '0000:2E'0000.0000...' Address Band Specification defines a 'Routable Encrypted / Encryption Protocol, which can be used to Encrypt; the 'ISP Backbone ID', the 'Users Backbone Account Number ID', the 'Network Backbone Account Number ID', and the User's IPtX IP Address: 'The Isolation and Privatization' of any Netwrok sharing the 'Backbone Connections'. E Terrell Internet Draft [Page 24] The IPtX-MX Domain Name Service Specification January 27th, 2008 The 'IPt 16,777,216' "Intelligent Quantum Tunneling Worm Protocol" 536,870,912 Bit-Mapped Length = 0000:00E0000.0000... 2E8 = 8 Bit Prefix \ \ 2E402,653,166 = 402,653,166 Bit Exponent \ / \ 2E2 = 2 Bit Base / \ | / 0000 : 00 E 0000 . 0000... | \ 2E8 = 8 Bit Exponential Operator \ \ 2E134,217,728 = 134,217,728 Bit Exponential Decimal String E Terrell Internet Draft [Page 25] The IPtX-MX Domain Name Service Specification January 27th, 2008 Work(s) in Progress; Computer Science / Internet Technology: These drafts represent the twelve chapters of the Networking Bible, designing a Network IP Addressing Specification that maintains a 100 Percent backward compatibility with the IPv4 Specification. In other words, this is a design specification developed from the Theory of the Expansion of the IPv4 IP Addressing Specification, which allowed the representation of the Network for the entire World on paper, and the possibility of an Infinite IP Address Pool. Nevertheless, the Internet-Drafts listed below, 'Cited as Work(s) in Progress', explain the design Specification for the development of the IPtX (IP Telecommunications Specification) Protocol Addressing System and the correction of the Mathematical Error in the Binary System. 1. http://www.ietf.org/internet-drafts/draft-terrell-logic-analy- bin-ip-spec-ipv7-ipv8-10.txt - 'Work(s) in Progress' (Foundational Theory for the New IPtX family IP Addressing Specification, and the Binary Enumeration correction) 2. http://www.ietf.org/internet-drafts/draft-terrell-simple-proof- support-logic-analy-bin-02.txt - 'Work(s) in Progress' (The completion of the 2nd Proof correcting the error in Binary Enumeration) 3. http://www.ietf.org/internet-drafts/draft-terrell-visual-change -redefining-role-ipv6-01.pdf - 'Work(s) in Progress' (Argument against the deployment of IPv6) 4. http://www.ietf.org/internet-drafts/draft-terrell-schem-desgn- ipt1-ipt2-cmput-tel-numb-02.pdf - 'Work(s) in Progress' (The foundation of the New IPtX IP Addressing Spec now similar to the Telephone Numbering System) 5. http://www.ietf.org/internet-drafts/draft-terrell-internet- protocol-t1-t2-ad-sp-06.pdf - 'Work(s) in Progress' (The IPtX IP Addressing Specification Address Space/IP Address Allocation Table; establishes the visual perspective that actually represents Networking Schematic of the entire World.) 6. http://www.ietf.org/internet-drafts/draft-terrell-iptx-spec-def -cidr-ach-net-descrip-01.pdf - 'Work(s) in Progress' (Re-Defining 'CIDR' {Classless Inter-Domain Routing Architecture} for the IPtX Addressing Standard) E Terrell Internet Draft [Page 26] The IPtX-MX Domain Name Service Specification January 27th, 2008 7. http://www.ietf.org/internet-drafts/draft-terrell-math-quant -new-para-redefi-bin-math-04.pdf - 'Work(s) in Progress' (The completion of the 3rd Proof correcting the error in Binary Enumeration) 8. http://www.ietf.org/internet-drafts/draft-terrell-gwebs-vs-ieps -00.pdf (Global Wide Emergency Broadcast System) 'Work(s) in Progress' 9. http://www.ietf.org/internet-drafts/draft-terrell-iptx-dhcp-req -iptx-ip-add-spec-00.pdf - 'Work(s) in Progress' (The development of DHCP {Dynamic Host Configuration Protocol} for the IPTX IP Addressing Spec) 10. http://www.ietf.org/internet-drafts/draft-terrell-iptx-dns-req -iptx-ip-add-spec-03.pdf - 'Work(s) in Progress' (The development of DNS {Domain Naming Specification} for IPTX IP Addressing Spec) 11. http://www.ietf.org/internet-drafts/draft-terrell-math-quant -ternary-logic-of-binary-sys-09.pdf(Derived the Binary System from the proof of "Fermat's Last Theorem", and Developed the Ternary Logic for the Binary System) 'Work(s) in Progress' 12. http://www.ietf.org/internet-drafts/draft-terrell-cidr-net -descrpt-expands-iptx-add-spc-19.pdf 'Work(s) in Progress' (An application of Quantum Scale Theory, the 2^X : 1 Compression Ratio, the Expansion derived from the 'CIDR Network Descriptor, and the Mathematics of Quantification provided the foundation for the development of the "Intelligent Quantum Tunneling Worm Protocol"; A Routable Mathematical Exponential Expression, BackEnd IP Addressing Space using the Compression Ratio 2^X : 1.) 13. http://www.ietf.org/internet-drafts/draft-terrell-iptx-mx-dns- specification-03.pdf((The development of the IPtX / IPtX-MX DNS Specification Logic for the Binary System) - "Work(s) in Progress" NOTE: These Drafts has Expired at www.ietf.org Web Site. However, you can still find copies of these Manuscripts posted at Web Sites all over the World. Suggestion; Perform Internet Search using either 'Yahoo' or 'Google' - Keyword: 'ETT-R&D Publications'}. E Terrell Internet Draft [Page 27] The IPtX-MX Domain Name Service Specification January 27th, 2008 Normative References Pure Mathematics: 1. The Proof of Fermat's Last Theorem; The Revolution in Mathematical Thought {Nov 1979} E. Terrell 2. The Rudiments of Finite Algebra; The Results of Quantification {July 1983} E. Terrell 3. The Rudiments of Finite Geometry; The Results of Quantification {June 2003} E. Terrell 4. The Rudiments of Finite Trigonometry; The Results of Quantification {July 2004} E. Terrell 5. The Mathematics of Quantification and the Metamorphosis of Pi:Tau {October 200} E. Terrell 6. The Mathematics of Quantification & The Rudiments of Finite Physics The Analysis of Newton's Laws of Motion...the Graviton' {December 2004) E. Terrell 7. Squaring the Circle? First! What is the Circle's Area? {January 2005} The Rhind Papyrus Tale, and the 10,000 year old quest involving "Squaring the Circle"; derivation of the equation resolving the Area of the Circle. An illusion perplexing the Sight and Mind of the greatest mathematicians for about 10,000 years, which maintains an elementary algebraic solution: (Pi(r)/2)^2 = Area of Circle. E Terrell Internet Draft [Page 28] The IPtX-MX Domain Name Service Specification January 27th, 2008 Informative References 1. G Boole ( Dover publication, 1958 ) "An Investigation of The Laws of Thought" On which is founded The Mathematical Theories of Logic and Probabilities; and the Logic of Computer Mathematics. 2. R Carnap ( University of Chicago Press, 1947 / 1958 ) "Meaning and Necessity" A study in Semantics and Modal Logic. 3. R Carnap ( Dover Publications, 1958 ) " Introduction to Symbolic Logic and its Applications" 4. Regis Desmeules ( Cisco Press, April 24, 2003 ) " Cisco Self-Study: Implementing Cisco IPv6 Networks " 5. Gary C. Kessler ( Auerbach Press, August 1997 ) " Handbook on Local Area Networks " 6. R. Hinden (Nokia) and S. Deering (Cisco Systems) RFC 2373 - " IP Version 6 Addressing Architecture " 7. Hartley, R.V.L; "Transmission of Information," Bell System Technical Journal, July 1928 8. Reza, Fazlollah M.; An Introduction to Information Theory. New York: Dover, 1994. 9. David J. C. MacKay; Information Theory, Inference, and Learning Algorithms Cambridge: Cambridge University Press, 2003. 10. DNS Implementation and Security RFCs: 2535, 2931, 2135, 1035, 1996, 2845, 2930, 2671, 1183, 1706, 2163, 1712, 1886, 1876, 1002, 2052, 2782, 2168, 2915, 2538, 2230, 2671, 2672, 2874, 1995, 3123, 1996, 2182, 1101, 1123, 1279, 1296, 1383, 1401, 1464, 1480, 1535, 1536, 1591, 1611, 1612, 1713, 1794, 1876, 1886, 2163, 2168, 2219, 2230, 2308, 2517, 2538, 2539, 2541, 2606, 2845, 2870, 2915, 2929, 2930, 2931, 3007, 3008, 3090, 3110, 3027, 3071, 3130, 3123, 3152, 2537, 2137, and 2065. E Terrell Internet Draft [Page 29] The IPtX-MX Domain Name Service Specification January 27th, 2008 Author: Eugene Terrell Principle Director Research & Development Engineering Theoretical Technologies Research & Development Publications (ETT-R&D Publications) 3312 64th Avenue Place Oakland, CA. 94605 Voice: 510-636-9885 E-Mail: eterrell00@netzero.net "This work is Dedicated to my first and only child, 'Princess Yahnay', because she is the gift of Dreams, the true treasure of my reality, and the 'Princess of the Universe'. (E.T. 2007)" E Terrell Internet Draft [Page 30] The IPtX-MX Domain Name Service Specification January 27th, 2008 Copyright (C) The IETF Trust (2007). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST, AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Acknowledgement Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA). E Terrell Internet Draft [Page 31] The IPtX-MX Domain Name Service Specification January 27th, 2008