attachment
<div dir="ltr"><div><div><div><div><div><div>Hi,<br><br></div>Well-written survey of the legitimate needs for security monitoring<br></div>(i.e., attack discovery and mitigation) across the whole Internet<br></div>(e.g., middleboxes, Enterprise, etc.) and effect of pervasive<br></div>encryption in obscuring these attack surfaces.<br><br></div>Cheers,<br></div>- Ira<br><div><div><div><div><div><div><div><div><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><br><div style="display:inline"></div><div style="display:inline"></div><div style="display:inline"></div><div></div><div></div><div></div><div></div></div></div></div></div></div>
<br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Stephen Farrell</b> <span dir="ltr"><<a href="mailto:stephen.farrell@cs.tcd.ie">stephen.farrell@cs.tcd.ie</a>></span><br>Date: Mon, Feb 13, 2017 at 11:50 AM<br>Subject: [saag] Fwd: Last Call: <draft-mm-wg-effect-encrypt-07.txt> (Effect of Pervasive Encryption) to Informational RFC<br>To: "<a href="mailto:saag@ietf.org">saag@ietf.org</a>" <<a href="mailto:saag@ietf.org">saag@ietf.org</a>><br><br><br><br>
Hiya,<br>
<br>
As previously discussed here, I've started the IETF LC<br>
for this. Further comments, if you have any, are probably<br>
better directed to <a href="mailto:ietf@ietf.org">ietf@ietf.org</a>, though of course I'd<br>
also consider any sent here.<br>
<br>
Cheers,<br>
S.<br>
<br>
<br>
-------- Forwarded Message --------<br>
Subject: Last Call: <draft-mm-wg-effect-encrypt-<wbr>07.txt> (Effect of<br>
Pervasive Encryption) to Informational RFC<br>
Date: Mon, 13 Feb 2017 08:40:50 -0800<br>
From: The IESG <<a href="mailto:iesg-secretary@ietf.org">iesg-secretary@ietf.org</a>><br>
Reply-To: <a href="mailto:ietf@ietf.org">ietf@ietf.org</a><br>
To: IETF-Announce <<a href="mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a>><br>
CC: Paul Hoffman <<a href="mailto:paul.hoffman@vpnc.org">paul.hoffman@vpnc.org</a>>, <a href="mailto:paul.hoffman@vpnc.org">paul.hoffman@vpnc.org</a>,<br>
<a href="mailto:draft-mm-wg-effect-encrypt@ietf.org">draft-mm-wg-effect-encrypt@<wbr>ietf.org</a>, <a href="mailto:stephen.farrell@cs.tcd.ie">stephen.farrell@cs.tcd.ie</a><br>
<br>
<br>
The IESG has received a request from an individual submitter to consider<br>
the following document:<br>
- 'Effect of Pervasive Encryption'<br>
<draft-mm-wg-effect-encrypt-<wbr>07.txt> as Informational RFC<br>
<br>
The IESG plans to make a decision in the next few weeks, and solicits<br>
final comments on this action. Please send substantive comments to the<br>
<a href="mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 2017-03-13. Exceptionally, comments may be<br>
sent to <a href="mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In either case, please retain the<br>
beginning of the Subject line to allow automated sorting.<br>
<br>
Abstract<br>
<br>
<br>
Increased use of encryption impacts operations for security and<br>
network management causing a shift in how these functions are<br>
performed. In some cases, new methods to both monitor and protect<br>
data will evolve. In other cases, the ability to monitor and<br>
troubleshoot could be eliminated. This draft includes a collection<br>
of current security and network management functions that may be<br>
impacted by the shift to increased use of encryption. This draft<br>
does not attempt to solve these problems, but rather document the<br>
current state to assist in the development of alternate options to<br>
achieve the intended purpose of the documented practices.<br>
<br>
<br>
<br>
<br>
The file can be obtained via<br>
<a href="https://datatracker.ietf.org/doc/draft-mm-wg-effect-encrypt/" rel="noreferrer" target="_blank">https://datatracker.ietf.org/<wbr>doc/draft-mm-wg-effect-<wbr>encrypt/</a><br>
<br>
IESG discussion can be tracked via<br>
<a href="https://datatracker.ietf.org/doc/draft-mm-wg-effect-encrypt/ballot/" rel="noreferrer" target="_blank">https://datatracker.ietf.org/<wbr>doc/draft-mm-wg-effect-<wbr>encrypt/ballot/</a><br>
<br>
No IPR declarations have been submitted directly on this I-D.<br>
<br>
I-D nits notes that there is one use of a 2119 MUST (which can be<br>
lowercased I guess) and the reference to [SACM] in 5.7 has no matching<br>
entry in section 12, but we can fix those later.<br>
This is an AD-sponsored last call. The relevant AD (Stephen<br>
Farrell) will be escaping the IESG in March, so there may not be time to<br>
get this document approved by the IESG before then,<br>
e.g., if there is substantive discussion during/after IETF LC.<br>
Warren Kumari, (one of the incoming ADs) has agreed to pick<br>
this up should that be necessary. But better to get it over the<br>
line if we do turn out to have IETF consensus for it now.<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>______________________________<wbr>_________________<br>
saag mailing list<br>
<a href="mailto:saag@ietf.org">saag@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/saag" rel="noreferrer" target="_blank">https://www.ietf.org/mailman/<wbr>listinfo/saag</a><br>
<br></div><br></div></div></div></div></div></div></div></div></div>