ISP aspects

Discussion of desired BMX7 features for supporting community networks ISPs

Everybodies perspective

Want to:

• Use encrypted packet forwarding over mesh (eg using wireguard)

ISP/GW perspective

Want to:

• Express networks reachable via ISP (itself) and BW to them (eg DSL uplink speed)
• Delegate particular or random prefix to a client
• Offer enhanced GW-tunnel services to selected nodes

Clients perspective

Clients (of ISPs or GWs) are seeking to lease source-address-prefixes and tunnel routes.

Want to:

• Choose ISP based on:
  • Reachable networks and promised BW
  • Trustability of GW
  • Mesh-Path BW to GW
  • Offered source address prefix leased by GW to client
• Express preferred prefix to be leased from ISP
• Choose to obtain public or anonymous prefix from ISP

Concrete feature and parameter proposal

--wgDev DEVNAME 
  [udp-port PORT] 
  <srcPrefix ADDRMASK [ 
    delegate NETMASK/MIN 
    [privacy PRIVVAL] 
    [supportedClients IDDIR] ] > |
  <srcAuto NETMASK/MAX 
    [trustedDelegators IDDIR]
    [srcPreference NETMASK]
    [srcPrivacy PRIVVAL]
    [wgOut OUTNAME] >

--wgOut OUTNAME
  [wgDev DEVNAME]
  <dst NETMASK/MIN/MAX>
  [src NETMASK]
  [trustedGws IDDIR]
  [trustedDelegators IDDIR]
  [minBandwidth BANDWIDTH]

--wgIn INNAME
  <wgDev DEVNAME <
    <dst NETMASK
      [src NETMASK]
      [bandwidth BANDWIDTH] > |
    <wgOut OUTNAME> > >

• DEVNAME := wireguard tunnel device name (e.g. wg0)
• OUTNAME := Section name for outgoing wg-tunnel routes
• INNAME := Section name for incoming wg-tunnel routes
• PORT := udp port number
• ADDRMASK := address/prefix-length
• PRIVVAL := 0=none, 1=anonymous, 2=public, 3=both
• IDDIR := Path to directory containing files named as BMX7 node identities
• NETMASK := network/prefix-length
• MAX := upper limit for given prefix-length
• MIN := lower limit for given prefix-length
• BANDWIDTH := Bandwidth in bits/second

Acronyms

• BW: BandWidth
• ISP: Internet Service Provider
• GW: Gateway to other network