Event JSON
{
"id": "a81a01d10a0ecd64bb687208a93b9b5be1b12d4f00a5ab9f17e46b7845e16353",
"pubkey": "1ace68472745b2642934c6172c5994f5f094f01deb752145d25225e637a87a50",
"created_at": 1742602887,
"kind": 1,
"tags": [
[
"p",
"726b54337caa3467a1ce92073fb9e93b4db61bd72a8b67d3ce730f7774f8f835",
"wss://relay.mostr.pub"
],
[
"p",
"1a5ac5b37984c5e37a11bc914029a81f025326ea7950c9475d9a3f21a494cb56",
"wss://relay.mostr.pub"
],
[
"e",
"00591440302bac63358039180eb0c2685420b2ded2f957b3f46a1a3761e68492",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://infosec.exchange/users/SteveBellovin/statuses/114203222835839419",
"activitypub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqwf44gvmu4g6x0gwwjgrnlw0f8dxmvx7h929k057wwv8hwa8clq6s0z5k2y Many years ago, I was on the Internet Architecture Board. The IAB and the Internet Engineering Steering Group were about to issue an RFC on cryptography policy. Looking at the RFC numbers published around then, I sent a note to Jon Postel, the RFC editor, and asked if we could have RFC 1984. He replied, \"We never reserve RFC numbers—but coincidences can happen.\" Guess what number the eventual RFC had…",
"sig": "744d0dff87b08db727181577a95e5d3830fdad19eb812f8d8f8ae29452007666c00d5cdfdb74f5f14d06e21a2b5fa4547470989e9ee3904f2a6413b8a2a0566b"
}