Re: [Pana] "PRF key" in RFC 5191 Section 8.5

Alper Yegin <alper.yegin@yegin.org> Thu, 24 January 2013 09:22 UTC

Return-Path: <alper.yegin@yegin.org>
X-Original-To: pana@ietfa.amsl.com
Delivered-To: pana@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6860221F84DE for <pana@ietfa.amsl.com>; Thu, 24 Jan 2013 01:22:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hJ78LE+pqL7q for <pana@ietfa.amsl.com>; Thu, 24 Jan 2013 01:22:10 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id B461421F86B7 for <pana@ietf.org>; Thu, 24 Jan 2013 01:22:10 -0800 (PST)
Received: from [192.168.2.49] (88.247.135.202.static.ttnet.com.tr [88.247.135.202]) by mrelay.perfora.net (node=mrus3) with ESMTP (Nemesis) id 0Mh9uD-1UKUaG1qMr-00N4qA; Thu, 24 Jan 2013 04:21:56 -0500
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset="us-ascii"
From: Alper Yegin <alper.yegin@yegin.org>
In-Reply-To: <50FC996E.5050801@toshiba.co.jp>
Date: Thu, 24 Jan 2013 11:21:52 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <48FF7BF6-DB35-4B2B-AAC4-01D7E2672BDE@yegin.org>
References: <50FC996E.5050801@toshiba.co.jp>
To: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
X-Mailer: Apple Mail (2.1283)
X-Provags-ID: V02:K0:DjgOpnsKqT8giaCjjzwYaPEPewsV7w4QLdRB2B6kf38 w8PqbzR2uc/RiSypKUJun9Um+30gAA3DQJ6vsezLU21oscrwPk 44ZMtB7Kevx4EO7GvLzb4q3p1SVLKZ7yFwxo6nLyYu3/6/pMxJ AAjefI06IN5cdkyjfhHNdlKMFUToPtI8GMdBuriO15ibJg07a4 JKyo9OYex2cYjMKcIeczcOGCjQtZuyKudavSWVNnnQHP/rHwY2 drvdw0rS3t1m2fc7YyftEiQe5WlBKetpBni4U6wtFpOKH9ib7j ZVGO7jnEns0E8sESW0cVScgF2I9ABFR5wlplzEpH/uPQQ2NPlW DyGMt7q+9rT75eEVTk8nPavk8vmMj8JNM+YJuBYQdF/rR4Yzj4 0szabiBZ1j57g==
Cc: pana@ietf.org
Subject: Re: [Pana] "PRF key" in RFC 5191 Section 8.5
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jan 2013 09:22:11 -0000

Yoshi,

I think your interpretation is correct, as the "e.g." examples confirm.

Alper


On Jan 21, 2013, at 3:27 AM, Yoshihiro Ohba wrote:

> I got a question from my colleague about meaning of "PRF key" in the
> following text in Section 8.5:
> 
> "
> 1. The PaC and the PAA each are likely to be able to compute a
> random nonce (according to [RFC4086]). The length of the nonce
> has to be 1/2 the length of the PRF key (e.g., 10 octets in the
> case of HMAC-SHA1).
> 
> 2. The PaC and the PAA each are not trusted with regard to the
> computation of a random nonce (according to [RFC4086]). The
> length of the nonce has to have the full length of the PRF key
> (e.g., 20 octets in the case of HMAC-SHA1).
> "
> 
> As far as I remember, "PRF key" means "output block of the negotiated
> pseudo-random function used in prf+". So HMAC-SHA1 is prf, the output
> block length is 20 octets.
> 
> Please let me know if you interpret "PRF key" in the above text in other
> ways.
> 
> Best Regards,
> Yoshihiro Ohba
> 
> 
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www.ietf.org/mailman/listinfo/pana