UMA1 Interop Participants and Solutions

Go to Features and Feature Tests page
Go to main UMA1 Interop Testing page 
Visit the uma-dev list archive

Participants in UMA1 testing must register on this page, either by editing the page or by contacting the UMA WG chair, and should subscribe to the uma-dev mailing list, which will be used for interop-related communications. No ranking of other special meaning should be attached to the order in which participants appear. Participants must supply:

1. Links to participant's organization, organization logo, and Twitter handle (if any)
2. Names and emails of 1-2 key contacts participating in the interop and available during the interop event
3. Whether the contacts will be participating F2F or virtually
4. Which UMA roles are covered in each solution
5. Any other relevant details as discussed below:
   
   1. TBS (any particular desired testing partners, how many wired network drops needed if participating F2F, static IP addresses required, any special requests for the event or venue, ?)
   2. AS role only:
      
      1. TBS (how RS and C can get client credentials if not dynamic, ?)
      2. Link to the AS configuration data
   3. RS role only:
      
      1. TBS (API documentation, ?)
   4. C role only:
      
      1. TBS

Results

Record feature-test-specific results in this matrix. An example result for a FOO:AS-to-BAR:RS interaction attempt regarding the F-as-config test might read: FT-rs-get-config-data failed. Config data from FOO:AS was malformed.

Record rollup results in this matrix. An example cell for a FOO:BAR comparison might read: Detected failures when FOO is AS and BAR is RS or C. When FOO is RS and BAR is AS, succeeds.