The Experts below are selected from a list of 8388 Experts worldwide ranked by ideXlab platform

Dirk Grunwald - One of the best experts on this subject based on the ideXlab platform.

  • enhancing location privacy in wireless lan through disposable Interface Identifiers a quantitative analysis
    Mobile Networks and Applications, 2005
    Co-Authors: Marco Gruteser, Dirk Grunwald
    Abstract:

    The recent proliferation of wireless local area networks (WLAN) has introduced new location privacy risks. An adversary controlling several access points could triangulate a client's position. In addition, Interface Identifiers uniquely identify each client, allowing tracking of location over time. We enhance location privacy through frequent disposal of a client's Interface Identifier. While not preventing triangulation per se, it protects against an adversary following a user's movements over time. Design challenges include selecting new Interface Identifiers, detecting address collisions at the MAC layer, and timing Identifier switches to balance network disruptions against privacy protection. Using a modified authentication protocol, network operators can still control access to their network. An analysis of a public WLAN usage trace shows that disposing addresses before reassociation already yields significant privacy improvements.

  • Enhancing location privacy in wireless LAN through disposable Interface Identifiers: A quantitative analysis
    Mobile Networks and Applications, 2005
    Co-Authors: Marco Gruteser, Dirk Grunwald
    Abstract:

    The recent proliferation of wireless local area networks (WLAN) has introduced new location privacy risks. An adversary controlling several access points could triangulate a clients position. In addition, Interface Identifiers uniquely identify each client, allowing tracking of location over time. We enhance location privacy through frequent disposal of a clients Interface Identifier. The described system curbs the adversarys ability to continuously track a clients position. Design challenges include selecting new Interface Identifiers, detecting address collisions at the MAC layer, and timing Identifier switches to balance network disruptions against privacy protection. Using a modified authentication protocol, network operators can still control access to their network. An analysis of a public WLAN usage trace shows that disposing addresses before reassociation already yields significant privacy improvements.

Marco Gruteser - One of the best experts on this subject based on the ideXlab platform.

  • enhancing location privacy in wireless lan through disposable Interface Identifiers a quantitative analysis
    Mobile Networks and Applications, 2005
    Co-Authors: Marco Gruteser, Dirk Grunwald
    Abstract:

    The recent proliferation of wireless local area networks (WLAN) has introduced new location privacy risks. An adversary controlling several access points could triangulate a client's position. In addition, Interface Identifiers uniquely identify each client, allowing tracking of location over time. We enhance location privacy through frequent disposal of a client's Interface Identifier. While not preventing triangulation per se, it protects against an adversary following a user's movements over time. Design challenges include selecting new Interface Identifiers, detecting address collisions at the MAC layer, and timing Identifier switches to balance network disruptions against privacy protection. Using a modified authentication protocol, network operators can still control access to their network. An analysis of a public WLAN usage trace shows that disposing addresses before reassociation already yields significant privacy improvements.

  • Enhancing location privacy in wireless LAN through disposable Interface Identifiers: A quantitative analysis
    Mobile Networks and Applications, 2005
    Co-Authors: Marco Gruteser, Dirk Grunwald
    Abstract:

    The recent proliferation of wireless local area networks (WLAN) has introduced new location privacy risks. An adversary controlling several access points could triangulate a clients position. In addition, Interface Identifiers uniquely identify each client, allowing tracking of location over time. We enhance location privacy through frequent disposal of a clients Interface Identifier. The described system curbs the adversarys ability to continuously track a clients position. Design challenges include selecting new Interface Identifiers, detecting address collisions at the MAC layer, and timing Identifier switches to balance network disruptions against privacy protection. Using a modified authentication protocol, network operators can still control access to their network. An analysis of a public WLAN usage trace shows that disposing addresses before reassociation already yields significant privacy improvements.

Richard P Draves - One of the best experts on this subject based on the ideXlab platform.

  • privacy extensions for stateless address autoconfiguration in ipv6
    RFC, 2001
    Co-Authors: Thomas Narten, Richard P Draves
    Abstract:

    Nodes use IPv6 stateless address autoconfiguration to generate addresses without the necessity of a Dynamic Host Configuration Protocol (DHCP) server. Addresses are formed by combining network prefixes with an Interface Identifier. On Interfaces that contain embedded IEEE Identifiers, the Interface Identifier is typically derived from it. On other Interface types, the Interface Identifier is generated through other means, for example, via random number generation. This document describes an extension to IPv6 stateless address autoconfiguration for Interfaces whose Interface Identifier is derived from an IEEE Identifier. Use of the extension causes nodes to generate global-scope addresses from Interface Identifiers that change over time, even in cases where the Interface contains an embedded IEEE Identifier. Changing the Interface Identifier (and the global-scope addresses generated from it) over time makes it more difficult for eavesdroppers and other information collectors to identify when different addresses used in different transactions actually correspond to the same node.

  • privacy extensions for stateless address autoconfiguration in ipv6 status of this memo
    2001
    Co-Authors: Thomas Narten, Richard P Draves
    Abstract:

    Nodes use IPv6 stateless address autoconfiguration to generate addresses without the necessity of a Dynamic Host Configuration Protocol (DHCP) server. Addresses are formed by combining network prefixes with an Interface Identifier. On Interfaces that contain embedded IEEE Identifiers, the Interface Identifier is typically derived from it. On other Interface types, the Interface Identifier is generated through other means, for example, via random number generation. This document describes an extension to IPv6 stateless address autoconfiguration for Interfaces whose Interface Identifier is derived from an IEEE Identifier. Use of the extension causes nodes to generate global-scope addresses from Interface Identifiers that change over time, even in cases where the Interface contains an embedded IEEE Identifier. Changing the Interface Identifier (and the global-scope addresses generated from it) over time makes it more difficult for eavesdroppers and other information collectors to identify when different addresses used in different transactions actually correspond to the same node.

  • Privacy Extensions for Stateless Address Autoconfiguration
    2001
    Co-Authors: Thomas Narten, Richard P Draves
    Abstract:

    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. Copyright Notice Copyright (C) The Internet Society (2001). All Rights Reserved. Nodes use IPv6 stateless address autoconfiguration to generate addresses without the necessity of a Dynamic Host Configuration Protocol (DHCP) server. Addresses are formed by combining network prefixes with an Interface Identifier. On Interfaces that contain embedded IEEE Identifiers, the Interface Identifier is typically derived from it. On other Interface types, the Interface Identifier is generated through other means, for example, via random numbe

Alberto Escudero Pascual - One of the best experts on this subject based on the ideXlab platform.

  • Privacy extensions for stateless address autoconfiguration
    2002
    Co-Authors: Alberto Escudero Pascual
    Abstract:

    Abstract- Stateless address autoconfiguration defines the mechanism for a IPv6 node to generate an address without the need of an external DHCP server based on the Interface Identifier. In the case of Ethernet the Interface Identifier is based on the EUI-64 Identifier derived from the Interface’s built-in 48-bit IEEE 802 address (MAC address). The IPv6 address generated via Stateless Autoconfiguration contains the same Interface Identifier regardless of the location the mobile node is attached to the Internet. RFC3041 presents a privacy extension to Stateless Autoconfiguration based on the idea of generating random Interface Identifiers periodically. The paper introduces the concept of “unobservability” of the privacy extension and studies in which scenarios a third party will be able to determine with high probability if a node is running RFC3041 or not. The paper shows the privacy implications of the universal/local bit of the current IPv6 addressing architecture and presents a set of suggested changes to enhance privacy. I. BACKGROUND This paper is divided as follows: Section 1 contains a very brief overview of the Internet Protocol Version 6, Section 2 describes the different mechanisms to generate a global scope address including the privacy extension for stateless address configuration RFC3041 [6]. Section 3 defines unobservability of the privacy extension. Section 4 introduces the level of privacy extension observability for different scenarios and finally in Section 5 we present a set of suggeste

Thomas Narten - One of the best experts on this subject based on the ideXlab platform.

  • privacy extensions for stateless address autoconfiguration in ipv6
    RFC, 2001
    Co-Authors: Thomas Narten, Richard P Draves
    Abstract:

    Nodes use IPv6 stateless address autoconfiguration to generate addresses without the necessity of a Dynamic Host Configuration Protocol (DHCP) server. Addresses are formed by combining network prefixes with an Interface Identifier. On Interfaces that contain embedded IEEE Identifiers, the Interface Identifier is typically derived from it. On other Interface types, the Interface Identifier is generated through other means, for example, via random number generation. This document describes an extension to IPv6 stateless address autoconfiguration for Interfaces whose Interface Identifier is derived from an IEEE Identifier. Use of the extension causes nodes to generate global-scope addresses from Interface Identifiers that change over time, even in cases where the Interface contains an embedded IEEE Identifier. Changing the Interface Identifier (and the global-scope addresses generated from it) over time makes it more difficult for eavesdroppers and other information collectors to identify when different addresses used in different transactions actually correspond to the same node.

  • privacy extensions for stateless address autoconfiguration in ipv6 status of this memo
    2001
    Co-Authors: Thomas Narten, Richard P Draves
    Abstract:

    Nodes use IPv6 stateless address autoconfiguration to generate addresses without the necessity of a Dynamic Host Configuration Protocol (DHCP) server. Addresses are formed by combining network prefixes with an Interface Identifier. On Interfaces that contain embedded IEEE Identifiers, the Interface Identifier is typically derived from it. On other Interface types, the Interface Identifier is generated through other means, for example, via random number generation. This document describes an extension to IPv6 stateless address autoconfiguration for Interfaces whose Interface Identifier is derived from an IEEE Identifier. Use of the extension causes nodes to generate global-scope addresses from Interface Identifiers that change over time, even in cases where the Interface contains an embedded IEEE Identifier. Changing the Interface Identifier (and the global-scope addresses generated from it) over time makes it more difficult for eavesdroppers and other information collectors to identify when different addresses used in different transactions actually correspond to the same node.

  • Privacy Extensions for Stateless Address Autoconfiguration
    2001
    Co-Authors: Thomas Narten, Richard P Draves
    Abstract:

    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. Copyright Notice Copyright (C) The Internet Society (2001). All Rights Reserved. Nodes use IPv6 stateless address autoconfiguration to generate addresses without the necessity of a Dynamic Host Configuration Protocol (DHCP) server. Addresses are formed by combining network prefixes with an Interface Identifier. On Interfaces that contain embedded IEEE Identifiers, the Interface Identifier is typically derived from it. On other Interface types, the Interface Identifier is generated through other means, for example, via random numbe