Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

RFC 35140: HTTP Do-Not-Stab (2023)

5snb.club

Post reply on HN
Print view View original

1–10 of 219 posts

Re: RFC 35140: HTTP Do-Not-Stab (2023)

#3

Post by vandyswa »

sillysaurusx wrote: post #2

I’ve always wondered, since an RFC is a request for comment, how does one leave a comment? And who?

RFC's operate under the IETF. RFC's are developed under some specific group, and you can join that group, the business is generally conducted on email. There are (well, were back when I participated) in-person meetings, but attendance there was not mandatory.

Re: RFC 35140: HTTP Do-Not-Stab (2023)

#7

Post by staplung »

sillysaurusx wrote: post #2

I’ve always wondered, since an RFC is a request for comment, how does one leave a comment? And who?

A bit of lore that I learned in my networking class in college was that the RFC name was chosen as tongue in cheek in that by the time a proposal gets to the RFC stage, comments are very much not appreciated. You're supposed to comment well before that point.

No idea if that bit of lore is true but it is certainly the case that RFCs are usually the final word on the relevant standard. In fact, once they get their ID, RFCs cannot be modified or rescinded; only superseded by another RFC.

Re: RFC 35140: HTTP Do-Not-Stab (2023)

#8

Post by SilasX »

staplung wrote: post #7
sillysaurusx wrote: post #2

I’ve always wondered, since an RFC is a request for comment, how does one leave a comment? And who?

A bit of lore that I learned in my networking class in college was that the RFC name was chosen as tongue in cheek in that by the time a proposal gets to the RFC stage, comments are very much not appreciated. You're supposed to comment well before that point. No idea if that bit of lore is true but it is certainly the case that RFCs are usually the final word on the relevant standard. In fact, once they get their ID,…

Then they should be renamed CFCs (closed for comments).

Re: RFC 35140: HTTP Do-Not-Stab (2023)

#9

Post by jsheard »

cuuupid wrote: post #5

For the low price of $20/1000 clicks, I will provide you with a stabbing consent banner, fully compliant with upcoming EU and CA regulations on web-based stabbing.

I'm sold, the distinctions between "necessary", "targeting", "performance" and "functional" stabbings are such a minefield. Not to mention how I'm supposed to properly disclose the 846 different stabbing brokers I work with. How's a man supposed to make a living stabbing people with all of this red tape in the way?
Post reply on HN