I am trying to implement elliptic curve point addition in hardware for NIST p256 and p384 curves. I have noticed the following issue with the suggested NIST routines:
Routine 2.2.7 of http://www.nsa.gov/ia/_files/nist-routines.pdf point addition $R = S + T$ is not valid for the case $S = T$ ( this would be a point doubling).
Is it correct to state that before performing point addition, you must first check if the two points are the same point and if they are the same point then perform a point doubling instead? If so how do you test if the points are the same?
I am using Jacobian coordinates for my intermediate computations so a given point may have a large number of congruent representations: $(x,y) => (X/Z^2,Y/Z^3,Z)$ e.g. a point $(16,64,1) ≡ (4,4,2) ≡ (p+16, p+64,1), …$.
How does one determine if two points are the same if they have a large number of possible representations?
A naive method could be that before performing point addition to convert back to affine coordinates and reduce all coordinates to the range $0 <= x < p$ so then both points have a unique representation but this defeats the purpose of using projective coordinates which is to avoid modular inverse during intermediate computation. In this case it would be better to do all computation in affine coordinates. There must be an easier way to test if $S ≡ T$ without doing this but I have not found many references to this problem. How is this handled in the real world?
In addition to using Jacobian coordinates, all of my intermediate results are not bounded by $0 <= n <= p$ but are instead bounded by $0 <= n <= M*p$ where $1 <= M < 2^r$ which is because of my modular multiplication algorithm which has not posed an issue except if trying to determine if the two points are congruent. This increases the search space in affine coordinates to M possible congruent points.
Does there exist a safe addition algorithm for generalized curves?
Inb4 use Edwards curves: I am required to support NIST p256 and p384 curves so I can't pick arbitrary curves.