Stefan Winter wrote:
> Attribute parsing should be easier with this option 1 - Length can
> always serve as a pointer to the next attribute, with explicit namespace
> ID. With option 2, attribute delimiters are only within NS-Specific, and
> Length points to the Namespace, if any. That makes two code paths, one
> for parsing NSID delimiters, and one for parsing attributes.
My $0.02 is that it's easier to do:
Parse NS stuff
NS1 - parse protocol-specific 1
NS2 - parse protocol-specific 2
The alternative is:
Parse NS stuff
NS1 - parse NS1-specific variant of protocol 1
NS2 - parse NS2-specific variant of protocol 2
I don't want to write yet another "almost RADIUS" or "almost Diameter"
encoder/decoder. I'd like to re-use the existing code where possible.
But the current consensus of the WG seems to be against this opinion.
Oh well.
Alan DeKok.
_______________________________________________
Emu mailing list
Emu@ietf.org
https://www.ietf.org/mailman/listinfo/emu
