Thanks Erica for turning this around so quickly.
Attached are two additional edits to the updated document that you sent
earlier today. One corrects a typo; the other adds the example discussed
during today's call.
Any further comments from this team should be applied to the attached
redline as the latest version.
Best, Lisa
At 11:46 AM 11/6/2017, Erica Varlese wrote:
Hi all,
I've just added in our edits from today's call. You can find the updated
document attached.Â
If there's any additional changes (or if you catch any typos), I'd be
glad to update :)
Thanks!
Erica
Erica Varlese |Â .blog Shepherd @ KKWT
Email: erica@my.blog
Skype: evarlese
On Mon, Nov 6, 2017 at 4:05 PM, Lisa Phifer
<lisa@corecom.com>
wrote:
- All, below please find notes and action
items from our final DT4 call today.
- Thanks everyone for your participation in this drafting team
-
- Best, Lisa
- 1) Reactions to ICANN60 feedback on RDS purposes overall
- 2) Resolution of specific comments on this purpose:
- Â Â Â a) Is merchantability about reputation more than
ownership of the domain name prior to possible purchase?
- Extend example of home purchase with domain name example - e.g.,
reputation of prior owner/prior use. Make home purchase sub-bullet. Add
new sub-bullet re: importance of reputation of previous registrant/use,
after domain name data has been updated by broker during sale.
- Â Â b) Should third party buyer be potential registrant no,
because there are many scenarios where the party making contact for
purchase will not end up being the registrant
- Buyer is broader category; irrelevant to call the buyer the potential
registrant. That might be too limiting later. eg. broker, proxy,
etc
- Â Â c) Why is trademark infringement part of this purpose?
Perhaps narrow text to indicate this is for cases in which the situation
is resolved through purchasing the domain name
- Delete "If legal action is required (i.e., in cases of trademark
infringement)" from Data - Registrant's Country. The country
provides jurisdictional context for local laws and procedures that may
apply throughout the purchase transaction.
- 3) Edits to address action item (see a-d above)
- Â Â a) Single-sentence summary of this purpose (insert below
Purpose Name in template):
- Information collected to enable contact between the registrant and
third party buyer to assist registrant in proving and exercising property
interest in the domain name and third party buyer in confirming the
registrant's property interest and related merchantability
- Â Â b) Are the tasks/users identified by your team so diverse
and distinct that they may be more than one purpose? If so, split them up
and describe each purpose separately
- This purpose does not need to be split apart; the purpose applies to
purchase/sale of any domain name.
- Â Â c) Which purposes covered by other teams are closely
related to or overlap the purpose(s) covered by your team?
- There are legal actions that may result in buying the domain name,
but this is distinct enough that it shouldn't be conflated. Domain name
control may come into play after a sale to effectuate a transfer but is
not the sale itself.
- Â Â d) Is there any data collected specifically for the stated
purpose? Or does that purpose use only data collected for other
purposes?
- Â Â Â Â Â Â - Delete legal contact from list - more relevant to
other purposes.
- Â Â Â Â Â Â - Team discussed and agreed that all remaining data
listed for this purpose is potentially used by other purposes as
well.
- 4) Plan to complete drafting team's work:
- Action: Erica to apply final edits by Wednesday 8 Nov and
send to DT4 mailing list
- Action: All DT4 members to review and finalize output on
Thursday 9 Nov
- Action: Lisa to submit final output to WG no later than
Friday 10 Nov
- Action: Fabricio to present to WG on Tuesday 14 Nov call
- Â Â Â Â Â Â Â Â Â Â Â Â Benjamin will also be on call but with
limited audio
- _______________________________________________
- Gnso-rds-pdp-4 mailing list
- Gnso-rds-pdp-4@icann.org
-
https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-4
Content-Type: application/msword;
name="DraftingTeam4-DNPurchaseSale-Purpose-v7-clean.doc"
Content-Disposition: attachment;
filename="DraftingTeam4-DNPurchaseSale-Purpose-v7-clean.doc"
X-Attachment-Id: f_j9ojf2c20