update.tex

ftam等标准协议服务器和客户端的源代码。

	    particular community. 
\end{describe}


\subsubsection{TP4}
\begin{describe}
\item[\verb"nsap\_default\_stack"]
	If the TP4 interface has access to both CONS and CLNS, this
	parameter is used to determine the default.  The value can be either
	\verb"CONS" or \verb"CLNS".
	The default value is \verb"CLNS".
	You should also consult \man isonsapsnpa(5), which defines how
	the default stack can be overridden for specific NSAP addresses.
\item[\verb"local\_nsap"]
	A default NSAP address for tsapd to listen on if the \verb"-N"
	flag is used! 
\end{describe}

\subsubsection{TLI TP4}
The following setting are only useful when TP\_TLI is defined, that is,
the TP4 is provided by the TLI interface.

\begin{describe}
\item[\verb"tli\_cots\_dev"]
	The name of the device node used to access COTS
	(default \verb"/dev/ositpi").
\item[\verb"tli\_clts\_dev"]
	The name of the device node used to access CLTS
	(default \verb"/dev/ositpi").
\end{describe}

\subsubsection{ICL TLI TP4}
When using TLI on an ICL~DRS6000, the following two addressing 
parameters will need setting:

\begin{describe}
\item[\verb"tli\_initiator\_prefix"]
	The subnet name of the network interface to use for outgoing X.25 calls
	(default \verb"x25_tliin").
\item[\verb"tli\_responder\_prefix"]
	The subnet name of the network interface to use for incomming
	X.25 calls. 
	(default \verb"x25_tlire").
\end{describe}

\subsubsection{XTI TP4}
The following setting is only useful when XTI is defined.  That is TP4
is provided by an XTI interface.  XTI is only alpha test in this release.
\begin{describe}
\item[\verb"xti\_tp0\_ident"]
	The string value is the string passed to the XTI interface during
	t\_bind for X121 addresses.
	Default \verb"TOSITP0".
\item[\verb"xti\_tp4\_ident"]
	The string value is the string passed to the XTI interface during
	t\_bind for TP4 addresses.
	Default \verb"TOSITP4".
\end{describe}


\chapter{QUIPU}

This chapter details changes to the Volume 5 manual: QUIPU.

There have been extensive changes to the Chapter 6: DE.  The new
chapter is included in its entirety as Appendix~\ref{DUA:de}.

There is a new Chapter on ``DM tools''.  These are a set of DISH shell
scripts which provide some simple bulk data management functions using
DAP.

Chapter 10 has a new sub section on the SearchACL attribute syntax, 
this is in Appendix~\ref{searchacl}.

Chapter 11 of Volume 5 has a new section describing searcl ACLs in
more detail.  This is included as Appendix~\ref{disc_sacl} of this document.
  
It should also be noted that the {\tt [e-mail]} support
address no longer exists.  This has been replaced with a bug reporting
address.  Any changes required will be incorporated into the ISODE Consortium
releases, and not released to the public domain.  

\begin{quote}
{\tt [e-mail]\/}
\end{quote}
However, it should be noted that the open discussion list 
\begin{quote}
{\tt [e-mail]\/}
\end{quote}
does still exists.  Mail 
\begin{quote}
{\tt [e-mail]\/}
\end{quote}
to join the discussion.

\section{Text Changes}

The second paragraph of Section 17.2.1, page 201 in volume 5 should read:
\begin{quote}
The fields \verb"ca_ext", \verb"ca_progress", \verb"ca_requestor" 
and \verb"ca_aliased_rdns" are provided as
they are defined within X.500.  Neither the QUIPU DSA or DUA use these
fields, but they must be initialized to zero.
\end{quote}
  
The text in Section 17.2.2 ``Results'' should read:
\begin{quote}
The field \verb"cr_aliasdereferenced" is set to \verb"TRUE" if the base
object of the operation was an alias, and was dereferenced.

The field \verb"cr_requestor" is the DN of the requestor of the
operation.  It is only used for secure operations.

The other fields are used by {\em pepsy} whilst encoding and decoding
the structure.
\end{quote}

All of the references to \file{.podrc} in Chapter 9 should be replaced
with \file{.duarc}

\chapter{Known Problems}

This chapter describes some known problems with the current
implementation of ISODE.

\subsubsection{Simply Encoded Data}

If ``user-data'' at the presentation layer is simply encoded, ISODE is
sometimes unable to decode the data.  ISODE always uses fully encoded
data.  A default context in not proposed by any of the applications,
thus simply encoded data is rarely required.

\subsubsection{Large RFC-1006 TPDUs}

If RFC-1006 is used to transfer a large TPDU, then the current
implementation effectively does a read of the RFC-1006 header,
followed by \verb+n+ bytes of data, as specified in the header.

If \verb+n+ is large, it will require several reads to 
actually read this number of bytes. These reads are done
synchronously, one after another until the packet is in. However, if
its a large packet and the TCP connection is unreliable, some of the 64K
may get dropped and have to be retransmitted.
If a router goes down also in this time you can get left hanging.
This particularly effects QUIPU.

\subsubsection{ACSE Initialisation}

