diff --git a/gpl-lgpl.tex b/gpl-lgpl.tex
index 0e9f417049cc3547d4714d71e6ffc6cc0a70fff4..126fd7120fe481051ca7d94320270bf14cbd8e9d 100644
--- a/gpl-lgpl.tex
+++ b/gpl-lgpl.tex
@@ -2574,14 +2574,21 @@ licensor in a chain of distribution.  The GPL solves this problem in another
 way --- through its automatic licensing provision found in GPLv3\~S10 (which
 is discussed in more detail in \S\~ref{GPLv3s10} of this tutorial).
 
-% FIXME: new section here, just to talk DRM before the other section.
-
-GPLv3 introduces provisions that respond to the growing practice of
-distributing GPL-covered programs in devices that employ technical means
-to restrict users from installing and running modified versions.  This
-practice thwarts the expectations of developers and users alike, because
-the right to modify is one of the core freedoms the GPL is designed to
-secure.
+\section{GPLv3's views on DRM and Device Lock-Down}
+
+The issues of DRM, device lock-down and encryption key disclosure were the
+most hotly debated during the GPLv3 process.  FSF's views on this were sadly
+frequently misunderstood and, comparing the provisions related to these
+issues in the earliest drafts of GPLv3 to  the final version of GPLv3 shows
+the FSF's willingness to compromise on tactical issues to reach the larger
+goal of software freedom.
+
+Specifically, GPLv3 introduced provisions that respond to the growing
+practice of distributing GPL-covered programs in devices that employ
+technical means to restrict users from installing and running modified
+versions.  This practice thwarts the expectations of developers and users
+alike, because the right to modify is one of the core freedoms the GPL is
+designed to secure.
 
 Technological measures to defeat users' rights --- often described by such
 Orwellian phrases as ``digital rights management,'' which actually means