Re: [weirds] Adopting documents

["Hollenbeck, Scott" <[e-mail]>]

From: [e-mail] [mailto:[e-mail]] On Behalf Of Murray S. Kucherawy
Sent: Wednesday, May 16, 2012 2:41 PM
To: [e-mail]
Subject: [weirds] Adopting documents

Greetings all, welcome to WEIRDS!

For our first trick, and while your co-chairs and AD plan out strategy, we'd like to have some discussion about which document(s) need to be adopted into the working group with the understanding that we may not publish all of them, some them could best be merged, some may need more work, etc.

So for the sake of getting that conversation started (and to get the datatracker to show everything that's been done so far on one page), I've put all of the following into Call For Adoption state for WEIRDS:

https://datatracker.ietf.org/doc/draft-designteam-weirds-using-http/
https://datatracker.ietf.org/doc/draft-kucherawy-weirds-requirements/
https://datatracker.ietf.org/doc/draft-sheng-weirds-icann-rws-dnrd/
https://datatracker.ietf.org/doc/draft-hollenbeck-dnrd-ap-query/
https://datatracker.ietf.org/doc/draft-newton-et-al-weirds-rir-query/
https://datatracker.ietf.org/doc/draft-sheng-weirds-icann-rws-dnrd/

Let's have some suggestions about which ones to adopt, which ones might be combined, which ones we should drop, etc., given the charter that got approved.  When we've converged on that, we can formally adopt the ones we select (or new ones that result) and get moving.

My take, keep:

draft-designteam-weirds-using-http
draft-hollenbeck-dnrd-ap-query
draft-newton-et-al-weirds-rir-query
draft-newton-et-al-weirds-rir-json-response

Drop:

draft-kucherawy-weirds-requirements: We can refer to RFC 3707 for requirements.

draft-sheng-weirds-icann-rws-dnrd: This draft will likely be replaced by draft-hollenbeck-dnrd-ap-query and at least one other draft that doesn't yet exist that describes name registry responses.

Scott