Protocol Draft - KEYINFO-TLV
Evangelos Haleplidis <ehalep@gmail.com> Mon, 31 March 2008 21:06 UTC
Message-Id: <TUE.1.APR.2008.000641.0300.>
Date: Tue, 01 Apr 2008 00:06:41 +0300
From: Evangelos Haleplidis <ehalep@gmail.com>
Subject: 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 some comment regarding the KEYINFO-TLV. 1. As with the PathData TLV there was no Graph, so I made up one. I include it in the end of the mail. 2. About the KeyID, it is not specified specific in the document what the size is. I guess it is an integer, shouldn't it be specified for clarity? How many Keys may exist for a specific table? Could/Should the KeyID be limited to less than 4 bytes? 3. In Page 45 it is written: KEYINFO-TLV := KeyID FULLDATA-TLV Shouldn't it be changed to: KEYINFO-TLV := KeyID KEYDATA KEYDATA := FULLDATA-TLV Or KEYINFO-TLV := KeyID KeyData This would be in accordance with the examples also in the appendix. Regards, Evangelos Haleplidis. =============================== KeyInfo-TLV Graph 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 | . . +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
- Re: Protocol Draft - KEYINFO-TLV Joel M. Halpern
- Protocol Draft - KEYINFO-TLV Evangelos Haleplidis
- Re: Protocol Draft - KEYINFO-TLV Evangelos Haleplidis
- Re: Protocol Draft - KEYINFO-TLV Wang,Weiming
- Protocol Draft - KEYINFO-TLV Evangelos Haleplidis