Re: [Pana] RFC 6345 errata

Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp> Fri, 14 October 2011 04:17 UTC

Return-Path: <yoshihiro.ohba@toshiba.co.jp>
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 4BA9921F8BF0 for <pana@ietfa.amsl.com>; Thu, 13 Oct 2011 21:17:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.089
X-Spam-Level:
X-Spam-Status: No, score=-4.089 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2YivLTxG9gHi for <pana@ietfa.amsl.com>; Thu, 13 Oct 2011 21:17:55 -0700 (PDT)
Received: from imx2.toshiba.co.jp (inet-tsb5.toshiba.co.jp [202.33.96.24]) by ietfa.amsl.com (Postfix) with ESMTP id 6C93721F8B15 for <pana@ietf.org>; Thu, 13 Oct 2011 21:17:54 -0700 (PDT)
Received: from arc1.toshiba.co.jp ([133.199.194.235]) by imx2.toshiba.co.jp with ESMTP id p9E4HqAl020039; Fri, 14 Oct 2011 13:17:52 +0900 (JST)
Received: (from root@localhost) by arc1.toshiba.co.jp id p9E4HqV2013775; Fri, 14 Oct 2011 13:17:52 +0900 (JST)
Received: from unknown [133.199.192.144] by arc1.toshiba.co.jp with ESMTP id PAA13771; Fri, 14 Oct 2011 13:17:52 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1]) by ovp2.toshiba.co.jp with ESMTP id p9E4Hp1Z005348; Fri, 14 Oct 2011 13:17:51 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id p9E4HxqC010104; Fri, 14 Oct 2011 13:17:59 +0900 (JST)
Received: from [133.196.16.80] by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTPA id <0LT100G7MFXRRO60@mail.po.toshiba.co.jp>; Fri, 14 Oct 2011 13:17:51 +0900 (JST)
Date: Fri, 14 Oct 2011 13:17:47 +0900
From: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-reply-to: <55333056-0FF8-464E-B503-E00FBEDE5FE7@yegin.org>
To: Alper Yegin <alper.yegin@yegin.org>
Message-id: <4E97B7EB.8050004@toshiba.co.jp>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-2022-JP
Content-transfer-encoding: 7bit
References: <4E96EC8A.9050803@toshiba.co.jp> <55333056-0FF8-464E-B503-E00FBEDE5FE7@yegin.org>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
Cc: "pana@ietf.org" <pana@ietf.org>
Subject: Re: [Pana] RFC 6345 errata
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: Fri, 14 Oct 2011 04:17:56 -0000

(2011/10/14 0:54), Alper Yegin wrote:
> Thanks for catching this.
> I confirm it is a bug and your fix handles it.

OK.  I will submit errata on this.

How about a potential typo(?) on RFC 5191 that I submitted a couple of
months ago for RFC 5191?

http://www.ietf.org/mail-archive/web/pana/current/msg03473.html

"
There is inconsistency about Key-Id data type as follows:

In Section 5.3, "The Key-Id AVP is of type Unsigned32 ..."

In Section 8.4, "The Key-Id AVP (AVP Code 4) is of type Integer32 ..."

The text in Section 8.4 seems incorrect, and should be corrected to:
"The Key-Id AVP (AVP Code 4) is of type Unsigned32 ..."
"

Yoshihiro Ohba

> 
> Alper
> 
> On Oct 13, 2011, at 4:50 PM, Yoshihiro Ohba wrote:
> 
>> My colleague Tanaka-san found out a potential error in RFC 6345 (PANA
>> relay).
>>
>> The following paragraph in Section 2:
>>
>> "
>> When the PRE receives the PRY message, it retrieves the PAA-
>> originated PANA message from the Relayed-Message AVP and the PaC's
>> IP address and UDP port number from and PaC-Information AVPs.  The
>> PAA-originated PANA message is sent to the PaC's IP address with
>> the source UDP port number set to the PANA port number (716) and
>> the destination UDP port number set to the UDP port number contained
>> in the Relayed-Message AVP.
>> "
>>
>> should read:
>>
>> "
>> When the PRE receives the PRY message, it retrieves the PAA-
>> originated PANA message from the Relayed-Message AVP and the PaC's
>> IP address and UDP port number from and PaC-Information AVPs.  The
>> PAA-originated PANA message is sent to the PaC's IP address with
>> the source UDP port number set to the PANA port number (716) and
>> the destination UDP port number set to the UDP port number contained
>> in the PaC-Information AVP.
>> "
>>
>> (s/Relayed-Message/PaC-Information/ in the last sentence.)
>>
>> Regards,
>> Yoshihiro Ohba
>> _______________________________________________
>> Pana mailing list
>> Pana@ietf.org
>> https://www.ietf.org/mailman/listinfo/pana
> 
>