[agent2agent] Re: [WIMSE] AAE supplier entry for the §3.1 delegation-chain row — draft-rampalli-cross-org-delegation-mapping, in the Bu -06 §18 vocabulary

[Lars Kersten Kroehl <[e-mail]>]

Iman, Karthik —

Corrected fields 7, 8, and 10 per Iman's review, taken verbatim. Fields 1–6, 9, and 11–21 stand as posted; the EMILIA evidence and pins are unchanged.

Claim grounding
Signed-mandate statements. Each AAE is asserted under the applicable issuer or delegator authority. Verification of the presented AAE and every ancestor links the terminal mandate back to the root AAE issuer; the root issuer does not directly sign every downstream mandate.

Signer role and principal relationship
The root signer acts as the root grant issuer. A delegated AAE signer is the immediate delegator, or an authority that delegator explicitly authorizes under Section 5 step 1. principal_did is a signed assertion. Base AAE does not verify the signer's relationship to that named principal or continuity of principal_did across the chain; a profile or enrollment process must supply that relationship.

Freshness
Temporal validity is bounded by not_before and not_after. If revocation_check is present, Step 8 applies. Step 4 requires a fresh, unused relying-party nonce and an iat inside the accepted skew window. When validity.single_use is true, Step 5 requires atomic check-and-record by VC id, shared across every accepting node.

Karthik — this is the version to cite. If you'd rather cite one consolidated entry, say so and I'll repost the full text with these folded in. Agreed on the informative PEDIGREE reference for the next AAE revision.

Lars




> Am 03.09.2026 um 18:19 schrieb Iman Schrock <team=[e-mail]>:
> 
> Lars, Karthik,
> 
> Thank you for expanding the entry. Fields 16 through 21 now separate
> the current draft from the historical evidence well. I think three
> lines need a technical correction before Karthik cites the post.
> 
> 7. Claim grounding
> 
> Signed-mandate statements. Each AAE is asserted under the applicable
> issuer or delegator authority. Verification of the presented AAE and
> every ancestor links the terminal mandate back to the root AAE issuer;
> the root issuer does not directly sign every downstream mandate.
> 
> 8. Signer role and principal relationship
> 
> The root signer acts as the root grant issuer. A delegated AAE signer
> is the immediate delegator, or an authority that delegator explicitly
> authorizes under Section 5 step 1. `principal_did` is a signed
> assertion. Base AAE does not verify the signer's relationship to that
> named principal or continuity of `principal_did` across the chain; a
> profile or enrollment process must supply that relationship.
> 
> 10. Freshness
> 
> Temporal validity is bounded by `not_before` and `not_after`. If
> `revocation_check` is present, Step 8 applies. Step 4 requires a
> fresh, unused relying-party nonce and an `iat` inside the accepted
> skew window. When `validity.single_use` is true, Step 5 requires
> atomic check-and-record by VC id, shared across every accepting node.
> 
> The EMILIA evidence wording and pins look right. I also agree that an
> informative PEDIGREE reference in the next AAE revision would make the
> pairing traceable from both directions.
> 
> Best,
> Iman
> 
> _______________________________________________
> agent2agent mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]