The type field of the DCUtR message definition should not be
optional, as a message without a Type is useless. Instead it should
be required.
See also circuit relay v2 specification using required for type.
message HopMessage {
enum Type {
RESERVE = 0;
CONNECT = 1;
STATUS = 2;
}
required Type type = 1;
message StopMessage {
enum Type {
CONNECT = 0;
STATUS = 1;
}
required Type type = 1;
If I am not mistaken, none of the libp2p implementations have released a DCUtR implementation yet, thus we can still easily make this change. Correct @marten-seemann?
The
type
field of the DCUtR message definition should not beoptional
, as a message without aType
is useless. Instead it should berequired
.See also circuit relay v2 specification using
required
fortype
.If I am not mistaken, none of the libp2p implementations have released a DCUtR implementation yet, thus we can still easily make this change. Correct @marten-seemann?