As per Relevance of the word identification, we have this rfc below:











Network Working Group A.
Request for Comments: 2323
Category: Informational 1 April 1998


IETF Identification and Security

Status of this

This memo provides information for the Internet community. It
not specify an Internet standard of any kind. Distribution of
memo is unlimited

Copyright

Copyright (C) The Internet Society (1998). All Rights Reserved

1.

This RFC is meant to represent a guideline by which the
conferences may run more effeciently with regards to
and security protocols, with specific attention paid to a
sub-group within the IETF: "facial hairius extremis".

This document will shed further illumination on these problems
provide some possible solutions

This memo provides entertainment for the Internet community. It
not specify an Internet standard of any kind, but is
unstandard, actually. Please laugh loud and hard

2.

It has come to the attention of THEY [1] that a certain "
hairius extremesis" of the male variety of the species "homo sapien
of the sub-culture "computeris extrordinarisis" have overrun the
conferences and thus led to the break-down of many identification
safety protocols

3. Per Capita (Anecdotal)

While collecting research about the sub-group "facial
extremis" (FHE), it was noted that the per capita appearance of
at IETFs was largely disproportional with the existence of FHEs
the world-at-large. In fact, the existence of facial hair at
within the IETF community is extraordinarily common among the
of the group. Apart from ZZ-Top and WWF Wrestling, it is
possible to find more facial hair within any occupational group.



Ramos Informational [Page 1]

RFC 2323 IETF Identification and Security Guidelines 1 April 1998


this author's own experience the average amount of men with long-
facial hair is less than 20%. Long-term versus short-term
hair is a very important distinction as short-term facial hair,
known as the temporary illness "goatee universitis" (which
range from full goatees to the less popular chin-goatee) is a
affliction for university-based males. Per capita (temporary)
hair can go as high as 40%. However, among the males of the IETF
per capita long-term facial hair is as high as 60% [2].

Ordinarily, this abundance of long-term FHE would not require that
RFC be written. However, increasingly there have been
regarding mistaken identification. For security purposes as well
ease of identification, this RFC will serve to clarify these
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
--jon., who tells me that he is often mistaken for a SOBbing
person. --jon. says, "People tell someone to look for me or him
say that I'm about so-tall with a big white beard, and
people are coming up to me and saying, 'Hi Scott' and he often
me that he is mistakenly hailed as, '--jon.'. Often the mistake
made solely on the appearance of our facial hair."

Another story --jon. told me is that once a woman called looking
a computer researcher but only having a first name and
description. The receiptionist asked for the description and
woman said she was looking for an older Caucasian man with a beard
The receptionist reportedly blurted out, "they all have beards!!!!"

On a more personal note, two researchers who were both employed
USC/ISI shaved their very famous facial hair and were
unrecognizable to friends and co-workers alike. If it weren't
B.M.'s Grateful Dead T-shirts and lack of shoes, or R.V.M.'s voice
would have never recognized them

5. Security

It is obvious to this researcher that facial hair of any variety is
very recognizable characteristic. Indeed, when giving a
of a male who has facial hair, it is always one of the
characteristics given. Ordinarily this would not be a problem,
facial hair in the world at large is below 20%. However, when
as a description at IETFs, disaster can insue






Ramos Informational [Page 2]

RFC 2323 IETF Identification and Security Guidelines 1 April 1998


6.

There are two parts to my proposed solution: the role of the
and the role of the FHE

For those who are seeking a FHE of known identity

-It is important to recognize these men as individuals

Just because a man has the facial hair you are looking for
please stop to inquire if you have the correct person.
of what a blow it is to a person's ego to be
misidentified, and think of how annoying it is to be hailed
someone across a crowded IETF room and they are yelling
WRONG NAME. So remember to look, identify, and ask BEFORE
begin rambling on about some Internet stuff

For the FHE

-Give proper signals when being sought

If someone mistakenly calls you the wrong name, do not
heart. Count to 10 and commonly reply, "You must have
me for so-and-so, I am not that person.", and walk away. Also
if someone calls you from across a room, raise your your arm
smile and wave vigorously in affirmation or raise your arm
shake your head and give them a sign that you are not who
are looking for. As an FHE it is part of your
to understand that facial hair is an extremely
physical characteristic. Understand that non-FHE people do
mean any harm

7.

In closing, I hope you found this RFC worthwhile and that it
some interesting points. I also hope that I was able to further
cause of FHE and to make everyone's life a little bit easier. ;^)

8.

[1]
THEY, "We Who Everyone Quotes But Doesn't Know Who We Are",
Culture, April 1998.

[2] 60% of IETF men have facial
A. Ramos, "Damn, A Lot Of Men Here Have Facial Hair", ISI Talk
September 1997.




Ramos Informational [Page 3]

RFC 2323 IETF Identification and Security Guidelines 1 April 1998


9.

I would like to thank the men of ISI who inspired me to write
RFC. I hope that my work will make life easier for you, and that
cases of mistaken identity will not be as common in the
because of this RFC. I understand your plight and feel for you
Good luck

Thanks to my life partner, Martin, who's reoccuring affliction
goatee universitis is a constant source of joy for me

10. Author's

Alegre
USC/
4676 Admiralty Way #1001
Marina del Rey, CA 90292

Phone: 310-822-1511 x153
EMail: ramos@isi.































Ramos Informational [Page 4]

RFC 2323 IETF Identification and Security Guidelines 1 April 1998


11. Full Copyright

Copyright (C) The Internet Society (1998). All Rights Reserved

This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English

The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns

This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
























Ramos Informational [Page 5]








if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.




RFC documents can be found at I.E.T.F.



Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX







Spectrum