Dot-base62x: building a compact and user-friendly text representation scheme of ipv6 addresses for cloud computing
© Liu et al; licensee Springer. 2012
Received: 16 December 2011
Accepted: 15 February 2012
Published: 12 April 2012
Cloud computing has dramatically reshaped the whole IT industry in recent years. With the transition from IPv4 to IPv6, services running in Cloud computing will face problems associated with IPv6 addressing: the notation is too long (39 bytes), there are too many variants of a single IPv6 address and a potential conflict may exist with conventional http_URL notation caused by the use of the colon (:). This paper proposes a new scheme to represent an IPv6 address with a shorter, more compact notation (27 bytes), without variants or conflicts with http_URL. The proposal is known as dot-base62x as it is an IPv6 address with Base62x and uses the well-known period (or dot) as a group delimiter instead of the colon. The relative merits and demerits of other works that predate this paper have been reviewed and critically evaluated. Cloud computing, as a continuously emerging mainstream of network-based applications, is likely to be a forerunner in the use of IPv6 as the base protocol. As a result, Cloud computing will benefit most from the new, compact and user-friendly textual representation of IPv6 address proposed by this paper.
KeywordsIPv6 address Cloud computing Base62x Colon hexadecimal Text Encoding/Decoding
Cloud computing paradigm has emerged as an energy- efficient, fault-tolerant and on-demand approach which enables ubiquitous network accesses to a shared pool of flexibly reconfigurable computing resources. Networks, servers, storage, applications and services can be rapidly deployed with minimal management input or service provider interaction. It is also marketed as a fast, low cost method for small and medium-size business to setup an online presence.
Cloud computing relies on the infrastructure of Internet; as a consequence, it will be significantly affected by the transition from current IPv4 to next generation IPv6. It is notable that all cloud computing service modes, e.g. SaaS, PaaS and IaaS, are made possible with the underlying support of TCP/IP. Without a reliable, efficient networking infrastructure it is unlikely that cloud computing would be able to develop. It is anticipated that there will be a protracted period of change and that dual-stack IP networking will be utilised for a considerable time.
The demand for new IP addresses is continuously increasing and it is speculated that after the depletion of IPv4, there will be a very high number of address and/or ports translated networks, which will be highly inefficient and very likely to be inconsistently applied.
A secondary motivator for transition has previously been that IPv6 may provide significant technical advantages over IPv4. Cloud computing may be able to satisfy the increasing demands for real-time interaction, peer to peer services, secure communication and complex network management but it seems unlikely that IPv4 networks will be able to fully meet the necessary transport criteria. The advantages offered by IPv6 will become a necessity for cloud computing to develop as fully and as rapidly as possible.
In order to address the limitations of IPv4, the Internet Engineering Task Force (IETF) developed the IP version 6 (IPv6) suite of protocols and standards. When compared with IPv4, the advantages of IPv6 fall into two categories:
✓ Changes that address fundamental inadequacies of IPv4.
· Larger address space. Probably the most commonly known advantage of IPv6 over IPv4 is its enlarged address space. While IPv4 address is 32-bit long, IPv6 uses a 128-bit address, the four fold increase in length results in approximately 8×1028 more addresses being available and resolving the public address depletion issues.
· Depreciation of NAT. The address space provided by IPv6 removes the need to connect multiple machines to the Internet using a single address and network address translation (NAT). NAT is not included in the IPv6 suite. Without NAT, direct peer-to-peer communication is possible, allowing machines to connect to each other without intermediate “broker” services, like mail exchangers/relays, web proxies, DNS forwarders or SIP gatekeepers, which are run by a service provider.
· Stateless and Stateful Address Configuration. The large address space allows for a simplified address configuration mechanism, providing a service similar to the dynamic host configuration protocol (DHCP) but avoiding the need to maintain state information about address leases.
Other modifications in this group also include removal of broadcasting, enhancements to multicast and streamlined routing tables which together improve performance, manageability and flexibility.
✓ Advanced features introduced with IPv6. e.g.
· Network built-in security. The current standards bring a full implementation of IPv6 to include network layer encryption and authentication using IPsec as a mandatory function. Among other advantages of fully integrated network traffic encryption this provides the means to encrypt traffic even within a local network, thus providing protection from insiders trying to sniff network traffic.
· Mobile IPv6. The IPv6 standards include a feature called “Mobile IPv6”. This allows “roaming” while maintaining a “home” network address at all times, keeping all existing network connections open even while the underlying network connectivity changes.
· Improved Quality-of-Service (QoS). A new capability is added in IPv6 to enable the labelling of packets belonging to particular traffic flows for which the sender requests special handling. This is done through the “flow label” component in the IPv6 header. This feature is particularly pertinent in real-time services, such as in video-conferencing. Flow-label allows all packets in an IPv6 flow to packet to be routed in a consistent manner to reduce jitter and prevent packets arriving out of sequence.
Whilst we believe that IPv6 will begin a new and improved communications era for the whole IT industry, we also accept that IPv6 itself is not perfect.
First, it is obvious that with such a large address space (3.4 × 1038 or 340 undecillion addresses) a significant number of characters will be required to represent any single address. A full IPv6 address consists of 32 bytes or a string of 39 characters (including 7 delimiters) in human readable form which is both challenging to remember and prone to mistakes when read, written or deployed. A longer notation means more buffer space is needed when saving, there is an increased cost in bandwidth and latency time during transit, and more computing power is used when reading/writing, searching/parsing, etc.
can be presented in at least eight different forms by using all of the published and accepted compression and omission methods.
Third, the use of the colon (:) separator in place of the dot (.) presents both a potential ambiguity with current http_URL/Windows UNC and the annoyance of being a “two-key” entry on most. It is unpredictable that how many systems and applications will be affected by this incompatibility.
Bearing these issues in mind and considering the increasing demands of cloud computing, this paper introduces a novel scheme to present an IPv6 address in Base62x with period (or “dot”) delimiters as used in IPv4. A particular relevance to cloud computing is to provide a consistent and readily manageable approach as early as possible to prevent ambiguity and repeated effort at a future date, the alternative being to continue on with a less useable format. This scheme will overcome the highlighted issues and offer other benefits after its implementation. This is the key finding of the study.
The remaining sections of this paper are organized as follows. Section 2 is a literature review of other works that relate to the issues identified above. Section 3 gives a brief introduction to Base62x notation including its definition, algorithm and usage. Then in section 4 the new scheme, dot-base62x is presented and explained in detail with experiments and analysis. Section 5 re-iterates some of the benefits with dot-base62x notation. A conclusion of the proposal is given in section 6 and there are suggestions for future consideration in section 7.
It is accepted that this paper is not the first to make critical comment on current IPv6 text representation and raise issues as described in section 1. It is also a near certainty that this paper will not the last until those issues have been solved in a better and more acceptable way. In other works technicians and engineers have expressed their opinions about the current IPv6 notation with words like “pretty long” “a bit unwieldy”, “ugly”, “untidy”, “awkward” and “difficult to comprehend and work with”.
Since the current IPv6 address scheme was introduced by IETF RFC 1884 in 1995, some work has been done to address current IPv6 text representation issues related to excessive length, too many appearance/forms of representation and the potential ambiguity with existing http_URL/Windows UNC. Here are some representative examples to be discussed in detail as below.
Papers aiming to shorten IPv6 address notation
Elz’s informational RFC 1924
Base85 uses this character set to express any numerical value, including IPv6 addresses.
The encoded string is clearly much shorter than the original one, but this is the only clearly apparent benefit. Primarily, it is an order of magnitude harder to read, use and understand. It also necessitates the user to learn a whole new alphabet. Finally, 85 is not a “bit-boundary” number, base85 therefore does not fully utilize all of the required 7 bits and as a result will produce over-length and discontiguous binary strings.
Due partly to the unusual format of “base 85” to express IPv6 address, the suitability of RFC1924 has been debated many times. It does however show that a new direction for achieving a shorter notation for IPv6 address was recognized very early into its development and it explains the logic process of its author who was trying to cope with the issues born with RFC 1884.
To a lesser degree, the author had found it was necessary to make some changes to RFC 1884 before RFC1924 was published in 1996 and had carried on his thought to a complete scheme.
Translucent implementation in traditional base 64
Parwez proposed “another brave idea to present a translucent representation of currently implemented IPv6 address with a more compact and end-user friendly format for IT professionals especially for naïve users in networking environments.”
Simply it can be said that presenting IPv6 address in base 64, the transformation goes under rules:
" “The character set to encode the base64 IPv6 address is: 0–9, a to z, A to Z, . (dot) and—(hyphen); Case sensitive IP scheming; each character represents 6-bits; Last character has to be among 0–3; Maximum number of characters are 22 or more precisely 21.33 characters; …” "
Although these “addresses” are in a format that is unfamiliar, the reduced character set makes them appear far less daunting than the Base85 example given earlier.
The base64 scheme attempts to solve the address length issue by introducing more symbols in a similar manner to Base85 scheme. Both schemes shorten the address representation but in doing so they sacrifice readability and manageability.
It is difficult to suggest that this scheme would be readily accepted by academia or industry as it could introduce more complication than the original RFC 1884/4291.
A recommendation for unifying all different variants
As noted in the first section of this paper, with at least eight formats there are too many legitimate ways to represent the same single IPv6 address in current colon hexadecimal notation. Since IPv6 addresses are not just used in IP header as binary mode numbers, the high number of variants is likely to cause unpredictable problems when handling literal IPv6 addresses as necessary in different computer systems and applications.
To avoid this confusion, Kawamura proposed IETF RFC 5952 to achieve the goal that any single IPv6 address should have only one textual representation. The suggestions for unifying all variants include methods for handling leading zeros in a 16-Bit field, use of “::” and lowercase. This is a positive attempt to avoid confusion by removing the misleading and mismatching among many similar forms of a single IPv6 address.
Since many possible methods had been provided, confusion could arise due to individual systems, applications and manufacturers adopting the method which they favoured most for their own purposes. The RFC proposes to avoid this situation by permitting only one shortened IPv6 address format. Addresses represented in any other way are not legitimate and therefore not permitted.
Proposals to resolve colon-related conflicts
Extra square brackets in domain part of http_URL
IETF RFC 2732, “Format for Literal IPv6 Addresses in URL’s” was created to address the colon-related issue. RFC 2732 narrates the situation where why this is necessary and how to handle it with one more pair of square brackets.
"“ The textual representation defined for literal IPv6 addresses in [ARCH] is not directly compatible with URL’s. Both use “:” and “.” characters as delimiters. This document defines the format for literal IPv6 Addresses in URL’s for implementation in World Wide Web browsers. The goal is to have a format that allows easy “cut” and “paste” operations with a minimum of editing of the literal address.” "
This proposal introduces further characters into IPv6 URLs in the form of square bracket to distinguish between the different meanings of the colon character. Examples of URLs which employ this format are
Microsoft changes to overcome unc violation
As proposed, this method involves more cost and greater complexity, which means it is not the best choice.
It is anticipated that colon-related issues in IPv6 address notation will not be limited to only the http_URL and Windows UNC examples that are presented here.
There is a very clear requirement to resolve all of these problems preferably in a single method and without introducing further compound confusion.
On-going studies on these issues
Cloud computing will generate a requirement for even more address space, much of which will be IPv6 by choice to take advantage of the technical improvements or out of simple necessity because IPv4 are not available. Presently only approximately 0.2% of Internet addresses are IPv6-based. Although this is a significant number in real terms, it is still considered feasible to modify the IPv6 address notation prior to mass migration. VeriSign observed a fourfold increase in IPv6 traffic over its infrastructure in 2010, this level of change suggests the urgency for Internet community to accept an alternative to the benefit of the whole IT industry.
In IETF RFC 4648, its authors summarized that base encoding “is used in many situations to store or transfer data in environments that, perhaps for legacy reasons are restricted to US-ASCII (Cerf, 1969) data. Base encoding can also be used in new applications that do not have legacy restrictions, simply because it makes it possible to manipulate objects with text editors”.
Many base encoding schemes have been invented over time for a multitude of different purposes. Within these schemes discrepancies are occasionally noted as the scheme is applied to an increased level of use and scrutiny. As a result, RFC 4648 states “The purpose of this specification is to establish common alphabet and encoding considerations. This will hopefully reduce ambiguity in other documents, leading to better interoperability”.
Base62x is a piece of work in the field of base encoding which strives to overcome some issues with conventional base 64 system.
As discussed in RFC 4648, traditional base 64 needs three more symbols (“+”, “/”, “=”) to organize its algorithm and representation. As noted by the RFC, this could be problematic in some scenarios:
Encoded into structures that mandate other requirements. For base 16 and base 32, this determines the use of upper- or lowercase alphabets. For base 64, the non-alphanumeric characters (in particular, “/”) may be problematic in file names and URLs.
Used as identifiers. Certain characters, notably “+” and “/” in the base 64 alphabet, are treated as word-breaks by legacy text search/index tools.
There are nine other groups of variants substituted into traditional base 64 as an attempt to resolve the problems introduced by these otherwise controversial symbols.
Base62x was first described in a paper where it is proposed as an alternative approach to Base64 for non-alphanumeric characters and is intended to be an improved implementation of Base64. It does not use any symbols in its representation, only case sensitive alphabetical (a-z, A-Z) and numeric characters (0–9).
Codes index comparisons
Examples of Base62x
Encoded text in Base62x
Since there is no symbol used in Base62x index table, it shortens the length of IPv6 address without adversely affecting readability, one of the important requirements of the proposed IPv6 address notation.
Dot-base62x notation of ipv6 address
Knuth’s book shows that as b is incremented the number notation will be shorter and compact, and at the same time, the set of a will get larger.
It is also obvious that a large base number should be used if a shorter is desired. This answers the question why the papers discussed in previous sections employed base 85 or base 64 to shorten the representation of IPv6 addresses. For an IP address, base 16 is the closest option next to base 10, afterwards there are base 32, base 64 and base 85 in Elz’s informal RFC paper.
where each “y” stands for one byte (8 bits or two characters). After encoding into Base62x, “yyy” (3 bytes, 24bits or six hex characters) will be replaced by “xxxx” (four base62x 6-bit characters) and “yy” (2 bytes, 16 bits or four hex characters) will be replaced by “xxx” (three base62x 6-bit characters) in Base62x.
where each “x” represents any one six-bit character (using the code scheme 0–9, a-z, A-Z, x1-3). As before, the first half of the address indicates the subnet prefix and the second half indicates the interface ID. The first 3-digit group indicates the subnet ID.
The proposed scheme is known as dot-base62x notation of IPv6 address and has the following features:
○ Encoded in Base62x
○ Dot-separated six segments
○ Prototype length: 22 codes + 5 dots = 27 characters
○ Character range: 0–9, A-Z, a-z
Conversions to/from dot-base62x
The process of converting an IPv6 address into dot-base62x can be summarized as these steps:
➢ S1. Divide the given 16-byte address into 6 segments as 3:3:2:3:3:2
➢ S2. Convert each segment into Base62x
➢ S3. Separate the Base62x encoded string into 4:4:3:4:4:3 as xxxx.xxxx.xxx.xxxx.xxxx.xxx
Two more IPv6 addresses conversions have been demonstrated using dot-base62x as below.
A batch conversion experiment was undertaken to observe the format of the dot-base62x notation in a real world simulation. The minimum and maximum length of each group was recorded and compared after converting different groups of randomly generated IPv6 addresses. The size of the test groups were as 102, 103, 104 and 105 IPv6 addresses.
In each set of the sample IPv6 addresses, the program converts each address into its corresponding dot-base62x format and records the length and the time taken to convert. On completion of a set, the maximum and minimum values are displayed and the average value calculated for the set. The experiment was repeated with three groups of random addresses for each set size to avoid anomalous or ambiguous results.
From Figure 8 it is clear that no major difference is observed across the sample ranges. The maximum lengths vary across a small range whilst the average and minimum lengths show practically zero deviation.
It is therefore predictable and conclusive that the average length will not increase with address samples ranging from 102, 105, 108, 1020 to the largest set of current IPv6 addresses, 2^128, i.e. 3.4 × 1038.
Comparisons between dot-base62x and colon hexadecimal notation of IPv6 address
Comparisons of dot-base62x and colon hexadecimal
Dot, full stop (.)
Number of separators
Format address length
Each 4 bits
Each 6 bits
Advantages and benefits of dot-base62x
The whole Internet community and especially Cloud computing, which will have a major reliance on IPv6, will benefit from the proposed scheme in the following aspects of IP-related systems and applications.
It is clear from Figure 9 that dot-base62x has a theoretical length reduction of approximately 30% (orig. column) and approximately 24% in real use (avg. column). In practice, only the average values are significant; the minimum and maximum lengths are largely irrelevant due to the low probability of these extremes in real network environments.
IP addresses do not exist exclusively in the headers of IP packets but are also widely used in many network-based systems and applications. Any decrease in length can translate to saving space on disk, reduced bandwidth in transit and reduced cost of operation. As discussed in RFC 5952, there are many scenarios that utilise the IP address in a literal rather than binary mode. Some of these scenarios could include:
· Searching Spread sheets and Text Files
· Searching with WHOIS
· Searching for an Address in a Network Diagram
○ Parsing and Modifying,
· Unexpected Modifying
○ Other Minor Problems.
All of these operations would benefit from reduced disk space and transit time as a consequence of the shortened IP address notation in dot-base62x format. RFC 5952 also discusses the further problem with colon hexadecimal notation in that different variants of presentation can lead to confusion.
Compact form, less segments, more human-friendly
The proposed scheme has a more compact form than current colon-hexadecimal notation.
Firstly, instead of the eight groups of characters in colon-hexadecimal, there are only six in dot-base62x. This simpler representation makes the scheme more human-friendly.
The first half of the address is the globally unique network ID, the second half is interface ID,
The first “yxx” stands for “subnet ID” for organization in unicast address.
Thirdly, an IPv4 address uses 4 character groups, using the dot-62x scheme an IPv6 address has 6 groups which is a more symmetric and aesthetically pleasing form.
Last but not least, the continuous two-key entry requirement of the colon symbol will very quickly lead to many years of tedium and non-standard keyboard mapping that is resolved by returning to the single keystroke period (or dot) separator.
Compatible with IPv4 dot-decimal
It is clear obvious that keeping the identical separator in both versions of IP will maintain consistency in the whole Internet community. People working within the field of networks are already familiar with dot-separated style IP address and will find in more acceptable for the transition from IPv4 to IPv6 if the proposed scheme became widely adopted.
Similar problems with colon-separated notation can be solved by dot-base62x format. A greater degree of compatibility is maintained. This in turn means more existing IPv4 systems and applications can be made to be seamlessly compatible with IPv6 addresses in dot-base62x.
Minimized the number of variants
RFC 5952 recommends a unified representation to avoid confusion caused by multiple output forms of colon hexadecimal notation from a single IPv6 address.
The root cause of this problem is that colon hexadecimal simply provides too many methods to represent a single IP address, e.g. case-sensitive or case-insensitive, positions of double colon, whether or when or where compressing leading zeros.
Dot-base62x notation avoids this issue by introducing only one method to compress a given single IPv6 address, the identical method which has been used with IPv4. The method is the natural and intuitive human response of simply suppressing all leading zeros. Therefore, any single IPv6 in dot-basex62 has one and only one textual representation in the same way that an IPv4 is only written in one form.
Confusion in the scenarios listed in the previous section, e.g. searching, logging, parsing and operating, where IPv6 addresses may be used as a textual identifier will be avoided if those IP addresses are encoded in dot-base62x due to the unique format of any single IPv6 address.
Avoiding conflict with exist http_URL/Windows UNC
Clearly, with the exception of IPv4 itself, there was no intention for IPv6 address notation to conflict with other existing RFC standards. However, the colon symbol serves as a “port” identifier part in current http_URL scheme, which could lead to confusion between a colon hexadecimal address and http_URL.
The current remedy for this conflict introduces further complication by enclosing the IPv6 address in a pair of square brackets before using it as an IP address in http_URL, e.g., http://[2001:db8:0000:0:1::1]:8080/file/to/path?query. Dot-base62x has no such problem, by abandoning colon in its output form and instead using the “dot” as in IPv4, a greater degree of compatibility is maintained. This in turn means more existing IPv4 systems and applications can be made to be seamlessly compatible with IPv6 addresses in dot-base62x.
The same problem arises with Windows UNC due to the transition from the dot-separated format to the colon-separated format. Dot-base62x will avoid this conflict. These examples can be handled as easily as with IPv4 addresses.
This research has introduced a compact, user-friendly textual representation of IPv6 addresses.
The Internet has revolutionized human history in recent decades and it will continue to contribute to and reshape the world for many years to come. Cloud computing as the mainstream services of future IT applications will encounter many scenarios where IP addresses are used in plain text representation rather than binary mode. This study reviews the development of current Internet addressing with a primary focus on potential IP evolution.
Literature reviews show that current colon hexadecimal notation of IPv6 address has the following issues when being deployed in cloud computing.
✘ Too long. Usually it has 39 characters, sometimes up to 45 characters.
✘ Too many variants. A single IPv6 can have several variations in appearance which can cause confusion.
✘ Colon (:) conflicts with http_URL/Windows UNC.
✘ Incompatible with IPv4.
A new scheme, named as dot-base62x, has been proposed by this study as a means to encode IPv6 addresses in Base62x and separate the encoded string with five dots. The proposed dot-base62x has the following advantages and benefits compared with current colon hexadecimal notation.
✓ Shorter notation. An IPv6 address length reduction of 30% or so in theory and 24% or so in practice are achieved.
✓ Compact shape, less segments, more human-friendly. Instead of eight segments/groups in its output form, dot-base62x only has six segments. Among these six segments, there are two segments with only three digits, providing an even more compact format than the fixed 4-digit with colon hexadecimal.
✓ Compatible with IPv4 dot-decimal. More existing IPv4 systems and applications can be made to be seamlessly compatible with IPv6 addresses in dot-base62x.
✓ Minimized the number of variants. Dot-base62x notation uses one and only one method to compress a given single IPv6 address, the natural human method which has been used with IPv4.
✓ Avoiding conflict with exist http_URL. Dot delimiting is used in dot-base62x. The colon (:) is not used due to conflicts with http_URL which uses the colon to identify a port. This also resolves the colon conflict problem with Microsoft Windows UNC.
From this paper we have reasonably concluded that current colon hexadecimal notation of IPv6 address is not the best or most suitable choice. We are confident that the proposed dot-base62x representation is a more suitable format and recommended its adoption for an IPv6 address in the coming IT era of Cloud computing.
Recommendations and future work
With vigorously-developed cloud computing in recent years, more and more services and devices will become cloud based. Every service and device will need at least one IP address. As a consequence, IPv6 is unlikely to be the final addressing scheme used on the Internet. For this proposed scheme itself, there are a few options, recommendations and further works to be done.
Fixed-width or various length of IPv6 in Base62x
Due to three double-digital characters being added in its index table, the length of strings encoded in dot-base62x may vary in a small range without any other compressing involved. This may be a major concern with dot-base62x when compared with colon hexadecimal.
Taking compressing and better compatibility into consideration, we recommend that keeping its varying length is a better choice from a long term and developmental point of view. As varying lengths are unavoidable in all schemes discussed, it is not considered significant that the length may extend 27 bytes in common use to 47 bytes in very rare extremes.
In this dot-base62x IPv6 address, it is hard to tell whether it is “1” (one) or “l” (letter L) in the 2nd segment “Rzn?”. The same confusion arises from the 5th segment “?NNR”. In this font style (Times New Roman), letter “l” is slightly thin and higher than number “1”, thus it is letter “l” in segment 2, and number “1” in segment 5.
Fortunately, “z” and “2” has no such misreading problem in such scenario and it is distinguishable that it is letter “z” in segment 2, number “2” in segment 6. But “z” and “2” may be confused with high likelihood when handwritten.
Though such study goes beyond this report, it is necessary to advise a set of hints to write or display these illegible characters if some practical methods have been found in future work addressing this interpretation issue.
Integration of IPv4 addressing
Next generation: IPv8 or IPv10
Along with dot-base62x this upgrading task becomes easier and more acceptable. We will actively anticipate the standards of IP address scheme after IPv6.
The work reported in this paper has been supported by the RLTF HECloud Programme (Ref: RLTFD005), the Visiting Scholar Foundation of Key Laboratory of Dependable Service Computing in Cyber Physical Society of the Ministry of Education China (CPS-DSC 2012FWJJ01). Major Program of the National Natural Science Foundation of China, under contact No. 90818028 and China 973 Fundamental R&D Program (No. 2011CB302600).
- Liu Z, Lallie HS, Liu L: “A Hash-based Secure Interface on Plain Connection”, Proceedings of CHINACOM’11. ICST.OTG & IEEE Press, Harbin, China; 2011.Google Scholar
- Davies J: Understanding IPv6. Second edition. Microsoft Press; 2008:43–45. 50, 92 50, 92Google Scholar
- Huston G: IPv4 Address Report, daily generated. Retrieved in August 2011. , 2011 http://www.potaroo.net/tools/ipv4/index.html , 2011Google Scholar
- Stockebrand B: IPv6 in Practice—A Unixer’s Guide to the Next Generation Internet. Springer, Berlin Heidelberg; 2007. ISBN 3–540–24524–3, 978–3-540–24524–7 ISBN 3-540-24524-3, 978-3-540-24524-7Google Scholar
- Hinden R, Deering S: IP Version 6 Addressing Architecture, IETF RFC 4291, 2005. retrieved in August 2011. http://www.rfc.net/rfc4291.htmlGoogle Scholar
- Kawamura S, Kawashima M: A Recommendation for IPv6 Address Text Representation, IETF RFC. retrieved in August 2011. http://tools.ietf.org/html/rfc5952Google Scholar
- Kozierok CM: The TCP/IP guide: a comprehensive, illustrated Internet protocols reference. No Starch Press; 7. 379 379Google Scholar
- Hinden R, Deering S: IP Version 6 Addressing Architecture, IETF RFC 1884, 1995. retrieved in August 2011. http://tools.ietf.org/html/rfc1884Google Scholar
- Elz R: “A Compact Representation of IPv6 Addresses”, IETF RFC 1924, 1996. retrieved in August 2011. http://tools.ietf.org/html/rfc1924Google Scholar
- Parwez R, Haq E: Translucent implementation of ipv6 addressing scheme in communication networks. International Journal for Infonomics (IJI) 2010,3(3):338–344.Google Scholar
- Hinden: Format for Literal IPv6 Addresses in URL's. IETF RFC 2732, 1999. retrieved in September 2011. http://www.ietf.org/rfc/rfc2732.txtGoogle Scholar
- Google: Google Trends. retrieved in August 2011. http://www.google.com/trends?q=ipv6+address&ctab=0&geo=all&date=allGoogle Scholar
- Leavitt N: IPv6: Any Closer to Adoption? Computer, IEEE Computer Society 2011,44(Number 9):15. ISSN 0018–9162 ISSN 0018–9162Google Scholar
- Josefsson S, The Base16, Base32, and Base64 Data Encodings: IETF RFC 4648, 2006. retrieved in August 2011. http://tools.ietf.org/html/rfc4648Google Scholar
- Wikipedia: Base64, 2011. retrieved in November 2011. http://en.wikipedia.org/wiki/Base64Google Scholar
- Liu Z, Liu L: Base62x: An Alternative Approach to Base64 for non-Alphanumeric Characters, Proceedings of ICNC & FSKD. IEEE Computer Society Press, Shanghai, China; 2011.Google Scholar
- Knuth DE: The Art of Computer Programming Volume 2: Seminumerical Algorithms, Third Edition. Reading. Addison-Wesley, Massachusetts; 1997:195. ISBN 0–201–89684–2 ISBN 0-201-89684-2Google Scholar
This article is published under license to BioMed Central Ltd. This is an Open Access article distributed under the terms of the Creative Commons Attribution License (http://creativecommons.org/licenses/by/2.0), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.