Scenarios with Host Identification Complications
RFC 7620
Document | Type |
RFC - Informational
(August 2015; No errata)
Was draft-boucadair-intarea-host-identifier-scenarios (individual)
|
|
---|---|---|---|
Authors | Mohamed Boucadair , Bruno Chatras , Tirumaleswar Reddy.K , Brandon Williams , Behcet Sarikaya | ||
Last updated | 2018-12-20 | ||
Stream | ISE | ||
Formats | plain text html pdf htmlized bibtex | ||
IETF conflict review | conflict-review-boucadair-intarea-host-identifier-scenarios | ||
Stream | ISE state | Published RFC | |
Consensus Boilerplate | Unknown | ||
Document shepherd | Adrian Farrel | ||
Shepherd write-up | Show (last changed 2015-04-20) | ||
IESG | IESG state | RFC 7620 (Informational) | |
Telechat date | |||
Responsible AD | (None) | ||
Send notices to | (None) | ||
IANA | IANA review state | IANA OK - No Actions Needed | |
IANA action state | No IANA Actions |
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 [Page 1] RFC 7620 Host Identification: Scenarios August 2015 Copyright Notice Copyright (c) 2015 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. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Scenario 1: Carrier-Grade NAT (CGN) . . . . . . . . . . . . . 4 4. Scenario 2: Address plus Port (A+P) . . . . . . . . . . . . . 5 5. Scenario 3: On-Premise Application Proxy Deployment . . . . . 6 6. Scenario 4: Distributed Proxy Deployment . . . . . . . . . . 7 7. Scenario 5: Overlay Network . . . . . . . . . . . . . . . . . 8 8. Scenario 6: Policy and Charging Control Architecture (PCC) . 10 9. Scenario 7: Emergency Calls . . . . . . . . . . . . . . . . . 12 10. Other Deployment Scenarios . . . . . . . . . . . . . . . . . 13 10.1. Open WLAN or Provider WLAN . . . . . . . . . . . . . . . 13 10.2. Cellular Networks . . . . . . . . . . . . . . . . . . . 14 10.3. Femtocells . . . . . . . . . . . . . . . . . . . . . . . 14 10.4. Traffic Detection Function (TDF) . . . . . . . . . . . . 17 10.5. Fixed and Mobile Network Convergence . . . . . . . . . . 18 11. Synthesis . . . . . . . . . . . . . . . . . . . . . . . . . . 21 12. Privacy Considerations . . . . . . . . . . . . . . . . . . . 21 13. Security Considerations . . . . . . . . . . . . . . . . . . . 22 14. Informative References . . . . . . . . . . . . . . . . . . . 22 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 25 Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26 Boucadair, et al. Informational [Page 2] RFC 7620 Host Identification: Scenarios August 2015 1. Introduction 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 HomeShow full document text