[IPP] Fwd: Last Call: Effect of Pervasive Encryption to Informational RFC

[IPP] Fwd: Last Call: Effect of Pervasive Encryption to Informational RFC

[IPP] Fwd: Last Call: Effect of Pervasive Encryption to Informational RFC

Ira McDonald blueroofmusic at gmail.com
Mon Feb 13 23:25:47 UTC 2017


Well-written survey of the legitimate needs for security monitoring
(i.e., attack discovery and mitigation) across the whole Internet
(e.g., middleboxes, Enterprise, etc.) and effect of pervasive
encryption in obscuring these attack surfaces.

- Ira

---------- Forwarded message ----------
From: Stephen Farrell <stephen.farrell at cs.tcd.ie>
Date: Mon, Feb 13, 2017 at 11:50 AM
Subject: [saag] Fwd: Last Call: <draft-mm-wg-effect-encrypt-07.txt> (Effect
of Pervasive Encryption) to Informational RFC
To: "saag at ietf.org" <saag at ietf.org>


As previously discussed here, I've started the IETF LC
for this. Further comments, if you have any, are probably
better directed to ietf at ietf.org, though of course I'd
also consider any sent here.


-------- Forwarded Message --------
Subject: Last Call: <draft-mm-wg-effect-encrypt-07.txt> (Effect of
Pervasive Encryption) to Informational RFC
Date: Mon, 13 Feb 2017 08:40:50 -0800
From: The IESG <iesg-secretary at ietf.org>
Reply-To: ietf at ietf.org
To: IETF-Announce <ietf-announce at ietf.org>
CC: Paul Hoffman <paul.hoffman at vpnc.org>, paul.hoffman at vpnc.org,
draft-mm-wg-effect-encrypt at ietf.org, stephen.farrell at cs.tcd.ie

The IESG has received a request from an individual submitter to consider
the following document:
- 'Effect of Pervasive Encryption'
  <draft-mm-wg-effect-encrypt-07.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf at ietf.org mailing lists by 2017-03-13. Exceptionally, comments may be
sent to iesg at ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.


   Increased use of encryption impacts operations for security and
   network management causing a shift in how these functions are
   performed.  In some cases, new methods to both monitor and protect
   data will evolve.  In other cases, the ability to monitor and
   troubleshoot could be eliminated.  This draft includes a collection
   of current security and network management functions that may be
   impacted by the shift to increased use of encryption.  This draft
   does not attempt to solve these problems, but rather document the
   current state to assist in the development of alternate options to
   achieve the intended purpose of the documented practices.

The file can be obtained via

IESG discussion can be tracked via

No IPR declarations have been submitted directly on this I-D.

I-D nits notes that there is one use of a 2119 MUST (which can be
lowercased I guess) and the reference to [SACM] in 5.7 has no matching
entry in section 12, but we can fix those later.
This is an AD-sponsored last call. The relevant AD (Stephen
Farrell) will be escaping the IESG in March, so there may not be time to
get this document approved by the IESG before then,
e.g., if there is substantive discussion during/after IETF LC.
Warren Kumari, (one of the incoming ADs) has agreed to pick
this up should that be necessary. But better to get it over the
line if we do turn out to have IETF consensus for it now.

saag mailing list
saag at ietf.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20170213/c41dd707/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 465 bytes
Desc: not available
URL: <http://www.pwg.org/pipermail/ipp/attachments/20170213/c41dd707/attachment.sig>

More information about the ipp mailing list