This repository was archived by the owner on Jan 2, 2026. It is now read-only.
Rewrite section #6.1.1.1 slightly #40
Description
A pDN must meet all the following requirements:
If the pDN describes an actor, it must have a "common name" attribute. The common name must be the [local name](https://polyproto.org/docs/protocols/core/#5-federation-ids-fids) of the actor. In the case of an actor with an FID of [email protected], the local name would be xenia. If the pDN describes a home server, the "common name" attribute must not be present.
Must have at least one domain component dc, specifying the domain name under which the home server can be reached. This includes the home server's top- and second-level domains, as well as all other subdomains, if present. If the home server does not have a sub- or top-level domain, the dc fields for these components should be omitted.
If the pDN describes an actor, the pDN must include the UID ([OID](https://en.wikipedia.org/wiki/Object_identifier) 0.9.2342.19200300.100.1.1) and uniqueIdentifier ([OID](https://en.wikipedia.org/wiki/Object_identifier) 0.9.2342.19200300.100.1.44) fields.
UID field must be equal to the federation ID of the actor, e.g., actor@domainname-of-home server.example.com.
uniqueIdentifier field must be a [Session ID](https://polyproto.org/docs/protocols/core/#6113-session-ids).
Can have other attributes if the additional attributes do not conflict with the above requirements. Additional attributes might be ignored by other home servers and other clients unless specified otherwise in a polyproto extension. Additional attributes not part of a polyproto extension must be non-critical X.509 extensions.
This is needlessly hard to read/understand and should be rewritten and reformatted for clarity and brevity.