Dear Tobias: > I think it's the other way around. The byte-separated values are all in > little-endian encoding and d_i and d_r are simply given as hex-encoded > numbers (in their natural big-endian encoding as you'd write a decimal > number). So I think the test vectors are correct.
I suppose I didn't interpret it that way given the text before d_i and d_r says "encoded in little-endian format" and there is no leading "0x" to indicate an integer versus a string. The test vectors in RFC 7748 are written similarly as a hex string without leading "0x" and must be decoded as strings (with decodeLittleEndian or decodeUCoordinate), rather than being interpreted as an integer. Given the tight relationship with RFC 7748, if RFC 8031 uses the same notation for the d_i and d_r values but must be interpreted differently is grounds for an errata, in my opinion. I suppose that clarification of the text would be acceptable. Best regards, Jonathan _______________________________________________ IPsec mailing list IPsec@ietf.org https://www.ietf.org/mailman/listinfo/ipsec
