Protocol /
Definitions
Protocol.Definitions History
Hide minor edits - Show changes to output
February 25, 2011, at 05:42 AM
by - simplify
Changed lines 1-34 from:
!!! Network
There are two networks here: the '''[Ripple] ''credit/trust/payment'' network''' and the '''[Internet] ''data'' network'''. We must be careful to specify which we are talking about.
!!! Node/Peer
''Node'' and ''peer'' could refer to entities on either the credit network or the data network. These are not the same in general -- for example, one data node could hold multiple credit nodes. So let's try to avoid them and instead use:
* '''[Ripple] Address''' - a node (point/vertex/endpoint) in the credit network that can receive and send payment.
* '''[Ripple] Host''' - a machine on the data network
If we must use ''node'', we should try to prefix ''credit'' or ''data'' where it's not clear. Historically, ''node'' has meant address in the credit network, and ''peer'' has meant host, so assume that if it's not clear. It's entirely possible that ''node'' will keep getting used out of sheer inertia.
Also, since a node is an abstract entity managed by server software on host hardware, they may be used interchangeably sometimes. For examples, saying a node "knows" something is the same as saying its server software knows something, or that its host knows something.
!!! Connection
Again, ''connection'' could be on either the credit network or the data network. So: '''credit/trust connection''' or '''data connection''', if it's not clear from context.
!!! User/Participant
''User'' means a human who controls one or more nodes. Often it implies that those nodes are grouped on a single server. (It's possible that a single human might have "users" on multiple servers.)
''Participant'' is a broad term that might mean user, address/node, server, or host, depending on the context. Sometimes it's, and so ''participant'' is used as a bit of a catch-all. It's an informal, vague word.
!!! Client/Server
In the context of the Ripple protocol, let's use '''server''' to describe the Ripple distributed protocol software, and/or a running instance of that software on a Ripple host. '''Client''' software is that which controls a server and/or retrieves data from it.
!!! Currency
See [[Main/Currency Ambiguity]].
to:
There are a lot of words here that have a lot of potential to cause confusion because of their ambiguity. Here are a few definitions for the purposes of the protocol designs:
* '''Credit Network''' - the abstract network of financial trust connections over which payments are routed in Ripple.
* also '''Trust Network''', '''Payment Network'''
* '''Data Network''' - the network of data connections that serves to pass messages between host machines; the internet.
* '''Node''' - an address in the credit network that can send and/or receive payment.
* also '''Address'''
* '''Server''' - the protocol software, an instance of that software running on a host machine, or the host itself running the software.
See also [[Main/Currency Ambiguity]].
* '''Credit Network''' - the abstract network of financial trust connections over which payments are routed in Ripple.
* also '''Trust Network''', '''Payment Network'''
* '''Data Network''' - the network of data connections that serves to pass messages between host machines; the internet.
* '''Node''' - an address in the credit network that can send and/or receive payment.
* also '''Address'''
* '''Server''' - the protocol software, an instance of that software running on a host machine, or the host itself running the software.
See also [[Main/Currency Ambiguity]].
Added lines 16-17:
Also, since a node is an abstract entity managed by server software on host hardware, they may be used interchangeably sometimes. For examples, saying a node "knows" something is the same as saying its server software knows something, or that its host knows something.
Changed line 26 from:
''Participant'' is a broad term that might mean user, or server, or host, depending on the context. Sometimes it's not yet clear at what level a certain action is performed, and so ''participant'' is used as a bit of a catch-all. It's an informal, vague word.
to:
''Participant'' is a broad term that might mean user, address/node, server, or host, depending on the context. Sometimes it's, and so ''participant'' is used as a bit of a catch-all. It's an informal, vague word.
Changed lines 14-15 from:
If we must use ''node'', we should always prefix ''credit'' or ''data'' where it's not clear.
to:
If we must use ''node'', we should try to prefix ''credit'' or ''data'' where it's not clear. Historically, ''node'' has meant address in the credit network, and ''peer'' has meant host, so assume that if it's not clear. It's entirely possible that ''node'' will keep getting used out of sheer inertia.
Added lines 19-24:
!!! User/Participant
''User'' means a human who controls one or more nodes. Often it implies that those nodes are grouped on a single server. (It's possible that a single human might have "users" on multiple servers.)
''Participant'' is a broad term that might mean user, or server, or host, depending on the context. Sometimes it's not yet clear at what level a certain action is performed, and so ''participant'' is used as a bit of a catch-all. It's an informal, vague word.
Changed line 22 from:
In the context of the Ripple protocol, let's use '''server''' to describe the Ripple protocol software, and/or a running instance of that software on a Ripple host. '''Client''' software is that which controls a server and/or retrieves data from it.
to:
In the context of the Ripple protocol, let's use '''server''' to describe the Ripple distributed protocol software, and/or a running instance of that software on a Ripple host. '''Client''' software is that which controls a server and/or retrieves data from it.
Added lines 1-26:
There are a lot of words here that have a lot of potential to cause confusion because of their ambiguity.
!!! Network
There are two networks here: the '''[Ripple] ''credit/trust/payment'' network''' and the '''[Internet] ''data'' network'''. We must be careful to specify which we are talking about.
!!! Node/Peer
''Node'' and ''peer'' could refer to entities on either the credit network or the data network. These are not the same in general -- for example, one data node could hold multiple credit nodes. So let's try to avoid them and instead use:
* '''[Ripple] Address''' - a node (point/vertex/endpoint) in the credit network that can receive and send payment.
* '''[Ripple] Host''' - a machine on the data network
If we must use ''node'', we should always prefix ''credit'' or ''data'' where it's not clear.
!!! Connection
Again, ''connection'' could be on either the credit network or the data network. So: '''credit/trust connection''' or '''data connection''', if it's not clear from context.
!!! Client/Server
In the context of the Ripple protocol, let's use '''server''' to describe the Ripple protocol software, and/or a running instance of that software on a Ripple host. '''Client''' software is that which controls a server and/or retrieves data from it.
!!! Currency
See [[Main/Currency Ambiguity]].
!!! Network
There are two networks here: the '''[Ripple] ''credit/trust/payment'' network''' and the '''[Internet] ''data'' network'''. We must be careful to specify which we are talking about.
!!! Node/Peer
''Node'' and ''peer'' could refer to entities on either the credit network or the data network. These are not the same in general -- for example, one data node could hold multiple credit nodes. So let's try to avoid them and instead use:
* '''[Ripple] Address''' - a node (point/vertex/endpoint) in the credit network that can receive and send payment.
* '''[Ripple] Host''' - a machine on the data network
If we must use ''node'', we should always prefix ''credit'' or ''data'' where it's not clear.
!!! Connection
Again, ''connection'' could be on either the credit network or the data network. So: '''credit/trust connection''' or '''data connection''', if it's not clear from context.
!!! Client/Server
In the context of the Ripple protocol, let's use '''server''' to describe the Ripple protocol software, and/or a running instance of that software on a Ripple host. '''Client''' software is that which controls a server and/or retrieves data from it.
!!! Currency
See [[Main/Currency Ambiguity]].