References from draft-thomson-geopriv-held-capabilities

This is an experimental product. These dependencies are extracted using heuristics looking for strings with particular prefixes. Notably, this means that references to I-Ds by title only are not reflected here. If it's really important, please inspect the documents' references sections directly.

Reference type help

Document Title Status Type Downref
BCP 14 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice normatively references
draft-barnes-geopriv-policy-uri Location Configuration Extensions for Policy Management
Refs Ref'd by
informatively references
draft-ietf-geopriv-arch An Architecture for Location and Location Privacy in Internet Applications
Refs Ref'd by
Best Current Practice informatively references
draft-ietf-geopriv-http-location-delivery HTTP-Enabled Location Delivery (HELD)
Refs Ref'd by
Proposed Standard normatively references
draft-ietf-geopriv-lis-discovery Discovering the Local Location Information Server (LIS)
Refs Ref'd by
Proposed Standard normatively references
draft-loreto-http-bidirectional Known Issues and Best Practices for the Use of Long Polling and Streaming in Bidirectional HTTP
Refs Ref'd by
Informational informatively references
draft-loreto-http-timeout Hypertext Transfer Protocol (HTTP) Timeouts
Refs Ref'd by
normatively references
draft-saintandre-tls-server-id-check Representation and Verification of Domain-Based Application Service Identity within Internet Public Key Infrastructure Using X.509 (PKIX) Certificates in the Context of Transport Layer Security (TLS)
Refs Ref'd by
Proposed Standard normatively references
draft-thomson-geopriv-held-measurements Using Device-provided Location-Related Measurements in Location Configuration Protocols
Refs Ref'd by
normatively references
draft-thomson-geopriv-uncertainty Representation of Uncertainty and Confidence in PIDF-LO
Refs Ref'd by
informatively references
draft-winterbottom-geopriv-deref-protocol A Location Dereferencing Protocol Using HELD
Refs Ref'd by
normatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice normatively references
RFC 2141 URN Syntax
Refs Ref'd by
Proposed Standard informatively references
RFC 2616 Hypertext Transfer Protocol -- HTTP/1.1
Refs Ref'd by
Draft Standard normatively references
RFC 2818 HTTP Over TLS
Refs Ref'd by
Informational normatively references
RFC 3688 The IETF XML Registry
Refs Ref'd by
Best Current Practice normatively references
RFC 5808 Requirements for a Location-by-Reference Mechanism
Refs Ref'd by
Informational informatively references