RFC 7620: Scenarios with Host Identification Complications
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC7620
- Published
- August 2015
- Authors
- M. Boucadair; B. Chatras; T. Reddy; B. Williams; B. Sarikaya
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 26
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7785Recommendations for Prefix Binding in the Context of Softwire Dual-Stack LiteCurrent
February 2016
- RFC 7849An IPv6 Profile for 3GPP Mobile DevicesCurrent
May 2016
- RFC 7974An Experimental TCP Option for Host IdentificationCurrent
October 2016
- RFC 8517An Inventory of Transport-Centric Functions Provided by Middleboxes: An Operator PerspectiveCurrent
February 2019
- RFC 6431Huawei Port Range Configuration Options for PPP IP Control Protocol (IPCP)Current
November 2011
- RFC 8921Dynamic Service Negotiation: The Connectivity Provisioning Negotiation Protocol (CPNP)Current
October 2020
- RFC 7596Lightweight 4over6: An Extension to the Dual-Stack Lite ArchitectureCurrent
July 2015
- RFC 7678Attribute-Value Pairs for Provisioning Customer Equipment Supporting IPv4-Over-IPv6 Transitional SolutionsCurrent
October 2015
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?