Re: Protocol Draft - KEYINFO-TLV

Evangelos Haleplidis <ehalep@gmail.com> Tue, 01 April 2008 21:20 UTC

Message-Id: <WED.2.APR.2008.002000.0300.>
Date: Wed, 2 Apr 2008 00:20:00 +0300
From: Evangelos Haleplidis <ehalep@gmail.com>
Subject: Re: Protocol Draft - KEYINFO-TLV
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-7"
Content-Transfer-Encoding: 7bit

Greetings again to the list,

I have a new question regarding the KeyInfoTLV.

Page 45:
       KEYINFO-TLV := KeyID FULLDATA-TLV

Page 46 About KeyData.
      *  The key's data is the data to look for in the array, in the
         fields identified by the key field.  The information is encoded
         according to the rules for the contents of a FULLDATA-TLV, and
         represent the field or fields which make up the key identified
         by the KeyID.

If I understand this correctly then the KeyInfoTLV should look like this:

     0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |        Type = KeyInfo         |               Length          |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                             KeyID                             |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |        Type = FullData        |               Length          |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                         Value=KeyData                         |
    .                                                               .
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

If this is the case, then does the KeyInfo Length contains also the length
of the KeyData?

Also, since there is only one KeyID, wouldn't the following format be more
useful:

     0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |        Type = KeyInfo         |               Length          |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                             KeyID                             |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                            KeyData                            |
    .                                                               .
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Whereas "KeyData_Length = Length - 8" and a different TLV for the KeyData is
not needed?

Is there a specific reason why KeyData is needed as a different TLV? From
the BNF I understand that the Key and the Fulldata (KeyData) go, when used,
together. Why split them?

Regards,
Evangelos Haleplidis.

-----Original Message-----
From: Forwarding and Control Element Separation
[mailto:FORCES@PEACH.EASE.LSOFT.COM] On Behalf Of Wang,Weiming
Sent: Tuesday, April 01, 2008 6:03 PM
To: FORCES@PEACH.EASE.LSOFT.COM
Subject: Re: Protocol Draft - KEYINFO-TLV

Hi Evangelos,