Tag Archives: engineering

The perpass list is for IETF discussion of pervasive monitoring. IETF specifications need to be designed to protect against pervasive monitoring where possible. This list is intended for technical discussions attempting to meet that goal. Discussion is limited to specific technical proposals for improvements in IETF protocols, their implementation or deployment and to IETF process changes aiming to increase the liklihood that development, implementation and deployment of IETF protocols results in better mitigation for pervasive monitoring. Those with proposals are encouraged to embody them in detailed internet-draft specifications, rather than relying solely on email messages. The typical modus-operandi of the perpass list should be to identify a credible piece of work, with identified volunteer effort, and then to find a home for that work within the IETF. Once such a home is identified work should move to whatever other lists are relevant.


That’s the ti­tle of RFC 7258, al­so known as BCP 188 (where BCP stands for “Best Cur­rent Practice”); it rep­re­sents In­ter­net Engi­neer­ing Task Force con­sen­sus on the fact that many pow­er­ful well-funded en­ti­ties feel it is ap­pro­pri­ate to mon­i­tor people’s use of the Net, with­out telling those peo­ple. The con­sen­sus is: This mon­i­tor­ing is an at­tack and de­sign­ers of In­ter­net pro­to­cols must work to mit­i­gate it.