Re: [IPFIX] I-D Action: draft-ietf-ipfix-text-adt-08.txt

Brian,

> So you're talking about distinguishing among typed export types (i.e., how to handle internal storage at an EP or CP), and this document is about textual representation of these data types (where the internal storage is (1) not in scope and (2) as per section 4.2 is only a matter of implicit ranges when no explicit range for an IE is given.
>
> I'm really not seeing how these relate.

Nope; I'm saying that in one line you should explain how reduced size 
encoding works wrt text encoding, using the example you've created using 
tcpControlBits:

          tcpControlBits(6)<unsigned16>[1]


Here the size of [1] doesn't immediately seem to agree with the 
<unsigned16> type.

So under Figure 1 you could say, "Note that IPFIX Reduced-Size Encoding 
[RFC7011] is being used for tcpControlBits."

(The same was done under Figure 19 in RFC6313.)

This both shows readers how to use RSE with textual encodings, and 
prevents future errata from "correcting" this apparent "mistake".

P.

_______________________________________________
IPFIX mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ipfix