!43 BoF @ -53; co-chair status; whois-fix status

Oki all,

For those who aren't on the !43 list (details below), a few days ago Leslie
Daigle ([email protected]) sent out a BoF announcement for -53. In
the proposed charter for the BoF (Cross-Registry Information Service Protocol
(CRISP)), backwards compatibility with RFC 954 is listed as a non-goal.

Shortly before -52, when I realized that both Dave and I had a beneficiary
relationship with the same company, incidently a whois:43 operator, and at
some risk of 3rd-party interference, I sent mail to this list announcing
that for family reasons I was cutting back on non-essential travel, and would
not travel from Maine to Salt Lake.

While my family reasons isn't likely to change till mid-year, I'm happy to
announce that the shared beneficiary relationship problem has been resolved,
and there is no risk of 3rd-party interference. I propose to continue to "co"
and move the -51 BoF and this mailing list to a working group -- with all of
your explicit, or at least tacit consent.

There is still, as I wrote then (11/9/01) still a charter to complete, and
time-line drift to correct for, assuming that the dates and deliverables were
approximately correct.

I'll still taking updates to the chart we started at London, the per-ccTLD
details. I'd like to se one for the per-RIR and per-LIR details. Anyone???

Eric


This is "below":

Discussions about Internet infrastructure directory service protocols and
requirements that aren't whois. <ietf-not43.lists.research.netsol.com>
mailto:[email protected]?subject=subscribe