Hmm. Try to ask on another way: There are several variable length
opaques throughout the draft, but - as far as I can see - the statement
"there is an extra length byte on the wire" (what seems logical to me,
btw) is provided only in conjunction with the RessourceID description.
Does this statement implicitly apply to all other variable length
opaques too?
Sorry, if I wasn't specific enough with my question. I hope, it is clear
now.
Regards
Eric Rescorla schrieb:
Thus, the 3-byte value
"Foo" would be encoded as: 03 46 4f 4f.
</quote>
In fact it should be "encoded" as "03 46 6f 6f", or it should be named "FOO"
:) (BTW: Those kind of errors in your draft is on the level I'm able to
discover... :))
Question behind: May I assume, that every "opaque" value, as far as no
explicitly determined in length, is preceded by a length byte (or more bits)
on the wire?
There should never be a simple opaque that isn't either a fixed-length
string (opaque foo[9]) or a veariable length vector (opaque foo<0..255>).
-Ekr
_______________________________________________
P2PSIP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/p2psip
