On 11/24/21 7:50 PM, Stephen J. Turnbull wrote:
Pedantry aside, I think we should probably have a Mailman-specific glossary for many terms, including the tests we use for validation. In this case, FQDN appears to be "sequence of characters not containing '@' or '/'."
Strongly agree about the glossary. For example, not every mailing list user will know the term "social login."
As for FQDN, is there some reason we shouldn't use the definition from RFC 1594, section 5.2?
5.2 What is a Fully Qualified Domain Name?
A Fully Qualified Domain Name (FQDN) is a domain name that
includes all higher level domains relevant to the entity named.
If you think of the DNS as a tree-structure with each node having
its own label, a Fully Qualified Domain Name for a specific node
would be its label followed by the labels of all the other nodes
between it and the root of the tree. For example, for a host, a
FQDN would include the string that identifies the particular host,
plus all domains of which the host is a part up to and including
the top-level domain (the root domain is always null). For
example, atlas.arc.nasa.gov is a Fully Qualified Domain Name for
the host at 128.102.128.50. In addition, arc.nasa.gov is the FQDN
for the Ames Research Center (ARC) domain under nasa.gov.This RFC has been obsoleted by RFC 2664, which no longer contains the FQDN definition -- likely because the RFC authors considered the term's meaning to be self-evident by the late 1990s, when the IETF published 2664. Many RFCs since then have used the term FQDN without defining it.
dn