Subject: [manet] DLEP-16: enhancing/extending DLEP

From: RJ Atkinson <[email-masked]>
Date: Mon, 17 Aug 2015 16:56:16 -0400

Earlier, on Friday July 17th 2015, Rick Taylor wrote, 
in part:
> As designed, 1 extension introduces 0..N signals and 
> 0..N data items, ...

ISSUE:

Surprisingly, the above quote is not something that one
readily can puzzle out from reading the actual DLEP text
specification (from version 15 or from version 16).

In fact, I cannot find ANY text in either version of
DLEP (15 or 16) that actually says this.

The approach outlined in the quote above is fine with me, 
but the DLEP specification is clear as mud about this
and needs to be edited to be crystal clear.

REQUESTED ACTION:

This needs to be clarified in the DLEP specification,
at least in these places:

- Section 3, 3rd paragraph or 4th paragraph, page 10.
- Section 3.1, 2nd paragraph, page 11.
- Section 9.6, 2nd paragraph, page 39.

Also, it probably ought to be repeated one additional time, 
in the IANA Considerations sub-section that defines the 
“DLEP Extensions” registry, which is the bit IANA would
read ordinarily.  Usually, an RFC is written so that the
good folks at IANA don’t have to read the entire RFC to
learn all the details they need to know for correct
allocation of code points in future.

Thanks,

Ran