Source note · Network-based location for E911 across platforms
RFC 6155 extends HELD so a requester can identify a device by IP address, MAC address, transport port numbers, NAI, URI, FQDN, cellular identifiers or DHCP Unique Identifier; it does not define LLDP or 802.11 measurements.
Checked 2026-10-14
- Vendor
- not restricted
- Product
- not restricted
- Subsystem
- HELD
- Deployment
- any
- Region
- not restricted
- Release range
- RFC 6155
- Checked
- 2026-10-14
Sources
- Use of Device Identity in HTTP-Enabled Location Delivery (HELD) — IETF · tier 1 standards and regulators · Sections 3.1 to 3.8
Cite this note
APA
WarmTransfer. (2026, October 14). Network-based location for E911 across platforms: source note e911-network-location-discovery-rfc6155-device-ids. WarmTransfer. https://warmtransfer.net/knowledge/claims/e911-network-location-discovery-rfc6155-device-ids
BibTeX
@misc{warmtransfer-claim-e911-network-location-discovery-rfc6155-device-ids,
title = {Network-based location for E911 across platforms: source note e911-network-location-discovery-rfc6155-device-ids},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/e911-network-location-discovery-rfc6155-device-ids},
note = {Source note e911-network-location-discovery-rfc6155-device-ids, checked 2026-10-14}
}