Browse Prior Art Database

Scenarios with Host Identification Complications (RFC7620)

IP.com Disclosure Number: IPCOM000242786D
Original Publication Date: 2015-Aug-01
Included in the Prior Art Database: 2015-Aug-15
Document File: 52 page(s) / 60K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Boucadair: AUTHOR [+6]

Abstract

The goal of this document is to enumerate scenarios that encounter the issue of uniquely identifying a host among those sharing the same IP address. Within this document, a host can be any device directly connected to a network operated by a network provider, a Home Gateway, or a roaming device located behind a Home Gateway.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 4% of the total text.

Independent Submission                                 M. Boucadair, Ed. Request for Comments: 7620                                    B. Chatras Category: Informational                                           Orange ISSN: 2070-1721                                                 T. Reddy                                                            Cisco Systems                                                              B. Williams                                                             Akamai, Inc.                                                              B. Sarikaya                                                                   Huawei                                                              August 2015

             Scenarios with Host Identification Complications

Abstract

   This document describes a set of scenarios in which complications    when identifying which policy to apply for a host are encountered.    This problem is abstracted as "host identification".  Describing    these scenarios allows commonalities between scenarios to be    identified, which is helpful during the solution design phase.

   This document does not include any solution-specific discussions.

IESG Note

   This document describes use cases where IP addresses are overloaded    with both location and identity properties.  Such semantic    overloading is seen as a contributor to a variety of issues within    the routing system [RFC4984].  Additionally, these use cases may be    seen as a way to justify solutions that are not consistent with IETF    Best Current Practices on protecting privacy [BCP160] [BCP188].

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for informational purposes.

   This is a contribution to the RFC Series, independently of any other    RFC stream.  The RFC Editor has chosen to publish this document at    its discretion and makes no statement about its value for    implementation or deployment.  Documents approved for publication by    the RFC Editor are not 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/rfc7620.

Boucadair, et al.             Informational            ...