Re: Suggestion for IETF Critical Infrastructrei WG.

"todd glassey" <tglassey@earthlink.net> Thu, 05 October 2006 19:45 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVZAE-0004I4-LX; Thu, 05 Oct 2006 15:45:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVZAD-0004Hz-Mf for ietf@ietf.org; Thu, 05 Oct 2006 15:45:49 -0400
Received: from elasmtp-banded.atl.sa.earthlink.net ([209.86.89.70]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GVZAC-0005DI-Dy for ietf@ietf.org; Thu, 05 Oct 2006 15:45:49 -0400
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=JRvor+3UUcrZMdnzCi5sJ6zwaZ0IYOqQMHD5d7TTM+RgUXNA5nsjJybGFAWmcTko; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [4.246.48.51] (helo=gw) by elasmtp-banded.atl.sa.earthlink.net with asmtp (Exim 4.34) id 1GVZ9q-0007Tj-R6; Thu, 05 Oct 2006 15:45:27 -0400
Message-ID: <022301c6e8b6$d060bb10$010aa8c0@home.glassey.com>
From: todd glassey <tglassey@earthlink.net>
To: ietf@ietf.org, Frank Ellermann <nobody@xyzzy.claranet.de>
References: <006b01c6e89d$0e12f230$010aa8c0@home.glassey.com> <45255BF5.22C3@xyzzy.claranet.de>
Date: Thu, 05 Oct 2006 12:45:21 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1807
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec790a4fc1c0d71ce49da473e0e15150a01b350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 4.246.48.51
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc:
Subject: Re: Suggestion for IETF Critical Infrastructrei WG.
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org

So then Frank -  this is an opportunity to not only correct that, but also
to create a CI nexus which would be a good thing for the IETF to focus on I
think.

At least from a Business Development venue, it seems to offer a whole
possibility of a new CI Area in the IETF as well.  That would mean a new AD
and a new seat for the IESG as well as probably a bunch of WG's  which would
popup to address standardization of many things that governments of the
World are frantically trying to accomplish now.

t
----- Original Message ----- 
From: "Frank Ellermann" <nobody@xyzzy.claranet.de>
To: <ietf@ietf.org>
Sent: Thursday, October 05, 2006 12:24 PM
Subject: Re: Suggestion for IETF Critical Infrastructrei WG.


> todd glassey wrote:
>
> > Any commentary?
>
> For me it sounds like a proposal to reinvent the IAB as WG.
> Some draft-iab-whatever and resulting RFCs like 4690 are
> quite interesting, examples:
>
> draft-iab-auth-mech-05
> draft-iab-dns-choices-03
> draft-iab-dos-05
> draft-iab-messaging-report-01
>
> That they tolerated the simultaneous SHOULD NOT vs. SHOULD
> "experiments" with critical e-mail was a counter-example.
>
> Frank
>
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf