From: Roland Hieber Date: Mon, 16 Dec 2013 14:44:33 +0000 (+0100) Subject: fix references, tuning X-Git-Tag: final~10 X-Git-Url: http://git.rohieb.name/skm-ma-ws1314.git/commitdiff_plain/04c610bbe6f1781d0b051334ae92788dddbb31de fix references, tuning --- diff --git a/biblio.bib b/biblio.bib index fff80b7..3d0c6e8 100644 --- a/biblio.bib +++ b/biblio.bib @@ -9,7 +9,7 @@ year = "2012" } -@misc{xep-0174, +@misc{xep0174, abstract = "This specification defines how to communicate over local or wide-area networks using the principles of zero-configuration networking for endpoint discovery and the syntax of XML streams and XMPP messaging for real-time communication. This method uses DNS-based Service Discovery and Multicast DNS to discover entities that support the protocol, including their IP addresses and preferred ports. Any two entities can then negotiate a serverless connection using XML streams in order to exchange XMPP message and IQ stanzas.", author = "Saint-Andre, Peter", howpublished = "\url{http://xmpp.org/extensions/xep-0174.html}", @@ -148,7 +148,7 @@ year = "2012" } -@misc{xep-0060, +@misc{xep0060, abstract = "This specification defines an XMPP protocol extension for generic publish-subscribe functionality. The protocol enables XMPP entities to create nodes (topics) at a pubsub service and publish information at those nodes; an event notification (with or without payload) is then broadcasted to all entities that have subscribed to the node. Pubsub therefore adheres to the classic Observer design pattern and can serve as the foundation for a wide variety of applications, including news feeds, content syndication, rich presence, geolocation, workflow systems, network management systems, and any other application that requires event notifications.", author = "Millard, Peter and Saint-Andre, Peter and Meijer, Ralph", howpublished = "\url{http://xmpp.org/extensions/xep-0060.html}", @@ -159,7 +159,7 @@ year = "2010" } -@misc{xep-0175, +@misc{xep0175, abstract = "This document specifies best practices for use of the SASL ANONYMOUS mechanism in the context of client authentication with an XMPP server.", author = "Saint-Andre, Peter", howpublished = "\url{http://xmpp.org/extensions/xep-0175.html}", @@ -169,8 +169,8 @@ title = "{XEP-0175: Best Practices for Use of SASL ANONYMOUS}", year = "2009" } -P -@misc{xep-0045, + +@misc{xep0045, abstract = "This specification defines an XMPP protocol extension for multi-user text chat, whereby multiple XMPP users can exchange messages in the context of a room or channel, similar to Internet Relay Chat (IRC). In addition to standard chatroom features such as room topics and invitations, the protocol defines a strong room control model, including the ability to kick and ban users, to name room moderators and administrators, to require membership or passwords in order to join the room, etc.", author = "Saint-Andre, Peter", howpublished = "\url{http://xmpp.org/extensions/xep-0045.html}", diff --git a/main.tex b/main.tex index 38eaf82..314324a 100644 --- a/main.tex +++ b/main.tex @@ -5,7 +5,7 @@ \usepackage{color} \usepackage{graphicx} \usepackage{wrapfig} -\usepackage{hyperref} +\usepackage[hidelinks=true]{hyperref} \urlstyle{sf} diff --git a/sec-chatty-things.tex b/sec-chatty-things.tex index f7ef5a8..62779b7 100644 --- a/sec-chatty-things.tex +++ b/sec-chatty-things.tex @@ -37,7 +37,7 @@ thus further reducing the memory footprint of a running system: \item support for IPv6 \item support for Multi-User Chats (XEP-0045), which are used for information filtering - \item support for SASL ANONYMOUS login for XMPP servers \ref{xep-0175} + \item support for SASL ANONYMOUS login for XMPP servers \cite{xep0175} \item a new publish-subscribe mechanism called Temporary Subscription for Presence (see \ref{sec:tsp}) \item XMPP Serverless Messaging (XEP-0174), using \term{uBonjour} as diff --git a/sec-xmpp.tex b/sec-xmpp.tex index 3a44829..1fadb2d 100644 --- a/sec-xmpp.tex +++ b/sec-xmpp.tex @@ -78,7 +78,7 @@ remembers the JIDs for her. In XMPP, this is address book is called In order to see their chat status (which can be one of ``online'', ``offline'', and several ``away'' or ``do not disturb'' states), a user needs to subscribe to the other user's status. The mechanism behind this is called -\term{Publish-Subscribe} and is specified in XEP-0060~\cite{xep-0060}. It can +\term{Publish-Subscribe} and is specified in XEP-0060~\cite{xep0060}. It can be used to notify interested users about changes in personal information, and implements the classic Observer pattern. @@ -94,7 +94,7 @@ All communication takes place between the client and the server over \code{} \subsubsection{Multi-User Chats} Besides one-to-one messaging, XMPP also allows users to create multi-user -chat rooms, which is specified in \cite{xep-0045}. Each chat room is given a +chat rooms, which is specified in \cite{xep0045}. Each chat room is given a unique JID to which the users send their messages to. Each incoming message is then dispatched to all users which have joined the room. @@ -105,7 +105,7 @@ the resource part of the room JID specifies the desired nick name. \pages{1} To overcome the need for a central server and authentication, XMPP Serverless -Messaging~\cite{xep-0174} allows XMPP clients on a network to build a +Messaging~\cite{xep0174} allows XMPP clients on a network to build a peer-to-peer mesh network and chat directly with each other. This feature was first introduced by Apple as part of their \term{Bonjour} project, and nowadays it is also available in many other XMPP clients.