Can we turn opaque_info into more concrete fields, in EAD_1?

[geonnave]

I am interested in exploring how we can reduce, as much as possible, the use of opaque_info, for the following reasons:

1. interoperability
2. the problem of providing "free connectivity" in EAD_1

Proposal

The proposal so far is to replace opaque_info by nearby_vs:

nearby_vs = {
  / macs-addrs   /     1: [ + bstr ],
  / pan-ids      /     2: [ + bstr ],
  / ipv4-addrs   /     3: [ + bstr ],
  / ipv6-addrs   /     4: [ + bstr ],
  / app-specific / 16-31: [ + bstr ],
}

Some comments:

1. the idea is to satisfy the problem of sending a list of "nearby Vs", while achieving better interoperability, in a way that is agnostic to the type of network identifier
2. for now, the proposal assumes that "nearby Vs" is the only type of contextual data that U would ever want to send to W
3. do we have concrete examples of other kind of contextual data that should be sent to W?

[geonnave]

Closing as obsolete after merging of #41.