RFC 4969

RFC 4969: IANA Registration for vCard Enumservice ✨

Okay bestie, welcome to RFC 4969 💖 Here's the title block tea:

• RFC number: 4969
• Title: IANA Registration for vCard Enumservice 🎀
• Author: Alexander Mayrhofer, from enum.at 🦋
• Stream: Network Working Group
• Category: Standards Track 👑
• Date: August 2007 🌸
• Obsoletes / Updates: the header doesn't list any RFC it obsoletes or updates, so nothing to see there 🙈

---

Status of This Memo 📜

So this doc is an Internet standards track protocol spec for the Internet community, and they're literally begging for discussion and suggestions for improvements 🥺 For the current standardization state and status of this protocol, check the "Internet Official Protocol Standards" (STD 1) 📚 And distribution of this memo is unlimited, so share away 💌

Copyright Notice 🌸

Copyright (C) The IETF Trust (2007).

Abstract 💅

This memo registers the Enumservice "vCard" using the URI schemes "http" and "https". 🎀 This Enumservice is used to point from an ENUM domain name to a vCard instance describing the user of the matching E.164 number.

Info gathered from those vCards could be used before, during, or after inbound or outbound communication happens 📞 For example, a callee might see the name and association of the caller before picking up the call 👀

Table of Contents 🗂️

1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3.  Enumservice Registration - vCard  . . . . . . . . . . . . . . . 2
4.  Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
5.  Security and Privacy Considerations . . . . . . . . . . . . . . 3
  5.1.  The ENUM Record Itself  . . . . . . . . . . . . . . . . . . 3
  5.2.  The Resource Identified . . . . . . . . . . . . . . . . . . 4
6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 5
8.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 5
  8.1.  Normative References  . . . . . . . . . . . . . . . . . . . 5
  8.2.  Informative References  . . . . . . . . . . . . . . . . . . 5

1. Introduction ✨

Okay so ENUM, which is E.164 Number Mapping [1], uses the Domain Name System (DNS) [2] to point from E.164 numbers [3] over to Uniform Resource Identifiers (URIs) [6] 📞 The steps for registering Enumservices are described in Section 3 of RFC 3761 ✍️

"vCard" [4] is a transport-independent data format for swapping info about an individual 💼 In this doc, the term "vCard" means one specific instance of that data format, an "electronic business card" 💖 vCards get passed around through several protocols; most commonly they're sent as electronic mail attachments or published on web servers 🌐 Most popular personal information manager apps can read and write them, so it's giving compatibility 💅

The Enumservice in this document is all about the relationship between an E.164 number and vCards 🦋 An ENUM record using this Enumservice points to a resource where a vCard for that E.164 number could be fetched 🧚

Clients could use those resources to, e.g., automatically update local address books 📒 (a Voice over IP phone could try to fetch vCards for all outbound and inbound calls taking place on that phone and show them together with the call journal 📱). In a more integrated scenario, info from those vCards could even be automatically pulled into the personal information manager app of the user 🌈

2. Terminology 🔑

Here are the key words: "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL". They're to be interpreted as described in RFC 2119 [5] 🎀

3. Enumservice Registration - vCard 🎀

Here's the registration template, bestie 📋

Enumservice Name: "vCard"

Enumservice Type: "vcard"

Enumservice Subtype: n/a

URI Schemes: "http", "https"
Functional Specification:

The functional spec is where the magic is ✨ This Enumservice says the resource identified is a plain vCard, according to RFC 2426, and you can access it with HTTP/HTTPS [7] 🦋

Clients fetching the vCard from the indicated resource should expect access to be restricted 🔒 And the comprehension of the data provided may vary depending on the client's identity 👀

The rest of the template goes like this:

Security Considerations: see Section 5

Intended Usage: COMMON

Author: Alexander Mayrhofer <alexander.mayrhofer@enum.at>

4. Example 🌈

Here's an example ENUM entry that references a vCard, and it could look like this:

$ORIGIN 6.4.9.0.6.4.9.7.0.2.4.4.e164.arpa.
@  IN NAPTR 100 10 "u" "E2U+vcard" \
"!^.*$!http://example.net/vcard.vcf!" .

Intellectual Property ✨

okay so bestie, the IETF is NOT taking a side on whether any intellectual property rights (or other rights someone might claim) over the tech in this doc are valid, or how far they reach 💅 it's also not saying whether a license is even available. and it hasn't gone hunting for any of those rights on its own 🙈 if you want the rules about rights in RFC docs, check out BCP 78 and BCP 79 🎀

copies of IPR disclosures sent to the IETF Secretariat, any license assurances, and the results of anyone trying to get a general license or permission to use those proprietary rights (for implementers or users of this spec) can all be found in the IETF's on-line IPR repository at http://www.ietf.org/ipr 🌸

and the IETF literally wants anyone to speak up if they know about copyrights, patents, patent applications, or other proprietary rights that might cover tech needed to implement this standard 🫶 send that info to the IETF at ietf-ipr@ietf.org 💖

Acknowledgement

funding for the RFC Editor function is currently provided by the Internet Society 🧚✨