Re: [Dime] Review of draft-ietf-dime-local-keytran-03

jouni korhonen <jouni.nospam@gmail.com> Mon, 17 May 2010 21:10 UTC

Return-Path: <jouni.nospam@gmail.com>
X-Original-To: dime@core3.amsl.com
Delivered-To: dime@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6D18528C156 for <dime@core3.amsl.com>; Mon, 17 May 2010 14:10:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.955
X-Spam-Level:
X-Spam-Status: No, score=-0.955 tagged_above=-999 required=5 tests=[AWL=-0.215, BAYES_20=-0.74]
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 Rbb3doSzvqQ7 for <dime@core3.amsl.com>; Mon, 17 May 2010 14:09:59 -0700 (PDT)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.152]) by core3.amsl.com (Postfix) with ESMTP id 5B67F28C154 for <dime@ietf.org>; Mon, 17 May 2010 14:09:59 -0700 (PDT)
Received: by fg-out-1718.google.com with SMTP id l26so2322647fgb.13 for <dime@ietf.org>; Mon, 17 May 2010 14:09:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=mll0UwSAMw89AJX5A/CT5yllvcSeKmVgYfiXMckCmEU=; b=kPouBOrj/CNNnYq62iUWCRRSn/f7/PYu0YJXuwldFv2nR59YtTotIt2Xl8Mlppz8l2 VDPaTDgPRY+6zQDY2s624oxsRHdoqAl2x+l8lIS8aBcyi3cMrkX1SnnE9FVVN0WUszeo JaaAVKsxlHard4+K8K0gA9SwOYa/DJ/nsm8vQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=S0qDxn4INJQHUE394bp7NhqPlPgyX4d3RPxzFfM3ZTb3mfWbrB2V8E8aZDE9R1B/9H /IHBcW3X0T1SgC8QgLZ1oNqz3voOvah9PF84wcJLFOia9D2gj5RND+m8E7d226cCrjZm fEfGkxK4JOiioSMDAkxvUxMHNiSrPyJzgYMYo=
Received: by 10.86.22.31 with SMTP id 31mr9454922fgv.24.1274130586620; Mon, 17 May 2010 14:09:46 -0700 (PDT)
Received: from a88-114-68-184.elisa-laajakaista.fi (a88-114-68-184.elisa-laajakaista.fi [88.114.68.184]) by mx.google.com with ESMTPS id e20sm5902504fga.11.2010.05.17.14.09.43 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 17 May 2010 14:09:44 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset="us-ascii"
From: jouni korhonen <jouni.nospam@gmail.com>
In-Reply-To: <AC1CFD94F59A264488DC2BEC3E890DE50A554399@xmb-sjc-225.amer.cisco.com>
Date: Tue, 18 May 2010 00:09:41 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <2BE3AA30-C1D6-41F1-9D6C-305DB8E1E867@gmail.com>
References: <AC1CFD94F59A264488DC2BEC3E890DE50A43AE83@xmb-sjc-225.amer.cisco.com> <00b701caedc5$92e4d150$b8ae73f0$@net> <AC1CFD94F59A264488DC2BEC3E890DE50A554125@xmb-sjc-225.amer.cisco.com> <000401caf25d$420b7d50$c62277f0$@net> <BLU0-SMTP1379FA02B7E014A72ABF23D8FC0@phx.gbl> <AC1CFD94F59A264488DC2BEC3E890DE50A554399@xmb-sjc-225.amer.cisco.com>
To: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>, Tom Taylor <tom111.taylor@bell.net>, Glen Zorn <gwz@net-zen.net>
X-Mailer: Apple Mail (2.1078)
Cc: dime@ietf.org
Subject: Re: [Dime] Review of draft-ietf-dime-local-keytran-03
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dime>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 May 2010 21:10:00 -0000

<chair mode>
So, everybody happy with Joe's proposal of leaving the domain out? If so, a new revision would be needed so that we can get this sorted out and successfully conclude the WGLC.

- Jouni


On May 13, 2010, at 7:35 PM, Joseph Salowey (jsalowey) wrote:

>>> 
>>> Tom Taylor mentioned this as well but I am still puzzled by it: in
> what
>>> scenario could this occur?  AFAIK all the keys are bound to a
> particular
>>> session which is itself bound to a particular access point.  What am
> I
>>> missing?
>>> 
>>> ...
>> [PTT]
>> OK, this is one for the architecture to answer. I'll review the
> different
>> interfaces to see if there is a case of anticipatory keying that isn't
>> bound as
>> tightly as you suggest. At the very least, I don't think the keys
> passed
>> to a
>> local ER server would be bound to a particular access point, but they
> may
>> indeed
>> be bound to a particular session, in some sense of session.
> 
> 
> [Joe] I can't think of a reason why the domain wouldn't already be known
> to the session.  I'd be okay with leaving the domain out until there is
> a use-case for it.  
> _______________________________________________
> DiME mailing list
> DiME@ietf.org
> https://www.ietf.org/mailman/listinfo/dime