Expand description
RFC 3325 asserted and preferred identity header values.
Trust is deliberately not represented here. Construction enforces RFC 3325’s strict one-or-two-value shape. Reception follows RFC 5876 §4.5 instead: syntactically valid values with an unexpected scheme or position are reported as ignored so a proxy can remove them without discarding the valid identities that preceded them.
Structs§
- Ignored
Identity - One syntactically parsed received identity that RFC 5876 §4.5 says not to use or forward.
- PAsserted
Identity - One strict
P-Asserted-Identityvalue (RFC 3325 §9.1). - PAsserted
Identity List - A complete identity field: strict for construction, tolerant and explicit on receive.
- PPreferred
Identity - One strict
P-Preferred-Identityvalue (RFC 3325 §9.2). - PPreferred
Identity List - A complete identity field: strict for construction, tolerant and explicit on receive.
Enums§
- Ignored
Identity Reason - Why RFC 5876 §4.5 says a received identity value is ignored.