pre-agenda for SLC

[Edward Lewis <lewis@tislabs.com>]

A month from now we will have the Salt Lake City meetings.  We'll have one
multicasted hour.

Here is what I hope to cover (as a first cut):

1) Status (document traffic)
2) What do we need before sending EPP(*) to the IESG?
    a) Implementation reports
    b) Identification/not-discussion of issues
3) Perhaps an issue discussion
4) Other document progress

I've been debating discussing "Future Directions" but I think that it would
be premature, so I want to refrain from that at SLC.  (IOW - don't suggest
it!)

Oh, the '*': the set of documents that seems to be prudent to progess are
in two groups:

#2-5 and #6, referring to this numbering.  I want to start to progress all
5, but I am shying away from formally tying the TCP transport to the core
documents - just for "show."  I don't want to detract from the effort to
develop #7.

>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

Some of the issues behind progressing the documents.  First, the IESG still
hasn't commented on the updated requirements.  Second, we will have a WG
last call when appropriate.  Third, I want to get some implementation
reports to give more creedence to the completeness of the drafts.  Note -
documents can progress to some levels of standards without implementations,
so the third point is not a necessary condition.  Also, the appropriate
time to go to last call may be before SLC, during, or after.

BTW - Jaap and I will be at the Marina del Ray ICANN meeting next week.

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis                                                NAI Labs
Phone: +1 443-259-2352                      Email: lewis@tislabs.com

You fly too often when ... the airport taxi is on speed-dial.

Opinions expressed are property of my evil twin, not my employer.