R. Atkinson

Bio: R. Atkinson is an academic researcher from Extreme Networks. The author has contributed to research in topics: Identifier/Locator Network Protocol & The Internet. The author has an hindex of 17, co-authored 33 publications receiving 6379 citations. Previous affiliations of R. Atkinson include Research Triangle Park.

Mobility as an integrated service through the use of naming

Abstract: As Mobile IP is deployed, so the requirements for its deployment evolve, reflecting the actual use of IP networks today. This includes the ability to use Mobile IP with IPsec, NATs and multi-homed networks. Furthermore, new requirements arise as people start to use IP in scenarios where the whole network is mobile (e.g. military networks), and where edge-networks may not be IP-enabled (e.g. sensor networks), but there is a requirement to interoperate across an IP network. In all these cases, rather than engineering retro-fits, creating an increasingly complex network landscape with possible unforeseen feature interactions and dependencies, we would prefer an integrated architectural solution. We present, from our ongoing work, a solution that would seem to meet all these needs, through a modified use of naming and addressing. Our proposal is incrementally deployable and existing core network routers & routing protocols need not change.

Integrating challenged networks

Abstract: For a comprehensive information coverage across theatre, it is necessary to integrate many different sources of data which are likely to use protocols specific to a specialised purpose. For example, resource-constrained or challenged networks such as sensor systems and MANET systems, using their own protocols, may be used in conjunction with other Internet Protocol (IP) based communication and need to be integrated into the GIG. While such integration may be possible today, the engineering is complex and the resultant system may be difficult to configure and maintain, as well as being brittle when systems changes or reconfiguration is required. Furthermore, when security and identity issues are considered, the additional overhead for enabling integration within the context of sensor systems and MANETs raises challenging technology issues. Based on our ongoing work, we present a potential solution which organises such systems based on identity and location, but allows integration with Internet-wide communication.

Harmonised resilience, security and mobility capability for IP

Abstract: Military communications currently require secure end-to-end, resilient connectivity via multi-homed connections, and need to support both mobile hosts and mobile networks. Today, such functions are possible to some degree, but the functions are not harmonised. Standards that support these functions were designed independently and implemented in isolation. So, achieving converged capabilities for optimal communications in forward operating areas is a technical challenge, and results in a complex network landscape which is likely to be difficult to operate and manage, and brittle under failure conditions. From our ongoing work, we present a new naming approach and use this to formulate a proposal to provide the following capability harmoniously: (a) multi-homed connectivity for traffic engineering and resilience; (b) true end-to-end network-layer security with high compatibility with the HAIPE architecture; (c) support for mobile hosts and mobile networks. Our approach is backwards compatible with IPv6 network equipment (existing IPv6 backbones can be used), and is also incrementally deployable.

Site-controlled secure multi-homing and traffic engineering for IP

Abstract: Site multi-homing is an important capability in modern military networks. Resilience of a site is greatly enhanced when it has multiple upstream connections to the Global Information Grid, including the global Internet. Similarly, the ability to provide traffic engineering for a site can be important in reducing delays and packet loss over low-bandwidth and/or high-delay uplinks. Current approaches to site multi-homing and site traffic engineering (a) require assistance from a trusted network service provider; (b) inject significant additional routing information into the global Internet routing system. This approach reduces flexibility, does not scale and is a widespread concern today. The proposed Identifier-Locator Network Protocol (ILNP) offers backward compatible extensions for IPv6 to enable a site to (a) use multiple routing prefixes concurrently, without needing to advertise these more-specific site prefixes upstream to the site's service providers; (b) enables edge-site controlled traffic engineering and localised addressing, without breaking end-to-end connectivity. This feature combination provides both multi-homing and traffic engineering capabilities without any adverse impact on the routing system and does not require anything more than unicast routing capability in the provider network. ILNP enables concurrent multi-path transmission for a flow, without requiring multicast routing, to increase flow resilience to path interruptions. This technique has a secondary security benefit of reducing the risk of an adversary successfully blocking an ILNP flow via a Denial-of-Service attack on any single path or single link.

ICMP Locator Update Message for the Identifier-Locator Network Protocol for IPv4 (ILNPv4)

Abstract: This note defines an experimental ICMP message type for IPv4 used with the Identifier-Locator Network Protocol (ILNP). ILNP is an experimental, evolutionary enhancement to IP. The ICMP message defined herein is used to dynamically update Identifier/Locator bindings for an existing ILNP session. This is a product of the IRTF Routing Research Group. This document defines an Experimental Protocol for the Internet community.

Systems and Methods for Secure Transaction Management and Electronic Rights Protection

Abstract: PROBLEM TO BE SOLVED: To solve the problem, wherein it is impossible for an electronic content information provider to provide commercially secure and effective method, for a configurable general-purpose electronic commercial transaction/distribution control system. SOLUTION: In this system, having at least one protected processing environment for safely controlling at least one portion of decoding of digital information, a secure content distribution method comprises a process for encapsulating digital information in one or more digital containers; a process for encrypting at least a portion of digital information; a process for associating at least partially secure control information for managing interactions with encrypted digital information and/or digital container; a process for delivering one or more digital containers to a digital information user; and a process for using a protected processing environment, for safely controlling at least a portion of the decoding of the digital information. COPYRIGHT: (C)2006,JPO&NCIPI

RTP: A Transport Protocol for Real-Time Applications

Abstract: This memorandum describes RTP, the real-time transport protocol. RTP provides end-to-end network transport functions suitable for applications transmitting real-time data, such as audio, video or simulation data, over multicast or unicast network services. RTP does not address resource reservation and does not guarantee quality-of-service for real-time services. The data transport is augmented by a control protocol (RTCP) to allow monitoring of the data delivery in a manner scalable to large multicast networks, and to provide minimal control and identification functionality. RTP and RTCP are designed to be independent of the underlying transport and network layers. The protocol supports the use of RTP-level translators and mixers.

SIP: Session Initiation Protocol

Abstract: This document describes Session Initiation Protocol (SIP), an application-layer control (signaling) protocol for creating, modifying, and terminating sessions with one or more participants. These sessions include Internet telephone calls, multimedia distribution, and multimedia conferences.

Security Architecture for the Internet Protocol

Abstract: This document describes an updated version of the "Security Architecture for IP", which is designed to provide security services for traffic at the IP layer. This document obsoletes RFC 2401 (November 1998). [STANDARDS-TRACK]

RPL: IPv6 Routing Protocol for Low-Power and Lossy Networks

Abstract: Low-Power and Lossy Networks (LLNs) are a class of network in which both the routers and their interconnect are constrained. LLN routers typically operate with constraints on processing power, memory, and energy (battery power). Their interconnects are characterized by high loss rates, low data rates, and instability. LLNs are comprised of anything from a few dozen to thousands of routers. Supported traffic flows include point-to-point (between devices inside the LLN), point- to-multipoint (from a central control point to a subset of devices inside the LLN), and multipoint-to-point (from devices inside the LLN towards a central control point). This document specifies the IPv6 Routing Protocol for Low-Power and Lossy Networks (RPL), which provides a mechanism whereby multipoint-to-point traffic from devices inside the LLN towards a central control point as well as point-to- multipoint traffic from the central control point to the devices inside the LLN are supported. Support for point-to-point traffic is also available. [STANDARDS-TRACK]