To:
"Ietf-Provreg" <ietf-provreg@cafax.se>
From:
"Paul George" <pgeorge@saraf.com>
Date:
Wed, 10 Jan 2001 10:17:22 -0500
Importance:
Normal
In-Reply-To:
<v0313030cb68221546fdb@[10.33.10.145]>
Sender:
owner-ietf-provreg@cafax.se
Subject:
RE: Charter last call summary
> I suspected as much, but I feel we need to > get the IETF process moving along. As perviously mentioned, would it help to get as many people as possible together in person (& teleconference) to really get rolling? I vote for Washington, DC. ;-) Paul George SARAF Software Solutions (703)538-5666 x234 -----Original Message----- From: Edward Lewis [mailto:lewis@tislabs.com] Sent: Wednesday, January 10, 2001 9:35 AM To: Marcel Schneider Cc: Edward Lewis; Paul George; ietf-provreg@cafax.se Subject: Re: Charter last call summary At 4:04 AM -0500 1/10/01, Marcel Schneider wrote: >As Peter said: this is common ICANN/gTLD usage. We are well >aware of it :). Others have used the terminology too. (It is certainly what I am familiar with, and I haven't been woking with ICANN.) I would think that any entity/agent that is entering data into a registry could be said to be acting as a registrar, even if the entity isn't otherwise known as one. Recall too that this protocol is designed for the case that the (entity acting like a) registry and the (entity acting like a) registrar are separated by a network. If there is no separation, this protocol may not apply to the situation. There will be no mandate from the IETF that this protocol be used in registration. Such a mandate may come from a registrar accrediting organization, but the IETF process can't be contingent on that. >Sorry for not answering quicker but we had a night in between >in Switzerland :). I suspected as much, but I feel we need to get the IETF process moving along. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Edward Lewis NAI Labs Phone: +1 443-259-2352 Email: lewis@tislabs.com Dilbert is an optimist. Opinions expressed are property of my evil twin, not my employer.