Issue link: https://read.uberflip.com/i/1428302
TR9-1.0.0 Roaming Configuration Guidelines ©2021 LoRa ® Alliance Page 7 of 10 The authors reserve the right to change specifications without notice. Configuration Parameter Type When Using Peer-to-Peer Interconnection When Using Hub-Based Interconnection Required only if the Peer end- devices roam into the Own network. Peer JS IP Address(es) Required if the Own firewall blocks outgoing connections and the Peer end-devices roam into the Own network. Not needed Peer JS HTTP Authentication Credentials User ID and password and/or certificate credentials for each JS that has an hNS-JS interface with the Peer NS. Note that a given JS may be owned by an entity other than the Peer. Reqired only if the Peer end- devices roam into the Own network. Not needed 101 Table 1 NS Configuration 102 103 Table 2 illustrates the configuration that needs to be made on each JS that has an hNS-JS 104 interface with the Own NS and that hosts the Own end-devices that may perform activation 105 under the coverage of the Peer. Such JSs may belong to a third party. 106 107 Configuration Parameter Type When Using Peer-to-Peer Interconnection When Using Hub-Based Interconnection Peer NetID(s) MUST be NetID assigned by the LoRa Alliance. MUST NOT be value 0 or 1. With the LoRaWAN Backend Interfaces 1.1 Specification, using values 0 or 1 will be allowed for the Peer as long as its end-devices do not roam into the Own network. Not needed Peer fNS URL URL to reach the fNS functionality on the Peer NS. Not needed Peer NS IP Address(es) Required if a firewall is used on a JS network. Not needed Peer NS HTTP Authentication Credentials User ID and password and/or certificate credentials. Not needed 108 Table 2 JS Configuration 109