64 research outputs found

    Unified Internet Messaging

    Get PDF
    As telephony services, mobile services and internet services continue to converge, the prospect of providing Unified Messaging and even Unified Communications becomes increasingly achievable. This paper discusses the growing importance of IP-based networks to Unified Messaging developments and examines some of the key services and protocols that are likely to make Unified Messaging more widely available. In this initial paper, we limit ourselves initially to the unification of text-based messaging using SMS and Email. The approach we make is based on the existing Internet Email framework but will take cognisance of the need to add voice and other non-text based messaging and communications at a later stage. Ultimately, the research project aims to build a working prototype of a generic messaging model that works for both non realtime and real-time communications. This model will provide a framework into which existing and future messaging protocols can be plugged. This paper originated from an applied research project which examined the integration possibilities for various messaging and communications protocol

    A security analysis of email communications

    Get PDF
    The objective of this report is to analyse the security and privacy risks of email communications and identify technical countermeasures capable of mitigating them effectively. In order to do so, the report analyses from a technical point of view the core set of communication protocols and standards that support email communications in order to identify and understand the existing security and privacy vulnerabilities. On the basis of this analysis, the report identifies and analyses technical countermeasures, in the form of newer standards, protocols and tools, aimed at ensuring a better protection of the security and privacy of email communications. The practical implementation of each countermeasure is evaluated in order to understand its limitations and identify potential technical and organisational constrains that could limit its effectiveness in practice. The outcome of the above mentioned analysis is a set of recommendations regarding technical and organisational measures that when combined properly have the potential of more effectively mitigating the privacy and security risks of today's email communications.JRC.G.6-Digital Citizen Securit

    Federal Emergency Management Information System (FEMIS) Bill of Materials (BOM) for FEMIS version 1.4.5

    Full text link

    Applications of internet technology for requirements elicitation

    Get PDF
    During the Requirements Elicitation part of a project various stakeholders need to be able to communicate their requirements to the developers, and the developers need to be able communicate their understanding back to the stakeholders. Communication between the various members of the project is the key factor during the Requirements Elicitation part of a project. Easing communications between stakeholders and developers makes the process of eliciting requirement easier, leading to better requirements specification and eventually a better product. The Requirements Elicitation Process through Internet (REPI) web site has been designed and implemented to explore this idea. The prototype version of REPI guides project members through the elicitation phase using the Software Engineering Institute\u27s framework for Requirements Elicitation. The REPI web site forces stakeholders to explicitly describe the requirements and encourage early discussion between stakeholders and developers. This decreases the likelihood of misunderstood requirements, leading to better requirements specification

    Derivation of the required elements for a definition of the term middleware

    Get PDF
    Thirteen contemporary definitions of Middleware were analyzed. The definitions agree that any software that can do the following should be classified as Middleware (1) provide service that provides transparent application-to-application interaction across the network, (2) act as a service provider for distributed applications, and (3) provide services that are primarily used by distributed applications (e.g., RPCs, ORBs, Directories, name-resolution services, etc.) Most definitions agree that Middleware is that level of software required to achieve platform, location, and network transparency. There is some discrepancy about the OSI levels at which middleware operates. The majority of definitions limit it to levels 5, 6, and 7. Additionally, almost half of the definitions do not include database transparency as something achieved by Middleware, perhaps due to the ambiguous classification of ODBC and JDBC as software. Assuming that the number of times a service is mentioned, the majority of the definitions rank services associated with legal access to an application as core to Middleware, along with valid, standardized APIs for application development as core to the definition of middleware

    Pervasive Messaging

    Get PDF
    Pervasive messaging is the part of pervasive computing that enables users to communicate with each other. Many of today's electronic messaging systems have their own distinct merits and peculiarities. Pervasive messaging will have to shield the user from these differences. In this paper, we introduce a taxonomy for electronic messaging systems, providing a uniform way to analyze, compare, and discuss electronic messaging systems. With this taxonomy, we analyze the current practice, demonstrating its shortfalls. To overcome these shortfalls, we introduce a novel messaging model: The Unified Messaging System. This system can, in fact, mimic any electronic messaging system, thus providing powerful unified messaging

    Internet Message Access Protocol - Version 4rev1

    Full text link

    Towards the definition of a quality model for mail servers

    Get PDF
    The paper presents an approach for building a Mail Server Quality Model, based on the ISO/IEC software quality standard. We start by defining the mail system domain to be used as general framework and the relevant technologies involved. Then a general overview of the ISO/IEC standard is given. The basic steps, the relevant considerations and criteria used to select the appropriated subcharacteristics and quality attributes are also presented. The selected attributes are categorized under the six ISO/IEC quality characteristics conforming the model. Finally some case studies requirements and two commercial mail server tools are used to evaluate the model.Postprint (published version

    Application of Multiprotocol Medical Imaging Communications and an Extended DICOM WADO Service in a Teleradiology Architecture

    Get PDF
    Multiprotocol medical imaging communication through the Internet is more flexible than the tight DICOM transfers. This paper introduces a modular multiprotocol teleradiology architecture that integrates DICOM and common Internet services (based on web, FTP, and E-mail) into a unique operational domain. The extended WADO service (a web extension of DICOM) and the other proposed services allow access to all levels of the DICOM information hierarchy as opposed to solely Object level. A lightweight client site is considered adequate, because the server site of the architecture provides clients with service interfaces through the web as well as invulnerable space for temporary storage, called as User Domains, so that users fulfill their applications' tasks. The proposed teleradiology architecture is pilot implemented using mainly Java-based technologies and is evaluated by engineers in collaboration with doctors. The new architecture ensures flexibility in access, user mobility, and enhanced data security
    corecore