Re: [tcpm] tcp-auth-opt issue: support for NATs

"Dan Wing" <dwing@cisco.com> Fri, 08 August 2008 01:46 UTC

Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B4DF53A6C5A; Thu, 7 Aug 2008 18:46:27 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E4C833A68C0 for <tcpm@core3.amsl.com>; Thu, 7 Aug 2008 18:46:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7OmfOe7p8Xk8 for <tcpm@core3.amsl.com>; Thu, 7 Aug 2008 18:46:25 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 1C8BC3A6C5A for <tcpm@ietf.org>; Thu, 7 Aug 2008 18:46:25 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.31,323,1215388800"; d="scan'208";a="63053858"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-1.cisco.com with ESMTP; 08 Aug 2008 01:46:25 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m781kPWD030387; Thu, 7 Aug 2008 18:46:25 -0700
Received: from dwingwxp01 ([10.32.240.194]) by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m781kOlx001626; Fri, 8 Aug 2008 01:46:24 GMT
From: Dan Wing <dwing@cisco.com>
To: 'Eric Rescorla' <ekr@networkresonance.com>, 'Joe Touch' <touch@ISI.EDU>
References: <4890F4BE.6060302@isi.edu><396556a20807301622l4cb33deuff73cd13d7a75ba1@mail.gmail.com><4890FBE8.1020203@isi.edu><396556a20807311700w1eda50b0o5da7ae52e6c1691a@mail.gmail.com><48935FFD.4090805@isi.edu><396556a20808051826w1a839577q956f379f56db1165@mail.gmail.com><20080806020257.D1C69525D8F@kilo.rtfm.com><396556a20808061742y19f8f5fh78fe66bfe4d415be@mail.gmail.com><20080807011812.DDC8050846@romeo.rtfm.com><396556a20808071047q5bda8acbje7a8fc9f9bf2e597@mail.gmail.com><20080807180512.77604529E4D@kilo.rtfm.com><489B3B72.8030604@isi.edu><20080807182005.04B5B52A03A@kilo.rtfm.com><489B407A.6030001@isi.edu><20080807185224.3A46750846@romeo.rtfm.com><489B4436.1000807@isi.edu> <20080807190941.E539F50846@romeo.rtfm.com>
Date: Thu, 07 Aug 2008 18:46:24 -0700
Message-ID: <21e501c8f8f8$91008f50$d35d150a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: Acj4wPZRNohPGFAHTeGyyW6YpNCsPwANsvZA
In-Reply-To: <20080807190941.E539F50846@romeo.rtfm.com>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=819; t=1218159985; x=1219023985; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dwing@cisco.com; z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com> |Subject:=20RE=3A=20[tcpm]=20tcp-auth-opt=20issue=3A=20supp ort=20for=20NATs |Sender:=20; bh=rQwK5InbW30j0HqEO9Xws5Q7aVOb+mW9sk/Xu038Eec=; b=uAqC5RbXZczRjPuawTl9GKSke4/DlFlqsDco+L1oa2Xt3kS0VHimQtltEW N1/P+QwQLDAv20dSiGLQG8BCnZFgarivPwYEw6Cx+9u/b0PSqNwHRlLMHAUZ nxawVv91c8;
Authentication-Results: sj-dkim-4; header.From=dwing@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; );
Cc: 'Adam Langley' <agl@imperialviolet.org>, tcpm@ietf.org
Subject: Re: [tcpm] tcp-auth-opt issue: support for NATs
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

> > Alternately, a good KMS could figure out when these IP addresses
> > changed, and update the TSAD accordingly. I would prefer this latter
> > solution...
> 
> Yeah, but what does that say about manual key management, 
> which is what we're going to have for the foreseeable future.

I agree with Eric.  

Using IP addresses as identifiers seems ill-advised now-a-days.  Ignoring
NATs, the same device can legitimately acquire different IP addresses
throughout one day (roaming from wireless access point to wireless access
point).  It might be a reasonable optimization, or a useful additional
security property, to require or to expect a key-id to come from the same IP
address it came from last time -- but I don't think it should be necessary
that the key-id come from the same IP address.

-d

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm