<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Thanks Seun for sharing to benefit our community!!<br><br>Mamadou<br><br><div><hr id="stopSpelling">Date: Sat, 22 Aug 2015 17:52:07 +0100<br>From: seun.ojedeji@gmail.com<br>To: africann@afrinic.net<br>CC: rpd@afrinic.net<br>Subject: [AfrICANN-discuss] Fwd: RFC 7624 on Confidentiality in the Face of Pervasive Surveillance: A Threat Model and Problem Statement<br><br><p dir="ltr">Hi,</p>
<p dir="ltr">This could be useful to internet users/providers that have interest/concern about internet privacy/surveillance.</p>
<p dir="ltr">The memo is still up for comments and anyone can contribute to improving it.</p>
<p dir="ltr">Cheers!</p>
<p dir="ltr">Sent from my Asus Zenfone2<br>
Kindly excuse brevity and typos.</p>
<div class="ecxgmail_quote">---------- Forwarded message ----------<br>From: "Avri Doria" <<a href="mailto:avri@acm.org">avri@acm.org</a>><br>Date: 22 Aug 2015 15:15<br>Subject: Fwd: RFC 7624 on Confidentiality in the Face of Pervasive Surveillance: A Threat Model and Problem Statement<br>To: <<a href="mailto:NCSG-DISCUSS@listserv.syr.edu">NCSG-DISCUSS@listserv.syr.edu</a>><br>Cc: <br><br>Thought this might be interesting/useful to several efforts.<br>
<br>
avri<br>
<br>
<br>
-------- Forwarded Message --------<br>
Subject: RFC 7624 on Confidentiality in the Face of Pervasive<br>
Surveillance: A Threat Model and Problem Statement<br>
Date: Thu, 20 Aug 2015 15:34:38 -0700 (PDT)<br>
From: <a href="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a><br>
To: <a href="mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a>, <a href="mailto:rfc-dist@rfc-editor.org">rfc-dist@rfc-editor.org</a><br>
CC: <a href="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a><br>
<br>
A new Request for Comments is now available in online RFC libraries.<br>
<br>
<br>
RFC 7624<br>
<br>
Title: Confidentiality in the Face of<br>
Pervasive Surveillance: A Threat Model and<br>
Problem Statement<br>
Author: R. Barnes, B. Schneier,<br>
C. Jennings, T. Hardie,<br>
B. Trammell, C. Huitema,<br>
D. Borkmann<br>
Status: Informational<br>
Stream: IAB<br>
Date: August 2015<br>
Mailbox: rlb@ipv.sx,<br>
<a href="mailto:schneier@schneier.com">schneier@schneier.com</a>,<br>
<a href="mailto:fluffy@cisco.com">fluffy@cisco.com</a>,<br>
<a href="mailto:ted.ietf@gmail.com">ted.ietf@gmail.com</a>,<br>
<a href="mailto:ietf@trammell.ch">ietf@trammell.ch</a>,<br>
<a href="mailto:huitema@huitema.net">huitema@huitema.net</a>,<br>
<a href="mailto:daniel@iogearbox.net">daniel@iogearbox.net</a><br>
Pages: 24<br>
Characters: 62260<br>
Updates/Obsoletes/SeeAlso: None<br>
<br>
I-D Tag: draft-iab-privsec-confidentiality-threat-07.txt<br>
<br>
URL: <a href="https://www.rfc-editor.org/info/rfc7624" rel="noreferrer" target="_blank">https://www.rfc-editor.org/info/rfc7624</a><br>
<br>
DOI: <a href="http://dx.doi.org/10.17487/RFC7624" rel="noreferrer" target="_blank">http://dx.doi.org/10.17487/RFC7624</a><br>
<br>
Since the initial revelations of pervasive surveillance in 2013,<br>
several classes of attacks on Internet communications have been<br>
discovered. In this document, we develop a threat model that<br>
describes these attacks on Internet confidentiality. We assume an<br>
attacker that is interested in undetected, indiscriminate<br>
eavesdropping. The threat model is based on published, verified<br>
attacks.<br>
<br>
This document is a product of the Internet Architecture Board.<br>
<br>
<br>
INFORMATIONAL: This memo provides information for the Internet community.<br>
It does not specify an Internet standard of any kind. Distribution of<br>
this memo is unlimited.<br>
<br>
This announcement is sent to the IETF-Announce and rfc-dist lists.<br>
To subscribe or unsubscribe, see<br>
<a href="https://www.ietf.org/mailman/listinfo/ietf-announce" rel="noreferrer" target="_blank">https://www.ietf.org/mailman/listinfo/ietf-announce</a><br>
<a href="https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist" rel="noreferrer" target="_blank">https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist</a><br>
<br>
For searching the RFC series, see <a href="https://www.rfc-editor.org/search" rel="noreferrer" target="_blank">https://www.rfc-editor.org/search</a><br>
For downloading RFCs, see <a href="https://www.rfc-editor.org/rfc.html" rel="noreferrer" target="_blank">https://www.rfc-editor.org/rfc.html</a><br>
<br>
Requests for special distribution should be addressed to either the<br>
author of the RFC in question, or to <a href="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a>. Unless<br>
specifically noted otherwise on the RFC itself, all RFCs are for<br>
unlimited distribution.<br>
<br>
<br>
The RFC Editor Team<br>
Association Management Solutions, LLC<br>
<br>
<br>
<br>
<br>
<br>
---<br>
This email has been checked for viruses by Avast antivirus software.<br>
<a href="https://www.avast.com/antivirus" rel="noreferrer" target="_blank">https://www.avast.com/antivirus</a><br>
</div>
<br>_______________________________________________
AfrICANN mailing list
AfrICANN@afrinic.net
https://lists.afrinic.net/mailman/listinfo/africann</div> </div></body>
</html>