This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[ncc-services-wg] Destruction of trust
- Previous message (by thread): [ncc-services-wg] Destruction of trust
- Next message (by thread): [ncc-services-wg] Destruction of trust
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sander Steffann
sander at steffann.nl
Thu Jul 19 17:51:05 CEST 2012
Hi, > What shocked me when I got the attached template was how the English was not grammatically correct and how unwilling the NCC was willing to make any change to the template. > > Just taking section II: > II. The LIR made an appropriate control to the correctness of the information provided by the Legacy Resource Holder and wishes to register the Legacy Resources on their LIR account on behalf of the Legacy Resource Holder. > > I had suggested the more correct form of: > II. The LIR has established the correctness of the information provided by the Legacy Resource Holder and wishes to register the Legacy Resources on their LIR account on behalf of the Legacy Resource Holder. > > but was turned down (as well as the 4 other changes I suggested to sections 2+3). This is a different template than the one from RIPE-452. Are there multiple EndUser<->LIR contract templates in use? > This template was never brought to the membership, but is presented as a "done deal" that every legacy holder has to sign. Yes, I can't remember any policy proposal that specified these requirements. Where do they come from? Thanks, Sander
- Previous message (by thread): [ncc-services-wg] Destruction of trust
- Next message (by thread): [ncc-services-wg] Destruction of trust
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]