<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">On the Fly Encoded Application Flows Recognition by Relying on Statistical Features of IP Traffic</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Gianluca</forename><surname>Maiolini</surname></persName>
							<email>gianluca.maiolini@elsagdatamat.com</email>
							<affiliation key="aff0">
								<orgName type="institution" key="instit1">AMTEC SpA</orgName>
								<orgName type="institution" key="instit2">Loc. San Martino</orgName>
								<address>
									<settlement>Piancastagnaio</settlement>
									<region>SI</region>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Andrea</forename><surname>Baiocchi</surname></persName>
							<email>andrea.baiocchi@uniroma1.it</email>
							<affiliation key="aff1">
								<orgName type="department">INFOCOM Dept</orgName>
								<orgName type="institution">University of Roma &quot;Sapienza&quot; Rome</orgName>
								<address>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Antonello</forename><surname>Rizzi</surname></persName>
							<email>antonello.rizzi@uniroma1.it</email>
							<affiliation key="aff1">
								<orgName type="department">INFOCOM Dept</orgName>
								<orgName type="institution">University of Roma &quot;Sapienza&quot; Rome</orgName>
								<address>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Sara</forename><surname>Ferri</surname></persName>
							<email>sara.ferri@elsagdatamat.com</email>
							<affiliation key="aff0">
								<orgName type="institution" key="instit1">AMTEC SpA</orgName>
								<orgName type="institution" key="instit2">Loc. San Martino</orgName>
								<address>
									<settlement>Piancastagnaio</settlement>
									<region>SI</region>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Letizia</forename><surname>Gabbrielli</surname></persName>
							<email>letizia.gabbrielli@elsagdatamat.com</email>
							<affiliation key="aff0">
								<orgName type="institution" key="instit1">AMTEC SpA</orgName>
								<orgName type="institution" key="instit2">Loc. San Martino</orgName>
								<address>
									<settlement>Piancastagnaio</settlement>
									<region>SI</region>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">On the Fly Encoded Application Flows Recognition by Relying on Statistical Features of IP Traffic</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">F322E2A6E6569418B6606C9100714AE9</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T20:21+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>Traffic analysis</term>
					<term>statistical traffic classification</term>
					<term>SSH</term>
					<term>cluster analysis</term>
					<term>k-means</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>The secure collaborative judicial workspace (SCJW) has to allow the actors to use a number of communication and scheduling instruments for managing and storing any kind of documentation, video and audio recordings, evidence, among different Judicial offices of different countries. In this scenario is very important to identify encoded application delivering those application services to guarantee secure communication, but at the same time it is important to not compromise privacy of information exchanged. In this paper we aim at identifying application flows encoded within SSH tunnels by relying on statistical feature of IP packets. This will enable SCJW network administrator to identify un-trusted applications without analyze traffic contents.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1">Introduction</head><p>One of the most critical aspects every government should consider in the context of such a modernization is the field of justice. The most prominent issues is guaranteeing that any information flowing within judicial information systems is treated in a secure manner. In a cross border judicial cooperation during investigations, the information flows between different actors, different systems and at different levels. These information are very sensitive, they should be protected from unauthorized access and should be accessed only by specific people according to their role in the judicial process. Moreover document transfer from one country to another country must comply with the requirements of non repudiation. In a generic request of cross-border judicial cooperation one independent platform will support the country requesting judicial cooperation and other platform will support the country providing judicial cooperation. The secure collaborative judicial workspace (SCJW) has to allow the actors to use a number of communication and scheduling instruments for managing Post-proceedings of the 2nd International Conference on ICT Solutions for Justice (ICT4Justice 2009) and storing any kind of documentation, video recordings, audio recordings, evidences etc, among different Judicial offices of different countries. So, the SCJW has to deal with:</p><p>• the request and exchange of critical evidence documentation,</p><p>• the request for remote interrogations via videoconference,</p><p>• the request for specific actions, such as phone interception in another country, • the request for warrant of arrest. In this context is basic a fast traffic classification means according to the services data is generated by. Secure Shell or SSH is a network protocol that allows data to be exchanged using a secure channel between two networked devices. It is often used to login to a remote computer but it is also applied for tunneling, file transfer and forwarding arbitrary TCP ports over a secure channel between a local and a remote computer. What makes the detection of this protocol interesting is that its traffic is encrypted. Thus any payload analysis based classification method is irrelevant since the payload is encrypted. Actually DPI technology cannot recognize application delivered within SSH flows.</p><p>The objective of our work is to develop a real time system to recognize and classify SSH flows by analyzing statistical features of first IP packets belonging to a SSH connection, such as directions and lengths. This enables us to identify service applications without compromise privacy of contents exchanged by users during network communications. By recognition we mean identifying which flows belong to SSH protocol as opposed to other application level protocols. By classification we mean to identify the kind of service carried within each SSH connection, such as SCP, SFTP and HTTP over SSH. Experiments show that our approach permits us to achieve great recognition accuracy up to 99.2% for SSH identification and, once SSH has been identified, applications in those SSH tunnels are classified with accuracy up to 99.8%.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">Related Work</head><p>Different approaches to traffic classification have been developed, using information available at IP layer such as inter-arrival times, bytes transferred, packet size. Some proposals <ref type="bibr" target="#b3">[4]</ref>[5] need also semantically complete TCP flows as input.</p><p>In <ref type="bibr" target="#b0">[1]</ref>, Karagiannis et al. developed a heuristic that uses social, functional and application level behaviours of a host to identify all traffic flows originating from it. This approach, although really innovative, is tailored onto a specific source host.</p><p>Salgarelli et al. <ref type="bibr" target="#b1">[2]</ref> used only size and inter-arrival time of first n packets to create a statistical descriptor (a Fingerprint) of an application layer protocol: this fingerprint is then used to measure the similarity of a certain flow to the corresponding protocol.</p><p>The Hidden Markov Models (HMM) theory is used in <ref type="bibr" target="#b2">[3]</ref>: packets size and interarrival time are used to build a model describing a certain protocol. The results of the training phase is a HMM model describing the behaviour of each protocol. Even though this approach can classify distinct encrypted applications, its performance on SSH is (76% detection rate and 8% false negative) is not as good as well known application traffic such as WWW and instant messaging.</p><p>Moore et al. <ref type="bibr" target="#b3">[4]</ref> used a supervised machine learning algorithm called Naive Bayes (and its generalization, Kernel Estimation) on a wide set of characteristics (tens or hundreds), as flow duration, packets inter-arrival time and payload size and their statistics (mean, variance...). Moreover, they use a filtering technique to identify the best characteristics to be used with the mentioned methods.</p><p>A number of works <ref type="bibr" target="#b4">[5]</ref>[6] <ref type="bibr" target="#b6">[7]</ref> rely on unsupervised learning techniques. McGregor et al. <ref type="bibr" target="#b4">[5]</ref> explore the possibility to use cluster analysis to group flows using transport layer attributes, but they do not evaluate the accuracy of the classification. Zander et al. <ref type="bibr" target="#b5">[6]</ref> extend this work using another Expectation Maximization (EM) algorithm named Autoclass. They also analyze the best set of attributes to use. Both these works only test Bayesian clustering technique trained by an EM algorithm, which has a slow learning time.</p><p>Bernaille et al. <ref type="bibr" target="#b6">[7]</ref> use faster clustering algorithms representing data in different spaces: K-means and Gaussian Mixture Models (GMM) for euclidean space and Spectral clustering in HMM based space. The only features they use are packet size and packet direction: they demonstrate the effectiveness of these algorithms even using a small number of packets (e.g. the first four of a TCP connection).</p><p>Alshammari et Al <ref type="bibr" target="#b7">[8]</ref>, work attempted to classify/identify applications services running over SSH. They have shown the utility of two supervised learning algorithms AdaBoost and RIPPER for classifying SSH traffic without using features such as payload, IP addresses and source/destination ports. Results indicate that a detection rate of 99% and a false positive rate of 0.7% can be achieved using RIPPER. Moreover, promising preliminary results were obtained when RIPPER was employed to identify which service was running over SSH. They can recognize applications inside SSH flows such SCP and SFTP with accuracy up to 99.8% but they have performed off-line analysis on complete traces. We aim at classifying applications inside SSH flows in real time mode just analyzing the firsts 4 packets after SSH negotiation. We rely on K-means cluster analysis machines algorithm.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3">Problem Statement</head><p>In this paper, we focus on the classification of IP flows generated from network applications communicating through TCP protocols. Our objective is to recognize SSH flows out of other applications such as HTTP, FTP, POP3, etc. and, once that is accomplished, to identify which service is actually carried within the encrypted SSH tunnel. Then, we first need to define exactly what we mean for TCP flow.</p><p>Definition: A flow F is the bi-directional, ordered sequence of IP packets exchanged during a TCP connection.</p><p>Within a TCP connection, application level data are delivered as well as control packets, such as those related to three way-handshake (RFC-793) and TCP ACK packets. So, TCP flow will be composed by packets from SYN (PK 0 ) to FIN (PK N-1 ). Each flow could be seen as a sequence of (PK 0 , …., PK N-1 ), where PK j represents the j-th IP packet exchanged during TCP connection. Since we aim at classifying application flows relying on statistical features of IP packets, such as length, direction, we will characterize each TCP flow F as an ordered sequence of N-tuples (d j , l j . t j ), with 0 ≤ j ≤ N-1, where:</p><p>• d j ∈ [0,1] where 1 encodes the direction detected for SYN packet and 0 the opposite direction; • l j length of IP PK j, in bytes; The packet length ranges between a minimum and a maximum. The latter is the MTU (Maximum Transmission Unit) of the interfaces crossed by TCP connections packets. In all experiments we found out MTU=1500 bytes has never been exceeded, which is just the largest allowed MTU of most Ethernet LANs and hence most of the Internet <ref type="bibr" target="#b9">[11]</ref>. As for the minimum length, it corresponds to those carrying a TCP ACK and is denoted as l ACK in the following. It is the smallest length detectable for a TCP packet as we tested during our experiments and as RFC 793 refers, typical values ranging between 40 and 56 bytes, depending on options in the TCP and IP headers.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4">Dataset Creation</head><p>Given our aim as stated in the introduction, we assume a trained machine learning approach, exploiting cluster analysis. To that end, we need both a test and a train data set. A data set for our purposes is composed of a collection of flows in the sense defined in Section III along with metadata per flow, reporting the known application layer protocol the flow belongs to.</p><p>Knowing the application protocol each flow belongs to is needed to reliably train our algorithm. Since publicly available traces have payloads stripped off (for obvious privacy reason, e.g. CAIDA traces) and classification results cannot be checked reliably, we resorted to artificial traffic carefully generated by exploiting network premises at the University campus, the Elsag Datamat site and a private home. This way we encompass three major kinds of Internet access points: institutional, business and domestic. The controlled traffic generation is a must specifically for collecting SSH traces whose service content is known, i.e. to further label each SSH flow with a metadata reading which service it is carrying among SCP, SFTP and HTTP.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.1">Data Collection</head><p>Our data collection approach is to simulate possible network scenarios using one or more computers to capture the resulting traffic. In order to have realistic traces and technology independent implementations of SSH (version 2) protocol, we used computers with heterogeneous operative systems, namely Linux and Windows. We simulate SSH connections by connecting three client computers deployed in three different LAN to one server. As shown in figure <ref type="figure" target="#fig_0">1</ref>, client LANs and SSH server have been connected to the Internet by using different geographic links. We run the following SSH services: SCP, SFTP and HTTP over SSH. SCP and SFTP are transfer file services natively available on OpenSSH <ref type="bibr">[10]</ref>. In particular we downloaded/uploaded files from clients to server using both SCP and SFTP protocols collecting eight thousands flows. HTTP over SSH traces have been collected downloading web pages through SSH tunnels (one SSH tunnel for each HTTP session). We get four thousands of flows.</p><p>SSH connections can tunnel several TCP flows at the same time: we are working in the case where each flow is assigned by SSH a separated channel, each with specific SSH identifier. Finally we will consider flows without SSH compression feature. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.2">Data Set Creation: Pre-processing of Traces</head><p>In order to create data sets we pre-processed collected traffic traces. In particular we think that removing packets related to TCP control messages from each flow F can help us highlighting the differences among various applications. Therefore we remove from each flow F packets related to:</p><p>• Three-way handshake of TCP: PK 0=SYN , PK 1=SYN-ACK , PK 2=ACK ;</p><p>• TCP ACK packets, i.e. those packets carrying only a TCP level ACK and no payload data; • Retransmitted packets. According to TCP protocol (RFC 793) the third packet (PK 2=ACK ) of each TCP connection flow F carries an ACK. In order to remove ACK packets and TCP header length at the same time, we detect PK ACK = &lt;d ACK , l ACK &gt; of each session, where:</p><p>• d ACK is 1, because ACK direction in three way handshake is always consistent with that of SYN packet; • l ACK , is the length of packet containing TCP ACK;</p><p>We aim at identifying application within SSH tunnels. Then, we further process SSH flows by removing packets related to the SSH initial handshake (see Figure <ref type="figure" target="#fig_1">2</ref>), these packets are easily recognizable thanks to a specific pattern in terms of length and direction of packets exchanged when a new SSH channel is open. We consider the following services inside encrypted SSH tunnels: SCP, SFTP and HTTP over SSH. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5">Classification Method</head><p>In this section some details about the adopted classification system are exploited.</p><p>Basically a classification problem can be defined as follows. Let P : X → L be an unknown oriented process to be modeled, where X is the domain set and the codomain L is a label set, i.e. a set in which it is not possible (or misleading) to define an ordering function and hence any dissimilarity measure between its elements.</p><p>If P is a single value function, we will call it classification function. Let S tr and S ts be two sets of input-output pairs, namely the training set and the test set. We will call instance of a classification problem a given pair (S tr , S ts ) with the constrain S tr ∩ S ts =Ø . A classification system is a pair (M , TA i ), where TA is the training algorithm, i.e. the set of instructions responsible for generating, exclusively on the basis of S tr , a particular instance M of the classification model family M, such that the classification error of M computed on S ts will be minimized. The generalization capability, i.e. the capability to correctly classify any pattern belonging to the input space of the oriented process domain to be modeled, is for sure the most important desired feature of a classification system. From this point of view, the mean classification error on S ts can be considered as an estimate of the expected behavior of the classifier over all the possible inputs. In the following, we describe a classification system trained by an unsupervised (clustering) procedure.</p><p>When dealing with patterns belonging to the R n vectorial space we can adopt a distance measure, such as the Euclidean distance; moreover, in this case we can define the prototype of the cluster as the centroid (the mean vector) of all the patterns in the cluster, thanks to the algebraic structure defined in R n . Consequently, the distance between a given pattern x i and a cluster C k can be easily defined as the Euclidean distance d(x i ; µ k ) where µ k is the centroid of the pattern belonging to C k :</p><formula xml:id="formula_0">∑ ∈ = k i C x i k k x m 1 µ</formula><p>A direct way to synthesize a classification model on the basis of a training set S tr consists in partitioning the patterns in the input space (discarding the class label information) by a clustering algorithm (in our case, by the K-means). Successively, each cluster is labeled by the most frequent class among its patterns. Thus, a classification model is a set of labeled clusters (centroids); note that more than one cluster can be associated with the same label, i.e. a class can be represented by more than one cluster. Assuming to represent a floating point number with four bytes, the amount of memory needed to store a classification model is K • (4 • n + 1) bytes, where n is the input space dimension and assuming to code class labels with one byte. An unlabeled pattern x is classified by determining the closest centroid µ i (and thus the closest cluster C i ) and by labeling x with the same class label associated with C i . It is important to underline that, since the initialization step of the K-Means is not deterministic, in order to compute a precise estimation of the performance of the classification model on the test set S ts , the whole algorithm must be run several times, averaging the classification errors on S ts yielded by the different classification models obtained in each run.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6">Experimental Results</head><p>By classifying plain SSH flows with our approach, we obtained results shown in table <ref type="table" target="#tab_0">1</ref>. We tried out processing all possible combination of packets up to ten packets after end of SSH negotiation (i.e. the initial common handshake phase, same in all SSH flows). As shown in Table <ref type="table" target="#tab_0">1</ref>, we tested different patterns representations, increasing the considered number of packets for each flow in order to identify which one contains more information to emphasize difference among applications. As shown in table 1, the K-means based algorithm yields very interesting results in terms of identification of encoded applications. We can detect different applications with accuracy up to 99.8 for HTTP over SSH protocol, just analyzing third and fourth packets after SSH negotiation. We can notice that analyzing also the fifth packet does not improve significantly accuracy. Moreover, increasing the considered number of packets means introducing delay for real time recognition.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="7">Conclusion</head><p>In this paper we present a model that could be useful to address the problem of traffic classification. To this end, we use only (poor) information available at network layer, namely packets size, directions and inter-arrival times. Our classification system based on cluster analysis can classify in real time encoded SSH traffic flows, overcoming actual limits of deep packet inspection. Our system does not compromise privacy of network users because to identify encoded SSH tunnel payload information are not inspected.</p><p>We are able to identify the nature of each SSH tunnel obtaining accuracy up to 99.88% in classifying HTTP over SSH just analyzing the third and fourth packet after the end of the SSH negotiation phase. The same encouraging results have been obtained by classifying SCP (up to 99.3) and SFTP (up to 99.05) applications. Further works should be performed in order to improve results for classification of download and upload flows for SCP and SFTP. Moreover, it will be necessary to investigate the applicability of the approach on wider application dataset.</p><p>Currently on-going work includes extension of the classification tool to more powerful classification algorithms, well beyond k-means; in this respect, k-means shall be regarded as a first use attempt, to verify the soundness of our approach, before proceeding to more complex yet reliable classification algorithms.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Fig. 1 :</head><label>1</label><figDesc>Fig. 1: Platform used to generate SSH traffic: SSH server is inside the University campus network; clients are at University, Elsag Datamat and a private home premise, respectively.</figDesc><graphic coords="5,217.46,214.18,187.30,105.11" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Fig. 2 :</head><label>2</label><figDesc>Fig. 2: Pre-processing of SSH flows</figDesc><graphic coords="6,205.34,138.47,211.66,128.87" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head>Table 1 .</head><label>1</label><figDesc>Encoded SSH applications flows   </figDesc><table><row><cell></cell><cell>HTTP</cell><cell></cell></row><row><cell>1° 2° 3° 4° 5°</cell><cell cols="2">over SSH scp</cell><cell>sftp</cell></row><row><cell cols="2">0 0 1 1 1 99.80%</cell><cell>98.93%</cell><cell>99.75%</cell></row><row><cell cols="2">0 0 1 1 0 99.88%</cell><cell>99.30%</cell><cell>99.05%</cell></row></table></figure>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">BLINC: Multilevel traffic classification in the dark</title>
		<author>
			<persName><forename type="first">K</forename><surname>Karagiannis</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Papagiannaki</surname></persName>
		</author>
		<author>
			<persName><surname>Faloutsos</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. of ACM SIGCOMM 2005</title>
				<meeting>of ACM SIGCOMM 2005<address><addrLine>Philadelphia, PA, USA</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2005-08">August 2005</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Traffic Classification through Simple Statistical Fingerprinting</title>
		<author>
			<persName><forename type="first">M</forename><surname>Crotti</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Dusi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Gringoli</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Salgarelli</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">ACM SIGCOMM Computer Communication Review</title>
		<imprint>
			<biblScope unit="volume">37</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="5" to="16" />
			<date type="published" when="2007-01">Jan. 2007</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">On Inferring Application Protocol Behaviors in Encrypted Network Traffic</title>
		<author>
			<persName><forename type="first">C</forename><surname>Wright</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Monrose</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Masson</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Special issue on Machine Learning for Computer Security</title>
				<imprint>
			<date type="published" when="2006">2006</date>
			<biblScope unit="volume">7</biblScope>
			<biblScope unit="page" from="2745" to="2769" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">Internet traffic classification using Bayesian analysis techniques</title>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">W</forename><surname>Moore</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Zuev</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">ACM SIGMETRICS 2005</title>
				<meeting><address><addrLine>Banff, Alberta, Canada</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2005-06">June 2005</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">Flow clustering using machine learning techniques</title>
		<author>
			<persName><forename type="first">A</forename><surname>Mcgregor</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Hall</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Lorier</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Brunskill</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">PAM 2004, Antibes Juan-les-Pins</title>
				<meeting><address><addrLine>France</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2004-04">April 2004</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Automated traffic classification and application identification using machine learning</title>
		<author>
			<persName><forename type="first">S</forename><surname>Zander</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Nguyen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Armitage</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">LCN 2005</title>
				<meeting><address><addrLine>Sydney, Australia</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2005-11">November 2005</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Early Application Identification</title>
		<author>
			<persName><forename type="first">L</forename><surname>Bernaille</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Teixeira</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Salamatian</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">proceedings of CoNEXT</title>
				<meeting>CoNEXT</meeting>
		<imprint>
			<date type="published" when="2006-12">December 2006</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">A Flow Based Approach For Ssh Traffic Detection</title>
		<author>
			<persName><forename type="first">R</forename><surname>Alshammari</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Nur Zincir-Heywood</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">ISIC. IEEE International Conference on</title>
				<imprint>
			<date type="published" when="2007">2007</date>
		</imprint>
	</monogr>
	<note>Systems, Man and Cybernetics</note>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">A Survey on Internet Traffic Identification</title>
		<author>
			<persName><forename type="first">A</forename><surname>Callado</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Kamienski</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Szabo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Gero</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Kelner</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Fernandes</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Sadok</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Communications Surveys &amp; Tutorials</title>
		<imprint>
			<biblScope unit="volume">11</biblScope>
			<biblScope unit="issue">3</biblScope>
			<biblScope unit="page">3</biblScope>
			<date type="published" when="2009">Quarter 2009</date>
		</imprint>
	</monogr>
	<note>IEEE</note>
</biblStruct>

<biblStruct xml:id="b9">
	<monogr>
		<title/>
		<author>
			<persName><surname>Mtu</surname></persName>
		</author>
		<imprint>
			<biblScope unit="volume">879</biblScope>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
