[NSIS] NATFW message format

Hi,

while reading section 4 (NATFW NSLP Message Components), I noticed the
following minor issues:

 * The order the objects may appear in a message is not specified.
   If there is no fixed order, it should be stated explicitly. It
   could also be noted that only one object of a type may appear
   in a message.

 * It would be nice to have preliminary object type IDs to make sure
   experimental implementations are compatible. The message types
   already have IDs.

 * The "Forward" treatment is never used in the draft. Is there a use
   case where it is necessary?

 * The NATFW_LT object is named "session lifetime", but sections
   4.3.[123] just use "lifetime".

 * The NATFW_INFO object has a 16 bit object type, while the common 
   object header only allows for 12 bits.

 * The NATFW_DTINFO_IPv4 object seems to have a variable length, judging
   from text and diagram, but the length is specified as 3 words.

 * The NATFW_TRACE's hop count seems to be unnecessary. The number of
   hops can be derived from the number of IP addresses in this object.

 * Is the NATFW_CREDENTIAL's length field really necessary? A concrete
   credential type could still decide to use these bits as a length
   field to support padding. For other credential types it might not
   be needed. If the credential data is a multiple of 32 bit, the
   leading 16 bit could be used as padding.

 * Would a version number in the message header make sense?

Thanks for reading,
	Matthias

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis