WARNING: This server is unstable and will be retired in the next days.
If you want to keep this forum available, please request immediately a migration
on the Nabble Support forum.
Forums that don't receive any migration request will be deleted forever.
** section 6 ABNF clash between port and obfport is still a nasty
IMO obfport should start with a mandatory '_'. We have to special-case
it anyway to parse the ALPHA component might as well bring it inline
with the rules for obfuscated node and obfuscated identifier ABNF.
Alternatively why bother with obfport at all?
As I understand/recall it the use-case was to enable for= or by= with
a visible IP and obfscated/private port.
Would not allowing one of the listed field values be obfuscated
identifier be better? that way the port can be omitted entirely from the
for= and whatever detail the hop needs to obfuscate and pass on can be
encoded inside the obfuscated identifier token.