During the initialisation stage of an ACSE connection, it is possible
for a connect request to momentarily block.


\appendix

\include{q-de}

\include{q-dm}

\chapter{Attribute Synatxes}

The sections in this appendix should be placed at the end of Section~10.3
``COSINE/Internet Attribute Syntaxes'' of the Version~7.0 manual.

\section{SearchACL}

\label{searchacl}
\index{searchACL attribute}
\begin{center}\small
\begin{tabular}{|l|}\hline
QUIPU Attributes \\ \hline
	searchACL\\
\hline
\end{tabular}
\end{center}
\begin{quote}\begin{verbatim}
<searchaclvalue>::= <aclwho> "#" <access> "#" <attrs> 
                    "#" <scope>
                    [ "#" <max-results> "#" <partialresults>
                    [ "#" <minkeylen> ]]
<access>        ::= "search" | "nosearch"
<attrs>         ::= "default" | <attr-list>
<attr-list>     ::= <attributetype> | <attributetype> 
                    "$" <attr-list>
<scope>         ::= <singlescope> | <singlescope> 
                    "$" <scope>
<singlescope>   ::= "subtree" | "singlelevel" | "baseobject"
<max-results>   ::= <integer>
<partialresults>::= "partialresults" | "nopartialresults"
<minkeylen>     ::= <integer>
\end{verbatim}\end{quote}
The use of the search ACL attribute is discussed in Section~\ref{disc_sacl}.

\section{ListACL}
\label{listacl}
\index{listACL attribute}
\begin{center}\small
\begin{tabular}{|l|}\hline
QUIPU Attributes \\ \hline
	listACL\\
\hline
\end{tabular}
\end{center}
\begin{quote}\begin{verbatim}
<listaclvalue>  ::= <aclwho> "#" <access> "#" <scope>
                        [ "#" <max-results> ]
<access>        ::= "list" | "nolist"
<scope>         ::= "entry" | "children"
<max-results>   ::= <integer>
\end{verbatim}\end{quote}
The use of the list ACL attribute is discussed in Section~\ref{disc_lacl}.

\section{AuthPolicy}
\label{authpolicy}
\index{authPolicy attribute}
\index{authentication policy}
\begin{center}\small
\begin{tabular}{|l|}\hline
QUIPU Attributes \\ \hline
	authPolicy\\
\hline
\end{tabular}
\end{center}
\begin{quote}\begin{verbatim}
<authpvalue>    ::= <modpolicy> "#" <readpolicy> 
                    "#" <searchpolicy>
<modpolicy>     ::= <authpolicy>
<readpolicy>    ::= <authpolicy>
<searchpolicy>  ::= <authpolicy>
<authpolicy>    ::= "trust" | "simple" | "strong"
\end{verbatim}\end{quote}

\include{q-sacl}

\chapter{ISODE Consortium}
\label{IC}

The ISODE Consortium is a not-for-profit cooperative enterprise, whose
mission is to promote and develop the ISODE package of OSI (Open
System Interconnection) applications, which has been used extensively
in the research community.  The ISODE Consortium will be able to
evolve the ISODE software more rapidly than would be possible for any
single member.  This will be to the mutual benefit of members of the
consortium, and will help to stimulate the market for OSI, which
is key technology to enable open communication between and within
organisations.  Membership of the ISODE Consortium is open to any
organisation in any country.

The ISODE Consortium releases of ISODE will be made exclusively
available to the ISODE Consortium members or by purchase of products
from ISODE Consortium members.  Academic organisations, and not for
profit or government organisations with research as their primary
purpose, will be given zero cost access to the ISODE Consortium releases,
on the basis of simply signing a licence with minimal administrative
overhead. This builds on a major strength of the ISODE package by
facilitating use of ISODE within the research community, whilst
allowing ISODE to evolve as a product base.

The ISODE Consortium has mailing lists for bug reports relating to the
ISODE Package.   These are:

\begin{quote}\begin{tabular}{ll}
[e-mail] &  -- bugs relating to QUIPU\\
[e-mail]    &  -- bugs relating to PP\\
[e-mail] &  -- bugs relating to any other parts of ISODE\\
\end{tabular}\end{quote}

These lists are for the planned ISODE Consortium releases of ISODE.  
Bug reports relating to the ``ISODE-8.0'' release of ISODE are
welcome.   Changes will be incorporated into the ISODE Consortium
releases, and not released to the public domain.  


Further information may be obtained from:-

\begin{tabular}{ll}
ISODE Consortium &               ISODE Consortium\\
US Office, c/o MCC &             European Office\\
P.O. Box 200195    &             P.O. Box 505\\
Austin             &             LONDON\\
TX 78720           &             SW11 1DX\\
USA                &           	 UK\\
Phone: [phone]       & Phone: [phone]\\
Fax:   [phone]       & Fax:   [phone]\\
EMail:  [e-mail]      & EMail:  [e-mail]\\
\end{tabular}

\chapter{Operating System Requirements}
\label{ports}

This appendix contains a table of hardware platforms and
operating systems this version of ISODE is believed to work on.  This
information is based upon reports sent to {\em bug-isode}.  
It is not known how accurate this table is.

\include{table-ports}


\end{document}