Re: [rfc-i] Multi-level bulleted list

Apologies, Krzysztof, for misspelling your name!

On 6/3/22 12:37 PM, Jean Mahoney wrote:
>
> Krysztof,
>
> To create a nested list like the one below, use the following 
> construction:
>
> <ul>
>    <li>
>      <t>Let's take a look at...</t>
>      <ul>
>        <li>The first and second entry...</li>
>        <li>The third entry...</li>
>      </ul>
>    </li>
>    <li>Some other stuff I added to this example...</li>
> </ul>
>
> which will create the following output:
>
>     *  Let's take a look at...
>
>        -  The first and second entry...
>
>        -  The third entry...
>
>     *  Some other stuff I added to this example...
>
> The key is to use <t/> around the text that is outside the nested list.
>
>
> More information on nested lists can be found here:
>
> https://authors.ietf.org/en/lists-in-rfcxml
>
>
> Best regards,
>
> Jean
>
>
> On 6/3/22 12:08 PM, Krzysztof Szarkowicz wrote:
>> Hello,
>>
>> I see some drafts use multi-level bulleted lists. For example 
>> https://datatracker.ietf.org/doc/html/draft-ietf-rtgwg-bgp-pic-18, in 
>> Section 5.2:
>>
>>
>>    o  Let's take a look at the flattened pathlist used by the prefix
>>       "VPN-IP2", The pathlist associated with the prefix "VPN-IP2" has
>>       three entries.
>>
>>        o The first and second entry have index "0". This is because
>>          both entries correspond to ePE2. Thus when hashing performed
>>          by the forwarding engine results in using first or the second
>>          entry in the pathlist, the forwarding engine will pick the
>>          correct VPN label "VPN-L22", which is the label advertised by
>>          ePE2 for the prefix "VPN-IP2".
>>
>>        o The third entry has the index "1". This is because the third
>>          entry corresponds to ePE3. Thus when the hashing is performed
>>          by the forwarding engine results in using the third entry in
>>          the flattened pathlist, the forwarding engine will pick the
>>          correct VPN label "VPN-L32", which is the label advertised by
>>          "ePE3" for the prefix "VPN-IP2”.
>>
>>
>> I couldn’t figure out, how to create such lists with version 3 XML 
>> template.
>>
>> Do you have some example (for version 3 XML template)?
>>
>>
>> Thank you,
>> Krzysztof
>>
>>
>>
>>
>> _______________________________________________
>> rfc-interest mailing list
>> rfc-interest@rfc-editor.org
>> https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest
>
> _______________________________________________
> rfc-interest mailing list
> rfc-interest@rfc-editor.org
> https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest