Re: [RPSEC] RPsec not meeting in Prague

Doug Montgomery <dougm@nist.gov> Sat, 10 March 2007 00:01 UTC

Return-path: <rpsec-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HPp1w-0001GU-6g; Fri, 09 Mar 2007 19:01:48 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HPp1v-0001GP-3R for rpsec@ietf.org; Fri, 09 Mar 2007 19:01:47 -0500
Received: from rimp1.nist.gov ([129.6.16.226] helo=smtp.nist.gov) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HPp1t-0008VN-Tr for rpsec@ietf.org; Fri, 09 Mar 2007 19:01:47 -0500
Received: from [127.0.0.1] (16-140.antd.nist.gov [129.6.140.16]) by smtp.nist.gov (8.13.1/8.13.1) with ESMTP id l2A01KOK027820; Fri, 9 Mar 2007 19:01:21 -0500
Message-ID: <45F1F551.90605@nist.gov>
Date: Fri, 09 Mar 2007 19:01:21 -0500
From: Doug Montgomery <dougm@nist.gov>
Organization: http://www.antd.nist.gov/
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Sandy Murphy <sandy@tislabs.com>
Subject: Re: [RPSEC] RPsec not meeting in Prague
References: <20070309232911.0F3903F421@pecan.tislabs.com>
In-Reply-To: <20070309232911.0F3903F421@pecan.tislabs.com>
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-NIST-MailScanner: Found to be clean
X-NIST-MailScanner-From: dougm@nist.gov
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: rpsec@ietf.org, ttauber@1-4-5.net, riw@cisco.com
X-BeenThere: rpsec@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Protocol Security Requirements <rpsec.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rpsec>, <mailto:rpsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/rpsec>
List-Post: <mailto:rpsec@ietf.org>
List-Help: <mailto:rpsec-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rpsec>, <mailto:rpsec-request@ietf.org?subject=subscribe>
Errors-To: rpsec-bounces@ietf.org


Sandy Murphy wrote:
>    o  In an environment where secured service is in the process of being
>       deployed a mechanism MUST exist to support a transition free of
>       coordinated, widespread service interruption.
>   
> OK?
>   
I was suggesting that the wording be a long the lines or requiring that
widespread (non-local?) or persistent outages not occur *specifically
because* of an incremental deployment scenario / state of partial
deployment.

Your wording above would seem to require that there not be an earth
quake in the bay area during deployment.   (i.e., doesn't make the point
of a casual relationship to  partial/incremental deployment).

Splitting hairs, I admit, but if folks think issues of incremental
deployment will be key, then worth be careful about the wording of  the
supposed  "requirement".
dougm





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