Skip to content

Instantly share code, notes, and snippets.

@justmoon

justmoon/TOPLEVEL.md

Last active February 8, 2017 09:37
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save justmoon/c1f24b595502251e6a1922a0e2069dd5 to your computer and use it in GitHub Desktop.
Save justmoon/c1f24b595502251e6a1922a0e2069dd5 to your computer and use it in GitHub Desktop.
Download ZIP
Top-level ILP address prefixes
Raw
TOPLEVEL.md

(This document is a draft.)

We define the following top-level ILP address prefixes:

  • g. for the globally routable address space defined by IL-RFC 0015
  • private. for any privately routable address space (similar to private networks in IP, e.g. 192.168.0.0/16)
  • example. for addresses appearing in examples or documentation
  • test1., test2., test3. for addresses using in testing (similar to TEST-NET-{1,2,3}; used by five-bells-integration-test)
  • local. for ledger-local addresses (similar to link-local addresses in IP, i.e. 169.254.0.0/16)
  • peer. for ledger-local addresses used in the context of a peering relationship (used by ilp-plugin-virtual)
  • self. for loopback addresses (similar to 127.0.0.0/8)
@mDuo13
Copy link

mDuo13 commented Feb 7, 2017

(similar to link-local addresses in IP, e.g.

Seems like an incomplete sentence here. Can you explain more on the difference between local. and self.?

Also, can you explain what peer. is for?

@sharafian
Copy link

peer. is currently used to address the trustlines between connectors. The connectors should know to send payments through trustlines, but they also shouldn't broadcast routes to them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment