Page History
...
Info |
---|
PROPOSED AGENDA
BACKGROUND DOCUMENTS |
Tip | ||
---|---|---|
| ||
Info | ||
---|---|---|
| ||
GNSO transcripts are located on the GNSO Calendar |
Note |
---|
Notes/ Action Items Action Items and main discussion point
o Priorities: 1, 2, 3, 4, and 5 & ICANN Notes
o Impression Document Registrar Feedback Item 3 discussion
o Proposed increase in character limit from 1000 to 2000 o Org informed that it can be implemented fairly easily in an upcoming enhancement cycle. o SC asked if there are security concerns regarding this update? Org informed that there might be a legal concern reg amount of data but no security concern. o Proposed language to better explain what “expedited” means in RDRS UI o Org informed that “expedited” at the determination of the requestor. o Org will add language to indicate that in an upcoming enhancement cycle. 3.AOB
o How should Rrs report abuse of RDRS when requestors claim to be a certain type of requestor (like LEA) but they are not? o RDRS pilot does not include an abuse investigator. o Disabling the requester account could be a possible solution? Problem not likely to go away by disabling account, but SC indicates it’s important to address the abuse o Is this a common problem? RDRS request or impostors? No data on this as there is no way to track. Within Tucows requests 20% of all RDRS requests are miscategorized. 24% of RDRS requests labeled as LEA are miscategorized o Org could provide more information in a future version of the FAQ to clarify LEA requests and submission from those claiming to be LE who are not o SC suggested a report function on RDRS.
o SC suggested adding a report on jurisdiction where LEA requests are coming from? o Org could make address mandatory (see impressions document Priority 1) in the request form which could provide that information? o Request to be added to “wishlist” Impressions document by SC. |