Network Working Group A. Ramos
Request for Comments: 2323 ISI
Category: Informational 1 April 1998
IETF Identification and Security Guidelines
1. Abstract
This RFC is meant to represent a guideline by which the IETF conferences may run more effeciently with regards to identification and security protocols, with specific attention paid to a particular sub-group within the IETF: "facial hairius extremis".
2. Introduction
It has come to the attention of THEY [1] that a certain "facial hairius extremesis" of the male variety of the species "homo sapien" of the sub-culture "computeris extrordinarisis" have overrun the IETF conferences and thus led to the break-down of many identification and safety protocols.
3. Per Capita (Anecdotal) Evidence
While collecting research about the sub-group "facial hairius extremis" (FHE), it was noted that the per capita appearance of FHEs at IETFs was largely disproportional with the existence of FHEs in the world-at-large. In fact, the existence of facial hair at all within the IETF community is extraordinarily common among the males of the group. Apart from ZZ-Top and WWF Wrestling, it is not possible to find more facial hair within any occupational group. In this author's own experience the average amount of men with long-term facial hair is less than 20%. Long-term versus short-term facial hair is a very important distinction as short-term facial hair, also known as the temporary illness "goatee universitis" (which symptoms range from full goatees to the less popular chin-goatee) is a common affliction for university-based males. Per capita (temporary) facial hair can go as high as 40%. However, among the males of the IETF the per capita long-term facial hair is as high as 60% [2].
Ramos Informational [Page 1]
RFC 2323 IETF Identification and Security Guidelines 1 April 1998
Ordinarily, this abundance of long-term FHE would not require that an RFC be written. However, increasingly there have been issues regarding mistaken identification. For security purposes as well as ease of identification, this RFC will serve to clarify these issues and hopefully provide a solution for them.
4. Mistaken Identification Syndrome (or "Are you --jon. or Scott?")
I was speaking to a very well-known network researcher, I'll call him --jon., who tells me that he is often mistaken for a SOBbing Harvard person. --jon. says, "People tell someone to look for me or him and say that I'm about so-tall with a big white beard, and suddenly people are coming up to me and saying, 'Hi Scott' and he often tells me that he is mistakenly hailed as, '--jon.'. Often the mistake is made solely on the appearance of our facial hair."
5. Security Considerations
It is obvious to this researcher that facial hair of any variety is a very recognizable characteristic. Indeed, when giving a description of a male who has facial hair, it is always one of the first characteristics given. Ordinarily this would not be a problem, since facial hair in the world at large is below 20%. However, when used as a description at IETFs, disaster can insue.
Ramos Informational [Page 2]
RFC 2323 IETF Identification and Security Guidelines 1 April 1998 6. SolutionsThere are two parts to my proposed solution: the role of the seeker and the role of the FHE.
7. Conclusion
In closing, I hope you found this RFC worthwhile and that it raised some interesting points. I also hope that I was able to further the cause of FHE and to make everyone's life a little bit easier. ;^)
8. References
[1] THEY
Ramos Informational [Page 3]
RFC 2323 IETF Identification and Security Guidelines 1 April 1998 9. AcknowledgementsI would like to thank the men of ISI who inspired me to write this RFC. I hope that my work will make life easier for you, and that the cases of mistaken identity will not be as common in the future because of this RFC. I understand your plight and feel for you. Good luck.
10. Author's Address
Alegre Ramos USC/ISI 4676 Admiralty Way #1001 Marina del Rey, CA 90292
Ramos Informational [Page 4]
RFC 2323 IETF Identification and Security Guidelines 1 April 1998 11. Full Copyright StatementCopyright (C) The Internet Society (1998). All Rights Reserved.