Summary

  • RFC 3191 placed a telephone-number representation inside an Internet mail local-part, but expressly denied it global meaning: only the MTA responsible for the right-hand domain was entitled to interpret the service selector, number and qualifiers.
  • The minimal format separated representation from effect. Human separators were ignored, unknown optional qualifiers could be ignored for execution but had to be preserved, multiple subaddresses became multiple email recipients, and successful DNS or mail routing did not prove subscriber identity, gateway execution or delivery on the telephone network.

A telephone number entered a namespace that already had an owner

By 2001, gateways between Internet mail and telephone services had accumulated several incompatible ways to put a telephone destination into an email address. The attraction was obvious. A mail user could reach a voice, fax or messaging gateway from an ordinary composer, while a provider could carry material over Internet mail before handing it to the switched network.

RFC 3191 did not attempt to translate the whole Global Switched Telephone Network into email. It defined a minimal common form. The local-part began with a service selector, an equals sign and a phone representation. A domain followed the at-sign. Optional registered qualifiers could refine the instruction.

That surface looked self-describing. It was not. The RFC repeated the ordinary mail rule: a local-part is not to be interpreted except by the MTA that handles the domain on the right. VOICE=+... could resemble a portable command, but its authority came from the chosen gateway domain. Another MTA's job was carriage, not telephone semantics.

This boundary prevented a useful syntax from becoming a claim of universal identity. A number-shaped local-part did not identify a verified subscriber. The domain did not certify that the number existed. Together they selected a gateway and presented it with an instruction.

The minimum was deliberately smaller than telephony

The core grammar was compact. The service selector used letters, digits and hyphens and was interpreted without regard to case. The global form began with +, followed by digits and optional dots or hyphens. The leading plus was reserved for the global numbering form; local or private dialing plans could exist, but could not borrow that signal.

The dots and hyphens served readers. Conforming implementations had to ignore them. They were allowed in the syntax but discouraged in transmission. Two strings with different visual grouping could therefore carry the same minimal number for processing.

That rule was not a general telephone-number normalizer. The RFC did not decide whether the number was assigned, reachable or sufficient for a particular service. It established which characters belonged to the minimal representation and which characters had no operational weight.

The examples made the limitation visible. VOICE, FAX and SMS strings illustrated possible shapes. The document warned that they did not necessarily represent valid addresses. Grammar illustrated a contract; it did not supply a directory of working endpoints.

Ignoring an extension did not authorize its erasure

A service could add a qualif-type1 element in the form of a slash, keyword, equals sign and value. The extension mechanism let later specifications express service-specific information without reopening the minimal grammar for every application.

A conforming minimal implementation could ignore a non-minimal qualifier it did not support. It could not silently delete it from the address it received. RFC 3191 required preservation of all qualifier elements.

The asymmetry matters. Ignoring says that this processor will not act on the field. Preserving says that a later processor may still possess the authority and knowledge to act on it. Deletion would convert local inability into a global decision.

Registration bounded the vocabulary. A service selector or qualifier needed a permanent specification sufficient for independent implementation. A qualifier registration could also restrict where it made sense. The registry did not prove that any gateway implemented the element, but it prevented the shared syntax from being extended by unrecorded private guesswork.

Gateway scars were accepted without becoming the preferred form

The complete object remained an Internet addr-spec, with the quoting rules of mail. Optional slashes could surround the telephone structure because other gateway systems, including X.400 paths, might leave them behind. Receivers had to accept those slashes, should not generate them and could remove them during conversion.

This was compatibility without canonising the scar. The syntax remembered that messages passed through systems with different address conventions. It allowed an old representation to arrive while giving new senders a cleaner form.

RFC 3191 itself was a similar revision. It replaced the older RFC 2303 and changed the expansion of PSTN from “Public” to GSTN, “Global”, because telephony no longer fitted a single- or few-public-operator picture. Yet it retained older ABNF variable names. Terminology changed to describe the institutional landscape; wire-facing identifiers stayed stable for compatibility.

One telephone mailbox could still require several email recipients

Telephone services could associate more than one subaddress with the same number. Mail had a different recipient model: each destination was represented by a separate address.

RFC 3191 therefore required multiple pstn-email elements when several subaddresses applied. A user agent could let a person enter them together, but it had to hand the MTA distinct recipients.

The conversion changed shape. One telephone mailbox with multiple internal selectors could not be compressed into one opaque mail recipient without losing mail's delivery accounting. Separate recipient records allowed acceptance, failure and retry to remain attributable.

This did not guarantee that each downstream subaddress worked. It preserved the ability to distinguish outcomes. A gateway might accept one recipient and reject another. A final fax device might answer neither. The email envelope, gateway handoff and telephone result remained different receipts.

DNS chose a mail route, not a telephone truth

Mail routing used the domain on the right. RFC 3191's security section therefore focused on DNS manipulation: a compromised server, a forged answer or contaminated additional information could divert a message through a hostile MTA or gateway.

Authoritative DNS evidence could protect the choice of mail route. It could not attest every fact beyond that choice. A correctly selected gateway might have faulty software, stale number data, a policy rejection or no route to the telephone destination. A valid number might belong to a different subscriber than a sender expected.

The chain needed separate observations: the address string submitted by the user agent, the DNS answer used by the MTA, SMTP acceptance by the gateway, the gateway's parsing decision, the instruction sent toward the switched network and any final service receipt. Collapsing them into “the email address worked” would lose where authority changed hands.

The minimal format succeeded by refusing to own the outcome

RFC 2846 provided a fuller superset for local dialing, post-dial sequences, subaddresses and recipient details. RFC 3192 applied the minimal framework specifically to fax. Those documents did not make the generic RFC 3191 form an execution engine.

Its achievement was narrower. Different gateway services could share one small envelope and one governed extension method. Transit systems could carry the instruction without interpreting it. Gateways could recognise registered vocabulary without claiming that every syntactically valid destination was real.

The historical lesson sits on either side of the at-sign. The left side held a telephone-shaped representation. The right side selected its interpreter. Neither side recorded the ultimate effect. Interoperation remained possible because the standard assigned each layer less authority than the whole address appeared to contain.