There is a working group on this as well with the following:
We have the following IETF Draft: http://tools.ietf.org/html/draft-denog-v6ops-addresspartnaming-02 Which gives us: 4. Naming Proposals We are presenting a broadest selection of mostly serious proposals which needs to be narrowed in the future by straw polls and finally select one using normal IETF consensus. 4.1. Chazwazza "Chazwazza" was proposed as a Simpsons reference, see [greg <http://tools.ietf.org/html/draft-denog-v6ops-addresspartnaming-02#ref-greg>]. While this is certainly a unique term in the networking world, it is not particularly meaningful nor easy to pronounce. 4.2. Chunk A chunk is commonly understood to be a specific amount of data. The term is not unique to IPv6, however easy to remember and pronounce. 4.3. Column The colons in an IPv6 address' text representation make it similar to a table. Besides that, the meaning of the word "column" has very lit- tle to do with the actual technical meaning of a 16bit piece of an IPv6 address, though. 4.4. Colonade, Colonnade Based on the colon as seperator the word sounds English (using a sin- gle 'n' to make it an artificial word) and is easy to spell and pro- nounce. Alternatively, "colonnade" could be used, overloading the existing, yet unrelated word with a new meaning. 4.5. Doctet Derived from "double octet", thus accurately describes the technical matter, as an octet is a standard term for a sequence of 8 bits. 4.6. Field A "field" describes a form of a data structure in many programming languages. The term stresses the fact that a field is one of multiple fractions of a bigger subject, just like countryside is divided into fields, or like IPv6 addresses into 16bit long pieces. A drawback of that similarity is the lack of uniqueness to IPv6, though. 4.7. Hexadectet "Hexadectet" is directly derived from IPv4's "octet", thus techni- cally correct and probably convenient to get used to. On the other hand, it is much harder to pronounce. 4.8. Hit Short for "hex-bit", short and convenient to pronounce, however usu- ally associated with a completely different meaning. 4.9. Orone Initially started as a typo in [greg <http://tools.ietf.org/html/draft-denog-v6ops-addresspartnaming-02#ref-greg>], "orone" is a short, unique word without a specific meaning yet. 4.10. Part The word "part" has been used throughout this document to describe the subject until there is a better term for this. It is very unspe- cific and can be used in countless ways, not only to describe 16bit long parts of an IPv6 address. 4.11. Provider number, customer number, network number These terms provide semantic descriptions of the different parts of an IPv6 address. However, it is not within the scope of this document to find terms describing semantic, but rather syntactic elements. Furthermore, naming the 16bit pieces of IPv6 addresses in a semantic way would introduce new problems, like limited applicability, e.g. it would not work for multicast addresses. 4.12. Quad nibble, qibble, quibble A nibble is a 4bit entity, hence 16 bits are a quad nibble. This is a rather bulky word, however, so "quibble" is a convenient abbrevia- tion. Also, it is a unique term, thus eliminating any chances of mis- interpretation. 4.13. Segment "Segment" is another obvious choice, however it is also quite unspe- cific and used in different contexts, e.g. "network segments". 4.14. Tuple A tuple is a sequence of typically heterogenous elements considered as a new entity by itself. It is also a short, descriptive word that is not yet associated with anything networking related. Usually a tuple exceeds grouping by creating a new semantic level. 4.15. Word A "word" usually refers to a fixed group of bits that are processed at a time, and especially on legacy x86 systems is a synonym for 16 bits. It has a different and much more unspecific meaning to less technically skilled people, which might be problematic. On 2010-10-28 2:49 PM, Brandon S Allbery KF8NH wrote: > On 10/28/10 14:34 , Dan Foster wrote: > > Well, I can't find a clear authoritative cite from a quick look but the > > wording of RFC2460 suggests '2-octet', '2 octet'? > > > > http://ipv6.net/RFC/rfc-2460-internet-protocol-version-6-ipv6-specification.html > > > Open to alternate suggestions, of course. > > The only one I've seen in anything resembling common usage is "group"; it > doesn't really need to be specified in more detail since it's mostly a > convenience syntax to make the address slightly more readable instead of a > quasi-fundamental aspect of the address (in IPv4 it's essentially a > leftover > from "classful" routing). > _______________________________________________ Tech mailing list [email protected] http://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
_______________________________________________ Tech mailing list [email protected] http://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
