Page History
...
For other places see: https://tinyurl.com/53s57jmh
Info |
---|
PROPOSED AGENDA
BACKGROUND DOCUMENTS Before the meeting, please review the following:
|
Tip | ||
---|---|---|
| ||
Apologies: Zak Muscovitch (BC), Steinar Grøtterød (At-Large), Daniel Nanghaka (At-Large) Alternates: Arinola Akinyemi (BC), Lutz Donnerhacke (At-Large), Raymond Mamattah (At-Large) |
Info | ||
---|---|---|
| ||
GNSO transcripts are located on the GNSO Calendar |
Note |
---|
Notes/ Action Items Action Items: Discussion of Outstanding Items on TAC: 1. Recommendation 7 (TAC Security) Jim Galvin to suggest revisions to Sarah Wyld’s suggested text for WG members to review. Previous Action Items: 1. WG members are encouraged to review the overview of proposed response to Charter Question h2 (see page 13 and 14 here [docs.google.com]) and provide comments and/or suggestions. Notes: Transfer Policy Review Phase 1 - Meeting #44 1. Roll Call & SOI updates 2. Welcome & Chair updates 3. Upcoming milestones and deliverables for Initial Report: Initial Report Delivery 15 June 2022: Key Dates: Upcoming Working Group Meetings: Highlights: Row 11 -- Formerly Recommendation 3, now Recommendation 7 -- From Sarah Wyld, suggested text for Recommendation 7 (TAC Security) – See recent email: Here is the current shared draft text [docs.google.com]: Row 12 -- Additional Candidate Recommendation xx under CQ b1: If a Gaining Registrar requests a transfer and an inter-registrar transfer lock is in place, the transfer must not proceed. Row 13 -- Response to CQ b2: Compliance input: For Contractual Compliance to be able to enforce the requirements, all requirements must be clearly enumerated and described within the text of the policy. Row 14 -- SME input on Recommendation 6.2: The Registry MUST securely store the TAC per the requirements specified in recommendation 3. Recommendation text: “When the Registrar of Record sets the TAC at the Registry, the Registry MUST securely store the TAC using a one-way hash that protects the TAC from disclosure.” Row 15 -- input on Recommendation 6.3: Compliance recommends detailing how this information must be provided and that the provision of this information must be documented. Recommendation text: “When the Registrar of Record provides the TAC to the RNH or their designated representative, the Registrar of Record MUST also provide information about when the TAC will expire.” Row 16 -- SME input on Recommendation 6.3: Consider developing standard easy to understand language for registrants around this additional info about when the TAC will expire, etc. Row 17 -- Formerly Recommendation 9, now Recommendation 11: Compliance input: If this is an obligation to be added to the Transfer Policy for registries, Compliance recommends that the text in the policy explains what “clear” means (what actions this entails) so that Compliance is able to enforce it against registries where applicable. Recommendation text: “The working group recommends that the TAC MUST be “one-time use.” In other words, it MUST be used no more than once per domain name. The Registry Operator MUST clear the TAC as part of completing the successful transfer request.” Row 18 -- Formerly Recommendation 11, now Recommendation 13: SME input on Recommendation 11.1: Suggestion to use hours instead of calendar days to avoid confusion. Recommendation text: 13.1: A standard Time to Live (TTL) for the TAC MUST be 14 calendar days from the time it is set at the Registry, enforced by the Registries. 5. AOB |