On 7 Jun 2006, at 04:52, Brian E Carpenter wrote:
I wouldn't want to exclude the operational and implementer community
either. I think the phrase used in draft-iab-rfc-editor is probably
the best short form: "the Internet research and engineering
community." Note of course that there is no way
Ran,
RJ Atkinson wrote:
On 5 Jun 2006, at 02:54, Brian E Carpenter wrote:
Earlier, Ran Atkinson wrote:
It has NOT been the case in the past that IETF was the community
in control of RFC-Editor. In fact, that would represent a major,
and in many people's view highly undesirable, change.
Hist
nevermind. figured it out.Phil Maceri 10247 Barlow CrossingPerrysburg, OH 43551Cell: 248-250-1194Home: 586-435-9542
> Date: Mon, 5 Jun 2006 15:35:41 +0200> To: franck@sopac.org; [EMAIL PROTECTED]> From: [EMAIL PROTECTED]> CC: [EMAIL PROTECTED]; ietf@ietf.org> Subject: Re: I
> From: [EMAIL PROTECTED]> CC: [EMAIL PROTECTED]; ietf@ietf.org> Subject: Re: IETF, IAB, & RFC-Editor> > Dear Franck,> the reference is not ISOC nor the IETF. The reference is the user. > Hence, the networking solution people may use on the digital > ecosystem they built
Dear Franck,
the reference is not ISOC nor the IETF. The reference is the user.
Hence, the networking solution people may use on the digital
ecosystem they built and own in common. The difficulty is to evaluate
from past and present IETF/ISOC contributions their future cons and
pros; and the m
On 5 Jun 2006, at 02:54, Brian E Carpenter wrote:
Earlier, Ran Atkinson wrote:
It has NOT been the case in the past that IETF was the community
in control of RFC-Editor. In fact, that would represent a major,
and in many people's view highly undesirable, change.
Historically, RFC-Editor has se
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
I suppose you are aware of the next ISOC board meeting in Marrakesh is
on the 1/2 July 2006 (www.isoc.org)
While I have kept an eye on the IETF list for qite some time, I still
consider myself a newbie in the relationship ISOC/IETF. I'm trying
Ran,
RJ Atkinson wrote:
Previously, someone wrote:
I finished reading the RFC editor document and have one major concern.
Ultimately, the rfc-editor function needs to be accountable to the
IETF community because we're the ones paying for it.
Incorrect. As I pointed out some weeks ago, and