Dear PERPASS,

Stephen asked me to take a stab at a problem statement for PERPASS.  With
some help from Bruce, Cullen, and Ted, the results have just been published
as draft-barnes-pervasive-problem-00.

In general, this draft tries to outline at a technical level what we mean
by pervasive attack, and what the high level mitigations are.

Comments welcome!

Thanks,
--Richard



---------- Forwarded message ----------
From: <[email protected]>
Date: Mon, Jan 6, 2014 at 9:17 PM
Subject: New Version Notification for draft-barnes-pervasive-problem-00.txt
To: Cullen Jennings <[email protected]>, Ted Hardie <[email protected]>,
Bruce Schneier <[email protected]>, Richard Barnes <[email protected]>



A new version of I-D, draft-barnes-pervasive-problem-00.txt
has been successfully submitted by Richard Barnes and posted to the
IETF repository.

Name:           draft-barnes-pervasive-problem
Revision:       00
Title:          Pervasive Attack: A Threat Model and Problem Statement
Document date:  2014-01-06
Group:          Individual Submission
Pages:          23
URL:
http://www.ietf.org/internet-drafts/draft-barnes-pervasive-problem-00.txt
Status:
https://datatracker.ietf.org/doc/draft-barnes-pervasive-problem/
Htmlized:       http://tools.ietf.org/html/draft-barnes-pervasive-problem-00


Abstract:
   Documents published in 2013 have revealed several classes of
   "pervasive" attack on Internet communications.  In this document, we
   review the main attacks that have been published, and develop a
   threat model that describes these pervasive attacks.  Based on this
   threat model, we discuss the techniques that can be employed in
   Internet protocol design to increase the protocols robustness to
   pervasive attacks.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat
_______________________________________________
perpass mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/perpass

Reply via email to