Aries Interop Profile

The Aries Interop Profile is a standardized framework developed by the Hyperledger community to ensure interoperability between different implementations of Aries agents. It defines specific versions of protocols and features that agent builders must implement to achieve compatibility. The profile serves as a crucial reference point for developers, providing clear guidelines about which protocol versions and features to support for guaranteed interoperability with other AIP-compliant agents.

Key differentiators include:

• Version-specific protocol sets with explicit commit references
• Modular sub-target system for optional capabilities
• Built-in feature discovery mechanism
• Self-reporting compliance system
• Comprehensive test suite integration

Technical Analysis:

1. Purpose and Scope:

• Defines interoperability standards for Aries agent implementations
• Provides versioned sets of RFC specifications
• Enables independent development of compatible agents
• Supports multiple concurrent major versions (e.g., AIP 1.0, AIP 2.0)

2. Key Technical Specifications:

• Uses discover-features protocol for capability discovery
• Implements standardized message formats:
  • https://didcomm.org message prefix requirement
  • Standardized DIDComm envelope formats
• Supports multiple credential formats:

  INDYCRED for Indy-based credentials
  LDCRED for JSON-LD credentials
  BBSCRED for BBS+ credentials

3. Implementation Requirements:

• Must support base protocol set including:
  • DID Exchange
  • Issue Credential v2
  • Present Proof v2
  • Basic Message
• Requires implementation of specified RFC versions
• Must follow defined message formatting and encryption standards

4. Security Considerations:

• Enforces standardized encryption envelope formats
• Requires specific DIDComm security protocols
• Implements standardized problem reporting mechanisms
• Supports revocation notification handling

5. Interoperability Features:

• Feature discovery protocol
• Standardized message decorators
• Cross-domain messaging support
• Mediator coordination capabilities
• Transport-agnostic design

6. Current Adoption Status:

• Multiple active versions (AIP 1.0, AIP 2.0)
• Supported by major implementations:
  • Aries Cloud Agent Python
  • Aries Framework .NET
  • Open Source Mobile Agent
  • Various commercial implementations