xpra icon
Bug tracker and wiki

Ticket #731: IANA-port-number-registration-request.txt

File IANA-port-number-registration-request.txt, 4.3 KB (added by Antoine Martin, 14 months ago)

automated response

Line 
1To whom it may concern:
2
3This is an automatically generated message to notify you that we have
4received your request, and it has been recorded in our ticketing
5system with a reference number of 927354. To check the status
6of your request, please see:
7
8https://tools.iana.org/public-view
9
10If you have any problems accessing this page, please contact
11iana@iana.org.
12
13There is no need to reply to this message right now. IANA staff will
14review your message shortly.
15
16If this message is in reply to a previously submitted ticket, it is
17possible that the previous ticket has been marked as closed. As we
18review this ticket, we will also review previous correspondence and
19take appropriate action.
20
21To expedite processing, and ensure our staff can view the full history
22of this request, please make sure you include the follow exact text in
23the subject line of all future correspondence on this issue:
24
25         [IANA #927354]
26
27You can also simply reply to this message, as this tag is already in
28the subject line.
29
30Thank you,
31
32The Internet Assigned Numbers Authority
33iana-ports@iana.org
34
35-------------------------------------------------------------------------
36
37Application for a Port Number and/or Service Name
38
39Assignee: Xpra <xpra@xpra.org>
40Contact Person: Antoine Martin <antoine@nagafix.co.uk>
41
42Resource Request:
43
44    [x] Port Number
45    [x] Service Name
46
47Transport Protocols:
48    [x] TCP
49    [x] UDP
50    [ ] SCTP
51    [x] DCCP
52
53Service Code:         [xpra]
54Service Name:         [xpra]
55Desired Port Number:  []
56Description:          [xpra network protocol]
57
58Reference:
59[xpra clients connect to xpra servers using a choice of 3 different packet encoding schemes (bencode, rencode, yaml), 3 stream compression algorithms (zlib, lzo, lz4). The connection can also use SSL. These are negotiated during the initial packet exchange, more options may be added in the future.
60http://xpra.org/trac/wiki/NetworkProtocol]
61
62Defined TXT Keys:     mode,display
63
641.  If broadcast/multicast is used, how and what for?
65[]
66
672.  If UDP is requested, please explain how traffic is limited, and whether the
68    protocol reacts to congestion.
69[UDP is not implemented yet but it is planned:
70http://xpra.org/trac/ticket/639]
71
723.  If UDP is requested, please indicate whether the service is solely
73    for the discovery of hosts supporting this protocol.
74[No, it will be for increasing video transfer performance.]
75
764.  Please explain how your protocol supports versioning.
77[The initial "hello" packet contains the protocol version, this is used for rough compatibility checks.
78Each end also sends a list of capabilities (mostly simple boolean flags), so that the other end knows what packets it is allowed to send and what extensions to these packets will be supported by the other end.]
79
805.  If your request is for more than one transport, please explain in
81    detail how the protocol differs over each transport.
82[]
83
846.  Please describe how your protocol supports security. Note that presently
85    there is no IETF consensus on when it is appropriate to use a second port
86    for an insecure version of a protocol.
87[The connections can be encrypted:
88http://xpra.org/trac/wiki/Encryption
89And there are a number of authentication modules (HMAC, etc):
90http://xpra.org/trac/wiki/Authentication]
91
927.  Please explain why a unique port assignment is necessary as opposed to a
93    port in range (49152-65535) or existing port.
94[This will make it possible for users to connect to a server without needing to know and specify what port to connect to.
95We have a proxy server which can then redirect the connection to the correct backend server automatically.]
96
978.  Please explain the state of development of your protocol.
98[It has been used in production for many years.]
99
1009.  If SCTP is requested, is there an existing TCP and/or UDP service name or
101    port number assignment? If yes, provide the existing service name and port number.
102[]
103
10410.  What specific SCTP capability is used by the application such that a
105    user who has the choice of both TCP (and/or UDP) and SCTP ports for
106    this application would choose SCTP? See RFC 4960 section 7.1.
107[]
108
10911. Please provide any other information that would be helpful in
110    understanding how this protocol differs from existing assigned services.
111[Using an assigned port can help us provide transparent multiplexing of access to graphical user sessions, just like an SSH server does for shell access.]