[rfc-i] How to indent artwork with surrounding block

[brian.e.carpenter at gmail.com (Brian E Carpenter)]

...
>>> *One* way to do so is to
>>> insert the "<CODE BEGINS>" / "<CODE ENDS>" brackets.

Sure. It's suggested for when the "code" conditions aren't applied
implicitly, i.e. when using a form of code that isn't listed at
http://trustee.ietf.org/license-info/Code-Components-List-4-23-09.txt

I use them in a current draft that contains CDDL, for example, because
I want that CDDL to be available for anyone to use in a syntax-driven
implementation. But I don't need them for the values defined in the IANA
Considerations, because those are automatically covered as "tables of values".

"classical programming code" is also covered automatically, so you don't
need the markers for C code, ever.

The Trust documents are crystal clear. It's a choice the document author
needs to make.

   Brian