UNPKG

nanomsg

Version:

Node bindings for nanomsg

github.com/nickdesaulniers/node-nanomsg

nickdesaulniers/node-nanomsg

172 lines (77 loc) • 3.88 kB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
Internet Engineering Task Force M. Sustrik, Ed. Internet-Draft Intended status: Informational June 5, 2014 Expires: December 7, 2014 List of SP protocol IDs sp-protocol-ids-01 Abstract This document is intended to be a central repository of SP protocol IDs. The intention is to pass the task to IANA later on. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on December 7, 2014. Copyright Notice Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Sustrik Expires December 7, 2014 [Page 1] Internet-Draft List of SP protocol IDs June 2014 1. Introduction Different mappings for scalability protocols (see, for example SPoverTCP [SPoverTCP]) define a protocol header which in turn contains SP endpoint type ID. The ID consists of protocol ID and end the endpoint role: +-----------------------+------------------------+ | Protocol ID (12 bits) | Endpoint role (4 bits) | +-----------------------+------------------------+ Protocol IDs denote the SP protocol used (such as request/reply or publish/subscribe), while endpoint role determines the role of the endpoint within the topology (requester vs. replier, publisher vs. subscriber etc.) Both numbers are in network byte order. Protocol IDs are global, while endpoint roles are specific to any given protocol. As such, protocol IDs are defined in this document, while endpoint roles are defined in specific SP protocol RFCs. Note that there's no versioning of SP protocols. New versions of old protocols should register with new protocol ID. 2. Protocol IDs 1 - pair (v1) 2 - publish/subscribe (v1) 3 - request/reply (v1) 4 - unassigned 5 - pipeline (v1) 6 - survey (v1) 7 - bus (v1) 8 - slowsand (v1) 9-3839 - unassigned 3840-4095 local and experimental 3. IANA Considerations This memo describes numbers that should be eventually managed by IANA. Sustrik Expires December 7, 2014 [Page 2] Internet-Draft List of SP protocol IDs June 2014 4. Security Considerations There are no security considerations. 5. References [SPoverTCP] Sustrik, M., "TCP mapping for SPs", August 2013. Author's Address Martin Sustrik (editor) Email: sustrik@250bpm.com Sustrik Expires December 7, 2014 [Page 3]