svn commit: lorikeet r124 - in trunk/samba4-ad-thesis: .

[abartlet at samba.org]

Author: abartlet
Date: 2004-11-08 04:44:03 +0000 (Mon, 08 Nov 2004)
New Revision: 124

WebSVN: http://websvn.samba.org/cgi-bin/viewcvs.cgi?view=rev&root=lorikeet&rev=124

Log:
A few more fixes to the thesis, and expand/footnote acronyms.

Andrew Bartlett

Modified:
   trunk/samba4-ad-thesis/ack.tex
   trunk/samba4-ad-thesis/chapters.tex


Changeset:
Modified: trunk/samba4-ad-thesis/ack.tex
===================================================================
--- trunk/samba4-ad-thesis/ack.tex	2004-11-07 06:03:03 UTC (rev 123)
+++ trunk/samba4-ad-thesis/ack.tex	2004-11-08 04:44:03 UTC (rev 124)
@@ -4,7 +4,7 @@
 \addcontentsline{toc}{chapter}{Acknowledgements}
 
 This thesis would not be possible without the work of many, many people.
-It is traditional to first thank my parents - for it was their support,
+It is traditional to first thank my parents: for it was their support,
 in so many forms, that started me down the road that has ended in
 Software Engineering. 
 

Modified: trunk/samba4-ad-thesis/chapters.tex
===================================================================
--- trunk/samba4-ad-thesis/chapters.tex	2004-11-07 06:03:03 UTC (rev 123)
+++ trunk/samba4-ad-thesis/chapters.tex	2004-11-08 04:44:03 UTC (rev 124)
@@ -54,10 +54,10 @@
 In developing the new Samba4 infrastructure, the Samba Team decided
 to implement calls in the same way as Microsoft Windows 2003 Server.
 This decision is in line with a policy the Samba Team has consistently
-followed: to emulate the latest versions of Microsoft's products whereever
+followed: to emulate the latest versions of Microsoft's products wherever
 possible. Because other software vendors test against the latest Microsoft
 releases, and because the latest Microsoft release is the only `standard'
-we can reference in CIFS, we must emulate that very closely.
+we can reference, we must emulate that very closely.
 
 This policy has been hampered in recent years by the significant changes
 made by Microsoft in developing Active Directory.  The Samba and IBM
@@ -87,7 +87,8 @@
 a Samba3 domain were unable to enjoy all of the advantages Kerberos
 offers. Recent work has allowed Unix-like clients to use Kerberos
 in such domains\citep{sambaheimdal}, but Windows clients are still
-stuck with Microsoft's proprietary NTLM\citep{davenportntlm}.
+stuck with Microsoft's proprietary NTLM\citep{davenportntlm}%
+\footnote{NTLM is an authentication scheme, described in Chapter \ref{cha:NTLM}}.
 
 NT4 is now a legacy technology\citep{nt4eol}, despite the number
 of sites still running NT4 on both the client and the server. Therefore,
@@ -101,16 +102,15 @@
 
 \section{More than had been done before }
 
-Support for the CIFS protocol is clearly a characteristic element
-of Samba, but in Samba4 this is extended: Samba4 moves beyond the
-CIFS%
-\footnote{The network file-system, formerly known as SMB, that I describe in
-section \ref{sec:CIFS} %
-} protocol to expose DCE RPC%
+Support for the CIFS%
+\footnote{CIFS is a network file-system, formerly known as SMB, that I
+  describe in section \ref{sec:CIFS}}
+ protocol is clearly a characteristic element
+of Samba, but in Samba4 this is extended: Samba4 moves beyond CIFS to expose DCE RPC%
 \footnote{DCE-RPC is a Remote Procedure Call system, i.e. a system that invokes
 functions over a network, to perform distributed computing. This is
-described in section \ref{sec:DCE-RPC}%
-} over non-CIFS transports, such as directly on TCP/IP. 
+ described in section \ref{sec:DCE-RPC}}
+ over non-CIFS transports, such as directly on TCP/IP. 
 
 In previous versions of Windows, DCE RPCs were principally made over
 named pipes pipes, a concept existing in the file-system and shared
@@ -206,8 +206,10 @@
 \label{sec:CIFS}CIFS\citep{mind,hertel,sniacifs}, perhaps the most
 important protocol in the Microsoft networking landscape, dominates
 the connections made between almost all clients and servers on a Windows
-network. As a network file-system, file and print services are carried
-over CIFS, but unlike other network file-systems CIFS also presents
+network. Expanded, CIFS stands for the Common Internet File System,
+but the name only really tells us that it is a network file-system.
+Being a network file-system, files are shared over it, but unlike
+other network file-systems CIFS also presents printing and 
 an Inter-Process Communication (IPC) interface. Accordingly CIFS carries
 much of the network activity in an Active Directory implementation.
 
@@ -215,7 +217,7 @@
 \subsection{CIFS, SMB and NetBIOS}
 
 There is much confusion and contradictory terminology in the area
-of CIFS networking. Originally Microsoft (Server Message Block), it
+of CIFS networking. Originally SMB (Server Message Block), CIFS
 sits on top of the complete NetBIOS stack of services. Both of these
 are quite sufficient to fill a book,%
 \footnote{Chris's Hertel's Implementing CIFS\citet{hertel} is a very good reference
@@ -230,7 +232,7 @@
 Communication (IPC) over the network, making CIFS a transport layer
 to RAP%
 \footnote{The Remote Administration Protocol (RAP) was implemented in LAN Manager,
-OS/2 and subsequently Windows NT but is now largly replaced by DCE-RPC.%
+OS/2 and subsequently Windows NT but is now largely replaced by DCE-RPC.%
 } and DCE-RPC in particular. This is unusual in networking, because
 both local and remote IPC are conducted in a very similar way, abstracting
 away many of the usual concerns. Because this CIFS transport layer
@@ -244,7 +246,7 @@
 
 \section{LDAP}
 
-The Lightweight Directory Access Protocol (LDAP\citet{rfc2251,rfc2252,rfc2253,rfc2254,rfc2255,rfc2256})
+The Lightweight Directory Access Protocol (LDAP)\citep{rfc2251,rfc2252,rfc2253,rfc2254,rfc2255,rfc2256}
 has become the Internet standard for access to structured information,
 in particular information in the format of an X.500-like tree. Active
 Directory exports much of its information in the form of an LDAP tree,
@@ -287,11 +289,12 @@
 
 \subsection{Interface Definitions}
 
-Each function exposed over DCE-RPC has an associated interface definition,
-and if you were to make a particular interface public, all you would
-need to do is publish the IDL file - a file that you would compile
-yourself to create the initial framework and library on which you
-build your own client or server. 
+Each function exposed over DCE-RPC has an associated interface
+definition, written in the Interface Definition Language (IDL), and if
+you were to make a particular interface public, all you would need to
+do is publish the IDL file.  This is the same IDL file that you would
+compile yourself to create the initial framework and library on which
+you build your own client or server.
 
 One of the big changes in Samba4 is PIDL, our own IDL compiler, detailed
 in Section \ref{sec:PIDL---Midl}.
@@ -479,7 +482,7 @@
 Both systems encrypt the challenge using the secret encryption key.
 The client sends its result (rc) to the server. If the client's result
 matches the server's result (rs), then the two nodes have matching
-keys. (Image and text (c) Chris Hertel(hertel), \texttt{http://www.ubiqx.org/cifs/figures/smb-11.html})\end{quote}
+keys. (Image and text (c) Chris Hertel\citep{hertel}, \texttt{http://www.ubiqx.org/cifs/figures/smb-11.html})\end{quote}
 
 \end{figure}
 
@@ -1368,7 +1371,7 @@
 time to the DRSUAPI (Directory Replication Service) endpoint, the
 client uses `standard' LDAP%
 \footnote{Standard in the sense of being TCP based (not UDP, as CLDAP is) and
-being largely conformant with the LDAPv3 specifications\citep{rfc2251}.%
+being largely conforment with the LDAPv3 specifications\citep{rfc2251}.%
 } to modify the Kerberos service principal names associated with the
 machine account.