Subject: [manet] DLEP-17: initial assignment tables & nearby text

From: RJ Atkinson <[email-masked]>
Date: Tue, 24 Nov 2015 12:47:27 -0500

1. Signals/Messages
--------------------
Section 9.0, 3rd paragraph, says:
	“The core DLEP signals and messages are:”

Table 1, which contains also items that I had not thought
were “core DLEP signals and messages” (e.g. Private Use
allocation), then follows.

My suggestion is to change the text above to read:
	“The core DLEP signals and messages have Type Code
         values from 1 to 16, inclusive.  The initial values
         for the DLEP Signals & Messages Registry are found
         in Table 1.”

2. Data Items
--------------
Section 10.0, 2nd paragraph, says:
	“The core DLEP data items are:”

Table 2, which contains also items that I had not thought
were “core DLEP data items” (e.g. Private Use allocation)
then follows.

My suggestion is to change the quoted text above to read:
	“The core DLEP data items have Type Code values 
	from 1 to 20, inclusive.  The initial values for
        the DLEP Data Item Registry are found in Table 2.”

3. Status Codes
---------------
(We don’t seem to have a defined set of “core” DLEP status codes,
which is OK with me, but unexpected after defining “core” values
earlier.)

I suggest inserting the following sentence just before
Table 3:
	“The initial values for the DLEP Status Codes Registry
	are found in Table 3.”

4. Extension Types
------------------

(editorial) 
Section 12.6 says in part:
	“Current allocations are:”

This ought instead to read:
	“Initial allocations are:”

because the reader’s definition of “current” is "when
they are reading the specification", rather than 
"the date that the specification was written”.

The “current” set is whatever the IANA Registry web page
says on the “current day” that one looks at that registry.

Thanks,

Ran