Subject: Appendix A Revisions required for consistency with proposed Issue 319 resolution

From: Bernard Aboba <[email-masked]>
Date: Tue, 27 Oct 2009 22:03:28 -0700

In looking through Appendix A, there are some sections that are inconsistent with the revisions proposed in Issue 319:

* Section A.1.1 refers to the integer64 data type, and does not include mention the potential Interface-Id type. 
   Does the data fit within the existing RADIUS data model, as outlined
   below?  

could be clarified by changing it to:
   
   Does the data fit within the basic data types described in Section 2.1.1,
   as outlined below? 

* Section A.2 says:

   All data types other than the ones described above in Appendix A.1
   SHOULD NOT be used.  This section describes in detail a number of
   data types that are NOT RECOMMENDED in new RADIUS specifications.
   Where possible, replacement data types are suggested.

To make it clear that existing complex types are not being deprecated, the text might be changed to say "described in Appendix A.1 and Appendix B"

* Section A.2.1 mentions integer64 data types.   

* The advice on authentication security attributes needs to be sync'd up with the new proposed text. 

* The advice on a 16-bit type field is inconsistent with the recently revised text. 

* Section A.2.2 might say "define a complex type not described in Appendix B which..."