Support/Handbook/NewPointsCalculation/grafix
Re-Appliance Process of Assurance Points
Record
Date of Assurance
Awarded
Points
Assurance Method
Real given Assurances
1
2005-07-01
0 !!
150
Thawte
150 pts Thawte transfer
2
2005-08-01
0 !!
0
F2F
150 pts real F2F superassurance (150-150=0)
3
2006-01-01
0 !!
0
F2F
35 pts real F2F assurance
4
2006-08-01
0 !!
0
F2F
20 pts real F2F assurance
2006-08-30
date where column awarded was inserted
5
2006-09-01
35
0
F2F
35 pts real F2F assurance
...
reflects all assurances given after 2006-08-30
6
2011-11-11
35
0
F2F
35 pts real F2F assurance
Result OLD
old count
150
Result NEW
Thawte removal
70 !!
150 + 35 + 20 pts missing from record 2-4
Records #2 - #4 can be revoked (by revoke assurance procedure) ... (the so called 0:0 case)
by request from Assuree or by request from Assurer
this results in the interim state ...
(it makes no difference to the points count if the 0:0 records are in the table or not)
Record
Date of Assurance
Awarded
Points
Assurance Method
Real given Assurances
1
2005-07-01
0 !!
150
Thawte
150 pts Thawte transfer
2006-08-30
date where column awarded was inserted
5
2006-09-01
35
0
F2F
35 pts real F2F assurance
...
reflects all assurances given after 2006-08-30
6
2011-11-11
35
0
F2F
35 pts real F2F assurance
Result OLD
old count
150
Result NEW
Thawte removal
70 !!
150 + 35 + 20 pts missing from record 2-4
... and can be re-applied by the old assurers (if they have their old CAP forms at hand and if assurers responds)
Record
Date of Assurance
Awarded
Points
Assurance Method
Real given Assurances
1
2005-07-01
0 !!
150
Thawte
150 pts Thawte transfer
2006-08-30
date where column awarded was inserted
5
2006-09-01
35
0
F2F
35 pts real F2F assurance
...
reflects all assurances given after 2006-08-30
6
2011-11-11
35
0
F2F
35 pts real F2F assurance
7, old 2
2005-08-01
35 !!
0
F2F
150 pts real F2F superassurance, only 35 pts can be re-awarded under AP (better then nothing)
8, old 3
2006-01-01
35
0
F2F
35 pts real F2F assurance
9, old 4
2006-08-01
20
0
F2F
20 pts real F2F assurance
Result OLD
old count
150
Result NEW
Thawte removal
160 limited to 100
points re-awarded from old records 2-4
Other Scenarios
1. Yellow lines, but no action needed
Record
Date of Assurance
Awarded
Points
Assurance Method
Real given Assurances
1
2005-07-01
0 !!
35
F2F
35 pts regular F2F assurance
2
2005-07-15
0 !!
35
F2F
35 pts regular F2F assurance
3
2005-07-16
0 !!
20
F2F
20 pts regular F2F assurance
4
2005-07-17
0 !!
10
F2F
35 pts regular F2F assurance, rounded down to 10 (limit 100 reached)
5
2005-08-01
0 !!
50
F2F
150 pts real F2F superassurance, (150-35-35-20-10=50) 50 pts to count as EP
6
2006-01-01
0 !!
0
F2F
35 pts real F2F assurance
7
2006-08-01
0 !!
0
F2F
20 pts real F2F assurance
2006-08-30
date where column awarded was inserted
8
2006-09-01
35
0
F2F
35 pts real F2F assurance, rounded down to 0, 100 pts limit reached
Result OLD
old count
150
Result NEW
Thawte removal
185 limited to 100 x1
There are some missing points but account isn't effected by the Thawte points removal
x1) 185 pts from rows: 1 (35), 2 (35), 3 (20), 4 (10), 5 (50), 8 (35)
This scenario describes regular F2F assurances, but this account has also yellow lines. The user isn't effected by the Thawte points removal. Row 4, there are 25 pts missing, but this doesn't effects the total count. Row 5, 100 pts are missing from the given 150 pts. If this assurance becomes revoked, the assurer can re-apply upto 35 pts (Super-Assurance points cannot be inserted into the system any more). So the counting 50 pts is more then a re-appliance. As there is no difference of AP and EP in the 150 Super-Assurance, this assurance counts 50 assurance pts after the Thawte points removal as the counting 50 doesn't acceed the 100 pts limit. The points on row 6 and 7 can be re-applied too, but there is no need for action in this case. The user has enough points to not fall below the 100 pts or 50 pts limit for beeing an assurer or to issue certs with the name in it.
This example shows the handling of assurances with > 35 points. If a 150 points assurance needs to be recalculated, the 150 points becomes splitted into 100 Assurance points and 50 Experience points. If in an old assurance counting not all of the 150 points are counted as the user has some points before, the difference upto 150 points has been applied. This difference value is now the value that can be re-calculated. If the count of 150 pts falls below 100 points this value counts as Assurance points in the new calculation. If the difference value exceeds 100 points, all points over 100 points are now added as Experience points (Experience points other way) in the new calculation.
2. Yellow lines, action needed some way
Record
Date of Assurance
Awarded
Points
Assurance Method
Real given Assurances
1
2005-07-01
0 !!
30
F2F
30 pts regular F2F assurance
2
2005-07-02
0 !!
60
Thawte
60 pts Thawte transfer
3
2005-08-01
0 !!
60
F2F
150 pts real F2F superassurance, rounded down to 60 pts (150-30-60=60)
4
2006-01-01
0 !!
0
F2F
35 pts real F2F assurance
2006-08-30
date where column awarded was inserted
Result OLD
old count
150
Result NEW
Thawte removal
90 x1
There are some missing points, but missing points of Superassurance cannot be re-applied. Only 35 pts on row 4 as regular F2F assurance
x1) 90 pts from row 1 and 3
This scenario describes a micture of F2F + Super-Assurance assurances and Thawte points transfer. But this account has also yellow lines. The only assurance that can be reapplied is the row 4 assurance. Missing points from the Super-Assurance cannot be reapplied.
This scenario also describes the handling of > 35 pts values. The 150 pts assurance from row 3 counts 10 Assurance points to fill the 100 pts limit + 50 Experience points (sum = 60). In the new calculation, these 60 points are now counted as full 60 Assurance points, as there is no measure how many points relate to Assurance points and how many points relate to Experience points. The general rule in recalculation is, that all points > 100 points are added to the Experience points counting (Experience points other way). So 60 points is less than 100 points, so this counts as Assurance points in the new calculation.
3. No Yellow lines, but action needed some way
Record
Date of Assurance
Awarded
Points
Assurance Method
Real given Assurances
1
2005-07-01
0 !!
60
Thawte
60 pts Thawte transfer
2
2005-07-02
0 !!
35
F2F
35 pts regular F2F assurance
3
2005-08-01
0 !!
5
F2F
35 pts real F2F assurance, rounded down to 5 pts (100-60-35=5)
2006-08-30
date where column awarded was inserted
Result OLD
old count
100
Result NEW
Thawte removal
40 x1
There are some missing points, in row 3, that can be re-applied. Good for addtl. 30 pts as regular F2F assurance
x1) 40 pts from row 2 and 3
This scenario describes a discrepance between awarded and counted assurance points without a yellow line marker (!). The assurance that can be reapplied is the row 3 assurance. Original awarded 35 pts, only 5 counts, so addtl. 30 points can be added on re-applying this assurance. This example also shows, that the user is falling below 2 levels: the 100 pts level (good for codesigning and becoming assurer) AND below the 50 pts level (good for issuing certs with the users name in it). At least with a repair, this user can retain the 50 pts level.