To:
"'Edward Lewis'" <lewis@tislabs.com>, ietf-provreg@cafax.se
Cc:
jaap@sidn.nl
From:
"Hollenbeck, Scott" <shollenbeck@verisign.com>
Date:
Thu, 25 Oct 2001 14:22:23 -0400
Sender:
owner-ietf-provreg@cafax.se
Subject:
RE: Trafficking documents
> -----Original Message----- > From: Edward Lewis [mailto:lewis@tislabs.com] > Sent: Thursday, October 25, 2001 1:27 PM > To: ietf-provreg@cafax.se > Cc: lewis@tislabs.com; jaap@sidn.nl > Subject: Trafficking documents > > > The WG has a few internet drafts under consideration: > > 1) The requirements > 2) EPP base > 3) EPP domain mapping > 4) EPP host mapping > 5) EPP contact mapping > 6) EPP over TCP > 7) EPP over BEEP > 8) Containers in EPP > 9) Definitions > > Doc #1 has been returned to the IESG. I haven't heard any feedback on that > yet. > > It appears to me that we want to advance (when ready) documents #2,3,4,5 as > a unit, and docs #6,7 optionally as the same unit - or at least separately > but at close to the same time. I'd rather not explicitly tie #6 and #7 given the relative maturity of the two documents. I suspect that #6 is closer to being "done" than #7, so it may make sense to move #6 forward as part of the #2-#5 package so that there's at least one transport document to complete the package. 2-5 without a transport document isn't a complete package. There haven't been very many comments directed towards epp-BEEP; I'd like to know if that's due to folks being happy with the draft, not having looked at it yet, or if there's a lack of interest. I've provided some comments based on a cursory read, but I haven't yet had a chance to give it the more thorough reading that's needed for me to feel as comfortable with it as I do with epp-TCP. -Scott-