References from draft-ietf-jmap-jscontact

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
BCP 14	Key words for use in RFCs to Indicate Requirement Levels References Referenced by	Best Current Practice	normatively references
BCP 205	Improving Awareness of Running Code: The Implementation Status Section References Referenced by	Best Current Practice	normatively references
BCP 47	Tags for Identifying Languages References Referenced by	Best Current Practice	normatively references
RFC 2046	Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types References Referenced by	Draft Standard	normatively references
RFC 2119	Key words for use in RFCs to Indicate Requirement Levels References Referenced by	Best Current Practice	normatively references
RFC 3261	SIP: Session Initiation Protocol References Referenced by	Proposed Standard	informatively references
RFC 3339	Date and Time on the Internet: Timestamps References Referenced by	Proposed Standard	informatively references
RFC 3966	The tel URI for Telephone Numbers References Referenced by	Proposed Standard	informatively references
RFC 4122	A Universally Unique IDentifier (UUID) URN Namespace References Referenced by	Proposed Standard	normatively references
RFC 5646	Tags for Identifying Languages References Referenced by	Best Current Practice	normatively references
RFC 5870	A Uniform Resource Identifier for Geographic Locations ('geo' URI) References Referenced by	Proposed Standard	normatively references
RFC 6068	The 'mailto' URI Scheme References Referenced by	Proposed Standard	informatively references
RFC 6350	vCard Format Specification References Referenced by	Proposed Standard	normatively references
RFC 6351	xCard: vCard XML Representation References Referenced by	Proposed Standard	normatively references
RFC 6473	vCard KIND:application References Referenced by	Proposed Standard	informatively references
RFC 6474	vCard Format Extensions: Place of Birth, Place and Date of Death References Referenced by	Proposed Standard	informatively references
RFC 6715	vCard Format Extensions: Representing vCard Extensions Defined by the Open Mobile Alliance (OMA) Converged Address Book (CAB) Group References Referenced by	Proposed Standard	informatively references
RFC 6869	vCard KIND:device References Referenced by	Proposed Standard	informatively references
RFC 7095	jCard: The JSON Format for vCard References Referenced by	Proposed Standard	normatively references
RFC 7493	The I-JSON Message Format References Referenced by	Proposed Standard	normatively references
RFC 7942	Improving Awareness of Running Code: The Implementation Status Section References Referenced by	Best Current Practice	normatively references
RFC 8174	Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words References Referenced by	Best Current Practice	normatively references
RFC 8259	The JavaScript Object Notation (JSON) Data Interchange Format References Referenced by	Internet Standard	normatively references
RFC 8605	vCard Format Extensions: ICANN Extensions for the Registration Data Access Protocol (RDAP) References Referenced by	Informational	informatively references
STD 90	The JavaScript Object Notation (JSON) Data Interchange Format References Referenced by	Internet Standard	normatively references