Re: [Pana] RFC 6345 errata

(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
> 
> 