Protocol Watch Thread

An evergreen thread for posting interesting news about protocols from the real world. Post links with short notes.


“ Then, during a particular rebuttal in the middle of the regional round—which took place by videoconference, the Midlands team gathered in front of a webcam in that same colorless faculty boardroom—Katsande realized something: They were winning. Representing Xenovia, Katsande argued that her client had the authority to repossess Candidia’s satellite without consulting its owners, citing an obscure piece of space law that says an object can be repossessed by a creditor without the need to seek consent. (It’s true: Just check the Protocol to the Convention on International Interests in Mobile Equipment on Matters Specific to Space Assets.)”

“Since SPTP can offer the exact same level of synchronization with a lot fewer resources consumed, we think it’s a reasonable alternative to the existing unicast PTP profiles.”

"Having it standardized and assigned a unicast profile identifier will encourage wider support, adoption, and popularization of PTP as a default precise time synchronization protocol.

The source code for the SPTP client and the server can be accessed on our GitHub page."

protocol adjacent: stonelifting etiquette

Stonelifting’s etiquette is akin to both gym etiquette and mountaineering etiquette. It’s about responsibility and respect for the stones and the land they sit on. You must be aware of it and understand it before attempting to lift any historic stones.
Stonelifting Etiquette —

bonus: some wonderful stone photos

:rock: :scissors: :page_facing_up: protocol

Didn’t realize “lightweight” was a semi-formal prefix in protocol naming and design style. As in LDAP.

Light vs heavy protocol is a dimension we didn’t talk about.

Extend to stripped-down/barebones too?

1 Like

“The protocol, per Apple, is also designed to mitigate the impact of key compromises by limiting how many past and future messages can be decrypted with a single compromised key. Specifically, its key rotation scheme guarantees that the keys are rotated every 50 messages at most and at least once every seven days.”

This is a nice protocol

In the wake of the recent bridge collapse in Baltimore, one positive note: the protocols that enabled rapid response worked remarkably well and probably saved many lives. I’m not sure if you even want to call them protocols, given that this is such a one-off event, but the people who work in public safety, transportation, and government somehow had organized themselves into patterns of communication that could respond to it, and presumably other unknown future happenings.


I think a lot of ppl that work in transportation default to calling their dispatch team when something goes wrong. This is intentional – companies want their pilots to speak up ASAP rather than trying to fix stuff on their own. Pilots are reassured that doing so won’t lead to being reprimanded. The resulting reflex of “when in doubt, call dispatch” is a major source of safety in transport operations.

Put it all together and it’s like how a body coagulates blood around a wound as a stop loss.