BRN-051030-8 - Revision history

Jeschke: Reverted edit of 1145731816, changed back to last version by Jon

2006-04-23T08:51:31Z

Reverted edit of 1145731816, changed back to last version by Jon

New page

=Title=
* VoIP in Wireless Multi-Hop Networks
* Assigned to: Jon Kowal

=Abstract=
* Voice over Internet Protocol (VoIP) communication requires some kind of quality of service. Latency and network throughput have to fullfill some minimum requirements.
* What are the requirements and to what extends are current mesh networks able to meet these requirements? To learn the requirements, different VoIP technologies have to be considered. The analysis of mesh network capabilities in terms of how to assure these requirements is the main focus of this work. Hints towards the devolopment of new routing technologies or the extension of existing VoIP technology (e.g. a SIP extension) MAY result from this work, development of new VoIP technology is NOT part of it.
* If successful, this contribution will allow to give a statement whether VoIP in current mesh networks is possible, and if not, what are the key problems to take care of, when developing future mesh network technologies.

=Literature=
* List of standard/basic papers a ''person skilled in the art'' should have read.
** RFC 3261 (Session Initiation Protocol, SIP)
** RFC 3489 (Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs), STUN)
* List of relevant conferences, standards organizations to follow up with.

=Competition=
* competing technologies, companies/research teams

=Personal Knowledge Base=
* Description of your work / your approach
* Results so far (reports, experiments downloadable software, ...)
== Analysis of current VoIP technologies ==
=== SIP ===
* [http://www.sipcenter.com/sip.nsf/html/IETF+SIP+RFCs+and+Drafts IETF SIP RFCs and Drafts]

=== Skype ===
* Skype is more of an application that makes use of a peer-to-peer protocol, and differenect codecs.
* [http://skype.nexxen.cz/dokumentace/public/SkypeProtocol/html/SkypeProtocol.htm An Analysis of the Skype Peer-to-Peer Internet Telephony Protocol]

=Project Plan: Working Packages=
* List of tasks, milestones with deadlines, and deliverables

==See Also==
For a list of currently available thesis topics see [http://sar.informatik.hu-berlin.de/research/thesis_proposals.htm]

Jon at 00:06, 13 February 2006

2006-02-13T00:06:01Z

← Older revision		Revision as of 00:06, 13 February 2006
Line 11:		Line 11:
	* List of standard/basic papers a ''person skilled in the art'' should have read.		* List of standard/basic papers a ''person skilled in the art'' should have read.
	** RFC 3261 (Session Initiation Protocol, SIP)		** RFC 3261 (Session Initiation Protocol, SIP)
	** RFC 3489 (Simple Traversal of User Datagram Protocol Through Network Address Translators (NATs), STUN)		** RFC 3489 (Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs), STUN)
	* List of relevant conferences, standards organizations to follow up with.		* List of relevant conferences, standards organizations to follow up with.

Line 23:		Line 23:
	=== SIP ===		=== SIP ===
	* [http://www.sipcenter.com/sip.nsf/html/IETF+SIP+RFCs+and+Drafts IETF SIP RFCs and Drafts]		* [http://www.sipcenter.com/sip.nsf/html/IETF+SIP+RFCs+and+Drafts IETF SIP RFCs and Drafts]

			=== Skype ===
			* Skype is more of an application that makes use of a peer-to-peer protocol, and differenect codecs.
			* [http://skype.nexxen.cz/dokumentace/public/SkypeProtocol/html/SkypeProtocol.htm An Analysis of the Skype Peer-to-Peer Internet Telephony Protocol]

	=Project Plan: Working Packages=		=Project Plan: Working Packages=

Jon at 23:34, 12 February 2006

2006-02-12T23:34:17Z

← Older revision		Revision as of 23:34, 12 February 2006
Line 1:		Line 1:
	=Title=		=Title=
			* VoIP in Wireless Multi-Hop Networks
	* Short title of your assigned task
	* Assigned to: ~~''your~~ ~~name''~~		* Assigned to: Jon Kowal

	=Abstract=		=Abstract=
			* Voice over Internet Protocol (VoIP) communication requires some kind of quality of service. Latency and network throughput have to fullfill some minimum requirements.
	* Problem statement.
			* What are the requirements and to what extends are current mesh networks able to meet these requirements? To learn the requirements, different VoIP technologies have to be considered. The analysis of mesh network capabilities in terms of how to assure these requirements is the main focus of this work. Hints towards the devolopment of new routing technologies or the extension of existing VoIP technology (e.g. a SIP extension) MAY result from this work, development of new VoIP technology is NOT part of it.
	* What do you want to achieve? What is NOT inside the scope of your work?
			* If successful, this contribution will allow to give a statement whether VoIP in current mesh networks is possible, and if not, what are the key problems to take care of, when developing future mesh network technologies.
	* If successful, what contribution will your work make (scientific, technical)?

	=Literature=		=Literature=
	* List of standard/basic papers a ''person skilled in the art'' should have read.		* List of standard/basic papers a ''person skilled in the art'' should have read.
			** RFC 3261 (Session Initiation Protocol, SIP)
			** RFC 3489 (Simple Traversal of User Datagram Protocol Through Network Address Translators (NATs), STUN)
	* List of relevant conferences, standards organizations to follow up with.		* List of relevant conferences, standards organizations to follow up with.

Line 18:		Line 20:
	* Description of your work / your approach		* Description of your work / your approach
	* Results so far (reports, experiments downloadable software, ...)		* Results so far (reports, experiments downloadable software, ...)
			== Analysis of current VoIP technologies ==
			=== SIP ===
			* [http://www.sipcenter.com/sip.nsf/html/IETF+SIP+RFCs+and+Drafts IETF SIP RFCs and Drafts]

	=Project Plan: Working Packages=		=Project Plan: Working Packages=

Jpr at 17:17, 6 December 2005

2005-12-06T17:17:00Z

New page

=Title=
* Short title of your assigned task
* Assigned to: ''your name''

=Abstract=
* Problem statement.
* What do you want to achieve? What is NOT inside the scope of your work?
* If successful, what contribution will your work make (scientific, technical)?

=Literature=
* List of standard/basic papers a ''person skilled in the art'' should have read.
* List of relevant conferences, standards organizations to follow up with.

=Competition=
* competing technologies, companies/research teams

=Personal Knowledge Base=
* Description of your work / your approach
* Results so far (reports, experiments downloadable software, ...)

=Project Plan: Working Packages=
* List of tasks, milestones with deadlines, and deliverables

==See Also==
For a list of currently available thesis topics see [http://sar.informatik.hu-berlin.de/research/thesis_proposals.htm]