scispace - formally typeset
Search or ask a question
Author

R. Atkinson

Other affiliations: Research Triangle Park
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.

Papers
More filters
Proceedings ArticleDOI
23 Oct 2006
TL;DR: This work proposes a coalition-based, multi-homed approach leveraging both local-area and wide-area connectivity, improving both the flexibility and robustness of communication, without conflicting with the security policy of sensitive communication.
Abstract: At present, military communications within battlefields are very restricted, both by policy and due to technology limitations. In Southwest Asia today, there are needlessly long and complex communications paths, often involving multiple relays and use of constrained-bandwidth MILSATCOM back-haul outside the theatre, when nearby forces could communicate directly via existing interoperable radios. This is a current problem for NATO and Coalition forces. The current Internet Protocol suite lacks core support for mobility, scalable support for multi-homed nodes, and does not provide the capabilities needed for optimal communications in forward operating areas. We propose a coalition-based, multi-homed approach lever-aging both local-area and wide-area connectivity, improving both the flexibility and robustness of communication, without conflicting with the security policy of sensitive communication. The Coalition Peering Domain (CPD), is a distributed, self-configuring architecture that supports the secure, collaborative networking relationships needed to provide this flexibility and robustness. The CPD facilitates the inter-connection of cooperating, but administratively separate, network segments. The CPD exploits multi-homed and multi-path communication to better-utilise all available connectivity. The Identifier-Locator Network Protocol (ILNP) provides native support for improved scalability in multi-homing and mobility, while easing use of network layer security and allowing inter-operation across different administrative domains. Our approach is compatible with current work in Mobile Ad-Hoc Networking (MANET). ILNP has excellent compatibility with IPv6: existing IPv6 backbone networks do not require any modification to carry ILNP traffic natively. There are practical, realistic and deployable engineering solutions to realise the CPD and ILNP within the framework of IPv6.

11 citations

01 Nov 2012
TL;DR: This document defines an Address Resolution Protocol (ARP) extension to support the Identifier-Locator Network Protocol for IPv4 (ILNPv4).
Abstract: This document defines an Address Resolution Protocol (ARP) extension to support the Identifier-Locator Network Protocol for IPv4 (ILNPv4). ILNP is an experimental, evolutionary enhancement to IP. This document is a product of the IRTF Routing Research Group. This document defines an Experimental Protocol for the Internet community.

11 citations

Proceedings ArticleDOI
01 Oct 2012
TL;DR: A VM mobility approach that enables datacentre operators to directly and unilaterally provide and control intra-site and wide-area VM mobility is described and several use cases with different degrees of location transparency are presented.
Abstract: Global Information Grid (GIG) operations would benefit greatly from improved support for virtual machines (VMs) that can migrate not only between physical devices within a datacentre, but also between physical devices located on different continents, while maintaining their existing IP communications sessions. Such VM migration can enable improvements with: CPU load-balancing, network traffic-engineering, distributed denial of service (DDoS) mitigation, fault-tolerance, and resilience. Existing migration approaches often require complex network configuration and management, may often require use of expensive proprietary technologies, and also often require active cooperation from upstream service providers. We describe a VM mobility approach that enables datacentre operators to directly and unilaterally provide and control intra-site and wide-area VM mobility. We present several use cases with different degrees of location transparency. Our mechanism is based on a new naming approach which has been recommended for progression within the IETF.

9 citations

01 Jul 2009
TL;DR: This document describes an optional method for encoding explicit packet Sensitivity Labels on IPv6 packets that is intended for use only within Multi-Level secure (MLS) networking environments that are both trusted and trustworthy.
Abstract: This document describes an optional method for encoding explicit packet Sensitivity Labels on IPv6 packets. It is intended for use only within Multi-Level secure (MLS) networking environments that are both trusted and trustworthy.

8 citations

27 Jul 2011
TL;DR: This note specifies an experimental ICMPv6 message type used with the Identifier-Locator Network Protocol (ILNP) used to dynamically update Identifier/Locator bindings for an existing ILNP session.
Abstract: This note specifies an experimental ICMPv6 message type used with the Identifier-Locator Network Protocol (ILNP). This message is used to dynamically update Identifier/Locator bindings for an existing ILNP session. This is a product of the IRTF Routing RG.

4 citations


Cited by
More filters
Patent
30 Sep 2010
TL;DR: In this article, the authors proposed a secure content distribution method for a configurable general-purpose electronic commercial transaction/distribution control system, which includes a process for encapsulating digital information in one or more digital containers, a process of encrypting at least a portion of digital information, a protocol for associating at least partially secure control information for managing interactions with encrypted digital information and/or digital container, and a process that delivering one or multiple digital containers to a digital information user.
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

7,643 citations

01 Jul 2003
TL;DR: RTP provides end-to-end network transport functions suitable for applications transmitting real-time data over multicast or unicast network services and is augmented by a control protocol (RTCP) to allow monitoring of the data delivery in a manner scalable to large multicast networks.
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.

7,183 citations

Book ChapterDOI
01 Jun 2002
TL;DR: Session Initiation Protocol (SIP) as discussed by the authors is an application layer control (signaling) protocol for creating, modifying, and terminating sessions with one or more participants, such as Internet telephone calls, multimedia distribution, and multimedia conferences.
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.

5,482 citations

01 Aug 1995
TL;DR: 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, and obsoletes RFC 2401 (November 1998).
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]

3,455 citations

ReportDOI
01 Mar 2012
TL;DR: 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 points to the devices insideThe LLN are supported.
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]

2,551 citations