I've been working on a protocol in which everything is addressed to a public key. I'm going to make an initial encapsulation of this protocol in email, but it should be able to be encapsulated in a wide variety of transports.
I would like a name for it. It would be nice if it were a pronounceable acronym, and an acronym that isn't in widespread usage for something else. It could be 3-4 letters, though particularly good longer acronyms would be fine. I'd like the acronym to mention cryptography and network in some way.
CAPE= Crypto Addressing Protocol Encapsulation
CANE= Crypto Addressing Network Encapsulation
If you want to help, but aren't sure what acronyms are already taken, this site: http://www.acronymfinder.com/ is a good one. In fact, that site is excellent if you're just curious about the meaning of a particular acronym. After you find the meaning, you can do a google search on it and find out all kinds of interesting things, whereas a google search on the plain acronym may not give you good results.
Good proposals so far:
NICE= Network Identity Cypto Encapsulation
SECURE= Spam Elimination Crypto User Renown Encapsulation
CANOE= Crypto Authorized Network Obfuscation Encapsulation
KAM= Key Addressed Messaging (doesn't mention cryptography enough though)
KAEM= Key Addressed Encrypted Messages
I feel the ones that start with 'K' though are somehow lacking, even though I really like making the main feature of the protocol (addressing messages to public keys) part of the name.
Chad Walstrom had some interesting things to say:
Key words to consider: crypto, network, key, public, authentification, secure, alice, bob, charlie, envelope, frame, packet, handshake, notary.
Another thing to consider is to step away from acronyms. Software doesn't necessarily have to be named after a constructed acronym.
Perhaps an animal or process.
babushka(the Russian dolls that fit within dolls)
piccilo(PublIC key EnveLOpe)
crane(CRyptic Network Frames, nice play against SWaN)
notary(In reference to a "public notary", an authticated, authentificated protocol).
Chad's ideas gave me another idea, which is:
cronies(CRyptO Network Identification Encapsulation System)
I like this idea because it evokes the notion of a group of close friends. Since the protocol includes no requirement for a certificate authority type entitiy, I imagine that close social networks will become important for the protocol's ultimate security.
What I really want to do is bootstrap on people's current methods of choosing to trust one another. Humans have evolved very complex social structures for deciding just these things, and I would like to make a protocol that allowed these existing mechanisms to extend over communications networks. I think a good way to do that is to make it easy to identify people you've already talked to.
Of course, the implication of 'cronies' is a social network that has negative consequences for society as a whole. But, I don't think that association is strong enough to cause people to reject it based on that name.
Another idea is 'anthill'. Ants use a public/private key like system for identifying each other. The public keys are the specific chemicals they exude to mark trails or give them a distinctive taste or smell. The private key is the factories in each of their bodies used to create those chemicals. This system is what causes anthills to be distinct from one another.
Now it has a homepage: http://www.cakem.net/