IETF Logo Mail Archive

Re: [OSPF] FW: Using dynamically derived Traffic Keys for Routing Protocols

Manav Bhatia <manav.bhatia@alcatel-lucent.com> Thu, 14 April 2011 05:11 UTC

Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: ospf@ietfc.amsl.com
Delivered-To: ospf@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id E67AEE07FC for <ospf@ietfc.amsl.com>; Wed, 13 Apr 2011 22:11:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.961
X-Spam-Level:
X-Spam-Status: No, score=-5.961 tagged_above=-999 required=5 tests=[AWL=0.638, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZwQxo7GJ66qR for <ospf@ietfc.amsl.com>; Wed, 13 Apr 2011 22:11:43 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfc.amsl.com (Postfix) with ESMTP id 24394E0839 for <ospf@ietf.org>; Wed, 13 Apr 2011 22:11:26 -0700 (PDT)
Received: from inbansmailrelay2.in.alcatel-lucent.com (h135-250-11-33.lucent.com [135.250.11.33]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id p3E5BMRa002727 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 14 Apr 2011 00:11:24 -0500 (CDT)
Received: from INBANSXCHHUB02.in.alcatel-lucent.com (inbansxchhub02.in.alcatel-lucent.com [135.250.12.35]) by inbansmailrelay2.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p3E5BKW8029606 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 14 Apr 2011 10:41:20 +0530
Received: from [135.250.26.32] (135.250.19.8) by INBANSXCHHUB02.in.alcatel-lucent.com (135.250.12.35) with Microsoft SMTP Server (TLS) id 8.3.106.1; Thu, 14 Apr 2011 10:41:20 +0530
Message-ID: <4DA681C2.5070108@alcatel-lucent.com>
Date: Thu, 14 Apr 2011 10:40:26 +0530
From: Manav Bhatia <manav.bhatia@alcatel-lucent.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9 ThunderBrowse/3.3.5
MIME-Version: 1.0
To: "curtis@occnc.com" <curtis@occnc.com>
References: <201104140507.p3E57IrZ030963@harbor.orleans.occnc.com>
In-Reply-To: <201104140507.p3E57IrZ030963@harbor.orleans.occnc.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
Cc: "ospf@ietf.org" <ospf@ietf.org>
Subject: Re: [OSPF] FW: Using dynamically derived Traffic Keys for Routing Protocols
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Apr 2011 05:11:44 -0000

Hi Curtis,

>
> You might want to say "for doing *session* key rollovers".  The
> persistant key rollover would need a different mechanism.
>

I had actually meant a persistant key rollover. Why would this mechanism 
not work there?

Assume A and B are speaking to each other and A now wants to move to a 
different key. All it needs to do is to generate a new Nonce that will 
be fed into the KDF that B will use to generate the new traffic key.

Also note that the keys used in this proposal will not be symmetrical.

Cheers, Manav

v2.23.0 | Report a Bug | By Email