% 
% This file was created by the TYPO3 extension
% bib
% --- Timezone: CEST
% Creation date: 2024-07-03
% Creation time: 21-36-12
% --- Number of references
% 9
% 

@Techreport { 2015-draft-moskowitz-hip-dex-04,
   title = {HIP Diet EXchange (DEX)},
   year = {2015},
   month = {7},
   day = {20},
   number = {draft-moskowitz-hip-dex-04},
   abstract = {This document specifies the Host Identity Protocol Diet EXchange (HIP DEX), a variant of the Host Identity Protocol Version 2 (HIPv2). The HIP DEX protocol design aims at reducing the overhead of the employed cryptographic primitives by omitting public-key signatures and hash functions. In doing so, the main goal is to still deliver similar security properties to HIPv2.

The HIP DEX protocol is primarily designed for computation or memory-constrained sensor/actuator devices. Like HIPv2, it is expected to be used together with a suitable security protocol such as the Encapsulated Security Payload (ESP) for the protection of upper layer protocol data. In addition, HIP DEX can also be used as a keying mechanism for security primitives at the MAC layer, e.g., for IEEE 802.15.4 networks.},
   note = {Work in progress},
   tags = {iotsec; ietf},
   url = {http://tools.ietf.org/html/draft-moskowitz-hip-dex-04},
   misc2 = {Online},
   institution = {Internet Engineering Task Force},
   type = {Internet-Draft},
   language = {en},
   author = {Moskowitz, Robert and Hummen, Ren{\'e}}
}

@Techreport { 2015-draft-moskowitz-hip-dex-03,
   title = {HIP Diet EXchange (DEX)},
   year = {2015},
   month = {6},
   day = {19},
   number = {draft-moskowitz-hip-dex-03},
   abstract = {This document specifies the Host Identity Protocol Diet EXchange (HIP DEX), a variant of the Host Identity Protocol Version 2 (HIPv2). The HIP DEX protocol design aims at reducing the overhead of the employed cryptographic primitives by omitting public-key signatures and hash functions. In doing so, the main goal is to still deliver similar security properties to HIPv2.

The HIP DEX protocol is primarily designed for computation or memory-constrained sensor/actuator devices. Like HIPv2, it is expected to be used together with a suitable security protocol such as the Encapsulated Security Payload (ESP) for the protection of upper layer protocol data. In addition, HIP DEX can also be used as a keying mechanism for security primitives at the MAC layer, e.g., for IEEE 802.15.4 networks.},
   note = {Work in progress},
   tags = {iotsec; ietf},
   url = {http://tools.ietf.org/html/draft-moskowitz-hip-dex-03},
   misc2 = {Online},
   institution = {Internet Engineering Task Force},
   type = {Internet-Draft},
   language = {en},
   author = {Moskowitz, Robert and Hummen, Ren{\'e}}
}

@Techreport { 2014-draft-moskowitz-hip-dex-02,
   title = {HIP Diet EXchange (DEX)},
   year = {2014},
   month = {12},
   day = {19},
   number = {draft-moskowitz-hip-dex-02},
   abstract = {This document specifies the Host Identity Protocol Diet EXchange (HIP DEX), a variant of the Host Identity Protocol Version 2 (HIPv2). The HIP DEX protocol design aims at reducing the overhead of the employed cryptographic primitives by omitting public-key signatures and hash functions. In doing so, the main goal is to still deliver similar security properties to HIPv2.

The HIP DEX protocol is primarily designed for computation or memory-constrained sensor/actuator devices. Like HIPv2, it is expected to be used together with a suitable security protocol such as the Encapsulated Security Payload (ESP) for the protection of upper layer protocol data. In addition, HIP DEX can also be used as a keying mechanism for security primitives at the MAC layer, e.g., for IEEE 802.15.4 networks.},
   note = {Work in progress},
   tags = {iotsec; ietf},
   url = {http://tools.ietf.org/html/draft-moskowitz-hip-dex-02},
   misc2 = {Online},
   institution = {Internet Engineering Task Force},
   type = {Internet-Draft},
   language = {en},
   author = {Moskowitz, Robert and Hummen, Ren{\'e}}
}

@Techreport { 2014-draft-moskowitz-hip-dex-01,
   title = {HIP Diet EXchange (DEX)},
   year = {2014},
   month = {3},
   day = {4},
   number = {draft-moskowitz-hip-dex-01},
   abstract = {This document specifies the Host Identity Protocol Diet EXchange (HIP
DEX), a variant of the HIP Base EXchange (HIP BEX) [rfc5201-bis].
The HIP DEX protocol design aims at reducing the overhead of the
employed cryptographic primitives by omitting public-key signatures
and hash functions.  In doing so, the main goal is to still deliver
similar security properties to HIP BEX.

The HIP DEX protocol is primarily targeted at computation or memory-constrained sensor devices.  Like HIP BEX, it is expected to be used
together with another suitable security protocol such as the
Encapsulated Security Payload (ESP) [rfc5202-bis] for the protection
of upper layer protocols.  HIP DEX can also be used as a keying
mechanism for a MAC layer security protocol as is supported by IEEE
802.15.4 [IEEE.802-15-4.2011].},
   note = {Work in progress},
   tags = {iotsec; ietf},
   url = {http://tools.ietf.org/html/draft-moskowitz-hip-dex-01},
   misc2 = {Online},
   institution = {Internet Engineering Task Force},
   type = {Internet-Draft},
   language = {en},
   author = {Moskowitz, Robert and Hummen, Ren{\'e}}
}

@Techreport { rfc5201-bis-04,
   title = {{Host Identity Protocol Version 2}},
   year = {2011},
   month = {1},
   volume = {1},
   number = {draft-ietf-hip-rfc5201-bis-04.txt},
   note = {{expires: July 24, 2011 (work in progress)}},
   tags = {mobile_access},
   url = {http://tools.ietf.org/html/draft-ietf-hip-rfc5201-bis-04},
   misc2 = {Online},
   publisher = {{IETF Trust}},
   howpublished = {An online version is available at: http://tools.ietf.org/html/draft-ietf-hip-rfc5201-bis-04},
   series = {Internet Drafts},
   organization = {{Internet Engineering Task Force}},
   institution = {Internet Engineering Task Force},
   language = {en},
   reviewed = {1},
   author = {Moskowitz, Robert and Jokela, Petri and Henderson, Thomas R. and Heer, Tobias}
}

@Techreport { rfc5201-bis-03,
   title = {{Host Identity Protocol Version 2}},
   year = {2010},
   month = {10},
   volume = {1},
   number = {draft-ietf-hip-rfc5201-bis-03.txt},
   note = {{expires: April 26, 2011 (work in progress)}},
   url = {http://tools.ietf.org/html/draft-ietf-hip-rfc5201-bis-03},
   misc2 = {Online},
   publisher = {{IETF Trust}},
   howpublished = {An online version is available at: http://tools.ietf.org/html/draft-ietf-hip-rfc5201-bis-03},
   series = {Internet Drafts},
   organization = {{Internet Engineering Task Force}},
   institution = {Internet Engineering Task Force},
   language = {en},
   reviewed = {1},
   author = {Moskowitz, Robert and Jokela, Petri and R. Henderson, Thomas and Heer, Tobias}
}

@Techreport { rfc5201-bis-01,
   title = {{Host Identity Protocol Version 2}},
   year = {2010},
   month = {9},
   volume = {1},
   number = {draft-ietf-hip-rfc5201-bis-01.txt},
   note = {{expires: March 7, 2011 (work in progress)}},
   url = {http://tools.ietf.org/html/draft-ietf-hip-rfc5201-bis-01},
   misc2 = {Online},
   publisher = {{IETF Trust}},
   howpublished = {An online version is available at: http://tools.ietf.org/html/draft-ietf-hip-rfc5201-bis-01},
   series = {Internet Drafts},
   organization = {{Internet Engineering Task Force}},
   institution = {Internet Engineering Task Force},
   language = {en},
   reviewed = {1},
   author = {Moskowitz, Robert and Jokela, Petri and R. Henderson, Thomas and Heer, Tobias}
}

@Techreport { moskowitz-rfc5201-bis-02,
   title = {{Host Identity Protocol Version 2}},
   year = {2010},
   month = {7},
   volume = {1},
   number = {draft-moskowitz-hip-rfc5201-bis-02.txt},
   note = {{expires: January 2, 2011 (work in progress)}},
   url = {http://tools.ietf.org/html/draft-moskowitz-hip-rfc5201-bis-02},
   misc2 = {Online},
   publisher = {{IETF Trust}},
   howpublished = {An online version is available at: http://tools.ietf.org/html/draft-moskowitz-hip-rfc5201-bis-02},
   series = {Internet Drafts},
   organization = {{Internet Engineering Task Force}},
   institution = {Internet Engineering Task Force},
   language = {en},
   reviewed = {1},
   author = {Moskowitz, Robert and Jokela, Petri and R. Henderson, Thomas and Heer, Tobias}
}

@Techreport { rfc5201-bis-02,
   title = {{Host Identity Protocol Version 2}},
   year = {2010},
   month = {7},
   volume = {1},
   number = {draft-ietf-hip-rfc5201-bis-02.txt},
   note = {{expires: March 7, 2011 (work in progress)}},
   url = {http://tools.ietf.org/html/draft-ietf-hip-rfc5201-bis-02},
   misc2 = {Online},
   publisher = {{IETF Trust}},
   howpublished = {An online version is available at: http://tools.ietf.org/html/draft-ietf-hip-rfc5201-bis-02},
   series = {Internet Drafts},
   organization = {{Internet Engineering Task Force}},
   institution = {Internet Engineering Task Force},
   language = {en},
   reviewed = {1},
   author = {Moskowitz, Robert and Jokela, Petri and R. Henderson, Thomas and Heer, Tobias}
}