Re: [RPSEC] BGP Security Requirements v08

Joe Touch <touch@ISI.EDU> Fri, 13 July 2007 16:40 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 1I9OCR-0004mj-H4; Fri, 13 Jul 2007 12:40:59 -0400
Received: from rpsec by megatron.ietf.org with local (Exim 4.43) id 1I9OCP-0004mY-TV for rpsec-confirm+ok@megatron.ietf.org; Fri, 13 Jul 2007 12:40:57 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I9OCP-0004mL-IY for rpsec@ietf.org; Fri, 13 Jul 2007 12:40:57 -0400
Received: from vapor.isi.edu ([128.9.64.64]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I9OCA-0008RK-At for rpsec@ietf.org; Fri, 13 Jul 2007 12:40:57 -0400
Received: from [128.9.168.63] (bet.isi.edu [128.9.168.63]) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id l6DGdbmd006190 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 13 Jul 2007 09:39:38 -0700 (PDT)
Message-ID: <4697AAC9.1060604@isi.edu>
Date: Fri, 13 Jul 2007 09:39:37 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
MIME-Version: 1.0
To: curtis@occnc.com
Subject: Re: [RPSEC] BGP Security Requirements v08
References: <200707131632.l6DGW1b3021820@harbor.brookfield.occnc.com>
In-Reply-To: <200707131632.l6DGW1b3021820@harbor.brookfield.occnc.com>
X-Enigmail-Version: 0.95.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: rpsec@ietf.org, Tony Tauber <ttauber@1-4-5.net>
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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Curtis Villamizar wrote:
> In message <4697224A.5050901@isi.edu>
> Joe Touch writes:
>>  
>> Curtis Villamizar wrote:
>> =2E..
>>> GTSM is very effective in protecting against certain high volume
>>> attacks that would cripple infrastructure protected by cryptographic
>>> means alone.  From a practical standpoint GTSM used alone may be
>>> inadequate as a solution (though some ISPs might contest even that)
>>> but it is a required part of any solution in an ISP environment.
>>> =20
>>> Curtis
>>  
>> I agree that DOS attacks benefit from protections that help reduce the
>> impact of attack traffic; GTSM falls into that category - it's clearly a
>> useful part of a DOS solution, but DOS protection isn't cryptographic
>> protection. The bulk of the BGP security requirements document focuses
>> on cryptographic issues - not DOS protection. It's worth noting the
>> difference, but not lumping the solutions together.
>>  
>> Joe
> 
> 
> Joe,
> 
> It would be most accurate most helpful to acknowledge the strengths
> and weaknesses of both and then define the limit of scope of your
> work. 

Agreed...

> So we seem to be in violent agreement about the difference between
> crypto solutions and DOS solutions.  Its just a matter of the wording
> in the draft not adequately acknowledging the part of the problem
> space that is not addressed.

Agreed!

...
> The way the draft reads now is GTSM, TCP/MD5, etc are all "prior work"
> and the reader might interpret this to mean that work meeting these
> BGP requirements supercede that prior work.  It doesn't state
> otherwise and it should.

Yes - that's the sort of thing I'm hoping to address in a brief paragraph.

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGl6rJE5f5cImnZrsRAnOpAJ998nCytW9y2YMhdb7bZaCgwOS6pwCeKQqh
JfW0JgqK0flx+06hGhgjiyU=
=chEy
-----END PGP SIGNATURE-----


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