Agenda bashing & Introductions.

• Only other topic of interest added is new use cases discussions, but
  will happen on the list

Note taker

• Wes will take notes

IETF Note Well.

Discussions and updates from authors

Update from Thomas on Architecture and Core

• architecture and CORE are now aligned better
• gateways could serve more than one network, so identification of the
  network to contact is important
  • which sub DLP do I want to talk with?

Discussions of items / issues identified by participants in the mailing list

• discussing architecture issues

• issue #7:

  • are gateways trusted, and what needs to trust what?
  • eg, gateways need to trust other gateways
  • there is an internal trust question too, about how clients trust
    their gateway (which is out of scope)
  • there is text to steal from other places (Rama, and past history
    of the BOF and legal agreements that may exist between
    gateways/networks)
  • Thomas will take this issue to the list and spell it out for
    discussion

• issue #10: How do deal with the number of active gateways

  • two views again: internal and external
  • external: it may rely on the transport as to doing loadbalacing
    etc and there are solved solutions
  • internal: how does selection of primary/secondary happen with
    voting, etc
  • internal: how do clients know who/what they need to talk to
  • Thomas will take this issue to the list and spell it out for
    discussion

asset-network identification (Thomas Hardjono)

• gateway identifiers need to be globally unique
• how do we prevent collisions
• how do this in a distributed way
• difficulties in a globally unique namespace to identify networks
  from a decentralized way
• application layer identifier vs connection identifier
• multiple options exist for doing both internal and external
  uniqueness

• one option is a field with some length:

  • a blockchain specific solution is a hash of the genisis block
  • non-blockchains should be self-defined about how they use that
    field

• Another option is an existing identifier system:

  • options to consider: DIDs, CIP2, URI based, ...
  • CIP2 has a namespace part and a suffix which is local

• security links are critical between protocol layers to ensure
  security