Basic Socket Interface Extensions for the Host Identity Protocol (HIP)
RFC 6317
Document | Type | RFC - Experimental (July 2011; No errata) | |
---|---|---|---|
Authors | Tom Henderson , Miika Komu | ||
Last updated | 2015-10-14 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Stream | WG state | WG Document | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 6317 (Experimental) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Ralph Droms | ||
IESG note | Gonzalo Camarillo (Gonzalo.Camarillo@ericsson.com) is the document shepherd. | ||
Send notices to | (None) |
Internet Engineering Task Force (IETF) M. Komu Request for Comments: 6317 Aalto University Category: Experimental T. Henderson ISSN: 2070-1721 The Boeing Company July 2011 Basic Socket Interface Extensions for the Host Identity Protocol (HIP) Abstract This document defines extensions to the current sockets API for the Host Identity Protocol (HIP). The extensions focus on the use of public-key-based identifiers discovered via DNS resolution, but also define interfaces for manual bindings between Host Identity Tags (HITs) and locators. With the extensions, the application can also support more relaxed security models where communication can be non- HIP-based, according to local policies. The extensions in this document are experimental and provide basic tools for further experimentation with policies. Status of This Memo This document is not an Internet Standards Track specification; it is published for examination, experimental implementation, and evaluation. This document defines an Experimental Protocol for the Internet community. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6317. Komu & Henderson Experimental [Page 1] RFC 6317 Basic API Extensions for HIP July 2011 Copyright Notice Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. Table of Contents 1. Introduction ....................................................3 2. Terminology .....................................................5 3. Name Resolution Process .........................................5 3.1. Interaction with the Resolver ..............................5 3.2. Interaction without a Resolver .............................6 4. API Syntax and Semantics ........................................7 4.1. Socket Family and Address Structure Extensions .............7 4.2. Extensions to Resolver Data Structures .....................9 4.3. The Use of getsockname() and getpeername() Functions ......12 4.4. Selection of Source HIT Type ..............................12 4.5. Verification of HIT Type ..................................13 4.6. Explicit Handling of Locators .............................14 5. Summary of New Definitions .....................................16 6. Security Considerations ........................................16 7. Contributors ...................................................17 8. Acknowledgments ................................................17 9. References .....................................................17 9.1. Normative References ......................................17 9.2. Informative References ....................................18 Komu & Henderson Experimental [Page 2] RFC 6317 Basic API Extensions for HIP July 2011Show full document text