James Kempf
James Kempf has a total of 16 co-authors. Here are the top co-authors by number of shared publications:
- Jonathan Wood
DoCoMo Communications Laboratories USA, Inc., 3240 Hillview Avenue, Palo Alto, CA 94304-1201, USA
2 shared publications - Pekka Nikander
DoCoMo Euro-Labs F. Dupont CELAR
2 shared publications - Ajoy Singh
Motorola
1 shared publication - Alf Zugenmaier
DoCoMo Communications Laboratories Europe GmbH, Landsberger Strasse 312, D-80687 Munich, Germany
1 shared publication - Anand Prasad
DoCoMo Communications Laboratories Europe GmbH, Landsberger Strasse 312, D-80687 Munich, Germany
1 shared publication - Atsushi Takeshita
NTT DoCoMo
1 shared publication
Latest Publications
- Open Access
- 1 June 2008
- Published by RFC Editor
Distributing a Symmetric Fast Mobile IPv6 (FMIPv6) Handover Key Using SEcure Neighbor Discovery (SEND)
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
- 1 June 2008
- Published by RFC Editor
Open AccessDistributing a Symmetric Fast Mobile IPv6 (FMIPv6) Handover Key Using SEcure Neighbor Discovery (SEND)
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
- 1 August 2007
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 809-816
Travelling without Moving: 802.11 Access Points backed by Secure NETLMM
In network-based localized mobility management (NETLMM), a mobile node is not involved in signalling related to mobility support, and keeps the same IP address after handoff from one link to another. The mobile node's current access router acts as a mobility access gateway by sending Proxy Local Binding Updates to the local mobility anchor on behalf of the mobile node. Due to some properties of the NETLMM domain, implementing it efficiently using IEEE 802.11 radio access networks is not straightforward. This paper presents the challenges involved with such an implementation, presents solutions to them, and analyze the overall performance of the complete system.
- 1 August 2007
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 809-816
Travelling without Moving: 802.11 Access Points backed by Secure NETLMM
In network-based localized mobility management (NETLMM), a mobile node is not involved in signalling related to mobility support, and keeps the same IP address after handoff from one link to another. The mobile node's current access router acts as a mobility access gateway by sending Proxy Local Binding Updates to the local mobility anchor on behalf of the mobile node. Due to some properties of the NETLMM domain, implementing it efficiently using IEEE 802.11 radio access networks is not straightforward. This paper presents the challenges involved with such an implementation, presents solutions to them, and analyze the overall performance of the complete system.
- Open Access
- 1 April 2007
- Published by RFC Editor
Security Threats to Network-Based Localized Mobility Management (NETLMM)
This document discusses security threats to network-based localized mobility management. Threats may occur on two interfaces: the interface between a localized mobility anchor and a mobile access gateway, as well as the interface between a mobile access gateway and a mobile node. Threats to the former interface impact the localized mobility management protocol itself.
- 1 April 2007
- Published by RFC Editor
Open AccessSecurity Threats to Network-Based Localized Mobility Management (NETLMM)
This document discusses security threats to network-based localized mobility management. Threats may occur on two interfaces: the interface between a localized mobility anchor and a mobile access gateway, as well as the interface between a mobile access gateway and a mobile node. Threats to the former interface impact the localized mobility management protocol itself.
- 15 June 2006
- Published by Springer Nature in Wireless Networks
- Vol. 13 (4) , 431-445
Real-time traffic support in heterogeneous mobile networks
- 15 June 2006
- Published by Springer Nature in Wireless Networks
- Vol. 13 (4) , 431-445
Real-time traffic support in heterogeneous mobile networks
- 30 December 2005
- Published by Springer Nature in Wireless Networks
- Vol. 12 (3) , 321-344
Link Synchronous Mobile IPv4 Handover Algorithms
- 30 December 2005
- Published by Springer Nature in Wireless Networks
- Vol. 12 (3) , 321-344
Link Synchronous Mobile IPv4 Handover Algorithms
- Open Access
- 1 July 2005
- Published by RFC Editor
Instructions for Seamoby and Experimental Mobility Protocol IANA Allocations
The Seamoby Candidate Access Router Discovery (CARD) protocol and the Context Transfer Protocol (CXTP) are experimental protocols designed to accelerate IP handover between wireless access routers. These protocols require IANA allocations for ICMP type and options, Stream Control Transmission Protocol (SCTP) Payload Protocol Identifiers, port numbers, and registries for certain formatted message options. This document contains instructions to IANA about which allocations are required for the Seamoby protocols. The ICMP subtype extension format for Seamoby has been additionally designed so that it can be utilized by other experimental mobility protocols, and the SCTP port number is also available for other experimental mobility protocols.
- 1 July 2005
- Published by RFC Editor
Open AccessInstructions for Seamoby and Experimental Mobility Protocol IANA Allocations
The Seamoby Candidate Access Router Discovery (CARD) protocol and the Context Transfer Protocol (CXTP) are experimental protocols designed to accelerate IP handover between wireless access routers. These protocols require IANA allocations for ICMP type and options, Stream Control Transmission Protocol (SCTP) Payload Protocol Identifiers, port numbers, and registries for certain formatted message options. This document contains instructions to IANA about which allocations are required for the Seamoby protocols. The ICMP subtype extension format for Seamoby has been additionally designed so that it can be utilized by other experimental mobility protocols, and the SCTP port number is also available for other experimental mobility protocols.
- Open Access
- 1 March 2005
- Published by RFC Editor
SEcure Neighbor Discovery (SEND)
IPv6 nodes use the Neighbor Discovery Protocol (NDP) to discover other nodes on the link, to determine their link-layer addresses to find routers, and to maintain reachability information about the paths to active neighbors. If not secured, NDP is vulnerable to various attacks. This document specifies security mechanisms for NDP. Unlike those in the original NDP specifications, these mechanisms do not use IPsec.
- 1 March 2005
- Published by RFC Editor
Open AccessSEcure Neighbor Discovery (SEND)
IPv6 nodes use the Neighbor Discovery Protocol (NDP) to discover other nodes on the link, to determine their link-layer addresses to find routers, and to maintain reachability information about the paths to active neighbors. If not secured, NDP is vulnerable to various attacks. This document specifies security mechanisms for NDP. Unlike those in the original NDP specifications, these mechanisms do not use IPsec.
- 1 June 2004
- Published by Springer Nature in Wireless Personal Communications
- Vol. 29 (3-4) , 389-414
Mobile IPv6 Security
- 1 June 2004
- Published by Springer Nature in Wireless Personal Communications
- Vol. 29 (3-4) , 389-414
Mobile IPv6 Security